http://bugs.winehq.com/show_bug.cgi?id=650
*** shadow/650 Fri May 10 11:57:42 2002
--- shadow/650.tmp.31817 Fri May 10 12:56:05 2002
***************
*** 1,10 ****
+============================================================================+
! | Processor related error messages when launching winedbg |
+----------------------------------------------------------------------------+
| Bug #: 650 Product: Wine |
! | Status: UNCONFIRMED Version: unspecified |
| Resolution: Platform: |
! | Severity: normal OS/Version: All |
| Priority: P1 Component: wine-debug |
+----------------------------------------------------------------------------+
| Assigned To: wine-bugs(a)winehq.com |
--- 1,10 ----
+============================================================================+
! | error messages when loading debugging information from libstdc++ on RedHat |
+----------------------------------------------------------------------------+
| Bug #: 650 Product: Wine |
! | Status: NEW Version: unspecified |
| Resolution: Platform: |
! | Severity: minor OS/Version: All |
| Priority: P1 Component: wine-debug |
+----------------------------------------------------------------------------+
| Assigned To: wine-bugs(a)winehq.com |
***************
*** 104,106 ****
--- 104,111 ----
you're right, libGL isn't the problem because I load Quake3 whithout problem.
no speed loss even at 1024x768 !!
+
+ ------- Additional Comments From apa3a(a)yahoo.com 2002-05-10 12:56 -------
+ Confirm per Sylvain's comments.
+ I can't reproduce the issue - the library is not loaded when I try to load
+ console with debugger. Probably this is RH 7.3-specific issue.
\ No newline at end of file
http://bugs.winehq.com/show_bug.cgi?id=650
*** shadow/650 Fri May 10 09:21:26 2002
--- shadow/650.tmp.27404 Fri May 10 11:57:42 2002
***************
*** 91,93 ****
--- 91,106 ----
I suspect that winedbg have problems with C++ debugging information or format of
this information is different in your new distribution, so try application,
writted in C++ or create one yourself.
+
+
+ ------- Additional Comments From spetreolle(a)yahoo.fr 2002-05-10 11:57 -------
+ I found another application that produces such output : wineconsole itself.
+ launching winedbg wineconsole being in wineconsole source directory reproduces
+ the problem. could i do some --debugmsg to where does it comes from ?
+
+ for info, the file you mentioned comes from the package libstdc++-2.96.110
+ provided by RedHat. But by the way, wineconsole isn't precisely a c++ application,
+ is it ?
+
+ you're right, libGL isn't the problem because I load Quake3 whithout problem.
+ no speed loss even at 1024x768 !!
\ No newline at end of file
http://bugs.winehq.com/show_bug.cgi?id=588
*** shadow/588 Tue Apr 30 13:55:00 2002
--- shadow/588.tmp.26534 Fri May 10 11:46:01 2002
***************
*** 24,26 ****
--- 24,34 ----
------- Additional Comments From apa3a(a)yahoo.com 2002-04-30 13:55 -------
James, could you describe how to reproduce the bug?
+
+ ------- Additional Comments From James(a)superbug.demon.co.uk 2002-05-10 11:46 -------
+ I can see this problem as well.
+ It happens with any Office 2000 programs.
+ Create a new Word document.
+ File->Save as
+ And when you try to save the file, it will not work, and the wine log displays: -
+ fixme:file:FindFirstChangeNotificationA this is not supported yet (non-trivial)
\ No newline at end of file
http://bugs.winehq.com/show_bug.cgi?id=650
*** shadow/650 Thu May 9 14:02:04 2002
--- shadow/650.tmp.16328 Fri May 10 09:21:26 2002
***************
*** 78,80 ****
--- 78,93 ----
and, yes, this is the same library everytime. /usr/lib/libGLcore.so.1 as I said
before.
+
+ ------- Additional Comments From apa3a(a)yahoo.com 2002-05-10 09:21 -------
+ It looks like the problem is with loading debugging information from the library
+ /usr/lib/libstdc++-libc6.2-2.so.3 and it is not related to the
+ /usr/lib/libGLcore.so.1 library, because the issue appears after the message
+ that /usr/lib/libGLcore.so.1 is loaded.
+ My telnet.exe (Windows NT) does not load neither library and I can't reproduce
+ the issue.
+ Can you find any other application, freely accessible which shows this problem?
+
+ I suspect that winedbg have problems with C++ debugging information or format of
+ this information is different in your new distribution, so try application,
+ writted in C++ or create one yourself.
http://bugs.winehq.com/show_bug.cgi?id=663
*** shadow/663 Fri May 10 03:29:17 2002
--- shadow/663.tmp.31964 Fri May 10 03:29:17 2002
***************
*** 0 ****
--- 1,25 ----
+ +============================================================================+
+ | Publisher stops reading keyboard and mouse input. |
+ +----------------------------------------------------------------------------+
+ | Bug #: 663 Product: Wine |
+ | Status: UNCONFIRMED Version: 20020411 |
+ | Resolution: Platform: |
+ | Severity: normal OS/Version: All |
+ | Priority: P1 Component: wine-binary |
+ +----------------------------------------------------------------------------+
+ | Assigned To: wine-bugs(a)winehq.com |
+ | Reported By: woolite(a)darkpact.com |
+ | CC list: Cc: |
+ +----------------------------------------------------------------------------+
+ | Milestone: TargetMilestone: --- |
+ | URL: |
+ +============================================================================+
+ | DESCRIPTION |
+ I'm using KDE 2.2.2 and I am trying to use MS Publisher 2000.
+ Here is the problem I am having.
+ In my ~/.wine/config file, I have Managed and Desktop disabled.
+ I load up Publisher, and it reads keyboard and mouse input as long as it's
+ maximized.
+ Once I resize the window (unmaximize) it stops reading keyboard presses and
+ mouse button presses. It does, however, still correctly give the screen
+ coordinates of the mouse when it is moved.
\ No newline at end of file
http://bugs.winehq.com/show_bug.cgi?id=662
*** shadow/662 Thu May 9 14:05:28 2002
--- shadow/662.tmp.8532 Thu May 9 22:44:51 2002
***************
*** 9,15 ****
+----------------------------------------------------------------------------+
| Assigned To: wine-bugs(a)winehq.com |
| Reported By: davidmccabe(a)mac.com |
- | CC list: Cc: |
+----------------------------------------------------------------------------+
| Milestone: TargetMilestone: --- |
| URL: |
--- 9,14 ----
***************
*** 21,23 ****
--- 20,33 ----
------- Additional Comments From davidmccabe(a)mac.com 2002-05-09 14:04 -------
*** Bug 661 has been marked as a duplicate of this bug. ***
+
+ ------- Additional Comments From tony_lambregts(a)telusplanet.net 2002-05-09 22:44 -------
+ OK not the right information to go on so...
+ You say it crashes on make. lets do this by hand so to speak.
+
+ ./configure
+ make depend
+ make 2>&1 | tee maketemp.log
+ tail maketemp.log 30 > make.log
+
+ attach the resulting make.log here.
http://bugs.winehq.com/show_bug.cgi?id=656
*** shadow/656 Tue May 7 17:10:18 2002
--- shadow/656.tmp.24609 Thu May 9 16:30:38 2002
***************
*** 41,43 ****
--- 41,72 ----
080e42d8:Ret kernel32.GlobalAlloc() retval=4037c4a6 ret=0040239b
Which means that one of those *Time*To*Time* functions are broken.
+
+ ------- Additional Comments From vberon(a)mecano.gme.usherb.ca 2002-05-09 16:30 -------
+ FileTimeToLocalFileTime takes a FILETIME (which is UTC) and converts it into
+ another FILETIME, this time in the current TZ.
+
+ FileTimeToSystemTime seems OK: both the input and the output are supposed to be
+ UTC, so no TZ conversion going on.
+
+ Now, the program takes a UTC time (from GetFileTime), transfers it to local (via
+ FileTimeToLocalFileTime), then takes that local time (at least the pointer
+ address seems to indicate that) and transforms it into a SYSTEMTIME (which is
+ supposed to be just another representation of a UTC time).
+
+ The problem seems to lie in the call to FileTimeToSystemTime: the program sends
+ an "illegal" time (local time) rather than a real file time (which is UTC).
+
+ I'll have to play a bit on a real Windows computer to try some stuff, and verify
+ what those 2 functions actually do on Windows.
+
+ I assume you're in CDT (-500 from UTC), which explains the 0500 difference in
+ the strings. Could you try again with a +0000 TZ? It might help to further
+ target the culprit...
+
+ Are there other calls you could try to trace, like the pointers from which the 2
+ strings are made of? It might help knowing what is the code path leading to one
+ and the other strings. Right now, my guess is that the first one (164848) is
+ constructed from the local time (pointer 0x40566650), and the second one
+ (214848) from a UTC time (pointer 0x40566648). The pointer 0x40566658 is just
+ another representation of 0x40566650.
\ No newline at end of file