X-Spam-Check-By: sourceware.org
From: "Dave Korn" <dave DOT korn AT artimi DOT com>
To: <cygwin AT cygwin DOT com>
References:  <ee84e5f30703061114q58aa0675jd4d4a69c759442a5 AT mail DOT gmail DOT com> <Pine DOT GSO DOT 4 DOT 63 DOT 0703061451230 DOT 6189 AT access1 DOT cims DOT nyu DOT edu> <esnbau$5m8$1 AT sea DOT gmane DOT org> <45EF3A38 DOT 8030205 AT cygwin DOT com> <esp7en$qqu$1 AT sea DOT gmane DOT org>
Subject: RE: GDB problem (under cygwin)
Date: Thu, 8 Mar 2007 17:00:56 -0000
Message-ID: <039501c761a3$58af5e80$2e08a8c0@CAM.ARTIMI.COM>
MIME-Version: 1.0
Content-Type: text/plain; 	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <esp7en$qqu$1@sea.gmane.org>
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
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 08 March 2007 14:43, Raymond Miller wrote:

> Finally I found what is the problem. 

  No, I don't think you have.  You haven't even clearly identified a problem.

  You say that the problem is that gdb reports a SIGSEGV in thread 2 when you
compiled with cygwin gcc, but for all anyone knows that could just be because
your program caused a crash and thread 2 is the signal-handling thread in
cygwin programs.

  When you compile with mingw's gcc, you are compiling an entirely different
program, because mingw doesn't support all the posix things like signals etc.
that cygwin supports.

> Is it a bug in that version?

  Again, nobody can tell.  We don't have your code, we don't have your
machine, you haven't given an adequate description of the problem.  Just going
by sheer balance of probabilities, however, it is far more likely that gcc is
doing the right thing and your program has a bug in it.

    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/