This is the mail archive of the gdb@sourceware.org mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Question about GDB event mechanism

From: Tom Tromey <tromey at redhat dot com>
To: Siva Chandra <sivachandra at google dot com>
Cc: gdb at sourceware dot org
Date: Wed, 09 May 2012 14:34:19 -0600
Subject: Re: Question about GDB event mechanism
References: <CAGyQ6gzaFNz9JN-HAsXKfhnXxLf9a-TFX7RoKbhMqDzSW9L-SQ@mail.gmail.com>

>>>>> "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

References:
- Question about GDB event mechanism
  - From: Siva Chandra

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]