Guile and GDB

[Ludovic Courtès]

Hello,

"Neil Jerram" <address@hidden> writes:

>     The first kind is that libguile includes the utility functions
>     gdb_print, gdb_eval, etc., and the variable gdb_output.  These have no
>     purpose except for developers to use from GDB when debugging
>     something.  For example, if you have a SCM x and want to know what it
>     is, you can do:
>     
>     (gdb) call gdb_print(x)
>     (gdb) p gdb_output

Actually, it's also meant to be used directly by GDB.  Normally, GDB
should try to display SCM values on its own (using its own copy of
`tags.h' and the corresponding printing procedures) and resort to
calling `gdb_print ()' when it doesn't know how to display a value.

In practice, GDB currently only supports the latter, which makes it
not-so-useful (the same result can be achieved with trivial GDB macros).
See http://sourceware.org/ml/gdb-patches/2007-07/msg00231.html .

Thanks,
Ludo'.