Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com From: "Dave Korn" To: Subject: RE: Problems with structs Date: Thu, 18 Mar 2004 10:45:52 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit In-Reply-To: Message-ID: X-OriginalArrivalTime: 18 Mar 2004 10:45:52.0671 (UTC) FILETIME=[2F2512F0:01C40CD6] > -----Original Message----- > From: cygwin-owner On Behalf Of c.h.breukink > Sent: 18 March 2004 08:07 > I am using Cygwin for the first time. And I got segmentation > faults in my application which worked fine on Unix. I think > now that I know why. It has something to do with structs.When > I leave them, I have no problems. Who have experience with this? > > Christien Breukink Well, there's two possibilities: 1) You have a stray pointer or malloc bug (or one of various similar problems) in your code, and it just happened to work and not crash by luck on Unix; minor differences in process layout and environment cause the underlying bug to be hidden in Unix and exposed in Cygwin. 2) You've found a bug or unimplemented feature in the cygwin api. If you're mentioning structs, my guess is you're doing something wrong with pointers or arrays. It's a very common thing in C. cheers, DaveK -- Can't think of a witty .sigline today.... -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/