From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18690 invoked by alias); 12 Jul 2012 08:44:47 -0000 Received: (qmail 18681 invoked by uid 22791); 12 Jul 2012 08:44:46 -0000 X-SWARE-Spam-Status: No, hits=1.0 required=5.0 tests=AWL,BAYES_00,CHARSET_FARAWAY_HEADER,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,KHOP_RCVD_TRUST,KHOP_THREADED,MIME_CHARSET_FARAWAY,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE,TW_BJ,TW_UQ X-Spam-Check-By: sourceware.org Received: from mail-ob0-f169.google.com (HELO mail-ob0-f169.google.com) (209.85.214.169) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 12 Jul 2012 08:44:33 +0000 Received: by obhx4 with SMTP id x4so3473061obh.0 for ; Thu, 12 Jul 2012 01:44:33 -0700 (PDT) MIME-Version: 1.0 Received: by 10.182.0.13 with SMTP id 13mr16488935oba.55.1342082672926; Thu, 12 Jul 2012 01:44:32 -0700 (PDT) Received: by 10.182.116.4 with HTTP; Thu, 12 Jul 2012 01:44:32 -0700 (PDT) In-Reply-To: <87mx36doam.fsf@fleche.redhat.com> References: <87mx36doam.fsf@fleche.redhat.com> Date: Thu, 12 Jul 2012 08:44:00 -0000 Message-ID: Subject: Re: [help] Linux kernel debug error: Cannot find DIE From: =?GB2312?B?1uzH7A==?= To: Tom Tromey Cc: gdb@sourceware.org Content-Type: text/plain; charset=GB2312 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2012-07/txt/msg00033.txt.bz2 I accept your suggestion and have a look at dwarf dump, and find some interestings: I just write very 2 simple case, and link them. There is warning like with the linked object: objdump: Warning: Bogus end-of-siblings marker detected at offset 7a in .debug_info section Does this warning will affect debugging that causes errors I met? Thanks zhuqing 2012/7/12 Tom Tromey : >>>>>> ">" =3D=3D =D6=EC=C7=EC writes: > >>> Dwarf Error: Cannot find DIE at 0x1634a7 referenced from DIE at >>> 0x17a459 [in module linux-kernel/linux-2.6.32.6/Build/vmlinux] > >>> I'm not sure this is caused by incorrect dwarf info generated by >>> open64 compiler or gdb issues, since the gcc build kernel binary is >>> able to debug. >>> I compared the dwarf info output of the two compiler with objdump >>> --dwarf=3Dinfo , open64's binary is about 1.95GB and gcc's binary is >>> 1.72GB, is that too large? > >>> Can someone give any clue on this to determine what is wrong here? > > There isn't an easy way to know what has gone wrong here. > > It could be incorrect DWARF -- meaning a compiler or (less likely) > linker bug. Or, it could be a gdb bug. > > I would debug it by using objdump or readelf to look at the DWARF around > the DIEs mentioned in the error message. > > The size of the DWARF is probably not an issue. > At least, this is not the error I would expect in that situation. > > Tom