From: Eli Zaretskii <eliz@gnu.org>
To: Jean Louis <bugs@gnu.support>
Cc: stefankangas@gmail.com, 45159@debbugs.gnu.org
Subject: bug#45159: 28.0.50; crash when no space on disk
Date: Thu, 10 Dec 2020 20:18:43 +0200 [thread overview]
Message-ID: <835z594j98.fsf@gnu.org> (raw)
In-Reply-To: <X9JOIuwxTbz55VzO@protected.rcdrun.com> (message from Jean Louis on Thu, 10 Dec 2020 19:34:42 +0300)
> Date: Thu, 10 Dec 2020 19:34:42 +0300
> From: Jean Louis <bugs@gnu.support>
> Cc: 45159@debbugs.gnu.org
>
> > > Should I send xbacktrace?
> >
> > Yes, send the output of bt and xbacktrace.
>
> I hope that format in attachment makes sense. gdb failed, it got
> problem itself, and I could just save XTerm log.
>
> If it does not help I will do nexti.
>
> #9 0x00000000004f982e in timer_check () at keyboard.c:4403
> nexttime = <optimized out>
> timers = 0x1bceb43
> idle_timers = 0x5434ce3
> tem = <optimized out>
> #10 0x00000000004f9c39 in readable_events (flags=flags@entry=1) at keyboard.c:3405
> #11 0x00000000004fa688 in get_input_pending (flags=flags@entry=1) at keyboard.c:6795
> #12 0x00000000004fd658 in detect_input_pending_run_timers (do_display=do_display@entry=false)
> at keyboard.c:10350
> old_timers_run = <optimized out>
Thanks, but this is incomplete: frames below #9 are missing. They are
the most important ones, as they show where exactly Emacs crashes. If
you reproduce this at will, please show the first 9 frames.
next prev parent reply other threads:[~2020-12-10 18:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-10 13:01 bug#45159: 28.0.50; crash when no space on disk Jean Louis
2020-12-10 14:05 ` Stefan Kangas
2020-12-10 16:34 ` Jean Louis
2020-12-10 18:18 ` Eli Zaretskii [this message]
2020-12-10 14:23 ` Eli Zaretskii
2020-12-10 16:59 ` Jean Louis
2020-12-10 17:13 ` Eli Zaretskii
2020-12-10 21:23 ` Jean Louis
2020-12-11 8:12 ` Eli Zaretskii
2020-12-12 1:36 ` Jean Louis
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=835z594j98.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=45159@debbugs.gnu.org \
--cc=bugs@gnu.support \
--cc=stefankangas@gmail.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).