From: <m.m.kettenis@chello.nl>
To: Joel Brobecker <brobecker@gnat.com>
Cc: <gdb@sources.redhat.com>
Subject: Re: Re: ptrace(2) autoconf tests
Date: Wed, 11 Aug 2004 07:04:00 -0000 [thread overview]
Message-ID: <20040811070407.NKQI2608.amsfep12-int.chello.nl@localhost> (raw)
> van: Joel Brobecker <brobecker@gnat.com>
> datum: 2004/08/10 di PM 09:03:05 MEST
> I tested your patch below successfully on our 2 AIX systems (4.3.2 and
> 5.1). I also verified that configure found the right profile for ptrace
> and that infptrace.c compiled without any warning.
>
> About configure finding the right profile, there is one thing I am not
> sure about: The second parameter reported by configure is pid_t, while
> the include file seem to be saying that it's an int on 4.3.2 and a
> signed long on 5.1. There were no warnings during the build, so I
> assumed all was right.
Most systems have `typedef int pid_t', and the compiler doesn't really distinguish
between the two. Since I test for `pid_t' before `int', the detected signature is slightly
of. But this doesn't matter precisely for that reason. So nothing to worry.
Mark
reply other threads:[~2004-08-11 7:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20040811070407.NKQI2608.amsfep12-int.chello.nl@localhost \
--to=m.m.kettenis@chello.nl \
--cc=brobecker@gnat.com \
--cc=gdb@sources.redhat.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