unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Angelo Graziosi <angelo.graziosi@alice.it>
Cc: emacs-devel@gnu.org
Subject: Re: Stak dump with tar.[bz2/gz] files (Cygwin)
Date: Sun, 15 Jun 2008 06:29:45 +0300	[thread overview]
Message-ID: <ubq23l6ja.fsf@gnu.org> (raw)
In-Reply-To: <4854708F.20508@alice.it>

> Date: Sun, 15 Jun 2008 03:29:51 +0200
> From: Angelo Graziosi <angelo.graziosi@alice.it>
> CC: emacs-devel@gnu.org
> 
> (gdb) run -Q
> Starting program: /usr/local/emacs/bin/emacs.exe -Q
> [New thread 3956.0xda8]
> [New thread 3956.0xadc]
> [New thread 3956.0x478]
> [New thread 3956.0xedc]
> [New thread 3956.0x178]
> [New thread 3956.0xf80]
> [New thread 3956.0x9f4]
> [New thread 3956.0xde8]
> [New thread 3956.0x1a0]
> [Switching to thread 3956.0xadc]
> 
> Breakpoint 1, 0x61016416 in open_stackdumpfile () from /usr/bin/cygwin1.dll
> 
> 
> 
> C-x C-f hello1.tar.bz2
> Parsing tar file...done
> 
> here Emacs hangs? The portion of overlapped window isn't redisplayed...
> 
> 
> 
> (gdb) c
> Continuing.
>        3 [sig] emacs 3956 open_stackdumpfile: Dumping stack trace to 
> emacs.exe.stackdump
> 
> Program exited with code 0103000.
> (gdb)
> 
> 
> As alternative:
> 
> [...]
> an alternative
> 
> [Switching to thread 3692.0xc0c]
> 
> Breakpoint 1, 0x61016416 in open_stackdumpfile () from /usr/bin/cygwin1.dll
> (gdb) bt
> #0  0x61016416 in open_stackdumpfile () from /usr/bin/cygwin1.dll
> #1  0x6101669e in stackdump () from /usr/bin/cygwin1.dll
> #2  0x61017fd5 in _cygtls::signal_exit () from /usr/bin/cygwin1.dll
> #3  0x61018638 in sigpacket::process () from /usr/bin/cygwin1.dll
> #4  0x61099f57 in wait_sig () from /usr/bin/cygwin1.dll
> #5  0x61002f32 in cygthread::callfunc () from /usr/bin/cygwin1.dll
> #6  0x61003769 in cygthread::stub () from /usr/bin/cygwin1.dll
> #7  0x00001074 in ?? ()
> #8  0x00000000 in ?? ()

This backtrace is in the wrong thread.  You need to switch to the
thread that runs the main Emacs code, I'm guessing that's the 1st or
the second of the threads announced after "run -Q" above.  The command
"info threads" should tell you more about each thread.




  reply	other threads:[~2008-06-15  3:29 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-12 12:37 Stak dump with tar.[bz2/gz] files (Cygwin) Angelo Graziosi
2008-06-12 16:05 ` Stefan Monnier
2008-06-12 20:00   ` Angelo Graziosi
2008-06-12 21:34     ` Stefan Monnier
2008-06-12 21:56       ` Angelo Graziosi
2008-06-13  1:42         ` Stefan Monnier
2008-06-13  6:46         ` Eli Zaretskii
2008-06-13 15:53           ` Angelo Graziosi
2008-06-13 16:41             ` Eli Zaretskii
2008-06-13  6:36     ` Eli Zaretskii
2008-06-13 15:45       ` Angelo Graziosi
2008-06-13 16:39         ` Eli Zaretskii
2008-06-13 23:29           ` Angelo Graziosi
2008-06-14 10:41             ` Eli Zaretskii
2008-06-15  1:29       ` Angelo Graziosi
2008-06-15  3:29         ` Eli Zaretskii [this message]
2008-06-15 12:50           ` Angelo Graziosi
2008-06-15 18:05             ` Eli Zaretskii
2008-06-15 21:45               ` Angelo Graziosi
2008-06-16 18:12                 ` Eli Zaretskii
2008-06-16 20:41                   ` Angelo Graziosi
2008-06-17  3:06                     ` Eli Zaretskii
2008-06-17  8:23                       ` Angelo Graziosi
2008-12-23 19:45 ` Angelo Graziosi
2008-12-23 19:51 ` Angelo Graziosi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ubq23l6ja.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=angelo.graziosi@alice.it \
    --cc=emacs-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).