Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 23 Oct 1998 20:51:15 -0400
From:      Nathan Dorfman <nathan@rtfm.net>
To:        freebsd-current@FreeBSD.ORG
Subject:   libmytinfo breaks vim-5.3 port, maybe others?
Message-ID:  <19981023205115.A5357@rtfm.net>

next in thread | raw e-mail | index | archive | help
Vim-5.3 (compiled from ports) won't run in -g (gvim) mode with
libmytinfo. At first I thought it was vim breakage, or Motif/Athena
or even X11 breakage. But read on:

CPU states: 14.8% user,  0.0% nice, 84.0% system,  1.2% interrupt,  0.0% idle

 5411 root      89   0  3692K  2960K RUN      0:33 92.19% 76.98% vim
  243 nathan     2   0 12344K  4060K select  21:49  4.39%  4.39% XF86_SVGA

After gdb vim 5411, it has this to say:

(gdb) bt
#0  0x283524da in tputs ()
#1  0x80a7146 in XtVaGetApplicationResources ()
#2  0x807bb81 in XtVaGetApplicationResources ()
#3  0x808c865 in XtVaGetApplicationResources ()
#4  <signal handler called>
#5  0x283524da in tputs ()
#6  0x80a7146 in XtVaGetApplicationResources ()
#7  0x80a7ab9 in XtVaGetApplicationResources ()
#8  0x806f84d in XtVaGetApplicationResources ()
#9  0x804b275 in XtVaGetApplicationResources ()

Anyway, I noticed something weird:

        libmytinfo.so.2 => /usr/lib/libmytinfo.so.2 (0x2834b000)

According to find -exec grep, this library is not mentioned anywhere
in the vim port or work dir. Are things being linked with it automagically
for some reason? Anyway, moving libtmyinfo.so.2 to foo and rebuilding
vim: built and ran fine. Anyone? Pilot error?


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19981023205115.A5357>