From: "Marcin Kościelnicki" <koriakin@0x04.net>
To: Pedro Alves <palves@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] gdbserver: Handle 'v' packet while processing qSymbol.
Date: Tue, 29 Mar 2016 23:51:00 -0000 [thread overview]
Message-ID: <56FB1504.6070202@0x04.net> (raw)
In-Reply-To: <56FAFB0A.4070602@redhat.com>
On 30/03/16 00:00, Pedro Alves wrote:
> On 03/12/2016 03:02 PM, Marcin KoÅcielnicki wrote:
>
>> gdb/ChangeLog | 5 +++++
>> gdb/gdbserver/ChangeLog | 10 ++++++++++
>> gdb/gdbserver/remote-utils.c | 41 +++++++++++++++++++++++++++--------------
>> gdb/gdbserver/server.c | 4 ++--
>> gdb/gdbserver/server.h | 4 ++++
>> gdb/remote.c | 22 +++++++++++++++++-----
>> 6 files changed, 65 insertions(+), 21 deletions(-)
>>
>> diff --git a/gdb/ChangeLog b/gdb/ChangeLog
>> index febe960..41f826e 100644
>> --- a/gdb/ChangeLog
>> +++ b/gdb/ChangeLog
>> @@ -1,3 +1,8 @@
>> +2016-03-12 Marcin KoÅcielnicki <koriakin@0x04.net>
>> +
>> + * remote.c (xfreep): New function.
>
> You can use free_current_contents instead.
Whoops, I should've guessed there's something like that already...
>
>> + (remote_check_symbols): Allocate own buffer for reply.
>> +
>
>> @@ -1499,21 +1499,35 @@ look_up_one_symbol (const char *name, CORE_ADDR *addrp, int may_ask_gdb)
>> main loop. For now, this is an adequate approximation; allow
>> GDB to read from memory while it figures out the address of the
>> symbol. */
>> - while (own_buf[0] == 'm')
>> + while (1)
>
> Comment above is stale.
>
> OK with those addressed.
Thanks, fixed and pushed.
>
> Thanks,
> Pedro Alves
>
prev parent reply other threads:[~2016-03-29 23:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-12 15:02 Marcin Kościelnicki
2016-03-29 21:49 ` Marcin Kościelnicki
2016-03-29 22:00 ` Pedro Alves
2016-03-29 23:51 ` Marcin Kościelnicki [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=56FB1504.6070202@0x04.net \
--to=koriakin@0x04.net \
--cc=gdb-patches@sourceware.org \
--cc=palves@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