From: Eli Zaretskii <eliz@gnu.org>
To: Doug Evans <dje@google.com>
Cc: gdb-patches@sourceware.org, palves@redhat.com, sergiodj@redhat.com
Subject: Re: [PATCH 3/4] python support for fetching separate debug files: add_separate_debug_file
Date: Fri, 21 Nov 2014 07:59:00 -0000 [thread overview]
Message-ID: <834mtt56i1.fsf@gnu.org> (raw)
In-Reply-To: <yjt2a93lo9a0.fsf@ruffy.mtv.corp.google.com>
> From: Doug Evans <dje@google.com>
> Date: Thu, 20 Nov 2014 13:24:23 -0800
>
> This patch provides an API call to add a separate debug file to an
> objfile.
>
> 2014-11-20 Doug Evans <dje@google.com>
>
> * NEWS: Mention gdb.Objfile.add_separate_debug_file.
> * python/py-objfile.c (objfpy_add_separate_debug_file): New function.
> (objfile_getset): Add "add_separate_debug_file".
>
> doc/
> * python.texi (Objfiles In Python): Document
> Objfile.add_separate_debug_file.
>
> testsuite/
> * gdb.python/py-objfile.exp: Add tests for
> objfile.add_separate_debug_file.
OK for the documentation parts.
Thanks.
next prev parent reply other threads:[~2014-11-21 7:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-20 21:24 Doug Evans
2014-11-21 7:59 ` Eli Zaretskii [this message]
2014-12-05 18:37 ` 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=834mtt56i1.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=sergiodj@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