decode-timeout wants a REAL, but explodes if given more than '(unsigned-byte 62)

Bug #1727789 reported by Ethan H. Schwartz
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
SBCL
Fix Released
Low
Unassigned

Bug Description

Trivial to reproduce:

(sb-sys:decode-timeout 9223372036854774807) =>
#<TYPE-ERROR expected-type: (UNSIGNED-BYTE 62) datum: 9223372036854774807000>

This is especially annoying if you accidentally give a huge value to the various sb-thread primitives' timeout argument.

This is from SBCL 1.4.0.220.

Jan Moringen (scymtym)
Changed in sbcl:
assignee: nobody → Jan Moringen (scymtym)
importance: Undecided → Low
status: New → Triaged
Revision history for this message
Attila Lendvai (attila-lendvai) wrote :
Jan Moringen (scymtym)
Changed in sbcl:
status: Triaged → Fix Committed
Jan Moringen (scymtym)
Changed in sbcl:
assignee: Jan Moringen (scymtym) → nobody
Changed in sbcl:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.