http://bugs.winehq.org/show_bug.cgi?id=13275
--- Comment #18 from Michael H. Warfield mhw@wittsend.com 2009-04-25 16:46:38 --- I saw that Wine 1.1.20 was out so I jumped back in to try this again. Some changes in Wine behavior but the failures remain. I have finally managed to get rpmbuild/rpm to build and install unstripped binaries. So all the symbols are in the binaries and the debug rpm's are installed. So, at this point, I don't know what else to do. I'm attaching three more logs from three runs. If you feel they are STILL missing something (I still see "Deferred" in those backtraces) I need to know specifically what I need to change or what I need to do to correct it. I've been over the debugging pages (I think) and I don't see what's missing.
IAC...
Removed my .wine directory and reran the Remedy user install. Installshield seems to do it's job and installs aruser and crystal reports and all that jazz.
Ran aruser. After logging in, Wine prompts me as before asking about Gecko. First run, I tell Wine to install gecko. It downloads and installs it and then Wine gives me a new dialog box that wasn't there with 1.1.19:
=== The program aruser.exe has encountered a serious problem and needs to close. We are sorry for the inconvenience.
This can be caused by a problem in the program or a deficiency in Wine. You may want to check http://appdb.winehq.org for tips about running this application.
If this problem is not present under Windows and has not been reported yet, you can report it at http://bugs.winehq.org.
[Close] ===
Ok... Improved error handling and exception handling. I like. But it blew up in the same spot. That will be the first backtrace.
Removed the .wine directory and reinstalled again.
Running Remedy this time I hit "Cancel" on the "Install Gecko" prompt. Now I get a screen and I see a partial message (which was there before, BTW) that looks like it's trying to tell me that rendering is disabled and an APERR about not being able to generate an app list (same as before). Ok the dialog box and kill the sub-window within Remedy and I get the above error message again (this is were it blew up before again). This will be the "no-gecko" log / backtrace attached.
Running Remedy again (did not reinstall this time), this time I did not try to kill the sub-window within remedy after the OK on the APERR dialog but went to open a form/object and do a search on it. When I hit search, I'm back to the third point where it blows and, again, I get the new error dialig box above. That will be the "search" log/backtrace attached.
I can now build and patch and install unstripped binaries and can run all the tests you like. I just need to know what you would like me to try next.