Bug 571298 - Eclipse Corrosion error push a stop to debugger starting "launchConfigEnv is null"
Summary: Eclipse Corrosion error push a stop to debugger starting "launchConfigEnv is ...
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 4.20   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-02-18 08:08 EST by Edrae de Minvoort CLA
Modified: 2021-02-19 05:31 EST (History)
0 users

See Also:

Attachments
Pop-up error when launching a debbug session (28.97 KB, image/jpeg)
2021-02-18 08:08 EST, Edrae de Minvoort CLA 		no flags Details
View All 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 Edrae de Minvoort CLA 2021-02-18 08:08:31 EST 
Created attachment 285594 [details]
Pop-up error when launching a debbug session

I change my Hard drive and so I made a fresh Eclipse Corrosion install but I kept my Rust projets. Problem is I get an error when I launch my prog in debug mode. It seems to work in run mode but I didn't test this that much.

Error is :
An internal error occurred during: "Launching my_prog". Cannot read the array length because "launchConfigEnv" is null

Important note : it seems to be linked with the use of an input file (debug configuration/common/input file)

I try many things, many installs, new projects, many, many things but nothing works (and I cannot figure out what launchConfigEnv is).
Comment 1 Edrae de Minvoort CLA 2021-02-19 05:31:26 EST 
I install 2019.12 Eclipse and it works fine. I will work a little with this version and try out more configuration to shrink the problem.