From: Doug Evans <dje@google.com>
To: gdb-patches@sourceware.org
Subject: Re: [RFA][python] Add program space support
Date: Wed, 07 Apr 2010 17:39:00 -0000 [thread overview]
Message-ID: <g2xe394668d1004071039h279352fbyeb4a2ee9e77dab1c@mail.gmail.com> (raw)
In-Reply-To: <20100407173222.A21C584397@ruffy.mtv.corp.google.com>
On Wed, Apr 7, 2010 at 10:32 AM, Doug Evans <dje@google.com> wrote:
> Hi.
>
> This patch adds basic support for program spaces to python.
>
> It also adds support for recording pretty-printers with a program space.
> This is useful, for example, when a class is entirely inlined and there
> isn't necessarily a .so to attach the pretty-printer to.
> Adding the pretty-printer to the gdb module isn't necessarily correct,
> different programs may have different implementations for the same class.
>
> Ok to check in?
Blech, forgot a NEWS entry.
2010-04-07 Doug Evans <dje@google.com>
* NEWS: Add entry for python program space support.
Index: NEWS
===================================================================
RCS file: /cvs/src/src/gdb/NEWS,v
retrieving revision 1.367
diff -u -p -r1.367 NEWS
--- NEWS 1 Apr 2010 14:11:22 -0000 1.367
+++ NEWS 7 Apr 2010 17:38:49 -0000
@@ -25,10 +25,13 @@
* Python scripting
-** The GDB Python API now has access to symbols, symbol tables, and
- frame's code blocks.
+** The GDB Python API now has access to program spaces, symbols,
+ symbol tables, and frame's code blocks.
-** New methods gdb.target_charset and gdb.target_wide_charset.
+** New methods gdb.target_charset, gdb.target_wide_charset,
+ gdb.progspaces, and gdb.current_progspace.
+
+** Pretty-printers are now also looked up in the current program space.
* Tracepoint actions were unified with breakpoint commands. In particular,
there are no longer differences in "info break" output for breakpoints and
next prev parent reply other threads:[~2010-04-07 17:39 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 [this message]
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
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=g2xe394668d1004071039h279352fbyeb4a2ee9e77dab1c@mail.gmail.com \
--to=dje@google.com \
--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