From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: RFC: next/finish/etc -vs- exceptions
Date: Wed, 01 Dec 2010 13:42:00 -0000 [thread overview]
Message-ID: <20101201134228.GA26690@host0.dyn.jankratochvil.net> (raw)
In-Reply-To: <m3oc96pnz5.fsf@fleche.redhat.com>
On Tue, 30 Nov 2010 21:15:26 +0100, Tom Tromey wrote:
> Jan> But maybe just all the breakpoints specific for that thread
> Jan> (clear_thread_inferior_resources) should be deleted which would
> Jan> also solve this problem?
Found out now I already filed it as:
delete thread-specific breakpoint on the thread exit
http://sourceware.org/bugzilla/show_bug.cgi?id=11568
> Calling delete_longjmp_breakpoint from clear_thread_inferior_resources
> worked for me. I'm not 100% confident that this is the correct fix though.
It is also not much a serious problem.
Thanks,
Jan
next prev parent reply other threads:[~2010-12-01 13:42 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-07 1:37 Tom Tromey
2010-11-24 17:53 ` Joel Brobecker
2010-11-24 18:24 ` Tom Tromey
2010-11-25 7:59 ` Jan Kratochvil
2010-11-27 17:25 ` Doug Evans
2010-11-28 8:29 ` Joel Brobecker
2010-11-30 16:43 ` Tom Tromey
2010-11-30 17:02 ` Jan Kratochvil
2010-11-30 17:15 ` Phil Muldoon
2010-11-30 20:15 ` Tom Tromey
2010-12-01 13:42 ` Jan Kratochvil [this message]
2010-12-01 21:40 ` Tom Tromey
2010-11-30 18:23 ` Tom Tromey
2010-11-30 18:55 ` Tom Tromey
2010-12-02 15:32 ` Tom Tromey
2010-12-09 16:37 ` Tom Tromey
2010-12-10 4:52 ` Jan Kratochvil
2010-12-10 20:07 ` Tom Tromey
2010-12-11 5:27 ` Jan Kratochvil
2010-12-15 21:18 ` Tom Tromey
[not found] <m37hzzzgk7.fsf@fleche.redhat.com>
[not found] ` <20090610161204.GB25703@adacore.com>
[not found] ` <m3hbyoghit.fsf@fleche.redhat.com>
[not found] ` <200906101806.31977.pedro@codesourcery.com>
[not found] ` <20090610171328.GA32661@caradoc.them.org>
2010-11-25 4:54 ` 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=20101201134228.GA26690@host0.dyn.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb-patches@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).