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: 18 Jun 2010 08:21:35 -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-18 08:21 -------
Sorry for interrupt here again.
I personally think that this "debug info about a variable is initialized or not"
should exist in the function which exception handling is enabled. For example:
Quote
try
{
A a;
CallXXX();
B b;
CAllYYY();
}
At this time, the variables info (initialed or not) should be recorded in
somewhere. Because exceptions can happens every where, the exception handler
need to call the "destruction of the already initialized objects".
I guess there is a table to record this debug info.. So, my question is: Can GDB
read this information?
thanks.
--
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.