------- Comment #13 from ebotcazou at gcc dot gnu dot org 2008-03-10 10:36
-------
> 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.
Thanks for experimenting.
> 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?
Probably. You can try to recompile the whole Emacs at -O0 though and see what
happens. Reopen the ticket if it behaves differently than at -O2.
--
ebotcazou at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |RESOLVED
Resolution| |INVALID
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35249
