From: Daniel Jacobowitz <drow@false.org>
To: gdb@sourceware.org, gdb@sources.redhat.com
Subject: Re: Multiple breakpoints
Date: Thu, 03 Apr 2008 14:02:00 -0000 [thread overview]
Message-ID: <20080403140140.GA20986@caradoc.them.org> (raw)
Message-ID: <20080403140200.DL8Hg4Nnl1Twj51SCHL9mqEVTHinRnl3wdS0N0nwx8U@z> (raw)
In-Reply-To: <ft2nc3$3vs$2@ger.gmane.org>
On Thu, Apr 03, 2008 at 05:51:00PM +0400, Vladimir Prus wrote:
> Daniel Jacobowitz wrote:
>
> > On Thu, Apr 03, 2008 at 11:01:10AM +0200, Andreas Schwab wrote:
> >> TRY_CATCH expands to a loop, probably the loop condition has been
> >> duplicated by the compiler.
> >
> > I think we try to set only one breakpoint per containing function,
> > though.
>
> Uh-uh, you keep on telling this :-)
> Per *block*, not per function.
Durn. Well, I would have thought the parts of a for loop were in the
same block, but I can see GCC deciding otherwise.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-04-03 14:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-03 8:54 Nick Roberts
2008-04-03 9:01 ` Andreas Schwab
2008-04-03 13:18 ` Daniel Jacobowitz
2008-04-03 13:55 ` Vladimir Prus
2008-04-03 14:07 ` Daniel Jacobowitz [this message]
2008-04-03 14:02 ` Daniel Jacobowitz
2008-04-03 17:37 ` Michael Snyder
2008-04-03 21:36 ` Michael Snyder
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=20080403140140.GA20986@caradoc.them.org \
--to=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=gdb@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