Hello strace developers, A while ago I stumbled upon strace-plus (http://code.google.com/p/strace-plus/) which provides a stack backtrace for every system call. I found this very useful, and was for a while considering packaging it for Debian. However, I realized that it would be much better if this functionality could be merged into strace.
The current version of strace-plus is not fit for merging. For example, libunwind likely needs to be made optional, it needs to use the system libunwind, a command line option to enable stack traces needs to be introduced, the preprocessing program for stack traces might need to be translated to C and included in the strace binary (to avoid a dependency on Python when used, if desirable), and it needs to be adapted to the latest development version of strace. In any case, my big question is: Would a patch to produce a stack trace for every system call be accepted by you, and what requirements would you place upon it? Regards, Alexander Toresson ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Strace-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/strace-devel
