Thanks to the clues, I got it working in the end.
The changes made were:
1. Strip out every PATH and CLASSPATH entries that may clash, and then
reboot. It took a fair few reboots.
2. Switch back to port 49153.
3. Uninstall the old JDKs to prevent them being picked up.
> -Original Message--
3.1.2 or 3.1.1 had a different port I think. Make sure you run
ANTLRWorks with the ANTLR that comes in its jar or make sure use the
latest of those tools. somewhere there is a mismatch :)
Ter
On Jun 1, 2009, at 4:51 PM, Matthew Rawlings wrote:
> Netstat shows nothing on port 49100
>
>> -O
Netstat shows nothing on port 49100
> -Original Message-
> From: Terence Parr [mailto:pa...@cs.usfca.edu]
> Sent: 02 June 2009 00:07
> To: Matthew Rawlings
> Cc: antlr-inter...@antlr.org
> Subject: Re: [antlr-interest] "Cannot launch the debugger"
>
> anything running already on that por
anything running already on that port?
Ter
On Jun 1, 2009, at 2:47 PM, Matthew Rawlings wrote:
> It definitely is 49100 in File->Preferences->Debugger
>
>> -Original Message-
>> From: Terence Parr [mailto:pa...@cs.usfca.edu]
> ...
>>
>> I'd make sure that your preferences have the right p
It definitely is 49100 in File->Preferences->Debugger
> -Original Message-
> From: Terence Parr [mailto:pa...@cs.usfca.edu]
...
>
> I'd make sure that your preferences have the right port number. should
> say 49100 for default local port.
> Ter
> On Jun 1, 2009, at 1:27 PM, Matthew Rawli
I'd make sure that your preferences have the right port number. should
say 49100 for default local port.
Ter
On Jun 1, 2009, at 1:27 PM, Matthew Rawlings wrote:
> I have been getting on fine learning ANTLR. I have written my
> grammars and executed the examples downloaded from “The Definitive
I have been getting on fine learning ANTLR. I have written my grammars and
executed the examples downloaded from "The Definitive ANTLR Reference". All
grammars work fine from the command line, and most work fine from
ANTLRWorks. The only problem is that whenever I separate the tree grammar
and pars
Hi Florian,
There are 2 things to resolve your problem:
1. Please use antlr-v3.1.2 instead. I verified a bug in 3.1.3, which caused
errors in the tree interpreter example.
2. To implement if-else-statement tree walker, we can use wildcard and tree
node stream index jumping. You may want to lo
Hello,
I have a parser grammar that creates an AST. My rule for if-then-else
looks like:
e : (IF cond=p THEN ifStat=e ELSE elseStat=e ENDIF ) -> ^(IF $cond
$ifStat $elseStat)
This creates a correct AST node containing the IF and its children. In
my tree grammar I match the node now with
Ned Gill wrote:
> On Mon, 01 Jun 2009 16:01:19 +0100, Ned Gill wrote:
>
>> I believe the node it's trying to duplicate is one of
>> stream->UP/DOWN/EOF_NODE/INVALID_NODE initialised in
>> antlr3CommonTreeNodeStreamNew (in antlr3commontreenodestream.c). It
>> looks
>> like those nodes never have
Ned Gill wrote:
Hi list,
I'm seeing a crash in dupNode in antlr3commontree.c in libantlr3c 3.1.3.
dupNode is being called on a common tree node which has a null factory.
Edited stack trace from GDB:
dupNode (tree=0x97debe0)
at antlr3commontree.c:402
getMissingSymbol (recognizer=0x9
On Mon, 01 Jun 2009 16:01:19 +0100, Ned Gill
wrote:
> I believe the node it's trying to duplicate is one of
> stream->UP/DOWN/EOF_NODE/INVALID_NODE initialised in
> antlr3CommonTreeNodeStreamNew (in antlr3commontreenodestream.c). It looks
> like those nodes never have their factory set. Is is s
Hi list,
I'm seeing a crash in dupNode in antlr3commontree.c in libantlr3c 3.1.3.
dupNode is being called on a common tree node which has a null factory.
Edited stack trace from GDB:
dupNode (tree=0x97debe0)
at antlr3commontree.c:402
getMissingSymbol (recognizer=0x97ec8f8, istream=0x97e
Hi all,
Resolved with scoping, but I'm sure this problem is occuring more than
one might hope. Is this something the devs are considering and/or
working on?
Sam
Sam Barnett-Cormack wrote:
> Hi all,
>
> Been away from work ill for a while, and now returning to my ASN.1 project.
>
> I'm havin
I've found that the grammar produces correct "non-debugging" parser.
But when the code is generated with the -debug flag it behaves as
described below. So there must be a bug somewhere inside the
debugger...
Regards,
Tomas
2009/5/29 Tomas Potrusil :
> Halo,
>
> I'm writing a SQL grammar. I've de
Dear Sir/Madam
At last you found us! Halwasiya Infosys is the one-stop shop you have
been looking for to fill all of your Web Development needs. From Logos
to Web Sites to Facebook Applications to Iphone Applications to
promoting your company on the web, we do it all and at very
competitive price
Online Dating and friend finder
http://friendfinder.com/go/g1100916
http://friendfinder.com/go/g1100916
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"il-antlr-interest" group.
To post to this group, send email to
17 matches
Mail list logo
