[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [tcf-dev] TCF arm stack unwind issue
|
Hi Carl,
TCF debugger does check for identical frames, it can handle non-ABI stack, and it traces only several frames at a time - exact number depends on user preferences. I'm not sure what could possibly cause an infinite loop. Could you send a test case?
Thanks,
Eugene
-----Original Message-----
From: tcf-dev-bounces@xxxxxxxxxxx [mailto:tcf-dev-bounces@xxxxxxxxxxx] On Behalf Of Carl van Schaik
Sent: Friday, April 24, 2015 11:04 PM
To: tcf-dev@xxxxxxxxxxx
Subject: [tcf-dev] TCF arm stack unwind issue
Hi,
We have run into a potential TCF bug on ARM using Luna 4.4 - not checked on
latest.
Eclipse enters an infinite loop attempting to read the stack and needs to be
closed. The issue occurs with a breakpoint in an ISR handler which may not
have a ABI compliant stack.
GDB only tries to read the memory at LR when given the "where" or
"backtrace" commands, then it detects successive identical stack frames and
stops:
(gdb) where
#0 0x60000068 in ?? ()
#1 0x60000054 in ?? ()
#2 0x60000054 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
Whilst Eclipse is in its infinite loop and the IDE becomes unresponsive.
Thanks,
Carl
_______________________________________________
tcf-dev mailing list
tcf-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/tcf-dev
This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately.
