From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9351 invoked by alias); 21 Feb 2011 15:24:48 -0000 Received: (qmail 9340 invoked by uid 22791); 21 Feb 2011 15:24:47 -0000 X-SWARE-Spam-Status: No, hits=-1.3 required=5.0 tests=AWL,BAYES_00,MSGID_MULTIPLE_AT X-Spam-Check-By: sourceware.org Received: from mailhost.u-strasbg.fr (HELO mailhost.u-strasbg.fr) (130.79.200.157) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 21 Feb 2011 15:24:41 +0000 Received: from md2.u-strasbg.fr (md2.u-strasbg.fr [IPv6:2001:660:2402::187]) by mailhost.u-strasbg.fr (8.14.3/jtpda-5.5pre1) with ESMTP id p1LFOZmm046732 ; Mon, 21 Feb 2011 16:24:35 +0100 (CET) (envelope-from pierre.muller@ics-cnrs.unistra.fr) Received: from mailserver.u-strasbg.fr (ms1.u-strasbg.fr [130.79.204.10]) by md2.u-strasbg.fr (8.14.4/jtpda-5.5pre1) with ESMTP id p1LFOY2n056764 ; Mon, 21 Feb 2011 16:24:35 +0100 (CET) (envelope-from pierre.muller@ics-cnrs.unistra.fr) Received: from E6510Muller (gw-ics.u-strasbg.fr [130.79.210.225]) (user=mullerp mech=LOGIN) by mailserver.u-strasbg.fr (8.14.4/jtpda-5.5pre1) with ESMTP id p1LFOYMj083323 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) ; Mon, 21 Feb 2011 16:24:34 +0100 (CET) (envelope-from pierre.muller@ics-cnrs.unistra.fr) From: "Pierre Muller" To: "'Pedro Alves'" Cc: References: <4D5C71F6.80208@vmware.com> <201102211150.04538.pedro@codesourcery.com> In-Reply-To: <201102211150.04538.pedro@codesourcery.com> Subject: RE: [RFA] Fix for testsuite errors with gdbserver (remote) Date: Mon, 21 Feb 2011 15:47:00 -0000 Message-ID: <00b601cbd1db$7173d250$545b76f0$@muller@ics-cnrs.unistra.fr> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2011-02/txt/msg00550.txt.bz2 > That all said, it looks like the python api doesn't define > exactly what can be done on an ExitedEvent, and even if > we address the gdbarch issue, if it's intended that the > python user code can do whatever, we're likely to see python/gdb > calls there that try to do something that calls has_stack_frames, > and that will internal error too. On that ground, I do think > we should put in Pierre's patch, as I'm not seeing what > possible harm can it do, and that gets things working again. > But I'll note that if the handler is allowed to assume the > whole api is available at this point, and that the current > global state can be used as if in the top-level, we'll > probably see other similar cases triggering. Should I take this as an approval of my patch? Or do you want me to wait some more in case someone else has a better idea of how to fix this issue? Pierre