On Fri, Sep 5, 2008 at 3:50 PM, Maric Michaud <[EMAIL PROTECTED]> wrote:
> Le Friday 05 September 2008 15:04:22 Marco Bizzarri, vous avez écrit :
>> Hi all.
>>
>> I'm experiencing a core dump while working in the following environment
>>
>> - debain etch
>> - python2.3
>> - openoffice.org 2.4
>> - Zope 2.8.8
>>
>> I was able to get a core dump, and the backtrace shows the following:
>>
>> Core was generated by `python2.3 tests/testActs.py'.
>> Program terminated with signal 11, Segmentation fault.
>> #0 0xb6b5219c in ?? () from /usr/lib/openoffice/program/libuno_cppu.so.3
> ... lot of backtrace ...
>> #9 0xb68c76c7 in ?? () from /usr/lib/openoffice/program/libuno_sal.so.3
>> #10 0x08797840 in ?? ()
>> #11 0x0989b6e0 in ?? ()
>> #12 0x00000000 in ?? ()
>>
>> Now, I can understand that the information I provided are not enough
>> to give me suggestions on solving this issue; so, I'm asking
>> suggesions on investigating the issue, namely:
>>
>> - should I ask here or is it better if I ask on a openoffice forum?
>
> Yes.
Ok
>> - should I use a debug-enabled python in order to have more meaningful
>> backtraces?
>
> What you need is more a debug enabled version of pyuno libraries.
Ok; I will check with the openoffice guys, then.
>> - is there something else I should do in order to have more clues
>> ("Read The Fine Manual (tm)" is an acceptable answer)
>
> You can try to find which function call exactly provoke the exception, the
> simplest way is to trace execution flow with some print statments and using
> non forking zope instance (runzope -d if I remember well).
>
Ok; just for completeness, this is not a running zope application, it
is a ZopeTestCase which is causing me the trouble. And, as usual, it
does not cause it always :-)
Regards
Marco
--
Marco Bizzarri
http://notenotturne.blogspot.com/
http://iliveinpisa.blogspot.com/
--
http://mail.python.org/mailman/listinfo/python-list
