From: "Dimitry Kloper" <dimka@my-dejanews.com>
To: caml-list@inria.fr
Subject: OCaml debugging on NT
Date: Wed, 16 Dec 1998 08:20:26 -0700 [thread overview]
Message-ID: <PJOGBMBEKJLGIAAA@my-dejanews.com> (raw)
I am starting a relatively large project which will extensively deal
with 3d graphics (based on OPenGL) from one side and parsing of different
text formats (e.g. HTML) from other. My primary platform is winNT.
I am at stage of choosing primary implementation language.
OCaml seems to be very attractive for me, but I can't find any really useful
debugging tools, especially for NT. ocamldebug is unavailable on NT. As far as
I understand it is not portable because of buggy sockets interface on NT.
#trace facility on toplevel seems to be useful, but it doesn't work with
class methods (or at least I didn't succeed to trace a method), and prints
info only about control flow and parameters, while I would expect output
like `/bin/sh -x`. Inserting print statements is always an option, but
it is very inconvenient, especially on beginning stages of the project.
So, my question is about known techniques of debugging and tracing of OCaml
code.
What I would expect is something like John's Libes tcl-debug for tcl.
Thanks.
-----== Sent via Deja News, The Discussion Network ==-----
http://www.dejanews.com/ Easy access to 50,000+ discussion forums
reply other threads:[~1998-12-18 8:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=PJOGBMBEKJLGIAAA@my-dejanews.com \
--to=dimka@my-dejanews.com \
--cc=caml-list@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