From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Harold Weissfield" To: cygwin@sourceware.cygnus.com Subject: Re: Memory Violation With Windres and Shared Data Segments Date: Fri, 06 Aug 1999 20:25:00 -0000 Message-id: <19990807032454.11049.qmail@hotmail.com> X-SW-Source: 1999-08/msg00126.html >I believe the only difference is that it has the "SHARED" bit set in >the section attributes, in addition to the usual initialized data, >read-write, etc flags. > >Can someone send me a testcase so I can see if my local changes fix this >or not? If it's obvious already, I know nothing about these shared >segments. > >Regards, >Mumit Thank you for your help, Mumit, Chris, and Anders. I will try to experiment around with the information that you guys have provided, and I shall reply back if I find any favorable results. In case you are wondering why I'm doing this, I am writing a shell replacement for Explorer for our lab at school, and one of the implementation details involves creating a global hook using SetWindowsHookEx(). Unfortunately, the requirements for having such a hook involve having a shared data segment in a DLL, so that is the dilema that I am presently trying to solve. Mumit, I am not aware of the proper procedures for submitting code, so forgive me if my approach is mistaken. During the process of developing this shell, I noticed that the following notification messages for the appbar were not in shellapi.h #define ABN_STATECHANGE 0x0000000 #define ABN_POSCHANGED 0x0000001 #define ABN_FULLSCREENAPP 0x0000002 #define ABN_WINDOWARRANGE 0x0000003 Please feel free to add them to the headers at your convenience. Meanwhile, I thank you once again, and I shall get busy on my coding. Cheers, Harold Weissfield _______________________________________________________________ Get Free Email and Do More On The Web. Visit http://www.msn.com -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Harold Weissfield" To: cygwin@sourceware.cygnus.com Subject: Re: Memory Violation With Windres and Shared Data Segments Date: Tue, 31 Aug 1999 23:49:00 -0000 Message-ID: <19990807032454.11049.qmail@hotmail.com> X-SW-Source: 1999-08n/msg00126.html Message-ID: <19990831234900.PKqc_IeEN5qo_R9xrIWRt2HvhrH1AxxYo_sASHxrUxw@z> >I believe the only difference is that it has the "SHARED" bit set in >the section attributes, in addition to the usual initialized data, >read-write, etc flags. > >Can someone send me a testcase so I can see if my local changes fix this >or not? If it's obvious already, I know nothing about these shared >segments. > >Regards, >Mumit Thank you for your help, Mumit, Chris, and Anders. I will try to experiment around with the information that you guys have provided, and I shall reply back if I find any favorable results. In case you are wondering why I'm doing this, I am writing a shell replacement for Explorer for our lab at school, and one of the implementation details involves creating a global hook using SetWindowsHookEx(). Unfortunately, the requirements for having such a hook involve having a shared data segment in a DLL, so that is the dilema that I am presently trying to solve. Mumit, I am not aware of the proper procedures for submitting code, so forgive me if my approach is mistaken. During the process of developing this shell, I noticed that the following notification messages for the appbar were not in shellapi.h #define ABN_STATECHANGE 0x0000000 #define ABN_POSCHANGED 0x0000001 #define ABN_FULLSCREENAPP 0x0000002 #define ABN_WINDOWARRANGE 0x0000003 Please feel free to add them to the headers at your convenience. Meanwhile, I thank you once again, and I shall get busy on my coding. Cheers, Harold Weissfield _______________________________________________________________ Get Free Email and Do More On The Web. Visit http://www.msn.com -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com