Bug#1003240: mlton: mlton_20210117+dfsg-3 cannot rebuild itself on hppa

2022-01-09 Thread Matthew Fluet
On Fri, Jan 7, 2022 at 3:51 PM Ryan Kavanagh wrote: > Control: tags -1 + confirmed > Control: retitle -1 mlton cannot rebuild itself on hppa or i386 > > On Thu, Jan 06, 2022 at 07:55:00PM +, John David Anglin wrote: > > It fails with a reproducible segmentation fault. > > I can reproduce

Bug#1003240: mlton: mlton_20210117+dfsg-3 cannot rebuild itself on hppa

2022-01-09 Thread Matthew Fluet
Although MLton does understand about running out of memory (when an `mmap` request fails), on recent versions of Linux, I've observed that the OOM killer will sometimes step in before a failing `mmap` request. But, I wouldn't think that that would manifest itself as a seg fault. In any case, I

Bug#1003240: mlton: mlton_20210117+dfsg-3 cannot rebuild itself on hppa

2022-01-07 Thread Ryan Kavanagh
Control: tags -1 + confirmed Control: retitle -1 mlton cannot rebuild itself on hppa or i386 On Thu, Jan 06, 2022 at 07:55:00PM +, John David Anglin wrote: > It fails with a reproducible segmentation fault. I can reproduce this even with the latest upstream HEAD on the hppa porterbox, using

Bug#1003240: mlton: mlton_20210117+dfsg-3 cannot rebuild itself on hppa

2022-01-07 Thread John David Anglin
Don't know about amd64 or x86. I tried adding "-codegen c" to MLTON_FLAGS but it didn't make any difference. Gdb generates full backtrace with core file.  Thus, in theory, it should be possible to debug.  But without symbols, it's hard to tell what's going on. The fault outside the chroot is

Bug#1003240: mlton: mlton_20210117+dfsg-3 cannot rebuild itself on hppa

2022-01-06 Thread Henry Cejtin
ssume that it isn't reproducible on AMD, right? Or better, x86 (32 bit)? One thing to try, under either of these, would be compiling stuff with -codegen c or, compiling the compiler with that. The idea is that the HPPA stuff must use the C compiler back end. On Thu, Jan 6, 2022 at 3:24 PM

Bug#1003240: mlton: mlton_20210117+dfsg-3 cannot rebuild itself on hppa

2022-01-06 Thread John David Anglin
Same issue with Linux overcommit turned off.  The machine is not running out of memory and there is lots of swap (40G). Don't really know what's causing segfault. On 2022-01-06 3:27 p.m., Henry Cejtin wrote: MLton understands about running out of memory, so it shouldn't just segfault. If it

Bug#1003240: mlton: mlton_20210117+dfsg-3 cannot rebuild itself on hppa

2022-01-06 Thread John David Anglin
How do I do that? On 2022-01-06 3:27 p.m., Henry Cejtin wrote: MLton understands about running out of memory, so it shouldn't just segfault. If it isn't too hard, could you try it with Linux overcommit turned off? On Thu, Jan 6, 2022 at 1:57 PM John David Anglin wrote: Source: mlton Version:

Bug#1003240: mlton: mlton_20210117+dfsg-3 cannot rebuild itself on hppa

2022-01-06 Thread Henry Cejtin
MLton understands about running out of memory, so it shouldn't just segfault. If it isn't too hard, could you try it with Linux overcommit turned off? On Thu, Jan 6, 2022 at 1:57 PM John David Anglin wrote: > > Source: mlton > Version: 20130715-3 > Severity: normal > > Dear Maintainer, > >

Bug#1003240: mlton: mlton_20210117+dfsg-3 cannot rebuild itself on hppa

2022-01-06 Thread John David Anglin
Source: mlton Version: 20130715-3 Severity: normal Dear Maintainer, Because of dependency problems mlton_20210117+dfsg-3 had to built manually on hppa. However, it seems mlton_20210117+dfsg-3 cannot rebuild itself on hppa. See log: