[Insight-users] Curves2DExtractor not working (MinGW & FLTK)

Luis Ibanez luis.ibanez at kitware.com
Wed Apr 8 12:15:32 EDT 2009


Hi Rick,

It seems to be throwing an exception...

At this point I'll suspect that there is a
mix up of ITK versions in your system.

  A) Are you using shared libraries ?
  B) Do you have other ITK libraries in your path ?


Please let us know,


     Thanks


         Luis


------------------------
Rick Giuly wrote:
> 
> Hi Luis,
> It seems that the debug information did not show up in the exe.
> 
> (I've attached the CMakeCache.txt file in case that might be useful.)
> 
> 
> $ /c/Program\ Files/pythonxy/mingw/bin/gdb.exe 
> /o/software/InsightApplications-
> 3.12.0-build-debug/ImageViewer/ImageViewer.exe
> GNU gdb 6.8
> Copyright (C) 2008 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later 
> <http://gnu.org/licenses/gpl.html>
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
> and "show warranty" for details.
> This GDB was configured as "i686-pc-mingw32"...
> (no debugging symbols found)
> (gdb) run
> Starting program: 
> o:/software/InsightApplications-3.12.0-build-debug/ImageViewer/ImageViewer.exe 
> 
> [New thread 5072.0x16ec]
> (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)
> gdb: unknown target exception 0xc0000135 at 0x7c964ed1
> 
> Program received signal ?, Unknown signal.
> 
> Program exited with code 030000000465.
> (gdb) You can't do that without a process to debug.
> 
> (gdb)
> 
> 
> 
> 
> -- 
> -Rick
> 
> Luis Ibanez wrote:
>  >
>  > Hi Rick,
>  >
>  > Just write "Debug" in front of the CMAKE_BUILD_TYPE.
>  >
>  > Then "c" for configure, "g" for generate, and once
>  > ccmake quits, you just type make.
>  >
>  > (may have to do "make clean" first, if makes doesn't
>  > start recompiling).
>  >
>  >
>  > After that you can run the ImageViewer from the debugger
>  > by running:
>  >
>  >
>  >    gdb  ImageViewer
>  >
>  > and typing "run" in the debugger prompt.
>  >
>  > Please let us know what you find.
>  >
>  >
>  >    Thanks
>  >
>  >
>  >       Luis
>  >
>  >


More information about the Insight-users mailing list