https://bugs.winehq.org/show_bug.cgi?id=52444
Bernhard Übelacker bernhardu@mailbox.org changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |bernhardu@mailbox.org
--- Comment #2 from Bernhard Übelacker bernhardu@mailbox.org --- A little off topic:
At least a standalone, regular linux gdb can be made loading the debug information from the mingw-built PE files with the gdbinit.py script by Rémi Bernon.
https://www.winehq.org/pipermail/wine-devel/2021-June/189134.html https://www.winehq.org/pipermail/wine-devel/2022-January/205224.html
There is also prototype of gdb able to iterate a processes dll list (currently just 64-bit processes) and load also the symbols from a mingw-built PE file.
https://github.com/JuliaComputing/gdb-solib-wine
----
Back on topic:
I tried now a windows eclipse package and a (quite old) i686 mingw windows gdb package which kind of worked with breaking into the process but eclipse has graphical glitches and showed most frames in winnt.h function NtCurrentTeb (which the gdb.exe did also interactively).
Therefore just to clarify - you want (unlike my short test above) to use a linux eclipse with a linux gdb to attach to a process running with wine from a tree built without mingw?