From: Daniel Jacobowitz <drow@false.org>
To: Doug Evans <dje@transmeta.com>
Cc: gdb@sources.redhat.com
Subject: Re: commands on tbreak breakpoints, should they work?
Date: Mon, 29 Mar 2004 16:27:00 -0000 [thread overview]
Message-ID: <20040326173038.GA12047@nevyn.them.org> (raw)
In-Reply-To: <200403261727.i2QHRZU29384@claire.transmeta.com>
On Fri, Mar 26, 2004 at 09:27:35AM -0800, Doug Evans wrote:
> gdb = 5.2.1
>
> I'm unable to add commands to tbreak breakpoints because gdb first
> deletes the breakpoint and then it looks for any breakpoints
> with commands to run.
>
> The docs say
> "You can give any breakpoint (or watchpoint or catchpoint) a series of
> commands to execute when your program stops due to that breakpoint."
>
> Is this a gdb bug or doc bug?
I'd say gdb bug. Could you try something newer?
>
> ---
> bash$ gcc -g hello.c
> bash$ gdb-5.2.1 ./a.out
> (gdb) tbreak main
> (gdb) commands
> echo foo\n
> end
> (gdb) run
>
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
prev parent reply other threads:[~2004-03-26 17:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-29 15:10 Doug Evans
2004-03-29 16:27 ` Daniel Jacobowitz [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=20040326173038.GA12047@nevyn.them.org \
--to=drow@false.org \
--cc=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