Graphical debugging instead of winedbg

[Ann and Jason Edmeades]

Hi

I was trying to get a gui replacement for winedbg as I can never remember
how to view memory etc, and saw 
http://www.winehq.com/site/docs/wine-devel/dbg-others 
where it talks about using kdbg. I was looking at a simple trap and thought
it ideal to test with....

So...

1. Winedbg:
I can get to the trap by winedbg program.exe, cont, and it stops and
displays everything ok

2. KDBG: I launch winedbg --gdb --no-start program.exe, and it starts and
issues the line target remote localhost:32835

I then issue kdbg -r localhost:32835 /usr/local/bin/wine-pthread and get a
popup stating "Sorry - KDbg, gdb: Using host libthread_db library
"/lib/tls/libthread_db.co.1" with an ok button

I click the ok button and the console I launched winedbg in issues various
messages about "loads DLL c:\windows\system\user32 etc etc and eventually
exception code=0x80000003 but nothing ever happens to the GUI

Note this is with cvs and Mandrake 10 if it makes any difference.

How do I get the gui support working?

3. Can we use msdev.exe or windbg.exe to debug under wine yet, now the
dbghelp is more functional? (I haven't tried for a long time)

Regards,
Jason

[Eric Pouech]

Ann and Jason Edmeades a écrit :
> Hi
>
> I was trying to get a gui replacement for winedbg as I can never remember
> how to view memory etc, and saw 
> http://www.winehq.com/site/docs/wine-devel/dbg-others 
> where it talks about using kdbg. I was looking at a simple trap and thought
> it ideal to test with....
>
> So...
> - Winedbg:
>
> I can get to the trap by winedbg program.exe, cont, and it stops and
> displays everything ok
> - KDBG: I launch winedbg --gdb --no-start program.exe, and it starts and
>
> issues the line target remote localhost:32835
>
> I then issue kdbg -r localhost:32835 /usr/local/bin/wine-pthread and get a
> popup stating "Sorry - KDbg, gdb: Using host libthread_db library
> "/lib/tls/libthread_db.co.1" with an ok button
>
> I click the ok button and the console I launched winedbg in issues various
> messages about "loads DLL c:\windows\system\user32 etc etc and eventually
> exception code=0x80000003 but nothing ever happens to the GUI
>
> Note this is with cvs and Mandrake 10 if it makes any difference.
>
> How do I get the gui support working?

two remarks:
- you indeed try to start two winegdb instances, and this won't work (at step 1 
& 2). You need to start your program at step 2.
- I get the same issue with kdbg as the one you described. More interestingly it 
also happens with non wine binaries, so I wonder if it's not an issue between 
kdbg and gdb.
> - Can we use msdev.exe or windbg.exe to debug under wine yet, now the
>
> dbghelp is more functional? (I haven't tried for a long time)

I haven't tried very recently, but windbg didn't fully work.

[Oliver Stieber]

--- Eric Pouech  wrote:
> Ann and Jason Edmeades a écrit :
> > Hi
> >
> > I was trying to get a gui replacement for winedbg
>
> as I can never remember
> > how to view memory etc, and saw

http://www.winehq.com/site/docs/wine-devel/dbg-others
> > where it talks about using kdbg. I was looking at
>
> a simple trap and thought
> > it ideal to test with....
> >
> > So...
> > - Winedbg:
> >
> > I can get to the trap by winedbg program.exe,
>
> cont, and it stops and
> > displays everything ok
> > - KDBG: I launch winedbg --gdb --no-start
>
> program.exe, and it starts and
> > issues the line target remote localhost:32835
> >
> > I then issue kdbg -r localhost:32835
>
> /usr/local/bin/wine-pthread and get a
> > popup stating "Sorry - KDbg, gdb: Using host
>
> libthread_db library
> > "/lib/tls/libthread_db.co.1" with an ok button
> >
> > I click the ok button and the console I launched
>
> winedbg in issues various
> > messages about "loads DLL c:\windows\system\user32
>
> etc etc and eventually
> > exception code=0x80000003 but nothing ever happens
>
> to the GUI
> > Note this is with cvs and Mandrake 10 if it makes
>
> any difference.
> > How do I get the gui support working?
>
> two remarks:
> - you indeed try to start two winegdb instances, and
>
> this won't work (at step 1 
> & 2). You need to start your program at step 2.
> - I get the same issue with kdbg as the one you
>
> described. More interestingly it 
> also happens with non wine binaries, so I wonder if
> it's not an issue between 
> kdbg and gdb.
> > - Can we use msdev.exe or windbg.exe to debug
>
> under wine yet, now the
> > dbghelp is more functional? (I haven't tried for a
>
> long time)
> I haven't tried very recently, but windbg didn't
> fully work.

KDBG seems to be working ok, except when I select run
winedbg reports

Unknown packet request vCont?
00000015:00000016: exception code=0x406d1388

http://www.rons.net.cn/htp/gdb/gdb_33.html

vCount should be valid so I'll see if I can find out
what's not going on.

I've tried ddd and get the same error.

[Ann and Jason Edmeades]

> KDBG seems to be working ok, except when I select run
> winedbg reports
> Unknown packet request vCont?
> 00000015:00000016: exception code=0x406d1388
> http://www.rons.net.cn/htp/gdb/gdb_33.html
> vCount should be valid so I'll see if I can find out
> what's not going on.
> I've tried ddd and get the same error.

Weird - I just cannot get things working with this one. I'm happy to try any
graphical environment, or update portions of my Linux to get it working -
Any suggestions on where to start?

Jason

[Oliver Stieber]

> > vCount should be valid so I'll see if I can find
>
> out
> > what's not going on.
>
> Weird - I just cannot get things working with this
> one. I'm happy to try any
> graphical environment, or update portions of my
> Linux to get it working -
> Any suggestions on where to start?

kdbg and ddd work fine it's just that winedbg is
missing some gdb remote debugging proxying.

I used
winedebug --gdb --no-start myapp.exe

For DDDd

load wine-pthread in ddd
entered the 'target remote localhost:######'
then typed 
cont.

For kdbg (1.9.5) kde 3.2.3

kdbg -r localhost:##### /usr/bin/wine-pthread
> Jason

___________________________________________________________ 
ALL-NEW Yahoo! Messenger - all new features - even more fun! http://uk.messenger.yahoo.com

[Oliver Stieber]

--- Ann and Jason Edmeades
 wrote:
> > KDBG seems to be working ok, except when I select
>
> run
> > winedbg reports
> > Unknown packet request vCont?
> > 00000015:00000016: exception code=0x406d1388
> > http://www.rons.net.cn/htp/gdb/gdb_33.html
> > vCount should be valid so I'll see if I can find
>
> out
> > what's not going on.
> > I've tried ddd and get the same error.
>
> Weird - I just cannot get things working with this
> one. I'm happy to try any
> graphical environment, or update portions of my
> Linux to get it working -
> Any suggestions on where to start?

I'm also running with

bash-2.05b# gdb --version
GNU gdb 6.2.1
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General
Public License, and you are
welcome to change it and/or distribute copies of it
under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show
warranty" for details.
This GDB was configured as "i686-pc-linux-gnu".

Jason, VCont's almost finished (well pending testing)
I'll send through a patch if you want to test it
first.

I've got a couple of nasties[lockups] in d3d9 that I
want to make sure have nothing to do with d3d9, and
winedbg was getting a bit too tricky to drill down
through structures and check pointers, with kdbg can I
do that easly.
> Jason

___________________________________________________________ 
ALL-NEW Yahoo! Messenger - all new features - even more fun! http://uk.messenger.yahoo.com

[Ann and Jason Edmeades]

Hi,
> > - Winedbg:
> >
> > I can get to the trap by winedbg program.exe, cont, and it stops and
> > displays everything ok
> > - KDBG: I launch winedbg --gdb --no-start program.exe, and it starts and
> >
> > issues the line target remote localhost:32835
> >
> > I then issue kdbg -r localhost:32835 /usr/local/bin/wine-pthread and geta
> > popup stating "Sorry - KDbg, gdb: Using host libthread_db library
> > "/lib/tls/libthread_db.co.1" with an ok button
> >
> > I click the ok button and the console I launched winedbg in issues

various
> > messages about "loads DLL c:\windows\system\user32 etc etc and eventually
> > exception code=0x80000003 but nothing ever happens to the GUI
> >
> > Note this is with cvs and Mandrake 10 if it makes any difference.
> >
> > How do I get the gui support working?
> two remarks:
> - you indeed try to start two winegdb instances, and this won't work (at
>
> step 1 & 2). You need to start your program at step 2.

Sorry, my first step was meant to show debugging standalone, ie with winedbg
works fine, ie there's no compile time issue
> - I get the same issue with kdbg as the one you described. More
>
> interestingly it also happens with non wine binaries, so I wonder if it's
> not an issue between kdbg and gdb.

Can you recommend a graphical debugger which can drive winedbg in this way?
I really cant remember the syntax for examining memory, stacks, registers
etc!

Jason

[Oliver Stieber]

--- Eric Pouech  wrote:
> Ann and Jason Edmeades a écrit :
> > Hi
> >
> > I was trying to get a gui replacement for winedbg
>
> as I can never remember
> > how to view memory etc, and saw

http://www.winehq.com/site/docs/wine-devel/dbg-others
> > where it talks about using kdbg. I was looking at
>
> a simple trap and thought
> > it ideal to test with....
> >
> > So...
> > - Winedbg:
> >
> > I can get to the trap by winedbg program.exe,
>
> cont, and it stops and
> > displays everything ok
> > - KDBG: I launch winedbg --gdb --no-start
>
> program.exe, and it starts and
> > issues the line target remote localhost:32835
> >
> > I then issue kdbg -r localhost:32835
>
> /usr/local/bin/wine-pthread and get a
> > popup stating "Sorry - KDbg, gdb: Using host
>
> libthread_db library
> > "/lib/tls/libthread_db.co.1" with an ok button
> >
> > I click the ok button and the console I launched
>
> winedbg in issues various
> > messages about "loads DLL c:\windows\system\user32
>
> etc etc and eventually
> > exception code=0x80000003 but nothing ever happens
>
> to the GUI
> > Note this is with cvs and Mandrake 10 if it makes
>
> any difference.
> > How do I get the gui support working?
>
> two remarks:
> - you indeed try to start two winegdb instances, and
>
> this won't work (at step 1 
> & 2). You need to start your program at step 2.
> - I get the same issue with kdbg as the one you
>
> described. More interestingly it 
> also happens with non wine binaries, so I wonder if
> it's not an issue between 
> kdbg and gdb.
> > - Can we use msdev.exe or windbg.exe to debug
>
> under wine yet, now the
> > dbghelp is more functional? (I haven't tried for a
>
> long time)
> I haven't tried very recently, but windbg didn't
> fully work.

KDBG seems to be working ok, except when I select run
winedbg reports

Unknown packet request vCont?
00000015:00000016: exception code=0x406d1388

http://www.rons.net.cn/htp/gdb/gdb_33.html

I had a look at wineDBG and sure enough it's not
there, vCont is just cont[sig], step[sig] with an
optional thread ID so I'll hack something out to get
ddd and kdbg working (maybe missing the tid for now)