public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "jan.kratochvil at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug fortran/11313] iFort: internal-error: print_frame_args: Assertion `nsym != NULL' failed
Date: Thu, 04 Nov 2010 06:59:00 -0000	[thread overview]
Message-ID: <bug-11313-4717-nAcxoB8C6D@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-11313-4717@http.sourceware.org/bugzilla/>

http://sourceware.org/bugzilla/show_bug.cgi?id=11313

Jan Kratochvil <jan.kratochvil at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|backtrace                   |fortran
            Version|7.1                         |7.2
         AssignedTo|unassigned at sourceware    |jan.kratochvil at redhat
                   |dot org                     |dot com
   Target Milestone|7.1                         |7.3
            Summary|internal-error:             |iFort: internal-error:
                   |print_frame_args: Assertion |print_frame_args: Assertion
                   |`nsym != NULL' failed       |`nsym != NULL' failed

--- Comment #10 from Jan Kratochvil <jan.kratochvil at redhat dot com> 2010-11-04 05:35:14 UTC ---
The `REF TO ->' / `<error reading variable>' problem is fixed by:
[new testcase] Regression 7.1->7.2 for iFort [Re: [RFA-v2] dwarf debug format:
Support DW_AT_variable_parameter attribute]
http://sourceware.org/ml/gdb-patches/2010-11/msg00084.html

so `str1' can be printed now with both patches:

(gdb) p str1
$1 = ' ' <repeats 16 times>
[...]
(gdb) p str1
$2 = 'arg1', ' ' <repeats 12 times>

-- 
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.


  parent reply	other threads:[~2010-11-04  5:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-11313-4717@http.sourceware.org/bugzilla/>
2010-11-03 21:27 ` [Bug backtrace/11313] " 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
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 ` jan.kratochvil at redhat dot com [this message]
2011-04-08 18:00 ` [Bug fortran/11313] iFort: " 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

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-nAcxoB8C6D@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: 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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).