From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28512 invoked by alias); 1 Apr 2010 12:40:58 -0000 Received: (qmail 28489 invoked by uid 48); 1 Apr 2010 12:40:58 -0000 Date: Thu, 01 Apr 2010 12:40:00 -0000 Message-ID: <20100401124058.28488.qmail@sourceware.org> From: "pmuldoon at redhat dot com" To: gdb-prs@sourceware.org In-Reply-To: <20100320163108.11407.niko.sams@gmail.com> References: <20100320163108.11407.niko.sams@gmail.com> Reply-To: sourceware-bugzilla@sourceware.org Subject: [Bug python/11407] -stack-list-locals should catch python exceptions and return the error per variable X-Bugzilla-Reason: CC Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-prs-owner@sourceware.org X-SW-Source: 2010-q2/txt/msg00003.txt.bz2 ------- Additional Comments From pmuldoon at redhat dot com 2010-04-01 12:40 ------- The problem I noted on my setup was common_val_print was raising a GDB error() due to a read at an invalid location. The function print_children() handles and clears its own Python exceptions, but this error() call was neither converted or handled. So this error was propagating as unhandled and the pretty printing process terminated in the command that called it. So commands like -stack-list-locals which print large amount of different variables were terminating prematurely. This draft patch in #12 fixes it for me, but I am not sure if it is correct. Does it work for you? I'd like Tom to have a look at this, hence the CC addition. -- 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.