Corrupt data in ...

[Elena Zannoni]

Michal Ludvig writes:
 > Hi Mark,
 > on AMD64/Linux I'm getting "During symbol reading...Corrupt data in 
 > /lib64/libm.so.6:.eh_frame; align 4 workaround apparently succeeded..." 
 > message. What does it mean and where to look for the problem?
 > 

That's a problem with the linker that generates corrupt debug info.
Richard Henderson put in a workaround to continue reading the FDE's
and CIE's even though they might be misaligned. What you are seeing is
a complaint that gets issued when this occurs.

Look for a recent message by rth to the gdb-patches list, from last week.

elena


 > ****
 > (top-gdb) b main
 > Breakpoint 3 at 0x4390b7: file gdb.c, line 30.
 > (top-gdb) r
 > Starting program: /usr/src/packages/BUILD/gdb-6.0/gdb/gdb
 > During symbol reading...Corrupt data in /lib64/libm.so.6:.eh_frame; 
 > align 4 workaround apparently succeeded...
 > During symbol reading...Corrupt data in /lib64/libc.so.6:.eh_frame; 
 > align 4 workaround apparently succeeded...
 > 
 > Breakpoint 3, main (argc=1, argv=0x7fbffff6d8) at gdb.c:30
 > 30        memset (&args, 0, sizeof args);
 > (top-gdb)
 > ****
 > 
 > Thanks!
 > 
 > Michal Ludvig
 > -- 
 > * SuSE CR, s.r.o     * mludvig@suse.cz
 > * (+420) 296.545.373 * http://www.suse.cz