From: Michael Snyder <msnyder@vmware.com>
To: Paul Pluzhnikov <ppluzhnikov@google.com>
Cc: Gaius Mulley <gaius@glam.ac.uk>,
Sandeep222 <sandeep.srikumar@honeywell.com>,
"gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: How to store function-name and its return values while program runs
Date: Sat, 22 Nov 2008 00:47:00 -0000 [thread overview]
Message-ID: <49275680.50509@vmware.com> (raw)
In-Reply-To: <8ac60eac0811211410s2196e9a1g28c824850b222bf6@mail.gmail.com>
Paul Pluzhnikov wrote:
> On Fri, Nov 21, 2008 at 11:04 AM, Michael Snyder <msnyder@vmware.com> wrote:
>
>> (gdb) break function1
>> (gdb) commands
>>> finish
>>> continue
>>> end
>> (gdb)
>
> I wished many times that above worked, but it doesn't: 'finish'
> appears to interrupt flow of script, and subsequent commands are
> never executed:
Am I halucinating? I thought we fixed that a long time ago.
prev parent reply other threads:[~2008-11-22 0:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-21 10:36 Sandeep222
2008-11-21 11:02 ` Gaius Mulley
2008-11-21 19:05 ` Michael Snyder
2008-11-21 22:11 ` Paul Pluzhnikov
2008-11-21 22:29 ` Joel Brobecker
2008-11-22 0:48 ` Michael Snyder
2008-11-22 0:59 ` Joel Brobecker
2008-11-22 0:47 ` Michael Snyder [this message]
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=49275680.50509@vmware.com \
--to=msnyder@vmware.com \
--cc=gaius@glam.ac.uk \
--cc=gdb@sourceware.org \
--cc=ppluzhnikov@google.com \
--cc=sandeep.srikumar@honeywell.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