Re: malloc-related SIGSEGV when cross-building i386 on NetBSD-10.0/amd64

2024-04-16 Thread Jörg Sonnenberger
On Tuesday, April 16, 2024 3:32:45 AM CEST Taylor R Campbell wrote: > It looks like somehow the thread's tls pointer (%gs) is null, but my > guess is that this happens only sometimes, e.g. during involuntary > kernel context switches that involve saving and restoring a trap > frame, which is why it

Re: malloc-related SIGSEGV when cross-building i386 on NetBSD-10.0/amd64

2024-04-16 Thread Emmanuel Dreyfus
On Tue, Apr 16, 2024 at 08:44:32AM +0200, Jörg Sonnenberger wrote: > Double check with printf or so first please, that this isn't just a gdb > artifact please. Segment registers on amd64 are weird. (gdb) printf "0x%x\n", $gs 0x0 -- Emmanuel Dreyfus m...@netbsd.org

Re: malloc-related SIGSEGV when cross-building i386 on NetBSD-10.0/amd64

2024-04-16 Thread Emmanuel Dreyfus
On Tue, Apr 16, 2024 at 01:32:45AM +, Taylor R Campbell wrote: > Great, thanks! Can you file a PR with this information so we can use > it to track fixes and pullups? kern/58158 -- Emmanuel Dreyfus m...@netbsd.org