@@ -47,14 +47,14 @@ you will get an error: `exec user process caused "exec format error"`.
4747We provide a Docker image with the most common developer tools already installed.
4848Download it by running...
4949
50- docker pull ev3dev/debian-jessie -cross
50+ docker pull ev3dev/debian-stretch -cross
5151
5252This will take some time. The download is nearly 1GB!
5353
5454
5555When it is finished, we can give it a shorter name...
5656
57- docker tag ev3dev/debian-jessie -cross ev3cc
57+ docker tag ev3dev/debian-stretch -cross ev3cc
5858
5959{% include /style/icon.html type="info" %}
6060Docker images are immutable. You can always revert back to this image after making
@@ -177,11 +177,7 @@ so that you can run builds without starting a new container each time.
177177Although it is possible to run gdb directly on the EV3, you will quickly run
178178out of memory. To get around this, we will do remote debugging.
179179
180- On your EV3, install ` gdbserver ` .
181-
182- sudo apt-get install gdbserver
183-
184- Now, let's debug our "hello world" program. First, we need to make sure we compile
180+ Let's debug our "hello world" program. First, we need to make sure we compile
185181with debugging symbols (thats the ` -g ` flag). You will need to copy the new
186182executable to the EV3 too if you haven't done the * mounting a remote file system*
187183thing yet.
@@ -193,11 +189,10 @@ computer (or VM) and `3333` is an arbitrary TCP port.
193189
194190 gdbserver host:3333 hello
195191
196- Then back in the brickstrap shell run gdb. ` target remote ` tells gdb to connect
197- to your EV3. Host name resolution seems to have issues in the brickstrap shell,
198- so you are better off using the IP address of your EV3 (192.168.0.100 in this
199- example). And of course, the port number needs to match what you used with
200- gdbserver.
192+ Then back in the docker container run gdb. ` target remote ` tells gdb to connect
193+ to your EV3. If you have trouble connecting by hostname, you can use the IP
194+ address of your EV3 instead (192.168.0.100 in this example). And of course, the
195+ port number needs to match what you used with gdbserver.
201196
202197 gdb hello
203198
0 commit comments