debugbreak.c 1.0.1 → 1.0.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +2 -2
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -20,7 +20,7 @@ int main()
|
|
|
20
20
|
|
|
21
21
|
**License**: the very permissive [2-Clause BSD](https://github.com/scottt/debugbreak/blob/master/COPYING).
|
|
22
22
|
|
|
23
|
-
Known Problem: if continuing execution after a debugbreak breakpoint hit doesn't work (e.g. on ARM or POWER), see [HOW-TO-USE-DEBUGBREAK-GDB-PY.md](HOW-TO-USE-DEBUGBREAK-GDB-PY.md) for a workaround.
|
|
23
|
+
Known Problem: if continuing execution after a debugbreak breakpoint hit doesn't work (e.g. on ARM or POWER), see [HOW-TO-USE-DEBUGBREAK-GDB-PY.md](https://github.com/scottt/debugbreak/blob/master/HOW-TO-USE-DEBUGBREAK-GDB-PY.md) for a workaround.
|
|
24
24
|
|
|
25
25
|
<br>
|
|
26
26
|
|
|
@@ -138,7 +138,7 @@ On ARM, **debug_break()** generates **.inst 0xe7f001f0** in ARM mode and **.inst
|
|
|
138
138
|
(gdb) # Change $l from 2 to 4 for ARM mode
|
|
139
139
|
```
|
|
140
140
|
to jump over the instruction.
|
|
141
|
-
A new GDB command, **debugbreak-step**, is defined in [debugbreak-gdb.py](https://github.com/scottt/debugbreak/blob/master/debugbreak-gdb.py) to automate the above. See [HOW-TO-USE-DEBUGBREAK-GDB-PY.md](HOW-TO-USE-DEBUGBREAK-GDB-PY.md) for sample usage.
|
|
141
|
+
A new GDB command, **debugbreak-step**, is defined in [debugbreak-gdb.py](https://github.com/scottt/debugbreak/blob/master/debugbreak-gdb.py) to automate the above. See [HOW-TO-USE-DEBUGBREAK-GDB-PY.md](https://github.com/scottt/debugbreak/blob/master/HOW-TO-USE-DEBUGBREAK-GDB-PY.md) for sample usage.
|
|
142
142
|
```
|
|
143
143
|
$ arm-none-linux-gnueabi-gdb -x debugbreak-gdb.py test/break-c++
|
|
144
144
|
<...>
|