u/stdusrin r/C_Programming • Recommends
Modern C development in Visual studio talk in 2023.
0:00 / 0:00
Modern C development with Visual studio in 2023.
Eskil Steenberg
37K subscribers • 6 videos on Hallway
- Recommended by 1 person: 1 in engineering communities.
- Presented by Eskil Steenberg
- May be out of date. The tools, versions or practices it shows have likely moved on.
Beginner. No background in the topic needed.
41K views3 years ago1 recommendation
Tools and practiceProgramming languagesCVim, Emacs and editorsDebugging
Eskil Steenberg provides a quick overview of how to set up, develop, and debug C code using Visual Studio.
This video is intended for people not familiar with Visual Studio, and gives a quick over view of what it is like to develop and debug C code in visual studio. This video is in no way endorsed, affiliated or sponsored by Microsoft. You can find my work on: quelsolaar.com Socials: @eskilsteenberg Regularly stream on: twitch.tv/quel_solaar Join our Discord at: discord.com/invite/Scg6trNUyWWhy it's here
1 person recommends thisWhat people say. Recommended as a practical guide to setting up a modern C development and debugging workflow in Visual Studio.
Moments people linked to
u/skeetoin r/C_Programming • Mentions
On “Freestanding CHIP-8 emulator written in C”
Specifically `*(volatile int *)0 = 0`, using `volatile` so that it isn't
optimized out. Here's the long story: Assertions should be more
debugger-oriented.
Quick summary: When running on a system with virtual memory, this reliably
brings the program to an immediate, unceremonious stop. It's exactly what
you want when running through a debugger, which is what you [always ought
to be doing]. For example:
int main(void)
{
for (int i = 0; i <= 1000; i++) {
ASSERT(I < 1000);
}
}
Here's what that looks like in GDB:
$ cc -g3 example.c
$ gdb ./a.out
Reading symbols from ./a.out...
(gdb) r
Starting program: ./a.out
Program received…