Re: SIGSEGV and SIGILL inside PyCFunction_Call

2017-07-20 Thread dieter
Anders Wegge Keller writes: > ... > The trouble with that is that nnrpd is a system daemon, and as such is a > bit difficult to trace in place. That's why I am asking for help Often, you can run a (typical) daemon in non-daemon mode -- specifically to debug problems (a usual requirement during d

Re: SIGSEGV and SIGILL inside PyCFunction_Call

2017-07-20 Thread Anders Wegge Keller
På Thu, 20 Jul 2017 07:44:26 +0200 dieter skrev: > Anders Wegge Keller writes: ... >> Weird observation #1: Sometimes the reason is SIGSEGV, sometimes it's >> SIGILL. > Python tends to be sensitive to the stack size. In previous times, > there have often be problems because the stack size

Re: SIGSEGV and SIGILL inside PyCFunction_Call

2017-07-19 Thread dieter
Anders Wegge Keller writes: > ... > I have an ongoing issue with my usenet setup. I'm that one dude who don't > want to learn perl. That means that I have to build inn from source, so I > can enable the python interpreter. That's not so bad, and the errors that > show up have been something that

SIGSEGV and SIGILL inside PyCFunction_Call

2017-07-19 Thread Anders Wegge Keller
I have an ongoing issue with my usenet setup. I'm that one dude who don't want to learn perl. That means that I have to build inn from source, so I can enable the python interpreter. That's not so bad, and the errors that show up have been something that I have been able to figure out by myself. A