Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Aleksandar Ristovski <aristovski@qnx.com>
To: gdb-patches@sources.redhat.com
Subject: [patch/doc] ptid from core section
Date: Fri, 05 Jun 2009 13:10:00 -0000	[thread overview]
Message-ID: <h0b5ef$j8p$1@ger.gmane.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 376 bytes --]

Hello,

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,

-- 
Aleksandar Ristovski
QNX Software Systems


* doc/gdbinit.texinfo (Adding support for debugging core files):
Add information about ptid_from_core_section_name and
core_section_name_from_ptid.


[-- Attachment #2: corelow.c-pid-from-section-doc-20090604.diff --]
[-- Type: text/x-patch, Size: 814 bytes --]

Index: gdb/doc/gdbint.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdbint.texinfo,v
retrieving revision 1.303
diff -u -p -r1.303 gdbint.texinfo
--- gdb/doc/gdbint.texinfo	7 May 2009 18:40:43 -0000	1.303
+++ gdb/doc/gdbint.texinfo	4 Jun 2009 16:15:09 -0000
@@ -4429,7 +4429,9 @@ The prerequisite for adding core file su
 core file support in BFD.
 
 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}.
 
 @node Defining Other Architecture Features 

             reply	other threads:[~2009-06-05 13:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-05 13:10 Aleksandar Ristovski [this message]
2009-06-05 15:04 ` Eli Zaretskii
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='h0b5ef$j8p$1@ger.gmane.org' \
    --to=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