From: Andreas Schwab <schwab@suse.de>
To: Chad Harrington <harrington.chad@gmail.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: typo in gdb/gdb_ptrace.c
Date: Thu, 23 Jun 2005 09:22:00 -0000 [thread overview]
Message-ID: <jehdfp8m31.fsf@sykes.suse.de> (raw)
In-Reply-To: <bc65d53d05062222395836675c@mail.gmail.com> (Chad Harrington's message of "Wed, 22 Jun 2005 23:39:13 -0600")
Chad Harrington <harrington.chad@gmail.com> writes:
> Below is the diff patch for my fix. It is not critical, but it sure
> looks like a mistake to me. This was in gdb-6.3, as you can see. The
> preprocessor is told to define PT_ATTACH if PTRACE_DETACH is defined.
> I think it should only define PT_ATTACH if PTRACE_ATTACH is defined,
> but I think they'd both be defined if one or the other is already
> defined anyway... It merely appears to be a typo. :-)
There is another typo in the previous line. I've checked this in as
obvious.
2005-06-23 Andreas Schwab <schwab@suse.de>
* gdb_ptrace.h: Fix typos when checking for PT_ATTACH. Reported
by Chad Harrington <harrington.chad@gmail.com>.
--- gdb/gdb_ptrace.h.~1.3.~ 2004-11-22 13:57:48.000000000 +0100
+++ gdb/gdb_ptrace.h 2005-06-23 11:02:57.000000000 +0200
@@ -92,8 +92,8 @@
/* Not all systems support attaching and detaching. */
-#ifndef PT_ATTCH
-# ifdef PTRACE_DETACH
+#ifndef PT_ATTACH
+# ifdef PTRACE_ATTACH
# define PT_ATTACH PTRACE_ATTACH
# endif
#endif
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-06-23 9:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-23 5:39 Chad Harrington
2005-06-23 9:22 ` Andreas Schwab [this message]
2005-06-23 20:11 ` Mark Kettenis
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=jehdfp8m31.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=gdb-patches@sources.redhat.com \
--cc=harrington.chad@gmail.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