Bug 415557 - EOF character (^Z) and newer CDT versions
Summary: EOF character (^Z) and newer CDT versions
Status: NEW
Alias: None
Product: CDT
Classification: Tools
Component: cdt-indexer (show other bugs)
Version: 8.2   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact: Jonah Graham CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-08-21 06:21 EDT by Kim Brouer CLA
Modified: 2020-09-04 15:19 EDT (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Kim Brouer CLA 2013-08-21 06:21:25 EDT 
The CDT indexers shipping with Juno and Kepler seem to dislike the ASCII character 26 (0x1A), that some Windows editors like to insert at the end of the file.

In those files, CDT doesn't find any references to static, file-scope variables.

The parser log says:
----
  Scanner problems:
     Bad character sequence encountered:  in file: C:\...\xyz.c:444
----

If I modify the file and save it in Eclipse, it reparses and finds the references, even though the EOF character is still there and the parser log also still contains the message.

Modifying the file in an external editor, again leaving the EOF in place, makes the problem reappear.

The CDT in Indigo never exhibited any issues with those files.