Version française
Home     About     Download     Resources     Contact us    
Browse thread
Buggy behavior in ocamldebug 3.0.9.3 breakpoint command
[ Home ] [ Index: by date | by threads ]
[ Search: ]

[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
Date: -- (:)
From: jv at ens dot fr <julien.vanegue@e...>
Subject: Buggy behavior in ocamldebug 3.0.9.3 breakpoint command
It seems like the "break funcname" syntax for putting breakpoints
given a function name is not working on 3.0.9 :


lmbdwr@relambda:~/projet-MPRI-2-4-2/src$ ocamldebug joujou.byte
        Objective Caml Debugger version 3.09.3

(ocd) set arguments ../test/good/pair.ml
(ocd) break eval
Loading program... done.
Unbound identifier eval
(ocd) break @ Interpreter 44
Breakpoint 1 at 123388 : file interpreter.ml, line 45, characters 21-1167
(ocd)
(ocd) run
*** Type:
'a0
Time : 6507 - pc : 123388 - module Interpreter
Breakpoint : 1
45 and eval env expr = <|b|>match expr with

(ocd) list 40 
40       printf ")"
41   | Closure(e, env) -> print_value (eval env e)
42
43
44 (* [eval env expr] returns the value of expression [expr] in 
environment [env] *)
45 and eval env expr = <|b|>match expr with
46   | EVar(x)             -> (find_var x env)
47   | EFun(var, e)        -> Closure(EFun(var, e), env)
48   | ERecFun(f, x, e)    -> Closure(ERecFun(f, x, e), env)
[...]


So the "eval" function is indeed existing but ocd refuses to break on 
it. Is it because its
using the "and ..." construct ? or is it a real bug in the break command ?

--
Julien Vanegue (vanegue at ens dot fr)