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: Fri, 13 Jun 2008 19:39:16 +0300	[thread overview]
Message-ID: <uej71cmrv.fsf@gnu.org> (raw)
In-Reply-To: <48529613.6020302@alice.it>

> Date: Fri, 13 Jun 2008 17:45:23 +0200
> From: Angelo Graziosi <angelo.graziosi@alice.it>
> 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.




  reply	other threads:[~2008-06-13 16:39 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 [this message]
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
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=uej71cmrv.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).