Breakage on builder NetBSD-x86_64-m64, revision 2e62ab400ff96334c92e5acf0a462cb9dc0d19a7

Breakage on builder NetBSD-x86_64-m64, revision 2e62ab400ff96334c92e5acf0a462cb9dc0d19a7

[gdb-buildbot]

Unfortunately it seems that there is a breakage on GDB.

Commit title: 'gdb: Introduce 'print max-depth' feature'
Revision: 2e62ab400ff96334c92e5acf0a462cb9dc0d19a7

You can find more details below:

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

Buildslave:
	gdb-amd64-netbsd7

Full Build URL:
	<http://gdb-build.sergiodj.net/builders/NetBSD-x86_64-m64/builds/6873>

Commit(s) tested:
	2e62ab400ff96334c92e5acf0a462cb9dc0d19a7

Author(s) (in the same order as the commits):
	Andrew Burgess <andrew.burgess@embecosm.com>

Subject:
	gdb: Introduce 'print max-depth' feature

Testsuite log (gdb.sum and gdb.log) URL(s):
	<http://gdb-build.sergiodj.net/results/NetBSD-x86_64-m64/2e/2e62ab400ff96334c92e5acf0a462cb9dc0d19a7/>

*** Failed to compiled GDB.  ***
============================

+++ The full log is too big to be posted here.
+++ These are the last 100 lines of it.

  CXX    common/buffer.o
  CXX    common/cleanups.o
  CXX    common/common-debug.o
  CXX    common/common-exceptions.o
  CXX    common/common-regcache.o
  CXX    common/common-utils.o
  CXX    common/environ.o
  CXX    common/errors.o
  CXX    common/fileio.o
  CXX    common/filestuff.o
  CXX    common/format.o
  CXX    common/gdb_tilde_expand.o
  CXX    common/gdb_vecs.o
  CXX    common/job-control.o
  CXX    common/netstuff.o
  CXX    common/new-op.o
  CXX    common/pathstuff.o
  CXX    common/posix-strerror.o
  CXX    common/print-utils.o
  CXX    common/ptid.o
  CXX    common/rsp-low.o
  CXX    common/run-time-clock.o
  CXX    common/scoped_mmap.o
  CXX    common/selftest.o
  CXX    common/signals-state-save-restore.o
  CXX    common/signals.o
  CXX    common/tdesc.o
  CXX    common/vec.o
  CXX    common/xml-utils.o
  CXX    compile/compile-c-support.o
  CXX    compile/compile-c-symbols.o
  CXX    compile/compile-c-types.o
  CXX    compile/compile-cplus-symbols.o
  CXX    compile/compile-cplus-types.o
  CXX    compile/compile-loc2c.o
  CXX    compile/compile-object-load.o
  CXX    compile/compile-object-run.o
  CXX    compile/compile.o
  CXX    complaints.o
  CXX    completer.o
  CXX    continuations.o
  CXX    copying.o
  CXX    corefile.o
  CXX    corelow.o
  CXX    cp-abi.o
  YACC   cp-name-parser.c
  CXX    cp-name-parser.o
  CXX    cp-namespace.o
  CXX    cp-support.o
  CXX    cp-valprint.o
  CXX    ctf.o
  YACC   d-exp.c
  CXX    d-exp.o
  CXX    d-lang.o
  CXX    d-namespace.o
  CXX    d-valprint.o
  CXX    dbxread.o
  CXX    dcache.o
  CXX    debug.o
  CXX    demangle.o
  CXX    dictionary.o
  CXX    disasm-selftests.o
  CXX    disasm.o
  CXX    dtrace-probe.o
  CXX    dummy-frame.o
  CXX    dwarf-index-cache.o
  CXX    dwarf-index-common.o
  CXX    dwarf-index-write.o
  CXX    dwarf2-frame-tailcall.o
  CXX    dwarf2-frame.o
  CXX    dwarf2expr.o
  CXX    dwarf2loc.o
  CXX    dwarf2read.o
  CXX    elfread.o
  CXX    eval.o
  CXX    event-loop.o
  CXX    event-top.o
  CXX    exceptions.o
  CXX    exec.o
  CXX    expprint.o
  CXX    extension.o
  YACC   f-exp.c
  CXX    f-exp.o
  CXX    f-lang.o
  CXX    f-typeprint.o
  CXX    f-valprint.o
  CXX    filename-seen-cache.o
  CXX    filesystem.o
  CXX    findcmd.o
  CXX    findvar.o
  CXX    fork-child.o
  CXX    frame-base.o
  CXX    frame-unwind.o
  CXX    frame.o
  CXX    gcore.o
  CXX    gdb-dlfcn.o
  CXX    gdb_bfd.o
  CXX    gdb_obstack.o
  CXX    gdb_regex.o
============================

Oh dear. I regret to inform you that commit 2e62ab400ff96334c92e5acf0a462cb9dc0d19a7 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:

	gdb: Introduce 'print max-depth' feature
	2e62ab400ff96334c92e5acf0a462cb9dc0d19a7

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.

Re: Breakage on builder NetBSD-x86_64-m64, revision 2e62ab400ff96334c92e5acf0a462cb9dc0d19a7

[Andrew Burgess]

* gdb-buildbot@sergiodj.net <gdb-buildbot@sergiodj.net> [2019-04-29 19:45:29 -0400]:

> Unfortunately it seems that there is a breakage on GDB.
> 
> Commit title: 'gdb: Introduce 'print max-depth' feature'
> Revision: 2e62ab400ff96334c92e5acf0a462cb9dc0d19a7
> 
> You can find more details below:
> 
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> 
> Buildslave:
> 	gdb-amd64-netbsd7
> 
> Full Build URL:
> 	<http://gdb-build.sergiodj.net/builders/NetBSD-x86_64-m64/builds/6873>
> 
> Commit(s) tested:
> 	2e62ab400ff96334c92e5acf0a462cb9dc0d19a7
> 
> Author(s) (in the same order as the commits):
> 	Andrew Burgess <andrew.burgess@embecosm.com>
> 
> Subject:
> 	gdb: Introduce 'print max-depth' feature
> 
> Testsuite log (gdb.sum and gdb.log) URL(s):
> 	<http://gdb-build.sergiodj.net/results/NetBSD-x86_64-m64/2e/2e62ab400ff96334c92e5acf0a462cb9dc0d19a7/>
> 
> *** Failed to compiled GDB.  ***
> ============================
> 
> +++ The full log is too big to be posted here.
> +++ These are the last 100 lines of it.
> 
>   CXX    common/buffer.o
>   CXX    common/cleanups.o
>   CXX    common/common-debug.o
>   CXX    common/common-exceptions.o
>   CXX    common/common-regcache.o
>   CXX    common/common-utils.o
>   CXX    common/environ.o
>   CXX    common/errors.o
>   CXX    common/fileio.o
>   CXX    common/filestuff.o
>   CXX    common/format.o
>   CXX    common/gdb_tilde_expand.o
>   CXX    common/gdb_vecs.o
>   CXX    common/job-control.o
>   CXX    common/netstuff.o
>   CXX    common/new-op.o
>   CXX    common/pathstuff.o
>   CXX    common/posix-strerror.o
>   CXX    common/print-utils.o
>   CXX    common/ptid.o
>   CXX    common/rsp-low.o
>   CXX    common/run-time-clock.o
>   CXX    common/scoped_mmap.o
>   CXX    common/selftest.o
>   CXX    common/signals-state-save-restore.o
>   CXX    common/signals.o
>   CXX    common/tdesc.o
>   CXX    common/vec.o
>   CXX    common/xml-utils.o
>   CXX    compile/compile-c-support.o
>   CXX    compile/compile-c-symbols.o
>   CXX    compile/compile-c-types.o
>   CXX    compile/compile-cplus-symbols.o
>   CXX    compile/compile-cplus-types.o
>   CXX    compile/compile-loc2c.o
>   CXX    compile/compile-object-load.o
>   CXX    compile/compile-object-run.o
>   CXX    compile/compile.o
>   CXX    complaints.o
>   CXX    completer.o
>   CXX    continuations.o
>   CXX    copying.o
>   CXX    corefile.o
>   CXX    corelow.o
>   CXX    cp-abi.o
>   YACC   cp-name-parser.c
>   CXX    cp-name-parser.o
>   CXX    cp-namespace.o
>   CXX    cp-support.o
>   CXX    cp-valprint.o
>   CXX    ctf.o
>   YACC   d-exp.c
>   CXX    d-exp.o
>   CXX    d-lang.o
>   CXX    d-namespace.o
>   CXX    d-valprint.o
>   CXX    dbxread.o
>   CXX    dcache.o
>   CXX    debug.o
>   CXX    demangle.o
>   CXX    dictionary.o
>   CXX    disasm-selftests.o
>   CXX    disasm.o
>   CXX    dtrace-probe.o
>   CXX    dummy-frame.o
>   CXX    dwarf-index-cache.o
>   CXX    dwarf-index-common.o
>   CXX    dwarf-index-write.o
>   CXX    dwarf2-frame-tailcall.o
>   CXX    dwarf2-frame.o
>   CXX    dwarf2expr.o
>   CXX    dwarf2loc.o
>   CXX    dwarf2read.o
>   CXX    elfread.o
>   CXX    eval.o
>   CXX    event-loop.o
>   CXX    event-top.o
>   CXX    exceptions.o
>   CXX    exec.o
>   CXX    expprint.o
>   CXX    extension.o
>   YACC   f-exp.c
>   CXX    f-exp.o
>   CXX    f-lang.o
>   CXX    f-typeprint.o
>   CXX    f-valprint.o
>   CXX    filename-seen-cache.o
>   CXX    filesystem.o
>   CXX    findcmd.o
>   CXX    findvar.o
>   CXX    fork-child.o
>   CXX    frame-base.o
>   CXX    frame-unwind.o
>   CXX    frame.o
>   CXX    gcore.o
>   CXX    gdb-dlfcn.o
>   CXX    gdb_bfd.o
>   CXX    gdb_obstack.o
>   CXX    gdb_regex.o
> ============================
> 

I took a look at the build log[1] and I can't see any reason for the
build to have failed (no errors as far as I can see).  The log
ends with this (which isn't included above):

    command timed out: 1200 seconds without output, attempting to kill
    process killed by signal 9
    program finished with exit code -1
    elapsedTime=4860.454399

Unless I've somehow caused the compile time of a file to increase by a
lot, which I don't think I have, then I'm hoping this was a random
blip.

For now, I'm no longer investigating this issue.  If anyone can help
me understand what I broke I'm obviously happy to debug & fix.

Thanks,
Andrew

[1] https://gdb-build.sergiodj.net/builders/NetBSD-x86_64-m64/builds/6873/steps/compile%20gdb/logs/stdio