go/misc/cgo/errors/testdata/err1.go

// Copyright 2013 The Go Authors. All rights reserved.
// Use of this source code is governed by a BSD-style
// license that can be found in the LICENSE file.

package main

/*
#cgo LDFLAGS: -L/nonexist

void test() {
	xxx;		// ERROR HERE
}
*/
import "C"

func main() {
	C.test()
}
all: make copyright headers consistent with one space after period Follows suit with https://go-review.googlesource.com/#/c/20111. Generated by running $ grep -R 'Go Authors. All' * \| cut -d":" -f1 \| while read F;do perl -pi -e 's/Go Authors. All/Go Authors. All/g' $F;done The code in cmd/internal/unvendor wasn't changed. Fixes #15213 Change-Id: I4f235cee0a62ec435f9e8540a1ec08ae03b1a75f Reviewed-on: https://go-review.googlesource.com/21819 Reviewed-by: Ian Lance Taylor <iant@golang.org> Run-TryBot: Ian Lance Taylor <iant@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> 2016-04-10 15:32:26 -06:00			`// Copyright 2013 The Go Authors. All rights reserved.`
cmd/cgo: fix line number in an error message Fixes #6563. R=golang-dev, iant CC=golang-dev https://golang.org/cl/14870046 2013-10-18 14:52:44 -06:00			`// Use of this source code is governed by a BSD-style`
			`// license that can be found in the LICENSE file.`

cmd/cgo: don't let #cgo directives mess up line numbering Fixes #5272. R=golang-dev, r CC=golang-dev https://golang.org/cl/13498046 2013-09-03 22:15:15 -06:00			`package main`

			`/*`
cmd/go: accept only limited compiler and linker flags in #cgo directives Both gcc and clang accept an option -fplugin=code.so to load a plugin from the ELF shared object file code.so. Obviously that plugin can then do anything it wants during the build. This is contrary to the goal of "go get" never running untrusted code during the build. (What happens if you choose to run the result of the build is your responsibility.) Disallow this behavior by only allowing a small set of known command-line flags in #cgo CFLAGS directives (and #cgo LDFLAGS, etc). The new restrictions can be adjusted by the environment variables CGO_CFLAGS_ALLOW, CGO_CFLAGS_DISALLOW, and so on. See the documentation. In addition to excluding cgo-defined flags, we also have to make sure that when we pass file names on the command line, they don't look like flags. So we now refuse to build packages containing suspicious file names like -x.go. A wrinkle in all this is that GNU binutils uniformly accept @foo on the command line to mean "if the file foo exists, then substitute its contents for @foo in the command line". So we must also reject @x.go, flags and flag arguments beginning with @, and so on. Fixes #23672, CVE-2018-6574. Change-Id: I59e7c1355155c335a5c5ae0d2cf8fa7aa313940a Reviewed-on: https://team-review.git.corp.google.com/209949 Reviewed-by: Ian Lance Taylor <iant@google.com> 2018-02-01 12:07:21 -07:00			`#cgo LDFLAGS: -L/nonexist`
cmd/cgo: don't let #cgo directives mess up line numbering Fixes #5272. R=golang-dev, r CC=golang-dev https://golang.org/cl/13498046 2013-09-03 22:15:15 -06:00
			`void test() {`
cmd/cgo: fix line number in an error message Fixes #6563. R=golang-dev, iant CC=golang-dev https://golang.org/cl/14870046 2013-10-18 14:52:44 -06:00			`xxx; // ERROR HERE`
cmd/cgo: don't let #cgo directives mess up line numbering Fixes #5272. R=golang-dev, r CC=golang-dev https://golang.org/cl/13498046 2013-09-03 22:15:15 -06:00			`}`
			`*/`
			`import "C"`

			`func main() {`
			`C.test()`
			`}`