Chema García <chema@safe...> wrote:

> I've been trying to compile Python 2.7 with dtrace support from
> https://hg.jcea.es/cpython-2011/ (branch dtrace-issue13405_2.7 ) to test
> http://bugs.python.org/issue13405#msg164610.
>
> I've also recompiled the kernel to enable dtrace support by following
> http://www.freebsd.org/doc/en/books/handbook/dtrace-enable.html , but
> dtrace enters into an infinite loop when compiling, and using 100% of
> CPU usage.
>
> I'm using FreeBSD 9.0-RELEASE-p3, and used:
>
> ./configure --with-dtrace && make
>
> And the issue occurs at:
>
> gcc -pthread -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall
> -Wstrict-prototypes  -I. -IInclude -I./Include  -DPy_BUILD_CORE -o
> Include/pydtrace_offsets  Include/pydtrace_offsets.c
> Include/pydtrace_offsets.sh OTHER  Python/ceval.o
> Include/pydtrace_offsets >  Include/pydtrace_offsets.h
> if test "dtrace" != "" ; then  dtrace -o Python/pydtrace.o
> -DPYDTRACE_STACK_HELPER  -I. -IInclude -I./Include -32  -C -G -s
> Include/pydtrace.d  Python/ceval.o Modules/gcmodule.o
> Objects/classobject.o Objects/typeobject.o;  else    touch
> Python/pydtrace.o ;  fi;
>
> I've tried removing '-DPYDTRACE_STACK_HELPER' with same results.

Does it make a difference if you remove the -O3 (and maybe -O2)?

Fabian