[ python-Bugs-1167262 ] Fails assertion in winsig.c under VC 8.0
SourceForge.net
noreply at sourceforge.net
Fri Nov 18 17:10:35 CET 2005
Bugs item #1167262, was opened at 2005-03-21 03:25
Message generated for change (Comment added) made by varmaa
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1167262&group_id=5470
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Python Library
Group: Python 2.5
Status: Open
Resolution: None
Priority: 5
Submitted By: Timothy Fitz (timothyfitz)
Assigned to: Nobody/Anonymous (nobody)
Summary: Fails assertion in winsig.c under VC 8.0
Initial Comment:
In 2.4 and current cvs initsignal in signalmodule.c calls
PyOS_getsig which calls signal with an invalid signal
number. Under VC 7.1 (and 7.0, and probably before)
this would return SIG_ERR however under VC 8.0 (beta)
this causes an assertion failure.
----------------------------------------------------------------------
Comment By: Atul Varma (varmaa)
Date: 2005-11-18 16:10
Message:
Logged In: YES
user_id=863202
Just wanted to mention that the Visual Studio 2005 products
were officially launched on November 7th, 2005, and this
same problem occurs when compiling the Python 2.4 source
using Visual C++ 2005 Express Edition.
----------------------------------------------------------------------
Comment By: Martin v. Löwis (loewis)
Date: 2005-10-12 07:54
Message:
Logged In: YES
user_id=21627
See #1311784 for more discussion of this problem.
----------------------------------------------------------------------
Comment By: Martin v. Löwis (loewis)
Date: 2005-04-01 22:02
Message:
Logged In: YES
user_id=21627
C99 7.14.1.1/p8 specifies
# 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.
So it seems to me that VC8 is in error: the request cannot
be "honored", so it should return SIG_ERR. Until/if VC8 is
released with that bug, I would like to take no action here.
When it is released, we still might consider to ignore it until
say, 8.1 comes along and fixes the bug.
----------------------------------------------------------------------
Comment By: Michael Hudson (mwh)
Date: 2005-03-27 20:59
Message:
Logged In: YES
user_id=6656
Ew. My first thought is, is that allowed by ANSI C? I'd guess it's
undefined behaviour. It still seems excessively unfriendly -- have you
reported this to MS?
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1167262&group_id=5470
More information about the Python-bugs-list
mailing list