From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: [cancel] Re: [patch] Fix deadlock on looped solib list
Date: Fri, 09 Apr 2010 15:42:00 -0000 [thread overview]
Message-ID: <20100409154245.GB8218@host0.dyn.jankratochvil.net> (raw)
In-Reply-To: <m3k4siubtw.fsf@fleche.redhat.com>
On Thu, 08 Apr 2010 00:39:23 +0200, Tom Tromey wrote:
> >>>>> "Jan" == Jan Kratochvil <jan.kratochvil@redhat.com> writes:
> Jan> I have just found now Daniel J.'s (not checked in):
> Jan> [RFC] Detect loops in the solib chain
> Jan> http://sourceware.org/ml/gdb-patches/2008-07/msg00347.html
>
> Bummer that this didn't go in.
therefore cancelling this thread in favor of the revived:
Re: [RFC] Detect loops in the solib chain
http://sourceware.org/ml/gdb-patches/2010-04/msg00245.html
Thanks,
Jan
prev parent reply other threads:[~2010-04-09 15:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-03 9:23 Jan Kratochvil
2010-04-07 19:47 ` Tom Tromey
2010-04-07 22:24 ` Jan Kratochvil
2010-04-07 22:39 ` Tom Tromey
2010-04-09 15:42 ` Jan Kratochvil [this message]
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=20100409154245.GB8218@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