|
Description
|
There is a problem
that 'xscreensaver' can't startup and dumped core file
after installing Patch:120094-11(or later) "X11 6.6.2: xscreensaver patch",
And after uninstalling Patch:120094-11, xscreensaver can start up.
It couldn't reproduce with -10, so the culprit should be -11.
--------------------------
Patch-ID# 120094-11
Keywords: security xscreensaver
Synopsis: X11 6.6.2: xscreensaver patch
Date: Feb/20/2007
--------------------------
It could be reprocued by just executing xscreensaver with -11 patch.
----------------------------
bash-3.00# /usr/X/bin/xscreensaver
(process:21206): GLib-GObject-CRITICAL **: gtype.c:2253: initialization
assertion failed, use g_type_init() prior to this function
(process:21206): GLib-GObject-CRITICAL **: file gobject.c: line 819:
assertion `G_TYPE_IS_OBJECT (object_type)' failed
(process:21206): GLib-GObject-CRITICAL **: file gobject.c: line 1561:
assertion `G_IS_OBJECT (object)' failed
Segmentation Fault (core dumped)
bash-3.00#
----------------------------
----------------------------
bash-2.05$ pwd
/cores/11045041/0619
bash-2.05$ ls
./ core
pkg_app.errors
../ dbxrc
pkg_app.info
11045041_pkg_app_xscreensaver.tar.Z dbxrc2
pkg_app.pldd
app/ opencore*
bash-2.05$ dbx -s dbxrc2
:
program terminated by signal SEGV (Segmentation Fault)
0xff33cf98: _kill+0x0008: blu _cerror ! 0xff2a06a0
(dbx)
(dbx) where -l
=>[1] libc.so.1:_kill(0x0, 0xb, 0x280, 0x0, 0x83280, 0x1), at 0xff33cf98
[2] xscreensaver:restore_real_vroot_handler(0xb, 0x0, 0x0, 0x0,
0x72400, 0x0), at 0x1b58c
[3] libc.so.1:__sighndlr(0xb, 0x0, 0xffbfef28, 0x1b448, 0x0, 0x0), at
0xff33c52c
---- called from signal handler with signal 11 (SIGSEGV) ------
[4] libgconf-2.so.4.1.0:set_engine(0x0, 0x8bde8, 0x0, 0xfeee9c00,
0xfeee9800, 0xfeee9800), at 0xfefa5ee8
[5] libgconf-2.so.4.1.0:gconf_client_get_default(0x0, 0xff331b20, 0x0,
0x1ee00, 0x10b4, 0xfefc5118), at 0xfefa6434
[6] xscreensaver:main_loop(0xffbff4d0, 0x10, 0x5a0, 0x63400, 0x44400,
0xffbff4d4), at 0x177b0
[7] xscreensaver:main(0x1, 0x42c00, 0x1, 0x2, 0x1, 0x0), at 0x186e8
(dbx) frame 4
0xfefa5ee8: set_engine+0x0004: ld [%i0 + 12], %o0
(dbx) regs
current frame: [4]
g0-g1 0x00000000 0x00000000 0x00000000 0x00000001
g2-g3 0x00000000 0x00000000 0x00000000 0x0008b948
g4-g5 0x00000000 0x00000001 0x00000000 0x00072000
g6-g7 0x00000000 0x00000000 0x00000000 0xff3a2000
o0-o1 0x00000000 0xfeee992c 0x00000000 0x00000008
o2-o3 0x00000000 0xfeee993c 0x00000000 0xfeee99f0
o4-o5 0x00000000 0x00000619 0x00000000 0xfeee9d14
o6-o7 0x00000000 0xffbff1e0 0x00000000 0xfeec3e9c
l0-l1 0x00000000 0x00000000 0x00000000 0xfefc71a8
l2-l3 0x00000000 0x0000085c 0x00000000 0x00000800
l4-l5 0x00000000 0x00000860 0x00000000 0xfeee9c00
l6-l7 0x00000000 0xfeee9800 0x00000000 0xfeee9800
i0-i1 0x00000000 0x00000000 0x00000000 0x0008bde8
^^^^^^^^^^
i2-i3 0x00000000 0x00000000 0x00000000 0xfeee9c00
i4-i5 0x00000000 0xfeee9800 0x00000000 0xfeee9800
i6-i7 0x00000000 0xffbff240 0x00000000 0xfefa6434
y 0x00000000 0x00000000
ccr 0x00000000 0x00000008
pc 0x00000000 0xfefa5ee8:set_engine+0x4 ld [%i0 + 12], %o0
npc 0x00000000 0xfefa5eec:set_engine+0x8 cmp %i1, %o0
(dbx) proc -map
Loadobject mappings for current core file:
0x00010000 /usr/openwin/bin/xscreensaver
0xff280000 /lib/libc.so.1
0xff200000 /usr/openwin/lib/libXt.so.4
:
----------------------------
I think this issue is similar to CR:6197569
6197569 "VM crash if java application tries to use system proxy
(Solaris10 build 71 CDE only)"
http://monaco.sfbay/detail.jsf?cr=6197569
I copied app(xscreensaver), core and libraries into here;
/net/cores.central/cores/11045041/0619
/net/cores.central/cores/11045041/0619_Cu
|