From: Alessandro Baretta <alex@baretta.com>
To: Chris Hecker <checker@d6.com>, Ocaml <caml-list@inria.fr>
Subject: Re: [Caml-list] ocamldebug and windows
Date: Wed, 23 Oct 2002 08:58:47 +0200 [thread overview]
Message-ID: <3DB648A7.403@baretta.com> (raw)
In-Reply-To: <4.3.2.7.2.20021022083244.035ebfb8@mail.d6.com>
Chris Hecker wrote:
>
> Is all of this really worth it when compared to having a cross-platform
> "normal" debugger, especially if that debugger architecture could work
> on native code as well? In other words, it seems like we're giving up a
> lot for this time-traveling feature. I've played with it a bit, and it
> seems fine, but the fact that it's central to the debugger architecture
> makes some other things harder (like porting it :).
I think time travel is one of the bigger bonuses of working
with O'Caml. I understand the need for a simple debugger
that works in all situations, but time travel is something
O'Caml cannot give up.
I was also surprised that the debugger couldn't eval and
link in
> arbitrary ocaml code, especially since a) the debugger works only on
> bytecode, and b) caml already has a toplevel.
This surprises me, too. Often, I'd like to run functions
manually when at a checkpoint, for the sake of printing
complex data structures. I would be content to be able to
invoke functions predefined in the executable being debugged.
Alex
-------------------
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
prev parent reply other threads:[~2002-10-23 6:47 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
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 [this message]
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=3DB648A7.403@baretta.com \
--to=alex@baretta.com \
--cc=caml-list@inria.fr \
--cc=checker@d6.com \
/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