[EMAIL PROTECTED] writes:
> >> #1 0x004f5cd4 in gh_pair_p (val=0x0) at gh_predicates.c:71
> >> #2 0x000517d0 in ?? ()
> >> #3 0x000519d8 in ?? ()
> >
> > Can you recompile with -g and send the backtrace of that? The ??
> > aren't helping me.
>
> Are you implying you are NOT psychic ? :-)
well,
On Mar 25, 2004, at 2:21 AM, Han-Wen Nienhuys wrote:
[EMAIL PROTECTED] writes:
It turns out that the MacOS X packages I announced for 2.1.33 and 34
don't actually work. I've downgraded the fink package to 2.1.32, which
works.
The backtrace I get is:
Program received signal EXC_BAD_ACCESS, C
[EMAIL PROTECTED] writes:
> It turns out that the MacOS X packages I announced for 2.1.33 and 34
> don't actually work. I've downgraded the fink package to 2.1.32, which
> works.
>
> The backtrace I get is:
>
> Program received signal EXC_BAD_ACCESS, Could not access memory.
> 0x00510498 in s
It turns out that the MacOS X packages I announced for 2.1.33 and 34
don't actually work. I've downgraded the fink package to 2.1.32, which
works.
--
lilypond --verbose says:
Opening pipe `kpsexpand \$TEXMF'
Opening pipe `kpsewhich -expand-path=\
