Re: Problem with exceptions on arm

[Henrik Grindal Bakken <hgb@ifi.uio.no>]

"Martin Guy" <martinwguy@yahoo.it> writes:

> On 3/27/08, Henrik Grindal Bakken <hgb@ifi.uio.no> wrote:
>>
>>  Hi.  I have built myself a cross-compiler x86->arm-linuxeabi, with
>>  which I'm having some problems.
>>  When I run on target, a simple test program with exceptions fail:
>>  $ /tmp/fnord
>>  terminate called after throwing an instance of 'char*'
>>  terminate called recursively
>>  Aborted
>
> Hi Henrik
>   I just tried your test program on Debian "armel"'s native gnueabi
> g++ (4.2.3), and it catches "hello" fine. Their gcc -v says:
>
> Using built-in specs.
> Target: arm-linux-gnueabi
> Configured with: ../src/configure -v
> --enable-languages=c,c++,fortran,obj-c++,treelang --prefix=/usr
> --enable-shared --with-system-zlib --libexecdir=/usr/lib
> --without-included-gettext --enable-threads=posix --enable-nls
> --with-gxx-include-dir=/usr/include/c++/4.2 --program-suffix=-4.2
> --enable-clocale=gnu --enable-libstdcxx-debug --enable-mpfr
> --disable-libmudflap --disable-libssp --disable-sjlj-exceptions
> --enable-checking=release --build=arm-linux-gnueabi
> --host=arm-linux-gnueabi --target=arm-linux-gnueabi
> Thread model: posix
> gcc version 4.2.3 (Debian 4.2.3-2)
>
> In case that's any help

Thanks, Martin.  It does help a little, I guess (ruling out
sjlj-exceptions, for one), but nothing springs at me from that
configure line.  Could this be kernel related?

-- 
Henrik Grindal Bakken <hgb@ifi.uio.no>
PGP ID: 8D436E52
Fingerprint: 131D 9590 F0CF 47EF 7963  02AF 9236 D25A 8D43 6E52