On Tue, 04 Jun 2013 16:19:17 +0200, Martin Milata wrote:
I noticed that the MiniDebugInfo files in Fedora 19
(F18 too) have different ELF program header tables than the
corresponding binaries and separate debuginfo files:
MiniDebugInfo files are symbol files only, they are not intended for
On 06/05/2013 05:42 AM, Jan Kratochvil wrote:
On Tue, 04 Jun 2013 16:19:17 +0200, Martin Milata wrote:
My question is, is the table supposed to
look like this and libunwind needs to be patched, or is it a bug?
Segments are irrelevant for symbols.
There is a problem with objdump and
On Wed, Jun 05, 2013 at 14:42:44 +0200, Jan Kratochvil wrote:
Debugging purposes use linking view. This is also why /usr/lib/debug/**.debug
files do not have valid program headers and the same applies to MiniDebugInfo.
Thanks for the insight, Jan. I think I know how to fix the problem now.
On Wed, 05 Jun 2013 16:25:27 +0200, John Reiser wrote:
On 06/05/2013 05:42 AM, Jan Kratochvil wrote:
Segments are irrelevant for symbols.
There is a problem with objdump and MiniDebugInfo and gdb treating ElfXX_Phdr
records as don't care. The problem is that other parts of the debugging
Hello,
in the process of making ABRT aware of MiniDebugInfo[1] through the
libunwind library, I noticed that the MiniDebugInfo files in Fedora 19
(F18 too) have different ELF program header tables than the
corresponding binaries and separate debuginfo files:
$ eu-readelf -l /usr/bin/cat
