Menu

GSL-library: No symbolic information

Help
2008-01-29
2012-07-26
  • Roosevelt79

    Roosevelt79 - 2008-01-29

    I have a problem debuggin a program with the gsl library on Visual C++ .Net.

    My settings:

    I downloaded the libgsl.a and libgslcblas.a files, as well as the include folder. I changed my project settings that the libraries are found. Up to now, no problem. My program compiles fine and I can access the functions provided by the libraries.

    But when I try to run the program in debug-mode in Visual C++, I got the following dialog box:

    No symbolic information
    xy.exe does not contain debugging information (Symbol information corrupt).
    Click OK to debug anyway.

    Any ideas?

     
    • Roosevelt79

      Roosevelt79 - 2008-01-30

      Thanks for the hint. Meanwhile I fixed the problem by myself.

      I downloaded the sources which include a Visual C++ project file. I opened it, compiled it and got the required libgsl.lib as well as libgslcblas.lib.

      These file work fine!

       
      • Keith Marshall

        Keith Marshall - 2008-01-30

        Looks like you found the appropriate solution :-)

        Just for the record, as I understand it Kees uses the MinGW port of the GNU Compiler Collection to build the GnuWin32 binaries. Even if he had built with debugging symbols enabled, you would not have been able to use it with Microsnot's debugger, for the two compilers use completely different, and thoroughly incompatible formats for the debugging info. To debug binaries built with GCC, you need to use the GNU Symbolic Debugger, GDB, (which of course, AFAIK, doesn't understand Microsnot's debugging symbols). You cannot mix the two incompatible formats of debugging info, with any realistic expectation of usability.

         
    • GnuWin

      GnuWin - 2008-01-29

      The libraries have been compiled without debug information. They would have to be re-compiled to make them useful for debugging.

       
MongoDB Logo MongoDB