On 19.04.11 11:41, Raúl Alexis Betancor Santana wrote:
On Tue, Apr 19, 2011 at 11:16:49AM +0200, Raphael Coeffic wrote:
On 19.04.11 10:35, Raphael Coeffic wrote:
Hi Raul,
On 19.04.11 10:32, Raúl Alexis Betancor Santana wrote:
Hi all
Till now, we have been working with a dsm script that used mod_py and
inside the dsm it does some task withing a py ( ... ) call, now after
updating our system to Debian Squeeze (stable) and to sems 1.4.0 ...
the .dsm script does not work anymore, moreover, sems segfault when
trying to run the .dsm script.
Does this have any relation with the problems of sems 1.4.X and the
python-modules package ?
Could be: I will have to have a look at that.
Just tried it right now, and I was able to load a script using
mod_py, and run this script without problems.
Could you please try to get a stack trace of the crash?
I you tell me how to, I'll send it to you, this is the debian package
... so maybe it's not compiled with debuging symbols.
In fact it is ;-)
depending on your config, you might need to run that as root:
# ulimit -c unlimited
# /usr/sbin/sems -f /etc/sems/sems.conf
hopefully you should get something saying 'core dumped'. Then, just look
for a file called core.XXXX, where XXXX is the process ID of the sems
instance which just crashed. Once you have the file (should be in
/var/cores/; if not, check this page:
http://aplawrence.com/Linux/limit_core_files.html), open it with gdb and
then use the backtrace command. If you have some way of uploading the
file somewhere (>100MB), I could also inspect it myself.
For example:
# gdb /usr/sbin/sems /var/cores/core.sems.sig11.23554
....
Program terminated with signal 11, Segmentation fault.
#0 0xb7902e47 in ?? () from /usr/lib/libpython2.6.so.1.0
(gdb) bt
#0 0xb7902e47 in ?? () from /usr/lib/libpython2.6.so.1.0
#1 0xb78e0277 in PyEval_GetGlobals () from /usr/lib/libpython2.6.so.1.0
#2 0xb78fcad7 in PyImport_Import () from /usr/lib/libpython2.6.so.1.0
#3 0xb7a799b2 in PySemsFactory::import_module (this=0x9091058,
modname=0xb7a8f5d0 "sys") at PySems.cpp:191
#4 0xb7a79c9f in PySemsFactory::set_sys_path (this=0x9091058,
script_path=...) at PySems.cpp:170
#5 0xb7a7a1e4 in PySemsFactory::init_python_interpreter
(this=0x9091058, script_path=...) at PySems.cpp:213
#6 0xb7a7c6ea in PySemsFactory::onLoad (this=0x9091058) at PySems.cpp:417
#7 0x080d2911 in AmPlugIn::load (this=0x9091490, directory=...,
plugins=...) at AmPlugIn.cpp:305
#8 0x08075b61 in main (argc=6, argv=0xbfa1c024) at sems.cpp:465
(The output above shows what happens with py_sems on debian squeeze.)
Cheers
Raphael.
_______________________________________________
Semsdev mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/semsdev
