I forgot to post back that I did eventually find the solution to this
problem.
I had it come back and bite me in the butt a second time and it took me a
lot longer to figure it out because I kept finding this thread and not the
thread where I had made mention of the solution.
Dear Future AJ,
Th
On Tue, Apr 19, 2011 at 10:58:28AM +1200, Michael Hope wrote:
> Hi AJ. Exception support can still be turned on in C code when it's
> supposed to interoperate with C++ code. An example is the 64 bit
> division routine in libgcc - it could potentially throw a division by
> zero exception when call
Hi AJ. Exception support can still be turned on in C code when it's
supposed to interoperate with C++ code. An example is the 64 bit
division routine in libgcc - it could potentially throw a division by
zero exception when called from C++ code even though the function is
written in C.
-- Michael
What is an "exception" in C?
There is no CPP (.cpp or .cxx) code in any of these libraries.
Interesting thing though:
cmem has a userspace and kernelspace component.
TI does really nasty stuff, like pull in .h files from the kernel and
whatnot.
I just tried again against the 2.6.38 kernel (was 2
On Tue, Apr 19, 2011 at 5:39 AM, AJ ONeal wrote:
>
> I'm compiling an application built with TI's DVSDK 3 *[0].
>
>
>
> /home/user/ti/dvsdk/dvsdk_3_01_00_10/linuxutils_2_25_02_08/packages/ti/sdo/linuxutils/cmem/lib/cmem.a470MV(cmem.o470MV):(.ARM.exidx+0x0):
> undefined reference to `__aeabi_unwind