Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA/testsuite] check bt problem after 2 steps is gone
Date: Thu, 27 Jul 2006 13:41:00 -0000	[thread overview]
Message-ID: <20060727134139.GB15735@nevyn.them.org> (raw)
In-Reply-To: <20060428174035.GF930@adacore.com>

On Fri, Apr 28, 2006 at 10:40:35AM -0700, Joel Brobecker wrote:
> Hello,
> 
> This is a new testcase that checks that the issue reported in:
> 
>         http://sources.redhat.com/ml/gdb-patches/2006-04/msg00367.html
> 
> will not regress again.
> 
> 2006-04-28  Joel Brobecker  <brobecker@adacore.com>
> 
>         * gdb.base/step-bt.c: New file.
>         * gdb.base/step-bt.exp: New testcase.
> 
> Tested on i686-pc-cygwin. on XFAIL on the last test with the current
> sources, all PASSes once the patch in the message mentioned above is
> applied.
> 
> OK to apply?

When the patch goes in, this is fine.  Thanks for the test.
> gdb_test "stepi 2" \
>          "" \
>          "step 2 instructions"
> 
> gdb_test "bt" \
>          "#0 +0x\[0-9a-z\]+ in hello .*#1 +0x\[0-9a-z\]* in main.*" \
>          "backtrace after two instruction steps"

Would it work to test backtrace after each of two stepi's?  That might
turn up interesting similar problems on more platforms.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2006-07-27 13:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-28 17:40 Joel Brobecker
2006-07-27 13:41 ` Daniel Jacobowitz [this message]
2006-07-28  1:11   ` Joel Brobecker
2006-07-28  1:51     ` Daniel Jacobowitz
2006-07-28  2:37       ` Joel Brobecker
2006-08-08 21:51 ` Joel Brobecker

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=20060727134139.GB15735@nevyn.them.org \
    --to=drow@false.org \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sources.redhat.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