)]}' { "log": [ { "commit": "95451ea43a7e2e4aa806ee7405e9167b2ee653c1", "tree": "746dbce5f6641774f833574e6fd7bb0dbc77d055", "parents": [ "e0fe0e3abde305a34de82134b7d8a7fa153d1897" ], "author": { "name": "Alan Modra", "email": "amodra@gmail.com", "time": "Sat Jun 13 10:27:22 2026 +0930" }, "committer": { "name": "Alan Modra", "email": "amodra@gmail.com", "time": "Sat Jun 13 14:23:42 2026 +0930" }, "message": "oss-fuzz: vms-alpha segfault in image_write_section\n\nYet another case where a fuzzed object file triggers a crash in the\nvms-alpha support.\n\n\t* vms-alpha.c (image_write_section): Don\u0027t segfault on NULL\n\timage_section.\n" }, { "commit": "e0fe0e3abde305a34de82134b7d8a7fa153d1897", "tree": "7a4d237d8d872bbc03fd76eac414c417bd56fd17", "parents": [ "085ef1cd85c81d2ce82ed165436daba7780458c1" ], "author": { "name": "Alan Modra", "email": "amodra@gmail.com", "time": "Fri Jun 12 23:23:48 2026 +0930" }, "committer": { "name": "Alan Modra", "email": "amodra@gmail.com", "time": "Sat Jun 13 14:20:45 2026 +0930" }, "message": "check bfd_alloc/bfd_malloc return in elflink.c\n\nAdd checks in a couple of places for a non-NULL return. While we\u0027re\nat it, don\u0027t use sprintf to concatenate two strings.\n\n\t* elflink.c (bfd_elf_link_record_dynamic_symbol): Check than\n\tbfd_malloc returns non-NULL.\n\t(get_dynamic_reloc_section_name): Similarly check bfd_alloc.\n\tReplace sprintf with two memcpys. Remove old_name NULL check.\n" }, { "commit": "085ef1cd85c81d2ce82ed165436daba7780458c1", "tree": "1eddffa69d081d444333f33424ddc9af47efe7cf", "parents": [ "2b675b263dfd5c780b8b77ae6b97543a6fb42d1c" ], "author": { "name": "Tom Tromey", "email": "tromey@adacore.com", "time": "Fri May 29 13:48:37 2026 -0600" }, "committer": { "name": "Tom Tromey", "email": "tromey@adacore.com", "time": "Fri Jun 12 09:23:38 2026 -0600" }, "message": "Add tests for Ada \"in\" operator\n\nCoverage testing showed that there were no existing tests of the Ada\n\"in\" operator. This patch adds tests for this.\n\nBug: https://sourceware.org/bugzilla/show_bug.cgi?id\u003d34041\n\n\n\n" }, { "commit": "2b675b263dfd5c780b8b77ae6b97543a6fb42d1c", "tree": "6b8d9baf1dd22b0767365c02c0c9d2270c81f120", "parents": [ "22143ca474bb7154a5c9b4aa20a3aba256c0137a" ], "author": { "name": "Pedro Alves", "email": "pedro@palves.net", "time": "Wed May 20 11:22:56 2026 +0100" }, "committer": { "name": "Pedro Alves", "email": "pedro@palves.net", "time": "Fri Jun 12 14:57:21 2026 +0100" }, "message": "Adjust gdb.python/py-events.exp for Cygwin/MinGW, \"info proc\" \u003d\u003e \"inferior\"\n\nThe testcase is using \"info proc\" to extract the inferior\u0027s process\nID. But \"info proc\" does not exist on all targets, including Windows.\nSwitch to using the get_inferior_pid routine from lib/gdb.exp, which\nuses \"inferior\" instead.\n\nWith this fixed, the testcase passes cleanly on Cygwin. I haven\u0027t\ntested on MinGW (I\u0027m not set up for Python testing there currently),\nbut at least (since the previous patches) the test should be able to\ncompile \u0026 run there now.\n\nAlso tested on x86_64-unknown-linux-gnu.\n\nChange-Id: If6ff482ceb011d9afe5ed40ef7e4e2f2cad8cae8\n" }, { "commit": "22143ca474bb7154a5c9b4aa20a3aba256c0137a", "tree": "df10e1c1269d20862ea56dc04f9b435bf7de841d", "parents": [ "ab20bdf8efc3e8607e6aa68464901bb109b544db" ], "author": { "name": "Pedro Alves", "email": "pedro@palves.net", "time": "Wed May 20 11:22:56 2026 +0100" }, "committer": { "name": "Pedro Alves", "email": "pedro@palves.net", "time": "Fri Jun 12 14:57:21 2026 +0100" }, "message": "Adjust gdb.python/py-events.exp for Cygwin/MinGW, no fork\n\nThe gdb.python/py-events.exp testcase currently uses fork, and relies\non \"set detach-on-fork off\".\n\nCygwin does support the fork syscall, but GDB can\u0027t follow forks\nthere, so \"detach-on-fork off\" has no effect. And also, there is no\nfork on native Windows, which makes the testcase unusable on MinGW\ncurrently.\n\nI don\u0027t see any reason the testcase needs to use fork or multiple\ninferiors. We can replace what those parts were testing by more\nfocused tests:\n\n - The clear_objfiles event was tested via following a fork. Instead,\n test a more directed \"file\" command.\n\n - Two-inferior quit was being used to test that gdb.ExitedEvent has\n no \"exit_code\". Quitting while an inferior is being debugged makes\n GDB kill the inferior. What\u0027s really being tested is the kill\n path, so write an explicit (single-inferior) kill test.\n\nTested on x86_64-unknown-linux-gnu.\n\nChange-Id: I21ee8af7b52653c6fdff9b4c1596cdde3cfe751a\n" }, { "commit": "ab20bdf8efc3e8607e6aa68464901bb109b544db", "tree": "dfdb37d887b533520888f38f1440148e73d5fb0e", "parents": [ "613b8ee3f8e2f697445fed3ee2c2748ba0089eea" ], "author": { "name": "Pedro Alves", "email": "pedro@palves.net", "time": "Wed May 20 11:22:56 2026 +0100" }, "committer": { "name": "Pedro Alves", "email": "pedro@palves.net", "time": "Fri Jun 12 14:57:21 2026 +0100" }, "message": "Adjust gdb.python/py-events.exp for Cygwin/MinGW, thread IDs\n\nThis commit fixes a couple issues in gdb.python/py-events.exp for\nCygwin and MinGW:\n\n1) - GDB prints Windows thread IDs in hex:\n\n (gdb) thread\n [Current thread is 1 (Thread 9528.0xa9c)]\n\nThe current code assumes decimal, so we only (incorrectly) extract the\n\"0\" after the dot.\n\n2) - Thread and process ID number spaces are different.\n\nThe current code assumes that the extracted thread ID is the same\nnumber as the extracted process ID, which is not true on Windows.\n\nAlso tested on x86_64-unknown-linux-gnu.\n\nChange-Id: Iebcc07c3ad0845b548334c0d5177b3ab9e9350cf\n" }, { "commit": "613b8ee3f8e2f697445fed3ee2c2748ba0089eea", "tree": "ae286336d52c5365911d4c5c3b1f3bddf1033e3b", "parents": [ "4fce4baa748ff16ff427b5b5f010e02cb80f48d1" ], "author": { "name": "Pedro Alves", "email": "pedro@palves.net", "time": "Wed May 20 11:45:57 2026 +0100" }, "committer": { "name": "Pedro Alves", "email": "pedro@palves.net", "time": "Fri Jun 12 14:57:21 2026 +0100" }, "message": "Windows gdb+gdbserver: Decode Cygwin ExitProcess codes\n\nOn native Cygwin, GDB misreports the inferior\u0027s exit reason in several\ncommon cases, resulting in several gdb.base/exitsignal.exp failures:\n\n $ grep FAIL gdb.sum\n FAIL: gdb.base/exitsignal.exp: how\u003drun: signal: program terminated with SIGSEGV (the program exited)\n FAIL: gdb.base/exitsignal.exp: how\u003drun: signal: $_exitsignal is 11 (SIGSEGV) after SIGSEGV.\n FAIL: gdb.base/exitsignal.exp: how\u003drun: signal: $_exitcode is still void after SIGSEGV\n FAIL: gdb.base/exitsignal.exp: how\u003drun: signal: $_exitsignal is 11 (SIGSEGV) after restarting the inferior\n FAIL: gdb.base/exitsignal.exp: how\u003drun: signal: $_exitcode is still void after restarting the inferior\n FAIL: gdb.base/exitsignal.exp: how\u003drun: normal: continue to exit\n FAIL: gdb.base/exitsignal.exp: how\u003drun: normal: $_exitcode is one after normal inferior is executed\n FAIL: gdb.base/exitsignal.exp: how\u003drun: normal: $_exitsignal is still void after normal inferior is executed\n FAIL: gdb.base/exitsignal.exp: how\u003dattach: normal: continue to exit (the program exited)\n FAIL: gdb.base/exitsignal.exp: how\u003dattach: normal: $_exitcode is one after normal inferior is executed\n\nFor example, from gdb.log, the normal exit case:\n\n ...\n [Thread 14300.0x4214 (id 1) exited with code 1]\n [Thread 14300.0x1b1c (id 4) exited with code 1]\n [Thread 14300.0x1e2c (id 2) exited with code 1]\n\n Program terminated with signal SIGHUP, Hangup.\n The program no longer exists.\n (gdb) FAIL: gdb.base/exitsignal.exp: how\u003drun: normal: continue to exit\n\nThe program in fact exited normally with code 1. SIGHUP happens to be\nsignal 1, and GDB picked the wrong interpretation.\n\nSimilarly, for the signal termination case:\n\n ...\n continue\n Continuing.\n [Thread 4600.0x3104 (id 4) exited with code 2816]\n [Thread 4600.0x2bcc (id 3) exited with code 2816]\n [Thread 4600.0x2f44 (id 1) exited with code 2816]\n [Inferior 1 (process 4600) exited with code 05400]\n (gdb) FAIL: gdb.base/exitsignal.exp: how\u003drun: signal: program terminated with SIGSEGV (the program exited)\n\nHere the inferior died with SIGSEGV, but GDB reported exit decimal\n2816 / octal 05400 / hex 0x0B00, which is SIGSEGV swapped into the\nhigh byte of a waitpid exit status.\n\nThe problem is that Cygwin waitpid exit status and Windows exit codes\ndo not have the same encoding, and GDB \u0026 GDBserver do not know about\nthis.\n\nThis commit fixes it. It adds a Cygwin-specific branch to the code\nthat determines the terminating signal and status of a program. The\nbranch for native Windows/MinGW GDB is left intact, no behavior change\nthere.\n\nThe way to decode the exit codes is a little bit tricky, see detailed\ncomments added by the patch. To exercise the \"raw NTSTATUS error\ncode\" path in windows_process_info::exit_process_to_target_status,\ngdb.base/exitsignal.exp is extended to debug a native Windows program\nthat crashes with a segfault (STATUS_ACCESS_VIOLATION).\n\nWith this, gdb.base/exitsignal.exp passes cleanly on Cygwin.\n\nReviewed-By: Eli Zaretskii \u003celiz@gnu.org\u003e\nChange-Id: Icaebcc234b71927915c996fd120884604441415b\n" }, { "commit": "4fce4baa748ff16ff427b5b5f010e02cb80f48d1", "tree": "134dc170396c9b40de39b1cedb54d79638f809bd", "parents": [ "c04f1f54f6cb17dd23fe183ca748271c10475c03" ], "author": { "name": "Pedro Alves", "email": "pedro@palves.net", "time": "Wed May 20 11:45:57 2026 +0100" }, "committer": { "name": "Pedro Alves", "email": "pedro@palves.net", "time": "Fri Jun 12 14:57:21 2026 +0100" }, "message": "Windows gdb+gdbserver: Share exit status logic\n\nMove the exit status logic added by commit 559e7e5056 (\"Improve\nprocess exit status macros on MinGW\") from both GDB and GDBserver to a\nshared routine used by both.\n\nThe next patch extends this routine with Cygwin-specific decoding.\n\nChange-Id: I4bf08c6beff0d1688064a81d49bbdd615643735e\n" }, { "commit": "c04f1f54f6cb17dd23fe183ca748271c10475c03", "tree": "4f7c805857d55915a277a20156adedfd3cbe2e40", "parents": [ "d02f36ae6ad1c7de236429d7a2036e5614e20cbf" ], "author": { "name": "Pedro Alves", "email": "pedro@palves.net", "time": "Sat May 23 03:08:31 2026 +0100" }, "committer": { "name": "Pedro Alves", "email": "pedro@palves.net", "time": "Fri Jun 12 14:57:21 2026 +0100" }, "message": "gdb/testsuite: Add mechanism to compile Windows native programs on Cygwin\n\nThis adds a new \"win32\" option to gdb_compile that lets us compile\nnative Windows programs when testing Cygwin. Will be used in a\nfollowing patch.\n\nThe testsuite tries to find the compiler to use automatically. You\ncan also explicitly set it with WIN32_CC_FOR_TARGET.\n\nChange-Id: I86e954494cf7f88164cdf1c9127be46d5437986f\n" }, { "commit": "d02f36ae6ad1c7de236429d7a2036e5614e20cbf", "tree": "eeac4719ba38d05189ff9d9261b879971a512a58", "parents": [ "b8adb91d42438a861ca0f014a73733b1ebda30af" ], "author": { "name": "Pedro Alves", "email": "pedro@palves.net", "time": "Sat May 23 02:01:12 2026 +0100" }, "committer": { "name": "Pedro Alves", "email": "pedro@palves.net", "time": "Fri Jun 12 14:57:21 2026 +0100" }, "message": "gdb.base/exitsignal.exp: Test attaching too\n\nOn some targets, like Cygwin (see the following commit), extracting\nthe exit code works differently depending on whether the inferior was\nrun by GDB, or GDB attached to an existing process. Extend\ngdb.base/exitsignal.exp to test both scenarios.\n\nNote: We add a wait_for_gdb sleep loop to segv.c and normal.c so the\nattach path can synchronize with GDB before the inferior runs. For\nsimplicity, the run path pokes the same variable from setup, so\nbehavior there is unchanged.\n\nThe testcase passes cleanly on Linux, native and gdbserver, and on\nMinGW too. Cygwin still requires more fixes.\n\nChange-Id: I9908aef0cea3eaec8134f05e347702baf753d10c\n" }, { "commit": "b8adb91d42438a861ca0f014a73733b1ebda30af", "tree": "3093e4fc92867144c5c5a48cf5b1d3133211bb8b", "parents": [ "2949fd1dd2969cb54177c8cbb60dff9224d89259" ], "author": { "name": "Pedro Alves", "email": "pedro@palves.net", "time": "Sat May 23 02:01:12 2026 +0100" }, "committer": { "name": "Pedro Alves", "email": "pedro@palves.net", "time": "Fri Jun 12 14:57:21 2026 +0100" }, "message": "gdb.base/exitsignal.exp: Exit with non-zero\n\ngdb.base/exitsignal.exp currently tests exiting with exit code 0.\nBut, testing for 0 is typically more \"dangerous\" in the sense that\nit\u0027s easy for some bug in GDB or the target backend to fail to extract\nthe exit code and return 0. Make it test exit code 1 instead.\n\ngdb.base/coredump-filter-build-id.exp currently reuses normal.c. It\ncould still use it with this patch, but it seems better to me to\nremove the coupling. Simply add a new .c file for that testcase,\nwhich still returns 0.\n\nChange-Id: I49ccfdbbe4be4445172476e7dd4e06142c8a672e\n" }, { "commit": "2949fd1dd2969cb54177c8cbb60dff9224d89259", "tree": "c2378606230c2e5733cdcf02e3f4b62609ef0cb7", "parents": [ "addf54463d8763fe254049aabf7ed131875d8ffb" ], "author": { "name": "Pedro Alves", "email": "pedro@palves.net", "time": "Sat May 23 02:01:12 2026 +0100" }, "committer": { "name": "Pedro Alves", "email": "pedro@palves.net", "time": "Fri Jun 12 14:57:21 2026 +0100" }, "message": "Adjust gdb.base/exitsignal.exp for MinGW, separate program names\n\nCurrently, gdb.base/exitsignal.exp on MinGW skips half the tests, like\nso:\n\n # of expected passes 13\n # of untested testcases 1\n\n... because the testcase actually compiles two programs, but the\nsecond program is compiled using the same executable name as the\nfirst, at a time when gdb still has the first executable open,\nresulting in:\n\n .../x86_64-w64-mingw32/bin/ld.exe: cannot open output file C:/.../gdb.base/exitsignal/exitsignal.exe: Permission denied\n\nThe use of standard_testfile in the middle of a testcase is a bit\nsurprising. Fix this by moving the second compilation to the top, and\ngive each executable its own name.\n\nMove the bulk of test code to two procedures, one for testing exiting\nwith signal, another for testing normal exit.\n\nWith this, gdb.base/exitsignal.exp passes cleanly on\nx86_64-w64-mingw32.\n\nChange-Id: I9a1af298b0e4f62f38b5c4b14787d7e40a2b5e2c\n" }, { "commit": "addf54463d8763fe254049aabf7ed131875d8ffb", "tree": "f7d57be7c90d863309c0f9a682bd5c9953e45712", "parents": [ "2bbd3cb2289792e8093eec3594b96795df0fc1d4" ], "author": { "name": "Pedro Alves", "email": "pedro@palves.net", "time": "Sat May 23 03:08:31 2026 +0100" }, "committer": { "name": "Pedro Alves", "email": "pedro@palves.net", "time": "Fri Jun 12 14:57:21 2026 +0100" }, "message": "Adjust gdb.base/exitsignal.exp for MinGW, second-chance SIGSEGV\n\nOn native Windows a segmentation fault is delivered as a SEH\nexception, so GDB stops twice: once for the first-chance exception,\nand -- if no SEH handler in the inferior catches it -- again for the\nsecond-chance exception, after which the process dies. The testcase\ncurrently continues only once, resulting in:\n\n ...\n continue\n Continuing.\n\n Thread 1 received signal SIGSEGV, Segmentation fault.\n 0x00007ff765ac1469 in main (argc\u003d1, argv\u003d0x9f2640) at C:/rocgdb/src.cascais-rsync/gdb/testsuite/gdb.base/segv.c:24\n 24 *(volatile int *) 0;\n (gdb) PASS: gdb.base/exitsignal.exp: trigger SIGSEGV\n continue\n Continuing.\n\n Thread 1 received signal SIGSEGV, Segmentation fault.\n 0x00007ff765ac1469 in main (argc\u003d1, argv\u003d0x9f2640) at C:/rocgdb/src.cascais-rsync/gdb/testsuite/gdb.base/segv.c:24\n 24 *(volatile int *) 0;\n (gdb) FAIL: gdb.base/exitsignal.exp: program terminated with SIGSEGV\n ...\n\nAdd a second continue on MinGW to step past the second-chance stop.\n\nWith this, gdb.base/exitsignal.exp passes cleanly on MinGW:\n\n -FAIL: gdb.base/exitsignal.exp: program terminated with SIGSEGV\n +PASS: gdb.base/exitsignal.exp: trigger SIGSEGV, second-chance\n +PASS: gdb.base/exitsignal.exp: program terminated with SIGSEGV\n\nChange-Id: Ibda1540a602b62c26a5b218d930402eccc3ba98f\n" }, { "commit": "2bbd3cb2289792e8093eec3594b96795df0fc1d4", "tree": "368db39c4809bda64f31bf79c44672a98812e487", "parents": [ "f67ddc1be6e447b62c970e372cb6459270a47f53" ], "author": { "name": "Pedro Alves", "email": "pedro@palves.net", "time": "Sat May 23 03:08:31 2026 +0100" }, "committer": { "name": "Pedro Alves", "email": "pedro@palves.net", "time": "Fri Jun 12 14:57:11 2026 +0100" }, "message": "Adjust gdb.base/exitsignal.exp for MinGW, trigger fault\n\ngdb.base/segv.c uses raise(SIGSEGV) to generate a SIGSEGV. On native\nWindows that does not generate an EXCEPTION_ACCESS_VIOLATION; raise is\na pure userspace construct: it dispatches to the registered SIGSEGV\nhandler if there is one, otherwise calls abort. GDB therefore never\nsees an exception to intercept. E.g.:\n\n ...\n continue\n Continuing.\n [Thread 1908.0x3308 (id 2) exited with code 3]\n [Inferior 1 (process 1908) exited with code 03]\n (gdb) FAIL: gdb.base/exitsignal.exp: trigger SIGSEGV (the program exited)\n continue\n The program is not being run.\n ...\n\nReplace the raise with a real null dereference so the kernel actually\nraises an access violation.\n\nNote: I confirmed no other tests use segv.c. segv.c and normal.c are\nboth \"owned\" by gdb.base/exitsignal.exp.\n\nChange-Id: Ib54d9e6998cf9bfc18dcb5e76d31a9deb0458da4\n" }, { "commit": "f67ddc1be6e447b62c970e372cb6459270a47f53", "tree": "6ac5cae6efd1424504b9d190c76aab4663ed5635", "parents": [ "9e6e6a2272c78ab8e975692427c641609c0b4573" ], "author": { "name": "Lancelot SIX", "email": "lancelot.six@amd.com", "time": "Tue Apr 16 09:26:36 2024 +0100" }, "committer": { "name": "Pedro Alves", "email": "pedro@palves.net", "time": "Fri Jun 12 14:36:48 2026 +0100" }, "message": "gdb/amd-dbgapi-target: Update xfer_partial to always use dbgapi\n\nOn the Windows platform, the entire \"global\" address space is not\nmapped in the inferior memory. For such configuration, part of the\nglobal address space lives in GPU memory, and can only be accessed via\nrocm-dbgapi.\n\nThis patch updates amd_dbgapi_target::xfer_partial so it always calls\ninto amd-dbgapi to access the global address space. GDB will still be\ncalled to access host memory using xfer_global_memory callback.\n\nTo be sure that the callback request is not routed back to dbgapi, the\nxfer_global_memory callback is modified to route the request to\nwhichever target sits below the amd-dbgapi target on the target stack.\n\nCo-Authored-By: Pedro Alves \u003cpedro@palves.net\u003e\nChange-Id: I2d5ca46edf65e2dec3606d18f7ad1d22d0275a63\n" }, { "commit": "9e6e6a2272c78ab8e975692427c641609c0b4573", "tree": "53e1c9e6de60074d21e5fcf6be2dc45fa4d8aa7f", "parents": [ "c4aa08decda4eaa2e3fd9126c6e152131b203dc1" ], "author": { "name": "Lancelot SIX", "email": "lancelot.six@amd.com", "time": "Wed May 08 11:36:28 2024 +0100" }, "committer": { "name": "Pedro Alves", "email": "pedro@palves.net", "time": "Fri Jun 12 14:36:48 2026 +0100" }, "message": "gdb/amd-dbgapi-target: Add amd-dbgapi-mingw-hdep.c for Windows\n\nThis patch adds amd-dbgapi-mingw-hdep.c which provides the\nimplementations for all the host specific interactions with dbgapi on\nMinGW.\n\nCo-Authored-By: Pedro Alves \u003cpedro@palves.net\u003e\nChange-Id: Ie244f2606b1e0af8f85b9113c3d93585eda893ed\n" }, { "commit": "c4aa08decda4eaa2e3fd9126c6e152131b203dc1", "tree": "59eaac084e15bae0707485e8a5762ac9037a43bd", "parents": [ "8b752803cf57408cfb7a50bc77a3cbc658f7ad23" ], "author": { "name": "Lancelot SIX", "email": "lancelot.six@amd.com", "time": "Wed May 08 11:15:22 2024 +0100" }, "committer": { "name": "Pedro Alves", "email": "pedro@palves.net", "time": "Fri Jun 12 14:36:40 2026 +0100" }, "message": "gdb/amd-dbgapi-target: Move Linux code to amd-dbagapi-posix-hdep.c\n\nThe current amd-dbgapi-target.c file contains some code that is Linux\nspecific. This patch extracts such code to host dependent files, so\nthey can be replaced for other host platforms.\n\nThe code in question is related to the event loop. The way dbgapi\nnotifies GDB that there is a pending event is platform specific. For\nLinux (the only platform supported so far), this is done using a file\ndescriptor GDB can use in its main event loop.\n\nThis patch introduces an overall host-dependency infrastructure and\nmoves the Linux-specific code to amd-dbgapi-posix-hdep.c. The \"posix\"\nnaming is because even though only Linux is supported, the code is\nreally plain POSIX code that would work on other POSIX platforms.\nThis also follows the existing posix-hdep.c nomenclature.\n\nCo-Authored-By: Pedro Alves \u003cpedro@palves.net\u003e\nChange-Id: Id3d4b947176e5cfe91b0ab64376fca1a6a8c6fc9\n" }, { "commit": "8b752803cf57408cfb7a50bc77a3cbc658f7ad23", "tree": "5b999c8c15f8afd70f7f313932b92ab279969bd1", "parents": [ "4cdc9a9d93571737476034869dd8caaecb5ca35d" ], "author": { "name": "Tom de Vries", "email": "tdevries@suse.de", "time": "Fri Jun 12 12:41:08 2026 +0200" }, "committer": { "name": "Tom de Vries", "email": "tdevries@suse.de", "time": "Fri Jun 12 12:41:08 2026 +0200" }, "message": "[gdb/build, clang] Fix ignored aligned attribute\n\nPR build/34279 reports a build failure with clang.\n\nThis is a regression since commit 6c85ef111b0 (\"[gdb] Use using instead of\ntypedef\"), which did:\n...\n-typedef long __attribute__ ((__aligned__ (4))) compat_x32_clock_t;\n+using compat_x32_clock_t \u003d long __attribute__ ((__aligned__ (4)));\n...\n\nThe problem is that clang ignores the attribute.\n\nFix this by reverting this part of the commit.\n\nBug: https://sourceware.org/bugzilla/show_bug.cgi?id\u003d34279\n" }, { "commit": "4cdc9a9d93571737476034869dd8caaecb5ca35d", "tree": "58474397b747e5e5357faffc40ca541ac70adb02", "parents": [ "0f6b256ca84c113a8b06d878f19ed98c40a62b3d" ], "author": { "name": "Richard Earnshaw", "email": "rearnsha@arm.com", "time": "Thu Jun 11 14:50:13 2026 +0100" }, "committer": { "name": "Richard Earnshaw", "email": "rearnsha@arm.com", "time": "Fri Jun 12 10:33:32 2026 +0100" }, "message": "gas: deprecate .vtable_entry and .vtable_inherit\n\nThese ELF directives were a GNU extension to support the C++ ABI\nthat was in use before the introduction of the generic C++ ABI in\nGCC-3.0. They\u0027re obsolete now and many newer targets simply\ndo not provide the back-end support for them.\n\nFlag them as deprecated in the NEWS file, and remove the documentation\nfor them. Warn (once) if the directive is used in a source file.\n" }, { "commit": "0f6b256ca84c113a8b06d878f19ed98c40a62b3d", "tree": "a7fc65c9d0b17a9d2aa0025ff2b31ae4121b088f", "parents": [ "d62f64e17b33fb76653fa0c008c61b782d07f8ec" ], "author": { "name": "Alan Modra", "email": "amodra@gmail.com", "time": "Fri Jun 12 08:32:18 2026 +0930" }, "committer": { "name": "Alan Modra", "email": "amodra@gmail.com", "time": "Fri Jun 12 08:49:42 2026 +0930" }, "message": "PR 30308 yet again\n\nCommit cc28c46227cd removed the symbol_resolving recursion guards in\ni386_intel_simplify_symbol. The testcases we\u0027d considered then just\ninvolved simple equates, handled by symbol_equated_to. However, more\ncomplex expressions can also cause unbounded recursion. This patch\nrestores the recursion guards.\n\n\t* config/tc-i386-intel.c (i386_intel_simplify_symbol): Add\n\trecursion guards.\n\t* testsuite/gas/i386/intel-equ-loop.s,\n\t* testsuite/gas/i386/intel-equ-loop.l: Extend testcase.\n" }, { "commit": "d62f64e17b33fb76653fa0c008c61b782d07f8ec", "tree": "920fdf011a2fe77a3830f3675dc2998fc9d88381", "parents": [ "c52a3e86835f40dc4048e038f3cec6b97dba69fb" ], "author": { "name": "Gopi Kumar Bulusu", "email": "gopi@sankhya.com", "time": "Thu May 07 17:47:40 2026 +0530" }, "committer": { "name": "Michael J. Eager", "email": "eager@eagercon.com", "time": "Thu Jun 11 05:49:52 2026 -0700" }, "message": "gdb/MicroBlaze: Add support for native linux gdb\n\nThis patch adds support for native microblazeel-linux-gdb including\nsupport for debugging with core dump files. Code is based on Xilinx/AMD\ngit repository used for Yocto builds with changes for proper indentation\nand removal of commented out code.\n\nTesting with native gdb has been checked to be working. Can load and run\na program using commands like break, step and finish. When a core file is\nspecified to gdb; registers can be examined using info reg. Tested using\nqemu-system-microblazeel from AMD/Xilinx Yocto 2025.2 release.\n\nSigned-off-by: David Holsgrove \u003cdavid.holsgrove@petalogix.com\u003e\nSigned-off-by: Nathan Rossi \u003cnathan.rossi@petalogix.com\u003e\nSigned-off-by: Mahesh Bodapati \u003cmbodapat@xilinx.com\u003e\nSigned-off-by: Gopi Kumar Bulusu \u003cgopi@sankhya.com\u003e\nSigned-off-by: Michael J. Eager \u003ceager@eagercon.com\u003e\n" }, { "commit": "c52a3e86835f40dc4048e038f3cec6b97dba69fb", "tree": "1133ab21db8979ff3b03ce14245daa011273c4df", "parents": [ "f4441fd82f1cf477683ed3c08271cff7e975937a" ], "author": { "name": "Rainer Orth", "email": "ro@CeBiTec.Uni-Bielefeld.DE", "time": "Thu Jun 11 10:05:03 2026 +0200" }, "committer": { "name": "Rainer Orth", "email": "ro@CeBiTec.Uni-Bielefeld.DE", "time": "Thu Jun 11 10:05:03 2026 +0200" }, "message": "gprof: Fix tests on Solaris [PR34237]\n\nThe gprof tests FAIL on Solaris:\n\ntst-gmon-gprof.sh ../gprof tst-gmon\n--- expected\n+++ actual\n@@ -1,3 +1,4 @@\n f1 2000\n f2 1000\n f3 1\n+main 1\nFAIL\n\nmain is included in the call graph, probably because Solaris still uses\nthe original BSD gmon.out format.\n\nThis patch allows for that difference. To distinguish between targets\nwith non-default handling, $target is passed to the test scripts.\n\nAs detailed in the PR, the powerpc with function descriptors special\ncase only applies to AIX, so that variant is guarded accordingly.\n\nTested on amd64-pc-solaris2.11, sparcv9-sun-solaris2.11, and\nx86_64-pc-linux-gnu.\n\n2026-06-08 Rainer Orth \u003cro@CeBiTec.Uni-Bielefeld.DE\u003e\n\n\tgprof:\n\tPR gprof/34237\n\t* testsuite/Makefile.am (tst-gmon-gprof.out): Pass $(target) to\n\ttst-gmon-gprof.sh.\n\t(tst-gmon-gprof-l.out): Likewise.\n\t(tst-gmon-gprof-l2.out): Likewise.\n\t* testsuite/Makefile.in: Regenerate.\n\n\t* testsuite/tst-gmon-gprof.sh (expected_dot): Remove.\n\t\u003c*-*-solaris2*\u003e: Allow main in execution counters.\n\t\u003cpowerpc-*-aix* | rs6000-*-aix*\u003e: Handle function descriptor case here.\n\t* testsuite/tst-gmon-gprof-l.sh: Likewise.\n\t* testsuite/tst-gmon-gprof-l2.sh: Likewise.\n" }, { "commit": "f4441fd82f1cf477683ed3c08271cff7e975937a", "tree": "af4f5cc08e6f2a91cc9682b2597ce12c7dc16de9", "parents": [ "6c85ef111b0430493792cde3b0fd572f1c78e732" ], "author": { "name": "Alan Modra", "email": "amodra@gmail.com", "time": "Thu Jun 11 11:10:40 2026 +0930" }, "committer": { "name": "Alan Modra", "email": "amodra@gmail.com", "time": "Thu Jun 11 16:38:53 2026 +0930" }, "message": "mips-coff: mips_reflo_reloc buffer overflow\n\nLike commit c2cb1bfb901e, but for mips-coff. Make the hi reloc list\nper-section rather than per-file, since fuzzers can generate objects\nwith cross-section refs where the hi reloc section data is freed\nbefore the lo relocs are processed.\n\nAlso properly sanity check the hi reloc offset.\n\n\t* libecoff.h (struct ecoff_tdata): Move mips_refhi_list to..\n\t(struct ecoff_section_tdata): ..here.\n\t(ecoff_section_data): Remove unused abfd arg.\n\t* coff-alpha.c (alpha_relocate_section): Update ecoff_section_data.\n\t* coff-mips.c (mips_refhi_reloc): Use bfd_reloc_offset_in_range.\n\tAllocate ecoff_section_data as necessary. Use that instead of\n\tbfd tdata.\n\t(mips_reflo_reloc): Adjust to suit tdata change.\n\t* ecoff.c (_bfd_ecoff_bfd_free_cached_info): Likewise.\n" }, { "commit": "6c85ef111b0430493792cde3b0fd572f1c78e732", "tree": "a4e73d21e6ffc6dd01280d91ad5ddcb6143a5fe6", "parents": [ "2eea7bca0ced1a25eb47ae586363fe32008b8566" ], "author": { "name": "Tom de Vries", "email": "tdevries@suse.de", "time": "Thu Jun 11 08:54:34 2026 +0200" }, "committer": { "name": "Tom de Vries", "email": "tdevries@suse.de", "time": "Thu Jun 11 08:54:34 2026 +0200" }, "message": "[gdb] Use using instead of typedef\n\nAfter commit 1eed06ae51d (\"[gdbsupport] Use using instead of typedef in\nnext_iterator\") I wondered if I could do something similar using sed.\n\nResult of:\n...\n$ find gdb* -type f -name \"*.[ch]\" -o -name \"*.cc\" \\\n | egrep -v /testsuite/ \\\n | xargs sed -i \\\n\t \u0027s/^\\([ \\t]*\\)typedef \\([a-zA-Z_0-9:\u003c\u003e,.() ]*\\) \\([\\*\u0026][\\*\u0026]*\\)\\([a-zA-Z_0-9]*\\);/\\1using \\4 \u003d \\2 \\3;/\u0027\n\n$ find gdb* -type f -name \"*.[ch]\" -o -name \"*.cc\" \\\n | egrep -v /testsuite/ \\\n | xargs sed -i \\\n\t \u0027s/^\\([ \\t]*\\)typedef \\([a-zA-Z_0-9:\u003c\u003e,.() ]*\\) \\([a-zA-Z_0-9]*\\);/\\1using \\3 \u003d \\2;/\u0027\n...\n\nTested on x86_64-linux.\n" }, { "commit": "2eea7bca0ced1a25eb47ae586363fe32008b8566", "tree": "5bea130ce206cb0c71b38ef9290c2b8760b55d9c", "parents": [ "a1c5e3df26f8d43954b9482e5f8e6d4b9b0fba3f" ], "author": { "name": "Jon Turney", "email": "jon.turney@dronecode.org.uk", "time": "Thu Jun 04 14:22:37 2026 +0100" }, "committer": { "name": "Alan Modra", "email": "amodra@gmail.com", "time": "Thu Jun 11 09:05:55 2026 +0930" }, "message": "ld: doc: Use consistent language for \u0027PE target\u0027-only options\n\nIt seems like the \u0027i386 PE targeted\u0027 phrasing probably predates x86_64\nPE support in binutils, and should have been touched when that was\nadded.\n\nEven loosely interpreting that phrase to mean \u0027those two Intel\narchitectures, you know what I mean\u0027, this is less than helpful now that\nPE aarch64 is a possibility.\n\nChange the use of various phrases like \u0027[This is an i386 PE specific\noption]\u0027 to conistently use \u0027[This option is specific to PE targeted\nports of the linker]\u0027 nearly everywhere.\n\nThe only options that really are specific in this way are\n\u0027--large-address-aware\u0027 (PE only) and \u0027--high-entropy-va\u0027 (PE+ only), so\nannotate those appropriately.\n\nDo an editing pass of the various other mentions of \u0027PE\u0027.\n\nAlso, add the \u0027PE only\u0027 annotation to the description of\n\u0027--leading-underscore\u0027 in the \u0027Options Specific to PE Targets\u0027 section,\nto be consistent with all the others.\n\nAlso, since we\u0027ve already mentioned that all the DllCharacteristics\nflags are PE-specific, don\u0027t awkwardly mention it (again) as part of the\nnote about what Windows version support for that flag was introduced in.\n\nFuture work: the phrase \u0027PE targeted port of the linker\u0027 seems a bit\noff, since cross-tools are a thing. Should it just be \u0027PE targeted linker\u0027?\n\n2026-06-01 Jon Turney \u003cjon.turney@dronecode.org.uk\u003e\n\n\t* ld.texi (Options): Use consistent language for \u0027PE target\u0027-only\n\toptions.\n" }, { "commit": "a1c5e3df26f8d43954b9482e5f8e6d4b9b0fba3f", "tree": "bc5c41889fcbd96bf55a0e6e4e4bd2d05d890d2a", "parents": [ "be655796fa92c0059224f51e4599c854ffd7440f" ], "author": { "name": "Tom Tromey", "email": "tromey@adacore.com", "time": "Tue Jun 09 06:51:02 2026 -0600" }, "committer": { "name": "Tom Tromey", "email": "tromey@adacore.com", "time": "Wed Jun 10 14:23:00 2026 -0600" }, "message": "Sort symtabs using their display filename\n\nWhile working on gnat-llvm, I found that many tests in\ngdb.ada/info_auto_lang.exp were failing. Investigating this, the\ndifference turned out to be a different sort order for the output. I\nthen tracked this down to gnat-llvm emitting:\n\n \u003ce3d\u003e DW_AT_name : (indirect string, offset: 0xdd4): pck.adb\n ...\n \u003ce45\u003e DW_AT_comp_dir : (indirect string, offset: 0xddc): /home/tromey/AdaCore/binutils-gdb/gdb/testsuite/gdb.ada/mi_dyn_arr/\n\n... whereas GCC emits:\n\n \u003c108b\u003e DW_AT_name : (indirect line string, offset: 0x10f): /home/tromey/gdb/binutils-gdb/gdb/testsuite/gdb.ada/mi_dyn_arr/pck.adb\n \u003c108f\u003e DW_AT_comp_dir : (indirect line string, offset: 0): /home/tromey/gdb/build/gdb/testsuite/outputs/gdb.ada/mi_dyn_arr\n\nThis distinction isn\u0027t relevant to the test, so I tried \"set\nfilename-display basename\". However, this setting had no effect.\n\nIt seems to me that, for \"info types\" and the like, the output should\nbe sorted according to the user\u0027s display preferences. This patch\nimplements this and adds a new DWARF assembler test.\n\nFinally, this updates info_auto_lang.exp to be insensitive to this\nquirk of gnat-llvm.\n\nApproved-By: Andrew Burgess \u003caburgess@redhat.com\u003e\n" }, { "commit": "be655796fa92c0059224f51e4599c854ffd7440f", "tree": "ebad641aa20dfb872bffec4f43b84e50adb2b5bb", "parents": [ "6ef2098548092df5bdb85c5e928fc235df21e97f" ], "author": { "name": "Andrew Burgess", "email": "aburgess@redhat.com", "time": "Wed Jun 10 19:43:24 2026 +0100" }, "committer": { "name": "Andrew Burgess", "email": "aburgess@redhat.com", "time": "Wed Jun 10 19:43:24 2026 +0100" }, "message": "gdb/testsuite: remove debug output messages from testsuite\n\nOver time I\u0027ve managed to leave various debug logging messages in the\ntestsuite, all of which include the \u0027APB\u0027 tag that I use to make\nsearching for these easier. None of these were required, they could\nall be removed.\n\nI have left the logging output in gdb.base/stap-probe.exp (but with\nthe \u0027APB\u0027 removed) as it looked slightly useful, and it\u0027s harmless to\nkeep it. But all of the other logging lines I just removed.\n\nThere should be no change in what is tested after this commit.\n" }, { "commit": "6ef2098548092df5bdb85c5e928fc235df21e97f", "tree": "fd6cee87f9c5ad875883737ac50a142f9a2f6ecd", "parents": [ "ddc575edf104eb477018a32b31074beffb179034" ], "author": { "name": "Sébastien Darche", "email": "sdarche@efficios.com", "time": "Thu May 21 11:12:17 2026 -0400" }, "committer": { "name": "Sébastien Darche", "email": "sdarche@efficios.com", "time": "Wed Jun 10 11:28:30 2026 -0400" }, "message": "gdb/breakpoint: remove assertion when printing internal breakpoints without locspecs\n\nWhen debugging gdb with `set debug breakpoint on`, gdb would crash if\nthe inferior happened to unload (through dlclose ()) a shared library\nthat contains jit debugging symbols:\n\n\t../../gdb/breakpoint.c:6473: internal-error: print_breakpoint_location:\n\tAssertion `b-\u003elocspec !\u003d nullptr || (!user_breakpoint_p (b) \u0026\u0026 (b-\u003etype\n\t\u003d\u003d bp_shlib_event || b-\u003etype \u003d\u003d bp_thread_event))\u0027 failed.\n\tA problem internal to GDB has been detected [...]\n\nThis assertion was added in commit 5770f68 (\"gdb: handle empty locspec\nwhen printing breakpoints\"). The assumption for this assert is that the\nuser may not call any (gdb-)debugging command between the time a shared\nlibrary is marked (bp_location-\u003eshlib_disabled is set) and the\nbreakpoint is actually removed. This would be true if the user called\n`maint info breakpoints` as explained in the original commit message.\n\nHowever, if `set debug breakpoint on` is called, gdb prints debugging\ninfo as the shared library is being unloaded. The ~jiter_objfile_data\ndtor deletes the breakpoint, which calls remove_breakpoint_1 on the\nbp_location in the recently unloaded shared object. Since `debug\nbreakpoint` is enabled, we go through print_breakpoint_location with the\nbp_location\u0027s shlib_disabled flag set, which results in the assert\nabove.\n\nThis commit removes the assertion as it is not true in all cases. I\u0027ve\nalso included a minimal test case that loads a shared library with a\n__jit_debug_register_code symbol. The test fails with the assert.\n\nApproved-By: Andrew Burgess \u003caburgess@redhat.com\u003e\nChange-Id: Ia19c84f194a6f0c10315548c7f423bfd86ef0266\n" }, { "commit": "ddc575edf104eb477018a32b31074beffb179034", "tree": "7264155985e7c75461fc372db9cca6c2e521bbfe", "parents": [ "31431841c09357f6f598549d69d9e98b89dde08e" ], "author": { "name": "Tom de Vries", "email": "tdevries@suse.de", "time": "Wed Jun 10 11:43:35 2026 +0200" }, "committer": { "name": "Tom de Vries", "email": "tdevries@suse.de", "time": "Wed Jun 10 11:43:35 2026 +0200" }, "message": "[gdb/testsuite] Codespell fixes\n\nFix typos in gdb/testsuite using an interactive session:\n...\n$ codespell --toml gdb/pyproject.toml -w -i 3 gdb/testsuite\n...\n" }, { "commit": "31431841c09357f6f598549d69d9e98b89dde08e", "tree": "a9906eba2921efb072cdda856c4f78a1047d90b0", "parents": [ "3feb42142005c63ac424a06d1b4d8a3b667d63e8" ], "author": { "name": "Tom de Vries", "email": "tdevries@suse.de", "time": "Wed Jun 10 11:11:53 2026 +0200" }, "committer": { "name": "Tom de Vries", "email": "tdevries@suse.de", "time": "Wed Jun 10 11:11:53 2026 +0200" }, "message": "[gdb/contrib] Fix UnicodeDecodeError in dwarf-to-dwarf-assembler.py\n\nWhen running dwarf-to-dwarf-assembler.py on outputs/gdb.rust/unicode/unicode,\nI run into a UnicodeDecodeError for (using readelf -w):\n...\n \u003c4\u003e\u003c9cf\u003e: Abbrev Number: 10 (DW_TAG_variable)\n \u003c9d3\u003e DW_AT_name : (indirect string, offset: 0xab4): 𝕯\n...\nor more explicit using llvm-dwarfdump -v:\n...\n0x000009cf: DW_TAG_variable [10] (0x000009c2)\n DW_AT_name [DW_FORM_strp] ( .debug_str[0x00000ab4] \\\n \u003d \"\\360\\235\\225\\257\")\n...\n\nFix this by using UTF-8 instead of ascii decoding, which gets us instead:\n...\n DW_AT_name 𝕯 DW_FORM_strp\n...\n\nBug: https://sourceware.org/bugzilla/show_bug.cgi?id\u003d33970\n" }, { "commit": "3feb42142005c63ac424a06d1b4d8a3b667d63e8", "tree": "d0319fa88113bec9aa3dcb9843a7ed52694a7443", "parents": [ "04e04460078274b4011b5cb892e162ff61083fcb" ], "author": { "name": "Tom de Vries", "email": "tdevries@suse.de", "time": "Wed Jun 10 09:54:22 2026 +0200" }, "committer": { "name": "Tom de Vries", "email": "tdevries@suse.de", "time": "Wed Jun 10 09:54:22 2026 +0200" }, "message": "[gdb/contrib] Fix ELFParseError in dwarf-to-dwarf-assembler.py\n\nWhen running dwarf-to-dwarf-assembler.py on\noutputs/gdb.dwarf2/implptr-64bit/implptr-64bit-d2-o8-a4-r4-t0, I run into:\n...\nelftools.common.exceptions.ELFParseError: expected 8, found 5\n...\nfor the DWARF:\n...\n \u003c2\u003e\u003c335\u003e: Abbrev Number: 8 (DW_TAG_variable)\n \u003c336\u003e DW_AT_name : p\n \u003c338\u003e DW_AT_location : 6 byte block: f2 14 3 0 0 0 \\\n (DW_OP_GNU_implicit_pointer: \u003c0x314\u003e 0)\n...\n\nPyelftools expects that DW_OP_GNU_implicit_pointer has an 8-byte reference\noperand (because it\u0027s a 64-bit DWARF unit), but instead it has a 4-byte\nreference.\n\nThe DWARF is correct, it\u0027s a cornercase of using DW_OP_GNU_implicit_pointer in\nDWARF v2, where DW_FORM_ref_addr references have the same size as an address\non the target system, something that was changed in DWARF v3.\n\nHandle this by catching the error and printing:\n...\nDW_AT_location \"\\xf2\\x14\\x03\\x00\\x00\\x00\" DW_FORM_block \\\n # Failed to print DWARF expression: expected 8, found 5\n...\n\nApproved-By: Tom Tromey \u003ctom@tromey.com\u003e\n" }, { "commit": "04e04460078274b4011b5cb892e162ff61083fcb", "tree": "cd3bae86f8e61f77bac1ccdfda2cdecc00983885", "parents": [ "500390720267e2f009f0354e5051fa2e176b143d" ], "author": { "name": "Tom de Vries", "email": "tdevries@suse.de", "time": "Wed Jun 10 09:54:22 2026 +0200" }, "committer": { "name": "Tom de Vries", "email": "tdevries@suse.de", "time": "Wed Jun 10 09:54:22 2026 +0200" }, "message": "[gdb/contrib] Fix KeyError in dwarf-to-dwarf-assembler.py\n\nExecutable outputs/gdb.threads/stepi-over-clone/stepi-over-clone contains the\nfollowing DWARF (using readelf -w):\n...\n \u003c31c5\u003e DW_AT_const_value : 8 byte block: ff ff ff ff ff ff ff ff\n...\nor more explicit using llvm-dwarfdump -v:\n...\n DW_AT_const_value [DW_FORM_block1] \\\n\t\t (\u003c0x08\u003e ff ff ff ff ff ff ff ff )\n...\n\nBefore commit 18ad8c1a54d (\"Emit DWARF expressions from\ndwarf-to-dwarf-assembler.py\"), the dwarf-to-dwarf-assembler.py script\ngenerated:\n...\nDW_AT_const_value { MANUAL: Fill expr list } SPECIAL_expr\n...\nfor this.\n\nBut since the commit, we run into a KeyError.\n\nThe problem is that we\u0027re trying to interpret some random data as a DWARF\nexpression.\n\nFix this by special-casing DW_AT_const_value, and generating instead:\n...\nDW_AT_const_value \"\\xff\\xff\\xff\\xff\\xff\\xff\\xff\\xff\" DW_FORM_block1\n...\nwhich mimics the style I found in gdb.dwarf2/info-locals-optimized-out.exp:\n...\n DW_TAG_variable {\n DW_AT_name const_bytes\n DW_AT_type :$int_type_label\n DW_AT_const_value \"\\x01\\x01\\x01\\x01\" DW_FORM_block1\n\t\t}\n...\n\nLikewise for DW_AT_discr_list.\n\nAnother case for which the KeyError triggers, is DWARF from\noutputs/gdb.ada/array_of_variant/p-minimal:\n...\n \u003c2\u003e\u003c14a4\u003e: Abbrev Number: 20 (DW_TAG_structure_type)\n \u003c14a5\u003e DW_AT_name : p__payload_t\n \u003c14a9\u003e DW_AT_byte_size : 18 byte block: \\\n fd 63 14 0 0 97 94 1 99 45 0 0 0 23 7 9 fc 1a \\\n\t\t\t\t (DW_OP_GNU_variable_value: \u003c0x1463\u003e; \\\n\t\t\t\t DW_OP_push_object_address; \\\n\t\t\t\t DW_OP_deref_size: 1; \\\n\t\t\t\t DW_OP_call4: \u003c0x1421\u003e; \\\n\t\t\t\t DW_OP_plus_uconst: 7; \\\n\t\t\t\t DW_OP_const1s: -4; DW_OP_and)\n...\nbecause the pyelftools version that I\u0027m using doesn\u0027t support\nDW_OP_GNU_variable_value yet (supported starting v0.33).\n\nFix this by catching the KeyError, and falling back to the string case:\n...\n DW_AT_byte_size \\\n \"\\xfd\\x63\\x14\\x00\\x00\\x97\\x94\\x01\\x99\\x45\\x00\\x00\\x00\\x23\\x07\\x09\\xfc\\x1a\" \\\n DW_FORM_exprloc # Failed to print op as DWARF expression: 0xfd\n...\n" }, { "commit": "500390720267e2f009f0354e5051fa2e176b143d", "tree": "5d29b229c0fdacd6a1c0560ae165310e26fae0e2", "parents": [ "06dc564fcc4a2cdb40d6572c8ba36cbb12904e26" ], "author": { "name": "Alan Modra", "email": "amodra@gmail.com", "time": "Wed Jun 10 11:40:59 2026 +0930" }, "committer": { "name": "Alan Modra", "email": "amodra@gmail.com", "time": "Wed Jun 10 15:27:37 2026 +0930" }, "message": "PR 34204 dlltool SEGVs with --exclude-symbols\n\nThis fixes a segfault introduced by commit 45a7f5a29de7 which didn\u0027t\ntake into account that there was a use of leading_underscore in option\nprocessing.\n\n\tPR 34204\n\t* dlltool.c (struct string_list): Make string a flexible array\n\tmember.\n\t(add_excludes): Adjust to suit. Extract code adding underscore\n\tand informing..\n\t(underscore_excludes): ..to here. New function.\n\t(main): Call underscore_excludes.\n" }, { "commit": "06dc564fcc4a2cdb40d6572c8ba36cbb12904e26", "tree": "b002b9a1aff6152cb89b9c7e48885acdede5abb6", "parents": [ "205b8647a090d49a4d994196207989ecfe4cb9e7" ], "author": { "name": "Markus Metzger", "email": "markus.t.metzger@intel.com", "time": "Thu Nov 20 11:21:41 2025 +0000" }, "committer": { "name": "Markus Metzger", "email": "markus.t.metzger@intel.com", "time": "Wed Jun 10 04:45:58 2026 +0000" }, "message": "gdb, btrace: support libipt v2.2 events\n\nAdd support for printing new events added in libipt v2.2 originating from\nEvent Tracing in combination with Flexible Return and Event Delivery\n(FRED) and from Trigger Tracing.\n\nReviewed-By: Keith Seitz \u003ckeiths@redhat.com\u003e\nReviewed-By: Eli Zaretskii \u003celiz@gnu.org\u003e\n" }, { "commit": "205b8647a090d49a4d994196207989ecfe4cb9e7", "tree": "e1d752850f6c4ac9e666062980d4c2804c2923d3", "parents": [ "970570ce5ca76907b25578e70ebbf58d46721a5f" ], "author": { "name": "Markus Metzger", "email": "markus.t.metzger@intel.com", "time": "Mon May 04 06:49:34 2026 +0000" }, "committer": { "name": "Markus Metzger", "email": "markus.t.metzger@intel.com", "time": "Wed Jun 10 04:44:47 2026 +0000" }, "message": "gdb, btrace: fix wrong #endif comments\n\nApproved-By: Simon Marchi \u003csimon.marchi@efficios.com\u003e\n" }, { "commit": "970570ce5ca76907b25578e70ebbf58d46721a5f", "tree": "0fdb8cbd8976658f552077f11de63378bf18905c", "parents": [ "ab0df7ebbf20de068d4fb3c3134407410afbc046" ], "author": { "name": "Tom de Vries", "email": "tdevries@suse.de", "time": "Tue Jun 09 22:14:07 2026 +0200" }, "committer": { "name": "Tom de Vries", "email": "tdevries@suse.de", "time": "Tue Jun 09 22:14:07 2026 +0200" }, "message": "[gdb] Add missing i18n support to warning strings (part 5)\n\nAdd missing i18n support to some multi-line warning strings.\n\nApproved-By: Tom Tromey \u003ctom@tromey.com\u003e\n" }, { "commit": "ab0df7ebbf20de068d4fb3c3134407410afbc046", "tree": "089fd9c45fc228188ed65171eb2b6512d7dc74fa", "parents": [ "3d094ec4c56db0b34c7e9a90084df8f89f2ca879" ], "author": { "name": "Tom de Vries", "email": "tdevries@suse.de", "time": "Tue Jun 09 22:14:07 2026 +0200" }, "committer": { "name": "Tom de Vries", "email": "tdevries@suse.de", "time": "Tue Jun 09 22:14:07 2026 +0200" }, "message": "[gdb] Add missing i18n support to warning strings (part 4)\n\nAdd missing i18n support to some warning strings.\n\nResult of:\n...\n$ find gdb* -type f -name \"*.[ch]\" -o -name \"*.cc\" \\\n | egrep -v /testsuite/ \\\n | xargs sed -i \\\n \u0027/\"[ \\t]*%s[ \\t]*\"/b l;s/\\([ \\t]\\)warning (\\(\"[^\"]*\"\\)\\(.*\\));/\\1warning (_(\\2)\\3);/;:l\u0027\n...\n\nApproved-By: Tom Tromey \u003ctom@tromey.com\u003e\n" }, { "commit": "3d094ec4c56db0b34c7e9a90084df8f89f2ca879", "tree": "bea15c3dab41931bd0b98f86fa3c7015d8f95d87", "parents": [ "6c22e5b94a17b88402dc90e3e526ee9f7fc1580a" ], "author": { "name": "Tom de Vries", "email": "tdevries@suse.de", "time": "Tue Jun 09 22:14:07 2026 +0200" }, "committer": { "name": "Tom de Vries", "email": "tdevries@suse.de", "time": "Tue Jun 09 22:14:07 2026 +0200" }, "message": "[gdb] Add missing i18n support to warning strings (part 3)\n\nAdd missing i18n support to some warning strings.\n\nResult of:\n...\n$ find gdb* -type f -name \"*.[ch]\" -o -name \"*.cc\"\n | egrep -v /testsuite/ \\\n | xargs sed -i \\\n \u0027/\"[ \\t]*%s[ \\t]*\"/b l;s/\\([ \\t]\\)warning (\\(\"[^\"]*\"\\),$/\\1warning (_(\\2),/;:l\u0027\n...\n\nApproved-By: Tom Tromey \u003ctom@tromey.com\u003e\n" }, { "commit": "6c22e5b94a17b88402dc90e3e526ee9f7fc1580a", "tree": "5675c225a6d9935a9d857e7fb95c5b91e7500eb9", "parents": [ "edad26d2e813bea2828b742e9e1fc208646d758a" ], "author": { "name": "Tom de Vries", "email": "tdevries@suse.de", "time": "Tue Jun 09 22:14:07 2026 +0200" }, "committer": { "name": "Tom de Vries", "email": "tdevries@suse.de", "time": "Tue Jun 09 22:14:07 2026 +0200" }, "message": "[gdb] Add missing i18n support to warning strings (part 2)\n\nAdd missing i18n support to some warning strings.\n\nResult of:\n...\n$ find gdb* -type f -name \"*.[ch]\" -o -name \"*.cc\" \\\n | egrep -v /testsuite/ \\\n | xargs sed -i \\\n \u0027/\"[ \\t]*%s[ \\t]*\"/b l;s/\\([ \\t]\\)warning (\\(\"[^\"]*\"\\)\\([^)]*\\));/\\1warning (_(\\2)\\3);/;:l\u0027\n...\n\nApproved-By: Tom Tromey \u003ctom@tromey.com\u003e\n" }, { "commit": "edad26d2e813bea2828b742e9e1fc208646d758a", "tree": "be9c9bccc18f6d4ff5f2c13289cdf5dc30337015", "parents": [ "635572ef07dce4a90c530dc7c18817e1a2107371" ], "author": { "name": "Tom de Vries", "email": "tdevries@suse.de", "time": "Tue Jun 09 22:14:07 2026 +0200" }, "committer": { "name": "Tom de Vries", "email": "tdevries@suse.de", "time": "Tue Jun 09 22:14:07 2026 +0200" }, "message": "[gdb] Add missing i18n support to warning strings (part 1)\n\nAdd missing i18n support to some warning strings.\n\nResult of:\n...\n$ find gdb* -type f -name \"*.[ch]\" -o -name \"*.cc\" \\\n | egrep -v /testsuite/ \\\n | xargs sed -i \\\n \u0027s/\\([ \\t]\\)warning (\\(\"[^\"]*\"\\));/\\1warning (_(\\2));/\u0027\n...\n\nApproved-By: Tom Tromey \u003ctom@tromey.com\u003e\n" }, { "commit": "635572ef07dce4a90c530dc7c18817e1a2107371", "tree": "a48ca2e6a71f213f10d421581f173277c890b369", "parents": [ "ca83136019f70ec8875114437e84b7a3b4fbeb14" ], "author": { "name": "Tom de Vries", "email": "tdevries@suse.de", "time": "Tue Jun 09 22:14:07 2026 +0200" }, "committer": { "name": "Tom de Vries", "email": "tdevries@suse.de", "time": "Tue Jun 09 22:14:07 2026 +0200" }, "message": "[gdb] Add missing i18n support to errors strings (part 5)\n\nAdd missing i18n support to some multi-line error strings.\n\nApproved-By: Tom Tromey \u003ctom@tromey.com\u003e\n" }, { "commit": "ca83136019f70ec8875114437e84b7a3b4fbeb14", "tree": "2952989088c4b57c6b9844221b2e5a4af6f23282", "parents": [ "d62997ecff3aa9e9ea15c4d73494f229c7d63ee1" ], "author": { "name": "Tom de Vries", "email": "tdevries@suse.de", "time": "Tue Jun 09 22:14:07 2026 +0200" }, "committer": { "name": "Tom de Vries", "email": "tdevries@suse.de", "time": "Tue Jun 09 22:14:07 2026 +0200" }, "message": "[gdb] Add missing i18n support to error strings (part 4)\n\nAdd missing i18n support to some error strings.\n\nResult of:\n...\n$ find gdb* -type f -name \"*.[ch]\" -o -name \"*.cc\" \\\n | egrep -v /testsuite/ \\\n | xargs sed -i \\\n \u0027/\"[ \\t]*%s[ \\t]*\"/b l;s/\\([ \\t]\\)error (\\(\"[^\"]*\"\\)\\(.*\\));/\\1error (_(\\2)\\3);/;:l\u0027\n...\n\nApproved-By: Tom Tromey \u003ctom@tromey.com\u003e\n" }, { "commit": "d62997ecff3aa9e9ea15c4d73494f229c7d63ee1", "tree": "b2eea1e03e7a6093e2413f6ef1740d5f9d0c6c09", "parents": [ "5a6fa4bf84e2dc5f02bbac3f2412a1a270b56036" ], "author": { "name": "Tom de Vries", "email": "tdevries@suse.de", "time": "Tue Jun 09 22:14:07 2026 +0200" }, "committer": { "name": "Tom de Vries", "email": "tdevries@suse.de", "time": "Tue Jun 09 22:14:07 2026 +0200" }, "message": "[gdb] Add missing i18n support to error strings (part 3)\n\nAdd missing i18n support to some error strings.\n\nResult of:\n...\n$ find gdb* -type f -name \"*.[ch]\" -o -name \"*.cc\" \\\n | egrep -v /testsuite/ \\\n | xargs sed -i \\\n \u0027/\"[ \\t]*%s[ \\t]*\"/b l;s/\\([ \\t]\\)error (\\(\"[^\"]*\"\\)\\([^)]*\\));/\\1error (_(\\2)\\3);/;:l\u0027\n...\n\nApproved-By: Tom Tromey \u003ctom@tromey.com\u003e\n" }, { "commit": "5a6fa4bf84e2dc5f02bbac3f2412a1a270b56036", "tree": "6386179addcb6f596332054048cf8ee3c7f24e5a", "parents": [ "d7e2f7f484c821458a669ade4be66c5b91a62f3f" ], "author": { "name": "Tom de Vries", "email": "tdevries@suse.de", "time": "Tue Jun 09 22:14:07 2026 +0200" }, "committer": { "name": "Tom de Vries", "email": "tdevries@suse.de", "time": "Tue Jun 09 22:14:07 2026 +0200" }, "message": "[gdb] Add missing i18n support to error strings (part 2)\n\nAdd missing i18n support to some error strings.\n\nResult of:\n...\n$ find gdb* -type f -name \"*.[ch]\" -o -name \"*.cc\" \\\n | egrep -v /testsuite/ \\\n | xargs sed -i \\\n \u0027/\"[ \\t]*%s[ \\t]*\"/b l;s/\\([ \\t]\\)error (\\(\"[^\"]*\"\\),$/\\1error (_(\\2),/;:l\u0027\n...\n\nApproved-By: Tom Tromey \u003ctom@tromey.com\u003e\n" }, { "commit": "d7e2f7f484c821458a669ade4be66c5b91a62f3f", "tree": "198d2c95254f3558424087d4a178dee07b170103", "parents": [ "1fa6aa8fcfab3c613bd4a0f2606e068a6ece4f88" ], "author": { "name": "Tom de Vries", "email": "tdevries@suse.de", "time": "Tue Jun 09 22:14:06 2026 +0200" }, "committer": { "name": "Tom de Vries", "email": "tdevries@suse.de", "time": "Tue Jun 09 22:14:06 2026 +0200" }, "message": "[gdb] Add missing i18n support to error strings (part 1)\n\nAdd missing i18n support to some error strings.\n\nResult of:\n...\n$ find gdb* -type f \\\n | egrep -v /testsuite/ \\\n | xargs sed -i \\\n \u0027s/\\([ \\t]\\)error (\\(\"[^\"]*\"\\));/\\1error (_(\\2));/\u0027\n...\n\nApproved-By: Tom Tromey \u003ctom@tromey.com\u003e\n" }, { "commit": "1fa6aa8fcfab3c613bd4a0f2606e068a6ece4f88", "tree": "b47d462dc4e5480f69777c5a37dc0ccbc050c263", "parents": [ "f0d6ada6cb2647173a0aa13220d987178fc3f64d" ], "author": { "name": "Tom de Vries", "email": "tdevries@suse.de", "time": "Tue Jun 09 20:31:54 2026 +0200" }, "committer": { "name": "Tom de Vries", "email": "tdevries@suse.de", "time": "Tue Jun 09 20:31:54 2026 +0200" }, "message": "[gdb/testsuite] Fix typo in configure.ac\n\nFix a typo in gdb/testsuite/configure.ac, and regenerate\ngdb/testsuite/configure.\n\nApproved-By: Tom Tromey \u003ctom@tromey.com\u003e\n" }, { "commit": "f0d6ada6cb2647173a0aa13220d987178fc3f64d", "tree": "c85d84ca37de259dc09541289323db69af3e0024", "parents": [ "d47ddaea734d0e423378466a7d899175e4a52796" ], "author": { "name": "Tom de Vries", "email": "tdevries@suse.de", "time": "Tue Jun 09 20:23:25 2026 +0200" }, "committer": { "name": "Tom de Vries", "email": "tdevries@suse.de", "time": "Tue Jun 09 20:23:25 2026 +0200" }, "message": "[gdb/build] Fix building gdb.pot\n\nSince commit 8708a20e2bb (\"gdb: store gdbtk object files into their sources\ndirectory\"), building gdb.pot is broken.\n\nThe commit added gdbtk/generic to CONFIG_SRC_SUBDIR, and building gdb.pot\nbreaks because the directory doesn\u0027t exist.\n\nFix this by ignoring the dir while building gdb.pot.\n\nApproved-By: Tom Tromey \u003ctom@tromey.com\u003e\n\nBug: https://sourceware.org/bugzilla/show_bug.cgi?id\u003d34212\n" }, { "commit": "d47ddaea734d0e423378466a7d899175e4a52796", "tree": "fe3e4390ff14753b8e50449fdd6c49ebdb639f6a", "parents": [ "1eed06ae51d73a195b78ce0903ada9c9c2c14cfb" ], "author": { "name": "Tom Tromey", "email": "tromey@adacore.com", "time": "Tue Jun 09 07:36:37 2026 -0600" }, "committer": { "name": "Tom Tromey", "email": "tromey@adacore.com", "time": "Tue Jun 09 10:34:51 2026 -0600" }, "message": "Make two Ada tests more robust\n\ntasks.exp and task_watch.exp were failing when run with gnat-llvm.\nInvestigating these showed the same problem (which makes sense because\nthe tests use the same program). In this code:\n\n for J in Task_List\u0027Range loop -- STOP_HERE\n Task_List (J).Call_Break_Me;\n end loop;\n\n... with GCC, the breakpoint set on the \u0027for\u0027 line is only hit a\nsingle time. However, with gnat-llvm, the breakpoint is hit on every\niteration of the loop. IMO this is a GCC bug.\n\nSimilarly, at the end of the function:\n\n null; -- STOP_HERE_2\n\n... with gnat-llvm, a breakpoint set here was not being hit. It seems\nperhaps somewhat strange to set a breakpoint on a null statement at\nthe end of a function; and while this might possibly be a gnat-llvm\nbug, this isn\u0027t really the point of this test.\n\nThis patch makes these tests more robust by arranging for the\nbreakpoints to be set before the loop and on a call, respectively.\n\nBecause this is Ada-specific, was reviewed internally, and is just a\nminor test case adjustment, I am checking it in.\n" }, { "commit": "1eed06ae51d73a195b78ce0903ada9c9c2c14cfb", "tree": "4b16203f0e2f8eef0f6ef04c04299e8030cc0fb1", "parents": [ "8aa13e4e29c4891adbef0dee4e5da26349cbc2c9" ], "author": { "name": "Tom de Vries", "email": "tdevries@suse.de", "time": "Tue Jun 09 14:37:16 2026 +0200" }, "committer": { "name": "Tom de Vries", "email": "tdevries@suse.de", "time": "Tue Jun 09 14:37:16 2026 +0200" }, "message": "[gdbsupport] Use using instead of typedef in next_iterator\n\nUse using instead of typedef in next_iterator. While we\u0027re at it, do the same\nin basic_safe_iterator.\n\nSuggested-By: Simon Marchi \u003csimon.marchi@polymtl.ca\u003e\nCo-Authored-By: Simon Marchi \u003csimon.marchi@polymtl.ca\u003e\n" }, { "commit": "8aa13e4e29c4891adbef0dee4e5da26349cbc2c9", "tree": "1786a7eeaacd1ca71952e6b502330c990e041394", "parents": [ "fb7b22bbeac9f26043f3aa92228c6ade7e2ea232" ], "author": { "name": "Tom de Vries", "email": "tdevries@suse.de", "time": "Tue Jun 09 14:37:16 2026 +0200" }, "committer": { "name": "Tom de Vries", "email": "tdevries@suse.de", "time": "Tue Jun 09 14:37:16 2026 +0200" }, "message": "[gdb] Add unit test for next_iterator\n\nI noticed that next_iterator doesn\u0027t have a selftest. Add this.\n" }, { "commit": "fb7b22bbeac9f26043f3aa92228c6ade7e2ea232", "tree": "189819a97611891045032ee6577379648aa00bcc", "parents": [ "bccfda8cc930fc2d16e65cd6df130bc7722dc772" ], "author": { "name": "Matthieu Longo", "email": "matthieu.longo@arm.com", "time": "Mon Jun 08 11:27:44 2026 +0100" }, "committer": { "name": "Matthieu Longo", "email": "matthieu.longo@arm.com", "time": "Tue Jun 09 10:58:21 2026 +0100" }, "message": "gdb_py_tp_name: remove redundant PyErr_Clear\n\ngdbpy_print_stack() already clears the error indicator.\nThus remove the following call to PyErr_Clear().\n\nApproved-By: Andrew Burgess \u003caburgess@redhat.com\u003e\n" }, { "commit": "bccfda8cc930fc2d16e65cd6df130bc7722dc772", "tree": "ccfd83d39e10859414a17ebb9f7e6213b5abaa59", "parents": [ "748350ae9e20d4698527c57bb3d3d76a33242cab" ], "author": { "name": "Etienne Brateau", "email": "etienne.brateau@gmail.com", "time": "Tue Jun 09 10:27:57 2026 +0200" }, "committer": { "name": "Tom de Vries", "email": "tdevries@suse.de", "time": "Tue Jun 09 10:27:57 2026 +0200" }, "message": "gdb: Fix build for gnu hurd\n\nCommit 695fd5ec122 (\"gdb: make find_memory_region_ftype a function_view\")\nbroke the build for gnu hurd. Fix this.\n\nApproved-By: Tom de Vries \u003ctdevries@suse.de\u003e\n" }, { "commit": "748350ae9e20d4698527c57bb3d3d76a33242cab", "tree": "ba74a984e90467a0ff024fb79776e3a86a62aa2b", "parents": [ "618fc86830cb51295ff9e177c0c55ebc93e5efc5" ], "author": { "name": "Matthieu Longo", "email": "matthieu.longo@arm.com", "time": "Wed May 20 11:46:56 2026 +0100" }, "committer": { "name": "Matthieu Longo", "email": "matthieu.longo@arm.com", "time": "Mon Jun 08 09:34:30 2026 +0100" }, "message": "gdb: fix typo gcs_availabe\n\nApproved-by: Thiago Jung Bauermann \u003cthiago.bauermann@linaro.org\u003e\n" }, { "commit": "618fc86830cb51295ff9e177c0c55ebc93e5efc5", "tree": "62b5a500ffbd5c4a412105949d79339ec8ae186a", "parents": [ "8a651beaceff37a5a4347c325755d81470c6f127" ], "author": { "name": "Alan Modra", "email": "amodra@gmail.com", "time": "Mon Jun 08 09:13:51 2026 +0930" }, "committer": { "name": "Alan Modra", "email": "amodra@gmail.com", "time": "Mon Jun 08 10:05:30 2026 +0930" }, "message": "Re: RISC-V: riscv_parse_subset_t\u0027s isa_spec is only parser input\n\ncheck_compiler_available fails with a ld segfault linking\nint main (void) { return 0; }\n\nProgram received signal SIGSEGV, Segmentation fault.\n0x0000000000466a64 in riscv_parse_add_subset (rps\u003drps@entry\u003d0x7fffffffd450, subset\u003dsubset@entry\u003d0x962ca0 \"zaamo\", major\u003d-1, minor\u003d-1, implicit\u003dimplicit@entry\u003dtrue) at /home/alan/src/binutils-gdb/bfd/elfxx-riscv.c:1947\n1947\t riscv_get_default_ext_version (*rps-\u003eisa_spec, subset,\n(gdb) p rps-\u003eisa_spec\n$1 \u003d (const enum riscv_spec_class *) 0x0\n\nThis was triggered when calling riscv_merge_attributes for crti.o\nwhich had\n(gdb) p ibfd-\u003etdata.elf_obj_data-\u003eknown_obj_attributes[OBJ_ATTR_PROC][Tag_RISCV_arch]\n$5 \u003d {type \u003d 2, i \u003d 0, s \u003d 0x97e4c0 \"rv64i2p1_m2p0_a2p1_f2p2_d2p2_c2p0_zicsr2p0_zifencei2p0_zmmul1p0\"}\n\nFix the segfault by reinstating a NULL check removed with commit\n413cf36d8e81\n" }, { "commit": "8a651beaceff37a5a4347c325755d81470c6f127", "tree": "73829ce8b54017b5cc2a98986d915834829d633e", "parents": [ "4562eab73d375e57f3c5a67f62d2678d7730d7ab" ], "author": { "name": "GDB Administrator", "email": "gdbadmin@sourceware.org", "time": "Mon Jun 08 00:00:08 2026 +0000" }, "committer": { "name": "GDB Admin", "email": "brobecker@adacore.com", "time": "Mon Jun 08 00:00:08 2026 +0000" }, "message": "Automatic date update in version.in\n" }, { "commit": "4562eab73d375e57f3c5a67f62d2678d7730d7ab", "tree": "21590200c713bf5a3147b09827694a90d94c510f", "parents": [ "0a6aadacb2e9a2695c82635dd8b2f7fccf537adf" ], "author": { "name": "GDB Administrator", "email": "gdbadmin@sourceware.org", "time": "Sun Jun 07 00:00:08 2026 +0000" }, "committer": { "name": "GDB Admin", "email": "brobecker@adacore.com", "time": "Sun Jun 07 00:00:08 2026 +0000" }, "message": "Automatic date update in version.in\n" }, { "commit": "0a6aadacb2e9a2695c82635dd8b2f7fccf537adf", "tree": "9702f524d4be104d384d15a9704a93fb898d037f", "parents": [ "f9c26587f19ebfacc8c55caa72120833dad7ee45" ], "author": { "name": "Alan Modra", "email": "amodra@gmail.com", "time": "Sat Jun 06 11:08:11 2026 +0930" }, "committer": { "name": "Alan Modra", "email": "amodra@gmail.com", "time": "Sat Jun 06 11:08:11 2026 +0930" }, "message": "filter_implib_symbols\n\nThis tidies filter_implib_symbols implementations, which I noticed\nreturned unsigned int but took long symbol counts. While unsigned int\nis very likely sufficient, size_t is better.\n\n_bfd_elf_filter_global_symbols is a linker-only function so really\nshould be moved to elflink.c, but I left it in elf.c as it calls\nsym_is_global, a static function in elf.c.\n\n\t* elf-bfd.h (struct elf_backend_data): Take size_t symcount\n\tand return a size_t from elf_backend_filter_implib_symbols.\n\t(_bfd_elf_filter_implib_symbols): Likewise. Rename from\n\t_bfd_elf_filter_global_symbols.\n\t* elf.c (_bfd_elf_filter_implib_symbols): Likewise. Use\n\tsize_t vars too, and avoid unnecessary casts.\n\t* elf32-arm.c (elf32_arm_filter_cmse_symbols): Likewise.\n\t(elf32_arm_filter_implib_symbols): Likewise.\n\t* elflink.c (elf_output_implib): Avoid unneccesary casts.\n\tCall elf_backend_filter_implib_symbols uncontitionally.\n\t* elfxx-target.h (elf_backend_filter_implib_symbols): Define\n\tfallback as _bfd_elf_filter_implib_symbols.\n" }, { "commit": "f9c26587f19ebfacc8c55caa72120833dad7ee45", "tree": "c8027258e96d6bce7c236accfda6ae19bd158e22", "parents": [ "8a676181f7b8e520c205c10b82d6b24a3a9cf431" ], "author": { "name": "Alan Modra", "email": "amodra@gmail.com", "time": "Sat Jun 06 11:06:40 2026 +0930" }, "committer": { "name": "Alan Modra", "email": "amodra@gmail.com", "time": "Sat Jun 06 11:06:40 2026 +0930" }, "message": "Drop output bfd param from many elf linker functions\n\nFunctions that are always passed a non-NULL bfd_link_info* and are not\ncalled by BFD_SEND using the output bfd, need not pass the output bfd\nas a parameter. It can be accessed via info-\u003eoutput_bfd. Removing\nthe excess parameters result in a small code size reduction on\nx86_64-linux --enable-targets\u003dall ld built with a static libbfd, from\n9896133 to 9893805 bytes.\n" }, { "commit": "8a676181f7b8e520c205c10b82d6b24a3a9cf431", "tree": "d15bb01b4b4ce9f58648bba303b395f2c2643c09", "parents": [ "f690b305d643b050b90fe75db462d5f7c608476e" ], "author": { "name": "Alan Modra", "email": "amodra@gmail.com", "time": "Sat Jun 06 11:05:45 2026 +0930" }, "committer": { "name": "Alan Modra", "email": "amodra@gmail.com", "time": "Sat Jun 06 11:05:45 2026 +0930" }, "message": "gas s_comm_internal uninitialised access\n\nAfter elf_common_parse calls ignore_rest_of_line on some errors,\ns_comm_internal calls demand_empty_rest_of_line. These functions\ncannot be both called, as they consume the end_of_stmt char in the\ninput buffer and the second call then consumes the next line of input,\nwhich may not even be in the input buffer.\n\n\t* config/obj-elf.c (elf_common_parse): Don\u0027t call\n\tignore_rest_of_line here.\n\t* read.c (ignore_rest_of_line): Expand comment.\n" }, { "commit": "f690b305d643b050b90fe75db462d5f7c608476e", "tree": "d2b45a667bcc2d4b1268699bcdaadcd9801f9faa", "parents": [ "18ad8c1a54d5d0e3fe3ff6c13f217e0dc840f991" ], "author": { "name": "GDB Administrator", "email": "gdbadmin@sourceware.org", "time": "Sat Jun 06 00:00:07 2026 +0000" }, "committer": { "name": "GDB Admin", "email": "brobecker@adacore.com", "time": "Sat Jun 06 00:00:07 2026 +0000" }, "message": "Automatic date update in version.in\n" }, { "commit": "18ad8c1a54d5d0e3fe3ff6c13f217e0dc840f991", "tree": "87a1372066ee1e1420faf7ac701b965de3b1a551", "parents": [ "aaa46d4b82956ba33c821d2833dd7041f6e138a6" ], "author": { "name": "Tom Tromey", "email": "tromey@adacore.com", "time": "Fri May 22 11:17:17 2026 -0600" }, "committer": { "name": "Tom Tromey", "email": "tromey@adacore.com", "time": "Fri Jun 05 15:11:26 2026 -0600" }, "message": "Emit DWARF expressions from dwarf-to-dwarf-assembler.py\n\nThis changes dwarf-to-dwarf-assembler.py to attempt to emit DWARF\nexpressions. It is not close to perfect, since it relies on the\nelftools formatting to some extent, but it does at least eliminate the\nneed to do a separate \"readelf\" step to try to work on the expression\nby hand.\n\n\n" }, { "commit": "aaa46d4b82956ba33c821d2833dd7041f6e138a6", "tree": "8f3744656d70ba605404596a8014053392d48466", "parents": [ "6c98b8bce9e5ef1d1d7753d834ee40b46be96609" ], "author": { "name": "Tom Tromey", "email": "tromey@adacore.com", "time": "Wed Apr 22 12:31:57 2026 -0600" }, "committer": { "name": "Tom Tromey", "email": "tromey@adacore.com", "time": "Fri Jun 05 15:09:09 2026 -0600" }, "message": "Use double quotes in some gdb output\n\nI looked for spots where gdb was using `...\u0027 or ``...\u0027\u0027 quoting, and\nchanged these to use double quotes instead.\n\nI think it might be good to regularize output quoting in gdb. My\nproposal is to use double quotes, though single quotes would also be\nfine. Using `...\u0027, though, is a kind of older style and has fallen\nout of favor in GNU; the relevant node is here:\n\n https://www.gnu.org/prep/standards/html_node/Quote-Characters.html\n\nBug: https://sourceware.org/bugzilla/show_bug.cgi?id\u003d34044\n\n\n\n" }, { "commit": "6c98b8bce9e5ef1d1d7753d834ee40b46be96609", "tree": "c9def0a209b2593641a41ca5f7e620eed0e70bb4", "parents": [ "6ea05a29486718bc4aff5865761b657a8253a1c4" ], "author": { "name": "Tom de Vries", "email": "tdevries@suse.de", "time": "Fri Jun 05 23:06:48 2026 +0200" }, "committer": { "name": "Tom de Vries", "email": "tdevries@suse.de", "time": "Fri Jun 05 23:06:48 2026 +0200" }, "message": "[gdb] Drop nullptr in \"get_selected_frame (nullptr)\"\n\nI came across \"get_selected_frame (nullptr)\", and realized nullptr is the\ndefault argument, so this can be simplified to \"get_selected_frame ()\".\n\nDo so using the following script:\n...\n$ find gdb* -type f -name \"*.[ch]\" -o -name \"*.cc\" \\\n | xargs sed -i \u0027s/get_selected_frame (nullptr)/get_selected_frame ()/\u0027\n...\nand likewise for \"get_selected_frame (NULL)\".\n\nTested on x86_64-linux.\n\nApproved-By: Tom Tromey \u003ctom@tromey.com\u003e\n" }, { "commit": "6ea05a29486718bc4aff5865761b657a8253a1c4", "tree": "b1948f6ab0248e1d2a68763a032229e0305d5d42", "parents": [ "eba7a4ccfb5e58e1701bcb22d4f5203804dd19b8" ], "author": { "name": "Tom de Vries", "email": "tdevries@suse.de", "time": "Fri Jun 05 23:03:42 2026 +0200" }, "committer": { "name": "Tom de Vries", "email": "tdevries@suse.de", "time": "Fri Jun 05 23:03:42 2026 +0200" }, "message": "[gdb/build] Fix Wnon-pod-varargs in bppy_repr\n\nI build gdb with clang and ran into a build breaker:\n...\ngdb/python/py-breakpoint.c:1074:52: error: cannot pass object of non-trivial \\\n type \u0027const std::string\u0027 (aka \u0027const basic_string\u003cchar\u003e\u0027) through variadic \\\n function; call will abort at runtime [-Wnon-pod-varargs]\n 1074 | return PyUnicode_FromFormat (\"\u003c%s (invalid)\u003e\", tp_name);\n | ^\n...\n\nThis looks like fallout from commit dafd73bcda6 (\"gdb/python: fix memory leak\nin gdb_py_tp_name\"), which changed the return type of gdbpy_py_obj_tp_name\nfrom const char * to std::string.\n\nWe could fix this using tp_name.c_str (), but instead fix this by simplifying\nthe code using gdb_py_invalid_object_repr.\n\nTested on x86_64-linux.\n\nApproved-By: Tom Tromey \u003ctom@tromey.com\u003e\n" }, { "commit": "eba7a4ccfb5e58e1701bcb22d4f5203804dd19b8", "tree": "a894a4eb7e722d8b7f112801e8f9927fc0251654", "parents": [ "17113bdf7c556b987c55b170acad223f24304298" ], "author": { "name": "Tom Tromey", "email": "tromey@adacore.com", "time": "Wed Jun 03 13:03:31 2026 -0600" }, "committer": { "name": "Tom Tromey", "email": "tromey@adacore.com", "time": "Fri Jun 05 14:51:13 2026 -0600" }, "message": "Add two new warnings to warning.m4\n\nI recently learned that GCC has improved -Wdangling-reference and\nadded -Wunterminated-string-initialization. Both of these seem\nsensible to me, so this patch adds them to warning.m4.\n\ngdb rebuilds cleanly with this in place on x86-64 Fedora 43.\n\nReviewed-By: Tom de Vries \u003ctdevries@suse.de\u003e\n" }, { "commit": "17113bdf7c556b987c55b170acad223f24304298", "tree": "33f73b46db56bb68d661a76204e93a121ead6eac", "parents": [ "3a5657bd3f26111214e70d3882150b06c9e45dff" ], "author": { "name": "Tom de Vries", "email": "tdevries@suse.de", "time": "Fri Jun 05 14:18:59 2026 +0200" }, "committer": { "name": "Tom de Vries", "email": "tdevries@suse.de", "time": "Fri Jun 05 14:18:59 2026 +0200" }, "message": "[gdb/testsuite] Add missing copyright notice in tclint-plugin.py\n\nI ran:\n...\n$ ./gdb/contrib/license-check-new-files.sh -s gdb-17-branchpoint HEAD\nScanning directories gdb*/...\ngdb/features/aarch64-fpmr.c: None\ngdb/features/aarch64-fpmr.xml: FSFAP-no-warranty-disclaimer\ngdb/syscalls/riscv-linux.xml: FSFAP\ngdb/syscalls/riscv-linux.xml.in: FSFAP-no-warranty-disclaimer\ngdb/testsuite/tclint-plugin.py: None\ngdbsupport/unordered_dense/stl.h: MIT\n...\nand found out that I forgot to add a copyright notice to\ngdb/testsuite/tclint-plugin.py.\n\nFix this by adding a copyright notice.\n" }, { "commit": "3a5657bd3f26111214e70d3882150b06c9e45dff", "tree": "035ad8611c956260d2d9cb33f0d8ffe1b4f6623f", "parents": [ "de7a82d53376d4652996e38090eccb0dcb9ad01a" ], "author": { "name": "Jan Beulich", "email": "jbeulich@suse.com", "time": "Fri Jun 05 11:12:00 2026 +0200" }, "committer": { "name": "Jan Beulich", "email": "jbeulich@suse.com", "time": "Fri Jun 05 11:12:00 2026 +0200" }, "message": "bfd/RISC-V: move _bfd_riscv_elf_merge_private_bfd_data()\n\nThe sole size dependent parameter used there is ARCH_SIZE. For just this\nthere\u0027s no good reason to build all of the involved code twice. Make the\nvalue a function parameter instead.\n\nReviewed-by: Jiawei \u003cjiawei@iscas.ac.cn\u003e\n" }, { "commit": "de7a82d53376d4652996e38090eccb0dcb9ad01a", "tree": "b8bb1088e0604834f8226a4069915d6c11534ba5", "parents": [ "952275b4a6c44fee709cb47236df9f604327d1d4" ], "author": { "name": "Jan Beulich", "email": "jbeulich@suse.com", "time": "Fri Jun 05 11:11:40 2026 +0200" }, "committer": { "name": "Jan Beulich", "email": "jbeulich@suse.com", "time": "Fri Jun 05 11:11:40 2026 +0200" }, "message": "RISC-V: drop dead code from subset parsing\n\nIn riscv_update_subset1(), when explicit_subset is NULL, errmsg_internal\nis the empty string. There\u0027s no need then to pass this as an extra\nargument to the error handler.\n\nriscv_parsing_subset_version() can\u0027t return NULL. Dropping the respective\nchecks clarifies that there is no issue with a missing error message (gas\nwould rely on one being emitted when parsing fails).\n\nReviewed-by: Jiawei \u003cjiawei@iscas.ac.cn\u003e\n" }, { "commit": "952275b4a6c44fee709cb47236df9f604327d1d4", "tree": "080aee59f905be1c9c086ef9af27fa96aaa8520a", "parents": [ "11cbe94d245c06313541e4e4c87745f74856d5dd" ], "author": { "name": "Jan Beulich", "email": "jbeulich@suse.com", "time": "Fri Jun 05 11:11:25 2026 +0200" }, "committer": { "name": "Jan Beulich", "email": "jbeulich@suse.com", "time": "Fri Jun 05 11:11:25 2026 +0200" }, "message": "RISC-V: avoid buffer underrun in subset parsing\n\nIn both instances \u0027p\u0027 can be the first character. Inspecting the character\nimmediately ahead of it is then UB.\n\nTo increase similarity between the two checks (each), also move the\nincrement of q past the check for the (bogus) \"\u003cnumber\u003ep\" ending.\n\nCorrect indentation in nearby code, where it being wrong is actively\nmisleading.\n\nReviewed-by: Jiawei \u003cjiawei@iscas.ac.cn\u003e\n" }, { "commit": "11cbe94d245c06313541e4e4c87745f74856d5dd", "tree": "045000094e8737580a91be02aa98ed37ffef61ef", "parents": [ "413cf36d8e816f8fbbe30d73e118416281c231e4" ], "author": { "name": "Jan Beulich", "email": "jbeulich@suse.com", "time": "Fri Jun 05 11:10:28 2026 +0200" }, "committer": { "name": "Jan Beulich", "email": "jbeulich@suse.com", "time": "Fri Jun 05 11:10:28 2026 +0200" }, "message": "RISC-V: error handling for subset parsing\n\nThe parsing of both the argument of -march\u003d and the operand(s) of\n\".option arch, ...\" can fail. In such a case for .option (and equally\nfor .attribute) prior state should continue to be used, while for -march\u003d\ndefaults should be put in place. In particular, extensions conflicting\nwith previously enabled extensions should not suddenly become available.\n\nWhile re-indenting riscv_set_rvc() invocations, leverage that C implies\nZca (and hence a check for the latter suffices). Mirror that change to\nriscv_set_arch() for consistency.\n\nReviewed-by: Jiawei \u003cjiawei@iscas.ac.cn\u003e\n" }, { "commit": "413cf36d8e816f8fbbe30d73e118416281c231e4", "tree": "6764e89b688bc51524c4e18d75b131bdb8beba4d", "parents": [ "aa04700525c30e140cdab646b72e31faa1608077" ], "author": { "name": "Jan Beulich", "email": "jbeulich@suse.com", "time": "Fri Jun 05 11:10:12 2026 +0200" }, "committer": { "name": "Jan Beulich", "email": "jbeulich@suse.com", "time": "Fri Jun 05 11:10:12 2026 +0200" }, "message": "RISC-V: riscv_parse_subset_t\u0027s isa_spec is only parser input\n\nMake the field pointer-to-const and drop indirection from\nriscv_get_default_ext_version(). This way it\u0027s more clear that parsing\nwon\u0027t alter the field.\n\nReviewed-by: Jiawei \u003cjiawei@iscas.ac.cn\u003e\n" }, { "commit": "aa04700525c30e140cdab646b72e31faa1608077", "tree": "d1f0c678aa3a5144908f4cd1444d8dae28e3cafb", "parents": [ "175c54561d4f9f5bae4064d0bdac5a228243589f" ], "author": { "name": "Jan Beulich", "email": "jbeulich@suse.com", "time": "Fri Jun 05 11:09:55 2026 +0200" }, "committer": { "name": "Jan Beulich", "email": "jbeulich@suse.com", "time": "Fri Jun 05 11:09:55 2026 +0200" }, "message": "RISC-V: riscv_set_arch() can fail\n\nIn that case neither riscv_rps_as.subset_list nor file_arch_str would be\nset, yet the NULL pointers would be happily passed into functions not\nexpecting such.\n\nReviewed-by: Jiawei \u003cjiawei@iscas.ac.cn\u003e\n" }, { "commit": "175c54561d4f9f5bae4064d0bdac5a228243589f", "tree": "b7080d5a5a2e4ab927bcd43e43d630f6a1ae59fa", "parents": [ "d573596275005ee7c003353e02a1198524889a4a" ], "author": { "name": "Jan Beulich", "email": "jbeulich@suse.com", "time": "Fri Jun 05 11:09:38 2026 +0200" }, "committer": { "name": "Jan Beulich", "email": "jbeulich@suse.com", "time": "Fri Jun 05 11:09:38 2026 +0200" }, "message": "RISC-V: match_*() improvements\n\nMatch functions referenced by macro insns should not\nunconditionally invoke match_opcode(): The macro enumeration can change\n(grow), making the function potentially yield false negatives.\n\nIn match_rs1_nonzero(), used solely by macro insns, add an assertion to\nthat effect.\n\nWhile there also drop the pointless attribute from\nmatch_rs1_nonzero_rs2_even()\u0027s first parameter.\n" }, { "commit": "d573596275005ee7c003353e02a1198524889a4a", "tree": "38ee9f460b6b48ebd566f1665dc334cc8baa1d94", "parents": [ "5a47f17d1d82edf037e156f921d0c4b3c37fce6a" ], "author": { "name": "Jan Beulich", "email": "jbeulich@suse.com", "time": "Fri Jun 05 11:09:18 2026 +0200" }, "committer": { "name": "Jan Beulich", "email": "jbeulich@suse.com", "time": "Fri Jun 05 11:09:18 2026 +0200" }, "message": "RISC-V: fold redundant code in riscv_ip()\n\nThe parsing of \u0027F\u0027 and \u0027O\u0027 .insn operands is pretty redundant. Have only a\nsingle instance each of common code, with the inner switch()es merely\nhandling the actual value insertion. This in particular simplifies the\naddition of new sub-forms.\n\nReviewed-by: Jiawei \u003cjiawei@iscas.ac.cn\u003e\n" }, { "commit": "5a47f17d1d82edf037e156f921d0c4b3c37fce6a", "tree": "cbbda7856634518c8f9c994c0bee78342ea6c483", "parents": [ "0bd641bceb683d1ca0768e8ce47d5a543451900a" ], "author": { "name": "Jan Beulich", "email": "jbeulich@suse.com", "time": "Fri Jun 05 11:08:48 2026 +0200" }, "committer": { "name": "Jan Beulich", "email": "jbeulich@suse.com", "time": "Fri Jun 05 11:08:48 2026 +0200" }, "message": "RISC-V: rename operand descriptor O4\n\nIt\u0027s describing a 7-bit field, so O7 is the more consistent (with other\nO\u003cn\u003e and F\u003cn\u003e) name. This way a subsequent change will also be a little\neasier.\n\nReviewed-by: Jiawei \u003cjiawei@iscas.ac.cn\u003e\n" }, { "commit": "0bd641bceb683d1ca0768e8ce47d5a543451900a", "tree": "b107ec5d5ad55277f0163f646d6c3b15452444b8", "parents": [ "9c8d2849382cca1cb24dc99a8b3da35cb2a334a6" ], "author": { "name": "Jan Beulich", "email": "jbeulich@suse.com", "time": "Fri Jun 05 11:08:14 2026 +0200" }, "committer": { "name": "Jan Beulich", "email": "jbeulich@suse.com", "time": "Fri Jun 05 11:08:14 2026 +0200" }, "message": "restore KVX maintainer\n\n... now that a new email address for Paul is known. This partly reverts\n1669d187cb4a (\u0027MAINTAINERS: move three people to \"Past Maintainers\"\u0027).\n" }, { "commit": "9c8d2849382cca1cb24dc99a8b3da35cb2a334a6", "tree": "7419588359caebd2eaade8b190b9f13e3682e907", "parents": [ "15363a3be77b71f9f15efbda91b9d247c031e20a" ], "author": { "name": "GDB Administrator", "email": "gdbadmin@sourceware.org", "time": "Fri Jun 05 00:00:08 2026 +0000" }, "committer": { "name": "GDB Admin", "email": "brobecker@adacore.com", "time": "Fri Jun 05 00:00:08 2026 +0000" }, "message": "Automatic date update in version.in\n" }, { "commit": "15363a3be77b71f9f15efbda91b9d247c031e20a", "tree": "13fb336e4a5b97cc1fe204bb12aca26e3f4f666d", "parents": [ "f08f36984176d9f22345b19f5c4fbe52f699a83f" ], "author": { "name": "Tom de Vries", "email": "tdevries@suse.de", "time": "Thu Jun 04 22:06:20 2026 +0200" }, "committer": { "name": "Tom de Vries", "email": "tdevries@suse.de", "time": "Thu Jun 04 22:06:20 2026 +0200" }, "message": "[gdb] Drop executable mode in some files\n\nDuring a review, Claude Code noticed that gdb/amd64-tdep.c has executable\nmode.\n\nThis was added by accident in commit f9aa48dc545 (\"gdb, amd64: extend the\namd64 prologue analyzer to skip register pushes\").\n\nFix this, and similar problems in other files.\n\nApproved-By: Simon Marchi \u003csimon.marchi@efficios.com\u003e\n" }, { "commit": "f08f36984176d9f22345b19f5c4fbe52f699a83f", "tree": "a62338cfd95e1a015c950a96c4ba379c93f244cc", "parents": [ "dafd73bcda60e9a54bdd43c79337dce452b1d8af" ], "author": { "name": "Simon Marchi", "email": "simon.marchi@efficios.com", "time": "Thu Jun 04 15:46:48 2026 -0400" }, "committer": { "name": "Simon Marchi", "email": "simon.marchi@efficios.com", "time": "Thu Jun 04 15:48:08 2026 -0400" }, "message": "gdb: z80: Guard against missing symtab in skip_prologue\n\nWith a Z80 ELF binary, \"break main\" crashes GDB internally.\n\"break *main\" works.\n\nThe crash happens in z80_skip_prologue after find_sal_for_pc returns\na symtab_and_line whose symtab is NULL. The code unconditionally calls:\n\n prologue_sal.symtab-\u003ecompunit()-\u003edebugformat()\n\n----- Backtrace -----\n0x6385f3c7fc41 gdb_internal_backtrace_1\n\t../../gdb/bt-utils.c:122\n0x6385f3c7fc41 _Z22gdb_internal_backtracev\n\t../../gdb/bt-utils.c:173\n0x6385f3dd2313 handle_fatal_signal\n\t../../gdb/event-top.c:1008\n0x6385f3dd28b9 handle_sigsegv\n\t../../gdb/event-top.c:1085\n0x757e7704532f ???\n\t./signal/../sysdeps/unix/sysv/linux/x86_64/libc_sigaction.c:0\n0x6385f40f8207 _ZNK15compunit_symtab11debugformatEv\n\t../../gdb/symtab.h:1857\n0x6385f40f8207 z80_skip_prologue\n\t../../gdb/z80-tdep.c:499\n0x6385f3c250bc _Z30gdbarch_skip_prologue_noexceptP7gdbarchm\n\t../../gdb/arch-utils.c:1046\n0x6385f3ff46f5 _Z17skip_prologue_salP15symtab_and_line\n\t../../gdb/symtab.c:3765\n0x6385f3ff4bba find_function_start_sal_1\n\t../../gdb/symtab.c:3538\n0x6385f3ff4c83 _Z23find_function_start_salmP11obj_sectionb\n\t../../gdb/symtab.c:3549\n0x6385f3e73c9e minsym_found\n\t../../gdb/linespec.c:4078\n0x6385f3e73c9e convert_linespec_to_sals\n\t../../gdb/linespec.c:2290\n0x6385f3e755f8 parse_linespec\n\t../../gdb/linespec.c:2655\n0x6385f3e76d35 location_spec_to_sals\n\t../../gdb/linespec.c:3053\n0x6385f3e771b0 _Z16decode_line_fullP13location_speciP13program_spaceP6symtabiP15linespec_resultPKcS8_\n\t../../gdb/linespec.c:3129\n0x6385f3c671d3 parse_breakpoint_sals\n\t../../gdb/breakpoint.c:9084\n0x6385f3c6b490 _Z17create_breakpointP7gdbarchP13location_specPKciiS4_bii6bptypei12auto_booleanPK14breakpoint_opsiiij\n\t../../gdb/breakpoint.c:9319\n0x6385f3c6be42 break_command_1\n\t../../gdb/breakpoint.c:9478\n0x6385f3cbe834 _Z8cmd_funcP16cmd_list_elementPKci\n\t../../gdb/cli/cli-decode.c:2810\n0x6385f4047c44 _Z15execute_commandPKci\n\t../../gdb/top.c:632\n0x6385f3dd3158 _Z15command_handlerPKc\n\t../../gdb/event-top.c:611\n0x6385f3dd4b60 _Z20command_line_handlerOSt10unique_ptrIcN3gdb13xfree_deleterIcEEE\n\t../../gdb/event-top.c:844\n0x6385f3dd3d74 gdb_rl_callback_handler\n\t../../gdb/event-top.c:288\n0x6385f41173e8 rl_callback_read_char\n\t../../../readline/readline/callback.c:302\n0x6385f3dd3eed gdb_rl_callback_read_char_wrapper_sjlj\n\t../../gdb/event-top.c:197\n0x6385f3dd40b3 gdb_rl_callback_read_char_wrapper_noexcept\n\t../../gdb/event-top.c:240\n0x6385f3dd40b3 gdb_rl_callback_read_char_wrapper\n\t../../gdb/event-top.c:252\n0x6385f4085c8f stdin_event_handler\n\t../../gdb/ui.c:161\n0x6385f41d7f85 gdb_wait_for_event\n\t../../gdbsupport/event-loop.cc:694\n0x6385f41d87e1 _Z16gdb_do_one_eventi\n\t../../gdbsupport/event-loop.cc:263\n0x6385f3e8be39 _ZN6interp12do_one_eventEi\n\t../../gdb/interps.h:90\n0x6385f3e8be39 start_event_loop\n\t../../gdb/main.c:400\n0x6385f3e8be39 captured_command_loop\n\t../../gdb/main.c:465\n0x6385f3e8e2c4 captured_main\n\t../../gdb/main.c:1373\n0x6385f3e8e2c4 _Z8gdb_mainP18captured_main_args\n\t../../gdb/main.c:1392\n0x6385f3bbf5bb main\n\t../../gdb/gdb.c:38\n---------------------\nA fatal error internal to GDB has been detected, further\ndebugging is not possible. GDB will now terminate.\n\nHow to reproduce:\n z80-...-gdb hello.elf\n (gdb) break main\n\nExpected:\nGDB should either set the breakpoint or fall back gracefully.\n\nActual:\nGDB terminates with an internal segmentation fault.\n\nTested fix:\nAdding null check for prologue_sal.symtab prevents the crash.\n\nChange-Id: Iaaf0e1602127de08b85b3ed18e3c4877c89b8efd\nApproved-By: Simon Marchi \u003csimon.marchi@efficios.com\u003e\n" }, { "commit": "dafd73bcda60e9a54bdd43c79337dce452b1d8af", "tree": "4053039ae848a1997a543474a5dc3d78babce65e", "parents": [ "fc7126f8630423ce0224f83e2688fd14fc01d2b7" ], "author": { "name": "Matthieu Longo", "email": "matthieu.longo@arm.com", "time": "Tue May 26 11:46:29 2026 +0100" }, "committer": { "name": "Matthieu Longo", "email": "matthieu.longo@arm.com", "time": "Thu Jun 04 15:09:54 2026 +0100" }, "message": "gdb/python: fix memory leak in gdb_py_tp_name\n\nThe current implementation of gdb_py_tp_name() leaks a reference to the\nobject returned by PyType_GetFullyQualifiedName() for Python \u003e\u003d 3.13, and\nPyType_GetQualName() for Python \u003e\u003d 3.11.\n\nManaging the strong reference on the returned PyObject* with a gdbpy_ref\u003c\u003e\nfixes the reference count, but also causes the temporary object to be\ndeallocated on function exit. As a consequence, the \u0027const char *\u0027 returned\nby PyUnicode_AsUTF8AndSize() becomes dangling and can no longer safely be\nreturned.\n\nThe proposed approach consists in changing gdb_py_tp_name() to return a\nstd::string, and forcing a copy of the \u0027const char *\u0027 value, statically\nor dynamically allocated, stored in a temporary or non-temporary PyObject,\ndepending on the version of Python it was compiled with.\nAn unfortunate side effect of this fix is that every call sites where the\ntp_name is printed, must now use `.c_str()\u0027 because PyErr_Format()\nand its siblings cannot handle std::string.\n\nApproved-By: Andrew Burgess \u003caburgess@redhat.com\u003e\n" }, { "commit": "fc7126f8630423ce0224f83e2688fd14fc01d2b7", "tree": "395ad524aa018960a83e061a2e540a0170ffea4d", "parents": [ "bd64797371d27c766d551d0bf115d9090f1d0594" ], "author": { "name": "Jon Turney", "email": "jon.turney@dronecode.org.uk", "time": "Fri May 22 13:43:15 2026 +0100" }, "committer": { "name": "Jon Turney", "email": "jon.turney@dronecode.org.uk", "time": "Thu Jun 04 13:00:35 2026 +0100" }, "message": "ld: Drop pep-dll-{aarch64,x86_64}.c\n\nWhen configuring with\n\u0027--enable-targets\u003dx86_64-w64-mingw32,aarch64-w64-mingw32\u0027, many\nduplicate symbol errors are produced:\n\n\u003e /usr/lib/gcc/x86_64-pc-cygwin/16/../../../../x86_64-pc-cygwin/bin/ld: pep-dll-aarch64.o: in function `pep_dll_id_target\u0027:\n\u003e /wip/binutils-gdb/build/ld/../../ld/pe-dll.c:493: multiple definition of `pep_dll_id_target\u0027; pep-dll.o:/wip/binutils-gdb/build/ld/../../ld/pe-dll.c:493: first defined here\n\u003e /usr/lib/gcc/x86_64-pc-cygwin/16/../../../../x86_64-pc-cygwin/bin/ld: pep-dll-aarch64.o: in function `pep_dll_add_excludes\u0027:\n\u003e /wip/binutils-gdb/build/ld/../../ld/pe-dll.c:586: multiple definition of `pep_dll_add_excludes\u0027; pep-dll.o:/wip/binutils-gdb/build/ld/../../ld/pe-dll.c:586: first defined here\n\u003e /usr/lib/gcc/x86_64-pc-cygwin/16/../../../../x86_64-pc-cygwin/bin/ld: pep-dll-aarch64.o: in function `pep_find_data_imports\u0027:\n\u003e /wip/binutils-gdb/build/ld/../../ld/pe-dll.c:1444: multiple definition of `pep_find_data_imports\u0027; pep-dll.o:/wip/binutils-gdb/build/ld/../../ld/pe-dll.c:1444: first defined here\n\u003e /usr/lib/gcc/x86_64-pc-cygwin/16/../../../../x86_64-pc-cygwin/bin/ld: pep-dll-aarch64.o: in function `pep_dll_generate_def_file\u0027:\n\u003e /wip/binutils-gdb/build/ld/../../ld/pe-dll.c:1877: multiple definition of `pep_dll_generate_def_file\u0027; pep-dll.o:/wip/binutils-gdb/build/ld/../../ld/pe-dll.c:1877: first defined here\n\u003e /usr/lib/gcc/x86_64-pc-cygwin/16/../../../../x86_64-pc-cygwin/bin/ld: pep-dll-aarch64.o: in function `pep_create_import_fixup\u0027:\n\u003e etc.\n\nOn investigation, this is unsurprising, since we\u0027re compiling the same code twice. In\nfact, configure.tgt has:\n\n\u003e arch64-*-pe* | aarch64-*-mingw*)\n\u003e targ_extra_ofiles\u003d\"deffilep.o pep-dll-aarch64.o pe-dll.o pdb.o\"\n\u003e x86_64-*-pe | x86_64-*-pep) targ_emul\u003di386pep ;\n\u003e targ_extra_ofiles\u003d\"deffilep.o pdb.o pep-dll-x86_64.o pe-dll.o\"\n\u003e x86_64-*-cygwin) targ_emul\u003di386pep ;\n\u003e targ_extra_ofiles\u003d\"deffilep.o pdb.o pep-dll.o pe-dll.o\"\n\u003e x86_64-*-mingw*) targ_emul\u003di386pep ;\n\u003e targ_extra_ofiles\u003d\"deffilep.o pdb.o pep-dll.o pe-dll.o\"\n\n... so we\u0027re potentially including pep-dll.c compiled under three\ndifferent names!\n\nI can\u0027t see anything in pe{,p}-dll.c which depends on the\nCOFF_WITH_peAArch64 or COFF_WITH_pex64 defines, so just remove all this.\n\n(Neither pep-dll-aarch64.o or pep-dll-x86_64.o are listed in\nALL_EMUL_EXTRA_OFILES, so this multiple definition problem doesn\u0027t show\nup when configured --enable-targets\u003dall\u0027, but this seems like another\nsource of subtle bugs if those defines did do anything here...)\n\nCc\u0027ed Evgeny (Hi!), because I think this crosses with not-yet-submitted\npatches of his which do add some code conditional on COFF_WITH_peAArch64.\n\nI imagine it\u0027s possible in code which *does* need to depend on the\noutput target to replace build time checks of COFF_WITH_pe{AArch64,x64}\nwith a runtime check of the output architecture (via\npe_details-\u003epe_arch?).\n\nCc: Evgeny Karpov \u003cevgeny.karpov@arm.com\u003e\nFixes: c60b3806799a (\"aarch64-pe support for LD, GAS and BFD\")\nSigned-off-by: Jon Turney \u003cjon.turney@dronecode.org.uk\u003e\n\n2026-05-29 Jon Turney \u003cjon.turney@dronecode.org.uk\u003e\n\n\t* Makefile.am (EXTRA_ld_new_SOURCES): Update.\n\t* Makefile.in: Regenerate.\n\t* configure.tgt (tar_extra_ofiles): Update.\n\t* pep-dll-aarch64.c: Remove.\n\t* pep-dll-x86_64.c: Remove.\n" }, { "commit": "bd64797371d27c766d551d0bf115d9090f1d0594", "tree": "525cf35a20d224232f183f7f67b741611c74befc", "parents": [ "48997323b0f929d3255a4845f8a3800c6c00a53a" ], "author": { "name": "Andrew Burgess", "email": "aburgess@redhat.com", "time": "Tue May 19 16:21:58 2026 +0100" }, "committer": { "name": "Andrew Burgess", "email": "aburgess@redhat.com", "time": "Thu Jun 04 10:33:10 2026 +0100" }, "message": "gdb/frame: add FRAME_SCOPED_DEBUG_START_END\n\nAdd the FRAME_SCOPED_DEBUG_START_END macro, and make use of it in a\ncouple of places.\n\nI find the frame debug output a little noisy, and it could be easier\nto match up the entry/exit lines, by making use of\nFRAME_SCOPED_DEBUG_START_END to print the frame level.\n\nWhile I was adding the FRAME_SCOPED_DEBUG_START_END calls, there were\na couple of places where I also moved a variable declaration from the\ntop the a function into the function body. And in another couple of\nplaces there was some debug output that could be removed, where the\nexisting debug just printed the frame level (this is now handled by\nthe START/END macro).\n\nThere should be no user visible changes after this commit unless \u0027set\ndebug frame on\u0027 is used of course.\n\nApproved-By: Tom Tromey \u003ctom@tromey.com\u003e\n" }, { "commit": "48997323b0f929d3255a4845f8a3800c6c00a53a", "tree": "0d31e7619fbefdc84da9a58ee8e69fe09aad1f33", "parents": [ "f8b82c843a960020c493111385b8c5728c20eac9" ], "author": { "name": "zhaozhou", "email": "zhaozhou@loongson.cn", "time": "Mon May 25 16:32:49 2026 +0800" }, "committer": { "name": "mengqinggang", "email": "mengqinggang@loongson.cn", "time": "Thu Jun 04 09:52:37 2026 +0800" }, "message": "LoongArch: Remove local hidden symbols testscase\n\nRemove the local symbol ldh definitions with hidden visibility from the\nrelax-call36-*.s tests. The hidden visibility is meaningless for local\ndefined symbols and makes the test cases error.\n" }, { "commit": "f8b82c843a960020c493111385b8c5728c20eac9", "tree": "8cf1fa2e12bb1bd48e309142cb909800a1074fc8", "parents": [ "f15bef31373c4e84c678935f8fcf4d0aff1cff0f" ], "author": { "name": "Xi Ruoyao", "email": "xry111@xry111.site", "time": "Fri May 15 01:13:58 2026 +0800" }, "committer": { "name": "mengqinggang", "email": "mengqinggang@loongson.cn", "time": "Thu Jun 04 09:51:24 2026 +0800" }, "message": "ld: enable elf32loongarch as extra target for elf64loongarch and vice versa\n\nAllow people to build GCC with multilib support even without\n--enable-targets\u003dall in binutils configuration.\n" }, { "commit": "f15bef31373c4e84c678935f8fcf4d0aff1cff0f", "tree": "0580e9a220bf035651aaa591d09122e524bed4ec", "parents": [ "bab15b5051f99ae731097fccb41aa5755827f517" ], "author": { "name": "GDB Administrator", "email": "gdbadmin@sourceware.org", "time": "Thu Jun 04 00:00:07 2026 +0000" }, "committer": { "name": "GDB Admin", "email": "brobecker@adacore.com", "time": "Thu Jun 04 00:00:07 2026 +0000" }, "message": "Automatic date update in version.in\n" }, { "commit": "bab15b5051f99ae731097fccb41aa5755827f517", "tree": "ace311c94e81ba80827be9f2055b1d7dab2edcb0", "parents": [ "51211b2bfbed5fb17d6478b80157ff3001e36b40" ], "author": { "name": "Alan Modra", "email": "amodra@gmail.com", "time": "Thu Jun 04 07:53:47 2026 +0930" }, "committer": { "name": "Alan Modra", "email": "amodra@gmail.com", "time": "Thu Jun 04 07:53:47 2026 +0930" }, "message": "elf_merge_st_other\n\nThis fixes a potential problem with merging non-visibility bits in\nst_other. Non-visibilty bits in st_other have an architecture\ndependent meaning, so they cannot just be copied from a foreign ELF\nobject file. I think the safest thing to do in this situation is\nignore non-visibility st_other bits. That\u0027s what this patch does.\n\n\tPR 34062\n\t* elflink.c (elf_merge_st_other): Replace abfd param with\n\tobfd and ibfd parameters. Do not call\n\telf_backend_merge_symbol_attribute when input xvec differs\n\tfrom output xvec.\n\t(_bfd_elf_merge_symbol, _bfd_elf_add_default_symbol),\n\t(elf_link_add_object_symbols),\n\t(_bfd_elf_copy_link_hash_symbol_type): Pass both output bfd\n\tand input bfd to elf_merge_st_other.\n" }, { "commit": "51211b2bfbed5fb17d6478b80157ff3001e36b40", "tree": "983fc5f192be94fd0e591b9908a596a8e836e9cb", "parents": [ "054fe087c7ed53fe987bc55353a2164bc2532d0f" ], "author": { "name": "Alan Modra", "email": "amodra@gmail.com", "time": "Thu Jun 04 07:52:44 2026 +0930" }, "committer": { "name": "Alan Modra", "email": "amodra@gmail.com", "time": "Thu Jun 04 07:52:44 2026 +0930" }, "message": "elflink.c: rename abfd and bed\n\nThis renames \"abfd\" function parameters to \"obfd\" when that parameter\nis always the output bfd, and to \"dynobj\" when it is always the input\nobject used to attach dynamic sections. \"bed\" variables which are set\nto the output bfd or dynobj backend data are renamed to \"obed\". (The\ndynobj xvec must be the same as the output xvec, or bad things\nhappen.) The idea is to make the use of bfd* parameter a little more\nobvious when reading the source.\n" }, { "commit": "054fe087c7ed53fe987bc55353a2164bc2532d0f", "tree": "2d58cd294f6b42e5a34a9966bec6d74b3beda984", "parents": [ "663cb9c0428068165fc98675599442163d302d41" ], "author": { "name": "Alan Modra", "email": "amodra@gmail.com", "time": "Tue Jun 02 20:06:15 2026 +0930" }, "committer": { "name": "Alan Modra", "email": "amodra@gmail.com", "time": "Wed Jun 03 21:34:16 2026 +0930" }, "message": "spu: .note.spu_name\n\nThis fixes a bug with the .note.spu_name section flags, which were\nmade SEC_LOAD without SEC_ALLOC. That combination doesn\u0027t really make\nsense and led to odd layout behaviour. In addition .note.spu_name\nnow uses the normal note alignment, with some tweaks to keep its file\noffset 16 byte aligned. This tends to work better in the testsuite\nwhen the standard scripts are not used and the note is merged with\nother notes.\n\nbfd/\n\t* elf32-spu.c (spu_elf_create_sections): Remove SEC_LOAD from\n\t.note.spu_name, and align to 4 bytes.\n\t(spu_elf_fake_sections): Tweak .note.spu_name output section\n\talignment for layout.\n\t(spu_elf_final_write_processing): New function.\n\t(elf_backend_final_write_processing): Define.\nbinutils/\n\t* testsuite/binutils-all/objcopy.exp (pr25662): Don\u0027t xfail spu.\nld/\n\t* testsuite/ld-elf/orphan-region.d: Don\u0027t xfail spu.\n\t* testsuite/ld-elf/pr23658-1e.d: Likewise.\n\t* testsuite/ld-scripts/provide-8.d: Likewise.\n\t* testsuite/ld-spu/ovl.d: Remove commented out old matches.\n\tAdjust expected overlay file offset.\n\t* testsuite/ld-spu/ovl2.d: Likewise.\n" }, { "commit": "663cb9c0428068165fc98675599442163d302d41", "tree": "ada119766c02fba33bb37884d01c82dc630afed7", "parents": [ "22e21551bd7eb2fe14cdebfb4d89d51e5d93b7dd" ], "author": { "name": "Andrew Burgess", "email": "aburgess@redhat.com", "time": "Tue Jun 02 15:34:36 2026 +0100" }, "committer": { "name": "Andrew Burgess", "email": "aburgess@redhat.com", "time": "Wed Jun 03 09:22:57 2026 +0100" }, "message": "gdb: handle missing arguments to \u0027maint test-remote-args\u0027\n\nI noticed that the \u0027maint test-remote-args\u0027 command, implemented by\nthe test_remote_args_command function in remote.c, contains this code:\n\n static void\n test_remote_args_command (const char *args, int from_tty)\n {\n std::vector\u003cstd::string\u003e split_args \u003d gdb::remote_args::split (args);\n ... etc ...\n\nThe problem here is that gdb::remote_args::split expects a std::string,\nand so ends up creating a std::string from ARGS. However, ARGS can be\nNULL, e.g. if a user does this:\n\n (gdb) maint test-remote-args\n\nThis ends up creating a std::string from a NULL pointer, which is\nundefined behaviour.\n\nFix this by adding a check to test_remote_args_command, and throwing\nan error if ARGS is NULL. Add a new test to verify this case.\n\nAdditionally, fix a typo in the header comment for\ntest_remote_args_command.\n\nApproved-By: Tom Tromey \u003ctom@tromey.com\u003e\n" }, { "commit": "22e21551bd7eb2fe14cdebfb4d89d51e5d93b7dd", "tree": "c528fbd720b5e88b553565514e21425dd77ae036", "parents": [ "ad6e2895e419d17ffa0803e69a89db12b5b75298" ], "author": { "name": "GDB Administrator", "email": "gdbadmin@sourceware.org", "time": "Wed Jun 03 00:00:08 2026 +0000" }, "committer": { "name": "GDB Admin", "email": "brobecker@adacore.com", "time": "Wed Jun 03 00:00:08 2026 +0000" }, "message": "Automatic date update in version.in\n" }, { "commit": "ad6e2895e419d17ffa0803e69a89db12b5b75298", "tree": "587bded50818b5ed685d4917f051b59b1906bf2a", "parents": [ "07016199820d9593acec22641153fc5ddbd7cbc1" ], "author": { "name": "Alan Modra", "email": "amodra@gmail.com", "time": "Tue Jun 02 15:25:52 2026 +0930" }, "committer": { "name": "Alan Modra", "email": "amodra@gmail.com", "time": "Tue Jun 02 20:06:52 2026 +0930" }, "message": "ld: run build-id test on more elf targets\n" }, { "commit": "07016199820d9593acec22641153fc5ddbd7cbc1", "tree": "f480a8ac90d1701ce58df6829a61e2b825028636", "parents": [ "ec6bbd2e0cb4d141db9048b0b5d5c0bcaa66c284" ], "author": { "name": "GDB Administrator", "email": "gdbadmin@sourceware.org", "time": "Tue Jun 02 00:00:07 2026 +0000" }, "committer": { "name": "GDB Admin", "email": "brobecker@adacore.com", "time": "Tue Jun 02 00:00:07 2026 +0000" }, "message": "Automatic date update in version.in\n" }, { "commit": "ec6bbd2e0cb4d141db9048b0b5d5c0bcaa66c284", "tree": "c160a1a499b0cc4a532be70c8d70c4014e0ad38a", "parents": [ "56d1cb796fa05735d71b7a5a29d73642b70fc96e" ], "author": { "name": "Ezra Sitorus", "email": "ezra.sitorus@arm.com", "time": "Mon Jun 01 23:36:46 2026 +0100" }, "committer": { "name": "Ezra Sitorus", "email": "ezra.sitorus@arm.com", "time": "Mon Jun 01 23:36:46 2026 +0100" }, "message": "gdb/aarch64: record/replay support for LRCPC3\n\nFEAT_LRCPC3 introduces various load/store instructions with release\nconsistency for cases where ordering is required. This patch teaches GDB\nto decode these instructions for recording and reversing.\n\nThe gdb.reverse/aarch64-lrcpc3.exp testcase verifies that the\ninstructions are recorded and correctly reversed. In particular, there\nare some interesting cases to note:\n* ldapur/stlur are SIMD instructions, but are not decoded in the simd\n function.\n* There are writeback cases to cover too. These were taken from the\n binutils testcases: gas/testsuite/gas/aarch64/rcpc3.s.\n\nThe full testsuite was done on aarch64-none-linux-gnu without LRCPC3.\nThe gdb.arch and gdb.reverse tests were run on Shrinkwrap with LRCPC3\nsupport.\n\nPlease note:\n1) There is no support for LRCPC and LRCPC2 instructions\n2) LRCPC3 is gated with +rcpc3 in GCC/binutils and LLVM.\n\nApproved-by: Thiago Jung Bauermann \u003cthiago.bauermann@linaro.org\u003e\n" }, { "commit": "56d1cb796fa05735d71b7a5a29d73642b70fc96e", "tree": "d4ee56dac0827e161851e29abd766e037abe4b5e", "parents": [ "022e48d59804c1178c91600b6d45dfa1e04d96e7" ], "author": { "name": "Tom de Vries", "email": "tdevries@suse.de", "time": "Mon Jun 01 20:14:37 2026 +0200" }, "committer": { "name": "Tom de Vries", "email": "tdevries@suse.de", "time": "Mon Jun 01 20:14:37 2026 +0200" }, "message": "[gdb] Remove \u0027/**\u003c\u0027 comment marker\n\nAnother comment marker doxygen supports is \"/**\u003c\". Replace it with \"/*\".\n\nSuggested-By: Kevin Buettner \u003ckevinb@redhat.com\u003e\nApproved-By: Tom Tromey \u003ctom@tromey.com\u003e\n\nBug: https://sourceware.org/bugzilla/show_bug.cgi?id\u003d34186\n" }, { "commit": "022e48d59804c1178c91600b6d45dfa1e04d96e7", "tree": "0e7c5e6145c4e4e17a1fa6d134ba12fd6e3e6338", "parents": [ "94e356ac49f3ffbfb4653372750f9f80d4c0db66" ], "author": { "name": "Tom de Vries", "email": "tdevries@suse.de", "time": "Mon Jun 01 20:14:37 2026 +0200" }, "committer": { "name": "Tom de Vries", "email": "tdevries@suse.de", "time": "Mon Jun 01 20:14:37 2026 +0200" }, "message": "[gdb] Remove \\page marker\n\nRemove doxygen \\page marker in gdb/gdbtypes.h.\n\nApproved-By: Kevin Buettner \u003ckevinb@redhat.com\u003e\nApproved-By: Tom Tromey \u003ctom@tromey.com\u003e\n\nBug: https://sourceware.org/bugzilla/show_bug.cgi?id\u003d34186\n" }, { "commit": "94e356ac49f3ffbfb4653372750f9f80d4c0db66", "tree": "36be7829e2aa72ada3ba5b2e83a8e31596fb9db9", "parents": [ "79f06b25a4158d2f6bb81392bcfadfad9ed04f42" ], "author": { "name": "Tom de Vries", "email": "tdevries@suse.de", "time": "Mon Jun 01 20:14:37 2026 +0200" }, "committer": { "name": "Tom de Vries", "email": "tdevries@suse.de", "time": "Mon Jun 01 20:14:37 2026 +0200" }, "message": "[gdb] Remove \u0027/* *\u0027 multi-line comment marker\n\nDoxygen supports a multi-line comment marker \u0027/**\u0027. In GDB we\u0027re using\nsomething slightly similar: \u0027/* *\u0027 [1].\n\nDrop this and just use \u0027/*\u0027.\n\nResult of:\n...\n$ find gdb* -type f -name \"*.[ch]\" -o -name \"*.def\" \\\n | egrep -v /testsuite/ \\\n | xargs sed -i \u0027s%/\\* \\* %/* %\u0027\n...\nand manually reverting the change in the comment for BINOP_MUL in\ngdb/std-operator.def.\n\nBug: https://sourceware.org/bugzilla/show_bug.cgi?id\u003d34186\n\nApproved-By: Kevin Buettner \u003ckevinb@redhat.com\u003e\nApproved-By: Tom Tromey \u003ctom@tromey.com\u003e\n\n[1] https://sourceware.org/gdb/wiki/DoxygenForGDB\n" }, { "commit": "79f06b25a4158d2f6bb81392bcfadfad9ed04f42", "tree": "d1dd734b99fc1572b1aada074c4652c5d6137360", "parents": [ "909db30adab1688870e978c85d014d4a36641f4e" ], "author": { "name": "Tom de Vries", "email": "tdevries@suse.de", "time": "Mon Jun 01 20:14:37 2026 +0200" }, "committer": { "name": "Tom de Vries", "email": "tdevries@suse.de", "time": "Mon Jun 01 20:14:37 2026 +0200" }, "message": "[gdb/doc] Remove doxygen support\n\nWe have some form of doxygen support, allowing to run \"make doxy\" in\nbuild/gdb/doc, but in the result I didn\u0027t find any references to gdbsupport\n(moved to top-level in 2019), so I\u0027m assuming this is unmaintained for a long\ntime now.\n\nRemove it.\n\nReviewed-by: Kevin Buettner \u003ckevinb@redhat.com\u003e\nApproved-By: Tom Tromey \u003ctom@tromey.com\u003e\n\nBug: https://sourceware.org/bugzilla/show_bug.cgi?id\u003d34186\n" }, { "commit": "909db30adab1688870e978c85d014d4a36641f4e", "tree": "985a0670088ef81c2eac104f90212d45366724dd", "parents": [ "48e2cc4f25491becead62276a39d30aa201166ef" ], "author": { "name": "Tom Tromey", "email": "tromey@adacore.com", "time": "Fri May 22 09:54:11 2026 -0600" }, "committer": { "name": "Tom Tromey", "email": "tromey@adacore.com", "time": "Mon Jun 01 08:17:41 2026 -0600" }, "message": "Convert dw2-const.exp to use the DWARF assembler\n\nThis patch converts dw2-const.exp to use the DWARF assembler rather\nthan a .S file. The conversion was largely done using the script from\ncontrib.\n\nFollowing a suggestion from Tom de Vries, this version sets addr_size\nto 8. This makes the test pass with -m32 as well.\n\nApproved-By: Tom de Vries \u003ctdevries@suse.de\u003e\n" }, { "commit": "48e2cc4f25491becead62276a39d30aa201166ef", "tree": "1c250216b73a23cb845a742b6357ad064b2c44fd", "parents": [ "198d9054c3256a1b614e842a3c9760875a4dbcc3" ], "author": { "name": "Tom de Vries", "email": "tdevries@suse.de", "time": "Mon Jun 01 14:53:36 2026 +0200" }, "committer": { "name": "Tom de Vries", "email": "tdevries@suse.de", "time": "Mon Jun 01 14:53:36 2026 +0200" }, "message": "[gdb/contrib] Add missing copyright notices\n\nI found a few files in gdb/contrib that were missing a copyright notice.\n\nIn codespell-ignore-words.txt, it was trivial to add, but I found a\ncodespell issue stating that it\u0027s not explicitly support, so I added a note\nabout that.\n\nIn codespell-dictionary.txt, I had to resort to a hack, using an \"empty word\"\nrewrite rule:\n...\n-\u003e# Comment here.\n...\n\nAlso, I found that empty lines are not allowed in codespell-dictionary.txt. I\nfiled an issue about these two problems [1].\n\nSince these two files were added in 2025, I\u0027ve used 2025-2026 as copyright\nyears.\n\nTested by running \"pre-commit run --all-files\".\n\n[1] https://github.com/codespell-project/codespell/issues/3901\n" }, { "commit": "198d9054c3256a1b614e842a3c9760875a4dbcc3", "tree": "b298662f3327bdb625ecc288368a91b31b56a269", "parents": [ "9ce6a00d6717771321979d7d1cd56097f32a8e16" ], "author": { "name": "Tom de Vries", "email": "tdevries@suse.de", "time": "Mon Jun 01 14:33:48 2026 +0200" }, "committer": { "name": "Tom de Vries", "email": "tdevries@suse.de", "time": "Mon Jun 01 14:33:48 2026 +0200" }, "message": "[pre-commit] Make gdb/doc codespell-clean\n\nFix typos in gdb/doc and replace \"SME\" with \"sme\" in\ngdb/contrib/codespell-ignore-words.txt, and add \"wither\" and \"stap\".\n" } ], "next": "9ce6a00d6717771321979d7d1cd56097f32a8e16" }