Bug 197928 - Make --auto-run-dsymutil=yes lazy
Summary: Make --auto-run-dsymutil=yes lazy
Status: ASSIGNED
Alias: None
Product: valgrind
Classification: Developer tools
Component: general (show other bugs)
Version: 3.5 SVN
Platform: Compiled Sources macOS
: NOR wishlist
Target Milestone: wanted3.6.0
Assignee: Julian Seward
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-06-26 08:01 UTC by Jesse Ruderman
Modified: 2009-08-20 02:56 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jesse Ruderman 2009-06-26 08:01:14 UTC
Would it be sensible to make --auto-run-dsymutil=yes only take the time to read symbols if a tool needs the symbols, e.g. to output an error?  That way, if there are no errors in a given library, the app would start up a little faster.
Comment 1 Nicholas Nethercote 2009-06-26 08:53:24 UTC
It would also make missing entries in the is_systemish_library check less likely to cause problems.
Comment 2 Nicholas Nethercote 2009-07-15 00:16:04 UTC
While we're at it, we could make all debug info reading lazy.  Instead of reading all debug symbols (and possibly runnying dsymutil, on Darwin) when code is loaded, attach a flag to the code indicating if its debug info has been loaded, and check that before doing any debug info lookups.  This might make a significant speed difference on really large programs.