Age | Commit message (Collapse) | Author | Files | Lines | |
---|---|---|---|---|---|
2024-03-03 | Set GDB version number to 14.2.gdb-14.2-release | Joel Brobecker | 1 | -1/+1 | |
This commit changes gdb/version.in to 14.2. | |||||
2024-03-03 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
2024-03-02 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
2024-03-01 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
2024-02-29 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
2024-02-28 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
2024-02-27 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
2024-02-26 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
2024-02-25 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
2024-02-24 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
2024-02-23 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
2024-02-22 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
2024-02-21 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
2024-02-20 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
2024-02-19 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
2024-02-18 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
2024-02-17 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
2024-02-16 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
2024-02-15 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
2024-02-14 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
2024-02-13 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
2024-02-12 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
2024-02-11 | Fix crash when calling Frame.static_link | Hannes Domani | 2 | -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-11 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
2024-02-10 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
2024-02-09 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
2024-02-08 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
2024-02-07 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
2024-02-06 | [gdb/tdep] Fix use-after-free in arm_exidx_fill_cache | Tom de Vries | 1 | -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-06 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
2024-02-05 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
2024-02-04 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
2024-02-03 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
2024-02-02 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
2024-02-01 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
2024-01-31 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
2024-01-30 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
2024-01-29 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
2024-01-28 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
2024-01-27 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
2024-01-26 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
2024-01-25 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
2024-01-24 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
2024-01-23 | gdb: fix "list ." related crash | Guinevere Larsen | 3 | -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-23 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
2024-01-22 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
2024-01-21 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
2024-01-20 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
2024-01-19 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |
2024-01-18 | Automatic date update in version.in | GDB Administrator | 1 | -1/+1 | |