summaryrefslogtreecommitdiffstats
path: root/docs/getting-started/app-workflow-debug-app.md
diff options
context:
space:
mode:
Diffstat (limited to 'docs/getting-started/app-workflow-debug-app.md')
-rw-r--r--docs/getting-started/app-workflow-debug-app.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/getting-started/app-workflow-debug-app.md b/docs/getting-started/app-workflow-debug-app.md
index 91ef905..c0899de 100644
--- a/docs/getting-started/app-workflow-debug-app.md
+++ b/docs/getting-started/app-workflow-debug-app.md
@@ -25,7 +25,7 @@ Here are three methods:
* Use Core Dumps if you have set the `agl-devel` feature.
Core Dumps are obviously more suited for post-mortem analysis.
For features, see the
- "[Features supported by `aglsetup`](../../../../../docs/getting_started/en/dev/reference/source-code.html#features-supported-by-aglsetup)"
+ "[Initializing Your Build Environment](./image-workflow-initialize-build-environment.html#initializing-your-build-environment)"
section.
**NOTE:** Core Dumps are available only with the "Flunky Flounder" release (i.e. 6.x).
@@ -43,5 +43,5 @@ Here are three methods:
In order to use third-party debugging tools, you need to include the tools in the target image.
You gain access to the tools by enabling the `agl-devel` feature when you run the
`aglsetup.sh` script as described in the
- "[Setup Build Environment Info](../../../../../docs/getting_started/en/dev/reference/source-code.html#set-up-build-environment-info)"
+ "[Initializing Your Build Environment](./image-workflow-initialize-build-environment.html#initializing-your-build-environment)"
section.