From: "Jocelyn Sérot" <jocelyn.serot@uca.fr>
To: OCaml Mailing List <caml-list@inria.fr>
Subject: [Caml-list] Problem with ocamldebug 4.06.0
Date: Thu, 19 Jul 2018 16:05:13 +0200 [thread overview]
Message-ID: <0E31DD5B-08EE-40C6-80CD-2BC8EDE31964@uca.fr> (raw)
[-- Attachment #1: Type: text/plain, Size: 1361 bytes --]
Hello,
I’m experiencing problems when using ocamldebug on a large program.
Namely, the debugger quits launching an « Not_found » exception as soon as i try to visualize some program variables (print) or dump thef frame
(ocd) …
(ocd) print t
Removed breakpoint 1 at 958036: file vhdl.ml, line 113, characters 19-30
Uncaught exception: Not_found
OCaml-Debugger exited abnormally with code 2
I’ve started to encounter this problem when i recrafted the program in order to use ocamlbuild and distribute the source code in several directories.
What is annoying is that the problem is not systematic it seems to dependi on the variable to be printed (or at least on the module where it is defined) - which makes isolating a minimum triggering program difficult :(
So my questions are
i) is there something special to do when using ocamldebug in a multi-directory source file context ? I of course tried to add « _build » and « subdir/_build » to the debug « path » using the directory command, w/o success
ii) has someone already encountered this problem
iii) is there a way to track down where / why the exception was launched (i.e. to debug the debugger)
iv) is there a chance that the pb is fixed in 4.07.0 (apparently no since nothing is told about ocamldebug in the release doc).
Any help appreciated
Cheers
Jocelyn
[-- Attachment #2: Type: text/html, Size: 2004 bytes --]
next reply other threads:[~2018-07-19 14:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-19 14:05 Jocelyn Sérot [this message]
2018-07-19 15:57 ` Gabriel Scherer
2018-07-19 16:24 ` Jocelyn Sérot
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=0E31DD5B-08EE-40C6-80CD-2BC8EDE31964@uca.fr \
--to=jocelyn.serot@uca.fr \
--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