John24

Forum Replies Created

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • in reply to: VisualGDB error: cc1plus.exe: out of memory allocating #7550
    John24
    Participant

    I found that the issue was the compiler needing more than 2Gb of memory. Fixed it telling Visual Studio 2013 to be /LARGEADDRESSAWARE (Handle Large Addresses). This can be usually done in multiple ways but because of using VisualGDB you can’t change linker settings in the properties sheet.

    This can be done using the common prompt in windows.

    1. Open Common Prompt
    2. Go to visual studio binary folder “cd C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\bin
    3. Run “editbin /LARGEADDRESSAWARE “C:\SysGCC\raspberry\libexec\gcc\arm-linux-gnueabihf\4.9\cc1plus.exe” command with the location of GCC compiler executable location.

    This should fix the problem.

    • This reply was modified 8 years, 10 months ago by John24.
    in reply to: VisualGDB can't debug parts of a library #7542
    John24
    Participant

    Hi Baxis,

     

    Thanks for the replies. Thanks to you I was able to spot what the issue was. At the end of library source files for PCL there is a #ifdef PCL_NO_PRECOMPILE statement which will not recompile the code if changed unless PCL_NO_PRECOMPILE is defined in the code.

    So it’s all good and working now 🙂 Thanks for your help, I really appreciate it!

    in reply to: VisualGDB can't debug parts of a library #7525
    John24
    Participant

    Hi Bazis,

    Thanks for your reply 🙂

    So running “info shared” gave me the Shared Object Library locations and I found the libpcl_filters.so file.

    Running “nm libpcl_filters.so | grep TestFunc1()” gave result of “no symbols” even when I tried to find a library function I had “no symbols result”. I assume I am doing something wrong.

     

    Because I am cross compiling on my machine and sending just the binaries to the Pi I assumed that files only on my machine need to be changed.

    I do apologise if I am doing this all wrong.

     

     

    in reply to: VisualGDB can't debug parts of a library #7506
    John24
    Participant

    Ok I have made sure that modified library code is in both my PC and Raspberry Pi. But it seems that the project is only using already compiled library .so files instead of my changed files.

    • This reply was modified 8 years, 10 months ago by John24.
    in reply to: VisualDGB error MSB3073 including a library #7394
    John24
    Participant

    That was the output window content.

     

    But after trial and error I found out that there was a dependency issue, when I included PCL library it needed to include another library. All fixed now 🙂

Viewing 5 posts - 1 through 5 (of 5 total)