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

Bug 328565

Summary:	Slow starting debug session when application have too much debug symbols
Product:	[Tools] CDT	Reporter:	Dimitar Peikov <Dimitar.Peikov>
Component:	cdt-debug	Assignee:	cdt-debug-inbox <cdt-debug-inbox>
Status:	NEW ---	QA Contact:	Jonah Graham <jonah>
Severity:	major
Priority:	P3	CC:	aegges, cdtdoug, pawel.1.piech
Version:	8.0
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Dimitar Peikov

2010-10-25 02:44:22 EDT

Build Identifier:  20100917-0705

If the debugging application have plenty of symbols, the time for launching is annoyng. For example with 20k symbols (produced by generated code) you may wait about a minute, and when starting gdb from console prompt is immediate. Is it possible to have symbol loading running in background ?

Reproducible: Always

Steps to Reproduce:
1. generate a project with 20k symbols (classes, functions, enumerations, variables, ...)
2. compile and start debugging
3.

Comment 1 Axel Mueller

2011-03-01 07:19:49 EST

(In reply to comment #0)
> Build Identifier:  20100917-0705
> 
> If the debugging application have plenty of symbols, the time for launching is
> annoyng. For example with 20k symbols (produced by generated code) you may wait
> about a minute, and when starting gdb from console prompt is immediate. Is it
> possible to have symbol loading running in background ?
> 
> Reproducible: Always
> 
> Steps to Reproduce:
> 1. generate a project with 20k symbols (classes, functions, enumerations,
> variables, ...)
> 2. compile and start debugging
> 3.
I guess gdb needs so much time to start because of all the source folders Eclipse passes to gdb.
Try the following:
- open your debug launch configuration
- select the source tab
- remove the "Default" source lookup path
- Add Absolute File Path