View Issue Details Jump to Notes ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0001003VTK(No Category)public2004-07-26 13:392007-08-04 16:00
ReporterMaarten De Jong 
Assigned To 
PriorityurgentSeverityfeatureReproducibilityN/A
StatusclosedResolutionno change required 
PlatformOSOS Version
Product Version 
Target VersionFixed in Version 
Summary0001003: Segmentation fault with VolumeRendering example
DescriptionOn a Linux 2.4.26/glibc 2.2.3/Python 2.2.1/nVidia OpenGL 31.23 system, where I have installed VTK 4.2 from sources, I get a segmentation fault if I run the PseudoVolumeRendering.py example from Examples/VolumeRendering/Python/ a little while after the output window is opened. No data is displayed at all, the window remains white until the crash. It seems to be the only example causing a core dump, all the others work just fine (and quite spectacularly so!). Using 'python' or 'vtkpython' has no effect.
TagsNo tags attached.
Project
Type
Attached Files

 Relationships

  Notes
(0001292)
Mathieu Malaterre (developer)
2004-07-26 16:01

Can you rebuild VTK in Debug mode, then run:

gdb python
> r PseudoVolumeRendering.py

And send the backtrace, thanks.
(0001302)
Maarten De Jong (reporter)
2004-07-27 14:39

I assume that by building VTK in debug mode you wanted me to enter 'Debug' on the CMAKE_BUILD_TYPE line? I have done that, and then after installing the debug version did

gdb python

which led to a backtrace which you won't find at all helpful:

(gdb) r PseudoVolumeRendering.py
Starting program: /usr/bin/python2.2 PseudoVolumeRendering.py
[New Thread 1024 (LWP 29623)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1024 (LWP 29623)]
0x420c12c4 in __nvsym14770 () from /usr/lib/libGLcore.so.1
(gdb) bt
#0 0x420c12c4 in __nvsym14770 () from /usr/lib/libGLcore.so.1
#1 0x00000000 in ?? ()

I have tried rebuilding VTK many times, but without success: every time these are all the frames I get. I am not compiling with any optimisation or special options of gcc to disable frame pointers: I made sure that the debug flags are quite vanilla.
(0001303)
Mathieu Malaterre (developer)
2004-07-27 14:43

> which led to a backtrace which you won't find at all helpful

wrong this is very helpful, that means you are using a buggy gl driver. try updating to the lastest one. Or one before, sometime they had bugs between version. Worse case, build Mesa, this will gives you a ligGL.so
And then use
export LD_PRELOAD=/opt/Mesa/libGL.so
to force the use of the Mesa GL library.

I am marking this a non bug.
(0001304)
Maarten De Jong (reporter)
2004-07-27 16:31

Thanks for the input---upgrading to nVidia's 61.06 driver solved the problem. Many thanks for the help, I had absolutely forgotten how old the 31.23 driver had become.

 Issue History
Date Modified Username Field Change
2007-08-04 15:59 Berk Geveci Assigned To Alan Scott =>
2007-08-04 15:59 Berk Geveci Reproducibility unable to reproduce => N/A
2007-08-04 15:59 Berk Geveci Status backlog => closed
2007-08-04 15:59 Berk Geveci Resolution unable to reproduce => no change required
2007-08-04 15:59 Berk Geveci Summary Goodsite => Segmentation fault with VolumeRendering example
2007-08-04 15:59 Berk Geveci Note Deleted: 0008239
2007-08-04 16:00 Berk Geveci Project @3@ => VTK
2011-06-16 13:11 Zack Galbreath Category => (No Category)


Copyright © 2000 - 2018 MantisBT Team