public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "Randy.Taylor at synopsys dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug backtrace/11313] internal-error: print_frame_args: Assertion `nsym != NULL' failed Date: Wed, 03 Nov 2010 21:37:00 -0000 [thread overview] Message-ID: <bug-11313-4717-lBfAO7Zt1m@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <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.
next prev parent reply other threads:[~2010-11-03 21:31 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-11313-4717@http.sourceware.org/bugzilla/> 2010-11-03 21:27 ` jan.kratochvil at redhat dot com 2010-11-03 21:31 ` jan.kratochvil at redhat dot com 2010-11-03 21:37 ` Randy.Taylor at synopsys dot com [this message] 2010-11-03 21:51 ` jan.kratochvil at redhat dot com 2010-11-04 5:35 ` Randy.Taylor at synopsys dot com 2010-11-04 6:59 ` [Bug fortran/11313] iFort: " jan.kratochvil at redhat dot com 2011-04-08 18:00 ` jan.kratochvil at redhat dot com 2011-04-08 18:00 ` jan.kratochvil at redhat dot com 2014-02-16 19:30 ` jackie.rosen at hushmail dot com 2014-05-28 19:44 ` schwab at sourceware dot org 2010-02-23 12:01 [Bug backtrace/11313] New: " mgrojo at indra dot es 2010-02-25 11:32 ` [Bug backtrace/11313] " mgrojo at indra dot es 2010-07-07 23:09 ` rtaylor at synopsys dot com 2010-07-07 23:14 ` rtaylor at synopsys dot com 2010-07-07 23:50 ` rtaylor at synopsys dot com 2010-07-13 19:02 ` rtaylor at synopsys dot com 2010-07-16 16:47 ` tromey at redhat dot com 2010-07-16 21:55 ` rtaylor at synopsys dot com
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=bug-11313-4717-lBfAO7Zt1m@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.org \ /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: linkBe 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).