Question

I compile C++ code with MinGW GCC on Windows. I’m currently dealing with a SIGSEGV that occasionally pops up in a multithreaded program, so I can’t really step through the program with GDB like I normally would. I’ve read through program logs but they only gave me an idea as to where the problem happened.

Can I get a stack trace of where the problem occurred? I saw a similar thread here but since I don’t have execinfo.h I cannot use it.

Answer 1

You can run the program with gdb (command r). Where ever it crashes, you will get back to gdb and you can look at the stack trace and variables.

You may want to look at this also, or search for “gdb multithreaded”.