On 05/11/05 15:34, Alexander Schmehl wrote: >>Architecture: amd64 (x86_64) > > > Strange, that is the second time, I hear about problems of ppracer on > amd64... sadly I don't have access to such a machine :(
I should perhaps have made that more clear instead of burying it at the bottom of my report. It could well be an amd64-specific problem, although I get a segfault running ppracer in a 32-bit chroot. That is with 64-bit everything else (X server, arts, etc - running 32-bit clients in this environment usually works fine) so I will try installing a full 32-bit system. Also, I will add a few other observations: if I run ppracer from a VT, and have not previously run it from an xterm in the same X session, I get the message: X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 134 (XFree86-VidModeExtension) Minor opcode of failed request: 10 (XF86VidModeSwitchToMode) Value in failed request: 0x4b Serial number of failed request: 104 Current serial number in output stream: 106 If I run it from an xterm, it changes the video mode then segfaults. If I now go back and run it from a VT, it segfaults there too. Finally if I run it in gdb on an xterm, the screen simply goes black and I can no longer use that X session. Running it in gdb on a VT results either in a segfault or an X error, depending on whether I have previously run it from an xterm or not, but does not trash the X session. -- Martin Orr
signature.asc
Description: OpenPGP digital signature
