[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: debugging guile runtime
From: |
rixed |
Subject: |
Re: debugging guile runtime |
Date: |
Tue, 30 Aug 2011 12:56:43 +0200 |
User-agent: |
Mutt/1.5.20 (2009-06-14) |
The problem is not that the *ports* are not closed (they are), but that
the other *files* (that are not port) are not closed.
When a program exec another one, it's supposed to close all files but 0,
1 and 2. open-process only closes the ports, so if you have other files
opened (that you have opened from C for instance) these files will be
communicated to the new process, which is not the intended behavior.
I state that open-process should _not_ try to close *ports*, but should
close all *files* (but 0, 1 and 2) instead.
- debugging guile runtime, rixed, 2011/08/29
- Re: debugging guile runtime, Nala Ginrut, 2011/08/29
- Re: debugging guile runtime, rixed, 2011/08/29
- Re: debugging guile runtime, Thien-Thi Nguyen, 2011/08/29
- Re: debugging guile runtime,
rixed <=
- Re: debugging guile runtime, Ludovic Courtès, 2011/08/30
- Re: debugging guile runtime, rixed, 2011/08/30
- Re: debugging guile runtime, Ludovic Courtès, 2011/08/30
- Re: debugging guile runtime, rixed, 2011/08/31
- Re: debugging guile runtime, Andy Wingo, 2011/08/31
Re: debugging guile runtime, Andy Wingo, 2011/08/31