From 7a53483ba8ff8783c57ce26931f2030565c311c5 Mon Sep 17 00:00:00 2001
From: Ciro Santilli <ciro.santilli@gmail.com>
Date: Thu, 12 Jul 2018 16:36:56 +0100
Subject: [PATCH] README: step debug dynamic loader stub

---
 README.adoc | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/README.adoc b/README.adoc
index 955f249..c09472b 100644
--- a/README.adoc
+++ b/README.adoc
@@ -2223,6 +2223,12 @@ which automatically finds unstripped shared libraries on the host for us.
 
 See also: https://stackoverflow.com/questions/8611194/debugging-shared-libraries-with-gdbserver/45252113#45252113
 
+=== gdbserver dynamic loader
+
+TODO: try to step debug the dynamic loader. Would be even easier if `starti` is available: https://stackoverflow.com/questions/10483544/stopping-at-the-first-machine-code-instruction-in-gdb
+
+Bibliography: https://stackoverflow.com/questions/20114565/gdb-step-into-dynamic-linkerld-so-code
+
 == CPU architecture
 
 The portability of the kernel and toolchains is amazing: change an option and most things magically work on completely different hardware.