this post was submitted on 25 Jun 2023
53 points (100.0% liked)

Programming

17424 readers
85 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 1 year ago
MODERATORS
snowe@programming.dev
Ategon@programming.dev
MaungaHikoi@lemmy.nz
53
Have you ever used git bisect? (programming.dev)
submitted 1 year ago by canpolat@programming.dev to c/programming@programming.dev
21 comments fedilink hide all child comments
 

cross-posted from: https://programming.dev/post/214031

Have you ever used git bisect? If so, how did you use it? Did it help you find a problem which would otherwise be difficult to find? Story time, I guess?

you are viewing a single comment's thread
view the rest of the comments
[–] hukaulaba@pawb.social 3 points 1 year ago

The few times I have used git bisect, it has been on projects with no automated tests where the reported issue last worked far in the past. It isn't my first option, but it is what I turn to if I can't figure out what the correct internal state for some portion of what triggers the issue is supposed to be, saving a lot of time I could have spent banging my head into a wall.