From: Andreas Schwab <schwab@suse.de>
To: gdb@sources.redhat.com
Cc: Indraneel Sarkar <isarkar@novell.com>
Subject: Re: linux-nat.c:471: internal-error: unknown ptrace event 5
Date: Tue, 31 May 2005 14:10:00 -0000 [thread overview]
Message-ID: <je64wztrkw.fsf@sykes.suse.de> (raw)
In-Reply-To: <20050530170456.GB24005@nevyn.them.org> (Daniel Jacobowitz's message of "Mon, 30 May 2005 13:04:56 -0400")
Daniel Jacobowitz <drow@false.org> writes:
> You didn't say what version of GDB you're using. There've been some
> changes lately.
This was tested with gdb 9.3.
> It looks like you're using 'set follow child'. Is that right?
I don't know. Indraneel, do you?
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2005-05-31 14:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-30 15:14 Andreas Schwab
2005-05-30 17:05 ` Daniel Jacobowitz
2005-05-31 14:10 ` Andreas Schwab [this message]
2005-05-31 14:27 Indraneel Sarkar
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=je64wztrkw.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=gdb@sources.redhat.com \
--cc=isarkar@novell.com \
/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