[coldfire-gnu-discuss] Weird behavior in gdb (m5475) ?
Nathan Sidwell
nathan at codesourcery.com
Wed Mar 28 09:48:53 UTC 2007
Andreas Engberg wrote:
> (gdb) x /i 0x4e2
> 0x4e2 <_puts_r+18>: movel %d2,%fp@(20463)
> (gdb) x /x 0x4e2
> 0x4e2 <_puts_r+18>: 0x2d424fef
>
> This is close but no cigar. According to objdump, the data (or in this
> case instruction) at address 0x4e2 should be :
> 4e2: 2d42 ffe4 movel %d2,%fp@(-28)
> Frankly, I'm puzzled.
hm, we've never seen this. We did notice a problem on our 5485 board where the
P&E wiggler would report multiple bus errors after a single erroneous access
(the bus error behaviour was sticky, and cleared after a time). P&E confirmed a
firmware bug and we'll be providing updated windows drivers in the next release
(which is imminent). I don't know if other issues were fixed at the same time.
Have you verified whether individual writes by gdb are read back correctly. Try
both byte and long writes with multiple alignments.
It's extremely odd that only certain parts of the 32bit word are being scrambled
like so -- and only certain addresses.
> Ideas? Suggestions? Oh, I've also downloaded the 30day pro. version but
> the problem persist.
Well, you can always avail yourself of the technical support that that
evaluation provides :)
nathan
--
Nathan Sidwell :: http://www.codesourcery.com :: CodeSourcery
nathan at codesourcery.com :: http://www.planetfall.pwp.blueyonder.co.uk
More information about the coldfire-gnu-discuss
mailing list