From: asmwarrior <asmwarrior@gmail.com>
To: xunxun <xunxun1982@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: gdb crash when I try to print a std::queue (Windows)
Date: Tue, 01 Nov 2011 01:46:00 -0000 [thread overview]
Message-ID: <4EAF4DEC.8020900@gmail.com> (raw)
In-Reply-To: <4EAE61BC.2060007@gmail.com>
On 2011-10-31 16:52, xunxun wrote:
> I think it's caused by
>
> CVSROOT: /cvs/src
> Module name: src
> Changes by: pmuldoon@sourceware.org 2011-10-27 09:14:27
>
> Modified files:
> gdb : ChangeLog
> gdb/python : py-breakpoint.c py-frame.c py-lazy-string.c
> py-symbol.c py-type.c
>
> Log message:
> 2011-10-27 Phil Muldoon<pmuldoon@redhat.com>
>
> * python/py-breakpoint.c (bppy_set_enabled): Use TRY_CATCH.
> (bppy_set_task): Ditto.
> (bppy_delete_breakpoint): Ditto.
> * python/py-symbol.c (gdbpy_lookup_symbol): Ditto.
> (gdbpy_lookup_global_symbol): Ditto.
> * python/py-lazy-string.c (stpy_convert_to_value): Ditto.
> * python/py-frame.c (frapy_is_valid): Ditto.
> (frame_info_to_frame_object): Ditto.
> * python/py-type.c (typy_lookup_type): Ditto.
> (typy_getitem): Ditto.
> (typy_has_key): Ditto.
> (typy_richcompare): Use TRY_CATCH. Do not return Py_NE on error.
>
> Patches:
> http://sourceware.org/cgi-bin/cvsweb.cgi/src/gdb/ChangeLog.diff?cvsroot=src&r1=1.13463&r2=1.13464
>
> http://sourceware.org/cgi-bin/cvsweb.cgi/src/gdb/python/py-breakpoint.c.diff?cvsroot=src&r1=1.27&r2=1.28
>
> http://sourceware.org/cgi-bin/cvsweb.cgi/src/gdb/python/py-frame.c.diff?cvsroot=src&r1=1.20&r2=1.21
>
> http://sourceware.org/cgi-bin/cvsweb.cgi/src/gdb/python/py-lazy-string.c.diff?cvsroot=src&r1=1.9&r2=1.10
>
> http://sourceware.org/cgi-bin/cvsweb.cgi/src/gdb/python/py-symbol.c.diff?cvsroot=src&r1=1.9&r2=1.10
>
> http://sourceware.org/cgi-bin/cvsweb.cgi/src/gdb/python/py-type.c.diff?cvsroot=src&r1=1.26&r2=1.27
>
>
>
> Before the commit, my gdb works well.
> But I have no time to find out the problem now.
>
> You can open a bug report.
>
>
>
I did test to check whether this commit introduce the crash problem,
then the result is YES.
see the details in:
http://sourceware.org/bugzilla/show_bug.cgi?id=13363#c5
I'm not quite familiar with gdb's source code, so I can't dig into it
further.
asmwarrior
ollydbg from codeblocks' forum
prev parent reply other threads:[~2011-11-01 1:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-30 13:30 asmwarrior
2011-10-30 18:17 ` asmwarrior
2011-10-31 8:50 ` 陳韋任
2011-10-31 8:52 ` asmwarrior
2011-10-31 9:42 ` xunxun
2011-11-01 1:46 ` asmwarrior [this message]
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=4EAF4DEC.8020900@gmail.com \
--to=asmwarrior@gmail.com \
--cc=gdb@sourceware.org \
--cc=xunxun1982@gmail.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).