public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "macro@linux-mips.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/16118] New: gdb.base/frame-args.exp PowerPC/Linux failures
Date: Mon, 04 Nov 2013 17:34:00 -0000	[thread overview]
Message-ID: <bug-16118-4717@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 16118
           Summary: gdb.base/frame-args.exp PowerPC/Linux failures
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: gdb
          Assignee: unassigned at sourceware dot org
          Reporter: macro@linux-mips.org
            Target: powerpc-linux-gnu

I see failures from gdb.base/frame-args.exp on the powerpc-linux-gnu
target:

(gdb) frame 1
#1  0x100006dc in call_me (i=3, f=5, s=<error reading variable: value has been
optimized out>, ss=0xbffff7d8, u=<error reading variable: value has been
optimized out>, e=green) at .../gdb/testsuite/gdb.base/frame-args.c:40
40        break_me ();
(gdb) FAIL: gdb.base/frame-args.exp: frame 1 with print frame-arguments set to
all

and:

(gdb) frame 1
#1  0x100006dc in call_me (i=3, f=5, s=<error reading variable: value has been
optimized out>, ss=0xbffff7d8, u=<error reading variable: value has been
optimized out>, e=green) at .../gdb/testsuite/gdb.base/frame-args.c:40
40        break_me ();
(gdb) FAIL: gdb.base/frame-args.exp: frame 1 with print frame-arguments set to
scalars

clearly because <error reading variable: value has been optimized out> is
printed rather than just <optimized out>.  The discussion here:

http://sourceware.org/ml/gdb-patches/2012-08/msg00715.html
http://sourceware.org/ml/gdb-patches/2012-09/msg00000.html

and commit 2603f7eeca78caeef1f362eccebe7cd4b589ba41 may be related,
although in my case GCC 4.8.1 is used.  Other targets seem unaffected.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


                 reply	other threads:[~2013-11-04 17:34 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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-16118-4717@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).