Update the description of the bfd_fill_in_gnu_debuglink_section function

diff --git a/bfd/ChangeLog b/bfd/ChangeLog
index 357b9b588e43d166bba41e270be3922db22e8870..b8987211dd4c5c25e362c4e9ec7fd5fa20bfeaf3 100644 (file)
--- a/bfd/ChangeLog
+++ b/bfd/ChangeLog
@@ -1,3 +1,8 @@
+2023-02-21  Nick Clifton  <nickc@redhat.com>
+
+       * opncls.c (bfd_fill_in_gnu_debuglink_section): Update
+       description.
+
 2023-02-17  Tom Tromey  <tom@tromey.com>
 
        * doc/doc.str (FUNCTION): Call func.

diff --git a/bfd/opncls.c b/bfd/opncls.c
index 4d0ca48ee78209c171f67a13b777ec2a374887a6..5dacad9b7d43df628ced9cf404da08ed01b9393c 100644 (file)
--- a/bfd/opncls.c
+++ b/bfd/opncls.c
@@ -1706,8 +1706,8 @@ SYNOPSIS
 DESCRIPTION
        Takes a @var{BFD} and containing a .gnu_debuglink section @var{SECT}
        and fills in the contents of the section to contain a link to the
-       specified @var{filename}.  The filename should be relative to the
-       current directory.
+       specified @var{filename}.  The filename should be absolute or
+       relative to the current directory.
 
        <<TRUE>> is returned if all is ok.  Otherwise <<FALSE>> is returned
        and bfd_error is set.
@@ -1733,12 +1733,7 @@ bfd_fill_in_gnu_debuglink_section (bfd *abfd,
       return false;
     }
 
-  /* Make sure that we can read the file.
-     XXX - Should we attempt to locate the debug info file using the same
-     algorithm as gdb ?  At the moment, since we are creating the
-     .gnu_debuglink section, we insist upon the user providing us with a
-     correct-for-section-creation-time path, but this need not conform to
-     the gdb location algorithm.  */
+  /* Open the linked file so that we can compute a CRC.  */
   handle = _bfd_real_fopen (filename, FOPEN_RB);
   if (handle == NULL)
     {