prog:dies_und_das
                Unterschiede
Hier werden die Unterschiede zwischen zwei Versionen angezeigt.
| Nächste Überarbeitung | Vorhergehende Überarbeitung | ||
| prog:dies_und_das [2016/12/11 12:21] – angelegt admin | prog:dies_und_das [2020/03/31 12:25] (aktuell) – [State-Machine] admin | ||
|---|---|---|---|
| Zeile 2: | Zeile 2: | ||
| - | **State-Machine** | + | ===== State-Machine  | 
|   * http:// |   * http:// | ||
| - | **Überflüssige Includes** | + | ===== Function Calls ===== | 
| + | |||
| + |    | ||
| + | |||
| + | ===== Überflüssige Includes  | ||
|   * http:// |   * http:// | ||
| + | |||
| + | ===== Reading and writing files/ | ||
| + | |||
| + | |||
| + |   * http:// | ||
| + |   * [[https:// | ||
| + | ===== Type-Casting in C ===== | ||
| + |   * https:// | ||
| + | |||
| + | ===== Pointers in C (Kurs) ===== | ||
| + |   * https:// | ||
| + | |||
| + |   * [[https:// | ||
| + |   * [[https:// | ||
| + | |||
| + |   * [[https:// | ||
| + | ===== Debugging mit Valgrind ===== | ||
| + | |||
| + | Mit Valgrind lassen sich Speicherprobleme und Segmentation Faults untersuchen und finden: | ||
| + | |||
| + | Unix Systeme liefern [[public_v6: | ||
| + | Signal 11 is SIGSEV (i.e. segmentation violation, a memory access bug in your code): 128 + 11 = 139 | ||
| + | |||
| + | |||
| + | |||
| + | <code bash> | ||
| + | valgrind --leak-check=full --track-origins=yes --show-reachable=yes --log-file=valgrindlog.txt  | ||
| + | ./ | ||
| + | -l LIB_PATH1 -l LIB_PATH2 --record-eventlog=false --debug-on-errors=false | ||
| + | </ | ||
| + | |||
| + | |||
| + |   * http:// | ||
| + | |||
| + | ===== Unlesbarer C-Code ;-) ===== | ||
| + | |||
| + |   * [[https:// | ||
| + |   * http:// | ||
| + |   * http:// | ||
| + |   * https:// | ||
prog/dies_und_das.1481458887.txt.gz · Zuletzt geändert:  (Externe Bearbeitung)
                
                