Re: How to catch GDB crash

Dmitry Smirnov
Tue Jul 8 08:27:00 GMT 2008


Most likely I've found the root cause: mi_on_resume() does not flush raw_stdout. I've added "gdb_flush (raw_stdout)" at the end of this function and everything seems to work fine.

Also, I've found a solution for Eclipse problem when it unable to work correctly after this "^running". On my mind it does not related to GDB (and to delayed "^running" :-) ), so I have no problems with GDB at this moment.

M-m-m, there is just one weird and minor observation: just after "target remote:12345" executed, Eclipse shows two identical threads: Thread[0] and Thread[1]. They are stopped at the same address. After I issued "-exec-continue" and GDB hits the breakpoint, Eclipse shows just one thread: Thread[1] with a correct call stack. Perhaps, I will have some time to debug it and get back if this is related to GDB.


-----Original Message-----
From: Pedro Alves <>
To:,  Dmitry Smirnov <>
Date: Mon, 7 Jul 2008 17:00:37 +0100
Subject: Re: How to catch GDB crash

> A Monday 07 July 2008 16:47:26, Dmitry Smirnov wrote:
> > Perhaps, "info threads" is fixed. But since both "info threads" and
> > "running" problems were [most probably] caused by the "main thread
> > registering" fix, maybe it is better to investigate "^running" problem
> > before submission? What if they are connected? ;-)
> I seriously doubt they are connected.  The code to output "^running"
> has nothing to do with having threads or not.
> > I have to say, that my goal is not just report issues, I would like to help
> > fixing them. 
> Welcome on board!  We need all the help we can get.
> > Unfortunately, I do not have much time to learn GDB, so I'm 
> > just asking for hints: what can I do to discover the root cause. 
> The best way is to do a binary search on the CVS HEAD sources, to
> find the patch that caused your issue.
> > For 
> > example, who is responding "^running"? What functions/files should I debug
> > to figure out the problem?
> Grepping for "^running" should get you there.  
> See here, your issue was most likelly introduced by this:
> -- 
> Pedro Alves

More information about the Gdb mailing list