Date: Wed, 11 Dec 1996 20:40:38 -0800 (PST) From: "Jonathan M. Bresler" <jmb> To: jfieber@indiana.edu Cc: nate@mt.sri.com, DARREND@novell.com, hackers@freebsd.org Subject: Re: Marimba for FreeBSD... Message-ID: <199612120440.UAA12851@freefall.freebsd.org> In-Reply-To: <Pine.BSI.3.95.961211184343.3546A-100000@fallout.campusview.indiana.edu> from "John Fieber" at Dec 11, 96 07:20:12 pm
next in thread | previous in thread | raw e-mail | index | archive | help
John Fieber wrote:
>
> On Wed, 11 Dec 1996, Nate Williams wrote:
>
> > It works fine on a pre-ALPHA system and a 2.1.6.1 system, as well as a
> > 2.2 system from last week and a -current system.
>
> Okay, good. Three responses so far confirming that it does work
> on systems like mine, but apparently not *exactly* like mine.
> So, where lies the crutial difference?
>
> Would a ktrace dump help anyone figure this out? It really
> doesn't get very far at all before crashing. It loads some
> libraries (m, Xt, Xext, X11, and c), tries to read
> /etc/malloc.conf (which doesn't exist), does a getrlimit,
> setrlimit, sigprocmask, sigaction, sigprocmask, break, break and
> crashes displaying:
>
> SIGSEGV 11* segmentation violation
> sig 11, code 12 or 0xc, sc 0xefbfd3a4, addr 0x1c
John,
Marimba seems to be very picky about where java is installed.
I had installed jdk102.11-26.tar.gz to /usr/local/share/java.
marimba would not run, could not find the Thread class.
I edited the tuner shell script (added the location of the Thread
class to the end of the CLASSPATH variable). then it started
dumping a trace and seg faulting, just like you experienced.
I moved java to /usr/local/java and NOW it works. initial start
up seems cranky. had to rm the files in ~/.marimba a couple times
to get the tuner to perform its initial installation configuration
stuff and then update itself.
initial config is (to the best of my memory)
entering your name and email address
specifing a http proxy (if there is one)
specifing a *marimba* proxy (if there is one)
downloading the newest version (1.2Mb [sic])
processing the update (some changes were made)
<like what! dang it! seems to be an
update in place. some original distribution
files were replaced...still an eerie feeling>>
when all is finished the "tuner" window appears--empty
just two shades of gray, darker across the top (ala menu bar)
and lighter in the remainder of the window.
rm'ed the files in ~/.marimba again, and restarted the tuner
entered all the info again and now i have a populated tuner
window that works.
so,,,,i guess you just have to keep pushing on it and it
does work in the end ;)
i still have some bogons however....it wants a different version
of one of the X libraries ...so.6.1.in place of ...so.6.0
my libmarimba.so has bad magic
bad magic number in "/home/jmb/tmp/marimba/tuner/lib/libmarimba.so" (/home/jmb/tmp/marimba/tuner/lib/libmarimba.so)
java.lang.UnsatisfiedLinkError: no marimba in shared library path
at java.lang.Runtime.loadLibrary(Runtime.java)
at java.lang.System.loadLibrary(System.java)
at marimba.desktop.FileSystem.<clinit>(FileSystem.java:254)
....
jmb
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199612120440.UAA12851>