- changed title to Flushing buffered port causes non positional custom port flush.
Flushing buffered port causes non positional custom port flush.
Issue #158
resolved
(import (rnrs) (rfc http) (rfc base64)) (define (basic-auth-string user password) (string-append "Basic " (base64-encode-string (string-append user ":" password)))) (define (access) (receive (status header body) (http-get "htaccess.cman.jp" "/sample_go/basic/" :secure #t :authorization (basic-auth-string "guest" "password")) body)) (display (access)) (newline)
Reported by @SaitoAtsushi
Comments (2)
-
reporter -
reporter - changed status to resolved
Using Sg_HasSetPortPosition to check if the given port has set port position on buffered port (Fixes
#158) Dont use stupid macro version of WriteConsole to write ASCII string.→ <<cset bcf102d5d1b5>>
- Log in to comment
The root cause is buffered port flush. It tries to set port position before flush. If the port is custom port and doesn't have set position procedure, then it raises an error. Then raising an error invokes ports flush including the target port, this causes error in error and VM would abort.