[wxPython-users] Re: Platform<=>version conflict or what?

[Phillip Stevens]

Hi Jorma,

Wednesday, July 4, 2007, 3:43:06 PM, you wrote:

> Hi Phil,

> Debugging of NSISed single exe-file is not very easy task and therefore
> I decided first to study the behaviour of my NSISed single file 
> executable on Win98 with "Dependency Walker", which normally gives a 
> very detailled analysis of running sw´s.
....
> Some advice ?

If you are finding debugging difficult to do by debugger,  my next
advice would be to have the running program itself emit more information
about what it is doing internally,  so that you can discover where things
go wrong,  and why.  Either in print statements,  or out to a log
file,  or somewhere.

Find out where the code first goes wrong.
Understand why what the code is doing is wrong,  or won't work.
Then change the code to fix it.

You might need to get the sources for both NSIS and wxPython in order
to do this.

Also see:
http://sourceforge.net/search/?group_artifact_id=373085&type_of_search=artifact&group_id=22049&words=.DLL

For NSIS patches involving .dll's.

Also see:
http://sourceforge.net/search/?type_of_search=artifact&group_id=22049&words=Windows+98

For NSIS bugs that involve Windows 98.

Not sure if any of these might be related to the problem you are
experiencing,  or not.  But if you haven't patched NSIS with any of the available
patches,  and a bug report looks like it might be related,  it might be worth applying
the patch for that problem,  if one is available.

All for now,

---Phil

> ---------------------------------------------------------------------
> To unsubscribe, e-mail: wxPython-users-unsubscribe at lists.wxwidgets.org
> For additional commands, e-mail:
> wxPython-users-help at lists.wxwidgets.org