From: Eli Zaretskii <eliz@gnu.org>
To: Pedro Alves <pedro@codesourcery.com>
Cc: drow@false.org, gdb-patches@sourceware.org
Subject: Re: [RFA 02/08] multi-process support: all targets manage inferior list
Date: Fri, 19 Sep 2008 15:28:00 -0000 [thread overview]
Message-ID: <u63osqhov.fsf@gnu.org> (raw)
In-Reply-To: <200809191459.10948.pedro@codesourcery.com>
> From: Pedro Alves <pedro@codesourcery.com>
> Date: Fri, 19 Sep 2008 14:59:10 +0100
> Cc: gdb-patches@sourceware.org
>
> > This looks otherwise OK (though I don't understand when you use
> > add_inferior vs add_inferior_silent).
>
> Hmmm, the initial thought was somewhat similar to the
> use of add_thread_silent in targets that didn't add the main thread
> to the list because they don't support multi-threads. (monitor,
> remote-sim). As in, don't emit a CLI note notification if
> the target pid was made up by GDB and thus should not be visible
> to the user, and emit if otherwise. This one seems to have been
> missed by that logic.
>
> But I agree that this sounds somewhat bogus. It should be the
> the target that should decide what to print... I'll need
> to do a few further adjustments for that to be possible
> though. These CLI notifications are off by default, so we
> can either get rid of add_inferior_silent, or make
> go32-nat.c also use it. Any preference? The attached does
> the latter.
I prefer the way of letting the target decide what to print. Can we
do that?
next prev parent reply other threads:[~2008-09-19 15:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-12 15:38 Pedro Alves
2008-09-18 22:52 ` Daniel Jacobowitz
2008-09-19 13:59 ` Pedro Alves
2008-09-19 14:08 ` Daniel Jacobowitz
2008-09-19 15:28 ` Eli Zaretskii [this message]
2008-09-22 15:43 ` Pedro Alves
2008-09-22 19:01 ` Eli Zaretskii
2008-09-22 19:02 ` Eli Zaretskii
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=u63osqhov.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=drow@false.org \
--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