Hi, and a regression in bug 10486
Hi I have found a regression in wine. a strange one. What is a policy about posting such regressions, here on malling list? (Or is regression is worth enough to post it here?) I don't play that particular game on wine and it's "minor" bug - but i have found (via bitsect) that "user32: Cache the window class name on the client side." produce strange effects on directx code. I have faith that regressions are supposed to post here as well. More info in bug #10486 Take care & Hope that helps -- Paweł Różański, a wine user witch occasionally post something on appdb/bugzilla
Re: Regression testing and cc-ing the author
James Hawkins wrote: > > On Nov 17, 2007, at 6:24 AM, Paul Vriens <[EMAIL PROTECTED]> > wrote: > >> Hi, >> >> I've opened a bug (which if fixed now btw) and the regression >> testing page at >> http://wiki.winehq.org/RegressionTesting said "Also be sure to add >> the author of >> the patch to the CC". >> >> So this is what I did. >> >> Should that line be removed from the wiki or do we generally want >> the author to >> be CC-ed? >> >> -- >> Cheers, >> >> Paul. >> >> > > It's not that cut and dry. Some people don't mind being CC'ed. Some > people do mind being CC'ed, and I know I'm not the only one. Some > devels aren't subscribed to wine-bugs. Like I said before, asking the > devel to assign the bug to himself is a lot more respectful. > > -- > James > > Is there a bugzilla setting for this? Eg "don't allow others to CC me"? Thanks, Scott Ritchie
Re: Removing Windows and Solaris from the Downloads page
I compiled wine on Solaris using a .spec provided by the people of http://pkgbuild.sourceforge.net/spec-files-extra/ Maybe contact them ? My version runs quite nice as far as i can see. Cheers
ReadProcessMemory Question
I am trying to read the memory of another process with ReadProcessMemory but I can only get it to work when I use VirtualAllocEx to commit the region of memory - problem is (as you very well know) that VirtualAllocEx initializes the region with 0s. So my question is how do I get ReadProcessMemory to work without using VirtualAllocEx?? - Be a better pen pal. Text or chat with friends inside Yahoo! Mail. See how.
Re: Add tests for RSA_AES provider in rsaenh
On Nov 17, 2007 11:45 AM, James Hawkins <[EMAIL PROTECTED]> wrote: > > > On Nov 17, 2007, at 9:34 AM, "Vijay Kiran Kamuju" > <[EMAIL PROTECTED]> wrote: > > > There is a test in derive_key function that fails. > > If I put a if condition to make it a todo_wine, it looks loke a hack > > and its ugly > > As that function is used alot. > > > > --- > > VJ > > > > On Nov 16, 2007 5:45 PM, Reece Dunn <[EMAIL PROTECTED]> wrote: > >> > >> On 16/11/2007, Vijay Kiran Kamuju <[EMAIL PROTECTED]> wrote: > >>> ChangeLog > >>> -- > >>> Add tests for RSA_AES provider in rsaenh > >>> > >>> Note: > >>> --- > >>> Some tests might fail as there is no RSA_AES provider in wine. > >>> These will be fixed once the implementation is in place, which > >>> will be > >>> sent next. > >> > >> The recommended way to do this is mark the parts of the tests that > >> fail in Wine with todo_wine. > >> > >> - Reece > >> > >> > >> > > > > > > Ugly or not, the tests wont be accepted otherwise. Also, please > bottom-post on this list. > > -- > James > It seems there is a bug in the tests, Once this is fixed I will resend it again. I have sent this to Juan Lang for review. Once our expert tells me whats wrong I will resend. Sorry for top posting, I was in a hurry. --- VJ
Re: Add tests for RSA_AES provider in rsaenh
On Nov 17, 2007, at 9:34 AM, "Vijay Kiran Kamuju" <[EMAIL PROTECTED]> wrote: > There is a test in derive_key function that fails. > If I put a if condition to make it a todo_wine, it looks loke a hack > and its ugly > As that function is used alot. > > --- > VJ > > On Nov 16, 2007 5:45 PM, Reece Dunn <[EMAIL PROTECTED]> wrote: >> >> On 16/11/2007, Vijay Kiran Kamuju <[EMAIL PROTECTED]> wrote: >>> ChangeLog >>> -- >>> Add tests for RSA_AES provider in rsaenh >>> >>> Note: >>> --- >>> Some tests might fail as there is no RSA_AES provider in wine. >>> These will be fixed once the implementation is in place, which >>> will be >>> sent next. >> >> The recommended way to do this is mark the parts of the tests that >> fail in Wine with todo_wine. >> >> - Reece >> >> >> > > Ugly or not, the tests wont be accepted otherwise. Also, please bottom-post on this list. -- James
Re: Regression testing and cc-ing the author
On Nov 17, 2007, at 6:24 AM, Paul Vriens <[EMAIL PROTECTED]> wrote: > Hi, > > I've opened a bug (which if fixed now btw) and the regression > testing page at > http://wiki.winehq.org/RegressionTesting said "Also be sure to add > the author of > the patch to the CC". > > So this is what I did. > > Should that line be removed from the wiki or do we generally want > the author to > be CC-ed? > > -- > Cheers, > > Paul. > > It's not that cut and dry. Some people don't mind being CC'ed. Some people do mind being CC'ed, and I know I'm not the only one. Some devels aren't subscribed to wine-bugs. Like I said before, asking the devel to assign the bug to himself is a lot more respectful. -- James
Re: Add tests for RSA_AES provider in rsaenh
There is a test in derive_key function that fails. If I put a if condition to make it a todo_wine, it looks loke a hack and its ugly As that function is used alot. --- VJ On Nov 16, 2007 5:45 PM, Reece Dunn <[EMAIL PROTECTED]> wrote: > > On 16/11/2007, Vijay Kiran Kamuju <[EMAIL PROTECTED]> wrote: > > ChangeLog > > -- > > Add tests for RSA_AES provider in rsaenh > > > > Note: > > --- > > Some tests might fail as there is no RSA_AES provider in wine. > > These will be fixed once the implementation is in place, which will be > > sent next. > > The recommended way to do this is mark the parts of the tests that > fail in Wine with todo_wine. > > - Reece > > >
Re: ReadProcessMemory question
Dave Cartright wrote: > I am trying to read the memory of another process with > ReadProcessmemory and I can only get it to work when I commit the > entire region I want to read with VirtualAllocEx - but as you probably > know when I do this it initializes the entire memory region to 0s. > So my question is how do I get ReadProcessmemory to read from the region?? It sounds to me like you're trying to read the previous contents of areas of memory. However, you don't seem to realise either that virtual memory is not physical memory or that uncommitted virtual memory is not backed by a page of memory in swap or physical memory, so calling ReadProcessMemory on it doesn't make sense as there is no data there to be read! Furthermore, when a page of virtual memory is deallocated then it free to be allocated again by any process in the system, and as you say it is initialised to all 0's as a security measure and you can't get that same page back again. -- Rob Shearman
re: ReadProcessMemory question
Dave wrote: > I am trying to read the memory of another process with > ReadProcessmemory and I can only get it to work when > I commit the entire region I want to read with VirtualAllocEx - > but as you probably know when I do this it > initializes the entire memory region to 0s. > So my question is how do I get ReadProcessmemory to read from the region?? What are you trying to do? A little more context might help. FWIW, ReadProcessMemory has some drawbacks as an IPC mechanism: http://blogs.msdn.com/oldnewthing/archive/2006/01/17/513779.aspx Here are a few examples of how to use ReadProcessMemory: http://www.gamedev.net/community/forums/topic.asp?topic_id=328279 http://www.codeproject.com/threads/int64_memsteal.asp
Re: Regression testing and cc-ing the author
On Nov 17, 2007 3:44 PM, Dmitry Timoshkov <[EMAIL PROTECTED]> wrote: > > "Paul Vriens" <[EMAIL PROTECTED]> wrote: > > > I've opened a bug (which if fixed now btw) and the regression testing page > > at > > http://wiki.winehq.org/RegressionTesting said "Also be sure to add the > > author of > > the patch to the CC". > > > > So this is what I did. > > > > Should that line be removed from the wiki or do we generally want the > > author to > > be CC-ed? > > IMHO that line should be left in the wiki, simply because not all patch > submitters are subscribed to wine-bugs mailing list. But I find nothing > wrong if somebody already subscribed asks to not add him to the cc: list. > > -- > Dmitry. > I saw James' email after I wrote that email. I think it's fine as well if somebody asks not to be added. But not everybody that adds bug descriptions reads wine-devel. At least I will not add anybody to the cc-list anymore and try to contact the author. Cheers, Paul.
Re: Regression testing and cc-ing the author
"Paul Vriens" <[EMAIL PROTECTED]> wrote: > I've opened a bug (which if fixed now btw) and the regression testing page at > http://wiki.winehq.org/RegressionTesting said "Also be sure to add the author > of > the patch to the CC". > > So this is what I did. > > Should that line be removed from the wiki or do we generally want the author > to > be CC-ed? IMHO that line should be left in the wiki, simply because not all patch submitters are subscribed to wine-bugs mailing list. But I find nothing wrong if somebody already subscribed asks to not add him to the cc: list. -- Dmitry.
Regression testing and cc-ing the author
Hi, I've opened a bug (which if fixed now btw) and the regression testing page at http://wiki.winehq.org/RegressionTesting said "Also be sure to add the author of the patch to the CC". So this is what I did. Should that line be removed from the wiki or do we generally want the author to be CC-ed? -- Cheers, Paul.
Re: #winehackers invite only?
On Sat, Nov 17, 2007 at 01:58:31PM +0100, Stefan Dösinger wrote: > Hello, > Did anyone change #winehackers to require an invite? What was the reason for > this? Sorry, we had a kiddie problem. It is back to normal now. Ciao, Marcus
Re: #winehackers invite only?
Am Samstag, 17. November 2007 13:58:31 schrieb Stefan Dösinger: > Hello, > Did anyone change #winehackers to require an invite? What was the reason > for this? It's sorted out already signature.asc Description: This is a digitally signed message part.
Re: Add tests for RSA_AES provider in rsaenh
On 16/11/2007, Vijay Kiran Kamuju <[EMAIL PROTECTED]> wrote: > ChangeLog > -- > Add tests for RSA_AES provider in rsaenh > > Note: > --- > Some tests might fail as there is no RSA_AES provider in wine. > These will be fixed once the implementation is in place, which will be > sent next. The recommended way to do this is mark the parts of the tests that fail in Wine with todo_wine. - Reece
#winehackers invite only?
Hello, Did anyone change #winehackers to require an invite? What was the reason for this? Thanks, Stefan signature.asc Description: This is a digitally signed message part.
Re: Removing Windows and Solaris from the Downloads page
Hi, Roderick Colenbrander schreef: > They should get updated. In case of Solaris there are some bugs which prevent > it from running I think. In case of Windows someone needs to update the > package. It is very useful to use some of the wine dlls (wined3d for > instance) or tests on Windows. > The question is what dlls should we include? Something like the d3d dll's would be useful, and a lot of other dll's (mshtml, shdocvw, etc) probably too. Unfortunately wine won't build on mingw properly,if you try a 'make' in mingw, it will bomb out on building in dll's. If someone wants to maintain windows dll's, the makefiles should be adjusted so that it will build properly, and skip the dll's wine can't emulate in windows. Such as ntdll, kernel32, advapi, to name a few, probably all dll's with wineserver calls and perhaps a few more. Regards, Maarten.
Re: Removing Windows and Solaris from the Downloads page
> It appears that the links for the Windows and Solaris versions on the > winehq downloads page are very, very old. Since they're no longer > maintained, we should just remove them, yes? > > Thanks, > Scott Ritchie > They should get updated. In case of Solaris there are some bugs which prevent it from running I think. In case of Windows someone needs to update the package. It is very useful to use some of the wine dlls (wined3d for instance) or tests on Windows. Roderick -- GMX FreeMail: 1 GB Postfach, 5 E-Mail-Adressen, 10 Free SMS. Alle Infos und kostenlose Anmeldung: http://www.gmx.net/de/go/freemail
