[vtkusers] Strange segmentation fault problem, Debian GNU/Linux and vtk

Jason Ruiter Jason.Ruiter at Altarum.org
Wed Nov 13 09:32:45 EST 2002


Attached are the gdb output for both vtk3.2 and vtk4.0.

Any help appreciated here.

Thanks
Jason





On Tue, 2002-11-12 at 21:37, Prabhu Ramachandran wrote:
> >>>>> "JR" == Jason Ruiter <Jason.Ruiter at Altarum.org> writes:
> 
>     JR> I'm running Debian GNU/Linux.  I've tried this on both woody
>     JR> and sid.  (Woody runs Xfree86 4.1 and Sid runs Xfree86 4.2).
>     JR> It happens on both vtk3.2 and vtk4.0.  I get the same
>     JR> behaviour from Nvidia Geforce4 128MB (both the nvidia and nv X
>     JR> drivers) and an ATI Radeon with 64MB.
> 
> Maybe you can run the segfault through gdb and see if that tells you
> anything.
> 
> cheers,
> prabhu

-------------- next part --------------
jruiter at jrr:~/ewnew$ gdb python
GNU gdb 2002-08-18-cvs
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 "i386-linux"...(no debugging symbols found)...
(gdb) run view.py
Starting program: /usr/bin/python view.py
(no debugging symbols found)...(no debugging symbols found)...[New Thread 16384 (LWP 26922)]

(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)...(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)...
Done reading
Color and opacity set
mapper created
Render setup
Starting render
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...[New Thread 32769 (LWP 27089)]
[New Thread 16386 (LWP 27090)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 16384 (LWP 26922)]
0x41617e15 in vtkVolumeRayCastFunction::FunctionInitialize(vtkRenderer*, vtkVolume*, VTKVRCStaticInfo*) () from /usr/lib/libvtkRendering.so.4
(gdb) 
-------------- next part --------------
jruiter at jburns:~/ewnew$ gdb /usr/bin/python
gdb: Symbol `emacs_ctlx_keymap' has different size in shared object, consider re-linking
GNU gdb 2002-04-01-cvs
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 "i386-linux"...(no debugging symbols found)...
(gdb) run view.py
Starting program: /usr/bin/python2.1 view.py
(no debugging symbols found)...[New Thread 1024 (LWP 6915)]
(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)...
Done reading
Color and opacity set
mapper created
Render setup
Starting render
(no debugging symbols found)...(no debugging symbols found)...
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1024 (LWP 6915)]
0x411bcde0 in vtkVolumeRayCastFunction::FunctionInitialize ()
   from /usr/lib/libVTKGraphics.so.3.2
(gdb) 


More information about the vtkusers mailing list