configure.in (GCC_UNWIND_INCLUDE): Assume we're built within the same tree as gcc.
* configure.in (GCC_UNWIND_INCLUDE): Assume we're built within the same tree as gcc. * configure: Rebuilt. * exception.cc (_Jv_Throw): Clarify commentary. From-SVN: r41025
This commit is contained in:
parent
847abd1f89
commit
212a2676d3
4 changed files with 213 additions and 228 deletions
|
@ -104,14 +104,13 @@ _Jv_Throw (jthrowable value)
|
|||
code = _Unwind_RaiseException (&xh->unwindHeader);
|
||||
#endif
|
||||
|
||||
/* FIXME: If code == _URC_END_OF_STACK, then we reached top of
|
||||
stack without finding a handler for the exception. I seem to
|
||||
recall that Java has specific rules to handle this.
|
||||
|
||||
If code is something else, we encountered some sort of heinous
|
||||
lossage, from which we could not recover. As is the way of such
|
||||
things we'll almost certainly have crashed before now, rather
|
||||
than actually being able to diagnose the problem. */
|
||||
/* If code == _URC_END_OF_STACK, then we reached top of stack without
|
||||
finding a handler for the exception. Since each thread is run in
|
||||
a try/catch, this oughtn't happen. If code is something else, we
|
||||
encountered some sort of heinous lossage from which we could not
|
||||
recover. As is the way of such things, almost certainly we will have
|
||||
crashed before now, rather than actually being able to diagnose the
|
||||
problem. */
|
||||
abort ();
|
||||
}
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue