public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
* [binutils-gdb] Consider addressable memory unit size in various value functions
@ 2015-07-28 16:24 sergiodj+buildbot
  2015-07-28 16:24 ` Failures on AIX-POWER7-plain, branch master sergiodj+buildbot
                   ` (16 more replies)
  0 siblings, 17 replies; 264+ messages in thread
From: sergiodj+buildbot @ 2015-07-28 16:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3ae385afe150f2e001a1cc8fb14f4ba0ab94cdf2 ***

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

Consider addressable memory unit size in various value functions
This patch updates various value handling functions to make them
consider the addressable memory unit size of the current architecture.
This allows to correctly extract and print values on architectures whose
addressable memory unit is not 8 bits.

The patch doesn't cover all the code that would ideally need to be
adjusted, only the code paths that we happen to use, plus a few obvious
ones.  Specifically, those areas are not covered by this patch:

 - Management of unavailable bits
 - Bitfields
 - C++ stuff

Regression-tested on x86-64 Ubuntu 14.04.  I saw no related test result
change.

gdb/ChangeLog:

	* c-valprint.c (c_val_print_array): Consider addressable memory
	unit size.
	(c_val_print_ptr): Likewise.
	(c_val_print_int): Likewise.
	* findvar.c (read_frame_register_value): Likewise.
	* valarith.c (find_size_for_pointer_math): Likewise.
	(value_ptrdiff): Likewise.
	(value_subscripted_rvalue): Likewise.
	* valops.c (read_value_memory): Likewise (and rename variables).
	(value_assign): Likewise.
	(value_repeat): Likewise.
	(value_array): Likewise.
	(value_slice): Likewise.
	* valprint.c (generic_val_print_ptr): Likewise.
	(generic_val_print_enum): 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.
	(val_print_scalar_formatted): Likewise.
	(val_print_array_elements): Likewise.
	* value.c (set_value_parent): Likewise.
	(value_contents_copy_raw): Likewise.
	(set_internalvar_component): Likewise.
	(value_primitive_field): Likewise.
	(value_fetch_lazy): Likewise.
	* value.h (read_value_memory): Update comment.


^ permalink raw reply	[flat|nested] 264+ messages in thread
* [binutils-gdb] objfiles.h,psympriv.h,psymtab.c: Whitespace.
@ 2015-08-15 23:05 sergiodj+buildbot
  2015-08-24 15:25 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ 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-24 14:41 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ 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-24 10:56 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ messages in thread
* [binutils-gdb] New /s modifier for the disassemble command.
@ 2015-08-15  4:59 sergiodj+buildbot
  2015-08-24  9:57 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ 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-24  8:49 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ messages in thread
* [binutils-gdb] Rename location accessor macro parameters to silence ARI
@ 2015-08-14 22:33 sergiodj+buildbot
  2015-08-24  8:46 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ messages in thread
* [binutils-gdb] mi_make_breakpoint: add "evaluated-by" option
@ 2015-08-14 21:57 sergiodj+buildbot
  2015-08-24  5:02 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ messages in thread
* [binutils-gdb] Fix ARI warnings in d-exp.y
@ 2015-08-14 20:00 sergiodj+buildbot
  2015-08-24  4:06 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ messages in thread
* [binutils-gdb] Add support for DT_MIPS_RLD_MAP_REL.
@ 2015-08-14 14:27 sergiodj+buildbot
  2015-08-24  0:22 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ messages in thread
* [binutils-gdb] Add myself to gdb MAINTAINERS
@ 2015-08-14 12:24 sergiodj+buildbot
  2015-08-23 20:39 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ messages in thread
* [binutils-gdb] Revert "Fix encoding or OpenRisk1000 PC relative relocations."
@ 2015-08-14  1:48 sergiodj+buildbot
  2015-08-23 16:56 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ 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-23 13:12 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ 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-23 12:10 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ messages in thread
* [binutils-gdb] gdb.base/dso2dso.exp: Improve testcase documentation.
@ 2015-08-13 18:46 sergiodj+buildbot
  2015-08-23  0:21 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ messages in thread
* [binutils-gdb] Fix Python frame unwinder issue caught by Valgrind
@ 2015-08-13 18:17 sergiodj+buildbot
  2015-08-22 23:26 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ messages in thread
* [binutils-gdb] Mass rename `explicit' -> `explicit_loc'.
@ 2015-08-13 17:22 sergiodj+buildbot
  2015-08-22 22:21 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ 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-22 18:38 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ 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-22 14:55 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ messages in thread
* [binutils-gdb] [Ada] Add support for subprogram renamings
@ 2015-08-13  7:47 sergiodj+buildbot
  2015-08-22 13:37 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ messages in thread
* [binutils-gdb] gdb.base/dso2dso.exp sometimes broken
@ 2015-08-13  2:02 sergiodj+buildbot
  2015-08-22  9:53 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ messages in thread
* [binutils-gdb] Set EI_OSABI to ELFOSABI_GNU for local IFUNC symbols
@ 2015-08-12 21:03 sergiodj+buildbot
  2015-08-22  6:08 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ messages in thread
* [binutils-gdb] [amd64] Invalid return address after displaced stepping
@ 2015-08-12 20:32 sergiodj+buildbot
  2015-08-22  2:24 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ messages in thread
* [binutils-gdb] Initialize `location' in gdbpy_decode_line
@ 2015-08-12 18:48 sergiodj+buildbot
  2015-08-21 22:41 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ 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-21 21:32 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ messages in thread
* [binutils-gdb] [MIPS] Map 'move' to 'or'.
@ 2015-08-12 16:23 sergiodj+buildbot
  2015-08-21 17:48 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ 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-21 14:05 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ messages in thread
* [binutils-gdb] Introduce save_vars, a testsuite proc for safely manipulating globals
@ 2015-08-12 13:24 sergiodj+buildbot
  2015-08-21 10:22 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ messages in thread
* [binutils-gdb] Sync ansidecl.h with GCC
@ 2015-08-12 12:58 sergiodj+buildbot
  2015-08-21  6:39 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ messages in thread
* [binutils-gdb] Remove trailing spaces in opcodes
@ 2015-08-12 12:26 sergiodj+buildbot
  2015-08-21  2:55 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ messages in thread
* [binutils-gdb] Remove trailing spaces in bfd
@ 2015-08-12 11:58 sergiodj+buildbot
  2015-08-20 23:12 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ 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-20 15:53 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ messages in thread
[parent not found: <33ebda9d6841e18d9ef18b94c3dcad7d0498ab3d@gdb-build>]
* [binutils-gdb] Properly skip IFUNC relocations in debug sections
@ 2015-08-12  5:48 sergiodj+buildbot
  2015-08-20 12:08 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ messages in thread
* [binutils-gdb] Explicit locations: documentation updates
@ 2015-08-12  5:23 sergiodj+buildbot
  2015-08-20  8:24 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ messages in thread
* [binutils-gdb] Explicit locations: MI support for explicit locations
@ 2015-08-12  4:59 sergiodj+buildbot
  2015-08-20  4:39 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ messages in thread
* [binutils-gdb] Explicit locations: add UI features for CLI
@ 2015-08-12  4:30 sergiodj+buildbot
  2015-08-20  0:54 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ messages in thread
* [binutils-gdb] Explicit locations: introduce explicit locations
@ 2015-08-12  4:04 sergiodj+buildbot
  2015-08-19 21:10 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ messages in thread
* [binutils-gdb] Explicit locations: introduce probe locations
@ 2015-08-12  3:38 sergiodj+buildbot
  2015-08-19 17:25 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ messages in thread
* [binutils-gdb] Explicit locations: introduce address locations
@ 2015-08-12  3:12 sergiodj+buildbot
  2015-08-19 13:42 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ messages in thread
* [binutils-gdb] Explicit locations: use new location API
@ 2015-08-12  2:47 sergiodj+buildbot
  2015-08-19  9:58 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ messages in thread
* [binutils-gdb] Explicit locations: introduce new struct event_location-based API
@ 2015-08-12  2:19 sergiodj+buildbot
  2015-08-19  6:14 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ messages in thread
* [binutils-gdb] Explicit locations: rename "address string"/"addr_string" to "location"
@ 2015-08-12  1:53 sergiodj+buildbot
  2015-08-19  2:30 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ messages in thread
* [binutils-gdb] [AArch64] Improve BFD overflow warning message for -fpic
@ 2015-08-12  1:26 sergiodj+buildbot
  2015-08-18 22:47 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ 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-18 19:04 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ messages in thread
* [binutils-gdb] [AArch64] Long branch veneer support far symbol defined by --defsym
@ 2015-08-12  0:36 sergiodj+buildbot
  2015-08-18 15:20 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ messages in thread
* [binutils-gdb] [AArch64] PR18668, repair long branch veneer for plt stub
@ 2015-08-12  0:11 sergiodj+buildbot
  2015-08-18 11:36 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ 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-18  7:54 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ 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-18  6:38 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ 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-18  5:37 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ 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-18  1:53 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ 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-17 22:10 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ 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-17 21:55 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ 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-17 20:43 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ 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-17 18:03 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ messages in thread
* [binutils-gdb] Skip IFUNC relocations in debug sections
@ 2015-08-11 20:12 sergiodj+buildbot
  2015-08-17 14:18 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ messages in thread
* [binutils-gdb] Fix the disassembly of the AArch64 SIMD EXT instruction.
@ 2015-08-11 17:19 sergiodj+buildbot
  2015-08-17 10:34 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ messages in thread
* [binutils-gdb] Fix encoding or OpenRisk1000 PC relative relocations.
@ 2015-08-11 16:46 sergiodj+buildbot
  2015-08-17  6:51 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ messages in thread
* [binutils-gdb] Fix typo in coff-sh.c.
@ 2015-08-11 16:13 sergiodj+buildbot
  2015-08-17  3:08 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ 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-16 23:25 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ messages in thread
* [binutils-gdb] Fix a typo in _bfd_elf_copy_private_bfd_data
@ 2015-08-11 11:05 sergiodj+buildbot
  2015-08-16 19:42 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ 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-16 16:01 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ 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-16 13:12 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ messages in thread
* [binutils-gdb] gdb/infrun.c: Various trivial ARI fixes.
@ 2015-08-10 18:17 sergiodj+buildbot
  2015-08-16 14:12 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ messages in thread
* [binutils-gdb] Replace hidden with versioned in elf_link_hash_entry
@ 2015-08-10 15:08 sergiodj+buildbot
  2015-08-16 14:42 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ messages in thread
* [binutils-gdb] Add SIGRIE instruction for MIPS R6
@ 2015-08-10  8:27 sergiodj+buildbot
  2015-08-16 14:42 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ 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-15 23:05 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ messages in thread
* [binutils-gdb] native Linux: enable always non-stop by default
@ 2015-08-08  0:24 sergiodj+buildbot
  2015-08-15 19:22 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ 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-15 15:39 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ 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-15 11:57 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ messages in thread
* [binutils-gdb] Disable displaced stepping if trying it fails
@ 2015-08-07 23:02 sergiodj+buildbot
  2015-08-15 11:33 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ 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-15 11:13 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ messages in thread
* [binutils-gdb] Fix interrupt-noterm.exp on targets always in non-stop
@ 2015-08-07 22:08 sergiodj+buildbot
  2015-08-15 10:30 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ 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-14 23:25 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ messages in thread
* [binutils-gdb] Factor out code to re-resume stepped thread
@ 2015-08-07 20:23 sergiodj+buildbot
  2015-08-14 19:44 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ messages in thread
* [binutils-gdb] Add comments to currently_stepping and target_resume
@ 2015-08-07 19:58 sergiodj+buildbot
  2015-08-14 15:44 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ messages in thread
* [binutils-gdb] Misc switch_back_to_stepped_thread cleanups
@ 2015-08-07 19:35 sergiodj+buildbot
  2015-08-14 11:44 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ messages in thread
* [binutils-gdb] Use keep_going in proceed and start_step_over too
@ 2015-08-07 19:05 sergiodj+buildbot
  2015-08-14 10:51 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ messages in thread
* [binutils-gdb] Make thread_still_needs_step_over consider stepping_over_watchpoint too
@ 2015-08-07 18:22 sergiodj+buildbot
  2015-08-14  7:11 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ 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-14  3:32 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ messages in thread
* [binutils-gdb] Change adjust_pc_after_break's prototype
@ 2015-08-07 17:20 sergiodj+buildbot
  2015-08-13 23:54 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ messages in thread
* [binutils-gdb] Fix and test "checkpoint" in non-stop mode
@ 2015-08-07 16:54 sergiodj+buildbot
  2015-08-13 20:16 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ messages in thread
* [binutils-gdb] ignore invalid DOF provider sections
@ 2015-08-07 15:44 sergiodj+buildbot
  2015-08-13 16:36 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ messages in thread
* [binutils-gdb] Properly merge hidden versioned symbol
@ 2015-08-07 12:17 sergiodj+buildbot
  2015-08-13  7:58 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ 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-13  6:42 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ messages in thread
* [binutils-gdb] gdb: get_frame_language now takes a frame parameter.
@ 2015-08-07 11:12 sergiodj+buildbot
  2015-08-13  3:05 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ messages in thread
* [binutils-gdb] Yaakov Selkowitz: fixes for in-tree libiconv
@ 2015-08-07  5:32 sergiodj+buildbot
  2015-08-12 16:11 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ messages in thread
* [binutils-gdb] Bump timeouts for a couple gdb.reverse/*-precsave.exp tests
@ 2015-08-06 23:28 sergiodj+buildbot
  2015-08-12 12:31 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ messages in thread
* [binutils-gdb] Add casts for legitimate integer to enum conversions
@ 2015-08-06 21:34 sergiodj+buildbot
  2015-08-12  7:32 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ messages in thread
* [binutils-gdb] gdbserver: no point in hiding the regcache type nowadays
@ 2015-08-06 18:16 sergiodj+buildbot
  2015-08-12  3:51 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ messages in thread
* [binutils-gdb] PR python/17136
@ 2015-08-06 17:22 sergiodj+buildbot
  2015-08-12  1:46 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ 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-11 13:47 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ messages in thread
* [binutils-gdb] Fix gdbserver --debug issues caught by Valgrind
@ 2015-08-06 15:14 sergiodj+buildbot
  2015-08-11 10:09 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ messages in thread
* [binutils-gdb] Revert "test slowdown"
@ 2015-08-06 14:26 sergiodj+buildbot
  2015-08-11  7:40 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ messages in thread
* [binutils-gdb] Test for PR18749: problems if whole process dies while (ptrace-) stopped
@ 2015-08-06 14:00 sergiodj+buildbot
  2015-08-11  7:24 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-08-06 14:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 83e97ed023e828a7d924b765661374272c7f7eb4 ***

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

Test for PR18749: problems if whole process dies while (ptrace-) stopped
This adds a kfailed test that has the whole process exit just while
several threads continuously step over a breakpoint.  Usually, the
process exits just while GDB or GDBserver is handling the breakpoint
hit.  In other words, the process disappears while the event thread is
(ptrace-) stopped.  This exposes several issues in GDB and GDBserver.
Errors, crashes, etc.

I fixed some of these issues recently, but there's a lot more to do.
It's a bit like playing whack-a-mole at the moment.  You fix an issue,
which then exposes several others.

E.g., with the native target, you get (among other errors):

  (...)
  [New Thread 0x7ffff47b9700 (LWP 18077)]
  [New Thread 0x7ffff3fb8700 (LWP 18078)]
  [New Thread 0x7ffff37b7700 (LWP 18079)]
  Cannot find user-level thread for LWP 18076: generic error
  (gdb) KFAIL: gdb.threads/process-dies-while-handling-bp.exp: non_stop=on: cond_bp_target=1: inferior 1 exited (prompt) (PRMS: gdb/18749)

gdb/testsuite/ChangeLog:
2015-08-06  Pedro Alves  <palves@redhat.com>

	PR gdb/18749
	* gdb.threads/process-dies-while-handling-bp.c: New file.
	* gdb.threads/process-dies-while-handling-bp.exp: New file.


^ permalink raw reply	[flat|nested] 264+ messages in thread
* [binutils-gdb] test slowdown
@ 2015-08-06 13:20 sergiodj+buildbot
  2015-08-11  6:40 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-08-06 13:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4807d3f32937bc4d932638fd8f8b3084be82b74a ***

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

test slowdown


^ permalink raw reply	[flat|nested] 264+ 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-10  3:32 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ 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-09 23:55 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ messages in thread
* [binutils-gdb] Remove get_thread_id
@ 2015-08-05  8:03 sergiodj+buildbot
  2015-08-09 13:06 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-08-05  8:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d89fa914ad6f10cf2827df9b3b86da1a7d9ddfd8 ***

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

Remove get_thread_id
This patch removes get_thread_id from aarch64-linux-nat.c,
arm-linux-nat.c and xtensa-linux-nat.c.

get_thread_id was added in this commit below in 2000,

  41c49b06c471443d3baf2eaa2463a315f9b5edca
  https://sourceware.org/ml/gdb-patches/2000-04/msg00398.html

which predates the ptid_t stuff added into GDB.  Nowadays, lwpid of
inferior_ptid is only zero when the inferior is created (in
fork-child.c:fork_inferior) and its lwpid will be set after
linux_nat_wait_1 gets the first event.  After that, lwpid of
inferior_ptid is not zero for linux-nat target, then we can use
ptid_get_lwp, so this function isn't needed anymore.

Even when GDB attaches to a process, the lwp of inferior_ptid
isn't zero,  see linux-nat.c:linux_nat_attach,

  /* The ptrace base target adds the main thread with (pid,0,0)
     format.  Decorate it with lwp info.  */
  ptid = ptid_build (ptid_get_pid (inferior_ptid),
		     ptid_get_pid (inferior_ptid),
		     0);

Note that linux_nat_xfer_partial shifts lwpid to pid for inferior_ptid
temperately for calling linux_ops->to_xfer_partial, but all the
affected functions in this patch are not called in
linux_ops->to_xfer_partial.

I think we can safely remove get_thread_id for all linux native targets.

Regression tested on arm-linux and aarch64-linux.  Unable to build
native GDB and test it on xtensa-linux.

gdb:

2015-08-05  Yao Qi  <yao.qi@linaro.org>

	* aarch64-linux-nat.c (get_thread_id): Remove.
	(debug_reg_change_callback): Call ptid_get_lwp instead of
	get_thread_id.
	(fetch_gregs_from_thread): Likewise.
	(store_gregs_to_thread): Likewise.
	(fetch_fpregs_from_thread): Likewise.
	(store_fpregs_to_thread): Likewise.
	(aarch64_linux_get_debug_reg_capacity): Likewise.
	* arm-linux-nat.c (get_thread_id): Remove.
	(GET_THREAD_ID): Update macro to use ptid_get_lwp.
	* xtensa-linux-nat.c (get_thread_id): Remove.
	(GET_THREAD_ID): Update macro to use ptid_get_lwp.
	* arm-linux-nat.c (get_thread_id): Remove.
	(GET_THREAD_ID): Remove.
	(fetch_fpregs): Call ptid_get_lwp instead of GET_THREAD_ID.
	(store_fpregs, fetch_regs, store_regs): Likewise.
	(fetch_wmmx_regs, store_wmmx_regs): Likewise.
	(fetch_vfp_regs, store_vfp_regs): Likewise.
	(arm_linux_read_description): Likewise.
	(arm_linux_get_hwbp_cap): Likewise.
	* xtensa-linux-nat.c (get_thread_id): Remove.
	(GET_THREAD_ID): Remove.
	(fetch_gregs, store_gregs): Call ptid_get_lwp instead of
	GET_THREAD_ID.


^ permalink raw reply	[flat|nested] 264+ messages in thread
* [binutils-gdb] python: fix Linetable case to LineTable in docstrings and comments
@ 2015-08-04 17:08 sergiodj+buildbot
  2015-08-09  5:52 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-08-04 17:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4efd80aa8a99adbb38d0719ba56b07c9970793b5 ***

Author: Ciro Santilli <ciro.santilli@gmail.com>
Branch: master
Commit: 4efd80aa8a99adbb38d0719ba56b07c9970793b5

python: fix Linetable case to LineTable in docstrings and comments
The class is called LineTable, not Linetable, as specified by
py-linetable.c/gdbpy_initialize_linetable:

    if (gdb_pymodule_addobject (gdb_module, "LineTable",

gdb/ChangeLog:

        * python/py-linetable.c: Fix case of Linetable to LineTable
        in docstrings and code comments.
        * python/py-symtab.c: Same.


^ permalink raw reply	[flat|nested] 264+ messages in thread
* [binutils-gdb] Fix stack buffer overflows when parsing corrupt ihex files.
@ 2015-08-04 16:14 sergiodj+buildbot
  2015-08-09  2:16 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-08-04 16:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7e27a9d5f22f9f7ead11738b1546d0b5c737266b ***

Author: Yuriy M. Kaminskiy <yumkam@gmail.com>
Branch: master
Commit: 7e27a9d5f22f9f7ead11738b1546d0b5c737266b

Fix stack buffer overflows when parsing corrupt ihex files.
	PR binutils/18750
	* ihex.c (ihex_scan): Fixes incorrect escape sequence in error message
	and stack overflow when char is signed and \200-\376 was in place of hex
	digit; also fixes \377 was handled as EOF instead of "incorrect character".
	(ihex_read_section): Changed for consistency.
	(ihex_bad_byte): Prevent (now impossible to trigger) stack
	overflow and incorrect escape sequence handling.
	* srec.c (srec_bad_byte): Likewise.

	* readelf.c (process_mips_specific): Fix incorrect escape
	sequence handling.


^ permalink raw reply	[flat|nested] 264+ messages in thread
* [binutils-gdb] Disable tracepoint support for aarch32
@ 2015-08-04 16:07 sergiodj+buildbot
  2015-08-08 22:40 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-08-04 16:07 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 524b57e6b3a36e0ce6573bbc4dba9f0bd9c165b1 ***

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

Disable tracepoint support for aarch32
We only support tracepoint for aarch64.  Although arm program can run
on aarch64, GDBserver doesn't support tracepoint for it.

gdb/gdbserver:

2015-08-04  Yao Qi  <yao.qi@linaro.org>

	* linux-aarch64-low.c (aarch64_supports_tracepoints): Return 0
	if current_thread is 32 bit.


^ permalink raw reply	[flat|nested] 264+ messages in thread
* [binutils-gdb] Disable Z0 packet on aarch64 on multi-arch debugging
@ 2015-08-04 15:25 sergiodj+buildbot
  2015-08-08 22:01 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-08-04 15:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6085d6f69562472c389679052dcfe66cf3068a76 ***

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

Disable Z0 packet on aarch64 on multi-arch debugging
In multi-arch debugging, if GDB sends Z0 packet, GDBserver should be
able to do several things below:

 - choose the right breakpoint instruction to insert according to the
   information available, such as 'kind' in Z0 packet and address,

 - choose the right breakpoint instruction to check memory writes and
   validate inserted memory breakpoint

 - be aware of different breakpoint instructions in $ARCH_breakpoint_at.

unfortunately GDBserver can't do them now.  Although x86 GDBserver
supports multi-arch, it doesn't need to support them above because
breakpoint instruction on i686 and x86_64 is the same.  However,
breakpoint instructions on aarch64 and arm (arm mode, thumb1, and thumb2)
are different.

I tried to teach aarch64 GDBserver backend to be really
multi-arch-capable in the following ways,

 - linux_low_target return the right breakpoint instruction according to
   the 'kind' in Z0 packet, and insert_memory_breakpoint can do the right
   thing.
 - once breakpoint is inserted, the breakpoint data and length is recorded
   in each breakpoint object, so that validate_breakpoint and
   check_mem_write can get the right breakpoint instruction from each
   breakpoint object, rather than from global variable breakpoint_data.
 - linux_low_target needs another hook function for pc increment after
   hitting a breakpoint.
 - let set_breakpoint_at, which is widely used for tracepoint, use the
   'default' breakpoint instruction.  We can always use aarch64 breakpoint
   instruction since arm doesn't support tracepoint yet.

looks it is not a small piece of work, so I decide to disable Z0 packet
on multi-arch, which means aarch64 GDBserver only supports Z0 packet
if it is started to debug only one process (extended protocol is not
used) and process target description is 64-bit.

gdb/gdbserver:

2015-08-04  Yao Qi  <yao.qi@linaro.org>

	* linux-aarch64-low.c (aarch64_supports_z_point_type): Return
	0 for Z_PACKET_SW_BP if it may be used in multi-arch debugging.
	* server.c (extended_protocol): Remove "static".
	* server.h (extended_protocol): Declare it.


^ permalink raw reply	[flat|nested] 264+ messages in thread
* [binutils-gdb] Get and set PC correctly on aarch64 in multi-arch
@ 2015-08-04 15:09 sergiodj+buildbot
  2015-08-08 18:25 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-08-04 15:09 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8a7e4587c4e7d78ebbb9bcc0e65bc03f784fde6b ***

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

Get and set PC correctly on aarch64 in multi-arch
gdb/gdbserver:

2015-08-04  Yao Qi  <yao.qi@linaro.org>

	* linux-aarch64-low.c (aarch64_get_pc): Get PC register on
	both aarch64 and aarch32.
	(aarch64_set_pc): Likewise.


^ permalink raw reply	[flat|nested] 264+ messages in thread
* [binutils-gdb] Use arm target description and regs_info for 32-bit file on aarch64 GDBserver
@ 2015-08-04 14:37 sergiodj+buildbot
  2015-08-08 17:33 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-08-04 14:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3b53ae99fbb6bea515284f725b83125d09cfea6f ***

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

Use arm target description and regs_info for 32-bit file on aarch64 GDBserver
This patch teaches aarch64-linux GDBserver use 32-bit arm target
description and regs_info if the elf file is 32-bit.

gdb/gdbserver:

2015-08-04  Yao Qi  <yao.qi@linaro.org>

	* configure.srv (case aarch64*-*-linux*): Append arm-with-neon.o
	to srv_regobj and append arm-core.xml arm-vfpv3.xml and
	arm-with-neon.xml to srv_xmlfiles.
	* linux-aarch64-low.c: Include linux-aarch32-low.h.
	(is_64bit_tdesc): New function.
	(aarch64_linux_read_description): New function.
	(aarch64_arch_setup): Call aarch64_linux_read_description.
	(regs_info): Rename to regs_info_aarch64.
	(aarch64_regs_info): Return right regs_info.
	(initialize_low_arch): Call initialize_low_arch_aarch32.


^ permalink raw reply	[flat|nested] 264+ messages in thread
* [binutils-gdb] New regs_info for aarch32
@ 2015-08-04 14:17 sergiodj+buildbot
  2015-08-08 17:02 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-08-04 14:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bd9e6534b7be7a228ce339bced963d2d15856390 ***

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

New regs_info for aarch32
This patch adds a new regs_info regs_info_aarch32 for aarch32, which
can be used by both aarch64 and arm backend.

gdb/gdbserver:

2015-08-04  Yao Qi  <yao.qi@linaro.org>

	* configure.srv (srv_tgtobj): Add linux-aarch32-low.o.
	* linux-aarch32-low.c: New file.
	* linux-aarch32-low.h: New file.
	* linux-arm-low.c (arm_fill_gregset): Move it to
	linux-aarch32-low.c.
	(arm_store_gregset): Likewise.
	(arm_fill_vfpregset): Call arm_fill_vfpregset_num
	(arm_store_vfpregset): Caa arm_store_vfpregset_num.
	(arm_arch_setup): Check if PTRACE_GETREGSET works.
	(regs_info): Rename to regs_info_arm.
	(arm_regs_info): Return regs_info_aarch32 if
	have_ptrace_getregset is 1 and target description is
	arm_with_neon or arm_with_vfpv3.
	(initialize_low_arch): Don't call init_registers_arm_with_neon.
	Call initialize_low_arch_aarch32 instead.


^ permalink raw reply	[flat|nested] 264+ messages in thread
* [binutils-gdb] Move have_ptrace_getregset to linux-low.c
@ 2015-08-04 13:49 sergiodj+buildbot
  2015-08-08 13:26 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ messages in thread
* [binutils-gdb] signal_command: Leftover cleanup chain regression
@ 2015-08-04 12:22 sergiodj+buildbot
  2015-08-08  9:50 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ messages in thread
* [binutils-gdb] ASAN attach crash - 7.9 regression
@ 2015-08-04 11:51 sergiodj+buildbot
  2015-08-08  9:35 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-08-04 11:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 978b9495b78054b76052a09064cae8c94a58b93e ***

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

ASAN attach crash - 7.9 regression
-fsanitize=address
gdb.base/attach-pie-noexec.exp

==32586==ERROR: AddressSanitizer: heap-use-after-free on address 0x60200004ed90 at pc 0x48ad50 bp 0x7ffceb3aef50 sp 0x7ffceb3aef20
READ of size 2 at 0x60200004ed90 thread T0
    #0 0x48ad4f in __interceptor_strlen (/home/jkratoch/redhat/gdb-test-asan/gdb/gdb+0x48ad4f)
    #1 0xeafe5c in xstrdup xstrdup.c:33
    #2 0x85e024 in attach_command /home/jkratoch/redhat/gdb-test-asan/gdb/infcmd.c:2680

regressed by:

commit 6c4486e63f7583ed85a0c72841f6ccceebbf858e
Author: Pedro Alves <palves@redhat.com>
Date:   Fri Oct 17 13:31:26 2014 +0100
    PR gdb/17471: Repeating a background command makes it foreground

gdb/ChangeLog
2015-08-04  Jan Kratochvil  <jan.kratochvil@redhat.com>

	PR gdb/18767
	* infcmd.c (attach_command): Move ARGS_CHAIN cleanup after last ARGS
	use.


^ permalink raw reply	[flat|nested] 264+ messages in thread
* [binutils-gdb] C++: dlsym casts in gdb/linux-thread-db.c and gdb/gdbserver/thread-db.c
@ 2015-08-04  8:57 sergiodj+buildbot
  2015-08-08  5:58 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-08-04  8:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 96e9210fd6fecc1926559dbfa45e7c7c59f7d821 ***

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

C++: dlsym casts in gdb/linux-thread-db.c and gdb/gdbserver/thread-db.c
Implicit void * -> function pointer conversion doesn't work in C++, so
in C++, we need to cast the result of dlsym.  This adds a few typedefs
and macros that make this easy.  GDBserver's version already had the
CHK macro, so I added it to GDB too.

Tested on x86_64 Fedora 20, native and gdbserver.

gdb/gdbserver/ChangeLog:
2015-08-04  Pedro Alves  <palves@redhat.com>

	* thread-db.c (struct thread_db): Use new typedefs.
	(try_thread_db_load_1): Define local TDB_DLSYM macro and use it in
	CHK calls.
	(disable_thread_event_reporting): Cast result of dlsym to
	destination function pointer type.
	(thread_db_mourn): Use td_ta_delete_ftype.

gdb/ChangeLog:
2015-08-04  Pedro Alves  <palves@redhat.com>

	* nat/gdb_thread_db.h (td_init_ftype, td_ta_new_ftype)
	(td_ta_map_lwp2thr_ftype, td_ta_thr_iter_ftype)
	(td_ta_event_addr_ftype, td_ta_set_event_ftype)
	(td_ta_clear_event_ftype, td_ta_event_getmsg_ftype)
	(td_thr_validate_ftype, td_thr_get_info_ftype)
	(td_thr_event_enable_ftype, td_thr_tls_get_addr_ftype)
	(td_thr_tlsbase_ftype, td_symbol_list_ftype, td_ta_delete_ftype):
	New typedefs.
	* linux-thread-db.c (struct thread_db_info): Use new typedefs.
	(try_thread_db_load_1): Define TDB_VERBOSE_DLSYM, TDB_DLSYM , CHK
	local macros and use them instead of verbose_dlsym and dlsym
	calls.


^ permalink raw reply	[flat|nested] 264+ messages in thread
* [binutils-gdb] dwarf2read.c: fix latent buglet
@ 2015-08-03 18:13 sergiodj+buildbot
  2015-08-07 15:33 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-08-03 18:13 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 666fcf91c0117da8294207f631df5a97fdc4157c ***

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

dwarf2read.c: fix latent buglet
cust->includes is:

struct compunit_symtab
{
...
  struct compunit_symtab **includes;

gdb/ChangeLog:
2015-08-03  Pedro Alves  <palves@redhat.com>

	* dwarf2read.c (compute_compunit_symtab_includes): Use size of struct
	compunit_symtab pointer.


^ permalink raw reply	[flat|nested] 264+ messages in thread
* [binutils-gdb] gdb.perf/single-step.exp (SINGLE_STEP_COUNT): Change to 1000 from 10000.
@ 2015-08-03 17:06 sergiodj+buildbot
  2015-08-07 14:53 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-08-03 17:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4e1bdb00c63a839037f31f005349c87702d50cfe ***

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

gdb.perf/single-step.exp (SINGLE_STEP_COUNT): Change to 1000 from 10000.
single-step.exp takes a while to run, and while that's not necessarily
bad, here it's because the default value of SINGLE_STEP_COUNT is 10,000.
We're not going to gain any more insight into perf issues
single-stepping (stepi) 10,000 times over 1,000 times,
so this patch changes the default to 1,000.

gdb/testsuite/ChangeLog:

	* gdb.perf/single-step.exp (SINGLE_STEP_COUNT): Change to 1000 from
	10000.


^ permalink raw reply	[flat|nested] 264+ messages in thread
* [binutils-gdb] Add parallel build support for perf tests.
@ 2015-08-03 16:42 sergiodj+buildbot
  2015-08-07 11:16 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-08-03 16:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3d3389010c00504602656ba6f16c6b91ade75243 ***

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

Add parallel build support for perf tests.
gdb/testsuite/ChangeLog:

	* Makefile.in (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/gdb.exp (make_gdb_parallel_path): New function
	(standard_output_file, standard_temp_file): Call it.
	(GDB_PARALLEL handling): Make outputs,temp,cache directories as subdirs
	of $GDB_PARALLEL.
	* lib/cache.exp (gdb_do_cache): Call make_gdb_parallel_path.


^ permalink raw reply	[flat|nested] 264+ messages in thread
* [binutils-gdb] Move basic perf-test output from perftest.log to perftest.sum.
@ 2015-08-03 16:15 sergiodj+buildbot
  2015-08-07 10:33 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-08-03 16:15 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT af061d3e9c09baa0df2f2d4724baed06cc6158ca ***

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

Move basic perf-test output from perftest.log to perftest.sum.
This patch does two things.
1) Add support for multiple data points.
2) Move the "report" output from perftest.log to perftest.sum.

I want to record the raw data somewhere, and a bit of statistical analysis
(standard deviation left for another day), but I also don't want
it to clutter up the basic report.
This patch takes a cue from gdb.{sum,log} and does the same thing
with perftest.{sum,log}.
Ultimately, we'll probably want to emit raw data to csv files or some
such and then do post-processing passes on that.

gdb/testsuite/ChangeLog:

	* lib/perftest/reporter.py (SUM_FILE_NAME): New global.
	(LOG_FILE_NAME): New global.
	(TextReporter.__init__): Initialize self.txt_sum.
	(TextReporter.report): Add support for multiple data-points.
	Move report to perftest.sum, put raw data in perftest.log.
	(TextReporter.start): Open sum and log files.
	(TextReporter.end): Close sum and log files.
	* lib/perftest/testresult.py (SingleStatisticTestResult.record): Handle
	multiple data-points.


^ permalink raw reply	[flat|nested] 264+ messages in thread
* [binutils-gdb] Fix build error due to uninitialized variable warning
@ 2015-08-03 12:53 sergiodj+buildbot
  2015-08-07  6:57 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-08-03 12:53 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1da03605ced73fc20f40ad649f3038e654d36dee ***

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

Fix build error due to uninitialized variable warning
As of commit a5fdf78a4402341a0ae23a5ca8a63825e2b5286c, building GDB with
a GCC 4.1 host compiler fails with:

gdb/cp-namespace.c: In function 'cp_lookup_symbol_via_imports':
gdb/cp-namespace.c:482: warning: 'sym.block' may be used uninitialized in this function

Apparently, more recent compilers are able to deduce that no actual
uninitialized use of sym.block takes place, but GCC 4.1 isn't yet
able to do that.

Fixed by adding an explicit initalization.

gdb/
	* cp-namespace.c (cp_lookup_symbol_via_imports): Fix uninitialized
	variable warning with some compilers.


^ permalink raw reply	[flat|nested] 264+ messages in thread
[parent not found: <e76460dbb9b9b34b9c7fc2f2e4faae38730d00b0@gdb-build>]
* [binutils-gdb] Complete the previous commit (block_found refactoring)
@ 2015-08-02 18:22 sergiodj+buildbot
  2015-08-02 18:58 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-08-02 18:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 835a09d99d585bfdc9f760970908e10bd8b2fec2 ***

Author: Pierre-Marie de Rodat <derodat@adacore.com>
Branch: master
Commit: 835a09d99d585bfdc9f760970908e10bd8b2fec2

Complete the previous commit (block_found refactoring)
The previous commit (Replace the block_found global with explicit
data-flow) lacks updates in a couple of files because it was not
tested building GDB with --enable-targets=all... but buildbots did.
This adds the appropriate simple updates to fix the build.

gdb/ChangeLog:

	* alpha-mdebug-tdep.c (find_proc_desc): Update call to
	lookup_symbol.
	* ft32-tdep.c (ft32_skip_prologue): Likewise.
	* moxie-tdep.c (moxie_skip_prologue): Likewise.
	* mt-tdep.c (mt_skip_prologue): Likewise.
	* xstormy16-tdep.c (xstormy16_skip_prologue): Likewise.


^ permalink raw reply	[flat|nested] 264+ messages in thread
* [binutils-gdb] Replace the block_found global with explicit data-flow
@ 2015-08-01  9:01 sergiodj+buildbot
  2015-08-02  7:59 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ messages in thread
* [binutils-gdb] testsuite: tcl exec& -> 'kill -9 $pid' is racy (attach-many-short-lived-thread.exp races and others)
@ 2015-07-31 22:38 sergiodj+buildbot
  2015-08-02  7:04 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-07-31 22:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2c8c5d375e91824387eeacd1d710e714f1534d36 ***

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

testsuite: tcl exec& -> 'kill -9 $pid' is racy (attach-many-short-lived-thread.exp races and others)
The buildbots show that attach-many-short-lived-thread.exp is racy.
But after staring at debug logs and playing with SystemTap scripts for
a (long) while, I figured out that neither GDB, nor the kernel nor the
test's program itself are at fault.

The problem is simply that the testsuite machinery is currently
subject to PID-reuse races.  The attach-many-short-lived-threads.c
test program just happens to be much more susceptible to trigger this
race because threads and processes share the same number space on
Linux, and the test spawns many many short lived threads in
succession, thus enlarging the race window a lot.

Part of the problem is that several tests spawn processes with "exec&"
(in order to test the "attach" command) , and then at the end of the
test, to make sure things are cleaned up, issue a 'remote_spawn "kill
-p $testpid"'.  Since with tcl's "exec&", tcl itself is responsible
for reaping the process's exit status, when we go kill the process,
testpid may have already exited _and_ its status may have (and often
has) been reaped already.  Thus it can happen that another process
meanwhile reuses $testpid, and that "kill" command kills the wrong
process...  Frequently, that happens to be
attach-many-short-lived-thread, but this explains other test's races
as well.

In the attach-many-short-lived-threads test, it sometimes manifests
like this:

 (gdb) file /home/pedro/gdb/mygit/build/gdb/testsuite/gdb.threads/attach-many-short-lived-threads
 Reading symbols from /home/pedro/gdb/mygit/build/gdb/testsuite/gdb.threads/attach-many-short-lived-threads...done.
 (gdb)           Loaded /home/pedro/gdb/mygit/build/gdb/testsuite/gdb.threads/attach-many-short-lived-threads into /home/pedro/gdb/mygit/build/gdb/testsuite/../../gdb/gdb
 attach 5940
 Attaching to program: /home/pedro/gdb/mygit/build/gdb/testsuite/gdb.threads/attach-many-short-lived-threads, process 5940
 warning: process 5940 is a zombie - the process has already terminated
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 ptrace: Operation not permitted.
 (gdb) PASS: gdb.threads/attach-many-short-lived-threads.exp: iter 1: attach
 info threads
 No threads.
 (gdb) PASS: gdb.threads/attach-many-short-lived-threads.exp: iter 1: no new threads
 set breakpoint always-inserted on
 (gdb) PASS: gdb.threads/attach-many-short-lived-threads.exp: iter 1: set breakpoint always-inserted on

Other times the process dies while the test is ongoing (the process is
ptrace-stopped):

 (gdb) print again = 1
 Cannot access memory at address 0x6020cc
 (gdb) FAIL: gdb.threads/attach-many-short-lived-threads.exp: iter 2: reset timer in the inferior

(Recall that on Linux, SIGKILL is not interceptable)

And other times it dies just while we're detaching:

 $4 = 319
 (gdb) PASS: gdb.threads/attach-many-short-lived-threads.exp: iter 2: print seconds_left
 detach
 Can't detach Thread 0x7fb13b7de700 (LWP 1842): No such process
 (gdb) FAIL: gdb.threads/attach-many-short-lived-threads.exp: iter 2: detach

GDB mishandles the latter (it should ignore ESRCH while detaching just
like when continuing), but that's another story.

The fix here is to change spawn_wait_for_attach to use Expect's
'spawn' command instead of Tcl's 'exec&' to spawn programs, because
with spawn we control when to wait for/reap the process.  That allows
killing the process by PID without being subject to pid-reuse races,
because even if the process is already dead, the kernel won't reuse
the process's PID until the zombie is reaped.

The other part of the problem lies in DejaGnu itself, unfortunately.
I have occasionally seen tests (attach-many-short-lived-threads
included, but not only that one) die with a random inexplicable
SIGTERM too, and that too is caused by the same reason, except that in
that case, the rogue SIGTERM is sent from this bit in DejaGnu's remote.exp:

    exec sh -c "exec > /dev/null 2>&1 && (kill -2 $pgid || kill -2 $pid) && sleep 5 && (kill $pgid || kill $pid) && sleep 5 && (kill -9 $pgid || kill -9 $pid) &"
    ...
    catch "wait -i $shell_id"

Even if the program exits promptly, that whole cascade of kills
carries on in the background, thus potentially killing the poor
process that manages to reuse $pid...

I sent a fix for that to the DejaGnu list:
 http://lists.gnu.org/archive/html/dejagnu/2015-07/msg00000.html

With both patches in place, I haven't seen
attach-many-short-lived-threads.exp fail again.

Tested on x86_64 Fedora 20, native, gdbserver and extended-gdbserver.

gdb/testsuite/ChangeLog:
2015-07-31  Pedro Alves  <palves@redhat.com>

	* gdb.base/attach-pie-misread.exp: Rename $res to $test_spawn_id.
	Use spawn_id_get_pid.  Wait for spawn id after eof.  Use
	kill_wait_spawned_process instead of explicit "kill -9".
	* gdb.base/attach-pie-noexec.exp: Adjust to spawn_wait_for_attach
	returning a spawn id instead of a pid.  Use spawn_id_get_pid and
	kill_wait_spawned_process.
	* gdb.base/attach-twice.exp: Likewise.
	* gdb.base/attach.exp: Likewise.
	(do_command_attach_tests): Use gdb_spawn_with_cmdline_opts and
	gdb_test_multiple.
	* gdb.base/solib-overlap.exp: Adjust to spawn_wait_for_attach
	returning a spawn id instead of a pid.  Use spawn_id_get_pid and
	kill_wait_spawned_process.
	* gdb.base/valgrind-infcall.exp: Likewise.
	* gdb.multi/multi-attach.exp: Likewise.
	* gdb.python/py-prompt.exp: Likewise.
	* gdb.python/py-sync-interp.exp: Likewise.
	* gdb.server/ext-attach.exp: Likewise.
	* gdb.threads/attach-into-signal.exp (corefunc): Use
	spawn_wait_for_attach, spawn_id_get_pid and
	kill_wait_spawned_process.
	* gdb.threads/attach-many-short-lived-threads.exp: Adjust to
	spawn_wait_for_attach returning a spawn id instead of a pid.  Use
	spawn_id_get_pid and kill_wait_spawned_process.
	* gdb.threads/attach-stopped.exp (corefunc): Use
	spawn_wait_for_attach, spawn_id_get_pid and
	kill_wait_spawned_process.
	* gdb.base/break-interp.exp: Rename $res to $test_spawn_id.
	Use spawn_id_get_pid.  Wait for spawn id after eof.  Use
	kill_wait_spawned_process instead of explicit "kill -9".
	* lib/gdb.exp (can_spawn_for_attach): Adjust comment.
	(kill_wait_spawned_process, spawn_id_get_pid): New procedures.
	(spawn_wait_for_attach): Use spawn instead of exec to spawn
	processes.  Don't map cygwin/windows pids here.  Now returns a
	spawn id list.


^ permalink raw reply	[flat|nested] 264+ messages in thread
* [binutils-gdb] Fix m32r_remove_watchpoint parameter type
@ 2015-07-31 18:24 sergiodj+buildbot
  2015-08-02  3:27 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-07-31 18:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b1c59ddc809bc4ad2c082b5cae02a18c68746257 ***

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

Fix m32r_remove_watchpoint parameter type
This change should have been in the previous patch (Mostly trivial enum
fixes).

gdb/ChangeLog:

	* remote-m32r-sdi.c (m32r_remove_watchpoint): Use enum type
	instead of integer.


^ permalink raw reply	[flat|nested] 264+ messages in thread
* [binutils-gdb] Mostly trivial enum fixes
@ 2015-07-31 17:25 sergiodj+buildbot
  2015-08-01 23:51 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ messages in thread
* [binutils-gdb] Don't allow non-stack memory writes in the prologue for nios2.
@ 2015-07-30 22:43 sergiodj+buildbot
  2015-08-01 19:15 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-07-30 22:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e1b5381f1b24d2c6b1e254cf7e35f8a470394adc ***

Author: Sandra Loosemore <sandra@codesourcery.com>
Branch: master
Commit: e1b5381f1b24d2c6b1e254cf7e35f8a470394adc

Don't allow non-stack memory writes in the prologue for nios2.
2015-07-30  Sandra Loosemore  <sandra@codesourcery.com>

	gdb/
	* nios2-tdep.c (nios2_analyze_prologue): Do what the comment
	already says and disallow non-stack memory writes in the prologue.


^ permalink raw reply	[flat|nested] 264+ messages in thread
* [binutils-gdb] remote follow fork and spurious child stops in non-stop mode
@ 2015-07-30 19:05 sergiodj+buildbot
  2015-07-31 20:31 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-07-30 19:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 998d452ac81bc240996c967dd27f7b747240cd66 ***

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

remote follow fork and spurious child stops in non-stop mode
Running gdb.threads/fork-plus-threads.exp against gdbserver in
extended-remote mode, even though the test passes, we still see broken
behavior:

 (gdb) PASS: gdb.threads/fork-plus-threads.exp: set detach-on-fork off
 continue &
 Continuing.
 (gdb) PASS: gdb.threads/fork-plus-threads.exp: continue &
 [New Thread 28092.28092]

 [Thread 28092.28092] #2 stopped.
 [New Thread 28094.28094]
 [Inferior 2 (process 28092) exited normally]
 [New Thread 28094.28105]
 [New Thread 28094.28109]

...

[Thread 28174.28174] #18 stopped.
 [New Thread 28185.28185]
 [Inferior 10 (process 28174) exited normally]
 [New Thread 28185.28196]

 [Thread 28185.28185] #20 stopped.
 Cannot remove breakpoints because program is no longer writable.
 Further execution is probably impossible.
 [Inferior 11 (process 28185) exited normally]
 [Inferior 1 (process 28091) exited normally]
 PASS: gdb.threads/fork-plus-threads.exp: reached breakpoint
 info threads
 No threads.
 (gdb) PASS: gdb.threads/fork-plus-threads.exp: no threads left
 info inferiors
   Num  Description       Executable
 * 1    <null>            /home/pedro/gdb/mygit/build/gdb/testsuite/gdb.threads/fork-plus-threads
 (gdb) PASS: gdb.threads/fork-plus-threads.exp: only inferior 1 left

All the "[Thread FOO] #NN stopped." above are bogus, as well as the
"Cannot remove breakpoints because program is no longer writable.",
which is a consequence.

The problem is that when we intercept a fork event, we should report
the event for the parent, only, and leave the child stopped, but not
report its stop event.  GDB later decides whether to follow the parent
or the child.  But because handle_extended_wait does not set the
child's last_status.kind to TARGET_WAITKIND_STOPPED, a
stop_all_threads/unstop_all_lwps sequence (e.g., from trying to access
memory) by mistake ends up queueing a SIGSTOP on the child, resuming
it, and then when that SIGSTOP is intercepted, because the LWP has
last_resume_kind set to resume_stop, gdbserver reports the stop to
GDB, as GDB_SIGNAL_0:

...
 >>>> entering unstop_all_lwps
 unstopping all lwps
 proceed_one_lwp: lwp 1600
    client wants LWP to remain 1600 stopped
 proceed_one_lwp: lwp 1828
 Client wants LWP 1828 to stop. Making sure it has a SIGSTOP pending
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 Sending sigstop to lwp 1828
 pc is 0x3615ebc7cc
 Resuming lwp 1828 (continue, signal 0, stop expected)
   continue from pc 0x3615ebc7cc
 unstop_all_lwps done
 sigchld_handler
 <<<< exiting unstop_all_lwps
 handling possible target event
 >>>> entering linux_wait_1
 linux_wait_1: [<all threads>]
 my_waitpid (-1, 0x40000001)
 my_waitpid (-1, 0x1): status(137f), 1828
 LWFE: waitpid(-1, ...) returned 1828, ERRNO-OK
 LLW: waitpid 1828 received Stopped (signal) (stopped)
 pc is 0x3615ebc7cc
 Expected stop.
 LLW: resume_stop SIGSTOP caught for LWP 1828.1828.
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
...
 linux_wait_1 ret = LWP 1828.1828, 1, 0
 <<<< exiting linux_wait_1
 Writing resume reply for LWP 1828.1828:1
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Tested on x86_64 Fedora 20, extended-remote.

gdb/gdbserver/ChangeLog:
2015-07-30  Pedro Alves  <palves@redhat.com>

	* linux-low.c (handle_extended_wait): Set the child's last
	reported status to TARGET_WAITKIND_STOPPED.


^ permalink raw reply	[flat|nested] 264+ messages in thread
* [binutils-gdb] PR threads/18600: Inferiors left around after fork+thread spawn
@ 2015-07-30 18:34 sergiodj+buildbot
  2015-07-31 19:48 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-07-30 18:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 69dde7dcb81f6baf2b823dcc03e040c29ee5de7d ***

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

PR threads/18600: Inferiors left around after fork+thread spawn
The new gdb.threads/fork-plus-threads.exp test exposes one more
problem.  When one types "info inferiors" after running the program,
one see's a couple inferior left still, while there should only be
inferior #1 left.  E.g.:

 (gdb) info inferiors
   Num  Description       Executable
   4    process 8393      /home/pedro/bugs/src/test
   2    process 8388      /home/pedro/bugs/src/test
 * 1    <null>            /home/pedro/bugs/src/test
 (gdb) info threads

Calling prune_inferiors() manually at this point (from a top gdb) does
not remove them, because they still have inf->pid != 0 (while they
shouldn't).  This suggests that we never mourned those inferiors.

Enabling logs (master + previous patch) we see:

 ...
 WL: waitpid Thread 0x7ffff7fc2740 (LWP 9513) received Trace/breakpoint trap (stopped)
 WL: Handling extended status 0x03057f
 LHEW: Got clone event from LWP 9513, new child is LWP 9579
 [New Thread 0x7ffff37b8700 (LWP 9579)]
 WL: waitpid Thread 0x7ffff7fc2740 (LWP 9508) received 0 (exited)
 WL: Thread 0x7ffff7fc2740 (LWP 9508) exited.
			    ^^^^^^^^
 [Thread 0x7ffff7fc2740 (LWP 9508) exited]
 WL: waitpid Thread 0x7ffff7fc2740 (LWP 9499) received 0 (exited)
 WL: Thread 0x7ffff7fc2740 (LWP 9499) exited.
 [Thread 0x7ffff7fc2740 (LWP 9499) exited]
 RSRL: resuming stopped-resumed LWP Thread 0x7ffff37b8700 (LWP 9579) at 0x3615ef4ce1: step=0
 ...
 (gdb) info inferiors
   Num  Description       Executable
   5    process 9508      /home/pedro/bugs/src/test
		^^^^
   4    process 9503      /home/pedro/bugs/src/test
   3    process 9500      /home/pedro/bugs/src/test
   2    process 9499      /home/pedro/bugs/src/test
 * 1    <null>            /home/pedro/bugs/src/test
 (gdb)
 ...

Note the "Thread 0x7ffff7fc2740 (LWP 9508) exited." line.
That's this in wait_lwp:

      /* Check if the thread has exited.  */
      if (WIFEXITED (status) || WIFSIGNALED (status))
	{
	  thread_dead = 1;
	  if (debug_linux_nat)
	    fprintf_unfiltered (gdb_stdlog, "WL: %s exited.\n",
				target_pid_to_str (lp->ptid));
	}
    }

That was the leader thread reporting an exit, meaning the whole
process is gone.  So the problem is that this code doesn't understand
that an WIFEXITED status of the leader LWP should be reported to
infrun as process exit.

gdb/ChangeLog:
2015-07-30  Pedro Alves  <palves@redhat.com>

	PR threads/18600
	* linux-nat.c (wait_lwp): Report to the core when thread group
	leader exits.

gdb/testsuite/ChangeLog:
2015-07-30  Pedro Alves  <palves@redhat.com>

	PR threads/18600
	* gdb.threads/fork-plus-threads.exp: Test that "info inferiors"
	only shows inferior 1.


^ permalink raw reply	[flat|nested] 264+ messages in thread
* [binutils-gdb] PR threads/18600: Threads left stopped after fork+thread spawn
@ 2015-07-30 18:03 sergiodj+buildbot
  2015-07-31 16:12 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-07-30 18:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4dd63d488a76482543517c4c4cde699ee6fa33ef ***

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

PR threads/18600: Threads left stopped after fork+thread spawn
When a program forks and another process start threads while gdb is
handling the fork event, newly created threads are left stuck stopped
by gdb, even though gdb presents them as "running", to the user.

This can be seen with the test added by this patch.  The test has the
inferior fork a certain number of times and waits for all children to
exit.  Each fork child spawns a number of threads that do nothing and
joins them immediately.  Normally, the program should run unimpeded
(from the point of view of the user) and exit very quickly.  Without
this fix, it doesn't because of some threads left stopped by gdb, so
inferior 1 never exits.

The program triggers when a new clone thread is found while inside the
linux_stop_and_wait_all_lwps call in linux-thread-db.c:

      linux_stop_and_wait_all_lwps ();

      ALL_LWPS (lp)
	if (ptid_get_pid (lp->ptid) == pid)
	  thread_from_lwp (lp->ptid);

      linux_unstop_all_lwps ();

Within linux_stop_and_wait_all_lwps, we reach
linux_handle_extended_wait with the "stopping" parameter set to 1, and
because of that we don't mark the new lwp as resumed.  As consequence,
the subsequent resume_stopped_resumed_lwps, called from
linux_unstop_all_lwps, never resumes the new LWP.

There's lots of cruft in linux_handle_extended_wait that no longer
makes sense.  On systems with CLONE events support, we don't rely on
libthread_db for thread listing anymore, so the code that preserves
stop_requested and the handling of last_resume_kind is all dead.

So the fix is to remove all that, and simply always mark the new LWP
as resumed, so that resume_stopped_resumed_lwps re-resumes it.

gdb/ChangeLog:
2015-07-30  Pedro Alves  <palves@redhat.com>
	    Simon Marchi  <simon.marchi@ericsson.com>

	PR threads/18600
	* linux-nat.c (linux_handle_extended_wait): On CLONE event, always
	mark the new thread as resumed.  Remove STOPPING parameter.
	(wait_lwp): Adjust call to linux_handle_extended_wait.
	(linux_nat_filter_event): Adjust call to
	linux_handle_extended_wait.
	(resume_stopped_resumed_lwps): Add debug output.

gdb/testsuite/ChangeLog:
2015-07-30  Simon Marchi  <simon.marchi@ericsson.com>
	    Pedro Alves  <palves@redhat.com>

	PR threads/18600
	* gdb.threads/fork-plus-threads.c: New file.
	* gdb.threads/fork-plus-threads.exp: New file.


^ permalink raw reply	[flat|nested] 264+ messages in thread
* [binutils-gdb] Remove isize output argument from fast_tracepoint_valid_at
@ 2015-07-30 17:17 sergiodj+buildbot
  2015-07-31 12:36 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-07-30 17:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6b940e6a063ac13372b44a03a54b6be33d22a183 ***

Author: Pierre Langlois <pierre.langlois@arm.com>
Branch: master
Commit: 6b940e6a063ac13372b44a03a54b6be33d22a183

Remove isize output argument from fast_tracepoint_valid_at
This patch removes the isize output argument from the
fast_tracepoint_valid_at gdbarch hook.  It was used to return the size
of the instruction that needs to be replaced when installing a fast
tracepoint.  Instead of getting this value from the
fast_tracepoint_valid_at hook, we can call the gdb_insn_length function.

If we do not do this, then architectures which do not have a restriction
on where to install the fast tracepoint will send uninitialized memory
off to GDBserver.  See remote_download_tracepoint:

~~~
int isize;

if (gdbarch_fast_tracepoint_valid_at (target_gdbarch (),
				      tpaddr, &isize, NULL))
  xsnprintf (buf + strlen (buf), BUF_SIZE - strlen (buf), ":F%x",
	     isize);
~~~

The default implementation of fast_tracepoint_valid_at will not set
isize resulting in uninitialized memory being sent.  Later on, GDBserver
could use this information to compute a jump offset.

gdb/ChangeLog:

	* arch-utils.c (default_fast_tracepoint_valid_at): Remove unused
	isize argument.
	* arch-utils.h (default_fast_tracepoint_valid_at): Likewise.
	* breakpoint.c (check_fast_tracepoint_sals): Adjust call to
	gdbarch_fast_tracepoint_valid_at.
	* gdbarch.sh (fast_tracepoint_valid_at): Remove isize argument.
	* gdbarch.h: Regenerate.
	* gdbarch.c: Regenerate.
	* i386-tdep.c (i386_fast_tracepoint_valid_at): Remove isize
	argument.  Do not set it.
	* remote.c (remote_download_tracepoint): Adjust call to
	gdbarch_fast_tracepoint_valid_at.  Call gdb_insn_length to get
	the instruction length.


^ permalink raw reply	[flat|nested] 264+ 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-07-31  4:40 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ messages in thread
* [binutils-gdb] [AArch64] Rename boolean arguments in decoding functions
@ 2015-07-30 11:50 sergiodj+buildbot
  2015-07-30 21:27 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-07-30 11:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0ea6402e6ce0af0623f0cfd180b626c7ccc41891 ***

Author: Pierre Langlois <pierre.langlois@arm.com>
Branch: master
Commit: 0ea6402e6ce0af0623f0cfd180b626c7ccc41891

[AArch64] Rename boolean arguments in decoding functions
This patch cleans up the decoding functions using booleans when they can
decode two instructions.  The boolean argument is used to know which of
the two instructions was decoded.

The instructions affected are BR/BLR, B/BL, CBZ/CBNZ and TBZ/TBNZ.

These arguments would be named after a named bit in the instruction
encoding, this patch renames them to 'is_XXX'.  Furthermore, the
'unsigned' type would be used to describe a boolean while
aarch64_decode_cb would use 'int' (see the 'is64' argument).  This patch
makes all booleans be 'int' and decoded bitfields be 'unsigned'.

gdb/ChangeLog:

	* aarch64-tdep.c (decode_b): Rename link argument to is_bl.
	Change its type to int *.
	(decode_br): Rename link argument to is_blr.  Change its type to
	int *.
	(decode_cb): Rename op argument to is_cbnz.  Change its type to
	int *.
	(decode_tb): Rename op argument to is_tbnz.  Change its type to
	int *.  Set is_tbnz to either 1 or 0.
	(aarch64_analyze_prologue): Change type of is_link to int.  Add
	new variables is_cbnz and is_tbnz.  Adjust call to
	aarch64_decode_cb and aarch64_decode_tb.


^ permalink raw reply	[flat|nested] 264+ messages in thread
* [binutils-gdb] Properly disassemble movnti in Intel mode
@ 2015-07-30 11:29 sergiodj+buildbot
  2015-07-30 17:49 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-07-30 11:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a8484f9612fc5b7d2b762b6fec950faa0fcd1483 ***

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

Properly disassemble movnti in Intel mode
gas/testsuite/

	PR binutils/13571
	* gas/i386/i386.exp: Run i386-intel and x86_64-intel.
	* gas/i386/i386-intel.d: New file.
	* gas/i386/x86_64-intel.d: Likewise.

opcodes/

	PR binutils/13571
	* i386-dis.c (MOD_0FC3): New.
	(PREFIX_0FC3): Renamed to ...
	(PREFIX_MOD_0_0FC3): This.
	(dis386_twobyte): Replace PREFIX_0FC3 with MOD_0FC3.
	(prefix_table): Replace Ma with Ev on movntiS.
	(mod_table): Add MOD_0FC3.


^ permalink raw reply	[flat|nested] 264+ messages in thread
* [binutils-gdb] Don't change the default symbol for relocatable link
@ 2015-07-30 10:44 sergiodj+buildbot
  2015-07-30 14:09 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-07-30 10:44 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c6e8a9a802bcd3a96ef14b6ea1b6cd60d5d8d065 ***

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

Don't change the default symbol for relocatable link
We should change the default symbol for the versioned symbol only when
not performing a relocatable link.

bfd/

	PR ld/18735
	* elflink.c (_bfd_elf_add_default_symbol): Add the default
	symbol if not performing a relocatable link.
	(elf_link_add_object_symbols): Adjust the default symbol if
	not performing a relocatable link.

ld/testsuite/

	PR ld/18735
	* ld-elf/pr18735.d: New file.
	* ld-elf/pr18735.s: Likewise.


^ permalink raw reply	[flat|nested] 264+ messages in thread
* [binutils-gdb] MIPS ptrace build fixes
@ 2015-07-30  0:59 sergiodj+buildbot
  2015-07-30  0:59 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-07-30  0:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT aa58a496ed9a3ee19233af0bfb7c76ae02b9b2c1 ***

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

MIPS ptrace build fixes
Since Pedro's ptrace cleanups, the MIPS buildbot compilation fails.
Code in MIPS native uses ptrace with 3 arguments, where ptrace requires
4.  When looking at the definition of ptrace in
/usr/include/sys/ptrace.h, it shows that it takes a variable number of
arguments.  The wrapper macro in nat/gdb_ptrace.h takes a fixed number
of arguments (4).  That would explain why it used to work and stopped.

I am pushing this as obvious, tell me if there is any problem.

I built-tested this with a MIPS toolchain (ct-ng), but I don't have any
setup to test it.  At least it should put back the buildbot builder in a
better shape.

gdb/ChangeLog:

	* mips-linux-nat.c (write_watchpoint_regs): Add NULL as ptrace's 4th
	parameter.
	(mips_linux_new_thread): Likewise.
	* nat/mips-linux-watch.c (mips_linux_read_watch_registers): Likewise.

gdb/gdbserver/ChangeLog:

	* linux-mips-low.c (mips_linux_prepare_to_resume): Add NULL as
	ptrace's 4th parameter.


^ permalink raw reply	[flat|nested] 264+ messages in thread
* [binutils-gdb] Make gdb.base/a2-run.exp use $inferior_spawn_id and gdb_test_stdio
@ 2015-07-29 16:17 sergiodj+buildbot
  2015-07-29 20:55 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-07-29 16:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 77e760c3aae925fef163d866a651079fea5f3143 ***

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

Make gdb.base/a2-run.exp use $inferior_spawn_id and gdb_test_stdio
This one is a little more complicated than the other patches in this
series, because of the exit status wrapper handling, requiring a
little state machine.

gdb/testsuite/ChangeLog:
2015-07-29  Pedro Alves  <palves@redhat.com>

	* gdb.base/a2-run.exp (saw_usage, saw_exit_wrapper)
	(saw_spurious_output): Expect inferior output from
	$inferior_spawn_id.  Use gdb_test_stdio.


^ permalink raw reply	[flat|nested] 264+ messages in thread
* [binutils-gdb] Make gdb.base/dprintf.exp use gdb_test_stdio
@ 2015-07-29 15:25 sergiodj+buildbot
  2015-07-29 19:54 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ messages in thread
* [binutils-gdb] Make gdb.base/catch-gdb-caused-signals.exp use gdb_test_stdio
@ 2015-07-29 14:53 sergiodj+buildbot
  2015-07-29 18:51 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-07-29 14:53 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2051d61f76bc009f42d094e57fa0e7114fb23a4e ***

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

Make gdb.base/catch-gdb-caused-signals.exp use gdb_test_stdio
gdb/testsuite/ChangeLog:
2015-07-29  Pedro Alves  <palves@redhat.com>

	* gdb.base/catch-gdb-caused-signals.exp: Use gdb_test_stdio.


^ permalink raw reply	[flat|nested] 264+ messages in thread
* [binutils-gdb] Make gdb.base/call-strs.exp use gdb_test_stdio
@ 2015-07-29 14:28 sergiodj+buildbot
  2015-07-29 17:48 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-07-29 14:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 452397af30f68f6d4ed05fa6d9fc30ca70cbe7f9 ***

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

Make gdb.base/call-strs.exp use gdb_test_stdio
gdb/testsuite/ChangeLog:
2015-07-29  Pedro Alves  <palves@redhat.com>

	* gdb.base/call-strs.exp: Use gdb_test_stdio instead of gdb_test.


^ permalink raw reply	[flat|nested] 264+ messages in thread
* [binutils-gdb] Make gdb.base/sizeof.exp use gdb_test_stdio
@ 2015-07-29 13:47 sergiodj+buildbot
  2015-07-29 16:46 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-07-29 13:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8aed9555b232946606f3fb9370c1657a71c2afaf ***

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

Make gdb.base/sizeof.exp use gdb_test_stdio
gdb/testsuite/ChangeLog:
2015-07-29  Pedro Alves  <palves@redhat.com>

	* gdb.base/sizeof.exp (check_sizeof, check_valueof): Use
	gdb_test_stdio.


^ permalink raw reply	[flat|nested] 264+ messages in thread
* [binutils-gdb] Introduce gdb_test_stdio
@ 2015-07-29 13:15 sergiodj+buildbot
  2015-07-29 15:43 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-07-29 13:15 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 188a61b4404369ae30dce95ad4b05975a3609a33 ***

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

Introduce gdb_test_stdio
This adds a new helper procedure to be used by tests that rely on
stdio.

gdb/testsuite/ChangeLog:
2015-07-29  Pedro Alves  <palves@redhat.com>

	* lib/gdb.exp (gdb_test_stdio): New procedure.


^ permalink raw reply	[flat|nested] 264+ 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-29 14:42 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ messages in thread
* [binutils-gdb] Don't rely on inferior I/O in {call-signal-resume, unwindonsignal}.exp
@ 2015-07-29 12:13 sergiodj+buildbot
  2015-07-29 13:40 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-07-29 12:13 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 23ffc893f5693f20dc807c6a7daad402de0c2e51 ***

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

Don't rely on inferior I/O in {call-signal-resume, unwindonsignal}.exp
These tests rely on inferior I/O, but that seems pointless and
unrelated here.  Simply remove the printf calls, and don't expect
them.

gdb/testsuite/ChangeLog:
2015-07-29  Pedro Alves  <palves@redhat.com>

	* gdb.base/call-signal-resume.exp: Remove check for
	gdb,noinferiorio.  Don't expect "no signal".  Use gdb_test.
	* gdb.base/unwindonsignal.exp: Likewise.
	* gdb.base/call-signals.c (gen_signal): Remove printf call.
	* gdb.base/unwindonsignal.c (gen_signal): Likewise.


^ permalink raw reply	[flat|nested] 264+ messages in thread
* [binutils-gdb] Don't rely on inferior I/O in gdb.base/siginfo-addr.exp
@ 2015-07-29 11:41 sergiodj+buildbot
  2015-07-29 12:37 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-07-29 11:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 655669183104eb8eab559b5faf2b5a676ab6cd3f ***

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

Don't rely on inferior I/O in gdb.base/siginfo-addr.exp
No point in relying on stdio in this test.  Simply run to a breakpoint
instead.

gdb/testsuite/ChangeLog:
2015-07-29  Pedro Alves  <palves@redhat.com>

	* gdb.base/siginfo-addr.c (pass): New function.
	(handler): Call it iff si_addr is correct.
	* gdb.base/siginfo-addr.exp: Remove gdb_skip_stdio_test check.
	Set a breakpoint at "pass" and continue to it.


^ permalink raw reply	[flat|nested] 264+ messages in thread
* [binutils-gdb] bfd/mmo.c (MMIX): Fix massive gcc LTO testsuite failures.
@ 2015-07-29  3:50 sergiodj+buildbot
  2015-07-29  4:45 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-07-29  3:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 11509220a045532b1995b4af5dac2f921b541003 ***

Author: Hans-Peter Nilsson <hp@bitrange.com>
Branch: master
Commit: 11509220a045532b1995b4af5dac2f921b541003

bfd/mmo.c (MMIX): Fix massive gcc LTO testsuite failures.
	* mmo.c (mmo_write_symbols_and_terminator): Skip symbol-type
	assignment loop for bfd plugin objects.


^ permalink raw reply	[flat|nested] 264+ 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-28 22:42 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ messages in thread
* [binutils-gdb] Fix gdb.server/server-exec-info.exp with the extended-remote board
@ 2015-07-28 17:33 sergiodj+buildbot
  2015-07-28 20:40 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-07-28 17:33 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bde40b8f563dd682b9c6bcb8e24c3f5bd944a4f6 ***

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

Fix gdb.server/server-exec-info.exp with the extended-remote board
This test fails with --target_board=native-extended-gdbserver because
it misses the usual "disconnect":

 (gdb) spawn ../gdbserver/gdbserver --once :2347 /home/pedro/gdb/mygit/build/gdb/testsuite/gdb.server/server-exec-info
 Process /home/pedro/gdb/mygit/build/gdb/testsuite/gdb.server/server-exec-info created; pid = 4736
 Listening on port 2347
 target extended-remote localhost:2347
 Already connected to a remote target.  Disconnect? (y or n) ^CsQuit
 (gdb) et sysroot remote:
 Undefined command: "et".  Try "help".
 (gdb) n
 The program is not being run.
 (gdb) FAIL: gdb.server/server-exec-info.exp: set sysroot remote: (got interactive prompt)
 info files
 (gdb) FAIL: gdb.server/server-exec-info.exp: info files

gdb/testsuite/ChangeLog:
2015-07-28  Pedro Alves  <palves@redhat.com>

	* gdb.server/server-exec-info.exp: Issue a "disconnect".


^ permalink raw reply	[flat|nested] 264+ messages in thread
* [binutils-gdb] Introduce get_value_arch
@ 2015-07-28 16:04 sergiodj+buildbot
  2015-07-28 18:52 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-07-28 16:04 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e512cdbdffafefa63baeb835ba6636fcef56e17d ***

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

Introduce get_value_arch
Similar to get_type_arch, used to get the gdbarch associated to a
struct value.

gdb/ChangeLog:

	* value.c (get_value_arch): New function.
	* value.h (get_value_arch): New declaration.


^ permalink raw reply	[flat|nested] 264+ messages in thread
* [binutils-gdb] Update comments in struct value for non-8-bits architectures
@ 2015-07-28 15:45 sergiodj+buildbot
  2015-07-28 17:50 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-07-28 15:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3723fda829671b273d7b31a0753bb1fa8f614cb6 ***

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

Update comments in struct value for non-8-bits architectures
gdb/ChangeLog:

	* value.c (struct value): Update comments.


^ permalink raw reply	[flat|nested] 264+ messages in thread
* [binutils-gdb] Update comment for struct type's length field, introduce type_length_units
@ 2015-07-28 15:23 sergiodj+buildbot
  2015-07-28 16:47 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-07-28 15:23 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2e0569314c2ee9e5635899d47b0bc0a4b9b08d8d ***

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

Update comment for struct type's length field, introduce type_length_units
This patch tries to clean up a bit the blur around the length field in
struct type, regarding its use with architectures with non-8-bits
addressable memory.  It clarifies that the field is expressed in host
bytes, which is what is the closest to the current reality.

It also introduces a new function to get the length of the type in
target addressable memory units.

gdb/ChangeLog:

	* gdbtypes.c (type_length_units): New function.
	* gdbtypes.h (type_length_units): New declaration.
	(struct type) <length>: Update comment.


^ permalink raw reply	[flat|nested] 264+ messages in thread
[parent not found: <13e1dec8960122ec0329f74e5915503e14db5ea2@gdb-build>]
* [binutils-gdb] Fallout from "Reorder more powerpc64 sections for -z relro"
@ 2015-07-28  9:27 sergiodj+buildbot
  2015-07-28 15:44 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-07-28  9:27 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e5654c0f8492e65b3e3ac5e1a2276856049eb1b1 ***

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

Fallout from "Reorder more powerpc64 sections for -z relro"
Commit 23283c1b changed the layout of some bss style sections on
powerpc64, but neglected to add a page gap before the third PT_LOAD
segment created by this reording.  Without a page gap we get two
PT_LOAD headers that overlap by one page in memory.  That shouldn't be
allowed because the dynamic loader will load garbage from the first
page of the last segment over the last page of the previous segment.

bfd/
	* elf.c (_bfd_elf_map_sections_to_segments): Do not make a new
	segment for loaded sections after nonloaded sections if the
	sections are on the same page.
ld/testsuite/
	* ld-powerpc/elfv2so.d: Update


^ permalink raw reply	[flat|nested] 264+ messages in thread
* [binutils-gdb] Check for asprintf and vasprintf during configure stage.
@ 2015-07-28  8:21 sergiodj+buildbot
  2015-07-28 14:42 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-07-28  8:21 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d6f1bafa2c05241b89c0303a9f6a2af89f51c39c ***

Author: Iain Buclaw <ibuclaw@gdcproject.org>
Branch: master
Commit: d6f1bafa2c05241b89c0303a9f6a2af89f51c39c

Check for asprintf and vasprintf during configure stage.
This should fix some build errors seen on AIX, MinGW, and possibly other
non-GNU systems too due to missing asprintf().

bfd/

	* configure.in: Add asprintf and vasprintf to AC_CHECK_DECLS.
	* config.in, configure: Regenerate.


^ permalink raw reply	[flat|nested] 264+ messages in thread
* [binutils-gdb] Remove xfail in gdb.mi/mi-watch.exp
@ 2015-07-28  0:42 sergiodj+buildbot
  2015-07-28 12:37 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ messages in thread
* [binutils-gdb] Factor out complex printing code from generic_val_print
@ 2015-07-28  0:15 sergiodj+buildbot
  2015-07-28 11:34 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-07-28  0:15 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0c87c0bfdfe19d5e2b8938d1db42c43e7b19e53f ***

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

Factor out complex printing code from generic_val_print
gdb/ChangeLog:

	* valprint.c (generic_val_print): Factor out complex
	printing code to ...
	(generic_val_print_complex): ... this new function.


^ permalink raw reply	[flat|nested] 264+ messages in thread
* [binutils-gdb] Factor out decfloat printing code from generic_val_print
@ 2015-07-27 23:49 sergiodj+buildbot
  2015-07-28 10:32 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-07-27 23:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9550ae5e548dd63599ffadedfe8d1768bfc94072 ***

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

Factor out decfloat printing code from generic_val_print
gdb/ChangeLog:

	* valprint.c (generic_val_print): Factor out decfloat
	printing code to ...
	(generic_val_print_decfloat): ... this new function.


^ permalink raw reply	[flat|nested] 264+ messages in thread
* [binutils-gdb] Factor out float printing code from generic_val_print
@ 2015-07-27 23:22 sergiodj+buildbot
  2015-07-28  9:30 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-07-27 23:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7784724bb1b8a5732239e27935cd76813b9df35c ***

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

Factor out float printing code from generic_val_print
gdb/ChangeLog:

	* valprint.c (generic_val_print): Factor out float
	printing code to ...
	(generic_val_print_float): ... this new function.


^ permalink raw reply	[flat|nested] 264+ messages in thread
* [binutils-gdb] Factor out char printing code from generic_val_print
@ 2015-07-27 22:53 sergiodj+buildbot
  2015-07-28  8:28 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-07-27 22:53 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 385f5affc00e88ad6ff0f8287bb3c1c43d59351c ***

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

Factor out char printing code from generic_val_print
gdb/ChangeLog:

	* valprint.c (generic_val_print): Factor out char
	printing code to ...
	(generic_val_print_char): ... this new function.


^ permalink raw reply	[flat|nested] 264+ messages in thread
* [binutils-gdb] Factor out int printing code from generic_val_print
@ 2015-07-27 22:28 sergiodj+buildbot
  2015-07-28  7:26 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ messages in thread
* [binutils-gdb] Factor out bool printing code from generic_val_print
@ 2015-07-27 22:04 sergiodj+buildbot
  2015-07-28  6:23 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-07-27 22:04 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e5bead4b23122be39e0bf32889fd609df6299e1c ***

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

Factor out bool printing code from generic_val_print
gdb/ChangeLog:

	* valprint.c (generic_val_print): Factor out bool
	printing code to ...
	(generic_val_print_bool): ... this new function.


^ permalink raw reply	[flat|nested] 264+ messages in thread
* [binutils-gdb] Factor out function/method printing code from generic_val_print
@ 2015-07-27 21:38 sergiodj+buildbot
  2015-07-28  5:40 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-07-27 21:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4a8c372f1f82d1be24d2575e5979690efd839e08 ***

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

Factor out function/method printing code from generic_val_print
gdb/ChangeLog:

	* valprint.c (generic_val_print): Factor out function/method
	printing code to ...
	(generic_val_print_func): ... this new function.


^ permalink raw reply	[flat|nested] 264+ messages in thread
* [binutils-gdb] Factor out flags printing code from generic_val_print
@ 2015-07-27 21:13 sergiodj+buildbot
  2015-07-28  4:46 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-07-27 21:13 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d93880bd1cd10d0ccf5346e261d5d145d50d8ab0 ***

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

Factor out flags printing code from generic_val_print
gdb/ChangeLog:

	* valprint.c (generic_val_print): Factor out flags
	printing code to ...
	(generic_val_print_flags): ... this new function.


^ permalink raw reply	[flat|nested] 264+ messages in thread
* [binutils-gdb] Factor out enum printing code from generic_val_print
@ 2015-07-27 20:50 sergiodj+buildbot
  2015-07-28  3:44 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-07-27 20:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ef0bc0dd961898d393627c3d502ad168028d7c40 ***

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

Factor out enum printing code from generic_val_print
gdb/ChangeLog:

	* valprint.c (generic_val_print): Factor out enum
	printing code to ...
	(generic_val_print_enum): ... this new function.


^ permalink raw reply	[flat|nested] 264+ messages in thread
* [binutils-gdb] Factor out reference printing code from generic_val_print
@ 2015-07-27 20:24 sergiodj+buildbot
  2015-07-28  2:43 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-07-27 20:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fe43fede4726122efbee9d52b9e68b47be97757f ***

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

Factor out reference printing code from generic_val_print
gdb/ChangeLog:

	* valprint.c (generic_val_print): Factor out reference
	printing code to ...
	(generic_val_print_ref): ... this new function.


^ permalink raw reply	[flat|nested] 264+ messages in thread
* [binutils-gdb] Factor out memberptr printing code from generic_val_print
@ 2015-07-27 20:01 sergiodj+buildbot
  2015-07-28  1:40 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-07-27 20:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 45000ea2f350fae68b4524059ae1876f8e89f2bb ***

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

Factor out memberptr printing code from generic_val_print
gdb/ChangeLog:

	* valprint.c (generic_val_print): Factor out memberptr
	printing code to ...
	(generic_val_print_memberptr): ... this new function.


^ permalink raw reply	[flat|nested] 264+ messages in thread
* [binutils-gdb] Factor out pointer printing code from generic_val_print
@ 2015-07-27 19:36 sergiodj+buildbot
  2015-07-28  0:39 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-07-27 19:36 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 81eb921ae109e875b9df6435ac6947181d824a67 ***

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

Factor out pointer printing code from generic_val_print
gdb/ChangeLog:

	* valprint.c (generic_val_print): Factor out pointer
	printing code to ...
	(generic_val_print_ptr): ... this new function.


^ permalink raw reply	[flat|nested] 264+ messages in thread
* [binutils-gdb] Factor out array printing code from generic_val_print
@ 2015-07-27 19:09 sergiodj+buildbot
  2015-07-27 23:37 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-07-27 19:09 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 557dbe8a5ea7f87fd9e6910997ca04f306cab195 ***

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

Factor out array printing code from generic_val_print
gdb/ChangeLog:

	* valprint.c (generic_val_print): Factor out array
	printing code to ...
	(generic_val_print_array): ... this new function.


^ permalink raw reply	[flat|nested] 264+ messages in thread
* [binutils-gdb] Factor out print_unpacked_pointer from generic_val_print
@ 2015-07-27 18:42 sergiodj+buildbot
  2015-07-27 22:35 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-07-27 18:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9f436164d55690a0b3d2e4308bfd8834996b97d1 ***

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

Factor out print_unpacked_pointer from generic_val_print
gdb/ChangeLog:

	* valprint.c (generic_val_print): Factor out
	print_unpacked_pointer code to ...
	(print_unpacked_pointer): ... this new function.


^ permalink raw reply	[flat|nested] 264+ messages in thread
* [binutils-gdb] Have SIGTERM promptly quit GDB even when the dummy target is active
@ 2015-07-27 17:23 sergiodj+buildbot
  2015-07-27 21:33 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-07-27 17:23 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 077836f7cf6725386c01ae3bb7111663b8f2b85e ***

Author: Patrick Palka <patrick@parcs.ath.cx>
Branch: master
Commit: 077836f7cf6725386c01ae3bb7111663b8f2b85e

Have SIGTERM promptly quit GDB even when the dummy target is active
GDB currently does not promptly quit after receiving a SIGTERM while no
proper target is active.  This is because in handle_sigterm we currently
look at target_can_async_p to determine whether to asynchronously quit
GDB using an async signal handler or to asynchronously quit using the
quit flag.  However, target_can_async_p is always false under the dummy
target, so under this target we always use the quit flag and not the
async signal handler to signal that GDB should quit.  So GDB won't quit
until a code path that checks the quit flag is executed.

To fix this issue, this patch makes the SIGTERM handler no longer
inspect target_can_async_p, and instead makes the handler
unconditionally set the quit flag _and_ mark the corresponding async
signal handler, so that if the target is async (or if it's the dummy
target) then we will likely quit through the async signal handler, and
if it's not async then we will likely quit through the quit flag.  This
redundant approach is similar to how we handle SIGINT.

gdb/ChangeLog:

	* event-top.c (handle_sigterm): Don't inspect
	target_can_async_p.  Always set the quit flag and always mark
	the async signal handler.

gdb/testsuite/ChangeLog:

	* gdb.base/gdb-sigterm-2.exp: New test.


^ permalink raw reply	[flat|nested] 264+ 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 20:31 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ messages in thread
* [binutils-gdb] Remove REMOTE_EXAMPLES from gdb/Makefile.in
@ 2015-07-27 16:26 sergiodj+buildbot
  2015-07-27 19:29 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-07-27 16:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 206350da0f99b9a50fe6405613b3b05561a55aae ***

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

Remove REMOTE_EXAMPLES from gdb/Makefile.in
I happen to see REMOTE_EXAMPLES isn't used anywhere, so this patch
removes it.

REMOTE_EXAMPLES was added in the following commit in 1991,

commit 86bbb439c8fa01fd55d6cbce102483a471ffd0c4
Author: John Gilmore <gnu@cygnus>
Date:   Fri May 3 19:57:13 1991 +0000

    There should be a Makefile in the cvs main directory, configured
    for "./config.gdb none", so that things like "make tags" and "make tar"
    will work.

and it was used like:

TARFILES = ${TAGFILES_MAINDIR} ${OTHERS} ${REMOTE_EXAMPLES}

However TARFILES was removed by the change latter in 1994,

Tue Aug 16 15:24:03 1994  Jim Kingdon  (kingdon@lioth.cygnus.com)

	* symtab.c (decode_line_1): If funfirstline and we get a
	non-LOC_BLOCK symbol (e.g. variable or type), then error().

	* Makefile.in (TARFILES, NONSRC, SFILES_STAND, SFILES_KGDB):
	Remove; unused.

Since then, REMOTE_EXAMPLES is not used any more.

gdb:

2015-07-27  Yao Qi  <yao.qi@linaro.org>

	* Makefile.in (REMOTE_EXAMPLES): Remove it.


^ permalink raw reply	[flat|nested] 264+ messages in thread
* [binutils-gdb] Regenerate configure files
@ 2015-07-27 15:58 sergiodj+buildbot
  2015-07-27 18:27 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-07-27 15:58 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 37a42ee9ad4e4bf635edc87661acb42175f20f91 ***

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

Regenerate configure files
bfd/

	* configure: Regenerated.

binutils/

	* configure: Regenerated.

gas/

	* configure: Regenerated.

gold/

	* configure: Regenerated.

gprof/

	* configure: Regenerated.

ld/

	* configure: Regenerated.

opcodes/

	* configure: Regenerated.


^ permalink raw reply	[flat|nested] 264+ messages in thread
* [binutils-gdb] Sync toplevel files with GCC
@ 2015-07-27 15:26 sergiodj+buildbot
  2015-07-27 17:25 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-07-27 15:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 136bb21fda016fcfc97dfeff692ee899951148de ***

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

Sync toplevel files with GCC
	Sync with GCC
	2015-07-24  Michael Darling  <darlingm@gmail.com>

	PR other/66259
	* config-ml.in: Reflects renaming of configure.in to configure.ac
	* configure: Likewise
	* configure.ac: Likewise


^ permalink raw reply	[flat|nested] 264+ messages in thread
* [binutils-gdb] Sync config with GCC
@ 2015-07-27 15:06 sergiodj+buildbot
  2015-07-27 16:23 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ messages in thread
* [binutils-gdb] Fix the address size computation for the MSP430 port.
@ 2015-07-27 14:27 sergiodj+buildbot
  2015-07-27 15:21 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-07-27 14:27 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 79559014b26f3c6bc64f29dabce613fa89418ee5 ***

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

Fix the address size computation for the MSP430 port.
	* elf32-msp430.c (uses_large_model): New function.
	(msp430_elf_eh_frame_address_size): New function.
	(elf_backend_eh_frame_address_size): Define.


^ permalink raw reply	[flat|nested] 264+ messages in thread
* [binutils-gdb] [AArch64] Fix extern protected data handling
@ 2015-07-27 11:38 sergiodj+buildbot
  2015-07-27 12:56 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-07-27 11:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 32f573bcb3aaa1c9defcad79dbb5851fcc02ae2d ***

Author: Szabolcs Nagy <szabolcs.nagy@arm.com>
Branch: master
Commit: 32f573bcb3aaa1c9defcad79dbb5851fcc02ae2d

[AArch64] Fix extern protected data handling
Emit *GLOB_DAT instead of *RELATIVE relocs for protected data
in shared objects.

This is needed for the fix of glibc bug 17711:
https://sourceware.org/bugzilla/show_bug.cgi?id=17711

bfd:
	PR ld/18705
	* elfnn-aarch64.c (elf_backend_extern_protected_data): Define.

ld/testsuite:
	PR ld/18705
	* ld-aarch64/protected-data.d: New.
	* ld-aarch64/protected-data.s: New.
	* ld-aarch64/aarch64-elf.exp: Add new test.


^ permalink raw reply	[flat|nested] 264+ messages in thread
* [binutils-gdb] [ARM] Fix extern protected data handling
@ 2015-07-27 10:59 sergiodj+buildbot
  2015-07-27 11:54 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-07-27 10:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b68a20d6675f1360ea4db50a9835c073675b9889 ***

Author: Szabolcs Nagy <szabolcs.nagy@arm.com>
Branch: master
Commit: b68a20d6675f1360ea4db50a9835c073675b9889

[ARM] Fix extern protected data handling
Emit *GLOB_DAT instead of *RELATIVE relocs for protected data
in shared objects.

This is needed for the fix of glibc bug 17711:
https://sourceware.org/bugzilla/show_bug.cgi?id=17711

bfd:
	PR ld/18705
	* elf32-arm.c (elf_backend_extern_protected_data): Define.

ld/testsuite:
	PR ld/18705
	* ld-arm/protected-data.d: New.
	* ld-arm/protected-data.s: New.
	* ld-arm/arm-elf.exp: Add new test.


^ permalink raw reply	[flat|nested] 264+ messages in thread
* [binutils-gdb] remote.c: Make read_ptid return a null value when no thread id is found.
@ 2015-07-26  5:14 sergiodj+buildbot
  2015-07-26 18:35 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-07-26  5:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c9f35b348e586c0f48592918324b6e15c815a702 ***

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

remote.c: Make read_ptid return a null value when no thread id is found.
When using GDB to debug an RX target using the GDB remote protocol,
using a Renesas supplied debug agent, I encountered the following
assertion error:

thread.c:85: internal-error: inferior_thread: Assertion `tp' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Create a core file of GDB? (y or n) n
Command aborted.

This assertion error occurs due to the fact that the value associated
with inferior_ptid is not on the thread list.

The remote debug output (obtained with "set debug remote 1") is fairly
short, so I will include it up to the point where things go wrong -
which is somewhat before the assertion failure:

    (gdb) target remote coyote.lan:61234
    Remote debugging using coyote.lan:61234
    Sending packet: $qSupported:multiprocess+;swbreak+;hwbreak+;qRelocInsn+#c9...Ack
    Packet received: PacketSize=c00;qXfer:memory-map:read-;qXfer:features:read-;QStartNoAckMode+;multiprocess+;QNonStop+
    Packet qSupported (supported-packets) is supported
    Sending packet: $QStartNoAckMode#b0...Ack
    Packet received: OK
    Sending packet: $Hgp0.0#ad...Packet received: OK
    Sending packet: $QNonStop:0#8c...Packet received: OK
    Sending packet: $qTStatus#49...Packet received:
    Packet qTStatus (trace-status) is NOT supported
    Sending packet: $?#3f...Packet received: S02
    Sending packet: $qfThreadInfo#bb...Packet received: m1
    Sending packet: $qsThreadInfo#c8...Packet received: l
    Sending packet: $qAttached:a410#bf...Packet received: 0
    Packet qAttached (query-attached) is supported
    Sending packet: $Hc-1#09...Packet received: OK
    Sending packet: $qC#b4...Packet received: QC not supported

Above is the trace starting from the invocation of "target remote"
through the call of get_current_thread() in remote_start_remote().
Below, I've pasted this line of code along with additional lines of
context.  The test following the call is especially important to
understanding both the problem and my patch.

          /* We have thread information; select the thread the target
             says should be current.  If we're reconnecting to a
             multi-threaded program, this will ideally be the thread
             that last reported an event before GDB disconnected.  */
          inferior_ptid = get_current_thread (wait_status);
          if (ptid_equal (inferior_ptid, null_ptid))
            {
              /* Odd... The target was able to list threads, but not
                 tell us which thread was current (no "thread"
                 register in T stop reply?).  Just pick the first
                 thread in the thread list then.  */
              inferior_ptid = thread_list->ptid;
            }
        }

Prior to getting to the code pasted above, remote_start_remote()
made a call to target_update_thread_list().  This corresponds to the
following lines from the above trace:

    Sending packet: $qfThreadInfo#bb...Packet received: m1
    Sending packet: $qsThreadInfo#c8...Packet received: l
    Sending packet: $qAttached:a410#bf...Packet received: 0
    Packet qAttached (query-attached) is supported

Once target_update_thread_list has completed, the thread list
contains a single entry: {pid = 42000, lwp = 1, tid = 0}.

remote_start_remote() then makes a call to set_continue_thread(),
accounting for this line of the trace:

    Sending packet: $Hc-1#09...Packet received: OK

Finally, the call to get_current_thread() is responsible for the last
line of the trace that I provided above:

    Sending packet: $qC#b4...Packet received: QC not supported

get_current_thread() calls stop_reply_extract_thread() with the wait
status. This returns null_ptid.

get_current_thread() then calls remote_current_thread with a null
inferior_ptid.  After the calls to putpkt() and getpkt(), rs->buf[0]
is 'Q', so read_ptid() is called and its result is returned.

The buffer passed to read_ptid() is " not supported".  read_ptid ultimately
returns a ptid of {pid = 4200, lwp = 0, tid = 0}.

However, this thread is not on the thread list.  As noted earlier, the
call to target_update_thread_list() had placed {pid = 42000, lwp = 1,
tid = 0} on the list.  This is the only thread in the list.

When these calls ultimately return to remote_start_remote(),
inferior_ptid gets set to {pid = 4200, lwp = 0, tid = 0}, which
(again) is not on the thread list.

It appears to me that the string " not supported" is coming from the
debug agent.  If so, it should be fixed, but I don't see a reason to
not consult the thread list in order to place a valid thread id in
inferior_ptid.

This (consultation of the thread list) is what is done when
inferior_ptid is null_ptid:

	  if (ptid_equal (inferior_ptid, null_ptid))
	    {
	      /* Odd... The target was able to list threads, but not
		 tell us which thread was current (no "thread"
		 register in T stop reply?).  Just pick the first
		 thread in the thread list then.  */
	      inferior_ptid = thread_list->ptid;
	    }

My patch causes a null inferior_ptid to be returned by read_ptid when
no thread id is found in the response from the debug agent.  This
return value ends up being returned by remote_current_thread() and
then by get_current_thread.  The assignment then places this null
value into inferior_ptid.  That, in turn, allows the ptid_equal test
(noted above) to fetch a valid thread from the thread list.  I no
longer see the assertion failure due a good value (which is on the
thread list) being placed in inferior_ptid.

This patch also adds two log warnings that may be output when "set
debug remote 1" is used.  When running against the Renesas debug agent
mentioned earlier, this is the relevant portion of the log output:

Sending packet: $qC#b4...Packet received: QC not supported
warning: garbage in qC reply
warning: couldn't determine remote current thread; picking first in list.

gdb/ChangeLog:

	* remote.c (read_ptid): Return null_ptid when no thread id
	is found.
	(remote_current_thread): Add log warning for malformed
	qC reply.
	(remote_start_remote): Add log warning when current thread
	not found.


^ permalink raw reply	[flat|nested] 264+ messages in thread
[parent not found: <54019719152ab269fb4cec2c6a8a245ba6af6e49@gdb-build>]
* [binutils-gdb] Revert "Sync readline/ to version 7.0 alpha"
@ 2015-07-25 20:08 sergiodj+buildbot
  2015-07-26 17:33 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-07-25 20:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5836a818eccb180d75c92ce4c861abb6fe8dec23 ***

Author: Patrick Palka <patrick@parcs.ath.cx>
Branch: master
Commit: 5836a818eccb180d75c92ce4c861abb6fe8dec23

Revert "Sync readline/ to version 7.0 alpha"
This reverts commit b558ff043d41ba8d17a82f5f9ae5f9dade66160e.
This reverts commit 4a11f2065906976675808364ddbd1c0f77eea41f.

The initial import commit failed to retain local changes made to
readline's configure.in (and the commit message erroneously stated that
there were no local changes that needed to be reapplied).  Also the
import caused a couple of build errors and a scattering of testsuite
regressions throughout many arches.  It's probably better to start over
with this import, hopefully more carefully next time.


^ permalink raw reply	[flat|nested] 264+ messages in thread
* [binutils-gdb] Revert: * Makefile.in (check/%.exp): Pass directory for GDB_PARALLEL.
@ 2015-07-25 19:17 sergiodj+buildbot
  2015-07-26 16:32 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-07-25 19:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b8cc7b2e9afab37eb9a7cff0d3ae4ebbcf7d494f ***

Author: Doug Evans <xdje42@gmail.com>
Branch: master
Commit: b8cc7b2e9afab37eb9a7cff0d3ae4ebbcf7d494f

Revert: * Makefile.in (check/%.exp): Pass directory for GDB_PARALLEL.
Regressions, e.g.,
http://gdb-build.sergiodj.net/builders/Fedora-x86_64-m32/builds/1501

gdb/testsuite/ChangeLog:

	Revert:
	* 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] 264+ messages in thread
* [binutils-gdb] Don't build readline's shared libs by default
@ 2015-07-25 15:49 sergiodj+buildbot
  2015-07-26 15:29 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-07-25 15:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b558ff043d41ba8d17a82f5f9ae5f9dade66160e ***

Author: Patrick Palka <patrick@parcs.ath.cx>
Branch: master
Commit: b558ff043d41ba8d17a82f5f9ae5f9dade66160e

Don't build readline's shared libs by default
Since the sync to version 7.0-alpho, readline now by default builds
(unused) shared libraries alongside static libraries, whereas before it
only built static libraries.  A couple of GDB buildbots were not happy
with this change:

  http://gdb-build.sergiodj.net/builders/AIX-POWER7-plain/builds/240
  http://gdb-build.sergiodj.net/builders/Fedora-i686/builds/1518

To get these buildbots building again, this patch alters readline's
configure.ac file to not build shared libraries by default, as was the
case with readline 6.2.  A more permanent fix may be to alter the
top-level Makefile.def to pass --disable-shared to readline, or to
investigate why these building these shared libraries are giving the
buildbots trouble.  (I think the proximate reason why the i686 buildbot
fails is because it passes CFLAGS=-m32 instead of CC="gcc -m32" to the
top-level configure script, and readline's linker commands don't inherit
CFLAGS.  Not sure about the AIX failure.)

readline/ChangeLog.gdb:

	* configure.ac: Default opt_shared_libs to no.
	* configure: Regenerate.


^ permalink raw reply	[flat|nested] 264+ messages in thread
* [binutils-gdb] Skip missing symbol version section check for executable
@ 2015-07-25 15:10 sergiodj+buildbot
  2015-07-26 14:27 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-07-25 15:10 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1659f720b0818d6666570f79bef53ac461b2b22f ***

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

Skip missing symbol version section check for executable
Missing symbol version section is a run-time problem only if it will
be referenced dynamically at run-time.  We should skip the check for
locally defined symbol, which isn't referenced by shared library, when
linking executable.

bfd/

	PR ld/18718
	* elflink.c (elf_link_output_extsym): Check symbol version
	section check only if not linking executable, the symbol is
	referenced by shared library or not locally defined.

ld/testsuite/

	PR ld/18718
	* ld-elf/pr18718.c: New file.
	* ld-elf/shared.exp: Run tests for PR ld/18718.


^ permalink raw reply	[flat|nested] 264+ messages in thread
* [binutils-gdb] Sync readline/ to version 7.0 alpha
@ 2015-07-25 14:01 sergiodj+buildbot
  2015-07-26 13:44 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-07-25 14:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4a11f2065906976675808364ddbd1c0f77eea41f ***

Author: Patrick Palka <patrick@parcs.ath.cx>
Branch: master
Commit: 4a11f2065906976675808364ddbd1c0f77eea41f

Sync readline/ to version 7.0 alpha
This patch syncs our upstream copy of readline from version 6.2 to the
latest version, 7.0 alpha (released July 10 2015).

I essentially copied what was done the last time readline was synced,
when Jan updated to readline 6.2 in 2011:
http://sourceware.org/ml/gdb-patches/2011-05/msg00003.html

Procedure:

1. I extracted the readline-7.0-alpha tarball on top of readline/.
2. I deleted all the new files under doc/ that were deliberately omitted
   before.
3. I regenerated readline/configure and readline/examples/rlfe/configure
   using autoconf 2.64.  No other configure files need regenerating.
4. I updated the function gdb_printable_part in completer.c with a
   trivial change made to the readline function it is based off of,
   printable_part in readline/complete.c.  There is more work to be done in
   completer.c to sync it with readline/complete.c, but it is non-trivial
   and should probably be done separately anyway.

Local patches that had to be reapplied:

    None.  readline 7.0 alpha contains all of our local readline
    patches.

New files in readline/:

    colors.{c,h}
    examples/{hist_erasedups,hist_purgecmd,rl-callbacktest,rlbasic}.c
    parse-colors.{c,h}
    readline.pc.in
    configure.ac

Deleted files in readline/:

    configure.in

Regressions:

After the sync there is one testsuite regression, the test
"signal SIGINT" in gdb.gdb/selftest.exp which now FAILs.  Previously,
the readline 6.2 SIGINT handler would temporarily reinstall the
underlying application's SIGINT handler and immediately re-raise SIGINT
so that the orginal handler gets invoked.  But now (since readline 6.3)
its SIGINT handler does not re-raise SIGINT or directly invoke the
original handler; it now sets a flag marking that SIGINT was raised, and
waits until readline explicitly has control to call the application's
SIGINT handler.  Anyway, because SIGINT is no longer re-raised from
within readline's SIGINT handler, doing "signal SIGINT" with a stopped
inferior gdb process will no longer resume and then immediately stop the
process (since there is no 2nd SIGINT to immediately catch).  Instead,
the inferior gdb process will now just print "Quit" and continue to run.
So with this commit, this particular test case is adjusted to reflect
this change in behavior (we now have to send a 2nd SIGINT manually to
stop it).

Aside from this one testsuite regression, I personally noticed no
regression in user-visible behavior.  Though I only tested on x86_64
and on i686 Debian Stretch.

Getting this kind of change in at the start of the GDB 7.11 development
cycle will allow us to get a lot of passive testing from developers and
from bleeding-edge users.

readline/ChangeLog.gdb:

	Import readline 7.0 alpha
	* configure: Regenerate.
	* examples/rlfe/configure: Regenerate.

gdb/ChangeLog:

	* completer.c (gdb_printable_part): Sync with readline function
	it is based off of.

gdb/testsuite/ChangeLog:

	* gdb.gdb/selftest.exp (test_with_self): Update test to now
	expect the GDB inferior to no longer immediately stop after
	being resumed with "signal SIGINT".


^ permalink raw reply	[flat|nested] 264+ messages in thread
* [binutils-gdb] Fix broken -Bsymbolic-functions
@ 2015-07-25 11:23 sergiodj+buildbot
  2015-07-26 12:41 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-07-25 11:23 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a496fbc8802f0a5719db6347a43cc869e03d83c9 ***

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

Fix broken -Bsymbolic-functions
For selected targets.  The testcase reveals a number of targets that
still need fixing.

bfd/
	* elf32-arm.c (elf32_arm_final_link_relocate): Use SYMBOLIC_BIND to
	check if a symbol should be bound symbolically.
	* elf32-hppa.c (elf32_hppa_check_relocs,
	elf32_hppa_adjust_dynamic_symbol, elf32_hppa_relocate_section,
	elf32_hppa_finish_dynamic_symbol): Likewise.
	* elf32-m68k.c (elf_m68k_check_relocs,
	elf_m68k_relocate_section): Likewise.
	* elf32-nios2.c (nios2_elf32_relocate_section,
	nios2_elf32_check_relocs, allocate_dynrelocs): Likewise.
	* elf32-tic6x.c (elf32_tic6x_finish_dynamic_symbol,
	elf32_tic6x_relocate_section): Likewise.
ld/testsuite/
	* ld-elf/symbolic-func.s,
	* ld-elf/symbolic-func.r: New test.
	* ld-elf/elf.exp: Run it.


^ permalink raw reply	[flat|nested] 264+ messages in thread
* [binutils-gdb] Revert 4fd4095a5ffe3d4e50e0dac5f8ad37b8478afa9d, log individual measurements.
@ 2015-07-25  1:51 sergiodj+buildbot
  2015-07-26 11:39 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-07-25  1:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ca3084f54b62ce06c6e70a6e1daafeb5e3317c12 ***

Author: Doug Evans <xdje42@gmail.com>
Branch: master
Commit: ca3084f54b62ce06c6e70a6e1daafeb5e3317c12

Revert 4fd4095a5ffe3d4e50e0dac5f8ad37b8478afa9d, log individual measurements.
I think I lost a patch along the way, because I remember needing
something like this, but the reverted patch isn't the right way to
do this.  Removing ...

gdb/testsuite/ChangeLog:

	* gdb.perf/lib/perftest/measure.py (MeasurementCpuTime::stop): Print
	result.
	(MeasurementWallTime::stop): Ditto.
	(MeasurementVmSizeTime::stop): Ditto.


^ permalink raw reply	[flat|nested] 264+ messages in thread
* [binutils-gdb] Add gmonster-{1,2} perf testcases.
@ 2015-07-25  1:28 sergiodj+buildbot
  2015-07-26 10:37 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ messages in thread
* [binutils-gdb] Add perf testcase generator.
@ 2015-07-25  1:05 sergiodj+buildbot
  2015-07-26  9:42 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ messages in thread
* [binutils-gdb] PerfTest::assemble functions return results.
@ 2015-07-25  0:40 sergiodj+buildbot
  2015-07-26  8:40 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ messages in thread
* [binutils-gdb] lib/gdb.exp (clean_restart): Make executable optional.
@ 2015-07-25  0:14 sergiodj+buildbot
  2015-07-26  8:01 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ messages in thread
* [binutils-gdb] Clean up testsuite compiler_info support.
@ 2015-07-24 23:49 sergiodj+buildbot
  2015-07-26  6:59 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ messages in thread
* [binutils-gdb] Add parallel build support for perf tests.
@ 2015-07-24 23:25 sergiodj+buildbot
  2015-07-26  5:57 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ messages in thread
* [binutils-gdb] Workaround debian change to default value of --as-needed.
@ 2015-07-24 22:54 sergiodj+buildbot
  2015-07-26  4:55 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ messages in thread
* [binutils-gdb] Print data from individual perf runs.
@ 2015-07-24 22:23 sergiodj+buildbot
  2015-07-26  3:53 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-07-24 22:23 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4fd4095a5ffe3d4e50e0dac5f8ad37b8478afa9d ***

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

Print data from individual perf runs.
gdb/testsuite/ChangeLog:

	* gdb.perf/lib/perftest/measure.py (MeasurementCpuTime::stop): Print
	result.
	(MeasurementWallTime::stop): Ditto.
	(MeasurementVmSizeTime::stop): Ditto.


^ permalink raw reply	[flat|nested] 264+ messages in thread
* [binutils-gdb] Call gdb_exit before gdb_skip_xml_test on gdb.base/catch-syscall.exp
@ 2015-07-24 20:59 sergiodj+buildbot
  2015-07-26  2:55 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-07-24 20:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1e76a7e9b156173a76e6a14a3ed41cefc9fed480 ***

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

Call gdb_exit before gdb_skip_xml_test on gdb.base/catch-syscall.exp
The gdb_skip_xml_test procedure explicitly says that it cannot be
invoked when GDB is running.  However, the testcase for "catch
syscall" is wrongly doing that, which is causing a failure on
native-extended-gdbserver tests:

  new FAIL: gdb.base/catch-syscall.exp: set tdesc filename /home/gdb-buildbot/fedora-x86-64-3/fedora-x86-64-native-extended-gdbserver-m32/build/gdb/testsuite/outputs/gdb.base/catch-syscall/trivial.xml (got interactive prompt)

This obvious commit fixes this, by calling gdb_exit before gdb_skip_xml_test.

Checked in as obvious.

gdb/testsuite/ChangeLog
2015-07-24  Sergio Durigan Junior  <sergiodj@redhat.com>

	* gdb.base/catch-syscall.exp: Call gdb_exit before
	gdb_skip_xml_test.


^ permalink raw reply	[flat|nested] 264+ messages in thread
* [binutils-gdb] Fix s390 GNU/Linux build after enum __ptrace_request changes
@ 2015-07-24 19:41 sergiodj+buildbot
  2015-07-26  1:49 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ messages in thread
* [binutils-gdb] gdb.python/py-events.exp and normal_stop observers ordering
@ 2015-07-24 19:12 sergiodj+buildbot
  2015-07-26  0:47 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-07-24 19:12 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5068630ad34dce5fefbe68d70d3a50cd8b92f71e ***

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

gdb.python/py-events.exp and normal_stop observers ordering
I have patches that:

 1 - make the CLI print stop info from a normal_stop observer, like MI
     does.

 2 - happen to change the order in which the Python and CLI/TUI
     normal_stop observers are installed.

With those in place, py-events.exp regresses like shown below [1],
because the Python stop events are output before CLI prints stop info,
instead of after, and the test doesn't expect that.

With the same Python hooks, the order in which MI and Python events is
emited today is already undefined, because MI also uses the
normal_stop observer for output.  I see no reason that we should in
general define the order observers, interpreters and scripting
languages get their turn at being notified of these events.  So this
patch makes the test cope with Python->CLI output order too.

Tested on x86_64 Fedora 20.

gdb/testsuite/
2015-07-24  Pedro Alves  <palves@redhat.com>

	* gdb.python/py-events.exp: Accept output between the stop event
	and the prompt.
	* gdb.python/py-evsignal.exp: Likewise.
	* gdb.python/py-evthreads.exp: Likewise.

[1] - The regressions in question look like:

Before said patches:
  (gdb) continue
  Continuing.
  event type: continue

  Breakpoint 2, first () at /home/pedro/gdb/mygit/build/../src/gdb/testsuite/gdb.python/py-events.c:30
  30	  for (i = 0; i < 2; i++)
  event type: stop
  event type: stop
  stop reason: breakpoint
  first breakpoint number: 2
  breakpoint number: 2
  breakpoint number: 3
  all threads stopped
  (gdb) PASS: gdb.python/py-events.exp: continue

After said patches:
  (gdb) continue
  Continuing.
  event type: continue
  event type: stop
  event type: stop
  stop reason: breakpoint
  first breakpoint number: 2
  breakpoint number: 2
  breakpoint number: 3
  all threads stopped

  Breakpoint 2, first () at /home/pedro/gdb/mygit/build/../src/gdb/testsuite/gdb.python/py-events.c:30
  30	  for (i = 0; i < 2; i++)
  (gdb) FAIL: gdb.python/py-events.exp: continue


^ permalink raw reply	[flat|nested] 264+ messages in thread
* [binutils-gdb] PR gdb/18717: internal error if non-leader thread exits process
@ 2015-07-24 18:44 sergiodj+buildbot
  2015-07-25 23:45 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-07-24 18:44 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7759842763d94dc2f1c7d52d09f9203830b753ab ***

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

PR gdb/18717: internal error if non-leader thread exits process
If a non-leader thread exits the process while all other threads are
ptrace-stopped, native gdb fails an assertion.  The test added by this
commit catches it:

 /home/pedro/gdb/mygit/build/../src/gdb/linux-nat.c:3198: internal-error: linux_nat_filter_event: Assertion `lp->resumed' failed.
 A problem internal to GDB has been detected,
 further debugging may prove unreliable.
 Quit this debugging session? (y or n)
 FAIL: gdb.threads/non-leader-exit-process.exp: program exits normally (GDB internal error)

The fix is just to remove the assertion.

With that out of the way, neither GDB not GDBserver handle this
perfectly though, so I'm adding a KFAIL:

 (gdb) continue
 Continuing.
 [Thread 0x7ffff7fc0700 (LWP 15350) exited]
 No unwaited-for children left.
 Couldn't get registers: No such process.
 (gdb) KFAIL: gdb.threads/non-ldr-exit.exp: program exits normally (PRMS: gdb/18717)

gdb/ChangeLog:
2015-07-24  Pedro Alves  <palves@redhat.com>

	PR gdb/18717
	* linux-nat.c (linux_nat_filter_event): Don't assert that the lwp
	is resumed, and extend the debug log.

gdb/testsuite/ChangeLog:
2015-07-24  Pedro Alves  <palves@redhat.com>

	PR gdb/18717
	* gdb.threads/non-ldr-exit.c: New file.
	* gdb.threads/non-ldr-exit.exp: New file.


^ permalink raw reply	[flat|nested] 264+ messages in thread
* [binutils-gdb] Fix failed exec error message
@ 2015-07-24 18:21 sergiodj+buildbot
  2015-07-25 22:35 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-07-24 18:21 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fe23c31f262151ce3265f5b90870d40cb6840f0a ***

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

Fix failed exec error message
Ref: https://sourceware.org/ml/gdb-patches/2015-07/msg00629.html

This fixes the bogus command line in the error message shown when the
SHELL environment variable points somewhere that's not something that
resembles a shell:

  $ SHELL=/nonexisting gdb /home/pedro/a.out
  (gdb) r
  Starting program: /home/pedro/a.out
 - Cannot exec /home/pedro/a.out -c exec /home/pedro/a.out .
 + Cannot exec /nonexisting -c exec /home/pedro/a.out .
  Error: No such file or directory
  During startup program exited with code 127.
  (gdb)

gdb/ChangeLog:
2015-07-24  Pedro Alves  <palves@redhat.com>

	* fork-child.c (fork_inferior): Print argv[0] instead of exec_file.


^ permalink raw reply	[flat|nested] 264+ messages in thread
* [binutils-gdb] Linux: sys/ptrace.h -> nat/gdb_ptrace.h everywhere
@ 2015-07-24 17:58 sergiodj+buildbot
  2015-07-25 21:33 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-07-24 17:58 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5826e159863b6cd69953dc01faf7c20414409909 ***

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

Linux: sys/ptrace.h -> nat/gdb_ptrace.h everywhere
So that we pick the enum __ptrace_request fix everywhere.

gdb/ChangeLog:
2015-07-24  Pedro Alves  <palves@redhat.com>

	* aarch64-linux-nat.c: Include nat/gdb_ptrace.h instead of
	sys/ptrace.h.
	* alpha-linux-nat.c: Likewise.
	* amd64-linux-nat.c: Likewise.
	* arm-linux-nat.c: Likewise.
	* hppa-linux-nat.c: Likewise.
	* i386-linux-nat.c: Likewise.
	* ia64-linux-nat.c: Likewise.
	* linux-fork.c: Likewise.
	* linux-nat.c: Likewise.
	* m32r-linux-nat.c: Likewise.
	* m68klinux-nat.c: Likewise.
	* mips-linux-nat.c: Likewise.
	* nat/linux-btrace.c: Likewise.
	* nat/linux-ptrace.c: Likewise.
	* nat/linux-ptrace.h
	* nat/mips-linux-watch.c: Likewise.
	* nat/x86-linux-dregs.c: Likewise.
	* ppc-linux-nat.c: Likewise.
	* s390-linux-nat.c: Likewise.
	* spu-linux-nat.c: Likewise.
	* tilegx-linux-nat.c: Likewise.
	* x86-linux-nat.c: Likewise.
	* xtensa-linux-nat.c: Likewise.

gdb/gdbserver/ChangeLog:
2015-07-24  Pedro Alves  <palves@redhat.c: Likewise.om>

	* linux-aarch64-low.c: Include nat/gdb_ptrace.h instead of
	sys/ptrace.h.
	* linux-arm-low.c: Likewise.
	* linux-cris-low.c: Likewise.
	* linux-crisv32-low.c: Likewise.
	* linux-low.c: Likewise.
	* linux-m68k-low.c: Likewise.
	* linux-mips-low.c: Likewise.
	* linux-nios2-low.c: Likewise.
	* linux-s390-low.c: Likewise.
	* linux-sparc-low.c: Likewise.
	* linux-tic6x-low.c: Likewise.
	* linux-tile-low.c: Likewise.
	* linux-x86-low.c: Likewise.


^ permalink raw reply	[flat|nested] 264+ messages in thread
* [binutils-gdb] Move gdb_ptrace.h to nat/
@ 2015-07-24 17:15 sergiodj+buildbot
  2015-07-25 17:03 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-07-24 17:15 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e379037592ff71dc633c6d3de0828babe805ae96 ***

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

Move gdb_ptrace.h to nat/
Now that gdbserver's configure defines PTRACE_TYPE_ARGx etc., we'll be
able to make gdbserver use gdb_ptrace.h too.  Move it to the native
target files directory.

gdb/ChangeLog:
2015-07-24  Pedro Alves  <palves@redhat.com>

	* gdb_ptrace.h: Move ...
	* nat/gdb_ptrace.h: ... here.
	* inf-ptrace.c: Adjust.


^ permalink raw reply	[flat|nested] 264+ messages in thread
* [binutils-gdb] make gdbserver use the same ptrace autoconf checks as gdb
@ 2015-07-24 16:56 sergiodj+buildbot
  2015-07-25 13:27 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-07-24 16:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT eb7aa56163cc15bb732aa3b07966103fd6940d50 ***

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

make gdbserver use the same ptrace autoconf checks as gdb
This factors the ptrace checks out of gdb's configure.ac to a new
ptrace.m4 file, and then makes gdbserver's configure.ac source it too.

gdb/ChangeLog:
2015-07-24  Pedro Alves  <palves@redhat.com>

	* acinclude.m4: Include ptrace.m4.
	* configure.ac: Call GDB_AC_PTRACE and move ptrace checks ...
	* ptrace.m4: ... to this new file.

gdb/gdbserver/ChangeLog:
2015-07-24  Pedro Alves  <palves@redhat.com>

	* acinclude.m4: Include ../ptrace.m4.
	* configure.ac: Call GDB_AC_PTRACE.
	* config.in, configure: Regenerate.


^ permalink raw reply	[flat|nested] 264+ messages in thread
* [binutils-gdb] Remove proc->priv->new_inferior
@ 2015-07-24 16:35 sergiodj+buildbot
  2015-07-25  9:52 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-07-24 16:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 55d7b841962c6e054735acdca2e0bb485afa0144 ***

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

Remove proc->priv->new_inferior
As the result of the previous patch, new_inferior is no longer used.
This patch is to remove it.

gdb/gdbserver:

2015-07-24  Yao Qi  <yao.qi@linaro.org>

	* linux-low.c (linux_create_inferior): Remove setting to
	proc->priv->new_inferior.
	(linux_attach): Likewise.
	(linux_low_filter_event): Likewise.
	* linux-low.h (struct process_info_private) <new_inferior>: Remove.


^ permalink raw reply	[flat|nested] 264+ messages in thread
* [binutils-gdb] Initialise target descrption after skipping extra traps for --wrapper
@ 2015-07-24 16:10 sergiodj+buildbot
  2015-07-25  6:16 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-07-24 16:10 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c06cbd92be66d82eb323a8c6ec451c1dccc02107 ***

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

Initialise target descrption after skipping extra traps for --wrapper
Nowadays, when --wrapper is used, GDBserver skips extra traps/stops
in the wrapper program, and stops at the first instruction of the
program to be debugged.  However, GDBserver created target description
in the first stop of inferior, and the executable of the inferior
is the wrapper program rather than the program to be debugged.  In
this way, the target description can be wrong if the architectures
of wrapper program and program to be debugged are different.  This
is shown by some fails in gdb.server/wrapper.exp on buildbot.

We are testing i686-linux GDB (Fedora-i686) on an x86_64-linux box
(fedora-x86-64-4) in buildbot, such configuration causes fails in
gdb.server/wrapper.exp like this:

spawn /home/gdb-buildbot-2/fedora-x86-64-4/fedora-i686/build/gdb/testsuite/../../gdb/gdbserver/gdbserver --once --wrapper env TEST=1 -- :2346 /home/gdb-buildbot-2/fedora-x86-64-4/fedora-i686/build/gdb/testsuite/outputs/gdb.server/wrapper/wrapper
Process /home/gdb-buildbot-2/fedora-x86-64-4/fedora-i686/build/gdb/testsuite/outputs/gdb.server/wrapper/wrapper created; pid = 8795
Can't debug 64-bit process with 32-bit GDBserver
Exiting
target remote localhost:2346
localhost:2346: Connection timed out.
(gdb) FAIL: gdb.server/wrapper.exp: setting breakpoint at marker

See https://sourceware.org/ml/gdb-testers/2015-q3/msg01541.html

In this case, program to be debugged ("wrapper") is 32-bit but wrapper
program ("/usr/bin/env") is 64-bit, so GDBserver gets the 64-bit
target description instead of 32-bit.

The root cause of this problem is that GDBserver creates target
description too early, and the rationale of fix could be creating
target description once the GDBserver skips extra traps and inferior
stops at the first instruction of the program we want to debug.  IOW,
when GDBserver skips extra traps, the inferior's tdesc is NULL, and
mywait and its callees shouldn't use inferior's tdesc, so in this
patch, we skip code that requires register access, see changes in
linux_resume_one_lwp_throw and need_step_over_p.

In linux_low_filter_event, if target description isn't initialised and
GDBserver attached the process, we create target description immediately,
because GDBserver don't have to skip extra traps for attach, IOW, it
makes no sense to use --attach and --wrapper together.  Otherwise, the
process is launched by GDBserver, we keep the status pending, and return.

After GDBserver skipped extra traps in start_inferior, we call a
target_ops hook arch_setup to initialise target description there.

gdb/gdbserver:

2015-07-24  Yao Qi  <yao.qi@linaro.org>

	* linux-low.c (linux_arch_setup): New function.
	(linux_low_filter_event): If proc->tdesc is NULL and
	proc->attached is true, call the_low_target.arch_setup.
	Otherwise, keep status pending, and return.
	(linux_resume_one_lwp_throw): Don't call get_pc if
	thread->while_stepping isn't NULL.  Don't call
	get_thread_regcache if proc->tdesc is NULL.
	(need_step_over_p): Return 0 if proc->tdesc is NULL.
	(linux_target_ops): Install arch_setup.
	* server.c (start_inferior): Call the_target->arch_setup.
	* target.h (struct target_ops) <arch_setup>: New field.
	(target_arch_setup): New marco.
	* lynx-low.c (lynx_target_ops): Update.
	* nto-low.c (nto_target_ops): Update.
	* spu-low.c (spu_target_ops): Update.
	* win32-low.c (win32_target_ops): Update.


^ permalink raw reply	[flat|nested] 264+ messages in thread
* [binutils-gdb] Set proc->priv->new_inferior out of linux_add_process
@ 2015-07-24 15:48 sergiodj+buildbot
  2015-07-25  2:39 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ messages in thread
* [binutils-gdb] Refactor start_inferior
@ 2015-07-24 15:23 sergiodj+buildbot
  2015-07-24 23:03 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ messages in thread
* [binutils-gdb] Test --wrapper when restarting process.
@ 2015-07-24 14:57 sergiodj+buildbot
  2015-07-24 22:10 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-07-24 14:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 11e6c98f1b6318d27ad55f9ac7d362fe7a668872 ***

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

Test --wrapper when restarting process.
My patch series will affect the code starting inferior in GDBserver
(callees of start_inferior), so we need tests to cover how
start_inferior is used in different cases.

In server.c:process_serial_event, start_inferior is used when
GBDserver receives 'R' packet, and this patch is to add a test
for this path, and see how --wrapper option works when the process
is restarted.

gdb/testsuite:

2015-07-24  Yao Qi  <yao.qi@linaro.org>

	* gdb.server/ext-wrapper.exp: Test --wrapper option when
	restarting process.


^ permalink raw reply	[flat|nested] 264+ messages in thread
* [binutils-gdb] Set general_thread after restart
@ 2015-07-24 14:36 sergiodj+buildbot
  2015-07-24 18:32 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-07-24 14:36 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 51aee833ed9c6bd67b0c0e4a8c7098a549e3d16d ***

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

Set general_thread after restart
When I run gdb.server/ext-restart.exp, I get the following GDB internal
error,

run^M
The program being debugged has been started already.^M
Start it from the beginning? (y or n) y^M
Sending packet: $vKill;53c5#3d...Packet received: OK^M
Packet vKill (kill) is supported^M
Sending packet: $vFile:close:6#b6...Packet received: F0^M
Sending packet: $vFile:close:3#b3...Packet received: F0^M
Starting program: /scratch/yao/gdb/build-git/x86_64/gdb/testsuite/gdb.server/ext-restart ^M
Sending packet: $QDisableRandomization:1#cf...Packet received: OK^M
Sending packet: $R0#82...Sending packet: $qC#b4...Packet received: QCp53c5.53c5^M  <-- [1]
Sending packet: $qAttached:53c5#c9...Packet received: E01^M
warning: Remote failure reply: E01^M
....
0x00002aaaaaaac2d0 in ?? () from target:/lib64/ld-linux-x86-64.so.2^M
/home/yao/SourceCode/gnu/gdb/git/gdb/thread.c:88: internal-error: inferior_thread: Assertion `tp' failed.^M
A problem internal to GDB has been detected,^M
further debugging may prove unreliable.^M
Quit this debugging session? (y or n) FAIL: gdb.server/ext-restart.exp: run to main (GDB internal error)
Resyncing due to internal error.

the test is to restart the program, to make sure GDBserver handles
packet 'R' correctly.  From the GDBserver output, we can see,

 Remote debugging from host 127.0.0.1^M
 Process /scratch/yao/gdb/build-git/x86_64/gdb/testsuite/gdb.server/ext-restart created; pid = 21445^M
 GDBserver restarting^M
 Process /scratch/yao/gdb/build-git/x86_64/gdb/testsuite/gdb.server/ext-restart created; pid = 21446^M
 Killing process(es): 21446

we first start process 21445(0x53c5), kill it and restart a new process
21446.  However, in the gdb output above [1], we can see that the reply
of qC is still the old process id rather than the new one.  Looks
general_thread isn't up to date after GDBserver receives R packet.
This patch is to update general_thread after call start_inferior.

gdb/gdbserver:

2015-07-24  Yao Qi  <yao.qi@linaro.org>

	* server.c (process_serial_event): Set general_thread.

gdb/testsuite:

2015-07-24  Yao Qi  <yao.qi@linaro.org>

	* gdb.server/ext-restart.exp: New file.


^ permalink raw reply	[flat|nested] 264+ messages in thread
* [binutils-gdb] Test --wrapper in extended-remote
@ 2015-07-24 13:53 sergiodj+buildbot
  2015-07-24 17:26 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-07-24 13:53 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8cfe207c9fcfcf940ec8eb834afde41432ec6d80 ***

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

Test --wrapper in extended-remote
We didn't test --wrapper option in extended-remote before, this patch
is to add a test case for it.  In order to pass option --wrapper to
gdbserver in extended-remote, I add arg in gdbserver_start_extended,
and its default value is "", so that other places use
gdbserver_start_extended don't have to be updated.

gdb/testsuite:

2015-07-24  Yao Qi  <yao.qi@linaro.org>

	* lib/gdbserver-support.exp (gdbserver_start_extended): Add
	argument options.
	* gdb.server/ext-wrapper.exp: New file.


^ permalink raw reply	[flat|nested] 264+ messages in thread
* [binutils-gdb] Correct reloc section name
@ 2015-07-24  6:38 sergiodj+buildbot
  2015-07-24 13:00 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-07-24  6:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 91cb26dac47265f178fb6635f1deebdfd244572a ***

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

Correct reloc section name
	* elf.c (_bfd_elf_assign_file_positions_for_non_load): Use .rela
	prefix for reloc section corresponding to rela section associated
	with renamed debug section.


^ permalink raw reply	[flat|nested] 264+ messages in thread
* [binutils-gdb] bfd_get_section_by_name_if hash chain traversal
@ 2015-07-24  6:05 sergiodj+buildbot
  2015-07-24  9:23 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ 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-24  1:38 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ messages in thread
* [binutils-gdb] Fix crash when reading dummy CUs.
@ 2015-07-23 16:45 sergiodj+buildbot
  2015-07-23 20:05 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ 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 14:20 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ 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 13:40 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ 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 10:50 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ messages in thread
* [binutils-gdb] Fix ubsan signed integer overflow
@ 2015-07-23  3:33 sergiodj+buildbot
  2015-07-23  7:01 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-07-23  3:33 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 070fe95d07c78349f0c8f0fa90aeb92d05248483 ***

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

Fix ubsan signed integer overflow
IMO a fairly useless warning in this case, but technically correct.

	PR 18708
	* i386-dis.c (get64): Avoid signed integer overflow.


^ permalink raw reply	[flat|nested] 264+ messages in thread
* [binutils-gdb] Fix memory operand size for vcvtt?ps2u?qq instructions
@ 2015-07-22 20:38 sergiodj+buildbot
  2015-07-23  0:07 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-07-22 20:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 20c2a615876bdf0d5dc8e2db86eea1312d9dc9b8 ***

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

Fix memory operand size for vcvtt?ps2u?qq instructions
When disassembling AVX512 vcvtt?ps2u?q instructions with data
broadcasting enabled, memory operand size should be DWORD.

gas/testsuite/

	PR binutils/18631
	* gas/i386avx512dq-intel.d: Replace "QWORD" with "DWORD" in
	vcvtt?ps2u?qq instructions disassembly regexes.
	Add disassembly regex for new test.
	* gas/i386/avx512dq.d: Likewise.
	* gas/i386/avx512dq_vl-intel.d: Likewise.
	* gas/i386/avx512dq_vl.d: Likewise.
	* gas/i386/x86-64-avx512dq-intel.d: Likewise.
	* gas/i386/x86-64-avx512dq.d: Likewise.
	* gas/i386/x86-64-avx512dq_vl-intel.d: Likewise.
	* gas/i386/x86-64-avx512dq_vl.d: Likewise.
	* gas/i386/avx512dq.s: Add new test for Intel syntax with memory
	operand and broadcasting enabled.
	* gas/i386/avx512dq_vl.s: Likewise.
	* gas/i386/x86-64-avx512dq.s: Likewise.
	* gas/i386/x86-64-avx512dq_vl.s: Likewise.

opcodes/

	PR binutils/18631
	* i386-dis-evex.h (EVEX_W_0F78_P_2): Replace "EXxmmq" with
	"EXEvexHalfBcstXmmq" for the second operand.
	(EVEX_W_0F79_P_2): Likewise.
	(EVEX_W_0F7A_P_2): Likewise.
	(EVEX_W_0F7B_P_2): Likewise.


^ permalink raw reply	[flat|nested] 264+ messages in thread
* [binutils-gdb] Fix ppc64 ELFv1 assertion failure
@ 2015-07-22 10:11 sergiodj+buildbot
  2015-07-22 12:33 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ 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 21:36 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ messages in thread
* [binutils-gdb] btrace: fix case label in btrace_data_append
@ 2015-07-21 12:11 sergiodj+buildbot
  2015-07-21 16:01 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ messages in thread
* [binutils-gdb] [ARM] Support correctly spelled ARMv6KZ architecture names
@ 2015-07-21  8:54 sergiodj+buildbot
  2015-07-21 12:23 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-07-21  8:54 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f33026a96558ba9231ad91eb989ea6f347a15899 ***

Author: Matthew Wahab <matthew.wahab@arm.com>
Branch: master
Commit: f33026a96558ba9231ad91eb989ea6f347a15899

[ARM] Support correctly spelled ARMv6KZ architecture names
2015-07-20  Matthew Wahab  <matthew.wahab@arm.com>

gas/
    * NEWS: Mention corrected spelling of armv6kz.
    * config/tc-arm.c (arm_cpus): Replace ARM_ARCH_V6ZK with
    ARM_ARCH_V6KZ.
    (arm_archs): Likewise. Also add "armv6kz" and "armv6kzt2".
    * doc/c-arm.texi: Replace "armv6zk" with "armv6kz".

gas/testsuite

    * gas/arm/attr-march-armv6kz.d: New.
    * gas/arm/attr-march-armv6kzt2.d: New.

include/opcode

    * arm.h (ARM_AEXT_V6ZK): Rename to ARM_AEXT_V6KZ.
    (ARM_AEXT_V6ZKT2): Rename to ARM_AEXT_V6KZT2.
    (ARM_ARCH_V6ZK): Rename to ARM_ARCH_V6KZ.
    (ARM_ARCH_V6ZKT2): Rename to ARM_ARCH_V6KZT2.


^ permalink raw reply	[flat|nested] 264+ messages in thread
* [binutils-gdb] gdb.ada/info_exc.exp: Adjust expected output in "info exception" test.
@ 2015-07-20 22:38 sergiodj+buildbot
  2015-07-21  1:51 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-07-20 22:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8b558f797a3a63aaa8de119ddf53c8afdd1dc6eb ***

Author: Joel Brobecker <brobecker@adacore.com>
Branch: master
Commit: 8b558f797a3a63aaa8de119ddf53c8afdd1dc6eb

gdb.ada/info_exc.exp: Adjust expected output in "info exception" test.
Since multi_line was moved to gdb.exp in a slightly stricter form,
The gdb.ada/info_exc.exp:info exceptions test has been failing.
This is because it now expects a new-line sequence at the end of
each argument given to multi_line, including ".*". But the intent
when writing the test was to signify "could-be-nothing-at-all".
As a result, the test fails on x86_64-linux with a runtime built as
recommended, because of that
extra new-line sequence.

gdb/testsuite/ChangeLog:

        * gdb.ada/info_exc.exp: Adjust "info exceptions" expected output.


^ permalink raw reply	[flat|nested] 264+ messages in thread
* [binutils-gdb] Fix ARI warnings to nat/aarch64-linux-hw-point.{c,h}
@ 2015-07-20 16:00 sergiodj+buildbot
  2015-07-20 16:44 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-07-20 16:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3675a06a823132663f7c2376796c5345032fddad ***

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

Fix ARI warnings to nat/aarch64-linux-hw-point.{c,h}
This patch is to fix two ARI warnings for nat/aarch64-linux-hw-point.{c,h}.

gdb:

2015-07-20  Yao Qi  <yao.qi@linaro.org>

	* nat/aarch64-linux-hw-point.c (aarch64_handle_unaligned_watchpoint):
	Re-indent the code.
	* nat/aarch64-linux-hw-point.h: Use ULONGEST rather than
	"unsigned long long".


^ permalink raw reply	[flat|nested] 264+ messages in thread
* [binutils-gdb] Make binutils abort message GDB friendly
@ 2015-07-20 13:07 sergiodj+buildbot
  2015-07-20 15:54 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ messages in thread
* [binutils-gdb] Regen two files
@ 2015-07-20  5:16 sergiodj+buildbot
  2015-07-20  7:58 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-07-20  5:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f2d7e0f45023ef1b469c627aff02ead3697b1240 ***

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

Regen two files
bfd/
	* po/SRC-POTFILES.in: Regenerate.
binutils/
	* doc/Makefile.in: Regenerate.


^ permalink raw reply	[flat|nested] 264+ 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-19 11:20 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ messages in thread
* [binutils-gdb] Move common aarch64 HW breakpoint/watchpoint code to nat/
@ 2015-07-17 15:21 sergiodj+buildbot
  2015-07-19  8:29 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ messages in thread
* [binutils-gdb] Pass aarch64_debug_reg_state to functions
@ 2015-07-17 14:57 sergiodj+buildbot
  2015-07-19  5:40 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ messages in thread
* [binutils-gdb] Use debug_printf to print debug message
@ 2015-07-17 14:32 sergiodj+buildbot
  2015-07-19  2:49 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-07-17 14:32 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 25abf97969e50190cb5532b25b8e1deef3ab3bde ***

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

Use debug_printf to print debug message
Some functions in aarch64-linux-nat.c and linux-aarch64-low.c looks
the same except for the code printing debug message.  In GDB, we use
fprintf_unfiltered (gdb_stdlog, ...) while in GDBserver, we use
fprintf (stderr, ...).  This patch is to change them to use debug_printf
so that these functions are the same, and I can move them to a common
place in the following patch.

gdb:

2015-07-17  Yao Qi  <yao.qi@linaro.org>

	* aarch64-linux-nat.c (aarch64_show_debug_reg_state): Use
	debug_printf.
	(aarch64_handle_unaligned_watchpoint): Likewise.

gdb/gdbserver:

2015-07-17  Yao Qi  <yao.qi@linaro.org>

	* linux-aarch64-low.c (aarch64_show_debug_reg_state): Use
	debug_printf.
	(aarch64_handle_unaligned_watchpoint): Likewise.


^ permalink raw reply	[flat|nested] 264+ messages in thread
* [binutils-gdb] int -> enum target_hw_bp_type in aarch64-linux-nat.c
@ 2015-07-17 13:56 sergiodj+buildbot
  2015-07-18 23:58 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-07-17 13:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2ecd81c23cd070cb66073f726bddf2a7083bdaf1 ***

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

int -> enum target_hw_bp_type in aarch64-linux-nat.c
This patch is to use 'enum target_hw_bp_type' instead of int for
breakpoint type, in order to make some functions in GDB and
GDBserver looks similar.

gdb:

2015-07-17  Yao Qi  <yao.qi@linaro.org>

	* aarch64-linux-nat.c (aarch64_dr_state_insert_one_point): Change
	argument type's type to 'enum target_hw_bp_type'.
	(aarch64_dr_state_remove_one_point): Likewise.
	(aarch64_handle_breakpoint): Likewise.
	(aarch64_linux_insert_hw_breakpoint): Likewise.
	(aarch64_linux_remove_hw_breakpoint): Likewise.
	(aarch64_handle_aligned_watchpoint): Likewise.


^ permalink raw reply	[flat|nested] 264+ messages in thread
* [binutils-gdb] Call ptid_get_pid instead of get_thread_id in aarch64_linux_get_debug_reg_capacity
@ 2015-07-17 13:16 sergiodj+buildbot
  2015-07-18 21:08 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-07-17 13:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e53b69389a7d743fe888926475d46167e91b1157 ***

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

Call ptid_get_pid instead of get_thread_id in aarch64_linux_get_debug_reg_capacity
aarch64_linux_get_debug_reg_capacity is called by
aarch64_linux_child_post_startup_inferior, and argument ptid is created in
inf-ptrace.c:inf_ptrace_create_inferior,

  /* On some targets, there must be some explicit actions taken after
     the inferior has been started up.  */
  target_post_startup_inferior (pid_to_ptid (pid));

so in aarch64_linux_get_debug_reg_capacity, we can get pid by ptid_get_pid,
and don't need to use get_thread_id.

gdb:

2015-07-17  Yao Qi  <yao.qi@linaro.org>

	* aarch64-linux-nat.c (aarch64_linux_get_debug_reg_capacity): Call
	ptid_get_pid instead of get_thread_id.


^ permalink raw reply	[flat|nested] 264+ messages in thread
* [binutils-gdb] [AArch64] Sort TLS reloc types alphabetically
@ 2015-07-17 12:23 sergiodj+buildbot
  2015-07-18 18:17 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-07-17 12:23 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4c0a9a6fa1c43e727e8de9ede87df7c21bd8500f ***

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

[AArch64] Sort TLS reloc types alphabetically


^ permalink raw reply	[flat|nested] 264+ messages in thread
* [binutils-gdb] Fix using uninitialised values
@ 2015-07-17 11:35 sergiodj+buildbot
  2015-07-18 15:27 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ messages in thread
* [binutils-gdb] Fix gdb.arch/i386-biarch-core.exp FAIL on i386.
@ 2015-07-16 16:29 sergiodj+buildbot
  2015-07-18 12:38 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-07-16 16:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 775a3298dca48e76e29045912e08025abacafa94 ***

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

Fix gdb.arch/i386-biarch-core.exp FAIL on i386.
This new test fails on i686 buildbot slaves,

(gdb) core-file /home/gdb-buildbot-2/fedora-x86-64-2/fedora-i686/build/gdb/testsuite/gdb.arch/i386-biarch-core.core
"/home/gdb-buildbot-2/fedora-x86-64-2/fedora-i686/build/gdb/testsuite/gdb.arch/i386-biarch-core.core"
is not a core dump: File format not recognized
(gdb) FAIL: gdb.arch/i386-biarch-core.exp: core-file

There are two problems:

(1) The testcase did not really test if elf64-i386 is supported by GDB (BFD).
That was OK for a Fedora testcase but I forgot about it when submitting it
upstream.

I haven't really verified if the GNU target is elf64-little but it seems so,
no other one seems suitable from:
	elf32-x86-64
	elf64-big
	elf64-k1om
	elf64-l1om
	elf64-little
	elf64-x86-64
	pei-x86-64

(2) The output of the "core-file" command itself can be arbitrary as the
elf64-i386 file with x86_64 registers is really broken; but that does not
matter much, important is the following test whether core file memory is
readable.
	./configure --enable-64-bit-bfd
	(gdb) core-file /home/jkratoch/redhat/gdb-test-build32-plus64/gdb/testsuite/gdb.arch/i386-biarch-core.core^M
	warning: Couldn't find general-purpose registers in core file.^M
	Failed to read a valid object file image from memory.^M
	warning: Couldn't find general-purpose registers in core file.^M
	#0  <unavailable> in ?? ()^M
	(gdb) FAIL: gdb.arch/i386-biarch-core.exp: core-file
	x/i 0x400078^M
	   0x400078:    hlt    ^M
	(gdb) PASS: gdb.arch/i386-biarch-core.exp: .text is readable

I do not know much dejagnu but I expect 'istarget' tests against the site.exp
'target_triplet' content which is set to the primary GDB target
(--target=...).

GDB is normally never configured for primary target elf64-i386, I think BFD
does not know such explicit target, it gets recognized as elf64-little.

In fact many testfiles of the GDB testsuite are wrong as they require
'istarget' (therefore primary GDB target) even for just loading arch specific
files which would be sufficient with secondary target (--enable-targets=...)
support.

This my new patch removes this 'istarget' check as it is IMO unrelated to what
we need to test.  Although you are right we do 'x/i' and test for 'hlt' so
I think we should test also for available 'set architecture i386'.
We could also test by 'x/bx' instead of 'x/i' to avoid such additional
test/requirement.

This testcase comes from a different bug from 2009:
	https://bugzilla.redhat.com/show_bug.cgi?id=457187
	http://pkgs.fedoraproject.org/cgit/gdb.git/commit/?id=94cd124608bf0dd359cb48a710800d72c21b30c3

That bug has been fixed in the meantime but the same testcase was reproducing
this new different bug - internal error regression - so I submitted it.

We can remove the "x/bx $address" test but it was useful for the previous bug
from 2009 as that time the internal error regression did not happen, just the
core file was not recognized (which would not be detected by the proposed
ignoring of the "core-file" command output) and so the core file was not
available.  That can be tested by the "x/bx $address" test.

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

	* gdb.arch/i386-biarch-core.exp: Replace istarget
	by "complete set gnutarget". Remove expectation for the "core-file"
	command.


^ permalink raw reply	[flat|nested] 264+ messages in thread
* [binutils-gdb] Updates the ARM disassembler's output of floating point constants to include the actual floating point value.
@ 2015-07-16 16:08 sergiodj+buildbot
  2015-07-18  9:48 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-07-16 16:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6f1c2142595b1ec203a7da998b2155403a433e89 ***

Author: Alessandro Marzocchi <alessandro.marzocchi@gmail.com>
Branch: master
Commit: 6f1c2142595b1ec203a7da998b2155403a433e89

Updates the ARM disassembler's output of floating point constants to include the actual floating point value.
opcodes	* arm-dis.c (print_insn_coprocessor): Added support for quarter
	float bitfield format.
	(coprocessor_opcodes): Changed VFP vmov reg,immediate to use new
	quarter float bitfield format.

tests	* gas/arm/vfpv3-const-conv.d: Update expected result due to change
	of comment for vmov reg,immediate with VFP coprocessor.


^ permalink raw reply	[flat|nested] 264+ 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-18  4:08 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ messages in thread
* [binutils-gdb] [AArch64] Mark single precision pseudo registers unavailable if invalid
@ 2015-07-16  9:32 sergiodj+buildbot
  2015-07-17 22:27 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-07-16  9:32 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4bcddaceb01a5ece549b2d807166b5e050801f5a ***

Author: Pierre Langlois <pierre.langlois@arm.com>
Branch: master
Commit: 4bcddaceb01a5ece549b2d807166b5e050801f5a

[AArch64] Mark single precision pseudo registers unavailable if invalid
I noticed two failure in gdb.trace/mi-trace-frame-collected.exp:

FAIL: gdb.trace/mi-trace-frame-collected.exp: live:
  -trace-frame-collected (register)
FAIL: gdb.trace/mi-trace-frame-collected.exp: tfile:
  -trace-frame-collected (register)

In these cases, we are not collecting registers so the MI command
-trace-frame-collected should only give us the value of the PC.
However, it also gives us all of the single precision pseudo registers,
initialized with 0x0.

We can reproduce this error by simply issuing the
'maint print cooked-register' when no inferior is connected:

~~~
...
(gdb) maint print cooked-register
 Name         Nr  Rel Offset    Size  Type            Cooked value
 x0            0    0      0       8 long            <unavailable>
 x1            1    1      8       8 long            <unavailable>
 ...
 d30         130   62   1540       8 *1              <unavailable>
 d31         131   63   1548       8 *1              <unavailable>
 s0          132   64   1556       4 *1              0x00000000
 s1          133   65   1560       4 *1              0x00000000
 s2          134   66   1564       4 *1              0x00000000
 ...
 s28         160   92   1668       4 *1              0x00000000
 s29         161   93   1672       4 *1              0x00000000
 s30         162   94   1676       4 *1              0x00000000
 s31         163   95   1680       4 *1              0x00000000
 h0          164   96   1684       2 *1              <unavailable>
 h1          165   97   1686       2 *1              <unavailable>
 h2          166   98   1688       2 *1              <unavailable>
 ...
~~~

It turns out GDB does not check if S registers are valid before returning
a value for them.  It should return <unavailable> in this case.

gdb/ChangeLog:

	* aarch64-tdep.c (aarch64_pseudo_read_value): Mark S register as
	unavailable if invalid.


^ permalink raw reply	[flat|nested] 264+ messages in thread
* [binutils-gdb] Revert the previous 7 commits of: Validate binary before use
@ 2015-07-15 18:40 sergiodj+buildbot
  2015-07-17 19:36 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-07-15 18:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT db1ff28b60f8886b8d7c634f1db2f939ba47a13c ***

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

Revert the previous 7 commits of: Validate binary before use
ddc98fbf2fd9e244a215a4d09e559180dc573a14 Create empty nat/linux-maps.[ch] and common/target-utils.[ch]
6e5b4429db0d66e2d0b27e1bcfe4709f3dae73ed Move gdb_regex* to common/
f7af1fcd759fa126612018a5916cf808df7bb8bc Prepare linux_find_memory_regions_full & co. for move
9904185cfde13d6c6849f1f042c8e3b74974cf08 Move linux_find_memory_regions_full & co.
700ca40f6fc1addd7238f4ab57f76c095ad3c99f gdbserver build-id attribute generator
ca5268b6be265580b91ef75c1a1a9815f581ae42 Validate symbol file using build-id
0a94970d663a053c523f23ac0d71deb25a77f709 Tests for validate symbol file using build-id

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

	Revert the previous 6 commits:
	Create empty nat/linux-maps.[ch] and common/target-utils.[ch].
	Move gdb_regex* to common/
	Prepare linux_find_memory_regions_full & co. for move
	Move linux_find_memory_regions_full & co.
	gdbserver build-id attribute generator
	Validate symbol file using build-id

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

	Revert the previous 3 commits:
	Move gdb_regex* to common/
	Move linux_find_memory_regions_full & co.
	gdbserver build-id attribute generator

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

	Revert the previous 2 commits:
	gdbserver build-id attribute generator
	Validate symbol file using build-id

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

	Revert the previous commit:
	Tests for validate symbol file using build-id.


^ permalink raw reply	[flat|nested] 264+ messages in thread
* [binutils-gdb] Tests for validate symbol file using build-id
@ 2015-07-15 18:01 sergiodj+buildbot
  2015-07-17 13:59 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-07-15 18:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0a94970d663a053c523f23ac0d71deb25a77f709 ***

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

Tests for validate symbol file using build-id
New testcase.

gdb/testsuite/ChangeLog
2015-07-15  Aleksandar Ristovski  <aristovski@qnx.com

	Tests for validate symbol file using build-id.
	* gdb.base/solib-mismatch-lib.c: New file.
	* gdb.base/solib-mismatch-libmod.c: New file.
	* gdb.base/solib-mismatch.c: New file.
	* gdb.base/solib-mismatch.exp: New file.


^ permalink raw reply	[flat|nested] 264+ messages in thread
* [binutils-gdb] Validate symbol file using build-id
@ 2015-07-15 17:53 sergiodj+buildbot
  2015-07-17 13:22 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-07-15 17:53 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ca5268b6be265580b91ef75c1a1a9815f581ae42 ***

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

Validate symbol file using build-id
Consumer part of the "build-id" attribute.

gdb/ChangeLog
2015-07-15  Aleksandar Ristovski  <aristovski@qnx.com
	    Jan Kratochvil  <jan.kratochvil@redhat.com>

	Validate symbol file using build-id.
	* NEWS (Changes since GDB 7.10): Add 'set validate-build-id'
	and 'show validate-build-id'.  Add build-id attribute.
	* solib-darwin.c (_initialize_darwin_solib): Assign validate value.
	* solib-dsbt.c (_initialize_dsbt_solib): Ditto.
	* solib-frv.c (_initialize_frv_solib): Ditto.
	* solib-spu.c (set_spu_solib_ops): Ditto.
	* solib-svr4.c: Include rsp-low.h.
	(NOTE_GNU_BUILD_ID_NAME): New define.
	(svr4_validate): New function.
	(svr4_copy_library_list): Duplicate field build_id.
	(library_list_start_library): Parse 'build-id' attribute.
	(svr4_library_attributes): Add 'build-id' attribute.
	(_initialize_svr4_solib): Assign validate value.
	* solib-target.c (solib.h): Include.
	(_initialize_solib_target): Assign validate value.
	* solib.c (validate_build_id, show_validate_build_id): New.
	(solib_map_sections): Use ops->validate.
	(clear_so): Free build_id.
	(default_solib_validate): New function.
	(_initialize_solib): Add "validate-build-id".
	* solib.h (default_solib_validate): New declaration.
	* solist.h (struct so_list): New fields 'build_idsz' and 'build_id'.
	(target_so_ops): New field 'validate'.

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

	* gdb.texinfo (Files): Add 'set validate-build-id'
	and 'show validate-build-id'.


^ permalink raw reply	[flat|nested] 264+ messages in thread
* [binutils-gdb] gdbserver build-id attribute generator
@ 2015-07-15 17:35 sergiodj+buildbot
  2015-07-17 12:00 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-07-15 17:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 700ca40f6fc1addd7238f4ab57f76c095ad3c99f ***

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

gdbserver build-id attribute generator
Producer part of the new "build-id" XML attribute.

gdb/ChangeLog
2015-07-15  Aleksandar Ristovski  <aristovski@qnx.com
	    Jan Kratochvil  <jan.kratochvil@redhat.com>

	gdbserver build-id attribute generator.
	* features/library-list-svr4.dtd (library-list-svr4): New
	'build-id' attribute.

gdb/doc/ChangeLog
2015-07-15  Aleksandar Ristovski  <aristovski@qnx.com
	    Jan Kratochvil  <jan.kratochvil@redhat.com>

	gdbserver build-id attribute generator.
	* gdb.texinfo (Library List Format for SVR4 Targets): Add
	'build-id' in description, example, new attribute in dtd.

gdb/gdbserver/ChangeLog
2015-07-15  Aleksandar Ristovski  <aristovski@qnx.com
	    Jan Kratochvil  <jan.kratochvil@redhat.com>

	gdbserver build-id attribute generator.
	* linux-low.c (nat/linux-maps.h, search.h, rsp-low.h): Include.
	(ElfXX_Ehdr, ElfXX_Phdr, ElfXX_Nhdr): New.
	(ELFXX_FLD, ELFXX_SIZEOF, ELFXX_ROUNDUP, BUILD_ID_INVALID): New.
	(find_phdr): New.
	(get_dynamic): Use find_pdhr to traverse program headers.
	(struct mapping_entry, mapping_entry_s, free_mapping_entry_vec)
	(compare_mapping_entry_range, struct find_memory_region_callback_data)
	(read_build_id, find_memory_region_callback, lrfind_mapping_entry)
	(get_hex_build_id): New.
	(linux_qxfer_libraries_svr4): Add optional build-id attribute
	to reply XML document.


^ permalink raw reply	[flat|nested] 264+ messages in thread
* [binutils-gdb] Move linux_find_memory_regions_full & co.
@ 2015-07-15 17:14 sergiodj+buildbot
  2015-07-17 10:39 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-07-15 17:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9904185cfde13d6c6849f1f042c8e3b74974cf08 ***

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

Move linux_find_memory_regions_full & co.
This should be just a move with no changes.

gdb/ChangeLog
2015-07-15  Aleksandar Ristovski  <aristovski@qnx.com
	    Jan Kratochvil  <jan.kratochvil@redhat.com>

	Move linux_find_memory_regions_full & co.
	* linux-tdep.c (nat/linux-maps.h): Include.
	(gdb_regex.h): Remove the include.
	(enum filterflags, struct smaps_vmflags, read_mapping, decode_vmflags)
	(mapping_is_anonymous_p, dump_mapping_p): Moved to nat/linux-maps.c.
	(linux_find_memory_region_ftype): Moved typedef to nat/linux-maps.h.
	(linux_find_memory_regions_full): Moved definition to nat/linux-maps.c.
	* nat/linux-maps.c: Include ctype.h, target/target-utils.h, gdb_regex.h
	and target/target.h.
	(struct smaps_vmflags, read_mapping, decode_vmflags)
	(mapping_is_anonymous_p, dump_mapping_p): Move from linux-tdep.c.
	(linux_find_memory_regions_full): Move from linux-tdep.c.
	* nat/linux-maps.h (read_mapping): New declaration.
	(linux_find_memory_region_ftype, enum filterflags): Moved from
	linux-tdep.c.
	(linux_find_memory_regions_full): New declaration.
	* target.c (target/target-utils.h): Include.
	(read_alloc_pread_ftype): Moved typedef to target/target-utils.h.
	(read_alloc, read_stralloc_func_ftype, read_stralloc): Moved
	definitions to target/target-utils.c.
	* target.h (target_fileio_read_stralloc): Move it to target/target.h.
	* target/target-utils.c (read_alloc, read_stralloc): Move definitions
	from target.c.
	* target/target-utils.h (read_alloc_pread_ftype): New typedef.
	(read_alloc): New declaration.
	(read_stralloc_func_ftype): New typedef.
	(read_stralloc): New declaration.
	* target/target.h (target_fileio_read_stralloc): Move it from target.h.

gdb/gdbserver/ChangeLog
2015-07-15  Aleksandar Ristovski  <aristovski@qnx.com
	    Jan Kratochvil  <jan.kratochvil@redhat.com>

	* target.c: Include target/target-utils.h and fcntl.h.
	(target_fileio_read_stralloc_1_pread, target_fileio_read_stralloc_1)
	(target_fileio_read_stralloc): New functions.


^ permalink raw reply	[flat|nested] 264+ messages in thread
* [binutils-gdb] Prepare linux_find_memory_regions_full & co. for move
@ 2015-07-15 16:55 sergiodj+buildbot
  2015-07-17  9:17 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-07-15 16:55 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f7af1fcd759fa126612018a5916cf808df7bb8bc ***

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

Prepare linux_find_memory_regions_full & co. for move
Prepare code for move into gdb/common/.

gdb/ChangeLog
2015-07-15  Aleksandar Ristovski  <aristovski@qnx.com
	    Jan Kratochvil  <jan.kratochvil@redhat.com>

	Prepare linux_find_memory_regions_full & co. for move.
	* linux-tdep.c (linux_find_memory_region_ftype): Comment.
	(linux_find_memory_regions_full): Change signature and prepare
	for moving to linux-maps.
	(linux_find_memory_regions_data): Rename field 'obfd' to 'data'.
	(linux_find_memory_regions_thunk): New.
	(linux_find_memory_regions_thunk): Use 'data' field instead of 'obfd'.
	(linux_find_memory_regions_gdb): New.
	(linux_find_memory_regions): Rename argument 'obfd' to 'func_data'.
	(linux_make_mappings_corefile_notes): Use
	linux_find_memory_regions_gdb.
	* target.c (read_alloc_pread_ftype): New typedef.
	(target_fileio_read_alloc_1_pread): New function.
	(read_alloc): Refactor from target_fileio_read_alloc_1.
	(read_stralloc_func_ftype): New typedef.
	(target_fileio_read_alloc_1): New implementation. Use read_alloc.
	(read_stralloc): Refactored from target_fileio_read_stralloc.
	(target_fileio_read_stralloc): New implementation, use read_stralloc.


^ permalink raw reply	[flat|nested] 264+ messages in thread
* [binutils-gdb] Create empty nat/linux-maps.[ch] and common/target-utils.[ch]
@ 2015-07-15 16:15 sergiodj+buildbot
  2015-07-17  3:36 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-07-15 16:15 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ddc98fbf2fd9e244a215a4d09e559180dc573a14 ***

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

Create empty nat/linux-maps.[ch] and common/target-utils.[ch]
Prepare new files for later move.

gdb/ChangeLog
2015-07-15  Aleksandar Ristovski  <aristovski@qnx.com
	    Jan Kratochvil  <jan.kratochvil@redhat.com>

	Create empty nat/linux-maps.[ch] and common/target-utils.[ch].
	* Makefile.in (HFILES_NO_SRCDIR); Add nat/linux-maps.h,
	common/target-utils.h.
	(COMMON_OBS): Add target-utils.o.
	(linux-maps.o, target-utils.o): New.
	* target/target-utils.c: New file.
	* target/target-utils.h: New file.
	* config/i386/linux.mh (NATDEPFILES): Add linux-maps.o.
	* config/i386/linux64.mh (NATDEPFILES): Ditto.
	* nat/linux-maps.c: New file.
	* nat/linux-maps.h: New file.

gdb/gdbserver/ChangeLog
2015-07-15  Aleksandar Ristovski  <aristovski@qnx.com
	    Jan Kratochvil  <jan.kratochvil@redhat.com>

	Create empty nat/linux-maps.[ch] and common/target-utils.[ch].
	* Makefile.in (OBS): Add target-utils.o.
	(linux-maps.o, target-utils.o): New.
	* configure.srv (srv_linux_obj): Add linux-maps.o.


^ permalink raw reply	[flat|nested] 264+ messages in thread
* [binutils-gdb] ari, btrace: avoid unsigned long long
@ 2015-07-15  6:52 sergiodj+buildbot
  2015-07-16 16:15 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ messages in thread
* [binutils-gdb] Remove CHECK_TYPEDEF, use check_typedef instead
@ 2015-07-14 21:08 sergiodj+buildbot
  2015-07-16 13:24 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ messages in thread
* [binutils-gdb] Add support reading D modules from DWARF
@ 2015-07-14 19:13 sergiodj+buildbot
  2015-07-16 10:33 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-07-14 19:13 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 452802827f0870df0c8ece81a7e098d94cee4536 ***

Author: Iain Buclaw <ibuclaw@gdcproject.org>
Branch: master
Commit: 452802827f0870df0c8ece81a7e098d94cee4536

Add support reading D modules from DWARF
Extends existing support for namespaces/modules in C++/Fortran/Java to
include language_d too.  However unlike Fortran/C++, the separator for
qualified names is a single dot.

2015-07-14  Iain Buclaw  <ibuclaw@gdcproject.org>

	* dwarf2read.c (find_slot_in_mapped_hash): Extend language support to
	also test for language_d.
	(dwarf2_compute_name): Likewise.
	(read_func_scope): Likewise.
	(read_structure_type): Likewise.
	(determine_prefix): Likewise.
	(read_import_statement): Use dot as the separator for language_d.
	(typename_concat): Likewise, but don't prefix the D main function.


^ permalink raw reply	[flat|nested] 264+ messages in thread
* [binutils-gdb] i386-biarch-core.exp: Fix comment typo
@ 2015-07-14 18:50 sergiodj+buildbot
  2015-07-16  7:42 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-07-14 18:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cfa68bae4271a51a4402f8ca7ccdc014be95d79d ***

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

i386-biarch-core.exp: Fix comment typo
gdb/testsuite/ChangeLog
2015-07-14  Jan Kratochvil  <jan.kratochvil@redhat.com>

	* gdb.arch/i386-biarch-core.exp: Fix comment typo.


^ permalink raw reply	[flat|nested] 264+ messages in thread
* [binutils-gdb] Remove trailing spaces in demangle.h
@ 2015-07-14 17:29 sergiodj+buildbot
  2015-07-15 20:19 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ messages in thread
From: sergiodj+buildbot @ 2015-07-14 17:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1d83d382dea9b98d4aa4aa0083713447b83e0ba5 ***

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

Remove trailing spaces in demangle.h


^ permalink raw reply	[flat|nested] 264+ messages in thread
* [binutils-gdb] Sync config/warnings.m4 with GCC
@ 2015-07-14 16:05 sergiodj+buildbot
  2015-07-15  8:57 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 264+ 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] 264+ messages in thread

end of thread, other threads:[~2015-08-24 15:25 UTC | newest]

Thread overview: 264+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-07-28 16:24 [binutils-gdb] Consider addressable memory unit size in various value functions sergiodj+buildbot
2015-07-28 16:24 ` Failures on AIX-POWER7-plain, branch master sergiodj+buildbot
2015-07-28 16:44 ` Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot
2015-07-28 16:52 ` Failures on Fedora-i686, " sergiodj+buildbot
2015-07-28 17:13 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot
2015-07-28 17:17 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot
2015-07-28 17:23 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot
2015-07-28 19:54 ` Failures on Debian-MIPS-m64, " sergiodj+buildbot
2015-07-29  4:56 ` Failures on Debian-i686, " sergiodj+buildbot
2015-07-29  5:22 ` Failures on Debian-i686-native-gdbserver, " sergiodj+buildbot
2015-07-29  6:54 ` Failures on Debian-i686-native-extended-gdbserver, " sergiodj+buildbot
2015-07-29 17:57 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot
2015-07-29 18:53 ` Failures on Debian-x86_64-native-gdbserver-m64, " sergiodj+buildbot
2015-07-30 12:49 ` Failures on Fedora-ppc64be-cc-with-index, " sergiodj+buildbot
2015-07-30 13:10 ` Failures on Fedora-ppc64be-m64, " sergiodj+buildbot
2015-07-30 13:47 ` Failures on Fedora-ppc64be-native-extended-gdbserver-m64, " sergiodj+buildbot
2015-07-31  6:47 ` Failures on Fedora-ppc64le-native-extended-gdbserver-m64, " sergiodj+buildbot
2015-07-31  7:22 ` Failures on Fedora-ppc64le-native-gdbserver-m64, " sergiodj+buildbot
  -- strict thread matches above, loose matches on Subject: below --
2015-08-15 23:05 [binutils-gdb] objfiles.h,psympriv.h,psymtab.c: Whitespace sergiodj+buildbot
2015-08-24 15:25 ` Failures on Debian-MIPS-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-24 14:41 ` Failures on Debian-MIPS-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-24 10:56 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-08-15  4:59 [binutils-gdb] New /s modifier for the disassemble command sergiodj+buildbot
2015-08-24  9:57 ` Failures on Debian-MIPS-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-24  8:49 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-08-14 22:33 [binutils-gdb] Rename location accessor macro parameters to silence ARI sergiodj+buildbot
2015-08-24  8:46 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-08-14 21:57 [binutils-gdb] mi_make_breakpoint: add "evaluated-by" option sergiodj+buildbot
2015-08-24  5:02 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-08-14 20:00 [binutils-gdb] Fix ARI warnings in d-exp.y sergiodj+buildbot
2015-08-24  4:06 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-08-14 14:27 [binutils-gdb] Add support for DT_MIPS_RLD_MAP_REL sergiodj+buildbot
2015-08-24  0:22 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-08-14 12:24 [binutils-gdb] Add myself to gdb MAINTAINERS sergiodj+buildbot
2015-08-23 20:39 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-08-14  1:48 [binutils-gdb] Revert "Fix encoding or OpenRisk1000 PC relative relocations." sergiodj+buildbot
2015-08-23 16:56 ` Failures on Debian-MIPS-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-23 13:12 ` Failures on Debian-MIPS-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-23 12:10 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-08-13 18:46 [binutils-gdb] gdb.base/dso2dso.exp: Improve testcase documentation sergiodj+buildbot
2015-08-23  0:21 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-08-13 18:17 [binutils-gdb] Fix Python frame unwinder issue caught by Valgrind sergiodj+buildbot
2015-08-22 23:26 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-08-13 17:22 [binutils-gdb] Mass rename `explicit' -> `explicit_loc' sergiodj+buildbot
2015-08-22 22:21 ` Failures on Debian-MIPS-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-22 18:38 ` Failures on Debian-MIPS-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-22 14:55 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-08-13  7:47 [binutils-gdb] [Ada] Add support for subprogram renamings sergiodj+buildbot
2015-08-22 13:37 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-08-13  2:02 [binutils-gdb] gdb.base/dso2dso.exp sometimes broken sergiodj+buildbot
2015-08-22  9:53 ` Failures on Debian-MIPS-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-22  6:08 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-08-12 20:32 [binutils-gdb] [amd64] Invalid return address after displaced stepping sergiodj+buildbot
2015-08-22  2:24 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-08-12 18:48 [binutils-gdb] Initialize `location' in gdbpy_decode_line sergiodj+buildbot
2015-08-21 22:41 ` Failures on Debian-MIPS-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-21 21:32 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-08-12 16:23 [binutils-gdb] [MIPS] Map 'move' to 'or' sergiodj+buildbot
2015-08-21 17:48 ` Failures on Debian-MIPS-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-21 14:05 ` Failures on Debian-MIPS-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-21 10:22 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-08-12 12:58 [binutils-gdb] Sync ansidecl.h with GCC sergiodj+buildbot
2015-08-21  6:39 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-08-12 12:26 [binutils-gdb] Remove trailing spaces in opcodes sergiodj+buildbot
2015-08-21  2:55 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-08-12 11:58 [binutils-gdb] Remove trailing spaces in bfd sergiodj+buildbot
2015-08-20 23:12 ` Failures on Debian-MIPS-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-20 15:53 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
     [not found] <33ebda9d6841e18d9ef18b94c3dcad7d0498ab3d@gdb-build>
2015-08-12  7:29 ` sergiodj+buildbot
2015-08-12  5:48 [binutils-gdb] Properly skip IFUNC relocations in debug sections sergiodj+buildbot
2015-08-20 12:08 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-08-12  5:23 [binutils-gdb] Explicit locations: documentation updates sergiodj+buildbot
2015-08-20  8:24 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-08-12  4:59 [binutils-gdb] Explicit locations: MI support for explicit locations sergiodj+buildbot
2015-08-20  4:39 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-08-12  4:30 [binutils-gdb] Explicit locations: add UI features for CLI sergiodj+buildbot
2015-08-20  0:54 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-08-12  4:04 [binutils-gdb] Explicit locations: introduce explicit locations sergiodj+buildbot
2015-08-19 21:10 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-08-12  3:38 [binutils-gdb] Explicit locations: introduce probe locations sergiodj+buildbot
2015-08-19 17:25 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-08-12  3:12 [binutils-gdb] Explicit locations: introduce address locations sergiodj+buildbot
2015-08-19 13:42 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-08-12  2:47 [binutils-gdb] Explicit locations: use new location API sergiodj+buildbot
2015-08-19  9:58 ` Failures on Debian-MIPS-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-19  6:14 ` Failures on Debian-MIPS-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-19  2:30 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-08-12  1:26 [binutils-gdb] [AArch64] Improve BFD overflow warning message for -fpic sergiodj+buildbot
2015-08-18 22:47 ` Failures on Debian-MIPS-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-18 19:04 ` Failures on Debian-MIPS-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-18 15:20 ` Failures on Debian-MIPS-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-18 11:36 ` Failures on Debian-MIPS-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-18  7:54 ` Failures on Debian-MIPS-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-18  6:38 ` Failures on Debian-MIPS-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-18  5:37 ` Failures on Debian-MIPS-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-18  1:53 ` Failures on Debian-MIPS-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-17 22:10 ` Failures on Debian-MIPS-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-17 21:55 ` Failures on Debian-MIPS-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-17 20:43 ` Failures on Debian-MIPS-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-17 18:03 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-08-11 20:12 [binutils-gdb] Skip IFUNC relocations in debug sections sergiodj+buildbot
2015-08-17 14:18 ` Failures on Debian-MIPS-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-17 10:34 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-08-11 16:46 [binutils-gdb] Fix encoding or OpenRisk1000 PC relative relocations sergiodj+buildbot
2015-08-17  6:51 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-08-11 16:13 [binutils-gdb] Fix typo in coff-sh.c sergiodj+buildbot
2015-08-17  3:08 ` Failures on Debian-MIPS-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-16 23:25 ` Failures on Debian-MIPS-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-16 19:42 ` Failures on Debian-MIPS-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-16 16:01 ` Failures on Debian-MIPS-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-16 13:12 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-08-10 18:17 [binutils-gdb] gdb/infrun.c: Various trivial ARI fixes sergiodj+buildbot
2015-08-16 14:12 ` Failures on Debian-MIPS-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-16 14:42 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-08-10  8:27 [binutils-gdb] Add SIGRIE instruction for MIPS R6 sergiodj+buildbot
2015-08-16 14:42 ` Failures on Debian-MIPS-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-15 23:05 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-08-08  0:24 [binutils-gdb] native Linux: enable always non-stop by default sergiodj+buildbot
2015-08-15 19:22 ` Failures on Debian-MIPS-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-15 15:39 ` Failures on Debian-MIPS-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-15 11:57 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-08-07 23:02 [binutils-gdb] Disable displaced stepping if trying it fails sergiodj+buildbot
2015-08-15 11:33 ` Failures on Debian-MIPS-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-15 11:13 ` Failures on Debian-MIPS-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-15 10:30 ` Failures on Debian-MIPS-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-14 23:25 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-08-07 20:23 [binutils-gdb] Factor out code to re-resume stepped thread sergiodj+buildbot
2015-08-14 19:44 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-08-07 19:58 [binutils-gdb] Add comments to currently_stepping and target_resume sergiodj+buildbot
2015-08-14 15:44 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-08-07 19:35 [binutils-gdb] Misc switch_back_to_stepped_thread cleanups sergiodj+buildbot
2015-08-14 11:44 ` Failures on Debian-MIPS-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-14 10:51 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-08-07 18:22 [binutils-gdb] Make thread_still_needs_step_over consider stepping_over_watchpoint too sergiodj+buildbot
2015-08-14  7:11 ` Failures on Debian-MIPS-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-14  3:32 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-08-07 17:20 [binutils-gdb] Change adjust_pc_after_break's prototype sergiodj+buildbot
2015-08-13 23:54 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-08-07 16:54 [binutils-gdb] Fix and test "checkpoint" in non-stop mode sergiodj+buildbot
2015-08-13 20:16 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-08-07 15:44 [binutils-gdb] ignore invalid DOF provider sections sergiodj+buildbot
2015-08-13 16:36 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-08-07 12:17 [binutils-gdb] Properly merge hidden versioned symbol sergiodj+buildbot
2015-08-13  7:58 ` Failures on Debian-MIPS-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-13  6:42 ` Failures on Debian-MIPS-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-13  3:05 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-08-07  5:32 [binutils-gdb] Yaakov Selkowitz: fixes for in-tree libiconv sergiodj+buildbot
2015-08-12 16:11 ` Failures on Debian-MIPS-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-12 12:31 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-08-06 21:34 [binutils-gdb] Add casts for legitimate integer to enum conversions sergiodj+buildbot
2015-08-12  7:32 ` Failures on Debian-MIPS-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-12  3:51 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-08-06 17:22 [binutils-gdb] PR python/17136 sergiodj+buildbot
2015-08-12  1:46 ` Failures on Debian-MIPS-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-11 13:47 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-08-06 15:14 [binutils-gdb] Fix gdbserver --debug issues caught by Valgrind sergiodj+buildbot
2015-08-11 10:09 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-08-06 14:26 [binutils-gdb] Revert "test slowdown" sergiodj+buildbot
2015-08-11  7:40 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-08-06 14:00 [binutils-gdb] Test for PR18749: problems if whole process dies while (ptrace-) stopped sergiodj+buildbot
2015-08-11  7:24 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-08-06 13:20 [binutils-gdb] test slowdown sergiodj+buildbot
2015-08-11  6:40 ` Failures on Debian-MIPS-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-10  3:32 ` Failures on Debian-MIPS-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-09 23:55 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-08-05  8:03 [binutils-gdb] Remove get_thread_id sergiodj+buildbot
2015-08-09 13:06 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-08-04 17:08 [binutils-gdb] python: fix Linetable case to LineTable in docstrings and comments sergiodj+buildbot
2015-08-09  5:52 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-08-04 16:14 [binutils-gdb] Fix stack buffer overflows when parsing corrupt ihex files sergiodj+buildbot
2015-08-09  2:16 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-08-04 16:07 [binutils-gdb] Disable tracepoint support for aarch32 sergiodj+buildbot
2015-08-08 22:40 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-08-04 15:25 [binutils-gdb] Disable Z0 packet on aarch64 on multi-arch debugging sergiodj+buildbot
2015-08-08 22:01 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-08-04 15:09 [binutils-gdb] Get and set PC correctly on aarch64 in multi-arch sergiodj+buildbot
2015-08-08 18:25 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-08-04 14:37 [binutils-gdb] Use arm target description and regs_info for 32-bit file on aarch64 GDBserver sergiodj+buildbot
2015-08-08 17:33 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-08-04 14:17 [binutils-gdb] New regs_info for aarch32 sergiodj+buildbot
2015-08-08 17:02 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-08-04 13:49 [binutils-gdb] Move have_ptrace_getregset to linux-low.c sergiodj+buildbot
2015-08-08 13:26 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-08-04 12:22 [binutils-gdb] signal_command: Leftover cleanup chain regression sergiodj+buildbot
2015-08-08  9:50 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-08-04 11:51 [binutils-gdb] ASAN attach crash - 7.9 regression sergiodj+buildbot
2015-08-08  9:35 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-08-04  8:57 [binutils-gdb] C++: dlsym casts in gdb/linux-thread-db.c and gdb/gdbserver/thread-db.c sergiodj+buildbot
2015-08-08  5:58 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-08-03 18:13 [binutils-gdb] dwarf2read.c: fix latent buglet sergiodj+buildbot
2015-08-07 15:33 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-08-03 17:06 [binutils-gdb] gdb.perf/single-step.exp (SINGLE_STEP_COUNT): Change to 1000 from 10000 sergiodj+buildbot
2015-08-07 14:53 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-08-03 16:42 [binutils-gdb] Add parallel build support for perf tests sergiodj+buildbot
2015-08-07 11:16 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-08-03 16:15 [binutils-gdb] Move basic perf-test output from perftest.log to perftest.sum sergiodj+buildbot
2015-08-07 10:33 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-08-03 12:53 [binutils-gdb] Fix build error due to uninitialized variable warning sergiodj+buildbot
2015-08-07  6:57 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
     [not found] <e76460dbb9b9b34b9c7fc2f2e4faae38730d00b0@gdb-build>
2015-08-02 22:45 ` sergiodj+buildbot
2015-08-02 18:22 [binutils-gdb] Complete the previous commit (block_found refactoring) sergiodj+buildbot
2015-08-02 18:58 ` Failures on Debian-MIPS-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-02  7:59 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-31 22:38 [binutils-gdb] testsuite: tcl exec& -> 'kill -9 $pid' is racy (attach-many-short-lived-thread.exp races and others) sergiodj+buildbot
2015-08-02  7:04 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-31 18:24 [binutils-gdb] Fix m32r_remove_watchpoint parameter type sergiodj+buildbot
2015-08-02  3:27 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-31 17:25 [binutils-gdb] Mostly trivial enum fixes sergiodj+buildbot
2015-08-01 23:51 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-30 22:43 [binutils-gdb] Don't allow non-stack memory writes in the prologue for nios2 sergiodj+buildbot
2015-08-01 19:15 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-30 19:05 [binutils-gdb] remote follow fork and spurious child stops in non-stop mode sergiodj+buildbot
2015-07-31 20:31 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-30 18:34 [binutils-gdb] PR threads/18600: Inferiors left around after fork+thread spawn sergiodj+buildbot
2015-07-31 19:48 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-30 18:03 [binutils-gdb] PR threads/18600: Threads left stopped after fork+thread spawn sergiodj+buildbot
2015-07-31 16:12 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-30 17:17 [binutils-gdb] Remove isize output argument from fast_tracepoint_valid_at sergiodj+buildbot
2015-07-31 12:36 ` Failures on Debian-MIPS-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-07-31  4:40 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-30 11:50 [binutils-gdb] [AArch64] Rename boolean arguments in decoding functions sergiodj+buildbot
2015-07-30 21:27 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-30 11:29 [binutils-gdb] Properly disassemble movnti in Intel mode sergiodj+buildbot
2015-07-30 17:49 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-30 10:44 [binutils-gdb] Don't change the default symbol for relocatable link sergiodj+buildbot
2015-07-30 14:09 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-30  0:59 [binutils-gdb] MIPS ptrace build fixes sergiodj+buildbot
2015-07-30  0:59 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-29 16:17 [binutils-gdb] Make gdb.base/a2-run.exp use $inferior_spawn_id and gdb_test_stdio sergiodj+buildbot
2015-07-29 20:55 ` Failures on Debian-MIPS-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-29 19:54 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-29 14:53 [binutils-gdb] Make gdb.base/catch-gdb-caused-signals.exp use gdb_test_stdio sergiodj+buildbot
2015-07-29 18:51 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-29 14:28 [binutils-gdb] Make gdb.base/call-strs.exp use gdb_test_stdio sergiodj+buildbot
2015-07-29 17:48 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-29 13:47 [binutils-gdb] Make gdb.base/sizeof.exp use gdb_test_stdio sergiodj+buildbot
2015-07-29 16:46 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-29 13:15 [binutils-gdb] Introduce gdb_test_stdio sergiodj+buildbot
2015-07-29 15:43 ` Failures on Debian-MIPS-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-29 14:42 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-29 12:13 [binutils-gdb] Don't rely on inferior I/O in {call-signal-resume, unwindonsignal}.exp sergiodj+buildbot
2015-07-29 13:40 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-29 11:41 [binutils-gdb] Don't rely on inferior I/O in gdb.base/siginfo-addr.exp sergiodj+buildbot
2015-07-29 12:37 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-29  3:50 [binutils-gdb] bfd/mmo.c (MMIX): Fix massive gcc LTO testsuite failures sergiodj+buildbot
2015-07-29  4:45 ` Failures on Debian-MIPS-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-28 22:42 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-28 17:33 [binutils-gdb] Fix gdb.server/server-exec-info.exp with the extended-remote board sergiodj+buildbot
2015-07-28 20:40 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-28 16:04 [binutils-gdb] Introduce get_value_arch sergiodj+buildbot
2015-07-28 18:52 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-28 15:45 [binutils-gdb] Update comments in struct value for non-8-bits architectures sergiodj+buildbot
2015-07-28 17:50 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-28 15:23 [binutils-gdb] Update comment for struct type's length field, introduce type_length_units sergiodj+buildbot
2015-07-28 16:47 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
     [not found] <13e1dec8960122ec0329f74e5915503e14db5ea2@gdb-build>
2015-07-28 13:39 ` sergiodj+buildbot
2015-07-28  9:27 [binutils-gdb] Fallout from "Reorder more powerpc64 sections for -z relro" sergiodj+buildbot
2015-07-28 15:44 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-28  8:21 [binutils-gdb] Check for asprintf and vasprintf during configure stage sergiodj+buildbot
2015-07-28 14:42 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-28  0:42 [binutils-gdb] Remove xfail in gdb.mi/mi-watch.exp sergiodj+buildbot
2015-07-28 12:37 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-28  0:15 [binutils-gdb] Factor out complex printing code from generic_val_print sergiodj+buildbot
2015-07-28 11:34 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-27 23:49 [binutils-gdb] Factor out decfloat printing code from generic_val_print sergiodj+buildbot
2015-07-28 10:32 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-27 23:22 [binutils-gdb] Factor out float printing code from generic_val_print sergiodj+buildbot
2015-07-28  9:30 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-27 22:53 [binutils-gdb] Factor out char printing code from generic_val_print sergiodj+buildbot
2015-07-28  8:28 ` Failures on Debian-MIPS-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  7:26 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-27 22:04 [binutils-gdb] Factor out bool printing code from generic_val_print sergiodj+buildbot
2015-07-28  6:23 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-27 21:38 [binutils-gdb] Factor out function/method printing code from generic_val_print sergiodj+buildbot
2015-07-28  5:40 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-27 21:13 [binutils-gdb] Factor out flags printing code from generic_val_print sergiodj+buildbot
2015-07-28  4:46 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-27 20:50 [binutils-gdb] Factor out enum printing code from generic_val_print sergiodj+buildbot
2015-07-28  3:44 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-27 20:24 [binutils-gdb] Factor out reference printing code from generic_val_print sergiodj+buildbot
2015-07-28  2:43 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-27 20:01 [binutils-gdb] Factor out memberptr printing code from generic_val_print sergiodj+buildbot
2015-07-28  1:40 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-27 19:36 [binutils-gdb] Factor out pointer printing code from generic_val_print sergiodj+buildbot
2015-07-28  0:39 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-27 19:09 [binutils-gdb] Factor out array printing code from generic_val_print sergiodj+buildbot
2015-07-27 23:37 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-27 18:42 [binutils-gdb] Factor out print_unpacked_pointer from generic_val_print sergiodj+buildbot
2015-07-27 22:35 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-27 17:23 [binutils-gdb] Have SIGTERM promptly quit GDB even when the dummy target is active sergiodj+buildbot
2015-07-27 21:33 ` Failures on Debian-MIPS-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 20:31 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-27 16:26 [binutils-gdb] Remove REMOTE_EXAMPLES from gdb/Makefile.in sergiodj+buildbot
2015-07-27 19:29 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-27 15:58 [binutils-gdb] Regenerate configure files sergiodj+buildbot
2015-07-27 18:27 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-27 15:26 [binutils-gdb] Sync toplevel files with GCC sergiodj+buildbot
2015-07-27 17:25 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-27 15:06 [binutils-gdb] Sync config with GCC sergiodj+buildbot
2015-07-27 16:23 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-27 14:27 [binutils-gdb] Fix the address size computation for the MSP430 port sergiodj+buildbot
2015-07-27 15:21 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-27 11:38 [binutils-gdb] [AArch64] Fix extern protected data handling sergiodj+buildbot
2015-07-27 12:56 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-27 10:59 [binutils-gdb] [ARM] Fix extern protected data handling sergiodj+buildbot
2015-07-27 11:54 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-26  5:14 [binutils-gdb] remote.c: Make read_ptid return a null value when no thread id is found sergiodj+buildbot
2015-07-26 18:35 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
     [not found] <54019719152ab269fb4cec2c6a8a245ba6af6e49@gdb-build>
2015-07-25 20:39 ` sergiodj+buildbot
2015-07-25 20:08 [binutils-gdb] Revert "Sync readline/ to version 7.0 alpha" sergiodj+buildbot
2015-07-26 17:33 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-25 19:17 [binutils-gdb] Revert: * Makefile.in (check/%.exp): Pass directory for GDB_PARALLEL sergiodj+buildbot
2015-07-26 16:32 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-25 15:49 [binutils-gdb] Don't build readline's shared libs by default sergiodj+buildbot
2015-07-26 15:29 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-25 15:10 [binutils-gdb] Skip missing symbol version section check for executable sergiodj+buildbot
2015-07-26 14:27 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-25 14:01 [binutils-gdb] Sync readline/ to version 7.0 alpha sergiodj+buildbot
2015-07-26 13:44 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-25 11:23 [binutils-gdb] Fix broken -Bsymbolic-functions sergiodj+buildbot
2015-07-26 12:41 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-25  1:51 [binutils-gdb] Revert 4fd4095a5ffe3d4e50e0dac5f8ad37b8478afa9d, log individual measurements sergiodj+buildbot
2015-07-26 11:39 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-25  1:28 [binutils-gdb] Add gmonster-{1,2} perf testcases sergiodj+buildbot
2015-07-26 10:37 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-25  1:05 [binutils-gdb] Add perf testcase generator sergiodj+buildbot
2015-07-26  9:42 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-25  0:40 [binutils-gdb] PerfTest::assemble functions return results sergiodj+buildbot
2015-07-26  8:40 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-25  0:14 [binutils-gdb] lib/gdb.exp (clean_restart): Make executable optional sergiodj+buildbot
2015-07-26  8:01 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-24 23:49 [binutils-gdb] Clean up testsuite compiler_info support sergiodj+buildbot
2015-07-26  6:59 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-24 23:25 [binutils-gdb] Add parallel build support for perf tests sergiodj+buildbot
2015-07-26  5:57 ` Failures on Debian-MIPS-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-26  4:55 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-24 22:23 [binutils-gdb] Print data from individual perf runs sergiodj+buildbot
2015-07-26  3:53 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-24 20:59 [binutils-gdb] Call gdb_exit before gdb_skip_xml_test on gdb.base/catch-syscall.exp sergiodj+buildbot
2015-07-26  2:55 ` Failures on Debian-MIPS-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-26  1:49 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-24 19:12 [binutils-gdb] gdb.python/py-events.exp and normal_stop observers ordering sergiodj+buildbot
2015-07-26  0:47 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-24 18:44 [binutils-gdb] PR gdb/18717: internal error if non-leader thread exits process sergiodj+buildbot
2015-07-25 23:45 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-24 18:21 [binutils-gdb] Fix failed exec error message sergiodj+buildbot
2015-07-25 22:35 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-24 17:58 [binutils-gdb] Linux: sys/ptrace.h -> nat/gdb_ptrace.h everywhere sergiodj+buildbot
2015-07-25 21:33 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-24 17:15 [binutils-gdb] Move gdb_ptrace.h to nat/ sergiodj+buildbot
2015-07-25 17:03 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-24 16:56 [binutils-gdb] make gdbserver use the same ptrace autoconf checks as gdb sergiodj+buildbot
2015-07-25 13:27 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-24 16:35 [binutils-gdb] Remove proc->priv->new_inferior sergiodj+buildbot
2015-07-25  9:52 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-24 16:10 [binutils-gdb] Initialise target descrption after skipping extra traps for --wrapper sergiodj+buildbot
2015-07-25  6:16 ` Failures on Debian-MIPS-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-25  2:39 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-24 15:23 [binutils-gdb] Refactor start_inferior sergiodj+buildbot
2015-07-24 23:03 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-24 14:57 [binutils-gdb] Test --wrapper when restarting process sergiodj+buildbot
2015-07-24 22:10 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-24 14:36 [binutils-gdb] Set general_thread after restart sergiodj+buildbot
2015-07-24 18:32 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-24 13:53 [binutils-gdb] Test --wrapper in extended-remote sergiodj+buildbot
2015-07-24 17:26 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-24  6:38 [binutils-gdb] Correct reloc section name sergiodj+buildbot
2015-07-24 13:00 ` Failures on Debian-MIPS-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  9:23 ` Failures on Debian-MIPS-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-24  1:38 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-23 16:45 [binutils-gdb] Fix crash when reading dummy CUs sergiodj+buildbot
2015-07-23 20:05 ` Failures on Debian-MIPS-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 14:20 ` Failures on Debian-MIPS-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 13:40 ` Failures on Debian-MIPS-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 10:50 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-23  3:33 [binutils-gdb] Fix ubsan signed integer overflow sergiodj+buildbot
2015-07-23  7:01 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-22 20:38 [binutils-gdb] Fix memory operand size for vcvtt?ps2u?qq instructions sergiodj+buildbot
2015-07-23  0:07 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-22 10:11 [binutils-gdb] Fix ppc64 ELFv1 assertion failure sergiodj+buildbot
2015-07-22 12:33 ` Failures on Debian-MIPS-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 21:36 ` Failures on Debian-MIPS-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 16:01 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-21  8:54 [binutils-gdb] [ARM] Support correctly spelled ARMv6KZ architecture names sergiodj+buildbot
2015-07-21 12:23 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-20 22:38 [binutils-gdb] gdb.ada/info_exc.exp: Adjust expected output in "info exception" test sergiodj+buildbot
2015-07-21  1:51 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-20 16:00 [binutils-gdb] Fix ARI warnings to nat/aarch64-linux-hw-point.{c,h} sergiodj+buildbot
2015-07-20 16:44 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-20 13:07 [binutils-gdb] Make binutils abort message GDB friendly sergiodj+buildbot
2015-07-20 15:54 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-20  5:16 [binutils-gdb] Regen two files sergiodj+buildbot
2015-07-20  7:58 ` Failures on Debian-MIPS-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-19 11:20 ` Failures on Debian-MIPS-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-19  8:29 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-17 14:57 [binutils-gdb] Pass aarch64_debug_reg_state to functions sergiodj+buildbot
2015-07-19  5:40 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-17 14:32 [binutils-gdb] Use debug_printf to print debug message sergiodj+buildbot
2015-07-19  2:49 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-17 13:56 [binutils-gdb] int -> enum target_hw_bp_type in aarch64-linux-nat.c sergiodj+buildbot
2015-07-18 23:58 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-17 13:16 [binutils-gdb] Call ptid_get_pid instead of get_thread_id in aarch64_linux_get_debug_reg_capacity sergiodj+buildbot
2015-07-18 21:08 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-17 12:23 [binutils-gdb] [AArch64] Sort TLS reloc types alphabetically sergiodj+buildbot
2015-07-18 18:17 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-17 11:35 [binutils-gdb] Fix using uninitialised values sergiodj+buildbot
2015-07-18 15:27 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-16 16:29 [binutils-gdb] Fix gdb.arch/i386-biarch-core.exp FAIL on i386 sergiodj+buildbot
2015-07-18 12:38 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-16 16:08 [binutils-gdb] Updates the ARM disassembler's output of floating point constants to include the actual floating point value sergiodj+buildbot
2015-07-18  9:48 ` Failures on Debian-MIPS-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-18  4:08 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-16  9:32 [binutils-gdb] [AArch64] Mark single precision pseudo registers unavailable if invalid sergiodj+buildbot
2015-07-17 22:27 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-15 18:40 [binutils-gdb] Revert the previous 7 commits of: Validate binary before use sergiodj+buildbot
2015-07-17 19:36 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-15 18:01 [binutils-gdb] Tests for validate symbol file using build-id sergiodj+buildbot
2015-07-17 13:59 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-15 17:53 [binutils-gdb] Validate symbol file using build-id sergiodj+buildbot
2015-07-17 13:22 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-15 17:35 [binutils-gdb] gdbserver build-id attribute generator sergiodj+buildbot
2015-07-17 12:00 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-15 17:14 [binutils-gdb] Move linux_find_memory_regions_full & co sergiodj+buildbot
2015-07-17 10:39 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-15 16:55 [binutils-gdb] Prepare linux_find_memory_regions_full & co. for move sergiodj+buildbot
2015-07-17  9:17 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-15 16:15 [binutils-gdb] Create empty nat/linux-maps.[ch] and common/target-utils.[ch] sergiodj+buildbot
2015-07-17  3:36 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-15  6:52 [binutils-gdb] ari, btrace: avoid unsigned long long sergiodj+buildbot
2015-07-16 16:15 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-14 21:08 [binutils-gdb] Remove CHECK_TYPEDEF, use check_typedef instead sergiodj+buildbot
2015-07-16 13:24 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-14 19:13 [binutils-gdb] Add support reading D modules from DWARF sergiodj+buildbot
2015-07-16 10:33 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-14 18:50 [binutils-gdb] i386-biarch-core.exp: Fix comment typo sergiodj+buildbot
2015-07-16  7:42 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-14 17:29 [binutils-gdb] Remove trailing spaces in demangle.h sergiodj+buildbot
2015-07-15 20:19 ` Failures on Debian-MIPS-m64, branch master sergiodj+buildbot
2015-07-14 16:05 [binutils-gdb] Sync config/warnings.m4 with GCC sergiodj+buildbot
2015-07-15  8:57 ` Failures on Debian-MIPS-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).