From: Eli Zaretskii <eliz@gnu.org>
To: Ivan Kanis <ivan.kanis@googlemail.com>
Cc: 10582@debbugs.gnu.org
Subject: bug#10582: quiting erc causes crash
Date: Fri, 23 Mar 2012 17:36:14 +0200 [thread overview]
Message-ID: <83haxfuy6p.fsf@gnu.org> (raw)
In-Reply-To: <87k42bpe8t.fsf@googlemail.com>
> From: Ivan Kanis <ivan.kanis@googlemail.com>
> Cc: 10582@debbugs.gnu.org
> Date: Fri, 23 Mar 2012 15:45:54 +0100
>
> > Note that I removed emacs-devel from the CC list: there's no need to
> > discuss bug reports on that list, it just confuses people and the bug
> > tracker.
>
> OK, who am I supposed to talk to when a bug is left alone?
You send a ping to the bug address. It will be automatically
reflected to the bug-gnu-emacs mailing list, to which all Emacs
maintainers and developers subscribe.
> > Also, please start GDB from the Emacs's src/ directory, so that the
> > backtrace includes the Lisp-level backtrace, and also some very
> > helpful commands are available for displaying Lisp data types.
>
> I do that already.
Including the last time it crashed? If so, how come there was no Lisp
backtrace at the end of the C-level backtrace you sent?
next prev parent reply other threads:[~2012-03-23 15:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-22 22:07 bug#10582: 24.0.92; quiting erc causes crash Ivan Kanis
[not found] ` <handler.10582.B.13272700691126.ack@debbugs.gnu.org>
2012-01-26 8:06 ` bug#10582: Acknowledgement (24.0.92; quiting erc causes crash) Ivan Kanis
2012-02-03 18:09 ` Ivan Kanis
2012-03-23 9:03 ` bug#10582: quiting erc causes crash Ivan Kanis
[not found] ` <87398zaduh.fsf_-_@kanis.fr>
2012-03-23 10:08 ` Eli Zaretskii
2012-03-23 14:45 ` Ivan Kanis
2012-03-23 15:36 ` Eli Zaretskii [this message]
2012-04-01 10:41 ` bug#10582: better backtrace Ivan Kanis
2012-04-01 16:19 ` Eli Zaretskii
2012-04-01 16:57 ` Ivan Kanis
2012-04-01 17:02 ` Eli Zaretskii
2012-04-01 20:13 ` Troels Nielsen
2012-04-03 17:58 ` Ivan Kanis
2012-04-27 6:22 ` Ivan Kanis
2012-10-07 1:53 ` Glenn Morris
2012-10-07 9:58 ` Ivan Kanis
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=83haxfuy6p.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=10582@debbugs.gnu.org \
--cc=ivan.kanis@googlemail.com \
/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).