This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [RFC] gdb.base/frame-args.exp

From: Luis Machado <lgustavo at codesourcery dot com>
To: Yao Qi <yao at codesourcery dot com>, "'gdb-patches at sourceware dot org'" <gdb-patches at sourceware dot org>
Date: Thu, 3 Jul 2014 08:03:22 +0100
Subject: Re: [RFC] gdb.base/frame-args.exp
Authentication-results: sourceware.org; auth=none
References: <53B26994 dot 8000306 at codesourcery dot com> <53B4FBE6 dot 20505 at codesourcery dot com>
Reply-to: <lgustavo at codesourcery dot com>

Hi Yao,

On 07/03/2014 07:44 AM, Yao Qi wrote:

On 07/01/2014 03:56 PM, Luis Machado wrote:

So it looks like we are taking a different route and GDB ends up
catching an error before displaying the optimized out information, thus
not matching what the testcase expects.

I could add a different pattern to the testcase and that would solve the
couple failures i see, but i wonder if we should tweak the testcase to
dodge optimizations?


Hi Luis,
Andrew Burgess had a patch changing "<error reading variable: value has
been optimized out>" to "<optimized out>" in this thread,

   PATCH: error reading variable: value has been optimized out
   https://sourceware.org/ml/gdb-patches/2012-08/msg00715.html

so I think "<optimized out>" is the right direction to go.  We should
fix gdb rather than update test case to match the current output, IMO.

Excellent! Thanks for pointing that out. Seeing the date of the patch, isuppose it has not gone in.


Regards,
Luis

Follow-Ups:
- Re: [RFC] gdb.base/frame-args.exp
  - From: Yao Qi

References:
- [RFC] gdb.base/frame-args.exp
  - From: Luis Machado
- Re: [RFC] gdb.base/frame-args.exp
  - From: Yao Qi

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]