Help in debugging WINE using WINEDEBUG

Questions about Wine on Linux
Locked
fhmanas
Level 2
Level 2
Posts: 12
Joined: Wed Dec 03, 2008 3:14 am

Help in debugging WINE using WINEDEBUG

Post by fhmanas »

Hello, I have an old Powerbuilder 5 app that we have been using Wine for. The app has been working 100% with WINE for years with no dll overrides since Wine 1.4. Recently an error occurred in one of the modules in the app "Unresolvable external function link error", this means that it could not find the function. I know this works on a WinXP machine so it is not the code.

But here is the clincher, I tried to debug using WINEDEBUG=+relay wine app.exe &> debug.log, and the program works with no errors, and the expected output happens, so there is nothing in the log that will show the error. I am using this as a workaround, but it is slow to process probably because of all the debug calls. Anybody with WINEDEBUG experience help me get to the bottom of the problem.

Thanks.
User avatar
dimesio
Moderator
Moderator
Posts: 13367
Joined: Tue Mar 25, 2008 10:30 pm

Re: Help in debugging WINE using WINEDEBUG

Post by dimesio »

What Wine version are you using, and did the appearance of this error coincide with an upgrade to Wine? Have you tried reinstalling the app to a clean wineprefix under current Wine?

If your Wine version is not the latest development release, upgrade. If this is occurring in current Wine, was triggered by a Wine upgrade, and a clean wineprefix doesn't help, then you should run a regression test and file a bug.

If the problem wasn't caused by an upgrade to Wine, what else changed on the system?
fhmanas
Level 2
Level 2
Posts: 12
Joined: Wed Dec 03, 2008 3:14 am

Re: Help in debugging WINE using WINEDEBUG

Post by fhmanas »

Am using latest Wine 1.7.44. Will try to go back to older wine version.
User avatar
dimesio
Moderator
Moderator
Posts: 13367
Joined: Tue Mar 25, 2008 10:30 pm

Re: Help in debugging WINE using WINEDEBUG

Post by dimesio »

If downgrading fixes it that will tell you it's a regression, but if that's the case, you will still need to test in the current development release, 1.7.46. It could be something that's already been fixed.
Locked