X-Spam-Check-By: sourceware.org Subject: Re: XP64 problem From: skaller To: mwoehlke Cc: cygwin AT cygwin DOT com In-Reply-To: References: <1151414993 DOT 7485 DOT 12 DOT camel AT rosella DOT wigram> Content-Type: text/plain Date: Wed, 28 Jun 2006 03:13:33 +1000 Message-Id: <1151428413.5596.22.camel@rosella.wigram> Mime-Version: 1.0 X-Mailer: Evolution 2.6.1 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk 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 Tue, 2006-06-27 at 09:54 -0500, mwoehlke wrote: > skaller wrote: > FWIW, I run Cygwin on Win2K3 R2 x64 with no problems. Well Cygwin 'runs' with no problems. The problem here seems to be a problem a with a binary generated by gcc et al, that is, it isn't really a Cygwin problem as such. > However, I mostly > use Microsoft's 'cl' as the compiler for my own programs. I do that too, and also use MinGW compiler bundled with Cygwin's gcc via the -nocygwin option thing. > Did you try using a debugger (like gdb) to see *why* your program is > SEGV'ing? I tried gdb briefly, but (a) its hard to use because it exhibits spurious errors due to signals Cygwin normally catches (b) I'm no expert with gdb I mainly develop on Linux: the building on Cygwin (and using cl) is just to check the system builds. -- John Skaller Felix, successor to C++: http://felix.sf.net -- 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/