public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: James Cownie <jcownie@etnus.com>
To: gdb@sources.redhat.com
Subject: Re: [PATCH] Naming dwarves
Date: Mon, 19 May 2003 13:07:00 -0000	[thread overview]
Message-ID: <19HkLf-5tz-00@etnus.com> (raw)
In-Reply-To: <200305171253.h4HCrTT0012142@elgar.kettenis.dyndns.org>

Mark Kettenis wrote :-

> There is also a public draft for DWARF Version 3, which should be
> largely binary compatible with Version 2.  Standardization of Version
> 3 seems to have stopped, but some of the proposed extensions are
> already in use. 

It's about to start up again (there was a hiatus when the dot com bust
happened, since at that point none of the companies wanted to pay any
money to have a "real" standard produced).

This message from Michael Eager gives the current status

  Date: Thu, 08 May 2003 12:12:15 -0700
  From: Michael Eager <eager@eagercon.com>
  To: Dwarf 2 <dwarf2@els.sgi.com>
  Cc: Scott McNeil <mcneil@freestandards.org>
  Subject: DWARF Standard becoming part of Free Standards Group
  Sender: owner-dwarf2@els.sgi.com

  As you may know, for some time I've been working on finding a
  standards organization with which to affiliate the DWARF standard.

  I've looked into a variety of organizations, ranging from the
  "heavy weight's" of ANSI or IEEE, and the lighter weight organization
  like IEEE-ISTO.  I believe that the Free Standards Group offers
  us an excellent combination of stability and public visiblity.

  You may be familiar with Free Standards Group because it is the
  home of the Linux Standards Base (FSG and LSB, respectively, for
  those who like TLAs).  You can find more info about FSG at
  http://www.freestandardsgroup.org.  While FSG has been closely
  associated with Linux in the past, its charter is broader and
  does encompass architecture-independent standards like DWARF.

  In the next few weeks, we will create a web page at FSG for
  DWARF which will include the Public Review Draft which has
  been languishing on my system for a long while.  We will arrange
  for public comments to be collected and evaluated.  I also hope
  to be able to add a FAQ and perhaps some other materials to
  the web site which will make using DWARF easier.  FSG also
  has facilities for spam-filtered mailing lists.

  -- 
  Michael Eager	 Eager Consulting     eager@eagercon.com
  1960 Park Blvd., Palo Alto, CA 94306  650-325-8077

The DWARF 3 site is at http://www.eagercon.com/dwarf/dwarf3std.htm
I'm not sure how you get on the mailing list, but talking to Mike
Eager seems a good start...

-- Jim 

James Cownie	<jcownie@etnus.com>
Etnus, LLC.     +44 117 9071438
http://www.etnus.com

  parent reply	other threads:[~2003-05-19 13:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-17 12:53 Mark Kettenis
2003-05-18  4:35 ` Daniel Jacobowitz
2003-05-20 21:01   ` Jim Blandy
2003-05-19 13:07 ` James Cownie [this message]
2003-05-19 14:03 ` Elena Zannoni
2003-05-20 18:54 ` Andrew Cagney

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=19HkLf-5tz-00@etnus.com \
    --to=jcownie@etnus.com \
    --cc=gdb@sources.redhat.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).