------- Comment #12 from simon dot marshall at misys dot com 2008-03-10 10:28 ------- > You really need to put the breakpoint on 'error' to be sure. Source location > information is seriously shaken by optimization in the 4.x series of compilers > so I wouldn't rely on it to put breakpoints in optimized code.
I put the call of error into a new function and put a breakpoint on that. The breakpoint on the new function is not hit when Emacs is starting. So, I can only conclude that the underlying problem is not a miscompilation by gcc. It seems to me that the underlying problem, which I still see and leads to the breakpoint on the new function being eventually hit when Emacs has been running for some time, is a bug in Emacs. Does that seem reasonable? Sorry for the wasted time, and thanks for looking at this. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35249
