[Python-bugs-list] [Bug #110856] Page fault in module KERNEL32.DLL (PR#186)

[noreply@sourceforge.net]

Bug #110856, was updated on 2000-Aug-01 14:37
Here is a current snapshot of the bug.

Project: Python
Category: None
Status: Open
Resolution: None
Bug Group: Irreproducible
Priority: 5
Summary: Page fault in module KERNEL32.DLL (PR#186)

Details: Jitterbug-Id: 186
Submitted-By: hauser@eos.ncsu.edu
Date: Fri, 21 Jan 2000 08:36:26 -0500 (EST)
Version: 1.5.2
OS: windows 95


I am new to Python and am having a problem on Windows 95 any time I use the
Tkinter module. An example follows:

>>>from Tkinter import *
>>>t = Button(None, {'text': 'Test', Pack: {}})
>>>q = Button(None, {'text': 'Quit', 'command': t.quit, Pack: {}})
>>>t.mainloop()

The window comes up and seems to work. Clicking on the 'Quit' button returns to
the Python screen.  Then:
>>>Ctrl-D    ->message comes up that illegal operation has been perforned:

Page fault in KERNEL32.DLL at 016f:6ff79ff3, computer hangs and has to be hard 
booted.
Everything else seems to work, the idle program comes up and everything is OK 
until I try to exit and the same problem happens.  If I don't use Tkinter I
don't have the problem and any time with Tkinter I make a window and exit from 
the window, and try to exit Python the same error appears.
I have found several references to Page faults in KERNEL32 in the Bug reports 
but have not seen any solutions.  Any help would be appreciated.  Thanks.




====================================================================
Audit trail:
Mon Jan 24 14:47:52 2000	guido	sent reply 1
Mon Jan 24 14:48:23 2000	guido	changed notes
Mon Jan 24 14:48:23 2000	guido	moved from incoming to irreproducible

Follow-Ups:

Date: 2000-Aug-01 14:38
By: none

Comment:
From: Guido van Rossum <bugs-py@python.org>
Subject: Re: Page fault in module KERNEL32.DLL (PR#186)
Date: Mon Jan 24 14:47:52 2000

John,

I am afraid I can't reproduce your problem, and I've never heard
of this type of behavior before.

My best guess is that some other Windows app that you have installed
is causing this behavior; this is basically impossible to debug.

I suggest that you post your problem description to comp.lang.python;
maybe someone there has a clever idea.  If you find a solution, please
reply to this message, leaving the subject intact.

In the mean time, I;ll keep your bug report in the "irreproducuble"
category.

Thanks,

--Guido van Rossum

-------------------------------------------------------

Date: 2000-Aug-01 14:38
By: none

Comment:
From: "Dr. John R. Hauser" <hauser@eos.ncsu.edu>
Subject: Re: Page fault in module KERNEL32.DLL (PR#186)
Date: Thu, 27 Jan 2000 15:34:33 -0500

Guido,

Thanks very much for your help.  With your suggestion I have traced the
problem to a file CSINJECT.exe which was being loaded on startup.  This is
a file associated with the Norton Clean Sweep utility.  After removing it
from my startup file, everything works fine.  I guess it was loaded when I
installed Norton Utilities and I have no idea what it does.  

Thanks again for you thoughts.

John Hauser


At 02:47 PM 1/24/2000 -0500, you wrote:
>John,
>
>I am afraid I can't reproduce your problem, and I've never heard
>of this type of behavior before.
>
>My best guess is that some other Windows app that you have installed
>is causing this behavior; this is basically impossible to debug.
>
>I suggest that you post your problem description to comp.lang.python;
>maybe someone there has a clever idea.  If you find a solution, please
>reply to this message, leaving the subject intact.
>
>In the mean time, I;ll keep your bug report in the "irreproducuble"
>category.
>
>Thanks,
>
>--Guido van Rossum
>
>
>


-------------------------------------------------------

Date: 2000-Aug-01 14:38
By: none

Comment:
Could be caused by another Windows app?
-------------------------------------------------------

Date: 2000-Sep-07 15:01
By: jhylton

Comment:
Please do triage on this bug.
-------------------------------------------------------

For detailed info, follow this link:
http://sourceforge.net/bugs/?func=detailbug&bug_id=110856&group_id=5470