Re: NetBSD-10.0/i386 spurious SIGSEGV

[Emmanuel Dreyfus <manu%netbsd.org@localhost>]

On Sat, Jun 08, 2024 at 10:10:58PM -0400, Mouse wrote:
> Are all the failures in __gettimeofday50?  All in trap-to-the-kernel
> calls?

Here is an example with syslogd

Core was generated by `syslogd'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0xbb0384d7 in writev () from /lib/libc.so.12
(gdb) bt
#0  0xbb0384d7 in writev () from /lib/libc.so.12
#1  0x0000a252 in fprintlog (f=0xbaf44c00, passedbuffer=<optimized out>, 
    qentry=0x0) at /usr/src/usr.sbin/syslogd/syslogd.c:2474
#2  0x0000b2b6 in logmsg (buffer=0xbaf295c0)
    at /usr/src/usr.sbin/syslogd/syslogd.c:2012
(...)

   0xbb0384d0 <writev>:	mov    $0x79,%eax
   0xbb0384d5 <writev+5>:	int    $0x80
=> 0xbb0384d7 <writev+7>:	jb     0xbb0384da <writev+10>
   0xbb0384d9 <writev+9>:	ret    


-- 
Emmanuel Dreyfus
manu%netbsd.org@localhost