From: Eli Zaretskii <eliz@gnu.org>
To: Mats Lidell <mats.lidell@cag.se>
Cc: ulm@gentoo.org, 30788@debbugs.gnu.org
Subject: bug#30788: 27.0.50; Getting 'char-displayable-p: Invalid hash table rehash size: 1.0' when starting emacs -Q
Date: Tue, 13 Mar 2018 20:08:15 +0200 [thread overview]
Message-ID: <83o9jrrgq8.fsf@gnu.org> (raw)
In-Reply-To: <873713an3w.fsf@mail.contactor.se> (message from Mats Lidell on Tue, 13 Mar 2018 18:42:27 +0100)
> From: Mats Lidell <mats.lidell@cag.se>
> Cc: Ulrich Mueller <ulm@gentoo.org>, <30788@debbugs.gnu.org>
> Date: Tue, 13 Mar 2018 18:42:27 +0100
>
> > Eli Zaretskii writes:
> > > Date: Tue, 13 Mar 2018 11:14:18 +0100
> > > From: Ulrich Mueller <ulm@gentoo.org>
> > >
> > > Downstream bug: https://bugs.gentoo.org/650332
> >
> > Can someone who can reproduce this please post a backtrace?
>
> I'm sorry Eli, I'm afraid I can't do that! (Or setting the pun aside lack the
> skills or have a too broken emacs ...) Please advice what I should do.
Start Emacs under GDB, put a breakpoint in Fmake_hash_table, where it
signals this error (line 4530 of fns.c in today's master), then run
Emacs with "run -Q", and when the breakpoint breaks, type "xbacktrace"
at the GDB prompt, and post the results here.
(If "xbacktrace" doesn't work, type "source /path/to/src/.gdbinit" and
try again.)
TIA
next prev parent reply other threads:[~2018-03-13 18:08 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-12 22:12 bug#30788: 27.0.50; Getting 'char-displayable-p: Invalid hash table rehash size: 1.0' when starting emacs -Q Mats Lidell
2018-03-13 3:44 ` Eli Zaretskii
2018-03-13 10:14 ` Ulrich Mueller
2018-03-13 16:14 ` Eli Zaretskii
2018-03-13 17:42 ` Mats Lidell
2018-03-13 18:08 ` Eli Zaretskii [this message]
2018-03-13 18:58 ` Ulrich Mueller
2018-03-13 19:07 ` Ulrich Mueller
2018-03-13 19:32 ` Eli Zaretskii
2018-03-13 20:06 ` Ulrich Mueller
2018-03-14 3:32 ` Eli Zaretskii
2018-03-14 6:48 ` Ulrich Mueller
2018-03-14 16:15 ` Eli Zaretskii
2018-03-14 17:57 ` Ulrich Mueller
2018-03-14 18:15 ` Eli Zaretskii
2018-03-14 21:19 ` Ulrich Mueller
2018-03-16 2:45 ` Noam Postavsky
2018-03-16 3:38 ` Eli Zaretskii
2018-03-13 21:26 ` Ulrich Mueller
2018-05-04 21:58 ` Peter Dyballa
2018-05-04 22:13 ` Glenn Morris
2018-05-05 8:06 ` Peter Dyballa
2018-05-15 14:02 ` Peter Dyballa
2018-05-15 17:06 ` Eli Zaretskii
2018-05-15 21:38 ` Peter Dyballa
2018-05-16 2:30 ` Eli Zaretskii
2018-05-16 23:22 ` Peter Dyballa
2018-05-17 14:56 ` Eli Zaretskii
2018-05-19 11:21 ` Peter Dyballa
2018-05-19 11:45 ` Philipp Stephani
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=83o9jrrgq8.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=30788@debbugs.gnu.org \
--cc=mats.lidell@cag.se \
--cc=ulm@gentoo.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).