Re: "tbreak" and "commands" commands...

["William A. Gatliff" <bgat at billgatliff dot com>]

Joel:


Does it work with "break" instead of "tbreak"?  I've never tried it
with tbreak, but "break" works in 5.1--- I use it a lot.

b.g.

On Fri, Jul 26, 2002 at 11:54:06AM -0700, Joel Brobecker wrote:
> Hello,
> 
> According to the documentation, we should be able to associate a list
> of commands to execute when the inferior hits a temporary breakpoint.
> It currently does not seem to be the case. Is there a limitation in this
> area, or is this a regression (in which case I'll be happy to work on
> this)?
> 
> Here is a small copy of a simple session:
> <<
> GNU gdb 2002-07-26-cvs
> [snip]
> This GDB was configured as "i686-pc-linux-gnu"...
> (gdb) tbreak test.c:8
> Breakpoint 1 at 0x804854f: file test.c, line 8.
> (gdb) command
> Type commands for when breakpoint 1 is hit, one per line.
> End with a line saying just "end".
> >printf "+++ breakpoint hit\n"
> >continue
> >end
> (gdb) run
> Starting program: /nfs/paris/paris.a/brobecke/act/report/gdb/B726-014__cont_abbrev/test.bonn 
> main () at test.c:8
> 8           printf ("Hello world.\n");
> (gdb) 
> >>
> 
> As you see, the inferior stopped at breakpoint 1, but the command list was
> not executed...
> 
> Thanks,
> -- 
> Joel

-- 
Bill Gatliff
bgat@billgatliff.com