Opened 19 months ago
Last modified 12 months ago
#343 assigned defect
Fixed point overflow by as_who$long with absurd maxusers
| Reported by: | Owned by: | Eric Swenson | |
|---|---|---|---|
| Priority: | minor | Milestone: | MR12.9 |
| Component: | Administration | Version: | MR12.8 |
| Keywords: | Cc: |
Description
Ready
M-> maxu 99999999
admin_: maxu: 99999999 (9999999 normal users)
Ready
M-> who -lg
Error: Fixed point overflow by as_who$long|4006
(>system_library_tools>bound_admin_tools_|4006)
(actually by support procedure pl1_signal_$pl1_signal_from_ops_|776
(>sl1>bound_library_1_|13712)) (fixedoverflow condition)
who: Execution aborted by error signal.
Ready
There are two problems here. maxu should reject absurd maxusers values, but who should not crash in any case.
Note:
See TracTickets
for help on using tickets.
The FPO error is only happening because the code in admin_ that sets maxu allows a value greater than 131071 to be stored in a fixed bin (17) value. Fixing that problem will prevent the FPO error in as_who$long.