This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: GDB Python API: stop/continue after breakpoint
- From: Tom Tromey <tromey at redhat dot com>
- To: Kevin Pouget <kevin dot pouget at gmail dot com>
- Cc: gdb at sourceware dot org
- Date: Wed, 20 Apr 2011 09:20:01 -0600
- 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>
>>>>> "Kevin" == Kevin Pouget <kevin.pouget@gmail.com> writes:
Sorry, I didn't notice this until your follow-up.
Kevin> thanks for your answer, the patch seems to feature what I was
Kevin> looking for. I'm a bit surprised that the stop/continue decision
Kevin> can't be done in this breakpoint_stop handler, but I guess that
Kevin> was too complicated ?
We intentionally made event handlers not return values.
My recollection is that this was done both due to simplicity and also
out of the desire to make it clear that event handlers ought to be
logically separate. Once handlers affect other handlers, the coding
gets more complicated, and it seems better to associate such actions
more directly with their causes.
Tom