--- In lpc2000@yahoogroups.com, 42Bastian Schick <bastian42@m...> wrote: > > A simple stack corruption. > That was it: An intelligent piece of HW replied with a "cannot happen (TM)" number of bytes, and the following copy routine exceeded the array boundaries, and hence clobbered the stack. I am still interested to see some piece of code to dissect the stack when a UNDEF exception occurs, so I can pinpoint the cause more easily.... > Normaly not that obvious coded :-) Exactly.... :-) Gunter
Message
Re: undef exception analysis
2005-11-30 by gm_muc