From: gdb-buildbot@sergiodj.net
To: Nick Clifton <nickc@redhat.com>, gdb-patches@sourceware.org
Subject: Breakage on builder Fedora-x86_64-m32, revision a67d66eb97e7613a38ffe6622d837303b3ecd31d
Date: Wed, 01 Nov 2017 15:27:00 -0000 [thread overview]
Message-ID: <E1e9uvo-0008Rx-9J@kwanyin.sergiodj.net> (raw)
In-Reply-To: <a67d66eb97e7613a38ffe6622d837303b3ecd31d-master-breakage@gdb-build>
Unfortunately it seems that there is a breakage on GDB.
Commit title: 'Prevent illegal memory accesses when attempting to read excessively large COFF line number tables.'
Revision: a67d66eb97e7613a38ffe6622d837303b3ecd31d
You can find more details below:
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Buildslave:
fedora-x86-64-1
Full Build URL:
<http://gdb-build.sergiodj.net/builders/Fedora-x86_64-m32/builds/7809>
Commit(s) tested:
a67d66eb97e7613a38ffe6622d837303b3ecd31d
Author(s) (in the same order as the commits):
Nick Clifton <nickc@redhat.com>
Subject:
Prevent illegal memory accesses when attempting to read excessively large COFF line number tables.
Testsuite log (gdb.sum and gdb.log) URL(s):
<http://gdb-build.sergiodj.net/results/Fedora-x86_64-m32/a6/a67d66eb97e7613a38ffe6622d837303b3ecd31d/>
*** Internal error on buildslave (no space left on device). ***
*** Please report this to the buildslave owner (see <http://gdb-build.sergiodj.net//buildslaves/fedora-x86-64-1>) ***
*** Failed to compiled GDB. ***
============================
../../binutils-gdb/readline/complete.c:701:12: warning: implicit declaration of function wcwidth; did you mean fnwidth? [-Wimplicit-function-declaration]
../../binutils-gdb/readline/display.c:768:15: warning: implicit declaration of function wcwidth [-Wimplicit-function-declaration]
../../binutils-gdb/readline/mbutil.c:122:12: warning: implicit declaration of function wcwidth [-Wimplicit-function-declaration]
Setting warning flags = -W -Wall -Wstrict-prototypes -Wmissing-prototypes -Wshadow -Wstack-usage=262144 -Werror
checking for cos in -lm... Setting warning flags = -W -Wall -Wstrict-prototypes -Wmissing-prototypes -Wshadow -Wstack-usage=262144 -Werror
checking compiler warning flags... -Wall -Wpointer-arith -Wno-unused -Wunused-value -Wunused-function -Wno-switch -Wno-char-subscripts -Wempty-body -Wunused-but-set-parameter -Wunused-but-set-variable -Wno-sign-compare -Wno-narrowing -Wno-error=maybe-uninitialized -Werror
checking compiler warning flags... -Wall -Wpointer-arith -Wno-unused -Wunused-value -Wunused-function -Wno-switch -Wno-char-subscripts -Wempty-body -Wunused-but-set-parameter -Wunused-but-set-variable -Wno-sign-compare -Wno-narrowing -Wno-error=maybe-uninitialized -Werror
============================
next prev parent reply other threads:[~2017-11-01 15:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-01 15:27 Oh dear. I regret to inform you that commit a67d66eb97e7613a38ffe6622d837303b3ecd31d might be unfortunate gdb-buildbot
2017-11-01 15:27 ` gdb-buildbot [this message]
2017-11-01 15:27 ` Breakage on builder Fedora-i686, revision a67d66eb97e7613a38ffe6622d837303b3ecd31d 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=E1e9uvo-0008Rx-9J@kwanyin.sergiodj.net \
--to=gdb-buildbot@sergiodj.net \
--cc=gdb-patches@sourceware.org \
--cc=nickc@redhat.com \
/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: link
Be 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