Exception propagation with optimization flags

["ldb" <ldb_nospam@hotmail.com>]

Can someone explain why this particular combinations of build flags
causes exceptions to stop propagating. I'm kind of at a loss for this.
This is a nested function, which raises, catches, prints some info and
reraises an exception, and a main program which is trying to catch this
exception, to print some further information. I've created a "minimal"
program to show the problem. This is gnatmake/gcc 3.4.5.

And, if anyone is an expert, can you explain to me the connection (if
there is one) with "libunwind-exceptions" in my gcc ./configure.

When I build with -O2 and -fomit-frame-pointer I get this:
EXCEPTION

raised SUPER.AWESOME.AWESOME_EXCEPTION : super.adb:12

If I remove -fomit-frame-pointer _or_ go down to -O1 (both o2 and fomit
are required to get the behavior), I get this:
EXCEPTION
HOLY MOLY


---------------------
with Ada.Text_Io; use Ada.Text_Io;

procedure Super is

   procedure Awesome is
      Awesome_Exception : exception;
   begin
      raise Awesome_Exception;
   exception
      when others =>
         Put_Line("EXCEPTION");
         raise Awesome_Exception;
   end Awesome;


begin
   Awesome;
exception
   when others=>
      Put_Line("HOLY MOLY");
end Super;
---------------------