From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24932 invoked by alias); 30 Jan 2012 18:24:14 -0000 Received: (qmail 24914 invoked by uid 22791); 30 Jan 2012 18:24:12 -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; Mon, 30 Jan 2012 18:24:00 +0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug python/12967] event.inferior_thread does not exist in all-stop/sync mode Date: Mon, 30 Jan 2012 18:24:00 -0000 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: palves at redhat 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 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: 2012-q1/txt/msg00131.txt.bz2 http://sourceware.org/bugzilla/show_bug.cgi?id=12967 Pedro Alves changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |palves at redhat dot com --- Comment #3 from Pedro Alves 2012-01-30 18:22:56 UTC --- > The docs say that inferior_thread should exist but be None > in all-stop. So, I think the bug is that it doesn't exist. Is there a reason things were done this way? It's awkward that the event doesn't say which thread was the event thread in all-stop mode. Can't we just change that? Stop events are still thread specific in all-stop. It's just that gdb suspends all the other non-event threads for you. E.g., with MI, in all-stop we have: *stopped,frame={addr="0x000000339e6ef451",func="clone",args=[],from="/lib64/libc.so.6"},thread-id="1",stopped-threads="all",core="3" Where thread-id is the moral equivalent of event.inferior_thread. stopped-threads="all" indicates that everything else was suspended along. In non-stop, we have: *stopped,frame={addr="0x000000339e6ef451",func="clone",args=[],from="/lib64/libc.so.6"},thread-id="1",stopped-threads=["1"],core="3" Even if the ThreadEvent doesn't learn about something like the stopped-threads set, it'd still be useful to at least make it report the event thread. -- 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.