On Tue, Mar 05, 2013 at 08:58:58AM -0500, Dave Anderson wrote:
 I'm thinking that it's probably best that the
".isra..." should be stripped
 during the symbol storage phase so that the crash sources have no idea 
 that they ever existed with those names.  The module symbol storage code has
 always done a similar thing in strip_module_symbol_end(). 
 
 And the gdb module must be doing the same kind of thing, because you can pass
 the "stripped" symbol name to gdb, and it knows what it is:
 
  crash> dis get_sigframe
  symbol not found: get_sigframe
  possible alternatives:
    ffffffff81058090 (t) get_sigframe.isra.1
  crash>
 
  crash> disass get_sigframe
  Dump of assembler code for function get_sigframe:
     0xffffffff81058090 <+0>:     nopl   0x0(%rax,%rax,1)
     0xffffffff81058095 <+5>:     push   %rbp
     0xffffffff81058096 <+6>:     mov    %rsp,%rbp
     0xffffffff81058099 <+9>:     push   %rbx
     0xffffffff8105809a <+10>:    mov    %rdx,%rbx
     0xffffffff8105809d <+13>:    sub    $0x18,%rsp
  ...  
 
 Anyway, I'll take care of that.   
Great, thanks.
One more thing - it looks like there are other "cloning symbols" in addition
to .isra... you can find the list here:
http://gcc.gnu.org/viewcvs/trunk/libiberty/testsuite/demangle-expected?re...
(find comment saying "Clone suffix tests"). Maybe we should handle them as
well?