guile-user
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: debugging guile test failure and segfault.


From: Ludovic Courtès
Subject: Re: debugging guile test failure and segfault.
Date: Sun, 10 Jun 2007 15:51:52 +0200
User-agent: Gnus/5.110006 (No Gnus v0.6) Emacs/21.4 (gnu/linux)

Hi,

Dan McMahill <address@hidden> writes:

> Backtrace:
> In unknown file:
>    ?: 0* [primitive-load "test-suite/tests/r4rs.test"]
> In test-suite/tests/r4rs.test:
>  923: 1*
> Exception during displaying of backtrace: system-error
>
> test-suite/tests/r4rs.test:88:45: In procedure ttyname in expression
> (write (cons fun args) port):
> test-suite/tests/r4rs.test:88:45: No such file or directory
> ABORT: (system-error)
> guile> (debug)
> Frame 9 at test-suite/tests/r4rs.test:88:45
>         ERROR: In procedure ttyname:
> ERROR: No such file or directory
> ABORT: (system-error)
> guile>
>
> this doesn't look promising.

Well, it's much better than a segfault.  ;-)

This happens when trying to display a file port allegedly backed by a
TTY file descriptor.  See `fports.c:fport_print' (line 676):

    if (isatty (fdes))
      scm_display (scm_ttyname (exp), port);

What seems to be happening is that `isatty (fdes)' returns true but then
`ttyname (fdes)' fails.

I suspect that the port at hand is `(current-output-port)' or some
such.  On GNU/Linux, we get the following:

  guile> (ttyname (current-output-port))
  "/dev/pts/11"

Can you try this on your OS?

Thanks,
Ludovic.





reply via email to

[Prev in Thread] Current Thread [Next in Thread]