Merge ^vendor/binutils/dist@214082 into contrib/binutils.

1 files changed, 22 insertions, 0 deletions

diff --git a/contrib/binutils/bfd/doc/core.texi b/contrib/binutils/bfd/doc/core.texi
index e45759cf647b..1f09445ef76d 100644
--- a/contrib/binutils/bfd/doc/core.texi
+++ b/contrib/binutils/bfd/doc/core.texi
@@ -1,6 +1,9 @@
 @section Core files
 
 
+@subsection Core file functions
+
+
 @strong{Description}@*
 These are functions pertaining to core files.
 
@@ -36,3 +39,22 @@ Return @code{TRUE} if the core file attached to @var{core_bfd}
 was generated by a run of the executable file attached to
 @var{exec_bfd}, @code{FALSE} otherwise.
 
+@findex generic_core_file_matches_executable_p
+@subsubsection @code{generic_core_file_matches_executable_p}
+@strong{Synopsis}
+@example
+bfd_boolean generic_core_file_matches_executable_p
+   (bfd *core_bfd, bfd *exec_bfd);
+@end example
+@strong{Description}@*
+Return TRUE if the core file attached to @var{core_bfd}
+was generated by a run of the executable file attached
+to @var{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.
+