[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#3659: FW: 23.0.95; crash on set-frame-font
From: |
Kenichi Handa |
Subject: |
bug#3659: FW: 23.0.95; crash on set-frame-font |
Date: |
Mon, 27 Jul 2009 10:44:23 +0900 |
In article
<63C2A154B1708946B60726AFDBA00AC00676DBAF@ukmailemea01.misys.global.ad>,
"Marshall, Simon" <Simon.Marshall@misys.com> writes:
> Breakpoint 3, Fsignal (error_symbol=5385409, data=6603597) at
> eval.c:1641
> 1641 register struct handler *allhandlers = handlerlist;
> (gdb) where
> #0 Fsignal (error_symbol=5385409, data=6603597) at eval.c:1641
> #1 0x002813e8 in xsignal (error_symbol=5385409, data=6603597) at
> eval.c:1751
> #2 0x00281480 in xsignal2 (error_symbol=5385409, arg1=5385985,
> arg2=5314561) at eval.c:1775
> #3 0x00259ab0 in wrong_type_argument (predicate=5385985, value=5314561)
> at data.c:115
> #4 0x000df1c8 in load_charset_map_from_vector (charset=0x369f30,
> vec=5314561, control_flag=2)
> at charset.c:608
> #5 0x000df57c in load_charset (charset=0x369f30, control_flag=2) at
> charset.c:658
> #6 0x000e61b8 in encode_char (charset=0x369f30, c=192) at
> charset.c:1807
Ok, so the Fsignal call is because "*charset" is completely
broken (according to your previous mail).
> #7 0x003337c4 in xfont_chars_supported (chars=9656829, xfont=0xbf4200,
> encoding=0x369f30,
> repertory=0x0) at xfont.c:238
> #8 0x0033458c in xfont_supported_scripts (display=0xa0e000,
> fontname=0xc83dfb "--------0------",
> props=5454596, encoding=0x369f30) at xfont.c:328
Your previous backtrace didn't show that
xfont_supported_scripts is called. It may be because the
previous backtrace was made by the emacs compiled with -O2.
Anyway, the above fontname has a strange format. For such a
fontname, xfont_supported_scripts should not be called from
xfont_list_pattern.
> #9 0x00334e30 in xfont_list_pattern (display=0xa0e000,
> pattern=0xffbeca84 "-*-*-*-*-*-*-*-*-*-*-*-*-*-*", registry=5314561,
> script=5314561)
> at xfont.c:466
Please set the breakpoint at xfont.c:414 with conditional:
buf[1]=='-' && buf[2]=='-' && buf[3]=='-' && buf[4]=='-'
(I think that is enough for matching with "--------0------")
When emacs stops at that breakpoint, execute the code one
line by one (by "n" command) until the line 466 (i.e. the
call of xfont_supported_scripts) while checking why none of
"if" conditions that leads to "continue" aren't satisfied.
---
Kenichi Handa
handa@m17n.org
- bug#3659: FW: 23.0.95; crash on set-frame-font, (continued)
- bug#3659: FW: 23.0.95; crash on set-frame-font, Kenichi Handa, 2009/07/23
- Message not available
- bug#3659: FW: 23.0.95; crash on set-frame-font, Kenichi Handa, 2009/07/23
- bug#3659: FW: 23.0.95; crash on set-frame-font, Marshall, Simon, 2009/07/24
- bug#3659: FW: 23.0.95; crash on set-frame-font, Kenichi Handa, 2009/07/24
- bug#3659: FW: 23.0.95; crash on set-frame-font, Marshall, Simon, 2009/07/24
- bug#3659: FW: 23.0.95; crash on set-frame-font, Kenichi Handa, 2009/07/24
- Message not available
- bug#3659: FW: 23.0.95; crash on set-frame-font, Chong Yidong, 2009/07/24
- bug#3659: FW: 23.0.95; crash on set-frame-font, Marshall, Simon, 2009/07/24
- bug#3659: FW: 23.0.95; crash on set-frame-font, Chong Yidong, 2009/07/26
- bug#3659: FW: 23.0.95; crash on set-frame-font, Marshall, Simon, 2009/07/27
- Message not available
- bug#3659: FW: 23.0.95; crash on set-frame-font,
Kenichi Handa <=
- Message not available
- bug#3659: FW: 23.0.95; crash on set-frame-font, Chong Yidong, 2009/07/27
- Message not available
- bug#3659: FW: 23.0.95; crash on set-frame-font, Chong Yidong, 2009/07/27
- Message not available
- bug#3659: FW: 23.0.95; crash on set-frame-font, Kenichi Handa, 2009/07/27
- bug#3659: FW: 23.0.95; crash on set-frame-font, Marshall, Simon, 2009/07/28