Skip to main content.
Navigation:
DENX
>
DULG
>
DebuggingTricks
Translations:
Edit
|
Attach
|
Raw
|
Ref-By
|
Printable
|
More
DULG
Sections of this site:
DENX Home
|
DULG
|
ELDK-5
|
Know
|
Training
|
U-Boot
|
U-Bootdoc
Topics
DULG Home
BoardSelect
Manual
FAQ
Application Notes
Changes
Index
List of pages in DULG
Search
%SECTION0{name=DebuggingTricks}% Tips and Tricks * To prevent GDB from jumping around in the code when trying to single step, i. e. when it seems as if the code is not executing line by line, you can recompile your code with the following additional compiler options: <verbatim> -fno-schedule-insns -fno-schedule-insns2 </verbatim> * On some systems (like the MPC8xx or MPC8260) you can only define one hardware breakpoint. Therefore you must delete an existing breakpoint before you can define a new one: <verbatim> (gdb) d b Delete all breakpoints? (y or n) y (gdb) b ex_preempt.c:63 Breakpoint 2 at 0xcf030080: file ex_preempt.c, line 63. </verbatim>
10.3. GDB Startup File and Utility Scripts
1. Abstract
10.5. Application Debugging
Prev
Home
Next
