summaryrefslogtreecommitdiff
path: root/libjava/exception.cc
diff options
context:
space:
mode:
authorrth <rth@138bc75d-0d04-0410-961f-82ee72b054a4>2001-04-02 23:26:50 +0000
committerrth <rth@138bc75d-0d04-0410-961f-82ee72b054a4>2001-04-02 23:26:50 +0000
commit0165a03e94dda34ef18da8b9b6dedff6c36c3330 (patch)
treef1574d849578659f7af4af27f0e2fb7b43b07dad /libjava/exception.cc
parent9e2e0ee1809922da015a27c8ba355bc9bb6fb1e5 (diff)
downloadgcc-0165a03e94dda34ef18da8b9b6dedff6c36c3330.tar.gz
* configure.in (GCC_UNWIND_INCLUDE): Assume we're built within
the same tree as gcc. * configure: Rebuilt. * exception.cc (_Jv_Throw): Clarify commentary. git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@41025 138bc75d-0d04-0410-961f-82ee72b054a4
Diffstat (limited to 'libjava/exception.cc')
-rw-r--r--libjava/exception.cc15
1 files changed, 7 insertions, 8 deletions
diff --git a/libjava/exception.cc b/libjava/exception.cc
index 41f7676063e..ff58be11b12 100644
--- a/libjava/exception.cc
+++ b/libjava/exception.cc
@@ -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 ();
}