From: "Richard W.M. Jones" <rich@annexia.org>
To: John Whitington <john@coherentgraphics.co.uk>
Cc: "caml-list@inria.fr" <caml-list@inria.fr>
Subject: Re: [Caml-list] Do you use a debugger with OCaml? If not, why not?
Date: Fri, 11 Dec 2015 18:58:37 +0000 [thread overview]
Message-ID: <20151211185837.GA9373@annexia.org> (raw)
In-Reply-To: <5655AE66.6000307@coherentgraphics.co.uk>
On Wed, Nov 25, 2015 at 12:49:42PM +0000, John Whitington wrote:
> So, I ask: What do you use for debugging small and large OCaml programs? If
> not a debugger, why not? What problems prevent it? How does your debugging
> process differ when writing OCaml compared with other languages you use?
No one seems to have mentioned gdb in this thread. I use it on OCaml
programs quite often. It's especially useful for finding bugs in my C
libraries :-) In fact I missed gdb when we ported the tools to aarch64
because stack traces didn't work properly for quite a while [now fixed].
Rich.
--
Richard Jones
Red Hat
prev parent reply other threads:[~2015-12-11 18:58 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
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 [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=20151211185837.GA9373@annexia.org \
--to=rich@annexia.org \
--cc=caml-list@inria.fr \
--cc=john@coherentgraphics.co.uk \
/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).