[QUOTE=KillerJaguar;48827512]gdb[/QUOTE]
using gdb is like using krazy glue to fix a broken vase and gluing your fingers together in the process
[QUOTE=Jund;48829905]using gdb is like using krazy glue to fix a broken vase and gluing your fingers together in the process[/QUOTE]
no that is more like trying to fix anything at all with debug.exe on old windows stuff
or maybe that is trying to fix your kids toy with a blowtorch and burning down the house in the process
[QUOTE=elitehakor;48826721]i was doing socket programming in c in linux and i had to put printf before every line to figure out which line was giving me a segmentation fault
[editline]4th October 2015[/editline]
it was HELL
[editline]4th October 2015[/editline]
i miss visual studio ;_;[/QUOTE]
I do this all the time. Unfortunately, the nature of segfaults is that if they are inside a function, none of the code in that function will execute if there's a segfault, so instead you have to start commenting out every line of code that could potentially be the issue THEN add the printf's.
And yet I prefer to do this than to take the time to learn any IDE or debugger
[QUOTE=Waterpi;48827303]Dumping two semi-relevant videos:
[video=youtube;u2ZYVt8tmPc]https://www.youtube.com/watch?v=u2ZYVt8tmPc[/video]
[video=youtube;hkDD03yeLnU]https://www.youtube.com/watch?v=hkDD03yeLnU[/video][/QUOTE]
This is why I can't watch these shows anymore. The worst has to be Scorpions or CSI: Cyber. I remember an episode where a guy created a circuit board to kill people on a roller coaster, and the "Custom board" was a Raspberry Pi. No Joke.
[editline]5th October 2015[/editline]
[QUOTE=Demache;48829576]Learned to program in C on Linux with GCC. Now using Visual Studio I feel spoiled as shit. You can see the values of all your variables at that current point, and its mostly intuitive to do so, which is really nice for figuring out run time errors that don't necessarily cause crashes, but goofy unexpected output without making tons of printf statements to print it on the screen literally.[/QUOTE]
You have to watch out though. If you program using Visual Studio and compile using GCC (Or G++ for C++), there are a lot of compatibility issues that pop up, and also some issues with variable initialization and garbage collection.
Who even bothers with pointers anymore
[sp]C# masterrace[/sp]
I'm looking at this thread and all of you are having a grand ol' time and I haven't a fucking clue whats going on
[QUOTE=NoOneKnowsMe;48832874]Who even bothers with pointers anymore
[sp]C# masterrace[/sp][/QUOTE]
[url]https://msdn.microsoft.com/en-us/library/y31yhkeb.aspx[/url]
v:disgust:v
[QUOTE=Gwoodman;48826906]why is bret hart supervising developers[/QUOTE]
The truth is that wrestlers are actually the people who were TOO GOOD at their chosen fields. So we, as a society, created wrestling tournaments and federations to keep them busy, to give the rest of us simple apes a chance.
Without these boundaries in place the world would be incredibly different. But for the better? Nobody knows or dares find out.
[QUOTE=Protocol7;48835315][url]https://msdn.microsoft.com/en-us/library/y31yhkeb.aspx[/url]
v:disgust:v[/QUOTE]
If it's marked as unsafe, you generally don't use it.
I don't understand why pointers are such a hard concept to grasp. They're literally just a pointer to a piece of memory.
[editline]5th October 2015[/editline]
[QUOTE=NoOneKnowsMe;48832874]Who even bothers with pointers anymore
[sp]C# masterrace[/sp][/QUOTE]
If you're using objects, you're using pointers.
[QUOTE=itisjuly;48835360]If it's marked as unsafe, you generally don't use it.[/QUOTE]
You pretty much have to in some situations like system calls. (Though I don't know why anyone'd want to do systems programming in C#...)
Sorry, you need to Log In to post a reply to this thread.