new unaligned traps

[Oscar Levi <elf@buici.com>]

Since upgrading a couple of days ago, I'm getting new unaligned traps
in a program that didn't use to have any.  In debugging it, I see they
are comming from the runtime startup code, probably in the c++
library.

 > ldd puree
 liblockfile.so.0 => /usr/lib/liblockfile.so.0 (0x0000020000002000)
 libstdc++-libc6.0-1.so.2 => /usr/lib/libstdc++-libc6.0-1.so.2 (0x0000020000104000)
 libm.so.6.1 => /lib/libm.so.6.1 (0x0000020000266000)
 libc.so.6.1 => /lib/libc.so.6.1 (0x0000020000392000)
 /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x0000020001000000)

It's hard to get a handle on the location of the unaligned trap since
the symbol for the trapping addresses is unavailable.

Too, I'm unsure about the memory layout.  Does the 2000 base for
liblockfile.so mean that an unaligned trap at 

  puree(1172): unaligned trap at 00000200000087a0: 000002000036750c 2d 1
  puree(1172): unaligned trap at 0000020000008798: 000002000036a044 29 1
  puree(1172): unaligned trap at 00000200000087a0: 000002000036a044 2d 1

is in that code?