In c or c++ While debugging a core dump,i.e., if we are left with a coredump file and try to debug using that core file is there a way we can see the last few lines of code before the dump occured.the stack trace only shows the function call. For eg:during debugging a running process in dbx or gdb list command list Display lines of a source file will give the part of the code currently under execution.in the same way do we have the option while looking into a core dump? I am working on solaris mdb. The list command in gdb should provide details of source code line numbers and the corresponding source listing from a core file if: • The executable was compiled with debug symbols enabled (eg. -g in gcc and g++) • A non-stripped version of the executable is available (ie. Has not had the debug information removed by running strip) • The debugger is able to find the relevant source files The debugger should still be able to provide file and line numbers even if it is unable to find the source files as the line number information forms a part of the debug symbols. This information should be available through the bt (backtrace) command, as well as the info symbol command.
A Guide to debug for dbx Users. File name of the core file to be debugged -r: N/A: Executes the object file and exits the debugger only if no error occurs -x. How to attach to a process using DBX. In some situations a process will not generate a core file. If the dbx debug executable exists on the system. Fbi Dna Auditor Training Program more.
Note that even if the core file was generated from a stripped executable, as long as you have access to a non-stripped version you can load that in gdb as well as specifying the core file. Take a look at chapter 13 and 15 of the to assist in giving gdb access to your source files.