Bug 31573

Summary:	XMMS crashes with floating point exception
Product:	Gentoo Linux	Reporter:	Bruce Chiarelli <mano15>
Component:	Current packages	Assignee:	Gentoo X packagers <x11>
Status:	RESOLVED INVALID
Severity:	normal	CC:	sound
Priority:	High
Version:	1.4
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---
Bug Depends on:	30814
Bug Blocks:

Description Bruce Chiarelli 2003-10-20 00:47:28 UTC

Upon selecting the "OpenGL Spectrum Analyzer" visualization plugin in XMMS, it crashes with a floating point exception.

So I fire up gdb:

----SNIP-----
bruce@meros bruce $ gdb
GNU gdb 5.3
Copyright 2002 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 "i686-pc-linux-gnu".
(gdb) file /usr/bin/xmms
Reading symbols from /usr/bin/xmms...(no debugging symbols found)...done.
(gdb) run
Starting program: /usr/bin/xmms
(no debugging symbols found)...[New Thread 16384 (LWP 29565)]
(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)...[New Thread 32769 (LWP 29566)]
[New Thread 16386 (LWP 29567)]
(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)...[New Thread 32771 (LWP 29568)]
[New Thread 49156 (LWP 29569)]
[New Thread 65541 (LWP 29570)]
[New Thread 81926 (LWP 29571)]
 
Program received signal SIGFPE, Arithmetic exception.
[Switching to Thread 81926 (LWP 29571)]
0x43581877 in _mesa_test_os_sse_exception_support ()
---Type <return> to continue, or q <return> to quit---

----SNIP----
Now here's the super-weird part: If I hit enter, followed by 'step' about ten or eleven times, the visualization window comes up and it operates flawlessly! I expect, from the output of each 'step' command, that it is either a problem with CFLAGS or with DRI:
----SNIP----

   from /usr/X11R6/lib/modules/dri/mga_dri.so
(gdb) step
Single stepping until exit from function _mesa_test_os_sse_exception_support,
which has no line number information.
0x43581591 in check_os_sse_support ()
   from /usr/X11R6/lib/modules/dri/mga_dri.so
(gdb) step
Single stepping until exit from function check_os_sse_support,
which has no line number information.
0x435812df in _mesa_init_all_x86_transform_asm ()
   from /usr/X11R6/lib/modules/dri/mga_dri.so
(gdb) step
Single stepping until exit from function _mesa_init_all_x86_transform_asm,
which has no line number information.
0x434e5084 in _math_init_transformation ()
   from /usr/X11R6/lib/modules/dri/mga_dri.so
(gdb) step
Single stepping until exit from function _math_init_transformation,
which has no line number information.
0x434e50a9 in _math_init () from /usr/X11R6/lib/modules/dri/mga_dri.so
(gdb) step
Single stepping until exit from function _math_init,
which has no line number information.
0x4346af3f in _mesa_initialize_context ()
   from /usr/X11R6/lib/modules/dri/mga_dri.so
(gdb) step
Single stepping until exit from function _mesa_initialize_context,
which has no line number information.
0x4346afea in _mesa_create_context ()
   from /usr/X11R6/lib/modules/dri/mga_dri.so
(gdb) step
Single stepping until exit from function _mesa_create_context,
which has no line number information.
0x435b16cc in mgaCreateContext () from /usr/X11R6/lib/modules/dri/mga_dri.so
(gdb) step
Single stepping until exit from function mgaCreateContext,
which has no line number information.
0x43455b0e in driCreateContext () from /usr/X11R6/lib/modules/dri/mga_dri.so
(gdb) step
Single stepping until exit from function driCreateContext,
which has no line number information.
0x4138e017 in CreateContext () from /usr/lib/libGL.so.1
(gdb) step
Single stepping until exit from function CreateContext,
which has no line number information.
0x4138bb7e in glXCreateContext () from /usr/lib/libGL.so.1
(gdb) step
Single stepping until exit from function glXCreateContext,
which has no line number information.
0x4131b49e in get_vplugin_info ()
   from /usr/lib/xmms/Visualization/libogl_spectrum.so
(gdb) step
Single stepping until exit from function get_vplugin_info,
which has no line number information.
[New Thread 98311 (LWP 29572)]
[New Thread 114696 (LWP 29573)]
 
Program exited normally.
(gdb)

----SNIP----

Comment 1 Donnie Berkholz (RETIRED) gentoo-dev

2003-12-29 06:18:59 UTC

If you suspect it may be CFLAGS, that problem is easy enough to eliminate. Change your CFLAGS to something innocent (like "-O2 -pipe") and recompile xfree and xmms, along with whatever other program you may be using for 3D acceleration.

Comment 2 Jeremy Huddleston (RETIRED) gentoo-dev

2004-02-06 20:26:28 UTC

This looks like a problem with GL / drivers and not xmms.  Are you still having the problem?

Comment 3 Brian Harring (RETIRED) gentoo-dev

2004-05-28 11:30:45 UTC

Marking it invalid, reopen if this is still an issues/pops up again.