[Bug 245470] New: Torcs crash
https://bugzilla.novell.com/show_bug.cgi?id=245470 Summary: Torcs crash Product: openSUSE 10.2 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Maintenance AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: vbergae@programo.com QAContact: qa@suse.de When I drive my car in TORCS and I collide with any element TORC exits. My Konsole output: user@localhost:~> torcs Visual Properties Report ------------------------ Compatibility mode, properties unknown. freeglut (/usr/lib/torcs/torcs-bin): Unable to create direct context rendering f or window '/usr/lib/torcs/torcs-bin' This may hurt performance. OpenAL backend info: Vendor: OpenAL Community Renderer: Software Version: 1.1 Available sources: 1024 or more Available buffers: 1024 or more Dynamic Sources: requested: 1003, created: 1003 #static sources: 21 #dyn sources : 1003 /usr/games/torcs: line 52: 10017 Violación de segmento $LIBDIR/torcs-bin -l $LO CAL_CONF -L $LIBDIR -D $DATADIR $* user@localhost:~> -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=245470 mhorvath@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team- |sndirsch@novell.com |screening@forge.provo.novell| |.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=245470 sndirsch@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |vbergae@programo.com ------- Comment #1 from sndirsch@novell.com 2007-02-14 09:58 MST ------- Can't reproduce this. Please start in gdb and provide a backtrace. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=245470 ------- Comment #2 from vbergae@programo.com 2007-02-15 05:43 MST ------- I can't do the backtrace: ---------------------- usuario@localhost:/usr/lib/torcs> gdb torcs-bin GNU gdb 6.5 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 "x86_64-suse-linux"...(no debugging symbols found) Using host libthread_db library "/lib64/libthread_db.so.1". (gdb) run Starting program: /usr/lib/torcs/torcs-bin (no debugging symbols found) /usr/lib/torcs/torcs-bin: error while loading shared libraries: libracescreens.so: cannot open shared object file: No such file or directory Program exited with code 0177. (gdb) bactrace Undefined command: "bactrace". Try "help". (gdb) backtrace No stack. (gdb) quit usuario@localhost:/usr/lib/torcs> ---------------------------------------- what can I do? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=245470 ------- Comment #3 from vbergae@programo.com 2007-02-15 05:48 MST ------- Ok, I'm discover the option -d in /usr/games/torcs o:-). I've launched torcs -d and crashes, here is the output: usuario@localhost:~> torcs -d GNU gdb 6.5 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 "x86_64-suse-linux"...(no debugging symbols found) Using host libthread_db library "/lib64/libthread_db.so.1". (gdb) Starting program: /usr/lib/torcs/torcs-bin -l /home/vbergae/.torcs -L /usr /lib/torcs -D /usr/share/games/torcs (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---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 foun d) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 47988904138400 (LWP 14452)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) Visual Properties Report ------------------------ Compatibility mode, properties unknown. freeglut (/usr/lib/torcs/torcs-bin): Unable to create direct context rendering f or window '/usr/lib/torcs/torcs-bin' This may hurt performance. (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [New Thread 1082140992 (LWP 14456)] OpenAL backend info: Vendor: OpenAL Community Renderer: Software Version: 1.1 Available sources: 1024 or more Available buffers: 1024 or more Dynamic Sources: requested: 1003, created: 1003 #static sources: 21 #dyn sources : 1003 Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 47988904138400 (LWP 14452)] 0x00002ba544c98af0 in ssgBranch::removeKid () from /usr/lib64/libplibssg.so.0 (gdb) usuario@localhost:~> -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=245470 sndirsch@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|sndirsch@novell.com |prusnak@novell.com Status|NEEDINFO |NEW Info Provider|vbergae@programo.com | ------- Comment #4 from sndirsch@novell.com 2007-02-15 07:35 MST ------- Sounds like a bug in plib. Reassigning. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=245470 prusnak@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED ------- Comment #5 from prusnak@novell.com 2007-02-15 10:00 MST ------- I can reproduce the bug. When I go to Sound Options and change Sound System to [disabled] or [plib], the crash does not occur. It happens only if [openal] is selected (and reporter indeed is using OpenAL). So the problem is not collision but sound that is played after collision. I suppose that is the reason why you can't reproduce it, Stefan. I will investigate more, because it may be bug in plib, using openal in a wrong way or in openal, I'm not sure. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=245470 ------- Comment #6 from prusnak@novell.com 2007-02-15 10:24 MST ------- gdb output: Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 1082677568 (LWP 6113)] (gdb) #0 0x00002ae0aabdd1fa in _alFloatMul (bpt=0x238e000, sa=0.347314566, len=6) at arch/i386/x86_floatmul.c:74 #1 0x00002ae0aabd25c9 in _alSourceParamApply (src=0x2aaaabe940f0, nc=2, len=4, buffers=0x2ae0aae12380) at al_source.c:2912 #2 0x00002ae0aabc73c2 in _alApplyFilters (cid=36864, sid=17421) at al_filter.c:420 #3 0x00002ae0aabcab8d in _alMixSources () at al_mixer.c:274 #4 0x00002ae0aabcbc57 in async_mixer_iterate (dummy=0x0) at al_mixer.c:1084 #5 0x00002ae0aabd43c1 in runThread (data=0x2ae0aabcbc07) at al_threadlib.c:19 #6 0x00002ae0aced2f4e in start_thread () from /lib64/libpthread.so.0 #7 0x00002ae0acc4e30d in clone () from /lib64/libc.so.6 #8 0x0000000000000000 in ?? () (gdb) quit -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=245470 prusnak@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED ------- Comment #7 from prusnak@novell.com 2007-02-16 04:48 MST ------- This is a known serious bug: http://www.nabble.com/Two-patches-for-Sample-OpenAL-implementation-(serios-b... Applied patch, tested, fixed in STABLE. Closing. Reopen if update needed for older releases. Thanks. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
participants (1)
-
bugzilla_noreply@novell.com