[ python-Bugs-1311784 ] python.exe 2.4.2 compiled with VS2005 crashes
SourceForge.net
noreply at sourceforge.net
Mon Oct 3 21:54:36 CEST 2005
Bugs item #1311784, was opened at 2005-10-03 05:18
Message generated for change (Comment added) made by nnorwitz
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1311784&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: Windows
Group: Python 2.4
Status: Open
Resolution: None
Priority: 5
Submitted By: Peter Klotz (pete_icoserve)
Assigned to: Nobody/Anonymous (nobody)
Summary: python.exe 2.4.2 compiled with VS2005 crashes
Initial Comment:
The C runtime library shipped with Visual Studio 2005
performs strict checking of parameters.
In function initsignal() in file
Modules\signalmodule.c, an iteration over all signals
from 1 to NSIG is performed.
The function PyOS_getsig() is called with each of these
integer values. PyOS_getsig() then calls signal() with
the given value which leads to the crash.
According to signal.h from VS2005 only these signals
are allowed:
#define SIGINT 2
#define SIGILL 4
#define SIGABRT_COMPAT 6
#define SIGFPE 8
#define SIGSEGV 11
#define SIGTERM 15
#define SIGBREAK 21
#define SIGABRT 22
A solution would be to restrict the loop in
initsignal() to the above values under Windows.
----------------------------------------------------------------------
>Comment By: Neal Norwitz (nnorwitz)
Date: 2005-10-03 12:54
Message:
Logged In: YES
user_id=33168
Do you suggest this be special cased for VS2005 specifically
or Windows in general (ie, any version/compiler)?
----------------------------------------------------------------------
Comment By: Peter Klotz (pete_icoserve)
Date: 2005-10-03 11:10
Message:
Logged In: YES
user_id=299547
VS2005 is still not released.
It is scheduled for November 7th 2005. I tested with CTP
(Community Technology Preview) August 2005.
However I doubt they will change the behavior of their C library
at this point of development.
----------------------------------------------------------------------
Comment By: Michael Hudson (mwh)
Date: 2005-10-03 06:05
Message:
Logged In: YES
user_id=6656
Is VS2005 actually out now then? This behaviour violates the C standard,
as far as we can tell, so we when VS2005 was in beta we hoped that they
would fix it for the final release.
If it is released, though, I guess we need to do something like you suggest
(along with some colourful comments, I guess).
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1311784&group_id=5470
More information about the Python-bugs-list
mailing list