Torcs Segfaults on Launch

[Paladine]

Binary package hint: torcs

I get the following error when trying to lauch torcs in Gutsy:

paladine@mail:~$ torcs
Visual Properties Report
------------------------
Compatibility mode, properties unknown.
/usr/games/torcs: line 52: 12025 Segmentation fault $LIBDIR/torcs-bin -l $LOCAL_CONF -L $LIBDIR -D $DATADIR $*

Paladine

[Emmet Hikory (persia)]

Torcs is working for me. Could you please install torcs-dbgsym, and attach the output of `torcs -d` and `torcs -l` to the bug report? Also, on which architecture are you experiencing the crash?

[Paladine (paladine)]

paladine@mail:~$ sudo apt-get install torcs-dbgsym
Password:
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Couldn't find package torcs-dbgsym

This package is not available in Gutsy standard repositories.

As for architecture see below:

AMD Athlon 64 X2 4400 Toledo Core
2GB DDR RAM
Nvidia Geforce 6600GT 128MB SLI Capable
NVidia Geforce 6600GT 128MB SLI Capable (yes 2 cards but not currently running in SLI mode)
2x 250GB SATA hard drives
Asus A8N SLI Delux mainboard
2x 19" LCD Displays running in Xinerama mode with one display per graphics card.

[Paladine (paladine)]

Seems this is an XRandR problem, see the output of torcs -d below:

paladine@mail:~$ torcs -d
GNU gdb 6.6-debian
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i486-linux-gnu"...
(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(gdb) Starting program: /usr/lib/torcs/torcs-bin -l /home/paladine/.torcs -L /usr/lib/torcs -D /usr/share/games/torcs
(no debugging symbols found)
Failed to read a valid object file image from memory.
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
---Type <return> to continue, or q <return> to quit---bt
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
---Type <return> to continue, or q <return> to quit---(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1229596944 (LWP 20117)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
Visual Properties Report
------------------------
Compatibility mode, properties unknown.

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1229596944 (LWP 20117)]
0xb7923454 in ?? () from /usr/lib/libXrandr.so.2
(gdb) quit
The program is running. Exit anyway? (y or n) [answered Y; input not from terminal]
paladine@mail:~$
--

XRandR is disabled by Xinerama so this would appear to be the cause of the segfault. Is it possible to build torcs without requiring XRandR? I discovered a similar problem with MythTV recently which was fixed by using --disable-xrandr passed during ./configure

See https://bugs.launchpad.net/ubuntu/+source/mythtv/+bug/109227 for more info on this.

Paladine

[Emmet Hikory (persia)]

Thanks for tracking it down. Based on this, I agree that this is likely due to the nVidia drivers not supporting XRandR 1.2. For future note, the -dbgsym packages are available from "deb http://people.ubuntu.com/~pitti/ddebs gutsy main universe". Also, typing "bt" at the gdb prompt prior to quit will generate a backtrace. I'm not sure that this should be fixed in torcs (and all other affected applications) only to be reverted when nVidia updates the driver.

[Paladine (paladine)]

I have an ongoing thread on nvnews linux forums regarding XRandR 1.2 support in NVidia Drivers, see below:

http://www.nvnews.net/vbulletin/showthread.php?t=92648

Paladine

[Michael R. Head (burner)]

Getting this on my nvidia-based T61p, too...

[Thomas Hotz (thotz-deactivatedaccount)]

I never had such problems so I can't confirm this behaviour. Does this still occur with supported Ubuntu versions like Ubuntu 10.04 LTS or Ubuntu 12.04 LTS?