On Jul 9, 2007, at 2:22 PM, David Daney wrote:
Joshua ChaitinPollak wrote:
On Jul 9, 2007, at 1:43 PM, David Daney wrote:
You don't say what version of uclibc you are using.
The last time I checked, exception handling on uClibc was
foobar. I am not sure if it is true for the versions you a
Joshua ChaitinPollak wrote:
On Jul 9, 2007, at 1:43 PM, David Daney wrote:
You don't say what version of uclibc you are using.
The last time I checked, exception handling on uClibc was foobar. I
am not sure if it is true for the versions you are using. There may
be patches floating around
On Jul 9, 2007, at 1:43 PM, David Daney wrote:
You don't say what version of uclibc you are using.
The last time I checked, exception handling on uClibc was foobar.
I am not sure if it is true for the versions you are using. There
may be patches floating around that make things work (I kn
Joshua ChaitinPollak wrote:
Hello,
I'm at my wits end. I'm building a C++ application for an embedded
device, but I'm having trouble catching exceptions within the embedded
environment. The exact same code works fine on my regular desktop
environment, with the same version of GCC (4.1.2).
I've
Hello,
I'm at my wits end. I'm building a C++ application for an embedded
device, but I'm having trouble catching exceptions within the embedded
environment. The exact same code works fine on my regular desktop
environment, with the same version of GCC (4.1.2).
I've been able to boil this down to
