Debugger bugs

[Mike Hearn]

Hi guys,

I've got a few problems with various debuggers. Can anybody help?

1) gdb doesn't seem to catch signals to sent to Wine. In a crash, winedbg
is invoked without gdb ever being aware of it.

2) winedbg can't locate files anymore, the paths seem to be stripped:

0x401cdb48 fixup_imports [loader.c:509] in ntdll: movl  0x0(%eax),%edx
Unable to open file loader.c
Wine-dbg>list
Wine-dbg>

3) winedbg won't print the values of local variables:

Wine-dbg>print i
fixme:dbghelp:SymGetTypeInfo Someone didn't properly set ModBase (0x4078ebfc)
fixme:winedbg:print_value ---error

thanks -mike

[Eric Pouech]

Mike Hearn a écrit :
> Hi guys,
>
> I've got a few problems with various debuggers. Can anybody help?
>
> 1) gdb doesn't seem to catch signals to sent to Wine. In a crash, winedbg
> is invoked without gdb ever being aware of it.
> run the winedbg in gdb proxy mode, this should work fine.
>
> 2) winedbg can't locate files anymore, the paths seem to be stripped:
>
> 0x401cdb48 fixup_imports [loader.c:509] in ntdll: movl  0x0(%eax),%edx
> Unable to open file loader.c
> Wine-dbg>list
> Wine-dbg>
> what does 'info share' report on ntdll ? (normally we should get full 
> path if stabs support is present)
> A+
> 3) winedbg won't print the values of local variables:
>
> Wine-dbg>print i
> fixme:dbghelp:SymGetTypeInfo Someone didn't properly set ModBase (0x4078ebfc)
> fixme:winedbg:print_value ---error
> this should be fixed RSN (for the moment, 'info locals' should work instead)

[Mike Hearn]

Eric Pouech <pouech-eric(a)wanadoo.fr> writes:
> what does 'info share' report on ntdll ? (normally we should get full
> path if stabs support is present)

I'm not sure, I'll check next time this happens ...
> > 3) winedbg won't print the values of local variables:
> > Wine-dbg>print i
> > fixme:dbghelp:SymGetTypeInfo Someone didn't properly set ModBase (0x4078ebfc)
> > fixme:winedbg:print_value ---error
> > this should be fixed RSN (for the moment, 'info locals' should work instead)

Cool. Another bug: I always get a stack dump starting at zero that
contains all zeros (ie the stack dumping doesn't seem to be working)

thanks -mike

[Eric Pouech]

Mike Hearn a écrit :
> Eric Pouech <pouech-eric(a)wanadoo.fr> writes:
> > what does 'info share' report on ntdll ? (normally we should get full
> > path if stabs support is present)
>
> I'm not sure, I'll check next time this happens ...
> and a recent fix by Alexandre may also have a positive impact on this
> Cool. Another bug: I always get a stack dump starting at zero that
> contains all zeros (ie the stack dumping doesn't seem to be working)
> thx, I fixed it in my tree
> A+