From: Ian Thompson <iant@palmchip.com>
To: linux-mips@oss.sgi.com
Subject: Debug format problem with -ggdb flag
Date: Wed, 02 May 2001 16:31:03 -0700 [thread overview]
Message-ID: <3AF098B7.F111B230@palmchip.com> (raw)
Hi,
I'm running into problems with the debug information that is generated
by the kernel compilation process. Basically, I'm seeing that
multiple function symbols have the same begin address in the .mdebug
section. For example -- the init_arch and r3081_wait functions in my
build have differnet addresses as far as compilation is concerned, and
code executes correctly. When I look into the .mdebug section, I see
that the begin, end, stab, and external records are all correct for
the r3081_wait function, but that the begin record for the init_arch
function is the same as that for the the r3081_wait function! This in
turn seems to be causing the stab and external records to be incorrect,
causing symbolic problems in my debugger.
I've traced the problem down, and it seems to be a side-effect of
partial linking. When the linker links multiple .o files into another
.o file (which is later used as input to another ld command), the
debug records inside the .mdebug section are getting corrupted. Has
anyone run into this problem before? Any suggestions of other flags
I can pass into the partial link that may help? I'm using the mipsel
rpm of binutils 2.9.5-3. Or, are there any alternatives to
partial linking that don't involve a lot of makefile manipulation?
I've tried using the -gcoff option to remove the stab records, but that
option does not allow the 2.4 kernel to compile under egcs 2.91.66.
Any ideas? Thanks,
-ian
--
----------------------------------------
Ian Thompson tel: 408.952.2023
Firmware Engineer fax: 408.570.0910
Palmchip Corporation www.palmchip.com
next reply other threads:[~2001-05-02 23:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-02 23:31 Ian Thompson [this message]
2001-05-05 17:53 ` Debug format problem with -ggdb flag Ralf Baechle
2001-05-08 7:36 ` binutils 2.8.1 problems Michael Shmulevich
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=3AF098B7.F111B230@palmchip.com \
--to=iant@palmchip.com \
--cc=linux-mips@oss.sgi.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