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 M
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 (n
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)
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 wo
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_MAC
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/Microso
