I would, but reportbug segfaults on me. I had this problem early in December but it went away again around December 14 after a libc update. I'm using the gcc-3.4 archive. Is anyone else seeing segfaults with reportbug?Yes. It seems to be a problem of python2.3 and gcc-4.0. I do not have a fix for this yet.
I have this problem, too, what would it take to recompile python2.3 locally with the appropriate gcc so I can fix it?
Here's a backtrace in case we're not talking about the same bug: #0 0x000000000043e7b2 in PyString_Size () #1 0x000000000047435e in PyEval_GetFuncName () #2 0x0000000000475f58 in PyEval_EvalCodeEx () #3 0x0000000000474056 in PyEval_GetFuncName () #4 0x0000000000475f58 in PyEval_EvalCodeEx () #5 0x0000000000476092 in PyEval_EvalCode () #6 0x000000000049aad6 in PyRun_FileExFlags () #7 0x000000000049ad9e in PyRun_SimpleFileExFlags () #8 0x000000000040feb1 in Py_Main () [..]
Greetings, -- Javier Kohen <[EMAIL PROTECTED]> ICQ: blashyrkh #2361802 Jabber: [EMAIL PROTECTED]
-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
