[cdt-dev] FW: New: Indexer hangs while "Computing Macro Expansion"

["Schaefer, Doug" <Doug.Schaefer@xxxxxxxxxxxxx>]

Our first componentized bug report :). I like how it looks.

Cheers,
D. 

-----Original Message-----
From: bugzilla-daemon@xxxxxxxxxxx [mailto:bugzilla-daemon@xxxxxxxxxxx] 
Sent: Tuesday, December 23, 2008 3:25 PM
To: Schaefer, Doug
Subject: [Bug 259600] New: Indexer hangs while "Computing Macro
Expansion"

https://bugs.eclipse.org/bugs/show_bug.cgi?id=259600
Product/Component: CDT / cdt-indexer
           Summary: Indexer hangs while "Computing Macro Expansion"
           Product: CDT
           Version: 6.0
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P3
         Component: cdt-indexer
        AssignedTo: cdt-core-inbox@xxxxxxxxxxx
        ReportedBy: steve.t.andrews@xxxxxxxxxxxxxx
         QAContact: markus.schorn@xxxxxxxxxxxxx


Build ID: I20081211-1908

Steps To Reproduce:
1.
2.
3.
We have a file in one of the projects we index that contains a template
decl that resembles the following:

       template <class T>
            class DumbPtr {
            public:

                DumbPtr<T> ();

                DumbPtr<T> (T* aPtr);

                DumbPtr<T> (const DumbPtr<T>& aObj);

                ~DumbPtr<T> ();

                ...

Note the (unusual? incorrect?) angle-bracket syntax that follows each
method prototype.  I thought that syntax was correct only for the
definition of the template methods, not their declaration -- but
template does compile under gcc 4.0.2.

During indexing, the indexer hangs on the file containing that template,
pegging the CPU and using significant memory.  There is no crash; but
indexing never completes.

When I remove the superflous angle brackets AND rebuild the project
indexes, indexing completes in a timely manner.


More information:
Can't provide the exact template due to confidentiality.


--
Configure bugmail: https://bugs.eclipse.org/bugs/userprefs.cgi?tab=email
------- You are receiving this mail because: ------- You are watching
the assignee of the bug.