Date: Wed, 09 Oct 1996 08:33:18 -0700 From: John Polstra <jdp@polstra.com> To: Masafumi NAKANE/=?ISO-2022-JP?B?GyRCQ2Y6LDJtSjgbKEI=?= <max@wide.ad.jp> Cc: freebsd-current@freebsd.org Subject: Re: ldconfig problem Message-ID: <199610091533.IAA23308@austin.polstra.com> In-Reply-To: Your message of "Wed, 09 Oct 1996 23:48:10 %2B0900." <199610091448.XAA01502@bourbon.sfc.wide.ad.jp>
next in thread | previous in thread | raw e-mail | index | archive | help
> Successful one: > > /usr/local/bin/kaffe: > -lkaffe_vm.0 => /usr/local/lib/libkaffe_vm.so.0.5 (0x801d000) > -lm.2 => /usr/lib/libm.so.2.0 (0x803e000) > -lc.3 => /usr/lib/libc.so.3.0 (0x8055000) > > > > Unsuccessful one: > > /usr/local/bin/kaffe: > -lkaffe_vm.0 => /usr/local/lib/libkaffe_vm.so.0.5 (0x801e000) > -lm.2 => /usr/lib/libm.so.2.0 (0x803f000) > -lc.3 => /usr/lib/libc.so.3.0 (0x8056000) Hmm, these both look OK. The shared libraries in the second case are mapped one page higher than in the first case, but that doesn't indicate a problem. Before mapping any shared libraries, the dynamic linker maps the entire "/var/run/ld.so.hints" file into memory. In the second case, that file is probably one page larger than in the first case, because it has the extra libraries from "/usr/local/lib/m3/FreeBSD2" in it. Does kaffe use dlopen(), or LD_PRELOAD, or any other unusual features of the dynamic linker? Can you examine the core file with a debugger and try to figure out what it's doing when it dies? John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199610091533.IAA23308>