https://bugs.documentfoundation.org/show_bug.cgi?id=170205
--- Comment #19 from Buovjaga <[email protected]> --- (In reply to bugzilla2 from comment #18) > I was wrong in comment 15 when saying that git master > (ff0eebbac4c03e820485ccb7ea1f6e9f06606a09) doesn't crash. It does crash! > > With commit cc9574aa24614d168ead5ace2fcc96267347279f it seems to run stable > so far, so I think it can be bisected. > > BUT, going from good to bad step by step will not work, because that will > take forever. I would need a list of Commits thats between the two mentioned > commits and a way to directly jump to any given commit. So I can always > devide the range by two, finding the culprit "faster" (it will still take a > looooong time)... It's true that if reproducing the issue is difficult, it can take a long time. This is the way you can find source commits in the bibisect repositories: https://wiki.documentfoundation.org/QA/Bibisect#Checking_out_a_specific_commit_based_on_source_hash However, it is only faster, if there are a small number of commits within the range, like 100-200. There is no difference between what you say about doing the division manually vs. doing the bibisect. -- You are receiving this mail because: You are the assignee for the bug.
