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

Johannes Luber jaluber at gmx.de
Thu Aug 14 08:55:21 PDT 2008


Jones, Larry schrieb:
> Johannes,
> 
> Thanks for the information.
> 
> I confirmed that the default of ANTLWorks 1.2b5 is still 49100; however,
> when I manually changed it to 49153, the behavior of ANTLWorks remained
> the same.

I've been informed shortly ago, that the debug constructor is missing 
the call of InitalizeCyclicDFAs(). Unfortunately not yet, which 
constructor, but I guess it is the one for the debug parser. Another 
problem is that I can't find InitalizeCyclicDFAs() in the Java target, 
so I'm not sure where the bug actually originated. I have to ask Ter 
about that one first, but you can try to add the call to 
InitalizeCyclicDFAs() yourself.

Johannes
> 
> -----Original Message-----
> From: Johannes Luber [mailto:jaluber at gmx.de] 
> Sent: Thursday, August 14, 2008 7: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.
> 



More information about the antlr-interest mailing list