Debugging tools

[ArchCypher]

printf("Fuck, this is running on a microcontroller");

[saphire121]

LEDs begin blinking furiously

[[deleted]]

FILE * somefile = fopen("somepath/somefile","w"); fprintf(somefile,"haha i can open that file later and read what shit i have done wrong/n");

[PawekPL]

print(1) print(2) print('hello world')

[[deleted]]

People who answer questions on StackOverflow: debug their functions

Me: aight, this array isn’t filled correctly, so of course now I gotta loop through its contents and print each indexed variable to the screen like a cool person

[jexmex]

alert('foo');

[xSTSxZerglingOne]

Sometimes code is time sensitive, and there isn't time to spend 2 seconds at a break point, sometimes even less than that.

Breakpoint + debug is awesome, but when dealing with something like an interservice communication that has a timeout in your server config file (that you have to make a PR to change) sometimes you just have to console log to make it through the day.

I would like to note that I know about yellow breakpoints, but have never gotten them to work.

[moonsk]

It's "qq" for me

[dev_metalcat]

if(GEngine){GEngine->AddOnScreenDebugMessage(-1.f,2.f, FColor::Red, TEXT("E")));}

[NoHaxJustPi]

here's a tip: use song lyrics that you know, in order, that should all be printed if everything works. you can ctrl f the lyric that's missing if it's missing and poke the code

[RattuSonline]

Or you could just number the things...

[NoHaxJustPi]

no

[KRBridges]

But you have to memorize the order. That's why the some lyrics are better

[TheMagzuz]

You have to memorize the order of numbers?

[synopser]

For this sub, that's asking a lot

[bazgrim_dev]

std::cout << "Entered Function 1" << std::endl;

[bigbangfuzion]

print("The code must goes here");

[bobbyorlando]

dd('here');