Re: [PATCH] Fix variable objects for references to pointers

[Daniel Jacobowitz <drow@false.org>]

On Thu, Jan 04, 2007 at 10:41:56PM +1300, Nick Roberts wrote:
> Something like below?
> 
> set end_of_proc [gdb_get_line_number "return 99;"]
> send_gdb "-break-insert $end_of_proc\n"
> mi_continue_to ".*" reference_to_pointer  "" ".*${srcfile}" $end_of_proc \
>     "continue to return 99"
> 
> 
> Other tests seem to use mi_gdb_test for -break-insert but I'm not interested in
> the result and mi_continue presumably sifts through the output until it reaches
> something it recognises.  I'm also not that interested in the breakpoint
> number so I've used a wildcard for future-proofing.

Let's hold off on this for a little bit and use Vlad's new stuff.

The above is better, except you really should use mi_gdb_test even if
you don't care about the result.  It's important that every time you
send a command to GDB that produces output, you also consume that
output.  Otherwise, you can get this behavior:

-> -break-insert $end_of_proc
-> -exec-continue
<- ^done
<- (gdb)
  Oops, that looks like the default case, something must have gone
  wrong with -exec-continue.  FAIL.
<- ^running
<- ^stopped
<- (gdb)

-- 
Daniel Jacobowitz
CodeSourcery