c/c++ fags BTFO
C/c++ fags BTFO
Other urls found in this thread:
play.rust-lang.org
twitter.com
>javalets can't into C
Rust doesn't have this problem :^)
for (;;)
printf("Segmentation fault\n");
here, I reverse-engineered your program
gdb, valgrind.
Werks everytime.
Windows doesn't have this problem.
why would anybody use c/c++ when there is Rust?
>I use Rust
>to stupid too understand Rust
>Rust
>play.rust-lang.org
blocks your path
>printf("%p", this);
>0x0
so this is the power of rustkeks
clang sanitizers, valgrind sucks for stack bugs
>t.
>t. triggered rustfag
Steve klabnik on suicide watch
Just saying, I have encountered JVM crashes while programming in Java too.
Learn how to use pointers/allocate memory properly, then.
>his language is so outdated it was created before memory protection
>it even needs an ancillary tool just to find memory faults
How can you ever recover?
no ancillary tool needed, just your brain, and if you need tools to catch your memory bugs you probably should be using rust :)
tl;dr use rust if you don't have brain
>too dumb to properly manage memory in C
>too dumb to properly use C++
>too dumb to use a memory sanitizer like asan
I bet you're the kind of retard who writes shitty Rust code filled with bugs and exploits thinking you're safe due to memory management, kek.
>getting segfaults in C++
even good C++ code throws segfaults if you fuck up your build script
did a c exercise in school today. task was to write a program that creates 10 process parented to init/systemd (pid = 1). how should i have done this? my retarded solution: create 10 processes using fork(), then kill the first processes so the 10 newly created processes are adopted by init.
That should kinda work, new process should not fall to PID 1 but some of other systemd processes for sure.
>what's gdm
GNOME Display Manager?
If you're too stupid to correctly allocate memory you don't deserve to be called a programmer.
...
you have to go back to india
yes, thats literally the standard daemonization
man 3 daemon might be what you are looking for.
...
i thought this wasn't recommended since it's not standardized in any way
You mentioned that systemd was the parent so I assumed it was a GNU/Linux program seeing as systemd only runs on GNU/Linux. Daemon is part of glibc but not part of POSIX though so if you want to run on non-GNU then you should stick to fork.
oh, i'm not him. i was just wondering.