Debugger missing at IMA :(
Posted: Thu Feb 13, 2014 4:25 pm
I'm trying to debug a failure that occurs rare after days or weeks on a PB-program running on debian wheezy 64bit with lots of logging. I thought my last logging gave me a clue but too less to find the bug. I enabled the debugger and purifier and recreated the binary (so my binary was almost 2x in size) however after the next crash that followed in about a week I got nothing from PB-debugger and my log (with increased loglevel) refused my previous idea (it crashed somewhere fully different). All I got was some "double free or corruption (fasttop)" from glibc (I did not get this first time without debugger) but nothing from PBs debugger itself.
This is a pretty annoying situation now. Usually (using C/++) I would run the binary through gdb and make some backtrace now. However this is not really helpful with that PB-bin. So it seems I'm delivered to the PB debugger which is quiet for unknown reason. I've no idea why because if I create some quick faulty test-binary that allocates once and frees twice I get some info from the debugger (and yet again some glibc-message that is a bit different). However the real code is not that small that it's easy to find (I've counted about 150 FreeMemory()) and it seems it occurs just after days, sometime weeks of running and lots of users connecting and disconnecting in meanwhile without issues - so a debugger that is reliable would be pretty important. Any ideas?
Greetings,
auser
This is a pretty annoying situation now. Usually (using C/++) I would run the binary through gdb and make some backtrace now. However this is not really helpful with that PB-bin. So it seems I'm delivered to the PB debugger which is quiet for unknown reason. I've no idea why because if I create some quick faulty test-binary that allocates once and frees twice I get some info from the debugger (and yet again some glibc-message that is a bit different). However the real code is not that small that it's easy to find (I've counted about 150 FreeMemory()) and it seems it occurs just after days, sometime weeks of running and lots of users connecting and disconnecting in meanwhile without issues - so a debugger that is reliable would be pretty important. Any ideas?
Greetings,
auser