[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug ld/28037] Semireproducible bug

From: nickc at redhat dot com
Subject: [Bug ld/28037] Semireproducible bug
Date: Thu, 01 Jul 2021 13:55:37 +0000


Nick Clifton <nickc at redhat dot com> changed:

           What    |Removed                     |Added
                 CC|                            |nickc at redhat dot com

--- Comment #1 from Nick Clifton <nickc at redhat dot com> ---
(In reply to Volker WeiƟmann from comment #0)
Hi Volker,

> sometimes (1 in 20 times maybe) 

A bug that does not happemn reliably is very hard to track down.  The most
common cause for such bugs are memory issues - either using uninitialised
memory or using freed memory or the like.  Are you able to run your tests
in an environment with additional memory debugging enabled ?  For example
by using valgrind, or setting the MALLOC_CHECK_ environment variable ?

Another possibility is a hardware problem.  If you have a faulty memory 
bank for example then that might explain the problem.  Are you able to
reproduce the failure on another machine ?

> = note: /usr/local/bin/ld: BFD (GNU Binutils)

This is not an official binutils release.  Nor is it the latest release.

Are you able to run your tests using the newest binutils (2.36.1) ?

> internal
> error, aborting at merge.c:939 in _bfd_merged_section_offset

This error suggests that the issue might be due to uninitialised memory.
There is a comment just before line 939 which says:

      /* This should only happen if somebody points into the padding
         after a NUL character but before next entity.  */
      if (*p)
        abort ();

So the implication is that 'p' is pointing into "padding" of some kind
and padding can often contain random bytes.  Still without more information
to go on, it is hard to make any further progress.


You are receiving this mail because:
You are on the CC list for the bug.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]