May 2003 - Wine-Devel - list.winehq.org

Re: New metabugs

by hatky

Thanks Francois, Your response was the most educating for me... --- Francois Gouget <fgouget(a)free.fr> wrote: > On Fri, 2 May 2003, hatky wrote: > [...] > > > Anyway, don't let me slow you down. Just > remember that > > > bug tracking is a social issue, and you have to > pay attention > > > to how the other developers feel about it. > > I am not sure what they realy think yes I only got > 3 > > responces 2 of witch where positive :)... > > I guess I will have to wait for the next week to > start > > when codewaver will return to flame me (or not) :) > > This is Wine's bugzilla so you don't need to worry > about CodeWeavers > flaming you (or about the CodeWeavers' needs). > However, as Dan said, > beware of the Wine developpers ;-). I do not fear my own breed. > > I know I used meta-bugs in the past and we used them > too in our internal > CodeWeavers bugzilla database. But meta-bugs are not > very practical in > the long term and it is worth considering > alternatives. In particular: > > * Component field > Some developpers are specialized in a certain > aspect of Wine. Havnig > specialists is good, it's certainly more efficient > than having to learn > from scratch each time. So we need to provide a way > for specialists to > find bugs in their area of expertise. > The 'Component' field is one way to do so. Let's > say you're a > Direct3D specialist, you can find bugs in that area > by querying Bugzilla > for all bugs tagged with 'Component=wine-directx'. > > * keywords > Keywords are another way to tag and query bugs. > It's pretty flexible > and even lets you put multiple keywords on a bug. > For instance you can > find all the bugs related to conformance testing by > querying Bugzilla > for bugs that have the 'conformance' keyword. > Similarly you can look for > all bugs related to programs for which the source is > available by > searching for bugs with the 'source' keyword. > See http://bugs.winehq.com/describekeywords.cgi This is very intersting and I actually did not really know about keywords I seen them some where but I never seen this link and it does look like a good way for doing this kind of stuff, I just now know I can actully update this.... > > > > That being said, > > * Bugzilla queries don't appear to work. Newman do > you know what's up? > Is it a database performance issue? Bugzilla bug? I had this problem but I tought the bug was me since some simple querys did work and I have never used the search,,, > > * Direct3D and DirectSound are pertty different > areas. Maybe we should > split the wine-directx component into direct3d, > directdraw, directsound > and the generic directx. That would be a nice idea. > > * Maybe we need a 'wine-msvcrt' component. I know > there are people > interested in msvcrt but looking at the component > list I don't know > where such bugs would go. Or maybe we should be a > bit more general and > have a 'wine-libc' so that it includes crtdll and > potential future C++ > libraries, etc. No comment. > > * Maybe we should add more keywords. I'm not saying > we should do it, > but adding 'game' keyword would provide the same > functionality as the > current game meta-bug. If we go this way, I could > see another useful > keyword: 'installer' to identify all bugs related to > application > installers. But we have to be careful not to add > frivolous keywords. I am highly for doing this and for both the 'game' and 'installer' keywords and I can not actually think of more to add and thats rare in my case :). > > * One useful things that can be done now is to > inspect all new bugs to > make sure that: > - the component field is set correctly > - the download URL to the binary or source is > provided if applicable > (in case of doubt ask the reporter) > - all applicable keywords are set > That said, things seem to be already pretty much > in order (more so > for the component field than for keywords). I know mine sould be redone where keywords is concerned I will do it soon. > > * Maybe people don't know about the keywords, > components and Bugzilla > queries. Maybe they need to be publicized somewhat. A simple link somewhere would do it justice (a block would make it even cool). > > > -- > Francois Gouget fgouget(a)free.fr > http://fgouget.free.fr/ > A black hole is just God dividing > by zero. > Thanks a LOT Francois, Hatky. __________________________________ Do you Yahoo!? The New Yahoo! Search - Faster. Easier. Bingo. http://search.yahoo.com

May 3, 2003

Re: New metabugs

by Francois Gouget

On Fri, 2 May 2003, hatky wrote: [...] > > Anyway, don't let me slow you down. Just remember that > > bug tracking is a social issue, and you have to pay attention > > to how the other developers feel about it. > I am not sure what they realy think yes I only got 3 > responces 2 of witch where positive :)... > I guess I will have to wait for the next week to start > when codewaver will return to flame me (or not) :) This is Wine's bugzilla so you don't need to worry about CodeWeavers flaming you (or about the CodeWeavers' needs). However, as Dan said, beware of the Wine developpers ;-). I know I used meta-bugs in the past and we used them too in our internal CodeWeavers bugzilla database. But meta-bugs are not very practical in the long term and it is worth considering alternatives. In particular: * Component field Some developpers are specialized in a certain aspect of Wine. Havnig specialists is good, it's certainly more efficient than having to learn from scratch each time. So we need to provide a way for specialists to find bugs in their area of expertise. The 'Component' field is one way to do so. Let's say you're a Direct3D specialist, you can find bugs in that area by querying Bugzilla for all bugs tagged with 'Component=wine-directx'. * keywords Keywords are another way to tag and query bugs. It's pretty flexible and even lets you put multiple keywords on a bug. For instance you can find all the bugs related to conformance testing by querying Bugzilla for bugs that have the 'conformance' keyword. Similarly you can look for all bugs related to programs for which the source is available by searching for bugs with the 'source' keyword. See http://bugs.winehq.com/describekeywords.cgi That being said, * Bugzilla queries don't appear to work. Newman do you know what's up? Is it a database performance issue? Bugzilla bug? * Direct3D and DirectSound are pertty different areas. Maybe we should split the wine-directx component into direct3d, directdraw, directsound and the generic directx. * Maybe we need a 'wine-msvcrt' component. I know there are people interested in msvcrt but looking at the component list I don't know where such bugs would go. Or maybe we should be a bit more general and have a 'wine-libc' so that it includes crtdll and potential future C++ libraries, etc. * Maybe we should add more keywords. I'm not saying we should do it, but adding 'game' keyword would provide the same functionality as the current game meta-bug. If we go this way, I could see another useful keyword: 'installer' to identify all bugs related to application installers. But we have to be careful not to add frivolous keywords. * One useful things that can be done now is to inspect all new bugs to make sure that: - the component field is set correctly - the download URL to the binary or source is provided if applicable (in case of doubt ask the reporter) - all applicable keywords are set That said, things seem to be already pretty much in order (more so for the component field than for keywords). * Maybe people don't know about the keywords, components and Bugzilla queries. Maybe they need to be publicized somewhat. -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ A black hole is just God dividing by zero.

May 2, 2003

Re: Volunteers needed - windows API db script ready

by Francois Gouget

On Fri, 2 May 2003, Dave Miller wrote: [...] > The script is available at http://home.ptd.net/~compsol. Please make sure > you get createdb.pl. There is another script, createwinedb.pl which will > ONLY parse the wine spec files. > > To run this you will need winedump, perl, and access to your windows > directory from within Linux. I mounted the Win95 filesystem using smbfs and all the files came out in uppercase. That's when I noticed that the script had trouble with uppercase filenames. I attached a patch below that should improve things. I also noticed it does not give any warning if winedump is not in the path. It might be nice to do so. > The cleaner the windows install the > better. We don't want to clutter the database with info from dlls > not provided with windows. Usage is as follows: > > createdb.pl -d -p <path to windows dir> -o <winver (ex. win98) I ran it on a clean Win95 system which should be pretty clean (never been used, nothing installed on it). I ran the script as follows: ./createdb.pl -d -p /home/fgouget/wine/apidb/mnt/WINDOWS -o win95-4.00.950 (the script adds .ref automatically) And I sent you the resulting file in a separate email. --- createdb.pl.orig 2003-05-01 21:43:20.000000000 -0700 +++ createdb.pl 2003-05-02 14:46:22.000000000 -0700 @@ -80,7 +80,7 @@ push @dir,$dirs."/".$_; } else { - push (@dlllist,"$_ $dirs\n") if /\.dll$/; + push (@dlllist,"$_ $dirs\n") if /\.dll$/i; } } @dlllist = sort @dlllist; @@ -126,10 +126,10 @@ chomp($_); s/^\s*(.*?)\s*$/$1/; ($a,$b,$c,$d,$e)=split(/\s+/,$_); - $fullname = $c if ($a =~ /Contents/ & $c =~ /.dll|.DLL/); + $fullname = $c if ($a =~ /Contents/ & $c =~ /.dll/i); ($path,$name2)=split(/^.*\//,$fullname); - if ($c =~ /.dll|.DLL/ & $a =~ /Content/) { + if ($c =~ /.dll/i & $a =~ /Content/) { ($name,$junk)=split(/\./,$name2); } @@ -187,7 +187,7 @@ chomp($_); s/^\s*(.*?)\s*$/$1/; ($a,$b,$c,$d,$e)=split(/\s+/,$_); - $fullname = $c if ($c =~ /.dll$/ & $a =~ /Dump/); + $fullname = $c if ($c =~ /.dll$/i & $a =~ /Dump/); next LINE if (length $a == 0 | length $a == 2 & length $b == 2 & length $c == 2 & length $d == 2); next LINE if ($b =~ /^[0-9]+$/ & length $c == 0 | $a =~ /TimeDateStamp/); if ($a eq "Name:") { -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ The software said it requires Win95 or better, so I installed Linux.

May 2, 2003

Re: Small DSound fix...

by Robert Reif

This patch is all wrong. It makes no sense to pass a software class id to a function that only accepts hardware ids. The real bug is in the class factory. 0 should be passed rather than the class id. Look at the capture part a few lines below it. Passing 0 or NULL will select the default device. I can't generate a patch now but the trivial fix is to pass 0 rather than the class id in the class factory. Bob.

May 2, 2003

iexplore 5.5.

by KK singh

hi, I have tried ie5 installation on wine and failed, I am trying to find workarounds for not using IE. Given a windows executable, can i detect which IE dependent calls it is making ? Or exactly what calls both direct api's and COM Interfaces are successful if IE5.5 is installed and fails otherwise. any pointers shall be helpful to me... Regards -kks PS: thanx for the earlier replies. __________________________________ Do you Yahoo!? The New Yahoo! Search - Faster. Easier. Bingo. http://search.yahoo.com

May 2, 2003

Re: A little Xlib adventure

by Mike Hearn

Any problems with this patch Alexandre? It's missed 3 rounds of commits now. thanks -mike On Tue, 2003-04-29 at 13:59, Mike Hearn wrote: > Got to start somewhere. This patch adds support for the netWM ping > protocol, which lets window managers like metacity present a nice "This > app is not responding, kill it?" window when the program freezes. This > unfortunately happens all too often with IE in particular, and while us > developers can see (and understand) critical section timeout messages, > people running from the menu or desktop icons cannot. > > I haven't bothered sending a message to the window (WM_NULL) because if > the program stops responding, it'll stop processing X messages as well. > If you want to test it out, just put an infinite loop in a test app then > try and close it. > > Tested with metacity from gnome2.2 - may work with latest KWin, if it > doesn't then file a bug in KDE bugzilla. > > ChangeLog: > Support _NET_WM_PING protocol so the WM can detect freezes

May 2, 2003

Re: Small DSound fix...

by Christian Costa

Vincent Béron wrote: > Christian Costa a écrit: > >> Lionel Ulmer wrote: >> >>> Hi all, >>> >>> This makes games which do NOT enumerate the sound devices and go >>> through the >>> ClassFactory work. >>> >>> It has also some miscellaneous tracing fixes. >>> >>> Changelog: >>> - misc. tracing fixes >>> - handle IID_IDirectSound(8) as the default sound driver >>> >> >> A ce que je vois ton patch remplace le mien (qui n'a pas ete accepte >> d'ailleurs)... >> >> P'tite curiosite.. :-) : >> Mais qu'est ce que ces foutues IIDs viennent faire a la place des >> GUID des devices ? >> C'est une bidouille ou bien DirectSoundCreate les acceptent vraiment ? > > > Envoyé en français par erreur à la liste probablement Christian? :) > > Whole translation for non-french speaking people here: > > I see that your patch replaces mine (which hasn't been accepted yet)... > > Out of curiosity... :-) : > What all those bloody IIDs do instead of devices' GUID? > Is it a gimmick or does DirectSoundCreate really accepts them? > > (me) > Sent to the list by mistake in French Christian? :) > > Vincent > > Arghhh! I should better go to sleep! Really sorry... :-( But well! Thanks for the translation though. :-) Christian

May 2, 2003

Re: Volunteers needed - windows API db script ready

by Dimitrie O. Paun

On Fri, 2 May 2003, Dave Miller wrote: > createdb.pl -d -p <path to windows dir> -o <winver (ex. win98) Please name the output file like so: <os-name>-<os-version>.ref, where: <os-name>: is one of: win9x, winnt, win2k, winxp <os-version: should be the version reported by Windows, such as 5.00.2195SP3. This is reported in the My Computer/Properties dialog. For the computer where I'm working from right now, the filename will be: win2k-5.00.2195SP3 This is important info, without it we may not be able to use the info you send in. -- Dimi.

May 2, 2003

Re: Volunteers needed - windows API db script ready

by Dave Miller

The script I am looking for people to run, createdb.pl will scan the actual windows dlls, run winedump on them, and nicely format the output. The other script does scan the wine spec files. It formats output in the same way but is for use with wine only. ----- Original Message ----- From: "Gerhard W. Gruber" <sparhawk(a)gmx.at> To: <wine-devel(a)winehq.com> Sent: Friday, May 02, 2003 5:04 PM Subject: Re: Volunteers needed - windows API db script ready > On Fri, 2 May 2003 01:57:36 -0400 (EDT), Dave Miller <compsol(a)ptdprolog.net> > wrote: > > >The script which dumps dll imports and exports now seems to parse > >everything correctly and organize it nicely in a text file. We need the > >script run against various windows versions. The output can be sent > >directly to me, but please verify I do not already have the data for that > >particular version of windows. I don't need 10 copies of win2k SP3 for > >example. :) > > I'm not sure if I understand you script crorrectly. Does the script scan > actual DLL binaries for import/export info and converts it to a spec file? Or > does this script only take a spec file? > > -- > Gerhard Gruber > > Für jedes menschliche Problem gibt es immer eine einfache Lösung: > Klar, einleuchtend und falsch. (Henry Louis Mencken) > > >

May 2, 2003

Re: Stub for SetSystemTimeAdjustment

by Dimitrie O. Paun

On Fri, 2 May 2003, Lionel Ulmer wrote: > Try the attached patch, it will work MUCH better :-) Please add a FIXME with a stub message, so we don't forget about it... -- Dimi.

May 2, 2003