Improve debugging documentation #32278
Conversation
cticenhour
left a comment
cticenhour
left a comment
There was a problem hiding this comment.
Thank you for adding all this! I had a few suggestions I wanted to note.
Co-authored-by: Casey Icenhour <[email protected]>
|
Job Documentation, step Docs: sync website on 495f7cb wanted to post the following: View the site here This comment will be updated on new commits. |
| When developing your own application, it is generally advised to start from the `devel` build, as it | ||
| offers a reasonable balance between speed and debugging checks. When an error cannot be easily addressed | ||
| with the information provided by the `devel` build, a `dbg` executable can be built for use in debuggers. | ||
| See [this page](application_development/debugging.md) for instructions on running the `dbg` executable |
There was a problem hiding this comment.
Without looking at the CI too closely, I imagine the failing apps do not have this markdown file (or the other one you link on line 72) available in their MooseDocs content. If you wanted to avoid a bunch of little patches....you could apply optional=True to stop this from being rendered when the file doesn't exist (might be wonky for those who get here in their application websites), or send them to the direct URL on the MOOSE website (which could be subject to change, but at least it is clickable on these broken apps!).
3 participants
ref #32211