lupyuen/lupyuen.org
1
0
Fork 0
mirror of https://github.com/lupyuen/lupyuen.github.io.git synced 2025-01-13 06:48:34 +08:00
Code Issues Projects Releases Packages Wiki Activity Actions 1

Update article

Browse source
This commit is contained in:
Lup Yuen Lee 2025-01-01 16:47:15 +08:00
parent 269cfc7244
commit d8474aa821
1 changed files with 22 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

28
src/bisect.md
View file

@ -289,8 +289,8 @@ _What happens in Git Bisect?_
git clone https://github.com/apache/nuttx
cd nuttx
git bisect start
git bisect good 6554ed4d ## Commit #1
git bisect bad 79a1ebb ## Commit #468
git bisect good 6554ed4 ## Commit #1
git bisect bad 79a1ebb ## Commit #468
git bisect run \
$HOME/nuttx-bisect/start-job-bisect.sh
```
@ -391,7 +391,19 @@ _What happens in Git Bisect?_
_Did Git Bisect find the correct Breaking Commit?_
To be absolutely sure: We run Git Bisect [__one more time__](https://gist.github.com/lupyuen/5a92fb9ea76751a54d2a82ba0341c493)...
To be _really really_ sure: We run Git Bisect [__one more time__](https://gist.github.com/lupyuen/5a92fb9ea76751a54d2a82ba0341c493)...
```bash
## Restart the Git Bisect (`sudo` is needed by Docker)
sudo --shell
git bisect start
git bisect good 6554ed4 ## Commit #1
git bisect bad 79a1ebb ## Commit #468
git bisect run \
$HOME/nuttx-bisect/start-job-bisect.sh
```
Here comes the twist, watch carefully...
```bash
## Commit #234 is Bad
@ -438,7 +450,13 @@ exit 1
run-job-bisect.sh ... fb92b60 ...
test_ltp_interfaces_pthread_barrierattr_init_2_1 FAILED
exit 1
```
[(See the __Complete Log__)](https://gist.github.com/lupyuen/5a92fb9ea76751a54d2a82ba0341c493)
Which deduces...
```bash
## Commit #132 is the Breaking Commit
fb92b60 is the first bad commit
@ -446,8 +464,6 @@ fb92b60 is the first bad commit
## 74bac56 is the first bad commit
```
[(See the __Complete Log__)](https://gist.github.com/lupyuen/5a92fb9ea76751a54d2a82ba0341c493)
__Commit #`132`__ is now the Breaking Commit, not Commit #`235`!
Hmmm something below has changed. Why?
@ -564,7 +580,7 @@ Needs more probing...
_What's ltp_interfaces_pthread_barrierattr_init_2_1? Why is the Stack Overflowing?_
We search the __NuttX Disassembly__...
We search the __NuttX Disassembly__ (pic above)
```bash
## Dump the disassembly to nuttx.S