|
From: Mark W. <ma...@so...> - 2023-04-01 21:58:43
|
https://sourceware.org/git/gitweb.cgi?p=valgrind.git;h=03e36bc36ec9fe9a6ea83e3ad0338480a5a97f6c commit 03e36bc36ec9fe9a6ea83e3ad0338480a5a97f6c Author: Mark Wielaard <ma...@kl...> Date: Sat Apr 1 23:58:14 2023 +0200 Commit access and try branches Diff: --- README_DEVELOPERS | 27 +++++++++++++++++++++++++++ 1 file changed, 27 insertions(+) diff --git a/README_DEVELOPERS b/README_DEVELOPERS index 5b0a1bc6ad..4ed21a561b 100644 --- a/README_DEVELOPERS +++ b/README_DEVELOPERS @@ -80,6 +80,33 @@ compare them on all the performance tests: perl perf/vg_perf --vg=../trunk1 --vg=../trunk2 perf/ +Commit access and try branches +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +To get commit access to the valgrind git repository on sourceware +you will have to ask an existing developer and fill in the following +form: https://sourceware.org/cgi-bin/pdw/ps_form.cgi + +Every developer with commit access can use try branches. Code committed +to a try branch will be build by the buildbot at builder.sourceware.org +https://builder.sourceware.org/buildbot/#/builders?tags=valgrind-try + +If you want to try a commit you can push to a special named try branch +(users/<your-user-name>/try-<topic>) as follows: + + git checkout -b frob + ...hack, hack, hack... OK, looks good to submit + git commit -a -m "Awesome hack" + git push origin frob:users/username/try-frob + +When all builders have build your patch the buildbot will sent you (or +actually the patch author) an email telling you if any builds failed and +references to all the logs. You can also find the logs and the builds here: +https://builder.sourceware.org/buildbot/#/builders?tags=valgrind-try + +Afterwards you can delete the branch again: + + git push origin :users/username/try-frob + Debugging Valgrind with GDB ~~~~~~~~~~~~~~~~~~~~~~~~~~~ To debug the valgrind launcher program (<prefix>/bin/valgrind) just |