Same here, after freshly upgrading from Intrepid to Jaunty RC, running
natively on hardware (no VM), wacom tablet configured in xorg.conf, but
not plugged in. Access via ssh possible. Reproducable.
Xorg.0.log contains those same lines as in the attached XorgLogOld.txt, except
for minor address offsets:
Backtrace:
0: /usr/bin/X(xorg_backtrace+0x3b) [0x813518b]
1: /usr/bin/X(xf86SigHandler+0x55) [0x80c7be5]
2: [0xb7f2b400]
3: /usr/bin/X(ActivateDevice+0x4f) [0x808662f]
4: /usr/bin/X(InitAndStartDevices+0x42) [0x8086732]
5: /usr/bin/X(main+0x36f) [0x807229f]
6: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe5) [0xb7af7775]
7: /usr/bin/X [0x80717a1]
Saw signal 11. Server aborting.
I recompiled the wacom package with DEB_BUILD_OPTIONS="nostrip noopt debug" and
ran it through gdb:
#0 0xb6c11aa0 in xf86WcmDevProc (pWcm=0x9949658, what=0)
at ../../../src/xdrv/xf86Wacom.c:1014
#1 0x0808662f in ActivateDevice ()
#2 0x08086732 in InitAndStartDevices ()
#3 0x0807229f in main ()
The section in question:
1009 static int xf86WcmDevProc(DeviceIntPtr pWcm, int what)
1010 {
1011 LocalDevicePtr local = (LocalDevicePtr)pWcm->public.devicePrivate;
1012 WacomDevicePtr priv = (WacomDevicePtr)PRIVATE(pWcm);
1013
1014 DBG(2, priv->debugLevel, ErrorF("BEGIN xf86WcmProc dev=%p priv=%p "
DBG expands like this:
#define DBG(lvl, dLevel, f) do { if ((lvl) <= dLevel) f; } while (0)
The error occurs when priv->debugLevel gets loaded in order to evaluate the if.
gdb confirms this:
(gdb) print priv->debugLevel
Cannot access memory at address 0x72657369
So the cause of the problem is that xf86WcmDevProc thinks this private
data should be a pointer to some valid wacom-specific data, which is not
the case. PRIVATE is an alias for XI_PRIVATE from
/usr/include/xorg/xf86Xinput.h.
I'll try to recompile xorg-server. Sometimes debugging would be so much
easier if I could simply grab those debug symbols via apt-get!!!
--
Xorg crashed with SIGSEGV in ActivateDevice() - wacom tablet
https://bugs.launchpad.net/bugs/336401
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
