Fix jumbled code renderings

Author: chudur-budur

docs/source/user_guide/debugging/altering.rst

@@ -1,3 +1,5 @@
+.. _altering:
+
 Altering Execution
 ==================
 
@@ -22,7 +24,7 @@ Example
 
 Source code :file:`numba_dpex/examples/debug/side-by-side-2.py`:
 
-.. literalinclude:: ../../../numba_dpex/examples/debug/side-by-side-2.py
+.. literalinclude:: ./../../../../numba_dpex/examples/debug/side-by-side-2.py
    :pyobject: common_loop_body
    :linenos:
    :lineno-match:

docs/source/user_guide/debugging/backtrace.rst

@@ -1,12 +1,14 @@
+.. _backtrace:
+
 Backtrace
 ==========
 
 The ``backtrace`` command displays a summary of how your program got where it
 is. Consider the following example
 ``numba_dpex/examples/debug/simple_dpex_func.py``:
 
-.. literalinclude:: ../../../numba_dpex/examples/debug/simple_dpex_func.py
-    :lines: 15-
+.. literalinclude:: ./../../../../numba_dpex/examples/debug/simple_dpex_func.py
+    :lines: 5-
     :linenos:
     :lineno-match:
 
@@ -19,13 +21,13 @@ numba_dpex.func.
 
 Example 1:
 
-.. literalinclude:: ../../../numba_dpex/examples/debug/commands/docs/backtrace_kernel
+.. literalinclude:: ./../../../../numba_dpex/examples/debug/commands/docs/backtrace_kernel
     :language: shell-session
     :emphasize-lines: 8,9
 
 Example 2:
 
-.. literalinclude:: ../../../numba_dpex/examples/debug/commands/docs/backtrace
+.. literalinclude:: ./../../../../numba_dpex/examples/debug/commands/docs/backtrace
     :language: shell-session
     :emphasize-lines: 8-10
 

docs/source/user_guide/debugging/breakpoints.rst

@@ -22,8 +22,8 @@ See also:
 Consider the following numba-dpex kernel code (refer
 ``numba_dpex/examples/debug/simple_sum.py`` for full example):
 
-.. literalinclude:: ../../../numba_dpex/examples/debug/simple_sum.py
-    :lines: 15-
+.. literalinclude:: ./../../../../numba_dpex/examples/debug/simple_sum.py
+    :lines: 5-
     :linenos:
     :lineno-match:
 
@@ -32,7 +32,7 @@ Consider the following numba-dpex kernel code (refer
 
 The debugger output:
 
-.. literalinclude:: ../../../numba_dpex/examples/debug/commands/docs/break_func
+.. literalinclude:: ./../../../../numba_dpex/examples/debug/commands/docs/break_func
     :language: shell-session
     :emphasize-lines: 3
 
@@ -41,7 +41,7 @@ The debugger output:
 
 The debugger output:
 
-.. literalinclude:: ../../../numba_dpex/examples/debug/commands/docs/break_line_number
+.. literalinclude:: ./../../../../numba_dpex/examples/debug/commands/docs/break_line_number
     :language: shell-session
     :emphasize-lines: 3
 
@@ -50,7 +50,7 @@ The debugger output:
 
 The debugger output:
 
-.. literalinclude:: ../../../numba_dpex/examples/debug/commands/docs/break_file_func
+.. literalinclude:: ./../../../../numba_dpex/examples/debug/commands/docs/break_file_func
     :language: shell-session
     :emphasize-lines: 3
 
@@ -59,7 +59,7 @@ The debugger output:
 
 The debugger output:
 
-.. literalinclude:: ../../../numba_dpex/examples/debug/commands/docs/break_conditional
+.. literalinclude:: ./../../../../numba_dpex/examples/debug/commands/docs/break_conditional
     :language: shell-session
     :emphasize-lines: 3
 
@@ -69,13 +69,13 @@ Breakpoints with nested functions
 Consider numba-dpex kernel code. See the source file
 ``numba_dpex/examples/debug/simple_dpex_func.py``:
 
-.. literalinclude:: ../../../numba_dpex/examples/debug/simple_dpex_func.py
-    :lines: 15-
+.. literalinclude:: ./../../../../numba_dpex/examples/debug/simple_dpex_func.py
+    :lines: 5-
     :linenos:
     :lineno-match:
 
 The debugger output:
 
-.. literalinclude:: ../../../numba_dpex/examples/debug/commands/docs/break_nested_func
+.. literalinclude:: ./../../../../numba_dpex/examples/debug/commands/docs/break_nested_func
     :language: shell-session
     :emphasize-lines: 3

docs/source/user_guide/debugging/data.rst

@@ -10,7 +10,7 @@ See `GDB* documentation <https://www.sourceware.org/gdb/onlinedocs/gdb/Data.html
 
 To print the value of a variable, run the ``print <variable>`` command.
 
-.. literalinclude:: ../../../numba_dpex/examples/debug/commands/docs/local_variables_0
+.. literalinclude:: ./../../../../numba_dpex/examples/debug/commands/docs/local_variables_0
     :language: shell-session
     :lines: 67-72
     :emphasize-lines: 1-6
@@ -24,7 +24,7 @@ Example - Complex Data Types
 
 Source code :file:`numba_dpex/examples/debug/side-by-side-2.py`:
 
-.. literalinclude:: ../../../numba_dpex/examples/debug/side-by-side-2.py
+.. literalinclude:: ./../../../../numba_dpex/examples/debug/side-by-side-2.py
    :pyobject: common_loop_body
    :linenos:
    :lineno-match:

docs/source/user_guide/debugging/debugging_environment.rst

@@ -27,8 +27,8 @@ Configure debugging environment
 
     You can check the correctness of the work with the following example:
 
-    .. literalinclude:: ../../../numba_dpex/examples/debug/simple_sum.py
-        :lines: 15-
+    .. literalinclude:: ./../../../../numba_dpex/examples/debug/simple_sum.py
+        :lines: 5-
         :linenos:
         :lineno-match:
 

docs/source/user_guide/debugging/frame_info.rst

@@ -20,7 +20,7 @@ Example
 
 Source code :file:`numba_dpex/examples/debug/side-by-side.py`:
 
-.. literalinclude:: ../../../numba_dpex/examples/debug/side-by-side.py
+.. literalinclude:: ./../../../../numba_dpex/examples/debug/side-by-side.py
    :pyobject: common_loop_body
    :linenos:
    :lineno-match:
@@ -59,21 +59,21 @@ Example
 
 Source code :file:`sum_local_vars.py`:
 
-.. literalinclude:: ../../../numba_dpex/examples/debug/sum_local_vars.py
-    :lines: 15-
+.. literalinclude:: ./../../../../numba_dpex/examples/debug/sum_local_vars.py
+    :lines: 5-
     :linenos:
     :lineno-match:
 
 Run the debugger with ``NUMBA_OPT=0``:
 
-.. literalinclude:: ../../../numba_dpex/examples/debug/commands/docs/local_variables_0
+.. literalinclude:: ./../../../../numba_dpex/examples/debug/commands/docs/local_variables_0
     :language: shell-session
     :lines: 1-6
 
 Use ``info locals``.
 Note that uninitialized variables are zeros:
 
-.. literalinclude:: ../../../numba_dpex/examples/debug/commands/docs/local_variables_0
+.. literalinclude:: ./../../../../numba_dpex/examples/debug/commands/docs/local_variables_0
     :language: shell-session
     :lines: 8-48
     :emphasize-lines: 1-16, 24-39

docs/source/user_guide/debugging/index.rst

@@ -42,15 +42,15 @@ Example of Intel® Distribution for GDB* usage
 
 You can use a sample kernel code, :file:`simple_sum.py`, for basic debugging:
 
-.. literalinclude:: ../../../numba_dpex/examples/debug/simple_sum.py
-    :lines: 15-
+.. literalinclude:: ./../../../../numba_dpex/examples/debug/simple_sum.py
+    :lines: 5-
     :linenos:
     :lineno-match:
 
 Use the following commands to create a breakpoint inside the kernel and run the
 debugger:
 
-.. literalinclude:: ../../../numba_dpex/examples/debug/commands/docs/simple_sum
+.. literalinclude:: ./../../../../numba_dpex/examples/debug/commands/docs/simple_sum
     :language: shell-session
 
 .. _debugging-features-and-limitations:

docs/source/user_guide/debugging/local_variables.rst

@@ -25,7 +25,7 @@ Example
 
 Source code :file:`numba_dpex/examples/debug/sum_local_vars.py`:
 
-.. literalinclude:: ../../../numba_dpex/examples/debug/sum_local_vars.py
+.. literalinclude:: ./../../../../numba_dpex/examples/debug/sum_local_vars.py
     :pyobject: data_parallel_sum
     :linenos:
     :lineno-match:
@@ -97,7 +97,7 @@ Example 1 - Using ``NUMBA_EXTEND_VARIABLE_LIFETIMES``
 
 Source code :file:`numba_dpex/tests/debugging/test_info.py`:
 
-.. literalinclude:: ../../../numba_dpex/examples/debug/side-by-side.py
+.. literalinclude:: ./../../../../numba_dpex/examples/debug/side-by-side.py
    :pyobject: common_loop_body
    :linenos:
    :lineno-match:
@@ -150,7 +150,7 @@ Example 2 - Using ``NUMBA_DUMP_ANNOTATION``
 
 Source code :file:`numba_dpex/examples/debug/sum_local_vars.py`:
 
-.. literalinclude:: ../../../numba_dpex/examples/debug/sum_local_vars.py
+.. literalinclude:: ./../../../../numba_dpex/examples/debug/sum_local_vars.py
     :pyobject: data_parallel_sum
     :linenos:
     :lineno-match:
@@ -230,8 +230,8 @@ As a workaround you can expand lifetime of the variable by using it (i.e.
 passing to dummy function `revive()`) at the end of the function. So numba will
 not insert `del a` until the end of the function.
 
-.. literalinclude:: ../../../numba_dpex/examples/debug/sum_local_vars_revive.py
-    :lines: 20-31
+.. literalinclude:: ./../../../../numba_dpex/examples/debug/sum_local_vars_revive.py
+    :lines: 5-
     :linenos:
     :lineno-match:
 
@@ -350,27 +350,27 @@ Example 3 - Using ``info locals``
 
 Source code :file:`sum_local_vars.py`:
 
-.. literalinclude:: ../../../numba_dpex/examples/debug/sum_local_vars.py
-    :lines: 15-
+.. literalinclude:: ./../../../../numba_dpex/examples/debug/sum_local_vars.py
+    :lines: 5-
     :linenos:
     :lineno-match:
 
 Run the debugger with ``NUMBA_OPT=0``:
 
-.. literalinclude:: ../../../numba_dpex/examples/debug/commands/docs/local_variables_0
+.. literalinclude:: ./../../../../numba_dpex/examples/debug/commands/docs/local_variables_0
     :language: shell-session
     :lines: 1-6
 
 Run the ``info locals`` command. The sample output on "no optimization" level ``NUMBA_OPT=0`` is as follows:
 
-.. literalinclude:: ../../../numba_dpex/examples/debug/commands/docs/local_variables_0
+.. literalinclude:: ./../../../../numba_dpex/examples/debug/commands/docs/local_variables_0
     :language: shell-session
     :lines: 8-48
     :emphasize-lines: 1-16, 24-39
 
 Since the debugger does not hit a line with the target variable ``l1``, the value equals 0. The true value of the variable ``l1`` is shown after stepping to line 22.
 
-.. literalinclude:: ../../../numba_dpex/examples/debug/commands/docs/local_variables_0
+.. literalinclude:: ./../../../../numba_dpex/examples/debug/commands/docs/local_variables_0
     :language: shell-session
     :lines: 49-66
     :emphasize-lines: 1-16

docs/source/user_guide/debugging/numba-0.55.rst

@@ -28,7 +28,7 @@ Example
 
 Source code :file:`numba_dpex/examples/debug/side-by-side.py`:
 
-.. literalinclude:: ../../../numba_dpex/examples/debug/side-by-side.py
+.. literalinclude:: ./../../../../numba_dpex/examples/debug/side-by-side.py
     :pyobject: common_loop_body
     :linenos:
     :lineno-match:

docs/source/user_guide/debugging/stepping.rst

@@ -8,15 +8,15 @@ Consider the following examples.
 
 ``numba_dpex/examples/debug/simple_sum.py``:
 
-.. literalinclude:: ../../../numba_dpex/examples/debug/simple_sum.py
-    :lines: 15-
+.. literalinclude:: ./../../../../numba_dpex/examples/debug/simple_sum.py
+    :lines: 5-
     :linenos:
     :lineno-match:
 
 Example with a nested function ``numba_dpex/examples/debug/simple_dpex_func.py``:
 
-.. literalinclude:: ../../../numba_dpex/examples/debug/simple_dpex_func.py
-    :lines: 15-
+.. literalinclude:: ./../../../../numba_dpex/examples/debug/simple_dpex_func.py
+    :lines: 5-
     :linenos:
     :lineno-match:
 
@@ -26,13 +26,13 @@ Example with a nested function ``numba_dpex/examples/debug/simple_dpex_func.py``
 
 Run the debugger and use the following commands:
 
-.. literalinclude:: ../../../numba_dpex/examples/debug/commands/docs/step_sum
+.. literalinclude:: ./../../../../numba_dpex/examples/debug/commands/docs/step_sum
     :language: shell-session
     :emphasize-lines: 8-13
 
 You can use stepping to switch to a nested function. See the example below:
 
-.. literalinclude:: ../../../numba_dpex/examples/debug/commands/docs/step_dpex_func
+.. literalinclude:: ./../../../../numba_dpex/examples/debug/commands/docs/step_dpex_func
     :language: shell-session
     :emphasize-lines: 8-14
 
@@ -41,7 +41,7 @@ You can use stepping to switch to a nested function. See the example below:
 
 The command allows you to move forward by machine instructions. The example uses an additional command ``x/i $pc``, which prints the instruction to be executed.
 
-.. literalinclude:: ../../../numba_dpex/examples/debug/commands/docs/stepi
+.. literalinclude:: ./../../../../numba_dpex/examples/debug/commands/docs/stepi
     :language: shell-session
     :emphasize-lines: 8-13
 
@@ -50,7 +50,7 @@ The command allows you to move forward by machine instructions. The example uses
 
 The command has stepping-like behavior, but it skips nested functions.
 
-.. literalinclude:: ../../../numba_dpex/examples/debug/commands/docs/next
+.. literalinclude:: ./../../../../numba_dpex/examples/debug/commands/docs/next
     :language: shell-session
     :emphasize-lines: 8-14
 
@@ -66,7 +66,7 @@ configure it for more efficient debugging. To ensure the current thread executes
 a single line without interference, set the scheduler-locking setting to `on` or
 `step`:
 
-.. literalinclude:: ../../../numba_dpex/examples/debug/commands/docs/sheduler_locking
+.. literalinclude:: ./../../../../numba_dpex/examples/debug/commands/docs/sheduler_locking
     :language: shell-session
     :emphasize-lines: 8-13