From: Bruce Ashfield <Bruce.Ashfield@seawaynetworks.com>
To: gdb@sources.redhat.com
Subject: Symbol reference strangeness
Date: Thu, 06 Mar 2003 19:35:00 -0000 [thread overview]
Message-ID: <20030306193545.GA12991@seawaynetworks.com> (raw)
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
next reply other threads:[~2003-03-06 19:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-06 19:35 Bruce Ashfield [this message]
2003-03-06 19:42 ` Daniel Jacobowitz
2003-03-06 19:57 ` Bruce Ashfield
2003-03-06 20:06 ` Daniel Jacobowitz
2003-03-11 17:54 ` Bruce Ashfield
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030306193545.GA12991@seawaynetworks.com \
--to=bruce.ashfield@seawaynetworks.com \
--cc=gdb@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox