[issue1755388] Problem with socket.gethostbyaddr() and KeyboardInterrupt

[Gabriel Genellina]

Gabriel Genellina <[EMAIL PROTECTED]> added the comment:

Yes, I know it's a bug, and certainly closing this report won't help 
solve it. I can't reopen this.

___
Python tracker <[EMAIL PROTECTED]>

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

[issue1755388] Problem with socket.gethostbyaddr() and KeyboardInterrupt

[STINNER Victor]

STINNER Victor <[EMAIL PROTECTED]> added the comment:

@gagenellina: It's a bug! Python does raise a KeyboardInterrupt 
exception, but too late. The exception is raised during the 
gethostbyaddr() so I expect to get a KeyboardInterrupt just after 
gethostbyaddr().

___
Python tracker <[EMAIL PROTECTED]>

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

[issue1755388] Problem with socket.gethostbyaddr() and KeyboardInterrupt

[Gabriel Genellina]

Changes by Gabriel Genellina <[EMAIL PROTECTED]>:


--
components: +Library (Lib) -Interpreter Core

___
Python tracker <[EMAIL PROTECTED]>

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

[issue1755388] Problem with socket.gethostbyaddr() and KeyboardInterrupt

[Gabriel Genellina]

Gabriel Genellina <[EMAIL PROTECTED]> added the comment:

I think that closing it as wontfix is not the proper thing to do. It 
is a real bug; closing it will hide it from anybody that could 
potentially fix it. Also it won't appear on bug listings unless you 
explicitely ask for closed ones. 

Setting the right categories might help.

--
components: +Interpreter Core -Extension Modules
type:  -> behavior
versions: +Python 2.6, Python 3.0 -Python 2.5
Added file: http://bugs.python.org/file12117/bug1755388.py

___
Python tracker <[EMAIL PROTECTED]>

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

[issue1755388] Problem with socket.gethostbyaddr() and KeyboardInterrupt

[STINNER Victor]

Changes by STINNER Victor <[EMAIL PROTECTED]>:


--
resolution:  -> wont fix
status: open -> closed

___
Python tracker <[EMAIL PROTECTED]>

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

[issue1755388] Problem with socket.gethostbyaddr() and KeyboardInterrupt

[STINNER Victor]

STINNER Victor <[EMAIL PROTECTED]> added the comment:

I don't know how to fix the bug and it looks like nobody cares about 
it. So I prefer to close it. Reopen it if you get the same error.

Added file: http://bugs.python.org/file12114/hostname.py

___
Python tracker <[EMAIL PROTECTED]>

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

[issue1755388] Problem with socket.gethostbyaddr() and KeyboardInterrupt

[STINNER Victor]

STINNER Victor <[EMAIL PROTECTED]> added the comment:

Using gdb, I dig the problem:
 * when CTRL+c is pressed, signal_handler (sig_num=2) 
at ./Modules/signalmodule.c:175 is called
 * signal_handler() stores the signal has a "pending call"
 * Linux kernel interrupts its name resolution (it looks like it's the 
read() syscall?) and return the error ETIMEDOUT (110)
 * back to socket_gethostbyaddr(): result=110, h=NULL
 * gethost_common() set an error using set_herror(1)
 * socket_gethostbyaddr() return NULL

Later, Py_MakePendingCalls() will call signal_default_int_handler() 
which raises the KeyboardInterrupt.

___
Python tracker <[EMAIL PROTECTED]>

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