5 Nov
2014
5 Nov
'14
11:45 a.m.
Sam Hartman wrote:
Hmm, I actually expect that programs will not change their behavior when under a debugger.
I agree. The underlying reason for the changes was the idea to catch fatal signals in normal circumstances. i.e. rather than simply exiting, print out a stack trace of where the problem came from. Once that code went in, the normal gdb workflow didn't work. Which necessitated fixes to the debugging code... and down the rabbit hole we went.
I've been debugging fatal signals in freeradius a fair bit recently and I have always seen the debugger behave as I expect.
<sigh> lldb. It hates people. Alan DeKok.