bfd_check_format: ignore errors from coff_real_object_p

[deliverable/binutils-gdb.git] / bfd / corefile.c

diff --git a/bfd/corefile.c b/bfd/corefile.c
index 1b87e86bc21df5da075dcc1cb168ed2aa0977409..0ce23de46257a7c7bf9ba4295b50eaea08080ddc 100644 (file)
--- a/bfd/corefile.c
+++ b/bfd/corefile.c
@@ -1,5 +1,5 @@
 /* Core file generic interface routines for BFD.
 /* Core file generic interface routines for BFD.

-   Copyright (C) 1990-2014 Free Software Foundation, Inc.
+   Copyright (C) 1990-2020 Free Software Foundation, Inc.

    Written by Cygnus Support.
 
    This file is part of BFD, the Binary File Descriptor library.
    Written by Cygnus Support.
 
    This file is part of BFD, the Binary File Descriptor library.


@@ -135,31 +135,31 @@ core_file_matches_executable_p (bfd *core_bfd, bfd *exec_bfd)
 
 /*
 FUNCTION
 
 /*
 FUNCTION

-        generic_core_file_matches_executable_p
+       generic_core_file_matches_executable_p

 
 SYNOPSIS
 
 SYNOPSIS

-        bfd_boolean generic_core_file_matches_executable_p
-          (bfd *core_bfd, bfd *exec_bfd);
+       bfd_boolean generic_core_file_matches_executable_p
+         (bfd *core_bfd, bfd *exec_bfd);

 
 DESCRIPTION
 
 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.
+       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.

 */
 
 bfd_boolean
 generic_core_file_matches_executable_p (bfd *core_bfd, bfd *exec_bfd)
 {
 */
 
 bfd_boolean
 generic_core_file_matches_executable_p (bfd *core_bfd, bfd *exec_bfd)
 {

-  char *exec;
-  char *core;
-  char *last_slash;
+  const char *exec;
+  const char *core;
+  const char *last_slash;

 
   if (exec_bfd == NULL || core_bfd == NULL)
     return TRUE;
 
   if (exec_bfd == NULL || core_bfd == NULL)
     return TRUE;


@@ -169,7 +169,7 @@ generic_core_file_matches_executable_p (bfd *core_bfd, bfd *exec_bfd)
      non-const char *.  In this case, the assignement does not lead to
      breaking the const, as we're only reading the string.  */
 
      non-const char *.  In this case, the assignement does not lead to
      breaking the const, as we're only reading the string.  */
 

-  core = (char *) bfd_core_file_failing_command (core_bfd);
+  core = bfd_core_file_failing_command (core_bfd);

   if (core == NULL)
     return TRUE;
 
   if (core == NULL)
     return TRUE;