public inbox for gdb-testers@sourceware.org help / color / mirror / Atom feed
From: gdb-buildbot@sergiodj.net To: gdb-testers@sourceware.org Subject: [binutils-gdb] gdb/testsuite: Allow DWARF assembler to create multiple line tables Date: Tue, 14 Jan 2020 06:48:00 -0000 [thread overview] Message-ID: <d93c6db74b7a9d6154f55f92d96f38819838bc99@gdb-build> (raw) *** TEST RESULTS FOR COMMIT d93c6db74b7a9d6154f55f92d96f38819838bc99 *** commit d93c6db74b7a9d6154f55f92d96f38819838bc99 Author: Andrew Burgess <andrew.burgess@embecosm.com> AuthorDate: Fri Dec 6 21:35:18 2019 +0000 Commit: Andrew Burgess <andrew.burgess@embecosm.com> CommitDate: Mon Jan 13 23:56:02 2020 +0000 gdb/testsuite: Allow DWARF assembler to create multiple line tables Fixes a bug in the DWARF assembler that prevents multiple line tables from being created in a test. We currently don't initialise a couple of flags, as a result we will only ever generate one end of file list, and one end of header, in the first line table. Any additional line tables will be missing these parts, and will therefore be corrupt. This fix will be required for a later commit. There should be no change in the testsuite after this commit. gdb/testsuite/ChangeLog: * lib/dwarf.exp (Dwarf::lines): Reset _line_saw_program and _line_saw_file. Change-Id: Id7123f217a036f26ee32d608db3064dd43164596 diff --git a/gdb/testsuite/ChangeLog b/gdb/testsuite/ChangeLog index 10d7cbec07..4209c5757c 100644 --- a/gdb/testsuite/ChangeLog +++ b/gdb/testsuite/ChangeLog @@ -1,3 +1,8 @@ +2020-01-13 Andrew Burgess <andrew.burgess@embecosm.com> + + * lib/dwarf.exp (Dwarf::lines): Reset _line_saw_program and + _line_saw_file. + 2020-01-13 Andrew Burgess <andrew.burgess@embecosm.com> * lib/tuiterm.exp (Term::_check_box): Check some parts of the top diff --git a/gdb/testsuite/lib/dwarf.exp b/gdb/testsuite/lib/dwarf.exp index da9763e00e..6c6ffbe7c2 100644 --- a/gdb/testsuite/lib/dwarf.exp +++ b/gdb/testsuite/lib/dwarf.exp @@ -1309,6 +1309,8 @@ namespace eval Dwarf { set is_64 0 set _unit_version 4 set _unit_addr_size default + set _line_saw_program 0 + set _line_saw_file 0 foreach { name value } $options { switch -exact -- $name {
next reply other threads:[~2020-01-14 6:41 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-01-14 6:48 gdb-buildbot [this message] 2020-01-14 6:57 ` Failures on Ubuntu-Aarch64-native-extended-gdbserver-m64, branch master gdb-buildbot 2020-01-14 7:42 ` Failures on Ubuntu-Aarch64-native-gdbserver-m64, " gdb-buildbot 2020-01-16 9:21 ` Failures on Fedora-x86_64-m32, " gdb-buildbot 2020-01-16 9:29 ` Failures on Fedora-x86_64-cc-with-index, " gdb-buildbot 2020-01-16 9:29 ` Failures on Fedora-i686, " gdb-buildbot 2020-01-16 10:00 ` Failures on Fedora-x86_64-m64, " gdb-buildbot 2020-01-16 10:09 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " gdb-buildbot 2020-01-16 10:20 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " gdb-buildbot 2020-01-16 10:29 ` Failures on Fedora-x86_64-native-gdbserver-m32, " gdb-buildbot 2020-01-16 10:29 ` Failures on Fedora-x86_64-native-gdbserver-m64, " gdb-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=d93c6db74b7a9d6154f55f92d96f38819838bc99@gdb-build \ --to=gdb-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).