X-Spam-Check-By: sourceware.org From: "Jon S. Berndt" To: Subject: RE: Thread-related segfault with cygwin 1.5.19-4 Date: Tue, 20 Jun 2006 07:15:11 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) In-Reply-To: <4497E364.19EACCFB@dessent.net> 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 > What you are seeing: > > - does not represent an actual problem in the pthread library > - is not an actual segfault > - is a bug/misfeature in gdb that has been fixed in CVS > - can be worked around just by typing "c" or "continue" > - has been discussed in depth, at length, ad infinitum, over and over > and over on this list numerous times in the past, so please read those > threads. Try a google search for: site:cygwin.com inurl:ml inurl:cygwin > inurl:2006 gdb sigsegv > > Brian I appreciate your response. This helps. It may not appear that I've done my research, but as an open source developer (and project coordinator) for many years, I understand the right way to seek help. I've been looking for days via various google searches, and asking other developers for help. I searched the cygwin mailing list archives, and checked the cygwin FAQ ("Known problems ..."). Even though this is not a real cygwin problem, if this question gets asked so often, it might be worth adding a response in the FAQ. Thanks, Jon -- 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/