The following information is output from gdb
Program received signal SIGSEGV, Segmentation fault.
0xb7341e78 in getMissingSymbol (recognizer=0x83e6a48, istream=0x83e5410,
e=0x83e9f70, expectedTokenType=4, follow=0xb6fe0810)
at src/antlr3baserecognizer.c:2199
2199 src/antlr3baserecognizer.c: No such file or directory.
in src/antlr3baserecognizer.c
(gdb) where
#0 0xb7341e78 in getMissingSymbol (recognizer=0x83e6a48, istream=0x83e5410,
e=0x83e9f70, expectedTokenType=4, follow=0xb6fe0810)
at src/antlr3baserecognizer.c:2199
#1 0xb73413e4 in recoverFromMismatchedToken (recognizer=0x83e6a48, ttype=4,
follow=0xb6fe0810) at src/antlr3baserecognizer.c:1510
#2 0xb73407b1 in match (recognizer=0x83e6a48, ttype=4, follow=0x0)
at src/antlr3baserecognizer.c:448
Information output from valgrind is similiar
==32170== at 0x4C45E78: getMissingSymbol (antlr3baserecognizer.c:2199)
==32170== by 0x4C453E3: recoverFromMismatchedToken
(antlr3baserecognizer.c:1510)
==32170== by 0x4C447B0: match (antlr3baserecognizer.c:448)
The code should be
token =
recognizer->state->tokFactory->newToken(recognizer->state->tokFactory);
2184
2185 // Set some of the token properties based on the current token
2186 //
2187 token->setLine (token,
current->getLine(current));
2188 token->setCharPositionInLine (token,
current->getCharPositionInLine(current));
2189 token->setChannel (token,
ANTLR3_TOKEN_DEFAULT_CHANNEL);
2190 token->setType (token,
expectedTokenType);
2191
2192 // Create the token text that shows it has been inserted
2193 //
2194 token->setText8(token, (pANTLR3_UINT8)"<missing ");
2195 text = token->getText(token);
2196
2197 if (text != NULL)
2198 {
2199 text->append8(text, (const char
*)recognizer->state->tokenNames[expectedTokenType]);
2200 text->append8(text, (const char *)">");
2201 }
Thanks
==============================
Regards,
Ronghui Yu
Sierra Atlantic
----- Original Message -----
From: Jim Idle
To: Ronghui Yu
Cc: [EMAIL PROTECTED]
Sent: Thursday, August 28, 2008 11:17 PM
Subject: Re: [antlr-interest] Is this a bug of ANTLR3.1?
On Thu, 2008-08-28 at 18:40 +0800, Ronghui Yu wrote:
I am using ANTLR3.1 for developing a SQL parser
One of my main rule looks like this
sql_statement:
sql_statement_command (';')?
But when generating parser codes from grammar file to C source, it always
take a very long time and consume as much as 5G memory because of the optional
semicolon
Then in order to make the development easier, I make the semicolon a
mandatory by removing the question mark, like this
sql_statement:
sql_statement_command ';'
It does make the building faster and require much less memory.
This indicates that there is something wrong with the formulation of your
grammar - getting the terminators correct in SQL is not easy.
But the problem now is, when parsing a statement without the semicolon,
such as the following
select * from tt
ANTLR won't handle this but issue a signal 11
His is the stack information when this happening, when all test has been
matched and is going to match the last semicolon
Program received signal SIGSEGV, Segmentation fault.
0xb7370a09 in getMissingSymbol () from
/home/oracle/install/lib/libantlr3c.so
(gdb) where
#0 0xb7370a09 in getMissingSymbol ()
from /home/oracle/install/lib/libantlr3c.so
#1 0xb73701d0 in recoverFromMismatchedToken ()
from /home/oracle/install/lib/libantlr3c.so
#2 0xb736f7bb in match () from /home/oracle/install/lib/libantlr3c.so
Yes - this probably is a bug. TO give me a bettr chance of seeing what is
happening, can you rebuild the runtime with debug information included (see
configure --help) and run it via valgrind? It is probably some boundary
condition that I did not anticipate.
Jim
__________________________________________________________________________________________________________________
DISCLAIMER:"The information contained in this message and the attachments (if
any) may be privileged and confidential and protected from disclosure. You are
hereby notified that any unauthorized use, dissemination, distribution or
copying of this communication, review, retransmission, or taking of any action
based upon this information, by persons or entities other than the intended
recipient, is strictly prohibited. If you are not the intended recipient or an
employee or agent responsible for delivering this message, and have received
this communication in error, please notify us immediately by replying to the
message and kindly delete the original message, attachments, if any, and all
its copies from your computer system. Thank you for your cooperation."
________________________________________________________________________________________________________________
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
List: http://www.antlr.org:8080/mailman/listinfo/antlr-interest
Unsubscribe:
http://www.antlr.org:8080/mailman/options/antlr-interest/your-email-address
