Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Luis Machado <lgustavo@codesourcery.com>
To: Yao Qi <yao@codesourcery.com>,
	"'gdb-patches@sourceware.org'"	<gdb-patches@sourceware.org>
Subject: Re: [RFC] gdb.base/frame-args.exp
Date: Thu, 03 Jul 2014 07:03:00 -0000	[thread overview]
Message-ID: <53B5003A.6070203@codesourcery.com> (raw)
In-Reply-To: <53B4FBE6.20505@codesourcery.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, i 
suppose it has not gone in.

Regards,
Luis


  reply	other threads:[~2014-07-03  7:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-01  7:56 Luis Machado
2014-07-03  6:46 ` Yao Qi
2014-07-03  7:03   ` Luis Machado [this message]
2014-07-03  7:29     ` Yao Qi

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=53B5003A.6070203@codesourcery.com \
    --to=lgustavo@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    --cc=yao@codesourcery.com \
    /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