Re: rust - volunteers sought...

[Adam <adam%netbsd.org@localhost>]

> However, this to no avail, re-starting the previously failed rust
> build of 1.77.2 (from wip/rust177) still crashes with
> 
>     Running `/usr/pkgsrc/wip/rust177/work/rustc-1.77.2-src/build/bootstrap/debug/rustc /usr/pkgsrc/wip/rust177/work/rustc-1.77.2-src/build/bootstrap/debug/rust
> 
> thread 'rustc' has overflowed its stack
> fatal runtime error: stack overflow
> 
> rustc exited with signal: 6 (SIGABRT) (core dumped)
> Did not run successfully: signal: 6 (SIGABRT) (core dumped)
> LD_LIBRARY_PATH="/usr/pkgsrc/wip/rust177/work/rustc-1.77.2-src/build/aarch64-unknown-netbsd/stage1/lib:/usr/pkgsrc/wip/rust177/work/rustc-1.77.2-src/build/aarch
> -------------
> error: could not compile `rustc_query_system` (lib)
> 
> This makes me wonder if the rust compiler detection of stack
> overflow is faulty, and that this isn't in fact the problem.
> I find it incredible that it actually overflows a 458MB stack.
> 
> The package Makefile already has
> 
> UNLIMIT_RESOURCES+=     cputime stacksize datasize virtualsize
> 
> However, I don't consider myself sufficiently competent to drive
> gdb to decide this hunch, and would appreciate some assistance on
> this point.

Quickly looking at it: bootstrap/debug/rustc is a wrapper for (I guess) an external compiler - the one from binary packages. For 1.77.2 we use 1.76.0. Maybe 1.75.0 might work, but I didn't check that.

By the way, on macOS the stack limit is 65520 kbytes and the build succeeds.

I'll try to investigate more.

Kind regards,
Adam