From: Tom Tromey <tromey@redhat.com>
To: Pedro Alves <palves@redhat.com>
Cc: Marc Khouzam <marc.khouzam@ericsson.com>,
"'gdb-patches\@sourceware.org'"
<gdb-patches@sourceware.org>
Subject: Re: [Patch] Cannot set pending bp if condition set explicitly
Date: Mon, 30 Jul 2012 15:36:00 -0000 [thread overview]
Message-ID: <87k3xl45x3.fsf@fleche.redhat.com> (raw)
In-Reply-To: <5016A5DD.8040502@redhat.com> (Pedro Alves's message of "Mon, 30 Jul 2012 16:18:53 +0100")
>>>>> "Pedro" == Pedro Alves <palves@redhat.com> writes:
Pedro> An alternative would be to restrict pending breakpoints conditions
Pedro> to globals only. Not sure whether that would fly.
Yeah, I'd rather not.
For example, it would mean that a breakpoint that examines function
arguments would work fine if the function was in the main program; but
if you refactored the code to move it to a shared library, it would not
work.
Also it seems to me that you'd have to add extra semantics to decide
what to do in the re-run case, where a conditional breakpoint is set in
a .so that is loaded at some point during the run. Here, won't the
breakpoint convert itself to pending, and then back when the .so is
loaded? Would this then mean that the expression is interpreted
differently?
Tom
next prev parent reply other threads:[~2012-07-30 15:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-24 14:45 Marc Khouzam
2012-07-25 15:28 ` Tom Tromey
2012-07-25 20:31 ` Marc Khouzam
2012-07-25 20:44 ` Tom Tromey
2012-07-26 19:05 ` Pedro Alves
2012-07-27 2:45 ` Marc Khouzam
2012-07-30 15:19 ` Pedro Alves
2012-07-30 15:36 ` Tom Tromey [this message]
2012-08-03 0:44 ` disable breakpoints with invalid condition (Re: [Patch] Cannot set pending bp if condition set explicitly) Pedro Alves
2012-08-03 0:51 ` [Patch] Cannot set pending bp if condition set explicitly 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=87k3xl45x3.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=marc.khouzam@ericsson.com \
--cc=palves@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