From: Yao Qi <yao@codesourcery.com>
To: <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Set breakpoint on the right line
Date: Tue, 19 Aug 2014 00:50:00 -0000 [thread overview]
Message-ID: <53F29E7B.2080602@codesourcery.com> (raw)
In-Reply-To: <1407806302-14295-1-git-send-email-yao@codesourcery.com>
On 08/12/2014 09:18 AM, Yao Qi wrote:
> In gdb.base/watchpoint-hw-hit-once.exp, test scans source and set
> breakpoint on the line having "break-at-exit",
>
> gdb_breakpoint [gdb_get_line_number "break-at-exit"]
>
> However, in watchpoint-hw-hit-once.c, there are two lines having
> this key word:
>
> dummy = 1; /* Stub to catch break-at-exit after WATCHEE has been hit. */
> dummy = 2; /* break-at-exit */
>
> so the test sets breakpoint on the first one, while I think it is
> expected to set breakpoint on the second one, as far as I can tell
> from the comments in watchpoint-hw-hit-once.c:
>
> /* Stub lines are present as no breakpoints/watchpoint gets hit if current PC
> already stays on the line PC while entering "step"/"continue". */
>
> This patch is to change the source matching pattern so that test
> can correctly set breakpoint on the right line. This patch fixes
> a fail we found on arm-none-eabi target. Run it again
> on x86_64-linux, no result changes.
>
> gdb/testsuite:
>
> 2014-08-12 Yao Qi <yao@codesourcery.com>
>
> * gdb.base/watchpoint-hw-hit-once.exp: Set breakpoint on the
> right line.
Ping. https://sourceware.org/ml/gdb-patches/2014-08/msg00190.html
--
Yao (é½å°§)
next prev parent reply other threads:[~2014-08-19 0:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-12 1:22 Yao Qi
2014-08-19 0:50 ` Yao Qi [this message]
2014-08-19 6:38 ` Joel Brobecker
2014-08-19 13:35 ` Yao Qi
2014-08-19 13:48 ` Joel Brobecker
2014-08-20 0:21 ` Yao Qi
2014-08-19 17:20 ` [OB/PUSHED] Remove stale comment (was: Re: [PATCH] Set breakpoint on the right line) Pedro Alves
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=53F29E7B.2080602@codesourcery.com \
--to=yao@codesourcery.com \
--cc=gdb-patches@sourceware.org \
/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