[issue37013] Fatal Python error in socket.if_indextoname()

2021-10-17 Thread Irit Katriel


Change by Irit Katriel :


--
versions: +Python 3.10, Python 3.11, Python 3.9 -Python 3.7, Python 3.8

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue37013] Fatal Python error in socket.if_indextoname()

2019-05-22 Thread Zackery Spytz


Change by Zackery Spytz :


--
keywords: +patch
pull_requests: +13418
stage:  -> patch review

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue37013] Fatal Python error in socket.if_indextoname()

2019-05-22 Thread Zackery Spytz


New submission from Zackery Spytz :

Python 3.8.0a4+ (heads/master:ef9d9b6312, May 22 2019, 08:35:25) 
[GCC 9.0.1 20190402 (experimental) [trunk revision 270074]] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import socket
>>> socket.if_indextoname(2**64 - 1)
Fatal Python error: a function returned NULL without setting an error
SystemError:  returned NULL without setting 
an error

Current thread 0x7f29d708d140 (most recent call first):
  File "", line 1 in 
Aborted (core dumped)

This is because socket.if_indextoname() does not use PyErr_Occurred() when 
checking PyLong_AsUnsignedLong() for failure.

--
components: Extension Modules
messages: 343215
nosy: ZackerySpytz, serhiy.storchaka, vstinner
priority: normal
severity: normal
status: open
title: Fatal Python error in socket.if_indextoname()
type: crash
versions: Python 3.7, Python 3.8

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com