Quote:
Originally Posted by mikewindlake
Is there an ETA on the fix? I just started mentoring (C# developer by day) What do I need to do get fix? Do I need to clone the Eclipseplugins and rebuild? I would like to be able to debug. It sounds like this also is affecting C++ too. We can certainly get the team going without debugging but it will certainly help me understand what's going one.
|
Not sure on overall ETA, although I"m going to try to see if I can get a workaround going tonight if I have time.
The fix to the ant build referenced in this thread that I (and others) looked at is merged here:
https://github.com/wpilibsuite/EclipsePlugins/pull/96 - you can potentially manually update the files in your [home]/wpilib/*/build folders to check out if it gets you any further. However, any of the other issues might require re-compiling the plugin (which I have not attempted yet)
For all the folks saying they're freezing, let eclipse run for at least five minutes to see if you get control back. If you do, check your error log and see if you have symptoms similar to this other thread:
https://www.chiefdelphi.com/forums/s...d.php?t=153511 ... I've got an issue in at
https://github.com/wpilibsuite/EclipsePlugins/issues/99 for what I"m seeing, but I'm still trying to nail down if it's a "just me" or "everyone" thing.
EDIT: Debugging progress last night: no dice yet. I was able to manually coax the RIO into debugging mode by creating the /tmp/frcdebug file and restarting the user code, and got eclipse to connect by manually creating a debug target (with the RIO's address and port). However, eclipse still was giving warnings about line number annotations not being turned on (despite the fact that we have debug="true" in the javac tag in the ant build). Still learning as I go, but I'm worried that I'm getting too far down the rabbit hole in the wrong direction....