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

Eli Zaretskii ha scritto:
> 
> 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.  

Hot to switch?


> The command
> "info threads" should tell you more about each thread.

$ gdb /usr/local/emacs/bin/emacs.exe
GNU gdb 6.8.0.20080328-cvs (cygwin-special)
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
<http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-pc-cygwin"...
(gdb) break open_stackdumpfile
Function "open_stackdumpfile" not defined.
Make breakpoint pending on future shared library load? (y or [n]) y

Breakpoint 1 (open_stackdumpfile) pending.
(gdb) run -Q
Starting program: /usr/local/emacs/bin/emacs.exe -Q
[New thread 2100.0x204]
[New thread 2100.0x250]
[New thread 2100.0xb30]
[New thread 2100.0xe48]
[New thread 2100.0xe28]
[New thread 2100.0xcf0]
[New thread 2100.0x454]
[New thread 2100.0xaa8]
[New thread 2100.0xe10]
[Switching to thread 2100.0x250]

Breakpoint 1, 0x61016416 in open_stackdumpfile () from /usr/bin/cygwin1.dll
(gdb) info threads
   9 thread 2100.0xe10  0x7c91e4f4 in ntdll!LdrAccessResource ()
    from /c/WINDOWS/system32/ntdll.dll
   8 thread 2100.0xaa8  0x7c91e4f4 in ntdll!LdrAccessResource ()
    from /c/WINDOWS/system32/ntdll.dll
   7 thread 2100.0x454  0x7c91e4f4 in ntdll!LdrAccessResource ()
    from /c/WINDOWS/system32/ntdll.dll
   6 thread 2100.0xcf0  0x7c91e4f4 in ntdll!LdrAccessResource ()
    from /c/WINDOWS/system32/ntdll.dll
   5 thread 2100.0xe28  0x7c91e4f4 in ntdll!LdrAccessResource ()
    from /c/WINDOWS/system32/ntdll.dll
   4 thread 2100.0xe48  0x7c91e4f4 in ntdll!LdrAccessResource ()
    from /c/WINDOWS/system32/ntdll.dll
   3 thread 2100.0xb30  0x7c91e4f4 in ntdll!LdrAccessResource ()
    from /c/WINDOWS/system32/ntdll.dll
* 2 thread 2100.0x250  0x61016416 in open_stackdumpfile ()
    from /usr/bin/cygwin1.dll
   1 thread 2100.0x204  0x7c91e4f4 in ntdll!LdrAccessResource ()
    from /c/WINDOWS/system32/ntdll.dll
(gdb) c
Continuing.
       3 [sig] emacs 2100 open_stackdumpfile: Dumping stack trace to 
emacs.exe.stackdump

Program exited with code 0103000.
(gdb)


    Angelo.




  reply	other threads:[~2008-06-15 12:50 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
2008-06-15 12:50           ` Angelo Graziosi [this message]
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=48551002.7020600@alice.it \
    --to=angelo.graziosi@alice.it \
    --cc=eliz@gnu.org \
    --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).