Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Jerome Vouillon <Jerome.Vouillon@inria.fr>
To: John Whitley <whitley@cse.buffalo.edu>, caml-list@inria.fr
Subject: Re: Olabldebug on classes?
Date: Mon, 22 Feb 1999 16:28:04 +0100	[thread overview]
Message-ID: <19990222162804.26352@pauillac.inria.fr> (raw)
In-Reply-To: <14032.63536.754773.125969@hadar.cse.Buffalo.EDU>; from John Whitley on Mon, Feb 22, 1999 at 01:54:20AM -0500


Hello,

> Perhaps I am simply being a bit slow today, but I cannot seem to get
> olabldebug to print/display class instance variables, mutable or
> otherwise.

This is a bug of the debugger (it has not been kept up to date with
respect to the compiler). The following patch fixes this problem.

-- Jérôme

Index: debugger/eval.ml
===================================================================
RCS file: /net/pauillac/caml/repository/csl/debugger/eval.ml,v
retrieving revision 1.20
diff -u -r1.20 eval.ml
--- eval.ml     1998/08/03 13:51:08     1.20
+++ eval.ml     1999/02/22 15:20:24
@@ -71,8 +71,10 @@
       begin try
         let (p, valdesc) = Env.lookup_value lid env in
         (begin match valdesc.val_kind with
-           Val_ivar _ ->
-             let (p0, _) = Env.lookup_value (Longident.Lident "*self*") env in
+           Val_ivar (_, cl_num) ->
+             let (p0, _) =
+               Env.lookup_value (Longident.Lident ("self-" ^ cl_num)) env
+             in
              let v = path event p0 in
              let i = path event p in
              Debugcom.Remote_value.field v (Debugcom.Remote_value.obj i)




      reply	other threads:[~1999-02-22 17:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-02-22  6:54 John Whitley
1999-02-22 15:28 ` Jerome Vouillon [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=19990222162804.26352@pauillac.inria.fr \
    --to=jerome.vouillon@inria.fr \
    --cc=caml-list@inria.fr \
    --cc=whitley@cse.buffalo.edu \
    /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