On 02/13/2013 05:41 PM, Stephan Bergmann wrote:
On 02/13/2013 04:46 PM, Tor Lillqvist wrote:
so that some catch block that should match doesn't.
Isn't one typical problem that two type_infos are compared for
equality by comparing the name string pointers instead of comparing
the name strings w
On 02/13/2013 04:46 PM, Tor Lillqvist wrote:
so that some catch block that should match doesn't.
Isn't one typical problem that two type_infos are compared for
equality by comparing the name string pointers instead of comparing
the name strings with strcmp? I have seen stuff like that both in t
> so that some catch block that should match doesn't.
Isn't one typical problem that two type_infos are compared for
equality by comparing the name string pointers instead of comparing
the name strings with strcmp? I have seen stuff like that both in the
Android and iOS ports, I think. Unfortunate
On 02/09/2013 10:04 PM, Henrik /KaarPoSoft wrote:
Program received signal SIGABRT, Aborted.
0x76fcaf65 in __GI_raise (sig=sig@entry=6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:63
63 ../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or directory.
#0 0x76fcaf65 in __GI_