Hi,
I also tried to search for tools that could identify alignment problems
automatically, but did not find anything useful. Probably the most easy
way to make such tool is to modify valgrind to track alignment for each
memory access operation. But don't know, I ended up finding and fixing
On Wed, Aug 23, 2006 at 10:52:58PM +0300, Siarhei Siamashka wrote:
But ARM is alignment sensitive, so you may have problems because of bad
alighment, I started making a page on wiki describing this issue (still very
incomplete): http://maemo.org/maemowiki/PortingFromX86ToARM
Thank you for
On Monday 21 August 2006 10:45, Detlef Schmicker wrote:
I had a look at the vncviewer and saw, that it is working in the sandbox
in connection with vino (gnome vnc server). On the device the CoRRE
encoding does not work.
Probably it is a byte order problem. The code has a lot of byte order
Hello,
I had a look at the vncviewer and saw, that it is working in the sandbox
in connection with vino (gnome vnc server). On the device the CoRRE
encoding does not work.
Probably it is a byte order problem. The code has a lot of byte order
(e.g. GUINT16_TO_BE). Is there a way to automaticaly
Hello,
The (linux) kernel has endianess-aware integer types (__be_u16 or
something similar) which allow the access to be checked for endianess
problems (basically reading an endianess-annotated type into a
non-endianess-specified (ie native endianess) type must go through a
byte order macro).
