FAQ
Python 3.1.1 in Windows XP Prof:


<code filename="sum.v4.py" language="Py3">
def number_from_user( prompt ):
while True:
spec = input( prompt )
try:
return float( spec )
except ValueError:
s = "Sorry, '{}' is not a valid number spec. Try e.g. '3.14'."
print( s.format( spec ) )
print()

print( "This program computes the sum of two numbers A and B." )
print()
a = number_from_user( "Number A, please: " )
b = number_from_user( "Number B, please: " )
sum = a + b
print()
print( "{} + {} = {}".format( a, b, sum ) )
</code>


To be thorough I tested the reaction to typing [Ctrl C] at the first prompt. It
then displayed the first part of traceback output,


<output part="1">
C:\Documents and Settings\Alf> sum.v4.py
This program computes the sum of two numbers A and B.

Number A, please: Traceback (most recent call last):
</output>


and seemingly hung for, I don't know, 20 seconds?, whereupon Microsoft's "Please
tell Bill Gates about it" box popped up; the interpreter had crashed.

Regretfully declining the offer to tell Bill Gates, and this I don't quite
understand, possibly buffer thing?, one more line of output then appeared:


<output part="2">
File "C:\Documents and Settings\Alf\sum.v4.py", line 13, in <module>

C:\Documents and Settings\Alf> _
</output>


In a normal traceback there are four more lines.

I thought I'd report this so I tried it several times more but unable to
reproduce: instead of above hang + crash + truncated traceback the complete
expected traceback appeared and the program terminated properly.

Can anyone reproduce?


Cheers,

- Alf

Search Discussions

  • MRAB at Apr 16, 2010 at 11:29 am

    Alf P. Steinbach wrote:
    Python 3.1.1 in Windows XP Prof:


    <code filename="sum.v4.py" language="Py3">
    def number_from_user( prompt ):
    while True:
    spec = input( prompt )
    try:
    return float( spec )
    except ValueError:
    s = "Sorry, '{}' is not a valid number spec. Try e.g. '3.14'."
    print( s.format( spec ) )
    print()

    print( "This program computes the sum of two numbers A and B." )
    print()
    a = number_from_user( "Number A, please: " )
    b = number_from_user( "Number B, please: " )
    sum = a + b
    print()
    print( "{} + {} = {}".format( a, b, sum ) )
    </code>


    To be thorough I tested the reaction to typing [Ctrl C] at the first
    prompt. It then displayed the first part of traceback output,


    <output part="1">
    C:\Documents and Settings\Alf> sum.v4.py
    This program computes the sum of two numbers A and B.

    Number A, please: Traceback (most recent call last):
    </output>


    and seemingly hung for, I don't know, 20 seconds?, whereupon Microsoft's
    "Please tell Bill Gates about it" box popped up; the interpreter had
    crashed.

    Regretfully declining the offer to tell Bill Gates, and this I don't
    quite understand, possibly buffer thing?, one more line of output then
    appeared:


    <output part="2">
    File "C:\Documents and Settings\Alf\sum.v4.py", line 13, in <module>

    C:\Documents and Settings\Alf> _
    </output>


    In a normal traceback there are four more lines.

    I thought I'd report this so I tried it several times more but unable to
    reproduce: instead of above hang + crash + truncated traceback the
    complete expected traceback appeared and the program terminated properly.

    Can anyone reproduce?
    I also have Python 3.1.1 on Windows XP Professional, but it doesn't
    crash for me!

    Does it happen every time?
  • Lie Ryan at Apr 16, 2010 at 11:42 am

    On 04/16/10 21:29, MRAB wrote:
    Alf P. Steinbach wrote:
    I thought I'd report this so I tried it several times more but unable
    to reproduce: instead of above hang + crash + truncated traceback the
    complete expected traceback appeared and the program terminated properly.

    Can anyone reproduce?
    I also have Python 3.1.1 on Windows XP Professional, but it doesn't
    crash for me!

    Does it happen every time?
    I believe Alf said it happened once only and he himself cannot reproduce it.

    btw, Alf, did you happen to Ctrl+C multiple times? Perhaps the timing of
    your interrupt happened exactly at the moment where it confused the
    interpreter. Possibly the second interrupt got received when the first
    interrupt was just part way printing the traceback.
  • Alf P. Steinbach at Apr 16, 2010 at 11:56 am

    * MRAB:
    Alf P. Steinbach wrote:
    Python 3.1.1 in Windows XP Prof:


    <code filename="sum.v4.py" language="Py3">
    def number_from_user( prompt ):
    while True:
    spec = input( prompt )
    try:
    return float( spec )
    except ValueError:
    s = "Sorry, '{}' is not a valid number spec. Try e.g.
    '3.14'."
    print( s.format( spec ) )
    print()

    print( "This program computes the sum of two numbers A and B." )
    print()
    a = number_from_user( "Number A, please: " )
    b = number_from_user( "Number B, please: " )
    sum = a + b
    print()
    print( "{} + {} = {}".format( a, b, sum ) )
    </code>


    To be thorough I tested the reaction to typing [Ctrl C] at the first
    prompt. It then displayed the first part of traceback output,


    <output part="1">
    C:\Documents and Settings\Alf> sum.v4.py
    This program computes the sum of two numbers A and B.

    Number A, please: Traceback (most recent call last):
    </output>


    and seemingly hung for, I don't know, 20 seconds?, whereupon
    Microsoft's "Please tell Bill Gates about it" box popped up; the
    interpreter had crashed.

    Regretfully declining the offer to tell Bill Gates, and this I don't
    quite understand, possibly buffer thing?, one more line of output then
    appeared:


    <output part="2">
    File "C:\Documents and Settings\Alf\sum.v4.py", line 13, in <module>

    C:\Documents and Settings\Alf> _
    </output>


    In a normal traceback there are four more lines.

    I thought I'd report this so I tried it several times more but unable
    to reproduce: instead of above hang + crash + truncated traceback the
    complete expected traceback appeared and the program terminated properly.

    Can anyone reproduce?
    I also have Python 3.1.1 on Windows XP Professional, but it doesn't
    crash for me!

    Does it happen every time?
    No, that's the problem, I'm unable to reproduce consistently or nearly at all.

    It just happened again (that's the second time), and this time I chose "Debug",
    firing up Visual Studio 2003 as the Just-In-Time debugger. However, and this has
    /never/ happened before, Visual Studio did not manage to catch the process state
    and reported the program as terminated.

    Here's the contents of the Visual Studio output pane:


    <vsinfo>
    'python.exe': Loaded 'C:\Program Files\cpython\python31\python.exe', No symbols
    loaded.
    'python.exe': Loaded 'C:\WINDOWS\SYSTEM32\ntdll.dll', No symbols loaded.
    'python.exe': Loaded 'C:\WINDOWS\SYSTEM32\kernel32.dll', No symbols loaded.
    'python.exe': Loaded 'C:\WINDOWS\SYSTEM32\python31.dll', No symbols loaded.
    'python.exe': Loaded 'C:\WINDOWS\SYSTEM32\user32.dll', No symbols loaded.
    'python.exe': Loaded 'C:\WINDOWS\SYSTEM32\gdi32.dll', No symbols loaded.
    'python.exe': Loaded 'C:\WINDOWS\SYSTEM32\advapi32.dll', No symbols loaded.
    'python.exe': Loaded 'C:\WINDOWS\SYSTEM32\rpcrt4.dll', No symbols loaded.
    'python.exe': Loaded 'C:\WINDOWS\SYSTEM32\shell32.dll', No symbols loaded.
    'python.exe': Loaded 'C:\WINDOWS\SYSTEM32\msvcrt.dll', No symbols loaded.
    'python.exe': Loaded 'C:\WINDOWS\SYSTEM32\shlwapi.dll', No symbols loaded.
    'python.exe': Loaded
    'C:\WINDOWS\WinSxS\x86_Microsoft.VC90.CRT_1fc8b3b9a1e18e3b_9.0.30729.1_x-ww_6f74963e\msvcr90.dll',
    No symbols loaded.
    'python.exe': Loaded 'C:\WINDOWS\SYSTEM32\imm32.dll', No symbols loaded.
    'python.exe': Loaded
    'C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.2600.2982_x-ww_ac3f9c03\comctl32.dll',
    No symbols loaded.
    'python.exe': Loaded 'C:\WINDOWS\SYSTEM32\comctl32.dll', No symbols loaded.
    'python.exe': Loaded 'C:\WINDOWS\SYSTEM32\version.dll', No symbols loaded.
    'python.exe': Loaded 'C:\WINDOWS\SYSTEM32\apphelp.dll', No symbols loaded.
    The thread 'Win32 Thread' (0xd54) has exited with code -1073740777 (0xc0000417).
    The program '[3292] python.exe: Native' has exited with code -1073740777
    (0xc0000417).
    </vsinfo>


    The error code 0xc0000417 is some custom one, not a standard Windows code.

    The crash address reported by the tell-Bill box was a low one with four zeroes
    at front, but I didn't note it because that box doesn't support copy to
    clipboard and I was sure I'd get it in Visual Studio, which I didn't.

    Is there any DLL above that shouldn't be there, like malware (it's the only
    thing I can think of, a program shouldn't retain state between invocations)?


    Cheers,

    - Alf
  • Alf P. Steinbach at Apr 16, 2010 at 12:23 pm

    * Alf P. Steinbach:
    * MRAB:
    Alf P. Steinbach wrote:
    Python 3.1.1 in Windows XP Prof:


    <code filename="sum.v4.py" language="Py3">
    def number_from_user( prompt ):
    while True:
    spec = input( prompt )
    try:
    return float( spec )
    except ValueError:
    s = "Sorry, '{}' is not a valid number spec. Try e.g.
    '3.14'."
    print( s.format( spec ) )
    print()

    print( "This program computes the sum of two numbers A and B." )
    print()
    a = number_from_user( "Number A, please: " )
    b = number_from_user( "Number B, please: " )
    sum = a + b
    print()
    print( "{} + {} = {}".format( a, b, sum ) )
    </code>


    To be thorough I tested the reaction to typing [Ctrl C] at the first
    prompt. It then displayed the first part of traceback output,


    <output part="1">
    C:\Documents and Settings\Alf> sum.v4.py
    This program computes the sum of two numbers A and B.

    Number A, please: Traceback (most recent call last):
    </output>


    and seemingly hung for, I don't know, 20 seconds?, whereupon
    Microsoft's "Please tell Bill Gates about it" box popped up; the
    interpreter had crashed.

    Regretfully declining the offer to tell Bill Gates, and this I don't
    quite understand, possibly buffer thing?, one more line of output
    then appeared:


    <output part="2">
    File "C:\Documents and Settings\Alf\sum.v4.py", line 13, in <module>

    C:\Documents and Settings\Alf> _
    </output>


    In a normal traceback there are four more lines.

    I thought I'd report this so I tried it several times more but unable
    to reproduce: instead of above hang + crash + truncated traceback the
    complete expected traceback appeared and the program terminated
    properly.

    Can anyone reproduce?
    I also have Python 3.1.1 on Windows XP Professional, but it doesn't
    crash for me!

    Does it happen every time?
    No, that's the problem, I'm unable to reproduce consistently or nearly
    at all.

    It just happened again (that's the second time), and this time I chose
    "Debug", firing up Visual Studio 2003 as the Just-In-Time debugger.
    However, and this has /never/ happened before, Visual Studio did not
    manage to catch the process state and reported the program as terminated.

    Here's the contents of the Visual Studio output pane:


    <vsinfo>
    'python.exe': Loaded 'C:\Program Files\cpython\python31\python.exe', No
    symbols loaded.
    'python.exe': Loaded 'C:\WINDOWS\SYSTEM32\ntdll.dll', No symbols loaded.
    'python.exe': Loaded 'C:\WINDOWS\SYSTEM32\kernel32.dll', No symbols loaded.
    'python.exe': Loaded 'C:\WINDOWS\SYSTEM32\python31.dll', No symbols loaded.
    'python.exe': Loaded 'C:\WINDOWS\SYSTEM32\user32.dll', No symbols loaded.
    'python.exe': Loaded 'C:\WINDOWS\SYSTEM32\gdi32.dll', No symbols loaded.
    'python.exe': Loaded 'C:\WINDOWS\SYSTEM32\advapi32.dll', No symbols loaded.
    'python.exe': Loaded 'C:\WINDOWS\SYSTEM32\rpcrt4.dll', No symbols loaded.
    'python.exe': Loaded 'C:\WINDOWS\SYSTEM32\shell32.dll', No symbols loaded.
    'python.exe': Loaded 'C:\WINDOWS\SYSTEM32\msvcrt.dll', No symbols loaded.
    'python.exe': Loaded 'C:\WINDOWS\SYSTEM32\shlwapi.dll', No symbols loaded.
    'python.exe': Loaded
    'C:\WINDOWS\WinSxS\x86_Microsoft.VC90.CRT_1fc8b3b9a1e18e3b_9.0.30729.1_x-ww_6f74963e\msvcr90.dll',
    No symbols loaded.
    'python.exe': Loaded 'C:\WINDOWS\SYSTEM32\imm32.dll', No symbols loaded.
    'python.exe': Loaded
    'C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.2600.2982_x-ww_ac3f9c03\comctl32.dll',
    No symbols loaded.
    'python.exe': Loaded 'C:\WINDOWS\SYSTEM32\comctl32.dll', No symbols loaded.
    'python.exe': Loaded 'C:\WINDOWS\SYSTEM32\version.dll', No symbols loaded.
    'python.exe': Loaded 'C:\WINDOWS\SYSTEM32\apphelp.dll', No symbols loaded.
    The thread 'Win32 Thread' (0xd54) has exited with code -1073740777
    (0xc0000417).
    The program '[3292] python.exe: Native' has exited with code -1073740777
    (0xc0000417).
    </vsinfo>


    The error code 0xc0000417 is some custom one, not a standard Windows code.

    The crash address reported by the tell-Bill box was a low one with four
    zeroes at front, but I didn't note it because that box doesn't support
    copy to clipboard and I was sure I'd get it in Visual Studio, which I
    didn't.
    I managed to crash it a third time. Same problem with JIT debugging, but this
    time I noted manually some info from the tell-Bill box:


    <info>
    AppName: python.exe
    AppVer: 0.0.0.0
    ModName: msvcr90.dll
    ModVer: 9.0.30729.1
    Offset: 00068389

    (Error Report Contents)
    Code: 0xc0000417
    Address: 0x0000000078588389
    </info>


    The tell-Bill box also reported more modules loaded than Visual Studio, but I
    think that has to do with the box itself:


    <modules>
    Module 1 python.exe
    Module 2 ntdll.dll
    Module 3 kernel32.dll
    Module 4 python31.dll
    Module 5 USER32.dll
    Module 6 GDI32.dll
    Module 7 ADVAPI32.dll
    Module 7 RPCRT4.dll
    Module 9 SHELL32.dll
    Module 10 msvcrt.dll
    Module 11 SHLWAPI.dll
    Module 12 MSVCR90.dll
    Module 13 IMM32.dll
    Module 14 comctl32.dll (FileVer 6.0:2900.2982)
    Module 15 comctl32.dll (FileVer 5.82:2900.2982)
    Module 16 faultrep.dll
    Module 17 VERSION.dll
    Module 18 USERENV.dll
    Module 19 WINSTA.dll
    Module 20 NETAPI32.dll
    Module 21 WTSAPI32.dll
    Module 22 SETUPAPI.dll
    Module 23 Apphelp.dll
    </modules>


    Finally, the box said that if I sent the report the following file would be
    attached:


    <file path="c:\windows\temp\8da7_appcompat.txt>
    <?xml version="1.0" encoding="UTF-16"?>
    <DATABASE>
    <EXE NAME="python.exe" FILTER="GRABMI_FILTER_PRIVACY">
    <MATCHING_FILE NAME="py3.exe" SIZE="26624" CHECKSUM="0xC55CD69D"
    MODULE_TYPE="WIN32" PE_CHECKSUM="0xFE8F" LINKER_VERSION="0x0"
    LINK_DATE="08/17/2009 15:03:45" UPTO_LINK_DATE="08/17/2009 15:03:45" />
    <MATCHING_FILE NAME="python.exe" SIZE="26624" CHECKSUM="0xC55CD69D"
    MODULE_TYPE="WIN32" PE_CHECKSUM="0xFE8F" LINKER_VERSION="0x0"
    LINK_DATE="08/17/2009 15:03:45" UPTO_LINK_DATE="08/17/2009 15:03:45" />
    <MATCHING_FILE NAME="pythonw.exe" SIZE="27136" CHECKSUM="0xA5DBF284"
    MODULE_TYPE="WIN32" PE_CHECKSUM="0xE6C7" LINKER_VERSION="0x0"
    LINK_DATE="08/17/2009 15:04:36" UPTO_LINK_DATE="08/17/2009 15:04:36" />
    <MATCHING_FILE NAME="pyw3.exe" SIZE="27136" CHECKSUM="0xA5DBF284"
    MODULE_TYPE="WIN32" PE_CHECKSUM="0xE6C7" LINKER_VERSION="0x0"
    LINK_DATE="08/17/2009 15:04:36" UPTO_LINK_DATE="08/17/2009 15:04:36" />
    <MATCHING_FILE NAME="w9xpopen.exe" SIZE="49664" CHECKSUM="0x4E298DA0"
    MODULE_TYPE="WIN32" PE_CHECKSUM="0x13E30" LINKER_VERSION="0x0"
    LINK_DATE="08/13/2009 17:55:13" UPTO_LINK_DATE="08/13/2009 17:55:13" />
    <MATCHING_FILE NAME="DLLs\sqlite3.dll" SIZE="302080" CHECKSUM="0x20195FFD"
    MODULE_TYPE="WIN32" PE_CHECKSUM="0x4F4DD" LINKER_VERSION="0x0"
    LINK_DATE="08/13/2009 17:57:11" UPTO_LINK_DATE="08/13/2009 17:57:11" />
    <MATCHING_FILE NAME="DLLs\tcl85.dll" SIZE="867328" CHECKSUM="0xCF388F56"
    BIN_FILE_VERSION="8.5.2.2" BIN_PRODUCT_VERSION="8.5.2.2" PRODUCT_VERSION="8.5.2"
    FILE_DESCRIPTION="Tcl DLL" COMPANY_NAME="ActiveState Corporation"
    PRODUCT_NAME="Tcl 8.5 for Windows" FILE_VERSION="8.5.2"
    ORIGINAL_FILENAME="tcl85.dll" LEGAL_COPYRIGHT="Copyright ? 2001 by ActiveState
    Corporation, et al" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x4"
    VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0xDDCB1" LINKER_VERSION="0x0"
    UPTO_BIN_FILE_VERSION="8.5.2.2" UPTO_BIN_PRODUCT_VERSION="8.5.2.2"
    LINK_DATE="11/06/2008 19:29:15" UPTO_LINK_DATE="11/06/2008 19:29:15"
    VER_LANGUAGE="English (United States) [0x409]" />
    <MATCHING_FILE NAME="DLLs\tclpip85.dll" SIZE="8192" CHECKSUM="0x13EA3659"
    MODULE_TYPE="WIN32" PE_CHECKSUM="0xBCF1" LINKER_VERSION="0x0"
    LINK_DATE="06/12/2008 16:15:39" UPTO_LINK_DATE="06/12/2008 16:15:39" />
    <MATCHING_FILE NAME="DLLs\tk85.dll" SIZE="1319936" CHECKSUM="0x499C647D"
    BIN_FILE_VERSION="8.5.2.2" BIN_PRODUCT_VERSION="8.5.2.2" PRODUCT_VERSION="8.5.2"
    FILE_DESCRIPTION="Tk DLL" COMPANY_NAME="ActiveState Corporation"
    PRODUCT_NAME="Tk 8.5 for Windows" FILE_VERSION="8.5.2"
    ORIGINAL_FILENAME="tk85.dll" LEGAL_COPYRIGHT="Copyright ? 2001 by ActiveState
    Corporation, et al" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x4"
    VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x145825"
    LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="8.5.2.2"
    UPTO_BIN_PRODUCT_VERSION="8.5.2.2" LINK_DATE="11/06/2008 19:37:30"
    UPTO_LINK_DATE="11/06/2008 19:37:30" VER_LANGUAGE="English (United States)
    [0x409]" />
    <MATCHING_FILE NAME="Lib\distutils\command\wininst-6.0.exe" SIZE="61440"
    CHECKSUM="0xE589B8AD" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0"
    LINK_DATE="05/31/2008 04:52:45" UPTO_LINK_DATE="05/31/2008 04:52:45" />
    <MATCHING_FILE NAME="Lib\distutils\command\wininst-7.1.exe" SIZE="65536"
    CHECKSUM="0xA2833DFD" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0"
    LINK_DATE="05/31/2008 04:53:42" UPTO_LINK_DATE="05/31/2008 04:53:42" />
    <MATCHING_FILE NAME="Lib\distutils\command\wininst-8.0.exe" SIZE="61440"
    CHECKSUM="0x8527B654" MODULE_TYPE="WIN32" PE_CHECKSUM="0x1701B"
    LINKER_VERSION="0x0" LINK_DATE="10/04/2006 15:16:27" UPTO_LINK_DATE="10/04/2006
    15:16:27" />
    <MATCHING_FILE NAME="Lib\distutils\command\wininst-9.0-amd64.exe"
    SIZE="224256" CHECKSUM="0x2C21FF43" MODULE_TYPE="WIN32" PE_CHECKSUM="0x3C5B1"
    LINKER_VERSION="0x0" LINK_DATE="01/29/2009 13:03:06" UPTO_LINK_DATE="01/29/2009
    13:03:06" />
    <MATCHING_FILE NAME="Lib\distutils\command\wininst-9.0.exe" SIZE="196096"
    CHECKSUM="0x4C294F6E" MODULE_TYPE="WIN32" PE_CHECKSUM="0x3C5CF"
    LINKER_VERSION="0x0" LINK_DATE="01/29/2009 13:02:55" UPTO_LINK_DATE="01/29/2009
    13:02:55" />
    <MATCHING_FILE NAME="tcl\dde1.3\tcldde13.dll" SIZE="18944"
    CHECKSUM="0x5F6F6F2F" MODULE_TYPE="WIN32" PE_CHECKSUM="0x138A6"
    LINKER_VERSION="0x0" LINK_DATE="06/12/2008 19:01:43" UPTO_LINK_DATE="06/12/2008
    19:01:43" />
    <MATCHING_FILE NAME="tcl\reg1.2\tclreg12.dll" SIZE="18432"
    CHECKSUM="0xBEEC9FAD" MODULE_TYPE="WIN32" PE_CHECKSUM="0xC2A5"
    LINKER_VERSION="0x0" LINK_DATE="06/12/2008 19:01:42" UPTO_LINK_DATE="06/12/2008
    19:01:42" />
    <MATCHING_FILE NAME="tcl\tix8.4.3\tix84.dll" SIZE="262656"
    CHECKSUM="0x3E0EAE66" MODULE_TYPE="WIN32" PE_CHECKSUM="0x4825B"
    LINKER_VERSION="0x0" LINK_DATE="02/13/2009 17:17:04" UPTO_LINK_DATE="02/13/2009
    17:17:04" />
    </EXE>
    <EXE NAME="MSVCR90.dll" FILTER="GRABMI_FILTER_THISFILEONLY">
    <MATCHING_FILE NAME="msvcr90.dll" SIZE="655872" CHECKSUM="0xA8551049"
    BIN_FILE_VERSION="9.0.30729.1" BIN_PRODUCT_VERSION="9.0.30729.1"
    PRODUCT_VERSION="9.00.30729.1" FILE_DESCRIPTION="Microsoft? C Runtime Library"
    COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft? Visual Studio?
    2008" FILE_VERSION="9.00.30729.1" ORIGINAL_FILENAME="MSVCR90.DLL"
    INTERNAL_NAME="MSVCR90.DLL" LEGAL_COPYRIGHT="? Microsoft Corporation. All
    rights reserved." VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x40004"
    VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0xA6621"
    LINKER_VERSION="0x90000" UPTO_BIN_FILE_VERSION="9.0.30729.1"
    UPTO_BIN_PRODUCT_VERSION="9.0.30729.1" LINK_DATE="07/29/2008 10:53:57"
    UPTO_LINK_DATE="07/29/2008 10:53:57" VER_LANGUAGE="English (United States)
    [0x409]" />
    </EXE>
    <EXE NAME="kernel32.dll" FILTER="GRABMI_FILTER_THISFILEONLY">
    <MATCHING_FILE NAME="kernel32.dll" SIZE="986112" CHECKSUM="0x359DA0B2"
    BIN_FILE_VERSION="5.1.2600.3541" BIN_PRODUCT_VERSION="5.1.2600.3541"
    PRODUCT_VERSION="5.1.2600.3541" FILE_DESCRIPTION="Windows NT BASE API Client
    DLL" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft? Windows?
    Operating System" FILE_VERSION="5.1.2600.3541 (xpsp_sp2_gdr.090321-1320)"
    ORIGINAL_FILENAME="kernel32" INTERNAL_NAME="kernel32" LEGAL_COPYRIGHT="?
    Microsoft Corporation. All rights reserved." VERFILEDATEHI="0x0"
    VERFILEDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32"
    PE_CHECKSUM="0xFEAFF" LINKER_VERSION="0x50001"
    UPTO_BIN_FILE_VERSION="5.1.2600.3541" UPTO_BIN_PRODUCT_VERSION="5.1.2600.3541"
    LINK_DATE="03/21/2009 14:18:57" UPTO_LINK_DATE="03/21/2009 14:18:57"
    VER_LANGUAGE="English (United States) [0x409]" />
    </EXE>
    </DATABASE>
    </file>


    Cheers,

    - Alf (baffled)
  • Alf P. Steinbach at Apr 16, 2010 at 12:49 pm
    * Alf P. Steinbach:
    >
    [About baffling almost not reproducible interpreter crash on Ctrl C]
    The error code 0xc0000417 is some custom one, not a standard Windows code.
    Sorry, I was wrong about that, just that the MS ErrLook utility didn't find it.

    <url:
    http://social.msdn.microsoft.com/Forums/en-US/vsdebug/thread/2d0577ec-562a-498d-af66-0177a3f2e52c>

    says it's


    STATUS_INVALID_CRUNTIME_PARAMETER
    #An invalid parameter was passed to a C runtime function.


    defined in [ntstatus.h].


    Cheers,

    - Alf
  • Alf P. Steinbach at Apr 16, 2010 at 1:06 pm

    * Alf P. Steinbach:
    * Alf P. Steinbach:
    [About baffling almost not reproducible interpreter crash on Ctrl C]
    The error code 0xc0000417 is some custom one, not a standard Windows
    code.
    Sorry, I was wrong about that, just that the MS ErrLook utility didn't
    find it.

    <url:
    http://social.msdn.microsoft.com/Forums/en-US/vsdebug/thread/2d0577ec-562a-498d-af66-0177a3f2e52c>


    says it's


    STATUS_INVALID_CRUNTIME_PARAMETER
    #An invalid parameter was passed to a C runtime function.


    defined in [ntstatus.h].
    Found a another bug discussion with

    * same exception,
    0xc0000417 STATUS_INVALID_CRUNTIME_PARAMETER

    * same address,
    0x78588389

    * almost same Python version,
    namely Py3,

    * almost same context,
    namely occurring when program terminates,

    at

    <url: http://www.mail-archive.com/pyinstaller at googlegroups.com/msg01564.html>

    Can I report a bug with so little information -- not generally reproducible,
    but hey, someone else has seen something nearly identical?


    Cheers,

    - Alf
  • Alf P. Steinbach at Apr 16, 2010 at 1:50 pm
    * Alf P. Steinbach:
    Found a another bug discussion with

    * same exception,
    0xc0000417 STATUS_INVALID_CRUNTIME_PARAMETER

    * same address,
    0x78588389

    * almost same Python version,
    namely Py3,

    * almost same context,
    namely occurring when program terminates,

    at

    <url:
    http://www.mail-archive.com/pyinstaller at googlegroups.com/msg01564.html>

    Can I report a bug with so little information -- not generally
    reproducible, but hey, someone else has seen something nearly identical?
    OK, I did, <url: http://bugs.python.org/issue8418>.


    Cheers,

    - Alf
  • Terry Reedy at Apr 16, 2010 at 7:10 pm

    On 4/16/2010 9:50 AM, Alf P. Steinbach wrote:
    * Alf P. Steinbach:
    Found a another bug discussion with

    * same exception,
    0xc0000417 STATUS_INVALID_CRUNTIME_PARAMETER

    * same address,
    0x78588389

    * almost same Python version,
    namely Py3,

    * almost same context,
    namely occurring when program terminates,

    at

    <url:
    http://www.mail-archive.com/pyinstaller at googlegroups.com/msg01564.html>

    Can I report a bug with so little information -- not generally
    reproducible, but hey, someone else has seen something nearly identical?
    OK, I did, <url: http://bugs.python.org/issue8418>.
    Good report. I might have just dismissed this as a random windows bug ;-).

    Terry Jan Reedy

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
grouppython-list @
categoriespython
postedApr 16, '10 at 10:54a
activeApr 16, '10 at 7:10p
posts9
users4
websitepython.org

People

Translate

site design / logo © 2022 Grokbase