Bill Borskey added the comment:
No worries. I find bugs in my day job, thought this might be a useful segfault
but it segfaults because it’s incrementing that reference count on the pyobj
that don’t exist. So pretty lame. I did spend an hour tracking it down so I
thought I’d let y’all know
Zachary Ware added the comment:
In general, as soon as you touch ctypes you're on your own :). ctypes has no
protections for this kind of case, so you need to protect yourself.
If you came across this some way that *should* have been safe, please provide
more information. But just passing
New submission from Bill Borskey :
Dereferencing a python object that does not exist through ctypes caused a
segfault in pymalloc_alloc.
rdi: 0x0006 rsi: 0x0006
0 org.python.python 0x0001081ee277 pymalloc_alloc + 74
1 org.python.python
