Add exceptq support
The trap should not occur, even with slow access. Unfortunately, the trap
is not within fm/2 code, so it's hard to analyze without a process dump.
I will be adding exceptq support to fm/2, once I get some in-progress
exceptq rework completed. This will provide enhanced trap logging,
without the need to resort to trap dumps.
Change History
(9)
| Milestone: |
→ Release_3.6
|
| Version: |
→ 3.06
|
| Milestone: |
Release_3.6 → Release_3.7
|
| Version: |
3.06 → 3.07
|
| Owner: |
set to Steven Levine
|
| Milestone: |
Release_3.7 → Release_3.8
|
| Version: |
3.07 → 3.08
|
| Milestone: |
Release_3.8
|
| Version: |
3.08
|
| Milestone: |
→ Release_3.15
|
| Resolution: |
→ fixed
|
| Status: |
assigned → closed
|
This is code complete, unless something shows up during stress testing.