From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32628 invoked by alias); 27 Aug 2002 15:04:10 -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 32613 invoked from network); 27 Aug 2002 15:04:06 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sources.redhat.com with SMTP; 27 Aug 2002 15:04:06 -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 g7REn7l11506 for ; Tue, 27 Aug 2002 10:49:08 -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 g7RF44u21514; Tue, 27 Aug 2002 11:04:04 -0400 Received: from romulus.sfbay.redhat.com (IDENT:P4SVEaFbcoAmA5/Ft12ti3lizTXp94n5@romulus.sfbay.redhat.com [172.16.27.251]) by potter.sfbay.redhat.com (8.11.6/8.11.6) with ESMTP id g7RF42e26611; Tue, 27 Aug 2002 08:04:02 -0700 Received: (from kev@localhost) by romulus.sfbay.redhat.com (8.11.6/8.11.6) id g7RF41303421; Tue, 27 Aug 2002 08:04:01 -0700 Date: Tue, 27 Aug 2002 08:04:00 -0000 From: Kevin Buettner Message-Id: <1020827150400.ZM3420@localhost.localdomain> In-Reply-To: Iztok Kobal "Re: Problem debugging SOs" (Aug 27, 7:40am) References: <3D6603AC.4010607@s5.net> <1020823145316.ZM626@localhost.localdomain> <3D69F82C.9020109@sysen.si> <1020826154249.ZM30715@localhost.localdomain> <3D6B10E6.90400@sysen.si> To: Iztok Kobal Subject: Re: Problem debugging SOs Cc: gdb@sources.redhat.com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2002-08/txt/msg00360.txt.bz2 On Aug 27, 7:40am, Iztok Kobal wrote: > code to be debugged was compiled with the gcc-2.95.2 -g3 > > No more problems seem to be directly related to the SO debugging > New problem with gdb-5.2.1 is that the (gdb step) behaves as > if it was the linked single .c) projects. Are you certain that the files containing the functions that you're trying to step into were compiled with -g ? The only time I see the behavior you describe is when I've forgotten to use -g. Kevin