Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: gdb@sourceware.org
Subject: Re: Multiple breakpoints
Date: Thu, 03 Apr 2008 09:01:00 -0000	[thread overview]
Message-ID: <jelk3vqpm1.fsf@sykes.suse.de> (raw)
In-Reply-To: <18420.39684.185853.891083@kahikatea.snap.net.nz> (Nick Roberts's 	message of "Thu\, 3 Apr 2008 20\:53\:24 +1200")

Nick Roberts <nickrob@snap.net.nz> writes:

> If I set a breakpoint on TRY_CATCH in gdb_evaluate_expression, I get
> multiple breakpoints:
>
>   gdb_evaluate_expression (struct expression *exp, struct value **value)
>   {
>     volatile struct gdb_exception except;
>
> ->  TRY_CATCH (except, RETURN_MASK_ERROR)
>       {
>         *value = evaluate_expression(exp);
>       }
>
>     if (except.reason < 0)
>       return 0;
>     return 1;
>   }
>
> where -> shows the breakpoint location.
>
>
> Is this to be expected?  The assembler looks like this:

TRY_CATCH expands to a loop, probably the loop condition has been
duplicated by the compiler.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."


  reply	other threads:[~2008-04-03  9:01 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 [this message]
2008-04-03 13:18   ` Daniel Jacobowitz
2008-04-03 13:55     ` Vladimir Prus
2008-04-03 14:07       ` Daniel Jacobowitz
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=jelk3vqpm1.fsf@sykes.suse.de \
    --to=schwab@suse.de \
    --cc=gdb@sourceware.org \
    --cc=nickrob@snap.net.nz \
    /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