printf() debugging no longer acceptable

Register a SA Forums Account here!
JOINING THE SA FORUMS WILL REMOVE THIS BIG AD, THE ANNOYING UNDERLINED ADS, AND STUPID INTERSTITIAL ADS!!!

You can: log in, read the tech support FAQ, or request your lost password. This dumb message (and those ads) will appear on every screen until you register! Get rid of this crap by registering your own SA Forums Account and joining roughly 150,000 Goons, for the one-time price of $9.95! We charge money because it costs us money per month for bills, and since we don't believe in showing ads to our users, we try to make the money back through forum registrations.

The Something Awful Forums > Discussion > Serious Hardware/Software Crap > YOSPOS > printf() debugging no longer acceptable

Stick Insect: Oct 24, 2010; My enemies are many.

My equals are none.

Using a debugger is computer vivisection

# ¿ Oct 20, 2019 01:20

Adbot: ADBOT LOVES YOU

# ¿ May 15, 2024 02:38

Stick Insect: Oct 24, 2010; My enemies are many.

My equals are none.

I've seen webapps produce gigabytes worth of logs everyday, because the webapp was full of debug print statements. Not because it was receiving a lot of traffic.

# ¿ Oct 20, 2019 10:12

Stick Insect: Oct 24, 2010; My enemies are many.

My equals are none.

josh2112 posted:

current debugging environment: DOS 2.1 DEBUG.COM on a 128-KB IBM PCjr

I remember using debug.com to create small executables by copying hexadecimal numbers from a book :3:

# ¿ Oct 21, 2019 22:45

The Something Awful Forums > Discussion > Serious Hardware/Software Crap > YOSPOS > printf() debugging no longer acceptable