From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12732 invoked by alias); 24 Jun 2011 13:44:47 -0000 Received: (qmail 12704 invoked by uid 22791); 24 Jun 2011 13:44:45 -0000 X-SWARE-Spam-Status: No, hits=-2.8 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from localhost (HELO sourceware.org) (127.0.0.1) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 24 Jun 2011 13:44:32 +0000 From: "pedro at codesourcery dot com" To: gdb-prs@sourceware.org Subject: [Bug python/12930] GDB state during gdb.Breakpoint::stop callback is unclear X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: python X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: pedro at codesourcery dot com X-Bugzilla-Status: NEW X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: CC Message-ID: In-Reply-To: References: X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 Date: Fri, 24 Jun 2011 13:44:00 -0000 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: 2011-q2/txt/msg00481.txt.bz2 http://sourceware.org/bugzilla/show_bug.cgi?id=12930 Pedro Alves changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pedro at codesourcery dot | |com --- Comment #1 from Pedro Alves 2011-06-24 13:44:29 UTC --- "(running)" is correct here. When the "stop" callback returns false, there should be no running->stopped->running transition visible, exactly because your callback claimed it didn't want the thread to "stop" (and nothing else wanted it to stop). >>From the user/frontend's perspective, the thread is still running at this point. [The user should get an error if he tries to resume a thread that is currently "running", irrespective of the thread happening to be presently suspended due to having hit some internal event (e.g., internal single-step event stops while handling a "s" command that requires several single-steps).] Internal events are hidden from the user. That's why we have running/stopped independent of executing/not-executing in the thread's internal state. -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.