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: "pmuldoon at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: 31 Mar 2010 14:47:18 -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 pmuldoon at redhat dot com 2010-03-31 14:47 -------
I'm trying to create a case (via gdb -i=mi2) where I can replicate the crash
when printing the child of value. print_string_repr (for to_string), and
print_children (for children) do call gdbpy_print_stack which in turn calls
PyErr_Print (). This prints the error and clears the exception. However if in
GDB an python exception is not caught (or cleared as above) it will be converted
to an internal GDB error() call which will terminate the current action GDB was
working on. There is one case in print_children where gdbpy_print_stack is not
called in a possible error condition (a child that is a string, but not a lazy
string). But trying to produce a testcase is turning out to be a painful
process. Do you have one handy that you could extract from your scenario?
--
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.