winedbg doesn't find source files

[Saulius Krasuckas]

When using CVS version of Wine I cannot get much debug:

[s2@katleriai Spawn]$ WINEDEBUG=+volume winedbg winecfg
fixme:console:SetConsoleCtrlHandler (0x4066a644,1) - no error checking or testing yet
WineDbg starting on pid 0xa
In 32 bit mode.
Unable to open file /process.c
Wine-dbg>br GetDriveTypeW
fixme:dbghelp:elf_lookup_symtab Already found symbol add_paint_count (/usr/src/wine-cvs/wine/dlls/user/../../windows/painting.c) in symtab painting.c @00074738 and painting.c @000a026c
fixme:dbghelp:elf_load_debug_info Unsupported Dwarf2 information
Breakpoint 1 at 0x403be249 GetDriveTypeW [volume.c:1418] in kernel32
Wine-dbg>c
fixme:winecfg:WinMain The winecfg tool is not yet complete, and does not actually alter your configuration.
fixme:winecfg:WinMain If you want to alter the way Wine works, look in the ~/.wine/config file for more information.
trace:volume:GetVolumeInformationW cannot open device L"\\.\C:": err 2
Stopped on breakpoint 1 at 0x403be249 GetDriveTypeW [volume.c:1418] in kernel32
Unable to open file volume.c
Wine-dbg>list 10
Wine-dbg>quit
WineDbg terminated on pid 0xa

I have had a long period of time not using the winedbg, so I cannot tell
whether it is a regression.  I am using "./configure && make depend &&
make" to build the Wine and then something like a "sudo make install", if
that matters.

I need an advice on how to setup winedbg the right way or an explanation,
whether this is a bug or an advanced feature.  TIA.

[Mike Hearn]

Saulius Krasuckas wrote:
> I have had a long period of time not using the winedbg, so I cannot tell
> whether it is a regression.  I am using "./configure && make depend &&
> make" to build the Wine and then something like a "sudo make install", if
> that matters.
>
> I need an advice on how to setup winedbg the right way or an explanation,
> whether this is a bug or an advanced feature.  TIA.

Nope, it's a bug, something to do with STABS parsing I think. I have 
reported it once to Eric but I think I didn't have enough info to help him.

[Vincent Béron]

Le mer 11/08/2004 à 04:50, Mike Hearn a écrit :
> Saulius Krasuckas wrote:
> > I have had a long period of time not using the winedbg, so I cannot tell
> > whether it is a regression.  I am using "./configure && make depend &&
> > make" to build the Wine and then something like a "sudo make install", if
> > that matters.
> >
> > I need an advice on how to setup winedbg the right way or an explanation,
> > whether this is a bug or an advanced feature.  TIA.
>
> Nope, it's a bug, something to do with STABS parsing I think. I have 
> reported it once to Eric but I think I didn't have enough info to help him.

The original message had this line:
fixme:dbghelp:elf_load_debug_info Unsupported Dwarf2 information

So I suspect your Wine is compiled with Dwarf2 debug symbols rather than
stabs+. Which gcc version was used?

Vincent

[Mike Hearn]

> The original message had this line:
> fixme:dbghelp:elf_load_debug_info Unsupported Dwarf2 information
>
> So I suspect your Wine is compiled with Dwarf2 debug symbols rather than
> stabs+. Which gcc version was used?

Yep but I see this problem even without that fixme, so I think it's 
generic ...

[Saulius Krasuckas]

On Wed, 11 Aug 2004, Mike Hearn wrote:
> > The original message had this line:
> > fixme:dbghelp:elf_load_debug_info Unsupported Dwarf2 information
> >
> > So I suspect your Wine is compiled with Dwarf2 debug symbols rather than
> > stabs+. Which gcc version was used?
>
> Yep but I see this problem even without that fixme, so I think it's 
> generic ...

Does this mean no developers are able to perform human-understandable
stepping and nexting at winedbg prompt in some latest Wine versions?

[Saulius Krasuckas]

On 11 Aug 2004, Vincent Béron wrote:
> Le mer 11/08/2004 à 04:50, Mike Hearn a écrit :
> > Saulius Krasuckas wrote:
> > > I need an advice on how to setup winedbg the right way or an explanation,
> > > whether this is a bug or an advanced feature.  TIA.
> >
> > Nope, it's a bug, something to do with STABS parsing I think. I have 
> > reported it once to Eric but I think I didn't have enough info to help him.

And what do you think, Mike, is he being very busy recently?  Would it be
OK to try to contact him directly?
> The original message had this line:
> fixme:dbghelp:elf_load_debug_info Unsupported Dwarf2 information
>
> So I suspect your Wine is compiled with Dwarf2 debug symbols rather than
> stabs+. Which gcc version was used?

How should I check that?  And gcc version is 3.2:

[s2@katleriai d3d8]$ gcc -v
Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2/specs
Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --host=i386-redhat-linux --with-system-zlib --enable-__cxa_atexit
Thread model: posix
gcc version 3.2 20020903 (Red Hat Linux 8.0 3.2-7)