RE: Error Code

[Mark Stephen Mrotek]

Aaron,

Thank you for your response. Please excuse my ignorance on MME's. 

I am still flummoxed by this matter. I have extracted both into small
snippets. In both cases they compile. Yet when I add them to the full score
the one with "(...)" throws the error. 
I have removed code to the last known clean complication. Then each
subsequent line was added to confirm compilation. Each time it worked. It is
only the last line - with the addition of the "(...)" that the error is
thrown.

I realize that you cannot comment on such lack of information. Perhaps you
could suggest another course of investigation?

Thank you.

Mark

-----Original Message-----
From: lilypond-user
[mailto:lilypond-user-bounces+carsonmark=address@hidden] On Behalf Of
Aaron Hill
Sent: Monday, January 27, 2020 6:14 PM
To: address@hidden
Subject: Re: Error Code...

On 2020-01-27 5:14 pm, Mark Stephen Mrotek wrote:
> The following compiles correctly:
> b8 ([\grace {c32 b a b d\noBeam} c16.])
> 
> When the last note, b32, is added:
> b8 ([\grace {c32 b a b d\noBeam} c16. b32])

In the future, be sure to always include syntactically-complete MWEs.  
The snippets above are each missing an outer set of braces.  And the lack of
a \version statement leaves us guessing.

After making some assumptions, the following compiles successfully for
me:

%%%%
\version "2.19.83"
{ b8 ([\grace {c32 b a b d\noBeam} c16.]) } { b8 ([\grace {c32 b a b
d\noBeam} c16. b32]) } %%%%


> Exited with return code -1073741819

In hexadecimal, that translates to 0xC0000005--the exception code for an
access violation (segmentation fault, in *nix parlance).  Something has
attempted to read from and/or write to an invalid or protected memory
address.  It would require further debugging to determine why this is
occurring, as there is not enough actionable information.


-- Aaron Hill