-------- Forwarded Message --------
Subject:        [PATCH 1/3] When stepping and plt is UNRESOLVED we need to
stop to avoid undefinite loop
Date:   Wed, 23 Mar 2016 11:13:03 +0100
From:   Thierry Fauck <[email protected]>
To:     [email protected]
CC:     Thierry Fauck <[email protected]>



From: Thierry Fauck <[email protected]>

This patch return appropriate flag to stop stepping

        modified:   sysdeps/linux-gnu/ppc/plt.c

Signed-off-by: Thierry Fauck <[email protected]>
---
 sysdeps/linux-gnu/ppc/plt.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/sysdeps/linux-gnu/ppc/plt.c b/sysdeps/linux-gnu/ppc/plt.c
index 5f81889..2238e4e 100644
--- a/sysdeps/linux-gnu/ppc/plt.c
+++ b/sysdeps/linux-gnu/ppc/plt.c
@@ -946,7 +946,7 @@ cb_keep_stepping_p(struct process_stopping_handler *self)
        /* In UNRESOLVED state, the RESOLVED_VALUE in fact contains
         * the PLT entry value.  */
        if (value == libsym->arch.resolved_value)
-               return CBS_CONT;
+               return CBS_STOP;
 
        debug(DEBUG_PROCESS, "pid=%d PLT got resolved to value %#"PRIx64,
              proc->pid, value);
-- 
2.7.0



_______________________________________________
Ltrace-devel mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/ltrace-devel

Reply via email to