Errors do not result in traces which makes debugging difficult
Bug #533681 reported by
David Rosenbaum
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Boots | Status tracked in Trunk | |||||
Trunk |
Fix Committed
|
High
|
Unassigned |
Bug Description
Errors do not result in traces; this is the desired behavior for normal use but is annoying when debugging. There should be a way (perhaps a debug option) to cause all (or some) errors to result in traces. (This was previously suggested by Clark).
Related branches
Changed in boots: | |
importance: | Undecided → High |
Changed in boots: | |
importance: | High → Medium |
Changed in boots: | |
importance: | Medium → High |
Changed in boots: | |
status: | New → Confirmed |
To post a comment you must log in.
Why did you change the priority of this bug back? I agree with you that this is an important feature, but it is neither core functionality nor critically affecting functionality. Compared with the importance we've assigned other bugs, imho this bug is medium priority.