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
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
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
> Date: Tue, 16 Apr 2024 00:59:31 +
> From: Emmanuel Dreyfus
>
> Program terminated with signal SIGSEGV, Segmentation fault.
> #0 0xf4bde597 in tsd_fetch_impl (minimal=false, init=true)
> at
> /usr/src/external/bsd/jemalloc/lib/../include/jemalloc/internal/tsd.h:270
> 270 return
On Mon, Apr 15, 2024 at 12:43:47AM +, Taylor R Campbell wrote:
> Can you get a stack trace with debug.tgz installed so we have source
> location for all of this?
Today, as is running the show
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0xf4bde597 in tsd_fetch_impl
> Date: Mon, 15 Apr 2024 00:21:32 +
> From: Emmanuel Dreyfus
>
> I cross-build i386 packages on an amd64 machine, using pkg_comp with
> CFLAHS-m32 in /etc/mk.conf.
>
> That worked well on NetBSD-9 but after upgradint to NetBSD-10.0, I get
> random SIGSEGV. Here are a few backtrace examples:
Hello
I cross-build i386 packages on an amd64 machine, using pkg_comp with
CFLAHS-m32 in /etc/mk.conf.
That worked well on NetBSD-9 but after upgradint to NetBSD-10.0, I get
random SIGSEGV. Here are a few backtrace examples:
In sed:
#0 0xf0d63c00 in je_malloc_tsd_boot0 () from /lib/libc.so.12
