+2016-01-18 Yao Qi <yao.qi@linaro.org>
+
+ * gdb.guile/scm-section-script.c: Replace @progbits with
+ %progbits.
+ * gdb.python/py-section-script.c: Likewise.
+
2016-01-15 Pedro Alves <palves@redhat.com>
* gdb.multi/tids.exp: Test star wildcard ranges.
/* Put the path to the pretty-printer script in .debug_gdb_scripts so
gdb will automagically loaded it.
Normally "MS" would appear here, as in
- .pushsection ".debug_gdb_scripts", "MS",@progbits,1
+ .pushsection ".debug_gdb_scripts", "MS",%progbits,1
but we remove it to test files appearing twice in the section. */
#define DEFINE_GDB_SCRIPT(script_name) \
asm("\
-.pushsection \".debug_gdb_scripts\", \"S\",@progbits\n\
+.pushsection \".debug_gdb_scripts\", \"S\",%progbits\n\
.byte " XSTRING (SECTION_SCRIPT_ID_SCHEME_FILE) "\n\
.asciz \"" script_name "\"\n\
.popsection \n\
/* Inlined scripts are harder to create in the same way as
DEFINE_GDB_SCRIPT_FILE. Keep things simple and just define it here.
Normally "MS" would appear here, as in
- .pushsection ".debug_gdb_scripts", "MS",@progbits,1
+ .pushsection ".debug_gdb_scripts", "MS",%progbits,1
but we remove it to test scripts appearing twice in the section. */
#define DEFINE_GDB_SCRIPT_TEXT \
asm( \
-".pushsection \".debug_gdb_scripts\", \"S\",@progbits\n" \
+".pushsection \".debug_gdb_scripts\", \"S\",%progbits\n" \
".byte " XSTRING (SECTION_SCRIPT_ID_SCHEME_TEXT) "\n" \
".ascii \"gdb.inlined-script\\n\"\n" \
".ascii \"(define test-cmd\\n\"\n" \
/* Put the path to the pretty-printer script in .debug_gdb_scripts so
gdb will automagically loaded it.
Normally "MS" would appear here, as in
- .pushsection ".debug_gdb_scripts", "MS",@progbits,1
+ .pushsection ".debug_gdb_scripts", "MS",%progbits,1
but we remove it to test files appearing twice in the section. */
#define DEFINE_GDB_SCRIPT_FILE(script_name) \
asm("\
-.pushsection \".debug_gdb_scripts\", \"S\",@progbits\n\
+.pushsection \".debug_gdb_scripts\", \"S\",%progbits\n\
.byte " XSTRING (SECTION_SCRIPT_ID_PYTHON_FILE) "\n\
.asciz \"" script_name "\"\n\
.popsection\n\
/* Inlined scripts are harder to create in the same way as
DEFINE_GDB_SCRIPT_FILE. Keep things simple and just define it here.
Normally "MS" would appear here, as in
- .pushsection ".debug_gdb_scripts", "MS",@progbits,1
+ .pushsection ".debug_gdb_scripts", "MS",%progbits,1
but we remove it to test scripts appearing twice in the section. */
#define DEFINE_GDB_SCRIPT_TEXT \
asm( \
-".pushsection \".debug_gdb_scripts\", \"S\",@progbits\n" \
+".pushsection \".debug_gdb_scripts\", \"S\",%progbits\n" \
".byte " XSTRING (SECTION_SCRIPT_ID_PYTHON_TEXT) "\n" \
".ascii \"gdb.inlined-script\\n\"\n" \
".ascii \"class test_cmd (gdb.Command):\\n\"\n" \