OK... I found that beast with that debugging option (I actually didn't know about)
I collected an Isosurface and a Contour Plot (from volumetric data) together with the Collect Module. The output was then fed into a SHADE Module. When shading is turned on the SHADE Module crashes and when shading is turned off, it will NOT chrash (but who will need unshaded isosurfaces ,-)). I can live without the Shade Module after an Isosurface, and my problem is solved now, but it is still a miracle for me why it chrashed most of the time, and not always... Anyway Thanks Alex > > It would be a good idea, first, to make sure which module is segfaulting. > You can turn on debugging in the Message window, and a message will be > printed when each module starts. The last is the one thats dying. The > most likely problem then is bad data - you can insert the Verify module in > front of the offending module and it'll do some consistency checking on the > data; that may reveal your problem. > > I'm curious - can you tell us more about the data? Contour plots are > appropriate on surface data, whereas isosurfaces are appropriate in > volumetric data. > > Greg > > Tobias Weissbach <[EMAIL PROTECTED]>@opendx.watson.ibm.com on > 07/17/2001 09:09:04 AM > > Please respond to [email protected] > > Sent by: [EMAIL PROTECTED] > > To: [email protected] > cc: > Subject: Re: [opendx-users] Signal 11 caught > > I still have this problem even with 1.5 GB of RAM. > Any Ideas, what the Problem could be ?? > > Thanks > > Alex > > > > > Hi > > > > I am trying to visualize isosurfaces and contour plots of a 3D data set. > > Displaying the contour plots works just fine, but when I use the > > IsoSurface Modul, > > DX loose the connection to the server and I get a message "Signal 11 > > caught". > > > > I guess that this is a memory problem. Will more memory fix this problem > > or is > > it a bug in the Isosurface Modul. > > > > Any ideas ?? > > > > I am using OpenDX 4.1.3 on Linux box (SuSE 7.1) with 768 MB RAM > > > > Thanks for Help. > > > > Alex
