From: Matthias Klose <doko@ubuntu.com>
To: tromey@redhat.com
Cc: asmwarrior <asmwarrior@gmail.com>,
gdb@sourceware.org, libstdc++@gcc.gnu.org
Subject: Re: About the "info locals" command of gdb and python pretty printer
Date: Fri, 02 Jul 2010 10:57:00 -0000 [thread overview]
Message-ID: <4C2DC60B.3010003@ubuntu.com> (raw)
In-Reply-To: <m36319bijq.fsf@fleche.redhat.com>
On 23.06.2010 22:28, Tom Tromey wrote:
>>>>>> ">" == Asm gmail<asmwarrior@gmail.com> writes:
>
>>> 1, It seems the current SVN std python script didn't works any
>>> more.
> [...]
>>> All the response from gdb just gives the same as print /r XXXX.
>
> I think this is pretty unlikely to have been caused by the recent patch.
> Instead it sounds like the printers aren't being read in.
>
> What version of Python are you using?
>
>>> Today, I have build gdb-cvs-20100623 , and try to make gdb crash on
>>> printing some uninitialized stl containers by pretty printers. But it
>>> stands through all the cases, so, it seems the gdb-cvs-20100623 is
>>> quite stable than the gdb-cvs-20100619. I'm not sure what has
>>> changed. It seems it more stable now.
>
> As far as I know, nothing in this area has changed.
my mistake. I did check in two chunks left over from testing. Reverted these on
the trunk. The 4.5 branch was not affected. Sorry.
Matthias
next prev parent reply other threads:[~2010-07-02 10:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-20 9:13 asmwarrior
2010-06-21 7:48 ` André Pönitz
2010-06-21 20:08 ` Tom Tromey
2010-06-22 0:29 ` asmwarrior
2010-06-22 2:18 ` Tom Tromey
2010-06-23 12:30 ` asmwarrior
[not found] ` <4C21FCDC.5050503__12891.7291098789$1277296251$gmane$org@gmail.com>
2010-06-23 20:28 ` Tom Tromey
2010-06-24 1:16 ` asmwarrior
2010-07-02 10:57 ` Matthias Klose [this message]
2010-06-21 3:02 asmwarrior
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=4C2DC60B.3010003@ubuntu.com \
--to=doko@ubuntu.com \
--cc=asmwarrior@gmail.com \
--cc=gdb@sourceware.org \
--cc=libstdc++@gcc.gnu.org \
--cc=tromey@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).