Issue 1205436: Bugfix for signal-handler on x64 Platform (original) (raw)
Issue1205436
This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.
This issue has been migrated to GitHub: https://github.com/python/cpython/issues/41997
classification
Title: | Bugfix for signal-handler on x64 Platform | ||
---|---|---|---|
Type: | Stage: | ||
Components: | Interpreter Core | Versions: | Python 2.4 |
process
Status: | closed | Resolution: | out of date |
---|---|---|---|
Dependencies: | Superseder: | ||
Assigned To: | Nosy List: | computercrustie, loewis, mwh, nnorwitz | |
Priority: | normal | Keywords: | patch |
Created on 2005-05-20 05:21 by computercrustie, last changed 2022-04-11 14:56 by admin. This issue is now closed.
Files | |||
---|---|---|---|
File name | Uploaded | Description | Edit |
pythonrun.c | computercrustie,2005-05-20 05:21 |
Messages (4) | ||
---|---|---|
msg48368 - (view) | Author: André Fritzsche (computercrustie) | Date: 2005-05-20 05:21 |
On x64 Platform (i used Visual Studio 2005 and Windows XP x64) the python.exe hang up on registering signal handler for none used signals. I fixed this on my machine with a switch-case construct for filtering the unsupported signals. | ||
msg48369 - (view) | Author: Michael Hudson (mwh) ![]() |
Date: 2005-05-20 11:09 |
Logged In: YES user_id=6656 Point the first: please attach patches, not files. Point the second: we think this is a microsoft bug. Quoting C99 (about the signal function): If the request can be honored, the signal function returns the value of func for the most recent successful call to signal for the specified signal sig. Otherwise, a value of SIG_ERR is returned and a positive value is stored in errno. That doesn't seem to allow calling abort(). As I think VS 2005 is still in beta, there's still hope that this will get fixed. | ||
msg48370 - (view) | Author: Neal Norwitz (nnorwitz) * ![]() |
Date: 2005-12-18 22:30 |
Logged In: YES user_id=33168 I believe this was fixed recently. Can you verify it works for you now? | ||
msg48371 - (view) | Author: Martin v. Löwis (loewis) * ![]() |
Date: 2006-04-15 08:52 |
Logged In: YES user_id=21627 nnorwitz is right: this was fixed (worked-around) with 1350409:; so closing this out-of-date. |
History | |||
---|---|---|---|
Date | User | Action | Args |
2022-04-11 14:56:11 | admin | set | github: 41997 |
2005-05-20 05:21:41 | computercrustie | create |