Subject: -current brokenness with dynamic executables
To: None <port-pmax@netbsd.org>
From: Simon Burge <simonb@telstra.com.au>
List: current-users
Date: 01/05/1999 15:24:58
[[ cross posted in case it's more than a pmax issue ]]
I just compiled and booted a -current GENERIC kernel with sources about
24 hours old, and all dynamic executables fail immediately. This is
with a -current userland of about December 8 last year vintage.
Here's the tail end of a ktrace for "grep" that fails with the new kernel:
18 ktrace CALL execve(0x7ffff808,0x7ffffce0,0x7ffffce8)
18 ktrace NAMI "/usr/bin/grep"
18 ktrace NAMI "/usr/libexec/ld.elf_so"
18 grep EMUL "netbsd"
18 grep RET execve JUSTRETURN
18 grep PSIG SIGSEGV SIG_DFL
18 grep NAMI "grep.core"
and for an normal "grep" on my December 8 kernel:
205 ktrace CALL execve(0x7ffff170,0x7ffff640,0x7ffff648)
205 ktrace NAMI "/usr/bin/grep"
205 ktrace NAMI "/usr/libexec/ld.elf_so"
205 grep EMUL "netbsd"
205 grep RET execve JUSTRETURN
205 grep CALL __sysctl(0x7ffff4e4,0x2,0x5ffeb090,0x7ffff4ec,0,0)
205 grep RET __sysctl 0
205 grep CALL mmap(0,0x8000,0x3,0x1004,0xffffffff,0,0,0)
205 grep RET mmap 537030656/0x20027000
... and so on ...
I'm still getting over holidays and catching up on mail. Did any signal
stuff change recently (the PSIG in the first ktrace)? If I get no
leads, I'll look at this further tomorrow...
Simon.