Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Andrew STUBBS <andrew.stubbs@st.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
	Joel Brobecker <brobecker@adacore.com>,
		hilfingr@gnat.com, gdb@sourceware.org
Subject: Re: [RFC] multiple breakpoints from FILE:LINE
Date: Fri, 13 Jan 2006 15:27:00 -0000	[thread overview]
Message-ID: <20060113152728.GC9758@nevyn.them.org> (raw)
In-Reply-To: <43C7B5EF.20900@st.com>

On Fri, Jan 13, 2006 at 02:15:11PM +0000, Andrew STUBBS wrote:
> Eli Zaretskii wrote:
> >How about something like
> >
> >    break something.adb:12 if SOME_CONDITION
> >
> >where SOME_CONDITION is something we should invent to specify the
> >instance where we want to put the single breakpoint?  This has the
> >advantage of using an existing syntax, especially if the condition
> >could be made to use some convenience variable.  By contrast, what you
> >suggest modifies the syntax of a location specification; do we really
> >want that?
> 
> Not that it makes any real difference but ...
> 
> To me that looks like it will set a break point everywhere and then 
> check at runtime if it is the right one.
> 
> Now I know you weren't thinking of doing that, but that's what the 
> condition normally means.
> 
> It may also make setting a real condition more tricky.

Yes, I agree.

I think we do want to modify the syntax of a location expression,
which is currently somewhat complicated and weakly defined.  However,
I've suggested that we do that as a second step - to specify one single
breakpoint, instead of the multiple ones we'd set by default.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2006-01-13 15:27 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-13 10:42 Paul Hilfinger
2006-01-13 11:32 ` Eli Zaretskii
2006-01-13 11:56   ` Joel Brobecker
2006-01-13 13:05     ` Eli Zaretskii
2006-01-13 14:17       ` Andrew STUBBS
2006-01-13 15:27         ` Daniel Jacobowitz [this message]
2006-01-13 15:25   ` Daniel Jacobowitz
2006-01-13 15:19 ` Paul Koning
2006-01-13 15:23 ` Daniel Jacobowitz
2006-01-13 15:40   ` Joel Brobecker
2006-01-14 10:15   ` Paul Hilfinger
2006-01-14 16:16     ` Daniel Jacobowitz
2006-01-15  1:51 : " Cyrille Comar
2006-01-15 22:23 ` Paul Hilfinger
2006-01-15 17:38 David Anderson
2006-01-15 17:50 ` Daniel Jacobowitz
2006-01-15 17:54 ` Robert Dewar
2006-01-15 18:33   ` Andreas Schwab
2006-01-15 19:06     ` Robert Dewar

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=20060113152728.GC9758@nevyn.them.org \
    --to=drow@false.org \
    --cc=andrew.stubbs@st.com \
    --cc=brobecker@adacore.com \
    --cc=eliz@gnu.org \
    --cc=gdb@sourceware.org \
    --cc=hilfingr@gnat.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