Odin Vex

Yes, edb segfaults, not the process being debugged. I've found a way to prevent it. As long as I don't interact with edb after I F9 resume it's fine and...

Edb seems to only crash if the process does something in particular, but unfortunately that's all I can determine. The nature of what I'm doing is sensitive.

I think it would be best if I could try to debug the issue locally. I've found it only segfaults if the target process goes through a specific routine. It's...

All gdb gives me: ``` Thread 1 "edb" received signal SIGSEGV, Segmentation fault. 0x0000556c07673aa6 in QDisassemblyView::drawJumpArrows(QPainter&, QDisassemblyView::DrawingContext const*) () ``` Edit: Attempted to consume those signals and `nostop nopass` them...

I'll attempt to use the AUR's `edb-debugger` package but edit the build routine to compile a debug. Meanwhile I'll try to see if disabling jump-arrows helps narrow. Edit: Disabling `Show...

Feedback, adding auth details to uri does not work, unfortunately. A mechanism to check for HTTP 401 should be added.

Further information: Extremely rarely Element may crash. I have not been able to capture logs regarding it. This is on an Android device with 8GB of RAM (more than 60%...

I will not allow my private e-mail address to be known just for some CLA. You already have my public GitHub e-mail, that alone is enough. If this is unacceptable...

Yes I know, "trace logs". There isn't a Issue template for "clarify what is happening". Not willing to risk data loss, given the confusion of that string.

The shell output/tty (Docker output). Log looked similar to https://www.reddit.com/r/Lidarr/comments/w9l7ow/why_is_lidarr_deleting_my_data/. I removed the Container for now, output not available.