From: Tom Tromey <tromey@redhat.com>
To: Kevin Pouget <kevin.pouget@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: GDB Python API: stop/continue after breakpoint
Date: Wed, 20 Apr 2011 15:20:00 -0000 [thread overview]
Message-ID: <m3mxjl2bmm.fsf@fleche.redhat.com> (raw)
In-Reply-To: <AANLkTimdG3HKmwKCwaZW-Mz27_SFOBYq9=aHezkDYSWs@mail.gmail.com> (Kevin Pouget's message of "Fri, 11 Mar 2011 18:52:19 +0100")
>>>>> "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
next prev parent reply other threads:[~2011-04-20 15:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-11 16:09 Kevin Pouget
2011-03-11 16:25 ` Phil Muldoon
[not found] ` <AANLkTin_a87WgchmZnzi9_XX4DXh8q-r3P7EyyDAzTA4@mail.gmail.com>
2011-03-11 17:52 ` Kevin Pouget
2011-04-20 14:59 ` Kevin Pouget
2011-04-20 15:15 ` Phil Muldoon
2011-04-20 15:39 ` Tom Tromey
2011-04-21 13:01 ` Kevin Pouget
[not found] ` <BANLkTinwMfsxA24q-5ekbapVdM_OP6rOsQ@mail.gmail.com>
2011-04-21 14:32 ` Kevin Pouget
2011-04-20 15:20 ` Tom Tromey [this message]
2011-03-21 14:20 ` Kevin Pouget
2011-03-21 14:39 ` Phil Muldoon
2011-03-21 15:11 ` Kevin Pouget
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3mxjl2bmm.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb@sourceware.org \
--cc=kevin.pouget@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox