From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28697 invoked by alias); 11 Jul 2012 20:40:54 -0000 Received: (qmail 28689 invoked by uid 22791); 11 Jul 2012 20:40:53 -0000 X-SWARE-Spam-Status: No, hits=-6.5 required=5.0 tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,RCVD_IN_DNSWL_HI,RCVD_IN_HOSTKARMA_W,SPF_HELO_PASS,TW_BJ,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 11 Jul 2012 20:40:35 +0000 Received: from int-mx10.intmail.prod.int.phx2.redhat.com (int-mx10.intmail.prod.int.phx2.redhat.com [10.5.11.23]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id q6BKeYgW005796 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 11 Jul 2012 16:40:34 -0400 Received: from barimba (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by int-mx10.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id q6BKeXGX018309 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Wed, 11 Jul 2012 16:40:33 -0400 From: Tom Tromey To: =?utf-8?B?5pyx5bqG?= Cc: gdb@sourceware.org Subject: Re: [help] Linux kernel debug error: Cannot find DIE References: Date: Wed, 11 Jul 2012 20:40:00 -0000 In-Reply-To: (=?utf-8?B?IuacseW6hiIncw==?= message of "Wed, 11 Jul 2012 17:32:05 +0800") Message-ID: <87mx36doam.fsf@fleche.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable 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/msg00027.txt.bz2 >>>>> ">" =3D=3D =E6=9C=B1=E5=BA=86 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