Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Phil Muldoon <pmuldoon@redhat.com>
Cc: gdb@sourceware.org, dnovillo@google.com,
	       Cary Coutant <ccoutant@google.com>,
	Mark Wielaard <mjw@redhat.com>
Subject: Re: GDB Talks at the GNU Cauldron
Date: Thu, 09 Feb 2012 14:03:00 -0000	[thread overview]
Message-ID: <20120209140330.GA12146@host2.jankratochvil.net> (raw)
In-Reply-To: <4F32DAC8.8020408@redhat.com>

On Wed, 08 Feb 2012 21:27:52 +0100, Phil Muldoon wrote:
> According to the organizers there are three to four talks at the
> Cauldron.  Something that Diego mentioned was the need to coordinate
> talks.  So, who has submitted abstracts, and what are their titles?
> It would be good to plan for this.

There is also one GDB-related submitted abour DWARF compression (posting with
Mark's agreement).

As I posted here before one general Roadmap talk of mine (I do not see any such
other talk here).


Regards,
Jan

------------------------------------------------------------------------------

Title: Reducing DWARF debuginfo size.
Authors: Cary Coutant <ccoutant@google.com>, Mark Wielaard <mjw@redhat.com>
Abstract: Generating, linking, reading and storing DWARF debuginfo take
significant resources, time and space.  We want to discuss some efforts
that have recently been done to reduce some of that in the compiler,
linker, package manager and tools, like debuggers, that use the DWARF
debug information.  We are interested in discussing efforts that worked,
the various tradeoffs, efforts that didn't produce significant results
and ideas for future DWARF reduction work and/or standardization.

Cary Coutant has been working on the Debug Fission project, DWARF
Extensions for Separate Debug Information Files:
http://gcc.gnu.org/wiki/DebugFission

Mark Wielaard has been working on the elfutils project, which contains
the libdw DWARF consumer library that is used by tools like systemtap
and the dwarves tools:
https://fedorahosted.org/elfutils/wiki/RoadMap

------------------------------------------------------------------------------

Title: GDB Roadmap
Authors: Jan Kratochvil
Abstract:
Status of missing features, status of features being worked on (known to me).

Which way to keep unused template methods code separate from the code output.
Dynamic types (such as variable length arrays) implementation choices in GDB.


      parent reply	other threads:[~2012-02-09 14:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-08 20:28 Phil Muldoon
2012-02-08 21:03 ` Kevin Pouget
2012-02-08 22:39 ` Stan Shebs
2012-02-09  8:18 ` Joachim Protze
2012-02-09 14:03 ` Jan Kratochvil [this message]

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=20120209140330.GA12146@host2.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=ccoutant@google.com \
    --cc=dnovillo@google.com \
    --cc=gdb@sourceware.org \
    --cc=mjw@redhat.com \
    --cc=pmuldoon@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