看他debug的模式 就好像在動手術一樣精確仔細
還不是普通的割除蘭尾這種簡單手術
是心臟瓣膜的那種高難度手術
有誰可以打開gdb後,在有問題的那段code附近隨意閱讀著組語
然後猜想著他是怎麼implement的,在0x5c018f44推測出這邊是一個loop,
getc會檢查他的flag設了沒,若是還沒設則會一直loop在哪裡,就像是block住在等user輸入一樣
然後一路追查下去看看flag何時會動到,watch他...
..
後來其實就是r8 沒有fixed ,跳去user前要先存起來才對
我自己中途就已經看到
a3001a1c <getc>:
a3001a1c: e598c020 ldr ip, [r8, #32]
a3001a20: e59cf004 ldr pc, [ip, #4]
就應該猜想出getc出了問題,又看到他動了r8,這關聯也太明顯了
可是還是沒自己把bug解決
好像毅力越來越不堅定了
Wednesday, November 28, 2012
Monday, September 24, 2012
What business can learn from open source 讀後感
這可能是我在看Startup, Paul Graham, or OSCON看到的好文章What business can learn from open source。
I love the:
paragraph about office.
paragraph about productive working hour.
好的作者都是隱藏幽默到句子裡
“The basic idea behind office hours is that if you can't make people work, you can at least prevent them from having fun”
And as the example of open source and blogging suggests, you'll enjoy it more, even if you fail. You'll be working on your own thing, instead of going to some office and doing what you're told. There may be more pain in your own company, but it won't hurt as much.
*Summary
So these, I think, are the three big lessons open source and blogging have to teach business: (1) that people work harder on stuff they like, (2) that the standard office environment is very unproductive, and (3) that bottom-up often works better than top-down.
Subscribe to:
Posts (Atom)