Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Jim Blandy <jimb@codesourcery.com>
To: Steven Johnson <sjohnson@sakuraindustries.com>
Cc: gdb@sources.redhat.com
Subject: Re: Problems with startup code symbols (Copious warnings)
Date: Thu, 08 Jun 2006 09:06:00 -0000	[thread overview]
Message-ID: <vt2zmgom7qt.fsf@theseus.home.> (raw)
In-Reply-To: <4487C21F.2090907@sakuraindustries.com> (Steven Johnson's message of "Thu, 08 Jun 2006 17:22:23 +1100")


Steven Johnson <sjohnson@sakuraindustries.com> writes:
> For ever and a day with GDB i've gotten the following warnings:
>
> warning: (Internal error: pc 0x00 in read in psymtab, but not in symtab.)
>
> I get it a lot.  I even patch GDB so it doesn't generate this warning,
> its so annoying.
>
> 0x00 happens to be my programs entry point (its an embedded system). 
> And is in Assembler code.
>
> I've never liked patching GDB to get rid of this warning, so I invested
> some time on it and I've just discovered 2 ways to make it go away:
>
> 1. If I compile my code with stabs+ debug info, I don't get the
> warning.  I would prefer to use Dwarf-2 however, as it seems to be the
> way of the future.
>
> 2. If I add:
>
> .section .debug_info,"",@progbits as the first directive in my asm file,
> the warning also goes away.  But so does the code when I view it under GDB.
>
> Does anyone know any special incantation I need to make in my ASM file,
> to get rid of the warning, but still retain the symbolic information so
> I can see the code and symbols under GDB?
>
> The file is a ".S" file, it is assembler but i build it with GCC.  The
> CPU is a PowerPC, Motorola MPC862.

Can you post an executable for which GDB produces this message, and
let us know which target you've configured GDB for?


  reply	other threads:[~2006-06-08  7:23 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-08  7:23 Steven Johnson
2006-06-08  9:06 ` Jim Blandy [this message]
2006-06-08 12:25   ` Steven Johnson
2006-06-08 23:10     ` Steven Johnson
2006-06-15  0:12     ` Jim Blandy
2006-06-15  7:33       ` Jim Blandy
2006-06-19  9:36         ` Frederic RISS
2006-06-20 12:23           ` Daniel Jacobowitz
2006-06-20 12:33             ` Frederic RISS
2006-06-20 12:56               ` Daniel Jacobowitz
2006-06-20 13:09                 ` Frederic RISS
2006-06-20 20:17                   ` Steven Johnson
2006-06-20 23:35                     ` Daniel Jacobowitz
2006-06-21  8:54                       ` Frederic RISS
2006-06-21 14:44                         ` Steven Johnson
2006-06-21 15:28                         ` Daniel Jacobowitz
2006-06-19 10:00         ` Steven Johnson

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=vt2zmgom7qt.fsf@theseus.home. \
    --to=jimb@codesourcery.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