1e041568 is inside python23.dll, somewhere around the PyArg_* and
PyObject_GC_* handlers. Maybe an argument issue in the Python/C
interface, or a garbage collection problem.
Have you used Dr. Watson to try to get a traceback?
···
On Sat, 11 Oct 2003 09:48:31 -0600, John Hoffman <theshadow@shambala.net> wrote:
Hi folks. I need your help.
I maintain an experimental modded version of the BitTorrent reference
client at http://bt.degreez.net . For the past few weeks I've been
chasing a bug that seems to be corrupting data downloaded by the
client. It is very elusive, only striking certain Windows-based
machines (and not me directly, which certainly doesn't help my debugging
efforts), and doesn't seem to be related to the operating system
version (98, XP, etc) or disk format. One user who's been plagued by
the problem recently reported an application error; ' The instruction at
"0x1e041568" referenced memory at "0x05000054". The memory could not be
"read". ' I suspect a problem with certain system DLLs being accessed
via wxWindows.
--
- Tim Roberts, timr@probo.com
Providenza & Boekelheide, Inc.
I maintain an experimental modded version of the BitTorrent reference client at http://bt.degreez.net . For the past few weeks I've been chasing a bug that seems to be corrupting data downloaded by the client. It is very elusive, only striking certain Windows-based machines (and not me directly, which certainly doesn't help my debugging efforts), and doesn't seem to be related to the operating system version (98, XP, etc) or disk format. One user who's been plagued by the problem recently reported an application error; ' The instruction at "0x1e041568" referenced memory at "0x05000054". The memory could not be "read". ' I suspect a problem with certain system DLLs being accessed via wxWindows.
1e041568 is inside python23.dll, somewhere around the PyArg_* and
PyObject_GC_* handlers. Maybe an argument issue in the Python/C
interface, or a garbage collection problem.
Have you used Dr. Watson to try to get a traceback?
Like I said, I've never experienced the problem myself; I've only gotten reports from users. Further, these users almost never get that sort of application crash; more often this manifests as data corruption. If someone could give me some direction as to how to include debugging code in with my distribution, I'd appreciate it...
I am having trouble getting the wxEVT_WIZARD_FINISHED to work properly. For
some reason, when the user presses the finish button, this function never
gets called. Anybody run into the same thing?
Gilad
···
----- Original Message -----
From: "John Hoffman" <theshadow@shambala.net>
To: <wxPython-users@lists.wxwindows.org>
Sent: Monday, October 13, 2003 1:16 PM
Subject: Re: [wxPython-users] Re: Application corruption problems
>>I maintain an experimental modded version of the BitTorrent reference
>>client at http://bt.degreez.net . For the past few weeks I've been
>>chasing a bug that seems to be corrupting data downloaded by the
>>client. It is very elusive, only striking certain Windows-based
>>machines (and not me directly, which certainly doesn't help my debugging
>>efforts), and doesn't seem to be related to the operating system
>>version (98, XP, etc) or disk format. One user who's been plagued by
>>the problem recently reported an application error; ' The instruction at
>>"0x1e041568" referenced memory at "0x05000054". The memory could not be
>>"read". ' I suspect a problem with certain system DLLs being accessed
>>via wxWindows.
>>
>>
>
>1e041568 is inside python23.dll, somewhere around the PyArg_* and
>PyObject_GC_* handlers. Maybe an argument issue in the Python/C
>interface, or a garbage collection problem.
>
>Have you used Dr. Watson to try to get a traceback?
>
Like I said, I've never experienced the problem myself; I've only gotten
reports from users. Further, these users almost never get that sort of
application crash; more often this manifests as data corruption. If
someone could give me some direction as to how to include debugging code
in with my distribution, I'd appreciate it...
---------------------------------------------------------------------
To unsubscribe, e-mail: wxPython-users-unsubscribe@lists.wxwindows.org
For additional commands, e-mail: wxPython-users-help@lists.wxwindows.org
[if you are going to start a new subject then please make a new email, not a reply]
Gilad Suberri wrote:
I am having trouble getting the wxEVT_WIZARD_FINISHED to work properly. For
some reason, when the user presses the finish button, this function never
gets called. Anybody run into the same thing?
A quick tweak to the demo shows that it is working here.
···
--
Robin Dunn
Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython!
I tweaked my demo to look like this:
EVT_WIZARD_PAGE_CHANGED(self, self.ID_wiz, self.OnWizPageChanged)
EVT_WIZARD_PAGE_CHANGING(self, self.ID_wiz, self.OnWizPageChanging)
EVT_WIZARD_CANCEL(self, self.ID_wiz, self.OnWizCancel)
EVT_WIZARD_FINISHED(self, self.ID_wiz, self.fin)
def fin(self,evt):
self.log.write("OnFinished")
and updated my system to Python 2.2.3 with wxPython 2.4.2.4 on my PC. For
some reason it still doesnt work, but works on my Solaris install of Python
2.2.3 with wxPython2.4.1.2. Am I missing something stupid? Thanks.
Gilad
···
----- Original Message -----
From: "Robin Dunn" <robin@alldunn.com>
To: <wxPython-users@lists.wxwindows.org>
Sent: Monday, October 13, 2003 4:51 PM
Subject: Re: [wxPython-users] wxWizard
[if you are going to start a new subject then please make a new email,
not a reply]
Gilad Suberri wrote:
> I am having trouble getting the wxEVT_WIZARD_FINISHED to work properly.
For
> some reason, when the user presses the finish button, this function
never
> gets called. Anybody run into the same thing?
A quick tweak to the demo shows that it is working here.
--
Robin Dunn
Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython!
---------------------------------------------------------------------
To unsubscribe, e-mail: wxPython-users-unsubscribe@lists.wxwindows.org
For additional commands, e-mail: wxPython-users-help@lists.wxwindows.org
I tweaked my demo to look like this:
EVT_WIZARD_PAGE_CHANGED(self, self.ID_wiz, self.OnWizPageChanged)
EVT_WIZARD_PAGE_CHANGING(self, self.ID_wiz, self.OnWizPageChanging)
EVT_WIZARD_CANCEL(self, self.ID_wiz, self.OnWizCancel)
EVT_WIZARD_FINISHED(self, self.ID_wiz, self.fin)
def fin(self,evt):
self.log.write("OnFinished")
and updated my system to Python 2.2.3 with wxPython 2.4.2.4 on my PC. For
some reason it still doesnt work, but works on my Solaris install of Python
2.2.3 with wxPython2.4.1.2. Am I missing something stupid? Thanks.
No, I tested on Linux before. When I do the same on Windows then I also don't get the event. I've responded to a similar message in wx-users with a patch to show the problem. It should get fixed for the next release.
···
--
Robin Dunn
Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython!