These are functions pertaining to core files.
bfd_core_file_failing_command
bfd_core_file_failing_signal
bfd_core_file_pid
core_file_matches_executable_p
generic_core_file_matches_executable_p
bfd_core_file_failing_command
const
char *bfd_core_file_failing_command (bfd *abfd);
¶Return a read-only string explaining which program was running when it failed and produced the core file abfd.
bfd_core_file_failing_signal
int
bfd_core_file_failing_signal (bfd *abfd);
¶Returns the signal number which caused the core dump which generated the file the BFD abfd is attached to.
bfd_core_file_pid
int
bfd_core_file_pid (bfd *abfd);
¶Returns the PID of the process the core dump the BFD abfd is attached to was generated from.
core_file_matches_executable_p
bool
core_file_matches_executable_p (bfd *core_bfd, bfd *exec_bfd);
¶Return TRUE
if the core file attached to core_bfd
was generated by a run of the executable file attached to
exec_bfd, FALSE
otherwise.
generic_core_file_matches_executable_p
bool
generic_core_file_matches_executable_p (bfd *core_bfd, bfd *exec_bfd);
¶Return TRUE if the core file attached to core_bfd was generated by a run of the executable file attached to exec_bfd. The match is based on executable basenames only.
Note: When not able to determine the core file failing command or the executable name, we still return TRUE even though we’re not sure that core file and executable match. This is to avoid generating a false warning in situations where we really don’t know whether they match or not.