From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: Doug Evans <dje@google.com>, Eli Zaretskii <eliz@gnu.org>
Subject: Re: [RFA][python] Add program space support
Date: Fri, 09 Apr 2010 15:42:00 -0000 [thread overview]
Message-ID: <201004091642.16651.pedro@codesourcery.com> (raw)
In-Reply-To: <g2ze394668d1004090834x870bda80l9dff6392da4df0d@mail.gmail.com>
On Friday 09 April 2010 16:34:11, Doug Evans wrote:
> 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).
Because they're not visible to the user in any way. It's all exposed
through inferiors.
--
Pedro Alves
next prev parent reply other threads:[~2010-04-09 15:42 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
2010-04-09 15:42 ` Pedro Alves [this message]
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=201004091642.16651.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=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