JUCE and VisualGDB

Sysprogs forums › Forums › VisualGDB › JUCE and VisualGDB

Log In Register Lost Password
Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • February 9, 2016 at 17:57 #7624
    Bagger
    Participant

    Heya all you good people

     

    So I have decided to get a remote debugging tool up and running for projects on embedded linux systems. Problem is that I use projucer to make my programs because I need the libraries and I am working on a very big project right now that have been made with said tool. Projucer makes me able to work on the C++ files on VS (autogenerated VS project) and autogenerates the needed makefile for Linux.

    The problem is that I don’t know how to combine the two tools so that I can debug projects that I made in projucer. I must confess that I am still learning and therefore it might be something very simple in the settings with paths. The closest thing I’ve come to an answer is from the posts from christoph.p who have combined the two tools and it seems like he succeded in it.

    I have been able to remote debug the standard “Hello World” on the Linux system (Intel NUC with ubuntu) from my VS 2015 with VisualGDB, I have also been able to somewhat use the quick debug feature on the projucer project on the system, but with problems (and it is very slow).

    I believe the biggest problem I have has something to do with setting up VisualGDB correctly and the autogenerated makefiles. I know that is not much to start from but I’ve tried a lot of things without success and was hoping to find someone that can show me in the right direction.

     

    Regards

    Bagger

    February 10, 2016 at 15:57 #7627
    support
    Keymaster

    Hi,

    To use VisualGDB with projucer you need to figure out 2 things:

    1. The exact command line to build your Projucer project
    2. The location of the executable it builds

    Once you know both of those, simply select “Import a project built with command-line tools” in VisualGDB Project Wizard and specify the command line and the executable. VisualGDB will automatically create a project that will wrap your projucer setup.

    February 11, 2016 at 10:01 #7633
    Bagger
    Participant

    Wauw that was simple -.-‘

    Thanks a lot man, could have used hours upon solving it but it was far easier than what I thought it would be.

    I ended up simply uploading a test program made with projucer onto the NUC (because I got some problems with the large project) and made sure it could build. I then made a new VS Linux project (VisualGDB) where I imported the existing project on the NUC and gave the permission to work on the folder. Added the destination of the make file and executable, and it worked! \(^.^)/

    So simple yet so frustrating to setup. Once again thanks!

    I’ll look into the problem I’ve had on the larger project and make another post in case I can’t figure out what to do.

     

    Regards Bagger

     

    *UPDATE*

    Everything worked as soon as I gave the debugger root access! Onward to learn how to remote debug more threads.

    • This reply was modified 8 years, 9 months ago by Bagger.
    February 11, 2016 at 10:39 #7635
    Bagger
    Participant

    If anyone has some tips/hints on how to remote debug multi-threaded applications on a linux platform, please throw them at me. 🙂

    February 11, 2016 at 19:58 #7636
    support
    Keymaster

    Hi,

    If you are doing heavy multi-threaded debugging, you may find the Parallel Stacks window usable. You may also find it usable to sketch relations between multiple functions and data objects (e.g. mutexes) via Code Map. VisualGDB actually supports it very well for C++ projects.

  • Author
    Posts
Log In Register Lost Password
Viewing 5 posts - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.