diff options
| -rw-r--r-- | gcc/go/gofrontend/MERGE | 2 | ||||
| -rw-r--r-- | libgo/README | 25 |
2 files changed, 26 insertions, 1 deletions
diff --git a/gcc/go/gofrontend/MERGE b/gcc/go/gofrontend/MERGE index 9191273..7c884a9 100644 --- a/gcc/go/gofrontend/MERGE +++ b/gcc/go/gofrontend/MERGE @@ -1,4 +1,4 @@ -859e8ed3d632d9fe43d03fb81f6abefecf5fe3a6 +f813c670deb8e0454c3f64de74bedb5dcedd10b4 The first line of this file holds the git revision number of the last merge done from the gofrontend repository. diff --git a/libgo/README b/libgo/README index d5af7e2..a39d524 100644 --- a/libgo/README +++ b/libgo/README @@ -42,3 +42,28 @@ http://code.google.com/legal/corporate-cla-v1.0.html. If the copyright holder for your code has already completed the agreement in connection with another Google open source project, it does not need to be completed again. + +Debugging +========= + +This describes how to test libgo when built as part of gccgo. + +To test a specific package, cd to the libgo build directory +(TARGET/libgo) and run `make PKG/check`. For example, `make +bytes/check`. + +To see the exact commands that it runs, including how the compiler is +invoked, run `make GOTESTFLAGS=--trace bytes/check`. This will +display the commands if the test fails. If the test passes, the +commands and other output will be visible in a file named +check-testlog in a subdirectory with the name of the package being +checked. In the case of bytes/check, this will create +bytes/check-testlog. + +To leave the test program behind, run `make GOTESTFLAGS=--keep +bytes/check`. That will leave a gotestNNNN/test directory in the +libgo build directory. In that directory you can run +`LD_LIBRARY_PATH=../../.libs ./a.out -test.short` to run the tests. +You can run specific failing tests using a -test.run option. You can +see the tests being run with the -test.v option. You can run the +program under a debugger such as gdb. |