GDB normally ignores breakpoints when it resumes execution, until at least one instruction has been executed. If it did not do this, you would be unable to proceed past a breakpoint without first disabling the breakpoint. This rule applies whether or not the breakpoint already existed when your program stopped. Source.
Monday, May 21, 2007
GDB and Ignoring Break Points on the First Instruction
I wondered this semester why GDB ignores breakpoints on the first instruction:
Subscribe to:
Post Comments (Atom)
Blog Archive
-
▼
2007
(316)
-
▼
May
(41)
- Running Journal, Thursday, 2007-05-31
- Exploratorium
- IKEA Shopping
- Bone Marrow Donation
- Yosemite Vacation Products
- Degnan's Deli Menu
- Yosemite Vacation Journal
- Final Exam Notes
- Silver Sake Sushi
- vimdiff
- Sexidecimal
- GDB and Ignoring Break Points on the First Instruc...
- 2007 3rd Annual Sacramento Japanese Film Festival
- Running Journal, Friday, 2007-05-18
- SomaFM Radio Song
- Running Journal, Wednesday, 2007-05-16
- Running Journal, Tuesday, 2007-05-15
- Running Journal, Monday, 2007-05-14
- KYDS Radio Song
- Running Journal, Sunday, 2007-05-13
- American River Parkway Plants
- Running Journal, Friday, 2007-05-11
- Bugbear Cake!
- Running Journal, Wednesday, 2007-05-09
- My 32 Bit Integer
- KoL Bugbear Cake
- Running Journal, Tuesday, 2007-05-08
- Duff's Device
- Running Journal, Sunday, 2007-05-06
- Radio Song
- Cookie Monster
- Raining Milk
- Time for new shorts
- Running Journal, Friday, 2007-05-04
- Running Journal, Thursday, 2007-05-03
- Big Sur-vivor
- Radio Song
- ZipCar
- Smoothie Recipe
- Dawn's Nintendo DS Lite Wish List
- Big Sur Marathon Result
-
▼
May
(41)
No comments:
Post a Comment