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/gdb-7.11-branch] Workaround gdbserver<7.7 for setfs Date: Wed, 27 Apr 2016 19:52:00 -0000 [thread overview] Message-ID: <a6ff23076f49c6322d96a76e0098f8019139bc4e@gdb-build> (raw) *** TEST RESULTS FOR COMMIT a6ff23076f49c6322d96a76e0098f8019139bc4e *** Author: Jan Kratochvil <jan.kratochvil@redhat.com> Branch: gdb-7.11-branch Commit: a6ff23076f49c6322d96a76e0098f8019139bc4e Workaround gdbserver<7.7 for setfs With current FSF GDB HEAD and old FSF gdbserver I expected I could do: gdb -ex 'file target:/root/redhat/threadit' -ex 'target remote :1234' (supplying that unsupported qXfer:exec-file:read by "file") But that does not work because: Sending packet: $vFile:setfs:0#bf...Packet received: OK Packet vFile:setfs (hostio-setfs) is supported ... Sending packet: $vFile:setfs:104#24...Packet received: OK "target:/root/redhat/threadit": could not open as an executable file: Invalid argument GDB documentation says: The valid responses to Host I/O packets are: An empty response indicates that this operation is not recognized. This "empty response" vs. "OK" was a bug in gdbserver < 7.7. It was fixed by: commit e7f0d979dd5cc4f8b658df892e93db69d6d660b7 Author: Yao Qi <yao@codesourcery.com> Date: Tue Dec 10 21:59:20 2013 +0800 Fix a bug in matching notifications. Message-ID: <1386684626-11415-1-git-send-email-yao@codesourcery.com> https://sourceware.org/ml/gdb-patches/2013-12/msg00373.html 2013-12-10 Yao Qi <yao@codesourcery.com> * notif.c (handle_notif_ack): Return 0 if no notification matches. with unpatched old FSF gdbserver and patched FSF GDB HEAD: gdb -ex 'file target:/root/redhat/threadit' -ex 'target remote :1234' Sending packet: $vFile:setfs:0#bf...Packet received: OK Packet vFile:setfs (hostio-setfs) is NOT supported ... (gdb) info sharedlibrary From To Syms Read Shared Object Library 0x00007ffff7ddbae0 0x00007ffff7df627a Yes (*) target:/lib64/ld-linux-x86-64.so.2 0x00007ffff7bc48a0 0x00007ffff7bcf514 Yes (*) target:/lib64/libpthread.so.0 gdb/ChangeLog 2016-04-27 Jan Kratochvil <jan.kratochvil@redhat.com> * remote.c (remote_start_remote): Detect PACKET_vFile_setfs.support.
next reply other threads:[~2016-04-27 19:52 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2016-04-27 19:52 sergiodj+buildbot [this message] 2016-04-27 19:52 ` Failures on RHEL-s390x-m64, branch gdb-7.11-branch sergiodj+buildbot 2016-04-27 20:09 ` Failures on Fedora-i686, " sergiodj+buildbot 2016-04-27 20:09 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot 2016-04-27 20:15 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot 2016-04-27 20:22 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot 2016-04-27 20:24 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot 2016-04-27 20:30 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot 2016-04-27 20:36 ` Failures on AIX-POWER7-plain, " sergiodj+buildbot 2016-04-27 20:42 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot 2016-04-27 21:17 ` Failures on Debian-i686-native-extended-gdbserver, " sergiodj+buildbot 2016-04-27 21:23 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot 2016-04-27 21:28 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot 2016-04-28 0:40 ` Failures on Fedora-ppc64be-m64, " sergiodj+buildbot 2016-04-28 1:00 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj+buildbot 2016-04-28 1:21 ` Failures on Fedora-ppc64be-native-extended-gdbserver-m64, " sergiodj+buildbot 2016-04-28 2:57 ` Failures on Fedora-ppc64le-native-extended-gdbserver-m64, " sergiodj+buildbot 2016-04-28 3:14 ` Failures on Fedora-ppc64le-native-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=a6ff23076f49c6322d96a76e0098f8019139bc4e@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).