From 4c16e1ab6a6c696785f9915647f8fcef6bda5093 Mon Sep 17 00:00:00 2001 From: Nick Clifton Date: Tue, 21 Feb 2023 11:15:52 +0000 Subject: [PATCH] Update the description of the bfd_fill_in_gnu_debuglink_section function --- bfd/ChangeLog | 5 +++++ bfd/opncls.c | 11 +++-------- 2 files changed, 8 insertions(+), 8 deletions(-) diff --git a/bfd/ChangeLog b/bfd/ChangeLog index 357b9b588e4..b8987211dd4 100644 --- a/bfd/ChangeLog +++ b/bfd/ChangeLog @@ -1,3 +1,8 @@ +2023-02-21 Nick Clifton + + * opncls.c (bfd_fill_in_gnu_debuglink_section): Update + description. + 2023-02-17 Tom Tromey * doc/doc.str (FUNCTION): Call func. diff --git a/bfd/opncls.c b/bfd/opncls.c index 4d0ca48ee78..5dacad9b7d4 100644 --- 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. <> is returned if all is ok. Otherwise <> 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) { -- 2.30.2