search for: rethrown

...terminate the program if it detects > that unwinding the exception only results in matches with cleanups. > Isn't that what's supposed to happen if there's no handler anywhere? It is, and it is what will happen: with the current code you will unwind into each landing pad and be rethrown until you get to the top. Then the program will be terminated. Yes, this means that you get terminated slightly more slowly than with gcc, however I don't see how to obtain correct invoke semantics (and thus: correctly working programs) without it. > - What is the right thing for Linux?...

...detects >> that unwinding the exception only results in matches with cleanups. >> Isn't that what's supposed to happen if there's no handler anywhere? > > It is, and it is what will happen: with the current code you will > unwind > into each landing pad and be rethrown until you get to the top. > Then the > program will be terminated. Yes, this means that you get > terminated slightly > more slowly than with gcc, however I don't see how to obtain > correct invoke > semantics (and thus: correctly working programs) without it. > &gt...

...llvm.eh.selector.i32( i8* %eh_ptr.i, i8* bitcast (i32 (...)* > @__gxx_personality_v0 to i8*), i32 0) > then it doesn't work either: the unwinder observes that there is > only a cleanup, and > using some special logic (bogus in this case) deduces that the > exception will be rethrown > after running the cleanup code (and thus the program terminated), so > doesn't bother running > the cleanup code and directly terminates the program (apparently > terminating programs quickly > was important to whoever wrote the unwinder, I don't know why; the > Ad...

...%eh_ptr.i, i8* bitcast (i32 (...)* > > @__gxx_personality_v0 to i8*), i32 0) > > then it doesn't work either: the unwinder observes that there is > > only a cleanup, and > > using some special logic (bogus in this case) deduces that the > > exception will be rethrown > > after running the cleanup code (and thus the program terminated), so > > doesn't bother running > > the cleanup code and directly terminates the program (apparently > > terminating programs quickly > > was important to whoever wrote the unwinder, I don'...

...ail call i32 (i8*, i8*, ...)* @llvm.eh.selector.i32( i8* %eh_ptr.i, i8* bitcast (i32 (...)* @__gxx_personality_v0 to i8*), i32 0) then it doesn't work either: the unwinder observes that there is only a cleanup, and using some special logic (bogus in this case) deduces that the exception will be rethrown after running the cleanup code (and thus the program terminated), so doesn't bother running the cleanup code and directly terminates the program (apparently terminating programs quickly was important to whoever wrote the unwinder, I don't know why; the Ada unwinder doesn't do this for e...

So I couldn't get exceptions to work on PPC darwin. After much digging and confusion, there seem to be two separate issues. The gcc testsuite is running the version of the unwinding code that was built with the local (llvm-)gcc, which doesn't work because nobody has implemented builtin_return_address for that target. So that's one problem. More seriously, the version of the

I''m trying to update records in a table based on data I get back from a form. In the simplest case, the params structure returned from the form is: {"illness"=>{"1"=>{"illness_date"=>"", "qualifier"=>""}}} The controller code works (i.e., updates the first record) when I do the following: params[:illness].each do

...nt, but as I mentioned in the review I was still seeing runtime errors when executing a program compiled with this code. I have since figured out why the program crashes at runtime, but fixing it is going to be a bit tricky. It has to do with some wrinkles in how the Microsoft runtime handles the rethrown exceptions. As the code above is written, the outer catch should handle both the inner catch and its try-block and the outer catch handler should return to a location in the parent function. An ideal numbering of the EH states would look something like this: void test1() { // EH state = -1 t...

...i, i8* bitcast (i32 (...)* >>> @__gxx_personality_v0 to i8*), i32 0) >>> then it doesn't work either: the unwinder observes that there is >>> only a cleanup, and >>> using some special logic (bogus in this case) deduces that the >>> exception will be rethrown >>> after running the cleanup code (and thus the program terminated), so >>> doesn't bother running >>> the cleanup code and directly terminates the program (apparently >>> terminating programs quickly >>> was important to whoever wrote the unwinder,...

...dwrite/tests: Test for superscript/subscript font metrics. Paul Gofman (3): d3dx9: Implement preshader parsing. d3dx9: Implement preshaders disassembly dump. d3dx9: D3DXVec3Transform should support input and output parameter overlap. Piotr Caban (4): msvcrt: Fix i386 rethrown exceptions handling. ieframe: Restore closed IOleClientSite in DoVerb. ieframe: Improve setting different client site in OleObject_SetClientSite. ieframe: Test setting different client site in OleObject_SetClientSite. Qian Hong (1): loader: Fix wld_prctl prototype. Rodrigo...

...duplicated assert.h include. mscoree: Remove duplicated include. Oleksij Rempel (2): shell32: Return empty list instead of NULL. krnl386.exe: Fix drive spec in get_media_id call. Piotr Caban (9): msvcrt: Fixed typo in DEFINE_EXCEPTION_TYPE_INFO macro. msvcrt: Handle rethrown exception in cxx_frame_handler. msvcp90: Added partial basic_ostream<char> implementation. msvcp90: Fix streamoff and streampos definition. msvcp90: Rename sentry_char_{create,destroy} functions. msvcp90: Call correct setstate function in basic_ostream class. msv...