From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23678 invoked by alias); 11 Jan 2010 08:46:11 -0000 Received: (qmail 23659 invoked by uid 22791); 11 Jan 2010 08:46:10 -0000 X-SWARE-Spam-Status: No, hits=-2.4 required=5.0 tests=AWL,BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Received: from plmler1.mail.eds.com (HELO plmler1.mail.eds.com) (199.228.142.71) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 11 Jan 2010 08:46:06 +0000 Received: from plmlir5.mail.eds.com (plmlir5-2.mail.eds.com [199.228.142.135]) by plmler1.mail.eds.com (8.14.2/8.13.8) with ESMTP id o0B8k4FC022994 for ; Mon, 11 Jan 2010 02:46:04 -0600 Received: from plmlir5.mail.eds.com (localhost [127.0.0.1]) by plmlir5.mail.eds.com (8.14.2/8.12.10) with ESMTP id o0B8k13S015813 for ; Mon, 11 Jan 2010 02:46:02 -0600 Received: from usplmvpfe001.ent.rt.verigy.net ([192.100.40.4]) by plmlir5.mail.eds.com (8.14.2/8.12.10) with ESMTP id o0B8k1W3015780 for ; Mon, 11 Jan 2010 02:46:01 -0600 X-EDSINT-Source-Ip: 192.100.40.4 Received: from usplmvpbe001.ent.rt.verigy.net ([10.16.58.34]) by usplmvpfe001.ent.rt.verigy.net with Microsoft SMTPSVC(6.0.3790.3959); Mon, 11 Jan 2010 02:46:01 -0600 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: pc 0x25c9b0 in read in psymtab, but not in symtab Date: Mon, 11 Jan 2010 08:46:00 -0000 Message-ID: <58596C4646708B4BB990C448399733300190922A@usplmvpbe001.ent.rt.verigy.net> In-Reply-To: <58596C4646708B4BB990C4483997333001908F74@usplmvpbe001.ent.rt.verigy.net> From: "Elmenthaler, Jens" To: 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: 2010-01/txt/msg00104.txt.bz2 > I'm running out of time, right now. But a guess a program that dlopen's a= > shared library could be good candidate. I will give it a try as soon as = < > possible. I can no longer reproduce the problem: the reason can be one of the followi= ng thing: - I rebooted my linux machine - completely recompiled my software I guess the trigger was the second, so I think the problem is sitting betwe= en keyboard and chair. Jens. -----Original Message----- From: gdb-owner@sourceware.org [mailto:gdb-owner@sourceware.org] On Behalf = Of Elmenthaler, Jens Sent: Freitag, 8. Januar 2010 17:32 To: Tristan Gingold; Chris Sutcliffe Cc: gdb@sourceware.org Subject: RE: pc 0x25c9b0 in read in psymtab, but not in symtab > Sadly, without reproducer I won't get far. In my case, the addresses complained about resolves to the following locati= ons (RedHat Enterprise Linux 5.3): maint translate-address 0x25c9b0 -> _dl_debug_state + 0 in section .text of /lib/ld-linux.so.2 maint translate-address 0x25c9b1 -> _dl_debug_state + 1 in section .text of /lib/ld-linux.so.2 This makes perfectly sense, as I see the messages while (or shortly after) = the gdb is stopped because of shared library event. I'm running out of time, right now. But a guess a program that dlopen's a s= hared library could be good candidate. I will give it a try as soon as poss= ible. Jens. -----Original Message----- From: gdb-owner@sourceware.org [mailto:gdb-owner@sourceware.org] On Behalf = Of Tristan Gingold Sent: Freitag, 8. Januar 2010 16:56 To: Chris Sutcliffe Cc: gdb@sourceware.org Subject: Re: pc 0x25c9b0 in read in psymtab, but not in symtab On Jan 8, 2010, at 4:42 PM, Chris Sutcliffe wrote: >> yes this bug I encounter some time ago, too. It is related to DLL files >> not having any debugging information but are shown in backtrace. Here it >> warns once about psymtab !=3D symtab and code in gdb fix it afterwards. = IMHO >> this warning is simply pretty bogus here, or the DLL loader should >> generate for pe-coff the symtab, too. >=20 > Hopefully this is helpful. Not that much. This doesn't sound coherent to me because if there is no de= bugging information both the psymtab and the symtab should be empty. > If there is anything else I can do to help track down the bug, please > let me know. It would be nice to have a reproducer. It doesn't need to be small and I t= hink sources are not needed to investigate this issue. Sadly, without reproducer I won't get far. Tristan.