From: Alexander T. <ale...@gm...> - 2012-07-22 20:34:41
|
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 |
From: Mike F. <va...@ge...> - 2012-07-23 00:35:26
Attachments:
signature.asc
|
On Sunday 22 July 2012 16:34:35 Alexander Toresson wrote: > 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? while i'm not a dev, if the patch is clean, i don't see why it wouldn't be merged -mike |