Article View: gnu.gdb.bug
Article #226Fortran problem with 3.2
From: Chris Smith
Date: Fri, 04 Aug 1989 00:17
Date: Fri, 04 Aug 1989 00:17
20 lines
992 bytes
992 bytes
The problem where Fortran causes gdb to say gdb: Internal error: Unexpected debugging symbol type 't' at symnum -2147269732. is due to Fortran's using N_GSYM for typedefs. Here's a fix, in dbxread.c function read_dbx_symtab, at around line 2307: case 'G': ADD_PSYMBOL_TO_LIST (namestring, p - namestring, VAR_NAMESPACE, LOC_EXTERNAL, global_psymbols, bufp->n_value); continue; + + /* Fortran puts out N_GSYM typedefs. Ignore them here. */ + case 't': + continue; + /* I don't think the default case should happen. A breakpoint here to check would probably be good. */ default:
Technical Details
Message-ID:
<1460@convex.UUCP>Path:
arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!usc!cs.utexas.edu!uunet!convex!mozart!csmithShow Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!usc!cs.utexas.edu!uunet!convex!mozart!csmith From: csmith@mozart.uucp (Chris Smith) Newsgroups: gnu.gdb.bug Subject: Fortran problem with 3.2 Message-ID: <1460@convex.UUCP> Date: 4 Aug 89 00:17:13 GMT Sender: news@convex.UUCP Reply-To: csmith@convex.com Lines: 20