From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-40878-listarch-gdb=sources.redhat.com@sourceware.org>
Received: (qmail 31262 invoked by alias); 9 May 2012 20:34:39 -0000
Received: (qmail 31218 invoked by uid 22791); 9 May 2012 20:34:36 -0000
X-SWARE-Spam-Status: No, hits=-6.4 required=5.0	tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,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, 09 May 2012 20:34:21 +0000
Received: from int-mx10.intmail.prod.int.phx2.redhat.com (int-mx10.intmail.prod.int.phx2.redhat.com [10.5.11.23])	by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id q49KYKNx004439	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK);	Wed, 9 May 2012 16:34:20 -0400
Received: from barimba (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1])	by int-mx10.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id q49KYJXN009810	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO);	Wed, 9 May 2012 16:34:19 -0400
From: Tom Tromey <tromey@redhat.com>
To: Siva Chandra <sivachandra@google.com>
Cc: gdb@sourceware.org
Subject: Re: Question about GDB event mechanism
References: <CAGyQ6gzaFNz9JN-HAsXKfhnXxLf9a-TFX7RoKbhMqDzSW9L-SQ@mail.gmail.com>
Date: Wed, 09 May 2012 20:34:00 -0000
In-Reply-To: <CAGyQ6gzaFNz9JN-HAsXKfhnXxLf9a-TFX7RoKbhMqDzSW9L-SQ@mail.gmail.com>	(Siva Chandra's message of "Fri, 4 May 2012 00:12:04 +0530")
Message-ID: <87wr4lqek4.fsf@fleche.redhat.com>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.95 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
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: 2012-05/txt/msg00034.txt.bz2

>>>>> "Siva" == Siva Chandra <sivachandra@google.com> writes:

Siva> I am trying to understand the event mechanism when used in Python
Siva> code.

I'm sorry about the delay in my reply.
I was away.

Siva> I would expect "Hello, Breakpoint!" to be printed, but it is not being
Siva> printed as 'run' is executed via 'execute_command_to_string' which
Siva> will reset gdb_stdout only after 'execute_command' returns.  The
Siva> notification of the breakpoint event is sent via 'normal_stop' before
Siva> 'execute_command' returns.
[...]
Siva> Hence, should the current behavior be documented or fixed?

I think it is a bug.
In my view, the events should trigger for all stops, regardless of where
the command originated.

Tom