[Bug c++/48394] New: ObjC exceptions cannot be caught in ObjC++

[Bug c++/48394] New: ObjC exceptions cannot be caught in ObjC++

[js-gcc at webkeks dot org]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48394

           Summary: ObjC exceptions cannot be caught in ObjC++
           Product: gcc
           Version: 4.6.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: js-gcc@webkeks.org


When trying to catch an ObjC exception in ObjC++, the object you get is bogus.
For example, this crashes:

@try {
        @throw [[OFObject alloc] init];
} @catch (id e) {
        [e release];
}

Trying to printf("%p", …) the exception before the throw and in the catch shows
that the pointer differs, which should not happen. I had this bug in various
GCC versions from 4.2 up to 4.6. I suspect even earlier versions are affected.

It would be nice if even for older versions an update could be released,
because some platforms are still stuck with gcc 4.2 or 4.4.

[Bug objc++/48394] ObjC exceptions cannot be caught in ObjC++

[paolo.carlini at oracle dot com]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48394

Paolo Carlini <paolo.carlini at oracle dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |nicola at gcc dot gnu.org
          Component|c++                         |objc++

--- Comment #1 from Paolo Carlini <paolo.carlini at oracle dot com> 2011-10-09 15:16:27 UTC ---
Nicola, this one was miscategorized as C++. Can you help triaging it?

[Bug objc++/48394] ObjC exceptions cannot be caught in ObjC++

[nicola at gcc dot gnu.org]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48394

Nicola Pero <nicola at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |DUPLICATE

--- Comment #2 from Nicola Pero <nicola at gcc dot gnu.org> 2011-10-09 23:11:09 UTC ---
Yes, as far as I can see this is basically a duplicate of objc++/23616.

The problem is that Objective-C exceptions in ObjC++ simply don't work due
to a basic problem in the implementation. :-(

Thanks

*** This bug has been marked as a duplicate of bug 23616 ***