This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[RFC] Add support for .debug_gdb_scripts to mach-o.


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}
   };
 


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]