From: Tom Ridge <tom.j.ridge@googlemail.com>
To: "Sébastien Hinderer" <Sebastien.Hinderer@inria.fr>,
caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] OCamldebug
Date: Fri, 24 Feb 2017 09:14:45 +0000 [thread overview]
Message-ID: <CABooLwM68FZREnSDMVCcVfdbOyanSJs8-MOKoaWr+fWyLF5TSQ@mail.gmail.com> (raw)
In-Reply-To: <20170224084132.eqmfxs2fvwe6emxw@pl-59055.rocqadm.inria.fr>
[-- Attachment #1: Type: text/plain, Size: 1147 bytes --]
Not sure. There is this clause in the ocamldebug page:
"For technical reasons, the debugger cannot call printing functions that
reside in the program being debugged. The code for the printing functions
must therefore be loaded explicitly in the debugger."
Also, I'm only trying to view a string...
On 24 February 2017 at 08:41, Sébastien Hinderer <
Sebastien.Hinderer@inria.fr> wrote:
> Tom Ridge (2017/02/23 16:49 +0000):
> > Regarding `#install_printer`, can you explain more? The type
> > "Key_value_types.key" is equal to string (in this particular case).
> > However, this type is produced via module application, and so I cannot
> > construct a printer that can print values of type "Key_value_types.key"
> > before program execution (which seems to be required for
> > #install_printer).
>
> Can't you add the pretty-printer to the module, actually?
>
> Sébastien.
>
> --
> Caml-list mailing list. Subscription management and archives:
> https://sympa.inria.fr/sympa/arc/caml-list
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
>
[-- Attachment #2: Type: text/html, Size: 1982 bytes --]
prev parent reply other threads:[~2017-02-24 9:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-23 16:24 Tom Ridge
2017-02-23 16:31 ` Ivan Gotovchits
2017-02-23 16:49 ` Tom Ridge
2017-02-23 17:02 ` Ivan Gotovchits
2017-02-24 9:16 ` Tom Ridge
2017-02-24 9:20 ` Tom Ridge
2017-02-24 9:28 ` Sébastien Hinderer
2017-02-24 8:41 ` Sébastien Hinderer
2017-02-24 9:14 ` Tom Ridge [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=CABooLwM68FZREnSDMVCcVfdbOyanSJs8-MOKoaWr+fWyLF5TSQ@mail.gmail.com \
--to=tom.j.ridge@googlemail.com \
--cc=Sebastien.Hinderer@inria.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;
as well as URLs for NNTP newsgroup(s).