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 probl
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 ...
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 wi
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
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 t
When using CVS version of Wine I cannot get much debug:
[EMAIL PROTECTED] 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 GetDriveT
