unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Peter Dyballa <Peter_Dyballa@Web.DE>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 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: Thu, 17 May 2018 01:22:15 +0200	[thread overview]
Message-ID: <34552DF5-61C4-4DE1-8E7A-CA09B1E4473A@Web.DE> (raw)
In-Reply-To: <83po1wjprz.fsf@gnu.org>



> Am 16.5.2018 um 04:30 schrieb Eli Zaretskii <eliz@gnu.org>:
> 
> So the next question is: which software resets the LC_NUMERIC setting?
> Perhaps by running Emacs under a debugger with a breakpoint on
> set_locale could answer that question.

A few problems here… The newly built debugger (macOS High Sierra, version 10.13, obviously comes without one) needs to be "codesigned". This does not work here as in theory, practically. Maybe I need to reboot, disable that "gatekeeper" completely, or whatever. Is maybe root allowed to use GDB instantly?

The easiest step was to build two Emacsen with different levels of debug information.

BTW, GDB and I cannot find the text set_locale, except here:

../src/xterm.c:        /* gtk_init does set_locale.  Fix locale before and after.  */

I am using the athena variant with Xaw3d.

--
Greetings

  Pete      <\
             _\     O  _
            |o \  _\\_/-\='
_____________(_)|-(_)  (_)___________________________________






  reply	other threads:[~2018-05-16 23:22 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
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 [this message]
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=34552DF5-61C4-4DE1-8E7A-CA09B1E4473A@Web.DE \
    --to=peter_dyballa@web.de \
    --cc=30788@debbugs.gnu.org \
    --cc=eliz@gnu.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).