How to catch GDB crash

Pedro Alves
Mon Jul 7 16:01:00 GMT 2008

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