While debugging a program in GDB, I get an unexpected "program exited normally". So I'm wondering if is there a way to find out from where (which line) the program exited.
Program is multi-threaded, if that matters.
GDB – how to find out from where program exited
gdb
Related Topic
- Gdb error “Program exited normally”
- GDB: Ctrl+C doesn’t interrupt process as it usually does but rather terminates the program
- How to run a program with commandline arguments using GDB within a Bash script
- How to enable reverse debugging on a multi-threaded program
- C++ – How to determine if an object is an instance of certain derived C++ class from a pointer to a base class in GDB
- C++ – “please check gdb is codesigned – see taskgated(8)” – How to get gdb installed with homebrew code signed
Best Answer
You could try the GDB command
break exitto set a breakpoint on the exit(2) library call. If that doesn't get you what you need, maybebreak _exit. You might need to start your program with 'sta' before getting the latter breakpoint to take. In either case, you should then be able to use thewherecommand to get a stack trace showing where you were when the program decided to exit.