GNU bug report logs - #62571
30.0.50; Crash on entering 20x enlarged number

Previous Next

Package: emacs;

Reported by: Jean Louis <bugs <at> gnu.support>

Date: Fri, 31 Mar 2023 17:26:02 UTC

Severity: normal

Tags: moreinfo

Found in version 30.0.50

Done: Stefan Kangas <stefankangas <at> gmail.com>

Bug is archived. No further changes may be made.

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 62571 in the body.
You can then email your comments to 62571 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to bug-gnu-emacs <at> gnu.org:
bug#62571; Package emacs. (Fri, 31 Mar 2023 17:26:02 GMT) Full text and rfc822 format available.

Acknowledgement sent to Jean Louis <bugs <at> gnu.support>:
New bug report received and forwarded. Copy sent to bug-gnu-emacs <at> gnu.org. (Fri, 31 Mar 2023 17:26:02 GMT) Full text and rfc822 format available.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Jean Louis <bugs <at> gnu.support>
To: bug-gnu-emacs <at> gnu.org
Subject: 30.0.50; Crash on entering 20x enlarged number
Date: Fri, 31 Mar 2023 20:23:31 +0300
Here is how to reproduce:

1. emacs -Q
2. C-x + and repeat pressing + for 20 times in total
3. I press 6, as I wanted to show to child how number 6 looks like
4. X Server crashed, I guess Emacs too, I have no idea

I did not test it with other numbers but 6, but it can easily be that X
Window server will crash with letters as well.

It is very repeatable. I am using Lucid built. Font used by default is
here below, if that matter.

             position: 5 of 145 (3%), column: 4
            character: h (displayed as h) (codepoint 104, #o150, #x68)
              charset: ascii (ASCII (ISO646 IRV))
code point in charset: 0x68
               script: latin
               syntax: w 	which means: word
             category: .:Base, L:Strong L2R, a:ASCII, l:Latin, r:Roman
             to input: type "C-x 8 RET 68" or "C-x 8 RET LATIN SMALL LETTER H"
          buffer code: #x68
            file code: #x68 (encoded by coding system utf-8-unix)
              display: by this font (glyph code):
    ftcrhb:-ADBO-Source Code Pro-regular-normal-normal-*-17-*-*-*-m-0-iso10646-1 (#x23)

Character code properties: customize what to show
  name: LATIN SMALL LETTER H
  general-category: Ll (Letter, Lowercase)
  decomposition: (104) ('h')

There are text properties here:
  face                 font-lock-comment-face
  fontified            t




In GNU Emacs 30.0.50 (build 9, x86_64-pc-linux-gnu, X toolkit, cairo
 version 1.17.6, Xaw3d scroll bars) of 2023-02-23 built on
 protected.rcdrun.com
Repository revision: 6411a9af03a4eb1a82db47a9642b11ba7edaaaf0
Repository branch: master
Windowing system distributor 'The X.Org Foundation', version 11.0.12101006
System Description: Parabola GNU/Linux-libre

Configured using:
 'configure --with-x-toolkit=lucid --with-mailutils'

Configured features:
ACL CAIRO DBUS FREETYPE GIF GLIB GMP GNUTLS GPM GSETTINGS HARFBUZZ JPEG
JSON LCMS2 LIBOTF LIBSYSTEMD LIBXML2 M17N_FLT MODULES NOTIFY INOTIFY
PDUMPER PNG RSVG SECCOMP SOUND SQLITE3 THREADS TIFF TOOLKIT_SCROLL_BARS
TREE_SITTER WEBP X11 XAW3D XDBE XIM XINPUT2 XPM LUCID ZLIB

Important settings:
  value of $LC_ALL: en_US.UTF-8
  value of $LANG: de_DE.UTF-8
  value of $XMODIFIERS: @im=exwm-xim
  locale-coding-system: utf-8-unix

Major mode: Lisp Interaction

Minor modes in effect:
  tooltip-mode: t
  global-eldoc-mode: t
  eldoc-mode: t
  show-paren-mode: t
  electric-indent-mode: t
  mouse-wheel-mode: t
  tool-bar-mode: t
  menu-bar-mode: t
  file-name-shadow-mode: t
  global-font-lock-mode: t
  font-lock-mode: t
  blink-cursor-mode: t
  line-number-mode: t
  indent-tabs-mode: t
  transient-mark-mode: t
  auto-composition-mode: t
  auto-encryption-mode: t
  auto-compression-mode: t

Load-path shadows:
None found.

Features:
(shadow sort mail-extr emacsbug message mailcap yank-media puny dired
dired-loaddefs rfc822 mml mml-sec password-cache epa derived epg rfc6068
epg-config gnus-util text-property-search time-date subr-x mm-decode
mm-bodies mm-encode mail-parse rfc2231 mailabbrev gmm-utils mailheader
cl-loaddefs cl-lib sendmail rfc2047 rfc2045 ietf-drums mm-util
mail-prsvr mail-utils rmc iso-transl tooltip cconv eldoc paren electric
uniquify ediff-hook vc-hooks lisp-float-type elisp-mode mwheel
term/x-win x-win term/common-win x-dnd tool-bar dnd fontset image
regexp-opt fringe tabulated-list replace newcomment text-mode lisp-mode
prog-mode register page tab-bar menu-bar rfn-eshadow isearch easymenu
timer select scroll-bar mouse jit-lock font-lock syntax font-core
term/tty-colors frame minibuffer nadvice seq simple cl-generic
indonesian philippine cham georgian utf-8-lang misc-lang vietnamese
tibetan thai tai-viet lao korean japanese eucjp-ms cp51932 hebrew greek
romanian slovak czech european ethiopic indian cyrillic chinese
composite emoji-zwj charscript charprop case-table epa-hook
jka-cmpr-hook help abbrev obarray oclosure cl-preloaded button loaddefs
theme-loaddefs faces cus-face macroexp files window text-properties
overlay sha1 md5 base64 format env code-pages mule custom widget keymap
hashtable-print-readable backquote threads dbusbind inotify lcms2
dynamic-setting system-font-setting font-render-setting cairo x-toolkit
xinput2 x multi-tty make-network-process emacs)

Memory information:
((conses 16 39119 7869)
 (symbols 48 5219 2)
 (strings 32 14185 1749)
 (string-bytes 1 397783)
 (vectors 16 10442)
 (vector-slots 8 158960 13134)
 (floats 8 40 19)
 (intervals 56 255 0)
 (buffers 984 11))

-- 
Jean

Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns

In support of Richard M. Stallman
https://stallmansupport.org/




Information forwarded to bug-gnu-emacs <at> gnu.org:
bug#62571; Package emacs. (Fri, 31 Mar 2023 18:08:01 GMT) Full text and rfc822 format available.

Message #8 received at 62571 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Jean Louis <bugs <at> gnu.support>
Cc: 62571 <at> debbugs.gnu.org
Subject: Re: bug#62571: 30.0.50; Crash on entering 20x enlarged number
Date: Fri, 31 Mar 2023 21:07:09 +0300
> From: Jean Louis <bugs <at> gnu.support>
> Date: Fri, 31 Mar 2023 20:23:31 +0300
> 
> 1. emacs -Q
> 2. C-x + and repeat pressing + for 20 times in total
> 3. I press 6, as I wanted to show to child how number 6 looks like
> 4. X Server crashed, I guess Emacs too, I have no idea

It doesn't crash here, but I'm not on X.

A backtrace in GDB would perhaps help understand what is going on.




Information forwarded to bug-gnu-emacs <at> gnu.org:
bug#62571; Package emacs. (Sat, 01 Apr 2023 00:44:02 GMT) Full text and rfc822 format available.

Message #11 received at 62571 <at> debbugs.gnu.org (full text, mbox):

From: Po Lu <luangruo <at> yahoo.com>
To: Jean Louis <bugs <at> gnu.support>
Cc: 62571 <at> debbugs.gnu.org
Subject: Re: bug#62571: 30.0.50; Crash on entering 20x enlarged number
Date: Sat, 01 Apr 2023 08:42:42 +0800
Jean Louis <bugs <at> gnu.support> writes:

> Here is how to reproduce:
>
> 1. emacs -Q
> 2. C-x + and repeat pressing + for 20 times in total
> 3. I press 6, as I wanted to show to child how number 6 looks like
> 4. X Server crashed, I guess Emacs too, I have no idea
>
> I did not test it with other numbers but 6, but it can easily be that X
> Window server will crash with letters as well.
>
> It is very repeatable. I am using Lucid built. Font used by default is
> here below, if that matter.
> Windowing system distributor 'The X.Org Foundation', version 11.0.12101006

Xorg should print its crashes to a log typically at /var/log/Xorg.N.log,
where N is the number of your display.

Such a crash message should contain its backtrace on GNU/Linux systems,
for example:

[ 14866.219] 
Backtrace:
[ 14866.219] 0: /usr/bin/X (xorg_backtrace+0x3b) [0x80b190b]
[ 14866.219] 1: /usr/bin/X (0x8048000+0x6202d) [0x80aa02d]
[ 14866.219] 2: (vdso) (__kernel_rt_sigreturn+0x0) [0xb789140c]
[ 14866.219] 16: /usr/bin/X (WriteToClient+0x15e) [0x80aac6e]
[ 14866.219] 17: /usr/bin/X (WriteEventsToClient+0x2be) [0x80929ae]
[ 14866.219] 18: /usr/bin/X (TryClientEvents+0xe2) [0x8095462]
[ 14866.219] 19: /usr/bin/X (DeliverEventsToWindow+0x390) [0x8098450]
[ 14866.219] 20: /usr/bin/X (DeliverEvents+0xf8) [0x8099018]
[ 14866.219] 21: /usr/bin/X (DeleteWindow+0x203) [0x8076b43]
[ 14866.219] 22: /usr/bin/X (FreeClientResources+0xed) [0x806389d]
[ 14866.219] 23: /usr/bin/X (CloseDownClient+0x69) [0x80659e9]
[ 14866.219] 24: /usr/bin/X (CheckConnections+0x137) [0x80a8987]
[ 14866.219] 25: /usr/bin/X (WaitForSomething+0x98c) [0x80a33ac]
[ 14866.220] 26: /usr/bin/X (0x8048000+0x2261e) [0x806a61e]
[ 14866.220] 27: /usr/bin/X (0x8048000+0x1a5ba) [0x80625ba]
[ 14866.220] 28: /lib/libc.so.6 (__libc_start_main+0xe7) [0xb75b5ce7]
[ 14866.220] 29: /usr/bin/X (0x8048000+0x1a191) [0x8062191]
[ 14866.220] Segmentation fault at address 0x1
[ 14866.220] 
Caught signal 11 (Segmentation fault). Server aborting

Typically, the DDX symbols printed are enough to give us an idea of what
has gone wrong.  Would you please try to obtain such a backtrace from
your X server crash?




Added tag(s) moreinfo. Request was from Stefan Kangas <stefankangas <at> gmail.com> to control <at> debbugs.gnu.org. (Mon, 04 Sep 2023 08:42:01 GMT) Full text and rfc822 format available.

Information forwarded to bug-gnu-emacs <at> gnu.org:
bug#62571; Package emacs. (Mon, 11 Sep 2023 23:56:02 GMT) Full text and rfc822 format available.

Message #16 received at 62571 <at> debbugs.gnu.org (full text, mbox):

From: Stefan Kangas <stefankangas <at> gmail.com>
To: Po Lu <luangruo <at> yahoo.com>
Cc: 62571 <at> debbugs.gnu.org, Jean Louis <bugs <at> gnu.support>
Subject: Re: bug#62571: 30.0.50; Crash on entering 20x enlarged number
Date: Mon, 11 Sep 2023 16:55:46 -0700
Po Lu <luangruo <at> yahoo.com> writes:

> Jean Louis <bugs <at> gnu.support> writes:
>
>> Here is how to reproduce:
>>
>> 1. emacs -Q
>> 2. C-x + and repeat pressing + for 20 times in total
>> 3. I press 6, as I wanted to show to child how number 6 looks like
>> 4. X Server crashed, I guess Emacs too, I have no idea
>>
>> I did not test it with other numbers but 6, but it can easily be that X
>> Window server will crash with letters as well.
>>
>> It is very repeatable. I am using Lucid built. Font used by default is
>> here below, if that matter.
>> Windowing system distributor 'The X.Org Foundation', version 11.0.12101006
>
> Xorg should print its crashes to a log typically at /var/log/Xorg.N.log,
> where N is the number of your display.
>
> Such a crash message should contain its backtrace on GNU/Linux systems,
> for example:
>
> [ 14866.219]
> Backtrace:
> [ 14866.219] 0: /usr/bin/X (xorg_backtrace+0x3b) [0x80b190b]
> [ 14866.219] 1: /usr/bin/X (0x8048000+0x6202d) [0x80aa02d]
> [ 14866.219] 2: (vdso) (__kernel_rt_sigreturn+0x0) [0xb789140c]
> [ 14866.219] 16: /usr/bin/X (WriteToClient+0x15e) [0x80aac6e]
> [ 14866.219] 17: /usr/bin/X (WriteEventsToClient+0x2be) [0x80929ae]
> [ 14866.219] 18: /usr/bin/X (TryClientEvents+0xe2) [0x8095462]
> [ 14866.219] 19: /usr/bin/X (DeliverEventsToWindow+0x390) [0x8098450]
> [ 14866.219] 20: /usr/bin/X (DeliverEvents+0xf8) [0x8099018]
> [ 14866.219] 21: /usr/bin/X (DeleteWindow+0x203) [0x8076b43]
> [ 14866.219] 22: /usr/bin/X (FreeClientResources+0xed) [0x806389d]
> [ 14866.219] 23: /usr/bin/X (CloseDownClient+0x69) [0x80659e9]
> [ 14866.219] 24: /usr/bin/X (CheckConnections+0x137) [0x80a8987]
> [ 14866.219] 25: /usr/bin/X (WaitForSomething+0x98c) [0x80a33ac]
> [ 14866.220] 26: /usr/bin/X (0x8048000+0x2261e) [0x806a61e]
> [ 14866.220] 27: /usr/bin/X (0x8048000+0x1a5ba) [0x80625ba]
> [ 14866.220] 28: /lib/libc.so.6 (__libc_start_main+0xe7) [0xb75b5ce7]
> [ 14866.220] 29: /usr/bin/X (0x8048000+0x1a191) [0x8062191]
> [ 14866.220] Segmentation fault at address 0x1
> [ 14866.220]
> Caught signal 11 (Segmentation fault). Server aborting
>
> Typically, the DDX symbols printed are enough to give us an idea of what
> has gone wrong.  Would you please try to obtain such a backtrace from
> your X server crash?

Ping.  Could you please try obtaining a backtrace?




Reply sent to Stefan Kangas <stefankangas <at> gmail.com>:
You have taken responsibility. (Mon, 23 Oct 2023 20:12:02 GMT) Full text and rfc822 format available.

Notification sent to Jean Louis <bugs <at> gnu.support>:
bug acknowledged by developer. (Mon, 23 Oct 2023 20:12:02 GMT) Full text and rfc822 format available.

Message #21 received at 62571-done <at> debbugs.gnu.org (full text, mbox):

From: Stefan Kangas <stefankangas <at> gmail.com>
To: Po Lu <luangruo <at> yahoo.com>
Cc: Jean Louis <bugs <at> gnu.support>, 62571-done <at> debbugs.gnu.org
Subject: Re: bug#62571: 30.0.50; Crash on entering 20x enlarged number
Date: Mon, 23 Oct 2023 13:11:18 -0700
Stefan Kangas <stefankangas <at> gmail.com> writes:

> Po Lu <luangruo <at> yahoo.com> writes:
>
>> Jean Louis <bugs <at> gnu.support> writes:
>>
>>> Here is how to reproduce:
>>>
>>> 1. emacs -Q
>>> 2. C-x + and repeat pressing + for 20 times in total
>>> 3. I press 6, as I wanted to show to child how number 6 looks like
>>> 4. X Server crashed, I guess Emacs too, I have no idea
>>>
>>> I did not test it with other numbers but 6, but it can easily be that X
>>> Window server will crash with letters as well.
>>>
>>> It is very repeatable. I am using Lucid built. Font used by default is
>>> here below, if that matter.
>>> Windowing system distributor 'The X.Org Foundation', version 11.0.12101006
>>
>> Xorg should print its crashes to a log typically at /var/log/Xorg.N.log,
>> where N is the number of your display.
>>
>> Such a crash message should contain its backtrace on GNU/Linux systems,
>> for example:
>>
>> [ 14866.219]
>> Backtrace:
>> [ 14866.219] 0: /usr/bin/X (xorg_backtrace+0x3b) [0x80b190b]
>> [ 14866.219] 1: /usr/bin/X (0x8048000+0x6202d) [0x80aa02d]
>> [ 14866.219] 2: (vdso) (__kernel_rt_sigreturn+0x0) [0xb789140c]
>> [ 14866.219] 16: /usr/bin/X (WriteToClient+0x15e) [0x80aac6e]
>> [ 14866.219] 17: /usr/bin/X (WriteEventsToClient+0x2be) [0x80929ae]
>> [ 14866.219] 18: /usr/bin/X (TryClientEvents+0xe2) [0x8095462]
>> [ 14866.219] 19: /usr/bin/X (DeliverEventsToWindow+0x390) [0x8098450]
>> [ 14866.219] 20: /usr/bin/X (DeliverEvents+0xf8) [0x8099018]
>> [ 14866.219] 21: /usr/bin/X (DeleteWindow+0x203) [0x8076b43]
>> [ 14866.219] 22: /usr/bin/X (FreeClientResources+0xed) [0x806389d]
>> [ 14866.219] 23: /usr/bin/X (CloseDownClient+0x69) [0x80659e9]
>> [ 14866.219] 24: /usr/bin/X (CheckConnections+0x137) [0x80a8987]
>> [ 14866.219] 25: /usr/bin/X (WaitForSomething+0x98c) [0x80a33ac]
>> [ 14866.220] 26: /usr/bin/X (0x8048000+0x2261e) [0x806a61e]
>> [ 14866.220] 27: /usr/bin/X (0x8048000+0x1a5ba) [0x80625ba]
>> [ 14866.220] 28: /lib/libc.so.6 (__libc_start_main+0xe7) [0xb75b5ce7]
>> [ 14866.220] 29: /usr/bin/X (0x8048000+0x1a191) [0x8062191]
>> [ 14866.220] Segmentation fault at address 0x1
>> [ 14866.220]
>> Caught signal 11 (Segmentation fault). Server aborting
>>
>> Typically, the DDX symbols printed are enough to give us an idea of what
>> has gone wrong.  Would you please try to obtain such a backtrace from
>> your X server crash?
>
> Ping.  Could you please try obtaining a backtrace?

More information was requested, but none was given within 6 weeks, so
I'm closing this bug.  If this is still an issue, please reply to this
email (use "Reply to all" in your email client) and we can reopen the
bug report.




bug archived. Request was from Debbugs Internal Request <help-debbugs <at> gnu.org> to internal_control <at> debbugs.gnu.org. (Tue, 21 Nov 2023 12:24:14 GMT) Full text and rfc822 format available.

This bug report was last modified 129 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.