From: Cary Coutant <ccoutant@google.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: Doug Evans <dje@google.com>, gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [RFA] py-value.exp: Use different names for C/C++ .o files.
Date: Wed, 07 Aug 2013 17:12:00 -0000 [thread overview]
Message-ID: <CAHACq4qUeZXGSiZqmTkz0JeP9OHvfkoMheiXFapQK6_x+gqQqA@mail.gmail.com> (raw)
In-Reply-To: <CAHACq4oqwE5j+qvgQ-=hA=VncA9dBTB8Q44t5r+8q1jMPDfnwA@mail.gmail.com>
> At the moment, the dwp utility generates the new v2 dwp file format,
> which isn't yet supported by GDB. I shouldn't have committed that
> change until GDB was prepared to support it, so I'll revert that patch
> shortly, and you'll be able to build a dwp that supports the v1 format
> that GDB does currently support. The top-of-trunk readelf can dump
> both v1 and v2 formats.
OK, I've committed a patch to revert the v2 support in dwp. I'll
restore it when GDB support is there.
-cary
next prev parent reply other threads:[~2013-08-07 17:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-01 21:10 Doug Evans
2013-08-07 15:15 ` Jan Kratochvil
2013-08-07 16:49 ` Cary Coutant
2013-08-07 17:12 ` Cary Coutant [this message]
2013-08-07 19:11 ` 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=CAHACq4qUeZXGSiZqmTkz0JeP9OHvfkoMheiXFapQK6_x+gqQqA@mail.gmail.com \
--to=ccoutant@google.com \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@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).