I am using winegcc/wineg++ to port a windows application to linux.
Everything works fine and I produce .a library files that I link to create executable (exe.so) files.
My problem is that I can not set breakpoints when I am debugging. I start winegdb on my exe.so and write "break <symbol>" where <symbol> is a symbol in n .a library that the .exe.so was linked with. But the symbol is newer recognized and when I "continue" in winegdb the break point is never reached.
I can however set breakpoints in .dll.so files such as the ones the are shipped with wine.
Is it possible to set breakpoints in .a libraries?
Debugging .a library created with winegcc
-
- Level 5
- Posts: 336
- Joined: Mon Nov 24, 2008 8:10 am
I'm not sure on what functions you can set breakpoints but it might be that winedbg only works on symbols which are 'visible'. When you compile a wine dll (.dll.so) a .spec file is used for exporting functions so that they can be linked to from programs or dlls. This info might be crucial (not sure). You could also try to set a breakpoint on the address (if you know it) or use gdb in combination with wine (there is some proxy mechanism).