Xterm windows dont open on jaguar 10.2 builds

2002-07-24
2002-07-24
  • Jeffrey Fanelli

    Jeffrey Fanelli - 2002-07-24

    When i launch Xfree 4.2 on my OSX 10.2 beta (6c92) it will quit when an Xterm is launched (rendering Xfree useless).  This happens on both my G4 and my Tibook.  Here's the output to the console that appears to point to the problem (xterm.log follows as well):

    dyld: xterm Undefined symbols:
    xterm undefined reference to _tgetent expected to be defined in /usr/lib/libSystem.B.dylib
    xterm undefined reference to _tgetstr expected to be defined in /usr/lib/libSystem.B.dylib
    dyld: xterm Undefined symbols:
    xterm undefined reference to _tgetent expected to be defined in /usr/lib/libSystem.B.dylib
    xterm undefined reference to _tgetstr expected to be defined in /usr/lib/libSystem.B.dylib
    dyld: xterm Undefined symbols:
    xterm undefined reference to _tgetent expected to be defined in /usr/lib/libSystem.B.dylib
    xterm undefined reference to _tgetstr expected to be defined in /usr/lib/libSystem.B.dylib
    Jul 24 14:46:58 pcp01130191pcs crashdump: Crash report written to: /Library/Logs/CrashReporter/xterm.crash.log

    waiting for X server to shut down Using keymapping provided in /System/Library/Keyboards/USA.keymapping.
    Display mode: Rootless Quartz
    Screen 0 added: 1280x1003 @ (0,21)
    Screen 0 placed at X11 coordinate (0,0).

    Quitting XDarwin...

    and here's the crash report:

    **********

    Date/Time:  2002-07-24 14:47:00 -0400
    OS Version: 10.2 (Build 6C92)
    Host:       **** (blocked)

    Command:    xterm
    PID:        4392

    Exception:  EXC_BREAKPOINT (0x0006)
    Code[0]:    0x00000001Code[1]:    0x8fe01460

    Thread 0 Crashed:
    #0   0x8fe01460 in halt
    #1   0x8fe10894 in link_in_need_modules
    #2   0x8fe12c04 in _dyld_bind_fully_image_containing_address
    #3   0x90004eb4 in _dyld_bind_fully_image_containing_address
    #4   0x90004e0c in sigaction__
    #5   0x9000eec0 in signal__
    #6   0x00027e84 in spawn
    #7   0x00027838 in main
    #8   0x00001ba8 in _start
    #9   0x000019d8 in start

    PPC Thread State:
      srr0: 0x8fe01460 srr1: 0x0002d030                vrsave: 0x00000000
       xer: 0x20000000   lr: 0x8fe09e18  ctr: 0x8fe29428   mq: 0x00000000
        r0: 0x00000004   r1: 0xbfffe510   r2: 0x8fe0b9d4   r3: 0x000000d5
        r4: 0x00000000   r5: 0x000000d5   r6: 0x0000000a   r7: 0x2e64796c
        r8: 0x2f6c6962   r9: 0x00000000  r10: 0x8fe4850c  r11: 0x0000001a
       r12: 0x8fe71afc  r13: 0x00000000  r14: 0x00000000  r15: 0x00000000
       r16: 0x00000000  r17: 0x00000000  r18: 0x00000000  r19: 0x00000000
       r20: 0x00000000  r21: 0xbffffd0c  r22: 0xbffffd08  r23: 0xbffffd04
       r24: 0xbffffd68  r25: 0x00000000  r26: 0x00000000  r27: 0x00027bdc

     
    • Torrey T. Lyons

      Torrey T. Lyons - 2002-07-24

      There is a Jaguar XTerm Update posted to our XFree86 4.2.0 release here. The update fixes the problem you have observed.

      (If you were on the XonX-Users or XonX-Announce mailing lists, you would have heard this already. I suppose we should make a news posting here as well about the update.)

       
    • Jeffrey Fanelli

      Jeffrey Fanelli - 2002-07-24

      kick-ass, thanks!  blame my lame-self for using Versiontracker.com as my update source :)

       

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks