Is there a way to see the call stack that caused the crash in vtk?

[gongwaner]

I was running into crash recently. Usually vtk output window pops up and reports error messages. The errors are usually in the following format:
ERROR: In {path_to_vtk_lib}/somefile.cxx: some error messages…

It doesn’t show me the call stack of this error, therefore it’s sometimes hard to debug such errors.
Is there a way to see the call stack/trace that lead to such errors?

Thanks

[cory.quammen (Cory Quammen (Kitware))]

@gongwaner

It doesn’t show me the call stack of this error, therefore it’s sometimes hard to debug such errors.
Is there a way to see the call stack/trace that lead to such errors?

If you have VTK built in Debug or RelWithDebInfo modes, you can set a breakpoint in your debugger at that error and examine the stack if that breakpoint is hit. The error gives the filename and line number which is the information you need to set the breakpoint.

[gongwaner]

Thanks for reply.I see.