On 2015/04/17 10:22, Mark Kettenis wrote: > > Date: Fri, 17 Apr 2015 09:04:26 +0100 > > From: Nicholas Marriott <[email protected]> > > > > Hi > > > > No not much use without symbols unfortunately. > > Stuart, > > If your didn't update your source tree, building tmux with make > DEBUG=-g and it should be possible to use the new binary to produce > backtraces with the old core dump. Just ignore the warning that GDB > gives you ;). > > Do check though that the optimization options don't change if you pass > DEBUG=-g. Sometimes that leaves off the -O2 option. In that case, > build with DEBUG="-g -O2". If you're paranoid you can disassemble the > critical bits of code in the original binary and compare with the new > binary.
I tried that already on the off chance (though wasn't expecting much as I was running a snapshot rather than my own build), but it didn't produce usable results. (gdb) bt #0 0x00000d5772447633 in ?? () #1 0x00007f7ffffc4510 in ?? () #2 0x00000d577255a990 in ?? () #3 0x00000d5a16e24680 in ?? () #4 0x0000000000006000 in ?? () #5 0x00000d5991538000 in ?? () #6 0x00007f7ffffc4510 in ?? () #7 0x00000018304ba610 in ?? () #8 0x0000000000000001 in ?? () #9 0x2011080800009560 in ?? () #10 0x0000000000000000 in ?? () Actually, it seems if I try that with any program with known consistent source (e.g. build games/rain without -g, run it, send it -ABRT, rebuild with -g, run gdb) I get similar useless traces.
