From: Pedro Alves <pedro@codesourcery.com>
To: gdb@sourceware.org, Eli Zaretskii <eliz@gnu.org>
Subject: Re: Breakpoint commands
Date: Sat, 24 Oct 2009 16:30:00 -0000 [thread overview]
Message-ID: <200910241704.00548.pedro@codesourcery.com> (raw)
In-Reply-To: <83iqe4g9t2.fsf@gnu.org>
A Saturday 24 October 2009 15:12:41, Eli Zaretskii escreveu:
> Some commands seem to be not working inside breakpoint commands, in
> the sense that breakpoint commands after them are not executed.
>
> Two examples that I tried were `finish' and `until'. What I wanted
> was to stop at function entry, print some variable, then let the
> function run to completion, and print some other (global) variable
> that gets modified by this function. The breakpoint commands
> therefore were something like
>
> break FOO
> commands
> >print BAR
> >finish
> >print BAZ
> >end
>
> and similarly with `until' instead of `finish'; I used the last line
> of the function's body for its argument.
>
> What I see is that the second `print' is never executed. Sounds like
> a bug to me. Or did I miss something?
>
From gdb.texinfo:'Break Commands':
"You can use breakpoint commands to start your program up again. Simply
use the @code{continue} command, or @code{step}, or any other command
that resumes execution.
Any other commands in the command list, after a command that resumes
execution, are ignored. This is because any time you resume execution
(even with a simple @code{next} or @code{step}), you may encounter
another breakpoint---which could have its own command list, leading to
ambiguities about which list to execute."
--
Pedro Alves
next prev parent reply other threads:[~2009-10-24 16:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-24 15:03 Eli Zaretskii
2009-10-24 16:30 ` Pedro Alves [this message]
2009-10-24 16:48 ` Eli Zaretskii
2009-10-24 23:05 ` Paul Pluzhnikov
2009-10-25 0:30 ` Michael Snyder
2009-10-26 11:30 ` Joel Brobecker
2009-10-26 13:15 ` Vladimir Prus
2009-10-26 23:42 ` Paul Pluzhnikov
2009-10-24 18:29 ` Andreas Schwab
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=200910241704.00548.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=eliz@gnu.org \
--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