clj-1102-improve-empty-stack-trace-handling-v1.txt
[CLJ-1102] Better handling of exceptions with empty stack traces Created: 04/Nov/12 Updated: 30/Nov/12 |
|
| Status: | Open |
| Project: | Clojure |
| Component/s: | None |
| Affects Version/s: | Release 1.5 |
| Fix Version/s: | None |
| Type: | Defect | Priority: | Minor |
| Reporter: | Andy Fingerhut | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Attachments: |
clj-1102-improve-empty-stack-trace-handling-v1.txt
|
| Patch: | Code |
| Approval: | Vetted |
| Description |
|
I don't know what I did to cause some exceptions to be thrown while running Clojure tests that return a length 0 array from (.getStackTrace throwable), but according to the Java docs this is legal. I searched all places in the Clojure code that call .getStackTrace and found two that don't handle this correctly, one of which causes an ArrayOutOfBoundsException (that is the one I found during my testing). |
| Comments |
| Comment by Andy Fingerhut [ 04/Nov/12 5:07 PM ] |
|
clj-1102-improve-empty-stack-trace-handling-v1.txt dated Nov 4 2012 improves the handling of .getStackTrace returning a length 0 array in two places. I checked all other places .getStackTrace was called and they seem to already handle this case gracefully. |
| Comment by Timothy Baldridge [ 30/Nov/12 2:57 PM ] |
|
Vetting. |