Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Steven Johnson <sjohnson@neurizon.net>
To: gdb@sources.redhat.com
Subject: Internal error in GDB
Date: Wed, 13 Nov 2002 23:40:00 -0000	[thread overview]
Message-ID: <3DD351ED.7000409@neurizon.net> (raw)

Im getting the error:

Internal error: pc 0x0 in read in psymtab, but not in symtab.

from a very recent CVS build of GDB (As of 11th November).

It happens when I set breakpoints in an assembler file, that has been 
assembled through GCC, using the C Preprocessor (.S file, not .s file).

It does nothing wrong, except pop up all the time and hence interfere 
with debugging significantly. (Im using insight and have to keep 
pressing OK to continue).

I searched the code and it seems to be coming from 
symtab.c:find_pc_sect_symtab (last if in the function)

The comment in the code indicates that this error may want to stop GDB 
cold. Thankfully it isn't, cause I seem to be getting it in error.

Also, the code here seems to be wrong, it prints the error, and then 
proceeds to look it up anyway. As in:

if (ps->readin)
   warning("Internal error: pc 0x%s in read in psymtab, but not in 
symtab.",paddr_nz(pc));

s = PSYMTAB_TO_SYMTAB(s)

I would have expected, from the error, it not to try and 
PSYMTAB_TO_SYMTAB, as it is saying it isn't in the SYMTAB. as in:

if (ps->readin)
   warning("Internal error: pc 0x%s in read in psymtab, but not in 
symtab.",paddr_nz(pc));
else
   s = PSYMTAB_TO_SYMTAB(s)

Anyway, what is going on here?  What do i need to do to my assembler 
file to prevent this warning?

Regards,
Steven Johnson



             reply	other threads:[~2002-11-14  7:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-13 23:40 Steven Johnson [this message]
2002-11-14  7:14 ` Daniel Jacobowitz
2002-11-19 12:09   ` Daniel Jacobowitz
2002-11-20 20:42     ` Jim Blandy
2002-11-20 20:50       ` DWARF-2 + discarded link-once sections (was Re: Internal error in GDB) Daniel Jacobowitz
2002-11-20 22:30         ` H. J. Lu
2002-11-20 22:40         ` Daniel Berlin

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=3DD351ED.7000409@neurizon.net \
    --to=sjohnson@neurizon.net \
    --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