public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "joel.sherrill at oarcorp dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/26758] New: gdb master fails to build on Cygwin Date: Mon, 19 Oct 2020 22:33:52 +0000 [thread overview] Message-ID: <bug-26758-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=26758 Bug ID: 26758 Summary: gdb master fails to build on Cygwin Product: gdb Version: HEAD Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: joel.sherrill at oarcorp dot com Target Milestone: --- Hash: 22cc388e2b940608d4d759dc61c0335cfc621de1 (19 Oct 2020 master Output: configure && make make[2]: Entering directory '/home/jrs007/test-gcc/b-native/gdbserver' CXX server.o ../../binutils-gdb/gdbserver/server.cc: In function ‘void handle_general_set(char*)’: ../../binutils-gdb/gdbserver/server.cc:832:12: error: ‘sprintf’ argument 3 overlaps destination object ‘own_buf’ [-Werror=restrict] 832 | sprintf (own_buf, "E.Unknown thread-events mode requested: %s\n", | ~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 833 | mode); | ~~~~~ ../../binutils-gdb/gdbserver/server.cc:553:27: note: destination object referenced by ‘restrict’-qualified argument 1 was declared here 553 | handle_general_set (char *own_buf) | ~~~~~~^~~~~~~ -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2020-10-19 22:33 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-10-19 22:33 joel.sherrill at oarcorp dot com [this message] 2020-10-20 12:20 ` [Bug gdb/26758] " cbiesinger at google dot com 2020-10-21 15:08 ` cbiesinger at google dot com 2020-10-22 22:16 ` joel.sherrill at oarcorp dot com
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=bug-26758-4717@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@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).