Re: hook-stop sees dummy frames, bug or feature?

[Joel Brobecker <brobecker@adacore.com>]

FWIW, I think that the gdb-6.8 behavior:

>  >gdb-6.8 ./gdb
[...]
>  (top-gdb) p malloc (0)
>  #0  <function called from gdb>          <<<<<< "frame" in hook-stop
>  Current language:  auto; currently asm
>  $1 = 11407376                           <<<<<< 'malloc (0)' result
>  Current language:  auto; currently c
>  (top-gdb) frame                         <<<<<< "frame" again shows something else.
>  #0  main (argc=1, argv=0x7ffff00043f8) at ../../src/gdb/gdb.c:28
>  28        memset (&args, 0, sizeof args);

To be less useful than the current CVS:

>  (top-gdb) p malloc (0)
>  #0  main (argc=1, argv=0x7fffffffe408) at ../../src/gdb/gdb.c:28   <<< "frame" in hook-stop.
>  28        memset (&args, 0, sizeof args);
>  $1 = 11407440
>  (top-gdb)

So I like the new behavior a little better.

-- 
Joel