{"push_id":1345329544,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"4dac951e11030b43b17f52df8bdfa7432e4bf73c","before":"4a2f4826907de97b089295000a67d2497aa94c99","commits":[{"sha":"4dac951e11030b43b17f52df8bdfa7432e4bf73c","author":{"name":"Luis Machado","email":"646c9ef7e189403d5d97be0f9e9ce3403963c527@codesourcery.com"},"message":"Fixup gdb.python/py-value.exp for bare-metal aarch64-elf\n\nI noticed that testing aarch64-elf gdb with a physical board\nran into issues with gdb.python/py-value.exp. Further investigation showed\nthat we were actually trying to dereference a NULL pointer (argv) when trying\nto access argv[0].\n\nBeing bare-metal, argv is not guaranteed to be valid. So we need to make sure\nargv is sane before accessing argv[0].\n\nThe following patch fixes up the test program to check for a NULL argv and also\nimproves the testcase a bit so it doesn't have to work with a hardcoded argc\nvalue.\n\nRegression-tested on x86-64 Ubuntu 16.04.\n\ngdb/testsuite/ChangeLog:\n\n2016-10-12  Luis Machado  <lgustavo@codesourcery.com>\n\n\t* gdb.python/py-value.c (main): Check if argv is NULL before using it.\n\t* gdb.python/py-value.exp (test_value_in_inferior): Don't use hardcoded\n\targc values.\n\tAdd 1 to argc so we guarantee distinct initial/modified argc values.","distinct":true,"url":"https://api.github.com/repos/mickael-guene/binutils/commits/4dac951e11030b43b17f52df8bdfa7432e4bf73c"}]}
{"actor":{"display_login":"mickael-guene"}}