From: Doug Evans <dje@transmeta.com>
To: gdb@sources.redhat.com
Subject: commands command not allowed in macros, bug?
Date: Wed, 31 Mar 2004 09:18:00 -0000 [thread overview]
Message-ID: <16489.7229.172668.763290@casey.transmeta.com> (raw)
In-Reply-To: <200403261736.i2QHaLn29409@claire.transmeta.com>
I wrote:
> (gdb) foo
> Breakpoint 1 at 0x8048406: file hello.c, line 6.
>
> [gdb is now hung waiting for the user to type `end']
>
> end # <<< type this in
> foo # gdb prints this, the commands of breakpoint 1 are run
> (gdb) quit
Oops, thinko.
s/commands of breakpoint 1 are run/rest of macro foo is run/
prev parent reply other threads:[~2004-03-30 7:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-29 18:43 Doug Evans
2004-03-31 9:18 ` Doug Evans [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=16489.7229.172668.763290@casey.transmeta.com \
--to=dje@transmeta.com \
--cc=gdb@sources.redhat.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