Bug 110472 - CDT parser aborts when editing simple source file
Summary: CDT parser aborts when editing simple source file
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Developer Suite
Classification: Retired
Component: eclipse
Version: 1.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jeremy Handcock
QA Contact: eclipse-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-11-19 20:10 UTC by Jeremy Handcock
Modified: 2007-04-18 16:59 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2003-12-17 16:34:28 UTC
Embargoed:


Attachments (Terms of Use)

Description Jeremy Handcock 2003-11-19 20:10:28 UTC
Description of problem:
I was editing a Hello World program using the CDT editor, and the
parser threw up on more than one occasion.

Version-Release number of selected component (if applicable):
snapshot-20031119-eclipse-2.1.1-3


How reproducible: Sometimes

Steps to Reproduce:
1. Edit a source file with the CDT editor
2.
3.
  
Actual results: I get things like the following printed on the console
where I started eclipse:

[snip]
Parse Aborted: Encountered "<EOF>" at line 63, column 8.
Was expecting:
    <CloseQuote2> ...

        Parse Aborted: Encountered "<EOF>" at line 250, column 3.
        Was expecting one of:
            <ArgName> ...
                <TagEnd> ...

                    Parse Aborted: Encountered "<EOF>" at line 492,
column 20.
                    Was expecting:
                        <CloseQuote2> ...
[/snip]

... which is odd, becuase my source file is not 492 lines long.  I
will investigate this further and move the PR upstream.

Comment 1 Tom Tromey 2003-11-21 17:10:27 UTC
Jeremy, I'm assigning these to you for triage, since you said
on the list you'd be looking at them.


Comment 2 Jeremy Handcock 2003-12-17 16:34:28 UTC
After examining the upstream bugs against the CDT parser, I've decided
to close this here.  There are still numerous problems with the 1.2
parser and NPEs in the parser code are not uncommon.  Until the parser
is stabilized upstream, we will continue to have sporadic problems
like this.


Note You need to log in before you can comment on or make changes to this bug.