wine-bugs June 2002

wine-bugs@winehq.org

9 participants
425 discussions

[Bug 836] New: - Speed up PDB support
by wine-bugs＠winehq.com 30 Jun '02

30 Jun '02

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.

1 0

[Bug 455] - FIXMEs
by wine-bugs＠winehq.com 30 Jun '02

30 Jun '02

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.

1 0

[Bug 835] New: - Add support for the new PDB format
by wine-bugs＠winehq.com 30 Jun '02

30 Jun '02

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.

1 0

[Bug 834] New: - Add DWARF2 support
by wine-bugs＠winehq.com 30 Jun '02

30 Jun '02

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.

1 0

[Bug 395] - Wine Tasklist Meta Bug
by wine-bugs＠winehq.com 30 Jun '02

30 Jun '02

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.

1 0

[Bug 833] New: - Add support for inferior function calls
by wine-bugs＠winehq.com 30 Jun '02

30 Jun '02

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.

1 0

[Bug 831] - Document the new trace-related winedbg commands
by wine-bugs＠winehq.com 30 Jun '02

30 Jun '02

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.

1 0

[Bug 831] - Document the new trace-related winedbg commands
by wine-bugs＠winehq.com 30 Jun '02

30 Jun '02

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.

1 0

[Bug 831] - Document the new trace-related winedbg commands
by wine-bugs＠winehq.com 30 Jun '02

30 Jun '02

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.

1 0

[Bug 395] - Wine Tasklist Meta Bug
by wine-bugs＠winehq.com 30 Jun '02

30 Jun '02

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.

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-bugs June 2002