Bug 576352 - Eclipse not functioning after mac upgrade
Summary: Eclipse not functioning after mac upgrade
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 4.22   Edit
Hardware: PC Mac OS X
: P3 critical (vote)
Target Milestone: ---   Edit
Assignee: JDT-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2021-09-30 06:54 EDT by Ananthu K Kumar CLA
Modified: 2023-09-21 13:18 EDT (History)
2 users (show)

See Also:


Attachments
error showing up (846.34 KB, image/png)
2021-09-30 06:54 EDT, Ananthu K Kumar CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ananthu K Kumar CLA 2021-09-30 06:54:11 EDT
Created attachment 287239 [details]
error showing up

I recently upgraded my Mac to Big Sur and all the eclipse configurations were lost. I reconfigured but now the codes stops at a particular line and won't go ahead.

I created a new workspace and it worked fine but the same issue rose again next day. 

The issue is not in the code as I'm successfully running it in Windows and Linux.
Comment 1 Sarika Sinha CLA 2021-09-30 07:12:14 EDT
What does it show on "Details" button click?
Any error logged in error log view or file?
Comment 2 Thomas Wolf CLA 2021-09-30 07:25:09 EDT
Just some observations from the screenshot:

The code is using the Java 1.8 libraries but run with a Java 13 JVM. Perhaps that contributes to the problem. I'd double-check compiler settings (source/target/release), and what java is actually used, and what libraries are picked up when the program is run.

Also check what execution environment is defined in the launch config.

Also, it seems that project is using JRE System Libraries that are part of the project itself [jre1.8.0_241]. The second project visible in the screenshot uses [JavaSE-1.8].
Comment 3 Eclipse Genie CLA 2023-09-21 13:18:12 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.