From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13607 invoked by alias); 16 Jul 2003 16:05:03 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 13596 invoked from network); 16 Jul 2003 16:05:02 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sources.redhat.com with SMTP; 16 Jul 2003 16:05:02 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.11.6/8.11.6) with ESMTP id h6GG51H26067 for ; Wed, 16 Jul 2003 12:05:01 -0400 Received: from pobox.corp.redhat.com (pobox.corp.redhat.com [172.16.52.156]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id h6GG50I32421 for ; Wed, 16 Jul 2003 12:05:00 -0400 Received: from localhost.redhat.com (romulus-int.sfbay.redhat.com [172.16.27.46]) by pobox.corp.redhat.com (8.11.6/8.11.6) with ESMTP id h6GG4xP08501 for ; Wed, 16 Jul 2003 12:05:00 -0400 Received: by localhost.redhat.com (Postfix, from userid 469) id D6C282CA3B; Wed, 16 Jul 2003 12:12:13 -0400 (EDT) From: Elena Zannoni MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16149.31069.451772.550121@localhost.redhat.com> Date: Wed, 16 Jul 2003 16:05:00 -0000 To: Michal Ludvig Cc: Mark Kettenis , gdb Subject: Re: Corrupt data in ... In-Reply-To: <3F156B42.90907@suse.cz> References: <3F156B42.90907@suse.cz> X-SW-Source: 2003-07/txt/msg00187.txt.bz2 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