This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: How to catch GDB crash
- From: Dmitry Smirnov <divis1969 at mail dot ru>
- To: gdb at sourceware dot org
- Date: Mon, 30 Jun 2008 19:56:56 +0400
- Subject: Re: How to catch GDB crash
- References: <E1KBsWk-000OcR-00.divis1969-mail-ru@f99.mail.ru>
- Reply-to: Dmitry Smirnov <divis1969 at mail dot ru>
Hi,
I've upgraded to gdb-6.8.50.20080630 and tested it.
Unfortunately, I was totally unable to run my test case from Eclipse CDT.
I've figured out that the problem is what GDB resonds to exec-run command.
Here is the Eclipse session log (it shows requests to GDB and responses)
84-exec-run
84^error,msg="Don't know how to run. Try \"help target\"."
I've tried older version of arm-elf-gdb (6.5):
123-exec-run
123^running
&"Don't know how to run. Try \"help target\".\n"
Don't know how to run. Try "help target".
123^error,msg="Don't know how to run. Try \"help target\"."
It seems that responses differs in 123^running (or maybe the order too?).
Is it possible to fix this?
Dmitry
-----Original Message-----
From: Dmitry Smirnov <divis1969@mail.ru>
To: Pedro Alves <pedro@codesourcery.com>
Date: Thu, 26 Jun 2008 18:32:46 +0400
Subject: Re: How to catch GDB crash
>
> Ok, you'd convinced me :-)
> You are right, the last resume() is executed with stepping_over_breakpoint equal to 1 whereas previously it was 0.
>
> I'll try your patch (I can find it in gdb-patches, right?).
>
> Dmitry
>
> -----Original Message-----
> From: Pedro Alves <pedro@codesourcery.com>
> To: gdb@sourceware.org, Dmitry Smirnov <divis1969@mail.ru>
> Date: Thu, 26 Jun 2008 15:20:54 +0100
> Subject: Re: How to catch GDB crash
>
> >
> > A Thursday 26 June 2008 14:56:26, Dmitry Smirnov wrote:
> > > I still have some doubts :-)
> > >
> >
> > Well, the doubts would go away if you tried the patches. :-)
> >