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

Programming

13386 readers
141 users here now

All things programming and coding related. Subcommunity of Technology.

This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 2 years ago
MODERATORS
alyaza@beehaw.org
Hexorg@beehaw.org
remington@beehaw.org
26
Have you ever used git bisect? (programming.dev)
submitted 1 year ago by canpolat@programming.dev to c/programming@beehaw.org
20 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
[–] AbelianGrape@beehaw.org 3 points 1 year ago

I've used it to fix regressions, most recently in a register allocator for a compiler. There's pretty much no chance I would've found that particular bug otherwise; it was caused by an innocuous change (one of those "this shouldn't matter" things) clashing badly with an incorrect assumption baked into a completely different part of the allocator.

I had seen the same effect from an unrelated bug on a different program. When I added a new test and saw the same effect, I had a "didn't I fix this already?" moment. When I saw that the previous fix was still there, I checked if an older version of the allocator exhibited the same bug on the new test, and it did not. Bisecting found the offending change relatively quickly and further conventional testing exposed the incorrect assumption.