[Bug dynamic-link/33224] New: gdb backtraces garbled with glibc trunk (since 8329939a37f483a16013dd8af8303cbcb86d92cb)

[sam at gentoo dot org]

https://sourceware.org/bugzilla/show_bug.cgi?id=33224

            Bug ID: 33224
           Summary: gdb backtraces garbled with glibc trunk (since
                    8329939a37f483a16013dd8af8303cbcb86d92cb)
           Product: glibc
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: dynamic-link
          Assignee: unassigned at sourceware dot org
          Reporter: sam at gentoo dot org
                CC: dilfridge at gentoo dot org, fweimer at redhat dot com
  Target Milestone: ---

Before 8329939a37f483a16013dd8af8303cbcb86d92cb, with:
```
int main() {
    int a = 1;
    __builtin_abort();
}
```
and `gcc a.c -o a -ggdb3`, I see a useful backtrace with `gdb ./a`:
```
Program received signal SIGABRT, Aborted.
0x00007ffff7e448bc in __pthread_kill_implementation () from
/usr/lib64/libc.so.6
(gdb) bt
#0  0x00007ffff7e448bc in __pthread_kill_implementation () from
/usr/lib64/libc.so.6
#1  0x00007ffff7dee246 in raise () from /usr/lib64/libc.so.6
#2  0x00007ffff7dd630b in abort () from /usr/lib64/libc.so.6
#3  0x0000555555555161 in main () at a.c:3
(gdb)
```

And at 8329939a37f483a16013dd8af8303cbcb86d92cb, I see completely garbled:
```
Program received signal SIGABRT, Aborted.
0x00007ffff7e448bc in ?? ()
(gdb) bt
#0  0x00007ffff7e448bc in ?? ()
#1  0x000000000000037f in ?? ()
#2  0xe67852f842bd8700 in ?? ()
#3  0x0000000000000006 in ?? ()
#4  0x00007fffffffdf60 in ?? ()
#5  0x0000000000000000 in ?? ()
```

Florian, what other information do you need?

-- 
You are receiving this mail because:
You are on the CC list for the bug.