From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8804 invoked by alias); 6 Mar 2003 19:57:14 -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 8796 invoked from network); 6 Mar 2003 19:57:13 -0000 Received: from unknown (HELO apollo.seawaynetworks.com) (216.209.86.50) by 172.16.49.205 with SMTP; 6 Mar 2003 19:57:13 -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 h26JvA5g018764; Thu, 6 Mar 2003 14:57:10 -0500 (EST) Received: (from ashfield@localhost) by camelot-019.seawaynetworks.com (8.11.6/8.11.6) id h26JvET22090; Thu, 6 Mar 2003 14:57:14 -0500 X-Authentication-Warning: camelot-019.seawaynetworks.com: ashfield set sender to ashfield@seawaynetworks.com using -f Date: Thu, 06 Mar 2003 19:57:00 -0000 From: Bruce Ashfield To: gdb@sources.redhat.com, drow@mvista.com Subject: Re: Symbol reference strangeness Message-ID: <20030306195714.GA13131@seawaynetworks.com> References: <20030306193545.GA12991@seawaynetworks.com> <20030306194213.GA24243@nevyn.them.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030306194213.GA24243@nevyn.them.org> User-Agent: Mutt/1.3.25i X-SW-Source: 2003-03/txt/msg00120.txt.bz2 Hi, Shoot. I was hoping they were similar, hard to tell with those search results. Here is the additional information, I'll see if I can put together a testcase, but I'm suspicious that part of the problem is due to the sizes of our images. > 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? ---------- > powerpc-eabi-gdb /local/ashfield/SW5000/swy/images/ccp_dbg_nopt_nin_v.img GNU gdb 5.3 Copyright 2002 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "--host=i686-pc-linux-gnu --target=powerpc-eabi"... (gdb) p /x debugLevel $1 = 0xfffffff (gdb) p &debugLevel $2 = (Uint32 *) 0x778e4 (gdb) p sealKernelMaxConsecutiveCt_g $3 = 3 (gdb) p &sealKernelMaxConsecutiveCt_g $4 = (Uint32 *) 0x77848 (gdb) p /x debugLevel Cannot access memory at address 0x40249fc0 (gdb) p &debugLevel $5 = (Uint32 *) 0x40249fc0 -------- Very strange indeed. The address is getting corrupted and I'm at a loss to explain it. This problem didn't pop up with the gcc-3.0 and older gdb's, which isn't that much of a surpise, with the amount of diffs. The two variables that I'm accessing are compiled in different parts of the system, placed in different static libraries and linked into the final image. Once I've crossed the boundary from the .a that is holding debugLevel to the one with sealKernelMaxConsecutiveCt_g, there seems to be no way back. Let me know what else I can provide (I'll work on that testcase). Cheers, Bruce Ashfield In message: Re: Symbol reference strangeness on March 06 Daniel Jacobowitz wrote: > On Thu, Mar 06, 2003 at 02:35:45PM -0500, Bruce Ashfield wrote: > > Hi all, > > > > 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). > > -- > Daniel Jacobowitz > MontaVista Software Debian GNU/Linux Developer -- Bruce Ashfield | "Thou shalt not follow the NULL pointer, for | chaos and madness await thee at its end." | - unknown