[ icewm-Bugs-697958 ] APM/ACPI crash on startup with 1.2.6

[SourceForge.net <no...@so...>]

Bugs item #697958, was opened at 2003-03-05 13:16
Message generated for change (Comment added) made by captnmark
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100031&aid=697958&group_id=31

>Category: verify-fixed
Group: crash
Status: Open
Resolution: Out of Date
Priority: 7
Submitted By: Klaus Schneider (kschn)
Assigned to: Marko Macek (captnmark)
Summary: APM/ACPI crash on startup with 1.2.6

Initial Comment:
I've found a strange SIGSEGV in icewm: when I startup,
*sometimes* icewm
crashes with a SIGSEGV but other times it doesn't.
Can't reproduce when
it happens, there doesn't seem to be any reasonable
explanation when it
happens.
If icewm once has started up correctly, it runs stable.

I've catched it with gdb, here is a backtrace:
(gdb) run
Starting program: /temp/src/icewm-1.2.6/src/icewm 
IceWM: using /home/klaus/.icewm for private
configuration files

Program received signal SIGSEGV, Segmentation fault.
0x402aa219 in malloc () from /lib/libc.so.6
(gdb) backtrace
#0  0x402aa219 in malloc () from /lib/libc.so.6
#1  0x402aa074 in malloc () from /lib/libc.so.6
#2  0x403648fe in _init () from /usr/lib/libfreetype.so.6
#3  0x40365658 in FT_Alloc () from
/usr/lib/libfreetype.so.6
#4  0x4037d14f in ps1_hints_apply () from
/usr/lib/libfreetype.so.6
#5  0x4037db6e in ps2_hints_apply () from
/usr/lib/libfreetype.so.6
#6  0x40379f2c in RepadBitmap () from
/usr/lib/libfreetype.so.6
#7  0x4039191e in TT_RunIns () from
/usr/lib/libfreetype.so.6
#8  0x40391af7 in TT_RunIns () from
/usr/lib/libfreetype.so.6
#9  0x403662e9 in FT_Load_Glyph () from
/usr/lib/libfreetype.so.6
#10 0x40135cc6 in XftGlyphLoad () from
/usr/X11R6/lib/libXft.so.1
#11 0x401373a0 in XftRenderExtents32 () from
/usr/X11R6/lib/libXft.so.1
#12 0x4012d336 in XftTextExtents32 () from
/usr/X11R6/lib/libXft.so.1
#13 0x08081b44 in YXftFont::partitions (this=0x8116820,
str=0x8118a50,
    len=3, nparts=0) at ypaint.cc:91
#14 0x080815cd in YXftFont::textWidth (this=0x8116820,
text=@0xbffff79c)
    at ypaint.cc:547
#15 0x0808167d in YXftFont::textWidth (this=0x8116820,
str=0x8118a40 "79%", 
    len=3) at ypaint.cc:557
#16 0x08080b35 in YFont::textWidth (this=0x8116820,
str=0x8118a40 "79%")
    at ypaint.cc:287
#17 0x08080cfd in YFont::multilineAlloc
(this=0x8116820, str=0x8118a40 "79%")
    at ypaint.cc:322
#18 0x08084714 in YToolTip::setText (this=0x81189c8,
tip=0xbffff8bc "79%")
    at ytooltip.cc:61
#19 0x0807eb00 in YWindow::setToolTip (this=0x8126b48,
tip=0xbffff8bc "79%")
    at ywindow.cc:806
#20 0x08079d7c in YApm::updateToolTip (this=0x8126b48)
at aapm.cc:441
#21 0x08079c6d in YApm::YApm (this=0x8126b48,
aParent=0x810ebe0) at
    aapm.cc:415
#22 0x08051369 in TaskBar::TaskBar (this=0x810ebe0,
aParent=0x80dc018)
    at wmtaskbar.cc:307
#23 0x080621f7 in YWMApp::YWMApp (this=0xbffffa68,
argc=0xbffffb14, 
    argv=0xbffffb18, displayName=0x0) at wmapp.cc:1270
#24 0x08062e4e in main (argc=1, argv=0xbffffb74) at
wmapp.cc:1591


(gdb) x/c 0x8118a50
0x8118a50:      55 '7'
(gdb) x/c 0x8118a51
0x8118a51:      0 '\0'
(gdb) x/c 0x8118a52
0x8118a52:      0 '\0'
(gdb) x/c 0x8118a53
0x8118a53:      0 '\0'
(gdb) x/c 0x8118a54
0x8118a54:      57 '9'
(gdb) x/c 0x8118a55
0x8118a55:      0 '\0'
(gdb) x/c 0x8118a56
0x8118a56:      0 '\0'
(gdb) x/c 0x8118a57
0x8118a57:      0 '\0'
(gdb) x/c 0x8118a58
0x8118a58:      37 '%'
(gdb) x/c 0x8118a59
0x8118a59:      0 '\0'


----------------------------------------------------------------------

>Comment By: Marko Macek (captnmark)
Date: 2003-07-19 08:02

Message:
Logged In: YES 
user_id=1814

This might be fixed by font fallback cleanups.

----------------------------------------------------------------------

Comment By: Marko Macek (captnmark)
Date: 2003-06-08 10:33

Message:
Logged In: YES 
user_id=1814

I can't reproduce this (enabled APM for  a while, and
valgrind shows nothing).

Please reproduce with latest version.

----------------------------------------------------------------------

Comment By: Klaus Schneider (kschn)
Date: 2003-03-10 12:25

Message:
Logged In: YES 
user_id=661237

The backtrace seems to be always the same, with slightly 
different addresses. The crash never happened if I set 
TaskBarShowAPMStatus=0. However it´s difficult to catch it 
because it does not happen too often.

----------------------------------------------------------------------

Comment By: Marko Macek (captnmark)
Date: 2003-03-05 20:43

Message:
Logged In: YES 
user_id=1814

Is the crash backtrace always the same?

If you set TaskBarShowAPMStatus=0, does the crash still happen?

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100031&aid=697958&group_id=31