GDB 10.1 release -- 2020-09-26 Update
Strasuns, Mihails
mihails.strasuns@intel.com
Tue Sep 29 12:14:08 GMT 2020
Hello,
FYI: I am currently investigating a regression caused by 7188ed02d2a7e3fce00a0214e70457c5ef56df6b (Replace dwarf2_per_cu_data::cu backlink with per-objfile map).
With my program it causes GDB to crash with the following backtrace:
#0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
#1 0x00007fe4e871c8b1 in __GI_abort () at abort.c:79
#2 0x000055e6b5a17333 in handle_sigsegv (sig=11) at /users/mstrasun/sources/gdb/gdb/event-top.c:885
#3 <signal handler called>
#4 0x000055e6b5f08f9e in htab_find_with_hash (htab=0x0, element=0x7ffcd1f58440, hash=3394)
at /users/mstrasun/sources/gdb/libiberty/hashtab.c:591
#5 0x000055e6b59d0b9b in follow_die_offset (sect_off=(unknown: 3394), offset_in_dwz=0,
ref_cu=0x7ffcd1f58528) at /users/mstrasun/sources/gdb/gdb/dwarf2/read.c:22273
#6 0x000055e6b59d0c2e in follow_die_ref (src_die=0x0, attr=0x7ffcd1f58540, ref_cu=0x7ffcd1f58528)
at /users/mstrasun/sources/gdb/gdb/dwarf2/read.c:22288
#7 0x000055e6b59ac51a in partial_die_full_name (pdi=0x55e6b87f02a0, cu=0x55e6b7811510)
at /users/mstrasun/sources/gdb/gdb/dwarf2/read.c:8296
#8 0x000055e6b59ac65c in add_partial_symbol (pdi=0x55e6b87f02a0, cu=0x55e6b7811510)
at /users/mstrasun/sources/gdb/gdb/dwarf2/read.c:8323
#9 0x000055e6b59ad040 in add_partial_subprogram (pdi=0x55e6b87f02a0, lowpc=0x7ffcd1f58760,
highpc=0x7ffcd1f58768, set_addrmap=0, cu=0x55e6b7811510)
at /users/mstrasun/sources/gdb/gdb/dwarf2/read.c:8591
<...>
After this patch die_hash ends up being null in this context.
BR,
Mihails
> -----Original Message-----
> From: Gdb-patches <gdb-patches-bounces@sourceware.org> On Behalf Of
> Joel Brobecker
> Sent: Saturday, September 26, 2020 8:35 PM
> To: gdb-patches@sourceware.org
> Subject: GDB 10.1 release -- 2020-09-26 Update
>
> Hi everyone,
>
> Here is another update on the release. I think we're converging with maybe
> one new item which I'm a little worried about, as this touches an area that is
> traditionally very complex and delicate (PR gdb/26642).
>
> Fixed Since the Previous Update:
> --------------------------------
>
> * [TomT] <PR tui/26638>
> TUI focus behavior change
> https://sourceware.org/bugzilla/show_bug.cgi?id=26638
>
> Added Since the Last Update:
> ----------------------------
>
> * [SimonM] <PR gdb/26642>
> "maintenance set target-async off" is broken on GNU/Linux
> https://sourceware.org/bugzilla/show_bug.cgi?id=26642
>
> Other Ongoing Items:
> --------------------
>
> * [EliZ] <PR build/26607>
> GDB build failure in gnulib if building on Windows version older than 8
> https://sourceware.org/bugzilla/show_bug.cgi?id=26607
>
> gnulib pushed a couple of patches:
> https://sourceware.org/pipermail/gdb-patches/2020-
> September/171920.html
>
> The proposal is the following:
> - On the branch: we review, and test the two patches, then
> integrate them;
> - On master, we schedule a gnulib update.
>
> Patch for the branch proposed at:
> https://sourceware.org/pipermail/gdb-patches/2020-
> September/172155.html
>
> Not Critical, but Requested:
> ----------------------------
>
> * [<unassigned>] <PR python/26586> (raised by Christian B)
> from_tty argument to Python's gdb.execute is no longer effective
> https://sourceware.org/bugzilla/show_bug.cgi?id=26586
>
> Not release blocking because not exactly a regressions (8.2 and 9
> already had the bug).
>
> Patch pushed to master:
>
> | commit 8f9929bb97dc0f0fdf60269ac8c9a7d50746646f (origin/master,
> origin/HEAD)
> | Author: Gareth Rees <grees@undo.io>
> | Date: Sat Sep 26 11:01:45 2020 -0700
> | Subject: gdb: Fix from_tty argument to gdb.execute in Python.
>
> Requested second opinion before backporting.
>
> * [AntonK, ShahabV] (suggested by SimonM)
> Add ARC Linux gdbserver support
>
> No movement since last update (waiting on path author).
>
> Patch (Aug 26th):
> https://sourceware.org/pipermail/gdb-patches/2020-August/171499.html
>
> Latest messages:
> https://sourceware.org/pipermail/gdb-patches/2020-
> September/171911.html
>
> --
> Joel
Intel Deutschland GmbH
Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de
Managing Directors: Christin Eisenschmid, Gary Kershaw
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928
More information about the Gdb-patches
mailing list