Fixed absolute paths that broke some images

Author: Frank01001

0.8.0/from_pydoc/generated/architectures/aarch64/aarch64_thread_context/index.html

@@ -1827,7 +1827,7 @@ <h2 id="libdebug.architectures.aarch64.aarch64_thread_context.Aarch64ThreadConte
 
     <div class="doc doc-contents ">
             <p class="doc doc-class-bases">
-              Bases: <code><a class="autorefs autorefs-internal" title="libdebug.state.thread_context.ThreadContext" href="../../../state/thread_context/#libdebug.state.thread_context.ThreadContext">ThreadContext</a></code></p>
+              Bases: <code><span title="libdebug.state.thread_context.ThreadContext">ThreadContext</span></code></p>
 
 
         <p>This object represents a thread in the context of the target aarch64 process. It holds information about the thread's state, registers and stack.</p>

0.8.0/from_pydoc/generated/architectures/amd64/amd64_thread_context/index.html

@@ -1827,7 +1827,7 @@ <h2 id="libdebug.architectures.amd64.amd64_thread_context.Amd64ThreadContext" cl
 
     <div class="doc doc-contents ">
             <p class="doc doc-class-bases">
-              Bases: <code><a class="autorefs autorefs-internal" title="libdebug.state.thread_context.ThreadContext" href="../../../state/thread_context/#libdebug.state.thread_context.ThreadContext">ThreadContext</a></code></p>
+              Bases: <code><span title="libdebug.state.thread_context.ThreadContext">ThreadContext</span></code></p>
 
 
         <p>This object represents a thread in the context of the target amd64 process. It holds information about the thread's state, registers and stack.</p>

0.8.0/from_pydoc/generated/architectures/amd64/compat/i386_over_amd64_thread_context/index.html

@@ -1827,7 +1827,7 @@ <h2 id="libdebug.architectures.amd64.compat.i386_over_amd64_thread_context.I386O
 
     <div class="doc doc-contents ">
             <p class="doc doc-class-bases">
-              Bases: <code><a class="autorefs autorefs-internal" title="libdebug.state.thread_context.ThreadContext" href="../../../../state/thread_context/#libdebug.state.thread_context.ThreadContext">ThreadContext</a></code></p>
+              Bases: <code><span title="libdebug.state.thread_context.ThreadContext">ThreadContext</span></code></p>
 
 
         <p>This object represents a thread in the context of the target i386 process when running on amd64. It holds information about the thread's state, registers and stack.</p>

0.8.0/from_pydoc/generated/architectures/i386/i386_thread_context/index.html

@@ -1827,7 +1827,7 @@ <h2 id="libdebug.architectures.i386.i386_thread_context.I386ThreadContext" class
 
     <div class="doc doc-contents ">
             <p class="doc doc-class-bases">
-              Bases: <code><a class="autorefs autorefs-internal" title="libdebug.state.thread_context.ThreadContext" href="../../../state/thread_context/#libdebug.state.thread_context.ThreadContext">ThreadContext</a></code></p>
+              Bases: <code><span title="libdebug.state.thread_context.ThreadContext">ThreadContext</span></code></p>
 
 
         <p>This object represents a thread in the context of the target i386 process. It holds information about the thread's state, registers and stack.</p>

0.8.0/from_pydoc/generated/snapshots/memory/memory_map_snapshot/index.html

@@ -1858,7 +1858,7 @@ <h2 id="libdebug.snapshots.memory.memory_map_snapshot.MemoryMapSnapshot" class="
 
     <div class="doc doc-contents ">
             <p class="doc doc-class-bases">
-              Bases: <code><a class="autorefs autorefs-internal" title="libdebug.data.memory_map.MemoryMap" href="../../../data/memory_map/#libdebug.data.memory_map.MemoryMap">MemoryMap</a></code></p>
+              Bases: <code><span title="libdebug.data.memory_map.MemoryMap">MemoryMap</span></code></p>
 
 
         <p>A snapshot of the memory map of the target process.</p>
@@ -1919,7 +1919,7 @@ <h2 id="libdebug.snapshots.memory.memory_map_snapshot.MemoryMapSnapshot" class="
             </td>
           </tr>
           <tr class="doc-section-item">
-            <td><code><a class="autorefs autorefs-internal" title="libdebug.snapshots.memory.memory_map_snapshot.MemoryMapSnapshot.offset" href="../../../data/memory_map/#libdebug.data.memory_map.MemoryMap.offset">offset</a></code></td>
+            <td><code><span title="libdebug.snapshots.memory.memory_map_snapshot.MemoryMapSnapshot.offset">offset</span></code></td>
             <td>
                   <code><span title="int">int</span></code>
             </td>
@@ -1930,7 +1930,7 @@ <h2 id="libdebug.snapshots.memory.memory_map_snapshot.MemoryMapSnapshot" class="
             </td>
           </tr>
           <tr class="doc-section-item">
-            <td><code><a class="autorefs autorefs-internal" title="libdebug.snapshots.memory.memory_map_snapshot.MemoryMapSnapshot.backing_file" href="../../../data/memory_map/#libdebug.data.memory_map.MemoryMap.backing_file">backing_file</a></code></td>
+            <td><code><span title="libdebug.snapshots.memory.memory_map_snapshot.MemoryMapSnapshot.backing_file">backing_file</span></code></td>
             <td>
                   <code><span title="str">str</span></code>
             </td>

0.8.0/from_pydoc/generated/snapshots/memory/snapshot_memory_view/index.html

@@ -1881,7 +1881,7 @@ <h2 id="libdebug.snapshots.memory.snapshot_memory_view.SnapshotMemoryView" class
 
     <div class="doc doc-contents ">
             <p class="doc doc-class-bases">
-              Bases: <code><a class="autorefs autorefs-internal" title="libdebug.memory.abstract_memory_view.AbstractMemoryView" href="../../../memory/abstract_memory_view/#libdebug.memory.abstract_memory_view.AbstractMemoryView">AbstractMemoryView</a></code></p>
+              Bases: <code><span title="libdebug.memory.abstract_memory_view.AbstractMemoryView">AbstractMemoryView</span></code></p>
 
 
         <p>Memory view for a thread / process snapshot.</p>
@@ -3114,7 +3114,7 @@ <h3 id="libdebug.snapshots.memory.snapshot_memory_view.SnapshotMemoryView.resolv
       <tbody>
           <tr class="doc-section-item">
 <td><code>Symbol</code></td>            <td>
-                  <code><a class="autorefs autorefs-internal" title="libdebug.data.symbol.Symbol" href="../../../data/symbol/#libdebug.data.symbol.Symbol">Symbol</a></code>
+                  <code><span title="libdebug.data.symbol.Symbol">Symbol</span></code>
             </td>
             <td>
               <div class="doc-md-description">

0.8.0/from_pydoc/generated/snapshots/registers/snapshot_registers/index.html

@@ -1836,7 +1836,7 @@ <h2 id="libdebug.snapshots.registers.snapshot_registers.SnapshotRegisters" class
 
     <div class="doc doc-contents ">
             <p class="doc doc-class-bases">
-              Bases: <code><a class="autorefs autorefs-internal" title="libdebug.data.registers.Registers" href="../../../data/registers/#libdebug.data.registers.Registers">Registers</a></code></p>
+              Bases: <code><span title="libdebug.data.registers.Registers">Registers</span></code></p>
 
 
         <p>Class that holds the state of the architectural-dependent registers of a snapshot.</p>

0.8.0/from_pydoc/generated/snapshots/thread/lw_thread_snapshot/index.html

@@ -2123,7 +2123,7 @@ <h3 id="libdebug.snapshots.thread.lw_thread_snapshot.LightweightThreadSnapshot._
                 <code>thread</code>
             </td>
             <td>
-                  <code><a class="autorefs autorefs-internal" title="libdebug.state.thread_context.ThreadContext" href="../../../state/thread_context/#libdebug.state.thread_context.ThreadContext">ThreadContext</a></code>
+                  <code><span title="libdebug.state.thread_context.ThreadContext">ThreadContext</span></code>
             </td>
             <td>
               <div class="doc-md-description">

0.8.0/from_pydoc/generated/snapshots/thread/thread_snapshot/index.html

@@ -2076,7 +2076,7 @@ <h3 id="libdebug.snapshots.thread.thread_snapshot.ThreadSnapshot.__init__" class
                 <code>thread</code>
             </td>
             <td>
-                  <code><a class="autorefs autorefs-internal" title="libdebug.state.thread_context.ThreadContext" href="../../../state/thread_context/#libdebug.state.thread_context.ThreadContext">ThreadContext</a></code>
+                  <code><span title="libdebug.state.thread_context.ThreadContext">ThreadContext</span></code>
             </td>
             <td>
               <div class="doc-md-description">

0.8.0/logging/liblog/index.html

@@ -1977,7 +1977,7 @@ <h3 id="debugger-logging"><span class="twemoji"><svg xmlns="http://www.w3.org/20
 <p><img src="https://github.com/libdebug/libdebug/blob/main/media/debugger_argv.png?raw=true" alt="debugger argv option" /></p>
 <h3 id="pipe-logging"><span class="twemoji"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"><path d="M22 14h-2v2h-6v-3h2v-2h-2V6a2 2 0 0 0-2-2H4V2H2v8h2V8h6v3H8v2h2v5a2 2 0 0 0 2 2h8v2h2"/></svg></span> Pipe Logging</h3>
 <p>The <code>pipe</code> option, on the other hand, displays all logs related to interactions with the process pipe: bytes received and bytes sent.</p>
-<p><img src="/assets/pipe_logging.jpeg" alt="pipe argv option" /></p>
+<p><img src="../../assets/pipe_logging.jpeg" alt="pipe argv option" /></p>
 <h3 id="the-best-of-both-worlds"><span class="twemoji"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"><path d="M3 1c-1.11 0-2 .89-2 2v11c0 1.11.89 2 2 2h4v4c0 1.11.89 2 2 2h11c1.11 0 2-.89 2-2V9c0-1.11-.89-2-2-2h-4V3c0-1.11-.89-2-2-2zm0 2h11v6h6v11H9v-6H3z"/></svg></span> The best of both worlds</h3>
 <p>The <code>dbg</code> option is the combination of the <code>pipe</code> and <code>debugger</code> options. It displays all logs related to the debugging operations performed on the process by libdebug, as well as interactions with the process pipe: bytes received and bytes sent.</p>
 <h2 id="changing-logging-levels-at-runtime"><span class="twemoji"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 576 512"><!--! Font Awesome Free 6.7.2 by @fontawesome - https://fontawesome.com License - https://fontawesome.com/license/free (Icons: CC BY 4.0, Fonts: SIL OFL 1.1, Code: MIT License) Copyright 2024 Fonticons, Inc.--><path d="M246.9 14.1C234 15.2 224 26 224 39c0 13.8 11.2 25 25 25h151c8.8 0 16-7.2 16-16V17.4c0-9.4-8-16.7-17.3-16zM240 112c0 44.2 35.8 80 80 80s80-35.8 80-80c0-5.5-.6-10.8-1.6-16H241.6c-1 5.2-1.6 10.5-1.6 16M72 224c-22.1 0-40 17.9-40 40s17.9 40 40 40h152v89.4l162.8-162.9c-13.3-4.3-27.3-6.5-41.6-6.5H72m345.7 20.9L246.6 416H416v-46.3l53.6 90.6c11.2 19 35.8 25.3 54.8 14.1s25.3-35.8 14.1-54.8l-76.2-128.8c-11.2-18.9-26.6-34.5-44.6-45.9M224 448v32c0 17.7 14.3 32 32 32h128c17.7 0 32-14.3 32-32v-32z"/></svg></span> Changing logging levels at runtime</h2>

0.8.0/multithreading/multithreading/index.html

@@ -2322,8 +2322,8 @@ <h3 id="hardware-breakpoints-and-watchpoints"><span class="twemoji"><svg xmlns="
 </div>
 <h3 id="signal-catching"><span class="twemoji"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"><path d="M20 10h-3V8.86c1.72-.45 3-2 3-3.86h-3V4c0-.55-.45-1-1-1H8c-.55 0-1 .45-1 1v1H4c0 1.86 1.28 3.41 3 3.86V10H4c0 1.86 1.28 3.41 3 3.86V15H4c0 1.86 1.28 3.41 3 3.86V20c0 .55.45 1 1 1h8c.55 0 1-.45 1-1v-1.14c1.72-.45 3-2 3-3.86h-3v-1.14c1.72-.45 3-2 3-3.86m-5 9H9V5h6zm-3-1c.83 0 1.5-.67 1.5-1.5S12.83 15 12 15s-1.5.67-1.5 1.5.67 1.5 1.5 1.5m0-4.5c.83 0 1.5-.67 1.5-1.5s-.67-1.5-1.5-1.5-1.5.67-1.5 1.5.67 1.5 1.5 1.5M12 9c.83 0 1.5-.67 1.5-1.5S12.83 6 12 6s-1.5.67-1.5 1.5S11.17 9 12 9"/></svg></span> Signal Catching</h3>
 <div style="text-align: center;">
-    <img src="/assets/bus_diagram_light.png#only-light" loading="lazy" width="512" />
-    <img src="/assets/bus_diagram.png#only-dark" loading="lazy" width="512" />
+    <img src="../../assets/bus_diagram_light.png#only-light" loading="lazy" width="512" />
+    <img src="../../assets/bus_diagram.png#only-dark" loading="lazy" width="512" />
 </div>
 
 <div style="text-align: center; font-size: 0.85rem;">

0.8.0/objects.inv

@@ -1903,7 +1903,7 @@ <h1 id="pretty-printing"><span class="twemoji"><svg xmlns="http://www.w3.org/200
 <p><strong>libdebug</strong> offers utilities to visualize the process's state in a human-readable format and with color highlighting. This can be especially useful when debugging complex binaries or when you need to quickly understand the behavior of a program.</p>
 <h2 id="registers-pretty-printing"><span class="twemoji"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"><path d="M7 7c-1.1 0-2 .9-2 2v6a2 2 0 0 0 2 2h2c1.11 0 2-.89 2-2V9a2 2 0 0 0-2-2zm0 2h2v6H7zm10.6 8-2.1-2.1-2.1 2.1-1.4-1.4 2.1-2.1-2.1-2.1 1.4-1.4 2.1 2.1 2.1-2.1 1.4 1.4-2.1 2.1 2.1 2.1z"/></svg></span> Registers Pretty Printing</h2>
 <p>There are two functions available to print the registers of a thread: <code>pprint_registers()</code> and <code>print_registers_all()</code>. The former will print the current values of the most commonly-interesting registers, while the latter will print all available registers.</p>
-<p><img src="/assets/pprint_regs.jpeg" alt="Pretty Printing Registers" width="100%"/></p>
+<p><img src="../../assets/pprint_regs.jpeg" alt="Pretty Printing Registers" width="100%"/></p>
 <div class="admonition tip">
 <p class="admonition-title">Aliases</p>
 <p>If you don't like long function names, you can use aliases for the two register pretty print functions. The shorter aliases are <code>pprint_regs()</code> and <code>print_regs_all()</code>.</p>
@@ -1944,7 +1944,7 @@ <h2 id="syscall-trace-pretty-printing"><span class="twemoji"><svg xmlns="http://
 </tbody>
 </table>
 <p><a href="../../stopping_events/syscalls">Handled syscalls</a> with a callback associated with them will be listed as such. Additionally, syscalls <a href="../../stopping_events/debugging_flow#hijacking">hijacked</a> through the <strong>libdebug</strong> API will be highlighted as striken through, allowing you to monitor both the original behavior and your own changes to the flow. The id of the thread that made the syscall will be printed in the beginning of the line in white bold.</p>
-<p><img src="/assets/pprint_syscalls.jpeg" alt="Pretty Printing Syscalls" width="`100%"/></p>
+<p><img src="../../assets/pprint_syscalls.jpeg" alt="Pretty Printing Syscalls" width="`100%"/></p>
 <h2 id="memory-maps-pretty-printing"><span class="twemoji"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"><path d="M15.5 12c2.5 0 4.5 2 4.5 4.5 0 .88-.25 1.71-.69 2.4l3.08 3.1L21 23.39l-3.12-3.07c-.69.43-1.51.68-2.38.68-2.5 0-4.5-2-4.5-4.5s2-4.5 4.5-4.5m0 2a2.5 2.5 0 0 0-2.5 2.5 2.5 2.5 0 0 0 2.5 2.5 2.5 2.5 0 0 0 2.5-2.5 2.5 2.5 0 0 0-2.5-2.5M14 6.11 8 4v11.89l1 .35v.26c0 .64.09 1.26.26 1.84L8 17.9l-5.34 2.07-.16.03a.5.5 0 0 1-.5-.5V4.38c0-.23.15-.41.36-.48L8 2l6 2.1L19.34 2h.16a.5.5 0 0 1 .5.5v9.31A6.48 6.48 0 0 0 15.5 10c-.5 0-1 .06-1.5.17z"/></svg></span> Memory Maps Pretty Printing</h2>
 <p>To pretty print the memory maps of a process, you can simply use the <code>pprint_maps()</code> function. This will print the memory maps of the process in a human-readable format, with color highlighting to distinguish between different memory regions.</p>
 <table>
@@ -1977,10 +1977,10 @@ <h2 id="memory-maps-pretty-printing"><span class="twemoji"><svg xmlns="http://ww
 </tr>
 </tbody>
 </table>
-<p><img src="/assets/pprint_maps.jpeg" alt="Pretty Printing Memory Maps" width="100%"/></p>
+<p><img src="../../assets/pprint_maps.jpeg" alt="Pretty Printing Memory Maps" width="100%"/></p>
 <h2 id="stack-trace-pretty-printing"><span class="twemoji"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"><path d="M11.063 1.456a1.75 1.75 0 0 1 1.874 0l8.383 5.316a1.75 1.75 0 0 1 0 2.956l-8.383 5.316a1.75 1.75 0 0 1-1.874 0L2.68 9.728a1.75 1.75 0 0 1 0-2.956Zm1.071 1.267a.25.25 0 0 0-.268 0L3.483 8.039a.25.25 0 0 0 0 .422l8.383 5.316a.25.25 0 0 0 .268 0l8.383-5.316a.25.25 0 0 0 0-.422Z"/><path d="M1.867 12.324a.75.75 0 0 1 1.035-.232l8.964 5.685a.25.25 0 0 0 .268 0l8.964-5.685a.75.75 0 0 1 .804 1.267l-8.965 5.685a1.75 1.75 0 0 1-1.874 0l-8.965-5.685a.75.75 0 0 1-.231-1.035"/><path d="M1.867 16.324a.75.75 0 0 1 1.035-.232l8.964 5.685a.25.25 0 0 0 .268 0l8.964-5.685a.75.75 0 0 1 .804 1.267l-8.965 5.685a1.75 1.75 0 0 1-1.874 0l-8.965-5.685a.75.75 0 0 1-.231-1.035"/></svg></span> Stack Trace Pretty Printing</h2>
 <p>To pretty print the stack trace (<a href="../stack_frame_utils">backtrace</a>) of a process, you can use the <code>pprint_backtrace()</code> function. This will print the stack trace of the process in a human-readable format.</p>
-<p><img src="/assets/pprint_backtrace.jpeg" alt="Pretty Printing Stack Trace" width="100%"/></p>
+<p><img src="../../assets/pprint_backtrace.jpeg" alt="Pretty Printing Stack Trace" width="100%"/></p>
 <h2 id="memory-pretty-printing"><span class="twemoji"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 576 512"><!--! Font Awesome Free 6.7.2 by @fontawesome - https://fontawesome.com License - https://fontawesome.com/license/free (Icons: CC BY 4.0, Fonts: SIL OFL 1.1, Code: MIT License) Copyright 2024 Fonticons, Inc.--><path d="M64 64C28.7 64 0 92.7 0 128v7.4c0 6.8 4.4 12.6 10.1 16.3C23.3 160.3 32 175.1 32 192s-8.7 31.7-21.9 40.3C4.4 236 0 241.8 0 248.6V320h576v-71.4c0-6.8-4.4-12.6-10.1-16.3-13.2-8.6-21.9-23.4-21.9-40.3s8.7-31.7 21.9-40.3c5.7-3.7 10.1-9.5 10.1-16.3V128c0-35.3-28.7-64-64-64zm512 288H0v64c0 17.7 14.3 32 32 32h48v-32c0-8.8 7.2-16 16-16s16 7.2 16 16v32h96v-32c0-8.8 7.2-16 16-16s16 7.2 16 16v32h96v-32c0-8.8 7.2-16 16-16s16 7.2 16 16v32h96v-32c0-8.8 7.2-16 16-16s16 7.2 16 16v32h48c17.7 0 32-14.3 32-32zM192 160v64c0 17.7-14.3 32-32 32s-32-14.3-32-32v-64c0-17.7 14.3-32 32-32s32 14.3 32 32m128 0v64c0 17.7-14.3 32-32 32s-32-14.3-32-32v-64c0-17.7 14.3-32 32-32s32 14.3 32 32m128 0v64c0 17.7-14.3 32-32 32s-32-14.3-32-32v-64c0-17.7 14.3-32 32-32s32 14.3 32 32"/></svg></span> Memory Pretty Printing</h2>
 <p>The <code>pprint_memory()</code> function will print the contents of the process memory within a certain range of addresses.</p>
 <div class="admonition abstract">

0.8.0/quality_of_life/pretty_printing/index.html

@@ -1772,8 +1772,8 @@ <h1 id="stack-frame-utils"><span class="twemoji"><svg xmlns="http://www.w3.org/2
 <p>Function calls in a binary executable are made according to a system calling convention. One constant in these conventions is the use of a stack frame to store the return addresses to resume at the end of the function.</p>
 <p>Different architectures have slightly different ways to retrieve the return address (for example, in AArch64, the latest return address is stored in <code>x30</code>, the Link Register). To abstract these differences, <strong>libdebug</strong> provides common utilities to resolve the stack trace (<em>backtrace</em>) of the running process (or thread).</p>
 <div style="text-align: center;">
-    <img src="/assets/backtrace_plot.png#only-light" loading="lazy" width="85%" />
-    <img src="/assets/backtrace_plot_dark.png#only-dark" loading="lazy" width="85%" />
+    <img src="../../assets/backtrace_plot.png#only-light" loading="lazy" width="85%" />
+    <img src="../../assets/backtrace_plot_dark.png#only-dark" loading="lazy" width="85%" />
 </div>
 
 <p><strong>libdebug</strong>'s <em>backtrace</em> is structured like a LIFO stack, with the top-most value being the current instruction pointer. Subsequent values are the return addresses of the functions that were called to reach the current instruction pointer.</p>