riscv-gnu-toolchain/gdb.git - Unnamed repository; edit this file 'description' to name the repository.

Age	Commit message (Collapse)	Author	Files	Lines
2021-11-17	Automatic date update in version.in	GDB Administrator	1	-1/+1

2021-11-16	Automatic date update in version.in	GDB Administrator	1	-1/+1

2021-11-15	Automatic date update in version.in	GDB Administrator	1	-1/+1

2021-11-14	Automatic date update in version.in	GDB Administrator	1	-1/+1

2021-11-13	Automatic date update in version.in	GDB Administrator	1	-1/+1

2021-11-12	Automatic date update in version.in	GDB Administrator	1	-1/+1

2021-11-11	Automatic date update in version.in	GDB Administrator	1	-1/+1

2021-11-10	Automatic date update in version.in	GDB Administrator	1	-1/+1

2021-11-09	Fix build on rhES5	Tom Tromey	8	-0/+69
	The rhES5 build failed due to an upstream import a while back. The bug here is that, while the 'personality' function exists, ADDR_NO_RANDOMIZE is only defined in <linux/personality.h>, not <sys/personality.h>. However, <linux/personality.h> does not declare the 'personality' function, and <sys/personality.h> and <linux/personality.h> cannot both be included. This patch restores one of the removed configure checks and updates the code to check it. We had this as a local patch at AdaCore, because it seemed like there was no interest upstream. However, now it turns out that this fixes PR build/28555, so I'm sending it now.
2021-11-09	Automatic date update in version.in	GDB Administrator	1	-1/+1

2021-11-08	Automatic date update in version.in	GDB Administrator	1	-1/+1

2021-11-07	Automatic date update in version.in	GDB Administrator	1	-1/+1

2021-11-06	Automatic date update in version.in	GDB Administrator	1	-1/+1

2021-11-05	Automatic date update in version.in	GDB Administrator	1	-1/+1

2021-11-04	Automatic date update in version.in	GDB Administrator	1	-1/+1

2021-11-03	[AArch64] Make gdbserver register set selection dynamic	Luis Machado	4	-85/+130
	The current register set selection mechanism for AArch64 is static, based on a pre-populated array of register sets. This means that we might potentially probe register sets that are not available. This is OK if the kernel errors out during ptrace, but probing the tag_ctl register, for example, does not result in a ptrace error if the kernel supports the tagged address ABI but not MTE (PR 28355). Making the register set selection dynamic, based on feature checks, solves this and simplifies the code a bit. It allows us to list all of the register sets only once, and pick and choose based on HWCAP/HWCAP2 or other properties. gdb/ChangeLog: 2021-11-03 Luis Machado <luis.machado@linaro.org> PR gdb/28355 * arch/aarch64.h (struct aarch64_features): New struct. gdbserver/ChangeLog: 2021-11-03 Luis Machado <luis.machado@linaro.org> PR gdb/28355 * linux-aarch64-low.cc (is_sve_tdesc): Remove. (aarch64_target::low_arch_setup): Rework to adjust the register sets. (aarch64_regsets): Update to list all register sets. (aarch64_regsets_info, regs_info_aarch64): Replace NULL with nullptr. (aarch64_sve_regsets, aarch64_sve_regsets_info) (regs_info_aarch64_sve): Remove. (aarch64_adjust_register_sets): New. (aarch64_target::get_regs_info): Remove references to removed structs. (initialize_low_arch): Likewise.
2021-11-03	Automatic date update in version.in	GDB Administrator	1	-1/+1

2021-11-02	Automatic date update in version.in	GDB Administrator	1	-1/+1

2021-11-01	Automatic date update in version.in	GDB Administrator	1	-1/+1

2021-10-31	Automatic date update in version.in	GDB Administrator	1	-1/+1

2021-10-30	Automatic date update in version.in	GDB Administrator	1	-1/+1

2021-10-29	Automatic date update in version.in	GDB Administrator	1	-1/+1

2021-10-28	Automatic date update in version.in	GDB Administrator	1	-1/+1

2021-10-27	Automatic date update in version.in	GDB Administrator	1	-1/+1

2021-10-26	Automatic date update in version.in	GDB Administrator	1	-1/+1

2021-10-25	Automatic date update in version.in	GDB Administrator	1	-1/+1

2021-10-24	Automatic date update in version.in	GDB Administrator	1	-1/+1

2021-10-23	Automatic date update in version.in	GDB Administrator	1	-1/+1

2021-10-22	Automatic date update in version.in	GDB Administrator	1	-1/+1

2021-10-22	[gdb/tui] Fix breakpoint display functionality	Tom de Vries	4	-2/+49
	In commit 81e6b8eb208 "Make tui-winsource not use breakpoint_chain", a loop body was transformed into a lambda function body: ... - for (bp = breakpoint_chain; - bp != NULL; - bp = bp->next) + iterate_over_breakpoints ([&] (breakpoint bp) -> bool ... and consequently: - a continue was replaced by a return, and - a final return was added. Then in commit 240edef62f0 "gdb: remove iterate_over_breakpoints function", we transformed back to a loop body: ... - iterate_over_breakpoints ([&] (breakpoint bp) -> bool + for (breakpoint bp : all_breakpoints ()) ... but without reverting the changes that introduced the two returns. Consequently, breakpoints no longer show up in the tui source window. Fix this by reverting the changes that introduced the two returns. Build on x86_64-linux, tested with all .exp test-cases that contain tuiterm_env. Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=28483 gdb/ChangeLog: 2021-10-22 Tom de Vries <tdevries@suse.de> PR tui/28483 tui/tui-winsource.c (tui_source_window_base::update_breakpoint_info): Fix returns in loop body. gdb/testsuite/ChangeLog: 2021-10-22 Tom de Vries <tdevries@suse.de> PR tui/28483 * gdb.tui/break.exp: New file.
2021-10-21	Automatic date update in version.in	GDB Administrator	1	-1/+1

2021-10-20	Automatic date update in version.in	GDB Administrator	1	-1/+1

2021-10-19	Automatic date update in version.in	GDB Administrator	1	-1/+1

2021-10-18	Automatic date update in version.in	GDB Administrator	1	-1/+1

2021-10-17	Automatic date update in version.in	GDB Administrator	1	-1/+1

2021-10-16	Automatic date update in version.in	GDB Administrator	1	-1/+1

2021-10-15	Automatic date update in version.in	GDB Administrator	1	-1/+1

2021-10-14	Automatic date update in version.in	GDB Administrator	1	-1/+1

2021-10-13	Automatic date update in version.in	GDB Administrator	1	-1/+1

2021-10-12	Automatic date update in version.in	GDB Administrator	1	-1/+1

2021-10-11	Automatic date update in version.in	GDB Administrator	1	-1/+1

2021-10-10	Automatic date update in version.in	GDB Administrator	1	-1/+1

2021-10-09	Automatic date update in version.in	GDB Administrator	1	-1/+1

2021-10-08	Automatic date update in version.in	GDB Administrator	1	-1/+1

2021-10-07	Automatic date update in version.in	GDB Administrator	1	-1/+1

2021-10-06	Automatic date update in version.in	GDB Administrator	1	-1/+1

2021-10-05	Automatic date update in version.in	GDB Administrator	1	-1/+1

2021-10-04	[gdb/build] Add CXX_DIALECT to CXX	Tom de Vries	7	-0/+48
	Say we use a gcc version that (while supporting c++11) does not support c++11 by default, and needs an -std setting to enable it. If gdb would use the default AX_CXX_COMPILE_STDCXX from autoconf-archive, then we'd have: ... CXX="g++ -std=gnu++11" ... That mechanism however has the following problem (quoting from commit 0bcda685399): ... the top level Makefile passes CXX down to subdirs, and that overrides whatever gdb/Makefile may set CXX to. The result would be that a make invocation from the build/gdb/ directory would use "g++ -std=gnu++11" as expected, while a make invocation at the top level would not. ... Commit 0bcda685399 fixes this by using a custom AX_CXX_COMPILE_STDCXX which does: ... CXX=g++ CXX_DIALECT=-std=gnu++11 ... The problem reported in PR28318 is that using the custom instead of the default AX_CXX_COMPILE_STDCXX makes the configure test for std::thread support fail. We could simply add $CXX_DIALECT to the test for std::thread support, but that would have to be repeated for each added c++ support test. Instead, fix this by doing: ... CXX="g++ -std=gnu++11" CXX_DIALECT=-std=gnu++11 ... This is somewhat awkward, since it results in -std=gnu++11 occuring twice in some situations: ... $ touch src/gdb/dwarf2/read.c $ ( cd build/gdb; make V=1 dwarf2/read.o ) g++-4.8 -std=gnu++11 -x c++ -std=gnu++11 ... ... However, both settings are needed: - the switch in CXX for the std::thread tests (and other tests) - the switch in CXX_DIALECT so it can be appended in Makefiles, to counteract the fact that the top-level Makefile overrides CXX The code added in gdb/ax_cxx_compile_stdcxx.m4 is copied from the default AX_CXX_COMPILE_STDCXX from autoconf-archive. Tested on x86_64-linux. Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=28318 gdb/ChangeLog: 2021-10-04 Tom de Vries <tdevries@suse.de> PR build/28318 * ax_cxx_compile_stdcxx.m4: Add CXX_DIALECT to CXX. * configure: Regenerate. gdbserver/ChangeLog: 2021-10-04 Tom de Vries <tdevries@suse.de> PR build/28318 * configure: Regenerate. gdbsupport/ChangeLog: 2021-10-04 Tom de Vries <tdevries@suse.de> PR build/28318 * configure: Regenerate.
2021-10-04	Automatic date update in version.in	GDB Administrator	1	-1/+1

2021-10-03	Automatic date update in version.in	GDB Administrator	1	-1/+1