From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: gdb-patches@sourceware.org
Cc: Victor Leschuk <vleschuk@accesssoftek.com>
Subject: [PATCH v2 0/5] DWARF-5: .debug_names index
Date: Sun, 18 Jun 2017 19:32:00 -0000 [thread overview]
Message-ID: <149781434459.10382.10368140746387313573.stgit@host1.jankratochvil.net> (raw)
Hi,
https://sourceware.org/git/gitweb.cgi?p=archer.git;a=shortlog;h=refs/heads/users/jkratoch/index
git://sourceware.org/git/archer.git
git diff gdb/master...archer/users/jkratoch/index
the patches mailed in this series depend on these already posted ones:
[gcc patch] DWARF-5: Define DW_IDX_GNU_static and DW_IDX_GNU_external
https://gcc.gnu.org/ml/gcc-patches/2017-05/msg02074.html
Message-ID: <20170526181408.GA15337@host1.jankratochvil.net>
+
[binutils patch] DWARF-5: readelf: .debug_names
https://sourceware.org/ml/binutils/2017-05/msg00291.html
Message-ID: <20170526181552.GA15442@host1.jankratochvil.net>
Default "save gdb-index" will switch to DWARF-5 but that requires also the
updated: contrib/gdb-add-index.sh
DWO is not yet handled. Discussed here whether it should be:
https://sourceware.org/ml/gdb-patches/2017-06/msg00479.html
Jan
next reply other threads:[~2017-06-18 19:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-18 19:32 Jan Kratochvil [this message]
2017-06-18 19:32 ` [PATCH v2 3/5] Code cleanup: dwarf2_initialize_objfile return value Jan Kratochvil
2017-06-18 19:32 ` [PATCH v2 4/5] Refactor: Move some generic code out of .gdb_index code Jan Kratochvil
2017-06-18 19:32 ` [PATCH v2 1/5] cc-with-tweaks.sh: Use gdb-add-index.sh Jan Kratochvil
2017-06-18 19:32 ` [PATCH v2 2/5] DWARF-5: .debug_names index producer Jan Kratochvil
2017-06-18 19:33 ` [PATCH v2 5/5] DWARF-5: .debug_names index consumer Jan Kratochvil
2017-06-19 20:56 ` obsolete: [PATCH v2 0/5] DWARF-5: .debug_names index Jan Kratochvil
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=149781434459.10382.10368140746387313573.stgit@host1.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=vleschuk@accesssoftek.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).