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

[Yao Qi]

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.

-- 
Yao (齐尧)