From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-return-105663-listarch-gcc=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 10912 invoked by alias); 23 Nov 2004 22:29:14 -0000
Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Archive: <http://gcc.gnu.org/ml/gcc/>
List-Post: <mailto:gcc@gcc.gnu.org>
List-Help: <http://gcc.gnu.org/ml/>
Sender: gcc-owner@gcc.gnu.org
Received: (qmail 10856 invoked from network); 23 Nov 2004 22:29:09 -0000
Received: from unknown (HELO smtp1.clear.net.nz) (203.97.33.27)
  by sourceware.org with SMTP; 23 Nov 2004 22:29:09 -0000
Received: from DANNY (218-101-109-10.dialup.clear.net.nz [218.101.109.10])
 by smtp1.clear.net.nz (CLEAR Net Mail)
 with SMTP id <0I7N00EO7L4JNW@smtp1.clear.net.nz> for gcc@gcc.gnu.org; Wed,
 24 Nov 2004 11:29:09 +1300 (NZDT)
Date: Tue, 23 Nov 2004 22:41:00 -0000
From: Danny Smith <dannysmith@clear.net.nz>
Subject: stdcall lib functions with exception throwing callbacks vs Dwarf2 EH
To: gcc@gcc.gnu.org
Cc: Cygwin <cygwin@cygwin.com>, mingw-dvlpr <mingw-dvlpr@lists.sourceforge.net>
Reply-to: Danny Smith <dannysmith@users.sourceforge.net>
Message-id: <001701c4d1ab$949322e0$0a6d65da@DANNY>
MIME-version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
X-SW-Source: 2004-11/txt/msg00856.txt.bz2

Hi, 
I've been trying to get DW2 EH exception handling working
on windows targets with general success, but have hit a snag.

If a C library function that takes a callback arg is compiled
using stdcall convention, C++ exception thrown by the callback
result in abort.

If the C libarary function uses normal (cdelc) calling convention
than exceptions thrown by callback are handled.

Example:



==============================================
/* callback.c  library functions */
/* compile this with c */

void
caller_c (void (*callback)(void))
{
  callback();
}


void __attribute__((stdcall))
caller_s (void (*callback)(void))
{
  callback();
}

==============================================

/* main.cc */
#include <stdio.h>
extern "C"
{
  typedef void (*foo)(void);
  extern void  caller_c (foo); 
  extern void __attribute__ ((__stdcall__)) caller_s (foo);  
}

void callback (void) 
{
  printf ("Hello from callback\n");
  fflush (stdout);  
  throw 1;
}


int main ()
{
  try {
    printf ("Testing cdecl\n");
    caller_c (callback);
  }
  catch (int) {
    printf ("Caught cdecl\n"); 
  }

  try {
    printf ("\nTesting stdcall\n");
    caller_s (callback);
  }
  catch (int) {
    printf ("Caught stdcall\n");
  }

return 0;
}

==================================================

Compiling with sjlj enabled compiler:

gcc -c -o callback.o callback.c
g++-sjlj -o main-sjlj.exe main.cc callback.o

Both throws are caught.

However, if using DW2 EH enabled compiler

g++-dw2 -omain-dw2.exe main.cc callback.o

I get this:

> Testing cdecl
> Hello from callback
> Caught cdecl

> Testing stdcall
> Hello from callback
>
> abnormal program termination.


This is significant for windows targets, since the
OS win32 api uses stdcall almost exclusively.

Before I pull any more hair out trying, does any one have any hints on
how to use an MD_FALLBACK_FRAME_STATE_FOR to workaround, or is this a
blocker for the use of DW2 EH on windows targets.

Danny