#90 closed defect (fixed)
W2 crashes because of a syntax error in the textual input.
Reported by: | Juergen Reuter | Owned by: | kilian |
---|---|---|---|
Priority: | P3 | Milestone: | |
Component: | core | Version: | 2.0.0alpha |
Severity: | normal | Keywords: | textual input |
Cc: |
Description (last modified by )
WHIZARD 2 seems to incorrectly parse the input file.
reuter@Melkor:~/Physik/progs/omwhiz/svn/hepforge_trunk/test$ ./whizard_test_plain.sh | Writing log to 'whizard.log' |=============================================================================| | WHIZARD 2.0.0 | |=============================================================================| | Initializing process library 'processes' | Loading process library 'processes' | Reading model file 'SM.mdl' | Using model: SM | Reading commands from file 'bug2.in' Line 17: show(cuts) Expected syntax: ARGUMENTS <show_arg> = ( <var_generic>* ) Found token: KEYWORD: 'cuts' *** Fatal error: Syntax error in textual input WHIZARD run aborted.
When the code is generated for the first time, WHIZARD runs through. Afterwards one gets the error message above.
Attachments (1)
Change History (8)
Changed 15 years ago by
comment:2 Changed 15 years ago by
Obviously this error is triggered by "show(cuts)" which does not exist. But this should be caught somehow.
comment:3 Changed 15 years ago by
With gfortran and 128 calls the integrations seem to run, with 127 calls
comment:4 Changed 15 years ago by
OK, delete the last line it belongs to Bug Report #91. I was too tired yesterday so this error occured.
comment:5 Changed 15 years ago by
Description: | modified (diff) |
---|---|
Priority: | P2 → P3 |
Severity: | critical → normal |
Status: | new → assigned |
Two points:
- This is indeed a syntax error. The lexer should provide more information about where this occurs (for any syntax error). However, this is no bug.
- show(cuts) should be implemented. As long as I have no pretty-printed output of expressions, the program can at least print the evaluation tree.
comment:6 Changed 15 years ago by
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
The first problem is reformulated as bug #93. The second problem is solved by [1322], but the implementation has the problem that the output is the parse tree (the only available info since cuts are compiled only when they are used). This is very verbose. I reformulated this as bug #94 and close the current one.
input file triggering the problem. I'm not sure whether newline really is an issue here.