From: Nick Roberts <nickrob@snap.net.nz>
To: Daniel Jacobowitz <drow@false.org>
Cc: Vladimir Prus <ghost@cs.msu.su>, gdb@sources.redhat.com
Subject: Re: Reporting of "program no longer exists"
Date: Sat, 14 Oct 2006 21:17:00 -0000 [thread overview]
Message-ID: <17713.21317.602083.615952@kahikatea.snap.net.nz> (raw)
In-Reply-To: <20061014210523.GA23445@nevyn.them.org>
> That's definitely possible, though I've only ever seen it with threads;
> in any case, wherever it appears, we should fix it. Losing track of
> the inferior this way is just silly.
I think Emacs does use threads (I don't know why). I also encounterd this
when trying to make GDB asynchronous. I think it was because I got to
ptrace (PTRACE_CONT,...) twice. The second encounter (and maybe the first)
being
if (ptrace (request, pid, 0, target_signal_to_host (signal)) == -1)
perror_with_name (("ptrace"));
in i386_linux_resume where it failed.
--
Nick http://www.inet.net.nz/~nickrob
next prev parent reply other threads:[~2006-10-14 21:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-14 16:33 Vladimir Prus
2006-10-14 16:39 ` Daniel Jacobowitz
2006-10-14 20:58 ` Nick Roberts
2006-10-14 21:05 ` Daniel Jacobowitz
2006-10-14 21:17 ` Nick Roberts [this message]
2006-10-15 4:36 ` Eli Zaretskii
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=17713.21317.602083.615952@kahikatea.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=ghost@cs.msu.su \
/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