Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [v8] multi-executable support
Date: Wed, 14 Oct 2009 03:03:00 -0000	[thread overview]
Message-ID: <20091014030310.GR5272@adacore.com> (raw)
In-Reply-To: <200910131440.48021.pedro@codesourcery.com>

Pedro,

I finally had some time to read through the lengthy threads for this.
I'll confess that I didn't look at the code much because I'm starved
for time and I trust you implicitly. I just looked at the discussions
and the resulting UI that you now propose.

I like the UI, and the concepts behind it. I did a careful reading of
the introductory comment in progspace.h and it's great that you took
the time to provide such a detailed introduction.  I'm planning on
extending it to discuss the VxWorks case :-).

Just a few nits: There is at least one location where I noticed some
"#if 0"'ed code, and I just told one of the contributors that we'd
like to avoid this sort of thing.  Can it be removed, or should we
really be keeping that piece of commented out code.  We usually use
FIXMEs instead.

In the documentation:

    +(@value{GDBP}) clone-inferior
    +Added inferior 2.
    +1 inferiors added.

This is really nit-picking, but when adding 1 inferior, should we have
a special message that does not say "inferiors" (plural). I usually
don't care much about this sort of detail, but for some reason, it
seems to matter to me in this case.

I am very impressed with the level of functionality that this patch
is bringing to GDB, and I look forward to seeing it part of GDB.

Just a personal request: If you commit the patch before Saturday,
could you just give me a heads up. I just want to make sure that
I can get a checkout of the sources before you apply your patch.
I think that the patch is going to break our VxWorks port, and I think
that fixing it will require a bit of thoughts and time.  So if I can
do a resync of the AdaCore sources up to before your patch, that'll
give me a little more time.

Cheers,
-- 
Joel


  reply	other threads:[~2009-10-14  3:03 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-05 15:59 [v6] " Pedro Alves
2009-10-05 21:57 ` Eli Zaretskii
2009-10-06 12:14   ` Pedro Alves
2009-10-06 14:29     ` Eli Zaretskii
2009-10-12  1:26     ` [v7] " Pedro Alves
2009-10-12 19:09       ` Eli Zaretskii
2009-10-13 13:40         ` [v8] " Pedro Alves
2009-10-14  3:03           ` Joel Brobecker [this message]
2009-10-14 15:16             ` Pedro Alves
2009-10-14 15:28               ` Joel Brobecker
2009-10-14 16:25               ` Tom Tromey
2009-10-14 16:48                 ` Pedro Alves
2009-10-14 17:41                   ` Tom Tromey
2009-10-06  5:13 ` [v6] " Sérgio Durigan Júnior
2009-10-06 13:55   ` 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=20091014030310.GR5272@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