November 2007 - Wine-Devel - list.winehq.org

Re: Regression testing and cc-ing the author

by Scott Ritchie

James Hawkins wrote: > > On Nov 17, 2007, at 6:24 AM, Paul Vriens <paul.vriens.wine(a)gmail.com> > 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

Nov. 18, 2007

Re: Removing Windows and Solaris from the Downloads page

by Chris McKillroy

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

Nov. 17, 2007

Re: Add tests for RSA_AES provider in rsaenh

by Vijay Kiran Kamuju

On Nov 17, 2007 11:45 AM, James Hawkins <truiken(a)gmail.com> wrote: > > > On Nov 17, 2007, at 9:34 AM, "Vijay Kiran Kamuju" > <infyquest(a)gmail.com> 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 <msclrhd(a)googlemail.com> wrote: > >> > >> On 16/11/2007, Vijay Kiran Kamuju <infyquest(a)gmail.com> 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

Nov. 17, 2007

Re: Add tests for RSA_AES provider in rsaenh

by James Hawkins

On Nov 17, 2007, at 9:34 AM, "Vijay Kiran Kamuju" <infyquest(a)gmail.com> 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 <msclrhd(a)googlemail.com> wrote: >> >> On 16/11/2007, Vijay Kiran Kamuju <infyquest(a)gmail.com> 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

Nov. 17, 2007

Re: Regression testing and cc-ing the author

by James Hawkins

On Nov 17, 2007, at 6:24 AM, Paul Vriens <paul.vriens.wine(a)gmail.com> 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

Nov. 17, 2007

Re: Add tests for RSA_AES provider in rsaenh

by Vijay Kiran Kamuju

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 <msclrhd(a)googlemail.com> wrote: > > On 16/11/2007, Vijay Kiran Kamuju <infyquest(a)gmail.com> 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 > > >

Nov. 17, 2007

Re: ReadProcessMemory question

by Robert Shearman

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

Nov. 17, 2007

re: ReadProcessMemory question

by Dan Kegel

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

Nov. 17, 2007

ReadProcessMemory Question

by Dave Cartright

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.

Nov. 17, 2007

Re: Regression testing and cc-ing the author

by Paul Vriens

On Nov 17, 2007 3:44 PM, Dmitry Timoshkov <dmitry(a)codeweavers.com> wrote: > > "Paul Vriens" <paul.vriens.wine(a)gmail.com> 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.

Nov. 17, 2007