> I am having a problem with the Insight debugger in the latest MSP430 Windows
> toolchain. It does not report the correct value for parameters that are
> passed on the stack.
> 

Unrelated as such, but this complaint reminds me of another.
I'm using the 3.0.4 compiler and the 5.1.1 gdb (yeah, I know!). The "bt"
command normally works fine whenever the machine had been running normally.
However, the stack trace is quite useless if it had been servicing an
interrupt. It would be *so* useful to know what background task had been
running (and where) at the point the interrupt happened.

I guess it's down to the 'bt' stack analyser not taking enough care to realise
that it's looking at a stack containing a push-sequence associated with an
interrupt.

Can this be fixed? Is there even enough info on the stack to let "bt" do
the reverse-analysis?

--

Steve Hosgood                               |
[email protected]                          | "A good plan today is better
Phone: +44 1792 203707 + ask for Steve      |   than a perfect plan tomorrow"
Fax:   +44 70922 70944                      |              - Conrad Brean
--------------------------------------------+
        http://tallyho.bc.nu/~steve         |  ( from the film "Wag the Dog" )



Reply via email to