From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28910 invoked by alias); 6 Mar 2003 19:35:43 -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 28903 invoked from network); 6 Mar 2003 19:35:42 -0000 Received: from unknown (HELO apollo.seawaynetworks.com) (216.209.86.50) by 172.16.49.205 with SMTP; 6 Mar 2003 19:35:42 -0000 Received: from camelot-019.seawaynetworks.com (camelot-019 [10.10.1.19]) by apollo.seawaynetworks.com (8.12.8/8.12.8) with ESMTP id h26JZf5g018005 for ; Thu, 6 Mar 2003 14:35:41 -0500 (EST) Received: (from ashfield@localhost) by camelot-019.seawaynetworks.com (8.11.6/8.11.6) id h26JZjj13069 for gdb@sources.redhat.com; Thu, 6 Mar 2003 14:35:45 -0500 X-Authentication-Warning: camelot-019.seawaynetworks.com: ashfield set sender to ashfield@seawaynetworks.com using -f Date: Thu, 06 Mar 2003 19:35:00 -0000 From: Bruce Ashfield To: gdb@sources.redhat.com Subject: Symbol reference strangeness Message-ID: <20030306193545.GA12991@seawaynetworks.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.25i X-SW-Source: 2003-03/txt/msg00118.txt.bz2 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 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. Cheers, Bruce Ashfield -- Bruce Ashfield | "Thou shalt not follow the NULL pointer, for | chaos and madness await thee at its end." | - unknown