|
Re: C++ exceptions: msg#00003gnu.cegcc.devel
On Fri, Jun 22, 2007 at 09:37:21PM +0200, Danny Backx wrote: > The null.C example however - when used with my exception handling code - > shows a dialog from my new exception handler, but never makes its way to > the C++ exception handler. Have you figured out a way to raise a c++ exception from the wince handler? > Running the null.C program on Linux creates a coredump too, no exception > handler is called. Invalid memory accesses don't cause exceptions under Linux. Also, it appears gcc may optimize out c++ exception handlers if it doesn't think the code can create an exception. It thinks it is running under a linux like environment and the optimizer wont even try to handle memory raised exceptions. > I assumed that the goal is to have the system level exception (from use > of a null pointer) be caught by the C++ exception handler. Am I wrong ? That is certainly what I'd like to see. :-) Thanks for looking at this. -Kevin ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ |
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| Previous by Date: | Rshd - blanks in path names: 00003, Danny Backx |
|---|---|
| Next by Date: | Re: C++ exceptions: 00003, Danny Backx |
| Previous by Thread: | Rshd - blanks in path namesi: 00003, Danny Backx |
| Next by Thread: | Re: C++ exceptions: 00003, Danny Backx |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
| News | FAQ | advertise |