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

Age	Commit message (Collapse)	Author	Files	Lines
2023-12-03	Set GDB version number to 14.1.gdb-14.1-release	Joel Brobecker	1	-1/+1
	This commit changes gdb/version.in to 14.1.
2023-12-03	Automatic date update in version.in	GDB Administrator	1	-1/+1

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

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

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

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

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

2023-11-27	i386: Use a fallback XSAVE layout for remote targets	John Baldwin	3	-0/+128
	If a target provides a target description including registers from the XSAVE extended region, but does not provide an XSAVE layout, use a fallback XSAVE layout based on the included registers. This fallback layout matches GDB's behavior in earlier releases which assumes the layout from Intel CPUs. This fallback layout is currently only used for remote targets since native targets which support XSAVE provide an explicit layout derived from CPUID. PR gdb/30912 Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=30912 Approved-By: Simon Marchi <simon.marchi@efficios.com> (cherry picked from commit 66637e209cc836c19a21a28e91046649c7702037)
2023-11-27	Fix bug in DAP handling of 'pause' requests	Tom Tromey	3	-3/+97
	While working on cancellation, I noticed that a DAP 'pause' request would set the "do not emit the continue" flag. This meant that a subsequent request that should provoke a 'continue' event would instead suppress the event. I then tried writing a more obvious test case for this, involving an inferior call -- and discovered that gdb.events.cont does not fire for an inferior call. This patch installs a new event listener for gdb.events.inferior_call and arranges for this to emit continue and stop events when appropriate. It also fixes the original bug, by adding a check to exec_and_expect_stop. (cherry picked from commit c618a1c548193d2a6a8c3d909a3d1c620a156b5d)
2023-11-27	Automatic date update in version.in	GDB Administrator	1	-1/+1

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

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

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

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

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

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

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

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

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

2023-11-17	Ignore static members in NoOpStructPrinter	Tom Tromey	3	-2/+21
	Hannes' patch to show local variables in the TUI pointed out that NoOpStructPrinter should ignore static members. This patch implements this. (cherry picked from commit 4a1b9a4badc8954221926b231b81392fa625653c)
2023-11-17	Implement the notStopped DAP response	Tom Tromey	4	-4/+59
	DAP specifies that a request can fail with the "notStopped" message if the inferior is running but the request requires that it first be stopped. This patch implements this for gdb. Most requests are assumed to require a stopped inferior, and the exceptions are noted by a new 'request' parameter. You may notice that the implementation is a bit racy. I think this is inherent -- unless the client waits for a stop event before sending a request, the request may be processed at any time relative to a stop. https://sourceware.org/bugzilla/show_bug.cgi?id=31037 Reviewed-by: Kévin Le Gouguec <legouguec@adacore.com> (cherry picked from commit cfd00e8050a58aacc6489ec0379908be1a12be73)
2023-11-17	Remove ExecutionInvoker	Tom Tromey	4	-31/+16
	ExecutionInvoker is no longer really needed, due to the previous DAP refactoring. This patch removes it in favor of an ordinary function. One spot (the 'continue' request) could still have used it, but is more succinctly expressed as a lambda. Reviewed-by: Kévin Le Gouguec <legouguec@adacore.com> (cherry picked from commit 68caad9d0b06d0ac231ce083ff62410a5a1806c1)
2023-11-17	Automatically run (most) DAP requests in gdb thread	Tom Tromey	14	-130/+116
	Nearly every DAP request implementation forwards its work to the gdb thread, using send_gdb_with_response. This patch refactors the 'request' decorator to make this automatic, and to provide some parameters so that the unusual requests can express their needs as well. In a few spots this simplifies the code by removing an unnecessary helper function. This could be done in more places as well if we wanted. The main motivation for this patch is that I thought it would be helpful for cancellation. I am still working on that, but meanwhile the parameterization of 'request' makes it easy to handle the 'notStopped' response as well. Reviewed-by: Kévin Le Gouguec <legouguec@adacore.com> (cherry picked from commit c98921b258b55272c5b4066d96441e4e07626eb2)
2023-11-17	Handle StackFrameFormat in DAP	Tom Tromey	6	-47/+453
	DAP specifies a StackFrameFormat object that can be used to change how the "name" part of a stack frame is constructed. While this output can already be done in a nicer way (and also letting the client choose the formatting), nevertheless it is in the spec, so I figured I'd implement it. While implementing this, I discovered that the current code does not correctly preserve frame IDs across requests. I rewrote frame iteration to preserve this, and it turned out to be simpler to combine these patches. Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=30475 (cherry picked from commit 1920148904fe5ca0035c1addf2376f9ab13ffd3d)
2023-11-17	Automatic date update in version.in	GDB Administrator	1	-1/+1

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

2023-11-15	Minor cleanups in ada-nested.exp	Tom Tromey	1	-5/+9
	This changes ada-nested.exp to fix a test name (the test expects three variables but is named "two"), and to iterate over all the variables that are found. It also adds a workaround to a problem Tom de Vries found with an older version of GNAT -- it emits a duplicate "x". (cherry picked from commit e1ccbfffb5e0121c084898ac63f042187621d4ec)
2023-11-15	Automatic date update in version.in	GDB Administrator	1	-1/+1

2023-11-14	Update gdb.Symbol.is_variable documentation	Tom Tromey	1	-1/+3
	Kévin found a bug in an earlier version of this series that was based on a misconception I had about Symbol.is_variable. This patch fixes the documentation to explain the method a bit better. Approved-By: Eli Zaretskii <eliz@gnu.org> (cherry picked from commit 5006ea556dad71c4c868cf5705e007e72e3b02b4)
2023-11-14	Handle the static link in FrameDecorator	Tom Tromey	3	-13/+174
	A co-worker requested that the DAP scope for a nested function's frame also show the variables from outer frames. DAP doesn't directly support this notion, so this patch arranges to put these variables into the inner frames "Locals" scope. I chose to do this only for DAP. For CLI and MI, gdb currently does not do this, so this preserves the behavior. Note that an earlier patch (see commit 4a1311ba) removed some code that seemed to do something similar. However, that code did not actually work. (cherry picked from commit ebea770b19c09489fe5e2cb5c1fd568f0f21e17e)
2023-11-14	Fix a bug in DAP scopes code	Tom Tromey	1	-2/+6
	While working on static links, I noticed that the DAP scopes code does not handle the scenario where a frame decorator returns None. This situation should be handled identically to a frame decorator returning an empty iterator. (cherry picked from commit e9dacb1d6caa5770d3e1722adc0ec74ff13a7a89)
2023-11-14	Add gdb.Frame.static_link method	Tom Tromey	3	-0/+39
	This adds a new gdb.Frame.static_link method to the gdb Python layer. This can be used to find the static link frame for a given frame. Reviewed-By: Eli Zaretskii <eliz@gnu.org> (cherry picked from commit 4ead09a294adbb718d642874a554e78d931c2830)
2023-11-14	Move follow_static_link to frame.c	Tom Tromey	3	-53/+53
	This moves the follow_static_link function to frame.c and exports it for use elsewhere. The API is changed slightly to make it more generically useful. (cherry picked from commit 19b83d5c9bac1db207dce26859c6ca84135615b0)
2023-11-14	Add block::function_block	Tom Tromey	2	-0/+19
	This adds the method block::function_block, to easily access a block's enclosing function block. (cherry picked from commit ba707cadae18a7cc8bb47a736d3d0438d44262a9)
2023-11-14	Add two convenience methods to block	Tom Tromey	2	-3/+17
	This adds a couple of convenience methods, block::is_static_block and block::is_global_block. (cherry picked from commit edf1b9640bbc981c8a094d6ca29d444b1ed50a2c)
2023-11-14	Automatic date update in version.in	GDB Administrator	1	-1/+1

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

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

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

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

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

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

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

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

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

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

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

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

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

2023-10-31	Implement DAP setVariable request	Tom Tromey	6	-21/+311
	This patch implements the DAP setVariable request. setVariable is a bit odd in that it specifies the variable to modify by passing in the variable's container and the name of the variable. This approach can't handle variable shadowing (there are a couple of open DAP bugs on this topic), so this patch renames duplicates to avoid the problem. (cherry picked from commit 87e3cc466e8ea352639beb6db40a36e339d608d1)