From: Jim Blandy <jimb@cygnus.com>
To: Mark Kettenis <kettenis@wins.uva.nl>
Cc: gdb-patches@cygnus.com, bug-gdb@cugnus.com
Subject: Re: Patch for Hurd gdb bug
Date: Mon, 26 Apr 1999 08:22:00 -0000 [thread overview]
Message-ID: <nppv4rpftg.fsf@zwingli.cygnus.com> (raw)
In-Reply-To: <199904251843.UAA00144@delius.kettenis.nl>
Mark Kettenis <kettenis@wins.uva.nl> writes:
> Here is a patch for a nasty bug that makes it impossible to attach to
> a crashed program. (The Hurd has this nice feature that it is possible
> to suspend programs that crashed. You can then attach the debugger to
> investigate why the program crashed. Very useful, especially since we
> do not have core dumps yet.)
Thanks for the fix! It should be in future snapshots (although it
will not be in 4.18.1).
1999-04-26 Jim Blandy <jimb@zwingli.cygnus.com>
1999-04-25 Mark Kettenis <kettenis@gnu.org>
* gnu-nat.c (gnu_attach): Call target_terminal_init before calling
inf_set_traced, since that function calls code that might try to
restore the terminal settings.
prev parent reply other threads:[~1999-04-26 8:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-04-25 12:40 Mark Kettenis
1999-04-25 11:42 ` Mark Kettenis
1999-04-26 8:22 ` Jim Blandy [this message]
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=nppv4rpftg.fsf@zwingli.cygnus.com \
--to=jimb@cygnus.com \
--cc=bug-gdb@cugnus.com \
--cc=gdb-patches@cygnus.com \
--cc=kettenis@wins.uva.nl \
/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