For the Mac users. I tend to use XCode now for just presenting the C files, the colours and such.
I also use vi for editing and do most of the things on the terminal.
On the terminal I use git and make. In most case I start the application with ./wp43s.
Sometimes from the debugger.
For the Mac users. I tend to use XCode now for just presenting the C files, the colours and such.
I also use vi for editing and do most of the things on the terminal.
On the terminal I use git and make. In most case I start the application with ./wp43s.
Sometimes from the debugger.
True, it works on the Mac, but there is still the same crashing and recently endless loop issue for huge long integers that seems hard to find on the DM42.
Currently on Mac I compile via make and the the terminal. I use Sublime Text for editing as the colours and IQ is good.
On my Mac I have no debugger working to trace, step and check variables. Do you know how to install that? Is it even possible?
The big pain often is XQuartz which very often stops working, and does not want to open a screen when you start the wp43* from the terminal.
The trick is adding:
CFLAGS += -g -O0 -v
to Makefile
Then 'make rebuild'.
Then run the app from the debugger: lldb wp43s
Then type r for run. The calculator now comes up and you can do whatever you want to test.
If the application crashes, type bt (back trace).
This will tell you exactly where the app crashes!
After that either type qy (quit, yes) or r (run) for another go.
(-g: generates additional symbolic debugging information for use with gdb debugger.
Apple does not use gdb, but instead lldb which is more or less the same.)
Type man lldb for more stuff you can do with the debugger.
The trick is adding:
CFLAGS += -g -O0 -v
to Makefile
Then 'make rebuild'.
Then run the app from the debugger: lldb wp43s
Then type r for run. The calculator now comes up and you can do whatever you want to test.
If the application crashes, type bt (back trace).
This will tell you exactly where the app crashes!
After that either type qy (quit, yes) or r (run) for another go.
(-g: generates additional symbolic debugging information for use with gdb debugger.
Apple does not use gdb, but instead lldb which is more or less the same.)
Type man lldb for more stuff you can do with the debugger.
Thank you so much. Can't wait for the next crash ...
A tip. Often I use 'make' and then I start the app a lot.
Or first 'make' and then 'lldb wp43s' (WP43S in the debugger).
On the terminal, enter 'make && ./wp43s' or 'make && lldb wp43s'.
It does a make and if there are errors, it stops.
If no errors are in the 'make', then it will start the calculator.
