[erlang-questions] diffrent emulator modes
Thu Sep 13 13:53:39 CEST 2007
Sanjaya Vitharana wrote:
> Hi Serge,
> 1.) What is the diffrence between below each and every erlang emulator modes (found in erl_bif_info.c)? are there any docs discribing those?
Some of them are described in erts/erl documentation. I put erl
arguments below showing how to enable the feature.
> " [source]"
> " [64-bit]"
> " [smp:%bpu]"
> " [async-threads:%d]"
> " [hipe]"
> " [kernel-poll:%s]"
> " [no-frag]"
> " [io-thread]"
> " [io-at-once]"
> " [port-tasks]"
> " [hybrid heap]"
> " [incremental GC]"
> " [type-assertions]"
> " [debug-compiled]"
> " [lock-checking]"
> " [purify-compiled]"
> " [valgrind-compiled]"
> 2.) How to configure & make erlang emulator in diffrent modes (above)
Support for most of the modes above are auto-detected by the configure
script, so if your OS supports them, the emulator will as well.
> I am specially interested on below areas for debugging purposes (erlang port driver debugging)
I am not familiar with this one.
> debug compiled emulator
> Runing debug compiled emulator in gdb
run erl with -emu_args to determine emulator startup command. Then do a
"gdb /path/to/beam" and in gdb do "run ARGS_OF_BEAM" where ARGS_OF_BEAM
are copied from the console output of -emu_args option.
> emulator compiled for valgrind
Never tried this one.
> 3.) how to run erlang in those modes ?
> Thanks in advance,
> Sanjaya Vitharana
More information about the erlang-questions