On Mon, Jun 11, 2001 at 02:16:51PM -0700, Larry Shatzer wrote:
>
> On Monday, June 11, 2001, at 02:11 PM, Jarkko Hietaniemi wrote:
>
> >> (gdb) run
> >
> > Oops, I meant to say
> >
> > run configpm configpm.tmp
> >
> > to get the same segfault, and after that 'where'.
>
> I hope I am doing everything right ;o)
I would say so.
> (gdb) run configpm configpm.tmp
> Starting program: /Users/lshatzer/perl/bleadperl/./miniperl configpm
> configpm.tmp
> [Switching to thread 1 (process 12126 thread 0x1a07)]
> dyld: /Users/lshatzer/perl/bleadperl/./miniperl multiple definitions of
> symbol _Perl_ck_exec
> /Users/lshatzer/perl/bleadperl/./miniperl definition of _Perl_ck_exec
> /System/Library/Perl/darwin/CORE/libperl.dylib(op.o) definition of
> _Perl_ck_exec
Ho-hum. On closer inspection the dynaloader error messages look much like
there's a big confusion going on: both the symbols of the newly built
(mini)perl *AND* the operating system's already installed shared
Perl library are visible. This definitely smells like a dangerous
recipe, we are mixing symbols from a 5.7.1+ executable and 5.6.0
library together. Now, why is the /System shared lib being pulled in?
> Program exited with code 0102.
> (gdb) where
> No stack.
--
$jhi++; # http://www.iki.fi/jhi/
# There is this special biologist word we use for 'stable'.
# It is 'dead'. -- Jack Cohen
