From: Fredrik Tolf <fredrik@dolda2000.com>
To: Duane Ellis <duane@duaneellis.com>, gdb@sourceware.org
Subject: Re: Bad performance in updating JIT debug symbols
Date: Sat, 17 Sep 2016 18:43:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.11.1609172042100.2866@shack.dolda2000.com> (raw)
In-Reply-To: <F4715250-E24B-452E-9232-2469AB2EB2B2@duaneellis.com>
On Sat, 17 Sep 2016, Duane Ellis wrote:
> So why not make a wrapper on the symbol lookup function
>
> Search the main list if that fails to find try the next list of syms.
>
> After you under 100 inserts resort your additional list. And start a new list
I can imagine a lot of ways to optimize the current code, but the main
point was that GDB seems to be stuck in a path of the code that is not
really intended to be used other than when GDB is "confused", so the main
question is why that happens.
next prev parent reply other threads:[~2016-09-17 18:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-17 17:25 Fredrik Tolf
[not found] ` <F4715250-E24B-452E-9232-2469AB2EB2B2@duaneellis.com>
2016-09-17 18:43 ` Fredrik Tolf [this message]
2016-09-18 13:55 ` Yichao Yu
2016-09-19 15:10 ` Pedro Alves
2016-09-19 15:45 ` Yichao Yu
2016-09-20 2:20 ` Fredrik Tolf
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=alpine.DEB.2.11.1609172042100.2866@shack.dolda2000.com \
--to=fredrik@dolda2000.com \
--cc=duane@duaneellis.com \
--cc=gdb@sourceware.org \
/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