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] PR23595, simple objcopy of executable failure for msp430-elf Date: Tue, 04 Sep 2018 18:26:00 -0000 [thread overview] Message-ID: <2542e49e21e6b7270f72c7be0fc4ff1a986371da@gdb-build> (raw) *** TEST RESULTS FOR COMMIT 2542e49e21e6b7270f72c7be0fc4ff1a986371da *** Author: Jozef Lawrynowicz <jozef.l@mittosystems.com> Branch: master Commit: 2542e49e21e6b7270f72c7be0fc4ff1a986371da PR23595, simple objcopy of executable failure for msp430-elf VMA of the first section in the segment containing the ELF file header (and possibly section headers too) can't be used to reliably find the size of the headers plus padding. What's really needed is sh_offset of the first section assuming it has contents (vma does have a relationship to sh_offset, but is only guaranteed in demand paged executables). If the first section is SHT_NOBITS and it hasn't been converted to have file contents by the existence of a following SHT_PROGBITS section in the same segment, the sh_offset value also isn't reliable. PR 23595 elf.c (copy_elf_program_header): When first segment contains only the headers and SHT_NOBITS sections, use segment p_filesz to calculate header and padding size. Use filepos of the first section otherwise.
next reply other threads:[~2018-09-03 8:38 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-09-04 18:26 sergiodj+buildbot [this message] 2018-09-04 18:33 ` *** COMPILATION FAILED *** Failures on Debian-s390x-native-extended-gdbserver-m64, branch master *** BREAKAGE *** sergiodj+buildbot 2018-09-04 18:34 ` *** COMPILATION FAILED *** Failures on RHEL-s390x-m64, " sergiodj+buildbot 2018-09-04 18:39 ` *** COMPILATION FAILED *** Failures on Debian-s390x-m64, " sergiodj+buildbot 2018-09-04 18:39 ` *** COMPILATION FAILED *** Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot 2018-09-04 18:40 ` Failures on Fedora-i686, branch master sergiodj+buildbot 2018-09-04 18:55 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot 2018-09-04 18:57 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot 2018-09-04 19:02 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot 2018-09-04 19:11 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot 2018-09-04 19:13 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot 2018-09-04 19:23 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot 2018-09-04 19:25 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot 2018-09-10 0:20 ` Failures on Fedora-s390x-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=2542e49e21e6b7270f72c7be0fc4ff1a986371da@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).