Add documentation for pipeline

Signed-off-by: Tushar Goel <[email protected]>

Author: TG1999

docs/built-in-pipelines.rst

@@ -52,6 +52,14 @@ Find Vulnerabilities
 
 .. _pipeline_inspect_packages:
 
+Inspect Elf Binaries
+---------------------
+.. autoclass:: scanpipe.pipelines.inspect_elf_binaries.InspectElfBinaries()
+    :members:
+    :member-order: bysource
+
+.. _pipeline_inspect_elf:
+
 Inspect Packages
 ----------------
 .. autoclass:: scanpipe.pipelines.inspect_packages.InspectPackages()

docs/faq.rst

@@ -39,6 +39,8 @@ Here are some general guidelines based on different input scenarios:
   use the :ref:`inspect_packages <pipeline_inspect_packages>` pipeline.
 - For scenarios involving both a **development and deployment codebase**, consider using
   the :ref:`map_deploy_to_develop <pipeline_map_deploy_to_develop>` pipeline.
+- For getting the DWARF debug symbol compilation unit paths when available from an elf binary.
+  use the :ref:`inspect_elf_binaries <pipeline_inspect_elf>` pipeline.
 
 These pipelines will automatically execute the necessary steps to scan and create the
 packages, dependencies, and resources for your project based on the input data provided.