From: Pedro Alves <palves@redhat.com>
To: Hui Zhu <teawater@gmail.com>
Cc: gdb-patches ml <gdb-patches@sourceware.org>
Subject: Re: [PATCH] fix PR 15180 "May only run agent-printf on the target"
Date: Wed, 26 Jun 2013 18:00:00 -0000 [thread overview]
Message-ID: <51CB2BAA.1070507@redhat.com> (raw)
In-Reply-To: <CANFwon1CBRpQYOCzUD16JX-4spE-cMJFq4PF0oGd8m1irJndoA@mail.gmail.com>
On 06/17/2013 08:47 AM, Hui Zhu wrote:
> Hi,
>
> This patch is for PR 15180 too. Because it depends on patch in
> http://sourceware.org/ml/gdb-patches/2013-06/msg00139.html
> So I post it in another thread.
>
> It make dprintf_after_condition_true doesn't do actions if dprintf
> style is agent. Because the actions is already did in agent.
If dprintf style is agent, then the target doesn't report events
for such hits. If we happen to see a trap reported for the
same address as another breakpoint, the trap is surely not explained
by the dprintf. IOW, we shouldn't have a bpstat a dprintf w/ style
agent at all. What is need is to override the breakpoint_hit method
of dprintf_breakpoint_ops to always return false for agent style dprintfs.
Or maybe I'm missing something. I have a hard time going from
the bug description in the PR to the patch.
>
> The test patch test the issue about 15180.
Hmm, I get:
Running target native-gdbserver
Using ../../../src/gdb/testsuite/boards/../boards/native-gdbserver.exp as board description file for target.
Using ../../../src/gdb/testsuite/config/gdbserver.exp as tool-and-target-specific interface file.
Running ../../../src/gdb/testsuite/gdb.base/dprintf-same-addr.exp ...
FAIL: gdb.base/dprintf-same-addr.exp: agent: First continue (the program exited)
FAIL: gdb.base/dprintf-same-addr.exp: agent: Second continue (the program is no longer running)
FAIL: gdb.base/dprintf-same-addr.exp: agent: check i
=== gdb Summary ===
# of expected passes 16
# of unexpected failures 3
# of unsupported tests 1
>
> Thanks,
> Hui
>
> 2013-06-17 Hui Zhu <hui@codesourcery.com>
>
> PR gdb/15180
> * breakpoint.c (dprintf_after_condition_true): Check dprintf style
> before do actions.
>
> 2013-06-17 Hui Zhu <hui@codesourcery.com>
>
> PR gdb/15180
> * gdb.base/dprintf-same-addr.c: New file.
> * gdb.base/dprintf-same-addr.exp: New file.
>
--
Pedro Alves
next prev parent reply other threads:[~2013-06-26 17:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-17 10:12 Hui Zhu
2013-06-26 18:00 ` Pedro Alves [this message]
2013-06-30 17:15 ` Hui Zhu
2013-07-01 8:10 ` Pedro Alves
2013-07-01 8:51 ` Hui Zhu
2013-07-01 14:29 ` Pedro Alves
2013-07-01 16:08 ` Hui Zhu
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=51CB2BAA.1070507@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=teawater@gmail.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