| Age | Commit message (Collapse) | Author | Files | Lines | |
|---|---|---|---|---|---|
| 2024-01-02 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
| 2024-01-01 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
| 2023-12-31 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
| 2023-12-30 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
| 2023-12-29 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
| 2023-12-28 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
| 2023-12-27 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
| 2023-12-26 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
| 2023-12-25 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
| 2023-12-24 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
| 2023-12-23 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
| 2023-12-22 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
| 2023-12-21 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
| 2023-12-20 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
| 2023-12-19 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
| 2023-12-18 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
| 2023-12-17 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
| 2023-12-16 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
| 2023-12-15 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
| 2023-12-14 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
| 2023-12-13 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
| 2023-12-12 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
| 2023-12-11 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
| 2023-12-10 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
| 2023-12-09 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
| 2023-12-08 | Fix printing of global variable stubs if no inferior is running | Hannes Domani | 3 | -1/+68 | |
| Since 3c45e9f915ae4aeab7312d6fc55a947859057572 gdb crashes when trying to print a global variable stub without a running inferior, because of a missing nullptr-check (the block_scope function took care of that check before it was converted to a method). With this check it works again: ``` (gdb) print s $1 = <incomplete type> ``` Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=31128 Approved-By: Tom Tromey <tom@tromey.com> (cherry picked from commit 576745e26c0ec76a53ba45b20af464628a50b3e4) | |||||
| 2023-12-08 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
| 2023-12-07 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
| 2023-12-06 | Fix DLL export forwarding | Hannes Domani | 1 | -1/+4 | |
| I noticed it when I was trying to set a breakpoint at ExitProcess: ``` (gdb) b ExitProcess Breakpoint 1 at 0x14001fdd0 (gdb) r Starting program: C:\qiewer\heob\heob64.exe Warning: Cannot insert breakpoint 1. Cannot access memory at address 0x3dbf4120 Cannot insert breakpoint 1. Cannot access memory at address 0x77644120 ``` The problem doesn't exist in gdb 13.2, and the difference can easily be seen when printing ExitProcess. gdb 14.1: ``` (gdb) p ExitProcess $1 = {<text variable, no debug info>} 0x77644120 <UserHandleGrantAccess+36128> ``` gdb 13.2: ``` (gdb) p ExitProcess $1 = {<text variable, no debug info>} 0x77734120 <ntdll!RtlExitUserProcess> ``` The new behavior started with 9675da25357c7a3f472731ddc6eb3becc65b469a, where VMA was then calculated relative to FORWARD_DLL_NAME, while it was relative to DLL_NAME before. Fixed by calculating VMA relative to DLL_NAME again. Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=31112 Approved-By: Tom Tromey <tom@tromey.com> (cherry picked from commit 2574cd903dd84e7081506e24c2e232ecda11a736) | |||||
| 2023-12-06 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
| 2023-12-05 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
| 2023-12-04 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
| 2023-12-03 | Bump GDB's version number to 14.1.90.DATE-git. | Joel Brobecker | 2 | -2/+2 | |
| This commit changes gdb/version.in to 14.1.90.DATE-git. This commit also makes the following changes in gdb/testsuite: * gdb.base/default.exp: Change $_gdb_minor to 2. | |||||
| 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 | |
 |
index : riscv-gnu-toolchain/binutils.git | |
| Unnamed repository; edit this file 'description' to name the repository. | root |
| aboutsummaryrefslogtreecommitdiff |