http://bugs.winehq.com/show_bug.cgi?id=395
fgouget(a)codeweavers.com changed:
What |Removed |Added
----------------------------------------------------------------------------
BugsThisDependsOn| |836
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://bugs.winehq.com/show_bug.cgi?id=395>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://bugs.winehq.com/show_bug.cgi?id=836
Summary: Speed up PDB support
Product: Wine
Version: CVS
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: wine-debug
AssignedTo: wine-bugs(a)winehq.com
ReportedBy: fgouget(a)codeweavers.com
PDB files contain 'hashtables' that make accessing symbol information very fast.
The problem is that winedbg does not support these hashtables. Because of this,
loading debug information from PDB files is very slow. So slow that it can cause
critical sections to time out (minutes). This performance issue is a problem for
people porting their own programs to Wine.
(People using the PDB files that are shipped with Microsoft's development SDK
escape this problem because these are stripped down)
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://bugs.winehq.com/show_bug.cgi?id=836>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://bugs.winehq.com/show_bug.cgi?id=455
fgouget(a)codeweavers.com changed:
What |Removed |Added
----------------------------------------------------------------------------
BugsThisDependsOn| |835
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://bugs.winehq.com/show_bug.cgi?id=455>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://bugs.winehq.com/show_bug.cgi?id=835
Summary: Add support for the new PDB format
Product: Wine
Version: CVS
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: wine-debug
AssignedTo: wine-bugs(a)winehq.com
ReportedBy: fgouget(a)codeweavers.com
(from WineConf) This format has been recently added, it is also called 'MSF 7.0'
and does not work with winedbg's current PDB code.
Supporting this new format would be useful to people trying to port their own
applications to Wine (since they obviously have the debug information). Again
the workaround is to instruct the compiler to use the old debug format but this
may not be possible when working with third party libraries.
Support would also be useful if this format is used to ship the debug
information for libraries that come with Windows 2000 or Windows XP.
However, we have yet to find an example of a PDB file in this format. If someone
does find such PDB files, please attach a small sample to this bug (source
file+.exe+.pdb)
Are the PDB files shipped with the MS development SDK in the new XP format?
Here is a related post on wine-devel:
* 2002/05/30 - Tijs van Bakel - Debug information
http://www.winehq.com/hypermail/wine-users/2000/11/0573.html
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://bugs.winehq.com/show_bug.cgi?id=835>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://bugs.winehq.com/show_bug.cgi?id=834
Summary: Add DWARF2 support
Product: Wine
Version: CVS
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: wine-debug
AssignedTo: wine-bugs(a)winehq.com
ReportedBy: fgouget(a)codeweavers.com
gcc 3.1 now uses the DWARF2 format for storing debug information. So if Wine or
a Winelib application is compiled with gcc 3, one must either explicitly tell
gcc to use the old debug format, or teach winedbg how to read the new format (or
not debug). Obviously, the only viable long term option is for winedbg to
support the new format.
Documentation about the DWARF2 format can be found there:
http://www.eagercon.com/dwarf/dwarf2std.htm
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://bugs.winehq.com/show_bug.cgi?id=834>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://bugs.winehq.com/show_bug.cgi?id=395
fgouget(a)codeweavers.com changed:
What |Removed |Added
----------------------------------------------------------------------------
BugsThisDependsOn| |833
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://bugs.winehq.com/show_bug.cgi?id=395>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://bugs.winehq.com/show_bug.cgi?id=833
Summary: Add support for inferior function calls
Product: Wine
Version: CVS
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: wine-debug
AssignedTo: wine-bugs(a)winehq.com
ReportedBy: fgouget(a)codeweavers.com
This would fall into the winedbg enhancement category. Here is a description of
what 'Inferior function calls' are by Ulrich Weigand:
'Inferior' in gdb speak is simply that program that is being debugged. An
'inferior function call' is the option to call a function inside the debuggee
while it is stopped inside the debugger. E.g. in gdb you can say 'call
some_func (args)' and the effect of this is that gdb creates a new, temporary
stack frame on the debuggee stack that is suitable to execute 'some_func' with
the given arguments, and then lets the debuggee run until it returns from that
function.
This is very useful to simplify debugging, e.g. if you have complex data
structures that are awkward to view with the regular debugger commands, you can
write a 'dump' function in your program, and call this function via inferior
call from the debugger whenever you want to inspect that data structure.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://bugs.winehq.com/show_bug.cgi?id=833>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://bugs.winehq.com/show_bug.cgi?id=831
------- Additional Comments From tony_lambregts(a)telusplanet.net 2002-06-29 23:37 -------
Created an attachment (id=195)
Patch for consideration
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://bugs.winehq.com/show_bug.cgi?id=831>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://bugs.winehq.com/show_bug.cgi?id=831
------- Additional Comments From fgouget(a)codeweavers.com 2002-06-29 23:29 -------
The WineDbg Command Reference sounds good. I would say either in the Misc
section (2.6.1) or in the 'Information on Wine's internals' (2.6.8) (with a
slight preference for the latter).
Adding a pointer to it in the debug logging section sounds good too.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://bugs.winehq.com/show_bug.cgi?id=831>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://bugs.winehq.com/show_bug.cgi?id=831
------- Additional Comments From tony_lambregts(a)telusplanet.net 2002-06-29 23:14 -------
I've looked at the documentation/debugger.sgml and I was wondering where to put
this. Do we want it right at the end of the WineDbg Command Reference?
http://www.winehq.org/Docs/wine-devel/dbg-commands.shtml
I guess it would be a good idea to put a blurb after the note about this right
at the begining of the debug logging section of documentation/debuging.sgml
http://www.winehq.org/Docs/wine-devel/debugging.shtml
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://bugs.winehq.com/show_bug.cgi?id=831>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://bugs.winehq.com/show_bug.cgi?id=395
fgouget(a)codeweavers.com changed:
What |Removed |Added
----------------------------------------------------------------------------
BugsThisDependsOn| |832
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://bugs.winehq.com/show_bug.cgi?id=395>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://bugs.winehq.com/show_bug.cgi?id=455
fgouget(a)codeweavers.com changed:
What |Removed |Added
----------------------------------------------------------------------------
BugsThisDependsOn| |829
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://bugs.winehq.com/show_bug.cgi?id=455>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://bugs.winehq.com/show_bug.cgi?id=831
Summary: Document the new trace-related winedbg commands
Product: Wine
Version: CVS
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: wine-documentation
AssignedTo: wine-bugs(a)winehq.com
ReportedBy: fgouget(a)codeweavers.com
(I was bout to enter a bug for this but it's been implemented already ;-)
It is now possible to enable/disable traces from the debugger interface.
-> update the documentation
See the following URL for more information:
http://www.winehq.com/hypermail/wine-devel/2002/05/0818.html
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://bugs.winehq.com/show_bug.cgi?id=831>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://bugs.winehq.com/show_bug.cgi?id=829
apa3a(a)yahoo.com changed:
What |Removed |Added
----------------------------------------------------------------------------
AssignedTo|wine-bugs(a)winehq.com |lionel.ulmer(a)free.fr
------- Additional Comments From apa3a(a)yahoo.com 2002-06-28 14:57 -------
Forwarding to Lionel.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://bugs.winehq.com/show_bug.cgi?id=829>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://bugs.winehq.com/show_bug.cgi?id=829
Summary: DIB_DirectDrawSurface_Blt does not properly support
DDBLT_WAIT
Product: Wine
Version: CVS
Platform: PC
OS/Version: All
Status: NEW
Severity: normal
Priority: P2
Component: wine-directx
AssignedTo: wine-bugs(a)winehq.com
ReportedBy: tony_lambregts(a)telusplanet.net
After playing around with SimCity 3000 some more I found that
DIB_DirectDrawSurface_Blt does not properly support DDBLT_WAIT. What wine
currently does is ignore the flag completely which in most cases is ok. The
problem shows up in SimCity when you click on the top half of the playing surface.
Because DDBLT_WAIT is not supported it makes a compleate mess of the screen.
By doing some serious debuging and a little searching of MSDN I found out what
the program expects to happen. All calls with the DDBLT_WAIT flag set are
supposed to be stored untill DIB_DirectDrawSurface_Blt is called without the
flag set. From what I can tell these requests should be processed in the reverse
order that they were submitted.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://bugs.winehq.com/show_bug.cgi?id=829>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://bugs.winehq.com/show_bug.cgi?id=825
------- Additional Comments From apa3a(a)yahoo.com 2002-06-27 13:33 -------
Jason, I wonder if you can reproduce the issue with even smaller test case -
when the dialog has only "Cancel" button.
BTW, <Esc> button works - it dismisses the dialog.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://bugs.winehq.com/show_bug.cgi?id=825>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://bugs.winehq.com/show_bug.cgi?id=825
apa3a(a)yahoo.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|Launched window treated as |Window in modal mode does
|child window |not receive mouse and
| |keyboard input
------- Additional Comments From apa3a(a)yahoo.com 2002-06-27 13:28 -------
It looks like the problem is even bigger - the modal dialog can't be accessed
with mouse, moved, does not receive keyboard input.
This bug may affect many VB applications
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://bugs.winehq.com/show_bug.cgi?id=825>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://bugs.winehq.com/show_bug.cgi?id=825
------- Additional Comments From us(a)the-edmeades.demon.co.uk 2002-06-27 12:21 -------
Testcase uploaded
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://bugs.winehq.com/show_bug.cgi?id=825>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Done... Dont know why it didnt work though!
-----Original Message-----
From: wine-bugs(a)winehq.com [mailto:wine-bugs@winehq.com]
Sent: 27 June 2002 17:37
To: us(a)the-edmeades.demon.co.uk
Subject: [Bug 825] - Launched window treated as child window
http://bugs.winehq.com/show_bug.cgi?id=825
------- Additional Comments From apa3a(a)yahoo.com 2002-06-27 11:36 -------
Jason, could you attach the archive directly to the bug report?
I can't download it.
Use hyperlink "Create a new attachment".
Thank you
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://bugs.winehq.com/show_bug.cgi?id=825>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://bugs.winehq.com/show_bug.cgi?id=780
apa3a(a)yahoo.com changed:
What |Removed |Added
----------------------------------------------------------------------------
AssignedTo|wine-bugs(a)winehq.com |pouech(a)winehq.com
Platform| |All
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://bugs.winehq.com/show_bug.cgi?id=780>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://bugs.winehq.com/show_bug.cgi?id=825
------- Additional Comments From us(a)the-edmeades.demon.co.uk 2002-06-27 12:16 -------
Created an attachment (id=191)
(720Kb testcase zipped)
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://bugs.winehq.com/show_bug.cgi?id=825>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://bugs.winehq.com/show_bug.cgi?id=657
apa3a(a)yahoo.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Platform| |All
Resolution| |WONTFIX
------- Additional Comments From apa3a(a)yahoo.com 2002-06-27 12:15 -------
No use of this bug.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://bugs.winehq.com/show_bug.cgi?id=657>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://bugs.winehq.com/show_bug.cgi?id=825
------- Additional Comments From apa3a(a)yahoo.com 2002-06-27 11:36 -------
Jason, could you attach the archive directly to the bug report?
I can't download it.
Use hyperlink "Create a new attachment".
Thank you
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://bugs.winehq.com/show_bug.cgi?id=825>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://bugs.winehq.com/show_bug.cgi?id=827
apa3a(a)yahoo.com changed:
What |Removed |Added
----------------------------------------------------------------------------
AssignedTo|wine-bugs(a)winehq.com |mike_mccormack(a)start.com.au
------- Additional Comments From apa3a(a)yahoo.com 2002-06-27 10:26 -------
Mike, could you look at this issue?
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://bugs.winehq.com/show_bug.cgi?id=827>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.