Fix for very big pid and tid numbers in logcat_text
There can be no space after pid colon if tid is big enough in logcat long format. Change-Id: I8e03e78c88e4bef1a5fdb3a04b77f58fa7d055bc Reviewed-on: https://code.wireshark.org/review/5411 Reviewed-by: Michal Labedzki <michal.labedzki@tieto.com>
This commit is contained in:
parent
1d8673c0df
commit
1cde318117
|
@ -32,7 +32,7 @@
|
|||
#define THREAD_STRING "([IVDWEF])\\( *(\\d+): *(\\d+)\\) (.*)"
|
||||
#define PROCESS_STRING "([IVDWEF])\\( *(\\d+)\\) (.*)"
|
||||
#define THREADTIME_STRING "(\\d{2}-\\d{2} \\d{2}:\\d{2}:\\d{2}\\.\\d{3}) +(\\d+) +(\\d+) ([IVDWEF]) (.*?): (.*)"
|
||||
#define LONG_STRING "\\[ (\\d{2}-\\d{2} \\d{2}:\\d{2}:\\d{2}\\.\\d{3}) +(\\d+): +(\\d+) ([IVDWEF])/(.+) ]\\R(.*)"
|
||||
#define LONG_STRING "\\[ (\\d{2}-\\d{2} \\d{2}:\\d{2}:\\d{2}\\.\\d{3}) +(\\d+): *(\\d+) ([IVDWEF])/(.+) ]\\R(.*)"
|
||||
|
||||
wtap_open_return_val logcat_text_open(wtap *wth, int *err, gchar **err_info);
|
||||
|
||||
|
|
Loading…
Reference in New Issue