• Johannes Weiner's avatar
    xtensa: always use correct stack pointer for stack traces · 586411dc
    Johannes Weiner authored
    Commit '28a0ce7f
     xtensa: use correct stack pointer for stack traces'
    changed the stack tracer from always reading the stack pointer
    register to always using the saved value in the task descriptor.
    The author was too dense to consider the fact that the saved stack
    value is stale for a running process und thus unusable for 'current'.
    What we do now is to use the stack pointer register (a1) for when the
    task is unknown - we can't help it then - or when the task is
    'current'.  For everything else use the saved stack pointer value
    contained in the task descriptor.
    Signed-off-by: default avatarJohannes Weiner <jw@emlix.com>
    Signed-off-by: default avatarChris Zankel <chris@zankel.net>
traps.c 12.3 KB