diff options
| -rw-r--r-- | gdb/testsuite/ChangeLog | 6 | ||||
| -rw-r--r-- | gdb/testsuite/gdb.guile/scm-section-script.c | 8 | ||||
| -rw-r--r-- | gdb/testsuite/gdb.python/py-section-script.c | 8 |
3 files changed, 14 insertions, 8 deletions
diff --git a/gdb/testsuite/ChangeLog b/gdb/testsuite/ChangeLog index 7ba90d7..08a699d 100644 --- a/gdb/testsuite/ChangeLog +++ b/gdb/testsuite/ChangeLog @@ -1,3 +1,9 @@ +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. diff --git a/gdb/testsuite/gdb.guile/scm-section-script.c b/gdb/testsuite/gdb.guile/scm-section-script.c index ddd4538..0f19613 100644 --- a/gdb/testsuite/gdb.guile/scm-section-script.c +++ b/gdb/testsuite/gdb.guile/scm-section-script.c @@ -21,12 +21,12 @@ /* 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\ @@ -43,12 +43,12 @@ DEFINE_GDB_SCRIPT (SCRIPT_FILE) /* 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" \ diff --git a/gdb/testsuite/gdb.python/py-section-script.c b/gdb/testsuite/gdb.python/py-section-script.c index 298698d..eb689a7 100644 --- a/gdb/testsuite/gdb.python/py-section-script.c +++ b/gdb/testsuite/gdb.python/py-section-script.c @@ -21,12 +21,12 @@ /* 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\ @@ -43,12 +43,12 @@ DEFINE_GDB_SCRIPT_FILE (SCRIPT_FILE) /* 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" \ |