Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com From: "Robert Collins" To: "'Ralf Habacker'" , "'Nicholas Wourms'" , Cc: Subject: RE: SysV Ipc shm revisited...A new solution Date: Sat, 8 Jun 2002 08:29:24 +1000 Message-ID: <002101c20e72$c78f40b0$0200a8c0@lifelesswks> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal In-Reply-To: <001c01c20e58$33d7d950$316307d5@BRAMSCHE> > -----Original Message----- > From: Ralf Habacker [mailto:Ralf.Habacker@freenet.de] > Sent: Saturday, 8 June 2002 5:19 AM > To: Robert Collins; 'Nicholas Wourms'; cygwin@cygwin.com > Cc: cwilson@ece.gatech.edu > Subject: RE: SysV Ipc shm revisited...A new solution > > > >Robert Collins wrote: > > > Already provided. What will happen when the 64 bit key is > exported is > > that fresh cygipc linked programs will fail, but existing > programs will > > still work correctly. If something like ipcdaemon2.exe exists - OR - > > cygipc is re-released as a 64-bit version, then new links > will succeed > > (but at the possible cost of breaking old binaries). > > > Why must this be ? Could not the released 64-bit version only > use the most > significant long word of key_t, so that it is compatible to > the old binaries and > can use the 64 bit key_t definition ? It wouldn't be compatible with the old binaries because the signature would still be wrong, and this would lead to immediate crashes when it tried to pop to much off the stack. Rob -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/