Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Doug Evans <dje@google.com>
To: Gary Benson <gbenson@redhat.com>, Pedro Alves <palves@redhat.com>
Cc: gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Don't mention "Unix" in native target name.
Date: Thu, 13 Mar 2014 00:13:00 -0000	[thread overview]
Message-ID: <CADPb22S5nkRENk-aWAPx_HU7JgBXhfffUD8Vi9=kA_eC91zTSQ@mail.gmail.com> (raw)
In-Reply-To: <20140312131607.GA5531@blade.nx>

On Wed, Mar 12, 2014 at 6:16 AM, Gary Benson <gbenson@redhat.com> wrote:
> Pedro Alves wrote:
>> I wonder whether anyone would miss this badly?  The difference would be:
>>
>>   (gdb) maint print target-stack
>>   The current target stack is:
>>    - multi-thread (multi-threaded child process.)
>> -  - child (Unix child process)
>> +  - child (Child process)
>>    - exec (Local exec file)
>>    - None (None)
>>
>>  (gdb) help target child
>> - Unix child process (started by the "run" command).
>> + Child process (started by the "run" command).
>>
>> I find it unnecessary (and really slightly a lie) on GNU/Linux.
>>
>> It's also odd that e.g., the Windows port says "Unix" in reaction to
>> "target child" (it was already that way before Windows used
>> inf-child.c).
>>
>> How about we just say the same mostly everywhere?
>
> I'm all for this.
>
>> In the same vein, I'd also rename Solaris/procfs.c's "target procfs"
>> to "target child".
>
> Ditto.

+1


  reply	other threads:[~2014-03-13  0:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-12 12:38 Pedro Alves
2014-03-12 13:16 ` Gary Benson
2014-03-13  0:13   ` Doug Evans [this message]
2014-03-13 12:30     ` Pedro Alves
2014-03-12 13:37 ` Rename Solaris's target to "target child" like most other ports Pedro Alves
2014-03-13  7:39   ` Joel Brobecker
2014-03-13 12:32     ` 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='CADPb22S5nkRENk-aWAPx_HU7JgBXhfffUD8Vi9=kA_eC91zTSQ@mail.gmail.com' \
    --to=dje@google.com \
    --cc=gbenson@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@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