From: Joel Brobecker <brobecker@adacore.com>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: yao@codesourcery.com, gdb-patches@sourceware.org
Subject: Re: New ARI warning Wed Apr 27 01:54:55 UTC 2011
Date: Wed, 27 Apr 2011 16:59:00 -0000 [thread overview]
Message-ID: <20110427165853.GD2489@adacore.com> (raw)
In-Reply-To: <201104271642.p3RGgUW8025117@glazunov.sibelius.xs4all.nl>
> And suddenly even that "trivial" linux-ptrace.h diff is turning into a
> can of worms. Some people, including me, have stated that the stuff in
> common/ should *not* depend on any configure checks
Do you think that's attainable, though? There are a lot of basic types
which depend on configure... There might be some code such as gdb_select
which might be useful to gdbserver as well, one day. I'm sure we might
be able to implement some of the code without the use of configure, but
configure helps keep things cleaner.
> In this case there probably is a way out though. I don't think there
> are any systems out there that don't have <sys/wait.h>. So we could
> just get rid of gdb_wait.h altogether.
Is that because sys/wait is somehow mandated (by C90, perhaps?).
I'm wondering why we had it in the first place, it must have been
useful at some point...
--
Joel
prev parent reply other threads:[~2011-04-27 16:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-27 1:55 GDB Administrator
2011-04-27 3:16 ` Yao Qi
2011-04-27 14:53 ` Tom Tromey
2011-04-27 15:08 ` Joel Brobecker
2011-04-27 15:48 ` Yao Qi
2011-04-27 16:18 ` Joel Brobecker
2011-04-27 16:44 ` Mark Kettenis
2011-04-27 16:59 ` Joel Brobecker [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=20110427165853.GD2489@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
--cc=yao@codesourcery.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