Tim Stack
Tim Stack
What version of lnav are you using?
I've pushed back on this previously because I wanted lnav to work with just the existing files on disk and not have any extra footprint. So, yes, the performance hit...
I pushed a change that should address the common case. I would say a redesign of the UI needs to be done before trying to work on edge cases.
So, it looks like there's a few options here. The default output format for journalctl seems to be syslog, so you can pipe it directly into lnav: $ journalctl |...
Would you be able to change this part of the regex: > `>> (?.+) >> (?.*)$` Having more than one repetitive match of `.` is not going to work very...
Closing since it sounds like the format is working and crash is fixed.
> looking forward for the next release (even a statically linked beta will do) Can you give this a try: https://github.com/tstack/lnav/releases/tag/v0.11.1-beta1
Since you're already running it in `lldb`, can you try getting a full backtrace (enter `bt`).
Yeah, the deepness would be the problem, it's probably stuck in a loop and overflowing the stack.
@rggjan Thanks for the extra info! Is this log actually recognized as a log by lnav? It's good to know there's ANSI sequences in the log.