[Bug 744] Changed - Cyclic "unhandled exception" error
wine-bugs at winehq.com
wine-bugs at winehq.com
Thu May 30 14:51:58 CDT 2002
http://bugs.winehq.com/show_bug.cgi?id=744
*** shadow/744 Thu May 30 07:20:33 2002
--- shadow/744.tmp.4066 Thu May 30 14:51:57 2002
***************
*** 59,61 ****
--- 59,129 ----
------- Additional Comments From apa3a at yahoo.com 2002-05-30 07:20 -------
One more - what does debugger say?
If the debugger is not configured to start see documentation how to configure it.
+
+ ------- Additional Comments From apa3a at yahoo.com 2002-05-30 14:51 -------
+ Pavel, please in future post your comments to the bug description, they will be
+ forwarded to the corresponding list
+
+ **********************************************
+ | * does the problem happen when you try to run any application with
+ wine or for
+ | some specific application?
+
+ It has happened for all applications I have already tried to run.
+
+ It has appeared after the transition to KDE 3.0 (or maybe to some
+ subsequent libraries); before, it was all OK! Except that the Truetype fonts
+ didn't work; I used to get a message "Upgrade to Freetype 2.x.x" or
+ somewhat such and the Truetype fonts were replaced by Linux bitmap ones.
+ (I have RedHat 7.1, repeating for clarity.)
+
+ | * does it happen if you just run "wine --version" ?
+
+ I don't now, I'm running Windows now, I must look under Linux, please
+ be patient.
+
+ | + One more - what does debugger say?
+ | + If the debugger is not configured to start see documentation how to
+ configure it.
+
+ Oh, I think the debugger IS configured to run (is it the default
+ setting?) but I think it starts n-times after the error happens but it
+ doesn't appear at all (yes, I have already seen the black window with huge
+ amount of error messages but it was on KDE2 -- was this the debugger? I
+ think it was). I think I have found the debugger in the task list (a lot
+ of tasks at once, it had been invoked repeatedly) but I'm not sure.
+ In this case - please be also patient.
+
+ + * is win_c real Windows directory or a fake one? If you use real
+ Windows
+ + directory, what version of Windows? Did you import Windows registry?
+
+ So, what's win_c? I have the connection point to the REAL Windows
+ partition mapped to /win/salvodralva, and then, I have a symlink to this
+ directory called /win_c .
+ I have Windows ME on this partition.
+ But -- how do I import the windows registry :-? :-s This could be the
+ case!
+ But I have run winesetuptk and configured out all the options, AFAIK.
+ Does it suffice?
+
+ Thanks in advance (uhh! not "in advice"!)
+ **********************************************
+
+ **********************************************
+ Ok, i get the Wine version without problems.
+ **********************************************
+
+ **********************************************
+ All that I have already written is true:
+
+ 1) The debugger says nothing. It just doesn't appear, even though I
+ write e.
+ g. winedbg c:\\windows\\sol.exe or c:\\windows\\freecell.exe.
+ 2) Wine only writes it starts the debugger, and it truly starts. I have
+ as
+ much debugger tasks in the task list as I want and allow :-) The number
+ of
+ wine tasks is the same as the number of the debugger tasks.
+ But as I have said, I can't see any debugger window.
+ **********************************************
More information about the wine-bugs
mailing list