Very Computer

by **Bart Smaalde** » Fri, 27 Oct 1995 04:00:00

I'm loathe to figure out the stabs format the compiler folks use;
it's pretty groaty. The gdb folks have grokked this so it is possible;
just not very enticing :-).

>> >I would like to be able to print a function call stack trace
>> >in C code similar to the way dbx does when you do a 'where'
>> >on a core file.

>> This works on Solaris 2.4 and higher (sparc, x86 and PPC):

>> /*
>> walks up call stack, printing library:routine+offset for each routine
>> */

>[snip]

>Thanks very much for that gem - I just tried it out.

>Is it possible to make it pick up the compiler's -g information
>(if present) so than not only public symbols, but static functions
>could also be identified (other than as an offset from the last
>public function)? I just had a look through some answerbooks,
>but I could find almost no mention of the ELF .debug section format
>(if that's the right thing to be looking for anyway).

>--

---
Bart Smaalders OS Performance SunSoft

http://playground.sun.com/~barts 2550 Garcia Ave
Mt View, CA 94043-1100

by **Sinan Kara** » Fri, 27 Oct 1995 04:00:00

Actually, I grokked it a while back. The only thing I
have not figured out completely yet how to edit it so
that I can export the same symbol as "C", "FORTRAN" and
"PASCAL" , but am working on it.....

I know how to export Fortran common stuff as "C"
variables and I can fool the "ld" linker.
However I have not been able to fool the de* yet....

Sinan

PS: see another post I just made. That program was written
by someone else that I helped a while back. Unfortunately
I do not remember his name to give him proper credit.

--
Redistribution by Microsoft Network is prohibited.

Very Computer

In C, how to print stack trace like db

In C, how to print stack trace like db

In C, how to print stack trace like db