From: "Josh Keller" <jkeller@keytechinc.com>
To: "Daniel Jacobowitz" <drow@false.org>
Cc: <binutils@sourceware.org>, "Reuben Johnston" <rjohnston@keytechinc.com>
Subject: Internal Error in GDB (was: ld includes entire archive (.a) when compiling .elf file)
Date: Fri, 07 Apr 2006 14:17:00 -0000 [thread overview]
Message-ID: <E736F3E26DE59146A2343541510255B579F3D5@mercury.keytechinc.com> (raw)
Daniel, for some reason, when I turn on garbage collection, I get the
following error (many, many times) when I run gdb:
Internal error: pc 0x0 in read in psymtab, but not in symtab.
I can still debug my program, but I get these errors all over the place.
I saw a thread back in 2002 titled (Internal error in GDB) initially
posted by Steven Johnson. I'm not sure what the ultimate resolution
was. Any ideas?
-Josh
-----Original Message-----
From: Daniel Jacobowitz [mailto:drow@false.org]
Sent: Friday, March 10, 2006 6:43 PM
To: Josh Keller
Cc: binutils@sourceware.org; Reuben Johnston
Subject: Re: ld includes entire archive (.a) when compiling .elf file
On Fri, Mar 10, 2006 at 06:08:53PM -0500, Josh Keller wrote:
> How will specifying the start of execution with (-e) remove the
> uncalled functions and unused variables? Does the ld linker even have
> the capability to automatically remove uncalled functions without
> having to specify each used section? I'm sorry if I sound really
> confused, I'm pretty new to this. Thanks for your patience.
No, you need that to prevent the linker from removing everything.
--
Daniel Jacobowitz
CodeSourcery
next reply other threads:[~2006-04-07 14:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-07 14:17 Josh Keller [this message]
2006-04-07 14:28 ` Daniel Jacobowitz
2006-04-07 14:51 ` Alan Modra
2006-04-07 14:34 Josh Keller
2006-04-07 14:38 ` Daniel Jacobowitz
2006-04-07 14:59 ` Dave Korn
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=E736F3E26DE59146A2343541510255B579F3D5@mercury.keytechinc.com \
--to=jkeller@keytechinc.com \
--cc=binutils@sourceware.org \
--cc=drow@false.org \
--cc=rjohnston@keytechinc.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).