Idle 2.3.4 on Red Hat 9 segmentation fault

[Ron Kneusel]

I've installed Python 2.3.4 on Red Hat 9 and everything seems to be
working fine. Tkinter is available and I can run GUI scripts.

However, when I try to start Idle I get a segmentation fault. Using
GDB and loading the idle script by hand:

gdb python2.3

(gdb) run
....

from idlelib.PyShell import main
main()

error here:

"Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1074892416 (LWP 2870)]
0x407a3c6c in Tcl_FindExecutable () from /usr/lib/libtcl8.3.so"

Is anyone else seeing this sort of thing?

Ron

[Anthony Baxter]

On 3 Jul 2004 05:06:35 -0700, Ron Kneusel <on********@hotmail.com> wrote:

I've installed Python 2.3.4 on Red Hat 9 and everything seems to be
working fine. Tkinter is available and I can run GUI scripts.

However, when I try to start Idle I get a segmentation fault. Using
GDB and loading the idle script by hand: "Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1074892416 (LWP 2870)]
0x407a3c6c in Tcl_FindExecutable () from /usr/lib/libtcl8.3.so"

Is anyone else seeing this sort of thing?

I don't recall seeing anything like this. What did you do when
building with respect to the RH9 disaster of Unicode-borked Tcl? Did
you try the fixed Tcl/Tk RPMs that I posted (see the release notes for
more)

Please consider logging a bug on SF, including the precise version of
tcl/tk installed on the system and gcc version, as well as the full
backtrace output from gdb.

[Ron Kneusel]

Anthony Baxter <an***********@gmail.com> wrote in message news:<ma**************************************@pyt hon.org>...

On 3 Jul 2004 05:06:35 -0700, Ron Kneusel <on********@hotmail.com> wrote:

I've installed Python 2.3.4 on Red Hat 9 and everything seems to be
working fine. Tkinter is available and I can run GUI scripts.

However, when I try to start Idle I get a segmentation fault. Using
GDB and loading the idle script by hand:

"Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1074892416 (LWP 2870)]
0x407a3c6c in Tcl_FindExecutable () from /usr/lib/libtcl8.3.so"

Is anyone else seeing this sort of thing?

I don't recall seeing anything like this. What did you do when
building with respect to the RH9 disaster of Unicode-borked Tcl? Did
you try the fixed Tcl/Tk RPMs that I posted (see the release notes for
more)

I just downloaded and installed the fixed Tcl/Tk RPMs you created and
now Idle runs just fine. Thanks!

Ron