From: Nick Roberts <nickrob@snap.net.nz>
To: Daniel Jacobowitz <drow@false.org>
Cc: Vladimir Prus <ghost@cs.msu.su>, gdb-patches@sources.redhat.com
Subject: Re: Reporting of "program no longer exists"
Date: Sun, 15 Oct 2006 19:47:00 -0000 [thread overview]
Message-ID: <17714.36770.10163.719995@kahikatea.snap.net.nz> (raw)
In-Reply-To: <20061015154128.GA14607@nevyn.them.org>
Daniel Jacobowitz writes:
> On Sun, Oct 15, 2006 at 06:13:15PM +1300, Nick Roberts wrote:
> > Currently if I run Emacs under GDB and type CTRL-C I get:
> >
> > (gdb) r
> > Starting program: /home/nickrob/emacs/src/emacs -geometry 80x40+0+0
> > [Thread debugging using libthread_db enabled]
> > [New Thread -1208174912 (LWP 7704)]
> > [Switching to Thread -1208174912 (LWP 7704)]
> > Breakpoint 3 at 0x80f654b: file xterm.c, line 7833.
> > Couldn't get registers: No such process.
>
> I assume this is a prerelease. The emacs21 I've got doesn't use
> pthreads at all.
Yes.
> > If I apply the patch below (from gdb-6.3-ia64-sigill-20051115.patch, a patch
> > for Fedora Core 5) I get:
> >
> > (gdb) r
> > Starting program: /home/nickrob/emacs/src/emacs -geometry 80x40+0+0
> > [Thread debugging using libthread_db enabled]
> > [New Thread -1208269120 (LWP 8067)]
> > [Switching to Thread -1208269120 (LWP 8067)]
> > Breakpoint 3 at 0x80f654b: file xterm.c, line 7833.
> >
> > Program terminated with signal SIGINT, Interrupt.
> > The program no longer exists.
> > (gdb)
>
> If you type Control-C, why did it kill emacs? Shouldn't it break in
> the debugger, and then let you resume?
Emacs uses Control-C to for keyboard-quit (at least in the terminal version) so
its .gdbinit has the line:
handle 2 noprint pass
> > Assuming this patch is appropriate, it's frustrating that patches by the
> > distributions don't get fed back (especially those from RedHat!).
>
> Yes, I know - but every distribution is guilty of this to some extent;
> it takes so much effort to get patches merged. We all do what we can.
It's in everyones interest that the versions don't diverge more than
necessary.
> For big patches I prefer to have the author submit them; I recently
> asked Jeff to resubmit one of the other patches from that SRPM, but
> haven't heard back from him yet. But this is a nice small one, so
> the usual copyright concerns don't matter.
>
> > 2005-11-15 Jeff Johnston <jjohnstn@redhat.com>
> >
> > * thread-db.c (thread_db_wait): Don't bother continuing if
> > the wait result indicates the program terminated with a signal.
>
> So, if you want to update the changelog to linux-thread-db.c, I think
> it'd be OK to apply this patch; it makes good sense.
OK, I've done this with Jeff's name on the ChangeLog. I've not added
(tiny change) as we do in Emacs as his name appears numerous times
previously and I assume his assignment hasn't been revoked.
--
Nick http://www.inet.net.nz/~nickrob
next parent reply other threads:[~2006-10-15 19:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200610142033.16596.ghost@cs.msu.su>
[not found] ` <20061014163911.GA16728@nevyn.them.org>
[not found] ` <17713.20182.174863.175193@kahikatea.snap.net.nz>
[not found] ` <20061014210523.GA23445@nevyn.them.org>
[not found] ` <17713.50027.927642.379449@kahikatea.snap.net.nz>
[not found] ` <20061015154128.GA14607@nevyn.them.org>
2006-10-15 19:47 ` Nick Roberts [this message]
2006-10-15 19:54 ` Daniel Jacobowitz
2006-10-15 20:28 ` Nick Roberts
2006-10-15 20:55 ` 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=17714.36770.10163.719995@kahikatea.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=drow@false.org \
--cc=gdb-patches@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