From: "Nicolas Cannasse" <warplayer@free.fr>
To: "Xavier Leroy" <xavier.leroy@inria.fr>, "Dmitry Bely" <dbely@mail.ru>
Cc: "OCaml" <caml-list@inria.fr>
Subject: Re: [Caml-list] ocamldebug and windows
Date: Tue, 22 Oct 2002 13:23:07 +0200 [thread overview]
Message-ID: <008201c279bd$65950500$3900a8c0@warp> (raw)
In-Reply-To: <20021022095740.A6289@pauillac.inria.fr>
> It is true that time-travel in the presence of I/O is, in general,
> impossible. (You can't "un-send" the network packets that were
> already sent!) However, I'd like it to work at least for programs
> that read or write regular files, as in the example above. Under
> Unix, fork() gets us 90% there -- there is still an issue with the
> reading/writing position being shared (not duplicated) between the
> parent and child process, but we are considering hacks to work around
> this.
Of course, backward program execution is really a great feature !
But what about simply having a debugger under Win32 without it ? That would
be far better than no debugger at all...
And perhaps that will motivate some *cool hackers* who will then work on the
checkpointing library you were talking about or equivalent solutions.
- Nicolas Cannasse
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
next prev parent reply other threads:[~2002-10-22 11:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-21 10:43 Dmitry Bely
2002-10-21 13:21 ` Xavier Leroy
2002-10-21 14:17 ` Dmitry Bely
2002-10-22 7:57 ` Xavier Leroy
2002-10-22 11:23 ` Nicolas Cannasse [this message]
2002-10-22 15:56 ` Chris Hecker
2002-10-22 16:42 ` Mattias Waldau
2002-10-22 20:46 ` Pierre Weis
2002-10-23 6:58 ` Alessandro Baretta
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='008201c279bd$65950500$3900a8c0@warp' \
--to=warplayer@free.fr \
--cc=caml-list@inria.fr \
--cc=dbely@mail.ru \
--cc=xavier.leroy@inria.fr \
/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