Documentation | Draft: Add section "Debugging" to RTEMS documentation (!43)

[Christian Mauderer (@c-mauderer)]

Christian Mauderer commented on a discussion on user/debugging/index.rst: https://gitlab.rtems.org/rtems/docs/rtems-docs/-/merge_requests/43#note_111263

 > +
 > +Debugging
 > +***********
 > +.. index:: Debugging
 > +.. index:: Embedded executable
 > +
 > +Debugging is a critical process in software development that involves
 > +identifying and resolving bugs or defects in a program. A debugger is a tool
 > +that allows developers to inspect the internal state of a program while it runs
 > +or after it crashes (like with a core dump), providing insights into the
 > +program's execution flow and state.
 > +
 > +A debugger allows us to:
 > +
 > +#. Set breakpoints to pause execution at specific points
 > +

No, I meant the lines between the points of the enumeration. You have:

```
#. Set breakpoints to pause execution at specific points

#. Step through code line-by-line or instruction by instruction 

#. Inspect/modify variables and memory 

#. Monitor a program's call stack and thread states
```

What I would expect:

```
#. Set breakpoints to pause execution at specific points
#. Step through code line-by-line or instruction by instruction 
#. Inspect/modify variables and memory 
#. Monitor a program's call stack and thread states
```

But both seems to work without problems. So it should be OK.

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/docs/rtems-docs/-/merge_requests/43#note_111263
You're receiving this email because of your account on gitlab.rtems.org.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/bugs/attachments/20240819/7164bea5/attachment.htm>