lilypond-user
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: LilyPond hangs on os x


From: address@hidden
Subject: Re: LilyPond hangs on os x
Date: Sat, 18 Aug 2012 19:01:34 -0400

On 24 juil. 2012, at 03:51, address@hidden wrote:

> On 6 juil. 2012, at 08:51, David Kastrup wrote:
> 
>> "address@hidden" <address@hidden> writes:
>> 
>>> Hey all,
>>> 
>>> I'm running LilyPond on the command line from Mac OS X and it is
>>> hanging right after printing the version.  I downloaded several
>>> versions (stable, unstable, previous unstable) and it happens with all
>>> of them.  This is a recent-ish development (about 5 days ago or so).
>> 
>> So what changed in your setup?
>> 
>>> Is there a tool I could use to diagnose on what function call the
>>> hangup happens?
>> 
>> Have you tried running LilyPond under gdb?  In that case, just pressing
>> C-c should get you back into the debugger, and bt should give you a
>> backtrace.
>> 
>> -- 
>> David Kastrup
>> 
>> 
>> _______________________________________________
>> lilypond-user mailing list
>> address@hidden
>> https://lists.gnu.org/mailman/listinfo/lilypond-user
> 
> Oddest thing...running GDB on LilyPond made LilyPond work and now it just 
> works...as if LilyPond feared GDB.  I know I do...
> 
> Cheers,
> MS
> 
> 
> _______________________________________________
> lilypond-user mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/lilypond-user

Lilypond still hangs periodically on OS X - whenever I do a backtrace, the last 
couple functions change from time to time but it is always in FreeType that the 
problem occurs:

#0  0x91b52b06 in read$NOCANCEL$UNIX2003 ()
#1  0x94c925a9 in __sread ()
#2  0x94c92642 in _sread ()
#3  0x94c91f27 in __srefill1 ()
#4  0x94c8f783 in __fread ()
#5  0x94c8f689 in fread ()
#6  0x007926e7 in ft_ansi_stream_io ()
#7  0x00797ead in FT_Stream_ReadAt ()
#8  0x00797f26 in FT_Stream_Read ()
#9  0x00797f81 in FT_Raccess_Get_HeaderInfo ()
#10 0x0079b85c in IsMacResource ()
#11 0x0079b2ae in FT_Open_Face ()
#12 0x0079c063 in FT_New_Face ()
#13 0x0081fa32 in FcFreeTypeQuery ()
#14 0x00819f3d in FcFileScanConfig ()
#15 0x0081a20d in FcDirScanConfig ()
#16 0x0081a32d in FcDirCacheScan ()
#17 0x00815d97 in FcConfigAddDirList ()
#18 0x00816087 in FcConfigBuildFonts ()
#19 0x000aacbc in init_fontconfig ()
#20 0x0010f43a in main_with_guile ()
#21 0x006264f0 in invoke_main_func ()
#22 0x005f4f22 in c_body ()
#23 0x006705d8 in scm_c_catch ()
#24 0x005f5451 in scm_i_with_continuation_barrier ()
#25 0x005f550d in scm_c_with_continuation_barrier ()
#26 0x0066f2db in scm_i_with_guile_and_parent ()
#27 0x0066f328 in scm_with_guile ()
#28 0x00626489 in scm_boot_guile ()
#29 0x001120ee in main ()

Perhaps the version of FreeType built and bundled w/ GUB for Mac OS X has a 
problem?

Cheers,
MS


reply via email to

[Prev in Thread] Current Thread [Next in Thread]