Breakage on builder Fedora-x86_64-cc-with-index, revision e0115a844607b280449986e661f551dff49a9031

Breakage on builder Fedora-x86_64-cc-with-index, revision e0115a844607b280449986e661f551dff49a9031

[gdb-buildbot]

Unfortunately it seems that there is a breakage on GDB.

Commit title: 'Update check for invalid values in pe_bfd_read_buildid function.'
Revision: e0115a844607b280449986e661f551dff49a9031

You can find more details below:

+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

Buildslave:
	fedora-x86-64-2

Full Build URL:
	<http://gdb-build.sergiodj.net/builders/Fedora-x86_64-cc-with-index/builds/7760>

Commit(s) tested:
	e0115a844607b280449986e661f551dff49a9031

Author(s) (in the same order as the commits):
	Nick Clifton <nickc@redhat.com>

Subject:
	Update check for invalid values in pe_bfd_read_buildid function.

Testsuite log (gdb.sum and gdb.log) URL(s):
	<http://gdb-build.sergiodj.net/results/Fedora-x86_64-cc-with-index/e0/e0115a844607b280449986e661f551dff49a9031/>

*** 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-2>) ***

*** Failed to compiled GDB.  ***
============================
checking for suffix of executables... Setting warning flags = -W -Wall -Wstrict-prototypes -Wmissing-prototypes -Wshadow -Wstack-usage=262144 -Werror
checking for strings.h... Setting warning flags = -W -Wall -Wstrict-prototypes -Wmissing-prototypes -Wshadow -Wstack-usage=262144 -Werror
============================

Oh dear. I regret to inform you that commit e0115a844607b280449986e661f551dff49a9031 might be unfortunate

[gdb-buildbot]

My lords, ladies, gentlemen, members of the public.

It is a matter of great regret and sadness to inform you that commit:

	Update check for invalid values in pe_bfd_read_buildid function.
	e0115a844607b280449986e661f551dff49a9031

might have made GDB unwell.  Since I am just your Butler BuildBot,
I kindly ask that a human superior officer double-check this.

Please note that if you are reading this message on gdb-patches, there might
be other builders broken.

You can find more details about the unfortunate breakage in the next messages.

Cheers,

Your GDB BuildBot.