Closed FriedrichGretz closed 7 years ago
Can you provide a specific set of steps to reproduce this issue?
I came accross this, while working with the grammar in issue #5 There asking to debug would first give the error message and clicking debug again simply presents the window where you choose text and starting rule and hitting OK then says: preparing... timeout.
The timeout of course happens because no classes were generated.
I belive the same would happen if you succeed to generate classes with debug, delete them manually and debug again.
On the bright side, as long as I really keep modifying the grammar it tries to recompile everytime, it seems.
An issue that I think is present also in versions before 1.5 is:
Usually if you made any changes to the grammar or if the Lexer/Parser classes or __Test___input file are missing, ANTLRworks would regenerate and recompile them when asked to Debug...
However sometimes it does not. E.g. if you delete classes, it still will assume they are there and run into timeout when trying to debug.
Also the test input seems to be stored by ANTLRworks internally because it suggests the previous test input even if you delete the __Test___input file.
Once you run into this behaviour you have to shut down ANTLRworks and restart it.