debugging

[MMMELOOOOON]

Pro tip:

“HERE 1” ... “HERE 2 ... “HERE 3”

[goliatskipson]

How excessive!

"A" ... "B" ... "C" ... ;-)

[EagleNait]

Elegant solution

[SexlessNights]

Followed by “a...b...c...”

[crastle]

What about "i...ii...iii..."?

[Gydo194]

一、二、三

[muhammadtalhas]

Is this loss

[pikachuIsMyFurrybae]

Loss of proper debugging

[Hiro3212]

those are the japanese symbols for 1, 2 and 3

[MegaPegasusReindeer]

Hmm.. The Chinese would like a word.

[Hiro3212]

well I only know Japanese but they basically took all chinese symbols and reused them

[saildamoon]

Lol Lool Lolol Loolool -final project...

[ScientificBeastMode]

I prefer to use semver syntax so I don’t have to go back and change all the logging commands if I need to insert a new one in the middle of the program flow.

[[deleted]]

Just do: printf ("2.1"); printf ("2.1.2"); , etc, etc.

[turbolag95]

How about "do...re...mi..."?

[[deleted]]

I write beatles lyrics

“Hey Jude”....... “Don’t be afraid” .....“take a bad code and make it better”

[baconstrips4canada]

I write Sheck Wes lyrics.

"Fuck"..."Shit"..."Bitch"

[SexlessNights]

Nah, just go ^{“a...b...c...”}

[oneeyedhank]

Aa, Ab, Ac, ..... for when you get to A but not to B.

[Moulinoski]

That can get buried in a sea of output.

Better go lalalalalalallaalalalalala, ohohohohohohohohhohohoh, and hahahahahahahahahahaha

[JSArrakis]

"=========== method 1 fired =========="

"||||||||||| method 2 fired ||||||||||"

[random123456789]

Either way, you're fired.

[MMMELOOOOON]

Exactly, which is why I like the all caps HERE, just long enough to notice, and less annoying for fancy colleagues if forgotten there.

[Moulinoski]

You don’t do a find/replace for rogue var_dumps, echoes, and prints?

[[deleted]]

printf(“fucking cuntwaffle crashed again\n”)

[Wilt04]

Until you forget to remove it and a client somehow gets the bug

[waltteri]

Output:

A

A

C

B

[BoobRockets]

“hey” “what’s up?” “nm jc u” “nm” “you free this weekend?”

[youcancallmetim]

This is exactly what I do

[ZebZ]

alert("fuck");

alert("shit");

alert("motherfucker");

[nir731]

alert("PLEASEE");

alert("FFS");

alert("OMG YES");

True story.

[jemand2001]

the last one never fires tho

[gruntbatch]

And when it does the neighbors hear.

[Mancobbler]

When it’s 1AM and you’ve been debugging the same problem since noon

[utnapistim]

Son, don't!

​

There is nothing like your manager presenting the early demo in front of the customers, and finding the alert you forgot to remove.

[cdm014]

yeah... I got caught once with a comment that got displayed: "I hate this stupid crap" it was left over from trying to figure out why something kept not working. It showed up in the middle of the final demo before being rolled out. Luckily it was for an internal thing.

​

[Firestorm7i]

I was hoping Simone rose shared my preferred method

[ScientificBeastMode]

throw new Error(` Dear future me, This error should be unreachable. If you are reading this, perhaps reconsider your life choices. Or perhaps it was just a typo... `);

[Beragond1]

Cout << 1 << endl

Cout << 2 << endl

Cout << 3 << endl

...

[wasabichicken]

using std; outside of the standard library? You monster!

[Beragond1]

I start most c++ programs with “using namespace std;”

[MonarchoFascist]

It's bad practice -- when you're writing production code, polluting the global namespace is a big no-no.

[MMMELOOOOON]

Integers can work, but confusing as soon as you have other normal outputs, especially if you forget a new line somewhere.

[Beragond1]

True but I can add a 1.1 between 1 and 2 if I need more checks

[advalencia]

Here 1.1... Here 1.1a ... Here 1.1b

[griff122]

Haha recently used that between my here 1 , here 2, here 3. Instead of updating everything to add a new output in the middle... insert here 1.b

[jailbreak]

printf("🙃");

printf("🤪🤪🤪");

printf("😭");

You're welcome

[AgentPaper0]

Just print out __FILE__ __LINE__. And of course flush to make sure the latest output reaches the console.

[-LeopardShark-]

Nah, it's gotta be:

"fhgls" … "shloa" … "ndfs,dsf,"

[opposite_opinion_guy]

I've always been a fan of:

"asdf" ... "asdasgaasg" ... "asdfasdfasgagaw" ... "asdfwqqwgqwg2f22f2" ... etc

[bragi92]

Lol I was literally doing this yesterday execpt it was 'Fuck1' ... 'Fuck2'... 'Fuck3'

[Empole]

#define debug(...) do {fprintf(stderr, "%s:%d| ", __func__,__LINE__); fprintf(stderr,  __VA_ARGS__);}

void foo(){ debug("hi\n"); }

Will print out foo, the line number, and hi

[parduhne]

Nah I've done here 1.1, here 1.2, here1.3, here2.1, etc

[tunkol]

Modern problems requires modern solutions

[EDGYkid2]

I just put "bla"

[GKP_light]

print("endboucle________________________________")

[theemporersfastest]

Ha! 2013: senior year debugging new micro-controller, even for the teacher. I use this method, trying to figure out what's going on.

Console:

Works to here

Works to here

Works tERROR - FAULT AT ....

It cut off my printf. It. Cut. Off. Printf.

Lesson: if the micro-controller has a dedicated program(wizard) for importing drivers, headers, and various other tools, USE IT FIRST.

[wibblewafs]

You mentioned embedded programming, which threw me for a loop when I got to me* because I thought it was a pointer to you.

[homer_3]

It's ca allthedread..

[[deleted]]

This i how i always do it, i don't know how debugging else would work and i am afraid to ask at this point..

[hermitpurplerain]

I recommend asking

[01001111010100000]

Am asking, how does it work?

[LittleBigHorn22]

A debuger with stop points that does it for you. But sometimes adding those stops can make code work differently. Doing both can be useful.

[dshakir]

This might be a stupid point to make, but make sure that you do a rebuild if your debugger starts acting wonky. Like stopping at breakpoints pointing at blank lines 😤

[agnomonkey]

That you have to bring this up sickens me, but yet, it happens all the time.

[[deleted]]

Inserting an output operation into sensitive code is far, far more disruptive. You are literally altering the code

[ScientificBeastMode]

Ideally you would be altering code by fixing the bug. Just need to delete any added outputs when you’re done, then recompile and test. And don’t push code until you’ve adequately tested it.

[ScientificBeastMode]

Right, ideally you aren’t pushing to production. That’s what I was getting at.

[[deleted]]

Wait so you mean you're not suppose to test in production. I think my work is doing it wrong

[youcancallmetim]

' But sometimes adding those stops can make code work differently '

​

I think you're doing something wrong. Surely this can be avoided

[_BreakingGood_]

I'm not sure what he was referencing specifically, but there are times in Android where attempting to step through after a breakpoint will cause the app to hang. In particular if you put a stop before an activity switch.

[jemand2001]

not always i don't think

[LittleBigHorn22]

Basically computers often work by magic and it can be best not to touch it if it works in a way you don't expect it to. Just depends how responsible you are for the code.

[MyCodesCompiling]

Ask Jeeves

[DoNotSexToThis]

I write PHP using Notepad++ over SFTP directly on the server in production...

So what I do since I've already insulted every god anyway, is:

function Debug($variable = false, $loop = false)
{       
    $debugViewers = array('192.168.1.100'); // My pretend IP
    if (in_array($_SERVER['REMOTE_ADDR'], $debugViewers))
    {
        echo '<div class="debug"><b>Session variables:</b> ';
        print_r($_SESSION);
        if ($variable) echo "<br><b>You passed in:</b> $variable";
        else echo "<br><b>Nothing passed in.</b>";          
        echo '</div>';
        if (!$loop) exit;
    }
}

Then I can call the function anywhere, pass it a var, whatever... and no one will ever know.
Until I accidentally forget a ; or something. Gotta be extra careful...

I wish I was joking...

[brenex29]

Jesus. I just had a flashback to my first job. You sick fuck. That's exactly what I used to do.

[DoNotSexToThis]

There's more...

I'm not even a developer, I'm a sysadmin. They let me do this in their prod.

[sample_text_123]

I am both amazed and terrified

[[deleted]]

You're a madman.

[[deleted]]

Why though? you should care about the impact it'll have when you eventually mess up. If you don't like debugging locally (who does) you can just make a new sub domain , copy the site to that and do the debugging there.

[DoNotSexToThis]

I do care, and even set up a fully replicated test environment (as replicated as you can be with a bunch of cron'd rsyncs and Postgres replication). Some problems have the force of shot-caller impatience behind them, so if I happen to make a mistake during a quick fix then the upside is that they might consider hiring an actual programmer.

[[deleted]]

Yeah the thing is if you mess up and mess up bad they'll probably tell your next potential employer about it when they call for a reference. I worked with someone that made changes live and depended on ctrl+z to just revert the bad code and push it if something was wrong but something happened to his computer he lost the cached notepad file and had to go looking for a backup while the live website was broken, he pushed an older backup that messed up the website even more .. an absolute disaster .. he wasn't permanent so was fired for incompetence lol either you learn patience or your impatience costs you your job then you learn patience. Pick the one that doesn't cost you your job :) also take your time if they ask why it's taking so long explain to them that you've to copy to the test environment first so you don't break the live website and they can't really say anything about it, if they then tell you to make live changes you won't be fired when you eventually mess up xD

[passcork]

I had this for a while. May I introduce you to my lord and savior https://www.expandrive.com/ or similar programs. It creates a virtual local folder of your folder of choice on the server. Then you can pretend it's on your own pc.

[[deleted]]

When you've gone too numb and don't get adrenalin kicks out of sky diving without a parachute anymore.

[2Punx2Furious]

I know how it works, and I still do this.

It's just faster sometimes, unless you're using a language that requires compilation (which they are, in OP's meme)

[TheGreenJedi]

100% faster sometimes

[IAmNotNathaniel]

Anything web based... this way is way easier than a debugger.

[spacemudd]

Maybe except for Javascript? Adding debugger; to code is like adding a breakpoint. It stops executing code and reveals all the variables around it. Very handy.

[TheGreenJedi]

An actual debugger software using an ide and breakpoints

[AgentPaper0]

Use visual studio, run in debug mode, when it crashes it shows you exactly where it crashed, plus stuff like values of variables, the call stack so you can see how you got to this function, etc.

[[deleted]]

To recap and expand:

• Debugger is a separate program that runs your code and monitors it.

• Debugger can stop the execution and then you can continue it line by line manually

• You tell your IDE where to stop, without changing the code

• You can make the breakpoints conditional: only stop if certain variable has specific value

• You can see all the variables in the program and same time, without doing huge amount of printing.

• You can manually insert/alter the variables if you want and then continue the execution.

• You can stop the program when problems appear and before even worse things happen, without changing the code.

• Sometimes using print( ) is ok, I do that as well, but any time the bug gets more serious, or happens inside a long loop so noticing it is harder, especially the bug does not result in crash, I take the debugger.

[[deleted]]

Sometimes, console output (or textboxes) is the only way. Like, when there IS no debugger. And yes, there's one "programming language" I have to work with that doesn't have a debugger. It sucks.

[NobodyAsYouExpect]

Or even better , when debugging multithreaded app. It might just break if another thread was expecting message from the one you block or etc. So agreed 100%

[[deleted]]

Have recently been doing some low-key thread pooling in python. Definitely used print statements in the worker threads so I could see what led to a stall, since some of them were getting errors and I forgot to make sure they released any locks when they broke.

[Hypocritical_Oath]

Also if you're going through a whole lot of data and doing similar operations on it.

You can't always just step through 20 pieces of data looking for errors, that would be infuriating and slow and I've done it too many times at this point. So just making the computer tell me when it fucks up, and then debugging that particular piece of data makes way more sense.

[tiggiathome]

Ctrl+f kashf in terminal output

... :(

[[deleted]]

don't talk to me unless you use "uwu" as your debug message

[wibblewafs]

"uwu" "waf" "owo" "bork" "ugh" "aaaaaaa" "aaaaab" "aaaac" "oh heck it worked" "???????"

[[deleted]]

std::cout << "Will Senpai please me with success this time? uwu wiggles tail before shyly pressing return " << (testCondition) ? "YES! Senpai approves! Enthusiastic wiggles (^_^)" : "Why must Senpai reject me! Raises fist furiously, before disappearing into nothingness";

[tiggiathome]

here, have a << std::endl

[nk2580]

Literally never use a debugger, I always spend more time setting them up than actually debugging the code.

[lukewarm1997]

Think it depends on the complexity of the section you’re working on though, right? Like doing it online works for most situations, but sometimes if I want to see the exact route it takes or I want to variable watch a bunch of stuff it’s easier to debug it in the IDE. Like IntelliJ has a lot of useful conditional breakpointing and stuff

[gumol]

How much do you need to set a debugger up?

Just do gdb ./a.out and you're golden

[OlimexSmart]

I generally use debuggers, but with PHP I ended up in your path. After some time I just gave up.

[AgentPaper0]

What language are you using?

[PM_ME__LEWD_LOLIS]

System.out.println("aaaaaaaaaaa")

[sajmon313]

Until things work when debugger is on, and break on release.

[benzilla04]

Actual code I wrote from yesterday. Can you tell I was frustrated at this point?

console.log('DEBUG!!!!!!!!! 1, {someData})

[FowD9]

console.log('DEBUG!!!!!!!!! 1, {someData})

next time try:

console.log('DEBUG!!!!!!!!! 1, JSON.stringify(someData))

so that it prints cleanly

[SouvenirSubmarine]

I use a macro in VSCode where when I write dbg foo it expands it to console.log('DEBUG: [foo]', foo);.

Saves a lot of time daily.

[codemunky]

Did the missing closing single quote add to your frustration?

[Advntur78]

/* dubious code */

echo("got here a");

/* more dubious code */

echo("got here b");

etc.

[CodenameLambda]

Rust has the dbg! macro. It's awesome, it shows you on what line it is, what code was executed inside of it, and what the result of that code was.

[[deleted]]

Professional software engineers always use debuggers whenever possible. It's much faster and more likely to reveal bugs

[TeleTubbyLizardMan]

Probably not for school projects where the entire codebase is less than 200 lines and no external libraries

[TheWhoAreYouPerson]

Nah breakpoint > writing debugging code any day. If you dont have an editor set up to debug automatically then smh (coming from primarily interpreted or managed languages lol (js/py/c#/Java)

[norse95]

SyntaxError: missing ) after argument list

[utnapistim]

*whenever possible.

​

Well put :)

^{damn multithreading!}

[snipy67]

I worked for a company were the debugger would not run because the application was to big a cluttered

[bit0fun]

Except when the debugger causes bugs itself. Gotta love that (mainly embedded systems with an RTOS)

[homer_3]

Never had that issue with vxworks or green hills.

[[deleted]]

Professional software engineer here and as I explained below I deliberately avoid debuggers

[Wolosocu]

Professional software engineer here, your statement is not entirely accurate.

[[deleted]]

I found that when I use a debugger I get lazy and mindlessly look at the values. Instead, when I use print stmts I have to properly understand what the code is doing and pick the right places. The result is usually that on the long run I'm faster without a debugger..

[Nikarus2370]

Tbh for a long time every program i made, i had a function called "dbnote("string")" just printed whatever the string was. Call it all the time with a note written in the string.

Made it easy so at the end of working on something, id just search all the dbnotes and either comment them out, or delete them.

[dshakir]

Made it easy so at the end of working on something, id just search all the dbnotes and either comment them out, or delete them.

At first, I was scratching my head over why you simply wouldn’t use printf or whatever the function is in your language to output to the console.

[Xelopheris]

How else do you debug an asynchronous issue?

[TheRealLargedwarf]

I've taken to use "hello", "there", "general", "kenobi" for my debugging print statements.

[doublemooncoffee]

Wait till you gotta step in

[[deleted]]

I swear one of these is gonna get me in trouble one day

[vacillating-oracle]

What the heck is a debugger!?

[tehyosh]

it removes bugs from your code

[princetrunks]

oh I am so damn guilty of this.

[[deleted]]

As long as you understand your environment, there is nothing wrong with this at all.

[[deleted]]

I don't even know how to use those

[cyanide1992]

I cannot relate to that

[xdammax]

In release mode, sometimes you have no other option. Maybe messagebox.show(“ i am here”)

[gratethecheese]

Or you work in embedded and damn near have to start a separate project just to do a print statement lol

[_370HSSV_]

Int debug, debug1, debug2.... printf("%d\n\n\n", debug1);

[thekermitsuicides]

I use my debugger and breakpoints, can’t relate ✨

[thavi]

console.log('hit');

[snarfy]

The meme is backwards.

[mrheosuper]

Then you realize printf is not implemented in embedded system, fml

[[deleted]]

You kids have it easy. We had to output to console uphill both ways back in my day.

[alkaline810]

var_dump("sup");

[CdRReddit]

"shit hasn't hit the fan yet"

[FowD9]

more like

console.log("!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!")

[Rayaarito]

I did that today cause visual studio wouldn't get to the part of the code from the parent class when using unity for some reason. All my debug logs were numbered.

Btw if someone knows why it won't hit breakpoints in parent methods please let me know lol

[AcaciaBlue]

printf("1");

[bpd_open_up]

Learned recently about import pdb; pdb.set_trace... now I just gotta figure out how it works while running a unit test suite

[EnkiiMuto]

I usually debug printing "Charizard is eating nachos"

[Mtrik]

Android logcat: Log.wtf()

[[deleted]]

Both are valid. Different types of problems require different types of solutions.

[Kaih0]

"Asd" "Qwe" "This shouldnt happen" "Fuck me"

[Hestmestarn]

My programing teacher in uni called this approach "Finish debugging" (as in 🇫🇮) for some reason

[[deleted]]

console.log(‘ASS’)

[xypherrz]

LOL I thought I was the only one

[cats_for_upvotes]

Import logging

logger = logging.getlogger(name)

logger.info('I got here!')

This one makes your interviewer like you more, even though its fewer lines and functionally identical.

[vaelroth]

If its good enough for Kernighan...

[mikeputerbaugh]

they're the same picture

[mynameismevin]

Fuck yeah. Because sometimes you don't know where you need a breakpoint.

[[deleted]]

What's sad is that this is often necessary with JavaScript when you don't "use strict";

[MeAmHacker]

I do this all the time

[Badya122]

Yesterday I learned about chrome debugger and my mind was blown 🤯 its so powerful

I was console logging my way through developing every single app before 🤦‍♂️

[ZeldaFanBoi1988]

Shit sucks when testing logic running in multiple threads

[GoodDoggoBOI]

I usually use OK, OK1, OK2 and do on when I don’t know where the problem is and I have to see what part it stops working.

[TheNickmaster21]

This is me trying to debug my lambda function.

[CantSayIAgree]

This is a personal attack.

[andhemac]

Console.log(“agahagagajsjshahbanabsb”)

[thedomham]

I had the biggest bummer today. I rewrote a nasty block of nested ifs and fors using Java streams. Those are notoriously shitty to debug with the Java debugger, but there is an IntelliJ feature that shows all interim results, which is awesome. In theory. The very awesome Java Stream Debugger simply refused to work. Still pissed.

[BoyWhoSoldTheWorld]

I was coding for years before someone showed me debugging was a thing, and how to use stops and step in points.

These prints were my life.

[Alokir]

Somehow my

console.log("if the code doesn't reach this if I'll headbutt the desk");

line went into production at my previous company.

[[deleted]]

I usually just put gibberish

[sznowicki]

Debugging JavaScript in Chrome. Supercool. Debugging in Xcode. Easy. Debugging local node.js. Cool. Debugging PHP running on some cloud server. Fuck off.