[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: debugging guile runtime
From: |
Ludovic Courtès |
Subject: |
Re: debugging guile runtime |
Date: |
Wed, 31 Aug 2011 00:25:27 +0200 |
User-agent: |
Gnus/5.110018 (No Gnus v0.18) Emacs/24.0.50 (gnu/linux) |
Hi,
address@hidden skribis:
> -[ Tue, Aug 30, 2011 at 05:55:22PM +0200, Ludovic Courtès ]----
>> Like in C, it???s up to the application to close those ports that it
>> considers worth closing upon exec.
[...]
> OK then, so it's not a bug and I have to live with this behavior
> (BTW, if anyone knows the rational behind this, I would be glad to
> know).
When typing “foo 2< baz 5> bar” in a shell, the shell first forks, the
opens/dups 2 and 5, and finally execs ‘foo’, which gets to see 2 and 5
as open FDs. Same for pipes.
> Except that, as previously discussed in another thread, there is no easy
> way to do that between the fork and the exec (since I don't want to
> actually close these files in the main program that starts the pipe).
Hmm right. We’d need to insert a hook in ‘open-pipe’ so that, when this
behavior is wanted, one can actually close those FDs.
Ideas?
Thanks,
Ludo’.
- 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, 2011/08/30
- 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 <=
- 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