[antlr-interest] ANTLRWorks 1.2b5 - Cannot Connect to C# Process

[Jones, Larry]

Interestingly, when I tried yesterday, I found that I could connect to a
Java targeted parser grammar on port 49153; however, when I tried to
connect to a tree grammar, I could neither connect to a C# application
nor a Java application.

-----Original Message-----
From: antlr-interest-bounces at antlr.org
[mailto:antlr-interest-bounces at antlr.org] On Behalf Of Foust
Sent: Thursday, August 14, 2008 4:01 PM
To: antlr-interest at antlr.org
Subject: Re: [antlr-interest] ANTLRWorks 1.2b5 - Cannot Connect to C#
Process


Johannes wrote:
> Does ANTLRworks demand the port 49100 instead 49153? Then the issue is

> that somehow the port change didn't make into the distribution. Ter 
> has to change the defalut port from 0xC001 to 0xBFCC, as well all the 
> targets.

AntlrWorks 1.2b5 won't connect for me anymore on *any* port. It thinks
49153 is in use, but trying 49100 used to work. Now it just times out.
Every time. After a reboot. It doesn't matter. Even for a test grammar
like:

	grammar test;
	start : 'hello';

If debugging from within AntlrWorks, does the port chosen need to match
what was compiled into Antrl, or can could AntlrWorks just search for an
unused port each time the Debug button was clicked?

Brent

> -----Original Message-----
> From: antlr-interest-bounces at antlr.org [mailto:antlr-interest- 
> bounces at antlr.org] On Behalf Of Johannes Luber
> Sent: Thursday, August 14, 2008 5:00 AM
> To: Jones, Larry
> Cc: antlr-interest at antlr.org
> Subject: Re: [antlr-interest] ANTLRWorks 1.2b5 - Cannot Connect to C# 
> Process
> 
> Jones, Larry schrieb:
> > I was trying to use ANTLRWorks 1.2b5 on Windows XP to connect to a 
> > parser generated in C#. I think I have followed the steps described
> in
> > the wiki. I:
> > - Built a lexer / parser using the -debug option. (I verified that
> the
> > generated parser inherits DebugParser.)
> > - Built an executable.
> > - Verified that it accepts command line input.
> > - Started in from a cmd window. It "hangs" waiting for console 
> > input.
> > - Started ANTLRWorks in a separate window.
> > - Opened the grammar used to generate my parser.
> > - Invoked Debugger | Remote Debug.
> > - When ANTLRWorks presents the connection dialog, I accepted the
> defaults.
> >
> > After a few minutes, ANTLRWorks displays an error message that it 
> > "Cannot launch the debugger" because of a "Time-out waiting to
> connect
> > to the remote parser." The window from which I launched ANTLRWorks 
> > contains a number of "java.net.ConnectException: Connection refused:

> > connect" messages.
> >
> > What additional steps must I take to use ANTLRWorks 1.2b5 to debug a

> > remote C# parser?
> >
> > Thanks.
> 
> Does ANTLRworks demand the port 49100 instead 49153? Then the issue is

> that somehow the port change didn't make into the distribution. Ter 
> has to change the defalut port from 0xC001 to 0xBFCC, as well all the 
> targets. The workaround is to change the port manually, until 3.1.1, 
> that is.
> 
> Johannes
> >
> >
> > *--*
> >
> > *Lawrence Allan Jones*
> > *Senior Developer / Technical Advisor*
> > Aspen Technology, Inc.
> > 2500 CityWest Blvd. Suite 1500
> > Houston, Texas 77042
> > USA
> > 281-504-3324 (work)
> > 281-504-3395 (fax)
> > larry.jones at aspentech.com <mailto:larry.jones at aspentech.com>
> > www.aspentech.com <http://www.aspentech.com/>
> >
> >
> >
> >
> >
> > This e-mail and any attachments are intended only for use by the
> > addressee(s) named herein and may contain legally privileged and/or 
> > confidential information. If you are not the intended recipient of
> this
> > e-mail, you are hereby notified any dissemination, distribution or 
> > copying of this email, and any attachments thereto, is strictly 
> > prohibited. If you receive this email in error please immediately
> notify
> > the sender and permanently delete the original copy and any copy of
> any
> > e-mail, and any printout thereof.


This e-mail and any attachments are intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient of this e-mail, you are hereby notified any dissemination, distribution or copying of this email, and any attachments thereto, is strictly prohibited. If you receive this email in error please immediately notify the sender and permanently delete the original copy and any copy of any e-mail, and any printout thereof.