examples/gcoap_dtls: Increase stack size

[maribu]

Contribution description

As the title says. The stack size was copied over from tests/pkg_tinydtls_sock_async cargo-cult style. Also some typos in the README were fixed.

Testing procedure

Previously on my Nucleo-F767ZI, the CoAP client triggered the MPU stack guard on sending the DTLS hello. With this, the board no longer crashes.

Issues/PRs references

None

[benpicco]

looks like Makefile.ci now needs an update

[benpicco]

I suppose this is still needed, right?

[maribu]

It is also needed with LWIP=1 actually. I wonder if stack usage of the client can be reduced a bit instead. Overflowing a 1.5 KiB stack is a bit surprising.

[maribu]

I'm cleaning up my stale branches currently. I think this is actually still needed. Any change to get this in? (Once someone fixes the surprising amount of stack consumption, this is a change that is trivial to revert.)

[maribu]

bors merge

[maribu]

bors cancel bors merge

[bors[bot]]

Canceled.

[maribu]

bors cancel bors merge

let's see if we can get three PRs into the merge train.

[bors[bot]]

Canceled.

[maribu]

bors cancel bors merge

[bors[bot]]

Canceled.

[bors[bot]]

Build failed (retrying...):

• Murdock

[bors[bot]]

Build failed:

• Murdock

[maribu]

rebased and ran the tool to update the Makefile.ci

bors retry

[bors[bot]]

:clock1: Waiting for PR status (GitHub check) to be set, probably by CI. Bors will automatically try to run when all required PR statuses are set.

[riot-ci]

Murdock results

:heavy_check_mark: PASSED

965b555d7e098417155fbba8ab0c524028d5b15b examples/gcoap_dtls: Increase stack size

Success	Failures	Total	Runtime
13	0	13	01m:02s

Artifacts

• Documentation preview

[bors[bot]]

Build succeeded:

• Murdock
• static-tests
• tools-build-success

[maribu]

Thx