[Bug ld/23906] LD Bug : Undocumented exit status 253

2018-11-22 Thread sch...@linux-m68k.org
https://sourceware.org/bugzilla/show_bug.cgi?id=23906

Andreas Schwab  changed:

   What|Removed |Added

   Severity|critical|normal

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
bug-binutils mailing list
bug-binutils@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-binutils


[Bug ld/23906] LD Bug : Undocumented exit status 253

2018-11-22 Thread nickc at redhat dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=23906

Nick Clifton  changed:

   What|Removed |Added

 CC||nickc at redhat dot com

--- Comment #1 from Nick Clifton  ---
Hi David,

> How can I assist you in isolating this issue? 

To me this sounds like a resource issue.  Ie I suspect that the linker is
running out of memory, or maybe stack space, and crashing.

Things that you can try:

  * Use a newer version of the linker.  The latest release is 2.31.1.

  * Try running the linker with its memory overhead reduction options:
--no-keep-memory and --reduce-memory-overhead

You may also find it useful to add the --print-memory-usage option
to see if this produces any useful output.

  * Try using the gold linker instead of the bfd based linker.

  * Try linking on a machine with more resources available.  Or, if
possible, a machine running a different OS.

  * Try running the linker from inside GDB, so that it might capture
the problem.  In order to obtain the command line for the linker
you can add -Wl,-debug to the g++ command line.

  * See if you can create a reproducible testcase that we can examine
ourselves.  I suspect however that it might be too big to upload,
but it would be worth a try.

Cheers
  Nick

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
bug-binutils mailing list
bug-binutils@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-binutils