snacktime wrote:
After debugging this some more I narrowed it down to an encryption
function in pycrypto that is triggering the segfault. I posted a bug
report. Don't really know enough about threading to know whether it's
a python bug or a pycrypto bug, but I'll let someone else sort that
out no
After debugging this some more I narrowed it down to an encryption
function in pycrypto that is triggering the segfault. I posted a bug
report. Don't really know enough about threading to know whether it's
a python bug or a pycrypto bug, but I'll let someone else sort that
out now..
Chris
--
ht
This is a followup with some more information. The program is written
in twisted and I posted this to twisted-python also. The freebsd list
wants a more detailed backtrace, which even with python compiled with
OPT -g and --with-pydebug isn't happening for some reason.
The script below calls a bl
snacktime wrote:
> I am consistantly getting seg faults and bus errors when running a
> multi threaded python application under 5.3-release-p2. Python was
> built from the port(python 2.4) with threading enabled.
I had similar problems some time ago. The solution/workaround was to remove
the thre
I posted this to freebsd-questions, but though I would put it here
also in case anyone has any ideas.
I am consistantly getting seg faults and bus errors when running a
multi threaded python application under 5.3-release-p2. Python was
built from the port(python 2.4) with threading enabled. Rebu
