RFE: please add possibility how to make glibc backtraces readable

[yarda]

Filling after discussion with jfilak.

There is e.g. the following glibc backtrace (catched from the logs or sent by user through e-mail, IRC):
/lib/libc.so.6[0x4606e143]
/lib/libc.so.6(__fortify_fail+0x45)[0x46109385]
/lib/libc.so.6[0x4610742a]
/lib/libc.so.6(__strcpy_chk+0x37)[0x46106777]
/sbin/ax25d[0x80498fe]
/lib/libc.so.6(__libc_start_main+0xf3)[0x46019b73]
/sbin/ax25d[0x804a6e1]
======= Memory map: ========
08048000-0804d000 r-xp 00000000 08:03 1985635 /usr/sbin/ax25d
0804d000-0804e000 r--p 00004000 08:03 1985635 /usr/sbin/ax25d
0804e000-0804f000 rw-p 00005000 08:03 1985635 /usr/sbin/ax25d
08320000-08341000 rw-p 00000000 00:00 0 [heap]
...

and if I know on which Fedora version and with which ax25-tools package this happened, it would be great to have simple way how to turn it into backtrace with debuginfo, i.e. to turn:
/sbin/ax25d[0x80498fe]
/sbin/ax25d[0x804a6e1]

into filenames and line numbers of source code.