aboutsummaryrefslogtreecommitdiff
AgeCommit message (Collapse)AuthorFilesLines
2024-01-17Automatic date update in version.inGDB Administrator1-1/+1
2024-01-16Automatic date update in version.inGDB Administrator1-1/+1
2024-01-15Automatic date update in version.inGDB Administrator1-1/+1
2024-01-14Automatic date update in version.inGDB Administrator1-1/+1
2024-01-13Automatic date update in version.inGDB Administrator1-1/+1
2024-01-12Automatic date update in version.inGDB Administrator1-1/+1
2024-01-11Automatic date update in version.inGDB Administrator1-1/+1
2024-01-10Automatic date update in version.inGDB Administrator1-1/+1
2024-01-09Automatic date update in version.inGDB Administrator1-1/+1
2024-01-08Automatic date update in version.inGDB Administrator1-1/+1
2024-01-07Automatic date update in version.inGDB Administrator1-1/+1
2024-01-06Automatic date update in version.inGDB Administrator1-1/+1
2024-01-05Automatic date update in version.inGDB Administrator1-1/+1
2024-01-04Automatic date update in version.inGDB Administrator1-1/+1
2024-01-03Automatic date update in version.inGDB Administrator1-1/+1
2024-01-02Automatic date update in version.inGDB Administrator1-1/+1
2024-01-01Automatic date update in version.inGDB Administrator1-1/+1
2023-12-31Automatic date update in version.inGDB Administrator1-1/+1
2023-12-30Automatic date update in version.inGDB Administrator1-1/+1
2023-12-29Automatic date update in version.inGDB Administrator1-1/+1
2023-12-28Automatic date update in version.inGDB Administrator1-1/+1
2023-12-27Automatic date update in version.inGDB Administrator1-1/+1
2023-12-26Automatic date update in version.inGDB Administrator1-1/+1
2023-12-25Automatic date update in version.inGDB Administrator1-1/+1
2023-12-24Automatic date update in version.inGDB Administrator1-1/+1
2023-12-23Automatic date update in version.inGDB Administrator1-1/+1
2023-12-22Automatic date update in version.inGDB Administrator1-1/+1
2023-12-21Automatic date update in version.inGDB Administrator1-1/+1
2023-12-20Automatic date update in version.inGDB Administrator1-1/+1
2023-12-19Automatic date update in version.inGDB Administrator1-1/+1
2023-12-18Automatic date update in version.inGDB Administrator1-1/+1
2023-12-17Automatic date update in version.inGDB Administrator1-1/+1
2023-12-16Automatic date update in version.inGDB Administrator1-1/+1
2023-12-15Automatic date update in version.inGDB Administrator1-1/+1
2023-12-14Automatic date update in version.inGDB Administrator1-1/+1
2023-12-13Automatic date update in version.inGDB Administrator1-1/+1
2023-12-12Automatic date update in version.inGDB Administrator1-1/+1
2023-12-11Automatic date update in version.inGDB Administrator1-1/+1
2023-12-10Automatic date update in version.inGDB Administrator1-1/+1
2023-12-09Automatic date update in version.inGDB Administrator1-1/+1
2023-12-08Fix printing of global variable stubs if no inferior is runningHannes Domani3-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-08Automatic date update in version.inGDB Administrator1-1/+1
2023-12-07Automatic date update in version.inGDB Administrator1-1/+1
2023-12-06Fix DLL export forwardingHannes Domani1-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-06Automatic date update in version.inGDB Administrator1-1/+1
2023-12-05Automatic date update in version.inGDB Administrator1-1/+1
2023-12-04Automatic date update in version.inGDB Administrator1-1/+1
2023-12-03Bump GDB's version number to 14.1.90.DATE-git.Joel Brobecker2-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-03Set GDB version number to 14.1.gdb-14.1-releaseJoel Brobecker1-1/+1
This commit changes gdb/version.in to 14.1.
2023-12-03Automatic date update in version.inGDB Administrator1-1/+1