🚀 go-pugleaf

I'm writing a profiling tool and am looking for documentation about the machine
code layout of GCC compiled programs.  Basically, given an interrupted program,
I want to use ptrace() to walk the call stack and report the functions invoked
(from main() or start() up to the point at which the interrupt occurred).

Without giving too many details away, I'm writing this for my IBM RS/6000
system at work.  However, I'm doing it on my own time and would like to create
a version that would work for 80x86 platforms running Linux (which I run at
home) that I could CopyLeft and distribute on the net.  I used the IBM Assembly
Language reference to complete most of the port at work (for programs compiled
under IBM's compilers).  However, I can't find any documentation to describe
the process I need to use under Linux and GCC.  I tried looking through GDB
source, but 15Mb is a lot to wade through.  I need to at least pick up the
function name, the program counter when the interrupt occurred, and the
instruction address of the last instruction in the function executing when the
interrupt occurred.  If possible, I'd also like to demangle C++ names on the
fly, extract line numbers, and the parameter list.

If someone could point me in the appropriate direction, I'd be very grateful.
Pointers to documentation and/or source code (i.e. lines xxx-yyy in file aaa
of gdb) would be great!

Thanks and regards,
John Croix
IBM - Austin