View Single Post
Old 06-03-2016, 09:19 AM   #40
NiLuJe
BLAM!
NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.
 
NiLuJe's Avatar
 
Posts: 13,506
Karma: 26047202
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
@xor_: Basically can't for the life of me get the kernel to coredump automatically. Which is rather annoying, since this appears to be a semi-random crash and a PITA to trigger in any case.
And on top of that, coredumps generated by gcore appear to be borked...

So my cheap workaround would be attaching gdb to luajit in a tmux session, and making sure you're in a position to re-attach on crash (i.e., usbnet). Binaries for all that are available in there.

(Because *that*, at least, works to get useful stacktraces ).

EDIT: For ref., this is the GH issue we're talking about.

EDITē: And my comments on stacktraces were in this one.

@xor_: Good point on its name, I just fixed that.

Last edited by NiLuJe; 06-03-2016 at 09:27 AM.
NiLuJe is offline   Reply With Quote