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

Age	Commit message (Collapse)	Author	Files	Lines
2023-02-16	Automatic date update in version.in	GDB Administrator	1	-1/+1

2023-02-15	Automatic date update in version.in	GDB Administrator	1	-1/+1

2023-02-14	Automatic date update in version.in	GDB Administrator	1	-1/+1

2023-02-13	Fix doc build dependencies for --with-system-readline	Keith Seitz	3	-4/+15
	PR build/30108 concerns building gdb documentation with --with-sytem-readline. If the in-tree readline directory is missing, though, the docs will fail to build: make[4]: Entering directory '/home/keiths/work/readline-doc-issue/linux/gdb/doc' make[4]: *** No rule to make target '../../../src/gdb/doc/../../readline/readline/doc/rluser.texi', needed by 'gdb.info'. Stop. The listed file (and hsuser.texi) are conditionally included by gdb.texinfo. When system readline is used, gdb/configure.ac will leave READLINE_TEXI_INCFLAGS empty, causing doc/Makefile.in to output a line to $BUILD/doc/GDBvn.texi with "@set SYSTEM_READLINE". This surpresses the inclusion of the missing files. They are not needed or used in this scenario. However, GDB_DOC_SOURCE_INCLUDES always lists these two files as dependencies, thus provoking the build error whenever readline/ is missing. This patch fixes this by creating (essentially) a conditional setting of the dependencies to be included from readline.
2023-02-13	Automatic date update in version.in	GDB Administrator	1	-1/+1

2023-02-12	Automatic date update in version.in	GDB Administrator	1	-1/+1

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

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

2023-02-09	Automatic date update in version.in	GDB Administrator	1	-1/+1

2023-02-08	Automatic date update in version.in	GDB Administrator	1	-1/+1

2023-02-07	Automatic date update in version.in	GDB Administrator	1	-1/+1

2023-02-06	Automatic date update in version.in	GDB Administrator	1	-1/+1

2023-02-05	Automatic date update in version.in	GDB Administrator	1	-1/+1

2023-02-04	Automatic date update in version.in	GDB Administrator	1	-1/+1

2023-02-03	Automatic date update in version.in	GDB Administrator	1	-1/+1

2023-02-02	Bump GDB's version number to 13.0.91.DATE-git.	Joel Brobecker	1	-1/+1
	This commit changes gdb/version.in to 13.0.91.DATE-git.
2023-02-02	Ensure that libbacktrace/allocfail.sh is not deleted when creating release ↵	Nick Clifton	3	-2/+7
	tarballs. * Makefile.am (CLEANFILES): Import patch from upstream to prevent allocafail.sh from being removed when running 'make clean'. (cherry picked from commit edf64cd235f5ecb3725e7cf1ff83bbdb6dd53340)
2023-02-02	Set GDB version number to 13.0.91.	Joel Brobecker	1	-1/+1
	This commit changes gdb/version.in to 13.0.91.
2023-02-02	gdb/NEWS: Change "Changes since GDB 12" to "Changes in GDB 13".	Joel Brobecker	1	-1/+1
	Now that the version number is confirmed to GDB 13, this commit updates the gdb/NEWS file accordingly, as per GDB's release procedures.
2023-02-02	Automatic date update in version.in	GDB Administrator	1	-1/+1

2023-02-01	Automatic date update in version.in	GDB Administrator	1	-1/+1

2023-01-31	gdb/arm: Use new dwarf2 function cache	Torbjörn SVENSSON	1	-32/+65
	This patch resolves the performance issue reported in pr/29738 by caching the values for the stack pointers for the inner frame. By doing so, the impact can be reduced to checking the state and returning the appropriate value. Signed-off-by: Torbjörn SVENSSON <torbjorn.svensson@foss.st.com> Signed-off-by: Yvan Roux <yvan.roux@foss.st.com>
2023-01-31	gdb: dwarf2 generic implementation for caching function data	Torbjörn SVENSSON	2	-2/+95
	When there is no dwarf2 data for a register, a function can be called to provide the value of this register. In some situations, it might not be trivial to determine the value to return and it would cause a performance bottleneck to do the computation each time. This patch allows the called function to have a "cache" object that it can use to store some metadata between calls to reduce the performance impact of the complex logic. The cache object is unique for each function and frame, so if there are more than one function pointer stored in the dwarf2_frame_cache->reg array, then the appropriate pointer will be supplied (the type is not known by the dwarf2 implementation). dwarf2_frame_get_fn_data can be used to retrieve the function unique cache object. dwarf2_frame_allocate_fn_data can be used to allocate and retrieve the function unique cache object. Signed-off-by: Torbjörn SVENSSON <torbjorn.svensson@foss.st.com> Signed-off-by: Yvan Roux <yvan.roux@foss.st.com>
2023-01-31	Automatic date update in version.in	GDB Administrator	1	-1/+1

2023-01-30	Fix comparator bug in cooked index	Tom Tromey	2	-85/+132
	Simon pointed out that the cooked index template-matching patch introduced a failure in libstdc++ debug mode. In particular, the new code violates the assumption of std::lower_bound and std::upper_bound that the range is sorted with respect to the comparison. When I first debugged this, I thought the problem was unfixable as-is and that a second layer of filtering would have to be done. However, on irc, Simon pointed out that it could perhaps be solved if the comparison function were assured that one operand always came from the index, with the other always being the search string. This patch implements this idea. First, a new mode is introduced: a sorting mode for cooked_index_entry::compare. In this mode, strings are compared case-insensitively, but we're careful to always sort '<' before any other printable character. This way, two names like "func" and "func<param>" will be sorted next to each other -- i.e., "func1" will not be seen between them. This is important when searching. Second, the compare function is changed to work in a strcmp-like way. This makes it easier to test and (IMO) understand. Third, the compare function is modified so that in non-sorting modes, the index entry is always the first argument. This allows consistency in compares. I regression tested this in libstdc++ debug mode on x86-64 Fedora 36. It fixes the crash that Simon saw. This is v2. I believe it addresses the review comments, except for the 'enum class' change, as I mentioned in email on the list. Approved-By: Simon Marchi <simon.marchi@efficios.com> (cherry picked from commit c121e82c39659d1140b1a6a3cfd72c765741b9f5)
2023-01-30	Automatic date update in version.in	GDB Administrator	1	-1/+1

2023-01-29	Automatic date update in version.in	GDB Administrator	1	-1/+1

2023-01-28	Automatic date update in version.in	GDB Administrator	1	-1/+1

2023-01-27	Automatic date update in version.in	GDB Administrator	1	-1/+1

2023-01-26	Automatic date update in version.in	GDB Administrator	1	-1/+1

2023-01-25	Automatic date update in version.in	GDB Administrator	1	-1/+1

2023-01-24	Automatic date update in version.in	GDB Administrator	1	-1/+1

2023-01-23	Automatic date update in version.in	GDB Administrator	1	-1/+1

2023-01-22	Automatic date update in version.in	GDB Administrator	1	-1/+1

2023-01-21	Automatic date update in version.in	GDB Administrator	1	-1/+1

2023-01-20	Automatic date update in version.in	GDB Administrator	1	-1/+1

2023-01-19	Automatic date update in version.in	GDB Administrator	1	-1/+1

2023-01-18	Automatic date update in version.in	GDB Administrator	1	-1/+1

2023-01-17	Fix parameter-less template regression in new DWARF reader	Tom Tromey	5	-22/+226
	PR c++/29896 points out a regression in the new DWARF reader. It does not properly handle a case like "break fn", where "fn" is a template function. This happens because the new index uses strncasecmp to compare. However, to make this work correctly, we need a custom function that ignores template parameters. This patch adds a custom comparison function and fixes the bug. A new test case is included. Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=29896 (cherry picked from commit ac37b79cc440e37fc704d425a6e450afb3c7ee89)
2023-01-17	Move hash_entry and eq_entry into cooked_index::do_finalize	Tom Tromey	1	-20/+14
	I was briefly confused by the hash_entry and eq_entry functions in the cooked index. They are only needed in a single method, and that method already has a couple of local lambdas for a different hash table. So, it seemed cleaner to move these there as well. (cherry picked from commit 5a89072f36ddd3be71103e3806d42ff5e49ff616)
2023-01-17	Avoid submitting empty tasks in parallel_for_each	Tom Tromey	2	-0/+69
	I found that parallel_for_each would submit empty tasks to the thread pool. For example, this can happen if the number of tasks is smaller than the number of available threads. In the DWARF reader, this resulted in the cooked index containing empty sub-indices. This patch arranges to instead shrink the result vector and process the trailing entries in the calling thread. (cherry picked from commit 63078a04984b73e1fdeb4571a63605ee5c13f929)
2023-01-17	Automatic date update in version.in	GDB Administrator	1	-1/+1

2023-01-16	Automatic date update in version.in	GDB Administrator	1	-1/+1

2023-01-15	Automatic date update in version.in	GDB Administrator	1	-1/+1

2023-01-14	Automatic date update in version.in	GDB Administrator	1	-1/+1

2023-01-13	Automatic date update in version.in	GDB Administrator	1	-1/+1

2023-01-12	Set _WIN32_WINNT in common.m4 configure check	Tom Tromey	5	-5/+48
	GCC recently added support for the Windows thread model, enabling libstdc++ to support Windows natively. However, this supporrt requires a version of Windows later than the minimum version that is supported by GDB. PR build/29966 points out that the GDB configure test for std::thread does not work in this situation, because _WIN32_WINNT is not defined in test program, and so <thread> seems to be fine. This patch is an attempt to fix the problem, by using the same setting for _WIN32_WINNT at configure time as is used at build time. I don't have access to one of the older systems so I don't think I can truly test this. I did do a mingw cross build, though. I'm going to ask the bug reporter to test it. Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=29966 (cherry picked from commit 2124b2de4bba05063218501dcccfc4cffe648cda)
2023-01-12	Automatic date update in version.in	GDB Administrator	1	-1/+1

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

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