You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Does this issue reproduce with the latest release?
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
set GOARCH=amd64
set GOBIN=E:\goPrjs\bin
set GOCACHE=C:\Users\yuguoxiu\AppData\Local\go-build
set GOEXE=.exe
set GOFLAGS=
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOOS=windows
set GOPATH=E:\goPrjs
set GOPROXY=
set GORACE=
set GOROOT=c:\go
set GOTMPDIR=
set GOTOOLDIR=c:\go\pkg\tool\windows_amd64
set GCCGO=gccgo
set CC=gcc
set CXX=g++
set CGO_ENABLED=1
set GOMOD=
set CGO_CFLAGS=-g -O2
set CGO_CPPFLAGS=
set CGO_CXXFLAGS=-g -O2
set CGO_FFLAGS=-g -O2
set CGO_LDFLAGS=-g -O2
set PKG_CONFIG=pkg-config
set GOGCCFLAGS=-m64 -mthreads -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=C:\Users\yuguoxiu\AppData\Local\Temp\go-build010222054=/tmp/go-build -gno-record-gcc-switches
What did you do?
I cross-compiled as
GOOS=linux GOARCH=amd64 go build
and run in linux, then the net/smtp/smtp.go func auth() throw error as "535 Error: terminal limit"
I want to local where the error message was throwed, but I search the golang source code without get the "terminal limit "
What did you expect to see?
What did you see instead?
The text was updated successfully, but these errors were encountered:
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
I cross-compiled as
GOOS=linux GOARCH=amd64 go build
and run in linux, then the
net/smtp/smtp.go func auth()
throw error as "535 Error: terminal limit"I want to local where the error message was throwed, but I search the golang source code without get the "terminal limit "
What did you expect to see?
What did you see instead?
The text was updated successfully, but these errors were encountered: