From: Stefan Kangas <stefan@marxist.se>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "Mark A. Hershberger" <mah@everybody.org>, 33091@debbugs.gnu.org
Subject: bug#33091: 27.0.50; Daily+ crashes in auto-save-hook
Date: Fri, 21 Aug 2020 00:47:58 -0700 [thread overview]
Message-ID: <CADwFkmnqiJcLRqipHy8MYc_YsJ+51A8+gMhDwtLtCQFoRXX54w@mail.gmail.com> (raw)
In-Reply-To: <834ldiqwkt.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 19 Oct 2018 09:28:34 +0300")
Hi Mark,
Eli Zaretskii <eliz@gnu.org> writes:
>> From: "Mark A. Hershberger" <mah@everybody.org>
>> Cc: 33091@debbugs.gnu.org
>> Date: Thu, 18 Oct 2018 16:15:51 -0400
>>
>> Eli Zaretskii <eliz@gnu.org> writes:
>>
>> > IOW, GC segfaults, and then Emacs tries to auto-save the session,
>> > which fails.
>> >
>> > Is it possible that GC hits a stack overflow? Can you try manually
>> > establishing whether that is the case by doing what stack_overflow in
>> > sysdep.c does?
>>
>> I don't know how to do this. I can follow directions if you can tell me
>> what to do, though.
>
> Given the backtrace you show in your report, I believe the commands
> below should do that:
>
> (gdb) frame 13
> (gdb) p/x siginfo->si_addr
> (gdb) p/x stack_bottom
> (gdb) p/x current_thread->stack_top
>
> Stack frame #13 is inside handle_sigsegv, according to your backtrace.
It seems like we need more information from you to make any progress
here. Did you have a chance to look into this?
Thanks.
Best regards,
Stefan Kangas
next prev parent reply other threads:[~2020-08-21 7:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-18 18:56 bug#33091: 27.0.50; Daily+ crashes in auto-save-hook Mark A. Hershberger
2018-10-18 20:09 ` Eli Zaretskii
2018-10-18 20:15 ` Mark A. Hershberger
2018-10-19 6:28 ` Eli Zaretskii
2020-08-21 7:47 ` Stefan Kangas [this message]
2020-08-21 14:54 ` Mark A. Hershberger
2020-08-21 17:00 ` Stefan Kangas
2020-08-21 17:09 ` Mark A. Hershberger
2020-10-01 12:38 ` Stefan Kangas
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CADwFkmnqiJcLRqipHy8MYc_YsJ+51A8+gMhDwtLtCQFoRXX54w@mail.gmail.com \
--to=stefan@marxist.se \
--cc=33091@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=mah@everybody.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.