corefile.texi revision 1.1.1.1
1@section Core files 2 3 4@subsection Core file functions 5 6 7@strong{Description}@* 8These are functions pertaining to core files. 9 10@findex bfd_core_file_failing_command 11@subsubsection @code{bfd_core_file_failing_command} 12@strong{Synopsis} 13@example 14const char *bfd_core_file_failing_command (bfd *abfd); 15@end example 16@strong{Description}@* 17Return a read-only string explaining which program was running 18when it failed and produced the core file @var{abfd}. 19 20@findex bfd_core_file_failing_signal 21@subsubsection @code{bfd_core_file_failing_signal} 22@strong{Synopsis} 23@example 24int bfd_core_file_failing_signal (bfd *abfd); 25@end example 26@strong{Description}@* 27Returns the signal number which caused the core dump which 28generated the file the BFD @var{abfd} is attached to. 29 30@findex bfd_core_file_pid 31@subsubsection @code{bfd_core_file_pid} 32@strong{Synopsis} 33@example 34int bfd_core_file_pid (bfd *abfd); 35@end example 36@strong{Description}@* 37Returns the PID of the process the core dump the BFD 38@var{abfd} is attached to was generated from. 39 40@findex core_file_matches_executable_p 41@subsubsection @code{core_file_matches_executable_p} 42@strong{Synopsis} 43@example 44bool core_file_matches_executable_p 45 (bfd *core_bfd, bfd *exec_bfd); 46@end example 47@strong{Description}@* 48Return @code{TRUE} if the core file attached to @var{core_bfd} 49was generated by a run of the executable file attached to 50@var{exec_bfd}, @code{FALSE} otherwise. 51 52@findex generic_core_file_matches_executable_p 53@subsubsection @code{generic_core_file_matches_executable_p} 54@strong{Synopsis} 55@example 56bool generic_core_file_matches_executable_p 57 (bfd *core_bfd, bfd *exec_bfd); 58@end example 59@strong{Description}@* 60Return TRUE if the core file attached to @var{core_bfd} 61was generated by a run of the executable file attached 62to @var{exec_bfd}. The match is based on executable 63basenames only. 64 65Note: When not able to determine the core file failing 66command or the executable name, we still return TRUE even 67though we're not sure that core file and executable match. 68This is to avoid generating a false warning in situations 69where we really don't know whether they match or not. 70 71