[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gdb
Subject:    Re: Bad performance in updating JIT debug symbols
From:       Fredrik Tolf <fredrik () dolda2000 ! com>
Date:       2016-09-17 18:43:25
Message-ID: alpine.DEB.2.11.1609172042100.2866 () shack ! dolda2000 ! com
[Download RAW message or body]

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.

[prev in list] [next in list] [prev in thread] [next in thread]