Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Edjunior Barbosa Machado <emachado@linux.vnet.ibm.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
	       Yao Qi <yao@codesourcery.com>
Subject: Re: [patch] Re: "optimized out" on gdb.base/gdb1090.exp
Date: Wed, 13 Apr 2011 21:20:00 -0000	[thread overview]
Message-ID: <4DA6136F.8060907@linux.vnet.ibm.com> (raw)
In-Reply-To: <20110413111504.GA28987@host1.jankratochvil.net>



On 04/13/2011 08:15 AM, Jan Kratochvil wrote:
> On Tue, 12 Apr 2011 23:21:48 +0200, Edjunior Barbosa Machado wrote:
>> Checking out the original PR 1090 that originated this testcase, it doesn't
>> mention any particularity regarding frame or backtrace, which leads me to
>> believe that changing where 'print' is called should not affect the main
>> focus of the testcase.
>
> PR 1090 should have been about "allocate a variable into multiple registers"
> which is still being tested so the testcase should be OK even this way.
>   <2><8d>: Abbrev Number: 8 (DW_TAG_variable)
>      <8e>    DW_AT_name        : s24
> [...]
>      <98>    DW_AT_location    : 6 byte block: 53 93 4 56 93 4    (DW_OP_reg3 (ebx); DW_OP_piece: 4; DW_OP_reg6 (esi); DW_OP_piece: 4)
>
>
> On Wed, 13 Apr 2011 03:26:11 +0200, Yao Qi wrote:
>> On 04/13/2011 05:21 AM, Edjunior Barbosa Machado wrote:
>>>
>>> 2011-04-12  Edjunior Machado<emachado@br.ibm.com>
>>>
>>>      * testsuite/gdb.base/gdb1090.exp: change breakpoint location to
>>> read the
>>
>> Please remove spurious spaces between "to" and "read".
>>
>>>      content of 's24' correctly (avoiding "optimized out").
>>>      * testsuite/gdb.base/gdb1090.c: add comment in order to set breakpoint.
>>          ^^^^^^^^^  Delete "testsuite/", since this changelog entry will
>> go to gdb/testsuite/ChangLog.
>
> And the first letter of the sentence should be capital.
> 	http://www.gnu.org/prep/standards/html_node/Style-of-Change-Logs.html#Style-of-Change-Logs
>
> Please check it in with those changes.
>
>
> Thanks,
> Jan
>

Thanks Jan and Yao Qi for the feedback. Checked in with the mentioned changes:
	http://sourceware.org/ml/gdb-cvs/2011-04/msg00083.html

-- 
Edjunior


      reply	other threads:[~2011-04-13 21:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4DA3A7D0.2000701@linux.vnet.ibm.com>
     [not found] ` <4DA3B701.3060902@codesourcery.com>
     [not found]   ` <4DA4573D.1040101@linux.vnet.ibm.com>
     [not found]     ` <20110412160220.GA18580@host1.jankratochvil.net>
2011-04-12 21:22       ` Edjunior Barbosa Machado
2011-04-13  1:26         ` Yao Qi
2011-04-13 11:15         ` Jan Kratochvil
2011-04-13 21:20           ` Edjunior Barbosa Machado [this message]

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=4DA6136F.8060907@linux.vnet.ibm.com \
    --to=emachado@linux.vnet.ibm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@redhat.com \
    --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