Can happen if you have an empty lexer rule that runs forever or if you start something that uses the same port. Kill the rogue java process if a lexer problem. Teat by running from command line first.
Jim On Sep 4, 2009, at 2:27 AM, Klaus Martinschitz <[email protected]> wrote: > Hi! > > I already looked around in the internet and do not find any answer to > solve following problem. I downloaded the newest antlr works version > 1.2.3 were antlr and antlr works are bundled. I normally start the jar > file. IF I try to debug I get an error message. Everything is set > correctly, classpath etc. Sometimes after a restart the same file > works > and sometimes not. I don't know why. > > Thanks for help, > > Klaus > > List: http://www.antlr.org/mailman/listinfo/antlr-interest > Unsubscribe: > http://www.antlr.org/mailman/options/antlr-interest/your-email-address List: http://www.antlr.org/mailman/listinfo/antlr-interest Unsubscribe: http://www.antlr.org/mailman/options/antlr-interest/your-email-address --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "il-antlr-interest" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/il-antlr-interest?hl=en -~----------~----~----~----~------~----~------~--~---
