On Mon, 20 Mar 2017, Paul Goyette wrote:
I've noticed for a while that xlockmore doesn't seem to be working. It
used to work just fine, at least with my favorite, -mode maze, but now it
seems to fail regardless of what mode you specify. It simply prints a
one-word message
Abort
without dropping core or any further debug info.
Is anyone else using this package? On amd64 port?
OK, it wasn't dropping a core file because the program runs 'setuid'!
Running xlock as root gives me a core dump, with the following traceback
info:
(gdb) target core xlock.core
[New process 1]
Core was generated by `xlock'.
Program terminated with signal SIGABRT, Aborted.
#0 0x000070725283dd7a in _sys___sigprocmask14 () from /usr/lib/libc.so.12
(gdb) bt
#0 0x000070725283dd7a in _sys___sigprocmask14 () from /usr/lib/libc.so.12
#1 0x000070724e0094fb in pthread_sigmask () from /usr/lib/libpthread.so.1
#2 0x000070724e7c643e in radeon_drm_winsys_create () from
/usr/X11R7/lib/modules/dri/r600_dri.so
#3 0x000070724e4ba1ac in dd_create_screen () from
/usr/X11R7/lib/modules/dri/r600_dri.so
#4 0x000070724e4bbbee in ?? () from /usr/X11R7/lib/modules/dri/r600_dri.so
#5 0x000070724e4c4f01 in ?? () from /usr/X11R7/lib/modules/dri/r600_dri.so
#6 0x0000707254858f6c in ?? () from /usr/X11R7/lib/libGL.so.2
#7 0x0000707254851263 in __glXInitialize () from /usr/X11R7/lib/libGL.so.2
#8 0x00007072548533df in ?? () from /usr/X11R7/lib/libGL.so.2
#9 0x000070725485350d in glXChooseVisual () from /usr/X11R7/lib/libGL.so.2
.
.
.
.
Anyone got any clues?
+------------------+--------------------------+------------------------+
| Paul Goyette | PGP Key fingerprint: | E-mail addresses: |
| (Retired) | FA29 0E3B 35AF E8AE 6651 | paul at whooppee.com |
| Kernel Developer | 0786 F758 55DE 53BA 7731 | pgoyette at netbsd.org |
+------------------+--------------------------+------------------------+