From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: archer@sourceware.org
Subject: [next-over-throw2] exception_resume_breakpoint comments
Date: Thu, 29 Apr 2010 16:47:00 -0000 [thread overview]
Message-ID: <20100429164722.GA5666@host0.dyn.jankratochvil.net> (raw)
Hi,
on this branch I have just seen suspicious:
static void
insert_exception_resume_breakpoint (struct thread_info *tp,
struct block *b,
struct frame_info *frame,
struct symbol *sym)
- does not use TP at all.
Then clear_thread_inferior_resources now clears tp->step_resume_breakpoint.
To make tp->exception_resume_breakpoint on par with existing
tp->step_resume_breakpoint IMO clear_thread_inferior_resources should clear
even tp->exception_resume_breakpoint.
Unrelated bug is that both these breakpoints should be set as thread-specific.
Another unrelated bug is that on a thread exit thread-specific breakpoints are
not deleted (one may ask if they should be deleted, though). Fix of these two
bugs would simplify clear_thread_inferior_resources to remove even the
tp->step_resume_breakpoint handling from there.
To get back in the scope of this specific patch I would just implement:
# To make tp->exception_resume_breakpoint on par with existing
# tp->step_resume_breakpoint IMO clear_thread_inferior_resources should clear
# even tp->exception_resume_breakpoint.
Thanks,
Jan
next reply other threads:[~2010-04-29 16:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-29 16:47 Jan Kratochvil [this message]
2010-04-30 16:08 ` Tom Tromey
2010-05-04 19:46 ` Jan Kratochvil
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=20100429164722.GA5666@host0.dyn.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=archer@sourceware.org \
--cc=tromey@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).