Re: Bug 29925 - Unable to reproduce

[Nick Clifton <nickc@redhat.com>]

Hi Deepesh,

> _but while doing make getting the below errors :_
> 
> /==489551==WARNING: invalid path to external symbolizer!/
> /==489551==WARNING: Failed to use and restart external symbolizer!/

Hmm, this is obviously some kind of issue with the sanitizer.  It may
be related to the fact that the test you are running is using the nm
program to examine a fuzzed input file.


> We’ve not seen the above errors by using the binutils tar file.
> And, the same errors were seen with latest binutils upstream sources.
> 
> 1. Why we are seeing these errors only with upstream git sources.

I *suspect* that it is because the release tarballs disable experimental
and development features.  (See the file bfd/development.sh - it has
different contents for release tarballs vs git sources).  In particular
releases do not define the ENABLE_CHECKING preprocessor define, which
in turn affects how some of the functions defined in bfd/elf-bfd.h work.

> 2. Is this issue applicable for older versions on binutils (2.36)?

Probably.  The code changed by the patch to fix the bug is also present
in the 2.35 sources.  I have not actually checked by building a set of
the binutils using these sources however.


> 3. Is this issue with any specific version of clang (we are using 14.0).

I could not say.  But you might try using a different version of clang,
or gcc instead of clang, and see if anything changes.


> 4. The bug Target Milestone 2.40, says fixed in 2.40 but we could still reproduce the issue on 2.40 

Are you sure ?  I have just checked and my 2.40 build does not show the
problem.  (I checked compiling both with Clang and with gcc).

I checked using both the official 2.40 release tarball and the binutils-2_40-branch
sources from the git repository.  Both work.

I also confirmed that building with the 2.39 sources does create a version
of nm that has the problem.

Cheers
   Nick