[vtkusers] dbx dumps core on Forte Developer 6

[Robert Belleman]

Johan,

Make sure dbx doesn't find Vtk libraries on other locations.
Type 'ldd Cube' to see where the loader finds the dynamic libraries. If
these differ from the locaton specified in the Makefile to Cube, use the
environment variable "LD_LIBRARY_PATH" to explicitly tell the loader
where to get them (both at runtime of Cube, and at the commandline to dbx
if you are going to debug).

I.e.:

env LD_LIBRARY_PATH=/path/to/vtk/libraries ./Cube
env LD_LIBRARY_PATH=/path/to/vtk/libraries dbx ./Cube core

-- Rob

-- 
[] Robert Belleman         X  Section Computational Science            []
[] robbel at science.uva.nl  |X| University of Amsterdam, the Netherlands []
[] tel: (+31) 20 525 7510  X  http://www.science.uva.nl/~robbel/       []

On Thu, Jul 19, 2001 at 10:26:16AM +0200, Johan de Jong wrote:
> Hi,
> 
> When I attempt to debug a VTK program (for example the demo 'Cube') dbx
> dumps core.
> I compiled VTK and the demo with the WorkShop 6 C++ 5.1 compiler (Forte
> Developer 6) on Sun Solaris 8.
> 
> Here's the dbx log:
> 
> (dbx) cd /user/jong/vtk/vtk3.2/vtk/vtkunix/graphics/examplesCxx
> (dbx) debug /user/jong/vtk/vtk3.2/vtk/vtkunix/graphics/examplesCxx/Cube
> Reading Cube
> Reading ld.so.1
> Reading libVTKPatented.so
> Reading libVTKImaging.so
> Reading libVTKGraphics.so
> Reading libVTKCommon.so
> 
> dbx: internal error: signal SIGSEGV (no mapping at the fault address)
> dbx's coredump will appear in /tmp
> 
> Any sugestions ?
> 
> -- 
> Johan de Jong
> Philips Medical Systems