From: Mark Shinwell <mshinwell@janestreet.com>
To: Jez <jezreel@gmail.com>
Cc: "caml-list@inria.fr" <caml-list@inria.fr>
Subject: Re: [Caml-list] How hard would it be to make it possible to invoke functions in the debugger?
Date: Tue, 2 Jun 2015 16:27:42 +0200 [thread overview]
Message-ID: <CAM3Ki74TJraTZJ_ToPF1rKeu-KpTMxcN+AjEkxwk6tWsfJFp+g@mail.gmail.com> (raw)
In-Reply-To: <CABVpgLXuq6HZwxcUzTgBK58+EdZj+kc+k+e0Mx25JxbbNuQaEg@mail.gmail.com>
Do you mean in the bytecode debugger (ocamldebug)? I'm not sure,
although others on this list will know.
The enhanced native code debugging support that I've been working on
should have this capability. This may land for 4.03 at the end of the
year, but could be delayed until next year.
Mark
On 1 June 2015 at 03:24, Jez <jezreel@gmail.com> wrote:
> I'd love if this were possible, and I'd be willing to poke around the OCaml
> codebase to make this work, assuming it's not a fundamentally difficult
> thing.
>
> Jez
prev parent reply other threads:[~2015-06-02 14:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-01 1:24 Jez
2015-06-02 14:27 ` Mark Shinwell [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=CAM3Ki74TJraTZJ_ToPF1rKeu-KpTMxcN+AjEkxwk6tWsfJFp+g@mail.gmail.com \
--to=mshinwell@janestreet.com \
--cc=caml-list@inria.fr \
--cc=jezreel@gmail.com \
/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).