#debugging

[python-programming-language]

Different ways of debugging my source code ...

Post #88: www.pythonforbiologists.com, My code isn't working, 2023.

[programmingmadness]

Me trying and failing to find out why a bug is happening:

[zzkt]

[hauxicrook]

[peachgull]

Debug scraps I found at :

[askagamedev]

Debugging Complications

Sometimes a bug is easy to catch. You do some normal set of inputs and the aberrant behavior appears. Sometimes a bug is difficult to reproduce. Here are some of the qualities that can make a bug difficult to nail down:

[Build-specific] - The bug only shows up in release or final builds.

Platform-specific - The bug only shows up on a particular platform (e.g. PS4, Linux dedicated server, Windows 10 service pack 2, etc.)

Random timing - The repro steps are always the same, but the bug doesn't always happen when the steps are taken

Frame-specific timing - Specific inputs must be made within a specific frame window to cause the bad behavior. Bonus difficulty if you have to reproduce the bug on a debug build with a low frame rate

Silent failure - The bug doesn't actually trigger any error messages or logs or anything, it just fails silently without a trace

Requires multiple players to repro - Happens only on a dedicated server with multiple squads all playing at once! Player A must do the action to Player B, and the bug appears on player C's screen!

Requires a long time to reproduce - The bad behavior happens only when leaving the game on for multiple hours, like via a [smoke test]

Live Environment Only - This bug only ever shows up in the live game

Even more fun, there's nothing stopping more than one of these complications to happen within the same bug. A build-specific, platform-specific, live-only bug that silently fails and requires a bunch of players that only happens after many hours? Fun!

[Join us on Discord] and/or [Support us on Patreon]

Got a burning question you want answered?

Short questions: Ask a Game Dev on Twitter

Long questions: Ask a Game Dev on Tumblr

Frequent Questions: The FAQ

[omeletcat]

I know when a tutorial or like person who has been programming for a long time says "you should take errors as tips and a helping hand instead of something negative" they try and help you out! and i bet that would make error hunting way less annoying but like.. no, i hate errors, if it was a person i'd punch it in the face.

i'm sorry errors, i'm sorry debug menu, but we can never be friends.

[theftmprogrammer]

ever have to debug something so frustrating you have to go touch grass?

[izicodes]

I keep not reading my code properly. This time it was with JavaScript.

Button wasn’t working because I used “.querySelectorAll” instead of “.querySelector” when I was targeting just one button.

The console kept saying “btn.addEventListener() is not a function” like yes it is, I used it on my other button elements so WORK.

But no. Spent an hour trying to fix it. I wasted an hour on this and my work is due in less than 4 hours.

Thanks JavaScript. Thank you. YOU COULDN’T HAVE SAID “Oh btw Loa, you’re using .querySelectorAll(), I think you should change that bestie” BUT NO IT LEFT ME TO CRY FOR AN HOUR.

[visual-oddities]

New Psychonauts video showcasing Raz interacting with the game pieces of the Asylum (which is normally glitched but I fixed the code).

[zeatheninteractive]

New Project

Polishing up the 'Noughts and Crosses' script for closed testing! 🛠️🎮 Made some adjustments to the restart button visibility, added extra player prompts, and improved the overall flow—everything's set for some friendly competition! Excited to see how it performs in the upcoming testing phase. Testing phase here we come.

[nerdymemes]

[frog707]

Seen on a coffee mug

Debugging = being the detective in a crime story where you are also the murderer

[milkweedman]

What is going on with this? The fiber loses the twist almost immediately, as I wind it on the spindle. My instincts say I'm pre-drafting too thick, but I'm not sure. I'm still a beginner and I'm trying to teach myself to love the variability of being a learner (lifelong perfectionism is a butt)

Your instincts are correct--that's a pretty thick singles to be spinning on what looks like a fairly small drop spindle. You could absolutely spin that thick on a bigger one.

There's sort of a rule of thumb here: small spindles spin fine yarn, big spindles spin thicker yarn (or are used to ply yarn). A small spindle like that might just not have the momentum to actually add twist to your fiber.

(There's exceptions to this rule and some complications re: supported spindles especially, but for drop spindles it's pretty much always true !)

But I'd guess that your main problem is that you're trying to spin fiber that's too thick for that spindle, so it's just not even taking the twist. If you spin the spindle and it only goes briefly: that's definitely what's happening. (if it spins for a good long while--at least 30 seconds--let me know) Pre-draft thinner and you should be good to go ! You can just rely on pre-drafting entirely here if you want (just to keep things simple while you learn) and try to pre-draft to the thickness that you want your single to be. That can help you learn consistency.

Another tip, just in case this is also happening here: make sure you're always winding the yarn onto the spindle in the same direction that you're spinning. Otherwise you're going to untwist the yarn somewhat as you wind on (less of a problem if you've got adequate twist, but if it's already really undertwisted then you will notice), plus it will be less stable and can even fly off or start to unwind as you spin.

Hope that helps !

And good luck with your spinning. Learning to embrace the imperfect nature of your handmade items can be hard, but it's really worth the effort. I'm currently having a great time spinning some extremely imperfect rolags for a museum display, and like--it doesn't get any more fun than that, imo :D

[ukagakadreamteam]

Hey, so this one's about the underfell sans ukagaka by change side (I think, thats the dev on the wiki anyways), and for some reason I've noticed that what would normally be a clothes pile (I think) has changed into..Two underfell sanses? Is there any fix to this? Also, the one that was the clothes pile is permanently stuck as holding a phone and looking at it. So only the actual one moves. For other info that may help, I'm on windows, only running this ghost + there is no error message when this happens/happened.

This is a tricky one! This ghost in particular has very unique code, and as I am not terribly familiar with it it is hard for me to spot errors in it. I took a look, but didn't find anything yet. We haven't seen anyone else with this issue before either, so there isn't a known fix.

Does this issue happen upon restarting the ghost/SSP? Or does something specific trigger it? That information would be a good place to start.

Additionally, it would be helpful if you can bring up SSP's script log, and show the log when the issue occurs, whether that be on boot or otherwise.

To open SSP's script log, you'll need to be in developer mode. You can toggle developer mode in the SSP preferences, on the General page.

Once you've done this, you should be able to click on a ghost and then press Ctrl + L to open script log. This will display a log of all the scripts that your open ghosts have run recently.

A screenshot of the log would be useful, although if the script is longer than the window itself, it would be more helpful if you could copy out the script(s) in question! You can do this by highlighting an entry, then clicking the Copy button.

I can't guarantee that we'll be able to find the issue or provide a fix, but we'll certainly try if we can have a bit more info to go off of!