bug#21822: 25.0.50; emacs_backtrace.txt

bug#21822: 25.0.50; emacs_backtrace.txt

[Drew Adams]

> Do you have BabelMap installed?  If not, could you install it, and
> then see which fonts cover this character on your machine?  Here, I
> have the following ones:
> 
>   Arial Unicode MS
>   Code2000
>   FreeSans
>   FreeSerif
>   Lucida Sans
>   Mangal
> 
> and Emacs actually chooses the last one when it displays this
> character.

Dunno what BabelMap is, or why I would want to install it.

Shouldn't it be enough to know that Emacs crashed when given
a char that it cannot show in the given font?  I didn't choose
the font - emacs -Q chose it.

bug#21822: 25.0.50; emacs_backtrace.txt

[Eli Zaretskii]

> Date: Wed, 4 Nov 2015 09:11:00 -0800 (PST)
> From: Drew Adams <drew.adams@oracle.com>
> Cc: lekktu@gmail.com, jwiegley@gmail.com, 21822@debbugs.gnu.org
> 
> > Do you have BabelMap installed?  If not, could you install it, and
> > then see which fonts cover this character on your machine?  Here, I
> > have the following ones:
> > 
> >   Arial Unicode MS
> >   Code2000
> >   FreeSans
> >   FreeSerif
> >   Lucida Sans
> >   Mangal
> > 
> > and Emacs actually chooses the last one when it displays this
> > character.
> 
> Dunno what BabelMap is

It's a nice program that can display any character you want, and also
can analyze font coverage on your system.

  http://www.babelstone.co.uk/Software/BabelMap.html

> or why I would want to install it.

It's the best way I know of to find out which fonts Emacs might have
tried to use for displaying that character.  Armed with that
knowledge, I might be able to reproduce your crash and fix it.

> Shouldn't it be enough to know that Emacs crashed when given
> a char that it cannot show in the given font?  I didn't choose
> the font - emacs -Q chose it.

The fonts Emacs choses depend on the fonts available on your system.
I cannot know which fonts you have that cover this character, and
Emacs doesn't crash for me (nor for Juanma) when we try your recipe.

Assuming you do want the reason for this crash be identified and
fixed, please help us by providing the information I asked for.

bug#21822: 25.0.50; emacs_backtrace.txt

[Drew Adams]

> It's a nice program that can display any character you want, and also
> can analyze font coverage on your system.
> http://www.babelstone.co.uk/Software/BabelMap.html

Yes, I saw that.  I can't get to it from behind the company firewall, as that site is flagged as having a history of security problems.  Might try it later, outside the firewall.

> It's the best way I know of to find out which fonts Emacs might have
> tried to use for displaying that character.  Armed with that
> knowledge, I might be able to reproduce your crash and fix it.

OK.

> > Shouldn't it be enough to know that Emacs crashed when given
> > a char that it cannot show in the given font?  I didn't choose
> > the font - emacs -Q chose it.
> 
> The fonts Emacs choses depend on the fonts available on your system.
> I cannot know which fonts you have that cover this character, and
> Emacs doesn't crash for me (nor for Juanma) when we try your recipe.
> 
> Assuming you do want the reason for this crash be identified and
> fixed, please help us by providing the information I asked for.

Understood.

bug#21822: 25.0.50; emacs_backtrace.txt

[Lars Magne Ingebrigtsen]

Drew Adams <drew.adams@oracle.com> writes:

>> It's a nice program that can display any character you want, and also
>> can analyze font coverage on your system.
>> http://www.babelstone.co.uk/Software/BabelMap.html
>
> Yes, I saw that.  I can't get to it from behind the company firewall,
> as that site is flagged as having a history of security problems.
> Might try it later, outside the firewall.
>
>> It's the best way I know of to find out which fonts Emacs might have
>> tried to use for displaying that character.  Armed with that
>> knowledge, I might be able to reproduce your crash and fix it.
>
> OK.
>
>> > Shouldn't it be enough to know that Emacs crashed when given
>> > a char that it cannot show in the given font?  I didn't choose
>> > the font - emacs -Q chose it.
>> 
>> The fonts Emacs choses depend on the fonts available on your system.
>> I cannot know which fonts you have that cover this character, and
>> Emacs doesn't crash for me (nor for Juanma) when we try your recipe.
>> 
>> Assuming you do want the reason for this crash be identified and
>> fixed, please help us by providing the information I asked for.
>
> Understood.

I think this was the final message in this thread.  Did you make any
progress in identifying the font?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

bug#21822: 25.0.50; emacs_backtrace.txt

[Drew Adams]

> >> > Shouldn't it be enough to know that Emacs crashed when given
> >> > a char that it cannot show in the given font?  I didn't choose
> >> > the font - emacs -Q chose it.
> >>
> >> The fonts Emacs choses depend on the fonts available on your system.
> >> I cannot know which fonts you have that cover this character, and
> >> Emacs doesn't crash for me (nor for Juanma) when we try your recipe.
> >>
> >> Assuming you do want the reason for this crash be identified and
> >> fixed, please help us by providing the information I asked for.
> >
> > Understood.
> 
> I think this was the final message in this thread.  Did you make any
> progress in identifying the font?

No.  I started to download Babel but it was flagged as a high
security risk, and I decided not to install it on my company
laptop.  Sorry.

As this was from emacs -Q, perhaps someone else can reproduce it.
If not, feel free to close the bug.  Thx.

bug#21822: 25.0.50; emacs_backtrace.txt

[Drew Adams]

> Could be something with a font Emacs tries to use on Drew's machine.
> It might be beneficial to try to find out which font is that.

With emacs -Q, (frame-parameters) tells me this wrt font stuff:

(font . "-outline-Courier New-normal-normal-normal-mono-17-*-*-*-c-*-iso8859-1")
(font-backend uniscribe gdi)

bug#21822: 25.0.50; emacs_backtrace.txt

[Juanma Barranquero]

[-- Attachment #1: Type: text/plain, Size: 1286 bytes --]

On Wed, Nov 4, 2015 at 5:37 PM, Drew Adams <drew.adams@oracle.com> wrote:

> (font . "-outline-Courier
New-normal-normal-normal-mono-17-*-*-*-c-*-iso8859-1")
> (font-backend uniscribe gdi)

But Courier New cannot display the character that you're trying to insert.
For example, after emacs -Q, doing C-x 8 <RET> 960 <RET> I get this
character:

             position: 192 of 192 (99%), column: 0
            character: ॠ (displayed as ॠ) (codepoint 2400, #o4540, #x960)
    preferred charset: unicode (Unicode (ISO10646))
code point in charset: 0x0960
               script: devanagari
               syntax: w which means: word
             category: .:Base, L:Left-to-right (strong), i:Indian
             to input: type "C-x 8 RET 960" or "C-x 8 RET DEVANAGARI LETTER
VOCALIC RR"
          buffer code: #xE0 #xA5 #xA0
            file code: not encodable by coding system iso-latin-1-dos
              display: by this font (glyph code)
    uniscribe:-outline-Nirmala
UI-normal-normal-normal-sans-13-*-*-*-p-*-iso10646-1 (#xF6)

Character code properties: customize what to show
  name: DEVANAGARI LETTER VOCALIC RR
  general-category: Lo (Letter, Other)
  decomposition: (2400) ('ॠ')

There are text properties here:
  fontified            nil

[-- Attachment #2: Type: text/html, Size: 1814 bytes --]

bug#21822: 25.0.50; emacs_backtrace.txt

[Drew Adams]

> (font . "-outline-Courier New-normal-normal-normal-mono-17-*-*-*-c-*-iso8859-1")
> (font-backend uniscribe gdi)

But Courier New cannot display the character that you're trying to insert. For example, after emacs -Q, doing C-x 8 <RET> 960 <RET> I get this character:

             position: 192 of 192 (99%), column: 0
            character: ॠ (displayed as ॠ) (codepoint 2400, #o4540, #x960)

OK; thanks.

I was mistakenly thinking of decimal 960 (not octal 960),
which is greek small PI.  IOW, I should have entered 3co (hex).

(Still, Emacs should not crash.)

bug#21822: 25.0.50; emacs_backtrace.txt

[Eli Zaretskii]

> Date: Wed, 4 Nov 2015 08:37:55 -0800 (PST)
> From: Drew Adams <drew.adams@oracle.com>
> Cc: drew.adams@oracle.com, jwiegley@gmail.com, 21822@debbugs.gnu.org
> 
> > Could be something with a font Emacs tries to use on Drew's machine.
> > It might be beneficial to try to find out which font is that.
> 
> With emacs -Q, (frame-parameters) tells me this wrt font stuff:
> 
> (font . "-outline-Courier New-normal-normal-normal-mono-17-*-*-*-c-*-iso8859-1")
> (font-backend uniscribe gdi)

Thanks, but that's not necessarily the answer to my question.  AFAICS,
Courier New doesn't have a glyph for this character.

Do you have BabelMap installed?  If not, could you install it, and
then see which fonts cover this character on your machine?  Here, I
have the following ones:

  Arial Unicode MS
  Code2000
  FreeSans
  FreeSerif
  Lucida Sans
  Mangal

and Emacs actually chooses the last one when it displays this
character.

bug#21822: 25.0.50; emacs_backtrace.txt

[Drew Adams]

From emacs -Q
In *scratch*, I tried C-x 8 RET 960 RET
and got a crash:

Exception 0xc0000005 at this address:
776e74f6

Backtrace:
012d315f
012d31d0
0114b7a5
01183f9c
01183f77
01183fd0
010010f5
76fc0317
77bd344b
77b99851

In GNU Emacs 25.0.50.1 (i686-pc-mingw32)
 of 2015-10-30
Repository revision: cadfceab1aaafaf2a1fd4f7a27fe488e9a06c3ae
Windowing system distributor 'Microsoft Corp.', version 6.1.7601
Configured using:
 'configure --prefix=/c/Devel/emacs/snapshot/trunk
 --enable-checking=yes,glyphs --enable-check-lisp-object-type
 --without-compress-install --with-wide-int 'CFLAGS=-O0 -ggdb3'
 LDFLAGS=-Lc:/Devel/emacs/lib 'CPPFLAGS=-DGC_MCHECK=1
 -Ic:/Devel/emacs/include''

Configured features:
XPM JPEG TIFF GIF PNG RSVG SOUND NOTIFY ACL GNUTLS LIBXML2 ZLIB
TOOLKIT_SCROLL_BARS

Important settings:
  value of $LANG: ENU
  locale-coding-system: cp1252

Major mode: Text

Minor modes in effect:
  tooltip-mode: t
  global-eldoc-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
  auto-composition-mode: t
  auto-encryption-mode: t
  auto-compression-mode: t
  line-number-mode: t
  transient-mark-mode: t

Recent messages:
For information about GNU Emacs and the GNU system, type C-h C-a.

Load-path shadows:
None found.

Features:
(shadow sort gnus-util mail-extr emacsbug message format-spec rfc822 mml
mml-sec mm-decode mm-bodies mm-encode mail-parse rfc2231 mailabbrev
gmm-utils mailheader sendmail rfc2047 rfc2045 ietf-drums mm-util
help-fns help-mode easymenu cl-loaddefs pcase cl-lib mail-prsvr
mail-utils dired time-date mule-util tooltip eldoc electric uniquify
ediff-hook vc-hooks lisp-float-type mwheel dos-w32 ls-lisp disp-table
w32-win w32-vars term/common-win tool-bar dnd fontset image regexp-opt
fringe tabulated-list newcomment elisp-mode lisp-mode prog-mode register
page menu-bar rfn-eshadow timer select scroll-bar mouse jit-lock
font-lock syntax facemenu font-core frame cl-generic 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 charscript case-table epa-hook
jka-cmpr-hook help simple abbrev minibuffer cl-preloaded nadvice
loaddefs button faces cus-face macroexp files text-properties overlay
sha1 md5 base64 format env code-pages mule custom widget
hashtable-print-readable backquote w32notify w32 multi-tty
make-network-process emacs)

Memory information:
((conses 16 165686 43954)
 (symbols 56 19082 0)
 (miscs 48 60 86)
 (strings 16 14431 7178)
 (string-bytes 1 392066)
 (vectors 16 10700)
 (vector-slots 8 407582 6084)
 (floats 8 134 287)
 (intervals 40 30810 6777)
 (buffers 856 13))

bug#21822: 25.0.50; emacs_backtrace.txt

[John Wiegley]

>>>>> Drew Adams <drew.adams@oracle.com> writes:

> From emacs -Q
> In *scratch*, I tried C-x 8 RET 960 RET
> and got a crash:

> Exception 0xc0000005 at this address:
> 776e74f6

> Backtrace:
> 012d315f
> 012d31d0
> 0114b7a5
> 01183f9c
> 01183f77
> 01183fd0
> 010010f5
> 76fc0317
> 77bd344b
> 77b99851

Was your executable stripped?  Since you built with -O0, it should be possible
to get a meaningful backtrace.

John

bug#21822: 25.0.50; emacs_backtrace.txt

[Drew Adams]

> Was your executable stripped?  Since you built with -O0, it should be
> possible to get a meaningful backtrace.

Ccing the builder, Juanma.

bug#21822: 25.0.50; emacs_backtrace.txt

[Juanma Barranquero]

[-- Attachment #1: Type: text/plain, Size: 397 bytes --]

The backtrace is not very informative, in this case

?? ??:0
w32_backtrace at w32fns.c:9289
emacs_abort at w32fns.c:9321
terminate_due_to_signal at emacs.c:398
handle_fatal_signal at sysdep.c:1591
deliver_thread_signal at sysdep.c:1565
deliver_fatal_thread_signal at sysdep.c:1603
?? at cygming-crtbegin.c:?
?? ??:0
?? ??:0
?? ??:0

and I don't get a crash with that recipe using the same binary.

[-- Attachment #2: Type: text/html, Size: 648 bytes --]

bug#21822: 25.0.50; emacs_backtrace.txt

[Eli Zaretskii]

> From: Juanma Barranquero <lekktu@gmail.com>
> Date: Wed, 4 Nov 2015 09:03:28 +0100
> Cc: John Wiegley <jwiegley@gmail.com>, 21822@debbugs.gnu.org
> 
> The backtrace is not very informative, in this case
> 
> ?? ??:0
> w32_backtrace at w32fns.c:9289
> emacs_abort at w32fns.c:9321
> terminate_due_to_signal at emacs.c:398
> handle_fatal_signal at sysdep.c:1591
> deliver_thread_signal at sysdep.c:1565
> deliver_fatal_thread_signal at sysdep.c:1603
> ?? at cygming-crtbegin.c:?
> ?? ??:0
> ?? ??:0
> ?? ??:0
> 
> and I don't get a crash with that recipe using the same binary.

Could be something with a font Emacs tries to use on Drew's machine.
It might be beneficial to try to find out which font is that.

bug#21822: 25.0.50; emacs_backtrace.txt

[Drew Adams]

> > From emacs -Q
> > In *scratch*, I tried C-x 8 RET 960 RET and got a crash:
> 
> Was your executable stripped?  Since you built with -O0, it should be
> possible to get a meaningful backtrace.

I don't build Emacs myself.  This was a build provided by Juanma,
who has already provided whatever additional info he could about it:

  The backtrace is not very informative, in this case

  ?? ??:0
  w32_backtrace at w32fns.c:9289
  emacs_abort at w32fns.c:9321
  terminate_due_to_signal at emacs.c:398
  handle_fatal_signal at sysdep.c:1591
  deliver_thread_signal at sysdep.c:1565
  deliver_fatal_thread_signal at sysdep.c:1603
  ?? at cygming-crtbegin.c:?
  ?? ??:0
  ?? ??:0
  ?? ??:0

  and I don't get a crash with that recipe using the same binary.

IOW, Juanma could not repro the crash.  Feel free to close the bug.