* add -json flag when running tests on TeamCity

* introduce TeamCity builds

* restore gdbserial constants for 386

Otherwise compilation fails.

* skip TestAttachRequest on Windows as it never finishes

* run tests on 1.16beta1

* Add support for evaluateName for variables

* More evaluateName logic tweaks and tests

* Make DeepSource happy
Co-authored-by: NPolina Sokolova <polinasok@users.noreply.github.com>

Co-authored-by: NPolina Sokolova <polinasok@users.noreply.github.com>

* Use address, not index to differentiate compound map keys

* Clean up calls to expectVarRegex
Co-authored-by: NPolina Sokolova <polinasok@users.noreply.github.com>

Co-authored-by: NPolina Sokolova <polinasok@users.noreply.github.com>

Fixes #637

add example for multiple  --build-flags

add example description to --build-flags

* proc: misc test fixes for Go 1.16

* proc: fix cgo stacktraces in Go 1.16 with simplified C -> Go call path

* dwarf/line: make dwarf/line correct when '\\' are used

Our code depends heavily on paths being '/' separated because go always
produced '/' separated file paths. The call to filepath.Join will
normalize the paths, on windows, to always be '\\' separated, which
violated our assumptions.

This didn't use to be a problem because the codepath that calls
filepath.Join was never exercised by executable files produced by Go,
but Go 1.16 started producing debug_line sections that use the
directory table with https://go-review.googlesource.com/c/go/+/263017/.

Fix this to always use path.Join after making sure, on windows, to
always normalize paths to use '/' as a separator. Replace the use of
filepath.IsAbs with an operating system independent version.

* goversion: bump supported Go version

The goroutines command can take a long time to complete if there are
many goroutines, add the possibility to terminate it early by pressing
ctrl-C.

Before go1.11 waitreason field was a string, not an int. Return 0
waitreason for old go versions.

Should fix #2282

* Added support for reading darwin/arm64 using gdbserver

* Trying to fix test failures

* Addressing review comments

If a thread exits while we are looking at it just treat it as if the
status had reported it as exited instead of doing something special.
Fixes flakiness in TestIssue387.

* Support local attach

* Undo loopprog change

* Remove test check for system-specific error message

* Skip attach tests on freebasd
Co-authored-by: NPolina Sokolova <polinasok@users.noreply.github.com>

Waits for the target process to have received the kill signal in
native.nativeProcess.kill. Fixes an infrequent error in TestKill.

Sometimes it makes debuggee to hang.

Should fix #2244

Fix bug in DAP test: TestEvaluateCallRequest.
In Go 1.15 the call injection will be executed on a different goroutine
from the goroutine where it was started on to avoid confusing the
garbage collector, the test must be aware of this fact and use the
goroutine ID from the stopped response instead of assuming 1 is the
currently selected goroutine.

Disables TestAttachDetach when running in Github Actions.

Disable some coredump tests when running in Github Actions (core size
limits?).

Change 24ec1754 (use CPUID to determine maximum size of XSAVE area)
broke the linux/386 backend, this commit fixes it.

Do not call detach if the target is no longer valid.

Fixes #2259
Co-authored-by: Na <a@kra>

the maximum size of the Xsave area was previously hardcoded but the
CPUID instruction can be used to determine its maximum size.

This adds the WaitSince and WaitReason fields for the goroutines to allow the users to easily understand why a goroutine is waiting.

The comment on the advanceRegs() method was referencing several
nonexistent fields. This patch fixes that, and improves the comment to
reference the peculiar interaction between the method and it.regs.

Fixes #852
Co-authored-by: Na <a@kra>

evalFunctionCall needs to remove the breakpoint from the current thread
after starting the function call injection, otherwise Continue will
think that the thread is stopped at a breakpoint and return to the user
instead of continuing the call injection.

Adds a flag that distinguishes the return values of an injected
function call from the return values of a function call executed by the
target program.

Thank you to: @polinasok, @aurkenb, @pohzipohzi, @chainhelen,
@hitzhangjie, @eliben, @suzmue, @andreimatei, @aaronsky.

Fix some stale comments and add some comments that I would have found
useful.

This is needed to fix the problem we have with 1.15.4+ after the
backport is applied to it. The DWARF standard isn't clear on what
should happen with the end_of_sequence opcode but this is consistent
with debug/dwarf.LineReader as well as gdb.

Co-authored-by: NPolina Sokolova <polinasok@users.noreply.github.com>

* service/dap: expand goroutine info in threads response

* Fix checks

* Make DeepSource happy
Co-authored-by: NPolina Sokolova <polinasok@users.noreply.github.com>

Co-authored-by: NPolina Sokolova <polinasok@users.noreply.github.com>

* Use the active xcode-select path instead of a hardcoded Xcode path

* Refactored exec.Command to invoke Output instead of running with a custom buffer for stdout

Addresses review comment by @derekparker

Change FindLocation to apply substitute path rules to location
expressions. Changes terminal to always print paths after applying
substitutions.

Implements #2203

1. Forward stdin/stdout/stderr to the target process when in foreground
   mode instead of always forwarding the current tty (issue #1964)
2. When redirecting a file descriptor make sure to also specify
   something for all three otherwise debugserver will misbehave (either
   exit on launch or run but giving the target process a closed file
   descriptor).

Fixes #1964

See https://github.com/golang/go/issues/42484

This patch adds some comments around RequestManualStop().