Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: dje@google.com (Doug Evans)
To: gdb-patches@sourceware.org, binutils@sourceware.org
Subject: [RFC] Add support for .debug_gdb_scripts to mach-o.
Date: Wed, 28 Dec 2011 00:35:00 -0000	[thread overview]
Message-ID: <20111228002342.D4E232461C9@ruffy.mtv.corp.google.com> (raw)

Hi.

I have no means of testing this.
And it's not clear that adding .debug_gdb_scripts to dwarf_section_names_xlat
is reasonable.

Can anyone using mach-o test this, or suggest a better fix?
There is a testcase for .debug_gdb_scripts in
gdb/testsuite/gdb.python/py-section-script.exp
but I'm not sure it'll work as is on mach-o.

TIA

2011-12-27  Doug Evans  <dje@google.com>

	* mach-o.c (dwarf_section_names_xlat): Add .debug_gdb_scripts.

Index: mach-o.c
===================================================================
RCS file: /cvs/src/src/bfd/mach-o.c,v
retrieving revision 1.81
diff -u -p -r1.81 mach-o.c
--- mach-o.c	19 Dec 2011 15:42:36 -0000	1.81
+++ mach-o.c	28 Dec 2011 00:15:14 -0000
@@ -195,6 +195,9 @@ static const mach_o_section_name_xlat dw
     {	".debug_macro",			"__debug_macro",
 	SEC_DEBUGGING,			BFD_MACH_O_S_REGULAR,
 	BFD_MACH_O_S_ATTR_DEBUG,	0},
+    {	".debug_gdb_scripts",		"__debug_gdb_scr",
+	SEC_DEBUGGING,			BFD_MACH_O_S_REGULAR,
+	BFD_MACH_O_S_ATTR_DEBUG,	0},
     { NULL, NULL, 0, 0, 0, 0}
   };
 


             reply	other threads:[~2011-12-28  0:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-28  0:35 Doug Evans [this message]
2011-12-31 20:11 ` Iain Sandoe
2012-01-01 19:07   ` Iain Sandoe

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=20111228002342.D4E232461C9@ruffy.mtv.corp.google.com \
    --to=dje@google.com \
    --cc=binutils@sourceware.org \
    --cc=gdb-patches@sourceware.org \
    /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