Description of problem: I have in logs now eight messages of this nature: kernel: rd-bomb[19235]: segfault at 0000002a9568b000 rip 0000000000403023 rsp 0000007fbfffeec0 error 6 Reported values are consistent with an exception of "rsp" which moves a bit. No idea if this happens on i386 or not. Yes, I know that I can turn that particular "hack" off. Version-Release number of selected component (if applicable): xscreensaver-4.18-4 How reproducible: Seems to be pretty consistent
What happens if you run /usr/X11R6/lib/xscreensaver/rd-bomb from the command line?
> What happens if you run /usr/X11R6/lib/xscreensaver/rd-bomb from the > command line? Segmentation fault and if I will try that under gdb then I see: (gdb) r Starting program: /usr/X11R6/lib/xscreensaver/rd-bomb warning: Child process unexpectedly missing: No child processes Program terminated with signal ?, Unknown signal. The program no longer exists. You can't do that without a process to debug.
If you are using kernel-2.6.9-1.724_FC3 a broken gdb is bug #144021 . If you are feeling brave you can always try putting it through valgrind...
Oh, I did not realized that ptrace got broken on FC3 too. This is from another box with a "rawhide" installation, xscreensaver-4.18-17 and after debuginfo package was installed. (gdb) r Starting program: /usr/libexec/xscreensaver/hacks/rd-bomb Program received signal SIGSEGV, Segmentation fault. 0x00000000004030fe in screenhack (dpy=0x50f920, win=39845889) at rd-bomb.c:277 277 qqq[j] = colors[mc[r1] % ncolors].pixel; (gdb) bt #0 0x00000000004030fe in screenhack (dpy=0x50f920, win=39845889) at rd-bomb.c:277 #1 0x0000000000404489 in main (argc=1, argv=0x7ffffffff818) at screenhack.c:678 #2 0x0000003b41d1c4ca in __libc_start_main () from /lib64/tls/libc.so.6 #3 0x00000000004022ba in _start () #4 0x00007ffffffff808 in ?? () #5 0x000000000000001c in ?? () #6 0x0000000000000001 in ?? () #7 0x00007ffffffffa4f in ?? () #8 0x0000000000000000 in ?? () Above 'r1' is 65500, 'colors[mc[r1] % ncolors]' gives {pixel = 15100542, red = 58880, green = 27207, blue = 32485, flags = 7 '\a', pad = 0 '\0'} and 'j' prints as -1430464576, i.e. 0xaabcd7c0. SIGSEGV looks "natural" in circumstances. :-) 'j' is a lower half of $r12 which actually contains 0x2aaaaabcbf70. Somebody fast and loose with types?
This seems to be fixed in xscreensaver-4.22-18 in rawhide
Fedora Core 3 is now maintained by the Fedora Legacy project for security updates only. If this problem is a security issue, please reopen and reassign to the Fedora Legacy product. If it is not a security issue and hasn't been resolved in the current FC5 updates or in the FC6 test release, reopen and change the version to match. Thank you!
The information we've requested above is required in order to review this problem report further and diagnose/fix the issue if it is still present. Since there haven't been any updates to the report in quite a long time now after we've requested additional information, we're assuming the problem is either no longer present in our current OS release, or that there is no longer any interest in tracking the problem. Setting status to CANTFIX, however if you still experience this problem after updating to our latest Fedora Core release and are still interested in Red Hat tracking the issue, and assisting in troubleshooting the problem, please feel free to provide the information requested above, and reopen the report. Thank you in advance. (this message is mass message)