Hi,
in general yes, but I currently don't know what to do exactly to get the
trace. (or do you just mean a backtrace in gdb from the core file?)
I'v found a core file mono.core in
/usr/pkgsrc/lang/mono/work/mono-2.6.1/mcs - sorry I've overlooked this
before, but some core-dumps are "normal" for several packages during
compilation ...
The script in "runtime/_tmpinst/bin/mono" seems to be the one called:
#! /bin/sh
r='/usr/pkgsrc/lang/mono/work/mono-2.6.1'
MONO_CFG_DIR='/usr/pkgsrc/lang/mono/work/mono-2.6.1/runtime/etc'
PATH="$r/runtime/_tmpinst/bin:$PATH"
MONO_SHARED_DIR=$r/runtime
export MONO_CFG_DIR MONO_SHARED_DIR PATH
exec "$r/libtool" --mode=execute "$r/mono/mini/mono" --config
"/usr/pkgsrc/lang/mono/work/mono-2.6.1/runtime/etc/mono/config" "$@"
The binary that belongs to the core file seems to be the one from
"mono/mini".
gdb says that it is semget() that is missing. OK - that may be the
problem - on both systems I've tried to compile mono no SYSV-ipc is
configured. (I avoid the SYSV-ipc in the kernel until I realy need it
due to the problems with the resouce management in it.)
It will take some time to retry with an other kernel because the System
is in productive use here ..
I come back as soon as possible with the results, but I think that would
be the problem. I think it will be in 1 ore two days.
W. Stukenbrock
Mihai Chelaru wrote:
On Fri, 2010-04-30 at 17:00 +0000,
Wolfgang.Stukenbrock%nagler-company.com@localhost wrote:
[1] Bad system call (core dumped) MONO_PATH=3D".//cl...
Can you obtain a trace from this core ?