This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug python/11407] -stack-list-locals should catch python exceptions and return the error per variable
- From: "asmwarrior at gmail dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: 19 Jun 2010 12:34:49 -0000
- Subject: [Bug python/11407] -stack-list-locals should catch python exceptions and return the error per variable
- References: <20100320163108.11407.niko.sams@gmail.com>
- Reply-to: sourceware-bugzilla at sourceware dot org
------- Additional Comments From asmwarrior at gmail dot com 2010-06-19 12:34 -------
(In reply to comment #26)
> Created an attachment (id=4853)
--> (http://sourceware.org/bugzilla/attachment.cgi?id=4853&action=view)
> Output from patch
>
> I get different results, GDB behaves as expected (Does not crash, abandons
> pretty printing for that local, prints the rest of the local out in raw format,
> moves onto the next local)
>
> I built your inferior with
>
> g++ -g3 -std=c++0x repr2.cpp -o repr2
>
> I see over on the libstdc++ list there might be differences in your compiler.
> In any case, this looks like a mingw issue? Might need to split up this bug.
Hi, thanks for your test.
I found that if I set the breakpoint in the line 11, the same as you, then run
info locals command
gdb.exe( 20100613cvs ), works
gdb.exe( 20100618cvs with your patch), gdb crash.
But if I run "info locals" in very line of my code, none of gdb can survive.
(Both of the gdb.exe will get crashes on some lines)
As you said, GDB under Windows are not stable as on linux.
--
http://sourceware.org/bugzilla/show_bug.cgi?id=11407
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.