Re: segfault in grob.cc

[John Galbraith]

   John Galbraith <address@hidden> writes:

   > With lilypond 1.4, I get a segfault in item.cc due to a NULL pointer
   > passed in from grob.cc at line 372.

   What version of guile do you run?  You may want to upgrade to
   guile-1.4, recompile, and see if it goes away.

I was running 1.3.4.  I recompiled with Guile 1.4.  
I also patched lilypond to 1.4.2.

This is weird: I only get the crash when lilypond is called from ly2dvi.
If I call lilypond directly (even if I cut and paste the lilypond command 
and arguments from a ly2dvi --verbose run) I don't see the crash.  This would
seem to violate some physical law, unless it was an environmental issue.
I commented out the setup_environment call in ly2dvi, with no effect.
Lilypond was still invoked and ran until the crash.  If I call lilypond  
just vanilla from the command line, I don't get a crash (or any of the
features of ly2dvi, obviously).  I commented out all my header information
with no effect.

Because I can't figure out how to actually run lilypond in the debugger
and trigger the crash, I have to load a core dump after the fact.

Unlike my previous post, I now seem to be getting stuck in an infinite
recursion in Grob::handle_broken_smobs (src=1100160656, criterion=9588)
at grob.cc:413 that is at least 10,000 levels deep - maybe a lot deeper.
I am suspicious that a recursion this deep is not normal...

   There's two things we can do about this; you can put the complex score
   up for ftp somewhere so that I (or someoene else) can debug it, or you
   can do some debugging yourself.

OK, things are getting pretty strange.  I will post a version of my input.
But first, I am going to try to trim it down as small as I can get it 
while still hitting the bug.  I will post when it is ready.

John