From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22675 invoked by alias); 26 Aug 2002 09:43:31 -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 22668 invoked from network); 26 Aug 2002 09:43:29 -0000 Received: from unknown (HELO felix.sypra.si) (212.118.92.52) by sources.redhat.com with SMTP; 26 Aug 2002 09:43:29 -0000 Received: from sysen.si ([10.1.10.15]) by felix.sypra.si (8.9.3/8.9.3) with ESMTP id MAA24164 for ; Mon, 26 Aug 2002 12:42:24 +0200 Message-ID: <3D69F82C.9020109@sysen.si> Date: Mon, 26 Aug 2002 02:43:00 -0000 From: Iztok Kobal Organization: SYSEN d.d. User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0rc2) Gecko/20020513 Netscape/7.0b1 X-Accept-Language: sl, en-us MIME-Version: 1.0 CC: gdb@sources.redhat.com Subject: Re: Problem debugging SOs References: <3D6603AC.4010607@s5.net> <1020823145316.ZM626@localhost.localdomain> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2002-08/txt/msg00320.txt.bz2 Thanks Kevin. I am responding a little bit late since I was out of the office for the week-end. I have taken a look to the references you wrote and, yes, that is exactly the thing that is happening. I have been also peep-ing into the gdb's source code and the code-in-the-matter is already included into the latest gdb-5.2.1 version which I am trying to use also. I have been trying with the 5.1.x and lately 5.2.1 (downloaded from ftp.gnu, configured without any options and compiled on my machine with the gcc 2.95.x) with the something better and something worse success: 1. SO's symbol resolving is behaving slightly better. But !!! I have to step into the function from the SO with the and go through the whole SO resolving stuff to come into the function body - instead of using simply Step Into command. And I have also changed my SO dlopen-ing from RTLD_LAZY to the RTLD_NOW | RTLD_GLOBAL so I could have presumed that the resolving stuff would not be executed anymore... with no obvious difference. 2. generally does not work for me anymore - it usually behaves as it was Step Over command really - I again have to execute and after that to come into the called function body. Pretty annoying, isnt't it ? Or setting the bunch of the breakpoints all over the code so the whole debugging process takes me a lot more than too much time. I was starting to think that the problem was related to the gcc stub info generation and I am going to try a gcc-3.0.4 instead of a 2.95.x which came with my SuSE distro. Please spare me the time and tell me if it would not work either ! Iztok Kevin Buettner wrote: > 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 > > > >