From: Lars Ingebrigtsen <larsi@gnus.org>
To: Dmitry Antipov <dmantipov@yandex.ru>
Cc: 16603@debbugs.gnu.org
Subject: bug#16603: 24.3.50; Segfault when viewing a backtrace
Date: Sun, 09 Feb 2014 22:37:12 -0800 [thread overview]
Message-ID: <8761on5v8n.fsf@building.gnus.org> (raw)
In-Reply-To: <52F8711E.7070602@yandex.ru> (Dmitry Antipov's message of "Mon, 10 Feb 2014 10:26:38 +0400")
Dmitry Antipov <dmantipov@yandex.ru> writes:
> On 02/08/2014 05:23 AM, Lars Ingebrigtsen wrote:
>
>> If you select Rotem's article three times (jumping out of the backtrace
>> the first two times), Emacs will segfault the third time. It seems to
>> be totally reproducible for me.
>
> I have the varying results, but no crash. Can you provide an exact
> key/command sequence causing the crash? And, of course, do you start
> from 'emacs -Q'?
Yup.
I do
(require 'gnus-group)
(setq debug-on-error t)
(gnus-read-ephemeral-emacs-bug-group 16577)
select Rotem's article, `q' out of the backtrace, `g' Rotem's article,
and I either get a segfault then, or after repeating this a couple of
times.
This is on 64-bit Fedora 19, if that's likely to make a difference...
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog http://lars.ingebrigtsen.no/
next prev parent reply other threads:[~2014-02-10 6:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-31 2:20 bug#16603: 24.3.50; Segfault when viewing a backtrace Lars Ingebrigtsen
2014-01-31 7:03 ` Dmitry Antipov
2014-01-31 8:10 ` Eli Zaretskii
2014-01-31 8:11 ` Lars Ingebrigtsen
2014-01-31 8:37 ` Eli Zaretskii
2014-02-07 3:44 ` Lars Ingebrigtsen
2014-02-07 3:50 ` Lars Ingebrigtsen
2014-02-07 5:48 ` Dmitry Antipov
2014-02-08 1:23 ` Lars Ingebrigtsen
2014-02-10 6:26 ` Dmitry Antipov
2014-02-10 6:37 ` Lars Ingebrigtsen [this message]
2014-02-10 9:30 ` Dmitry Antipov
2014-02-10 9:32 ` Lars Ingebrigtsen
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=8761on5v8n.fsf@building.gnus.org \
--to=larsi@gnus.org \
--cc=16603@debbugs.gnu.org \
--cc=dmantipov@yandex.ru \
/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).