From: Nala Ginrut <nalaginrut@gmail.com>
To: rixed@happyleptic.org, guile-user@gnu.org
Subject: Re: debugging guile runtime
Date: Mon, 29 Aug 2011 22:35:20 +0800 [thread overview]
Message-ID: <CAPjoZocyrLRwa=3sSu8UZ2jy=MhJuu3DiVn3-URhwQBZORmxqg@mail.gmail.com> (raw)
In-Reply-To: <20110829125030.GB30079@ccellier.rd.securactive.lan>
[-- Attachment #1: Type: text/plain, Size: 197 bytes --]
On Mon, Aug 29, 2011 at 8:50 PM, <rixed@happyleptic.org> wrote:
#4 fork does not close all open files.
>
well, I got the same question, will fork auto close in Guile or should I
close it myself?
[-- Attachment #2: Type: text/html, Size: 491 bytes --]
next prev parent reply other threads:[~2011-08-29 14:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-29 12:50 debugging guile runtime rixed
2011-08-29 14:35 ` Nala Ginrut [this message]
2011-08-29 16:24 ` rixed
2011-08-29 19:20 ` Thien-Thi Nguyen
2011-08-30 10:56 ` rixed
2011-08-30 15:55 ` Ludovic Courtès
2011-08-30 16:25 ` rixed
2011-08-30 22:25 ` Ludovic Courtès
2011-08-31 7:38 ` rixed
2011-08-31 21:10 ` Andy Wingo
2011-08-31 21:07 ` Andy Wingo
2011-09-01 11:32 ` rixed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAPjoZocyrLRwa=3sSu8UZ2jy=MhJuu3DiVn3-URhwQBZORmxqg@mail.gmail.com' \
--to=nalaginrut@gmail.com \
--cc=guile-user@gnu.org \
--cc=rixed@happyleptic.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).