Idle 2.3.4 on Red Hat 9 segmentation fault

Collapse
This topic is closed.
X
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • Ron Kneusel
    #1

    Idle 2.3.4 on Red Hat 9 segmentation fault

    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:
    [color=blue]
    >gdb python2.3[/color]
    (gdb) run
    ....[color=blue][color=green][color=darkred]
    >>> from idlelib.PyShell import main
    >>> main()[/color][/color][/color]

    error here:

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

    Is anyone else seeing this sort of thing?

    Ron
    Tags: None
    • Anthony Baxter
      #2
      Re: Idle 2.3.4 on Red Hat 9 segmentation fault

      On 3 Jul 2004 05:06:35 -0700, Ron Kneusel <oneelkruns@hot mail.com> wrote:[color=blue]
      > 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:[/color]
      [color=blue]
      > "Program received signal SIGSEGV, Segmentation fault.
      > [Switching to Thread 1074892416 (LWP 2870)]
      > 0x407a3c6c in Tcl_FindExecuta ble () from /usr/lib/libtcl8.3.so"
      >
      > Is anyone else seeing this sort of thing?[/color]

      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.

        Comment

        • Ron Kneusel
          #3
          Re: Idle 2.3.4 on Red Hat 9 segmentation fault

          Anthony Baxter <anthonybaxter@ gmail.com> wrote in message news:<mailman.3 82.1088867054.2 7577.python-list@python.org >...[color=blue]
          > On 3 Jul 2004 05:06:35 -0700, Ron Kneusel <oneelkruns@hot mail.com> wrote:[color=green]
          > > 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:[/color]
          >[color=green]
          > > "Program received signal SIGSEGV, Segmentation fault.
          > > [Switching to Thread 1074892416 (LWP 2870)]
          > > 0x407a3c6c in Tcl_FindExecuta ble () from /usr/lib/libtcl8.3.so"
          > >
          > > Is anyone else seeing this sort of thing?[/color]
          >
          > 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)[/color]

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

          Ron

            Comment

            Previous template Next
            Working...