[issue45825] Heap Segmentation Fault
Bill Borskey
report at bugs.python.org
Wed Nov 17 10:11:42 EST 2021
Bill Borskey <wborskey at gmail.com> 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 in case you wanted to fix it.
Cheers
> On Nov 17, 2021, at 6:08 AM, Zachary Ware <report at bugs.python.org> wrote:
>
>
> Zachary Ware <zachary.ware at gmail.com> 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 a random memory address to ctypes is likely to cause segfaults or worse.
>
> ----------
> nosy: +zach.ware
> resolution: -> not a bug
> status: open -> pending
>
> _______________________________________
> Python tracker <report at bugs.python.org>
> <https://bugs.python.org/issue45825>
> _______________________________________
----------
status: pending -> open
_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue45825>
_______________________________________
More information about the Python-bugs-list
mailing list