From: Tom Tromey <tromey@redhat.com>
To: "Markus Grunwald" <markus.grunwald@gmx.de>
Cc: gdb@sourceware.org
Subject: Re: Big speed differences when setting breakpoints
Date: Mon, 09 Aug 2010 16:37:00 -0000 [thread overview]
Message-ID: <m3eie7kaje.fsf@fleche.redhat.com> (raw)
In-Reply-To: <e94cd1ab56c877bb47ca240fed407176.squirrel@grunwald.homedns.org> (Markus Grunwald's message of "Mon, 9 Aug 2010 08:29:46 +0200 (CEST)")
>>>>> "Markus" == Markus Grunwald <markus.grunwald@gmx.de> writes:
Markus> Can somebody explain these differences?
I am going to guess it is this:
http://sourceware.org/bugzilla/show_bug.cgi?id=8367
There have been several patches for this. I'm not sure what has
happened with them. For my part I am not sure how important the
symlink-with-different-base-name case is.
Tom
next prev parent reply other threads:[~2010-08-09 16:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-09 6:30 Markus Grunwald
2010-08-09 16:37 ` Tom Tromey [this message]
2010-08-10 8:25 ` Antwort: " Martin.Runge
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=m3eie7kaje.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb@sourceware.org \
--cc=markus.grunwald@gmx.de \
/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).