Strange segfault in extension

[Berthold Höllmann]

I have an extension that, where calling a function, generates an
segmentatin fault. This is nothing new for me, but I stumbled over the
backtrace in gdb. Why is "args" getting the address 0x1? Is this
possible?

Here is the top of my Backtrace

#0  0xfe4069f0 in LexSrt_method (self=0x0, args=0x1) at module/LexSrt.c:73
#1  0xaea38 in PyCFunction_Call (func=0x1c43f0, arg=0x274c30, kw=0x0)
    at Objects/methodobject.c:80
#2  0x4abb4 in eval_frame (f=0x30d3f8) at Python/ceval.c:2004

Thanks for your help

Berthold
-- 
Dipl.-Ing. Berthold Höllmann   __   Address:       
hoel at germanlloyd.org        G /  \ L Germanischer Lloyd
phone: +49-40-36149-7374    -+----+- Vorsetzen 32/35    P.O.Box 111606
fax  : +49-40-36149-7320      \__/   D-20459 Hamburg    D-20416 Hamburg