From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Stak dump with tar.[bz2/gz] files (Cygwin) Date: Fri, 13 Jun 2008 19:39:16 +0300 Message-ID: References: <48511871.1090203@alice.it> <4851806A.6070104@alice.it> <48529613.6020302@alice.it> Reply-To: Eli Zaretskii NNTP-Posting-Host: lo.gmane.org Content-Transfer-Encoding: 7BIT X-Trace: ger.gmane.org 1213375380 31790 80.91.229.12 (13 Jun 2008 16:43:00 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 13 Jun 2008 16:43:00 +0000 (UTC) Cc: emacs-devel@gnu.org To: Angelo Graziosi Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Jun 13 18:43:43 2008 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1K7CNI-00057Q-Rb for ged-emacs-devel@m.gmane.org; Fri, 13 Jun 2008 18:43:41 +0200 Original-Received: from localhost ([127.0.0.1]:46363 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1K7CMU-0003mo-HS for ged-emacs-devel@m.gmane.org; Fri, 13 Jun 2008 12:42:50 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1K7CJw-0002ls-5C for emacs-devel@gnu.org; Fri, 13 Jun 2008 12:40:12 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1K7CJv-0002l8-8v for emacs-devel@gnu.org; Fri, 13 Jun 2008 12:40:11 -0400 Original-Received: from [199.232.76.173] (port=38247 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1K7CJv-0002l2-35 for emacs-devel@gnu.org; Fri, 13 Jun 2008 12:40:11 -0400 Original-Received: from mtaout1.012.net.il ([84.95.2.1]:47561) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1K7CJu-0000sq-Ui for emacs-devel@gnu.org; Fri, 13 Jun 2008 12:40:11 -0400 Original-Received: from HOME-C4E4A596F7 ([84.228.241.111]) by i-mtaout1.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0K2E00KXJUYJLY30@i-mtaout1.012.net.il> for emacs-devel@gnu.org; Fri, 13 Jun 2008 19:54:20 +0300 (IDT) In-reply-to: <48529613.6020302@alice.it> X-012-Sender: halo1@inter.net.il X-detected-kernel: by monty-python.gnu.org: Solaris 9.1 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:99123 Archived-At: > Date: Fri, 13 Jun 2008 17:45:23 +0200 > From: Angelo Graziosi > CC: emacs-devel@gnu.org > > > Also, I think the two new threads above are spawned to handle the > > signal. Maybe you can set a breakpoint in open_stackdumpfile, and > > then, when that breakpoint is hit, see where the main thread caught > > the signal. > > Where is open_stackdumpfile? I think it belongs to Cygwin sources... So? You can put a breakpoint on a function even if its sources are not available. The idea was to stop Emacs when it is about to dump core, and then see what happens in the application thread. > >> GNU gdb 6.8.0.20080328-cvs (cygwin-special) > > > > If the above doesn't help, perhaps try using a stable release of GDB > > instead of a CVS snapshot, to avoid being hit by some regression > > introduced into the development code. > > That is the official version which comes with Cygwin, not my choose... Sigh.