Torcs crashed unexpectantly

Bug #104413 reported by Richard Edwards
16
Affects Status Importance Assigned to Milestone
torcs (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: torcs

I allowed the system to send a bug report from this address

ProblemType: Crash
Architecture: i386
Date: Sun Apr 8 00:26:42 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/lib/torcs/torcs-bin
Package: torcs 1.2.4-2ubuntu1
PackageArchitecture: i386
ProcCmdline: /usr/lib/torcs//torcs-bin -m -l /home/rwe1/.torcs// -L /usr/lib/torcs// -D /usr/share/games/torcs//
ProcCwd: /usr/share/games/torcs
ProcEnviron:
 SHELL=/bin/bash
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
Signal: 11
SourcePackage: torcs
StacktraceTop:
 strlen () from /lib/tls/i686/cmov/libc.so.6
 ulStrEqual () from /usr/lib/libplibul.so.1.8.4
 ssgAddTextureFormat () from /usr/lib/libplibssg.so.1.8.4
 grLoadScene ()
 initTrack ()
Uname: Linux kubuntu704 2.6.20-14-generic #2 SMP Mon Apr 2 20:37:49 UTC 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

Revision history for this message
Richard Edwards (rwe111) wrote :
Revision history for this message
Adrien Cunin (adri2000) wrote :

Thanks for your bug report. What were you doing when it crashed? Can you reproduce the crash?

Changed in torcs:
status: Unconfirmed → Needs Info
Revision history for this message
Richard Edwards (rwe111) wrote : Re: [Bug 104413] Re: Torcs crashed unexpectantly

Adrien Cunin wrote:
> Thanks for your bug report. What were you doing when it crashed? Can you
> reproduce the crash?
>
> ** Changed in: torcs (Ubuntu)
> Status: Unconfirmed => Needs Info
>
>
Hi Adrien,

I actually thought I had closed the application/game and had logged out
of my session and shut the machine down. When I turned the machine back
on the next day and started a new session thats when I got the
message. The game wasn't playing that well probably because I was
unfamiliar with it and I haven't the chance to play it again. I have
had a number of games installed and removed because they would lock up
but never filed a bug report. This machine is not a high end one, and
the hardware is getting old. I'll play the game again and report back
if I have any problems.

Thanks

Revision history for this message
Miguel Martinez (el-quark) wrote :

Hi guys,

I've also got a problem with torcs, although I suspect it has something to do with libc6. The issue is that for some circuits, whenever a practice, qualifying (any driver) or race ends, torcs crashes unexpectedly. The tracks it crashes are e-track 2, e-track 3, e-road, michigan (torcs 1.3.0) and brondehach (downloaded course). This is the error one gets:

*** glibc detected *** /usr/lib/torcs/torcs-bin: free(): invalid pointer: 0x08059998 ***

Curiously, this happens with Torcs 1.2.4 available on the repositories, with 1.3.0 compiled by myself using several different flags and, finally, also happens with the precompiled 1.3.0 package. However, and strangely enough, the precompiled package works like a charm in my Debian testing (lenny) pc. I've also been told that if one points apt's sources to Gutsy and just download torcs 1.3.0 and its dependencies it will work OK. I attach the gdb error log from self-compiled torcs 1.3.0.

As a final note, I'd like to say that I've uninstalled libc6-686 and recompiled torcs to see if the issue lied there, but the error was still the same. As the error was still showing, I finally reinstalled the i686 optimized glibc.

Thanks for your comments,

Miguel

Revision history for this message
Miguel Martinez (el-quark) wrote :

I've found out with the help of the folks at the Torcs Racing Board that the piece of software that was causing problems was fglrx. If I uninstall fglrx and use only the FLOSS r300 driver, torcs runs as well as usual. Does this grant a bug against fglrx?

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for torcs (Ubuntu) because there has been no activity for 60 days.]

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.