From: Daniel Jacobowitz <drow@false.org>
To: Steven Johnson <sjohnson@sakuraindustries.com>
Cc: Michael Eager <eager@eagercon.com>, gdb@sources.redhat.com
Subject: Re: GDB internal error: pc in psymtab, not in symtab
Date: Thu, 12 Oct 2006 12:52:00 -0000 [thread overview]
Message-ID: <20061012125241.GA32739@nevyn.them.org> (raw)
In-Reply-To: <452DF4D9.607@sakuraindustries.com>
On Thu, Oct 12, 2006 at 06:55:05PM +1100, Steven Johnson wrote:
> I suggest you read this thread:
> http://sourceware.org/ml/gdb/2006-06/msg00085.html
>
> It may be the cause of your problem, as it is the cause of this warning
> for me.
>
> I simply comment out the code referred to in this post and this warning
> goes away for me. I can't come up with a better way to deal with it.
> Of course if you also have .linkonce sections in your program, you are
> probably hosed.
That was already fixed in CVS for your case, as you may recall.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-10-12 12:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-12 4:29 Michael Eager
2006-10-12 4:43 ` Daniel Jacobowitz
2006-10-12 7:55 ` Steven Johnson
2006-10-12 12:52 ` Daniel Jacobowitz [this message]
2006-10-12 20:30 ` Steven Johnson
2006-10-12 15:11 ` Michael Eager
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=20061012125241.GA32739@nevyn.them.org \
--to=drow@false.org \
--cc=eager@eagercon.com \
--cc=gdb@sources.redhat.com \
--cc=sjohnson@sakuraindustries.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