From: asmwarrior <asmwarrior@gmail.com>
To: gdb@sourceware.org
Cc: gcc@gcc.gnu.org
Subject: Re: About the "info locals" command of gdb and python pretty printer
Date: Mon, 21 Jun 2010 03:02:00 -0000 [thread overview]
Message-ID: <4C1ED5DC.2000201@gmail.com> (raw)
Hi, all. About the "info locals" and python pretty printer problem I
post here:
http://sourceware.org/ml/gdb/2010-06/msg00080.html
see the result here:
http://forums.codeblocks.org/index.php/topic,12747.msg86443.html#msg86443
I have solved this problem by hacking the GDB source code. You can see
the changed code here:
http://sourceware.org/bugzilla/show_bug.cgi?id=11407#c33
Asmwarrior (ollydbg from codeblocks' forum)
next reply other threads:[~2010-06-21 3:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-21 3:02 asmwarrior [this message]
-- strict thread matches above, loose matches on Subject: below --
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
[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
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=4C1ED5DC.2000201@gmail.com \
--to=asmwarrior@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=gdb@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).