From: Pedro Alves <palves@redhat.com>
To: Stan Shebs <stanshebs@earthlink.net>
Cc: Tom Tromey <tromey@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH v2] dynamic printf
Date: Wed, 16 May 2012 20:52:00 -0000 [thread overview]
Message-ID: <4FB4137C.6000107@redhat.com> (raw)
In-Reply-To: <4FB41216.2080508@earthlink.net>
On 05/16/2012 09:46 PM, Stan Shebs wrote:
>> I thought this approach would break "next"ing over a dprintf location.
>
> Indeed, thus this part of the introduction to this patch: :-)
>
> "... Joel previously noted a problem with the "continue" in the command list, which is
> that stepping/nexting over a dprintf becomes a continue instead (this is a problem for
> general breakpoint command lists as well). I tinkered with bpstats a bit, but didn't
> come up with a good solution.
This is normally handled by the bpstat saying "don't stop". Doesn't that work
for this? Why?
> Ironically, the agent version doesn't have this problem, because the resume happens automatically inside GDBserver, and GDB is oblivious.
That's sort of what happens when the bpstat returns "don't stop for this".
--
Pedro Alves
next prev parent reply other threads:[~2012-05-16 20:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-08 6:27 Stan Shebs
2012-05-08 7:50 ` Yao Qi
2012-05-14 15:54 ` Stan Shebs
2012-05-15 4:10 ` [commit] Fix spu-tdep.c build regression [Re: [PATCH v2] dynamic printf] Jan Kratochvil
2012-05-15 10:24 ` Jim Meyering
2012-05-15 13:10 ` [commit] testsuite: gdb.base/dprintf.exp PR 12649 race " Jan Kratochvil
2012-05-15 13:34 ` Joel Brobecker
2012-05-15 13:37 ` [commit#2] " Jan Kratochvil
2012-05-16 20:17 ` [PATCH v2] dynamic printf Tom Tromey
2012-05-16 20:46 ` Stan Shebs
2012-05-16 20:52 ` Pedro Alves [this message]
2012-05-16 22:25 ` Stan Shebs
2012-05-17 1:56 ` Tom Tromey
2012-05-18 15:38 ` Pedro Alves
2012-05-16 20:53 ` Pedro Alves
2012-05-16 21:06 ` Tom Tromey
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=4FB4137C.6000107@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=stanshebs@earthlink.net \
--cc=tromey@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