The current implementation does not set the ack bit
for outgoing data segments and the fin segment.
However, RFC793 states that all segments
should have an ack bit set in order to present a valid
ack nr. in outgoing segments.
Currently, data segments and acknowledgement segments
are distinguished by the existence of their ack bit.
With the new assumption, that both of these types of
segments need an ack bit set, I had to change several
parts of the current implementation to make this
decision by inspecting the payload size.
destiny: added parens
When qemu-i386 shuts down the instance on its own accord, like in the
hello-world example, then the terminal is broken afterwards.
This PR ensures that the terminal flags are restored on shutdown.
Almost everything was build sequentially in RIOT, because we employed
explicit for-loops to build directories (DIRS). This PR makes our make
system use normal dependencies to build directories.
All our compiling rules were duplicated, once for the application, once
for modules. This PR makes the application a normal module, removing
this duplication.
Our buildtests build one project concurrently for multiple boards.
The current creation of the `PROJDEPS` for `test_bloom` might fail if
* board `A` notices that the dependency is missing and gets preempted,
* board `B` creates the dependency and gets preempted,
* board `A` starts the creation but gets preempted in the middle of the process,
* board `B` works with a half complete created file.
This PR creates the dependency in the individual `BINDIR`.
`cpu/lpc1768/Makefile` contains many lines that don't belong into this
file, but the maybe `Makefile.include`. Either way, this Makefile is
never called with these goals.
This includes GNU readline features and debugging.
Build with `make BOARD=qemu-i386 all-debug`.
Run with `make BOARD=qemu-i386 term`.
Debug with `make BOARD=qemu-i386 debug`. The default debugger is `gdb`.
Also supported are `debug-tui` (GDB Text User Interface), `debug-kdbg`,
and `debug-ddd`. Set a breakpoint in e.g. "startup" or "main", and
hit/write "continue".
The debugger can only run with a quite new toolchain (e.g. Debian
testing). Ubuntu 13.10. for example will likely report a crash in GDB
when switching from 16bit code to 32bit code.
