Hi,
#
https://fedorahosted.org/abrt/wiki/RFE
# RETRACE SERVER
# * recreating the bt means:
# o downloading the required debuginfo (if it's not cached)
# o replacing the ???? with proper function names
# o add a line numbers pointing to source file
Backtracing without debuginfo cannot provide the complete information now
(it misses inlined frames) and more features in development + planned also
could not be supported in the future. Preview of the latter is shown at:
Re: [PATCH] Debug info extensions to support optimized out parameters
http://gcc.gnu.org/ml/gcc-patches/2010-09/msg00385.html
Since Fedora 14 GDB supports .gdb_index (by Tom Tromey) and therefore now
debuginfofs has started to make sense. It made no sense before as GDB read
the whole .debug file first just to index it; this is no longer true and only
the small .gdb_index section is being read in.
http://fedoraproject.org/wiki/Features/DebuginfoFS
debuginfofs can provide the same debug info features as an upload of the whole
core file; the core upload is not feasible for security reasons.
Still it means retrace server cannot do the backtracing task, this has to be
done at the client side - for security reasons.
Which network protocol, its signing and what servers to use for DebuginfoFS
remains a question. Also .gdb_index has been developed with the goal of
improved on-disk performance; a network filesystem performance may need more
tuning. GDB could also use some file access library (neon as an example) for
the .debug files access avoiding the need of mounting any network filesystem.
Regards,
Jan