Question about debug info

Bjorn Gustavsson <>
Thu Aug 31 14:42:42 CEST 2006


-compile(debug_info) does not work. The debug_info options must be given on
the command line for the compiler.

I'll try to fix it for R11B-2 (or at least correct the documentation to
point out that it doesn't work).

How to check:

Eshell V5.5.1  (abort with ^G)
1> c(t, debug_info).
{ok,t}
2> beam_lib:info(t).
[{file,"t.beam"},
 {module,t},
 {chunks,[{"Atom",20,77},
          {"Code",108,129},
          {"StrT",248,0},
          {"ImpT",256,40},
          {"ExpT",304,40},
          {"LocT",352,4},
          {"Attr",364,40},
          {"CInf",412,172},
          {"Abst",592,285}]}]

If the second number on the last line (285 in this case) is non-zero, there
is debug info in the beam file. If the number is zero, if there is no line
at all containing "Abst", there is no debug information.

/Bjorn

"Gomes, Pedro" <> writes:

> Hello All,
> I tryed to use the Erlang debugger and in order to do it I need to
> compile the source modules with debug info and for that matter I used
> -compile(debug_info)
> 
> This seems to have no effect, even if the .beam module increases its
> size, because the debugger still continues to issue an error saying
> there no debug information present in the .beam module.
> 
> What am I doing wrong ?
> 
> Thanks,
> Pedro

-- 
Björn Gustavsson, Erlang/OTP, Ericsson AB



More information about the erlang-questions mailing list