From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-39080-listarch-gdb=sources.redhat.com@sourceware.org>
Received: (qmail 17957 invoked by alias); 20 Apr 2011 15:39:49 -0000
Received: (qmail 17944 invoked by uid 22791); 20 Apr 2011 15:39:47 -0000
X-SWARE-Spam-Status: No, hits=-6.9 required=5.0	tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,SPF_HELO_PASS,T_RP_MATCHES_RCVD
X-Spam-Check-By: sourceware.org
Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28)    by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 20 Apr 2011 15:39:34 +0000
Received: from int-mx09.intmail.prod.int.phx2.redhat.com (int-mx09.intmail.prod.int.phx2.redhat.com [10.5.11.22])	by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id p3KFdW8H007623	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK);	Wed, 20 Apr 2011 11:39:32 -0400
Received: from ns3.rdu.redhat.com (ns3.rdu.redhat.com [10.11.255.199])	by int-mx09.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id p3KFdVYc015489;	Wed, 20 Apr 2011 11:39:31 -0400
Received: from opsy.redhat.com (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1])	by ns3.rdu.redhat.com (8.13.8/8.13.8) with ESMTP id p3KFdVWD003413;	Wed, 20 Apr 2011 11:39:31 -0400
Received: by opsy.redhat.com (Postfix, from userid 500)	id D00DF378091; Wed, 20 Apr 2011 09:39:30 -0600 (MDT)
From: Tom Tromey <tromey@redhat.com>
To: Kevin Pouget <kevin.pouget@gmail.com>
Cc: pmuldoon@redhat.com, gdb@sourceware.org
Subject: Re: GDB Python API: stop/continue after breakpoint
References: <AANLkTim7t_4C8n=PJ8ZgCT=HsU7vdHMXyGWOe6QVCHfE@mail.gmail.com>	<m3wrk58w0d.fsf@redhat.com>	<AANLkTin_a87WgchmZnzi9_XX4DXh8q-r3P7EyyDAzTA4@mail.gmail.com>	<AANLkTimdG3HKmwKCwaZW-Mz27_SFOBYq9=aHezkDYSWs@mail.gmail.com>	<BANLkTikdOZEf4_85TA=Aj8+zBmPGX8-sBw@mail.gmail.com>
Date: Wed, 20 Apr 2011 15:39:00 -0000
In-Reply-To: <BANLkTikdOZEf4_85TA=Aj8+zBmPGX8-sBw@mail.gmail.com> (Kevin	Pouget's message of "Wed, 20 Apr 2011 10:58:46 -0400")
Message-ID: <m3ipu92aq5.fsf@fleche.redhat.com>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Mailing-List: contact gdb-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb.sourceware.org>
List-Subscribe: <mailto:gdb-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb/>
List-Post: <mailto:gdb@sourceware.org>
List-Help: <mailto:gdb-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-owner@sourceware.org
X-SW-Source: 2011-04/txt/msg00114.txt.bz2

>>>>> "Kevin" == Kevin Pouget <kevin.pouget@gmail.com> writes:

Kevin> * in MyBreakpoint.stop(), I can say continue/stop the inferior, but I
Kevin> can't run "finish" (or "next" or what ever, I guess), because the
Kevin> inferior is still considered as running:

I think it would be pretty difficult to get this to work.

Kevin> * in event.stop.connect() that's possible, but I can't
Kevin> `gdb.execute("continue")' the execution because I would miss any
Kevin> "non-python" reasons to stop (ie, a user-breakpoint, a signal ...)

I think you should be able to examine the stop event object to see what
caused the event.  If the event is a gdb.BreakpointEvent, and if
event.breakpoint is your breakpoint, then do what you want.

Tom