eth-janishutz/eth-summaries
1
0
Fork 0
mirror of https://github.com/janishutz/eth-summaries.git synced 2026-03-14 17:00:05 +01:00
Code Issues Packages Projects Releases Wiki Activity

[SPCA] Update code imports

Browse Source
This commit is contained in:
Janis Hutz
2026-01-22 07:35:37 +01:00
parent f92b002524
commit 5dffd7391c
18 changed files with 28 additions and 30 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
semester3/spca/parts/01_c/03_memory/00_intro.tex
View File

@@ -3,7 +3,7 @@ In comparison to most other languages, \lC\ does not feature automatic memory ma
This of course has both advantages and disadvantages.
\rmvspace
\inputcodewithfilename{c}{code-examples/00_c/02_memory/}{00_memory.c}
\inputcodewithfilename{c}{}{code-examples/00_c/02_memory/00_memory.c}
\drmvspace
Notably, the argument \texttt{size\_t sz} for \texttt{malloc}, \texttt{calloc} and \texttt{realloc} is an \texttt{unsigned} integer of some size
@@ -15,7 +15,7 @@ you get undefined behaviour.
\warn{Memory corruption} There are many ways to corrupt memory in \lC. The below code shows off a few of them:
\rmvspace
\inputcodewithfilename{c}{code-examples/00_c/02_memory/}{01_mem-corruption.c}
\inputcodewithfilename{c}{}{code-examples/00_c/02_memory/01_mem-corruption.c}
\drmvspace
\warn{Memory leaks} If we allocate memory, but never free it, we use more and more memory (old memory is inaccessible)