Re: 9.1 xdpyinfo oddity

[Eduardo Horvath <eeh%NetBSD.org@localhost>]

On Wed, 21 Oct 2020, Mouse wrote:

> ktracing both working and failing runs, they appear identical (except
> for ASLR-style pointer differences) right up until it's about to start
> printing things.  It does
> 
>    507      1 xdpyinfo CALL  __fstat50(1,0x7f7fffbd4de0)
> 
> (where of course the PID and the pointer differ between runs).
> __fstat50 succeeds (the RET line shows 0) in each case, but in the
> "working" case, it then does ten mmaps of 0x1000 bytes (all mmaps are
> of ANONYMOUS memory), does TIOCGETA on stdout, and starts printing

It sounds to me as if xdpyinfo is checking to see if stdout is a tty and 
is doing something wrong if it isn't.  Doesn't sound like it has anything 
to do with the server at all.

Eduardo