While building and trying out the windows installer yesterday, I had some crashes in pydocgui.pyw (the module documentation server), both on win98SE and on XP Pro. The crash ocurred when it was closed, and it seems only when the test suite was also installed (usually it also finds something in the test suite). Win98 was unhelpful as usual in only showing the top of the machine stack, winXP displayed a message box showing an access violation in TclNotifier. I were not able to debug this, because I couldn't get Tkinter to work in the version running from the build dir, and I had no more time - I assume there are some env vars to be set so that it finds the tcl and tk dlls. I could not reproduce the problem with the final built which is no out in the cold, so I assume it was a temporary problem. But it would be nice if other people could try this out as well before this comes back later on me. Thanks, Thomas

I can't get my Python 2.3.3c1 program to work. It keeps core dumping (leaving python.core). I'm not doing anything strange, just documented stuff from the manuals. I tried 'gdb -c python.core' and then using 'back', but there are no labels compiled in (I hate that...); how can I get the labels to be included? "./configure --debug" doesn't work. I assume without the labels the numbers are meaningless. Running this under OpenBSD 3.2. Then, where should I submit my core dump (if anywhere?)? I used to have the URL bookmarked, but just upgraded and lost most of my old bookmarks.... John

JD writes:

Running this under OpenBSD 3.2. Then, where should I submit my core dump (if anywhere?)?

You should submit bug reports to sf.net/projects/python, and provide a link to the core dump on a server of your control (as SF has a limit on file upload size). Please understand that several months, or even years, may pass until such a bug report is looked at, so if you actually need this to work, you will have to investigate it in more detail. On Unix, Python is, by default, compiled with symbols if the compiler is gcc. To find out why gdb does not see symbols, you should post a few lines of make output, showing typical compiler and linker invocations. Regards, Martin

>> Submit bug reports here: >> >> http://sourceforge.net/tracker/?group_id=5470&atid=105470 JD> Thanx, OK, I logged in, and got the main page which confirmed my JD> login was good. But I cannot find any links that allow me to submit JD> bug reports. Where is the link? I cannot find it. Pop up that page (while logged in) and search for "Submit New". JD> There are two columns in the main page.... One titled... JD> My Assigned Tracker Items and another titled My Tasks Wrong page. Once you log in, SF takes you to your "my sf.net" page. After logging in, pop back to http://sourceforge.net/projects/python then poke the "Bugs" link, which will take you to the bug tracker (the first URL above). JD> Another thing also.... if I click on Python Bugs link in the left JD> column, it goes into a "Browse Bugs" section, but then there is yet JD> another "Please log in" in red. Sounds like you have cookies disabled. To use SourceForge you need to run with cookie support turned on. Skip

Aahz writes:

On Mon, Dec 15, 2003, Skip Montanaro wrote:

...

Sounds like you have cookies disabled. To use SourceForge you need to run with cookie support turned on.

...and you can't use Lynx, either. :-(

It seems that you can, so long as you "attach" /dev/null to the bug report each time you do anything... Cheers, mwh -- surely, somewhere, somehow, in the history of computing, at least one manual has been written that you could at least remotely attempt to consider possibly glancing at. -- Adam Rixey