[Bug ld/28037] Semireproducible bug
https://sourceware.org/bugzilla/show_bug.cgi?id=28037 Volker Weißmann changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |NOTABUG --- Comment #4 from Volker Weißmann --- Probably NOTABUG, my installation was faulty: https://github.com/rust-lang/rust/issues/86734#issuecomment-1493337645 -- You are receiving this mail because: You are on the CC list for the bug.
[Bug ld/28037] Semireproducible bug
https://sourceware.org/bugzilla/show_bug.cgi?id=28037 --- Comment #3 from Volker Weißmann --- (In reply to Nick Clifton from comment #1) > (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) 2.34.50.20200328 > > 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. > > Cheers > Nick First of all sorry, that I only see your comment two years later. Second, this bug probably just occured because my installation was broken: https://github.com/rust-lang/rust/issues/86734#issuecomment-1493337645 -- You are receiving this mail because: You are on the CC list for the bug.
[Bug ld/28037] Semireproducible bug
https://sourceware.org/bugzilla/show_bug.cgi?id=28037 Josh Stone changed: What|Removed |Added CC||jistone at redhat dot com --- Comment #2 from Josh Stone --- There's a similar report using Ubuntu's 2.38 here: https://github.com/rust-lang/rust/issues/111956 (also "non-repeatable", and no code provided yet.) -- You are receiving this mail because: You are on the CC list for the bug.
[Bug ld/28037] Semireproducible bug
https://sourceware.org/bugzilla/show_bug.cgi?id=28037 Nick Clifton changed: What|Removed |Added CC||nickc at redhat dot com --- Comment #1 from Nick Clifton --- (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) 2.34.50.20200328 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. Cheers Nick -- You are receiving this mail because: You are on the CC list for the bug.
