Debugger problems

Gunilla Arendt gunilla@REDACTED
Thu Feb 21 14:01:24 CET 2002


>From R8, the Debugger needs the abstract code for a module.
I.e. any module to be debugged must be compiled with the option
'debug_info' set. Example:
  unix> erlc +debug_info m.erl
  1> c(m, debug_info).

This greatly improves code handling in the Debugger but unfortunately
the documentation has not been updated accordingly, sorry about that.

An improved Debugger (with updated documentation) is under development
and will be released soon.

/ Gunilla

Kurt Luoto wrote:
> I am also having problems with the debugger in the R8 distribution running
> on Windows2000 and on Windows98.  It doesn't seem to matter what module
> (file) I try to interpret, I get the following error report on the Erlang
> emulator screen:
> ----------------------------------------------------------------------------
> --------------------------------
> Erlang (BEAM) emulator version 5.1 [threads:0]
> Eshell V5.1  (abort with ^G)
> 1> gs error: gstk: unexpected reply: Monitor
> =ERROR REPORT==== 20-Feb-2002::22:41:21 ===
> Error in process <0.49.0> with exit value:
> {badarg,[{erlang,binary_to_term,[<<0
> bytes>>]},{dbg_iload,abstr,1},{dbg_iload,store_module,3},{dbg_iload,load_mod
> 1,3
> ]}
> ----------------------------------------------------------------------------
> --------------------------------
> After that, the debugger is pretty much dead.
> This happens even on trivial files that compile and test correctly.
> -- Kurt Luoto

More information about the erlang-questions mailing list