WineDBG / dbghelp symbol problem

[Eric Pouech]

Roderick Colenbrander wrote:

>I have attached a tarball containing two logs one in case it works (log.works) 
>and one in which it fails (log.fails). When it worked wine was installed 
>in /usr/local and in the other case in /emul/ia32-linux/usr.
>
>In the working case I executed 'WINEDEBUG=+dbghelp winedbg notepad' and piped 
>the output to a log and directly killed it. You'll notice the first line of 
>winedbg in it.
>
>The second time I did the same but because wine wasn't in the path yet I 
>did 'WINEDEBUG=+dbghelp /emu/ia32-linux/usr/bin/wine winedbg notepad'. In 
>previous cases I had symlinks to wine/wineserver in the path and at that 
>moment the same problem appeared
>
>Roderick
>
>On Thursday 24 August 2006 18:55, Eric Pouech wrote:
>  
>
>>Eric Pouech wrote:
>>    
>>
>>>Dbghelp looks for the ELF module in the PATH and LD_LIBRARY_PATH
>>>environment
>>>variables, while the internal loader relies on WINEDLLPATH and the
>>>default DLL dir (or the build one). You could work around this by
>>>setting one of those variables.
>>>Dbghelp needs to be updated to follow the loader's rules from libwine
>>>(I'll do it later on this week)
>>>A+
>>>      
>>>
>>as a matter of fact, we already take care of the WINEDLLPATH in dbghelp
>>so the issue is somewhere else
>>could you send me the +dbghelp trace in both cases (when it works and
>>when it doesn't)
>>TIA
>>    
>>
Hi Roderick

thanks for the logs
why isn't /emul/ia32-linux/usr/bin/ in your PATH environment variable ?
that should fix it (and I don't see a simple way of guessing the exec 
path from the debugger)
A+