Im trying the new source line debugger but dont understand a few things and there is no documentation.

First, I can only see global variables but their values are incorrect, seems like memory address or somethig.

I stop with a breakpoint and try to step through the source but it runs till end.Do I need to mark with breakpoints all lines?

Im very happy with the new IDE. Great work mates!

[ Editado por tolkien 29.03.2018 - 20:33 ]

Quote:


Hi,

Thanks for the encouraging words.It's absolutely true that documentation is severely lacking. It's a pity because there are probably many features that only I know about myself. Problem is that I don't have time or motivation to work on proper documentation (even though I keep telling myself I should). I prefer to code on my spare time.

The debugger is still work in progress and there are many things missing or not fully implemented. Hopefully this will improve over time. As you spotted, proper trace functionality is missing so for now you indeed have to mark set breakpoints (btw, those can be conditional if you want. Use the rmb popup for that).

There's an issue with global variables and they indeed don't show correct values. We didn't have the time to fix this before release.

However, local variables should definitely work. One thing you should be careful about is gcc's optimization options. The DEBUG target uses -Og by default, which I recently discovered to be a bad idea. Better change to -O0 when working with the debugger. This will be the default in the next release. Let me know if that helps or otherwise give me a hint of what kind of code you are testing with.



/Nicholai

Yes...I understand you. Work on documentation is a real boring task! ;)

I have changed -Og to -O0 and I can now see local variables with its true values. Keep this good work Nadir and team!

Well done, 18 years without a debugger was a pity!
SAS/C CodeProbe was already perfect. Finally no stone age debugging anymore!