[antlr-interest] Problem running debugger in Antlrworks 1.0

[Isabelle Muszynski]

It could also be that an old connection is still open. Look at running processes, and if a debugger connection is still open, 
kill it.

Isabelle
> ----- Original Message -----
> From: "Shmuel Siegel" <ssiegel at finjan.com>
> To: "Simon Fairall (Alphawest)" <Simon.Fairall at optus.com.au>, antlr-interest at antlr.org
> Subject: Re: [antlr-interest] Problem running debugger in Antlrworks 1.0
> Date: Thu, 24 May 2007 15:56:57 +0300
> 
> 
> I have only been able to get the debugger to work if the grammar doesn't
> use packages.
> 
> 
> 
> ________________________________
> 
> From: antlr-interest-bounces at antlr.org
> [mailto:antlr-interest-bounces at antlr.org] On Behalf Of Simon Fairall
> (Alphawest)
> Sent: Thursday, May 24, 2007 5:13 AM
> To: antlr-interest at antlr.org
> Subject: [antlr-interest] Problem running debugger in Antlrworks 1.0
> 
> 
> 
> I have been trying to get the debugger to work in Antlrworks with no
> success. I am using a PC with Windows Vista and jdk 1.6.
> 
> 
> 
> To simplify the testing I am using the Expr example . When I select the
> debugger, the code is generated and compiled but the process is never
> able to connect to the parser. The output of netstat -na would indicate
> that the debugger port is listening during the connect phase. The
> console for the Antlrworks session shows a warning on the compile then
> java.net.connectException (repeats) during the connection phase.
> 
> 
> 
> Has anyone had this problem and been able to solve it? Alternatively,
> does anyone have any instructions on how to execute the compiled parser
> test code directly?
> 
> 
> 
> Regards,
> 
> 
> 
> Simon Fairall

>


=


-- 
Powered by Outblaze