Native c++ code try/catch support or not?

[wjjsun]

Hi,

When I try to compile a C++ code with try/catch statements, it can not pass build.
Does anyone know if try/catch is supported or not in android? Or how can I fix this issue?

test code:
#include <stdio.h>

int main()
{
try
{
printf("try statement\n");
throw 1;
}
catch (...)
{
printf("catch exeption here\n");
}
}

Android.mk
LOCAL_PATH := $(call my-dir)
include $(CLEAR_VARS)

LOCAL_ARM_MODE := arm

LOCAL_SRC_FILES := \
./test.cpp

LOCAL_CFLAGS += -fexceptions

LOCAL_LDFLAGS += -lstdc++

LOCAL_MODULE := test

include $(BUILD_EXECUTABLE)

compile error:
mydroid/try_catch/./test.cpp:9: undefined reference to `__cxa_allocate_exception'

wjjsun
2008/12/22

[Emyr]

Wouldn't it be easier just to do it in Java like everyone else?

If you're really fussy about your limited coding skillset, read this thread:
http://groups.google.com/group/andro...7594c37a?pli=1

[wjjsun]

Thanks,Emyr,

I want to porting a C/C++ project to android native code, which means it's impossible to rewrite it in JAVA language. just as tcpdump project is porting to android by default.

But during porting, I found try/catch statement will cause compile problem.

Any idea to handle such case?

BRs
wjjsun
2009/01/02

[jjagogo]

Google implemented their own libc and libc++ routines instead of using the gnu software. The goal was to get around some licensing issues and create a light weight set of libraries. They decided NOT to implement exceptions in there implementation. You could cross compile a linux for ARM and install the libraries needed for exceptions, but since space is limited you'll probably have to put it in the SD card.

[Ageless Stranger]

I have been programming for over 18 years and never had the need to use one try or catch statement, and I use c/c++ most of the time. I know the benefits of using try/catch, but I guess I am too pedantic when it comes to coding, checking pointers whenever I use them, checking return types and acting on them in a structured way. Things like try/catch and garbage collection has made programmers lazy, but I guess this is the "new" thing (pun intended) and I'm old and set in my ways. Why stop at native c or c++ when you can do it in assembler? hmm maybe that is going a little too far, but I wouldnt mind coding in fortran for the G1

[Emyr]

Exceptions thrown by library functions in Java make sure programmers don't ignore type conversion errors and errors they might not usually consider... Or at least that's what I'd like to believe!