Re: C++ exceptions in C [was: Re: CVS commit: src/external/bsd/atf/dist/atf-c++]

[christos%astron.com@localhost (Christos Zoulas)]

In article 
<AANLkTimNWTtDaomIpHJ9ZeDTJzdjl-Y9W83SAhl2d_B0%mail.gmail.com@localhost>,
Julio Merino  <jmmv%NetBSD.org@localhost> wrote:
>Hi toolchainers,
>
>[ Please CC me any replies ]
>
>Can anyone that understands the C/C++ ABI provide some insight on the
>change below?  I'm interested in knowing which behavior is right
>(i386's or amd64's) or if this is behavior is just undefined.  In the
>former case, I'll write a test case for the problem; in the latter,
>I'll just ignore it :-P
>
>Summarizing: what should happen when a C++ function calls a C function
>that, in turn, calls another C++ function that throws exceptions?  Up
>to where should exceptions propagate?  Intuition tells me that they
>should never reach C land.  (Yeah, no comments on this bizarre
>setup...)

I think it is undefined.

christos