This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug backtrace/11313] internal-error: print_frame_args: Assertion`nsym != NULL' failed
- From: "Randy.Taylor at synopsys dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Wed, 3 Nov 2010 21:31:34 +0000
- Subject: [Bug backtrace/11313] internal-error: print_frame_args: Assertion`nsym != NULL' failed
- Auto-submitted: auto-generated
- References: <bug-11313-4717@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=11313
--- Comment #7 from Randy.Taylor at synopsys dot com 2010-11-03 21:31:20 UTC ---
Hi Jan,
To your question, our user believes that the Intel Fortran compiler produces
faster code than does gfortran.
Would this change that was just made go into the 7.3.50 release of gdb?
Randy
-----Original Message-----
From: jan.kratochvil at redhat dot com
[mailto:sourceware-bugzilla@sourceware.org]
Sent: Wednesday, November 03, 2010 2:28 PM
To: Randy.Taylor@synopsys.COM
Subject: [Bug backtrace/11313] internal-error: print_frame_args: Assertion
`nsym != NULL' failed
http://sourceware.org/bugzilla/show_bug.cgi?id=11313
--- Comment #6 from Jan Kratochvil <jan.kratochvil at redhat dot com>
2010-11-03 21:27:17 UTC ---
Created attachment 5108
--> http://sourceware.org/bugzilla/attachment.cgi?id=5108
Fix for the case insensitivity part.
With this patch GDB no longer crashes on internal error.
Still it displays incorrectly:
$3 = (REF TO -> ( character*16 )) @0x31677261: <error reading variable>
which is IIRC due to invalid DWARF produced by iFort but I would have to
recheck it.
Why don't you use gfortran?
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.