Bug 16118 - gdb.base/frame-args.exp PowerPC/Linux failures
Summary: gdb.base/frame-args.exp PowerPC/Linux failures
Status: NEW
Alias: None
Product: gdb
Classification: Unclassified
Component: gdb (show other bugs)
Version: HEAD
: P2 normal
Target Milestone: ---
Assignee: Not yet assigned to anyone
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-11-04 17:34 UTC by Maciej W. Rozycki
Modified: 2013-11-04 17:34 UTC (History)
0 users

See Also:
Host:
Target: powerpc-linux-gnu
Build:
Last reconfirmed:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Maciej W. Rozycki 2013-11-04 17:34:21 UTC 
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.