caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Nathaniel J. Gaylinn" <ngaylinn@cs.brown.edu>
To: caml-list@yquem.inria.fr
Subject: OCaml IDE (working with the OCaml debugger)
Date: Mon, 20 Jun 2005 16:07:28 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.58.0506201606330.2193@point> (raw)


Although I've spent a good amount of time working with OCaml, I've never
really made much use of the debugger. However, I feel that having a nice
interface for the ocaml debugger is an important feature for my program to
have!

Still, there are two small issues of just using the debugger that I'm
having some problems with, and until I have a better handle on them I
can't do much to develop a GUI for the debugger.

To start with, I found the stepping pattern of ocamldebug to be rather
unintuitive. After playing with it for an afternoon, I feel I have a
pretty good handle on how OCaml steps through code, but I can't personally
put it into words. Is there a simple way to describe how OCaml steps
through source code? How come in a recursive function invocation that goes
from n = 0 to n = m does the debugger seem to only stop when n = 1 to m
and not when n = 0? If this isn't clear, I can post an example.

Secondly, I often find with simple programs that OCaml doesn't list any
events in the module my source code defines, even though the source code
contains recursive function definitons and calls! What is the minimum
required for ocamldebug to see events in a simple program?

Thanks,
  -- Nate Gaylinn


                 reply	other threads:[~2005-06-20 20:07 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=Pine.LNX.4.58.0506201606330.2193@point \
    --to=ngaylinn@cs.brown.edu \
    --cc=caml-list@yquem.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;
as well as URLs for NNTP newsgroup(s).