From: Joel Brobecker <brobecker@adacore.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: Vladimir Prus <vladimir@codesourcery.com>, gdb-patches@sourceware.org
Subject: Re: [1/3] broken -thread-info output in non-stop mode, suppress_stop_observer
Date: Wed, 18 Mar 2009 15:16:00 -0000 [thread overview]
Message-ID: <20090318150006.GD18396@adacore.com> (raw)
In-Reply-To: <200903171724.54512.pedro@codesourcery.com>
> Hmmm, I do wonder if we could rewrite "finish" to not rely on
> bpstat_find_breakpoint after normal_stop, but to instead add a new
> BPSTAT_WHAT_FINISH and handle it from within handle_inferior_event's
> internal breakpoint handling switch (where we handle
> BPSTAT_WHAT_STEP_RESUME, etc.). Since that runs before normal_stop,
> we wouldn't have to suppress the normal_stop observer.
Seems like worth a try indeed. It might simplify how the "finish"
command is implemented too.
--
Joel
next prev parent reply other threads:[~2009-03-18 15:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-17 6:23 Pedro Alves
2009-03-17 7:29 ` Vladimir Prus
2009-03-17 17:27 ` Pedro Alves
2009-03-18 15:16 ` Joel Brobecker [this message]
2009-03-22 21:24 ` Pedro Alves
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=20090318150006.GD18396@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.com \
--cc=vladimir@codesourcery.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