From: Matthieu Dubuget <matthieu.dubuget@gmail.com>
To: Caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] Do you use a debugger with OCaml? If not, why not?
Date: Wed, 25 Nov 2015 14:26:57 +0100 [thread overview]
Message-ID: <5655B721.6010608@gmail.com> (raw)
In-Reply-To: <5655AE66.6000307@coherentgraphics.co.uk>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello,
I recently had to understand a bug. I tried to use OCaml debugger, but
soon gave up with this approach, because I was not able to reach the
time location where the bug occured (even after I had solved the
install_printer step that is necessary to output structured values).
One reason why it was difficult to narrow the problem was because of a
shifting of the hilighted code fragments in emacs (yes: I used
ocamldebug from emacs). I suppose (but I was too lazy to check this
assumption) that this is due to my comments: in this program they are
full of UTF-8 mathematical characters.
And I came back to the traditionnal printf debugging method.
For sure, a simpler and more robust way to visualize/follow the
execution of a program would be a great help to debug ocaml programs.
I have no idea how multi-threaded programs are supposed to be debugged,
thought?
Salutations
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
iEYEARECAAYFAlZVtyEACgkQCBfXUPYKuPWNdACfRX09FkwVbcrB6IiPiFGTuptL
4PUAn3OXNqvMaio0KOI8IPie7DyTxiGA
=Lb6/
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2015-11-25 13:26 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-25 12:49 John Whitington
2015-11-25 13:12 ` Francois Berenger
2015-11-25 13:23 ` Ivan Gotovchits
2015-11-25 15:27 ` Gerd Stolpmann
2015-11-25 16:04 ` Chan Ngo
2015-11-25 13:26 ` Matthieu Dubuget [this message]
2015-12-01 12:06 ` Matthieu Dubuget
2015-11-25 14:02 ` Markus Weißmann
2015-11-25 14:05 ` Nils Becker
2015-11-25 15:55 ` Daniel Bünzli
2015-11-26 9:14 ` Leonardo Laguna Ruiz
2015-11-26 10:59 ` Tom Ridge
2015-11-30 17:56 ` Xavier Van de Woestyne
2015-11-25 16:06 ` Maverick Woo
2015-11-25 16:16 ` Anton Bachin
2015-11-25 16:52 ` Michael Grünewald
2015-11-25 18:23 ` Török Edwin
2015-11-25 20:23 ` David MENTRÉ
2015-11-26 10:11 ` Malcolm Matalka
2015-11-26 10:57 ` Romain Bardou
2015-12-11 18:58 ` Richard W.M. Jones
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=5655B721.6010608@gmail.com \
--to=matthieu.dubuget@gmail.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