C · EMBEDDED · 1:1 · 60 MIN · FROM €50.00/H
Live with a software engineer from the embedded industry. We debug your segfault, draw the memory layout, and finally make malloc, free and pointer arithmetic feel boring instead of scary.
Anton LIVE Software Engineer · C and embedded · FIAE responds ≤ 2 h , View profile Free first conversation →
Already decided? Straight to a session →
Free intro call, €0 · Single session €59.99/h · First hour €47.99 with code ERSTIS26
Live from a real session
// free in reverse, head goes last void free_list(Node *head) { while (head != NULL) { Node *next = head->next; free(head); head = next; } }
From your first int main() to a small embedded routine that reads a sensor over a register. We focus on what is on your exam sheet or your bench, not on every corner of the standard.
Concrete sessions, concrete artefacts. You decide after the first chat whether we work the full arc or jump straight to pointers and memory.
We look at your exam, your lab task or your firmware. After 30 min we both know whether the gap is syntax, pointers, memory or just unfamiliarity with the toolchain.
Drill the basics without rushing: types, control flow, scope, the build process. Solid base, no quiet gaps.
The whiteboard session. We draw addresses, dereferences and arrays until pointer code reads naturally and *p, p[i] and &x stop being magic.
Stack vs heap, malloc and free, structs and linked lists. Common segfault patterns recognised on sight.
If your context is hardware: bit masks, volatile, memory-mapped registers, ISRs. From datasheet to working blink-LED.
We walk your real task. You leave with code that compiles cleanly, runs and that you can defend in an oral.
I built Study IT because I have seen first-hand how IT teaching at university falls apart.
The people who teach here know code from real projects. Practice decides, not the diploma.
Reach me directly: marcel.schmidtpeter@study-it.education
Ausbildung zum Fachinformatiker im Embedded-Bereich, danach B.Sc. Informatik, heute Software Engineer mit C-Anteilen. Pointer, Speicher, Strukturen und die Schnittstelle Hard- und Software aus erster Hand.
„Mein Ziel ist, dass du Sicherheit im Umgang mit Code gewinnst und Zusammenhänge wirklich verstehst, statt fertige Lösungen zu übernehmen."
One session, an intensive block, or semester support. Same hourly rate, same senior tutor.
One allocation, two snapshots: before the free() and after. What the Java compiler and Python's GC do for you, in C you do yourself. Once you've seen this, segfaults stop being scary.
One allocation, two snapshots: legitimate at t=1, dangling at t=2. Same address, one bug.
Anton · Tutor Memory snapshot · heap lifecycle , View profile free() returns the heap block to malloc. The stack pointer arr is unchanged. It still holds the same address. Hence the name dangling pointer. You can still dereference arr, and the compiler won't complain.
The freed block is still inside your process's address space. The OS hasn't taken it back. malloc just marked it as available. So you read stale values. Works sometimes. Breaks the moment malloc reuses the block for someone else and you read foreign data.
C asks the developer to track lifetimes. free() is just a regular function call. The compiler sees no link between free(arr) and a later arr[0]. Java/Python have garbage collection and bounds checking; in C, that's your job.
Right after every free(), set `arr = NULL;`. The next dereference then segfaults loudly. The bug surfaces instead of hiding. Failing fast beats silent corruption. In a large codebase this saves days of debugging.
That is exactly what we draw in your session: where your pointer points, and where it does not.
30 minutes to talk, then you decide. One session is often enough to flip the mental model. A second one makes it robust.
Career switch into embedded, Programming I, or the apprentice route? We have a page for that.
