public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: uweigand@de.ibm.com
Cc: gdb-patches@sourceware.org, binutils@sourceware.org
Subject: Re: [rfc][1/3] Remote core file generation: BFD support
Date: Fri, 21 Oct 2011 19:54:00 -0000	[thread overview]
Message-ID: <201110211951.p9LJpOQk022852@glazunov.sibelius.xs4all.nl> (raw)
In-Reply-To: <201110211856.p9LIu92B012443@d06av02.portsmouth.uk.ibm.com>	(uweigand@de.ibm.com)

> 
> Hello,
> 
> when implementing support for core file generation with remote targets
> in GDB I ran into the problem that the elfcore_write_prpsinfo and
> elfcore_write_prstatus are only defined for native targets.  This is
> even though they could be implemented for remote targets if the
> back-end provides the backend_write_core_note callback.
> 
> The following patch provides those functions unconditionally, so that
> they can use the back-end callback if present, and return NULL to
> signal failure if the callback is not available.
> 
> 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.

  reply	other threads:[~2011-10-21 19:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-21 18:56 Ulrich Weigand
2011-10-21 19:54 ` Mark Kettenis [this message]
2011-10-21 20:53   ` Ulrich Weigand
2011-11-09 16:00 ` Pedro Alves
2011-11-09 18:18   ` Ulrich Weigand
2012-01-16 22:31     ` 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=201110211951.p9LJpOQk022852@glazunov.sibelius.xs4all.nl \
    --to=mark.kettenis@xs4all.nl \
    --cc=binutils@sourceware.org \
    --cc=gdb-patches@sourceware.org \
    --cc=uweigand@de.ibm.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).