Port-m68k archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: Does anyone use xterm on NetBSD/m68k 7.0?
okuyama%flex.phys.tohoku.ac.jp@localhost (Rin Okuyama) writes:
>On 2015/11/08 17:47, Michael van Elst wrote:
>> That explains the difference. In a few hours I've built 7.99.21 with
>> Xorg and can verify.
>Thank you very much. That's a big help!
NetBSD/amiga 7.99.21, -current userland. xterm starts but no shell,
the xterm apparently has forked and the child is in zombie state:
UID PID PPID CPU PRI NI VSZ RSS WCHAN STAT TTY TIME COMMAND
1000 1769 1915 0 85 0 7352 4520 select S pts/0 0:01.77 xterm
1000 1910 1769 0 0 0 0 0 - Z pts/0 0:00.00 (xterm)
The parent seems to operate normally. Sending a CHLD signal is caught and
then the parent exits cleanly.
2066 1 xterm __select50(0x6, 0x62fa0, 0x62f70, 0, 0) Err#4 EINTR
2066 1 xterm SIGCHLD caught handler=0x3b02c mask=0x0 code=0x0
2066 1 xterm __wait450(0xffffffff, 0, 0, 0) = 1882, -1
2066 1 xterm __wait450(0xffffffff, 0, 0x1, 0) Err#10 ECHILD
2066 1 xterm setcontext(0x1dffe69c) JUSTRETURN
2066 1 xterm read(0x5, 0xe6aa01c, 0x1000) Err#35 EAGAIN
2066 1 xterm recvmsg(0x3, 0x1dffe9a8, 0) Err#35 EAGAIN
2066 1 xterm recvmsg(0x3, 0x1dffe88c, 0) Err#35 EAGAIN
2066 1 xterm recvmsg(0x3, 0x1dffe88c, 0) Err#35 EAGAIN
2066 1 xterm poll(0xe6026c8, 0x1, 0) = 0, 1
2066 1 xterm kill(0xfffff8a6, 0x1) Err#3 ESRCH
2066 1 xterm ioctl(0x5, TIOCFLUSH, 0x1dffe85c) = 0, -1
"\0\0\0\^B"
...
--
--
Michael van Elst
Internet: mlelstv%serpens.de@localhost
"A potential Snark may lurk in every tree."
Home |
Main Index |
Thread Index |
Old Index