public inbox for gdb-testers@sourceware.org help / color / mirror / Atom feed
From: sergiodj+buildbot@sergiodj.net To: gdb-testers@sourceware.org Subject: [binutils-gdb] Fix gdb.reverse/next-reverse-bkpt-over-sr.exp Date: Thu, 07 Apr 2016 16:55:00 -0000 [thread overview] Message-ID: <bde475616e3fdb6d41c047956aaf627fbf34a85d@gdb-build> (raw) *** TEST RESULTS FOR COMMIT bde475616e3fdb6d41c047956aaf627fbf34a85d *** Author: Yao Qi <yao.qi@linaro.org> Branch: master Commit: bde475616e3fdb6d41c047956aaf627fbf34a85d Fix gdb.reverse/next-reverse-bkpt-over-sr.exp I see the fail on aarch64-linux, (gdb) reverse-next Breakpoint 2, callee () at /home/yao/SourceCode/gnu/gdb/git/gdb/testsuite/gdb.reverse/step-reverse.c:26^M 26 myglob++; return 0; /* ARRIVED IN CALLEE */ (gdb) FAIL: gdb.reverse/next-reverse-bkpt-over-sr.exp: reverse-next over call trips user breakpoint at function entry The test expects program stops at line 25, but program stops at line 26. (gdb) maintenance info line-table objfile: /scratch/yao/gdb/build-git/aarch64-linux-gnu/gdb/testsuite/outputs/gdb.reverse/next-reverse-bkpt-over-sr/next-reverse-bkpt-over-sr ((struct objfile *) 0x613000002880) compunit_symtab: ((struct compunit_symtab *) 0x621000121760) symtab: /home/yao/SourceCode/gnu/gdb/git/gdb/testsuite/gdb.reverse/step-reverse.c ((struct symtab *) 0x6210001217e0) linetable: ((struct linetable *) 0x6210001520d0): INDEX LINE ADDRESS 0 25 0x0000000000400890 1 26 0x0000000000400890 2 27 0x00000000004008b0 (gdb) disassemble callee Dump of assembler code for function callee: 0x0000000000400890 <+0>: adrp x0, 0x410000 0x0000000000400894 <+4>: add x0, x0, #0xcac the line-table show that the first instruction of function callee is mapped line 25 and 26. I am not sure the line-table is correct, but it is not the point of this test. The goal of this test is to test program hits the breakpoint on the first instruction of function after 'reverse-next', so I change this test to expect the breakpoint number the program hits. gdb/testsuite: 2016-04-07 Yao Qi <yao.qi@linaro.org> * gdb.reverse/next-reverse-bkpt-over-sr.exp: Match the breakpoint number instead of the comments on some line.
next reply other threads:[~2016-04-07 16:55 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2016-04-07 16:55 sergiodj+buildbot [this message] 2016-04-07 16:55 ` Failures on Fedora-i686, branch master sergiodj+buildbot 2016-04-07 17:34 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot 2016-04-07 17:49 ` Failures on Debian-i686, " sergiodj+buildbot 2016-04-07 17:58 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot 2016-04-07 18:11 ` Failures on Debian-s390x-m64, " sergiodj+buildbot 2016-04-07 18:15 ` Failures on Debian-i686-native-extended-gdbserver, " sergiodj+buildbot 2016-04-07 18:20 ` Failures on Debian-x86_64-m64, " sergiodj+buildbot 2016-04-07 18:50 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot 2016-04-07 18:53 ` Failures on Fedora-ppc64be-cc-with-index, " sergiodj+buildbot 2016-04-07 20:26 ` Failures on Fedora-ppc64le-native-extended-gdbserver-m64, " sergiodj+buildbot
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=bde475616e3fdb6d41c047956aaf627fbf34a85d@gdb-build \ --to=sergiodj+buildbot@sergiodj.net \ --cc=gdb-testers@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: linkBe 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; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).