Bug 29925 - Unable to reproduce

Bug 29925 - Unable to reproduce

[Deepesh Rajan]

[-- Attachment #1: Type: text/plain, Size: 2399 bytes --]

Hi All,

From the bug 29925 from the following link
https://sourceware.org/bugzilla/show_bug.cgi?id=29925

I was trying to reproduce the issue on binutils 2.36 .



steps for reproducing the issue:

   1. git clone git://sourceware.org/git/binutils-gdb.git
   2. git checkout binutils_2_36
   3. CC="clang -fsanitize=address" CXX="clang++ -fsanitize=address"
   ./configure --disable-shared && make -j$(nproc)
   4. ./binutils/nm-new -A -a -l -S -s --special-syms --synthetic
   --with-symbol-versions -D poc



*but while doing make getting the below errors :*



*==489551==WARNING: invalid path to external symbolizer!*

*==489551==WARNING: Failed to use and restart external symbolizer!*

*=================================================================*

*==489551==ERROR: LeakSanitizer: detected memory leaks*

*==489597==WARNING: invalid path to external symbolizer!*

*==489597==WARNING: Failed to use and restart external symbolizer!*

*=================================================================*

*==489600==WARNING: invalid path to external symbolizer!*

*==489597==ERROR: LeakSanitizer: detected memory leaks*

*==489600==WARNING: Failed to use and restart external symbolizer!*

*=================================================================*

*Direct leak of 24 byte(s) in 1 object(s) allocated from:*

*==489600==ERROR: LeakSanitizer: detected memory leaks*

*==489602==WARNING: invalid path to external symbolizer!*

*Direct leak of 24 byte(s) in 1 object(s) allocated from:*

*==489602==WARNING: Failed to use and restart external symbolizer!*

*=================================================================*

*==489602==ERROR: LeakSanitizer: detected memory leaks*



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.

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

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

4. The bug Target Milestone 2.40, says fixed in 2.40 but we could still
reproduce the issue on 2.40 (we’ve checked the fix patch is present in
sources) and could not reproduce in 2.42. In which version the issue is
fixed?



Thanks in advance.

Regards,
Deepesh

Re: Bug 29925 - Unable to reproduce

[Nick Clifton]

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