From: "Christian Biesinger via gdb-patches" <gdb-patches@sourceware.org>
To: Kamil Rytarowski <n54@gmx.com>
Cc: gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH 2/3 v2] Define _KMEMUSER in arm-nbsd-nat.c
Date: Mon, 27 Jan 2020 21:28:00 -0000 [thread overview]
Message-ID: <CAPTJ0XHMQD17ygQPpv5tkuwjzCdJ=iN9X=JVocu9sbduM7xd+g@mail.gmail.com> (raw)
In-Reply-To: <7a00a471-ab23-a235-d9bb-1d5d574bdacd@gmx.com>
On Fri, Jan 24, 2020 at 5:37 PM Kamil Rytarowski <n54@gmx.com> wrote:
>
> On 24.01.2020 17:01, Christian Biesinger wrote:
> > On Fri, Jan 24, 2020 at 4:49 PM Kamil Rytarowski <n54@gmx.com> wrote:
> >>
> >> On 24.01.2020 16:35, Christian Biesinger via gdb-patches wrote:
> >>> On Fri, Jan 24, 2020 at 4:23 PM Kamil Rytarowski <n54@gmx.com> wrote:
> >>>>
> >>>> On 24.01.2020 15:53, Christian Biesinger via gdb-patches wrote:
> >>>>> Hi Kamil,
> >>>>>
> >>>>> I have a related question. NetBSD applied this patch:
> >>>>> https://www.mail-archive.com/tech@openbsd.org/msg44100.html
> >>>>>
> >>>>
> >>>> Is this the right link?
> >>>
> >>> Yeah -- that patch changes a system header at the top and patches GDB
> >>> at the bottom.
> >>>
> >>
> >> This is not a change in NetBSD, so it is unrelated.
> >
> > My apologies, I completely misread that. I'll see if I can find where
> > NetBSD changed their FP register data structure, or perhaps your
> > downstream patch will still work (although that probably has to come
> > from one of y'all for copyright reasons?)
> >
>
> Please cherry-pick what you need and I will find the original author.
> Many people in NetBSD have FSF papers done.
Thanks. I think this patch would probably be the most important since
it fixes a compile error:
https://github.com/NetBSD/pkgsrc-wip/blob/master/gdb-netbsd/patches/patch-gdb_arm-nbsd-nat.c
However, I don't understand why arm_netbsd_core_fns /
fetch_core_registers was added. As far as I can tell, because that
struct uses bfd_target_unknown_flavour and default_core_sniffer, it
will never be used.
Christian
next prev parent reply other threads:[~2020-01-27 21:25 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-24 14:15 [PATCH 0/3] Fix some ARM NetBSD compile errors cbiesinger
2020-01-24 14:15 ` [PATCH 1/3] Support the NetBSD version of pthread_setname_np cbiesinger
2020-01-24 14:59 ` Kamil Rytarowski
2020-01-24 15:04 ` Tom Tromey
2020-01-24 14:15 ` [PATCH 3/3] Make the class name in the definition match the declaration cbiesinger
2020-01-24 14:54 ` Kamil Rytarowski
2020-01-24 15:06 ` Tom Tromey
2020-01-24 15:49 ` Christian Biesinger via gdb-patches
2020-01-24 14:18 ` [PATCH 2/3] Define _KMEMUSER in arm-nbsd-nat.c cbiesinger
2020-01-24 14:22 ` [PATCH 2/3 v2] " cbiesinger
2020-01-24 14:32 ` Kamil Rytarowski
2020-01-24 14:34 ` Christian Biesinger via gdb-patches
2020-01-24 14:36 ` [PATCH v3 2/3] Define _KERNTYPES " cbiesinger
2020-01-24 15:04 ` Tom Tromey
2020-01-24 14:58 ` [PATCH 2/3 v2] Define _KMEMUSER " Christian Biesinger via gdb-patches
2020-01-24 15:36 ` Kamil Rytarowski
2020-01-24 15:37 ` Christian Biesinger via gdb-patches
2020-01-24 15:49 ` Kamil Rytarowski
2020-01-24 16:25 ` Christian Biesinger via gdb-patches
2020-01-24 16:45 ` Kamil Rytarowski
2020-01-27 21:28 ` Christian Biesinger via gdb-patches [this message]
2020-02-05 18:02 ` Christian Biesinger via gdb-patches
2020-02-06 13:25 ` Kamil Rytarowski
2020-02-06 13:19 ` Kamil Rytarowski
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='CAPTJ0XHMQD17ygQPpv5tkuwjzCdJ=iN9X=JVocu9sbduM7xd+g@mail.gmail.com' \
--to=gdb-patches@sourceware.org \
--cc=cbiesinger@google.com \
--cc=n54@gmx.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