Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Commit6ad9bf3

Browse files
authored
Expand the esp8266 hardware debugging limitations section (esp8266#8879)
It's trivial to run into a problem caused by the single hardware breakpointlimitation, but the existing documentation doesn't explicitly address thissituation (and search results for the error message aren't particularlyhelpful).This commit updates the documentation with an explicit example of whathappens when a breakpoint expression matches multiple locations, along witha possible workaround.
1 parent503502f commit6ad9bf3

File tree

1 file changed

+29
-0
lines changed

1 file changed

+29
-0
lines changed

‎doc/gdb.rst‎

Lines changed: 29 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -380,4 +380,33 @@ breakpoint) command in GDB while debugging instead of the more common
380380
``break`` command, since ``thb`` will remove the breakpoint once it is
381381
reached automatically and save you some trouble.
382382
383+
Because of the single hardware breakpoint limitation, you must pay careful
384+
attention to the output from ``gdb`` when you set a breakpoint. If your
385+
breakpoint expression matches multiple locations, as in this example:
383386
387+
.. code:: bash
388+
389+
(gdb) break loop
390+
Breakpoint 1 at 0x40202c84: loop. (2 locations)
391+
392+
Then you will be unable to ``continue``:
393+
394+
.. code:: bash
395+
396+
(gdb) cont
397+
Continuing.
398+
Note: automatically using hardware breakpoints for read-only addresses.
399+
Warning:
400+
Cannot insert hardware breakpoint 1.
401+
Could not insert hardware breakpoints:
402+
You may have requested too many hardware breakpoints/watchpoints.
403+
404+
You can resolve this situation by deleting the previous breakpoint and
405+
using a more specific breakpoint expression:
406+
407+
.. code:: bash
408+
409+
(gdb) delete
410+
Delete all breakpoints? (y or n) y
411+
(gdb) break mysketch.ino:loop
412+
Breakpoint 2 at 0x40202c84: file .../mysketch.ino, line 113.

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp