Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Aleksandar Ristovski <aristovski@qnx.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch/doc] ptid from core section
Date: Fri, 05 Jun 2009 15:04:00 -0000	[thread overview]
Message-ID: <E1MCaxW-00062z-K9@fencepost.gnu.org> (raw)
In-Reply-To: <h0b5ef$j8p$1@ger.gmane.org> (message from Aleksandar Ristovski 	on Fri, 05 Jun 2009 09:09:34 -0400)

> From:  Aleksandar Ristovski <aristovski@qnx.com>
> Date:  Fri, 05 Jun 2009 09:09:34 -0400
> 
> Providing 
> http://sourceware.org/ml/gdb-patches/2009-06/msg00079.html 
> gets approved, this patch adds a clue about new callbacks in 
> internal gdb documentation.

Thanks.  However,

>  Once BFD support is available, writing the apropriate
> -@code{regset_from_core_section} architecture function should be all
> +@code{regset_from_core_section} and optionally
> +@code{ptid_from_core_section_name} and @code{core_section_name_from_ptid}
> +architecture functions should be all
>  that is needed in order to add support for core files in @value{GDBN}.

this say that the latter two APIs are optional, but does not say a
word when would the programmer want to define these optional APIs and
what would she lose if she doesn't.  Can you find a concise way of
saying that without getting into too elaborate details?


  reply	other threads:[~2009-06-05 15:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-05 13:10 Aleksandar Ristovski
2009-06-05 15:04 ` Eli Zaretskii [this message]
2009-06-05 15:38   ` Aleksandar Ristovski
2009-06-06  0:40     ` Eli Zaretskii

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=E1MCaxW-00062z-K9@fencepost.gnu.org \
    --to=eliz@gnu.org \
    --cc=aristovski@qnx.com \
    --cc=gdb-patches@sources.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