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 Date: Sun, 24 Apr 2005 10:09:41 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Again, XWin crashes with cigwin-1.5.15-1 on Win98. Message-ID: <20050424140941.GA3578@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com References: <151440-22005402462012803 AT cantv DOT net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.8i On Sun, Apr 24, 2005 at 02:05:52PM +0200, Alexander Gottwald wrote: >Rodrigo Medina wrote: > >> null screen fn ReparentWindow >> null screen fn RestackWindow >> InitQueue - Calling pthread_mutex_init >> InitQueue - pthread_mutex_init returned >> InitQueue - Calling pthread_cond_init >> InitQueue - pthread_cond_init returned >> ---Type to continue, or q to quit--- >> >> Program received signal SIGSEGV, Segmentation fault. >> [Switching to thread -46904803.0xffc16851] >> 0xbff7a606 in KERNEL32!Heap32ListNext () >> from /cygdrive/c/WINDOWS/SYSTEM/KERNEL32.DLL >> (gdb) > >what about a backtrace? The message is very useless. > >thread apply all bt should print a backtrace for all thread Unless you're using a debugging DLL the backtrace is also useless. This. Is a recording. cgf -- 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/