Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Doug Evans <dje@google.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA][python] Add program space support
Date: Fri, 09 Apr 2010 15:34:00 -0000	[thread overview]
Message-ID: <g2ze394668d1004090834x870bda80l9dff6392da4df0d@mail.gmail.com> (raw)
In-Reply-To: <83634113i1.fsf@gnu.org>

On Fri, Apr 9, 2010 at 12:36 AM, Eli Zaretskii <eliz@gnu.org> wrote:
>> Date: Thu, 8 Apr 2010 15:24:32 -0700
>> From: Doug Evans <dje@google.com>
>> Cc: gdb-patches@sourceware.org
>>
>> >> +A program space, or ``progspace'', represents a symbolic view
>> >> +of an address space.
>> >
>> > An @xref here to where program spaces are described would be useful.
>>
>> There is no existing section describing program spaces and I wouldn't
>> know what to say beyond what I've already written.
>> Suggestions?  We *could* leave it as is for now.
>
> I didn't ask for you to explain again what program spaces are.  I
> asked for a cross-reference to the place where they are already
> explained.  Like this:
>
>  @xref{Inferiors and Programs, program spaces}, for more details
>  about program spaces.
>
> Thanks.
>

I guess I misunderstood.  I grepped all of gdb.texinfo, including that
particular xref, and saw nothing that would satisfy "where program
spaces are described" (or explained).
Plus the only reference to program spaces in that particular xref is
inside the description of a "maint" command - "[...], when debugging
GDB itself, ...".  It didn't seem kosher to refer users to sections
intended for GDB developers.  But no matter, learn something new every
day.
Thanks.


  reply	other threads:[~2010-04-09 15:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-07 17:32 Doug Evans
2010-04-07 17:39 ` Doug Evans
2010-04-07 17:54   ` Eli Zaretskii
2010-04-07 17:52 ` Eli Zaretskii
2010-04-08 22:24   ` Doug Evans
2010-04-09  7:37     ` Eli Zaretskii
2010-04-09 15:34       ` Doug Evans [this message]
2010-04-09 15:42         ` Pedro Alves
2010-04-14 22:47           ` Doug Evans

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=g2ze394668d1004090834x870bda80l9dff6392da4df0d@mail.gmail.com \
    --to=dje@google.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    /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