a2137f94d6add libipt-cmake4-patch to fix build failure w/ cmake-4Tom de Vries2025-05-12 08:30:00 +00:00
164495090fAccepting request 1272090 from devel:gccAna Guerrero2025-04-24 15:24:56 +00:00
6bd3891873- Mention fixup-gdb-6.5-gcore-buffer-limit-test.patch.Tom de Vries2025-04-23 08:29:50 +00:00
09b5ea38aa- Mention changes in GDB 16: * GDB now supports watchpoints for tagged data pointers (see https://en.wikipedia.org/wiki/Tagged_pointer) on amd64, such as the one used by the Linear Address Masking (LAM) feature provided by Intel. * Debugging support for Intel MPX has been removed. This includes the removal of: * MPX register support * the commands "show/set mpx bound" (deprecated since GDB 15) * i386 and amd64 implementation of the hooks report_signal_info and get_siginfo_type. * GDB now supports printing of asynchronous events from the Intel Processor Trace during 'record instruction-history', 'record function-call-history' and all stepping commands. This can be controlled with the new "set record btrace pt event-tracing" command. * GDB now supports printing of ptwrite payloads from the Intel Processor Trace during 'record instruction-history', 'record function-call-history' and all stepping commands. The payload is also accessible in Python as a RecordAuxiliary object. Printing is customizable via a ptwrite filter function in Python. By default, the raw ptwrite payload is printed for each ptwrite that is encountered. * For breakpoints that are created in the 'pending' state, any 'thread' or 'task' keywords are parsed at the time the breakpoint is created, rather than at the time the breakpoint becomes non-pending. * Thread-specific breakpoints are only inserted into the program space in which the thread of interest is running. In most cases program spaces are unique for each inferior, so this means that thread-specific breakpoints will usually only be inserted for the inferior containing the thread of interest. The breakpoint will be hit no less than before. * For ARM targets, the offset of the pc in the jmp_buf has been fixed to match glibc 2.20 and later. This should only matter when not using libc probes. This may cause breakage when using an incompatible libc, like uclibc or newlib, or an older glibc. * MTE (Memory Tagging Extension) debugging is now supported on AArch64 baremetal targets. * In a record session, when a forward emulation reaches the end of the reverse history, the warning message has been changed to indicate that the end of the history has been reached. It also specifies that the forward execution can continue, and the recording will also continue. * The Ada 'Object_Size attribute is now supported. * New bash script gstack uses GDB to print stack traces of running processes. * Python API: * Added gdb.record.clear. Clears the trace data of the current recording. This forces re-decoding of the trace for successive commands. * Added the new event source gdb.tui_enabled. * New module gdb.missing_objfile that facilitates dealing with missing objfiles when opening a core-file. * New function gdb.missing_objfile.register_handler that can register an instance of a sub-class of gdb.missing_debug.MissingObjfileHandler as a handler for missing objfiles. * New class gdb.missing_objfile.MissingObjfileHandler which can be sub-classed to create handlers for missing objfiles. * The 'signed' argument to gdb.Architecture.integer_type() will no longer accept non-bool types. * The gdb.MICommand.installed property can only be set to True or False. * The 'qualified' argument to gdb.Breakpoint constructor will no longer accept non-bool types. * Added the gdb.Symbol.is_artificial attribute. * Debugger Adapter Protocol changes: * The "scopes" request will now return a scope holding global variables from the stack frame's compilation unit. * The "scopes" request will return a "returnValue" scope holding the return value from the latest "stepOut" command, when appropriate. * The "launch" and "attach" requests were rewritten in accordance with some clarifications to the spec. Now they can be sent at any time after the "initialized" event, but will not take effect (or send a response) until after the "configurationDone" request has been sent. * The "variables" request will not return artificial symbols. * New commands: * show jit-reader-directory Show the name of the directory that "jit-reader-load" uses for relative file names. * set style line-number foreground COLOR set style line-number background COLOR set style line-number intensity VALUE Control the styling of line numbers printed by GDB. * set style command foreground COLOR set style command background COLOR set style command intensity VALUE Control the styling of GDB commands when displayed by GDB. * set style title foreground COLOR set style title background COLOR set style title intensity VALUE This style now applies to the header line of lists, for example the first line of the output of "info breakpoints". Previous uses of this style have been replaced with the new "command" style. * set warn-language-frame-mismatch [on|off] show warn-language-frame-mismatch Control the warning that is emitted when specifying a language that does not match the current frame's language. * maintenance info inline-frames [ADDRESS] New command which displays GDB's inline-frame information for the current address, or for ADDRESS if specified. The output identifies inlined frames which start at the specified address. * maintenance info blocks [ADDRESS] New command which displays information about all of the blocks at ADDRESS, or at the current address if ADDRESS is not given. Blocks are listed starting at the inner global block out to the most inner block. * info missing-objfile-handlers List all the registered missing-objfile handlers. * enable missing-objfile-handler LOCUS HANDLER disable missing-objfile-handler LOCUS HANDLER Enable or disable a missing-objfile handler with a name matching the regular expression HANDLER, in LOCUS. LOCUS can be 'global' to operate on global missing-objfile handler, 'progspace' to operate on handlers within the current program space, or can be a regular expression which is matched against the filename of the primary executable in each program space. * Changed commands: * remove-symbol-file This command now supports file-name completion. * remove-symbol-file -a ADDRESS The ADDRESS expression can now be a full expression consisting of multiple terms, e.g. 'function + 0x1000' (without quotes), previously only a single term could be given. * target core target exec target tfile target ctf compile file maint print c-tdesc save gdb-index These commands now require their filename argument to be quoted if it contains white space or quote characters. If the argument contains no such special characters then quoting is not required. * maintenance print remote-registers Add an "Expedited" column to the output of the command. It indicates which registers were included in the last stop reply packet received by GDB. * show configuration Now includes the version of GNU Readline library that GDB is using. * New remote packets: * vFile:stat Return information about files on the remote system. Like vFile:fstat but takes a filename rather than an open file descriptor. * x addr,length Given ADDR and LENGTH, fetch LENGTH units from the memory at address ADDR and send the fetched data in binary format. This packet is equivalent to 'm', except that the data in the response are in binary format. * binary-upload in qSupported reply If the stub sends back 'binary-upload+' in it's qSupported reply, then GDB will, where possible, make use of the 'x' packet. If the stub doesn't report this feature supported, then GDB will not use the 'x' packet.Tom de Vries2025-04-22 15:00:47 +00:00
64642b155e- Update to 16.3. Patches dropped: * gdb-16.2.90.6c82a557806.17-04-2025.patch Maintenance script qa-local.sh: * Update version to 16.3. - Patches added: * gdb-testsuite-fix-timeout-in-gdb.threads-inf-thr-cou.patchTom de Vries2025-04-21 07:01:41 +00:00
3f37a4f8cbAccepting request 1267603 from devel:gccAna Guerrero2025-04-18 14:14:01 +00:00
62c2efd3ba- Update to current gdb-16-branch (gdb 16.2.90). Patches dropped: * core-target-open-segfault.patch * tui-wrefresh-issue.patch * gdb-rhbz2354997-gstack-drop-readnever.patch * gdb-record-fix-out-of-bounds-write-in-aarch64_record.patch * gdb-tdep-backport-i386_canonicalize_syscall-rewrite-.patch Patches added: * gdb-16.2.90.6c82a557806.17-04-2025.patchTom de Vries2025-04-17 21:28:26 +00:00
783b8d9968- Mention changes in GDB 15: * The MPX commands "show/set mpx bound" have been deprecated, as Intel listed MPX as removed in 2019. * GDB index now contains information about the main function. * This speeds up startup when it is being used for some large binaries. * On hosts where threading is available, DWARF reading is now done in the background, resulting in faster startup. This can be controlled using "maint set dwarf synchronous". * Changed commands: * disassemble: Attempting to use both the 'r' and 'b' flags with the disassemble command will now give an error. Previously the 'b' flag would always override the 'r' flag. * gcore, generate-core-file: GDB now generates sparse core files, on systems that support it. * maintenance info line-table: Add an EPILOGUE-BEGIN column to the output of the command. It indicates if the line is considered the start of the epilogue, and thus a point at which the frame can be considered destroyed. * set unwindonsignal on|off, show unwindonsignal: These commands are now aliases for the new set/show unwind-on-signal. * target record-full: This command now gives an error if any unexpected arguments are found after the command. * list .: When using the command "list ." in a location that has no debug information or no file loaded, GDB now says that there is no debug information to print lines. This makes it more obvious that there is no information, as opposed to implying there is no inferior loaded. * New commands: * info missing-debug-handler: List all the registered missing debug handlers. * enable missing-debug-handler LOCUS HANDLER, disable missing-debug-handler LOCUS HANDLER: Enable or disable a missing debug handler with a name matching the regular expression HANDLER, in LOCUS. LOCUS can be 'global' to operate on global missing debug handler, 'progspace' to operate on handlers within the current program space, or can be a regular expression which is matched against the filename of the primary executable in each program space. * maintenance info linux-lwps: List all LWPs under control of the linux-nat target. * set remote thread-options-packet, show remote thread-options-packet: Set/show the use of the thread options packet. * set direct-call-timeout SECONDS, show direct-call-timeout, set indirect-call-timeout SECONDS, show indirect-call-timeout: These new settings can be used to limit how long GDB will wait for an inferior function call to complete. The direct timeout is used for inferior function calls from e.g. 'call' and 'print' commands, while the indirect timeout is used for inferior function calls from within a conditional breakpoint expression. The default for the direct timeout is unlimited, while the default for the indirect timeout is 30 seconds. These timeouts will only have an effect for targets that are operating in async mode. For non-async targets the timeouts are ignored, GDB will wait indefinitely for an inferior function to complete, unless interrupted by the user using Ctrl-C. * set unwind-on-timeout on|off, show unwind-on-timeout: These commands control whether GDB should unwind the stack when a timeout occurs during an inferior function call. The default is off, in which case the inferior will remain in the frame where the timeout occurred. When on, GDB will unwind the stack removing the dummy frame that was added for the inferior call, and restoring the inferior state to how it was before the inferior call started. * set unwind-on-signal on|off, show unwind-on-signal: These new commands replaces the existing set/show unwindonsignal. The old command is maintained as an alias. * New features in the GDB remote stub, GDBserver: * The --remote-debug and --event-loop-debug command line options have been removed. * The --debug command line option now takes an optional comma separated list of components to emit debug for. The currently supported components are: all, threads, event-loop, and remote. If no components are given then threads is assumed. * The 'monitor set remote-debug' and 'monitor set event-loop-debug' command have been removed. * The 'monitor set debug 0|1' command has been extended to take a component name, e.g.: 'monitor set debug COMPONENT off|on'. Possible component names are: all, threads, event-loop, and remote. * Python API: * New function gdb.notify_mi(NAME, DATA), that emits custom GDB/MI async notification. * New read/write attribute gdb.Value.bytes that contains a bytes object holding the contents of this value. * New module gdb.missing_debug that facilitates dealing with objfiles that are missing any debug information. * New function gdb.missing_debug.register_handler that can register an instance of a sub-class of gdb.missing_debug.MissingDebugInfo as a handler for objfiles that are missing debug information. * New class gdb.missing_debug.MissingDebugInfo which can be sub-classed to create handlers for objfiles with missing debug information. * Stop events now have a "details" attribute that holds a dictionary that carries the same information as an MI "*stopped" event. * New function gdb.interrupt(), that interrupts GDB as if the user typed control-c. * New gdb.InferiorThread.ptid_string attribute. This read-only attribute contains the string that appears in the 'Target Id' column of the 'info threads' command output. * It is no longer possible to create new gdb.Progspace object using 'gdb.Progspace()', this will result in a TypeError. Progspace objects can still be obtained through calling other API functions, for example 'gdb.current_progspace()'. * User defined attributes can be added to a gdb.Inferior object, these will be stored in the object's new Inferior.__dict__ attribute. * User defined attributes can be added to a gdb.InferiorThread object, these will be stored in the object's new InferiorThread.__dict__ attribute. * New constants gdb.SYMBOL_TYPE_DOMAIN, gdb.SYMBOL_FUNCTION_DOMAIN, and gdb.SEARCH_*_DOMAIN corresponding to all the existing symbol domains. Symbol lookup can now search in multiple domains at once, and can also narrowly search for just a type or function. * Debugger Adapter Protocol changes: * GDB now emits the "process" event. * GDB now supports the "cancel" request. * The "attach" request now supports specifying the program. * New command "set debug dap-log-level" controls DAP logging. * The "set debug dap-log-file" command is now documented. This command was available in GDB 14 but not documented. * Guile API: * New constants SYMBOL_TYPE_DOMAIN, SYMBOL_FUNCTION_DOMAIN, and SEARCH_*_DOMAIN corresponding to all the existing symbol domains. Symbol lookup can now search in multiple domains at once, and can also narrowly search for just a type or function. * Remote packets: * New stop reason clone: Indicates that a clone system call was executed. * New remote packets: * QThreadOptions: Enable/disable optional event reporting, on a per-thread basis. Currently supported options are GDB_THREAD_OPTION_CLONE, to enable clone event reporting, and GDB_THREAD_OPTION_EXIT to enable thread exit event reporting. * QThreadOptions in qSupported: * The qSupported packet allows GDB to inform the stub it supports the QThreadOptions packet, and the qSupported response can contain the set of thread options the remote stub supports. * qIsAddressTagged: This new packet allows GDB to query the stub about a given address to check if it is tagged or not. Many memory tagging-related GDB commands need to perform this check before they read/write the allocation tag related to an address. Currently, however, this is done through a 'vFile' request to read the file /proc/<PID>/smaps and check if the address is in a region reported as memory tagged. Since not all targets have a notion of what the smaps file is about, this new packet provides a more generic way to perform such a check.Tom de Vries2025-02-17 16:43:29 +00:00
9a26e73894- Patches added (bsc#1220490): * fixup-gdb-6.6-buildid-locate-rpm.patchTom de Vries2024-04-10 15:43:01 +00:00
b5d1c65ac2Accepting request 1159816 from devel:gccAna Guerrero2024-03-21 16:00:06 +00:00
93003f4505- Avoid using a %gcc macro to support using gcc 4.8 for building on SLE11. Use the regular language compilers for testing.Richard Biener2024-03-20 10:38:11 +00:00
69639f4e6dAccepting request 1152308 from devel:gccAna Guerrero2024-02-28 18:45:23 +00:00
16c32eb249Accepting request 1152215 from home:dimstar:rpm4.20:gTom de Vries2024-02-27 14:38:23 +00:00
ff5514afc9- Maintenance script qa.sh: * Add PR31214 kfail. * Add kfail for fails in gdb.reverse/solib-precsave.exp / gdb.reverse/solib-reverse.exp fixed by commit fe6356def67 ("PowerPC and aarch64: Fix reverse stepping failure"). * Extend PR31004 kfail. - Don't require %{python}-base for gdb-testresults package. - Fix debuginfod handling: * Enable for sle_version >= 150400 (bsc#1185605, jsc#PED-1149, jsc#PED-1138), SLE15-SP4 and later. * Enable for suse_version >= 1600, ALP and Tumbleweed. * Add back "BuildRequires: libdebuginfod1" to prevent selecting dummy variant. * Add "BuildRequires: debuginfod-client" to prevent unresolved due to conflict with dummy variant. * Add --with-debuginfod=yes to prevent silently dropping support. - Patches added (backport from master): * gdb-testsuite-add-missing-no-prompt-anchor-in-gdb.ba.patch * gdb-testsuite-remove-spurious-in-save_vars.patchTom de Vries2024-02-01 07:32:03 +00:00
0c21457f3aAccepting request 1133867 from devel:gccAna Guerrero2023-12-19 22:15:32 +00:00
Tom de Vries
Ana Guerrero
Tom de Vries
Dominique Leuenberger
Richard Biener