Re: GCC 4.8 Toolchain
 

First off, I haven't done any debugging with this toolchain, so take anything I say with a grain of salt. Patrick probably has the best understanding of how this all works - I suggest you try and contact him, and then document your procedure so others can replicate.

There are a few things I can say though.

1) There might be a problem using WindRiver for debugging, as the stock toolchain uses gcc 3 and this toolchain is gcc 4. There are ABI incompatibilities between the two versions, but I do not know if these incompatibilities have a significant impact on debugging. It's worth a try though.

2) There is a decent amount of information on the Wiki, but the debugging section is more notes-style than tutorial-style, so it might take a while to figure out. If you do figure it out and have something to add, we would of course appreciate that.

3) You might need to add -g in CMAKE_CXX_FLAGS - I don't recall if CMake puts it there by default.

Re: GCC 4.8 Toolchain
 

I had mixed results with debugging, but I was finally able to find the bug. I quickly found that I couldn't get gdb to work -- it hung at 'enabling debug mode', and so I didn't waste much time with that. However, I was running the command from a linux VM running on an OSX host, so take that with a grain of salt.

By setting the CMAKE_BUILD_TYPE to Debug, I was able to do Debugging via Wind River. I had to manually load the symbols and source code before it would work, but when I clicked pause or whatever it would show local variables and the stack trace and such. Oddly enough, when everything was hung at a semTake call, Wind River could not successfully show the entire stack, but would only show the OS stack pieces, and couldn't show the stack back into the task's code.

I was finally able to get a full stack trace via netconsole. By entering 'tt <taskid>' at the netconsole prompt, it was able to provide a full stack trace, and I was able to identify my hung threads... which ended up being a nasty bug in NetworkTables (forum post if you're interested).

Re: GCC 4.8 Toolchain
 

We competed in a week 1 regional using this toolchain on a Linux Mint distribution. We had no issues with the build environment. Worked great. Super fast compiles and deploys. We didn't need any debugging beyond printf.

Re: GCC 4.8 Toolchain
 

Glad to here that there were no issues! Did you build the packages yourself or did you use the repository (just curious)?

Re: GCC 4.8 Toolchain
 

We used your repos. Thanks for keeping them updated.