[erlang-questions] Cannot build a work vm on FreeBSD with dtrace AND enable dirty-schedulers

Steve Vinoski <>
Sat Apr 12 16:38:45 CEST 2014


I can't reproduce the problem either. Running FreeBSD 10.0 in a Parallels
VM on OS X 10.8.5, using gcc49 and with the VM configured for 4 cores:

$ CC=gcc49 CXX=g++49 MAKE=gmake ./configure --with-dynamic-trace=dtrace
--enable-dirty-schedulers
$ ./bin/erl
Erlang/OTP 17 [erts-6.0] [source] [64-bit] [smp:4:4] [ds:4:4:10]
[async-threads:10] [hipe] [kernel-poll:false] [dtrace]

Eshell V6.0  (abort with ^G)
1>

So, perhaps Kenji is correct that it's a problem specific to VirtualBox on
Ubuntu. One thing to check is that SMP support is enabled, since dirty
scheduler support currently requires SMP support.

--steve



On Fri, Apr 11, 2014 at 10:15 PM, Kenji Rikitake <> wrote:

> The dirty scheduler on FreeBSD 10-STABLE on a *non-VM native* machine
> (Core i5, 16GB RAM) works alright here with both gcc47 and *clang*. I'm
> using kerl.  I suspect it's a VirtualBox-on-Ubuntu problem.
>
> uname -a:
>
> FreeBSD minimax.priv.k2r.org 10.0-STABLE FreeBSD 10.0-STABLE #33 r264285:
> Wed Apr  9 09:25:02 JST 2014     :/usr/obj/usr/src/sys/K2RKERNEL
>  amd64
>
> .kerlrc setting:
>
> # since .kerl is a dot file for /bin/sh, exporting inside the environment
> will define the env variables
> # NOTE WELL: these export command will affect *your login environment*
> when activating curl!
> # for clang with concurrent make
> export CC=clang CXX=clang CFLAGS="-g -O3 -fstack-protector"
> LDFLAGS="-fstack-protector" MAKEFLAGS="-j"
> # for gcc47
> #export CC=gcc47 CXX=gcc47 CFLAGS="-g -O3 -fomit-frame-pointer
> -fstack-protector" LDFLAGS="-fstack-protector" MAKEFLAGS="-j"
> #
> KERL_CONFIGURE_OPTIONS="--disable-native-libs --enable-vm-probes
> --with-dynamic-trace=dtrace --with-ssl=/usr/local --with-javac
> --enable-hipe --enable-kernel-poll
> --with-wx-config=/usr/local/bin/wxgtk2u-2.8-config --without-odbc
> --enable-threads --enable-sctp --enable-smp-support
> -enable-dirty-schedulers --disable-silent-rules"
>
> erl shell output:
>
> Erlang/OTP 17 [erts-6.0] [source] [64-bit] [smp:4:4] [ds:4:4:10]
> [async-threads:10] [hipe] [kernel-poll:false] [dtrace]
>
> Eshell V6.0  (abort with ^G)
> 1> erlang:system_info(dirty_cpu_schedulers).
> 4
> 2>
>
> Kenji Rikitake
>
> ++> Wu Ray <> [2014-04-11 12:30:02 +0800]:
> > Date: Fri, 11 Apr 2014 12:30:02 +0800
> > From: Wu Ray <>
> > To: 
> > Subject: [erlang-questions] Cannot build a work vm on FreeBSD with dtrace
> >  AND enable dirty-schedulers
> >
> > Hi, list
> >
> > I cannot build a working erlang 17 on FreeBSD 10.0, with dtrace AND
> enabled
> > dirty-schedulers at the same time, that's my steps:
> > ./configure --with-dynamic-trace=dtrace --enable-dirty-schedulers
> > gmake
> >
> > then, the build erl vm just quit with:
> > Segmentation fault(core dumped)
> >
> > I've tried gcc47, same result.
> > CC=gcc47 CXX=g++47 ./configure --with-dynamic-trace=dtrace
> > --enable-dirty-schedulers
> >
> > if I build with-dtrace OR enable dirty-schedulers separately, the VMs run
> > well.
> > but the dirty-schedulers number looks strange:
> >
> > Erlang/OTP 17 [erts-6.0] [source] [64-bit]
> > [ds:10:5851653:18446744073709551611] [async-threads:38554976] [hipe]
> > [kernel-poll:]
> >
> > Eshell V6.0 (abort with ^G)
> > 1> erlang:system_info(dirty_cpu_schedulers).
> > ** exception error: bad argument
> >      in function  erlang:system_info/1
> >         called as erlang:system_info(dirty_cpu_schedulers)
> >
> >
> > And, gcc48 cannot build a working VM with enabled dirty-schedulers, the
> vm
> > quit with Segmentation fault.
> >
> > BTW: my FreeBSD 10.0 is running in VirtualBox 4.3.10 on Ubuntu13.10
> >
> >
> > regards,
>
> > _______________________________________________
> > erlang-questions mailing list
> > 
> > http://erlang.org/mailman/listinfo/erlang-questions
>
> _______________________________________________
> erlang-questions mailing list
> 
> http://erlang.org/mailman/listinfo/erlang-questions
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20140412/3c0142a8/attachment.html>


More information about the erlang-questions mailing list