From: Joel Brobecker <brobecker@adacore.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Get rid of ATTACH_NO_WAIT
Date: Thu, 03 Jul 2008 16:48:00 -0000 [thread overview]
Message-ID: <20080703164744.GA19465@adacore.com> (raw)
In-Reply-To: <200806280025.40155.pedro@codesourcery.com>
Hi Pedro,
> 2008-06-28 Pedro Alves <pedro@codesourcery.com>
>
> * config/i386/nm-cygwin.h (ATTACH_NO_WAIT): Delete.
> * config/i386/nm-i386gnu.h (ATTACH_NO_WAIT): Delete.
>
> * target.h (struct target_ops): Add to_attach_no_wait member.
> (target_attach_no_wait): New.
> * target.c (update_current_target): Inherit to_attach_no_wait.
>
> * infcmd.c: Replace ATTACH_NO_WAIT compile time check by
> target_attach_no_wait runtime check.
>
> * gnu-nat.c (init_gnu_ops): Set to_attach_no_wait in gnu_ops.
> * win32-nat.c (init_win32_ops): Set to_attach_no_wait in
> win32_ops.
I will be glad to see this macro go, and overall the patch looks good
to me.
One thing I had to think about a little was whether this property
should be inherited or not (see target.c:update_current_target()).
I'm still not sure, but I think it should. Imagine that we had
a thread stratum on win32. Wouldn't you lose the attach_no_wait property
when this thread stratum got pushed on the target? Until we find a
target where the process and thread strata need a different setting,
I think it's safer for now to make it inheritable. What do you think?
--
Joel
next prev parent reply other threads:[~2008-07-03 16:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-28 0:15 Pedro Alves
2008-06-28 1:00 ` Pedro Alves
2008-07-03 16:48 ` Joel Brobecker [this message]
2008-07-03 17:13 ` Pedro Alves
2008-07-03 17:29 ` Joel Brobecker
2008-07-03 17:41 ` Pedro Alves
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=20080703164744.GA19465@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@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