From: Simon Marchi <simon.marchi@polymtl.ca>
To: gdb@sourceware.org
Cc: tromey@redhat.com
Subject: Multi-threaded dwarf parsing
Date: Wed, 24 Feb 2016 02:45:00 -0000 [thread overview]
Message-ID: <2c38d5c574de28faa9fc94fe4ed17d45@simark.ca> (raw)
Hi all,
When debugging large programs, simply loading the binary in gdb can take
a significant amount of time. I was wondering if the dwarf parsing
(building partial and/or full symtabs, I suppose) could be a good
candidate for parallelization. I did some quick checks to determine
that, at least when reading from my SSD drive, the operation is not
IO-bound. Also, according to my limited understanding of the Dwarf
format, it seems like the compilation units DIEs are entities that could
be processed independently. These two facts, if we assume they are
true, suggest that there is a good potential for performance gain here.
I couldn't find anything on the mailing list about that, please point
out any discussion I might have missed.
I found (and it was a very good surprise) this branch by Tom Tromey:
https://github.com/tromey/gdb/tree/threaded-dwarf-reader
According to his description (from https://github.com/tromey/gdb/wiki):
"I think it doesn't help any real-world case". I'd like to ask you
directly, Tom: now that you debug Firefox (i.e. a quite large program)
daily with gdb, are you still of the same opinion? Of course, I'm also
interested in what others have to say about that. Is it something that
would have value, you think?
Also, since not so long ago, LLDB does it. Apparently, it "can
drastically incrase the speed of loading debug info" (sic). If it's
good for LLDB, I don't see why it wouldn't be good for GDB.
Ref: http://blog.llvm.org/2015/10/llvm-weekly-95-oct-26th-2015.html
So, in a word, are there any gotchas or good reasons not do take this
path?
Simon
next reply other threads:[~2016-02-24 2:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-24 2:45 Simon Marchi [this message]
2016-02-24 11:06 ` Pedro Alves
2016-02-24 15:30 ` Tom Tromey
2016-02-24 16:43 ` Simon Marchi
2016-02-24 19:50 ` Tom Tromey
2016-02-24 20:25 ` Jan Kratochvil
2016-02-24 20:37 ` Simon Marchi
2016-02-24 21:28 ` Jan Kratochvil
2016-02-24 21:10 ` Pedro Alves
2016-02-24 21:22 ` Jan Kratochvil
2016-02-25 3:31 ` Tom Tromey
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=2c38d5c574de28faa9fc94fe4ed17d45@simark.ca \
--to=simon.marchi@polymtl.ca \
--cc=gdb@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