Re: debugging guile test failure and segfault.

[Dan McMahill]

Ludovic Courtès wrote:
> Hi,
>
> Dan McMahill <address@hidden> writes:
>
> > I'll bet thats whats going on with NetBSD as well.  My failed tests
> > are all inside a chroot environment.
>
> Well, we *could* modify the file port write (i.e., `fport_print ()') so
> that it doesn't fail when `ttyname' does, if that's a common problem.
>
> Or you could set up a chroot jail where `/dev/pts/*' are visible, if
> that's the source of the problem.


ok, I think this much smaller test case is instructive:

#include <stdio.h>
#include <unistd.h>

int main(int argc, char **argv)
{
        int fd = 0;
        char *n;

        printf ("isatty(%d) = %d\n", fd, isatty (fd));

        n = ttyname (fd);
        printf ("ttyname(%d) = \"%s\"\n", fd, n != NULL ? n : "unknown");

        return 0;
}


SunOS-5.9/sparc

chroot:

isatty(0) = 1
ttyname(0) = "unknown"

no chroot:

isatty(0) = 1
ttyname(0) = "/dev/pts/32"


NetBSD-2/alpha

chroot:

isatty(0) = 1
ttyname(0) = "unknown"

no chroot:

isatty(0) = 1
ttyname(0) = "/dev/ttyp2"

NetBSD-4/i386

chroot:

isatty(0) = 1
ttyname(0) = "/dev/ttyp2"

no chroot:

isatty(0) = 1
ttyname(0) = "/dev/ttyp1"


Wierd that the NetBSD-4 box doesn't seem to care about being in the 
chroot jail.