Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 330009

Summary:	Sorting of follow-up errors from gcc in Problems tab
Product:	[Tools] CDT	Reporter:	David Björkevik <david>
Component:	cdt-build	Assignee:	Project Inbox <cdt-core-inbox>
Status:	RESOLVED WORKSFORME	QA Contact:	Doug Schaefer <cdtdoug>
Severity:	minor
Priority:	P3	CC:	cdtdoug
Version:	7.0.1
Target Milestone:	---
Hardware:	PC
OS:	Linux
Whiteboard:

Description David Björkevik

2010-11-11 10:51:34 EST

Sometimes gcc/g++ emits follow-up errors with more information, such as "in this context", "instantiated from here" or "candidate is...".

Due to the way errors are sorted in Problems, the relationship between the follow-up error and the original error is lost. This makes it especially hard to debug errors related to the use of templates.

For instance, if the wrong type is used for templates, the main error will show up in libstdc++, and the follow-up error shows where the problem is.

Comment 1 Andrew Gvozdev

2010-11-11 11:07:21 EST

I would recommend to work with Console View on those. You can doubleclick on the error line to navigate to the source code from there.

Comment 2 Andrew Gvozdev

2010-12-01 11:50:26 EST

Actually, there is even a way to set up the Problems View.
1. In View Menu (click the small triangle in right upper corner of the panel, next to "Minimize") select Preferences and add ID to the list of shown columns.
2. In View Menu select "Group By" as None.
3. Select "Sort By" by ID.

This way you gonna get the markers in order of creation, and related ones will be close to each other.