Displaying 3 results from an estimated 3 matches for "exitearly".
2017 Oct 24
3
lld: sigbus error handling
...in LLD
> itself and translating it into a proper error code or message, this would
> be reasonable.
>
Signal handlers and signal masks are inherently process-wide, so there's no
way to encapsulate them to lld functions. So my plan is to change the name
of lld::{coff,elf}::link's `ExitEarly` parameter to `IsStandalone`, and we
(not only call exit(2) but also) set a signal handler only when the
argument is true. Since library users pass false to the parameter, it
shouldn't change the behavior of lld for the library use case.
On Mon, Oct 23, 2017 at 6:21 PM, Rui Ueyama via llvm-dev...
2017 Oct 24
3
lld: sigbus error handling
...r error code or message, this would
>>> be reasonable.
>>>
>>
>> Signal handlers and signal masks are inherently process-wide, so there's
>> no way to encapsulate them to lld functions. So my plan is to change the
>> name of lld::{coff,elf}::link's `ExitEarly` parameter to `IsStandalone`,
>> and we (not only call exit(2) but also) set a signal handler only when the
>> argument is true. Since library users pass false to the parameter, it
>> shouldn't change the behavior of lld for the library use case.
>>
>
> This sounds...
2017 Oct 23
8
lld: sigbus error handling
If your system does not support fallocate(2), we use ftruncate(2) to create
an output file. fallocate(2) succeeds even if your disk have less space
than the requested size, because it creates a sparse file. If you mmap such
sparse file, you'll receive a SIGBUS when the disk actually becomes full.
So, lld can die suddenly with SIGBUS when your disk becomes full, and
currently we are not doing