Ideally, a bug report regarding Elsa should include the following:

• A C/C++ input file that is:
  • already preprocessed,
  • minimized using Delta,
  • and attached to the email as text/plain if possible.
• If the input came from a publicly-available software package, please tell me what it is and where to get it. Sometimes I can use this information to make a more accurate diagnosis and fix. Also, I might decide to try pushing the whole package through Elsa myself, saving you the time of submitting separate bug reports.
• A ccparse command line to demonstrate the failure. For example,

        ./ccparse test.cc
      

  or

        ./ccparse -tr c_lang test.c
      

• An explanation of what is wrong with what ccparse does. Examples include:
  • The input is valid C++, but ccparse gives the error "(...)".
  • ccparse fails with the assertion "(...)".
  • The input is invalid C++, but ccparse accepts it. (Note that such bugs generally receive lower priority.)
  • The AST computed by parse is inconsistent with the correct semantics of the input. In this case, if possible, use "-tr printTypedAST" to print the AST and indicate what part is wrong.
• Which compiler or compilers (including version numbers) you have tried the input with, and whether they accept or reject it. For example, "works with gcc-3.4.3 but fails with gcc-2.95.3". If you believe the input is valid C++, please try to confirm by running through gcc version 3.4.0 or later. Earlier versions of gcc have bugs that Elsa does not emulate, and may never do so.

I will try to get to your bug report as soon as possible, but Elsa is just a hobby project so it might take a little while. Of course, you're welcome to try to fix the problem yourself and send me a patch!