I've got an application that is crashing in Wine and I am trying to debug it.
However, I am runnign into a problem before I even get started...
When I go into the debugger (winedbg) it complains that it cannot find "debug information" in any of the 32bit DLL's. Indeed, from within the debugger I cannot find nor break at any of the DLL functions... which is quite a drag.
I'm sure there is some simple solution to this relted to a problem with my setup or the way I am running the debugger, but I can't figure it out.
I have tried recompiling and reinstalling all of wine with the -g compiler option (seems reasonable, I suppose) but that doesn't solve it. I've told wine/configure to "--enable-debug", to no avail. I don;t know what I'm missing and I can't find any useful suggestions in any of the documentation or FAQ's (not that thtere is nothing useful... just I haven't yet found it, though I have looked)
Any hints/help would be most appreciated.
sample error message: No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\USER32.DLL' (0x40690000)
sample error message: No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\USER32.DLL' (0x40690000)
From thread 'Need help debugging' Jan 15 with aswer from Mike Hearn:
- How to compile debug information into the 32bit DLL's so I don't get 'No debug information in 32bit DLL' anymore and maybe some better info? I tried 'configure --enable-debug && make depend && make && su -c "make install"' to no avail.
They have debugging info in, but unfortunately there has been breakage in the debugger recently which has not yet been fixed in CVS. This is very bad EricP sent a patch here which works great for me and fixed all my debugger problems, try looking in the archives for Jan and December looking for it (it was sent to wine-devel not wine-patches iirc).
For now try setting WINELOADER to the path to your actual wine binary (wine-pthread)
Eric, could you please submit that patch? Even if it's not correct, having the debuggers out of action like this is causing big problems.
Eric, could you please submit that patch? Even if it's not correct, having the debuggers out of action like this is causing big problems.
as I already wrote, the patch I sent to wine-devel is: 1/ a dirty hack 2/ doesn't address all the issues 3/ a wrong solution to the real problem For the time being, setting WINELOADER to the wine exec is the best solution.
A+
On Sat, 24 Jan 2004 07:18:04 +0100, Eric Pouech wrote:
as I already wrote, the patch I sent to wine-devel is: 1/ a dirty hack 2/ doesn't address all the issues 3/ a wrong solution to the real problem
Yes, sorry, I remember but the guy was quoting an earlier email of mine, I wasn't repeating the request ;)
thanks -mike
-
Andrew L. Bereson -
Eric Pouech -
Frank Schruefer -
Mike Hearn