[Visualpython-users] more on idlefork problems

[Gary P. <pa...@in...>]

I have news to report re: my problems with idlefork.

Again, I know that I seem to be the only one having problems, but maybe
someday someone else will ...

Recall that under Win98 idlefork froze my system requiring reboot.

I've upgraded to XP.   Now idlefork will run and everything seems fine, but
when I close idlefork an error is generated ... can't read locatation
0x000000028 or something.

if I start idlefork from the command line (python idle.py) it starts
normally.
if I start it using python -v idle.py it spews an enormous number of
messages, most of which go by too fast to read. THere is one that I can
sort-of read because it is repeated about 50 times.  It contains the
filename "CallTips.py", but that's about all I can grab.  Then it seems to
go into shut-down mode.  The final messages are

----------------------------------
[...]
# cleanup sys
# cleanup __builtin__
PyThreadState_Clear:  warning: thread still has a frame
# cleanup ints:  14 unfreed ints in 3 out of 6 blocks
# cleanup floats:  4 unfreed floats in 1 out of 1 block

[here there is a looooonng pause during which the cpu roars along at 100%]

Font Tahoma 8 still in cache.
TkFontPkgFree:  all fonts should have been freed already

This application has requested the Runtime to terminate it in an unusual
way.
Please contact the application's support team for more information
--------------------------------------

What's the DOS way of redirecting all that output into a file?
If I start regular idle using "python -v idle.py"  it starts just fine
(spewing many fewers messages than idlefork), and quits just fine.
Ringing any bells?

-Gary