🚀 go-pugleaf

In article <9207201607.AA02430@bugs.airs.com> andrew@airs.COM (Andrew Evans) writes:
>I've been using gdb 4.5 on a SCO UNIX machine for some time now.  I've
>been very pleased with the evolution and development of the program.
>I find gdb very useful in my work, and I have an idea which would be
>valuable to me and possibly others as well.
>
>I would like gdb to be able to provide a feature for tracing the
>execution of a running program.  The output could be similar to what
>you get when stepping through a program: print the source line and any
>display expressions.  An abbreviated form printing just function calls
>and their arguments (and return values) would be useful as well.  The
>idea here is to eliminate a lot of return-pressing when tracing
>execution through large portions of code.  I feel that this would make
>pinpointing certain bugs much easier.
>
>Although I'm not familiar with the gdb code, it seems to me that this
>would be fairly simple to do, since most of the functionality already
>exists.  Some way of automating these systems is what's needed.  I'm
>hoping that some gdb expert would be able to do this without much
>effort.
>
>Thanks for a great program, and I hope you find this useful.
>
>---
>Andrew Evans - Infinity Development Systems - Waltham, MA
>

I agree !! I needed exactly the same thing today, and I spent many hours to emulate
a similar facility.

Stefano