From: Doug Evans <dje@google.com>
To: gdb <gdb@sourceware.org>
Subject: Symbol Handling improvements
Date: Wed, 02 May 2012 22:13:00 -0000 [thread overview]
Message-ID: <CADPb22ToxAAUmdaaGYn=xWyeuEGmrJZvHr1SnTyX72wpWxAQXw@mail.gmail.com> (raw)
[bcc gdb-patches, just to make sure it reaches everyone]
Hi.
fyi, I have started a page to collect issues related to symbol
handling, debug info, etc. and to list ideas people are thinking
about.
I don't have any specific actions to take yet.
It's just a beginning.
http://sourceware.org/gdb/wiki/SymbolHandling
Comments welcome.
next reply other threads:[~2012-05-02 22:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-02 22:13 Doug Evans [this message]
2012-05-02 22:17 ` Doug Evans
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='CADPb22ToxAAUmdaaGYn=xWyeuEGmrJZvHr1SnTyX72wpWxAQXw@mail.gmail.com' \
--to=dje@google.com \
--cc=gdb@sourceware.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