From: Mads Jensen <mads379@gmail.com>
To: caml-list@inria.fr
Subject: [Caml-list] ocamldebug and -pack
Date: Sun, 16 Nov 2014 14:43:24 +0100 [thread overview]
Message-ID: <CAM1coagNvx9MwHm+oH_Ajt3f+w6XPxhSjEXeDXi4YybdLjLWYw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 824 bytes --]
Hi,
I tried out ocamldebug on the hello world example[1] of the ocaml-cohttp
library. I configured the debugger by writing the results of `ocamlfind
query -recursive core async cohttp cohttp.async` into a file and prefixed
each line with `directory`. For more information see this blog post about
my setup[2].
As I stepped through the code I would see errors like this:
(ocd) step
Time: 1084742 - pc: 4416712 - module Cohttp.Request
No source file for Cohttp.Request.
I chatted with whitequark on IRC and he suggests that it might be because
ocamldebug doesn't support compilation units compiled with the -pack flag.
Is that the case? If so, is this a bug?
Cheers,
Mads
[1]
https://github.com/mirage/ocaml-cohttp/blob/master/examples/async/hello_world.ml
[2] http://mads379.github.io/ocaml/2014/11/15/ocamldebug.html
[-- Attachment #2: Type: text/html, Size: 2133 bytes --]
reply other threads:[~2014-11-16 13:43 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=CAM1coagNvx9MwHm+oH_Ajt3f+w6XPxhSjEXeDXi4YybdLjLWYw@mail.gmail.com \
--to=mads379@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