> dd if=/dev/urandom bs=65536 of=/dev/mem
FWIW, secururelevel > 0 fixes this issue. so, perhaps you
can rephrase by including something about correct separation
of privs, since root write-access to /dev/mem is literally
giving it kernel-level privs.
.mrg.
>> It seems so far, from not really paying attention, that there is
>> nothing wrong with ghc but that there is a bug in the kernel.
> Yes of course no userland code should be able to crash the kernel :D
I used to think so. Then it occurred to me that there are various ways
for userland to crash
Committed a workaround to lang/ghc94. I hope it can avoid the panic. You
can remove the workaround simply by deleting lang/ghc94/hacks.mk.
On 2/7/23 12:36 AM, Greg Troxel wrote:
PHO writes:
On 2/6/23 5:27 PM, Nikita Ronja Gillmann wrote:
I encountered this on some version of 10.99.2 and la
PHO writes:
> On 2/6/23 5:27 PM, Nikita Ronja Gillmann wrote:
>> I encountered this on some version of 10.99.2 and last night again on
>> 10.99.2 from Friday morning.
>> This is an obvious blocker for me for making 9.4.4 the default.
>> I propose to either revert to the last version or make the d
PHO transcribed 0.7K bytes:
On 2/6/23 5:27 PM, Nikita Ronja Gillmann wrote:
I encountered this on some version of 10.99.2 and last night again on
10.99.2 from Friday morning.
This is an obvious blocker for me for making 9.4.4 the default.
I propose to either revert to the last version or make th
On 2/6/23 5:27 PM, Nikita Ronja Gillmann wrote:
> I encountered this on some version of 10.99.2 and last night again on
> 10.99.2 from Friday morning.
> This is an obvious blocker for me for making 9.4.4 the default.
> I propose to either revert to the last version or make the default GHC
> versio
I encountered this on some version of 10.99.2 and last night again on
10.99.2 from Friday morning.
This is an obvious blocker for me for making 9.4.4 the default.
I propose to either revert to the last version or make the default GHC
version setable.
PHO transcribed 2.3K bytes:
On 2/6/23 8:54 A
