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 09:36:43 +0300 Message-ID: References: <48511871.1090203@alice.it> <4851806A.6070104@alice.it> Reply-To: Eli Zaretskii NNTP-Posting-Host: lo.gmane.org X-Trace: ger.gmane.org 1213339133 4769 80.91.229.12 (13 Jun 2008 06:38:53 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 13 Jun 2008 06:38:53 +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 08:39:37 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 1K72we-00032r-Bj for ged-emacs-devel@m.gmane.org; Fri, 13 Jun 2008 08:39:36 +0200 Original-Received: from localhost ([127.0.0.1]:48424 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1K72ua-0002zt-9t for ged-emacs-devel@m.gmane.org; Fri, 13 Jun 2008 02:37:24 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1K72uJ-0002w5-BA for emacs-devel@gnu.org; Fri, 13 Jun 2008 02:37:07 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1K72u2-0002rj-Uo for emacs-devel@gnu.org; Fri, 13 Jun 2008 02:37:06 -0400 Original-Received: from [199.232.76.173] (port=37620 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1K72u2-0002re-Qi for emacs-devel@gnu.org; Fri, 13 Jun 2008 02:36:50 -0400 Original-Received: from mtaout5.012.net.il ([84.95.2.13]:56827) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1K72u1-0007ad-TV for emacs-devel@gnu.org; Fri, 13 Jun 2008 02:36:50 -0400 Original-Received: from HOME-C4E4A596F7 ([80.230.28.131]) by i_mtaout5.012.net.il (HyperSendmail v2004.12) with ESMTPA id <0K2E009LH329T3I0@i_mtaout5.012.net.il> for emacs-devel@gnu.org; Fri, 13 Jun 2008 09:51:46 +0300 (IDT) In-reply-to: <4851806A.6070104@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:99067 Archived-At: > Date: Thu, 12 Jun 2008 22:00:42 +0200 > From: Angelo Graziosi > Cc: emacs-devel@gnu.org > > C-x C-f /tmp/hello1.tar.bz2 > > [New thread 4060.0xb8] > [New thread 4060.0x2fc] > 3 [sig] emacs 4060 open_stackdumpfile: Dumping stack trace to > emacs.exe.stackdump > > Program exited with code 0103000. This is not helpful. For some reason, GDB didn't catch the signal. (Is that "3" the signal number or something else?) Apart of asking on the Cygwin list what does this all mean, I'd suggest to do this, once you are inside GDB, but _before_ the "run -Q" command: (gdb) handle all print Beware: this will cause GDB to catch the SIGINT signal generated when you press C-g in Emacs, so try to avoid using C-g in this session. 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. > 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.