Debugging, Profiling, Code improvement tools
  • Introduction
  • Chapter1: 追蹤問題
    • 1.1.找出錯誤來源
  • Chapter2: 解決問題
    • 2.1.Check list
      • 2.1.1.確認前後條件
  • Chapter3: 錯誤訊息
    • 3.1.python
      • 'charmap' codec can't decode byte 0x8f in position 17: character maps to <undefined>
  • Chapter4:版本管理工具
    • 4.1.Git
      • 4.1.1.Working tree, Index/Cache, Repository and Object
      • 4.1.2.commit
      • 4.1.3.cherry-pick
      • 4.1.4.rebase
    • 4.2.TortoiseGit
      • 4.2.1.bisect
      • 4.4.2.reflog & reset
      • 4.2.3.blame
  • Chapter5: 除錯工具
    • 5.1.Visual studio
      • 5.1.1.輸出debug訊息
      • 5.1.2.中斷點
      • 5.1.3.載入符號, 檢視堆疊
      • 5.1.4.追蹤點
      • 5.1.5.單步執行程式
      • 5.1.6.日誌
      • 5.1.7.靜態程式分析
    • 5.2. WinDbg
      • 5.2.1.安裝WinDbg
      • 5.2.2.設定project及symbol path
      • 5.2.3.分析.dmp file
    • 5.3.API
      • 5.3.1.核心傾印
  • Chapter6: 效能分析工具
    • 6.1.Introduction
    • 6.2.Windows
      • 6.2.1.效能分析指標
      • 6.2.2.Windows Performance Monitor
      • 6.2.3.Process monitor
      • 6.2.4.Windows Performance Toolkit
    • 6.3.C++ project
      • 6.3.1.SMART BEAR AQ Time
    • 6.4.Python project
      • 6.4.1.cProfile, snakeviz
  • Chapter7: 程式碼優化工具
    • 7.1.Python
      • 7.1.1.vulture
Powered by GitBook
On this page

Was this helpful?

  1. Chapter4:版本管理工具
  2. 4.2.TortoiseGit

4.2.1.bisect

Previous4.2.TortoiseGitNext4.4.2.reflog & reset

Last updated 5 years ago

Was this helpful?

  • 1.Introduction

    • Sometimes your project occur some accident (or bug) so that you need to trace back to find out the bug was caused from which commit

    • Git provides git bisect which was the tool to find the commit efficiently

    • This section records the bisect usage of TortoiseGit

  • 2.Getting started

    • 1.You must to have idea that Which commit was good (the bug did not occur) and which was bad (the bug did occur) before performing bisect.

    • 2.Open the solution folder and right click on it, choose TortoiseGit -> Bisect start

    • 3.TortoiseGit will prompt a window and you must input the good commit and bad commit that you know.

    • 4.Input those commits and click OK.

    • 5.TortoiseGit to the commit between good one and bad one.

    • 6.Test current commit, mark Bisect good if good and vice versa.

    • 7.Repeat step.6 and TortoiseGit will help you to find the last good one

  • 3.Reference

https://tortoisegit.org/docs/tortoisegit/tgit-dug-bisect.html