public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: gdb@sources.redhat.com
Subject: Re: warning: (Internal error: pc 0xd00 in read in psymtab, but not in symtab.)
Date: Tue, 15 Nov 2005 02:09:00 -0000	[thread overview]
Message-ID: <20051115020856.GB9639@nevyn.them.org> (raw)
In-Reply-To: <20051115010716.GA14640@Power-Mac-G5.local>

On Mon, Nov 14, 2005 at 08:07:16PM -0500, Ron McCall wrote:
> If I enter "disas main" instead, no warnings are printed.  There is a
> symbol at 0xd00 named trace_exc and "disas trace_exc" also generates the
> warnings.  Note that the trace exception handler is written in assembly
> (GNU as) and normally resides in a custom section named "excvectbl".
> However, I changed that to ".text" just to make sure it wasn't the
> custom section that was causing grief and that didn't help.
> 
> Anything else I should look at?

Then it's probably a result of having some code with no debug info. 
You may want to try producing a small test case, that you can post for
us to examine.

-- 
Daniel Jacobowitz
CodeSourcery, LLC

  reply	other threads:[~2005-11-15  2:09 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-08 15:07 Ron McCall
2005-11-13 17:39 ` Daniel Jacobowitz
2005-11-15  1:07   ` Ron McCall
2005-11-15  2:09     ` Daniel Jacobowitz [this message]
2005-11-16  3:28       ` Ron McCall
2005-11-15  6:50     ` Vladimir Prus
2005-11-15 20:46       ` Ron McCall
2005-11-15 23:10         ` Jim Blandy
2005-11-15 23:25           ` Daniel Jacobowitz
2005-11-16  0:12             ` Jim Blandy
2005-11-16  0:38               ` Daniel Jacobowitz
2005-11-16  1:33                 ` Jim Blandy
2005-11-16  2:53                   ` Daniel Jacobowitz
     [not found]                   ` <20051116025218.GA27921@nevyn.them.org>
2005-11-16  2:54                     ` Jim Blandy
2005-11-16  2:56                       ` Daniel Jacobowitz

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=20051115020856.GB9639@nevyn.them.org \
    --to=drow@false.org \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).