From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32097 invoked by alias); 6 Mar 2003 19:42:20 -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 32090 invoked from network); 6 Mar 2003 19:42:19 -0000 Received: from unknown (HELO crack.them.org) (65.125.64.184) by 172.16.49.205 with SMTP; 6 Mar 2003 19:42:19 -0000 Received: from nevyn.them.org ([66.93.61.169] ident=mail) by crack.them.org with asmtp (Exim 3.12 #1 (Debian)) id 18r39H-0006HG-00; Thu, 06 Mar 2003 15:43:31 -0600 Received: from drow by nevyn.them.org with local (Exim 3.36 #1 (Debian)) id 18r1Fu-0008Rp-00; Thu, 06 Mar 2003 14:42:14 -0500 Date: Thu, 06 Mar 2003 19:42:00 -0000 From: Daniel Jacobowitz To: Bruce Ashfield Cc: gdb@sources.redhat.com Subject: Re: Symbol reference strangeness Message-ID: <20030306194213.GA24243@nevyn.them.org> Mail-Followup-To: Bruce Ashfield , gdb@sources.redhat.com References: <20030306193545.GA12991@seawaynetworks.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030306193545.GA12991@seawaynetworks.com> User-Agent: Mutt/1.5.1i X-SW-Source: 2003-03/txt/msg00119.txt.bz2 On Thu, Mar 06, 2003 at 02:35:45PM -0500, Bruce Ashfield wrote: > Hi all, > > I'm trying to determine what's happening with the symbols for > a project I'm working one. I've completed a move from a gcc-3.0 > to a gcc-3.2 based toolchain and I've also upgraded to gdb-5.3. > Ever since the switch over I've been seeing odd problems accessings > variables and other symbols in the generated images. > > I've gone over the compile flags and gdb options without much > success. I just finished trying the latest CVS snapshot of gdb > without any more luck. I'm hoping someone can slap me and point > me in the right direction. > > The most similar problems I've found to what I'm seeing on the > mailing list archives are: > > http://sources.redhat.com/ml/gdb/2002-12/msg00111.html > http://sources.redhat.com/ml/bug-gdb/2000-09/msg00012.html > > Which fairly closely describe what I've been seeing. So I'm No, that's a completely different problem (and fixed now, though I don't remember if the fix was in 5.3 or not). > now making sure that everything is being compiled with -gdwarf-2, > but that is only partially helping the problem, now I can see > some variables but not others, where before loading the same > symbol file multiple times would eventually get me at some > variables. > > The following capture will best describe what I'm seeing. > > (gdb) p /x debugLevel > $1 = 0xfffffff > (gdb) p sealKernelMaxConsecutiveCt_g > $3 = 3 > (gdb) p /x debugLevel > Cannot access memory at address 0x40249fc0 > > There are other ways of making this happen, but this is the > most simple. Very strange and I'm running out of things to try, > any suggestions would be greatly appreciated. > > Here are some point form technical details: > > compiler: 3.2.2 (powerpc cross compiler, host linux) > gdb: 5.3 and latest March CVS snapshot > compiling with: -gdwarf-2 in debug mode. I'd need a testcase to be able to help much. Is that the right or wrong address? What does p &debugLevel say? Where is it actually located? -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer