Re: [Cegcc-devel] Catching exceptions with mingw32ce

2007-07-10 Thread Pedro Alves
Hi Danny, Somehow I missed this mail entirely. Sorry for that. In case it still helps and for the record, I'll reply below. Probably you've found this stuff out by yourself by now. Danny Backx wrote: > On Sun, 2007-06-03 at 19:01 +0100, Pedro Alves wrote: >> The exception c++ model that both mi

Re: [Cegcc-devel] Catching exceptions with mingw32ce

2007-06-09 Thread Danny Backx
On Sun, 2007-06-03 at 19:01 +0100, Pedro Alves wrote: > The exception c++ model that both mingw32ce and cegcc use is the sjlj model. > It is similar with the SEH model on x86. It certainly works. > > SEH is an OS thing, so it always works, but it happens that registering > handlers manually is mu

Re: [Cegcc-devel] Catching exceptions with mingw32ce

2007-06-05 Thread Pedro Alves
On 6/5/07, Kevin O'Connor <[EMAIL PROTECTED]> wrote: > On Sun, Jun 03, 2007 at 11:09:34PM +0100, Pedro Alves wrote: > > Kevin O'Connor wrote: > > > So, is it possible to have mingw32ce install a global SEH handler that > > > just translates the exception into an sjlj one? That is, can we > > > mod

Re: [Cegcc-devel] Catching exceptions with mingw32ce

2007-06-04 Thread Kevin O'Connor
On Sun, Jun 03, 2007 at 11:09:34PM +0100, Pedro Alves wrote: > Kevin O'Connor wrote: > > So, is it possible to have mingw32ce install a global SEH handler that > > just translates the exception into an sjlj one? That is, can we > > modify the standard crt0.S file so that it causes wince exceptions

Re: [Cegcc-devel] Catching exceptions with mingw32ce

2007-06-03 Thread Pedro Alves
Kevin O'Connor wrote: > Hi Pedro, > > I'm going to reply to both your emails here. > > On Sat, Jun 02, 2007 at 08:20:12PM +0100, Pedro Alves wrote: >> Hi Kevin, >> >> glad to see you're still around :) > > Heh, my silence was just because everything has been working really > well. :-) > > On S

Re: [Cegcc-devel] Catching exceptions with mingw32ce

2007-06-03 Thread Kevin O'Connor
Hi Pedro, I'm going to reply to both your emails here. On Sat, Jun 02, 2007 at 08:20:12PM +0100, Pedro Alves wrote: > Hi Kevin, > > glad to see you're still around :) Heh, my silence was just because everything has been working really well. :-) On Sun, Jun 03, 2007 at 07:01:35PM +0100, Pedro

Re: [Cegcc-devel] Catching exceptions with mingw32ce

2007-06-03 Thread Pedro Alves
Danny Backx wrote: > On Sat, 2007-06-02 at 20:59 +0100, Pedro Alves wrote: >> Pedro Alves wrote: >>> Kevin O'Connor wrote: >>> I recently ported the haret application >>> (http://www.handhelds.org/moin/moin.cgi/HaRET) to mingwce32. In the >>> process, I used the c++ compiler, mainly because there

Re: [Cegcc-devel] Catching exceptions with mingw32ce

2007-06-03 Thread Danny Backx
On Sat, 2007-06-02 at 20:59 +0100, Pedro Alves wrote: > Pedro Alves wrote: > > Kevin O'Connor wrote: > > I recently ported the haret application > > (http://www.handhelds.org/moin/moin.cgi/HaRET) to mingwce32. In the > > process, I used the c++ compiler, mainly because there were a few > > places

Re: [Cegcc-devel] Catching exceptions with mingw32ce

2007-06-02 Thread Pedro Alves
Pedro Alves wrote: > Hi Kevin, > > glad to see you're still around :) > > Kevin O'Connor wrote: >> I recently ported the haret application >> (http://www.handhelds.org/moin/moin.cgi/HaRET) to mingwce32. In the >> process, I used the c++ compiler, mainly because there were a few >> places in the

Re: [Cegcc-devel] Catching exceptions with mingw32ce

2007-06-02 Thread Pedro Alves
Hi Kevin, glad to see you're still around :) Kevin O'Connor wrote: > > I recently ported the haret application > (http://www.handhelds.org/moin/moin.cgi/HaRET) to mingwce32. In the > process, I used the c++ compiler, mainly because there were a few > places in the existing msvc code that would

[Cegcc-devel] Catching exceptions with mingw32ce

2007-06-02 Thread Kevin O'Connor
Hi, I recently ported the haret application (http://www.handhelds.org/moin/moin.cgi/HaRET) to mingwce32. In the process, I used the c++ compiler, mainly because there were a few places in the existing msvc code that would catch bad pointer accesses and handle them gracefully. In the old code you