From: Michal Ludvig <mludvig@suse.cz>
To: Mark Kettenis <kettenis@chello.nl>
Cc: gdb <gdb@sources.redhat.com>
Subject: Corrupt data in ...
Date: Wed, 16 Jul 2003 15:12:00 -0000 [thread overview]
Message-ID: <3F156B42.90907@suse.cz> (raw)
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?
****
(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
next reply other threads:[~2003-07-16 15:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-16 15:12 Michal Ludvig [this message]
2003-07-16 16:05 ` Elena Zannoni
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3F156B42.90907@suse.cz \
--to=mludvig@suse.cz \
--cc=gdb@sources.redhat.com \
--cc=kettenis@chello.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).