From: Michael Eager <eager@eagerm.com>
To: gdb@sourceware.org, lldb-dev@lists.llvm.org,
llvm-dev@lists.llvm.org, GCC Mailing List <gcc@gcc.gnu.org>
Subject: DWARF Committee resumes meetings
Date: Wed, 27 Jan 2021 12:26:36 -0800 [thread overview]
Message-ID: <b578b963-96ab-b919-9d79-920012e0660f@eagerm.com> (raw)
The DWARF Debugging Standard Committee (http://dwarfstd.org) is planning
to resume meetings starting in February. The DWARF debugging file
format, as you likely know, is widely used by compilers and debuggers to
support source level debugging. The Committee released Version 5 of the
DWARF Standard in 2017 and will start work on Version 6.
The committee consists of more than 20 committee members from a broad
cross-section of the compiler and debugger development community,
representing a dozen companies and including a number of independent
developers, working on both proprietary and open source products.
A list of the current proposals or issues can be found on the Open
Issues web page: http://dwarfstd.org/Issues.php. If you would like to
submit a comment, proposal, or issue, go to the Public Comment page:
http://dwarfstd.org/Comment.php.
If you are interested in participating on the DWARF Committee please
contact me privately.
--
Michael Eager, DWARF Committee Chair
reply other threads:[~2021-01-27 20:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=b578b963-96ab-b919-9d79-920012e0660f@eagerm.com \
--to=eager@eagerm.com \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sourceware.org \
--cc=lldb-dev@lists.llvm.org \
--cc=llvm-dev@lists.llvm.org \
/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).