Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Kamil Rytarowski <kamil@netbsd.org>
To: Simon Marchi <simark@simark.ca>,
	Kamil Rytarowski <kamil@netbsd.org>,
	gdb-patches@sourceware.org
Subject: Re: [PATCH] Implement xfer_partial TARGET_OBJECT_SIGNAL_INFO for NetBSD
Date: Tue, 28 Jul 2020 17:17:47 +0200	[thread overview]
Message-ID: <f4ab04fa-403c-c66a-56f7-73a8c0582ac9@netbsd.org> (raw)
In-Reply-To: <1ba798b7-5e10-ad24-bc4d-1ab05e5c58c2@simark.ca>


[-- Attachment #1.1: Type: text/plain, Size: 1441 bytes --]

On 28.07.2020 17:15, Simon Marchi wrote:
> On 2020-07-28 11:07 a.m., Kamil Rytarowski wrote:
>> This looks like a generic GDB bug wiith this arch_composite_type vs
>> arch_type. For now, I have used set_name + gdbarch_obstack_strdup.
>>
>> Feel free to fix the problem in GDB later and pass the name directly in
>> arch_composite_type.
> 
> I mean, you could easily use for now:
> 
>   arch_composite_type (..., gdbarch_obstack_strdup (name), ...);
> 
> Simon
> 

I know, I decided to go for set_name as it will be more agnostic to
further possible arch_composite_type() changes.

On 28.07.2020 17:17, Simon Marchi wrote:
> On 2020-07-28 11:04 a.m., Kamil Rytarowski wrote:
>> diff --git a/gdb/nbsd-nat.c b/gdb/nbsd-nat.c
>> index a9405ebf862..bdf3388de0b 100644
>> --- a/gdb/nbsd-nat.c
>> +++ b/gdb/nbsd-nat.c
>> @@ -845,3 +845,48 @@ nbsd_nat_target::supports_multi_process ()
>>  {
>>    return true;
>>  }
>> +
>> +/* Implement the "xfer_partial" target_ops method.  */
>> +
>> +enum target_xfer_status
>> +nbsd_nat_target::xfer_partial (enum target_object object,
>> +                               const char *annex, gdb_byte *readbuf,
>> +                               const gdb_byte *writebuf,
>> +                               ULONGEST offset, ULONGEST len,
>> +                               ULONGEST *xfered_len)
> Spaces here.


I'm going to fix this.

Is this patch good otherwise?


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2020-07-28 15:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-27  7:41 Kamil Rytarowski
2020-07-27 15:42 ` John Baldwin
2020-07-28 13:26 ` Simon Marchi
2020-07-28 15:07   ` Kamil Rytarowski
2020-07-28 15:15     ` Simon Marchi
2020-07-28 15:17       ` Kamil Rytarowski [this message]
2020-07-28 15:21         ` Simon Marchi
2020-07-28 15:04 ` [PATCH v2] " Kamil Rytarowski
2020-07-28 15:17   ` Simon Marchi
2020-07-28 15:58   ` [PATCH v3] " Kamil Rytarowski
2020-07-28 16:21     ` Simon Marchi

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=f4ab04fa-403c-c66a-56f7-73a8c0582ac9@netbsd.org \
    --to=kamil@netbsd.org \
    --cc=gdb-patches@sourceware.org \
    --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