From: Daniel Jacobowitz <drow@false.org>
To: Fred Fish <fnf@specifix.com>
Cc: gdb-patches@sourceware.org
Subject: Re: RFC: Don't kill the program after "file"
Date: Tue, 01 Aug 2006 22:11:00 -0000 [thread overview]
Message-ID: <20060801221105.GA22931@nevyn.them.org> (raw)
In-Reply-To: <200608011617.28914.fnf@specifix.com>
On Tue, Aug 01, 2006 at 04:17:28PM -0400, Fred Fish wrote:
> I'm currently getting new failures with a mips-elf toolchain, and
> other toolchains, when using the simulator for testing. I'm not
> entirely sure that they are due to this change, but it seems likely.
>
> Here is a snippet from the gdb.log file:
> (gdb) kill
> The program is not being run.
> (gdb) file /links/build/latest/trunk/mips-elf/gdb/gdb/testsuite/gdb.base/opaque
> A program is being debugged already.
> Are you sure you want to change the file? (y or n) ERROR: couldn't load /links/build/latest/trunk/mips-elf/gdb/gdb/testsuite/gdb.base/opaque into /links/build/latest/trunk/mips-elf/gdb/gdb/testsuite/../../gdb/gdb (timed out).
The simulator is being a bit schizophrenic. It is not running, yet it
is. This happens because inferior_ptid is set to null_ptid after kill
or before execution, and the sim target is left on the stack, but
to_has_execution is always set for "target sim".
As it happens I have patches for a similar issue with target
extended-remote. The remote patches are substantial, but I can
probably break out the simulator related bits. I'll try to do that.
They change target_has_execution from "is capable of running" to
"is running right now".
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-08-01 22:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-01 20:17 Fred Fish
2006-08-01 22:11 ` Daniel Jacobowitz [this message]
2006-08-10 20:08 ` Fred Fish
2006-08-17 18:48 ` Daniel Jacobowitz
-- strict thread matches above, loose matches on Subject: below --
2006-06-13 20:50 Daniel Jacobowitz
2006-06-14 19:55 ` Jim Blandy
2006-06-14 20:06 ` Jim Blandy
2006-06-26 19:00 ` Kevin Buettner
2006-07-12 20:16 ` Daniel Jacobowitz
2006-07-24 20:36 ` Daniel Jacobowitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060801221105.GA22931@nevyn.them.org \
--to=drow@false.org \
--cc=fnf@specifix.com \
--cc=gdb-patches@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox