🚀 go-pugleaf

Hi,
        When gdb prints out a stack frame, it prints out
        every argument in full form.  There doesn't seem
        to be any way to control the amount of info it
        gives.

        This is real difficult when c++ references are involved,
        'cos the deref_ref parameter in val_print() seems
        to be hard wired as 1 just about everywhere.
        I get some truly fat / possibly infinite
        frame dumps out of this, and no way to find out
        where I am.

        I can hack round this by controlling deref_ref from
        an environment variable.  It would be nice if
        this was settable from gdb, and even better if
	the verbosity of these printouts could be
	controlled.

	Also, is 404828592 bytes a record for core dumps, or
	don't you subscribe to comp.archives.core-dumps :-)

regards,
kb@stl.stc.co.uk	"..am I being chastised as I loll? ..life is good!"