From: Rae Kim via Gdb-patches <gdb-patches@sourceware.org>
To: Simon Marchi <simark@simark.ca>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v2] gdb: multi-line support for "document" command
Date: Thu, 3 Dec 2020 09:09:12 +0900 [thread overview]
Message-ID: <20201203000912.5dfnezqjumf6b2qj@raekf.iptime.org> (raw)
In-Reply-To: <6a1676d0-cc7a-1bdb-a2d1-5efb03aebdd3@simark.ca>
Thank you for your help.
I thought I already sent you thanks-email but couldn't find it in my sent box.
I am still getting used to TUI email client.
I will update the bugzilla once the copyright assignment is finished.
Regards,
Rae Kim
On Wed, Dec 02, 2020 at 09:38:08AM -0500, Simon Marchi wrote:
>
> On 2020-12-02 7:45 a.m., Rae Kim wrote:
> > "document" command executed in python, gdb.execute("document
> > <comname>\n...\nend\n"), will wait for user input. Python extension stops
> > working from that point.
> >
> > multi-line suport was introduced in commit 56bcdbea2. But "document" support
> > seem to be implemented.
>
> Thanks, this is fine.
>
> I don't think you have a copyright assignment on file, right? If not
> could you please fill this form and send it to the FSF?
>
> https://git.savannah.gnu.org/cgit/gnulib.git/plain/doc/Copyright/request-assign.future
>
> It can take a bit of time for them to process it, so please let us know
> when it is done. I filed this bug with the 11.1 milestone so we don't
> forget about your patch for the next GDB release:
>
> https://sourceware.org/bugzilla/show_bug.cgi?id=26996
>
> Simon
next prev parent reply other threads:[~2020-12-03 0:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-28 14:24 [PATCH] " Rae Kim via Gdb-patches
2020-12-01 15:22 ` Simon Marchi
2020-12-02 12:45 ` [PATCH v2] " Rae Kim via Gdb-patches
2020-12-02 14:38 ` Simon Marchi
2020-12-03 0:09 ` Rae Kim via Gdb-patches [this message]
2020-12-16 3:54 ` Simon Marchi via Gdb-patches
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=20201203000912.5dfnezqjumf6b2qj@raekf.iptime.org \
--to=gdb-patches@sourceware.org \
--cc=raekim@gmail.com \
--cc=simark@simark.ca \
/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