This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [patch/doc] ptid from core section
- From: Eli Zaretskii <eliz at gnu dot org>
- To: Aleksandar Ristovski <aristovski at qnx dot com>
- Cc: gdb-patches at sources dot redhat dot com
- Date: Fri, 05 Jun 2009 11:03:54 -0400
- Subject: Re: [patch/doc] ptid from core section
- References: <h0b5ef$j8p$1@ger.gmane.org>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> 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?