From: Rasmus <rasmus@gmx.us>
To: Tassilo Horn <tassilo@member.fsf.org>
Cc: emacs-devel@gnu.org
Subject: Re: gtk3, emacs 24 and gnome shell
Date: Thu, 27 Oct 2011 21:46:02 +0100 [thread overview]
Message-ID: <8762jaqi2d.fsf@gmail.com> (raw)
In-Reply-To: <87hb2x5u7g.fsf@thinkpad.tsdh.de> (Tassilo Horn's message of "Tue, 25 Oct 2011 10:52:35 +0200")
Tassilo Horn <tassilo@member.fsf.org> writes:
> Rasmus <rasmus@gmx.us> writes:
>
>> Is there a way to have Emacs always log itself?
>
> Run it in gdb. Compile it without optimizations and -ggdb in CFLAGS and
> then run it like so:
>
> $ cd path/to/emacs/src/
> $ gdb emacs
> gdb> run
>
> Then you'll get C and lisp backtraces when emacs crashes. (It's
> important to start emacs from its src directory, because that contains
> some GDB setup scripts.)
I run the program using gdb etc. as suggested above, but no message is
echoed upon a crash. Do I have to issue some command to get a
backtrace?
Thanks,
Rasmus
--
Sent from my Emacs
next prev parent reply other threads:[~2011-10-27 20:46 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-24 12:06 gtk3, emacs 24 and gnome shell Andrea Crotti
2011-10-24 13:51 ` Tassilo Horn
2011-10-24 14:23 ` Andrea Crotti
2011-10-24 15:34 ` Tassilo Horn
2011-10-24 23:19 ` Rasmus
2011-10-25 4:30 ` Chong Yidong
2011-10-25 7:06 ` Tassilo Horn
2011-10-25 8:23 ` Rasmus
2011-10-25 8:52 ` Tassilo Horn
2011-10-27 20:46 ` Rasmus [this message]
2011-10-27 22:01 ` Paul Eggert
2011-10-28 6:18 ` Tassilo Horn
2011-10-28 6:58 ` Eli Zaretskii
2011-10-28 18:21 ` Rasmus Pank Roulund
2011-10-28 23:30 ` Michael Welsh Duggan
2011-10-29 8:55 ` Eli Zaretskii
2011-10-29 15:45 ` Michael Welsh Duggan
2011-10-29 15:54 ` Michael Welsh Duggan
2011-11-03 4:42 ` Chris Moore
2011-11-03 1:08 ` Rasmus
2011-11-03 3:59 ` Eli Zaretskii
2011-11-04 1:02 ` Rasmus
2011-11-03 1:08 ` Rasmus
-- strict thread matches above, loose matches on Subject: below --
2011-12-13 21:00 Benjamin Redelings
2011-12-14 7:07 ` Jan D.
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=8762jaqi2d.fsf@gmail.com \
--to=rasmus@gmx.us \
--cc=emacs-devel@gnu.org \
--cc=tassilo@member.fsf.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).