This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: gdb crash when I try to print a std::queue (Windows)
- From: asmwarrior <asmwarrior at gmail dot com>
- To: xunxun <xunxun1982 at gmail dot com>
- Cc: gdb at sourceware dot org
- Date: Tue, 01 Nov 2011 09:39:56 +0800
- Subject: Re: gdb crash when I try to print a std::queue (Windows)
- References: <4EAD4FE7.9050102@gmail.com> <4EAD56D4.5020709@gmail.com> <20111031084035.GA40553@cs.nctu.edu.tw> <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