X-Spam-Check-By: sourceware.org Date: Thu, 8 Feb 2007 10:05:52 +0100 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: weird seg. fault related to fhandler_pipe::get_guard() Message-ID: <20070208090552.GZ27843@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <15882 DOT 52592 DOT qm AT web32408 DOT mail DOT mud DOT yahoo DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <15882.52592.qm@web32408.mail.mud.yahoo.com> User-Agent: Mutt/1.4.2.2i Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 On Feb 7 14:12, winner wei wrote: > Building was a success, but when run it I got a segmentation fault > immediately while executing function C (B was fine, and nothing was > run in C). The code has no any problems on linux, solaris and irix. This is no indication whatsoever. I have code which runs perfectly on Cygwin but crashes on my 64 bit Linux installation. The cause is simply a missing header file. > Stack trace: > Frame Function Args > 000773D8 005E5B63 (001A77F0, 00000001, 00B06F38, 00A510E8) > 001A41B8 0041D81B (001A77F0, 00000000, 00000001, 00000000) > 0022CB98 0040C814 (0022CBC0, 00912930, 00686FB0, 004011BF) > 0022CCA8 00401238 (00000003, 00912930, 00910090, 60030000) > 0022CD98 61006198 (00000000, 0022CDD0, 61005510, 0022CDD0) > 61005510 61004416 (0000009C, A02404C7, E8611001, FFFFFF48) The call stack shows that it happens in your code. It shows nothing else. You will have to build your application with -g and debug it with gdb the usual way. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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/