Obtener ayuda en vivo
How to run a backtrace on a core file? After a segfault or process crash you may need to obtain more information. Backtraces can provide more detailed information.
When a core file happens, Tech support will need a back trace of the core file. The machine that the core happens on will have the same libraries and library versions, and when the coredump is analyzed elsewhere the analysis tools can give misleading information or refuse to work at all without the same libraries.
Operating system platforms have different methods of obtaining back trace information. Please refer to vendor for information.
gdb on linux or HPUX: gdb /opt/quest/sbin/vasd /tmp/core.13587
dbx on AIX: dbx /opt/quest/sbin/vasd /path/core
adb on Solaris : adb /opt/quest/sbin/vasd /core
pstack on Solaris: pstack /path/to/core/file/core
The bt and where commands on gdb and dbx tell the debugger to print out a trace of the program stack from the attached core file.
Note: If you are running the trace against vasd and you encounter the message:
".vasd" does not match current program (ignored)
Then use /opt/quest/sbin/.vasd, the actual binary. ( And not vasd, the wrapper script ).
dbx on AIX: dbx /opt/quest/sbin/.vasd /path/core
If a core file is not created, run the command: ulimit -c
If it is set to 0, then you will need to set it to unlimited by running: ulimit -c unlimited
When a program changes its running-as identity, some oses like RedHat don't let it dump core unless you tell it to. Please refer to the following link about this: http://linuxtechres.blogspot.com/2011/09/how-to-enable-core-dump-for-application.html
© 2023 One Identity LLC. ALL RIGHTS RESERVED. Feedback Términos de uso Privacidad Cookie Preference Center