From: Virgile Prevosto <virgile.prevosto@m4x.org>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Elusive String.blit exception
Date: Thu, 3 Mar 2005 11:15:48 +0100 [thread overview]
Message-ID: <20050303111548.3d8e211d@mpiat2314> (raw)
In-Reply-To: <20050303095229.GA32100@furbychan.cocan.org>
Le 03/03/2005, à 09:52:29 AM, Richard Jones a écrit:
> On Wed, Mar 02, 2005 at 11:18:35PM -0500, Mike Hamburg wrote:
> > Where could this exception be coming from? Is there any way to
> > automatically get a backtrace when my program dies on an exception?
> >
>
> Yes. Compile your whole program as bytecode and then export the
Just a small addition: when compiling and linking the program, don't
forget to add the -g option to ocamlc, so that the generated bytecode
contains the necessary debugging informations.
--
E tutto per oggi, a la prossima volta
Virgile
prev parent reply other threads:[~2005-03-03 10:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-03 4:18 Mike Hamburg
2005-03-03 9:52 ` [Caml-list] " Richard Jones
2005-03-03 10:15 ` Virgile Prevosto [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=20050303111548.3d8e211d@mpiat2314 \
--to=virgile.prevosto@m4x.org \
--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).