You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When I use a specific regex pattern, lnav crashes on startup. The crash happens before patterns would be validated against the samples.
Take the i2p_router_log.json from this commit: ce88dce (this should be the same as the above, but doubly escaped for JSON)
Put that in a new format definition
Start lnav for any log file, or without one with lnav -N
I'll send the crash log in email.
This pattern is so complicated for the reason that the software it was made for produces several different kinds of log lines.
The top level group is for setting a regex flag.
There are 3 variants in it, each in its own group, for the primary log lines, Java exceptions, and the log format that is used at startup.
If any one of the first 2 variants are taken out, lnav does not crash anymore. That way the pattern looks like the following:
Without the primary format:
lnav version
v0.12.2
Describe the bug
When I use a specific regex pattern, lnav crashes on startup. The crash happens before patterns would be validated against the samples.
The regex pattern in question is the following:
To Reproduce
Steps to reproduce the behavior:
i2p_router_log.json
from this commit: ce88dce (this should be the same as the above, but doubly escaped for JSON)lnav -N
I'll send the crash log in email.
This pattern is so complicated for the reason that the software it was made for produces several different kinds of log lines.
The top level group is for setting a regex flag.
There are 3 variants in it, each in its own group, for the primary log lines, Java exceptions, and the log format that is used at startup.
If any one of the first 2 variants are taken out, lnav does not crash anymore. That way the pattern looks like the following:
Without the primary format:
Without exception recognition (used for marking errors):
The text was updated successfully, but these errors were encountered: