>Segmentation fault (core dumped)
Segmentation fault (core dumped)
Nathaniel Peterson
Landon Bennett
Just use gdb
Noah Anderson
Just use printf
Jayden Smith
Just use Windows
Ryan Johnson
Just patch it
Austin Flores
Just be yourself
Lucas Nelson
Just use macOS
Ryder Reed
just do it
Lucas Morales
>dinamically allocating memory for matrices in C
>int ** m = (int **) malloc(N*M*sizeof(int));
I spent more than I want to admit until I noticed
Leo Williams
Use valgrind
Julian James
just copy something from stackoverflow
Grayson Edwards
just
Liam White
This is why UNIX sucks. Portability was a mistake.
Levi Bailey
On Windows, you'll instead get something along the lines of "program has stopped responding" when a program segfaults. It's still a segfault, however.
Evan Robinson
This is what I like aboutg C. Those who persevere become more careful programmers.
Kayden Foster
I have a lot to say about this and difficulty in programming in general, but, well, you definitely won't see soyboys programming in C.
Eli Foster
>Trying to reach an area of memory not belonging to you.
What are you, a thief?
Aiden Garcia
manage your memory better retard
Kayden Mitchell
Your autism know no bounds, user.
Mason Garcia
just use LLDB
Carter Fisher
just use Ruby
Christopher Turner
this
give it back op
Nathan Ross
Xorg :0 -configure
Segmentation fault
Fucking arch.
Ayden Foster
just use java
Elijah Baker
>NullPointerException
Aiden Cox
>Those who persevere, live on to contribute industry crippling attack vectors to malicious actors around the world
ftfy
Ryan Hall
>casting malloc
>in C
Colton Taylor
give it back jamal
Mason Morris
>./a
>bash: a: No such file or directory
>ls
>a
Landon Garcia
Observe the only specimen on Jow Forums that got beyond hello world in C.
Evan Gray
>chmod +x a
I think there's an obscure reason why it says that. Pretty sure that it's a bug that got promoted to a feature tho.
Brandon Fisher
It says that when it's not compiled on the same architecture as it's running (64bit executable on 32bit machine)
(Correct me if I said that wrong, I'm having trouble finding the right words rn)
Levi Rogers
protected mode was a mistake
m68k will rise again
Daniel Sanders
this
Henry Garcia
>purchased Ryzen
everyone point and laff.
Gavin Martin
Yeah, you can't run a 64-bit program on a 32-bit system; however, you can do it the other way around.
Camden Hernandez
It happens when the program requests to be loaded using a dynamic linker that doesn't exist on your system. The kernel tries to open the requested linker, fails, and reports the "file not found" error back to userspace.
32 vs. 64 bit issues come from the fact that the dynamic linker has a different name on each architecture (ld-linux.so.2 vs. ld-linux-x86-64.so.2).