http://bugs.winehq.com/show_bug.cgi?id=901
------- Additional Comments From tony_lambregts(a)telusplanet.net 2002-07-21 20:47 -------
Sorry that sould probably have been --debugmsg +midi or +midi,+wave
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=901>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://bugs.winehq.com/show_bug.cgi?id=901
------- Additional Comments From tony_lambregts(a)telusplanet.net 2002-07-21 20:08 -------
What is the program that gives this error. Is there a downloadable version that
someone could test with? If not a trace (--debugmsg +wave) that shows the
problem would be a step in the right direction.
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=901>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://bugs.winehq.com/show_bug.cgi?id=904
fgouget(a)codeweavers.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |tasklist
------- Additional Comments From fgouget(a)codeweavers.com 2002-07-21 16:23 -------
A couple notes about the above patch: I started implementing the changes
described in the original comment. The implementation is far from complete or
clean but may be used as a valuable starting point and illustration of the changes.
You will note that the debugger also uses threads a lot, and it will need a lot
more fixing before it works. The above patch just makes sure it still compiles.
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=904>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://bugs.winehq.com/show_bug.cgi?id=904
------- Additional Comments From fgouget(a)codeweavers.com 2002-07-21 16:20 -------
Created an attachment (id=237)
Incomplete&untested fix
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=904>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://bugs.winehq.com/show_bug.cgi?id=904
Summary: Solaris: Add threading support
Product: Wine
Version: CVS
Platform: PC
OS/Version: Solaris
Status: NEW
Severity: normal
Priority: P2
Component: wine-ports
AssignedTo: wine-bugs(a)winehq.com
ReportedBy: fgouget(a)codeweavers.com
Threading does not work correctly on Solaris (an issue for both x86 and Sparc
platforms). The reason is that Linux (and FreeBSD) treat threads differently
from Solaris.
* on Linux a process can contain multiple threads and each thread gets a unique
system-wide identifier which is confusingly called a pid (process id). It can be
argued that Linux does not in fact have the notion of what a process is: there
is no object that represents the process that contains all these threads. So you
cannot kill a process, you can only kill its individual threads. This is because
you can only send signals to specific threads so that when you 'kill -9 pid',
you only kill one individual thread in the process.
* on Solaris too a process can contain multiple threads (called lightweight
processes or lwp for short). However, processes and threads are each separate
system objects. When you send a signal it is sent to the process: 'kill -9 pid'
will kill the process and all its threads. Also, individual lwps do not have a
globally unique identifier. Instead their ids (typically 0, 1, 2, etc.) are only
unique within a process. So if you want to refer to a specific lwp in the system
you must use specify both the pid and the lwpid.
Wine and in particular the Wine server, need the following functionality:
1. uniquely identify a thread in the system
2. sending a signal to a specific thread
3. precisely identifying a thread's parent thread
(for handle inheritance when creating a new process, etc. It is a
prerequisite for the debugger too)
See the following files for reference:
* server/process.c server/process.h
Where the wineserver keeps track of Windows processes
* server/thread.c server/thread.h
Where the wineserver keeps track of Windows threads
* scheduler/client.c
Called by a new Windows thread to register itself
* scheduler/process.c
Called by a new Windows process to register itself
* include/wine/server_protocol.h
Defines the structures used for the wineserver protocol
Then, to identify a thread uniquely we can:
* add a unix_pid field to the 'struct process' in server/process.h
* rename the 'unix_pid' field in 'struct thread' to 'unix_tid' in
server/thread.h
* on Linux, set unix_pid=0 and unix_tid=getpid()
* on Solaris, set unix_pid=getpid() and unix_tid=_lwp_self()
* make sure we do not write code that would identify a process by its unix_pid
(would be a tempting thing to do on Solaris but does not work on Linux)
* use both unix_pid and unix_tid whenever we need to identify a thread (i.e.
find its struct thread structure)
To send a signal to a specific thread, the solution is to use the procfs:
Open /proc/<pid>/lwp</lwpid>/lwpctl and write two ints: PCKILL followed by the
signal id. Do a man -s 4 proc or find it online at:
http://www.cs.princeton.edu/cgi-bin/man2html?proc:4
Identifying a thread's parent is harder because there is no lwp_getppid()
function. So I propose the following trick:
* just before creating a new process (in fork_and_exec), set the
WINE_PARENT_LWPID environment variable to "pid:lwpid"
* during the process initialization check for the WINE_PARENT_LWPID environment
variable and reset it right after use
* if set, make sure that the pid matches our ppid. If so, then the information
it contains is valid and the lwpid is the id of our parent lwp
(which means wrapper scripts must _exec_ wine)
* if the pid does not match our ppid, then this is a stale environment
variable: a Wine process must have started a Unix process, which in turn
launched another Wine process. But the Unix process is our parent, not the Wine
process so there are no handles to inherit anyway.
* if the variable is not set, then this Wine process was started from Unix so
there is nothing to inherit
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=904>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://bugs.winehq.com/show_bug.cgi?id=901
------- Additional Comments From hoingram(a)bellsouth.net 2002-07-21 14:13 -------
i upgraded to version 20020710 but had the same error. Is there anything else I
can try?
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=901>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://bugs.winehq.com/show_bug.cgi?id=903
Summary: PathIsURL returning true for invalid formats.
Product: Wine
Version: CVS
Platform: PC
URL: http://msdn.microsoft.com/library/default.asp?url=/libra
ry/en-
us/shellcc/platform/Shell/reference/shlwapi/path/pathisu
rl.asp
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: wine-binary
AssignedTo: wine-bugs(a)winehq.com
ReportedBy: dclark(a)akamail.com
According to the above URL, a "microsoft.com" should not be considered a valid
URL. It needs to be preceded with "http://". The wine implementation of
PathIsURLA returns true for those kinds of entries.
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=903>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://bugs.winehq.com/show_bug.cgi?id=900
------- Additional Comments From tony_lambregts(a)telusplanet.net 2002-07-21 12:23 -------
Out of curiosity how old is your computer? I do regression testing all the time
on mine.
P233 with 96 mb RAM and 40GB hardDrive. I did regression testing with a 3GB
harddrive and 32 mb ram using the same computer.
Yes it is time consuming but you can use your computer while it is doing a
compile. With the timeframe you are talking about it should take at most 6
itinerations to narrow it down to the day the patch was applied.
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=900>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://bugs.winehq.com/show_bug.cgi?id=900
------- Additional Comments From hogger2(a)mushworld.dnsart.com 2002-07-21 11:28 -------
There is no download for this program, however there is a for to fill out to get
the lite version on cd mailed to you for free. This is the version I used. I
have a relatively old computer, so regression testing would be very very time
consuming. However below is the url to the form to get a copy of the cd for
anyone willing to help.
http://www.cadencepcb.com/products/downloads/orcaddemo/frmorcaddemocd.asp
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=900>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://bugs.winehq.com/show_bug.cgi?id=889
------- Additional Comments From tuiningas_ml(a)shaw.ca 2002-07-21 00:26 -------
I followed the trail a little bit
further as I noticed that "hot spots" on an image (like buttons) would
fade in and out when the window wasn't at the top left of the screen.
The trail led to the file dlls/x11drv/winpos.c. It is making a call to
MapWindowPoints() which in turn calls WINPOS_GetWinOffset(). If I
eliminate the call to MapWindowPoints() in the function expose_window()
at line 290, (and restore the original version of windows/winpos.c)
everything works beautifully. The window draws itself properly and the
buttons work as expected. I am not all that familiar with Wine code,
though, so can anyone think of a good reason why this code ought to be
there? Should I submit a patch? And if so, can anyone point me to the
method required for doing so? Thanks.
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=889>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://bugs.winehq.com/show_bug.cgi?id=901
------- Additional Comments From tony_lambregts(a)telusplanet.net 2002-07-20 23:08 -------
Well the first thing you should do is get a newer version of wine
http://www.winehq.com/download/
I recommend installing from tarball. This isn't to hard to do if you follow the
instructions in the README file. Also have a look at the wine users guide.
http://www.winehq.com/Docs/wine-user/
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=901>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://bugs.winehq.com/show_bug.cgi?id=902
tony_lambregts(a)telusplanet.net changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |DUPLICATE
------- Additional Comments From tony_lambregts(a)telusplanet.net 2002-07-20 22:57 -------
*** This bug has been marked as a duplicate of 901 ***
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=902>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://bugs.winehq.com/show_bug.cgi?id=901
------- Additional Comments From tony_lambregts(a)telusplanet.net 2002-07-20 22:57 -------
*** Bug 902 has been marked as a duplicate 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=901>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://bugs.winehq.com/show_bug.cgi?id=792
------- Additional Comments From tony_lambregts(a)telusplanet.net 2002-07-20 22:16 -------
Created an attachment (id=236)
Screen shot showing "cutouts"
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=792>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://bugs.winehq.com/show_bug.cgi?id=792
------- Additional Comments From tony_lambregts(a)telusplanet.net 2002-07-20 22:11 -------
Well I'm making progress. I found out that none of the backgrounds for any of
the controls are really being drawn. Each of the individual controls has a
cutout in the screen. As the controls are drawn the cutouts are "filled in" by
the controls, but in the case of the files group the individual controls are not
big enough to fill in the whole area.
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=792>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://bugs.winehq.com/show_bug.cgi?id=902
Summary: sound
Product: Wine
Version: 20010112
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P5
Component: wine-multimedia
AssignedTo: wine-bugs(a)winehq.com
ReportedBy: hoingram(a)bellsouth.net
the I am using version 20011226 on a SuSE 8.0 machine. The error i get is
fixme:midi:OSS_MidiInit Synthesizer support MIDI in. Not
supported yet (please report)
err:wave:wodPlayer_Reset grin
I am trying to run a cbt specifically netg that has sound on it. The sound does
not work correctly.
Can anyone help me fix this.
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=902>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://bugs.winehq.com/show_bug.cgi?id=901
Summary: sound
Product: Wine
Version: 20010112
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P5
Component: wine-multimedia
AssignedTo: wine-bugs(a)winehq.com
ReportedBy: hoingram(a)bellsouth.net
the I am using version 20011226 on a SuSE 8.0 machine. The error i get is
fixme:midi:OSS_MidiInit Synthesizer support MIDI in. Not
supported yet (please report)
err:wave:wodPlayer_Reset grin
I am trying to run a cbt specifically netg that has sound on it. The sound does
not work correctly.
Can anyone help me fix this.
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=901>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://bugs.winehq.com/show_bug.cgi?id=900
tony_lambregts(a)telusplanet.net changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |regression
------- Additional Comments From tony_lambregts(a)telusplanet.net 2002-07-20 15:46 -------
This is a regression bug from your description. As bugs go this is easy to find
and fix using regression testing as outlined in the following link:
http://www.winehq.org/Docs/wine-devel/cvs-regression.shtml
If there is a downloadable version of this program then it is possible for
someone else to do the regression testing. If there isn't then it is up to 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=900>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://bugs.winehq.com/show_bug.cgi?id=900
Summary: Upgrade from 20020605 to 20020710 broke Orcad Caputre
Support
Product: Wine
Version: 20020710
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: wine-binary
AssignedTo: wine-bugs(a)winehq.com
ReportedBy: hogger2(a)mushworld.dnsart.com
Upon upgrading from 20020605 to 20020710, whenever I try to use ORcad Capture (a
part of the PSpice Lite software), I get window popup with a tilebar of DSM0006
and an error message unable to save <the file I was trying to create> and on the
next line, "system error". What's interesting is the file does get created, but
the program refuses to register that it exists (still prompts me to save unsaved
stuff. If you need more detailed information, please e-mail back. Thankyou
--Greg
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=900>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://bugs.winehq.com/show_bug.cgi?id=885
------- Additional Comments From dclark(a)akamail.com 2002-07-20 11:38 -------
I tried both. They partially fix it for me, but not completely. I still get a
single piece of the old view, though it is a much smaller piece than before. It
always happens if I first move forward and then turn sideways. And of course the
other noticable thing is that the window does not slide (scroll) but instead
just jumps from one view to the other.
I notice that if I obscure part of the window with another window and then
uncover it, that it is repainted with the corruption still there. By the way, I
can always get the window to repaint correctly by sliding my mouse down into the
area at the bottom where the books are kept. This might require the window focus
to be set to focus follows mouse.
I don't really have much of a feel for where the problem is. It appears to me
that the bitblt commands have the correct parameters, so like you I think this
is some sort of timing problem. I have the Xlib reference book that explains the
XCopyArea command, but it does not mention any gotchas if the two Drawables are
the same. At the point I don't think I now enough to know how to attack it.
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=885>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://bugs.winehq.com/show_bug.cgi?id=899
Summary: Bad focus messages on window creation
Product: Wine
Version: 20020710
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: wine-directx
AssignedTo: wine-bugs(a)winehq.com
ReportedBy: mmazur(a)pld-linux.org
Well. I've runned myself some starcraft 1.00. But there is a problem. When the
window get's created I have no graphics. The game itself "thinks" everything is
ok though. Now if I have Desktop commented out and "Managed" = "Y" it's kind of
easy to get the graphics working. Simply switching focus to another window, and
then clicking back on starcrafts window get's the graphics back. IMHO this has
something to do with some messages (wm_paint?) not being sent to the starcraft
window upon creation.
Note1: twm has the same behaviour :)
Note2: same thing with a snapshot from 200204 and current cvs winex. So this has
to be old.
Note3: guess what happens when I turn "DXGrab" = "Y". Alt+Tab doesn't work, and
I'm blind enough not to be able to get out of starcraft :) Thank Linus for SysRq :)
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=899>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://bugs.winehq.com/show_bug.cgi?id=733
gerald(a)pfeifer.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution| |FIXED
------- Additional Comments From gerald(a)pfeifer.com 2002-07-20 06:49 -------
As far as I can tell, this has been resolved now by virtue of the
"properly detect reentrant libc" fix to configure. On FreeBSD (and
other non-Linux systems) previously a reentrant libc was not detected
probperly.
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=733>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://bugs.winehq.com/show_bug.cgi?id=898
Summary: fixme:dc:GetDCEx not supported yet
Product: Wine
Version: 20020509
Platform: PC
OS/Version: Linux
Status: NEW
Severity: trivial
Priority: P2
Component: wine-programs
AssignedTo: wine-bugs(a)winehq.com
ReportedBy: corporal_pisang(a)counter-strike.com.my
fixme:dc:GetDCEx not supported yet on other process window 10021
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=898>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://bugs.winehq.com/show_bug.cgi?id=787
------- Additional Comments From corporal_pisang(a)counter-strike.com.my 2002-07-20 05:38 -------
happens with wine-20020710 as well.
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=787>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.