[Top][All Lists]

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

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

From: davidledger at live dot com.au
Subject: [Bug ld/23906] LD Bug : Undocumented exit status 253
Date: Thu, 13 Dec 2018 10:27:41 +0000


--- Comment #24 from David Ledger <davidledger at live dot com.au> ---
Should I raise the bug with them or does your team do that?

David Ledger - Electronics Design Engineer
 Skype: david.j.ledger

From: tnfchris at sourceware dot org <address@hidden>
Sent: Thursday, December 13, 2018 9:17:10 PM
To: address@hidden
Subject: [Bug ld/23906] LD Bug : Undocumented exit status 253


--- Comment #23 from Tamar Christina <tnfchris at sourceware dot org> ---
> Anyway to get it to work within windows, I tried EditBin.exe but it didn’t 
> work. I set the reserve stack to 512Mb.

I suspect the reason that isn't working is that setting the reserve stack just
reserves the virtual memory but doesn't change the committed memory, and so the
OS only has allocated still the original amount.

On windows when the stack is allocated you're not allowed to do it more than a
pagesize at a time. Normally applications emit a  __chkstk_ms call for this but
I can't find any such calls in the ld binary.  Ofcourse it is likely the case
that I can't find it because the binaries have been fully stripped..

You could try using editbin but also specifying the commit size. This will only
work if you actually have enough physical memory to back the requested size.
But I believe it should work then too.

> How did you get ld. from GCC9 to work for this target?

The LD was actually the same, it's the compiler that generated less symbols.
But it's not a clean migration as GCC9 no longer allows SP to be clobbered via
inline assembly. So I had to comment out some parts of the code.

A bug needs to be raised against libiberty in GCC for a proper fix.

You are receiving this mail because:
You reported the bug.

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]