On Wed, Mar 06, 2013 at 09:31:58AM -0500, Dave Anderson wrote:
Right, I did see another googled-reference to other
demangling/cloning
text symbols with extensions added to them, but I want to be very careful
not to throw the baby out with the bathwater.
So far it does seem safe to truncate all of the ".isra." symbols.
But then I looked at the ".constprop." symbols, for example:
crash> sym -q kzalloc
ffffffff81068060 (t) kzalloc.constprop.8
ffffffff8108c630 (t) kzalloc
ffffffff8134d1ee (t) kzalloc.constprop.2
ffffffff8134f1dd (t) kzalloc
ffffffff81358f5d (t) kzalloc
ffffffff8135ff7d (t) kzalloc
ffffffff813691fd (t) kzalloc
ffffffff813a53c0 (t) kzalloc
ffffffff813aca30 (t) kzalloc.constprop.3
...
If I stripped them, a "dis kzalloc" would then select the
first one it sees, which may not be the one of interest.
I think that it would probably be more helpful, or at least
safer, if they were left as is.
Agreed.
And then there are the ".part." symbols with no preceding
".isra.".
I haven't had the chance to study whether it's safe to strip
them, but upon first glance they look strippable.
But I want to do this carefully, perhaps also adding an invocation
command line to opt-out of any stripping at all.
OK, and the command line option sounds good too.