A while back I posted a question about how to get debugging working with eclipse in fedora 4. I am having some success, so if anyone else out there is interested here's how it is set up.
In regedit:
* disabled auto winedbg by renaming AeDebug I changed HKEY_LOCAL_MACHINE/Software/Microsoft/Windows NT/Current Version/AeDebug to AeDebug-DISABLED. Without this gdb doesn't seem to be able to get a hold of SEGFAULTs.
In eclipse's Run/Debug dialog box:
* set the c/c++ application to WINE_SRC/loader/wine-pthread WINE_SRC points to a compiled version of wine. For me, I got the wine src rpm and ran rpmbuild -bb. This is where main() is, which eclipse looks for at start up.
* put your .exe.so file on the Arguments tab
* choose the GDB Debugger on the Debugger tab
* add WINE_SRC on the Source tab as a "Filesystem directory with subdirectories"
The only weirdness so far is that sometimes (not always) the debugger suspends when a new thread is created. I just resume (F8) past that. And I am not sure what impact bypassing wine-preload's exec-shield workaround will have on me. More on that if I learn more.
But I gotta say that having a functioning IDE with integrated debugging on Linux is a major relief and, for me at least, a long time coming!
... mo
PS: I installed FC4, and then did yum update. eclipse is version 3.1.1 updated from the eclipse UI from the version that came with FC4.
Michael Ost wrote:
A while back I posted a question about how to get debugging working with eclipse in fedora 4. I am having some success, so if anyone else out there is interested here's how it is set up.
In regedit:
- disabled auto winedbg by renaming AeDebug I changed HKEY_LOCAL_MACHINE/Software/Microsoft/Windows NT/Current Version/AeDebug to AeDebug-DISABLED. Without this gdb doesn't seem to be able to get a hold of SEGFAULTs.
In eclipse's Run/Debug dialog box:
set the c/c++ application to WINE_SRC/loader/wine-pthread WINE_SRC points to a compiled version of wine. For me, I got the wine src rpm and ran rpmbuild -bb. This is where main() is, which eclipse looks for at start up.
put your .exe.so file on the Arguments tab
choose the GDB Debugger on the Debugger tab
add WINE_SRC on the Source tab as a "Filesystem directory with
subdirectories"
you could (not tested) alternatively: - set winegdb --gdb as the name for executing gdb - not reset the AeDebug key - set the executable to be the real exec (+ .so extension if run from the build tree) that should work also you would this way: - keep all the preloader stuff, so that your memory layout is better (and the same than when run from command line) - still be compatible with the segfault stuff A+
On Sat, 2006-01-07 at 18:04 +0100, Eric Pouech wrote:
you could (not tested) alternatively:
- set winegdb --gdb as the name for executing gdb
- not reset the AeDebug key
- set the executable to be the real exec (+ .so extension if run from
the build tree) that should work also you would this way:
- keep all the preloader stuff, so that your memory layout is better
(and the same than when run from command line)
- still be compatible with the segfault stuff
I'll try that and let you know what I find once my development tree gets usable again. It's pretty hacked up right now. Thanks ... mo
On Sat, 2006-01-07 at 18:04 +0100, Eric Pouech wrote:
Michael Ost wrote:
A while back I posted a question about how to get debugging working with eclipse in fedora 4. I am having some success, so if anyone else out there is interested here's how it is set up.
you could (not tested) alternatively:
- set winegdb --gdb as the name for executing gdb
- not reset the AeDebug key
- set the executable to be the real exec (+ .so extension if run from
the build tree) that should work also
Just tried this and eclipse says "Exec error: Cannot run winedbg --gdb". winedbg --gdb MYAPP does launch from the command line, however. Any suggestions?
BTW winedbg MYAPP ARGS works better. with the --gdb flag MYAPP doesn't terminate properly. But I'll get to that later.
you would this way:
- keep all the preloader stuff, so that your memory layout is better
(and the same than when run from command line)
- still be compatible with the segfault stuff
Agreed, if I can get it to work! Thanks ... mo
Michael Ost wrote:
On Sat, 2006-01-07 at 18:04 +0100, Eric Pouech wrote:
Michael Ost wrote:
A while back I posted a question about how to get debugging working with eclipse in fedora 4. I am having some success, so if anyone else out there is interested here's how it is set up.
you could (not tested) alternatively:
- set winegdb --gdb as the name for executing gdb
- not reset the AeDebug key
- set the executable to be the real exec (+ .so extension if run from
the build tree) that should work also
Just tried this and eclipse says "Exec error: Cannot run winedbg --gdb". winedbg --gdb MYAPP does launch from the command line, however. Any suggestions?
BTW winedbg MYAPP ARGS works better. with the --gdb flag MYAPP doesn't terminate properly. But I'll get to that later.
you mean (about MYAPP ARGS) when run in eclipse (that it does work to some extend, wheread MYAPP fails) ?
On Tue, 2006-01-24 at 22:27 +0100, Eric Pouech wrote:
Michael Ost wrote:
BTW winedbg MYAPP ARGS works better. with the --gdb flag MYAPP doesn't terminate properly. But I'll get to that later.
you mean (about MYAPP ARGS) when run in eclipse (that it does work to some extend, wheread MYAPP fails) ?
No, that running winedbg MYAPP from the command line works. And that winedbg --gdb MYAPP from the command line doesn't terminate properly. I tried those as a way to confirm that what I am asking eclipse to do for debugging actually works from the command line.
Cheers... mo
-
Eric Pouech -
Michael Ost