From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: mark.kettenis@xs4all.nl (Mark Kettenis)
Cc: gdb-patches@sourceware.org, binutils@sourceware.org
Subject: Re: [rfc][1/3] Remote core file generation: BFD support
Date: Fri, 21 Oct 2011 20:58:00 -0000 [thread overview]
Message-ID: <201110212053.p9LKrcAn022020@d06av02.portsmouth.uk.ibm.com> (raw)
In-Reply-To: <201110211951.p9LJpOQk022852@glazunov.sibelius.xs4all.nl> from "Mark Kettenis" at Oct 21, 2011 09:51:24 PM
Mark Kettenis wrote:
> > The patch in addition implements the callback for ARM Linux.
>
> There's a bit of a problem with this diff. You're installing the
> callback into the generic ARM vector, but the notes you're writing out
> are (almost certainly) Linux-specific.
Well, the routine is used to write notes named "CORE" with a note type
that is passed in as parameter (NT_PRPSINFO or NT_PRSTATUS). I think
the only OS on ARM that uses this particular note name/type is Linux.
(OpenBSD for example uses completely different notes ...)
Do you know of any OS that uses a note of the same name and type,
but with different contents?
Interestingly enough, at the same place where I installed the new
routine, routines to *read* those core file notes were already present
(elf32_arm_nabi_grok_prstatus, elf32_arm_nabi_grok_psinfo).
Also, the PPC implementation of elf_backend_write_core_note is likewise
installed into the generic PowerPC vector.
Bye,
Ulrich
--
Dr. Ulrich Weigand
GNU Toolchain for Linux on System z and Cell BE
Ulrich.Weigand@de.ibm.com
next prev parent reply other threads:[~2011-10-21 20:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-21 18:57 Ulrich Weigand
2011-10-21 20:37 ` Mark Kettenis
2011-10-21 20:58 ` Ulrich Weigand [this message]
2011-11-09 16:00 ` Pedro Alves
2011-11-09 18:18 ` Ulrich Weigand
2012-01-16 23:23 ` Alan Modra
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=201110212053.p9LKrcAn022020@d06av02.portsmouth.uk.ibm.com \
--to=uweigand@de.ibm.com \
--cc=binutils@sourceware.org \
--cc=gdb-patches@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
/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