public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
* [binutils-gdb] Fix testsuite regression by: Do not skip prologue for asm (.S) files
@ 2015-07-10 13:38 sergiodj+buildbot
  2015-07-10 13:38 ` Failures on AIX-POWER7-plain, branch master sergiodj+buildbot
                   ` (11 more replies)
  0 siblings, 12 replies; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-07-10 13:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 218a5a11a07268228484af88666739852ba36552 ***

Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Branch: master
Commit: 218a5a11a07268228484af88666739852ba36552

Fix testsuite regression by: Do not skip prologue for asm (.S) files
I have somehow missed gdb.asm/asm-source.exp PASS->FAIL even on x86_64.

It has no longer valid assumption that "break" breaks after the prologue even
in assembler.  So I have changed this assumption of the testfile.

gdb/testsuite/ChangeLog
2015-07-10  Jan Kratochvil  <jan.kratochvil@redhat.com>

	* gdb.asm/asm-source.exp (f at main): Stop at gdbasm_enter.
	(n at main): New.
	* gdb.asm/asmsrc1.s: Add comment "mark: main enter".


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] PRU Opcode Port
@ 2016-12-31  4:19 sergiodj+buildbot
  2017-01-14  1:03 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-12-31  4:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 111468496477e97c9414d2d54f97bfdaa380f794 ***

Author: Dimitar Dimitrov <dimitar@dinux.eu>
Branch: master
Commit: 111468496477e97c9414d2d54f97bfdaa380f794

PRU Opcode Port

opcodes/
	* Makefile.am: Add PRU source files.
	* configure.ac: Add PRU target.
	* disassemble.c (disassembler): Register PRU arch.
	* pru-dis.c: New file.
	* pru-opc.c: New file.
	* Makefile.in: Regenerate.
	* configure: Regenerate.

Signed-off-by: Dimitar Dimitrov <dimitar@dinux.eu>


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] PRU BFD support
@ 2016-12-31  3:06 sergiodj+buildbot
  2017-01-13 23:34 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-12-31  3:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 889294f6ffb380eb37b1f1f3bd22807fa9204c14 ***

Author: Dimitar Dimitrov <dimitar@dinux.eu>
Branch: master
Commit: 889294f6ffb380eb37b1f1f3bd22807fa9204c14

PRU BFD support

include/
	* elf/common.h: Add PRU ELF.
	* elf/pru.h: New file.
	* opcode/pru.h: New file.
	* dis-asm.h (print_insn_pru): Declare.
bfd/
	* archures.c: Add bfd_arch_pru.
	* Makefile.am: Add PRU target.
	* config.bfd: Ditto.
	* configure.ac: Ditto.
	* elf-bfd.h (enum elf_target_id): Add PRU_ELF_DATA.
	* targets.c: Add pru_elf32_vec.
	* reloc.c: Add PRU relocations.
	* cpu-pru.c: New file.
	* elf32-pru.c: New file.
	* Makefile.in: Regenerate.
	* configure: Regenerate.
	* po/SRC-POTFILES.in: Regenerate.
	* bfd-in2.h: Regenerate
	* libbfd.h: Regenerate.

Signed-off-by: Dimitar Dimitrov <dimitar@dinux.eu>


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Check bfd support for bfd_mips_elf_get_abiflags in mips make rule
@ 2016-12-28 13:44 sergiodj+buildbot
  2017-01-13 17:52 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-12-28 13:44 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0fa6f7cee7dedb600799234b1e2d52c5b0da8f96 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 0fa6f7cee7dedb600799234b1e2d52c5b0da8f96

Check bfd support for bfd_mips_elf_get_abiflags in mips make rule

The previous scheme with a dependency in opcodes on libbfd.la
broke "make distclean".

	* configure.ac: Revert 2016-12-23.
	* Makefile.am: Likewise.
	(MIPS_DEFS): Define.
	(mips-dis.lo): Add rule.
	* Makefile.in: Regenerate.
	* aclocal.m4: Regenerate.
	* config.in: Regenerate.
	* configure: Regenerate.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] MIPS16/GAS: Disallow EXTEND delay-slot scheduling
@ 2016-12-23 21:34 sergiodj+buildbot
  2017-01-05  0:33 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-12-23 21:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 645c455650ed35460afdacb078c7c58308607fbe ***

Author: Maciej W. Rozycki <macro@imgtec.com>
Branch: master
Commit: 645c455650ed35460afdacb078c7c58308607fbe

MIPS16/GAS: Disallow EXTEND delay-slot scheduling

Do not allow any explicitly coded EXTEND instruction to be automatically
scheduled into a jump delay slot, as an EXTEND prefix is coupled with
the next regular MIPS16 instruction and therefore swapping it with a
jump would change program's semantics; EXTEND is not architecturally
allowed to be present in a jump delay slot anyway.

	opcodes/
	* mips16-opc.c (mips16_opcodes): Set NODS in `pinfo' for
	"extend".

	gas/
	* testsuite/gas/mips/mips16-extend-swap.d: New test.
	* testsuite/gas/mips/mips16-extend-swap.s: New test source.
	* testsuite/gas/mips/mips.exp: Run the new test.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] opcodes: Use autoconf to check for `bfd_mips_elf_get_abiflags' in BFD
@ 2016-12-23 21:30 sergiodj+buildbot
  2017-01-04 23:11 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-12-23 21:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9e76c212e6311abaee4d02473473f7d6dcad972f ***

Author: Maciej W. Rozycki <macro@imgtec.com>
Branch: master
Commit: 9e76c212e6311abaee4d02473473f7d6dcad972f

opcodes: Use autoconf to check for `bfd_mips_elf_get_abiflags' in BFD

Fix a regression introduced with commit 5e7fc731f80e ("MIPS/opcodes:
Also set disassembler's ASE flags from ELF structures"), further updated
with commit 4df995c77118 ("MIPS/opcodes: Also set disassembler's ASE
flags from ELF structures"), and use autoconf to check for the presence
of `bfd_mips_elf_get_abiflags' in BFD.

	opcodes/
	* mips-dis.c (set_default_mips_dis_options): Use
	HAVE_BFD_MIPS_ELF_GET_ABIFLAGS rather than BFD64 to guard the
	call to `bfd_mips_elf_get_abiflags'.
	* configure.ac: Check for `bfd_mips_elf_get_abiflags' in BFD.
	* Makefile.am (CONFIG_STATUS_DEPENDENCIES): Add `libbfd.la'.
	* aclocal.m4: Regenerate.
	* configure: Regenerate.
	* config.in: Regenerate.
	* Makefile.in: Regenerate.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Updated email address.
@ 2016-12-23 12:50 sergiodj+buildbot
  2017-01-04 14:39 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-12-23 12:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6096dda15babc5307b1a0e9624d4e0028fd429e1 ***

Author: Bernhard Heckel <bernhard.heckel@intel.com>
Branch: master
Commit: 6096dda15babc5307b1a0e9624d4e0028fd429e1

Updated email address.

2016-12-23  Bernhard Heckel  <bernhard.heckel@intel.com>

gdb/Changelog:
	* MAINTAINERS (Write After Approval): Updated email address.

Change-Id: I46b81392c2bd4b04e8e2aea2bb4bef2d0b509d24


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Remove high bit set characters
@ 2016-12-21 11:51 sergiodj+buildbot
  2016-12-23 17:56 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-12-21 11:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4e25adb3956f880efc28bfebabe79be7338b413f ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 4e25adb3956f880efc28bfebabe79be7338b413f

Remove high bit set characters

gas/
	* doc/c-lm32.texi: Fix chars with high bit set.
	* testsuite/gas/bfin/vector2.s: Likewise.
gold/
	* arm.cc: Fix comment chars with high bit set.
include/
	* coff/pe.h: Fix comment chars with high bit set.
	* opcode/xgate.h: Likewise.
ld/
	* testsuite/ld-scripts/sysroot-prefix.exp: Fix chars with high bit set.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] MIPS16/opcodes: Correct 64-bit macros' ISA membership
@ 2016-12-20 14:09 sergiodj+buildbot
  2016-12-23 14:23 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-12-20 14:09 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4ebce1a0a5911e71aa2d00932ffb2126ff1f3633 ***

Author: Maciej W. Rozycki <macro@imgtec.com>
Branch: master
Commit: 4ebce1a0a5911e71aa2d00932ffb2126ff1f3633

MIPS16/opcodes: Correct 64-bit macros' ISA membership

Limit the DDIV, DDIVU, DREM, DREMU and DSUBU macros to the MIPS III
rather than MIPS I ISA.  These macros expand to machine code sequences
including 64-bit instructions which require a 64-bit ISA.  Entries for
those instructions are already correctly marked, however the marking is
ignored if entries are used in the process of macro expansion rather
than directly, making it possible to indirectly produce 64-bit machine
code even when output requested has been limited to a 32-bit ISA.

	opcodes/
	* mips16-opc.c (mips16_opcodes): Set membership to I3 rather
	than I1 for the "ddiv", "ddivu", "drem", "dremu" and "dsubu"
	INSN_MACRO entries.

	gas/
	* testsuite/gas/mips/mips16-macro.l: New list test.
	* testsuite/gas/mips/mips.exp: Run the new test.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] MAINTAINERS: Add myself as a MIPS maintainer
@ 2016-12-15  1:26 sergiodj+buildbot
  2016-12-15  3:54 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-12-15  1:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cadf97cf20cf76af35e41075dff81197fbec0e51 ***

Author: Maciej W. Rozycki <macro@imgtec.com>
Branch: master
Commit: cadf97cf20cf76af35e41075dff81197fbec0e51

MAINTAINERS: Add myself as a MIPS maintainer

	* MAINTAINERS (Maintainers for particular sims): Add myself as
	a MIPS maintainer.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] MIPS16/opcodes: Fix and clarify MIPS16e commentary
@ 2016-12-14 22:56 sergiodj+buildbot
  2016-12-14 23:16 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-12-14 22:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 63e014fccdd91a89873554f6b33d7128d7112813 ***

Author: Maciej W. Rozycki <macro@imgtec.com>
Branch: master
Commit: 63e014fccdd91a89873554f6b33d7128d7112813

MIPS16/opcodes: Fix and clarify MIPS16e commentary

Correct the note about JALRC/JRC being compact jumps rather than
branches, and add a reference from where the remaining MIPS16e additions
live and the jumps used to be too, complementing commit ceb94aa50d68
("Update insn_mo when converting to a MIPS16e compact jump"),
<https://sourceware.org/ml/binutils/2011-06/msg00369.html>.

	opcodes/
	* mips16-opc.c (mips16_opcodes): Update comments on MIPS16e
	compact jumps.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [Binutils][AARCH64]Remove Cn register for coprocessor CRn, CRm field
@ 2016-12-13 17:55 sergiodj+buildbot
  2016-12-13 18:59 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-12-13 17:55 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a6a51754740513db76fdee3aa153cdd51e87a24a ***

Author: Renlin Li <renlin.li@arm.com>
Branch: master
Commit: a6a51754740513db76fdee3aa153cdd51e87a24a

[Binutils][AARCH64]Remove Cn register for coprocessor CRn, CRm field

The internal CN register representation for coprocessor fields used in aarch64
sys, sysl instructions are removed in this patch.

After the change, those fields are represented as immediate. Related checks are
added as well.

opcodes/

	* aarch64-opc.c (aarch64_opnd_qualifiers): New CR value range
	qualifier.
	(operand_general_constraint_met_p): Remove case for CP_REG.
	(aarch64_print_operand): Print CRn, CRm operand using imm field.
	* aarch64-tbl.h (QL_SYS): Use CR qualifier.
	(QL_SYSL): Likewise.
	(aarch64_opcode_table): Change CRn, CRm operand class and type.
	* aarch64-opc-2.c : Regenerate.
	* aarch64-asm-2.c : Likewise.
	* aarch64-dis-2.c : Likewise.

include/

	* opcode/aarch64.h (aarch64_operand_class): Remove
	AARCH64_OPND_CLASS_CP_REG.
	(enum aarch64_opnd): Change AARCH64_OPND_Cn to AARCH64_OPND_CRn,
	AARCH64_OPND_Cm to AARCH64_OPND_CRm.
	(aarch64_opnd_qualifier): Define AARCH64_OPND_QLF_CR qualifier.

gas/

	* config/tc-aarch64.c (AARCH64_REG_TYPES): Remove CN register.
	(get_reg_expected_msg): Remove CN register case.
	(parse_operands): rewrite parser for CRn, CRm operand.
	(reg_names): Remove CN register.
	* testsuite/gas/aarch64/diagnostic.s: Add a new test case.
	* testsuite/gas/aarch64/diagnostic.l: Adjust error message.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Don't add PHDR for objcopy/strip or ld script specifying PHDRS
@ 2016-12-13  0:21 sergiodj+buildbot
  2016-12-13  3:22 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-12-13  0:21 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 22b05d33b4c870d65972ff8aefdd297ddc66d139 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 22b05d33b4c870d65972ff8aefdd297ddc66d139

Don't add PHDR for objcopy/strip or ld script specifying PHDRS

HPPA64 needs to add a DT_PHDR header for shared libs.  That's fine
when linking but shouldn't happen for strip/objcopy.  Also PHDR must
come first so there's no need to look at all program headers.

bfd/
	* elf64-hppa.c (elf64_hppa_modify_segment_map): Don't add PHDR
	for objcopy/strip or when a ld script specifies PHDRS.
ld/
	* testsuite/ld-elf/nobits-1.d: Remove xfail for hppa64.
	* testsuite/ld-elf/note-1.d: Likewise.
	* testsuite/ld-elf/note-2.d: Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] MIPS16/opcodes: Fix PC-relative operation delay-slot adjustment
@ 2016-12-09  0:50 sergiodj+buildbot
  2016-12-09  6:38 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-12-09  0:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 860b03a8f357d1565bd9d79ae25121059b2d28ae ***

Author: Maciej W. Rozycki <macro@imgtec.com>
Branch: master
Commit: 860b03a8f357d1565bd9d79ae25121059b2d28ae

MIPS16/opcodes: Fix PC-relative operation delay-slot adjustment

Complement commit dd8b7c222e0e ("MIPS: mips16e jalrc/jrc opcodes"),
<https://sourceware.org/ml/binutils/2005-07/msg00349.html>, and stop the
disassembler making a delay-slot adjustment for PC-relative operations
following either MIPS16e compact jumps, or undefined RR/J(AL)R(C)
encodings that have the `l' (link) and `ra' (source register is `ra')
bits set both at a time.  Adjust code description for accuracy.  Add a
suitable test case.

	opcodes/
	* mips-dis.c (print_mips16_insn_arg): Avoid delay-slot
	adjustment for PC-relative operations following MIPS16e compact
	jumps or undefined RR/J(AL)R(C) encodings.

	binutils/
	* testsuite/binutils-all/mips/mips16-pcrel.d: New test.
	* testsuite/binutils-all/mips/mips16-pcrel.s: New test source.
	* testsuite/binutils-all/mips/mips.exp: Run the new test.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix crash when disassembling invalid range on powerpc vle
@ 2016-12-08 13:58 sergiodj+buildbot
  2016-12-08 18:28 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-12-08 13:58 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3a2488dd21a895df3ffb49048f5de1a83ce2ddd4 ***

Author: Luis Machado <lgustavo@codesourcery.com>
Branch: master
Commit: 3a2488dd21a895df3ffb49048f5de1a83ce2ddd4

Fix crash when disassembling invalid range on powerpc vle

I got a report of a gdb crash for vle and further investigation showed an
attempt to disassemble an invalid memory range.  I tracked the crash down
to the code in get_powerpc_dialect, where we fail to make sure we have a
valid section pointer before dereferencing it.

There is no such problem for rs6000-based disassembling.

opcodes/ChangeLog:

2016-12-08  Luis Machado  <lgustavo@codesourcery.com>

	* ppc-dis.c (get_powerpc_dialect): Check NULL info->section.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] sync binutils config/ with gcc
@ 2016-12-08 13:02 sergiodj+buildbot
  2016-12-08 17:22 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-12-08 13:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT da17fe9de923fcee29e6f809693eb7e590966575 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: da17fe9de923fcee29e6f809693eb7e590966575

sync binutils config/ with gcc

config/
	* acx.m4: Import from gcc.
	* bootstrap-asan.mk: Likewise.
	* multi.m4: Likewise.
/
	* configure: Regnerate.
gas/
	* configure: Regnerate.
ld/
	* configure: Regnerate.
libiberty/
	* configure: Regnerate.
zlib/
	* configure: Regnerate.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] MIPS/opcodes: Correct an `interaction' comment typo
@ 2016-12-07 14:36 sergiodj+buildbot
  2016-12-07 17:10 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-12-07 14:36 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5f5c6e032e8d5303e9903c0538f84f76bb4d8733 ***

Author: Maciej W. Rozycki <macro@imgtec.com>
Branch: master
Commit: 5f5c6e032e8d5303e9903c0538f84f76bb4d8733

MIPS/opcodes: Correct an `interaction' comment typo

	opcodes/
	* mips-dis.c (print_mips16_insn_arg): Fix comment typo.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Add unit test to aarch64 prologue analyzer
@ 2016-12-02 10:11 sergiodj+buildbot
  2016-12-02 18:00 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-12-02 10:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4d9a9006139d1ceea787cdda871dff8943e493f0 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 4d9a9006139d1ceea787cdda871dff8943e493f0

Add unit test to aarch64 prologue analyzer

We don't have an effective way to test prologue analyzer which is
highly dependent on instruction patterns in prologue generated by
compiler.  GDB prologue analyzer may not handle the new sequences
generated by new compiler, or may still handle some sequences that
generated by very old compilers which are no longer used.  The
former is a functionality issue, while the latter is a maintenance
issue.

The input and output of prologue analyzer is quite clear, so it
fits for unit test.  The input is series of instructions, and the
output are 1) where prologue end, 2) where registers are saved.
In aarch64, they are represented in 'struct aarch64_prologue_cache'.

This patch refactors aarch64_analyze_prologue so it can read
instructions from either real target or test harness.  In unit
test aarch64_analyze_prologue_test, aarch64_analyze_prologue gets
instructions we prepared in the test, as the input of prologue
analyzer.  Then, we checked various fields in
'struct aarch64_prologue_cache'.

gdb:

2016-12-02  Yao Qi  <yao.qi@linaro.org>
	    Pedro Alves  <palves@redhat.com>

	* aarch64-tdep.c: Include "selftest.h".
	(abstract_instruction_reader): New class.
	(instruction_reader): New class.
	(aarch64_analyze_prologue): Add new parameter reader.  Call
	reader.read instead of read_memory_unsigned_integer.
	[GDB_SELF_TEST] (instruction_reader_test): New class.
	(aarch64_analyze_prologue_test): New function.
	(_initialize_aarch64_tdep) [GDB_SELF_TEST]: Register
	selftests::aarch64_analyze_prologue_test.
	* trad-frame.c (trad_frame_cache_zalloc):
	(trad_frame_alloc_saved_regs): Add a new function.
	* trad-frame.h (trad_frame_alloc_saved_regs): Declare.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Class-ify ui_out_hdr
@ 2016-12-02  2:49 sergiodj+buildbot
  2016-12-02 10:46 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-12-02  2:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 37e20dd6599203c4e261fc3a2e86711c90cbbed9 ***

Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: 37e20dd6599203c4e261fc3a2e86711c90cbbed9

Class-ify ui_out_hdr

This patch makes ui_out_hdr (the object that represents an ui-out table
header) a proper C++ class.  No behavior changes, it's all about
encapsulation.

gdb/ChangeLog:

	* ui-out.c (struct ui_out_hdr): Replace with ...
	(class ui_out_hdr): ... this.
	(append_header_to_list): Update.
	(get_next_header): Update.
	(ui_out_query_field): Update.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix test names starting with uppercase using gdb_test on a single line.
@ 2016-12-01 21:50 sergiodj+buildbot
  2016-12-01 22:42 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-12-01 21:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cdc7edd7b17dddd3558bd04d9b2fb5a73dc75f1c ***

Author: Luis Machado <lgustavo@codesourcery.com>
Branch: master
Commit: cdc7edd7b17dddd3558bd04d9b2fb5a73dc75f1c

Fix test names starting with uppercase using gdb_test on a single line.

Changes in v3:
  Fixed incorrect substitutions.

This fixes offender testcases that have test names starting with uppercase
when using gdb_test in a single line construct.

gdb/testsuite/ChangeLog
2016-12-01  Luis Machado  <lgustavo@codesourcery.com>

	Fix test names starting with uppercase throughout the files.

	* gdb.arch/i386-mpx-simple_segv.exp
	* gdb.arch/i386-mpx.exp
	* gdb.arch/i386-permbkpt.exp
	* gdb.arch/pa-nullify.exp
	* gdb.arch/powerpc-d128-regs.exp
	* gdb.arch/vsx-regs.exp
	* gdb.base/bfp-test.exp
	* gdb.base/break.exp
	* gdb.base/breakpoint-shadow.exp
	* gdb.base/callfuncs.exp
	* gdb.base/charset.exp
	* gdb.base/commands.exp
	* gdb.base/completion.exp
	* gdb.base/dfp-test.exp
	* gdb.base/echo.exp
	* gdb.base/ending-run.exp
	* gdb.base/eval.exp
	* gdb.base/expand-psymtabs.exp
	* gdb.base/float128.exp
	* gdb.base/floatn.exp
	* gdb.base/foll-exec-mode.exp
	* gdb.base/gdb1056.exp
	* gdb.base/gdb11531.exp
	* gdb.base/kill-after-signal.exp
	* gdb.base/multi-forks.exp
	* gdb.base/overlays.exp
	* gdb.base/pending.exp
	* gdb.base/sepdebug.exp
	* gdb.base/testenv.exp
	* gdb.base/valgrind-db-attach.exp
	* gdb.base/watch_thread_num.exp
	* gdb.base/watchpoint-cond-gone.exp
	* gdb.base/watchpoint.exp
	* gdb.base/watchpoints.exp
	* gdb.cp/arg-reference.exp
	* gdb.cp/baseenum.exp
	* gdb.cp/operator.exp
	* gdb.cp/shadow.exp
	* gdb.dwarf2/dw2-op-out-param.exp
	* gdb.dwarf2/dw2-reg-undefined.exp
	* gdb.go/chan.exp
	* gdb.go/hello.exp
	* gdb.go/integers.exp
	* gdb.go/methods.exp
	* gdb.go/package.exp
	* gdb.guile/scm-parameter.exp
	* gdb.guile/scm-progspace.exp
	* gdb.guile/scm-value.exp
	* gdb.mi/mi-pending.exp
	* gdb.mi/user-selected-context-sync.exp
	* gdb.multi/multi-attach.exp
	* gdb.multi/tids.exp
	* gdb.opt/clobbered-registers-O2.exp
	* gdb.pascal/floats.exp
	* gdb.pascal/integers.exp
	* gdb.python/py-block.exp
	* gdb.python/py-events.exp
	* gdb.python/py-parameter.exp
	* gdb.python/py-symbol.exp
	* gdb.python/py-symtab.exp
	* gdb.python/py-type.exp
	* gdb.python/py-value.exp
	* gdb.python/py-xmethods.exp
	* gdb.python/python.exp
	* gdb.reverse/break-precsave.exp
	* gdb.reverse/consecutive-precsave.exp
	* gdb.reverse/finish-precsave.exp
	* gdb.reverse/i386-precsave.exp
	* gdb.reverse/machinestate-precsave.exp
	* gdb.reverse/sigall-precsave.exp
	* gdb.reverse/solib-precsave.exp
	* gdb.reverse/step-precsave.exp
	* gdb.reverse/until-precsave.exp
	* gdb.reverse/watch-precsave.exp
	* gdb.server/ext-attach.exp
	* gdb.server/ext-restart.exp
	* gdb.server/ext-run.exp
	* gdb.server/ext-wrapper.exp
	* gdb.stabs/gdb11479.exp
	* gdb.stabs/weird.exp
	* gdb.threads/attach-many-short-lived-threads.exp
	* gdb.threads/kill.exp
	* gdb.threads/watchpoint-fork.exp


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] gdbarch software_single_step frame_info to regcache: alpha
@ 2016-11-22 16:56 sergiodj+buildbot
  2016-11-22 17:43 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-11-22 16:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7ab2d0874025af6ee858b32c576f2461c0a1df3d ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 7ab2d0874025af6ee858b32c576f2461c0a1df3d

gdbarch software_single_step frame_info to regcache: alpha

gdb:

2016-11-22  Yao Qi  <yao.qi@linaro.org>

	* alpha-tdep.c (alpha_deal_with_atomic_sequence): Call
	get_regcache_arch instead of get_frame_arch.  Call
	regcache_read_pc instead of get_frame_pc.
	(alpha_next_pc): Replace parameter frame with regcache.
	Call regcache_raw_get_unsigned instead of
	get_frame_register_unsigned.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Create subobject value in pretty printer
@ 2016-11-21 14:37 sergiodj+buildbot
  2016-11-21 15:04 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-11-21 14:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3fff9862d5229def9318912c2de64a03dab74532 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 3fff9862d5229def9318912c2de64a03dab74532

Create subobject value in pretty printer

Nowadays, we create a value of subobject in pretty printer with 'address'
being used,

  value = value_from_contents_and_address (type, valaddr + embedded_offset,
					   address + embedded_offset);

  set_value_component_location (value, val);
  /* set_value_component_location resets the address, so we may
     need to set it again.  */
  if (VALUE_LVAL (value) != lval_internalvar
      && VALUE_LVAL (value) != lval_internalvar_component
      && VALUE_LVAL (value) != lval_computed)
    set_value_address (value, address + embedded_offset);

value_from_contents_and_address creates a value from memory, but the
value we are pretty-printing may not from memory at all.

Instead of using value_from_contents_and_address, we create a value
of subobject with the same location as object's but different offset.
We avoid using address in this way.  As a result, parameter 'address'
in apply_val_pretty_printer is no longer needed, we can remove it in
next step.

We've already had the location of the 'whole' value, so it is safe
to assume we can create a value of 'component' or 'suboject' value
at the same location but with different offset.

gdb:

2016-11-21  Yao Qi  <yao.qi@linaro.org>

	* guile/scm-pretty-print.c (gdbscm_apply_val_pretty_printer):
	Don't call value_from_contents_and_address and
	set_value_address.  Call value_from_component.
	* python/py-prettyprint.c (gdbpy_apply_val_pretty_printer):
	Likewise.
	* value.c (value_from_component): New function.
	* value.h (value_from_component): Likewise.
	* valarith.c (value_subscripted_rvalue): Call
	value_from_component.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] libiberty: Add Rust symbol demangling.
@ 2016-11-18 19:31 sergiodj+buildbot
  2016-11-19  4:01 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-11-18 19:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 535aade664ac4170fe82e52c9addd686156220a1 ***

Author: David Tolnay <dtolnay@gmail.com>
Branch: master
Commit: 535aade664ac4170fe82e52c9addd686156220a1

libiberty: Add Rust symbol demangling.

Adds Rust symbol demangler. Rust mangles symbols using GNU_V3 style,
adding a hash and various special character subtitutions. This adds
a new rust style to cplus_demangle and adds 3 helper functions
rust_demangle, rust_demangle_sym and rust_is_mangled.

rust-demangle.c was written by David. Mark did the code formatting to
GNU style and integration into the gcc/libiberty build system and
testsuite.

include/ChangeLog:

2016-11-03  David Tolnay <dtolnay@gmail.com>
           Mark Wielaard  <mark@klomp.org>

       * demangle.h (DMGL_RUST): New macro.
       (DMGL_STYLE_MASK): Add DMGL_RUST.
       (demangling_styles): Add dlang_rust.
       (RUST_DEMANGLING_STYLE_STRING): New macro.
       (RUST_DEMANGLING): New macro.
       (rust_demangle): New prototype.
       (rust_is_mangled): Likewise.
       (rust_demangle_sym): Likewise.

libiberty/ChangeLog:

2016-11-03  David Tolnay <dtolnay@gmail.com>
           Mark Wielaard  <mark@klomp.org>

       * Makefile.in (CFILES): Add rust-demangle.c.
       (REQUIRED_OFILES): Add rust-demangle.o.
       * cplus-dem.c (libiberty_demanglers): Add rust_demangling case.
       (cplus_demangle): Handle RUST_DEMANGLING.
       (rust_demangle): New function.
       * rust-demangle.c: New file.
       * testsuite/Makefile.in (really-check): Add check-rust-demangle.
       (check-rust-demangle): New rule.
       * testsuite/rust-demangle-expected: New file.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] libiberty: Fix some demangler crashes caused by reading past end of input.
@ 2016-11-18 18:18 sergiodj+buildbot
  2016-11-18 23:02 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-11-18 18:18 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1706852c3c6c1d39f949c933d37647d02509b9cb ***

Author: Mark Wielaard <mark@klomp.org>
Branch: master
Commit: 1706852c3c6c1d39f949c933d37647d02509b9cb

libiberty: Fix some demangler crashes caused by reading past end of input.

In various situations the cplus_demangle () function could read past the
end of input causing crashes. Add checks in various places to not advance
the demangle string location and fail early when end of string is reached.
Add various examples of input strings to the testsuite that would crash
test-demangle before the fixes.

Found by using the American Fuzzy Lop (afl) fuzzer.

libiberty/ChangeLog:

       * cplus-dem.c (demangle_signature): After 'H', template function,
       no success and don't advance position if end of string reached.
       (demangle_template): After 'z', template name, return zero on
       premature end of string.
       (gnu_special): Guard strchr against searching for zero characters.
       (do_type): If member, only advance mangled string when 'F' found.
       * testsuite/demangle-expected: Add examples of strings that could
       crash the demangler by reading past end of input.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Make gdb.PendingFrame.read_register handle "user" registers.
@ 2016-11-16 22:59 sergiodj+buildbot
  2016-11-17  6:01 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-11-16 22:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 33cc7d368f420326606695daafd6292e2779c6af ***

Author: Kevin Buettner <kevinb@redhat.com>
Branch: master
Commit: 33cc7d368f420326606695daafd6292e2779c6af

Make gdb.PendingFrame.read_register handle "user" registers.

The C function, pending_framepy_read_register(), which implements
the python interface gdb.PendingFrame.read_register does not handle
the so called "user" registers like "pc".  An assertion error is
triggered due to the user registers having numbers larger than or
equal to gdbarch_num_regs(gdbarch).

With the VALUE_FRAME_ID tweak in place, the call to
get_frame_register_value() can simply be replaced by a call to
value_of_register(), which handles both real registers as well as the
user registers.

gdb/ChangeLog:

	* python/py-unwind.c (pending_framepy_read_register): Use
	value_of_register() instead of get_frame_register_value().


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Change meaning of VALUE_FRAME_ID; rename to VALUE_NEXT_FRAME_ID
@ 2016-11-16 22:04 sergiodj+buildbot
  2016-11-17  0:10 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-11-16 22:04 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 41b56feb5063aee4fefb4a991eb796d1e8a7475e ***

Author: Kevin Buettner <kevinb@redhat.com>
Branch: master
Commit: 41b56feb5063aee4fefb4a991eb796d1e8a7475e

Change meaning of VALUE_FRAME_ID; rename to VALUE_NEXT_FRAME_ID

The VALUE_FRAME_ID macro provides access to a member in struct value
that's used to hold the frame id that's used when determining a
register's value or when assigning to a register.  The underlying
member has a long and obscure name.  I won't refer to it here, but
will simply refer to VALUE_FRAME_ID as if it's the struct value member
instead of being a convenient macro.

At the moment, without this patch in place, VALUE_FRAME_ID is set in
value_of_register_lazy() and several other locations to hold the frame
id of the frame passed to those functions.

VALUE_FRAME_ID is used in the lval_register case of
value_fetch_lazy().  To fetch the register's value, it calls
get_frame_register_value() which, in turn, calls
frame_unwind_register_value() with frame->next.

A python based unwinder may wish to determine the value of a register
or evaluate an expression containing a register.  When it does this,
value_fetch_lazy() will be called under some circumstances.  It will
attempt to determine the frame id associated with the frame passed to
it.  In so doing, it will end up back in the frame sniffer of the very
same python unwinder that's attempting to learn the value of a
register as part of the sniffing operation.  This recursion is not
desirable.

As noted above, when value_fetch_lazy() wants to fetch a register's
value, it does so (indirectly) by unwinding from frame->next.

With this in mind, a solution suggests itself:  Change VALUE_FRAME_ID
to hold the frame id associated with the next frame.  Then, when it
comes time to obtain the value associated with the register, we can
simply unwind from the frame corresponding to the frame id stored in
VALUE_FRAME_ID.  This neatly avoids the python unwinder recursion
problem by changing when the "next" operation occurs.  Instead of the
"next" operation occuring when the register value is fetched, it
occurs earlier on when assigning a frame id to VALUE_FRAME_ID.
(Thanks to Pedro for this suggestion.)

This patch implements this idea.

It builds on the patch "Distinguish sentinel frame from null frame".
Without that work in place, it's necessary to check for null_id at
several places and then obtain the sentinel frame.

It also renames most occurences of VALUE_FRAME_ID to
VALUE_NEXT_FRAME_ID to reflect the new meaning of this field.

There are several uses of VALUE_FRAME_ID which were not changed.  In
each case, the original meaning of VALUE_FRAME_ID is required to get
correct results.  In all but one of these uses, either
put_frame_register_bytes() or get_frame_register_bytes() is being
called with the frame value obtained from VALUE_FRAME_ID.  Both of
these functions perform some unwinding by performing a "->next"
operation on the frame passed to it.  If we were to use the new
VALUE_NEXT_FRAME_ID macro, this would effectively do two "->next"
operations, which is not what we want.

The VALUE_FRAME_ID macro has been redefined in terms of
VALUE_NEXT_FRAME_ID.  It simply fetches the previous frame's id,
providing this id as the value of the macro.

gdb/ChangeLog:

	* value.h (VALUE_FRAME_ID): Rename to VALUE_NEXT_FRAME_ID. Update
	comment.  Create new VALUE_FRAME_ID which is defined in terms of
	VALUE_NEXT_FRAME_ID.
	(deprecated_value_frame_id_hack): Rename to
	deprecated_value_next_frame_id_hack.
	* dwarf2loc.c, findvar.c, frame-unwind.c, sentinel-frame.c,
	valarith.c, valops.c, value.c: Adjust nearly all occurences of
	VALUE_FRAME_ID to VALUE_NEXT_FRAME_ID.	Add comments for those
	which did not change.
	* value.c (struct value): Rename frame_id field to next_frame_id.
	Update comment.
	(deprecated_value_frame_id_hack): Rename to
	deprecated_value_next_frame_id_hack.
	(value_fetch_lazy): Call frame_unwind_register_value()
	instead of get_frame_register_value().
	* frame.c (get_prev_frame_id_by_id): New function.
	* frame.h (get_prev_frame_id_by_id): Declare.
	* dwarf2loc.c (dwarf2_evaluate_loc_desc_full): Make
	VALUE_NEXT_FRAME_ID refer to the next frame.
	* findvar.c (value_of_register_lazy): Likewise.
	(default_value_from_register): Likewise.
	(value_from_register): Likewise.
	* frame_unwind.c (frame_unwind_got_optimized): Likewise.
	* sentinel-frame.c (sentinel_frame_prev_register): Likewise.
	* value.h (VALUE_FRAME_ID): Update comment describing this macro.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Extend test gdb.python/py-recurse-unwind.exp
@ 2016-11-16 20:03 sergiodj+buildbot
  2016-11-16 21:49 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-11-16 20:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1a2f3d7ff1d79b1290704e48c71e905b987393a6 ***

Author: Kevin Buettner <kevinb@redhat.com>
Branch: master
Commit: 1a2f3d7ff1d79b1290704e48c71e905b987393a6

Extend test gdb.python/py-recurse-unwind.exp

This patch modifies the unwinder (sniffer) defined in
py-recurse-unwind.py so that, depending upon the value of one of its
class variables, it will take different paths through the code,
testing different functionality.

The original test attempted to obtain the value of an undefined
symbol.

This somewhat expanded test checks to see if 'pc' can be read via
gdb.PendingFrame.read_register() and also via gdb.parse_and_eval().

gdb/testsuite/ChangeLog:

	* gdb.python/py-recurse-unwind.c (main): Add loop.
	* gdb.python/py-recurse-unwind.py (TestUnwinder): Add calls
	to read_register() and gdb.parse_and_eval().  Make each code
	call a separate case that can be individually tested.
	* gdb.python/py-recurse-unwind.exp (cont_and_backtrace): New
	proc. Call cont_and_backtrace for each of the code paths that
	we want to test in the unwinder.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix PR20789 - relaxation with negative valued diff relocs
@ 2016-11-16 20:01 sergiodj+buildbot
  2016-11-16 20:26 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-11-16 20:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4cb771f214ed6a2102e37bce255c6be5d0642f3a ***

Author: Senthil Kumar Selvaraj <senthil_kumar.selvaraj@atmel.com>
Branch: master
Commit: 4cb771f214ed6a2102e37bce255c6be5d0642f3a

Fix PR20789 - relaxation with negative valued diff relocs

Fix issues with diff relocs that have a negative value
i.e. sym2 - sym1 where sym2 is lesser than sym1.

The assembler generates a diff reloc with symbol as start of section
and addend as sym2 offset, and encodes assembly time difference at
the reloc offset.

The existing relaxation logic adjusts addends if the relaxed insn lies
between symbol and addend. That doesn't work for diff relocs where
sym2 is less than sym1 *and* the relaxed insn happens to be between
sym2 and sym1.

Fix the problems by

1. Using signed handling of the difference value (bfd_signed_vma instead
of bfd_vma, bfd_{get,set}_signed_xxx instead of bfd_{get,set}_xxx).

2. Not assuming sym2 is bigger than sym1. It instead computes the actual
addresses and sets the lower and higher addresses as start and end
addresses respectively and then sees if insn is between start and end.

3. Creating a new function elf32_avr_adjust_reloc_if_spans_insn to
centralize reloc adjustment, and ensuring diff relocs get adjusted
correctly even if their sym + addend doesn't overlap a relaxed insn.

It also removes a redundant variable did_pad. It is never set if
did_shrink is TRUE, and the code does a early return if did_shrink is
FALSE.

bfd/ChangeLog

2016-11-15  Senthil Kumar Selvaraj  <senthil_kumar.selvaraj@atmel.com>

       PR ld/20789
       * bfd/elf32-avr.c (elf32_avr_adjust_diff_reloc_value): Do signed
       manipulation of diff value, and don't assume sym2 is less than sym1.
       (elf32_avr_adjust_reloc_if_spans_insn): New function.
       (elf32_avr_relax_delete_bytes): Use elf32_avr_adjust_diff_reloc_value,
       and remove redundant did_pad.

ld/ChangeLog

2016-11-15  Senthil Kumar Selvaraj  <senthil_kumar.selvaraj@atmel.com>

       PR ld/20789
       * ld/testsuite/ld-avr/pr20789.d: New test.
       * ld/testsuite/ld-avr/pr20789.s: New test.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] gdb: update gnulib to pull in C++ namespace support fixes
@ 2016-11-16  0:24 sergiodj+buildbot
  2016-11-16  4:22 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-11-16  0:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4c62b19fd2e6b81ce7cbb7d01e84c09352ccf224 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 4c62b19fd2e6b81ce7cbb7d01e84c09352ccf224

gdb: update gnulib to pull in C++ namespace support fixes

I've been experimenting with making use of gnulib's C++ namespace support:

 https://www.gnu.org/software/gnulib/manual/html_node/A-C_002b_002b-namespace-for-gnulib.html

That stumbled on a few gnulib issues, which I've fixed upstream:

 [PATCH] Fix gnulib C++ namespace support and std::frexp
 https://lists.gnu.org/archive/html/bug-gnulib/2016-11/msg00039.html

 [PATCH] Fix real-floating argument functions in C++ mode
 https://lists.gnu.org/archive/html/bug-gnulib/2016-11/msg00049.html

 [PATCH] Avoid having GNULIB_NAMESPACE::func always inject references to rpl_func
 https://lists.gnu.org/archive/html/bug-gnulib/2016-11/msg00040.html

 [PATCH] C++: "#define timeval rpl_timeval" -> typedef in GNULIB_NAMESPACE
 https://lists.gnu.org/archive/html/bug-gnulib/2016-11/msg00058.html

This merge pulls those in.

gdb/ChangeLog:
2016-11-15  Pedro Alves  <palves@redhat.com>

	* gnulib/update-gnulib.sh (GNULIB_COMMIT_SHA1): Set to
	38237baf99386101934cd93278023aa4ae523ec0.
	* gnulib/configure, gnulib/config.in: Regenerate.
	* gnulib/import/Makefile.am: Regenerate.
	* gnulib/import/Makefile.in: Regenerate.
	* gnulib/import/canonicalize-lgpl.c: Update.
	* gnulib/import/extra/snippet/c++defs.h: Update.
	* gnulib/import/m4/stdint.m4: Update.
	* gnulib/import/m4/stdlib_h.m4: Update.
	* gnulib/import/math.in.h: Update.
	* gnulib/import/stdlib.in.h: Update.
	* gnulib/import/sys_time.in.h: Update.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] bitfield-parent-optimized-out: Fix struct definition
@ 2016-11-15 20:24 sergiodj+buildbot
  2016-11-15 22:33 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-11-15 20:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b7f38fdae7c75e1d13abd455b3931950db28d22b ***

Author: Andreas Arnez <arnez@linux.vnet.ibm.com>
Branch: master
Commit: b7f38fdae7c75e1d13abd455b3931950db28d22b

bitfield-parent-optimized-out: Fix struct definition

The "struct S" type in bitfield-parent-optimized-out.exp is declared to
have a size of 4 bytes but to hold two 4-byte members: an int-based
bitfield and a 4-byte int.  Also, both members have the same
data_member_location 2, causing them to overlap and to reach 2 bytes
beyond the structure's boundary.

This is fixed by increasing the structure size to 8 and setting the
first and second member's data_member_location to 0 and 4, respectively.

gdb/testsuite/ChangeLog:

	* gdb.dwarf2/bitfield-parent-optimized-out.exp: Fix DWARF code for
	the definition of struct S.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Accept hidden COFF symbols, but treat them as if they were debugging symbols.
@ 2016-11-11 12:40 sergiodj+buildbot
  2016-11-11 14:40 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-11-11 12:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7103ad7639b7ed80bec170404185a8e39079446b ***

Author: Luke Allardyce <lukeallardyce@gmail.com>
Branch: master
Commit: 7103ad7639b7ed80bec170404185a8e39079446b

Accept hidden COFF symbols, but treat them as if they were debugging symbols.

	PR ld/20722
	* coffcode.h (coff_slurp_symbol_table): Accept C_HIDDEN symbols,
	but treat them as debugging symbols.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Remove apply_val_pretty_printer parameter valaddr
@ 2016-11-11 12:02 sergiodj+buildbot
  2016-11-11 13:40 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-11-11 12:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 668e167446b2777869f413841ec05aed59473d9f ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 668e167446b2777869f413841ec05aed59473d9f

Remove apply_val_pretty_printer parameter valaddr

This patch removes the parameter valaddr of
extension_language_ops::apply_val_pretty_printer and remove const from
"struct value *val".  valaddr can be got in each extension language's
implementation of apply_val_pretty_printer.

gdb:

2016-11-11  Yao Qi  <yao.qi@linaro.org>

	* cp-valprint.c (cp_print_value): Remove local base_valaddr.
	* extension-priv.h (struct extension_language_ops)
	<apply_val_pretty_printer>: Remove the second parameter.
	Remove const from "struct value *".  Callers updated.
	* extension.c (apply_ext_lang_val_pretty_printer): Update
	comments.  Remove parameter valaddr.  Remove const from
	"struct value *".
	* extension.h (apply_ext_lang_val_pretty_printer): Update
	declaration.
	* guile/guile-internal.h (gdbscm_apply_val_pretty_printer):
	Update declaration.
	* guile/scm-pretty-print.c (gdbscm_apply_val_pretty_printer):
	Remove parameter valaddr.  Remove const from "struct value *".
	* python/py-prettyprint.c (gdbpy_apply_val_pretty_printer):
	Likewise.
	* python/python-internal.h (gdbpy_apply_val_pretty_printer):
	Update declaration.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] sim: mips: fix dv-tx3904cpu build error
@ 2016-11-11 10:09 sergiodj+buildbot
  2016-11-11 11:47 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-11-11 10:09 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 91588b3af8e026ba11c7368476cc1f3fa8c2e2b1 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 91588b3af8e026ba11c7368476cc1f3fa8c2e2b1

sim: mips: fix dv-tx3904cpu build error

When building for mipstx39-rtems4.12 targets, some funcs use SD and CPU
implicitly.  Restore the defines for these to the local sd and cpu vars.

This was broken by the clean up in commit d47f5b30d8481272e9480118bdcb.

Reported-by: Joel Sherrill <joel.sherrill@oarcorp.com>


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Provide a more helpful error message when the BFD library is unable to load an extremely large section.
@ 2016-11-10 12:31 sergiodj+buildbot
  2016-11-10 12:31 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-11-10 12:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a18590c38657a982f8d544f2f54f39ba9abe9fca ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: a18590c38657a982f8d544f2f54f39ba9abe9fca

Provide a more helpful error message when the BFD library is unable to load an extremely large section.

	PR target/20737
	* elfnn-aarch64.c (elfNN_aarch64_final_link_relocate): Bind defined
	symbol locally in PIE.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [AArch64] Bind defined symbol locally in PIE
@ 2016-11-10  9:30 sergiodj+buildbot
  2016-11-10 11:51 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-11-10  9:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ac33b731d214d79738ca04d27f7464d4482f6a01 ***

Author: Jiong Wang <jiong.wang@arm.com>
Branch: master
Commit: ac33b731d214d79738ca04d27f7464d4482f6a01

[AArch64] Bind defined symbol locally in PIE

bfd/
	PR target/20737
	* elfnn-aarch64.c (elfNN_aarch64_final_link_relocate): Bind defined
	symbol locally in PIE.

ld/
	* testsuite/ld-aarch64/pie-bind-locally-a.s: New test source.
	* testsuite/ld-aarch64/pie-bind-locally-b.s: Likewise.
	* testsuite/ld-aarch64/pie-bind-locally.d: New testcase.
	* testsuite/ld-aarch64/aarch64-elf.exp: Run new testcase.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] tui-disasm: Fix window content buffer overrun
@ 2016-11-10  8:07 sergiodj+buildbot
  2016-11-10 11:51 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-11-10  8:07 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0bb65f1e7c9eed7338ef2e4a2f5b42d010409c39 ***

Author: Andreas Arnez <arnez@linux.vnet.ibm.com>
Branch: master
Commit: 0bb65f1e7c9eed7338ef2e4a2f5b42d010409c39

tui-disasm: Fix window content buffer overrun

A user reported a GDB crash with TUI when trying to debug a function
with a long demangled C++ method name.  It turned out that the logic for
displaying the TUI disassembly window has a bug that can cause a buffer
overrun, possibly overwriting GDB-internal data structures.  In
particular, the logic performs an unguarded strcpy.

Another (harmless) bug in tui_alloc_source_buffer causes the buffer to
be two lines longer than needed.  This may have made the crash appear
less frequently.

gdb/ChangeLog:

	* tui/tui-disasm.c (tui_set_disassem_content): Fix line buffer
	overrun due to unchecked strcpy.

gdb/testsuite/ChangeLog:

	* gdb.base/tui-layout.c: New file.
	* gdb.base/tui-layout.exp: Use tui-layout.c, to ensure that the
	disassembly window contains very long lines.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Use unique_xmalloc_ptr in Python code
@ 2016-11-10  7:49 sergiodj+buildbot
  2016-11-10 11:51 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-11-10  7:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9b9720149dfee4a9a961c29d0382fc5bdf9c975b ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 9b9720149dfee4a9a961c29d0382fc5bdf9c975b

Use unique_xmalloc_ptr in Python code

This changes some utility functions in the Python code to return
unique_xmalloc_ptr, and then fixes up the callers.

I chose unique_xmalloc_ptr rather than std::string because at a few
call points the xmalloc'd string is released and ownership transferred
elsewhere.

This patch found a few existing memory leaks.  For example,
py-unwind.c called gdbpy_obj_to_string but never freed the result.

Built and regression tested on the buildbot.

2016-11-09  Tom Tromey  <tom@tromey.com>

	* varobj.h (varobj_get_display_hint): Change return type.
	* varobj.c (varobj_get_display_hint): Return unique_xmalloc_ptr.
	(varobj_value_get_print_value): Update.
	* python/python.c (gdbpy_before_prompt_hook, gdbpy_print_stack)
	(gdbpy_apply_type_printers): Update.
	* python/python-internal.h (unicode_to_target_string)
	(python_string_to_target_string, python_string_to_host_string)
	(gdbpy_obj_to_string, gdbpy_exception_to_string)
	(gdbpy_get_display_hint): Change return types.
	* python/py-varobj.c (py_varobj_iter_next): Update.
	* python/py-value.c (valpy_getitem, convert_value_from_python):
	Update.
	* python/py-utils.c (unicode_to_encoded_string)
	(unicode_to_target_string, python_string_to_target_string)
	(python_string_to_host_string, gdbpy_obj_to_string)
	(gdbpy_exception_to_string): Return unique_xmalloc_ptr.
	* python/py-unwind.c (pyuw_parse_register_id): Update.
	* python/py-type.c (typy_getitem): Update.
	* python/py-prettyprint.c (gdbpy_get_display_hint)
	(print_stack_unless_memory_error, print_children)
	(gdbpy_apply_val_pretty_printer): Update.
	* python/py-param.c (set_parameter_value): Update.
	(get_doc_string, call_doc_function): Return unique_xmalloc_ptr.
	(get_set_value, get_show_value, compute_enum_values, parmpy_init):
	Update.
	* python/py-infthread.c (thpy_set_name): Update.
	* python/py-function.c (fnpy_call, fnpy_init): Update.
	* python/py-framefilter.c (extract_sym): Change "name" to
	unique_xmalloc_ptr.
	(enumerate_args, enumerate_locals): Update.
	(py_print_frame): Use unique_xmalloc_ptr.
	* python/py-frame.c (frapy_read_var): Update.  Remove cleanup.
	* python/py-cmd.c (cmdpy_function, cmdpy_completer, cmdpy_init):
	Update.
	* python/py-breakpoint.c (bppy_set_condition): Use
	unique_xmalloc_ptr.
	(bppy_init): Likewise.  Remove cleanup.
	(local_setattro): Update.
	* mi/mi-cmd-var.c (print_varobj, mi_cmd_var_list_children)
	(varobj_update_one): Update.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Further cleanup/modernization of gdb.base/commands.exp
@ 2016-11-10  7:48 sergiodj+buildbot
  2016-11-10 11:50 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-11-10  7:48 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fad0c9fb7dd362bdb5a3e4f89fb7f6e6789f5beb ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: fad0c9fb7dd362bdb5a3e4f89fb7f6e6789f5beb

Further cleanup/modernization of gdb.base/commands.exp

 - Use multi_line for matching multi-line GDB output.

 - Add a multi_line_input variant of multi_line to build GDB input and
   use it throughout.

   (The two changes above make the tests much more readable, IMO.)

 - Add a new valnum_re global to get rid of the multiple "\\\$\[0-9\]*".

 - Remove gdb_stop_suppressing_tests uses.

 - tighten a few regexps.

 - Replace send_gdb/gdb_expect with gdb_test_multiple and simplify,
   making pass/fail messages the same.

gdb/ChangeLog:
2016-11-09  Pedro Alves  <palves@redhat.com>

	* gdb.base/commands.exp (runto_or_return): New procedure.
	(gdbvar_simple_if_test, gdbvar_simple_while_test)
	(gdbvar_complex_if_while_test, progvar_simple_if_test)
	(progvar_simple_while_test, progvar_complex_if_while_test)
	(if_while_breakpoint_command_test)
	(infrun_breakpoint_command_test, breakpoint_command_test)
	(user_defined_command_test, watchpoint_command_test)
	(test_command_prompt_position, redefine_hook_test)
	(stray_arg0_test, error_clears_commands_left, redefine_hook_test)
	(redefine_backtrace_test): Use runto_or_return, $valnum_re,
	multi_line_input and multi_line.  Remove gdb_expect and
	gdb_stop_suppressing_tests uses.
	* lib/gdb.exp (valnum_re): New global.
	* lib/gdb.exp (valnum_re): New global.
	(multi_line_input): New procedure.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] X86: Remove the .s suffix from EVEX vpextrw
@ 2016-11-10  7:47 sergiodj+buildbot
  2016-11-10 11:51 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-11-10  7:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 60227d64dd9228be1a07fc7122894fc2875b1a70 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 60227d64dd9228be1a07fc7122894fc2875b1a70

X86: Remove the .s suffix from EVEX vpextrw

The .s suffix indicates that the instruction is encoded by swapping
2 register operands.  Since vpextrw takes an XMM register and an
integer register, the .s suffix should be ignored for EVEX vpextrw.

gas/

	PR binutils/20799
	* testsuite/gas/i386/opcode.s: Add a test for EVEX vpextrw.
	* testsuite/gas/i386/opcode-intel.d: Updated.
	* testsuite/gas/i386/opcode-suffix.d: Likewise.
	* testsuite/gas/i386/opcode.d: Likewise.
	* testsuite/gas/i386/x86-64-avx512bw-opts.s: Remove vpextrw
	tests.
	* testsuite/gas/i386/x86-64-avx512bw-opts-intel.d: Updated.
	* testsuite/gas/i386/x86-64-avx512bw-opts.d: Likewise.

opcodes/

	PR binutils/20799
	* i386-dis-evex.h (evex_table): Replace EdqwS with Edqw.
	* i386-dis.c (EdqwS): Removed.
	(dqw_swap_mode): Likewise.
	(intel_operand_size): Don't check dqw_swap_mode.
	(OP_E_register): Likewise.
	(OP_E_memory): Likewise.
	(OP_G): Likewise.
	(OP_EX): Likewise.
	* i386-opc.tbl: Remove "S" from EVEX vpextrw.
	* i386-tbl.h: Regerated.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] X86: Merge AVX512F vmovq
@ 2016-11-10  7:47 sergiodj+buildbot
  2016-11-10 11:51 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-11-10  7:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7efeed176a291c15c74e80aee5d7f906e28081cf ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 7efeed176a291c15c74e80aee5d7f906e28081cf

X86: Merge AVX512F vmovq

AVX512F vmovq doesn't support masking.  We can't swap register operand
in AVX512F vmovq with Reg64 since Reg64 != RegXMM.  This patch merges
AVX512F vmovq.

	* i386-opc.tbl: Merge AVX512F vmovq.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Make gdb.mi/user-selected-context-sync.exp use proc_with_prefix
@ 2016-11-10  7:46 sergiodj+buildbot
  2016-11-10 11:50 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-11-10  7:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8354c62cd144964fce17e11ce035c0c2c0635cbf ***

Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: 8354c62cd144964fce17e11ce035c0c2c0635cbf

Make gdb.mi/user-selected-context-sync.exp use proc_with_prefix

Pedro's patch provides a cleaner way to prefix tests with the proc name,
so let's use that.

gdb/testsuite/ChangeLog:

	* gdb.mi/user-selected-context-sync.exp (with_test_prefix_procname):
	Remove.
	(test_setup): Define with proc_with_prefix.
	(test_cli_inferior): Likewise.
	(test_cli_thread): Likewise.
	(test_cli_frame): Likewise.
	(test_cli_select_frame): Likewise.
	(test_cli_up_down): Likewise.
	(test_mi_thread_select): Likewise.
	(test_mi_stack_select_frame): Likewise.
	(test_cli_in_mi_inferior): Likewise.
	(test_cli_in_mi_thread): Likewise.
	(test_cli_in_mi_frame): Likewise.
	(top level): Do not use with_test_prefix_procname.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] agent_expr_up: gdb::unique_ptr -> std::unique_ptr
@ 2016-11-10  7:45 sergiodj+buildbot
  2016-11-10 11:51 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-11-10  7:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6c73cd95f96d37dbf6092a87c8ba0f35277223a5 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 6c73cd95f96d37dbf6092a87c8ba0f35277223a5

agent_expr_up: gdb::unique_ptr -> std::unique_ptr

Now that we require C++11, use std::unique_ptr directly.  This allows
simplifying collection_list a bit by placing unique pointers in the
vector directly, making the vector own its elements.

gdb/ChangeLog:
2016-11-09  Pedro Alves  <palves@redhat.com>

	* ax-gdb.c (agent_eval_command_one): Use std::move instead of
	gdb::move.
	* ax.h (agent_expr_up): Use std::unique_ptr instead of
	gdb::unique_ptr.
	* breakpoint.c (parse_cond_to_aexpr): Use std::move instead of
	gdb::move.
	* tracepoint.c (collection_list::collect_symbol): Likewise.
	(collection_list::~collection_list): Delete.
	(encode_actions_1): Use std::move instead of gdb::move.
	(collection_list::add_aexpr): Use std::move instead of
	unique_ptr::release.
	* tracepoint.h (collection_list) <~collection_list>: Delete
	declaration.
	<m_aexprs>: Now a vector of agent_ptr_up.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] gdb/testsuite: Introduce "proc_with_prefix"
@ 2016-11-10  7:45 sergiodj+buildbot
  2016-11-10 11:50 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-11-10  7:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 64f367a201565d5c7d1e03da072db51123ac2174 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 64f367a201565d5c7d1e03da072db51123ac2174

gdb/testsuite: Introduce "proc_with_prefix"

While adding new tests to gdb.base/commands.exp, I noticed that the
file includes a bunch of individual testcases split into their own
procedures, and that none have ever been adjusted to use
with_test_prefix.  Instead, each gdb_test/gdb_test_multiple/etc
invocation takes care of including the procedure name in the test
message, in order to make sure test messages are unique.

Simon convinced me that using the procedure name as prefix is not that
bad of an idea:
  https://sourceware.org/ml/gdb-patches/2016-10/msg00020.html

This commit adds an IMO simpler alternative to
with_test_prefix_procname added by that patch -- a new
"proc_with_prefix" convenience proc that is meant to be used in place
of "proc", and then uses it in commands.exp.  Procedures defined with
this automatically run their bodies under with_test_prefix $proc_name.

Here's a sample of the resulting gdb.sum diff:

 [...]
 -PASS: gdb.base/commands.exp: break factorial #3
 -PASS: gdb.base/commands.exp: set value to 5 in test_command_prompt_position
 -PASS: gdb.base/commands.exp: if test in test_command_prompt_position
 -PASS: gdb.base/commands.exp: > OK in test_command_prompt_position
 +PASS: gdb.base/commands.exp: test_command_prompt_position: break factorial
 +PASS: gdb.base/commands.exp: test_command_prompt_position: set value to 5
 +PASS: gdb.base/commands.exp: test_command_prompt_position: if test
 +PASS: gdb.base/commands.exp: test_command_prompt_position: > OK
 [...]

gdb/testsuite/ChangeLog:
2016-11-09  Pedro Alves  <palves@redhat.com>

	* gdb.base/commands.exp (gdbvar_simple_if_test)
	(gdbvar_simple_while_test, gdbvar_complex_if_while_test)
	(progvar_simple_if_test, progvar_simple_while_test)
	(progvar_complex_if_while_test, if_while_breakpoint_command_test)
	(infrun_breakpoint_command_test, breakpoint_command_test)
	(user_defined_command_test, watchpoint_command_test)
	(test_command_prompt_position, deprecated_command_test)
	(bp_deleted_in_command, temporary_breakpoint_commands)
	(stray_arg0_test, source_file_with_indented_comment)
	(recursive_source_test, if_commands_test)
	(error_clears_commands_left, redefine_hook_test)
	(redefine_backtrace_test): Use proc_with_prefix.
	* lib/gdb.exp (proc_with_prefix): New proc.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] tui-winsource: Remove failed-allocation logic
@ 2016-11-10  6:36 sergiodj+buildbot
  2016-11-10 11:51 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-11-10  6:36 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8c84bffb45ac63b98fffc5c1a492c2eb7e4f27e2 ***

Author: Andreas Arnez <arnez@linux.vnet.ibm.com>
Branch: master
Commit: 8c84bffb45ac63b98fffc5c1a492c2eb7e4f27e2

tui-winsource: Remove failed-allocation logic

This removes dead code in tui_alloc_source_buffer for handling a NULL
return value from xmalloc.

gdb/ChangeLog:

	* tui/tui-winsource.c (tui_alloc_source_buffer): Remove
	failed-xmalloc handling.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] gdb: Use vector::emplace_back
@ 2016-11-10  5:47 sergiodj+buildbot
  2016-11-10 12:30 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-11-10  5:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7a63494a0df60cf71b9cf03c4eb8f24719d03e66 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 7a63494a0df60cf71b9cf03c4eb8f24719d03e66

gdb: Use vector::emplace_back

Now that we require C++11, we can use vector::emplace_back to
construct elements in place instead of constructing and then copying.

gdb/ChangeLog:
2016-11-09  Pedro Alves  <palves@redhat.com>

	* main.c (struct cmdarg): Add constructor.
	(captured_main_1): Use vector::emplace_back.
	* tracepoint.c (collection_list::add_memrange): Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] tui-disasm: Fix line buffer size calculation
@ 2016-11-10  4:19 sergiodj+buildbot
  2016-11-10 11:50 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-11-10  4:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f5396833d35a257902409493a63f777dcd771868 ***

Author: Andreas Arnez <arnez@linux.vnet.ibm.com>
Branch: master
Commit: f5396833d35a257902409493a63f777dcd771868

tui-disasm: Fix line buffer size calculation

The code that fills the TUI disassembly window content first calculates
the maximum full length of a displayed disassembly line.  This
calculation typically yields the wrong result.  The result is too large,
so the bug does not cause any run-time failures, but unnecessary
confusion for the reader.  This patch fixes the calculation.

gdb/ChangeLog:

	* tui/tui-disasm.c (tui_set_disassem_content): Fix calculation of
	the longest disassembly line's length.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] tui-winsource: Allocate for actual lines only
@ 2016-11-10  3:59 sergiodj+buildbot
  2016-11-10 11:50 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-11-10  3:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7bc2c8b83ea82b4315c67e7658af815aed062e73 ***

Author: Andreas Arnez <arnez@linux.vnet.ibm.com>
Branch: master
Commit: 7bc2c8b83ea82b4315c67e7658af815aed062e73

tui-winsource: Allocate for actual lines only

The logic for allocating a TUI source window's content buffer allocates
two more lines than needed, because it does not reduce the window height
by the highlight box's overhead.  However, it does reduce the line width
accordingly.  This patch makes the height and width calculation
consistent and improves the comment.

gdb/ChangeLog:

	* tui/tui-winsource.c (tui_alloc_source_buffer): Subtract
	highlight box's overhead when calculating the content height.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] darwin-nat.c: handle Darwin 16 (aka Sierra).
@ 2016-11-10  1:21 sergiodj+buildbot
  2016-11-10 11:50 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-11-10  1:21 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 82b19a4d2f9c9e8d56fdffdd702f7db4af486386 ***

Author: Tristan Gingold <gingold@adacore.com>
Branch: master
Commit: 82b19a4d2f9c9e8d56fdffdd702f7db4af486386

darwin-nat.c: handle Darwin 16 (aka Sierra).

Support message from new task and dead name notification on task of an
existing process.
With Sierra, exec(2) terminate the current task and creates a new one.
'set startup-with-shell off' must still be used on Darwin 16.

2016-11-09  Tristan Gingold  <gingold@adacore.com>

	* darwin-nat.c (find_inferior_task_it): Fix indentation.
	(find_inferior_notify_it): Remove.
	(find_inferior_pid_it): New function.
	(darwin_find_inferior_by_notify): Remove.
	(darwin_find_inferior_by_pid): New function.
	(darwin_find_new_inferior): New function.
	(darwin_check_message_ndr): New function from
	darwin_decode_exception_message.
	(darwin_decode_exception_message): Call darwin_check_message_ndr.
	Handle SIGTRAP addressed to an unknown task (when a task spawned).
	(darwin_decode_notify_message): New function.
	(darwin_decode_message): Handle unknown task.
	(darwin_deallocate_threads): New function from darwin_mourn_inferior.
	(darwin_mourn_inferior): Use darwin_deallocate_threads and
	darwin_deallocate_exception_ports.
	(darwin_deallocate_exception_ports): New function from
	darwin_mourn_inferior.
	(darwin_setup_exceptions): New function from darwin_attach_pid.
	(darwin_setup_request_notification): Likewise.
	(darwin_attach_pid): Call darwin_setup_request_notification and
	darwin_setup_request_notification.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix py-value.exp failure on Python 3
@ 2016-11-09 23:50 sergiodj+buildbot
  2016-11-10 11:50 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-11-09 23:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7353f2470c2eda19c31c9fa44c315c7c69dea7c4 ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 7353f2470c2eda19c31c9fa44c315c7c69dea7c4

Fix py-value.exp failure on Python 3

I happened to notice that one test in py-value.exp did not work
properly with Python 3.  This patch fixes the problem.

2016-11-08  Tom Tromey  <tom@tromey.com>

	* gdb.python/py-value.exp (test_value_creation): Make "long" test
	depend on Python 2.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] X86: Remove the THREE_BYTE_0F7A entry
@ 2016-11-09 23:16 sergiodj+buildbot
  2016-11-10 11:50 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-11-09 23:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1f334aeb2268db153f01143e9b0ac01448ecaa56 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 1f334aeb2268db153f01143e9b0ac01448ecaa56

X86: Remove the THREE_BYTE_0F7A entry

Remove the THREE_BYTE_0F7A entry which is leftover from SSE5.

	PR binutils/20701
	* i386-dis.c (THREE_BYTE_0F7A): Removed.
	(dis386_twobyte): Don't use THREE_BYTE_0F7A.
	(three_byte_table): Remove THREE_BYTE_0F7A.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix some error-handling bugs in python frame filters
@ 2016-11-09 21:50 sergiodj+buildbot
  2016-11-10 11:51 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-11-09 21:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 30a7bb833cbd848b1814f18b91dfdafba4e86839 ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 30a7bb833cbd848b1814f18b91dfdafba4e86839

Fix some error-handling bugs in python frame filters

While writing a Python frame filter, I found a few bugs in the current
frame filter code.  In particular:

* One spot converts a Python long to a CORE_ADDR using PyLong_AsLong.
  However, this can fail on overflow.  I changed this to use
  get_addr_from_python.

* Another spot is doing the same but with PyLong_AsUnsignedLongLong; I
  changed this as well just for consistency.

* Converting line numbers can print "-1" if conversion from long
  fails.  This isn't fatal but just a bit ugly.

I've included a test case for the first issue.  The line number one
didn't seem important enough to bother with.

2016-11-08  Tom Tromey  <tom@tromey.com>

	* python/py-framefilter.c (py_print_frame): Use
	get_addr_from_python.  Check for errors when getting line number.

2016-11-08  Tom Tromey  <tom@tromey.com>

	* gdb.python/py-framefilter.py (ElidingFrameDecorator.address):
	New method.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Remove parameter valaddr from la_val_print
@ 2016-11-09 20:30 sergiodj+buildbot
  2016-11-10 11:49 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-11-09 20:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e8b24d9ff5b9419fc079f5fe975fac6f499f8bfb ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: e8b24d9ff5b9419fc079f5fe975fac6f499f8bfb

Remove parameter valaddr from la_val_print

Nowadays, we pass both val and return value of
value_contents_for_printing (val) to la_val_print.  The latter is
unnecessary.  This patch removes the second parameter of la_val_print,
and get valaddr in each language's implementation by calling
value_contents_for_printing.  Since value_contents_for_printing calls
value_fetch_lazy, I also make VAL non-const.

Note that
 - I don't clean up the valaddr usages in each language's routines,
 - I don't remove valaddr from apply_ext_lang_val_pretty_printer, and
   extension language ops apply_val_pretty_printer.

They can be done in followup patches.

gdb:

2016-11-08  Yao Qi  <yao.qi@linaro.org>

	* ada-lang.h (ada_val_print): Remove second parameter.  Remove
	const from "struct value *".
	* ada-valprint.c (print_field_values): Remove const from
	"struct value *".
	(val_print_packed_array_elements): Likewise.
	(print_variant_part): Likewise.
	(ada_val_print_string): Likewise.
	(ada_val_print_gnat_array): Likewise.
	(ada_val_print_ptr): Likewise.
	(ada_val_print_num): Likewise.
	(ada_val_print_enum): Likewise.
	(ada_val_print_flt): Likewise.
	(ada_val_print_union): Likewise.
	(ada_val_print_struct_union): Likewise.
	(ada_val_print_ref): Likewise.
	(ada_val_print_1): Remove second parameter.  Remove const from
	"struct value *".
	(ada_val_print): Likewise.
	* c-lang.h (c_val_print): Likewise.
	* c-valprint.c (c_val_print_array): Remove const from
	"struct value *".
	(c_val_print_ptr): Likewise.
	(c_val_print_struct): Likewise.
	(c_val_print_union): Likewise.
	(c_val_print_int): Likewise.
	(c_val_print_memberptr): Likewise.
	(c_val_print): Remove second parameter.  Remove const from
	"struct value *".  All callers updated.
	* cp-valprint.c (cp_print_value): Remove const from
	"struct value *".
	(cp_print_value_fields): Likewise.
	(c_val_print_value): Likewise.
	* d-lang.h (d_val_print): Remove second parameter.  Remove const
	from "struct value *".
	* d-valprint.c (dynamic_array_type): Likewise.
	(d_val_print): Likewise.
	* f-lang.h (f_val_print): Likewise.
	* f-valprint.c (f_val_print): Likewise.
	* go-lang.h (go_val_print): Likewise.
	* go-valprint.c (print_go_string): Likewise.
	(go_val_print): Likewise.
	* language.c (unk_lang_val_print): Likewise.
	* language.h (struct language_defn) <la_val_print>: Likewise.
	Update comments.
	(LA_VAL_PRINT): Remove.
	* m2-lang.h (m2_val_print): Remove const from
	"struct value *".
	* m2-valprint.c (m2_print_array_contents): Likewise.
	(m2_val_print): Likewise.
	* p-lang.h (pascal_val_print): Remove second parameter.  Remove
	const from "struct value *".
	(pascal_object_print_value_fields): Likewise.
	* p-valprint.c (pascal_val_print): Likewise.
	(pascal_object_print_value_fields): Likewise.
	(pascal_object_print_value): Likewise.
	* rust-lang.c (rust_get_disr_info): Likewise.
	(val_print_struct): Likewise.
	(rust_val_print): Likewise.
	* valprint.c (generic_val_print_array): Likewise.
	(generic_val_print_ptr): Likewise.
	(generic_val_print_memberptr): Likewise.
	(generic_val_print_ref): Likewise.
	(generic_val_print_enum): Likewise.
	(generic_val_print_flags): Likewise.
	(generic_val_print_func): Likewise.
	(generic_val_print_bool): Likewise.
	(generic_val_print_int): Likewise.
	(generic_val_print_char): Likewise.
	(generic_val_print_float): Likewise.
	(generic_val_print_decfloat): Likewise.
	(generic_val_print_complex): Likewise.
	(generic_val_print): Likewise.
	(val_print): Likewise.
	(common_val_print): Likewise.
	(val_print_type_code_flags): Likewise.
	(val_print_scalar_formatted): Likewise.
	(val_print_array_elements): Likewise.
	* valprint.h (val_print_array_elements): Update declaration.
	(val_print_scalar_formatted): Likewise.
	(generic_val_print): Likewise.
	* value.h (val_print): Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Use get_frame_register_value instead of deprecated_frame_register_read
@ 2016-11-09 19:49 sergiodj+buildbot
  2016-11-10 11:49 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-11-09 19:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cc977dc7d53ef4546592a4f02a2e06a621beae6f ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: cc977dc7d53ef4546592a4f02a2e06a621beae6f

Use get_frame_register_value instead of deprecated_frame_register_read

This patch calls get_frame_register_value instead of
deprecated_frame_register_read, so that we can pass
value_contents_for_printing to val_print.  Both
get_frame_register_value and deprecated_frame_register_read call
frame_unwind_register_value indirectly, so no functionality is changed
by this patch.

gdb:

2016-11-08  Yao Qi  <yao.qi@linaro.org>

	* mt-tdep.c (mt_registers_info): Call
	get_frame_register_value instead of
	deprecated_frame_register_read.
	* sh64-tdep.c (sh64_do_register): Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Eliminate agent_expr_p; VEC -> std::vector in struct bp_target_info
@ 2016-11-09 18:42 sergiodj+buildbot
  2016-11-10 11:49 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-11-09 18:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3cde5c42d1c1ddcf8bbde5c47233c644370c959c ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 3cde5c42d1c1ddcf8bbde5c47233c644370c959c

Eliminate agent_expr_p; VEC -> std::vector in struct bp_target_info

After the previous patch, we end up with these two types with quite
similar, and potentially confusing names:

  typedef gdb::unique_ptr<agent_expr> agent_expr_up;

  /* Pointer to an agent_expr structure.  */
  typedef struct agent_expr *agent_expr_p;

The latter is only necessary to put agent_expr pointers in VECs.  So
just eliminate it and use std::vector instead.

gdb/ChangeLog:
2016-11-08  Pedro Alves  <palves@redhat.com>

	* ax.h (agent_expr_p): Delete.
	(DEF_VEC_P (agent_expr_p)): Delete.
	* breakpoint.c (build_target_condition_list)
	(build_target_command_list): Adjust to use of std::vector.
	(bp_location_dtor): Remove now unnecessary VEC_free calls.
	* breakpoint.h: Include <vector>.
	(struct bp_target_info) <conditions, tcommands>: Now
	std::vector's.
	* remote.c (remote_add_target_side_condition): bp_tgt->conditions
	is now a std::vector; adjust.
	(remote_add_target_side_commands, remote_insert_breakpoint):
	bp_tgt->tcommands is now a std::vector; adjust.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] 'struct agent_expr *' -> unique_ptr<agent_expr>
@ 2016-11-09 17:48 sergiodj+buildbot
  2016-11-10 11:51 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-11-09 17:48 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 833177a4a5c1a2a6cabe70bfe35ecf241b68d169 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 833177a4a5c1a2a6cabe70bfe35ecf241b68d169

'struct agent_expr *' -> unique_ptr<agent_expr>

This patch makes the gen_* functions return a unique_ptr instead of
raw pointer:

  typedef gdb::unique_ptr<agent_expr> agent_expr_up;

and then adjusts the codebase throughout to stop using
make_cleanup_free_agent_expr.

The cond_bytecode and cmd_bytecode fields of struct bp_location are
owning pointers, so they're changed to be unique_ptr's instead of raw
pointers.

gdb/ChangeLog:
2016-11-08  Pedro Alves  <palves@redhat.com>

	* ax-gdb.c (is_nontrivial_conversion): Use agent_expr_up.
	(gen_trace_for_var, gen_trace_for_expr, gen_eval_for_expr)
	(gen_trace_for_return_address, gen_printf): Use and return an
	agent_expr_up.  Don't use make_cleanup_free_agent_expr.
	(agent_eval_command_one, maint_agent_printf_command): Use
	agent_expr_up.  Don't use make_cleanup_free_agent_expr.
	* ax-gdb.h (gen_trace_for_expr, gen_trace_for_var)
	(gen_trace_for_return_address, gen_eval_for_expr, gen_printf): Use
	agent_expr_up.
	* ax-general.c (new_agent_expr): Rename to ...
	(agent_expr::agent_expr): ... this, and now a constructor.
	(free_agent_expr): Rename to ...
	(agent_expr::~agent_exp): ... this, and now a destructor.
	(do_free_agent_expr_cleanup, make_cleanup_free_agent_expr):
	Delete.
	* ax.h (struct agent_expr): Add ctor/dtor.
	(agent_expr_up): New typedef.
	(new_agent_expr, free_agent_expr, make_cleanup_free_agent_expr):
	Delete declarations.
	* breakpoint.c (parse_cond_to_aexpr): Use and return an
	agent_expr_up.  Don't use make_cleanup_free_agent_expr.
	(build_target_condition_list): Adjust to use agent_expr_up.
	(parse_cmd_to_aexpr): Use and return an agent_expr_up.  Don't use
	make_cleanup_free_agent_expr.
	(build_target_command_list): Adjust to use agent_expr_up.
	(force_breakpoint_reinsertion): Adjust to use agent_expr_up.
	(bp_location_dtor): Remove unnecessary free_agent_expr and xfree
	calls.
	* breakpoint.h (struct bp_target_info) <cond_bytecode,
	cmd_bytecode>: Now agent_expr_up's.
	* remote.c (remote_download_tracepoint): Adjust to use
	agent_expr_up and remove use of make_cleanup_free_agent_expr.
	* tracepoint.c (validate_actionline, collect_symbol): Adjust to
	use agent_expr_up and remove uses of make_cleanup_free_agent_expr.
	(collection_list::~collection_list): Call delete instead of
	free_agent_expr.
	(encode_actions_1): Adjust to use agent_expr_up and remove uses of
	make_cleanup_free_agent_expr.
	(add_aexpr): Change parameter type to agent_expr_up; Return a raw
	agent_expr pointer.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] i386-tdep.c (i386_gdbarch_init): Add comments.
@ 2016-11-08  0:39 sergiodj+buildbot
  2016-11-08  5:07 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-11-08  0:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ad9eb1fdda263cd91ee8fb36292fb29d546b0076 ***

Author: Doug Evans <dje@google.com>
Branch: master
Commit: ad9eb1fdda263cd91ee8fb36292fb29d546b0076

i386-tdep.c (i386_gdbarch_init): Add comments.

gdb/ChangeLog:

	* i386-tdep.c (i386_gdbarch_init): Add comments.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] arc/nps400: Validate address type operands correctly
@ 2016-11-04 23:14 sergiodj+buildbot
  2016-11-05  2:40 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-11-04 23:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b437d035ddf4e4c0c566c577ee059790ed28ad9b ***

Author: Andrew Burgess <andrew.burgess@embecosm.com>
Branch: master
Commit: b437d035ddf4e4c0c566c577ee059790ed28ad9b

arc/nps400: Validate address type operands correctly

When we match against an address type operand within an instruction it
is important that we match exactly the right address type operand early
on, during the opcode selection phase.  If we wait until the operand
insertion phase to check that we have the correct address operand, then
it is too late to select an alternative opcode.  This becomes important
only when we have multiple opcodes with the same mnemonic, and operand
lists that differ only in the type of the address operands.

This commit fixes this issue, and adds some example instructions that
require this issue to be fixed (the instructions are identical except
for the address type operand).

gas/ChangeLog:

	* config/tc-arc.c (find_opcode_match): Use insert function to
	validate matching address type operands.
	* testsuite/gas/arc/nps400-10.d: New file.
	* testsuite/gas/arc/nps400-10.s: New file.

opcodes/ChangeLog:

	* arc-opc.c (arc_flag_operands): Add F_DI14.
	(arc_flag_classes): Add C_DI14.
	* arc-nps400-tbl.h: Add new exc instructions.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] arc: Replace ARC_SHORT macro with arc_opcode_len function
@ 2016-11-03 17:51 sergiodj+buildbot
  2016-11-04 10:05 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-11-03 17:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 06fe285fd293e999481ec8f5c619658aa5e3b48b ***

Author: Graham Markall <graham.markall@embecosm.com>
Branch: master
Commit: 06fe285fd293e999481ec8f5c619658aa5e3b48b

arc: Replace ARC_SHORT macro with arc_opcode_len function

In preparation for moving to a world where arc instructions can be 2, 4,
6, or 8 bytes in length, replace the ARC_SHORT macro (which is either
true of false) with an arc_opcode_len function that returns a length in
bytes.

There should be no functional change after this commit.

gas/ChangeLog:

	* config/tc-arc.c (assemble_insn): Replace use of ARC_SHORT with
	arc_opcode_len.

include/ChangeLog:

	* opcode/arc.h (arc_opcode_len): Declare.
	(ARC_SHORT): Delete.

opcodes/ChangeLog:

	* arc-dis.c (find_format_from_table): Replace use of ARC_SHORT
	with arc_opcode_len.
	(find_format_long_instructions): Likewise.
	* arc-opc.c (arc_opcode_len): New function.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Remove gdbarch_remote_breakpoint_from_pc
@ 2016-11-03 15:50 sergiodj+buildbot
  2016-11-03 22:46 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-11-03 15:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c0f4a997c26760d2584946196ee5c411d1a632a6 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: c0f4a997c26760d2584946196ee5c411d1a632a6

Remove gdbarch_remote_breakpoint_from_pc

This patch removes gdbarch method remote_breakpoint_from_pc, as it
is no longer used.

gdb:

2016-11-03  Yao Qi  <yao.qi@linaro.org>

	* arch-utils.c (default_remote_breakpoint_from_pc): Remove.
	* arch-utils.h (default_remote_breakpoint_from_pc): Remove.
	* arm-tdep.c (arm_remote_breakpoint_from_pc): Remove.
	(arm_gdbarch_init): Don't call
	set_gdbarch_remote_breakpoint_from_pc.
	* gdbarch.sh (remote_breakpoint_from_pc): Remove.
	* gdbarch.c, gdbarch.h: Regenerate.
	* mips-tdep.c (mips_remote_breakpoint_from_pc): Remove.
	(mips_gdbarch_init): Don't call
	set_gdbarch_remote_breakpoint_from_pc.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] New gdbarch methods breakpoint_kind_from_pc and sw_breakpoint_from_kind
@ 2016-11-03 15:40 sergiodj+buildbot
  2016-11-03 21:00 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-11-03 15:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cd6c3b4ffc4ea6f56f12581419e2eed885441beb ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: cd6c3b4ffc4ea6f56f12581419e2eed885441beb

New gdbarch methods breakpoint_kind_from_pc and sw_breakpoint_from_kind

This patch adds two gdbarch methods breakpoint_kind_from_pc and
sw_breakpoint_from_kind, and uses target_info.placed_size as "kind"
of the breakpoint.  This patch updates the usages of
target_info.placed_size.

The "kind" of a breakpoint is determined by gdbarch rather than
target, so we have gdbarch method breakpoint_kind_from_pc, and we
should set target_info.placed_size out of each implementation of
target to_insert_breakpoint.  In this way, each target doesn't have
to set target_info.placed_size any more.

This patch also sets target_info.placed_address before
target_insert_breakpoint too, so that target to_insert_breakpoint
can use it, see record_full_insert_breakpoint.

Before we call target_insert_breakpoint, we set
target_info.placed_address and target_info.placed_size like this,

      CORE_ADDR addr = bl->target_info.reqstd_address;

      bl->target_info.placed_size = gdbarch_breakpoint_kind_from_pc (bl->gdbarch, &addr);
      bl->target_info.placed_address = addr;

      return target_insert_breakpoint (bl->gdbarch, &bl->target_info);

target_insert_breakpoint may fail, but it doesn't matter to the "kind"
and "placed_address" of a breakpoint.  They should be determined by
gdbarch.

gdb:

2016-11-03  Yao Qi  <yao.qi@linaro.org>

	* arch-utils.h (GDBARCH_BREAKPOINT_MANIPULATION): Define
	breakpoint_kind_from_pc and sw_breakpoint_from_kind.
	(GDBARCH_BREAKPOINT_MANIPULATION_ENDIAN): Likewise.
	(SET_GDBARCH_BREAKPOINT_MANIPULATION): Call
	set_gdbarch_breakpoint_kind_from_pc and
	set_gdbarch_sw_breakpoint_from_kind.
	* arm-tdep.c: Add comments.
	* bfin-tdep.c: Likewise.
	* breakpoint.c (breakpoint_kind): New function.
	(insert_bp_location): Set target_info.placed_size and
	target_info.placed_address.
	(bkpt_insert_location): Likewise.
	* cris-tdep.c: Add comments.
	* gdbarch.sh (breakpoint_kind_from_pc): New.
	(sw_breakpoint_from_kind): New.
	* gdbarch.c, gdbarch.h: Regenerated.
	* ia64-tdep.c (ia64_memory_insert_breakpoint): Don't set
	bp_tgt->placed_size.
	(ia64_memory_remove_breakpoint): Don't assert
	bp_tgt->placed_size.
	(ia64_breakpoint_kind_from_pc): New function.
	(ia64_gdbarch_init): Install ia64_breakpoint_kind_from_pc.
	* m32r-tdep.c (m32r_memory_insert_breakpoint): Don't set
	bp_tgt->placed_size.
	* mem-break.c (default_memory_insert_breakpoint): Don't set
	bp_tgt->placed_size.  Call gdbarch_sw_breakpoint_from_kind.
	(default_memory_remove_breakpoint): Call
	gdbarch_sw_breakpoint_from_kind.
	(memory_validate_breakpoint): Don't check bp_tgt->placed_size.
	* mips-tdep.c: Add comments.
	* mt-tdep.c: Likewise.
	* nios2-tdep.c: Likewise.
	* record-full.c (record_full_insert_breakpoint): Don't call
	gdbarch_breakpoint_from_pc.  Don't set bp_tgt->placed_address
	and bp_tgt->placed_size.
	* remote.c (remote_insert_breakpoint): Don't call
	gdbarch_remote_breakpoint_from_pc.  Use bp_tgt->placed_size.
	Don't set bp_tgt->placed_address and bp_tgt->placed_size.
	(remote_insert_hw_breakpoint): Likewise.
	* score-tdep.c: Likewise.
	* sh-tdep.c: Likewise.
	* tic6x-tdep.c: Likewise.
	* v850-tdep.c: Likewise.
	* xtensa-tdep.c: Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Add enum for mips breakpoint kinds
@ 2016-11-03 15:21 sergiodj+buildbot
  2016-11-03 18:20 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-11-03 15:21 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 44f1c4d7b0160a51ecf7fe1af42416f1d2a71356 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 44f1c4d7b0160a51ecf7fe1af42416f1d2a71356

Add enum for mips breakpoint kinds

This patch adds an enum mips_breakpoint_kind to avoid using magic
numbers as much as possible.

gdb:

2016-11-03  Yao Qi  <yao.qi@linaro.org>

	* mips-tdep.c (mips_breakpoint_kind): New enum.
	(mips_breakpoint_from_pc): Use it.
	(mips_remote_breakpoint_from_pc): Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Updated Danish translation for the BFD library.
@ 2016-11-03 11:46 sergiodj+buildbot
  2016-11-03 14:54 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-11-03 11:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 225b362d1036121a611f3dd17fdb6780070ba51f ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: 225b362d1036121a611f3dd17fdb6780070ba51f

Updated Danish translation for the BFD library.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Add support for RISC-V architecture.
@ 2016-11-01 17:00 sergiodj+buildbot
  2016-11-01 23:23 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-11-01 17:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e23eba971dd409b999dd83d8df0f842680c1c642 ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: e23eba971dd409b999dd83d8df0f842680c1c642

Add support for RISC-V architecture.

bfd	* Makefile.am: Add entries for riscv32-elf and riscv64-elf.
	* config.bdf: Likewise.
	* configure.ac: Likewise.
	* Makefile.in: Regenerate.
	* configure: Regenerate.
	* archures.c: Add bfd_riscv_arch.
	* reloc.c: Add riscv relocs.
	* targets.c: Add riscv_elf32_vec and riscv_elf64_vec.
	* bfd-in2.h: Regenerate.
	* libbfd.h: Regenerate.
	* elf-bfd.h: Add RISCV_ELF_DATA to enum elf_target_id.
	* elfnn-riscv.c: New file.
	* elfxx-riscv.c: New file.
	* elfxx-riscv.h: New file.

binutils* readelf.c (guess_is_rela): Add EM_RISCV.
	(get_machine_name): Likewise.
	(dump_relocations): Add support for riscv relocations.
	(get_machine_flags): Add support for riscv flags.
	(is_32bit_abs_reloc): Add R_RISCV_32.
	(is_64bit_abs_reloc): Add R_RISCV_64.
	(is_none_reloc): Add R_RISCV_NONE.
	* testsuite/binutils-all/objdump.exp (cpus_expected): Add riscv.
	Expect the debug_ranges test to fail.

gas	* Makefile.am: Add riscv files.
	* Makefile.in: Regenerate.
	* NEWS: Mention the support for this architecture.
	* configure.in: Define a default architecture.
	* configure: Regenerate.
	* configure.tgt: Add entries for riscv.
	* doc/as.texinfo: Likewise.
	* testsuite/gas/all/gas.exp: Expect the redef tests to fail.
	* testsuite/gas/elf/elf.exp: Expect the groupauto tests to fail.
	* config/tc-riscv.c: New file.
	* config/tc-riscv.h: New file.
	* doc/c-riscv.texi: New file.
	* testsuite/gas/riscv: New directory.
	* testsuite/gas/riscv/riscv.exp: New file.
	* testsuite/gas/riscv/t_insns.d: New file.
	* testsuite/gas/riscv/t_insns.s: New file.

ld	* Makefile.am: Add riscv files.
	* Makefile.in: Regenerate.
	* NEWS: Mention the support for this target.
	* configure.tgt: Add riscv entries.
	* emulparams/elf32lriscv-defs.sh: New file.
	* emulparams/elf32lriscv.sh: New file.
	* emulparams/elf64lriscv-defs.sh: New file.
	* emulparams/elf64lriscv.sh: New file.
	* emultempl/riscvelf.em: New file.

opcodes	* configure.ac: Add entry for bfd_riscv_arch.
	* configure: Regenerate.
	* disassemble.c (disassembler): Add support for riscv.
	(disassembler_usage): Likewise.
	* riscv-dis.c: New file.
	* riscv-opc.c: New file.

include	* dis-asm.h: Add prototypes for print_insn_riscv and
	print_riscv_disassembler_options.
	* elf/riscv.h: New file.
	* opcode/riscv-opc.h: New file.
	* opcode/riscv.h: New file.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] MIPS: Remove remains of IRIX OS ABI support
@ 2016-10-31 17:24 sergiodj+buildbot
  2016-10-31 18:42 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-10-31 17:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT de4bfa865e5ea54f2ab5b7af53e4abe825da699e ***

Author: Maciej W. Rozycki <macro@imgtec.com>
Branch: master
Commit: de4bfa865e5ea54f2ab5b7af53e4abe825da699e

MIPS: Remove remains of IRIX OS ABI support

Complement commit 3831839c089c ("Delete IRIX support") and remove dead
MIPS target IRIX OS ABI support code.

	gdb/
	* defs.h (gdb_osabi): Remove GDB_OSABI_IRIX enum value.
	* osabi.c (gdb_osabi_names): Remove "Irix" entry.
	* mips-tdep.c (mips_irix_reg_names): Remove.
	(mips_register_type): Remove GDB_OSABI_IRIX code.
	(mips_pseudo_register_type): Likewise.
	(mips_breakpoint_from_pc): Likewise.
	(mips_gdbarch_init): Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] gdb/NEWS: Mention C++11 requirement
@ 2016-10-29 16:50 sergiodj+buildbot
  2016-10-29 17:55 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-10-29 16:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d29469235333ac99df5476499a59998ce49b39fa ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: d29469235333ac99df5476499a59998ce49b39fa

gdb/NEWS: Mention C++11 requirement

gdb/ChangeLog:
2016-10-29  Pedro Alves  <palves@redhat.com>

	* NEWS: Adjust to mention C++11 requirement.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Support command-line redirection in native MS-Windows debugging
@ 2016-10-29 16:13 sergiodj+buildbot
  2016-10-29 16:38 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-10-29 16:13 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8ba42bc5da8015fd0bd9e7f021af9cb0ef252005 ***

Author: Eli Zaretskii <eliz@gnu.org>
Branch: master
Commit: 8ba42bc5da8015fd0bd9e7f021af9cb0ef252005

Support command-line redirection in native MS-Windows debugging

gdb/ChangeLog
2016-10-29  Eli Zaretskii  <eliz@gnu.org>

	* NEWS: Mention support for redirection on MS-Windows.

	* windows-nat.c (redir_open, redir_set_redirection)
	(redirect_inferior_handles) [!__CYGWIN__]: New functions.
	(windows_create_inferior) [!__CYGWIN__]: Use
	'redirect_inferior_handles' to redirect standard handles of the
	debuggee if the command line requests that.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix duplicate test message in mi-trace-save.exp
@ 2016-10-17 23:24 sergiodj+buildbot
  2016-10-18  0:18 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-10-17 23:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e42b25a0407fbbf3529815f69bd56a61b1821295 ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: e42b25a0407fbbf3529815f69bd56a61b1821295

Fix duplicate test message in mi-trace-save.exp

gdb/testsuite/ChangeLog:

	* gdb.trace/mi-trace-save.exp (test_trace_save_wrong_num_args):
	Change test message.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix comment in mi-trace-save.exp
@ 2016-10-17 21:50 sergiodj+buildbot
  2016-10-17 22:53 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-10-17 21:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3ccdb4324b0dc9fa46ee7cad9b370f8c7c370c3b ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: 3ccdb4324b0dc9fa46ee7cad9b370f8c7c370c3b

Fix comment in mi-trace-save.exp

This fixes a comment I forgot to update in the previous patch.

gdb/testsuite/ChangeLog:

	* gdb.trace/mi-trace-save.exp (test_trace_save_wrong_num_args):
	Update comment.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] gdb: Fix phony iconv build
@ 2016-10-17 16:34 sergiodj+buildbot
  2016-10-17 17:22 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-10-17 16:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5562a44eb490b5777c9e786971907c0727d88495 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 5562a44eb490b5777c9e786971907c0727d88495

gdb: Fix phony iconv build

Cross building gdb for mingw32 on Fedora 23 fails with:

  x86_64-w64-mingw32-g++ -g -O2  [...]  ../../src/gdb/charset.c
  In file included from ../../src/gdb/charset.c:21:0:
  ../../src/gdb/charset.h:134:3: error: 'iconv_t' does not name a type
     iconv_t m_desc;
     ^
  ../../src/gdb/charset.c: In constructor 'wchar_iterator::wchar_iterator(const gdb_byte*, size_t, const char*, size_t)':
  ../../src/gdb/charset.c:600:3: error: 'm_desc' was not declared in this scope
     m_desc = iconv_open (INTERMEDIATE_ENCODING, charset);
     ^
  ../../src/gdb/charset.c: In destructor 'wchar_iterator::~wchar_iterator()':
  ../../src/gdb/charset.c:607:7: error: 'm_desc' was not declared in this scope
     if (m_desc != (iconv_t) -1)
	 ^
  ../../src/gdb/charset.c: In member function 'int wchar_iterator::iterate(wchar_iterate_result*, gdb_wchar_t**, const gdb_byte**, size_t*)':
  ../../src/gdb/charset.c:633:25: error: 'm_desc' was not declared in this scope
	 size_t r = iconv (m_desc, &inptr, &m_bytes, &outptr, &out_avail);
			   ^

This is a regression caused by commit cda6c55bd399 (Turn wchar
iterator into a class).  The problem is that iconv_t is now exposed in
gdb/charset.h, while before it was only used in gdb/charset.c.

gdb/charset.c, under #ifdef PHONY_ICONV, does:

 #undef iconv_t
 #define iconv_t int

So it seems the simplest is to use 'int' in the header file too.

gdb/ChangeLog:
2016-10-17  Pedro Alves  <palves@redhat.com>

	* charset.h (class wchar_iterator) [PHONY_ICONV] <m_desc>: Use
	'int' as type.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Removed pseudo invalid instructions opcodes.
@ 2016-10-17 13:56 sergiodj+buildbot
  2016-10-17 14:12 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-10-17 13:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT decf5bd1570be3de10aeab99869a9548d17b1354 ***

Author: Cupertino Miranda <cmiranda@synopsys.com>
Branch: master
Commit: decf5bd1570be3de10aeab99869a9548d17b1354

Removed pseudo invalid instructions opcodes.

The disassember was generating invXXX instructions for cases when in reality we
had llockd or scondd instrutions.

opcodes/ChangeLog:

    Cupertino Miranda  <cmiranda@synopsys.com>
	arc-tbl.h: Removed any "inv.+" instructions from the table.

gas/ChangeLog:

    Cupertino Miranda  <cmiranda@synopsys.com>
        testsuite/arc/dis-inv.s: Test to validate patch.
        testsuite/arc/dis-inv.d: Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Sync libiberty sources with gcc mainline.
@ 2016-10-17  9:46 sergiodj+buildbot
  2016-10-17 10:01 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-10-17  9:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 41f225defe891ff71d3c8a149cdc1ed8f3a64c5c ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: 41f225defe891ff71d3c8a149cdc1ed8f3a64c5c

Sync libiberty sources with gcc mainline.

2016-09-19  Andrew Stubbs  <ams@codesourcery.com>

	* pex-win32.c (argv_to_cmdline): Quote zero-length parameters.
	* testsuite/test-pexecute.c (main): Insert check for zero-length parameters.

2016-09-10  Mark Wielaard  <mjw@redhat.com>

	* cp-demangle.c (d_substitution): Change struct demangle_component
	variable name from c to dc.

2016-08-12  Marek Polacek  <polacek@redhat.com>

	PR c/7652
	* cp-demangle.c (d_print_mod): Add FALLTHRU.

2016-08-04  Marcel B?hme  <boehme.marcel@gmail.com>

	PR c++/71696
	* cplus-dem.c: Prevent infinite recursion when there is a cycle
	in the referencing of remembered mangled types.
	(work_stuff): New stack to keep track of the remembered mangled
	types that are currently being processed.
	(push_processed_type): New method to push currently processed
	remembered type onto the stack.
	(pop_processed_type): New method to pop currently processed
	remembered type from the stack.
	(work_stuff_copy_to_from): Copy values of new variables.
	(delete_non_B_K_work_stuff): Free stack memory.
	(demangle_args): Push/Pop currently processed remembered type.
	(do_type): Do not demangle a cyclic reference and push/pop
	referenced remembered type.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix set sysroot command on AIX
@ 2016-10-14 13:25 sergiodj+buildbot
  2016-10-14 13:34 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-10-14 13:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 754c39c2f32a796ad9983836deb7c4429c808e48 ***

Author: Ulrich Weigand <ulrich.weigand@de.ibm.com>
Branch: master
Commit: 754c39c2f32a796ad9983836deb7c4429c808e48

Fix set sysroot command on AIX

set sysroot command on AIX has no effect if a program depends on shared
library archives (.a).  Fixed by using solib_find and solib_bfd_fopen
instead of gdb_bfd_open in solib_aix_bfd_open.

gdb/
2016-10-14  Sangamesh Mallayya  <sangamesh.swamy@in.ibm.com>
	    Ulrich Weigand  <uweigand@de.ibm.com>

	* solib-aix.c (solib_aix_bfd_open): Call solib_find so that sysroot
	path is set properly if program has a dependency on .a archive and
	sysroot is set via set sysroot command.

Signed-off-by: Ulrich Weigand <ulrich.weigand@de.ibm.com>


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [ARC] Disassembler: fix LIMM detection for short instructions.
@ 2016-10-14 12:37 sergiodj+buildbot
  2016-10-14 12:37 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-10-14 12:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e5b06ef06b062f0626462abb182ee5470cf798bc ***

Author: Claudiu Zissulescu <claziss@synopsys.com>
Branch: master
Commit: e5b06ef06b062f0626462abb182ee5470cf798bc

[ARC] Disassembler: fix LIMM detection for short instructions.

The ARC (short) instructions are using a special register number to
indicate is the instruction uses a long immediate (LIMM).  In the case
of short instruction, this LIMM indicator depends on the ISA version
used. Thus, for ARCv1 processors, the LIMM indicator is 0x3E, the same
value used in "long" instructions.  However, for the ARCv2 processors,
this LIMM indicator is 0x1E.

This patch fixes the LIMM detection for ARCv1 ISA and adds two tests.

gas/
2016-10-13  Claudiu Zissulescu  <claziss@synopsys.com>

	* testsuite/gas/arc/shortlimm_a7.d: New file.
	* testsuite/gas/arc/shortlimm_a7.s: Likewise.
	* testsuite/gas/arc/shortlimm_hs.d: Likewise.
	* testsuite/gas/arc/shortlimm_hs.s: Likewise.

include/
2016-10-13  Claudiu Zissulescu  <claziss@synopsys.com>

	* opcode/arc.h (ARC_OPCODE_ARCV2): New define.

opcodes/
2016-10-13  Claudiu Zissulescu  <claziss@synopsys.com>

        * arc-dis.c (find_format_from_table): Discriminate LIMM indicator
	usage on ISA basis.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Share proc get_var_address
@ 2016-10-13 15:27 sergiodj+buildbot
  2016-10-13 16:29 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-10-13 15:27 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5ad9dba7519caa3e6193c87699ae37e24d0fe05c ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 5ad9dba7519caa3e6193c87699ae37e24d0fe05c

Share proc get_var_address

This patch moves proc get_var_address into lib/gdb.exp, and remove the
duplicate copy in gdb.base/*.exp files.

gdb/testsuite:

2016-10-13  Yao Qi  <yao.qi@linaro.org>

	* gdb.base/code_elim.exp (get_var_address): Remove.
	* gdb.base/relocate.exp: Likewise.
	* gdb.base/shreloc.exp: Likewise.
	* lib/gdb.exp (get_var_address): New.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Skip testing structures with floating points
@ 2016-10-13 14:54 sergiodj+buildbot
  2016-10-13 15:12 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-10-13 14:54 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 62df7e210ebf096dc09ad14d9316fcda0f6217f7 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 62df7e210ebf096dc09ad14d9316fcda0f6217f7

Skip testing structures with floating points

This patch skips some tests related to floating point in structs.exp
if gdb_skip_float_test return false.

gdb/testsuite:

2016-10-13  Yao Qi  <yao.qi@linaro.org>

	* gdb.base/structs.exp: Invoke gdb_skip_float_test, and do
	floating point tests if $skip_float_test is false.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Remove unnecessary null_cleanup
@ 2016-10-13  4:50 sergiodj+buildbot
  2016-10-13  5:06 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-10-13  4:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d1a760cbb796b62f18ff6b81a189fd261809ef74 ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: d1a760cbb796b62f18ff6b81a189fd261809ef74

Remove unnecessary null_cleanup

This patch removes an unnecessary null_cleanup.

2016-10-12  Tom Tromey  <tom@tromey.com>

	* tracepoint.c (trace_dump_command): Remove unnecessary
	null_cleanup.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Turn wchar iterator into a class
@ 2016-10-13  2:59 sergiodj+buildbot
  2016-10-13  3:53 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-10-13  2:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cda6c55bd399a8892d62178d4daeb074def909e0 ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: cda6c55bd399a8892d62178d4daeb074def909e0

Turn wchar iterator into a class

This changes wchar_iterator from charset.c into a real C++ class, then
updates the users to use the class.  This lets us remove some cleanups
in favor of the class' destructor.

2016-10-12  Tom Tromey  <tom@tromey.com>

	* valprint.c (generic_emit_char, count_next_character)
	(generic_printstr): Update.
	* charset.c (struct wchar_iterator): Move to charset.h.
	(wchar_iterator::wchar_iterator): Rename from
	make_wchar_iterator, turn into a constructor.
	(wchar_iterator::~wchar_iterator): Rename from
	do_cleanup_iterator, turn into a destructor.
	(make_cleanup_wchar_iterator): Remove.
	(wchar_iterator::iterate): Rename from wchar_iterate.  Remove
	"iter" argument.  Update.
	* charset.h: Include <vector>.
	(class wchar_iterator): New class, from old struct
	wchar_iterator.
	(make_wchar_iterator, make_cleanup_wchar_iterator): Don't
	declare.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Convert tid_range_parser and get_number_or_range to classes
@ 2016-10-13  1:21 sergiodj+buildbot
  2016-10-13  1:34 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-10-13  1:21 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bfd282882d534cd4f48e2fc29d4ce0923c52352b ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: bfd282882d534cd4f48e2fc29d4ce0923c52352b

Convert tid_range_parser and get_number_or_range to classes

This converts tid_range_parser and get_number_or_range to be classes.
The various tid_range_parser_* and get_number_or_range_* functions
become methods on the respective classes.  Then it updates the users
to follow.

The rationale for the change is that this provides better
encapsulation.  For example, this forced me to think of a better
interface between tid_range_parser and get_number_or_range, since the
former peeked into the latter's internals a bit too much.  That ended
up resulting mostly in these two not-just-straight-1-1 changes:

  void
 -tid_range_parser_skip (struct tid_range_parser *parser)
 +tid_range_parser::skip_range ()
  {
 ...

 -  tid_range_parser_init (parser, parser->range_parser.end_ptr,
 -			 parser->default_inferior);
 +  m_range_parser.skip_range ();
 +  init (m_range_parser.string (), m_default_inferior);
  }

 and:

    /* If we successfully parsed a thread number or finished parsing a
       thread range, switch back to assuming the next TID is
       inferior-qualified.  */
 -  if (parser->range_parser.end_ptr == NULL
 -      || parser->range_parser.string == parser->range_parser.end_ptr)
 +  if (!m_range_parser.in_range ())
      {

For the same reason (encapsulation), this moves the enum
tid_range_state definition to within the tid_parser class's scope,
since that is private implementation detail.

While at it, switch to use "bool" for booleans.

gdb/ChangeLog:
2016-10-13  Pedro Alves  <palves@redhat.com>
	    Tom Tromey  <tom@tromey.com>

	* tid-parse.h (tid_range_parser): New class.
	(enum tid_range_state): Move into tid_range_parser's scope.
	Remove TID_RANGE_ prefix from all values.
	(tid_range_parser_get_tid, tid_range_parser_get_tid_range)
	(tid_range_parser_star_range, tid_range_parser_finished)
	(tid_range_parser_skip, tid_range_parser_qualified): Don't
	declare.
	(tid_is_in_list): Update comment.
	* tid-parse.c (tid_range_parser::tid_range_parser): New.
	(init, finished, get_string, skip, tid_is_qualified)
	(get_tid_or_range, get_tid_range, get_tid, star_range): Rename;
	turn into methods.
	(tid_is_in_list): Adjust.
	* cli/cli-utils.h (number_or_range_parser): New class.
	(init_number_or_range, get_number_or_range)
	(number_range_setup_range): Don't declare.
	* cli/cli-utils.c
	(number_or_range_parser::number_or_range_parser): New.
	(init_number_or_range, get_number_or_range)
	(number_range_setup_range): Rename; turn into methods.
	(number_is_in_list): Adjust.
	* breakpoint.c (map_breakpoint_numbers): Adjust.  Use bool.
	(trace_pass_command, get_tracepoint_by_number): Adjust.
	* breakpoint.h (get_tracepoint_by_number): Adjust.
	* inferior.c (detach_inferior_command, kill_inferior_command)
	(remove_inferior_command): Adjust.
	* linespec.c (decode_line_2): Adjust.
	* memattr.c (mem_enable_command, mem_disable_command)
	(mem_delete_command): Adjust.
	* printcmd.c (map_display_numbers): Adjust.
	* reverse.c (delete_bookmark_command, bookmarks_info): Adjust.
	* thread.c (thread_apply_command): Adjust.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [AArch64] Track FP registers in prologue analyzer
@ 2016-10-12 11:51 sergiodj+buildbot
  2016-10-12 12:26 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-10-12 11:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 187f5d00acf0ffe5390f282fd4d6285bcd6fccb9 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 187f5d00acf0ffe5390f282fd4d6285bcd6fccb9

[AArch64] Track FP registers in prologue analyzer

We don't track FP registers in aarch64 prologue analyzer, so this causes
an internal error when FP registers are saved by "stp" instruction in
prologue (stp	d8, d9, [sp,#128]),

 tbreak _Unwind_RaiseException^M
 aarch64-tdep.c:335: internal-error: CORE_ADDR aarch64_analyze_prologue(gdbarch*, CORE_ADDR, CORE_ADDR, aarch64_prologue_cache*): Assertion `inst.operands[0].type == AARCH64_OPND_Rt' failed.^M
 A problem internal to GDB has been detected,

This patch teaches GDB to track FP registers (D registers) in prologue
analyzer.

gdb:

2016-10-12  Yao Qi  <yao.qi@linaro.org>

	PR tdep/20682
	* aarch64-tdep.c: Replace 32 with AARCH64_D_REGISTER_COUNT.
	(aarch64_analyze_prologue): Extend array 'regs' for D registers.
	Assert that operand 0 and 1 can be X or D registers.  Update
	register number for D registers.  Update registers in frame
	cache.
	* aarch64-tdep.h (AARCH64_D_REGISTER_COUNT): New macro.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] testsuite: Fix gdb.arch/powerpc-prologue.c compilation
@ 2016-10-11 17:27 sergiodj+buildbot
  2016-10-11 17:38 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-10-11 17:27 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8f1a8fc4df2244f548d55fbecce20b7cd6f90e16 ***

Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Branch: master
Commit: 8f1a8fc4df2244f548d55fbecce20b7cd6f90e16

testsuite: Fix gdb.arch/powerpc-prologue.c compilation

gcc-6.2.1

gdb compile failed, gdb/testsuite/gdb.arch/powerpc-prologue.c: In function 'main':
gdb/testsuite/gdb.arch/powerpc-prologue.c:32:3: warning: implicit declaration of function 'optimized_1' [-Wimplicit-function-declaration]
   optimized_1 ();
   ^~~~~~~~~~~

gdb/testsuite/ChangeLog
2016-10-11  Jan Kratochvil  <jan.kratochvil@redhat.com>

	* gdb.arch/powerpc-prologue.c (optimized_1): New declaration.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [AArch64] PR target/20666, fix wrong encoding of new introduced BFC pseudo
@ 2016-10-11 10:42 sergiodj+buildbot
  2016-10-11 10:53 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-10-11 10:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 93562a343c26f67d2bd0e93cceb18a0a793087c2 ***

Author: Jiong Wang <jiong.wang@arm.com>
Branch: master
Commit: 93562a343c26f67d2bd0e93cceb18a0a793087c2

[AArch64] PR target/20666, fix wrong encoding of new introduced BFC pseudo

opcode/
	PR target/20666
	* aarch64-asm.c (convert_bfc_to_bfm): Fix dest index.

gas/
	* testsuite/gas/aarch64/alias-2.d: Update expected results.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Always descend into output section statements in lang_do_assignments
@ 2016-10-11  7:59 sergiodj+buildbot
  2016-10-11  8:11 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-10-11  7:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f02cb058822459ea29a9fdaa928c2623df435908 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: f02cb058822459ea29a9fdaa928c2623df435908

Always descend into output section statements in lang_do_assignments

See https://sourceware.org/ml/binutils/2016-07/msg00091.html
This patch stop --gc-sections elf_gc_sweep_symbol localizing symbols
that ought to remain global.

The difficulty with always descending into output section statements
is that symbols defined by the script in such statements don't have
a bfd section when lang_do_assignments runs early in the link process.
There are two approaches to curing this problem.  Either we can
create the bfd section early, or we can use a special section.  This
patch takes the latter approach and uses bfd_und_section.  (Creating
bfd sections early results in changed output section order, and thus
lots of testsuite failures.  You can't create all output sections
early to ensure proper ordering as KEEP then stops empty sections
from being stripped.)

The wrinkle with this approach is that some code that runs at
gc-sections time needs to be made aware of the odd defined symbols
using bfd_und_section.

bfd/
	* elf64-x86-64.c (elf_x86_64_convert_load_reloc): Handle symbols
	defined temporarily with bfd_und_section.
	* elflink.c (_bfd_elf_gc_keep): Don't set SEC_KEEP for bfd_und_section.
	* elfxx-mips.c (mips_elf_local_pic_function_p): Exclude defined
	symbols with bfd_und_section.
ld/
	* ldlang.c (lang_do_assignments_1): Descend into output section
	statements that do not yet have bfd sections.  Set symbol section
	temporarily for symbols defined in such statements to the undefined
	section.  Don't error on data or reloc statements until final phase.
	* ldexp.c (exp_fold_tree_1 <etree_assign>): Handle bfd_und_section
	in expld.section.
	* testsuite/ld-mmix/bpo-10.d: Adjust.
	* testsuite/ld-mmix/bpo-11.d: Adjust.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Remove v850_dbtrap_breakpoint_from_pc
@ 2016-10-10  9:44 sergiodj+buildbot
  2016-10-10  9:55 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-10-10  9:44 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ff12a6593a1675aa9ba5340aa2984af19cf8966c ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: ff12a6593a1675aa9ba5340aa2984af19cf8966c

Remove v850_dbtrap_breakpoint_from_pc

v850 has two functions to install to gdbarch_breakpoint_from_pc,
and it selects one according to info.bfd_arch_info->mach.  However,
we can select the kind/length of breakpoint instruction inside
v850_breakpoint_from_pc by gdbarch_bfd_arch_info (gdbarch)->mach.
This patch is to do that, and remove v850_dbtrap_breakpoint_from_pc.

gdb:

2016-08-30  Yao Qi  <yao.qi@linaro.org>

	* v850-tdep.c (v850_breakpoint_from_pc): Use the right
	breakpoint instruction.
	(v850_dbtrap_breakpoint_from_pc): Remove.
	(v850_gdbarch_init): Update.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] ui-out.c: Remove unused parameter to push_level
@ 2016-10-09  0:26 sergiodj+buildbot
  2016-10-09  1:52 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-10-09  0:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 49d06418ada11004ca1cdc0ec5847358e83fc67a ***

Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: 49d06418ada11004ca1cdc0ec5847358e83fc67a

ui-out.c: Remove unused parameter to push_level

The parameter "id" is unused.

gdb/ChangeLog:

	* ui-out.c (push_level): Remove "id" parameter.
	(ui_out_begin): Update call.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] bfd_merge_private_bfd_data tidy
@ 2016-10-07  7:33 sergiodj+buildbot
  2016-10-07 10:45 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-10-07  7:33 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1047201fd0f402428bb3331638a198413f97f476 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 1047201fd0f402428bb3331638a198413f97f476

bfd_merge_private_bfd_data tidy

bfd_merge_private_bfd_data and _bfd_generic_verify_endian_match are
linker functions, so move them to linker.c.

bfd/
	* Makefile.am (LIBBFD_H_FILES): Update.
	* doc/Makefile.am (LIBBFD_H_DEP): Likewise.
	* cpu-sh.c (sh_merge_bfd_arch): Move to..
	* elf32-sh.c: ..here, and make static.
	* elf32-arc.c (arc_elf_merge_private_bfd_data): Delete extraneous
	error.
	* elf32-cris.c (cris_elf_merge_private_bfd_data): Don't call
	_bfd_generic_verify_endian_match.
	* elf32-microblaze.c (microblaze_elf_merge_private_bfd_data): Delete.
	(bfd_elf32_bfd_merge_private_bfd_data): Define as
	_bfd_generic_verify_endian_match.
	* elf32-mt.c (mt_elf_merge_private_bfd_data): Don't test
	boolean == FALSE.
	* elf32-xgate.c (_bfd_xgate_elf_merge_private_bfd_data): Delete.
	(bfd_elf32_bfd_merge_private_bfd_data): Don't define.
	* elf32-xgate.h (_bfd_xgate_elf_merge_private_bfd_data): Delete.
	* libbfd-in.h (_bfd_generic_verify_endian_match): Delete.
	* libbfd.c (_bfd_generic_verify_endian_match): Move to..
	* linker.c: ..here, and make internal.
	* bfd.c (bfd_merge_private_bfd_data): Move to..
	* linker.c: ..here.
	* Makefile.in: Regenerate.
	* doc/Makefile.in: Regenerate.
	* bfd-in2.h: Regenerate.
	* libbfd.h: Regenerate.
opcodes/
	* sh-opc.h (sh_merge_bfd_arch): Delete prototype.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] python: accept address and explicit locations in gdb.decode_line
@ 2016-10-07  7:22 sergiodj+buildbot
  2016-10-07 13:19 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-10-07  7:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 68dadef54c216f7ec75c27d74193897b18c5f9ab ***

Author: Markus Metzger <markus.t.metzger@intel.com>
Branch: master
Commit: 68dadef54c216f7ec75c27d74193897b18c5f9ab

python: accept address and explicit locations in gdb.decode_line

The gdb.decode_line python function is documented to support the same location
expressions as the "break" command.  It currently expects a linespec location.

Instead of creating a linespec location directly, create the location via
string_to_event_location_basic.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix gdb.Value->python conversion for large unsigned ints.
@ 2016-10-07  4:51 sergiodj+buildbot
  2016-10-07  8:03 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-10-07  4:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 33fa2c6e1b1e63599156f7d79de8c0a6ea69c8af ***

Author: Doug Evans <dje@google.com>
Branch: master
Commit: 33fa2c6e1b1e63599156f7d79de8c0a6ea69c8af

Fix gdb.Value->python conversion for large unsigned ints.

gdb/ChangeLog:

	* python/py-value.c (valpy_long): Handle unsigned values.

gdb/testsuite/ChangeLog:

	* gdb.python/py-value.exp (test_value_creation): Add test for large
	unsigned 64-bit value.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] gdb: Remove some C compiler support leftovers
@ 2016-10-06 23:29 sergiodj+buildbot
  2016-10-07  8:56 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-10-06 23:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ddb6d633875b76f9d772af901118233fc498253a ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: ddb6d633875b76f9d772af901118233fc498253a

gdb: Remove some C compiler support leftovers

Remove some __cplusplus checks, inline EXPORTED_CONST, and update some comments.

gdb/ChangeLog:
2016-10-06  Pedro Alves  <palves@redhat.com>

	* cp-valprint.c (vtbl_ptr_name): Write "extern const" instead of
	EXPORTED_CONST.
	* stub-termcap.c: Remove __cplusplus checks.
	* common/common-defs.h [!__cplusplus] (EXTERN_C, EXTERN_C_PUSH,
	EXTERN_C_POP): Delete.
	* common/common-exceptions.h (GDB_XCPT_SJMP): Update comments.
	(GDB_XCPT) [!__cplusplus]: Delete.
	(throw_exception, throw_exception_sjlj): Update comments.
	* guile/guile-internal.h (as_a_scm_t_subr) [!__cplusplus]: Delete.
	* guile/guile.c (extension_language_guile): Write "extern const"
	instead of EXPORTED_CONST.
	* features/feature_to_c.sh: Don't emit !__cplusplus code.  Write
	"extern const" instead of EXPORTED_CONST.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] testsuite: solib-disc: Use `standard_output_file'
@ 2016-10-06 16:49 sergiodj+buildbot
  2016-10-06 18:21 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-10-06 16:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7470adbb872d5363580eb5e0a8dbb231c286ee4c ***

Author: Maciej W. Rozycki <macro@imgtec.com>
Branch: master
Commit: 7470adbb872d5363580eb5e0a8dbb231c286ee4c

testsuite: solib-disc: Use `standard_output_file'

Correct a commit 2151ccc56c74 ("Always organize test artifacts in a
directory hierarchy") regression causing:

Running .../gdb/testsuite/gdb.base/solib-disc.exp ...
gdb compile failed, Assembler messages:
Fatal error: can't create .../gdb/testsuite/gdb.base/so-disc-shr.c.o: No such file or directory

by using `standard_output_file' to construct output file names
throughout.

	gdb/testsuite/
	* gdb.base/solib-disc.exp: Use `standard_output_file'
	throughout.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Don't use boolean OR in arithmetic expressions
@ 2016-10-06  0:04 sergiodj+buildbot
  2016-10-06  3:36 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-10-06  0:04 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 616ec3583b7b6ba0a4e581c426b700b0664a3027 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 616ec3583b7b6ba0a4e581c426b700b0664a3027

Don't use boolean OR in arithmetic expressions

bfd/
	* elf32-epiphany.c (epiphany_final_link_relocate): Use bitwise
	OR in arithmetic expression, not boolean OR.
opcodes/
	* cr16-dis.c (print_insn_cr16): Don't use boolean OR in arithmetic.
	* crx-dis.c (print_insn_crx): Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] PR gdb/20653 - small cleanup in string_to_explicit_location
@ 2016-10-05 17:55 sergiodj+buildbot
  2016-10-05 19:32 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-10-05 17:55 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e742d386c480efa5229bc8b1887a7718f840a457 ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: e742d386c480efa5229bc8b1887a7718f840a457

PR gdb/20653 - small cleanup in string_to_explicit_location

This bug points out that string_to_explicit_location compares a char*
against '\0'; whereas comparing against NULL is more normal.

2016-10-05  Tom Tromey  <tom@tromey.com>

	PR breakpoints/20653:
	* location.c (string_to_explicit_location): Use NULL, not '\0'.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] PR symtab/20652 - fix psymbol_compare
@ 2016-10-05 17:49 sergiodj+buildbot
  2016-10-05 18:19 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-10-05 17:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3e611445bf05fa20e0befa41afa42651d1983734 ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 3e611445bf05fa20e0befa41afa42651d1983734

PR symtab/20652 - fix psymbol_compare

This fixes an oversight in psymbol_compare.

2016-10-05  Tom Tromey  <tom@tromey.com>

	PR symtab/20652:
	* psymtab.c (psymbol_compare): Correctly compare "ginfo.value"
	fields.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] arc: Remove annoying debug message
@ 2016-10-05 14:41 sergiodj+buildbot
  2016-10-05 14:48 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-10-05 14:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ed2f09e183df513e9616c53cdace32cf8b824b98 ***

Author: Anton Kolesov <Anton.Kolesov@synopsys.com>
Branch: master
Commit: ed2f09e183df513e9616c53cdace32cf8b824b98

arc: Remove annoying debug message

The logging message is called too often - once for each register when it's
value has to be evaluated. This floods the screen for commands like "info
register all", but doesn't give really any help at debugging GDB issues.
Between increasing the debug level of this message and removing it altogether I
think that removing it is preferable.

gdb/ChangeLog:

	arc-tdep.c (arc_frame_prev_register): Remove annoying log message.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Update the path arm-*.xml files for aarch64
@ 2016-10-05 11:11 sergiodj+buildbot
  2016-10-05 13:38 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-10-05 11:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c1d0b70ae517512a77eed778c6dd7d8a941962fc ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: c1d0b70ae517512a77eed778c6dd7d8a941962fc

Update the path arm-*.xml files for aarch64

0a69eedb (Clean up the XML files for ARM) breaks the GDBserver build
on aarch64 because some arm-*.xml files can't be found.

This patch is to fix the build failure.

gdb/gdbserver:

2016-10-05  Yao Qi  <yao.qi@linaro.org>

	* configure.srv: Update the path of arm-*.xml files.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Generate s390 target description c files
@ 2016-10-05  9:18 sergiodj+buildbot
  2016-10-05 11:10 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-10-05  9:18 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT defaaad59909ead1722f978463fc2e4bdeb0629c ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: defaaad59909ead1722f978463fc2e4bdeb0629c

Generate s390 target description c files

If I delete all target description c files under features/ directory,
and run make GDB=/scratch/yao/gdb/build-git/all-targets/gdb/gdb cfiles,
some s390 target description c files are not generated.

This patch adds these s390 xml files to XMLTOC, so these c files can
be generated.

gdb:

2016-10-05  Yao Qi  <yao.qi@linaro.org>

	* features/Makefile (XMLTOC): Add s390-tevx-linux64.xml,
	s390-vx-linux64.xml, s390x-tevx-linux64.xml and
	s390x-vx-linux64.xml.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Add missing dependencies to BFD_H_FILES
@ 2016-09-30 19:17 sergiodj+buildbot
  2016-09-30 19:32 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-09-30 19:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 92c6e4fe5d6f30a24fe15795a6a3b25afd0b24c9 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 92c6e4fe5d6f30a24fe15795a6a3b25afd0b24c9

Add missing dependencies to BFD_H_FILES

	* Makefile.am (BFD_H_FILES): Add linker.c and simple.c.  Sort
	as per comment at head of bfd-in2.h.
	* Makefile.in: Regenerate.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [ARM] PR ld/20608 Relocation truncated to fit: R_ARM_THM_JUMP24 for relocation to PLT entry
@ 2016-09-28 22:44 sergiodj+buildbot
  2016-09-28 23:50 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-09-28 22:44 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2df2751d1927e1231bbe7d548139da98d6ca9b9a ***

Author: Christophe Lyon <christophe.lyon@linaro.org>
Branch: master
Commit: 2df2751d1927e1231bbe7d548139da98d6ca9b9a

[ARM] PR ld/20608 Relocation truncated to fit: R_ARM_THM_JUMP24 for relocation to PLT entry

2016-09-28  Christophe Lyon  <christophe.lyon@linaro.org>

	PR ld/20608
	bfd/
	* elf32-arm.c (arm_type_of_stub): Handle the case when the pre-PLT
	Thumb-ARM stub is too far.

	ld
	* testsuite/ld-arm/arm-elf.exp: Handle new testcase.
	* testsuite/ld-arm/farcall-mixed-app2.d: New file.
	* testsuite/ld-arm/farcall-mixed-app2.r: Likewise.
	* testsuite/ld-arm/farcall-mixed-app2.s: Likewise.
	* testsuite/ld-arm/farcall-mixed-app2.sym: Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Ensure that the timestamp in PE/COFF headers is always initialised.
@ 2016-09-28  0:56 sergiodj+buildbot
  2016-09-28  1:27 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-09-28  0:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1c5f704fc035bc705dee887418f42cb8bca24b5d ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: 1c5f704fc035bc705dee887418f42cb8bca24b5d

Ensure that the timestamp in PE/COFF headers is always initialised.

	PR ld/20634
	* peXXigen.c (_bfd_XXi_only_swap_filehdr_out): Put 0 in the
	timestamp field if real time values are not being stored.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix the calculation of AMD64_PCRQUAD relocations.
@ 2016-09-26 22:57 sergiodj+buildbot
  2016-09-27  1:30 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-09-26 22:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 384f7503344b1d07561f801ced7493858cde6164 ***

Author: Awson <kyrab@mail.ru>
Branch: master
Commit: 384f7503344b1d07561f801ced7493858cde6164

Fix the calculation of AMD64_PCRQUAD relocations.

	PR ld/17955
	* coff-x86_64.c (coff_amd64_rtype_to_howto): Use an 8 byte offset
	for R_AMD64_PCRQUAD relocations.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Call debug_exit in linux_wait_1
@ 2016-09-26 11:09 sergiodj+buildbot
  2016-09-26 15:44 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-09-26 11:09 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT edeeb6024373d865284903f0b96b9811afde0441 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: edeeb6024373d865284903f0b96b9811afde0441

Call debug_exit in linux_wait_1

When I read the GDBserver debug message, I find the "entering" of
linux_wait_1 doesn't match the "existing" of linux_wait_1.  Looks
we don't call debug_exit somewhere in linux_wait_1 on return.

gdb/gdbserver:

2016-09-26  Yao Qi  <yao.qi@linaro.org>

	* linux-low.c (linux_wait_1): Call debug_exit.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Use std::vector in objfiles.c
@ 2016-09-24  4:16 sergiodj+buildbot
  2016-09-24 15:24 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-09-24  4:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cfe826d45ea2e15f0df4c039dfa4b9ea605831da ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: cfe826d45ea2e15f0df4c039dfa4b9ea605831da

Use std::vector in objfiles.c

This patch changes a spot in objfiles.c to use a std::vector, removing
a cleanup.

2016-09-23  Tom Tromey  <tom@tromey.com>

	* objfiles.c: Include <vector>.
	(objfile_relocate): Use std::vector.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Delete relocations associatesd with deleted exidx entries.
@ 2016-09-23 19:06 sergiodj+buildbot
  2016-09-24  2:26 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-09-23 19:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5025eb7c0d87b01507116353b5d63b163d7add3d ***

Author: Akihiko Odaki <akihiko.odaki.4i@stu.hosei.ac.jp>
Branch: master
Commit: 5025eb7c0d87b01507116353b5d63b163d7add3d

Delete relocations associatesd with deleted exidx entries.

	PR ld/20595
ld	* testsuite/ld-arm/unwind-4.d: Add -q option to linker command
	line and -r option to objdump command line.  Match emitted relocs
	to make sure that superflous relocs are not generated.

bfd	* elf-bfd.h (struct elf_backend_data): Add
	elf_backend_count_output_relocs callback to count relocations in
	the final output.
	* elf-arm.c (elf32_arm_add_relocation): Deleted.
	(elf32_arm_write_section): Move additional relocation to emit_relocs.
	(elf32_arm_count_output_relocs): New function.
	(emit_relocs): New function.
	(elf32_arm_emit_relocs): New function.
	(elf32_arm_vxworks_emit_relocs): New function.
	(elf_backend_emit_relocs): Updated to use the new functions.
	(elf_backend_count_output_relocs): New define.
	* bfd/elflink.c (bfd_elf_final_link): Do not add additional_reloc_count
	to the relocation count.
	(_bfd_elf_link_size_reloc_section): Use callback to count the
	relocations which will be in output.
	(_bfd_elf_default_count_output_relocs): New function.
	* bfd/elfxx-target.h (elf_backend_count_output_relocs): New define.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix build breakage from commit 6ec2b2
@ 2016-09-22 23:04 sergiodj+buildbot
  2016-09-23 22:22 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-09-22 23:04 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT de6784544abc97d5e396cb1e83eda1ae09f63d40 ***

Author: Edjunior Barbosa Machado <emachado@linux.vnet.ibm.com>
Branch: master
Commit: de6784544abc97d5e396cb1e83eda1ae09f63d40

Fix build breakage from commit 6ec2b2

I was notified by buildbot that my patch (commit 6ec2b2) has broken the build
on x86_64:

../../binutils-gdb/gdb/rs6000-tdep.c: In function int ppc_process_record_op31(gdbarch*, regcache*, CORE_ADDR, uint32_t):
../../binutils-gdb/gdb/rs6000-tdep.c:4705:50: error: cannot convert CORE_ADDR* {aka long unsigned int*} to ULONGEST* {aka long long unsigned int*} for argument 3 to register_status regcache_raw_read_unsigned(regcache*, int, ULONGEST*)
         tdep->ppc_gp0_regnum + PPC_RA (insn), &ea);
                                                  ^
../../binutils-gdb/gdb/rs6000-tdep.c:4718:50: error: cannot convert CORE_ADDR* {aka long unsigned int*} to ULONGEST* {aka long long unsigned int*} for argument 3 to register_status regcache_raw_read_unsigned(regcache*, int, ULONGEST*)
         tdep->ppc_gp0_regnum + PPC_RA (insn), &ea);
                                                  ^
The patch below should fix it.

gdb/ChangeLog:
2016-09-22  Edjunior Barbosa Machado  <emachado@linux.vnet.ibm.com>

	* rs6000-tdep.c (ppc_process_record_op31): Fix
	regcache_raw_read_unsigned call using the correct parameter type.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] PR gdb/20604 - fix "quit" when an invalid expression is used
@ 2016-09-22 14:56 sergiodj+buildbot
  2016-09-23 16:24 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-09-22 14:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 36cf1806a87fdd208c704d0768af232ce35aae9f ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 36cf1806a87fdd208c704d0768af232ce35aae9f

PR gdb/20604 - fix "quit" when an invalid expression is used

This fixes PR gdb/20604.  The bug here is that passing an invalid
expression to "quit" -- e.g., "quit()" -- causes gdb to enter a
non-functioning state.

The immediate problem is that quit_force resets the terminal before
evaluating the expression.  However, it seemed to me that it doesn't
really make sense to pass the quit_force argument to kill_or_detach
(which passes it to to_detach), first because conflating the exit
status for "quit" and the signal to pass when detaching doesn't make
sense, and second because to_detach implementations generally only
accept a constant here, while "quit" accepts an expression.  So, I
removed that.

As an aside, I think the "detach SIGNO" functionality is not
documented.

Built and regtested on x86-64 Fedora 24.

2016-09-21  Tom Tromey  <tom@tromey.com>

	PR gdb/20604:
	* top.h (quit_force): Update.
	* top.c (quit_force): Changed type of first argument.  Don't
	evaluate expression.  Pass NULL to kill_or_detach.
	* cli/cli-cmds.c (quit_command): Evaluate "args".

2016-09-21  Tom Tromey  <tom@tromey.com>

	PR gdb/20604:
	* gdb.base/quit.exp: New file.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [AArch64] Use "must" rather than "should" in error messages
@ 2016-09-22 12:08 sergiodj+buildbot
  2016-09-23  6:48 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-09-22 12:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ab3b8fcfdb06695d27eaec4eedb019ada4a5713e ***

Author: Richard Sandiford <richard.sandiford@arm.com>
Branch: master
Commit: ab3b8fcfdb06695d27eaec4eedb019ada4a5713e

[AArch64] Use "must" rather than "should" in error messages

One of the review comments from the SVE series was that it would
be better to use "must" rather than "should" in error messages.
I think this patch fixes all cases in the AArch64 code.
It also uses "must be" instead of "expected to be".

opcodes/
	* aarch64-opc.c (operand_general_constraint_met_p): Use "must be"
	rather than "should be" or "expected to be" in error messages.

gas/
	* config/tc-aarch64.c (output_operand_error_record): Use "must be"
	rather than "should be" or "expected to be" in error messages.
	(parse_operands): Likewise.
	* testsuite/gas/aarch64/diagnostic.l: Likewise.
	* testsuite/gas/aarch64/legacy_reg_names.l: Likewise.
	* testsuite/gas/aarch64/sve-invalid.l: Likewise.
	* testsuite/gas/aarch64/sve-reg-diagnostic.l: Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [AArch64][SVE 31/32] Add SVE instructions
@ 2016-09-22 10:26 sergiodj+buildbot
  2016-09-23  3:18 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-09-22 10:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c0890d26289c4dad0e2ddedb7822a32a0645d150 ***

Author: Richard Sandiford <richard.sandiford@arm.com>
Branch: master
Commit: c0890d26289c4dad0e2ddedb7822a32a0645d150

[AArch64][SVE 31/32] Add SVE instructions

This patch adds the SVE instruction definitions and associated OP_*
enum values.

include/
	* opcode/aarch64.h (AARCH64_FEATURE_SVE): New macro.
	(OP_MOV_P_P, OP_MOV_Z_P_Z, OP_MOV_Z_V, OP_MOV_Z_Z, OP_MOV_Z_Zi)
	(OP_MOVM_P_P_P, OP_MOVS_P_P, OP_MOVZS_P_P_P, OP_MOVZ_P_P_P)
	(OP_NOTS_P_P_P_Z, OP_NOT_P_P_P_Z): New aarch64_ops.

opcodes/
	* aarch64-tbl.h (OP_SVE_B, OP_SVE_BB, OP_SVE_BBBU, OP_SVE_BMB)
	(OP_SVE_BPB, OP_SVE_BUB, OP_SVE_BUBB, OP_SVE_BUU, OP_SVE_BZ)
	(OP_SVE_BZB, OP_SVE_BZBB, OP_SVE_BZU, OP_SVE_DD, OP_SVE_DDD)
	(OP_SVE_DMD, OP_SVE_DMH, OP_SVE_DMS, OP_SVE_DU, OP_SVE_DUD, OP_SVE_DUU)
	(OP_SVE_DUV_BHS, OP_SVE_DUV_BHSD, OP_SVE_DZD, OP_SVE_DZU, OP_SVE_HB)
	(OP_SVE_HMD, OP_SVE_HMS, OP_SVE_HU, OP_SVE_HUU, OP_SVE_HZU, OP_SVE_RR)
	(OP_SVE_RURV_BHSD, OP_SVE_RUV_BHSD, OP_SVE_SMD, OP_SVE_SMH, OP_SVE_SMS)
	(OP_SVE_SU, OP_SVE_SUS, OP_SVE_SUU, OP_SVE_SZS, OP_SVE_SZU, OP_SVE_UB)
	(OP_SVE_UUD, OP_SVE_UUS, OP_SVE_VMR_BHSD, OP_SVE_VMU_SD)
	(OP_SVE_VMVD_BHS, OP_SVE_VMVU_BHSD, OP_SVE_VMVU_SD, OP_SVE_VMVV_BHSD)
	(OP_SVE_VMVV_SD, OP_SVE_VMV_BHSD, OP_SVE_VMV_HSD, OP_SVE_VMV_SD)
	(OP_SVE_VM_SD, OP_SVE_VPU_BHSD, OP_SVE_VPV_BHSD, OP_SVE_VRR_BHSD)
	(OP_SVE_VRU_BHSD, OP_SVE_VR_BHSD, OP_SVE_VUR_BHSD, OP_SVE_VUU_BHSD)
	(OP_SVE_VUVV_BHSD, OP_SVE_VUVV_SD, OP_SVE_VUV_BHSD, OP_SVE_VUV_SD)
	(OP_SVE_VU_BHSD, OP_SVE_VU_HSD, OP_SVE_VU_SD, OP_SVE_VVD_BHS)
	(OP_SVE_VVU_BHSD, OP_SVE_VVVU_SD, OP_SVE_VVV_BHSD, OP_SVE_VVV_SD)
	(OP_SVE_VV_BHSD, OP_SVE_VV_HSD_BHS, OP_SVE_VV_SD, OP_SVE_VWW_BHSD)
	(OP_SVE_VXX_BHSD, OP_SVE_VZVD_BHS, OP_SVE_VZVU_BHSD, OP_SVE_VZVV_BHSD)
	(OP_SVE_VZVV_SD, OP_SVE_VZV_SD, OP_SVE_V_SD, OP_SVE_WU, OP_SVE_WV_BHSD)
	(OP_SVE_XU, OP_SVE_XUV_BHSD, OP_SVE_XVW_BHSD, OP_SVE_XV_BHSD)
	(OP_SVE_XWU, OP_SVE_XXU): New macros.
	(aarch64_feature_sve): New variable.
	(SVE): New macro.
	(_SVE_INSN): Likewise.
	(aarch64_opcode_table): Add SVE instructions.
	* aarch64-opc.h (extract_fields): Declare.
	* aarch64-opc-2.c: Regenerate.
	* aarch64-asm.c (do_misc_encoding): Handle the new SVE aarch64_ops.
	* aarch64-asm-2.c: Regenerate.
	* aarch64-dis.c (extract_fields): Make global.
	(do_misc_decoding): Handle the new SVE aarch64_ops.
	* aarch64-dis-2.c: Regenerate.

gas/
	* doc/c-aarch64.texi: Document the "sve" feature.
	* config/tc-aarch64.c (REG_TYPE_R_Z_BHSDQ_VZP): New register type.
	(get_reg_expected_msg): Handle it.
	(parse_operands): When parsing operands of an SVE instruction,
	disallow immediates that match REG_TYPE_R_Z_BHSDQ_VZP.
	(aarch64_features): Add an entry for SVE.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [AArch64][SVE 24/32] Add AARCH64_OPND_SVE_PATTERN_SCALED
@ 2016-09-22  5:23 sergiodj+buildbot
  2016-09-22 13:37 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-09-22  5:23 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2442d8466e221ba6cf4ec4bd2a819fdcb1e5ea7e ***

Author: Richard Sandiford <richard.sandiford@arm.com>
Branch: master
Commit: 2442d8466e221ba6cf4ec4bd2a819fdcb1e5ea7e

[AArch64][SVE 24/32] Add AARCH64_OPND_SVE_PATTERN_SCALED

Some SVE instructions count the number of elements in a given vector
pattern and allow a scale factor of [1, 16] to be applied to the result.
This scale factor is written ", MUL #n", where "MUL" is a new operator.
E.g.:

	UQINCD	X0, POW2, MUL #2

This patch adds support for this kind of operand.

All existing operators were shifts of some kind, so there was a natural
range of [0, 63] regardless of context.  This was then narrowered further
by later checks (e.g. to [0, 31] when used for 32-bit values).

In contrast, MUL doesn't really have a natural context-independent range.
Rather than pick one arbitrarily, it seemed better to make the "shift"
amount a full 64-bit value and leave the range test to the usual
operand-checking code.  I've rearranged the fields of aarch64_opnd_info
so that this doesn't increase the size of the structure (although I don't
think its size is critical anyway).

include/
	* opcode/aarch64.h (AARCH64_OPND_SVE_PATTERN_SCALED): New
	aarch64_opnd.
	(AARCH64_MOD_MUL): New aarch64_modifier_kind.
	(aarch64_opnd_info): Make shifter.amount an int64_t and
	rearrange the fields.

opcodes/
	* aarch64-tbl.h (AARCH64_OPERANDS): Add an entry for
	AARCH64_OPND_SVE_PATTERN_SCALED.
	* aarch64-opc.h (FLD_SVE_imm4): New aarch64_field_kind.
	* aarch64-opc.c (fields): Add a corresponding entry.
	(set_multiplier_out_of_range_error): New function.
	(aarch64_operand_modifiers): Add entry for AARCH64_MOD_MUL.
	(operand_general_constraint_met_p): Handle
	AARCH64_OPND_SVE_PATTERN_SCALED.
	(print_register_offset_address): Use PRIi64 to print the
	shift amount.
	(aarch64_print_operand): Likewise.  Handle
	AARCH64_OPND_SVE_PATTERN_SCALED.
	* aarch64-opc-2.c: Regenerate.
	* aarch64-asm.h (ins_sve_scale): New inserter.
	* aarch64-asm.c (aarch64_ins_sve_scale): New function.
	* aarch64-asm-2.c: Regenerate.
	* aarch64-dis.h (ext_sve_scale): New inserter.
	* aarch64-dis.c (aarch64_ext_sve_scale): New function.
	* aarch64-dis-2.c: Regenerate.

gas/
	* config/tc-aarch64.c (SHIFTED_MUL): New parse_shift_mode.
	(parse_shift): Handle it.  Reject AARCH64_MOD_MUL for all other
	shift modes.  Skip range tests for AARCH64_MOD_MUL.
	(process_omitted_operand): Handle AARCH64_OPND_SVE_PATTERN_SCALED.
	(parse_operands): Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [AArch64][SVE 22/32] Add qualifiers for merging and zeroing predication
@ 2016-09-22  4:21 sergiodj+buildbot
  2016-09-22 10:36 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-09-22  4:21 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d50c751e00b5336b4604b92271ab84615fdb0d27 ***

Author: Richard Sandiford <richard.sandiford@arm.com>
Branch: master
Commit: d50c751e00b5336b4604b92271ab84615fdb0d27

[AArch64][SVE 22/32] Add qualifiers for merging and zeroing predication

This patch adds qualifiers to represent /z and /m suffixes on
predicate registers.

include/
	* opcode/aarch64.h (AARCH64_OPND_QLF_P_Z): New aarch64_opnd_qualifier.
	(AARCH64_OPND_QLF_P_M): Likewise.

opcodes/
	* aarch64-opc.c (aarch64_opnd_qualifiers): Add entries for
	AARCH64_OPND_QLF_P_[ZM].
	(aarch64_print_operand): Print /z and /m where appropriate.

gas/
	* config/tc-aarch64.c (vector_el_type): Add NT_zero and NT_merge.
	(parse_vector_type_for_operand): Assert that the skipped character
	is a '.'.
	(parse_predication_for_operand): New function.
	(parse_typed_reg): Parse /z and /m suffixes for predicate registers.
	(vectype_to_qualifier): Handle NT_zero and NT_merge.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [AArch64][SVE 21/32] Add Zn and Pn registers
@ 2016-09-22  2:34 sergiodj+buildbot
  2016-09-22  9:19 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-09-22  2:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f11ad6bc0fc44b94c6970115bb6984b497b967e7 ***

Author: Richard Sandiford <richard.sandiford@arm.com>
Branch: master
Commit: f11ad6bc0fc44b94c6970115bb6984b497b967e7

[AArch64][SVE 21/32] Add Zn and Pn registers

This patch adds the Zn and Pn registers, and associated fields and
operands.

include/
	* opcode/aarch64.h (AARCH64_OPND_CLASS_SVE_REG): New
	aarch64_operand_class.
	(AARCH64_OPND_CLASS_PRED_REG): Likewise.
	(AARCH64_OPND_SVE_Pd, AARCH64_OPND_SVE_Pg3, AARCH64_OPND_SVE_Pg4_5)
	(AARCH64_OPND_SVE_Pg4_10, AARCH64_OPND_SVE_Pg4_16)
	(AARCH64_OPND_SVE_Pm, AARCH64_OPND_SVE_Pn, AARCH64_OPND_SVE_Pt)
	(AARCH64_OPND_SVE_Za_5, AARCH64_OPND_SVE_Za_16, AARCH64_OPND_SVE_Zd)
	(AARCH64_OPND_SVE_Zm_5, AARCH64_OPND_SVE_Zm_16, AARCH64_OPND_SVE_Zn)
	(AARCH64_OPND_SVE_Zn_INDEX, AARCH64_OPND_SVE_ZnxN)
	(AARCH64_OPND_SVE_Zt, AARCH64_OPND_SVE_ZtxN): New aarch64_opnds.

opcodes/
	* aarch64-tbl.h (AARCH64_OPERANDS): Add entries for new SVE operands.
	* aarch64-opc.h (FLD_SVE_Pd, FLD_SVE_Pg3, FLD_SVE_Pg4_5)
	(FLD_SVE_Pg4_10, FLD_SVE_Pg4_16, FLD_SVE_Pm, FLD_SVE_Pn, FLD_SVE_Pt)
	(FLD_SVE_Za_5, FLD_SVE_Za_16, FLD_SVE_Zd, FLD_SVE_Zm_5, FLD_SVE_Zm_16)
	(FLD_SVE_Zn, FLD_SVE_Zt, FLD_SVE_tzsh): New aarch64_field_kinds.
	* aarch64-opc.c (fields): Add corresponding entries here.
	(operand_general_constraint_met_p): Check that SVE register lists
	have the correct length.  Check the ranges of SVE index registers.
	Check for cases where p8-p15 are used in 3-bit predicate fields.
	(aarch64_print_operand): Handle the new SVE operands.
	* aarch64-opc-2.c: Regenerate.
	* aarch64-asm.h (ins_sve_index, ins_sve_reglist): New inserters.
	* aarch64-asm.c (aarch64_ins_sve_index): New function.
	(aarch64_ins_sve_reglist): Likewise.
	* aarch64-asm-2.c: Regenerate.
	* aarch64-dis.h (ext_sve_index, ext_sve_reglist): New extractors.
	* aarch64-dis.c (aarch64_ext_sve_index): New function.
	(aarch64_ext_sve_reglist): Likewise.
	* aarch64-dis-2.c: Regenerate.

gas/
	* config/tc-aarch64.c (NTA_HASVARWIDTH): New macro.
	(AARCH64_REG_TYPES): Add ZN and PN.
	(get_reg_expected_msg): Handle them.
	(parse_vector_type_for_operand): Add a reg_type parameter.
	Skip the width for Zn and Pn registers.
	(parse_typed_reg): Extend vector handling to Zn and Pn.  Update the
	call to parse_vector_type_for_operand.  Set HASVARTYPE for Zn and Pn,
	expecting the width to be 0.
	(parse_vector_reg_list): Restrict error about [BHSD]nn operands to
	REG_TYPE_VN.
	(vectype_to_qualifier): Use S_[BHSD] qualifiers for NTA_HASVARWIDTH.
	(parse_operands): Handle the new Zn and Pn operands.
	(REGSET16): New macro, split out from...
	(REGSET31): ...here.
	(reg_names): Add Zn and Pn entries.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [AArch64][SVE 19/32] Refactor address-printing code
@ 2016-09-22  1:25 sergiodj+buildbot
  2016-09-22  6:12 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-09-22  1:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 01dbfe4c0e2b832c6b1076e8d373b162e2faa376 ***

Author: Richard Sandiford <richard.sandiford@arm.com>
Branch: master
Commit: 01dbfe4c0e2b832c6b1076e8d373b162e2faa376

[AArch64][SVE 19/32] Refactor address-printing code

SVE adds addresses in which the base or offset are vector registers.
The addresses otherwise have the same kind of form as normal AArch64
addresses, including things like SXTW with or without a shift, UXTW
with or without a shift, and LSL.

This patch therefore refactors the address-printing code so that it
can cope with both scalar and vector registers.

opcodes/
	* aarch64-opc.c (get_offset_int_reg_name): New function.
	(print_immediate_offset_address): Likewise.
	(print_register_offset_address): Take the base and offset
	registers as parameters.
	(aarch64_print_operand): Update caller accordingly.  Use
	print_immediate_offset_address.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [AArch64][SVE 18/32] Tidy definition of aarch64-opc.c:int_reg
@ 2016-09-22  0:34 sergiodj+buildbot
  2016-09-22  5:25 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-09-22  0:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 72e9f31937f063ed6f5991a2b8c00068fa2dc8fc ***

Author: Richard Sandiford <richard.sandiford@arm.com>
Branch: master
Commit: 72e9f31937f063ed6f5991a2b8c00068fa2dc8fc

[AArch64][SVE 18/32] Tidy definition of aarch64-opc.c:int_reg

Use a macro to define 31 regular registers followed by a supplied
value for 0b11111.  The SVE code will also use this for vector base
and offset registers.

opcodes/
	* aarch64-opc.c (BANK): New macro.
	(R32, R64): Take a register number as argument
	(int_reg): Use BANK.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [AArch64][SVE 17/32] Add a prefix parameter to print_register_list
@ 2016-09-21 23:40 sergiodj+buildbot
  2016-09-22  3:55 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-09-21 23:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8a7f0c1b5ae35d041886855ac7ca9b9533e8788a ***

Author: Richard Sandiford <richard.sandiford@arm.com>
Branch: master
Commit: 8a7f0c1b5ae35d041886855ac7ca9b9533e8788a

[AArch64][SVE 17/32] Add a prefix parameter to print_register_list

This patch generalises the interface to print_register_list so
that it can print register lists involving SVE z registers as
well as AdvSIMD v ones.

opcodes/
	* aarch64-opc.c (print_register_list): Add a prefix parameter.
	(aarch64_print_operand): Update accordingly.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [AArch64][SVE 16/32] Use specific insert/extract methods for fpimm
@ 2016-09-21 23:35 sergiodj+buildbot
  2016-09-22  2:04 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-09-21 23:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT aa2aa4c69429444836821a92cb99396d02dcb996 ***

Author: Richard Sandiford <richard.sandiford@arm.com>
Branch: master
Commit: aa2aa4c69429444836821a92cb99396d02dcb996

[AArch64][SVE 16/32] Use specific insert/extract methods for fpimm

FPIMM used the normal "imm" insert/extract methods, with a specific
test for FPIMM in the extract method.  SVE needs to use the same
extractors, so rather than add extra checks for specific operand types,
it seemed cleaner to use a separate insert/extract method.

opcodes/
	* aarch64-tbl.h (AARCH64_OPERNADS): Use fpimm rather than imm
	for FPIMM.
	* aarch64-asm.h (ins_fpimm): New inserter.
	* aarch64-asm.c (aarch64_ins_fpimm): New function.
	* aarch64-asm-2.c: Regenerate.
	* aarch64-dis.h (ext_fpimm): New extractor.
	* aarch64-dis.c (aarch64_ext_imm): Remove fpimm test.
	(aarch64_ext_fpimm): New function.
	* aarch64-dis-2.c: Regenerate.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [AArch64][SVE 02/32] Avoid hard-coded limit in indented_print
@ 2016-09-21 19:48 sergiodj+buildbot
  2016-09-21 19:49 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-09-21 19:48 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bd11d5d83775e6d05c8e49f2233fb1cf883ff5b4 ***

Author: Richard Sandiford <richard.sandiford@arm.com>
Branch: master
Commit: bd11d5d83775e6d05c8e49f2233fb1cf883ff5b4

[AArch64][SVE 02/32] Avoid hard-coded limit in indented_print

The maximum indentation needed by aarch64-gen.c grows as more
instructions are added to aarch64-tbl.h.  Rather than having to
increase the indentation limit to a higher value, it seemed better
to replace it with "%*s".

opcodes/
	* aarch64-gen.c (indented_print): Avoid hard-coded indentation limit.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Avoid -Wduplicated-cond warnings in gdb/python
@ 2016-09-20 21:40 sergiodj+buildbot
  2016-09-21 12:29 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-09-20 21:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 12c58cd4dc805cbac97a6d93c971c2496313dce4 ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 12c58cd4dc805cbac97a6d93c971c2496313dce4

Avoid -Wduplicated-cond warnings in gdb/python

I tried building gdb with -Wduplicated-cond.  This patch fixes the
simpler issue that was found.

In Python 3, "int" and "long" are synonyms, so code like:

      else if (PyLong_Check (obj))
...
      else if (PyInt_Check (obj))

.... will trigger this warning.  The fix is to conditionalize the
PyInt_Check branches on Python 2.

Tested by rebuilding, with both version of Python, on x86-64 Fedora 24.

2016-09-20  Tom Tromey  <tom@tromey.com>

	* python/py-value.c (convert_value_from_python): Make PyInt_Check
	conditional on Python 2.
	* python/py-arch.c (archpy_disassemble): Make PyInt_Check
	conditional on Python 2.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] bfd: allow negative offsets to _GLOBAL_OFFSET_TABLE_ in elf64 SPARC
@ 2016-09-19 23:22 sergiodj+buildbot
  2016-09-20  0:43 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-09-19 23:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b19753ce31da347605dfa903c6fd2158e2444f0d ***

Author: Jose E. Marchesi <jose.marchesi@oracle.com>
Branch: master
Commit: b19753ce31da347605dfa903c6fd2158e2444f0d

bfd: allow negative offsets to _GLOBAL_OFFSET_TABLE_ in elf64 SPARC

The code compiled with the -fpic model in SPARC uses 13-bit signed
immediate PC-relative loads to fetch entries from the GOT table.  In
theory this would allow using a GOT table (.got section) containing up
to 1024 entries in elf32 or 512 entries in elf64.

However, in elf64 sparc GNU targets _GLOBAL_OFFSET_TABLE_ is always
placed at the beginning of the .got section, making it impossible to use
negative offsets.  This limits the usage of -fpic to GOT tables
containing a maximum of 257 entries in elf64.

This patch activates an optimization that is already used in sparc-elf32
also in sparc-elf64, that sets _GLOBAL_OFFSET_TABLE_ to point 0x1000
into the .got section if the section size is bigger than 0x1000.

2016-09-19  Jose E. Marchesi  <jose.marchesi@oracle.com>

	* elfxx-sparc.c (_bfd_sparc_elf_size_dynamic_sections): Allow
	negative offsets to _GLOBAL_OFFSET_TABLE_ if the .got section is
	bigger than 0x1000 bytes.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Consolidate target_mourn_inferior between GDB and gdbserver
@ 2016-09-19 16:45 sergiodj+buildbot
  2016-09-19 17:15 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-09-19 16:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bc1e6c81d5b77d78282c47f6fd7f697e564a6eb6 ***

Author: Sergio Durigan Junior <sergiodj@redhat.com>
Branch: master
Commit: bc1e6c81d5b77d78282c47f6fd7f697e564a6eb6

Consolidate target_mourn_inferior between GDB and gdbserver

This patch consolidates the API of target_mourn_inferior between GDB
and gdbserver, in my continuing efforts to make sharing the
fork_inferior function possible between both.

GDB's version of the function did not care about the inferior's ptid
being mourned, but gdbserver's needed to know this information.  Since
it actually makes sense to pass the ptid as an argument, instead of
depending on a global value directly (which GDB's version did), I
decided to make the generic API to accept it.  I then went on and
extended all calls being made on GDB to include a ptid argument (which
ended up being inferior_ptid most of the times, anyway), and now we
have a more sane interface.

On GDB's side, after talking to Pedro a bit about it, we decided that
just an assertion to make sure that the ptid being passed is equal to
inferior_ptid would be enough for now, on the GDB side.  We can remove
the assertion and perform more operations later if we ever pass
anything different than inferior_ptid.

Regression tested on our BuildBot, everything OK.

I'd appreciate a special look at gdb/windows-nat.c's modification
because I wasn't really sure what to do there.  It seemed to me that
maybe I should build a ptid out of the process information there, but
then I am almost sure the assertion on GDB's side would trigger.

gdb/ChangeLog:
2016-09-19  Sergio Durigan Junior  <sergiodj@redhat.com>

	* darwin-nat.c (darwin_kill_inferior): Adjusting call to
	target_mourn_inferior to include ptid_t argument.
	* fork-child.c (startup_inferior): Likewise.
	* gnu-nat.c (gnu_kill_inferior): Likewise.
	* inf-ptrace.c (inf_ptrace_kill): Likewise.
	* infrun.c (handle_inferior_event_1): Likewise.
	* linux-nat.c (linux_nat_attach): Likewise.
	(linux_nat_kill): Likewise.
	* nto-procfs.c (interrupt_query): Likewise.
	(procfs_interrupt): Likewise.
	(procfs_kill_inferior): Likewise.
	* procfs.c (procfs_kill_inferior): Likewise.
	* record.c (record_mourn_inferior): Likewise.
	* remote-sim.c (gdbsim_kill): Likewise.
	* remote.c (remote_detach_1): Likewise.
	(remote_kill): Likewise.
	* target.c (target_mourn_inferior): Change declaration to accept
	new ptid_t argument; use gdb_assert on it.
	* target.h (target_mourn_inferior): Move function prototype from
	here...
	* target/target.h (target_mourn_inferior): ... to here.  Adjust it
	to accept new ptid_t argument.
	* windows-nat.c (get_windows_debug_event): Adjusting call to
	target_mourn_inferior to include ptid_t argument.

gdb/gdbserver/ChangeLog:
2016-09-19  Sergio Durigan Junior  <sergiodj@redhat.com>

	* server.c (start_inferior): Call target_mourn_inferior instead of
	mourn_inferior; pass ptid_t argument to it.
	(resume): Likewise.
	(handle_target_event): Likewise.
	* target.c (target_mourn_inferior): New function.
	* target.h (mourn_inferior): Delete macro.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] linux-nat: Add function lwp_is_stepping
@ 2016-09-17  0:28 sergiodj+buildbot
  2016-09-17 16:39 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-09-17  0:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0e00e962c57138f0dd8c261cbd6918782deec3c4 ***

Author: Andreas Arnez <arnez@linux.vnet.ibm.com>
Branch: master
Commit: 0e00e962c57138f0dd8c261cbd6918782deec3c4

linux-nat: Add function lwp_is_stepping

Add the function lwp_is_stepping which indicates whether the given LWP
is currently single-stepping.  This is a common interface, usable from
native GDB as well as from gdbserver.

gdb/gdbserver/ChangeLog:

	* linux-low.c (lwp_is_stepping): New function.

gdb/ChangeLog:

	* nat/linux-nat.h (lwp_is_stepping): New declaration.
	* linux-nat.c (lwp_is_stepping): New function.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] S390: Enable "maint set show-debug-regs"
@ 2016-09-16 23:32 sergiodj+buildbot
  2016-09-17  4:19 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-09-16 23:32 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 169fe0df159c04cd7344d24cc6b1268bd219f830 ***

Author: Andreas Arnez <arnez@linux.vnet.ibm.com>
Branch: master
Commit: 169fe0df159c04cd7344d24cc6b1268bd219f830

S390: Enable "maint set show-debug-regs"

Implement a new function for dumping the S390 "debug
registers" (actually, the PER info) and invoke it at appropriate places.
Respect the variable show_debug_regs and make it settable by the user.

gdb/ChangeLog:

	* s390-linux-nat.c (gdbcmd.h): New include.
	(s390_show_debug_regs): New function.
	(s390_stopped_by_watchpoint): Call it, if show_debug_regs is set.
	(s390_prepare_to_resume): Likewise.
	(_initialize_s390_nat): Register the command "maint set
	show-debug-regs".


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] S390: Multi-inferior watchpoint support
@ 2016-09-16 23:12 sergiodj+buildbot
  2016-09-17  1:20 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-09-16 23:12 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 373c3dad74da78c46bc1fe4280a26d07e5b54cdd ***

Author: Andreas Arnez <arnez@linux.vnet.ibm.com>
Branch: master
Commit: 373c3dad74da78c46bc1fe4280a26d07e5b54cdd

S390: Multi-inferior watchpoint support

Support different sets of watchpoints in multiple inferiors.

gdb/ChangeLog:

	* s390-linux-nat.c (watch_areas): Remove variable.  Replace by a
	member of...
	(struct s390_debug_reg_state): ...this.  New struct.
	(struct s390_process_info): New struct.
	(s390_process_list): New variable.
	(s390_find_process_pid, s390_add_process, s390_process_info_get)
	(s390_get_debug_reg_state): New functions.
	(s390_stopped_by_watchpoint): Now access the watch_areas VEC via
	s390_get_debug_reg_state.
	(s390_prepare_to_resume): Likewise.
	(s390_insert_watchpoint): Likewise.
	(s390_remove_watchpoint): Likewise.
	(s390_forget_process, s390_linux_new_fork): New linux_nat target
	methods.
	(_initialize_s390_nat): Register them.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] testsuite: Fix false FAIL in gdb.cp/casts.exp
@ 2016-09-16 20:49 sergiodj+buildbot
  2016-09-16 21:05 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-09-16 20:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d41a5c096ec613f7df33d5d5ea4c0e512ac1e87a ***

Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Branch: master
Commit: d41a5c096ec613f7df33d5d5ea4c0e512ac1e87a

testsuite: Fix false FAIL in gdb.cp/casts.exp

gcc-6.2.1-1.fc26.x86_64

gdb compile failed, /home/jkratoch/redhat/gdb-clean/gdb/testsuite/gdb.cp/casts.cc:40:10: error: expected primary-expression before 'int'
 decltype(int x)
          ^~~
/home/jkratoch/redhat/gdb-clean/gdb/testsuite/gdb.cp/casts.cc:40:10: error: expected ')' before 'int'
/home/jkratoch/redhat/gdb-clean/gdb/testsuite/gdb.cp/casts.cc:40:1: error: expected unqualified-id before 'decltype'
 decltype(int x)
 ^~~~~~~~
/home/jkratoch/redhat/gdb-clean/gdb/testsuite/gdb.cp/casts.cc: In function 'int main(int, char**)':
/home/jkratoch/redhat/gdb-clean/gdb/testsuite/gdb.cp/casts.cc:59:14: error: expected primary-expression before 'decltype'
   double y = decltype(2);
              ^~~~~~~~

'decltype' is a registered keyword since C++11 which is now a default for GCC.

On Thu, 15 Sep 2016 14:06:56 +0200, Pedro Alves wrote:

Seems to be exercising the FLAG_SHADOW bits:

...
    {"__typeof__", TYPEOF, OP_TYPEOF, 0 },
    {"__typeof", TYPEOF, OP_TYPEOF, 0 },
    {"typeof", TYPEOF, OP_TYPEOF, FLAG_SHADOW },
    {"__decltype", DECLTYPE, OP_DECLTYPE, FLAG_CXX },
    {"decltype", DECLTYPE, OP_DECLTYPE, FLAG_CXX | FLAG_SHADOW },
...

/* This is used to associate some attributes with a token.  */

enum token_flag
{
...
  /* If this bit is set, the token is conditional: if there is a
     symbol of the same name, then the token is a symbol; otherwise,
     the token is a keyword.  */

  FLAG_SHADOW = 2
};

So perhaps a better fix is to move that particular test to a
separate testcase that force-compiles with -std=c++03.

gdb/testsuite/ChangeLog
2016-09-16  Jan Kratochvil  <jan.kratochvil@redhat.com>

	* gdb.cp/casts.cc (decltype): Move it ...
	(main): ... with its call to ...
	* gdb.cp/casts03.cc: ... a new file.
	* gdb.cp/casts.exp: Add new file casts03.cc, move decltype test to it.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Modify POWER9 support to match final ISA 3.0 documentation.
@ 2016-09-15 21:47 sergiodj+buildbot
  2016-09-15 22:17 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-09-15 21:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fd486b633e87f8ab2977592d56a6d98168814e2e ***

Author: Peter Bergner <bergner@vnet.ibm.com>
Branch: master
Commit: fd486b633e87f8ab2977592d56a6d98168814e2e

Modify POWER9 support to match final ISA 3.0 documentation.

opcodes/
	* ppc-opc.c (powerpc_opcodes) <slbiag>: New mnemonic.
	<addex., brd, brh, brw, lwzmx, nandxor, rldixor, setbool,
	xor3>: Delete mnemonics.
	<cp_abort>: Rename mnemonic from ...
	<cpabort>: ...to this.
	<setb>: Change to a X form instruction.
	<sync>: Change to 1 operand form.
	<copy>: Delete mnemonic.
	<copy_first>: Rename mnemonic from ...
	<copy>: ...to this.
	<paste, paste.>: Delete mnemonics.
	<paste_last>: Rename mnemonic from ...
	<paste.>: ...to this.

gas/
	* testsuite/gas/ppc/power9.d <slbiag, cpabort> New tests.
	<addex., brd, brh, brw, lwzmx, nandxor, rldixor, setbool,
	xor3, cp_abort, copy_first, paste, paste_last, sync>: Remove tests.
	<copy, paste.>: Update tests.
	* testsuite/gas/ppc/power9.s: Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix ld --gc-section segfault with ARMv8-M entry function in absolute section
@ 2016-09-15  4:45 sergiodj+buildbot
  2016-09-15 12:25 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-09-15  4:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4f90d84b2f2995829d6af475077598d45ef1d127 ***

Author: Thomas Preud'homme <thomas.preudhomme@arm.com>
Branch: master
Commit: 4f90d84b2f2995829d6af475077598d45ef1d127

Fix ld --gc-section segfault with ARMv8-M entry function in absolute section

bfd/
2016-09-14  Thomas Preud'homme  <thomas.preudhomme@arm.com>

	* elf32-arm.c (elf32_arm_gc_mark_extra_sections): Only mark section
	not already marked.

ld/
2016-09-14  Thomas Preud'homme  <thomas.preudhomme@arm.com>

	* testsuite/ld-arm/cmse-veneers.s: Add a test for ARMv8-M Security
	Extensions entry functions in absolute section.
	* testsuite/ld-arm/cmse-veneers.rd: Adapt expected output accordingly.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix for gdb.server/non-existing-program.exp test case
@ 2016-09-14 13:01 sergiodj+buildbot
  2016-09-14 14:41 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-09-14 13:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1d8cb77dff14d44b1e3b670442438da496f99c6e ***

Author: Carl E. Love <carll@oc4738070240.ibm.com>
Branch: master
Commit: 1d8cb77dff14d44b1e3b670442438da496f99c6e

Fix for gdb.server/non-existing-program.exp test case

The last commit was supposed to have the reference to ptrace () removed.
The patch didn't get updated correctly before the commit.  This commit
fixes the comment as requested

gdbserver/ChangeLog

	2016-09-06  Carl Love  <cel@us.ibm.com>

	* server.c (start_inferior):  Fixed comment, requested comment change
	didn't get updated correctly.  Removed reference to ptrace () call as
 	it is only true on Linux systems.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix false FAIL on gdb.base/stap-probe.exp, due to ICF optimization
@ 2016-09-12 17:26 sergiodj+buildbot
  2016-09-12 17:35 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-09-12 17:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2c29df25b7c2ff006b45afd80ee6dd734ebbd47c ***

Author: Sergio Durigan Junior <sergiodj@redhat.com>
Branch: master
Commit: 2c29df25b7c2ff006b45afd80ee6dd734ebbd47c

Fix false FAIL on gdb.base/stap-probe.exp, due to ICF optimization

GCC 6's ICF optimization pass is making the declaration of 'm1' and
'm2', on gdb.base/stap-probe.c, to be unified.  However, this leads to
only one instance of the probe 'two' being created, which causes a
failure on the testsuite (which expects a multi-location breakpoint to
be inserted on the probe).

This patch fixes this failure by declaring a dummy variable on 'm1',
and using it as an argument to m1's version of probe 'two'.  Since we
do not care about the contents of the functions nor about the
arguments of each probe 'two', this is OK.

gdb/testsuite/ChangeLog:
2016-09-11  Sergio Durigan Junior  <sergiodj@redhat.com>
	    Jan Kratochvil  <jan.kratochvil@redhat.com>

	* gdb.base/stap-probe.c (m1): New variable 'dummy', necessary to
	make m1's definition to be different from m2's.  Use 'dummy' as an
	argument for probe 'two'.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Pass HWCAP to ifunc resolver
@ 2016-09-10 23:25 sergiodj+buildbot
  2016-09-12  4:56 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-09-10 23:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e1b2624a08fae1f669d879946d5041945b4dc248 ***

Author: Andreas Arnez <arnez@linux.vnet.ibm.com>
Branch: master
Commit: e1b2624a08fae1f669d879946d5041945b4dc248

Pass HWCAP to ifunc resolver

On various GNU Elf architectures, including AArch64, ARM, s390/s390x,
ppc32/64, and sparc32/64, the dynamic loader passes HWCAP as a parameter
to each ifunc resolver.  Currently there is an open glibc Bugzilla that
requests this to be generalized to all architectures:

  https://sourceware.org/bugzilla/show_bug.cgi?id=19766

And various ifunc resolvers already rely on receiving HWCAP.  Currently
GDB always calls an ifunc resolver without any arguments; thus the
resolver may receive garbage, and based on that, the resolver may decide
to return a function that is not suited for the given platform.

This patch always passes HWCAP to ifunc resolvers, even on systems where
the dynamic loader currently behaves otherwise.  The rationale is
that (1) the dynamic loader may get adjusted on those systems as well in
the future; (2) passing an unused argument should not cause a problem
with existing resolvers; and (3) the logic is much simpler without such
a distinction.

gdb/ChangeLog:

	* elfread.c (auxv.h): New include.
	(elf_gnu_ifunc_resolve_addr): Pass HWCAP to ifunc resolver.

gdb/testsuite/ChangeLog:

	* gdb.base/gnu-ifunc-lib.c (resolver_hwcap): New external
	variable declaration.
	(gnu_ifunc): Add parameter hwcap.  Store it in resolver_hwcap.
	* gdb.base/gnu-ifunc.c (resolver_hwcap): New global variable.
	* gdb.base/gnu-ifunc.exp: Add test to verify that the resolver
	received HWCAP as its argument.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Introduce make_cleanup_restore_current_ui
@ 2016-09-07  5:56 sergiodj+buildbot
  2016-09-07 18:58 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-09-07  5:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a025b477cc466112af0b120c5f2bf5d62a62017e ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: a025b477cc466112af0b120c5f2bf5d62a62017e

Introduce make_cleanup_restore_current_ui

Just a tidy, no functional changes.

gdb/ChangeLog:
2016-09-06  Pedro Alves  <palves@redhat.com>

	* event-top.c (restore_ui_cleanup): Now static.
	(make_cleanup_restore_current_ui): New function.
	(switch_thru_all_uis_init): Use it.
	* infcall.c (call_thread_fsm_should_stop): Use it.
	* infrun.c (fetch_inferior_event): Use it.
	* top.c (new_ui_command): Use it.
	* top.h (restore_ui_cleanup): Delete declaration.
	(make_cleanup_restore_current_ui): New declaration.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Add gdbarch callback to provide formats for debug info float types
@ 2016-09-07  0:07 sergiodj+buildbot
  2016-09-07 13:30 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-09-07  0:07 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9b790ce7227fa346d08a41462119e9a3e93f5e80 ***

Author: Ulrich Weigand <ulrich.weigand@de.ibm.com>
Branch: master
Commit: 9b790ce7227fa346d08a41462119e9a3e93f5e80

Add gdbarch callback to provide formats for debug info float types

At this point, all TYPE_CODE_FLT types carry their floating-point format,
except for those creating from reading DWARF or stabs debug info.  Those
will be addressed by this commit.

The main issue here is that we actually have to determine which floating-
point format to use.  Currently, we only have the type length as input
to this decision.  In the future, we may hopefully get --at least in
DWARF-- additional information to help disambiguate multiple different
formats of the same length.  For now, we can still look at the type name
as a hint.

This decision logic is encapsulated in a gdbarch callback to allow
platform-specific overrides.  The default implementation use the same
logic (compare type length against the various gdbarch_..._bit sizes)
that is currently implemented in floatformat_from_length.

With this commit, all platforms still use the default logic, so there
should be no actual change in behavior.  A follow-on commit will add
support for __float128 on Intel and Power.

Once dwarf2read.c and stabsread.c make use of the new callback to
determine floating-point formats, we're now sure every TYPE_CODE_FLT
type will always carry its format.  The commit therefore adds asserts
to verify_floatformat to ensure new code will continue to always
provide formats, and removes the code in floatformat_from_type that
used to handle types with a NULL TYPE_FLOATFORMAT.

gdb/ChangeLog:

	* gdbarch.sh (floatformat_for_type): New gdbarch callback.
	* gdbarch.h, gdbarch.c: Re-generate.
	* arch-utils.h (default_floatformat_for_type): New prototype.
	* arch-utils.c (default_floatformat_for_type): New function.

	* doublest.c (floatformat_from_length): Remove.
	(floatformat_from_type): Assume TYPE_FLOATFORMAT is non-NULL.
	* gdbtypes.c (verify_floatformat): Require non-NULL format.

	* dwarf2read.c (dwarf2_init_float_type): New function.
	(read_base_type): Use it.
	* stabsread.c (dbx_init_float_type): New function.
	(read_sun_floating_type): Use it.
	(read_range_type): Likewise.

Signed-off-by: Ulrich Weigand <ulrich.weigand@de.ibm.com>


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Remove obsolete TYPE_FLAG_... values
@ 2016-09-06 22:01 sergiodj+buildbot
  2016-09-07  0:09 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-09-06 22:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a9ff5f12cff6cd06f74ecf387ac5468984c94c6f ***

Author: Ulrich Weigand <ulrich.weigand@de.ibm.com>
Branch: master
Commit: a9ff5f12cff6cd06f74ecf387ac5468984c94c6f

Remove obsolete TYPE_FLAG_... values

Now that init_type no longer takes a FLAGS argument, there is no user of
the TYPE_FLAGS_... enum values left.  This commit removes them (and all
references to them in comments as well).

This is mostly a no-op, except for a change to the Python type printer,
which attempted to use them before.  (As best as I can tell, this wasn't
really needed anyway, since it was only used to pretty-print type
*instance* flags, which only use the instance flags.)

gdb/ChangeLog:

	* gdbtypes.h (enum type_flag_value): Remove.
	Remove references to TYPE_FLAG_... in comments throughout.
	* gdbtypes.c (recursive_dump_type): Do not print TYPE_FLAG_...
	flags, print the corresponding TYPE_... access macro names.
	Remove references to TYPE_FLAG_... in comments throughout.
	* infcall.c: Remove references to TYPE_FLAG_... in comments.
	* valprint.c: Likewise.
	* gdb-gdb.py (class TypeFlag): No longer consider TYPE_FLAG_...
	values, only TYPE_INSTANCE_FLAG_... values.
	(class TypeFlagsPrinter): Likewise.

gdb/testsuite/ChangeLog:

	* gdb.cp/hang.exp: Remove reference to TYPE_FLAG_STUB in comment.

Signed-off-by: Ulrich Weigand <ulrich.weigand@de.ibm.com>


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Handle DW_OP_form_tls_address
@ 2016-09-03 12:46 sergiodj+buildbot
  2016-09-04 19:46 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-09-03 12:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4aa4e28bdcf5f0d733def62b542fea11d5f219d5 ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 4aa4e28bdcf5f0d733def62b542fea11d5f219d5

Handle DW_OP_form_tls_address

Currently gdb supports DW_OP_GNU_push_tls_address, but not
DW_OP_form_tls_address.  I think it would be better if the toolchain
as a whole moved to using the standard opcode, and the prerequisite to
this is getting gdb to recognize it.

GCC can sometimes emit DW_OP_form_tls_address for emultls targets.  As
far as I know, nobody has ever tried this with gdb (since it wouldn't
work at all).

I don't think there's a major drawback to using a single opcode for
all targets, because computing the location of a thread-local is
already target specific.

This is PR gdb/11616.

I don't know how to write a test case for this; though it's worth
noting that there aren't explicit tests for DW_OP_GNU_push_tls_address
either -- and if I change GCC, these paths will be tested to the same
extent they are now.

2016-09-02  Tom Tromey  <tom@tromey.com>

	PR gdb/11616:
	* dwarf2read.c (decode_locdesc): Handle DW_OP_form_tls_address.
	* dwarf2loc.c (dwarf2_compile_expr_to_ax): Handle
	DW_OP_form_tls_address.
	(locexpr_describe_location_piece): Likewise.
	* dwarf2expr.h (struct dwarf_expr_context_funcs): Update comment.
	* dwarf2expr.c (execute_stack_op): Handle DW_OP_form_tls_address.
	(ctx_no_get_tls_address): Mention DW_OP_form_tls_address.
	* compile/compile-loc2c.c (struct insn_info): Update comment.
	(compute_stack_depth_worker): Handle DW_OP_form_tls_address.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Use target_continue{, _no_signal} instead of target_resume
@ 2016-09-02  9:02 sergiodj+buildbot
  2016-09-02  9:07 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-09-02  9:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 049a857091cff98371b5688140832a3cf767153c ***

Author: Sergio Durigan Junior <sergiodj@redhat.com>
Branch: master
Commit: 049a857091cff98371b5688140832a3cf767153c

Use target_continue{,_no_signal} instead of target_resume

This commit implements a new function, target_continue, on top of the
target_resume function.  Then, it replaces all calls to target_resume
by calls to target_continue or to the already existing
target_continue_no_signal.

This is one of the (many) necessary steps needed to consolidate the
target interface between GDB and gdbserver.  In particular, I am
interested in the impact this change will have on the unification of
the fork_inferior function (which I have been working on).

Tested on the BuildBot, no regressions introduced.

gdb/gdbserver/ChangeLog:
2016-09-31  Sergio Durigan Junior  <sergiodj@redhat.com>

	* server.c (start_inferior): New variable 'ptid'.  Replace calls
	to the_target->resume by target_continue{,_no_signal}, depending
	on the case.
	* target.c (target_stop_and_wait): Call target_continue_no_signal
	instead of the_target->resume.
	(target_continue): New function.

gdb/ChangeLog:
2016-09-31  Sergio Durigan Junior  <sergiodj@redhat.com>

	* fork-child.c (startup_inferior): Replace calls to target_resume
	by target_continue{,_no_signal}, depending on the case.
	* linux-nat.c (cleanup_target_stop): Call
	target_continue_no_signal instead of target_resume.
	* procfs.c (procfs_wait): Likewise.
	* target.c (target_continue): New function.
	* target/target.h (target_continue): New prototype.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] PowerPC64, correct grouping of stubs for ld.bfd
@ 2016-08-31 19:13 sergiodj+buildbot
  2016-08-31 19:31 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-08-31 19:13 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 09f92717713cfc7595b29caa3f017f88e7f7e279 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 09f92717713cfc7595b29caa3f017f88e7f7e279

PowerPC64, correct grouping of stubs for ld.bfd

Like 57f6d32d, this patch ensures that sections containing external
conditional branches limit the group size.

	* elf64-ppc.c (group_sections): Delete stub14_group_size.  Instead,
	track max group size with a new "group_size" var that is reduced
	by a factor of 1024 from the 24-bit branch size whenever a 14-bit
	branch is seen.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fixed issue with NULL pointer access on header var.
@ 2016-08-31  5:42 sergiodj+buildbot
  2016-08-31 10:10 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-08-31  5:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7763838e991e4d17a24c4214db5144eefd515543 ***

Author: Cupertino Miranda <cmiranda@synopsys.com>
Branch: master
Commit: 7763838e991e4d17a24c4214db5144eefd515543

Fixed issue with NULL pointer access on header var.

Variable "header" in function is set conditionally, but was accessed without
verifying if pointer was NULL.

opcodes/ChangeLog:

    Cupertino Miranda  <cmiranda@synopsys.com>
	* opcodes/arc-dis.c (print_insn_arc): Changed.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix commit 980aa3e6
@ 2016-08-27 12:09 sergiodj+buildbot
  2016-08-29 14:20 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-08-27 12:09 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8a9e8e72fe88095043d16f8a56b5a1e150ee288b ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 8a9e8e72fe88095043d16f8a56b5a1e150ee288b

Fix commit 980aa3e6

Commit 980aa3e6 was supposed to cure dyn_reloc counting problems, but
did the opposite.  For PIC we count two types of dyn_reloc, those on
pc-relative relocs, and the total.  If a sym needs pc-relative dyn
relocs then all the relocs are dynamic.  If not, then only those that
are must_be_dyn_reloc are dynamic.

	PR 20519
	* elf64-ppc.c (pc_dynrelocs): New function.
	(ppc64_elf_relocate_section): Use it and must_be_dyn_reloc to
	handle pic dynamic relocs.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Add missing ARMv8-M special registers
@ 2016-08-26 17:28 sergiodj+buildbot
  2016-08-27  0:26 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-08-26 17:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1a336194b70b712074a3f5479a01cc221003a152 ***

Author: Thomas Preud'homme <thomas.preudhomme@arm.com>
Branch: master
Commit: 1a336194b70b712074a3f5479a01cc221003a152

Add missing ARMv8-M special registers

2016-08-26  Thomas Preud'homme  <thomas.preudhomme@arm.com>

gas/
	* config/tc-arm.c (v7m_psrs): Add MSPLIM, PSPLIM, MSPLIM_NS,
	PSPLIM_NS, PRIMASK_NS, BASEPRI_NS, FAULTMASK_NS, CONTROL_NS, SP_NS and
	their lowecase counterpart special registers.  Write register
	identifier in hex.
	* testsuite/gas/arm/archv8m-cmse-msr.s: Reorganize tests per
	operation, special register and then case.  Use different register for
	each operation.  Add tests for new special registers.
	* testsuite/gas/arm/archv8m-cmse-msr-base.d: Adapt expected result
	accordingly.
	* testsuite/gas/arm/archv8m-cmse-msr-main.d: Likewise.
	* testsuite/gas/arm/archv8m-main-dsp-4.d: Likewise.

opcodes/
	* arm-dis.c (psr_name): Use hex as case labels.  Add detection for
	MSPLIM, PSPLIM, MSPLIM_NS, PSPLIM_NS, PRIMASK_NS, BASEPRI_NS,
	FAULTMASK_NS, CONTROL_NS and SP_NS special registers.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Dynamic TLS GOT entries would not be relocated.
@ 2016-08-26 17:24 sergiodj+buildbot
  2016-08-26 20:03 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-08-26 17:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 980aa3e6dfeb0f018915f65be4b2987667f31fe9 ***

Author: Cupertino Miranda <cmiranda@synopsys.com>
Branch: master
Commit: 980aa3e6dfeb0f018915f65be4b2987667f31fe9

Dynamic TLS GOT entries would not be relocated.

Forgot to set should_relocate to TRUE in case of GOT and TLS relocations of
undefined symbols for shared libraries.
In dynamic libraries if symbol is not known the instruction relocation would
not be resolved to point to the respective .got entry.
A test was created to detect similar future mistakes.

bfd/ChangeLog:

Cupertino Miranda  <cmiranda@synopsys.com>

	* elf32-arc.c (elf_arc_relocate_section): Changed. Set should_relocate
	to TRUE for GOT and TLS relocs.

ld/ChangeLog:

Cupertino Miranda  <cmiranda@synopsys.com>

	* ld/testsuite/ld-arc/tls_gd-01.s: Added a testcase for this patch.
	* ld/testsuite/ld-arc/tls_gd-01.d: Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fixed -init, -fini linker options.
@ 2016-08-26 16:28 sergiodj+buildbot
  2016-08-26 18:11 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-08-26 16:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 65b94e90977efe3235381708f5a3e0d541026d88 ***

Author: Cupertino Miranda <cmiranda@synopsys.com>
Branch: master
Commit: 65b94e90977efe3235381708f5a3e0d541026d88

Fixed -init, -fini linker options.

ARC was overloading this options by forcing DT_INIT AND DT_FINI
to always point to _init and _fini, respectively.

bfd/ChangeLog:

Cupertino Miranda  <cmiranda@synospsys.com>

	* elf32-arc.c (elf_arc_finish_dynamic_sections): Changed.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] S390: Add support for core dump NOTE sections
@ 2016-08-26 12:23 sergiodj+buildbot
  2016-08-26 13:23 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-08-26 12:23 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e3e9290d6c7bc276ac6a15a9d5793a49dde92c41 ***

Author: Andreas Arnez <arnez@linux.vnet.ibm.com>
Branch: master
Commit: e3e9290d6c7bc276ac6a15a9d5793a49dde92c41

S390: Add support for core dump NOTE sections

This enhances the 32-bit and 64-bit s390 ELF backends with support for
reading and writing the core dump note sections NT_PRSTATUS and
NT_PRPSINFO.  Byte swapping is done as appropriate, such that core files
can now be processed correctly on non-s390 platforms.

bfd/ChangeLog:

	* elf32-s390.c (stdarg.h): New include.
	(elf_s390_grok_psinfo): New function.
	(elf_s390_write_core_note): New function.
	(elf_backend_grok_psinfo): Declare backend hook.
	(elf_backend_write_core_note): Likewise.
	* elf64-s390.c (stdarg.h): New include.
	(elf_s390_grok_prstatus): New function.
	(elf_s390_grok_psinfo): New function.
	(elf_s390_write_core_note): New function.
	(elf_backend_grok_prstatus): Declare backend hook.
	(elf_backend_grok_psinfo): Likewise.
	(elf_backend_write_core_note): Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] S390: Indentation fixes in elf32/64-s390.c
@ 2016-08-26 11:41 sergiodj+buildbot
  2016-08-26 12:35 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-08-26 11:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ceada89664de30158de12d3d8f7bd7880ff6af29 ***

Author: Andreas Arnez <arnez@linux.vnet.ibm.com>
Branch: master
Commit: ceada89664de30158de12d3d8f7bd7880ff6af29

S390: Indentation fixes in elf32/64-s390.c

Some indentation fixes in elf32-s390.c and elf64-s390.c.  Whitespace
changes only.

bfd/ChangeLog:

	* elf32-s390.c (allocate_dynrelocs): Fix indentation.
	(elf_s390_finish_ifunc_symbol): Likewise.
	(elf_s390_finish_dynamic_symbol): Likewise.
	(elf_s390_finish_dynamic_sections): Likewise.
	(elf_s390_grok_prstatus): Likewise.
	* elf64-s390.c (elf_s390_hash_table): Fix indentation.
	(elf_s390_finish_dynamic_symbol): Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] xtensa: Avoid designated inits, for C++ compliance
@ 2016-08-26 10:59 sergiodj+buildbot
  2016-08-26 11:23 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-08-26 10:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ae68ff9f280902d9cead28b90979e75dc046492e ***

Author: Andreas Arnez <arnez@linux.vnet.ibm.com>
Branch: master
Commit: ae68ff9f280902d9cead28b90979e75dc046492e

xtensa: Avoid designated inits, for C++ compliance

C++ does not officially support designators in initializer lists.  Thus
some compilers may issue errors when encountering them.  Modern versions
of GCC seem to allow them by default, as a GCC extension, even though
the GCC documentation explicitly states otherwise: "[...] This extension
is not implemented in GNU C++."  But some older GCC versions (like
4.4.7) did indeed emit an error instead, like this:

  .../gdb/xtensa-config.c:219: error: expected primary-expression before
			       . token

This patch removes the only such instance I've seen when building with
'--enable-targets=all'.

gdb/ChangeLog:

	* xtensa-tdep.h (XTENSA_GDBARCH_TDEP_INSTANTIATE): Replace
	designated initializer list by plain initializer list, for C++
	compliance.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Test case to detect recursive unwinding in Python-based unwinders.
@ 2016-08-25  7:58 sergiodj+buildbot
  2016-08-25  9:29 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-08-25  7:58 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bb1fe4acb8927fc4d451402f3f5fc245144c987e ***

Author: Kevin Buettner <kevinb@redhat.com>
Branch: master
Commit: bb1fe4acb8927fc4d451402f3f5fc245144c987e

Test case to detect recursive unwinding in Python-based unwinders.

This test case verifies that GDB will not attempt to invoke a python
unwinder recursively.

At the moment, the behavior exhibited by GDB looks like this:

    (gdb) source py-recurse-unwind.py
    Python script imported
    (gdb) b ccc
    Breakpoint 1 at 0x4004bd: file py-recurse-unwind.c, line 23.
    (gdb) run
    Starting program: py-recurse-unwind
    TestUnwinder: Recursion detected - returning early.
    TestUnwinder: Recursion detected - returning early.
    TestUnwinder: Recursion detected - returning early.
    TestUnwinder: Recursion detected - returning early.

    Breakpoint 1, ccc (arg=<unavailable>) at py-recurse-unwind.c:23
    23      }
    (gdb) bt
    #-1 ccc (arg=<unavailable>) at py-recurse-unwind.c:23
    Backtrace stopped: previous frame identical to this frame (corrupt stack?)

[I've shortened pathnames for easier reading.]

The desired / expected behavior looks like this:

    (gdb) source py-recurse-unwind.py
    Python script imported
    (gdb) b ccc
    Breakpoint 1 at 0x4004bd: file py-recurse-unwind.c, line 23.
    (gdb) run
    Starting program: py-recurse-unwind

    Breakpoint 1, ccc (arg=789) at py-recurse-unwind.c:23
    23      }
    (gdb) bt
    #0  ccc (arg=789) at py-recurse-unwind.c:23
    #1  0x00000000004004d5 in bbb (arg=456) at py-recurse-unwind.c:28
    #2  0x00000000004004ed in aaa (arg=123) at py-recurse-unwind.c:34
    #3  0x00000000004004fe in main () at py-recurse-unwind.c:40

Note that GDB's problems go well beyond the fact that it invokes the
unwinder recursively.  In the process it messes up some internal state
(the frame stash) leading to display of (only) the sentinel frame in
the backtrace.

gdb/testsuite/ChangeLog:

	* gdb.python/py-recurse-unwind.c: New file.
	* gdb.python/py-recurse-unwind.py: New file.
	* gdb.python/py-recurse-unwind.exp: New file.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Allow resetting an empty inferior-tty
@ 2016-08-24 20:24 sergiodj+buildbot
  2016-08-25  9:01 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-08-24 20:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0a1ddfa6b67201bb06f51fb47b56096e81bec5c0 ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: 0a1ddfa6b67201bb06f51fb47b56096e81bec5c0

Allow resetting an empty inferior-tty

This patch allows the user to set the inferior-tty to "empty", in order
to come back to the default behaviour of using the same tty as gdb is
using.

This is already supported in MI (and tested in gdb.mi/mi-basics.exp).

I added a new test, set-inferior-tty.exp, where I test only the setting
and unsetting of the parameter.  It would be nice to actually test that
the inferior output properly goes to the separate tty, but that will be
for another day.

gdb/ChangeLog:

	* infcmd.c (set_inferior_io_terminal): Set inferior terminal to
	NULL if terminal_name is an empty string.
	(_initialize_infcmd): Make the argument of "set inferior-tty"
	optional, mention it in the help doc.

gdb/doc/ChangeLog:

	* gdb.texinfo (Input/Output): Mention possibility to unset
	inferior-tty.

gdb/testsuite/ChangeLog:

	* gdb.base/set-inferior-tty.exp: New file.
	* gdb.base/set-inferior-tty.c: New file.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix for gdb.base/pc-fp.exp.
@ 2016-08-24 18:43 sergiodj+buildbot
  2016-08-25  8:57 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-08-24 18:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bdd78711b4c1ae26dbc8c2a64f28abec3486ae6c ***

Author: Carl E. Love <carll@oc4738070240.ibm.com>
Branch: master
Commit: bdd78711b4c1ae26dbc8c2a64f28abec3486ae6c

Fix for gdb.base/pc-fp.exp.

It is my understanding that GDB used to require each architecture to
define a Frame Pointer (fp).  However, this functionality was deprecated
some time ago so the call to setup the fp_reg was changed to deprecated
(set_gdbarch_deprecated_fp_regnum).  It should have been removed from the
Power code.

That said, the code "set_gdbarch_deprecated_fp_regnum
(gdbarch, PPC_R0_REGNUM + 1);" sets up register r1 as the frame pointer.
Register r1 is no longer used to hold the frame pointer on Power.  By
removing the fp definition for Power in GDB, it causes GDB to fall back
to the call get_frame_base_address (frame) which returns the correct value
depending on the specific senario but most of the time is the DWARF
canonical frame address.

gdb/ChangeLog

2016-08-24  Carl Love  <cel@us.ibm.com>

	* rs6000-tdep.c (rs6000_gdbarch_init): Remove call
        set_gdbarch_deprecated_fp_regnum() from initialization function.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix PR20494 - User input stops being echoed in CLI
@ 2016-08-23 22:53 sergiodj+buildbot
  2016-08-23 23:23 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-08-23 22:53 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d9de1fe3d5607f96491e8f16f474b9441cbec849 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: d9de1fe3d5607f96491e8f16f474b9441cbec849

Fix PR20494 - User input stops being echoed in CLI

This patch fixes a problem that problem triggers if you start an
inferior, e.g., with the "start" command, in a UI created with the
new-ui command, and then run a foreground execution command in the
main UI.  Once the program stops for the latter command, typing in the
main UI no longer echoes back to the user.

The problem revolves around this:

- gdb_has_a_terminal computes its result lazily, on first call.

  that is what saves gdb's initial main UI terminal state (the UI
  associated with stdin):

          our_terminal_info.ttystate = serial_get_tty_state (stdin_serial);

  This is the state that target_terminal_ours() restores.

- In this scenario, the gdb_has_a_terminal function happens to be
  first ever called from within the target_terminal_init call in
  startup_inferior:

      (top-gdb) bt
      #0  gdb_has_a_terminal () at src/gdb/inflow.c:157
      #1  0x000000000079db22 in child_terminal_init_with_pgrp () at src/gdb/inflow.c:217
       [...]
      #4  0x000000000065bacb in target_terminal_init () at src/gdb/target.c:456
      #5  0x00000000004676d2 in startup_inferior () at src/gdb/fork-child.c:531
       [...]
      #7  0x000000000046b168 in linux_nat_create_inferior () at src/gdb/linux-nat.c:1112
       [...]
      #9  0x00000000005f20c9 in start_command (args=0x0, from_tty=1) at src/gdb/infcmd.c:657

If the command to start the inferior is issued on the main UI, then
readline will have deprepped the terminal when we reach the above, and
the problem doesn't appear.

If however the command is issued on a non-main UI, then when we reach
that gdb_has_a_terminal call, the main UI's terminal state is still
set to whatever readline has sets it to in rl_prep_terminal, which
happens to have echo disabled.  Later, when the following synchronous
execution command finishes, we'll call target_terminal_ours to restore
gdb's the main UI's terminal settings, and that restores the terminal
state with echo disabled...

Conceptually, the fix is to move the gdb_has_a_terminal call earlier,
to someplace during GDB initialization, before readline/ncurses have
had a chance to change terminal settings.  Turns out that
"set_initial_gdb_ttystate" is exactly such a place.

I say conceptually, because the fix actually inlines the
gdb_has_a_terminal part that saves the terminal state in
set_initial_gdb_ttystate and then simplifies gdb_has_a_terminal, since
there's no point in making gdb_has_a_terminal do lazy computation.

gdb/ChangeLog:
2016-08-23  Pedro Alves  <palves@redhat.com>

	PR gdb/20494
	* inflow.c (our_terminal_info, initial_gdb_ttystate): Update
	comments.
	(enum gdb_has_a_terminal_flag_enum, gdb_has_a_terminal_flag):
	Delete.
	(set_initial_gdb_ttystate): Record our_terminal_info here too,
	instead of ...
	(gdb_has_a_terminal): ... here.  Reimplement in terms of
	initial_gdb_ttystate.  Make static.
	* terminal.h (gdb_has_a_terminal): Delete declaration.
	(set_initial_gdb_ttystate): Add comment.
	* top.c (show_interactive_mode): Use input_interactive_p instead
	of gdb_has_a_terminal.

gdb/testsuite/ChangeLog:
2016-08-23  Pedro Alves  <palves@redhat.com>

	PR gdb/20494
	* gdb.base/new-ui-echo.c: New file.
	* gdb.base/new-ui-echo.exp: New file.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] gdbserver_spawn "" rather than gdbserver_spawn ${binfile}
@ 2016-08-23 17:39 sergiodj+buildbot
  2016-08-23 20:59 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-08-23 17:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e9d9abd7470ea500eb4e82567fff68e87a30efb9 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: e9d9abd7470ea500eb4e82567fff68e87a30efb9

gdbserver_spawn "" rather than gdbserver_spawn ${binfile}

Hi,
I happen to see gdbserver is spawned like this in gdb.log,

spawn /scratch/yao/gdb/build-git/x86_64/gdb/testsuite/../../gdb/gdbserver/gdbserver --once :2346 /scratch/yao/gdb/build-git/x86_64/gdb/testsuite/outputs/gdb.s
erver/connect-stopped-target/connect-stopped-target /scratch/yao/gdb/build-git/x86_64/gdb/testsuite/outputs/gdb.server/connect-stopped-target/connect-stopped-t
arget

spawn /scratch/yao/gdb/build-git/x86_64/gdb/testsuite/../../gdb/gdbserver/gdbserver --once :2347 /scratch/yao/gdb/build-git/x86_64/gdb/testsuite/outputs/gdb.s
erver/connect-stopped-target/connect-stopped-target /scratch/yao/gdb/build-git/x86_64/gdb/testsuite/outputs/gdb.server/connect-stopped-target/connect-stopped-t
arget

as we can see, there are two instances of connect-stopped-target or
connect-stopped-target in the command line spawning gdbserver, but
none of these gets parameters from command line.  In these two
tests, gdbserver is spawned via "gdbserver_spawn ${binfile}".  However,
the argument of gdbserver_spawn is the argument passed the child
inferior, not the program itself.

 # Start a gdbserver process running SERVER_EXEC, and connect GDB
 # to it.  CHILD_ARGS are passed to the inferior.
 #
 # Returns the target protocol and socket to connect to.

proc gdbserver_spawn { child_args } {
    set target_exec [gdbserver_download_current_prog]

GDBserver gets the program via last_loaded_file, which is set by
gdb_file_cmd.  In each test, we don't need to pass ${binfile}.

gdb/testsuite:

2016-08-23  Yao Qi  <yao.qi@linaro.org>

	* gdb.server/connect-stopped-target.exp (do_test): Pass "" to
	gdbserver_spawn.
	* gdb.server/connect-without-multi-process.exp (do_test):
	Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] R_OR1K_GOTOFF_* relocations
@ 2016-08-23 13:28 sergiodj+buildbot
  2016-08-23 13:43 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-08-23 13:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT eacfca90f1ff457d3a7be9d593040218b6208d2b ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: eacfca90f1ff457d3a7be9d593040218b6208d2b

R_OR1K_GOTOFF_* relocations

	PR 20475
	* elf32-or1k.c (or1k_elf_relocate_section): Offset from
	_GLOBAL_OFFSET_TABLE_, not start of .got section.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Free the string buffer used by the chew program to hold each file it parses.
@ 2016-08-22 21:15 sergiodj+buildbot
  2016-08-22 22:29 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-08-22 21:15 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5fbe0d878a691b9be42bb2bdebd027ac3dfd38c2 ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: 5fbe0d878a691b9be42bb2bdebd027ac3dfd38c2

Free the string buffer used by the chew program to hold each file it parses.

	* doc/chew.c (main): Free the string buffer used to files as they
	are parsed.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Error on unsupported PowerPC ifuncs
@ 2016-08-22 20:15 sergiodj+buildbot
  2016-08-22 20:56 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-08-22 20:15 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 888a7fc3665a67e20da1bce2f865b0ff9ef15842 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 888a7fc3665a67e20da1bce2f865b0ff9ef15842

Error on unsupported PowerPC ifuncs

The pr19784 tests fail on ppc32 due to a gcc bug.  The failure should
be noticed when building both libpr19784a.so and libpr19784b.so,
rather than ld building a buggy libpr19784a.so that fails at run time.
This patch fixes that by moving the @local ifunc check out of
check_relocs, where a call destination may not yet be known to be
ifunc.  The patch also adds a related error for -mbss-plt code.

	* elf32-ppc.c (ppc_elf_check_relocs): Move error for @local ifunc..
	(ppc_elf_relocate_section): ..to here.  Comment.  Error on
	detecting -mbss-plt -fPIC local ifuncs too.
	(ppc_elf_size_dynamic_sections): Comment on unnecessary glink
	branch table entries.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [AArch64] Match instruction "STP with base register" in prologue
@ 2016-08-19 19:59 sergiodj+buildbot
  2016-08-20  5:13 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-08-19 19:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 03bcd7394eefb9399f5ab97919a0463dea274c02 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 03bcd7394eefb9399f5ab97919a0463dea274c02

[AArch64] Match instruction "STP with base register" in prologue

Nowadays, we only match pre-indexed STP in prologue.  Due to the change
in gcc, https://gcc.gnu.org/ml/gcc-patches/2016-07/msg01933.html, it
may generate "STP with base register" in prologue, which GDB doesn't
handle.  That is to say, previously GCC generates prologue like this,

 sub sp, sp, #490
 stp x29, x30, [sp, #-96]!
 mov x29, sp

with the gcc patch above, GCC generates prologue like like this,

 sub sp, sp, #4f0
 stp x29, x30, [sp]
 mov x29, sp

This patch is to teach GDB to recognize this instruction in prologue
analysis.

gdb:

2016-08-19  Yao Qi  <yao.qi@linaro.org>

	* aarch64-tdep.c (aarch64_analyze_prologue): Handle register
	based STP instruction.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] x32: Avoid unsigned long when installing fast tracepoint jump pads
@ 2016-08-19 17:02 sergiodj+buildbot
  2016-08-19 17:20 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-08-19 17:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c8ef42eed100c2439e600e846caa7437da93ac17 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: c8ef42eed100c2439e600e846caa7437da93ac17

x32: Avoid unsigned long when installing fast tracepoint jump pads

We're casting through unsigned long to write a 64-bit immediate
operand of movabs (the comment said movl, but that was incorrect).
The problem is that unsigned long is 32-bit on x32, so we were writing
fewer bytes than necessary.

Fix this by using an 8 byte memcpy like in other similar places in the
function.

gdb/gdbserver/ChangeLog:
2016-08-19  Pedro Alves  <palves@redhat.com>

	* linux-x86-low.c (amd64_install_fast_tracepoint_jump_pad): Fix
	comment.  Use memcpy instead of casting through unsigned long.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix for powerpc-power.exp gdb regression test for Power 9
@ 2016-08-19  6:30 sergiodj+buildbot
  2016-08-19  8:49 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-08-19  6:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 63373e4f1610f3917cdb034b8e34dbd44c86489d ***

Author: Carl Love <cel@us.ibm.com>
Branch: master
Commit: 63373e4f1610f3917cdb034b8e34dbd44c86489d

Fix for powerpc-power.exp gdb regression test for Power 9

The GDB testsuite reports 5 test failures on Power 7 instructions.
Additionally the ppc test is missing the new Power 9 instructions as
well as a large number of older instructions.  Additionally, some
instruction names have changed or been deleted.  This patch
fixes the test failures and completely updates the test to make it
consistent with the supported Power 9 instructions listed in:

   gas/testsuite/gas/ppc/power7.d
   gas/testsuite/gas/ppc/power8.d
   gas/testsuite/gas/ppc/power9.d
   gas/testsuite/gas/ppc/altivec.d
   gas/testsuite/gas/ppc/altivec2.d
   gas/testsuite/gas/ppc/altivec3.d
   gas/testsuite/gas/ppc/vsx.d
   gas/testsuite/gas/ppc/vsx2.d
   gas/testsuite/gas/ppc/vsx3.d
-----------------------------------------------------

gdb/testsuite/ChangeLog

2016-08-18  Carl Love  <cel@us.ibm.com>

	* gdb.arch/powerpc-power.s: Add new Power9 instruction tests
	and sync up the test with tests in gas/testsuite/gas/ppc.
	* gdb.arch/powerpc-power.exp: Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix remove-inferior error message
@ 2016-08-18 15:13 sergiodj+buildbot
  2016-08-18 20:24 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-08-18 15:13 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT eb2332d78d4ef40a2696aa0f6c833ea26a739efc ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: eb2332d78d4ef40a2696aa0f6c833ea26a739efc

Fix remove-inferior error message

This error message should not contain the word symbol:

  (gdb) remove-inferiors 1
  Warning: Can not remove current symbol inferior 1.

gdb/ChangeLog:

	* inferior.c (remove_inferior_command): Fix error message.

gdb/testsuite/ChangeLog:

	* gdb.multi/remove-inferiors.exp (test_remove_inferiors): Fix
	expected error message.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Add remove-inferiors test
@ 2016-08-18 14:37 sergiodj+buildbot
  2016-08-18 15:02 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-08-18 14:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 63c61e04bb7168f0819fc590ac44e7583b225f7b ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: 63c61e04bb7168f0819fc590ac44e7583b225f7b

Add remove-inferiors test

I noticed that the remove-inferiors command was not tested, and as I am
doing some changes related to the user selection, I want to make sure I
don't break it.  For example, I want to make sure it's not possible to
remove the current inferior.

gdb/testsuite/ChangeLog:

	* gdb.multi/remove-inferiors.exp: New file.
	* gdb.multi/remove-inferiors.c: New file.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Remove stale comment
@ 2016-08-17 23:52 sergiodj+buildbot
  2016-08-18 14:05 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-08-17 23:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9b19e39006796a4dc90f9801f44bb6f07fdb6386 ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: 9b19e39006796a4dc90f9801f44bb6f07fdb6386

Remove stale comment

This comment seems outdated, since exiting an inferior does not remove
it.

gdb/ChangeLog:

	* inferior.c (exit_inferior_1): Remove comment.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] sim: cgen: constify mode_names
@ 2016-08-15 12:16 sergiodj+buildbot
  2016-08-15 12:26 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-08-15 12:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4c171e25a8c83fc26b78430fa632fa9e64f61050 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 4c171e25a8c83fc26b78430fa632fa9e64f61050

sim: cgen: constify mode_names


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] sim: cgen: drop unused argv/envp definitions
@ 2016-08-14  7:01 sergiodj+buildbot
  2016-08-14  8:49 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-08-14  7:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6b97945424f3714d2f9f6866079fd2bc658f4285 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 6b97945424f3714d2f9f6866079fd2bc658f4285

sim: cgen: drop unused argv/envp definitions

The common argv/envp are used now by all ports, so drop this old
cgen fragment.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Correct .dynsym sh_info
@ 2016-08-13 21:55 sergiodj+buildbot
  2016-08-13 21:55 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-08-13 21:55 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 90ac242072dc68ad454aaaa228868b0f1c8e10f9 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 90ac242072dc68ad454aaaa228868b0f1c8e10f9

Correct .dynsym sh_info

bfd/
	* elf-bfd.h (struct elf_link_hash_table): Add local_dynsymcount.
	* elflink.c (_bfd_elf_link_renumber_dynsyms): Set local_dynsymcount.
	(bfd_elf_final_link): Set .dynsym sh_info from local_dynsymcount.
ld/
	* testsuite/ld-tic6x/shlib-1.rd: Correct expected .dynsym sh_info.
	* testsuite/ld-tic6x/shlib-1b.rd: Likewise.
	* testsuite/ld-tic6x/shlib-1r.rd: Likewise.
	* testsuite/ld-tic6x/shlib-1rb.rd: Likewise.
	* testsuite/ld-tic6x/shlib-app-1.rd: Likewise.
	* testsuite/ld-tic6x/shlib-app-1b.rd: Likewise.
	* testsuite/ld-tic6x/shlib-app-1r.rd: Likewise.
	* testsuite/ld-tic6x/shlib-app-1rb.rd: Likewise.
	* testsuite/ld-tic6x/shlib-noindex.rd: Likewise.
	* testsuite/ld-tic6x/static-app-1.rd: Likewise.
	* testsuite/ld-tic6x/static-app-1b.rd: Likewise.
	* testsuite/ld-tic6x/static-app-1r.rd: Likewise.
	* testsuite/ld-tic6x/static-app-1rb.rd: Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix fallout from gdb/20413's fix (x32: linux_ptrace_test_ret_to_nx: Cannot PTRACE_PEEKUSER)
@ 2016-08-12 10:33 sergiodj+buildbot
  2016-08-12 13:46 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-08-12 10:33 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 39b22471578843019026c50fcdbe0483a6045970 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 39b22471578843019026c50fcdbe0483a6045970

Fix fallout from gdb/20413's fix (x32: linux_ptrace_test_ret_to_nx: Cannot PTRACE_PEEKUSER)

Fixes, on NIOS GNU/Linux:

  In file included from
  /scratch/mbilal/nois-lite/src/gdb-trunk/gdb/gdbserver/../nat/linux-ptrace.c:26:0:
  /scratch/mbilal/nois-lite/src/gdb-trunk/gdb/gdbserver/../gregset.h:27:23:
  error: unknown type name 'gregset_t'
   #define GDB_GREGSET_T gregset_t
			 ^

Fix this by including sys/procfs.h directly.  We shouldn't really be
including a gdb-only header in a gdb/nat/ file, anyway.  Whoops.

gdb/ChangeLog:
2016-08-11  Pedro Alves  <palves@redhat.com>

	PR gdb/20413
	* nat/linux-ptrace.c: Include <sys/procfs.h> instead of
	"gregset.h".


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Handle correctly passing a bad interpreter name to new-ui
@ 2016-08-09 13:28 sergiodj+buildbot
  2016-07-26 14:07 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-08-09 13:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8194e927cc66e8cceb9890240ad75363b3ca6d53 ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: 8194e927cc66e8cceb9890240ad75363b3ca6d53

Handle correctly passing a bad interpreter name to new-ui

When a bad interpreter name is passed to new-ui, such as:

  (gdb)  new-ui bloop /dev/pts/10

A partially created UI is left in the UI list, with interp set to NULL.
Trying to do anything that will print on this UI (such as "start") will
cause a segmentation fault.

Changes in v2:

  - Use with_test_prefix to namespace test procedures
  - Give an explicit stable test name
  - Add a "bad terminal path" test
  - Remove useless runto_main
  - Add missing intro comments

I did not factor out the pty spawn, as there is some magic involved I
don't quite understand.  But it wouldn't bring that much anyway.

gdb/ChangeLog:

	* top.h (make_delete_ui_cleanup): New declaration.
	* top.c (delete_ui_cleanup): New function.
	(make_delete_ui_cleanup): New function.
	(new_ui_command): Create restore_ui cleanup earlier, create a
	delete_ui cleanup and discard it on success.

gdb/testsuite/ChangeLog:

	* gdb.base/new-ui.exp (do_test_invalid_args): New
	procedure.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] linux-procfs: Introduce enum proc_state
@ 2016-08-09 13:06 sergiodj+buildbot
  2016-07-26 12:34 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-08-09 13:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d617208bb06bd461b52ce041d89f7127e3044762 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: d617208bb06bd461b52ce041d89f7127e3044762

linux-procfs: Introduce enum proc_state

Parse the process's /proc/PID/status state into an enum instead of the
current scheme of passing state strings around.

gdb/ChangeLog:
2016-07-25  Pedro Alves  <palves@redhat.com>

	* nat/linux-procfs.c (enum proc_state): New enum.
	(parse_proc_status_state): New function.
	(linux_proc_pid_get_state): Replace output string buffer parameter
	with an output proc_state parameter.  Use parse_proc_status_state.
	(linux_proc_pid_is_gone): Adjust to use proc_state values.
	(linux_proc_pid_has_state): Change type of 'state' parameter; now
	an enum proc_state.  Adjust to linux_proc_pid_get_state interface
	change.
	(linux_proc_pid_is_stopped)
	(linux_proc_pid_is_trace_stopped_nowarn)
	(linux_proc_pid_is_zombie_maybe_warn): Adjust to
	linux_proc_pid_get_state interface change.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix memory leaks in chew program.
@ 2016-08-08 16:36 sergiodj+buildbot
  2016-08-09 11:42 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-08-08 16:36 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8a286b63457628b0a55d395f14005f254512e27d ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: 8a286b63457628b0a55d395f14005f254512e27d

Fix memory leaks in chew program.

	* doc/chew.c (delete_string): Only free the string buffer if it is
	there.  Mark the buffer as NULL after freeing.
	(drop): Free the dropped string.
	(free_words): New function: Frees the memory allocated to the
	dictionary.
	(add_instrinsic): Duplicate the name string, so that it can be
	freed later on.
	(compile): Free unused words.
	(main): Free the dictionary and top level string buffers at the
	end.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] 2016-08-04 Thomas Preud'homme <thomas.preudhomme@arm.com>
@ 2016-08-04 16:49 sergiodj+buildbot
  2016-08-04 19:23 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-08-04 16:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 54ddd295b505efe4b07cc1e939d4e150032603d8 ***

Author: Thomas Preud'homme <thomas.preudhomme@arm.com>
Branch: master
Commit: 54ddd295b505efe4b07cc1e939d4e150032603d8

2016-08-04  Thomas Preud'homme  <thomas.preudhomme@arm.com>

bfd/
	* bfd-in.h (bfd_elf32_arm_set_target_relocs): Add one parameter.
	* bfd-in2.h: Regenerate.
	* elf32-arm.c (struct elf32_arm_link_hash_table): Declare new
	cmse_implib field.
	(bfd_elf32_arm_set_target_relocs): Add new parameter to initialize
	cmse_implib field in struct elf32_arm_link_hash_table.
	(elf32_arm_filter_cmse_symbols): New function.
	(elf32_arm_filter_implib_symbols): Likewise.
	(elf_backend_filter_implib_symbols): Define to
	elf32_arm_filter_implib_symbols.

ld/
	* emultempl/armelf.em (cmse_implib): Declare and define this new
	static variable.
	(arm_elf_create_output_section_statements): Add new cmse_implib
	parameter.
	(OPTION_CMSE_IMPLIB): Define macro.
	(PARSE_AND_LIST_LONGOPTS): Add entry for new --cmse-implib switch.
	(PARSE_AND_LIST_OPTIONS): Likewise.
	(PARSE_AND_LIST_ARGS_CASES): Handle OPTION_CMSE_IMPLIB case.
	* ld.texinfo (--cmse-implib): Document new option.
	* testsuite/ld-arm/arm-elf.exp
	(Secure gateway import library generation): New test.
	(Secure gateway import library generation: errors): Likewise.
	* testsuite/ld-arm/cmse-implib.s: New file.
	* testsuite/ld-arm/cmse-implib-errors.out: Likewise.
	* testsuite/ld-arm/cmse-implib.rd: Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [GDBserver] Remove td_ta_event_addr td_ta_set_event and td_ta_event_getmsg
@ 2016-08-02 16:45 sergiodj+buildbot
  2016-08-02 18:45 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-08-02 16:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 979659d08478172311764b468bfce4960b38760b ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 979659d08478172311764b468bfce4960b38760b

[GDBserver] Remove td_ta_event_addr td_ta_set_event and td_ta_event_getmsg

As a result of this commit,

  9b4c5f878ff39e04127a1ad95f6b3832afe6d278
  (Remove support for thread events without PTRACE_EVENT_CLONE in GDBServer.)

the last usage of td_ta_event_addr td_ta_set_event and
td_ta_event_getmsg were removed.  They are no longer used.  This patch
is to remove them.

gdb/gdbserver:

2016-08-02  Yao Qi  <yao.qi@linaro.org>

	* thread-db.c (struct thread_db) <td_ta_event_getmsg_p>: Remove.
	<td_ta_set_event_p, td_ta_event_addr_p>: Remove.
	(thread_db_load_search): Update.
	(try_thread_db_load_1): Don't look for td_ta_event_addr,
	td_ta_set_event and td_ta_event_getmsg.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Synchronize libiberty sources with FSF GCC mainline version.
@ 2016-08-02 14:43 sergiodj+buildbot
  2016-08-02 14:52 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-08-02 14:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fa3fcee7b8c73070306ec358e730d1dfcac246bf ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: fa3fcee7b8c73070306ec358e730d1dfcac246bf

Synchronize libiberty sources with FSF GCC mainline version.

include	* libiberty.h (MAX_ALLOCA_SIZE): New macro.

libiberty * make-relative-prefix.c (make_relative_prefix_1): Fall back to
	malloc if alloca argument is greater than MAX_ALLOCA_SIZE.

	* cp-demangle.c (cplus_demangle_operators): Add f[lrLR].
	(d_expression_1): Handle them.
	(d_maybe_print_fold_expression): New.
	(d_print_comp_inner): Use it.
	(d_index_template_argument): Handle negative index.

	* cp-demangle.c (cplus_demangle_operators): Add sP and sZ.
	(d_print_comp_inner): Handle them.
	(d_template_args_1): Split out from d_template_args.
	(d_args_length): New.

	PR c++/70926
	* cplus-dem.c: Handle large values and overflow when demangling
	length variables.
	(demangle_template_value_parm): Read only until end of mangled string.
	(do_hpacc_template_literal): Likewise.
	(do_type): Handle overflow when demangling array indices.

	* cp-demangle.c (cplus_demangle_print_callback): Avoid zero-length
	  VLAs.

	PR c++/70498
	* cp-demangle.c (d_expression_1): Formatting fix.

	* cplus-dem.c (enum type_kind_t): Add tk_rvalue_reference
	constant.
	(demangle_template_value_parm): Handle tk_rvalue_reference
	type kind.
	(do_type): Support 'O' type id (rvalue references).

	* testsuite/demangle-expected: Add tests.

	PR c++/70498
	* cp-demangle.c: Parse numbers as integer instead of long to avoid
	overflow after sanity checks. Include <limits.h> if available.
	(INT_MAX): Define if necessary.
	(d_make_template_param): Takes integer argument instead of long.
	(d_make_function_param): Likewise.
	(d_append_num): Likewise.
	(d_identifier): Likewise.
	(d_number): Parse as and return integer.
	(d_compact_number): Handle overflow.
	(d_source_name): Change variable type to integer for parsed number.
	(d_java_resource): Likewise.
	(d_special_name): Likewise.
	(d_discriminator): Likewise.
	(d_unnamed_type): Likewise.
	* testsuite/demangle-expected: Add regression test cases.

	* configure: Remove SH5 support.

	PR c++/69687
	* cplus-dem.c: Include <limits.h> if available.
	(INT_MAX): Define if necessary.
	(remember_type, remember_Ktype, register_Btype, string_need):
	Abort if we detect cases where we the size of the allocation would
	overflow.

	PR c++/70492
	* cplus-dem.c (gnu_special): Handle case where consume_count returns
	-1.

	PR c++/67394
	PR c++/70481
	* cplus-dem.c (squangle_mop_up): Zero bsize/ksize after freeing
	btypevec/ktypevec.
	* testsuite/demangle-expected: Add coverage tests.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix SH GOT allocation in the presence of linker garbage collection.
@ 2016-08-02 12:23 sergiodj+buildbot
  2016-08-02 12:56 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-08-02 12:23 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a94d834c9d0108f0bb50ddc311554d1bed320f54 ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: a94d834c9d0108f0bb50ddc311554d1bed320f54

Fix SH GOT allocation in the presence of linker garbage collection.

	PR ld/17739
ld	* emulparams/shelf.sh (CHECK_RELOCS_AFTER_OPEN_INPUT): Define with
	valye 'yes'.
	* emulparams/shelf32.sh: Likewise.
	* emulparams/shelf32.sh: Likewise.
	* emulparams/shelf_nto.sh: Likewise.
	* emulparams/shelf_nto.sh: Likewise.
	* emulparams/shelf_vxworks.sh: Likewise.
	* emulparams/shelf_vxworks.sh: Likewise.
	* emulparams/shlelf32_linux.sh: Likewise.
	* emulparams/shlelf32_linux.sh: Likewise.
	* emulparams/shlelf_linux.sh: Likewise.
	* emulparams/shlelf_linux.sh: Likewise.
	* emulparams/shlelf_nto.sh: Likewise.
	* emulparams/shlelf_nto.sh: Likewise.

bfd	* elf32-sh.c (sh_elf_gc_sweep_hook): Delete.
	(elf_backend_sweep_hook): Delete.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Swap "single-process" and "multi-process" in process-dies-while-detaching.exp
@ 2016-08-01 13:20 sergiodj+buildbot
  2016-08-01 13:41 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-08-01 13:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 41bfcd638a4e0e48b96ce4de2845372dea481322 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 41bfcd638a4e0e48b96ce4de2845372dea481322

Swap "single-process" and "multi-process" in process-dies-while-detaching.exp

"single-process" and "multi-process" are used in the test message of
process-dies-while-detaching.exp, but they are misplaced due to

    set mode [expr {$multi_process ? "single-process" : "multi-process"}]

This patch is to swap them.

gdb/testsuite:

2016-08-01  Yao Qi  <yao.qi@linaro.org>

	* gdb.threads/process-dies-while-detaching.exp (do_test): Set
	variable mode to "multi-process" if $multi_process is 1, otherwise
	set it to "single-process".


^ permalink raw reply	[flat|nested] 1181+ messages in thread
[parent not found: <db18dbabad8e7b63e98d47813ef20acac7072350@gdb-build>]
[parent not found: <293acfae4e3c9aad417e262edc9847c79bbbbb11@gdb-build>]
[parent not found: <6598661d14c90cabac1daa5e683d1e17883b2e41@gdb-build>]
[parent not found: <54806ffa85643c3a1ee721d5c3f5586d32f86ee1@gdb-build>]
[parent not found: <40c31709c6a51926fcb409611caa52b2da6515c0@gdb-build>]
[parent not found: <9cf12d57c58a82cfe3e6fee26d1ea55dfe49f9c4@gdb-build>]
[parent not found: <e0461dbb653dbb3c46ea7a15054fd2c98f879f31@gdb-build>]
[parent not found: <c0272db5854a799a9f3bb3803c3d03d1a62b9ac2@gdb-build>]
* [binutils-gdb] Allow empty struct expressions in Rust
@ 2016-07-22  3:02 sergiodj+buildbot
  2016-07-22  3:05 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-07-22  3:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 12df5c002dcbfc5ac54983e1e7040a182f71a753 ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 12df5c002dcbfc5ac54983e1e7040a182f71a753

Allow empty struct expressions in Rust

I learned recently that empty struct expressions, like "X{}", have been
promoted from experimental to stable in Rust.  This patch changes the
Rust expression parser to allow this case.

New test case included.
Built and regtested on x86-64 Fedora 23, using Rust 1.11 beta.

2016-07-21  Tom Tromey  <tom@tromey.com>

	* rust-lang.c (rust_tuple_struct_type_p): Return false for empty
	structs.
	* rust-exp.y (struct_expr_list): Allow empty elements.

2016-07-21  Tom Tromey  <tom@tromey.com>

	* gdb.rust/simple.rs (main): Use empty struct expression.
	* gdb.rust/simple.exp: Add tests for empty struct expression.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Set BFD_VERSION to 2.27.51
@ 2016-07-22  0:11 sergiodj+buildbot
  2016-07-22  5:03 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-07-22  0:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fecd57f9f1f58f043861d5929a650f35a88a6caa ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: fecd57f9f1f58f043861d5929a650f35a88a6caa

Set BFD_VERSION to 2.27.51

bfd/

	* version.m4 (BFD_VERSION): Set to 2.27.51.
	* configure: Regenerated.

binutils/

	* configure: Regenerated.

gas/

	* configure: Regenerated.

gprof/

	* configure: Regenerated.

ld/

	* configure: Regenerated.

opcodes/

	* configure: Regenerated.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Add -Wunused-but-set-* to build
@ 2016-07-21 21:22 sergiodj+buildbot
  2016-07-22  2:01 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-07-21 21:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 305450edd3f96bfeebff78300e1e93487563d90a ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 305450edd3f96bfeebff78300e1e93487563d90a

Add -Wunused-but-set-* to build

This adds -Wunused-but-set-variable and -Wunused-but-set-parameter to
configure.

2016-07-21  Tom Tromey  <tom@tromey.com>

	* configure: Rebuild.
	* warning.m4 (AM_GDB_WARNINGS) <build_warnings>: Add
	-Wunused-but-set-parameter, -Wunused-but-set-variable.

2016-07-21  Tom Tromey  <tom@tromey.com>

	* configure: Rebuild.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Remove unused variable in windows-nat.c
@ 2016-07-21 19:45 sergiodj+buildbot
  2016-07-21 23:04 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-07-21 19:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c25b7ccef4d6d96ed4af1d27c79d78767dba7161 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: c25b7ccef4d6d96ed4af1d27c79d78767dba7161

Remove unused variable in windows-nat.c

Leave the call for side effects.

gdb/ChangeLog:
2016-07-21  Pedro Alves  <palves@redhat.com>

	* windows-nat.c (handle_exception): Remove "th".


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Support vCont s and S actions with software single step
@ 2016-07-21 17:54 sergiodj+buildbot
  2016-07-21 20:54 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-07-21 17:54 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 21536b367ce73eed103e1389b5f45010f0c96bbb ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 21536b367ce73eed103e1389b5f45010f0c96bbb

Support vCont s and S actions with software single step

GDBserver with software single step should be able to claim supporting
vCont s and S actions, so that GDB knows the remote target can do
single step.  It doesn't matter to GDB that the single step in the
remote target is done via hardware or software.

gdb/gdbserver:

2016-07-21  Yao Qi  <yao.qi@linaro.org>

	* server.c (handle_v_requests): Support s and S actions
	if target_supports_software_single_step return true.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Create sub classes of 'struct breakpoint'
@ 2016-07-21 12:41 sergiodj+buildbot
  2016-07-21 14:10 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-07-21 12:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9aa76cd0a7b2cfdcc9da31e7763a695fac89f569 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 9aa76cd0a7b2cfdcc9da31e7763a695fac89f569

Create sub classes of 'struct breakpoint'

Nowadays, there are three types of breakpoint in GDBserver,

 - gdb breakpoints,
 - reinsert breakpoints, used for software single step,
 - other breakpoints, used for tracepoint,

but we only have one 'struct breakpoint' for all of them.  Some fields
are only useful to one type of breakpoint.  For example, cond_list
and command_list are only used by gdb breakpoints, while handler is
only used by other breakpoints.

This patch changes 'struct breakpoint' to a base class, which has fields
needed by all breakpoint types, also add three sub-classes to
'struct breakpoint' to these three types of breakpoints.

gdb/gdbserver:

2016-07-21  Yao Qi  <yao.qi@linaro.org>

	* mem-break.c (struct breakpoint) <cond_list>: Remove.
	<command_list, handler>: Remove.
	(struct gdb_breakpoint): New.
	(struct other_breakpoint): New.
	(struct reinsert_breakpoint): New.
	(is_gdb_breakpoint): New function.
	(any_persistent_commands): Update command_list if
	is_gdb_breakpoint returns true.
	(set_breakpoint): Create breakpoints according to their types.
	(find_gdb_breakpoint): Return 'struct gdb_breakpoint *'.
	(set_gdb_breakpoint_1): Likewise.
	(set_gdb_breakpoint): Likewise.
	(clear_breakpoint_conditions): Change parameter type to
	'struct gdb_breakpoint *'.
	(clear_breakpoint_commands): Likewise.
	(clear_breakpoint_conditions_and_commands): Likewise.
	(add_condition_to_breakpoint): Likewise.
	(add_breakpoint_condition): Likewise.
	(add_commands_to_breakpoint): Likewise.
	(check_breakpoints): Check other_breakpoint.
	(clone_one_breakpoint): Clone breakpopint according to its type.
	* mem-break.h (struct gdb_breakpoint): Declare.
	(set_gdb_breakpoint): Update declaration.
	(clear_breakpoint_conditions_and_commands): Likewise.
	(add_breakpoint_condition): Likewise.
	(add_breakpoint_commands): Likewise.
	* server.c (process_point_options): Change parameter type to
	'struct gdb_breakpoint *'.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Skip gdb.server/ tests if lack of XML support
@ 2016-07-21 11:10 sergiodj+buildbot
  2016-07-21 12:17 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-07-21 11:10 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bae62ee2087bb54fd06746c99de9b734cc58a721 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: bae62ee2087bb54fd06746c99de9b734cc58a721

Skip gdb.server/ tests if lack of XML support

I recently see some gdb.server/*.exp fails in my native gdb testing,
in which libexpat isn't available, so GDB isn't able to parse xml file.
It causes gdb.server/ tests fails because GDB can't get registers
correctly from GDBserver.

(gdb) PASS: gdb.server/connect-without-multi-process.exp: multiprocess=off: break main
target remote localhost:2352^M
Remote debugging using localhost:2352^M
warning: Can not parse XML target description; XML support was disabled at compile time^M
Reading /lib/ld-linux-armhf.so.3 from remote target...^M
warning: File transfers from remote targets can be slow. Use "set sysroot" to access files locally instead.^M
Reading /lib/ld-linux-armhf.so.3 from remote target...^M
Reading symbols from target:/lib/ld-linux-armhf.so.3...Reading /lib/ld-2.17.so.debug from remote target...^M
Reading /lib/.debug/ld-2.17.so.debug from remote target...^M
(no debugging symbols found)...done.^M
Remote 'g' packet reply is too long: 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000efffbe00000000808d0f4d100000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000^
0x4d0f8d80 in _start () from target:/lib/ld-linux-armhf.so.3^M

Without XML support in GDB, it can't parse xml sent by GDBserver, and has
to fall back to the oldest arch.  However, GDBserver doesn't know this
(IMO, this is a defect in RSP), and still choose the right target
description to create regcache and 'g' packet.  If the port only has
one target description or coincidentally two sides choose the same
target description, there is no such issue.  Otherwise, GDB is broken
on read registers.

This patch is to skip gdbserver tests if XML is not support and the
target has multiple target descriptions.

gdb/testsuite:

2016-07-21  Yao Qi  <yao.qi@linaro.org>

	* lib/gdbserver-support.exp (skip_gdbserver_tests): Return 1
	if gdb_skip_xml_test is true on some targets.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Enable ptrace events on new child processes.
@ 2016-07-20 20:22 sergiodj+buildbot
  2016-07-20 23:47 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-07-20 20:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5fa14c6b9789bad6f91dd21889f7b1a0eb75c6d0 ***

Author: John Baldwin <jhb@FreeBSD.org>
Branch: master
Commit: 5fa14c6b9789bad6f91dd21889f7b1a0eb75c6d0

Enable ptrace events on new child processes.

New child processes on FreeBSD do not inherit optional ptrace events
such as fork and LWP events from the parent process.  Instead,
explicitly enable events on new children when reporting a fork
event.

gdb/ChangeLog:

	* fbsd-nat.c (fbsd_wait): Use "fbsd_enable_proc_events" on
	new child processes.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Handle version 1a of FreeBSD's NT_PRSINFO.
@ 2016-07-20 18:21 sergiodj+buildbot
  2016-07-20 19:21 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-07-20 18:21 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0064d22386b99c047bbff3bcc73b6bfce9c29b4c ***

Author: John Baldwin <jhb@FreeBSD.org>
Branch: master
Commit: 0064d22386b99c047bbff3bcc73b6bfce9c29b4c

Handle version 1a of FreeBSD's NT_PRSINFO.

Version 1a adds a pr_pid member containing the process ID of the
terminating process.  The presence of pr_pid is inferred from the
note's size.

bfd/ChangeLog:

	* elf.c (elfcore_grok_freebsd_psinfo): Check for minimum note size
	and handle pr_pid if present.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Mark some more powerpc relocs as not handled by generic linker
@ 2016-07-20  4:10 sergiodj+buildbot
  2016-07-20  5:33 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-07-20  4:10 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3ce512885ba76da53fae84cd1a555bc721fdd25e ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 3ce512885ba76da53fae84cd1a555bc721fdd25e

Mark some more powerpc relocs as not handled by generic linker

	* elf64-ppc.c (ppc64_elf_howto_raw <R_PPC64_PLTREL32>): Put
	ppc64_elf_unhandled_reloc for special_function.
	* elf32-ppc.c (ppc_elf_howto_raw): Similarly for lots of relocs.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Use do_self_tests in selftest.exp
@ 2016-07-19 10:01 sergiodj+buildbot
  2016-07-19 10:39 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-07-19 10:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f25827c194fe9894f2c65f7e1101854022be4328 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: f25827c194fe9894f2c65f7e1101854022be4328

Use do_self_tests in selftest.exp

This patch uses do_self_tests to simplify selftest.exp.  It doesn't
change the tests except the order,

-PASS: gdb.gdb/selftest.exp: Disassemble main
 PASS: gdb.gdb/selftest.exp: breakpoint in captured_main
+PASS: gdb.gdb/selftest.exp: run until breakpoint at captured_main
+PASS: gdb.gdb/selftest.exp: Disassemble main
 PASS: gdb.gdb/selftest.exp: set interrupt character in test_with_self
 PASS: gdb.gdb/selftest.exp: set listsize to 1
-PASS: gdb.gdb/selftest.exp: run until breakpoint at captured_main

gdb/testsuite:

2016-07-19  Yao Qi  <yao.qi@linaro.org>

	* gdb.gdb/selftest.exp: Remove checks on is_remote and isnative.
	(test_with_self): Remove some code.  Remove argument executable.
	(top-level): Use do_self_tests.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Don't include libbfd.h outside of bfd, part 4
@ 2016-07-16 15:01 sergiodj+buildbot
  2016-07-16 15:30 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-07-16 15:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4212b42d795628dcc36bcffc7cf16175f7698305 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 4212b42d795628dcc36bcffc7cf16175f7698305

Don't include libbfd.h outside of bfd, part 4

Not much to see here, just renaming a function.

bfd/
	* targets.c (bfd_seach_for_target): Rename to..
	(bfd_iterate_over_targets): ..this.  Rewrite doc.
	* bfd-in2.h: Regenerate.
ld/
	* ldlang.c (open_output): Replace bfd_search_for_target with
	bfd_iterate_over_targets.  Localize vars.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] GDB testsuite: Escape paths used in regular expressions
@ 2016-07-15 18:48 sergiodj+buildbot
  2016-07-15 18:56 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-07-15 18:48 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 37539ebee2ea9fc0daceaae1074a79de88d563fb ***

Author: Don Breazeal <donb@codesourcery.com>
Branch: master
Commit: 37539ebee2ea9fc0daceaae1074a79de88d563fb

GDB testsuite: Escape paths used in regular expressions

This patch fixes problems with a few GDB testsuites when executing in a
path that contains special characters (e.g. "++").  When such paths are
used as a regular expression, the regular expression parser will choke
and cause the tests to fail.  This patch uses string_to_regexp to
escape strings that will be used as regular expressions, in order to
sanitize path names used in expect scripts.

2016-07-15  Zachary Welch  <zwelch@codesourcery.com>
	    Don Breazeal <donb@codesourcery.com>

	gdb/testsuite/ChangeLog:
	* gdb.base/maint.exp: Escape paths used in regular expressions.
	* gdb.stabs/weird.exp: Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Tidy up debugging in the ARC port of the BFD library.
@ 2016-07-15 11:25 sergiodj+buildbot
  2016-07-15 11:27 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-07-15 11:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f7e8b360fe6dd93aae7cb4af554dc66364da4fe0 ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: f7e8b360fe6dd93aae7cb4af554dc66364da4fe0

Tidy up debugging in the ARC port of the BFD library.

bfd	* elf32-arc.c (PR_DEBUG): Delete.
	Fix printing of debug information.  Fix formatting of debug
	statements.
	(debug_arc_reloc): Handle symbols that are not from an input file.
	(arc_do_relocation): Remove excessive exclamation points.
	(elf_arc_relocate_section): Print an informative message if the
	relocation fails, even if debugging is not enabled.
	* arc-got.h: Fix formatting.  Fix printing of debug information.
	(new_got_entry_to_list): Use xmalloc.
	* config.bfd: use the big-endian arc vector as the default vector
	for big-endian arc targets.

ld	* testsuite/ld-arc/arc.exp: Always run the sda-relocs test in
	little endian mode.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] BFD: Let targets handle relocations against absolute symbols
@ 2016-07-14 21:44 sergiodj+buildbot
  2016-07-14 23:57 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-07-14 21:44 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0c117286270e8166022900f4e5fef89719ccd2dc ***

Author: Maciej W. Rozycki <macro@imgtec.com>
Branch: master
Commit: 0c117286270e8166022900f4e5fef89719ccd2dc

BFD: Let targets handle relocations against absolute symbols

Fix a generic BFD issue with relocations against absolute symbols, which
are installed without using any individual relocation handler provided
by the backend.  This causes any absolute section's addend to be lost on
REL targets such as o32 MIPS, and also relocation-specific calculation
adjustments are not made.

As an example assembling this program:

$ cat test.s
	.text
foo:
	b	bar
	b	baz

	.set	bar, 0x1234
$ as -EB -32 -o test-o32.o test.s
$ as -EB -n32 -o test-n32.o test.s

produces this binary code:

$ objdump -dr test-o32.o test-n32.o

test-o32.o:     file format elf32-tradbigmips

Disassembly of section .text:

00000000 <foo>:
   0:	10000000 	b	4 <foo+0x4>
			0: R_MIPS_PC16	*ABS*
   4:	00000000 	nop
   8:	1000ffff 	b	8 <foo+0x8>
			8: R_MIPS_PC16	baz
   c:	00000000 	nop

test-n32.o:     file format elf32-ntradbigmips

Disassembly of section .text:

00000000 <foo>:
   0:	10000000 	b	4 <foo+0x4>
			0: R_MIPS_PC16	*ABS*+0x1230
   4:	00000000 	nop
   8:	10000000 	b	c <foo+0xc>
			8: R_MIPS_PC16	baz-0x4
   c:	00000000 	nop
$

where it is clearly visible in `test-o32.o', which uses REL relocations,
that the absolute section's addend equivalent to the value of `bar' -- a
reference to which cannot be fully resolved at the assembly time,
because the reference is PC-relative -- has been lost, as has been the
relocation-specific adjustment of -4, required to take into account the
PC+4-relative calculation made by hardware with branches and seen in the
external symbol reference to `baz' as the `ffff' addend encoded in the
instruction word.  In `test-n32.o', which uses RELA relocations, the
absolute section's addend has been correctly retained.

Give precedence then in `bfd_perform_relocation' and
`bfd_install_relocation' to any individual relocation handler the
backend selected may have provided, while still resorting to the generic
calculation otherwise.  This retains the semantics which we've had since
forever or before the beginning of our repository history, and is at the
very least compatible with `bfd_elf_generic_reloc' being used as the
handler.

Retain the `bfd_is_und_section' check unchanged at the beginning of
`bfd_perform_relocation' since this does not affect the semantics of the
function.  The check returns the same `bfd_reloc_undefined' code the
check for a null `howto' does, so swapping the two does not matter.
Also the check is is mutually exclusive with the `bfd_is_abs_section'
check, since a section cannot be absolute and undefined both at once, so
swapping the two does not matter either.

With this change applied the program quoted above now has the in-place
addend correctly calculated and installed in the field being relocated:

$ objdump -dr fixed-o32.o

fixed-o32.o:     file format elf32-tradbigmips

Disassembly of section .text:

00000000 <foo>:
   0:	1000048c 	b	1234 <bar>
			0: R_MIPS_PC16	*ABS*
   4:	00000000 	nop
   8:	1000ffff 	b	8 <foo+0x8>
			8: R_MIPS_PC16	baz
   c:	00000000 	nop
$

Add a set of MIPS tests to cover the relevant cases, including absolute
symbols with addends, and verifying that PC-relative relocations against
symbols concerned resolve to the same value in the final link regardless
of whether the REL or the RELA relocation form is used.  Exclude linker
tests though which would overflow the in-place addend on REL targets and
use them as dump patterns for RELA targets only.

	bfd/
	* reloc.c (bfd_perform_relocation): Try the `howto' handler
	first with relocations against absolute symbols.
	(bfd_install_relocation): Likewise.

	gas/
	* testsuite/gas/mips/mips16-branch-absolute.d: Update patterns.
	* testsuite/gas/mips/branch-absolute.d: New test.
	* testsuite/gas/mips/branch-absolute-n32.d: New test.
	* testsuite/gas/mips/branch-absolute-n64.d: New test.
	* testsuite/gas/mips/branch-absolute-addend-n32.d: New test.
	* testsuite/gas/mips/branch-absolute-addend-n64.d: New test.
	* testsuite/gas/mips/mips16-branch-absolute-n32.d: New test.
	* testsuite/gas/mips/mips16-branch-absolute-n64.d: New test.
	* testsuite/gas/mips/mips16-branch-absolute-addend-n32.d: New
	test.
	* testsuite/gas/mips/mips16-branch-absolute-addend-n64.d: New
	test.
	* testsuite/gas/mips/micromips-branch-absolute.d: New test.
	* testsuite/gas/mips/micromips-branch-absolute-n32.d: New test.
	* testsuite/gas/mips/micromips-branch-absolute-n64.d: New test.
	* testsuite/gas/mips/micromips-branch-absolute-addend-n32.d: New
	test.
	* testsuite/gas/mips/micromips-branch-absolute-addend-n64.d: New
	test.
	* testsuite/gas/mips/branch-absolute.s: New test source.
	* testsuite/gas/mips/branch-absolute-addend.s: New test source.
	* testsuite/gas/mips/mips16-branch-absolute-addend.s: New test
	source.
	* testsuite/gas/mips/micromips-branch-absolute.s: New test
	source.
	* testsuite/gas/mips/micromips-branch-absolute-addend.s: New
	test source.
	* testsuite/gas/mips/mips.exp: Run the new tests.

	ld/
	* testsuite/ld-mips-elf/branch-absolute.d: New test.
	* testsuite/ld-mips-elf/branch-absolute-n32.d: New test.
	* testsuite/ld-mips-elf/branch-absolute-n64.d: New test.
	* testsuite/ld-mips-elf/branch-absolute-addend.d: New test.
	* testsuite/ld-mips-elf/branch-absolute-addend-n32.d: New test.
	* testsuite/ld-mips-elf/branch-absolute-addend-n64.d: New test.
	* testsuite/ld-mips-elf/micromips-branch-absolute.d: New test.
	* testsuite/ld-mips-elf/micromips-branch-absolute-n32.d: New
	test.
	* testsuite/ld-mips-elf/micromips-branch-absolute-n64.d: New
	test.
	* testsuite/ld-mips-elf/micromips-branch-absolute-addend.d: New
	test.
	* testsuite/ld-mips-elf/micromips-branch-absolute-addend-n32.d:
	New test.
	* testsuite/ld-mips-elf/micromips-branch-absolute-addend-n64.d:
	New test.
	* testsuite/ld-mips-elf/mips-elf.exp: Run the new tests, except
	from `branch-absolute-addend' and
	`micromips-branch-absolute-addend', referred indirectly only.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Use getcurx in curses code
@ 2016-07-14 18:10 sergiodj+buildbot
  2016-07-14 18:54 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-07-14 18:10 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cecc8b99060bf82632345bd1c07d50c7ae8d81ef ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: cecc8b99060bf82632345bd1c07d50c7ae8d81ef

Use getcurx in curses code

As suggested by Pedro, this changes a few spots to use getcurx, rather
than getyx.  This avoids some unused variable warnings.

2016-07-14  Tom Tromey  <tom@tromey.com>

	* tui/tui-winsource.c (tui_show_source_line): Use getcurx.
	* tui/tui-io.c (tui_puts): Use getcurx.
	(tui_redisplay_readline): Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Small improvements to the ARM simulator to cope with illegal binaries.
@ 2016-07-14  9:52 sergiodj+buildbot
  2016-07-14 10:05 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-07-14  9:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7df94786e4723ba93d8982e55fc5e652b4b80142 ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: 7df94786e4723ba93d8982e55fc5e652b4b80142

Small improvements to the ARM simulator to cope with illegal binaries.

	* armemu.c (Multiply64): Only issue error messages about invalid
	arguments if debugging is enabled.
	* armos.c (ARMul_OSHandleSWI): Ignore invalid flags.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] opcodes, gas: support for the ldtxa SPARC instructions.
@ 2016-07-13 14:28 sergiodj+buildbot
  2016-07-13 14:28 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-07-13 14:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6e7ced37e756420742d51abb044c24d0f1929143 ***

Author: Jose E. Marchesi <jose.marchesi@oracle.com>
Branch: master
Commit: 6e7ced37e756420742d51abb044c24d0f1929143

opcodes,gas: support for the ldtxa SPARC instructions.

This patch adds support for the LDTXA instructions, along with the
corresponding ASIs.  Tests for GAS are included.

opcodes/ChangeLog:

2016-07-12  Jose E. Marchesi  <jose.marchesi@oracle.com>

	* sparc-opc.c (ldtxa): New macro.
	(sparc_opcodes): Use the macro defined above to add entries for
	the LDTXA instructions.
	(asi_table): Add the ASI_TWINX_* asis used in the LDTXA
	instruction.

gas/ChangeLog:

2016-07-12  Jose E. Marchesi  <jose.marchesi@oracle.com>

	* testsuite/gas/sparc/ldtxa.s: New file.
	* testsuite/gas/sparc/ldtxa.d: Likewise.
	* testsuite/gas/sparc/sparc.exp: Execute the ldtxa test.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Match the selftest output when captured_main is inlined
@ 2016-07-12 14:56 sergiodj+buildbot
  2016-07-12 15:05 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-07-12 14:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3cfe46b618f140ce93de3cdbe9693b51eea4acf3 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 3cfe46b618f140ce93de3cdbe9693b51eea4acf3

Match the selftest output when captured_main is inlined

In gdb.gdb/observer.exp, I see the following fail,

(gdb) break captured_main^M
Breakpoint 1 at 0x57e409: file ../../binutils-gdb/gdb/main.c, line 492.^M
(gdb) PASS: gdb.gdb/observer.exp: breakpoint in captured_main
run -nw -nx -data-directory /home/yao.qi/SourceCode/gnu/build/gdb/testsuite/../data-directory^M
Starting program: /home/yao.qi/SourceCode/gnu/build/gdb/testsuite/outputs/gdb.gdb/observer/xgdb -nw -nx -data-directory /home/yao.qi/SourceCode/gnu/build/gdb/testsuite/../data-directory^M
[Thread debugging using libthread_db enabled]^M
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".^M
^M
Breakpoint 1, gdb_main (args=args@entry=0x7fffffffdca0) at ../../binutils-gdb/gdb/main.c:1157^M
1157          captured_main (args);^M
(gdb) FAIL: gdb.gdb/observer.exp: run until breakpoint at captured_main

looks the test sets breakpoint on captured_main, and expects program
stops at captured_main.  However, program stops at the place where
captured_main is called, because captured_main is inlined,

 <1><8519e3>: Abbrev Number: 58 (DW_TAG_subprogram)
    <8519e4>   DW_AT_name        : (indirect string, offset: 0x880d3): captured_main
    <8519e8>   DW_AT_decl_file   : 1
    <8519e9>   DW_AT_decl_line   : 444
    <8519eb>   DW_AT_type        : <0x846e48>
    <8519ef>   DW_AT_inline      : 1    (inlined)
    <8519f0>   DW_AT_sibling     : <0x851c01>

The test passes if I build GDB with '-O0 -g3', because captured_main
isn't inlined.  This patch is to match the output when captured_main
is inlined.

gdb/testsuite:

2016-07-12  Yao Qi  <yao.qi@linaro.org>

	* lib/selftest-support.exp (selftest_setup): Match the output
	when captured_main is inlined.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix grammar in error message.
@ 2016-07-12 10:20 sergiodj+buildbot
  2016-07-12 10:34 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-07-12 10:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f231881ea65232b3f67379326a5b605c465dffc4 ***

Author: Douglas B Rupp <rupp@adacore.com>
Branch: master
Commit: f231881ea65232b3f67379326a5b605c465dffc4

Fix grammar in error message.

	* binary.c (binary_set_section_contents): Fix grammar in warning
	message.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix of default lookup for "this" symbol.
@ 2016-07-07 15:52 sergiodj+buildbot
  2016-07-07 16:01 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-07-07 15:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4f19a0e6b45c63c0b4afe27a19d144cca412d4ae ***

Author: Walfred Tedeschi <walfred.tedeschi@intel.com>
Branch: master
Commit: 4f19a0e6b45c63c0b4afe27a19d144cca412d4ae

Fix of default lookup for "this" symbol.

Using the default lookup for the symbol "this" might lead to segmentation
fault in GDB.
Some languages, e.g. Fortran, use as default lookup routine the C++
routines.
For those languages "this" can be the instance of a class or even the
definition of a class.
When an instance of a class having the name "this" is evaluated
in GDB a segmentation fault was observed.

As example of the issue take into consideration the Fortran code:
  type foo
    real :: a
    type(bar) :: x
    character*7 :: b
  end type foo
  type(foo) :: this

Issue appears when evaluating the variable "this" in GDB.

Within the language definition structure there is a field that represents
the name of the special symbol used for the C++ "this" for the language
being described.
The fix presented here takes into account the aforementioned field. In the
case the aforementioned field is NULL "this" is not represented in the
language described and the lookup should return a null_block_symbol.

Tests: Performed tests with gfortran and ifort.

Reviewed:
https://sourceware.org/ml/gdb-patches/2016-04/msg00068.html

After the commited patch:
https://sourceware.org/ml/gdb-patches/2016-06/msg00364.html
Patch can be applied.

2016-06-16  Walfred Tedeschi  <walfred.tedeschi@intel.com>

gdb/ChangeLog:

	* cp-namespace.c (cp_lookup_bare_symbol): Use language passed as
	parameter to look for the symbol "this".

gdb/testsuite/ChangeLog:

	* gdb.fortran/derived-types.exp (result_line, result_line_2):
	New variables.
	(print this%a, print this%b, print this): New tests.
	* gdb.fortran/derived-types.f90 (this): New object and
	initialization.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Remove extra output directory level for Ada tests
@ 2016-07-06 16:12 sergiodj+buildbot
  2016-07-06 17:56 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-07-06 16:12 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f0464b231f046b836e2ed721d764fa309f18eb39 ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: f0464b231f046b836e2ed721d764fa309f18eb39

Remove extra output directory level for Ada tests

The output of Ada tests create a layout where the test name
("formatted_ref" in this example) appears twice:

outputs
 gdb.ada
     formatted_ref
         formatted_ref
             b~formatted_ref.adb
             b~formatted_ref.ads
             b~formatted_ref.ali
             b~formatted_ref.o
             defs.ali
             defs.o
             formatted_ref
             formatted_ref.ali
             formatted_ref.o

This causes a problem when testing with the native-gdbserver board, when
the binary has the same name as the test.  When gdb_remote_download is
called to upload the compiled binary, the implementation for
native-gdbserver copies it in the standard output directory (in
outputs/gdb.ada/formatted_ref).  However, there is already a directory
named formatted_ref in there, so the copy fails and gdbserver isn't able
to load the binary.

This patch bypasses the problem by removing the extra directory level.
The compiled binary will already be in its final location in the
standard output directory, so the copy will effectively be a no-op.

gdb/testsuite/ChangeLog:

	* lib/ada.exp: Remove extra directory level in build directory.
	* gdb.ada/cond_lang.exp: Likewise.
	* gdb.ada/exec_changed.exp: Likewise.
	* gdb.ada/lang_switch.exp: Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Use 'ptid_t' instead of 'ptid' for fbsd_next_vfork_done's return type.
@ 2016-07-06 13:14 sergiodj+buildbot
  2016-07-06 13:27 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-07-06 13:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ee950322ca2c77494b1742f304632f667ed6ce79 ***

Author: John Baldwin <jhb@FreeBSD.org>
Branch: master
Commit: ee950322ca2c77494b1742f304632f667ed6ce79

Use 'ptid_t' instead of 'ptid' for fbsd_next_vfork_done's return type.

'ptid' compiles in C++, but not C.

gdb/ChangeLog:
	* fbsd-nat.c (fbsd_is_vfork_done_pending): Fix return type.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] babeltrace compilation regression
@ 2016-07-05  9:02 sergiodj+buildbot
  2016-07-05  9:16 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-07-05  9:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 13cdc2afb7873547ec2910ba647fb4a68602252f ***

Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Branch: master
Commit: 13cdc2afb7873547ec2910ba647fb4a68602252f

babeltrace compilation regression

Since:
	commit 2d681be471cf8aff8f296cb7713c39e9aa4fc2bb
	Author: Andreas Arnez <arnez@linux.vnet.ibm.com>
	Date:   Wed Apr 27 15:52:16 2016 +0200
	    Avoid non-C++-enabled babeltrace versions
tested with:
	libbabeltrace-devel-1.2.4-4.fc24.x86_64
	libbabeltrace-devel-1.4.0-2.fc25.x86_64
it can no longer build due to:
	configure:16435: gcc -o conftest -m64 -g3 -pipe -Wall -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -fno-diagno
stics-show-caret  -Werror  -static-libstdc++ -static-libgcc  conftest.c -ldl -ldl -lncurses -lm -ldl  -lbabeltrace -lbabeltrace-ctf >&5
	conftest.c: In function 'main':
	conftest.c:208:7: error: 'pos' is a pointer; did you mean to use '->'?

gdb/ChangeLog
2016-07-05  Jan Kratochvil  <jan.kratochvil@redhat.com>

	* configure: Regenerate.
	* configure.ac (HAVE_LIBBABELTRACE): Fix pos variable dereference.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Move fbsd_resume and related functions below fork following helper code.
@ 2016-07-01 18:19 sergiodj+buildbot
  2016-07-01 18:47 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-07-01 18:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8607ea632c806235554aa2336cf01bf3758c1264 ***

Author: John Baldwin <jhb@FreeBSD.org>
Branch: master
Commit: 8607ea632c806235554aa2336cf01bf3758c1264

Move fbsd_resume and related functions below fork following helper code.

gdb/ChangeLog:

	* fbsd-nat.c (super_resume): Move earlier next to "super_wait".
	(resume_one_thread_cb): Move below fork following helper code.
	(resume_all_threads_cb): Likewise.
	(fbsd_resume): Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix Thumb-2 BL detection
@ 2016-07-01 16:41 sergiodj+buildbot
  2016-07-01 17:00 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-07-01 16:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5e866f5aeeaf7514f5ca4f9eaba41594eac22e5b ***

Author: Thomas Preud'homme <thomas.preudhomme@arm.com>
Branch: master
Commit: 5e866f5aeeaf7514f5ca4f9eaba41594eac22e5b

Fix Thumb-2 BL detection

2016-07-01  Thomas Preud'homme  <thomas.preudhomme@arm.com>

bfd/
	* elf32-arm.c (using_thumb2_bl): New function.
	(arm_type_of_stub): Declare thumb2 variable together and change type
	to bfd_boolean.  Use using_thumb2_bl () to determine whether
	THM_MAX_FWD_BRANCH_OFFSET or THM2_MAX_FWD_BRANCH_OFFSET should be
	checked for BL range.
	(elf32_arm_final_link_relocate): Use using_thumb2_bl () to determine
	the bit size of BL offset.

ld/
	* testsuite/ld-arm/arm-elf.exp (Thumb-2 BL): Assemble for ARMv7.
	(Thumb-2 BL on ARMv6-M): New testcase.
	* testsuite/ld-arm/thumb2-bl.d: Do not try to match testcase filename.
	* testsuite/ld-arm/thumb2-bl.s: Do not select architecture.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Forget watchpoint locations when inferior exits or is killed/detached
@ 2016-07-01 11:56 sergiodj+buildbot
  2016-07-01 12:00 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-07-01 11:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 630008884535a5b26828325e48e729034c110536 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 630008884535a5b26828325e48e729034c110536

Forget watchpoint locations when inferior exits or is killed/detached

If you have two inferiors (or more), set watchpoints in one of the
inferiors, and then that inferior exits, until you manually delete the
watchpoint (or something forces a breakpoint re-set), you can't resume
the other inferior.

This is exercised by the test added by this commit.  Without the GDB
fix, this test fails like this:

 FAIL: gdb.multi/watchpoint-multi-exit.exp: dispose=kill: continue to marker in inferior 1
 FAIL: gdb.multi/watchpoint-multi-exit.exp: dispose=detach: continue to marker in inferior 1
 FAIL: gdb.multi/watchpoint-multi-exit.exp: dispose=exit: continue to marker in inferior 1

and gdb.log shows (in all three cases):

 (gdb) continue
 Continuing.
 Warning:
 Could not insert hardware watchpoint 2.
 Could not insert hardware breakpoints:
 You may have requested too many hardware breakpoints/watchpoints.

 Command aborted.
 (gdb) FAIL: gdb.multi/watchpoint-multi-exit.exp: dispose=kill: continue to marker in inferior 1

The problem is that GDB doesn't forget about the locations of
watchpoints set in the inferior that is now dead.  When we try to
continue the inferior that is still alive, we reach
insert_breakpoint_locations, which has the the loop that triggers the
error:

  /* If we failed to insert all locations of a watchpoint, remove
     them, as half-inserted watchpoint is of limited use.  */

That loop finds locations that are not marked inserted, but which
according to should_be_inserted should have been inserted, and so
errors out.

gdb/ChangeLog:
2016-07-01  Pedro Alves  <palves@redhat.com>

	* breakpoint.c (breakpoint_init_inferior): Discard watchpoint
	locations.
	* infcmd.c (detach_command): Call breakpoint_init_inferior.

gdb/testsuite/ChangeLog:
2016-07-01  Pedro Alves  <palves@redhat.com>

	* gdb.multi/watchpoint-multi-exit.c: New file.
	* gdb.multi/watchpoint-multi-exit.exp: New file.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] x86: allow suffix-less movzw and 64-bit movzb
@ 2016-07-01  8:42 sergiodj+buildbot
  2016-07-01  9:10 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-07-01  8:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c07315e0c610e0e3317b4c02266f81793df253d2 ***

Author: Jan Beulich <jbeulich@novell.com>
Branch: master
Commit: c07315e0c610e0e3317b4c02266f81793df253d2

x86: allow suffix-less movzw and 64-bit movzb

... just like is already the case for 16- and 32-bit movzb: I can't see
why omitting suffixes on this (and movs{b,w,l}) is not allowed, when it
is allowed for all other instructions where the suffix is redundant
with (one of) the operands.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix typo in comment
@ 2016-06-30 15:32 sergiodj+buildbot
  2016-06-30 15:43 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-06-30 15:32 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 838441e4a2a041e3a5dd26e886c67be22529502d ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 838441e4a2a041e3a5dd26e886c67be22529502d

Fix typo in comment

This patch fixes the typo "uf" in the comment.  I'll push it in as the
change is obvious.

2016-06-30  Yao Qi  <yao.qi@linaro.org>

	* arm-dis.c (print_insn): Fix typo in comment.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix PR python/20129 - use of non-existing variable
@ 2016-06-29 16:58 sergiodj+buildbot
  2016-06-29 17:48 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-06-29 16:58 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 803b47e5d4dc86b953aba0bc44865de287726dbe ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 803b47e5d4dc86b953aba0bc44865de287726dbe

Fix PR python/20129 - use of non-existing variable

PR python/20129 concerns the error message one gets from a command
like "disable frame-filter global NoSuchFilter".  Currently this
throws a second, unexpected, exception due to the use of a
non-existing variable named "name".

This patch adds regression tests and fixes a couple of spots to use
the correct variable name.

Built and regtested on x86-64 Fedora 23.

2016-06-29  Tom Tromey  <tom@tromey.com>

	PR python/20129:
	* python/lib/gdb/command/frame_filters.py (_do_enable_frame_filter)
	(SetFrameFilterPriority._set_filter_priority): Use "frame_filter",
	not "name".

2016-06-29  Tom Tromey  <tom@tromey.com>

	PR python/20129:
	* gdb.python/py-framefilter.exp: Add tests for setting priority
	and disabling of non-existent frame filter.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [AArch64] Use int64_t for address offset
@ 2016-06-28 17:17 sergiodj+buildbot
  2016-06-28 18:05 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-06-28 17:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2ac09a5bbbff78d363ede2f038c31a9b1cb0887b ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 2ac09a5bbbff78d363ede2f038c31a9b1cb0887b

[AArch64] Use int64_t for address offset

In AArch64 displaced stepping and fast tracepoint, GDB/GDBserver needs
to check whether the offset can fit in the range.  We are using int32_t
for offset, it is sufficient to get an offset from an instruction, but
it is not enough to get an offset from two addresses.  For example,
we have a BL in shared lib which is at 0x0000002000040774, and the
scratch pad for displaced stepping is at 0x400698.  The offset can't
fit in 28 bit imm.  However, since we are using int32_t for offset, GDB
thinks the offset can fit it, and generate the B instruction with wrong
offset.

It fixes the following fail,

-FAIL: gdb.base/dso2dso.exp: next over call to sub2

gdb:

2016-06-28  Yao Qi  <yao.qi@linaro.org>

	* aarch64-tdep.c (aarch64_displaced_step_b): Use int64_t for
	variable new_offset.

gdb/gdbserver:

2016-06-28  Yao Qi  <yao.qi@linaro.org>

	* linux-aarch64-low.c (aarch64_ftrace_insn_reloc_b): Use int64_t
	for variable new_offset.
	(aarch64_ftrace_insn_reloc_b_cond): Likewise.
	(aarch64_ftrace_insn_reloc_cb): Likewise.
	(aarch64_ftrace_insn_reloc_tb): Likewise.
	(aarch64_install_fast_tracepoint_jump_pad): Likewise.  Use
	PRIx64 instead of PRIx32.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix typo in previous commit
@ 2016-06-28 16:19 sergiodj+buildbot
  2016-06-28 17:04 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-06-28 16:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bb95c51a232dffb46067c402ac62f1f3303b6bbd ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: bb95c51a232dffb46067c402ac62f1f3303b6bbd

Fix typo in previous commit


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Remove parameter sysret from linux_target_ops.get_syscall_trapinfo
@ 2016-06-28 13:01 sergiodj+buildbot
  2016-06-28 13:25 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-06-28 13:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4cc32bec04aadc5c070d0f4aee656313a4854c11 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 4cc32bec04aadc5c070d0f4aee656313a4854c11

Remove parameter sysret from linux_target_ops.get_syscall_trapinfo

When I implement linux_target_ops.get_syscall_trapinfo for aarch64 and arm,
I find the second parameter sysret isn't used at all.  In RSP, we don't
need syscall return value either, because GDB can figure out the return
value from registers content got by 'g' packet.

This patch is to remove them.

gdb/gdbserver:

2016-06-28  Yao Qi  <yao.qi@linaro.org>

	* linux-low.c (get_syscall_trapinfo): Remove parameter sysret.
	Callers updated.
	* linux-low.h (struct linux_target_ops) <get_syscall_trapinfo>:
	Remove parameter sysno.
	* linux-x86-low.c (x86_get_syscall_trapinfo): Remove parameter
	sysret.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] MIPS16: Add R_MIPS16_PC16_S1 branch relocation support
@ 2016-06-28  0:55 sergiodj+buildbot
  2016-06-28  1:24 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-06-28  0:55 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c9775dde32773c57d4eb5dfb4265eda9cb8adbe8 ***

Author: Maciej W. Rozycki <macro@imgtec.com>
Branch: master
Commit: c9775dde32773c57d4eb5dfb4265eda9cb8adbe8

MIPS16: Add R_MIPS16_PC16_S1 branch relocation support

For R_MIPS16_PC16_S1 the calculation is `(sign_extend(A) + S - P) >> 1'
and the usual MIPS16 bit shuffling applies to relocated field handling,
as per the encoding of the branch target in the extended form of the
MIPS16 B, BEQZ, BNEZ, BTEQZ and BTNEZ instructions.

	include/
	* elf/mips.h (R_MIPS16_PC16_S1): New relocation.

	bfd/
	* elf32-mips.c (elf_mips16_howto_table_rel): Add
	R_MIPS16_PC16_S1.
	(mips16_reloc_map): Likewise.
	* elf64-mips.c (mips16_elf64_howto_table_rel): Likewise.
	(mips16_elf64_howto_table_rela): Likewise.
	(mips16_reloc_map): Likewise.
	* elfn32-mips.c (elf_mips16_howto_table_rel): Likewise.
	(elf_mips16_howto_table_rela): Likewise.
	(mips16_reloc_map): Likewise.
	* elfxx-mips.c (mips16_branch_reloc_p): New function.
	(mips16_reloc_p): Handle R_MIPS16_PC16_S1.
	(b_reloc_p): Likewise.
	(mips_elf_calculate_relocation): Likewise.
	(_bfd_mips_elf_check_relocs): Likewise.
	* reloc.c (BFD_RELOC_MIPS16_16_PCREL_S1): New relocation.
	* bfd-in2.h: Regenerate.
	* libbfd.h: Regenerate.

	gas/
	* config/tc-mips.c (mips16_reloc_p): Handle
	BFD_RELOC_MIPS16_16_PCREL_S1.
	(b_reloc_p): Likewise.
	(limited_pcrel_reloc_p): Likewise.
	(md_pcrel_from): Likewise.
	(md_apply_fix): Likewise.
	(tc_gen_reloc): Likewise.
	(md_convert_frag): Likewise.
	(mips_fix_adjustable): Update comment.
	* testsuite/gas/mips/mips16-branch-reloc-2.d: Remove error
	output, add dump patterns.
	* testsuite/gas/mips/mips16-branch-reloc-3.d: Remove error
	output, add dump patterns.
	* testsuite/gas/mips/mips16-branch-addend-2.d: Remove error
	output, add dump patterns.
	* testsuite/gas/mips/mips16-branch-addend-3.d: Remove error
	output, add dump patterns.
	* testsuite/gas/mips/mips16-branch-absolute.d: Remove error
	output, add dump patterns.
	* testsuite/gas/mips/mips16-branch-reloc-2.l: Remove file.
	* testsuite/gas/mips/mips16-branch-reloc-3.l: Remove file.
	* testsuite/gas/mips/mips16-branch-addend-2.l: Remove file.
	* testsuite/gas/mips/mips16-branch-addend-3.l: Remove file.
	* testsuite/gas/mips/mips16-branch-absolute.l: Remove file.
	* testsuite/gas/mips/mips16-branch-addend-2.s: Add padding.
	* testsuite/gas/mips/branch-weak.s: Adjust alignment, avoid
	implicit instruction padding, avoid MIPS16 JR->JRC conversion.
	* testsuite/gas/mips/branch-weak-6.d: New test.
	* testsuite/gas/mips/branch-weak-7.d: New test.
	* testsuite/gas/mips/mips.exp: Run the new tests.

	ld/
	* testsuite/ld-mips-elf/mips16-branch-2.d: New test.
	* testsuite/ld-mips-elf/mips16-branch-3.d: New test.
	* testsuite/ld-mips-elf/mips16-branch-addend-2.d: New test.
	* testsuite/ld-mips-elf/mips16-branch-addend-3.d: New test.
	* testsuite/ld-mips-elf/mips16-branch.s: New test source.
	* testsuite/ld-mips-elf/mips-elf.exp: Run the new tests.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix use of a dangling pointer for Python breakpoint objects
@ 2016-06-27 10:42 sergiodj+buildbot
  2016-06-27 11:30 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-06-27 10:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f4952523968703caa027a5922263eb97b88bedc3 ***

Author: Pierre-Marie de Rodat <derodat@adacore.com>
Branch: master
Commit: f4952523968703caa027a5922263eb97b88bedc3

Fix use of a dangling pointer for Python breakpoint objects

When a Python script tries to create a breakpoint but fails to do so,
gdb.Breakpoint.__init__ raises an exception and the breakpoint does not
exist anymore in the Python interpreter. However, GDB still keeps a
reference to the Python object to be used for a later hook, which is
wrong.

This commit adds the necessary cleanup code so that there is no stale
reference to this Python object. It also adds a new testcase to
reproduce the bug and check the fix.

2016-06-25  Pierre-Marie de Rodat  <derodat@adacore.com>

gdb/
	* python/py-breakpoint.c (bppy_init): Clear bppy_pending_object
	when there is an error during the breakpoint creation.

gdb/testsuite

	* gdb.python/py-breakpoint-create-fail.c,
	gdb.python/py-breakpoint-create-fail.exp,
	gdb.python/py-breakpoint-create-fail.py: New testcase.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] remove a few sentinals
@ 2016-06-25 16:48 sergiodj+buildbot
  2016-06-25 17:07 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-06-25 16:48 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5703197e0421f490c3dc25ecd9ea04ca59750b64 ***

Author: Trevor Saunders <tbsaunde+binutils@tbsaunde.org>
Branch: master
Commit: 5703197e0421f490c3dc25ecd9ea04ca59750b64

remove a few sentinals

gas/ChangeLog:

2016-06-25  Trevor Saunders  <tbsaunde+binutils@tbsaunde.org>

	* config/tc-bfin.c (bfin_cpus): Remove sentinal.
	(md_parse_option): Adjust.
	* config/tc-aarch64.c (aarch64_parse_abi): Replace use of a sentinal
	with iteration from 0 to ARRAY_SIZE.
	* config/tc-mcore.c (md_begin): Likewise.
	* config/tc-visium.c (visium_parse_arch): Likewise.

opcodes/ChangeLog:

2016-06-25  Trevor Saunders  <tbsaunde+binutils@tbsaunde.org>

	* mcore-opc.h: Remove sentinal.
	* mcore-dis.c (print_insn_mcore): Adjust.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Add a gdbarch 'print_auxv_entry' method for FreeBSD ABIs.
@ 2016-06-24 22:59 sergiodj+buildbot
  2016-06-24 22:53 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-06-24 22:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 82372b2f2747d347e24bb10ddc7bc7e828222a42 ***

Author: John Baldwin <jhb@FreeBSD.org>
Branch: master
Commit: 82372b2f2747d347e24bb10ddc7bc7e828222a42

Add a gdbarch 'print_auxv_entry' method for FreeBSD ABIs.

Add a 'print_auxv_entry' method for FreeBSD ABIs that parses
FreeBSD-specific auxiliary vector entries and outputs a suitable
description using fprint_auxv_entry.

gdb/ChangeLog:

	* fbsd-tdep.c: Include "auxv.h".
	(fbsd_print_auxv_entry): New function.
	(fbsd_init_abi): Install gdbarch "print_auxv_entry" method.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Create a pseudo section for the ELF AUXV core dump note on FreeBSD.
@ 2016-06-24 20:19 sergiodj+buildbot
  2016-06-24 21:08 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-06-24 20:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3350c5f5de3d2e62dd9de2a76cf2d5d8728d2600 ***

Author: John Baldwin <jhb@FreeBSD.org>
Branch: master
Commit: 3350c5f5de3d2e62dd9de2a76cf2d5d8728d2600

Create a pseudo section for the ELF AUXV core dump note on FreeBSD.

The procstat AUXV core dump note in FreeBSD consists of 32-bit integer
followed by an array of auxiliary vector entries.

bfd/ChangeLog:

	* elf.c (elfcore_grok_freebsd_note): Handle NT_FREEBSD_PROCSTAT_AUXV
	notes.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Move logic out of symbol_find_demangled_name
@ 2016-06-24  6:09 sergiodj+buildbot
  2016-06-24  6:20 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-06-24  6:09 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8b302db80cb07f5f3264b50e1b51fdb8ecb29183 ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 8b302db80cb07f5f3264b50e1b51fdb8ecb29183

Move logic out of symbol_find_demangled_name

This patch moves most of the demangling logic out of
symbol_find_demangled_name into the various language_defn objects.

The simplest way to do this seemed to be to add a new method to
language_defn.  This is shame given the existing la_demangle, but
given Ada's unusual needs, and the differing demangling options
between languages, la_demangle didn't seem to fit.

In order to make this work, I made enum language order-sensitive.
This helps preserve the current ordering of demangling operations.

2016-06-23  Tom Tromey  <tom@tromey.com>

	* symtab.c (symbol_find_demangled_name): Loop over languages and
	use language_sniff_from_mangled_name.
	* rust-lang.c (rust_sniff_from_mangled_name): New function.
	(rust_language_defn): Update.
	* p-lang.c (pascal_language_defn): Update.
	* opencl-lang.c (opencl_language_defn): Update.
	* objc-lang.c (objc_sniff_from_mangled_name): New function.
	(objc_language_defn): Update.
	* m2-lang.c (m2_language_defn): Update.
	* language.h (struct language_defn) <la_sniff_from_mangled_name>: New
	field.
	(language_sniff_from_mangled_name): Declare.
	* language.c (language_sniff_from_mangled_name): New function.
	(unknown_language_defn, auto_language_defn, local_language_defn):
	Update.
	* jv-lang.c (java_sniff_from_mangled_name): New function.
	(java_language_defn): Use it.
	* go-lang.c (go_sniff_from_mangled_name): New function.
	(go_language_defn): Use it.
	* f-lang.c (f_language_defn): Update.
	* defs.h (enum language): Reorder.
	* d-lang.c (d_sniff_from_mangled_name): New function.
	(d_language_defn): Use it.
	* cp-support.h (gdb_sniff_from_mangled_name): Declare.
	* cp-support.c (gdb_sniff_from_mangled_name): New function.
	* c-lang.c (c_language_defn, cplus_language_defn)
	(asm_language_defn, minimal_language_defn): Update.
	* ada-lang.c (ada_sniff_from_mangled_name): New function.
	(ada_language_defn): Use it.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Add support for yet some more new ISA 3.0 instructions.
@ 2016-06-22 23:12 sergiodj+buildbot
  2016-06-24  1:10 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-06-22 23:12 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6fd3a02da5548c71ff469f978444ef6c3af18783 ***

Author: Peter Bergner <bergner@vnet.ibm.com>
Branch: master
Commit: 6fd3a02da5548c71ff469f978444ef6c3af18783

Add support for yet some more new ISA 3.0 instructions.

opcodes/
	* ppc-opc.c (RM, DRM, VXASH, VXASH_MASK, XMMF, XMMF_MASK): New defines.
	(powerpc_opcodes) <brd, brh, brw, mffsce, mffscdrn, mffscdrni,
	mffscrn, mffscrni, mffsl, nandxor, rldixor, setbool,
	xor3>: New mnemonics.
	<setb>: Change to a VX form instruction.
	(insert_sh6): Add support for rldixor.
	(extract_sh6): Likewise.

gas/
	* testsuite/gas/ppc/power9.d <brd, brh, brw, mffs, mffs., mffsce,
	mffscdrn, mffscdrni, mffscrn, mffscrni, mffsl, nandxor, rldixor,
	setbool, xor3>: New tests.
	* testsuite/gas/ppc/power9.s: Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] tilegx: move TILEGX_NUM_PIPELINE_ENCODINGS to tilegx_pipeline enum
@ 2016-06-22  9:22 sergiodj+buildbot
  2016-06-23 22:49 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-06-22  9:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6edaf4d75b45ff08d7296095506904663b8f0576 ***

Author: Trevor Saunders <tbsaunde+binutils@tbsaunde.org>
Branch: master
Commit: 6edaf4d75b45ff08d7296095506904663b8f0576

tilegx: move TILEGX_NUM_PIPELINE_ENCODINGS to tilegx_pipeline enum

Its closely related to what the encodings are, more than a set of random
constants, so it seems to make sense to put it here.

include/ChangeLog:

2016-06-22  Trevor Saunders  <tbsaunde+binutils@tbsaunde.org>

	* opcode/tilegx.h: Move TILEGX_NUM_PIPELINE_ENCODINGS into
	tilegx_pipeline.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Arc assembler: Convert nps400 from a machine type to an extension.
@ 2016-06-22  3:18 sergiodj+buildbot
  2016-06-23 20:02 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-06-22  3:18 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bdd582dbf14f12998a0003b5aa772d7868bc3dc7 ***

Author: Graham Markall <graham.markall@embecosm.com>
Branch: master
Commit: bdd582dbf14f12998a0003b5aa772d7868bc3dc7

Arc assembler: Convert nps400 from a machine type to an extension.

gas	* config/tc-arc.c (check_cpu_feature, md_parse_option):
	Add nps400 option and feature. Add check for nps400
	feature. Refactor existing checks to check subclass before
	feature enablement.
	(md_show_usage): Document flags for NPS-400 and add some other
	undocumented flags.
	(cpu_type): Remove nps400 CPU type entry
	(check_zol): Remove bfd_mach_arc_nps400 case.
	(md_show_usage): Add help on -mcpu=nps400.
	(cpu_types): Add entry for nps400 as arc700 plus nps400 extension
	set.
	* doc/c-arc.texi: Document the -mnps400, -mspfp, -mdpfp, and
	-fpuda flags.  Document -mcpu=nps400.
	* testsuite/gas/arc/nps-400-0.d: Use -mcpu=arc700 -mnps400. Change
	expected flags to match ARC700 instead of NPS400.
	* testsuite/gas/arc/nps-400-1.d: Use -mcpu=arc700 -mnps400.
	* testsuite/gas/arc/nps-400-2.d: Likewise.
	* testsuite/gas/arc/nps-400-3.d: Likewise.
	* testsuite/gas/arc/nps-400-4.d: Likewise.
	* testsuite/gas/arc/nps-400-5.d: Likewise.
	* testsuite/gas/arc/nps-400-6.d: Likewise.
	* testsuite/gas/arc/nps-400-7.d: Likewise.
	* testsuite/gas/arc/textinsn2op01.s: Change opcode of myinsn to
	avoid clash with cbba instruction.
	* testsuite/gas/arc/textinsn2op01.d: Likewise.
	* testsuite/gas/arc/textinsn3op.d: Likewise.
	* testsuite/gas/arc/textinsn3op.s: Likewise.
	* testsuite/gas/arc/nps-400-0.d: Test using NPS-400 using
	-mcpu=nps400 as an alternative to -mcpu=arc700 -mnps400 flags.

binutils* readelf.c (decode_ARC_machine_flags): Remove E_ARC_MACH_NPS400
	case.

ld	* testsuite/ld-arc/nps-1a.d: Use -mcpu=arc700 -mnps400.
	* testsuite/ld-arc/nps-1b.d: Likewise.

include	* opcode/arc.h: Add nps400 extension and instruction
	subclass.
	Remove ARC_OPCODE_NPS400
	* elf/arc.h: Remove E_ARC_MACH_NPS400

opcodes	* arc-dis.c (arc_insn_length): Add comment on instruction length.
	Use same method for determining	instruction length on ARC700 and
	NPS-400.
	(arc_insn_length, print_insn_arc): Remove bfd_mach_arc_nps400.
	* arc-nps400-tbl.h: Make all nps400 instructions ARC700 instructions
	with the NPS400 subclass.
	* arc-opc.c: Likewise.

bfd	* archures.c: Remove bfd_mach_arc_nps400.
	* bfd-in2.h: Likewise.
	* cpu-arc.c (arch_info_struct): Likewise.
	* elf32-arc.c (arc_elf_object_p, arc_elf_final_write_processing):
	Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Add "new-ui console" tests
@ 2016-06-21 23:24 sergiodj+buildbot
  2016-06-23 17:22 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-06-21 23:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ac69f7863a6b5dbd1792356275de437371b8c879 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: ac69f7863a6b5dbd1792356275de437371b8c879

Add "new-ui console" tests

This adds a test that uses new-ui to create a secondary console, and
then runs some basic smoke tests.  It ensures that:

 - synchronous commands send output to the UI that initiated it

 - asynchronous events like breakpoint hits are reported on all
   consoles.

 - "new-ui" without arguments doesn't crash.

 - The "new-ui" command doesn't repeat.

gdb/testsuite/ChangeLog:
2016-06-21  Pedro Alves  <palves@redhat.com>

	* gdb.base/new-ui.exp: New file.
	* lib/mi-support.exp (switch_gdb_spawn_id): Move to ...
	* lib/gdb.exp (switch_gdb_spawn_id): ... here.
	(with_spawn_id): New procedure.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Always switch fork child to the main UI
@ 2016-06-21 22:18 sergiodj+buildbot
  2016-06-23 15:46 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-06-21 22:18 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 49940788ab38b9d58c663cf38855f29c0ebb1b55 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 49940788ab38b9d58c663cf38855f29c0ebb1b55

Always switch fork child to the main UI

The following scenario:

 - gdb started in normal CLI mode.

 - separate MI channel created with new-ui

 - inferior output redirected with the "set inferior-tty" command.

 - use -exec-run in the MI channel to run the inferior

is presently mishandled.

When we create the inferior, in fork-child.c, right after vfork, we'll
close all the file descriptors in the vfork child, and then dup the
tty to file descriptors 0/1/2, create a session, etc.  Note that when
we close all descriptors, we close the file descriptors behind
gdb_stdin/gdb_stdout/gdb_stderr of all secondary UIs...  So if
anything goes wrong in the child and it calls warning/error, it'll end
up writting to the current UI's stdout/stderr streams, which are
backed by file descriptors that have since been closed.  Because this
happens in a vfork region, the corresponding stdin/stdout/stderr in
the parent/gdb end up corrupted.

The fix is to switch to the main UI right after the vfork, so that
gdb_stdin/gdb_stdout/gdb_stderr are correctly mapped to
stdin/stdout/stderr (and thus to file descriptors 0/1/2), so this code
works as it has always worked.

(Technically, we're doing a lot of stuff we shouldn't be doing after a
vfork, while we should only be calling async-signal-safe functions.)

gdb/ChangeLog:
2016-06-21  Pedro Alves  <palves@redhat.com>

	* fork-child.c (fork_inferior): Switch the child to the main UI
	right after vfork.  Save/restore the current UI in the parent.
	Flush outputs of the main UI instead of the current UI.

gdb/testsuite/ChangeLog:
2016-06-21  Pedro Alves  <palves@redhat.com>

	* gdb.mi/mi-exec-run.exp: New file.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Make mi-break.exp always expect breakpoint commands output on the main UI
@ 2016-06-21 21:40 sergiodj+buildbot
  2016-06-23 14:02 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-06-21 21:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ef274d26b57336b3baa5bb0ae93b49178bc45631 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: ef274d26b57336b3baa5bb0ae93b49178bc45631

Make mi-break.exp always expect breakpoint commands output on the main UI

mi-break.exp regresses when tested with MI running on a secondary UI,
with RUNTESTFLAGS="FORCE_SEPARATE_MI_TTY=1".

The problem is simply that the test sets a breakpoint, and attaches
"print" commands to the breakpoint.  Since breakpoint commands always
run with the main UI as current UI, the breakpoint command's output
goes to the main UI.  So we need to tweak the test to expect it there.

gdb/testsuite/ChangeLog:
2016-06-21  Pedro Alves  <palves@redhat.com>

	* gdb.mi/mi-break.exp (test_breakpoint_commands): Always expect
	breakpoint command's output on the main UI.
	(test_break): New procedure, factored out from calls in the top
	level.
	(top level): Use foreach_with_prefix to test MI as main UI and as
	separate UI.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Add new command to create extra console/mi UIs
@ 2016-06-21 18:51 sergiodj+buildbot
  2016-06-22 22:59 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-06-21 18:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 60eb5395fa7a7b8e3cd1841e38b6d1a0c16be0d0 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 60eb5395fa7a7b8e3cd1841e38b6d1a0c16be0d0

Add new command to create extra console/mi UIs

With all the previous plumbing in place, it's now easy to add a
command that actually creates a new console/mi UI.

The intended use case is to make it possible and easy for MI frontends
to provide a fully featured GDB console to users, with readline
support, command line editing, history, etc., just like if gdb was
started on the command line.  Currently MI frontends have to try to
implement all of that theirselves and make use of "-interpreter-exec
console ...", which is far from perfect.  If you ever tried Eclipse's
gdb console window, you'll know what I mean...

Instead of trying to multiplex console through MI, this command let's
just leverage all the built in readline/editing support already inside
gdb.

The plan is for the MI frontend to start GDB in regular console mode,
running inside a terminal emulator widget embedded in Eclipse (which
already exists, for supporting the shell widget; other frontends have
similar widgets), and then tell GDB to run a full MI interpreter on an
specified input/output device, independent of the console.

My original prototype planned to do things the other way around --
start GDB in MI mode, and then start an extra CLI console on separate
tty.  I handed over that prototype to Marc Khouzam @ Eclipse CDT, and
after experimentation and discussion, we ended up concluding that
starting GDB in CLI mode instead was both easier and actually also
supported an interesting use case -- connect an Eclipse frontend to a
GDB that is already running outside Eclipse.

The current usage is "new-ui <interpreter> <tty>".

E.g., on a terminal run this scriplet:

 $ cat gdb-client
 #!/bin/bash

 reset
 tty
 tail -f /dev/null

 $ gdb-client
 /dev/pts/15

Now run gdb on another terminal, and tell it to start a MI interpreter
on the tty of the other terminal:

 ...
 (gdb) new-ui mi /dev/pts/15
 New UI allocated

Now back to the the gdb-client terminal, we'll get an MI prompt, ready
for MI input:

 /dev/pts/15
 =thread-group-added,id="i1"
 (gdb)

You can also start a new UI running a CLI, with:

 (gdb) new-ui console /dev/pts/15

Though note that this console won't support readline command editing.
It works as if "set editing off" was entered.

gdb/ChangeLog:
2016-06-21  Pedro Alves  <palves@redhat.com>

	* interps.c (set_top_level_interpreter): New function, factored
	out from captured_main.
	(interpreter_completer): Make extern.
	* interps.h (set_top_level_interpreter, interpreter_completer):
	New declarations.
	(captured_main): Use set_top_level_interpreter.
	* top.c [!O_NOCTTY] (O_NOCTTY): Define as 0.
	(open_terminal_stream, new_ui_command): New functions.
	(init_main): Install the "new-ui" command.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Make stdin be per UI
@ 2016-06-21 18:04 sergiodj+buildbot
  2016-06-22 22:04 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-06-21 18:04 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 268a799a454ce862f516ff2215290fae08eca7fa ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 268a799a454ce862f516ff2215290fae08eca7fa

Make stdin be per UI

This commit makes each UI have its own "stdin" stream pointer.  This
is used to determine whether the "from_tty" argument to
execute_command, etc. should be true.

Related, this commit makes input_from_terminal_p take an UI parameter,
and then avoids the gdb_has_a_terminal in it.  gdb_has_a_terminal only
returns info on gdb's own main/primary terminal (the real stdin).
However, the places that call input_from_terminal_p really want to
know is whether the command came from an interactive tty.  This patch
thus renames input_from_terminal_p to input_interactive_p for clarity,
and then makes input_interactive_p check for "set interactive" itself,
along with ISATTY, instead of calling gdb_has_a_terminal.  Actually,
quit_force wants to call input_interactive_p _after_ stdin is closed,
we can't call ISATTY that late.  So instead we save the result of
ISATTY in a field of the UI.

gdb/ChangeLog:
2016-06-21  Pedro Alves  <palves@redhat.com>

	* cli/cli-script.c (read_next_line): Adjust to per-UI stdin.
	(read_command_lines): Use input_interactive_p instead of
	input_from_terminal_p.
	* defs.h (struct ui): Forward declare.
	(input_from_terminal_p): Rename to ...
	(input_interactive_p): ... this.
	* event-top.c (stdin_event_handler): Pass 0 as from_tty argument
	to quit_command.
	(command_handler): Adjust to per-UI stdin.
	(handle_line_of_input): Adjust to per-UI stdin and use
	input_interactive_p instead of ISATTY and input_from_terminal_p.
	(gdb_readline_no_editing_callback): Adjust to per-UI stdin.
	(command_line_handler): Always pass true as "from_tty" parameter
	of handle_line_of_input and execute_command.
	(async_sigterm_handler): Pass 0 as from_tty argument to
	quit_command.
	* inflow.c (interactive_mode, show_interactive_mode): Moved to ...
	(gdb_has_a_terminal): Don't check interactive_mode here.
	(_initialize_inflow): Don't install "set interactive-mode" here.
	* main.c (captured_command_loop): Adjust to per-UI stdin.
	* mi/mi-interp.c (mi_execute_command_wrapper): Adjust to per-UI
	stdin.
	* top.c (new_ui): Save the stdin stream and whether it's a tty.
	(dont_repeat): Adjust to per-UI stdin.
	(command_line_input): Adjust to per-UI stdin and to use
	input_interactive_p.
	(quit_force): Write history if any UI supports interactive input.
	(interactive_mode, show_interactive_mode): Move here, from
	inflow.c.
	(input_from_terminal_p): Rename to ...
	(input_interactive_p): ... this, and check the "interactive_mode"
	global instead of calling gdb_has_a_terminal.
	(_initialize_top): Install "set interactive-mode" here.
	* top.h (struct ui) <stdin_stream, input_interactive_p>: New
	fields.
	* utils.c (quit): Pass 0 as from_tty argument to quit_force.
	(defaulted_query): Adjust to per-UI stdin and to use
	input_interactive_p.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Push thread->control.command_interp to the struct thread_fsm
@ 2016-06-21 15:18 sergiodj+buildbot
  2016-06-22  9:09 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-06-21 15:18 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8980e177bb62ec64875b335cf8733b41f3aae2fd ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 8980e177bb62ec64875b335cf8733b41f3aae2fd

Push thread->control.command_interp to the struct thread_fsm

I noticed that if we step into an inline function, step_1 never
reaches proceed, and thus nevers sets the thread's
tp->control.command_interp.  Because of that,
should_print_stop_to_console fails to determine that is should print
stop output to the console.

The fix is to set the thread's command_interp earlier.  However, I
realized that we can move that field to the thread_fsm, given that its
lifetime is exactly the same as thread_fsm.  So the patch plumbs all
fsms constructors to take the command interp and store it in the
thread_fsm.

We can see the fix in action, with e.g., the gdb.opt/inline-cmds.exp
test, and issuing a step when stopped at line 67:

 &"s\n"
 ^running
 *running,thread-id="all"
 (gdb)
 ~"67\t  result = func2 ();\n"
 *stopped,reason="end-stepping-range",frame={addr="0x00000000004004d0",func="main",args=[],file="/home/pedro/gdb/mygit/src/gdb/testsuite/gdb.opt/inline-cmds.c",fullname="/home/pedro/gdb/mygit/src/gdb/testsuite/gdb.opt/inline-cmds.c",line="67"},thread-id="1",stopped-threads="all",core="0"
 (gdb)
 s
 &"s\n"
 ^running
 *running,thread-id="all"
 (gdb)
+ ~"func2 () at /home/pedro/gdb/mygit/src/gdb/testsuite/gdb.opt/inline-cmds.c:67\n"
+ ~"67\t  result = func2 ();\n"
 *stopped,reason="end-stepping-range",frame={addr="0x00000000004004d0",func="func2",args=[],file="/home/pedro/gdb/mygit/src/gdb/testsuite/gdb.opt/inline-cmds.c",fullname="/home/pedro/gdb/mygit/src/gdb/testsuite/gdb.opt/inline-cmds.c",line="67"},thread-id="1",stopped-threads="all",core="0"
 (gdb)

(The inline-cmds.exp command is adjusted to exercise this.)

(Due to the follow_fork change, this also fixes "next N" across a fork
with "set follow-fork child" with "set detach-on-fork on".  Commands
that rely on internal breakpoints, like "finish" will still require
more work to migrate breakpoints etc. to the child thread.)

gdb/ChangeLog:
2016-06-21  Pedro Alves  <palves@redhat.com>

	* breakpoint.c (new_until_break_fsm): Add 'cmd_interp' parameter.
	(until_break_fsm_should_stop, until_break_fsm_clean_up): Add
	thread parameter.
	(until_break_command): Pass command interpreter to thread fsm
	ctor.
	* cli/cli-interp.c (should_print_stop_to_console): Adjust.
	* gdbthread.h (struct thread_control_state) <command_interp>:
	Delete field.
	* infcall.c (new_call_thread_fsm): Add 'cmd_interp' parameter.
	Pass it down.
	(call_thread_fsm_should_stop): Add thread parameter.
	(call_function_by_hand_dummy): Pass command interpreter to thread
	fsm ctor.  Pass thread pointer to fsm clean up method.
	* infcmd.c: Include interps.h.
	(struct step_command_fsm) <thread>: Delete field.
	(new_step_command_fsm): Add 'cmd_interp' parameter.  Pass it down.
	(step_command_fsm_prepare): Remove references to fsm's thread
	field.
	(step_1): Pass command interpreter to thread
	fsm ctor.  Pass thread pointer to fsm clean up method.
	(step_command_fsm_should_stop, step_command_fsm_clean_up): Add
	thread parameter and use it.
	(new_until_next_fsm): Add 'cmd_interp' parameter.  Pass it down.
	(until_next_fsm_should_stop, until_next_fsm_clean_up): Add thread
	parameter and use it.
	(until_next_command): Pass command interpreter to thread fsm ctor.
	(struct finish_command_fsm) <thread>: Delete field.
	(finish_command_fsm_ops): Add NULL slot for should_notify_stop.
	(new_finish_command_fsm): Add 'cmd_interp' parameter and pass it
	down.  Remove thread parameter and adjust.
	(finish_command_fsm_should_stop, finish_command_fsm_clean_up): Add
	thread parameter and use it.
	(finish_command): Pass command interpreter to thread fsm ctor.
	Don't pass thread.
	* infrun.c (follow_fork): Move thread fsm to child fork instead of
	command interpreter, only.
	(clear_proceed_status_thread): Remove reference to command_interp.
	(proceed): Don't record the thread's command interpreter.
	(clean_up_just_stopped_threads_fsms): Pass thread to fsm clean_up
	method.
	(fetch_inferior_event): Pass thread to fsm should_stop method.
	* thread-fsm.c (thread_fsm_ctor): Add 'cmd_interp' parameter.
	Store it.
	(thread_fsm_clean_up, thread_fsm_should_stop): Add thread
	parameter and pass it down.
	* thread-fsm.h (struct thread_fsm) <command_interp>: New field.
	(struct thread_fsm_ops) <clean_up, should_stop>: Add thread
	parameter.
	(thread_fsm_ctor): Add 'cmd_interp' parameter.
	(thread_fsm_clean_up, thread_fsm_should_stop): Add thread
	parameter.
	* thread.c (thread_cancel_execution_command): Pass thread to
	thread fsm clean_up method.

gdb/testsuite/ChangeLog:
2016-06-21  Pedro Alves  <palves@redhat.com>

	* gdb.opt/inline-cmds.c: Add "set mi break here" marker.
	* gdb.opt/inline-cmds.exp: Add MI tests.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Replace the sync_execution global with a new enum prompt_state tristate
@ 2016-06-21 13:19 sergiodj+buildbot
  2016-06-21 21:31 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-06-21 13:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3b12939dfc2399200f243851fd55d0e392b64165 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 3b12939dfc2399200f243851fd55d0e392b64165

Replace the sync_execution global with a new enum prompt_state tristate

When sync_execution (a boolean) is true, it means we're running a
foreground command -- we hide the prompt stop listening to input, give
the inferior the terminal, then go to the event loop waiting for the
target to stop.

With multiple independent UIs, we need to track whether each UI is
synchronously blocked waiting for the target.  IOW, if you do
"continue" in one console, that console stops accepting commands, but
you should still be free to type other commands in the others
consoles.

Just simply making sync_execution be per-UI alone not sufficient,
because of this in fetch_inferior_event:

  /* If the inferior was in sync execution mode, and now isn't,
     restore the prompt (a synchronous execution command has finished,
     and we're ready for input).  */
  if (current_ui->async && was_sync && !sync_execution)
    observer_notify_sync_execution_done ();

We'd have to record at entry the "was_sync" state for each UI, not
just of the current UI.

This patch instead replaces the sync_execution flag by a per-UI
tristate flag indicating the command line prompt state:

 enum prompt_state
 {
   /* The command line is blocked simulating synchronous execution.
      This is used to implement the foreground execution commands
      ('run', 'continue', etc.).  We won't display the prompt and
      accept further commands until the execution is actually over.  */
   PROMPT_BLOCKED,

   /* The command finished; display the prompt before returning back to
      the top level.  */
   PROMPT_NEEDED,

   /* We've displayed the prompt already, ready for input.  */
   PROMPTED,
 ;

I think the end result is _much_ clearer than the current code, and,
it addresses the original motivation too.

gdb/ChangeLog:
2016-06-21  Pedro Alves  <palves@redhat.com>

	* annotate.c: Include top.h.
	(async_background_execution_p): Delete.
	(print_value_flags): Check the UI's prompt state rather then
	async_background_execution_p.
	* event-loop.c (start_event_loop): Set the prompt state to
	PROMPT_NEEDED.
	* event-top.c (display_gdb_prompt, async_enable_stdin)
	(async_disable_stdin): Check the current UI's prompt state instead
	of the sync_execution global.
	(command_line_handler): Set the prompt state to PROMPT_NEEDED
	before running a command, and display the prompt if still needed
	afterwards.
	* infcall.c (struct call_thread_fsm) <waiting_ui>: New field.
	(new_call_thread_fsm): New parameter 'waiting_ui'.  Store it.
	(call_thread_fsm_should_stop): Set the prompt state to
	PROMPT_NEEDED.
	(run_inferior_call): Adjust to temporarily set the prompt state to
	PROMPT_BLOCKED instead of using the sync_execution global.
	(call_function_by_hand_dummy): Pass the current UI to
	new_call_thread_fsm.
	* infcmd.c: Include top.h.
	(continue_1): Check the current UI's prompt state instead of the
	sync_execution global.
	(continue_command): Validate global execution state before calling
	prepare_execution_command.
	(step_1): Call all_uis_check_sync_execution_done.
	(attach_post_wait): Don't call async_enable_stdin here.  Remove
	reference to sync_execution.
	* infrun.c (sync_execution): Delete global.
	(follow_fork_inferior)
	(reinstall_readline_callback_handler_cleanup): Check the current
	UI's prompt state instead of the sync_execution global.
	(check_curr_ui_sync_execution_done)
	(all_uis_check_sync_execution_done): New functions.
	(fetch_inferior_event): Call all_uis_check_sync_execution_done
	instead of trying to determine whether the global sync execution
	changed.
	(handle_no_resumed): Check the prompt state of all UIs.
	(normal_stop): Emit the no unwait-for even to all PROMPT_BLOCKED
	UIs.  Emit the "Switching to" notification to all UIs.  Enable
	stdin in all UIs.
	* infrun.h (sync_execution): Delete.
	(all_uis_check_sync_execution_done): Declare.
	* main.c (captured_command_loop): Don't call
	interp_pre_command_loop if the prompt is blocked.
	(catch_command_errors, catch_command_errors_const): Adjust.
	(captured_main): Set the initial prompt state to PROMPT_NEEDED.
	* mi/mi-interp.c (display_mi_prompt): Set the prompt state to
	PROMPTED.
	(mi_interpreter_resume): Don't clear sync_execution.  Remove hack
	comment.
	(mi_execute_command_input_handler): Set the prompt state to
	PROMPT_NEEDED before executing the command, and only display the
	prompt if the prompt state is PROMPT_NEEDED afterwards.
	(mi_on_resume_1): Adjust to check the prompt state.
	* target.c (target_terminal_inferior): Adjust to check the prompt
	state.
	* top.c (wait_sync_command_done, maybe_wait_sync_command_done)
	(execute_command): Check the current UI's prompt state instead of
	sync_execution.
	* top.h (enum prompt_state): New.
	(struct ui) <prompt_state>: New field.
	(ALL_UIS): New macro.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Make raw_stdout be per MI instance
@ 2016-06-21 11:28 sergiodj+buildbot
  2016-06-21 18:45 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-06-21 11:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9204d6922cb80f34dd799e57f7f0c74bc86e7027 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 9204d6922cb80f34dd799e57f7f0c74bc86e7027

Make raw_stdout be per MI instance

Each MI instance should obviously have its own raw output channel,
along with save_raw_stdout.

gdb/ChangeLog:
2016-06-21  Pedro Alves  <palves@redhat.com>

	* interps.c (current_interpreter): New function.
	* interps.h (current_interpreter): New declaration.
	* mi/mi-cmds.h (raw_stdout): Delete declaration.
	* mi/mi-common.h (struct mi_interp) <raw_stdout,
	saved_raw_stdout>: New field.
	* mi/mi-interp.c (display_mi_prompt): New parameter 'mi'.  Adjust
	to per-UI raw_stdout.
	(mi_interpreter_init): Adjust to per-UI raw_stdout.
	(mi_on_sync_execution_done, mi_execute_command_input_handler)
	(mi_command_loop): Pass MI instance to display_mi_prompt.
	(mi_on_normal_stop_1, mi_output_running_pid, mi_on_resume_1)
	(mi_on_resume): Adjust to per-UI raw_stdout.
	(saved_raw_stdout): Delete.
	(mi_set_logging): Adjust to per-UI raw_stdout and
	saved_raw_stdout.
	* mi/mi-main.c (raw_stdout): Delete.
	(mi_cmd_gdb_exit, captured_mi_execute_command)
	(mi_print_exception, mi_load_progress): Adjust to per-UI
	raw_stdout.
	(print_diff_now, mi_print_timing_maybe): New ui_file parameter.
	Pass it along.
	(print_diff): New ui_file parameter.  Send output there instead of
	raw_stdout.
	* mi/mi-main.h (struct ui_file): Forward declare.
	(mi_print_timing_maybe): Add ui_file parameter.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Make out and error streams be per UI
@ 2016-06-21 10:04 sergiodj+buildbot
  2016-06-21 10:53 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-06-21 10:04 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 694ec099d2fca9e7d47848e8a7fc40ea3aa47a32 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 694ec099d2fca9e7d47848e8a7fc40ea3aa47a32

Make out and error streams be per UI

stderr_fileopen () references stderr directly, which doesn't work when
we have a separate UI with its own stderr-like stream.  So this also
adds a "errstream" to "struct ui", and plumbs stderr_fileopen to take
a stream parameter.

gdb/ChangeLog:
2016-06-21  Pedro Alves  <palves@redhat.com>

	* event-top.c (gdb_setup_readline): Pass the UI's outstream and
	errstream to stdout_fileopen and stderr_fileopen.
	* exceptions.c: Include top.h.
	(print_flush): Open the current UI's outstream file descriptor,
	instead of hardcoding file descriptor 1.
	* main.c (captured_main): Save the main UI's out and error
	streams.  Adjust stderr_fileopen call.
	* top.h (struct ui) <outstream, errstream>: New fields.
	* ui-file.c (stderr_fileopen): Add stream parameter.  Use it
	instead of stderr.
	* ui-file.h (stderr_fileopen): Add stream parameter and update
	comment.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Make input_fd be per UI
@ 2016-06-21  6:37 sergiodj+buildbot
  2016-06-21  9:34 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-06-21  6:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 41fd2b0f5d958fe3056da5c7af4032b1b99d726f ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 41fd2b0f5d958fe3056da5c7af4032b1b99d726f

Make input_fd be per UI

And with that, we can switch the current UI to the UI whose input
descriptor woke up the event loop.  IOW, if the user types in UI 2,
the event loop wakes up, switches to UI 2, and processes the input.
Next the user types in UI 3, the event loop wakes up and switches to
UI 3, etc.

gdb/ChangeLog:
2016-06-21  Pedro Alves  <palves@redhat.com>

	* event-top.c (input_fd): Delete.
	(stdin_event_handler): Switch to the UI whose input descriptor got
	the event.  Adjust to per-UI input_fd.
	(gdb_setup_readline): Don't set the input_fd global.  Adjust to
	per-UI input_fd.
	(gdb_disable_readline): Adjust to per-UI input_fd.
	* event-top.h (input_fd): Delete declaration.
	* linux-nat.c (linux_nat_terminal_inferior): Don't remove input_fd
	from the event-loop here.
	(linux_nat_terminal_ours): Don't register input_fd in the
	event-loop here.
	* main.c (captured_main): Adjust to per-UI input_fd.
	* remote.c (remote_terminal_inferior): Don't remove input_fd from
	the event-loop here.
	(remote_terminal_ours): Don't register input_fd in the event-loop
	here.
	* target.c: Include top.h and event-top.h.
	(target_terminal_inferior): Remove input_fd from the event-loop
	here.
	(target_terminal_ours): Register input_fd in the event-loop.
	* top.h (struct ui) <input_fd>: New field.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Make the intepreters output to all UIs
@ 2016-06-21  4:34 sergiodj+buildbot
  2016-06-21  6:58 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-06-21  4:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 73ab01a07dfef77a9d845be2ef87754435eeffa1 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 73ab01a07dfef77a9d845be2ef87754435eeffa1

Make the intepreters output to all UIs

When we have multiple consoles, MI channels, etc., then we need to
broadcast breakpoint hits, etc. to all UIs.  In the past, I've
adjusted most of the run control to communicate events to the
interpreters through observer notifications, so events would be
properly sent to console and MI streams, in sync and async modes.

This patch does the next logical step -- have each interpreter's
observers output interpreter-specific info to _all_ UIs.

Note that when we have multiple instances of active cli/tui
interpreters, then the cli_interp and tui_interp globals no longer
work.  This is addressed by this patch.

Also, the interpreters currently register some observers when resumed
and remove them when suspended.  If we have multiple instances of the
interpreters, and they can be suspended/resumed at different,
independent times, that no longer works.  What we instead do is always
install the observers, and then have the observers themselves know
when to do nothing.

An earlier prototype of this series did the looping over struct UIs in
common code, and then dispatched events to the interpreters through a
matching interp_on_foo method for each observer.  That turned out a
lot more complicated than the present solution, as we'd end up with
having to create a new interp method every time some interpreter
wanted to listen to some observer notification, resulting in a lot of
duplicated make-work and more coupling than desirable.

gdb/ChangeLog:
2016-06-21  Pedro Alves  <palves@redhat.com>

	* cli/cli-interp.c (cli_interp): Delete.
	(as_cli_interp): New function.
	(cli_on_normal_stop, cli_on_signal_received)
	(cli_on_end_stepping_range, cli_on_signal_exited, cli_on_exited)
	(cli_on_no_history): Send output to all CLI UIs.
	(cli_on_sync_execution_done, cli_on_command_error): Skip output if
	the top level interpreter is not a CLI.
	(cli_interpreter_init): Don't set cli_interp or install observers
	here.
	(_initialize_cli_interp): Install observers here.
	* event-top.c (main_ui_, ui_list): New globals.
	(current_ui): Point to main_ui_.
	(restore_ui_cleanup, switch_thru_all_uis_init)
	(switch_thru_all_uis_cond, switch_thru_all_uis_next): New
	functions.
	* mi/mi-interp.c (as_mi_interp): New function.
	(mi_interpreter_init): Don't install observers here.
	(mi_on_sync_execution_done): Skip output if the top level
	interpreter is not a MI.
	(mi_new_thread, mi_thread_exit, mi_record_changed)
	(mi_inferior_added, mi_inferior_appeared, mi_inferior_exit)
	(mi_inferior_removed): Send output to all MI UIs.
	(find_mi_interpreter, mi_interp_data): Delete.
	(find_mi_interp): New function.
	(mi_on_signal_received, mi_on_end_stepping_range)
	(mi_on_signal_exited, mi_on_exited, mi_on_no_history): Send output
	to all MI UIs.
	(mi_on_normal_stop): Rename to ...
	(mi_on_normal_stop_1): ... this.
	(mi_on_normal_stop): Reimplement, sending output to all MI UIs.
	(mi_traceframe_changed, mi_tsv_created, mi_tsv_deleted)
	(mi_tsv_modified, mi_breakpoint_created, mi_breakpoint_deleted)
	(mi_breakpoint_modified, mi_output_running_pid): Send output to
	all MI UIs.
	(mi_on_resume): Rename to ...
	(mi_on_resume_1): ... this.  Don't handle infcalls here.
	(mi_on_resume): Reimplement, sending output to all MI UIs.
	(mi_solib_loaded, mi_solib_unloaded, mi_command_param_changed)
	(mi_memory_changed): Send output to all MI UIs.
	(report_initial_inferior): Install observers here.
	* top.h (struct ui) <next>: New field.
	(ui_list): Declare.
	(struct switch_thru_all_uis): New.
	(switch_thru_all_uis_init, switch_thru_all_uis_cond)
	(switch_thru_all_uis_next): Declare.
	(SWITCH_THRU_ALL_UIS): New macro.
	* tui/tui-interp.c (tui_interp): Delete global.
	(as_tui_interp): New function.
	(tui_on_normal_stop, tui_on_signal_received)
	(tui_on_end_stepping_range, tui_on_signal_exited, tui_on_exited)
	(tui_on_no_history): Send output to all TUI UIs.
	(tui_on_sync_execution_done, tui_on_command_error): Skip output if
	the top level interpreter is not a TUI.
	(tui_init): Don't set tui_interp or install observers here.
	(_initialize_tui_interp): Install observers here.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Make the interpreters be per UI
@ 2016-06-21  3:09 sergiodj+buildbot
  2016-06-21  5:02 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-06-21  3:09 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cb814510676f7f6c08b329af2f57006fa598b619 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: cb814510676f7f6c08b329af2f57006fa598b619

Make the interpreters be per UI

Make each UI have its own interpreter list, top level interpreter,
current interpreter, etc.  The "interpreter_async" global is not
really specific to an struct interp (it crosses interpreter-exec ...),
so I moved it to "struct ui" directly, while the other globals were
left hidden in interps.c, opaque to the rest of GDB.

gdb/ChangeLog:
2016-06-21  Pedro Alves  <palves@redhat.com>

	* breakpoint.c (bpstat_do_actions_1): Access the current UI's
	async field instead of the interpreter_async global.
	* cli/cli-script.c (execute_user_command, while_command)
	(if_command, script_from_file): Likewise.
	* compile/compile.c: Include top.h instead of interps.h.
	(compile_file_command, compile_code_command)
	(compile_print_command): Access the current UI's async field
	instead of the interpreter_async global.
	* guile/guile.c: Include top.h instead of interps.h.
	(guile_repl_command, guile_command, gdbscm_execute_gdb_command):
	Access the current UI's async field instead of the
	interpreter_async global.
	* guile/scm-ports.c: Include top.h instead of interps.h.
	(ioscm_with_output_to_port_worker): Access the current UI's async
	field instead of the interpreter_async global.
	* inf-loop.c (inferior_event_handler): Likewise.
	* infcall.c (run_inferior_call): Likewise.
	* infrun.c (reinstall_readline_callback_handler_cleanup)
	(fetch_inferior_event): Likewise.
	* interps.c (interpreter_async): Delete.
	(struct ui_interp_info): New.
	(get_current_interp_info): New function.
	(interp_list, current_interpreter, top_level_interpreter_ptr):
	Delete.
	(interp_add, interp_set, interp_lookup, interp_ui_out)
	(current_interp_set_logging, interp_set_temp)
	(current_interp_named_p): Adjust to per-UI interpreters.
	(command_interpreter): Delete.
	(command_interp, current_interp_command_loop, interp_quiet_p)
	(interp_exec, interpreter_exec_cmd, interpreter_completer)
	(top_level_interpreter, top_level_interpreter_data): Adjust to
	per-UI interpreters.
	* interps.h (interpreter_async): Delete.
	* main.c (captured_command_loop): Access the current UI's async
	field instead of the interpreter_async global.
	* python/python.c (python_interactive_command, python_command)
	(execute_gdb_command): Likewise.
	* top.c (maybe_wait_sync_command_done, execute_command_to_string):
	Access the current UI's async field instead of the
	interpreter_async global.
	* top.h (struct tl_interp_info): Forward declare.
	(struct ui) <interp_info, async>: New fields.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Introduce "struct ui"
@ 2016-06-21  1:57 sergiodj+buildbot
  2016-06-21  3:09 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-06-21  1:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a74e1786ac24d4ef1ce8a92a1ab06c727a462881 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: a74e1786ac24d4ef1ce8a92a1ab06c727a462881

Introduce "struct ui"

This is a step towards supporting multiple consoles/MIs, each on its
own stdio streams / terminal.

See intro comment in top.h.

(I've had trouble picking a name for this object.  I've started out
with "struct console" originally.  But then this is about MI as well,
and there's "interpreter-exec console", which is specifically about
the CLI...

So I changed to "struct terminal", but, then we have a terminal object
that works when the input is not a terminal as well ...

Then I sort of gave up and renamed it to "struct top_level".  But it
then gets horribly confusing when we talk about the "top level
interpreter that's running on the current top level".

In the end, I realized we're already sort of calling this "ui", in
struct ui_out, struct ui_file, and a few coments here and there.)

gdb/ChangeLog:
2016-06-21  Pedro Alves  <palves@redhat.com>

	* event-top.c: Update readline-related comments.
	(input_handler, call_readline): Delete globals.
	(gdb_rl_callback_handler): Call the current UI's input_handler
	method.
	(change_line_handler): Adjust to set current UI's properties
	instead of globals.
	(current_ui_, current_ui): New globals.
	(get_command_line_buffer): Rewrite to refer to the current UI.
	(stdin_event_handler): Adjust to call the call_readline method of
	the current UI.
	(gdb_readline_no_editing_callback): Adjust to call the current UI's
	input_handler method.
	(gdb_setup_readline): Adjust to set current UI's properties
	instead of globals.
	* event-top.h (call_readline, input_handler): Delete declarations.
	* mi/mi-interp.c (mi_interpreter_resume): Adjust to set current
	UI's properties instead of globals.
	* top.c (gdb_readline_wrapper_cleanup): Adjust to set current UI's
	properties instead of globals.
	(gdb_readline_wrapper): Adjust to call and set current UI's
	methods instead of globals.
	* top.h: Include buffer.h and event-loop.h.
	(struct ui): New struct.
	(current_ui): New declaration.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] PR ld/20276: Set non_ir_ref on common symbol
@ 2016-06-20  2:13 sergiodj+buildbot
  2016-06-20  2:36 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-06-20  2:13 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0616a2803812f5c13f8936d281bd71c3d9c09655 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 0616a2803812f5c13f8936d281bd71c3d9c09655

PR ld/20276: Set non_ir_ref on common symbol

Also, don't check alignment on symbol from plugin dummy input.

bfd/
	PR ld/20276
	* elflink.c (elf_link_add_object_symbols): Don't check alignment
	on symbol from plugin dummy input.
ld/
	PR ld/20276
	* plugin.c (plugin_notice): Set non_ir_ref on common symbols.
	* testsuite/ld-plugin/lto.exp (lto_link_tests): Add test for
	PR ld/20276.
	(lto_run_tests): Likewise.
	* testsuite/ld-plugin/pass.out: New file.
	* testsuite/ld-plugin/pr20276a.c: Likewise.
	* testsuite/ld-plugin/pr20276b.c: Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Don't generate PLT for IFUNC GOT/pointer reference
@ 2016-06-18 16:43 sergiodj+buildbot
  2016-06-18 17:08 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-06-18 16:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 233cc9c13af8e8182d0ce5b306526b59f5b11f37 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 233cc9c13af8e8182d0ce5b306526b59f5b11f37

Don't generate PLT for IFUNC GOT/pointer reference

If a backend supports it, PLT entry isn't needed when all references
to a STT_GNU_IFUNC symbols are done via GOT or static function pointers.
For GOT entries, We generate dynamic R_*_GLOB_DAT relocations for
preemptable symbols and R_*_IRELATIVE relocations for non-preemptable
symbols to update them with real function address.  For static pointer
pointers, we generate dynamic pointer relocations and store them in:

1. .rel[a].ifunc section in PIC object.
2. .rel[a].got section in dynamic executable.
3. .rel[a].iplt section in static executable.

We don't allocate GOT entry if it isn't used.

bfd/

	PR ld/20253
	* elf-bfd.h (_bfd_elf_allocate_ifunc_dyn_relocs): Add an
	bfd_boolean argument.
	* elf-ifunc.c (_bfd_elf_create_ifunc_sections): Replace
	"shared object" with "PIC object" in comments.
	(_bfd_elf_allocate_ifunc_dyn_relocs): Updated.  Replace
	"shared object" with "PIC object" in comments.  Avoid PLT if
	requested.  Generate dynamic relocations for non-GOT references.
	Make room for the special first entry in PLT and allocate PLT
	entry only for PLT and PC-relative references.  Store dynamic
	GOT relocations in .rel[a].iplt section for static executables.
	If PLT isn't used, always use GOT for symbol value.  Don't
	allocate GOT entry if it isn't used.
	* elf32-i386.c (elf_i386_check_relocs): Increment PLT reference
	count only in the code section.  Allocate dynamic pointer
	relocation against STT_GNU_IFUNC symbol in the non-code section.
	(elf_i386_adjust_dynamic_symbol): Increment PLT reference count
	only for PC-relative references.
	(elf_i386_allocate_dynrelocs): Pass TRUE to
	_bfd_elf_allocate_ifunc_dyn_relocs.
	(elf_i386_relocate_section): Allow R_386_GOT32/R_386_GOT32X
	relocations against STT_GNU_IFUNC symbols without PLT.  Generate
	dynamic pointer relocation against STT_GNU_IFUNC symbol in
	the non-code section and store it in the proper REL section.
	Don't allow non-pointer relocation against STT_GNU_IFUNC symbol
	without PLT.
	(elf_i386_finish_dynamic_symbol): Generate dynamic
	R_386_IRELATIVE and R_386_GLOB_DAT GOT relocations against
	STT_GNU_IFUNC symbols without PLT.
	(elf_i386_finish_dynamic_sections): Don't handle local
	STT_GNU_IFUNC symbols here.
	(elf_i386_output_arch_local_syms): Handle local STT_GNU_IFUNC
	symbols here.
	(elf_backend_output_arch_local_syms): New.
	* elf32-x86-64.c (elf_i386_check_relocs): Increment PLT reference
	count only in the code section.  Allocate dynamic pointer
	relocation against STT_GNU_IFUNC symbol in the non-code section.
	(elf_x86_64_adjust_dynamic_symbol): Increment PLT reference
	count only for PC-relative references.
	(elf_x86_64_allocate_dynrelocs): Pass TRUE to
	_bfd_elf_allocate_ifunc_dyn_relocs.
	(elf_x86_64_relocate_section): Allow R_X86_64_GOTPCREL,
	R_X86_64_GOTPCRELX, R_X86_64_REX_GOTPCRELX and
	R_X86_64_GOTPCREL64 relocations against STT_GNU_IFUNC symbols
	without PLT.  Generate dynamic pointer relocation against
	STT_GNU_IFUNC symbol in the non-code section and store it in
	the proper RELA section.  Don't allow non-pointer relocation
	against STT_GNU_IFUNC symbol without PLT.
	(elf_x86_64_finish_dynamic_symbol): Generate dynamic
	R_X86_64_IRELATIVE and R_X86_64_GLOB_DAT GOT relocations against
	STT_GNU_IFUNC symbols without PLT.
	(elf_x86_64_finish_dynamic_sections): Don't handle local
	STT_GNU_IFUNC symbols here.
	(elf_x86_64_output_arch_local_syms): Handle local STT_GNU_IFUNC
	symbols here.
	(elf_backend_output_arch_local_syms): New.
	* elfnn-aarch64.c (elfNN_aarch64_allocate_ifunc_dynrelocs):
	Pass FALSE to _bfd_elf_allocate_ifunc_dyn_relocs.

ld/

	PR ld/20253
	* testsuite/ld-i386/i386.exp: Run PR ld/20253 tests.
	* testsuite/ld-i386/no-plt.exp: Likewise.
	* testsuite/ld-x86-64/no-plt.exp: Likewise.
	* testsuite/ld-i386/pr13302.d: Remove .rel.plt section.
	* testsuite/ld-ifunc/ifunc-13-i386.d: Likewise.
	* testsuite/ld-ifunc/ifunc-13-x86-64.d: Likewise.
	* testsuite/ld-ifunc/ifunc-15-i386.d: Likewise.
	* testsuite/ld-ifunc/ifunc-15-x86-64.d: Likewise.
	* testsuite/ld-x86-64/pr13082-5a.d: Likewise.
	* testsuite/ld-x86-64/pr13082-5b.d: Likewise.
	* testsuite/ld-x86-64/pr13082-6a.d: Likewise.
	* testsuite/ld-x86-64/pr13082-6b.d: Likewise.
	* testsuite/ld-i386/pr20244-2a.d: Remove .plt section.
	* testsuite/ld-ifunc/ifunc-21-i386.d: Likewise.
	* testsuite/ld-ifunc/ifunc-21-x86-64.d: Likewise.
	* testsuite/ld-ifunc/ifunc-22-i386.d: Likewise.
	* testsuite/ld-ifunc/ifunc-22-x86-64.d: Likewise.
	* testsuite/ld-i386/pr20244-2b.d: Updated.
	* testsuite/ld-i386/pr20244-2c.d: Likewise.
	* testsuite/ld-ifunc/ifunc-18a-i386.d: Likewise.
	* testsuite/ld-ifunc/ifunc-18a-x86-64.d: Likewise.
	* testsuite/ld-ifunc/ifunc-18b-i386.d: Likewise.
	* testsuite/ld-ifunc/ifunc-18b-x86-64.d: Likewise.
	* testsuite/ld-i386/pr20253-1a.c: New file.
	* testsuite/ld-i386/pr20253-1b.S: Likewise.
	* testsuite/ld-i386/pr20253-1c.S: Likewise.
	* testsuite/ld-i386/pr20253-1d.S: Likewise.
	* testsuite/ld-i386/pr20253-2a.c: Likewise.
	* testsuite/ld-i386/pr20253-2b.S: Likewise.
	* testsuite/ld-i386/pr20253-2c.S: Likewise.
	* testsuite/ld-i386/pr20253-2d.S: Likewise.
	* testsuite/ld-i386/pr20253-3.d: Likewise.
	* testsuite/ld-i386/pr20253-3.s: Likewise.
	* testsuite/ld-i386/pr20253-4.s: Likewise.
	* testsuite/ld-i386/pr20253-4a.d: Likewise.
	* testsuite/ld-i386/pr20253-4b.d: Likewise.
	* testsuite/ld-i386/pr20253-4c.d: Likewise.
	* testsuite/ld-i386/pr20253-5.d: Likewise.
	* testsuite/ld-i386/pr20253-5.s: Likewise.
	* testsuite/ld-ifunc/ifunc-23-x86.s: Likewise.
	* testsuite/ld-ifunc/ifunc-23a-x86.d: Likewise.
	* testsuite/ld-ifunc/ifunc-23b-x86.d: Likewise.
	* testsuite/ld-ifunc/ifunc-23c-x86.d: Likewise.
	* testsuite/ld-ifunc/ifunc-24-x86.s: Likewise.
	* testsuite/ld-ifunc/ifunc-24a-x86.d: Likewise.
	* testsuite/ld-ifunc/ifunc-24b-x86.d: Likewise.
	* testsuite/ld-ifunc/ifunc-24c-x86.d: Likewise.
	* testsuite/ld-ifunc/ifunc-25-x86.s: Likewise.
	* testsuite/ld-ifunc/ifunc-25a-x86.d: Likewise.
	* testsuite/ld-ifunc/ifunc-25b-x86.d: Likewise.
	* testsuite/ld-ifunc/ifunc-25c-x86.d: Likewise.
	* testsuite/ld-x86-64/pr20253-1.s: Likewise.
	* testsuite/ld-x86-64/pr20253-1a.d: Likewise.
	* testsuite/ld-x86-64/pr20253-1b.d: Likewise.
	* testsuite/ld-x86-64/pr20253-1c.d: Likewise.
	* testsuite/ld-x86-64/pr20253-1d.d: Likewise.
	* testsuite/ld-x86-64/pr20253-1e.d: Likewise.
	* testsuite/ld-x86-64/pr20253-1f.d: Likewise.
	* testsuite/ld-x86-64/pr20253-1g.d: Likewise.
	* testsuite/ld-x86-64/pr20253-1h.d: Likewise.
	* testsuite/ld-x86-64/pr20253-1i.d: Likewise.
	* testsuite/ld-x86-64/pr20253-1j.d: Likewise.
	* testsuite/ld-x86-64/pr20253-1k.d: Likewise.
	* testsuite/ld-x86-64/pr20253-1l.d: Likewise.
	* testsuite/ld-x86-64/pr20253-2a.c: Likewise.
	* testsuite/ld-x86-64/pr20253-2b.S: Likewise.
	* testsuite/ld-x86-64/pr20253-2c.S: Likewise.
	* testsuite/ld-x86-64/pr20253-2d.S: Likewise.
	* testsuite/ld-x86-64/pr20253-3.d: Likewise.
	* testsuite/ld-x86-64/pr20253-3.s: Likewise.
	* testsuite/ld-x86-64/pr20253-4.s: Likewise.
	* testsuite/ld-x86-64/pr20253-4a.d: Likewise.
	* testsuite/ld-x86-64/pr20253-4b.d: Likewise.
	* testsuite/ld-x86-64/pr20253-4c.d: Likewise.
	* testsuite/ld-x86-64/pr20253-4d.d: Likewise.
	* testsuite/ld-x86-64/pr20253-4e.d: Likewise.
	* testsuite/ld-x86-64/pr20253-4f.d: Likewise.
	* testsuite/ld-x86-64/pr20253-5.s: Likewise.
	* testsuite/ld-x86-64/pr20253-5a.d: Likewise.
	* testsuite/ld-x86-64/pr20253-5b.d: Likewise.
	* testsuite/ld-ifunc/ifunc-18a-i386.d: Remove extra IRELATIVE
	relocation.
	* testsuite/ld-ifunc/ifunc-18a-x86-64.d: Likewise.
	* testsuite/ld-ifunc/ifunc-18b-i386.d: Likewise.
	* testsuite/ld-ifunc/ifunc-18b-x86-64.d: Likewise.
	* testsuite/ld-ifunc/ifunc-18a.s: Fix a typo.
	* testsuite/ld-x86-64/x86-64.exp: Run pr20253-1 tests.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Handle reinsert breakpoints for vforked child
@ 2016-06-17 18:03 sergiodj+buildbot
  2016-06-17 18:26 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-06-17 18:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2e7b624b851c34f6bc2ab75fcbc94db75f72eb3a ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 2e7b624b851c34f6bc2ab75fcbc94db75f72eb3a

Handle reinsert breakpoints for vforked child

When a thread is doing step-over with reinsert breakpoint, and the
instruction executed is a syscall doing vfork, both parent and child
share the memory, so the reinsert breakpoint in the space is visible
to both of them.  Also, removing the reinsert breakpoints from the
child will effectively remove them from the parent.  We should
carefully manipulate reinsert breakpoints for both processes.

What we are doing here is that

 - uninsert reinsert breakpoints from the parent before cloning the
   breakpoint list.  We use "uninsert" instead of "remove", because
   we need to "reinsert" them back after vfork is done.  In fact,
   "uninsert" removes them from both child and parent process space.
 - reinsert breakpoints in parent process are still copied to child's
   breakpoint list,
 - remove them from child's breakpoint list as what we did for fork,
   at this point, reinsert breakpoints are removed from the child and
   the parent, but they are still tracked by the parent's breakpoint
   list,
 - once vfork is done, "reinsert" them back to the parent,

gdb/gdbserver:

2016-06-17  Yao Qi  <yao.qi@linaro.org>

	* linux-low.c (handle_extended_wait): Call
	uninsert_reinsert_breakpoints for the parent process.  Remove
	reinsert breakpoints from the child process.  Reinsert them to
	the parent process when vfork is done.
	* mem-break.c (uninsert_reinsert_breakpoints): New function.
	(reinsert_reinsert_breakpoints): New function.
	* mem-break.h (uninsert_reinsert_breakpoints): Declare
	(reinsert_reinsert_breakpoints): Declare.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] gdb: new AndesTech NDS32 port
@ 2016-06-17 11:35 sergiodj+buildbot
  2016-06-17 12:50 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-06-17 11:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a28d8e5037333291991f7b0036b273e8ca1ffc34 ***

Author: Yan-Ting Lin <currygt52@gmail.com>
Branch: master
Commit: a28d8e5037333291991f7b0036b273e8ca1ffc34

gdb: new AndesTech NDS32 port

gdb/ChangeLog:

	* Makefile.in (ALL_TARGET_OBS): Add nds32-tdep.o.
	(HFILES_NO_SRCDIR): Add nds32-tdep.h.
	(ALLDEPFILES): Add nds32-tdep.c.
	* NEWS: Mention new NDS32 port.
	* configure.tgt: Add NDS32.
	* nds32-tdep.c: New file.
	* nds32-tdep.h: New file.
	* features/Makefile (XMLTOC): Add nds32.xml.
	* features/nds32-core.xml: New file.
	* features/nds32-fpu.xml: New file.
	* features/nds32-system.xml: New file.
	* features/nds32.c: New file (generated).
	* features/nds32.xml: New file.

gdb/doc/ChangeLog:

	* gdb.texinfo (Standard Target Features): Document NDS32 features.
	(NDS32 Features): New Section.

gdb/testsuite/ChangeLog:

	* gdb.base/float.exp: Add target check for nds32*-*-*.
	* gdb.xml/tdesc-regs.exp: Set core-regs for nds32*-*-*.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] bfd/s390: Fix DT_PLTRELSZ in presence of R_390_IRELATIVE.
@ 2016-06-16 15:53 sergiodj+buildbot
  2016-06-16 15:54 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-06-16 15:53 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f92339b8f316de65add11aeb9cd8ea72630aa556 ***

Author: Marcin Kocielnicki <koriakin@0x04.net>
Branch: master
Commit: f92339b8f316de65add11aeb9cd8ea72630aa556

bfd/s390: Fix DT_PLTRELSZ in presence of R_390_IRELATIVE.

This was broken by 4ade44b727ee77adaa9c22719935d012e253a5e6,
which changed the calculation to use the .rela.plt linker section
instead of its output section - thus skipping .rela.iplt .
Fix the calculations to include it.

bfd/ChangeLog:

	* elf32-s390.c (elf_s390_finish_dynamic_sections): Include
	.rela.iplt in DT_PLTRELSZ.
	* elf64-s390.c (elf_s390_finish_dynamic_sections): Likewise,
	for DT_PLTRELSZ and DT_RELASZ as well.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Check SEC_ALLOC before allocating dynamic relocation
@ 2016-06-16  2:00 sergiodj+buildbot
  2016-06-16  2:41 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-06-16  2:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4c23f2ffa8fbd467bca51956130a1f30cfe34371 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 4c23f2ffa8fbd467bca51956130a1f30cfe34371

Check SEC_ALLOC before allocating dynamic relocation

	* elf32-i386.c (elf_i386_check_relocs): Check SEC_ALLOC before
	allocating dynamic relocation.
	* elf64-x86-64.c (elf_x86_64_check_relocs): Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [ARC] Add ldbit for nps
@ 2016-06-14 17:03 sergiodj+buildbot
  2016-06-14 18:46 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-06-14 17:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 28215275a6bbb7c4b4c2d683a1d94fead7dacc35 ***

Author: Graham Markall <graham.markall@embecosm.com>
Branch: master
Commit: 28215275a6bbb7c4b4c2d683a1d94fead7dacc35

[ARC] Add ldbit for nps

This commit adds the ldbit instruction for the NPS-400. The ldbit
instruction uses the same encoding as the ld instruction, but sets
the ZZ field to 11 (which is a reserved setting), and sets the AA
field to 1 or 2 for the x2 and x4 flags respectively.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [ARC] Add arithmetic and logic instructions for nps
@ 2016-06-14 15:50 sergiodj+buildbot
  2016-06-14 16:14 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-06-14 15:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 14053c1903cc0e4f0130570f61aee2825661cd7d ***

Author: Graham Markall <graham.markall@embecosm.com>
Branch: master
Commit: 14053c1903cc0e4f0130570f61aee2825661cd7d

[ARC] Add arithmetic and logic instructions for nps

This commit completes the implementation of arithmetic and logic
instructions for the NPS-400. These instructions are:

- calcbsd / calcbxd
- calckey / calcxkey
- mxb / imxb
- addl, subl, orl, andl, xorl
- andab / orab
- lbdsize
- bdlen
- csms, csma, cbba
- zncv
- hofs


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Delete bfd_my_archive macro
@ 2016-06-14  6:41 sergiodj+buildbot
  2016-06-14  6:41 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-06-14  6:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3860d2b4b72feeef4cf045c6c9907a0476f46f3d ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 3860d2b4b72feeef4cf045c6c9907a0476f46f3d

Delete bfd_my_archive macro

Many more places use abfd->my_archive rather than bfd_my_archive (abfd),
so let's make the code consistently use the first idiom.

bfd/
	* bfd-in.h (bfd_my_archive): Delete.
	* bfd-in2.h: Regenerate.
binutils/
	* ar.c: Expand uses of bfd_my_archive.
	* size.c: Likewise.
ld/
	* ldlang.c: Expand uses of bfd_my_archive.
	* ldmain.c: Likewise.
	* ldmisc.c: Likewise.
	* plugin.c: Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] MIPS/BFD: Update outdated comment about o32 R_MIPS_PC32 reloc support
@ 2016-06-13 20:20 sergiodj+buildbot
  2016-06-13 20:17 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-06-13 20:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0c9663cbd41c27a8e20ca88a53ba3deae374f1d8 ***

Author: Maciej W. Rozycki <macro@imgtec.com>
Branch: master
Commit: 0c9663cbd41c27a8e20ca88a53ba3deae374f1d8

MIPS/BFD: Update outdated comment about o32 R_MIPS_PC32 reloc support

Complement:

commit b47468a6dbd1b54c44c2edc0f7db64a073d894ea
Author: Catherine Moore <clm@redhat.com>
Date:   Mon May 6 15:25:45 2013 +0000

and the return of support for R_MIPS_PC32 there.

	bfd/
	* elf32-mips.c (elf_mips_gnu_pcrel32): Update comment.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix compile time warning about a redundant comparison in an assertion statement.
@ 2016-06-13 13:44 sergiodj+buildbot
  2016-06-13 14:00 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-06-13 13:44 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e46dd0f46b9a2ac2b07343b91c447620ede47d26 ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: e46dd0f46b9a2ac2b07343b91c447620ede47d26

Fix compile time warning about a redundant comparison in an assertion statement.

	* gdbtypes.c (replace_type): Fix assertion.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Subtract GOT base only with a base register
@ 2016-06-12  4:48 sergiodj+buildbot
  2016-06-12  5:02 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-06-12  4:48 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 74d7f0aa5b1e27da215349fb32337e1d83aca7d7 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 74d7f0aa5b1e27da215349fb32337e1d83aca7d7

Subtract GOT base only with a base register

When relocating R_386_GOT32 in "op $0, bar@GOT", we shouldn't subtract
GOT base without a base register and we should disallow it without a
base register for PIC.

bfd/

	PR ld/20244
	* elf32-i386.c (elf_i386_relocate_section): When relocating
	R_386_GOT32, return error without a base register for PIC and
	subtract the .got.plt section address only with a base register.

ld/

	PR ld/20244
	* testsuite/ld-i386/i386.exp: Run pr20244-1a and pr20244-1b.
	* testsuite/ld-i386/pr20244-1.s: New file.
	* testsuite/ld-i386/pr20244-1a.d: Likewise.
	* testsuite/ld-i386/pr20244-1b.d: Likewise.
	* testsuite/ld-i386/pr20244-1c.d: Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Use size_t rather than bfd_size_type
@ 2016-06-11  8:19 sergiodj+buildbot
  2016-06-11  8:39 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-06-11  8:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ef53be89160126f2fa5dec8f1ec3bd6d99fb0681 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: ef53be89160126f2fa5dec8f1ec3bd6d99fb0681

Use size_t rather than bfd_size_type

I noticed when writing _bfd_elf_strtab_save/restore that size_t would
be better than bfd_size_type for a number of things in elf-strtab.c.
Using a 64-bit bfd_size_type on a 32-bit host doesn't make much sense
for array sizes and indices.

	* elf-strtab.c (struct strtab_save): Use size_t for "size".
	(struct elf_strtab_hash): Likewise for "size" and "alloced".
	(_bfd_elf_strtab_init): Formatting.
	(_bfd_elf_strtab_add): Return size_t rather than bfd_size_type.
	(_bfd_elf_strtab_addref): Take size_t idx param.
	(_bfd_elf_strtab_delref, _bfd_elf_strtab_refcount): Likewise.
	(_bfd_elf_strtab_offset): Likewise.
	(_bfd_elf_strtab_clear_all_refs): Use size_t idx.
	(_bfd_elf_strtab_save): Use size_t "idx" and "size" vars.
	(_bfd_elf_strtab_restore, _bfd_elf_strtab_emit): Similarly.
	(_bfd_elf_strtab_finalize): Similarly.
	* elf-bfd.h (_bfd_elf_strtab_add): Update prototypes.
	(_bfd_elf_strtab_addref, _bfd_elf_strtab_delref): Likewise.
	(_bfd_elf_strtab_refcount, _bfd_elf_strtab_offset): Likewise.
	* elf.c (bfd_elf_get_elf_syms): Calculate symbol buffer size
	using bfd_size_type.
	(bfd_section_from_shdr): Delete amt.
	(_bfd_elf_init_reloc_shdr): Likewise.
	(_bfd_elf_link_assign_sym_version): Likewise.
	(assign_section_numbers): Use size_t reloc_count.
	* elflink.c (struct elf_symbuf_head): Use size_t "count".
	(bfd_elf_link_record_dynamic_symbol): Use size_t for some vars.
	(elf_link_is_defined_archive_symbol): Likewise.
	(elf_add_dt_needed_tag): Likewise.
	(elf_finalize_dynstr): Likewise.
	(elf_link_add_object_symbols): Likewise.
	(bfd_elf_size_dynamic_sections): Likewise.
	(elf_create_symbuf): Similarly.
	(bfd_elf_match_symbols_in_sections): Likewise.
	(elf_link_swap_symbols_out): Likewise.
	(elf_link_check_versioned_symbol): Likewise.
	(bfd_elf_gc_record_vtinherit): Likewise.
	(bfd_elf_gc_common_finalize_got_offsets): Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix rust-exp handling in makefile
@ 2016-06-10 16:12 sergiodj+buildbot
  2016-06-10 16:43 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-06-10 16:12 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT edef7b8cf3d811ce8630591dbed1257ba16164ff ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: edef7b8cf3d811ce8630591dbed1257ba16164ff

Fix rust-exp handling in makefile

I noticed that the rust-exp handling in the Makefile differed from
that of other .y files.  I believe I noticed this by seeing a stray
"rm" in the build log.

This patch changes the Makefile to bring the rust-exp handling in line
with that of other .y files.

2016-06-10  Tom Tromey  <tom@tromey.com>

	* Makefile.in (COMMON_OBS): Remove rust-exp.o.
	(YYFILES): Add rust-exp.c.
	(YYOBJ): Add rust-exp.o.
	(local-maintainer-clean): Remove rust-exp.c.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] PR python/19819 - remove unused globals from py-xmethods.c
@ 2016-06-09 21:14 sergiodj+buildbot
  2016-06-09 21:47 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-06-09 21:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4dee35314b3bae66125faf69e1d2949ff7b00b49 ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 4dee35314b3bae66125faf69e1d2949ff7b00b49

PR python/19819 - remove unused globals from py-xmethods.c

PR python/19819 concerns some unused global variables in
py-xmethods.c.  This patch deletes the unused globals.

Tested by rebuilding.

2016-06-09  Tom Tromey  <tom@tromey.com>

	PR python/19819:
	* python/py-xmethods.c (invoke_method_name)
	(py_get_result_type_method_name, py_invoke_method_name): Remove.
	(gdbpy_initialize_xmethods): Don't initialize
	py_invoke_method_name, py_get_result_type_method_name.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] mi/mi-interp.c: Add missing braces
@ 2016-06-07 16:02 sergiodj+buildbot
  2016-06-07 16:26 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-06-07 16:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1aec0b6ad6eae1fa97bb1a4a47959ff204aa15a2 ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: 1aec0b6ad6eae1fa97bb1a4a47959ff204aa15a2

mi/mi-interp.c: Add missing braces

gdb/ChangeLog:

	* mi/mi-interp.c (mi_record_changed): Add missing braces.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Frame static link: Handle null pointer.
@ 2016-06-07 11:49 sergiodj+buildbot
  2016-06-07 12:19 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-06-07 11:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2091da296fd563f62d856dcb5a049a63484ed65e ***

Author: Bernhard Heckel <bernhard.heckel@intel.com>
Branch: master
Commit: 2091da296fd563f62d856dcb5a049a63484ed65e

Frame static link: Handle null pointer.

2016-06-07  Bernhard Heckel  <bernhard.heckel@intel.com>

gdb/Changelog:
	* findvar.c (follow_static_link): Check for valid pointer.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Add method/format information to =record-started
@ 2016-06-06 21:21 sergiodj+buildbot
  2016-06-06 21:39 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-06-06 21:21 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 38b022b4452f996fb5a8598f80d850b594621bcf ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: 38b022b4452f996fb5a8598f80d850b594621bcf

Add method/format information to =record-started

Eclipse CDT now supports enabling execution recording using two methods
(full and btrace) and both formats for btrace (bts and pt).  In the
event that recording is enabled behind the back of the GUI (by the user
on the command line, or a script), we need to know which method/format
are being used, so it can be correctly reflected in the interface.  This
patch adds this information to the =record-started async record.

Before:

  =record-started,thread-group="i1"

After:

  =record-started,thread-group="i1",method="btrace",format="bts"
  =record-started,thread-group="i1",method="btrace",format="pt"
  =record-started,thread-group="i1",method="full"

The "format" field is only present when the current method supports
multiple formats (only the btrace method as of now).

gdb/ChangeLog:

	* NEWS: Mention the new fields in =record-started.
	* common/btrace-common.h (btrace_format_short_string): New function
	declaration.
	* common/btrace-common.c (btrace_format_short_string): New
	function.
	* mi/mi-interp.c (mi_record_changed): Output method and format
	fields in the =record-started record.
	* record-btrace.c (record_btrace_open): Adapt record_changed
	notification.
	* record-full.c (record_full_open): Likewise.
	* record.c (cmd_record_stop): Likewise.

gdb/doc/ChangeLog:

	* gdb.texinfo (GDB/MI Async Records): Document method and
	format fields in =record-started.
	* observer.texi (record_changed): Add method and format
	parameters.

gdb/testsuite/ChangeLog:

	* gdb.mi/mi-record-changed.exp: Adjust =record-started output
	matching.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Handle indirect branches for AMD64 and Intel64
@ 2016-06-03 23:15 sergiodj+buildbot
  2016-06-03 23:30 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-06-03 23:15 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 07f5af7d3c635234284e7a0f7dd7a410b1628b8b ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 07f5af7d3c635234284e7a0f7dd7a410b1628b8b

Handle indirect branches for AMD64 and Intel64

AMD64 spec and Intel64 spec differ in indirect branches in 64-bit mode.
AMD64 supports indirect branches with 16-bit address via the data size
prefix while the data size prefix is ignored by Intel64.

gas/

	PR binutis/18386
	* testsuite/gas/i386/i386.exp: Run x86-64-branch-4.
	* testsuite/gas/i386/x86-64-branch.d: Updated.
	* testsuite/gas/i386/ilp32/x86-64-branch.d: Likewise.
	* testsuite/gas/i386/x86-64-branch-4.l: New file.
	* testsuite/gas/i386/x86-64-branch-4.s: Likewise.

opcodes/

	PR binutis/18386
	* i386-dis.c (indirEv): Replace stack_v_mode with indir_v_mode.
	(indir_v_mode): New.
	Add comments for '&'.
	(reg_table): Replace "{T|}" with "{&|}" on call and jmp.
	(putop): Handle '&'.
	(intel_operand_size): Handle indir_v_mode.
	(OP_E_register): Likewise.
	* i386-opc.tbl: Mark 64-bit indirect call/jmp as AMD64.  Add
	64-bit indirect call/jmp for AMD64.
	* i386-tbl.h: Regenerated


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix C++ build for Cygwin
@ 2016-06-03 11:47 sergiodj+buildbot
  2016-06-03 12:00 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-06-03 11:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0ae534d2cfef358bcde3166ce3a29faf85bc632a ***

Author: Jon Turney <jon.turney@dronecode.org.uk>
Branch: master
Commit: 0ae534d2cfef358bcde3166ce3a29faf85bc632a

Fix C++ build for Cygwin

gdb/ChangeLog:

2016-06-02  Jon Turney  <jon.turney@dronecode.org.uk>

	* windows-nat.c (handle_output_debug_string): Return type of
	gdb_signal_from_host() is gdb_signal, not an int.
	(windows_get_exec_module_filename): Add pointer casts for C++.

gdb/gdbserver/ChangeLog:

2016-06-02  Jon Turney  <jon.turney@dronecode.org.uk>

	* win32-low.c (win32_create_inferior): Add pointer casts for C++.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix PR python/18984
@ 2016-06-02 19:39 sergiodj+buildbot
  2016-06-02 20:07 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-06-02 19:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1b40ec0559f4b24ccdf6b073610c526c4aa33c4d ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 1b40ec0559f4b24ccdf6b073610c526c4aa33c4d

Fix PR python/18984

This fixes PR python/18984.

The bug is that gdbpy_solib_name uses GDB_PY_LL_ARG, whereas it should
use GDB_PY_LLU_ARG to avoid overflow.

Built and tested on x86-64 Fedora 23.

2016-06-02  Tom Tromey  <tom@tromey.com>

	PR python/18984:
	* python/python.c (gdbpy_solib_name): Use GDB_PY_LLU_ARG.

2016-06-02  Tom Tromey  <tom@tromey.com>

	PR python/18984:
	* gdb.python/py-shared.exp: Add solib_name test.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] mi-memory-changed.exp: Fix filename passed to untested
@ 2016-06-02 15:40 sergiodj+buildbot
  2016-06-02 17:16 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-06-02 15:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 193bd37899bc7e301b195929bc7e335bea03d4e4 ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: 193bd37899bc7e301b195929bc7e335bea03d4e4

mi-memory-changed.exp: Fix filename passed to untested

gdb/testsuite/ChangeLog:

	* gdb.mi/mi-memory-changed.exp: Fix filename passed to untested.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Replace data32 with data16 in comments
@ 2016-06-02 14:30 sergiodj+buildbot
  2016-06-02 15:02 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-06-02 14:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3ddf1bdd423a127564d5d13cabde8863431576a3 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 3ddf1bdd423a127564d5d13cabde8863431576a3

Replace data32 with data16 in comments

The 0x66 prefix is data16, not data32 in 64-bit.

	* elf64-x86-64.c: Replace data32 with data16 in comments.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Add new Serbian translation for the bfd library.
@ 2016-06-01 16:03 sergiodj+buildbot
  2016-06-01 18:26 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-06-01 16:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 885a10879eea3cf7ccbb324109a56f0bc391dcfa ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: 885a10879eea3cf7ccbb324109a56f0bc391dcfa

Add new Serbian translation for the bfd library.

	* po/sr.po: New Serbian translation.
	* configure.ac (ALL_LINGUAS): Add sr.
	* configure: Regenerate.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] infcmd, btrace: fix crash in 'finish' for tailcall-only frames
@ 2016-06-01  9:27 sergiodj+buildbot
  2016-06-01 11:03 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-06-01  9:27 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e3b5daf9f735999259c5a8f68b422850c59897e5 ***

Author: Markus Metzger <markus.t.metzger@intel.com>
Branch: master
Commit: e3b5daf9f735999259c5a8f68b422850c59897e5

infcmd, btrace: fix crash in 'finish' for tailcall-only frames

Patch 7eb895307f53 Skip unwritable frames in command "finish"
skips non-writable frames in addition to tailcall frames.

If skip_tailcall_frames already returns NULL, skip_unwritable_frames
will be called with a NULL frame and crash in get_frame_arch.  This is
caught by gdb.btrace/tailcall-only.exp.

Further, if we ever end up with a mixture of tailcall and non-writable
frames, we may not skip all of them, as intended.

Loop over skip_tailcall_frames and skip_unwritable_frames as long as at least
one of them makes progress.

gdb/
	* infcmd.c (skip_finish_frames): New.
	(finish_command): Call skip_finish_frames.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Wake up interruptible_select in remote_fileio ctrl-c handler
@ 2016-06-01  8:46 sergiodj+buildbot
  2016-06-01  9:16 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-06-01  8:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 03d73f1fd9d89d89bdd021cad26693e4f6abc07a ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 03d73f1fd9d89d89bdd021cad26693e4f6abc07a

Wake up interruptible_select in remote_fileio ctrl-c handler

As reported in PR 19998, after type ctrl-c, GDB hang there and does
not send interrupt.  It causes a fail in gdb.base/interrupt.exp.
All targets support remote fileio should be affected.

When we type ctrc-c, SIGINT is handled by remote_fileio_sig_set,
as shown below,

 #0  remote_fileio_sig_set (sigint_func=0x4495d0 <remote_fileio_ctrl_c_signal_handler(int)>) at /home/yao/SourceCode/gnu/gdb/git/gdb/remote-fileio.c:325
 #1  0x00000000004495de in remote_fileio_ctrl_c_signal_handler (signo=<optimised out>) at /home/yao/SourceCode/gnu/gdb/git/gdb/remote-fileio.c:349
 #2  <signal handler called>
 #3  0x00007ffff647ed83 in __select_nocancel () at ../sysdeps/unix/syscall-template.S:81
 #4  0x00000000005530ce in interruptible_select (n=10, readfds=readfds@entry=0x7fffffffd730, writefds=writefds@entry=0x0, exceptfds=exceptfds@entry=0x0,
    timeout=timeout@entry=0x0) at /home/yao/SourceCode/gnu/gdb/git/gdb/event-top.c:1017
 #5  0x000000000061ab20 in stdio_file_read (file=<optimised out>, buf=0x12d02e0 "\n\022-\001", length_buf=16383)
    at /home/yao/SourceCode/gnu/gdb/git/gdb/ui-file.c:577
 #6  0x000000000044a4dc in remote_fileio_func_read (buf=0x12c0360 "") at /home/yao/SourceCode/gnu/gdb/git/gdb/remote-fileio.c:583
 #7  0x0000000000449598 in do_remote_fileio_request (uiout=<optimised out>, buf_arg=buf_arg@entry=0x12c0340)
    at /home/yao/SourceCode/gnu/gdb/git/gdb/remote-fileio.c:1179

we don't set quit_serial_event,

  do
    {
      res = gdb_select (n, readfds, writefds, exceptfds, timeout);
    }
  while (res == -1 && errno == EINTR);

  if (res == 1 && FD_ISSET (fd, readfds))
    {
      errno = EINTR;
      return -1;
    }
  return res;

we can't go out of the loop above, and that is why GDB can't send
interrupt.

Recently, we stop throwing exception from SIGINT handler
(remote_fileio_ctrl_c_signal_handler)
https://sourceware.org/ml/gdb-patches/2016-03/msg00372.html, which
is correct, because gdb_select is interruptible.  However, in the
same patch series, we add interruptible_select later as a wrapper
to gdb_select, https://sourceware.org/ml/gdb-patches/2016-03/msg00375.html
and it is not interruptible (because of the loop in it) unless
select/poll-able file descriptors are marked.

This fix in this patch is to call quit_serial_event_set, so that we can
go out of the loop above, return -1 and set errno to EINTR.

2016-06-01  Yao Qi  <yao.qi@linaro.org>

	PR remote/19998
	* remote-fileio.c (remote_fileio_ctrl_c_signal_handler): Call
	quit_serial_event_set.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [PR gdb/19893] Fix handling of synthetic C++ references
@ 2016-05-31 19:07 sergiodj+buildbot
  2016-05-31 19:38 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-05-31 19:07 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3326303bf5ae4c92f2fbbff387ce231a16c1c8bf ***

Author: Martin Galvan <martin.galvan@tallertechnologies.com>
Branch: master
Commit: 3326303bf5ae4c92f2fbbff387ce231a16c1c8bf

[PR gdb/19893] Fix handling of synthetic C++ references

https://sourceware.org/bugzilla/show_bug.cgi?id=19893

I've traced the main source of the problem to pieced_value_funcs.coerce_ref not being
implemented. Since gdb always assumes references are implemented as pointers, this
causes it to think that it's dealing with a NULL pointer, thus breaking any operations
involving synthetic references.

What I did here was implementing pieced_value_funcs.coerce_ref using some of the synthetic
pointer handling code from indirect_pieced_value, as Pedro suggested. I also made a few
adjustments to the reference printing code so that it correctly shows either the address
of the referenced value or (if it's non-addressable) the "<synthetic pointer>" string.

I also wrote some unit tests based on Dwarf::assemble; these took a while to make
because in most cases I needed a synthetic reference to a physical variable. Additionally,
I started working on a unit test for classes that have a vtable, but ran into a few issues
so that'll probably go in a future patch. One thing that should definitely be fixed is that
proc function_range (called for MACRO_AT_func) will always try to compile/link using gcc
with the default options instead of g++, thus breaking C++ compilations that require e.g. libstdc++.

gdb/ChangeLog:

	* dwarf2loc.c (coerce_pieced_ref, indirect_synthetic_pointer,
	fetch_const_value_from_synthetic_pointer): New functions.
	(indirect_pieced_value): Move lower half to indirect_synthetic_pointer.
	(pieced_value_funcs): Implement coerce_ref.
	* valops.c (value_addr): Call coerce_ref for synthetic references.
	* valprint.c (valprint_check_validity): Return true for synthetic
	references.  Also, don't show "<synthetic pointer>" if they reference
	addressable values.
	(generic_val_print_ref): Handle synthetic references.  Also move some
	code to print_ref_address.
	(print_ref_address, get_value_addr_contents): New functions.

gdb/testsuite/ChangeLog:

	* gdb.dwarf2/implref.exp: Rename to...
	* gdb.dwarf2/implref-const.exp: ...this.  Also add more test statements.
	* gdb.dwarf2/implref-array.c: New file.
	* gdb.dwarf2/implref-array.exp: Likewise.
	* gdb.dwarf2/implref-global.c: Likewise.
	* gdb.dwarf2/implref-global.exp: Likewise.
	* gdb.dwarf2/implref-struct.c: Likewise.
	* gdb.dwarf2/implref-struct.exp: Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Don't needlessly clear xmemdup allocated memory.
@ 2016-05-31 11:20 sergiodj+buildbot
  2016-05-31 11:37 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-05-31 11:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c12969f8b53659f0d70b5e049c49b97a96826a3f ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: c12969f8b53659f0d70b5e049c49b97a96826a3f

Don't needlessly clear xmemdup allocated memory.

	* xmemdup.c (xmemdup): Use xmalloc rather than xcalloc.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Add variable length tests for emit_ref in trace-condition.exp
@ 2016-05-30 17:30 sergiodj+buildbot
  2016-05-30 20:58 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-05-30 17:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2320162a6219c664a8da2e2ff68b08d6f6c2ffcc ***

Author: Antoine Tremblay <antoine.tremblay@ericsson.com>
Branch: master
Commit: 2320162a6219c664a8da2e2ff68b08d6f6c2ffcc

Add variable length tests for emit_ref in trace-condition.exp

This patch add variable length tests for emit_ref by reading the variable
passed as argument of 8 to 64 bit.

gdb/testsuite/ChangeLog:

	* gdb.trace/trace-condition.c (marker): Adapt signature to 8 to 64
	bits types.
	(main): Adapt to 8 to 64 bits types.
	* gdb.trace/trace-condition.exp: Add new tests.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Add counter-cases for trace-condition.exp tests
@ 2016-05-30 17:04 sergiodj+buildbot
  2016-05-30 17:28 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-05-30 17:04 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7faeb45ae36426b827c49457cf7186d73756cccc ***

Author: Antoine Tremblay <antoine.tremblay@ericsson.com>
Branch: master
Commit: 7faeb45ae36426b827c49457cf7186d73756cccc

Add counter-cases for trace-condition.exp tests

In trace-condition.exp, tests are done by doing a conditional tracepoint
and validating that the trace contains all the frames that could be
collected if that condition is true.

E.g. test_tracepoints $trace_command "21 + 21 == 42" 10

This will always return true and collect the 10 frames possible to collect
with the test program.

However, if the condition evaluation is broken such that the condition is
unconditional we will not notice this problem.

This patch adds counter-cases to such conditions like so:

$trace_command "21 + 11 == 42" 0

This way such a problem would be noticed.

gdb/testsuite/ChangeLog:

	* gdb.trace/trace-condition.exp: Add counter-case tests.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Code cleanup: dwarf2_get_pc_bounds: -1/0/+1 -> enum
@ 2016-05-30 12:29 sergiodj+buildbot
  2016-05-30 12:46 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-05-30 12:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3a2b436ae9958a1029545c03201b7223ff33c150 ***

Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Branch: master
Commit: 3a2b436ae9958a1029545c03201b7223ff33c150

Code cleanup: dwarf2_get_pc_bounds: -1/0/+1 -> enum

Make the code (maybe) more readable + primarily prepare it for [patch 2/2]
enum extension.

This change should have no code change impact.

gdb/ChangeLog
2016-05-30  Jan Kratochvil  <jan.kratochvil@redhat.com>

	Code cleanup: dwarf2_get_pc_bounds: -1/0/+1 -> enum
	* dwarf2read.c (enum pc_bounds_kind) New.
	(dwarf2_get_pc_bounds): Use it in the declaration.
	(process_psymtab_comp_unit_reader): Adjust caller.  Rename has_pc_info
	to cu_bounds_kind.
	(read_func_scope, read_lexical_block_scope, read_call_site_scope):
	Adjust callers.
	(dwarf2_get_pc_bounds): Use enum pc_bounds_kind in the definition.
	(dwarf2_get_subprogram_pc_bounds, get_scope_pc_bounds): Adjust callers.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] NEWS: QCatchSyscalls: simplify
@ 2016-05-29 18:59 sergiodj+buildbot
  2016-05-29 19:17 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-05-29 18:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT aab3c527d779a8e833a469203336afcc17512559 ***

Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Branch: master
Commit: aab3c527d779a8e833a469203336afcc17512559

NEWS: QCatchSyscalls: simplify

Standardize the QCatchSyscalls NEWS entry.

gdb/ChangeLog
2016-05-29  Jan Kratochvil  <jan.kratochvil@redhat.com>

	* NEWS (QCatchSyscalls): Remove the parameter.  Include ...
	(QCatchSyscalls:1 in qSupported) ... this separate entry which got
	deleted.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] MIPS/BFD: Enable local R_MIPS_26 overflow detection
@ 2016-05-28 10:13 sergiodj+buildbot
  2016-05-28 21:24 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-05-28 10:13 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7743482350c9c97484a429070db7d994a643a9eb ***

Author: Maciej W. Rozycki <macro@imgtec.com>
Branch: master
Commit: 7743482350c9c97484a429070db7d994a643a9eb

MIPS/BFD: Enable local R_MIPS_26 overflow detection

The original MIPS SVR4 psABI defines the calculation for the R_MIPS_26
relocation in a complex way, as follows[1]:

Name        Value Field    Symbol   Calculation
R_MIPS_26     4   T-targ26 local    (((A << 2) | \
                                      (P & 0xf0000000)) + S) >> 2
              4   T-targ26 external (sign-extend(A << 2) + S) >> 2

This is further clarified, by correcting typos (already applied in the
excerpt above) in the 64-bit psABI extension[2].  A note is included in
both documents to specify that for the purpose of relocation processing
a local symbol is one with binding STB_LOCAL and type STT_SECTION, and
otherwise, a symbol is external.

We have both calculations implemented for the R_MIPS_26 relocation, and
by extension also for the R_MIPS16_26 and R_MICROMIPS_26_S1 relocations,
from now on collectively called jump relocations.  However our code uses
a different condition to tell local and external symbols apart, that is
it only checks for the STB_LOCAL binding and ignores the symbol type,
however for REL relocations only.  The external calculation is used for
all RELA jump relocations.

In reality the difference matters for jump relocations referring local
MIPS16 and, as from recent commit 44d3da233815 ("MIPS/GAS: Treat local
jump relocs the same no matter if REL or RELA"), also local microMIPS
symbols.  Such relocations are not converted to refer to corresponding
section symbols instead and retain the original local symbol reference.

It can be inferred from the relocation calculation definitions that the
addend is effectively unsigned for the local case and explicitly signed
for the external case.  With the REL relocation format it makes sense
given the limited range provided for by the field being relocated: the
use of an unsigned addend expands the range by one bit for the local
case, because a negative offset from a section symbol makes no sense,
and any usable negative offset from the original local symbol will have
worked out positive if converted to a section-relative reference.  In
the external case a signed addend gives more flexibility as offsets both
negative and positive can be used with a symbol.  Any such offsets will
typically have a small value.

The inclusion of the (P & 0xf0000000) component, ORed in the calculation
in the local case, seems questionable as bits 31:28 are not included in
the relocatable field and are masked out as the relocation is applied.
Their value is therefore irrelevant for output processing, the relocated
field ends up the same regardless of their value.  They could be used
for overflow detection, however this is precluded by adding them to bits
31:28 of the symbol referred, as the sum will not correspond to the
value calculated by the processor at run time whenever bits 31:28 of the
symbol referred are not all zeros, even though it is valid as long they
are the same as bits 31:28 of P.

We deal with this problem by ignoring any overflow resulting from the
local calculation.  This however makes us miss genuine overflow cases,
where 31:28 of the symbol referred are different from bits 31:28 of P,
and non-functional code is produced.

Given the situation, for the purpose of overflow detection we can change
our code to follow the original psABI and only treat the in-place addend
as unsigned in the section symbol case, permitting jumps to offsets
128MiB and above into section.  Sections so large may be uncommon, but
still a reasonable use case.  On the other hand such large offsets from
regular local symbols are not expected and it makes sense to support
(possibly small) negative offsets instead, also in consistency with what
we do for global symbols.

Drop the (P & 0xf0000000) component then, treat the addend as signed
with local non-section symbols and also detect an overflow in the result
of such calculation with local symbols.  NB it does not affect the value
computed for the relocatable field, it only affects overflow detection.

References:

[1] "SYSTEM V APPLICATION BINARY INTERFACE, MIPS RISC Processor
    Supplement, 3rd Edition", Figure 4-11: "Relocation Types", p. 4-19
    <http://www.linux-mips.org/pub/linux/mips/doc/ABI/mipsabi.pdf>

[2] "64-bit ELF Object File Specification, Draft Version 2.5", Table 32
    "Relocation Types", p. 45
    <http://techpubs.sgi.com/library/manuals/4000/007-4658-001/pdf/007-4658-001.pdf>

	bfd/
	* elfxx-mips.c (mips_elf_calculate_relocation): <R_MIPS16_26>
	<R_MIPS_26, R_MICROMIPS_26_S1>: Drop the region bits of the
	reloc location from calculation, treat the addend as signed with
	local non-section symbols and enable overflow detection.

	ld/
	* testsuite/ld-mips-elf/jal-global-overflow-0.d: New test.
	* testsuite/ld-mips-elf/jal-global-overflow-1.d: New test.
	* testsuite/ld-mips-elf/jal-local-overflow-0.d: New test.
	* testsuite/ld-mips-elf/jal-local-overflow-1.d: New test.
	* testsuite/ld-mips-elf/jal-global-overflow.s: New test source.
	* testsuite/ld-mips-elf/jal-local-overflow.s: New test source.
	* testsuite/ld-mips-elf/mips-elf.exp: Run the new tests.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Update x86 CPU_XXX_FLAGS handling
@ 2016-05-27 17:19 sergiodj+buildbot
  2016-05-28 16:11 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-05-27 17:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1848e567343e9c50979453463f34e0a55ba892eb ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 1848e567343e9c50979453463f34e0a55ba892eb

Update x86 CPU_XXX_FLAGS handling

Support defining CPU_XXX_FLAGS with other CPU_XXX_FLAGS.  Update
CPU_XXX_FLAGS to enable more bits like x87 and SYSCALL.  Don't enable
MMX when enabling SSE, AVX or AVX512.  Don't disable AVX nor AVX512 when
disabling SSE.  Don't disable AVX512 when disabling AVX.  Disable F16C,
FMA, FMA4 and XOP when disabling AVX.  Add 87, no287, no387, no687,
nosse2, nosse3, nossse3, nosse4.1, nosse4.2, nosse4 and noavx2 directives
to x86 assembler.

TODO: Add more .noXXX, like .noavx512f, directives to x86 assembler.

gas/

	PR gas/20145
	* config/tc-i386.c (cpu_arch): Add 687.
	(cpu_noarch): Add no287, no387, no687, nosse2, nosse3, nossse3,
	nosse4.1, nosse4.2, nosse4 and noavx2.
	(parse_real_register): Check cpuregmmx instead of cpummx for MMX
	register.  Check cpuregxmm instead of cpusse for XMM register.
	Check cpuregymm instead of cpuavx for YMM register.  Check
	cpuregzmm/cpuregmask instead of cpuavx512f for ZMMM/mask register.
	* doc/c-i386.texi: Mention 687, no287, no387, no687, nosse2,
	nosse3, nossse3, nosse4.1, nosse4.2, nosse4 and noavx2.
	* testsuite/gas/i386/arch-10-prefetchw.d (as): Add mmx.
	* testsuite/gas/i386/arch-10.d (as): Likewise.
	* testsuite/gas/i386/arch-11.s: Add ".arch .mmx".
	* testsuite/gas/i386/i386.exp: Pass mmx to assembler for
	arch-10-3 and arch-10-4.  Run no87-3, nosse-4, nosse-5, noavx-3
	and noavx-4.
	* testsuite/gas/i386/no87-3.l: New file.
	* testsuite/gas/i386/no87-3.s: Likewise.
	* testsuite/gas/i386/noavx-3.l: Likewise.
	* testsuite/gas/i386/noavx-3.s: Likewise.
	* testsuite/gas/i386/noavx-4.d: Likewise.
	* testsuite/gas/i386/noavx-4.s: Likewise.
	* testsuite/gas/i386/nosse-4.l: Likewise.
	* testsuite/gas/i386/nosse-4.s: Likewise.
	* testsuite/gas/i386/nosse-5.d: Likewise.
	* testsuite/gas/i386/nosse-5.s: Likewise.

opcodes/

	PR gas/20145
	* i386-gen.c (cpu_flag_init): Update CPU_XXX_FLAGS.  Remove
	CpuMMX from CPU_SSE_FLAGS.  Remove AVX and AVX512 bits from
	CPU_ANY_SSE_FLAGS.  Remove AVX512 bits from CPU_ANY_AVX_FLAGS.
	Add CPU_XSAVE_FLAGS to CPU_XSAVEOPT_FLAGS, CPU_XSAVE_FLAGS and
	CpuXSAVEC.  Add CPU_AVX_FLAGS to CpuF16C.  Remove CpuMMX from
	CPU_AVX512F_FLAGS, CPU_AVX512CD_FLAGS, CPU_AVX512ER_FLAGS,
	CPU_AVX512PF_FLAGS, CPU_AVX512DQ_FLAGS and CPU_AVX512BW_FLAGS.
	Add CPU_SSE2_FLAGS to CPU_SHA_FLAGS.   Add CPU_ANY_287_FLAGS,
	CPU_ANY_387_FLAGS, CPU_ANY_687_FLAGS, CPU_ANY_SSE2_FLAGS,
	CPU_ANY_SSE3_FLAGS, CPU_ANY_SSSE3_FLAGS, CPU_ANY_SSE4_1_FLAGS,
	CPU_ANY_SSE4_2_FLAGS and CPU_ANY_AVX2_FLAGS.  Enable CpuRegMMX
	for MMX.  Enable CpuRegXMM for SSE, AVX and AVX512.  Enable
	CpuRegYMM for AVX and AVX512VL,  Enable CpuRegZMM and
	CpuRegMask for AVX512.
	(cpu_flags): Add CpuRegMMX, CpuRegXMM, CpuRegYMM, CpuRegZMM
	and CpuRegMask.
	(set_bitfield_from_cpu_flag_init): New function.
	(set_bitfield): Remove const on f.  Call
	set_bitfield_from_cpu_flag_init to handle CPU_XXX_FLAGS.
	* i386-opc.h (CpuRegMMX): New.
	(CpuRegXMM): Likewise.
	(CpuRegYMM): Likewise.
	(CpuRegZMM): Likewise.
	(CpuRegMask): Likewise.
	(i386_cpu_flags): Add cpuregmmx, cpuregxmm, cpuregymm, cpuregzmm
	and cpuregmask.
	* i386-init.h: Regenerated.
	* i386-tbl.h: Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Replace CpuAMD64/CpuIntel64 with AMD64/Intel64
@ 2016-05-27 15:15 sergiodj+buildbot
  2016-05-28 12:01 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-05-27 15:15 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e92bae62606702c1c07e095789ffed103e0e34c5 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: e92bae62606702c1c07e095789ffed103e0e34c5

Replace CpuAMD64/CpuIntel64 with AMD64/Intel64

AMD64 vs CpuIntel64 ISA should be handled similar as AT&T vs Intel
syntax.  Since cpu_flags isn't sorted by position, we need to check
the whole cpu_flags array for the maximum position when verifying
CpuMax.

gas/

	PR gas/20154
	* config/tc-i386.c (cpu_flags_match): Don't set cpuamd64 nor
	cpuintel64.
	(match_template): Check Intel64/AMD64 ISA.

opcodes/

	PR gas/20154
	* i386-gen.c (cpu_flags): Remove CpuAMD64 and CpuIntel64.
	(opcode_modifiers): Add AMD64 and Intel64.
	(main): Properly verify CpuMax.
	* i386-opc.h (CpuAMD64): Removed.
	(CpuIntel64): Likewise.
	(CpuMax): Set to CpuNo64.
	(i386_cpu_flags): Remove cpuamd64 and cpuintel64.
	(AMD64): New.
	(Intel64): Likewise.
	(i386_opcode_modifier): Add amd64 and intel64.
	(i386-opc.tbl): Replace CpuAMD64/CpuIntel64 with AMD64/Intel64
	on call and jmp.
	* i386-init.h: Regenerated.
	* i386-tbl.h: Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] gdb: Forward VALUE_LVAL when avoiding side effects for STRUCTOP_PTR
@ 2016-05-27 12:46 sergiodj+buildbot
  2016-05-27 15:03 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-05-27 12:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ac775bf4d35b7a2d5715e0ccf3d648d4670213fd ***

Author: Andrew Burgess <andrew.burgess@embecosm.com>
Branch: master
Commit: ac775bf4d35b7a2d5715e0ccf3d648d4670213fd

gdb: Forward VALUE_LVAL when avoiding side effects for STRUCTOP_PTR

Assume that we have a C program like this:

  struct foo_type
  {
    int var;
  } foo;

  struct foo_type *foo_ptr = &foo;

  int
  main ()
  {
    return foo_ptr->var;
  }

Then GDB should be able to evaluate the following, however, it currently
does not:

  (gdb) start
  ...
  (gdb) whatis &(foo_ptr->var)
  Attempt to take address of value not located in memory.

The problem is that in EVAL_AVOID_SIDE_EFFECTS mode,
eval.c:evaluate_subexp_standard always returns a not_lval value as the
result for a STRUCTOP_PTR operation. As a consequence, the rest of
the code believes that one cannot take the address of the returned
value.

This patch fixes STRUCTOP_PTR handling so that the VALUE_LVAL
attribute for the returned value is properly initialized.  After this
change, the above session becomes:

  (gdb) start
  ...
  (gdb) whatis &(foo_ptr->var)
  type = int *

This commit is largely the same as commit 2520f728b710 (Forward
VALUE_LVAL when avoiding side effects for STRUCTOP_STRUCT) but applied
to STRUCTOP_PTR rather than STRUCTOP_STRUCT.  Both of these commits are
building on top of commit ac1ca910d74d (Fixes for PR exp/15364).

gdb/ChangeLog:

	* eval.c (evaluate_subexp_standard): If EVAL_AVOID_SIDE_EFFECTS
	mode, forward the VALUE_LVAL attribute to the returned value in
	the STRUCTOP_PTR case.

gdb/testsuite/ChangeLog:

	* gdb.base/whatis.c: Extend the test case.
	* gdb.base/whatis.exp: Add additional tests.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Enable 64-bit archives in ar and ranlib
@ 2016-05-25 17:04 sergiodj+buildbot
  2016-05-25 17:19 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-05-25 17:04 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e6cc316af931911da20249e19f9342e5cf8aeeff ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: e6cc316af931911da20249e19f9342e5cf8aeeff

Enable 64-bit archives in ar and ranlib

Since existing ld and gold support the 64-bit (MIPS) ELF archives, we
can use the 64-bit (MIPS) ELF archives as 64-bit archives.  Since the
plugin target is used to create archive in plugin-enabled ar, we need
a way to enable 64-bit archives in the plugin target.  This patch adds
--enable-64-bit-archive to bfd to force 64-bit archives in ar and
ranlib.  Since both 64-bit MIPS and s390 ELF targets currently use
64-bit archives, 64-bit archives are enabled by default for them.
64-bit archive is generated automatically if the archive is too big.

Tested on Linux/x86 and Linux/x86-64 with existing ld and gold.

bfd/

	PR binutils/14625
	* archive.c (bfd_slurp_armap): Replace
	bfd_elf64_archive_slurp_armap with
	_bfd_archive_64_bit_slurp_armap.
	(bsd_write_armap): Call _bfd_archive_64_bit_write_armap if
	BFD64 is defined and the archive is too big.
	(coff_write_armap): Likewise.
	* archive64.c (bfd_elf64_archive_slurp_armap): Renamed to ...
	(_bfd_archive_64_bit_slurp_armap): This.
	(bfd_elf64_archive_write_armap): Renamed to ...
	(_bfd_archive_64_bit_write_armap): This.
	* configure.ac: Add --enable-64-bit-archive.
	(want_64_bit_archive): New.  Set to true by default for 64-bit
	MIPS and s390 ELF targets.
	(USE_64_BIT_ARCHIVE): New AC_DEFINE.
	* config.in: Regenerated.
	* configure: Likewise.
	* elf64-mips.c (bfd_elf64_archive_functions): Removed.
	(bfd_elf64_archive_slurp_armap): Likewise.
	(bfd_elf64_archive_write_armap): Likewise.
	(bfd_elf64_archive_slurp_extended_name_table): Likewise.
	(bfd_elf64_archive_construct_extended_name_table): Likewise.
	(bfd_elf64_archive_truncate_arname): Likewise.
	(bfd_elf64_archive_read_ar_hdr): Likewise.
	(bfd_elf64_archive_write_ar_hdr): Likewise.
	(bfd_elf64_archive_openr_next_archived_file): Likewise.
	(bfd_elf64_archive_get_elt_at_index): Likewise.
	(bfd_elf64_archive_generic_stat_arch_elt): Likewise.
	(bfd_elf64_archive_update_armap_timestamp): Likewise.
	* elf64-s390.c (bfd_elf64_archive_functions): Removed.
	(bfd_elf64_archive_slurp_armap): Likewise.
	(bfd_elf64_archive_write_armap): Likewise.
	(bfd_elf64_archive_slurp_extended_name_table): Likewise.
	(bfd_elf64_archive_construct_extended_name_table): Likewise.
	(bfd_elf64_archive_truncate_arname): Likewise.
	(bfd_elf64_archive_read_ar_hdr): Likewise.
	(bfd_elf64_archive_write_ar_hdr): Likewise.
	(bfd_elf64_archive_openr_next_archived_file): Likewise.
	(bfd_elf64_archive_get_elt_at_index): Likewise.
	(bfd_elf64_archive_generic_stat_arch_elt): Likewise.
	(bfd_elf64_archive_update_armap_timestamp): Likewise.
	* elfxx-target.h (TARGET_BIG_SYM): Use _bfd_archive_64_bit on
	BFD_JUMP_TABLE_ARCHIVE if USE_64_BIT_ARCHIVE is defined and
	bfd_elfNN_archive_functions isn't defined.
	(TARGET_LITTLE_SYM): Likewise.
	* libbfd-in.h (_bfd_archive_64_bit_slurp_armap): New prototype.
	(_bfd_archive_64_bit_write_armap): Likewise.
	(_bfd_archive_64_bit_slurp_extended_name_table): New macro.
	(_bfd_archive_64_bit_construct_extended_name_table): Likewise.
	(_bfd_archive_64_bit_truncate_arname): Likewise.
	(_bfd_archive_64_bit_read_ar_hdr): Likewise.
	(_bfd_archive_64_bit_write_ar_hdr): Likewise.
	(_bfd_archive_64_bit_openr_next_archived_file): Likewise.
	(_bfd_archive_64_bit_get_elt_at_index): Likewise.
	(_bfd_archive_64_bit_generic_stat_arch_elt): Likewise.
	(_bfd_archive_64_bit_update_armap_timestamp): Likewise.
	* libbfd.h: Regenerated.
	* plugin.c (plugin_vec): Use _bfd_archive_64_bit on
	BFD_JUMP_TABLE_ARCHIVE if USE_64_BIT_ARCHIVE is defined.

binutils/

	PR binutils/14625
	* NEWS: Mention --enable-64-bit-archive.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Skip an archive element if not added by linker
@ 2016-05-25 15:55 sergiodj+buildbot
  2016-05-25 16:15 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-05-25 15:55 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b95a0a3177bcf797c8f5ad6a7d276fb6275352b7 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: b95a0a3177bcf797c8f5ad6a7d276fb6275352b7

Skip an archive element if not added by linker

During archive rescan to resolve symbol references for files added by
LTO, linker add_archive_element callback is called to check if an
archive element should added.  After all IR symbols have been claimed,
linker won't claim new IR symbols and shouldn't add the LTO archive
element.  This patch updates linker add_archive_element callback to
return FALSE when seeing an LTO archive element during rescan and
changes ELF linker to skip such archive element.

bfd/

	PR ld/20103
	* cofflink.c (coff_link_check_archive_element): Return TRUE if
	linker add_archive_element callback returns FALSE.
	* ecoff.c (ecoff_link_check_archive_element): Likewise.
	* elf64-ia64-vms.c (elf64_vms_link_add_archive_symbols): Skip
	archive element if linker add_archive_element callback returns
	FALSE.
	* elflink.c (elf_link_add_archive_symbols): Likewise.
	* pdp11.c (aout_link_check_ar_symbols): Likewise.
	* vms-alpha.c (alpha_vms_link_add_archive_symbols): Likewise.
	* xcofflink.c (xcoff_link_check_dynamic_ar_symbols): Likewise.
	(xcoff_link_check_ar_symbols): Likewise.

ld/

	PR ld/20103
	* ldmain.c (add_archive_element): Don't claim new IR symbols
	after all IR symbols have been claimed.
	* plugin.c (plugin_call_claim_file): Remove no_more_claiming
	check.
	* testsuite/ld-plugin/lto.exp (pr20103): New proc.
	Run PR ld/20103 tests.
	* testsuite/ld-plugin/pr20103a.c: New file.
	* testsuite/ld-plugin/pr20103b.c: Likewise.
	* testsuite/ld-plugin/pr20103c.c: Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fortran, testsuite: Add testcases for nested structures.
@ 2016-05-25  7:51 sergiodj+buildbot
  2016-05-25 11:26 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-05-25  7:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 86d8a84882643db4d8c28cea8e4a358465cb11f5 ***

Author: Bernhard Heckel <bernhard.heckel@intel.com>
Branch: master
Commit: 86d8a84882643db4d8c28cea8e4a358465cb11f5

Fortran, testsuite: Add testcases for nested structures.

As as result of printing only the outer elements of nested structures,
some testcases have to be added to check for corner cases with VLA's.

2016-05-25  Bernhard Heckel  <bernhard.heckel@intel.com>

gdb/testsuite/Changelog:
	* gdb.fortran/vla-type.exp: Access elements in nested structs.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fortran, typeprint: Decrease level of details when printing elements of a structure.
@ 2016-05-25  7:40 sergiodj+buildbot
  2016-05-25 10:09 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-05-25  7:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e188eb36215c031304aa7d2630447e2d0726adf5 ***

Author: Bernhard Heckel <bernhard.heckel@intel.com>
Branch: master
Commit: e188eb36215c031304aa7d2630447e2d0726adf5

Fortran, typeprint: Decrease level of details when printing elements of a structure.

According to the typeprint's description, the level of details is
decreased by one for the typeprint of elements of a structure.

Before:
(gdb) ptype t3v
type = Type t3
    integer(kind=4) :: t3_i
    Type t2
        integer(kind=4) :: t2_i
        Type t1
            integer(kind=4) :: t1_i
            real(kind=4) :: t1_r
        End Type t1 :: t1_n
    End Type t2 :: t2_n
End Type t3

After:
(gdb) ptype t3v
type = Type t3
    integer(kind=4) :: t3_i
    Type t2 :: t2_n
End Type t3

2016-05-25  Bernhard Heckel  <bernhard.heckel@intel.com>

gdb/Changelog:
	* f-typeprint.c (f_type_print_base): Decrease show by one.

gdb/testsuite/Changelog:
	* gdb.fortran/type.f90: Add nested structures.
	* gdb.fortran/whatis-type.exp: Whatis/ptype nested structures.
	* gdb.fortran/derived-type.exp: Adapt expected output.
	* gdb.fortran/vla-type.exp: Adapt expected output.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fortran, testsuite: Use multi_line in whatis_type testcase.
@ 2016-05-25  7:07 sergiodj+buildbot
  2016-05-25  7:20 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-05-25  7:07 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3cd81d8df727cc961b9333d5e977718c622bf9c3 ***

Author: Bernhard Heckel <bernhard.heckel@intel.com>
Branch: master
Commit: 3cd81d8df727cc961b9333d5e977718c622bf9c3

Fortran, testsuite: Use multi_line in whatis_type testcase.

2016-05-25  Bernhard Heckel  <bernhard.heckel@intel.com>

gdb/testsuite/Changelog:
	* gdb.fortran/whatis_type.exp: Use multi_line.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] add nb_inplace_divide for python 2
@ 2016-05-24 16:24 sergiodj+buildbot
  2016-05-24 21:41 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-05-24 16:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e2b7f516fc688975ea22ad3cf2066c6972454fdc ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: e2b7f516fc688975ea22ad3cf2066c6972454fdc

add nb_inplace_divide for python 2

Python 2's PyNumberMethods has nb_inplace_divide, but Python 3 does
not.  This patch adds it for Python 2.

This buglet didn't cause much fallout because the only non-NULL entry
in value_object_as_number after this is for valpy_divide; and the
missing slot caused it to slide up to nb_floor_divide (where
nb_true_divide was intended).

2016-05-24  Tom Tromey  <tom@tromey.com>

	* python/py-value.c (value_object_as_number): Add
	nb_inplace_divide for Python 2.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [Linux] Avoid refetching core-of-thread if thread hasn't run
@ 2016-05-24 14:24 sergiodj+buildbot
  2016-05-24 16:40 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-05-24 14:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1ad3de988d2f41c72de66613c68ed78507a3abbd ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 1ad3de988d2f41c72de66613c68ed78507a3abbd

[Linux] Avoid refetching core-of-thread if thread hasn't run

Hacking the gdb.threads/attach-many-short-lived-threads.exp test to
spawn thousands of threads instead of dozens, I saw GDB having trouble
keeping up with threads being spawned too fast, when it tried to stop
them all.  This was because while gdb is doing that, it updates the
thread list to make sure no new thread has sneaked in that might need
to be paused.  It does this a few times until it sees no-new-threads
twice in a row.  The thread listing update itself is not that
expensive, however, in the Linux backend, updating the threads list
calls linux_common_core_of_thread for each LWP to record on which core
each LWP was last seen running, which opens/reads/closes a /proc file
for each LWP which becomes expensive when you need to do it for
thousands of LWPs.

perf shows gdb in linux_common_core_of_thread 44% of the time, in the
stop_all_threads -> update_thread_list path in this use case.

This patch simply makes linux_common_core_of_thread avoid updating the
core the thread is bound to if the thread hasn't run since the last
time we updated that info.  This makes linux_common_core_of_thread
disappear into the noise in the perf report.

gdb/ChangeLog:
2016-05-24  Pedro Alves  <palves@redhat.com>

	PR gdb/19828
	* linux-nat.c (linux_resume_one_lwp_throw): Clear the LWP's core
	field.
	(linux_nat_update_thread_list): Don't fetch the core if already
	known.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Linux native thread create/exit events support
@ 2016-05-24 14:06 sergiodj+buildbot
  2016-05-24 14:27 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-05-24 14:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT aa01bd3689d204ce3d657cf7eb17b8343d79a080 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: aa01bd3689d204ce3d657cf7eb17b8343d79a080

Linux native thread create/exit events support

A following patch (fix for gdb/19828) makes linux-nat.c add threads to
GDB's thread list earlier in the "attach" sequence, and that causes a
surprising regression on
gdb.threads/attach-many-short-lived-threads.exp on my machine.  The
extra "thread x exited" handling and traffic slows down that test
enough that GDB core has trouble keeping up with new threads that are
spawned while trying to stop existing ones.

I saw the exact same issue with remote/gdbserver a while ago and fixed
it in 65706a29bac5 (Remote thread create/exit events) so part of the
fix here is the exact same -- add support for thread created events to
gdb/linux-nat.c.  infrun.c:stop_all_threads enables those events when
it tries to stop threads, which ensures that new threads never get a
chance to themselves start new threads, thus fixing the race.

gdb/
2016-05-24  Pedro Alves  <palves@redhat.com>

	PR gdb/19828
	* linux-nat.c (report_thread_events): New global.
	(linux_handle_extended_wait): Report
	TARGET_WAITKIND_THREAD_CREATED if thread event reporting is
	enabled.
	(wait_lwp, linux_nat_filter_event): Report all thread exits if
	thread event reporting is enabled.  Remove comment.
	(filter_exit_event): New function.
	(linux_nat_wait_1): Use it.
	(linux_nat_thread_events): New function.
	(linux_nat_add_target): Install it as target_thread_events method.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Enable R_AARCH64_NONE for 64-bit code.
@ 2016-05-23 23:52 sergiodj+buildbot
  2016-05-24  0:10 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-05-23 23:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b7f28d873c8bb26500e46828d34445cebfab7fd4 ***

Author: Jim Wilson <jim.wilson@linaro.org>
Branch: master
Commit: b7f28d873c8bb26500e46828d34445cebfab7fd4

Enable R_AARCH64_NONE for 64-bit code.

	* elfnn-aarch64.c: Unconditionally enable R_AARCH64_NULL and
	R_AARCH64_NONE.  Use HOWTO64 for R_AARCH64_NULL.
	* relocs.c: Add BFD_RELOC_AARCH64_NULL.
	* bfd-in2.h: Regenerate.
	* libbfd.h: Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [ARC] Update instruction type and delay slot info.
@ 2016-05-23 16:44 sergiodj+buildbot
  2016-05-23 17:49 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-05-23 16:44 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d9eca1df01c0e6f7f22566c154e63b1df9315790 ***

Author: Claudiu Zissulescu <claziss@synopsys.com>
Branch: master
Commit: d9eca1df01c0e6f7f22566c154e63b1df9315790

[ARC] Update instruction type and delay slot info.

This patch corrects the instructioninformation passed into the
disassebler_info structure.

include/
2016-05-23  Claudiu Zissulescu  <claziss@synopsys.com>

	* opcode/arc.h (insn_subclass_t): Add COND.
	(flag_class_t): Add F_CLASS_EXTEND.

opcodes/
2016-05-23  Claudiu Zissulescu  <claziss@synopsys.com>

	* arc-dis.c (print_flags): Set branch_delay_insns, and insn_type
	information.
	(print_insn_arc): Set insn_type information.
	* arc-opc.c (C_CC): Add F_CLASS_COND.
	* arc-tbl.h (bbit0, bbit1): Update subclass to COND.
	(beq_s, bge_s, bgt_s, bhi_s, bhs_s): Likewise.
	(ble_s, blo_s, bls_s, blt_s, bne_s): Likewise.
	(breq, breq_s, brge, brhs, brlo, brlt): Likewise.
	(brne, brne_s, jeq_s, jne_s): Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Search for libutil-freebsd as alternative to libutil
@ 2016-05-23  8:08 sergiodj+buildbot
  2016-05-23  8:16 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-05-23  8:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 37773e7803b370802302719a48c9c46f64c602b4 ***

Author: Jon Boden <jon@ubuntubsd.org>
Branch: master
Commit: 37773e7803b370802302719a48c9c46f64c602b4

Search for libutil-freebsd as alternative to libutil

GDB needs kinfo_getvmmap() on GNU/kFreeBSD systems same as on
pure FreeBSD.  However on these systems the FreeBSD version of libutil
is renamed to libutil-freebsd.

2016-05-23  Jon Boden  <jon@ubuntubsd.org>

	* configure.ac: Search for libutil-freebsd as alternative to libutil.
	* configure: Re-generated.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Don't check R_386_GOT32 when setting need_convert_load
@ 2016-05-20 17:00 sergiodj+buildbot
  2016-05-20 17:12 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-05-20 17:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 52bf37dd91e5dd983ed20d1329293d077fe71e41 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 52bf37dd91e5dd983ed20d1329293d077fe71e41

Don't check R_386_GOT32 when setting need_convert_load

Since we no longer convert R_386_GOT32, don't check R_386_GOT32 when
setting need_convert_load.

	* elf32-i386.c (elf_i386_check_relocs): Don't check R_386_GOT32
	when setting need_convert_load.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix invalid implicit conversions from void *
@ 2016-05-19 13:44 sergiodj+buildbot
  2016-05-19 14:51 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-05-19 13:44 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bfb0d950a58edc4eb1f102174af38a364f4f43f7 ***

Author: Andreas Schwab <schwab@suse.de>
Branch: master
Commit: bfb0d950a58edc4eb1f102174af38a364f4f43f7

Fix invalid implicit conversions from void *

	* ia64-libunwind-tdep.c (libunwind_descr): Add cast from void *.
	(libunwind_frame_set_descr): Likewise.
	(libunwind_frame_cache): Likewise.
	(libunwind_frame_dealloc_cache): Likewise.
	(libunwind_frame_sniffer): Likewise.
	(libunwind_search_unwind_table): Likewise.
	(libunwind_sigtramp_frame_sniffer): Likewise.
	(libunwind_get_reg_special): Likewise.
	(libunwind_load): Likewise.
	* ia64-linux-nat.c (ia64_linux_fetch_register): Likewise.
	(ia64_linux_store_register): Likewise.
	(ia64_linux_xfer_partial): Likewise.
	* ia64-tdep.c (ia64_access_reg): Likewise.
	(ia64_access_fpreg): Likewise.
	(ia64_access_rse_reg): Likewise.
	(ia64_access_rse_fpreg): Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Remove unsupported `am34-*-linux*' target triplet
@ 2016-05-19 10:25 sergiodj+buildbot
  2016-05-19 12:42 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-05-19 10:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6b200de0f7a7008f74cde68fe87aa62b7729cd9a ***

Author: Maciej W. Rozycki <macro@imgtec.com>
Branch: master
Commit: 6b200de0f7a7008f74cde68fe87aa62b7729cd9a

Remove unsupported `am34-*-linux*' target triplet

The `am34-*-linux*' target cannot be configured for, `am34' is not a CPU
name recognized by `config.sub'.  It has never been, required code has
not been contributed to GNU config, neither before nor since the
addition of the target triplet to our configury with commit bfff16424942
("Add MN10300 linker relaxation support for symbol differences") back in
2007.  Also there is no difference in actual tool configuration between
the `am34-*-linux*' and `am33_2.0-*-linux*' targets, except from a
different executable prefix and tooldir name.

Given the above remove the target triplet from our configuration.

	bfd/
	* config.bfd: Remove `am34-*-linux*' support.

	ld/
	* configure.tgt: Remove `am34-*-linux*' support.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix ppc64le S-record test fail
@ 2016-05-19  5:14 sergiodj+buildbot
  2016-05-19  9:25 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-05-19  5:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9f284bf9da3ecc689405cb7b698c7714acdf1ab0 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 9f284bf9da3ecc689405cb7b698c7714acdf1ab0

Fix ppc64le S-record test fail

Segfaults on --defsym symbol (__stack_chk_fail in this instance).

	* elf64-ppc.c (ppc64_elf_branch_reloc): Check for NULL owner
	before dereferencing.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] MIPS/opcodes: Correct mixed MIPS16 and microMIPS disassembly
@ 2016-05-18 12:39 sergiodj+buildbot
  2016-05-19  4:32 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-05-18 12:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1401d2fe675c5b0634a97e84e6b094eea527e63e ***

Author: Maciej W. Rozycki <macro@imgtec.com>
Branch: master
Commit: 1401d2fe675c5b0634a97e84e6b094eea527e63e

MIPS/opcodes: Correct mixed MIPS16 and microMIPS disassembly

Mixing MIPS16 and microMIPS code in a single binary isn't usually
supported but GAS happily produces such code if requested.  However it
is not correctly disassembled even if a symbol table is available and
function symbols are correctly anotated with the ISA mode.  This is
because the ELF-header global microMIPS ASE flag takes precedence over
MIPS16 function annotation, causing them to be treated as regular MIPS
code.

Correct the problem by respecting function symbol anotation regardless
of the ELF-header flag.

	binutils/
	* testsuite/binutils-all/mips/mixed-mips16-micromips.d: New test.
	* testsuite/binutils-all/mips/mixed-mips16-micromips.s: New test
	source.
	* testsuite/binutils-all/mips/mips.exp: Run the new test.

	opcodes/
	* mips-dis.c (is_compressed_mode_p): Add `micromips_p' operand,
	replacing references to `micromips_ase' throughout.
	(_print_insn_mips): Don't use file-level microMIPS annotation to
	determine the disassembly mode with the symbol table.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] elf32-arm.c build breakage
@ 2016-05-18  6:45 sergiodj+buildbot
  2016-05-19  2:55 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-05-18  6:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7f9919700d0023db7d66fee9f437251a263f5d53 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 7f9919700d0023db7d66fee9f437251a263f5d53

elf32-arm.c build breakage

	* elf32-arm.c (elf32_arm_size_stubs): Free or cache local syms
	for each BFD.  Don't goto error_ret_free_local from outside loop.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix -exec-run not running asynchronously with mi-async on (PR gdb/18077)
@ 2016-05-18  1:09 sergiodj+buildbot
  2016-05-19  1:17 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-05-18  1:09 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 61c6156df6e3c638eb3bdb4a6e3d418a43a6eb70 ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: 61c6156df6e3c638eb3bdb4a6e3d418a43a6eb70

Fix -exec-run not running asynchronously with mi-async on (PR gdb/18077)

When doing -exec-run on a freshly started GDB, the only target on the
target stack at the time the dummy one.  When mi_async_p is called to
know whether the run should be async, it queries whether the current
target (dummy) supports async, and the answer is no.  The fix is to make
the code query the target that will be used for the run, which is not
necessarily the current target.

No regressions in the gdb.mi directory using the unix, native-gdbserver
and native-extended-gdbserver boards.  The test doesn't pass when
forcing maint set target-async off, obviously, since it makes mi-async
have no effect.  It doesn't seem like other tests are checking for that
eventuality, so I didn't in the new test.

gdb/ChangeLog:

	* mi/mi-main.c (run_one_inferior): Use run target to determine
	whether to run async or not.
	(mi_cmd_exec_run): Likewise.

gdb/testsuite/ChangeLog:

	* gdb.mi/mi-async-run.exp: New file.
	* gdb.mi/mi-async-run.c: New file.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Add Rust documentation
@ 2016-05-17 23:52 sergiodj+buildbot
  2016-05-18 22:40 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-05-17 23:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0bdfa368bc8dbea2f39706e34306c9b67883bbb1 ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 0bdfa368bc8dbea2f39706e34306c9b67883bbb1

Add Rust documentation

This patch adds documentation for the new Rust support in gdb.

2016-05-17  Tom Tromey  <tom@tromey.com>

	* NEWS: Add Rust item.

2016-05-17  Tom Tromey  <tom@tromey.com>

	* gdb.texinfo (Supported Languages): Mention Rust.  Update menu.
	(Rust): New node.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Add array start and end strings to generic_val_print_decorations
@ 2016-05-17 22:37 sergiodj+buildbot
  2016-05-17 23:58 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-05-17 22:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 00272ec4b0cc22c1b9d60d39ce7bf5b2d5512582 ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 00272ec4b0cc22c1b9d60d39ce7bf5b2d5512582

Add array start and end strings to generic_val_print_decorations

For Rust value-printing, I wanted to use generic_val_print_array, but
I also wanted to control the starting and ending strings.

This patch adds new strings to generic_val_print_decorations, updates
generic_val_print_array to use them, and updates all the existing
instances of generic_val_print_decorations.

2016-05-17  Tom Tromey  <tom@tromey.com>

	* valprint.h (struct generic_val_print_array) <array_start,
	array_end>: New fields.
	* valprint.c (generic_val_print_array): Add "decorations"
	parameter.  Use "array_start", "array_end".
	(generic_val_print) <TYPE_CODE_ARRAY>: Update.
	* p-valprint.c (p_decorations): Update.
	* m2-valprint.c (m2_decorations): Update.
	* f-valprint.c (f_decorations): Update.
	* c-valprint.c (c_decorations): Update.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Update gdb test suite for Rust
@ 2016-05-17 21:36 sergiodj+buildbot
  2016-05-18 18:54 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-05-17 21:36 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 67218854b1987d89593ccaf5feaf5b29b1b976f2 ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 67218854b1987d89593ccaf5feaf5b29b1b976f2

Update gdb test suite for Rust

This updates the gdb test suite for Rust.

2016-05-17  Tom Tromey  <tom@tromey.com>
	    Manish Goregaokar <manishsmail@gmail.com>

	* lib/rust-support.exp: New file.
	* lib/gdb.exp (skip_rust_tests): New proc.
	(build_executable_from_specs): Handle rust.
	* lib/future.exp (gdb_find_rustc): New proc.
	(gdb_default_target_compile): Handle rust.
	* gdb.rust/expr.exp: New file.
	* gdb.rust/generics.exp: New file.
	* gdb.rust/generics.rs: New file.
	* gdb.rust/methods.exp: New file.
	* gdb.rust/methods.rs: New file.
	* gdb.rust/modules.exp: New file.
	* gdb.rust/modules.rs: New file.
	* gdb.rust/simple.exp: New file.
	* gdb.rust/simple.rs: New file.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Add DW_LANG_Rust
@ 2016-05-17 17:58 sergiodj+buildbot
  2016-05-17 18:28 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-05-17 17:58 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5ff087ac1870878ad980503f5c8b60b6ffa32350 ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 5ff087ac1870878ad980503f5c8b60b6ffa32350

Add DW_LANG_Rust

include/
	* dwarf2.h (enum dwarf_source_language) <DW_LANG_Rust,
	DW_LANG_Rust_old>: New constants.

git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@235643 138bc75d-0d04-0410-961f-82ee72b054a4


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Accept valid one byte signed and unsigned values for the IMM8 operand.
@ 2016-05-13 20:38 sergiodj+buildbot
  2016-05-13 21:07 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-05-13 20:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1178da445ad5faf37f9cc2be3aaa69d916f10f62 ***

Author: Peter Bergner <bergner@vnet.ibm.com>
Branch: master
Commit: 1178da445ad5faf37f9cc2be3aaa69d916f10f62

Accept valid one byte signed and unsigned values for the IMM8 operand.

opcodes/
	* ppc-opc.c (IMM8): Use PPC_OPERAND_SIGNOPT.

gas/
	* testsuite/gas/ppc/power9.d <xxspltib>: Add additional operand tests.
	* testsuite/gas/ppc/power9.s: Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] ld -z combreloc reloc sorting
@ 2016-05-12 15:11 sergiodj+buildbot
  2016-05-12 15:58 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-05-12 15:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1997c9943a1979a7407f3c70ead92493a799e13e ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 1997c9943a1979a7407f3c70ead92493a799e13e

ld -z combreloc reloc sorting

PLT relocs don't appear in .rela.dyn, at least not when using
normal linker scripts.  However, if they do, then they ought to be
placed last rather than in the middle of other relocs.

	* elf-bfd.h (elf_reloc_type_class): Put reloc_class_plt last.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [AArch64] Remove redundant tls relax in elfNN_aarch64_final_link_relocate
@ 2016-05-11 11:26 sergiodj+buildbot
  2016-05-11 12:30 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-05-11 11:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4e7fbb34f0546360e86b56dcd32b4d6478662b41 ***

Author: Jiong Wang <jiong.wang@arm.com>
Branch: master
Commit: 4e7fbb34f0546360e86b56dcd32b4d6478662b41

[AArch64] Remove redundant tls relax in elfNN_aarch64_final_link_relocate

bfd/
  * elfnn-aarch64.c (elfNN_aarch64_final_link_relocate): Remove redundant
  aarch64_tls_transition check.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] fix up two issues with the removal of unused variables
@ 2016-05-11  1:45 sergiodj+buildbot
  2016-05-11  2:39 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-05-11  1:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT df140a0bc3140bca133cd7ced6e18903db69c396 ***

Author: Trevor Saunders <tbsaunde+binutils@tbsaunde.org>
Branch: master
Commit: df140a0bc3140bca133cd7ced6e18903db69c396

fix up two issues with the removal of unused variables

gdb/ChangeLog:

2016-05-10  Trevor Saunders  <tbsaunde+binutils@tbsaunde.org>

	* iq2000-tdep.c (iq2000_scan_prologue): Remove if that shouldn't guard
	anything.
	* linespec.c (add_sal_to_sals): Restore call to symtab_to_fullname.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Enable Intel RDPID instruction.
@ 2016-05-10 19:42 sergiodj+buildbot
  2016-05-10 23:38 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-05-10 19:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8bc526963edde8cf8789ce82072d05fd2bcc90c4 ***

Author: Alexander Fomin <alexander.fomin@intel.com>
Branch: master
Commit: 8bc526963edde8cf8789ce82072d05fd2bcc90c4

Enable Intel RDPID instruction.

This patch enables Intel RDPID instruction described in Intel64 and
IA-32 Architectures Software Developer's Manual, April 2016.

gas/

	* config/tc-i386.c (cpu_arch): Add RDPID.
	* doc/c-i386.texi: Document RDPID.

gas/testsuite/

	* gas/i386/i386.exp: Run RDPID tests.
	* gas/i386/prefix.d: Adjust.
	* gas/i386/rdpid.s: New test.
	* gas/i386/rdpid.d: Ditto.
	* gas/i386/rdpid-intel.d: Ditto.
	* gas/i386/x86-64-rdpid.s: Ditto.
	* gas/i386/x86-64-rdpid.d: Ditto.
	* gas/i386/x86-64-rdpid-intel.d: Ditto.

opcodes/

	* i386-dis.c (prefix_table): Add RDPID instruction.
	* i386-gen.c (cpu_flag_init): Add RDPID flag.
	(cpu_flags): Add RDPID bitfield.
	* i386-opc.h (enum): Add RDPID element.
	(i386_cpu_flags): Add RDPID field.
	* i386-opc.tbl: Add RDPID instruction.
	* i386-init.h: Regenerate.
	* i386-tbl.h: Regenerate.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Use getters/setters to access ARM branch type
@ 2016-05-10 18:49 sergiodj+buildbot
  2016-05-10 21:23 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-05-10 18:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 39d911fc3c6519799ca1af4365d4b56f9d71ca94 ***

Author: Thomas Preud'homme <thomas.preudhomme@arm.com>
Branch: master
Commit: 39d911fc3c6519799ca1af4365d4b56f9d71ca94

Use getters/setters to access ARM branch type

2016-05-10  Thomas Preud'homme  <thomas.preudhomme@arm.com>

bfd/
	* elf32-arm.c (elf32_arm_size_stubs): Use new macros
	ARM_GET_SYM_BRANCH_TYPE and ARM_SET_SYM_BRANCH_TYPE to respectively get
	and set branch type of a symbol.
	(bfd_elf32_arm_process_before_allocation): Likewise.
	(elf32_arm_relocate_section): Likewise and fix identation along the
	way.
	(allocate_dynrelocs_for_symbol): Likewise.
	(elf32_arm_finish_dynamic_symbol): Likewise.
	(elf32_arm_swap_symbol_in): Likewise.
	(elf32_arm_swap_symbol_out): Likewise.

gas/
	* config/tc-arm.c (arm_adjust_symtab): Use ARM_SET_SYM_BRANCH_TYPE to
	set branch type of a symbol.

gdb/
	* arm-tdep.c (arm_elf_make_msymbol_special): Use
	ARM_GET_SYM_BRANCH_TYPE to get branch type of a symbol.

include/
	* arm.h (enum arm_st_branch_type): Add new ST_BRANCH_ENUM_SIZE
	enumerator.
	(NUM_ENUM_ARM_ST_BRANCH_TYPE_BITS): New macro.
	(ENUM_ARM_ST_BRANCH_TYPE_BITMASK): Likewise.
	(ARM_SYM_BRANCH_TYPE): Replace by ...
	(ARM_GET_SYM_BRANCH_TYPE): This and ...
	(ARM_SET_SYM_BRANCH_TYPE): This in two versions depending on whether
	BFD_ASSERT is defined or not.

ld/
	* emultempl/armelf.em (gld${EMULATION_NAME}_finish): Use
	ARM_GET_SYM_BRANCH_TYPE to get branch type of a symbol.

opcodes/
	* arm-dis.c (get_sym_code_type): Use ARM_GET_SYM_BRANCH_TYPE to get
	branch type of a symbol.
	(print_insn): Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Allow extension availability to depend on several architecture bits
@ 2016-05-10 16:24 sergiodj+buildbot
  2016-05-10 17:12 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-05-10 16:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d942732e829030b8eab483dd48b979f8eed7c9e2 ***

Author: Thomas Preud'homme <thomas.preudhomme@arm.com>
Branch: master
Commit: d942732e829030b8eab483dd48b979f8eed7c9e2

Allow extension availability to depend on several architecture bits

2016-05-10  Thomas Preud'homme  <thomas.preudhomme@arm.com>

gas/
	* config/tc-arm.c (struct arm_option_extension_value_table): Make
	allowed_archs an array with 2 entries.
	(ARM_EXT_OPT): Adapt to only fill the first entry of allowed_archs.
	(ARM_EXT_OPT2): New macro filling the two entries of allowed_archs.
	(arm_extensions): Use separate entries in allowed_archs when several
	archs are allowed to use an extension and change ARCH_ANY in
	ARM_ARCH_NONE in allowed_archs.
	(arm_parse_extension): Check that, for each allowed_archs entry, all
	bits are set in the current architecture, ignoring ARM_ANY entries.
	(s_arm_arch_extension): Likewise.

include/
	* arm.h (ARM_FSET_CPU_SUBSET): Define macro.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Redundant hash table check
@ 2016-05-09  8:25 sergiodj+buildbot
  2016-05-09  9:08 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-05-09  8:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ae1bb197269ca8f7aa560168c0dfd0bb80730e0f ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: ae1bb197269ca8f7aa560168c0dfd0bb80730e0f

Redundant hash table check

	* elf64-ppc.c (ppc64_elf_init_stub_bfd): Remove redundant NULL check.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Strip global symbol defined in discarded section
@ 2016-05-06 17:03 sergiodj+buildbot
  2016-05-06 17:40 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-05-06 17:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 97196564c7e981bab7b968e19b171c5dfcb28c3c ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 97196564c7e981bab7b968e19b171c5dfcb28c3c

Strip global symbol defined in discarded section

When a global symbol is defined in COMDAT group, we shouldn't leave an
undefined symbol in symbol table when the symbol section is discarded
unless there is a reference to the symbol outside of COMDAT group.

bfd/

	PR ld/17550
	* elf-bfd.h (elf_link_hash_entry): Update comments for indx,
	documenting that indx == -3 if symbol is defined in a discarded
	section.
	* elflink.c (elf_link_add_object_symbols): Set indx to -3 if
	symbol is defined in a discarded section.
	(elf_link_output_extsym): Strip a global symbol defined in a
	discarded section.

ld/

	PR ld/17550
	* testsuite/ld-elf/pr17550-1.s: New file.
	* testsuite/ld-elf/pr17550-2.s: Likewise.
	* testsuite/ld-elf/pr17550-3.s: Likewise.
	* testsuite/ld-elf/pr17550-4.s: Likewise.
	* testsuite/ld-elf/pr17550a.d: Likewise.
	* testsuite/ld-elf/pr17550b.d: Likewise.
	* testsuite/ld-elf/pr17550c.d: Likewise.
	* testsuite/ld-elf/pr17550d.d: Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Initialize res in get_next_pcs_read_memory_unsigned_integer
@ 2016-05-05  9:13 sergiodj+buildbot
  2016-05-05  9:46 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-05-05  9:13 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9e78496443ec1525ee94c54249779639b4cded0b ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 9e78496443ec1525ee94c54249779639b4cded0b

Initialize res in get_next_pcs_read_memory_unsigned_integer

This patch initialize res to zero, otherwise, it may have some garbage
bits after the *the_target->read_memory call.

gdb/gdbserver:

2016-05-05  Yao Qi  <yao.qi@linaro.org>

	* linux-arm-low.c (get_next_pcs_read_memory_unsigned_integer):
	Initialize res to zero.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [ARC] Add SYNTAX_NOP and SYNTAX_1OP for extension instructions
@ 2016-05-04 15:43 sergiodj+buildbot
  2016-05-04 17:49 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-05-04 15:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 945e0f82dad31db89a107b496532886fe215c011 ***

Author: Claudiu Zissulescu <claziss@synopsys.com>
Branch: master
Commit: 945e0f82dad31db89a107b496532886fe215c011

[ARC] Add SYNTAX_NOP and SYNTAX_1OP for extension instructions

gas/
2016-05-03  Claudiu Zissulescu  <claziss@synopsys.com>

	* config/tc-arc.c (syntaxclass): Add SYNTAX_NOP and SYNTAX_1OP.
	(arc_extinsn): Handle new introduced syntax.
	* testsuite/gas/arc/textinsn1op.d: New file.
	* testsuite/gas/arc/textinsn1op.s: Likewise.
	* doc/c-arc.texi: Document SYNTAX_NOP and SYNTAX_1OP.

opcodes/
2016-05-03  Claudiu Zissulescu  <claziss@synopsys.com>

	* arc-ext.c (dump_ARC_extmap): Handle SYNATX_NOP and SYNTAX_1OP.
	(arcExtMap_genOpcode): Likewise.
	* arc-opc.c (arg_32bit_rc): Define new variable.
	(arg_32bit_u6): Likewise.
	(arg_32bit_limm): Likewise.

include/
2016-05-03  Claudiu Zissulescu  <claziss@synopsys.com>

	* opcode/arc.h (ARC_SYNTAX_1OP): Declare
	(ARC_SYNTAX_NOP): Likewsie.
	(ARC_OP1_MUST_BE_IMM): Update defined value.
	(ARC_OP1_IMM_IMPLIED): Likewise.
	(arg_32bit_rc, arg_32bit_u6, arg_32bit_limm): Declare.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Introduce procedure use_gdb_stub
@ 2016-05-04 13:48 sergiodj+buildbot
  2016-05-04 14:37 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-05-04 13:48 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8929ad8bbca9a8b036eba0397992d6f3b4d1966b ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: 8929ad8bbca9a8b036eba0397992d6f3b4d1966b

Introduce procedure use_gdb_stub

This patch introduces the use_gdb_stub procedure, which allows getting
the right value of the use_gdb_stub variable/property in any all
situations.

When calling it before the $use_gdb_stub global variable has been set,
it will return the value of the use_gdb_stub property from the board
file.  This happens when tests want to bail out early (even before gdb
has been started) when the current test setup is a stub.

Otherwise, it returns the value of the $use_gdb_stub global.

It's possible for these two to differ when a test file overrides the
value of the global.

gdb/testsuite/ChangeLog:

	* lib/gdb.exp (use_gdb_stub): New procedure.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] PR symtab/19914 fix handling of dwp + split debug
@ 2016-05-04  0:22 sergiodj+buildbot
  2016-05-04  4:39 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-05-04  0:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6c4474237ab3356b100ebbdd6ff1a8839745023d ***

Author: Doug Evans <dje@google.com>
Branch: master
Commit: 6c4474237ab3356b100ebbdd6ff1a8839745023d

PR symtab/19914 fix handling of dwp + split debug

	PR symtab/19914
	* dwarf2read.c (open_and_init_dwp_file): Look at backlink if objfile
	is separate debug file.

	testsuite/
	* gdb.dwarf2/dwp-sepdebug.c: New file.
	* gdb.dwarf2/dwp-sepdebug.exp: New file.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] PR 10549: MIPS/LD: Handle OSABI setting for STB_GNU_UNIQUE
@ 2016-05-03 23:21 sergiodj+buildbot
  2016-05-04  0:07 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-05-03 23:21 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6d6a648c0789fb227ee2adfb089fe0ce8174708d ***

Author: Maciej W. Rozycki <macro@imgtec.com>
Branch: master
Commit: 6d6a648c0789fb227ee2adfb089fe0ce8174708d

PR 10549: MIPS/LD: Handle OSABI setting for STB_GNU_UNIQUE

Add missing OSABI handling for MIPS/LD, complementing:

commit f64b2e8d60f277b705c96d4b4e585f5f7c847cc4
Author: Nick Clifton <nickc@redhat.com>
Date:   Mon Apr 11 08:13:22 2011 +0000

Adjust test coverage accordingly.

	bfd/
	PR 10549
	* elfxx-mips.c (_bfd_mips_elf_add_symbol_hook): Handle
	STB_GNU_UNIQUE.

	ld/
	PR 10549
	* testsuite/ld-unique/unique.exp: Also run for `mips*-*-*'.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix gdb/python/python.c use-after-free
@ 2016-05-03 12:30 sergiodj+buildbot
  2016-05-03 18:35 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-05-03 12:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 86f1abec458df24ea7d4a38a7b3e21861c5b9bd8 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 86f1abec458df24ea7d4a38a7b3e21861c5b9bd8

Fix gdb/python/python.c use-after-free

Valgrind shows:

 ==26964== Invalid read of size 1
 ==26964==    at 0x6E14100: __GI_strcmp (strcmp.S:180)
 ==26964==    by 0x6DB55AA: setlocale (setlocale.c:238)
 ==26964==    by 0x4E0455: _initialize_python() (python.c:1731)
 ==26964==    by 0x786731: initialize_all_files() (init.c:319)
 ==26964==    by 0x72EF0A: gdb_init(char*) (top.c:1929)
 ==26964==    by 0x60BCAC: captured_main(void*) (main.c:863)
 ==26964==    by 0x606AD5: catch_errors(int (*)(void*), void*, char*, return_mask) (exceptions.c:234)
 ==26964==    by 0x60C608: gdb_main(captured_main_args*) (main.c:1165)
 ==26964==    by 0x40CAEC: main (gdb.c:32)
 ==26964==  Address 0x81d30a0 is 0 bytes inside a block of size 181 free'd
 ==26964==    at 0x4C29CF0: free (vg_replace_malloc.c:530)
 ==26964==    by 0x6DB5B65: setname (setlocale.c:201)
 ==26964==    by 0x6DB5B65: setlocale (setlocale.c:388)
 ==26964==    by 0x4E037F: _initialize_python() (python.c:1712)
 ==26964==    by 0x786731: initialize_all_files() (init.c:319)
 ==26964==    by 0x72EF0A: gdb_init(char*) (top.c:1929)
 ==26964==    by 0x60BCAC: captured_main(void*) (main.c:863)
 ==26964==    by 0x606AD5: catch_errors(int (*)(void*), void*, char*, return_mask) (exceptions.c:234)
 ==26964==    by 0x60C608: gdb_main(captured_main_args*) (main.c:1165)
 ==26964==    by 0x40CAEC: main (gdb.c:32)

The problem is doing this:

  oldloc = setlocale (LC_ALL, NULL);
  setlocale (LC_ALL, "");
  ...
  setlocale (LC_ALL, oldloc);

I.e., the second setlocale call frees 'oldloc'.

>From http://pubs.opengroup.org/onlinepubs/9699919799/functions/setlocale.html :

 "The returned string pointer might be invalidated or the string
 content might be overwritten by a subsequent call to setlocale()."

gdb/ChangeLog:
2016-05-03  Pedro Alves <palves@redhat.com>

	PR python/20037
	* python/python.c (_initialize_python) [IS_PY3K]: xstrdup/xfree
	oldloc.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [AArch64] Also puts value in place for R_AARCH64_RELATIVE
@ 2016-05-03 11:27 sergiodj+buildbot
  2016-05-03 16:21 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-05-03 11:27 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1f56df9d0d5ad89806c24e71f296576d82344613 ***

Author: Jiong Wang <jiong.wang@arm.com>
Branch: master
Commit: 1f56df9d0d5ad89806c24e71f296576d82344613

[AArch64] Also puts value in place for R_AARCH64_RELATIVE

When handling absolute relocations for global symbols bind within the
shared object, AArch64 will generate one dynamic RELATIVE relocation,
but won't apply the value for this absolution relocations at static
linking stage. This is different from AArch64 gold linker and x86-64.

This is not a bug as AArch64 is RELA, there is only guarantee that
relocation addend is placed in the relocation entry.  But some
system softwares originally writen for x86-64 might assume AArch64
bfd linker gets the same behavior as x86-64, then they could take
advantage of this buy skipping those RELATIVE dynamic relocations
if the load address is the same as the static linking address.

This patch makes AArch64 BFD linker applies absolution relocations at
static linking stage for scenario described above.  Meanwhile old AArch64
android loader has a bug (PR19163) which relies on current linker behavior
as a workaround, so the same option --no-apply-dynamic-relocs added.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix generation of AArhc64 instruction table.
@ 2016-05-03 11:07 sergiodj+buildbot
  2016-05-03 15:19 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-05-03 11:07 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 20f55f3866ab70778d08fec2c09626cff9ed781d ***

Author: Szabolcs Nagy <szabolcs.nagy@arm.com>
Branch: master
Commit: 20f55f3866ab70778d08fec2c09626cff9ed781d

Fix generation of AArhc64 instruction table.

	* aarch64-gen.c (VERIFIER): Define.
	* aarch64-opc.c (VERIFIER): Define.
	(verify_ldpsw): Use static linkage.
	* aarch64-opc.h (verify_ldpsw): Remove.
	* aarch64-tbl.h: Use VERIFIER for verifiers.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix "-Wl,--dynamic-list" gdb/configure test
@ 2016-05-03  9:56 sergiodj+buildbot
  2016-05-03 13:04 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-05-03  9:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1b4f615e4087a3ae9feba5912312cdcabc25e6a5 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 1b4f615e4087a3ae9feba5912312cdcabc25e6a5

Fix "-Wl,--dynamic-list" gdb/configure test

The -Wl,--dynamic-list test is currently broken on Fedora 23, when you
configure with --with-python=python3.4.  We see:

 configure:13741: checking for the dynamic export flag
 configure:13796: gcc -o conftest -g3 -O0  -fno-strict-aliasing -DNDEBUG -fwrapv    -Wl,--dynamic-list=/home/pedro/gdb/mygit/src/gdb/proc-service.list conftest.c -ldl -lncurses -lm -ldl  -lpthread -ldl -lutil -lm -lpython3.4m -Xlinker -export-dynamic >&5
 conftest.c:182:30: fatal error: python3.4/Python.h: No such file or directory
 compilation terminated.
 configure:13796: $? = 1

The correct -I path is in PYTHON_CPPFLAGS:

 PYTHON_CPPFLAGS='-I/usr/include/python3.4m -I/usr/include/python3.4m'

(Other Python-related tests in the file are already doing this.)

gdb/ChangeLog:
2016-05-03  Pedro Alves  <palves@redhat.com>

	* configure.ac (checking for the dynamic export flag): Add
	$PYTHON_CPPFLAGS to CPPFLAGS.
	* configure: Regenerate.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [gdb] Fix -Wparentheses warnings
@ 2016-05-03  9:05 sergiodj+buildbot
  2016-05-03  9:47 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-05-03  9:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b631e59ba05af7c888838d3e2d6d408bfe60b57f ***

Author: Kyrylo Tkachov <kyrylo.tkachov@arm.com>
Branch: master
Commit: b631e59ba05af7c888838d3e2d6d408bfe60b57f

[gdb] Fix -Wparentheses warnings

2016-05-03  Kyrylo Tkachov  <kyrylo.tkachov@arm.com>

	* symfile.c (find_pc_overlay): Add braces to avoid -Wparentheses
	warning.
	(find_pc_mapped_section): Likewise.
	(list_overlays_command): Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix annota-input-while-running.exp remote check
@ 2016-05-02 17:20 sergiodj+buildbot
  2016-05-02 18:27 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-05-02 17:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 740feeaa2049d0f9a7e5928191124583a1a8c645 ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: 740feeaa2049d0f9a7e5928191124583a1a8c645

Fix annota-input-while-running.exp remote check

The comment says that we can't use runto_main here becore it doesn't
know how to handle annotation.  Instead, the test puts a breakpoint at
main and calls run by hand.  Therefore, it can't work with stub targets,
since they can't "run".  The check should be then changed to check the
use_gdb_stub variable instead of [is_remote target].

But as an alternative, we can just use runto_main and enable annotations
after, since the "run to main" part is not really part of what we want
to test.

I also removed the "set test..." line that is unused.

gdb/testsuite/ChangeLog:

	* gdb.base/annota-input-while-running.exp: Don't check for
	[is_remote target].  Enable annotations after running to main.
	Remove unused "set test..." line.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Pass GOT_RELOC to UNDEFINED_WEAK_RESOLVED_TO_ZERO
@ 2016-04-29 15:45 sergiodj+buildbot
  2016-04-29 16:35 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-04-29 15:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e62b9723fdfcf655ecbd46ea455567593e333f47 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: e62b9723fdfcf655ecbd46ea455567593e333f47

Pass GOT_RELOC to UNDEFINED_WEAK_RESOLVED_TO_ZERO

When UNDEFINED_WEAK_RESOLVED_TO_ZERO is checked to convert load via
GOT, has_got_reloc is always TRUE.  This patch adds GOT_RELOC, which
is TRUE in x86 convert_load, to UNDEFINED_WEAK_RESOLVED_TO_ZERO.

	* elf32-i386.c (UNDEFINED_WEAK_RESOLVED_TO_ZERO): Take GOT_RELOC
	and replace (EH)->has_got_reloc with GOT_RELOC.
	(elf_i386_fixup_symbol): Pass has_got_reloc to
	UNDEFINED_WEAK_RESOLVED_TO_ZERO.
	(elf_i386_allocate_dynrelocs): Likewise.
	(elf_i386_relocate_section): Likewise.
	(elf_i386_finish_dynamic_symbol): Likewise.
	(elf_i386_convert_load): Pass TRUE to
	UNDEFINED_WEAK_RESOLVED_TO_ZERO.
	* elf64-x86-64.c (UNDEFINED_WEAK_RESOLVED_TO_ZERO): Take
	GOT_RELOC and replace (EH)->has_got_reloc with GOT_RELOC.
	(elf_x86_64_fixup_symbol): Pass has_got_reloc to
	UNDEFINED_WEAK_RESOLVED_TO_ZERO.
	(elf_x86_64_allocate_dynrelocs): Likewise.
	(elf_x86_64_relocate_section): Likewise.
	(elf_x86_64_finish_dynamic_symbol): Likewise.
	(elf_x86_64_convert_load): Pass TRUE to
	UNDEFINED_WEAK_RESOLVED_TO_ZERO.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] X86-64: Set check_relocs_failed on error
@ 2016-04-29 12:01 sergiodj+buildbot
  2016-04-29 12:43 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-04-29 12:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT afd9acee15d55fccf2a25b72c99303f7cbaaa1c2 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: afd9acee15d55fccf2a25b72c99303f7cbaaa1c2

X86-64: Set check_relocs_failed on error

When checking relocations, set check_relocs_failed on error.

	* elf64-x86-64.c (elf_x86_64_check_relocs): Set
	check_relocs_failed on error.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Don't show deprecated commands in help
@ 2016-04-28 18:29 sergiodj+buildbot
  2016-04-28 20:56 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-04-28 18:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0400cf2f56c41896ecf52b88baa1d6178eb10432 ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: 0400cf2f56c41896ecf52b88baa1d6178eb10432

Don't show deprecated commands in help

Just like completion doesn't show deprecated commands, I think that help
should not list them, so that we don't incite users to use them.

gdb/ChangeLog:

	* cli/cli-decode.c (help_cmd_list): Do not list commands that
	are deprecated.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] MIPS/Linux: Also recognize TRAP_BRKPT and TRAP_HWBKPT
@ 2016-04-15 23:19 sergiodj+buildbot
  2016-04-15 23:57 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-04-15 23:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 77770d832135a252d22eb95166c5ccfd40ca6a69 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 77770d832135a252d22eb95166c5ccfd40ca6a69

MIPS/Linux: Also recognize TRAP_BRKPT and TRAP_HWBKPT

This makes the MIPS Linux backends recognize TRAP_BRKPT and
TRAP_HWBKPT in siginfo.si_code in addition to SI_KERNEL, since Linux
4.6 now reports the finer-grained si_code values too.

Refs:
 https://sourceware.org/ml/gdb-patches/2016-02/msg00756.html
 https://sourceware.org/ml/gdb-patches/2016-04/msg00090.html

On kernels that report SI_KERNEL (<= 4.5), we'll enter the "ambiguous"
path of save_stop_reason:

	  if (GDB_ARCH_IS_TRAP_BRKPT (siginfo.si_code)
	      && GDB_ARCH_IS_TRAP_HWBKPT (siginfo.si_code))
	    {
	      /* The si_code is ambiguous on this arch -- check debug
		 registers.  */
	      if (!check_stopped_by_watchpoint (lp))
		lp->stop_reason = TARGET_STOPPED_BY_SW_BREAKPOINT;
	    }

while on kernels that report the finer-grained si_code values (>= 4.6),
we'll enter the corresponding branches:

	  else if (GDB_ARCH_IS_TRAP_BRKPT (siginfo.si_code))
	    {
	    }
	  else if (GDB_ARCH_IS_TRAP_HWBKPT (siginfo.si_code))
	    {
	      ...

gdb/ChangeLog:
2016-04-15  Pedro Alves  <palves@redhat.com>

	* nat/linux-ptrace.h [__mips__] (GDB_ARCH_IS_TRAP_BRKPT): Also
	accept TRAP_BRKPT.
	 [__mips__] (GDB_ARCH_IS_TRAP_HWBKPT): Also accept TRAP_HWBKPT.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix copying Solaris binaries with objcopy.
@ 2016-04-14 11:19 sergiodj+buildbot
  2016-04-14 12:07 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-04-14 11:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 84865015459b4e9e8ac67f9b91617fbd856d5119 ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: 84865015459b4e9e8ac67f9b91617fbd856d5119

Fix copying Solaris binaries with objcopy.

	PR target/19938
bfd	* elf-bbfd.h (struct elf_backend_data): New field:
	elf_strtab_flags.
	New field: elf_backend_set_special_section_info_and_link
	* elfxx-target.h (elf_backend_strtab_flags): Define if not already
	defined.
	(elf_backend_set_special_section_info_and_link): Define if not
	already defined.
	(elfNN_bed): Use elf_backend_set_special_section_info_and_link and
	elf_backend_strtab_flags macros to initialise fields in structure.
	* elf.c (_bfd_elf_make_section_from_shdr): Check for SHF_STRINGS
	being set even if SHF_MERGE is not set.
	(elf_fake_sections): Likewise.
	(section_match): New function.  Matches two ELF sections based
	upon fixed characteristics.
	(find_link): New function.  Locates a section in a BFD that
	matches a section in a different BFD.
	(_bfd_elf_copy_private_bfd_data): Copy the sh_info and sh_link
	fields of reserved sections.
	(bfd_elf_compute_section_file_positions): Set the flags for the
	.shstrtab section based upon the elf_strtab_flags field in the
	elf_backend_data structure.
	(swap_out_syms): Likewise for the .strtab section.
	* elflink.c (bfd_elf_final_link): Set the flags for the
	.strtab section based upon the elf_strtab_flags field in the
	elf_backend_data structure.
	* elf32-i386.c (elf32_i386_set_special_info_link): New function.
	(elf_backend_strtab_flags): Set to SHF_STRINGS for Solaris
	targets.
	(elf_backend_set_special_section_info_and_link): Define for
	Solaris targets.
	* elf32-sparc.c: Likewise.
	* elf64-x86-64.c: Likewise.

binutils* testsuite/binutils-all/i386/compressed-1b.d: Allow for the
	string sections possibly having the SHF_STRINGS flag bit set.
	* testsuite/binutils-all/i386/compressed-1c.d: Likewise.
	* testsuite/binutils-all/readelf.s: Likewise.
	* testsuite/binutils-all/readelf.s-64: Likewise.
	* testsuite/binutils-all/x86-64/compressed-1b.d: Likewise.
	* testsuite/binutils-all/x86-64/compressed-1c.d: Likewise.

gas	* testsuite/gas/i386/ilp32/x86-64-unwind.d: Allow for the string
	sections possibly having the SHF_STRINGS flag bit set.
	* testsuite/gas/i386/x86-64-unwind.d: Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Debugging without a binary (regression)
@ 2016-04-13 20:40 sergiodj+buildbot
  2016-04-14  9:31 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-04-13 20:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 57d1de9cf3ba8dd98eaf4a3d131c05ec4c49779d ***

Author: Luis Machado <lgustavo@codesourcery.com>
Branch: master
Commit: 57d1de9cf3ba8dd98eaf4a3d131c05ec4c49779d

Debugging without a binary (regression)

When we attempt to debug a process using GDBserver in standard remote mode
without a symbol file on GDB's end, we may run into an issue where GDB cuts
the connection attempt short due to an error. The error is caused by not
being able to open a symbol file, like so:

--

(gdb) set sysroot
(gdb) tar rem :2345
Remote debugging using :2345
/proc/23769/exe: Permission denied.
(gdb) i r
The program has no registers now.
(gdb)

It should've been like this:

(gdb) set sysroot
(gdb) tar rem :2345
Remote debugging using :2345
warning: /tmp/symbol-file: Permission denied.
0xf7ddb2d0 in ?? ()
(gdb) i r
eax            0x0  0
ecx            0x0  0
edx            0x0  0
ebx            0x0  0
esp            0xffffdfa0 0xffffdfa0
ebp            0x0  0x0
esi            0x0  0
edi            0x0  0
eip            0xf7ddb2d0 0xf7ddb2d0
eflags         0x200  [ IF ]
cs             0x33 51
ss             0x2b 43
ds             0x0  0
es             0x0  0
fs             0x0  0
gs             0x0  0
(gdb)

This is caused by a couple of function calls within exec_file_locate_attach
that can potentially throw errors.

The following patch guards both exec_file_attach and symbol_file_add_main to
prevent the errors from disrupting the connection process.

There was also a case where native GDB tripped on this problem, but it was
mostly fixed by bf74e428bca61022bd5cdf6bf28789a184748b4d.

Regression-tested on x86-64/Ubuntu.

gdb/ChangeLog:

2016-04-13  Luis Machado  <lgustavo@codesourcery.com>

	* exec.c (exec_file_locate_attach): Guard a couple functions
	that can throw errors.
	(exception_print_same): New helper function.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Eliminate immediate_quit
@ 2016-04-13  6:32 sergiodj+buildbot
  2016-04-13 21:58 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-04-13  6:32 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 585a46a2d01d25181926329f258f1d1374f93e99 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 585a46a2d01d25181926329f258f1d1374f93e99

Eliminate immediate_quit

This finally gets rid of immediate_quit (and surrounding
infrustruture), as nothing sets it anymore.

gdb_call_async_signal_handler was only necessary in order to handle
immediate_quit.  We can just call mark_async_signal_handler directly
on all hosts now.

In turn, we can clean up mingw-hdep.c's gdb_select a bit, as
sigint_event / sigint_handler is no longer needed.

gdb/ChangeLog:
2016-04-12  Pedro Alves  <palves@redhat.com>

	* defs.h: Update comments on SIGINT handling.
	(immediate_quit): Delete declaration.
	* event-loop.c (call_async_signal_handler): Delete.
	* event-loop.h (call_async_signal_handler): Delete declaration.
	(mark_async_signal_handler): Update comments.
	(gdb_call_async_signal_handler): Delete declaration.
	* event-top.c (handle_sigint): Call mark_async_signal_handler
	instead of gdb_call_async_signal_handler.
	* exceptions.c (prepare_to_throw_exception): Remove reference to
	immediate_quit.
	(exception_fprintf): Remove comments about immediate_quit.
	* mingw-hdep.c (sigint_event, sigint_handler): Delete.
	(gdb_select): Don't wait on sigint_event.
	(gdb_call_async_signal_handler): Delete.
	(_initialize_mingw_hdep): Delete.
	* posix-hdep.c (gdb_call_async_signal_handler): Delete.
	* utils.c (immediate_quit): Delete.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Use target_terminal_ours_for_output in MI
@ 2016-04-13  5:01 sergiodj+buildbot
  2016-04-13 19:13 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-04-13  5:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5fe966540d6b748f825774868463003700f0c878 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 5fe966540d6b748f825774868463003700f0c878

Use target_terminal_ours_for_output in MI

The MI code only does output, so leave raw/cooked mode alone, as well
as the SIGINT handler.  Restore terminal settings after output, while
at it.  Also, a couple events missed calling target_terminal_ours
before output, even.

gdb/ChangeLog:
2016-04-12  Pedro Alves  <palves@redhat.com>

	* mi/mi-interp.c (mi_new_thread): Put
	target_terminal_ours_for_output in effect while outputting.
	(mi_thread_exit): Use target_terminal_ours_for_output instead of
	target_terminal_ours.
	(mi_record_changed, mi_inferior_added, mi_inferior_appeared)
	(mi_inferior_exit, mi_inferior_removed, mi_traceframe_changed)
	(mi_tsv_created, mi_tsv_deleted, mi_tsv_modified)
	(mi_breakpoint_created, mi_breakpoint_deleted)
	(mi_breakpoint_modified, mi_solib_loaded, mi_solib_unloaded)
	(mi_command_param_changed, mi_memory_changed)
	(report_initial_inferior): Use target_terminal_ours_for_output
	instead of target_terminal_ours.  Restore terminal settings.
	* mi/mi-main.c (mi_execute_command): Use
	target_terminal_ours_for_output instead of target_terminal_ours.
	Restore terminal settings.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Use target_terminal_ours_for_output in exceptions.c
@ 2016-04-13  2:29 sergiodj+buildbot
  2016-04-13 14:36 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-04-13  2:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 481ac8c9bbbfc4b7506dfdb4a5b92b859d5c47d9 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 481ac8c9bbbfc4b7506dfdb4a5b92b859d5c47d9

Use target_terminal_ours_for_output in exceptions.c

We're only doing output here, so leave raw/cooked mode alone, as well
as the SIGINT handler.

Restore terminal settings after output, while at it.

gdb/ChangeLog:
2016-04-12  Pedro Alves  <palves@redhat.com>

	* exceptions.c (print_flush): Use target_terminal_ours_for_output
	instead of target_terminal_ours, and restore target terminal with
	a cleanup.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix inconsistent handling of EINTR in ser-*.c backends
@ 2016-04-13  2:05 sergiodj+buildbot
  2016-04-13 12:00 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-04-13  2:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 75ee59252d49dffb017905125cdf826f89a6baf9 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 75ee59252d49dffb017905125cdf826f89a6baf9

Fix inconsistent handling of EINTR in ser-*.c backends

- If serial->write_prim returns EINTR, ser_bas_write returns it to the
  caller.  This just looks wrong to me -- part of the output may have
  already been sent, and there's no way for the caller to know that,
  and thus no way for a caller to handle a partial write correctly.

- While ser-unix.c:ser_unix_read_prim retries on EINTR,
  ser-tcp.c:net_read_prim does not.

This commit moves EINTR handling to the ser_base_write and
ser_base_readchar level, so all serial backends (at least those that
use it) end up handling EINTR consistently.

gdb/ChangeLog:
2016-04-12  Pedro Alves  <palves@redhat.com>

	* ser-base.c (fd_event): Retry read_prim on EINTR.
	(do_ser_base_readchar): Retry read_prim on EINTR.
	(ser_base_write): Retry write_prim on EINTR.
	* ser-unix.c (ser_unix_read_prim): Don't retry on EINTR here.
	(ser_unix_write_prim): Remove comment.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Use target_terminal_ours_for_output in warning/internal_error
@ 2016-04-12 20:57 sergiodj+buildbot
  2016-04-13 16:39 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-04-12 20:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c5ac15402a894e87a118526a066880f596b3c78d ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: c5ac15402a894e87a118526a066880f596b3c78d

Use target_terminal_ours_for_output in warning/internal_error

We're only doing output here, so leave raw/cooked mode alone, as well
as the SIGINT handler.

And restore terminal settings, while at it.

gdb/ChangeLog:
2016-04-12  Pedro Alves  <palves@redhat.com>

	* utils.c (vwarning, internal_vproblem): Use
	make_cleanup_restore_target_terminal and
	target_terminal_ours_for_output.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Make Python use a struct serial event
@ 2016-04-12 20:54 sergiodj+buildbot
  2016-04-13  1:16 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-04-12 20:54 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6eddd09a12e752c08f55e62fbb30d42058a6b1ea ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 6eddd09a12e752c08f55e62fbb30d42058a6b1ea

Make Python use a struct serial event

Now that we have an abstract for wakeable events, use it instead of a
(heavier) serial pipe.

gdb/ChangeLog:
2016-04-12  Pedro Alves  <palves@redhat.com>

	* python/python.c: Include "ser-event.h".
	(gdbpy_event_fds): Delete.
	(gdbpy_serial_event): New.
	(gdbpy_run_events): Change prototype.  Use serial_event_clear
	instead of serial_readchar.
	(gdbpy_post_event): Use serial_event_set instead of serial_write.
	(gdbpy_initialize_events): Use make_serial_event instead of
	serial_pipe.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Inline command_loop in read_command_line
@ 2016-04-12 16:45 sergiodj+buildbot
  2016-04-12 17:51 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-04-12 16:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT faa4ebe148cfe83f06d881cfc80d95575d3bf746 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: faa4ebe148cfe83f06d881cfc80d95575d3bf746

Inline command_loop in read_command_line

read_command_line is the only caller, and here we can assume we're
reading a regular file, not stdin.

gdb/ChangeLog:
2016-04-12  Pedro Alves  <palves@redhat.com>

	* top.c (read_command_file): Inline command_loop here.
	(command_loop): Delete.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] MIPS/opcodes: Fix undecoded MIPS16 extended instruction bit disassembly
@ 2016-04-11 17:20 sergiodj+buildbot
  2016-04-11 18:00 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-04-11 17:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 92708ceca544456c26b4b82e2e7fc8afcf1641c8 ***

Author: Maciej W. Rozycki <macro@imgtec.com>
Branch: master
Commit: 92708ceca544456c26b4b82e2e7fc8afcf1641c8

MIPS/opcodes: Fix undecoded MIPS16 extended instruction bit disassembly

Correct the disassembly of hardware don't cares in MIPS16 extended
instructions.  Rather than e.g.:

   0:	f008 0231 	addiu	v0,sp,16433
   4:	f520 3260 	sll	v0,v1,-12

print:

   0:	f008 0231 	addiu	v0,sp,16401
   4:	f520 3260 	sll	v0,v1,20

respectively instead.

	opcodes/
	* mips-dis.c (print_mips16_insn_arg): Mask unused extended
	instruction bits out.

	binutils/
	* testsuite/binutils-all/mips/mips16-undecoded.d: New test.
	* testsuite/binutils-all/mips/mips16-undecoded.s: New test
	source.
	* testsuite/binutils-all/mips/mips.exp: Run the new test.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Make gdb.server/solib-list.exp work for remote targets
@ 2016-04-08 23:05 sergiodj+buildbot
  2016-04-08 23:40 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-04-08 23:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f48e22e3f2fdbe540a807b3ef2e9b5d3b08616e3 ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: f48e22e3f2fdbe540a807b3ef2e9b5d3b08616e3

Make gdb.server/solib-list.exp work for remote targets

There are a few small changes needed to make it work with a real remote
target.

 - Remove the [is_remote target] check.
 - Remove soname setting when building the lib, it's done by default now
   anyway.
 - In the compilation of the executable, pass the shared lib using the
   shlib option, so that RPATH is set.
 - Download the program to the target using gdb_remote_download, and
   record the remote path.  Remove loading of the program using
   gdb_load_shlibs, which was not really appropriate anyway.
 - Run the remote path through readlink (see comment in the code).
 - Start gdbserver with the remote path.

Also, don't set executable and objfile variables, as they are unused.

Tested with native, native-gdbserver, native-extended-gdbserver, and a
remote gdbserver.

gdb/testsuite/ChangeLog:

	* gdb.server/solib-list.exp: Remove is_remote check.
	Pass shlib= to gdb_compile.  Don't link shared library with
	-soname.  Call gdb_remote_download instead of gdb_load_shlibs.
	Run binary filename through "readlink -f" on the target.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] value: Make accessor methods' parameters const-correct
@ 2016-04-08 18:24 sergiodj+buildbot
  2016-04-08 19:17 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-04-08 18:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4bf7b526bed1c86b1f20b18e642865f446751e06 ***

Author: Martin Galvan <martin.galvan@tallertechnologies.com>
Branch: master
Commit: 4bf7b526bed1c86b1f20b18e642865f446751e06

value: Make accessor methods' parameters const-correct

I did a quick pass over value.c and value.h and made some of the accessor methods'
pass-by-reference parameters const-correct. Besides the obvious benefits, this is
required if we want to use them on values that are already declared as const
(such as the parameters to lval_funcs).

There's probably a lot more stuff that can be made const, here and elsewhere.

gdb/ChangeLog:
2016-04-08  Martin Galvan  <martin.galvan@tallertechnologies.com>

    * value.c (value_next): Make pass-by-reference parameters const-correct.
    (value_parent): Likewise.
    (value_enclosing_type): Likewise.
    (value_lazy): Likewise.
    (value_stack): Likewise.
    (value_embedded_offset): Likewise.
    (value_pointed_to_offset): Likewise.
    (value_raw_address): Likewise.
    (deprecated_value_modifiable): Likewise.
    (value_free_to_mark): Likewise.
    (value_release_to_mark): Likewise.
    (internalvar_name): Likewise.
    (readjust_indirect_value_type): Likewise.
    (value_initialized): Likewise.
    * value.h (value_next): Likewise.
    (value_parent): Likewise.
    (value_enclosing_type): Likewise.
    (value_lazy): Likewise.
    (value_stack): Likewise.
    (value_embedded_offset): Likewise.
    (value_pointed_to_offset): Likewise.
    (value_raw_address): Likewise.
    (deprecated_value_modifiable): Likewise.
    (value_free_to_mark): Likewise.
    (value_release_to_mark): Likewise.
    (internalvar_name): Likewise.
    (readjust_indirect_value_type): Likewise.
    (value_initialized): Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] gas/arc: Handle multiple arc_opcode chains for same mnemonic
@ 2016-04-07 17:52 sergiodj+buildbot
  2016-04-07 19:55 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-04-07 17:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1328504b287b2c284419d989e0d05e7d6d3ffa59 ***

Author: Andrew Burgess <andrew.burgess@embecosm.com>
Branch: master
Commit: 1328504b287b2c284419d989e0d05e7d6d3ffa59

gas/arc: Handle multiple arc_opcode chains for same mnemonic

This commit completes support for having multiple instructions with the
same mnemonic in non-contiguous blocks within the arc_opcodes table.

The commit adds an iterator mechanism for the arc_opcode_hash_entry
structure, which is then used in find_opcode_match to consider all
arc_opcode entries with the same mnemonic, even when these instructions
are stored in non-contiguous blocks.

I extend the comment on the arc_opcodes table to discuss how entries
within the table are organised, and to mention how instructions can be
split into multiple groups if needed, but that the table is still
searched in table order.

There should be no user visible changes after this commit.

gas/ChangeLog:

	* config/tc-arc.c (struct arc_opcode_hash_entry_iterator): New
	structure.
	(arc_opcode_hash_entry_iterator_init): New function.
	(arc_opcode_hash_entry_iterator_next): New function.
	(find_opcode_match): Iterate over all arc_opcode entries
	referenced by the arc_opcode_hash_entry passed in as a parameter.

opcodes/ChangeLog:

	* arc-opc.c (arc_opcodes): Extend comment to discus table layout.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix gdb.reverse/next-reverse-bkpt-over-sr.exp
@ 2016-04-07 16:55 sergiodj+buildbot
  2016-04-07 18:20 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-04-07 16:55 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bde475616e3fdb6d41c047956aaf627fbf34a85d ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: bde475616e3fdb6d41c047956aaf627fbf34a85d

Fix gdb.reverse/next-reverse-bkpt-over-sr.exp

I see the fail on aarch64-linux,

(gdb) reverse-next

Breakpoint 2, callee () at /home/yao/SourceCode/gnu/gdb/git/gdb/testsuite/gdb.reverse/step-reverse.c:26^M
26        myglob++; return 0;   /* ARRIVED IN CALLEE */
(gdb) FAIL: gdb.reverse/next-reverse-bkpt-over-sr.exp: reverse-next over call trips user breakpoint at function entry

The test expects program stops at line 25, but program stops at line 26.

(gdb) maintenance info line-table
objfile: /scratch/yao/gdb/build-git/aarch64-linux-gnu/gdb/testsuite/outputs/gdb.reverse/next-reverse-bkpt-over-sr/next-reverse-bkpt-over-sr ((struct objfile *) 0x613000002880)
compunit_symtab: ((struct compunit_symtab *) 0x621000121760)
symtab: /home/yao/SourceCode/gnu/gdb/git/gdb/testsuite/gdb.reverse/step-reverse.c ((struct symtab *) 0x6210001217e0)
linetable: ((struct linetable *) 0x6210001520d0):
INDEX    LINE ADDRESS
0          25 0x0000000000400890
1          26 0x0000000000400890
2          27 0x00000000004008b0

(gdb) disassemble callee
Dump of assembler code for function callee:
   0x0000000000400890 <+0>:     adrp    x0, 0x410000
   0x0000000000400894 <+4>:     add     x0, x0, #0xcac

the line-table show that the first instruction of function callee is
mapped line 25 and 26.  I am not sure the line-table is correct, but
it is not the point of this test.  The goal of this test is to test
program hits the breakpoint on the first instruction of function after
'reverse-next', so I change this test to expect the breakpoint number
the program hits.

gdb/testsuite:

2016-04-07  Yao Qi  <yao.qi@linaro.org>

	* gdb.reverse/next-reverse-bkpt-over-sr.exp: Match the breakpoint
	number instead of the comments on some line.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Optimized-out pointer: New test for error handling
@ 2016-04-06 21:44 sergiodj+buildbot
  2016-04-06 22:29 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-04-06 21:44 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b16f8a3b1ecce592fe331a5b1ce6632951350e9c ***

Author: Don Breazeal <donb@codesourcery.com>
Branch: master
Commit: b16f8a3b1ecce592fe331a5b1ce6632951350e9c

Optimized-out pointer: New test for error handling

This patch implements a test that ensures that with "set print object
on", -var-create returns "<optimized out>" for an optimized out pointer
to structure, rather than throwing an error, while also ensuring that
any attempt to dereference the pointer *will* throw an error.

It uses the dwarf assembler to construct the appropriate debug info
to represent a pointer-to-struct in the program as optimized out,
and then accesses that pointer in various ways.  The test uses both
the console interpreter and the MI interpreter.

gdb/testsuite/ChangeLog:
2016-04-06  Don Breazeal  <donb@codesourcery.com>

	* gdb.dwarf2/dw2-opt-structptr.c: New test program.
	* gdb.dwarf2/dw2-opt-structptr.exp: New test script.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix memory leak in ld ARM backend
@ 2016-04-06  8:42 sergiodj+buildbot
  2016-04-06  9:17 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-04-06  8:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 15dd01b1209ec92b361dd2547708dd17ffc2a786 ***

Author: Thomas Preud'homme <thomas.preudhomme@arm.com>
Branch: master
Commit: 15dd01b1209ec92b361dd2547708dd17ffc2a786

Fix memory leak in ld ARM backend

2016-04-06  Thomas Preud'homme  <thomas.preudhomme@arm.com>

	bfd/
	* elf32-arm.c (elf32_arm_size_stubs): Move error_ret_free_local to be
	a fall through from error_ret_free_internal.  Free local_syms in
	error_ret_free_local if allocated from bfd_elf_get_elf_syms ().


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] arc/nps400: Add additional instructions
@ 2016-04-05 22:02 sergiodj+buildbot
  2016-04-06  0:10 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-04-05 22:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 820f03ffe027367f275e9debb5f3f3376820ab37 ***

Author: Andrew Burgess <andrew.burgess@embecosm.com>
Branch: master
Commit: 820f03ffe027367f275e9debb5f3f3376820ab37

arc/nps400: Add additional instructions

Adds the movbi, decode1, fbset, fbclear, encode0, encode1, rflt, crc16,
and crc32 instructions for the nps400 arc machine type.

gas/ChangeLog:

	* testsuite/gas/arc/nps400-1.d: Update expected results.
	* testsuite/gas/arc/nps400-1.s: Additional test cases.

opcodes/ChangeLog:

	* arc-nps400-tbl.h: Add movbi, decode1, fbset, fbclear, encode0,
	encode1, rflt, crc16, and crc32 instructions.
	* arc-opc.c (arc_flag_operands): Add F_NPS_R.
	(arc_flag_classes): Add C_NPS_R.
	(insert_nps_bitop_size_2b): New function.
	(extract_nps_bitop_size_2b): Likewise.
	(insert_nps_bitop_uimm8): Likewise.
	(extract_nps_bitop_uimm8): Likewise.
	(arc_operands): Add new operand entries.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Improve gdb_remote_download, remove gdb_download
@ 2016-04-05 18:35 sergiodj+buildbot
  2016-04-05 22:23 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-04-05 18:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7817ea46148df2931cf00d17aeedb844b6e4e4db ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: 7817ea46148df2931cf00d17aeedb844b6e4e4db

Improve gdb_remote_download, remove gdb_download

This patch removes gdb_download in favor of gdb_remote_download, since
they are very close in functionality.  Also, in preparation for the
following patch about shared library handling during tests, it improves
gdb_remote_download so that it uses standard_output_file for any
destination board that is local, not only host.

If the destination board is remote, gdb_remote_download will use the
standard remote_download from DejaGnu, resulting in the file being
transferred on the remote system.

If the destination is local, gdb_remote_download will copy the file to
the standard test directory (found using standard_output_file).  Tcl's
file copy seems to handle gracefully cases where the source file is the
same as the destination, so I don't think it's necessary to check for
that case ourselves, as a previous version of the patch did.

I'd prefer to keep the name gdb_download instead of gdb_remote_download,
since I don't like the fact that gdb_remote_download implies that the
destination is remote, when it's not always the case.  However,
gdb_remote_download is used at many more places than gdb_download, so
it's easier to reuse that.  Also, since it's a wrapper around DejaGnu's
remote_download, it might be better to keep that name.  I don't know.

I ran the testsuite native, with native-gdbserver and with a
remote gdbserver, and didn't see any related failure.

gdb/testsuite/ChangeLog:

	* gdb.base/jit-so.exp: Use gdb_remote_download instead of
	gdb_download.  Use it even if the target is not remote.
	* gdb.base/jit.exp (compile_jit_test): Likewise.
	* lib/gdb.exp (gdb_remote_download): Copy files to the standard
	output directory if the destination board is local, otherwise use
	the standard remote_download from DejaGnu.
	(gdb_download): Remove.
	(gdb_load_shlibs): Use gdb_remote_download instead of
	gdb_download.
	* lib/gdbserver-support.exp (gdbserver_download_current_prog):
	Use gdb_remote_download instead of gdb_download.  Use it even if
	the target is not remote.
	* lib/mi-support.exp (mi_load_shlibs): Use gdb_remote_download
	instead of gdb_download.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [ARC] 24 bit reloc and overflow detection fix.
@ 2016-04-05 16:09 sergiodj+buildbot
  2016-04-05 17:39 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-04-05 16:09 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 094fb06395d03ac343d1ce14a3621d1b4f78a0cc ***

Author: Claudiu Zissulescu <claziss@synopsys.com>
Branch: master
Commit: 094fb06395d03ac343d1ce14a3621d1b4f78a0cc

[ARC] 24 bit reloc and overflow detection fix.

bfd/
2016-04-05  Cupertino Miranda  <cmiranda@synopsys.com>

	* elf32-arc.c (name_for_global_symbol): Changed assert.
	(get_replace_function): Created.:
	(struct arc_relocation_data): Changed to signed types.
	(defines S, L, P, PDATA): Casted to signed type.
	(defines SECTSTART, _SDA_BASE_, TLS_REL): Likewise.
	(PRINT_DEBUG_RELOC_INFO_BEFORE): Changed.
	(arc_do_relocation): Changed.

include/
2016-04-05  Cupertino Miranda  <cmiranda@synopsys.com>

	* opcode/arc-func.h (replace_bits24): Changed.
	(replace_bits24_be): Created.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [ARC] Dynamic relocs verification for dynindx == -1.
@ 2016-04-05 15:04 sergiodj+buildbot
  2016-04-05 15:59 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-04-05 15:04 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 94e5c97160abbcf2274f8d58dc2900bc85c1c384 ***

Author: Claudiu Zissulescu <claziss@synopsys.com>
Branch: master
Commit: 94e5c97160abbcf2274f8d58dc2900bc85c1c384

[ARC] Dynamic relocs verification for dynindx == -1.

bfd/
2016-04-05  Cupertino Miranda  <cmiranda@synopsys.com>

	* elf32-arc.c (name_for_global_symbol): Added assert to check for
	symbol index.
	(elf_arc_relocate_section): Added and changed asserts, validating
	the synamic symbol index.
	(elf_arc_finish_dynamic_symbol): Do not fill the dynamic
	relocation if symbol has dynindx set to -1.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix gdb.mi/mi-breakpoint-changed.exp for remote targets
@ 2016-04-04 14:48 sergiodj+buildbot
  2016-04-04 15:25 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-04-04 14:48 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7beb7f68a0514c489f8305b79ce3938a6a4e54f9 ***

Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: 7beb7f68a0514c489f8305b79ce3938a6a4e54f9

Fix gdb.mi/mi-breakpoint-changed.exp for remote targets

The libraries are never downloaded to the target for the first test
(test_insert_delete_modify), so the executable can't run properly.

I also added some with_test_prefix to help differentiate between the
different test case phases.

gdb/testsuite/ChangeLog:

	* gdb.mi/mi-breakpoint-changed.exp: Add some with_test_prefix.
	(test_insert_delete_modify): Call mi_load_shlibs before trying to
	run.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] gdb: allow enumeration constants as second operand of BINOP_REPEAT
@ 2016-04-01 15:14 sergiodj+buildbot
  2016-04-01 16:08 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-04-01 15:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cc63428a4c290772d99863aead457c29ee223dc5 ***

Author: Artemiy Volkov <artemiyv@acm.org>
Branch: master
Commit: cc63428a4c290772d99863aead457c29ee223dc5

gdb: allow enumeration constants as second operand of BINOP_REPEAT

This patch adds support for TYPE_CODE_ENUM values to be supplied
as right-hand side operand of the BINOP_REPEAT (@) operator. The
following should now work:

enum {
  sz = 17
};

int
main ()
{
  int arr[sz + 1] = { 0 };
  return 0; /* line 9 here */
}

(gdb) b 9
(gdb) r
(gdb) p arr@sz
$1 = {0 <repeats 17 times>}
(gdb)

A couple of tests is also included in this patch to demonstrate that it is
working as intended.

gdb/Changelog:

2016-04-01  Artemiy Volkov  <artemiyv@acm.org>

	PR gdb/19820
	* eval.c (evaluate_subexp_standard): Allow TYPE_CODE_ENUM to be
        the type of BINOP_REPEAT's second operand.

gdb/testsuite/Changelog:

2016-04-01  Artemiy Volkov  <artemiyv@acm.org>

	PR gdb/19820
	* gdb.base/printcmds.exp: Add artificial arrays tests.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] gdbserver: Fix C++ build errors in tracepoint.c
@ 2016-03-31 22:48 sergiodj+buildbot
  2016-04-01  1:50 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-03-31 22:48 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 252db07e1d4c5733b91a53b9fe4881b873eae049 ***

Author: Marcin Kocielnicki <koriakin@0x04.net>
Branch: master
Commit: 252db07e1d4c5733b91a53b9fe4881b873eae049

gdbserver: Fix C++ build errors in tracepoint.c

These were introduced by 1cda1512689aabb36588a01370002632a0c8e560
and a13c46966d308297a1273e35ccc807a3912d573d .  One is a simple
missing cast, the other is const usage on global function pointers
exported from IPA: in C++, consts are static, and thus won't be
exported from the DSO (the build error was because of non-applicable
visibility("default")).

gdb/gdbserver/ChangeLog:

	* tracepoint.c (gdb_collect_ptr): Remove const qualifier.
	(get_raw_reg_ptr): Likewise.
	(get_trace_state_variable_value_ptr): Likewise.
	(set_trace_state_variable_value_ptr): Likewise.
	(initialize_tracepoint): Cast alloc_jump_pad_buffer result to
	char *.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Add regression test for PR gdb/19858 (JIT code registration on attach)
@ 2016-03-31 19:22 sergiodj+buildbot
  2016-03-31 22:05 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-03-31 19:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 64cdf930d9ed85e93ae55adbc20b0f9848ef863b ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 64cdf930d9ed85e93ae55adbc20b0f9848ef863b

Add regression test for PR gdb/19858 (JIT code registration on attach)

This test would fail without the previous gdb/jit.c fix:

  (gdb) attach 23031
  Attaching to program: .../build/gdb/testsuite/outputs/gdb.base/jit/jit-main, process 23031
  [...]
  207           WAIT_FOR_GDB; i = 0;  /* gdb break here 1 */
  (gdb) PASS: gdb.base/jit.exp: attach: one_jit_test-2: attach
  set var wait_for_gdb = 0
  (gdb) PASS: gdb.base/jit.exp: attach: one_jit_test-2: set var wait_for_gdb = 0
  info function ^jit_function
  All functions matching regular expression "^jit_function":
  (gdb) FAIL: gdb.base/jit.exp: attach: one_jit_test-2: info function ^jit_function

gdb/testsuite/ChangeLog:
2016-03-31  Pedro Alves  <palves@redhat.com>

	PR gdb/19858
	* gdb.base/jit-main.c: Include unistd.h.
	(ATTACH): Define to 0 if not already defined.
	(wait_for_gdb, mypid): New globals.
	(WAIT_FOR_GDB): New macro.
	(MAIN): Set an alarm.  Store the process's pid.  Wait for GDB at
	some breakpoint locations.
	* gdb.base/jit.exp (clean_reattach, continue_to_test_location):
	New procedures.
	(one_jit_test): Add REATTACH parameter, and handle it.  Use
	continue_to_test_location.
	(top level): Test attach, and adjusts calls to one_jit_test.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix PR gdb/19858: GDB doesn't register the JIT libraries on attach
@ 2016-03-31 19:01 sergiodj+buildbot
  2016-03-31 19:31 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-03-31 19:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9bb84c9f97cb81df81f18f4e47d6b24fa37b597c ***

Author: Yichao Yu <yyc1992@gmail.com>
Branch: master
Commit: 9bb84c9f97cb81df81f18f4e47d6b24fa37b597c

Fix PR gdb/19858: GDB doesn't register the JIT libraries on attach

Ref: https://sourceware.org/ml/gdb/2016-03/msg00023.html

GDB currently fails to fetch the list of already-registered JIT
modules on attach.

Nothing is calling jit_inferior_init, which is what is responsible for
walking the JIT object list at init time.

Despite the misleading naming, jit_inferior_created_hook ->
jit_inferior_init is only called when the inferior execs.

This regressed with the fix for PR gdb/13431 (03bef283c2d3):
 https://sourceware.org/ml/gdb-patches/2012-02/msg00023.html which
removed the inferior_created (jit_inferior_created_observer)
observer.

Adding an inferior_created observer back fixes the issue.

In turn, this exposes a bug in jit_breakpoint_re_set_internal as well,
which is returning the wrong result when we already have the
breakpoint at the right address.

gdb/ChangeLog:
2016-03-31  Yichao Yu  <yyc1992@gmail.com>

	PR gdb/19858
	* jit.c (jit_breakpoint_re_set_internal): Return 0 if we already
	got the breakpoint at the right address.
	(jit_inferior_created): New function.
	(_initialize_jit): Install jit_inferior_created as
	inferior_created observer.

Signed-off-by: Pedro Alves <palves@redhat.com>


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] IPA: Add alloc_jump_pad_buffer target hook.
@ 2016-03-31 14:33 sergiodj+buildbot
  2016-03-31 15:47 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-03-31 14:33 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a13c46966d308297a1273e35ccc807a3912d573d ***

Author: Marcin Kocielnicki <koriakin@0x04.net>
Branch: master
Commit: a13c46966d308297a1273e35ccc807a3912d573d

IPA: Add alloc_jump_pad_buffer target hook.

Targets may have various requirements on the required location of the jump
pad area.  Currently IPA allocates it at the lowest possible address,
so that it is reachable by branches from the executable.  However, this
fails on powerpc, which has executable link address (0x10000000) much
larger than branch reach (+/- 32MiB).

This makes jump pad buffer allocation a target hook instead.  The current
implementations are as follows:

- i386 and s390: Branches can reach anywhere, so just mmap it.  This
  avoids the linear search dance.
- x86_64: Branches have +/-2GiB of reach, and executable is loaded low,
  so just call mmap with MAP_32BIT.  Likewise avoids the linear search.
- aarch64: Branches have +-128MiB of reach, executable loaded at 4MiB.
  Do a linear search from 4MiB-size downwards to page_size.
- s390x: Branches have +-4GiB of reach, executable loaded at 2GiB.
  Do like on aarch64.

gdb/gdbserver/ChangeLog:

	* linux-aarch64-ipa.c: Add <sys/mman.h> and <sys/auxv.h> includes.
	(alloc_jump_pad_buffer): New function.
	* linux-amd64-ipa.c: Add <sys/mman.h> include.
	(alloc_jump_pad_buffer): New function.
	* linux-i386-ipa.c (alloc_jump_pad_buffer): New function.
	* linux-s390-ipa.c: Add <sys/mman.h> and <sys/auxv.h> includes.
	(alloc_jump_pad_buffer): New function.
	* tracepoint.c (getauxval) [!HAVE_GETAUXVAL]: New function.
	(initialize_tracepoint): Delegate to alloc_jump_pad_buffer.
	* tracepoint.h (alloc_jump_pad_buffer): New prototype.
	(getauxval) [!HAVE_GETAUXVAL]: New prototype.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] python: Use console format for output of gdb.execute command
@ 2016-03-31 12:58 sergiodj+buildbot
  2016-03-31 14:06 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-03-31 12:58 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e7ea3ec7c623be0b9be1eaf4929794652a84be11 ***

Author: Catalin Udma <catalin.udma@freescale.com>
Branch: master
Commit: e7ea3ec7c623be0b9be1eaf4929794652a84be11

python: Use console format for output of gdb.execute command

When gdb is started in MI mode, the output of gdb.execute
command is in MI-format in case when it is executed from python stop
handler while for all other cases the output is in console-format.

To assure consistent output format, this is fixed by using the console
format for all python gdb command executions.

PR python/19743

gdb/ChangeLog:
2016-03-31  Catalin Udma  <catalin.udma@freescale.com>

	PR python/19743
	* python/python.c (execute_gdb_command): Use console uiout
	when executing gdb command.
	* utils.c (restore_ui_out_closure): New structure.
	(do_restore_ui_out): New function.
	(make_cleanup_restore_ui_out): Likewise.
	* utils.h (make_cleanup_restore_ui_out): Declare.

gdb/testsuite/ChangeLog:
2016-03-31  Catalin Udma  <catalin.udma@freescale.com>

	PR python/19743
	* gdb.python/py-mi-events-gdb.py: New file.
	* gdb.python/py-mi-events.c: New file.
	* gdb.python/py-mi-events.exp: New file.

Signed-off-by: Catalin Udma <catalin.udma@freescale.com>


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Simplify gdb.reverse/until-reverse.c
@ 2016-03-30 16:17 sergiodj+buildbot
  2016-03-30 17:24 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-03-30 16:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e6359af3fdda6b9265565ecbd213763244ed8594 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: e6359af3fdda6b9265565ecbd213763244ed8594

Simplify gdb.reverse/until-reverse.c

Nowadays, functions fprintf, printf and malloc are executed in
gdb.reverse/until-reverse.c, so that it takes much time to record
instructions inside them.  This may cause timeout, and we had several
fixes to bump the timeout,

 https://sourceware.org/ml/gdb-patches/2012-02/msg00038.html
 https://sourceware.org/ml/gdb-patches/2015-08/msg00186.html

also I still see this on arm-linux,

 continue
 Continuing.
 Do you want to auto delete previous execution log entries when record/replay buffer becomes full (record full stop-at-limit)?([y] or n) n
 Process record: stopped by user.

 Program stopped.
 0xf77021e6 in __linkin_atfork (newp=0xf7751748 <atfork_mem>) at ../nptl/sysdeps/unix/sysv/linux/register-atfork.c:117
 117     ../nptl/sysdeps/unix/sysv/linux/register-atfork.c: No such file or directory.
 (gdb) FAIL: gdb.reverse/until-precsave.exp: run to end of main (got interactive prompt)

however, I can't figure out how these functions (fprintf, printf and
malloc) are related to the test itself.  marker1 is a function from
shared library too so we don't need these complicated libc functions
at all.  IMO, recording the instructions in these libc functions has
nothing to do with the test itself except slow down the test.  This
patch is to remove the usage of fprintf and printf, and also move
malloc to a dead code path.

gdb/testsuite:

2016-03-30  Yao Qi  <yao.qi@linaro.org>

	* gdb.reverse/until-precsave.exp: Match function name only.
	* gdb.reverse/until-reverse.c (main): Don't call fprintf nor printf.
	Move malloc to a condition block.
	* gdb.reverse/until-reverse.exp: Match function name only.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] gdbserver: Handle 'v' packet while processing qSymbol.
@ 2016-03-30  0:32 sergiodj+buildbot
  2016-03-30 11:01 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-03-30  0:32 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 28170b88cc8b40fdea2b065dafe6e1872a47ee4e ***

Author: Marcin Kocielnicki <koriakin@0x04.net>
Branch: master
Commit: 28170b88cc8b40fdea2b065dafe6e1872a47ee4e

gdbserver: Handle 'v' packet while processing qSymbol.

On powerpc64, qSymbol query may require gdb to read a function
descriptor, sending a vFile packet to gdbserver.  Thus, we need
to handle 'v' packet in look_up_one_symbol.

vFile replies may be quite long, and require reallocating own_buf.
Since handle_v_requests assumes the buffer is the static global own_buf
from server.c and reallocates it, we need to make own_buf global and
use it from look_up_one_symbol instead of using our own auto variable.
I've also done the same change in relocate_instruction, just in case.

On gdb side, in remote_check_symbols, rs->buf may be clobbered by vFile
handling, yet we need its contents for the reply (the symbol name is
stored there).  Allocate a new buffer instead.

This broke fast tracepoints on powerpc64, due to errors in reading IPA
symbols.

gdb/ChangeLog:

	* remote.c (remote_check_symbols): Allocate own buffer for reply.

gdbserver/ChangeLog:

	* remote-utils.c (look_up_one_symbol): Remove own_buf, handle 'v'
	packets.
	(relocate_instruction): Remove own_buf.
	* server.c (own_buf): Make global.
	(handle_v_requests): Make global.
	* server.h (own_buf): New declaration.
	(handle_v_requests): New prototype.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] gdb/NEWS: Add mention of s390*-linux tracepoints.
@ 2016-03-30  0:26 sergiodj+buildbot
  2016-03-30  9:01 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-03-30  0:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c37c0ba69b670f0994b53078abdb07737f816a5a ***

Author: Marcin Kocielnicki <koriakin@0x04.net>
Branch: master
Commit: c37c0ba69b670f0994b53078abdb07737f816a5a

gdb/NEWS: Add mention of s390*-linux tracepoints.

gdb/ChangeLog:

	* NEWS: Mention support for tracepoints on s390*-linux.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] gdbserver/s390: Add support for compiled agent expressions.
@ 2016-03-29 22:49 sergiodj+buildbot
  2016-03-30  1:35 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-03-29 22:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f39e8743546602977f860811f44aa327736b97dc ***

Author: Marcin Kocielnicki <koriakin@0x04.net>
Branch: master
Commit: f39e8743546602977f860811f44aa327736b97dc

gdbserver/s390: Add support for compiled agent expressions.

These sequences assume a z900+ CPU, like the rest of fast tracepoint
support.

gdb/gdbserver/ChangeLog:

	PR 18377
	* linux-s390-low.c (add_insns): New function.
	(s390_emit_prologue): New function.
	(s390_emit_epilogue): New function.
	(s390_emit_add): New function.
	(s390_emit_sub): New function.
	(s390_emit_mul): New function.
	(s390_emit_lsh): New function.
	(s390_emit_rsh_signed): New function.
	(s390_emit_rsh_unsigned): New function.
	(s390_emit_ext): New function.
	(s390_emit_log_not): New function.
	(s390_emit_bit_and): New function.
	(s390_emit_bit_or): New function.
	(s390_emit_bit_xor): New function.
	(s390_emit_bit_not): New function.
	(s390_emit_equal): New function.
	(s390_emit_less_signed): New function.
	(s390_emit_less_unsigned): New function.
	(s390_emit_ref): New function.
	(s390_emit_if_goto): New function.
	(s390_emit_goto): New function.
	(s390_write_goto_address): New function.
	(s390_emit_litpool): New function.
	(s390_emit_const): New function.
	(s390_emit_call): New function.
	(s390_emit_reg): New function.
	(s390_emit_pop): New function.
	(s390_emit_stack_flush): New function.
	(s390_emit_zero_ext): New function.
	(s390_emit_swap): New function.
	(s390_emit_stack_adjust): New function.
	(s390_emit_set_r2): New function.
	(s390_emit_int_call_1): New function.
	(s390_emit_void_call_2): New function.
	(s390_emit_eq_goto): New function.
	(s390_emit_ne_goto): New function.
	(s390_emit_lt_goto): New function.
	(s390_emit_le_goto): New function.
	(s390_emit_gt_goto): New function.
	(s390_emit_ge_goto): New function.
	(s390x_emit_prologue): New function.
	(s390x_emit_epilogue): New function.
	(s390x_emit_add): New function.
	(s390x_emit_sub): New function.
	(s390x_emit_mul): New function.
	(s390x_emit_lsh): New function.
	(s390x_emit_rsh_signed): New function.
	(s390x_emit_rsh_unsigned): New function.
	(s390x_emit_ext): New function.
	(s390x_emit_log_not): New function.
	(s390x_emit_bit_and): New function.
	(s390x_emit_bit_or): New function.
	(s390x_emit_bit_xor): New function.
	(s390x_emit_bit_not): New function.
	(s390x_emit_equal): New function.
	(s390x_emit_less_signed): New function.
	(s390x_emit_less_unsigned): New function.
	(s390x_emit_ref): New function.
	(s390x_emit_if_goto): New function.
	(s390x_emit_const): New function.
	(s390x_emit_call): New function.
	(s390x_emit_reg): New function.
	(s390x_emit_pop): New function.
	(s390x_emit_stack_flush): New function.
	(s390x_emit_zero_ext): New function.
	(s390x_emit_swap): New function.
	(s390x_emit_stack_adjust): New function.
	(s390x_emit_int_call_1): New function.
	(s390x_emit_void_call_2): New function.
	(s390x_emit_eq_goto): New function.
	(s390x_emit_ne_goto): New function.
	(s390x_emit_lt_goto): New function.
	(s390x_emit_le_goto): New function.
	(s390x_emit_gt_goto): New function.
	(s390x_emit_ge_goto): New function.
	(s390_emit_ops): New function.
	(struct linux_target_ops): Fill in emit_ops hook.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [ARC] Add support for Quarkse opcodes.
@ 2016-03-29 13:24 sergiodj+buildbot
  2016-03-29 14:19 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-03-29 13:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f2dd88387a40ec152fa3b8221f02c83d14f897e9 ***

Author: Claudiu Zissulescu <claziss@synopsys.com>
Branch: master
Commit: f2dd88387a40ec152fa3b8221f02c83d14f897e9

[ARC] Add support for Quarkse opcodes.

gas/
2016-03-29  Claudiu Zissulescu  <claziss@synopsys.com>

        * testsuite/gas/arc/ext2op.d: New file.
        * testsuite/gas/arc/ext2op.s: Likewise.
        * testsuite/gas/arc/ext3op.d: Likewise.
        * testsuite/gas/arc/ext3op.s: Likewise.

opcodes/
2016-03-29  Claudiu Zissulescu  <claziss@synopsys.com>

        * arc-tbl.h (invld07): Remove.
        * arc-ext-tbl.h: New file.
        * arc-dis.c (FIELDA, FIELDB, FIELDC): Remove.
        * arc-opc.c (arc_opcodes): Add ext-tbl include.

include/
2016-03-29  Claudiu Zissulescu  <claziss@synopsys.com>

        * opcode/arc.h (insn_subclass_t): Add QUARKSE subclass.
        (FIELDA, FIELDB, FIELDC, FIELDF, FIELDQ, INSN3OP, INSN2OP)
        (INSN2OP, INSN3OP_ABC, INSN3OP_ALC, INSN3OP_ABL, INSN3OP_ALL)
        (INSN3OP_0BC, INSN3OP_0LC, INSN3OP_0BL, INSN3OP_0LL, INSN3OP_ABU)
        (INSN3OP_ALU, INSN3OP_0BU, INSN3OP_0LU, INSN3OP_BBS, INSN3OP_0LS)
        (INSN3OP_CBBC, INSN3OP_CBBL, INSN3OP_C0LC, INSN3OP_C0LL)
        (INSN3OP_CBBU, INSN3OP_C0LU, MINSN3OP_ABC, MINSN3OP_ALC)
        (MINSN3OP_ABL, MINSN3OP_ALL, MINSN3OP_0BC, MINSN3OP_0LC)
        (MINSN3OP_0BL, MINSN3OP_0LL, MINSN3OP_ABU, MINSN3OP_ALU)
        (MINSN3OP_0BU, MINSN3OP_0LU, MINSN3OP_BBS, MINSN3OP_0LS)
        (MINSN3OP_CBBC, MINSN3OP_CBBL, MINSN3OP_C0LC, MINSN3OP_C0LL)
        (MINSN3OP_CBBU, MINSN3OP_C0LU, INSN2OP_BC, INSN2OP_BL, INSN2OP_0C)
        (INSN2OP_0L INSN2OP_BU, INSN2OP_0U, MINSN2OP_BC, MINSN2OP_BL)
        (MINSN2OP_0C, MINSN2OP_0L, MINSN2OP_BU, MINSN2OP_0U): Define.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] PE/COFF regression in base of code and data calculation
@ 2016-03-29  5:59 sergiodj+buildbot
  2016-03-29  9:37 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-03-29  5:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e2b4fc913bad3b6a6e4b00b11c7c75268892150d ***

Author: Toni Spets <toni.spets@iki.fi>
Branch: master
Commit: e2b4fc913bad3b6a6e4b00b11c7c75268892150d

PE/COFF regression in base of code and data calculation

	PR 19878
	* coffcode.h (coff_write_object_contents): Revert accidental
	2014-11-10 change.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] sparc: reorder wr instructions in sparc_opcodes to fix diagnostics
@ 2016-03-24 17:25 sergiodj+buildbot
  2016-03-24 21:56 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-03-24 17:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a6b71f422b2a4c1dae639064945bc8697528c57b ***

Author: Jose E. Marchesi <jose.marchesi@oracle.com>
Branch: master
Commit: a6b71f422b2a4c1dae639064945bc8697528c57b

sparc: reorder wr instructions in sparc_opcodes to fix diagnostics

This patch changes the location of several variants of the `wr'
instruction in sparc_opcodes.  This is to get the assembler to emit the
right diagnostics when an invalid %asrN register is used in an
instruction.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] make more variables const
@ 2016-03-22 23:14 sergiodj+buildbot
  2016-03-23  0:18 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-03-22 23:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b9bb4a935677558b76795d2053263a8981578f54 ***

Author: Trevor Saunders <tbsaunde+binutils@tbsaunde.org>
Branch: master
Commit: b9bb4a935677558b76795d2053263a8981578f54

make more variables const

gas/ChangeLog:

2016-03-22  Trevor Saunders  <tbsaunde+binutils@tbsaunde.org>

	* config/tc-h8300.c (h8300_elf_section): Add const qualifiers.
	* config/tc-ia64.c (obj_elf_vms_common): Likewise.
	* config/tc-m68hc11.c (md_begin): Likewise.
	(print_opcode_list): Likewise.
	* config/tc-msp430.c (msp430_section): Likewise.
	* config/tc-score.c (struct s3_insn_to_dependency): Likewise.
	(s3_build_dependency_insn_hsh): Likewise.
	* config/tc-score7.c (struct s7_insn_to_dependency): Likewise.
	(s7_build_dependency_insn_hsh): Likewise.
	* config/tc-tic4x.c: Likewise.
	* config/tc-tic54x.c (tic54x_set_default_include): Likewise.
	(subsym_get_arg): Likewise.
	* config/tc-xtensa.c (struct suffix_reloc_map): Likewise.
	(get_directive): Likewise.
	(cache_literal_section): Likewise.
	* config/xtensa-relax.c: Likewise.
	* symbols.c (symbol_create): Likewise.
	(local_symbol_make): Likewise.
	(symbol_relc_make_expr): Likewise.

include/ChangeLog:

2016-03-22  Trevor Saunders  <tbsaunde+binutils@tbsaunde.org>

	* opcode/i960.h: Add const qualifiers.
	* opcode/tic4x.h (struct tic4x_inst): Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Attribute with DW_FORM_flag_present
@ 2016-03-22 12:26 sergiodj+buildbot
  2016-03-22 13:25 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-03-22 12:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a97fbc7e3ca781b8d95ed8591c6ee65f2d8a798a ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: a97fbc7e3ca781b8d95ed8591c6ee65f2d8a798a

Attribute with DW_FORM_flag_present

	PR 19850
	* dwarf2.c (read_attribute_value): Skip info_ptr check for
	DW_FORM_flag_present.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix possible unbounded stack use in peXXigen.c
@ 2016-03-22 10:41 sergiodj+buildbot
  2016-03-22 11:35 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-03-22 10:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7769fa97a0fe54a9455a9d96970373dbbf714458 ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: 7769fa97a0fe54a9455a9d96970373dbbf714458

Fix possible unbounded stack use in peXXigen.c

	* peXXigen.c (_bfd_XXi_write_codeview_record): Fix possible
	unbounded stack use.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix the disassembly of the AArch64's OOR instruction as a MOV instruction.
@ 2016-03-18 18:39 sergiodj+buildbot
  2016-03-20  5:36 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-03-18 18:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8678914fcb40e4c620a33e6b38a14df928fa780a ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: 8678914fcb40e4c620a33e6b38a14df928fa780a

Fix the disassembly of the AArch64's OOR instruction as a MOV instruction.

	PR target/19721
opcodes	* aarch64-tbl.h (aarch64_opcode_table): Fix type of second operand
	of MOV insn that aliases an ORR insn.

gas	* testsuite/gas/aarch64/pr19721.s: New test source file.
	* testsuite/gas/aarch64/pr19721.d: New test driver file.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Check lwp_signal_can_be_delivered for enqueue/dequeue pending signals
@ 2016-03-18 15:17 sergiodj+buildbot
  2016-03-19 14:41 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-03-18 15:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 35ac8b3e2dbbe1fcd107dfcc6bbc4faed6bdc63f ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 35ac8b3e2dbbe1fcd107dfcc6bbc4faed6bdc63f

Check lwp_signal_can_be_delivered for enqueue/dequeue pending signals

The enqueue and dequeue signals in linux_resume_one_lwp_throw use one
condition and its inverted one.  This patch is to move the condition
into a function lwp_signal_can_be_delivered, so that the next patch can
change the condition in one place.

gdb/gdbserver:

2016-03-18  Yao Qi  <yao.qi@linaro.org>

	* linux-low.c (lwp_signal_can_be_delivered): New function.
	(linux_resume_one_lwp_throw): Use lwp_signal_can_be_delivered.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Remove redundant WIFSTOPPED check
@ 2016-03-18 14:39 sergiodj+buildbot
  2016-03-19  0:58 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-03-18 14:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 80aea927cc7bf97a2bc22e1fb2111c52be295e8b ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 80aea927cc7bf97a2bc22e1fb2111c52be295e8b

Remove redundant WIFSTOPPED check

WIFSTOPPED is checked linux_wstatus_maybe_breakpoint, so WIFSTOPPED
in "WIFSTOPPED (wstat) && linux_wstatus_maybe_breakpoint (wstat)"
is redundant.  This patch removes WIFSTOPPED check.

gdb/gdbserver:

2016-03-18  Yao Qi  <yao.qi@linaro.org>

	* linux-low.c (linux_low_filter_event): Remove redundant
	WIFSTOPPED check together with linux_wstatus_maybe_breakpoint.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] linux-record: Simplify with record_mem_at_reg()
@ 2016-03-17  9:47 sergiodj+buildbot
  2016-03-18  4:54 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-03-17  9:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5fd0888aff1abfa6e06cfa48164e72c48072ac79 ***

Author: Andreas Arnez <arnez@linux.vnet.ibm.com>
Branch: master
Commit: 5fd0888aff1abfa6e06cfa48164e72c48072ac79

linux-record: Simplify with record_mem_at_reg()

The function record_linux_system_call() often records a memory area
whose address is contained in a register.  So far this required two
function calls: one for fetching the register value, and another one for
recording the memory area.  These two function calls are now merged into
a new local helper function, and all occurrences are adjusted.  This
reduces the source code and makes it more readable.

gdb/ChangeLog:

	* linux-record.c (record_mem_at_reg): New helper function.
	(record_linux_system_call): Exploit new helper function where
	applicable.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Process record: Fix arm-linux syscall arguments
@ 2016-03-16 19:42 sergiodj+buildbot
  2016-03-16 22:29 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-03-16 19:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6b94a855beef3a301509dfac6bf5446d1953524b ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 6b94a855beef3a301509dfac6bf5446d1953524b

Process record: Fix arm-linux syscall arguments

Arguments are passed in r0-r6 on arm linux syscall (both EABI and OABI).
This patch is to set arm_linux_record_tdep.arg{1-7} to the right
register number.

This patch fixes the following test failures...

-FAIL: gdb.reverse/getresuid-reverse.exp: check ruid record
-FAIL: gdb.reverse/getresuid-reverse.exp: check rgid record
-FAIL: gdb.reverse/pipe-reverse.exp: check pipe record
-FAIL: gdb.reverse/readv-reverse.exp: check readv record
-FAIL: gdb.reverse/readv-reverse.exp: check readv record
-FAIL: gdb.reverse/readv-reverse.exp: check readv record
-FAIL: gdb.reverse/readv-reverse.exp: check readv record
-FAIL: gdb.reverse/waitpid-reverse.exp: check waitpid record

gdb:

2016-03-16  Yao Qi  <yao.qi@linaro.org>

	* arm-linux-tdep.c (arm_linux_init_abi): Fix
	arm_linux_record_tdep.arg1, arm_linux_record_tdep.arg2 and
	arm_linux_record_tdep.arg3.  Set arm_linux_record_tdep.arg4,
	arm_linux_record_tdep.arg5, arm_linux_record_tdep.arg6, and
	arm_linux_record_tdep.arg7.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] xml-tdesc.c (tdesc_start_enum): Fix c++ build.
@ 2016-03-16 17:48 sergiodj+buildbot
  2016-03-17 23:01 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-03-16 17:48 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bfeeb14b8468ab3f60d719f2cde697d1b537eba8 ***

Author: Doug Evans <dje@google.com>
Branch: master
Commit: bfeeb14b8468ab3f60d719f2cde697d1b537eba8

xml-tdesc.c (tdesc_start_enum): Fix c++ build.

gdb/ChangeLog:

	* xml-tdesc.c (tdesc_start_enum): Fix c++ build.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [ARM] Support ARMv8.2 FP16 simd instructions
@ 2016-03-16 16:29 sergiodj+buildbot
  2016-03-17  9:39 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-03-16 16:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cc9333013723880949a1e07a3e04bdbc1a3c3032 ***

Author: Jiong Wang <jiong.wang@arm.com>
Branch: master
Commit: cc9333013723880949a1e07a3e04bdbc1a3c3032

[ARM] Support ARMv8.2 FP16 simd instructions

gas/
	* config/tc-arm.c (N_S_32): New.
	(N_F_16_32): Likewise.
	(N_SUF_32): Support N_F16.
	(N_IF_32): Likewise.
	(neon_dyadic_misc): Likewise.
	(do_neon_cmp): Likewise.
	(do_neon_cmp_inv): Likewise.
	(do_neon_mul): Likewise.
	(do_neon_fcmp_absolute): Likewise.
	(do_neon_step): Likewise.
	(do_neon_abs_neg): Likewise.
	(CVT_FLAVOR_VAR): Likewise.
	(do_neon_cvt_1): Likewise.
	(do_neon_recip_est): Likewise.
	(do_vmaxnm): Likewise.
	(do_vrint_1): Likewise.
	(neon_check_type): Check architecture support for FP16 extension.
	(insns): Update comments.
	* testsuite/gas/arm/armv8-2-fp16-simd.s: New test source.
	* testsuite/gas/arm/armv8-2-fp16-simd.d: New testcase for arm mode.
	* testsuite/gas/arm/armv8-2-fp16-simd-thumb.d: Likewise for thumb mode.
	* testsuite/gas/arm/armv8-2-fp16-simd-warning.d: New rejection test for
	arm mode.
	* testsuite/gas/arm/armv8-2-fp16-simd-warning-thumb.d: Likewise for
	thumb mode.
	* testsuite/gas/arm/armv8-2-fp16-simd-warning.l: New expected rejection
	error file.

opcode/
	* arm-dis.c (neon_opcodes): Support new FP16 instructions.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix PR gdb/19676: Internal error in linux-thread.db.c if /proc not mounted
@ 2016-03-15 17:14 sergiodj+buildbot
  2016-03-15 19:26 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-03-15 17:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1eb2dbb8d73c344e199fd04531ec3f649e2835b2 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 1eb2dbb8d73c344e199fd04531ec3f649e2835b2

Fix PR gdb/19676: Internal error in linux-thread.db.c if /proc not mounted

If /proc is not mounted, GDB fails an assertion in find_new_threads_once:

 Continuing.
 .../src/gdb/linux-thread-db.c:1249: internal-error: find_new_threads_once: Assertion `!target_has_execution' failed.
 A problem internal to GDB has been detected,
 further debugging may prove unreliable.
 Quit this debugging session? (y or n)

That was supposed to catch misuses of td_ta_thr_iter, which is unsafe
for live debugging.  However, if /proc is not mounted, we still
fallback to using it.

I didn't bother with a warning, because GDB already prints several
others related to failing to open /proc files.

gdb/ChangeLog:
2016-03-15  Pedro Alves  <palves@redhat.com>

	PR gdb/19676
	* linux-thread-db.c (try_thread_db_load_1): Leave
	info->td_ta_thr_iter_p NULL iff debugging a live process and we
	have /proc access.
	(find_new_threads_once): Assert that we have a non-NULL
	info->td_ta_thr_iter_p instead of checking whether the target has
	execution.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] gdb/s390: Fill gen_return_address hook.
@ 2016-03-13 10:06 sergiodj+buildbot
  2016-03-13 11:11 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-03-13 10:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 70104a908773d7df0af48ca5c48856886bafea13 ***

Author: Marcin Kocielnicki <koriakin@0x04.net>
Branch: master
Commit: 70104a908773d7df0af48ca5c48856886bafea13

gdb/s390: Fill gen_return_address hook.

gdb/ChangeLog:

	* s390-linux-tdep.c (s390_gen_return_address): New function.
	(s390_gdbarch_init): Fill gen_return_address hook.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix some places where octet to byte conversions are needed.
@ 2016-03-11  9:28 sergiodj+buildbot
  2016-03-11 10:12 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-03-11  9:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 37b01f6a13f21f274bf9758ecbf5d9efd6153444 ***

Author: Dan Gissel <dgisselq@ieee.org>
Branch: master
Commit: 37b01f6a13f21f274bf9758ecbf5d9efd6153444

Fix some places where octet to byte conversions are needed.

	PR 19713
	* elf.c (_bfd_elf_section_offset): Ensure that the returned offset
	uses bytes not octets.
	* elflink.c (resolve_section): Likewise.
	Add a bfd parameter.
	(eval_section): Pass the input_bfd to resolve_section.
	(bfd_elf_perform_complex_relocation): Convert byte offset to
	octets before read and writing values.
	(elf_link_input_bfd): Add byte to octet conversions.
	(elf_reloc_link_order): Likewise.
	(elf_fixup_link_order): Likewise.
	(bfd_elf_final_link): Likewise.
	* reloc.c (_bfd_final_link_relocate): Likewise.
	* syms.c (_bfd_stab_section_find_nearest_line): Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Add $_as_string convenience function
@ 2016-03-10 22:34 sergiodj+buildbot
  2016-03-11  6:40 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-03-10 22:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f2f3ccb9f81255fd1b4f877600f39979c2d7ece5 ***

Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: f2f3ccb9f81255fd1b4f877600f39979c2d7ece5

Add $_as_string convenience function

This patch is a follow-up to "Add printf format specifier for printing
enumerator":

  https://sourceware.org/ml/gdb-patches/2016-02/msg00144.html

Instead of having a solution specific to the printf command, Pedro
suggested adding a general purpose function $_as_string() that would
cover this use case and more.

So, in order to print the textual label of an enum, one can use:

  (gdb) printf "Visiting node of type %s\n", $_as_string(node)
  Visiting node of type NODE_INTEGER

gdb/ChangeLog:

	* data-directory/Makefile.in (PYTHON_FILE_LIST): Install
	gdb/function/as_string.py.
	* python/lib/gdb/function/as_string.py: New file.
	* NEWS: Mention the new $_as_string function.

gdb/testsuite/ChangeLog:

	* gdb.python/py-as-string.exp: New file.
	* gdb.python/py-as-string.c: New file.

gdb/doc/ChangeLog:

	* gdb.texinfo (Convenience Functions): Document $_as_string.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] gdb.trace/change-loc.exp: Don't depend on tracepoint ordering.
@ 2016-03-09 22:03 sergiodj+buildbot
  2016-03-10  6:00 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-03-09 22:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ba84e0da35d29dd8969a4bcdd84e3eaa48927a84 ***

Author: Marcin Kocielnicki <koriakin@0x04.net>
Branch: master
Commit: ba84e0da35d29dd8969a4bcdd84e3eaa48927a84

gdb.trace/change-loc.exp: Don't depend on tracepoint ordering.

powerpc (32-bit) loads shared libraries below the main executable, so
the PENDING location is the first one, which the current regex doesn't
match.  Split it into two tests instead, one looking for the pending
tracepoint location, and the other for two installed locations.

gdb/testsuite/ChangeLog:

	* gdb.trace/change-loc.exp: Don't depend on tracepoint location
	ordering.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] More "Program" -> "Thread NN received signal" testsuite adjustment
@ 2016-03-09 21:55 sergiodj+buildbot
  2016-03-11  3:59 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-03-09 21:55 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 00dbd492e462565366a2691e0579b510ce4c3733 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 00dbd492e462565366a2691e0579b510ce4c3733

More "Program" -> "Thread NN received signal" testsuite adjustment

These tests should have been adjusted by f303dbd60d9c (Fix PR
threads/19422 - show which thread caused stop), but clearly I had
missed grepping for potential-fail cases.

gdb/testsuite/ChangeLog
2016-03-09  Pedro Alves  <palves@redhat.com>

	* gdb.threads/attach-into-signal.exp: Adjust to "Program received
	signal" -> "Thread NN received signal" output change.
	* gdb.threads/ia64-sigill.exp: Likewise.
	* gdb.threads/linux-dp.exp: Likewise.
	* gdb.threads/manythreads.exp: Likewise.
	* gdb.threads/pending-step.exp: Likewise.
	* gdb.threads/print-threads.exp: Likewise.
	* gdb.threads/sigstep-threads.exp: Likewise.
	* gdb.threads/staticthreads.exp: Likewise.
	* gdb.threads/tls.exp: Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Simplify saved_command_line handling
@ 2016-03-09 21:09 sergiodj+buildbot
  2016-03-10 23:54 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-03-09 21:09 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2669cade3dcebf5d572bcd535cf21934cbc1633c ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 2669cade3dcebf5d572bcd535cf21934cbc1633c

Simplify saved_command_line handling

There doesn't seem to be much point in trying to reuse this buffer.
Prefer simplicity instead.

(In case you're wondering whether this fixes an off-by-one: linelength
is misnamed; it's really a size including terminating null char.)

gdb/ChangeLog:
2016-03-09  Pedro Alves  <palves@redhat.com>

	* event-top.c (command_line_handler): Use xfree + xstrdup instead
	of xrealloc + strcpy.
	* main.c (captured_main): Use xstrdup instead of xmalloc plus
	manual clear.
	* top.c (saved_command_line): Rewrite comment.
	(saved_command_line_size): Delete.
	(command_line_input): Use xfree + xstrdup instead of xrealloc +
	strcpy.
	* top.h (saved_command_line_size): Delete declaration.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Use struct buffer in gdb_readline_no_editing
@ 2016-03-09 20:47 sergiodj+buildbot
  2016-03-10 21:18 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-03-09 20:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7a3bde34bc61af108556c74b661533dadddcb178 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 7a3bde34bc61af108556c74b661533dadddcb178

Use struct buffer in gdb_readline_no_editing

gdb/ChangeLog:
2016-03-09  Pedro Alves  <palves@redhat.com>

	* common/buffer.h (buffer_grow_char): New function.
	* top.c: Include buffer.h.
	(gdb_readline_no_editing): Rename 'prompt_arg' parameter to
	'prompt'.  Use struct buffer instead of xrealloc.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] gdb_readline -> gdb_readline_no_editing
@ 2016-03-09 20:36 sergiodj+buildbot
  2016-03-10 19:42 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-03-09 20:36 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c5c136ea94f21e5ff968d5b402494611464c7b31 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: c5c136ea94f21e5ff968d5b402494611464c7b31

gdb_readline -> gdb_readline_no_editing

Name this such that it's clearer that this is not a wrapper for the
real readline, but instead a replacement that provides no command line
editing features.

gdb/ChangeLog:
2016-03-09  Pedro Alves  <palves@redhat.com>

	* defs.h (gdb_readline): Delete declaration.
	* top.c (gdb_readline): Rename to ...
	(gdb_readline_no_editing): ... this, and make static.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Update prompt_for_continue comments
@ 2016-03-09 20:27 sergiodj+buildbot
  2016-03-10 18:09 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-03-09 20:27 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 720d2e96b424bb4bb1f7021f86763ff3df078e2b ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 720d2e96b424bb4bb1f7021f86763ff3df078e2b

Update prompt_for_continue comments

These comments are out of date -- we no longer call gdb_readline.  And
I think that mentioning the event loop is more useful here than
whatever GO32 issue had with gdb_readline, which may even no longer be
an issue.

gdb/ChangeLog:
2016-03-09  Pedro Alves  <palves@redhat.com>

	* utils.c (prompt_for_continue): Update comments.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Eliminate async_annotation_suffix
@ 2016-03-09 20:15 sergiodj+buildbot
  2016-03-10 16:20 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-03-09 20:15 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 608ff013aae02e3ac4687691db57bbcb8984fe18 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 608ff013aae02e3ac4687691db57bbcb8984fe18

Eliminate async_annotation_suffix

The comments and existence of this global are a bit of misleading
obfuscation, since this is only ever used to print the prompt
annotation, and never changes.  Just hardcode "prompt" where
necessary, as done for most other annotations.

gdb/ChangeLog:
2016-03-09  Pedro Alves  <palves@redhat.com>

	* event-top.c (async_annotation_suffix): Delete.
	(top_level_prompt, command_line_handler): Don't use
	'async_annotation_suffix' and simplify.
	* event-top.h (async_annotation_suffix): Delete declaration.
	(init_main): Remove reference to 'async_annotation_suffix'.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] gdb_readline2 -> gdb_readline_no_editing_callback
@ 2016-03-09 20:06 sergiodj+buildbot
  2016-03-10 14:41 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-03-09 20:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c70061cf94691182484924c79cbbdd2203ef92d5 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: c70061cf94691182484924c79cbbdd2203ef92d5

gdb_readline2 -> gdb_readline_no_editing_callback

The "2" in "gdb_readline2" doesn't really convey much.  Rename for
clarity.

gdb/ChangeLog:
2016-03-09  Pedro Alves  <palves@redhat.com>

	* event-top.c (gdb_readline2): Rename to ...
	(gdb_readline_no_editing_callback): ... this.
	(change_line_handler, stdin_event_handler)
	(gdb_setup_readline): Adjust.
	* event-top.h (gdb_readline2): Rename to ...
	(gdb_readline_no_editing_callback): ... this, and move closer to
	other readline-related declarations.
	* mi/mi-interp.c (mi_interpreter_resume): Adjust.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Garbage collect window_hook
@ 2016-03-09 19:54 sergiodj+buildbot
  2016-03-10 12:43 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-03-09 19:54 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8a243832540cb3bd246192db1f0a4dfa44d92dcf ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 8a243832540cb3bd246192db1f0a4dfa44d92dcf

Garbage collect window_hook

I checked, and Insight doesn't set this.

gdb/ChangeLog:
2016-03-09  Pedro Alves  <palves@redhat.com>

	* top.c (window_hook): Delete.
	(command_loop): Remove references to window_hook.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] gdb.trace/entry-values.exp: Fixes for powerpc64.
@ 2016-03-09 19:21 sergiodj+buildbot
  2016-03-10  8:20 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-03-09 19:21 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 98fa59e9b06fa479cafb852ef87e5a9bfd87ae54 ***

Author: Marcin Kocielnicki <koriakin@0x04.net>
Branch: master
Commit: 98fa59e9b06fa479cafb852ef87e5a9bfd87ae54

gdb.trace/entry-values.exp: Fixes for powerpc64.

On powerpc64, "disassemble foo" doesn't work properly on object files
(it can't process the relocations in .opd section) - instead, let's
link it into an executable and load that.

Also, backtrace displays .main, not main.  Accept both.

gdb/testsuite/ChangeLog:

	* gdb.trace/entry-values.exp: Link ${binfile}1.o to ${binfile}1 and
	use it for disassembly; accept .main in addition to main in backtrace.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Avoid spaces in osabi names
@ 2016-03-09 16:19 sergiodj+buildbot
  2016-03-09 20:53 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-03-09 16:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f7990f1690e9ef0471634c871c790f6cf706866d ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: f7990f1690e9ef0471634c871c790f6cf706866d

Avoid spaces in osabi names

It's not possible today to select some of the osabis by name.
Specifically, those that have spaces in their names and then the first
word is ambiguous...

For example:
 (gdb) set osabi <TAB>
 [...]
 FreeBSD ELF
 FreeBSD a.out
 [...]
 (gdb) set osabi FreeBSD ELF
 Ambiguous item "FreeBSD ELF".

In reality, because "set osabi" is an enum command, that was
equivalent to trying "set osabi FreeBSD", which is then obviously
ambiguous, because of "FreeBSD ELF" and "FreeBSD a.out".

Also, even if the first word is not ambiguous, we actually ignore
whatever comes after the first word:

 (gdb) set osabi GNU/Linux
 (gdb) show osabi
 The current OS ABI is "GNU/Linux".
 The default OS ABI is "GNU/Linux".
 (gdb) set osabi Windows SomeNonsense
                         ^^^^^^^^^^^^
 (gdb) show osabi
 The current OS ABI is "Windows CE".
 The default OS ABI is "GNU/Linux".
 (gdb)

Fix this by avoiding spaces in osabi names.

We could instead make "set osabi" have a custom set hook, or
alternatively make the enum set hook (in cli-setshow.c) handle values
with spaces, but OTOH, I have a feeling that could cause trouble.
E.g., in cases where we might want to write more than one enum value
in the same line.  We could support quoting as workaround, but, not
sure we want that.  "No spaces" seems like a simpler rule.

gdb/ChangeLog:
2016-03-09  Pedro Alves  <palves@redhat.com>

	* osabi.c (gdb_osabi_names): Avoid spaces in osabi names.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix v850 bfd arch info printable names
@ 2016-03-09 15:59 sergiodj+buildbot
  2016-03-09 18:20 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-03-09 15:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4b05e0a74b3fb21b56e821423b8a334e4be9cfe7 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 4b05e0a74b3fb21b56e821423b8a334e4be9cfe7

Fix v850 bfd arch info printable names

Currently, it's not possible to manually set some of the v850 archs in
gdb:

 (gdb) set architecture v850<TAB>
 v850 (using old gcc ABI)
 v850-rh850
 v850e
 v850e (using old gcc ABI)
 v850e1
 [...]
 (gdb) set architecture v850 (using old gcc ABI)
 Ambiguous item "v850 (using old gcc ABI)".

The problem is that "set architecture" is a GDB "enum command", and
GDB only considers an enum value to be the string up until the first
space.  So writing "v850 (using old gcc ABI)" is the same as writing
"v850", and then that's not an unambiguous arch printable name prefix.

v850 is actually the only arch that has spaces in its printable name.
One can conveniently see that with e.g.:

 (gdb) set max-completions unlimited
 (gdb) complete set architecture
 ...

Rather than hack GDB into accepting this somehow, make v850 arch
printable names more like the printable names of the other archs, and
put the abi variant in the "machine" part, after a ':'.

We now get:

 (gdb) set architecture v850<TAB>
 v850:old-gcc-abi
 v850:rh850
 v850e
 v850e1
 v850e1:old-gcc-abi
 v850e2
 v850e2:old-gcc-abi
 [...]

And now "set architecture v850:old-gcc-abi" works as expected.

I ran the binutils/gas/ld testsuites, and found no regressions.  I
don't have a cross compiler handy, but I ran the gdb tests anyway,
which covers at least some snoke testing.

I think that the OUTPUT_ARCH in ld/scripttempl/v850.sc may have got
broken with the previous 2012 change, since I hacked v850_rh850.sc to
output "v850" and ld failed to grok it.  I think it only works if the
old GCC ABI is the configured v850 default ABI.  That's now fixed by
changing to use explicit v850:old-gcc-abi.

Also, this actually "fixes" an existing GDB test, which isn't likewise
expecting spaces in arch names, when GDB is configured for
--target=v850:

  (gdb) FAIL: gdb.xml/tdesc-arch.exp: read valid architectures

bfd/ChangeLog:
2016-03-09  Pedro Alves  <palves@redhat.com>

	* cpu-v850.c (N): Append ":old-gcc-abi" instead of " (using old
	gcc ABI)" to printable name.
	* cpu-v850_rh850.c (bfd_v850_rh850_arch): Use "v850:rh850" instead
	of "v850-rh850" as printable name.

ld/ChangeLog:
2016-03-09  Pedro Alves  <palves@redhat.com>

	* scripttempl/v850.sc: Use "v850:old-gcc-abi" as OUTPUT_ARCH.
	* scripttempl/v850_rh850.sc: Use "v850:rh850" as OUTPUT_ARCH.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] For COFF and COFF/PE targets, skip relocations against absolute symbols.
@ 2016-03-09 15:43 sergiodj+buildbot
  2016-03-09 16:37 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-03-09 15:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 26c62da040fb9d602da269a3bdffdea13a4367c7 ***

Author: Leon Winter <winter-gcc@bfw-online.de>
Branch: master
Commit: 26c62da040fb9d602da269a3bdffdea13a4367c7

For COFF and COFF/PE targets, skip relocations against absolute symbols.

	PR ld/19623
	* cofflink.c (_bfd_coff_generic_relocate_section): Do not apply
	relocations against absolute symbols.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Handle local IFUNC symbols in shared object
@ 2016-03-08 17:47 sergiodj+buildbot
  2016-03-08 18:39 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-03-08 17:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d1ed1c7d69e6656de213b12594e702afec31a66d ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: d1ed1c7d69e6656de213b12594e702afec31a66d

Handle local IFUNC symbols in shared object

Increment PLT reference count for locally defined local IFUNC symbols
in shared object since STT_GNU_IFUNC symbol must go through PLT even
if it is locally defined and undefined symbol may turn out to be a
STT_GNU_IFUNC symbol later.

bfd/

	PR ld/19784
	* elf32-i386.c (elf_i386_check_relocs): Increment PLT reference
	count for locally defined local IFUNC symbols in shared object.
	* elf64-x86-64.c (elf_x86_64_check_relocs): Likewise.

ld/

	PR ld/19784
	* testsuite/ld-i386/i386.exp: Remove pr19636-2e-nacl test.
	* testsuite/ld-i386/pr19636-2e-nacl.d: Moved to ...
	* testsuite/ld-i386/pr19636-2e.d: Here.  Remove notarget.
	* testsuite/ld-ifunc/ifunc.exp: Run PR ld/19784 tests.
	* testsuite/ld-ifunc/pass.out: New file.
	* testsuite/ld-ifunc/pr19784a.c: Likewise.
	* testsuite/ld-ifunc/pr19784b.c: Likewise.
	* testsuite/ld-ifunc/pr19784c.c: Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix "set architecture mips:10000" crash
@ 2016-03-07 16:52 sergiodj+buildbot
  2016-03-07 19:52 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-03-07 16:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e6c2f47b45315ba13f25fb57e51389d0c5ed0701 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: e6c2f47b45315ba13f25fb57e51389d0c5ed0701

Fix "set architecture mips:10000" crash

Fix this GDB crash:

  $ gdb -ex "set architecture mips:10000"
  Segmentation fault (core dumped)

Backtrace:

  Program received signal SIGSEGV, Segmentation fault.
  0x0000000000495b1b in mips_gdbarch_init (info=..., arches=0x0) at /home/pedro/gdb/mygit/cxx-convertion/src/gdb/mips-tdep.c:8436
  8436              if (bfd_get_flavour (info.abfd) == bfd_target_elf_flavour
  (top-gdb) bt
  #0  0x0000000000495b1b in mips_gdbarch_init (info=..., arches=0x0) at .../src/gdb/mips-tdep.c:8436
  #1  0x00000000007348a6 in gdbarch_find_by_info (info=...) at .../src/gdb/gdbarch.c:5155
  #2  0x000000000073563c in gdbarch_update_p (info=...) at .../src/gdb/arch-utils.c:522
  #3  0x0000000000735585 in set_architecture (ignore_args=0x0, from_tty=1, c=0x26bc870) at .../src/gdb/arch-utils.c:496
  #4  0x00000000005f29fd in do_sfunc (c=0x26bc870, args=0x0, from_tty=1) at .../src/gdb/cli/cli-decode.c:121
  #5  0x00000000005fd3f3 in do_set_command (arg=0x7fffffffdcdd "mips:10000", from_tty=1, c=0x26bc870) at .../src/gdb/cli/cli-setshow.c:455
  #6  0x0000000000836157 in execute_command (p=0x7fffffffdcdd "mips:10000", from_tty=1) at .../src/gdb/top.c:460
  #7  0x000000000071abfb in catch_command_errors (command=0x835f6b <execute_command>, arg=0x7fffffffdccc "set architecture mips:10000", from_tty=1)
      at .../src/gdb/main.c:368
  #8  0x000000000071bf4f in captured_main (data=0x7fffffffd750) at .../src/gdb/main.c:1132
  #9  0x0000000000716737 in catch_errors (func=0x71af44 <captured_main>, func_args=0x7fffffffd750, errstring=0x106b9a1 "", mask=RETURN_MASK_ALL)
      at .../src/gdb/exceptions.c:240
  #10 0x000000000071bfe6 in gdb_main (args=0x7fffffffd750) at .../src/gdb/main.c:1164
  #11 0x000000000040a6ad in main (argc=4, argv=0x7fffffffd858) at .../src/gdb/gdb.c:32
  (top-gdb)

We already check whether info.abfd is NULL before all other
bfd_get_flavour calls in the same function.  Just this one case was
missing.

(This was exposed by a WIP test that tries all "set architecture ARCH"
values.)

gdb/ChangeLog:
2016-03-07  Pedro Alves  <palves@redhat.com>

	* mips-tdep.c (mips_gdbarch_init): Check whether info.abfd is NULL
	before calling bfd_get_flavour.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Improve analysis of racy testcases
@ 2016-03-06  1:57 sergiodj+buildbot
  2016-03-06  3:38 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-03-06  1:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fb6a751f5f1fe7912e84dd90d06395c357da47c2 ***

Author: Sergio Durigan Junior <sergiodj@redhat.com>
Branch: master
Commit: fb6a751f5f1fe7912e84dd90d06395c357da47c2

Improve analysis of racy testcases

This is an initial attempt to introduce some mechanisms to identify
racy testcases present in our testsuite.  As can be seen in previous
discussions, racy tests are really bothersome and cause our BuildBot
to pollute the gdb-testers mailing list with hundreds of
false-positives messages every month.  Hopefully, identifying these
racy tests in advance (and automatically) will contribute to the
reduction of noise traffic to gdb-testers, maybe to the point where we
will be able to send the failure messages directly to the authors of
the commits.

I spent some time trying to decide the best way to tackle this
problem, and decided that there is no silver bullet.  Racy tests are
tricky and it is difficult to catch them, so the best solution I could
find (for now?) is to run our testsuite a number of times in a row,
and then compare the results (i.e., the gdb.sum files generated during
each run).  The more times you run the tests, the more racy tests you
are likely to detect (at the expense of waiting longer and longer).
You can also run the tests in parallel, which makes things faster (and
contribute to catching more racy tests, because your machine will have
less resources for each test and some of them are likely to fail when
this happens).  I did some tests in my machine (8-core i7, 16GB RAM),
and running the whole GDB testsuite 5 times using -j6 took 23 minutes.
Not bad.

In order to run the racy test machinery, you need to specify the
RACY_ITER environment variable.  You will assign a number to this
variable, which represents the number of times you want to run the
tests.  So, for example, if you want to run the whole testsuite 3
times in parallel (using 2 cores), you will do:

  make check RACY_ITER=3 -j2

It is also possible to use the TESTS variable and specify which tests
you want to run:

  make check TEST='gdb.base/default.exp' RACY_ITER=3 -j2

And so on.  The output files will be put at the directory
gdb/testsuite/racy_outputs/.

After make invokes the necessary rules to run the tests, it finally
runs a Python script that will analyze the resulting gdb.sum files.
This Python script will read each file, and construct a series of sets
based on the results of the tests (one set for FAIL's, one for
PASS'es, one for KFAIL's, etc.).  It will then do some set operations
and come up with a list of unique, sorted testcases that are racy.
The algorithm behind this is:

  for state in PASS, FAIL, XFAIL, XPASS...; do
    if a test's state in every sumfile is $state; then
      it is not racy
    else
      it is racy

(The algorithm is actually a bit more complex than that, because it
takes into account other things in order to decide whether the test
should be ignored or not).

IOW, a test must have the same state in every sumfile.

After processing everything, the script prints the racy tests it could
identify on stdout.  I am redirecting this to a file named racy.sum.

Something else that I wasn't sure how to deal with was non-unique
messages in our testsuite.  I decided to do the same thing I do in our
BuildBot: include a unique identifier in the end of message, like:

  gdb.base/xyz.exp: non-unique message
  gdb.base/xyz.exp: non-unique message <<2>>

This means that you will have to be careful about them when you use
the racy.sum file.

I ran the script several times here, and it did a good job catching
some well-known racy tests.  Overall, I am satisfied with this
approach and I think it will be helpful to have it upstream'ed.  I
also intend to extend our BuildBot and create new, specialized
builders that will be responsible for detecting the racy tests every X
number of days.

2016-03-05  Sergio Durigan Junior  <sergiodj@redhat.com>

	* Makefile.in (DEFAULT_RACY_ITER): New variable.
	(CHECK_TARGET_TMP): Likewise.
	(check-single-racy): New rule.
	(check-parallel-racy): Likewise.
	(TEST_TARGETS): Adjust rule to account for RACY_ITER.
	(do-check-parallel-racy): New rule.
	(check-racy/%.exp): Likewise.
	* README (Racy testcases): New section.
	* analyze-racy-logs.py: New file.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] ARM process record: VMOV
@ 2016-03-04 17:01 sergiodj+buildbot
  2016-03-04 19:48 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-03-04 17:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f1771dcebf80c75a13ca456491ddfb9b43fcaddf ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: f1771dcebf80c75a13ca456491ddfb9b43fcaddf

ARM process record: VMOV

ARM process record gets the wrong register number for VMOV (from core
register to single-precision register).  That is, we should record
the D register rather than the S pseudo register.  The patch also
removes the condition "bit (arm_insn_r->arm_insn, 20)" check, which
has been checked above.

It fixes the following internal error,

(gdb) PASS: gdb.reverse/finish-precsave.exp: BP at end of main
continue^M
Continuing.^M
../../binutils-gdb/gdb/regcache.c:649: internal-error: regcache_raw_read: Assertion `regnum >= 0 && regnum < regcache->descr->nr_raw_registers' failed.^M
A problem internal to GDB has been detected,FAIL: gdb.reverse/finish-precsave.exp: run to end of main (GDB internal error)

gdb:

2016-03-04  Yao Qi  <yao.qi@linaro.org>

	* arm-tdep.c (arm_record_vdata_transfer_insn): Simplify the
	condition check.  Record the right D register number.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Add missing ChangeLog entries for commit 82838
@ 2016-03-04 16:41 sergiodj+buildbot
  2016-03-04 21:11 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-03-04 16:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3f1f41f55f2fa5d390e57074477b6407302c8c46 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 3f1f41f55f2fa5d390e57074477b6407302c8c46

Add missing ChangeLog entries for commit 82838

Fix gold/testsuite/plugin_layout_with_alignment.sh permission.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] feature_to_c.sh: Print help when passing no arguments
@ 2016-03-04 15:16 sergiodj+buildbot
  2016-03-04 16:46 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-03-04 15:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 73519cce7cbe31609a2aa9c27955555237a0c51f ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: 73519cce7cbe31609a2aa9c27955555237a0c51f

feature_to_c.sh: Print help when passing no arguments

I found that odd that passing no arguments to feature_to_c.sh produces
this:

$ ./feature_to_c.sh
./feature_to_c.sh: 23: shift: can't shift that many

but passing one argument shows the help:

$ ./feature_to_c.sh hello
Usage: ./feature_to_c.sh OUTPUTFILE INPUTFILE...

This patch changes the script to show the help in both cases.

gdb/ChangeLog:

	* features/feature_to_c.sh: Print the help when passing no
	argument.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Treat common symbol in executable as definition
@ 2016-03-04 14:50 sergiodj+buildbot
  2016-03-04 15:33 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-03-04 14:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 07492f668d2173da7a2bda3707ff0985e0f460b6 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 07492f668d2173da7a2bda3707ff0985e0f460b6

Treat common symbol in executable as definition

Common symbol in executable is a definition, which overrides definition
from shared objects.  When linker sees a new definition from a shared
object, the new dynamic definition should be overridden by the previous
common symbol in executable.

bfd/

	PR ld/19579
	* elflink.c (_bfd_elf_merge_symbol): Treat common symbol in
	executable as definition if the new definition comes from a
	shared library.

ld/

	PR ld/19579
	* testsuite/ld-elf/pr19579a.c: New file.
	* testsuite/ld-elf/pr19579b.c: Likewise.
	* testsuite/ld-elf/shared.exp: Run PR ld/19579 test.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] get_symbols() plugin API tweak to support --start-lib/--end-lib.
@ 2016-03-03 21:03 sergiodj+buildbot
  2016-03-04  0:47 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-03-03 21:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 95ecdfbfcbf508919652a0254ee2b8c6572a949e ***

Author: Evgenii Stepanov <eugenis@google.com>
Branch: master
Commit: 95ecdfbfcbf508919652a0254ee2b8c6572a949e

get_symbols() plugin API tweak to support --start-lib/--end-lib.

Let the plugin know that a file is not being included in the link by
returning LDPS_NO_SYMS from get_symbols().

include/
	* plugin-api.h (enum ld_plugin_tag): Add LDPT_GET_SYMBOLS_V3.

gold/
	* plugin.h (Pluginobj::get_symbol_resolution_info): Add version
	parameter.
	* plugin.cc (get_symbols_v3): New function.
	(Plugin::load): Add LDPT_GET_SYMBOLS_V3.
	(Pluginobj::get_symbol_resolution_info): Return LDPS_NO_SYMS when using
	new version.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix bugs in the simulation of the AArch64's ADDP, FADDP, LD1, CCMP and CCMP instructions.
@ 2016-03-03 15:34 sergiodj+buildbot
  2016-03-03 21:58 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-03-03 15:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 57aa17424380be1c3e362a5601071f1f3a6f74f6 ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: 57aa17424380be1c3e362a5601071f1f3a6f74f6

Fix bugs in the simulation of the AArch64's ADDP, FADDP, LD1, CCMP and CCMP instructions.

	* simulator.c (set_flags_for_sub32): Correct type of signbit.
	(CondCompare): Swap interpretation of bit 30.
	(DO_ADDP): Delete macro.
	(do_vec_ADDP): Copy source registers before starting to update
	destination register.
	(do_vec_FADDP): Likewise.
	(do_vec_load_store): Fix computation of sizeof_operation.
	(rbit64): Fix type of constant.
	(aarch64_step): When displaying insn value, display all 32 bits.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Update comments to start_step_over
@ 2016-03-03 10:36 sergiodj+buildbot
  2016-03-03 20:07 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-03-03 10:36 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c40c8d4b6793b71eed7cf9fa7467edda2271dc86 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: c40c8d4b6793b71eed7cf9fa7467edda2271dc86

Update comments to start_step_over

I happen to see that comments to start_step_over isn't in sync with
code, so this patch is to update the comments.

gdb/gdbserver:

2016-03-03  Yao Qi  <yao.qi@linaro.org>

	* linux-low.c: Update comments to start_step_over.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Step over fork/vfork syscall insn in gdbserver
@ 2016-03-03 10:00 sergiodj+buildbot
  2016-03-03 14:44 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-03-03 10:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 92fa70b0bd8690d979357ebcdb501a9e4aa42ea6 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 92fa70b0bd8690d979357ebcdb501a9e4aa42ea6

Step over fork/vfork syscall insn in gdbserver

We can also extend disp-step-syscall.exp to test GDBserver step over
breakpoint on syscall instruction.  That is, we set a breakpoint
with a false condition on syscall instruction, so that GDBserver will
step over it.

This test triggers a GDBserver internal error, which can be fixed by
this series.

(gdb) PASS: gdb.base/disp-step-syscall.exp: fork: break cond on target: break on syscall insns
continue^M
Continuing.^M
Remote connection closed^M
(gdb) FAIL: gdb.base/disp-step-syscall.exp: fork: break cond on target: continue to fork again

In GDBserver, there is an internal error,

/home/yao/SourceCode/gnu/gdb/git/gdb/gdbserver/linux-low.c:1922: A problem internal to GDBserver has been detected.
unsuspend LWP 25554, suspended=-1

the simplified reproducer is like,

$ ./gdb ./testsuite/outputs/gdb.base/disp-step-syscall/disp-step-fork
(gdb) b main
(gdb) c
(gdb) disassemble fork // in order to find the address of insn 'syscall'
....
   0x00007ffff7ad6023 <+179>:	syscall
(gdb) b *0x00007ffff7ad6023 if main == 0
(gdb) c

gdb/testsuite:

2016-03-03  Yao Qi  <yao.qi@linaro.org>

	* gdb.base/disp-step-syscall.exp (break_cond_on_syscall): New.
	If target supports condition evaluation on target, invoke
	break_cond_on_syscall for fork and vfork.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] testsuite: Fix timeout issues during print of vla-arrays.
@ 2016-03-02 17:06 sergiodj+buildbot
  2016-03-02 23:46 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-03-02 17:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 07e448ade17bc8fb52469a5b2184017f94669bd6 ***

Author: bernhard.heckel <bernhard.heckel@intel.com>
Branch: master
Commit: 07e448ade17bc8fb52469a5b2184017f94669bd6

testsuite: Fix timeout issues during print of vla-arrays.

Printing and resolving of dynamic array's causes sporadic timeout issues on loaded systems.

2016-03-02  Bernhard Heckel  <bernhard.heckel@intel.com>

gdb/testsuite/Changelog:

     * gdb.fortran/vla-history.exp: Lookup array elements and printing exceeds timeout.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix gdb.trace/ftrace-lock.c compilation
@ 2016-03-01 18:47 sergiodj+buildbot
  2016-03-01 23:21 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-03-01 18:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 86e501afd46d7f0d31738bd62457593401d79bad ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 86e501afd46d7f0d31738bd62457593401d79bad

Fix gdb.trace/ftrace-lock.c compilation

Fixes, on F23:

 .../src/gdb/testsuite/gdb.trace/ftrace-lock.c: In function 'gdb_agent_gdb_collect':
 .../src/gdb/testsuite/gdb.trace/ftrace-lock.c:50:3: warning: implicit declaration of function 'sleep' [-Wimplicit-function-declaration]
    sleep (1);
    ^

gdb/testsuite/ChangeLog:
2016-03-01  Pedro Alves  <palves@redhat.com>

	* gdb.trace/ftrace-lock.c: Include <unistd.h>.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix gdb.threads/watchpoint-fork*.c compilation
@ 2016-03-01 17:53 sergiodj+buildbot
  2016-03-01 21:31 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-03-01 17:53 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1e903e320352db86233e1dd2d10fd140f5d4a887 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 1e903e320352db86233e1dd2d10fd140f5d4a887

Fix gdb.threads/watchpoint-fork*.c compilation

This testcase currently fails to compile on Fedora 23:

 .../src/gdb/testsuite/gdb.threads/watchpoint-fork-mt.c: In function 'start':
 .../src/gdb/testsuite/gdb.threads/watchpoint-fork-mt.c:70:11: warning: implicit declaration of function 'pthread_yield' [-Wimplicit-function-declaration]
	i = pthread_yield ();
	    ^
 .../src/gdb/testsuite/gdb.threads/watchpoint-fork-child.c: In function 'forkoff':
 .../src/gdb/testsuite/gdb.threads/watchpoint-fork-child.c:114:8: warning: implicit declaration of function 'pthread_yield' [-Wimplicit-function-declaratio
 n]
     i = pthread_yield ();
	 ^
 /tmp/ccUkNIsI.o: In function `start':
 .../src/gdb/testsuite/gdb.threads/watchpoint-fork-mt.c:70: undefined reference to `pthread_yield'
 (...)
 collect2: error: ld returned 1 exit status

 UNSUPPORTED: gdb.threads/watchpoint-fork.exp: child: multithreaded: Couldn't compile watchpoint-fork-child.c: unrecognized error
 UNTESTED: gdb.threads/watchpoint-fork.exp: child: multithreaded: watchpoint-fork.exp
 testcase .../src/gdb/testsuite/gdb.threads/watchpoint-fork.exp completed i

The glibc manual says, on _GNU_SOURCE:

 "You should define these macros by using #define preprocessor
 directives at the top of your source code files. These directives must
 come before any #include of a system header file."

I instead put it in the header all the .c files of the testcase must
include anyway.

gdb/testsuite/ChangeLog:
2016-03-01  Pedro Alves  <palves@redhat.com>

	* gdb.threads/watchpoint-fork-child.c: Include "watchpoint-fork.h"
	before anything else.
	* gdb.threads/watchpoint-fork-mt.c: Likewise.  Don't define
	_GNU_SOURCE here.
	* gdb.threads/watchpoint-fork-st.c: Include "watchpoint-fork.h"
	before anything else.
	* gdb.threads/watchpoint-fork.h: Define _GNU_SOURCE.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Optimize x86 GOT32X/GOTPCRELX relocations
@ 2016-02-26 17:52 sergiodj+buildbot
  2016-02-27  7:39 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-02-26 17:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bae420ef26f4331415b0503141c5931318025906 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: bae420ef26f4331415b0503141c5931318025906

Optimize x86 GOT32X/GOTPCRELX relocations

R_386_GOT32X, R_X86_64_GOTPCRELX and R_X86_64_REX_GOTPCRELX relocations
retrieve the symbol address via its GOT slot.  If the symbol address is
known at the link-time, we can use it directly by changing instruction
encoding.  Indirect branch can only be converted to PC relative direct
branch.  MOV can be changed to LEA or encoded differently with signed
address.  The subset of binary operations can be encoded only with
signed address.

If undefined weak symbol is resolved to zero link-time, we can use it
as address.  Zero addresss can't used with PC relative direct branch
when PIC is true since the current PC is unknown.  In 64-bit, 32-bit
relocation for PC relatiave direct branch to zero may also overflow.

If this optimization causes relocation overflow, --no-relax can be used
to work around it.

bfd/

	PR ld/19609
	* elf32-i386.c (elf_i386_convert_load): Convert to R_386_32 for
	load with locally bound symbols if PIC is false or there is no
	base register.  Optimize branch to 0 if PIC is false.
	(elf_i386_relocate_section): Don't generate dynamic relocations
	against undefined weak symbols if PIC is false.
	* elf64-x86-64.c (elf_x86_64_convert_load): Disable optimization
	if we can't estimate relocation overflow with --no-relax.
	Convert to R_X86_64_32S/R_X86_64_32 for load with locally bound
	symbols if PIC is false.  Optimize branch to 0 if PIC is false.
	(elf_x86_64_relocate_section): Don't generate dynamic relocations
	against undefined weak symbols if PIC is false.

ld/

	PR ld/19609
	* testsuite/ld-i386/got1.dd: Updated.
	* testsuite/ld-i386/lea1c.d: Likewise.
	* testsuite/ld-i386/load1-nacl.d: Likewise.
	* testsuite/ld-i386/load1.d: Likewise.
	* testsuite/ld-i386/load4b.d: Likewise.
	* testsuite/ld-i386/load5b.d: Likewise.
	* testsuite/ld-i386/mov1b.d: Likewise.
	* testsuite/ld-x86-64/mov1b.d: Likewise.
	* testsuite/ld-x86-64/mov1d.d: Likewise.
	* testsuite/ld-ifunc/ifunc-21-i386.d: Likewise.
	* testsuite/ld-ifunc/ifunc-21-x86-64.d: Likewise.
	* testsuite/ld-ifunc/ifunc-22-i386.d: Likewise.
	* testsuite/ld-ifunc/ifunc-22-x86-64.d: Likewise.
	* testsuite/ld-x86-64/gotpcrel1.dd: Likewise.
	* testsuite/ld-x86-64/lea1a.d: Likewise.
	* testsuite/ld-x86-64/lea1b.d: Likewise.
	* testsuite/ld-x86-64/lea1c.d: Likewise.
	* testsuite/ld-x86-64/lea1d.d: Likewise.
	* testsuite/ld-x86-64/lea1e.d: Likewise.
	* testsuite/ld-x86-64/lea1f.d: Likewise.
	* testsuite/ld-x86-64/mov1b.d: Likewise.
	* testsuite/ld-x86-64/mov1d.d: Likewise.
	* testsuite/ld-x86-64/pr13082-3b.d: Likewise.
	* testsuite/ld-x86-64/pr13082-4b.d: Likewise.
	* testsuite/ld-x86-64/lea1.s: Add tests for 32-bit registers.
	* testsuite/ld-i386/pr19609-1.s: New file.
	* testsuite/ld-i386/pr19609-1a.d: Likewise.
	* testsuite/ld-i386/pr19609-1b.d: Likewise.
	* testsuite/ld-i386/pr19609-1c.d: Likewise.
	* testsuite/ld-i386/pr19609-1d.d: Likewise.
	* testsuite/ld-i386/pr19609-1e.d: Likewise.
	* testsuite/ld-i386/pr19609-1f.d: Likewise.
	* testsuite/ld-i386/pr19609-1g.d: Likewise.
	* testsuite/ld-i386/pr19609-1h.d: Likewise.
	* testsuite/ld-i386/pr19609-1i.d: Likewise.
	* testsuite/ld-i386/pr19609-2.s: Likewise.
	* testsuite/ld-i386/pr19609-2a.d: Likewise.
	* testsuite/ld-i386/pr19609-2b.d: Likewise.
	* testsuite/ld-i386/pr19609-2c.d: Likewise.
	* testsuite/ld-i386/undefweak.s: Likewise.
	* testsuite/ld-i386/undefweaka.d: Likewise.
	* testsuite/ld-i386/undefweakb.d: Likewise.
	* testsuite/ld-x86-64/pr13082-3c.d: Likewise.
	* testsuite/ld-x86-64/pr13082-3d.d: Likewise.
	* testsuite/ld-x86-64/pr19609-1.s: Likewise.
	* testsuite/ld-x86-64/pr19609-1a.d: Likewise.
	* testsuite/ld-x86-64/pr19609-1b.d: Likewise.
	* testsuite/ld-x86-64/pr19609-1c.d: Likewise.
	* testsuite/ld-x86-64/pr19609-1d.d: Likewise.
	* testsuite/ld-x86-64/pr19609-1e.d: Likewise.
	* testsuite/ld-x86-64/pr19609-1f.d: Likewise.
	* testsuite/ld-x86-64/pr19609-1g.d: Likewise.
	* testsuite/ld-x86-64/pr19609-1h.d: Likewise.
	* testsuite/ld-x86-64/pr19609-1i.d: Likewise.
	* testsuite/ld-x86-64/pr19609-1j.d: Likewise.
	* testsuite/ld-x86-64/pr19609-1k.d: Likewise.
	* testsuite/ld-x86-64/pr19609-1l.d: Likewise.
	* testsuite/ld-x86-64/pr19609-1m.d: Likewise.
	* testsuite/ld-x86-64/pr19609-2.s: Likewise.
	* testsuite/ld-x86-64/pr19609-2a.d: Likewise.
	* testsuite/ld-x86-64/pr19609-2b.d: Likewise.
	* testsuite/ld-x86-64/pr19609-2c.d: Likewise.
	* testsuite/ld-x86-64/pr19609-2d.d: Likewise.
	* testsuite/ld-x86-64/pr19609-3.s: Likewise.
	* testsuite/ld-x86-64/pr19609-3a.d: Likewise.
	* testsuite/ld-x86-64/pr19609-3b.d: Likewise.
	* testsuite/ld-x86-64/pr19609-4.s: Likewise.
	* testsuite/ld-x86-64/pr19609-4a.d: Likewise.
	* testsuite/ld-x86-64/pr19609-4b.d: Likewise.
	* testsuite/ld-x86-64/pr19609-4c.d: Likewise.
	* testsuite/ld-x86-64/pr19609-4d.d: Likewise.
	* testsuite/ld-x86-64/pr19609-4e.d: Likewise.
	* testsuite/ld-x86-64/pr19609-5.s: Likewise.
	* testsuite/ld-x86-64/pr19609-5a.d: Likewise.
	* testsuite/ld-x86-64/pr19609-5b.d: Likewise.
	* testsuite/ld-x86-64/pr19609-5c.d: Likewise.
	* testsuite/ld-x86-64/pr19609-5d.d: Likewise.
	* testsuite/ld-x86-64/pr19609-5e.d: Likewise.
	* testsuite/ld-x86-64/pr19609-6.s: Likewise.
	* testsuite/ld-x86-64/pr19609-6a.d: Likewise.
	* testsuite/ld-x86-64/pr19609-6b.d: Likewise.
	* testsuite/ld-x86-64/pr19609-6c.d: Likewise.
	* testsuite/ld-x86-64/pr19609-6d.d: Likewise.
	* testsuite/ld-x86-64/pr19609-7.s: Likewise.
	* testsuite/ld-x86-64/pr19609-7a.d: Likewise.
	* testsuite/ld-x86-64/pr19609-7b.d: Likewise.
	* testsuite/ld-x86-64/pr19609-7c.d: Likewise.
	* testsuite/ld-x86-64/pr19609-7d.d: Likewise.
	* testsuite/ld-i386/i386.exp: Run undefweak tests and tests for
	PR ld/19609.
	* testsuite/ld-x86-64/x86-64.exp: Run pr13082-3c, pr13082-3d
	and tests for PR ld/19609.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
[parent not found: <ab50308758bfde9ab7b50e6def65e20f0b560702@gdb-build>]
* [binutils-gdb] Update symbol version for symbol from linker script
@ 2016-02-24 23:37 sergiodj+buildbot
  2016-02-25  7:41 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-02-24 23:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0f550b3df1d4ae31d12505cf93981313c9c6dd25 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 0f550b3df1d4ae31d12505cf93981313c9c6dd25

Update symbol version for symbol from linker script

We need to update symbol version for symbols from linker script.

bfd/

	PR ld/19698
	* elflink.c (bfd_elf_record_link_assignment): Set versioned if
	symbol version is unknown.

ld/

	PR ld/19698
	* testsuite/ld-elf/pr19698.d: New file.
	* testsuite/ld-elf/pr19698.s: Likewise.
	* testsuite/ld-elf/pr19698.t: Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Move tfile-avx.exp to tracefile-pseudo-reg.exp
@ 2016-02-24 19:30 sergiodj+buildbot
  2016-02-24 19:39 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-02-24 19:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 861ca91fc65b9a53b807f6d5c5253fc33f92e7d8 ***

Author: Antoine Tremblay <antoine.tremblay@ericsson.com>
Branch: master
Commit: 861ca91fc65b9a53b807f6d5c5253fc33f92e7d8

Move tfile-avx.exp to tracefile-pseudo-reg.exp

As it is planned to add more architectures to this test, rename to a more
generic name.

gdb/testsuite/ChangeLog:

	* gdb.trace/tfile-avx.c: Move to...
	* gdb.trace/tracefile-pseudo-reg.c: Here.
	* gdb.trace/tfile-avx.exp: Move to...
	* gdb.trace/tracefile-pseudo-reg.exp: Here.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Move new skip features to proper section (post 7.11).
@ 2016-02-24 18:24 sergiodj+buildbot
  2016-02-24 18:33 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-02-24 18:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d2dffb8d3be366d4d02de06e92c24c9abdb0adfc ***

Author: Doug Evans <dje@google.com>
Branch: master
Commit: d2dffb8d3be366d4d02de06e92c24c9abdb0adfc

Move new skip features to proper section (post 7.11).


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] powerpc: Support z-point type in gdbserver.
@ 2016-02-24 17:45 sergiodj+buildbot
  2016-02-24 17:54 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-02-24 17:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 657f9cde9d531c9929bef9e02a8064101d568f50 ***

Author: Wei-cheng Wang <cole945@gmail.com>
Branch: master
Commit: 657f9cde9d531c9929bef9e02a8064101d568f50

powerpc: Support z-point type in gdbserver.

Support z-point, so tracepoints and breakpoints can be inserted at the same
location.

gdb/gdbserver/ChangeLog:

2016-02-24  Wei-cheng Wang  <cole945@gmail.com>

	* linux-ppc-low.c (ppc_supports_z_point_type): New function:
	(ppc_insert_point, ppc_remove_point): Insert/remove z-packet breakpoints.
	(ppc64_emit_ops_vector): Add target ops - ppc_supports_z_point_type,
	ppc_insert_point, ppc_remove_point.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Revert "ABS32"
@ 2016-02-24 15:09 sergiodj+buildbot
  2016-02-24 16:12 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-02-24 15:09 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 92d77487b3dbfd934c5565bab09e0f3051e0b08d ***

Author: Renlin Li <renlin.li@arm.com>
Branch: master
Commit: 92d77487b3dbfd934c5565bab09e0f3051e0b08d

Revert "ABS32"

This reverts commit 30bdf5c82e5734ac9f0b18eb7af631806d419270.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [OPCODES][ARM][1/3]Add armv8.2 fp16 instruction dissembler support.
@ 2016-02-24 14:22 sergiodj+buildbot
  2016-02-24 16:01 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-02-24 14:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b0c11777665276f8e9b590bbe4832a7c66f5093d ***

Author: Renlin Li <renlin.li@arm.com>
Branch: master
Commit: b0c11777665276f8e9b590bbe4832a7c66f5093d

[OPCODES][ARM][1/3]Add armv8.2 fp16 instruction dissembler support.

opcodes/

2016-02-24  Renlin Li  <renlin.li@arm.com>

	* arm-dis.c (coprocessor_opcodes): Add fp16 instruction entries.
	(print_insn_coprocessor): Support fp16 instruction.

gas/

2016-02-24  Renlin Li  <renlin.li@arm.com>

	* testsuite/gas/arm/copro.d: Adjust output.
	* testsuite/gas/arm/copro.s: Adjust co-processor num.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [OPCODES][ARM]Fix mask for a few coprocessor opcodes.
@ 2016-02-24 14:12 sergiodj+buildbot
  2016-02-24 15:42 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-02-24 14:12 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3e309328e8d91e37f2f3cea15f8a686d3bdfa700 ***

Author: Renlin Li <renlin.li@arm.com>
Branch: master
Commit: 3e309328e8d91e37f2f3cea15f8a686d3bdfa700

[OPCODES][ARM]Fix mask for a few coprocessor opcodes.

opcodes/

2016-02-24  Renlin Li  <renlin.li@arm.com>

	* arm-dis.c (coprocessor_opcodes): Fix mask for vsel, vmaxnm, vminnm,
	vrint(mpna).

gas/

2016-02-24  Renlin Li  <renlin.li@arm.com>

	* testsuite/gas/arm/mask_1.d: New.
	* testsuite/gas/arm/mask_1.s: New.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [OPCODE][ARM]Correct disassembler for cdp/cdp2, mcr/mcr2, mrc/mrc2, ldc/ldc2, stc/stc2
@ 2016-02-24 14:09 sergiodj+buildbot
  2016-02-24 15:22 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-02-24 14:09 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8afc7bea4018bf535902503c9a25dd4a96dfa3ca ***

Author: Renlin Li <renlin.li@arm.com>
Branch: master
Commit: 8afc7bea4018bf535902503c9a25dd4a96dfa3ca

[OPCODE][ARM]Correct disassembler for cdp/cdp2, mcr/mcr2, mrc/mrc2, ldc/ldc2, stc/stc2

opcodes/

2016-02-24  Renlin Li  <renlin.li@arm.com>

	* arm-dis.c (print_insn_coprocessor): Check co-processor number for
	cpd/cpd2, mcr/mcr2, mrc/mrc2, ldc/ldc2, stc/stc2.

gas/

2016-02-24  Renlin Li  <renlin.li@arm.com>

	* testsuite/gas/arm/copro.s: Use coprocessor other than 10, 11.
	* testsuite/gas/arm/copro.d: Update.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] ABS32
@ 2016-02-24 14:07 sergiodj+buildbot
  2016-02-24 14:54 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-02-24 14:07 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 30bdf5c82e5734ac9f0b18eb7af631806d419270 ***

Author: Renlin Li <renlin.li@arm.com>
Branch: master
Commit: 30bdf5c82e5734ac9f0b18eb7af631806d419270

ABS32


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Set plt_got.offset to (bfd_vma) -1
@ 2016-02-24 13:54 sergiodj+buildbot
  2016-02-24 14:20 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-02-24 13:54 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 13f422778ff5307dad1f66d25a1d211bb8f76a8b ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 13f422778ff5307dad1f66d25a1d211bb8f76a8b

Set plt_got.offset to (bfd_vma) -1

Since plt_got.offset may be updated in x86 allocate_dynrelocs, set
plt_got.offset to (bfd_vma) -1 when setting needs_plt to 0.

	* elf32-i386.c (elf_i386_allocate_dynrelocs): Set plt_got.offset
	to (bfd_vma) -1 when setting needs_plt to 0.
	* elf64-x86-64.c (elf_x86_64_allocate_dynrelocs): Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix logic in exec_file_locate_attach
@ 2016-02-24 12:00 sergiodj+buildbot
  2016-02-24 12:40 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-02-24 12:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bf74e428bca61022bd5cdf6bf28789a184748b4d ***

Author: Gary Benson <gbenson@redhat.com>
Branch: master
Commit: bf74e428bca61022bd5cdf6bf28789a184748b4d

Fix logic in exec_file_locate_attach

This commit fixes an error in exec_file_locate_attach where
the main executable could be loaded from outside the sysroot
if a nonempty, non-"target:" sysroot was set but the discovered
executable filename did not exist in that sysroot and did exist
on the main filesystem.

gdb/ChangeLog:

	* exec.c (exec_file_locate_attach): Do not attempt to
	locate main executable locally if not found in sysroot.

gdb/testsuite/ChangeLog:

	* gdb.base/attach-pie-noexec.exp: Do not expect an error
	message on attach.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Build unavailable-stack frames for tracepoint.
@ 2016-02-24  3:22 sergiodj+buildbot
  2016-02-24  3:38 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-02-24  3:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 50ae56ec464580492a5f987f658acc6ad82131b6 ***

Author: Wei-cheng Wang <cole945@gmail.com>
Branch: master
Commit: 50ae56ec464580492a5f987f658acc6ad82131b6

Build unavailable-stack frames for tracepoint.

gdb/ChangeLog:

2016-02-24  Wei-cheng Wang  <cole945@gmail.com>

	* rs6000-tdep.c (rs6000_frame_cache, rs6000_frame_this_id): Handle
	unavailable PC/SP to build unavailable frame.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] arm-tdep.c: Remove unused "to" parameters
@ 2016-02-23 18:34 sergiodj+buildbot
  2016-02-23 19:21 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-02-23 18:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1254566561957d2202d61e12881b0eb40d33a64c ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: 1254566561957d2202d61e12881b0eb40d33a64c

arm-tdep.c: Remove unused "to" parameters

gdb/ChangeLog:

	* arm-tdep.c (arm_decode_svc_copro): Remove "to" parameter.
	(thumb_process_displaced_insn): Likewise.
	(arm_process_displaced_insn): Adjust calls.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [AArch64] Remove redundant calculation of plt stub destination for veneer
@ 2016-02-22 12:34 sergiodj+buildbot
  2016-02-22 14:23 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-02-22 12:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9a2284679086e32c0c2a46e08b23edde6fc8be85 ***

Author: Jiong Wang <jiong.wang@arm.com>
Branch: master
Commit: 9a2284679086e32c0c2a46e08b23edde6fc8be85

[AArch64] Remove redundant calculation of plt stub destination for veneer

elfNN_aarch64_size_stubs, the caller of aarch64_type_stub has redirected
the final destination of long branch veneer to plt stub if the call
should go through it.

It's redundant to do the same check and redirect again from scratch
inside aarch64_type_stub.

bfd/
  * elfnn-aarch64. (aarch64_type_of_stub): Remove redundation calcuation
  for destination.  Remove useless function parameters.
  (elfNN_aarch64_size_stubs): Update parameters for aarch64_type_of_stub.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Remove search_parents parameter from d_lookup_symbol_imports.
@ 2016-02-21 20:46 sergiodj+buildbot
  2016-02-21 21:12 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-02-21 20:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 30a6a7f035026d05b52c92c26d4cb7ea3c6d6e5c ***

Author: Iain Buclaw <ibuclaw@gdcproject.org>
Branch: master
Commit: 30a6a7f035026d05b52c92c26d4cb7ea3c6d6e5c

Remove search_parents parameter from d_lookup_symbol_imports.

gdb/ChangeLog:

	* d-namespace.c (d_lookup_symbol_imports): Remove argument
	'search_parents'.  All callers updated.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Add D support to gdb_default_target_compile.
@ 2016-02-18 21:14 sergiodj+buildbot
  2016-02-18 22:37 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-02-18 21:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 24f75eadabc519563ed119932c77874a016a799a ***

Author: Iain Buclaw <ibuclaw@gdcproject.org>
Branch: master
Commit: 24f75eadabc519563ed119932c77874a016a799a

Add D support to gdb_default_target_compile.

gdb/testsuite/ChangeLog:

	* lib/future.exp: Add D support.
	(gdb_find_gdc): New proc.
	(gdb_default_target_compile): Add D support.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [x86-64] Omit dynamic sections symbols
@ 2016-02-17 19:31 sergiodj+buildbot
  2016-02-17 20:26 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-02-17 19:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8f79b794ce055b3b4041788182080f4ce3f9048e ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 8f79b794ce055b3b4041788182080f4ce3f9048e

[x86-64] Omit dynamic sections symbols

Define elf_backend_omit_section_dynsym to bfd_true for x86-64, similar
to i386, x86-64 doesn't need dynamic sections symbols.

bfd/

	* elf64-x86-64.c (elf_backend_omit_section_dynsym): New.  Defined
	to bfd_true.

ld/

	* testsuite/ld-ifunc/ifunc-1-local-x86.d: Updated.
	* testsuite/ld-ifunc/ifunc-1-x86.d: Likewise.
	* testsuite/ld-ifunc/ifunc-2-local-x86-64.d: Likewise.
	* testsuite/ld-ifunc/ifunc-2-x86-64.d: Likewise.
	* testsuite/ld-ifunc/ifunc-3a-x86.d: Likewise.
	* testsuite/ld-ifunc/pr17154-x86-64.d: Likewise.
	* testsuite/ld-x86-64/bnd-ifunc-1.d: Likewise.
	* testsuite/ld-x86-64/bnd-ifunc-2.d: Likewise.
	* testsuite/ld-x86-64/bnd-plt-1.d: Likewise.
	* testsuite/ld-x86-64/ilp32-4-nacl.d: Likewise.
	* testsuite/ld-x86-64/ilp32-4.d: Likewise.
	* testsuite/ld-x86-64/load1c-nacl.d: Likewise.
	* testsuite/ld-x86-64/load1c.d: Likewise.
	* testsuite/ld-x86-64/load1d-nacl.d: Likewise.
	* testsuite/ld-x86-64/load1d.d: Likewise.
	* testsuite/ld-x86-64/pr14207.d: Likewise.
	* testsuite/ld-x86-64/pr19162.d: Likewise.
	* testsuite/ld-x86-64/tlsdesc-nacl.rd: Likewise.
	* testsuite/ld-x86-64/tlsdesc.rd: Likewise.
	* testsuite/ld-x86-64/tlsgdesc-nacl.rd: Likewise.
	* testsuite/ld-x86-64/tlsgdesc.rd: Likewise.
	* testsuite/ld-x86-64/tlspic-nacl.rd: Likewise.
	* testsuite/ld-x86-64/tlspic.rd: Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix cleanup in arm_linux_software_single_step
@ 2016-02-16 14:26 sergiodj+buildbot
  2016-02-16 20:16 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-02-16 14:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b442c911ee0e7444ee63edcc7da26089f6023cb6 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: b442c911ee0e7444ee63edcc7da26089f6023cb6

Fix cleanup in arm_linux_software_single_step

I see the following error in testing aarch64 GDB debugging arm
program.

(gdb) PASS: gdb.reverse/readv-reverse.exp: set breakpoint at marker2
continue
Continuing.
=================================================================
==32273==ERROR: AddressSanitizer: attempting free on address which was not malloc()-ed: 0x000000ce4c00 in thread T0
    #0 0x2ba5615645c7 in __interceptor_free (/usr/lib/x86_64-linux-gnu/libasan.so.1+0x545c7)^M
    #1 0x4be8b5 in VEC_CORE_ADDR_cleanup /home/yao/SourceCode/gnu/gdb/git/gdb/common/gdb_vecs.h:34^M
    #2 0x5e6d95 in do_my_cleanups /home/yao/SourceCode/gnu/gdb/git/gdb/common/cleanups.c:154^M
    #3 0x64c99a in fetch_inferior_event /home/yao/SourceCode/gnu/gdb/git/gdb/infrun.c:3975^M
    #4 0x678437 in inferior_event_handler /home/yao/SourceCode/gnu/gdb/git/gdb/inf-loop.c:44^M
    #5 0x5078f6 in remote_async_serial_handler /home/yao/SourceCode/gnu/gdb/git/gdb/remote.c:13223^M
    #6 0x4cecfd in run_async_handler_and_reschedule /home/yao/SourceCode/gnu/gdb/git/gdb/ser-base.c:137^M
    #7 0x676864 in gdb_wait_for_event /home/yao/SourceCode/gnu/gdb/git/gdb/event-loop.c:834^M
    #8 0x676a27 in gdb_do_one_event /home/yao/SourceCode/gnu/gdb/git/gdb/event-loop.c:323^M
    #9 0x676aed in start_event_loop /home/yao/SourceCode/gnu/gdb/git/gdb/event-loop.c:347^M
    #10 0x6706d2 in captured_command_loop /home/yao/SourceCode/gnu/gdb/git/gdb/main.c:318^M
    #11 0x66db8c in catch_errors /home/yao/SourceCode/gnu/gdb/git/gdb/exceptions.c:240^M
    #12 0x6716dd in captured_main /home/yao/SourceCode/gnu/gdb/git/gdb/main.c:1157^M
    #13 0x66db8c in catch_errors /home/yao/SourceCode/gnu/gdb/git/gdb/exceptions.c:240^M
    #14 0x671b7a in gdb_main /home/yao/SourceCode/gnu/gdb/git/gdb/main.c:1165^M
    #15 0x467684 in main /home/yao/SourceCode/gnu/gdb/git/gdb/gdb.c:32^M
    #16 0x2ba563ed7ec4 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21ec4)^M
    #17 0x4676b2 (/scratch/yao/gdb/build-git/aarch64-linux-gnu/gdb/gdb+0x4676b2)

looks we should discard cleanup if function
arm_linux_software_single_step returns early, or create cleanup when
it is needed.

gdb:

2016-02-16  Yao Qi  <yao.qi@linaro.org>

	* arm-linux-tdep.c (arm_linux_software_single_step): Assign
	'old_chain' later.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] stack: check frame_unwind_caller_id
@ 2016-02-12  9:10 sergiodj+buildbot
  2016-02-12 12:23 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-02-12  9:10 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a038fa3e14a477d4d72a26c2e139fa47d2774be2 ***

Author: Markus Metzger <markus.t.metzger@intel.com>
Branch: master
Commit: a038fa3e14a477d4d72a26c2e139fa47d2774be2

stack: check frame_unwind_caller_id

Callers of frame_unwind_caller_* functions are supposed to check
frame_unwind_caller_id.

Add such a check to frame_info and treat an invalid caller ID as if the caller
PC were not available.

gdb/
	* stack.c (frame_info): Check frame_unwind_caller_id.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Correct assertion in NIOS2 linker to allow signed 16-buit immediate values.
@ 2016-02-10 11:38 sergiodj+buildbot
  2016-02-11  8:51 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-02-10 11:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 83da6e748c8f105f07e17f53aa6b99ed7867ff5f ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: 83da6e748c8f105f07e17f53aa6b99ed7867ff5f

Correct assertion in NIOS2 linker to allow signed 16-buit immediate values.

	PR 19405
	* elf32-nios2.c (nios2_elf32_install_imm16): Allow for signed
	immediate values.
	* elf-eh-frame.c (_bfd_elf_discard_section_eh_frame): Limit the
	number of messages about FDE encoding preventing .eh_frame_hdr
	generation.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Use string_to_event_location_basic in guile.
@ 2016-02-09 23:05 sergiodj+buildbot
  2016-02-10  9:45 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-02-09 23:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a96e36da2f5278949099b0b985b2fa6ce474b135 ***

Author: Keith Seitz <keiths@redhat.com>
Branch: master
Commit: a96e36da2f5278949099b0b985b2fa6ce474b135

Use string_to_event_location_basic in guile.

This patch, analogous to the previous python patch, implements proper
legacy linespec support in guile code using the newly introduced
string_to_event_location_basic.

gdb/ChangeLog

	* guile/scm-breakpoint.c (gdbscm_register_breakpoint_x): Skip
	leading whitespace and use string_to_event_location_basic instead
	of new_linespec_location.

gdb/testsuite/ChangeLog

	* gdb.guile/scm-breakpoint.exp (test_bkpt_address): New procedure.
	(toplevel): Call test_bkpt_address.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Refactor string_to_event_location for legacy linespec support.
@ 2016-02-09 22:48 sergiodj+buildbot
  2016-02-09 23:48 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-02-09 22:48 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT eeb1af437c6f1ca111bc31b63eefc5344b553681 ***

Author: Keith Seitz <keiths@redhat.com>
Branch: master
Commit: eeb1af437c6f1ca111bc31b63eefc5344b553681

Refactor string_to_event_location for legacy linespec support.

This patch refactors string_to_event_location, breaking it into two
separate functions:

1) string_to_event_location_basic
A "basic" string parser that implements support for "legacy" linespecs
(linespec, address, and probe locations).  This function is intended to
be used by any UI wishing/needing to support this legacy behavior.

2) string_to_event_location
This is now intended as a CLI-only function which adds explicit location
parsing in a CLI-appropriate manner (in the form of traditional option/value
pairs).

Together these patches serve to simplify string-to-event location parsing
for all existing non-CLI interfaces (MI, guile, and python).

gdb/ChangeLog

	* location.c (string_to_explicit_location): Note that "-p" is
	reserved for probe locations and return NULL for any input
	that starts with that.
	(string_to_event_location): Move "legacy" linespec code to ...
	(string_to_event_location_basic): ... here.
	* location.h (string_to_event_location): Update comment.
	(string_to_event_location_basic): New function.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
[parent not found: <8adce0342f5f50aba0154fc56ca59df45b219738@gdb-build>]
* [binutils-gdb] Add a more helpful warning message to explain why some AArch64 relocations can overflow.
@ 2016-02-09 11:06 sergiodj+buildbot
  2016-02-09 15:39 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-02-09 11:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 027e9c750c20fe8031a2b6d6272cd57bbf445df5 ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: 027e9c750c20fe8031a2b6d6272cd57bbf445df5

Add a more helpful warning message to explain why some AArch64 relocations can overflow.

bfd	* elfnn-aarch64.c (elfNN_aarch64_relocate_section): Add a more
	helpful warning message to explain why certain AArch64 relocs
	might overflow.

ld	* testsuite/ld-aarch64/reloc-overflow-bad.d: New test.
	* testsuite/ld-aarch64/reloc-overflow-1.s: New source file.
	* testsuite/ld-aarch64/reloc-overflow-2.s: New source file.
	* testsuite/ld-aarch64/aarch64-elf.exp: Run the new test.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix in-tree, parallel running of Ada tests
@ 2016-02-08 19:12 sergiodj+buildbot
  2016-02-08 20:56 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-02-08 19:12 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 437277d47a15711f29e02e5265ce8bbb8c8ef4f5 ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: 437277d47a15711f29e02e5265ce8bbb8c8ef4f5

Fix in-tree, parallel running of Ada tests

While testing the following patch,

  [PATCH] Always organize test artifacts in a directory hierarchy
  https://sourceware.org/ml/gdb-patches/2016-01/msg00133.html

I noticed that it broke Ada testing.  This lead me to think that
parallel testing when building in-tree didn't work previously in Ada.
It is confirmed by this test:

$ make check TESTS="gdb.ada/fun_addr.exp" -j 2
...
Running ./gdb.ada/fun_addr.exp ...
FAIL: gdb.ada/fun_addr.exp: compilation foo.adb
...

This patch fixes in-tree parallel testing for Ada, and consequently
serial and parallel testing when the aforementioned patch is applied.

The problem originates from the fact that Ada support code cd's to the
builddir before compiling.  In itself it's not a problem, it allows to
place intermediate auto-generated files in that directory.  The Ada
compilation refers to the source file, which is in another directory,
only by its base name (e.g. foo.adb).  In serial mode, that worked
because builddir was the same as the source directory (e.g.
gdb.ada/fun_addr/).  In an out-of-tree build, it works because the
source directory is added as an include directory (note: this is not the
same $srcdir as autoconf's):

  set srcdir [file dirname $source]
  additional_flags=-I$srcdir

which becomes:

  additional_flags=-I/home/emaisin/build/binutils-gdb/gdb/testsuite/gdb.ada/fun_addr

However, when building in-tree, srcdir is relative: ./gdb.ada/fun_addr.
When using parallel or always-in-outputs-directory mode, we are cd'ed in
the outputs directory.  So -I$srcdir is relative to the current
directory, which is wrong.

To fix it, I made the TCL variable srcdir (set in site.exp, from which
everything else is derived) always absolute.  It is done by assigning
autoconf's abs_srcdir instead of autoconf's srcdir.  This way -I$srcdir
will always be good, regardless of where we cd'ed to.  A small apparent
change is that when running tests, DejaGnu will say:

  Running /tmp/binutils-gdb/gdb/testsuite/gdb.ada/fun_addr.exp ...

instead of

  Running ./gdb.ada/fun_addr.exp ...

I hope it's not too much of an annoyance.  I think that it should make
the testsuite a tiny bit more robust against other bugs of the same
class.

Regtested in & out of tree, only with native target.

gdb/testsuite/ChangeLog:

	* Makefile.in (abs_srcdir): Assign @abs_srcdir@.
	(site.exp): Assign abs_srcdir to tcl's srcdir.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] gdb: Guard against undefined behaviour in mi-vla-fortran.exp
@ 2016-02-01 18:40 sergiodj+buildbot
  2016-02-01 20:19 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-02-01 18:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 37a8db1a336ce78a46bf7f303e47e17b2a1bf694 ***

Author: Andrew Burgess <andrew.burgess@embecosm.com>
Branch: master
Commit: 37a8db1a336ce78a46bf7f303e47e17b2a1bf694

gdb: Guard against undefined behaviour in mi-vla-fortran.exp

The test gdb.mi/mi-vla-fortran.exp reveals an issue with the DWARF
generated by gfortran.

In the test a pointer variable 'pvla2' is created:
    real, pointer :: pvla2 (:, :)

Initially this variable will be unassociated, so something like this:
    l = associated(pvla2)

should return false.

In the test gdb stops at a point _before_ pvla2 is associated with
anything, and we then try to print pvla2, the expectation is that gdb
should reply <not associated>.

The problem is that the data the DWARF directs gdb to read (to identify
if the variable is associated or not) is not initialised until the first
time pvla2 is accessed.

As a result gdb ends up reading uninitialised memory, sometimes this
uninitialised memory indicates the variable is associated (when it's
not).  This first mistake can lead to a cascade of errors, reading
uninitialised memory, with the result that gdb builds an invalid type to
associate with the variable pvla2.

In some cases, this invalid type can be very large, which when we try to
print pvla2 causes gdb to allocate a large amount of memory.

A recent commit added a new gdb variable 'max-value-size', which
prevents gdb from allocating values of extreme size.  As a result
directly trying to print pvla2 will now now error rather than allocate a
large amount of memory.

However, some of the later tests create a varobj for pvla2, and then
ask for the children of that varobj to be displayed.  In the case where
an invalid type has been computed for pvla2 then the number of children
can be wrong, and very big, in which case trying to display all of these
children can cause gdb to consume an excessive amount of memory.

This commit first detects if printing pvla2 triggers the max-value-size
error, if it does then we avoid all the follow on tests relating to the
unassociated pvla2, which avoids the second error printing the varobj
children.

gdb/testsuite/ChangeLog:

	* gdb.mi/mi-vla-fortran.exp: Add XFAIL for accessing unassociated
	pointer.  Don't perform further tests on the unassociated pointer
	if the first test fails.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] gdb: New set/show max-value-size command.
@ 2016-02-01 18:23 sergiodj+buildbot
  2016-02-01 19:03 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-02-01 18:23 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5fdf6324fafd60f967e2e8323fdacf84b1bfcea3 ***

Author: Andrew Burgess <andrew.burgess@embecosm.com>
Branch: master
Commit: 5fdf6324fafd60f967e2e8323fdacf84b1bfcea3

gdb: New set/show max-value-size command.

For languages with dynamic types, an incorrect program, or uninitialised
variables within a program, could result in an incorrect, overly large
type being associated with a value.  Currently, attempting to print such
a variable will result in gdb trying to allocate an overly large buffer.

If this large memory allocation fails then the result can be gdb either
terminating, or (due to memory contention) becoming unresponsive for the
user.

A new user visible variable in gdb helps guard against such problems,
two new commands are available:

   set max-value-size
   show max-value-size

The 'max-value-size' is the maximum size of memory in bytes that gdb
will allocate for the contents of a value.  Any attempt to allocate a
value with a size greater than this will result in an error.  The
initial default for this limit is set at 64k, this is based on a similar
limit that exists within the ada specific code.

It is possible for the user to set max-value-size to unlimited, in which
case the old behaviour is restored.

gdb/ChangeLog:

	* value.c (max_value_size): New variable.
	(MIN_VALUE_FOR_MAX_VALUE_SIZE): New define.
	(show_max_value_size): New function.
	(check_type_length_before_alloc): New function.
	(allocate_value_contents): Call check_type_length_before_alloc.
	(set_value_enclosing_type): Likewise.
	(_initialize_values): Add set/show handler for max-value-size.
	* NEWS: Mention new set/show command.

gdb/doc/ChangeLog:

	* gdb.texinfo (Value Sizes): New section.
	(Data): Add the 'Value Sizes' node to the menu.

gdb/testsuite/ChangeLog:

	* gdb.base/max-value-size.c: New file.
	* gdb.base/max-value-size.exp: New file.
	* gdb.base/huge.exp: Disable max-value-size for this test.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Check reloc against IFUNC symbol only with dynamic symbols
@ 2016-01-31  0:17 sergiodj+buildbot
  2016-01-31  3:24 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-01-31  0:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d9e3b590692e62d83c21e39ec6641c4c09e70e4c ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: d9e3b590692e62d83c21e39ec6641c4c09e70e4c

Check reloc against IFUNC symbol only with dynamic symbols

There is no need to check relocation IFUNC symbol if there are no
dynamic symbols.

bfd/

	PR ld/19539
	* elf32-i386.c (elf_i386_reloc_type_class): Check relocation
	against STT_GNU_IFUNC symbol only with dynamic symbols.
	* elf64-x86-64.c (elf_x86_64_reloc_type_class): Likewise.

ld/

	PR ld/19539
	* testsuite/ld-elf/pr19539.d: New file.
	* testsuite/ld-elf/pr19539.s: Likewise.
	* testsuite/ld-elf/pr19539.t: Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix two misleading indentation warnings
@ 2016-01-29 20:45 sergiodj+buildbot
  2016-01-29 21:35 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-01-29 20:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a2e3e93f4423899d99687da3ce4ac57cbed437f9 ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: a2e3e93f4423899d99687da3ce4ac57cbed437f9

Fix two misleading indentation warnings

Two small changes so everything builds with latest GCC and its
-Wmisleading-indentation.

In the aarch64-tdep.c case, the two misindented lines should actually be
part of the for loop.  It looks like the indentation is all done using
spaces in that file though...  I fixed it (changed for tabs + spaces) for
the lines I touched.

In the xcoffread.c case, we can simply remove the braces and fix the
indentation.

gdb/ChangeLog:

	* aarch64-tdep.c (aarch64_record_asimd_load_store): Add braces
	to for include additional lines.
	* xcoffread.c (scan_xcoff_symtab): Remove unnecessary braces.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Sync libiberty with GCC.
@ 2016-01-28 21:00 sergiodj+buildbot
  2016-01-28 21:37 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-01-28 21:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9d98de835cb018419e0ef97db37fcf9061247750 ***

Author: Iain Buclaw <ibuclaw@gdcproject.org>
Branch: master
Commit: 9d98de835cb018419e0ef97db37fcf9061247750

Sync libiberty with GCC.

libiberty/ChangeLog:
	* d-demangle.c (dlang_call_convention): Handle extern Objective-C
	function calling convention.
	(dlang_call_convention_p): Likewise.
	(dlang_type): Likewise.
	* testsuite/d-demangle-expected: Add coverage tests.

	* d-demangle.c (dlang_function_args): Append ',' for variadic functions
	only if parameters were seen before the elipsis symbol.
	* testsuite/d-demangle-expected: Add coverage test for parameter-less
	variadic functions.

	* d-demangle.c (dlang_type): Handle function types only in the context
	of seeing a pointer type symbol.
	* testsuite/d-demangle-expected: Update function pointer tests.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [GDBserver] Use regcache_read_pc in install_software_single_step_breakpoints
@ 2016-01-26 14:40 sergiodj+buildbot
  2016-01-26 17:08 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-01-26 14:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d80209703ec2fc85e0a4b3d4d23e7ed448987aca ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: d80209703ec2fc85e0a4b3d4d23e7ed448987aca

[GDBserver] Use regcache_read_pc in install_software_single_step_breakpoints

In install_software_single_step_breakpoints, we've got the regcache
of current_thread, so we don't have to bother get_pc to get pc,
instead we can get pc from regcache directly.  Note that the callers
of install_software_single_step_breakpoints have already switched
current_thread to LWP.

Since the pc is got from regcache_read_pc, in the next patch, we can
get pc inside the implementation of *the_low_target.get_next_pcs and
stop passing pc to *the_low_target.get_next_pcs.

gdb/gdbserver:

2016-01-26  Yao Qi  <yao.qi@linaro.org>

	* linux-low.c (install_software_single_step_breakpoints): Call
	regcache_read_pc instead of get_pc.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [GDBserver] Check input interrupt after reading in a packet
@ 2016-01-26 14:03 sergiodj+buildbot
  2016-01-26 14:43 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-01-26 14:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 18879fef1741464e522624bcc529048400453e0d ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 18879fef1741464e522624bcc529048400453e0d

[GDBserver] Check input interrupt after reading in a packet

GDBserver may read some packet together with '\003' in one go.  We've
already checked '\003' first when reading packet by my patch,

  Check input interrupt first when reading packet
  https://sourceware.org/ml/gdb-patches/2016-01/msg00057.html

but if we don't check '\003' *after* each packet, the interrupt will
be processed next time GDBserver reads from the buffer, so that the
interrupt isn't processed in time.  For example, GDB sends vCont;c and
interrupt (see gdb.base/interrupt-noterm.exp), we'll resume the
inferior and wait once packet vCont;c is seen.  If we don't check the
interrupt character after vCont;c packet, interrupt character will stay
in the buffer unattended until GDBserver returns from the wait, which
may take a while.  Note that since we've read '\003' from file
descriptor, SIGIO signal handler input_interrupt doesn't help either.

This issue can be exposed by hacking the end of getpkt like
@@ -1041,6 +1050,9 @@ getpkt (char *buf)
        }
     }

+  if (readchar_bufcnt > 0)
+    gdb_assert (*readchar_bufp != '\003');
+
   return bp - buf;
 }

and this can trigger internal error,
(gdb) PASS: gdb.base/interrupt-noterm.exp: interrupt
Remote connection closed^M
(gdb) FAIL: gdb.base/interrupt-noterm.exp: inferior received SIGINT
Remote debugging from host 10.2.206.40^M
/home/yao/SourceCode/gnu/gdb/git/gdb/gdbserver/remote-utils.c:1054: A problem internal to GDBserver has been detected.^M
getpkt: Assertion `*readchar_bufp != '\003'' failed.^M

This patch is to peek the buffer, if it is '\003', consume it and call
*the_target->request_interrupt.

gdb/gdbserver:

2016-01-26  Yao Qi  <yao.qi@linaro.org>

	* remote-utils.c (getpkt): If the buffer isn't empty, and the
	first character is '\003', call *the_target->request_interrupt.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix memory corruption on Mach-O systems by suppressing a memory tidy up.
@ 2016-01-25  9:41 sergiodj+buildbot
  2016-01-25  9:47 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-01-25  9:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cf466c2ac5ac55bb9b30b96fbdcad564e8c1ccc8 ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: cf466c2ac5ac55bb9b30b96fbdcad564e8c1ccc8

Fix memory corruption on Mach-O systems by suppressing a memory tidy up.

	PR target/19435
	* mach-o.c (bfd_mach_o_close_and_cleanup): Suppress code to free
	dsym filename buffer.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] * lib/ada.exp (gdb_compile_ada): Fix typo.
@ 2016-01-22  0:30 sergiodj+buildbot
  2016-01-22  8:19 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-01-22  0:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4f5946a8630ec027d412ee078974f8d92e5ab3a0 ***

Author: Doug Evans <dje@google.com>
Branch: master
Commit: 4f5946a8630ec027d412ee078974f8d92e5ab3a0

* lib/ada.exp (gdb_compile_ada): Fix typo.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix regression introduced in "break *<EXPR>" by explicit location patches.
@ 2016-01-21 10:33 sergiodj+buildbot
  2016-01-21 18:04 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-01-21 10:33 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 305e13e67faaf940ce6eb708847a655a0735a651 ***

Author: Joel Brobecker <brobecker@adacore.com>
Branch: master
Commit: 305e13e67faaf940ce6eb708847a655a0735a651

Fix regression introduced in "break *<EXPR>" by explicit location patches.

A relatively recent patch support for explicit locations, and part
of that patch cleaned up the way we parse breakpoint locations.
Unfortunatly, a small regression crept in for "*<EXPR>" breakpoint
locations. In particular, on PIE programs, one can see the issue by
doing the following, with any program:

    (gdb) b *main
    Breakpoint 1 at 0x51a: file hello.c, line 3.
    (gdb) run
    Starting program: /[...]/hello
    Error in re-setting breakpoint 1: Warning:
    Cannot insert breakpoint 1.
    Cannot access memory at address 0x51a

    Warning:
    Cannot insert breakpoint 1.
    Cannot access memory at address 0x51a

Just for the record, this regression was introduced by:

    commit a06efdd6effd149a1d392df8d62824e44872003a
    Date:   Tue Aug 11 17:09:35 2015 -0700
    Subject: Explicit locations: introduce address locations

What happens is that the patch makes the implicit assumption that
the address computed the first time is static, as if it was designed
to only support litteral expressions (Eg. "*0x1234"). This allows
the shortcut of not re-computing the breakpoint location's address
when re-setting breakpoints.

However, this does not work in general, as demonstrated in the example
above.

This patch plugs that hole simply by saving the original expression
used to compute the address as part of the address location, so as
to then re-evaluate that expression during breakpoint re-set.

gdb/ChangeLog:

        * location.h (new_address_location): Add new parameters
        "addr_string" and "addr_string_len".
        (get_address_string_location): Add declaration.
        * location.c (new_address_location): Add new parameters
        "addr_string" and "addr_string_len".  If not NULL, store
        a copy of the addr_string in the new location as well.
        (get_address_string_location): New function.
        (string_to_event_location): Update call to new_address_location.
        * linespec.c (event_location_to_sals) <ADDRESS_LOCATION>:
        Save the event location in the parser's state before
        passing it to convert_address_location_to_sals.
        * breakpoint.c (create_thread_event_breakpoint): Update call
        to new_address_location.
        (init_breakpoint_sal): Get the event location's string, if any,
        and use it to update call to new_address_location.
        * python/py-finishbreakpoint.c (bpfinishpy_init):
        Update call to new_address_location.
        * spu-tdep.c (spu_catch_start): Likewise.

        * config/djgpp/fnchange.lst: Add entries for
        gdb/testsuite/gdb.base/break-fun-addr1.c and
        gdb/testsuite/gdb.base/break-fun-addr2.c.

gdb/testsuite/ChangeLog:

        * gdb.base/break-fun-addr.exp: New file.
        * gdb.base/break-fun-addr1.c: New file.
        * gdb.base/break-fun-addr2.c: New file.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [AArch64] Reject invalid immediate operands to MSR UAO
@ 2016-01-20 14:43 sergiodj+buildbot
  2016-01-21  6:15 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-01-20 14:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0bff6e2d6942690d81ce1f33728de07835b0f5b7 ***

Author: Matthew Wahab <matthew.wahab@arm.com>
Branch: master
Commit: 0bff6e2d6942690d81ce1f33728de07835b0f5b7

[AArch64] Reject invalid immediate operands to MSR UAO

In the instruction to write to the ARMv8.2 PSTATE field UAO,
MSR UAO, #<imm>, the immediate should be either 0 or 1 but GAS accepts
any unsigned 4-bit integer.

This patch implements the constraint on the immediate, generating an
error if the immediate operand is invalid, and adds tests for the
illegal forms.

opcodes/
2016-01-20  Matthew Wahab  <matthew.wahab@arm.com>

	* aarch64-opc.c (operand_general_constraint_met_p): Check validity
	of MSR UAO immediate operand.

gas/
2016-01-20  Matthew Wahab  <matthew.wahab@arm.com>

	* testsuite/gas/aarch64/armv8_2-a-illegal.d: New.
	* testsuite/gas/aarch64/armv8_2-a-illegal.l: New.
	* testsuite/gas/aarch64/armv8_2-a-illegal.s: New.

Change-Id: Ibdec4967c00b1ef3be9dbc43d23b2c70d1a0b28c


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Add support for an ARM specific 'y' section attribute flag to mark the section as NOREAD.
@ 2016-01-20 13:05 sergiodj+buildbot
  2016-01-21  0:30 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-01-20 13:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 91f68a68f992e3f6c3da26c616b5257230bd1eec ***

Author: Mickael Guene <mickael.guene@st.com>
Branch: master
Commit: 91f68a68f992e3f6c3da26c616b5257230bd1eec

Add support for an ARM specific 'y' section attribute flag to mark the section as NOREAD.

bfd/ChangeLog:
      * elf32-arm.c ((elf32_arm_special_sections): Remove catch of noread
      section using '.text.noread' pattern.

gas/ChangeLog:
      * config/obj-elf.c (obj_elf_change_section) : Allow arm section with
      SHF_ARM_NOREAD section flag.
      * config/tc-arm.h (md_elf_section_letter) : Implement this hook to
      handle letter 'y'.
     (arm_elf_section_letter) : Declare it.
      * config/tc-arm.c (arm_elf_section_letter): Handle letter 'y' to set
      SHF_ARM_NOREAD section flag.
      * doc/c-arm.texi (ARM section attribute 'y'): Document it.

gas/testsuite/ChangeLog:
      * gas/arm/section-execute-only.s: New test case.
      * gas/arm/section-execute-only.d: Expected output.

ld/testsuite/ChangeLog:
      * ld-arm/thumb1-noread-not-present-mixing-two-section.s: Add 'y'
      attribute usage.
      * ld-arm/thumb1-noread-present-one-section.s: Likewise.
      * ld-arm/thumb1-noread-present-two-section.s: Likewise.
      * ld-arm/thumb1-input-section-flag-match.s: Likewise.

binutils/ChangeLog:
      * readelf.c (get_elf_section_flags): Display y letter for section
      with SHF_ARM_NOREAD section flag in readelf section output.
      (process_section_headers): Add y letter in readelf section output
      key mapping for ARM architecture.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] minor reformatting in printcmd.c::print_scalar_formatted
@ 2016-01-20  4:14 sergiodj+buildbot
  2016-01-20 20:44 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-01-20  4:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT be56871ee8f65c51b9eee611532ed036a71a72e0 ***

Author: Joel Brobecker <brobecker@adacore.com>
Branch: master
Commit: be56871ee8f65c51b9eee611532ed036a71a72e0

minor reformatting in printcmd.c::print_scalar_formatted

(GNU Coding Standard...)

gdb/ChangeLog:

        * printcmd.c (print_scalar_formatted): move binary operator from
        end of line to beginning of next line.  Adjust formatting
        accordingly.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Use a separate variable for the size passed to sysctl.
@ 2016-01-19 23:43 sergiodj+buildbot
  2016-01-20 15:31 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-01-19 23:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f2feec9809edbeeee0bb5b036e4ae25f9c37cd14 ***

Author: John Baldwin <jhb@FreeBSD.org>
Branch: master
Commit: f2feec9809edbeeee0bb5b036e4ae25f9c37cd14

Use a separate variable for the size passed to sysctl.

This fixes a sign mismatch warning.

gdb/ChangeLog:

	* fbsd-nat.c (fbsd_pid_to_exec_file): Use new "buflen" instead of
	"len" with sysctl.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Dump register notes for each thread when generating a FreeBSD core.
@ 2016-01-19 18:00 sergiodj+buildbot
  2016-01-20 11:47 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-01-19 18:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 20a0aab3ed0f4bb5c304e560751b09b7b82a3e65 ***

Author: John Baldwin <jhb@FreeBSD.org>
Branch: master
Commit: 20a0aab3ed0f4bb5c304e560751b09b7b82a3e65

Dump register notes for each thread when generating a FreeBSD core.

gdb/ChangeLog:

	* fbsd-tdep.c (find_stop_signal): Remove.
	(struct fbsd_collect_regset_section_cb) <lwp>: New field.
	<stop_signal>: New field.
	<abort_iteration>: New field.
	(fbsd_collect_regset_section_cb): Use new fields.
	(fbsd_collect_thread_registers): New function.
	(struct fbsd_corefile_thread_data): New structure.
	(fbsd_corefile_thread): New function.
	(fbsd_make_corefile_notes): Use new function to dump notes for each
	non-exited thread in a process.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Add support for extracting thread names from cores.
@ 2016-01-19 17:26 sergiodj+buildbot
  2016-01-20  4:26 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-01-19 17:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4dfc5dbc4e1b267d440dd515a42fe6fd96a8d860 ***

Author: John Baldwin <jhb@FreeBSD.org>
Branch: master
Commit: 4dfc5dbc4e1b267d440dd515a42fe6fd96a8d860

Add support for extracting thread names from cores.

Add a new gdbarch method to extract a thread name from a core for a
given thread.  Use this new method in core_thread_name to implement the
to_thread_name target op.

gdb/ChangeLog:

	* corelow.c (core_thread_name): New function.
	(init_core_ops): Use "core_thread_name" for the "to_thread_name"
	target op.
	* gdbarch.sh (core_thread_name): New gdbarch callback.
	* gdbarch.h: Re-generate.
	* gdbarch.c: Re-generate.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] MIPS: Only build microMIPS specific simulator functions if microMIPS support is required.
@ 2016-01-18 22:01 sergiodj+buildbot
  2016-01-18 23:14 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-01-18 22:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3d304f48cafbff4b7a1c0a9d338fb20aa4e4934b ***

Author: Andrew Bennett <andrew.bennett@imgtec.com>
Branch: master
Commit: 3d304f48cafbff4b7a1c0a9d338fb20aa4e4934b

MIPS: Only build microMIPS specific simulator functions if microMIPS support is required.

This fixes PR sim/19441.  In the MIPS simulator the microMIPS
functions in micromips.igen were not predicated on the microMIPS
models.  This was causing build issues for some target triples.
This patch sets all the microMIPS specific functions to only be built if
the micromips32, micromips64 or micromipsdsp models are used.

	PR sim/19441
	* micromips.igen (delayslot_micromips): Enable for `micromips32',
	`micromips64' and `micromipsdsp' only.
	(process_isa_mode): Enable for `micromips32' and `micromips64' only.
	(do_micromips_jalr, do_micromips_jal): Likewise.
	(compute_movep_src_reg): Likewise.
	(compute_andi16_imm): Likewise.
	(convert_fmt_micromips): Likewise.
	(convert_fmt_micromips_cvt_d): Likewise.
	(convert_fmt_micromips_cvt_s): Likewise.
	(FMT_MICROMIPS): Likewise.
	(FMT_MICROMIPS_CVT_D): Likewise.
	(FMT_MICROMIPS_CVT_S): Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Replace some $ARCH_{get, set}_pc with linux_{get, set}_pc_64bit
@ 2016-01-18 15:19 sergiodj+buildbot
  2016-01-18 17:29 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-01-18 15:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6f69e520676f5f434cf43c250865036b3d516429 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 6f69e520676f5f434cf43c250865036b3d516429

Replace some $ARCH_{get,set}_pc with linux_{get,set}_pc_64bit

This patch is the follow-up of
https://sourceware.org/ml/gdb-patches/2016-01/msg00164.html to provide
linux_{get,set}_pc_64bit functions.

Rebuild GDBserver with tilegx-linux-gcc.  Not tested.

I think about pc in Tile-GX a little bit.  Looks current Tile-GX
supports debugging 32-bit program (multi-arch), but PC is always
64-bit.  See this thread
https://sourceware.org/ml/gdb-patches/2013-02/msg00113.html
and GDBserver reads PC as 64-bit through ptrace.  However, if
the inferior is 32-bit, the PC in the target description and
regcache is 32-bit, so only 32-bit contents are sent back GDB.
Anyway, Tile-GX GDBserver may have some problems here, but this
patch doesn't change anything.

gdb/gdbserver:

2016-01-18  Yao Qi  <yao.qi@linaro.org>

	* linux-low.c (linux_set_pc_64bit): New function.
	(linux_get_pc_64bit): New function.
	* linux-low.h (linux_set_pc_64bit, linux_get_pc_64bit):
	Declare.
	* linux-sparc-low.c (debug_threads): Remove declaration.
	(sparc_get_pc): Remove.
	(the_low_target): Use linux_get_pc_64bit instead of
	sparc_get_pc.
	* linux-tile-low.c (tile_get_pc, tile_set_pc): Remove.
	(the_low_target): Use linux_get_pc_64bit and
	linux_set_pc_64bit.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Remove trademark acknowledgements throughout
@ 2016-01-12 15:09 sergiodj+buildbot
  2016-01-12 15:52 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-01-12 15:09 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bc504a311794145e7aef2011f31ea87aa64bea4c ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: bc504a311794145e7aef2011f31ea87aa64bea4c

Remove trademark acknowledgements throughout

The GNU Coding Standards say:

  "Please do not include any trademark acknowledgements in GNU
  software packages or documentation."

gdb/ChangeLog:
2016-01-12  Pedro Alves  <palves@redhat.com>

	Remove use of the registered trademark symbol throughout.

gdb/gdbserver/ChangeLog:
2016-01-12  Pedro Alves  <palves@redhat.com>

	Remove use of the registered trademark symbol throughout.

gdb/doc/ChangeLog:
2016-01-12  Pedro Alves  <palves@redhat.com>

	Remove use of the registered trademark symbol throughout.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] testsuite: Fix false FAILs on too long base directory
@ 2016-01-11 21:16 sergiodj+buildbot
  2016-01-11 22:13 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-01-11 21:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c0ecb95f3dc0c3e8d1545f0a37c0c3e537e1ea96 ***

Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Branch: master
Commit: c0ecb95f3dc0c3e8d1545f0a37c0c3e537e1ea96

testsuite: Fix false FAILs on too long base directory

I was getting

gu (print arg0)^M
= 0x7fffffffdafb
"/unsafebuild-x86_64-redhat-linux-gnu/gdb/testsuite.unix.-m64/outputs/gdb.guile/scm-value/scm-"...^M
(gdb) FAIL: gdb.guile/scm-value.exp: verify dereferenced value
python print (arg0)^M
0x7fffffffdafd
"/unsafebuild-x86_64-redhat-linux-gnu/gdb/testsuite.unix.-m64/outputs/gdb.python/py-value/py-v"...^M
(gdb) FAIL: gdb.python/py-value.exp: verify dereferenced value

and also:

(gdb) p argv[0]^M
$2 = 0x7fffffffd832 "/home/jkratoch/redhat/gdb-test-", 'x' <repeats 169
times>...^M
(gdb) FAIL: gdb.guile/scm-value.exp: argv[0] should be available on this
target

gdb/testsuite/ChangeLog
2016-01-11  Jan Kratochvil  <jan.kratochvil@redhat.com>

	* gdb.guile/scm-value.exp (test_value_in_inferior): Set print elements
	and repeats to unlimited.
	* gdb.python/py-value.exp: Likewise.
	* lib/gdb.exp (gdb_has_argv0): Save and temporarily set print elements
	and repeats to unlimited.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Delete opcodes that have been removed from ISA 3.0.
@ 2016-01-11 18:06 sergiodj+buildbot
  2016-01-11 18:53 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-01-11 18:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT afa8d4054b8e0b1384f2d07f1c15163c0699d660 ***

Author: Peter Bergner <bergner@vnet.ibm.com>
Branch: master
Commit: afa8d4054b8e0b1384f2d07f1c15163c0699d660

Delete opcodes that have been removed from ISA 3.0.

opcodes/
	* ppc-opc.c <xscmpnedp>: Delete.
	<xvcmpnedp>: Likewise.
	<xvcmpnedp.>: Likewise.
	<xvcmpnesp>: Likewise.
	<xvcmpnesp.>: Likewise.

gas/
	* testsuite/gas/ppc/power9.d <xscmpnedp, xvcmpnedp, xvcmpnedp.,
	xvcmpnesp, xvcmpnesp.>: Delete tests.
	* testsuite/gas/ppc/power9.s: Likewise.
	* testsuite/gas/ppc/vsx3.d: Likewise.
	* testsuite/gas/ppc/vsx3.s: Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] sim: move many common settings from CPPFLAGS to config.h
@ 2016-01-11  0:08 sergiodj+buildbot
  2016-01-11  5:36 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2016-01-11  0:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ce39bd389039d99458950b072550ab52f0a07a34 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: ce39bd389039d99458950b072550ab52f0a07a34

sim: move many common settings from CPPFLAGS to config.h

Rather than stuffing the command line with a bunch of -D flags, start
moving things to config.h which is managed by autoheader.  This makes
the makefile a bit simpler and the build output tighter, and it makes
the migration to automake easier as there are fewer vars to juggle.

We'll want to move the other options out too, but it'll take more work.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] sim: ppc: track closed state of file descriptors 0, 1, and 2.
@ 2015-12-30  0:30 sergiodj+buildbot
  2015-12-30  1:39 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-12-30  0:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 90d99f327063af7d87c61234896d4a1dbe073a43 ***

Author: Kevin Buettner <kevinb@redhat.com>
Branch: master
Commit: 90d99f327063af7d87c61234896d4a1dbe073a43

sim: ppc: track closed state of file descriptors 0, 1, and 2.

This change tracks the "closed" state of file descriptors 0, 1, and 2,
introducing the function fdbad() to emul_netbsd.c and emul_unix.c.
Note that a function of the same name and purpose exists in
sim/common/callback.c.

This patch eliminates all of the "unresolved testcases" when testing
GDB against the powerpc simulator.

This occurs because the powerpc simulator closes, on behalf of the
testcase, the file descriptors associated with stdin, stdout, and
stderr.  GDB still needs these descriptors to communicate with the
user or, in this case, with the testing framework.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] sim: sim-core: pass down cpu to hw accesses when available
@ 2015-12-26 19:56 sergiodj+buildbot
  2015-12-26 22:15 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-12-26 19:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT dea10706e9159ba6e94eab4c25010f3006d033a0 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: dea10706e9159ba6e94eab4c25010f3006d033a0

sim: sim-core: pass down cpu to hw accesses when available

The bfin port has been using the device callback largely so it could be
passed the cpu when available.  Add this logic to the common core code
so all ports get access to the active cpu.

The semantics of these buffer functions are changed slightly in that
errors halt the engine synchronously rather than returning the length
to the caller.  We'll probably adjust this in a follow up commit.

The bfin code isn't updated just yet as it has a bit more logic in the
device layer that needs to be unwound at which point we can delete it
entirely.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] sim: arm: delete unused code
@ 2015-12-25  8:19 sergiodj+buildbot
  2015-12-26  7:58 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-12-25  8:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 91d6df784db745df2b0a6827de8306246083bc94 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 91d6df784db745df2b0a6827de8306246083bc94

sim: arm: delete unused code

These vestiges of the 20 year old emulator are just getting in the way.
Punt all the dead code we either don't compile or don't use.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] sim: delete SIM_HAVE_MEM_SIZE
@ 2015-12-25  1:00 sergiodj+buildbot
  2015-12-25 13:52 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-12-25  1:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b1af947345ccba81244d3370756d0047d3bc8b6e ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: b1af947345ccba81244d3370756d0047d3bc8b6e

sim: delete SIM_HAVE_MEM_SIZE

This define isn't used anywhere (doesn't seem to ever have been used by
versions committed), so delete the commented out code as it's dead.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] sim: delete SIM_HAVE_SIMCACHE
@ 2015-12-25  0:34 sergiodj+buildbot
  2015-12-25  3:20 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-12-25  0:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8abe6c668e9336418277e64983587f121c8534e6 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 8abe6c668e9336418277e64983587f121c8534e6

sim: delete SIM_HAVE_SIMCACHE

This was used by the old run interface, but we punted that awhile ago,
so drop this define too.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [testsuite/Ada] stop using project files when building test programs
@ 2015-12-24  5:38 sergiodj+buildbot
  2015-12-24  6:16 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-12-24  5:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ab8314b3d99625c9a2125d39f4f3e74bf9e49cce ***

Author: Joel Brobecker <brobecker@adacore.com>
Branch: master
Commit: ab8314b3d99625c9a2125d39f4f3e74bf9e49cce

[testsuite/Ada] stop using project files when building test programs

The current approach when building Ada programs for testing is
based on the use of a project file (testsuite/gdb.ada/gnat_ada.gpr).
To do that, we pass a number of additional arguments to target_compile,
one of them being the project file (via "-P/path/to/gnat_ada.gpr").
This used to work well-enough, but AdaCore is currently working towards
removing project-file support from gnatmake (the prefered tool for
using project files is gprbuild). So, we need to either switch
the compilation to gprbuild, or stop using project files.

First, using gprbuild is not always what users will be using to
build their applications. So having the option of using gnatmake
provides more flexibility towards exactly reproducing past bugs.
If we ever need a testcase that requires the use of gprbuild, then
I believe support for a new target needs to be added to dejagnu's
target_compile.

Also, the only real reason behind using a project file in the first
place is that we wanted to make it easy to specify the directory
where all compilation artifacts get stored. This is a consequence
of the organization choice we made for gdb.ada to keep each testcase
well organized. It is very easy to achieve that goal without using
project files.

This is therefore what this patch does: It change gdb_compile_ada
to build any program using gnatmake without using a project file
(by temporarily changing the current working directory).

There is a small (beneficial) side-effect; in the situation where
GDB is built in-tree, gnatmake is called as...

        % gnatmake [...] unit.adb

... which means that the debugging info in unit.o will say contain
a filename whose name is 'unit.adb', rather than '/path/to/unit.adb'.
This also better matches what users might typically do. But the side-
effect is that the unit name in the GDB output is not always a full
path. This patch tweaks a couple of testcases to make the path part
optional.

gdb/testsuite:

        * lib/ada.exp (target_compile_ada_from_dir): New function.
        (gdb_compile_ada): Reimplement avoiding the use of project files.
        * gdb.ada/gnat_ada.gpr: Delete.
        * gdb.ada/cond_lang.exp: Adjust test to make path before
        filename optional.
        * gdb.ada/small_reg_param.exp: Likewise.

Tested on x86_64-linux, with both in-tree and out-of-tree builds.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Remove HP-UX reference in foll-vfork.exp
@ 2015-12-22 16:10 sergiodj+buildbot
  2015-12-22 21:43 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-12-22 16:10 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fe33faff35a8ee19db823149e764e3373e603bb9 ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: fe33faff35a8ee19db823149e764e3373e603bb9

Remove HP-UX reference in foll-vfork.exp

One more I just found.

Tested with native, native-gdbserver and native-extended-gdbserver on
Linux.

gdb/testsuite/ChangeLog:

	* gdb.base/foll-vork.exp: Remove HP-UX special case.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Remove dead code in testsuite
@ 2015-12-21 19:50 sergiodj+buildbot
  2015-12-21 20:33 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-12-21 19:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 10125099f09197b325c7e0e7f2af6d3c04f929a6 ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: 10125099f09197b325c7e0e7f2af6d3c04f929a6

Remove dead code in testsuite

This patch removes cases from the testsuite that are not posssibly used.  The
messages "Catch of * not yet implemented" were removed here:

https://www.sourceware.org/ml/gdb-patches/2004-01/msg00679.html

I changed the regexp at the same time to match the string more closely.

gdb/testsuite/ChangeLog:

	* gdb.base/break.exp: Remove dead code.
	* gdb.base/sepdebug.exp: Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [ARM] Enable CRC by default for ARMv8.1 and later.
@ 2015-12-17 21:47 sergiodj+buildbot
  2015-12-19 11:59 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-12-17 21:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 29b1539538f5f285e017adbc64b8d72b45c104a8 ***

Author: Matthew Wahab <matthew.wahab@arm.com>
Branch: master
Commit: 29b1539538f5f285e017adbc64b8d72b45c104a8

[ARM] Enable CRC by default for ARMv8.1 and later.

ARMv8.1 includes CRC as a required extension but the +crc feature isn't
enabled by -march=armv8.1-a as it should be. This patch fixes that.

opcode/include
2015-12-15  Matthew Wahab  <matthew.wahab@arm.com>

	* arm.h (ARM_ARCH_V8_1A): Add the CRC_EXT_ARMV8 co-processor
	feature macro.
	(ARM_ARCH_V8_2A): Likewise.

Change-Id: Id1fe0e6fa51dede19d61e1fd08e68628ea1b1e9e


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Target remote mode fork and exec test updates
@ 2015-12-17 16:37 sergiodj+buildbot
  2015-12-18 20:33 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-12-17 16:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a8f077dc25b1732fb272a7ff10f72b5ca6f67b70 ***

Author: Don Breazeal <donb@codesourcery.com>
Branch: master
Commit: a8f077dc25b1732fb272a7ff10f72b5ca6f67b70

Target remote mode fork and exec test updates

This patch updates tests for fork and exec events in target remote mode.
In the majority of cases this was a simple matter of removing some code
that disabled the test for target remote.  In a few cases the test needed
to be disabled; in those cases the gdb_protocol was checked instead of
using the [is_remote target] etc.

In a couple of cases we needed to use clean_restart, since target remote
doesn't support the run command, and in one case we had to modify an expect
expression to allow for a "multiprocess-style" ptid.

Tested with the patch that implemented target remote mode fork and exec
event support.

gdb/testsuite/ChangeLog:

	* gdb.base/execl-update-breakpoints.exp (main): Enable for target
	remote.
	* gdb.base/foll-exec-mode.exp (main): Disable for target remote.
	* gdb.base/foll-exec.exp (main): Enable for target remote.
	* gdb.base/foll-fork.exp (main): Likewise.
	* gdb.base/foll-vfork.exp (main): Likewise.
	* gdb.base/multi-forks.exp (main): Likewise, and use clean_restart.
	(proc continue_to_exit_bp_loc): Use clean_restart.
	* gdb.base/pie-execl.exp (main): Disable for target remote.
	* gdb.base/watch-vfork.exp (main): Enable for target remote.
	* gdb.mi/mi-nsthrexec.exp (main): Likewise.
	* gdb.threads/execl.exp (main): Likewise.
	* gdb.threads/fork-child-threads.exp (main): Likewise.
	* gdb.threads/fork-plus-threads.exp (main): Disable for target
	remote.
	* gdb.threads/fork-thread-pending.exp (main): Enable for target
	remote.
	* gdb.threads/linux-dp.exp (check_philosopher_stack): Allow
	pid.tid style ptids, instead of just tid.
	* gdb.threads/thread-execl.exp (main): Enable for target remote.
	* gdb.threads/watchpoint-fork.exp (main): Likewise.
	* gdb.trace/report.exp (use_collected_data): Allow pid.tid style
	ptids, instead of just tid.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] gdb: Extend help text for 'list' command.
@ 2015-12-17  9:52 sergiodj+buildbot
  2015-12-18  1:51 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-12-17  9:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4fdd372d502d241eb42032844836ae031830237a ***

Author: Andrew Burgess <andrew.burgess@embecosm.com>
Branch: master
Commit: 4fdd372d502d241eb42032844836ae031830237a

gdb: Extend help text for 'list' command.

Reference the 'listsize' setting in the help text for the 'list' command
to help users find this setting.

gdb/ChangeLog:

	* cli/cli-cmds.c (_initialize_cli_cmds): Extend help text for
	'list' command.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] gdb: Small code restructure for list_command.
@ 2015-12-17  3:20 sergiodj+buildbot
  2015-12-17 20:19 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-12-17  3:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1a48ce76774633e9e27dd245ba275a714b2b339f ***

Author: Andrew Burgess <andrew.burgess@embecosm.com>
Branch: master
Commit: 1a48ce76774633e9e27dd245ba275a714b2b339f

gdb: Small code restructure for list_command.

Move handling of special +/- arguments to the list_command function
inside a single if block, this helps group all related functionality
together.  There should be no user visible changes after this commit.

gdb/ChangeLog:

	* cli/cli-cmds.c (list_command): Move all handling of +/-
	arguments into a single if block.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Remove "spaces" references from gdb.multi/base.exp
@ 2015-12-17  1:05 sergiodj+buildbot
  2015-12-17  5:24 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-12-17  1:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 36d6fc0a3cbda55b9eb07a351c1312e369d4743f ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 36d6fc0a3cbda55b9eb07a351c1312e369d4743f

Remove "spaces" references from gdb.multi/base.exp

I think these references to "spaces" came from the original multi-exec
submission that exposed "symbol spaces" to the user and had a
different UI, and then survived a global find/replace.

gdb/testsuite/ChangeLog:
2015-12-10  Pedro Alves  <palves@redhat.com>

	* gdb.multi/base.exp: Remove stale "spaces" references.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Stop using nowarnings in gdb/testsuite/gdb.multi/
@ 2015-12-17  0:22 sergiodj+buildbot
  2015-12-17  1:26 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-12-17  0:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 762f774785f4ef878ac4c831e1f4733dc957234d ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 762f774785f4ef878ac4c831e1f4733dc957234d

Stop using nowarnings in gdb/testsuite/gdb.multi/

Several of the gdb.multi tests use the "nowarnings" option to suppress
warnings.  The warnings in question all come from missing headers,
like e.g.:

 src/gdb/testsuite/gdb.multi/multi-arch-exec.c:28:3: warning: incompatible implicit declaration of built-in function 'exit' [enabled by default]
    exit (1);
    ^

There's no point in trying to avoid to include standard headers.  In
gdb.base/hangout.c's case, it's even dangerous, as that file calls
printf.  In order to compile a call to a variatic function correctly,
a declaration must be visible.

gdb/testsuite/ChangeLog:
2015-12-10  Pedro Alves  <palves@redhat.com>

	* gdb.multi/base.exp: Don't use nowarnings.
	* gdb.multi/bkpt-multi-exec.exp: Don't use nowarnings.
	* gdb.multi/hangout.c: Include stdio.h.
	* gdb.multi/hello.c: Include stdlib.h.
	* gdb.multi/multi-arch-exec.c: Include stdlib.h.
	* gdb.multi/multi-arch-exec.exp: Don't use nowarnings.
	* gdb.multi/multi-arch.exp: Don't use nowarnings.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Remove support for thread events without PTRACE_EVENT_CLONE in GDB
@ 2015-12-10 16:00 sergiodj+buildbot
  2015-12-10 18:46 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-12-10 16:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c2c2a31fdb228d41ce3db62b268efea04bd39c18 ***

Author: Antoine Tremblay <antoine.tremblay@ericsson.com>
Branch: master
Commit: c2c2a31fdb228d41ce3db62b268efea04bd39c18

Remove support for thread events without PTRACE_EVENT_CLONE in GDB

Before, on systems that did not support PTRACE_EVENT_CLONE, both GDB and
GDBServer coordinated with libthread_db.so to insert breakpoints at magic
locations in libpthread.so, in order to break at thread creation and
thread death.

Support for thread events was removed from GDBServer as patch:
https://sourceware.org/ml/gdb-patches/2015-11/msg00466.html

This patch removes support for thread events in GDB.

No regressions found on Ubuntu 14.04 x86_64.

gdb/ChangeLog:

	* breakpoint.c (remove_thread_event_breakpoints): Remove.
	* breakpoint.h (remove_thread_event_breakpoints): Remove
	declaration.
	* linux-nat.c (in_pid_list_p): Remove.
	(lin_lwp_attach_lwp): Remove.
	* linux-nat.h (lin_lwp_attach_lwp): Remove declaration.
	* linux-thread-db.c (thread_db_use_events): Remove.
	(struct thread_db_info) <td_create_bp_addr>: Remove.
	<td_death_bp_addr>: Likewise.
	<td_ta_event_addr_p>: Likewise.
	<td_ta_set_event_p>: Likewise.
	<td_ta_clear_event_p>: Likewise.
	<td_ta_event_getmsg_p>: Likewise.
	<td_thr_event_enable_p>: Likewise.
	(attach_thread): Likewise.
	(detach_thread): Likewise.
	(have_threads_callback): Likewise.
	(have_threads): Likewise.
	(enable_thread_event): Likewise.
	(enable_thread_event_reporting): Likewise.
	(try_thread_db_load_1): Remove td_ta_event_addr, td_ta_set_event,
	td_ta_clear_event, td_ta_event_getmsg, td_thr_event_enable
	initializations.
	(try_thread_db_load_1): Remove enable_thread_event_reporting call.
	(disable_thread_event_reporting): Remove.
	(record_thread): Adapt to thread_db_use_event removal.
	(detach_thread): Remove.
	(thread_db_detach): Adapt to thread_db_use_event removal.
	(check_event): Remove.
	(thread_db_wait): Adapt to thread events support removal.
	(thread_db_mourn_inferior): Likewise.
	(find_new_threads_callback): Likewise.
	(find_new_threads_once): Likewise.
	(thread_db_update_thread_list): Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix GOT address computations in initial PLT entries for nios2.
@ 2015-12-10  0:31 sergiodj+buildbot
  2015-12-10  2:36 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-12-10  0:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 33d4099fc891760ea1f080746dee4dcfc36c757c ***

Author: Sandra Loosemore <sandra@codesourcery.com>
Branch: master
Commit: 33d4099fc891760ea1f080746dee4dcfc36c757c

Fix GOT address computations in initial PLT entries for nios2.

2015-12-09  Sandra Loosemore  <sandra@codesourcery.com>

	bfd/
	* elf32-nios2.c (nios2_elf32_finish_dynamic_sections): Correct
	%hiadj/%lo computations for _GLOBAL_OFFSET_TABLE_ in initial
	PLT entries.  Assert alignment requirements.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix relaxation in RX linker when --no-keep-memory is specified.
@ 2015-12-07 14:59 sergiodj+buildbot
  2015-12-07 23:56 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-12-07 14:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5ee4a06adea76e607f47eceff65c6bd4a98c49ff ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: 5ee4a06adea76e607f47eceff65c6bd4a98c49ff

Fix relaxation in RX linker when --no-keep-memory is specified.

	* elf32-rx.c (elf32_rx_relax_delete_bytes): Add extra parameter -
	the start of the relocs for the section.  Delete code to load in
	the relocs.
	(elf32_rx_relax_section): Do not free the loaded relocs.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix instruction skipping when using software single step in GDBServer
@ 2015-12-01  4:06 sergiodj+buildbot
  2015-12-01 18:33 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-12-01  4:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2d97cd356e0f0320ecb71cf6a10616ba4618f318 ***

Author: Antoine Tremblay <antoine.tremblay@ericsson.com>
Branch: master
Commit: 2d97cd356e0f0320ecb71cf6a10616ba4618f318

Fix instruction skipping when using software single step in GDBServer

Without this patch, when doing a software single step, with for example
a conditional breakpoint, gdbserver would wrongly avance the pc of
breakpoint_len and skips an instruction.

This is due to gdbserver assuming that it's hardware single stepping.
When it resumes from the breakpoint address it expects the trap to be
caused by ptrace and if it's rather caused by a software breakpoint
it assumes this is a permanent breakpoint and that it needs to skip
over it.

However when software single stepping, this breakpoint is legitimate as
it's the reinsert breakpoint gdbserver has put in place to break at
the next instruction. Thus gdbserver wrongly advances the pc and skips
an instruction.

This patch fixes this behavior so that gdbserver checks if it is a
reinsert breakpoint from software single stepping. If it is it won't
advance the pc. And if there's no reinsert breakpoint there we assume
then that it's a permanent breakpoint and advance the pc.

Here's a commented log of what would happen before and after the fix on
gdbserver :

/* Here there is a conditional breakpoint at 0x10428 that needs to be
stepped over. */

Need step over [LWP 11204]? yes, found breakpoint at 0x10428
...
/* e7f001f0 is a breakpoint instruction on arm
   Here gdbserver writes the software breakpoint we would like to hit
*/
Writing e7f001f0 to 0x0001042c in process 11204
...
Resuming lwp 11220 (continue, signal 0, stop not expected)
  pending reinsert at 0x10428
stop pc is 00010428
  continue from pc 0x10428
...

/* Here gdbserver hit the software breakpoint that was in place
   for the step over */

stop pc is 0001042c
pc is 0x1042c
step-over for LWP 11220.11220 executed software breakpoint
Finished step over.
Could not find fast tracepoint jump at 0x10428 in list (reinserting).

/* Here gdbserver writes back the original instruction */
Writing e50b3008 to 0x0001042c in process 11220
Step-over finished.
Need step over [LWP 11220]? No

/* Here because gdbserver assumes this is a permenant breakpoint it advances
the pc of breakpoint_len, in this case 4 bytes, so we have just skipped
the instruction that was written back here :
Writing e50b3008 to 0x0001042c in process 11220
*/

stop pc is 00010430
pc is 0x10430
Need step over [LWP 11220]? No, no breakpoint found at 0x10430
Proceeding, no step-over needed
proceed_one_lwp: lwp 11220
stop pc is 00010430

This patch fixes this situation and we get the right behavior :

Writing e50b3008 to 0x0001042c in process 11245
Hit a gdbserver breakpoint.
Hit a gdbserver breakpoint.
Step-over finished.
proceeding all threads.
Need step over [LWP 11245]? No
stop pc is 0001042c
pc is 0x1042c
Need step over [LWP 11245]? No, no breakpoint found at 0x1042c
Proceeding, no step-over needed
proceed_one_lwp: lwp 11245
stop pc is 0001042c
pc is 0x1042c
Resuming lwp 11245 (continue, signal 0, stop not expected)
stop pc is 0001042c
  continue from pc 0x1042c

It also works if the value at 0x0001042c is a permanent breakpoint.
If so gdbserver will finish the step over, remove the reinserted breakpoint,
resume at that location and on the next SIGTRAP gdbserver will trigger
the advance PC condition as reinsert_breakpoint_inserted_here will be false.

I also tested this against bp-permanent.exp on arm (with a work in progress
software single step patchset) without any regressions.

It's also tested against x86 bp-permanent.exp without any regression.

So both software and hardware single step are tested.

No regressions on Ubuntu 14.04 on ARMv7 and x86.
With gdbserver-{native,extended} / { -marm -mthumb }

gdb/gdbserver/ChangeLog:

	* linux-low.c (linux_wait_1): Fix pc advance condition.
	* mem-break.c (reinsert_breakpoint_inserted_here): New function.
	* mem-break.h (reinsert_breakpoint_inserted_here): New declaration.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix breakpoint size when stepping over a permanent breakpoint in GDBServer.
@ 2015-11-30 22:15 sergiodj+buildbot
  2015-12-01 17:02 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-11-30 22:15 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 769ef81fec526f3c7513c88e82f98045f8971d14 ***

Author: Antoine Tremblay <antoine.tremblay@ericsson.com>
Branch: master
Commit: 769ef81fec526f3c7513c88e82f98045f8971d14

Fix breakpoint size when stepping over a permanent breakpoint in GDBServer.

When manually stepping over a permanent breakpoint on ARM we need to fetch the
right breakpoint size based on the current instruction set used.

Since this is not encoded in the stop_pc, the instruction mode needs to be
fetched from the CPSR register.

This is done by introducing a new target operation called :
breakpoint_kind_from_current_state.

For other targets that do not need this, breakpoint_kind_from_pc is used.

No regressions, tested on ubuntu 14.04 ARMv7 and x86.
With gdbserver-{native,extended} / { -marm -mthumb }

gdb/gdbserver/ChangeLog:

	* linux-arm-low.c (arm_is_thumb_mode): New function.
	(arm_breakpoint_at): Use arm_is_thumb_mode.
	(arm_breakpoint_kind_from_current_state): New function.
	(struct linux_target_ops) <breakpoint_kind_from_current_state>:
	Initialize.
	* linux-low.c (linux_wait_1): Call breakpoint_kind_from_current_state.
	(linux_breakpoint_kind_from_current_state): New function.
	(struct target_ops <breakpoint_kind_from_current_state>: Initialize.
	* linux-low.h (struct linux_target_ops)
	<breakpoint_kind_from_current_state>: New field.
	* target.h (struct target_ops): Likewise.
	(target_breakpoint_kind_from_current_state): New macro.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] PR other/61321 - demangler crash on casts in template parameters
@ 2015-11-28 17:44 sergiodj+buildbot
  2015-11-29  0:25 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-11-28 17:44 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c4be264168ee2f6c38b6b9b3db0a166441be478b ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: c4be264168ee2f6c38b6b9b3db0a166441be478b

PR other/61321 - demangler crash on casts in template parameters

The fix for bug 59195:

 [C++ demangler handles conversion operator incorrectly]
 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59195

unfortunately makes the demangler crash due to infinite recursion, in
case of casts in template parameters.

For example, with:

 template<int> struct A {};
 template <typename Y> void function_temp(A<sizeof ((Y)(999))>) {}
 template void function_temp<int>(A<sizeof (int)>);

The 'function_temp<int>' instantiation above mangles to:

  _Z13function_tempIiEv1AIXszcvT_Li999EEE

The demangler parses this as:

typed name
  template
    name 'function_temp'
    template argument list
      builtin type int
  function type
    builtin type void
    argument list
      template                          (*)
        name 'A'
        template argument list
          unary operator
            operator sizeof
            unary operator
              cast
                template parameter 0    (**)
              literal
                builtin type int
                name '999'

And after the fix for 59195, due to:

 static void
 d_print_cast (struct d_print_info *dpi, int options,
	       const struct demangle_component *dc)
 {
 ...
   /* For a cast operator, we need the template parameters from
      the enclosing template in scope for processing the type.  */
   if (dpi->current_template != NULL)
     {
       dpt.next = dpi->templates;
       dpi->templates = &dpt;
       dpt.template_decl = dpi->current_template;
     }

when printing the template argument list of A (what should be "<sizeof
(int)>"), the template parameter 0 (that is, "T_", the '**' above) now
refers to the first parameter of the the template argument list of the
'A' template (the '*' above), exactly what we were already trying to
print.  This leads to infinite recursion, and stack exaustion.  The
template parameter 0 should actually refer to the first parameter of
the 'function_temp' template.

Where it reads "for the cast operator" in the comment in d_print_cast
(above), it's really talking about a conversion operator, like:

  struct A { template <typename U> explicit operator U(); };

We don't want to inject the template parameters from the enclosing
template in scope when processing a cast _expression_, only when
handling a conversion operator.

The problem is that DEMANGLE_COMPONENT_CAST is currently ambiguous,
and means _both_ 'conversion operator' and 'cast expression'.

Fix this by adding a new DEMANGLE_COMPONENT_CONVERSION component type,
which does what DEMANGLE_COMPONENT_CAST does today, and making
DEMANGLE_COMPONENT_CAST just simply print its component subtree.

I think we could instead reuse DEMANGLE_COMPONENT_CAST and in
d_print_comp_inner still do:

 @@ -5001,9 +5013,9 @@ d_print_comp_inner (struct d_print_info *dpi, int options,
        d_print_comp (dpi, options, dc->u.s_extended_operator.name);
        return;

     case DEMANGLE_COMPONENT_CAST:
       d_append_string (dpi, "operator ");
 -     d_print_cast (dpi, options, dc);
 +     d_print_conversion (dpi, options, dc);
       return;

leaving the unary cast case below calling d_print_cast, but seems to
me that spliting the component types makes it easier to reason about
the code.

g++'s testsuite actually generates three symbols that crash the
demangler in the same way.  I've added those as tests in the demangler
testsuite as well.

And then this fixes PR other/61233 too, which happens to be a
demangler crash originally reported to GDB, at:
https://sourceware.org/bugzilla/show_bug.cgi?id=16957

Bootstrapped and regtested on x86_64 Fedora 20.

Also ran this through GDB's testsuite.  GDB will require a small
update to use DEMANGLE_COMPONENT_CONVERSION in one place it's using
DEMANGLE_COMPONENT_CAST in its sources.

libiberty/
2015-11-27  Pedro Alves  <palves@redhat.com>

        PR other/61321
        PR other/61233
        * demangle.h (enum demangle_component_type)
        <DEMANGLE_COMPONENT_CONVERSION>: New value.
        * cp-demangle.c (d_demangle_callback, d_make_comp): Handle
        DEMANGLE_COMPONENT_CONVERSION.
        (is_ctor_dtor_or_conversion): Handle DEMANGLE_COMPONENT_CONVERSION
        instead of DEMANGLE_COMPONENT_CAST.
        (d_operator_name): Return a DEMANGLE_COMPONENT_CONVERSION
        component if handling a conversion.
        (d_count_templates_scopes, d_print_comp_inner): Handle
        DEMANGLE_COMPONENT_CONVERSION.
        (d_print_comp_inner): Handle DEMANGLE_COMPONENT_CONVERSION instead
        of DEMANGLE_COMPONENT_CAST.
        (d_print_cast): Rename as ...
        (d_print_conversion): ... this.  Adjust comments.
        (d_print_cast): Rewrite - simply print the left subcomponent.
        * cp-demint.c (cplus_demangle_fill_component): Handle
        DEMANGLE_COMPONENT_CONVERSION.

        * testsuite/demangle-expected: Add tests.

git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@231020 138bc75d-0d04-0410-961f-82ee72b054a4


^ permalink raw reply	[flat|nested] 1181+ messages in thread
[parent not found: <e19616610d7327664f99215a69cb326682742dc3@gdb-build>]
* [binutils-gdb] List inferiors/threads/pspaces in ascending order
@ 2015-11-24 19:08 sergiodj+buildbot
  2015-11-24 22:25 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-11-24 19:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7e0aa6aa9983c745aedc203db0cc360a0ad47cac ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 7e0aa6aa9983c745aedc203db0cc360a0ad47cac

List inferiors/threads/pspaces in ascending order

Before:
  (gdb) info threads
    Id   Target Id         Frame
    3    Thread 0x7ffff77c3700 (LWP 29035) callme () at foo.c:30
    2    Thread 0x7ffff7fc4700 (LWP 29034) 0x000000000040087b in child_function_2 (arg=0x0) at foo.c:60
  * 1    Thread 0x7ffff7fc5740 (LWP 29030) 0x0000003b37209237 in pthread_join (threadid=140737353893632, thread_return=0x0) at pthread_join.c:92

After:
  (gdb) info threads
    Id   Target Id         Frame
  * 1    Thread 0x7ffff7fc5740 (LWP 29030) 0x0000003b37209237 in pthread_join (threadid=140737353893632, thread_return=0x0) at pthread_join.c:92
    2    Thread 0x7ffff7fc4700 (LWP 29034) 0x000000000040087b in child_function_2 (arg=0x0) at foo.c:60
    3    Thread 0x7ffff77c3700 (LWP 29035) callme () at foo.c:30

gdb/doc/ChangeLog:
2015-11-24  Pedro Alves  <palves@redhat.com>

	PR 17539
	* gdb.texinfo (Inferiors and Programs): Adjust "maint info
	program-spaces" example to ascending order listing.
	(Threads): Adjust "info threads" example to ascending order
	listing.
	(Forks): Adjust "info inferiors" example to ascending order
	listing.

gdb/ChangeLog:
2015-11-24  Pedro Alves  <palves@redhat.com>

	PR 17539
	* inferior.c (add_inferior_silent): Append the new inferior to the
	end of the list.
	* progspace.c (add_program_space): Append the new pspace to the
	end of the list.
	* thread.c (new_thread): Append the new thread to the end of the
	list.

gdb/testsuite/ChangeLog:
2015-11-24  Pedro Alves  <palves@redhat.com>

	PR 17539
	* gdb.base/foll-exec-mode.exp: Adjust to GDB listing inferiors and
	threads in ascending order.
	* gdb.base/foll-fork.exp: Likewise.
	* gdb.base/foll-vfork.exp: Likewise.
	* gdb.base/multi-forks.exp: Likewise.
	* gdb.mi/mi-nonstop.exp: Likewise.
	* gdb.mi/mi-nsintrall.exp: Likewise.
	* gdb.multi/base.exp: Likewise.
	* gdb.multi/multi-arch.exp: Likewise.
	* gdb.python/py-inferior.exp: Likewise.
	* gdb.threads/break-while-running.exp: Likewise.
	* gdb.threads/execl.exp: Likewise.
	* gdb.threads/gcore-thread.exp: Likewise.
	* gdb.threads/info-threads-cur-sal.exp: Likewise.
	* gdb.threads/kill.exp: Likewise.
	* gdb.threads/linux-dp.exp: Likewise.
	* gdb.threads/multiple-step-overs.exp: Likewise.
	* gdb.threads/next-bp-other-thread.exp: Likewise.
	* gdb.threads/step-bg-decr-pc-switch-thread.exp: Likewise.
	* gdb.threads/step-over-lands-on-breakpoint.exp: Likewise.
	* gdb.threads/step-over-trips-on-watchpoint.exp: Likewise.
	* gdb.threads/thread-find.exp: Likewise.
	* gdb.threads/tls.exp: Likewise.
	* lib/mi-support.exp (mi_reverse_list): Delete.
	(mi_check_thread_states): No longer reverse list.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] binutils: add support for arm-*-darwin and aarch64-*-darwin.
@ 2015-11-20 14:07 sergiodj+buildbot
  2015-11-21  0:34 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-11-20 14:07 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f075eb5e6b0dd850304f78cf4d5c94df7b44c7a3 ***

Author: Tristan Gingold <gingold@adacore.com>
Branch: master
Commit: f075eb5e6b0dd850304f78cf4d5c94df7b44c7a3

binutils: add support for arm-*-darwin and aarch64-*-darwin.

Currently only in bfd and binutils.

ChangeLog/
	* configure.ac: Add aarch64-*-darwin* and arm-*-darwin*.
	* configure: Regenerate.

bfd/ChangeLog/
	* targets.c (aarch64_mach_o_vec, arm_mach_o_vec): Declare.
	(_bfd_target_vector): Add new vectors.
	* reloc.c (BFD_RELOC_MACH_O_SUBTRACTOR32)
	(BFD_RELOC_MACH_O_SUBTRACTOR64, BFD_RELOC_MACH_O_ARM64_ADDEND)
	(BFD_RELOC_MACH_O_ARM64_GOT_LOAD_PAGE21)
	(BFD_RELOC_MACH_O_ARM64_GOT_LOAD_PAGEOFF12)
	(BFD_RELOC_MACH_O_ARM64_POINTER_TO_GOT): New relocations.
	(BFD_RELOC_MACH_O_X86_64_SUBTRACTOR32)
	(BFD_RELOC_MACH_O_X86_64_SUBTRACTOR64): Remove.
	* mach-o-x86-64.c (bfd_mach_o_x86_64_swap_reloc_out): Change
	name of subtractor relocations.
	* config.bfd: Handle aarch64-*-darwin*, arm-*-darwin*.
	* Makefile.am (BFD32_BACKENDS): Add mach-o-arm.lo.
	(BFD32_BACKENDS_CFILES): Add mach-o-arm.c.
	(BFD64_BACKENDS): Add mach-o-aarch64.lo.
	(BFD64_BACKENDS_CFILES): Add mach-o-aarch64.c.
	* configure.ac: Handle aarch64_mach_o_vec and arm_mach_o_vec.
	* mach-o-aarch64.c: New file.
	* mach-o-arm.c: New file.
	* Makefile.in: Regenerate.
	* bfd-in2.h: Regenerate.
	* configure: Regenerate.
	* libbfd.h: Regenerate.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Synchronize PDP11 page size between BFD and LD.
@ 2015-11-20 13:08 sergiodj+buildbot
  2015-11-21  0:19 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-11-20 13:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 11b8aeb88174dd67ff8b7c58377e8ef94ccf274e ***

Author: David Bridgham <dab@froghouse.org>
Branch: master
Commit: 11b8aeb88174dd67ff8b7c58377e8ef94ccf274e

Synchronize PDP11 page size between BFD and LD.

	* pdp11.c (TARGET_PAGE_SIZE): Set to 256 to match definition in
	ld/emulparams/pdp11.sh.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
[parent not found: <bb82e93484cdd56c67efd52b869a6123b2623f6c@gdb-build>]
* [binutils-gdb] gdb: Workaround bad gdbserver qSupported:xmlRegisters=i386; UnknwnFeat+ handling
@ 2015-11-19 18:47 sergiodj+buildbot
  2015-11-20 15:38 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-11-19 18:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b35d5edb03798388d503d922d8f909a133bf93dd ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: b35d5edb03798388d503d922d8f909a133bf93dd

gdb: Workaround bad gdbserver qSupported:xmlRegisters=i386;UnknwnFeat+ handling

gdbserver's target_process_qsupported is called for each feature that
the gdbserver common code does not recognize.  The only current
implementation, for x86 Linux, does this:

  static void
  x86_linux_process_qsupported (const char *query)
  {
    /* Return if gdb doesn't support XML.  If gdb sends "xmlRegisters="
       with "i386" in qSupported query, it supports x86 XML target
       descriptions.  */
    use_xml = 0;
    if (query != NULL && startswith (query, "xmlRegisters="))
      {
	char *copy = xstrdup (query + 13);
	char *p;

	for (p = strtok (copy, ","); p != NULL; p = strtok (NULL, ","))
	  {
	    if (strcmp (p, "i386") == 0)
	      {
		use_xml = 1;
		break;
	      }
	  }

	free (copy);
      }

    x86_linux_update_xmltarget ();
  }

Notice that this clears use_xml and calls x86_linux_update_xmltarget
each time target_process_qsupported is called.  So if gdb sends in any
unknown feature after "xmlRegisters=i386", like e.g.,
"xmlRegisters=i386;UnknownFeature+" gdbserver ends up not reporting a
XML description...

Work around this by having GDB send the "xmlRegisters=" feature last.

gdb/ChangeLog:
2015-11-19  Pedro Alves  <palves@redhat.com>

	* remote.c (remote_query_supported): Send the "xmlRegisters="
	feature last.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix out of boundary access in pass_in_v
@ 2015-11-18 12:02 sergiodj+buildbot
  2015-11-18 12:30 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-11-18 12:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0735fdddbc086291f6d2357e8fa57e5df6095e89 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 0735fdddbc086291f6d2357e8fa57e5df6095e89

Fix out of boundary access in pass_in_v

Hi,
I build GDB with -fsanitize=address, and run testsuite.  In
gdb.base/callfuncs.exp, I see the following error,

p t_float_values(0.0,0.0)
=================================================================
==8088==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x6020000cb650 at pc 0x6e195c bp 0x7fff164f9770 sp 0x7fff164f9768
READ of size 16 at 0x6020000cb650 thread T0^
    #0 0x6e195b in regcache_raw_write /home/yao/SourceCode/gnu/gdb/git/gdb/regcache.c:912
    #1 0x6e1e52 in regcache_cooked_write /home/yao/SourceCode/gnu/gdb/git/gdb/regcache.c:945
    #2 0x466d69 in pass_in_v /home/yao/SourceCode/gnu/gdb/git/gdb/aarch64-tdep.c:1101
    #3 0x467512 in pass_in_v_or_stack /home/yao/SourceCode/gnu/gdb/git/gdb/aarch64-tdep.c:1196
    #4 0x467d7d in aarch64_push_dummy_call /home/yao/SourceCode/gnu/gdb/git/gdb/aarch64-tdep.c:1335

The code in pass_in_v read contents from V registers (128 bit), but the
data passed through V registers can be less than 128 bit.  In this case,
float is passed.  So writing V registers contents into contents buff
will cause overflow.  In this patch, we add an array reg[V_REGISTER_SIZE],
which is to hold the contents from V registers, and then copy useful
bits to buf.

gdb:

2015-11-18  Yao Qi  <yao.qi@linaro.org>

	* aarch64-tdep.c (pass_in_v): Add argument len.  Add local array
	reg.  Callers updated.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Prevent looping in archives
@ 2015-11-18 11:52 sergiodj+buildbot
  2015-11-18 12:14 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-11-18 11:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4978e369fb75a8b7756bf4201668b2a9d9556286 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 4978e369fb75a8b7756bf4201668b2a9d9556286

Prevent looping in archives

	PR 19256
	* archive.c (bfd_generic_openr_next_archived_file): Don't allow
	backward file movement via "negative" sizes.
	* coff-alpha.c (alpha_ecoff_openr_next_archived_file): Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] mach-o cleanup: remove useless calls to bfd_seek.
@ 2015-11-18 11:42 sergiodj+buildbot
  2015-11-18 11:52 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-11-18 11:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 47daa70fe08c57aaafa6fe1a7e762072909d0f8f ***

Author: Tristan Gingold <gingold@adacore.com>
Branch: master
Commit: 47daa70fe08c57aaafa6fe1a7e762072909d0f8f

mach-o cleanup: remove useless calls to bfd_seek.

Also support new commands.

bfd/
	* mach-o.h (struct mach_o_data_struct): Add hdr_offset field.
	(bfd_mach_o_fat_archive_p): Renames prototype.
	(bfd_mach_o_fat_openr_next_archived_file): Renames.
	(bfd_mach_o_header_p): Add argument.
	* mach-o.c (bfd_mach_o_read_header): Add hdr_off argument and
	use it.
	(bfd_mach_o_read_section_32, bfd_mach_o_read_section_64)
	(bfd_mach_o_read_section): Remove offset argument.
	(bfd_mach_o_read_dylinker): Remove bfd_seek call.
	(bfd_mach_o_read_dylib, bfd_mach_o_read_prebound_dylib)
	(bfd_mach_o_read_prebind_cksum, bfd_mach_o_read_twolevel_hints)
	(bfd_mach_o_read_fvmlib, bfd_mach_o_read_dysymtab)
	(bfd_mach_o_read_symtab, bfd_mach_o_read_uuid)
	(bfd_mach_o_read_linkedit, bfd_mach_o_read_str)
	(bfd_mach_o_read_dyld_info, bfd_mach_o_read_version_min)
	(bfd_mach_o_read_encryption_info): Likewise.
	(bfd_mach_o_read_encryption_info_64): New function.
	(bfd_mach_o_read_main, bfd_mach_o_read_source_version)
	(bfd_mach_o_read_segment): Remove call to bfd_seek.
	(bfd_mach_o_read_command): Use hdr_offset in bfd_seek.
	Handle BFD_MACH_O_LC_LINKER_OPTIMIZATION_HINT,
	BFD_MACH_O_LC_ENCRYPTION_INFO_64, BFD_MACH_O_LC_VERSION_MIN_WATCHOS.
	(bfd_mach_o_header_p): Add hdr_off argument.
	(bfd_mach_o_gen_object_p, bfd_mach_o_gen_core_p): Adjust calls.
	(bfd_mach_o_fat_archive_p): Renames.
	(bfd_mach_o_fat_openr_next_archived_file): Renames.
	(bfd_mach_o_close_and_cleanup): Remove useless code.
	(bfd_mach_o_close_and_cleanup): Define.
	* mach-o-x86-64.c (bfd_mach_o_x86_64_object_p)
	(bfd_mach_o_x86_64_core_p): Adjust calls.
	* mach-o-target.c: Move defines for archive from mach-o.c.
	Remove check on TARGET_ARCHIVE.
	* mach-o-i386.c (bfd_mach_o_i386_object_p)
	(bfd_mach_o_i386_core_p): Adjust calls.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] sim: mn10300/v850: drop unused WITH_CORE define
@ 2015-11-18  4:25 sergiodj+buildbot
  2015-11-18 10:08 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-11-18  4:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c389945b7a470aa328972026fe4a836c57ccb7ae ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: c389945b7a470aa328972026fe4a836c57ccb7ae

sim: mn10300/v850: drop unused WITH_CORE define

This was dropped from the sim core in 1997, so no point in having these
sim ports continue to define it.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] sim: always enable modulo memory
@ 2015-11-18  4:18 sergiodj+buildbot
  2015-11-18  9:54 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-11-18  4:18 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cdf850e9d953f765f600e1ecae61664eab5ae7f1 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: cdf850e9d953f765f600e1ecae61664eab5ae7f1

sim: always enable modulo memory

Having this be a config option doesn't make sense: the code size is
pretty much the same (as all the logic is still active), and if it's
disabled, the sim throws an error if you try to use it.  That means
we can't break sims that weren't using it before by enabling it all
the time.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [sim/ppc] Fix printf_filtered reference
@ 2015-11-17 21:29 sergiodj+buildbot
  2015-11-18  9:38 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-11-17 21:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a6760b615451518704601cae9327d333fe4bec57 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: a6760b615451518704601cae9327d333fe4bec57

[sim/ppc] Fix printf_filtered reference

Building a gdb that includes the PPC sim in C++ mode fails to link with:

(...)s.o compile-object-load.o compile-object-run.o compile-loc2c.o compile-c-support.o inflow.o    init.o \
          ../sim/ppc/libsim.a ../readline/libreadline.a ../opcodes/libopcodes.a ../bfd/libbfd.a -lz  ../libiberty/libiberty.a ../libdecnumber/libdecnumber.a    -ldl -ldl -lncurses -lm -ldl  -lguile-2.0 -lgc  -lpthread -ldl -lutil -lm -lpython2.7 -Xlinker -export-dynamic -lexpat -llzma -lbabeltrace -lbabeltrace-ctf  ../libiberty/libiberty.a  build-gnulib/import/libgnu.a
../sim/ppc/libsim.a(sim_calls.o): In function `sim_open':
/home/pedro/gdb/mygit/cxx-convertion/src/sim/ppc/sim_calls.c:73: undefined reference to `printf_filtered'
/home/pedro/gdb/mygit/cxx-convertion/src/sim/ppc/sim_calls.c:73: undefined reference to `printf_filtered'
../sim/ppc/libsim.a(sim_calls.o): In function `sim_close':
/home/pedro/gdb/mygit/cxx-convertion/src/sim/ppc/sim_calls.c:93: undefined reference to `printf_filtered'
/home/pedro/gdb/mygit/cxx-convertion/src/sim/ppc/sim_calls.c:93: undefined reference to `printf_filtered'
../sim/ppc/libsim.a(sim_calls.o): In function `sim_load':
/home/pedro/gdb/mygit/cxx-convertion/src/sim/ppc/sim_calls.c:102: undefined reference to `printf_filtered'
../sim/ppc/libsim.a(sim_calls.o):/home/pedro/gdb/mygit/cxx-convertion/src/sim/ppc/sim_calls.c:102: more undefined references to `printf_filtered' follow
collect2: error: ld returned 1 exit status

The undefined references come from TRACE macro calls, which expand to
calls to printf_filtered.

But note that the sim's 'printf_filtered' is actually a #define to
'sim_io_printf_filtered', in sim_callbacks.h :

 #define printf_filtered sim_io_printf_filtered

AFAICS, this is not meant to call gdb's printf_filtered function.  The
ChangeLog entry that added the printf_filtered macro reads:

 Tue Jul 30 21:12:24 1996  Andrew Cagney  <cagney@kremvax.highland.com.au>

	 * sim_callbacks.h (sim_io_printf_filtered): Replace
	 printf_filtered with a local simulator specific version.  Add
	 #define printf_filtered to simplify updating of existing code.

That is, just another incomplete/partial transition.  Maybe prior to
1996 this was really meant to call gdb's printf_filtered version.

The reference to printf_filtered appears because sim_calls.c, the
compilation unit that fails to link, has this at the top:

 #undef printf_filtered /* blow away the mapping */

presumably so that this further below:

 void
 sim_io_printf_filtered(const char *fmt,
			...)
 {
   (...)
   callbacks->printf_filtered(callbacks, "%s", message);
 }

works.  So those TRACE macros instances in sim_calls.c just happen to
work because gdb is linked in, which satisfies the 'printf_filtered'
reference, when GDB is built in C mode.  When built in C++ mode, the
problem is exposed, as GDB's printf_filtered is mangled.

The fix here is to make the TRACE macro call sim_io_printf_filtered
directly.

(Standalone "run" doesn't fail to link simply because the offending
routines are not part of its link.)

sim/ppc/ChangeLog
2015-11-17  Pedro Alves  <palves@redhat.com>

	* debug.h (TRACE, ITRACE, DTRACE, DITRACE, PTRACE): Call
	sim_io_printf_filtered instead of printf_filtered.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix gdb.threads/multiple-step-overs.exp fails on arm
@ 2015-11-17 17:26 sergiodj+buildbot
  2015-11-18  9:20 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-11-17 17:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1946c4ccca04e374acc040fc30c8b44d2c9ca0a8 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 1946c4ccca04e374acc040fc30c8b44d2c9ca0a8

Fix gdb.threads/multiple-step-overs.exp fails on arm

Hi,
Some tests in gdb.threads/multiple-step-overs.exp fail on arm target
when the displaced stepping on, but they pass when displaced stepping
is off.

 FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: step: step
 FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: next: next
 FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: continue: continue
 FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: signal thr1: continue to sigusr1_handler

when displaced stepping is on,

Sending packet: $vCont;c#a8...infrun: infrun_async(1)^M <--- [1]
infrun: prepare_to_wait^M
infrun: target_wait (-1.0.0, status) =^M
infrun:   -1.0.0 [Thread 0],^M
infrun:   status->kind = ignore^M
infrun: TARGET_WAITKIND_IGNORE^M
infrun: prepare_to_wait^M
Packet received: T05swbreak:;0b:f8faffbe;0d:409ee7b6;0f:d0880000;thread:p635.636;core:0;^M
infrun: target_wait (-1.0.0, status) =^M
infrun:   1589.1590.0 [Thread 1590],^M
infrun:   status->kind = stopped, signal = GDB_SIGNAL_TRAP^M
infrun: TARGET_WAITKIND_STOPPED^M
infrun: stop_pc = 0x88d0^M
infrun: context switch^M
infrun: Switching context from Thread 1591 to Thread 1590^

GDB resumes the whole process (all threads) rather than the specific
thread for which GDB wants to step over the breakpoint (as shown in [1]).
That is wrong because we resume a single thread and leave others stopped
when doing a normal step over where we temporarily remove the breakpoint,
single-step, reinsert the breakpoint, is that if we let other threads run
in the period while the breakpoint is removed, then these other threads
could miss the breakpoint.  Since with displaced stepping, we don't ever
remove the breakpoint, it should be fine to let other threads run.  However,
there's another reason that we should not let other threads run: that is
the case where some of those threads are also stopped for a breakpoint that
itself needs to be stepped over.  If we just let those threads run, then
they immediately re-trap their breakpoint again.

when displaced stepping is off, GDB behaves correctly, only resumes
the specific thread (as shown in [2]).

Sending packet: $vCont;c:p611.613#b2...infrun: infrun_async(1)^M <-- [2]
infrun: prepare_to_wait^M
infrun: target_wait (-1.0.0, status) =^M
infrun:   -1.0.0 [Thread 0],^M
infrun:   status->kind = ignore^M
infrun: TARGET_WAITKIND_IGNORE^M
infrun: prepare_to_wait^M
Packet received: T05swbreak:;0b:f8faffbe;0d:409e67b6;0f:48880000;thread:p611.613;core:1;^M
infrun: target_wait (-1.0.0, status) =^M
infrun:   1553.1555.0 [Thread 1555],^M
infrun:   status->kind = stopped, signal = GDB_SIGNAL_TRAP^M
infrun: TARGET_WAITKIND_STOPPED^M
infrun: clear_step_over_info^M
infrun: stop_pc = 0x8848

The current logic in GDB on deciding the set of threads to resume is:

  /* Decide the set of threads to ask the target to resume.  */
  if ((step || thread_has_single_step_breakpoints_set (tp))
      && tp->control.trap_expected)
    {
      /* We're allowing a thread to run past a breakpoint it has
	 hit, by single-stepping the thread with the breakpoint
	 removed.  In which case, we need to single-step only this
	 thread, and keep others stopped, as they can miss this
	 breakpoint if allowed to run.  */
      resume_ptid = inferior_ptid;
    }
  else
    resume_ptid = internal_resume_ptid (user_step);

it doesn't handle the case correctly that GDB continue (instead of
single step) the thread for displaced stepping.

I also update the comment below to reflect the code.  I remove the
"with the breakpoint removed" comment, because GDB doesn't remove
breakpoints in displaced stepping, so we don't have to worry that
other threads may miss the breakpoint.

Patch is regression tested on both x86_64-linux and arm-linux.

gdb:

2015-11-17  Yao Qi  <yao.qi@linaro.org>

	* infrun.c (resume): Check control.trap_expected only
	when deciding the set of threads to resume.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Introduce null_block_symbol
@ 2015-11-17 17:18 sergiodj+buildbot
  2015-11-18  9:00 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-11-17 17:18 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b6b806729dd5c4c46981d59f351460b4d7989548 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: b6b806729dd5c4c46981d59f351460b4d7989548

Introduce null_block_symbol

... in the spirit of null_ptid, null_frame_id, etc.

Fixes two instances of:

  /root/binutils-gdb/gdb/cp-namespace.c: In function 'block_symbol cp_lookup_nested_symbol(type*, const char*, const block*, domain_enum)':
  /root/binutils-gdb/gdb/cp-namespace.c:1010: warning: jump to case label
  /root/binutils-gdb/gdb/cp-namespace.c:1008: error:   crosses initialization of 'block_symbol <anonymous>'

Compiler info:

  Reading specs from /usr/lib/gcc-lib/amd64-unknown-openbsd5.8/4.2.1/specs
  Target: amd64-unknown-openbsd5.8
  Configured with: OpenBSD/amd64 system compiler
  Thread model: posix
  gcc version 4.2.1 20070719

gdb/ChangeLog:
2015-11-17  Pedro Alves  <palves@redhat.com>

	* cp-namespace.c (cp_lookup_bare_symbol)
	(cp_search_static_and_baseclasses, cp_lookup_symbol_via_imports)
	(cp_lookup_symbol_via_all_imports, cp_lookup_nested_symbol_1)
	(cp_lookup_nested_symbol): Use null_block_symbol.
	* d-namespace.c (d_lookup_symbol, d_lookup_nested_symbol)
	(d_lookup_symbol_imports, d_lookup_symbol_module): Use
	null_block_symbol.
	* symtab.c (null_block_symbol): New global.
	* symtab.h (null_block_symbol): Declare.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [C++] Always use setjmp/longjmp for exceptions
@ 2015-11-17 17:09 sergiodj+buildbot
  2015-11-18  8:42 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-11-17 17:09 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT eec461d0a8e7ae14c7fe8f0196ab8d0e30285d83 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: eec461d0a8e7ae14c7fe8f0196ab8d0e30285d83

[C++] Always use setjmp/longjmp for exceptions

We currently throw exceptions from signal handlers (e.g., for
Quit/ctrl-c).  But throwing C++ exceptions from signal handlers is
undefined.  (That doesn't restore signal masks, like siglongjmp does,
and, because asynchronous signals can arrive at any instruction, we'd
have to build _everything_ with -fasync-unwind-tables to make it
reliable.)  It happens to work on x86_64 GNU/Linux at least, but it's
likely broken on other ports.

Until we stop throwing from signal handlers, use setjmp/longjmp based
exceptions in C++ mode as well.

gdb/ChangeLog:
2015-11-17  Pedro Alves  <palves@redhat.com>

	* common/common-exceptions.h (GDB_XCPT_SJMP, GDB_XCPT_TRY)
	(GDB_XCPT_RAW_TRY, GDB_XCPT): Define.
	Replace __cplusplus checks with GDB_XCPT checks throughout.
	* common/common-exceptions.c: Replace __cplusplus checks with
	GDB_XCPT checks throughout.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] MinGW and attribute format(printf/gnu_printf)
@ 2015-11-17 17:01 sergiodj+buildbot
  2015-11-18  8:26 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-11-17 17:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 91ee7171d0886731900ab0238ce3795241d877a4 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 91ee7171d0886731900ab0238ce3795241d877a4

MinGW and attribute format(printf/gnu_printf)

Cross building gdbserver for --host=x86_64-w64-mingw32 with gcc 4.8.4
20141219 (Fedora MinGW 4.8.4-1.fc20), I get:

  src/gdb/gdbserver/tracepoint.c: In function 'cmd_qtdp':
  src/gdb/gdbserver/tracepoint.c:2577:7: error: unknown conversion type character 'l' in format [-Werror=format=]
	 trace_debug ("Defined %stracepoint %d at 0x%s, "
	 ^
  src/gdb/gdbserver/tracepoint.c:2577:7: error: unknown conversion type character 'l' in format [-Werror=format=]
  src/gdb/gdbserver/tracepoint.c:2577:7: error: too many arguments for format [-Werror=format-extra-args]
  src/gdb/gdbserver/tracepoint.c: In function 'stop_tracing':
  src/gdb/gdbserver/tracepoint.c:3447:7: error: unknown conversion type character 'l' in format [-Werror=format=]
	 trace_debug ("Stopping the trace because "
	 ^
  src/gdb/gdbserver/tracepoint.c:3447:7: error: too many arguments for format [-Werror=format-extra-args]
  src/gdb/gdbserver/tracepoint.c: In function 'collect_data_at_tracepoint':
  src/gdb/gdbserver/tracepoint.c:4651:3: error: unknown conversion type character 'l' in format [-Werror=format=]
     trace_debug ("Making new traceframe for tracepoint %d at 0x%s, hit %" PRIu64,
     ^
  src/gdb/gdbserver/tracepoint.c:4651:3: error: too many arguments for format [-Werror=format-extra-args]
  src/gdb/gdbserver/tracepoint.c: In function 'collect_data_at_step':
  src/gdb/gdbserver/tracepoint.c:4687:3: error: unknown conversion type character 'l' in format [-Werror=format=]
     trace_debug ("Making new step traceframe for "
     ^

trace_debug is a macro that calls:

  static void trace_vdebug (const char *, ...) ATTRIBUTE_PRINTF (1, 2);

The calls that fail checking use PRIu64, etc., like:

      trace_debug ("Defined %stracepoint %d at 0x%s, "
		   "enabled %d step %" PRIu64 " pass %" PRIu64,
		   tpoint->type == fast_tracepoint ? "fast "
		   : tpoint->type == static_tracepoint ? "static " : "",
		   tpoint->number, paddress (tpoint->address), tpoint->enabled,
		   tpoint->step_count, tpoint->pass_count);

gnulib's stdio/printf module replacements may make %llu, etc. work on
mingw, instead of the MS-specific %I64u, and thus may make PRIu64
expand to %llu.  However, gcc isn't aware of that, because libiberty's
ansidecl.h defines ATTRIBUTE_PRINTF as using attribute format(printf).
But, with that format, gcc checks for MS-style format strings (%I64u).
In order to have gcc expect gnu/standard formats, we need to use
gnu_printf format instead.  Which version to use (printf/gnu_printf)
depends on msvcrt and mingw version, and so gnulib has a
configure-time check, and defines _GL_ATTRIBUTE_FORMAT_PRINTF
accordingly.

Since _GL_ATTRIBUTE_FORMAT_PRINTF is compatible with ATTRIBUTE_PRINTF,
the fix is simply to make use of the former.

gdb/ChangeLog:
2015-11-17  Pedro Alves  <palves@redhat.com>

	* common/common-defs.h (ATTRIBUTE_PRINTF): Redefine in terms of
	_GL_ATTRIBUTE_FORMAT_PRINTF after including ansidecl.h.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [C++/mingw] handle_output_debug_string
@ 2015-11-17 16:22 sergiodj+buildbot
  2015-11-18  3:01 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-11-17 16:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c08790597c54c015ecfcd7ea56ebe30fa1d9e946 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: c08790597c54c015ecfcd7ea56ebe30fa1d9e946

[C++/mingw] handle_output_debug_string

Fixes:

 ../../../src/gdb/gdbserver/win32-low.c: In function 'int win32_kill(int)':
 ../../../src/gdb/gdbserver/win32-low.c:823:46: error: invalid conversion from 'int' to 'target_waitkind' [-fpermissive]
     struct target_waitstatus our_status = { 0 };
					       ^

handle_output_debug_string doesn't use the parameter for anything
(it's an output parameter in the gdb version), so just remove it.

gdb/gdbserver/ChangeLog:
2015-11-17  Pedro Alves  <palves@redhat.com>

	* win32-low.c (handle_output_debug_string): Remove parameter.
	(win32_kill): Remove our_status local and adjust call to
	handle_output_debug_string.
	(get_child_debug_event): Adjust call to
	handle_output_debug_string.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix the disassembly of conditional instructions will illegal condition selections.
@ 2015-11-17 11:47 sergiodj+buildbot
  2015-11-17 12:57 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-11-17 11:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e7286c5668bcc5de0bfe523ac7b7cddabeffebe5 ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: e7286c5668bcc5de0bfe523ac7b7cddabeffebe5

Fix the disassembly of conditional instructions will illegal condition selections.

	* rx-dis.c (condition_names): Replace always and never with
	invalid, since the always/never conditions can never be legal.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] sim: testsuite: support basic vars in flags
@ 2015-11-15  6:14 sergiodj+buildbot
  2015-11-15 19:31 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-11-15  6:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9bea4d16a6f009585841c1134a024d10a61b8d56 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 9bea4d16a6f009585841c1134a024d10a61b8d56

sim: testsuite: support basic vars in flags

Sometimes in tests, we need supplemental files like linker scripts or
board helper files.  There's no way to set those flags in the tests
currently and relative paths don't work (breaks out of tree builds).

Update the main option parser to replace some strings on the fly.  Now
tests can do things like:

Long term we'll want to switch the framework to use the dejagnu helpers
like dg-xxx that gcc & gdb utilize.  But that'll require more rework.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Bump version to 2.26.51
@ 2015-11-15  0:35 sergiodj+buildbot
  2015-11-15 12:40 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-11-15  0:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d8bd95efd8119e06e6753c841f1bbc54bb09d5de ***

Author: Tristan Gingold <gingold@adacore.com>
Branch: master
Commit: d8bd95efd8119e06e6753c841f1bbc54bb09d5de

Bump version to 2.26.51

bfd/
2015-11-13  Tristan Gingold  <gingold@adacore.com>

	* version.m4: Bump version to 2.26.51
	* configure: Regenerate.

binutils/
2015-11-13  Tristan Gingold  <gingold@adacore.com>

	* configure: Regenerate.

gas/
2015-11-13  Tristan Gingold  <gingold@adacore.com>

	* configure: Regenerate.

gprof/
2015-11-13  Tristan Gingold  <gingold@adacore.com>

	* configure: Regenerate.

ld/
2015-11-13  Tristan Gingold  <gingold@adacore.com>

	* configure: Regenerate.

opcodes/
2015-11-13  Tristan Gingold  <gingold@adacore.com>

	* configure: Regenerate.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] sim: m32c: move test code to testsuite
@ 2015-11-10  5:32 sergiodj+buildbot
  2015-11-10  8:15 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-11-10  5:32 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1057567ea711d80f9937653179b06507827d5819 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 1057567ea711d80f9937653179b06507827d5819

sim: m32c: move test code to testsuite

Various target code belongs in the testsuite/ subdir, so move the m32c
code to match all the other targets.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Copy gnulib obstack files
@ 2015-11-09  5:01 sergiodj+buildbot
  2015-11-09  5:45 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-11-09  5:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 314dee8ea9be79a450d9f0b451619b67ebe0e017 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 314dee8ea9be79a450d9f0b451619b67ebe0e017

Copy gnulib obstack files

This copies obstack.[ch] from gnulib, and updates the docs.  The next
patch should be applied if someone repeats the import at a later date.

include/
	PR gdb/17133
	* obstack.h: Import current gnulib file.
libiberty/
	PR gdb/17133
	* obstack.c: Import current gnulib file.
	* obstacks.texi: Updated doc, from glibc's manual/memory.texi.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Use aarch64_decode_insn in aarch64_analyze_prologue
@ 2015-11-05  9:59 sergiodj+buildbot
  2015-11-05 14:09 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-11-05  9:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d9ebcbce29f3621a687872270cc8952ba1501e56 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: d9ebcbce29f3621a687872270cc8952ba1501e56

Use aarch64_decode_insn in aarch64_analyze_prologue

This patch convert aarch64_analyze_prologue to using aarch64_decode_insn
to decode instructions.  After this change, aarch64_analyze_prologue
looks much simple, and some aarch64_decode_* functions are removed
accordingly.

gdb:

2015-11-05  Yao Qi  <yao.qi@linaro.org>

	* aarch64-tdep.c (extract_signed_bitfield): Remove.
	(decode_masked_match): Remove.
	(aarch64_decode_add_sub_imm): Remove.
	(aarch64_decode_br): Remove.
	(aarch64_decode_eret): Remove.
	(aarch64_decode_movz): Remove.
	(aarch64_decode_orr_shifted_register_x): Remove.
	(aarch64_decode_ret): Remove.
	(aarch64_decode_stp_offset): Remove.
	(aarch64_decode_stur): Remove.
	(aarch64_analyze_prologue): Call aarch64_decode_insn
	and use aarch64_inst to decode instructions.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
[parent not found: <10268a4c0d64b3892397aeaafbc4b91f6a1e0dc8@gdb-build>]
* [binutils-gdb] gnu-v2-abi.c: Add casts
@ 2015-10-29 17:35 sergiodj+buildbot
  2015-10-30  5:01 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-10-29 17:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ebf05345dadb3fcb232cb788a9126e563f6bb767 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: ebf05345dadb3fcb232cb788a9126e563f6bb767

gnu-v2-abi.c: Add casts

I looked at changing these is_destructor_name/is_constructor_name
interfaces in order to detangle the boolean result from the ctor/dtor
kind return, but then realized that this design goes all the way down
to the libiberty demangler interfaces.  E.g, include/demangle.h:

 ~~~
 /* Return non-zero iff NAME is the mangled form of a constructor name
    in the G++ V3 ABI demangling style.  Specifically, return an `enum
    gnu_v3_ctor_kinds' value indicating what kind of constructor
    it is.  */
 extern enum gnu_v3_ctor_kinds
	 is_gnu_v3_mangled_ctor (const char *name);


 enum gnu_v3_dtor_kinds {
   gnu_v3_deleting_dtor = 1,
   gnu_v3_complete_object_dtor,
   gnu_v3_base_object_dtor,
   /* These are not part of the V3 ABI.  Unified destructors are generated
      as a speed-for-space optimization when the -fdeclone-ctor-dtor option
      is used, and are always internal symbols.  */
   gnu_v3_unified_dtor,
   gnu_v3_object_dtor_group
 };
 ~~~

libiberty/cp-demangle.c:

 ~~~
 enum gnu_v3_ctor_kinds
 is_gnu_v3_mangled_ctor (const char *name)
 {
   enum gnu_v3_ctor_kinds ctor_kind;
   enum gnu_v3_dtor_kinds dtor_kind;

   if (! is_ctor_or_dtor (name, &ctor_kind, &dtor_kind))
     return (enum gnu_v3_ctor_kinds) 0;
   return ctor_kind;
 }
 ~~~

etc.

gdb/ChangeLog:
2015-10-29  Pedro Alves  <palves@redhat.com>

	* gnu-v2-abi.c (gnuv2_is_destructor_name)
	(gnuv2_is_constructor_name): Add casts.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix access_to_packed_array.exp typos/errors
@ 2015-10-27  5:19 sergiodj+buildbot
  2015-10-27 19:34 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-10-27  5:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5e2e7507b4ef8410501452224d98071657ea2d53 ***

Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Branch: master
Commit: 5e2e7507b4ef8410501452224d98071657ea2d53

Fix access_to_packed_array.exp typos/errors

Running ./gdb.ada/access_to_packed_array.exp ...
ERROR: tcl error sourcing ./gdb.ada/access_to_packed_array.exp.
ERROR: extra characters after close-quote
    while executing
"gdb_test "print pack.a" "\\(0 => 1, 2, 3, 4, 5, 6, 7, 8, 9, 10\\)")"
    (file "./gdb.ada/access_to_packed_array.exp" line 29)
    invoked from within
"source ./gdb.ada/access_to_packed_array.exp"
    ("uplevel" body line 1)
    invoked from within
"uplevel #0 source ./gdb.ada/access_to_packed_array.exp"
    invoked from within
"catch "uplevel #0 source $test_file_name""

Unrelated to the typos I have changed the print expectations s/"x"/" = x"/
as for example expectation "3" should not match " = 43".

2015-10-27  Jan Kratochvil  <jan.kratochvil@redhat.com>

	* gdb.ada/access_to_packed_array.exp: Fix typos erroring the testfile.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] sparc64-tdep.c: Don't assign using memcpy return
@ 2015-10-24 23:13 sergiodj+buildbot
  2015-10-25 13:38 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-10-24 23:13 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cfcb22a541ab8f783bf667cf7afbbfd9cd243cce ***

Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: cfcb22a541ab8f783bf667cf7afbbfd9cd243cce

sparc64-tdep.c: Don't assign using memcpy return

This:

  valbuf = memcpy (buf, valbuf, len);

causes a build failure in C++, because memcpy returns the value of
"buf" as a void *.  Instead of adding a cast, we can just do the
assignment separately.

gdb/ChangeLog:

	* sparc64-tdep.c (sparc64_store_arguments): Split assignment of
	valbuf.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Add cast in nto-tdep.c
@ 2015-10-22 16:10 sergiodj+buildbot
  2015-10-23  7:13 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-10-22 16:10 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fb70bc1a74d371cc6cc07e018df436a17c26037e ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: fb70bc1a74d371cc6cc07e018df436a17c26037e

Add cast in nto-tdep.c

gdb/ChangeLog:

	* nto-tdep.c (nto_inferior_data): Add cast.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] fort_dyn_array: add basic fortran dyn array support
@ 2015-10-21 19:47 sergiodj+buildbot
  2015-10-22  3:25 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-10-21 19:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3f2f83ddcba5b04389dd3c666ce7d4cace7e5b63 ***

Author: Keven Boell <keven.boell@linux.intel.com>
Branch: master
Commit: 3f2f83ddcba5b04389dd3c666ce7d4cace7e5b63

fort_dyn_array: add basic fortran dyn array support

Fortran provide types whose values may be dynamically allocated
or associated with a variable under explicit program control.
The purpose of this commit is:

  * to read allocated/associated DWARF tags and store them in
    the dynamic property list of main_type.

  * enable GDB to print the value of a dynamic array in Fortran
    in case the type is allocated or associated (pointer to
    dynamic array).

Examples:
    (gdb) p vla_not_allocated
    $1 = <not allocated>

    (gdb) p vla_allocated
    $1 = (1, 2, 3)

    (gdb) p vla_ptr_not_associated
    $1 = <not associated>

    (gdb) p vla_ptr_associated
    $1 = (1, 2, 3)

Add basic test coverage for most dynamic array use-cases in Fortran.
The commit contains the following tests:
  * Ensure that values of Fortran dynamic arrays
    can be evaluated correctly in various ways and states.
  * Ensure that Fortran primitives can be evaluated
    correctly when used as a dynamic array.
  * Dynamic arrays passed to subroutines and handled
    in different ways inside the routine.
  * Ensure that the ptype of dynamic arrays in
    Fortran can be printed in GDB correctly.
  * Ensure that dynamic arrays in different states
    (allocated/associated) can be evaluated.
  * Dynamic arrays passed to functions and returned from
    functions.
  * History values of dynamic arrays can be accessed and
    printed again with the correct values.
  * Dynamic array evaluations using MI protocol.
  * Sizeof output of dynamic arrays in various states.

The patch was tested using the test suite on Ubuntu 12.04 64bit.

gdb/ChangeLog:

        * dwarf2read.c (set_die_type): Add read of
        DW_AT_allocated and DW_AT_associated.
        * f-typeprint.c: New include of typeprint.h
        (f_print_type): Add check for allocated/associated
        status of type.
        (f_type_print_varspec_suffix): Add check for
        allocated/associated status of type.
        * gdbtypes.c (create_array_type_with_stride):
        Add check for valid data location of type in
        case allocated or associated attributes are set.
        Length of an array should be only calculated if
        allocated or associated is resolved as true.
        (is_dynamic_type_internal): Add check for allocated/
        associated.
        (resolve_dynamic_array): Evaluate allocated/associated
        properties.
        * gdbtypes.h (enum dynamic_prop_node_kind): <DYN_PROP_ALLOCATED>
        <DYN_PROP_ASSOCIATED>: New enums.
        (TYPE_ALLOCATED_PROP, TYPE_ASSOCIATED_PROP): New macros.
        (type_not_allocated): New function.
        (type_not_associated): New function.
        * valarith.c (value_subscripted_rvalue): Add check for
        allocated/associated.
        * valprint.c: New include of typeprint.h.
        (valprint_check_validity): Add check for allocated/associated.
        (value_check_printable): Add check for allocated/
        associated.
        * typeprint.h (val_print_not_allocated): New function.
        (val_print_not_associated): New function.
        * typeprint.c (val_print_not_allocated): New function.
        (val_print_not_associated): New function.

gdb/testsuite/ChangeLog:

        * gdb.fortran/vla-alloc-assoc.exp: New file.
        * gdb.fortran/vla-datatypes.exp: New file.
        * gdb.fortran/vla-datatypes.f90: New file.
        * gdb.fortran/vla-history.exp: New file.
        * gdb.fortran/vla-ptype-sub.exp: New file.
        * gdb.fortran/vla-ptype.exp: New file.
        * gdb.fortran/vla-sizeof.exp: New file.
        * gdb.fortran/vla-sub.f90: New file.
        * gdb.fortran/vla-value-sub-arbitrary.exp: New file.
        * gdb.fortran/vla-value-sub-finish.exp: New file.
        * gdb.fortran/vla-value-sub.exp: New file.
        * gdb.fortran/vla-value.exp: New file.
        * gdb.fortran/vla-ptr-info.exp: New file.
        * gdb.mi/mi-vla-fortran.exp: New file.
        * gdb.mi/vla.f90: New file.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [nto] Fix nto target stopped by watchpoint.
@ 2015-10-21 14:47 sergiodj+buildbot
  2015-10-21 15:24 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-10-21 14:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a9889169e5b21efb8c42105fc62461be43968d64 ***

Author: Aleksandar Ristovski <aristovski@qnx.com>
Branch: master
Commit: a9889169e5b21efb8c42105fc62461be43968d64

[nto] Fix nto target stopped by watchpoint.

Fix 'stopped by watchpoint' detection: add inferior data, use inferior data
for storing last stopped flags needed for detection.

gdb/ChangeLog:

	* nto-procfs.c (procfs_wait): Set stopped_flags nad stopped_pc.
	(procfs_stopped_by_watchpoint): Use flags stored in inferior data.
	* nto-tdep.c (nto_new_inferior_data_reg): New definition.
	(nto_new_inferior_data, nto_inferior_data_cleanup, nto_inferior_data):
	New functions.
	(_initialize_nto_tdep): New forward declaration, new function.
	* nto-tdep.h (struct nto_inferior_data): New struct.
	(nto_inferior_data): New function declaration.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
[parent not found: <170742de5dd5be2156f938e00e2451526ef57d5c@gdb-build>]
* [binutils-gdb] ada-lang.c: malloc/alloca casts for C++
@ 2015-10-13 18:50 sergiodj+buildbot
  2015-10-13 20:06 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-10-13 18:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT aa5c10ce9b1bd04a7f4a619d5e956c977fcd60d3 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: aa5c10ce9b1bd04a7f4a619d5e956c977fcd60d3

ada-lang.c: malloc/alloca casts for C++

gdb/ChangeLog:
2015-10-13  Pedro Alves  <palves@redhat.com>

	* ada-lang.c (ada_value_primitive_packed_val): Add casts to malloc
	and alloca calls.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] aarch64: Use gdb_sys_no_syscall enum instead of -1
@ 2015-10-12 16:35 sergiodj+buildbot
  2015-10-13  3:09 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-10-12 16:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cb65d272fd09b79b7911cc00b5262d4fe14a40d7 ***

Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: cb65d272fd09b79b7911cc00b5262d4fe14a40d7

aarch64: Use gdb_sys_no_syscall enum instead of -1

Fixes:

/home/simark/src/binutils-gdb/gdb/aarch64-linux-tdep.c: In function "gdb_syscall aarch64_canonicalize_syscall(aarch64_syscall)":
/home/simark/src/binutils-gdb/gdb/aarch64-linux-tdep.c:874:13: error: invalid conversion from "int" to "gdb_syscall" [-fpermissive]
     return -1;
             ^

gdb/ChangeLog:

	* aarch64-linux-tdep.c (aarch64_canonicalize_syscall): Return
	gdb_sys_no_syscall instead of -1.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] New test case gdb.arch/disp-step-insn-reloc.exp
@ 2015-10-12 11:36 sergiodj+buildbot
  2015-10-12 19:18 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-10-12 11:36 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0fd8ac1c450d340d0b11823107d9e990341e7e11 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 0fd8ac1c450d340d0b11823107d9e990341e7e11

New test case gdb.arch/disp-step-insn-reloc.exp

This patch adds a new test case which uses gdb.arch/insn-reloc.c too
to test displaced stepping.  Nowadays, tests are for x86, x86_64 and
aarch64.

gdb/testsuite:

2015-10-12  Yao Qi  <yao.qi@linaro.org>

	* gdb.arch/disp-step-insn-reloc.exp: New test case.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Reorder variable declarations in ada_value_primitive_packed_val
@ 2015-10-09 22:00 sergiodj+buildbot
  2015-10-10  5:26 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-10-09 22:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a1c95e6b6ede168770664cdca8ae1568187554b4 ***

Author: Joel Brobecker <brobecker@adacore.com>
Branch: master
Commit: a1c95e6b6ede168770664cdca8ae1568187554b4

Reorder variable declarations in ada_value_primitive_packed_val

This patch just changes the order in which local variables are declared
so as to group the logically-related variables together.  No code
change otherwise.

gdb/ChangeLog:

        * ada-lang.c (ada_value_primitive_packed_val): Reorder local
        variable declarations.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] btrace: fix void return
@ 2015-10-08  7:41 sergiodj+buildbot
  2015-10-08  7:48 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-10-08  7:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 04c4fe8c59d3f2870a5df7be7f55fca60d88381f ***

Author: Markus Metzger <markus.t.metzger@intel.com>
Branch: master
Commit: 04c4fe8c59d3f2870a5df7be7f55fca60d88381f

btrace: fix void return

record_btrace_resume returns the void return from the to_resume method of the
target beneath.  Split this into calling to_resume and return.

gdb/
	* record-btrace.c (record_btrace_resume): Fix void return.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Avoid using 'template' C++ keyword
@ 2015-10-07 14:29 sergiodj+buildbot
  2015-10-07 14:35 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-10-07 14:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 875880c661e71a7622d8f7282f0dd1ef756040ff ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 875880c661e71a7622d8f7282f0dd1ef756040ff

Avoid using 'template' C++ keyword

'template' is used in include/opcode/aarch64.h as below,

 typedef struct
 {
   const char *template;
   uint32_t value;
   int has_xt;
 } aarch64_sys_ins_reg;

and it triggers compilation errors when GDB is built in C++ mode.

In file included from git/gdb/aarch64-tdep.c:62:0:
git/gdb/../include/opcode/aarch64.h:651:15: error: expected unqualified-id before 'template'
   const char *template;

This patch is to rename field template to name.

gas/

	* config/tc-aarch64.c (md_begin): Access field 'name' rather
	than 'template'.

include/opcode/

	* aarch64.h (aarch64_sys_ins_reg) <template>: Removed.
	<name>: New field.

opcodes/

	* aarch64-dis.c (aarch64_ext_sysins_op): Access field
	'name' rather than 'template'.
	* aarch64-opc.c (aarch64_print_operand): Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Wrap include/opcode/aarch64.h in extern "C" for C++
@ 2015-10-07 14:11 sergiodj+buildbot
  2015-10-07 14:17 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-10-07 14:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d3e12b29aef25bc9d1830b0a05643b11296f1b8f ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: d3e12b29aef25bc9d1830b0a05643b11296f1b8f

Wrap include/opcode/aarch64.h in extern "C" for C++

This is sufficient to link an aarch64 GDB built in C++ mode.  Pedro
did something similar in Feb
https://sourceware.org/ml/binutils/2015-02/msg00176.html

include/opcode/

2015-10-07  Yao Qi  <yao.qi@linaro.org>

	* aarch64.h [__cplusplus]: Wrap in extern "C".


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] New ARC implementation.
@ 2015-10-07 13:26 sergiodj+buildbot
  2015-10-07 13:41 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-10-07 13:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 886a250647ac0c608f20a7007fc2167a70f64e20 ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: 886a250647ac0c608f20a7007fc2167a70f64e20

New ARC implementation.

bfd	* archures.c: Remove support for older ARC. Added support for new
	ARC cpus (ARC600, ARC601, ARC700, ARCV2).
	* bfd-in2.h: Likewise.
	* config.bfd: Likewise.
	* cpu-arc.c: Likewise.
	* elf32-arc.c: Totally changed file with a refactored
	inplementation of the ARC port.
	* libbfd.h: Added ARC specific relocation types.
	* reloc.c: Likewise.

gas     * config/tc-arc.c: Revamped file for ARC support.
        * config/tc-arc.h: Likewise.
        * doc/as.texinfo: Add new ARC options.
        * doc/c-arc.texi: Likewise.

ld	* configure.tgt: Added target arc-*-elf* and arc*-*-linux-uclibc*.
	* emulparams/arcebelf_prof.sh: New file
	* emulparams/arcebelf.sh: Likewise.
	* emulparams/arceblinux_prof.sh: Likewise.
	* emulparams/arceblinux.sh: Likewise.
	* emulparams/arcelf_prof.sh: Likewise.
	* emulparams/arcelf.sh: Likewise.
	* emulparams/arclinux_prof.sh: Likewise.
	* emulparams/arclinux.sh: Likewise.
	* emulparams/arcv2elfx.sh: Likewise.
	* emulparams/arcv2elf.sh: Likewise.
	* emultempl/arclinux.em: Likewise.
	* scripttempl/arclinux.sc: Likewise.
	* scripttempl/elfarc.sc: Likewise.
	* scripttempl/elfarcv2.sc: Likewise
	* Makefile.am: Add new ARC emulations.
	* Makefile.in: Regenerate.
	* NEWS: Mention the new feature.

opcodes * arc-dis.c: Revamped file for ARC support
	* arc-dis.h: Likewise.
	* arc-ext.c: Likewise.
	* arc-ext.h: Likewise.
	* arc-opc.c: Likewise.
	* arc-fxi.h: New file.
	* arc-regs.h: Likewise.
	* arc-tbl.h: Likewise.

binutils * readelf.c (get_machine_name): Remove A5 reference. Add ARCompact
	and ARCv2.
	(get_machine_flags): Handle EM_ARCV2 and EM_ARCOMPACT.
	(guess_is_rela): Likewise.
	(dump_relocations): Likewise.
	(is_32bit_abs_reloc): Likewise.
	(is_16bit_abs_reloc): Likewise.
	(is_none_reloc): Likewise.
	* NEWS: Mention the new feature.

include	* dis-asm.h (arc_get_disassembler): Correct declaration.
	* arc-reloc.def: Macro file with definition of all relocation
	types.
	* arc.h: Changed macros for the newly supported ARC cpus.  Altered
	enum defining the supported relocations.
	* common.h: Changed EM_ARC_A5 definition to EM_ARC_COMPACT. Added
	macro for EM_ARC_COMPACT2.
        * arc-func.h: New file.
        * arc.h: Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [aarch64] expose disas_aarch64_insn and rename it to aarch64_decode_insn
@ 2015-10-02 14:46 sergiodj+buildbot
  2015-10-02 16:29 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-10-02 14:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 36f4aab18ccf897b405f137d6cd4f9673bd947fc ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 36f4aab18ccf897b405f137d6cd4f9673bd947fc

[aarch64] expose disas_aarch64_insn and rename it to aarch64_decode_insn

We want to use disas_aarch64_insn inside GDB to decode instructions, so
this patch exposes it and rename it to aarch64_decode_insn to follow
the conventions of other interfaces.

include/opcode:

2015-10-02  Yao Qi  <yao.qi@linaro.org>

	* aarch64.h (aarch64_decode_insn): Declare it.

opcodes:

2015-10-02  Yao Qi  <yao.qi@linaro.org>

	* aarch64-dis.c	(disas_aarch64_insn): Remove static.  Change
	argument insn type to aarch64_insn.  Rename to ...
	(aarch64_decode_insn): ... it.
	(print_insn_aarch64_word): Caller updated.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] The FT32's disassembly of 10-bit literals has the incorrect mask.
@ 2015-09-25 20:12 sergiodj+buildbot
  2015-09-26  7:49 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-09-25 20:12 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9a09557a93b9f11371e4213589878437e567f897 ***

Author: jamesbowman <jamesb@excamera.com>
Branch: master
Commit: 9a09557a93b9f11371e4213589878437e567f897

The FT32's disassembly of 10-bit literals has the incorrect mask.

[opcodes]
	* ft32-dis.c (print_insn_ft32): Fix incorrect data field mask.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Wrap gdb_agent_op_sizes by #ifndef IN_PROCESS_AGENT
@ 2015-09-21 14:29 sergiodj+buildbot
  2015-09-21 17:51 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-09-21 14:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9812b2e60750cc7bbfa252d9ae8d85a72a399e01 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 9812b2e60750cc7bbfa252d9ae8d85a72a399e01

Wrap gdb_agent_op_sizes by #ifndef IN_PROCESS_AGENT

Hi,
I see the following build warning with recent GCC built from mainline,

aarch64-none-linux-gnu-gcc -g -O2    -I. -I/home/yao/SourceCode/gnu/gdb/git/gdb/gdbserver -I/home/yao/SourceCode/gnu/gdb/git/gdb/gdbserver/../common -I/home/yao/SourceCode/gnu/gdb/git/gdb/gdbserver/../regformats -I/home/yao/SourceCode/gnu/gdb/git/gdb/gdbserver/.. -I/home/yao/SourceCode/gnu/gdb/git/gdb/gdbserver/../../include -I/home/yao/SourceCode/gnu/gdb/git/gdb/gdbserver/../gnulib/import -Ibuild-gnulib-gdbserver/import  -Wall -Wpointer-arith -Wformat-nonliteral -Wno-char-subscripts -Wempty-body -Wdeclaration-after-statement -Werror -DGDBSERVER  -DCONFIG_UST_GDB_INTEGRATION -fPIC -DIN_PROCESS_AGENT -fvisibility=hidden -c -o ax-ipa.o -MT ax-ipa.o -MMD -MP -MF .deps/ax-ipa.Tpo `echo " -Wall -Wpointer-arith -Wformat-nonliteral -Wno-char-subscripts -Wempty-body -Wdeclaration-after-statement " | sed "s/ -Wformat-nonliteral / -Wno-format-nonliteral /g"` /home/yao/SourceCode/gnu/gdb/git/gdb/gdbserver/ax.c
/home/yao/SourceCode/gnu/gdb/git/gdb/gdbserver/ax.c:73:28: error: 'gdb_agent_op_sizes' defined but not used [-Werror=unused-const-variable]
 static const unsigned char gdb_agent_op_sizes [gdb_agent_op_last] =
                            ^
cc1: all warnings being treated as errors

gdb_agent_op_sizes is only used in function is_goto_target, which is
defined inside #ifndef IN_PROCESS_AGENT.  This warning is not arch
specific, so GCC mainline for other targets should produce this warning
too, although this warning is triggered by enabling aarch64 fast
tracepoint.  The fix is to move gdb_agent_op_sizes to

gdb/gdbserver:

2015-09-21  Yao Qi  <yao.qi@linaro.org>

	* ax.c [!IN_PROCESS_AGENT] (gdb_agent_op_sizes): Define it.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] btrace: resume all requested threads
@ 2015-09-18 14:15 sergiodj+buildbot
  2015-09-19  8:42 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-09-18 14:15 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0ca912dfef6289f9d2cd7d70b7ec80883a9b4395 ***

Author: Markus Metzger <markus.t.metzger@intel.com>
Branch: master
Commit: 0ca912dfef6289f9d2cd7d70b7ec80883a9b4395

btrace: resume all requested threads

The record targets are implicitly schedlocked.  They only step the current
thread and keep other threads where they are.

Change record btrace to step all requested threads in to_resume.

For maintenance and debugging, we keep the old behaviour when the target below
is not non-stop.  Enable with "maint set target-non-stop on".

gdb/
	* record-btrace.c (record_btrace_resume_thread): A move request
	overwrites a previous move request.
	(record_btrace_find_resume_thread): Removed.
	(record_btrace_resume): Resume all requested threads.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] btrace: add missing NO_HISTORY
@ 2015-09-18 14:04 sergiodj+buildbot
  2015-09-19  2:23 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-09-18 14:04 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cf8f8f0c4244b4980ce538680f81de3738ba08d6 ***

Author: Markus Metzger <markus.t.metzger@intel.com>
Branch: master
Commit: cf8f8f0c4244b4980ce538680f81de3738ba08d6

btrace: add missing NO_HISTORY

If a single-step ended right at the end of the execution history, we forgot
to announce that.  Fix it.

gdb/
	* record-btrace.c (record_btrace_single_step_forward): Return
	NO_HISTORY if a step brings us to the end of the execution history.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Remove one unnecessary iteration in insertion sort
@ 2015-09-18  4:32 sergiodj+buildbot
  2015-09-18  8:43 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-09-18  4:32 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b29b8669ad250df649a0f02c5575e7163a2cd9e4 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: b29b8669ad250df649a0f02c5575e7163a2cd9e4

Remove one unnecessary iteration in insertion sort

	PR 18867
	* elflink.c (elf_link_adjust_relocs): Correct start of insertion
	sort main loop.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] non-stop-fair-events.exp slower on software single-step && !displ-step targets
@ 2015-09-16 15:53 sergiodj+buildbot
  2015-09-18  4:11 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-09-16 15:53 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1ed415e2b9b985aac087c35949d0e1e489ab496d ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 1ed415e2b9b985aac087c35949d0e1e489ab496d

non-stop-fair-events.exp slower on software single-step && !displ-step targets

On software single-step targets that don't support displaced stepping,
threads keep hitting each other's single-step breakpoints, and then
GDB needs to pause all threads to step past those.  The end result is
that progress in the main thread will be slower and it may take a bit
longer for the signal to be queued.  This patch bumps the timeout on
such targets.

gdb/testsuite/ChangeLog:
2015-09-16  Pedro Alves  <palves@redhat.com>
	    Sandra Loosemore <sandra@codesourcery.com>

	* gdb.threads/non-stop-fair-events.c (timeout): New global.
	(SECONDS): Redefine.
	(main): Call pthread_kill and alarm early.
	* gdb.threads/non-stop-fair-events.exp: Probe displaced stepping
	support.
	(test): If the target can't hardware step and doesn't support
	displaced stepping, increase the timeout.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Make it easier to debug non-stop-fair-events.exp
@ 2015-09-16 15:38 sergiodj+buildbot
  2015-09-18  4:00 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-09-16 15:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d136eff549649f23b12121575362dfa09343ea0a ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: d136eff549649f23b12121575362dfa09343ea0a

Make it easier to debug non-stop-fair-events.exp

If we enable infrun debug running this test, it quickly fails with a
full expect buffer.  That can be simply handled with a couple
exp_continues.  As it's annoying to hack this every time we need to
debug the test, this patch adds bits to enable debugging support
easily, with a one-line change.

And then, if any iteration of the test fails, we end up with a long
cascade of time outs.  Just bail out when we see the first fail.

gdb/testsuite/
2015-09-16  Pedro Alves  <palves@redhat.com>

	* gdb.threads/non-stop-fair-events.exp (gdb_test_no_anchor)
	(enable_debug): New procedures.
	(test): Use them.  Bail out if waiting for threads fails.
	(top level): Bail out if a test fails.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Don't skip gdb.asm/asm-source.exp on aarch64
@ 2015-09-16 15:03 sergiodj+buildbot
  2015-09-18  3:51 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-09-16 15:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 991f019c506528fa94ac173db6f1120f8b2373bf ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 991f019c506528fa94ac173db6f1120f8b2373bf

Don't skip gdb.asm/asm-source.exp on aarch64

This patch adds gdb.asm/aarch64.inc, so asm-source.exp isn't skipped
on aarch64 any more.

gdb/testsuite:

2015-09-16  Yao Qi  <yao.qi@linaro.org>

	* gdb.asm/asm-source.exp: Set asm-arch for
	aarch64*-*-* target.
	* gdb.asm/aarch64.inc: New file.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix slowdown in ld -r for most common case of out-of-order relocs
@ 2015-09-16 13:43 sergiodj+buildbot
  2015-09-17 19:50 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-09-16 13:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bca6d0e3195217576b39fa1205469e1d578b386a ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: bca6d0e3195217576b39fa1205469e1d578b386a

Fix slowdown in ld -r for most common case of out-of-order relocs

I chose insertion sort since relocs are mostly sorted, but there is a
common case we can handle better;  A run of relocs put out of order
due to not linking input files in order.

	PR 18867
	* elflink.c (elf_link_adjust_relocs): Modify insertion sort to
	insert a run.  Return status in case of malloc failure.
	Adjust callers.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [Ada] Enhance type printing for arrays with variable-sized elements
@ 2015-09-15 22:14 sergiodj+buildbot
  2015-09-17 11:36 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-09-15 22:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bfca584fae65570fa8ed052f662948763f3ccfa8 ***

Author: Pierre-Marie de Rodat <derodat@adacore.com>
Branch: master
Commit: bfca584fae65570fa8ed052f662948763f3ccfa8

[Ada] Enhance type printing for arrays with variable-sized elements

This change is relevant only for standard DWARF (as opposed to the GNAT
encodings extensions): at the time of writing it only makes a difference
with GCC patches that are to be integrated: see the patch series
submission at
<https://gcc.gnu.org/ml/gcc-patches/2015-07/msg01353.html>.

Given the following Ada declarations:

   subtype Small_Int is Natural range 0 .. 100;
   type R_Type (L : Small_Int := 0) is record
      S : String (1 .. L);
   end record;
   type A_Type is array (Natural range <>) of R_Type;

   A : A_Type := (1 => (L => 0, S => ""),
                  2 => (L => 2, S => "ab"));

Before this change, we would get the following GDB session:

    (gdb) ptype a
    type = array (1 .. 2) of foo.r_type <packed: 838-bit elements>

This is wrong: "a" is not a packed array.  This output comes from the
fact that, because R_Type has a dynamic size (with a maximum), the
compiler has to describe in the debugging information the size allocated
for each array element (i.e. the stride, in DWARF parlance: see
DW_AT_byte_stride).  Ada type printing currently assumes that arrays
with a stride are packed, hence the above output.

In practice, GNAT never performs bit-packing for arrays that contain
variable-sized elements.  Leveraging this fact, this patch enhances type
printing so that ptype does not pretend that arrays are packed when they
have a stride and they contain dynamic elements.  After this change, we
get the following expected output:

    (gdb) ptype a
    type = array (1 .. 2) of foo.r_type

gdb/ChangeLog:

	* ada-typeprint.c (print_array_type): Do not describe arrays as
	packed when they embed dynamic elements.

gdb/testsuite/ChangeLog:

	* gdb.ada/array_of_variable_length.exp: New testcase.
	* gdb.ada/array_of_variable_length/foo.adb: New file.
	* gdb.ada/array_of_variable_length/pck.adb: New file.
	* gdb.ada/array_of_variable_length/pck.ads: New file.

Tested on x86_64-linux, no regression.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Handle clang naming of function static local variable.
@ 2015-09-15 21:24 sergiodj+buildbot
  2015-09-17 11:17 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-09-15 21:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b326e5870e54f52d52c32388f7f6e07454e2f2c2 ***

Author: Doug Evans <dje@google.com>
Branch: master
Commit: b326e5870e54f52d52c32388f7f6e07454e2f2c2

Handle clang naming of function static local variable.

clang names the local variable t_structs_a.buf.

gdb/testsuite/ChangeLog:

	* gdb.base/callfuncs.exp (do_function_calls): Handle clang naming
	of function static local variable.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix PR/18564 - regression in showing __thread so extern variable
@ 2015-09-15 19:46 sergiodj+buildbot
  2015-09-17 10:51 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-09-15 19:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5382cfab6110741b8ba36965b30334c00d8f9409 ***

Author: Philippe Waroquiers <philippe.waroquiers@skynet.be>
Branch: master
Commit: 5382cfab6110741b8ba36965b30334c00d8f9409

Fix PR/18564 - regression in showing __thread so extern variable

Ensure tls variable address is not relocated, as the msym addr
is an offset in the thread local storage of the shared library/object.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [ppc64le] Use skip_entrypoint for skip_trampoline_code
@ 2015-09-15 18:25 sergiodj+buildbot
  2015-09-16 16:17 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-09-15 18:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 141c5cc4c44a6ce1a5c628c0f4849a8b1c91d383 ***

Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Branch: master
Commit: 141c5cc4c44a6ce1a5c628c0f4849a8b1c91d383

[ppc64le] Use skip_entrypoint for skip_trampoline_code

ppc64le loses control when stepping between two PLT-called functions inside
a shared library:

29        shlib_second (); /* first-hit */^M
(gdb) PASS: gdb.base/solib-intra-step.exp: first-hit
step^M
^M
Program received signal SIGABRT, Aborted.^M
0x00003fffb7cbe578 in __GI_raise (sig=<optimized out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56^M
56        return INLINE_SYSCALL (tgkill, 3, pid, selftid, sig);^M
(gdb) FAIL: gdb.base/solib-intra-step.exp: second-hit
->
29        shlib_second (); /* first-hit */^M
(gdb) PASS: gdb.base/solib-intra-step.exp: first-hit
step^M
shlib_second () at ./gdb.base/solib-intra-step-lib.c:23^M
23        abort (); /* second-hit */^M
(gdb) PASS: gdb.base/solib-intra-step.exp: second-hit

This is because gdbarch_skip_trampoline_code() will resolve the final function
as shlib_second+0 and place there the breakpoint, but ld.so will jump after
the breakpoint - at shlib_second+8 - as it is ELFv2 local symbol optimization:

Dump of assembler code for function shlib_second:
   0x0000000000000804 <+0>:     addis   r2,r12,2
   0x0000000000000808 <+4>:     addi    r2,r2,30668
   0x000000000000080c <+8>:     mflr    r0

Currently gdbarch_skip_entrypoint() has been called in skip_prologue_sal() and
fill_in_stop_func() but that is not enough.  I believe
gdbarch_skip_entrypoint() should be called after every
gdbarch_skip_trampoline_code().

gdb/ChangeLog
2015-09-15  Jan Kratochvil  <jan.kratochvil@redhat.com>

	* linespec.c (minsym_found): Call gdbarch_skip_entrypoint.
	* ppc64-tdep.c (ppc64_skip_trampoline_code): Rename to ...
	(ppc64_skip_trampoline_code_1): ... here.
	(ppc64_skip_trampoline_code): New wrapper function.
	* symtab.c (find_function_start_sal): Call gdbarch_skip_entrypoint.

gdb/testsuite/ChangeLog
2015-09-15  Jan Kratochvil  <jan.kratochvil@redhat.com>

	* gdb.opt/solib-intra-step-lib.c: New file.
	* gdb.opt/solib-intra-step-main.c: New file.
	* gdb.opt/solib-intra-step.exp: New file.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] gdbserver: Fix exec stop reply reporting conditions
@ 2015-09-15 17:47 sergiodj+buildbot
  2015-09-16 12:57 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-09-15 17:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d57e0d5022e0d3409f68bb02fd27311d8d0327ea ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: d57e0d5022e0d3409f68bb02fd27311d8d0327ea

gdbserver: Fix exec stop reply reporting conditions

gdb/gdbserver/ChangeLog:
2015-09-15  Pedro Alves  <palves@redhat.com>

	* remote-utils.c (prepare_resume_reply) <TARGET_WAITKIND_EXECD>:
	Check whether to report exec events instead of checking whether
	multiprocess is enabled.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix gdb.threads/non-ldr-exc-3.exp race
@ 2015-09-15 16:59 sergiodj+buildbot
  2015-09-15 20:32 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-09-15 16:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d15dcecdee0f07b0b088dd3a8ebb50826c5b7bc5 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: d15dcecdee0f07b0b088dd3a8ebb50826c5b7bc5

Fix gdb.threads/non-ldr-exc-3.exp race

gdb.threads/non-ldr-exc-3.exp is sometimes failing like this:

 [Switching to Thread 6831.6832]

 Breakpoint 2, thread_execler (arg=0x0) at /home/pedro/gdb/mygit/build/../src/gdb/testsuite/gdb.threads/non-ldr-exc-3.c:41
 41        if (execl (image, image, argv1, NULL) == -1) /* break-here */
 PASS: gdb.threads/non-ldr-exc-3.exp: lock-sched=on,non-stop=off: continue to breakpoint
 (gdb) set scheduler-locking on
 (gdb) FAIL: gdb.threads/non-ldr-exc-3.exp: lock-sched=on,non-stop=off: set scheduler-locking on

The problem is that the gdb_test_multiple is missing the prompt
anchor.  The problem was introduced by 2fd33e9448.  This reverts the
hunk that introduced the problem, reverting back to
gdb_continue_to_breakpoint.

gdb/testsuite/ChangeLog:
2015-09-15  Pedro Alves  <palves@redhat.com>

	* gdb.threads/non-ldr-exc-3.exp (do_test): Use
	gdb_continue_to_breakpoint instead of gdb_test_multiple.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Support single step by arch or target
@ 2015-09-15 14:02 sergiodj+buildbot
  2015-09-15 17:41 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-09-15 14:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 750ce8d1caf237464dd663de54ad055c0e58409d ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 750ce8d1caf237464dd663de54ad055c0e58409d

Support single step by arch or target

Nowadays, GDB only knows whether architecture supports hardware single
step or software single step (through gdbarch hook software_single_step),
and for a given instruction or instruction sequence, GDB knows how to
do single step (hardware or software).  However, GDB doesn't know whether
the target supports hardware single step.  It is possible that the
architecture doesn't support hardware single step, such as arm, but
the target supports, such as simulator.  This was discussed in this
thread https://www.sourceware.org/ml/gdb/2009-12/msg00033.html before.

I encounter this problem for aarch64 multi-arch support.  When aarch64
debugs arm program, gdbarch is arm, so software single step is still
used.  However, the underneath linux kernel does support hardware
single step, so IWBN to use it.

This patch is to add a new target_ops hook to_can_do_single_step, and
only use it in arm_linux_software_single_step to decide whether or not
to use hardware single step.  On the native aarch64 linux target, 1 is
returned.  On other targets, -1 is returned.  On the remote target, if
the target supports s and S actions in the vCont? reply, then target
can do single step.  However,  old GDBserver will send s and S in the
reply to vCont?, which will confuse new GDB.  For example, old GDBserver
on arm-linux will send s and S in the reply to vCont?, but it doesn't
support hardware single step.  On the other hand, new GDBserver, on
arm-linux for example, will not send s and S in the reply to vCont?,
but old GDB thinks it doesn't support vCont packet at all.  In order
to address this problem, I add a new qSupported feature vContSupported,
which indicates GDB wants to know the supported actions in the reply
to vCont?, and qSupported response contains vContSupported if the
stub is able tell supported vCont actions in the reply of vCont?.

If the patched GDB talks with patched GDBserver on x86, the RSP traffic
is like this:

 -> $qSupported:...+;vContSupported+
 <- ...+;vContSupported+
 ...
 -> $vCont?
 <- vCont;c;C;t;s;S;r

then, GDB knows the stub can do single step, and may stop using software
single step even the architecture doesn't support hardware single step.

If the patched GDB talks with patched GDBserver on arm, the last vCont?
reply will become:

 <- vCont;c;C;t

GDB thinks the target doesn't support single step, so it will use software
single step.

If the patched GDB talks with unpatched GDBserver, the RSP traffic is like
this:

 -> $qSupported:...+;vContSupported+
 <- ...+
 ...
 -> $vCont?
 <- vCont;c;C;t;s;S;r

although GDBserver returns s and S, GDB still thinks GDBserver may not
support single step because it doesn't support vContSupported.

If the unpatched GDB talks with patched GDBserver on x86, the RSP traffic
is like:

 -> $qSupported:...+;
 <- ...+;vContSupported+
 ...
 -> $vCont?
 <- vCont;c;C;t;s;S;r

Since GDB doesn't sent vContSupported in the qSupported feature, GDBserver
sends s and S regardless of the support of hardware single step.

gdb:

2015-09-15  Yao Qi  <yao.qi@linaro.org>

	* aarch64-linux-nat.c (aarch64_linux_can_do_single_step): New
	function.
	(_initialize_aarch64_linux_nat): Install it to to_can_do_single_step.
	* arm-linux-tdep.c (arm_linux_software_single_step): Return 0
	if target_can_do_single_step returns 1.
	* remote.c (struct vCont_action_support) <s, S>: New fields.
	(PACKET_vContSupported): New enum.
	(remote_protocol_features): New element for vContSupported.
	(remote_query_supported): Append "vContSupported+".
	(remote_vcont_probe): Remove support_s and support_S, use
	rs->supports_vCont.s and rs->supports_vCont.S instead.  Disable
	vCont packet if c and C actions are not supported.
	(remote_can_do_single_step): New function.
	(init_remote_ops): Install it to to_can_do_single_step.
	(_initialize_remote): Call add_packet_config_cmd.
	* target.h (struct target_ops) <to_can_do_single_step>: New field.
	(target_can_do_single_step): New macro.
	* target-delegates.c: Re-generated.

gdb/gdbserver:

2015-09-15  Yao Qi  <yao.qi@linaro.org>

	* server.c (vCont_supported): New global variable.
	(handle_query): Set vCont_supported to 1 if "vContSupported+"
	matches.  Append ";vContSupported+" to own_buf.
	(handle_v_requests): Append ";s;S" to own_buf if target supports
	hardware single step or vCont_supported is false.
	(capture_main): Set vCont_supported to zero.

gdb/doc:

2015-09-15  Yao Qi  <yao.qi@linaro.org>

	* gdb.texinfo (General Query Packets): Add vContSupported to
	tables of 'gdbfeatures' and 'stub features' supported in the
	qSupported packet, as well as to the list containing stub
	feature details.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] aarch64 multi-arch support (part 2): siginfo fixup
@ 2015-09-15 10:25 sergiodj+buildbot
  2015-09-15 13:39 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-09-15 10:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ade90bdeb78ccaeb294e34af04751f2f649a324f ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: ade90bdeb78ccaeb294e34af04751f2f649a324f

aarch64 multi-arch support (part 2): siginfo fixup

This patch is to fixup the siginfo_t when aarch64 gdb or gdbserver
read from or write to the arm inferior.  It is to convert the
"struct siginfo_t" between aarch64 and arm, which is quite mechanical.

gdb/gdbserver:

2015-09-15  Yao Qi  <yao.qi@linaro.org>

	* linux-aarch64-low.c (aarch64_linux_siginfo_fixup): New
	function.
	(struct linux_target_ops the_low_target): Install
	aarch64_linux_siginfo_fixup.

gdb:

2015-09-15  Yao Qi  <yao.qi@linaro.org>

	* aarch64-linux-nat.c (aarch64_linux_siginfo_fixup): New function.
	(_initialize_aarch64_linux_nat): Call linux_nat_set_siginfo_fixup.
	* nat/aarch64-linux.c (aarch64_compat_siginfo_from_siginfo):
	New function.
	(aarch64_siginfo_from_compat_siginfo): New function.
	* nat/aarch64-linux.h: Include signal.h.
	(compat_int_t, compat_uptr_t, compat_time_t): Typedef.
	(compat_timer_t, compat_clock_t): Likewise.
	(struct compat_timeval): New.
	(union compat_sigval): New.
	(struct compat_siginfo): New.
	(cpt_si_pid, cpt_si_uid, cpt_si_timerid): New macros.
	(cpt_si_overrun, cpt_si_status, cpt_si_utime): Likewise.
	(cpt_si_stime, cpt_si_ptr, cpt_si_addr): Likewise.
	(cpt_si_band, cpt_si_fd): Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix the SH behavior for EF_SH_PIC flag in FDPIC ABI
@ 2015-09-15  9:41 sergiodj+buildbot
  2015-09-15 10:15 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-09-15  9:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fbedb42d07cdc97a5bc698d1f7732ee776763cbc ***

Author: Rich Felker <dalias@libc.org>
Branch: master
Commit: fbedb42d07cdc97a5bc698d1f7732ee776763cbc

Fix the SH behavior for EF_SH_PIC flag in FDPIC ABI

Fix it so that it's compatible with the kernel and other FDPIC targets.

* elf32-sh.c (sh_elf_relocate_section): Set EF_SH_PIC flag
instead of clearing it on cross-section relocations.
(sh_elf_merge_private_data): Clear EF_SH_PIC flag by default.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Bail out of processing stop if hook-stop resumes target / changes context
@ 2015-09-14 15:40 sergiodj+buildbot
  2015-09-15  9:38 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-09-14 15:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4c2f2a792a5971fcc7fe6511725eaf50d19d302b ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 4c2f2a792a5971fcc7fe6511725eaf50d19d302b

Bail out of processing stop if hook-stop resumes target / changes context

This patch, relative to a tree with
https://sourceware.org/ml/gdb-patches/2015-08/msg00295.html, fixes
issues/crashes that trigger if something unexpected happens during a
hook-stop.

E.g., if the inferior disappears while running the hook-stop, we hit
failed assertions:

 (gdb) define hook-stop
 Type commands for definition of "hook-stop".
 End with a line saying just "end".
 >kill
 >end
 (gdb) si
 Kill the program being debugged? (y or n) [answered Y; input not from terminal]
 /home/pedro/gdb/mygit/build/../src/gdb/thread.c:88: internal-error: inferior_thread: Assertion `tp' failed.
 A problem internal to GDB has been detected,
 further debugging may prove unreliable.
 Quit this debugging session? (y or n)

I noticed that if a hook-stop issues a synchronous execution command,
we print the same stop event twice:

 (gdb) define hook-stop
 Type commands for definition of "hook-stop".
 End with a line saying just "end".
 >si
 >end
 (gdb) si
 0x000000000040074a      42          args[i] = 1; /* Init value.  */  <<<<<<< once
 0x000000000040074a      42          args[i] = 1; /* Init value.  */  <<<<<<< twice
 (gdb)

In MI:

 *stopped,reason="end-stepping-range",frame={addr="0x000000000040074a",func="main",args=[],file="threads.c",fullname="/home/pedro/gdb/tests/threads.c",line="42"},thread-id="1",stopped-threads="all",core="0"
 *stopped,reason="end-stepping-range",frame={addr="0x000000000040074a",func="main",args=[],file="threads.c",fullname="/home/pedro/gdb/tests/threads.c",line="42"},thread-id="1",stopped-threads="all",core="0"
 (gdb)

The fix has GDB stop processing the event if the context changed.  I
don't expect people to be doing crazy things from the hook-stop.
E.g., it gives me headaches to try to come up a proper behavior for
handling a thread change from a hook-stop... (E.g., imagine the
hook-stop does thread N; step, with scheduler-locing on).  I think the
most important bit here is preventing crashes.

The patch adds a new hook-stop.exp test that covers the above and also
merges in the old hook-stop-continue.exp and hook-stop-frame.exp into
the same framework.

gdb/ChangeLog:
2015-09-14  Pedro Alves  <palves@redhat.com>

	* infrun.c (current_stop_id): New global.
	(get_stop_id, new_stop_id): New functions.
	(fetch_inferior_event): Handle normal_stop proceeding the target.
	(struct stop_context): New.
	(save_stop_context, release_stop_context_cleanup)
	(stop_context_changed): New functions.
	(normal_stop): Return true if the hook-stop changes the stop
	context.
	* infrun.h (get_stop_id): Declare.
	(normal_stop): Now returns int.  Add documentation.

gdb/testsuite/ChangeLog:
2015-09-14  Pedro Alves  <palves@redhat.com>

	* gdb.base/hook-stop-continue.c: Delete.
	* gdb.base/hook-stop-continue.exp: Delete.
	* gdb.base/hook-stop-frame.c: Delete.
	* gdb.base/hook-stop-frame.exp: Delete.
	* gdb.base/hook-stop.c: New file.
	* gdb.base/hook-stop.exp: New file.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Remove duplicate gdb/NEWS entry
@ 2015-09-14 14:39 sergiodj+buildbot
  2015-09-14 19:29 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-09-14 14:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b027a8fa7dc4854e72ddada0b495b52166be2974 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: b027a8fa7dc4854e72ddada0b495b52166be2974

Remove duplicate gdb/NEWS entry

Commit fbea99ea8a06 added this to both the "Changes in GDB 7.10" and
"Changes since GDB 7.10" sections by mistake.

gdb/ChangeLog:
2015-09-14  Pedro Alves  <palves@redhat.com>

	* NEWS (Changes in GDB 7.10, New commands>: Remove duplicate
	mention of maint set/show target-non-stop.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Set .plt entry size to 0 in elf32-hppa.c
@ 2015-09-12 17:42 sergiodj+buildbot
  2015-09-14 11:10 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-09-12 17:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f3c3938c1c1a57f78e1be9d2dbb9ea0cda12edf6 ***

Author: John David Anglin <danglin@gcc.gnu.org>
Branch: master
Commit: f3c3938c1c1a57f78e1be9d2dbb9ea0cda12edf6

Set .plt entry size to 0 in elf32-hppa.c


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Extended-remote exec documentation
@ 2015-09-11 19:53 sergiodj+buildbot
  2015-09-12 17:35 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-09-11 19:53 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b459a59be3a9b92a27b71790f5e3f3be38595cb3 ***

Author: Don Breazeal <donb@codesourcery.com>
Branch: master
Commit: b459a59be3a9b92a27b71790f5e3f3be38595cb3

Extended-remote exec documentation

This patch adds documentation of support for exec events on
extended-remote Linux targets.

gdb/ChangeLog:

	* NEWS: Announce new remote packets for the exec-events
	feature and the exec-events feature and associated commands.

gdb/doc/ChangeLog:

	* gdb.texinfo (Remote Configuration): Add exec event
	feature to table of packet settings.
	(Stop Reply Packets): Add exec events to the list of stop
	reasons.
	(General Query Packets): Add exec events to tables of
	'gdbfeatures' and 'stub features' supported in the qSupported
	packet, as well as to the list containing stub feature
	details.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Extended-remote exec test
@ 2015-09-11 18:47 sergiodj+buildbot
  2015-09-12 17:28 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-09-11 18:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2fd33e94480fc2c662d1ad28f83e522cc5dbdc2e ***

Author: Don Breazeal <donb@codesourcery.com>
Branch: master
Commit: 2fd33e94480fc2c662d1ad28f83e522cc5dbdc2e

Extended-remote exec test

This patch updates several exec-related tests and some of the library
functions in order to get them running with extended-remote.  There were
three changes that were required, as follows:

In gdb.base/foll-exec.exp, use 'clean_start' in place of proc 'zap_session'
to reset the state of the debugger between tests.  This sets 'remote
exec-file' to execute the correct binary file in each subsequent test.

In gdb.base/pie-execl.exp, there is an expect statement with an expression
that is used to match output from both gdb and the program under debug.
For the remote target, this had to be split into two expressions, using
$inferior_spawn_id to match the output from the program.

Because I had encountered problems with extended-remote exec events in
non-stop mode in my manual testing, I added non-stop testing to the
non-ldr-exc-[1234].exp tests.  In order to set non-stop mode for remote
targets, it is necessary to 'set non-stop on' after gdb has started, but
before it connects to gdbserver.  This is done using 'save_vars' to set
non-stop mode in GDBFLAGS, so GDB sets non-stop mode on startup.

gdb/testsuite/ChangeLog:

	* gdb.base/foll-exec.c: Add copyright header.  Fix
	formatting issues.
	* gdb.base/foll-exec.exp (zap_session): Delete proc.
	(do_exec_tests): Use clean_restart in place of zap_session,
	and for test initialization.  Fix formatting issues.  Use
	fail in place of perror.
	* gdb.base/pie-execl.exp (main): Use 'inferior_spawn_id' in
	an expect statement to match an expression with output from
	the program under debug.
	* gdb.threads/non-ldr-exc-1.exp (do_test, main): Add
	non-stop tests and pass stop mode argument to clean_restart.
	Use save_vars to enable non-stop in GDBFLAGS.
	* gdb.threads/non-ldr-exc-2.exp: Likewise.
	* gdb.threads/non-ldr-exc-3.exp: Likewise.
	* gdb.threads/non-ldr-exc-4.exp: Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Extended-remote catch exec
@ 2015-09-11 18:42 sergiodj+buildbot
  2015-09-12 17:18 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-09-11 18:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d46addbb52a1f6d970bcac583b0b00ff4326e116 ***

Author: Don Breazeal <donb@codesourcery.com>
Branch: master
Commit: d46addbb52a1f6d970bcac583b0b00ff4326e116

Extended-remote catch exec

This patch implements exec catchpoints for extended-remote Linux
targets.  The implementation follows the same approach used for
fork catchpoints, implementing extended-remote target routines for
inserting and removing the catchpoints by just checking if exec events
are supported.  Existing host-side code and previous support for
extended-remote exec events takes care of the rest.

gdb/ChangeLog:

	* remote.c (remote_exec_event_p): New function.
	(remote_insert_exec_catchpoint): New function.
	(remote_remove_exec_catchpoint): New function.
	(init_extended_remote_ops): Initialize extended_remote_ops
	members to_insert_exec_catchpoint and
	to_remove_exec_catchpoint.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [AArch64] Cleanup comments in instruction decoding functions
@ 2015-09-11 16:41 sergiodj+buildbot
  2015-09-11 23:01 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-09-11 16:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 669e74e8295e8aef1dc052f30ff30bad624eb0f6 ***

Author: Pierre Langlois <pierre.langlois@arm.com>
Branch: master
Commit: 669e74e8295e8aef1dc052f30ff30bad624eb0f6

[AArch64] Cleanup comments in instruction decoding functions

gdb/ChangeLog:

	* aarch64-tdep.c (decode_cb): Move up comment describing the
	encoding.
	(decode_tb): Fix a typo in comment above the function.  Move up
	comment describing the encoding.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] gdb/18947: [aarch64]Step into shared library is very slow.
@ 2015-09-11 14:43 sergiodj+buildbot
  2015-09-11 17:58 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-09-11 14:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6dcaef99fab7e59e3eeb16a95d4c29b7b499b408 ***

Author: Mihail-Marian Nistor <mihail.nistor@freescale.com>
Branch: master
Commit: 6dcaef99fab7e59e3eeb16a95d4c29b7b499b408

gdb/18947: [aarch64]Step into shared library is very slow.

Install gdbarch_skip_solib_resolver on aarch64 GNU/Linux

gdb/ChangeLog:

2015-09-11  Mihail-Marian Nistor  <mihail.nistor@freescale.com>

	PR gdb/18947
	* aarch64-linux-tdep.c: (aarch64_linux_init_abi): Install
	glibc_skip_solib_resolver as gdbarch_skip_solib_resolver callback.

Signed-off-by: Mihail-Marian Nistor <mihail.nistor@freescale.com>


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Small refactor in ada-lang.c:scan_discrim_bound
@ 2015-09-10 15:59 sergiodj+buildbot
  2015-09-11 15:41 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-09-10 15:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5da1a4d34e730e0b4e2f034c81d22d5948a6ce67 ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: 5da1a4d34e730e0b4e2f034c81d22d5948a6ce67

Small refactor in ada-lang.c:scan_discrim_bound

Factor out common arithmetic operations for clarity.

gdb/ChangeLog:

	* ada-lang.c (scan_discrim_bound): Factor out arithmetic
	operations.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] S/390: Fix instruction format of crj*, clrj*, and clgrj*.
@ 2015-09-10 13:53 sergiodj+buildbot
  2015-09-11 14:35 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-09-10 13:53 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT be62444771a4a711300e2439fb1232415d9c835c ***

Author: Andreas Krebbel <krebbel@linux.vnet.ibm.com>
Branch: master
Commit: be62444771a4a711300e2439fb1232415d9c835c

S/390: Fix instruction format of crj*, clrj*, and clgrj*.

This fixes the instruction format for 3 of the compare and branch
extended mnemonics.  That way the extended mnemonics are actually
being found by objdump.

gas/testsuite/ChangeLog:

2015-09-10  Andreas Krebbel  <krebbel@linux.vnet.ibm.com>

	* gas/s390/zarch-z10.d: Fix testcase for some of the compare and
	branch extended mnemonics.

opcodes/ChangeLog:

2015-09-10  Andreas Krebbel  <krebbel@linux.vnet.ibm.com>

	* s390-opc.txt: Fix instruction format of crj*, clrj*, and clgrj*.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] S/390: Fix MASK_RIE_R0PI and MASK_RIE_R0PU.
@ 2015-09-10 13:38 sergiodj+buildbot
  2015-09-11 14:30 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-09-10 13:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9c1c2a0bb14ff5f74e68a7f1d67b8a7021c71cdf ***

Author: Andreas Krebbel <krebbel@linux.vnet.ibm.com>
Branch: master
Commit: 9c1c2a0bb14ff5f74e68a7f1d67b8a7021c71cdf

S/390: Fix MASK_RIE_R0PI and MASK_RIE_R0PU.

This makes objdump to be able to recognize some of the extended
mnemonics more often.  It does not lead to wrong being generated.

opcodes/ChangeLog:

2015-09-10  Andreas Krebbel  <krebbel@linux.vnet.ibm.com>

	* s390-opc.c: Fix MASK_RIE_R0PI and MASK_RIE_R0PU.

gas/testsuite/ChangeLog:

2015-09-10  Andreas Krebbel  <krebbel@linux.vnet.ibm.com>

	* gas/s390/zarch-z10.d: Fix testcase for compare and branch
	extended mnemonics.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Call target_can_download_tracepoint if there are tracepoints to download
@ 2015-09-10 11:45 sergiodj+buildbot
  2015-09-11  6:19 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-09-10 11:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT dd2e65cc2c48f2fe1343840b610bc6dd4246f35b ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: dd2e65cc2c48f2fe1343840b610bc6dd4246f35b

Call target_can_download_tracepoint if there are tracepoints to download

Nowadays, GDB calls target_can_download_tracepoint at the entry of
download_tracepoint_locations, which is called by.
update_global_location_list.  Sometimes, it is not needed to call
target_can_download_tracepoint at all because there is no tracepoint
created.  In remote target, target_can_download_tracepoint send
qTStatus to the remote in order to know whether tracepoint can be
downloaded or not.  This means some redundant qTStatus packets are
sent.

This patch is to teach GDB to call target_can_download_tracepoint
lazily, only on the moment there are tracepoint to download.
gdb.perf/single-step.exp (with a local patch to measure RSP packets)
shows the number of RSP packets is reduced because there is no
tracepoint at all, so GDB doesn't send qTStatus any more.

                       # of RSP packets
                       original  patched
single-step rsp 1000   7000      6000
single-step rsp 2000   14000     12000
single-step rsp 3000   21000     18000
single-step rsp 4000   28000     24000

gdb:

2015-09-10  Yao Qi  <yao.qi@linaro.org>

	* breakpoint.c (download_tracepoint_locations): New local
	can_download_tracepoint.  Check the result of
	target_can_download_tracepoint and save it in
	can_download_tracepoint if there are tracepoints to download.
	* linux-nat.h (enum tribool): Move it to ...
	* common/common-types.h: ... here.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Garbage collect thread continuations
@ 2015-09-09 19:44 sergiodj+buildbot
  2015-09-10 15:03 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-09-09 19:44 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a85a3079233ddf4c5537ec90c03d3394b93ef355 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: a85a3079233ddf4c5537ec90c03d3394b93ef355

Garbage collect thread continuations

Nothing uses thread continuations anymore.

(inferior continuations are still used by the attach command.)

gdb/ChangeLog:
2015-09-09  Pedro Alves  <palves@redhat.com>

	* continuations.c (add_continuation, restore_thread_cleanup)
	(do_all_continuations_ptid, do_all_continuations_thread_callback)
	(do_all_continuations_thread, do_all_continuations)
	(discard_all_continuations_thread_callback)
	(discard_all_continuations_thread, discard_all_continuations)
	(add_intermediate_continuation)
	(do_all_intermediate_continuations_thread_callback)
	(do_all_intermediate_continuations_thread)
	(do_all_intermediate_continuations)
	(discard_all_intermediate_continuations_thread_callback)
	(discard_all_intermediate_continuations_thread)
	(discard_all_intermediate_continuations): Delete.
	* continuations.h (add_continuation, do_all_continuations)
	(do_all_continuations_thread, discard_all_continuations)
	(discard_all_continuations_thread, add_intermediate_continuation)
	(do_all_intermediate_continuations)
	(do_all_intermediate_continuations_thread)
	(discard_all_intermediate_continuations)
	(discard_all_intermediate_continuations_thread): Delete
	declarations.
	* event-top.c (stdin_event_handler): Delete references to
	continuations.
	* gdbthread.h (struct thread_info): Delete continuations and
	intermediate_continuations fields.
	* inf-loop.c (inferior_event_handler): Remove references to
	continuations.
	* infrun.c (infrun_thread_stop_requested_callback): Remove
	references to continuations.
	* target.h (enum inferior_event_type) <INF_EXEC_CONTINUE>: Delete.
	* thread.c: Don't include "continuations.h".
	(clear_thread_inferior_resources): Remove references to
	continuations.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] * gdb.python/py-prettyprint.exp: Check result of run_lang_tests.
@ 2015-09-09 18:53 sergiodj+buildbot
  2015-09-11  1:41 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-09-09 18:53 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e70b6e8eee4fc1ad1270a63ad000d11fd657d7a7 ***

Author: Doug Evans <dje@google.com>
Branch: master
Commit: e70b6e8eee4fc1ad1270a63ad000d11fd657d7a7

* gdb.python/py-prettyprint.exp: Check result of run_lang_tests.

gdb/testsuite/ChangeLog:

	* gdb.python/py-prettyprint.exp: Check result of run_lang_tests.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] * gdb.base/savedregs.exp: Fix typo.
@ 2015-09-09 18:32 sergiodj+buildbot
  2015-09-10 20:16 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-09-09 18:32 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4c666f844a4481749c60f4f1ba6cfc8efd3a4eee ***

Author: Doug Evans <dje@google.com>
Branch: master
Commit: 4c666f844a4481749c60f4f1ba6cfc8efd3a4eee

* gdb.base/savedregs.exp: Fix typo.

gdb/testsuite/ChangeLog:

	* gdb.base/savedregs.exp: Fix typo.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Delete enum inferior_event_handler::INF_TIMER
@ 2015-09-09 18:25 sergiodj+buildbot
  2015-09-10 17:56 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-09-09 18:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cfe7570334fc9aefc64bdb0791fec03a736f2851 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: cfe7570334fc9aefc64bdb0791fec03a736f2851

Delete enum inferior_event_handler::INF_TIMER

Nothing ever uses this.

gdb/ChangeLog:
2015-09-09  Pedro Alves  <palves@redhat.com>

	* inf-loop.c (inferior_event_handler): Delete INF_TIMER case.
	* target.h (enum inferior_event_type) <INF_TIMER>: Delete.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Garbage collect dummy_frame_ctx_saver
@ 2015-09-09 18:10 sergiodj+buildbot
  2015-09-10 12:59 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-09-09 18:10 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0700e23e5f73b2a498526a79de34217429b44988 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 0700e23e5f73b2a498526a79de34217429b44988

Garbage collect dummy_frame_ctx_saver

Since the "finish" command and infcall's FSMs are now responsible for
saving the return value, the dummy_frame_ctx_saver is no longer needed
anywhere.

gdb/ChangeLog:
2015-09-09  Pedro Alves  <palves@redhat.com>

	* infcall.c (struct dummy_frame_context_saver): Delete.
	(dummy_frame_context_saver_free, dummy_frame_context_saver_dtor)
	(dummy_frame_context_saver_drop)
	(dummy_frame_context_saver_cleanup)
	(dummy_frame_context_saver_get_regs)
	(dummy_frame_context_saver_setup): Delete.
	* infcall.h (dummy_frame_context_saver_drop)
	(dummy_frame_context_saver_cleanup)
	(dummy_frame_context_saver_get_regs, dummy_frame_context_saver):
	Delete.
	(get_return_value): Remove 'ctx_saver' paremeter.  Adjust.
	* inferior.h (get_return_value): Remove 'ctx_saver' paremeter.
	* python/py-finishbreakpoint.c (bpfinishpy_pre_stop_hook): Adjust.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Convert the until/advance commands to thread_fsm mechanism
@ 2015-09-09 18:03 sergiodj+buildbot
  2015-09-10 11:01 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-09-09 18:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cfc3163382898a537c742bee1bf8240b3c09df35 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: cfc3163382898a537c742bee1bf8240b3c09df35

Convert the until/advance commands to thread_fsm mechanism

gdb/ChangeLog:
2015-09-09  Pedro Alves  <palves@redhat.com>

	* breakpoint.c: Include "thread-fsm.h".
	(struct until_break_command_continuation_args): Delete.
	(struct until_break_fsm): New.
	(until_break_fsm_ops): New global.
	(new_until_break_fsm, until_break_fsm_should_stop): New functions.
	(until_break_command_continuation): Delete.
	(until_break_fsm_clean_up): New function.
	(until_break_fsm_async_reply_reason): New function.
	(until_break_command): Adjust to create an until_break_fsm instead
	of a continuation.
	(momentary_bkpt_print_it): No longer print MI's async-stop-reason
	here.
	* infcmd.c (struct until_next_fsm): New.
	(until_next_fsm_ops): New global.
	(new_until_next_fsm, until_next_fsm_should_stop): New function.
	(until_next_continuation): Delete.
	(until_next_fsm_clean_up, until_next_fsm_async_reply_reason): New
	functions.
	(until_next_command): Adjust to create a new until_next_fsm
	instead of a continuation.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Convert infcalls to thread_fsm mechanism
@ 2015-09-09 17:56 sergiodj+buildbot
  2015-09-10  8:09 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-09-09 17:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 388a708404618466bbe51b7198de7a64f0a5da9f ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 388a708404618466bbe51b7198de7a64f0a5da9f

Convert infcalls to thread_fsm mechanism

This removes infcall-specific special casing from normal_stop,
simplifying it.

Like the "finish" command's, the FSM is responsible for storing the
function's return value.

gdb/ChangeLog:
2015-09-09  Pedro Alves  <palves@redhat.com>

	* infcall.c: Include thread_fsm.h.
	(struct call_return_meta_info): New.
	(get_call_return_value): New function, factored out from
	call_function_by_hand_dummy.
	(struct call_thread_fsm): New.
	(call_thread_fsm_ops): New global.
	(new_call_thread_fsm, call_thread_fsm_should_stop)
	(call_thread_fsm_should_notify_stop): New functions.
	(run_inferior_call): Add 'sm' parameter.  Associate the FSM with
	the thread.
	(call_function_by_hand_dummy): Create a new call_thread_fsm
	instance, associate it with the thread, and wait for the FSM to
	finish.  If finished successfully, fetch the function's result
	value out of the FSM.
	* infrun.c (fetch_inferior_event): If the FSM says the stop
	shouldn't be notified, don't call normal_stop.
	(maybe_remove_breakpoints): New function, factored out from ...
	(normal_stop): ... here.  Simplify.
	* infrun.h (maybe_remove_breakpoints): Declare.
	* thread-fsm.c (thread_fsm_should_notify_stop): New function.
	(thread-fsm.h) <struct thread_fsm_ops>: New field.
	(thread_fsm_should_notify_stop): Declare.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Replace "struct continuation" mechanism by something more extensible
@ 2015-09-09 17:48 sergiodj+buildbot
  2015-09-10  5:57 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-09-09 17:48 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 243a925328f8e3184b2356bee497181049c0174f ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 243a925328f8e3184b2356bee497181049c0174f

Replace "struct continuation" mechanism by something more extensible

This adds an object oriented replacement for the "struct continuation"
mechanism, and converts the stepping commands (step, next, stepi,
nexti) and the "finish" commands to use it.

It adds a new thread "class" (struct thread_fsm) that contains the
necessary info and callbacks to manage the state machine of a thread's
execution command.

This allows getting rid of some hacks.  E.g., in fetch_inferior_event
and normal_stop we no longer need to know whether a thread is doing a
multi-step (e.g., step N).  This effectively makes the
intermediate_continuations unused -- they'll be garbage collected in a
separate patch.  (They were never a proper abstraction, IMO.  See how
fetch_inferior_event needs to check step_multi before knowing whether
to call INF_EXEC_CONTINUE or INF_EXEC_COMPLETE.)

The target async vs !async uiout hacks in mi_on_normal_stop go away
too.

print_stop_event is no longer called from normal_stop.  Instead it is
now called from within each interpreter's normal_stop observer.  This
clears the path to make each interpreter print a stop event the way it
sees fit.  Currently we have some hacks in common code to
differenciate CLI vs TUI vs MI around this area.

The "finish" command's FSM class stores the return value plus that
value's position in the value history, so that those can be printed to
both MI and CLI's streams.  This fixes the CLI "finish" command when
run from MI -- it now also includes the function's return value in the
CLI stream:

  (gdb)
  ~"callee3 (strarg=0x400730 \"A string argument.\") at src/gdb/testsuite/gdb.mi/basics.c:35\n"
  ~"35\t}\n"
 +~"Value returned is $1 = 0\n"
  *stopped,reason="function-finished",frame=...,gdb-result-var="$1",return-value="0",thread-id="1",stopped-threads="all",core="0"
 -FAIL: gdb.mi/mi-cli.exp: CLI finish: check CLI output
 +PASS: gdb.mi/mi-cli.exp: CLI finish: check CLI output

gdb/ChangeLog:
2015-09-09  Pedro Alves  <palves@redhat.com>

	* Makefile.in (COMMON_OBS): Add thread-fsm.o.
	* breakpoint.c (handle_jit_event): Print debug output.
	(bpstat_what): Split event callback handling to ...
	(bpstat_run_callbacks): ... this new function.
	(momentary_bkpt_print_it): No longer handle bp_finish here.
	* breakpoint.h (bpstat_run_callbacks): Declare.
	* gdbthread.h (struct thread_info) <step_multi>: Delete field.
	<thread_fsm>: New field.
	(thread_cancel_execution_command): Declare.
	* infcmd.c: Include thread-fsm.h.
	(struct step_command_fsm): New.
	(step_command_fsm_ops): New global.
	(new_step_command_fsm, step_command_fsm_prepare): New functions.
	(step_1): Adjust to use step_command_fsm_prepare and
	prepare_one_step.
	(struct step_1_continuation_args): Delete.
	(step_1_continuation): Delete.
	(step_command_fsm_should_stop): New function.
	(step_once): Delete.
	(step_command_fsm_clean_up, step_command_fsm_async_reply_reason)
	(prepare_one_step): New function, based on step_once.
	(until_next_command): Remove step_multi reference.
	(struct return_value_info): New.
	(print_return_value): Rename to ...
	(print_return_value_1): ... this.  New struct return_value_info
	parameter.  Adjust.
	(print_return_value): Reimplement as wrapper around
	print_return_value_1.
	(struct finish_command_fsm): New.
	(finish_command_continuation): Delete.
	(finish_command_fsm_ops): New global.
	(new_finish_command_fsm, finish_command_fsm_should_stop): New
	functions.
	(finish_command_fsm_clean_up, finish_command_fsm_return_value):
	New.
	(finish_command_continuation_free_arg): Delete.
	(finish_command_fsm_async_reply_reason): New.
	(finish_backward, finish_forward): Change symbol parameter to a
	finish_command_fsm.  Adjust.
	(finish_command): Create a finish_command_fsm.  Adjust.
	* infrun.c: Include "thread-fsm.h".
	(clear_proceed_status_thread): Delete the thread's FSM.
	(infrun_thread_stop_requested_callback): Cancel the thread's
	execution command.
	(clean_up_just_stopped_threads_fsms): New function.
	(fetch_inferior_event): Handle the event_thread's should_stop
	method saying the command isn't done yet.
	(process_event_stop_test): Run breakpoint callbacks here.
	(print_stop_event): Rename to ...
	(print_stop_location): ... this.
	(restore_current_uiout_cleanup): New function.
	(print_stop_event): Reimplement.
	(normal_stop): No longer notify the end_stepping_range observers
	here handle "step N" nor "finish" here.  No longer call
	print_stop_event here.
	* infrun.h (struct return_value_info): Forward declare.
	(print_return_value): Declare.
	(print_stop_event): Change prototype.
	* thread-fsm.c: New file.
	* thread-fsm.h: New file.
	* thread.c: Include "thread-fsm.h".
	(thread_cancel_execution_command): New function.
	(clear_thread_inferior_resources): Call it.
	* cli/cli-interp.c (cli_on_normal_stop): New function.
	(cli_interpreter_init): Install cli_on_normal_stop as normal_stop
	observer.
	* mi/mi-interp.c: Include "thread-fsm.h".
	(restore_current_uiout_cleanup): Delete.
	(mi_on_normal_stop): If the thread has an FSM associated, and it
	finished, ask it for the async-reply-reason to print.  Always call
	print_stop_event here, regardless of the top-level interpreter.
	Check bpstat_what to tell whether an asynchronous breakpoint hit
	triggered.
	* tui/tui-interp.c (tui_on_normal_stop): New function.
	(tui_init): Install tui_on_normal_stop as normal_stop observer.

gdb/testsuite/ChangeLog:
2015-09-09  Pedro Alves  <palves@redhat.com>

	* gdb.mi/mi-cli.exp: Add CLI finish tests.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [AArch64] Sort IS_AARCH64_TLS_RELAX_RELOC in alphabetic order
@ 2015-09-09 13:36 sergiodj+buildbot
  2015-09-09 21:38 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-09-09 13:36 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4af68b9c78aad1b82bfd6e2e960747eb160bb4d8 ***

Author: Jiong Wang <jiong.wang@arm.com>
Branch: master
Commit: 4af68b9c78aad1b82bfd6e2e960747eb160bb4d8

[AArch64] Sort IS_AARCH64_TLS_RELAX_RELOC in alphabetic order

This can also speedup the check as TLSDESC is the default model for
global/local dynamic that the big "||" check can finish more quickly
than putting them at the bottom.

2015-09-09  Jiong. Wang  <jiong.wang@arm.com>

bfd/
  * elfnn-aarch64.c (IS_AARCH64_TLS_RELAX_RELOC): Sort alphabetically.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] S/390: Remove trailing zeros on 4-bytes opcodes.
@ 2015-09-09 12:30 sergiodj+buildbot
  2015-09-09 16:01 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-09-09 12:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d660d56578248bf3bb56150295cecc763f112061 ***

Author: Andreas Krebbel <krebbel@linux.vnet.ibm.com>
Branch: master
Commit: d660d56578248bf3bb56150295cecc763f112061

S/390: Remove trailing zeros on 4-bytes opcodes.

This is a NOP change only relevant when reading the file or parsing it
with other tools.

opcodes/ChangeLog:

2015-09-09  Andreas Krebbel  <krebbel@linux.vnet.ibm.com>

	* s390-opc.c: Add OP32 definition.
	* s390-opc.txt: Reduce the opcode padding of some extended
	mnemonics from 6 to the actual length (which is 4).


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] S/390: Fix opcode of ppno.
@ 2015-09-09 12:23 sergiodj+buildbot
  2015-09-09 13:56 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-09-09 12:23 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c694bafc0bc795a63e607689cc35ad44047790e6 ***

Author: Andreas Krebbel <krebbel@linux.vnet.ibm.com>
Branch: master
Commit: c694bafc0bc795a63e607689cc35ad44047790e6

S/390: Fix opcode of ppno.

opcodes/ChangeLog:

2015-09-09  Andreas Krebbel  <krebbel@linux.vnet.ibm.com>

	* s390-opc.txt: Fix opcode of ppno instruction.

gas/testsuite/ChangeLog:

2015-09-09  Andreas Krebbel  <krebbel@linux.vnet.ibm.com>

	* gas/s390/zarch-z13.d: Fix opcode of ppno instruction.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Improve hand-call-in-threads.exp failure handling.
@ 2015-09-09  2:59 sergiodj+buildbot
  2015-09-09  5:11 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-09-09  2:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c0fa8fbd1c2f02921b90083e595a8452d3d51ba2 ***

Author: Sandra Loosemore <sandra@codesourcery.com>
Branch: master
Commit: c0fa8fbd1c2f02921b90083e595a8452d3d51ba2

Improve hand-call-in-threads.exp failure handling.

2015-09-08  Sandra Loosemore  <sandra@codesourcery.com>

	gdb/testsuite/
	* gdb.threads/hand-call-in-threads.exp: Make sure the thread
	command actually switches threads.  Give up on remaining
	tests if target fails to stop at breakpoint.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] gdb/tui: Remove casts of NULL during assignment.
@ 2015-09-04 16:27 sergiodj+buildbot
  2015-09-05  0:45 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-09-04 16:27 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e65b52456bc3f60a176fece5e34e420c5a75bd16 ***

Author: Andrew Burgess <andrew.burgess@embecosm.com>
Branch: master
Commit: e65b52456bc3f60a176fece5e34e420c5a75bd16

gdb/tui: Remove casts of NULL during assignment.

In the following code:

    struct symbol *wsym = (struct symbol *) NULL;

the cast of NULL is redundant, it adds noise, and is just one more thing
to change if the type of wsym ever changes.  There are a relatively
small number of places in gdb where the above code pattern is used.
Usually the cast is removed like this:

    struct symbol *wsym = NULL;

This commit updates all the places within the gdb/tui directory where we
cast NULL during assignment, removing the cast.

gdb/ChangeLog:

	* tui/tui-data.c (win_with_focus): Remove cast of NULL pointer.
	(tui_next_win): Likewise.
	(tui_prev_win): Likewise.
	(tui_partial_win_by_name): Likewise.
	(tui_init_generic_part): Likewise.
	(init_content_element): Likewise.
	(tui_del_window): Likewise.
	(tui_free_window): Likewise.
	(tui_del_data_windows): Likewise.
	(tui_free_data_content): Likewise.
	* tui/tui-layout.c (make_source_or_disasm_window): Likewise.
	* tui/tui-regs.c (tui_show_register_group): Likewise.
	* tui/tui-win.c (tui_resize_all): Likewise.
	(tui_set_focus): Likewise.
	(tui_set_win_height): Likewise.
	(make_invisible_and_set_new_height): Likewise.
	* tui/tui-windata.c (tui_delete_data_content_windows): Likewise.
	* tui/tui-wingeneral.c (make_visible): Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] gdb/cli: Remove casts of NULL during assignment.
@ 2015-09-04 16:19 sergiodj+buildbot
  2015-09-04 22:17 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-09-04 16:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b03e6ad9cd2064214c0fbff179c7e47c855315e3 ***

Author: Andrew Burgess <andrew.burgess@embecosm.com>
Branch: master
Commit: b03e6ad9cd2064214c0fbff179c7e47c855315e3

gdb/cli: Remove casts of NULL during assignment.

In the following code:

    struct symbol *wsym = (struct symbol *) NULL;

the cast of NULL is redundant, it adds noise, and is just one more thing
to change if the type of wsym ever changes.  There are a relatively
small number of places in gdb where the above code pattern is used.
Usually the cast is removed like this:

    struct symbol *wsym = NULL;

This commit updates all the places within the gdb/cli directory where we
cast NULL during assignment, removing the cast.

gdb/ChangeLog:

	* cli/cli-decode.c (find_cmd): Remove cast of NULL pointer.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] gdb: Remove casts of NULL during assignment.
@ 2015-09-04 16:05 sergiodj+buildbot
  2015-09-04 19:43 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-09-04 16:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT be9033582599e50521feb879d7476756c2c8c017 ***

Author: Andrew Burgess <andrew.burgess@embecosm.com>
Branch: master
Commit: be9033582599e50521feb879d7476756c2c8c017

gdb: Remove casts of NULL during assignment.

In the following code:

    struct symbol *wsym = (struct symbol *) NULL;

the cast of NULL is redundant, it adds noise, and is just one more thing
to change if the type of wsym ever changes.  There are a relatively
small number of places in gdb where the above code pattern is used.
Usually the cast is removed like this:

    struct symbol *wsym = NULL;

This commit updates all the places within the gdb/ directory where we
cast NULL during assignment, removing the cast.

gdb/ChangeLog:

	* c-valprint.c (print_unpacked_pointer): Remove cast of NULL
	pointer.
	* dbxread.c (dbx_end_psymtab): Likewise.
	* gnu-nat.c (gnu_write_inferior): Likewise.
	* mdebugread.c (cross_ref): Likewise.
	* p-valprint.c (pascal_val_print): Likewise.
	* xcoffread.c (xcoff_end_psymtab): Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Mention multi-arch debugging support in NEWS
@ 2015-09-04 14:38 sergiodj+buildbot
  2015-09-04 16:22 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-09-04 14:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 02f024f9a527012938e978c233fef39f439a5013 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 02f024f9a527012938e978c233fef39f439a5013

Mention multi-arch debugging support in NEWS

gdb:

2015-09-04  Yao Qi  <yao.qi@linaro.org>

	* NEWS: Mention the aarch64 multi-arch debugging support.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [Ada] Make string_char_type a true TYPE_CODE_CHAR type in Ada
@ 2015-09-03 16:02 sergiodj+buildbot
  2015-09-03 18:27 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-09-03 16:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cd7c1778e72ce29f7f42d91ab08ae855c7ef8f7a ***

Author: Pierre-Marie de Rodat <derodat@adacore.com>
Branch: master
Commit: cd7c1778e72ce29f7f42d91ab08ae855c7ef8f7a

[Ada] Make string_char_type a true TYPE_CODE_CHAR type in Ada

Before this change, trying to call an overloaded function with at least
one character literal in argument would fail.  For instance, given these
two functions:

   function F (C : Character) return Integer is
   begin
      return Character'Pos (C);
   end F;

   function F (I : Integer) return Integer is
   begin
      return -I;
   end F;

We would get the following GDB session:

    (gdb) p f('A')
    $1 = -65
    (gdb) p f(1)
    $1 = -1

This is wrong because the first call should select the first F function
and thus return 65.

The root problem is that ada-lang.c:ada_language_arch_info stores in
string_char_type a type whose code is TYPE_CODE_INT instead of
TYPE_CODE_CHAR.  As a result, all parsed character literals are turned
into integer values and during overload matching, the TYPE_CODE_CHAR
formal rejects the TYPE_CODE_INT actual.

This change turns string_char_type into a true TYPE_CODE_CHAR type in
ada-lang.c so that we have instead the expected:

    (gdb) p f('A')
    $1 = 65

gdb/ChangeLog:

	* ada-lang.c (ada_language_arch_info): Create a TYPE_CODE_CHAR
	type instead of a TYPE_CODE_INT one for the string_char_type
	and the ada_primitive_type_char types.

gdb/testsuite/ChangeLog:

	* gdb.ada/funcall_char.exp: New testcase.
	* gdb.ada/funcall_char/foo.adb: New file.

Tested on x86_64-linux, no regression.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [aarch64] Check region OK for HW watchpoint in GDBserver
@ 2015-09-03 13:32 sergiodj+buildbot
  2015-09-03 15:10 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-09-03 13:32 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 39edd165f42176f8c1d40e08d63f344f10241870 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 39edd165f42176f8c1d40e08d63f344f10241870

[aarch64] Check region OK for HW watchpoint in GDBserver

Nowadays, if user requests HW watchpoint to monitor a large memory area
or unaligned area, aarch64 GDB will split into multiple aligned areas,
and use multiple debugging registers to watch them.  However, the
registers are not updated in a transaction way.  GDBserver doesn't revert
updates in previous iterations if some debugging registers fail to update
due to some reason, like no free debugging registers available, in the
latter iteration.  For example, if we have a char buf[34], and watch buf
in gdb,

(gdb) watch buf
Hardware watchpoint 2: buf
(gdb) c
Continuing.
infrun: clear_proceed_status_thread (Thread 13466)
infrun: proceed (addr=0xffffffffffffffff, signal=GDB_SIGNAL_DEFAULT)
infrun: step-over queue now empty
infrun: resuming [Thread 13466] for step-over
Sending packet: $m410838,22#35...Packet received: 00000000000000000000000000000000000000000000000000000000000000000000
infrun: skipping breakpoint: stepping past insn at: 0x400524
infrun: skipping breakpoint: stepping past insn at: 0x400524
Sending packet: $Z2,410838,22#80...Packet received: E01 <----- [1]
Packet Z2 (write-watchpoint) is supported
Sending packet: $Z0,7fb7fe0a8c,4#43...Packet received: OK
Warning:
Could not insert hardware watchpoint 2.
Could not insert hardware breakpoints:
You may have requested too many hardware breakpoints/watchpoints.

GDB receives E01 for Z2 packet [1] but GDBserver updates the debugging
register status,

insert_point (addr=0x00410838, len=34, type=hw-write-watchpoint):
	BREAKPOINTs:
	BP0: addr=0x0, ctrl=0x00000000, ref.count=0
	BP1: addr=0x0, ctrl=0x00000000, ref.count=0
	BP2: addr=0x0, ctrl=0x00000000, ref.count=0
	BP3: addr=0x0, ctrl=0x00000000, ref.count=0
	BP4: addr=0x0, ctrl=0x00000000, ref.count=0
	BP5: addr=0x0, ctrl=0x00000000, ref.count=0
	WATCHPOINTs:
	WP0: addr=0x410850, ctrl=0x00001ff5, ref.count=1
	WP1: addr=0x410848, ctrl=0x00001ff5, ref.count=1
	WP2: addr=0x410840, ctrl=0x00001ff5, ref.count=1
	WP3: addr=0x410838, ctrl=0x00001ff5, ref.count=1

four debugging registers can not monitor 34-byte long area, so the last
iteration of updating debugging register state fails but previous
iterations succeed.  This makes GDB think no HW watchpoint is inserted
but some debugging registers are used.

This problem was exposed by "watch buf" gdb.base/watchpoint.exp with
aarch64 GDBserver debugging arm 32-bit program.  The buf is 30-byte long
but 4-byte aligned, and four debugging registers can't cover 34-byte
(extend 4 bytes to be 8-byte aligned) area.  However, this problem
does exist on non-multi-arch debugging scenario as well.

This patch moves code in aarch64_linux_region_ok_for_hw_watchpoint to
aarch64_linux_region_ok_for_watchpoint in nat/aarch64-linux-hw-point.c.
Then, checks with aarch64_linux_region_ok_for_watchpoint, like what we
are doing in GDB.  If the region is OK, call aarch64_handle_watchpoint.

Regression tested on aarch64 with both 64-bit program and 32-bit
program.  Some fails in gdb.base/watchpoint.exp are fixed.

gdb:

2015-09-03  Yao Qi  <yao.qi@linaro.org>

	* aarch64-linux-nat.c (aarch64_linux_region_ok_for_hw_watchpoint):
	Move code to aarch64_linux_region_ok_for_watchpoint.  Call
	aarch64_linux_region_ok_for_watchpoint.
	* nat/aarch64-linux-hw-point.c (aarch64_linux_region_ok_for_watchpoint):
	New function.
	* nat/aarch64-linux-hw-point.h (aarch64_linux_region_ok_for_watchpoint):
	Declare it.

gdb/gdbserver:

2015-09-03  Yao Qi  <yao.qi@linaro.org>

	* linux-aarch64-low.c (aarch64_insert_point): Call
	aarch64_handle_watchpoint if aarch64_linux_region_ok_for_watchpoint
	returns true.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Update documentation of function copy_type_recursive
@ 2015-09-03  1:11 sergiodj+buildbot
  2015-09-03  4:55 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-09-03  1:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT eed8b28a07c32f835dfb4ff21fb9c0bf33c738df ***

Author: Patrick Palka <patrick@parcs.ath.cx>
Branch: master
Commit: eed8b28a07c32f835dfb4ff21fb9c0bf33c738df

Update documentation of function copy_type_recursive

Following commit 8f57eec2fb3 ("Use gdbarch obstack to allocate types in
alloc_type_arch") it is no longer the case that the type returned by
copy_type_recursive is allocated using malloc.  Because the function
uses alloc_type_arch internally, the new type is now allocated on the
gdbarch associated with the type, and is thus owned by that gdbarch.

gdb/ChangeLog:

	* gdbtypes.c (copy_type_recursive): Update documentation.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Rename R_386_irelative to R_386_ext2
@ 2015-09-02 12:24 sergiodj+buildbot
  2015-09-02 13:23 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-09-02 12:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c74be520ba8ed2d013d43916b923b837294343cc ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: c74be520ba8ed2d013d43916b923b837294343cc

Rename R_386_irelative to R_386_ext2

	* elf32-i386.c (R_386_irelative): Renamed to ...
	(R_386_ext2): This.
	(R_386_vt_offset): Updated.
	(elf_i386_rtype_to_howto): Likewise.
	(elf_i386_relocate_section): Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Initialize yet another variable to silence GCC warning from last-but-one commit
@ 2015-09-02  5:54 sergiodj+buildbot
  2015-09-02  9:37 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-09-02  5:54 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 73c6b4756a7cee53c274ed05fddcd079b8b7e57c ***

Author: Sergio Durigan Junior <sergiodj@redhat.com>
Branch: master
Commit: 73c6b4756a7cee53c274ed05fddcd079b8b7e57c

Initialize yet another variable to silence GCC warning from last-but-one commit

Yet another BuildBot e-mail, yet another breakage on RHEL-7.1 s390x
(which uses an older GCC).  This time,
solib-svr4.c:solib_event_probe_action has the probe_argc variable,
which is now inside a TRY..CATCH and therefore needs to be
initialized.  Pushed as obvious.

gdb/ChangeLog:
2015-09-01  Sergio Durigan Junior  <sergiodj@redhat.com>

	* solib-svr4.c (solib_event_probe_action): Initialize 'probe_argc'
	as zero.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Initialize variable and silence GCC warning from last commit
@ 2015-09-02  4:42 sergiodj+buildbot
  2015-09-02  7:42 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-09-02  4:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ad1c917a79e8c5aa67657f148415c1bee01b240f ***

Author: Sergio Durigan Junior <sergiodj@redhat.com>
Branch: master
Commit: ad1c917a79e8c5aa67657f148415c1bee01b240f

Initialize variable and silence GCC warning from last commit

BuildBot e-mailed me to let me know that my last commit broke GDB on
RHEL-7.1 s390x.  On solib-svr4.c:svr4_handle_solib_event, 'val' now
needs to be initialized as NULL because it is inside a TRY..CATCH
block.  This patch does that.  Pushed as obvious.

gdb/ChangeLog:
2015-09-01  Sergio Durigan Junior  <sergiodj@redhat.com>

	* solib-svr4.c (svr4_handle_solib_event): Initialize 'val' as NULL


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Catching errors on probes-based dynamic linker interface
@ 2015-09-02  4:28 sergiodj+buildbot
  2015-09-02  6:57 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-09-02  4:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3bd7e5b7ee5ea0b3bbb4030ca841f66faad74f0f ***

Author: Sergio Durigan Junior <sergiodj@redhat.com>
Branch: master
Commit: 3bd7e5b7ee5ea0b3bbb4030ca841f66faad74f0f

Catching errors on probes-based dynamic linker interface

This patch is intended to make the interaction between the
probes-based dynamic linker interface and the SystemTap SDT probe code
on GDB more robust.  It does that by wrapping the calls to the probe
API with TRY...CATCH'es, so that any exception thrown will be caught
and handled properly.

The idea for this patch came from
<https://bugzilla.redhat.com/show_bug.cgi?id=1196181>, which is a bug
initially filed against Fedora GDB (but now under Fedora GLIBC).  This
bug happens on armhfp (although it could happen on other targets as
well), and is triggered because GCC generates a strange argument for
one of the probes used by GDB in the dynamic linker interface.  As can
be seen in the bug, this argument is "-4@.L1052".

I don't want to discuss the reasons for this argument to be there
(this discussion belongs to the bug, or to another thread), but GDB
could definitely do a better error handling here.  Currently, one sees
the following message when there is an error in the probes-based
dynamic linker interface:

  (gdb) run
  Starting program: /bin/inferior
  warning: Probes-based dynamic linker interface failed.
  Reverting to original interface.

  Cannot parse expression `.L976 4@r4'.
  (gdb)

Which means that one needs to explicitly issue a "continue" command to
make GDB continue running the inferior, even though this error is not
fatal and GDB will fallback to the old interface automatically.

This is where this patch helps: it makes GDB still print the necessary
warnings or error messages, but it *also* does not stop the inferior
unnecessarily.

I have tested this patch on the systems where this error happens, but
I could not come up with a way to create a testcase for it.
Nevertheless, it should be straightforward to see that this patch does
improve the current situation.

gdb/ChangeLog:
2015-09-01  Sergio Durigan Junior  <sergiodj@redhat.com>

	* solib-svr4.c (solib_event_probe_action): Call
	get_probe_argument_count using TRY...CATCH.
	(svr4_handle_solib_event): Likewise, for evaluate_probe_argument.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [Ada] Fix completion for multiple function matches
@ 2015-09-01 13:04 sergiodj+buildbot
  2015-09-01 17:00 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-09-01 13:04 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT dc5c874652de144c5ab05d11e85013b568678039 ***

Author: Pierre-Marie de Rodat <derodat@adacore.com>
Branch: master
Commit: dc5c874652de144c5ab05d11e85013b568678039

[Ada] Fix completion for multiple function matches

Before this change, trying to complete an expression ending with an
ambiguous function name (i.e. for which there are multiple matches)
would display a menu with a prompt for the user to pick one. For
instance:

    (gdb) p func<tab>Multiple matches for func
    [0] cancel
    [1] pack2.func at pack2.adb:5
    [2] pack.func at pack.adb:5
    >

This is not user friendly and actually triggered a segmentation fault
after the user did pick one. It is not clear whether the segmentation
fault needs a separate fix, but this is the only known case which
exhibits it at the moment, and this case must be fixed itself.

The problem lies in ada-lang.c (ada_resolve_function): when we got
multiple matches, we should not display the menu if we are in completion
mode. This patch adjusts the corresponding condition accordingly.

gdb/ChangeLog:

	* ada-lang.c (ada_resolve_function): Do not ask the user what
	match to use when in completion mode.

gdb/testsuite/ChangeLog:

	* gdb.ada/complete.exp: Add "pck.ambiguous_func" to the relevant
	expected outputs.  Add two testcases for completing ambiguous
	functions.
	* gdb.ada/complete/aux_pck.adb: New file.
	* gdb.ada/complete/aux_pck.ads: New file.
	* gdb.ada/complete/foo.adb: Pull Aux_Pck and call the two
	Ambiguous_Func functions.
	* gdb.ada/complete/pck.ads: Add an Ambiguous_Func function.
	* gdb.ada/complete/pck.adb: Likewise.

Tested on x86_64-linux, no regression.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Skip PLT for function pointer initialization
@ 2015-09-01 12:28 sergiodj+buildbot
  2015-09-01 14:33 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-09-01 12:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 04ebc307f9601168c165fb63aa39a676e45454b7 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 04ebc307f9601168c165fb63aa39a676e45454b7

Skip PLT for function pointer initialization

We use its PLT entry to initialize function pointer at run-time.  If
there is no other usage for the PLT entry, we can generate run-time
function pointer relocations in read-write section, which can be
resolved by dynamic linker, to initialize function pointers.  It avoids
the extra indirect branch overhead in PLT.

bfd/

	PR ld/18900
	* elf32-i386.c (elf_i386_link_hash_entry): Add
	func_pointer_refcount.
	(elf_i386_link_hash_newfunc): Clear func_pointer_refcount.
	(elf_i386_get_local_sym_hash): Likewise.
	(elf_i386_copy_indirect_symbol): Also copy
	func_pointer_refcount.
	(elf_i386_check_relocs): Increment func_pointer_refcount.
	(elf_i386_gc_sweep_hook): Decrement func_pointer_refcount.
	(elf_i386_allocate_dynrelocs): Don't create the PLT entry if
	there are only function pointer relocations which can be
	resolved at run-time.  Keep dynanamic relocations for run-time
	function pointer initialization.
	(elf_i386_relocate_section): Copy dynamic function pointer
	relocations.
	* elf64-x86-64.c (elf_x86_64_link_hash_entry): Add
	func_pointer_refcount.
	(elf_x86_64_link_hash_newfunc): Clear func_pointer_refcount.
	(elf_x86_64_get_local_sym_hash): Likewise.
	(elf_x86_64_copy_indirect_symbol): Also copy
	func_pointer_refcount.
	(elf_x86_64_check_relocs): Increment func_pointer_refcount.
	(elf_x86_64_gc_sweep_hook): Decrement func_pointer_refcount.
	(elf_x86_64_allocate_dynrelocs): Don't create the PLT entry if
	there are only function pointer relocations which can be
	resolved at run-time.  Keep dynanamic relocations for run-time
	function pointer initialization.
	(elf_x86_64_relocate_section): Copy dynamic function pointer
	relocations.

ld/testsuite/

	PR ld/18900
	* ld-i386/i386.exp: Run tests for PR ld/18900.
	* ld-x86-64/x86-64.exp: Likewise.
	* ld-i386/pr18900.out: New file.
	* ld-i386/pr18900a.c: Likewise.
	* ld-i386/pr18900a.c: Likewise.
	* ld-i386/pr18900a.rd: Likewise.
	* ld-i386/pr18900b.c: Likewise.
	* ld-i386/pr18900b.rd: Likewise.
	* ld-i386/pr18900c.c: Likewise.
	* ld-x86-64/pr18900.out: Likewise.
	* ld-x86-64/pr18900a.c: Likewise.
	* ld-x86-64/pr18900a.rd: Likewise.
	* ld-x86-64/pr18900b.c: Likewise.
	* ld-x86-64/pr18900b.rd: Likewise.
	* ld-x86-64/pr18900c.c: Likewise.
	* ld-x86-64/mpx3.dd: Updated.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Optimise PowerPC64 r2 adjusting stubs
@ 2015-08-31 13:54 sergiodj+buildbot
  2015-08-31 21:10 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-31 13:54 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a7c4979727e13498b8d4d85c72ddf65611c532a9 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: a7c4979727e13498b8d4d85c72ddf65611c532a9

Optimise PowerPC64 r2 adjusting stubs

Sometimes these stubs don't need to change the low 16-bits of r2, so in
that case omit a useless addi r2,r2,0 insn.  Also, change the get_r2off
error return from 0 to -1 since 0 is a valid return for ELFv2 -R objects.

	* elf64-ppc.c (get_r2off): Return -1 on error.
	(ppc_build_one_stub): Adjust for get_r2off change.  Don't emit
	addi r2,r2,0 on r2off stubs when the low 16-bit delta is zero.
	(ppc_size_one_stub): Corresponding size changes for r2off stubs.
	Add condition in test for -R objects.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] ppc64 section group handling
@ 2015-08-31 13:47 sergiodj+buildbot
  2015-08-31 18:59 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-31 13:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6f20ed8a6ba1a01fb356eea8ea45310ed8478a27 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 6f20ed8a6ba1a01fb356eea8ea45310ed8478a27

ppc64 section group handling

Two organizational changes to the array of additional info kept for
sections.
1) Move group info into a per-group allocated struct, in preparation
for future changes that need per-group accounting.
2) Expand the array to include output sections, which simplifies
sizing and removes the need for a separate output section array.

	* section.c (section_id): Make file scope.
	(bfd_get_next_section_id): New function.
	* elf64-ppc.c (struct map_stub): Remove toc_off field.  Move decl.
	(struct ppc_stub_hash_entry): Delete stub_sec and id_sec.  Add
	group.  Update all uses.
	(struct ppc_link_hash_table): Delete top_id, top_index, and
	input_list.  Add sec_info_arr_size.  Rename stub_group to
	sec_info, and make group info indirect.  Update stub_group refs
	throughout file.
	(ppc_add_stub): Don't look for stub_sec on link_sec stub_group
	entry.
	(ppc_build_one_stub): Delete FIXME.
	(ppc64_elf_setup_section_lists): Size htab->sec_info for all
	sections, not just input sections.  Don't create htab->input_list.
	(ppc64_elf_next_input_section): Update to use sec_info union as
	list pointer.
	(PREV_SEC): Delete.
	(group_sections): Pass "info" param rather than "htab".  Iterate
	over output sections rather than input_list.  Use sec_info union
	as list pointers.  Alloc atruct map_stub, and return fail status.
	* bfd-in2.h: Regenerate.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] gdb/tui: Make local variable const.
@ 2015-08-31 11:07 sergiodj+buildbot
  2015-08-31 17:14 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-31 11:07 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 136765eab14d32f5fec607f755c3096eb43bf96f ***

Author: Andrew Burgess <andrew.burgess@embecosm.com>
Branch: master
Commit: 136765eab14d32f5fec607f755c3096eb43bf96f

gdb/tui: Make local variable const.

Small clean up to make a local variable const and remove a cast of NULL.

gdb/ChangeLog:

	* tui/tui-data.c (tui_win_name): Make local variable const, remove
	cast of NULL.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix assertion failure in linux-thread-db
@ 2015-08-27 17:52 sergiodj+buildbot
  2015-08-29 18:54 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-27 17:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e0fd7c47bd01e0a6eecf5dec4a4be958f8b3bbc8 ***

Author: Ulrich Weigand <ulrich.weigand@de.ibm.com>
Branch: master
Commit: e0fd7c47bd01e0a6eecf5dec4a4be958f8b3bbc8

Fix assertion failure in linux-thread-db

Since we are no longer using thread events by default in linux-thread-db,
the find_new_threads_once routine contains an assertion that it should
never be called on a live inferior unless using thread events:
  gdb_assert (!target_has_execution || thread_db_use_events ());

However, there is a code path from thread_db_get_thread_local_address
that will in fact call find_new_threads_once in some scenarios.  In
particular, this is currently always triggered when starting up any
Cell/B.E. combined exeuctable.

To fix this, this patch removes the call to thread_db_find_new_threads_1
when the current thread was not yet detected.  In its place, we now just
call thread_from_lwp to detect this one thread if necessary.

ChangeLog:

	* linux-thread-db.c (thread_db_get_thread_local_address): If the
	thread was not yet discovered, use thread_from_lwp instead of
	calling thread_db_find_new_threads_1.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Report UNRESOLVED on failures while detecting Cell/B.E.
@ 2015-08-27 17:43 sergiodj+buildbot
  2015-08-29 16:42 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-27 17:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4e83a1e776c0acdaca9e69be9576db9efcd5f511 ***

Author: Ulrich Weigand <ulrich.weigand@de.ibm.com>
Branch: master
Commit: 4e83a1e776c0acdaca9e69be9576db9efcd5f511

Report UNRESOLVED on failures while detecting Cell/B.E.

The gdb.cell testcases use the predicate skip_cell_tests defined in
lib/cell.exp to determine whether Cell/B.E. test cases ought to be
run. This tests verifies that we have a toolchain that supports
generating combined Cell/B.E. binaries, and that the target machine
actually is a Cell/B.E.

In order to do so, a small test program is built and run (under the
debugger).  Any failure is taken as a sign that we don't have a
Cell/B.E. machine and the tests are to be skipped.

This has the unfortunate effect that a serious bug in GDB that causes
internal compiler errors even on the trivial test program does not
lead to any failures in the testsuite, since now all gdb.cell test
are simply skipped.

This patch changes skip_cell_tests to at least report UNRESOLVED
in cases where execution of the test program fails in unexpected
ways.

testsuite/ChangeLog:

	* lib/cell.exp (skip_cell_tests): Report UNRESOLVED on unexpected
	failures to run the test program under GDB.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Import the "signal-h" module from gnulib
@ 2015-08-27 12:35 sergiodj+buildbot
  2015-08-28 23:09 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-27 12:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0750520d890bd6ac3ba958a921fbeebe5915e50f ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 0750520d890bd6ac3ba958a921fbeebe5915e50f

Import the "signal-h" module from gnulib

This gives us a signal.h replacement that makes sure the sighandler_t
typedef (a GNU extension) is always available.  A follow up patch will
make use of this.

gdb/ChangeLog:
2015-08-27  Pedro Alves  <palves@redhat.com>

	* gnulib/update-gnulib.sh (IMPORTED_GNULIB_MODULES): Add signal-h.
	* gnulib/aclocal.m4: Renegerate.
	* gnulib/config.in: Renegerate.
	* gnulib/configure: Renegerate.
	* gnulib/import/Makefile.am: Update.
	* gnulib/import/Makefile.in: Regenerate.
	* gnulib/import/m4/gnulib-cache.m4: Update.
	* gnulib/import/m4/gnulib-comp.m4: Update.
	* gnulib/import/m4/signal_h.m4: New file.
	* gnulib/import/signal.in.h: New file.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Unset attach_flag when running a new process
@ 2015-08-27  1:02 sergiodj+buildbot
  2015-08-28 11:49 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-27  1:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e9756d52bea3834ffb31d0a907944bd022250ed8 ***

Author: Patrick Palka <patrick@parcs.ath.cx>
Branch: master
Commit: e9756d52bea3834ffb31d0a907944bd022250ed8

Unset attach_flag when running a new process

We currently set attach_flag when attaching to a process, so we should
make sure to unset it when forking a new process.  Otherwise attach_flag
would remain set after forking, if the previous process associated with
the inferior was attached to.

gdb/ChangeLog:

	* target.c (target_pre_inferior): Unset attach_flag.

gdb/testsuite/ChangeLog:

	* gdb.base/run-after-attach.exp: New test file.
	* gdb.base/run-after-attach.c: New test file.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Replace some xmalloc-family functions with XNEW-family ones
@ 2015-08-26 21:30 sergiodj+buildbot
  2015-08-28  7:21 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-26 21:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8d7493201cf01c9836403695f67f7e157341bfd5 ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: 8d7493201cf01c9836403695f67f7e157341bfd5

Replace some xmalloc-family functions with XNEW-family ones

This patch is part of the make-gdb-buildable-in-C++ effort.  The idea is
to change some calls to the xmalloc family of functions to calls to the
equivalents in the XNEW family.  This avoids adding an explicit cast, so
it keeps the code a bit more readable.  Some of them also map relatively
well to a C++ equivalent (XNEW (struct foo) -> new foo), so it will be
possible to do scripted replacements if needed.

I only changed calls that were obviously allocating memory for one or
multiple "objects".  Allocation of variable sizes (such as strings or
buffer handling) will be for later (and won't use XNEW).

  - xmalloc (sizeof (struct foo)) -> XNEW (struct foo)
  - xmalloc (num * sizeof (struct foo)) -> XNEWVEC (struct foo, num)
  - xcalloc (1, sizeof (struct foo)) -> XCNEW (struct foo)
  - xcalloc (num, sizeof (struct foo)) -> XCNEWVEC (struct foo, num)
  - xrealloc (p, num * sizeof (struct foo) -> XRESIZEVEC (struct foo, p, num)
  - obstack_alloc (ob, sizeof (struct foo)) -> XOBNEW (ob, struct foo)
  - obstack_alloc (ob, num * sizeof (struct foo)) -> XOBNEWVEC (ob, struct foo, num)
  - alloca (sizeof (struct foo)) -> XALLOCA (struct foo)
  - alloca (num * sizeof (struct foo)) -> XALLOCAVEC (struct foo, num)

Some instances of xmalloc followed by memset to zero the buffer were
replaced by XCNEW or XCNEWVEC.

I regtested on x86-64, Ubuntu 14.04, but the patch touches many
architecture-specific files.  For those I'll have to rely on the
buildbot or people complaining that I broke their gdb.

gdb/ChangeLog:

	* aarch64-linux-nat.c (aarch64_add_process): Likewise.
	* aarch64-tdep.c (aarch64_gdbarch_init): Likewise.
	* ada-exp.y (write_ambiguous_var): Likewise.
	* ada-lang.c (resolve_subexp): Likewise.
	(user_select_syms): Likewise.
	(assign_aggregate): Likewise.
	(ada_evaluate_subexp): Likewise.
	(cache_symbol): Likewise.
	* addrmap.c (allocate_key): Likewise.
	(addrmap_create_mutable): Likewise.
	* aix-thread.c (sync_threadlists): Likewise.
	* alpha-tdep.c (alpha_push_dummy_call): Likewise.
	(alpha_gdbarch_init): Likewise.
	* amd64-windows-tdep.c (amd64_windows_push_arguments): Likewise.
	* arm-linux-nat.c (arm_linux_add_process): Likewise.
	* arm-linux-tdep.c (arm_linux_displaced_step_copy_insn): Likewise.
	* arm-tdep.c (push_stack_item): Likewise.
	(arm_displaced_step_copy_insn): Likewise.
	(arm_gdbarch_init): Likewise.
	(_initialize_arm_tdep): Likewise.
	* avr-tdep.c (push_stack_item): Likewise.
	* ax-general.c (new_agent_expr): Likewise.
	* block.c (block_initialize_namespace): Likewise.
	* breakpoint.c (alloc_counted_command_line): Likewise.
	(update_dprintf_command_list): Likewise.
	(parse_breakpoint_sals): Likewise.
	(decode_static_tracepoint_spec): Likewise.
	(until_break_command): Likewise.
	(clear_command): Likewise.
	(update_global_location_list): Likewise.
	(get_breakpoint_objfile_data) Likewise.
	* btrace.c (ftrace_new_function): Likewise.
	(btrace_set_insn_history): Likewise.
	(btrace_set_call_history): Likewise.
	* buildsym.c (add_symbol_to_list): Likewise.
	(record_pending_block): Likewise.
	(start_subfile): Likewise.
	(start_buildsym_compunit): Likewise.
	(push_subfile): Likewise.
	(end_symtab_get_static_block): Likewise.
	(buildsym_init): Likewise.
	* cli/cli-cmds.c (source_command): Likewise.
	* cli/cli-decode.c (add_cmd): Likewise.
	* cli/cli-script.c (build_command_line): Likewise.
	(setup_user_args): Likewise.
	(realloc_body_list): Likewise.
	(process_next_line): Likewise.
	(copy_command_lines): Likewise.
	* cli/cli-setshow.c (do_set_command): Likewise.
	* coff-pe-read.c (read_pe_exported_syms): Likewise.
	* coffread.c (coff_locate_sections): Likewise.
	(coff_symtab_read): Likewise.
	(coff_read_struct_type): Likewise.
	* common/cleanups.c (make_my_cleanup2): Likewise.
	* common/common-exceptions.c (throw_it): Likewise.
	* common/filestuff.c (make_cleanup_close): Likewise.
	* common/format.c (parse_format_string): Likewise.
	* common/queue.h (DEFINE_QUEUE_P): Likewise.
	* compile/compile-object-load.c (munmap_list_add): Likewise.
	(compile_object_load): Likewise.
	* compile/compile-object-run.c (compile_object_run): Likewise.
	* compile/compile.c (append_args): Likewise.
	* corefile.c (specify_exec_file_hook): Likewise.
	* cp-support.c (make_symbol_overload_list): Likewise.
	* cris-tdep.c (push_stack_item): Likewise.
	(cris_gdbarch_init): Likewise.
	* ctf.c (ctf_trace_file_writer_new): Likewise.
	* dbxread.c (init_header_files): Likewise.
	(add_new_header_file): Likewise.
	(init_bincl_list): Likewise.
	(dbx_end_psymtab): Likewise.
	(start_psymtab): Likewise.
	(dbx_end_psymtab): Likewise.
	* dcache.c (dcache_init): Likewise.
	* dictionary.c (dict_create_hashed): Likewise.
	(dict_create_hashed_expandable): Likewise.
	(dict_create_linear): Likewise.
	(dict_create_linear_expandable): Likewise.
	* dtrace-probe.c (dtrace_process_dof_probe): Likewise.
	* dummy-frame.c (register_dummy_frame_dtor): Likewise.
	* dwarf2-frame-tailcall.c (cache_new_ref1): Likewise.
	* dwarf2-frame.c (dwarf2_build_frame_info): Likewise.
	(decode_frame_entry_1): Likewise.
	* dwarf2expr.c (new_dwarf_expr_context): Likewise.
	* dwarf2loc.c (dwarf2_compile_expr_to_ax): Likewise.
	* dwarf2read.c (dwarf2_has_info): Likewise.
	(create_signatured_type_table_from_index): Likewise.
	(dwarf2_read_index): Likewise.
	(dw2_get_file_names_reader): Likewise.
	(create_all_type_units): Likewise.
	(read_cutu_die_from_dwo): Likewise.
	(init_tu_and_read_dwo_dies): Likewise.
	(init_cutu_and_read_dies): Likewise.
	(create_all_comp_units): Likewise.
	(queue_comp_unit): Likewise.
	(inherit_abstract_dies): Likewise.
	(read_call_site_scope): Likewise.
	(dwarf2_add_field): Likewise.
	(dwarf2_add_typedef): Likewise.
	(dwarf2_add_member_fn): Likewise.
	(attr_to_dynamic_prop): Likewise.
	(abbrev_table_alloc_abbrev): Likewise.
	(abbrev_table_read_table): Likewise.
	(add_include_dir): Likewise.
	(add_file_name): Likewise.
	(dwarf_decode_line_header): Likewise.
	(dwarf2_const_value_attr): Likewise.
	(dwarf_alloc_block): Likewise.
	(parse_macro_definition): Likewise.
	(set_die_type): Likewise.
	(write_psymtabs_to_index): Likewise.
	(create_cus_from_index): Likewise.
	(dwarf2_create_include_psymtab): Likewise.
	(process_psymtab_comp_unit_reader): Likewise.
	(build_type_psymtab_dependencies): Likewise.
	(read_comp_units_from_section): Likewise.
	(compute_compunit_symtab_includes): Likewise.
	(create_dwo_unit_in_dwp_v1): Likewise.
	(create_dwo_unit_in_dwp_v2): Likewise.
	(read_func_scope): Likewise.
	(process_structure_scope): Likewise.
	(mark_common_block_symbol_computed): Likewise.
	(load_partial_dies): Likewise.
	(dwarf2_symbol_mark_computed): Likewise.
	* elfread.c (elf_symfile_segments): Likewise.
	(elf_read_minimal_symbols): Likewise.
	* environ.c (make_environ): Likewise.
	* eval.c (evaluate_subexp_standard): Likewise.
	* event-loop.c (create_file_handler): Likewise.
	(create_async_signal_handler): Likewise.
	(create_async_event_handler): Likewise.
	(create_timer): Likewise.
	* exec.c (build_section_table): Likewise.
	* fbsd-nat.c (fbsd_remember_child): Likewise.
	* fork-child.c (fork_inferior): Likewise.
	* frv-tdep.c (new_variant): Likewise.
	* gdbarch.sh (gdbarch_alloc): Likewise.
	(append_name): Likewise.
	* gdbtypes.c (rank_function): Likewise.
	(copy_type_recursive): Likewise.
	(add_dyn_prop): Likewise.
	* gnu-nat.c (make_proc): Likewise.
	(make_inf): Likewise.
	(gnu_write_inferior): Likewise.
	* gnu-v3-abi.c (build_gdb_vtable_type): Likewise.
	(build_std_type_info_type): Likewise.
	* guile/scm-param.c (compute_enum_list): Likewise.
	* guile/scm-utils.c (gdbscm_parse_function_args): Likewise.
	* guile/scm-value.c (gdbscm_value_call): Likewise.
	* h8300-tdep.c (h8300_gdbarch_init): Likewise.
	* hppa-tdep.c (hppa_init_objfile_priv_data): Likewise.
	(read_unwind_info): Likewise.
	* ia64-tdep.c (ia64_gdbarch_init): Likewise.
	* infcall.c (dummy_frame_context_saver_setup): Likewise.
	(call_function_by_hand_dummy): Likewise.
	* infcmd.c (step_once): Likewise.
	(finish_forward): Likewise.
	(attach_command): Likewise.
	(notice_new_inferior): Likewise.
	* inferior.c (add_inferior_silent): Likewise.
	* infrun.c (add_displaced_stepping_state): Likewise.
	(save_infcall_control_state): Likewise.
	(save_inferior_ptid): Likewise.
	(_initialize_infrun): Likewise.
	* jit.c (bfd_open_from_target_memory): Likewise.
	(jit_gdbarch_data_init): Likewise.
	* language.c (add_language): Likewise.
	* linespec.c (decode_line_2): Likewise.
	* linux-nat.c (add_to_pid_list): Likewise.
	(add_initial_lwp): Likewise.
	* linux-thread-db.c (add_thread_db_info): Likewise.
	(record_thread): Likewise.
	(info_auto_load_libthread_db): Likewise.
	* m32c-tdep.c (m32c_gdbarch_init): Likewise.
	* m68hc11-tdep.c (m68hc11_gdbarch_init): Likewise.
	* m68k-tdep.c (m68k_gdbarch_init): Likewise.
	* m88k-tdep.c (m88k_analyze_prologue): Likewise.
	* macrocmd.c (macro_define_command): Likewise.
	* macroexp.c (gather_arguments): Likewise.
	* macroscope.c (sal_macro_scope): Likewise.
	* macrotab.c (new_macro_table): Likewise.
	* mdebugread.c (push_parse_stack): Likewise.
	(parse_partial_symbols): Likewise.
	(parse_symbol): Likewise.
	(psymtab_to_symtab_1): Likewise.
	(new_block): Likewise.
	(new_psymtab): Likewise.
	(mdebug_build_psymtabs): Likewise.
	(add_pending): Likewise.
	(elfmdebug_build_psymtabs): Likewise.
	* mep-tdep.c (mep_gdbarch_init): Likewise.
	* mi/mi-main.c (mi_execute_command): Likewise.
	* mi/mi-parse.c (mi_parse_argv): Likewise.
	* minidebug.c (lzma_open): Likewise.
	* minsyms.c (terminate_minimal_symbol_table): Likewise.
	* mips-linux-nat.c (mips_linux_insert_watchpoint): Likewise.
	* mips-tdep.c (mips_gdbarch_init): Likewise.
	* mn10300-tdep.c (mn10300_gdbarch_init): Likewise.
	* msp430-tdep.c (msp430_gdbarch_init): Likewise.
	* mt-tdep.c (mt_registers_info): Likewise.
	* nat/aarch64-linux.c (aarch64_linux_new_thread): Likewise.
	* nat/linux-btrace.c (linux_enable_bts): Likewise.
	(linux_enable_pt): Likewise.
	* nat/linux-osdata.c (linux_xfer_osdata_processes): Likewise.
	(linux_xfer_osdata_processgroups): Likewise.
	* nios2-tdep.c (nios2_gdbarch_init): Likewise.
	* nto-procfs.c (procfs_meminfo): Likewise.
	* objc-lang.c (start_msglist): Likewise.
	(selectors_info): Likewise.
	(classes_info): Likewise.
	(find_methods): Likewise.
	* objfiles.c (allocate_objfile): Likewise.
	(update_section_map): Likewise.
	* osabi.c (gdbarch_register_osabi): Likewise.
	(gdbarch_register_osabi_sniffer): Likewise.
	* parse.c (start_arglist): Likewise.
	* ppc-linux-nat.c (hwdebug_find_thread_points_by_tid): Likewise.
	(hwdebug_insert_point): Likewise.
	* printcmd.c (display_command): Likewise.
	(ui_printf): Likewise.
	* procfs.c (create_procinfo): Likewise.
	(load_syscalls): Likewise.
	(proc_get_LDT_entry): Likewise.
	(proc_update_threads): Likewise.
	* prologue-value.c (make_pv_area): Likewise.
	(pv_area_store): Likewise.
	* psymtab.c (extend_psymbol_list): Likewise.
	(init_psymbol_list): Likewise.
	(allocate_psymtab): Likewise.
	* python/py-inferior.c (add_thread_object): Likewise.
	* python/py-param.c (compute_enum_values): Likewise.
	* python/py-value.c (valpy_call): Likewise.
	* python/py-varobj.c (py_varobj_iter_next): Likewise.
	* python/python.c (ensure_python_env): Likewise.
	* record-btrace.c (record_btrace_start_replaying): Likewise.
	* record-full.c (record_full_reg_alloc): Likewise.
	(record_full_mem_alloc): Likewise.
	(record_full_end_alloc): Likewise.
	(record_full_core_xfer_partial): Likewise.
	* regcache.c (get_thread_arch_aspace_regcache): Likewise.
	* remote-fileio.c (remote_fileio_init_fd_map): Likewise.
	* remote-notif.c (remote_notif_state_allocate): Likewise.
	* remote.c (demand_private_info): Likewise.
	(remote_notif_stop_alloc_reply): Likewise.
	(remote_enable_btrace): Likewise.
	* reverse.c (save_bookmark_command): Likewise.
	* rl78-tdep.c (rl78_gdbarch_init): Likewise.
	* rx-tdep.c (rx_gdbarch_init): Likewise.
	* s390-linux-nat.c (s390_insert_watchpoint): Likewise.
	* ser-go32.c (dos_get_tty_state): Likewise.
	(dos_copy_tty_state): Likewise.
	* ser-mingw.c (ser_windows_open): Likewise.
	(ser_console_wait_handle): Likewise.
	(ser_console_get_tty_state): Likewise.
	(make_pipe_state): Likewise.
	(net_windows_open): Likewise.
	* ser-unix.c (hardwire_get_tty_state): Likewise.
	(hardwire_copy_tty_state): Likewise.
	* solib-aix.c (solib_aix_new_lm_info): Likewise.
	* solib-dsbt.c (dsbt_current_sos): Likewise.
	(dsbt_relocate_main_executable): Likewise.
	* solib-frv.c (frv_current_sos): Likewise.
	(frv_relocate_main_executable): Likewise.
	* solib-spu.c (spu_bfd_fopen): Likewise.
	* solib-svr4.c (lm_info_read): Likewise.
	(svr4_copy_library_list): Likewise.
	(svr4_default_sos): Likewise.
	* source.c (find_source_lines): Likewise.
	(line_info): Likewise.
	(add_substitute_path_rule): Likewise.
	* spu-linux-nat.c (spu_bfd_open): Likewise.
	* spu-tdep.c (info_spu_dma_cmdlist): Likewise.
	* stabsread.c (dbx_lookup_type): Likewise.
	(read_type): Likewise.
	(read_member_functions): Likewise.
	(read_struct_fields): Likewise.
	(read_baseclasses): Likewise.
	(read_args): Likewise.
	(_initialize_stabsread): Likewise.
	* stack.c (func_command): Likewise.
	* stap-probe.c (handle_stap_probe): Likewise.
	* symfile.c (addrs_section_sort): Likewise.
	(addr_info_make_relative): Likewise.
	(load_section_callback): Likewise.
	(add_symbol_file_command): Likewise.
	(init_filename_language_table): Likewise.
	* symtab.c (create_filename_seen_cache): Likewise.
	(sort_search_symbols_remove_dups): Likewise.
	(search_symbols): Likewise.
	* target.c (make_cleanup_restore_target_terminal): Likewise.
	* thread.c (new_thread): Likewise.
	(enable_thread_stack_temporaries): Likewise.
	(make_cleanup_restore_current_thread): Likewise.
	(thread_apply_all_command): Likewise.
	* tic6x-tdep.c (tic6x_gdbarch_init): Likewise.
	* top.c (gdb_readline_wrapper): Likewise.
	* tracefile-tfile.c (tfile_trace_file_writer_new): Likewise.
	* tracepoint.c (trace_find_line_command): Likewise.
	(all_tracepoint_actions_and_cleanup): Likewise.
	(make_cleanup_restore_current_traceframe): Likewise.
	(get_uploaded_tp): Likewise.
	(get_uploaded_tsv): Likewise.
	* tui/tui-data.c (tui_alloc_generic_win_info): Likewise.
	(tui_alloc_win_info): Likewise.
	(tui_alloc_content): Likewise.
	(tui_add_content_elements): Likewise.
	* tui/tui-disasm.c (tui_find_disassembly_address): Likewise.
	(tui_set_disassem_content): Likewise.
	* ui-file.c (ui_file_new): Likewise.
	(stdio_file_new): Likewise.
	(tee_file_new): Likewise.
	* utils.c (make_cleanup_restore_integer): Likewise.
	(add_internal_problem_command): Likewise.
	* v850-tdep.c (v850_gdbarch_init): Likewise.
	* valops.c (find_oload_champ): Likewise.
	* value.c (allocate_value_lazy): Likewise.
	(record_latest_value): Likewise.
	(create_internalvar): Likewise.
	* varobj.c (install_variable): Likewise.
	(new_variable): Likewise.
	(new_root_variable): Likewise.
	(cppush): Likewise.
	(_initialize_varobj): Likewise.
	* windows-nat.c (windows_make_so): Likewise.
	* x86-nat.c (x86_add_process): Likewise.
	* xcoffread.c (arrange_linetable): Likewise.
	(allocate_include_entry): Likewise.
	(process_linenos): Likewise.
	(SYMBOL_DUP): Likewise.
	(xcoff_start_psymtab): Likewise.
	(xcoff_end_psymtab): Likewise.
	* xml-support.c (gdb_xml_parse_attr_ulongest): Likewise.
	* xtensa-tdep.c (xtensa_register_type): Likewise.
	* gdbarch.c: Regenerate.
	* gdbarch.h: Regenerate.

gdb/gdbserver/ChangeLog:

	* ax.c (gdb_parse_agent_expr): Likewise.
	(compile_bytecodes): Likewise.
	* dll.c (loaded_dll): Likewise.
	* event-loop.c (append_callback_event): Likewise.
	(create_file_handler): Likewise.
	(create_file_event): Likewise.
	* hostio.c (handle_open): Likewise.
	* inferiors.c (add_thread): Likewise.
	(add_process): Likewise.
	* linux-aarch64-low.c (aarch64_linux_new_process): Likewise.
	* linux-arm-low.c (arm_new_process): Likewise.
	(arm_new_thread): Likewise.
	* linux-low.c (add_to_pid_list): Likewise.
	(linux_add_process): Likewise.
	(handle_extended_wait): Likewise.
	(add_lwp): Likewise.
	(enqueue_one_deferred_signal): Likewise.
	(enqueue_pending_signal): Likewise.
	(linux_resume_one_lwp_throw): Likewise.
	(linux_resume_one_thread): Likewise.
	(linux_read_memory): Likewise.
	(linux_write_memory): Likewise.
	* linux-mips-low.c (mips_linux_new_process): Likewise.
	(mips_linux_new_thread): Likewise.
	(mips_add_watchpoint): Likewise.
	* linux-x86-low.c (initialize_low_arch): Likewise.
	* lynx-low.c (lynx_add_process): Likewise.
	* mem-break.c (set_raw_breakpoint_at): Likewise.
	(set_breakpoint): Likewise.
	(add_condition_to_breakpoint): Likewise.
	(add_commands_to_breakpoint): Likewise.
	(clone_agent_expr): Likewise.
	(clone_one_breakpoint): Likewise.
	* regcache.c (new_register_cache): Likewise.
	* remote-utils.c (look_up_one_symbol): Likewise.
	* server.c (queue_stop_reply): Likewise.
	(start_inferior): Likewise.
	(queue_stop_reply_callback): Likewise.
	(handle_target_event): Likewise.
	* spu-low.c (fetch_ppc_memory): Likewise.
	(store_ppc_memory): Likewise.
	* target.c (set_target_ops): Likewise.
	* thread-db.c (thread_db_load_search): Likewise.
	(try_thread_db_load_1): Likewise.
	* tracepoint.c (add_tracepoint): Likewise.
	(add_tracepoint_action): Likewise.
	(create_trace_state_variable): Likewise.
	(cmd_qtdpsrc): Likewise.
	(cmd_qtro): Likewise.
	(add_while_stepping_state): Likewise.
	* win32-low.c (child_add_thread): Likewise.
	(get_image_name): Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix native follow-exec-mode "new"
@ 2015-08-26 21:28 sergiodj+buildbot
  2015-08-28  6:23 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-26 21:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 17d8546e6067d0133f19275d1ccc25cf93cfc7bc ***

Author: Don Breazeal <donb@codesourcery.com>
Branch: master
Commit: 17d8546e6067d0133f19275d1ccc25cf93cfc7bc

Fix native follow-exec-mode "new"

This patch fixes a segmentation fault in native GDB when
handling an exec event with follow-exec-mode set to "new".

The stack trace from the segfault was this:

 0  0x0000000000669594 in gdbarch_data (gdbarch=0x0, data=0x20da7a0)
    at /scratch/dbreazea/sandbox/exec-nat/binutils-gdb/gdb/gdbarch.c:4847
 1  0x00000000004d430e in get_remote_arch_state ()
    at /scratch/dbreazea/sandbox/exec-nat/binutils-gdb/gdb/remote.c:603
 2  0x00000000004d431e in get_remote_state ()
    at /scratch/dbreazea/sandbox/exec-nat/binutils-gdb/gdb/remote.c:616
 3  0x00000000004dda8b in discard_pending_stop_replies (inf=0x217c710)
    at /scratch/dbreazea/sandbox/exec-nat/binutils-gdb/gdb/remote.c:5775
 4  0x00000000006a5928 in observer_inferior_exit_notification_stub (
    data=0x4dda7a <discard_pending_stop_replies>, args_data=0x7fff12c258f0)
    at ./observer.inc:1137
 5  0x00000000006a419a in generic_observer_notify (subject=0x21dfbe0,
    args=0x7fff12c258f0)
    at /scratch/dbreazea/sandbox/exec-nat/binutils-gdb/gdb/observer.c:167
 6  0x00000000006a59ba in observer_notify_inferior_exit (inf=0x217c710)
    at ./observer.inc:1162
 7  0x00000000007981d5 in exit_inferior_1 (inftoex=0x217c710, silent=1)
    at /scratch/dbreazea/sandbox/exec-nat/binutils-gdb/gdb/inferior.c:244
 8  0x00000000007982f2 in exit_inferior_num_silent (num=1)
    at /scratch/dbreazea/sandbox/exec-nat/binutils-gdb/gdb/inferior.c:286
 9  0x000000000062f93d in follow_exec (ptid=...,
    execd_pathname=0x7fff12c259a0 "/scratch/dbreazea/sandbox/exec-nat/build/gdb/testsuite/gdb.base/execd-prog")
    at /scratch/dbreazea/sandbox/exec-nat/binutils-gdb/gdb/infrun.c:1195

In follow_exec we were creating a new inferior for the execd program,
as required by the exec mode, but we were doing it before calling
exit_inferior_num_silent on the original inferior.  So on entry to
exit_inferior_num_silent we had two inferiors with the same ptid.

In the calls made by exit_inferior_num_silent, the current inferior
is temporarily saved and replaced in order to make use of functions
that only operate on the current inferior (for example, in
do_all_continuations, called while deleting the threads of the original
inferior).  When we restored the original inferior, we just took the
first inferior that matched the ptid of the original and got the new
(wrong) one.  It hadn't been initialized yet and had no gdbarch
pointer, and GDB segfaulted.

The fix for that is to call exit_inferior_num_silent before adding the new
inferior, so that we never have two inferiors with the same ptid.  Then
exit_inferior_num_silent uses the original inferior as the current inferior
throughout, and can find a valid gdbarch pointer.

Once we have finished with the exit of the old inferior and added the
new one, we need to create a new thread for the new inferior.  In the
function that called follow_exec, handle_inferior_event_1,
ecs->event_thread now points to the thread that was deleted with the
exit of the original inferior.  To remedy this we create the new thread,
and once we return from follow_exec we reset ecs->event_thread.

Note that we are guaranteed that we can reset ecs->event_thread
safely using inferior_thread because we have set the current
inferior in follow_exec, and inferior_ptid was set by the call
to context_switch at the beginning of exec event handling.

gdb/ChangeLog:

	* infrun.c (follow_exec): Re-order operations for
	handling follow-exec-mode "new".
	(handle_inferior_event_1): Assign ecs->event_thread
	to the current thread.
	* remote.c (get_remote_arch_state): Add an assertion.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] New test for follow-exec-mode
@ 2015-08-26 21:20 sergiodj+buildbot
  2015-08-28  3:57 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-26 21:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8d37573b4356a38d091b0f18b69f91797a7cef26 ***

Author: Don Breazeal <donb@codesourcery.com>
Branch: master
Commit: 8d37573b4356a38d091b0f18b69f91797a7cef26

New test for follow-exec-mode

This patch implements a new GDB test for follow-exec-mode.  Although
there is a GDB test for debugging across an exec, there is no test for
follow-exec-mode.  This test is derived from gdb.base/foll-exec.exp,
and re-uses execd-prog.c as the program to exec.

The following behavior is tested:

follow-exec-mode == "same"
 - 'next' over the exec, check for one inferior
 - 'continue' past the exec to a breakpoint, check for one inferior
 - after the exec, use a 'run' command to run the current binary
follow-exec-mode == "new"
 - 'next' over the exec, check for two inferiors
 - 'continue' past the exec to a breakpoint, check for two inferiors
 - after the exec, use a 'run' command to run the current binary
 - after the exec, use the 'inferior' command to switch inferiors,
   then use a 'run' command to run the current binary

Note that single-step breakpoints do not survive across an exec.
There has to be a breakpoint in the execed program in order for
it to stop right after the exec.

gdb/testsuite/ChangeLog:

	* gdb.base/foll-exec-2.c: New test program.
	* gdb.base/foll-exec-2.exp: New test.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] gdb: Add Markus Metzger as btrace maintainer
@ 2015-08-26 17:07 sergiodj+buildbot
  2015-08-28  1:55 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-26 17:07 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ba49e44bdcfdb5e936686a42d84e5ca043267cab ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: ba49e44bdcfdb5e936686a42d84e5ca043267cab

gdb: Add Markus Metzger as btrace maintainer

gdb/ChangeLog:
2015-08-26  Pedro Alves  <palves@redhat.com>

	* MAINTAINERS: Add Markus Metzger as btrace maintainer.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Select MIPS ABi based upon abiflags rather than e_flags.
@ 2015-08-26 13:53 sergiodj+buildbot
  2015-08-27 21:34 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-26 13:53 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c97c330ba8e80776c546e5f562916bf077e358b3 ***

Author: Matthew Fortune <matthew.fortune@imgtec.com>
Branch: master
Commit: c97c330ba8e80776c546e5f562916bf077e358b3

Select MIPS ABi based upon abiflags rather than e_flags.

bfd	PR ld/18401
	* elfxx-mips.c (bfd_mips_isa_ext_mach): New function: Converts an
	ISA value to a bfd machine number.
	(bfd_mips_isa_ext): Update the ISA level and revision if
	necessary.  Use mips_mach_extends_p to decide if the ISA extension
	needs to be set.
	(_bfd_mips_elf_merge_private_bfd_data): Allow the ISA extension to
	be inferred from the ABI setting.  Set the ISA level from the
	maximum of the incoming and outgoing ISA levels.

tests
	* ld-mips-elf/mips-elf-flags.exp: Add more ISA conflict tests.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Replace assertions with warning messages about ELF binaries containing multiple symbol tables.
@ 2015-08-25 17:18 sergiodj+buildbot
  2015-08-27 19:24 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-25 17:18 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 16ad13eca4a18139cd1dec214ec83fdc7c47ffda ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: 16ad13eca4a18139cd1dec214ec83fdc7c47ffda

Replace assertions with warning messages about ELF binaries containing multiple symbol tables.

	PR binutils/18854
	* elf.c (bfd_section_from_shdr): Replace assertions with warnings
	about multiple symbol tables.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Use debug_printf in debug_reg_change_callback
@ 2015-08-25 13:03 sergiodj+buildbot
  2015-08-26  6:35 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-25 13:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 32a271eeaf1b1be1367b6ea181a0f39a3da71d45 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 32a271eeaf1b1be1367b6ea181a0f39a3da71d45

Use debug_printf in debug_reg_change_callback

gdb:

2015-08-25  Yao Qi  <yao.qi@linaro.org>

	* aarch64-linux-nat.c (debug_reg_change_callback): Use
	debug_printf.

gdb/gdbserver:

2015-08-25  Yao Qi  <yao.qi@linaro.org>

	* linux-aarch64-low.c (debug_reg_change_callback): Use
	debug_printf.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Move aarch64_linux_prepare_to_resume to nat/aarch64-linux.c
@ 2015-08-25 12:13 sergiodj+buildbot
  2015-08-26 21:07 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-25 12:13 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT db3cb7cb3e51e5eb834412adbf90e81bb76846c6 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: db3cb7cb3e51e5eb834412adbf90e81bb76846c6

Move aarch64_linux_prepare_to_resume to nat/aarch64-linux.c

gdb:

2015-08-25  Yao Qi  <yao.qi@linaro.org>

	* Makefile.in (aarch64-liunx.o): New rule.
	(HFILES_NO_SRCDIR): Add aarch64-linux.h.
	* config/aarch64/linux.mh (NAT_FILE): Add aarch64-linux.o.
	* aarch64-linux-nat.c: Include nat/aarch64-linux.h.
	* aarch64-linux-nat.c (aarch64_get_debug_reg_state): Make it
	extern.
	(aarch64_linux_prepare_to_resume): Move it nat/aarch64-linux.c.
	* nat/aarch64-linux-hw-point.h (aarch64_debug_reg_state): Declare
	* nat/aarch64-linux.c: New file.
	* nat/aarch64-linux.h: New file.

gdb/gdbserver:

2015-08-25  Yao Qi  <yao.qi@linaro.org>

	* Makefile.in (aarch64-linux.o): New rule.
	* configure.srv (aarch64*-*-linux*): Append aarch64-linux.o to
	srv_tgtobj.
	* linux-aarch64-low.c: Include nat/aarch64-linux.h.
	(aarch64_init_debug_reg_state): Make it extern.
	(aarch64_linux_prepare_to_resume): Remove.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Make aarch64_linux_prepare_to_resume the same on GDB and GDBserver
@ 2015-08-25 12:05 sergiodj+buildbot
  2015-08-26 18:33 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-25 12:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f6011a1c84b1bd616617bfde84dca63f250c950d ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: f6011a1c84b1bd616617bfde84dca63f250c950d

Make aarch64_linux_prepare_to_resume the same on GDB and GDBserver

gdb:

2015-08-25  Yao Qi  <yao.qi@linaro.org>

	* aarch64-linux-nat.c (aarch64_linux_prepare_to_resume): Use
	lwp_arch_private_info and ptid_of_lwp.

gdb/gdbserver:

2015-08-25  Yao Qi  <yao.qi@linaro.org>

	* linux-aarch64-low.c (aarch64_linux_prepare_to_resume): Use
	lwp_arch_private_info and ptid_of_lwp.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Remove some comments in debug_reg_change_callback
@ 2015-08-25 11:05 sergiodj+buildbot
  2015-08-25 22:16 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-25 11:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 31a43dd5e1cfb8bb387885b3f641d6d2c04ac5dd ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 31a43dd5e1cfb8bb387885b3f641d6d2c04ac5dd

Remove some comments in debug_reg_change_callback

gdb/gdbserver:

2015-08-25  Yao Qi  <yao.qi@linaro.org>

	* linux-aarch64-low.c (debug_reg_change_callback): Remove comments.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] gdbserver crashes when multiprocess extensions aren't supported
@ 2015-08-24 19:25 sergiodj+buildbot
  2015-08-25 15:27 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-24 19:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3d40fbb53b4478d94b6fa5abad0796cec5d5db49 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 3d40fbb53b4478d94b6fa5abad0796cec5d5db49

gdbserver crashes when multiprocess extensions aren't supported

Ref: https://sourceware.org/ml/gdb-patches/2015-08/msg00675.html

If multiprocess extensions are off (because specific gdbserver port
doesn't support them), then when gdbserver doesn't have a thread
selected yet, and GDB sends Hg packet to select one, gdbserver
crashes.  That's because extracting the desired thread id out of the
packet that GDB sent depends on the current thread to fill in the
missing process id ...  Fix this by getting the process id from the
first (and only) process in the processes list instead.

The GNU/Linux port doesn't trip on this because it always runs with
multiprocess extensions enabled.  To make it easier to catch such
regressions going forward, this commit also adds a new smoke test that
spawns gdbserver, connects to it and runs to main with the
multiprocess extensions force-disabled.

gdb/gdbserver/ChangeLog:
2015-08-24  Pedro Alves  <palves@redhat.com>

	* inferiors.c (get_first_process): New function.
	* inferiors.h (get_first_process): New declaration.
	* remote-utils.c (read_ptid): Default to the first process in the
	list, instead of to the current thread's process.

gdb/testsuite/ChangeLog:
2015-08-24  Pedro Alves  <palves@redhat.com>

	* gdb.server/connect-without-multi-process.c: New file.
	* gdb.server/connect-without-multi-process.exp: New file.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] gdb/testsuite/: garbage collect a few references to dead targets
@ 2015-08-24 15:27 sergiodj+buildbot
  2015-08-24 22:29 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-24 15:27 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0ebbc52beef41c725f75b22c80a37fee00303bb0 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 0ebbc52beef41c725f75b22c80a37fee00303bb0

gdb/testsuite/: garbage collect a few references to dead targets

gdb/testsuite/ChangeLog:
2015-08-24  Pedro Alves  <palves@redhat.com>

	* config/m32r-stub.exp: Remove file.
	* gdb.base/call-ar-st.exp: Remove reference to sparclet.
	* gdb.base/call-rt-st.exp: Likewise.
	* gdb.base/call-strs.exp: Likewise.
	* gdb.base/default.exp: Remove references to h8300-*-hms and
	*-*-udi*.
	* gdb.base/funcargs.exp: Remove reference to sparclet-*-*.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Delete the remaining ROM monitor targets
@ 2015-08-24 14:55 sergiodj+buildbot
  2015-08-24 20:02 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-24 14:55 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 40e0b27177e747600d3ec186458fe0e482a1cf77 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 40e0b27177e747600d3ec186458fe0e482a1cf77

Delete the remaining ROM monitor targets

Ref: https://sourceware.org/ml/gdb/2015-07/msg00011.html

All of these targets use gdb/monitor.c, which has bit rotted
years ago (I'd guess around ~6), and nobody seems to
have noticed:

 | target         | source               |
 |----------------+----------------------|
 | target dbug    | gdb/dbug-rom.c       |
 | target picobug | gdb/microblaze-rom.c |
 | target dink32  | gdb/dink32-rom.c     |
 | target m32r    | gdb/m32r-rom.c       |
 | target mon2000 | gdb/m32r-rom.c       |
 | target ppcbug  | gdb/ppcbug-rom.c     |

This deletes them, along with finally removing monitor.c.

A manual update will be done separately.

gdb/ChangeLog:
2015-08-24  Pedro Alves  <palves@redhat.com>

	* NEWS: Mention removed support for the various ROM monitors.
	* Makefile.in (ALL_TARGET_OBS): Remove dbug-rom.o, dink32-rom.o,
	ppcbug-rom.o, m32r-rom.o, dsrec.o and monitor.o from gdb_target_obs.
	* configure.tgt (h8300-*-*): Remove monitor.o and m32r-rom.o from
	gdb_target_obs.
	(m68*-*-*): Remove monitor.o dbug-rom.o and dsrec.o from
	gdb_target_obs.
	(microblaze*-linux-*): Remove microblaze-rom.o, monitor.o and
	dsrec.o from gdb_target_obs.
	(microblaze*-*-*): Remove microblaze-rom.o, monitor.o and dsrec.o
	from gdb_target_obs.
	(powerpc-*-lynx*178): Remove monitor.o and dsrec.o from
	gdb_target_obs.
	(powerpc*-*-*): Remove monitor.o, dsrec.o, ppcbug-rom.o and
	dink32-rom.o from gdb_target_obs.
	(sh*-*-linux*): Remove monitor.o and dsrec.o from gdb_target_obs.
	(sh*): Remove monitor.o and dsrec.o from gdb_target_obs.
	* dbug-rom.c, dink32-rom.c, dsrec.c, m32r-rom.c, microblaze-rom.c,
	monitor.c, monitor.h, ppcbug-rom.c, srec.h: Delete files.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Missing parts of fixes for in-tree libiconv
@ 2015-08-24 10:41 sergiodj+buildbot
  2015-08-24 12:28 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-24 10:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cfe101c6a8227b6b97ed2da85895db7d6083bfa6 ***

Author: Yaakov Selkowitz <yselkowi@redhat.com>
Branch: master
Commit: cfe101c6a8227b6b97ed2da85895db7d6083bfa6

Missing parts of fixes for in-tree libiconv

(Commit d23d1dff missed pushing the config/iconv.m4 change, and to
regenerate binutils' configure.)

Original description:

This is the second in a series of patches to make a build with an
in-tree GNU libiconv work as designed.

Currently GDB is the only toolchain component which actually uses an
in-tree libiconv.  This patch modifies the common AM_ICONV to use an
in-tree libiconv when present and not already provided by libc.
(GDB's workaround uses an in-tree libiconv even when libc provides
iconv(3); I'm not sure when or why that would be desirable.)

config/ChangeLog:
2015-08-24  Yaakov Selkowitz  <yselkowi@redhat.com>

	* iconv.m4 (AM_ICONV_LINK): Use in-tree libiconv when present.

binutils/ChangeLog:
2015-08-24  Yaakov Selkowitz  <yselkowi@redhat.com>

	* configure: Regenerate.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Reorder enum output_type for better code generation
@ 2015-08-23 14:03 sergiodj+buildbot
  2015-08-23 15:14 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  2015-08-23 18:23 ` sergiodj+buildbot
  0 siblings, 2 replies; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-23 14:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5f329d5b1409dfb86e3eb6a22e9f84cc58c254b1 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 5f329d5b1409dfb86e3eb6a22e9f84cc58c254b1

Reorder enum output_type for better code generation

Works around a gcc bug #67328 for the most commonly used of bfd_link_pic
and bfd_link_executable.

	* bfdlink.h (enum output_type): Reorder enum.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
[parent not found: <99b0bb12cdb22489b403df6afe992b81bebbd9ec@gdb-build>]
[parent not found: <f8904751117dc8d4d04e5c5286b71b854e6ebba5@gdb-build>]
[parent not found: <049412e38f9ac04654940173db63a37ebca9bfc3@gdb-build>]
* [binutils-gdb] Uninitialized vd_nodename
@ 2015-08-22  7:09 sergiodj+buildbot
  2015-08-22 20:02 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-22  7:09 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 595bce7595e076391e7147b0c6db57a8edf2e406 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 595bce7595e076391e7147b0c6db57a8edf2e406

Uninitialized vd_nodename

Belt and braces fix.  Either of the changes here is sufficient to
ensure vd_nodename is initialized properly.

	* elf.c (_bfd_elf_slurp_version_tables): Always init vd_nodename.
	Don't copy fields not set by _bfd_elf_swap_verdef_in.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] tui: don't overwrite a secondary prompt that was given no input
@ 2015-08-21 20:38 sergiodj+buildbot
  2015-08-22 13:38 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-21 20:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 948578a989f8c666c9b0e92c9a50906724921f14 ***

Author: Patrick Palka <patrick@parcs.ath.cx>
Branch: master
Commit: 948578a989f8c666c9b0e92c9a50906724921f14

tui: don't overwrite a secondary prompt that was given no input

This patch fixes the following bug in TUI:

  (gdb) break foo
  No symbol table is loaded.  Use the "file" command.
  Make breakpoint pending on future shared library load? (y or [n]) <ENTER>

By submitting an empty command line to a secondary prompt, the line
corresponding to the secondary prompt is undesirably cleared and
overwritten.  Outside of a secondary prompt, clearing the prompt line
after submitting an empty command line is intended behavior which
complements GDB's repeat-command shorthand.  But inside a secondary
prompt, this behavior is undesired since the shorthand is not applicable
in that case.  We should retain the secondary-prompt line even when it's
given no input.

This patch makes sure that a prompt that was given an empty command line
is cleared and overwritten only if it's not a secondary prompt.  To
acheive this, a new predicate is defined which informs us whether the
current input handler is a secondary prompt.

gdb/ChangeLog:

	* top.h (gdb_in_secondary_prompt_p): Declare.
	* top.c (gdb_secondary_prompt_depth): Define.
	(gdb_in_secondary_prompt_p): Define.
	(gdb_readline_wrapper_cleanup): Decrement
	gdb_secondary_prompt_depth.
	(gdb_readline_wrapper): Increment gdb_secondary_prompt_depth.
	* tui/tui-io.c (tui_getc): Don't clear the prompt line if we
	are in a secondary prompt.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Use tui_putc to output newline entered by the user
@ 2015-08-21 20:30 sergiodj+buildbot
  2015-08-22 11:54 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-21 20:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7a8bcb88e77380fe9672b4f10777cc9e48011dd4 ***

Author: Patrick Palka <patrick@parcs.ath.cx>
Branch: master
Commit: 7a8bcb88e77380fe9672b4f10777cc9e48011dd4

Use tui_putc to output newline entered by the user

This is necessary to make sure that start_line is updated after a
command has been entered.  Usually, start_line gets updated anyway
because most commands output text, and outputting text is done through
the function tui_puts, which updates start_line.  However if a command
does not output text, then tui_puts will not get called and start_line
will not get updated in time for the next prompt to be displayed.

One can observe this bug by executing the command "delete" within TUI.
After executing, the prompt line

  (gdb) delete

gets overwritten by the next prompt.  With this patch, the prompt line
gets preserved.

gdb/ChangeLog:

	* tui/tui-io.c (tui_getc): Use tui_putc instead of waddch to
	emit the newline.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix gdbserver crash exposed by gdb.threads/process-dies-while-handling-bp.exp
@ 2015-08-21 19:24 sergiodj+buildbot
  2015-08-22 10:06 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-21 19:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 465a859e0a991d3bfe8a9ee65a29a223c42e2ce7 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 465a859e0a991d3bfe8a9ee65a29a223c42e2ce7

Fix gdbserver crash exposed by gdb.threads/process-dies-while-handling-bp.exp

Running that test in a loop, I found a gdbserver core dump with the
following back trace:

 Core was generated by `../gdbserver/gdbserver --once --multi :2346'.
 Program terminated with signal SIGSEGV, Segmentation fault.
 #0  0x0000000000406ab6 in inferior_regcache_data (inferior=0x0) at src/gdb/gdbserver/inferiors.c:236
 236       return inferior->regcache_data;
 (gdb) up
 #1  0x0000000000406d7f in get_thread_regcache (thread=0x0, fetch=1) at src/gdb/gdbserver/regcache.c:31
 31        regcache = (struct regcache *) inferior_regcache_data (thread);
 (gdb) bt
 #0  0x0000000000406ab6 in inferior_regcache_data (inferior=0x0) at src/gdb/gdbserver/inferiors.c:236
 #1  0x0000000000406d7f in get_thread_regcache (thread=0x0, fetch=1) at src/gdb/gdbserver/regcache.c:31
 #2  0x0000000000409271 in prepare_resume_reply (buf=0x20dd593 "", ptid=..., status=0x20edce0) at src/gdb/gdbserver/remote-utils.c:1147
 #3  0x000000000040ab0a in vstop_notif_reply (event=0x20edcc0, own_buf=0x20dd590 "T05") at src/gdb/gdbserver/server.c:183
 #4  0x0000000000426b38 in notif_write_event (notif=0x66e6c0 <notif_stop>, own_buf=0x20dd590 "T05") at src/gdb/gdbserver/notif.c:69
 #5  0x0000000000426c55 in handle_notif_ack (own_buf=0x20dd590 "T05", packet_len=8) at src/gdb/gdbserver/notif.c:113
 #6  0x000000000041118f in handle_v_requests (own_buf=0x20dd590 "T05", packet_len=8, new_packet_len=0x7fff742c77b8)
     at src/gdb/gdbserver/server.c:2862
 #7  0x0000000000413850 in process_serial_event () at src/gdb/gdbserver/server.c:4148
 #8  0x0000000000413945 in handle_serial_event (err=0, client_data=0x0) at src/gdb/gdbserver/server.c:4196
 #9  0x000000000041a1ef in handle_file_event (event_file_desc=5) at src/gdb/gdbserver/event-loop.c:429
 #10 0x00000000004199b6 in process_event () at src/gdb/gdbserver/event-loop.c:184
 #11 0x000000000041a735 in start_event_loop () at src/gdb/gdbserver/event-loop.c:547
 #12 0x00000000004123d2 in captured_main (argc=4, argv=0x7fff742c7ac8) at src/gdb/gdbserver/server.c:3562
 #13 0x000000000041252e in main (argc=4, argv=0x7fff742c7ac8) at src/gdb/gdbserver/server.c:3631

Clearly this means that a thread pushed a stop reply in the event
queue, and then before GDB confused the event, the whole process died,
along with its thread.  But the pending thread event was left
dangling.  When GDB fetched that event, gdbserver looked up the
corresponding thread, but found NULL; not expecting this, gdbserver
crashes when it tries to read this thread's registers.

gdb/gdbserver/
2015-08-21  Pedro Alves  <palves@redhat.com>

	PR gdb/18749
	* inferiors.c (remove_thread): Discard any pending stop reply for
	this thread.
	* server.c (remove_all_on_match_pid): Rename to ...
	(remove_all_on_match_ptid): ... this.  Work with a filter ptid
	instead of a pid.
	(discard_queued_stop_replies): Change parameter to a ptid.  Now
	extern.
	(handle_v_kill, kill_inferior_callback)
	(process_serial_event): Adjust.
	(captured_main): Call initialize_notif before starting the
	program, thus before threads are created.
	* server.h (discard_queued_stop_replies): Declare.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] gdbserver: don't pick a random thread if the current thread dies
@ 2015-08-21 18:54 sergiodj+buildbot
  2015-08-22  8:55 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-21 18:54 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f0db101d9897732d6556456e542d12ecf9e12e42 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: f0db101d9897732d6556456e542d12ecf9e12e42

gdbserver: don't pick a random thread if the current thread dies

In all-stop mode, if the current thread disappears while stopping all
threads, gdbserver calls set_desired_thread(0) ['0' means "I want the
continue thread"] which just picks the first thread in the list.

This looks like a dangerous thing to do.  GDBserver continues
processing whatever it was doing, but to the wrong thread.  If
debugging more than one process, we may even pick the wrong process.
Instead, GDBserver should detect the situation and bail out of
whatever is was doing.

The backends used to pay attention to the set 'cont_thread' (the Hc
thread, used in the old way to resume threads, before vCont), but all
such 'cont_thread' checks have been eliminated meanwhile.  The
remaining implicit dependencies that I found on there being a selected
thread in the backends are in the Ctrl-C handling, which some backends
use as thread to send a signal to.  Even that seems to me to be better
handled by always using the first thread in the list or by using the
signal_pid PID.

In order to make this a systematic approach, I'm making
set_desired_thread never fallback to a random thread, and instead end
up with current_thread == NULL, like already done in non-stop mode.
Then I updated all callers to handle the situation.

I stumbled on this while fixing other bugs exposed by
gdb.threads/fork-plus-threads.exp test.  The problems I saw were fixed
in a different way, but in any case, I think the potential for
problems is more or less obvious, and the resulting code looks a bit
less magical to me.

Tested on x86-64 Fedora 20, w/ native-extended-gdbserver board.

gdb/gdbserver/ChangeLog:
2015-08-21  Pedro Alves  <palves@redhat.com>

	* linux-low.c (wait_for_sigstop): Always switch to no thread
	selected if the previously current thread dies.
	* lynx-low.c (lynx_request_interrupt): Use the first thread's
	process instead of the current thread's.
	* remote-utils.c (input_interrupt): Don't check if there's no
	current thread.
	* server.c (gdb_read_memory, gdb_write_memory): If setting the
	current thread to the general thread fails, error out.
	(handle_qxfer_auxv, handle_qxfer_libraries)
	(handle_qxfer_libraries_svr4, handle_qxfer_siginfo)
	(handle_qxfer_spu, handle_qxfer_statictrace, handle_qxfer_fdpic)
	(handle_query): Check if there's a thread selected instead of
	checking whether there's any thread in the thread list.
	(handle_qxfer_threads, handle_qxfer_btrace)
	(handle_qxfer_btrace_conf): Don't error out early if there's no
	thread in the thread list.
	(handle_v_cont, myresume): Don't set the current thread to the
	continue thread.
	(process_serial_event) <Hg handling>: Also set thread_id if the
	previous general thread is still alive.
	(process_serial_event) <g/G handling>: If setting the current
	thread to the general thread fails, error out.
	* spu-low.c (spu_resume, spu_request_interrupt): Use the first
	thread's lwp instead of the current thread's.
	* target.c (set_desired_thread): If the desired thread was not
	found, leave the current thread pointing to NULL.  Return an int
	(boolean) indicating success.
	* target.h (set_desired_thread): Change return type to int.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Make remote file transfers interruptible
@ 2015-08-21 17:27 sergiodj+buildbot
  2015-08-22  3:01 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-21 17:27 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2d7711a36720b0bc44fee20d0bf057614ead21c2 ***

Author: Gary Benson <gbenson@redhat.com>
Branch: master
Commit: 2d7711a36720b0bc44fee20d0bf057614ead21c2

Make remote file transfers interruptible

This commit makes it possible to interrupt remote file transfers.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Warn when accessing binaries from remote targets
@ 2015-08-21 17:09 sergiodj+buildbot
  2015-08-22  2:04 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-21 17:09 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4313b8c0ed5877feb5034bfff4056e1ccfe221f1 ***

Author: Gary Benson <gbenson@redhat.com>
Branch: master
Commit: 4313b8c0ed5877feb5034bfff4056e1ccfe221f1

Warn when accessing binaries from remote targets

GDB provides no indicator of progress during file operations, and can
appear to have locked up during slow remote transfers.  This commit
updates GDB to print a warning each time a file is accessed over RSP.
An additional message detailing how to avoid remote transfers is
printed for the first transfer only.

gdb/ChangeLog:

	* target.h (struct target_ops) <to_fileio_open>: New argument
	warn_if_slow.  Update comment.  All implementations updated.
	(target_fileio_open_warn_if_slow): New declaration.
	* target.c (target_fileio_open): Renamed as...
	(target_fileio_open_1): ...this.  New argument warn_if_slow.
	Pass warn_if_slow to implementation.  Update debug printing.
	(target_fileio_open): New function.
	(target_fileio_open_warn_if_slow): Likewise.
	* gdb_bfd.c (gdb_bfd_iovec_fileio_open): Use new function
	target_fileio_open_warn_if_slow.

gdb/testsuite/ChangeLog:

	* gdb.trace/pending.exp: Cope with remote transfer warnings.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix stale cleanup left by linux_mntns_access_fs
@ 2015-08-21 16:06 sergiodj+buildbot
  2015-08-21 20:31 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-21 16:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f36b87190aed31b1ef7787e5966be542e8abdb58 ***

Author: Gary Benson <gbenson@redhat.com>
Branch: master
Commit: f36b87190aed31b1ef7787e5966be542e8abdb58

Fix stale cleanup left by linux_mntns_access_fs

This commit fixes a stale cleanup left by linux_mntns_access_fs.

gdb/ChangeLog:

	* nat/linux-namespaces.c (linux_mntns_access_fs):
	Do not overwrite old_chain.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] xtensa: implement NPTL helpers
@ 2015-08-21 12:48 sergiodj+buildbot
  2015-08-21 18:45 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-21 12:48 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 40045d91812b25c88c8275b8c08d27c234b68ba8 ***

Author: Max Filippov <jcmvbkbc@gmail.com>
Branch: master
Commit: 40045d91812b25c88c8275b8c08d27c234b68ba8

xtensa: implement NPTL helpers

These changes allow debugging multithreaded NPTL xtensa applications.

2015-08-20  Max Filippov  <jcmvbkbc@gmail.com>
gdb/gdbserver/
	* configure.srv (xtensa*-*-linux*): Add srv_linux_thread_db=yes.
	* linux-xtensa-low.c (arch/xtensa.h gdb_proc_service.h): New
	#includes.
	(ps_get_thread_area): New function.

2015-08-20  Max Filippov  <jcmvbkbc@gmail.com>
gdb/
	* arch/xtensa.h: New file.
	* xtensa-linux-nat.c (gdb_proc_service.h): New #include.
	(ps_get_thread_area): New function.
	* xtensa-linux-tdep.c (xtensa_linux_init_abi): Add call to
	set_gdbarch_fetch_tls_load_module_address to enable TLS support.
	* xtensa-tdep.c (osabi.h): New #include.
	(xtensa_gdbarch_init): Call gdbarch_init_osabi to register
	xtensa-specific hooks.
	* xtensa-tdep.h (struct xtensa_elf_gregset_t): Add threadptr
	member and move the structure to arch/xtensa.h.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] PR binutils/18257: Properly decode x86/Intel mask instructions.
@ 2015-08-21 11:57 sergiodj+buildbot
  2015-08-21 16:45 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-21 11:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ab4e4ed5dabc378c06ee647afd5793513393ae3f ***

Author: Alexander Fomin <alexander.fomin@intel.com>
Branch: master
Commit: ab4e4ed5dabc378c06ee647afd5793513393ae3f

PR binutils/18257: Properly decode x86/Intel mask instructions.

opcodes/

	PR binutils/18257
	* i386-dis.c: Use MOD_TABLE for most of mask instructions.
	(MOD enum): Add MOD_VEX_W_0_0F41_P_0_LEN_1, MOD_VEX_W_1_0F41_P_0_LEN_1,
	MOD_VEX_W_0_0F41_P_2_LEN_1, MOD_VEX_W_1_0F41_P_2_LEN_1,
	MOD_VEX_W_0_0F42_P_0_LEN_1, MOD_VEX_W_1_0F42_P_0_LEN_1,
	MOD_VEX_W_0_0F42_P_2_LEN_1, MOD_VEX_W_1_0F42_P_2_LEN_1,
	MOD_VEX_W_0_0F44_P_0_LEN_1, MOD_VEX_W_1_0F44_P_0_LEN_1,
	MOD_VEX_W_0_0F44_P_2_LEN_1, MOD_VEX_W_1_0F44_P_2_LEN_1,
	MOD_VEX_W_0_0F45_P_0_LEN_1, MOD_VEX_W_1_0F45_P_0_LEN_1,
	MOD_VEX_W_0_0F45_P_2_LEN_1, MOD_VEX_W_1_0F45_P_2_LEN_1,
	MOD_VEX_W_0_0F46_P_0_LEN_1, MOD_VEX_W_1_0F46_P_0_LEN_1,
	MOD_VEX_W_0_0F46_P_2_LEN_1, MOD_VEX_W_1_0F46_P_2_LEN_1,
	MOD_VEX_W_0_0F47_P_0_LEN_1, MOD_VEX_W_1_0F47_P_0_LEN_1,
	MOD_VEX_W_0_0F47_P_2_LEN_1, MOD_VEX_W_1_0F47_P_2_LEN_1,
	MOD_VEX_W_0_0F4A_P_0_LEN_1, MOD_VEX_W_1_0F4A_P_0_LEN_1,
	MOD_VEX_W_0_0F4A_P_2_LEN_1, MOD_VEX_W_1_0F4A_P_2_LEN_1,
	MOD_VEX_W_0_0F4B_P_0_LEN_1, MOD_VEX_W_1_0F4B_P_0_LEN_1,
	MOD_VEX_W_0_0F4B_P_2_LEN_1, MOD_VEX_W_0_0F91_P_0_LEN_0,
	MOD_VEX_W_1_0F91_P_0_LEN_0, MOD_VEX_W_0_0F91_P_2_LEN_0,
	MOD_VEX_W_1_0F91_P_2_LEN_0, MOD_VEX_W_0_0F92_P_0_LEN_0,
	MOD_VEX_W_0_0F92_P_2_LEN_0, MOD_VEX_W_0_0F92_P_3_LEN_0,
	MOD_VEX_W_1_0F92_P_3_LEN_0, MOD_VEX_W_0_0F93_P_0_LEN_0,
	MOD_VEX_W_0_0F93_P_2_LEN_0, MOD_VEX_W_0_0F93_P_3_LEN_0,
	MOD_VEX_W_1_0F93_P_3_LEN_0, MOD_VEX_W_0_0F98_P_0_LEN_0,
	MOD_VEX_W_1_0F98_P_0_LEN_0, MOD_VEX_W_0_0F98_P_2_LEN_0,
	MOD_VEX_W_1_0F98_P_2_LEN_0, MOD_VEX_W_0_0F99_P_0_LEN_0,
	MOD_VEX_W_1_0F99_P_0_LEN_0, MOD_VEX_W_0_0F99_P_2_LEN_0,
	MOD_VEX_W_1_0F99_P_2_LEN_0, MOD_VEX_W_0_0F3A30_P_2_LEN_0,
	MOD_VEX_W_1_0F3A30_P_2_LEN_0, MOD_VEX_W_0_0F3A31_P_2_LEN_0,
	MOD_VEX_W_1_0F3A31_P_2_LEN_0, MOD_VEX_W_0_0F3A32_P_2_LEN_0,
	MOD_VEX_W_1_0F3A32_P_2_LEN_0, MOD_VEX_W_0_0F3A33_P_2_LEN_0,
	MOD_VEX_W_1_0F3A33_P_2_LEN_0.
	(vex_w_table): Replace terminals with MOD_TABLE entries for
	most of mask instructions.

gas/testsuite

	PR binutils/18257
	* gas/i386/disassem.s: Add mask instructions with invalid ModR/M byte.
	* gas/i386/x86-64-disassem.s: Likewise.
	* gas/i386/disassem.d: Updated.
	* gas/i386/x86-64-disassem.d: Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Add readahead cache to gdb's vFile:pread
@ 2015-08-21  9:41 sergiodj+buildbot
  2015-08-21 13:11 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-21  9:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 80152258b9dfe033828e5c5b6dc3252be1ba7a84 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 80152258b9dfe033828e5c5b6dc3252be1ba7a84

Add readahead cache to gdb's vFile:pread

This patch almost halves the time it takes to "target remote + run to
main" on a higher-latency connection.

E.g., I've got a ping time of ~85ms to an x86-64 machine on the gcc
compile farm (almost 2000km away from me), and I'm behind a ~16Mbit
ADSL.  When I connect to a gdbserver debugging itself on that machine
and run to main, it takes almost 55 seconds:

 [palves@gcc76] $ ./gdbserver :9999 ./gdbserver
 [palves@home] $ ssh -L 9999:localhost:9999 gcc76.fsffrance.org
 [palves@home] $ time ./gdb -data-directory=data-directory -ex "tar rem :9999" -ex "b main" -ex "c" -ex "set confirm off" -ex "quit"

 Pristine gdb 7.10.50.20150820-cvs gets us:
 ...
 Remote debugging using :9999
 Reading symbols from target:/home/palves/gdb/build/gdb/gdbserver/gdbserver...done.
 Reading symbols from target:/lib64/ld-linux-x86-64.so.2...(no debugging symbols found)...done.
 0x00007ffff7ddd190 in ?? () from target:/lib64/ld-linux-x86-64.so.2
 Breakpoint 1 at 0x41200c: file ../../../src/gdb/gdbserver/server.c, line 3635.
 Continuing.

 Breakpoint 1, main (argc=1, argv=0x7fffffffe3d8) at ../../../src/gdb/gdbserver/server.c:3635
 3635    ../../../src/gdb/gdbserver/server.c: No such file or directory.
 /home/palves/gdb/build/gdb/gdbserver/gdbserver: No such file or directory.

 real    0m54.803s
 user    0m0.329s
 sys     0m0.064s

While with the readahead cache added by this patch, it drops to:

 real    0m29.462s
 user    0m0.454s
 sys     0m0.054s

I added a few counters to show cache hit/miss, and got:

 readahead cache miss 142
 readahead cache hit 310

Tested on x86_64 Fedora 20.

gdb/ChangeLog:
2015-08-21  Pedro Alves  <palves@redhat.com>

	* remote.c (struct readahead_cache): New.
	(struct remote_state) <readahead_cache>: New field.
	(remote_open_1): Invalidate the cache.
	(readahead_cache_invalidate, readahead_cache_invalidate_fd): New
	functions.
	(remote_hostio_pwrite): Invalidate the readahead cache.
	(remote_hostio_pread): Rename to ...
	(remote_hostio_pread_vFile): ... this.
	(remote_hostio_pread_from_cache): New function.
	(remote_hostio_pread): Reimplement.
	(remote_hostio_close): Invalidate the readahead cache.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] procfs.c: Include "filestuff.h"
@ 2015-08-21  8:24 sergiodj+buildbot
  2015-08-21  9:35 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-21  8:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 88fc5eb7e23af132eacb895e475b31be0f7623e6 ***

Author: Marcin Cieslak <saper@saper.info>
Branch: master
Commit: 88fc5eb7e23af132eacb895e475b31be0f7623e6

procfs.c: Include "filestuff.h"

Fixes implicit function declaration
error in gdb/procfs.c:4927 about undeclared
make_cleanup_close().

gdb/ChangeLog:

	PR build/18843
	* procfs.c: Include "filestuff.h".


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Remove fields curch and cur_line from TUI_CMD_WIN
@ 2015-08-21  3:18 sergiodj+buildbot
  2015-08-21  4:31 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-21  3:18 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6f1cb6eac2f28c6e1cb49c011f2b916afb90b4ff ***

Author: Patrick Palka <patrick@parcs.ath.cx>
Branch: master
Commit: 6f1cb6eac2f28c6e1cb49c011f2b916afb90b4ff

Remove fields curch and cur_line from TUI_CMD_WIN

These fields are currently used to track the location of the cursor
inside the command window.  But their usefulness is questionable because
ncurses already internally keeps track of the location of the cursor,
whose coordinates we can query using the functions getyx(), getcurx() or
getcury().  It is an unnecessary pain to keep these fields in sync with
ncurses, and their meaning is not well-defined anyway.  For instance, it
is not clear whether the coordinates held in these fields are
authoritative, or whether the coordinates reported by ncurses are.

So to keep things simple, this patch removes these fields and replaces
existing reads of these fields with calls to the appropriate ncurses
querying functions, and replaces writes to these fields with calls to
wmove() (when necessary and applicable).

In the function tui_cont_sig(), I removed the call to wmove() entirely
because moving to (start_line, curch) makes no sense.  The move should
have been to (cur_line, curch) -- which would now be a no-op.

Tested on x86_64 Fedora 22, no obvious regressions.

gdb/ChangeLog:

	* tui/tui-data.h (tui_command_info): Remove fields cur_line and
	curch.
	* tui/tui-data.c (tui_clear_win_detail) [CMD_WIN]: Don't set
	cur_line or curch, instead call wmove().
	(init_win_info) [CMD_WIN]: Likewise.
	* tui/tui-io.c (tui_puts): Likewise. Don't read cur_line,
	instead call getcury().
	(tui_redisplay_readline): Don't set cur_line or curch.
	(tui_mld_erase_entire_line): Don't read cur_line, instead call
	getcury().
	(tui_cont_sig): Remove call to wmove.
	(tui_getc): Don't read cur_line or curch, instead call getcury()
	or getyx().  Don't set curch.
	* tui/tui-win.c (make_visible_with_new_height) [CMD_WIN]: Don't
	set cur_line or curch.  Always move cursor to (0,0).


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix gdb.server/solib-list.exp native-extended-gdbserver regression
@ 2015-08-20 19:30 sergiodj+buildbot
  2015-08-20 20:47 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-20 19:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0e433b32028e65f1f2f13e7c0d26061a37b7d583 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 0e433b32028e65f1f2f13e7c0d26061a37b7d583

Fix gdb.server/solib-list.exp native-extended-gdbserver regression

Commit 221e1a37 (remote non-stop: Process initially stopped threads
before other commands) caused a test regression when testing with the
native-extended-gdbserver board:

  FAIL: gdb.server/solib-list.exp: non-stop 1: non-stop interior stop (timeout)

This "interior stop" now happens before "target remote" prints the
prompt, so we should no longer explicitly expect it.

gdb/testsuite/ChangeLog:
2015-08-20  Pedro Alves  <palves@redhat.com>

	* gdb.server/solib-list.exp: No longer expect an interior stop in
	non-stop mode.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] remote non-stop: Process initially stopped threads before other commands
@ 2015-08-20 17:48 sergiodj+buildbot
  2015-08-20 19:04 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-20 17:48 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 221e1a37cd14f7c98b4ea1ab24bd721a8b144711 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 221e1a37cd14f7c98b4ea1ab24bd721a8b144711

remote non-stop: Process initially stopped threads before other commands

The main motivation for this is making non-stop / all-stop behave
similarly on initial connection, in order to move in the direction of
reimplementing all-stop mode with the remote target always running in
non-stop mode.

When we connect to a remote target in non-stop mode, we may find
threads either running or already stopped.  The act of connecting
itself does not force threads to stop.  To handle that, the remote
non-stop connection is currently roughly like this:

 #1 - Fetch list of remote threads (qXfer:threads:read, qfThreadInfo,
    etc).  All threads are assumed to be running until the target
    reports an asynchronous stop reply for them.

 #2 - Fetch the initial set of threads that were already stopped, with
    the '?'  packet.  (In non-stop, this is coupled with the vStopped
    mechanism to be able to retrieve the status of more than one
    thread.)

The stop replies fetched in #2 are placed in the pending stop reply
queue, and left for the regular event loop to process.  That is,
"target remote" finishes and returns _before_ those stops are
processed.

That means that it's possible to have GDB process further commands
before the initial set of stopped threads is reported to the user.

E.g., before the patch, note how the prompt is printed before the
frame:

 Remote debugging using :9999
 (gdb)
 [Thread 15296] #1 stopped.
 0x0000003615a011f0 in ?? ()

Even though thread #1 was not running, for a moment, the user can see
it as such:

 $ gdb a.out -ex "set non-stop 1" -ex "tar rem :9999"  -ex "info threads" -ex "info registers"
 Remote debugging using :9999
   Id   Target Id         Frame
 * 1    Thread 4772       (running)
 Target is executing.                 <<<<<<< info registers
 (gdb)
 [Thread 4772] #1 stopped.
 0x0000003615a011f0 in ?? ()

To fix that, this commit makes gdb process all threads found already
stopped at connection time, before giving the prompt to the user.

The fix takes a cue from fork-child.c:startup_inferior [1], and
processes the events locally in remote.c, avoiding the whole
wait_for_inferior/handle_inferior_event path.  I decided to try this
approach after noticing that:

 - several cases in handle_inferior_event miss checking stop_soon.
 - we don't want to fetch the thread list in normal_stop.

and trying to fix them was resulting in sprinkling stop_soon checks in
many places, and uglifying normal_stop even more.

While with this patch, I'm avoiding changing GDB's output other than
when the prompt is printed, I think this approach is more flexible if
we do want to change it.  And also, it's likely easier to get rid of
the MI *running event that is still sent for threads that are
initially found stopped, if we want to.

This happens to fix the testsuite too.  All non-stop tests are racy
against "target remote" / gdbserver testing currently.  That is,
sometimes the tests run, but other times they're just skipped without
any indication of PASS/FAIL.  When that happens, the logs show:

 target remote localhost:2346
 Remote debugging using localhost:2346
 (gdb)
 [Thread 25418] #1 stopped.
 0x0000003615a011f0 in ?? ()
 ^CQuit
 (gdb) Remote debugging from host 127.0.0.1
 Killing process(es): 25418
 monitor exit
 (gdb) Remote connection closed
 (gdb) testcase /home/pedro/gdb/mygit/build/../src/gdb/testsuite/gdb.threads/multi-create-ns-info-thr.exp completed in 61 seconds

The trouble here is that there's output after the prompt, and the
regex in question doesn't expect that:

   -re "Remote debugging using .*$serialport_re.*$gdb_prompt $" {
	verbose "Set target to $targetname"
	return 0
    }

[1] - before startup_inferior was added, we'd go through
wait_for_inferior/handle_inferior_event while going through the shell,
and that turned out problematic.

Tested on x86_64 Fedora 20, gdbserver.

gdb/ChangeLog:
2015-08-20  Pedro Alves  <palves@redhat.com>

	* infrun.c (print_target_wait_results): Make extern.
	* infrun.h (print_target_wait_results): Declare.
	* remote.c (set_stop_requested_callback): Delete.
	(process_initial_stop_replies): New function.
	(remote_start_remote): Use it.
	(stop_reply_queue_length): New function.

gdb/testsuite/ChangeLog:
2015-08-20  Pedro Alves  <palves@redhat.com>

	* gdb.server/connect-stopped-target.c: New file.
	* gdb.server/connect-stopped-target.exp: New file.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix language of compilation unit with unknown file extension
@ 2015-08-20 11:45 sergiodj+buildbot
  2015-08-20 14:31 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-20 11:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 40e3ad0ebb0c71008b928d6d350e9258dc1dcf2a ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 40e3ad0ebb0c71008b928d6d350e9258dc1dcf2a

Fix language of compilation unit with unknown file extension

Here, in dwarfread.c:process_full_comp_unit:

      /* Set symtab language to language from DW_AT_language.  If the
	 compilation is from a C file generated by language preprocessors, do
	 not set the language if it was already deduced by start_subfile.  */
      if (!(cu->language == language_c
	    && COMPUNIT_FILETABS (cust)->language != language_c))
	COMPUNIT_FILETABS (cust)->language = cu->language;

in case start_subfile doesn't manage to deduce a language
COMPUNIT_FILETABS(cust)->language ends up as language_unknown, not
language_c.  So the condition above evals false and we never set the
language from the cu's language.

gdb/ChangeLog:
2015-08-20  Pedro Alves  <palves@redhat.com>

	* dwarf2read.c (process_full_comp_unit): To tell whether
	start_subfile managed to deduce a language, test for
	language_unknown instead of language_c.

gdb/testsuite/ChangeLog:
2015-08-20  Pedro Alves  <palves@redhat.com>

	* gdb.dwarf2/comp-unit-lang.exp: New file.
	* gdb.dwarf2/comp-unit-lang.c: New file.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [Ada] Fix parsing for expressions with attributes and characters
@ 2015-08-20  8:24 sergiodj+buildbot
  2015-08-20 12:37 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-20  8:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT af39b3270a1385027b2a5d145b9ba7564bd39f7a ***

Author: Pierre-Marie de Rodat <derodat@adacore.com>
Branch: master
Commit: af39b3270a1385027b2a5d145b9ba7564bd39f7a

[Ada] Fix parsing for expressions with attributes and characters

Before this change, trying to evaluate the following Ada expression
yielded a syntax error, even though it's completely legal:

    (gdb) p s'first = 'a'
    Error in expression, near `'.

The problem lies in the lexer (gdb/ada-lex.l): at the point we reach "'a'",
we're still in the BEFORE_QUAL_QUOTE start condition (the mechanism to
distinguish character literals from other "tick" usages: qualified
expressions and attributes), so we consider that this quote is actually a
separate "tick".

This changes resets the start condition to INITIAL in the
{TICK}[a-zA-Z][a-zA-Z]+ rule (for attributes): attributes activate this
BEFORE_QUAL_QUOTE condition and in this case the above rule is always
executed rather than the <BEFORE_QUAL_QUOTE>"'" one (in flex, it's
always the longest match that is chosen). We now have instead:

    (gdb) p s'first = 'a'
    $1 = true

gdb/ChangeLog:

	* ada-lex.l: Reset the start condition to INITIAL in the rule
	that matches attributes.

gdb/testsuite/ChangeLog:

	* gdb.ada/attr_ref_and_charlit.exp: New testcase.
	* gdb.ada/attr_ref_and_charlit/foo.adb: New file.

Tested on x86_64-linux, no regression.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] dwarf2read.c: Check type of string valued attributes prior to decoding.
@ 2015-08-19 19:00 sergiodj+buildbot
  2015-08-20 10:40 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-19 19:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7d45c7c3f692d93c3a33a043c347f1386681deb4 ***

Author: Kevin Buettner <kevinb@redhat.com>
Branch: master
Commit: 7d45c7c3f692d93c3a33a043c347f1386681deb4

dwarf2read.c: Check type of string valued attributes prior to decoding.

This change introduces a new function, dwarf2_string_attr(), which is
a wrapper for dwarf2_attr().  dwarf2read.c has been updated to
call dwarf2_string_attr in most instances where a string-valued
attribute is decoded to produce a string value.  In most cases, it
simplifies the code; in some instances, the complexity of the code
remains unchanged.

I performed this change by looking for instances where the
result of DW_STRING was used in an assignment.  Many of these
had a pattern which (roughly) looks something like this:

  struct attribute *attr = NULL;

  attr = dwarf2_attr (die, name, cu);
  if (attr != NULL && DW_STRING (attr))
    {
      const char *str;
      ...
      str = DW_STRING (attr);
      ... /* Use str in some fashion.  */
    }

Code of this form is transformed to look like this instead:

  const char *str;

  str = dwarf2_string_attr (die, name, cu)
  if (str != NULL)
    {
       ...
       /* Use str in some fashion.  */
       ...
    }

In addition to invoking dwarf2_attr() and DW_STRING(),
dwarf2_string_attr() checks to make sure that the attribute's
`form' field matches one of DW_FORM_strp, DW_FORM_string, or
DW_FORM_GNU_strp_alt.  If it does not match one of these forms,
it will return a NULL value in addition to calling complaint().

An earlier version of this patch did this type checking for one
particular instance where a string attribute was being decoded.
The situation that I was attempting to handle in that earlier patch is
this:

The Texas Instruments compiler uses the encoding for
DW_AT_MIPS_linkage_name for other purposes.  TI uses the encoding,
0x2007, for TI_AT_TI_end_line which, unlike DW_AT_MIPS_linkage_name,
does not have a string-typed value.  In this instance, GDB was attempting
to use an integer value as a string pointer, with predictable results.
(GDB would die with a segmentation fault.)

I've added a test which reproduces the problem that I was orignally
wanting to fix.  It uses DW_AT_MIPS_linkage name with an associate
value which is a string, and again, where the value is a small
integer.

My test case causes GDB to segfault in an unpatched GDB.  There
will be two PASSes in a patched GDB.

Unpatched GDB:

(gdb) ptype f
ERROR: Process no longer exists
UNRESOLVED: gdb.dwarf2/dw2-bad-mips-linkage-name.exp: ptype f
ERROR: Couldn't send ptype g to GDB.
UNRESOLVED: gdb.dwarf2/dw2-bad-mips-linkage-name.exp: ptype g

Patched GDB:

(gdb) ptype f
type = bool ()
(gdb) PASS: gdb.dwarf2/dw2-bad-mips-linkage-name.exp: ptype f
ptype g
type = bool ()
(gdb) PASS: gdb.dwarf2/dw2-bad-mips-linkage-name.exp: ptype g

I see no regressions on an x86_64 native target.

gdb/ChangeLog:

	* dwarf2read.c (dwarf2_string_attr): New function.
	(lookup_dwo_unit, process_psymtab_comp_unit_reader)
	(dwarf2_compute_name, dwarf2_physname, find_file_and_directory)
	(read_call_site_scope, namespace_name, guess_full_die_structure_name)
	(anonymous_struct_prefix, prepare_one_comp_unit): Use
	dwarf2_string_attr in place of dwarf2_attr and DW_STRING.

gdb/testsuite/ChangeLog:

	* gdb.dwarf2/dw2-bad-mips-linkage-name.c: New file.
	* gdb.dwarf2/dw2-bad-mips-linkage-name.exp: New file.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [AArch64][4/6] LD support TLSLD move/add relocation types
@ 2015-08-19 17:46 sergiodj+buildbot
  2015-08-19 23:30 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-19 17:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6ffe9a1ba36f3a896ae323e35a207b6451e8f7f9 ***

Author: Jiong Wang <jiong.wang@arm.com>
Branch: master
Commit: 6ffe9a1ba36f3a896ae323e35a207b6451e8f7f9

[AArch64][4/6] LD support TLSLD move/add relocation types

2015-08-19  Jiong Wang  <jiong.wang@arm.com>

bfd/
  PR ld/18276
  * elfnn-aarch64.c (IS_AARCH64_TLS_RELOC): Recognize new relocation
  types, including BFD_RELOC_AARCH64_TLSLD_ADD_DTPREL_HI12,
  BFD_RELOC_AARCH64_TLSLD_MOVW_DTPREL_G0,
  BFD_RELOC_AARCH64_TLSLD_MOVW_DTPREL_G0_NC,
  BFD_RELOC_AARCH64_TLSLD_MOVW_DTPREL_G1,
  BFD_RELOC_AARCH64_TLSLD_MOVW_DTPREL_G1_NC,
  BFD_RELOC_AARCH64_TLSLD_MOVW_DTPREL_G2.
  (elfNN_aarch64_final_link_relocate): Likewise.
  * elfxx-aarch64.c (_bfd_aarch64_elf_put_addend): Likewise.
  (_bfd_aarch64_elf_resolve_relocation): Likewise.

ld/testsuite/
  * ld-aarch64/emit-relocs-87.s: New testcase.
  * ld-aarch64/emit-relocs-88.s: Likewise.
  * ld-aarch64/emit-relocs-88-overflow.s: Likewise.
  * ld-aarch64/emit-relocs-89.s: Likewise.
  * ld-aarch64/emit-relocs-90.s: Likewise.
  * ld-aarch64/emit-relocs-90-overflow.s: Likewise.
  * ld-aarch64/emit-relocs-523.s: Likewise.
  * ld-aarch64/emit-relocs-524.s: Likewise.
  * ld-aarch64/emit-relocs-525.s: Likewise.
  * ld-aarch64/emit-relocs-527.s: Likewise.
  * ld-aarch64/emit-relocs-526.s: Likewise.
  * ld-aarch64/emit-relocs-528.s: Likewise.
  * ld-aarch64/emit-relocs-528-overflow.s: Likewise.
  * ld-aarch64/emit-relocs-87.d: New expectation file.
  * ld-aarch64/emit-relocs-88.d: Likewise.
  * ld-aarch64/emit-relocs-88-overflow.d: Likewise.
  * ld-aarch64/emit-relocs-89.d: Likewise.
  * ld-aarch64/emit-relocs-90.d: Likewise.
  * ld-aarch64/emit-relocs-90-overflow.d: Likewise.
  * ld-aarch64/emit-relocs-91.d: Likewise.
  * ld-aarch64/emit-relocs-523.d: Likewise.
  * ld-aarch64/emit-relocs-524.d: Likewise.
  * ld-aarch64/emit-relocs-525.d: Likewise.
  * ld-aarch64/emit-relocs-526.d: Likewise.
  * ld-aarch64/emit-relocs-527.d: Likewise.
  * ld-aarch64/emit-relocs-528.d: Likewise.
  * ld-aarch64/emit-relocs-528-overflow.d: Likewise.
  * ld-aarch64/aarch64-elf.exp: Run new testcases.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [AArch64][3/6] GAS support TLSLD move/add relocation types
@ 2015-08-19 17:17 sergiodj+buildbot
  2015-08-19 21:41 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-19 17:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 49df5539f9070c01128135a7d63f44b2efc4de6a ***

Author: Jiong Wang <jiong.wang@arm.com>
Branch: master
Commit: 49df5539f9070c01128135a7d63f44b2efc4de6a

[AArch64][3/6] GAS support TLSLD move/add relocation types

2015-08-19  Jiong Wang  <jiong.wang@arm.com>

bfd/
  * reloc.c (BFD_RELOC_AARCH64_TLSLD_ADD_DTPREL_HI12,
  BFD_RELOC_AARCH64_TLSLD_MOVW_DTPREL_G0,
  BFD_RELOC_AARCH64_TLSLD_MOVW_DTPREL_G0_NC,
  BFD_RELOC_AARCH64_TLSLD_MOVW_DTPREL_G1,
  BFD_RELOC_AARCH64_TLSLD_MOVW_DTPREL_G1_NC,
  BFD_RELOC_AARCH64_TLSLD_MOVW_DTPREL_G2): New entries.
  * elfnn-aarch64.c (elfNN_aarch64_howto_table): Likewise.
  * bfd-in2.h: Regenerate.
  * libbfd.h: Regenerate.

gas/
  * config/tc-aarch64.c (reloc_table): New relocation modifiers,
  "dtprel_hi12", "dtprel_g0", "dtprel_g0_nc", "dtprel_g1",
  "dtprel_g1_nc", "dtprel_g2".
  (md_apply_fix): Support new relocation types.
  (aarch64_force_relocation): Likewise.
  (process_movw_reloc_info): Likewise.

gas/testsuite/
  * gas/aarch64/reloc-dtprel_g0.s: New testcase.
  * gas/aarch64/reloc-dtprel_g0-ilp32.s: Likewise.
  * gas/aarch64/reloc-dtprel_g0_nc.s: Likewise.
  * gas/aarch64/reloc-dtprel_g0_nc-ilp32.s: Likewise.
  * gas/aarch64/reloc-dtprel_g1.s: Likewise.
  * gas/aarch64/reloc-dtprel_g1-ilp32.s: Likewise.
  * gas/aarch64/reloc-dtprel_g1_nc.s: Likewise.
  * gas/aarch64/reloc-dtprel_g2.s: Likewise.
  * gas/aarch64/reloc-dtprel_hi12.s: Likewise.
  * gas/aarch64/reloc-dtprel_hi12-ilp32.s: Likewise.
  * gas/aarch64/reloc-dtprel_g0.d: New expectation file.
  * gas/aarch64/reloc-dtprel_g0-ilp32.d: Likewise.
  * gas/aarch64/reloc-dtprel_g0_nc.d: Likewise.
  * gas/aarch64/reloc-dtprel_g0_nc-ilp32.d: Likewise.
  * gas/aarch64/reloc-dtprel_g1.d: Likewise.
  * gas/aarch64/reloc-dtprel_g1-ilp32.d: Likewise.
  * gas/aarch64/reloc-dtprel_g1_nc.d: Likewise.
  * gas/aarch64/reloc-dtprel_g2.d: Likewise.
  * gas/aarch64/reloc-dtprel_hi12.d: Likewise.
  * gas/aarch64/reloc-dtprel_hi12-ilp32.d: Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [AArch64][6/6] LD support TLSLD load/store relocation types
@ 2015-08-19 16:50 sergiodj+buildbot
  2015-08-20  8:57 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-19 16:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 07c9aa07cdcf00eff8e186f3ca1779e5e3ffdb75 ***

Author: Jiong Wang <jiong.wang@arm.com>
Branch: master
Commit: 07c9aa07cdcf00eff8e186f3ca1779e5e3ffdb75

[AArch64][6/6] LD support TLSLD load/store relocation types

2015-08-19  Jiong Wang  <jiong.wang@arm.com>

bfd/
  * elfnn-aarch64.c (IS_AARCH64_TLS_RELOC): Recognize new relocation
  types, including BFD_RELOC_AARCH64_TLSLD_LDST16_DTPREL_LO12,
  BFD_RELOC_AARCH64_TLSLD_LDST16_DTPREL_LO12_NC,
  BFD_RELOC_AARCH64_TLSLD_LDST32_DTPREL_LO12,
  BFD_RELOC_AARCH64_TLSLD_LDST32_DTPREL_LO12_NC,
  BFD_RELOC_AARCH64_TLSLD_LDST64_DTPREL_LO12,
  BFD_RELOC_AARCH64_TLSLD_LDST64_DTPREL_LO12_NC,
  BFD_RELOC_AARCH64_TLSLD_LDST8_DTPREL_LO12,
  BFD_RELOC_AARCH64_TLSLD_LDST8_DTPREL_LO12_NC.
  (elfNN_aarch64_final_link_relocate): Likewise.
  * elfxx-aarch64.c (_bfd_aarch64_elf_put_addend): Likewise.
  (_bfd_aarch64_elf_resolve_relocation): Likewise.

ld/testsuite/
  * ld-aarch64/emit-relocs-531.s: New testcase.
  * ld-aarch64/emit-relocs-531-overflow.s: Likewise.
  * ld-aarch64/emit-relocs-532.s: Likewise.
  * ld-aarch64/emit-relocs-533.s: Likewise.
  * ld-aarch64/emit-relocs-533-overflow.s: Likewise.
  * ld-aarch64/emit-relocs-534.s: Likewise.
  * ld-aarch64/emit-relocs-535.s: Likewise.
  * ld-aarch64/emit-relocs-535-overflow.s: Likewise.
  * ld-aarch64/emit-relocs-536.s: Likewise.
  * ld-aarch64/emit-relocs-537.s: Likewise.
  * ld-aarch64/emit-relocs-537-overflow.s: Likewise.
  * ld-aarch64/emit-relocs-538.s: Likewise.
  * ld-aarch64/emit-relocs-531.d: New expectation file.
  * ld-aarch64/emit-relocs-531-overflow.d: Likewise.
  * ld-aarch64/emit-relocs-532.d: Likewise.
  * ld-aarch64/emit-relocs-533.d: Likewise.
  * ld-aarch64/emit-relocs-533-overflow.d: Likewise.
  * ld-aarch64/emit-relocs-534.d: Likewise.
  * ld-aarch64/emit-relocs-535.d: Likewise.
  * ld-aarch64/emit-relocs-535-overflow.d: Likewise.
  * ld-aarch64/emit-relocs-536.d: Likewise.
  * ld-aarch64/emit-relocs-537.d: Likewise.
  * ld-aarch64/emit-relocs-537-overflow.d: Likewise.
  * ld-aarch64/emit-relocs-538.d: Likewise.
  * ld-aarch64/aarch64-elf.exp: Run new testcases.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [AArch64][5/6] GAS support TLSLD load/store relocation types
@ 2015-08-19 16:42 sergiodj+buildbot
  2015-08-20  0:53 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-19 16:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4c5625238cccb048261d7ce0eb748ee5e0d67cf0 ***

Author: Jiong Wang <jiong.wang@arm.com>
Branch: master
Commit: 4c5625238cccb048261d7ce0eb748ee5e0d67cf0

[AArch64][5/6] GAS support TLSLD load/store relocation types

2015-08-19  Jiong Wang  <jiong.wang@arm.com>

bfd/
  * reloc.c: New entries, including
  BFD_RELOC_AARCH64_TLSLD_LDST16_DTPREL_LO12,
  BFD_RELOC_AARCH64_TLSLD_LDST16_DTPREL_LO12_NC,
  BFD_RELOC_AARCH64_TLSLD_LDST32_DTPREL_LO12,
  BFD_RELOC_AARCH64_TLSLD_LDST32_DTPREL_LO12_NC,
  BFD_RELOC_AARCH64_TLSLD_LDST64_DTPREL_LO12,
  BFD_RELOC_AARCH64_TLSLD_LDST64_DTPREL_LO12_NC.
  BFD_RELOC_AARCH64_TLSLD_LDST8_DTPREL_LO12,
  BFD_RELOC_AARCH64_TLSLD_LDST8_DTPREL_LO12_NC.
  * elfnn-aarch64.c (elfNN_aarch64_howto_table): Likewise.
  * bfd-in2.h: Regenerate.
  * libbfd.h: Regenerate.

gas/
  * config/tc-aarch64.c (reloc_table): New relocation types support for
  dtprel_lo12.
  (ldst_lo12_determine_real_reloc_type): Support
  BFD_RELOC_AARCH64_TLSLD_LDST16_DTPREL_LO12,
  BFD_RELOC_AARCH64_TLSLD_LDST16_DTPREL_LO12_NC,
  BFD_RELOC_AARCH64_TLSLD_LDST32_DTPREL_LO12,
  BFD_RELOC_AARCH64_TLSLD_LDST32_DTPREL_LO12_NC,
  BFD_RELOC_AARCH64_TLSLD_LDST64_DTPREL_LO12,
  BFD_RELOC_AARCH64_TLSLD_LDST64_DTPREL_LO12_NC,
  BFD_RELOC_AARCH64_TLSLD_LDST8_DTPREL_LO12,
  BFD_RELOC_AARCH64_TLSLD_LDST8_DTPREL_LO12_NC.
  (parse_operands): Likewise.
  (md_apply_fix): Likewise
  (aarch64_force_relocation): Likewise.
  (process_movw_reloc_info): Likewise.

gas/testsuite/
  * gas/aarch64/reloc-dtprel_lo12-ldst8.s: New testcase.
  * gas/aarch64/reloc-dtprel_lo12_nc-ldstc.s: Likewise.
  * gas/aarch64/reloc-dtprel_lo12-ldst16.s: Likewise.
  * gas/aarch64/reloc-dtprel_lo12_nc-ldst16.s: Likewise.
  * gas/aarch64/reloc-dtprel_lo12-ldst32.s: Likewise.
  * gas/aarch64/reloc-dtprel_lo12_nc-ldst32.s: Likewise.
  * gas/aarch64/reloc-dtprel_lo12-ldst64.s: Likewise.
  * gas/aarch64/reloc-dtprel_lo12_nc-ldst64.s: Likewise.
  * gas/aarch64/reloc-dtprel_lo12-ldst8.d: New expectation file.
  * gas/aarch64/reloc-dtprel_lo12_nc-ldst8.d: Likewise.
  * gas/aarch64/reloc-dtprel_lo12-ldst16.d: Likewise.
  * gas/aarch64/reloc-dtprel_lo12_nc-ldst16.d: Likewise.
  * gas/aarch64/reloc-dtprel_lo12-ldst32.d: Likewise.
  * gas/aarch64/reloc-dtprel_lo12_nc-ldst32.d: Likewise.
  * gas/aarch64/reloc-dtprel-lo12-ldst64.d: Likewise.
  * gas/aarch64/reloc-dtprel_lo12_nc-ldst64.d: Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [AArch64][2/6] LD support BFD_RELOC_AARCH64_TLSLD_ADD_DTPREL_LO12_NC
@ 2015-08-19 16:18 sergiodj+buildbot
  2015-08-19 20:30 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-19 16:18 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 753999c1ec8fa76bd5ed5509d1e5909d010e80ee ***

Author: Jiong Wang <jiong.wang@arm.com>
Branch: master
Commit: 753999c1ec8fa76bd5ed5509d1e5909d010e80ee

[AArch64][2/6] LD support BFD_RELOC_AARCH64_TLSLD_ADD_DTPREL_LO12_NC

2015-08-19  Jiong Wang  <jiong.wang@arm.com>

bfd/
  * elfnn-aarch64.c (IS_AARCH64_TLS_RELOC): Recognize
  BFD_RELOC_AARCH64_TLSLD_ADD_DTPREL_LO12_NC.
  (aarch64_reloc_got_type): Likewise.
  (elfNN_aarch64_final_link_relocate): Likewise.
  (elfNN_aarch64_relocate_section): Likewise.
  * elfxx-aarch64.c (_bfd_aarch64_elf_put_addend): Likewise.
  (_bfd_aarch64_elf_resolve_relocation): Likewise.

ld/testsuite/
  * ld-aarch64/emit-relocs-530.s: New testcase.
  * ld-aarch64/emit-relocs-92.s: Likewise.
  * ld-aarch64/emit-relocs-530.d: New expectation file.
  * ld-aarch64/emit-relocs-92.d: Likewise.
  * ld-aarch64/aarch64-elf.exp: Run new testcases.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [AArch64][1/6] GAS support BFD_RELOC_AARCH64_TLSLD_ADD_DTPREL_LO12_NC
@ 2015-08-19 16:10 sergiodj+buildbot
  2015-08-19 18:28 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-19 16:10 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 13289c10e20281adf480d9822861412a7ade721d ***

Author: Jiong Wang <jiong.wang@arm.com>
Branch: master
Commit: 13289c10e20281adf480d9822861412a7ade721d

[AArch64][1/6] GAS support BFD_RELOC_AARCH64_TLSLD_ADD_DTPREL_LO12_NC

2015-08-19  Jiong Wang  <jiong.wang@arm.com>

bfd/
  * reloc.c (BFD_RELOC_AARCH64_TLSLD_ADD_DTPREL_LO12_NC): New entry.
  * bfd-in2.h: Regenerate.
  * libbfd.h: Regenerate.
  * elfnn-aarch64.c (elfNN_aarch64_howto_table): New entry for
  BFD_RELOC_AARCH64_TLSLD_ADD_DTPREL_LO12_NC.

gas/
  * config/tc-aarch64.c (reloc_table): New relocation modifiers.
  (md_apply_fix): Support BFD_RELOC_AARCH64_TLSLD_ADD_DTPREL_LO12_NC.
  (aarch64_force_relocation): Likewise.

gas/testsuite/
  * gas/aarch64/reloc-dtprel_lo12_nc.s: New testcase.
  * gas/aarch64/reloc-dtprel_lo12_nc-ilp32.s: Likewise.
  * gas/aarch64/reloc-dtprel_lo12_nc.d: New expectation file.
  * gas/aarch64/reloc-dtprel_lo12_nc-ilp32.d: Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Prelimit number of bytes to read in "vFile:pread:"
@ 2015-08-19 13:10 sergiodj+buildbot
  2015-08-19 14:20 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-19 13:10 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 45face3ba147a4c5f4f7e09cf10c95986b915002 ***

Author: Gary Benson <gbenson@redhat.com>
Branch: master
Commit: 45face3ba147a4c5f4f7e09cf10c95986b915002

Prelimit number of bytes to read in "vFile:pread:"

While handling "vFile:pread:" packets, gdbserver would read the
number of bytes requested regardless of whether this would fit
into the reply packet.  gdbserver would then return a packet's
worth of data and discard the remainder.  When accessing large
binaries GDB (via BFD) routinely makes large "vFile:pread:"
requests, resulting in gdbserver allocating large unnecessary
buffers and reading some portions of the file many times over.

This commit causes gdbserver to limit the number of bytes to be
read to a sensible maximum prior to allocating buffers and reading
data.

gdb/gdbserver/ChangeLog:

	* hostio.c (handle_pread): Do not attempt to read more data
	than hostio_reply_with_data can fit in a packet.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Remove link_info.pic
@ 2015-08-19  4:02 sergiodj+buildbot
  2015-08-19  9:09 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-19  4:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 64d94ba01a4f56ac10bb277e66bb00d82bd97f10 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 64d94ba01a4f56ac10bb277e66bb00d82bd97f10

Remove link_info.pic

Adding type_pie to output_type allows us to remove link_info.pic and
with some reordering of the enum, produces better code.

include/
	* bfdlink.h (enum output_type): Delete type_executable, add type_pde
	and type_pie.  Reorder.
	(struct bfd_link_info): Delete pic field.
	(bfd_link_executable, bfd_link_pde, bfd_link_pie, bfd_link_pic): Adjust.
ld/
	* emultempl/aix.em: Don't set link_info.pic.
	* emultempl/pe.em: Likewise.
	* emultempl/pep.em: Likewise.
	* emultempl/sunos.em: Likewise.
	* lexsup.c (parse_args): Likewise.  Set type_pie for -pie.
	* plugin.c (set_tv_header <LDPT_LINKER_OUTPUT>): Simplify.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Add bfd_link_pde, and simplify some tests of link_info.type
@ 2015-08-19  3:57 sergiodj+buildbot
  2015-08-19  7:16 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-19  3:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3cbc1e5e68341e53a03fe7e9d38fc02e0d78c418 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 3cbc1e5e68341e53a03fe7e9d38fc02e0d78c418

Add bfd_link_pde, and simplify some tests of link_info.type

include/
	* bfdlink.h (bfd_link_pde): Define.
bfd/
	* elf-s390-common.c: Simplify expressions using
	bfd_linke_executable, bfd_link_pie and bfd_link_pic.
	* elf32-arm.c: Likewise.
	* elf32-bfin.c: Likewise.
	* elf32-frv.c: Likewise.
	* elf32-m68k.c: Likewise.
	* elf32-nios2.c: Likewise.
	* elf32-ppc.c: Likewise.
	* elf32-s390.c: Likewise.
	* elf32-sh.c: Likewise.
	* elf64-alpha.c: Likewise.
	* elf64-ppc.c: Likewise.
	* elf64-s390.c: Likewise.
	* elflink.c: Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] gdbserver/linux-aarch32-low: build failure when NT_ARM_VFP not defined
@ 2015-08-18 22:51 sergiodj+buildbot
  2015-08-19  5:32 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-18 22:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 16d5f64295ccf2a8e9fe3ed350c94c38cee5a481 ***

Author: Joel Brobecker <brobecker@adacore.com>
Branch: master
Commit: 16d5f64295ccf2a8e9fe3ed350c94c38cee5a481

gdbserver/linux-aarch32-low: build failure when NT_ARM_VFP not defined

On some older versions of GNU/Linux, gdbserver now fails to build
due to an undefined reference to NT_ARM_VFP. Same issue on Android,
where this macros is undefined until Android API level 21 (Android
5.0 "Lollipop").

This patch modifies linux-aarch32-low.c to define that macros when
not already defined.

gdb/gdbserver/ChangeLog:

        * linux-aarch32-low.c (NT_ARM_VFP): Define if not already defined.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] PR mi/18833 gdb.execute ("set param value", to_string=True) will crash gdb if using MI
@ 2015-08-18 21:13 sergiodj+buildbot
  2015-08-19  3:07 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-18 21:13 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4d6cceb4e40a057dbe4d9ad94b0641d5f4725c09 ***

Author: Doug Evans <dje@google.com>
Branch: master
Commit: 4d6cceb4e40a057dbe4d9ad94b0641d5f4725c09

PR mi/18833 gdb.execute ("set param value", to_string=True) will crash gdb if using MI

gdb/ChangeLog:

	* cli/cli-logging.c (pop_output_files): Don't restore redirection
	if MI-like.
	* mi/mi-out.c: #include "vec.h".
	(ui_filep): New type.
	(DEV_VEC_P (ui_filep)): New type.
	(struct ui_out_data) <buffer, original_buffer>: Delete.
	(struct ui_out_data) <streams>: New member.
	(mi_ui_out_impl): Add data_destroy field.
	(mi_field_string, mi_field_fmt): Update.
	(mi_flush, mi_redirect, field_separator): Update.
	(mi_open, mi_close): Update.
	(mi_out_buffered, mi_out_rewind, mi_out_put): Update.
	(mi_out_data_ctor, mi_out_data_dtor): New functions.
	(mi_out_new): Call mi_out_data_ctor.

testsuite/gdb/ChangeLog:

	* lib/gdb.exp (skip_python_tests_prompt): Renamed from
	skip_python_tests.  New arg prompt_regexp.
	(skip_python_tests): New function.
	* lib/mi-support.exp (mi_skip_python_tests): New function.
	* gdb.python/py-mi-objfile-gdb.py: New file.
	* gdb.python/py-mi-objfile.c: New file.
	* gdb.python/py-mi-objfile.exp: New file.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix mis-parsing of hex register numbers in 'T' stop replies.
@ 2015-08-18 17:42 sergiodj+buildbot
  2015-08-18 23:46 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-18 17:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 26d56a939e9e54e09d46ea6e9678463ac344fa33 ***

Author: Sandra Loosemore <sandra@codesourcery.com>
Branch: master
Commit: 26d56a939e9e54e09d46ea6e9678463ac344fa33

Fix mis-parsing of hex register numbers in 'T' stop replies.

2015-08-18  Sandra Loosemore  <sandra@codesourcery.com>

	gdb/
	* remote.c (strprefix): New.
	(remote_parse_stop_reply): Use strprefix instead of strncmp
	to ensure exact match of keyword.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Return reloc_class_ifunc for reloc against IFUNC
@ 2015-08-18 17:09 sergiodj+buildbot
  2015-08-18 22:19 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-18 17:09 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cae1fbbb7e3d770702a0d7a5027b46835e6adc13 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: cae1fbbb7e3d770702a0d7a5027b46835e6adc13

Return reloc_class_ifunc for reloc against IFUNC

elf_XXX_reloc_type_class should return reloc_class_ifunc for relocation
against STT_GNU_IFUNC symbol.

bfd/

	PR ld/18841
	* elf-bfd.h (elf_link_hash_table): Add dynsym.
	* elf32-i386.c (elf_i386_reloc_type_class): Return
	reloc_class_ifunc for relocation against STT_GNU_IFUNC symbol.
	* elf64-x86-64.c (elf_x86_64_reloc_type_class): Likewise.
	* elflink.c (_bfd_elf_link_create_dynamic_sections): Set dynsym.
	(bfd_elf_size_dynsym_hash_dynstr): Use dynsym.
	(elf_final_link_info): Remove dynsym_sec.
	(elf_link_output_extsym): Replace dynsym_sec with dynsym.
	(bfd_elf_final_link): Remove reference to dynsym_sec.  Replace
	dynsym_sec with dynsym.

ld/testsuite/

	PR ld/18841
	* ld-ifunc/ifunc.exp: Add a test for PR ld/18841.
	* ld-ifunc/pr18841.out: New file.
	* ld-ifunc/pr18841a.c: Likewise.
	* ld-ifunc/pr18841b.c: Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [AArch64] Cleanup TLS relocation types which don't go through GOT table
@ 2015-08-18 16:03 sergiodj+buildbot
  2015-08-18 20:52 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-18 16:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 44b4145b723b43b175d4378c77bd79faaaa80312 ***

Author: Jiong Wang <jiong.wang@arm.com>
Branch: master
Commit: 44b4145b723b43b175d4378c77bd79faaaa80312

[AArch64] Cleanup TLS relocation types which don't go through GOT table

This patch done two types of cleanup:

  * in aarch64_reloc_got_type and elfNN_aarch64_relocate_section

    We don't need those redundant "case" check, as they can be merged
    with the "default" which just "break".

  * in elfNN_aarch64_gc_sweep_hook and elfNN_aarch64_check_relocs

    All TLS local executable relocations and some local dynamic
    relocations (those calculate module offset) actually don't need GOT
    entry, so remove them from GOT entry counting.

2015-08-18  Jiong Wang  <jiong.wang@arm.com>

bfd/
  * elfnn-aarch64.c (aarch64_reloc_got_type): Delete useless check.
  (elfNN_aarch64_relocate_section): Likewise.
  (elfNN_aarch64_gc_sweep_hook): Likewise.
  (elfNN_aarch64_check_relocs): Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] gdb: New maintenance command to disable bfd sharing.
@ 2015-08-18 13:56 sergiodj+buildbot
  2015-08-18 16:32 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-18 13:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 18989b3c5642e2ba533e02737797dcf06134229b ***

Author: Andrew Burgess <andrew.burgess@embecosm.com>
Branch: master
Commit: 18989b3c5642e2ba533e02737797dcf06134229b

gdb: New maintenance command to disable bfd sharing.

In some rare maintainer cases it is desirable to be able to disable bfd
sharing.  This patch adds new commands maintenance set/show commands for
bfd-sharing, allowing gdb's bfd cache to be turned off.

gdb/ChangeLog:

	* gdb_bfd.c (bfd_sharing): New variable.
	(show_bfd_sharing): New function.
	(gdb_bfd_open): Check bfd_sharing variable.
	(_initialize_gdb_bfd): Add new set/show command.
	* NEWS: Mention new command.

gdb/doc/ChangeLog:

	* gdb.texinfo (Maintenance Commands): Move documentation of "main
	info bfds" to...
	(File Caching): A New section.  Outline bfd caching, and add new
	description for "main set/show bfd-sharing".


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] gdb: Add debug tracing for bfd cache activity.
@ 2015-08-18 13:28 sergiodj+buildbot
  2015-08-18 18:01 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-18 13:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 566f5e3b385a99c09b5babc9f90dae93e052d52c ***

Author: Andrew Burgess <andrew.burgess@embecosm.com>
Branch: master
Commit: 566f5e3b385a99c09b5babc9f90dae93e052d52c

gdb: Add debug tracing for bfd cache activity.

This patch adds a new debug flag bfd-cache, which when set to non-zero
produces debugging log messages relating to gdb's bfd cache.

gdb/ChangeLog:

	* gdb_bfd.c (debug_bfd_cache): New variable.
	(show_bfd_cache_debug): New function.
	(gdb_bfd_open): Add debug logging.
	(gdb_bfd_ref): Likewise.
	(gdb_bfd_unref): Likewise.
	(_initialize_gdb_bfd): Add new set/show command.
	* NEWS: Mention new command.

gdb/doc/ChangeLog:

	* gdb.texinfo (File Caching): Document "set/show debug bfd-cache".


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] gdb: Improve cache matching criteria for the bfd cache.
@ 2015-08-18 13:12 sergiodj+buildbot
  2015-08-18 15:03 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-18 13:12 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c04fe68f6b94815d3f49c9aed64b2c388d45f4aa ***

Author: Andrew Burgess <andrew.burgess@embecosm.com>
Branch: master
Commit: c04fe68f6b94815d3f49c9aed64b2c388d45f4aa

gdb: Improve cache matching criteria for the bfd cache.

Within gdb open bfd objects are reused where possible if an attempt is
made to reopen a file that is already being debugged.  To spot if the on
disc file has changed gdb currently examines the mtime of the file and
compares it to the mtime of the open bfd in the cache.

A problem exists when the on disc file is being rapidly regenerated, as
happens, for example, with automated testing.  In some cases the file is
generated so quickly that the mtime appears not to change, while the on
disc file has changed.

This patch extends the bfd cache to also hold the file size of the file,
the inode of the file, and the device id of the file; gdb can then
compare filename, file size, mtime, inode, and device id to determine if
an existing bfd object can be reused.

gdb/ChangeLog:

	* gdb_bfd.c (struct gdb_bfd_data): Add size, inode, and device id
	field.
	(struct gdb_bfd_cache_search): Likewise.
	(eq_bfd): Compare the size, inode, and device id fields.
	(gdb_bfd_open): Initialise the size, inode, and device id fields.
	(gdb_bfd_ref): Likewise.
	(gdb_bfd_unref): Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Add output_type to bfd_link_info
@ 2015-08-18 13:03 sergiodj+buildbot
  2015-08-18 13:42 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-18 13:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0e1862bb401f47716446aef143b2bf7a4563f541 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 0e1862bb401f47716446aef143b2bf7a4563f541

Add output_type to bfd_link_info

The "shared" field in bfd_link_info is set for both DSO and and PIE.
There are separate fields for executable and relocatable outputs.  This
patch adds an "output_type" field:

enum output_type
{
  type_unknown = 0,
  type_executable,
  type_dll,
  type_relocatable
};

and a "pic" field to bfd_link_info to replace shared, executable and
relocatable fields so that we can use the "output_type" field to check
for output type and the "pic" field check if output is PIC.  Macros,
bfd_link_executable, bfd_link_dll, bfd_link_relocatable, bfd_link_pic
and bfd_link_pie, are provided to check for output features.

bfd/

	* bfd/aoutx.h: Replace shared, executable, relocatable and pie
	fields with bfd_link_executable, bfd_link_dll,
	bfd_link_relocatable, bfd_link_pic and bfd_link_pie.
	* bfd/bout.c: Likewise.
	* bfd/coff-alpha.c: Likewise.
	* bfd/coff-arm.c: Likewise.
	* bfd/coff-i386.c: Likewise.
	* bfd/coff-i960.c: Likewise.
	* bfd/coff-m68k.c: Likewise.
	* bfd/coff-mcore.c: Likewise.
	* bfd/coff-mips.c: Likewise.
	* bfd/coff-ppc.c: Likewise.
	* bfd/coff-rs6000.c: Likewise.
	* bfd/coff-sh.c: Likewise.
	* bfd/coff-tic80.c: Likewise.
	* bfd/coff-x86_64.c: Likewise.
	* bfd/coff64-rs6000.c: Likewise.
	* bfd/coffgen.c: Likewise.
	* bfd/cofflink.c: Likewise.
	* bfd/ecoff.c: Likewise.
	* bfd/ecofflink.c: Likewise.
	* bfd/elf-bfd.h: Likewise.
	* bfd/elf-eh-frame.c: Likewise.
	* bfd/elf-ifunc.c: Likewise.
	* bfd/elf-m10200.c: Likewise.
	* bfd/elf-m10300.c: Likewise.
	* bfd/elf-s390-common.c: Likewise.
	* bfd/elf-vxworks.c: Likewise.
	* bfd/elf.c: Likewise.
	* bfd/elf32-arm.c: Likewise.
	* bfd/elf32-avr.c: Likewise.
	* bfd/elf32-bfin.c: Likewise.
	* bfd/elf32-cr16.c: Likewise.
	* bfd/elf32-cr16c.c: Likewise.
	* bfd/elf32-cris.c: Likewise.
	* bfd/elf32-crx.c: Likewise.
	* bfd/elf32-d10v.c: Likewise.
	* bfd/elf32-dlx.c: Likewise.
	* bfd/elf32-epiphany.c: Likewise.
	* bfd/elf32-fr30.c: Likewise.
	* bfd/elf32-frv.c: Likewise.
	* bfd/elf32-ft32.c: Likewise.
	* bfd/elf32-h8300.c: Likewise.
	* bfd/elf32-hppa.c: Likewise.
	* bfd/elf32-i370.c: Likewise.
	* bfd/elf32-i386.c: Likewise.
	* bfd/elf32-i860.c: Likewise.
	* bfd/elf32-ip2k.c: Likewise.
	* bfd/elf32-iq2000.c: Likewise.
	* bfd/elf32-lm32.c: Likewise.
	* bfd/elf32-m32c.c: Likewise.
	* bfd/elf32-m32r.c: Likewise.
	* bfd/elf32-m68hc11.c: Likewise.
	* bfd/elf32-m68hc1x.c: Likewise.
	* bfd/elf32-m68k.c: Likewise.
	* bfd/elf32-mcore.c: Likewise.
	* bfd/elf32-mep.c: Likewise.
	* bfd/elf32-metag.c: Likewise.
	* bfd/elf32-microblaze.c: Likewise.
	* bfd/elf32-moxie.c: Likewise.
	* bfd/elf32-msp430.c: Likewise.
	* bfd/elf32-mt.c: Likewise.
	* bfd/elf32-nds32.c: Likewise.
	* bfd/elf32-nios2.c: Likewise.
	* bfd/elf32-or1k.c: Likewise.
	* bfd/elf32-ppc.c: Likewise.
	* bfd/elf32-rl78.c: Likewise.
	* bfd/elf32-rx.c: Likewise.
	* bfd/elf32-s390.c: Likewise.
	* bfd/elf32-score.c: Likewise.
	* bfd/elf32-score7.c: Likewise.
	* bfd/elf32-sh-symbian.c: Likewise.
	* bfd/elf32-sh.c: Likewise.
	* bfd/elf32-sh64.c: Likewise.
	* bfd/elf32-spu.c: Likewise.
	* bfd/elf32-tic6x.c: Likewise.
	* bfd/elf32-tilepro.c: Likewise.
	* bfd/elf32-v850.c: Likewise.
	* bfd/elf32-vax.c: Likewise.
	* bfd/elf32-visium.c: Likewise.
	* bfd/elf32-xc16x.c: Likewise.
	* bfd/elf32-xstormy16.c: Likewise.
	* bfd/elf32-xtensa.c: Likewise.
	* bfd/elf64-alpha.c: Likewise.
	* bfd/elf64-hppa.c: Likewise.
	* bfd/elf64-ia64-vms.c: Likewise.
	* bfd/elf64-mmix.c: Likewise.
	* bfd/elf64-ppc.c: Likewise.
	* bfd/elf64-s390.c: Likewise.
	* bfd/elf64-sh64.c: Likewise.
	* bfd/elf64-x86-64.c: Likewise.
	* bfd/elflink.c: Likewise.
	* bfd/elfnn-aarch64.c: Likewise.
	* bfd/elfnn-ia64.c: Likewise.
	* bfd/elfxx-mips.c: Likewise.
	* bfd/elfxx-sparc.c: Likewise.
	* bfd/elfxx-tilegx.c: Likewise.
	* bfd/i386linux.c: Likewise.
	* bfd/linker.c: Likewise.
	* bfd/m68klinux.c: Likewise.
	* bfd/pdp11.c: Likewise.
	* bfd/pe-mips.c: Likewise.
	* bfd/peXXigen.c: Likewise.
	* bfd/reloc.c: Likewise.
	* bfd/reloc16.c: Likewise.
	* bfd/sparclinux.c: Likewise.
	* bfd/sunos.c: Likewise.
	* bfd/vms-alpha.c: Likewise.
	* bfd/xcofflink.c: Likewise.

include/

	* include/bfdlink.h (output_type): New enum.
	(bfd_link_executable): New macro.
	(bfd_link_dll): Likewise.
	(bfd_link_relocatable): Likewise.
	(bfd_link_pic): Likewise.
	(bfd_link_pie): Likewise.
	(bfd_link_info): Remove shared, executable, pie and relocatable.
	Add output_type and pic.

ld/

	* ld/ldctor.c: Replace shared, executable, relocatable and pie
	fields with bfd_link_executable, bfd_link_dll,
	bfd_link_relocatable, bfd_link_pic and bfd_link_pie.
	* ld/ldemul.c: Likewise.
	* ld/ldfile.c: Likewise.
	* ld/ldlang.c: Likewise.
	* ld/ldmain.c: Likewise.
	* ld/ldwrite.c: Likewise.
	* ld/lexsup.c: Likewise.
	* ld/pe-dll.c: Likewise.
	* ld/plugin.c: Likewise.
	* ld/emultempl/aarch64elf.em: Likewise.
	* ld/emultempl/aix.em: Likewise.
	* ld/emultempl/alphaelf.em: Likewise.
	* ld/emultempl/armcoff.em: Likewise.
	* ld/emultempl/armelf.em: Likewise.
	* ld/emultempl/avrelf.em: Likewise.
	* ld/emultempl/beos.em: Likewise.
	* ld/emultempl/cr16elf.em: Likewise.
	* ld/emultempl/elf-generic.em: Likewise.
	* ld/emultempl/elf32.em: Likewise.
	* ld/emultempl/genelf.em: Likewise.
	* ld/emultempl/generic.em: Likewise.
	* ld/emultempl/gld960.em: Likewise.
	* ld/emultempl/gld960c.em: Likewise.
	* ld/emultempl/hppaelf.em: Likewise.
	* ld/emultempl/irix.em: Likewise.
	* ld/emultempl/linux.em: Likewise.
	* ld/emultempl/lnk960.em: Likewise.
	* ld/emultempl/m68hc1xelf.em: Likewise.
	* ld/emultempl/m68kcoff.em: Likewise.
	* ld/emultempl/m68kelf.em: Likewise.
	* ld/emultempl/metagelf.em: Likewise.
	* ld/emultempl/mipself.em: Likewise.
	* ld/emultempl/mmo.em: Likewise.
	* ld/emultempl/msp430.em: Likewise.
	* ld/emultempl/nds32elf.em: Likewise.
	* ld/emultempl/needrelax.em: Likewise.
	* ld/emultempl/nios2elf.em: Likewise.
	* ld/emultempl/pe.em: Likewise.
	* ld/emultempl/pep.em: Likewise.
	* ld/emultempl/ppc32elf.em: Likewise.
	* ld/emultempl/ppc64elf.em: Likewise.
	* ld/emultempl/sh64elf.em: Likewise.
	* ld/emultempl/solaris2.em: Likewise.
	* ld/emultempl/spuelf.em: Likewise.
	* ld/emultempl/sunos.em: Likewise.
	* ld/emultempl/tic6xdsbt.em: Likewise.
	* ld/emultempl/ticoff.em: Likewise.
	* ld/emultempl/v850elf.em: Likewise.
	* ld/emultempl/vms.em: Likewise.
	* ld/emultempl/vxworks.em: Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] x86/Linux: disable all-stop on top of non-stop
@ 2015-08-18 10:19 sergiodj+buildbot
  2015-08-18 10:55 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-18 10:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b2a33439909493f5bf93ada871bd588f365d61f4 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: b2a33439909493f5bf93ada871bd588f365d61f4

x86/Linux: disable all-stop on top of non-stop

Markus reported that ASNS breaks target record-btrace.  In particular,
the gdb.btrace/multi-thread-step.exp test fails (both with BTS and PT
tracing) with a crash in py-inferior.c:

 Program received signal SIGSEGV, Segmentation fault.

 0x00000000006aa40d in add_thread_object (tp=0x27d32d0)

     at /users/mmetzger/team/gdb/git/gdb/python/py-inferior.c:337

 337       entry->next = inf_obj->threads;

My machine doesn't support BTS nor PT, so I missed this...

Disabling ASNS temporarily on x86 until this is addressed.

Tested on x86_64 Fedora 20.

gdb/ChangeLog:
2015-08-18  Pedro Alves  <palves@redhat.com>

	* linux-nat.c (linux_nat_always_non_stop_p): If the linux_ops
	target implements to_always_non_stop_p, call it.
	* x86-linux-nat.c (x86_linux_always_non_stop_p): New function.
	(x86_linux_create_target): Install it as to_always_non_stop_p
	method.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Use $SED in bfd Makefile
@ 2015-08-18  8:05 sergiodj+buildbot
  2015-08-18  9:33 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-18  8:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fe875424a05df7c4055cd9382ab76f65e952c4dd ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: fe875424a05df7c4055cd9382ab76f65e952c4dd

Use $SED in bfd Makefile

	PR 18667
	* Makefile.am: Use $(SED) in place of sed throughout.
	* Makefile.in: Regenerate.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] PPC64: Allow .TOC. in linker script to override backend calculated value
@ 2015-08-18  7:34 sergiodj+buildbot
  2015-08-18  8:21 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-18  7:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 43417696fe32416607940258ded622c121872515 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 43417696fe32416607940258ded622c121872515

PPC64: Allow .TOC. in linker script to override backend calculated value

bfd/
	* elf64-ppc.c (ppc64_elf_func_desc_adjust): Don't redefine .TOC.
	if already defined, and set linker_def.
	(ppc64_elf_set_toc): Use .TOC. value if defined other than by
	the backend.
ld/
	* ldexp.c (exp_fold_tree_1): Clear linker_def on symbol assignment.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] ui-out.c (default_ui_out_impl): Add comment.
@ 2015-08-17 20:18 sergiodj+buildbot
  2015-08-17 22:34 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-17 20:18 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 71b57e37fe94bbc17f57f8f9ca5e9c5400cedd6b ***

Author: Doug Evans <dje@google.com>
Branch: master
Commit: 71b57e37fe94bbc17f57f8f9ca5e9c5400cedd6b

ui-out.c (default_ui_out_impl): Add comment.

gdb/ChangeLog:

	* ui-out.c (default_ui_out_impl): Add comment.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [D] Implement looking up members of D enums.
@ 2015-08-17 20:03 sergiodj+buildbot
  2015-08-17 21:20 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-17 20:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7f3706ebfeb44e6b1f39f95fe44b7099a91c32c9 ***

Author: Iain Buclaw <ibuclaw@gdcproject.org>
Branch: master
Commit: 7f3706ebfeb44e6b1f39f95fe44b7099a91c32c9

[D] Implement looking up members of D enums.

In D, all named enums are explicitly scoped (the C++ equivalent of enum class)
so they should be handled as such in the language-specific symbol lookup
routines.  However so as to support D compilers that don't emit enums as
DW_AT_enum_class, need to make sure that appropriate checks for
TYPE_DECLARED_CLASS are done.

gdb/ChangeLog

	* d-exp.y (type_aggregate_p): New function.
	(PrimaryExpression : TypeExp '.' IdentifierExp): Use it.
	(classify_inner_name): Likewise.
	* d-namespace.c (d_lookup_nested_symbol): Handle TYPE_CODE_ENUM.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Move strace -m/explicit location test to strace.exp
@ 2015-08-17 19:21 sergiodj+buildbot
  2015-08-17 20:07 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-17 19:21 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ad89c2aa677c28c76ffd5a35e2b36eece4d82597 ***

Author: Keith Seitz <keiths@redhat.com>
Branch: master
Commit: ad89c2aa677c28c76ffd5a35e2b36eece4d82597

Move strace -m/explicit location test to strace.exp

One of the build slaves shows this error running explicit.exp:

(gdb) strace -m gdbfoobarbaz
Remote failure reply: E.In-process agent library not loaded in process.
Fast and static tracepoints unavailable.
(gdb) FAIL: gdb.linespec/explicit.exp: strace -m gdbfoobarbaz

There are two big problems with this test:
1) The expected output is actually not what the test is meant to test for.
2) This test should really only run where it is supported.

This is most easily fixed by moving the test to gdb.trace/strace.exp.

gdb/testsuite/ChangeLog

	* gdb.linespec/explicit.exp: Move strace test from here ...
	* gdb.trace/strace.exp: ... to here.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Trailing space in opcodes/ generated files
@ 2015-08-17  2:48 sergiodj+buildbot
  2015-08-17 11:50 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-17  2:48 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 919b75f7e28942fe320dc533759f88131f160bf3 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 919b75f7e28942fe320dc533759f88131f160bf3

Trailing space in opcodes/ generated files

HJ recently removed trailing space in binutils files, but unfortunately
they return when regenerating files in opcodes.  This fixes the regen
process.

	* cgen.sh: Trim trailing space from cgen output.
	* ia64-gen.c (print_dependency_table): Don't generate trailing space.
	(print_dis_table): Likewise.
	* opc2c.c (dump_lines): Likewise.
	(orig_filename): Warning fix.
	* ia64-asmtab.c: Regenerate.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] psymtab.c (add_psymbol_to_bcache): Remove "val" arg.
@ 2015-08-16 23:49 sergiodj+buildbot
  2015-08-17  9:55 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-16 23:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1762568fd6bd84f1b1a488375cf320a1efa06b22 ***

Author: Doug Evans <xdje42@gmail.com>
Branch: master
Commit: 1762568fd6bd84f1b1a488375cf320a1efa06b22

psymtab.c (add_psymbol_to_bcache): Remove "val" arg.

gdb/ChangeLog:

	* psymtab.c (add_psymbol_to_bcache): Remove "val" arg.  All callers
	updated.
	(add_psymbol_to_list): Ditto.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Add end_psymtab_common, have all debug info readers call it.
@ 2015-08-16  0:29 sergiodj+buildbot
  2015-08-17  8:43 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-16  0:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8763cedeec7f0a1daea41c2231bda165652e273b ***

Author: Doug Evans <xdje42@gmail.com>
Branch: master
Commit: 8763cedeec7f0a1daea41c2231bda165652e273b

Add end_psymtab_common, have all debug info readers call it.

gdb/ChangeLog:

	* dbxread.c (dbx_end_psymtab): Renamed from end_psymtab.  All callers
	updated.  Call end_psymtab_common.
	* dwarf2read.c (process_psymtab_comp_unit_reader): Call
	end_psymtab_common.
	(build_type_psymtabs_reader): Ditto.
	* psympriv.h (sort_pst_symbols): Delete.
	(end_psymtab_common): Declare.
	* psymtab.c (sort_pst_symbols): Make static.
	(end_psymtab_common): New function.
	* xcoffread.c (xcoff_end_psymtab): Call end_psymtab_common.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Use macros for some enum bit field sizes.
@ 2015-08-15 23:57 sergiodj+buildbot
  2015-08-17  5:09 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-15 23:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 51cdc99310171d6c53d2d00103a0ce34374d0b9b ***

Author: Doug Evans <xdje42@gmail.com>
Branch: master
Commit: 51cdc99310171d6c53d2d00103a0ce34374d0b9b

Use macros for some enum bit field sizes.

gdb/ChangeLog:

	* defs.h (LANGUAGE_BITS): Define.
	* psympriv.h (partial_symbol) <domain>: Use SYMBOL_DOMAIN_BITS.
	(partial_symbol) <aclass>: Use SYMBOL_ACLASS_BITS.
	* symtab.h (general_symbol_info> <language>: Usage LANGUAGE_BITS.
	(minimal_symbol_type): Add nr_minsym_types.
	(MINSYM_TYPE_BITS): Define.
	(minimal_symbol) <type>: Use MINSYM_TYPE_BITS.
	(domain_enum_tag): Add NR_DOMAINS.
	(SYMBOL_DOMAIN_BITS): Change from 4 to 3.
	(SYMBOL_ACLASS_BITS): Define from 6 to 5.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] objfiles.h,psympriv.h,psymtab.c: Whitespace.
@ 2015-08-15 23:05 sergiodj+buildbot
  2015-08-17  4:31 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-15 23:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 95cf586902b681310e63ee06d89ba2498d1d5dcf ***

Author: Doug Evans <xdje42@gmail.com>
Branch: master
Commit: 95cf586902b681310e63ee06d89ba2498d1d5dcf

objfiles.h,psympriv.h,psymtab.c: Whitespace.

gdb/ChangeLog:

	* objfiles.h: Whitespace cleanup.
	* psympriv.h: Whitespace cleanup.
	* psymtab.c: Whitespace/coding convention cleanup.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix invoking "[kill|detach] inferiors" on inferiors that are not running
@ 2015-08-15 18:05 sergiodj+buildbot
  2015-08-16 15:46 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-15 18:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e3ae3c4345fa14f2f3b0b2c5d4d23760af9f74f5 ***

Author: Patrick Palka <patrick@parcs.ath.cx>
Branch: master
Commit: e3ae3c4345fa14f2f3b0b2c5d4d23760af9f74f5

Fix invoking "[kill|detach] inferiors" on inferiors that are not running

Invoking either of the above commands on an inferior that's not running
triggers the following assert failure:

  .../binutils-gdb/gdb/thread.c:514: internal-error: any_thread_of_process: Assertion `pid != 0' failed.

The fix is straightforward.  This patch also adds a test to check the
basic functionality of these commands, along with testing this fix in
particular.  Tested on x86_64 Linux.

gdb/ChangeLog:

	* inferior.c (detach_inferior_command): Don't call
	any_thread_of_process when pid is 0.
	(kill_inferior_command): Likewise.

gdb/testsuite/ChangeLog:

	* gdb.base/kill-detach-inferiors-cmd.exp: New test file.
	* gdb.base/kill-detach-inferiors-cmd.c: New test file.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] perftest/utils.py (select_file): Kill any existing inferior before selecting a new file.
@ 2015-08-15  6:44 sergiodj+buildbot
  2015-08-16 13:12 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-15  6:44 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 604b263620af66e3bf881f146e329b4de06104a5 ***

Author: Doug Evans <xdje42@gmail.com>
Branch: master
Commit: 604b263620af66e3bf881f146e329b4de06104a5

perftest/utils.py (select_file): Kill any existing inferior before selecting a new file.

gdb/testsuite/ChangeLog:

	* gdb.perf/lib/perftest/utils.py (select_file): Kill any existing
	inferior before selecting a new file.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] New /s modifier for the disassemble command.
@ 2015-08-15  4:59 sergiodj+buildbot
  2015-08-15 23:12 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-15  4:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6ff0ba5f7b8a2b10642bbb233a32043595c55670 ***

Author: Doug Evans <xdje42@gmail.com>
Branch: master
Commit: 6ff0ba5f7b8a2b10642bbb233a32043595c55670

New /s modifier for the disassemble command.

The "source centric" /m option to the disassemble command is often
unhelpful, e.g., in the presence of optimized code.
This patch adds a /s modifier that is better.
For one, /m only prints instructions from the originating source file,
leaving out instructions from e.g., inlined functions from other files.

gdb/ChangeLog:

	PR gdb/11833
	* NEWS: Document new /s modifier for the disassemble command.
	* cli/cli-cmds.c (disassemble_command): Add support for /s.
	(_initialize_cli_cmds): Update online docs of disassemble command.
	* disasm.c: #include "source.h".
	(struct deprecated_dis_line_entry): Renamed from dis_line_entry.
	All uses updated.
	(dis_line_entry): New struct.
	(hash_dis_line_entry, eq_dis_line_entry): New functions.
	(allocate_dis_line_table): New functions.
	(maybe_add_dis_line_entry, line_has_code_p): New functions.
	(dump_insns): New arg end_pc.  All callers updated.
	(do_mixed_source_and_assembly_deprecated): Renamed from
	do_mixed_source_and_assembly.  All callers updated.
	(do_mixed_source_and_assembly): New function.
	(gdb_disassembly): Handle /s (DISASSEMBLY_SOURCE).
	* disasm.h (DISASSEMBLY_SOURCE_DEPRECATED): Renamed from
	DISASSEMBLY_SOURCE.  All uses updated.
	(DISASSEMBLY_SOURCE): New macro.
	* mi/mi-cmd-disas.c (mi_cmd_disassemble): New modes 4,5.

gdb/doc/ChangeLog:

	* gdb.texinfo (Machine Code): Update docs for mixed source/assembly
	disassembly.
	(GDB/MI Data Manipulation): Update docs for new disassembly modes.

gdb/testsuite/ChangeLog:

	* gdb.mi/mi-disassemble.exp: Update.
	* gdb.base/disasm-optim.S: New file.
	* gdb.base/disasm-optim.c: New file.
	* gdb.base/disasm-optim.h: New file.
	* gdb.base/disasm-optim.exp: New file.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Rename `typename' in d-exp.y to avoid C++ reserved word
@ 2015-08-15  0:47 sergiodj+buildbot
  2015-08-15 21:58 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-15  0:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b56ccc202ab674998baf52a710d736702734f9ab ***

Author: Keith Seitz <keiths@redhat.com>
Branch: master
Commit: b56ccc202ab674998baf52a710d736702734f9ab

Rename `typename' in d-exp.y to avoid C++ reserved word

A recent patch introduced a variable named `typename' into d-exp.y,
and one of the --enable-with-cxx build slaves consequently failed to compile
this.  This patch simply adds an underscore into the name to avoid the
reserved word.

gdb/ChangeLog

	* d-exp.y (PrimaryExpression : TypeExp '.' IdentifierExp): Rename
	`typename' to `type_name' to avoid C++ reserved word.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Rename location accessor macro parameters to silence ARI
@ 2015-08-14 22:33 sergiodj+buildbot
  2015-08-15 20:48 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-14 22:33 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ebdad8fc7fd12b52a2dd14cdca735728b2f7ebc7 ***

Author: Keith Seitz <keiths@redhat.com>
Branch: master
Commit: ebdad8fc7fd12b52a2dd14cdca735728b2f7ebc7

Rename location accessor macro parameters to silence ARI

The locations patch I recently committed contains macro definitions
such as:

This causes an ARI error to be emitted by the server ("Do not use PTR, ISO C
90 implies `void *'").  While this ARI error is bogus in this context,
it is just easiest to squash the error completely by renaming the macro
parameters.

gdb/ChangeLog

	* location.c (EL_TYPE, EL_LINESPEC, EL_PROBE, EL_ADDRESS)
	(EL_EXPLICIT, EL_STRING): Change macro parameter to "P" to
	silence ARI errors.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] mi_make_breakpoint: add "evaluated-by" option
@ 2015-08-14 21:57 sergiodj+buildbot
  2015-08-15 19:37 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-14 21:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6613eb10d10ee79ef09bf4dfe696586f479c8d02 ***

Author: Keith Seitz <keiths@redhat.com>
Branch: master
Commit: 6613eb10d10ee79ef09bf4dfe696586f479c8d02

mi_make_breakpoint: add "evaluated-by" option

For some time now, GDB has permitted target-side evaluation of
breakpoint conditions.  On targets that support this feature, GDB
may output an "evaluated-by" field into the breakpoint reply.

This patch adds handling for this option, and outputs a default
pattern to optionally recognize (and ignore) this pattern in the
reply.

gdb/testsuite/ChangeLog

	* lib/mi-support.exp (mi_make_breakpoint): Add option/handling for
	"evaluated-by".


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix ARI warnings in d-exp.y
@ 2015-08-14 20:00 sergiodj+buildbot
  2015-08-15 18:24 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-14 20:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c0fe2ae7064c4f927034aca87913bc28920721d9 ***

Author: Iain Buclaw <ibuclaw@gdcproject.org>
Branch: master
Commit: c0fe2ae7064c4f927034aca87913bc28920721d9

Fix ARI warnings in d-exp.y

This fixes four ARI warnings found in d-exp.y.

This is comprised of three uses of the && or || at the end of a line, and one
use of sprintf.

gdb/ChangeLog

	* d-exp.y (PrimaryExpression : TypeExp '.' IdentifierExp): Use
	xstrprintf instead of malloc and sprintf.
	(PrimaryExpression : IdentifierExp): Avoid operator at end of line.
	(lex_one_token): Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Add support for DT_MIPS_RLD_MAP_REL.
@ 2015-08-14 14:27 sergiodj+buildbot
  2015-08-15 17:07 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-14 14:27 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a738da3abe2bc02d70521086cf1d0e23565b8fbe ***

Author: Matthew Fortune <matthew.fortune@imgtec.com>
Branch: master
Commit: a738da3abe2bc02d70521086cf1d0e23565b8fbe

Add support for DT_MIPS_RLD_MAP_REL.

This tag allows debugging of MIPS position independent executables
and provides access to shared library information.

gdb/gdbserver/

	* linux-low.c (get_r_debug): Handle DT_MIPS_RLD_MAP_REL.

gdb/

	* solib-svr4.c (read_program_header): Add base_addr argument to
	report the runtime address of the segment.
	(find_program_interpreter): Update read_program_header call to pass
	a NULL pointer for the new argument.
	(scan_dyntag): Add ptr_addr argument to report the runtime address
	of the tag payload.
	(scan_dyntag_auxv): Likewise and use thew new base_addr argument of
	read_program_header to get the base address of the dynamic segment.
	(elf_locate_base): Update uses of scan_dyntag, scan_dyntag_auxv and
	read_program_header.
	(elf_locate_base): Scan for and handle DT_MIPS_RLD_MAP_REL.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Add myself to gdb MAINTAINERS
@ 2015-08-14 12:24 sergiodj+buildbot
  2015-08-15 12:10 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-14 12:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f8edc4ff051b4e29997681cb3bc9078d98f4d457 ***

Author: Matthew Fortune <matthew.fortune@imgtec.com>
Branch: master
Commit: f8edc4ff051b4e29997681cb3bc9078d98f4d457

Add myself to gdb MAINTAINERS

gdb/
	* MAINTAINERS (Write After Approval): Add Matthew Fortune.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Revert "Fix encoding or OpenRisk1000 PC relative relocations."
@ 2015-08-14  1:48 sergiodj+buildbot
  2015-08-15  1:29 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-14  1:48 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9b57267f4ffa4f8a168f89630a4b68fb51a419de ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 9b57267f4ffa4f8a168f89630a4b68fb51a419de

Revert "Fix encoding or OpenRisk1000 PC relative relocations."

This reverts commit dbac553d28887561e3f154654ec8e70195d89943.

	PR ld/18759
	* elf32-or1k.c: Revert 2015-08-11 change.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [D] Move classification of symbols from the grammar to the lexer.
@ 2015-08-13 21:02 sergiodj+buildbot
  2015-08-15  0:39 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-13 21:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 444c1ed8915961384af694249701fa7896e11da8 ***

Author: Iain Buclaw <ibuclaw@gdcproject.org>
Branch: master
Commit: 444c1ed8915961384af694249701fa7896e11da8

[D] Move classification of symbols from the grammar to the lexer.

This makes it so that alternating '.' and identifier tokens are resolved to
symbols as early as possible, which should all the addition of D properties -
such as EXP.sizeof and EXP.typeof - without the shift/reduce conflicts that
would occur in the current parsing strategy.

gdb/ChangeLog

	* d-exp.y (%union): Add voidval.
	(%token): Add UNKNOWN_NAME as a token to represent an unclassified
	name in the lexing stage.
	(PostfixExpression): Move symbol completion handling in grammar here
	from PrimaryExpression.
	(PrimaryExpression): Move routines to handle resolving identifier
	tokens in the grammar here from push_expression_name.
	(IdentifierExp): Remove the handling of alternating '.' and identifier
	tokens.
	(TypeExp): Allow TypeExp to be wrapped in parenthesis in the grammar.
	(BasicType): Remove C-style typename rules.
	(d_type_from_name, d_module_from_name, push_variable)
	(push_fieldnames, push_type_name, push_module_name)
	(push_expression_name): Remove.
	(lex_one_token): Rename from yylex.  Replace pstate with par_state.
	(token_and_value): New type.
	(token_fifo, popping, name_obstack): New globals.
	(classify_name): New function.
	(classify_inner_name): Likewise.
	(yylex): Likewise.
	(d_parse): Initialize token_fifo, popping and name_obstack.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [D] Support looking up symbols in the current and imported modules.
@ 2015-08-13 20:36 sergiodj+buildbot
  2015-08-14 23:07 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-13 20:36 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bc7c9fab612d4d33f7fe5d17eef4f5bd5cdc4144 ***

Author: Iain Buclaw <ibuclaw@gdcproject.org>
Branch: master
Commit: bc7c9fab612d4d33f7fe5d17eef4f5bd5cdc4144

[D] Support looking up symbols in the current and imported modules.

In D, there is the notion of modules, and importing from one to the other,
whether it is a basic, selective or renamed import declaration.

	module A;
	import X;
	void foo() {
	  import Y : bar;
	}

If the compiler emits DW_TAG_imported_declaration at the appropriate locations,
then we can make use of what gdb stores in using_direct when performing
nonlocal symbol lookups.

gdb/ChangeLog

	* Makefile.in (SFILES): Add d-namespace.c.
	(COMMON_OBS): Add d-namespace.o.
	* d-lang.c (d_language_defn): Use d_lookup_symbol_nonlocal as the
	la_lookup_symbol_nonlocal callback function pointer.
	* d-lang.h (d_lookup_symbol_nonlocal): New declaration.
	(d_lookup_nested_symbol): New declaration.
	* d-namespace.c: New file.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] gdb.base/dso2dso.exp: Improve testcase documentation.
@ 2015-08-13 18:46 sergiodj+buildbot
  2015-08-14 10:00 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-13 18:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 52bbc560524ec3691203eccd05207d13913a1e35 ***

Author: Joel Brobecker <brobecker@adacore.com>
Branch: master
Commit: 52bbc560524ec3691203eccd05207d13913a1e35

gdb.base/dso2dso.exp: Improve testcase documentation.

gdb/testsuite/ChangeLog:

        * gdb.base/dso2dso.exp: Improve the testcase's documentation.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix Python frame unwinder issue caught by Valgrind
@ 2015-08-13 18:17 sergiodj+buildbot
  2015-08-13 23:17 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-13 18:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3207396b9532f179bad24a9fb9a83253f3f5144d ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 3207396b9532f179bad24a9fb9a83253f3f5144d

Fix Python frame unwinder issue caught by Valgrind

Valgrind shows:

 ==17026== Invalid write of size 8
 ==17026==    at 0x54AA80: pending_frame_invalidate (py-unwind.c:477)
 ==17026==    by 0x5AB934: do_my_cleanups (cleanups.c:155)
 ==17026==    by 0x5AB9AF: do_cleanups (cleanups.c:177)
 ==17026==    by 0x54B009: pyuw_sniffer (py-unwind.c:606)
 ==17026==    by 0x755DAC: frame_unwind_try_unwinder (frame-unwind.c:105)
 ==17026==    by 0x755EEE: frame_unwind_find_by_frame (frame-unwind.c:160)
 ==17026==    by 0x750FFA: compute_frame_id (frame.c:454)
 ==17026==    by 0x753BD6: get_prev_frame_if_no_cycle (frame.c:1781)
 ==17026==    by 0x754292: get_prev_frame_always_1 (frame.c:1955)
 ==17026==    by 0x7542DA: get_prev_frame_always (frame.c:1971)
 ==17026==    by 0x7547BE: get_prev_frame (frame.c:2213)
 ==17026==    by 0x7532BD: unwind_to_current_frame (frame.c:1450)
 ==17026==  Address 0xd27b570 is 16 bytes inside a block of size 32 free'd
 ==17026==    at 0x4A07577: free (in /usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so)
 ==17026==    by 0x54B276: gdb_Py_DECREF (python-internal.h:185)
 ==17026==    by 0x54B298: py_decref (py-utils.c:34)
 ==17026==    by 0x5AB934: do_my_cleanups (cleanups.c:155)
 ==17026==    by 0x5AB9AF: do_cleanups (cleanups.c:177)
 ==17026==    by 0x54B009: pyuw_sniffer (py-unwind.c:606)
 ==17026==    by 0x755DAC: frame_unwind_try_unwinder (frame-unwind.c:105)
 ==17026==    by 0x755EEE: frame_unwind_find_by_frame (frame-unwind.c:160)
 ==17026==    by 0x750FFA: compute_frame_id (frame.c:454)
 ==17026==    by 0x753BD6: get_prev_frame_if_no_cycle (frame.c:1781)
 ==17026==    by 0x754292: get_prev_frame_always_1 (frame.c:1955)
 ==17026==    by 0x7542DA: get_prev_frame_always (frame.c:1971)
 ==17026==

Simply invalidate the object before releasing it.

gdb/ChangeLog:
2015-08-13  Pedro Alves  <palves@redhat.com>

	* python/py-unwind.c (pyuw_sniffer): Install the invalidate
	cleanup after the decref cleanup, not before.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Mass rename `explicit' -> `explicit_loc'.
@ 2015-08-13 17:22 sergiodj+buildbot
  2015-08-13 22:05 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-13 17:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 67994074671a31e3d2fb78f6036f38095211ac49 ***

Author: Keith Seitz <keiths@redhat.com>
Branch: master
Commit: 67994074671a31e3d2fb78f6036f38095211ac49

Mass rename `explicit' -> `explicit_loc'.

BuildBot reminded me that "explicit" is a reserved keyword in C++.
This patch simply renames all the (illegal) uses of "explicit". This should
fix the build errors with --enable-build-with-cxx bots.

gdb/ChangeLog

	* break-catch-throw.c (re_set_exception_catchpoint) Rename
	reserved C++ keyword "explicit" to "explicit_loc".
	* breakpoint.c (create_overlay_event_breakpoint)
	(create_longjmp_master_breakpoint)
	(create_std_terminate_master_breakpoint)
	(create_exception_master_breakpoint, update_static_tracepoint):
	Rename reserved C++ keyword "explicit" to "explicit_loc".
	* completer.c (collect_explicit_location_matches)
	(explicit_location_completer): Rename reserved C++ keyword
	"explicit" to "explicit_loc".
	* linespec.c (struct linespec) <explicit>: Rename to "explicit_loc".
	(canonicalize_linespec, create_sals_line_offset)
	(convert_linespec_to_sals, convert_explicit_location_to_sals)
	(event_location_to_sals, decode_objc): Rename reserved C++ keyword
	"explicit" to "explicit_loc".
	* location.c (struct event_location) <explicit>: Rename to
	"explicit_loc".
	(initialize_explicit_location, new_explicit_location)
	(explicit_location_to_string_internal, explicit_location_to_linespec):
	Rename reserved C++ keyword "explicit" to "explicit_loc".
	* location.h (explicit_location_to_string)
	(explicit_location_to_linespec, initialize_explicit_location)
	(new_explicit_location): Rename reserved C++ keyword "explicit"
	to "explicit_loc".
	* mi/mi-cmd-break.c (mi_cmd_break_insert_1): Rename reserved C++
	keyword "explicit" to "explicit_loc".


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Issue an error for read-only segment with dynamic IFUNC relocations
@ 2015-08-13 11:55 sergiodj+buildbot
  2015-08-13 20:53 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-13 11:55 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8efa2874ab298f3923f4127340da119435f87c39 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 8efa2874ab298f3923f4127340da119435f87c39

Issue an error for read-only segment with dynamic IFUNC relocations

To load an ELF binary with DT_TEXTREL tag, the dynamic linker calls
__mprotect on the read-only segment with PROT_READ|PROT_WRITE before
applying dynamic relocation.  It leads to segfault when performing
IFUNC relocations since the read-only segment has no execute permission.
This patch changes x86 linker to issue an error for read-only segment
with dynamic IFUNC relocations.  Other backends with IFUNC support
may need a similar change.

bfd/

	PR ld/18801
	* elf32-i386.c (elf_i386_size_dynamic_sections): Issue an error
	for read-only segment with dynamic IFUNC relocations.
	* elf64-x86-64.c (elf_x86_64_size_dynamic_sections): Likewise.

ld/testsuite/

	PR ld/18801
	* ld-i386/i386.exp: Run pr18801.
	* ld-x86-64/x86-64.exp: Likewise.
	* ld-i386/pr18801.d: New file.
	* ld-i386/pr18801.s: Likewise.
	* ld-x86-64/pr18801.d: Likewise.
	* ld-x86-64/pr18801.s: Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fixes for unpredictable nops and 26-bit versions of teq, tst, cmn, cmp.
@ 2015-08-13 10:53 sergiodj+buildbot
  2015-08-13 19:41 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-13 10:53 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4ab90a7a90ccf8a671f139c1c6387ba8028e6011 ***

Author: Andre Vieira <andre.simoesdiasvieira@arm.com>
Branch: master
Commit: 4ab90a7a90ccf8a671f139c1c6387ba8028e6011

Fixes for unpredictable nops and 26-bit versions of teq,tst,cmn,cmp.

opcodes * arm-dis.c (print_insn_arm): Disassembling for all targets V6
	and higher with ARM instruction set will now mark the 26-bit
	versions of teq,tst,cmn and cmp as UNPREDICTABLE.
	(arm_opcodes): Fix for unpredictable nop being recognized as a teq.

test    * gas/arm/nops.d: New.
	* gas/arm/nops.s: New.
	* gas/arm/inst.d: Changed expectation file for 26-bit  teq,
	tst, cmn and cmp.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [Ada] Add support for subprogram renamings
@ 2015-08-13  7:47 sergiodj+buildbot
  2015-08-13 18:17 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-13  7:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 22cee43f9af76fc4c10c3d4018a9ada6d7c5c1a5 ***

Author: Pierre-Marie de Rodat <derodat@adacore.com>
Branch: master
Commit: 22cee43f9af76fc4c10c3d4018a9ada6d7c5c1a5

[Ada] Add support for subprogram renamings

Consider the following declaration:

    function Foo (I : Integer) return Integer renames Pack.Bar;

As Foo is not materialized as a routine whose name is derived from Foo,
GDB currently cannot use it:

    (gdb) print foo(0)
    No definition of "foo" in current context.

However, compilers can emit DW_TAG_imported_declaration in order to
materialize the fact that Foo is actually another name for Pack.Bar.
This commit enhances the DWARF reader to record global renamings (it
used to put global ones in a static block) and enhances the Ada engine
to leverage this information during symbol lookup.

gdb/ChangeLog:

	* ada-lang.c: Include namespace.h
	(aux_add_nonlocal_symbols): Fix a function name in comment.
	(ada_add_block_renamings): New.
	(add_nonlocal_symbols): Add global renamings handling.
	(ada_lookup_symbol_list_worker): Move the symbol lookup part
	to...
	(ada_add_all_symbols): ... this new function.
	(ada_add_block_symbols): Try to match the input name against the
	"using directives list", perform a recursive symbol lookup on
	the matched declarations.
	* block.h (struct block): Move the_namespace to top-level as
	namespace_info. Remove the language_specific field.
	(BLOCK_NAMESPACE): Update access to the namespace_info field.
	* buildsym.h (using_directives): Rename into...
	(local_using_directives): ... this.
	(global_using_directives): New.
	(struct context_stack): Rename the using_directives field into
	local_using_directives.
	* buildsym.c (finish_block_internal): Deal with the proper
	using directives repository (local or global).
	(prepare_for_building): Reset local_using_directives. Assert
	that there is no pending global using directive.
	(reset_symtab_globals): Reset global_using_directives and
	local_using_directives.
	(end_symtab_get_static_block): Don't ignore symtabs that have
	only using directives.
	(push_context): Update references to local_using_directives.
	(buildsym_init): Do not reset using_directives.
	* cp-support.c: Include namespace.h.
	* cp-support.h (struct using_direct): Move to namespace.h.
	(cp_add_using_directives): Move to namespace.h.
	* cp-namespace.c: Include namespace.h
	(cp_add_using_directive): Move to namespace.c, rename it to
	add_using_directive, add a "using_directives" argument and use
	it as the pending using directives repository.  All callers
	updated.
	* dwarf2read.c (using_directives): New.
	(read_import_statement): Call using_directives.
	(read_func_scope): Update references to local_using_directives.
	(read_lexical_block_scope): Likewise.
	(read_namespace): Update the heading comment, call
	using_directives.
	* namespace.h: New file.
	* namespace.c: New file.
	* Makefile.in (SFILES): Add namespace.c.
	(COMMON_OBS): Add namespace.o

gdb/testsuite/ChangeLog:

	* gdb.ada/fun_renaming.exp: New testcase.
	* gdb.ada/fun_renaming/fun_renaming.adb: New file.
	* gdb.ada/fun_renaming/pack.adb: New file.
	* gdb.ada/fun_renaming/pack.ads: New file.

Tested on x86_64-linux.  Support for this in GCC is in the pipeline: see
<https://gcc.gnu.org/ml/gcc-patches/2015-07/msg02166.html>.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] gdb.base/dso2dso.exp sometimes broken
@ 2015-08-13  2:02 sergiodj+buildbot
  2015-08-13 16:57 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-13  2:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ea8812bceab054cab438bb51916f1d81118811b3 ***

Author: Keith Seitz <keiths@redhat.com>
Branch: master
Commit: ea8812bceab054cab438bb51916f1d81118811b3

gdb.base/dso2dso.exp sometimes broken

Keith reported that gdb.base/dso2dso.exp is broken, with the following
error:

| $ make check RUNTESTFLAGS=dso2dso.exp
| [snip]
| Running ../../../src/gdb/testsuite/gdb.base/dso2dso.exp ...
| ERROR: tcl error sourcing ../../../src/gdb/testsuite/gdb.base/dso2dso.exp.
| ERROR: couldn't open
| "../../../src/gdb/testsuite/gdb.base/../../../src/gdb/testsuite/gdb.base/dso2dso-dso1.c":
| no such file or directory
|     while executing
| "error "$message""
|     (procedure "gdb_get_line_number" line 14)
|     invoked from within
| "gdb_get_line_number "STOP HERE" $srcfile_libdso1"
|     (file "../../../src/gdb/testsuite/gdb.base/dso2dso.exp" line 60)
|     invoked from within
| "source ../../../src/gdb/testsuite/gdb.base/dso2dso.exp"
|     ("uplevel" body line 1)
|     invoked from within
| "uplevel #0 source ../../../src/gdb/testsuite/gdb.base/dso2dso.exp"
|     invoked from within
| "catch "uplevel #0 source $test_file_name""

This happens because gdb_get_line_number will prepend $srcdir/$subdir
if the given filename does not start with "/", and this happens when
GDB was configured using a relative path to the configure script.
When using an absolute path like I do, we avoid the pre-pending that
Keith is seeing.

gdb/testsuite/ChangeLog:

        Keith Seitz  <keiths@redhat.com>:
        * gdb.base/dso2dso.exp: Pass basename of source file in call
        to gdb_get_line_number.

Tested on x86_64-linux with both scenarios.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Set EI_OSABI to ELFOSABI_GNU for local IFUNC symbols
@ 2015-08-12 21:03 sergiodj+buildbot
  2015-08-13 15:31 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-12 21:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 13a2df29c930eda49837741902b67021ab004990 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 13a2df29c930eda49837741902b67021ab004990

Set EI_OSABI to ELFOSABI_GNU for local IFUNC symbols

Since the backend elf_add_symbol_hook isn't called on local symbols,
the EI_OSABI field isn't to ELFOSABI_GNU where are local IFUNC symbols.
This patch changes the x86 backends to set has_gnu_symbols if there are
relocations against IFUNC symbols.  Other backends with IFUNC support
may need a similar change.

This patch also changes the type of has_gnu_symbols from bfd_boolean to
enum elf_gnu_symbols.

bfd/

	PR ld/18815
	* elf-bfd.h (elf_gnu_symbols): New enum.
	(elf_obj_tdata): Use elf_gnu_symbols on has_gnu_symbols.
	* elf-s390-common.c (elf_s390_add_symbol_hook): Set
	has_gnu_symbols to elf_gnu_symbol_any.
	* elf32-arm.c (elf32_arm_add_symbol_hook): Likewise.
	* elf32-m68k.c (elf_m68k_add_symbol_hook): Likewise.
	* elf32-ppc.c (ppc_elf_add_symbol_hook): Likewise.
	* elf32-sparc.c (elf32_sparc_add_symbol_hook): Likewise.
	* elf64-ppc.c (ppc64_elf_add_symbol_hook): Likewise.
	* elf64-sparc.c (elf64_sparc_add_symbol_hook): Likewise.
	* lfxx-aarch64.c (_bfd_aarch64_elf_add_symbol_hook): Likewise.
	* elf32-i386.c (elf_i386_check_relocs): Update has_gnu_symbols
	if there are relocations against IFUNC symbols.
	(elf_i386_add_symbol_hook): Don't check STT_GNU_IFUNC here.
	* elf64-x86-64. (elf_x86_64_check_relocs): Update has_gnu_symbols
	if there are relocations against IFUNC symbols.
	(elf_x86_64_add_symbol_hook): Don't check STT_GNU_IFUNC here.

ld/testsuite/

	PR ld/18815
	* ld-i386/i386.exp: Run pr18815.
	* ld-x86-64/x86-64.exp: Likewise.
	* ld-i386/pr18815.d: New file.
	* ld-i386/pr18815.s: Likewise.
	* ld-x86-64/pr18815.d: Likewise.
	* ld-x86-64/pr18815.s: Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [amd64] Invalid return address after displaced stepping
@ 2015-08-12 20:32 sergiodj+buildbot
  2015-08-13 14:19 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-12 20:32 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4dafcdeb1341c4dd1a4641373bc17aab3ef2e788 ***

Author: Joel Brobecker <brobecker@adacore.com>
Branch: master
Commit: 4dafcdeb1341c4dd1a4641373bc17aab3ef2e788

[amd64] Invalid return address after displaced stepping

Making all-stop run on top of non-stop caused a small regression
in behavior. This was observed on x86_64-linux. The attached testcase
is in C whereas the investigation was done with an Ada program,
but it's the same scenario, and using a C testcase allows wider testing.
Basically: I am debugging a single-threaded program, and currently
stopped inside a function provided by a shared-library, at a line
calling a subprogram provided by a second shared library, and trying
to "next" over that function call.

Before we changed the default all-stop behavior, we had:

    7             Impl_Initialize;  -- Stop here and try "next" over this line
    (gdb) n
    8             return 5;  <<-- OK

But now, "next" just stops much earlier:

    (gdb) n
    0x00007ffff7bd8560 in impl.initialize@plt () from /[...]/lib/libpck.so

What happens is that next stops at a call instruction, which calls
the function's PLT, and GDB fails to notice that the inferior stepped
into a subroutine, and so decides that we're done. We can see another
symptom of the same issue by looking at the backtrace at the point
GDB stopped:

    (gdb) bt
    #0  0x00007ffff7bd8560 in impl.initialize@plt ()
       from /[...]/lib/libpck.so
    #1  0x00000000f7bd86f9 in ?? ()
    #2  0x00007fffffffdf50 in ?? ()
    #3  0x0000000000401893 in a () at /[...]/a.adb:7
    Backtrace stopped: frame did not save the PC

With a functioning GDB, the backtrace looks like the following instead:

    #0  0x00007ffff7bd8560 in impl.initialize@plt ()
       from /[...]/lib/libpck.so
    #1  0x00007ffff7bd86f9 in sub () at /[...]/pck.adb:7
    #2  0x0000000000401893 in a () at /[...]/a.adb:7

Note how, for frame #1, the address looks quite similar, except
for the high-order bits not being set:

    #1  0x00007ffff7bd86f9 in sub () at /[...]/pck.adb:7   <<<--  OK
    #1  0x00000000f7bd86f9 in ?? ()                        <<<--  WRONG
              ^^^^
              ||||
              Wrong

Investigating this further led me to displaced stepping.
As we are "next"-ing from a location where a breakpoint is inserted,
we need to step out of it, and since we're on non-stop mode, we need
to do it using displaced stepping. And looking at
amd64-tdep.c:amd64_displaced_step_fixup, I found the code that handles
the return address:

    regcache_cooked_read_unsigned (regs, AMD64_RSP_REGNUM, &rsp);
    retaddr = read_memory_unsigned_integer (rsp, retaddr_len, byte_order);
    retaddr = (retaddr - insn_offset) & 0xffffffffUL;

The mask used to compute retaddr looks wrong to me, keeping only
4 bytes instead of 8, and explains why the high order bits of
the backtrace are unset. What happens is that, after the displaced
stepping has completed, GDB restores that return address at the location
where the program expects it.  But because the top half bits of
the address have been masked out, the return address is now invalid.
The incorrect behavior of the "next" command and the backtrace at
that location are the first symptoms of that.  Another symptom is
that this actually alters the behavior of the program, where a "cont"
from there soon leads to a SEGV when the inferior tries to jump back
to that incorrect return address:

    (gdb) c
    Continuing.

    Program received signal SIGSEGV, Segmentation fault.
    0x00000000f7bd86f9 in ?? ()
    ^^^^^^^^^^^^^^^^^^

This patch fixes the issue by using a mask that seems more appropriate
for this architecture.

gdb/ChangeLog:

        * amd64-tdep.c (amd64_displaced_step_fixup): Fix the mask used to
        compute RETADDR.

gdb/testsuite/ChangeLog:

        * gdb.base/dso2dso-dso2.c, gdb.base/dso2dso-dso2.h,
        gdb.base/dso2dso-dso1.c, gdb.base/dso2dso-dso1.h, gdb.base/dso2dso.c,
        gdb.base/dso2dso.exp: New files.

Tested on x86_64-linux, no regression.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Initialize `location' in gdbpy_decode_line
@ 2015-08-12 18:48 sergiodj+buildbot
  2015-08-13 13:07 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-12 18:48 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 59ecaff36145add82c315ba7a008c4a5db4a6f51 ***

Author: Keith Seitz <keiths@redhat.com>
Branch: master
Commit: 59ecaff36145add82c315ba7a008c4a5db4a6f51

Initialize `location' in gdbpy_decode_line

BuildBot flagged an uninitialized variable coming from one of the patches
in my recently committed locations/explicit patchset.

The following patch fixes this.

gdb/ChangeLog

	* python/python.c (gdbpy_decode_line): Initialize `location' to NULL
	and only call decode_line_1 when it is non-NULL.

diff --git a/gdb/python/python.c b/gdb/python/python.c
index c28f98b..14da62c 100644
--- a/gdb/python/python.c
+++ b/gdb/python/python.c
@@ -730,7 +730,7 @@ gdbpy_decode_line (PyObject *self, PyObject *args)
   PyObject *result = NULL;
   PyObject *return_result = NULL;
   PyObject *unparsed = NULL;
-  struct event_location *location;
+  struct event_location *location = NULL;

   if (! PyArg_ParseTuple (args, "|s", &arg))
     return NULL;
@@ -747,7 +747,7 @@ gdbpy_decode_line (PyObject *self, PyObject *args)

   TRY
     {
-      if (arg)
+      if (location != NULL)
 	sals = decode_line_1 (location, 0, 0, 0);
       else
 	{


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Guarantee save-and-restore of GDBFLAGS on gdb.base/checkpoint-ns.exp
@ 2015-08-12 16:46 sergiodj+buildbot
  2015-08-13 12:08 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-12 16:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5ba325978c354b9f0e238864e3afb4f9b528c04e ***

Author: Sergio Durigan Junior <sergiodj@redhat.com>
Branch: master
Commit: 5ba325978c354b9f0e238864e3afb4f9b528c04e

Guarantee save-and-restore of GDBFLAGS on gdb.base/checkpoint-ns.exp

Keith found out that several tests were failing when testing the
native-gdbserver board on Fedora (x86_64).  Strangely, these failures
had not been reported by our BuildBot.  Later, he found that the reason
for this was because the failures only happened when running the
testsuite without FORCE_PARALLEL (i.e., on serial mode; maybe it would
be worth having a builder testing things on serial...).  Then, he
decided to start bisecting the changes to see which one introduced the
failure (it was not trivial to know this only by looking at gdb.log).

After a lot of time, he found that Pedro's commit
e1316e60d4d1fe406efc6e7536b2bdb43733e9d2 was the culprit.  There was
nothing wrong in the code, but the new gdb.base/checkpoint-ns.exp
testcase did something that left the GDBFLAGS variable in an
inconsistent state.  This test works by modifying this variable to set
non-stop on, sourcing gdb.base/checkpoint.exp (which does the hard
work), and then restoring the old value on GDBFLAGS.  However, this was
not working because gdb.base/checkpoint.exp bails out if it is being
tested on gdbserver, and when it calls "continue" the control goes back
to the function calling the tests, and not to
gdb.base/checkpoint-ns.exp.

The fix is simple: just wrap the "source" call, and make
gdb.base/checkpoint-ns.exp aware of the "continue"/"return" calls made
by gdb.base/checkpoint.exp.

gdb/testsuite/ChangeLog:
2015-08-12  Sergio Durigan Junior  <sergiodj@redhat.com>
	    Pedro Alves  <palves@redhat.com>
	    Keith Seitz  <keiths@redhat.com>

	* gdb.base/checkpoint-ns.exp: Use save_vars to save and restore
	GDBFLAGS.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [MIPS] Map 'move' to 'or'.
@ 2015-08-12 16:23 sergiodj+buildbot
  2015-08-13 11:28 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-12 16:23 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 40fc1451c63d21a1448bb21e39a7b70ecb959213 ***

Author: Simon Dardis <simon.dardis@imgtec.com>
Branch: master
Commit: 40fc1451c63d21a1448bb21e39a7b70ecb959213

[MIPS] Map 'move' to 'or'.

The MIPS assembly idiom 'move' now maps to the 'or' machine instruction. This
change affects microMIPS, MIPS32, MIPS64.

2015-08-12  Simon Dardis  <simon.dardis@imgtec.com>

opcodes/

	* micromips-opc.c (micromips_opcodes): Re-order table so that move
	based on 'or' is first.
	* mips-opc.c (mips_builtin_opcodes): Ditto.

bfd/

	* elfxx-mips.c (STUB_MOVE): Change to use 'or' only.
	(mips_o32_exec_plt0_entry, mips_n32_exec_plt0_entry,
	mips_n64_exec_plt0_entry, micromips_insn32_o32_exec_plt0_entry):
	Update to use 'or' instead of 'addu/daddu'.
	(_bfd_mips_elf_finish_dynamic_symbol): Update usage of STUB_MOVE.
	(move_insns_32): Reorder table.

gas/

	* config/tc-mips.c (move_register): Change to use 'or' only.
	(s_cpload, s_cpsetup, s_cprestore, s_cpreturn): Update to
	use or for move.

gas/testsuite/

	* gas/mips/elf-rel23.d: Update test.
	* gas/mips/elf-rel23.d: Ditto.
	* gas/mips/elf-rel23a.d: Ditto.
	* gas/mips/elf-rel23b.d: Ditto.
	* gas/mips/elf_e_flags1.d: Ditto.
	* gas/mips/elf_e_flags2.d: Ditto.
	* gas/mips/elf_e_flags3.d: Ditto.
	* gas/mips/elf_e_flags4.d: Ditto.
	* gas/mips/loc-swap-dis.d: Ditto.
	* gas/mips/micromips-insn32.d: Ditto.
	* gas/mips/micromips-noinsn32.d: Ditto.
	* gas/mips/micromips-trap.d: Ditto.
	* gas/mips/micromips.d: Ditto.
	* gas/mips/mips-abi32-pic.d: Ditto.
	* gas/mips/mips-abi32.d: Ditto.
	* gas/mips/mips-gp32-fp32-pic.d: Ditto.
	* gas/mips/mips-gp32-fp32.d: Ditto.
	* gas/mips/mips-gp32-fp64-pic.d: Ditto.
	* gas/mips/mips-gp32-fp64.d: Ditto.
	* gas/mips/mips-gp64-fp32-pic.d: Ditto.
	* gas/mips/mips-gp64-fp32.d: Ditto.
	* gas/mips/mips-gp64-fp64-pic.d: Ditto.
	* gas/mips/mips-gp64-fp64.d: Ditto.
	* gas/mips/mipsr6@loc-swap-dis.d: Ditto.
	* gas/mips/tls-o32.d: Ditto.
	* gas/mips/uld2-eb.d: Ditto.
	* gas/mips/uld2-el.d: Ditto.
	* gas/mips/ulw2-eb-ilocks.d: Ditto.
	* gas/mips/ulw2-eb.d: Ditto.
	* gas/mips/ulw2-el-ilocks.d: Ditto.
	* gas/mips/ulw2-el.d: Ditto.
	* gas/mips/move.d: New test.
	* gas/mips/move.s: Ditto.
	* gas/mips/micromips32-move.d: Ditto.
	* gas/mips/micromips32-move.s: Ditto.
	* gas/mips/mips.exp: Run the new tests.

gold/

	* mips.cc (plt0_entry_o32, plt0_entry_n32, plt0_entry_n64,
	lazy_stub_normal_1, lazy_stub_normal_1_n64,
	lazy_stub_normal_2, lazy_stub_normal_2_n64, lazy_stub_big,
	lazy_stub_big_n64, lazy_stub_micromips32_normal_1_n64,
	lazy_stub_micromips32_normal_2_n64, lazy_stub_micromips32_big,
	lazy_stub_micromips32_big_n64): Update to use 'or' for move instead
	of 'addu/daddu'.

ld/testsuite/

	* ld-mips-elf/compressed-plt-1-n32-mips16.od: Update test.
	* ld-mips-elf/compressed-plt-1-n32-umips.od: Ditto.
	* ld-mips-elf/compressed-plt-1-o32-mips16-got.od: Ditto.
	* ld-mips-elf/compressed-plt-1-o32-mips16-only.od: Ditto.
	* ld-mips-elf/compressed-plt-1-o32-mips16-word.od: Ditto.
	* ld-mips-elf/compressed-plt-1-o32-mips16.od: Ditto.
	* ld-mips-elf/compressed-plt-1-o32-se.od: Ditto.
	* ld-mips-elf/compressed-plt-1-o32-umips-got.od: Ditto.
	* ld-mips-elf/compressed-plt-1-o32-umips-word.od: Ditto.
	* ld-mips-elf/compressed-plt-1-o32-umips.od: Ditto.
	* ld-mips-elf/jalx-2.dd: Ditto.
	* ld-mips-elf/mips16-pic-3.dd: Ditto.
	* ld-mips-elf/pic-and-nonpic-3a.dd: Ditto.
	* ld-mips-elf/pic-and-nonpic-3b.dd: Ditto.
	* ld-mips-elf/pic-and-nonpic-5b.dd: Ditto.
	* ld-mips-elf/pic-and-nonpic-6-n32.dd: Ditto.
	* ld-mips-elf/pic-and-nonpic-6-o32.dd: Ditto.
	* ld-mips-elf/stub-dynsym-1-10000.d: Ditto.
	* ld-mips-elf/stub-dynsym-1-2fe80.d: Ditto.
	* ld-mips-elf/stub-dynsym-1-7fff.d: Ditto.
	* ld-mips-elf/stub-dynsym-1-8000.d: Ditto.
	* ld-mips-elf/stub-dynsym-1-fff0.d: Ditto.
	* ld-mips-elf/tlsbin-o32.d: Ditto.
	* ld-mips-elf/tlsdyn-o32-1.d: Ditto.
	* ld-mips-elf/tlsdyn-o32-2.d: Ditto.
	* ld-mips-elf/tlsdyn-o32-3.d: Ditto.
	* ld-mips-elf/tlsdyn-o32.d: Ditto.
	* ld-mips-elf/tlslib-o32.d: Ditto.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Use save_vars to replace existing manipulation of globals in tests
@ 2015-08-12 15:57 sergiodj+buildbot
  2015-08-13 10:48 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-12 15:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b6dafabfb18e3ab207a1818ebe68e30337b5515d ***

Author: Patrick Palka <patrick@parcs.ath.cx>
Branch: master
Commit: b6dafabfb18e3ab207a1818ebe68e30337b5515d

Use save_vars to replace existing manipulation of globals in tests

gdb/testsuite/ChangeLog:

	* gdb.base/gdbhistsize-history.exp
	(test_histsize_history_setting): Use save_vars.
	* gdb.base/gdbinit-history.exp (test_gdbinit_history_setting):
	Use save_vars.
	(test_no_truncation_of_unlimited_history_file): Use save_vars.
	* gdb.base/readline.exp: Use save_vars.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Introduce save_vars, a testsuite proc for safely manipulating globals
@ 2015-08-12 13:24 sergiodj+buildbot
  2015-08-13 10:04 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-12 13:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT abe8e6075bac6596f9105bbc9607038543ac849e ***

Author: Patrick Palka <patrick@parcs.ath.cx>
Branch: master
Commit: abe8e6075bac6596f9105bbc9607038543ac849e

Introduce save_vars, a testsuite proc for safely manipulating globals

gdb/testsuite/ChangeLog:

	* lib/gdb.exp (save_vars): New proc.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Sync ansidecl.h with GCC
@ 2015-08-12 12:58 sergiodj+buildbot
  2015-08-13  9:20 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-12 12:58 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT dd419f3aac048176e4e760dc8f29d3429c4f07ce ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: dd419f3aac048176e4e760dc8f29d3429c4f07ce

Sync ansidecl.h with GCC

	Sync with GCC
	2015-08-11  Trevor Saunders  <tbsaunde+gcc@tbsaunde.org>

	* ansidecl.h (GCC_FINAL): New macro.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Remove trailing spaces in opcodes
@ 2015-08-12 12:26 sergiodj+buildbot
  2015-08-13  8:10 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-12 12:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 43e65147c07b1400ae0dbb6694882eceb2363713 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 43e65147c07b1400ae0dbb6694882eceb2363713

Remove trailing spaces in opcodes


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Remove trailing spaces in bfd
@ 2015-08-12 11:58 sergiodj+buildbot
  2015-08-13  7:27 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-12 11:58 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1b7868733d45220e63b72a1814f30e090f761821 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 1b7868733d45220e63b72a1814f30e090f761821

Remove trailing spaces in bfd


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [regression] Do not read from catchpoint/watchpoint locations' addresses when checking for a permanent breakpoint
@ 2015-08-12  8:50 sergiodj+buildbot
  2015-08-12 22:53 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-12  8:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 244558af868d5427903c35c5105bf5499639f81f ***

Author: Luis Machado <lgustavo@codesourcery.com>
Branch: master
Commit: 244558af868d5427903c35c5105bf5499639f81f

[regression] Do not read from catchpoint/watchpoint locations' addresses when checking for a permanent breakpoint

While running bare-metal tests with GDB i noticed some failures in
gdb.base/break.exp, related to the use of the catch commands.

It turns out GDB tries to access memory address 0x0 whenever one tries
to insert a catchpoint, which should obviously not happen.

This was introduced with the changes for permanent breakpoints. In special,
bp_loc_is_permanent tries to check if there is a breakpoint inserted at
the same address as the current breakpoint's location's address. In the
case of catchpoints, this is 0x0.

(top-gdb) catch fork
Sending packet: $m0,1#fa...Packet received: E01
Catchpoint 4 (fork)

(top-gdb) catch vfork
Sending packet: $m0,1#fa...Packet received: E01
Catchpoint 5 (vfork)

It is not obvious to detect because this fails silently for Linux. For our
bare-metal testing, though, this fails with a clear error message from the
target about not being able to read such address.

The attached patch addresses this by bailing out of bp_loc_is_permanent (...)
if the location address is not meaningful. I also took the opportunity to
update the comment for breakpoint_address_is_meaningful, which mentioned
breakpoint addresses as opposed to their locations' addresses.

gdb/ChangeLog:

2015-08-11  Luis Machado  <lgustavo@codesourcery.com>

	* breakpoint.c (bp_loc_is_permanent): Return 0 when breakpoint
	location address is not meaningful.
	(breakpoint_address_is_meaningful): Update comment.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Properly skip IFUNC relocations in debug sections
@ 2015-08-12  5:48 sergiodj+buildbot
  2015-08-12 22:08 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-12  5:48 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0eace2105dc6c005fdc908414ad564d318b71540 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 0eace2105dc6c005fdc908414ad564d318b71540

Properly skip IFUNC relocations in debug sections

Use "continue" instead of "break" to skip IFUNC relocations in debug
sections.

	* elf32-i386.c (elf_i386_relocate_section): Properly skip IFUNC
	relocations in debug sections.
	* elf64-x86-64.c (elf_x86_64_relocate_section): Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Explicit locations: documentation updates
@ 2015-08-12  5:23 sergiodj+buildbot
  2015-08-12 21:24 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-12  5:23 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 629500fae69737a6230a564e8fef1f42c3ef1116 ***

Author: Keith Seitz <keiths@redhat.com>
Branch: master
Commit: 629500fae69737a6230a564e8fef1f42c3ef1116

Explicit locations: documentation updates

This patch adds documentation for explicit locations to both the
User Manual and gdb's online help system.

gdb/ChangeLog:

	* NEWS: Mention explicit locations.
	* breakpoint.c [LOCATION_HELP_STRING]: New macro.
	[BREAK_ARGS_HELP]: Use LOCATION_HELP_STRING.
	(_initialize_breakpoint): Update documentation for
	"clear", "break", "trace", "strace", "ftrace", and "dprintf".

gdb/doc/ChangeLog:

	* gdb.texinfo (Thread-Specific Breakpoints, Printing Source Lines):
	Use "location(s)"instead of "linespec(s)".
	(Specifying a Location): Rewrite.
	Add subsections describing linespec, address, and explicit locations.
	Add node/menu for each subsection.
	(Source and Machine Code, C Preprocessor Macros)
	(Create and Delete Trace points)
	(Extensions for Ada Tasks): Use "location(s)" instead of "linespec(s)".
	(Continuing at a Different Address): Remove "linespec" examples.
	Add reference to "Specify a Location"
	(The -break-insert Command): Rewrite.  Add anchor.
	Add reference to appropriate manual section discussing locations.
	(The -dprintf-insert Command): Refer to -break-insert for
	specification of 'location'.

gdb/testsuite/ChangeLog:

	* gdb.base/help.exp: Update help_breakpoint_text.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Explicit locations: MI support for explicit locations
@ 2015-08-12  4:59 sergiodj+buildbot
  2015-08-12 20:41 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-12  4:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT eb8c4e2e66329dc7bf2024d55991efe8587075c0 ***

Author: Keith Seitz <keiths@redhat.com>
Branch: master
Commit: eb8c4e2e66329dc7bf2024d55991efe8587075c0

Explicit locations: MI support for explicit locations

This patch adds support for explicit locations to MI's -break-insert
command. The new options, documented in the User Manual, are
--source, --line, --function, and --label.

gdb/ChangeLog:

	* mi/mi-cmd-break.c (mi_cmd_break_insert_1): Add support for
	explicit locations, options "--source", "--function",
	"--label", and "--line".

gdb/testsuite/ChangeLog:

	* gdb.mi/mi-break.exp (test_explicit_breakpoints): New proc.
	(at toplevel): Call test_explicit_breakpoints.
	* gdb.mi/mi-dprintf.exp: Add tests for explicit dprintf
	breakpoints.
	* lib/mi-support.exp (mi_make_breakpoint): Add support for
	breakpoint conditions, "-cond".


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Explicit locations: add UI features for CLI
@ 2015-08-12  4:30 sergiodj+buildbot
  2015-08-12 20:01 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-12  4:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 87f0e7204722a986f79f245eee716f0870832d47 ***

Author: Keith Seitz <keiths@redhat.com>
Branch: master
Commit: 87f0e7204722a986f79f245eee716f0870832d47

Explicit locations: add UI features for CLI

This patch exposes explicit locations to the CLI user.  This enables
users to "explicitly" specify attributes of the breakpoint location
to avoid any ambiguity that might otherwise exist with linespecs.

The general syntax of explicit locations is:
-source SOURCE_FILENAME -line {+-}LINE -function FUNCTION_NAME
-label LABEL_NAME

Option names may be abbreviated, e.g., "-s SOURCE_FILENAME -li 3" and users
may use the completer with either options or values.

gdb/ChangeLog:

	* completer.c: Include location.h.
	(enum match_type): New enum.
	(location_completer): Rename to ...
	(linespec_completer): ... this.
	(collect_explicit_location_matches, backup_text_ptr)
	(explicit_location_completer): New functions.
	(location_completer): "New" function; handle linespec
	and explicit location completions.
	(complete_line_internal): Remove all location completer-specific
	handling.
	* linespec.c (linespec_lexer_lex_keyword, is_ada_operator)
	(find_toplevel_char): Export.
	(linespec_parse_line_offset): Export.
	Issue error if STRING is not numerical.
	(gdb_get_linespec_parser_quote_characters): New function.
	* linespec.h (linespec_parse_line_offset): Declare.
	(get_gdb_linespec_parser_quote_characters): Declare.
	(is_ada_operator): Declare.
	(find_toplevel_char): Declare.
	(linespec_lexer_lex_keyword): Declare.
	* location.c (explicit_to_event_location): New function.
	(explicit_location_lex_one): New function.
	(string_to_explicit_location): New function.
	(string_to_event_location): Handle explicit locations.
	* location.h (explicit_to_event_location): Declare.
	(string_to_explicit_location): Declare.

gdb/testsuite/ChangeLog:

	* gdb.linespec/3explicit.c: New file.
	* gdb.linespec/cpexplicit.cc: New file.
	* gdb.linespec/cpexplicit.exp: New file.
	* gdb.linespec/explicit.c: New file.
	* gdb.linespec/explicit.exp: New file.
	* gdb.linespec/explicit2.c: New file.
	* gdb.linespec/ls-errs.exp: Add explicit location tests.
	* lib/gdb.exp (capture_command_output): Regexp-escape `command'
	before using in the matching pattern.
	Clarify that `prefix' is a regular expression.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Explicit locations: introduce explicit locations
@ 2015-08-12  4:04 sergiodj+buildbot
  2015-08-12 19:19 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-12  4:04 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 00e52e5376c7ec604a739e6242e6be36221162d7 ***

Author: Keith Seitz <keiths@redhat.com>
Branch: master
Commit: 00e52e5376c7ec604a739e6242e6be36221162d7

Explicit locations: introduce explicit locations

This patch add support for explicit locations and switches many linespec
locations to this new location type.  This patch also converts all
linespec locations entered by the user to an explicit representation
internally (thus bypassing the linespec parser when resetting the
breakpoint).

This patch does not introduce any user-visible changes.


gdb/ChangeLog:

	* break-catch-throw.c (re_set_exception_catchpoint): Convert
	linespec into explicit location.
	* breakpoint.c (create_overlay_breakpoint)
	(create_longjmp_master_breakpoint)
	(create_std_terminate_master_breakpoint)
	(create_exception_master_breakpoint): Convert linespec into explicit
	location.
	(update_static_tracepoint): Convert linespec into explicit location.
	* linespec.c (enum offset_relative_sign, struct line_offset): Move
	location.h.
	(struct linespec) <expression, expr_pc, source_filename>
	<function_name, label_name, line_offset>: Replace with ...
	<explicit>: ... this.
	<is_linespec>: New member.
	(PARSER_EXPLICIT): New accessor macro.
	(undefined_label_error): New function.
	(source_file_not_found_error): New function.
	(linespec_parse_basic): The parser result is now an explicit location.
	Use PARSER_EXPLICIT to access it.
	Use undefined_label_error.
	(canonicalize_linespec): Convert canonical linespec into explicit
	location.
	Move string representation of location to explicit_location_to_linespec
	and use it and explicit_location_to_string to save string
	representations of the canonical location.
	(create_sals_line_offset, convert_linespec_to_sals): `ls' contains an
	explicit location.  Update all references.
	(convert_explicit_location_to_sals): New function.
	(parse_linespec): Use PARSER_EXPLICIT to access the parser
	result's explicit location.
	(linespec_state_constructor): Initialize is_linespec.
	Use PARSER_EXPLICIT.
	(linespec_parser_delete): Use PARSER_EXPLICIT to access the parser's
	result.
	(event_location_to_sals): For linespec locations, set is_linespec.
	Handle explicit locations.
	(decode_objc): 'ls' contains an explicit location now. Update all
	references.
	(symtabs_from_filename): Use source_file_not_found_error.
	* location.c (struct event_location.u) <explicit>: New member.
	(initialize_explicit_location): New function.
	(initialize_event_location): Initialize explicit locations.
	(new_explicit_location, get_explicit_location)
	(get_explicit_location_const): New functions.
	(explicit_to_string_internal): New function; most of contents moved
	from canonicalize_linespec.
	(explicit_location_to_string): New function.
	(explicit_location_to_linespec): New function.
	(copy_event_location, delete_event_location)
	(event_location_to_string_const, event_location_empty_p): Handle
	explicit locations.
	* location.h (enum offset_relative_sign, struct line_offset): Move
	here from linespec.h.
	(enum event_location_type): Add EXPLICIT_LOCATION.
	(struct explicit_location): New structure.
	(explicit_location_to_string): Declare.
	(explicit_location_to_linespec): Declare.
	(new_explicit_location, get_explicit_locationp
	(get_explicit_location_const, initialize_explicit_location): Declare.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Explicit locations: introduce probe locations
@ 2015-08-12  3:38 sergiodj+buildbot
  2015-08-12 18:33 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-12  3:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5b56227bdc000d129d393772f1e4544b5ea0fd46 ***

Author: Keith Seitz <keiths@redhat.com>
Branch: master
Commit: 5b56227bdc000d129d393772f1e4544b5ea0fd46

Explicit locations: introduce probe locations

This patch adds support for probe locations and converts existing
probe linespec locations to the new location type.

gdb/ChangeLog:

	* break-catch-throw.c (re_set_exception_catchpoint): Convert
	linespec for stap probe to probe location.
	* breakpoint.c (create_longjmp_master_breakpoint)
	(create_exception_master_breakpoint): Likewise.
	(break_command_1): Remove local variable `arg_cp'.
	Check location type to set appropriate breakpoint ops methods.
	(trace_command): Likewise.
	* linespec.c (event_location_to_sals): Assert on probe locations.
	* location.c (EL_PROBE): Add macro definition.
	(new_probe_location, get_probe_location): New functions.
	(copy_event_location, delete_event_location, event_location_to_string)
	(string_to_event_location, event_location_empty_p): Handle probe
	locations.
	* location.h (enum event_location_type): Add PROBE_LOCATION.
	(new_probe_location, get_probe_location): Declare.
	* probe.c (parse_probes): Assert that LOCATION is a probe location.
	Convert linespec into probe location.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Explicit locations: introduce address locations
@ 2015-08-12  3:12 sergiodj+buildbot
  2015-08-12 17:49 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-12  3:12 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a06efdd6effd149a1d392df8d62824e44872003a ***

Author: Keith Seitz <keiths@redhat.com>
Branch: master
Commit: a06efdd6effd149a1d392df8d62824e44872003a

Explicit locations: introduce address locations

This patch adds support for address locations, of the form "*ADDR".
[Support for address linespecs has been removed/replaced by this "new"
location type.] This patch also converts any existing address locations
from its previous linespec type.

gdb/ChangeLog:

	* breakpoint.c (create_thread_event_breakpoint, init_breakpoint_sal):
	Convert linespec to address location.
	* linespec.c (canonicalize_linespec): Do not handle address
	locations here.
	(convert_address_location_to_sals): New function; contents moved
	from ...
	(convert_linespc_to_sals): ... here.
	(parse_linespec): Remove address locations from linespec grammar.
	Remove handling of address locations.
	(linespec_lex_to_end): Remove handling of address linespecs.
	(event_location_to_sals): Handle ADDRESS_LOCATION.
	(linespec_expression_to_pc): Export.
	* linespec.h (linespec_expression_to_pc): Add declaration.
	* location.c (struct event_location.u) <address>: New member.
	(new_address_location, get_address_location): New functions.
	(copy_event_location, delete_event_location, event_location_to_string)
	(string_to_event_location, event_location_empty_p): Handle address
	locations.
	* location.h (enum event_location_type): Add ADDRESS_LOCATION.
	(new_address_location, get_address_location): Declare.
	* python/py-finishbreakpoint.c (bpfinishpy_init): Convert linespec
	to address location.
	* spu-tdep.c (spu_catch_start): Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Explicit locations: use new location API
@ 2015-08-12  2:47 sergiodj+buildbot
  2015-08-12 17:07 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-12  2:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f00aae0f7b11c4dc85c38d5fad46975033ba3fff ***

Author: Keith Seitz <keiths@redhat.com>
Branch: master
Commit: f00aae0f7b11c4dc85c38d5fad46975033ba3fff

Explicit locations: use new location API

This patch converts the code base to use the new struct event_location
API being introduced. This patch preserves the current functionality and
adds no new features.

The "big picture" API usage introduced by this patch may be illustrated
with a simple exmaple. Where previously developers would write:

void
my_command (char *arg, int from_tty)
{
   create_breakpoint (..., arg, ...);
   ...
}

one now uses:

void
my_command (char *arg, int from_tty)
{
   struct event_locaiton *location;
   struct cleanup *back_to;

   location = string_to_event_locaiton (&arg, ...);
   back_to = make_cleanup_delete_event_location (location);
   create_breakpoint (..., location, ...);
   do_cleanups (back_to);
}

Linespec-decoding functions (now called location-decoding) such as
decode_line_full no longer skip argument pointers over processed input.
That functionality has been moved into string_to_event_location as
demonstrated above.

gdb/ChangeLog

	* ax-gdb.c: Include location.h.
	(agent_command_1) Use linespec location instead of address
	string.
	* break-catch-throw.c: Include location.h.
	(re_set_exception_catchpoint): Use linespec locations instead
	of address strings.
	* breakpoint.c: Include location.h.
	(create_overlay_event_breakpoint, create_longjmp_master_breakpoint)
	(create_std_terminate_master_breakpoint)
	(create_exception_master_breakpoint, update_breakpoints_after_exec):
	Use linespec location instead of address string.
	(print_breakpoint_location):  Use locations and
	event_location_to_string.
	Print extra_string for pending locations for non-MI streams.
	(print_one_breakpoint_location): Use locations and
	event_location_to_string.
	(init_raw_breakpoint_without_location): Initialize b->location.
	(create_thread_event_breakpoint): Use linespec location instead of
	address string.
	(init_breakpoint_sal): Likewise.
	Only save extra_string if it is non-NULL and not the empty string.
	Use event_location_to_string instead of `addr_string'.
	Constify `p' and `endp'.
	Use skip_spaces_const/skip_space_const instead of non-const versions.
	Copy the location into the breakpoint.
	If LOCATION is NULL, save the breakpoint address as a linespec location
	instead of an address string.
	(create_breakpoint_sal): Change `addr_string' parameter to a struct
	event_location. All uses updated.
	(create_breakpoints_sal): Likewise for local variable `addr_string'.
	(parse_breakpoint_sals): Use locations instead of address strings.
	Remove check for empty linespec with conditional.
	Refactor.
	(decode_static_tracepoint_spec): Make argument const and update
	function.
	(create_breakpoint): Change `arg' to a struct event_location and
	rename.
	Remove `copy_arg' and `addr_start'.
	If EXTRA_STRING is empty, set it to NULL.
	Don't populate `canonical' for pending breakpoints.
	Pass `extra_string' to find_condition_and_thread.
	Clear `extra_string' if `rest' was NULL.
	Do not error with "garbage after location" if setting a dprintf
	breakpoint.
	Copy the location into the breakpoint instead of an address string.
	(break_command_1): Use string_to_event_location and pass this to
	create_breakpoint instead of an address string.
	Check against `arg_cp' for a probe linespec.
	(dprintf_command): Use string_to_event_location and pass this to
	create_breakpoint instead of an address string.
	Throw an exception if no format string was specified.
	(print_recreate_ranged_breakpoint): Use event_location_to_string
	instead of address strings.
	(break_range_command, until_break_command)
	(init_ada_exception_breakpoint): Use locations instead
	of address strings.
	(say_where): Print out extra_string for pending locations.
	(base_breakpoint_dtor): Delete `location' and `location_range_end' of
	the breakpoint.
	(base_breakpoint_create_sals_from_location): Use struct event_location
	instead of address string.
	Remove `addr_start' and `copy_arg' parameters.
	(base_breakpoint_decode_location): Use struct event_location instead of
	address string.
	(bkpt_re_set): Use locations instead of address strings.
	Use event_location_empty_p to check for unset location.
	(bkpt_print_recreate): Use event_location_to_string instead of
	an address string.
	Print out extra_string for pending locations.
	(bkpt_create_sals_from_location, bkpt_decode_location)
 	(bkpt_probe_create_sals_from_location): Use struct event_location
	instead of address string.
	(bkpt_probe_decode_location): Use struct event_location instead of
	address string.
	(tracepoint_print_recreate): Use event_location_to_string to
	recreate the tracepoint.
	(tracepoint_create_sals_from_location, tracepoint_decode_location)
	(tracepoint_probe_create_sals_from_location)
	(tracepoint_probe_decode_location): Use struct event_location
	instead of address string.
	(dprintf_print_recreate): Use event_location_to_string to recreate
	the dprintf.
	(dprintf_re_set): Remove check for valid/missing format string.
	(strace_marker_create_sals_from_location)
	(strace_marker_create_breakpoints_sal, strace_marker_decode_location)
	(update_static_tracepoint): Use struct event_location instead of
	address string.
	(location_to_sals): Likewise.
	Pass `extra_string' to find_condition_and_thread.
	For newly resolved pending breakpoint locations, clear the location's
	string representation.
	Assert that the breakpoint's condition string is NULL when
	condition_not_parsed.
	(breakpoint_re_set_default, create_sals_from_location_default)
	(decode_location_default, trace_command, ftrace_command)
	(strace_command, create_tracepoint_from_upload): Use locations
	instead of address strings.
	* breakpoint.h (struct breakpoint_ops) <create_sals_from_location>:
	Use struct event_location instead of address string.
	Update all uses.
	<decode_location>: Likewise.
	(struct breakpoint) <addr_string>: Change to struct event_location
	and rename `location'.
	<addr_string_range_end>: Change to struct event_location and rename
	`location_range_end'.
	(create_breakpoint): Use struct event_location instead of address
	string.
	* cli/cli-cmds.c: Include location.h.
	(edit_command, list_command): Use locations instead of address strings.
	* elfread.c: Include location.h.
	(elf_gnu_ifunc_resolver_return_stop): Use event_location_to_string.
	* guile/scm-breakpoint.c: Include location.h.
	(bpscm_print_breakpoint_smob): Use event_location_to_string.
	(gdbscm_register_breakpoint): Use locations instead of address
	strings.
	* linespec.c: Include location.h.
	(struct ls_parser) <stream>: Change to const char *.
	(PARSER_STREAM): Update.
	(lionespec_lexer_lex_keyword): According to find_condition_and_thread,
	keywords must be followed by whitespace.
	(canonicalize_linespec): Save a linespec location into `canonical'.
	Save a canonical linespec into `canonical'.
	(parse_linespec): Change `argptr' to const char * and rename `arg'.
	All uses updated.
	Update function description.
	(linespec_parser_new): Initialize `parser'.
	Update initialization of  parsing stream.
	(event_location_to_sals): New function.
	(decode_line_full): Change `argptr' to a struct event_location and
	rename it `location'.
	Use locations instead of address strings.
	Call event_location_to_sals instead of parse_linespec.
	(decode_line_1): Likewise.
	(decode_line_with_current_source, decode_line_with_last_displayed)
	Use locations instead of address strings.
	(decode_objc): Likewise.
	Change `argptr' to const char * and rename `arg'.
	(destroy_linespec_result): Delete the linespec result's location
	instead of freeing the address string.
	* linespec.h (struct linespec_result) <addr_string>: Change to
	struct event_location and rename to ...
	<location>: ... this.
	(decode_line_1, decode_line_full): Change `argptr' to struct
	event_location.  All callers updated.
	* mi/mi-cmd-break.c: Include language.h, location.h, and linespec.h.
	(mi_cmd_break_insert_1): Use locations instead of address strings.
	Throw an error if there was "garbage" at the end of the specified
	linespec.
	* probe.c: Include location.h.
	(parse_probes): Change `argptr' to struct event_location.
	Use event locations instead of address strings.
	* probe.h (parse_probes): Change `argptr' to struct event_location.
	* python/py-breakpoint.c: Include location.h.
	(bppy_get_location): Constify local variable `str'.
	Use event_location_to_string.
	(bppy_init): Use locations instead of address strings.
	* python/py-finishbreakpoint.c: Include location.h.
	(bpfinishpy_init): Remove local variable `addr_str'.
	Use locations instead of address strings.
	* python/python.c: Include location.h.
	(gdbpy_decode_line): Use locations instead of address strings.
	* remote.c: Include location.h.
	(remote_download_tracepoint): Use locations instead of address
	strings.
	* spu-tdep.c: Include location.h.
	(spu_catch_start): Remove local variable `buf'.
	Use locations instead of address strings.
	* tracepoint.c: Include location.h.
	(scope_info): Use locations instead of address strings.
	(encode_source_string): Constify parameter `src'.
	* tracepoint.h (encode_source_string): Likewise.

gdb/testsuite/ChangeLog

	* gdb.base/dprintf-pending.exp: Update dprintf "without format"
	test.
	Add tests for missing ",FMT" and ",".


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Explicit locations: introduce new struct event_location-based API
@ 2015-08-12  2:19 sergiodj+buildbot
  2015-08-12 16:12 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-12  2:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c7c1b3e998a77eb077ac3c08c88a97d2e11dfef0 ***

Author: Keith Seitz <keiths@redhat.com>
Branch: master
Commit: c7c1b3e998a77eb077ac3c08c88a97d2e11dfef0

Explicit locations: introduce new struct event_location-based API

This patch introduces the new breakpoint/"linespec" API based on
a new struct event_location.  This API currently only supports
traditional linespecs, maintaining the status quo of the code base.
Future patches will add additional functionality for other location
types such as address locations.

gdb/ChangeLog:

	* Makefile.in (SFILES): Add location.c.
	(HFILES_NO_SRCDIR): Add location.h.
	(COMMON_OBS): Add location.o.
	* linespec.c (linespec_lex_to_end): New function.
	* linespec.h (linespec_lex_to_end): Declare.
	* location.c: New file.
	* location.h: New file.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Explicit locations: rename "address string"/"addr_string" to "location"
@ 2015-08-12  1:53 sergiodj+buildbot
  2015-08-12 14:55 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-12  1:53 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5f700d83f7f3ea422d789c51a25f04818bf788d7 ***

Author: Keith Seitz <keiths@redhat.com>
Branch: master
Commit: 5f700d83f7f3ea422d789c51a25f04818bf788d7

Explicit locations: rename "address string"/"addr_string" to "location"

This patch renames all occurrances of "addr_string" and "address
string" in the breakpoint/linespec APIs.  This will emphasize the
change from address strings used in setting breakpoints (et al) to the
new locations-based API introduced in subsequent patches.

gdb/ChangeLog:

	* breakpoint.h (struct breakpoint_ops) <create_sals_from_address>:
	Renamed to create_sals_from_location.
	<decode_linespec>: Renamed to decode_location.
	Update all callers.
	* breakpoint.c (create_sals_from_address_default): Renamed to ...
	(create_sals_from_location_default): ... this.
	(addr_string_to_sals): Renamed to ...
	(location_to_sals): ... this.
	(decode_linespec_default): Renamed to ...
	(decode_location_default): ... this.
	(base_breakpoint_create_sals_from_address): Renamed to ...
	(base_breakpoint_create_sals_from_location): ... this.
	(bkpt_create_sals_from_address): Renamed to ...
	(bkpt_create_sals_from_location): ... this.
	(bkpt_decode_linespec): Renamed to ...
	(bkpt_decode_location): ... this.
	(bkpt_probe_create_sals_from_address): Renamed to ...
	(bkpt_probe_create_sals_from_location): ... this.
	(tracepoint_create_sals_from_address): Renamed to ...
	(tracepoint_create_sals_from_location): ... this.
	(tracepoint_decode_linespec): Renamed to ...
	(tracepoint_decode_location): ... this.
	(tracepoint_probe_create_sals_from_address): Renamed to ...
	(tracepoint_probe_create_sals_from_location): ... this.
	(tracepoint_probe_decode_linespec): Renamed to ...
	(tracepoint_probe_decode_location): ... this.
	(strace_marker_create_sals_from_address): Renamed to ...
	(strace_marker_create_sals_from_location): ... this.
	(decode_linespec_default): Renamed to ...
	(decode_location_default): ... this.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [AArch64] Improve BFD overflow warning message for -fpic
@ 2015-08-12  1:26 sergiodj+buildbot
  2015-08-12 13:35 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-12  1:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c674f5cd3f900c5b12996ea5188ff818fe9eb6bc ***

Author: Jiong Wang <jiong.wang@arm.com>
Branch: master
Commit: c674f5cd3f900c5b12996ea5188ff818fe9eb6bc

[AArch64] Improve BFD overflow warning message for -fpic

2015-08-11  Jiong Wang  <jiong.wang@arm.com>

bfd/
  * elfnn-aarch64.c (elfNN_aarch64_relocate_section): Improve warning
  message for R_AARCH64_LD64_GOTPAGE_LO15/R_AARCH64_LD32_GOTPAGE_LO14.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [AArch64]Speed up linking speed by skipping unncessary TLS reloc type check
@ 2015-08-12  1:03 sergiodj+buildbot
  2015-08-12 12:24 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-12  1:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9331eea1f83b94c6f5a72ebf643aa8978a0b0a13 ***

Author: Jiong Wang <jiong.wang@arm.com>
Branch: master
Commit: 9331eea1f83b94c6f5a72ebf643aa8978a0b0a13

[AArch64]Speed up linking speed by skipping unncessary TLS reloc type check

2015-08-11  Jiong Wang  <jiong.wang@arm.com>

bfd/
   * elfnn-aarch64.c (IS_AARCH64_TLS_RELAX_RELOC): New.
  (aarch64_can_relax_tls): Use the new IS_AARCH64_TLS_RELAX_RELOC.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [AArch64] Long branch veneer support far symbol defined by --defsym
@ 2015-08-12  0:36 sergiodj+buildbot
  2015-08-12 11:05 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-12  0:36 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f678ded748f994a16e27fc3ac1d1c9451b98f608 ***

Author: Jiong Wang <jiong.wang@arm.com>
Branch: master
Commit: f678ded748f994a16e27fc3ac1d1c9451b98f608

[AArch64] Long branch veneer support far symbol defined by --defsym

2015-08-11  Jiong Wang  <jiong.wang@arm.com>

bfd/
  * bfd/elfnn-aarch64.c (aarch64_type_of_stub): New parameter "sym_sec".
  Loose the check for symbol from ABS section.
  (elfNN_aarch64_size_stubs): Pass sym_sec.

ld/testsuite/
  * ld-aarch64/farcall-b-defsym.s: New test.
  * ld-aarch64/farcall-bl-defsym.s: Likewise.
  * ld-aarch64/farcall-b-defsym.d: New expectation.
  * ld-aarch64/farcall-bl-defsym.d: Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [AArch64] PR18668, repair long branch veneer for plt stub
@ 2015-08-12  0:11 sergiodj+buildbot
  2015-08-12  9:40 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-12  0:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 07f9ddfeba5b572451471f905473f7ddbba1d472 ***

Author: Jiong Wang <jiong.wang@arm.com>
Branch: master
Commit: 07f9ddfeba5b572451471f905473f7ddbba1d472

[AArch64] PR18668, repair long branch veneer for plt stub

2015-08-11  Jiong Wang  <jiong.wang@arm.com>
bfd/
   PR ld/18668
   * elfnn-aarch64.c (aarch64_type_of_stub): Update destination for
   calls go through plt stub.
   (elfNN_aarch64_final_link_relocate): Adjust code logic for CALL26,
   JUMP26 relocation to support inserting veneer for call to plt stub.

ld/testsuite/
   * ld-aarch64/farcall-b-gsym.s: New test.
   * ld-aarch64/farcall-b-plt.s: Likewise.
   * ld-aarch64/farcall-bl-plt.s: Likewise.
   * ld-aarch64/farcall-b-gsym.d: New expect file.
   * ld-aarch64/farcall-b-plt.d: Likewise.
   * ld-aarch64/farcall-bl-plt.d: Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [AArch64][8/8] LD support BFD_RELOC_AARCH64_TLSLD_ADD_DTPREL_LO12
@ 2015-08-11 23:44 sergiodj+buildbot
  2015-08-12  8:22 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-11 23:44 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 40fbed84815b00960f7fac8d2e7857942df4308c ***

Author: Jiong Wang <jiong.wang@arm.com>
Branch: master
Commit: 40fbed84815b00960f7fac8d2e7857942df4308c

[AArch64][8/8] LD support BFD_RELOC_AARCH64_TLSLD_ADD_DTPREL_LO12

2015-08-11  Jiong Wang  <jiong.wang@arm.com>

bfd/
  * elfnn-aarch64.c (IS_AARCH64_TLS_RELOC): Recognize
  BFD_RELOC_AARCH64_TLSLD_ADD_DTPREL_LO12.
  (aarch64_reloc_got_type): Likewise.
  (elfNN_aarch64_final_link_relocate): Likewise.
  (elfNN_aarch64_relocate_section): Likewise.
  * elfxx-aarch64.c (_bfd_aarch64_elf_put_addend): Likewise.
  (_bfd_aarch64_elf_resolve_relocation): Likewise.

ld/testsuite/
  * ld-aarch64/emit-relocs-529.s: New testcase.
  * ld-aarch64/emit-relocs-529-overflow.s: Likewise.
  * ld-aarch64/emit-relocs-86.s: Likewise.
  * ld-aarch64/emit-relocs-86-overflow.s: Likewise.
  * ld-aarch64/emit-relocs-529.d: New expectation file.
  * ld-aarch64/emit-relocs-529-overflow.d: Likewise.
  * ld-aarch64/emit-relocs-86.d: Likewise.
  * ld-aarch64/emit-relocs-86-overflow.d: Likewise.
  * ld-aarch64/aarch64-elf.exp: Run new testcases.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [AArch64][7/8] GAS support BFD_RELOC_AARCH64_TLSLD_ADD_DTPREL_LO12
@ 2015-08-11 23:19 sergiodj+buildbot
  2015-08-12  7:12 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-11 23:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 70151fb54ab6e3d5dc7f99fe3fbfa7ad2f1ab2af ***

Author: Jiong Wang <jiong.wang@arm.com>
Branch: master
Commit: 70151fb54ab6e3d5dc7f99fe3fbfa7ad2f1ab2af

[AArch64][7/8] GAS support BFD_RELOC_AARCH64_TLSLD_ADD_DTPREL_LO12

2015-08-11  Jiong Wang  <jiong.wang@arm.com>

include/elf/
  * aarch64.h (R_AARCH64_P32_TLSLD_ADD_DTPREL_LO12): Define.

bfd/
  * reloc.c (BFD_RELOC_AARCH64_TLSLD_ADD_DTPREL_LO12): New entry.
  * bfd-in2.h: Regenerate.
  * libbfd.h: Regenerate.
  * elfnn-aarch64.c (elfNN_aarch64_howto_table): New entry for
  BFD_RELOC_AARCH64_TLSLD_ADD_DTPREL_LO12.

gas/
  * config/tc-aarch64.c (reloc_table): New relocation modifiers
  "dtprel_lo12".
  (md_apply_fix): Support BFD_RELOC_AARCH64_TLSLD_ADD_DTPREL_LO12.
  (aarch64_force_relocation): Likewise.

gas/testsuite/
  * gas/aarch64/reloc-dtprel_lo12-1.s: New testcase.
  * gas/aarch64/reloc-dtprel_lo12-ilp32-1.s: Likewise.
  * gas/aarch64/reloc-dtprel_lo12-1.d: New expectation file.
  * gas/aarch64/reloc-dtprel_lo12-ilp32-1.d: Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [AArch64][6/8] LD support BFD_RELOC_AARCH64_TLSLD_ADD_LO12_NC
@ 2015-08-11 22:57 sergiodj+buildbot
  2015-08-12  6:02 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-11 22:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 73f925cc20e839d4b7352b809a33e4e7dcbfa05a ***

Author: Jiong Wang <jiong.wang@arm.com>
Branch: master
Commit: 73f925cc20e839d4b7352b809a33e4e7dcbfa05a

[AArch64][6/8] LD support BFD_RELOC_AARCH64_TLSLD_ADD_LO12_NC

2015-08-11  Jiong Wang  <jiong.wang@arm.com>

bfd/
  * elfnn-aarch64.c (IS_AARCH64_TLS_RELOC): Recognize
  BFD_RELOC_AARCH64_TLSLD_ADD_LO12_NC.
  (aarch64_reloc_got_type): Likewise.
  (elfNN_aarch64_final_link_relocate): Likewise.
  (elfNN_aarch64_relocate_section): Likewise.
  (elfNN_aarch64_gc_sweep_hook): Likewise.
  (elfNN_aarch64_check_relocs): Likewise.
  * elfxx-aarch64.c (_bfd_aarch64_elf_put_addend): Likewise.
  (_bfd_aarch64_elf_resolve_relocation): Likewise.

ld/testsuite/
  * ld-aarch64/tls-small-ld.s: Update testcase.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [AArch64][5/8] GAS support BFD_RELOC_AARCH64_TLSLD_ADD_LO12_NC
@ 2015-08-11 22:27 sergiodj+buildbot
  2015-08-12  4:53 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-11 22:27 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a12fad50d28b9251893c6709ac4374773350c21a ***

Author: Jiong Wang <jiong.wang@arm.com>
Branch: master
Commit: a12fad50d28b9251893c6709ac4374773350c21a

[AArch64][5/8] GAS support BFD_RELOC_AARCH64_TLSLD_ADD_LO12_NC

2015-08-11  Jiong Wang  <jiong.wang@arm.com>

bfd/
  * reloc.c (BFD_RELOC_AARCH64_TLSLD_ADD_LO12_NC): New entry.
  * bfd-in2.h: Regenerate.
  * libbfd.h: Regenerate.
  * elfnn-aarch64.c (elfNN_aarch64_howto_table): New entry for
  BFD_RELOC_AARCH64_TLSLD_ADD_LO12_NC.

gas/
  * config/tc-aarch64.c (reloc_table): New relocation modifiers.
  (md_apply_fix): Support BFD_RELOC_AARCH64_TLSLD_ADD_LO12_NC.
  (aarch64_force_relocation): Likewise.

gas/testsuite/
  * gas/aarch64/reloc-tlsldm_lo12_nc-1.s: New testcase.
  * gas/aarch64/reloc-tlsldm_lo12_nc-ilp32-1.s: Likewise.
  * gas/aarch64/reloc-tlsldm_lo12_nc-1.d: New expectation file.
  * gas/aarch64/reloc-tlsldm_lo12_nc-ilp32-1.d: Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [AArch64][4/8] Add R_AARCH64_P32_TLSLD_ADD_LO12_NC in elf header
@ 2015-08-11 22:07 sergiodj+buildbot
  2015-08-12  3:40 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-11 22:07 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 56a2e4507a4249634422fba2373b651b774c55ac ***

Author: Jiong Wang <jiong.wang@arm.com>
Branch: master
Commit: 56a2e4507a4249634422fba2373b651b774c55ac

[AArch64][4/8] Add R_AARCH64_P32_TLSLD_ADD_LO12_NC in elf header

2015-08-11  Jiong Wang  <jiong.wang@arm.com>

include/elf/
  * aarch64.h (R_AARCH64_P32_TLSLD_ADD_LO12_NC): Define.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [AArch64][3/8] LD support BFD_RELOC_AARCH64_TLSLD_ADR_PAGE21
@ 2015-08-11 21:42 sergiodj+buildbot
  2015-08-12  2:26 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-11 21:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f69e49203b49b7353748b78a9d8111440d9ac291 ***

Author: Jiong Wang <jiong.wang@arm.com>
Branch: master
Commit: f69e49203b49b7353748b78a9d8111440d9ac291

[AArch64][3/8] LD support BFD_RELOC_AARCH64_TLSLD_ADR_PAGE21

2015-08-11  Jiong Wang  <jiong.wang@arm.com>

bfd/
  * elfnn-aarch64.c (IS_AARCH64_TLS_RELOC): Recognize
  BFD_RELOC_AARCH64_TLSLD_ADR_PAGE21.
  (aarch64_reloc_got_type): Likewise.
  (elfNN_aarch64_final_link_relocate): Likewise.
  (elfNN_aarch64_relocate_section): Likewise.
  (elfNN_aarch64_gc_sweep_hook): Likewise.
  (elfNN_aarch64_check_relocs): Likewise.
  * elfxx-aarch64.c (_bfd_aarch64_elf_put_addend): Likewise.
  (_bfd_aarch64_elf_resolve_relocation): Likewise.

ld/testsuite/
  * ld-aarch64/tls-small-ld.s: New file.
  * ld-aarch64/tls-small-ld.d: Likewise.
  * ld-aarch64/aarch64-elf.exp: Run new test.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [AArch64][2/8] GAS support BFD_RELOC_AARCH64_TLSLD_ADR_PAGE21
@ 2015-08-11 21:17 sergiodj+buildbot
  2015-08-11 23:50 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-11 21:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1107e076cff62e1093da024ab73e5648051781ab ***

Author: Jiong Wang <jiong.wang@arm.com>
Branch: master
Commit: 1107e076cff62e1093da024ab73e5648051781ab

[AArch64][2/8] GAS support BFD_RELOC_AARCH64_TLSLD_ADR_PAGE21

2015-08-11  Jiong Wang  <jiong.wang@arm.com>

bfd/
  * reloc.c (BFD_RELOC_AARCH64_TLSLD_ADR_PAGE21): New entry.
  * bfd-in2.h: Regenerate.
  * libbfd.h: Regenerate.
  * elfnn-aarch64.c (elfNN_aarch64_howto_table): New entry for
  BFD_RELOC_AARCH64_TLSLD_ADR_PAGE21.

gas/
  * config/tc-aarch64.c (reloc_table): New relocation modifiers.
  (md_apply_fix): Support BFD_RELOC_AARCH64_TLSLD_ADR_PAGE21.
  (aarch64_force_relocation): Likewise.

gas/testsuite/
  * gas/aarch64/reloc-tlsldm-page-1.s: New testcase.
  * gas/aarch64/reloc-tlsldm-page-ilp32-1.s: Likewise.
  * gas/aarch64/reloc-tlsldm-page-1.d: New expectation file.
  * gas/aarch64/reloc-tlsldm-page-ilp32-1.d: Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [AArch64][1/8] Add R_AARCH64_P32_TLSLD_ADR_PAGE21 in elf header
@ 2015-08-11 20:42 sergiodj+buildbot
  2015-08-11 22:15 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-11 20:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2c0a466a7f83eb1ee5f5da0bdd7b4b643fbe3278 ***

Author: Jiong Wang <jiong.wang@arm.com>
Branch: master
Commit: 2c0a466a7f83eb1ee5f5da0bdd7b4b643fbe3278

[AArch64][1/8] Add R_AARCH64_P32_TLSLD_ADR_PAGE21 in elf header

2015-08-11  Jiong Wang  <jiong.wang@arm.com>

include/elf/
  * aarch64.h (R_AARCH64_P32_TLSLD_ADR_PAGE21): Define.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Skip IFUNC relocations in debug sections
@ 2015-08-11 20:12 sergiodj+buildbot
  2015-08-11 21:02 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-11 20:12 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 97dc35c88dd470465a99edeb0b491012a368f2bf ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 97dc35c88dd470465a99edeb0b491012a368f2bf

Skip IFUNC relocations in debug sections

Skip IFUNC relocations in debug sections ignored by ld.so.

bfd/

	PR ld/18808
	* elf32-i386.c (elf_i386_relocate_section): Skip IFUNC
	relocations in debug sections.
	* elf64-x86-64.c (elf_x86_64_relocate_section): Likewise.

ld/testsuite/

	PR ld/18808
	* ld-ifunc/ifunc.exp: Add a test for PR ld/18808.
	* ld-ifunc/pr18808.out: New file.
	* ld-ifunc/pr18808a.c: Likewise.
	* ld-ifunc/pr18808b.c: Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix the disassembly of the AArch64 SIMD EXT instruction.
@ 2015-08-11 17:19 sergiodj+buildbot
  2015-08-11 19:39 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-11 17:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 922c5db5e733526f12e2fbfeb72c7f1f90089d53 ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: 922c5db5e733526f12e2fbfeb72c7f1f90089d53

Fix the disassembly of the AArch64 SIMD EXT instruction.

	PR 18800
	* aarch64-tbl.h (aarch64_opcode_table): Fix mask for SIMD EXT
	instruction.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix encoding or OpenRisk1000 PC relative relocations.
@ 2015-08-11 16:46 sergiodj+buildbot
  2015-08-11 18:26 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-11 16:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT dbac553d28887561e3f154654ec8e70195d89943 ***

Author: Peter Zotov <whitequark@whitequark.org>
Branch: master
Commit: dbac553d28887561e3f154654ec8e70195d89943

Fix encoding or OpenRisk1000 PC relative relocations.

	PR ld/18759
	* elf32-or1k.c (R_OR1K_32_PCREL): Set pcrel_offset to TRUE.
	(R_OR1K_16_PCREL): Likewise.
	(R_OR1K_8_PCREL): Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix typo in coff-sh.c.
@ 2015-08-11 16:13 sergiodj+buildbot
  2015-08-11 17:12 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-11 16:13 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4c0160b8e2f902ecdf6a42dc20b5f39b0a48fac7 ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: 4c0160b8e2f902ecdf6a42dc20b5f39b0a48fac7

Fix typo in coff-sh.c.

	PR binutils/18747
	* coff-sh.c (_bfd_sh_align_load_span): Fix typo when setting
	opcode count.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix memory access problems discovered when running some binary tools on corrupt files.
@ 2015-08-11 11:35 sergiodj+buildbot
  2015-08-11 12:55 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-11 11:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4b0e8a5f80441fad8eddaf68e7af70bd6991aa37 ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: 4b0e8a5f80441fad8eddaf68e7af70bd6991aa37

Fix memory access problems discovered when running some binary tools on corrupt files.

	PR binutils/18758
	* elf.c (_bfd_elf_setup_sections): Add checks for corrupt section
	group information.
	* peicode.h (pe_ILF_make_a_section): Ensure alignment of the
	used_by_bfd pointer.
	(pe_ILF_build_a_bfd): Ensure alignment of vars.data pointer.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix a typo in _bfd_elf_copy_private_bfd_data
@ 2015-08-11 11:05 sergiodj+buildbot
  2015-08-11 11:45 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-11 11:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 64140f86ab732f9ed87beccab07c32befaf9ca52 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 64140f86ab732f9ed87beccab07c32befaf9ca52

Fix a typo in _bfd_elf_copy_private_bfd_data

	* elf.c (_bfd_elf_copy_private_bfd_data): Fix a typo.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] PR gdb/18669 libiberty demangle.test failure: strtod() on sparc-sun-solaris2.9
@ 2015-08-11  7:25 sergiodj+buildbot
  2015-08-11  8:05 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-11  7:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 30379291886a171e6dc202122bc1c583318c2e17 ***

Author: Iain Buclaw <ibuclaw@gdcproject.org>
Branch: master
Commit: 30379291886a171e6dc202122bc1c583318c2e17

PR gdb/18669 libiberty demangle.test failure: strtod() on sparc-sun-solaris2.9

Test symbols did not demangle as per the d-demangle-expected tests because
strtod() on Solaris 9 does not accept hexadecimal numbers.

This has now been fixed up so that no attempt at formatting/converting the
demangled hexadecimal literals are done.

libiberty/ChangeLog:

2015-08-11  Iain Buclaw  <ibuclaw@gdcproject.org>

	* d-demangle.c (dlang_parse_real): Remove call to strtod.
	(strtod): Remove declaration.
	* testsuite/d-demangle-expected: Update float and complex literal
	tests to check correct hexadecimal demangling.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] PR gdb/17960 Internal error: tracker != NULL when completing on file:function
@ 2015-08-10 19:25 sergiodj+buildbot
  2015-08-10 20:07 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-10 19:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e27852be65403306da198b3c1d7b222acd6bdfe9 ***

Author: Doug Evans <dje@google.com>
Branch: master
Commit: e27852be65403306da198b3c1d7b222acd6bdfe9

PR gdb/17960 Internal error: tracker != NULL when completing on file:function

gdb/ChangeLog:

	* symtab.c (make_file_symbol_completion_list_1): Renamed from
	make_file_symbol_completion_list and made static.
	(make_file_symbol_completion_list): New function.

gdb/testsuite/ChangeLog:

	* gdb.base/completion.exp: Add location completer tests.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] gdb/infrun.c: Various trivial ARI fixes.
@ 2015-08-10 18:17 sergiodj+buildbot
  2015-08-10 18:53 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-10 18:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fd7dcb94cbd44629b3929336aec8b76c3e339656 ***

Author: Joel Brobecker <brobecker@adacore.com>
Branch: master
Commit: fd7dcb94cbd44629b3929336aec8b76c3e339656

gdb/infrun.c: Various trivial ARI fixes.

gdb/ChangeLog:

        * infrun.c (follow_fork, displaced_step_prepare, resume): Remove
        trailing new-line at end of warning message.
        (proceed): Add i18n marker to error messages.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Replace hidden with versioned in elf_link_hash_entry
@ 2015-08-10 15:08 sergiodj+buildbot
  2015-08-10 16:07 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-10 15:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 422f11824b3abf6c71042e2ee3aed572f250fc89 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 422f11824b3abf6c71042e2ee3aed572f250fc89

Replace hidden with versioned in elf_link_hash_entry

This patch replaces the "hidden" field with the "versioned" field in
elf_link_hash_entry so that we can avoid calling strchr and strrchr if
the symbol is unversioned.

	* elf-bfd.h (elf_symbol_version): New enum.
	(elf_link_hash_entry): Replace hidden with versioned.
	* elflink.c (_bfd_elf_merge_symbol): Don't look for symbol
	version if the symbol is unversioned.  Initialize versioned.
	(_bfd_elf_add_default_symbol): Don't look for symbol version
	if the symbol is unversioned or hidden.  Initialize versioned.
	(elf_collect_hash_codes): Don't look for symbol version if the
	symbol is unversioned.
	(elf_collect_gnu_hash_codes): Likewise.
	(bfd_elf_gc_mark_dynamic_ref_symbol): Likewise.
	(_bfd_elf_link_hash_copy_indirect): Check versioned instead of
	hidden.
	(elf_link_output_extsym): Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Add SIGRIE instruction for MIPS R6
@ 2015-08-10  8:27 sergiodj+buildbot
  2015-08-10 14:55 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-10  8:27 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 75fb7498c25ba89262867abe5340a8d38f1e19cd ***

Author: Robert Suchanek <robert.suchanek@imgtec.com>
Branch: master
Commit: 75fb7498c25ba89262867abe5340a8d38f1e19cd

Add SIGRIE instruction for MIPS R6

opcodes/

	* mips-opc.c (mips_builtin_opcodes): Add "sigrie".

gas/testsuite/

	* gas/mips/r6.s: Add tests for "sigrie".
	* gas/mips/r6.d: Check for "sigrie".
	* gas/mips/r6-n32.d: Likewise.
	* gas/mips/r6-n64.d: Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Check sh_type/sh_flags/sh_addralign/sh_entsize when copying sh_link/sh_info
@ 2015-08-08  0:51 sergiodj+buildbot
  2015-08-10 12:33 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-08  0:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d4ac1f878ecef58f1e4b4ff0cbfb4b475656eaf4 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: d4ac1f878ecef58f1e4b4ff0cbfb4b475656eaf4

Check sh_type/sh_flags/sh_addralign/sh_entsize when copying sh_link/sh_info

When copying the sh_link and sh_info fields in stripped section headers,
we also check if the sh_type, sh_flags, /sh_addralign and sh_entsize
fields of the output section match the output.  Since --only-keep-debug
turns all non-debug sections into SHT_NOBITS sections, the output
SHT_NOBITS type matches any input type.

bfd/

	PR binutils/18785
	* elf.c (_bfd_elf_copy_private_bfd_data): When copying the
	sh_link and sh_info fields in stripped section headers, we also
	check if the sh_type, sh_flags, /sh_addralign and sh_entsize
	fields of the output section match the output.  Since
	--only-keep-debug turns all non-debug sections into SHT_NOBITS
	sections, the output SHT_NOBITS type matches any input type.

binutils/testsuite/

	PR binutils/18785
	* binutils-all/objcopy.exp: Run strip-12.
	* binutils-all/strip-12.d: New file.
	* binutils-all/strip-12.s: Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] native Linux: enable always non-stop by default
@ 2015-08-08  0:24 sergiodj+buildbot
  2015-08-10  9:51 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-08  0:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f12899e9f081bb857c96999386e64a4252c4a325 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: f12899e9f081bb857c96999386e64a4252c4a325

native Linux: enable always non-stop by default

The testsuite shows no regressions with this forced on, on:

 - Native x86_64 Fedora 20, with and output "set displaced off".

 - Native x86_64 Fedora 20, on top of x86 software single-step series.

 - PPC64 Fedora 18.

 - S/390 RHEL 7.1.

Let's try making it the default.

gdb/ChangeLog:
2015-08-07  Pedro Alves  <palves@redhat.com>

	* linux-nat.c (linux_nat_always_non_stop_p): Return 1.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] S/390: displaced stepping and PC-relative RIL-b/RIL-c instructions
@ 2015-08-07 23:57 sergiodj+buildbot
  2015-08-09 23:17 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-07 23:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5ac213430b710e8aaed1f4cea6ff809783201df9 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 5ac213430b710e8aaed1f4cea6ff809783201df9

S/390: displaced stepping and PC-relative RIL-b/RIL-c instructions

This adds displaced stepping support for the General-Instruction
Extension Facility instructions, which have a PC-relative displacement
(RIL-b/RIL-c).  We already handle RIL branches, but not others.

Currently, displaced stepping a breakpoint put on any of these
instructions results in the inferior crashing when or after the
instruction is executed out-of-line in the scratch pad.

This patch takes the easy route of patching the displacement in the
copy of the instruction in the scratch pad.  As the displacement is a
signed 32-bit field, it's possible that the stratch pad ends too far
that the needed displacement doesn't fit in the adjusted instruction,
as e.g., if stepping over a breakpoint in a shared library (the
scratch pad is around the main program's entry point).  That case is
detected and GDB falls back to stepping over the breakpoint in-line
(which involves pausing all threads momentarily).

(We could probably do something smarter, but I don't plan on doing it
myself.  This was already sufficient to get "maint set target-non-stop
on" working regression free on S/390.)

Tested on S/390 RHEL 7.1, where it fixes a few hundred FAILs when
testing with displaced stepping force-enabled, with the end result
being no regressions compared to a test run that doesn't force
displaced stepping.  Fixes the non-stop tests compared to mainline
too; most are crashing due to this on the machine I run tests on.

gdb/ChangeLog:
2015-08-07  Pedro Alves  <palves@redhat.com>

	* s390-linux-tdep.c (is_non_branch_ril)
	(s390_displaced_step_copy_insn): New functions.
	(s390_displaced_step_fixup): Update comment.
	(s390_gdbarch_init): Install s390_displaced_step_copy_insn as
	gdbarch_displaced_step_copy_insn hook.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] PPC64: Fix gdb.arch/ppc64-atomic-inst.exp with displaced stepping
@ 2015-08-07 23:36 sergiodj+buildbot
  2015-08-09 22:02 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-07 23:36 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7f03bd92e389a32da490bb55037881cf374d0f69 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 7f03bd92e389a32da490bb55037881cf374d0f69

PPC64: Fix gdb.arch/ppc64-atomic-inst.exp with displaced stepping

The ppc64 displaced step code can't handle atomic sequences.  Fallback
to stepping over the breakpoint in-line if we detect one.

gdb/ChangeLog:
2015-08-07  Pedro Alves  <palves@redhat.com>

	* infrun.c (displaced_step_prepare_throw): Return -1 if
	gdbarch_displaced_step_copy_insn returns NULL.  Update intro
	comment.
	* rs6000-tdep.c (LWARX_MASK, LWARX_INSTRUCTION, LDARX_INSTRUCTION)
	(STWCX_MASK, STWCX_INSTRUCTION, STDCX_INSTRUCTION): Move higher up
	in file.
	(ppc_displaced_step_copy_insn): New function.
	(ppc_displaced_step_fixup): Update comment.
	(rs6000_gdbarch_init): Install ppc_displaced_step_copy_insn as
	gdbarch_displaced_step_copy_insn hook.
	* gdbarch.sh (displaced_step_copy_insn): Document what happens on
	NULL return.
	* gdbarch.h: Regenerate.

gdb/testsuite/ChangeLog:
2015-08-07  Pedro Alves  <palves@redhat.com>

	* gdb.arch/ppc64-atomic-inst.exp (do_test): New procedure, move
	tests here.
	(top level): Run do_test with and without displaced stepping.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Disable displaced stepping if trying it fails
@ 2015-08-07 23:02 sergiodj+buildbot
  2015-08-09 20:51 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-07 23:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3fc8eb30a95df3fd07a63e9bd0a9d309b86a0357 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 3fc8eb30a95df3fd07a63e9bd0a9d309b86a0357

Disable displaced stepping if trying it fails

Running the testsuite with "maint set target-non-stop on" shows:

 (gdb) PASS: gdb.base/valgrind-infcall.exp: continue #98 (false warning)
 continue
 Continuing.
 dl_main (phdr=<optimized out>..., auxv=<optimized out>) at rtld.c:2302
 2302      LIBC_PROBE (init_complete, 2, LM_ID_BASE, r);
 Cannot access memory at address 0x400532
 (gdb) PASS: gdb.base/valgrind-infcall.exp: continue #99 (false warning)
 p gdb_test_infcall ()
 $1 = 1
 (gdb) FAIL: gdb.base/valgrind-infcall.exp: p gdb_test_infcall ()

Even though that was a native GNU/Linux test run, this test spawns
Valgrind and connects to it with "target remote".  The error above is
actually orthogonal to target-non-stop.  The real issue is that that
enables displaced stepping, and displaced stepping doesn't work with
Valgrind, because we can't write to the inferior memory (thus can't
copy the instruction to the scratch pad area).

I'm sure there will be other targets with the same issue, so trying to
identify Valgrind wouldn't be sufficient.  The fix is to try setting
up the displaced step anyway.  If we get a MEMORY_ERROR, we disable
displaced stepping for that inferior, and fall back to doing an
in-line step-over.  If "set displaced-stepping" is "on" (as opposed to
"auto), GDB warns displaced stepping failed ("on" is mainly useful for
the testsuite, not for users).

Tested on x86_64 Fedora 20.

gdb/ChangeLog:
2015-08-07  Pedro Alves  <palves@redhat.com>

	* inferior.h (struct inferior) <displaced_stepping_failed>: New
	field.
	* infrun.c (use_displaced_stepping_now_p): New parameter 'inf'.
	Return false if dispaced stepping failed before.
	(resume): Pass the current inferior to
	use_displaced_stepping_now_p.  Wrap displaced_step_prepare in
	TRY/CATCH.  If we get a MEMORY_ERROR, set the inferior's
	displaced_stepping_failed flag, and fall back to an in-line
	step-over.

gdb/testsuite/ChangeLog:
2015-08-07  Pedro Alves  <palves@redhat.com>

	* gdb.base/valgrind-disp-step.c: New file.
	* gdb.base/valgrind-disp-step.exp: New file.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix step-over-{trips-on-watchpoint|lands-on-breakpoint}.exp race
@ 2015-08-07 22:44 sergiodj+buildbot
  2015-08-09 19:40 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-07 22:44 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d4569d7bc572ae8f10d7c527cbdfbc9d26cc1ed8 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: d4569d7bc572ae8f10d7c527cbdfbc9d26cc1ed8

Fix step-over-{trips-on-watchpoint|lands-on-breakpoint}.exp race

On a target that is both always in non-stop mode and can do displaced
stepping (such as native x86_64 GNU/Linux, with "maint set
target-non-stop on"), the step-over-trips-on-watchpoint.exp test
sometimes fails like this:

   (gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: no thread-specific bp: step: thread 1
   set scheduler-locking off
   (gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: no thread-specific bp: step: set scheduler-locking off
   step
  -[Switching to Thread 0x7ffff7fc0700 (LWP 11782)]
  -Hardware watchpoint 4: watch_me
  -
  -Old value = 0
  -New value = 1
  -child_function (arg=0x0) at /home/pedro/gdb/mygit/src/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c:39
  -39           other = 1; /* set thread-specific breakpoint here */
  -(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: no thread-specific bp: step: step
  +wait_threads () at /home/pedro/gdb/mygit/src/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c:49
  +49       return 1; /* in wait_threads */
  +(gdb) FAIL: gdb.threads/step-over-trips-on-watchpoint.exp: no thread-specific bp: step: step

Note "scheduler-locking" was set off.  The problem is that on such
targets, the step-over of thread 2 and the "step" of thread 1 can be
set to run simultaneously (since with displaced stepping the
breakpoint isn't ever removed from the target), and sometimes, the
"step" of thread 1 finishes first, so it'd take another resume to see
the watchpoint trigger.  Fix this by replacing the wait_threads
function with a one-line infinite loop that doesn't call any function,
so that the "step" of thread 1 never finishes.

gdb/testsuite/ChangeLog:
2015-08-07  Pedro Alves  <palves@redhat.com>

	* gdb.threads/step-over-lands-on-breakpoint.c (wait_threads):
	Delete function.
	(main): Add alarm.  Run an infinite loop instead of calling
	wait_threads.
	* gdb.threads/step-over-lands-on-breakpoint.exp (do_test): Change
	comment.
	* gdb.threads/step-over-trips-on-watchpoint.c (wait_threads):
	Delete function.
	(main): Add alarm.  Run an infinite loop instead of calling
	wait_threads.
	* gdb.threads/step-over-trips-on-watchpoint.exp (do_test): Change
	comment.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix interrupt-noterm.exp on targets always in non-stop
@ 2015-08-07 22:08 sergiodj+buildbot
  2015-08-09 18:30 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-07 22:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bfedc46af315dc6484295699c35e05040d76d700 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: bfedc46af315dc6484295699c35e05040d76d700

Fix interrupt-noterm.exp on targets always in non-stop

With "maint set target-non-stop on" we get:

 @@ -66,13 +66,16 @@ Continuing.
  interrupt
  (gdb) PASS: gdb.base/interrupt-noterm.exp: interrupt

 -Program received signal SIGINT, Interrupt.
 -PASS: gdb.base/interrupt-noterm.exp: inferior received SIGINT
 -testcase src/gdb/testsuite/gdb.base/interrupt-noterm.exp completed in 0 seconds
 +[process 12119] #1 stopped.
 +0x0000003615ebc6d0 in __nanosleep_nocancel () at ../sysdeps/unix/syscall-template.S:81
 +81     T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
 +FAIL: gdb.base/interrupt-noterm.exp: inferior received SIGINT (timeout)
 +testcase src/gdb/testsuite/gdb.base/interrupt-noterm.exp completed in 10 seconds

That is, we get "[$thread] #1 stopped" instead of SIGINT.

The issue is that we don't currently distinguish send
"interrupt/ctrl-c" to target terminal vs "stop/pause" thread well;
both cases go through "target_stop".

And then, the native Linux backend (linux-nat.c) implements
target_stop with SIGSTOP in non-stop mode, and SIGINT in all-stop
mode.  Since "maint set target-non-stop on" forces the backend to be
always running in non-stop mode, even though the user-visible behavior
is "set non-stop" is "off", "interrupt" causes a SIGSTOP instead of
the SIGINT the test expects.

Fix this by introducing a target_interrupt method to use in the
"interrupt/ctrl-c" case, so "set non-stop off" can always work the
same irrespective of "maint set target-non-stop on/off".  I'm
explictly considering changing the "set non-stop on" behavior as out
of scope here.

Most of the patch is an across-the-board rename of to_stop hook
implementations to to_interrupt.  The only targets where something
more than a rename is being done are linux-nat.c and remote.c, which
are the only targets that support async, and thus are the only ones
the core side calls target_stop on.

gdb/ChangeLog:
2015-08-07  Pedro Alves  <palves@redhat.com>

	* darwin-nat.c (darwin_stop): Rename to ...
	(darwin_interrupt): ... this.
	(_initialize_darwin_inferior): Adjust.
	* gnu-nat.c (gnu_stop): Delete.
	(gnu_target): Don't install gnu_stop.
	* inf-ptrace.c (inf_ptrace_stop): Rename to ...
	(inf_ptrace_interrupt): ... this.
	(inf_ptrace_target): Adjust.
	* infcmd.c (interrupt_target_1): Use target_interrupt instead of
	target_stop.
	* linux-nat (linux_nat_stop): Rename to ...
	(linux_nat_interrupt): ... this.
	(linux_nat_stop): Reimplement.
	(linux_nat_add_target): Install linux_nat_interrupt.
	* nto-procfs.c (nto_interrupt_twice): Rename to ...
	(nto_handle_sigint_twice): ... this.
	(nto_interrupt): Rename to ...
	(nto_handle_sigint): ... this.  Call target_interrupt instead of
	target_stop.
	(procfs_wait): Adjust.
	(procfs_stop): Rename to ...
	(procfs_interrupt): ... this.
	(init_procfs_targets): Adjust.
	* procfs.c (procfs_stop): Rename to ...
	(procfs_interrupt): ... this.
	(procfs_target): Adjust.
	* remote-m32r-sdi.c (m32r_stop): Rename to ...
	(m32r_interrupt): ... this.
	(init_m32r_ops): Adjust.
	* remote-sim.c (gdbsim_stop_inferior): Rename to ...
	(gdbsim_interrupt_inferior): ... this.
	(gdbsim_stop): Rename to ...
	(gdbsim_interrupt): ... this.
	(gdbsim_cntrl_c): Adjust.
	(init_gdbsim_ops): Adjust.
	* remote.c (sync_remote_interrupt): Adjust comments.
	(remote_stop_as): Rename to ...
	(remote_interrupt_as): ... this.
	(remote_stop): Adjust comment.
	(remote_interrupt): New function.
	(init_remote_ops): Install remote_interrupt.
	* target.c (target_interrupt): New function.
	* target.h (struct target_ops) <to_interrupt>: New field.
	(target_interrupt): New declaration.
	* windows-nat.c (windows_stop): Rename to ...
	(windows_interrupt): ... this.
	* target-delegates.c: Regenerate.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix signal-while-stepping-over-bp-other-thread.exp on targets always in non-stop
@ 2015-08-07 21:49 sergiodj+buildbot
  2015-08-09 17:20 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-07 21:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d55007b58352c0b5fd2817e003b6dcf4e3ee4c07 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: d55007b58352c0b5fd2817e003b6dcf4e3ee4c07

Fix signal-while-stepping-over-bp-other-thread.exp on targets always in non-stop

With "maint set target-non-stop on" we get:

 -PASS: gdb.threads/signal-while-stepping-over-bp-other-thread.exp: step
 +FAIL: gdb.threads/signal-while-stepping-over-bp-other-thread.exp: step

The issue is simply that switch_back_to_stepped_thread is not used in
non-stop mode, thus infrun doesn't output the expected "switching back
to stepped thread" log.

gdb/testsuite/ChangeLog:
2015-08-07  Pedro Alves  <palves@redhat.com>

	* signal-while-stepping-over-bp-other-thread.exp: Expect "restart
	threads" as alternative to "switching back to stepped thread".


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Implement all-stop on top of a target running non-stop mode
@ 2015-08-07 21:15 sergiodj+buildbot
  2015-08-09 16:05 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-07 21:15 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fbea99ea8a062e5cd96e2d88336984ed3adc93d4 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: fbea99ea8a062e5cd96e2d88336984ed3adc93d4

Implement all-stop on top of a target running non-stop mode

This finally implements user-visible all-stop mode running with the
target_ops backend always in non-stop mode.  This is a stepping stone
towards finer-grained control of threads, being able to do interesting
things like thread groups, associating groups with breakpoints, etc.
>From the user's perspective, all-stop mode is really just a special
case of being able to stop and resume specific sets of threads, so it
makes sense to do this step first.

With this, even in all-stop, the target is no longer in charge of
stopping all threads before reporting an event to the core -- the core
takes care of it when it sees fit.  For example, when "next"- or
"step"-ing, we can avoid stopping and resuming all threads at each
internal single-step, and instead only stop all threads when we're
about to present the stop to the user.

The implementation is almost straight forward, as the heavy lifting
has been done already in previous patches.  Basically, we replace
checks for "set non-stop on/off" (the non_stop global), with calls to
a new target_is_non_stop_p function.  In a few places, if "set
non-stop off", we stop all threads explicitly, and in a few other
places we resume all threads explicitly, making use of existing
methods that were added for teaching non-stop to step over breakpoints
without displaced stepping.

This adds a new "maint set target-non-stop on/off/auto" knob that
allows both disabling the feature if we find problems, and
force-enable it for development (useful when teaching a target about
this.  The default is "auto", which means the feature is enabled if a
new target method says it should be enabled.  The patch implements the
method in linux-nat.c, just for illustration, because it still returns
false.  We'll need a few follow up fixes before turning it on by
default.  This is a separate target method from indicating regular
non-stop support, because e.g., while e.g., native linux-nat.c is
close to regression free with all-stop-non-stop (with following
patches will fixing the remaining regressions), remote.c+gdbserver
will still need more fixing, even though it supports "set non-stop
on".

Tested on x86_64 Fedora 20, native, with and without "set displaced
off", and with and without "maint set target-non-stop on"; and also
against gdbserver.

gdb/ChangeLog:
2015-08-07  Pedro Alves  <palves@redhat.com>

	* NEWS: Mention "maint set/show target-non-stop".
	* breakpoint.c (update_global_location_list): Check
	target_is_non_stop_p instead of non_stop.
	* infcmd.c (attach_command_post_wait, attach_command): Likewise.
	* infrun.c (show_can_use_displaced_stepping)
	(can_use_displaced_stepping_p, start_step_over_inferior):
	Likewise.
	(internal_resume_ptid): New function.
	(resume): Use it.
	(proceed): Check target_is_non_stop_p instead of non_stop.  If in
	all-stop mode but the target is always in non-stop mode, start all
	the other threads that are implicitly resumed too.
	(for_each_just_stopped_thread, fetch_inferior_event)
	(adjust_pc_after_break, stop_all_threads): Check
	target_is_non_stop_p instead of non_stop.
	(handle_inferior_event): Likewise.  Handle detach-fork in all-stop
	with the target always in non-stop mode.
	(handle_signal_stop) <random signal>: Check target_is_non_stop_p
	instead of non_stop.
	(switch_back_to_stepped_thread): Check target_is_non_stop_p
	instead of non_stop.
	(keep_going_stepped_thread): Use internal_resume_ptid.
	(stop_waiting): If in all-stop mode, and the target is in non-stop
	mode, stop all threads.
	(keep_going_pass): Likewise, when starting a new in-line step-over
	sequence.
	* linux-nat.c (get_pending_status, select_event_lwp)
	(linux_nat_filter_event, linux_nat_wait_1, linux_nat_wait): Check
	target_is_non_stop_p instead of non_stop.
	(linux_nat_always_non_stop_p): New function.
	(linux_nat_stop): Check target_is_non_stop_p instead of non_stop.
	(linux_nat_add_target): Install linux_nat_always_non_stop_p.
	* target-delegates.c: Regenerate.
	* target.c (target_is_non_stop_p): New function.
	(target_non_stop_enabled, target_non_stop_enabled_1): New globals.
	(maint_set_target_non_stop_command)
	(maint_show_target_non_stop_command): New functions.
	(_initilize_target): Install "maint set/show target-non-stop"
	commands.
	* target.h (struct target_ops) <to_always_non_stop_p>: New field.
	(target_non_stop_enabled): New declaration.
	(target_is_non_stop_p): New declaration.

gdb/doc/ChangeLog:
2015-08-07  Pedro Alves  <palves@redhat.com>

	* gdb.texinfo (Maintenance Commands): Document "maint set/show
	target-non-stop".


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Teach non-stop to do in-line step-overs (stop all, step, restart)
@ 2015-08-07 21:07 sergiodj+buildbot
  2015-08-09 14:55 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-07 21:07 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 372316f12874a30c62e6d71079ca3b86c786fb7e ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 372316f12874a30c62e6d71079ca3b86c786fb7e

Teach non-stop to do in-line step-overs (stop all, step, restart)

That is, step past breakpoints by:

 - pausing all threads
 - removing breakpoint at PC
 - single-step
 - reinsert breakpoint
 - restart threads

similarly to all-stop (with displaced stepping disabled).  This allows
non-stop to work on targets/architectures without displaced stepping
support.  That is, it makes displaced stepping an optimization instead
of a requirement.  For example, in principle, all GNU/Linux ports
support non-stop mode at the target_ops level, but not all
corresponding gdbarch's implement displaced stepping.  This should
make non-stop work for all (albeit, not as efficiently).  And then
there are scenarios where even if the architecture supports displaced
stepping, we can't use it, because we e.g., don't find a usable
address to use as displaced step scratch pad.  It should also fix
stepping past watchpoints on targets that have non-continuable
watchpoints in non-stop mode (e.g., PPC, untested).  Running the
instruction out of line in the displaced stepping scratch pad doesn't
help that case, as the copied instruction reads/writes the same
watched memory...  We can fix that too by teaching GDB to only remove
the watchpoint from the thread that we want to move past the
watchpoint (currently, removing a watchpoint always removes it from
all threads), but again, that can be considered an optimization; not
all targets would support it.

For those familiar with the gdb and gdbserver Linux target_ops
backends, the implementation should look similar, except it is done on
the core side.  When we pause threads, we may find they stop with an
interesting event that should be handled later when the thread is
re-resumed, thus we store such events in the thread object, and mark
the event as pending.  We should only consume pending events if the
thread is indeed resumed, thus we add a new "resumed" flag to the
thread object.  At a later stage, we might add new target methods to
accelerate some of this, like "pause all threads", with corresponding
RSP packets, but we'd still need a fallback method for remote targets
that don't support such packets, so, again, that can be deferred as
optimization.

My _real_ motivation here is making it possible to reimplement
all-stop mode on top of the target always working on non-stop mode, so
that e.g., we can send RSP packets to a remote target even while the
target is running -- can't do that in the all-stop RSP variant, by
design).

Tested on x86_64 Fedora 20, with and without "set displaced off"
forced.  The latter forces the new code paths whenever GDB needs to
step past a breakpoint.

gdb/ChangeLog:
2015-08-07  Pedro Alves  <pedro@codesourcery.com>

	* breakpoint.c (breakpoints_should_be_inserted_now): If any thread
	has a pending status, return true.
	* gdbthread.h: Include target/waitstatus.h.
	(struct thread_suspend_state) <stop_reason, waitstatus_pending_p,
	stop_pc>: New fields.
	(struct thread_info) <resumed>: New field.
	(set_resumed): Declare.
	* infrun.c: Include "event-loop.h".
	(infrun_async_inferior_event_token, infrun_is_async): New globals.
	(infrun_async): New function.
	(clear_step_over_info): Add debug output.
	(displaced_step_in_progress_any_inferior): New function.
	(displaced_step_fixup): New returns int.
	(start_step_over): Handle in-line step-overs too.  Assert the
	thread is marked resumed.
	(resume_cleanups): Clear the thread's resumed flag.
	(resume): Set the thread's resumed flag.  Return early if the
	thread has a pending status.  Allow stepping a breakpoint with no
	signal.
	(proceed): Adjust to check 'resumed' instead of 'executing'.
	(clear_proceed_status_thread): If the thread has a pending status,
	and that status is a finished step, discard the pending status.
	(clear_proceed_status): Don't clear step_over_info here.
	(random_pending_event_thread, do_target_wait): New functions.
	(prepare_for_detach, wait_for_inferior, fetch_inferior_event): Use
	do_target_wait.
	(wait_one): New function.
	(THREAD_STOPPED_BY): New macro.
	(thread_stopped_by_watchpoint, thread_stopped_by_sw_breakpoint)
	(thread_stopped_by_hw_breakpoint): New functions.
	(switch_to_thread_cleanup, save_waitstatus, stop_all_threads): New
	functions.
	(handle_inferior_event): Also call set_resumed(false) on all
	threads implicitly stopped by the event.
	(restart_threads, resumed_thread_with_pending_status): New
	functions.
	(finish_step_over): If we were doing an in-line step-over before,
	and no longer are after trying to start a new step-over, restart
	all threads.  If we have multiple threads with pending events,
	save the current event and go through the event loop again.
	(handle_signal_stop): Return early if finish_step_over returns
	false.
	<random signal>: If we get a signal while stepping over a
	breakpoint in-line in non-stop mode, restart all threads.  Clear
	step_over_info before delivering the signal.
	(keep_going_stepped_thread): Use internal_error instead of
	gdb_assert.  Mark the thread as resumed.
	(keep_going_pass_signal): Assert the thread isn't already resumed.
	If some other thread is doing an in-line step-over, defer the
	resume.  If we just started a new in-line step-over, stop all
	threads.  Don't clear step_over_info.
	(infrun_async_inferior_event_handler): New function.
	(_initialize_infrun): Create async event handler with
	infrun_async_inferior_event_handler as callback.
	(infrun_async): New declaration.
	* target.c (target_async): New function.
	* target.h (target_async): Declare macro and readd as function
	declaration.
	* target/waitstatus.h (enum target_stop_reason)
	<TARGET_STOPPED_BY_SINGLE_STEP>: New value.
	* thread.c (new_thread): Clear the new waitstatus field.
	(set_resumed): New function.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Factor out code to re-resume stepped thread
@ 2015-08-07 20:23 sergiodj+buildbot
  2015-08-09 13:34 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-07 20:23 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2ac7589cfe1df06506adb133e99b2b89212c9a11 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 2ac7589cfe1df06506adb133e99b2b89212c9a11

Factor out code to re-resume stepped thread

Just a code refactor, no funcionality change intended.

gdb/ChangeLog:
2015-08-07  Pedro Alves  <palves@redhat.com>

	* infrun.c (keep_going_stepped_thread): New function, factored out
	from ...
	(switch_back_to_stepped_thread): ... here.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Add comments to currently_stepping and target_resume
@ 2015-08-07 19:58 sergiodj+buildbot
  2015-08-09 12:23 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-07 19:58 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8b0615634896718c982d367a01ec61120084d3fb ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 8b0615634896718c982d367a01ec61120084d3fb

Add comments to currently_stepping and target_resume

Clarify that currently_stepping works at a higher level than
target_resume.

gdb/ChangeLog:
2015-08-07  Pedro Alves  <palves@redhat.com>

	* infrun.c (currently_stepping): Extend intro comment.
	* target.h (target_resume): Extend intro comment.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Misc switch_back_to_stepped_thread cleanups
@ 2015-08-07 19:35 sergiodj+buildbot
  2015-08-09 11:13 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-07 19:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1afd5965eda86caed3af7f23fd1f8802831360b6 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 1afd5965eda86caed3af7f23fd1f8802831360b6

Misc switch_back_to_stepped_thread cleanups

Several misc cleanups that prepare the tail end of this function, the
part that actually re-resumes the stepped thread.

The most non-obvious would be the currently_stepping change, I guess.
That's because it isn't ever correct to pass step=1 to target_resume
on software single-step targets, and currently_stepping works at a
conceptual higher level, it returns step=true even on software step
targets.  It doesn't really matter on hardware step targets, as the
breakpoint will be hit immediately, but it's just wrong on software
step targets.  I tested it against my x86 software single-step branch,
and it indeed fixes failed assertions (that catch spurious
PTRACE_SINGLESTEP requests) there.

gdb/ChangeLog:
2015-08-07  Pedro Alves  <palves@redhat.com>

	* infrun.c (switch_back_to_stepped_thread): Use ecs->ptid instead
	of inferior_ptid.  If the stepped thread vanished, return 0
	instead of resuming here.  Use reset_ecs.  Print the prev_pc and
	the current stop_pc in log message.  Clear trap_expected if the
	thread advanced.  Don't pass currently_stepping to
	do_target_resume.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Use keep_going in proceed and start_step_over too
@ 2015-08-07 19:05 sergiodj+buildbot
  2015-08-09  9:58 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-07 19:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4d9d9d0423ed611fa6d620ca3aa088fc16a0d59e ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 4d9d9d0423ed611fa6d620ca3aa088fc16a0d59e

Use keep_going in proceed and start_step_over too

The main motivation of this patch is sharing more code between the
proceed (starting the inferior for the first time) and keep_going
(restarting the inferior after handling an event) paths and using the
step_over_chain queue now embedded in the thread_info object for
pending in-line step-overs too (instead of just for displaced
stepping).

So this commit:

 - splits out a new keep_going_pass_signal function out of keep_going
   that is just like keep_going except for the bits that clear the
   signal to pass if the signal is set to "handle nopass".

 - makes proceed use keep_going too.

 - Makes start_step_over use keep_going_pass_signal instead of lower
   level displaced stepping things.

One user visible change: if inserting breakpoints while trying to
proceed fails, we now get:

  (gdb) si
  Warning:
  Could not insert hardware watchpoint 7.
  Could not insert hardware breakpoints:
  You may have requested too many hardware breakpoints/watchpoints.

  Command aborted.
  (gdb)

while before we only saw warnings with no indication that the command
was cancelled:

  (gdb) si
  Warning:
  Could not insert hardware watchpoint 7.
  Could not insert hardware breakpoints:
  You may have requested too many hardware breakpoints/watchpoints.

  (gdb)

Tested on x86_64-linux-gnu, ppc64-linux-gnu and s390-linux-gnu.

gdb/ChangeLog:
2015-08-07  Pedro Alves  <palves@redhat.com>

	* gdbthread.h (struct thread_info) <prev_pc>: Extend comment.
	* infrun.c (struct execution_control_state): Move higher up in the
	file.
	(reset_ecs): New function.
	(start_step_over): Now returns int.  Rewrite to use
	keep_going_pass_signal instead of manually starting a displaced step.
	(resume): Don't call set_running here.  If displaced stepping
	can't start now, clear trap_expected.
	(find_thread_needs_step_over): Delete function.
	(proceed): Set up finish_thread_state_cleanup.  Call set_running.
	If the current thread needs a step over, push it in the step-over
	chain.  Don't set insert breakpoints nor call resume directly
	here.  Instead rewrite to use start_step_over and
	keep_going_pass_signal.
	(finish_step_over): New function.
	(handle_signal_stop): Call finish_step_over instead of
	start_step_over.
	(switch_back_to_stepped_thread): If the event thread needs another
	step-over do that first.  Use start_step_over.
	(keep_going_pass_signal): New function, factored out from ...
	(keep_going): ... here.
	(_initialize_infrun): Comment moved here.
	* thread.c (set_running_thread): New function.
	(set_running, finish_thread_state): Use set_running_thread.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Embed the pending step-over chain in thread_info objects
@ 2015-08-07 18:40 sergiodj+buildbot
  2015-08-09  5:11 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-07 18:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c2829269f5af8a860b54ceac3596610b1f51fee5 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: c2829269f5af8a860b54ceac3596610b1f51fee5

Embed the pending step-over chain in thread_info objects

In order to teach non-stop mode to do in-line step-overs (pause all
threads, remove breakpoint, single-step, reinsert breakpoint, restart
threads), we'll need to be able to queue in-line step over requests,
much like we queue displaced stepping (out-of-line) requests.
Actually, the queue should be the same -- threads wait for their turn
to step past something (breakpoint, watchpoint), doesn't matter what
technique we end up using when the step over actually starts.

I found that the queue management ends up simpler and more efficient
if embedded in the thread objects themselves.  This commit converts
the existing displaced stepping queue to that.  Later patches will
make the in-line step-overs code paths use it too.

gdb/ChangeLog:
2015-08-07  Pedro Alves  <palves@redhat.com>

	* gdbthread.h (struct thread_info) <step_over_prev,
	step_over_next>: New fields.
	(thread_step_over_chain_enqueue, thread_step_over_chain_remove)
	(thread_step_over_chain_next, thread_is_in_step_over_chain): New
	declarations.
	* infrun.c (struct displaced_step_request): Delete.
	(struct displaced_step_inferior_state) <step_request_queue>:
	Delete field.
	(displaced_step_prepare): Assert that trap_expected is set.  Use
	thread_step_over_chain_enqueue.  Split starting a new displaced
	step to ...
	(start_step_over): ... this new function.
	(resume): Assert the thread isn't waiting for a step over already.
	(proceed): Assert the thread isn't waiting for a step over
	already.
	(infrun_thread_stop_requested): Adjust to remove threads from the
	embedded step-over chain.
	(handle_inferior_event) <fork/vfork>: Call start_step_over after
	displaced_step_fixup.
	(handle_signal_stop): Call start_step_over after
	displaced_step_fixup.
	* infrun.h (step_over_queue_head): New declaration.
	* thread.c (step_over_chain_enqueue, step_over_chain_remove)
	(thread_step_over_chain_next, thread_is_in_step_over_chain)
	(thread_step_over_chain_enqueue)
	(thread_step_over_chain_remove): New functions.
	(delete_thread_1): Remove thread from the step-over chain.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
[parent not found: <33ebda9d6841e18d9ef18b94c3dcad7d0498ab3d@gdb-build>]
* [binutils-gdb] Make thread_still_needs_step_over consider stepping_over_watchpoint too
@ 2015-08-07 18:22 sergiodj+buildbot
  2015-08-08 23:10 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-07 18:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6c4cfb244b408f980be24ea2175bc58baf74a6f9 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 6c4cfb244b408f980be24ea2175bc58baf74a6f9

Make thread_still_needs_step_over consider stepping_over_watchpoint too

I noticed that even though keep_going knows to start a step over for a
watchpoint, thread_still_needs_step_over forgets it.

gdb/ChangeLog:
2015-08-07  Pedro Alves  <palves@redhat.com>

	* infrun.c (thread_still_needs_step_over): Rename to ...
	(thread_still_needs_step_over_bp): ... this.
	(enum step_over_what): New.
	(thread_still_needs_step_over): Reimplement.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] remote.c/all-stop: Implement TARGET_WAITKIND_NO_RESUMED and TARGET_WNOHANG
@ 2015-08-07 17:47 sergiodj+buildbot
  2015-08-08 21:56 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-07 17:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 567420d10895611e03d5ee65e6b24c16a69a6e99 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 567420d10895611e03d5ee65e6b24c16a69a6e99

remote.c/all-stop: Implement TARGET_WAITKIND_NO_RESUMED and TARGET_WNOHANG

Even though "target remote" supports target-async, the all-stop
target_wait implementation ignores TARGET_WNOHANG.  If the core
happens to poll for events and we've already read the stop reply out
of the serial/socket, remote_wait_as hangs forever instead of
returning an indication that there are no events to process.  This
can't happen currently, but later changes will trigger this.

gdb/ChangeLog:
2015-08-07  Pedro Alves  <palves@redhat.com>

	* remote.c (remote_wait_as): If not waiting for a stop reply,
	return TARGET_WAITKIND_NO_RESUMED.  If TARGET_WNOHANG is
	requested, don't block waiting forever.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Change adjust_pc_after_break's prototype
@ 2015-08-07 17:20 sergiodj+buildbot
  2015-08-08 20:47 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-07 17:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d8dd4d5fe6d5ab971b731df5f65025a0dbbdb912 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: d8dd4d5fe6d5ab971b731df5f65025a0dbbdb912

Change adjust_pc_after_break's prototype

Prepare to use it in contexts without an ecs handy.  Follow up patches
will make use of this.

gdb/ChangeLog:
2015-08-07  Pedro Alves  <pedro@codesourcery.com>

	* infrun.c (adjust_pc_after_break): Now takes thread_info and
	waitstatus pointers instead of an ecs.  Adjust.
	(handle_inferior_event): Adjust caller.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix and test "checkpoint" in non-stop mode
@ 2015-08-07 16:54 sergiodj+buildbot
  2015-08-08 19:38 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-07 16:54 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e1316e60d4d1fe406efc6e7536b2bdb43733e9d2 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: e1316e60d4d1fe406efc6e7536b2bdb43733e9d2

Fix and test "checkpoint" in non-stop mode

Letting a "checkpoint" run to exit with "set non-stop on" behaves
differently compared to the default all-stop mode ("set non-stop
off").

Currently, in non-stop mode:

  (gdb) start
  Temporary breakpoint 1 at 0x40086b: file src/gdb/testsuite/gdb.base/checkpoint.c, line 28.
  Starting program: build/gdb/testsuite/gdb.base/checkpoint

  Temporary breakpoint 1, main () at src/gdb/testsuite/gdb.base/checkpoint.c:28
  28        char *tmp = &linebuf[0];
  (gdb) checkpoint
  checkpoint 1: fork returned pid 24948.
  (gdb) c
  Continuing.
  Copy complete.
  Deleting copy.
  [Inferior 1 (process 24944) exited normally]
  [Switching to process 24948]
  (gdb) info threads
    Id   Target Id         Frame
    1    process 24948 "checkpoint" (running)

  No selected thread.  See `help thread'.
  (gdb) c
  The program is not being run.
  (gdb)

Two issues above:

 1. Thread 1 got stuck in "(running)" state (it isn't really running)

 2. While checkpoints try to preserve the illusion that the thread is
    still the same when the process exits, GDB switched to "No thread
    selected." instead of staying with thread 1 selected.

Problem #1 is caused by handle_inferior_event and normal_stop not
considering that when a
TARGET_WAITKIND_SIGNALLED/TARGET_WAITKIND_EXITED event is reported,
and the inferior is mourned, the target may still have execution.

Problem #2 is caused by the make_cleanup_restore_current_thread
cleanup installed by fetch_inferior_event not being able to find the
original thread 1's ptid in the thread list, thus not being able to
restore thread 1 as selected thread.  The fix is to make the cleanup
installed by make_cleanup_restore_current_thread aware of thread ptid
changes, by installing a thread_ptid_changed observer that adjusts the
cleanup's data.

After the patch, we get the same in all-stop and non-stop modes:

  (gdb) c
  Continuing.
  Copy complete.
  Deleting copy.
  [Inferior 1 (process 25109) exited normally]
  [Switching to process 25113]
  (gdb) info threads
    Id   Target Id         Frame
  * 1    process 25113 "checkpoint" main () at src/gdb/testsuite/gdb.base/checkpoint.c:28
  (gdb)

Turns out the whole checkpoints.exp file can run in non-stop mode
unmodified.  I thought of moving most of the test file's contents to a
procedure that can be called twice, once in non-stop mode and another
in all-stop mode.  But then, the test already takes close to 30
seconds to run on my machine, so I thought it'd be nicer to run
all-stop and non-stop mode in parallel.  Thus I added a new
checkpoint-ns.exp file that just appends "set non-stop on" to GDBFLAGS
and sources checkpoint.exp.

gdb/ChangeLog:
2015-08-07  Pedro Alves  <palves@redhat.com>

	* infrun.c (handle_inferior_event): If we get
	TARGET_WAITKIND_SIGNALLED or TARGET_WAITKIND_EXITED in non-stop
	mode, mark all threads of the exiting process as not-executing.
	(normal_stop): If we get TARGET_WAITKIND_SIGNALLED or
	TARGET_WAITKIND_EXITED in non-stop mode, finish all threads of the
	exiting process, if inferior_ptid still points at a process.
	* thread.c (struct current_thread_cleanup) <next>: New field.
	(current_thread_cleanup_chain): New global.
	(restore_current_thread_ptid_changed): New function.
	(restore_current_thread_cleanup_dtor): Remove the cleanup from the
	current_thread_cleanup_chain list.
	(make_cleanup_restore_current_thread): Add the cleanup data to the
	current_thread_cleanup_chain list.
	(_initialize_thread): Install restore_current_thread_ptid_changed
	as thread_ptid_changed observer.

gdb/testsuite/ChangeLog:
2015-08-07  Pedro Alves  <palves@redhat.com>

	* gdb.base/checkpoint-ns.exp: New file.
	* gdb.base/checkpoint.exp: Pass explicit "checkpoint.c" to
	standard_testfile.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] ignore invalid DOF provider sections
@ 2015-08-07 15:44 sergiodj+buildbot
  2015-08-08 18:27 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-07 15:44 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 47e9c225c1cb6fb1809218f5f546a70fc85f705c ***

Author: Joel Brobecker <brobecker@adacore.com>
Branch: master
Commit: 47e9c225c1cb6fb1809218f5f546a70fc85f705c

ignore invalid DOF provider sections
On x86-solaris 10, we noticed that starting a program would sometimes
cause the debugger to crash. For instance:

    % gdb a
    (gdb) break adainit
    Breakpoint 1 at 0x8051f03
    (gdb) run
    Starting program: /[...]/a
    [Thread debugging using libthread_db enabled]
    zsh: 24398 segmentation fault (core dumped)  /[...]/gdb a

The exception occurs in dtrace_process_dof_probe, while trying
to process each probe referenced by a DTRACE_DOF_SECT_TYPE_PROVIDER
DOF section from /lib/libc.so.1. For reference, the ELF section
in that shared library providing the DOF data has the following
characteristics:

    Idx Name          Size      VMA       LMA       File off  Algn
     14 .SUNW_dof     0000109d  000b4398  000b4398  000b4398  2**3
                      CONTENTS, ALLOC, LOAD, READONLY, DATA

The function dtrace_process_dof gets passed the contents of that
ELF section, which allows it to determine the location of the table
where all DOF sections are described. I dumped the contents of
each DOF section as seen by GDB, and it seemed to be plausible,
because the offset of each DOF section was pretty much equal to
the sum of the offset and size of the previous DOF section. Also,
the offset + sum of the last section corresponds to the size of
the .SUNW_dof section.

Things start to break down when processing one of the DOF sections
that has a type of DTRACE_DOF_SECT_TYPE_PROVIDER. It gets the contents
of this DOF section via:

        struct dtrace_dof_provider *provider = (struct dtrace_dof_provider *)
          DTRACE_DOF_PTR (dof, DOF_UINT (dof, section->dofs_offset));

Said more simply, the struct dtrace_dof_provider data is at
section->dofs_offset of the entire DOF contents. Given that
the contents of SECTION seemed to make sense, so far so good.

However, what SECTION tells us is that our DOF provider section
is 40 bytes long:

    (gdb) print *section
    $36 = {dofs_type = 15, dofs_align = 4, dofs_flags = 1,
           dofs_entsize = 0, dofs_offset = 3264, dofs_size = 40}
                                                 ^^^^^^^^^^^^^^

But on the other hand:

    (gdb) p sizeof (struct dtrace_dof_provider)
    $54 = 44

In other words GDB expected a bigger DOF section and when we try to
fetch the value of the last field of that DOF section (dofpv_prenoffs)...

    eoffsets_s = DTRACE_DOF_SECT (dof,
                                  DOF_UINT (dof, provider->dofpv_prenoffs));

... we end up reading data that actually belongs to another DOF
section, and therefore irrelevant. This in turn means that the value
of eofftab gets incorrectly set, since it depends on eoffsets_s:

    eofftab = DTRACE_DOF_PTR (dof, DOF_UINT (dof, eoffsets_s->dofs_offset));

This invalid address quickly catches up to us when we pass it to
dtrace_process_dof_probe shortly after, where we crash because
we try to subscript it:

    Program received signal SIGSEGV, Segmentation fault.
    0x08155bba in dtrace_process_dof_probe ([...]) at [...]/dtrace-probe.c:378
    378             = ((uint32_t *) eofftab)[...];

This patch fixes the issue by detecting provider DOF sections
that are smaller than expected, and discarding the DOF data.

gdb/ChangeLog:

        * dtrace-probe.c (dtrace_process_dof): Ignore the objfile's DOF
        data if a DTRACE_DOF_SECT_TYPE_PROVIDER section is found to be
        smaller than expected.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Sync config.sub and config.guess with GCC
@ 2015-08-07 15:10 sergiodj+buildbot
  2015-08-08 17:16 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-07 15:10 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5960642af99c6dc84b28e1bc69a617099b9dee97 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 5960642af99c6dc84b28e1bc69a617099b9dee97

Sync config.sub and config.guess with GCC
	Sync with GCC
	2015-07-28  Ben Elliston  <bje@gnu.org>

	* config.sub, config.guess: Import from upstream.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Remove CpuFMA4 support from CPU_ZNVER1_FLAGS.
@ 2015-08-07 14:44 sergiodj+buildbot
  2015-08-08 16:03 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-07 14:44 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 36aed29d3774a156c88ca7110f3c12605d861b9c ***

Author: Amit Pawar <Amit.Pawar@amd.com>
Branch: master
Commit: 36aed29d3774a156c88ca7110f3c12605d861b9c

Remove CpuFMA4 support from CPU_ZNVER1_FLAGS.
opcodes/

	* i386-gen.c: Remove CpuFMA4 from CPU_ZNVER1_FLAGS.
	* i386-init.h: Regenerated.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Properly merge hidden versioned symbol
@ 2015-08-07 12:17 sergiodj+buildbot
  2015-08-08 14:45 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-07 12:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6e33951edcbed1fd803beabcde2af3b252b92164 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 6e33951edcbed1fd803beabcde2af3b252b92164

Properly merge hidden versioned symbol
The hidden versioned symbol can only be merged with the versioned
symbol with the same symbol version.  _bfd_elf_merge_symbol should
check the symbol version before merging the new hidden versioned
symbol with the existing symbol.  _bfd_elf_link_hash_copy_indirect can't
copy any references to the hidden versioned symbol.   We need to
bind a symbol locally when linking executable if it is locally defined,
hidden versioned, not referenced by shared library and not exported.

bfd/

	PR ld/18720
	* elflink.c (_bfd_elf_merge_symbol): Add a parameter to indicate
	if the new symbol matches the existing one.  The new hidden
	versioned symbol matches the existing symbol if they have the
	same symbol version. Update the existing symbol only if they
	match.
	(_bfd_elf_add_default_symbol): Update call to
	_bfd_elf_merge_symbol.
	(_bfd_elf_link_assign_sym_version): Don't set the hidden field
	here.
	(elf_link_add_object_symbols): Override a definition only if the
	new symbol matches the existing one.
	(_bfd_elf_link_hash_copy_indirect): Don't copy any references to
	the hidden versioned symbol.
	(elf_link_output_extsym): Bind a symbol locally when linking
	executable if it is locally defined, hidden versioned, not
	referenced by shared library and not exported.  Turn on
	VERSYM_HIDDEN only if the hidden vesioned symbol is defined
	locally.

ld/testsuite/

	PR ld/18720
	* ld-elf/indirect.exp: Run tests for PR ld/18720.
	* ld-elf/pr18720.out: New file.
	* ld-elf/pr18720a.c: Likewise.
	* ld-elf/pr18720b.c: Likewise.
	* ld-elf/pr18720c.c: Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] gdb: Move get_frame_language from stack.c to frame.c.
@ 2015-08-07 11:34 sergiodj+buildbot
  2015-08-08 12:58 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-07 11:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 060967202b8def804d9afccad343d2eaef8a81cf ***

Author: Andrew Burgess <andrew.burgess@embecosm.com>
Branch: master
Commit: 060967202b8def804d9afccad343d2eaef8a81cf

gdb: Move get_frame_language from stack.c to frame.c.
The get_frame_language feels like it would be more at home in frame.c
rather than in stack.c, while the declaration, that is currently in
language.h can be moved into frame.h to match.

A couple of new includes are added, but otherwise no substantial change
here.

gdb/ChangeLog:

	* stack.c (get_frame_language): Moved ...
	* frame.c (get_frame_language): ... to here.
	* language.h (get_frame_language): Declaration moved to frame.h.
	* frame.h: Add language.h include, for language enum.
	(get_frame_language): Declaration moved from language.h.
	* language.c: Add frame.h include.
	* top.c: Add frame.h include.
	* symtab.h (struct obj_section): Declare.
	(struct cmd_list_element): Declare.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] gdb: get_frame_language now takes a frame parameter.
@ 2015-08-07 11:12 sergiodj+buildbot
  2015-08-08 11:26 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-07 11:12 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7ff38b1c898be5db053193f26d6a3a1d8a6074e8 ***

Author: Andrew Burgess <andrew.burgess@embecosm.com>
Branch: master
Commit: 7ff38b1c898be5db053193f26d6a3a1d8a6074e8

gdb: get_frame_language now takes a frame parameter.
As part of a drive to remove deprecated_safe_get_selected_frame, make
the get_frame_language function take a frame parameter.  Given the name
of the function this actually seems to make a lot of sense.

The task of fetching a suitable frame is then passed to the calling
functions.  For get_frame_language there are not many callers, these are
updated to get the selected frame in a suitable way.

gdb/ChangeLog:

	* language.c (show_language_command): Find selected frame before
	asking for the language of that frame.
	(set_language_command): Likewise.
	* language.h (get_frame_language): Add frame parameter.
	* stack.c (get_frame_language): Add frame parameter, assert
	parameter is not NULL, update comment and reindent.
	* top.c (check_frame_language_change): Pass the selected frame
	into get_frame_language.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] btrace: indicate speculative execution
@ 2015-08-07  8:58 sergiodj+buildbot
  2015-08-08  9:38 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-07  8:58 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT da8c46d2967b6325dcd2cc72eca26d807964c93c ***

Author: Markus Metzger <markus.t.metzger@intel.com>
Branch: master
Commit: da8c46d2967b6325dcd2cc72eca26d807964c93c

btrace: indicate speculative execution
Indicate speculatively executed instructions with a leading '?'.  We use the
space that is normally used for the PC prefix.  In the case where the
instruction at the current PC had been executed speculatively before, the PC
prefix will be partially overwritten resulting in "?> ".

As a side-effect, the /p modifier to omit the PC prefix in the "record
instruction-history" command now uses a 3-space PC prefix "   " in order to
have enough space for the speculative execution indication.

gdb/
	* btrace.c (btrace_compute_ftrace_bts): Clear insn flags.
	(pt_btrace_insn_flags): New.
	(ftrace_add_pt): Call pt_btrace_insn_flags.
	* btrace.h (btrace_insn_flag): New.
	(btrace_insn) <flags>: New.
	* record-btrace.c (btrace_insn_history): Print insn prefix.
	* NEWS: Announce it.

doc/
	* gdb.texinfo (Process Record and Replay): Document prefixing of
	speculatively executed instructions in the "record instruction-history"
	command.

testsuite/
	* gdb.btrace/instruction_history.exp: Update.
	* gdb.btrace/tsx.exp: New.
	* gdb.btrace/tsx.c: New.
	* lib/gdb.exp (skip_tsx_tests, skip_btrace_pt_tests): New.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] configure: check for perf_event.h version
@ 2015-08-07  8:34 sergiodj+buildbot
  2015-08-08  4:19 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-07  8:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5599c404621b2d8ac021c1427aee6e8974572042 ***

Author: Markus Metzger <markus.t.metzger@intel.com>
Branch: master
Commit: 5599c404621b2d8ac021c1427aee6e8974572042

configure: check for perf_event.h version
Intel(R) Processor Trace support requires a recent linux/perf_event.h header.

When GDB is built on an older system, Intel(R) Processor Trace will not be
available and there is no indication in the configure and build log as to
what went wrong.

Check for a compatible linux/perf_event.h at configure-time.

gdb/
	* configure.ac: Check for PERF_ATTR_SIZE_VER5 in linux/perf_event.h
	* configure: Regenerate.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Yaakov Selkowitz: fixes for in-tree libiconv
@ 2015-08-07  5:32 sergiodj+buildbot
  2015-08-07 23:22 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-07  5:32 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 016a3251631341bf4d8fe50966d2b70f8ea69e96 ***

Author: DJ Delorie <dj@redhat.com>
Branch: master
Commit: 016a3251631341bf4d8fe50966d2b70f8ea69e96

Yaakov Selkowitz: fixes for in-tree libiconv
        * Makefile.def (libiconv): Define bootstrap=true.
        Mark pdf/html/info as missing.
        (configure-gcc): Depend on all-libiconv.
        (all-gcc): Ditto.
        (configure-libcpp): Ditto.
        (all-libcpp): Ditto.
        (configure-intl): Ditto.
        (all-intl): Ditto.
        * Makefile.in: Regenerate.

binutils/
        * configure: Regenerate.

gdb/
        * Makefile.in (LIBICONV): Define.
        (CLIBS): Add LIBICONV.
        * acinclude.m4: Use config/iconv.m4 instead of custom AM_ICONV.
        * configure: Regenerate.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Bump timeouts for a couple gdb.reverse/*-precsave.exp tests
@ 2015-08-06 23:28 sergiodj+buildbot
  2015-08-07 22:09 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-06 23:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT de1c2c52237dd3e8d94df7b4a304ac9df75c8cf3 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: de1c2c52237dd3e8d94df7b4a304ac9df75c8cf3

Bump timeouts for a couple gdb.reverse/*-precsave.exp tests
The buildbot shows that PPC64 and x86_64 builders, both native and
extended-remote gdbserver frequently timeout these tests.
until-precsave.exp times out on my x86_64 occasionally as well.
Inspecting the logs, we see that if we waited some more, the tests
would pass.

Simply bump until-precsave.exp timeouts further, and apply the same
treatment to step-precsave.exp.

gdb/testsuite/ChangeLog:
2015-08-06  Pedro Alves <palves@redhat.com>

	* gdb.reverse/step-precsave.exp: Use with_timeout_factor to
	increase timeout.
	* gdb.reverse/until-precsave.exp: Bump timeouts.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix gdb.base/valgrind-infcall.exp with the native-extended-gdbserver board
@ 2015-08-06 22:52 sergiodj+buildbot
  2015-08-07 20:58 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-06 22:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 782e0bf46a84f57139f25c31c2ffc93508f07ef5 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 782e0bf46a84f57139f25c31c2ffc93508f07ef5

Fix gdb.base/valgrind-infcall.exp with the native-extended-gdbserver board
This test fails with --target_board=native-extended-gdbserver because
it misses the usual "disconnect":

 (gdb)  target remote | /usr/lib64/valgrind/../../bin/vgdb --pid=30454
 Already connected to a remote target.  Disconnect? (y or n) n
 Still connected.
 (gdb) FAIL: gdb.base/valgrind-infcall.exp: target remote for vgdb (got interactive prompt)

gdb/testsuite/ChangeLog:
2015-08-06  Pedro Alves  <palves@redhat.com>

	* gdb.base/valgrind-infcall.exp: Issue a "disconnect".


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Add casts for legitimate integer to enum conversions
@ 2015-08-06 21:34 sergiodj+buildbot
  2015-08-07 19:47 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-06 21:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT aead7601eb0ddc3fa51d43747bdad0e02abda342 ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: aead7601eb0ddc3fa51d43747bdad0e02abda342

Add casts for legitimate integer to enum conversions
This patch is mostly extracted from Pedro's C++ branch.  It adds explicit
casts from integer to enum types, where it is really the intention to do
so.  This could be because we are ...

 * iterating on enum values (we need to iterate on an equivalent integer)
 * converting from a value read from bytes (dwarf attribute, agent
 expression opcode) to the equivalent enum
 * reading the equivalent integer value from another language (Python/Guile)

An exception to that is the casts in regcache.c.  It seems to me like
struct regcache's register_status field could be a pointer to an array of
enum register_status.  Doing so would waste a bit of memory (4 bytes
used by the enum vs 1 byte used by the current signed char, for each
register).  If we switch to C++11 one day, we can define the underlying
type of an enum type, so we could have the best of both worlds.

gdb/ChangeLog:

	* arm-tdep.c (set_fp_model_sfunc): Add cast from integer to enum.
	(arm_set_abi): Likewise.
	* ax-general.c (ax_print): Likewise.
	* c-exp.y (exp : string_exp): Likewise.
	* compile/compile-loc2c.c (compute_stack_depth_worker): Likewise.
	(do_compile_dwarf_expr_to_c): Likewise.
	* cp-name-parser.y (demangler_special : DEMANGLER_SPECIAL start):
	Likewise.
	* dwarf2expr.c (execute_stack_op): Likewise.
	* dwarf2loc.c (dwarf2_compile_expr_to_ax): Likewise.
	(disassemble_dwarf_expression): Likewise.
	* dwarf2read.c (dwarf2_add_member_fn): Likewise.
	(read_array_order): Likewise.
	(abbrev_table_read_table): Likewise.
	(read_attribute_value): Likewise.
	(skip_unknown_opcode): Likewise.
	(dwarf_decode_macro_bytes): Likewise.
	(dwarf_decode_macros): Likewise.
	* eval.c (value_f90_subarray): Likewise.
	* guile/scm-param.c (gdbscm_make_parameter): Likewise.
	* i386-linux-tdep.c (i386_canonicalize_syscall): Likewise.
	* infrun.c (handle_command): Likewise.
	* memory-map.c (memory_map_start_memory): Likewise.
	* osabi.c (set_osabi): Likewise.
	* parse.c (operator_length_standard): Likewise.
	* ppc-linux-tdep.c (ppc_canonicalize_syscall): Likewise, and use
	single return point.
	* python/py-frame.c (gdbpy_frame_stop_reason_string): Likewise.
	* python/py-symbol.c (gdbpy_lookup_symbol): Likewise.
	(gdbpy_lookup_global_symbol): Likewise.
	* record-full.c (record_full_restore): Likewise.
	* regcache.c (regcache_register_status): Likewise.
	(regcache_raw_read): Likewise.
	(regcache_cooked_read): Likewise.
	* rs6000-tdep.c (powerpc_set_vector_abi): Likewise.
	* symtab.c (initialize_ordinary_address_classes): Likewise.
	* target-debug.h (target_debug_print_signals): Likewise.
	* utils.c (do_restore_current_language): Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] gdbserver: no point in hiding the regcache type nowadays
@ 2015-08-06 18:16 sergiodj+buildbot
  2015-08-07 17:23 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-06 18:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a44892be35506471a53e5bc8c2def4ffccf451f9 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: a44892be35506471a53e5bc8c2def4ffccf451f9

gdbserver: no point in hiding the regcache type nowadays
The regcache used to be hidden inside inferiors.c, but since the
tracepoints support that it's a first class object.  This also fixes a
few implicit pointer conversion errors in C++ mode, caused by a few
places missing the explicit cast.

gdb/gdbserver/ChangeLog:
2015-08-06  Pedro Alves  <palves@redhat.com>

	* gdbthread.h (struct regcache): Forward declare.
	(struct thread_info) <regcache_data>: Now a struct regcache
	pointer.
	* inferiors.c (inferior_regcache_data)
	(set_inferior_regcache_data): Now work with struct regcache
	pointers.
	* inferiors.h (struct regcache): Forward declare.
	(inferior_regcache_data, set_inferior_regcache_data): Now work
	with struct regcache pointers.
	* regcache.c (get_thread_regcache, regcache_invalidate_thread)
	(free_register_cache_thread): Remove struct regcache pointer
	casts.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] PR python/17136
@ 2015-08-06 17:22 sergiodj+buildbot
  2015-08-07 14:52 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-06 17:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ca0a5f0bd33d0aa17a5cf518e41e47ddfde486ad ***

Author: Clem Dickey <clemd@acm.org>
Branch: master
Commit: ca0a5f0bd33d0aa17a5cf518e41e47ddfde486ad

PR python/17136
gdb/ChangeLog:

	* python/lib/gdb/command/type_printers.py (InfoTypePrinter): Fix typo.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] gdbserver: fix silent error exit
@ 2015-08-06 16:55 sergiodj+buildbot
  2015-08-07 13:43 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-06 16:55 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 608a1e46394e9df951968c9112fbec3065da5fba ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 608a1e46394e9df951968c9112fbec3065da5fba

gdbserver: fix silent error exit
Running gdb.threads/process-dies-while-handling-bp.exp against
gdbserver sometimes FAILs because GDBserver drops the connection, but
the logs leave no clue on what the reason could be.  Running manually
a few times, I saw the same:

 $  ./gdbserver/gdbserver --multi :9999 testsuite/gdb.threads/process-dies-while-handling-bp
 Process testsuite/gdb.threads/process-dies-while-handling-bp created; pid = 12766
 Listening on port 9999
 Remote debugging from host 127.0.0.1
 Listening on port 9999

 Child exited with status 0

 Child exited with status 0

What happened is that an exception escaped and gdbserver reopened the
connection, which led to that second "Listening on port 9999" output.

The error was a failure to access registers from a now-dead thread.
The exception probably shouldn't have escaped here, but meanwhile,
this at least makes the issue less mysterious.

Tested on x86_64 Fedora 20.

gdb/gdbserver/ChangeLog:
2015-08-06  Pedro Alves  <palves@redhat.com>

	* server.c (captured_main): On error, print the exception message
	to stderr, and if run_once is set, throw a quit.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Change type of struct complaints::series
@ 2015-08-06 16:28 sergiodj+buildbot
  2015-08-07 12:10 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-06 16:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 05d999b0896ab6ccd4ce23a715765484c60a967d ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: 05d999b0896ab6ccd4ce23a715765484c60a967d

Change type of struct complaints::series
Found while processing the C++ enum changes.  It seems like series
should be of type enum complaint_series, instead of adding a cast.

Redundant and out of date comments are also removed.

gdb/ChangeLog:

	* complaints.c (enum complaint_series): Add newlines and remove
	out of date comment.
	(struct complaints) <series>: Change type to enum
	complaint_series and remove out of date comment.
	(symfile_complaint_hook): Use equivalent enum value
	ISOLATED_MESSAGE instead of 0.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] gdbserver: move_out_of_jump_pad_callback misses switching current thread
@ 2015-08-06 15:39 sergiodj+buildbot
  2015-08-07 10:05 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-06 15:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f0ce0d3a331129309a46a6a9ac85fce35acae72b ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: f0ce0d3a331129309a46a6a9ac85fce35acae72b

gdbserver: move_out_of_jump_pad_callback misses switching current thread
While hacking on the fix for PR threads/18600 (Threads left stopped
after fork+thread spawn), I once saw its test (fork-plus-threads.exp)
FAIL against gdbserver because move_out_of_jump_pad_callback has a
gdb_breakpoint_here call, and the caller isn't making sure the current
thread points to the right thread.  In the case I saw, the current
thread pointed to the wrong process, so gdb_breakpoint_here returned
the wrong answer.  Unfortunately I didn't save logs.  Still, seems
obvious enough and it should fix a potential occasional racy FAIL.

Tested on x86_64 Fedora 20.

gdb/gdbserver/ChangeLog:
2015-08-06  Pedro Alves  <palves@redhat.com>

	* linux-low.c (move_out_of_jump_pad_callback): Temporarily switch
	the current thread.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix gdbserver --debug issues caught by Valgrind
@ 2015-08-06 15:14 sergiodj+buildbot
  2015-08-07  9:15 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-06 15:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bf47e2482d3e88580ba5a22db48bc773fa8ced3f ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: bf47e2482d3e88580ba5a22db48bc773fa8ced3f

Fix gdbserver --debug issues caught by Valgrind
Running gdbserver --debug under Valgrind shows:

 ==4803== Invalid read of size 4
 ==4803==    at 0x432B62: linux_write_memory (linux-low.c:5320)
 ==4803==    by 0x4143F7: write_inferior_memory (target.c:83)
 ==4803==    by 0x415895: remove_memory_breakpoint (mem-break.c:362)
 ==4803==    by 0x432EF5: linux_remove_point (linux-low.c:5460)
 ==4803==    by 0x416319: delete_raw_breakpoint (mem-break.c:802)
 ==4803==    by 0x4163F3: release_breakpoint (mem-break.c:842)
 ==4803==    by 0x416477: delete_breakpoint_1 (mem-break.c:869)
 ==4803==    by 0x4164EF: delete_breakpoint (mem-break.c:891)
 ==4803==    by 0x416843: delete_gdb_breakpoint_1 (mem-break.c:1069)
 ==4803==    by 0x4168D8: delete_gdb_breakpoint (mem-break.c:1098)
 ==4803==    by 0x4134E3: process_serial_event (server.c:4051)
 ==4803==    by 0x4138E4: handle_serial_event (server.c:4196)
 ==4803==  Address 0x4c6b930 is 0 bytes inside a block of size 1 alloc'd
 ==4803==    at 0x4A0645D: malloc (in /usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so)
 ==4803==    by 0x4240C6: xmalloc (common-utils.c:43)
 ==4803==    by 0x41439C: write_inferior_memory (target.c:80)
 ==4803==    by 0x415895: remove_memory_breakpoint (mem-break.c:362)
 ==4803==    by 0x432EF5: linux_remove_point (linux-low.c:5460)
 ==4803==    by 0x416319: delete_raw_breakpoint (mem-break.c:802)
 ==4803==    by 0x4163F3: release_breakpoint (mem-break.c:842)
 ==4803==    by 0x416477: delete_breakpoint_1 (mem-break.c:869)
 ==4803==    by 0x4164EF: delete_breakpoint (mem-break.c:891)
 ==4803==    by 0x416843: delete_gdb_breakpoint_1 (mem-break.c:1069)
 ==4803==    by 0x4168D8: delete_gdb_breakpoint (mem-break.c:1098)
 ==4803==    by 0x4134E3: process_serial_event (server.c:4051)
 ==4803==

And:

 ==7272== Conditional jump or move depends on uninitialised value(s)
 ==7272==    at 0x3615E48361: vfprintf (vfprintf.c:1634)
 ==7272==    by 0x414E89: debug_vprintf (debug.c:60)
 ==7272==    by 0x42800A: debug_printf (common-debug.c:35)
 ==7272==    by 0x43937B: my_waitpid (linux-waitpid.c:149)
 ==7272==    by 0x42D740: linux_wait_for_event_filtered (linux-low.c:2441)
 ==7272==    by 0x42DADA: linux_wait_for_event (linux-low.c:2552)
 ==7272==    by 0x42E165: linux_wait_1 (linux-low.c:2860)
 ==7272==    by 0x42F5D8: linux_wait (linux-low.c:3453)
 ==7272==    by 0x4144A4: mywait (target.c:107)
 ==7272==    by 0x413969: handle_target_event (server.c:4214)
 ==7272==    by 0x41A1A6: handle_file_event (event-loop.c:429)
 ==7272==    by 0x41996D: process_event (event-loop.c:184)

gdb/ChangeLog:
2015-08-06  Pedro Alves  <palves@redhat.com>

	* nat/linux-waitpid.c (my_waitpid): Only print *status if waitpid
	returned > 0.

gdb/gdbserver/ChangeLog:
2015-08-06  Pedro Alves  <palves@redhat.com>

	* linux-low.c (linux_write_memory): Rewrite debug output to avoid
	reading beyond the passed in buffer length.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Revert "test slowdown"
@ 2015-08-06 14:26 sergiodj+buildbot
  2015-08-07  5:44 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-06 14:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f6a9d9c7db9b6b58e6915869c1bd7c83d96d31ee ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: f6a9d9c7db9b6b58e6915869c1bd7c83d96d31ee

Revert "test slowdown"
That was pushed by mistake.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Linux gdbserver confused when event randomization picks process exit event
@ 2015-08-06 10:08 sergiodj+buildbot
  2015-08-06 13:21 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-06 10:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 00db26facc14ac830adef704bba9b24d0d366ddf ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 00db26facc14ac830adef704bba9b24d0d366ddf

Linux gdbserver confused when event randomization picks process exit event
The tail end of linux_wait_1 isn't expecting that the select_event_lwp
machinery can pick a whole-process exit event to report to GDB.  When
that happens, both gdb and gdbserver end up quite confused:

 ...
 (gdb)
 [Thread 24971.24971] #1 stopped.
 0x0000003615a011f0 in ?? ()
 c&
 Continuing.
 (gdb) [New Thread 24971.24981]
 [New Thread 24983.24983]
 [New Thread 24971.24982]

 [Thread 24983.24983] #3 stopped.
 0x0000003615ebc7cc in __libc_fork () at ../nptl/sysdeps/unix/sysv/linux/fork.c:130
 130       pid = ARCH_FORK ();
 [New Thread 24984.24984]
 Error in re-setting breakpoint -16: PC register is not available
 Error in re-setting breakpoint -17: PC register is not available
 Error in re-setting breakpoint -18: PC register is not available
 Error in re-setting breakpoint -19: PC register is not available
 Error in re-setting breakpoint -24: PC register is not available
 Error in re-setting breakpoint -25: PC register is not available
 Error in re-setting breakpoint -26: PC register is not available
 Error in re-setting breakpoint -27: PC register is not available
 Error in re-setting breakpoint -28: PC register is not available
 Error in re-setting breakpoint -29: PC register is not available
 Error in re-setting breakpoint -30: PC register is not available
 PC register is not available
 (gdb)

gdb/gdbserver/ChangeLog:
2015-08-06  Pedro Alves  <palves@redhat.com>

	* linux-low.c (add_lwp): Set waitstatus to TARGET_WAITKIND_IGNORE.
	(linux_thread_alive): Use lwp_is_marked_dead.
	(extended_event_reported): Delete.
	(linux_wait_1): Check if waitstatus is TARGET_WAITKIND_IGNORE
	instead of extended_event_reported.
	(mark_lwp_dead): Don't set the 'dead' flag.  Store the waitstatus
	as well.
	(lwp_is_marked_dead): New function.
	(lwp_running): Use lwp_is_marked_dead.
	* linux-low.h: Delete 'dead' field, and update 'waitstatus's
	comment.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] stepping is disturbed by setjmp/longjmp | try/catch in other threads
@ 2015-08-05 19:19 sergiodj+buildbot
  2015-08-05 21:14 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-05 19:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0a39bb3218ec528236da4953a97d07f0da9313ce ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 0a39bb3218ec528236da4953a97d07f0da9313ce

stepping is disturbed by setjmp/longjmp | try/catch in other threads
At https://sourceware.org/ml/gdb-patches/2015-08/msg00097.html, Joel
observed that trying to next/step a program on GNU/Linux sometimes
results in the following failed assertion:

	% gdb -q .obj/gprof/main
    (gdb) start
    (gdb) n
    (gdb) step
    [...]/infrun.c:2391: internal-error:
    resume: Assertion `sig != GDB_SIGNAL_0' failed.

What happened is that, during the "next" operation, GDB hit a
longjmp/exception/step-resume breakpoint but failed to see that this
breakpoint was set for a different thread than the one being stepped.

Joel's detailed analysis follows:

More precisely, at the end of the "start" command, we are stopped at
the start of function Main in main.adb; there are 4 threads in total,
and we are in the main thread (which is thread 1):

    (gdb) info thread
      Id   Target Id         Frame
      4    Thread 0xb7a56ba0 (LWP 28379) 0xffffe410 in __kernel_vsyscall ()
      3    Thread 0xb7c5aba0 (LWP 28378) 0xffffe410 in __kernel_vsyscall ()
      2    Thread 0xb7e5eba0 (LWP 28377) 0xffffe410 in __kernel_vsyscall ()
    * 1    Thread 0xb7ea18c0 (LWP 28370) main () at /[...]/main.adb:57

All the logs below reference Thread ID/LWP, but it'll be easier to
talk about the threads by GDB thread number.  For instance, thread 1
is LWP 28370 while thread 3 is LWP 28378.  So, the explanations below
translate the LWPs into thread numbers.

Back to what happens while we are trying to "next' our program:
    (gdb) n
    infrun: clear_proceed_status_thread (Thread 0xb7a56ba0 (LWP 28379))
    infrun: clear_proceed_status_thread (Thread 0xb7c5aba0 (LWP 28378))
    infrun: clear_proceed_status_thread (Thread 0xb7e5eba0 (LWP 28377))
    infrun: clear_proceed_status_thread (Thread 0xb7ea18c0 (LWP 28370))
    infrun: proceed (addr=0xffffffff, signal=GDB_SIGNAL_DEFAULT)
    infrun: resume (step=1, signal=GDB_SIGNAL_0), trap_expected=0, current thread [Thread 0xb7ea18c0 (LWP 28370)] at 0x805451e
    infrun: target_wait (-1.0.0, status) =
    infrun:   28370.28370.0 [Thread 0xb7ea18c0 (LWP 28370)],
    infrun:   status->kind = stopped, signal = GDB_SIGNAL_TRAP
    infrun: TARGET_WAITKIND_STOPPED
    infrun: stop_pc = 0x8054523

We've resumed thread 1 (LWP 28370), and received in return a signal
that the same thread stopped slightly further.  It's still in the
range of instructions for the line of source we started the "next"
from, as evidenced by the following trace...

    infrun: stepping inside range [0x805451e-0x8054531]

... and thus, we decide to continue stepping the same thread:

    infrun: resume (step=1, signal=GDB_SIGNAL_0), trap_expected=0, current thread [Thread 0xb7ea18c0 (LWP 28370)] at 0x8054523
    infrun: prepare_to_wait

That's when we get an event from a different thread (thread 3)...

    infrun: target_wait (-1.0.0, status) =
    infrun:   28370.28378.0 [Thread 0xb7c5aba0 (LWP 28378)],
    infrun:   status->kind = stopped, signal = GDB_SIGNAL_TRAP
    infrun: TARGET_WAITKIND_STOPPED
    infrun: stop_pc = 0x80782d0
    infrun: context switch
    infrun: Switching context from Thread 0xb7ea18c0 (LWP 28370) to Thread 0xb7c5aba0 (LWP 28378)

... which we find to be at the address where we set a breakpoint on
"the unwinder debug hook" (namely "_Unwind_DebugHook").  But GDB fails
to notice that the breakpoint was inserted for thread 1 only, and so
decides to handle it as...

    infrun: BPSTAT_WHAT_SET_LONGJMP_RESUME

... and inserts a breakpoint at the corresponding resume address, as
evidenced by this the next log:

    infrun: exception resume at 80542a2

That breakpoint seems innocent right now, but will play a role fairly
quickly.  But for now, GDB has inserted the exception-resume
breakpoint, and needs to single-step thread 3 past the breakpoint it
just hit.  Thus, it temporarily disables the exception breakpoint, and
requests a step of that thread:

    infrun: skipping breakpoint: stepping past insn at: 0x80782d0
    infrun: skipping breakpoint: stepping past insn at: 0x80782d0
    infrun: skipping breakpoint: stepping past insn at: 0x80782d0
    infrun: resume (step=1, signal=GDB_SIGNAL_0), trap_expected=1, current thread [Thread 0xb7c5aba0 (LWP 28378)] at 0x80782d0
    infrun: prepare_to_wait

We then get a notification, still from thread 3, that it's now past
that breakpoint...

    infrun: prepare_to_wait
    infrun: target_wait (-1.0.0, status) =
    infrun:   28370.28378.0 [Thread 0xb7c5aba0 (LWP 28378)],
    infrun:   status->kind = stopped, signal = GDB_SIGNAL_TRAP
    infrun: TARGET_WAITKIND_STOPPED
    infrun: stop_pc = 0x8078424

... so we can resume what we were doing before, which is single-stepping
thread 1 until we get to a new line of code:

    infrun: switching back to stepped thread
    infrun: Switching context from Thread 0xb7c5aba0 (LWP 28378) to Thread 0xb7ea18c0 (LWP 28370)
    infrun: expected thread still hasn't advanced
    infrun: resume (step=1, signal=GDB_SIGNAL_0), trap_expected=0, current thread [Thread 0xb7ea18c0 (LWP 28370)] at 0x8054523

The "resume" log above shows that we're resuming thread 1 from where
we left off (0x8054523).  We get one more stop at 0x8054529, which is
still inside our stepping range so we go again.  That's when we get
the following event, from thread 3:

    infrun: prepare_to_wait
    infrun: target_wait (-1.0.0, status) =
    infrun:   28370.28378.0 [Thread 0xb7c5aba0 (LWP 28378)],
    infrun:   status->kind = stopped, signal = GDB_SIGNAL_TRAP
    infrun: TARGET_WAITKIND_STOPPED
    infrun: stop_pc = 0x80542a2

Now the stop_pc address is interesting, because it's the address of
"exception resume" breakpoint...

    infrun: context switch
    infrun: Switching context from Thread 0xb7ea18c0 (LWP 28370) to Thread 0xb7c5aba0 (LWP 28378)
    infrun: BPSTAT_WHAT_CLEAR_LONGJMP_RESUME

... and since that location is at a different line of code, this is
where it decides the "next" operation should stop:

    infrun: stop_waiting
    [Switching to Thread 0xb7c5aba0 (LWP 28378)]
    0x080542a2 in inte_tache_rt.ttache_rt (
        <_task>=0x80968ec <inte_tache_rt_inst.tache2>)
        at /[...]/inte_tache_rt.adb:54
    54            end loop;

However, what GDB should have noticed earlier that the exception
breakpoint we hit was for a different thread, thus should have
single-stepped that thread out of the breakpoint _without_ inserting
the exception-return breakpoint, and then resumed the single-stepping
of the initial thread (thread 1) until that thread stepped out of its
stepping range.

This is what this patch does, and after applying it, GDB now correctly
stops on the next line of code.

The patch adds a C++ test that exercises this, both for setjmp/longjmp
and exception breakpoints.  With an unpatched GDB it shows:

 (gdb) next
 [Switching to Thread 22445.22455]
 thread_try_catch (arg=0x0) at /home/pedro/gdb/mygit/build/../src/gdb/testsuite/gdb.threads/next-other-thr-longjmp.c:59
 59            catch (...)
 (gdb) FAIL: gdb.threads/next-other-thr-longjmp.exp: next to line 1
 next
 /home/pedro/gdb/mygit/build/../src/gdb/infrun.c:4865: internal-error: process_event_stop_test: Assertion `ecs->event_thread->control.exception_resume_breakpoint != NULL' fa
 iled.
 A problem internal to GDB has been detected,
 further debugging may prove unreliable.
 Quit this debugging session? (y or n) FAIL: gdb.threads/next-other-thr-longjmp.exp: next to line 2 (GDB internal error)
 Resyncing due to internal error.
 n

Tested on x86_64-linux, no regressions.

gdb/ChangeLog:
2015-08-05  Pedro Alves  <palves@redhat.com>
	    Joel Brobecker  <brobecker@adacore.com>

        * breakpoint.c (bpstat_what) <bp_longjmp, bp_longjmp_call_dummy>
	<bp_exception, bp_longjmp_resume, bp_exception_resume>: Handle the
	case where BS->STOP is not set.

gdb/testsuite/ChangeLog:
2015-08-05  Pedro Alves  <palves@redhat.com>

	* gdb.threads/next-while-other-thread-longjmps.c: New file.
	* gdb.threads/next-while-other-thread-longjmps.exp: New file.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Change the behaviour of the --only-keep-debug option to objcopy and strip so that the sh_link and sh_info fields in stripped section headers are preserved.
@ 2015-08-05 15:27 sergiodj+buildbot
  2015-08-05 19:10 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-05 15:27 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 63b9bbb7d7bcdcb6e0f59dd8da9615d80c537b8d ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: 63b9bbb7d7bcdcb6e0f59dd8da9615d80c537b8d

Change the behaviour of the --only-keep-debug option to objcopy and strip so that the sh_link and sh_info fields in stripped section headers are preserved.
bfd	* elf.c (_bfd_elf_copy_private_bfd_data): Copy the sh_link and
	sh_info fields of sections whose type has been changed to
	SHT_NOBITS.

bin	* doc/binutils.texi: Document that the --only-keep-debug option
	to strip and objcopy preserves the section headers of stripped
	sections.

tests	* binutils-all/objcopy.exp (keep_debug_symbols_and_check_links):
	New proc.  Checks that debug-info-only binaries retain the
	sh_link field in stripped sections.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Protect nat/gdb_thread_db.h against multiple inclusion.
@ 2015-08-05 14:43 sergiodj+buildbot
  2015-08-05 17:39 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-05 14:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 260439cb8ec21ffd75b240aadc55fd341c8c8dd4 ***

Author: Ulrich Weigand <ulrich.weigand@de.ibm.com>
Branch: master
Commit: 260439cb8ec21ffd75b240aadc55fd341c8c8dd4

Protect nat/gdb_thread_db.h against multiple inclusion.
Fixes a build error due to typedef redefinition with some compilers.

Also added missing copyright header.

gdb/
	* nat/gdb_thread_db.h: Add copyright header.
	Protect against multiple inclusion.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Move have_ptrace_getregset to linux-low.c
@ 2015-08-04 13:49 sergiodj+buildbot
  2015-08-04 22:35 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-04 13:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ded48a5ef34314f7af698b7ec7916b084c94b18d ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: ded48a5ef34314f7af698b7ec7916b084c94b18d

Move have_ptrace_getregset to linux-low.c
This patch moves variable have_ptrace_getregset from linux-x86-low.c
to linux-low.c, so that arm can use it too.

gdb/gdbserver:

2015-08-04  Yao Qi  <yao.qi@linaro.org>

	* linux-x86-low.c (have_ptrace_getregset): Move it to ...
	* linux-low.c: ... here.
	* linux-low.h (have_ptrace_getregset): Declare it.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] signal_command: Leftover cleanup chain regression
@ 2015-08-04 12:22 sergiodj+buildbot
  2015-08-04 20:12 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-04 12:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c6343a91d94e9516afe56dfe85e435922bd9ea04 ***

Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Branch: master
Commit: c6343a91d94e9516afe56dfe85e435922bd9ea04

signal_command: Leftover cleanup chain regression
gdb/ChangeLog
2015-08-04  Jan Kratochvil  <jan.kratochvil@redhat.com>

	* infcmd.c (signal_command): Call do_cleanups for args_chain.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix "FAIL: -Bsymbolic-functions" for cris-linux in ld
@ 2015-08-03 19:07 sergiodj+buildbot
  2015-08-04 10:46 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-03 19:07 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cb1c8103f13d413e05ca6e61e21b56bba3baae74 ***

Author: Hans-Peter Nilsson <hp@bitrange.com>
Branch: master
Commit: cb1c8103f13d413e05ca6e61e21b56bba3baae74

Fix "FAIL: -Bsymbolic-functions" for cris-linux in ld
	* elf32-cris.c (cris_elf_relocate_section)
	(elf_cris_finish_dynamic_symbol, cris_elf_check_relocs)
	(elf_cris_discard_excess_dso_dynamics): Use SYMBOLIC_BIND, not
	just h->symbolic, to check if a symbol should be bound
	symbolically.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Replace the block_found global with explicit data-flow
@ 2015-08-01  9:01 sergiodj+buildbot
  2015-08-03 16:42 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-08-01  9:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d12307c199dfdb9cad1ea79d2626224e705089a3 ***

Author: Pierre-Marie de Rodat <derodat@adacore.com>
Branch: master
Commit: d12307c199dfdb9cad1ea79d2626224e705089a3

Replace the block_found global with explicit data-flow
As Pedro suggested on gdb-patches@ (see
https://sourceware.org/ml/gdb-patches/2015-05/msg00714.html), this
change makes symbol lookup functions return a structure that includes
both the symbol found and the block in which it was found.  This makes
it possible to get rid of the block_found global variable and thus makes
block hunting explicit.

gdb/

	* ada-exp.y (write_object_renaming): Replace struct
	ada_symbol_info with struct block_symbol.  Update field
	references accordingly.
	(block_lookup, select_possible_type_sym): Likewise.
	(find_primitive_type): Likewise.  Also update call to
	ada_lookup_symbol to extract the symbol itself.
	(write_var_or_type, write_name_assoc): Likewise.
	* ada-lang.h (struct ada_symbol_info): Remove.
	(ada_lookup_symbol_list): Replace struct ada_symbol_info with
	struct block_symbol.
	(ada_lookup_encoded_symbol, user_select_syms): Likewise.
	(ada_lookup_symbol): Return struct block_symbol instead of a
	mere symbol.
	* ada-lang.c (defns_collected): Replace struct ada_symbol_info
	with struct block_symbol.
	(resolve_subexp, ada_resolve_function, sort_choices,
	user_select_syms, is_nonfunction, add_defn_to_vec,
	num_defns_collected, defns_collected,
	symbols_are_identical_enums, remove_extra_symbols,
	remove_irrelevant_renamings, add_lookup_symbol_list_worker,
	ada_lookup_symbol_list, ada_iterate_over_symbols,
	ada_lookup_encoded_symbol, get_var_value): Likewise.
	(ada_lookup_symbol): Return a block_symbol instead of a mere
	symbol.  Replace struct ada_symbol_info with struct
	block_symbol.
	(ada_lookup_symbol_nonlocal): Likewise.
	(standard_lookup): Make block passing explicit through
	lookup_symbol_in_language.
	* ada-tasks.c (get_tcb_types_info): Update the calls to
	lookup_symbol_in_language to extract the mere symbol out of the
	returned value.
	(ada_tasks_inferior_data_sniffer): Likewise.
	* ax-gdb.c (gen_static_field): Likewise for the call to
	lookup_symbol.
	(gen_maybe_namespace_elt): Deal with struct symbol_in_block from
	lookup functions.
	(gen_expr): Likewise.
	* c-exp.y: Likewise.  Remove uses of block_found.
	(lex_one_token, classify_inner_name, c_print_token): Likewise.
	(classify_name): Likewise.  Rename the "sym" local variable to
	"bsym".
	* c-valprint.c (print_unpacked_pointer): Likewise.
	* compile/compile-c-symbols.c (convert_symbol_sym): Promote the
	"sym" parameter from struct symbol * to struct block_symbol.
	Use it to remove uses of block_found.  Deal with struct
	symbol_in_block from lookup functions.
	(gcc_convert_symbol): Likewise.  Update the call to
	convert_symbol_sym.
	* compile/compile-object-load.c (compile_object_load): Deal with
	struct symbol_in_block from lookup functions.
	* cp-namespace.c (cp_lookup_nested_symbol_1,
	cp_lookup_nested_symbol, cp_lookup_bare_symbol,
	cp_search_static_and_baseclasses,
	cp_lookup_symbol_in_namespace, cp_lookup_symbol_via_imports,
	cp_lookup_symbol_imports_or_template,
	cp_lookup_symbol_via_all_imports, cp_lookup_symbol_namespace,
	lookup_namespace_scope, cp_lookup_nonlocal,
	find_symbol_in_baseclass): Return struct symbol_in_block instead
	of mere symbols and deal with struct symbol_in_block from lookup
	functions.
	* cp-support.c (inspect_type, replace_typedefs,
	cp_lookup_rtti_type): Deal with struct symbol_in_block from
	lookup functions.
	* cp-support.h (cp_lookup_symbol_nonlocal,
	cp_lookup_symbol_from_namespace,
	cp_lookup_symbol_imports_or_template, cp_lookup_nested_symbol):
	Return struct symbol_in_block instead of mere symbols.
	* d-exp.y (d_type_from_name, d_module_from_name, push_variable,
	push_module_name):
	Deal with struct symbol_in_block from lookup functions.  Remove
	uses of block_found.
	* eval.c (evaluate_subexp_standard): Update call to
	cp_lookup_symbol_namespace.
	* f-exp.y: Deal with struct symbol_in_block from lookup
	functions.  Remove uses of block_found.
	(yylex): Likewise.
	* gdbtypes.c (lookup_typename, lookup_struct, lookup_union,
	lookup_enum, lookup_template_type, check_typedef): Deal with
	struct symbol_in_block from lookup functions.
	* guile/scm-frame.c (gdbscm_frame_read_var): Likewise.
	* guile/scm-symbol.c (gdbscm_lookup_symbol): Likewise.
	(gdbscm_lookup_global_symbol): Likewise.
	* gnu-v3-abi.c (gnuv3_get_typeid_type): Likewise.
	* go-exp.y: Likewise.  Remove uses of block_found.
	(package_name_p, classify_packaged_name, classify_name):
	Likewise.
	* infrun.c (insert_exception_resume_breakpoint): Likewise.
	* jv-exp.y (push_variable): Likewise.
	* jv-lang.c (java_lookup_class, get_java_object_type): Likewise.
	* language.c (language_bool_type): Likewise.
	* language.h (struct language_defn): Update
	la_lookup_symbol_nonlocal to return a struct symbol_in_block
	rather than a mere symbol.
	* linespec.c (find_label_symbols): Deal with struct
	symbol_in_block from lookup functions.
	* m2-exp.y: Likewise.  Remove uses of block_found.
	(yylex): Likewise.
	* mi/mi-cmd-stack.c (list_args_or_locals): Likewise.
	* objc-lang.c (lookup_struct_typedef, find_imps): Likewise.
	* p-exp.y: Likewise.  Remove uses of block_found.
	(yylex): Likewise.
	* p-valprint.c (pascal_val_print): Likewise.
	* parse.c (write_dollar_variable): Likewise.  Remove uses of
	block_found.
	* parser-defs.h (struct symtoken): Turn the SYM field into a
	struct symbol_in_block.
	* printcmd.c (address_info): Deal with struct symbol_in_block
	from lookup functions.
	* python/py-frame.c (frapy_read_var): Likewise.
	* python/py-symbol.c (gdbpy_lookup_symbol,
	gdbpy_lookup_global_symbol): Likewise.
	* skip.c (skip_function_command): Likewise.
	* solib-darwin.c (darwin_lookup_lib_symbol): Return a struct
	symbol_in_block instead of a mere symbol.
	* solib-spu.c (spu_lookup_lib_symbol): Likewise.
	* solib-svr4.c (elf_lookup_lib_symbol): Likewise.
	* solib.c (solib_global_lookup): Likewise.
	* solist.h (solib_global_lookup): Likewise.
	(struct target_so_ops): Update lookup_lib_global_symbol to
	return a struct symbol_in_block rather than a mere symbol.
	* source.c (select_source_symtab): Deal with struct
	symbol_in_block from lookup functions.
	* stack.c (print_frame_args, iterate_over_block_arg_vars):
	Likewise.
	* symfile.c (set_initial_language): Likewise.
	* symtab.c (SYMBOL_LOOKUP_FAILED): Turn into a struct
	symbol_in_block.
	(SYMBOL_LOOKUP_FAILED_P): New predicate as a macro.
	(struct symbol_cache_slot): Turn the FOUND field into a struct
	symbol_in_block.
	(block_found): Remove.
	(eq_symbol_entry): Update to deal with struct symbol_in_block in
	cache slots.
	(symbol_cache_lookup): Return a struct symbol_in_block rather
	than a mere symbol.
	(symbol_cache_mark_found): Add a BLOCK parameter to fill
	appropriately the cache slots.  Update callers.
	(symbol_cache_dump): Update cache slots handling to the type
	change.
	(lookup_symbol_in_language, lookup_symbol, lookup_language_this,
	lookup_symbol_aux, lookup_local_symbol,
	lookup_symbol_in_objfile, lookup_global_symbol_from_objfile,
	lookup_symbol_in_objfile_symtabs,
	lookup_symbol_in_objfile_from_linkage_name,
	lookup_symbol_via_quick_fns, basic_lookup_symbol_nonlocal,
	lookup_symbol_in_static_block, lookup_static_symbol,
	lookup_global_symbol):
	Return a struct symbol_in_block rather than a mere symbol.  Deal
	with struct symbol_in_block from other lookup functions.  Remove
	uses of block_found.
	(lookup_symbol_in_block): Remove uses of block_found.
	(struct global_sym_lookup_data): Turn the RESULT field into a
	struct symbol_in_block.
	(lookup_symbol_global_iterator_cb): Update references to the
	RESULT field.
	(search_symbols): Deal with struct symbol_in_block from lookup
	functions.
	* symtab.h (struct symbol_in_block): New structure.
	(block_found): Remove.
	(lookup_symbol_in_language, lookup_symbol,
	basic_lookup_symbol_nonlocal, lookup_symbol_in_static_block,
	looku_static_symbol, lookup_global_symbol,
	lookup_symbol_in_block, lookup_language_this,
	lookup_global_symbol_from_objfile): Return a struct
	symbol_in_block rather than just a mere symbol.  Update comments
	to remove mentions of block_found.
	* valops.c (find_function_in_inferior,
	value_struct_elt_for_reference, value_maybe_namespace_elt,
	value_of_this):  Deal with struct symbol_in_block from lookup
	functions.
	* value.c (value_static_field, value_fn_field): Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Mostly trivial enum fixes
@ 2015-07-31 17:25 sergiodj+buildbot
  2015-08-03 11:50 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-07-31 17:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f486487f558686c05d4f4d91a75638b9da399044 ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: f486487f558686c05d4f4d91a75638b9da399044

Mostly trivial enum fixes
This is a patch I extracted from Pedro's C++ branch.  It contains the
most trivial enum fixes, where an integer type/value was used instead
of the appropriate enum type/value.  It fixes many C++ errors, since
in C++ you can't mix integers and enums implicitely.

Regardless of the C++ conversion, I think this is a good cleanup to make
use of the appropriate enum types.

Regression-tested on native x86_64.

gdb/ChangeLog:

	* aarch64-linux-nat.c (aarch64_linux_can_use_hw_breakpoint): Use enum
	type or value instead of integer.
	(aarch64_linux_insert_watchpoint): Likewise.
	(aarch64_linux_remove_watchpoint): Likewise.
	* ada-lang.c (ada_op_print_tab): Likewise.
	* amd64-linux-tdep.c (amd64_canonicalize_syscall): Likewise.
	(amd64_linux_syscall_record_common): Likewise.
	* arch-utils.c (target_byte_order_user): Likewise.
	(default_byte_order): Likewise.
	* arm-linux-nat.c (arm_linux_can_use_hw_breakpoint): Likewise.
	(arm_linux_get_hwbp_type): Likewise.
	(arm_linux_hw_watchpoint_initialize): Likewise.
	(arm_linux_insert_watchpoint): Likewise.
	* arm-linux-tdep.c (arm_canonicalize_syscall): Likewise.
	(arm_linux_syscall_record): Likewise.
	* breakpoint.c (update_watchpoint): Likewise.
	(breakpoint_here_p): Likewise.
	(bpstat_print): Likewise.
	(enable_breakpoint_disp): Likewise.
	* c-lang.c (c_op_print_tab): Likewise.
	* cli/cli-decode.c (add_info_alias): Likewise.
	* d-lang.c (d_op_print_tab): Likewise.
	* eval.c (evaluate_subexp_standard): Likewise.
	* f-exp.y (dot_ops): Likewise.
	(f77_keywords): Likewise.
	* f-lang.c (f_op_print_tab): Likewise.
	* go-lang.c (go_op_print_tab): Likewise.
	* guile/scm-breakpoint.c (gdbscm_make_breakpoint): Likewise.
	* guile/scm-cmd.c (gdbscm_make_command): Likewise.
	* guile/scm-param.c (gdbscm_make_parameter): Likewise.
	* guile/scm-pretty-print.c (gdbscm_apply_val_pretty_printer): Likewise.
	* guile/scm-string.c (struct scm_to_stringn_data): Likewise.
	(struct scm_from_stringn_data): Likewise.
	* i386-linux-tdep.c (i386_canonicalize_syscall): Likewise.
	* ia64-linux-nat.c (ia64_linux_insert_watchpoint): Likewise.
	(ia64_linux_remove_watchpoint): Likewise.
	(ia64_linux_can_use_hw_breakpoint): Likewise.
	* infrun.c (print_stop_event): Likewise.
	* jv-lang.c (java_op_print_tab): Likewise.
	* linux-nat.c (linux_proc_xfer_partial): Likewise.
	* linux-nat.h (struct lwp_info): Likewise.
	* linux-thread-db.c (enable_thread_event): Likewise.
	* m2-lang.c (m2_op_print_tab): Likewise.
	* mi/mi-cmd-stack.c (mi_cmd_stack_list_locals): Likewise.
	(mi_cmd_stack_list_variables): Likewise.
	* mi/mi-main.c (mi_cmd_trace_frame_collected): Likewise.
	* mi/mi-out.c (mi_table_begin): Likewise.
	(mi_table_header): Likewise.
	* mips-linux-nat.c (mips_linux_can_use_hw_breakpoint): Likewise.
	(mips_linux_insert_watchpoint): Likewise.
	(mips_linux_remove_watchpoint): Likewise.
	* nat/mips-linux-watch.c (mips_linux_watch_type_to_irw): Likewise.
	* nat/mips-linux-watch.h (struct mips_watchpoint): Likewise.
	(mips_linux_watch_type_to_irw): Likewise.
	* nto-procfs.c (procfs_can_use_hw_breakpoint): Likewise.
	(procfs_insert_hw_watchpoint): Likewise.
	(procfs_remove_hw_watchpoint): Likewise.
	(procfs_hw_watchpoint): Likewise.
	(procfs_can_use_hw_breakpoint): Likewise.
	(procfs_remove_hw_watchpoint): Likewise.
	(procfs_insert_hw_watchpoint): Likewise.
	* p-lang.c (pascal_op_print_tab): Likewise.
	* ppc-linux-nat.c (ppc_linux_can_use_hw_breakpoint): Likewise.
	* ppc-linux-tdep.c (ppu2spu_unwind_register): Likewise.
	* ppc-sysv-tdep.c (get_decimal_float_return_value): Likewise.
	* procfs.c (procfs_can_use_hw_breakpoint): Likewise.
	(procfs_insert_watchpoint): Likewise.
	(procfs_remove_watchpoint): Likewise.
	* psymtab.c (recursively_search_psymtabs): Likewise.
	* remote-m32r-sdi.c (m32r_can_use_hw_watchpoint): Likewise.
	(m32r_insert_watchpoint): Likewise.
	* remote-mips.c (mips_can_use_watchpoint): Likewise.
	(mips_insert_watchpoint): Likewise.
	(mips_remove_watchpoint): Likewise.
	* remote.c (watchpoint_to_Z_packet): Likewise.
	(remote_insert_watchpoint): Likewise.
	(remote_remove_watchpoint): Likewise.
	(remote_check_watch_resources): Likewise.
	* s390-linux-nat.c (s390_insert_watchpoint): Likewise.
	(s390_remove_watchpoint): Likewise.
	(s390_can_use_hw_breakpoint): Likewise.
	* s390-linux-tdep.c (s390_gdbarch_init): Likewise.
	* spu-linux-nat.c (spu_can_use_hw_breakpoint): Likewise.
	* target.h (struct target_ops): Likewise.
	* tilegx-tdep.c (tilegx_analyze_prologue): Likewise.
	* ui-out.c (struct ui_out_hdr): Likewise.
	(append_header_to_list): Likewise.
	(get_next_header): Likewise.
	(verify_field): Likewise.
	(ui_out_begin): Likewise.
	(ui_out_field_int): Likewise.
	(ui_out_field_fmt_int): Likewise.
	(ui_out_field_skip): Likewise.
	(ui_out_field_string): Likewise.
	(ui_out_field_fmt): Likewise.
	* varobj.c (new_variable): Likewise.
	* x86-nat.c (x86_insert_watchpoint): Likewise.
	(x86_remove_watchpoint): Likewise.
	(x86_can_use_hw_breakpoint): Likewise.
	* xtensa-tdep.h (struct gdbarch_tdep): Likewise.
	* inflow.c (enum gdb_has_a_terminal_flag_enum): Add name to
	previously anonymous enumeration type..
	* linux-record.h (enum gdb_syscall): Add gdb_sys_no_syscall
	value.
	* target-debug.h (target_debug_print_enum_target_hw_bp_type): New.
	(target_debug_print_enum_bptype): New.
	* target-delegates.c: Regenerate.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Don't use arm_regmap and arm_num_regs in arm_fill_gregset and arm_store_gregset
@ 2015-07-30 14:49 sergiodj+buildbot
  2015-08-02 15:32 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-07-30 14:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT deca266c89cf61c679f759a74bdf362960b0cc2c ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: deca266c89cf61c679f759a74bdf362960b0cc2c

Don't use arm_regmap and arm_num_regs in arm_fill_gregset and arm_store_gregset
In order to align with arm-linux-nat.c counterparts, we don't use
arm_num_regs and arm_regmap in functions arm_fill_gregset and
arm_store_gregset.  Instead, we use register numbers.  With this
patch applied, arm_fill_gregset and arm_store_gregset don't need
arm_num_regs and arm_regmap, and they will be moved to a separate
file shared for both arm and aarch64 in the following patch.

gdb/gdbserver:

2015-07-30  Yao Qi  <yao.qi@linaro.org>

	* linux-arm-low.c: Include arch/arm.h.
	(arm_fill_gregset): Don't use arm_num_regs and arm_regmap.
	(arm_store_gregset): Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Move ARM register numbers enum to arch/arm.h
@ 2015-07-30 14:17 sergiodj+buildbot
  2015-08-02 12:25 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-07-30 14:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ec74129274bf2fb65aac9381a19731c570f7be29 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: ec74129274bf2fb65aac9381a19731c570f7be29

Move ARM register numbers enum to arch/arm.h
This patch moves ARM register numbers enum to arch/arm.h, so that it
can used by GDBserver too.

This patch also creates a new directory gdb/arch in which arch-specific
or target-specific files are placed.

gdb:

2015-07-30  Yao Qi  <yao.qi@linaro.org>

	* arm-tdep.h (enum gdb_regnum): Move it to ...
	* arch/arm.h: ... here.  New file.
	* Makefile.in (HFILES_NO_SRCDIR): Add arch/arm.h.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Make gdb.base/call-ar-st.exp use gdb_test_stdio
@ 2015-07-29 16:38 sergiodj+buildbot
  2015-07-31 14:20 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-07-29 16:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 789c3a0cc3b1ace2d54ecc37fdbdb967f1810aaf ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 789c3a0cc3b1ace2d54ecc37fdbdb967f1810aaf

Make gdb.base/call-ar-st.exp use gdb_test_stdio
gdb/testsuite/ChangeLog:
2015-07-29  Pedro Alves  <palves@redhat.com>

	* gdb.base/call-ar-st.exp: Use gdb_test_stdio+multi_line instead
	of gdb_test_sequence.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Make gdb.base/dprintf.exp use gdb_test_stdio
@ 2015-07-29 15:25 sergiodj+buildbot
  2015-07-31 10:10 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-07-29 15:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8396d2cdf4b013b237bf8cca306bbec602bdbb72 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 8396d2cdf4b013b237bf8cca306bbec602bdbb72

Make gdb.base/dprintf.exp use gdb_test_stdio
This one needed a larger revamp.  The issue is that the "info
breakpoints" test at the bottom of the file is broken on targets that
can do both server-side dprintf, and inferior I/O, because then
neither the breakpoint numbers match nor the "already hit N times"
output.

Address that by making the test restart gdb from scratch when
switching between dprintf styles.  Test groups are factored into
procedures, and we now use with_test_prefix.  While we're changing
test messages, lowercase a few test messages, and then while at it,
modernize a couple things here and there.

gdb/testsuite/ChangeLog:
2015-07-29  Pedro Alves  <palves@redhat.com>

	* gdb.base/dprintf.exp: Use standard_testfile.  Change
	prepare_for_testing call.
	(srcfile): Don't set.
	(restart): New procedure.
	(test_dprintf): New procecure, use to continue over dprintfs.
	(test_call, test_agent): New procedures, tests moved here.
	Restart gdb and recreate dprintfs.  Adjust expected output.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Don't rely on inferior I/O in gdb.base/restore.exp
@ 2015-07-29 12:46 sergiodj+buildbot
  2015-07-30 23:14 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-07-29 12:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 12264a451d993a0a8635be82bed15618e0f4645f ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 12264a451d993a0a8635be82bed15618e0f4645f

Don't rely on inferior I/O in gdb.base/restore.exp
There seems to be no point in relying on stdio here.  Simply use
gdb_continue_to_end instead.

(not removing the printf calls, as the .c file is half generated.)

gdb/testsuite/ChangeLog:
2015-07-29  Pedro Alves  <palves@redhat.com>

	* gdb.base/restore.exp (restore_tests): Use gdb_continue_to_end.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Uniquify test names from gdb.python/{py-objfile.exp, py-pp-registration.exp}
@ 2015-07-28 21:47 sergiodj+buildbot
  2015-07-29 20:48 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-07-28 21:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d60a92216e5d599fed6b37c58c744debe38a0b24 ***

Author: Sergio Durigan Junior <sergiodj@redhat.com>
Branch: master
Commit: d60a92216e5d599fed6b37c58c744debe38a0b24

Uniquify test names from gdb.python/{py-objfile.exp,py-pp-registration.exp}
While running some regression tests, I noticed that the two Python
tests mentioned in the $SUBJECT contain non-unique names.  This is a
violation of our guidelines:

  <https://sourceware.org/gdb/wiki/GDBTestcaseCookbook#Make_sure_test_messages_are_unique>

And also makes things harder for BuildBot.  So I hacked both testcases
and made every test name unique.  I guess this could be considered an
obvious patch, but I decided to post it before pushing because others
may have different opinions about the names.

OK to apply?

gdb/testsuite/ChangeLog:
2015-07-28  Sergio Durigan Junior  <sergiodj@redhat.com>

	* gdb.python/py-objfile.exp: Make some tests have unique names.
	* gdb.python/py-pp-registration.exp: Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Remove xfail in gdb.mi/mi-watch.exp
@ 2015-07-28  0:42 sergiodj+buildbot
  2015-07-29  8:24 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-07-28  0:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT da33c9a7bff093e772a381bf9ab42d876089cdcf ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: da33c9a7bff093e772a381bf9ab42d876089cdcf

Remove xfail in gdb.mi/mi-watch.exp
I noticed there was an unexpected pass in mi-watch.exp when running on
x86_64.  Doing a bit of archeology shows that the xfail was added by
4a543da.  This particular test failed on the MIPS architecture, which
the original contributor was working with.  Here is the thread:

https://www.sourceware.org/ml/gdb-patches/2007-09/msg00151.html

Looking at the latest buildbot results for MIPS, it seems that it's also
an unexpected pass on that architecture.  Therefore, I see no reason to
leave the xfail in place.

gdb/testsuite/ChangeLog:

	* gdb.mi/mi-watch.exp (test_watchpoint_triggering): Remove xfail.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Factor out int printing code from generic_val_print
@ 2015-07-27 22:28 sergiodj+buildbot
  2015-07-28 18:00 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-07-27 22:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b21b63420be3857c1d0e2676e1214d63fe38ed3d ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: b21b63420be3857c1d0e2676e1214d63fe38ed3d

Factor out int printing code from generic_val_print
gdb/ChangeLog:

	* valprint.c (generic_val_print): Factor out integer
	printing code to ...
	(generic_val_print_int): ... this new function.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [gdbserver] Don't set srv_linux_usrregs for aarch64*-*-linux*
@ 2015-07-27 16:55 sergiodj+buildbot
  2015-07-27 21:45 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-07-27 16:55 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 50904b25ecf09f14c9406157b7f51255b21f54c0 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 50904b25ecf09f14c9406157b7f51255b21f54c0

[gdbserver] Don't set srv_linux_usrregs for aarch64*-*-linux*
We don't use PTRACE_PEEKUSR/PTRACE_POKEUSR on aarch64-linux, so don't
need to set srv_linux_usrregs.  This patch removes that line.

gdb/gdbserver:

2015-07-27  Yao Qi  <yao.qi@linaro.org>

	* configure.srv (case aarch64*-*-linux*): Don't set
	srv_linux_usrregs.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Sync config with GCC
@ 2015-07-27 15:06 sergiodj+buildbot
  2015-07-27 16:39 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-07-27 15:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT edb71a9c3838b83424f6eb0ef04eab5b31aa7f4a ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: edb71a9c3838b83424f6eb0ef04eab5b31aa7f4a

Sync config with GCC
	Sync with GCC
	2015-07-24  Micahel Darling  <darlingm@gmail.com>

	PR other/66259
	* gettext.m4: Reflects renaming of configure.in to configure.ac
	* po.m4: Likewise
	* stdint.m4: Likewise
	* tcl.m4: Likewise


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Add gmonster-{1,2} perf testcases.
@ 2015-07-25  1:28 sergiodj+buildbot
  2015-07-25 21:17 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-07-25  1:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7fecd1b400ba3ba0ae9efba3662e1f75b519860f ***

Author: Doug Evans <dje@google.com>
Branch: master
Commit: 7fecd1b400ba3ba0ae9efba3662e1f75b519860f

Add gmonster-{1,2} perf testcases.
These testcases are mocks of real programs.
GDB doesn't care what the programs do, they just have to look
and/or behave like the real program.
These testcases exercise gdb when debugging really large programs.
E.g., gmonster-1 has 10,000 CUs, and gmonster-2 has 1000 shared libs
(which is actually a little small, 5000 would be more accurate).

gdb/testsuite/ChangeLog:

	* gdb.perf/lib/perftest/utils.py: New file.
	* gdb.perf/gm-hello.cc: New file.
	* gdb.perf/gm-pervasive-typedef.cc: New file.
	* gdb.perf/gm-pervasive-typedef.h: New file.
	* gdb.perf/gm-std.cc: New file.
	* gdb.perf/gm-std.h: New file.
	* gdb.perf/gm-use-cerr.cc: New file.
	* gdb.perf/gm-utils.h: New file.
	* gdb.perf/gmonster-null-lookup.py: New file.
	* gdb.perf/gmonster-pervasive-typedef.py: New file.
	* gdb.perf/gmonster-print-cerr.py: New file.
	* gdb.perf/gmonster-ptype-string.py: New file.
	* gdb.perf/gmonster-runto-main.py: New file.
	* gdb.perf/gmonster-select-file.py: New file.
	* gdb.perf/gmonster1-null-lookup.exp: New file.
	* gdb.perf/gmonster1-pervasive-typedef.exp: New file.
	* gdb.perf/gmonster1-print-cerr.exp: New file.
	* gdb.perf/gmonster1-ptype-string.exp: New file.
	* gdb.perf/gmonster1-runto-main.exp: New file.
	* gdb.perf/gmonster1-select-file.exp: New file.
	* gdb.perf/gmonster1.cc: New file.
	* gdb.perf/gmonster1.exp: New file.
	* gdb.perf/gmonster2-null-lookup.exp: New file.
	* gdb.perf/gmonster2-pervasive-typedef.exp: New file.
	* gdb.perf/gmonster2-print-cerr.exp: New file.
	* gdb.perf/gmonster2-ptype-string.exp: New file.
	* gdb.perf/gmonster2-runto-main.exp: New file.
	* gdb.perf/gmonster2-select-file.exp: New file.
	* gdb.perf/gmonster2.cc: New file.
	* gdb.perf/gmonster2.exp: New file.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Add perf testcase generator.
@ 2015-07-25  1:05 sergiodj+buildbot
  2015-07-25 19:41 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-07-25  1:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6eab34f3dc27a571071d8c56146c2ffda133f454 ***

Author: Doug Evans <dje@google.com>
Branch: master
Commit: 6eab34f3dc27a571071d8c56146c2ffda133f454

Add perf testcase generator.
gdb/testsuite/ChangeLog:

	* gdb.perf/README: New file.
	* lib/perftest.exp (tcl_string_list_to_python_list): New function.
	* lib/gen-perf-test.exp: New file.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] PerfTest::assemble functions return results.
@ 2015-07-25  0:40 sergiodj+buildbot
  2015-07-25 17:46 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-07-25  0:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 63738bfdb96f654322794384993a6f5d8608aab9 ***

Author: Doug Evans <dje@google.com>
Branch: master
Commit: 63738bfdb96f654322794384993a6f5d8608aab9

PerfTest::assemble functions return results.
gdb/testsuite/ChangeLog:

	* lib/perftest.exp (PerfTest::compile): Unconditionally call body.
	(PerfTest::startup): New function.
	(PerfTest::run): Return result of calling body.
	(PerfTest::assemble): Rewrite.
	* gdb.perf/backtrace.exp (PerfTest::assemble): Update function result.
	* gdb.perf/disassemble.exp (PerfTest::assemble): Ditto.
	* gdb.perf/single-step.exp (PerfTest::assemble): Ditto.
	* gdb.perf/skip-prologue.exp (PerfTest::assemble): Ditto.
	* gdb.perf/solib.exp (PerfTest::assemble): Ditto.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] lib/gdb.exp (clean_restart): Make executable optional.
@ 2015-07-25  0:14 sergiodj+buildbot
  2015-07-25 16:05 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-07-25  0:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7b606f95c9bcfa1b569fe5d33f7d2a73d39322f4 ***

Author: Doug Evans <dje@google.com>
Branch: master
Commit: 7b606f95c9bcfa1b569fe5d33f7d2a73d39322f4

lib/gdb.exp (clean_restart): Make executable optional.
gdb/testsuite/ChangeLog:

	* lib/gdb.exp (clean_restart): Make executable optional.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Clean up testsuite compiler_info support.
@ 2015-07-24 23:49 sergiodj+buildbot
  2015-07-25 14:31 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-07-24 23:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a97b16b8fcfc7ac818c43c9f9457966cfc47aed6 ***

Author: Doug Evans <dje@google.com>
Branch: master
Commit: a97b16b8fcfc7ac818c43c9f9457966cfc47aed6

Clean up testsuite compiler_info support.
gdb/testsuite/ChangeLog:

	* gdb.base/watchpoint.exp (test_complex_watchpoint): Remove
	compiler_info references.
	* gdb.cp/temargs.exp: Ditto.
	* lib/gdb.exp: Unset compiler_info instead of setting to "unknown".
	(get_compiler_info): Early exit if already computed.  Set compiler_info
	to "unknown" if there was a problem.
	(test_compiler_info): Add function comment.  Call get_compiler_info.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Add parallel build support for perf tests.
@ 2015-07-24 23:25 sergiodj+buildbot
  2015-07-25 12:55 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-07-24 23:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 35baa57fcfb50f7db24f7850ec9e34f4bc25b45c ***

Author: Doug Evans <dje@google.com>
Branch: master
Commit: 35baa57fcfb50f7db24f7850ec9e34f4bc25b45c

Add parallel build support for perf tests.
gdb/testsuite/ChangeLog:

	* Makefile.in (check/%.exp): Pass directory for GDB_PARALLEL.
	(workers/%.worker, build-perf): New rule.
	(GDB_PERFTEST_MODE): New variable.
	(check-perf): Use it.
	(clean): Clean up gdb.perf parallel build subdirs.
	* lib/build-piece.exp: New file.
	* lib/cache.exp (gdb_do_cache): Include $GDB_PARALLEL in path name.
	* lib/gdb.exp (standard_output_file): Include $GDB_PARALLEL in path
	name.
	(standard_temp_file): Ditto.
	(GDB_PARALLEL handling): Make outputs,temp,cache directories as subdirs
	of $GDB_PARALLEL.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Workaround debian change to default value of --as-needed.
@ 2015-07-24 22:54 sergiodj+buildbot
  2015-07-25 11:19 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-07-24 22:54 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6ebea266fd0a7a56c90db3ab6237ff9f6c919747 ***

Author: Doug Evans <dje@google.com>
Branch: master
Commit: 6ebea266fd0a7a56c90db3ab6237ff9f6c919747

Workaround debian change to default value of --as-needed.
gdb/testsuite/ChangeLog:

	* lib/future.exp (gdb_default_target_compile): New option
	"early_flags".
	* lib/gdb.exp (gdb_compile): Undo debian's change in default of
	--as-needed.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix s390 GNU/Linux build after enum __ptrace_request changes
@ 2015-07-24 19:41 sergiodj+buildbot
  2015-07-25  5:36 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-07-24 19:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2b4cab865440e2c61d72da31a1a5045c840c60fe ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 2b4cab865440e2c61d72da31a1a5045c840c60fe

Fix s390 GNU/Linux build after enum __ptrace_request changes
The buildbot noticed that the enum __ptrace_request series broke the
s390 GNU/Linux build:

../../binutils-gdb/gdb/s390-linux-nat.c: In function 'fetch_regs':
../../binutils-gdb/gdb/s390-linux-nat.c:226:54: error: macro "ptrace" requires 4 arguments, but only 3 given
   if (ptrace (PTRACE_PEEKUSR_AREA, tid, (long) &parea) < 0)
                                                      ^
../../binutils-gdb/gdb/s390-linux-nat.c: In function 'store_regs':
../../binutils-gdb/gdb/s390-linux-nat.c:243:54: error: macro "ptrace" requires 4 arguments, but only 3 given
   if (ptrace (PTRACE_PEEKUSR_AREA, tid, (long) &parea) < 0)
                                                      ^

Fix this the same way it's handled everywhere else -- just pass 0 as
forth argument, which also handles non-varargs ptrace prototypes in
non-glibc libcs, e.g., Bionic (if it ever gets a s390 port...).

gdb/ChangeLog:
2015-07-24  Pedro Alves  <palves@redhat.com>

	* s390-linux-nat.c (fetch_regs, store_regs, fetch_fpregs)
	(s390_stopped_by_watchpoint, s390_prepare_to_resume): Pass 0 as
	forth argument to ptrace PTRACE_PEEKUSR_AREA/PTRACE_POKEUSR_AREA.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Set proc->priv->new_inferior out of linux_add_process
@ 2015-07-24 15:48 sergiodj+buildbot
  2015-07-24 22:33 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-07-24 15:48 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5ae3ebbae55482a9fdd01bd21455b396e23e4077 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 5ae3ebbae55482a9fdd01bd21455b396e23e4077

Set proc->priv->new_inferior out of linux_add_process
Nowadays, we set proc->priv->new_inferior to 1 inside linux_add_process,
and new_inferior is used as a flag to initialise target description later.
linux_add_process is used for the three cases, fork/vfork event
(handle_extended_wait), run the program (linux_create_inferior), and
attach to the process (linux_attach).  In the first case, the child's
target description is copied from parent's, so we don't need to initialise
target description again later, which means we don't need to set
proc->priv->new_inferior to 1 in this case.  For the rest of two cases,
we need this flag.

This patch move the code setting proc->priv->new_inferior to 1 inside
linux_add_process to linux_create_inferior and linux_attach.  No
functionality is changed.

gdb/gdbserver:

2015-07-24  Yao Qi  <yao.qi@linaro.org>

	* linux-low.c (linux_add_process): Don't set
	proc->priv->new_inferior.
	(linux_create_inferior): Set proc->priv->new_inferior to 1.
	(linux_attach): Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Refactor start_inferior
@ 2015-07-24 15:23 sergiodj+buildbot
  2015-07-24 20:24 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-07-24 15:23 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT eb97750bce2bf37176f745636815600177fbdba8 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: eb97750bce2bf37176f745636815600177fbdba8

Refactor start_inferior
This patch is to refactor function start_inferior that signal_pid
is return in one place.

gdb/gdbserver:

2015-07-24  Yao Qi  <yao.qi@linaro.org>

	* server.c (start_inferior): Code refactor.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] bfd_get_section_by_name_if hash chain traversal
@ 2015-07-24  6:05 sergiodj+buildbot
  2015-07-24  7:08 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-07-24  6:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2fb9328d8daa751f3b71745636323eddccaaacce ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 2fb9328d8daa751f3b71745636323eddccaaacce

bfd_get_section_by_name_if hash chain traversal
This function stops too soon, as I found when the hash chain happened
to contain two .debug_macro sections and a .bss section:
.debug_macro -> .bss -> .debug_macro

	* section.c (bfd_get_section_by_name_if): Iterate over entire hash
	chain.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix DT_MIPS_RLD_MAP_REL tag for n64 target and 32-bit host.
@ 2015-07-23 22:06 sergiodj+buildbot
  2015-07-23 23:40 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-07-23 22:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d5cff5df74b18e1e5ed94de8f4c9adee3ffd95c6 ***

Author: Joseph Myers <joseph@codesourcery.com>
Branch: master
Commit: d5cff5df74b18e1e5ed94de8f4c9adee3ffd95c6

Fix DT_MIPS_RLD_MAP_REL tag for n64 target and 32-bit host.
For the case of MIPS n64 target and 32-bit host, the computation of
the DT_MIPS_RLD_MAP_REL tag involves sdyn->output_section->vma +
sdyn->output_offset (64-bit) being added to b (32-bit host pointer),
so losing the high part and resulting in an incorrect
DT_MIPS_RLD_MAP_REL tag, and all dynamically linked glibc tests
failing for n64.  This patch fixes this (spot-tested with glibc tests;
however, I don't have a self-contained testcase for this bug).

	* elfxx-mips.c (_bfd_mips_elf_finish_dynamic_sections)
	<DT_MIPS_RLD_MAP_REL>: Add target address to host address
	difference, not to host pointer.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix crash when reading dummy CUs.
@ 2015-07-23 16:45 sergiodj+buildbot
  2015-07-23 18:36 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-07-23 16:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cc12ce380e8dab7e3cee8ecad29db6e9bb36a8fa ***

Author: Doug Evans <dje@google.com>
Branch: master
Commit: cc12ce380e8dab7e3cee8ecad29db6e9bb36a8fa

Fix crash when reading dummy CUs.
Dummy CUs are used by the incremental linker to pre-allocate space
in the output file. They have a DWARF header but no contents.

gdb/ChangeLog:

	* dwarf2read.c (dwarf2_per_cu_data): Add comment.
	(load_cu): Handle dummy CUs.
	(dw2_do_instantiate_symtab, process_queuef): Ditto.
	(dwarf2_fetch_die_loc_sect_off, dwarf2_fetch_constant_bytes): Ditto.

gdb/testsuite/ChangeLog:

	* gdb.dwarf2/dw2-dummy-cu.S: New file.
	* gdb.dwarf2/dw2-dummy-cu.exp: New file.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] py-linetable.c: Fix doc of LineTable.source_lines' return type
@ 2015-07-23 13:59 sergiodj+buildbot
  2015-07-23 16:21 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-07-23 13:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7b849db4f213d6734b4121ca5e5cab3341a5140c ***

Author: Ciro Santilli <ciro.santilli@gmail.com>
Branch: master
Commit: 7b849db4f213d6734b4121ca5e5cab3341a5140c

py-linetable.c: Fix doc of LineTable.source_lines' return type
The ltpy_get_all_source_lines function, use to implement
the gdb.LineTable.source_lines method, returns a list:

    source_list = PyDict_Keys (source_dict);
    return source_list;

This patch fixes the function's documentation as well as its docstring
to say that it returns a list rather than a FrozenSet.

gdb/ChangeLog:

        * py-linetable.c (ltpy_get_all_source_lines): Adjust function
        documentation to say that it returns a list rather than
        a FrozenSet.
        (linetable_object_methods): Update the docstring of the
        "source_line" entry.

Tested on x86_64-linux.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] gdb/gdbtypes: fix handling of typedef layers between array types
@ 2015-07-23 13:22 sergiodj+buildbot
  2015-07-23 14:26 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-07-23 13:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d0d8478068ae7c01b1a504ca2fba90c1d36c5566 ***

Author: Pierre-Marie de Rodat <derodat@adacore.com>
Branch: master
Commit: d0d8478068ae7c01b1a504ca2fba90c1d36c5566

gdb/gdbtypes: fix handling of typedef layers between array types
When a dynamic array type contains a typedef-wrapped array, an assertion
failure occurs during type resolution.  This is what happens in the
following Ada case:

    type Rec_Type is record
       I : Integer;
       B : Boolean;
    end record;

    type Vec_Type is array (1 .. 4) of Rec_Type;

    type Array_Type is array (Positive range <>) of Vec_Type;

If users try to print or even pass to an inferior call a variable A of
type Array_Type, GDB will raise an error:

    (gdb) print a
    ../../src/gdb/gdbtypes.c:1807: internal-error:
    resolve_dynamic_array: Assertion `TYPE_CODE (type) ==
    TYPE_CODE_ARRAY' failed.
    A problem internal to GDB has been detected,
    further debugging may prove unreliable.
    Quit this debugging session? (y or n)

What happens is that during dynamic array type resolution, we first peel
TYPE_CODE_TYPEDEF layers wrapping the array element type and check if
its type is itself TYPE_CODE_ARRAY.  If it is, we pass the
typedef-wrapped type to a recursive call to resolve_dynamic_array
whereas this function expects only TYPE_CODE_ARRAY types.

This patch makes it pass the peeled type to the recursive call so that
type resolution can continue smoothly.

gdb/ChangeLog:

	* gdbtypes.c (resolve_dynamic_array): Pass the peeled element
	type to the recursive call instead of the original (maybe
	TYPE_CODE_TYPEDEF) type.

gdb/testsuite/ChangeLog:

	* gdb.ada/var_arr_typedef.exp: New testcase.
	* gdb.ada/var_arr_typedef/pack.adb: New file.
	* gdb.ada/var_arr_typedef/pack.ads: New file.
	* gdb.ada/var_arr_typedef/var_arr_typedef.adb: New file.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Return zero in aarch64_linux_can_use_hw_breakpoint if target doesn't support HW watchpoint/breakpoint
@ 2015-07-23 10:40 sergiodj+buildbot
  2015-07-23 12:27 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-07-23 10:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c2fbdc5901a9220d0953f14c27760c3d3ae13074 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: c2fbdc5901a9220d0953f14c27760c3d3ae13074

Return zero in aarch64_linux_can_use_hw_breakpoint if target doesn't support HW watchpoint/breakpoint
Nowadays aarch64_linux_can_use_hw_breakpoint always return one, but it
can be smarter, say, if GDB knows target doesn't support HW watchpoint
or breakpoint because HW watchpoint/breakpoint is disabled in linux
kernel, for example, it can safely return zero.

gdb:

2015-07-23  Yao Qi  <yao.qi@linaro.org>

	* aarch64-linux-nat.c (aarch64_linux_can_use_hw_breakpoint): If
	TYPE is watchpoint, return zero if aarch64_num_wp_regs is zero.
	If TYPE is breakpoint, return zero if arch64_num_bp_regs is zero.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix ppc64 ELFv1 assertion failure
@ 2015-07-22 10:11 sergiodj+buildbot
  2015-07-22 11:46 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-07-22 10:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bb854a36d192bfa6609da9e3b1342e33da445598 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: bb854a36d192bfa6609da9e3b1342e33da445598

Fix ppc64 ELFv1 assertion failure
Bogus assembly can hit an assertion in opd_entry_value when the symbol
referenced by a function descriptor is undefined.  Worse, the code
after the assert copies unitialised memory to return the code section.
This uninitialised pointer can later be dereferencd, possibly causing
a linker segmentation fault.

	* elf64-ppc.c (opd_entry_value): Remove assertion.  Instead,
	return -1 if symbol referenced is not defined.  Tidy.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Move aarch64_linux_get_debug_reg_capacity to nat/aarch64-linux-hw-point.c
@ 2015-07-21 15:55 sergiodj+buildbot
  2015-07-21 17:07 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-07-21 15:55 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT af1b22f3004774f8c5c570abe7fab629026032f7 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: af1b22f3004774f8c5c570abe7fab629026032f7

Move aarch64_linux_get_debug_reg_capacity to nat/aarch64-linux-hw-point.c
There are also some duplication on getting HW watchpoint/breakpoint
registers info between GDB and GDBserver.  This patch moves them
to nat/aarch64-linux-hw-point.c.

Note that ENABLE_NLS is not defined in GDBserver, so it should be OK
to use _( markup.

gdb:

2015-07-21  Yao Qi  <yao.qi@linaro.org>

	* aarch64-linux-nat.c (aarch64_linux_get_debug_reg_capacity):
	Move it to nat/aarch64-linux-hw-point.c.
	(aarch64_linux_child_post_startup_inferior): Update.
	* nat/aarch64-linux-hw-point.c (aarch64_linux_get_debug_reg_capacity):
	New function.
	* nat/aarch64-linux-hw-point.h (aarch64_linux_get_debug_reg_capacity):
	Declare it.

gdb/gdbserver:

2015-07-21  Yao Qi  <yao.qi@linaro.org>

	* linux-aarch64-low.c (aarch64_arch_setup): Remove code and call
	aarch64_linux_get_debug_reg_capacity.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] btrace: fix case label in btrace_data_append
@ 2015-07-21 12:11 sergiodj+buildbot
  2015-07-21 13:37 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-07-21 12:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 40e050d242199ac67803c155ac2062169e5cf53d ***

Author: Markus Metzger <markus.t.metzger@intel.com>
Branch: master
Commit: 40e050d242199ac67803c155ac2062169e5cf53d

btrace: fix case label in btrace_data_append
gdb/
	* common/btrace-common.c (btrace_data_append): Change case label.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Make binutils abort message GDB friendly
@ 2015-07-20 13:07 sergiodj+buildbot
  2015-07-20 18:06 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-07-20 13:07 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7ac018954bd9c2d964204a451ecabdd7d8a11945 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 7ac018954bd9c2d964204a451ecabdd7d8a11945

Make binutils abort message GDB friendly
We used to generate abort messages like:

internal error, aborting at .../bfd/elf64-x86-64.c line 1554 in elf_x86_64_check_relocs

We can't cut and paste "file line ???" to GDB.  This patch changes those
abort messages to

internal error, aborting at .../bfd/elf64-x86-64.c:1554 in elf_x86_64_check_relocs

so that we can cut and paste "file:???" to GDB.

bfd/

	* bfd.c (_bfd_abort): Replace " line " with ":" in output
	message.

gas/

	* messages.c (as_assert): Replace " line " with ":" in output
	message.
	(as_abort): Likewise.

ld/

	* ldmisc.c (ld_abort): Replace " line " with ":" in output
	message.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] dwarf2read: Allow SEC_ALLOC sections to be located at address 0.
@ 2015-07-18 17:30 sergiodj+buildbot
  2015-07-18 18:51 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-07-18 17:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b4e1fd615ae6582170a6bb62d6519d586bd5347e ***

Author: Kevin Buettner <kevinb@redhat.com>
Branch: master
Commit: b4e1fd615ae6582170a6bb62d6519d586bd5347e

dwarf2read: Allow SEC_ALLOC sections to be located at address 0.
GDB already allows statically initialized variables, located in
SEC_LOAD sections, to be placed at address 0.  This change allows
uninitialized variables (which are in SEC_ALLOC sections) to be placed
address 0 as well.

gdb/ChangeLog:

	* dwarf2read.c (dwarf2_locate_sections): Allow has_section_at_zero
	to be set for SEC_ALLOC sections too.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Move common aarch64 HW breakpoint/watchpoint code to nat/
@ 2015-07-17 15:21 sergiodj+buildbot
  2015-07-18  0:13 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-07-17 15:21 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 554717a3edce7e266d409cd2c9c76d92584ac156 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 554717a3edce7e266d409cd2c9c76d92584ac156

Move common aarch64 HW breakpoint/watchpoint code to nat/
When I look at test fails related to watchpoint on aarch64-linux,
I find there are some code duplicates between GDB and GDBserver.
This patch is to move some of them to a nat/aarch64-linux-hw-point.{h,c}.

The only change I do is about the dr_changed_t typedef, which was
ULONGEST in GDB and 'unsigned long long' in GDBserver.  Each bit
of dr_changed_t represents a status of each HW breakpoint or
watchpoint register, and the max number of HW breakpoint or watchpoint
registers is 16, so the width of 'unsigned long long' is sufficient.

gdb:

2015-07-17  Yao Qi  <yao.qi@linaro.org>

	* Makefile.in (HFILES_NO_SRCDIR): Add
	nat/aarch64-linux-hw-point.h.
	(aarch64-linux-hw-point.o): New rule.
	* nat/aarch64-linux-hw-point.h: New file.
	* nat/aarch64-linux-hw-point.c: New file.
	* aarch64-linux-nat.c: Include nat/aarch64-linux-hw-point.h.
	(AARCH64_HBP_MAX_NUM): Move to nat/aarch64-linux-hw-point.h.
	(AARCH64_HWP_MAX_NUM, AARCH64_HBP_ALIGNMENT): Likewise.
	(AARCH64_HWP_ALIGNMENT): Likewise.
	(AARCH64_HWP_MAX_LEN_PER_REG): Likewise.
	(AARCH64_DEBUG_NUM_SLOTS, AARCH64_DEBUG_ARCH): Likewise.
	(AARCH64_DEBUG_ARCH_V8, DR_MARK_ALL_CHANGED): Likewise.
	(DR_MARK_N_CHANGED, DR_CLEAR_CHANGED): Likewise.
	(DR_HAS_CHANGED, DR_N_HAS_CHANGE): Likewise.
	(aarch64_num_bp_regs, aarch64_num_wp_regs): Likewise.
	(struct aarch64_debug_reg_state): Likewise.
	(struct arch_lwp_info):	Likewise.
	(aarch64_linux_set_debug_regs): Likewise.
	(aarch64_notify_debug_reg_change): Remove static.
	(aarch64_align_watchpoint): Likewise.
	(DR_CONTROL_ENABLED, DR_CONTROL_LENGTH): Likewise.
	(aarch64_watchpoint_length): Likewise.
	(aarch64_point_encode_ctrl_reg): Likewise
	(aarch64_point_is_aligned): Likewise.
	(aarch64_dr_state_insert_one_point): Likewise.
	(aarch64_dr_state_remove_one_point): Likewise.
	(aarch64_handle_breakpoint): Likewise.
	(aarch64_handle_aligned_watchpoint): Likewise.
	(aarch64_handle_unaligned_watchpoint): Likewise.
	(aarch64_handle_watchpoint): Likewise.
	* config/aarch64/linux.mh (NAT_FILE): Add
	aarch64-linux-hw-point.o.

gdb/gdbserver:

2015-07-17  Yao Qi  <yao.qi@linaro.org>

	* Makefile.in (aarch64-linux-hw-point.o): New rule.
	* configure.srv (srv_tgtobj): Append aarch64-linux-hw-point.o.
	* linux-aarch64-low.c: Include nat/aarch64-linux-hw-point.h.
	(AARCH64_HBP_MAX_NUM): Move to nat/aarch64-linux-hw-point.h.
	(AARCH64_HWP_MAX_NUM, AARCH64_HBP_ALIGNMENT): Likewise.
	(AARCH64_HWP_ALIGNMENT): Likewise.
	(AARCH64_HWP_MAX_LEN_PER_REG): Likewise.
	(AARCH64_DEBUG_NUM_SLOTS, AARCH64_DEBUG_ARCH): Likewise.
	(aarch64_num_bp_regs, aarch64_num_wp_regs): Likewise.
	(AARCH64_DEBUG_ARCH_V8, DR_MARK_ALL_CHANGED): Likewise.
	(DR_MARK_N_CHANGED, DR_CLEAR_CHANGED): Likewise.
	(DR_HAS_CHANGED, DR_N_HAS_CHANGE): Likewise.
	(struct aarch64_debug_reg_state): Likewise.
	(struct arch_lwp_info):	Likewise.
	(aarch64_align_watchpoint): Likewise.
	(DR_CONTROL_ENABLED, DR_CONTROL_LENGTH): Likewise.
	(aarch64_watchpoint_length): Likewise.
	(aarch64_point_encode_ctrl_reg): Likewise
	(aarch64_point_is_aligned): Likewise.
	(aarch64_align_watchpoint): Likewise.
	(aarch64_linux_set_debug_regs):
	(aarch64_dr_state_insert_one_point): Likewise.
	(aarch64_dr_state_remove_one_point): Likewise.
	(aarch64_handle_breakpoint): Likewise.
	(aarch64_handle_aligned_watchpoint): Likewise.
	(aarch64_handle_unaligned_watchpoint): Likewise.
	(aarch64_handle_watchpoint): Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Pass aarch64_debug_reg_state to functions
@ 2015-07-17 14:57 sergiodj+buildbot
  2015-07-17 22:34 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-07-17 14:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c67ca4de63fb3018a7e21ec4afe709d4c0dd52c4 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: c67ca4de63fb3018a7e21ec4afe709d4c0dd52c4

Pass aarch64_debug_reg_state to functions
Some functions on handling HW watchpoint in GDB and GDBserver looks the
same except the code getting debug register state from current inferior.
In GDB, we get debug register state like this:

  state = aarch64_get_debug_reg_state (ptid_get_pid (inferior_ptid));

while in GDBserver, we get debug register state like this:

  state = aarch64_get_debug_reg_state ();

This patch is to move two lines above out of some functions, and pass
aarch64_debug_reg_state to these functions, in this way, these functions
are the same, and can be moved to a common place.

gdb:

2015-07-17  Yao Qi  <yao.qi@linaro.org>

	* aarch64-linux-nat.c (aarch64_handle_breakpoint): Add argument
	state and don't call aarch64_get_debug_reg_state.  All callers
	update.
	(aarch64_linux_insert_hw_breakpoint): Call
	aarch64_get_debug_reg_state earlier.
	(aarch64_linux_remove_hw_breakpoint): Likewise.
	(aarch64_handle_aligned_watchpoint): Add argument state and
	don't call aarch64_get_debug_reg_state.  All callers update.
	(aarch64_handle_unaligned_watchpoint): Likewise.
	(aarch64_handle_watchpoint): Add argument state.
	(aarch64_linux_insert_watchpoint): Call aarch64_get_debug_reg_state
	earlier.
	(aarch64_linux_remove_watchpoint): Likewise.

gdb/gdbserver:

2015-07-17  Yao Qi  <yao.qi@linaro.org>

	* linux-aarch64-low.c (aarch64_handle_breakpoint): Add argument state
	and don't aarch64_get_debug_reg_state.  All callers update.
	(aarch64_handle_aligned_watchpoint): Likewise.
	(aarch64_handle_unaligned_watchpoint): Likewise.
	(aarch64_handle_watchpoint): Likewise.
	(aarch64_insert_point): Call aarch64_get_debug_reg_state earlier.
	(aarch64_remove_point): Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix using uninitialised values
@ 2015-07-17 11:35 sergiodj+buildbot
  2015-07-17 12:37 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-07-17 11:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6a49a997b406fba3a389d9d8a6ff72042606c69d ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 6a49a997b406fba3a389d9d8a6ff72042606c69d

Fix using uninitialised values
We did a code refacotr here
https://sourceware.org/ml/gdb-patches/2013-11/msg00063.html

>	(get_current_thread): New function, factored out from ...
>	(add_current_inferior_and_thread): ... this.  Adjust.
>
>@@ -3332,18 +3371,8 @@ add_current_inferior_and_thread (char *wait_status)
>
>   inferior_ptid = null_ptid;
>
>-  /* Now, if we have thread information, update inferior_ptid.  First
>-     if we have a stop reply handy, maybe it's a T stop reply with a
>-     "thread" register we can extract the current thread from.  If
>-     not, ask the remote which is the current thread, with qC.  The
>-     former method avoids a roundtrip.  Note we don't use
>-     remote_parse_stop_reply as that makes use of the target
>-     architecture, which we haven't yet fully determined at this
>-     point.  */
>-  if (wait_status != NULL)
>-    ptid = stop_reply_extract_thread (wait_status);
>-  if (ptid_equal (ptid, null_ptid))
>-    ptid = remote_current_thread (inferior_ptid);
>+  /* Now, if we have thread information, update inferior_ptid.  */
>+  ptid = get_current_thread (wait_status);

but after the refactor, local variable ptid is used without
initialisation.  However, before this change, ptid is initialised to
null_ptid.  This error can be found by valgrind too...

==3298==    at 0x6B99BA: ptid_equal (ptid.c:80)
==3298==    by 0x4C67FF: get_current_thread (remote.c:3484)
==3298==    by 0x4C6951: add_current_inferior_and_thread (remote.c:3511)
==3298==    by 0x4C762C: extended_remote_create_inferior (remote.c:8506)
==3298==    by 0x5A5312: run_command_1 (infcmd.c:606)
==3298==    by 0x68B4FB: execute_command (top.c:463)
==3298==    by 0x5C7214: command_handler (event-top.c:494)
==3298==    by 0x5C78A3: command_line_handler (event-top.c:692)
==3298==    by 0x6DEB57: rl_callback_read_char (callback.c:220)
==3298==    by 0x5C7278: rl_callback_read_char_wrapper (event-top.c:171)
==3298==    by 0x5C72C2: stdin_event_handler (event-top.c:432)
==3298==    by 0x5C6194: gdb_wait_for_event (event-loop.c:834)

This patch initialises local variable ptid to null in get_current_thread.
We don't need to initialise ptid in add_current_inferior_and_thread,
so this patch also removes the ptid initialisation.

gdb:

2015-07-17  Yao Qi  <yao.qi@linaro.org>

	* remote.c (get_current_thread): Initialise ptid to null_ptid.
	(add_current_inferior_and_thread): Don't initialise ptid.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [AArch64][2/3] GAS support BFD_RELOC_AARCH64_TLSLD_ADR_PREL21
@ 2015-07-16 15:29 sergiodj+buildbot
  2015-07-16 18:36 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-07-16 15:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6c37fedc41b028905cc828c0eccd3a8720512e4e ***

Author: Jiong Wang <jiong.wang@arm.com>
Branch: master
Commit: 6c37fedc41b028905cc828c0eccd3a8720512e4e

[AArch64][2/3] GAS support BFD_RELOC_AARCH64_TLSLD_ADR_PREL21


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [AArch64][1/3] Add R_AARCH64_P32_TLSLD_ADR_PREL21 in elf header
@ 2015-07-16 15:06 sergiodj+buildbot
  2015-07-16 16:47 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-07-16 15:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 53e8fd0f07cec1eb36149a64e4ed45923967453c ***

Author: Jiong Wang <jiong.wang@arm.com>
Branch: master
Commit: 53e8fd0f07cec1eb36149a64e4ed45923967453c

[AArch64][1/3] Add R_AARCH64_P32_TLSLD_ADR_PREL21 in elf header


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Unbreak nios2-*-linux* GDB testing.
@ 2015-07-15 15:43 sergiodj+buildbot
  2015-07-15 23:24 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-07-15 15:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 03346981fe6c11ab63b54a8d1919d6357e659684 ***

Author: Sandra Loosemore <sandra@codesourcery.com>
Branch: master
Commit: 03346981fe6c11ab63b54a8d1919d6357e659684

Unbreak nios2-*-linux* GDB testing.
2015-07-15  Sandra Loosemore  <sandra@codesourcery.com>

	gdb/testsuite/
	* gdb.base/sigaltstack.exp (finish_test): Add kfail for
	nios2-*-linux*.
	* gdb.base/sigbpt.exp (stepi_out): Likewise.
	* gdb.base/siginfo.exp: Likewise.
	* gdb.base/sigstep.exp (advance, advancei): Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [GDBserver][AArch64] Enable support for range stepping
@ 2015-07-15 14:22 sergiodj+buildbot
  2015-07-15 21:27 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-07-15 14:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d1d0aea1ea3572451ed04dc22a31ec1c50c606de ***

Author: Pierre Langlois <pierre.langlois@arm.com>
Branch: master
Commit: d1d0aea1ea3572451ed04dc22a31ec1c50c606de

[GDBserver][AArch64] Enable support for range stepping
gdb/gdbserver/Changelog:

	* linux-aarch64-low.c (aarch64_supports_range_stepping): New
	function, return 1.
	(the_low_target): Install it.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [testsuite] Skip gdb.trace/range-stepping.exp test case if not supported
@ 2015-07-15 13:43 sergiodj+buildbot
  2015-07-15 19:27 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-07-15 13:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 42422cc7d6c2e816ef1c4d268f41b58c031344f2 ***

Author: Pierre Langlois <pierre.langlois@arm.com>
Branch: master
Commit: 42422cc7d6c2e816ef1c4d268f41b58c031344f2

[testsuite] Skip gdb.trace/range-stepping.exp test case if not supported
Tracepoints and range stepping are independent features.  This patch
skips the gdb.trace/range-stepping.exp test case if the target does not
support range stepping.

gdb/testsuite/ChangeLog:

	* gdb.base/range-stepping.exp (gdb_range_stepping_enabled):
	Move it to ...
	* lib/range-stepping-support.exp (gdb_range_stepping_enabled):
	... here.
	* gdb.trace/range-stepping.exp: Check that the target supports
	range stepping.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] ari, btrace: avoid unsigned long long
@ 2015-07-15  6:52 sergiodj+buildbot
  2015-07-15 18:05 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-07-15  6:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e7b01ce03de85cfbbddb6ed755486db528abf1d1 ***

Author: Markus Metzger <markus.t.metzger@intel.com>
Branch: master
Commit: e7b01ce03de85cfbbddb6ed755486db528abf1d1

ari, btrace: avoid unsigned long long
Fix the ARI warning about the use of unsigned long long.  We can't use
ULONGEST as this is defined unsigned long on 64-bit systems.  This will
result in a compile error when storing a pointer to an unsigned long long
structure field (declared in perf_event.h as __u64) in a ULONGEST * variable.

Use size_t to hold the buffer size inside GDB and __u64 when interfacing the
Linux kernel.

gdb/
	* nat/linux-btrace.c (perf_event_read): Change the type of DATA_HEAD.
	(perf_event_read_all): Change the type of SIZE and DATA_HEAD.
	(perf_event_read_bts): Change the type of SIZE and READ.
	(linux_enable_bts): Change the type of SIZE, PAGES, DATA_SIZE,
	and DATA_OFFSET.  Move DATA_SIZE declaration.  Restrict the buffer size
	to UINT_MAX.  Check for overflows when using DATA_HEAD from the perf
	mmap page.
	(linux_enable_pt): Change the type of PAGES and SIZE.  Restrict the
	buffer size to UINT_MAX.
	(linux_read_bts): Change the type of BUFFER_SIZE, SIZE, DATA_HEAD, and
	DATA_TAIL.
	* nat/linux-btrace.h (struct perf_event_buffer)<size, data_head>
	<last_head>: Change type.
	* common/btrace-common.h (struct btrace_dat_pt) <size>: Change type.
	* common/btrace-common.c (btrace_data_append): Change the type of
	SIZE.
	* btrace.c (parse_xml_raw): Change the type of SIZE.  Change oddness
	check.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Remove CHECK_TYPEDEF, use check_typedef instead
@ 2015-07-14 21:08 sergiodj+buildbot
  2015-07-15 16:02 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-07-14 21:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f168693bc9d109c387e442119354bd57ecec8267 ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: f168693bc9d109c387e442119354bd57ecec8267

Remove CHECK_TYPEDEF, use check_typedef instead
I think that the CHECK_TYPEDEF macro is not necessary, and even a bit
annoying.  It makes unclear the fact that the "type" variables gets
overwritten.  It has actually bitten me a few times.  I think the
following, explicit form, is better.

  type = check_typedef (type);

This patches changes all instances of CHECK_TYPEDEF for an equivalent
call to check_typedef.  The bulk of the change was done with this sed:

  sed -i 's/CHECK_TYPEDEF (\([^)]*\));/\1 = check_typedef (\1);/' <file>.c

The ChangeLog was generated using David Malcom's generate_changelog.py.
I manually fixed those places where it gets the wrong function name,
hopefully all of them.

The patch was built-tested, and I ran a few smoke tests.

gdb/ChangeLog:
	* gdbtypes.h (CHECK_TYPEDEF): Remove.
	* aarch64-tdep.c (aarch64_return_in_memory): Replace CHECK_TYPEDEF
        with check_typedef.
	* ada-lang.c (decode_constrained_packed_array_type): Likewise.
	(ada_array_length): Likewise.
	(find_parallel_type_by_descriptive_type): Likewise.
	(ada_check_typedef): Likewise.
	* arm-tdep.c (arm_return_in_memory): Likewise.
	* ax-gdb.c (gen_trace_static_fields): Likewise.
	(gen_struct_ref_recursive): Likewise.
	* c-exp.y (exp : SIZEOF '(' type ')' %prec UNARY): Likewise.
	(variable: block COLONCOLON name): Likewise.
	(qualified_name: TYPENAME COLONCOLON name): Likewise.
	* c-lang.c (classify_type): Likewise.
	* c-typeprint.c (c_print_type): Likewise.
	(c_print_typedef): Likewise.
	(c_type_print_base): Likewise.
	* c-valprint.c (c_val_print): Likewise.
	* compile/compile-c-types.c (convert_type): Likewise.
	* compile/compile-object-load.c (get_out_value_type): Likewise.
	* completer.c (add_struct_fields): Likewise.
	(expression_completer): Likewise.
	* cp-namespace.c (cp_find_type_baseclass_by_name): Likewise.
	(cp_lookup_nested_symbol_1): Likewise.
	(cp_lookup_nested_symbol): Likewise.
	* cp-valprint.c (cp_print_value_fields): Likewise.
	(cp_print_static_field): Likewise.
	* d-valprint.c (d_val_print): Likewise.
	* eval.c (evaluate_subexp_standard): Likewise.
	(evaluate_subexp_for_sizeof): Likewise.
	* f-exp.y (exp : SIZEOF '(' type ')' %prec UNARY): Likewise.
	* f-typeprint.c (f_type_print_base): Likewise.
	* f-valprint.c (f_val_print): Likewise.
	* gdbtypes.c (get_discrete_bounds): Likewise.
	(create_array_type_with_stride): Likewise.
	(type_name_no_tag_or_error): Likewise.
	(lookup_struct_elt_type): Likewise.
	(get_unsigned_type_max): Likewise.
	(internal_type_vptr_fieldno): Likewise.
	(set_type_vptr_fieldno): Likewise.
	(internal_type_vptr_basetype): Likewise.
	(set_type_vptr_basetype): Likewise.
        (get_vptr_fieldno): Likewise.
	(is_integral_type): Likewise.
	(is_scalar_type): Likewise.
        (is_scalar_type_recursive): Likewise.
	(distance_to_ancestor): Likewise.
	(is_unique_ancestor_worker): Likewise.
	(check_types_equal): Likewise.
	* gnu-v2-abi.c (gnuv2_value_rtti_type): Likewise.
	* gnu-v3-abi.c (gnuv3_dynamic_class): Likewise.
	(gnuv3_get_vtable): Likewise.
	(gnuv3_pass_by_reference): Likewise.
	* go-exp.y (exp : SIZEOF_KEYWORD '(' type ')' %prec UNARY): Likewise.
	* go-lang.c (gccgo_string_p): Likewise.
	(go_classify_struct_type): Likewise.
	* go-typeprint.c (go_print_type): Likewise.
	* go-valprint.c (go_val_print): Likewise.
	* guile/scm-math.c (vlscm_binop): Likewise.
	* guile/scm-value.c (gdbscm_value_dynamic_type): Likewise.
	(gdbscm_value_to_bytevector): Likewise.
	(gdbscm_value_to_bool): Likewise.
	(gdbscm_value_to_integer): Likewise.
	(gdbscm_value_to_real): Likewise.
	* infcall.c (call_function_by_hand_dummy): Likewise.
	* infcmd.c (get_return_value): Likewise.
	* jv-lang.c (is_object_type): Likewise.
	* jv-typeprint.c (java_type_print_base): Likewise.
	* jv-valprint.c (java_print_value_fields): Likewise.
	(java_val_print): Likewise.
	* linespec.c (find_methods): Likewise.
	(collect_one_symbol): Likewise.
	* m2-typeprint.c (m2_print_type): Likewise.
	(m2_print_typedef): Likewise.
	(m2_get_discrete_bounds): Likewise.
	* m2-valprint.c (m2_print_long_set): Likewise.
	(m2_print_unbounded_array): Likewise.
	(m2_print_array_contents): Likewise.
	(m2_val_print): Likewise.
	* opencl-lang.c (opencl_print_type): Likewise.
	* p-exp.y (exp : SIZEOF '(' type ')' %prec UNARY): Likewise.
	* p-typeprint.c (pascal_print_type): Likewise.
	(pascal_print_typedef): Likewise.
	(pascal_type_print_base): Likewise.
	* p-valprint.c (pascal_val_print): Likewise.
	(pascal_object_print_value_fields): Likewise.
	(pascal_object_print_static_field): Likewise.
	* python/py-type.c (typy_fields_items): Likewise.
	(typy_get_composite): Likewise.
	* python/py-value.c (valpy_get_dynamic_type): Likewise.
	(valpy_binop): Likewise.
	(valpy_long): Likewise.
	(valpy_float): Likewise.
	* stack.c (return_command): Likewise.
	* symtab.c (check_field): Likewise.
	(lookup_symbol_aux): Likewise.
	* tic6x-tdep.c (tic6x_return_value): Likewise.
	* typeprint.c (print_type_scalar): Likewise.
	* valarith.c (value_vector_widen): Likewise.
	* valops.c (value_cast): Likewise.
	(value_assign): Likewise.
	(do_search_struct_field): Likewise.
	(search_struct_method): Likewise.
	(find_method_list): Likewise.
	* valprint.c (val_print_scalar_type_p): Likewise.
	(valprint_check_validity): Likewise.
	(generic_val_print): Likewise.
	* value.c (unpack_double): Likewise.
	(value_primitive_field): Likewise.
	(unpack_bits_as_long): Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Sync Makefile.tpl with GCC
@ 2015-07-14 18:28 sergiodj+buildbot
  2015-07-15 11:38 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-07-14 18:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 22121df01ff9247b3cb272f52632848f9631f80f ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 22121df01ff9247b3cb272f52632848f9631f80f

Sync Makefile.tpl with GCC
	* Makefile.in: Regenerated.

	Sync with GCC
	2015-05-21  Jason Merrill  <jason@redhat.com>

	* Makefile.tpl: Update comments.

	2015-04-22  Bernhard Reutner-Fischer  <aldot@gcc.gnu.org>

	* Makefile.tpl: Remove surplus whitespace throughout.

	2015-03-25  Martin Liska  <mliska@suse.cz>
		    Yury Gribov  <y.gribov@samsung.com>

	* Makefile.tpl: Fix ln source location for vimrc file.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Sync longlong.h with GCC
@ 2015-07-14 18:08 sergiodj+buildbot
  2015-07-15  9:49 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-07-14 18:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT dc2edb520a534fd0c2af169d46b4d892208e8f42 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: dc2edb520a534fd0c2af169d46b4d892208e8f42

Sync longlong.h with GCC
	Sync with GCC
	2014-10-28  Richard Henderson  <rth@redhat.com>

	* longlong.h [__alpha] (umul_ppmm): Disable for c++.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Sync ansidecl.h with GCC
@ 2015-07-14 17:09 sergiodj+buildbot
  2015-07-15  4:44 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-07-14 17:09 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4d6404f01d38b1f34bd9bba4d78276e8154f3312 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 4d6404f01d38b1f34bd9bba4d78276e8154f3312

Sync ansidecl.h with GCC
	Sync with GCC
	2015-03-02  Markus Trippelsdorf  <markus@trippelsdorf.de>

	PR target/65261
	* ansidecl.h (ATTRIBUTE_NO_SANITIZE_UNDEFINED): New macro.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Sync config files with GCC
@ 2015-07-14 16:50 sergiodj+buildbot
  2015-07-15  2:08 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-07-14 16:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 49d00f48e8e3c1331d367785f19c69867a47b4cd ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 49d00f48e8e3c1331d367785f19c69867a47b4cd

Sync config files with GCC
	Sync with GCC
	2015-05-13  Eric Botcazou  <ebotcazou@adacore.com>

	* sjlj.m4: New file.

	2015-05-04  Trevor Saunders  <tbsaunde+gcc@tbsaunde.org>

	* bitfields.m4: Change int to long long, and use bitfields of
	width 1 instead of 0.

	2015-05-01  Trevor Saunders  <tbsaunde+gcc@tbsaunde.org>

	* bitfields.m4: New file.

	2015-04-14  H.J. Lu  <hongjiu.lu@intel.com>

	* bootstrap-mpx.mk: New file.

	2015-03-25  Uros Bizjak  <ubizjak@gmail.com>

	PR bootstrap/65537
	* bootstrap-lto-noplugin.mk: New build configuration.

	2014-11-13  Kirill Yukhin  <kirill.yukhin@intel.com>

	* target-posix: New file.

	2014-10-27  Tom Tromey  <tromey@redhat.com>

	* gcc-plugin.m4: New file.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix build issue with nat/linux-namespaces.c.
@ 2015-07-14 16:28 sergiodj+buildbot
  2015-07-15  0:15 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-07-14 16:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 99fe86f7999afd2743b08c550b10f083ae4bd9bd ***

Author: Peter Bergner <bergner@vnet.ibm.com>
Branch: master
Commit: 99fe86f7999afd2743b08c550b10f083ae4bd9bd

Fix build issue with nat/linux-namespaces.c.
	* nat/linux-namespaces.c (setns): Rename from this ...
	(do_setns): ... to this.  Support calling setns if it exists.
	(mnsh_handle_setns): Call do_setns.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Sync config/warnings.m4 with GCC
@ 2015-07-14 16:05 sergiodj+buildbot
  2015-07-14 22:36 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-07-14 16:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8a643cc36cf121de3a9131f95547eba927413710 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 8a643cc36cf121de3a9131f95547eba927413710

Sync config/warnings.m4 with GCC
config/

	Sync with GCC
	2015-05-27  Jason Merrill  <jason@redhat.com>

	PR bootstrap/66304
	* warnings.m4 (ACX_PROG_CXX_WARNING_OPTS)
	(ACX_PROG_CXX_WARNINGS_ARE_ERRORS)
	(ACX_PROG_CXX_WARNING_ALMOST_PEDANTIC): New.
	(ACX_PROG_CC_WARNING_OPTS, ACX_PROG_CC_WARNING_ALMOST_PEDANTIC)
	(ACX_PROG_CC_WARNINGS_ARE_ERRORS): Push into C language context.

libdecnumber/

	* configure: Regenerated.

libiberty/

	* configure: Regenerated.

opcodes/

	* configure: Regenerated.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Sync toplevel configure.ac with GCC
@ 2015-07-14 15:13 sergiodj+buildbot
  2015-07-14 18:52 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-07-14 15:13 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ce6c656dcb8257b7c05975039700e3c9f4c3af3b ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: ce6c656dcb8257b7c05975039700e3c9f4c3af3b

Sync toplevel configure.ac with GCC
	Sync with GCC
	2015-06-02  Jason Merrill  <jason@redhat.com>

	PR bootstrap/66319
	* configure.ac: Use -std=gnu++98.

	2015-05-28  Mike Frysinger  <vapier@gentoo.org>

	* configure.ac (--vtable-verify): Use AS_HELP_STRING for help.
	* configure: Regenerate.

	2015-05-11  Paulo Matos  <paulo@matos-sorge.com>

	* configure.ac: Fix typo.
	* configure: Regenerate.

	2015-05-03  Matthias Klose  <doko@ubuntu.com>

	* configure.ac: Match $host configured with triplets.
	* configure: Regenerate.

	2015-04-17  Jakub Jelinek  <jakub@redhat.com>

	PR bootstrap/62077
	* configure.ac (--enable-stage1-checking): Default to
	release,misc,gimple,rtlflag,tree,types if --disable-checking
	or --enable-checking is not specified and DEV-PHASE is not
	experimental.
	* configure: Regenerated.

	2015-03-27  Uros Bizjak  <ubizjak@gmail.com>

	Install back PR target/47230 fix (Revert the revert).

config/

	Sync with GCC
	* mh-alpha-linux: Restored.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Remove extraneous whitespace from ARM sim sources.
@ 2015-07-14 11:31 sergiodj+buildbot
  2015-07-14 16:33 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-07-14 11:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 454de2ee151958e0c45d4ed0f3e496156e29d3a2 ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: 454de2ee151958e0c45d4ed0f3e496156e29d3a2

Remove extraneous whitespace from ARM sim sources.
	* armcopro.c: Remove extraneous whitespace.
	* armdefs.h: Likewise.
	* armfpe.h: Likewise.
	* arminit.c: Likewise.
	* armopts.h: Likewise.
	* armos.c: Likewise.
	* armos.h: Likewise.
	* armrdi.c: Likewise.
	* armsupp.c: Likewise.
	* armvirt.c: Likewise.
	* bag.c: Likewise.
	* bag.h: Likewise.
	* communicate.c: Likewise.
	* communicate.h: Likewise.
	* dbg_conf.h: Likewise.
	* dbg_cp.h: Likewise.
	* dbg_hif.h: Likewise.
	* dbg_rdi.h: Likewise.
	* gdbhost.c: Likewise.
	* gdbhost.h: Likewise.
	* iwmmxt.c: Likewise.
	* iwmmxt.h: Likewise.
	* kid.c: Likewise.
	* main.c: Likewise.
	* maverick.c: Likewise.
	* parent.c: Likewise.
	* thumbemu.c: Likewise.
	* wrapper.c: Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] gdbserver/Linux: internal error when killing a process that is already gone
@ 2015-07-14 10:02 sergiodj+buildbot
  2015-07-14 11:23 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-07-14 10:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 586b02a96f744497c8921a558f1c386287849ab0 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 586b02a96f744497c8921a558f1c386287849ab0

gdbserver/Linux: internal error when killing a process that is already gone
If the process disappears (e.g., killed with "kill -9" from the shell)
while it was stopped under GDBserver's control, and the GDBserver
tries to kill it, GDBserver asserts:

 (gdb) shell kill -9 23084
 (gdb) kill
 ...
 Killing process(es): 23084
 /home/pedro/gdb/mygit/src/gdb/gdbserver/linux-low.c:972: A problem internal to GDBserver has been detected.
 kill_wait_lwp: Assertion `res > 0' failed.
 ...

gdb/gdbserver/ChangeLog:
2015-07-14  Pedro Alves  <palves@redhat.com>

	* linux-low.c (kill_wait_lwp): Don't assert if waitpid fails.
	Instead, ignore ECHILD, and throw an error for other errnos.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] gdb/tui: Add command completion to winheight command.
@ 2015-07-13 14:51 sergiodj+buildbot
  2015-07-13 16:33 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-07-13 14:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 97605e61a14518b1a0ac2a576f4f3c843743e4d5 ***

Author: Andrew Burgess <andrew.burgess@embecosm.com>
Branch: master
Commit: 97605e61a14518b1a0ac2a576f4f3c843743e4d5

gdb/tui: Add command completion to winheight command.
Share the window name completion code from the focus command with the
winheight command, providing window name completion for the winheight
command.

gdb/ChangeLog:

	* tui/tui-win.c (window_name_completer): New function.
	(focus_completer): Call window_name_completer.  All old content
	moved into window_name_completer.
	(winheight_completer): New function.
	(_initialize_tui_win): Rename variable.  Add completer to
	winheight command.  Update doc string on winheight.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix GDB breakage due to addition of new nios2 mach types in BFD.
@ 2015-07-12 14:26 sergiodj+buildbot
  2015-07-12 16:02 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-07-12 14:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8d6dbeb44ca93b836e3af8f8d3993997bf347112 ***

Author: Sandra Loosemore <sandra@codesourcery.com>
Branch: master
Commit: 8d6dbeb44ca93b836e3af8f8d3993997bf347112

Fix GDB breakage due to addition of new nios2 mach types in BFD.
2015-07-12  Sandra Loosemore  <sandra@codesourcery.com>

	gdb/
	* nios2-linux-tdep.c (_initialize_nios2_linux_tdep): Register
	all nios2 mach variants.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Properly convert objects between different ELF classes
@ 2015-07-10 22:00 sergiodj+buildbot
  2015-07-11 19:46 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-07-10 22:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 889884731e09b46e4c2ecb051dfde1e2f69d2b47 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 889884731e09b46e4c2ecb051dfde1e2f69d2b47

Properly convert objects between different ELF classes
The output SHF_COMPRESSED section size is different from input if
ELF classes of input and output aren't the same.  We must adjust
the section sizes as well as the compression headers in
SHF_COMPRESSED sections when converting objects between different
ELF classes.

bfd/

	 PR binutils/18656
	 * bfd.c (bfd_convert_section_size): New function.
	 (bfd_convert_section_contents): Likewise.
	 * bfd-in2.h: Regenerated.

binutils/

2015-07-10  H.J. Lu  <hongjiu.lu@intel.com>

	 PR binutils/18656
	 * objcopy.c (setup_section): Call bfd_convert_section_size
	 to get the output section size.
	 (copy_section): Get the section size from the output section
	 and call bfd_get_full_section_contents to convert section
	 contents for output.

binutils/testsuite/

	 PR binutils/18656
	 * binutils-all/compress.exp (convert_test): New proc.
	 Run conversion tests between x86-64 and x32.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] rx-tdep.c: Use target_read_code instead of target_read_memory.
@ 2015-07-10 20:31 sergiodj+buildbot
  2015-07-11 18:14 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-07-10 20:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a0e28e54675fd92e73df71fed5d4f6c718f40102 ***

Author: Kevin Buettner <kevinb@redhat.com>
Branch: master
Commit: a0e28e54675fd92e73df71fed5d4f6c718f40102

rx-tdep.c: Use target_read_code instead of target_read_memory.
This change causes the prologue scanner and the frame type scanner in
rx-tdep.c to use target_read_code() instead of target_read_memory().
This change allows these instruction scanners to operate much more
quickly due to the fact that target_read_code() can potentially read
from a cache maintained by GDB.

gdb/ChangeLog:

	* rx-tdep.c (rx_get_opcode_byte): Use target_read_code instead
	of target_read_memory.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] gdb/tui: Use cleanups to free string copies.
@ 2015-07-10 12:39 sergiodj+buildbot
  2015-07-11 10:33 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-07-10 12:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c101f28fea4fc8621bdf864bc6e2132244dbe6a7 ***

Author: Andrew Burgess <andrew.burgess@embecosm.com>
Branch: master
Commit: c101f28fea4fc8621bdf864bc6e2132244dbe6a7

gdb/tui: Use cleanups to free string copies.
In parse_scrolling_args it is possible for a string copy to leak if an
error occurs.  Switching to using a cleanup fixes this leak.

In tui_set_win_height the string can't be leaked, but switching to using
a cleanup guards against the possibility that a leak could be introduced
in the future (by adding an error somewhere in the call stack).

gdb/ChangeLog:

	* tui/tui-win.c (tui_set_win_height): Use a cleanup to free the
	string copy.
	(parse_scrolling_args): Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] gdb: Convert TUI windows names to lower case.
@ 2015-07-10 11:43 sergiodj+buildbot
  2015-07-11  7:37 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-07-10 11:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6dce28e413375aa878cf43853d32657d1fc26c6f ***

Author: Andrew Burgess <andrew.burgess@embecosm.com>
Branch: master
Commit: 6dce28e413375aa878cf43853d32657d1fc26c6f

gdb: Convert TUI windows names to lower case.
This commit converts the window names for the TUI windows to lower case.
The windows names are already lower case in the documentation, and are
shown as lower case in some of the command completion results.

Given that all the commands that take a window name currently accept
upper or lower case, this commit just changes the window names to lower
case in the remaining places they are displayed by gdb.

gdb/ChangeLog:

	* tui/tui-data.h (SRC_NAME): Convert to lower case.
	(CMD_NAME): Likewise.
	(DATA_NAME): Likewise.
	(DISASSEM_NAME): Likewise.
	* tui/tui-win.c (tui_set_focus): Window names are now lower case.
	(tui_set_win_height): Likewise.
	(parse_scrolling_args): Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
[parent not found: <66c4b3e8a628a207bc6aafef6af0c4128195f56e@kwanyin>]
[parent not found: <bcd8537ce10dd72b053fa54e87525defa26f3fd0@kwanyin>]
[parent not found: <10e9aaa3b8554f997db993c8158493a96030d4d5@kwanyin>]
[parent not found: <8a13d42d99390c36d5e7884b509e6bb92ec72e3c@kwanyin>]
[parent not found: <a844296a982bdff7c14dab355de0fca75486add6@kwanyin>]
[parent not found: <118ca22445afc728069ca80be2f30dae6913059e@kwanyin>]
[parent not found: <0561fea48c107b271308a013c485c29cbd5c13b5@kwanyin>]
[parent not found: <2fd0f80d57e8437d70ba79921efd3ce02e755755@kwanyin>]
[parent not found: <58bfce93438e1f936d4547bb9659b7d096e2823f@kwanyin>]
[parent not found: <b0fd6b3037669534962b1ffe860db178ea7e1239@kwanyin>]
[parent not found: <bbcbf914a6ad801bfa7d4e56150217a1d53e07af@kwanyin>]
[parent not found: <0986c744dfecb8177de90020646090e9ed23cfe7@kwanyin>]
[parent not found: <b5fca6d7284b2cd2e90efc556eb6a29a1b177476@kwanyin>]
[parent not found: <c45613e33dbdc646b6fd7f02f86635639e852bfb@kwanyin>]
[parent not found: <d0bf44cb88be21ea009a4fe0e59a3d3e6e545aed@kwanyin>]
* [binutils-gdb] [GDBServer][AArch64] Enable support for Z0 packets
@ 2015-06-29 10:40 sergiodj+buildbot
  2015-06-29 14:21 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-06-29 10:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 96c97461222f9cb1a16b3b90fb7316c9c3d8732a ***

Author: Pierre Langlois <pierre.langlois@arm.com>
Branch: master
Commit: 96c97461222f9cb1a16b3b90fb7316c9c3d8732a

[GDBServer][AArch64] Enable support for Z0 packets
This patch lets GDBServer handle software breakpoints instead of relying
on GDB.

gdb/gdbserver/ChangeLog:

	* linux-aarch64-low.c (aarch64_supports_z_point_type): Enable for
	Z_PACKET_SW_BP.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [GDBServer][AArch64] Use the same break instruction as GDB
@ 2015-06-29 10:17 sergiodj+buildbot
  2015-06-29 12:31 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-06-29 10:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 37d669427f8b90f3c9d17a6e04d72c731d3abdbc ***

Author: Pierre Langlois <pierre.langlois@arm.com>
Branch: master
Commit: 37d669427f8b90f3c9d17a6e04d72c731d3abdbc

[GDBServer][AArch64] Use the same break instruction as GDB
GDB uses a "brk #0" instruction to perform a software breakpoint while
GDBServer uses an illegal instruction.  Both instructions should match.

When enabling support for the 'Z0' packet, we let GDBServer insert the
breakpoint instruction instead of GDB.  And in case of permanent
breakpoints for example, GDB will check if a breakpoint is inserted in the
inferior with `program_breakpoint_here_p (gdbarch, address)', and
compare the instruction read from the inferior with the breakpoint
instruction.

On AArch64, instructions are always little endian so we need to
represent it as an array of bytes, as done in aarch64-tdep.c.

gdb/gdbserver/ChangeLog:

	* linux-aarch64-low.c: Remove comment about endianness.
	(aarch64_breakpoint): Change type to gdb_byte[].  Set to "brk #0".
	(aarch64_breakpoint_at): Change type of insn to gdb_byte[].  Use
	memcmp.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Update my email address
@ 2015-06-29  9:46 sergiodj+buildbot
  2015-06-29 10:58 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-06-29  9:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1451ea7da40a82e8cf6a39fa8d0fc74ff230600a ***

Author: Pierre Langlois <pierre.langlois@arm.com>
Branch: master
Commit: 1451ea7da40a82e8cf6a39fa8d0fc74ff230600a

Update my email address
gdb/ChangeLog:

	* MAINTAINERS (Write After Approval): Update my email address.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] PR 16253 revisited
@ 2015-06-26 19:05 sergiodj+buildbot
  2015-06-26 20:26 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-06-26 19:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ee93cd5e1e61e5739a1a44e0d1d166ae09d04dc2 ***

Author: Keith Seitz <keiths@redhat.com>
Branch: master
Commit: ee93cd5e1e61e5739a1a44e0d1d166ae09d04dc2

PR 16253 revisited
Last year a patch was submitted/approved/commited to eliminate
symbol_matches_domain which was causing this problem.  It was later reverted
because it introduced a (severe) performance regression.

Recap:

(gdb) list
1	enum e {A,B,C} e;
2	int main (void) { return 0; }
3
(gdb) p e
Attempt to use a type name as an expression

The parser attempts to find a symbol named "e" of VAR_DOMAIN.
This gets passed down through lookup_symbol and (eventually) into
block_lookup_symbol_primary, which iterates over the block's dictionary
of symbols:

  for (sym = dict_iter_name_first (block->dict, name, &dict_iter);
       sym != NULL;
       sym = dict_iter_name_next (name, &dict_iter))
    {
      if (symbol_matches_domain (SYMBOL_LANGUAGE (sym),
                                 SYMBOL_DOMAIN (sym), domain))
        return sym;
    }

The problem here is that we have a symbol named "e" in both STRUCT_DOMAIN
and VAR_DOMAIN, and for languages like C++, Java, and Ada, where a tag name
may be used as an implicit typedef of the type, symbol_matches_domain ignores
the difference between VAR_DOMAIN and STRUCT_DOMAIN.  As it happens, the
STRUCT_DOMAIN symbol is found first, considered a match, and that symbol is
returned to the parser, eliciting the (now dreaded) error message.

Since this bug exists specifically because we have both STRUCT and VAR_DOMAIN
symbols in a given block/CU, this patch rather simply/naively changes
block_lookup_symbol_primary so that it continues to search for an exact
domain match on the symbol if symbol_matches_domain returns a symbol
which does not exactly match the requested domain.

This "fixes" the immediate problem, but admittedly might uncover other,
related bugs.  [Paranoia?] However, it causes no regressions (functional
or performance) in the test suite.  A similar change has been made
to block_lookup_symbol for other cases in which this bug might appear.

The tests from the previous submission have been resurrected and updated.
However since we can still be given a matching symbol with a different domain
than requested, we cannot say that a symbol "was not found."  The error
messages today will still be the (dreaded) "Attempt to use a type name..."

ChangeLog

	PR 16253
	* block.c (block_lookup_symbol): For non-function blocks,
	continue to search for a symbol with an exact domain match
	Otherwise, return any previously found "best domain" symbol.
	(block_lookup_symbol_primary): Likewise.

testsuite/ChangeLog

	PR 16253
	* gdb.cp/var-tag-2.cc: New file.
	* gdb.cp/var-tag-3.cc: New file.
	* gdb.cp/var-tag-4.cc: New file.
	* gdb.cp/var-tag.cc: New file.
	* gdb.cp/var-tag.exp: New file.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Add option to remove duplicate command history entries
@ 2015-06-26 15:18 sergiodj+buildbot
  2015-06-26 19:05 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-06-26 15:18 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fc637f04c741b08726cc1631428bf094235ecb4e ***

Author: Patrick Palka <patrick@parcs.ath.cx>
Branch: master
Commit: fc637f04c741b08726cc1631428bf094235ecb4e

Add option to remove duplicate command history entries
This patch implements the new option "history remove-duplicates", which
controls the removal of duplicate history entries ("off" by default).

The motivation for this option is to be able to reduce the prevalence of
basic commands such as "up" and "down" in the history file.  These
common commands crowd out more unique commands in the history file (when
the history file has a fixed size), and they make navigation of the
history file via ^P, ^N and ^R more inconvenient.

The option takes an integer denoting the number of history entries to
look back at for a history entry that is a duplicate of the latest one.
"history remove-duplicates 1" is equivalent to bash's ignoredups option,
and "history remove-duplicates unlimited" is equivalent to bash's
erasedups option.

[ I decided to go with this integer approach instead of a tri-state enum
  because it's slightly more flexible and seemingly more intuitive than
  leave/erase/ignore.  ]

gdb/ChangeLog:

	* NEWS: Mention the new option "history remove-duplicates".
	* top.c (history_remove_duplicates): New static variable.
	(show_history_remove_duplicates): New static function.
	(gdb_add_history): Conditionally remove duplicate history
	entries.
	(init_main): Add "history remove-duplicates" option.

gdb/doc/ChangeLog:

	* gdb.texinfo (Command History): Document the new option
	"history remove-duplicates".

gdb/testsuite/ChangeLog:

	* gdb.base/history-duplicates.exp: New test.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Add tab completion for TUI's "focus" command
@ 2015-06-26 14:37 sergiodj+buildbot
  2015-06-26 17:09 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-06-26 14:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2e52ae68e7cedc3a1f9908c98ee60a8602705835 ***

Author: Patrick Palka <patrick@parcs.ath.cx>
Branch: master
Commit: 2e52ae68e7cedc3a1f9908c98ee60a8602705835

Add tab completion for TUI's "focus" command
The implementation is pretty straightforward, with the only caveat being
that the "src", "cmd", "next" and "prev" entries get delibrately added
to the completion list even when the TUI has not yet been initialized
(i.e. has never been enabled during the session), since invoking the
"focus" command with these arguments already works when the TUI has not
yet been initialized.

gdb/ChangeLog:

	* tui/tui-win.c (focus_completer): New static function.
	(_initialize_tui_win): Set the completion function of the
	"focus" command to focus_completer.

gdb/testsuite/ChangeLog:

	* gdb.base/completion.exp: Test the completion of the "focus"
	command.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Do not skip prologue for asm (.S) files
@ 2015-06-26 13:34 sergiodj+buildbot
  2015-06-26 15:34 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-06-26 13:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6e22494e5076e4d3c0b2c2785883162f83db499e ***

Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Branch: master
Commit: 6e22494e5076e4d3c0b2c2785883162f83db499e

Do not skip prologue for asm (.S) files
GDB tries to skip prologue for .S files according to .debug_line but it then
places the breakpoint to a location where it is never hit.

This is because #defines in .S files cause prologue skipping which is
completely inappropriate, for s390x:

glibc/sysdeps/unix/syscall-template.S
78:/* This is a "normal" system call stub: if there is an error,
79:   it returns -1 and sets errno.  */
80:
81:T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
82:     ret

00000000000f4210 T __select
 Line Number Statements:
  Extended opcode 2: set Address to 0xf41c8
  Advance Line by 80 to 81
  Copy
  Advance PC by 102 to 0xf422e
  Special opcode 6: advance Address by 0 to 0xf422e and Line by 1 to 82
  Special opcode 34: advance Address by 2 to 0xf4230 and Line by 1 to 83
  Advance PC by 38 to 0xf4256
  Extended opcode 1: End of Sequence
  Compilation Unit @ offset 0x28b3e0:
 <0><28b3eb>: Abbrev Number: 1 (DW_TAG_compile_unit)
    <28b3ec>   DW_AT_stmt_list   : 0x7b439
    <28b3f0>   DW_AT_low_pc	 : 0xf41c8
    <28b3f8>   DW_AT_high_pc     : 0xf4256
    <28b400>   DW_AT_name        : ../sysdeps/unix/syscall-template.S
    <28b423>   DW_AT_comp_dir    : /usr/src/debug////////glibc-2.17-c758a686/misc
    <28b452>   DW_AT_producer    : GNU AS 2.23.52.0.1
    <28b465>   DW_AT_language    : 32769        (MIPS assembler)

without debuginfo or with debuginfo and the fix - correct address:
(gdb) b select
Breakpoint 1 at 0xf4210

It is also where .dynsym+.symtab point to:
00000000000f4210 T __select
00000000000f4210 W select

with debuginfo, without the fix:
(gdb) b select
Breakpoint 1 at 0xf41c8: file ../sysdeps/unix/syscall-template.S, line 81.

One part is to behave for asm files similar way like for 'locations_valid':
  /* Symtab has been compiled with both optimizations and debug info so that
     GDB may stop skipping prologues as variables locations are valid already
     at function entry points.  */
  unsigned int locations_valid : 1;

The other part is to extend the 'locations_valid'-like functionality more.

Both minsym_found and find_function_start_sal need to be patched, otherwise
their addresses do not match and GDB regresses on ppc64:

gdb/ChangeLog
2015-06-26  Jan Kratochvil  <jan.kratochvil@redhat.com>

	* linespec.c (minsym_found): Reset sal.PC for COMPUNIT_LOCATIONS_VALID
	and language_asm..
	* symtab.c (find_function_start_sal): Likewise.

gdb/testsuite/ChangeLog
2015-06-26  Jan Kratochvil  <jan.kratochvil@redhat.com>

	* gdb.arch/amd64-prologue-skip.S: New file.
	* gdb.arch/amd64-prologue-skip.exp: New file.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Add support for DT_MIPS_RLD_MAP_REL.
@ 2015-06-26 13:00 sergiodj+buildbot
  2015-06-26 14:00 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-06-26 13:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a5499fa4649e4325cf46edfff2f24dae2fe2afef ***

Author: Matthew Fortune <matthew.fortune@imgtec.com>
Branch: master
Commit: a5499fa4649e4325cf46edfff2f24dae2fe2afef

Add support for DT_MIPS_RLD_MAP_REL.
This tag makes it possible to access the debug map when debugging position
independent executables.

bfd/

	* elfxx-mips.c (_bfd_mips_elf_create_dynamic_sections): Use executable
	instead of !shared to indicate an application vs shared library.
	(_bfd_mips_elf_size_dynamic_sections): Likewise.
	(_bfd_mips_elf_finish_dynamic_sections): Handle DT_MIPS_RLD_MAP_REL.
	(_bfd_mips_elf_get_target_dtag): Likewise.

binutils/

	* readelf.c (get_mips_dynamic_type): Handle DT_MIPS_RLD_MAP_REL.

include/

	* elf/mips.h (DT_MIPS_RLD_MAP_REL): New macro.

ld/testsuite/

	* ld-mips-elf/pic-and-nonpic-3b.ad: Adjust for extra dynamic tag.
	* ld-mips-elf/pic-and-nonpic-4b.ad: Likewise.
	* ld-mips-elf/pic-and-nonpic-5b.ad: Likewise.
	* ld-mips-elf/pic-and-nonpic-6-n32.ad: Likewise.
	* ld-mips-elf/pic-and-nonpic-6-n64.ad: Likewise.
	* ld-mips-elf/pic-and-nonpic-6-o32.ad: Likewise.
	* ld-mips-elf/tlsdyn-o32-1.d: Likewise.
	* ld-mips-elf/tlsdyn-o32-1.got: Likewise.
	* ld-mips-elf/tlsdyn-o32-2.d: Likewise.
	* ld-mips-elf/tlsdyn-o32-2.got: Likewise.
	* ld-mips-elf/tlsdyn-o32-3.d: Likewise.
	* ld-mips-elf/tlsdyn-o32-3.got: Likewise.
	* ld-mips-elf/tlsdyn-o32.d: Likewise.
	* ld-mips-elf/tlsdyn-o32.got: Likewise.
	* ld-mips-elf/pie-n32.d: New file.
	* ld-mips-elf/pie-n64.d: Likewise.
	* ld-mips-elf/pie-o32.d: Likewise.
	* ld-mips-elf/pie.s: Likewise.
	* ld-mips-elf/mips-elf.exp: Add new tests.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Don't set sh_size for .shstrtab twice
@ 2015-06-25 20:28 sergiodj+buildbot
  2015-06-25 23:50 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-06-25 20:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 946748d5ed1d218adfccd523be9fdf280adfe434 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 946748d5ed1d218adfccd523be9fdf280adfe434

Don't set sh_size for .shstrtab twice
_bfd_elf_assign_file_positions_for_non_load will set the sh_size
field for .shstrtab section.  There is need to initialize it in
_bfd_elf_compute_section_file_positions.

	* elf.c (_bfd_elf_compute_section_file_positions): Don't
	initialize sh_size for .shstrtab here.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] py-prettyprint.exp: Add is_address_zero_readable check
@ 2015-06-25 17:56 sergiodj+buildbot
  2015-06-25 21:32 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-06-25 17:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bf7b9cd9aa4645119792e9d1689e0f014f43934f ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: bf7b9cd9aa4645119792e9d1689e0f014f43934f

py-prettyprint.exp: Add is_address_zero_readable check
gdb/testsuite/ChangeLog:

	* gdb.python/py-prettyprint.exp (run_lang_tests): Add
	is_address_zero_readable check.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Correctly notice empty sysroots in solib_find_1
@ 2015-06-25 10:52 sergiodj+buildbot
  2015-06-25 18:09 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-06-25 10:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f8773be1be076f828b93ac3bebeab3f782e191e4 ***

Author: Gary Benson <gbenson@redhat.com>
Branch: master
Commit: f8773be1be076f828b93ac3bebeab3f782e191e4

Correctly notice empty sysroots in solib_find_1
Some parts of solib_find_1 should only operate if the sysroot
is nonempty after processing, but the logic that checked this
happened before trailing slashes were stripped so empty but
non-NULL sysroots were possible.  This commit moves the logic
so it correctly notices all empty sysroots.

gdb/ChangeLog:

	* solib.c (solib_find_1): Set local variable sysroot to NULL if
	it is the empty string after trailing slashes have been stripped.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix lrealpath memory leak in build_id_to_debug_bfd
@ 2015-06-24 21:35 sergiodj+buildbot
  2015-06-25 12:59 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-06-24 21:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 32fad71f9e6cdf73fe3c10123b23f42397b83e7d ***

Author: Keith Seitz <keiths@redhat.com>
Branch: master
Commit: 32fad71f9e6cdf73fe3c10123b23f42397b83e7d

Fix lrealpath memory leak in build_id_to_debug_bfd
Valgrind reports memory leaking from build_id_to_debug_bfd:
==7261== 88 bytes in 2 blocks are definitely lost in loss record 31,319 of 35,132
==7261==    at 0x4A06BCF: malloc (vg_replace_malloc.c:296)
==7261==    by 0x32CA88A9B9: strdup (strdup.c:42)
==7261==    by 0xFE62AB: lrealpath (lrealpath.c:88)
==7261==    by 0x7F7AD6: build_id_to_debug_bfd (build-id.c:116)
==7261==    by 0x7F7BB5: find_separate_debug_file_by_buildid (build-id.c:149)
==7261==    by 0x6D9382: elf_symfile_read (elfread.c:1348)
==7261==    by 0x777F02: read_symbols (symfile.c:875)
==7261==    by 0x778505: syms_from_objfile_1 (symfile.c:1078)
==7261==    by 0x778548: syms_from_objfile (symfile.c:1094)
==7261==    by 0x778746: symbol_file_add_with_addrs (symfile.c:1191)
==7261==    by 0x77893B: symbol_file_add_from_bfd (symfile.c:1280)
==7261==    by 0x8E51E3: solib_read_symbols (solib.c:706)
==7261==    by 0x8E58AF: solib_add (solib.c:1029)

This occurs because commit 1be5090b in bfd, addressing PR 11983, started
taking a copy of the input filename instead of directly caching it.  It
appears that this code was never updated to reflect that API change.

This simple patch creates a cleanup to free the return value for lrealpath.

gdb/ChangeLog

	* build-id.c (build_id_to_debug_bfd): Add cleanup to free
	return value from lrealpath.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Sync libiberty from GCC, replaying updates to configure scripts
@ 2015-06-24 20:10 sergiodj+buildbot
  2015-06-25  9:40 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-06-24 20:10 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f91ca6bc00c1e3c70c1d2f4527d4297b76e2eaca ***

Author: Iain Buclaw <ibuclaw@gdcproject.org>
Branch: master
Commit: f91ca6bc00c1e3c70c1d2f4527d4297b76e2eaca

Sync libiberty from GCC, replaying updates to configure scripts


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] sim: trace: drop unused trace_one_insn
@ 2015-06-24 17:33 sergiodj+buildbot
  2015-06-25  6:14 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-06-24 17:33 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 602a67cbeaf6b42bc513a873aec82e53235b8754 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 602a67cbeaf6b42bc513a873aec82e53235b8754

sim: trace: drop unused trace_one_insn
Everyone has migrated to the split functions (trace_prefix + trace_generic)
a while ago, so we can drop this one now.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] gdb: sim: handle target sysroot prefix
@ 2015-06-24 15:10 sergiodj+buildbot
  2015-06-24 17:55 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-06-24 15:10 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 23bf70af12aa0c14e79c02b6098117bdba8c8a3a ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 23bf70af12aa0c14e79c02b6098117bdba8c8a3a

gdb: sim: handle target sysroot prefix
The default gdb sysroot now sets itself to "target:".  This works for
most remote targets, but when using the simulator, this causes problems
as the sim will attempt to search for that path.

Update the remote-sim logic to skip this leading prefix when it is found
so that the sysroot isn't passed in as an invalid value.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Call set_gdbarch_get_siginfo_type in linux_init_abi
@ 2015-06-24 14:45 sergiodj+buildbot
  2015-06-24 16:47 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-06-24 14:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5cd867b414fe3609dbf596c373343474132775a8 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 5cd867b414fe3609dbf596c373343474132775a8

Call set_gdbarch_get_siginfo_type in linux_init_abi
linux_get_siginfo_type is installed to many linux gdbarch.  This patch
is to move this to a common area linux-tdep.c:linux_init_abi, so that
linux_get_siginfo_type is installed to every linux gdbarch.  If some
linux gdbarch needs its own version, please override it in
$ARCH_linux_init_abi.  In the testsuite, we enable siginfo related
tests for all linux targets.

gdb:

2015-06-24  Yao Qi  <yao.qi@linaro.org>

	* aarch64-linux-tdep.c (aarch64_linux_init_abi): Don't call
	set_gdbarch_get_siginfo_type.
	* amd64-linux-tdep.c (amd64_linux_init_abi_common): Likewise.
	* arm-linux-tdep.c (arm_linux_init_abi): Likewise.
	* i386-linux-tdep.c (i386_linux_init_abi): Likewise.
	* m68klinux-tdep.c (m68k_linux_init_abi): Likewise.
	* ppc-linux-tdep.c (ppc_linux_init_abi): Likewise.
	* s390-linux-tdep.c (s390_gdbarch_init): Likewise.
	* tilegx-linux-tdep.c (tilegx_linux_init_abi): Likewise.
	* linux-tdep.c (linux_get_siginfo_type): Change it to static.
	(linux_init_abi): Call set_gdbarch_get_siginfo_type.
	* linux-tdep.h (linux_get_siginfo_type): Remove the declaration.

gdb/testsuite:

2015-06-24  Yao Qi  <yao.qi@linaro.org>

	* lib/gdb.exp (supports_get_siginfo_type): Return 1 for all
	linux targets.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] sim: common: replace SIM_FILTER_PATH with lbasename
@ 2015-06-23 22:31 sergiodj+buildbot
  2015-06-24  7:26 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-06-23 22:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e750549018d67d545bdaf90cc058f97b954600cc ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: e750549018d67d545bdaf90cc058f97b954600cc

sim: common: replace SIM_FILTER_PATH with lbasename
This helper macro has largely the same behavior as libiberty's lbasename.
There is a slight nuance related to colons, but it's not clear what the
point of that is, and the code implies that it just wants the basename.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix GDBHISTSIZE test failure on i686
@ 2015-06-23 22:27 sergiodj+buildbot
  2015-06-24  8:02 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-06-23 22:27 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0fc26cafacfff9f53d898bb73495b384b80d6d31 ***

Author: Patrick Palka <patrick@parcs.ath.cx>
Branch: master
Commit: 0fc26cafacfff9f53d898bb73495b384b80d6d31

Fix GDBHISTSIZE test failure on i686
The test

  test_histsize_history_setting "99999999999999999999999999999999999" "unlimited"

was failing on i686 because the condition in init_history() for
determining whether to map a large GDBHISTSIZE value to infinity was

  long var = strtol (tmpenv);
  if (var > INT_MAX)
    history_size = unlimited;

but this condition is never true on i686 because INT_MAX == LONG_MAX.
So in order to properly map large out-of-range values of GDBHISTSIZE to
infinity on targets where LONG_MAX > INT_MAX as well as on i686, we have
to instead change the above condition to

  if (var > INT_MAX
      || (var == INT_MAX && errno == ERANGE))
    history_size = unlimited;

gdb/ChangeLog:

	* top.c (init_history): Look at errno after calling strtol to
	properly map large GDBHISTSIZE values to infinity.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] sim: trace: do not enable internal debug by default
@ 2015-06-23 20:03 sergiodj+buildbot
  2015-06-23 21:58 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-06-23 20:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4953dc20941a48eed02b575cec29d8de419f87eb ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 4953dc20941a48eed02b575cec29d8de419f87eb

sim: trace: do not enable internal debug by default
Since --trace-debug is for people hacking on the sim sources rather than
people just using the sim, default it to off.  This matches the behavior
of other debug knobs we have.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] sim: assume recentish compiler/systems
@ 2015-06-23 19:10 sergiodj+buildbot
  2015-06-23 20:28 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-06-23 19:10 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b50a153264dae2267e3846772819515c648e3c97 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: b50a153264dae2267e3846772819515c648e3c97

sim: assume recentish compiler/systems
Assume the build system supports stdint.h/stdarg.h as those have been
around long enough and we don't care about pre-stdc compilers anymore.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] gdb: microblaze: delete useless stubs
@ 2015-06-23 14:06 sergiodj+buildbot
  2015-06-23 16:27 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-06-23 14:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7564fe458c2fe1a77eecfaf5e2f99bec8961d457 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 7564fe458c2fe1a77eecfaf5e2f99bec8961d457

gdb: microblaze: delete useless stubs
These don't accomplish anything the common core doesn't already, so
punt them as they purely waste code.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Convert have_ptrace_getregset to a tri-state boolean
@ 2015-06-23 13:26 sergiodj+buildbot
  2015-06-23 14:40 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-06-23 13:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0bdb2f78497a1b3be65d1428cc02f7d4e1d3a888 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 0bdb2f78497a1b3be65d1428cc02f7d4e1d3a888

Convert have_ptrace_getregset to a tri-state boolean
have_ptrace_getregset is a tri-state variable (-1, 0, 1), and we have
some conditions like "if (have_ptrace_getregset)", which is not correct.
I'll explain why it is not correct in the following example.  This fix
to this problem to replace the test (have_ptrace_getregset) to test
(have_ptrace_getregset == 1) or (have_ptrace_getregset == -1) etc.
However Doug thinks it hinders readability
https://sourceware.org/ml/gdb-patches/2015-05/msg00692.html so I decide
to add a new enum tribool and change have_ptrace_getregset to it, in
order to make these tests more readable.

have_ptrace_getregset is initialised to -1, and is adjusted to 0 or 1 in
$ARCH_linux_read_description according to the capability of the kernel.
However, it is possible that have_ptrace_getregset is used before it is
set to 0 or 1, which means it is still -1.  This is shown below.

(gdb) run
Starting program: gdb/testsuite/gdb.base/break

Breakpoint 2, amd64_linux_fetch_inferior_registers (ops=0xceaa80, regcache=0xe72000, regnum=16) at git/gdb/amd64-linux-nat.c:128
128	{
top?p have_ptrace_getregset
$1 = TRIBOOL_UNKNOWN
top?c
Continuing.

Breakpoint 2, amd64_linux_fetch_inferior_registers (ops=0xceaa80, regcache=0xe72000, regnum=16) at git/gdb/amd64-linux-nat.c:128
128	{
top?c
Continuing.

Breakpoint 1, x86_linux_read_description (ops=0xceaa80) at git/gdb/x86-linux-nat.c:117
117	{

PTRACE_GETREGSET command is used even GDB doesn't know whether
PTRACE_GETREGSET is supported or not.  It is wrong, but works on x86.
However it doesn't work on arm-linux if the kernel doesn't support
PTRACE_GETREGSET at all.  We'll get:

(gdb) run
Starting program: gdb/testsuite/gdb.base/break
warning: Unable to fetch general register.
PC register is not available

gdb:

2015-06-23  Yao Qi  <yao.qi@linaro.org>

	* amd64-linux-nat.c (amd64_linux_fetch_inferior_registers):
	Check whether have_ptrace_getregset is TRIBOOL_TRUE explicitly.
	(amd64_linux_store_inferior_registers): Likewise.
	* arm-linux-nat.c (fetch_fpregister): Likewise.
	(fetch_fpregs, store_fpregister): Likewise.
	(store_fpregister, store_fpregs): Likewise.
	(fetch_register, fetch_regs): Likewise.
	(store_register, store_regs): Likewise.
	(fetch_vfp_regs, store_vfp_regs): Likewise.
	(arm_linux_read_description): Check have_ptrace_getregset is
	TRIBOOL_UNKNOWN.  Set have_ptrace_getregset to TRIBOOL_TRUE
	or TRIBOOL_FALSE.
	* i386-linux-nat.c (fetch_xstateregs): Check
	have_ptrace_getregset is not TRIBOOL_TRUE.
	(store_xstateregs): Likewise.
	* linux-nat.c (have_ptrace_getregset): Change its type to
	enum tribool.
	* linux-nat.h (tribool): New enum.
	* x86-linux-nat.c (x86_linux_read_description): Use enum tribool.
	Check whether have_ptrace_getregset is TRIBOOL_TRUE.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [AArch64] Generate DT_TEXTREL for relocation against read-only section
@ 2015-06-23 11:38 sergiodj+buildbot
  2015-06-23 13:23 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-06-23 11:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c217058957a45a93481da35e1531ed120750d739 ***

Author: Jiong Wang <jiong.wang@arm.com>
Branch: master
Commit: c217058957a45a93481da35e1531ed120750d739

[AArch64] Generate DT_TEXTREL for relocation against read-only section
2015-06-23  Jiong Wang  <jiong.wang@arm.com>

  bfd/
    * elfnn-aarch64.c (aarch64_readonly_dynrelocs): New function.
    (elfNN_aarch64_size_dynamic_sections): Traverse hash table to check
    relocations against read-only sections.

  ld/testsuite/
    * ld-aarch64/dt_textrel.s: New testcase.
    * ld-aarch64/dt_textrel.d: New expectation file.
    * ld-aarch64/aarch64-elf.exp: Run new testcase.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Stop "objdump -d" from disassembling past a symbolic address.
@ 2015-06-22 16:34 sergiodj+buildbot
  2015-06-22 17:50 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-06-22 16:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bdc4de1b24353c4213e404029252ec75065499de ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: bdc4de1b24353c4213e404029252ec75065499de

Stop "objdump -d" from disassembling past a symbolic address.
include	* dis-asm.h (struct disassemble_info): Add stop_vma field.

binuti  * objdump.c (disassemble_bytes): Set the stop_vma field in the
	disassemble_info structure when disassembling code sections with
	-d.
	* doc/binutils.texi (objdump): Document the discrepancy between -d
	and -D.

opcodes	* dis-buf.c (buffer_read_memory): Fail is stop_vma is set and the
	requested region lies beyond it.
	* bfin-dis.c (print_insn_bfin): Ignore sysop instructions when
	looking for 32-bit insns.
	* mcore-dis.c (print_insn_mcore): Disable stop_vma when reading
	data.
	* sh-dis.c (print_insn_sh): Likewise.
	* tic6x-dis.c (print_insn_tic6x): Disable stop_vma when reading
	blocks of instructions.
	* vax-dis.c (print_insn_vax): Check that the requested address
	does not clash with the stop_vma.

tests	* gas/arm/backslash-at.s: Add extra .byte directives so that the
	foo symbol does not appear to point half way through an
	instruction.
	* gas/arm/backslash-at.d: Update expected disassembly.
	* gas/i386/ilp32/x86-64-opcode-inval-intel.d: Likewise.
	* gas/i386/ilp32/x86-64-opcode-inval.d: Likewise.
	* gas/i386/x86-64-opcode-inval-intel.d: Likewise.
	* gas/i386/x86-64-opcode-inval.d: Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Don't skip hw breakpoint/watchpoint tests for aarch64 target
@ 2015-06-22 13:09 sergiodj+buildbot
  2015-06-22 14:14 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-06-22 13:09 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 52042a003f3e9200c992bc5cf4607dc7655b1f7b ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 52042a003f3e9200c992bc5cf4607dc7655b1f7b

Don't skip hw breakpoint/watchpoint tests for aarch64 target
This patch is to let skip_hw_breakpoint_tests and skip_hw_watchpoint_tests
return 0 for aarch64 target, since aarch64 has HW watchpoint and
breakpoint registers.

With this patch applied, about 1560 watchpoint/breakpoint related tests
become enabled on aarch64-linux native testing.

gdb/testsuite:

2015-06-22  Yao Qi  <yao.qi@linaro.org>

	* lib/gdb.exp (skip_hw_breakpoint_tests): Return 0 for target
	aarch64*-*-*.
	(skip_hw_watchpoint_tests): Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] sim: common: use standard intXX_t types for signedXX
@ 2015-06-21 18:58 sergiodj+buildbot
  2015-06-21 20:37 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-06-21 18:58 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f55b33d51b056c665568c6204bd3ced7f1ec15c8 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: f55b33d51b056c665568c6204bd3ced7f1ec15c8

sim: common: use standard intXX_t types for signedXX
Let's assume that the system supports the POSIX int8/16/32/64_t types
as this collapses the logic significantly.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] sim: common: standardize multiple include defines
@ 2015-06-21 17:56 sergiodj+buildbot
  2015-06-21 18:58 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-06-21 17:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 618b526e31d3df71e9526a0753271624a568564e ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 618b526e31d3df71e9526a0753271624a568564e

sim: common: standardize multiple include defines
We use SIM_xxx_H in most headers, so convert _SIM_xxx_H_ over to it.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Allow for optional operands with non-zero default values.
@ 2015-06-19 22:42 sergiodj+buildbot
  2015-06-19 23:57 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-06-19 22:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 11a0cf2ec0ed6e70ff25e9a50c2223dcd98c1c10 ***

Author: Peter Bergner <bergner@vnet.ibm.com>
Branch: master
Commit: 11a0cf2ec0ed6e70ff25e9a50c2223dcd98c1c10

Allow for optional operands with non-zero default values.
ISA 2.07 (ie, POWER8) added the rfebb instruction which takes one operand
with the value of either a 0 or 1.  It also defines an extended mnemonic
with no operands (ie, "rfebb") that is supposed to be equivalent to "rfebb 1".
I implemented rfebb's lone operand with PPC_OPERAND_OPTIONAL, but the
problem is, optional operands that are ommitted always default to the
value 0, which is wrong in this case.  I have added support for allowing
non-zero default values by adding an additional flag PPC_OPERAND_OPTIONAL_VALUE
that specifies that the default operand value to be used is stored in the
SHIFT field of the operand field immediately following this one.

This fixes the rfebb issue.  I also fixed the mftb and mfcr instructions
so they use the same mechanism.  This allows us to flag invalid uses of
mfcr where we explicitly pass in a zero FXM value, like the use in a2.[sd].

include/opcode/

	* ppc.h (PPC_OPERAND_OPTIONAL_VALUE): New.
	(ppc_optional_operand_value): New inline function.

opcodes/
	* ppc-dis.h (skip_optional_operands): Use ppc_optional_operand_value.
	* ppc-opc.c (FXM4): Add non-zero optional value.
	(TBR): Likewise.
	(SXL): Likewise.
	(insert_fxm): Handle new default operand value.
	(extract_fxm): Likewise.
	(insert_tbr): Likewise.
	(extract_tbr): Likewise.

gas/
	* config/tc-ppc.c (md_assemble): Use ppc_optional_operand_value.
	Allow for optional operands without insert functions.

gas/testsuite/
	* gas/ppc/power8.d: Fixup rfebb test results.
	* gas/ppc/a2.s: Fix invalid mfcr test.
	* gas/ppc/a2.d: Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Remove special support in gdb for Sun's version of stabs.
@ 2015-06-19 19:00 sergiodj+buildbot
  2015-06-19 20:01 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-06-19 19:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 18a94d75a0a9baca8e2db2563fa3e637415ad86e ***

Author: Doug Evans <dje@google.com>
Branch: master
Commit: 18a94d75a0a9baca8e2db2563fa3e637415ad86e

Remove special support in gdb for Sun's version of stabs.
Discussion:
https://sourceware.org/ml/gdb-patches/2015-05/msg00169.html

gdb/ChangeLog:

	* NEWS: Mention Sun's version of stabs is no longer supported.
	* elfread.c (free_elfinfo): Delete.  All uses updated.
	(elfstab_offset_sections): Delete.  All uses updated.
	* gdb-stabs.h (stab_section_info): Delete.  All uses updated.
	* psympriv.h (partial_symtab) <section_offsets>: Delete.
	All uses updated.
	* psymtab.c (start_psymtab_common): Delete arg section_offsets.
	All callers updated.

gdb/doc/ChangeLog:

	* stabs.texinfo (ELF Linker Relocation): Mention Sun stabs is no
	longer supported.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] remote: consider addressable unit size when reading/writing memory
@ 2015-06-18 17:40 sergiodj+buildbot
  2015-06-18 20:07 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-06-18 17:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 124e13d9e753ef307d6fe478e2cd6dd738de1a0f ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: 124e13d9e753ef307d6fe478e2cd6dd738de1a0f

remote: consider addressable unit size when reading/writing memory
Adapt code in remote.c to take into account addressable unit size when
reading/writing memory.

A few variables are renamed and suffixed with _bytes or _units. This
way, it's more obvious if there is any place where we add or compare
values of different kinds (which would be a mistake).

gdb/ChangeLog:

	* common/rsp-low.c (needs_escaping): New.
	(remote_escape_output): Add unit_size parameter. Refactor to
	support multi-byte addressable units.  Rename parameters.
	* common/rsp-low.h (remote_escape_output): Add unit_size
	parameter and rename others. Update doc.
	* remote.c (align_for_efficient_write): New.
	(remote_write_bytes_aux): Add unit_size parameter and use it.
	Rename some variables.  Update doc.
	(remote_xfer_partial): Get unit size and use it.
	(remote_read_bytes_1): Add unit_size parameter and use it.
	Rename some variables. Update doc.
	(remote_write_bytes): Same.
	(remote_xfer_live_readonly_partial): Same.
	(remote_read_bytes): Same.
	(remote_flash_write): Update call to remote_write_bytes_aux.
	(remote_write_qxfer): Update call to remote_escape_output.
	(remote_search_memory): Same.
	(remote_hostio_pwrite): Same.

gdb/gdbserver/ChangeLog:

	* server.c (write_qxfer_response): Update call to
	remote_escape_output.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Test the interaction between GDBHISTSIZE and .gdbinit
@ 2015-06-18 17:01 sergiodj+buildbot
  2015-06-18 18:33 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-06-18 17:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 74bd41ce65c6c2c30ff67519bfc1d00b61826d96 ***

Author: Patrick Palka <patrick@parcs.ath.cx>
Branch: master
Commit: 74bd41ce65c6c2c30ff67519bfc1d00b61826d96

Test the interaction between GDBHISTSIZE and .gdbinit
The value inside the GDBHISTSIZE environment variable, only if valid,
should override setting the history size through one's .gdbinit file.

gdb/testsuite/ChangeLog:

	* gdb.base/gdbinit-history.exp: Test the interaction between
	setting GDBHISTSIZE and setting the history size via .gdbinit.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] sim: syscall: simplify unknown syscall trace
@ 2015-06-18  9:00 sergiodj+buildbot
  2015-06-18 14:35 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-06-18  9:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 57b42d6489218e29cb18edd111c97f4390b62ad9 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 57b42d6489218e29cb18edd111c97f4390b62ad9

sim: syscall: simplify unknown syscall trace
Since we always include the raw syscall number when tracing, also
including it in the name when it's unknown is redundant.  Simplify
the code by using a constant string.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Tweak the handling of $GDBHISTSIZE edge cases [PR gdb/16999]
@ 2015-06-17 21:32 sergiodj+buildbot
  2015-06-18  8:17 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-06-17 21:32 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bc460514b9db46a491c2c39cd118b02608742968 ***

Author: Patrick Palka <patrick@parcs.ath.cx>
Branch: master
Commit: bc460514b9db46a491c2c39cd118b02608742968

Tweak the handling of $GDBHISTSIZE edge cases [PR gdb/16999]
When GDB reads a nonsensical value for the GDBHISTSIZE environment
variable, i.e. one that is non-numeric or negative, GDB then sets its
history size to 0.  This behavior is annoying and also inconsistent
with the behavior of bash.

This patch makes the behavior of invalid GDBHISTSIZE consistent with how
bash handles HISTSIZE.  When we encounter a null or out-of-range
GDBHISTSIZE (outside of [0, INT_MAX]) we now set the history size to
unlimited instead of 0.  When we encounter a non-numeric GDBHISTSIZE we
do nothing.

gdb/ChangeLog:

	PR gdb/16999
	* NEWS: Mention new GDBHISTSIZE behavior.
	* top.c (init_history): For null or out-of-range GDBHISTSIZE,
	set history size to unlimited.  Ignore non-numeric GDBHISTSIZE.

gdb/doc/ChangeLog:

	PR gdb/16999
	* gdb.texinfo (Command History): Mention new GDBHISTSIZE
	behavior.

gdb/testsuite/ChangeLog:

	PR gdb/16999
	* gdb.base/gdbhistsize-history.exp: New test.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Read $GDBHISTSIZE instead of $HISTSIZE
@ 2015-06-17 20:35 sergiodj+buildbot
  2015-06-18  6:18 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-06-17 20:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b58c513b7932cfb9852d66e07282b9c2379197ed ***

Author: Patrick Palka <patrick@parcs.ath.cx>
Branch: master
Commit: b58c513b7932cfb9852d66e07282b9c2379197ed

Read $GDBHISTSIZE instead of $HISTSIZE
The HISTSIZE environment variable is generally expected to be read by
shells, not by applications.  Some distros for example globally export
HISTSIZE in /etc/profile -- with the intention that it only affects
shells -- and by doing so it renders useless GDB's own mechanism for
setting the history size via .gdbinit.  Also, annoyances may arise when
HISTSIZE is not interpreted the same way by the shell and by GDB, e.g.
PR gdb/16999.  That can always be fixed on a shell-by-shell basis but it
may be impossible to be consistent with the behavior of all shells at
once.  Finally it just makes sense to not confound shell environment
variables with application environment variables.

gdb/ChangeLog:

	* NEWS: Mention that GDBHISTSIZE is read instead of HISTSIZE.
	* top.c (init_history): Read from GDBHISTSIZE instead of
	HISTSIZE.
	(init_main): Refer to GDBHISTSIZE instead of HISTSIZE.

gdb/doc/ChangeLog:

	* gdb.texinfo (Command History): Replace occurrences of HISTSIZE
	with GDBHISTSIZE.

gdb/testsuite/ChangeLog:

	* gdb.base/gdbinit-history.exp: Replace occurrences of HISTSIZE
	with GDBHISTSIZE.
	* gdb.base/readline.exp: Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Remove unused function make_breakpoint_permanent.
@ 2015-06-17 20:32 sergiodj+buildbot
  2015-06-18  9:48 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-06-17 20:32 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT da4616f69f53c221477388b6f2d4abee9bba0722 ***

Author: Luis Machado <lgustavo@codesourcery.com>
Branch: master
Commit: da4616f69f53c221477388b6f2d4abee9bba0722

Remove unused function make_breakpoint_permanent.
make_breakpoint_permanent is no longer used anywhere and can be
safely removed.

gdb/ChangeLog:

2015-06-17  Luis Machado  <lgustavo@codesourcery.com>

	* breakpoint.c (make_breakpoint_permanent): Remove unused
	function.
	* breakpoint.h (make_breakpoint_permanent): Remove declaration.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] sim: syscall: unify memory helpers
@ 2015-06-17 18:39 sergiodj+buildbot
  2015-06-17 21:31 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-06-17 18:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 61a0c964e611eaf72489c3049ba206b2f91ea4a9 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 61a0c964e611eaf72489c3049ba206b2f91ea4a9

sim: syscall: unify memory helpers
Almost every port implements these two callbacks in the same way, so
unify them in the common layer.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] sim: callback: add human readable strings for debugging to maps
@ 2015-06-17 17:40 sergiodj+buildbot
  2015-06-17 19:46 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-06-17 17:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6362a3f8757bfce133b724df2077573433823ad4 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 6362a3f8757bfce133b724df2077573433823ad4

sim: callback: add human readable strings for debugging to maps
When tracing, we often want to display the human readable name for the
various syscall/errno values.  Rather than make each target duplicate
the lookup, extend the existing maps to include the string directly,
and add helper functions to look up the constants.

While most targets are autogenerated (from libgloss), the bfin/cris
targets have custom maps for the Linux ABI which need to be updated
by hand.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Don't truncate the history file when history size is unlimited
@ 2015-06-17 14:12 sergiodj+buildbot
  2015-06-17 14:39 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-06-17 14:12 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2093d2d31460dc351145c4c295ea4a101e0c5aed ***

Author: Patrick Palka <patrick@parcs.ath.cx>
Branch: master
Commit: 2093d2d31460dc351145c4c295ea4a101e0c5aed

Don't truncate the history file when history size is unlimited
We still do not handle "set history size unlimited" correctly.  In
particular, after writing to the history file, we truncate the history
even if it is unlimited.

This patch makes sure that we do not call history_truncate_file() if the
history is not stifled (i.e. if it's unlimited).  This bug causes the
history file to be truncated to zero on exit when one has "set history
size unlimited" in their gdbinit file.  Although this code exists in GDB
7.8, the bug is masked by a pre-existing bug that's been only fixed in
GDB 7.9 (PR gdb/17820).

gdb/ChangeLog:

	* top.c (gdb_safe_append_history): Do not call
	history_truncate_file if the history is not stifled.

gdb/testsuite/ChangeLog:

	* gdb.base/gdbinit-history.exp: Add test case to check that
	an unlimited history file does not get truncated on exit.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] S390: Add syscall info for syscalls from 344 up to 354
@ 2015-06-17 10:18 sergiodj+buildbot
  2015-06-17 12:54 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-06-17 10:18 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fc2484855563d0cd3e43b9f2d937481b5f5e4a7b ***

Author: Andreas Arnez <arnez@linux.vnet.ibm.com>
Branch: master
Commit: fc2484855563d0cd3e43b9f2d937481b5f5e4a7b

S390: Add syscall info for syscalls from 344 up to 354
Represent new Linux syscalls for s390 and s390x in GDB's syscall info.
Add the syscalls from 344 (finit_module) up to 354 (execveat).

gdb/ChangeLog:

	* syscalls/s390-linux.xml: Add syscalls 344 through 354.
	* syscalls/s390x-linux.xml: Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Add vector ABI tests to gnu_vector.exp
@ 2015-06-17  9:39 sergiodj+buildbot
  2015-06-17 10:38 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-06-17  9:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e6c693af14c0488998a784d560b8cfbcf15db99a ***

Author: Andreas Arnez <arnez@linux.vnet.ibm.com>
Branch: master
Commit: e6c693af14c0488998a784d560b8cfbcf15db99a

Add vector ABI tests to gnu_vector.exp
So far the gnu_vector test was limited to "static" aspects of GDB's
vector support, like evaluating vector-valued expressions.  This patch
enriches the test and adds checks for GDB's vector ABI support as well.
The new checks particularly verify inferior function calls with vector
arguments and GDB's handling of vector return values.

The test now attempts to compile for the target's "native" architecture,
such that a hardware vector ABI is used if available.

Since GDB has no vector ABI support for x86 and x86_64 targets, most of
the new checks are KFAILed there.

gdb/testsuite/ChangeLog:

	* gdb.base/gnu_vector.c: Include stdarg.h and stdio.h.
	(VECTOR): New macro.  Use it...
	(int4, uint4, char4, float4, int2, longlong2, float2, double2):
	...for these typedefs.
	(int8, char1, int1, double1): New typedefs.
	(struct just_int2, struct two_int2): New structures.
	(add_some_intvecs, add_many_charvecs, add_various_floatvecs)
	(add_structvecs, add_singlevecs): New functions.
	(main): Call add_some_intvecs twice.
	* gdb.base/gnu_vector.exp: Drop GCC version check; just attempt
	the compile and exit upon failure.  Try compiling for the "native"
	architecture.  Test inferior function calls with vector arguments
	and vector return value handling with "finish" and "return".


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] GDB Namespaces - Define MSG_CMSG_CLOEXEC if not defined.
@ 2015-06-16 16:49 sergiodj+buildbot
  2015-06-16 21:15 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-06-16 16:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4da680addb9f9c22f24f0294b8b9b9ca52cecd7f ***

Author: Michael Eager <eager@eagercon.com>
Branch: master
Commit: 4da680addb9f9c22f24f0294b8b9b9ca52cecd7f

GDB Namespaces - Define MSG_CMSG_CLOEXEC if not defined.
2015-06-16  Michael Eager  <eager@eagercon.com>

	* nat/linux-namespaces.c (MSG_CMSG_CLOEXEC): Define if not defined.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix build when size_t is not available in bfd-in2.h
@ 2015-06-16 13:55 sergiodj+buildbot
  2015-06-16 16:06 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-06-16 13:55 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 56f4083249f4633084d4e8d89fc065e895f874cf ***

Author: Jon Turney <jon.turney@dronecode.org.uk>
Branch: master
Commit: 56f4083249f4633084d4e8d89fc065e895f874cf

Fix build when size_t is not available in bfd-in2.h
bfd/ChangeLog:

2015-06-15  Jon Turney  <jon.turney@dronecode.org.uk>

	* bfd.c: Change struct bfd_build_id to use bfd_size_type.
	* bfd-in2.h : Regenerate.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fixes a compile time warnng about left shifting a negative value.
@ 2015-06-16 12:56 sergiodj+buildbot
  2015-06-16 13:55 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-06-16 12:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 24b4cf66a626566e7903813a2e0156778f4903f9 ***

Author: Szabolcs Nagy <szabolcs.nagy@arm.com>
Branch: master
Commit: 24b4cf66a626566e7903813a2e0156778f4903f9

Fixes a compile time warnng about left shifting a negative value.
	* arm-dis.c (print_insn_coprocessor): Avoid negative shift.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] MI: consider addressable unit size when reading/writing memory
@ 2015-06-15 20:11 sergiodj+buildbot
  2015-06-16  1:21 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-06-15 20:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cfc32360afdc8605b2dd2062e857313e62c40e30 ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: cfc32360afdc8605b2dd2062e857313e62c40e30

MI: consider addressable unit size when reading/writing memory
As a user of the target memory read/write interface, the MI code must
adjust its memory allocations to take into account the addressable memory
unitsize of the target.

gdb/ChangeLog:

	mi/mi-main.c (mi_cmd_data_read_memory_bytes): Consider byte
	size.
	(mi_cmd_data_write_memory_bytes): Same.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Cleanup write_memory doc
@ 2015-06-15 18:19 sergiodj+buildbot
  2015-06-15 23:47 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-06-15 18:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cb6f16cf4f7a12f9aadddc0451d47f0511729c8d ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: cb6f16cf4f7a12f9aadddc0451d47f0511729c8d

Cleanup write_memory doc
This doc about write_memory seems outdated.

gdb/ChangeLog:

	* corefile.c (write_memory): Update doc.
	* gdbcore.h (write_memory): Same.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Merge multiple hex conversions
@ 2015-06-15 16:18 sergiodj+buildbot
  2015-06-15 20:10 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-06-15 16:18 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 909c2cdaa78f5c33ce61a3b47e86f831025d0a02 ***

Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Branch: master
Commit: 909c2cdaa78f5c33ce61a3b47e86f831025d0a02

Merge multiple hex conversions
gdb/ChangeLog
2015-06-15  Aleksandar Ristovski  <aristovski@qnx.com
	    Jan Kratochvil  <jan.kratochvil@redhat.com>

	Merge multiple hex conversions.
	* monitor.c: Include rsp-low.h.
	(fromhex): Remove definition.

gdb/gdbserver/ChangeLog
2015-06-15  Aleksandar Ristovski  <aristovski@qnx.com
	    Jan Kratochvil  <jan.kratochvil@redhat.com>

	Merge multiple hex conversions.
	* gdbreplay.c (tohex): Rename to 'fromhex'.
	(logchar): Use fromhex.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Move utility functions to common/
@ 2015-06-15 15:24 sergiodj+buildbot
  2015-06-15 18:13 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-06-15 15:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 03aef70fecec83e109c65337a59600ad36def6bf ***

Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Branch: master
Commit: 03aef70fecec83e109c65337a59600ad36def6bf

Move utility functions to common/
gdb/ChangeLog
2015-06-15  Aleksandar Ristovski  <aristovski@qnx.com
	    Jan Kratochvil  <jan.kratochvil@redhat.com>

	Move utility functions to common/.
	* cli/cli-utils.c (skip_spaces, skip_spaces_const, skip_to_space_const):
	Move defs to common/common-utils.c.
	* cli/cli-utils.h (skip_spaces, skip_spaces_const, skip_to_space)
	(skip_to_space_const): Move decls to common/common-utils.h.
	* common/common-defs.h: Move include of common-types.h before
	common-utils.h.
	* common/common-utils.c: Include host-defs.h and ctype.h.
	(HIGH_BYTE_POSN, is_digit_in_base, digit_to_int, strtoulst): Move
	from utils.c.
	(skip_spaces, skip_spaces_const, skip_to_space_const): Move from
	cli/cli-utils.c.
	* common/common-utils.h (strtoulst): Move decl from utils.h.
	(skip_spaces, skip_spaces_const, skip_to_space, skip_to_space_const):
	Move from cli/cli-utils.h.
	* common/host-defs.h: Include limits.h.
	(TARGET_CHAR_BIT, HOST_CHAR_BIT): Moved from defs.h.
	(skip_spaces, skip_spaces_const): Move decls from cli/cli-utils.h.
	* defs.h (TARGET_CHAR_BIT, HOST_CHAR_BIT): Move to
	common/common-utils.h.
	* utils.c (HIGH_BYTE_POSN, is_digit_in_base, digit_to_int)
	(strtoulst): Move to common/common-utils.c.
	* utils.h (strtoulst): Moved decl to common/common-utils.h.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Copy aarch64-linux.xml to build tree.
@ 2015-06-15 13:23 sergiodj+buildbot
  2015-06-15 16:35 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-06-15 13:23 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d1168cc1a9825b96747440b0bd1f82c4498e6343 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: d1168cc1a9825b96747440b0bd1f82c4498e6343

Copy aarch64-linux.xml to build tree.
This patch fixes a bug that aarch64-linux.xml isn't copied to the
build tree, so that some tests catch-syscall.exp fail.

gdb:

2015-06-15  Yao Qi  <yao.qi@linaro.org>

	* data-directory/Makefile.in (SYSCALLS_FILES): Add aarch64-linux.xml.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Allow gdb to find debug symbols file by build-id for PE file format also
@ 2015-06-15 12:26 sergiodj+buildbot
  2015-06-15 15:02 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-06-15 12:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c74f7d1c6c5a968330208757f476c67a4bb66643 ***

Author: Jon Turney <jon.turney@dronecode.org.uk>
Branch: master
Commit: c74f7d1c6c5a968330208757f476c67a4bb66643

Allow gdb to find debug symbols file by build-id for PE file format also
This promotes BFD's struct elf_build_id to the generic struct bfd_build_id,
populated when an ELF or PE BFD is read.

gdb is updated to use that, and to use the build-id to find symbols for PE files
also.

There is currently no generic way to extract the build-id from an object file,
perhaps an option to objdump to do this might make sense?

On x86_64-pc-cygwin, gdb's sepdebug.exp changes:

-# of unsupported tests          1
+# of expected passes            90

I don't seem to get consistent testsuite runs on i686-linux-gnu, but there
don't appear to be any regressions.

bfd/ChangeLog:

2015-06-10  Jon Turney  <jon.turney@dronecode.org.uk>

	* elf-bfd.h : Remove struct elf_build_id.
	* bfd.c : Add struct bfd_build_id.
	* bfd-in2.h: Regenerate.
	* elf.c (elfobj_grok_gnu_build_id): Update to use bfd_build_id.
	* libpei.h: Add protoype and macros for
	bfd_XXi_slurp_codeview_record.
	* peXXigen.c (_bfd_XXi_slurp_codeview_record): Make public
	* peicode.h (pe_bfd_read_buildid): Add.
	(pe_bfd_object_p): Use pe_bfd_read_buildid().

gdb/ChangeLog:

2015-06-10  Jon Turney  <jon.turney@dronecode.org.uk>

	* build-id.c: Don't include elf-bfd.h.
	(build_id_bfd_get): Use bfd_build_id.
	(build_id_verify): Ditto.
	* build-id.h: Ditto.
	(find_separate_debug_file_by_buildid): Ditto.
	* python/py-objfile.c: Don't include elf-bfd.h.
	(objfpy_get_build_id) Use bfd_build_id.
	(objfpy_build_id_matches, objfpy_lookup_objfile_by_build_id): Ditto.
	* coffread.c: Include build-id.h.
	(coff_symfile_read): Try find_separate_debug_file_by_buildid.

gdb/doc/ChangeLog:

2015-06-10  Jon Turney  <jon.turney@dronecode.org.uk>

	* gdb.texinfo (Separate Debug Files): Document that PE is also
	supported.

gdb/testsuite/ChangeLog:

2015-06-10  Jon Turney  <jon.turney@dronecode.org.uk>

	* gdb.base/sepdebug.exp: Add EXEEXT where needed.
	* lib/gdb.exp (get_build_id): Teach how to extract build-id from a
	PE file.
	* lib/future.exp (gdb_find_objdump): Add gdb_find_objdump.

Signed-off-by: Jon Turney <jon.turney@dronecode.org.uk>


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [AArch64] Gas add BFD_RELOC_AARCH64_LD64_GOTOFF_LO15 support
@ 2015-06-15 10:31 sergiodj+buildbot
  2015-06-15 11:37 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-06-15 10:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 87f5fbcc7aa49cee13e9ed44587b80d695d7e781 ***

Author: Renlin Li <renlin.li@arm.com>
Branch: master
Commit: 87f5fbcc7aa49cee13e9ed44587b80d695d7e781

[AArch64] Gas add BFD_RELOC_AARCH64_LD64_GOTOFF_LO15 support
2015-06-15  Renlin Li <renlin.li@arm.com>
bfd/
    * reloc.c (BFD_RELOC_AARCH64_LD64_GOTOFF_LO15): New entry.
    * elfnn-aarch64.c (elfNN_aarch64_howto_table): New entry for
    BFD_RELOC_AARCH64_LD64_GOTOFF_LO15.
    * bfd-in2.h: Regenerate.
    * libbfd.h: Regenerate.

gas/
    * config/tc-aarch64.c (reloc_table): New relocation modifier.
    (md_apply_fix): Support BFD_RELOC_AARCH64_LD64_GOTOFF_LO15.
    (aarch64_force_relocation): Ditto

gas/testsuite/
    * gas/aarch64/reloc-insn.s: Update test
    * gas/aarch64/reloc-insn.d: Update expected result.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] DJGPP port of binutils broken due to 64 bit cygwin fix
@ 2015-06-15  7:16 sergiodj+buildbot
  2015-06-15 10:31 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-06-15  7:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3a062fa1eeee8296dece36a9bb7ecc8d4500de18 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 3a062fa1eeee8296dece36a9bb7ecc8d4500de18

DJGPP port of binutils broken due to 64 bit cygwin fix
	* cofflink.c (_bfd_coff_generic_relocate_section): Revert
	2014-03-26 change.  Call _bfd_clear_contents for relocs against
	local and global symbols defined in discarded input sections.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] gdbarch: add addressable_memory_unit_size method
@ 2015-06-12 23:15 sergiodj+buildbot
  2015-06-13 20:07 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-06-12 23:15 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3374165f51fa3cc3ce1b1bf8c72293464da9d511 ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: 3374165f51fa3cc3ce1b1bf8c72293464da9d511

gdbarch: add addressable_memory_unit_size method
Add a new gdbarch method to get the length of an addressable memory unit
for a given architecture. The default implementation returns 1.

gdb/ChangeLog:

	* arch-utils.h (default_addressable_memory_unit_size): New.
	* arch-utils.c (default_addressable_memory_unit_size): New.
	* gdbarch.sh (addressable_memory_unit_size): New.
	* gdbarch.h: Re-generate.
	* gdbarch.c: Re-generate.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] sim: update configure.in->configure.ac docs
@ 2015-06-12 19:37 sergiodj+buildbot
  2015-06-13 13:44 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-06-12 19:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 306f4178efa1851c411438aea39ddc553bc3070d ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 306f4178efa1851c411438aea39ddc553bc3070d

sim: update configure.in->configure.ac docs
A few places still refer to the configure.in file; update them.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] sim: bfin: expand CB_SYS_xxx comment
@ 2015-06-12 17:42 sergiodj+buildbot
  2015-06-13 15:05 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-06-12 17:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT aaa9dc0170d5a2c09712f65f38dd308e7cfd4df0 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: aaa9dc0170d5a2c09712f65f38dd308e7cfd4df0

sim: bfin: expand CB_SYS_xxx comment


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] sim: drop -DTRACE from configure
@ 2015-06-12 16:25 sergiodj+buildbot
  2015-06-13 11:06 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-06-12 16:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a34870829162e3276a9e0152efe2c7de5677a0c3 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: a34870829162e3276a9e0152efe2c7de5677a0c3

sim: drop -DTRACE from configure
No code uses this anymore and the symbol conflicts with the new TRACE
helper.  Punt it from configure.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] sim: moxie: rename TRACE to MOXIE_TRACE_INSN
@ 2015-06-12 10:53 sergiodj+buildbot
  2015-06-12 19:37 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-06-12 10:53 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 53d2389fd01ea7eaa83bb2727efd64c9904951ec ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 53d2389fd01ea7eaa83bb2727efd64c9904951ec

sim: moxie: rename TRACE to MOXIE_TRACE_INSN
We want to add new common trace helpers including "TRACE", so rename the
moxie one to MOXIE_TRACE_INSN.  This also matches what the code is doing.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] sim: msp430: delete unused trace macros
@ 2015-06-11 16:58 sergiodj+buildbot
  2015-06-12 14:45 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-06-11 16:58 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c1d8560ea5721191e30e2fcad720345730918497 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: c1d8560ea5721191e30e2fcad720345730918497

sim: msp430: delete unused trace macros
These macros were copied from the Blackfin port but never used, so delete
them as part of the trace unification work.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] sim: trace: centralize the system tracing
@ 2015-06-11 16:24 sergiodj+buildbot
  2015-06-12 13:12 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-06-11 16:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 83034798de7d11d2e26b3760e26b2c9cadec9fd4 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 83034798de7d11d2e26b3760e26b2c9cadec9fd4

sim: trace: centralize the system tracing
First we convert the ETRACE_P to STRACE_EVENTS_P.  This means we move from
using the sim_events.trace storage to the common sim_state_base.trace_data
array.  With that deleted, the common trace init code can be simplified so
the sim state works the same as the sim cpu.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] sim: trace: add STRACE_xxx_P macros
@ 2015-06-11 16:17 sergiodj+buildbot
  2015-06-12 11:18 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-06-11 16:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ce4eda4a58d4634577cf998b928572bed6779246 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: ce4eda4a58d4634577cf998b928572bed6779246

sim: trace: add STRACE_xxx_P macros
These are the parallel to the TRACE_xxx_P macros and fill out the full
set to match the existing debug one.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] sim: trace: use existing defines for the useful mask
@ 2015-06-11 16:10 sergiodj+buildbot
  2015-06-12  9:29 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-06-11 16:10 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a6c2a374e05770dd7469e050f5d6603e3f034f17 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: a6c2a374e05770dd7469e050f5d6603e3f034f17

sim: trace: use existing defines for the useful mask
No point in duplicating the shift logic when we have macros already to
keep that all unified.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Use pulongest for printing ssize_t
@ 2015-06-11 12:42 sergiodj+buildbot
  2015-06-11 19:04 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-06-11 12:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6449ed0d3a78ba8c25e8a634f8d6ed120a4cac7f ***

Author: Gary Benson <gbenson@redhat.com>
Branch: master
Commit: 6449ed0d3a78ba8c25e8a634f8d6ed120a4cac7f

Use pulongest for printing ssize_t
This commit changes the debug printing code in linux-namespaces.c
to use pulongest instead of "%ld".

gdb/ChangeLog:

	* nat/linux-namespaces.c (mnsh_send_message): Use pulongest.
	(mnsh_recv_message): Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Remove linux_proc_pid_get_ns
@ 2015-06-10 13:51 sergiodj+buildbot
  2015-06-10 18:39 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-06-10 13:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9bc3a9760b22a6187fdce6abc3df8f0c1d483a21 ***

Author: Gary Benson <gbenson@redhat.com>
Branch: master
Commit: 9bc3a9760b22a6187fdce6abc3df8f0c1d483a21

Remove linux_proc_pid_get_ns
This commit removes linux_proc_pid_get_ns, and updates its only
caller to use linux_ns_same instead.

gdb/ChangeLog:

	* linux-thread-db.c (nat/linux-namespaces.h): New include.
	(check_pid_namespace_match): Use linux_ns_same rather than
	linux_proc_pid_get_ns to spot PID namespace mismatches.
	* nat/linux-procfs.h (linux_proc_pid_get_ns): Remove.
	* nat/linux-procfs.c (linux_proc_pid_get_ns): Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Add support for bound table in the Intel MPX context.
@ 2015-06-10 11:49 sergiodj+buildbot
  2015-06-10 12:55 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-06-10 11:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 29c1c24429a099eca297080dba56a8c090e3136a ***

Author: Walfred Tedeschi <walfred.tedeschi@intel.com>
Branch: master
Commit: 29c1c24429a099eca297080dba56a8c090e3136a

Add support for bound table in the Intel MPX context.
Intel(R) Memory protection bound information are located in register
to be tested using the MPX new instructions. Since the number of
bound registers are limited a table is used to provide storage for
bounds during run-time.

In order to investigate the contents of the MPX bound table two new
commands are added to GDB.  "show mpx bound" and "set mpx bound" are
used to display and set values on the MPX bound table.

2015-04-20  Walfred Tedeschi  <walfred.tedeschi@intel.com>
            Mircea Gherzan  <mircea.gherzan@intel.com>

	* i386-tdep.c (MPX_BASE_MASK, MPX_BD_MASK, MPX_BT_MASK, MPX_BD_MASK_32,
	MPX_BT_MASK_32): New macros.
	(i386_mpx_set_bounds): New function that implements
	the command "set-mpx-bound".
	(i386_mpx_enabled) Helper function to test MPX availability.
	(i386_mpx_bd_base) Helper function to calculate the base directory
	address. (i386_mpx_get_bt_entry) Helper function to access a bound
	table entry. (i386_mpx_print_bounds) Effectively display bound
	information. (_initialize_i386_tdep): Qdd new commands
	to commands "set mpx" and "show mpx". (_initialize_i386_tdep):
	Add "bound" to the commands "show mpx" and "set mpx" commands.
	(mpx_set_cmdlist and mpx_show_cmdlist):
	list for the new prefixed "set mpx" and "show mpx" commands.
	* NEWS: List new commands for MPX support.

testsuite:

	* gdb.arch/i386-mpx-map.c: New file.
	* gdb.arch/i386-mpx-map.exp: New File.

doc:
	* gdb.texinfo (i386): Add documentation about "show mpx bound"
	and "set mpx bound".


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix spelling mistakes in sim/common/sim-events.c error messages.
@ 2015-06-09 18:49 sergiodj+buildbot
  2015-06-09 19:49 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-06-09 18:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 509c2f329a42646e64c7c3e8796f8b3bbd904032 ***

Author: Mike Stump <mrs@mrs.kithrup.com>
Branch: master
Commit: 509c2f329a42646e64c7c3e8796f8b3bbd904032

Fix spelling mistakes in sim/common/sim-events.c error messages.
sim/common/ChangeLog:

        * sim-events.c (sim_events_schedule_after_signal): Fix spelling
        mistake in call to sim_engine_abort.
        (sim_events_schedule_after_signal): Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Don't assume File-I/O mode bits match the host's format
@ 2015-06-09 12:54 sergiodj+buildbot
  2015-06-09 14:45 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-06-09 12:54 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3ac2e371a1abd1279f66477aa4fc68039da1872e ***

Author: Gary Benson <gbenson@redhat.com>
Branch: master
Commit: 3ac2e371a1abd1279f66477aa4fc68039da1872e

Don't assume File-I/O mode bits match the host's format
inf_child_fileio_open and its gdbserver equivalent both assume that
the mode_t bits defined in gdb/fileio.h are the same as those used
by the open system call, but there is no mechanism to ensure this is
the case.  This commit adds a conversion function to handle systems
where the File-I/O definitions do not align with the host's.

gdb/ChangeLog:

	* common/fileio.h (fileio_to_host_mode): New declaration.
	* common/fileio.c (fileio_to_host_mode): New Function.
	* inf-child.c (inf_child_fileio_open): Process mode argument
	with fileio_to_host_mode.

gdb/gdbserver/ChangeLog:

	* hostio.c (handle_open): Process mode argument with
	fileio_to_host_mode.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix preprocessor conditional
@ 2015-06-09  9:40 sergiodj+buildbot
  2015-06-09 10:15 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-06-09  9:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ecef18c564bd609aa7640564747b807bfe1632c6 ***

Author: Gary Benson <gbenson@redhat.com>
Branch: master
Commit: ecef18c564bd609aa7640564747b807bfe1632c6

Fix preprocessor conditional
This commit fixes a typo in common/fileio.c where S_IWGRP was
misspelled as S_IWRGRP in a preprocessor conditional, causing
Host-I/O "vFile:fstat:" and File-I/O "Fstat" and "Ffstat"
responses to always indicate files were not group-writable
regardless of their actual status.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Move vgdb special case into remote_filesystem_is_local
@ 2015-06-05 15:33 sergiodj+buildbot
  2015-06-05 16:51 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-06-05 15:33 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e3dd7556ad89bf00c2a92f76079ae1c53dc130a8 ***

Author: Gary Benson <gbenson@redhat.com>
Branch: master
Commit: e3dd7556ad89bf00c2a92f76079ae1c53dc130a8

Move vgdb special case into remote_filesystem_is_local
Valgrind GDB (vgdb) presents itself as a remote target but works on
the local filesystem.  gdb_bfd_open contained a special case to make
vgdb work with "target:" sysroots, but the implementation meant that
GDB would fall back to the local filesystem if *any* to_fileio_open
method failed with ENOSYS for *any* reason.  This commit moves the
vgdb special case to remote_filesystem_is_local to allow the fallback
to be restricted only to the specific case that remote file transfer
is unsupported.  This commit also adds a warning which is displayed
the first time the fallback is used.

gdb/ChangeLog:

	* gdb_bfd.c (gdb_bfd_open): Move vgdb special case to...
	* remote.c (remote_filesystem_is_local): ...here.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] ppc476 linker workaround shared lib fixes
@ 2015-06-05 11:06 sergiodj+buildbot
  2015-06-05 12:12 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-06-05 11:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f8b447819b3d65c3bea65dee860110aa198c081e ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: f8b447819b3d65c3bea65dee860110aa198c081e

ppc476 linker workaround shared lib fixes
When building a shared lib from non-PIC objects, we'll get dynamic
text relocations.  These need to move with any insns we move.
Otherwise the dynamic reloc will modify the branch, resulting in
crashes and other unpleasant behaviour.

Also, ld -r --ppc476-workaround used with sufficiently aligned PIC
objects needs a fix for emitted REL16 relocs.

bfd/
	* elf64-ppc.c (ppc_elf_relocate_section): Move dynamic text
	relocs with insns moved by --ppc476-workaround.  Correct
	output of REL16 relocs.
ld/testsuite/
	* ld-powerpc/ppc476-shared.s,
	* ld-powerpc/ppc476-shared.lnk,
	* ld-powerpc/ppc476-shared.d,
	* ld-powerpc/ppc476-shared2.d: New tests.
	* ld-powerpc/powerpc.exp: Run them.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] compile-print.exp: xfail->kfail for '@' GDB array operator
@ 2015-06-04 20:00 sergiodj+buildbot
  2015-06-04 23:37 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-06-04 20:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d5eba19a654f31f7409bd17b0d3dd2e4c483280e ***

Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Branch: master
Commit: d5eba19a654f31f7409bd17b0d3dd2e4c483280e

compile-print.exp: xfail->kfail for '@' GDB array operator
Patch implementing '@' GDB array operator in GCC has been rejected:
	https://gcc.gnu.org/ml/gcc-patches/2015-06/msg00414.html
and so there is now a GDB tracker to implement it just in GDB:
	https://sourceware.org/bugzilla/show_bug.cgi?id=18489

gdb/testsuite/ChangeLog
2015-06-04  Jan Kratochvil  <jan.kratochvil@redhat.com>

	* gdb.compile/compile-print.exp (compile print *vararray@3)
	(compile print *vararrayp@3): Change xfail to kfail compile/18489.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fixes the check for emulated MSP430 instrucrtions that take no operands.
@ 2015-06-04 15:54 sergiodj+buildbot
  2015-06-04 17:02 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-06-04 15:54 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 13be46a23c97f8bdb4ac028c1498197e44fe2e62 ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: 13be46a23c97f8bdb4ac028c1498197e44fe2e62

Fixes the check for emulated MSP430 instrucrtions that take no operands.
	PR 18474
	* msp430-dis.c (msp430_nooperands): Fix check for emulated insns.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [AArch64] Add support for ARMv8.1 command line option
@ 2015-06-04 10:37 sergiodj+buildbot
  2015-06-04 11:50 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-06-04 10:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 88f0ea342dc6eb3d93a29895febdebe3e425a048 ***

Author: Matthew Wahab <matthew.wahab@arm.com>
Branch: master
Commit: 88f0ea342dc6eb3d93a29895febdebe3e425a048

[AArch64] Add support for ARMv8.1 command line option


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] compile: Use also inferior munmap
@ 2015-06-03 19:45 sergiodj+buildbot
  2015-06-03 21:21 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-06-03 19:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7f36105668d57c26b52037202f5d97dbad91336b ***

Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Branch: master
Commit: 7f36105668d57c26b52037202f5d97dbad91336b

compile: Use also inferior munmap
Currently inferior memory is allocated by inferior mmap() but it is never
deallocated; despite the injected objfile incl. its symbols is freed.  This was
intentional so that one can do for example:
inferior:
	char *str = "foo";
GDB:
	(gdb) compile code str = "bar";

I believe later patches will be needed to introduce full control over keeping
vs. discarding the injected module as being discussed in:
	compile: objfiles lifetime UI
	https://sourceware.org/ml/gdb/2015-04/msg00051.html
	Message-ID: <20150429135735.GA16974@host1.jankratochvil.net>
	https://sourceware.org/ml/gdb/2015-05/msg00007.html

As decided by Phil it is better not to leak inferior pages as users can
workaround the issue above for example by:
	(gdb) compile code str = strdup ("bar");

I have checked that in fact gdb/doc/ (written by Phil) already expects the
injected code will be unmapped so that does not need to be changed:
	compile code int ff = 5; p = &ff;
	In this example, @code{p} would point to @code{ff} when the
	@code{compile} command is executing the source code provided to it.
	However, as variables in the (example) program persist with their
	assigned values, the variable @code{p} would point to an invalid
	location when the command exists.

gdb/ChangeLog
2015-04-28  Jan Kratochvil  <jan.kratochvil@redhat.com>

	* arch-utils.c (default_infcall_munmap): New.
	* arch-utils.h (default_infcall_munmap): New declaration.
	* compile/compile-object-load.c (struct munmap_list, munmap_list_add)
	(munmap_list_free, munmap_listp_free_cleanup): New.
	(struct setup_sections_data): Add field munmap_list_headp.
	(setup_sections): Call munmap_list_add.
	(compile_object_load): New variable munmap_list_head, initialize
	setup_sections_data.munmap_list_headp, return munmap_list_head.
	* compile/compile-object-load.h (struct munmap_list): New declaration.
	(struct compile_module): Add field munmap_list_head.
	(munmap_list_free): New declaration.
	* compile/compile-object-run.c (struct do_module_cleanup): Add field
	munmap_list_head.
	(do_module_cleanup): Call munmap_list_free.
	(compile_object_run): Pass munmap_list_head to do_module_cleanup.
	* gdbarch.c: Regenerate.
	* gdbarch.h: Regenerate.
	* gdbarch.sh (infcall_munmap): New.
	* linux-tdep.c (linux_infcall_munmap): New.
	(linux_init_abi): Install it.

gdb/testsuite/ChangeLog
2015-04-28  Jan Kratochvil  <jan.kratochvil@redhat.com>

	* gdb.compile/compile.exp (keep jit in memory): Rename to ...
	(do not keep jit in memory): ... this.
	(expect 5): Change it to ...
	(expect no 5): ... this.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix =thread-exited not showing up when detaching (PR 15564)
@ 2015-06-02 19:59 sergiodj+buildbot
  2015-06-02 20:25 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-06-02 19:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3b462ec2bedca7392bf4720db44fdf2a46ad8b4d ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: 3b462ec2bedca7392bf4720db44fdf2a46ad8b4d

Fix =thread-exited not showing up when detaching (PR 15564)
I sent a patch in 2013 for this (incorrectly named =thread-created):

  https://cygwin.com/ml/gdb-patches/2013-06/msg00129.html

Tom Tromey was ok with the change, but suggested to add a test as well.
Then I forgot about this patch until today. So here it is again, with the
corresponding test.

The problem is that the =thread-exited event does not appear when detaching
from a local process. It does appear with remote though. It's not a really
big deal, but I'd like it to be consistent.

Tested with local and remote Linux on my Ubuntu 14.04.

gdb/ChangeLog:

	PR gdb/15564
	* inferior.c (detach_inferior): Call exit_inferior_1 with silent = 0.

gdb/testsuite/ChangeLog:

	PR gdb/15564
	* gdb.mi/mi-detach.exp: New file.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [ARM] Support for ARMv8.1 Adv.SIMD extension
@ 2015-06-02 13:22 sergiodj+buildbot
  2015-06-02 18:55 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-06-02 13:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d6b4b13ed2859a1eafd6c94c0dc64b20fdbde1ba ***

Author: Matthew Wahab <matthew.wahab@arm.com>
Branch: master
Commit: d6b4b13ed2859a1eafd6c94c0dc64b20fdbde1ba

[ARM] Support for ARMv8.1 Adv.SIMD extension


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [ARM] Rework CPU feature selection in the disassembler
@ 2015-06-02 12:32 sergiodj+buildbot
  2015-06-02 16:06 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-06-02 12:32 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1af1dd51db991700c0e66b35d777a44e6953bbd2 ***

Author: Matthew Wahab <matthew.wahab@arm.com>
Branch: master
Commit: 1af1dd51db991700c0e66b35d777a44e6953bbd2

[ARM] Rework CPU feature selection in the disassembler
include/opcode/
	* arm.h (ARM_FEATURE_ALL): New.

opcodes/
	* arm-dis.c (select_arm_features): Rework to avoid used of
	redefined macros.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [AArch64] Support for ARMv8.1a Adv.SIMD instructions
@ 2015-06-02 11:35 sergiodj+buildbot
  2015-06-02 14:24 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-06-02 11:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9e1f0fa7f3f7aef95d27e197562906bc648849bb ***

Author: Matthew Wahab <matthew.wahab@arm.com>
Branch: master
Commit: 9e1f0fa7f3f7aef95d27e197562906bc648849bb

[AArch64] Support for ARMv8.1a Adv.SIMD instructions
2015-06-02  Matthew Wahab  <matthew.wahab@arm.com>

gas/
  * config/tc-aarch64.c (aarch64_features): Add "rdma".
  * doc/c-aarch64.texi (AArch64 Extensions): Add "rdma".

gas/testsuite/
  * rdma-directive.d: New.
  * rdma.d: New.
  * rdma.s: New.

include/opcode/
  * aarch64.h (AARCH64_FEATURE_RDMA): New.

opcode/
  * aarch64-tbl.h (aarch64_feature_rdma): New.
  (RDMA): New.
  (aarch64_opcode_table): Add "sqrmlah" and "sqrdmlsh" instructions.
  * aarch64-asm-2.c: Regenerate.
  * aarch64-dis-2.c: Regenerate.
  * aarch64-opc-2.c: Regenerate.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [AArch64] Support for ARMv8.1a Limited Ordering Regions extension
@ 2015-06-02 10:50 sergiodj+buildbot
  2015-06-02 12:29 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-06-02 10:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 290806fd94099361f28e012cebca058c8c4f0e45 ***

Author: Matthew Wahab <matthew.wahab@arm.com>
Branch: master
Commit: 290806fd94099361f28e012cebca058c8c4f0e45

[AArch64] Support for ARMv8.1a Limited Ordering Regions extension
2015-06-02  Matthew Wahab  <matthew.wahab@arm.com>
include/
  * aarch64.h (AARCH64_FEATURE_LOR): New.

opcodes/
  * aarch64-tbl.h (aarch64_feature_lor): New.
  (LOR): New.
  (aarch64_opdocde_table): Add "ldlar", "ldlarb", "ldlarh", "stllr",
  "stllrb", "stllrh".
  * aarch64-asm-2.c: Regenerate.
  * aarch64-dis-2.c: Regenerate.
  * aarch64-opc-2.c: Regenerate.

gas/
  * config/tc-aarch64.c (aarch64_features): Add "lor".
  * doc/c-aarch64.c (Aarch64 Extensions): Add "lor" to list of
  architecture extensions.

gas/testsuite/
  * lor-directive.d: New.
  * lor.d: New.
  * lor.s: New.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [AArch64] BFD support BFD_RELOC_AARCH64_LD32_GOTPAGE_LO14
@ 2015-06-01 14:58 sergiodj+buildbot
  2015-06-02  2:42 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-06-01 14:58 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7018c0308ac5d936b68c280bfcdc80bef77225e1 ***

Author: Jiong Wang <jiong.wang@arm.com>
Branch: master
Commit: 7018c0308ac5d936b68c280bfcdc80bef77225e1

[AArch64] BFD support BFD_RELOC_AARCH64_LD32_GOTPAGE_LO14
This patch add BFD_RELOC_AARCH64_LD32_GOTPAGE_LO14 relocation
supoprt in bfd linker.

2015-06-01  Jiong Wang  <jiong.wang@arm.com>

bfd/
  * elfnn-aarch64.c (aarch64_reloc_got_type): Support
  BFD_RELOC_AARCH64_LD32_GOTPAGE_LO14.
  (elfNN_aarch64_final_link_relocate): Ditto.
  (elfNN_aarch64_gc_swap_hook): Ditto.
  (elfNN_aarch64_check_relocs): Ditto.
  * elfxx-aarch64.c (_bfd_aarch64_elf_put_addend): Ditto.

ld/testsuite/
  * ld-aarch64/emit-relocs-28.s: New test file.
  * ld-aarch64/emit-relocs-28.d: Ditto.
  * ld-aarch64/aarch64-elf.exp: Run new test.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [AArch64] GAS support BFD_RELOC_AARCH64_LD32_GOTPAGE_LO14
@ 2015-06-01 14:50 sergiodj+buildbot
  2015-06-02  1:07 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-06-01 14:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3d715ce4202ef799e288261d08a5438c82e7c21e ***

Author: Jiong Wang <jiong.wang@arm.com>
Branch: master
Commit: 3d715ce4202ef799e288261d08a5438c82e7c21e

[AArch64] GAS support BFD_RELOC_AARCH64_LD32_GOTPAGE_LO14
This patch add BFD_RELOC_AARCH64_LD32_GOTPAGE_LO14 support in Gas.

The relocation modifier
===
  :gotpage_lo14:symbol

2015-06-01 Jiong.Wang <jiong.wang@arm.com>

bfd/
  * reloc.c (BFD_RELOC_AARCH64_LD32_GOTPAGE_LO14): New entry.
  * bfd-in2.h: Regenerate.
  * libbfd.h: Regenerate.
  * elfnn-aarch64.c (elfNN_aarch64_howto_table): New entry for
  BFD_RELOC_AARCH64_LD32_GOTPAGE_LO14.

gas/
  * config/tc-aarch64.c (reloc_table): New relocation modifiers.
  (md_apply_fix): Support BFD_RELOC_AARCH64_LD32_GOTPAGE_LO14.
  (aarch64_force_relocation): Ditto.

gas/testsuite/
  * gas/aarch64/ilp32-basic.s: New testcase.
  * gas/aarch64/ilp32-basic.d: Ditto.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] PR symtab/18392
@ 2015-06-01 12:56 sergiodj+buildbot
  2015-06-01 22:40 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-06-01 12:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e0619de699ae6e86d8b93fa96a7668aef2e9636a ***

Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Branch: master
Commit: e0619de699ae6e86d8b93fa96a7668aef2e9636a

PR symtab/18392
Initially there is some chain (let's say the longest one
but that doe snot matter).  Consequently its elements from the middle are
being removed and there remains only some few unambiguous top and bottom ones.

The original idea why the comparison should be sharp ("<") was that if there
are multiple chains like (0xaddr show jmp instruction address):
        main(0x100) -> a(0x200) -> d(0x400)
        main(0x100) -> a(0x200) -> c(0x300) -> d(0x400)
then - such situation cannot exist - if two jmp instructions in "a" have the
same address they must also jump to the same address (*).

(*) jump to a computed address would be never considered for the DWARF
    tail-call records.

So there could be:
        main(0x100) -> a(0x200) -> d(0x400)
        main(0x100) -> a(0x270) -> c(0x300) -> d(0x400)
But then "a" frame itself is ambiguous and it must not be displayed.

I did not realize that there can be self-tail-call:
        main(0x100) -> a(0x200) -> d(0x400)
        main(0x100) -> a(0x280) -> a(0x200) -> d(0x400)
which intersects to:
        main(0x100) -> <???>? -> a(0x200) -> d(0x400)
And so if the first chain was chosen the
        main(0x100) -> a(0x200) -> d(0x400)
then the final intersection has callers+callees==length.

> for example, if CALLERS is 3 and
> CALLEES is 2, what does the chain look like?

main(0x100) -> x(0x150) -> y(0x200) -> <???>? -> a(0x200) -> d(0x400)

And if LENGTH is 7 then:
        call_site[0] = main(0x100)
        call_site[1] = x(0x150)
        call_site[2] = y(0x200)
        call_site[3] = garbage
        call_site[4] = garbage
        call_site[5] = a(0x200)
        call_site[6] = d(0x400)

gdb/ChangeLog
2015-06-01  Andreas Schwab  <schwab@linux-m68k.org>
	    Jan Kratochvil  <jan.kratochvil@redhat.com>

	PR symtab/18392
	* dwarf2-frame-tailcall.c (pretended_chain_levels): Correct
	assertion.
	* dwarf2loc.c (chain_candidate): Likewise.

gdb/testsuite/ChangeLog
2015-06-01  Jan Kratochvil  <jan.kratochvil@redhat.com>

	PR symtab/18392
	* gdb.arch/amd64-tailcall-self.S: New file.
	* gdb.arch/amd64-tailcall-self.c: New file.
	* gdb.arch/amd64-tailcall-self.exp: New file.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fetch and store GP registers by PTRACE_{G,S}ETREGSET
@ 2015-06-01 12:32 sergiodj+buildbot
  2015-06-01 18:12 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-06-01 12:32 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 10766686b02fce9eedd6217ca76f457106a8142c ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 10766686b02fce9eedd6217ca76f457106a8142c

Fetch and store GP registers by PTRACE_{G,S}ETREGSET
If kernel supports PTRACE_GETREGSET, GDB uses PTRACE_{G,S}ETREGSET
to fetch and store GP registers.

gdb:

2015-06-01  Yao Qi  <yao.qi@linaro.org>

	* arm-linux-nat.c (fetch_register): Use PTRACE_GETREGSET.
	(fetch_regs): Likewise.
	(store_regs): Use PTRACE_SETREGSET.
	(store_register): Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Check whether kernel supports PTRACE_GETREGSET
@ 2015-06-01 12:27 sergiodj+buildbot
  2015-06-01 17:11 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-06-01 12:27 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7efe48d196f3fb6f55fc53b8021a410848c0a677 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 7efe48d196f3fb6f55fc53b8021a410848c0a677

Check whether kernel supports PTRACE_GETREGSET
gdb:

2015-06-01  Yao Qi  <yao.qi@linaro.org>

	* arm-linux-nat.c (arm_linux_read_description): Check whether
	kernel supports PTRACE_GETREGSET.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] x86/Intel: fix i386_optab[] for vcvt{,u}si2s{d,s}
@ 2015-06-01  9:59 sergiodj+buildbot
  2015-06-01 11:20 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-06-01  9:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d194d186a7dd9f23f34a9aef593ce691af3c875f ***

Author: Jan Beulich <jbeulich@novell.com>
Branch: master
Commit: d194d186a7dd9f23f34a9aef593ce691af3c875f

x86/Intel: fix i386_optab[] for vcvt{,u}si2s{d,s}
opcodes/
2015-06-01  Jan Beulich  <jbeulich@suse.com>

	* i386-tbl.h: Regenerate.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [AArch64] BFD_RELOC_AARCH64_TLSLE_ADD_LO12 should enable overflow check
@ 2015-06-01  9:39 sergiodj+buildbot
  2015-06-01  9:59 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-06-01  9:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 36e6c1400b94b9da7ba0dff5b3900a8d3e3b0c75 ***

Author: Jiong Wang <jiong.wang@arm.com>
Branch: master
Commit: 36e6c1400b94b9da7ba0dff5b3900a8d3e3b0c75

[AArch64] BFD_RELOC_AARCH64_TLSLE_ADD_LO12 should enable overflow check
BFD_RELOC_AARCH64_TLSLE_ADD_LO12 is used to generate simplest
one-instruction addressing for TLS LE model when tls size is smaller
4K. Linker need to make sure there is no TLS offset overflow.

2015-06-01  Jiong Wang  <jiong.wang@arm.com>

bfd/
  * elfnn-aarch64.c (elfNN_aarch64_howto_table): Set overflow type to
  complain_overflow_unsigned for BFD_RELOC_AARCH64_TLSLE_ADD_LO12.
  * elfxx-aarch64.c (_bfd_aarch64_elf_resolve_relocation): Don't use
  PGOFF for BFD_RELOC_AARCH64_TLSLE_ADD_LO12, that will mask off all
  potential high overflowed bits.

ld/testsuite/
  * ld-aarch64/tprel_add_lo12_overflow.s: New testcase.
  * ld-aarch64/tprel_add_lo12_overflow.d: Nex expectation file.
  * ld-aarch64/aarch64-elf.exp: Run new testcase.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [AArch64] BFD Support BFD_RELOC_AARCH64_LD64_GOTPAGE_LO15
@ 2015-06-01  9:32 sergiodj+buildbot
  2015-06-01  9:44 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-06-01  9:32 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 99ad26cb0d4f9152dbe5ed03b74020cc52d84d94 ***

Author: Jiong Wang <jiong.wang@arm.com>
Branch: master
Commit: 99ad26cb0d4f9152dbe5ed03b74020cc52d84d94

[AArch64] BFD Support BFD_RELOC_AARCH64_LD64_GOTPAGE_LO15
2015-06-01  Jiong Wang  <jiong.wang@arm.com>
bfd/
	* elfnn-aarch64.c (aarch64_reloc_got_type): Support
	BFD_RELOC_AARCH64_LD64_GOTPAGE_LO15.
	(elfNN_aarch64_final_link_relocate): Ditto.
	(elfNN_aarch64_gc_swap_hook): Ditto.
	(elfNN_aarch64_check_relocs): Ditto.
	* elfxx-aarch64.c (_bfd_aarch64_elf_put_addend): Ditto.

ld/testsuite/
	* ld-aarch64/emit-relocs-313.s: New test file.
	* ld-aarch64/emit-relocs-313.d: Ditto.
	* ld-aarch64/aarch64-elf.exp: Run new test.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [AArch64] GAS Support BFD_RELOC_AARCH64_LD64_GOTPAGE_LO15
@ 2015-06-01  9:26 sergiodj+buildbot
  2015-06-01  9:32 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-06-01  9:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a921b5bd708cc6e8afa3cf33443cda54b4e8cae6 ***

Author: Jiong Wang <jiong.wang@arm.com>
Branch: master
Commit: a921b5bd708cc6e8afa3cf33443cda54b4e8cae6

[AArch64] GAS Support BFD_RELOC_AARCH64_LD64_GOTPAGE_LO15
2015-06-01 Jiong.Wang <jiong.wang@arm.com>

bfd/
  * reloc.c (BFD_RELOC_AARCH64_LD64_GOTPAGE_LO15): New entry.
  * bfd-in2.h: Regenerate.
  * libbfd.h: Regenerate.
  * elfnn-aarch64.c (elfNN_aarch64_howto_table): New entry for
  BFD_RELOC_AARCH64_LD64_GOTPAGE_LO15.

gas/
  * config/tc-aarch64.c (reloc_table): New relocation modifiers.
  (md_apply_fix): Support BFD_RELOC_AARCH64_LD64_GOTPAGE_LO15.
  (aarch64_force_relocation): Ditto.

gas/testsuite/
  * gas/aarch64/reloc-insn.s: New testcase.
  * gas/aarch64/reloc-insn.d: Ditto.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] x86/Intel: disassemble vcvt{, u}si2s{d, s} with correct operand order
@ 2015-06-01  8:05 sergiodj+buildbot
  2015-06-01  8:25 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-06-01  8:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3a8547d2fb5319890dda877fb313822053083c3a ***

Author: Jan Beulich <jbeulich@novell.com>
Branch: master
Commit: 3a8547d2fb5319890dda877fb313822053083c3a

x86/Intel: disassemble vcvt{,u}si2s{d,s} with correct operand order
As pointed out before, the documentation mandates the rounding mode to
follow the GPR, so disassembler should produce output accordingly.

gas/testsuite/
2015-06-01  Jan Beulich  <jbeulich@suse.com>

	* gas/i386/avx512f.s: Adjust operand order for Intel syntax
	vcvt{,u}si2ss.
	* gas/i386/x86-64-avx512f.s: Adjust operand order for Intel
	syntax vcvt{,u}si2s{d,s}.

opcodes/
2015-06-01  Jan Beulich  <jbeulich@suse.com>

	* i386-dis.c (print_insn): Swap rounding mode specifier and
	general purpose register in Intel mode.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] x86/Intel: accept mandated operand order for vcvt{, u}si2s{d, s}
@ 2015-06-01  8:00 sergiodj+buildbot
  2015-06-01  8:05 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-06-01  8:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 015c54d5a6a052f074fab168bc70296131276e80 ***

Author: Jan Beulich <jbeulich@novell.com>
Branch: master
Commit: 015c54d5a6a052f074fab168bc70296131276e80

x86/Intel: accept mandated operand order for vcvt{,u}si2s{d,s}
As pointed out before, the documentation mandates the rounding mode to
follow the GPR, so gas should accept such input. As the brojen code got
released already we sadly will need to continue to also accept the
badly ordered operands.

gas/testsuite/
2015-06-01  Jan Beulich  <jbeulich@suse.com>

	* gas/i386/avx512f-intel.d: Adjust expectations on operand order.
	* gas/i386/evex-lig256-intel.d: Likewise.
	* gas/i386/evex-lig512-intel.d: Likewise.
	* gas/i386/x86-64-avx512f-intel.d: Likewise.
	* gas/i386/x86-64-evex-lig256-intel.d: Likewise.
	* gas/i386/x86-64-evex-lig512-intel.d: Likewise.

opcodes/
2015-06-01  Jan Beulich  <jbeulich@suse.com>

	* i386-opc.tbl: New IntelSyntax entries for vcvt{,u}si2s{d,s}.
	* i386-tbl.h: Regenerate.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Don't ignore domain in nested lookups.
@ 2015-05-27 20:10 sergiodj+buildbot
  2015-05-27 21:50 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-05-27 20:10 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4dcabcc2b5d82dca1089f87e5830a8cd3b5a4bd6 ***

Author: Doug Evans <dje@google.com>
Branch: master
Commit: 4dcabcc2b5d82dca1089f87e5830a8cd3b5a4bd6

Don't ignore domain in nested lookups.
gdb/ChangeLog:

	* cp-namespace.c (cp_lookup_nested_symbol): New arg "domain".
	All callers updated.
	(cp_lookup_nested_symbol_1, find_symbol_in_baseclass): Ditto.
	* cp-support.h (cp_lookup_nested_symbol): Update.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] PR symtab/18258
@ 2015-05-27 19:35 sergiodj+buildbot
  2015-05-27 20:17 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-05-27 19:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b2e2f908b863c27abb00108a03ebe2598baec55c ***

Author: Doug Evans <dje@google.com>
Branch: master
Commit: b2e2f908b863c27abb00108a03ebe2598baec55c

PR symtab/18258
gdb/ChangeLog:

	* block.c (block_find_symbol): New function.
	(block_find_non_opaque_type): Ditto.
	(block_find_non_opaque_type_preferred): Ditto.
	* block.h (block_symbol_matcher_ftype): New typedef.
	(block_find_symbol): Declare.
	(block_find_non_opaque_type): Ditto.
	(block_find_non_opaque_type_preferred): Ditto.
	* dwarf2read.c (dw2_lookup_symbol): Call block_find_symbol.
	* psymtab.c (psym_lookup_symbol): Ditto.
	* symtab.c (basic_lookup_transparent_type_1): New function.
	(basic_lookup_transparent_type): Call it.

gdb/testsuite/ChangeLog:

	* gdb.dwarf2/opaque-type-lookup-2.c: New file.
	* gdb.dwarf2/opaque-type-lookup.c: New file.
	* gdb.dwarf2/opaque-type-lookup.exp: New file.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [aarch64] Handle unknown instruction encoding
@ 2015-05-27 16:42 sergiodj+buildbot
  2015-05-27 17:49 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-05-27 16:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f62fce356bf1df27e01fc40a3a277fc924019ee7 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: f62fce356bf1df27e01fc40a3a277fc924019ee7

[aarch64] Handle unknown instruction encoding
We see the following build error:

 gdb/aarch64-tdep.c: In function 'aarch64_process_record':
 gdb/aarch64-tdep.c:2823:17: error: 'record_buf[0]' may be used uninitialized in this function [-Werror=maybe-uninitialized]
                 memcpy(&REGS[0], &RECORD_BUF[0], sizeof(uint32_t)*LENGTH); \
                 ^
 gdb/aarch64-tdep.c:3529:12: note: 'record_buf[0]' was declared here
   uint32_t record_buf[2];

since record_buf[0] isn't initialized in some paths in which
instruction encodings doesn't exist in current ARMv8 reference manual.
This patch is to let the function return AARCH64_RECORD_UNKNOWN for
these paths.

gdb:

2015-05-27  Yao Qi  <yao.qi@linaro.org>

	* aarch64-tdep.c (aarch64_record_data_proc_simd_fp): Return
	AARCH64_RECORD_UNKNOWN for unknown instruction encoding.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix ARI warnings in aarch64-tdep.c
@ 2015-05-27 10:48 sergiodj+buildbot
  2015-05-27 11:01 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-05-27 10:48 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5d98d3cd862ab5d463f71926788d52bf1b30ef79 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 5d98d3cd862ab5d463f71926788d52bf1b30ef79

Fix ARI warnings in aarch64-tdep.c
This patch fixes some ARI warnings:

 $ bash ./gdb/contrib/ari/gdb_ari.sh -Wall -Werror -Wari gdb/aarch64-tdep.c
 gdb/aarch64-tdep.c:3009: code: Do not use &&, or || at the end of a line
 gdb/aarch64-tdep.c:3010: code: Do not use &&, or || at the end of a line
 gdb/aarch64-tdep.c:3413: code: Do not use &&, or || at the end of a line
 gdb/aarch64-tdep.c:3460: code: Do not use &&, or || at the end of a line

This patch moves && from the end of line to the start of the line.

gdb:

2015-05-27  Yao Qi  <yao.qi@linaro.org>

	* aarch64-tdep.c (aarch64_record_branch_except_sys): Split lines
	before operator &&.
	(aarch64_record_load_store): Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] PR c++/18141, c++/18417.
@ 2015-05-27  0:27 sergiodj+buildbot
  2015-05-27  8:56 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-05-27  0:27 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 82c7be3106bbbf753f441f8a8113f2cac5e7cba8 ***

Author: Doug Evans <dje@google.com>
Branch: master
Commit: 82c7be3106bbbf753f441f8a8113f2cac5e7cba8

PR c++/18141, c++/18417.
gdb/ChangeLog:

	* cp-support.c (cp_lookup_rtti_type): Handle the case of NAME being
	a typedef.

gdb/testsuite/ChangeLog:

	* gdb.cp/iostream.cc: New file.
	* gdb.cp/iostream.exp: New file.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Rename dwarf2 to dwarf in "set debug" and maintenance commands.
@ 2015-05-27  0:00 sergiodj+buildbot
  2015-05-27  1:10 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-05-27  0:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b4f5498457d0648811a9cc9d34d3c6635509dffc ***

Author: Doug Evans <dje@google.com>
Branch: master
Commit: b4f5498457d0648811a9cc9d34d3c6635509dffc

Rename dwarf2 to dwarf in "set debug" and maintenance commands.
gdb/ChangeLog:

	* NEWS: Add entries for command renamings.
	* dwarf2read.c (dwarf_read_debug): Renamed from dwarf2_read_debug.
	All uses updated.
	(dwarf_die_debug): Renamed from dwarf2_die_debug.  All uses updated.
	(dwarf_max_cache_age): Renamed from dwarf2_max_cache_age.
	All uses updated.
	(show_dwarf_max_cache_age): Renamed from show_dwarf2_max_cache_age.
	All callers updated.  Fix spelling of DWARF in help text.
	(set_dwarf_cmdlist): Renamed from set_dwarf2_cmdlist.
	All uses updated.
	(show_dwarf_cmdlist): Renamed from show_dwarf2_cmdlist.
	All uses updated.
	(set_dwarf_cmd): Renamed from set_dwarf2_cmd.  All callers updated.
	(show_dwarf_cmd): Renamed from show_dwarf2_cmd.  All callers updated.
	(dwarf_always_disassemble): Renamed from dwarf_always_disassemble.
	All uses updated.
	(show_dwarf_always_disassemble): Renamed from
	show_dwarf2_always_disassemble.  All callers updated.
	(_initialize_dwarf2_read): Rename "set/show dwarf2" prefix to
	"set/show dwarf".  Rename "set/show dwarf2 max-cache-age" to
	"set/show dwarf max-cache-age".  Rename
	"set/show dwarf2 always-disassemble" to
	"set/show dwarf always-disassemble".  Rename
	"set/show debug dwarf2-read" to "set/show debug dwarf-read".  Rename
	"set/show debug dwarf2-die" to "set/show debug dwarf-die".

gdb/doc/ChangeLog:

	* gdb.texinfo (Debugging Output): Update for DWARF "set debug"
	command renamings.
	(Maintenance Commands): Update for DWARF "set debug" command renamings.

gdb/testsuite/ChangeLog:

	* gdb.dwarf2/dw2-op-call.exp: Update.
	* gdb.dwarf2/dw4-sig-types.exp: Update.
	* gdb.dwarf2/implptr.exp: Update.
	* gdb.mi/mi-cmd-param-changed.exp: Update.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] PR python/18438
@ 2015-05-26 23:21 sergiodj+buildbot
  2015-05-26 23:26 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-05-26 23:21 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4ea6efe9365f8a87723fe01a2dd8ddf5cdec1498 ***

Author: Doug Evans <dje@google.com>
Branch: master
Commit: 4ea6efe9365f8a87723fe01a2dd8ddf5cdec1498

PR python/18438
gdb/ChangeLog:

	* python/py-lazy-string.c (stpy_convert_to_value): Use
	gdbpy_gdb_memory_error not PyExc_MemoryError.
	(gdbpy_create_lazy_string_object): Ditto.

gdb/testsuite/ChangeLog:

	* gdb.python/py-lazy-string.c: New file.
	* gdb.python/py-lazy-string.exp: New file.
	* gdb.python/py-prettyprint.c (lazystring) <len>: New member.
	(main): Update.  Add estring3.
	* gdb.python/py-prettyprint.exp: Add tests for strings at address 0.
	* gdb.python/py-prettyprint.py (pp_ls): Handle length.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] gdb: tui: Minor fix to compare against NULL.
@ 2015-05-26 21:49 sergiodj+buildbot
  2015-05-26 21:59 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-05-26 21:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b93fd21dccc2cfa9a335ddba7435a341b49330ae ***

Author: Andrew Burgess <andrew.burgess@embecosm.com>
Branch: master
Commit: b93fd21dccc2cfa9a335ddba7435a341b49330ae

gdb: tui: Minor fix to compare against NULL.
Minor coding standard fix to compare against NULL.

gdb/ChangeLog:

	* tui/tui-regs.c (tui_reg_next_command): Compare against NULL.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] gdb: Add 'tui reg prev' command.
@ 2015-05-26 21:39 sergiodj+buildbot
  2015-05-26 21:45 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-05-26 21:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 55b400279267cad460ca62a8211f0b414f564e93 ***

Author: Andrew Burgess <andrew.burgess@embecosm.com>
Branch: master
Commit: 55b400279267cad460ca62a8211f0b414f564e93

gdb: Add 'tui reg prev' command.
There is already a 'tui reg next' command, this adds a symmetric 'tui
reg prev' command.

gdb/ChangeLog:

	* tui/tui-regs.c (tui_reg_prev_command): New function.
	(_initialize_tui_regs): Add 'prev' command for 'tui reg'.
	* reggroups.c (reggroup_prev): New function.
	* reggroups.h (reggroup_prev): Add declaration.  Update comment.

gdb/doc/ChangeLog:

	* gdb.texinfo (TUI Commands): Add 'tui reg prev' details.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] New gdb.reverse test case for aarch64 instructions
@ 2015-05-26 14:39 sergiodj+buildbot
  2015-05-26 17:34 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-05-26 14:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f6bb7db35da7b1d150a467f97c41d5bf72c3baf5 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: f6bb7db35da7b1d150a467f97c41d5bf72c3baf5

New gdb.reverse test case for aarch64 instructions
This patch adds a test case to test the process record for some of
aarch64 instructions.

In each function, GDB turns on process record, and single step until
program goes to the end of the function.  Then, single step backward.
In each of forward single step and backward single step, the contents
of registers are saved, and test compares them.  If there is any
differences, a FAIL is emitted.

The test is flexible, and we can test other instructions easily in the
future.

gdb/testsuite:

2015-05-26  Omair Javaid  <omair.javaid@linaro.org>
	    Yao Qi  <yao.qi@linaro.org>

	* gdb.reverse/aarch64.c: New.
	* gdb.reverse/aarch64.exp: New.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Enables gdb.reverse testsuite for aarch64*-linux targets
@ 2015-05-26 14:29 sergiodj+buildbot
  2015-05-26 17:16 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-05-26 14:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a81bfbd06b949518055b21d19f47332edbd992e0 ***

Author: Omair Javaid <omair.javaid@linaro.org>
Branch: master
Commit: a81bfbd06b949518055b21d19f47332edbd992e0

Enables gdb.reverse testsuite for aarch64*-linux targets
This patch enable gdb.reverse tests for aarch64*-linux targets.

With this patch, there are 7 FAILs in gdb.reverse/ tests.

 FAIL: gdb.reverse/finish-reverse-bkpt.exp: reverse-finish from void_func trips breakpoint at entry
 FAIL: gdb.reverse/finish-reverse-bkpt.exp: no spurious proceed after breakpoint stop
 FAIL: gdb.reverse/next-reverse-bkpt-over-sr.exp: reverse-next over call trips user breakpoint at function entry
 FAIL: gdb.reverse/step-precsave.exp: reverse step into fn call
 FAIL: gdb.reverse/step-precsave.exp: reverse step out of called fn
 FAIL: gdb.reverse/step-reverse.exp: reverse step into fn call
 FAIL: gdb.reverse/step-reverse.exp: reverse step out of called fn

gdb/testsuite:

2015-05-26  Omair Javaid  <omair.javaid@linaro.org>

	* lib/gdb.exp (supports_process_record): Return true for aarch64*-linux*.
	(supports_reverse): Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Implements aarch64 process record and reverse debugging support
@ 2015-05-26 14:20 sergiodj+buildbot
  2015-05-26 16:54 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-05-26 14:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 99afc88b396045cfe3755bede41a45ad3bed021d ***

Author: Omair Javaid <omair.javaid@linaro.org>
Branch: master
Commit: 99afc88b396045cfe3755bede41a45ad3bed021d

Implements aarch64 process record and reverse debugging support
This patch adds the support of aarch64-linux process record and reverse
debugging.  The implementation is similar to ARM's counterpart.

2015-05-26  Omair Javaid  <omair.javaid@linaro.org>
	    Yao Qi  <yao.qi@linaro.org>

	* aarch64-linux-tdep.c: Include linux-record.h and
	record-full.h.
	(struct linux_record_tdep aarch64_linux_record_tdep): Declare.
	(aarch64_syscall): New enum.
	(aarch64_canonicalize_syscall): New function.
	(aarch64_all_but_pc_registers_record): New function.
	(aarch64_linux_syscall_record): New function.
	(aarch64_linux_init_abi): Install AArch64 process record
	handler.  Update to handle syscall recording.
	* aarch64-tdep.c: Include record.h and record-full.h.
	(submask, bit, bits, REG_ALLOC, MEM_ALLOC): New macros.
	(struct aarch64_mem_r): Define.
	(aarch64_record_result): New enum.
	(struct insn_decode_record): Define.
	(insn_decode_record): New typedef.
	(aarch64_record_data_proc_reg): New function.
	(aarch64_record_data_proc_imm): New function.
	(aarch64_record_branch_except_sys): New function.
	(aarch64_record_load_store): New function.
	(aarch64_record_data_proc_simd_fp): New function.
	(aarch64_record_asimd_load_store): New function.
	(aarch64_record_decode_insn_handler): New function.
	(deallocate_reg_mem): New function.
	(aarch64_process_record): New function.
	* aarch64-tdep.h (struct gdbarch_tdep) <aarch64_syscall_record>:
	New field.
	(aarch64_process_record): New extern declaration.
	* configure.tgt: Add linux-record.o to gdb_target_obs.
	* linux-record.h (struct linux_record_tdep) <arg7>: New field.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] gdb: New 'tui enable' and 'tui disable' commands.
@ 2015-05-22 10:45 sergiodj+buildbot
  2015-05-22 11:41 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-05-22 10:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a4ea0946c3f1badd6755b85b4e50e2ec4841e69c ***

Author: Andrew Burgess <andrew.burgess@embecosm.com>
Branch: master
Commit: a4ea0946c3f1badd6755b85b4e50e2ec4841e69c

gdb: New 'tui enable' and 'tui disable' commands.
Add new commands to specifically enable and disable tui mode.  This is
in addition to the readline bindings, but might be easier for a user to
discover if they accidentally end up in tui mode.

gdb/ChangeLog:

	* NEWS: Mention 'tui enable' and 'tui disable'.
	* tui/tui.c (tui_enable_command): New function.
	(tui_disable_command): New function.
	(_initialize_tui): New function.

gdb/doc/ChangeLog:

	* gdb.texinfo (TUI): Include 'tui enable' in the introduction.
	(TUI Commands): Add 'tui enable' and 'tui disable' details.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] gdb: Use NULL not 0 in a tui function.
@ 2015-05-21 21:54 sergiodj+buildbot
  2015-05-22  3:49 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-05-21 21:54 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b75c69bbf05b90a71a3ed7e54ad24ac5ded2ae1e ***

Author: Andrew Burgess <andrew.burgess@embecosm.com>
Branch: master
Commit: b75c69bbf05b90a71a3ed7e54ad24ac5ded2ae1e

gdb: Use NULL not 0 in a tui function.
gdb/ChangeLog:

	* tui/tui-regs.c (tui_reg_next_command): Use NULL not 0.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] gdb: Remove register class specific layout names.
@ 2015-05-21 19:20 sergiodj+buildbot
  2015-05-21 20:35 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-05-21 19:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7bd0be3a9b06dda7a9f3d54402d6f594faa4a1b1 ***

Author: Andrew Burgess <andrew.burgess@embecosm.com>
Branch: master
Commit: 7bd0be3a9b06dda7a9f3d54402d6f594faa4a1b1

gdb: Remove register class specific layout names.
The layout command supports the layout names $FREGS, $GREGS, $SREGS,
and $REGS. The intention of these layout names was to display the tui
register window with a specific set of registers.

First, these layout names no longer work, and haven't for a while, using
any of them will just result in switching to the general register view.

Second there is already the command 'tui reg GROUP' command to set the
displayed register set to GROUP, so making the layout command also
control the register set feels like unnecessary overloading of the
layout command.

This commit removes all code relating to supporting the register set
specific names from the layout command.  Afterwards the user can select
an available layout using the layout command, and control the choice of
register set using the 'tui reg GROUP' command.

gdb/ChangeLog:

	* tui/tui-layout.c (tui_set_layout): Remove
	tui_register_display_type parameter.  Remove all checking of this
	parameter, and reindent function.  Update header comment.
	(tui_set_layout_for_display_command): Rename to...
	(tui_set_layout_by_name): ...this, and don't check for different
	register class types, don't pass a tui_register_display_type to
	tui_set_layout.  Update header comment.
	(layout_names): Remove register set specific names.
	* tui/tui-layout.h (tui_set_layout): Remove
	tui_register_display_type parameter.
	* tui/tui.c (tui_rl_change_windows): Don't pass a
	tui_register_display_type to tui_set_layout.
	(tui_rl_delete_other_windows): Likewise.
	(tui_enable): Likewise.
	* tui/tui-data.h (TUI_FLOAT_REGS_NAME): Remove.
	(TUI_FLOAT_REGS_NAME_LOWER): Remove.
	(TUI_GENERAL_REGS_NAME): Remove.
	(TUI_GENERAL_REGS_NAME_LOWER): Remove.
	(TUI_SPECIAL_REGS_NAME): Remove.
	(TUI_SPECIAL_REGS_NAME_LOWER): Remove.
	(TUI_GENERAL_SPECIAL_REGS_NAME): Remove.
	(TUI_GENERAL_SPECIAL_REGS_NAME_LOWER): Remove.
	(enum tui_register_display_type): Remove.
	(struct tui_layout_def): Remove regs_display_type and
	float_regs_display_type fields.
	(struct tui_data_info): Remove regs_display_type field.
	(tui_layout_command): Use new name for
	tui_set_layout_for_display_command.
	* tui/tui-data.c (layout_def): Don't initialise removed fields.
	(tui_clear_win_detail): Don't initialise removed fields of
	win_info.
	* tui/tui-regs.c (tui_show_registers): Use new name for
	tui_set_layout_for_display_command.
	* tui/tui.h (tui_set_layout_for_display_command): Rename
	declaration to...
	(tui_set_layout_by_name): ...this.
	* printcmd.c (display_command): Remove tui related layout call,
	and reindent.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Skip extra relocations in .rel.plt/.rela.plt
@ 2015-05-20 15:11 sergiodj+buildbot
  2015-05-20 15:42 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-05-20 15:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fca6ae69c41882f5adfba05da7d932b7c8bc2153 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: fca6ae69c41882f5adfba05da7d932b7c8bc2153

Skip extra relocations in .rel.plt/.rela.plt
Extra relocations may be added to the .rel.plt/.rela.plt section, which
are unrelated to PLT.  We should skip them when retrieving PLT entry
symbol values.

	PR binutils/18437
	* elf32-i386.c (elf_i386_get_plt_sym_val): Skip extra relocations
	in .rel.plt/.rela.plt.
	* elf64-x86-64.c (elf_x86_64_get_plt_sym_val): Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] gdb/ada-lang.c: Rename local variable typename into type_name...
@ 2015-05-20  7:46 sergiodj+buildbot
  2015-05-20  8:43 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-05-20  7:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1da0522ea716f4c679cc1fe85c39459417ec2749 ***

Author: Joel Brobecker <brobecker@adacore.com>
Branch: master
Commit: 1da0522ea716f4c679cc1fe85c39459417ec2749

gdb/ada-lang.c: Rename local variable typename into type_name...
... to avoid a build failure when building with C++ compiler
(when configured with --enable-build-with-cxx). We cannot use
"typename" as it is a C++ reserved keyword.

gdb/ChangeLog:

        * ada-lang.c (to_fixed_array_type): Rename local variable
        typename into type_name.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] compile: Fix ASAN crash for gdb.compile/compile.exp
@ 2015-05-19 14:37 sergiodj+buildbot
  2015-05-19 15:39 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-05-19 14:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5fe75eec33c0f55536f09b2f3d692fb688a2c423 ***

Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Branch: master
Commit: 5fe75eec33c0f55536f09b2f3d692fb688a2c423

compile: Fix ASAN crash for gdb.compile/compile.exp
(gdb) PASS: gdb.compile/compile.exp: set unwindonsignal on
compile code *(volatile int *) 0 = 0;
Program received signal SIGSEGV, Segmentation fault.
0x00007ffff7fba426 in _gdb_expr (__regs=0x7ffff7fb8000) at gdb command line:1
1	gdb command line: No such file or directory.
=================================================================
==10462==ERROR: AddressSanitizer: heap-use-after-free on address 0x621000cf7a3d at pc 0x0000004e46b9 bp 0x7ffdeb0f7a40 sp 0x7ffdeb0f71b8
READ of size 10 at 0x621000cf7a3d thread T0
    #0 0x4e46b8 in printf_common(void*, char const*, __va_list_tag*) [clone .isra.6] (/home/jkratoch/redhat/gdb-clean-asan/gdb/gdb+0x4e46
b8)
    #1 0x4f645e in vasprintf (/home/jkratoch/redhat/gdb-clean-asan/gdb/gdb+0x4f645e)
    #2 0xe5cf00 in xstrvprintf common/common-utils.c:120
    #3 0xe74192 in throw_it common/common-exceptions.c:332
    #4 0xe742f6 in throw_verror common/common-exceptions.c:361
    #5 0xddc89e in verror /home/jkratoch/redhat/gdb-clean-asan/gdb/utils.c:541
    #6 0xe734bd in error common/errors.c:43
    #7 0xafa1d6 in call_function_by_hand_dummy /home/jkratoch/redhat/gdb-clean-asan/gdb/infcall.c:1031
    #8 0xe81858 in compile_object_run compile/compile-object-run.c:119
    #9 0xe7733c in eval_compile_command compile/compile.c:577
    #10 0xe7541e in compile_code_command compile/compile.c:153

It is obvious why that happens, dummy_frame_pop() will call compile objfile
cleanup which will free that objfile and NAME then becomes a stale pointer.

> Is there any reason we release OBJFILE in the dummy frame dtor?  Why
> don't we register a cleanup to release in OBJFILE in compile_object_run?
> together with releasing compile_module?  'struct compile_module' has a
> field objfile, which should be released together with
> 'struct compile_module' instead of dummy_frame.

(gdb) break puts
Breakpoint 2 at 0x3830c6fd30: file ioputs.c, line 34.
(gdb) compile code puts("hello")
Breakpoint 2, _IO_puts (str=0x7ffff7ff8000 "hello") at ioputs.c:34
34      {
The program being debugged stopped while in a function called from GDB.
Evaluation of the expression containing the function
(_gdb_expr) will be abandoned.
When the function is done executing, GDB will silently stop.
(gdb) bt
(gdb) _

Now compile_object_run() called from line
	(gdb) compile code puts("hello")
has finished for a long time.  But we still need to have that injected code
OBJFILE valid when GDB is executing it.  Therefore OBJFILE is freed only from
destructor of the frame #1.

At the patched line of call_function_by_hand_dummy() the dummy frame
destructor has not yet been run but it will be run before the fetched NAME
will get used.

gdb/ChangeLog
2015-05-19  Jan Kratochvil  <jan.kratochvil@redhat.com>

	Fix ASAN crash for gdb.compile/compile.exp.
	* infcall.c (call_function_by_hand_dummy): Use xstrdup for NAME.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] compile: gdb_stdout -> gdb_stdlog
@ 2015-05-19 12:47 sergiodj+buildbot
  2015-05-19 14:06 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-05-19 12:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a40635885c50f14782d80251a8966bf4dd271f76 ***

Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Branch: master
Commit: a40635885c50f14782d80251a8966bf4dd271f76

compile: gdb_stdout -> gdb_stdlog
Please send debug output to gdb_stdlog.

OK but gdb/compile/ is using now only gdb_stdout; the error above is due to
a copy-paste.  So I will send a follow-up patch to change all the other
gdb/compile/ gdb_stdout strings to gdb_stdlog.

gdb/ChangeLog
2015-05-19  Jan Kratochvil  <jan.kratochvil@redhat.com>

	* compile/compile-c-symbols.c (convert_symbol_sym, gcc_convert_symbol)
	(gcc_symbol_address): Change gdb_stdout to gdb_stdlog.
	* compile/compile-object-load.c (setup_sections, compile_object_load):
	Likewise.
	* compile/compile.c (compile_to_object): Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix gdb.base/gdbinit-history.exp when HISTSIZE is set in the environment
@ 2015-05-19 10:23 sergiodj+buildbot
  2015-05-19 11:18 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-05-19 10:23 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 84204ed7c0ccaa790dff8e124e710277d9a8abc9 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 84204ed7c0ccaa790dff8e124e710277d9a8abc9

Fix gdb.base/gdbinit-history.exp when HISTSIZE is set in the environment
Some buildslaves are showing that this test is failing.  E.g.,:

 https://sourceware.org/ml/gdb-testers/2015-q2/msg04164.html

The issue is that HISTSIZE is set to 1000 in the environment that runs
the tests (that's the default in Fedora, set in /etc/profile).

We can trivially reproduce it with:

 $ HISTSIZE=1000 make check RUNTESTFLAGS="gdbinit-history.exp"
 (...)
 Running /home/pedro/gdb/mygit/src/gdb/testsuite/gdb.base/gdbinit-history.exp ...
 FAIL: gdb.base/gdbinit-history.exp: show history size
 FAIL: gdb.base/gdbinit-history.exp: show history size
 FAIL: gdb.base/gdbinit-history.exp: show commands

gdb.log shows:
 ...
 (gdb) set height 0
 (gdb) set width 0
 (gdb) show history size
 The size of the command history is 1000.
 (gdb) FAIL: gdb.base/gdbinit-history.exp: show history size

gdb/testsuite/ChangeLog:
2015-05-19  Pedro Alves  <palves@redhat.com>

	* gdb.base/gdbinit-history.exp (test_gdbinit_history_setting):
	Save the whole env array instead of just HOME.  Unset HISTSIZE in
	the environment while testing.  Restore whole environment
	afterwards.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Remove Disp32 from AMD64 direct call/jmp
@ 2015-05-18 11:31 sergiodj+buildbot
  2015-05-18 12:40 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-05-18 11:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 071f0063b422ed1f51a673c817a7656bab3e152f ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 071f0063b422ed1f51a673c817a7656bab3e152f

Remove Disp32 from AMD64 direct call/jmp
	* i386-opc.tbl: Remove Disp32 from AMD64 direct call/jmp.
	* i386-init.h: Regenerated.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [AArch64] Remove X86-64 comments
@ 2015-05-18 10:01 sergiodj+buildbot
  2015-05-18 11:08 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-05-18 10:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 80de0c6d618be3656fa5a82bf445e0cd1b4b16d3 ***

Author: Jiong Wang <jiong.wang@arm.com>
Branch: master
Commit: 80de0c6d618be3656fa5a82bf445e0cd1b4b16d3

[AArch64] Remove X86-64 comments
bfd/
  * elfnn-aarch64.c (elfNN_aarch64_adjust_dynamic_symbol): Rewrite comments.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] sim: erc32: restore attribution
@ 2015-05-17  9:35 sergiodj+buildbot
  2015-05-17 10:02 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-05-17  9:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 296730a52b06fe7dd658924acae1269a54015d52 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 296730a52b06fe7dd658924acae1269a54015d52

sim: erc32: restore attribution


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] compile: Fix uninitialized variable compiler warnings
@ 2015-05-16 20:42 sergiodj+buildbot
  2015-05-16 22:11 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-05-16 20:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d976bace1c68aed43311651c1033c23b3c983094 ***

Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Branch: master
Commit: d976bace1c68aed43311651c1033c23b3c983094

compile: Fix uninitialized variable compiler warnings
gdb/ChangeLog
2015-05-16  Jan Kratochvil  <jan.kratochvil@redhat.com>

	* compile/compile-object-load.c (get_out_value_type): Fix uninitialized
	variable compiler warnings.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Add support for unbuffered and zero sized Guile ports.
@ 2015-05-16 19:57 sergiodj+buildbot
  2015-05-17  0:03 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-05-16 19:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 37442ce10aaa2f84d245631d38e25ee47e5057aa ***

Author: Doug Evans <xdje42@gmail.com>
Branch: master
Commit: 37442ce10aaa2f84d245631d38e25ee47e5057aa

Add support for unbuffered and zero sized Guile ports.
gdb/ChangeLog

	* NEWS: Mention support for unbuffered Guile memory ports.
	* scm-ports.c (ioscm_memory_port): Update comments on end, size.
	(ioscm_lseek_address): Improve overflow calculation.
	(gdbscm_memory_port_fill_input): Add assert.
	(gdbscm_memory_port_write): Handle unbuffered ports.
	Handle large writes identical to Guile's fport_write.
	(gdbscm_memory_port_seek): Fix seeking past end check.
	(gdbscm_memory_port_close): Handle closing unbuffered port.
	(ioscm_parse_mode_bits): Recognize "0" for unbuffered ports.
	(ioscm_init_memory_port): Handle unbuffered ports.
	(ioscm_reinit_memory_port): Ditto.
	(ioscm_init_memory_port): Update size calculation.
	(gdbscm_open_memory): Support zero sized ports.

gdb/testsuite/ChangeLog

	* gdb.guile/scm-ports.c: New file.
	* gdb.guile/scm-ports.exp: Add memory port tests.

gdb/doc/ChangeLog

	* guile.texi (Memory Ports in Guile): Document support for unbuffered
	memory ports.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Don't generate PLT relocations for now binding
@ 2015-05-16 15:35 sergiodj+buildbot
  2015-05-16 20:50 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-05-16 15:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 25070364b0ce33eed46aa5d78ebebbec6accec7e ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 25070364b0ce33eed46aa5d78ebebbec6accec7e

Don't generate PLT relocations for now binding
There is no need for PLT relocations with -z now. We can use GOT
relocations, which take less space, instead and replace 16-byte .plt
entres with 8-byte .plt.got entries.

bfd/

	* elf32-i386.c (elf_i386_check_relocs): Create .plt.got section
	for now binding.
	(elf_i386_allocate_dynrelocs): Use .plt.got section for now
	binding.
	* elf64-x86-64.c (elf_x86_64_check_relocs): Create .plt.got
	section for now binding.
	(elf_x86_64_allocate_dynrelocs): Use .plt.got section for now
	binding.

ld/testsuite/

	* ld-i386/i386.exp: Run PR ld/17689 tests with -z now.
	* ld-x86-64/x86-64.exp: Likewise
	* ld-i386/pr17689now.rd: New file.
	* ld-x86-64/pr17689now.rd: Likewise


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] compile: Fix detected inferior type
@ 2015-05-16 15:20 sergiodj+buildbot
  2015-05-16 20:32 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-05-16 15:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4d18dfad9edf822df205edc2c1fe3fe9f1e467b8 ***

Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Branch: master
Commit: 4d18dfad9edf822df205edc2c1fe3fe9f1e467b8

compile: Fix detected inferior type
gdb/ChangeLog
2015-05-16  Jan Kratochvil  <jan.kratochvil@redhat.com>

	* compile/compile-object-load.c (get_out_value_type): Fix returned type.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] compile: New 'compile print'
@ 2015-05-16 15:07 sergiodj+buildbot
  2015-05-16 20:14 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-05-16 15:07 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 36de76f9cc2eea0bd5f1b7ce74ef60e1aa0b27c2 ***

Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Branch: master
Commit: 36de76f9cc2eea0bd5f1b7ce74ef60e1aa0b27c2

compile: New 'compile print'
It is planned the existing GDB command 'print' will be able to evaluate its
expressions using the compiler.  There will be some option to choose between
the existing GDB evaluation and the compiler evaluation.  But as an
intermediate step this patch provides the expression printing feature as a new
command.

I can imagine it could be also called 'maintenance compile print' as in the
future one should be able to use its functionality by the normal 'print'
command.

There was a discussion with Eli about the command name:
	https://sourceware.org/ml/gdb-patches/2015-03/msg00880.html
As there were no other comments yet I haven't renamed it yet, before there is
some confirmation about settlement on the final name.

Support for the GDB '@' operator to create arrays has been submitted for GCC:
	[gcc patch] libcc1: '@' GDB array operator
	https://gcc.gnu.org/ml/gcc-patches/2015-03/msg01451.html


gdb/ChangeLog
2015-05-16  Jan Kratochvil  <jan.kratochvil@redhat.com>
	    Phil Muldoon  <pmuldoon@redhat.com>

	* NEWS (Changes since GDB 7.9): Add compile print.
	* compile/compile-c-support.c (add_code_header, add_code_footer)
	(c_compute_program): Add COMPILE_I_PRINT_ADDRESS_SCOPE and
	COMPILE_I_PRINT_VALUE_SCOPE.
	* compile/compile-internal.h (COMPILE_I_PRINT_OUT_ARG_TYPE)
	(COMPILE_I_PRINT_OUT_ARG, COMPILE_I_EXPR_VAL, COMPILE_I_EXPR_PTR_TYPE):
	New.
	* compile/compile-object-load.c: Include block.h.
	(get_out_value_type): New function.
	(compile_object_load): Handle COMPILE_I_PRINT_ADDRESS_SCOPE and
	COMPILE_I_PRINT_VALUE_SCOPE.  Set compile_module's OUT_VALUE_ADDR and
	OUT_VALUE_TYPE.
	* compile/compile-object-load.h (struct compile_module): Add fields
	out_value_addr and out_value_type.
	* compile/compile-object-run.c: Include valprint.h and compile.h.
	(struct do_module_cleanup): Add fields out_value_addr and
	out_value_type.
	(do_module_cleanup): Handle COMPILE_I_PRINT_ADDRESS_SCOPE and
	COMPILE_I_PRINT_VALUE_SCOPE.
	(compile_object_run): Propagate out_value_addr and out_value_type.
	Pass OUT_VALUE_ADDR.
	* compile/compile.c: Include valprint.h.
	(compile_print_value, compile_print_command): New functions.
	(eval_compile_command): Handle failed COMPILE_I_PRINT_ADDRESS_SCOPE.
	(_initialize_compile): Update compile code help text.  Install
	compile_print_command.
	* compile/compile.h (compile_print_value): New prototype.
	* defs.h (enum compile_i_scope_types): Add
	COMPILE_I_PRINT_ADDRESS_SCOPE and COMPILE_I_PRINT_VALUE_SCOPE.

gdb/doc/ChangeLog
2015-05-16  Jan Kratochvil  <jan.kratochvil@redhat.com>

	* gdb.texinfo (Compiling and Injecting Code): Add compile print.

gdb/testsuite/ChangeLog
2015-05-16  Jan Kratochvil  <jan.kratochvil@redhat.com>

	* gdb.compile/compile-print.c: New file.
	* gdb.compile/compile-print.exp: New file.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] compile: Add one debug message
@ 2015-05-16 12:38 sergiodj+buildbot
  2015-05-16 13:05 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-05-16 12:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b6de3f9642c58439c31690255c3a4326728da88d ***

Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Branch: master
Commit: b6de3f9642c58439c31690255c3a4326728da88d

compile: Add one debug message
gdb/ChangeLog
2015-05-16  Jan Kratochvil  <jan.kratochvil@redhat.com>

	* compile/compile-object-load.c (compile_object_load): Add
	COMPILE_DEBUG message.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Array indexed by non-contiguous enumeration types
@ 2015-05-15 22:25 sergiodj+buildbot
  2015-05-15 23:54 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-05-15 22:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT aa7151351ed16c5a4eb1334c9a1af1b06dbb7a99 ***

Author: Jerome Guitton <guitton@adacore.com>
Branch: master
Commit: aa7151351ed16c5a4eb1334c9a1af1b06dbb7a99

Array indexed by non-contiguous enumeration types
In Ada, index types of arrays can be enumeration types, and enumeration
types can be non-contiguous. In which case the address of elements is
not given by the value of the index, but by its position in the enumeration
type.

In other words, in this example:

 type Color is (Blue, Red);
 for Color use (Blue => 8, Red => 12, Green => 16);

 type A is array (Color) of Integer;
 type B is array (1 .. 3) of Integer;

Arrays of type A and B will have the same layout in memory, even if
the enumeration Color has a hole in its set of integer value.

Since recently support for such a feature was in ada-lang.c, where the
array was casted to a regular continuous index range. We were losing
the information of index type. And this was not quite working for
subranges in variable-length fields; their bounds are expressed using
the integer value of the bounds, not its position in the enumeration,
and there was some confusion all over ada-lang.c as to whether we had
the position or the integer value was used for indexes.

The idea behind this patch is to clean this up by keeping the real
representation of these array index types and bounds when representing
the value, and only use the position when accessing the elements or
computing the length. This first patch fixes the printing of such
an array.

To the best of my knowledge, this feature only exists in Ada so it
should only affect this language.

gdb/ChangeLog:

        Jerome Guitton  <guitton@adacore.com>:
        * ada-lang.c (ada_value_ptr_subscript): Use enum position of
        index to get element instead of enum value.
        (ada_value_slice_from_ptr, ada_value_slice): Use enum position
        of index to compute length, but enum values to compute bounds.
        (ada_array_length): Use enum position of index instead of enum value.
        (pos_atr): Move position computation to...
        (ada_evaluate_subexp): Use enum values to compute bounds.
        * gdbtypes.c (discrete_position): ...this new function.
        * gdbtypes.h (discrete_position): New function declaration.
        * valprint.c (val_print_array_elements): Call discrete_position
        to handle array indexed by non-contiguous enumeration types.

gdb/testsuite/ChangeLog:

        * gdb.ada/arr_enum_with_gap: New testcase.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix build gdbserver build errors on arm, mips, aarch64.
@ 2015-05-14 20:35 sergiodj+buildbot
  2015-05-14 21:53 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-05-14 20:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 61a7418ccb7c2de12d4c4df79e193f32db938a11 ***

Author: Don Breazeal <donb@codesourcery.com>
Branch: master
Commit: 61a7418ccb7c2de12d4c4df79e193f32db938a11

Fix build gdbserver build errors on arm, mips, aarch64.
Fix build errors introduced by
https://sourceware.org/ml/gdb-patches/2015-05/msg00281.html, which
didn't account for the change of the name of the struct process_info
field 'private' to 'priv' made in
https://sourceware.org/ml/gdb-patches/2015-02/msg00829.html.

gdb/gdbserver/ChangeLog:

	* linux-aarch64-low.c (aarch64_linux_new_fork): Change reference
	to process_info.private to process_info.priv.
	* linux-arm-low.c (arm_new_fork): Likewise.
	* linux-mips-low.c (mips_linux_new_fork): Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix gdbserver build failure on arm-android.
@ 2015-05-14 14:17 sergiodj+buildbot
  2015-05-14 19:23 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-05-14 14:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1041a03c1b4d03c39033c8bb942148dc3e4b4acc ***

Author: Joel Brobecker <brobecker@adacore.com>
Branch: master
Commit: 1041a03c1b4d03c39033c8bb942148dc3e4b4acc

Fix gdbserver build failure on arm-android.
The following patch...

| proc-service, extern "C"
|
| libthread_db.so calls symbols in the client (GDB), through the
| proc-service interface.  These routines must have extern "C" linkage
| so their symbol names are not mangled when GDB is built as a C++
| program.  On the GDBserver side, we were missing fallback declarations for
| all these symbols.
|
| gdb/ChangeLog:
|
|     * gdb_proc_service.h: Wrap with EXTERN_C_PUSH/EXTERN_C_POP.
|
| gdb/gdbserver/ChangeLog:
| 2015-02-27  Pedro Alves  <palves@redhat.com>
|
|     * gdb_proc_service.h: Wrap with EXTERN_C_PUSH/EXTERN_C_POP.
|     [!HAVE_PROC_SERVICE_H] (struct ps_prochandle): Forward declare.
|     [!HAVE_PROC_SERVICE_H] (ps_pdread, ps_pdwrite, ps_ptread)
|     ps_ptwrite, ps_lgetregs, ps_lsetregs, ps_lgetfpregs)
|     (ps_lsetfpregs, ps_getpid)
|     (ps_get_thread_area, ps_pglobal_lookup, ps_pstop, ps_pcontinue)
|     (ps_lstop, ps_lcontinue, ps_lgetxregsize, ps_lgetxregs)
|     (ps_lsetxregs, ps_plog): Declare.

... added a number of declarations which do not compile when cross-
compiling GDBserver on arm-android. The problem comes from type
prfpregset_t not being declared:

    /[...]/gdbserver/gdb_proc_service.h:98:47:
    error: unknown type name 'prfpregset_t'

After searching through the includes of the install we have,
I could not find that type being declared anywhere. So I did
the same as for prgregset_t, and created the typedef if the
type isn't declared.

gdb/gdbserver/ChangeLog:

        * configure.ac: Add prfpregset_t BFD_HAVE_SYS_PROCFS_TYPE check.
        * configure, config.in: Regenerate.
        * gdb_proc_service.h [HAVE_PRFPREGSET_T] (prfpregset_t):
        Declare typedef.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Remove buggy xterm workaround in tui_dispatch_ctrl_char()
@ 2015-05-14 12:20 sergiodj+buildbot
  2015-05-14 17:30 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-05-14 12:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e3555239e04fa6dba2a165b3b52598a880474a22 ***

Author: Patrick Palka <patrick@parcs.ath.cx>
Branch: master
Commit: e3555239e04fa6dba2a165b3b52598a880474a22

Remove buggy xterm workaround in tui_dispatch_ctrl_char()
The function tui_dispatch_ctrl_char() has an old workaround (from 1999)
for buggy terminals and/or ncurses library that don't return page
up/down keys as single characters.  Because the workaround is so old, I
think the bug it is targetting is no longer relevant anymore.

But more importantly, the workaround is itself buggy: it 1) performs a
blocking call to wgetch() and 2) if the key returned by wgetch() does
not make up a relevant key sequence it throws away the input instead of
pushing it back via ungetch().  And indeed the workaround breaks Alt-key
sequences under TERM=xterm because of bug #2.

So this patch removes the buggy workaround and tidies up the function
accordingly.

I personally tested this change on a recent xterm (with TERM=xterm) in
Fedora 20 and had no problems with having ncurses properly interpret
page up/down keys.  And Alt-key sequences now work when TERM=xterm too.

gdb/ChangeLog:

	* tui/tui-command.c: Remove include of <ctype.h>.
	(tui_dispatch_ctrl_char): Remove workaround for xterm terminals.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [AArch64] Remove BFD overflow check restrictions
@ 2015-05-14 11:50 sergiodj+buildbot
  2015-05-14 15:38 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-05-14 11:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fdc3b1b1ef461fb81a53c9ce95117e5f134fc828 ***

Author: Jiong Wang <jiong.wang@arm.com>
Branch: master
Commit: fdc3b1b1ef461fb81a53c9ce95117e5f134fc828

[AArch64] Remove BFD overflow check restrictions
bfd/
  * elfnn-aarch64.c (elfNN_aarch64_relocate_section): Remove overflow
  check restriction.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] dwarf2read.c (die_needs_namespace): Return 1 for DW_TAG_inlined_subroutine.
@ 2015-05-13 21:11 sergiodj+buildbot
  2015-05-14 12:13 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-05-13 21:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 08a76f8ab86efbd5c85c9bd3979c4c06b9e84258 ***

Author: Martin Galvan <martin.galvan@tallertechnologies.com>
Branch: master
Commit: 08a76f8ab86efbd5c85c9bd3979c4c06b9e84258

dwarf2read.c (die_needs_namespace): Return 1 for DW_TAG_inlined_subroutine.
gdb/ChangeLog:

	* dwarf2read.c (die_needs_namespace): Return 1 for
	DW_TAG_inlined_subroutine.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] dwarf2read.c (die_needs_namespace): Return 1 for DW_TAG_inlined_subroutine.
@ 2015-05-13 20:59 sergiodj+buildbot
  2015-05-14  9:38 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-05-13 20:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT da0580a62bff4cdfa53ef6b491f5158cc7a5744a ***

Author: Doug Evans <dje@google.com>
Branch: master
Commit: da0580a62bff4cdfa53ef6b491f5158cc7a5744a

dwarf2read.c (die_needs_namespace): Return 1 for DW_TAG_inlined_subroutine.
gdb/ChangeLog:

	* dwarf2read.c (die_needs_namespace): Return 1 for
	DW_TAG_inlined_subroutine.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Make regcache_cpy_no_passthrough static
@ 2015-05-13 18:54 sergiodj+buildbot
  2015-05-14  8:06 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-05-13 18:54 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bd49952bd7fbe616e2cb488e8080502f2338aaa2 ***

Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Branch: master
Commit: bd49952bd7fbe616e2cb488e8080502f2338aaa2

Make regcache_cpy_no_passthrough static
regcache_cpy_no_passthrough is no longer used for a standalone call.

gdb/ChangeLog
2015-05-13  Jan Kratochvil  <jan.kratochvil@redhat.com>

	* regcache.c (regcache_cpy_no_passthrough): New declaration.
	(regcache_cpy_no_passthrough): Make it static, add function comment.
	* regcache.h (regcache_dup, regcache_cpy): Reduce/update their comment.
	(regcache_cpy_no_passthrough): Remove declaration.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] infcall: stop_registers -> register_dummy_frame_dtor
@ 2015-05-13 18:53 sergiodj+buildbot
  2015-05-14  5:01 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-05-13 18:53 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8a6c40311297f60ad13827650fdde13da301b505 ***

Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Branch: master
Commit: 8a6c40311297f60ad13827650fdde13da301b505

infcall: stop_registers -> register_dummy_frame_dtor
With dummy_frame destructors GDB no longer has to use global stop_registers.
dummy_frame's registers can be now stored associated with their specific
dummy_frame.

gdb/ChangeLog
2015-05-13  Jan Kratochvil  <jan.kratochvil@redhat.com>

	* infcall.c (struct dummy_frame_context_saver)
	(dummy_frame_context_saver_data_free, dummy_frame_context_saver_dtor)
	(dummy_frame_context_saver_drop, dummy_frame_context_saver_cleanup)
	(dummy_frame_context_saver_get_regs, dummy_frame_context_saver_setup):
	New.
	(call_function_by_hand_dummy): Move discard_cleanups of
	inf_status_cleanup before dummy_frame_push.  Call
	dummy_frame_context_saver_setup and prepare context_saver_cleanup.
	Use dummy_frame_context_saver_get_regs instead of stop_registers.
	* infcall.h (struct dummy_frame_context_saver)
	(dummy_frame_context_saver_drop, dummy_frame_context_saver_cleanup)
	(dummy_frame_context_saver_get_regs, dummy_frame_context_saver_setup):
	New declarations.
	* infcmd.c: Include infcall.h.
	(get_return_value): Add parameter ctx_saver, use it instead of
	stop_registers.
	(print_return_value): Add parameter ctx_saver, pass it.
	(struct finish_command_continuation_args): Add field ctx_saver.
	(finish_command_continuation): Update print_return_value caller.
	(finish_command_continuation_free_arg): Free also ctx_saver.
	(finish_forward): Call dummy_frame_context_saver_setup.
	* inferior.h (struct dummy_frame_context_saver): New declaration.
	(get_return_value): Add parameter ctx_saver.
	* python/py-finishbreakpoint.c (bpfinishpy_pre_stop_hook): Update
	get_return_value caller.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Remove stop_registers
@ 2015-05-13 18:53 sergiodj+buildbot
  2015-05-14  6:34 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-05-13 18:53 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 46c03469b37d2ccb6a1eaa3ea4e21c57d07246fc ***

Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Branch: master
Commit: 46c03469b37d2ccb6a1eaa3ea4e21c57d07246fc

Remove stop_registers
Now stop_registers are no longer used and it can be removed.

I am not much sure what 'proceed_to_finish' really means now so I make a wild
guess while updating comments about it.

gdb/ChangeLog
2015-05-13  Jan Kratochvil  <jan.kratochvil@redhat.com>

	* gdbthread.h (struct thread_control_state): Update comment for
	proceed_to_finish.
	* infcall.c (run_inferior_call): Update comment about
	proceed_to_finish.
	* infcmd.c (get_return_value): Update comment about stop_registers.
	(finish_forward): Update comment about proceed_to_finish.
	* infrun.c (stop_registers): Remove.
	(clear_proceed_status, normal_stop): Remove stop_registers handling.
	* infrun.h (stop_registers): Remove.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Call dummy_frame_dtor_ftype also from remove_dummy_frame
@ 2015-05-13 18:53 sergiodj+buildbot
  2015-05-14  1:27 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-05-13 18:53 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5e9705017f5b257421136b8d7752b9c793335ace ***

Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Branch: master
Commit: 5e9705017f5b257421136b8d7752b9c793335ace

Call dummy_frame_dtor_ftype also from remove_dummy_frame
There was now a leak-like bug that if dummy_frame "disappeared" by
remove_dummy_frame then its destructor was not called.  For example in the case
of 'compile code' dummy frames the injected objfile would never get freed after
some inferior longjmp out of the injected code.

gdb/ChangeLog
2015-05-13  Jan Kratochvil  <jan.kratochvil@redhat.com>

	* compile/compile-object-run.c (do_module_cleanup): Add parameter
	registers_valid.
	(compile_object_run): Update do_module_cleanup caller.
	* dummy-frame.c: Include infcall.h.
	(struct dummy_frame): Update dtor comment.
	(remove_dummy_frame): Call dtor.
	(pop_dummy_frame): Update dtor caller.
	* dummy-frame.h (dummy_frame_dtor_ftype): Add parameter
	registers_valid.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] register_dummy_frame_dtor: Permit multiple dtors
@ 2015-05-13 18:53 sergiodj+buildbot
  2015-05-14  3:21 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-05-13 18:53 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 109896905babca2d99e13f74bc887acf14cd1ab7 ***

Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Branch: master
Commit: 109896905babca2d99e13f74bc887acf14cd1ab7

register_dummy_frame_dtor: Permit multiple dtors
Later patch needs two independent destructors for the same dummy_frame.
Therefore the registrar has been extended to an arbitrary number of
destructors.

gdb/ChangeLog
2015-05-13  Jan Kratochvil  <jan.kratochvil@redhat.com>

	* dummy-frame.c (struct dummy_frame_dtor_list): New.
	(struct dummy_frame): Replace dtor and dtor_data by dtor_list.
	(remove_dummy_frame): Process dtor_list.
	(pop_dummy_frame): Process dtor_list.
	(register_dummy_frame_dtor): Maintain dtor_list.
	(find_dummy_frame_dtor): Handle dtor_list.
	* dummy-frame.h (register_dummy_frame_dtor, find_dummy_frame_dtor):
	Update comments.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] gdb/NEWS: Move "Xmethods can now specify a result type" to GDB 7.9.1 section.
@ 2015-05-13 17:35 sergiodj+buildbot
  2015-05-13 21:32 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-05-13 17:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f5f85ab95ff104eae872622ab3e2ad30a2b3d47a ***

Author: Joel Brobecker <brobecker@adacore.com>
Branch: master
Commit: f5f85ab95ff104eae872622ab3e2ad30a2b3d47a

gdb/NEWS: Move "Xmethods can now specify a result type" to GDB 7.9.1 section.
As this change was ported to GDB 7.9.1, the NEWS entry is moved to
a newly-created "Changes in GDB 7.9.1" section, matching the NEWS
file which is going to be distributed with the GDB 7.9.1 release.

gdb/ChangeLog:

        * NEWS: Create "Changes in GDB 7.9.1" section.  Move news about
        Xmethods now being able to specify a result type to that new
        section.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Disable the configuration of GDB for HPUX targets.
@ 2015-05-13 16:35 sergiodj+buildbot
  2015-05-13 19:54 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-05-13 16:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5569a85f45e4df3563254cea4caa02c7cb092480 ***

Author: John David Anglin <dave.anglin@bell.net>
Branch: master
Commit: 5569a85f45e4df3563254cea4caa02c7cb092480

Disable the configuration of GDB for HPUX targets.
	* configure.ac: Disable configuration of GDB for HPUX targets.
	* configure: Regenerate.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Avoid race condition when handling a SIGWINCH signal
@ 2015-05-13 15:59 sergiodj+buildbot
  2015-05-13 18:19 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-05-13 15:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1e04046d0b7e0f87bc6e2fefd966c9dd89d2ce13 ***

Author: Patrick Palka <patrick@parcs.ath.cx>
Branch: master
Commit: 1e04046d0b7e0f87bc6e2fefd966c9dd89d2ce13

Avoid race condition when handling a SIGWINCH signal
The control variable win_resized must be cleared before responding to
it.

Otherwise there is a small window where another SIGWINCH might occur in
between the handling of an earlier SIGWINCH and the clearing of
win_resized, at which point win_resized would be set (again) by the
signal handler.  Shortly thereafter we would clear win_resized even
though we only handled the earlier SIGWINCH but not the latest one.
This chain of events is all avoided if we clear win_resized first.

gdb/ChangeLog:

	* tui/tui-win.c (tui_async_resize_screen): Clear win_resized
	first before resizing the window.
	* tui.c (tui_enable): Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] dummy_frame_dtor_ftype vs. call_function_by_hand_dummy_dtor_ftype cleanup
@ 2015-05-13 13:59 sergiodj+buildbot
  2015-05-13 16:44 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-05-13 13:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 558e5469679897ee57ad6706074f55ff4952cf43 ***

Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Branch: master
Commit: 558e5469679897ee57ad6706074f55ff4952cf43

dummy_frame_dtor_ftype vs. call_function_by_hand_dummy_dtor_ftype cleanup
Both dummy_frame_dtor_ftype and call_function_by_hand_dummy_dtor_ftype
represent the same type, there was some mistake/duplication during check-in.

gdb/ChangeLog
2015-05-08  Jan Kratochvil  <jan.kratochvil@redhat.com>

	* dummy-frame.c (struct dummy_frame): Use proper typedef for dtor.
	* dummy-frame.h (dummy_frame_dtor_ftype): Add its comment.
	* infcall.c (call_function_by_hand_dummy): Use proper typedef for
	dummy_dtor parameter.
	* infcall.h: Include dummy-frame.h.
	(call_function_by_hand_dummy_dtor_ftype): Remove.
	(call_function_by_hand_dummy): Use proper typedef for dummy_dtor
	parameter.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Allocate the first .plt entry space only if needed
@ 2015-05-12 20:17 sergiodj+buildbot
  2015-05-13  4:55 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-05-12 20:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a3747075ae478f27bf3e0643021a85fb6cdad0e3 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: a3747075ae478f27bf3e0643021a85fb6cdad0e3

Allocate the first .plt entry space only if needed
Commit dd7e64d45b317128f5fe813a8da0b13b4ad046ae may optimize out
i386/x86-64 JUMP_SLOT relocation.  If there is no JUMP_SLOT relocation
left, we don't need to the first .plt entry.  This patch allocates
space for the first .plt entry only if we also reserve space for a PLT
slot for JUMP_SLOT relocation.

bfd/

	* elf32-i386.c (elf_i386_allocate_dynrelocs): Allocate space
	for the first .plt entry only if needed.
	* elf64-x86-64.c (elf_x86_64_allocate_dynrelocs): Likewise.

ld/testsuite/

	* ld-i386/i386.exp: Run pltgot-1 for Linux targets.
	* ld-x86-64/x86-64.exp: Likewise.
	* ld-i386/pltgot-1.d: New file.
	* ld-i386/pltgot-1.s: Likewise.
	* ld-x86-64/pltgot-1.d: Likewise.
	* ld-x86-64/pltgot-1.s: Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Extended-remote fork catch
@ 2015-05-12 17:21 sergiodj+buildbot
  2015-05-13  0:29 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-05-12 17:21 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cbb8991cabdd85b7828f59c92f754c5a2101b0b6 ***

Author: Don Breazeal <donb@codesourcery.com>
Branch: master
Commit: cbb8991cabdd85b7828f59c92f754c5a2101b0b6

Extended-remote fork catch
This patch implements catchpoints for fork events on extended-remote
Linux targets.

Implementation appeared to be straightforward, requiring four new functions
in remote.c to implement insert/remove of fork/vfork catchpoints.  These
functions are essentially stubs that just return 0 ('success') if the
required features are enabled.  If the fork events are being reported, then
catchpoints are set and hit.

However, there are some extra issues that arise with catchpoints.

1) Thread creation reporting -- fork catchpoints are hit before the
   follow_fork has been completed.  When stopped at a fork catchpoint
   in the native implementation, the new process is not 'reported'
   until after the follow is done.  It doesn't show up in the inferiors
   list or the threads list.  However, in the gdbserver case, an
   'info threads' while stopped at a fork catchpoint will retrieve the
   new thread info from the target and add it to GDB's data structures,
   prior to the follow operations.  Because of this premature report,
   things on the GDB side eventually get very confused.

   So in remote.c:remote_update_thread_list, we check to see if there
   are any pending fork parent threads.  If there are we remove the
   related fork child thread from the thread list sent by the target.

2) Kill process before fork is followed -- on the native side in
   linux-nat.c:linux_nat_kill, there is some code to handle the case where
   a fork has occurred but follow_fork hasn't been called yet.  It does
   this by using the last status to determine if a follow is pending, and
   if it is, to kill the child task.  The use of last_status is fragile
   in situations like non-stop mode where other events may have occurred
   after the fork event.  This patch identifies a fork parent
   in remote.c:extended_remote_kill in a way similar to that used in
   thread creation reporting above.  If one is found, it kills the new
   child as well.

Tested on x64 Ubuntu Lucid, native, remote, extended-remote.  Tested the
case of killing the forking process before the fork has been followed
manually.

gdb/ChangeLog:
        * remote.c (remote_insert_fork_catchpoint): New function.
        (remote_remove_fork_catchpoint): New function.
        (remote_insert_vfork_catchpoint): New function.
        (remote_remove_vfork_catchpoint): New function.
        (pending_fork_parent_callback): New function.
        (remove_new_fork_child): New function.
        (remote_update_thread_list): Call remote_notif_get_pending_events
        and remove_new_fork_child.
        (extended_remote_kill): Kill fork child when killing the
        parent before follow_fork completes.
        (init_extended_remote_ops): Initialize target vector with
        new fork catchpoint functions.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Extended-remote fork event docs
@ 2015-05-12 17:21 sergiodj+buildbot
  2015-05-13  2:24 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-05-12 17:21 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0d71eef55dc5ce12d9bfa3cefb40d81a9b5fa2e6 ***

Author: Don Breazeal <donb@codesourcery.com>
Branch: master
Commit: 0d71eef55dc5ce12d9bfa3cefb40d81a9b5fa2e6

Extended-remote fork event docs
This patch contains the accumulated documentation changes for the
rest of the extended-remote follow fork patchset.

gdb/ChangeLog:

        * NEWS: Announce fork support in the RSP and support
          for fork debugging in extended mode.

gdb/doc/ChangeLog:

        * gdb.texinfo (Forks): Note that fork debugging is
          supported in extended mode.
          (Remote Configuration): Add fork event features to table
          of packet settings.
          (Stop Reply Packets): Add fork events to list of stop reasons.
          (General Query Packets): Add fork events to tables of
          'gdbfeatures' and 'stub features' supported in the qSupported
          packet, as well as to the list containing stub feature
          details.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Extended-remote Linux follow fork
@ 2015-05-12 17:20 sergiodj+buildbot
  2015-05-12 21:14 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-05-12 17:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT de0d863ec3fda88e488cee568f943c7998b68862 ***

Author: Don Breazeal <donb@codesourcery.com>
Branch: master
Commit: de0d863ec3fda88e488cee568f943c7998b68862

Extended-remote Linux follow fork
This patch implements basic support for follow-fork and detach-on-fork on
extended-remote Linux targets.  Only 'fork' is supported in this patch;
'vfork' support is added n a subsequent patch.  This patch depends on
the previous patches in the patch series.

Sufficient extended-remote functionality has been implemented here to pass
gdb.base/multi-forks.exp, as well as gdb.base/foll-fork.exp with the
catchpoint tests commented out.  Some other fork tests fail with this
patch because it doesn't provide the architecture support needed for
watchpoint inheritance or fork catchpoints.

The implementation follows the same general structure as for the native
implementation as much as possible.

This implementation includes:
 * enabling fork events in linux-low.c in initialize_low and
   linux_enable_extended_features

 * handling fork events in gdbserver/linux-low.c:handle_extended_wait

   - when a fork event occurs in gdbserver, we must do the full creation
     of the new process, thread, lwp, and breakpoint lists.  This is
     required whether or not the new child is destined to be
     detached-on-fork, because GDB will make target calls that require all
     the structures.  In particular we need the breakpoint lists in order
     to remove the breakpoints from a detaching child.  If we are not
     detaching the child we will need all these structures anyway.

   - as part of this event handling we store the target_waitstatus in a new
     member of the parent lwp_info structure, 'waitstatus'.  This
     is used to store extended event information for reporting to GDB.

   - handle_extended_wait is given a return value, denoting whether the
     handled event should be reported to GDB.  Previously it had only
     handled clone events, which were never reported.

 * using a new predicate in gdbserver to control handling of the fork event
   (and eventually all extended events) in linux_wait_1.  The predicate,
   extended_event_reported, checks a target_waitstatus.kind for an
   extended ptrace event.

 * implementing a new RSP 'T' Stop Reply Packet stop reason: "fork", in
   gdbserver/remote-utils.c and remote.c.

 * implementing new target and RSP support for target_follow_fork with
   target extended-remote.  (The RSP components were actually defined in
   patch 1, but they see their first use here).

   - remote target routine remote_follow_fork, which just sends the 'D;pid'
     detach packet to detach the new fork child cleanly.  We can't just
     call target_detach because the data structures for the forked child
     have not been allocated on the host side.

Tested on x64 Ubuntu Lucid, native, remote, extended-remote.

gdb/gdbserver/ChangeLog:

        * linux-low.c (handle_extended_wait): Implement return value,
        rename argument 'event_child' to 'event_lwp', handle
        PTRACE_EVENT_FORK, call internal_error for unrecognized event.
        (linux_low_ptrace_options): New function.
        (linux_low_filter_event): Call linux_low_ptrace_options,
        use different argument fo linux_enable_event_reporting,
        use return value from handle_extended_wait.
        (extended_event_reported): New function.
        (linux_wait_1): Call extended_event_reported and set
        status to report fork events.
        (linux_write_memory): Add pid to debug message.
        (reset_lwp_ptrace_options_callback): New function.
        (linux_handle_new_gdb_connection): New function.
        (linux_target_ops): Initialize new structure member.
        * linux-low.h (struct lwp_info) <waitstatus>: New member.
        * lynx-low.c: Initialize new structure member.
        * remote-utils.c (prepare_resume_reply): Implement stop reason
        "fork" for "T" stop message.
        * server.c (handle_query): Call handle_new_gdb_connection.
        * server.h (report_fork_events): Declare global flag.
        * target.h (struct target_ops) <handle_new_gdb_connection>:
        New member.
        (target_handle_new_gdb_connection): New macro.
        * win32-low.c: Initialize new structure member.

gdb/ChangeLog:

        * linux-nat.c (linux_nat_ptrace_options): New function.
        (linux_init_ptrace, wait_lwp, linux_nat_filter_event):
        Call linux_nat_ptrace_options and use different argument to
        linux_enable_event_reporting.
        (_initialize_linux_nat): Delete call to
        linux_ptrace_set_additional_flags.
        * nat/linux-ptrace.c (current_ptrace_options): Rename to
        supported_ptrace_options.
        (additional_flags): Delete variable.
        (linux_check_ptrace_features): Use supported_ptrace_options.
        (linux_test_for_tracesysgood, linux_test_for_tracefork):
        Likewise, and remove additional_flags check.
        (linux_enable_event_reporting): Change 'attached' argument to
        'options'.  Use supported_ptrace_options.
        (ptrace_supports_feature): Change comment.  Use
        supported_ptrace_options.
        (linux_ptrace_set_additional_flags): Delete function.
        * nat/linux-ptrace.h (linux_ptrace_set_additional_flags):
        Delete function prototype.
        * remote.c (remote_fork_event_p): New function.
        (remote_detach_pid): New function.
        (remote_detach_1): Call remote_detach_pid, don't mourn inferior
        if doing detach-on-fork.
        (remote_follow_fork): New function.
        (remote_parse_stop_reply): Handle new "T" stop reason "fork".
        (remote_pid_to_str): Print "process" strings for pid/0/0 ptids.
        (init_extended_remote_ops): Initialize to_follow_fork.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Remove Disp16|Disp32 from 64-bit direct branches
@ 2015-05-11 21:37 sergiodj+buildbot
  2015-05-11 22:08 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-05-11 21:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 70cead076728d1bc0d905b32fcb0c44c25f00ccc ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 70cead076728d1bc0d905b32fcb0c44c25f00ccc

Remove Disp16|Disp32 from 64-bit direct branches
Disp16 and Disp32 aren't supported by direct branches in 64-bit mode.
This patch removes them from 64-bit direct branches.

	* opcodes/i386-opc.tbl (call): Remove Disp16|Disp32 from 64-bit
	direct branch.
	(jmp): Likewise.
	* i386-tbl.h: Regenerated.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Avoid segfault on missing directory table.
@ 2015-05-09  0:26 sergiodj+buildbot
  2015-05-09 11:44 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-05-09  0:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT afa6c9abf2c12c8e6155d088ea45e5091ca79c57 ***

Author: Sandra Loosemore <sandra@codesourcery.com>
Branch: master
Commit: afa6c9abf2c12c8e6155d088ea45e5091ca79c57

Avoid segfault on missing directory table.
2015-05-08  Yao Qi  <yao@codesourcery.com>
	    Sandra Loosemore  <sandra@codesourcery.com>

	gdb/
	* dwarf2read.c (setup_type_unit_groups): Do NULL pointer check
	to 'lh->include_dirs' before accessing to it.
	(psymtab_include_file_name): Likewise.
	(dwarf_decode_lines_1): Likewise.
	(dwarf_decode_lines): Likewise.
	(file_file_name): Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix register save offset for nios2 signal handler trampolines.
@ 2015-05-08 22:57 sergiodj+buildbot
  2015-05-09 10:24 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-05-08 22:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 35d54293c3a0fb5e8cd3a82a1e2a6e0481b615af ***

Author: Sandra Loosemore <sandra@codesourcery.com>
Branch: master
Commit: 35d54293c3a0fb5e8cd3a82a1e2a6e0481b615af

Fix register save offset for nios2 signal handler trampolines.
2015-05-08  Sandra Loosemore  <sandra@codesourcery.com>

	gdb/
	* nios2-linux-tdep.c (NIOS2_SIGRETURN_TRAMP_ADDR): Define.
	(NIOS2_SIGRETURN_REGSAVE_OFFSET): Define.
	(nios2_linux_rt_sigreturn_init): Adjust base address of
	register save area.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Remove unused declaration of print_return_value.
@ 2015-05-08 19:10 sergiodj+buildbot
  2015-05-08 21:37 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-05-08 19:10 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT dd9f02a0ca7a9873717933345e393edb3d5da6bc ***

Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Branch: master
Commit: dd9f02a0ca7a9873717933345e393edb3d5da6bc

Remove unused declaration of print_return_value.
gdb/ChangeLog
2015-05-08  Jan Kratochvil  <jan.kratochvil@redhat.com>

	* infcmd.c (print_return_value): Remove unused declaration.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Switch erc32 simulator copyright headers to FSF.
@ 2015-05-08 15:28 sergiodj+buildbot
  2015-05-08 17:15 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-05-08 15:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 17d88f73c0e38b80a4c9180ab7ae5383f9d0fb05 ***

Author: Joel Brobecker <brobecker@adacore.com>
Branch: master
Commit: 17d88f73c0e38b80a4c9180ab7ae5383f9d0fb05

Switch erc32 simulator copyright headers to FSF.
Permission was granted by Jiri Gaisler, who has a copyright assignment
on file for GDB.

sim/erc32/ChangeLog:

        * configure.ac: Add copyright header.
        * erc32.c: Change copyright holder to FSF.  Reformat.
        * exec.c, float.c, func.c, interf.c, sis.c, sis.h: Likewise.
        * help.c, startsim: Add copyright header.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] S390: Fix for inadvertently setting 24-bit mode in fill_gregset
@ 2015-05-08 11:46 sergiodj+buildbot
  2015-05-08 12:37 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-05-08 11:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2492f0d005f0390eabb3deb58aa7db7fcd716763 ***

Author: Andreas Arnez <arnez@linux.vnet.ibm.com>
Branch: master
Commit: 2492f0d005f0390eabb3deb58aa7db7fcd716763

S390: Fix for inadvertently setting 24-bit mode in fill_gregset
On 64-bit S390 platforms, for programs compiled with -m31, it could
happen that GDB inadvertently cleared the inferior's 31-bit addressing
mode bit and left the inferior running in 24-bit addressing mode.  In
particular this occurred with checkpoint.exp, when the "restore"
command needed to create a new regcache copy: At the time when the
PSWM register was copied over, the addressing mode bit was taken from
the PSWA register, which was still zero since it had not been copied
yet.  And when the PSWA register was copied, the addressing mode was
not updated again.

The fix affects fill_gregset, where the bits "belonging" to each of
the PSWA and PSWM registers are now carefully separated.  The
addressing mode bit is no longer touched when writing PSWM, and --
more importantly -- it *is* written when writing PSWA.

gdb/ChangeLog:

	* s390-linux-nat.c (fill_gregset): Avoid relying on the PSWA
	register in the regcache when treating the PSWM register, and vice
	versa.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Make the "info dll" command available on all platform.
@ 2015-05-06 18:06 sergiodj+buildbot
  2015-05-06 18:51 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-05-06 18:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b30a0bc387d63a28362bb08c351da32b50228530 ***

Author: Joel Brobecker <brobecker@adacore.com>
Branch: master
Commit: b30a0bc387d63a28362bb08c351da32b50228530

Make the "info dll" command available on all platform.
The "info dll", an alias of the "info sharedlibrary" command, is
currently only defined in windows native versions. This patch makes
it universally available by moving the alias declaration to solib.c,
and adjusts the documentation accordingly.

Making it universally available has two benefits:
  - Windows users moving to a Unix platforms are still able to use
    the same command for getting the list of shared libraries;
  - Unix to Windows cross debuggers now provide that command also.

gdb/ChangeLog:

        * solib.c (_initialize_solib): Add "info dll" alias creation.
        * windows-nat.c (set_windows_aliases): Delete.
        (_initialize_windows_nat): Remove deprecated_init_ui_hook
        assignment.
        * NEWS: Add news entry about "info dll" now being available
        on all platforms.

gdb/doc/ChangeLog:

        * gdb.texinfo (Files): Add "info dll" documentation.
        (Cygwin Native): Remove "info dll" documentation.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] DWARF: cannot break on out-of-line function nested inside inlined function.
@ 2015-05-06  1:28 sergiodj+buildbot
  2015-05-06  3:20 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-05-06  1:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3ea89b92fb0765075a27a3a0239552ae880722ff ***

Author: Pierre-Marie de Rodat <derodat@adacore.com>
Branch: master
Commit: 3ea89b92fb0765075a27a3a0239552ae880722ff

DWARF: cannot break on out-of-line function nested inside inlined function.
Consider the following code, which defines a function, Child2,
which is itself nested inside Child1:

    procedure Foo_O224_021 is
        O1 : constant Object_Type := Get_Str ("Foo");
        procedure Child1 is
            O2 : constant Object_Type := Get_Str ("Foo");
            function Child2 (S : String) return Boolean is -- STOP
            begin
                for C of S loop
                    Do_Nothing (C);
                    if C = 'o' then
                        return True;
                    end if;
                end loop;
                return False;
            end Child2;
            R : Boolean;
        begin
            R := Child2 ("Foo");
            R := Child2 ("Bar");
            R := Child2 ("Foobar");
        end Child1;
    begin
        Child1;
    end Foo_O224_021;

On x86_64-linux, when compiled at -O2, GDB is unable to insert
a breakpoint on Child2:

    % gnatmake -g -O2 foo_o224_021
    % gdb foo_o224_021
    (gdb) b child2
    Function "child2" not defined.
    (gdb) b foo_o224_021.child1.child2
    Function "foo_o224_021.child1.child2" not defined.

The problem is caused by the fact that GDB did not create a symbol
for Child2, and this, in turn, is caused by the fact that the compiler
decided to inline Child1, but not Child2. The DWARF debugging info
first provides an abstract instance tree for Child1...

 <3><1b7b>: Abbrev Number: 29 (DW_TAG_subprogram)
    <1b7c>   DW_AT_name        : (indirect string, offset: 0x23f8): foo_o224_021__child1
    <1b82>   DW_AT_inline      : 1      (inlined)
    <1b83>   DW_AT_sibling     : <0x1c01>

... where that subprogram is given the DW_AT_inline attribute.
Inside that function there is a lexical block which has no PC
range (corresponding to the fact that this is the abstract tree):

 <4><1b87>: Abbrev Number: 30 (DW_TAG_lexical_block)

... inside which our subprogram Child2 is described:

 <5><1b92>: Abbrev Number: 32 (DW_TAG_subprogram)
    <1b93>   DW_AT_name        : (indirect string, offset: 0x2452): foo_o224_021__child1__child2
    <1b99>   DW_AT_type        : <0x1ab1>
    <1b9d>   DW_AT_low_pc      : 0x402300
    <1ba5>   DW_AT_high_pc     : 0x57
    [...]

Then, later on, we get the concrete instance tree, starting at:

 <3><1c5e>: Abbrev Number: 41 (DW_TAG_inlined_subroutine)
    <1c5f>   DW_AT_abstract_origin: <0x1b7b>
    <1c63>   DW_AT_entry_pc    : 0x4025fd
    <1c6b>   DW_AT_ranges      : 0x150

... which refers to Child1. One of that inlined subroutine children
is the concrete instance of the empty lexical block we saw above
(in the abstract instance tree), which gives the actual address
range for this inlined instance:

 <5><1c7a>: Abbrev Number: 43 (DW_TAG_lexical_block)
    <1c7b>   DW_AT_abstract_origin: <0x1b87>
    <1c7f>   DW_AT_ranges      : 0x180

This is the DIE which provides the context inside which we can
record Child2. But unfortunately, GDB does not take the abstract
origin into account when handling lexical blocks, causing it
to miss the fact that this block contains some symbols described
in the abstract instance tree. This is the first half of this patch:
modifying GDB to follow DW_AT_abstract_origin attributes for
lexical blocks.

But this not enough to fix the issue, as we're still unable to
break on Child2 with just that change. The second issue can be
traced to the way inherit_abstract_dies determines the list of
DIEs to inherit from. For that, it iterates over all the DIEs in
the concrete instance tree, and finds the list of DIEs from the
abstract instance tree that are not referenced from the concrete
instance tree. As it happens, there is one type of DIE in the
concrete instance tree which does reference Child2's DIE, but
in fact does otherwise define a concrete instance of the reference
DIE; that's (where <0x1b92> is Child2's DIE):

 <6><1d3c>: Abbrev Number: 35 (DW_TAG_GNU_call_site)
    <1d3d>   DW_AT_low_pc      : 0x4026a4
    <1d45>   DW_AT_abstract_origin: <0x1b92>

So, the second part of the patch is to modify inherit_abstract_dies
to ignore DW_TAG_GNU_call_site DIEs when iterating over the concrete
instance tree.

This patch also includes a testcase which can be used to reproduce
the issue. Unfortunately, for it to actually pass, a smal patch in
GCC is also necessary to make sure that GCC provides lexical blocks'
DW_AT_abstract_origin attributes from the concrete tree back to
the abstract tree. We hope to be able to submit and integrate that
patch in the GCC tree soon. Meanwhile, a setup_xfail has been added.

gdb/ChangeLog:

	2014-05-05  Pierre-Marie de Rodat  <derodat@adacore.com>
	* dwarf2read.c (inherit_abstract_dies): Skip
	DW_TAG_GNU_call_site dies while inheriting children of an
	abstract DIE into a scope.
	(read_lexical_block_scope): Inherit abstract DIE's for
	lexical scopes.

gdb/testsuite/ChangeLog:

        * gdb.ada/out_of_line_in_inlined: New testcase.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Further document ada-lang.c::value_assign_to_component & fix whitespaces.
@ 2015-05-05 22:44 sergiodj+buildbot
  2015-05-06  5:20 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-05-05 22:44 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7c5127443be1d3d0477b3b1d25875023992409bc ***

Author: Joel Brobecker <brobecker@adacore.com>
Branch: master
Commit: 7c5127443be1d3d0477b3b1d25875023992409bc

Further document ada-lang.c::value_assign_to_component & fix whitespaces.
This patch improves the documentation of ada-lang.c's
value_assign_to_component to publish the fact that it also works
with not_lval values.

And touching this area of the code showed that there were a number
of whitespace issues, as well as a formatting issue of the main comment
(no leading '*' on each line). This patch fixes those while at it.

No functional change, however.

gdb/ChangeLog:

        * ada-lang.c (value_assign_to_component): Reformat and improve
        documentation. Remove all trailing spaces.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [Ada] array of variant record subscripting
@ 2015-05-05 19:43 sergiodj+buildbot
  2015-05-05 21:34 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-05-05 19:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ca34b84ff68f5823e215a4d0b44b92f35cbb74a5 ***

Author: Joel Brobecker <brobecker@adacore.com>
Branch: master
Commit: ca34b84ff68f5823e215a4d0b44b92f35cbb74a5

[Ada] array of variant record subscripting
Consider the following (Ada) array...

   A1 : Array_Type := (1 => (I => 0, S => <>),
                       2 => (I => 1, S => "A"),
                       3 => (I => 2, S => "AB"));

... where Array_Type is declared as follow:

   subtype Small_Type is Integer range 0 .. 10;
   type Record_Type (I : Small_Type := 0) is record
      S : String (1 .. I);
   end record;
   type Array_Type is array (Integer range <>) of Record_Type;

Trying to print the value of each element individually does not
always work. Printing the value of the first one does:

(gdb) p a1(1)
    $1 = (i => 0, s => "")

But printing the value of the subsequent ones often does not.
For instance:

    (gdb) p a1(2)
    $2 = (i => 1, s => "")  <<<--- s should be "A"
    (gdb) p a1(3)
    $3 = (i => 2, s => "")  <<<--- s should be "AB"

I traced the problem to ada_value_primitive_packed_val,
which is trying to perform the array subscripting by
extracting the value of the corresponding array element
into a buffer where the contents is now byte-aligned.

The element type that ada_value_primitive_packed_val gets passed
is a dynamic type. As it happens, that dynamic type can get resolved
thanks to:

      v = value_at (type, value_address (obj));
      type = value_type (v);

However, obj represents the array, so the address given in the call
to value_at represents the value of the first element. As a result,
the solution of component S's upper bound always gets resolved based
on the value of component I in the  first element of the array, whose
value is 0, thus leading to GDB mistakely resolving the element type
where S's upper bound is always 0.

The proper fix would be to systematically resolve the element type
first. But, this requires us to extract-and-realign the element's
value so as to be able to pass it as "valaddr" to resolve_dynamic_type.
In the meantime, it's easy to make the situation a little better by
passing "value_address (obj) + offset" as the object address. This
only works when BIT_OFFSET is nul, but that should be the case when
the element type is anything but a scalar, which seems to be the only
situation where it seems important to resolve the type now. And we're
not that worse off otherwise.

But we'll try to find a better solution in a separate patch.

gdb/ChangeLog:

        * ada-lang.c (ada_value_primitive_packed_val): Use a more
        correct address in call to value_at.  Adjust call to
        value_address accordingly.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Add valaddr support in dynamic property resolution.
@ 2015-05-05 19:07 sergiodj+buildbot
  2015-05-05 19:36 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-05-05 19:07 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c3345124196f9d0439db35c16b5d24d1a305ccdd ***

Author: Joel Brobecker <brobecker@adacore.com>
Branch: master
Commit: c3345124196f9d0439db35c16b5d24d1a305ccdd

Add valaddr support in dynamic property resolution.
This is the second part of enhancing the debugger to print the value
of arrays of records whose size is variable when only standard DWARF
info is available (no GNAT encoding). For instance:

   subtype Small_Type is Integer range 0 .. 10;
   type Record_Type (I : Small_Type := 0) is record
      S : String (1 .. I);
   end record;
   type Array_Type is array (Integer range <>) of Record_Type;

   A1 : Array_Type := (1 => (I => 0, S => <>),
                       2 => (I => 1, S => "A"),
                       3 => (I => 2, S => "AB"));

Currently, GDB prints the following output:

        (gdb) p a1
        $1 = (

The error happens while the ada-valprint module is trying to print
the value of an element of our array. Because of the fact that
the array's element (type Record_Type) has a variant size, the DWARF
info for our array provide the array's stride:

     <1><749>: Abbrev Number: 10 (DW_TAG_array_type)
        <74a>   DW_AT_name        : (indirect string, offset: 0xb6d): pck__T18s
        <74e>   DW_AT_byte_stride : 16
        <74f>   DW_AT_type        : <0x6ea>

And because our array has a stride, ada-valprint treats it the same
way as packed arrays (see ada-valprint.c::ada_val_print_array):

  if (TYPE_FIELD_BITSIZE (type, 0) > 0)
    val_print_packed_array_elements (type, valaddr, offset_aligned,
                                     0, stream, recurse,
                                     original_value, options);

The first thing that we should notice in the call above is that
the "valaddr" buffer and the associated offset (OFFSET_ALIGNED)
is passed, but that the corresponding array's address is not.
This can be explained by looking inside val_print_packed_array_elements,
where we see that the function unpacks each element of our array from
the buffer alone (ada_value_primitive_packed_val), and then prints
the resulting artificial value instead:

      v0 = ada_value_primitive_packed_val (NULL, valaddr + offset,
                                           (i0 * bitsize) / HOST_CHAR_BIT,
                                           (i0 * bitsize) % HOST_CHAR_BIT,
                                           bitsize, elttype);

      [...]
              val_print (elttype, value_contents_for_printing (v0),
                         value_embedded_offset (v0), 0, stream,
                         recurse + 1, v0, &opts, current_language);

Of particular interest, here, is the fact that we call val_print
with a null address, which is OK, since we're providing a buffer
instead (value_contents_for_printing). Also, providing an address
might not always possible, since packing could place elements at
boundaries that are not byte-aligned.

Things go south when val_print tries to see if there is a pretty-printer
that could be applied. In particular, one of the first things that
the Python pretty-printer does is to create a value using our buffer,
and the given address, which in this case is null (see call to
value_from_contents_and_address in gdbpy_apply_val_pretty_printer).

value_from_contents_and_address, in turn immediately tries to resolve
the type, using the given address, which is null. But, because our
array element is a record containing an array whose bound is the value
of one of its elements (the "s" component), the debugging info for
the array's upper bound is a reference...

 <3><71a>: Abbrev Number: 7 (DW_TAG_subrange_type)
    <71b>   DW_AT_type        : <0x724>
    <71f>   DW_AT_upper_bound : <0x703>

... to component "i" of our record...

 <2><703>: Abbrev Number: 5 (DW_TAG_member)
    <704>   DW_AT_name        : i
    <706>   DW_AT_decl_file   : 2
    <707>   DW_AT_decl_line   : 6
    <708>   DW_AT_type        : <0x6d1>
    <70c>   DW_AT_data_member_location: 0

... where that component is located at offset 0 of the start
of the record. dwarf2_evaluate_property correctly determines
the offset where to load the value of the bound from, but then
tries to read that value from inferior memory using the address
that was given, which is null. See case PROP_ADDR_OFFSET in
dwarf2_evaluate_property:

        val = value_at (baton->offset_info.type,
                        pinfo->addr + baton->offset_info.offset);

This triggers a memory error, which then causes the printing to terminate.

Since there are going to be situations where providing an address
alone is not going to be sufficient (packed arrays where array elements
are not stored at byte boundaries), this patch fixes the issue by
enhancing the type resolution to take both address and data. This
follows the same principle as the val_print module, where both
address and buffer ("valaddr") can be passed as arguments. If the data
has already been fetched from inferior memory (or provided by the
debugging info in some form -- Eg a constant), then use that data
instead of reading it from inferior memory.

Note that this should also be a good step towards being able to handle
dynamic types whose value is stored outside of inferior memory
(Eg: in a register).

With this patch, GDB isn't able to print all of A1, but does perform
a little better:

    (gdb) p a1
    $1 = ((i => 0, s => , (i => 1, s => , (i => 2, s => )

There is another issue which is independent of this one, and will
therefore be patched separately.

gdb/ChangeLog:

        * dwarf2loc.h (struct property_addr_info): Add "valaddr" field.
        * dwarf2loc.c (dwarf2_evaluate_property): Add handling of
        pinfo->valaddr.
        * gdbtypes.h (resolve_dynamic_type): Add "valaddr" parameter.
        * gdbtypes.c (resolve_dynamic_struct): Set pinfo.valaddr.
        (resolve_dynamic_type_internal): Set pinfo.valaddr.
        Add handling of addr_stack->valaddr.
        (resolve_dynamic_type): Add "valaddr" parameter.
        Set pinfo.valaddr field.
        * ada-lang.c (ada_discrete_type_high_bound): Update call to
        resolve_dynamic_type.
        (ada_discrete_type_low_bound): Likewise.
        * findvar.c (default_read_var_value): Likewise.
        * value.c (value_from_contents_and_address): Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix handling of relocs for the MeP target.
@ 2015-04-30 15:38 sergiodj+buildbot
  2015-04-30 15:43 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-04-30 15:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 153a27763ccc9979fdb5f342e21eb1666c8f117b ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: 153a27763ccc9979fdb5f342e21eb1666c8f117b

Fix handling of relocs for the MeP target.
bfd	PR 18317
	* elf32-mep.c (MEPREL): Use bfd_elf_generic_reloc instead of
	mep_reloc.
	(mep_reloc): Delete unused function.

bin	* readelf.c (get_machine_flags): Add description of MeP flags.

tests	* binutils-all/objdump.exp (cpus_expected): Add MeP CPU names.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Allow passing fd == NULL to exec_file_find and solib_find
@ 2015-04-29 14:34 sergiodj+buildbot
  2015-04-29 15:05 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-04-29 14:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 998d2a3ef31378d3d980972dc68f4926b720a7e9 ***

Author: Gary Benson <gbenson@redhat.com>
Branch: master
Commit: 998d2a3ef31378d3d980972dc68f4926b720a7e9

Allow passing fd == NULL to exec_file_find and solib_find
This commit allows NULL to be passed as the int *fd argument
to exec_file_find and solib_find to simplify use cases where
the caller does not require the file to be opened.

gdb/ChangeLog:

	* solib.c (solib_find_1): Allow fd argument to be NULL.
	(exec_file_find): Update comment.
	(solib_find): Likewise.
	* exec.c (exec_file_locate_attach): Use NULL as fd
	argument to exec_file_find to avoid having to close
	the opened file.
	* infrun.c (follow_exec): Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Add support for absolute PE/x86 relocations.
@ 2015-04-29 11:41 sergiodj+buildbot
  2015-04-29 12:13 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-04-29 11:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a93d5cb1976818c8d34133fd8798b3df76269f80 ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: a93d5cb1976818c8d34133fd8798b3df76269f80

Add support for absolute PE/x86 relocations.
	PR 17099
	* coff-i386.c (coff_i386_rtype_to_howto): Allow absolute PCRLONG
	relocs.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Add support for catching exec events on FreeBSD.
@ 2015-04-27 23:51 sergiodj+buildbot
  2015-04-28 15:34 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-04-27 23:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d2b41ca0f9c5641a6b8f42c8013ba042cf5ba120 ***

Author: John Baldwin <jhb@FreeBSD.org>
Branch: master
Commit: d2b41ca0f9c5641a6b8f42c8013ba042cf5ba120

Add support for catching exec events on FreeBSD.
FreeBSD kernels that support fork tracing always stop a process to
report events for exec.  Such a process will have the PL_FLAG_EXEC
flag set in the pl_flags field of the ptrace_lwpinfo struct returned
by PT_LWPINFO.  The structure does not include the pathname passed to
exec, so use fbsd_pid_to_exec_file to query the pathname of the
process' executable.

gdb/ChangeLog:

	* fbsd-nat.c: (fbsd_wait) [PL_FLAG_EXEC]: Report TARGET_WAITKIND_EXECD
	event if PL_FLAG_EXEC is set.
	[PL_FLAG_EXEC] (fbsd_insert_exec_catchpoint): New function.
	[PL_FLAG_EXEC] (fbsd_remove_exec_catchpoint): New function.
	(fbsd_nat_add_target) [PL_FLAG_EXEC]: Set
	"to_insert_exec_catchpoint" to "fbsd_insert_exec_catchpoint".
	Set "to_remove_exec_catchpoint" to "fbsd_remove_exec_catchpoint".


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Enable fork tracing for native FreeBSD targets.
@ 2015-04-27 23:43 sergiodj+buildbot
  2015-04-28  9:59 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-04-27 23:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e58e05d677d33da3646721bdd225ec6e90424000 ***

Author: John Baldwin <jhb@FreeBSD.org>
Branch: master
Commit: e58e05d677d33da3646721bdd225ec6e90424000

Enable fork tracing for native FreeBSD targets.
Enable PT_FOLLOW_FORK on all processes.  When this is enabled, both
the parent and child process stop when a fork or vfork occurs.

A target operation for wait uses PT_LWPINFO to fetch more detailed
information about the state of a stopped process.  A parent process
sets the PL_FLAG_FORKED flag in the pl_flags field of the structure
returned by PT_LWPINFO as well as the pid of the new child process.
The child process sets the PL_FLAG_CHILD flag in the pl_flags field.

When a fork is detected, the wait hook waits for both processes to
report their respective events.  It then reports the fork to GDB as
a single TARGET_WAITKIND_FORKED or TARGET_WAITKIND_VFORKED event.
The kernel does not guarantee the order the events are reported in.
If the parent process' event is reported first, then the wait hook
explicitly waits for the child process.  If the child process' event
is reported first, the event is recorded on an internal list of
pending child events and the wait hook waits for another event.
Later when the parent process' event is reported, the parent will
use the previously-recorded child process event instead of explicitly
waiting on the child process.

To distinguish vfork events from fork events, the external process
structure for the child process is extracted from the kernel.  The
P_PPWAIT flag is set in the ki_flags field of this structure if the
process was created via vfork, but it is not set for a regular fork.

gdb/ChangeLog:

	* fbsd-nat.c: [PT_LWPINFO] New variable super_wait.
	[TDP_RFPPWAIT] New variable fbsd_pending_children.
	[TDP_RFPPWAIT] (fbsd_remember_child): New function.
	[TDP_RFPPWAIT] (fbsd_is_child_pending): New function.
	[TDP_RFPPWAIT] (fbsd_fetch_kinfo_proc): New function.
	[PT_LWPINFO] (fbsd_wait): New function.
	[TDP_RFPPWAIT] (fbsd_follow_fork): New function.
	[TDP_RFPPWAIT] (fbsd_insert_fork_catchpoint): New function.
	[TDP_RFPPWAIT] (fbsd_remove_fork_catchpoint): New function.
	[TDP_RFPPWAIT] (fbsd_insert_vfork_catchpoint): New function.
	[TDP_RFPPWAIT] (fbsd_remove_vfork_catchpoint): New function.
	[TDP_RFPPWAIT] (fbsd_enable_follow_fork): New function.
	[TDP_RFPPWAIT] (fbsd_post_startup_inferior): New function.
	[TDP_RFPPWAIT] (fbsd_post_attach): New function.
	(fbsd_nat_add_target) [PT_LWPINFO] Set "to_wait" to
	"fbsd_wait".
	[TDP_RFPPWAIT] Set "to_follow_fork" to "fbsd_follow_fork".
	Set "to_insert_fork_catchpoint" to "fbsd_insert_fork_catchpoint".
	Set "to_remove_fork_catchpoint" to "fbsd_remove_fork_catchpoint".
	Set "to_insert_vfork_catchpoint" to "fbsd_insert_vfork_catchpoint".
	Set "to_remove_vfork_catchpoint" to "fbsd_remove_vfork_catchpoint".
	Set "to_post_startup_inferior" to "fbsd_post_startup_inferior".
	Set "to_post_attach" to "fbsd_post_attach".


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Add fbsd_nat_add_target.
@ 2015-04-27 23:34 sergiodj+buildbot
  2015-04-28  3:43 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-04-27 23:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8f60fe014dd0afdc1013fc22a3ef5ba01e94e331 ***

Author: John Baldwin <jhb@FreeBSD.org>
Branch: master
Commit: 8f60fe014dd0afdc1013fc22a3ef5ba01e94e331

Add fbsd_nat_add_target.
Add a wrapper for add_target in fbsd-nat.c to override target operations
common to all native FreeBSD targets.

gdb/ChangeLog:

	* fbsd-nat.c (fbsd_pid_to_exec_file): Mark static.
	(fbsd_find_memory_regions): Mark static.
	(fbsd_nat_add_target): New function.
	* fbsd-nat.h: Export fbsd_nat_add_target and remove prototypes for
	fbsd_pid_to_exec_file and fbsd_find_memory_regions.
	* amd64fbsd-nat.c (_initialize_amd64fbsd_nat): Use fbsd_nat_add_target.
	* i386fbsd-nat.c (_initialize_i386fbsd_nat): Likewise.
	* ppcfbsd-nat.c (_initialize_ppcfbsd_nat): Likewise.
	* sparc64fbsd-nat.c (_initialize_sparc64fbsd_nat): Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] gdb: Add internationalization support to a few strings.
@ 2015-04-25  0:02 sergiodj+buildbot
  2015-04-25 10:07 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-04-25  0:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6faec16b1c633a8043791e0d15d7e7f1c8d448c1 ***

Author: Andrew Burgess <andrew.burgess@embecosm.com>
Branch: master
Commit: 6faec16b1c633a8043791e0d15d7e7f1c8d448c1

gdb: Add internationalization support to a few strings.
Spotted a few strings that were missing internationalization support.

gdb/ChangeLog:

	* cli/cli-dump.c (srec_dump_command): Add internationalization
	mark ups.
	(ihex_dump_command): Likewise.
	(tekhex_dump_command): Likewise.
	(binary_dump_command): Likewise.
	(binary_append_command): Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix typo in check for valid register number in RX sim.
@ 2015-04-24 16:38 sergiodj+buildbot
  2015-04-24 17:00 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-04-24 16:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 63c72d1ae497cdf43db5347464a97164e720b83f ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: 63c72d1ae497cdf43db5347464a97164e720b83f

Fix typo in check for valid register number in RX sim.
	PR sim/18273
	* reg.c (put_reg): Fix check for valid register number.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] A new board file remote-gdbserver-on-localhost.exp
@ 2015-04-24 10:15 sergiodj+buildbot
  2015-04-24 10:56 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-04-24 10:15 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8dbe7ca5a5755274fca1d3021ad648a1575e66cb ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 8dbe7ca5a5755274fca1d3021ad648a1575e66cb

A new board file remote-gdbserver-on-localhost.exp
This patch is to add a new board file that does real remote gdbserver
testing on localhost.  This board file can be used to reproduce PR 18208.

gdb/testsuite

2015-04-24  Yao Qi  <yao.qi@linaro.org>

	* boards/remote-gdbserver-on-localhost.exp: New file.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Delay setting up compressed debug section names
@ 2015-04-23 23:56 sergiodj+buildbot
  2015-04-24  1:58 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-04-23 23:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3e19fb8f990e4ce8a08f9cf2817cd9e9398648d5 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 3e19fb8f990e4ce8a08f9cf2817cd9e9398648d5

Delay setting up compressed debug section names
When we set up st_name for output section name in elf_fake_sections, we
don't know if the compressed DWARF debug section will be smaller. We may
end up with compressed DWARF debug sections which are bigger than the
uncompressed ones.  This patch delays setting up st_name for output DWARF
debug section to _bfd_elf_assign_file_positions_for_non_load which will
compress the output debug section.  We also postpone placement of shstrtab
section after DWARF debug sections have been compressed.  The net effect
is .shstrtab section is now placed after .symtab and .strtab sections.

bfd/

	PR ld/18277
	* compress.c (bfd_compress_section_contents): Remove the
	write_compress argument.
	(bfd_init_section_compress_status): Updated.
	(bfd_compress_section): Likewise.
	* elf.c (_bfd_elf_set_reloc_sh_name): New.
	(_bfd_elf_init_reloc_shdr): Add delay_st_name_p.  Set sh_name
	to (unsigned int) -1 if delay_st_name_p is TRUE.  Use
	_bfd_elf_set_reloc_sh_name.
	(elf_fake_sections): Don't rename DWARF debug section for
	linker output if it will be compressed.  Instead, set
	delay_st_name_p to TRUE and pass it to _bfd_elf_init_reloc_shdr.
	(assign_section_numbers): Call _bfd_elf_strtab_addref only if
	sh_name != (unsigned int) -1.  Don't finalize nor assign
	shstrtab section here.  Delay setting output section names to
	_bfd_elf_write_object_contents.
	(_bfd_elf_compute_section_file_positions): Update comments on
	sh_offset for shstrtab section.
	(assign_file_positions_for_non_load_sections): Set sh_offset to
	-1 for shstrtab section.
	(assign_file_positions_except_relocs): Likewise.
	(_bfd_elf_assign_file_positions_for_non_load): Set up sh_name
	when compressing DWARF debug sections.  Place shstrtab section
	after DWARF debug sections have been compressed.
	(_bfd_elf_write_object_contents): Setting sh_name for output
	sections.

ld/testsuite/

	PR ld/18277
	* ld-elf/compressed1d.d: New.
	* ld-elf/compressed1e.d: Likewise.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] windows-nat: Don't change current_event.dwThreadId in handle_output_debug_string()
@ 2015-04-22 20:17 sergiodj+buildbot
  2015-04-22 22:46 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-04-22 20:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f16eab5ffbd9128410241abc48edcd5871c91137 ***

Author: Jon Turney <jon.turney@dronecode.org.uk>
Branch: master
Commit: f16eab5ffbd9128410241abc48edcd5871c91137

windows-nat: Don't change current_event.dwThreadId in handle_output_debug_string()
Using the 'catch-signal' test from the testsuite, on x86_64 Cygwin:

    $ ./gdb testsuite/outputs/gdb.base/catch-signal/catch-signal.exe
    [...]
    (gdb) catch signal
    Catchpoint 1 (standard signals)
    (gdb) r
    [...]
    Catchpoint 1 (signal SIGHUP), main () at
    ../../../gdb/testsuite/gdb.base/catch-signal.c:40
    40        raise (SIGHUP);               /* second HUP */
    (gdb) c
    Continuing.
    main () at ../../../gdb/testsuite/gdb.base/catch-signal.c:40
    40        raise (SIGHUP);               /* second HUP */
    Failed to resume program execution (ContinueDebugEvent failed, error 87)
    (gdb)

This error occurs because when handle_output_debug_string processes a Cygwin
signal message, it re-writes current_event.dwThreadId to reflect the thread that
the signal will be delivered to, which can be different to the thread reporting
the signal.

Altering current_event.dwThreadId() will cause ContinueDebugEvent() to be
applied to the wrong thread and fail.

So, rather than re-writing the thread id in current_event, use the thread
id by returning it.

With this patch applied this test now yields the expected result:

    $ ./gdb testsuite/outputs/gdb.base/catch-signal/catch-signal.exe
    [...]
    (gdb) catch signal
    Catchpoint 1 (standard signals)
    (gdb) r
    [...]
    Catchpoint 1 (signal SIGHUP), main () at
    ../../../gdb/testsuite/gdb.base/catch-signal.c:40
    40        raise (SIGHUP);               /* second HUP */
    (gdb) c
    Continuing.
    Catchpoint 1 (signal SIGHUP), main () at
    ../../../gdb/testsuite/gdb.base/catch-signal.c:42
    42        raise (SIGHUP);               /* third HUP */
    (gdb)

gdb/ChangeLog:

2015-04-22  Jon Turney  <jon.turney@dronecode.org.uk>

	* windows-nat.c (handle_output_debug_string): Don't change
	current_event.dwThreadId.
	(get_windows_debug_event): Use thread_id, rather than relying on
	current_event.dwThreadId being changed.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] sim/erc32: Switched emulated memory to host endian order.
@ 2015-04-19  6:48 sergiodj+buildbot
  2015-04-19  7:39 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-04-19  6:48 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d3e9b40afb8e7bd09522044951cdce4710676c3e ***

Author: Jiri Gaisler <jiri@gaisler.se>
Branch: master
Commit: d3e9b40afb8e7bd09522044951cdce4710676c3e

sim/erc32: Switched emulated memory to host endian order.
Change data ordering in emulated memory from target order (big endian)
to host order. Improves performance and simplifies most memory
operations. Requires some byte twisting during stores on little
endian hosts (intel). Also removed support for little-endian binaries.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] sim: unify SIM_CPU definition
@ 2015-04-18  9:26 sergiodj+buildbot
  2015-04-18 10:18 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-04-18  9:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 20bca71d82598a015de0991196e45f0b5f7ead81 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 20bca71d82598a015de0991196e45f0b5f7ead81

sim: unify SIM_CPU definition
Since every target typedefs this the same way, move it to the common code.

We have to leave Blackfin behind here for now because of inter-dependencies
on types and headers: sim-base.h includes sim-model.h which needs types in
machs.h which needs types in bfim-sim.h which needs SIM_CPU.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] solib-svr4.c (svr4_exec_displacement): Rename outer "displacement".
@ 2015-04-17 18:36 sergiodj+buildbot
  2015-04-18  2:20 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-04-17 18:36 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8f61baf802b597c11fec288f840d9f7feb18eb0e ***

Author: Doug Evans <dje@google.com>
Branch: master
Commit: 8f61baf802b597c11fec288f840d9f7feb18eb0e

solib-svr4.c (svr4_exec_displacement): Rename outer "displacement".
gdb/ChangeLog:

	* solib-svr4.c (svr4_exec_displacement): Rename outer "displacement"
	to "exec_displacement" to avoid confusion with inner use of the name.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] gdbserver/xtensa: fix typo in XCHAL_HAVE_LOOPS
@ 2015-04-17 16:16 sergiodj+buildbot
  2015-04-17 22:24 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-04-17 16:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a2d5a9d76f2366ed93095fc5a63eafa06b22f808 ***

Author: Max Filippov <jcmvbkbc@gmail.com>
Branch: master
Commit: a2d5a9d76f2366ed93095fc5a63eafa06b22f808

gdbserver/xtensa: fix typo in XCHAL_HAVE_LOOPS
This fixes lbeg/lend/lcount registers handling through gdbserver.

2015-04-17  Max Filippov  <jcmvbkbc@gmail.com>
gdb/gdbserver/
	* linux-xtensa-low.c (xtensa_fill_gregset)
	(xtensa_store_gregset): Check XCHAL_HAVE_LOOPS instead of
	XCHAL_HAVE_LOOP.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] gdbserver/xtensa: drop xtensa_usrregs_info
@ 2015-04-17 14:33 sergiodj+buildbot
  2015-04-17 21:24 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-04-17 14:33 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT deb44829ecc1dd38275af0fcf91acd319e227a89 ***

Author: Max Filippov <jcmvbkbc@gmail.com>
Branch: master
Commit: deb44829ecc1dd38275af0fcf91acd319e227a89

gdbserver/xtensa: drop xtensa_usrregs_info
xtensa_usrregs_info refers to undefined variables xtensa_num_regs and
xtensa_regmap. Drop xtensa_usrregs_info and replace pointer to usrregs
in regs_info with NULL since all registers are read/set through regsets.

2015-04-17  Max Filippov  <jcmvbkbc@gmail.com>
gdb/gdbserver/
	* linux-xtensa-low.c (xtensa_usrregs_info): Remove.
	(regs_info): Replace usrregs pointer with NULL.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] gdb: add myself to blackfin/write-after-approval
@ 2015-04-17  8:27 sergiodj+buildbot
  2015-04-17 10:56 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-04-17  8:27 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 92209ddfdc725c51d0368716ee316193deb24e8a ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 92209ddfdc725c51d0368716ee316193deb24e8a

gdb: add myself to blackfin/write-after-approval


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] sim: replace CIA_{GET,SET} with CPU_PC_{GET,SET}
@ 2015-04-17  7:40 sergiodj+buildbot
  2015-04-17  8:39 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-04-17  7:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 034685f9ce92cf6dfb6656745365b6a5904a8e84 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 034685f9ce92cf6dfb6656745365b6a5904a8e84

sim: replace CIA_{GET,SET} with CPU_PC_{GET,SET}
The CIA_{GET,SET} macros serve the same function as CPU_PC_{GET,SET}
except the latter adds a layer of indirection via the sim state.  This
lets models set up different functions at runtime and doesn't reach so
directly into the arch-specific cpu state.

It also doesn't make sense to have two sets of macros that do exactly
the same thing, so lets standardize on the one that gets us more.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix {mi-tracepoint-changed, mi-tsv-changed}.exp with native-extended-gdbserver
@ 2015-04-16 14:48 sergiodj+buildbot
  2015-04-16 16:15 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-04-16 14:48 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e797481d53d846c8adb51576385fdf7f8cb272ac ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: e797481d53d846c8adb51576385fdf7f8cb272ac

Fix {mi-tracepoint-changed, mi-tsv-changed}.exp with native-extended-gdbserver
Fixes:

 -FAIL: gdb.trace/mi-tracepoint-changed.exp: reconnect: break-info 1
 +PASS: gdb.trace/mi-tracepoint-changed.exp: reconnect: tracepoint created
 +PASS: gdb.trace/mi-tracepoint-changed.exp: reconnect: tracepoint on marker is installed
 +PASS: gdb.trace/mi-tracepoint-changed.exp: reconnect: break-info 1


 -FAIL: gdb.trace/mi-tsv-changed.exp: upload: tsv1 created
 -FAIL: gdb.trace/mi-tsv-changed.exp: upload: tsv2 created
 +PASS: gdb.trace/mi-tsv-changed.exp: upload: tsv1 created
 +PASS: gdb.trace/mi-tsv-changed.exp: upload: tsv2 created

These tests do something like this:

 #0 - start gdb/gdbserver normally
 #1 - setup some things in the debug session
 #2 - disconnect from gdbserver
 #3 - restart gdb
 #4 - reconnect to gdbserver

The problem is that the native-extended-gdbserver board always spawns
a new gdbserver instance in #3 (and has gdb connect to that).  So when
the test gets to #4, it connects to that new instance instead of the
old one:

 (gdb) spawn ../gdbserver/gdbserver --multi :2354
 Listening on port 2354
 target extended-remote localhost:2354
 Remote debugging using localhost:2354
 ...
 spawn ../gdbserver/gdbserver --multi :2355
 Listening on port 2355
 47-target-select extended-remote localhost:2355
 =tsv-created,name="trace_timestamp",initial="0"\n
 47^connected
 (gdb)
 ...
 47-target-select extended-remote localhost:2355
 47^connected
 (gdb)
 FAIL: gdb.trace/mi-tsv-changed.exp: upload: tsv1 created
 FAIL: gdb.trace/mi-tsv-changed.exp: upload: tsv2 created

testsuite/ChangeLog:
2015-04-16  Pedro Alves  <palves@redhat.com>

	* boards/native-extended-gdbserver.exp (mi_gdb_start): Don't start
	a new gdbserver if gdbserver_reconnect_p is set.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Make info fun|var|types interruptable.
@ 2015-04-15 20:39 sergiodj+buildbot
  2015-04-16  5:59 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-04-15 20:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 61d96d7e2e0a44336fc53eb79ccb59b41705cdb3 ***

Author: Doug Evans <dje@google.com>
Branch: master
Commit: 61d96d7e2e0a44336fc53eb79ccb59b41705cdb3

Make info fun|var|types interruptable.
"info fun foo" can be a pain when it's not interruptable,
especially if you're not exactly sure of what you're looking for
and provide something that matches too much.

gdb/ChangeLog:

	* dwarf2read.c (dw2_expand_symtabs_matching): Add some QUIT calls.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Handle invalid prefixes for rdrand and rdseed
@ 2015-04-15 18:36 sergiodj+buildbot
  2015-04-16  0:03 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-04-15 18:36 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f24bcbaa5a6e30556e2da20bfd78e7823741475a ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: f24bcbaa5a6e30556e2da20bfd78e7823741475a

Handle invalid prefixes for rdrand and rdseed
This patch puts rdrand and rdseed in prefix_table so that invalid
prefixes for rdrand and rdseed are handled properly.

gas/testsuite/

	PR binutils/17898
	* gas/i386/prefix.s: Add rdrand/rdseed prefix tests.
	* gas/i386/prefix.d: Updated.

opcodes/

	PR binutils/17898
	* i386-dis.c (PREFIX_0FC7_REG_6): Renamed to ...
	(PREFIX_MOD_0_0FC7_REG_6): This.
	(PREFIX_MOD_3_0FC7_REG_6): New.
	(PREFIX_MOD_3_0FC7_REG_7): Likewise.
	(prefix_table): Replace PREFIX_0FC7_REG_6 with
	PREFIX_MOD_0_0FC7_REG_6.  Add PREFIX_MOD_3_0FC7_REG_6 and
	PREFIX_MOD_3_0FC7_REG_7.
	(mod_table): Replace PREFIX_0FC7_REG_6 with
	PREFIX_MOD_0_0FC7_REG_6.  Use PREFIX_MOD_3_0FC7_REG_6 and
	PREFIX_MOD_3_0FC7_REG_7.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Replace mandatory_prefix with prefix_requirement
@ 2015-04-15 18:13 sergiodj+buildbot
  2015-04-15 22:45 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-04-15 18:13 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 507bd32558eb1c0054b7989d52ac1ab25cc5b0ac ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 507bd32558eb1c0054b7989d52ac1ab25cc5b0ac

Replace mandatory_prefix with prefix_requirement
	* i386-dis.c (PREFIX_MANDATORY_REPZ): Removed.
	(PREFIX_MANDATORY_REPNZ): Likewise.
	(PREFIX_MANDATORY_DATA): Likewise.
	(PREFIX_MANDATORY_ADDR): Likewise.
	(PREFIX_MANDATORY_LOCK): Likewise.
	(PREFIX_MANDATORY): Likewise.
	(PREFIX_UD_SHIFT): Set to 8
	(PREFIX_UD_REPZ): Updated.
	(PREFIX_UD_REPNZ): Likewise.
	(PREFIX_UD_DATA): Likewise.
	(PREFIX_UD_ADDR): Likewise.
	(PREFIX_UD_LOCK): Likewise.
	(PREFIX_IGNORED_SHIFT): New.
	(PREFIX_IGNORED_REPZ): Likewise.
	(PREFIX_IGNORED_REPNZ): Likewise.
	(PREFIX_IGNORED_DATA): Likewise.
	(PREFIX_IGNORED_ADDR): Likewise.
	(PREFIX_IGNORED_LOCK): Likewise.
	(PREFIX_OPCODE): Likewise.
	(PREFIX_IGNORED): Likewise.
	(Bad_Opcode): Replace PREFIX_MANDATORY with 0.
	(dis386_twobyte): Replace PREFIX_MANDATORY with PREFIX_OPCODE.
	(three_byte_table): Likewise.
	(mod_table): Likewise.
	(mandatory_prefix): Renamed to ...
	(prefix_requirement): This.
	(prefix_table): Replace PREFIX_MANDATORY with PREFIX_OPCODE.
	Update PREFIX_90 entry.
	(get_valid_dis386): Check prefix_requirement to see if a prefix
	should be ignored.
	(print_insn): Replace mandatory_prefix with prefix_requirement.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [arm] Update displaced stepping debug message
@ 2015-04-15 16:19 sergiodj+buildbot
  2015-04-15 18:45 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-04-15 16:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6bbbba9ba5bcde0b2f4613e1bec3226cf567dcf9 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 6bbbba9ba5bcde0b2f4613e1bec3226cf567dcf9

[arm] Update displaced stepping debug message
When I "set debug displaced 1" to fix fail in
gdb.base/disp-step-syscall.exp, the debug message is wrong.  This
patch is to fix it.

gdb:

2015-04-15  Yao Qi  <yao.qi@linaro.org>

	* arm-linux-tdep.c (arm_linux_copy_svc): Update debug message.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix fails in gdb.dwarf2/dynarr-ptr.exp
@ 2015-04-15 13:24 sergiodj+buildbot
  2015-04-15 15:44 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-04-15 13:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8cbc97c629061306efb30aa83440bec7380c584e ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 8cbc97c629061306efb30aa83440bec7380c584e

Fix fails in gdb.dwarf2/dynarr-ptr.exp
I see many fails in gdb.dwarf2/dynarr-ptr.exp on arm-linux target,
started from this

print foo.three_ptr.all^M
Cannot access memory at address 0x107c8^M
(gdb) FAIL: gdb.dwarf2/dynarr-ptr.exp: print foo.three_ptr.all
print foo.three_ptr.all(1)^M
Cannot access memory at address 0x107c8

It turns out that ":$ptr_size" is used incorrectly.

             array_ptr_label: DW_TAG_pointer_type {
                 {DW_AT_byte_size :$ptr_size }
                                  ^^^^^^^^^^
                 {DW_AT_type :$array_label}
             }

Since the FORM isn't given, and it starts with the ":", it is regarded
as a label reference by dwarf assembler.  The generated asm file on
x86_64 is

        .uleb128        6               /* Abbrev (DW_TAG_pointer_type) */
        .4byte        8 - .Lcu1_begin   <----- WRONG
        .4byte        .Llabel2 - .Lcu1_begin

Looks .Lcu1_begin is 0 on x86_64 and that is why this test passes on
x86_64.  On arm, .Lcu1_begin is an address somewhere, and the value
of DW_AT_byte_size is a very large number, so memory read request
of such large length failed.

This patch is to remove ":" and set the form explicitly.  The generated
asm file on x86_64 becomes

        .uleb128        6               /* Abbrev (DW_TAG_pointer_type) */
        .byte        8
        .4byte        .Llabel2 - .Lcu1_begin

gdb/testsuite:

2015-04-15  Yao Qi  <yao.qi@linaro.org>

	* gdb.dwarf2/dynarr-ptr.exp (assemble): Use $ptr_size instead
	of ":$ptr_size" and set its form explicitly.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Fix typo in commit 6ff71e76
@ 2015-04-15  2:15 sergiodj+buildbot
  2015-04-15  8:15 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-04-15  2:15 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 95b57adeb751b56a1192867f9f1e1be2fad608dd ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 95b57adeb751b56a1192867f9f1e1be2fad608dd

Fix typo in commit 6ff71e76
	* elf32-rl78.c (rl78_elf_relocate_section): Typo fix.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Adds support to the RL78 port for linker relaxation affecting .debug sections.
@ 2015-04-14 15:29 sergiodj+buildbot
  2015-04-14 15:33 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-04-14 15:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6ff71e768112317de1236a429e7c88c9d3e32116 ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: 6ff71e768112317de1236a429e7c88c9d3e32116

Adds support to the RL78 port for linker relaxation affecting .debug sections.
gas	* config/tc-rl78.h (TC_LINKRELAX_FIXUP): Define.
	(TC_FORCE_RELOCATION_SUB_SAME): Define.
	(DWARF2_USE_FIXED_ADVANCE_PC): Define.

	* gas/lns/lns.exp: Add RL78 to list of targets using
	DW_LNS_fixed_advance_pc.

bfd	* elf32-rl78.c (RL78_OP_REL): New macro.
	(rl78_elf_howto_table): Use it for complex relocs.
	(get_symbol_value): Handle the cases when the info or status
	arguments are NULL.
	(get_romstart): Cache the status returned by get_symbol_value.
	(get_ramstart): Likewise.
	(RL78_STACK_PUSH): Generate an error message if the stack
	overflows.
	(RL78_STACK_POP): Likewise for underflows.
	(rl78_compute_complex_reloc): New function.  Contains the basic
	processing code for all RL78 complex relocs.
	(rl78_special_reloc): New function.  Provides special reloc
	handling for complex relocs.
	(rl78_elf_relocate_section): Use rl78_compute_complex_reloc.
	(rl78_offset_for_reloc): Likewise.

binutils* readelf.c (target_specific_reloc_handling): Add code to handle
	RL78 complex relocs.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] * MAINTAINERS: Update my email address.
@ 2015-04-13 22:25 sergiodj+buildbot
  2015-04-13 23:16 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-04-13 22:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT dd177e81b4d58a520b1a16e1c992a4ea94ab7de5 ***

Author: Stan Shebs <stanshebs@google.com>
Branch: master
Commit: dd177e81b4d58a520b1a16e1c992a4ea94ab7de5

* MAINTAINERS: Update my email address.
diff --git a/gdb/MAINTAINERS b/gdb/MAINTAINERS
index a67a1a8..0fdd8e5 100644
--- a/gdb/MAINTAINERS
+++ b/gdb/MAINTAINERS
@@ -156,7 +156,7 @@ Doug Evans                  dje@google.com
 Daniel Jacobowitz              drow@false.org
 Mark Kettenis                  kettenis@gnu.org
 Yao Qi                         yao.qi@arm.com
-Stan Shebs                     stan@codesourcery.com
+Stan Shebs                     stanshebs@google.com
 Ulrich Weigand                 Ulrich.Weigand@de.ibm.com
 Elena Zannoni                  elena.zannoni@oracle.com
 Eli Zaretskii                  eliz@gnu.org
@@ -631,7 +631,7 @@ Keith Seitz                                 keiths@redhat.com
 Carlos Eduardo Seo                             cseo@linux.vnet.ibm.com
 Ozkan Sezer                                    sezeroz@gmail.com
 Marcus Shawcroft                               marcus.shawcroft@arm.com
-Stan Shebs                                     stan@codesourcery.com
+Stan Shebs                                     stanshebs@google.com
 Joel Sherrill                                  joel.sherrill@oarcorp.com
 Mark Shinwell                                  shinwell@codesourcery.com
 Craig Silverstein                              csilvers@google.com


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Harden gdb.base/coredump-filter.exp
@ 2015-04-13 17:49 sergiodj+buildbot
  2015-04-13 20:16 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-04-13 17:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7578d5f72c4abb6b49b0394bc810192b06088705 ***

Author: Luis Machado <lgustavo@codesourcery.com>
Branch: master
Commit: 7578d5f72c4abb6b49b0394bc810192b06088705

Harden gdb.base/coredump-filter.exp
This testcase seems to assume the target is running Linux, so bare metal,
simulators and other debugging stubs running different OS' will have a
hard time executing some of the commands the testcase issues.

Even restricting the testcase to Linux systems (which the patch below does),
there are still problems with, say, QEMU not providing PID information when
"info inferior" is issued. As a consequence, the subsequent tests will either
fail or will not make much sense.

The attached patch checks if PID information is available. If not, it just
bails out and avoids running into a number of failures.

gdb/testsuite/ChangeLog:
2015-04-13  Luis Machado  <lgustavo@codesourcery.com>

	* gdb.base/coredump-filter.exp: Restrict test to Linux systems only.
	Handle the case of targets that do not provide PID information.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] sim: arm/mips: fix sim_read/sim_write linkage errors
@ 2015-04-12 10:22 sergiodj+buildbot
  2015-04-12 11:28 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-04-12 10:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e787f858a43c9a6b54a74cec24f954b52619433e ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: e787f858a43c9a6b54a74cec24f954b52619433e

sim: arm/mips: fix sim_read/sim_write linkage errors
With sim-hrw.o being built & linked in the common list, some people are
getting linking errors now for these targets.  Move the main objects that
provide these functions before the common list to avoid that.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Don't call getpagesize more than once
@ 2015-04-12  0:12 sergiodj+buildbot
  2015-04-12  3:17 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-04-12  0:12 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 263b1a3c1f9be7a3bafdb26d69f808974f886680 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 263b1a3c1f9be7a3bafdb26d69f808974f886680

Don't call getpagesize more than once


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Initialize pagesize_m1 in bfd_cache_init
@ 2015-04-11 22:33 sergiodj+buildbot
  2015-04-11 23:00 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-04-11 22:33 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2c008f9a5b65fe8d9379e761b056fabeb34a5da6 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 2c008f9a5b65fe8d9379e761b056fabeb34a5da6

Initialize pagesize_m1 in bfd_cache_init
There is no need to check and initialize pagesize_m1 in cache_bmmap.

	* cache.c (cache_bmmap): Move pagesize_m1 ... to
	(pagesize_m1): Here.
	(bfd_cache_init): Initialize pagesize_m1.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [arm] watchpoint-reuse-slot.exp: skip setting HW points on some address
@ 2015-04-10 19:18 sergiodj+buildbot
  2015-04-10 21:58 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-04-10 19:18 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT de3db44c87a30c67deb38fa9d43d2db3bc98c161 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: de3db44c87a30c67deb38fa9d43d2db3bc98c161

[arm] watchpoint-reuse-slot.exp: skip setting HW points on some address
Hi,
ARM linux kernel has some requirements on the address/length setting
for HW breakpoints/watchpoints, but watchpoint-reuse-slot.exp doesn't
consider them and sets HW points on various addresses.  Many fails
are causes as a result:

stepi^M
Warning:^M
Could not insert hardware watchpoint 20.^M
Could not insert hardware breakpoints:^M
You may have requested too many hardware breakpoints/watchpoints.^M
^M
(gdb) FAIL: gdb.base/watchpoint-reuse-slot.exp: always-inserted off: watch x watch: : width 2, iter 2: base + 1: stepi advanced

watch *(buf.byte + 2 + 1)@2^M
Hardware watchpoint 388: *(buf.byte + 2 + 1)@2^M
Warning:^M
Could not insert hardware watchpoint 388.^M
Could not insert hardware breakpoints:^M
You may have requested too many hardware breakpoints/watchpoints.^M
^M
(gdb) FAIL: gdb.base/watchpoint-reuse-slot.exp: always-inserted on: watch x watch: : width 2, iter 2: base + 1: watch *(buf.byte + 2 + 1)@2

This patch is to reflect kernel requirements in watchpoint-reuse-slot.exp
in order to skip some tests.

gdb/testsuite:

2015-04-10  Yao Qi  <yao.qi@linaro.org>

	* gdb.base/watchpoint-reuse-slot.exp (valid_addr_p): Return
	false for some offset and width combinations which aren't
	supported by linux kernel.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Test step-over-{lands-on-breakpoint|trips-on-watchpoint}.exp with displaced stepping
@ 2015-04-10 15:56 sergiodj+buildbot
  2015-04-10 20:00 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-04-10 15:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c79d856c88fbc58584d811c04b4812618aa6ac7b ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: c79d856c88fbc58584d811c04b4812618aa6ac7b

Test step-over-{lands-on-breakpoint|trips-on-watchpoint}.exp with displaced stepping
These tests exercise the infrun.c:proceed code that needs to know to
start new step overs (along with switch_back_to_stepped_thread, etc.).
That code is tricky to get right in the multitude of possible
combinations (at least):

 (native | remote)
  X (all-stop | all-stop-but-target-always-in-non-stop)
  X (displaced-stepping | in-line step-over).

The first two above are properties of the target, but the different
step-over-breakpoint methods should work with any target that supports
them.  This patch makes sure we always test both methods on all
targets.

Tested on x86-64 Fedora 20.

gdb/testsuite/ChangeLog:
2015-04-10  Pedro Alves  <palves@redhat.com>

	* gdb.threads/step-over-lands-on-breakpoint.exp (do_test): New
	procedure, factored out from ...
	(top level): ... here.  Add "set displaced-stepping" testing axis.
	* gdb.threads/step-over-trips-on-watchpoint.exp (do_test): New
	parameter "displaced".  Use it.
	(top level): Use foreach and add "set displaced-stepping" testing
	axis.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] [arm] Fix displaced stepping for thumb alu reg instruction
@ 2015-04-10 10:05 sergiodj+buildbot
  2015-04-10 11:16 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-04-10 10:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ef713951c571c8490ca57c17c88785c6df1ed840 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: ef713951c571c8490ca57c17c88785c6df1ed840

[arm] Fix displaced stepping for thumb alu reg instruction
Recent patch series "V2 All-stop on top of non-stop" causes a SIGSEGV
in the test case,

> -PASS: gdb.base/info-shared.exp: continue to breakpoint: library function #4
> +FAIL: gdb.base/info-shared.exp: continue to breakpoint: library function #4
>
> continue^M
> Continuing.^M
> ^M
> Program received signal SIGSEGV, Segmentation fault.^M
> 0x40021564 in ?? () gdb/testsuite/gdb.base/info-shared-solib1.so^M
> (gdb) FAIL: gdb.base/info-shared.exp: continue to breakpoint: library function #4

and an ARM displaced stepping bug is exposed.  It can be reproduced by
the modified gdb.arch/arm-disp-step.exp as below,

continue^M
Continuing.^M
^M
Program received signal SIGSEGV, Segmentation fault.^M
0xa713cfcc in ?? ()^M
(gdb) FAIL: gdb.arch/arm-disp-step.exp: continue to breakpoint: continue to test_add_rn_pc_end

This patch is to fix it.

gdb:

2015-04-10  Yao Qi  <yao.qi@linaro.org>

	* arm-tdep.c (install_alu_reg): Update comment.
	(thumb_copy_alu_reg): Remove local variable rn.  Update
	debugging message.  Use r2 instead of r1 in the modified
	instruction.

gdb/testsuite:

2015-04-10  Yao Qi  <yao.qi@linaro.org>

	* gdb.arch/arm-disp-step.S (main): Call test_add_rn_pc.
	(test_add_rn_pc): New function.
	* gdb.arch/arm-disp-step.exp (test_add_rn_pc): New proc.
	(top level): Invoke test_add_rn_pc.


^ permalink raw reply	[flat|nested] 1181+ messages in thread
* [binutils-gdb] Properly check --compress-debug-sections=XXX
@ 2015-04-09 18:55 sergiodj+buildbot
  2015-04-10  3:29 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1181+ messages in thread
From: sergiodj+buildbot @ 2015-04-09 18:55 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cd6faa73f8e3b888ee8b73a733382a5587aca202 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: cd6faa73f8e3b888ee8b73a733382a5587aca202

Properly check --compress-debug-sections=XXX
We can't check if input is ELF in copy_file since some targets may only
set xvec after bfd_check_format_matches is called.  This patch moves
this check to copy_object.

bfd/

	* elfxx-target.h (TARGET_BIG_SYM): Add BFD_COMPRESS_GABI to
	object_flags.
	(TARGET_LITTLE_SYM): Likewise.

binutils/

	* objcopy.c (do_debug_sections): Use bit patterns.
	(copy_object): Return FALSE for compress_zlib, compress_gnu_zlib
	and compress_gabi_zlib on non-ELF input.
	(copy_file): Don't check non-ELF input here.


^ permalink raw reply	[flat|nested] 1181+ messages in thread

end of thread, other threads:[~2017-01-14  1:03 UTC | newest]

Thread overview: 1181+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-07-10 13:38 [binutils-gdb] Fix testsuite regression by: Do not skip prologue for asm (.S) files sergiodj+buildbot
2015-07-10 13:38 ` Failures on AIX-POWER7-plain, branch master sergiodj+buildbot
2015-07-10 14:02 ` Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot
2015-07-10 14:19 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot
2015-07-10 14:25 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot
2015-07-10 14:35 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot
2015-07-10 14:51 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot
2015-07-10 21:19 ` Failures on Debian-i686-native-gdbserver, " sergiodj+buildbot
2015-07-11  0:27 ` Failures on Fedora-ppc64be-cc-with-index, " sergiodj+buildbot
2015-07-11  1:25 ` Failures on Fedora-ppc64be-native-extended-gdbserver-m64, " sergiodj+buildbot
2015-07-11  6:18 ` Failures on Fedora-ppc64le-native-extended-gdbserver-m64, " sergiodj+buildbot
2015-07-11  6:53 ` Failures on Fedora-ppc64le-native-gdbserver-m64, " sergiodj+buildbot
2015-07-11 13:39 ` Failures on Debian-x86_64-m64, " sergiodj+buildbot
  -- strict thread matches above, loose matches on Subject: below --
2016-12-31  4:19 [binutils-gdb] PRU Opcode Port sergiodj+buildbot
2017-01-14  1:03 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-12-31  3:06 [binutils-gdb] PRU BFD support sergiodj+buildbot
2017-01-13 23:34 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-12-28 13:44 [binutils-gdb] Check bfd support for bfd_mips_elf_get_abiflags in mips make rule sergiodj+buildbot
2017-01-13 17:52 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-12-23 21:34 [binutils-gdb] MIPS16/GAS: Disallow EXTEND delay-slot scheduling sergiodj+buildbot
2017-01-05  0:33 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-12-23 21:30 [binutils-gdb] opcodes: Use autoconf to check for `bfd_mips_elf_get_abiflags' in BFD sergiodj+buildbot
2017-01-04 23:11 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-12-23 12:50 [binutils-gdb] Updated email address sergiodj+buildbot
2017-01-04 14:39 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-12-21 11:51 [binutils-gdb] Remove high bit set characters sergiodj+buildbot
2016-12-23 17:56 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-12-20 14:09 [binutils-gdb] MIPS16/opcodes: Correct 64-bit macros' ISA membership sergiodj+buildbot
2016-12-23 14:23 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-12-15  1:26 [binutils-gdb] MAINTAINERS: Add myself as a MIPS maintainer sergiodj+buildbot
2016-12-15  3:54 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-12-14 22:56 [binutils-gdb] MIPS16/opcodes: Fix and clarify MIPS16e commentary sergiodj+buildbot
2016-12-14 23:16 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-12-13 17:55 [binutils-gdb] [Binutils][AARCH64]Remove Cn register for coprocessor CRn, CRm field sergiodj+buildbot
2016-12-13 18:59 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-12-13  0:21 [binutils-gdb] Don't add PHDR for objcopy/strip or ld script specifying PHDRS sergiodj+buildbot
2016-12-13  3:22 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-12-09  0:50 [binutils-gdb] MIPS16/opcodes: Fix PC-relative operation delay-slot adjustment sergiodj+buildbot
2016-12-09  6:38 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-12-08 13:58 [binutils-gdb] Fix crash when disassembling invalid range on powerpc vle sergiodj+buildbot
2016-12-08 18:28 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-12-08 13:02 [binutils-gdb] sync binutils config/ with gcc sergiodj+buildbot
2016-12-08 17:22 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-12-07 14:36 [binutils-gdb] MIPS/opcodes: Correct an `interaction' comment typo sergiodj+buildbot
2016-12-07 17:10 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-12-02 10:11 [binutils-gdb] Add unit test to aarch64 prologue analyzer sergiodj+buildbot
2016-12-02 18:00 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-12-02  2:49 [binutils-gdb] Class-ify ui_out_hdr sergiodj+buildbot
2016-12-02 10:46 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-12-01 21:50 [binutils-gdb] Fix test names starting with uppercase using gdb_test on a single line sergiodj+buildbot
2016-12-01 22:42 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-11-22 16:56 [binutils-gdb] gdbarch software_single_step frame_info to regcache: alpha sergiodj+buildbot
2016-11-22 17:43 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-11-21 14:37 [binutils-gdb] Create subobject value in pretty printer sergiodj+buildbot
2016-11-21 15:04 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-11-18 19:31 [binutils-gdb] libiberty: Add Rust symbol demangling sergiodj+buildbot
2016-11-19  4:01 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-11-18 18:18 [binutils-gdb] libiberty: Fix some demangler crashes caused by reading past end of input sergiodj+buildbot
2016-11-18 23:02 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-11-16 22:59 [binutils-gdb] Make gdb.PendingFrame.read_register handle "user" registers sergiodj+buildbot
2016-11-17  6:01 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-11-16 22:04 [binutils-gdb] Change meaning of VALUE_FRAME_ID; rename to VALUE_NEXT_FRAME_ID sergiodj+buildbot
2016-11-17  0:10 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-11-16 20:03 [binutils-gdb] Extend test gdb.python/py-recurse-unwind.exp sergiodj+buildbot
2016-11-16 21:49 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-11-16 20:01 [binutils-gdb] Fix PR20789 - relaxation with negative valued diff relocs sergiodj+buildbot
2016-11-16 20:26 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-11-16  0:24 [binutils-gdb] gdb: update gnulib to pull in C++ namespace support fixes sergiodj+buildbot
2016-11-16  4:22 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-11-15 20:24 [binutils-gdb] bitfield-parent-optimized-out: Fix struct definition sergiodj+buildbot
2016-11-15 22:33 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-11-11 12:40 [binutils-gdb] Accept hidden COFF symbols, but treat them as if they were debugging symbols sergiodj+buildbot
2016-11-11 14:40 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-11-11 12:02 [binutils-gdb] Remove apply_val_pretty_printer parameter valaddr sergiodj+buildbot
2016-11-11 13:40 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-11-11 10:09 [binutils-gdb] sim: mips: fix dv-tx3904cpu build error sergiodj+buildbot
2016-11-11 11:47 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-11-10 12:31 [binutils-gdb] Provide a more helpful error message when the BFD library is unable to load an extremely large section sergiodj+buildbot
2016-11-10 12:31 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-11-10  9:30 [binutils-gdb] [AArch64] Bind defined symbol locally in PIE sergiodj+buildbot
2016-11-10 11:51 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-11-10  8:07 [binutils-gdb] tui-disasm: Fix window content buffer overrun sergiodj+buildbot
2016-11-10 11:51 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-11-10  7:49 [binutils-gdb] Use unique_xmalloc_ptr in Python code sergiodj+buildbot
2016-11-10 11:51 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-11-10  7:48 [binutils-gdb] Further cleanup/modernization of gdb.base/commands.exp sergiodj+buildbot
2016-11-10 11:50 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-11-10  7:47 [binutils-gdb] X86: Remove the .s suffix from EVEX vpextrw sergiodj+buildbot
2016-11-10 11:51 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-11-10  7:47 [binutils-gdb] X86: Merge AVX512F vmovq sergiodj+buildbot
2016-11-10 11:51 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-11-10  7:46 [binutils-gdb] Make gdb.mi/user-selected-context-sync.exp use proc_with_prefix sergiodj+buildbot
2016-11-10 11:50 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-11-10  7:45 [binutils-gdb] agent_expr_up: gdb::unique_ptr -> std::unique_ptr sergiodj+buildbot
2016-11-10 11:51 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-11-10  7:45 [binutils-gdb] gdb/testsuite: Introduce "proc_with_prefix" sergiodj+buildbot
2016-11-10 11:50 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-11-10  6:36 [binutils-gdb] tui-winsource: Remove failed-allocation logic sergiodj+buildbot
2016-11-10 11:51 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-11-10  5:47 [binutils-gdb] gdb: Use vector::emplace_back sergiodj+buildbot
2016-11-10 12:30 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-11-10  4:19 [binutils-gdb] tui-disasm: Fix line buffer size calculation sergiodj+buildbot
2016-11-10 11:50 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-11-10  3:59 [binutils-gdb] tui-winsource: Allocate for actual lines only sergiodj+buildbot
2016-11-10 11:50 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-11-10  1:21 [binutils-gdb] darwin-nat.c: handle Darwin 16 (aka Sierra) sergiodj+buildbot
2016-11-10 11:50 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-11-09 23:50 [binutils-gdb] Fix py-value.exp failure on Python 3 sergiodj+buildbot
2016-11-10 11:50 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-11-09 23:16 [binutils-gdb] X86: Remove the THREE_BYTE_0F7A entry sergiodj+buildbot
2016-11-10 11:50 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-11-09 21:50 [binutils-gdb] Fix some error-handling bugs in python frame filters sergiodj+buildbot
2016-11-10 11:51 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-11-09 20:30 [binutils-gdb] Remove parameter valaddr from la_val_print sergiodj+buildbot
2016-11-10 11:49 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-11-09 19:49 [binutils-gdb] Use get_frame_register_value instead of deprecated_frame_register_read sergiodj+buildbot
2016-11-10 11:49 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-11-09 18:42 [binutils-gdb] Eliminate agent_expr_p; VEC -> std::vector in struct bp_target_info sergiodj+buildbot
2016-11-10 11:49 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-11-09 17:48 [binutils-gdb] 'struct agent_expr *' -> unique_ptr<agent_expr> sergiodj+buildbot
2016-11-10 11:51 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-11-08  0:39 [binutils-gdb] i386-tdep.c (i386_gdbarch_init): Add comments sergiodj+buildbot
2016-11-08  5:07 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-11-04 23:14 [binutils-gdb] arc/nps400: Validate address type operands correctly sergiodj+buildbot
2016-11-05  2:40 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-11-03 17:51 [binutils-gdb] arc: Replace ARC_SHORT macro with arc_opcode_len function sergiodj+buildbot
2016-11-04 10:05 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-11-03 15:50 [binutils-gdb] Remove gdbarch_remote_breakpoint_from_pc sergiodj+buildbot
2016-11-03 22:46 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-11-03 15:40 [binutils-gdb] New gdbarch methods breakpoint_kind_from_pc and sw_breakpoint_from_kind sergiodj+buildbot
2016-11-03 21:00 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-11-03 15:21 [binutils-gdb] Add enum for mips breakpoint kinds sergiodj+buildbot
2016-11-03 18:20 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-11-03 11:46 [binutils-gdb] Updated Danish translation for the BFD library sergiodj+buildbot
2016-11-03 14:54 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-11-01 17:00 [binutils-gdb] Add support for RISC-V architecture sergiodj+buildbot
2016-11-01 23:23 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-10-31 17:24 [binutils-gdb] MIPS: Remove remains of IRIX OS ABI support sergiodj+buildbot
2016-10-31 18:42 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-10-29 16:50 [binutils-gdb] gdb/NEWS: Mention C++11 requirement sergiodj+buildbot
2016-10-29 17:55 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-10-29 16:13 [binutils-gdb] Support command-line redirection in native MS-Windows debugging sergiodj+buildbot
2016-10-29 16:38 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-10-17 23:24 [binutils-gdb] Fix duplicate test message in mi-trace-save.exp sergiodj+buildbot
2016-10-18  0:18 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-10-17 21:50 [binutils-gdb] Fix comment in mi-trace-save.exp sergiodj+buildbot
2016-10-17 22:53 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-10-17 16:34 [binutils-gdb] gdb: Fix phony iconv build sergiodj+buildbot
2016-10-17 17:22 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-10-17 13:56 [binutils-gdb] Removed pseudo invalid instructions opcodes sergiodj+buildbot
2016-10-17 14:12 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-10-17  9:46 [binutils-gdb] Sync libiberty sources with gcc mainline sergiodj+buildbot
2016-10-17 10:01 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-10-14 13:25 [binutils-gdb] Fix set sysroot command on AIX sergiodj+buildbot
2016-10-14 13:34 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-10-14 12:37 [binutils-gdb] [ARC] Disassembler: fix LIMM detection for short instructions sergiodj+buildbot
2016-10-14 12:37 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-10-13 15:27 [binutils-gdb] Share proc get_var_address sergiodj+buildbot
2016-10-13 16:29 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-10-13 14:54 [binutils-gdb] Skip testing structures with floating points sergiodj+buildbot
2016-10-13 15:12 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-10-13  4:50 [binutils-gdb] Remove unnecessary null_cleanup sergiodj+buildbot
2016-10-13  5:06 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-10-13  2:59 [binutils-gdb] Turn wchar iterator into a class sergiodj+buildbot
2016-10-13  3:53 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-10-13  1:21 [binutils-gdb] Convert tid_range_parser and get_number_or_range to classes sergiodj+buildbot
2016-10-13  1:34 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-10-12 11:51 [binutils-gdb] [AArch64] Track FP registers in prologue analyzer sergiodj+buildbot
2016-10-12 12:26 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-10-11 17:27 [binutils-gdb] testsuite: Fix gdb.arch/powerpc-prologue.c compilation sergiodj+buildbot
2016-10-11 17:38 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-10-11 10:42 [binutils-gdb] [AArch64] PR target/20666, fix wrong encoding of new introduced BFC pseudo sergiodj+buildbot
2016-10-11 10:53 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-10-11  7:59 [binutils-gdb] Always descend into output section statements in lang_do_assignments sergiodj+buildbot
2016-10-11  8:11 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-10-10  9:44 [binutils-gdb] Remove v850_dbtrap_breakpoint_from_pc sergiodj+buildbot
2016-10-10  9:55 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-10-09  0:26 [binutils-gdb] ui-out.c: Remove unused parameter to push_level sergiodj+buildbot
2016-10-09  1:52 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-10-07  7:33 [binutils-gdb] bfd_merge_private_bfd_data tidy sergiodj+buildbot
2016-10-07 10:45 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-10-07  7:22 [binutils-gdb] python: accept address and explicit locations in gdb.decode_line sergiodj+buildbot
2016-10-07 13:19 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-10-07  4:51 [binutils-gdb] Fix gdb.Value->python conversion for large unsigned ints sergiodj+buildbot
2016-10-07  8:03 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-10-06 23:29 [binutils-gdb] gdb: Remove some C compiler support leftovers sergiodj+buildbot
2016-10-07  8:56 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-10-06 16:49 [binutils-gdb] testsuite: solib-disc: Use `standard_output_file' sergiodj+buildbot
2016-10-06 18:21 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-10-06  0:04 [binutils-gdb] Don't use boolean OR in arithmetic expressions sergiodj+buildbot
2016-10-06  3:36 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-10-05 17:55 [binutils-gdb] PR gdb/20653 - small cleanup in string_to_explicit_location sergiodj+buildbot
2016-10-05 19:32 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-10-05 17:49 [binutils-gdb] PR symtab/20652 - fix psymbol_compare sergiodj+buildbot
2016-10-05 18:19 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-10-05 14:41 [binutils-gdb] arc: Remove annoying debug message sergiodj+buildbot
2016-10-05 14:48 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-10-05 11:11 [binutils-gdb] Update the path arm-*.xml files for aarch64 sergiodj+buildbot
2016-10-05 13:38 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-10-05  9:18 [binutils-gdb] Generate s390 target description c files sergiodj+buildbot
2016-10-05 11:10 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-09-30 19:17 [binutils-gdb] Add missing dependencies to BFD_H_FILES sergiodj+buildbot
2016-09-30 19:32 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-09-28 22:44 [binutils-gdb] [ARM] PR ld/20608 Relocation truncated to fit: R_ARM_THM_JUMP24 for relocation to PLT entry sergiodj+buildbot
2016-09-28 23:50 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-09-28  0:56 [binutils-gdb] Ensure that the timestamp in PE/COFF headers is always initialised sergiodj+buildbot
2016-09-28  1:27 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-09-26 22:57 [binutils-gdb] Fix the calculation of AMD64_PCRQUAD relocations sergiodj+buildbot
2016-09-27  1:30 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-09-26 11:09 [binutils-gdb] Call debug_exit in linux_wait_1 sergiodj+buildbot
2016-09-26 15:44 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-09-24  4:16 [binutils-gdb] Use std::vector in objfiles.c sergiodj+buildbot
2016-09-24 15:24 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-09-23 19:06 [binutils-gdb] Delete relocations associatesd with deleted exidx entries sergiodj+buildbot
2016-09-24  2:26 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-09-22 23:04 [binutils-gdb] Fix build breakage from commit 6ec2b2 sergiodj+buildbot
2016-09-23 22:22 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-09-22 14:56 [binutils-gdb] PR gdb/20604 - fix "quit" when an invalid expression is used sergiodj+buildbot
2016-09-23 16:24 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-09-22 12:08 [binutils-gdb] [AArch64] Use "must" rather than "should" in error messages sergiodj+buildbot
2016-09-23  6:48 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-09-22 10:26 [binutils-gdb] [AArch64][SVE 31/32] Add SVE instructions sergiodj+buildbot
2016-09-23  3:18 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-09-22  5:23 [binutils-gdb] [AArch64][SVE 24/32] Add AARCH64_OPND_SVE_PATTERN_SCALED sergiodj+buildbot
2016-09-22 13:37 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-09-22  4:21 [binutils-gdb] [AArch64][SVE 22/32] Add qualifiers for merging and zeroing predication sergiodj+buildbot
2016-09-22 10:36 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-09-22  2:34 [binutils-gdb] [AArch64][SVE 21/32] Add Zn and Pn registers sergiodj+buildbot
2016-09-22  9:19 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-09-22  1:25 [binutils-gdb] [AArch64][SVE 19/32] Refactor address-printing code sergiodj+buildbot
2016-09-22  6:12 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-09-22  0:34 [binutils-gdb] [AArch64][SVE 18/32] Tidy definition of aarch64-opc.c:int_reg sergiodj+buildbot
2016-09-22  5:25 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-09-21 23:40 [binutils-gdb] [AArch64][SVE 17/32] Add a prefix parameter to print_register_list sergiodj+buildbot
2016-09-22  3:55 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-09-21 23:35 [binutils-gdb] [AArch64][SVE 16/32] Use specific insert/extract methods for fpimm sergiodj+buildbot
2016-09-22  2:04 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-09-21 19:48 [binutils-gdb] [AArch64][SVE 02/32] Avoid hard-coded limit in indented_print sergiodj+buildbot
2016-09-21 19:49 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-09-20 21:40 [binutils-gdb] Avoid -Wduplicated-cond warnings in gdb/python sergiodj+buildbot
2016-09-21 12:29 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-09-19 23:22 [binutils-gdb] bfd: allow negative offsets to _GLOBAL_OFFSET_TABLE_ in elf64 SPARC sergiodj+buildbot
2016-09-20  0:43 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-09-19 16:45 [binutils-gdb] Consolidate target_mourn_inferior between GDB and gdbserver sergiodj+buildbot
2016-09-19 17:15 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-09-17  0:28 [binutils-gdb] linux-nat: Add function lwp_is_stepping sergiodj+buildbot
2016-09-17 16:39 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-09-16 23:32 [binutils-gdb] S390: Enable "maint set show-debug-regs" sergiodj+buildbot
2016-09-17  4:19 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-09-16 23:12 [binutils-gdb] S390: Multi-inferior watchpoint support sergiodj+buildbot
2016-09-17  1:20 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-09-16 20:49 [binutils-gdb] testsuite: Fix false FAIL in gdb.cp/casts.exp sergiodj+buildbot
2016-09-16 21:05 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-09-15 21:47 [binutils-gdb] Modify POWER9 support to match final ISA 3.0 documentation sergiodj+buildbot
2016-09-15 22:17 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-09-15  4:45 [binutils-gdb] Fix ld --gc-section segfault with ARMv8-M entry function in absolute section sergiodj+buildbot
2016-09-15 12:25 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-09-14 13:01 [binutils-gdb] Fix for gdb.server/non-existing-program.exp test case sergiodj+buildbot
2016-09-14 14:41 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-09-12 17:26 [binutils-gdb] Fix false FAIL on gdb.base/stap-probe.exp, due to ICF optimization sergiodj+buildbot
2016-09-12 17:35 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-09-10 23:25 [binutils-gdb] Pass HWCAP to ifunc resolver sergiodj+buildbot
2016-09-12  4:56 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-09-07  5:56 [binutils-gdb] Introduce make_cleanup_restore_current_ui sergiodj+buildbot
2016-09-07 18:58 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-09-07  0:07 [binutils-gdb] Add gdbarch callback to provide formats for debug info float types sergiodj+buildbot
2016-09-07 13:30 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-09-06 22:01 [binutils-gdb] Remove obsolete TYPE_FLAG_... values sergiodj+buildbot
2016-09-07  0:09 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-09-03 12:46 [binutils-gdb] Handle DW_OP_form_tls_address sergiodj+buildbot
2016-09-04 19:46 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-09-02  9:02 [binutils-gdb] Use target_continue{, _no_signal} instead of target_resume sergiodj+buildbot
2016-09-02  9:07 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-08-31 19:13 [binutils-gdb] PowerPC64, correct grouping of stubs for ld.bfd sergiodj+buildbot
2016-08-31 19:31 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-08-31  5:42 [binutils-gdb] Fixed issue with NULL pointer access on header var sergiodj+buildbot
2016-08-31 10:10 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-08-27 12:09 [binutils-gdb] Fix commit 980aa3e6 sergiodj+buildbot
2016-08-29 14:20 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-08-26 17:28 [binutils-gdb] Add missing ARMv8-M special registers sergiodj+buildbot
2016-08-27  0:26 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-08-26 17:24 [binutils-gdb] Dynamic TLS GOT entries would not be relocated sergiodj+buildbot
2016-08-26 20:03 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-08-26 16:28 [binutils-gdb] Fixed -init, -fini linker options sergiodj+buildbot
2016-08-26 18:11 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-08-26 12:23 [binutils-gdb] S390: Add support for core dump NOTE sections sergiodj+buildbot
2016-08-26 13:23 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-08-26 11:41 [binutils-gdb] S390: Indentation fixes in elf32/64-s390.c sergiodj+buildbot
2016-08-26 12:35 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-08-26 10:59 [binutils-gdb] xtensa: Avoid designated inits, for C++ compliance sergiodj+buildbot
2016-08-26 11:23 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-08-25  7:58 [binutils-gdb] Test case to detect recursive unwinding in Python-based unwinders sergiodj+buildbot
2016-08-25  9:29 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-08-24 20:24 [binutils-gdb] Allow resetting an empty inferior-tty sergiodj+buildbot
2016-08-25  9:01 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-08-24 18:43 [binutils-gdb] Fix for gdb.base/pc-fp.exp sergiodj+buildbot
2016-08-25  8:57 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-08-23 22:53 [binutils-gdb] Fix PR20494 - User input stops being echoed in CLI sergiodj+buildbot
2016-08-23 23:23 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-08-23 17:39 [binutils-gdb] gdbserver_spawn "" rather than gdbserver_spawn ${binfile} sergiodj+buildbot
2016-08-23 20:59 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-08-23 13:28 [binutils-gdb] R_OR1K_GOTOFF_* relocations sergiodj+buildbot
2016-08-23 13:43 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-08-22 21:15 [binutils-gdb] Free the string buffer used by the chew program to hold each file it parses sergiodj+buildbot
2016-08-22 22:29 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-08-22 20:15 [binutils-gdb] Error on unsupported PowerPC ifuncs sergiodj+buildbot
2016-08-22 20:56 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-08-19 19:59 [binutils-gdb] [AArch64] Match instruction "STP with base register" in prologue sergiodj+buildbot
2016-08-20  5:13 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-08-19 17:02 [binutils-gdb] x32: Avoid unsigned long when installing fast tracepoint jump pads sergiodj+buildbot
2016-08-19 17:20 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-08-19  6:30 [binutils-gdb] Fix for powerpc-power.exp gdb regression test for Power 9 sergiodj+buildbot
2016-08-19  8:49 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-08-18 15:13 [binutils-gdb] Fix remove-inferior error message sergiodj+buildbot
2016-08-18 20:24 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-08-18 14:37 [binutils-gdb] Add remove-inferiors test sergiodj+buildbot
2016-08-18 15:02 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-08-17 23:52 [binutils-gdb] Remove stale comment sergiodj+buildbot
2016-08-18 14:05 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-08-15 12:16 [binutils-gdb] sim: cgen: constify mode_names sergiodj+buildbot
2016-08-15 12:26 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-08-14  7:01 [binutils-gdb] sim: cgen: drop unused argv/envp definitions sergiodj+buildbot
2016-08-14  8:49 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-08-13 21:55 [binutils-gdb] Correct .dynsym sh_info sergiodj+buildbot
2016-08-13 21:55 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-08-12 10:33 [binutils-gdb] Fix fallout from gdb/20413's fix (x32: linux_ptrace_test_ret_to_nx: Cannot PTRACE_PEEKUSER) sergiodj+buildbot
2016-08-12 13:46 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-08-09 13:28 [binutils-gdb] Handle correctly passing a bad interpreter name to new-ui sergiodj+buildbot
2016-07-26 14:07 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-08-09 13:06 [binutils-gdb] linux-procfs: Introduce enum proc_state sergiodj+buildbot
2016-07-26 12:34 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-08-08 16:36 [binutils-gdb] Fix memory leaks in chew program sergiodj+buildbot
2016-08-09 11:42 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-08-04 16:49 [binutils-gdb] 2016-08-04 Thomas Preud'homme <thomas.preudhomme@arm.com> sergiodj+buildbot
2016-08-04 19:23 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-08-02 16:45 [binutils-gdb] [GDBserver] Remove td_ta_event_addr td_ta_set_event and td_ta_event_getmsg sergiodj+buildbot
2016-08-02 18:45 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-08-02 14:43 [binutils-gdb] Synchronize libiberty sources with FSF GCC mainline version sergiodj+buildbot
2016-08-02 14:52 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-08-02 12:23 [binutils-gdb] Fix SH GOT allocation in the presence of linker garbage collection sergiodj+buildbot
2016-08-02 12:56 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-08-01 13:20 [binutils-gdb] Swap "single-process" and "multi-process" in process-dies-while-detaching.exp sergiodj+buildbot
2016-08-01 13:41 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
     [not found] <db18dbabad8e7b63e98d47813ef20acac7072350@gdb-build>
2016-07-28  6:50 ` sergiodj+buildbot
     [not found] <293acfae4e3c9aad417e262edc9847c79bbbbb11@gdb-build>
2016-07-28  2:22 ` sergiodj+buildbot
     [not found] <6598661d14c90cabac1daa5e683d1e17883b2e41@gdb-build>
2016-07-27 18:38 ` sergiodj+buildbot
     [not found] <54806ffa85643c3a1ee721d5c3f5586d32f86ee1@gdb-build>
2016-07-27 17:21 ` sergiodj+buildbot
     [not found] <40c31709c6a51926fcb409611caa52b2da6515c0@gdb-build>
2016-07-27 16:31 ` sergiodj+buildbot
     [not found] <9cf12d57c58a82cfe3e6fee26d1ea55dfe49f9c4@gdb-build>
2016-07-27 11:00 ` sergiodj+buildbot
     [not found] <e0461dbb653dbb3c46ea7a15054fd2c98f879f31@gdb-build>
2016-07-26 21:14 ` sergiodj+buildbot
     [not found] <c0272db5854a799a9f3bb3803c3d03d1a62b9ac2@gdb-build>
2016-07-25 11:04 ` sergiodj+buildbot
2016-07-22  3:02 [binutils-gdb] Allow empty struct expressions in Rust sergiodj+buildbot
2016-07-22  3:05 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-07-22  0:11 [binutils-gdb] Set BFD_VERSION to 2.27.51 sergiodj+buildbot
2016-07-22  5:03 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-07-21 21:22 [binutils-gdb] Add -Wunused-but-set-* to build sergiodj+buildbot
2016-07-22  2:01 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-07-21 19:45 [binutils-gdb] Remove unused variable in windows-nat.c sergiodj+buildbot
2016-07-21 23:04 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-07-21 17:54 [binutils-gdb] Support vCont s and S actions with software single step sergiodj+buildbot
2016-07-21 20:54 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-07-21 12:41 [binutils-gdb] Create sub classes of 'struct breakpoint' sergiodj+buildbot
2016-07-21 14:10 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-07-21 11:10 [binutils-gdb] Skip gdb.server/ tests if lack of XML support sergiodj+buildbot
2016-07-21 12:17 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-07-20 20:22 [binutils-gdb] Enable ptrace events on new child processes sergiodj+buildbot
2016-07-20 23:47 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-07-20 18:21 [binutils-gdb] Handle version 1a of FreeBSD's NT_PRSINFO sergiodj+buildbot
2016-07-20 19:21 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-07-20  4:10 [binutils-gdb] Mark some more powerpc relocs as not handled by generic linker sergiodj+buildbot
2016-07-20  5:33 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-07-19 10:01 [binutils-gdb] Use do_self_tests in selftest.exp sergiodj+buildbot
2016-07-19 10:39 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-07-16 15:01 [binutils-gdb] Don't include libbfd.h outside of bfd, part 4 sergiodj+buildbot
2016-07-16 15:30 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-07-15 18:48 [binutils-gdb] GDB testsuite: Escape paths used in regular expressions sergiodj+buildbot
2016-07-15 18:56 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-07-15 11:25 [binutils-gdb] Tidy up debugging in the ARC port of the BFD library sergiodj+buildbot
2016-07-15 11:27 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-07-14 21:44 [binutils-gdb] BFD: Let targets handle relocations against absolute symbols sergiodj+buildbot
2016-07-14 23:57 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-07-14 18:10 [binutils-gdb] Use getcurx in curses code sergiodj+buildbot
2016-07-14 18:54 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-07-14  9:52 [binutils-gdb] Small improvements to the ARM simulator to cope with illegal binaries sergiodj+buildbot
2016-07-14 10:05 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-07-13 14:28 [binutils-gdb] opcodes, gas: support for the ldtxa SPARC instructions sergiodj+buildbot
2016-07-13 14:28 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-07-12 14:56 [binutils-gdb] Match the selftest output when captured_main is inlined sergiodj+buildbot
2016-07-12 15:05 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-07-12 10:20 [binutils-gdb] Fix grammar in error message sergiodj+buildbot
2016-07-12 10:34 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-07-07 15:52 [binutils-gdb] Fix of default lookup for "this" symbol sergiodj+buildbot
2016-07-07 16:01 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-07-06 16:12 [binutils-gdb] Remove extra output directory level for Ada tests sergiodj+buildbot
2016-07-06 17:56 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-07-06 13:14 [binutils-gdb] Use 'ptid_t' instead of 'ptid' for fbsd_next_vfork_done's return type sergiodj+buildbot
2016-07-06 13:27 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-07-05  9:02 [binutils-gdb] babeltrace compilation regression sergiodj+buildbot
2016-07-05  9:16 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-07-01 18:19 [binutils-gdb] Move fbsd_resume and related functions below fork following helper code sergiodj+buildbot
2016-07-01 18:47 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-07-01 16:41 [binutils-gdb] Fix Thumb-2 BL detection sergiodj+buildbot
2016-07-01 17:00 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-07-01 11:56 [binutils-gdb] Forget watchpoint locations when inferior exits or is killed/detached sergiodj+buildbot
2016-07-01 12:00 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-07-01  8:42 [binutils-gdb] x86: allow suffix-less movzw and 64-bit movzb sergiodj+buildbot
2016-07-01  9:10 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-06-30 15:32 [binutils-gdb] Fix typo in comment sergiodj+buildbot
2016-06-30 15:43 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-06-29 16:58 [binutils-gdb] Fix PR python/20129 - use of non-existing variable sergiodj+buildbot
2016-06-29 17:48 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-06-28 17:17 [binutils-gdb] [AArch64] Use int64_t for address offset sergiodj+buildbot
2016-06-28 18:05 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-06-28 16:19 [binutils-gdb] Fix typo in previous commit sergiodj+buildbot
2016-06-28 17:04 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-06-28 13:01 [binutils-gdb] Remove parameter sysret from linux_target_ops.get_syscall_trapinfo sergiodj+buildbot
2016-06-28 13:25 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-06-28  0:55 [binutils-gdb] MIPS16: Add R_MIPS16_PC16_S1 branch relocation support sergiodj+buildbot
2016-06-28  1:24 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-06-27 10:42 [binutils-gdb] Fix use of a dangling pointer for Python breakpoint objects sergiodj+buildbot
2016-06-27 11:30 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-06-25 16:48 [binutils-gdb] remove a few sentinals sergiodj+buildbot
2016-06-25 17:07 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-06-24 22:59 [binutils-gdb] Add a gdbarch 'print_auxv_entry' method for FreeBSD ABIs sergiodj+buildbot
2016-06-24 22:53 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-06-24 20:19 [binutils-gdb] Create a pseudo section for the ELF AUXV core dump note on FreeBSD sergiodj+buildbot
2016-06-24 21:08 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-06-24  6:09 [binutils-gdb] Move logic out of symbol_find_demangled_name sergiodj+buildbot
2016-06-24  6:20 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-06-22 23:12 [binutils-gdb] Add support for yet some more new ISA 3.0 instructions sergiodj+buildbot
2016-06-24  1:10 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-06-22  9:22 [binutils-gdb] tilegx: move TILEGX_NUM_PIPELINE_ENCODINGS to tilegx_pipeline enum sergiodj+buildbot
2016-06-23 22:49 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-06-22  3:18 [binutils-gdb] Arc assembler: Convert nps400 from a machine type to an extension sergiodj+buildbot
2016-06-23 20:02 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-06-21 23:24 [binutils-gdb] Add "new-ui console" tests sergiodj+buildbot
2016-06-23 17:22 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-06-21 22:18 [binutils-gdb] Always switch fork child to the main UI sergiodj+buildbot
2016-06-23 15:46 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-06-21 21:40 [binutils-gdb] Make mi-break.exp always expect breakpoint commands output on the main UI sergiodj+buildbot
2016-06-23 14:02 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-06-21 18:51 [binutils-gdb] Add new command to create extra console/mi UIs sergiodj+buildbot
2016-06-22 22:59 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-06-21 18:04 [binutils-gdb] Make stdin be per UI sergiodj+buildbot
2016-06-22 22:04 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-06-21 15:18 [binutils-gdb] Push thread->control.command_interp to the struct thread_fsm sergiodj+buildbot
2016-06-22  9:09 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-06-21 13:19 [binutils-gdb] Replace the sync_execution global with a new enum prompt_state tristate sergiodj+buildbot
2016-06-21 21:31 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-06-21 11:28 [binutils-gdb] Make raw_stdout be per MI instance sergiodj+buildbot
2016-06-21 18:45 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-06-21 10:04 [binutils-gdb] Make out and error streams be per UI sergiodj+buildbot
2016-06-21 10:53 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-06-21  6:37 [binutils-gdb] Make input_fd be per UI sergiodj+buildbot
2016-06-21  9:34 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-06-21  4:34 [binutils-gdb] Make the intepreters output to all UIs sergiodj+buildbot
2016-06-21  6:58 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-06-21  3:09 [binutils-gdb] Make the interpreters be per UI sergiodj+buildbot
2016-06-21  5:02 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-06-21  1:57 [binutils-gdb] Introduce "struct ui" sergiodj+buildbot
2016-06-21  3:09 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-06-20  2:13 [binutils-gdb] PR ld/20276: Set non_ir_ref on common symbol sergiodj+buildbot
2016-06-20  2:36 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-06-18 16:43 [binutils-gdb] Don't generate PLT for IFUNC GOT/pointer reference sergiodj+buildbot
2016-06-18 17:08 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-06-17 18:03 [binutils-gdb] Handle reinsert breakpoints for vforked child sergiodj+buildbot
2016-06-17 18:26 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-06-17 11:35 [binutils-gdb] gdb: new AndesTech NDS32 port sergiodj+buildbot
2016-06-17 12:50 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-06-16 15:53 [binutils-gdb] bfd/s390: Fix DT_PLTRELSZ in presence of R_390_IRELATIVE sergiodj+buildbot
2016-06-16 15:54 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-06-16  2:00 [binutils-gdb] Check SEC_ALLOC before allocating dynamic relocation sergiodj+buildbot
2016-06-16  2:41 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-06-14 17:03 [binutils-gdb] [ARC] Add ldbit for nps sergiodj+buildbot
2016-06-14 18:46 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-06-14 15:50 [binutils-gdb] [ARC] Add arithmetic and logic instructions for nps sergiodj+buildbot
2016-06-14 16:14 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-06-14  6:41 [binutils-gdb] Delete bfd_my_archive macro sergiodj+buildbot
2016-06-14  6:41 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-06-13 20:20 [binutils-gdb] MIPS/BFD: Update outdated comment about o32 R_MIPS_PC32 reloc support sergiodj+buildbot
2016-06-13 20:17 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-06-13 13:44 [binutils-gdb] Fix compile time warning about a redundant comparison in an assertion statement sergiodj+buildbot
2016-06-13 14:00 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-06-12  4:48 [binutils-gdb] Subtract GOT base only with a base register sergiodj+buildbot
2016-06-12  5:02 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-06-11  8:19 [binutils-gdb] Use size_t rather than bfd_size_type sergiodj+buildbot
2016-06-11  8:39 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-06-10 16:12 [binutils-gdb] Fix rust-exp handling in makefile sergiodj+buildbot
2016-06-10 16:43 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-06-09 21:14 [binutils-gdb] PR python/19819 - remove unused globals from py-xmethods.c sergiodj+buildbot
2016-06-09 21:47 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-06-07 16:02 [binutils-gdb] mi/mi-interp.c: Add missing braces sergiodj+buildbot
2016-06-07 16:26 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-06-07 11:49 [binutils-gdb] Frame static link: Handle null pointer sergiodj+buildbot
2016-06-07 12:19 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-06-06 21:21 [binutils-gdb] Add method/format information to =record-started sergiodj+buildbot
2016-06-06 21:39 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-06-03 23:15 [binutils-gdb] Handle indirect branches for AMD64 and Intel64 sergiodj+buildbot
2016-06-03 23:30 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-06-03 11:47 [binutils-gdb] Fix C++ build for Cygwin sergiodj+buildbot
2016-06-03 12:00 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-06-02 19:39 [binutils-gdb] Fix PR python/18984 sergiodj+buildbot
2016-06-02 20:07 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-06-02 15:40 [binutils-gdb] mi-memory-changed.exp: Fix filename passed to untested sergiodj+buildbot
2016-06-02 17:16 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-06-02 14:30 [binutils-gdb] Replace data32 with data16 in comments sergiodj+buildbot
2016-06-02 15:02 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-06-01 16:03 [binutils-gdb] Add new Serbian translation for the bfd library sergiodj+buildbot
2016-06-01 18:26 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-06-01  9:27 [binutils-gdb] infcmd, btrace: fix crash in 'finish' for tailcall-only frames sergiodj+buildbot
2016-06-01 11:03 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-06-01  8:46 [binutils-gdb] Wake up interruptible_select in remote_fileio ctrl-c handler sergiodj+buildbot
2016-06-01  9:16 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-05-31 19:07 [binutils-gdb] [PR gdb/19893] Fix handling of synthetic C++ references sergiodj+buildbot
2016-05-31 19:38 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-05-31 11:20 [binutils-gdb] Don't needlessly clear xmemdup allocated memory sergiodj+buildbot
2016-05-31 11:37 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-05-30 17:30 [binutils-gdb] Add variable length tests for emit_ref in trace-condition.exp sergiodj+buildbot
2016-05-30 20:58 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-05-30 17:04 [binutils-gdb] Add counter-cases for trace-condition.exp tests sergiodj+buildbot
2016-05-30 17:28 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-05-30 12:29 [binutils-gdb] Code cleanup: dwarf2_get_pc_bounds: -1/0/+1 -> enum sergiodj+buildbot
2016-05-30 12:46 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-05-29 18:59 [binutils-gdb] NEWS: QCatchSyscalls: simplify sergiodj+buildbot
2016-05-29 19:17 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-05-28 10:13 [binutils-gdb] MIPS/BFD: Enable local R_MIPS_26 overflow detection sergiodj+buildbot
2016-05-28 21:24 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-05-27 17:19 [binutils-gdb] Update x86 CPU_XXX_FLAGS handling sergiodj+buildbot
2016-05-28 16:11 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-05-27 15:15 [binutils-gdb] Replace CpuAMD64/CpuIntel64 with AMD64/Intel64 sergiodj+buildbot
2016-05-28 12:01 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-05-27 12:46 [binutils-gdb] gdb: Forward VALUE_LVAL when avoiding side effects for STRUCTOP_PTR sergiodj+buildbot
2016-05-27 15:03 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-05-25 17:04 [binutils-gdb] Enable 64-bit archives in ar and ranlib sergiodj+buildbot
2016-05-25 17:19 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-05-25 15:55 [binutils-gdb] Skip an archive element if not added by linker sergiodj+buildbot
2016-05-25 16:15 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-05-25  7:51 [binutils-gdb] Fortran, testsuite: Add testcases for nested structures sergiodj+buildbot
2016-05-25 11:26 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-05-25  7:40 [binutils-gdb] Fortran, typeprint: Decrease level of details when printing elements of a structure sergiodj+buildbot
2016-05-25 10:09 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-05-25  7:07 [binutils-gdb] Fortran, testsuite: Use multi_line in whatis_type testcase sergiodj+buildbot
2016-05-25  7:20 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-05-24 16:24 [binutils-gdb] add nb_inplace_divide for python 2 sergiodj+buildbot
2016-05-24 21:41 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-05-24 14:24 [binutils-gdb] [Linux] Avoid refetching core-of-thread if thread hasn't run sergiodj+buildbot
2016-05-24 16:40 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-05-24 14:06 [binutils-gdb] Linux native thread create/exit events support sergiodj+buildbot
2016-05-24 14:27 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-05-23 23:52 [binutils-gdb] Enable R_AARCH64_NONE for 64-bit code sergiodj+buildbot
2016-05-24  0:10 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-05-23 16:44 [binutils-gdb] [ARC] Update instruction type and delay slot info sergiodj+buildbot
2016-05-23 17:49 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-05-23  8:08 [binutils-gdb] Search for libutil-freebsd as alternative to libutil sergiodj+buildbot
2016-05-23  8:16 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-05-20 17:00 [binutils-gdb] Don't check R_386_GOT32 when setting need_convert_load sergiodj+buildbot
2016-05-20 17:12 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-05-19 13:44 [binutils-gdb] Fix invalid implicit conversions from void * sergiodj+buildbot
2016-05-19 14:51 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-05-19 10:25 [binutils-gdb] Remove unsupported `am34-*-linux*' target triplet sergiodj+buildbot
2016-05-19 12:42 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-05-19  5:14 [binutils-gdb] Fix ppc64le S-record test fail sergiodj+buildbot
2016-05-19  9:25 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-05-18 12:39 [binutils-gdb] MIPS/opcodes: Correct mixed MIPS16 and microMIPS disassembly sergiodj+buildbot
2016-05-19  4:32 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-05-18  6:45 [binutils-gdb] elf32-arm.c build breakage sergiodj+buildbot
2016-05-19  2:55 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-05-18  1:09 [binutils-gdb] Fix -exec-run not running asynchronously with mi-async on (PR gdb/18077) sergiodj+buildbot
2016-05-19  1:17 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-05-17 23:52 [binutils-gdb] Add Rust documentation sergiodj+buildbot
2016-05-18 22:40 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-05-17 22:37 [binutils-gdb] Add array start and end strings to generic_val_print_decorations sergiodj+buildbot
2016-05-17 23:58 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-05-17 21:36 [binutils-gdb] Update gdb test suite for Rust sergiodj+buildbot
2016-05-18 18:54 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-05-17 17:58 [binutils-gdb] Add DW_LANG_Rust sergiodj+buildbot
2016-05-17 18:28 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-05-13 20:38 [binutils-gdb] Accept valid one byte signed and unsigned values for the IMM8 operand sergiodj+buildbot
2016-05-13 21:07 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-05-12 15:11 [binutils-gdb] ld -z combreloc reloc sorting sergiodj+buildbot
2016-05-12 15:58 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-05-11 11:26 [binutils-gdb] [AArch64] Remove redundant tls relax in elfNN_aarch64_final_link_relocate sergiodj+buildbot
2016-05-11 12:30 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-05-11  1:45 [binutils-gdb] fix up two issues with the removal of unused variables sergiodj+buildbot
2016-05-11  2:39 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-05-10 19:42 [binutils-gdb] Enable Intel RDPID instruction sergiodj+buildbot
2016-05-10 23:38 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-05-10 18:49 [binutils-gdb] Use getters/setters to access ARM branch type sergiodj+buildbot
2016-05-10 21:23 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-05-10 16:24 [binutils-gdb] Allow extension availability to depend on several architecture bits sergiodj+buildbot
2016-05-10 17:12 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-05-09  8:25 [binutils-gdb] Redundant hash table check sergiodj+buildbot
2016-05-09  9:08 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-05-06 17:03 [binutils-gdb] Strip global symbol defined in discarded section sergiodj+buildbot
2016-05-06 17:40 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-05-05  9:13 [binutils-gdb] Initialize res in get_next_pcs_read_memory_unsigned_integer sergiodj+buildbot
2016-05-05  9:46 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-05-04 15:43 [binutils-gdb] [ARC] Add SYNTAX_NOP and SYNTAX_1OP for extension instructions sergiodj+buildbot
2016-05-04 17:49 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-05-04 13:48 [binutils-gdb] Introduce procedure use_gdb_stub sergiodj+buildbot
2016-05-04 14:37 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-05-04  0:22 [binutils-gdb] PR symtab/19914 fix handling of dwp + split debug sergiodj+buildbot
2016-05-04  4:39 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-05-03 23:21 [binutils-gdb] PR 10549: MIPS/LD: Handle OSABI setting for STB_GNU_UNIQUE sergiodj+buildbot
2016-05-04  0:07 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-05-03 12:30 [binutils-gdb] Fix gdb/python/python.c use-after-free sergiodj+buildbot
2016-05-03 18:35 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-05-03 11:27 [binutils-gdb] [AArch64] Also puts value in place for R_AARCH64_RELATIVE sergiodj+buildbot
2016-05-03 16:21 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-05-03 11:07 [binutils-gdb] Fix generation of AArhc64 instruction table sergiodj+buildbot
2016-05-03 15:19 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-05-03  9:56 [binutils-gdb] Fix "-Wl,--dynamic-list" gdb/configure test sergiodj+buildbot
2016-05-03 13:04 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-05-03  9:05 [binutils-gdb] [gdb] Fix -Wparentheses warnings sergiodj+buildbot
2016-05-03  9:47 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-05-02 17:20 [binutils-gdb] Fix annota-input-while-running.exp remote check sergiodj+buildbot
2016-05-02 18:27 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-04-29 15:45 [binutils-gdb] Pass GOT_RELOC to UNDEFINED_WEAK_RESOLVED_TO_ZERO sergiodj+buildbot
2016-04-29 16:35 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-04-29 12:01 [binutils-gdb] X86-64: Set check_relocs_failed on error sergiodj+buildbot
2016-04-29 12:43 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-04-28 18:29 [binutils-gdb] Don't show deprecated commands in help sergiodj+buildbot
2016-04-28 20:56 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-04-15 23:19 [binutils-gdb] MIPS/Linux: Also recognize TRAP_BRKPT and TRAP_HWBKPT sergiodj+buildbot
2016-04-15 23:57 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-04-14 11:19 [binutils-gdb] Fix copying Solaris binaries with objcopy sergiodj+buildbot
2016-04-14 12:07 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-04-13 20:40 [binutils-gdb] Debugging without a binary (regression) sergiodj+buildbot
2016-04-14  9:31 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-04-13  6:32 [binutils-gdb] Eliminate immediate_quit sergiodj+buildbot
2016-04-13 21:58 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-04-13  5:01 [binutils-gdb] Use target_terminal_ours_for_output in MI sergiodj+buildbot
2016-04-13 19:13 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-04-13  2:29 [binutils-gdb] Use target_terminal_ours_for_output in exceptions.c sergiodj+buildbot
2016-04-13 14:36 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-04-13  2:05 [binutils-gdb] Fix inconsistent handling of EINTR in ser-*.c backends sergiodj+buildbot
2016-04-13 12:00 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-04-12 20:57 [binutils-gdb] Use target_terminal_ours_for_output in warning/internal_error sergiodj+buildbot
2016-04-13 16:39 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-04-12 20:54 [binutils-gdb] Make Python use a struct serial event sergiodj+buildbot
2016-04-13  1:16 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-04-12 16:45 [binutils-gdb] Inline command_loop in read_command_line sergiodj+buildbot
2016-04-12 17:51 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-04-11 17:20 [binutils-gdb] MIPS/opcodes: Fix undecoded MIPS16 extended instruction bit disassembly sergiodj+buildbot
2016-04-11 18:00 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-04-08 23:05 [binutils-gdb] Make gdb.server/solib-list.exp work for remote targets sergiodj+buildbot
2016-04-08 23:40 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-04-08 18:24 [binutils-gdb] value: Make accessor methods' parameters const-correct sergiodj+buildbot
2016-04-08 19:17 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-04-07 17:52 [binutils-gdb] gas/arc: Handle multiple arc_opcode chains for same mnemonic sergiodj+buildbot
2016-04-07 19:55 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-04-07 16:55 [binutils-gdb] Fix gdb.reverse/next-reverse-bkpt-over-sr.exp sergiodj+buildbot
2016-04-07 18:20 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-04-06 21:44 [binutils-gdb] Optimized-out pointer: New test for error handling sergiodj+buildbot
2016-04-06 22:29 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-04-06  8:42 [binutils-gdb] Fix memory leak in ld ARM backend sergiodj+buildbot
2016-04-06  9:17 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-04-05 22:02 [binutils-gdb] arc/nps400: Add additional instructions sergiodj+buildbot
2016-04-06  0:10 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-04-05 18:35 [binutils-gdb] Improve gdb_remote_download, remove gdb_download sergiodj+buildbot
2016-04-05 22:23 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-04-05 16:09 [binutils-gdb] [ARC] 24 bit reloc and overflow detection fix sergiodj+buildbot
2016-04-05 17:39 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-04-05 15:04 [binutils-gdb] [ARC] Dynamic relocs verification for dynindx == -1 sergiodj+buildbot
2016-04-05 15:59 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-04-04 14:48 [binutils-gdb] Fix gdb.mi/mi-breakpoint-changed.exp for remote targets sergiodj+buildbot
2016-04-04 15:25 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-04-01 15:14 [binutils-gdb] gdb: allow enumeration constants as second operand of BINOP_REPEAT sergiodj+buildbot
2016-04-01 16:08 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-03-31 22:48 [binutils-gdb] gdbserver: Fix C++ build errors in tracepoint.c sergiodj+buildbot
2016-04-01  1:50 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-03-31 19:22 [binutils-gdb] Add regression test for PR gdb/19858 (JIT code registration on attach) sergiodj+buildbot
2016-03-31 22:05 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-03-31 19:01 [binutils-gdb] Fix PR gdb/19858: GDB doesn't register the JIT libraries on attach sergiodj+buildbot
2016-03-31 19:31 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-03-31 14:33 [binutils-gdb] IPA: Add alloc_jump_pad_buffer target hook sergiodj+buildbot
2016-03-31 15:47 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-03-31 12:58 [binutils-gdb] python: Use console format for output of gdb.execute command sergiodj+buildbot
2016-03-31 14:06 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-03-30 16:17 [binutils-gdb] Simplify gdb.reverse/until-reverse.c sergiodj+buildbot
2016-03-30 17:24 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-03-30  0:32 [binutils-gdb] gdbserver: Handle 'v' packet while processing qSymbol sergiodj+buildbot
2016-03-30 11:01 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-03-30  0:26 [binutils-gdb] gdb/NEWS: Add mention of s390*-linux tracepoints sergiodj+buildbot
2016-03-30  9:01 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-03-29 22:49 [binutils-gdb] gdbserver/s390: Add support for compiled agent expressions sergiodj+buildbot
2016-03-30  1:35 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-03-29 13:24 [binutils-gdb] [ARC] Add support for Quarkse opcodes sergiodj+buildbot
2016-03-29 14:19 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-03-29  5:59 [binutils-gdb] PE/COFF regression in base of code and data calculation sergiodj+buildbot
2016-03-29  9:37 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-03-24 17:25 [binutils-gdb] sparc: reorder wr instructions in sparc_opcodes to fix diagnostics sergiodj+buildbot
2016-03-24 21:56 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-03-22 23:14 [binutils-gdb] make more variables const sergiodj+buildbot
2016-03-23  0:18 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-03-22 12:26 [binutils-gdb] Attribute with DW_FORM_flag_present sergiodj+buildbot
2016-03-22 13:25 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-03-22 10:41 [binutils-gdb] Fix possible unbounded stack use in peXXigen.c sergiodj+buildbot
2016-03-22 11:35 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-03-18 18:39 [binutils-gdb] Fix the disassembly of the AArch64's OOR instruction as a MOV instruction sergiodj+buildbot
2016-03-20  5:36 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-03-18 15:17 [binutils-gdb] Check lwp_signal_can_be_delivered for enqueue/dequeue pending signals sergiodj+buildbot
2016-03-19 14:41 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-03-18 14:39 [binutils-gdb] Remove redundant WIFSTOPPED check sergiodj+buildbot
2016-03-19  0:58 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-03-17  9:47 [binutils-gdb] linux-record: Simplify with record_mem_at_reg() sergiodj+buildbot
2016-03-18  4:54 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-03-16 19:42 [binutils-gdb] Process record: Fix arm-linux syscall arguments sergiodj+buildbot
2016-03-16 22:29 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-03-16 17:48 [binutils-gdb] xml-tdesc.c (tdesc_start_enum): Fix c++ build sergiodj+buildbot
2016-03-17 23:01 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-03-16 16:29 [binutils-gdb] [ARM] Support ARMv8.2 FP16 simd instructions sergiodj+buildbot
2016-03-17  9:39 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-03-15 17:14 [binutils-gdb] Fix PR gdb/19676: Internal error in linux-thread.db.c if /proc not mounted sergiodj+buildbot
2016-03-15 19:26 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-03-13 10:06 [binutils-gdb] gdb/s390: Fill gen_return_address hook sergiodj+buildbot
2016-03-13 11:11 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-03-11  9:28 [binutils-gdb] Fix some places where octet to byte conversions are needed sergiodj+buildbot
2016-03-11 10:12 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-03-10 22:34 [binutils-gdb] Add $_as_string convenience function sergiodj+buildbot
2016-03-11  6:40 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-03-09 22:03 [binutils-gdb] gdb.trace/change-loc.exp: Don't depend on tracepoint ordering sergiodj+buildbot
2016-03-10  6:00 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-03-09 21:55 [binutils-gdb] More "Program" -> "Thread NN received signal" testsuite adjustment sergiodj+buildbot
2016-03-11  3:59 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-03-09 21:09 [binutils-gdb] Simplify saved_command_line handling sergiodj+buildbot
2016-03-10 23:54 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-03-09 20:47 [binutils-gdb] Use struct buffer in gdb_readline_no_editing sergiodj+buildbot
2016-03-10 21:18 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-03-09 20:36 [binutils-gdb] gdb_readline -> gdb_readline_no_editing sergiodj+buildbot
2016-03-10 19:42 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-03-09 20:27 [binutils-gdb] Update prompt_for_continue comments sergiodj+buildbot
2016-03-10 18:09 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-03-09 20:15 [binutils-gdb] Eliminate async_annotation_suffix sergiodj+buildbot
2016-03-10 16:20 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-03-09 20:06 [binutils-gdb] gdb_readline2 -> gdb_readline_no_editing_callback sergiodj+buildbot
2016-03-10 14:41 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-03-09 19:54 [binutils-gdb] Garbage collect window_hook sergiodj+buildbot
2016-03-10 12:43 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-03-09 19:21 [binutils-gdb] gdb.trace/entry-values.exp: Fixes for powerpc64 sergiodj+buildbot
2016-03-10  8:20 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-03-09 16:19 [binutils-gdb] Avoid spaces in osabi names sergiodj+buildbot
2016-03-09 20:53 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-03-09 15:59 [binutils-gdb] Fix v850 bfd arch info printable names sergiodj+buildbot
2016-03-09 18:20 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-03-09 15:43 [binutils-gdb] For COFF and COFF/PE targets, skip relocations against absolute symbols sergiodj+buildbot
2016-03-09 16:37 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-03-08 17:47 [binutils-gdb] Handle local IFUNC symbols in shared object sergiodj+buildbot
2016-03-08 18:39 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-03-07 16:52 [binutils-gdb] Fix "set architecture mips:10000" crash sergiodj+buildbot
2016-03-07 19:52 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-03-06  1:57 [binutils-gdb] Improve analysis of racy testcases sergiodj+buildbot
2016-03-06  3:38 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-03-04 17:01 [binutils-gdb] ARM process record: VMOV sergiodj+buildbot
2016-03-04 19:48 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-03-04 16:41 [binutils-gdb] Add missing ChangeLog entries for commit 82838 sergiodj+buildbot
2016-03-04 21:11 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-03-04 15:16 [binutils-gdb] feature_to_c.sh: Print help when passing no arguments sergiodj+buildbot
2016-03-04 16:46 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-03-04 14:50 [binutils-gdb] Treat common symbol in executable as definition sergiodj+buildbot
2016-03-04 15:33 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-03-03 21:03 [binutils-gdb] get_symbols() plugin API tweak to support --start-lib/--end-lib sergiodj+buildbot
2016-03-04  0:47 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-03-03 15:34 [binutils-gdb] Fix bugs in the simulation of the AArch64's ADDP, FADDP, LD1, CCMP and CCMP instructions sergiodj+buildbot
2016-03-03 21:58 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-03-03 10:36 [binutils-gdb] Update comments to start_step_over sergiodj+buildbot
2016-03-03 20:07 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-03-03 10:00 [binutils-gdb] Step over fork/vfork syscall insn in gdbserver sergiodj+buildbot
2016-03-03 14:44 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-03-02 17:06 [binutils-gdb] testsuite: Fix timeout issues during print of vla-arrays sergiodj+buildbot
2016-03-02 23:46 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-03-01 18:47 [binutils-gdb] Fix gdb.trace/ftrace-lock.c compilation sergiodj+buildbot
2016-03-01 23:21 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-03-01 17:53 [binutils-gdb] Fix gdb.threads/watchpoint-fork*.c compilation sergiodj+buildbot
2016-03-01 21:31 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-02-26 17:52 [binutils-gdb] Optimize x86 GOT32X/GOTPCRELX relocations sergiodj+buildbot
2016-02-27  7:39 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
     [not found] <ab50308758bfde9ab7b50e6def65e20f0b560702@gdb-build>
2016-02-26  8:44 ` sergiodj+buildbot
2016-02-24 23:37 [binutils-gdb] Update symbol version for symbol from linker script sergiodj+buildbot
2016-02-25  7:41 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-02-24 19:30 [binutils-gdb] Move tfile-avx.exp to tracefile-pseudo-reg.exp sergiodj+buildbot
2016-02-24 19:39 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-02-24 18:24 [binutils-gdb] Move new skip features to proper section (post 7.11) sergiodj+buildbot
2016-02-24 18:33 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-02-24 17:45 [binutils-gdb] powerpc: Support z-point type in gdbserver sergiodj+buildbot
2016-02-24 17:54 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-02-24 15:09 [binutils-gdb] Revert "ABS32" sergiodj+buildbot
2016-02-24 16:12 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-02-24 14:22 [binutils-gdb] [OPCODES][ARM][1/3]Add armv8.2 fp16 instruction dissembler support sergiodj+buildbot
2016-02-24 16:01 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-02-24 14:12 [binutils-gdb] [OPCODES][ARM]Fix mask for a few coprocessor opcodes sergiodj+buildbot
2016-02-24 15:42 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-02-24 14:09 [binutils-gdb] [OPCODE][ARM]Correct disassembler for cdp/cdp2, mcr/mcr2, mrc/mrc2, ldc/ldc2, stc/stc2 sergiodj+buildbot
2016-02-24 15:22 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-02-24 14:07 [binutils-gdb] ABS32 sergiodj+buildbot
2016-02-24 14:54 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-02-24 13:54 [binutils-gdb] Set plt_got.offset to (bfd_vma) -1 sergiodj+buildbot
2016-02-24 14:20 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-02-24 12:00 [binutils-gdb] Fix logic in exec_file_locate_attach sergiodj+buildbot
2016-02-24 12:40 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-02-24  3:22 [binutils-gdb] Build unavailable-stack frames for tracepoint sergiodj+buildbot
2016-02-24  3:38 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-02-23 18:34 [binutils-gdb] arm-tdep.c: Remove unused "to" parameters sergiodj+buildbot
2016-02-23 19:21 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-02-22 12:34 [binutils-gdb] [AArch64] Remove redundant calculation of plt stub destination for veneer sergiodj+buildbot
2016-02-22 14:23 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-02-21 20:46 [binutils-gdb] Remove search_parents parameter from d_lookup_symbol_imports sergiodj+buildbot
2016-02-21 21:12 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-02-18 21:14 [binutils-gdb] Add D support to gdb_default_target_compile sergiodj+buildbot
2016-02-18 22:37 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-02-17 19:31 [binutils-gdb] [x86-64] Omit dynamic sections symbols sergiodj+buildbot
2016-02-17 20:26 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-02-16 14:26 [binutils-gdb] Fix cleanup in arm_linux_software_single_step sergiodj+buildbot
2016-02-16 20:16 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-02-12  9:10 [binutils-gdb] stack: check frame_unwind_caller_id sergiodj+buildbot
2016-02-12 12:23 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-02-10 11:38 [binutils-gdb] Correct assertion in NIOS2 linker to allow signed 16-buit immediate values sergiodj+buildbot
2016-02-11  8:51 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-02-09 23:05 [binutils-gdb] Use string_to_event_location_basic in guile sergiodj+buildbot
2016-02-10  9:45 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-02-09 22:48 [binutils-gdb] Refactor string_to_event_location for legacy linespec support sergiodj+buildbot
2016-02-09 23:48 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
     [not found] <8adce0342f5f50aba0154fc56ca59df45b219738@gdb-build>
2016-02-09 17:16 ` sergiodj+buildbot
2016-02-09 11:06 [binutils-gdb] Add a more helpful warning message to explain why some AArch64 relocations can overflow sergiodj+buildbot
2016-02-09 15:39 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-02-08 19:12 [binutils-gdb] Fix in-tree, parallel running of Ada tests sergiodj+buildbot
2016-02-08 20:56 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-02-01 18:40 [binutils-gdb] gdb: Guard against undefined behaviour in mi-vla-fortran.exp sergiodj+buildbot
2016-02-01 20:19 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-02-01 18:23 [binutils-gdb] gdb: New set/show max-value-size command sergiodj+buildbot
2016-02-01 19:03 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-01-31  0:17 [binutils-gdb] Check reloc against IFUNC symbol only with dynamic symbols sergiodj+buildbot
2016-01-31  3:24 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-01-29 20:45 [binutils-gdb] Fix two misleading indentation warnings sergiodj+buildbot
2016-01-29 21:35 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-01-28 21:00 [binutils-gdb] Sync libiberty with GCC sergiodj+buildbot
2016-01-28 21:37 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-01-26 14:40 [binutils-gdb] [GDBserver] Use regcache_read_pc in install_software_single_step_breakpoints sergiodj+buildbot
2016-01-26 17:08 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-01-26 14:03 [binutils-gdb] [GDBserver] Check input interrupt after reading in a packet sergiodj+buildbot
2016-01-26 14:43 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-01-25  9:41 [binutils-gdb] Fix memory corruption on Mach-O systems by suppressing a memory tidy up sergiodj+buildbot
2016-01-25  9:47 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-01-22  0:30 [binutils-gdb] * lib/ada.exp (gdb_compile_ada): Fix typo sergiodj+buildbot
2016-01-22  8:19 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-01-21 10:33 [binutils-gdb] Fix regression introduced in "break *<EXPR>" by explicit location patches sergiodj+buildbot
2016-01-21 18:04 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-01-20 14:43 [binutils-gdb] [AArch64] Reject invalid immediate operands to MSR UAO sergiodj+buildbot
2016-01-21  6:15 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-01-20 13:05 [binutils-gdb] Add support for an ARM specific 'y' section attribute flag to mark the section as NOREAD sergiodj+buildbot
2016-01-21  0:30 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-01-20  4:14 [binutils-gdb] minor reformatting in printcmd.c::print_scalar_formatted sergiodj+buildbot
2016-01-20 20:44 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-01-19 23:43 [binutils-gdb] Use a separate variable for the size passed to sysctl sergiodj+buildbot
2016-01-20 15:31 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-01-19 18:00 [binutils-gdb] Dump register notes for each thread when generating a FreeBSD core sergiodj+buildbot
2016-01-20 11:47 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-01-19 17:26 [binutils-gdb] Add support for extracting thread names from cores sergiodj+buildbot
2016-01-20  4:26 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-01-18 22:01 [binutils-gdb] MIPS: Only build microMIPS specific simulator functions if microMIPS support is required sergiodj+buildbot
2016-01-18 23:14 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-01-18 15:19 [binutils-gdb] Replace some $ARCH_{get, set}_pc with linux_{get, set}_pc_64bit sergiodj+buildbot
2016-01-18 17:29 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-01-12 15:09 [binutils-gdb] Remove trademark acknowledgements throughout sergiodj+buildbot
2016-01-12 15:52 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-01-11 21:16 [binutils-gdb] testsuite: Fix false FAILs on too long base directory sergiodj+buildbot
2016-01-11 22:13 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-01-11 18:06 [binutils-gdb] Delete opcodes that have been removed from ISA 3.0 sergiodj+buildbot
2016-01-11 18:53 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2016-01-11  0:08 [binutils-gdb] sim: move many common settings from CPPFLAGS to config.h sergiodj+buildbot
2016-01-11  5:36 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-12-30  0:30 [binutils-gdb] sim: ppc: track closed state of file descriptors 0, 1, and 2 sergiodj+buildbot
2015-12-30  1:39 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-12-26 19:56 [binutils-gdb] sim: sim-core: pass down cpu to hw accesses when available sergiodj+buildbot
2015-12-26 22:15 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-12-25  8:19 [binutils-gdb] sim: arm: delete unused code sergiodj+buildbot
2015-12-26  7:58 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-12-25  1:00 [binutils-gdb] sim: delete SIM_HAVE_MEM_SIZE sergiodj+buildbot
2015-12-25 13:52 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-12-25  0:34 [binutils-gdb] sim: delete SIM_HAVE_SIMCACHE sergiodj+buildbot
2015-12-25  3:20 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-12-24  5:38 [binutils-gdb] [testsuite/Ada] stop using project files when building test programs sergiodj+buildbot
2015-12-24  6:16 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-12-22 16:10 [binutils-gdb] Remove HP-UX reference in foll-vfork.exp sergiodj+buildbot
2015-12-22 21:43 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-12-21 19:50 [binutils-gdb] Remove dead code in testsuite sergiodj+buildbot
2015-12-21 20:33 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-12-17 21:47 [binutils-gdb] [ARM] Enable CRC by default for ARMv8.1 and later sergiodj+buildbot
2015-12-19 11:59 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-12-17 16:37 [binutils-gdb] Target remote mode fork and exec test updates sergiodj+buildbot
2015-12-18 20:33 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-12-17  9:52 [binutils-gdb] gdb: Extend help text for 'list' command sergiodj+buildbot
2015-12-18  1:51 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-12-17  3:20 [binutils-gdb] gdb: Small code restructure for list_command sergiodj+buildbot
2015-12-17 20:19 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-12-17  1:05 [binutils-gdb] Remove "spaces" references from gdb.multi/base.exp sergiodj+buildbot
2015-12-17  5:24 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-12-17  0:22 [binutils-gdb] Stop using nowarnings in gdb/testsuite/gdb.multi/ sergiodj+buildbot
2015-12-17  1:26 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-12-10 16:00 [binutils-gdb] Remove support for thread events without PTRACE_EVENT_CLONE in GDB sergiodj+buildbot
2015-12-10 18:46 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-12-10  0:31 [binutils-gdb] Fix GOT address computations in initial PLT entries for nios2 sergiodj+buildbot
2015-12-10  2:36 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-12-07 14:59 [binutils-gdb] Fix relaxation in RX linker when --no-keep-memory is specified sergiodj+buildbot
2015-12-07 23:56 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-12-01  4:06 [binutils-gdb] Fix instruction skipping when using software single step in GDBServer sergiodj+buildbot
2015-12-01 18:33 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-11-30 22:15 [binutils-gdb] Fix breakpoint size when stepping over a permanent breakpoint in GDBServer sergiodj+buildbot
2015-12-01 17:02 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-11-28 17:44 [binutils-gdb] PR other/61321 - demangler crash on casts in template parameters sergiodj+buildbot
2015-11-29  0:25 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
     [not found] <e19616610d7327664f99215a69cb326682742dc3@gdb-build>
2015-11-28  0:54 ` sergiodj+buildbot
2015-11-24 19:08 [binutils-gdb] List inferiors/threads/pspaces in ascending order sergiodj+buildbot
2015-11-24 22:25 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-11-20 14:07 [binutils-gdb] binutils: add support for arm-*-darwin and aarch64-*-darwin sergiodj+buildbot
2015-11-21  0:34 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-11-20 13:08 [binutils-gdb] Synchronize PDP11 page size between BFD and LD sergiodj+buildbot
2015-11-21  0:19 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
     [not found] <bb82e93484cdd56c67efd52b869a6123b2623f6c@gdb-build>
2015-11-20 12:49 ` sergiodj+buildbot
2015-11-19 18:47 [binutils-gdb] gdb: Workaround bad gdbserver qSupported:xmlRegisters=i386; UnknwnFeat+ handling sergiodj+buildbot
2015-11-20 15:38 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-11-18 12:02 [binutils-gdb] Fix out of boundary access in pass_in_v sergiodj+buildbot
2015-11-18 12:30 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-11-18 11:52 [binutils-gdb] Prevent looping in archives sergiodj+buildbot
2015-11-18 12:14 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-11-18 11:42 [binutils-gdb] mach-o cleanup: remove useless calls to bfd_seek sergiodj+buildbot
2015-11-18 11:52 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-11-18  4:25 [binutils-gdb] sim: mn10300/v850: drop unused WITH_CORE define sergiodj+buildbot
2015-11-18 10:08 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-11-18  4:18 [binutils-gdb] sim: always enable modulo memory sergiodj+buildbot
2015-11-18  9:54 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-11-17 21:29 [binutils-gdb] [sim/ppc] Fix printf_filtered reference sergiodj+buildbot
2015-11-18  9:38 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-11-17 17:26 [binutils-gdb] Fix gdb.threads/multiple-step-overs.exp fails on arm sergiodj+buildbot
2015-11-18  9:20 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-11-17 17:18 [binutils-gdb] Introduce null_block_symbol sergiodj+buildbot
2015-11-18  9:00 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-11-17 17:09 [binutils-gdb] [C++] Always use setjmp/longjmp for exceptions sergiodj+buildbot
2015-11-18  8:42 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-11-17 17:01 [binutils-gdb] MinGW and attribute format(printf/gnu_printf) sergiodj+buildbot
2015-11-18  8:26 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-11-17 16:22 [binutils-gdb] [C++/mingw] handle_output_debug_string sergiodj+buildbot
2015-11-18  3:01 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-11-17 11:47 [binutils-gdb] Fix the disassembly of conditional instructions will illegal condition selections sergiodj+buildbot
2015-11-17 12:57 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-11-15  6:14 [binutils-gdb] sim: testsuite: support basic vars in flags sergiodj+buildbot
2015-11-15 19:31 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-11-15  0:35 [binutils-gdb] Bump version to 2.26.51 sergiodj+buildbot
2015-11-15 12:40 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-11-10  5:32 [binutils-gdb] sim: m32c: move test code to testsuite sergiodj+buildbot
2015-11-10  8:15 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-11-09  5:01 [binutils-gdb] Copy gnulib obstack files sergiodj+buildbot
2015-11-09  5:45 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-11-05  9:59 [binutils-gdb] Use aarch64_decode_insn in aarch64_analyze_prologue sergiodj+buildbot
2015-11-05 14:09 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
     [not found] <10268a4c0d64b3892397aeaafbc4b91f6a1e0dc8@gdb-build>
2015-10-31 19:07 ` sergiodj+buildbot
2015-10-29 17:35 [binutils-gdb] gnu-v2-abi.c: Add casts sergiodj+buildbot
2015-10-30  5:01 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-10-27  5:19 [binutils-gdb] Fix access_to_packed_array.exp typos/errors sergiodj+buildbot
2015-10-27 19:34 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-10-24 23:13 [binutils-gdb] sparc64-tdep.c: Don't assign using memcpy return sergiodj+buildbot
2015-10-25 13:38 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-10-22 16:10 [binutils-gdb] Add cast in nto-tdep.c sergiodj+buildbot
2015-10-23  7:13 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-10-21 19:47 [binutils-gdb] fort_dyn_array: add basic fortran dyn array support sergiodj+buildbot
2015-10-22  3:25 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-10-21 14:47 [binutils-gdb] [nto] Fix nto target stopped by watchpoint sergiodj+buildbot
2015-10-21 15:24 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
     [not found] <170742de5dd5be2156f938e00e2451526ef57d5c@gdb-build>
2015-10-13 22:27 ` sergiodj+buildbot
2015-10-13 18:50 [binutils-gdb] ada-lang.c: malloc/alloca casts for C++ sergiodj+buildbot
2015-10-13 20:06 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-10-12 16:35 [binutils-gdb] aarch64: Use gdb_sys_no_syscall enum instead of -1 sergiodj+buildbot
2015-10-13  3:09 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-10-12 11:36 [binutils-gdb] New test case gdb.arch/disp-step-insn-reloc.exp sergiodj+buildbot
2015-10-12 19:18 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-10-09 22:00 [binutils-gdb] Reorder variable declarations in ada_value_primitive_packed_val sergiodj+buildbot
2015-10-10  5:26 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-10-08  7:41 [binutils-gdb] btrace: fix void return sergiodj+buildbot
2015-10-08  7:48 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-10-07 14:29 [binutils-gdb] Avoid using 'template' C++ keyword sergiodj+buildbot
2015-10-07 14:35 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-10-07 14:11 [binutils-gdb] Wrap include/opcode/aarch64.h in extern "C" for C++ sergiodj+buildbot
2015-10-07 14:17 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-10-07 13:26 [binutils-gdb] New ARC implementation sergiodj+buildbot
2015-10-07 13:41 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-10-02 14:46 [binutils-gdb] [aarch64] expose disas_aarch64_insn and rename it to aarch64_decode_insn sergiodj+buildbot
2015-10-02 16:29 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-09-25 20:12 [binutils-gdb] The FT32's disassembly of 10-bit literals has the incorrect mask sergiodj+buildbot
2015-09-26  7:49 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-09-21 14:29 [binutils-gdb] Wrap gdb_agent_op_sizes by #ifndef IN_PROCESS_AGENT sergiodj+buildbot
2015-09-21 17:51 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-09-18 14:15 [binutils-gdb] btrace: resume all requested threads sergiodj+buildbot
2015-09-19  8:42 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-09-18 14:04 [binutils-gdb] btrace: add missing NO_HISTORY sergiodj+buildbot
2015-09-19  2:23 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-09-18  4:32 [binutils-gdb] Remove one unnecessary iteration in insertion sort sergiodj+buildbot
2015-09-18  8:43 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-09-16 15:53 [binutils-gdb] non-stop-fair-events.exp slower on software single-step && !displ-step targets sergiodj+buildbot
2015-09-18  4:11 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-09-16 15:38 [binutils-gdb] Make it easier to debug non-stop-fair-events.exp sergiodj+buildbot
2015-09-18  4:00 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-09-16 15:03 [binutils-gdb] Don't skip gdb.asm/asm-source.exp on aarch64 sergiodj+buildbot
2015-09-18  3:51 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-09-16 13:43 [binutils-gdb] Fix slowdown in ld -r for most common case of out-of-order relocs sergiodj+buildbot
2015-09-17 19:50 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-09-15 22:14 [binutils-gdb] [Ada] Enhance type printing for arrays with variable-sized elements sergiodj+buildbot
2015-09-17 11:36 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-09-15 21:24 [binutils-gdb] Handle clang naming of function static local variable sergiodj+buildbot
2015-09-17 11:17 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-09-15 19:46 [binutils-gdb] Fix PR/18564 - regression in showing __thread so extern variable sergiodj+buildbot
2015-09-17 10:51 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-09-15 18:25 [binutils-gdb] [ppc64le] Use skip_entrypoint for skip_trampoline_code sergiodj+buildbot
2015-09-16 16:17 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-09-15 17:47 [binutils-gdb] gdbserver: Fix exec stop reply reporting conditions sergiodj+buildbot
2015-09-16 12:57 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-09-15 16:59 [binutils-gdb] Fix gdb.threads/non-ldr-exc-3.exp race sergiodj+buildbot
2015-09-15 20:32 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-09-15 14:02 [binutils-gdb] Support single step by arch or target sergiodj+buildbot
2015-09-15 17:41 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-09-15 10:25 [binutils-gdb] aarch64 multi-arch support (part 2): siginfo fixup sergiodj+buildbot
2015-09-15 13:39 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-09-15  9:41 [binutils-gdb] Fix the SH behavior for EF_SH_PIC flag in FDPIC ABI sergiodj+buildbot
2015-09-15 10:15 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-09-14 15:40 [binutils-gdb] Bail out of processing stop if hook-stop resumes target / changes context sergiodj+buildbot
2015-09-15  9:38 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-09-14 14:39 [binutils-gdb] Remove duplicate gdb/NEWS entry sergiodj+buildbot
2015-09-14 19:29 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-09-12 17:42 [binutils-gdb] Set .plt entry size to 0 in elf32-hppa.c sergiodj+buildbot
2015-09-14 11:10 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-09-11 19:53 [binutils-gdb] Extended-remote exec documentation sergiodj+buildbot
2015-09-12 17:35 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-09-11 18:47 [binutils-gdb] Extended-remote exec test sergiodj+buildbot
2015-09-12 17:28 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-09-11 18:42 [binutils-gdb] Extended-remote catch exec sergiodj+buildbot
2015-09-12 17:18 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-09-11 16:41 [binutils-gdb] [AArch64] Cleanup comments in instruction decoding functions sergiodj+buildbot
2015-09-11 23:01 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-09-11 14:43 [binutils-gdb] gdb/18947: [aarch64]Step into shared library is very slow sergiodj+buildbot
2015-09-11 17:58 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-09-10 15:59 [binutils-gdb] Small refactor in ada-lang.c:scan_discrim_bound sergiodj+buildbot
2015-09-11 15:41 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-09-10 13:53 [binutils-gdb] S/390: Fix instruction format of crj*, clrj*, and clgrj* sergiodj+buildbot
2015-09-11 14:35 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-09-10 13:38 [binutils-gdb] S/390: Fix MASK_RIE_R0PI and MASK_RIE_R0PU sergiodj+buildbot
2015-09-11 14:30 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-09-10 11:45 [binutils-gdb] Call target_can_download_tracepoint if there are tracepoints to download sergiodj+buildbot
2015-09-11  6:19 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-09-09 19:44 [binutils-gdb] Garbage collect thread continuations sergiodj+buildbot
2015-09-10 15:03 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-09-09 18:53 [binutils-gdb] * gdb.python/py-prettyprint.exp: Check result of run_lang_tests sergiodj+buildbot
2015-09-11  1:41 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-09-09 18:32 [binutils-gdb] * gdb.base/savedregs.exp: Fix typo sergiodj+buildbot
2015-09-10 20:16 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-09-09 18:25 [binutils-gdb] Delete enum inferior_event_handler::INF_TIMER sergiodj+buildbot
2015-09-10 17:56 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-09-09 18:10 [binutils-gdb] Garbage collect dummy_frame_ctx_saver sergiodj+buildbot
2015-09-10 12:59 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-09-09 18:03 [binutils-gdb] Convert the until/advance commands to thread_fsm mechanism sergiodj+buildbot
2015-09-10 11:01 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-09-09 17:56 [binutils-gdb] Convert infcalls to thread_fsm mechanism sergiodj+buildbot
2015-09-10  8:09 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-09-09 17:48 [binutils-gdb] Replace "struct continuation" mechanism by something more extensible sergiodj+buildbot
2015-09-10  5:57 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-09-09 13:36 [binutils-gdb] [AArch64] Sort IS_AARCH64_TLS_RELAX_RELOC in alphabetic order sergiodj+buildbot
2015-09-09 21:38 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-09-09 12:30 [binutils-gdb] S/390: Remove trailing zeros on 4-bytes opcodes sergiodj+buildbot
2015-09-09 16:01 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-09-09 12:23 [binutils-gdb] S/390: Fix opcode of ppno sergiodj+buildbot
2015-09-09 13:56 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-09-09  2:59 [binutils-gdb] Improve hand-call-in-threads.exp failure handling sergiodj+buildbot
2015-09-09  5:11 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-09-04 16:27 [binutils-gdb] gdb/tui: Remove casts of NULL during assignment sergiodj+buildbot
2015-09-05  0:45 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-09-04 16:19 [binutils-gdb] gdb/cli: Remove casts of NULL during assignment sergiodj+buildbot
2015-09-04 22:17 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-09-04 16:05 [binutils-gdb] gdb: Remove casts of NULL during assignment sergiodj+buildbot
2015-09-04 19:43 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-09-04 14:38 [binutils-gdb] Mention multi-arch debugging support in NEWS sergiodj+buildbot
2015-09-04 16:22 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-09-03 16:02 [binutils-gdb] [Ada] Make string_char_type a true TYPE_CODE_CHAR type in Ada sergiodj+buildbot
2015-09-03 18:27 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-09-03 13:32 [binutils-gdb] [aarch64] Check region OK for HW watchpoint in GDBserver sergiodj+buildbot
2015-09-03 15:10 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-09-03  1:11 [binutils-gdb] Update documentation of function copy_type_recursive sergiodj+buildbot
2015-09-03  4:55 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-09-02 12:24 [binutils-gdb] Rename R_386_irelative to R_386_ext2 sergiodj+buildbot
2015-09-02 13:23 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-09-02  5:54 [binutils-gdb] Initialize yet another variable to silence GCC warning from last-but-one commit sergiodj+buildbot
2015-09-02  9:37 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-09-02  4:42 [binutils-gdb] Initialize variable and silence GCC warning from last commit sergiodj+buildbot
2015-09-02  7:42 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-09-02  4:28 [binutils-gdb] Catching errors on probes-based dynamic linker interface sergiodj+buildbot
2015-09-02  6:57 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-09-01 13:04 [binutils-gdb] [Ada] Fix completion for multiple function matches sergiodj+buildbot
2015-09-01 17:00 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-09-01 12:28 [binutils-gdb] Skip PLT for function pointer initialization sergiodj+buildbot
2015-09-01 14:33 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-31 13:54 [binutils-gdb] Optimise PowerPC64 r2 adjusting stubs sergiodj+buildbot
2015-08-31 21:10 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-31 13:47 [binutils-gdb] ppc64 section group handling sergiodj+buildbot
2015-08-31 18:59 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-31 11:07 [binutils-gdb] gdb/tui: Make local variable const sergiodj+buildbot
2015-08-31 17:14 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-27 17:52 [binutils-gdb] Fix assertion failure in linux-thread-db sergiodj+buildbot
2015-08-29 18:54 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-27 17:43 [binutils-gdb] Report UNRESOLVED on failures while detecting Cell/B.E sergiodj+buildbot
2015-08-29 16:42 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-27 12:35 [binutils-gdb] Import the "signal-h" module from gnulib sergiodj+buildbot
2015-08-28 23:09 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-27  1:02 [binutils-gdb] Unset attach_flag when running a new process sergiodj+buildbot
2015-08-28 11:49 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-26 21:30 [binutils-gdb] Replace some xmalloc-family functions with XNEW-family ones sergiodj+buildbot
2015-08-28  7:21 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-26 21:28 [binutils-gdb] Fix native follow-exec-mode "new" sergiodj+buildbot
2015-08-28  6:23 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-26 21:20 [binutils-gdb] New test for follow-exec-mode sergiodj+buildbot
2015-08-28  3:57 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-26 17:07 [binutils-gdb] gdb: Add Markus Metzger as btrace maintainer sergiodj+buildbot
2015-08-28  1:55 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-26 13:53 [binutils-gdb] Select MIPS ABi based upon abiflags rather than e_flags sergiodj+buildbot
2015-08-27 21:34 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-25 17:18 [binutils-gdb] Replace assertions with warning messages about ELF binaries containing multiple symbol tables sergiodj+buildbot
2015-08-27 19:24 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-25 13:03 [binutils-gdb] Use debug_printf in debug_reg_change_callback sergiodj+buildbot
2015-08-26  6:35 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-25 12:13 [binutils-gdb] Move aarch64_linux_prepare_to_resume to nat/aarch64-linux.c sergiodj+buildbot
2015-08-26 21:07 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-25 12:05 [binutils-gdb] Make aarch64_linux_prepare_to_resume the same on GDB and GDBserver sergiodj+buildbot
2015-08-26 18:33 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-25 11:05 [binutils-gdb] Remove some comments in debug_reg_change_callback sergiodj+buildbot
2015-08-25 22:16 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-24 19:25 [binutils-gdb] gdbserver crashes when multiprocess extensions aren't supported sergiodj+buildbot
2015-08-25 15:27 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-24 15:27 [binutils-gdb] gdb/testsuite/: garbage collect a few references to dead targets sergiodj+buildbot
2015-08-24 22:29 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-24 14:55 [binutils-gdb] Delete the remaining ROM monitor targets sergiodj+buildbot
2015-08-24 20:02 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-24 10:41 [binutils-gdb] Missing parts of fixes for in-tree libiconv sergiodj+buildbot
2015-08-24 12:28 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-23 14:03 [binutils-gdb] Reorder enum output_type for better code generation sergiodj+buildbot
2015-08-23 15:14 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-23 18:23 ` sergiodj+buildbot
     [not found] <99b0bb12cdb22489b403df6afe992b81bebbd9ec@gdb-build>
2015-08-22 18:18 ` sergiodj+buildbot
     [not found] <f8904751117dc8d4d04e5c5286b71b854e6ebba5@gdb-build>
2015-08-22 16:35 ` sergiodj+buildbot
     [not found] <049412e38f9ac04654940173db63a37ebca9bfc3@gdb-build>
2015-08-22 15:22 ` sergiodj+buildbot
2015-08-22  7:09 [binutils-gdb] Uninitialized vd_nodename sergiodj+buildbot
2015-08-22 20:02 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-21 20:38 [binutils-gdb] tui: don't overwrite a secondary prompt that was given no input sergiodj+buildbot
2015-08-22 13:38 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-21 20:30 [binutils-gdb] Use tui_putc to output newline entered by the user sergiodj+buildbot
2015-08-22 11:54 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-21 19:24 [binutils-gdb] Fix gdbserver crash exposed by gdb.threads/process-dies-while-handling-bp.exp sergiodj+buildbot
2015-08-22 10:06 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-21 18:54 [binutils-gdb] gdbserver: don't pick a random thread if the current thread dies sergiodj+buildbot
2015-08-22  8:55 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-21 17:27 [binutils-gdb] Make remote file transfers interruptible sergiodj+buildbot
2015-08-22  3:01 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-21 17:09 [binutils-gdb] Warn when accessing binaries from remote targets sergiodj+buildbot
2015-08-22  2:04 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-21 16:06 [binutils-gdb] Fix stale cleanup left by linux_mntns_access_fs sergiodj+buildbot
2015-08-21 20:31 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-21 12:48 [binutils-gdb] xtensa: implement NPTL helpers sergiodj+buildbot
2015-08-21 18:45 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-21 11:57 [binutils-gdb] PR binutils/18257: Properly decode x86/Intel mask instructions sergiodj+buildbot
2015-08-21 16:45 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-21  9:41 [binutils-gdb] Add readahead cache to gdb's vFile:pread sergiodj+buildbot
2015-08-21 13:11 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-21  8:24 [binutils-gdb] procfs.c: Include "filestuff.h" sergiodj+buildbot
2015-08-21  9:35 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-21  3:18 [binutils-gdb] Remove fields curch and cur_line from TUI_CMD_WIN sergiodj+buildbot
2015-08-21  4:31 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-20 19:30 [binutils-gdb] Fix gdb.server/solib-list.exp native-extended-gdbserver regression sergiodj+buildbot
2015-08-20 20:47 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-20 17:48 [binutils-gdb] remote non-stop: Process initially stopped threads before other commands sergiodj+buildbot
2015-08-20 19:04 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-20 11:45 [binutils-gdb] Fix language of compilation unit with unknown file extension sergiodj+buildbot
2015-08-20 14:31 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-20  8:24 [binutils-gdb] [Ada] Fix parsing for expressions with attributes and characters sergiodj+buildbot
2015-08-20 12:37 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-19 19:00 [binutils-gdb] dwarf2read.c: Check type of string valued attributes prior to decoding sergiodj+buildbot
2015-08-20 10:40 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-19 17:46 [binutils-gdb] [AArch64][4/6] LD support TLSLD move/add relocation types sergiodj+buildbot
2015-08-19 23:30 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-19 17:17 [binutils-gdb] [AArch64][3/6] GAS support TLSLD move/add relocation types sergiodj+buildbot
2015-08-19 21:41 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-19 16:50 [binutils-gdb] [AArch64][6/6] LD support TLSLD load/store relocation types sergiodj+buildbot
2015-08-20  8:57 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-19 16:42 [binutils-gdb] [AArch64][5/6] GAS support TLSLD load/store relocation types sergiodj+buildbot
2015-08-20  0:53 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-19 16:18 [binutils-gdb] [AArch64][2/6] LD support BFD_RELOC_AARCH64_TLSLD_ADD_DTPREL_LO12_NC sergiodj+buildbot
2015-08-19 20:30 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-19 16:10 [binutils-gdb] [AArch64][1/6] GAS support BFD_RELOC_AARCH64_TLSLD_ADD_DTPREL_LO12_NC sergiodj+buildbot
2015-08-19 18:28 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-19 13:10 [binutils-gdb] Prelimit number of bytes to read in "vFile:pread:" sergiodj+buildbot
2015-08-19 14:20 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-19  4:02 [binutils-gdb] Remove link_info.pic sergiodj+buildbot
2015-08-19  9:09 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-19  3:57 [binutils-gdb] Add bfd_link_pde, and simplify some tests of link_info.type sergiodj+buildbot
2015-08-19  7:16 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-18 22:51 [binutils-gdb] gdbserver/linux-aarch32-low: build failure when NT_ARM_VFP not defined sergiodj+buildbot
2015-08-19  5:32 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-18 21:13 [binutils-gdb] PR mi/18833 gdb.execute ("set param value", to_string=True) will crash gdb if using MI sergiodj+buildbot
2015-08-19  3:07 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-18 17:42 [binutils-gdb] Fix mis-parsing of hex register numbers in 'T' stop replies sergiodj+buildbot
2015-08-18 23:46 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-18 17:09 [binutils-gdb] Return reloc_class_ifunc for reloc against IFUNC sergiodj+buildbot
2015-08-18 22:19 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-18 16:03 [binutils-gdb] [AArch64] Cleanup TLS relocation types which don't go through GOT table sergiodj+buildbot
2015-08-18 20:52 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-18 13:56 [binutils-gdb] gdb: New maintenance command to disable bfd sharing sergiodj+buildbot
2015-08-18 16:32 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-18 13:28 [binutils-gdb] gdb: Add debug tracing for bfd cache activity sergiodj+buildbot
2015-08-18 18:01 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-18 13:12 [binutils-gdb] gdb: Improve cache matching criteria for the bfd cache sergiodj+buildbot
2015-08-18 15:03 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-18 13:03 [binutils-gdb] Add output_type to bfd_link_info sergiodj+buildbot
2015-08-18 13:42 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-18 10:19 [binutils-gdb] x86/Linux: disable all-stop on top of non-stop sergiodj+buildbot
2015-08-18 10:55 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-18  8:05 [binutils-gdb] Use $SED in bfd Makefile sergiodj+buildbot
2015-08-18  9:33 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-18  7:34 [binutils-gdb] PPC64: Allow .TOC. in linker script to override backend calculated value sergiodj+buildbot
2015-08-18  8:21 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-17 20:18 [binutils-gdb] ui-out.c (default_ui_out_impl): Add comment sergiodj+buildbot
2015-08-17 22:34 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-17 20:03 [binutils-gdb] [D] Implement looking up members of D enums sergiodj+buildbot
2015-08-17 21:20 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-17 19:21 [binutils-gdb] Move strace -m/explicit location test to strace.exp sergiodj+buildbot
2015-08-17 20:07 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-17  2:48 [binutils-gdb] Trailing space in opcodes/ generated files sergiodj+buildbot
2015-08-17 11:50 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-16 23:49 [binutils-gdb] psymtab.c (add_psymbol_to_bcache): Remove "val" arg sergiodj+buildbot
2015-08-17  9:55 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-16  0:29 [binutils-gdb] Add end_psymtab_common, have all debug info readers call it sergiodj+buildbot
2015-08-17  8:43 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-15 23:57 [binutils-gdb] Use macros for some enum bit field sizes sergiodj+buildbot
2015-08-17  5:09 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-15 23:05 [binutils-gdb] objfiles.h,psympriv.h,psymtab.c: Whitespace sergiodj+buildbot
2015-08-17  4:31 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-15 18:05 [binutils-gdb] Fix invoking "[kill|detach] inferiors" on inferiors that are not running sergiodj+buildbot
2015-08-16 15:46 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-15  6:44 [binutils-gdb] perftest/utils.py (select_file): Kill any existing inferior before selecting a new file sergiodj+buildbot
2015-08-16 13:12 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-15  4:59 [binutils-gdb] New /s modifier for the disassemble command sergiodj+buildbot
2015-08-15 23:12 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-15  0:47 [binutils-gdb] Rename `typename' in d-exp.y to avoid C++ reserved word sergiodj+buildbot
2015-08-15 21:58 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-14 22:33 [binutils-gdb] Rename location accessor macro parameters to silence ARI sergiodj+buildbot
2015-08-15 20:48 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-14 21:57 [binutils-gdb] mi_make_breakpoint: add "evaluated-by" option sergiodj+buildbot
2015-08-15 19:37 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-14 20:00 [binutils-gdb] Fix ARI warnings in d-exp.y sergiodj+buildbot
2015-08-15 18:24 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-14 14:27 [binutils-gdb] Add support for DT_MIPS_RLD_MAP_REL sergiodj+buildbot
2015-08-15 17:07 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-14 12:24 [binutils-gdb] Add myself to gdb MAINTAINERS sergiodj+buildbot
2015-08-15 12:10 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-14  1:48 [binutils-gdb] Revert "Fix encoding or OpenRisk1000 PC relative relocations." sergiodj+buildbot
2015-08-15  1:29 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-13 21:02 [binutils-gdb] [D] Move classification of symbols from the grammar to the lexer sergiodj+buildbot
2015-08-15  0:39 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-13 20:36 [binutils-gdb] [D] Support looking up symbols in the current and imported modules sergiodj+buildbot
2015-08-14 23:07 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-13 18:46 [binutils-gdb] gdb.base/dso2dso.exp: Improve testcase documentation sergiodj+buildbot
2015-08-14 10:00 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-13 18:17 [binutils-gdb] Fix Python frame unwinder issue caught by Valgrind sergiodj+buildbot
2015-08-13 23:17 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-13 17:22 [binutils-gdb] Mass rename `explicit' -> `explicit_loc' sergiodj+buildbot
2015-08-13 22:05 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-13 11:55 [binutils-gdb] Issue an error for read-only segment with dynamic IFUNC relocations sergiodj+buildbot
2015-08-13 20:53 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-13 10:53 [binutils-gdb] Fixes for unpredictable nops and 26-bit versions of teq, tst, cmn, cmp sergiodj+buildbot
2015-08-13 19:41 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-13  7:47 [binutils-gdb] [Ada] Add support for subprogram renamings sergiodj+buildbot
2015-08-13 18:17 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-13  2:02 [binutils-gdb] gdb.base/dso2dso.exp sometimes broken sergiodj+buildbot
2015-08-13 16:57 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-12 21:03 [binutils-gdb] Set EI_OSABI to ELFOSABI_GNU for local IFUNC symbols sergiodj+buildbot
2015-08-13 15:31 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-12 20:32 [binutils-gdb] [amd64] Invalid return address after displaced stepping sergiodj+buildbot
2015-08-13 14:19 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-12 18:48 [binutils-gdb] Initialize `location' in gdbpy_decode_line sergiodj+buildbot
2015-08-13 13:07 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-12 16:46 [binutils-gdb] Guarantee save-and-restore of GDBFLAGS on gdb.base/checkpoint-ns.exp sergiodj+buildbot
2015-08-13 12:08 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-12 16:23 [binutils-gdb] [MIPS] Map 'move' to 'or' sergiodj+buildbot
2015-08-13 11:28 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-12 15:57 [binutils-gdb] Use save_vars to replace existing manipulation of globals in tests sergiodj+buildbot
2015-08-13 10:48 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-12 13:24 [binutils-gdb] Introduce save_vars, a testsuite proc for safely manipulating globals sergiodj+buildbot
2015-08-13 10:04 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-12 12:58 [binutils-gdb] Sync ansidecl.h with GCC sergiodj+buildbot
2015-08-13  9:20 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-12 12:26 [binutils-gdb] Remove trailing spaces in opcodes sergiodj+buildbot
2015-08-13  8:10 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-12 11:58 [binutils-gdb] Remove trailing spaces in bfd sergiodj+buildbot
2015-08-13  7:27 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-12  8:50 [binutils-gdb] [regression] Do not read from catchpoint/watchpoint locations' addresses when checking for a permanent breakpoint sergiodj+buildbot
2015-08-12 22:53 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-12  5:48 [binutils-gdb] Properly skip IFUNC relocations in debug sections sergiodj+buildbot
2015-08-12 22:08 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-12  5:23 [binutils-gdb] Explicit locations: documentation updates sergiodj+buildbot
2015-08-12 21:24 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-12  4:59 [binutils-gdb] Explicit locations: MI support for explicit locations sergiodj+buildbot
2015-08-12 20:41 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-12  4:30 [binutils-gdb] Explicit locations: add UI features for CLI sergiodj+buildbot
2015-08-12 20:01 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-12  4:04 [binutils-gdb] Explicit locations: introduce explicit locations sergiodj+buildbot
2015-08-12 19:19 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-12  3:38 [binutils-gdb] Explicit locations: introduce probe locations sergiodj+buildbot
2015-08-12 18:33 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-12  3:12 [binutils-gdb] Explicit locations: introduce address locations sergiodj+buildbot
2015-08-12 17:49 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-12  2:47 [binutils-gdb] Explicit locations: use new location API sergiodj+buildbot
2015-08-12 17:07 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-12  2:19 [binutils-gdb] Explicit locations: introduce new struct event_location-based API sergiodj+buildbot
2015-08-12 16:12 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-12  1:53 [binutils-gdb] Explicit locations: rename "address string"/"addr_string" to "location" sergiodj+buildbot
2015-08-12 14:55 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-12  1:26 [binutils-gdb] [AArch64] Improve BFD overflow warning message for -fpic sergiodj+buildbot
2015-08-12 13:35 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-12  1:03 [binutils-gdb] [AArch64]Speed up linking speed by skipping unncessary TLS reloc type check sergiodj+buildbot
2015-08-12 12:24 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-12  0:36 [binutils-gdb] [AArch64] Long branch veneer support far symbol defined by --defsym sergiodj+buildbot
2015-08-12 11:05 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-12  0:11 [binutils-gdb] [AArch64] PR18668, repair long branch veneer for plt stub sergiodj+buildbot
2015-08-12  9:40 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-11 23:44 [binutils-gdb] [AArch64][8/8] LD support BFD_RELOC_AARCH64_TLSLD_ADD_DTPREL_LO12 sergiodj+buildbot
2015-08-12  8:22 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-11 23:19 [binutils-gdb] [AArch64][7/8] GAS support BFD_RELOC_AARCH64_TLSLD_ADD_DTPREL_LO12 sergiodj+buildbot
2015-08-12  7:12 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-11 22:57 [binutils-gdb] [AArch64][6/8] LD support BFD_RELOC_AARCH64_TLSLD_ADD_LO12_NC sergiodj+buildbot
2015-08-12  6:02 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-11 22:27 [binutils-gdb] [AArch64][5/8] GAS support BFD_RELOC_AARCH64_TLSLD_ADD_LO12_NC sergiodj+buildbot
2015-08-12  4:53 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-11 22:07 [binutils-gdb] [AArch64][4/8] Add R_AARCH64_P32_TLSLD_ADD_LO12_NC in elf header sergiodj+buildbot
2015-08-12  3:40 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-11 21:42 [binutils-gdb] [AArch64][3/8] LD support BFD_RELOC_AARCH64_TLSLD_ADR_PAGE21 sergiodj+buildbot
2015-08-12  2:26 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-11 21:17 [binutils-gdb] [AArch64][2/8] GAS support BFD_RELOC_AARCH64_TLSLD_ADR_PAGE21 sergiodj+buildbot
2015-08-11 23:50 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-11 20:42 [binutils-gdb] [AArch64][1/8] Add R_AARCH64_P32_TLSLD_ADR_PAGE21 in elf header sergiodj+buildbot
2015-08-11 22:15 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-11 20:12 [binutils-gdb] Skip IFUNC relocations in debug sections sergiodj+buildbot
2015-08-11 21:02 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-11 17:19 [binutils-gdb] Fix the disassembly of the AArch64 SIMD EXT instruction sergiodj+buildbot
2015-08-11 19:39 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-11 16:46 [binutils-gdb] Fix encoding or OpenRisk1000 PC relative relocations sergiodj+buildbot
2015-08-11 18:26 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-11 16:13 [binutils-gdb] Fix typo in coff-sh.c sergiodj+buildbot
2015-08-11 17:12 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-11 11:35 [binutils-gdb] Fix memory access problems discovered when running some binary tools on corrupt files sergiodj+buildbot
2015-08-11 12:55 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-11 11:05 [binutils-gdb] Fix a typo in _bfd_elf_copy_private_bfd_data sergiodj+buildbot
2015-08-11 11:45 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-11  7:25 [binutils-gdb] PR gdb/18669 libiberty demangle.test failure: strtod() on sparc-sun-solaris2.9 sergiodj+buildbot
2015-08-11  8:05 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-10 19:25 [binutils-gdb] PR gdb/17960 Internal error: tracker != NULL when completing on file:function sergiodj+buildbot
2015-08-10 20:07 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-10 18:17 [binutils-gdb] gdb/infrun.c: Various trivial ARI fixes sergiodj+buildbot
2015-08-10 18:53 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-10 15:08 [binutils-gdb] Replace hidden with versioned in elf_link_hash_entry sergiodj+buildbot
2015-08-10 16:07 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-10  8:27 [binutils-gdb] Add SIGRIE instruction for MIPS R6 sergiodj+buildbot
2015-08-10 14:55 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-08  0:51 [binutils-gdb] Check sh_type/sh_flags/sh_addralign/sh_entsize when copying sh_link/sh_info sergiodj+buildbot
2015-08-10 12:33 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-08  0:24 [binutils-gdb] native Linux: enable always non-stop by default sergiodj+buildbot
2015-08-10  9:51 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-07 23:57 [binutils-gdb] S/390: displaced stepping and PC-relative RIL-b/RIL-c instructions sergiodj+buildbot
2015-08-09 23:17 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-07 23:36 [binutils-gdb] PPC64: Fix gdb.arch/ppc64-atomic-inst.exp with displaced stepping sergiodj+buildbot
2015-08-09 22:02 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-07 23:02 [binutils-gdb] Disable displaced stepping if trying it fails sergiodj+buildbot
2015-08-09 20:51 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-07 22:44 [binutils-gdb] Fix step-over-{trips-on-watchpoint|lands-on-breakpoint}.exp race sergiodj+buildbot
2015-08-09 19:40 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-07 22:08 [binutils-gdb] Fix interrupt-noterm.exp on targets always in non-stop sergiodj+buildbot
2015-08-09 18:30 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-07 21:49 [binutils-gdb] Fix signal-while-stepping-over-bp-other-thread.exp on targets always in non-stop sergiodj+buildbot
2015-08-09 17:20 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-07 21:15 [binutils-gdb] Implement all-stop on top of a target running non-stop mode sergiodj+buildbot
2015-08-09 16:05 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-07 21:07 [binutils-gdb] Teach non-stop to do in-line step-overs (stop all, step, restart) sergiodj+buildbot
2015-08-09 14:55 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-07 20:23 [binutils-gdb] Factor out code to re-resume stepped thread sergiodj+buildbot
2015-08-09 13:34 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-07 19:58 [binutils-gdb] Add comments to currently_stepping and target_resume sergiodj+buildbot
2015-08-09 12:23 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-07 19:35 [binutils-gdb] Misc switch_back_to_stepped_thread cleanups sergiodj+buildbot
2015-08-09 11:13 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-07 19:05 [binutils-gdb] Use keep_going in proceed and start_step_over too sergiodj+buildbot
2015-08-09  9:58 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-07 18:40 [binutils-gdb] Embed the pending step-over chain in thread_info objects sergiodj+buildbot
2015-08-09  5:11 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
     [not found] <33ebda9d6841e18d9ef18b94c3dcad7d0498ab3d@gdb-build>
2015-08-07 18:37 ` sergiodj+buildbot
2015-08-07 18:22 [binutils-gdb] Make thread_still_needs_step_over consider stepping_over_watchpoint too sergiodj+buildbot
2015-08-08 23:10 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-07 17:47 [binutils-gdb] remote.c/all-stop: Implement TARGET_WAITKIND_NO_RESUMED and TARGET_WNOHANG sergiodj+buildbot
2015-08-08 21:56 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-07 17:20 [binutils-gdb] Change adjust_pc_after_break's prototype sergiodj+buildbot
2015-08-08 20:47 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-07 16:54 [binutils-gdb] Fix and test "checkpoint" in non-stop mode sergiodj+buildbot
2015-08-08 19:38 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-07 15:44 [binutils-gdb] ignore invalid DOF provider sections sergiodj+buildbot
2015-08-08 18:27 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-07 15:10 [binutils-gdb] Sync config.sub and config.guess with GCC sergiodj+buildbot
2015-08-08 17:16 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-07 14:44 [binutils-gdb] Remove CpuFMA4 support from CPU_ZNVER1_FLAGS sergiodj+buildbot
2015-08-08 16:03 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-07 12:17 [binutils-gdb] Properly merge hidden versioned symbol sergiodj+buildbot
2015-08-08 14:45 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-07 11:34 [binutils-gdb] gdb: Move get_frame_language from stack.c to frame.c sergiodj+buildbot
2015-08-08 12:58 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-07 11:12 [binutils-gdb] gdb: get_frame_language now takes a frame parameter sergiodj+buildbot
2015-08-08 11:26 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-07  8:58 [binutils-gdb] btrace: indicate speculative execution sergiodj+buildbot
2015-08-08  9:38 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-07  8:34 [binutils-gdb] configure: check for perf_event.h version sergiodj+buildbot
2015-08-08  4:19 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-07  5:32 [binutils-gdb] Yaakov Selkowitz: fixes for in-tree libiconv sergiodj+buildbot
2015-08-07 23:22 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-06 23:28 [binutils-gdb] Bump timeouts for a couple gdb.reverse/*-precsave.exp tests sergiodj+buildbot
2015-08-07 22:09 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-06 22:52 [binutils-gdb] Fix gdb.base/valgrind-infcall.exp with the native-extended-gdbserver board sergiodj+buildbot
2015-08-07 20:58 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-06 21:34 [binutils-gdb] Add casts for legitimate integer to enum conversions sergiodj+buildbot
2015-08-07 19:47 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-06 18:16 [binutils-gdb] gdbserver: no point in hiding the regcache type nowadays sergiodj+buildbot
2015-08-07 17:23 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-06 17:22 [binutils-gdb] PR python/17136 sergiodj+buildbot
2015-08-07 14:52 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-06 16:55 [binutils-gdb] gdbserver: fix silent error exit sergiodj+buildbot
2015-08-07 13:43 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-06 16:28 [binutils-gdb] Change type of struct complaints::series sergiodj+buildbot
2015-08-07 12:10 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-06 15:39 [binutils-gdb] gdbserver: move_out_of_jump_pad_callback misses switching current thread sergiodj+buildbot
2015-08-07 10:05 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-06 15:14 [binutils-gdb] Fix gdbserver --debug issues caught by Valgrind sergiodj+buildbot
2015-08-07  9:15 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-06 14:26 [binutils-gdb] Revert "test slowdown" sergiodj+buildbot
2015-08-07  5:44 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-06 10:08 [binutils-gdb] Linux gdbserver confused when event randomization picks process exit event sergiodj+buildbot
2015-08-06 13:21 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-05 19:19 [binutils-gdb] stepping is disturbed by setjmp/longjmp | try/catch in other threads sergiodj+buildbot
2015-08-05 21:14 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-05 15:27 [binutils-gdb] Change the behaviour of the --only-keep-debug option to objcopy and strip so that the sh_link and sh_info fields in stripped section headers are preserved sergiodj+buildbot
2015-08-05 19:10 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-05 14:43 [binutils-gdb] Protect nat/gdb_thread_db.h against multiple inclusion sergiodj+buildbot
2015-08-05 17:39 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-04 13:49 [binutils-gdb] Move have_ptrace_getregset to linux-low.c sergiodj+buildbot
2015-08-04 22:35 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-04 12:22 [binutils-gdb] signal_command: Leftover cleanup chain regression sergiodj+buildbot
2015-08-04 20:12 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-03 19:07 [binutils-gdb] Fix "FAIL: -Bsymbolic-functions" for cris-linux in ld sergiodj+buildbot
2015-08-04 10:46 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-08-01  9:01 [binutils-gdb] Replace the block_found global with explicit data-flow sergiodj+buildbot
2015-08-03 16:42 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-07-31 17:25 [binutils-gdb] Mostly trivial enum fixes sergiodj+buildbot
2015-08-03 11:50 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-07-30 14:49 [binutils-gdb] Don't use arm_regmap and arm_num_regs in arm_fill_gregset and arm_store_gregset sergiodj+buildbot
2015-08-02 15:32 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-07-30 14:17 [binutils-gdb] Move ARM register numbers enum to arch/arm.h sergiodj+buildbot
2015-08-02 12:25 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-07-29 16:38 [binutils-gdb] Make gdb.base/call-ar-st.exp use gdb_test_stdio sergiodj+buildbot
2015-07-31 14:20 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-07-29 15:25 [binutils-gdb] Make gdb.base/dprintf.exp use gdb_test_stdio sergiodj+buildbot
2015-07-31 10:10 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-07-29 12:46 [binutils-gdb] Don't rely on inferior I/O in gdb.base/restore.exp sergiodj+buildbot
2015-07-30 23:14 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-07-28 21:47 [binutils-gdb] Uniquify test names from gdb.python/{py-objfile.exp, py-pp-registration.exp} sergiodj+buildbot
2015-07-29 20:48 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-07-28  0:42 [binutils-gdb] Remove xfail in gdb.mi/mi-watch.exp sergiodj+buildbot
2015-07-29  8:24 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-07-27 22:28 [binutils-gdb] Factor out int printing code from generic_val_print sergiodj+buildbot
2015-07-28 18:00 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-07-27 16:55 [binutils-gdb] [gdbserver] Don't set srv_linux_usrregs for aarch64*-*-linux* sergiodj+buildbot
2015-07-27 21:45 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-07-27 15:06 [binutils-gdb] Sync config with GCC sergiodj+buildbot
2015-07-27 16:39 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-07-25  1:28 [binutils-gdb] Add gmonster-{1,2} perf testcases sergiodj+buildbot
2015-07-25 21:17 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-07-25  1:05 [binutils-gdb] Add perf testcase generator sergiodj+buildbot
2015-07-25 19:41 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-07-25  0:40 [binutils-gdb] PerfTest::assemble functions return results sergiodj+buildbot
2015-07-25 17:46 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-07-25  0:14 [binutils-gdb] lib/gdb.exp (clean_restart): Make executable optional sergiodj+buildbot
2015-07-25 16:05 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-07-24 23:49 [binutils-gdb] Clean up testsuite compiler_info support sergiodj+buildbot
2015-07-25 14:31 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-07-24 23:25 [binutils-gdb] Add parallel build support for perf tests sergiodj+buildbot
2015-07-25 12:55 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-07-24 22:54 [binutils-gdb] Workaround debian change to default value of --as-needed sergiodj+buildbot
2015-07-25 11:19 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-07-24 19:41 [binutils-gdb] Fix s390 GNU/Linux build after enum __ptrace_request changes sergiodj+buildbot
2015-07-25  5:36 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-07-24 15:48 [binutils-gdb] Set proc->priv->new_inferior out of linux_add_process sergiodj+buildbot
2015-07-24 22:33 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-07-24 15:23 [binutils-gdb] Refactor start_inferior sergiodj+buildbot
2015-07-24 20:24 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-07-24  6:05 [binutils-gdb] bfd_get_section_by_name_if hash chain traversal sergiodj+buildbot
2015-07-24  7:08 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-07-23 22:06 [binutils-gdb] Fix DT_MIPS_RLD_MAP_REL tag for n64 target and 32-bit host sergiodj+buildbot
2015-07-23 23:40 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-07-23 16:45 [binutils-gdb] Fix crash when reading dummy CUs sergiodj+buildbot
2015-07-23 18:36 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-07-23 13:59 [binutils-gdb] py-linetable.c: Fix doc of LineTable.source_lines' return type sergiodj+buildbot
2015-07-23 16:21 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-07-23 13:22 [binutils-gdb] gdb/gdbtypes: fix handling of typedef layers between array types sergiodj+buildbot
2015-07-23 14:26 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-07-23 10:40 [binutils-gdb] Return zero in aarch64_linux_can_use_hw_breakpoint if target doesn't support HW watchpoint/breakpoint sergiodj+buildbot
2015-07-23 12:27 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-07-22 10:11 [binutils-gdb] Fix ppc64 ELFv1 assertion failure sergiodj+buildbot
2015-07-22 11:46 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-07-21 15:55 [binutils-gdb] Move aarch64_linux_get_debug_reg_capacity to nat/aarch64-linux-hw-point.c sergiodj+buildbot
2015-07-21 17:07 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-07-21 12:11 [binutils-gdb] btrace: fix case label in btrace_data_append sergiodj+buildbot
2015-07-21 13:37 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-07-20 13:07 [binutils-gdb] Make binutils abort message GDB friendly sergiodj+buildbot
2015-07-20 18:06 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-07-18 17:30 [binutils-gdb] dwarf2read: Allow SEC_ALLOC sections to be located at address 0 sergiodj+buildbot
2015-07-18 18:51 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-07-17 15:21 [binutils-gdb] Move common aarch64 HW breakpoint/watchpoint code to nat/ sergiodj+buildbot
2015-07-18  0:13 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-07-17 14:57 [binutils-gdb] Pass aarch64_debug_reg_state to functions sergiodj+buildbot
2015-07-17 22:34 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-07-17 11:35 [binutils-gdb] Fix using uninitialised values sergiodj+buildbot
2015-07-17 12:37 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-07-16 15:29 [binutils-gdb] [AArch64][2/3] GAS support BFD_RELOC_AARCH64_TLSLD_ADR_PREL21 sergiodj+buildbot
2015-07-16 18:36 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-07-16 15:06 [binutils-gdb] [AArch64][1/3] Add R_AARCH64_P32_TLSLD_ADR_PREL21 in elf header sergiodj+buildbot
2015-07-16 16:47 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-07-15 15:43 [binutils-gdb] Unbreak nios2-*-linux* GDB testing sergiodj+buildbot
2015-07-15 23:24 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-07-15 14:22 [binutils-gdb] [GDBserver][AArch64] Enable support for range stepping sergiodj+buildbot
2015-07-15 21:27 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-07-15 13:43 [binutils-gdb] [testsuite] Skip gdb.trace/range-stepping.exp test case if not supported sergiodj+buildbot
2015-07-15 19:27 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-07-15  6:52 [binutils-gdb] ari, btrace: avoid unsigned long long sergiodj+buildbot
2015-07-15 18:05 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-07-14 21:08 [binutils-gdb] Remove CHECK_TYPEDEF, use check_typedef instead sergiodj+buildbot
2015-07-15 16:02 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-07-14 18:28 [binutils-gdb] Sync Makefile.tpl with GCC sergiodj+buildbot
2015-07-15 11:38 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-07-14 18:08 [binutils-gdb] Sync longlong.h with GCC sergiodj+buildbot
2015-07-15  9:49 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-07-14 17:09 [binutils-gdb] Sync ansidecl.h with GCC sergiodj+buildbot
2015-07-15  4:44 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-07-14 16:50 [binutils-gdb] Sync config files with GCC sergiodj+buildbot
2015-07-15  2:08 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-07-14 16:28 [binutils-gdb] Fix build issue with nat/linux-namespaces.c sergiodj+buildbot
2015-07-15  0:15 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-07-14 16:05 [binutils-gdb] Sync config/warnings.m4 with GCC sergiodj+buildbot
2015-07-14 22:36 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-07-14 15:13 [binutils-gdb] Sync toplevel configure.ac with GCC sergiodj+buildbot
2015-07-14 18:52 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-07-14 11:31 [binutils-gdb] Remove extraneous whitespace from ARM sim sources sergiodj+buildbot
2015-07-14 16:33 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-07-14 10:02 [binutils-gdb] gdbserver/Linux: internal error when killing a process that is already gone sergiodj+buildbot
2015-07-14 11:23 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-07-13 14:51 [binutils-gdb] gdb/tui: Add command completion to winheight command sergiodj+buildbot
2015-07-13 16:33 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-07-12 14:26 [binutils-gdb] Fix GDB breakage due to addition of new nios2 mach types in BFD sergiodj+buildbot
2015-07-12 16:02 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-07-10 22:00 [binutils-gdb] Properly convert objects between different ELF classes sergiodj+buildbot
2015-07-11 19:46 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-07-10 20:31 [binutils-gdb] rx-tdep.c: Use target_read_code instead of target_read_memory sergiodj+buildbot
2015-07-11 18:14 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-07-10 12:39 [binutils-gdb] gdb/tui: Use cleanups to free string copies sergiodj+buildbot
2015-07-11 10:33 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-07-10 11:43 [binutils-gdb] gdb: Convert TUI windows names to lower case sergiodj+buildbot
2015-07-11  7:37 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
     [not found] <66c4b3e8a628a207bc6aafef6af0c4128195f56e@kwanyin>
2015-07-06 23:17 ` sergiodj+buildbot
     [not found] <bcd8537ce10dd72b053fa54e87525defa26f3fd0@kwanyin>
2015-07-06 21:39 ` sergiodj+buildbot
     [not found] <10e9aaa3b8554f997db993c8158493a96030d4d5@kwanyin>
2015-07-06 20:35 ` sergiodj+buildbot
     [not found] <8a13d42d99390c36d5e7884b509e6bb92ec72e3c@kwanyin>
2015-07-06 19:31 ` sergiodj+buildbot
     [not found] <a844296a982bdff7c14dab355de0fca75486add6@kwanyin>
2015-07-06 17:56 ` sergiodj+buildbot
     [not found] <118ca22445afc728069ca80be2f30dae6913059e@kwanyin>
2015-07-06 14:06 ` sergiodj+buildbot
     [not found] <0561fea48c107b271308a013c485c29cbd5c13b5@kwanyin>
2015-07-03  2:08 ` sergiodj+buildbot
     [not found] <2fd0f80d57e8437d70ba79921efd3ce02e755755@kwanyin>
2015-07-02 22:52 ` sergiodj+buildbot
     [not found] <58bfce93438e1f936d4547bb9659b7d096e2823f@kwanyin>
2015-07-02 12:20 ` sergiodj+buildbot
     [not found] <b0fd6b3037669534962b1ffe860db178ea7e1239@kwanyin>
2015-07-02  8:19 ` sergiodj+buildbot
     [not found] <bbcbf914a6ad801bfa7d4e56150217a1d53e07af@kwanyin>
2015-07-01 17:45 ` sergiodj+buildbot
     [not found] <0986c744dfecb8177de90020646090e9ed23cfe7@kwanyin>
2015-07-01  5:16 ` sergiodj+buildbot
     [not found] <b5fca6d7284b2cd2e90efc556eb6a29a1b177476@kwanyin>
2015-07-01  4:04 ` sergiodj+buildbot
     [not found] <c45613e33dbdc646b6fd7f02f86635639e852bfb@kwanyin>
2015-07-01  2:05 ` sergiodj+buildbot
     [not found] <d0bf44cb88be21ea009a4fe0e59a3d3e6e545aed@kwanyin>
2015-06-30 23:46 ` sergiodj+buildbot
2015-06-29 10:40 [binutils-gdb] [GDBServer][AArch64] Enable support for Z0 packets sergiodj+buildbot
2015-06-29 14:21 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-06-29 10:17 [binutils-gdb] [GDBServer][AArch64] Use the same break instruction as GDB sergiodj+buildbot
2015-06-29 12:31 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-06-29  9:46 [binutils-gdb] Update my email address sergiodj+buildbot
2015-06-29 10:58 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-06-26 19:05 [binutils-gdb] PR 16253 revisited sergiodj+buildbot
2015-06-26 20:26 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-06-26 15:18 [binutils-gdb] Add option to remove duplicate command history entries sergiodj+buildbot
2015-06-26 19:05 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-06-26 14:37 [binutils-gdb] Add tab completion for TUI's "focus" command sergiodj+buildbot
2015-06-26 17:09 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-06-26 13:34 [binutils-gdb] Do not skip prologue for asm (.S) files sergiodj+buildbot
2015-06-26 15:34 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-06-26 13:00 [binutils-gdb] Add support for DT_MIPS_RLD_MAP_REL sergiodj+buildbot
2015-06-26 14:00 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-06-25 20:28 [binutils-gdb] Don't set sh_size for .shstrtab twice sergiodj+buildbot
2015-06-25 23:50 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-06-25 17:56 [binutils-gdb] py-prettyprint.exp: Add is_address_zero_readable check sergiodj+buildbot
2015-06-25 21:32 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-06-25 10:52 [binutils-gdb] Correctly notice empty sysroots in solib_find_1 sergiodj+buildbot
2015-06-25 18:09 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-06-24 21:35 [binutils-gdb] Fix lrealpath memory leak in build_id_to_debug_bfd sergiodj+buildbot
2015-06-25 12:59 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-06-24 20:10 [binutils-gdb] Sync libiberty from GCC, replaying updates to configure scripts sergiodj+buildbot
2015-06-25  9:40 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-06-24 17:33 [binutils-gdb] sim: trace: drop unused trace_one_insn sergiodj+buildbot
2015-06-25  6:14 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-06-24 15:10 [binutils-gdb] gdb: sim: handle target sysroot prefix sergiodj+buildbot
2015-06-24 17:55 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-06-24 14:45 [binutils-gdb] Call set_gdbarch_get_siginfo_type in linux_init_abi sergiodj+buildbot
2015-06-24 16:47 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-06-23 22:31 [binutils-gdb] sim: common: replace SIM_FILTER_PATH with lbasename sergiodj+buildbot
2015-06-24  7:26 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-06-23 22:27 [binutils-gdb] Fix GDBHISTSIZE test failure on i686 sergiodj+buildbot
2015-06-24  8:02 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-06-23 20:03 [binutils-gdb] sim: trace: do not enable internal debug by default sergiodj+buildbot
2015-06-23 21:58 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-06-23 19:10 [binutils-gdb] sim: assume recentish compiler/systems sergiodj+buildbot
2015-06-23 20:28 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-06-23 14:06 [binutils-gdb] gdb: microblaze: delete useless stubs sergiodj+buildbot
2015-06-23 16:27 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-06-23 13:26 [binutils-gdb] Convert have_ptrace_getregset to a tri-state boolean sergiodj+buildbot
2015-06-23 14:40 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-06-23 11:38 [binutils-gdb] [AArch64] Generate DT_TEXTREL for relocation against read-only section sergiodj+buildbot
2015-06-23 13:23 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-06-22 16:34 [binutils-gdb] Stop "objdump -d" from disassembling past a symbolic address sergiodj+buildbot
2015-06-22 17:50 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-06-22 13:09 [binutils-gdb] Don't skip hw breakpoint/watchpoint tests for aarch64 target sergiodj+buildbot
2015-06-22 14:14 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-06-21 18:58 [binutils-gdb] sim: common: use standard intXX_t types for signedXX sergiodj+buildbot
2015-06-21 20:37 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-06-21 17:56 [binutils-gdb] sim: common: standardize multiple include defines sergiodj+buildbot
2015-06-21 18:58 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-06-19 22:42 [binutils-gdb] Allow for optional operands with non-zero default values sergiodj+buildbot
2015-06-19 23:57 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-06-19 19:00 [binutils-gdb] Remove special support in gdb for Sun's version of stabs sergiodj+buildbot
2015-06-19 20:01 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-06-18 17:40 [binutils-gdb] remote: consider addressable unit size when reading/writing memory sergiodj+buildbot
2015-06-18 20:07 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-06-18 17:01 [binutils-gdb] Test the interaction between GDBHISTSIZE and .gdbinit sergiodj+buildbot
2015-06-18 18:33 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-06-18  9:00 [binutils-gdb] sim: syscall: simplify unknown syscall trace sergiodj+buildbot
2015-06-18 14:35 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-06-17 21:32 [binutils-gdb] Tweak the handling of $GDBHISTSIZE edge cases [PR gdb/16999] sergiodj+buildbot
2015-06-18  8:17 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-06-17 20:35 [binutils-gdb] Read $GDBHISTSIZE instead of $HISTSIZE sergiodj+buildbot
2015-06-18  6:18 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-06-17 20:32 [binutils-gdb] Remove unused function make_breakpoint_permanent sergiodj+buildbot
2015-06-18  9:48 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-06-17 18:39 [binutils-gdb] sim: syscall: unify memory helpers sergiodj+buildbot
2015-06-17 21:31 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-06-17 17:40 [binutils-gdb] sim: callback: add human readable strings for debugging to maps sergiodj+buildbot
2015-06-17 19:46 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-06-17 14:12 [binutils-gdb] Don't truncate the history file when history size is unlimited sergiodj+buildbot
2015-06-17 14:39 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-06-17 10:18 [binutils-gdb] S390: Add syscall info for syscalls from 344 up to 354 sergiodj+buildbot
2015-06-17 12:54 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-06-17  9:39 [binutils-gdb] Add vector ABI tests to gnu_vector.exp sergiodj+buildbot
2015-06-17 10:38 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-06-16 16:49 [binutils-gdb] GDB Namespaces - Define MSG_CMSG_CLOEXEC if not defined sergiodj+buildbot
2015-06-16 21:15 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-06-16 13:55 [binutils-gdb] Fix build when size_t is not available in bfd-in2.h sergiodj+buildbot
2015-06-16 16:06 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-06-16 12:56 [binutils-gdb] Fixes a compile time warnng about left shifting a negative value sergiodj+buildbot
2015-06-16 13:55 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-06-15 20:11 [binutils-gdb] MI: consider addressable unit size when reading/writing memory sergiodj+buildbot
2015-06-16  1:21 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-06-15 18:19 [binutils-gdb] Cleanup write_memory doc sergiodj+buildbot
2015-06-15 23:47 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-06-15 16:18 [binutils-gdb] Merge multiple hex conversions sergiodj+buildbot
2015-06-15 20:10 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-06-15 15:24 [binutils-gdb] Move utility functions to common/ sergiodj+buildbot
2015-06-15 18:13 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-06-15 13:23 [binutils-gdb] Copy aarch64-linux.xml to build tree sergiodj+buildbot
2015-06-15 16:35 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-06-15 12:26 [binutils-gdb] Allow gdb to find debug symbols file by build-id for PE file format also sergiodj+buildbot
2015-06-15 15:02 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-06-15 10:31 [binutils-gdb] [AArch64] Gas add BFD_RELOC_AARCH64_LD64_GOTOFF_LO15 support sergiodj+buildbot
2015-06-15 11:37 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-06-15  7:16 [binutils-gdb] DJGPP port of binutils broken due to 64 bit cygwin fix sergiodj+buildbot
2015-06-15 10:31 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-06-12 23:15 [binutils-gdb] gdbarch: add addressable_memory_unit_size method sergiodj+buildbot
2015-06-13 20:07 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-06-12 19:37 [binutils-gdb] sim: update configure.in->configure.ac docs sergiodj+buildbot
2015-06-13 13:44 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-06-12 17:42 [binutils-gdb] sim: bfin: expand CB_SYS_xxx comment sergiodj+buildbot
2015-06-13 15:05 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-06-12 16:25 [binutils-gdb] sim: drop -DTRACE from configure sergiodj+buildbot
2015-06-13 11:06 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-06-12 10:53 [binutils-gdb] sim: moxie: rename TRACE to MOXIE_TRACE_INSN sergiodj+buildbot
2015-06-12 19:37 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-06-11 16:58 [binutils-gdb] sim: msp430: delete unused trace macros sergiodj+buildbot
2015-06-12 14:45 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-06-11 16:24 [binutils-gdb] sim: trace: centralize the system tracing sergiodj+buildbot
2015-06-12 13:12 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-06-11 16:17 [binutils-gdb] sim: trace: add STRACE_xxx_P macros sergiodj+buildbot
2015-06-12 11:18 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-06-11 16:10 [binutils-gdb] sim: trace: use existing defines for the useful mask sergiodj+buildbot
2015-06-12  9:29 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-06-11 12:42 [binutils-gdb] Use pulongest for printing ssize_t sergiodj+buildbot
2015-06-11 19:04 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-06-10 13:51 [binutils-gdb] Remove linux_proc_pid_get_ns sergiodj+buildbot
2015-06-10 18:39 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-06-10 11:49 [binutils-gdb] Add support for bound table in the Intel MPX context sergiodj+buildbot
2015-06-10 12:55 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-06-09 18:49 [binutils-gdb] Fix spelling mistakes in sim/common/sim-events.c error messages sergiodj+buildbot
2015-06-09 19:49 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-06-09 12:54 [binutils-gdb] Don't assume File-I/O mode bits match the host's format sergiodj+buildbot
2015-06-09 14:45 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-06-09  9:40 [binutils-gdb] Fix preprocessor conditional sergiodj+buildbot
2015-06-09 10:15 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-06-05 15:33 [binutils-gdb] Move vgdb special case into remote_filesystem_is_local sergiodj+buildbot
2015-06-05 16:51 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-06-05 11:06 [binutils-gdb] ppc476 linker workaround shared lib fixes sergiodj+buildbot
2015-06-05 12:12 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-06-04 20:00 [binutils-gdb] compile-print.exp: xfail->kfail for '@' GDB array operator sergiodj+buildbot
2015-06-04 23:37 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-06-04 15:54 [binutils-gdb] Fixes the check for emulated MSP430 instrucrtions that take no operands sergiodj+buildbot
2015-06-04 17:02 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-06-04 10:37 [binutils-gdb] [AArch64] Add support for ARMv8.1 command line option sergiodj+buildbot
2015-06-04 11:50 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-06-03 19:45 [binutils-gdb] compile: Use also inferior munmap sergiodj+buildbot
2015-06-03 21:21 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-06-02 19:59 [binutils-gdb] Fix =thread-exited not showing up when detaching (PR 15564) sergiodj+buildbot
2015-06-02 20:25 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-06-02 13:22 [binutils-gdb] [ARM] Support for ARMv8.1 Adv.SIMD extension sergiodj+buildbot
2015-06-02 18:55 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-06-02 12:32 [binutils-gdb] [ARM] Rework CPU feature selection in the disassembler sergiodj+buildbot
2015-06-02 16:06 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-06-02 11:35 [binutils-gdb] [AArch64] Support for ARMv8.1a Adv.SIMD instructions sergiodj+buildbot
2015-06-02 14:24 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-06-02 10:50 [binutils-gdb] [AArch64] Support for ARMv8.1a Limited Ordering Regions extension sergiodj+buildbot
2015-06-02 12:29 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-06-01 14:58 [binutils-gdb] [AArch64] BFD support BFD_RELOC_AARCH64_LD32_GOTPAGE_LO14 sergiodj+buildbot
2015-06-02  2:42 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-06-01 14:50 [binutils-gdb] [AArch64] GAS support BFD_RELOC_AARCH64_LD32_GOTPAGE_LO14 sergiodj+buildbot
2015-06-02  1:07 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-06-01 12:56 [binutils-gdb] PR symtab/18392 sergiodj+buildbot
2015-06-01 22:40 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-06-01 12:32 [binutils-gdb] Fetch and store GP registers by PTRACE_{G,S}ETREGSET sergiodj+buildbot
2015-06-01 18:12 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-06-01 12:27 [binutils-gdb] Check whether kernel supports PTRACE_GETREGSET sergiodj+buildbot
2015-06-01 17:11 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-06-01  9:59 [binutils-gdb] x86/Intel: fix i386_optab[] for vcvt{,u}si2s{d,s} sergiodj+buildbot
2015-06-01 11:20 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-06-01  9:39 [binutils-gdb] [AArch64] BFD_RELOC_AARCH64_TLSLE_ADD_LO12 should enable overflow check sergiodj+buildbot
2015-06-01  9:59 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-06-01  9:32 [binutils-gdb] [AArch64] BFD Support BFD_RELOC_AARCH64_LD64_GOTPAGE_LO15 sergiodj+buildbot
2015-06-01  9:44 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-06-01  9:26 [binutils-gdb] [AArch64] GAS Support BFD_RELOC_AARCH64_LD64_GOTPAGE_LO15 sergiodj+buildbot
2015-06-01  9:32 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-06-01  8:05 [binutils-gdb] x86/Intel: disassemble vcvt{, u}si2s{d, s} with correct operand order sergiodj+buildbot
2015-06-01  8:25 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-06-01  8:00 [binutils-gdb] x86/Intel: accept mandated operand order for vcvt{, u}si2s{d, s} sergiodj+buildbot
2015-06-01  8:05 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-05-27 20:10 [binutils-gdb] Don't ignore domain in nested lookups sergiodj+buildbot
2015-05-27 21:50 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-05-27 19:35 [binutils-gdb] PR symtab/18258 sergiodj+buildbot
2015-05-27 20:17 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-05-27 16:42 [binutils-gdb] [aarch64] Handle unknown instruction encoding sergiodj+buildbot
2015-05-27 17:49 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-05-27 10:48 [binutils-gdb] Fix ARI warnings in aarch64-tdep.c sergiodj+buildbot
2015-05-27 11:01 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-05-27  0:27 [binutils-gdb] PR c++/18141, c++/18417 sergiodj+buildbot
2015-05-27  8:56 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-05-27  0:00 [binutils-gdb] Rename dwarf2 to dwarf in "set debug" and maintenance commands sergiodj+buildbot
2015-05-27  1:10 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-05-26 23:21 [binutils-gdb] PR python/18438 sergiodj+buildbot
2015-05-26 23:26 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-05-26 21:49 [binutils-gdb] gdb: tui: Minor fix to compare against NULL sergiodj+buildbot
2015-05-26 21:59 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-05-26 21:39 [binutils-gdb] gdb: Add 'tui reg prev' command sergiodj+buildbot
2015-05-26 21:45 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-05-26 14:39 [binutils-gdb] New gdb.reverse test case for aarch64 instructions sergiodj+buildbot
2015-05-26 17:34 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-05-26 14:29 [binutils-gdb] Enables gdb.reverse testsuite for aarch64*-linux targets sergiodj+buildbot
2015-05-26 17:16 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-05-26 14:20 [binutils-gdb] Implements aarch64 process record and reverse debugging support sergiodj+buildbot
2015-05-26 16:54 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-05-22 10:45 [binutils-gdb] gdb: New 'tui enable' and 'tui disable' commands sergiodj+buildbot
2015-05-22 11:41 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-05-21 21:54 [binutils-gdb] gdb: Use NULL not 0 in a tui function sergiodj+buildbot
2015-05-22  3:49 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-05-21 19:20 [binutils-gdb] gdb: Remove register class specific layout names sergiodj+buildbot
2015-05-21 20:35 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-05-20 15:11 [binutils-gdb] Skip extra relocations in .rel.plt/.rela.plt sergiodj+buildbot
2015-05-20 15:42 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-05-20  7:46 [binutils-gdb] gdb/ada-lang.c: Rename local variable typename into type_name sergiodj+buildbot
2015-05-20  8:43 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-05-19 14:37 [binutils-gdb] compile: Fix ASAN crash for gdb.compile/compile.exp sergiodj+buildbot
2015-05-19 15:39 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-05-19 12:47 [binutils-gdb] compile: gdb_stdout -> gdb_stdlog sergiodj+buildbot
2015-05-19 14:06 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-05-19 10:23 [binutils-gdb] Fix gdb.base/gdbinit-history.exp when HISTSIZE is set in the environment sergiodj+buildbot
2015-05-19 11:18 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-05-18 11:31 [binutils-gdb] Remove Disp32 from AMD64 direct call/jmp sergiodj+buildbot
2015-05-18 12:40 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-05-18 10:01 [binutils-gdb] [AArch64] Remove X86-64 comments sergiodj+buildbot
2015-05-18 11:08 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-05-17  9:35 [binutils-gdb] sim: erc32: restore attribution sergiodj+buildbot
2015-05-17 10:02 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-05-16 20:42 [binutils-gdb] compile: Fix uninitialized variable compiler warnings sergiodj+buildbot
2015-05-16 22:11 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-05-16 19:57 [binutils-gdb] Add support for unbuffered and zero sized Guile ports sergiodj+buildbot
2015-05-17  0:03 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-05-16 15:35 [binutils-gdb] Don't generate PLT relocations for now binding sergiodj+buildbot
2015-05-16 20:50 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-05-16 15:20 [binutils-gdb] compile: Fix detected inferior type sergiodj+buildbot
2015-05-16 20:32 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-05-16 15:07 [binutils-gdb] compile: New 'compile print' sergiodj+buildbot
2015-05-16 20:14 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-05-16 12:38 [binutils-gdb] compile: Add one debug message sergiodj+buildbot
2015-05-16 13:05 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-05-15 22:25 [binutils-gdb] Array indexed by non-contiguous enumeration types sergiodj+buildbot
2015-05-15 23:54 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-05-14 20:35 [binutils-gdb] Fix build gdbserver build errors on arm, mips, aarch64 sergiodj+buildbot
2015-05-14 21:53 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-05-14 14:17 [binutils-gdb] Fix gdbserver build failure on arm-android sergiodj+buildbot
2015-05-14 19:23 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-05-14 12:20 [binutils-gdb] Remove buggy xterm workaround in tui_dispatch_ctrl_char() sergiodj+buildbot
2015-05-14 17:30 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-05-14 11:50 [binutils-gdb] [AArch64] Remove BFD overflow check restrictions sergiodj+buildbot
2015-05-14 15:38 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-05-13 21:11 [binutils-gdb] dwarf2read.c (die_needs_namespace): Return 1 for DW_TAG_inlined_subroutine sergiodj+buildbot
2015-05-14 12:13 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-05-13 20:59 [binutils-gdb] dwarf2read.c (die_needs_namespace): Return 1 for DW_TAG_inlined_subroutine sergiodj+buildbot
2015-05-14  9:38 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-05-13 18:54 [binutils-gdb] Make regcache_cpy_no_passthrough static sergiodj+buildbot
2015-05-14  8:06 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-05-13 18:53 [binutils-gdb] infcall: stop_registers -> register_dummy_frame_dtor sergiodj+buildbot
2015-05-14  5:01 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-05-13 18:53 [binutils-gdb] Remove stop_registers sergiodj+buildbot
2015-05-14  6:34 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-05-13 18:53 [binutils-gdb] Call dummy_frame_dtor_ftype also from remove_dummy_frame sergiodj+buildbot
2015-05-14  1:27 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-05-13 18:53 [binutils-gdb] register_dummy_frame_dtor: Permit multiple dtors sergiodj+buildbot
2015-05-14  3:21 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-05-13 17:35 [binutils-gdb] gdb/NEWS: Move "Xmethods can now specify a result type" to GDB 7.9.1 section sergiodj+buildbot
2015-05-13 21:32 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-05-13 16:35 [binutils-gdb] Disable the configuration of GDB for HPUX targets sergiodj+buildbot
2015-05-13 19:54 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-05-13 15:59 [binutils-gdb] Avoid race condition when handling a SIGWINCH signal sergiodj+buildbot
2015-05-13 18:19 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-05-13 13:59 [binutils-gdb] dummy_frame_dtor_ftype vs. call_function_by_hand_dummy_dtor_ftype cleanup sergiodj+buildbot
2015-05-13 16:44 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-05-12 20:17 [binutils-gdb] Allocate the first .plt entry space only if needed sergiodj+buildbot
2015-05-13  4:55 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-05-12 17:21 [binutils-gdb] Extended-remote fork catch sergiodj+buildbot
2015-05-13  0:29 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-05-12 17:21 [binutils-gdb] Extended-remote fork event docs sergiodj+buildbot
2015-05-13  2:24 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-05-12 17:20 [binutils-gdb] Extended-remote Linux follow fork sergiodj+buildbot
2015-05-12 21:14 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-05-11 21:37 [binutils-gdb] Remove Disp16|Disp32 from 64-bit direct branches sergiodj+buildbot
2015-05-11 22:08 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-05-09  0:26 [binutils-gdb] Avoid segfault on missing directory table sergiodj+buildbot
2015-05-09 11:44 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-05-08 22:57 [binutils-gdb] Fix register save offset for nios2 signal handler trampolines sergiodj+buildbot
2015-05-09 10:24 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-05-08 19:10 [binutils-gdb] Remove unused declaration of print_return_value sergiodj+buildbot
2015-05-08 21:37 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-05-08 15:28 [binutils-gdb] Switch erc32 simulator copyright headers to FSF sergiodj+buildbot
2015-05-08 17:15 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-05-08 11:46 [binutils-gdb] S390: Fix for inadvertently setting 24-bit mode in fill_gregset sergiodj+buildbot
2015-05-08 12:37 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-05-06 18:06 [binutils-gdb] Make the "info dll" command available on all platform sergiodj+buildbot
2015-05-06 18:51 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-05-06  1:28 [binutils-gdb] DWARF: cannot break on out-of-line function nested inside inlined function sergiodj+buildbot
2015-05-06  3:20 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-05-05 22:44 [binutils-gdb] Further document ada-lang.c::value_assign_to_component & fix whitespaces sergiodj+buildbot
2015-05-06  5:20 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-05-05 19:43 [binutils-gdb] [Ada] array of variant record subscripting sergiodj+buildbot
2015-05-05 21:34 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-05-05 19:07 [binutils-gdb] Add valaddr support in dynamic property resolution sergiodj+buildbot
2015-05-05 19:36 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-04-30 15:38 [binutils-gdb] Fix handling of relocs for the MeP target sergiodj+buildbot
2015-04-30 15:43 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-04-29 14:34 [binutils-gdb] Allow passing fd == NULL to exec_file_find and solib_find sergiodj+buildbot
2015-04-29 15:05 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-04-29 11:41 [binutils-gdb] Add support for absolute PE/x86 relocations sergiodj+buildbot
2015-04-29 12:13 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-04-27 23:51 [binutils-gdb] Add support for catching exec events on FreeBSD sergiodj+buildbot
2015-04-28 15:34 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-04-27 23:43 [binutils-gdb] Enable fork tracing for native FreeBSD targets sergiodj+buildbot
2015-04-28  9:59 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-04-27 23:34 [binutils-gdb] Add fbsd_nat_add_target sergiodj+buildbot
2015-04-28  3:43 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-04-25  0:02 [binutils-gdb] gdb: Add internationalization support to a few strings sergiodj+buildbot
2015-04-25 10:07 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-04-24 16:38 [binutils-gdb] Fix typo in check for valid register number in RX sim sergiodj+buildbot
2015-04-24 17:00 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-04-24 10:15 [binutils-gdb] A new board file remote-gdbserver-on-localhost.exp sergiodj+buildbot
2015-04-24 10:56 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-04-23 23:56 [binutils-gdb] Delay setting up compressed debug section names sergiodj+buildbot
2015-04-24  1:58 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-04-22 20:17 [binutils-gdb] windows-nat: Don't change current_event.dwThreadId in handle_output_debug_string() sergiodj+buildbot
2015-04-22 22:46 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-04-19  6:48 [binutils-gdb] sim/erc32: Switched emulated memory to host endian order sergiodj+buildbot
2015-04-19  7:39 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-04-18  9:26 [binutils-gdb] sim: unify SIM_CPU definition sergiodj+buildbot
2015-04-18 10:18 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-04-17 18:36 [binutils-gdb] solib-svr4.c (svr4_exec_displacement): Rename outer "displacement" sergiodj+buildbot
2015-04-18  2:20 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-04-17 16:16 [binutils-gdb] gdbserver/xtensa: fix typo in XCHAL_HAVE_LOOPS sergiodj+buildbot
2015-04-17 22:24 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-04-17 14:33 [binutils-gdb] gdbserver/xtensa: drop xtensa_usrregs_info sergiodj+buildbot
2015-04-17 21:24 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-04-17  8:27 [binutils-gdb] gdb: add myself to blackfin/write-after-approval sergiodj+buildbot
2015-04-17 10:56 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-04-17  7:40 [binutils-gdb] sim: replace CIA_{GET,SET} with CPU_PC_{GET,SET} sergiodj+buildbot
2015-04-17  8:39 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-04-16 14:48 [binutils-gdb] Fix {mi-tracepoint-changed, mi-tsv-changed}.exp with native-extended-gdbserver sergiodj+buildbot
2015-04-16 16:15 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-04-15 20:39 [binutils-gdb] Make info fun|var|types interruptable sergiodj+buildbot
2015-04-16  5:59 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-04-15 18:36 [binutils-gdb] Handle invalid prefixes for rdrand and rdseed sergiodj+buildbot
2015-04-16  0:03 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-04-15 18:13 [binutils-gdb] Replace mandatory_prefix with prefix_requirement sergiodj+buildbot
2015-04-15 22:45 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-04-15 16:19 [binutils-gdb] [arm] Update displaced stepping debug message sergiodj+buildbot
2015-04-15 18:45 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-04-15 13:24 [binutils-gdb] Fix fails in gdb.dwarf2/dynarr-ptr.exp sergiodj+buildbot
2015-04-15 15:44 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-04-15  2:15 [binutils-gdb] Fix typo in commit 6ff71e76 sergiodj+buildbot
2015-04-15  8:15 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-04-14 15:29 [binutils-gdb] Adds support to the RL78 port for linker relaxation affecting .debug sections sergiodj+buildbot
2015-04-14 15:33 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-04-13 22:25 [binutils-gdb] * MAINTAINERS: Update my email address sergiodj+buildbot
2015-04-13 23:16 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-04-13 17:49 [binutils-gdb] Harden gdb.base/coredump-filter.exp sergiodj+buildbot
2015-04-13 20:16 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-04-12 10:22 [binutils-gdb] sim: arm/mips: fix sim_read/sim_write linkage errors sergiodj+buildbot
2015-04-12 11:28 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-04-12  0:12 [binutils-gdb] Don't call getpagesize more than once sergiodj+buildbot
2015-04-12  3:17 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-04-11 22:33 [binutils-gdb] Initialize pagesize_m1 in bfd_cache_init sergiodj+buildbot
2015-04-11 23:00 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-04-10 19:18 [binutils-gdb] [arm] watchpoint-reuse-slot.exp: skip setting HW points on some address sergiodj+buildbot
2015-04-10 21:58 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-04-10 15:56 [binutils-gdb] Test step-over-{lands-on-breakpoint|trips-on-watchpoint}.exp with displaced stepping sergiodj+buildbot
2015-04-10 20:00 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-04-10 10:05 [binutils-gdb] [arm] Fix displaced stepping for thumb alu reg instruction sergiodj+buildbot
2015-04-10 11:16 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot
2015-04-09 18:55 [binutils-gdb] Properly check --compress-debug-sections=XXX sergiodj+buildbot
2015-04-10  3:29 ` Failures on Debian-x86_64-m64, branch master sergiodj+buildbot

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).