Bug 394094 - [Analysis: From Ganymede+CDT5.0.2 to Juno+CDT8.1.0] Debug-Mode freezes with DSF depending on GDB-Version ; Debug Mode gives error messages without DSF
Summary: [Analysis: From Ganymede+CDT5.0.2 to Juno+CDT8.1.0] Debug-Mode freezes with D...
Status: NEW
Alias: None
Product: CDT
Classification: Tools
Component: cdt-debug (show other bugs)
Version: 8.1.0   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: cdt-debug-inbox@eclipse.org CLA
QA Contact: Jonah Graham CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-11-12 09:03 EST by Robert Hartmann CLA
Modified: 2020-09-04 15:22 EDT (History)
3 users (show)

See Also:


Attachments
Analysis: From Ganymede+CDT5.0.2 to Juno+CDT8.1.1; error messages, screenshots etc. (7.47 MB, application/pdf)
2012-11-12 09:03 EST, Robert Hartmann CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Robert Hartmann CLA 2012-11-12 09:03:31 EST
Created attachment 223450 [details]
Analysis: From Ganymede+CDT5.0.2 to Juno+CDT8.1.1; error messages, screenshots etc.

Long story in short:
After moving some C , C++ projects placed on an USB-stick between
different versions of Eclipse/CDT environments I discovered some “unfriendly” behavior while using GDB from MinGW as debugger inside the CDT-Eclipse-Plug-In:
You can’t start or end the Debug-Run operation, because
•  you get error messages from invalid path or environment settings
•  you get no error messages, but the launching mechanism doesn’t work 
•  launching mechanism freezes
•  you can’t terminate a launching process
On other Eclipse/CDT environments none of these problems occur with the same projects on the same USB-stick.
That forces me to do some behavior researches on systematically chosen Eclipse/CDT environments.
I did my research on Windows XP Home SP3 (German version), but I could verify it on Windows XP Professional SP3 (English version).

For my complete analysis please see the attached file. It containts screenshots as "pdf_file_attachments" inside. 



Best regards,
 Robert