If you could correlate place of error with the source code you could get=20
more information. From the dump you provided it is in main+92 offset.=20
You can try looking at line information and see which line corresponds=20
to this offset. Try objdump and see if you can figure out where exactly=20
in source code this happens.

Regards,
Alex


R=E9mi Zara wrote:
>=20
> Le 26 avr. 07 =E0 23:12, Alex Pelts a =E9crit :
>=20
>> It is not the mapping that is the problem but alignment. It is trying=20
>> to store word (32 bits) at the address that is aligned on 1 byte (cf).
>> I don't know much about how netbsd translates mips exceptions to=20
>> signals but I think from your register dump the problem is alignment.
>=20
> Interesting !
> So maybe some option is lacking for GCC ? it seems to build ok on debia=
n=20
> 3.1 with gcc version 3.3.5 (Debian 1:3.3.5-13) (see=20
> http://www.pgbuildfarm.org/cgi-bin/show_status.pl?member=3Dlionfish)
> without any option. Any idea ?
>=20
> I'm using
>=20
> bash-3.2# gcc -v
> Using built-in specs.
> Target: mipsel--netbsd
> Configured with: /usr/src/tools/gcc/../../gnu/dist/gcc4/configure=20
> --enable-long-long --disable-multilib --enable-threads --disable-symver=
s=20
> --build=3Dx86_64-unknown-netbsd4.99.12 --host=3Dmipsel--netbsd=20
> --target=3Dmipsel--netbsd
> Thread model: posix
> gcc version 4.1.2 20070110 prerelease (NetBSD nb1 20070110)
>=20
>=20
> Regards,
>=20
> R=E9mi Zara
>=20
>> Regards,
>> Alex
>=20
>=20