From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14155 invoked by alias); 23 Aug 2002 14:53:30 -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 14146 invoked from network); 23 Aug 2002 14:53:25 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sources.redhat.com with SMTP; 23 Aug 2002 14:53:25 -0000 Received: from int-mx2.corp.redhat.com (nat-pool-rdu.redhat.com [172.16.52.200] (may be forged)) by mx1.redhat.com (8.11.6/8.11.6) with ESMTP id g7NEcml02872 for ; Fri, 23 Aug 2002 10:38:48 -0400 Received: from potter.sfbay.redhat.com (potter.sfbay.redhat.com [172.16.27.15]) by int-mx2.corp.redhat.com (8.11.6/8.11.6) with ESMTP id g7NErMu23633; Fri, 23 Aug 2002 10:53:23 -0400 Received: from romulus.sfbay.redhat.com (IDENT:ua/DVDL4DxcXUb3zctwEtS92oI5JipZb@romulus.sfbay.redhat.com [172.16.27.251]) by potter.sfbay.redhat.com (8.11.6/8.11.6) with ESMTP id g7NErLe12714; Fri, 23 Aug 2002 07:53:21 -0700 Received: (from kev@localhost) by romulus.sfbay.redhat.com (8.11.6/8.11.6) id g7NErGw00627; Fri, 23 Aug 2002 07:53:16 -0700 Date: Fri, 23 Aug 2002 07:53:00 -0000 From: Kevin Buettner Message-Id: <1020823145316.ZM626@localhost.localdomain> In-Reply-To: Iztok "Problem debugging SOs" (Aug 23, 11:43am) References: <3D6603AC.4010607@s5.net> To: Iztok , gdb@sources.redhat.com Subject: Re: Problem debugging SOs MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2002-08/txt/msg00288.txt.bz2 On Aug 23, 11:43am, Iztok wrote: > Version 5.0 > Platform i386 Linux SuSE 7.0 > > I've got situation when shared object is loaded at runtime via the > dlopen function. GDB afterwards shows that the symbols from this shared > object are loaded but when trying to step into the function from this SO > nothing shows. > > Full debugging info is included in SO. > > How should I prepare the system to debug such SW ? I think you may be seeing a linker bug. Newer versions of gdb have a fix to work around the bug, but gdb-5.0 did not. For more information, see the threads associated with: http://sources.redhat.com/ml/gdb/2001-08/msg00221.html http://sources.redhat.com/ml/gdb-patches/2001-09/msg00003.html The simple fix is to update to a newer version of gdb. Either 5.2 or the current development sources should be fine. Kevin