Hi Jan.
I just dug around in samba source codes (I saw lot of backtrace output in logs) and I found this:
http://www.gnu.org/software/libc/manual/html_node/Backtraces.html
Also: http://www.nongnu.org/libunwind/man/libunwind(3).html I'm not sure if libunwind is right for you.
Have nice day. Robin Hack
On Mon, Jul 14, 2014 at 09:49:48AM +0200, Jan Synacek wrote:
"Frank Ch. Eigler" fche@redhat.com writes:
jsynacek wrote:
[...] I suggest that all the providers (I'm now mainly concerned about openlmi-providers) have a common, unified tracing facility. We should be able to turn it on as the lowest logging level and it should trace entrance/exit of all functions. This would make debugging and pinpointing failures much easier. [...]
You might find on-demand dynamic tracing with a tool such as perf or systemtap can do this particular job, without manual instrumentation. (If you do wish to compile in tracing code, I'd recommend KISS; maybe consider systemtap <sys/sdt.h> markers that gdb can trace too.)
- FChE
I'll try those locally, thanks!
In my original post, I should have also mentioned that the goal should also be to provide a trace in production -- in my opinion, it's good to see the trace in logs together with everything else if need be.
-- Jan Synacek Software Engineer, Red Hat _______________________________________________ openlmi-devel mailing list openlmi-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/openlmi-devel