backtrace

I am using backtrace to get the information from where the exception is thrown. In the constructor of my exception, I am storing the backtrace in a std::string, and in the catch block for exceptions of this type, I am printing this backtrace. But I was wondering, is it possible to somehow get the same backtrace in the catch block for other exception types? I don't think so. When executons stops in catch block the stack is unwound, and all that has happened before is not in stack anymore. You might be interested in a Boost library under development: Portable Backtrace . Example: #include <boost

I'm writing this for Android (ARM only), but I believe the principle is the same for generic Linux as well. I'm trying to capture the stack trace from within the signal handler, so that I can log it when my app crashes. This is what I've come up with using <unwind.h> . Initialization: struct sigaction signalhandlerDescriptor; memset(&signalhandlerDescriptor, 0, sizeof(signalhandlerDescriptor)); signalhandlerDescriptor.sa_flags = SA_SIGINFO; signalhandlerDescriptor._u._sa_sigaction = signalHandler; sigaction(SIGSEGV, &signalhandlerDescriptor, 0); The code itself: struct BacktraceState { void**

Alright, second question on SO in one day. Looks like Windows programming makes me happy... : S I'm currently trying to get the function call stack on a Win32 executable. This morning, I've also asked a question about this: Win32 - Backtrace from C code Now, I'm pretty sure that the StackWalk64 function is the key for this. I've read some articles on how to use it, as well as the MS documentation. It actually displays frames on my test program, so it kinda work... The problem is that I'm not able to retrieve the symbol name from the stack informations. I'm using the SymGetSymFromAddr64

In Linux, to get a backtrace you can use backtrace() library call, but it only returns backtrace of current thread. Is there any way to get a backtrace of some other thread, assuming I know it's TID (or pthread_t) and I can guarantee it sleeps? It seems that libunwind (http://www.nongnu.org/libunwind/) project can help. The problem is that it is not supported by CentOS, so I prefer not to use it. Any other ideas? Thanks. Signal Handling with the help of backtrace can solve your purpose. I mean if you have a PID of the Thread, you can raise a signal for that thread. and in the handler you can

The Linux specific backtrace() and backtrace_symbols() allows you to produce a call trace of the program. However, it only prints function addresses, not their names for my program. How can I make them print the function names as well ? I've tried compiling the program with -g as well as -ggdb . The test case below just prints this: BACKTRACE ------------ ./a.out() [0x8048616] ./a.out() [0x8048623] /lib/libc.so.6(__libc_start_main+0xf3) [0x4a937413] ./a.out() [0x8048421] ---------------------- I'd want the first 2 items to also show the function names, foo and main Code: #include <execinfo.h>

Trying to debug PHP using its default current-line-only error messages is horrible. How can I get PHP to produce a backtrace (stack trace) when errors are produced? Xdebug prints a backtrace table on errors, and you don't have to write any PHP code to implement it. Downside is you have to install it as a PHP extension. My script for installing an error handler that produces a backtrace: <?php function process_error_backtrace($errno, $errstr, $errfile, $errline, $errcontext) { if(!(error_reporting() & $errno)) return; switch($errno) { case E_WARNING : case E_USER_WARNING : case E_STRICT : case

I'm currently looking for a way to get backtrace information under Windows, from C code (no C++). I'm building a cross-platform C library, with reference-counting memory management. It also have an integrated memory debugger that provides informations about memory mistakes ( XEOS C Foundation Library ). When a fault occurs, the debugger is launched, providing information about the fault, and the memory record involved. On Linux or Mac OS X, I can look for execinfo.h in order to use the backtrace function, so I can display additional infos about the memory fault. I'm looking for the same thing