This is the mail archive of the
insight-prs@sourceware.org
mailing list for the Insight project.
Re: insight/265: Insight crashes
- From: kseitz at sources dot redhat dot com
- To: akashrai at gmail dot com, insight-prs at sources dot redhat dot com, kseitz at sources dot redhat dot com, nobody at sources dot redhat dot com
- Date: 1 Sep 2005 04:19:19 -0000
- Subject: Re: insight/265: Insight crashes
- Reply-to: kseitz at sources dot redhat dot com, akashrai at gmail dot com, insight-prs at sources dot redhat dot com, kseitz at sources dot redhat dot com, nobody at sources dot redhat dot com, insight-gnats at sources dot redhat dot com
Synopsis: Insight crashes
Responsible-Changed-From-To: unassigned->kseitz
Responsible-Changed-By: kseitz
Responsible-Changed-When: Thu Sep 1 04:19:18 2005
Responsible-Changed-Why:
mine
State-Changed-From-To: open->analyzed
State-Changed-By: kseitz
State-Changed-When: Thu Sep 1 04:19:18 2005
State-Changed-Why:
How are you reloading the executable?
If your executable changes while you are debugging it, gdb will automatically reload it the next time you run it. You do not need to use the "file" command or "File->Open...".
The next time it crashes, can you add a stack backtrace to this PR?
http://sourceware.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=insight&pr=265