ESP-IDF plugin C indexing destroyed by last Eclipse 2024-06 (4.32.0) update (IEP-1259)

[powerbroker]

After update Eclipse to latest version ESP-IDF C project indexer is totally broken. It generates tons of fake errors about implicitly included headers like "Symbol 'false' could not be resolved", "Type 'uint8_t' could not be resolved", "Unresolved inclusion: "esp_log.h", etc.

In the opposite to behavior of previous version, manual Index/Rebuild could help. Now it doesn't work at all, making error highlighting absolutely useless.

To Reproduce

1. Ensure following Eclipse version:
   Eclipse IDE for Embedded C/C++ Developers (includes Incubating components)
   Version: 2024-06 (4.32.0)
   Build id: 20240606-1231
   Java vendor: Eclipse Adoptium
   Java runtime version: 21.0.3+9-LTS
   Java version: 21.0.3
2. Extend JVM memory by -Xms2048m and e.g. -Xmx16324m in eclipse.ini, so Eclipse most likely won't hang on ESP-IDF project.
3. Ensure latest stable or even beta ESP-IDF plugin is installed
4. In Preferences / C/C++ / Indexer enable eager indexing: 'Index source files not included...', 'Index unused headers', 'Index all header variants', 'Allow heuristic resolution ...'
5. Open attached project, build it. Note successful build and binary generation.
6. Enforce manual 'Index / Rebuild' from project context menu.
7. Enjoy tons of fake errors in 'Problems' tab and error markers in source text editor.

Expected behavior
No fake errors muzz be generated when code builds successfully

Espressif-IDE Product Information:
Operating System: windows 11
Java Runtime Version: 21.0.3+9-LTS
Eclipse Version: 4.32.0.v20240601-0610
Eclipse CDT Version: 11.6.0.202403071917
IDF Eclipse Plugin Version: 3.0.0.202406051940
ESP-IDF v5.2.1-dirty
Python set for IDF_PYTHON_ENV: Python 3.9.16

ESP32-Blink-fucking.zip

[AndriiFilippov]

hi @powerbroker !

I don't see this issue on the master version. You can try it by using the artifacts down below on this page: https://github.com/espressif/idf-eclipse-plugin/actions/runs/10849628637 . Let me know if you experience this issue there as well. Thanks