O' big bug buster Bernhard! Congratulations on finding a similar bug.
You did better than I! I did as you suggested, and checked if my top 19 frames in gdb's back trace kind of repeat all the time. At this point, I think I have to report that, no, I can not confirm they repeat. I just see one copy. My main concern? The normal way of eliciting a back trace from within gdb didn't work. The non repeating lines were reported by defining a function in gdb and logging output to a file. Details are in this bug report's 15th message. Maybe it omitted duplicate lines. I dunno. But yeah, the stack traces to have some similar code. Thank you very much for finding the similar bug! So, Kingsley On 03/18/2019 18:22, Bernhard Übelacker wrote: > Hello Kingsley G. Morse Jr., > the backtrace of the crash you reported seems to be quite > similar to another bug reported in #908549. > > Can you confirm that you just forwarded the top 19 frames > and that they kind of repeat all the time? > > Kind regards, > Bernhard > > > #908549: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908549 -- Time is the fire in which we all burn.