Stack trace details lost when re-raising exception
Bug #415420 reported by
Iain Lowe
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| VMBuilder |
Fix Released
|
Undecided
|
Iain Lowe | ||
Bug Description
During the core creation of a new VM (in VMBuilder/vm.py) any raised exception is first caught and then re-raised. Doing this loses the stack trace information from the exception and "resets" the trace to begin where the exception is re-raised.
Related branches
lp:~ilowe/vmbuilder/lp415420
- Soren Hansen: Approve
- Diff: None lines
| Changed in vmbuilder: | |
| assignee: | nobody → Iain Lowe (ilowe) |
| status: | New → Fix Committed |
| Changed in vmbuilder: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
