aboutsummaryrefslogtreecommitdiff
AgeCommit message (Collapse)AuthorFilesLines
2024-03-03Set GDB version number to 14.2.gdb-14.2-releaseJoel Brobecker1-1/+1
This commit changes gdb/version.in to 14.2.
2024-03-03Automatic date update in version.inGDB Administrator1-1/+1
2024-03-02Automatic date update in version.inGDB Administrator1-1/+1
2024-03-01Automatic date update in version.inGDB Administrator1-1/+1
2024-02-29Automatic date update in version.inGDB Administrator1-1/+1
2024-02-28Automatic date update in version.inGDB Administrator1-1/+1
2024-02-27Automatic date update in version.inGDB Administrator1-1/+1
2024-02-26Automatic date update in version.inGDB Administrator1-1/+1
2024-02-25Automatic date update in version.inGDB Administrator1-1/+1
2024-02-24Automatic date update in version.inGDB Administrator1-1/+1
2024-02-23Automatic date update in version.inGDB Administrator1-1/+1
2024-02-22Automatic date update in version.inGDB Administrator1-1/+1
2024-02-21Automatic date update in version.inGDB Administrator1-1/+1
2024-02-20Automatic date update in version.inGDB Administrator1-1/+1
2024-02-19Automatic date update in version.inGDB Administrator1-1/+1
2024-02-18Automatic date update in version.inGDB Administrator1-1/+1
2024-02-17Automatic date update in version.inGDB Administrator1-1/+1
2024-02-16Automatic date update in version.inGDB Administrator1-1/+1
2024-02-15Automatic date update in version.inGDB Administrator1-1/+1
2024-02-14Automatic date update in version.inGDB Administrator1-1/+1
2024-02-13Automatic date update in version.inGDB Administrator1-1/+1
2024-02-12Automatic date update in version.inGDB Administrator1-1/+1
2024-02-11Fix crash when calling Frame.static_linkHannes Domani2-0/+17
If you try to call Frame.static_link for a frame without debug info, gdb crashes: ``` Temporary breakpoint 1, 0x000000013f821650 in main () (gdb) py print(gdb.selected_frame().static_link()) This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information. ``` The problem was a missing check if get_frame_block returns nullptr inside frame_follow_static_link. With this, it works: ``` Temporary breakpoint 1, 0x000000013f941650 in main () (gdb) py print(gdb.selected_frame().static_link()) None ``` Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=31366 Approved-By: Tom Tromey <tom@tromey.com>
2024-02-11Automatic date update in version.inGDB Administrator1-1/+1
2024-02-10Automatic date update in version.inGDB Administrator1-1/+1
2024-02-09Automatic date update in version.inGDB Administrator1-1/+1
2024-02-08Automatic date update in version.inGDB Administrator1-1/+1
2024-02-07Automatic date update in version.inGDB Administrator1-1/+1
2024-02-06[gdb/tdep] Fix use-after-free in arm_exidx_fill_cacheTom de Vries1-1/+1
On arm-linux the linaro CI occasionally reports: ... (gdb) up 10 #4 0x0001b864 in pthread_join () (gdb) FAIL: gdb.threads/staticthreads.exp: up 10 ... while this is expected: ... (gdb) up 10 #3 0x00010568 in main (argc=1, argv=0xfffeede4) at staticthreads.c:76 76 pthread_join (thread, NULL); (gdb) PASS: gdb.threads/staticthreads.exp: up 10 ... Thiago investigated the problem, and using valgrind found an invalid read in arm_exidx_fill_cache. The problem happens as follows: - an objfile and corresponding per_bfd are allocated - some memory is allocated in arm_exidx_new_objfile using objfile->objfile_obstack, for the "exception table entry cache". - a symbol reread is triggered, and the objfile, including the objfile_obstack, is destroyed - a new objfile is allocated, using the same per_bfd - again arm_exidx_new_objfile is called, but since the same per_bfd is used, it doesn't allocate any new memory for the "exception table entry cache". - the "exception table entry cache" is accessed by arm_exidx_fill_cache, and we have a use-after-free. This is a regression since commit a2726d4ff80 ("[ARM] Store exception handling information per-bfd instead of per-objfile"), which changed the "exception table entry cache" from per-objfile to per-bfd, but failed to update the obstack_alloc. Fix this by using objfile->per_bfd->storage_obstack instead of objfile->objfile_obstack. I couldn't reproduce the FAIL myself, but Thiago confirmed that the patch fixes it. Tested on arm-linux. Approved-By: Luis Machado <luis.machado@arm.com> PR tdep/31254 Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=31254
2024-02-06Automatic date update in version.inGDB Administrator1-1/+1
2024-02-05Automatic date update in version.inGDB Administrator1-1/+1
2024-02-04Automatic date update in version.inGDB Administrator1-1/+1
2024-02-03Automatic date update in version.inGDB Administrator1-1/+1
2024-02-02Automatic date update in version.inGDB Administrator1-1/+1
2024-02-01Automatic date update in version.inGDB Administrator1-1/+1
2024-01-31Automatic date update in version.inGDB Administrator1-1/+1
2024-01-30Automatic date update in version.inGDB Administrator1-1/+1
2024-01-29Automatic date update in version.inGDB Administrator1-1/+1
2024-01-28Automatic date update in version.inGDB Administrator1-1/+1
2024-01-27Automatic date update in version.inGDB Administrator1-1/+1
2024-01-26Automatic date update in version.inGDB Administrator1-1/+1
2024-01-25Automatic date update in version.inGDB Administrator1-1/+1
2024-01-24Automatic date update in version.inGDB Administrator1-1/+1
2024-01-23gdb: fix "list ." related crashGuinevere Larsen3-0/+60
When a user attempts to use the "list ." command with an inferior that doesn't have debug symbols, GDB would crash. This was reported as PR gdb/31256. The crash would happen when attempting to get the current symtab_and_line for the stop location, because the symtab would return a null pointer and we'd attempt to dereference it to print the line. This commit fixes that by checking for an empty symtab and erroring out of the function if it happens. Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=31256 Approved-By: Tom Tromey <tom@tromey.com>
2024-01-23Automatic date update in version.inGDB Administrator1-1/+1
2024-01-22Automatic date update in version.inGDB Administrator1-1/+1
2024-01-21Automatic date update in version.inGDB Administrator1-1/+1
2024-01-20Automatic date update in version.inGDB Administrator1-1/+1
2024-01-19Automatic date update in version.inGDB Administrator1-1/+1
2024-01-18Automatic date update in version.inGDB Administrator1-1/+1