Re: [Dprobes] Stack trace unwindind

[Tom Z. <za...@us...>]

Hello,

There are a few different ways you can get stack traces - in an RPN 
program, you can use the 'log st' instruction to log the current stack
trace information.  Alternatively, you can have stack trace information
logged automatically whenever the RPN program raies an exception, by
specifying 'autostacktrace=yes' in your RPN file.

In a dpcc program, you only get a stack trace if the program raised an
exception that was never eventually caught, the assumption being that
there's not much need to print a stack trace unless there was a program-
stopping exception.  If that's not a good assumption, we can add a
built-in function that's basically a simple wrapper around the 'log st'
RPN instruction.

Also, the 'tailprint' script in the base dpcc directory can do a 
minimalistic parse of the stack trace information, but it doesn't know
anything about dpcc program symbols, so would have to be manually 
matched up with the RPN file generated by dpcc, then again to the 
C program.  Clearly this would be quite tedious - having user-readable
stack trace info is on our TODO list.

-- 
Regards,

Tom Zanussi <za...@us...>
IBM Linux Technology Center/RAS

Florin Cremenescu writes:
 > 
 >  Hello !
 > 
 >  
 >  I am a new user of DProbes (in fact, I hope I'll be,
 > because until now I have not even compiled it...). 
 > 
 >  While reading the docs of DProbes and dppc, I
 > wondered if there is a built-in function which logs
 > the stack trace of a program. It would be very useful.
 > 
 > 
 >  Thanks,
 >    Florin Cremenescu
 > 
 > 
 > __________________________________________________
 > Do You Yahoo!?
 > Yahoo! Health - Feel better, live better
 > http://health.yahoo.com
 > _______________________________________________
 > Dprobes mailing list
 > Dp...@ww...
 > http://www-124.ibm.com/developerworks/oss/mailman/listinfo/dprobes
 >