public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
* [binutils-gdb] S390: Add syscall info for syscalls up to 374
@ 2016-03-17 10:26 sergiodj+buildbot
  2016-03-17 10:29 ` Failures on AIX-POWER7-plain, branch master sergiodj+buildbot
                   ` (23 more replies)
  0 siblings, 24 replies; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-03-17 10:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bba960fc4b3f330ec75ef7d3581aaaed4c560c49 ***

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

S390: Add syscall info for syscalls up to 374

Represent new Linux syscalls for s390 and s390x in GDB's syscall info.
Add the syscalls from 355 (userfaultfd) up to 374 (mlock2) as well as
the previously reserved NUMA syscalls 268-270, 287, and 310.

gdb/ChangeLog:

	* syscalls/s390-linux.xml: Add NUMA syscalls and new syscalls up
	to 374.
	* syscalls/s390x-linux.xml: Likewise.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [spu] throw error when target_read_memory fails
@ 2016-03-18 16:52 sergiodj+buildbot
  2016-03-19 16:13 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-03-18 16:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 941319d15194580a047484a53f232d374dc2d712 ***

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

[spu] throw error when target_read_memory fails

I happen to see that 1 is returned in spu_software_single_step when
target_read_memory returns 1.  It must be wrong.  That patch changes
it to throwing an error.  Note that I choose to throw error because I
find the code in the end of spu_software_single_step throws errors.

gdb:

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

	* spu-tdep.c (spu_software_single_step): Throw error when
	target_read_memory fails.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Set signal to 0 after enqueue_pending_signal
@ 2016-03-18 15:06 sergiodj+buildbot
  2016-03-19 13:13 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-03-18 15:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 94610ec4ee630e677d15361353796cac17339c53 ***

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

Set signal to 0 after enqueue_pending_signal

Today, we enqueue signal in linux_resume_one_lwp_throw, but set
variable 'signal' many lines below with the comment

      /* Postpone any pending signal.  It was enqueued above.  */
      signal = 0;

I feel difficult to associate code across many lines, and we should
move the code close to enqueue_pending_signal call.  This is what
this patch does in general.  After this change, variable 'signal'
is set to zero very early, so the 'signal' value in the following
debugging message makes no sense, so I remove it from the debugging
message.  The function returns early if lwp->status_pending_p is
true, so 'signal' value in the debugging message doesn't matter,
AFAICS.  Also, I move one debugging message several lines below to
make it close the real ptrace call,

  if (debug_threads)
    debug_printf ("Resuming lwp %ld (%s, signal %d, stop %s)\n",
		  lwpid_of (thread), step ? "step" : "continue", signal,
		  lwp->stop_expected ? "expected" : "not expected");

so that the debugging message can reflect what GDBserver does.  This
is a code refactor and only debugging messages are affected.

gdb/gdbserver:

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

	* linux-low.c (linux_resume_one_lwp_throw): Set 'signal' to
	0 if signal is enqueued.  Remove 'signal' from one debugging
	message.  Move one debugging message to some lines below.
	Remove code setting 'signal' to 0.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Remove redundant WIFSTOPPED check
@ 2016-03-18 14:39 sergiodj+buildbot
  2016-03-19  3:58 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-03-18 14:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 80aea927cc7bf97a2bc22e1fb2111c52be295e8b ***

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

Remove redundant WIFSTOPPED check

WIFSTOPPED is checked linux_wstatus_maybe_breakpoint, so WIFSTOPPED
in "WIFSTOPPED (wstat) && linux_wstatus_maybe_breakpoint (wstat)"
is redundant.  This patch removes WIFSTOPPED check.

gdb/gdbserver:

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

	* linux-low.c (linux_low_filter_event): Remove redundant
	WIFSTOPPED check together with linux_wstatus_maybe_breakpoint.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Add mips and s390 build targets for gold.
@ 2016-03-17 23:01 sergiodj+buildbot
  2016-03-18 13:21 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-03-17 23:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ea01647092eefeca9336b36809962ff097306b41 ***

Author: Cary Coutant <ccoutant@gmail.com>
Branch: master
Commit: ea01647092eefeca9336b36809962ff097306b41

Add mips and s390 build targets for gold.

	* configure.ac: Add mips and s390 to the gold target check.
	* configure: Regenerate.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] S390: Fix output path for s390-multiarch test case
@ 2016-03-17 10:12 sergiodj+buildbot
  2016-03-18  6:48 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-03-17 10:12 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 64bcd522de3ae1b88d042986de8e36e44b9f2e42 ***

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

S390: Fix output path for s390-multiarch test case

Since test artifacts are organized in a directory hierarchy, the
s390-multiarch test case is not executed correctly any more.  This is
because it uses an obsolete way of constructing the output paths.

This fix invokes standard_testfile instead.

gdb/testsuite/ChangeLog:

	* gdb.arch/s390-multiarch.exp: Use standard_testfile instead of
	maintaining separate logic for constructing the output path.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] linux-record.c: Fix whitespace issues
@ 2016-03-17  9:34 sergiodj+buildbot
  2016-03-18  4:02 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-03-17  9:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0fc8f115fd95a88ff2ce4c839b634b39d200c734 ***

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

linux-record.c: Fix whitespace issues

This patch changes whitespace only, fixing whitespace issues in
linux-record.c.

gdb/ChangeLog:

	* linux-record.c: Fix whitespace issues; tabify, remove trailing
	spaces.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] linux-record: Fix bad fall-through for pipe/pipe2
@ 2016-03-17  9:19 sergiodj+buildbot
  2016-03-18  2:47 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-03-17  9:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT afdab9165435e17169b4984eeb29ea751319aa74 ***

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

linux-record: Fix bad fall-through for pipe/pipe2

This patch added handling for some syscalls to linux-record.c:

  https://sourceware.org/ml/gdb-patches/2015-10/msg00452.html

But for both `pipe' and `pipe2' the patch lacks a statement after an
`if', such that the following `break' is interpreted as the `if'-body
instead.

This adds the missing (return-) statements for the conditionals.

gdb/ChangeLog:

	* linux-record.c (record_linux_system_call): Add missing return
	statements to handling of pipe and pipe2 syscalls.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] PR remote/19496, interrupted syscall in forking-threads-plus-bkpt
@ 2016-03-16 22:29 sergiodj+buildbot
  2016-03-18  1:16 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-03-16 22:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7868401b7b63d851eea5de3b780591238d579bd1 ***

Author: Don Breazeal <donb@codesourcery.com>
Branch: master
Commit: 7868401b7b63d851eea5de3b780591238d579bd1

PR remote/19496, interrupted syscall in forking-threads-plus-bkpt

This patch addresses "fork:Interrupted system call" (or wait:) failures
in gdb.threads/forking-threads-plus-breakpoint.exp.

The test program spawns ten threads, each of which do ten fork/waitpid
sequences.  The cause of the problem was that when one of the fork
children exited before the corresponding fork parent could initiate its
waitpid for that child, a SIGCHLD and/or SIGSTOP was delivered and
interrupted a fork or waitpid in another thread.

The fix was to wrap the system calls in a loop to retry the call if
it was interrupted, like:

do
  {
    pid = fork ();
  }
while (pid == -1 && errno == EINTR);

Since this is a Linux-only test I figure it is OK to use errno and EINTR.
I tried a number of alternative fixes using SIG_IGN, SA_RESTART,
pthread_sigblock, and bsd_signal, but none of these worked as well.

Tested on Nios II Linux target with x86 Linux host.

gdb/testsuite/ChangeLog:
2016-03-16  Don Breazeal  <donb@codesourcery.com>

	* gdb.threads/forking-threads-plus-breakpoint.c (thread_forks):
	Retry fork and waitpid on interrupted system call errors.
	* gdb.threads/forking-threads-plus-breakpoint.exp: (do_test):
	Use with_timeout_factor to increase timeout to 90.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Process record: Fix arm-linux syscall arguments
@ 2016-03-16 19:42 sergiodj+buildbot
  2016-03-16 23:37 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-03-16 19:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6b94a855beef3a301509dfac6bf5446d1953524b ***

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

Process record: Fix arm-linux syscall arguments

Arguments are passed in r0-r6 on arm linux syscall (both EABI and OABI).
This patch is to set arm_linux_record_tdep.arg{1-7} to the right
register number.

This patch fixes the following test failures...

-FAIL: gdb.reverse/getresuid-reverse.exp: check ruid record
-FAIL: gdb.reverse/getresuid-reverse.exp: check rgid record
-FAIL: gdb.reverse/pipe-reverse.exp: check pipe record
-FAIL: gdb.reverse/readv-reverse.exp: check readv record
-FAIL: gdb.reverse/readv-reverse.exp: check readv record
-FAIL: gdb.reverse/readv-reverse.exp: check readv record
-FAIL: gdb.reverse/readv-reverse.exp: check readv record
-FAIL: gdb.reverse/waitpid-reverse.exp: check waitpid record

gdb:

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

	* arm-linux-tdep.c (arm_linux_init_abi): Fix
	arm_linux_record_tdep.arg1, arm_linux_record_tdep.arg2 and
	arm_linux_record_tdep.arg3.  Set arm_linux_record_tdep.arg4,
	arm_linux_record_tdep.arg5, arm_linux_record_tdep.arg6, and
	arm_linux_record_tdep.arg7.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] PR 18303, Tolerate malformed input for lookup_symbol-called functions
@ 2016-03-16 17:23 sergiodj+buildbot
  2016-03-16 17:24 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-03-16 17:23 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1cafadb4e4eb329dea01355c6632b3077113d80c ***

Author: Don Breazeal <donb@codesourcery.com>
Branch: master
Commit: 1cafadb4e4eb329dea01355c6632b3077113d80c

PR 18303, Tolerate malformed input for lookup_symbol-called functions

lookup_symbol is often called with user input.  Consequently, any
function called from lookup_symbol{,_in_language} should attempt to
deal with malformed input gracefully.  After all, malformed user
input is not a programming/API error.

This patch does not attempt to find/correct all instances of this.  It
only fixes locations in the code that trigger test suite failures.

This patch fixes PR breakpoints/18303, "Assertion: -breakpoint-insert
with windows paths of file in non-current directory".

The patch includes three new tests related to this.  One is just
gdb.linespec/ls-errs.exp copied and converted to use C++ instead of C, and
to add a case using a file name containing a Windows-style logical drive
specifier.  The others include an MI test to provide a regression test for
the specific case reported in PR 18303, and a C++ test for proper error
handling of access to a program variable when using a file scope specifier
that refers to a non-existent file.

Tested on x86_64 native Linux.

gdb/ChangeLog
2016-01-28  Keith Seitz  <keiths@redhat.com>

	PR breakpoints/18303
	* cp-namespace.c (cp_lookup_bare_symbol): Change assertion to
	look for "::" instead of simply ":".
	(cp_search_static_and_baseclasses): Return null_block_symbol for
	malformed input.
	Remove assertions.
	* cp-support.c (cp_find_first_component_aux): Do not return
	a prefix length for ':' unless the next character is also ':'.

gdb/testsuite/ChangeLog
2016-01-28  Don Breazeal  <donb@codesourcery.com>

	* gdb.cp/scope-err.cc: New test program.
	* gdb.cp/scope-err.exp: New test script.
	* gdb.linespec/ls-errs.c (myfunction): Expanded to have multiple
	lines and "set breakpoint here" comment.
	* gdb.linespec/ls-errs.exp: Added C++ testing and new test case.
	Fixed some whitespace and format issues.
	* gdb.mi/mi-linespec-err-cp.cc: New test program.
	* gdb.mi/mi-linespec-err-cp.exp: New test script.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [ARM] Support ARMv8.2 FP16 simd instructions
@ 2016-03-16 16:29 sergiodj+buildbot
  2016-03-17 10:58 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-03-16 16:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cc9333013723880949a1e07a3e04bdbc1a3c3032 ***

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

[ARM] Support ARMv8.2 FP16 simd instructions

gas/
	* config/tc-arm.c (N_S_32): New.
	(N_F_16_32): Likewise.
	(N_SUF_32): Support N_F16.
	(N_IF_32): Likewise.
	(neon_dyadic_misc): Likewise.
	(do_neon_cmp): Likewise.
	(do_neon_cmp_inv): Likewise.
	(do_neon_mul): Likewise.
	(do_neon_fcmp_absolute): Likewise.
	(do_neon_step): Likewise.
	(do_neon_abs_neg): Likewise.
	(CVT_FLAVOR_VAR): Likewise.
	(do_neon_cvt_1): Likewise.
	(do_neon_recip_est): Likewise.
	(do_vmaxnm): Likewise.
	(do_vrint_1): Likewise.
	(neon_check_type): Check architecture support for FP16 extension.
	(insns): Update comments.
	* testsuite/gas/arm/armv8-2-fp16-simd.s: New test source.
	* testsuite/gas/arm/armv8-2-fp16-simd.d: New testcase for arm mode.
	* testsuite/gas/arm/armv8-2-fp16-simd-thumb.d: Likewise for thumb mode.
	* testsuite/gas/arm/armv8-2-fp16-simd-warning.d: New rejection test for
	arm mode.
	* testsuite/gas/arm/armv8-2-fp16-simd-warning-thumb.d: Likewise for
	thumb mode.
	* testsuite/gas/arm/armv8-2-fp16-simd-warning.l: New expected rejection
	error file.

opcode/
	* arm-dis.c (neon_opcodes): Support new FP16 instructions.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Fix PR gdb/19676: Internal error in linux-thread.db.c if /proc not mounted
@ 2016-03-15 17:14 sergiodj+buildbot
  2016-03-15 19:55 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-03-15 17:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1eb2dbb8d73c344e199fd04531ec3f649e2835b2 ***

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

Fix PR gdb/19676: Internal error in linux-thread.db.c if /proc not mounted

If /proc is not mounted, GDB fails an assertion in find_new_threads_once:

 Continuing.
 .../src/gdb/linux-thread-db.c:1249: internal-error: find_new_threads_once: Assertion `!target_has_execution' failed.
 A problem internal to GDB has been detected,
 further debugging may prove unreliable.
 Quit this debugging session? (y or n)

That was supposed to catch misuses of td_ta_thr_iter, which is unsafe
for live debugging.  However, if /proc is not mounted, we still
fallback to using it.

I didn't bother with a warning, because GDB already prints several
others related to failing to open /proc files.

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

	PR gdb/19676
	* linux-thread-db.c (try_thread_db_load_1): Leave
	info->td_ta_thr_iter_p NULL iff debugging a live process and we
	have /proc access.
	(find_new_threads_once): Assert that we have a non-NULL
	info->td_ta_thr_iter_p instead of checking whether the target has
	execution.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Fix PR gdb/19676: Disable displaced stepping if /proc not mounted
@ 2016-03-15 16:47 sergiodj+buildbot
  2016-03-15 18:18 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-03-15 16:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 16b4184277c4ad5b4a20278060fd3f6259d1ed49 ***

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

Fix PR gdb/19676: Disable displaced stepping if /proc not mounted

On GNU/Linux archs that support displaced stepping, if /proc is not
mounted, GDB gets stuck not able to step past breakpoints:

 (gdb) c
 Continuing.
 dl_main (phdr=<optimized out>, phnum=<optimized out>, user_entry=<optimized out>, auxv=<optimized out>) at rtld.c:2163
 2163      LIBC_PROBE (init_complete, 2, LM_ID_BASE, r);
 Cannot find AT_ENTRY auxiliary vector entry.
 (gdb) c
 Continuing.
 dl_main (phdr=<optimized out>, phnum=<optimized out>, user_entry=<optimized out>, auxv=<optimized out>) at rtld.c:2163
 2163      LIBC_PROBE (init_complete, 2, LM_ID_BASE, r);
 Cannot find AT_ENTRY auxiliary vector entry.
 (gdb)

That's because GDB can't figure out where the scratch pad is.

This is a regression introduced by the earlier changes to make the
Linux native target always work in non-stop mode.

This commit makes GDB detect the case and fallback to stepping over
breakpoints in-line.

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

	PR gdb/19676
	* infrun.c (displaced_step_prepare): Also disable displaced
	stepping on NOT_SUPPORTED_ERROR.
	* linux-tdep.c (linux_displaced_step_location): If reading auxv
	fails, throw NOT_SUPPORTED_ERROR instead of generic error.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Regenerate bfd-in2.h
@ 2016-03-14 20:28 sergiodj+buildbot
  2016-03-14 21:40 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-03-14 20:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fbe48798204180aa11c55e5377c1e23700b9c280 ***

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

Regenerate bfd-in2.h

	* bfd-in2.h: Regenerated.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] gdb.base/default.exp: Add missing $_as_string to "show convenience" test
@ 2016-03-14 16:56 sergiodj+buildbot
  2016-03-14 18:30 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-03-14 16:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fa4ff313317d6234bbd818b09332e7d85349a56a ***

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

gdb.base/default.exp: Add missing $_as_string to "show convenience" test

When adding the $_as_string convenience function, I missed a new test
failure in default.exp.  The tests lists the convenience functions, so
$_as_string should be added to the expected list.

Fixes:

+FAIL: gdb.base/default.exp: show convenience ($_caller_is = <internal function _caller_is> not found)

gdb/testsuite/ChangeLog:

	* gdb.base/default.exp: Add $_as_string to the list of expected
	convenience functions.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] gdb/s390: Fill pseudo register agent expression hooks.
@ 2016-03-11 10:15 sergiodj+buildbot
  2016-03-11 11:59 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-03-11 10:15 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c4b3e547d50b01dcf909498119ff6c0af482f2c8 ***

Author: Marcin Kocielnicki <koriakin@0x04.net>
Branch: master
Commit: c4b3e547d50b01dcf909498119ff6c0af482f2c8

gdb/s390: Fill pseudo register agent expression hooks.

gdb/ChangeLog:

	* s390-linux-tdep.c (s390_ax_pseudo_register_collect): New function.
	(s390_ax_pseudo_register_push_stack): New function.
	(s390_gdbarch_init): Fill ax_pseudo_register_collect and
	ax_pseudo_register_push_stack hooks.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Add $_as_string convenience function
@ 2016-03-10 22:34 sergiodj+buildbot
  2016-03-11  6:54 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-03-10 22:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f2f3ccb9f81255fd1b4f877600f39979c2d7ece5 ***

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

Add $_as_string convenience function

This patch is a follow-up to "Add printf format specifier for printing
enumerator":

  https://sourceware.org/ml/gdb-patches/2016-02/msg00144.html

Instead of having a solution specific to the printf command, Pedro
suggested adding a general purpose function $_as_string() that would
cover this use case and more.

So, in order to print the textual label of an enum, one can use:

  (gdb) printf "Visiting node of type %s\n", $_as_string(node)
  Visiting node of type NODE_INTEGER

gdb/ChangeLog:

	* data-directory/Makefile.in (PYTHON_FILE_LIST): Install
	gdb/function/as_string.py.
	* python/lib/gdb/function/as_string.py: New file.
	* NEWS: Mention the new $_as_string function.

gdb/testsuite/ChangeLog:

	* gdb.python/py-as-string.exp: New file.
	* gdb.python/py-as-string.c: New file.

gdb/doc/ChangeLog:

	* gdb.texinfo (Convenience Functions): Document $_as_string.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Mark the i370 target as obsolete.
@ 2016-03-10 15:43 sergiodj+buildbot
  2016-03-11  5:32 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-03-10 15:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3ed4ff97cbbeeb2658286769ac9e8a6a35390f26 ***

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

Mark the i370 target as obsolete.

	* config.bfd: Mark the i370 target as obsolete.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] gdb.trace/tfind.exp: Force call via global entry point on ppc64le.
@ 2016-03-10  1:30 sergiodj+buildbot
  2016-03-10  7:29 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-03-10  1:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f77198c878424891f11d6550370f8d9382f412de ***

Author: Marcin Kocielnicki <koriakin@0x04.net>
Branch: master
Commit: f77198c878424891f11d6550370f8d9382f412de

gdb.trace/tfind.exp: Force call via global entry point on ppc64le.

tfind.exp sets a breakpoint on *gdb_recursion_test, which is the global
entry point on ppc64le, and won't be hit, since the call uses
the local entry.  Fix by calling the function via a pointer in a global
variable, forcing use of the global entry.

This patch is a slightly modified hunk extracted from
https://sourceware.org/ml/gdb-patches/2015-07/msg00353.html

gdb/testsuite/ChangeLog:

2016-03-09  Wei-cheng Wang  <cole945@gmail.com>
	    Marcin Kocielnicki  <koriakin@0x04.net>

	* gdb.trace/actions.c (gdb_recursion_test_fp): New typedef.
	(gdb_recursion_test_ptr): New global variable.
	(gdb_recursion_test): Call gdb_recursion_test_ptr instead of
	gdb_recursion_test.
	(gdb_c_test): Ditto.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] gdb: Add tracepoint support for powerpc.
@ 2016-03-09 23:54 sergiodj+buildbot
  2016-03-10 10:10 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-03-09 23:54 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b04fd3bec955560e00fb0cf6b75e36187a207113 ***

Author: Marcin Kocielnicki <koriakin@0x04.net>
Branch: master
Commit: b04fd3bec955560e00fb0cf6b75e36187a207113

gdb: Add tracepoint support for powerpc.

gdb/gdbserver/ChangeLog:

	* linux-ppc-low.c (ppc_supports_tracepoints): New function.
	(struct linux_target_ops): Wire in the above.

gdb/testsuite/ChangeLog:

	* gdb.trace/ftrace.exp: Set arg0exp for ppc.
	* gdb.trace/mi-trace-unavailable.exp: Set pcnum for ppc.
	* gdb.trace/pending.exp: Accept leading dot before function name.
	* gdb.trace/trace-common.h: Add fast tracepoint dummy insn for ppc.
	* lib/trace-support.exp: Set registers for ppc.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] gdb.trace/change-loc.exp: Don't depend on tracepoint ordering.
@ 2016-03-09 22:03 sergiodj+buildbot
  2016-03-10  6:17 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-03-09 22:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ba84e0da35d29dd8969a4bcdd84e3eaa48927a84 ***

Author: Marcin Kocielnicki <koriakin@0x04.net>
Branch: master
Commit: ba84e0da35d29dd8969a4bcdd84e3eaa48927a84

gdb.trace/change-loc.exp: Don't depend on tracepoint ordering.

powerpc (32-bit) loads shared libraries below the main executable, so
the PENDING location is the first one, which the current regex doesn't
match.  Split it into two tests instead, one looking for the pending
tracepoint location, and the other for two installed locations.

gdb/testsuite/ChangeLog:

	* gdb.trace/change-loc.exp: Don't depend on tracepoint location
	ordering.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] More "Program" -> "Thread NN received signal" testsuite adjustment
@ 2016-03-09 21:55 sergiodj+buildbot
  2016-03-11  4:19 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-03-09 21:55 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 00dbd492e462565366a2691e0579b510ce4c3733 ***

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

More "Program" -> "Thread NN received signal" testsuite adjustment

These tests should have been adjusted by f303dbd60d9c (Fix PR
threads/19422 - show which thread caused stop), but clearly I had
missed grepping for potential-fail cases.

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

	* gdb.threads/attach-into-signal.exp: Adjust to "Program received
	signal" -> "Thread NN received signal" output change.
	* gdb.threads/ia64-sigill.exp: Likewise.
	* gdb.threads/linux-dp.exp: Likewise.
	* gdb.threads/manythreads.exp: Likewise.
	* gdb.threads/pending-step.exp: Likewise.
	* gdb.threads/print-threads.exp: Likewise.
	* gdb.threads/sigstep-threads.exp: Likewise.
	* gdb.threads/staticthreads.exp: Likewise.
	* gdb.threads/tls.exp: Likewise.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Simplify saved_command_line handling
@ 2016-03-09 21:09 sergiodj+buildbot
  2016-03-11  0:27 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-03-09 21:09 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2669cade3dcebf5d572bcd535cf21934cbc1633c ***

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

Simplify saved_command_line handling

There doesn't seem to be much point in trying to reuse this buffer.
Prefer simplicity instead.

(In case you're wondering whether this fixes an off-by-one: linelength
is misnamed; it's really a size including terminating null char.)

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

	* event-top.c (command_line_handler): Use xfree + xstrdup instead
	of xrealloc + strcpy.
	* main.c (captured_main): Use xstrdup instead of xmalloc plus
	manual clear.
	* top.c (saved_command_line): Rewrite comment.
	(saved_command_line_size): Delete.
	(command_line_input): Use xfree + xstrdup instead of xrealloc +
	strcpy.
	* top.h (saved_command_line_size): Delete declaration.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Use struct buffer in gdb_readline_no_editing
@ 2016-03-09 20:47 sergiodj+buildbot
  2016-03-10 21:42 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-03-09 20:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7a3bde34bc61af108556c74b661533dadddcb178 ***

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

Use struct buffer in gdb_readline_no_editing

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

	* common/buffer.h (buffer_grow_char): New function.
	* top.c: Include buffer.h.
	(gdb_readline_no_editing): Rename 'prompt_arg' parameter to
	'prompt'.  Use struct buffer instead of xrealloc.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] gdb_readline -> gdb_readline_no_editing
@ 2016-03-09 20:36 sergiodj+buildbot
  2016-03-10 20:13 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-03-09 20:36 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c5c136ea94f21e5ff968d5b402494611464c7b31 ***

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

gdb_readline -> gdb_readline_no_editing

Name this such that it's clearer that this is not a wrapper for the
real readline, but instead a replacement that provides no command line
editing features.

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

	* defs.h (gdb_readline): Delete declaration.
	* top.c (gdb_readline): Rename to ...
	(gdb_readline_no_editing): ... this, and make static.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Update prompt_for_continue comments
@ 2016-03-09 20:27 sergiodj+buildbot
  2016-03-10 18:44 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-03-09 20:27 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 720d2e96b424bb4bb1f7021f86763ff3df078e2b ***

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

Update prompt_for_continue comments

These comments are out of date -- we no longer call gdb_readline.  And
I think that mentioning the event loop is more useful here than
whatever GO32 issue had with gdb_readline, which may even no longer be
an issue.

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

	* utils.c (prompt_for_continue): Update comments.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] gdb_readline2 -> gdb_readline_no_editing_callback
@ 2016-03-09 20:06 sergiodj+buildbot
  2016-03-10 15:14 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-03-09 20:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c70061cf94691182484924c79cbbdd2203ef92d5 ***

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

gdb_readline2 -> gdb_readline_no_editing_callback

The "2" in "gdb_readline2" doesn't really convey much.  Rename for
clarity.

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

	* event-top.c (gdb_readline2): Rename to ...
	(gdb_readline_no_editing_callback): ... this.
	(change_line_handler, stdin_event_handler)
	(gdb_setup_readline): Adjust.
	* event-top.h (gdb_readline2): Rename to ...
	(gdb_readline_no_editing_callback): ... this, and move closer to
	other readline-related declarations.
	* mi/mi-interp.c (mi_interpreter_resume): Adjust.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Garbage collect window_hook
@ 2016-03-09 19:54 sergiodj+buildbot
  2016-03-10 13:26 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-03-09 19:54 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8a243832540cb3bd246192db1f0a4dfa44d92dcf ***

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

Garbage collect window_hook

I checked, and Insight doesn't set this.

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

	* top.c (window_hook): Delete.
	(command_loop): Remove references to window_hook.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] gdb/rs6000: Read backchain as unsigned.
@ 2016-03-09 18:40 sergiodj+buildbot
  2016-03-10  3:57 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-03-09 18:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cc2c4da8813b980a4e68272bb43583f4af6fe89c ***

Author: Marcin Kocielnicki <koriakin@0x04.net>
Branch: master
Commit: cc2c4da8813b980a4e68272bb43583f4af6fe89c

gdb/rs6000: Read backchain as unsigned.

Previously, backchain was read as a signed quantity, resulting in
addresses like 0xfffffffffffeded0 instead of 0xfffeded0 returned by
unwinder on 32-bit powerpc.  While normally such addresses are masked
off, this causes problems for tracepoints, since 0xfffffffffffeded0
is considered unavailable.

Fixes a test failure in gdb.trace/entry-values.exp.

gdb/ChangeLog:

	* corefile.c (safe_read_memory_unsigned_integer): New function.
	* gdbcore.h (safe_read_memory_unsigned_integer): New prototype.
	* rs6000-tdep.c (rs6000_frame_cache): Read backchain as unsigned.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] gdb: Add gen_return_address for powerpc.
@ 2016-03-09 18:28 sergiodj+buildbot
  2016-03-10  2:49 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-03-09 18:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a67914defbe57290c714975d7c1ccefa787fd635 ***

Author: Marcin Kocielnicki <koriakin@0x04.net>
Branch: master
Commit: a67914defbe57290c714975d7c1ccefa787fd635

gdb: Add gen_return_address for powerpc.

gdb/ChangeLog:

	* rs6000-tdep.c: Add "ax.h" and "ax-gdb.h" includes.
	(rs6000_gen_return_address): New function.
	(rs6000_gdbarch_init): Wire in the above.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] gdb: Add ax_pseudo_register_collect for powerpc.
@ 2016-03-09 18:02 sergiodj+buildbot
  2016-03-10  1:31 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-03-09 18:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2a2fa07bd121498a492f84312a36629383fc9445 ***

Author: Marcin Kocielnicki <koriakin@0x04.net>
Branch: master
Commit: 2a2fa07bd121498a492f84312a36629383fc9445

gdb: Add ax_pseudo_register_collect for powerpc.

gdb/ChangeLog:

	* rs6000-tdep.c (rs6000_ax_pseudo_register_collect): New function.
	(rs6000_gdbarch_init): Wire in the above.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] S390: Add use of unavailable-stack frame ID
@ 2016-03-09 16:30 sergiodj+buildbot
  2016-03-09 23:05 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-03-09 16:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6d53bec88f4c1576f74e918400aa2ccac2d129db ***

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

S390: Add use of unavailable-stack frame ID

When determining the frame ID of an inline frame, GDB currently asserts
that a valid ID of the underlying real frame is found, and that it does
not match outer_frame_id.  From inline_frame_this_id():

  /* For now, require we don't match outer_frame_id either (see
     comment above).  */
  gdb_assert (!frame_id_eq (*this_id, outer_frame_id));

However, this assertion may fail when the real frame's unwinder can not
determine the frame ID.  This happened on an s390x target with a binary
that lacked call frame information and also confused the prologue
analyzer, because then s390_frame_this_id() left the frame ID at its
default.

To fix this, this change enhances s390_frame_this_id such that an
unavailable-stack frame ID is built if no frame base can be determined
but the function address is available.

gdb/ChangeLog:

	* s390-linux-tdep.c (s390_prologue_frame_unwind_cache): Store
	frame func's PC in info->func before any other failure can occur.
	(s390_frame_this_id): Use frame_id_build_unavailable_stack if
	info->func has been filled out.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Avoid spaces in osabi names
@ 2016-03-09 16:19 sergiodj+buildbot
  2016-03-09 21:29 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-03-09 16:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f7990f1690e9ef0471634c871c790f6cf706866d ***

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

Avoid spaces in osabi names

It's not possible today to select some of the osabis by name.
Specifically, those that have spaces in their names and then the first
word is ambiguous...

For example:
 (gdb) set osabi <TAB>
 [...]
 FreeBSD ELF
 FreeBSD a.out
 [...]
 (gdb) set osabi FreeBSD ELF
 Ambiguous item "FreeBSD ELF".

In reality, because "set osabi" is an enum command, that was
equivalent to trying "set osabi FreeBSD", which is then obviously
ambiguous, because of "FreeBSD ELF" and "FreeBSD a.out".

Also, even if the first word is not ambiguous, we actually ignore
whatever comes after the first word:

 (gdb) set osabi GNU/Linux
 (gdb) show osabi
 The current OS ABI is "GNU/Linux".
 The default OS ABI is "GNU/Linux".
 (gdb) set osabi Windows SomeNonsense
                         ^^^^^^^^^^^^
 (gdb) show osabi
 The current OS ABI is "Windows CE".
 The default OS ABI is "GNU/Linux".
 (gdb)

Fix this by avoiding spaces in osabi names.

We could instead make "set osabi" have a custom set hook, or
alternatively make the enum set hook (in cli-setshow.c) handle values
with spaces, but OTOH, I have a feeling that could cause trouble.
E.g., in cases where we might want to write more than one enum value
in the same line.  We could support quoting as workaround, but, not
sure we want that.  "No spaces" seems like a simpler rule.

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

	* osabi.c (gdb_osabi_names): Avoid spaces in osabi names.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [FR-V] Handle FR300
@ 2016-03-09 16:08 sergiodj+buildbot
  2016-03-09 19:57 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-03-09 16:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 087ccc6a4f8c754a4f4d31810839a631dbeabe0d ***

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

[FR-V] Handle FR300

Even though "set architecture" presents fr300 as option:

 (gdb) set architecture fr<TAB>
 fr300  fr400  fr450  fr500  fr550  frv

Actually selecting fr300 doesn't work:

 (gdb) set architecture fr300
 Architecture `fr300' not recognized.
 The target architecture is set automatically (currently i386)
 (gdb)

This just looks like an obvious oversight.  Looking around gcc and
binutils sources, FR300 is basically a FR500 specialized for DSP and
low power.

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

	* frv-tdep.c (frv_gdbarch_init): Handle bfd_mach_fr300.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] For COFF and COFF/PE targets, skip relocations against absolute symbols.
@ 2016-03-09 15:43 sergiodj+buildbot
  2016-03-09 17:03 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-03-09 15:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 26c62da040fb9d602da269a3bdffdea13a4367c7 ***

Author: Leon Winter <winter-gcc@bfw-online.de>
Branch: master
Commit: 26c62da040fb9d602da269a3bdffdea13a4367c7

For COFF and COFF/PE targets, skip relocations against absolute symbols.

	PR ld/19623
	* cofflink.c (_bfd_coff_generic_relocate_section): Do not apply
	relocations against absolute symbols.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Allow zero length archive elements
@ 2016-03-09  6:37 sergiodj+buildbot
  2016-03-09 10:31 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-03-09  6:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 03ee85837ec2e10f7b67c417b17ab3ffa97a98d2 ***

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

Allow zero length archive elements

	PR binutils/19775
	* coff-alpha.c (alpha_ecoff_openr_next_archived_file): Allow zero
	length elements in the archive.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Don't create dynamic sections when relocatable
@ 2016-03-09  4:57 sergiodj+buildbot
  2016-03-09  9:38 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-03-09  4:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9c1d7a087682074d585253ad38719ec2363eb2b7 ***

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

Don't create dynamic sections when relocatable

Since dynamic sections aren't applicable to relocatable file, don't
create dynamic sections for -E/--dynamic-list when relocatable.

bfd/

	PR ld/19789
	* elflink.c (elf_link_add_object_symbols): Create dynamic sections
	for -E/--dynamic-list only when not relocatable.

ld/

	PR ld/19789
	* testsuite/ld-elf/pr19789.d: New file.
	* testsuite/ld-elf/pr19789.s: Likewise.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Fix floating conversion buffer overrun when host/target format matches
@ 2016-03-09  4:23 sergiodj+buildbot
  2016-03-09  6:48 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-03-09  4:23 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d7a87b5e4343467db23b70e73b156c9cc79c50ea ***

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

Fix floating conversion buffer overrun when host/target format matches

Running the testsuite with a gdb configured with --enable-libmcheck
reveals a problem:

  (gdb) ptype 3 * 2.0
  type = <12-byte float>
  memory clobbered past end of allocated block
  ERROR: Process no longer exists
  UNRESOLVED: gdb.ada/ptype_arith_binop.exp: ptype 3 * 2.0

  (gdb) PASS: gdb.dlang/expression.exp: ptype 0x1.FFFFFFFFFFFFFp1023
  ptype 0x1p-52L
  type = real
  memory clobbered past end of allocated block
  ERROR: Process no longer exists
  UNRESOLVED: gdb.dlang/expression.exp: ptype 0x1p-52L

Even though this shows up with Ada and D, it's easy to reproduce in C
too.  We just need to print a long double, when the current arch is
32-bit, which is the default when gdb starts up:

 $ ./gdb -q -ex "ptype 1.0L"
 type = long double
 memory clobbered past end of allocated block
 Aborted (core dumped)

Valgrind shows:

 ==22159== Invalid write of size 8
 ==22159==    at 0x8464A9: floatformat_from_doublest (doublest.c:756)
 ==22159==    by 0x846822: store_typed_floating (doublest.c:867)
 ==22159==    by 0x6A7959: value_from_double (value.c:3662)
 ==22159==    by 0x6A9F2D: evaluate_subexp_standard (eval.c:745)
 ==22159==    by 0x7F31AF: evaluate_subexp_c (c-lang.c:716)
 ==22159==    by 0x6A8986: evaluate_subexp (eval.c:79)
 ==22159==    by 0x6A8BA3: evaluate_type (eval.c:174)
 ==22159==    by 0x817CCF: whatis_exp (typeprint.c:456)
 ==22159==    by 0x817EAA: ptype_command (typeprint.c:508)
 ==22159==    by 0x5F267B: do_cfunc (cli-decode.c:105)
 ==22159==    by 0x5F5618: cmd_func (cli-decode.c:1885)
 ==22159==    by 0x83622A: execute_command (top.c:475)
 ==22159==  Address 0x8c6cb28 is 8 bytes inside a block of size 12 alloc'd
 ==22159==    at 0x4C2AA98: calloc (vg_replace_malloc.c:711)
 ==22159==    by 0x87384A: xcalloc (common-utils.c:83)
 ==22159==    by 0x873889: xzalloc (common-utils.c:93)
 ==22159==    by 0x6A34CB: allocate_value_contents (value.c:1036)
 ==22159==    by 0x6A3501: allocate_value (value.c:1047)
 ==22159==    by 0x6A790A: value_from_double (value.c:3656)
 ==22159==    by 0x6A9F2D: evaluate_subexp_standard (eval.c:745)
 ==22159==    by 0x7F31AF: evaluate_subexp_c (c-lang.c:716)
 ==22159==    by 0x6A8986: evaluate_subexp (eval.c:79)
 ==22159==    by 0x6A8BA3: evaluate_type (eval.c:174)
 ==22159==    by 0x817CCF: whatis_exp (typeprint.c:456)
 ==22159==    by 0x817EAA: ptype_command (typeprint.c:508)
 ==22159==
 type = long double
 (gdb)

Even if the target and host floating-point formats match, the length
of the types might still be different.  On x86, long double is the
80-bit extended precision type on both 32-bit and 64-bit ABIs, but by
default it is stored as 12 bytes on 32-bit, and 16 bytes on 64-bit,
for alignment reasons.  Several places in doublest.c already consider
this, but floatformat_to_doublest and floatformat_from_doublest miss
it.  E.g., convert_typed_floating and store_typed_floating,

Tested on x86-64 Fedora 23 with --enable-libmcheck, where it fixes the
crashed above.

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

	* doublest.c: Extend comments.
	(floatformat_to_doublest, floatformat_from_doublest): Copy the
	floatformat's total size, not the host type's size.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Assert that a floating type's length is at least as long as its format
@ 2016-03-09  3:19 sergiodj+buildbot
  2016-03-09  5:39 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-03-09  3:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b79497cb1cdc9b3053e5f0387bf3056c08c9bbdd ***

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

Assert that a floating type's length is at least as long as its format

This would have caught the HP/PA bug fixed in the previous patch:

 .../src/gdb/gdbtypes.c:4690: internal-error: arch_float_type: Assertion `len >= floatformat_totalsize_bytes (floatformats[0])' failed.
 A problem internal to GDB has been detected,
 further debugging may prove unreliable.
 Quit this debugging session? (y or n)

Tested on x86-64 Fedora 23, --enable-targets=all.

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

	* doublest.c (floatformat_totalsize_bytes): New function.
	(floatformat_from_type): Assert that the type's length is at least
	as long as the floatformat's totalsize.
	* doublest.h (floatformat_totalsize_bytes): New declaration.
	* gdbtypes.c (arch_float_type): Assert that the type's length is
	at least as long as the floatformat's totalsize.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Fix HP/PA GNU/Linux "long double" format
@ 2016-03-09  2:37 sergiodj+buildbot
  2016-03-09  4:14 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-03-09  2:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT aacca8a7a9c7f93955fa9dbf796b030ffce1b956 ***

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

Fix HP/PA GNU/Linux "long double" format

This:

 $ ./gdb -ex "set architecture hppa1.0" -ex "set osabi GNU/Linux" -ex "ptype 1.0L"

Shows that HPPA/Linux support for long doubles is broken.  It causes
GDB to access memory out of bounds.  With Valgrind, we see:

 The target architecture is assumed to be hppa1.0
 ==4371== Invalid write of size 8
 ==4371==    at 0x4C2F21F: memset (vg_replace_strmem.c:1224)
 ==4371==    by 0x8451C4: convert_doublest_to_floatformat (doublest.c:362)
 ==4371==    by 0x845F86: floatformat_from_doublest (doublest.c:769)
 ==4371==    by 0x84628E: store_typed_floating (doublest.c:873)
 ==4371==    by 0x6A7C3D: value_from_double (value.c:3662)
 ==4371==    by 0x6AA211: evaluate_subexp_standard (eval.c:745)
 ==4371==    by 0x7F306D: evaluate_subexp_c (c-lang.c:716)
 ==4371==    by 0x6A8C6A: evaluate_subexp (eval.c:79)
 ==4371==    by 0x6A8E87: evaluate_type (eval.c:174)
 ==4371==    by 0x817B8D: whatis_exp (typeprint.c:456)
 ==4371==    by 0x817D68: ptype_command (typeprint.c:508)
 ==4371==    by 0x5F2977: do_cfunc (cli-decode.c:105)
 ==4371==  Address 0x8998d18 is 0 bytes after a block of size 8 alloc'd
 ==4371==    at 0x4C2AA98: calloc (vg_replace_malloc.c:711)
 ==4371==    by 0x8732B6: xcalloc (common-utils.c:83)
 ==4371==    by 0x8732F5: xzalloc (common-utils.c:93)
 ==4371==    by 0x6A37AF: allocate_value_contents (value.c:1036)
 ==4371==    by 0x6A37E5: allocate_value (value.c:1047)
 ==4371==    by 0x6A7BEE: value_from_double (value.c:3656)
 ==4371==    by 0x6AA211: evaluate_subexp_standard (eval.c:745)
 ==4371==    by 0x7F306D: evaluate_subexp_c (c-lang.c:716)
 ==4371==    by 0x6A8C6A: evaluate_subexp (eval.c:79)
 ==4371==    by 0x6A8E87: evaluate_type (eval.c:174)
 ==4371==    by 0x817B8D: whatis_exp (typeprint.c:456)
 ==4371==    by 0x817D68: ptype_command (typeprint.c:508)

The trouble is that hppa_linux_init_abi overrides the default
long_double_bit set by the generic hppa-tdep.c:

  set_gdbarch_long_double_bit (gdbarch, 128);
  set_gdbarch_long_double_format (gdbarch, floatformats_ia64_quad);

with:

  /* On hppa-linux, currently, sizeof(long double) == 8.  There has been
     some discussions to support 128-bit long double, but it requires some
     more work in gcc and glibc first.  */
  set_gdbarch_long_double_bit (gdbarch, 64);

which misses overriding the long_double_format, so we end with a weird
combination of:

  set_gdbarch_long_double_bit (gdbarch, 64);
  set_gdbarch_long_double_format (gdbarch, floatformats_ia64_quad);

Weird because floatformats_ia64_quad's totalsize is longer than 64-bits.

The floatformat conversion routines use the struct floatformat's
totalsize (in bits) to know how much to copy/convert, thus the buffer
overruns.

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

	* hppa-linux-tdep.c (hppa_linux_init_abi): Set the long double
	format to floatformats_ieee_double.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Group common symbol checking together
@ 2016-03-08 13:50 sergiodj+buildbot
  2016-03-08 16:03 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-03-08 13:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 202ac193bbbecc96a4978d1ac3d17148253f9b01 ***

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

Group common symbol checking together

	PR ld/19579
	* elflink.c (_bfd_elf_merge_symbol): Group common symbol checking
	together.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Allow zero length archive elements.
@ 2016-03-07 17:40 sergiodj+buildbot
  2016-03-07 21:39 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-03-07 17:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4fc874242f8f1bf17cf6e65b159dd804e793e6cd ***

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

Allow zero length archive elements.

bfd	PR binutils/19775
	* archive.c (bfd_generic_openr_next_archived_file): Allow zero
	length elements in the archive.

binutils PR binutils/19775
	* testsuite/binutils-all/ar.exp (proc empty_archive): New proc.
	Run the new proc.
	* testsuite/binutils-all/empty: New, empty, file.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [AArch64] Create .got section if _GLOBAL_OFFSET_TABLE_ referenced
@ 2016-03-07 15:51 sergiodj+buildbot
  2016-03-07 18:42 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-03-07 15:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 18f822a08fd5cb8fed8b0b318e7945545c255081 ***

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

[AArch64] Create .got section if _GLOBAL_OFFSET_TABLE_ referenced

2016-03-07  Jiong Wang  <jiong.wang@arm.com>

bfd/
  * elfnn-aarch64.c (elfNN_aarch64_check_relocs): Always create .got section
  if the symbol "_GLOBAL_OFFSET_TABLE_" referenced.

ld/
  * testsuite/ld-aarch64/implicit_got_section_1.s: New test source file.
  * testsuite/ld-aarch64/implicit_got_section_1.d: New test expected result.
  * testsuite/ld-aarch64/aarch64-elf.exp: Run new test.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Add const qualifiers at various places.
@ 2016-03-07 15:39 sergiodj+buildbot
  2016-03-07 17:05 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-03-07 15:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f86f586366275bbb5ae77520eb990769f05a3030 ***

Author: Trevor Saunders <tbsaunde+binutils@tbsaunde.org>
Branch: master
Commit: f86f586366275bbb5ae77520eb990769f05a3030

Add const qualifiers at various places.

opcodes	* mcore-opc.h: Add const qualifiers.
	* microblaze-opc.h (struct op_code_struct): Likewise.
	* sh-opc.h: Likewise.
	* tic4x-dis.c (tic4x_print_indirect): Likewise.
	(tic4x_print_op): Likewise.

include	* opcode/dlx.h (struct dlx_opcode): Add const qualifiers.
	* opcode/h8300.h (struct h8_opcode): Likewise.
	* opcode/hppa.h (struct pa_opcode): Likewise.
	* opcode/msp430.h: Likewise.
	* opcode/spu.h (struct spu_opcode): Likewise.
	* opcode/tic30.h (struct _register): Likewise.
	* opcode/tic4x.h (struct tic4x_register): Likewise.
	(struct tic4x_cond): Likewise.
	(struct tic4x_indirect): Likewise.
	(struct tic4x_inst): Likewise.
	* opcode/visium.h (struct reg_entry): Likewise.

gas	* config/tc-arc.c: Add const qualifiers.
	* config/tc-h8300.c (md_begin): Likewise.
	* config/tc-ia64.c (print_prmask): Likewise.
	* config/tc-msp430.c (msp430_operands): Likewise.
	* config/tc-nds32.c (struct suffix_name): Likewise.
	(struct nds32_parse_option_table): Likewise.
	(struct nds32_set_option_table): Likewise.
	(do_pseudo_pushpopm): Likewise.
	(do_pseudo_pushpop_stack): Likewise.
	(nds32_relax_relocs): Likewise.
	(nds32_flag): Likewise.
	(struct nds32_hint_map): Likewise.
	(nds32_find_reloc_table): Likewise.
	(nds32_match_hint_insn): Likewise.
	* config/tc-s390.c: Likewise.
	* config/tc-sh.c (get_specific): Likewise.
	* config/tc-tic30.c: Likewise.
	* config/tc-tic4x.c (tic4x_inst_add): Likewise.
	(tic4x_indirect_parse): Likewise.
	* config/tc-vax.c (vax_cons): Likewise.
	* config/tc-z80.c (struct reg_entry): Likewise.
	* config/tc-epiphany.c (md_assemble): Adjust.
	(epiphany_assemble): New function.
	(epiphany_elf_section_rtn): Call do_align directly.
	(epiphany_elf_section_text): Likewise.
	* config/tc-ip2k.c (ip2k_elf_section_rtn): Likewise.
	(ip2k_elf_section_text): Likewise.
	* read.c (do_align): Make it not static.
	* read.h (do_align): New prototype.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Set executable bit on analyze-racy-logs.py
@ 2016-03-06 22:42 sergiodj+buildbot
  2016-03-06 23:54 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-03-06 22:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5eb264df40e1e3ffeb2627456889a1dc5df00f16 ***

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

Set executable bit on analyze-racy-logs.py

I forgot to do it in my previous commit.  This is necessary because we
execute the script directly on gdb/testsuite/Makefile.in.

gdb/testsuite/ChangeLog:
2016-03-06  Sergio Durigan Junior  <sergiodj@redhat.com>

	* analyze-racy-logs.py: Set executable bit.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Improve analysis of racy testcases
@ 2016-03-06  1:57 sergiodj+buildbot
  2016-03-06  3:57 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-03-06  1:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fb6a751f5f1fe7912e84dd90d06395c357da47c2 ***

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

Improve analysis of racy testcases

This is an initial attempt to introduce some mechanisms to identify
racy testcases present in our testsuite.  As can be seen in previous
discussions, racy tests are really bothersome and cause our BuildBot
to pollute the gdb-testers mailing list with hundreds of
false-positives messages every month.  Hopefully, identifying these
racy tests in advance (and automatically) will contribute to the
reduction of noise traffic to gdb-testers, maybe to the point where we
will be able to send the failure messages directly to the authors of
the commits.

I spent some time trying to decide the best way to tackle this
problem, and decided that there is no silver bullet.  Racy tests are
tricky and it is difficult to catch them, so the best solution I could
find (for now?) is to run our testsuite a number of times in a row,
and then compare the results (i.e., the gdb.sum files generated during
each run).  The more times you run the tests, the more racy tests you
are likely to detect (at the expense of waiting longer and longer).
You can also run the tests in parallel, which makes things faster (and
contribute to catching more racy tests, because your machine will have
less resources for each test and some of them are likely to fail when
this happens).  I did some tests in my machine (8-core i7, 16GB RAM),
and running the whole GDB testsuite 5 times using -j6 took 23 minutes.
Not bad.

In order to run the racy test machinery, you need to specify the
RACY_ITER environment variable.  You will assign a number to this
variable, which represents the number of times you want to run the
tests.  So, for example, if you want to run the whole testsuite 3
times in parallel (using 2 cores), you will do:

  make check RACY_ITER=3 -j2

It is also possible to use the TESTS variable and specify which tests
you want to run:

  make check TEST='gdb.base/default.exp' RACY_ITER=3 -j2

And so on.  The output files will be put at the directory
gdb/testsuite/racy_outputs/.

After make invokes the necessary rules to run the tests, it finally
runs a Python script that will analyze the resulting gdb.sum files.
This Python script will read each file, and construct a series of sets
based on the results of the tests (one set for FAIL's, one for
PASS'es, one for KFAIL's, etc.).  It will then do some set operations
and come up with a list of unique, sorted testcases that are racy.
The algorithm behind this is:

  for state in PASS, FAIL, XFAIL, XPASS...; do
    if a test's state in every sumfile is $state; then
      it is not racy
    else
      it is racy

(The algorithm is actually a bit more complex than that, because it
takes into account other things in order to decide whether the test
should be ignored or not).

IOW, a test must have the same state in every sumfile.

After processing everything, the script prints the racy tests it could
identify on stdout.  I am redirecting this to a file named racy.sum.

Something else that I wasn't sure how to deal with was non-unique
messages in our testsuite.  I decided to do the same thing I do in our
BuildBot: include a unique identifier in the end of message, like:

  gdb.base/xyz.exp: non-unique message
  gdb.base/xyz.exp: non-unique message <<2>>

This means that you will have to be careful about them when you use
the racy.sum file.

I ran the script several times here, and it did a good job catching
some well-known racy tests.  Overall, I am satisfied with this
approach and I think it will be helpful to have it upstream'ed.  I
also intend to extend our BuildBot and create new, specialized
builders that will be responsible for detecting the racy tests every X
number of days.

2016-03-05  Sergio Durigan Junior  <sergiodj@redhat.com>

	* Makefile.in (DEFAULT_RACY_ITER): New variable.
	(CHECK_TARGET_TMP): Likewise.
	(check-single-racy): New rule.
	(check-parallel-racy): Likewise.
	(TEST_TARGETS): Adjust rule to account for RACY_ITER.
	(do-check-parallel-racy): New rule.
	(check-racy/%.exp): Likewise.
	* README (Racy testcases): New section.
	* analyze-racy-logs.py: New file.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Fix argument passing for call
@ 2016-03-05 12:31 sergiodj+buildbot
  2016-03-06  1:57 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-03-05 12:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cb86f3880e61c79e59b9225e79c3544a1fcd8005 ***

Author: Denis Chertykov <chertykov@gmail.com>
Branch: master
Commit: cb86f3880e61c79e59b9225e79c3544a1fcd8005

Fix argument passing for call

When calling function with argument of size more than 8 bytes fails with
an error "That operation is not available on integers of more than 8 bytes.".
avr-gdb considers only 8 bytes (sizeof(long long)) in case of passing the
argument in registers. When the argument is of size more than 8 byte
then the utility function to extract bytes failed with the above error.

    gdb/
	* avr-tdep.c (AVR_LAST_ARG_REGNUM): Define.
        (avr_push_dummy_call): Correct last needed argument register.
        Write MSB of argument into register and subsequent bytes into
        other registers in decreasing order.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] ARM process record: VMOV
@ 2016-03-04 17:01 sergiodj+buildbot
  2016-03-04 20:35 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-03-04 17:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f1771dcebf80c75a13ca456491ddfb9b43fcaddf ***

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

ARM process record: VMOV

ARM process record gets the wrong register number for VMOV (from core
register to single-precision register).  That is, we should record
the D register rather than the S pseudo register.  The patch also
removes the condition "bit (arm_insn_r->arm_insn, 20)" check, which
has been checked above.

It fixes the following internal error,

(gdb) PASS: gdb.reverse/finish-precsave.exp: BP at end of main
continue^M
Continuing.^M
../../binutils-gdb/gdb/regcache.c:649: internal-error: regcache_raw_read: Assertion `regnum >= 0 && regnum < regcache->descr->nr_raw_registers' failed.^M
A problem internal to GDB has been detected,FAIL: gdb.reverse/finish-precsave.exp: run to end of main (GDB internal error)

gdb:

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

	* arm-tdep.c (arm_record_vdata_transfer_insn): Simplify the
	condition check.  Record the right D register number.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Tweak ARM process record
@ 2016-03-04 16:10 sergiodj+buildbot
  2016-03-04 18:57 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-03-04 16:10 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ca92db2d5885c03d3e0ed23c96b5c6ab336d908d ***

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

Tweak ARM process record

This patch removes the printing "Process record does not support",
and do the print by calling arm_record_unsupported_insn in the
caller.  Also, call arm_record_extension_space only when condition
is 0xf.

gdb:

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

	* arm-tdep.c (arm_record_extension_space): Remove code
	printing "Process record does not support".
	(arm_record_data_proc_misc_ld_str): Likewise.
	(decode_insn): Call arm_record_extension_space if condition
	is 0xf.  Call arm_record_unsupported_insn if ret isn't
	ARM_RECORD_SUCCESS.  Use 'ret' instead of 'insn_id' to hold
	the value of thumb2_record_decode_insn_handler.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] feature_to_c.sh: Print help when passing no arguments
@ 2016-03-04 15:16 sergiodj+buildbot
  2016-03-04 17:18 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-03-04 15:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 73519cce7cbe31609a2aa9c27955555237a0c51f ***

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

feature_to_c.sh: Print help when passing no arguments

I found that odd that passing no arguments to feature_to_c.sh produces
this:

$ ./feature_to_c.sh
./feature_to_c.sh: 23: shift: can't shift that many

but passing one argument shows the help:

$ ./feature_to_c.sh hello
Usage: ./feature_to_c.sh OUTPUTFILE INPUTFILE...

This patch changes the script to show the help in both cases.

gdb/ChangeLog:

	* features/feature_to_c.sh: Print the help when passing no
	argument.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Treat common symbol in executable as definition
@ 2016-03-04 14:50 sergiodj+buildbot
  2016-03-04 15:56 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-03-04 14:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 07492f668d2173da7a2bda3707ff0985e0f460b6 ***

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

Treat common symbol in executable as definition

Common symbol in executable is a definition, which overrides definition
from shared objects.  When linker sees a new definition from a shared
object, the new dynamic definition should be overridden by the previous
common symbol in executable.

bfd/

	PR ld/19579
	* elflink.c (_bfd_elf_merge_symbol): Treat common symbol in
	executable as definition if the new definition comes from a
	shared library.

ld/

	PR ld/19579
	* testsuite/ld-elf/pr19579a.c: New file.
	* testsuite/ld-elf/pr19579b.c: Likewise.
	* testsuite/ld-elf/shared.exp: Run PR ld/19579 test.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [ARM] Add feature check for ARMv8.1 AdvSIMD instructions.
@ 2016-03-04 11:45 sergiodj+buildbot
  2016-03-04 12:55 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-03-04 11:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 643afb90da9066e9d3c6dc721920b14ed343bec9 ***

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

[ARM] Add feature check for ARMv8.1 AdvSIMD instructions.

gas/
2016-03-04  Matthew Wahab  <matthew.wahab@arm.com>

	* config/gas/tc-arm.c (fpu_neon_ext_v8_1): Restrict to the ARMv8.1 RDMA
	feature.
	(record_feature_use): New.
	(mark_feature_used): Use record_feature_use.
	(do_neon_qrdmlah): New.
	(insns): Use do_neon_qrdmlah for vqrdmlah and vqrdmlsh and
	variants.
	(arm_extensions): Put into alphabetical order.  Re-indent "simd"
	and "rdma" entries.  Fix the incorrect merge value for "+rdma".
	* testsuite/gas/arm/armv8-a+rdma-warning.d: New.
	* testsuite/gas/arm/armv8-a+rdma.d: Add assembler command line options.
	Make source file explicit.
	* testsuite/gas/arm/armv8-a+rdma.l: New.
	* testsuite/gas/arm/armv8-a+rdma.s: Remove .arch and .arch_extension
	directives.  Fix white-space.
	* testsuite/gas/arm/armv8_1-a+simd.d: New.

include/opcode
2016-03-04  Matthew Wahab  <matthew.wahab@arm.com>

	* arm.h (ARM_ARCH_V8_1A): Add FPU_NEON_EXT_RDMA.
	(ARM_CPU_HAS_FEATURE): Add comment.

Change-Id: Ie19250e8fa50aed44e44ab40ff30b04b38bc1a3d


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] get_symbols() plugin API tweak to support --start-lib/--end-lib.
@ 2016-03-03 21:03 sergiodj+buildbot
  2016-03-04  1:20 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-03-03 21:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 95ecdfbfcbf508919652a0254ee2b8c6572a949e ***

Author: Evgenii Stepanov <eugenis@google.com>
Branch: master
Commit: 95ecdfbfcbf508919652a0254ee2b8c6572a949e

get_symbols() plugin API tweak to support --start-lib/--end-lib.

Let the plugin know that a file is not being included in the link by
returning LDPS_NO_SYMS from get_symbols().

include/
	* plugin-api.h (enum ld_plugin_tag): Add LDPT_GET_SYMBOLS_V3.

gold/
	* plugin.h (Pluginobj::get_symbol_resolution_info): Add version
	parameter.
	* plugin.cc (get_symbols_v3): New function.
	(Plugin::load): Add LDPT_GET_SYMBOLS_V3.
	(Pluginobj::get_symbol_resolution_info): Return LDPS_NO_SYMS when using
	new version.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Fix bugs in the simulation of the AArch64's ADDP, FADDP, LD1, CCMP and CCMP instructions.
@ 2016-03-03 15:34 sergiodj+buildbot
  2016-03-03 22:33 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-03-03 15:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 57aa17424380be1c3e362a5601071f1f3a6f74f6 ***

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

Fix bugs in the simulation of the AArch64's ADDP, FADDP, LD1, CCMP and CCMP instructions.

	* simulator.c (set_flags_for_sub32): Correct type of signbit.
	(CondCompare): Swap interpretation of bit 30.
	(DO_ADDP): Delete macro.
	(do_vec_ADDP): Copy source registers before starting to update
	destination register.
	(do_vec_FADDP): Likewise.
	(do_vec_load_store): Fix computation of sizeof_operation.
	(rbit64): Fix type of constant.
	(aarch64_step): When displaying insn value, display all 32 bits.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Update comments to start_step_over
@ 2016-03-03 10:36 sergiodj+buildbot
  2016-03-03 21:03 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-03-03 10:36 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c40c8d4b6793b71eed7cf9fa7467edda2271dc86 ***

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

Update comments to start_step_over

I happen to see that comments to start_step_over isn't in sync with
code, so this patch is to update the comments.

gdb/gdbserver:

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

	* linux-low.c: Update comments to start_step_over.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Reformat gdb.base/step-over-syscall.exp
@ 2016-03-03 10:20 sergiodj+buildbot
  2016-03-03 17:39 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-03-03 10:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ea50786226737509a8f4c2734699a5fc15cc63c4 ***

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

Reformat gdb.base/step-over-syscall.exp

gdb/testsuite:

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

	* gdb.base/step-over-syscall.exp (disp_step_cross_syscall): Fix
	code format.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Step over fork/vfork syscall insn in gdbserver
@ 2016-03-03 10:00 sergiodj+buildbot
  2016-03-03 15:08 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-03-03 10:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 92fa70b0bd8690d979357ebcdb501a9e4aa42ea6 ***

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

Step over fork/vfork syscall insn in gdbserver

We can also extend disp-step-syscall.exp to test GDBserver step over
breakpoint on syscall instruction.  That is, we set a breakpoint
with a false condition on syscall instruction, so that GDBserver will
step over it.

This test triggers a GDBserver internal error, which can be fixed by
this series.

(gdb) PASS: gdb.base/disp-step-syscall.exp: fork: break cond on target: break on syscall insns
continue^M
Continuing.^M
Remote connection closed^M
(gdb) FAIL: gdb.base/disp-step-syscall.exp: fork: break cond on target: continue to fork again

In GDBserver, there is an internal error,

/home/yao/SourceCode/gnu/gdb/git/gdb/gdbserver/linux-low.c:1922: A problem internal to GDBserver has been detected.
unsuspend LWP 25554, suspended=-1

the simplified reproducer is like,

$ ./gdb ./testsuite/outputs/gdb.base/disp-step-syscall/disp-step-fork
(gdb) b main
(gdb) c
(gdb) disassemble fork // in order to find the address of insn 'syscall'
....
   0x00007ffff7ad6023 <+179>:	syscall
(gdb) b *0x00007ffff7ad6023 if main == 0
(gdb) c

gdb/testsuite:

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

	* gdb.base/disp-step-syscall.exp (break_cond_on_syscall): New.
	If target supports condition evaluation on target, invoke
	break_cond_on_syscall for fork and vfork.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Step over syscalll insn with disp-step on and off
@ 2016-03-03  9:51 sergiodj+buildbot
  2016-03-03 13:28 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-03-03  9:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e197ad3c87723a2bdf383d38fcfa3eaa4fa1ba12 ***

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

Step over syscalll insn with disp-step on and off

disp-step-syscall.exp was added to test displaced stepping over syscall
instructions, in which we set breakpoint on syscall instruction, and
step over it.  In fact, we can extend the test to non-displaced-stepping
case.  This patch wraps the test with displaced stepping on and off.
Note that the indentation and format isn't adjusted here to make this
patch easy to read.  The following patch will fix the format separately.

gdb/testsuite:

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

	* gdb.base/disp-step-syscall.exp: Don't invoke
	support_displaced_stepping.
	(disp_step_cross_syscall): Test with displaced stepping off and
	on if supported.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Refactor gdb.base/disp-step-syscall.exp for general step over test
@ 2016-03-03  9:42 sergiodj+buildbot
  2016-03-03 12:01 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-03-03  9:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0b47da9f176aa73854f1ff8ae00afda11a4f338a ***

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

Refactor gdb.base/disp-step-syscall.exp for general step over test

This patch moves some code out of disp_step_cross_syscall to a new proc
check_pc_after_cross_syscall and setup.  Procedure setup is to start a
fresh GDB and compute the syscall instruction address.

gdb/testsuite:

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

	* gdb.base/disp-step-syscall.exp (check_pc_after_cross_syscall): New
	proc.
	(setup): New proc.
	(disp_step_cross_syscall): Move code to check_pc_after_cross_syscall
	and setup.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Call enqueue_pending_signal in linux_resume_one_lwp_throw
@ 2016-03-02 17:42 sergiodj+buildbot
  2016-03-03  9:31 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-03-02 17:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fdbd04a8adef3a48eeac7702e9243c7c31e47256 ***

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

Call enqueue_pending_signal in linux_resume_one_lwp_throw

Replace the code which is exactly what enqueue_pending_signal does.

gdb/gdbserver:

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

	* linux-low.c (linux_resume_one_lwp_throw): Replace code with
	enqueue_pending_signal.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] testsuite: Fix timeout issues during print of vla-arrays.
@ 2016-03-02 17:06 sergiodj+buildbot
  2016-03-03  0:30 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-03-02 17:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 07e448ade17bc8fb52469a5b2184017f94669bd6 ***

Author: bernhard.heckel <bernhard.heckel@intel.com>
Branch: master
Commit: 07e448ade17bc8fb52469a5b2184017f94669bd6

testsuite: Fix timeout issues during print of vla-arrays.

Printing and resolving of dynamic array's causes sporadic timeout issues on loaded systems.

2016-03-02  Bernhard Heckel  <bernhard.heckel@intel.com>

gdb/testsuite/Changelog:

     * gdb.fortran/vla-history.exp: Lookup array elements and printing exceeds timeout.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [OBV] gdbserver: Only write ipa_tdesc_idx if agent is actually loaded.
@ 2016-03-02 16:31 sergiodj+buildbot
  2016-03-03  8:53 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-03-02 16:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6896a8fa1e1d24a8fcc9b30efc0b195246b46029 ***

Author: Marcin Kocielnicki <koriakin@0x04.net>
Branch: master
Commit: 6896a8fa1e1d24a8fcc9b30efc0b195246b46029

[OBV] gdbserver: Only write ipa_tdesc_idx if agent is actually loaded.

Fixes rather embarassing gdb.trace regressions.

gdb/gdbserver/ChangeLog:

	* tracepoint.c (cmd_qtstart): Only set ipa_tdesc_idx if agent
	is actually loaded.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] testsuite: Remove unnecessary code in fortran vla-history test.
@ 2016-03-02 16:16 sergiodj+buildbot
  2016-03-03  7:00 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-03-02 16:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 065ab6dc804575bce7df58477b2cfcb2b2a6eafb ***

Author: Bernhard Heckel <bernhard.heckel@intel.com>
Branch: master
Commit: 065ab6dc804575bce7df58477b2cfcb2b2a6eafb

testsuite: Remove unnecessary code in fortran vla-history test.

testsuite: Remove unnecessary code in fortran vla-history test.

2016-03-02  Bernhard Heckel  <bernhard.heckel@intel.com>

gdb/testsuite/Changelog:

     * gdb.fortran/vla-history.exp: Remove breakpoint.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] testsuite: Fix run to main issue introduced by GCC 5.x.
@ 2016-03-02 15:53 sergiodj+buildbot
  2016-03-02 22:36 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-03-02 15:53 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9ac2d526d9ae70272bf7fc436f2e3ad11a84d58b ***

Author: bernhard.heckel <bernhard.heckel@intel.com>
Branch: master
Commit: 9ac2d526d9ae70272bf7fc436f2e3ad11a84d58b

testsuite: Fix run to main issue introduced by GCC 5.x.

Adding a dummy assignment as a new breakpoint anchor because
breakpoint on return statement doesn't work for GCC 5.x.

2016-03-02  Bernhard Heckel  <bernhard.heckel@intel.com>

gdb/testsuite/Changelog:

     * gdb.cp/vla-cxx.cc: Insert dummy assignment as anchor for an breakpoint.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] testsuite: Nullify pointers before first usage.
@ 2016-03-02 15:43 sergiodj+buildbot
  2016-03-02 20:46 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-03-02 15:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 178073690aec73fdb5f4452b49f108407edde700 ***

Author: Bernhard Heckel <bernhard.heckel@intel.com>
Branch: master
Commit: 178073690aec73fdb5f4452b49f108407edde700

testsuite: Nullify pointers before first usage.

Nullify pointers to avoid an undefined association status.

2016-03-02  Bernhard Heckel  <bernhard.heckel@intel.com>

gdb/testsuite/Changelog:

     * gdb.mi/vla.f90: Nullify pointer after declaration.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Add new maintainer to Write After Approval.
@ 2016-03-02 15:30 sergiodj+buildbot
  2016-03-02 18:53 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-03-02 15:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 650beae39d31e5ce2680649e2fb697e0e4a9e3eb ***

Author: Bernhard Heckel <bernhard.heckel@intel.com>
Branch: master
Commit: 650beae39d31e5ce2680649e2fb697e0e4a9e3eb

Add new maintainer to Write After Approval.

Add new maintainer to Write After Approval.

2016-03-02  Bernhard Heckel  <bernhard.heckel@intel.com>

    * MAINTAINERS (Write After Approval): Add Bernhard Heckel.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Regenerate or1k opcodes file
@ 2016-03-02 14:03 sergiodj+buildbot
  2016-03-02 15:36 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-03-02 14:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d11698cd0d9bb22b51598ee37af0aaf1d44ec5c7 ***

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

Regenerate or1k opcodes file

CGEN patch now committed upstream to use hex numbers for large enums.

	* or1k-desc.h: Regenerate.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Regenerate bfd files.
@ 2016-03-02  4:03 sergiodj+buildbot
  2016-03-02  7:42 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-03-02  4:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 70a5df4fe30fd37166c3b62071fd816e49082d2e ***

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

Regenerate bfd files.

	* Makefile.in: Regenerate.
	* po/SRC-POTFILES.in: Regenerate.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Regenerate rl78 opcodes file
@ 2016-03-02  3:46 sergiodj+buildbot
  2016-03-02 14:03 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-03-02  3:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c697cf0b2b85cb1231e2c76c52cfed43770aa04a ***

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

Regenerate rl78 opcodes file

For newer comments.

	* rl78-decode.c: Regenerate.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Fix shift left warning at source
@ 2016-03-02  3:28 sergiodj+buildbot
  2016-03-02  5:54 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-03-02  3:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 62de1c630f16c21418464727692bcd29e23ef1b0 ***

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

Fix shift left warning at source

cpu/
	* fr30.cpu (f-m4): Replace -1 << 4 with -16.
opcodes/
	* fr30-ibld.c: Regenerate.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Fix gdb.trace/ftrace-lock.c compilation
@ 2016-03-01 18:47 sergiodj+buildbot
  2016-03-02  0:11 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-03-01 18:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 86e501afd46d7f0d31738bd62457593401d79bad ***

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

Fix gdb.trace/ftrace-lock.c compilation

Fixes, on F23:

 .../src/gdb/testsuite/gdb.trace/ftrace-lock.c: In function 'gdb_agent_gdb_collect':
 .../src/gdb/testsuite/gdb.trace/ftrace-lock.c:50:3: warning: implicit declaration of function 'sleep' [-Wimplicit-function-declaration]
    sleep (1);
    ^

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

	* gdb.trace/ftrace-lock.c: Include <unistd.h>.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Fix gdb.threads/watchpoint-fork*.c compilation
@ 2016-03-01 17:53 sergiodj+buildbot
  2016-03-01 21:59 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-03-01 17:53 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1e903e320352db86233e1dd2d10fd140f5d4a887 ***

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

Fix gdb.threads/watchpoint-fork*.c compilation

This testcase currently fails to compile on Fedora 23:

 .../src/gdb/testsuite/gdb.threads/watchpoint-fork-mt.c: In function 'start':
 .../src/gdb/testsuite/gdb.threads/watchpoint-fork-mt.c:70:11: warning: implicit declaration of function 'pthread_yield' [-Wimplicit-function-declaration]
	i = pthread_yield ();
	    ^
 .../src/gdb/testsuite/gdb.threads/watchpoint-fork-child.c: In function 'forkoff':
 .../src/gdb/testsuite/gdb.threads/watchpoint-fork-child.c:114:8: warning: implicit declaration of function 'pthread_yield' [-Wimplicit-function-declaratio
 n]
     i = pthread_yield ();
	 ^
 /tmp/ccUkNIsI.o: In function `start':
 .../src/gdb/testsuite/gdb.threads/watchpoint-fork-mt.c:70: undefined reference to `pthread_yield'
 (...)
 collect2: error: ld returned 1 exit status

 UNSUPPORTED: gdb.threads/watchpoint-fork.exp: child: multithreaded: Couldn't compile watchpoint-fork-child.c: unrecognized error
 UNTESTED: gdb.threads/watchpoint-fork.exp: child: multithreaded: watchpoint-fork.exp
 testcase .../src/gdb/testsuite/gdb.threads/watchpoint-fork.exp completed i

The glibc manual says, on _GNU_SOURCE:

 "You should define these macros by using #define preprocessor
 directives at the top of your source code files. These directives must
 come before any #include of a system header file."

I instead put it in the header all the .c files of the testcase must
include anyway.

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

	* gdb.threads/watchpoint-fork-child.c: Include "watchpoint-fork.h"
	before anything else.
	* gdb.threads/watchpoint-fork-mt.c: Likewise.  Don't define
	_GNU_SOURCE here.
	* gdb.threads/watchpoint-fork-st.c: Include "watchpoint-fork.h"
	before anything else.
	* gdb.threads/watchpoint-fork.h: Define _GNU_SOURCE.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Fix gdb.base/catch-fork-kill.c compilation
@ 2016-03-01 17:26 sergiodj+buildbot
  2016-03-01 20:19 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-03-01 17:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6ccb54e2a82ca934f6d430b87ab015b7bfecc413 ***

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

Fix gdb.base/catch-fork-kill.c compilation

Fixes:

 Running .../src/gdb/testsuite/gdb.base/catch-fork-kill.exp ...
 gdb compile failed, .../src/gdb/testsuite/gdb.base/catch-fork-kill.c: In function 'main':
 .../src/gdb/testsuite/gdb.base/catch-fork-kill.c:81:4: warning: implicit declaration of function 'wait' [-Wimplicit-function-declaration]
     wait (NULL);
     ^

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

	* gdb.base/catch-fork-kill.c: Include <sys/wait.h>.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Fix output path for arm-disp-step.exp
@ 2016-03-01 15:41 sergiodj+buildbot
  2016-03-01 18:32 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-03-01 15:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 30ca9da1193ec4c82cc67a2ec2e6fb6adac7ab84 ***

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

Fix output path for arm-disp-step.exp

This patch fixes the following error,

ERROR: (/scratch/yao/gdb/build-git/arm-linux-gnueabihf/gdb/testsuite/outputs/gdb.arch/arm-disp-step/arm-disp-step) No such file or directory
FAIL: gdb.arch/arm-disp-step.exp: Can't run to main

gdb/testsuite:

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

	* gdb.arch/arm-disp-step.exp: Use standard_testfile and
	prepare_for_testing.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Compile gdb.arch/arm-neon.c with "quiet"
@ 2016-03-01 15:31 sergiodj+buildbot
  2016-03-01 17:01 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-03-01 15:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT dc856b382065cdfab3f9bb484c07e182950eb4d4 ***

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

Compile gdb.arch/arm-neon.c with "quiet"

When we compile gdb.arch/arm-neon.c with options that don't enable NEON,
there are many error/warnings emitted into gdb.sum, which is annoying.
This patch fixes it by passing quiet to prepare_for_testing.

gdb/testsuite:

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

	* gdb.arch/arm-neon.exp: Pass quiet to prepare_for_testing.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] S390: Fix output path for s390-tdbregs test case
@ 2016-03-01 12:05 sergiodj+buildbot
  2016-03-01 15:19 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-03-01 12:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4a9321595003d86dd4794d0edab071f91989808e ***

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

S390: Fix output path for s390-tdbregs test case

Since test artifacts are always organized in a directory hierarchy, the
s390-tdbregs test case is not executed correctly any more.  This is
because it uses an obsolete way of constructing the executable's path.

This change invokes prepare_for_testing instead.

gdb/testsuite/ChangeLog:

	* gdb.arch/s390-tdbregs.exp: Use prepare_for_testing instead of
	manually constructing the output path.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] aarch64-linux process record: more syscalls
@ 2016-02-29 17:29 sergiodj+buildbot
  2016-02-29 21:29 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-02-29 17:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d521906965b3e94648a723a13576236aaba301d0 ***

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

aarch64-linux process record: more syscalls

The last patch supports several syscalls in linux-record.c, so now
GDB aarch64-linux backend can return these canonicalized syscall numbers
per aarch64 syscall number.

This patch fixes the following fails,

Process record and replay target doesn't support syscall number 59^M
Process record: failed to record execution log.^M
^M
Program stopped.^M
0x00000020000eab28 in pipe () from /lib/aarch64-linux-gnu/libc.so.6^M
(gdb) FAIL: gdb.reverse/pipe-reverse.exp: continue to breakpoint: marker2

Process record and replay target doesn't support syscall number 59^M
Process record: failed to record execution log.^M
^M
Program stopped.^M
0x00000020000eab28 in pipe () from /lib/aarch64-linux-gnu/libc.so.6^M
(gdb) FAIL: gdb.reverse/readv-reverse.exp: continue to breakpoint: marker2

gdb:

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

	* aarch64-linux-tdep.c (aarch64_canonicalize_syscall): Support
	eventfd2, eventfd2, dup3, inotify_init1, fallocate and pipe2.
	Return gdb_sys_epoll_create1 instead of gdb_sys_epoll_create
	for aarch64_sys_epoll_create1.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [ARC] Local symbols relocation cleanup
@ 2016-02-29 16:04 sergiodj+buildbot
  2016-02-29 18:22 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-02-29 16:04 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 841fdfcdd9caa69f3ad7560a2806d421e23f598a ***

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

[ARC] Local symbols relocation cleanup

bfd/
2016-02-29  Cupertino Miranda  <cmiranda@synopsys.com>

	* elf32-arc.c (elf_arc_relocate_section): Added rules to fix the
	relocation addend when sections get merged.

gas/
2016-02-29  Cupertino Miranda  <cmiranda@synopsys.com>
	    Claudiu Zissulescu  <Claudiu.Zissulescu@synopsys.com>

        * config/tc-arc.c (arc_extra_reloc): Change size to 0.
        (tc_arc_fix_adjustable): Changed default return value to 1.
        * testsuite/gas/arc/j.d: Updated expected symbol
        * testsuite/gas/arc/jl.d: Likewise
        * testsuite/gas/arc/relax-avoid1.d: Likewise
        * testsuite/gas/arc/st.d: Likewise

ld/
2016-02-29 Cupertino Miranda  <cmiranda@synopsys.com>

	* testsuite/ld-elf/merge.d: Removed xfail for ARC.
	* testsuite/ld-elf/merge2.d: Likewise.
	* testsuite/ld-elf/merge3.d: Likewise.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [ARC] General fixes.
@ 2016-02-29 15:24 sergiodj+buildbot
  2016-02-29 16:49 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-02-29 15:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7e4588997ebdddefc48d8be2d51a715822817c0e ***

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

[ARC] General fixes.

bfd/
2016-02-29  Cupertino Miranda <Cupertino.Miranda@synopsys.com>

	* elf32-arc.c (arc_elf_final_write_processing): Add condition to
	the flag change.
        (elf_arc_relocate_section): Fixes and conditions to support PIE.
	Assert for code sections dynamic relocs.

gas/
2016-02-29  Claudiu Zissulescu  <Claudiu.Zissulescu@synopsys.com>

	* config/tc-arc.c: Enable code density instructions for ARC EM.

ld/
2016-02-29  Cupertino Miranda  <Cupertino.Miranda@synopsys.com>

	* scripttempl/arclinux.sc: Force .tdata and .tbss to always be
	generated.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
[parent not found: <1ed0c2a4bbe8ad5f5404014a6351b2b74db75577@gdb-build>]
* [binutils-gdb] Add aarch64-*-rtems* target
@ 2016-02-26 20:30 sergiodj+buildbot
  2016-02-27 13:29 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-02-26 20:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 12a132db164ea95e9e457427c2c97005f94c5a70 ***

Author: Joel Sherrill <joel@rtems.org>
Branch: master
Commit: 12a132db164ea95e9e457427c2c97005f94c5a70

Add aarch64-*-rtems* target


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Add x86_64-*-rtems* target
@ 2016-02-26 20:20 sergiodj+buildbot
  2016-02-27 11:59 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-02-26 20:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f73dbb0e48ef50d2743fed89b68530b731329f05 ***

Author: Joel Sherrill <joel.sherrill@oarcorp.com>
Branch: master
Commit: f73dbb0e48ef50d2743fed89b68530b731329f05

Add x86_64-*-rtems* target

	ld/configure.tgt: Also add stanza for x86_64-*-elf.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [BFD][AARCH64]Fix MOVW_SABS_G(0, 1, 2) relocation overflow check.
@ 2016-02-26 18:19 sergiodj+buildbot
  2016-02-27 10:14 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-02-26 18:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c5e3a3641ea9d6ed2918021fd77925825d24e9be ***

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

[BFD][AARCH64]Fix MOVW_SABS_G(0,1,2) relocation overflow check.

For these three relocations, 17 bit signed value should be used, instead of
16 bit. The bitsize field is changed from 16 to 17, this field in aarch64
backend is used for overflow check only.

bfd/

2016-02-26  Renlin Li  <renlin.li@arm.com>

    * elfnn-aarch64.c (elfNN_aarch64_howto_table): Fix signed overflow
    check for MOVW_SABS_G0, MOVW_SABS_G1, MOVW_SABS_G2.

ld/

2016-02-26  Renlin Li  <renlin.li@arm.com>

    * testsuite/ld-aarch64/aarch64-elf.exp: Run new testcases.
    * testsuite/ld-aarch64/emit-relocs-270.d: Update to use new boundary.
    * testsuite/ld-aarch64/emit-relocs-271.d: Likewise.
    * testsuite/ld-aarch64/emit-relocs-272.d: Likewise.
    * testsuite/ld-aarch64/emit-relocs-270-overflow.d: New.
    * testsuite/ld-aarch64/emit-relocs-270-overflow.s: New.
    * testsuite/ld-aarch64/emit-relocs-271-overflow.d: New.
    * testsuite/ld-aarch64/emit-relocs-271-overflow.s: New.
    * testsuite/ld-aarch64/emit-relocs-272-overflow.d: New.
    * testsuite/ld-aarch64/emit-relocs-272-overflow.s: New.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Optimize x86 GOT32X/GOTPCRELX relocations
@ 2016-02-26 17:52 sergiodj+buildbot
  2016-02-27  8:35 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-02-26 17:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bae420ef26f4331415b0503141c5931318025906 ***

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

Optimize x86 GOT32X/GOTPCRELX relocations

R_386_GOT32X, R_X86_64_GOTPCRELX and R_X86_64_REX_GOTPCRELX relocations
retrieve the symbol address via its GOT slot.  If the symbol address is
known at the link-time, we can use it directly by changing instruction
encoding.  Indirect branch can only be converted to PC relative direct
branch.  MOV can be changed to LEA or encoded differently with signed
address.  The subset of binary operations can be encoded only with
signed address.

If undefined weak symbol is resolved to zero link-time, we can use it
as address.  Zero addresss can't used with PC relative direct branch
when PIC is true since the current PC is unknown.  In 64-bit, 32-bit
relocation for PC relatiave direct branch to zero may also overflow.

If this optimization causes relocation overflow, --no-relax can be used
to work around it.

bfd/

	PR ld/19609
	* elf32-i386.c (elf_i386_convert_load): Convert to R_386_32 for
	load with locally bound symbols if PIC is false or there is no
	base register.  Optimize branch to 0 if PIC is false.
	(elf_i386_relocate_section): Don't generate dynamic relocations
	against undefined weak symbols if PIC is false.
	* elf64-x86-64.c (elf_x86_64_convert_load): Disable optimization
	if we can't estimate relocation overflow with --no-relax.
	Convert to R_X86_64_32S/R_X86_64_32 for load with locally bound
	symbols if PIC is false.  Optimize branch to 0 if PIC is false.
	(elf_x86_64_relocate_section): Don't generate dynamic relocations
	against undefined weak symbols if PIC is false.

ld/

	PR ld/19609
	* testsuite/ld-i386/got1.dd: Updated.
	* testsuite/ld-i386/lea1c.d: Likewise.
	* testsuite/ld-i386/load1-nacl.d: Likewise.
	* testsuite/ld-i386/load1.d: Likewise.
	* testsuite/ld-i386/load4b.d: Likewise.
	* testsuite/ld-i386/load5b.d: Likewise.
	* testsuite/ld-i386/mov1b.d: Likewise.
	* testsuite/ld-x86-64/mov1b.d: Likewise.
	* testsuite/ld-x86-64/mov1d.d: Likewise.
	* testsuite/ld-ifunc/ifunc-21-i386.d: Likewise.
	* testsuite/ld-ifunc/ifunc-21-x86-64.d: Likewise.
	* testsuite/ld-ifunc/ifunc-22-i386.d: Likewise.
	* testsuite/ld-ifunc/ifunc-22-x86-64.d: Likewise.
	* testsuite/ld-x86-64/gotpcrel1.dd: Likewise.
	* testsuite/ld-x86-64/lea1a.d: Likewise.
	* testsuite/ld-x86-64/lea1b.d: Likewise.
	* testsuite/ld-x86-64/lea1c.d: Likewise.
	* testsuite/ld-x86-64/lea1d.d: Likewise.
	* testsuite/ld-x86-64/lea1e.d: Likewise.
	* testsuite/ld-x86-64/lea1f.d: Likewise.
	* testsuite/ld-x86-64/mov1b.d: Likewise.
	* testsuite/ld-x86-64/mov1d.d: Likewise.
	* testsuite/ld-x86-64/pr13082-3b.d: Likewise.
	* testsuite/ld-x86-64/pr13082-4b.d: Likewise.
	* testsuite/ld-x86-64/lea1.s: Add tests for 32-bit registers.
	* testsuite/ld-i386/pr19609-1.s: New file.
	* testsuite/ld-i386/pr19609-1a.d: Likewise.
	* testsuite/ld-i386/pr19609-1b.d: Likewise.
	* testsuite/ld-i386/pr19609-1c.d: Likewise.
	* testsuite/ld-i386/pr19609-1d.d: Likewise.
	* testsuite/ld-i386/pr19609-1e.d: Likewise.
	* testsuite/ld-i386/pr19609-1f.d: Likewise.
	* testsuite/ld-i386/pr19609-1g.d: Likewise.
	* testsuite/ld-i386/pr19609-1h.d: Likewise.
	* testsuite/ld-i386/pr19609-1i.d: Likewise.
	* testsuite/ld-i386/pr19609-2.s: Likewise.
	* testsuite/ld-i386/pr19609-2a.d: Likewise.
	* testsuite/ld-i386/pr19609-2b.d: Likewise.
	* testsuite/ld-i386/pr19609-2c.d: Likewise.
	* testsuite/ld-i386/undefweak.s: Likewise.
	* testsuite/ld-i386/undefweaka.d: Likewise.
	* testsuite/ld-i386/undefweakb.d: Likewise.
	* testsuite/ld-x86-64/pr13082-3c.d: Likewise.
	* testsuite/ld-x86-64/pr13082-3d.d: Likewise.
	* testsuite/ld-x86-64/pr19609-1.s: Likewise.
	* testsuite/ld-x86-64/pr19609-1a.d: Likewise.
	* testsuite/ld-x86-64/pr19609-1b.d: Likewise.
	* testsuite/ld-x86-64/pr19609-1c.d: Likewise.
	* testsuite/ld-x86-64/pr19609-1d.d: Likewise.
	* testsuite/ld-x86-64/pr19609-1e.d: Likewise.
	* testsuite/ld-x86-64/pr19609-1f.d: Likewise.
	* testsuite/ld-x86-64/pr19609-1g.d: Likewise.
	* testsuite/ld-x86-64/pr19609-1h.d: Likewise.
	* testsuite/ld-x86-64/pr19609-1i.d: Likewise.
	* testsuite/ld-x86-64/pr19609-1j.d: Likewise.
	* testsuite/ld-x86-64/pr19609-1k.d: Likewise.
	* testsuite/ld-x86-64/pr19609-1l.d: Likewise.
	* testsuite/ld-x86-64/pr19609-1m.d: Likewise.
	* testsuite/ld-x86-64/pr19609-2.s: Likewise.
	* testsuite/ld-x86-64/pr19609-2a.d: Likewise.
	* testsuite/ld-x86-64/pr19609-2b.d: Likewise.
	* testsuite/ld-x86-64/pr19609-2c.d: Likewise.
	* testsuite/ld-x86-64/pr19609-2d.d: Likewise.
	* testsuite/ld-x86-64/pr19609-3.s: Likewise.
	* testsuite/ld-x86-64/pr19609-3a.d: Likewise.
	* testsuite/ld-x86-64/pr19609-3b.d: Likewise.
	* testsuite/ld-x86-64/pr19609-4.s: Likewise.
	* testsuite/ld-x86-64/pr19609-4a.d: Likewise.
	* testsuite/ld-x86-64/pr19609-4b.d: Likewise.
	* testsuite/ld-x86-64/pr19609-4c.d: Likewise.
	* testsuite/ld-x86-64/pr19609-4d.d: Likewise.
	* testsuite/ld-x86-64/pr19609-4e.d: Likewise.
	* testsuite/ld-x86-64/pr19609-5.s: Likewise.
	* testsuite/ld-x86-64/pr19609-5a.d: Likewise.
	* testsuite/ld-x86-64/pr19609-5b.d: Likewise.
	* testsuite/ld-x86-64/pr19609-5c.d: Likewise.
	* testsuite/ld-x86-64/pr19609-5d.d: Likewise.
	* testsuite/ld-x86-64/pr19609-5e.d: Likewise.
	* testsuite/ld-x86-64/pr19609-6.s: Likewise.
	* testsuite/ld-x86-64/pr19609-6a.d: Likewise.
	* testsuite/ld-x86-64/pr19609-6b.d: Likewise.
	* testsuite/ld-x86-64/pr19609-6c.d: Likewise.
	* testsuite/ld-x86-64/pr19609-6d.d: Likewise.
	* testsuite/ld-x86-64/pr19609-7.s: Likewise.
	* testsuite/ld-x86-64/pr19609-7a.d: Likewise.
	* testsuite/ld-x86-64/pr19609-7b.d: Likewise.
	* testsuite/ld-x86-64/pr19609-7c.d: Likewise.
	* testsuite/ld-x86-64/pr19609-7d.d: Likewise.
	* testsuite/ld-i386/i386.exp: Run undefweak tests and tests for
	PR ld/19609.
	* testsuite/ld-x86-64/x86-64.exp: Run pr13082-3c, pr13082-3d
	and tests for PR ld/19609.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Rename gdb.reverse/aarch64.{exp, c} to gdb.reverse/insn-reverse.{exp, c}
@ 2016-02-26 16:01 sergiodj+buildbot
  2016-02-26 21:39 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-02-26 16:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ce90fefec908ee50ae5a3b22b03447df638a54c1 ***

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

Rename gdb.reverse/aarch64.{exp,c} to gdb.reverse/insn-reverse.{exp,c}

gdb/testsuite:

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

	* gdb.reverse/aarch64.c: Rename to ...
	* gdb.reverse/insn-reverse.c: ... it.
	* gdb.reverse/aarch64.exp: Rename to ...
	* gdb.reverse/insn-reverse.exp: ... it.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Fix various bugs in arm_record_exreg_ld_st_insn
@ 2016-02-26 16:00 sergiodj+buildbot
  2016-02-27  1:31 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-02-26 16:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9fde51ed303ea3ecbaa7c0084ea417e775a5db29 ***

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

Fix various bugs in arm_record_exreg_ld_st_insn

This patch fixes various bugs in arm_record_exreg_ld_st_insn, and use
gdb.reverse/insn-reverse.c to test more arm instructions.

 - Set flag SINGLE_REG correctly.  In the arch reference manual,
   SING_REG is true when the bit 8 of instruction is zero.
 - Record the right D registers for instructions changing S registers.
 - Fix the order of length and address in record_buf_mem array.
 - Shift the offset by 2 instead of by 24.

This patch also fixes one internal error,

(gdb) PASS: gdb.reverse/finish-precsave.exp: BP at end of main
continue^M
Continuing.^M
../../binutils-gdb/gdb/utils.c:1072: internal-error: virtual memory exhausted.^M
A problem internal to GDB has been detected,FAIL: gdb.reverse/finish-precsave.exp: run to end of main (GDB internal error)

gdb:

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

	* arm-tdep.c (arm_record_exreg_ld_st_insn): Set 'single_reg'
	per bit 8.  Check bit 20 instead of bit 4 for VMOV
	instruction.  Record D registers for instructions changing
	S registers.  Change of the order of length and address
	in record_buf_mem array.

gdb/testsuite:

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

	* gdb.reverse/insn-reverse.c [__arm__] (ext_reg_load): New.
	[__arm__] (ext_reg_mov, ext_reg_push_pop): New.
	(testcases): Update.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Record right reg num of thumb special data instructions
@ 2016-02-26 15:51 sergiodj+buildbot
  2016-02-26 23:24 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-02-26 15:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1f33efec7c6d1357d7e867176cfb88942fc513a8 ***

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

Record right reg num of thumb special data instructions

When GDB decodes these thumb special data instructions, such as 'mov sp, r7'
the Rd is got incorrectly.  According to the arch reference manual, the Rd
is DN:Rdn, in which DN is bit 7 and Rdn is bits 0 to 2.  This patch fixes it.

gdb:

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

	* arm-tdep.c (thumb_record_ld_st_reg_offset): Fix the register
	number of Rd.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Properly implement STT_COMMON
@ 2016-02-26 14:51 sergiodj+buildbot
  2016-02-26 18:17 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-02-26 14:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b8871f357fdfa9c0c06d2d3e5600391d8c994f37 ***

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

Properly implement STT_COMMON

The BFD configure option, --enable-elf-stt-common, can't be to used to
verify STT_COMMON implementation with the normal binutils build.  Instead,
this patch removes it from BFD.  It adds --elf-stt-common=[no|yes] to ELF
assembler/objcopy and adds -z common/-z nocommon to ld.

A configure option, --enable-elf-stt-common, is added to gas to specify
whether ELF assembler should generate common symbols with the STT_COMMON
type by default.

Since BSF_KEEP_G is never used, it is renamed to BSF_ELF_COMMON for ELF
common symbols.

bfd/

	PR ld/19645
	* bfd.c (bfd): Change flags to 20 bits.
	(BFD_CONVERT_ELF_COMMON): New.
	(BFD_USE_ELF_STT_COMMON): Likewise.
	(BFD_FLAGS_SAVED): Add BFD_CONVERT_ELF_COMMON and
	BFD_USE_ELF_STT_COMMON.
	(BFD_FLAGS_FOR_BFD_USE_MASK): Likewise.
	* configure.ac: Remove --enable-elf-stt-common.
	* elf.c (swap_out_syms): Choose STT_COMMON or STT_OBJECT for
	common symbol depending on BFD_CONVERT_ELF_COMMON and
	BFD_USE_ELF_STT_COMMON.
	* elfcode.h (elf_slurp_symbol_table): Set BSF_ELF_COMMON for
	STT_COMMON.
	* elflink.c (bfd_elf_link_mark_dynamic_symbol): Also check
	STT_COMMON.
	(elf_link_convert_common_type): New function.
	(elf_link_output_extsym): Choose STT_COMMON or STT_OBJECT for
	common symbol depending on BFD_CONVERT_ELF_COMMON and
	BFD_USE_ELF_STT_COMMON.  Set sym.st_info after sym.st_shndx.
	* elfxx-target.h (TARGET_BIG_SYM): Add BFD_CONVERT_ELF_COMMON
	and BFD_USE_ELF_STT_COMMON to object_flags.
	(TARGET_LITTLE_SYM): Likewise.
	* syms.c (BSF_KEEP_G): Renamed to ...
	(BSF_ELF_COMMON): This.
	* bfd-in2.h: Regenerated.
	* config.in: Likewise.
	* configure: Likewise.

binutils/

	PR ld/19645
	* NEWS: Mention --elf-stt-common= for objcopy.
	* doc/binutils.texi: Document --elf-stt-common= for objcopy.
	* objcopy.c (do_elf_stt_common): New.
	(command_line_switch): Add OPTION_ELF_STT_COMMON.
	(copy_options): Add --elf-stt-common=.
	(copy_usage): Add --elf-stt-common=.
	(copy_object): Also check do_elf_stt_common for ELF targets.
	(copy_file): Handle do_elf_stt_common.
	(copy_main): Handle OPTION_ELF_STT_COMMON.
	* readelf.c (apply_relocations): Support STT_COMMON.
	* testsuite/binutils-all/common-1.s: New file.
	* testsuite/binutils-all/common-1a.d: Likewise.
	* testsuite/binutils-all/common-1b.d: Likewise.
	* testsuite/binutils-all/common-1c.d: Likewise.
	* testsuite/binutils-all/common-1d.d: Likewise.
	* testsuite/binutils-all/common-1e.d: Likewise.
	* testsuite/binutils-all/common-1f.d: Likewise.
	* testsuite/binutils-all/common-2.s: Likewise.
	* testsuite/binutils-all/common-2a.d: Likewise.
	* testsuite/binutils-all/common-2b.d: Likewise.
	* testsuite/binutils-all/common-2c.d: Likewise.
	* testsuite/binutils-all/common-2d.d: Likewise.
	* testsuite/binutils-all/common-2e.d: Likewise.
	* testsuite/binutils-all/common-2f.d: Likewise.
	* testsuite/binutils-all/objcopy.exp
	(objcopy_test_elf_common_symbols): New proc.
	Run objcopy_test_elf_common_symbols for ELF targets

gas/

	PR ld/19645
	* NEWS: Mention --enable-elf-stt-common and --elf-stt-common=
	for ELF assemblers.
	* as.c (flag_use_elf_stt_common): New.
	(show_usage): Add --elf-stt-common=.
	(option_values): Add OPTION_ELF_STT_COMMON.
	(std_longopts): Add --elf-stt-common=.
	(parse_args): Handle --elf-stt-common=.
	* as.h (flag_use_elf_stt_common): New.
	* config.in: Regenerated.
	* configure: Likewise.
	* configure.ac: Add --enable-elf-stt-common and define
	DEFAULT_GENERATE_ELF_STT_COMMON.
	* gas/write.c (write_object_file): Set BFD_CONVERT_ELF_COMMON
	and BFD_USE_ELF_STT_COMMON if flag_use_elf_stt_common is set.
	* doc/as.texinfo: Document --elf-stt-common=.
	* testsuite/gas/elf/common3.s: New file.
	* testsuite/gas/elf/common3a.d: Likewise.
	* testsuite/gas/elf/common3b.d: Likewise.
	* testsuite/gas/elf/common4.s: Likewise.
	* testsuite/gas/elf/common4a.d: Likewise.
	* testsuite/gas/elf/common4b.d: Likewise.
	* testsuite/gas/i386/dw2-compress-3b.d: Likewise.
	* testsuite/gas/i386/dw2-compressed-3b.d: Likewise.
	* testsuite/gas/elf/elf.exp: Run common3a, common3b, common4a
	and common4b.
	* testsuite/gas/i386/dw2-compress-3.d: Renamed to ...
	* testsuite/gas/i386/dw2-compress-3a.d: This.  Pass
	--elf-stt-common=no to as.
	* testsuite/gas/i386/dw2-compressed-3.d: Renamed to ...
	* testsuite/gas/i386/dw2-compressed-3a.d: This.  Pass
	--elf-stt-common=no to as.
	* testsuite/gas/i386/i386.exp: Run dw2-compress-3a,
	dw2-compress-3b, dw2-compressed-3a and dw2-compressed-3b instead
	of dw2-compress-3 and dw2-compressed-3.

include/

	PR ld/19645
	* bfdlink.h (bfd_link_elf_stt_common): New enum.
	(bfd_link_info): Add elf_stt_common.

ld/

	PR ld/19645
	* NEWS: Mention -z common/-z nocommon for ELF targets.
	* emultempl/elf32.em (gld${EMULATION_NAME}_handle_option): Handle
	-z common and -z nocommon.
	* ld.texinfo: Document -z common/-z nocommon.
	* lexsup.c (elf_shlib_list_options): Add -z common/-z nocommon.
	* testsuite/ld-elf/tls_common.exp: Test --elf-stt-common=no and
	--elf-stt-common=yes with assembler.
	* testsuite/ld-elfcomm/common-1.s: New file.
	* testsuite/ld-elfcomm/common-1a.d: Likewise.
	* testsuite/ld-elfcomm/common-1b.d: Likewise.
	* testsuite/ld-elfcomm/common-1c.d: Likewise.
	* testsuite/ld-elfcomm/common-1d.d: Likewise.
	* testsuite/ld-elfcomm/common-1e.d: Likewise.
	* testsuite/ld-elfcomm/common-1f.d: Likewise.
	* testsuite/ld-elfcomm/common-2.s: Likewise.
	* testsuite/ld-elfcomm/common-2a.d: Likewise.
	* testsuite/ld-elfcomm/common-2b.d: Likewise.
	* testsuite/ld-elfcomm/common-2c.d: Likewise.
	* testsuite/ld-elfcomm/common-2d.d: Likewise.
	* testsuite/ld-elfcomm/common-2e.d: Likewise.
	* testsuite/ld-elfcomm/common-2f.d: Likewise.
	* testsuite/ld-elfcomm/common-3a.rd: Likewise.
	* testsuite/ld-elfcomm/common-3b.rd: Likewise.
	* testsuite/ld-i386/pr19645.d: Likewise.
	* testsuite/ld-i386/pr19645.s: Likewise.
	* testsuite/ld-x86-64/largecomm-1.s: Likewise.
	* testsuite/ld-x86-64/largecomm-1a.d: Likewise.
	* testsuite/ld-x86-64/largecomm-1b.d: Likewise.
	* testsuite/ld-x86-64/largecomm-1c.d: Likewise.
	* testsuite/ld-x86-64/largecomm-1d.d: Likewise.
	* testsuite/ld-x86-64/largecomm-1e.d: Likewise.
	* testsuite/ld-x86-64/largecomm-1f.d: Likewise.
	* testsuite/ld-x86-64/pr19645.d: Likewise.
	* testsuite/ld-x86-64/pr19645.s: Likewise.
	* testsuite/ld-elfcomm/elfcomm.exp: Test --elf-stt-common=yes
	with assembler.
	(assembler_generates_commons): Removed.
	Run -z common/-z nocommon tests.  Run *.d tests.
	* testsuite/ld-i386/i386.exp: Run pr19645.
	* testsuite/ld-x86-64/x86-64.exp: Likewise.
	* testsuite/ld-x86-64/dwarfreloc.exp: Test --elf-stt-common with
	assembler.  Test STT_COMMON with readelf.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Fix powerpc64 -r --save-restore-funcs
@ 2016-02-26 13:00 sergiodj+buildbot
  2016-02-26 14:49 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-02-26 13:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b32547cd11bec3baf53e0dedf3c733cd3e0839f6 ***

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

Fix powerpc64 -r --save-restore-funcs

	* elf64-ppc.c (create_linkage_sections): Create sfpr when
	save_restore_funcs, rest of sections when not relocatable.
	(ppc64_elf_init_stub_bfd): Always call create_linkage_sections.
	(sfpr_define): Define all symbols on emitted code.
	(ppc64_elf_func_desc_adjust): Adjust for sfpr now being created
	when relocatable.  Move sfpr_define loop earlier.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
[parent not found: <ab50308758bfde9ab7b50e6def65e20f0b560702@gdb-build>]
[parent not found: <ae91f6253926e4dadebcae90772f4f5a5bd06056@gdb-build>]
[parent not found: <678b48b7cf0bd518ebc234bda98229cc602c2a45@gdb-build>]
* [binutils-gdb] avoid compiler warnings in remote-m32r-sdi.c
@ 2016-02-25 17:42 sergiodj+buildbot
  2016-02-26  0:18 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-02-25 17:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1547ef64562ebbfcdc768ce93979f09bdd119b11 ***

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

avoid compiler warnings in remote-m32r-sdi.c

gdb/ChangeLog:

	* remote-m32r-sdi.c (recv_char_data): Initialize val to avoid
	compiler warning.
	(recv_long_data): Ditto.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Remove gdb.base/branches.c
@ 2016-02-25 17:22 sergiodj+buildbot
  2016-02-25 22:38 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-02-25 17:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6cb59ff1111c1d5e955ca0eeddab6f03db0fbfb7 ***

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

Remove gdb.base/branches.c

This patch removes gdb.base/branches.c which was added by the following
commit, but it is not used at all.

commit ea8122af1432abdeb256b2c669eb3d0cf8cb97bf
Author: John Metzler <jmetzler@cygnus>
Date:   Thu Apr 16 17:56:11 1998 +0000

    Thu Apr 16 10:52:34 1998  John Metzler  <jmetzler@cygnus.com>

        * gdb.base/branches.c: Code with lots of loops and
        subroutines. Used to test gdbs ability to single step through PC
        changes, especially to test mips-tdep.c:mips_next_pc

gdb/testsuite:

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

	* gdb.base/branches.c: Remove.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
[parent not found: <7337a6f2297cdd91bb852b479b284e5796d62cc9@gdb-build>]
* [binutils-gdb] Map registers to remote numbers when encoding an ax_reg or ax_reg_mask operation
@ 2016-02-25 14:46 sergiodj+buildbot
  2016-02-25 15:53 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-02-25 14:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1eb7c2d886c0faac42d2b68862b0e6b0d3182d98 ***

Author: Antoine Tremblay <antoine.tremblay@ericsson.com>
Branch: master
Commit: 1eb7c2d886c0faac42d2b68862b0e6b0d3182d98

Map registers to remote numbers when encoding an ax_reg or ax_reg_mask operation

When encoding the agent expression operation ax_reg or ax_reg_mask, the
register number used is internal to GDB. However GDBServer expects a tdesc
based number.

This usually does not cause a problem since at the moment, for raw
registers GDBServer R trace action ignores the register mask and just
collects all registers.

It can be a problem, however with pseudo registers on some platforms if the
tdesc number doesn't match the GDB internal register number.

This is the case with ARM, the upcoming ARM tracepoint support, fails
these test cases without this patch:

gdb.trace/collection.exp: collect register locals collectively:*

GDBSever would exit with: unhandled register size
Since the register number is not mapped.

This patch fixes these issues by calling gdbarch_remote_register_number
before encoding the register number in the ax_reg or ax_reg_mask operation.

Tested on x86 native-gdbserver no regressions observed.

gdb/ChangeLog:

	* ax-general.c (ax_reg): Call gdbarch_remote_register_number.
	(ax_reg_mask): Likewise.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Update symbol version for symbol from linker script
@ 2016-02-24 23:37 sergiodj+buildbot
  2016-02-25  8:17 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-02-24 23:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0f550b3df1d4ae31d12505cf93981313c9c6dd25 ***

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

Update symbol version for symbol from linker script

We need to update symbol version for symbols from linker script.

bfd/

	PR ld/19698
	* elflink.c (bfd_elf_record_link_assignment): Set versioned if
	symbol version is unknown.

ld/

	PR ld/19698
	* testsuite/ld-elf/pr19698.d: New file.
	* testsuite/ld-elf/pr19698.s: Likewise.
	* testsuite/ld-elf/pr19698.t: Likewise.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Handle MIPS Linux SIGTRAP siginfo.si_code values
@ 2016-02-24 23:11 sergiodj+buildbot
  2016-02-25  0:31 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-02-24 23:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e7ad2f145c05bc60b1cd2796c8f3b72f02e3e730 ***

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

Handle MIPS Linux SIGTRAP siginfo.si_code values

This unbreaks pending/delayed breakpoints handling, as well as
hardware watchpoints, on MIPS.

Ref: https://sourceware.org/ml/gdb-patches/2016-02/msg00681.html

The MIPS kernel reports SI_KERNEL for all kernel generated traps,
instead of TRAP_BRKPT / TRAP_HWBKPT, but GDB isn't aware of this.

Basically, this commit:

- Folds watchpoints logic into check_stopped_by_breakpoint, and
  renames it to save_stop_reason.

- Adds GDB_ARCH_IS_TRAP_HWBKPT.

- Makes MIPS set both GDB_ARCH_IS_TRAP_BRPT and
  GDB_ARCH_IS_TRAP_HWBKPT to SI_KERNEL.  In save_stop_reason, we
  handle the case of the same si_code returning true for both
  TRAP_BRPT and TRAP_HWBKPT by looking at what the debug registers
  say.

Tested on x86-64 Fedora 20, native and gdbserver.

gdb/ChangeLog:
2016-02-24  Pedro Alves  <palves@redhat.com>

	* linux-nat.c (save_sigtrap) Delete.
	(stop_wait_callback): Call save_stop_reason instead of
	save_sigtrap.
	(check_stopped_by_breakpoint): Rename to ...
	(save_stop_reason): ... this.  Bits of save_sigtrap folded here.
	Use GDB_ARCH_IS_TRAP_HWBKPT and handle ambiguous
	GDB_ARCH_IS_TRAP_BRKPT / GDB_ARCH_IS_TRAP_HWBKPT.  Factor out
	common code between the USE_SIGTRAP_SIGINFO and
	!USE_SIGTRAP_SIGINFO blocks.
	(linux_nat_filter_event): Call save_stop_reason instead of
	save_sigtrap.
	* nat/linux-ptrace.h: Check for both SI_KERNEL and TRAP_BRKPT
	si_code for MIPS.
	* nat/linux-ptrace.h: Fix "TRAP_HWBPT" typo in x86 table.  Add
	comments on MIPS behavior.
	(GDB_ARCH_IS_TRAP_HWBKPT): Define for all archs.

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

	* linux-low.c (check_stopped_by_breakpoint): Rename to ...
	(save_stop_reason): ... this.  Use GDB_ARCH_IS_TRAP_HWBKPT and
	handle ambiguous GDB_ARCH_IS_TRAP_BRKPT / GDB_ARCH_IS_TRAP_HWBKPT.
	Factor out common code between the USE_SIGTRAP_SIGINFO and
	!USE_SIGTRAP_SIGINFO blocks.
	(linux_low_filter_event): Call save_stop_reason instead of
	check_stopped_by_breakpoint and check_stopped_by_watchpoint.
	Update comments.
	(linux_wait_1): Update comments.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
[parent not found: <338435ef105ff51e967571ad073830ec1eb5a4ab@gdb-build>]
* [binutils-gdb] Move tfile-avx.exp to tracefile-pseudo-reg.exp
@ 2016-02-24 19:30 sergiodj+buildbot
  2016-02-24 19:50 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-02-24 19:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 861ca91fc65b9a53b807f6d5c5253fc33f92e7d8 ***

Author: Antoine Tremblay <antoine.tremblay@ericsson.com>
Branch: master
Commit: 861ca91fc65b9a53b807f6d5c5253fc33f92e7d8

Move tfile-avx.exp to tracefile-pseudo-reg.exp

As it is planned to add more architectures to this test, rename to a more
generic name.

gdb/testsuite/ChangeLog:

	* gdb.trace/tfile-avx.c: Move to...
	* gdb.trace/tracefile-pseudo-reg.c: Here.
	* gdb.trace/tfile-avx.exp: Move to...
	* gdb.trace/tracefile-pseudo-reg.exp: Here.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Move new skip features to proper section (post 7.11).
@ 2016-02-24 18:24 sergiodj+buildbot
  2016-02-24 18:36 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-02-24 18:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d2dffb8d3be366d4d02de06e92c24c9abdb0adfc ***

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

Move new skip features to proper section (post 7.11).


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] powerpc: Support z-point type in gdbserver.
@ 2016-02-24 17:45 sergiodj+buildbot
  2016-02-24 17:57 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-02-24 17:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 657f9cde9d531c9929bef9e02a8064101d568f50 ***

Author: Wei-cheng Wang <cole945@gmail.com>
Branch: master
Commit: 657f9cde9d531c9929bef9e02a8064101d568f50

powerpc: Support z-point type in gdbserver.

Support z-point, so tracepoints and breakpoints can be inserted at the same
location.

gdb/gdbserver/ChangeLog:

2016-02-24  Wei-cheng Wang  <cole945@gmail.com>

	* linux-ppc-low.c (ppc_supports_z_point_type): New function:
	(ppc_insert_point, ppc_remove_point): Insert/remove z-packet breakpoints.
	(ppc64_emit_ops_vector): Add target ops - ppc_supports_z_point_type,
	ppc_insert_point, ppc_remove_point.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Revert "ABS32"
@ 2016-02-24 15:09 sergiodj+buildbot
  2016-02-24 16:15 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-02-24 15:09 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 92d77487b3dbfd934c5565bab09e0f3051e0b08d ***

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

Revert "ABS32"

This reverts commit 30bdf5c82e5734ac9f0b18eb7af631806d419270.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [OPCODES][ARM][1/3]Add armv8.2 fp16 instruction dissembler support.
@ 2016-02-24 14:22 sergiodj+buildbot
  2016-02-24 16:03 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-02-24 14:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b0c11777665276f8e9b590bbe4832a7c66f5093d ***

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

[OPCODES][ARM][1/3]Add armv8.2 fp16 instruction dissembler support.

opcodes/

2016-02-24  Renlin Li  <renlin.li@arm.com>

	* arm-dis.c (coprocessor_opcodes): Add fp16 instruction entries.
	(print_insn_coprocessor): Support fp16 instruction.

gas/

2016-02-24  Renlin Li  <renlin.li@arm.com>

	* testsuite/gas/arm/copro.d: Adjust output.
	* testsuite/gas/arm/copro.s: Adjust co-processor num.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [OPCODES][ARM]Fix mask for a few coprocessor opcodes.
@ 2016-02-24 14:12 sergiodj+buildbot
  2016-02-24 15:48 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-02-24 14:12 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3e309328e8d91e37f2f3cea15f8a686d3bdfa700 ***

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

[OPCODES][ARM]Fix mask for a few coprocessor opcodes.

opcodes/

2016-02-24  Renlin Li  <renlin.li@arm.com>

	* arm-dis.c (coprocessor_opcodes): Fix mask for vsel, vmaxnm, vminnm,
	vrint(mpna).

gas/

2016-02-24  Renlin Li  <renlin.li@arm.com>

	* testsuite/gas/arm/mask_1.d: New.
	* testsuite/gas/arm/mask_1.s: New.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [OPCODE][ARM]Correct disassembler for cdp/cdp2, mcr/mcr2, mrc/mrc2, ldc/ldc2, stc/stc2
@ 2016-02-24 14:09 sergiodj+buildbot
  2016-02-24 15:30 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-02-24 14:09 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8afc7bea4018bf535902503c9a25dd4a96dfa3ca ***

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

[OPCODE][ARM]Correct disassembler for cdp/cdp2, mcr/mcr2, mrc/mrc2, ldc/ldc2, stc/stc2

opcodes/

2016-02-24  Renlin Li  <renlin.li@arm.com>

	* arm-dis.c (print_insn_coprocessor): Check co-processor number for
	cpd/cpd2, mcr/mcr2, mrc/mrc2, ldc/ldc2, stc/stc2.

gas/

2016-02-24  Renlin Li  <renlin.li@arm.com>

	* testsuite/gas/arm/copro.s: Use coprocessor other than 10, 11.
	* testsuite/gas/arm/copro.d: Update.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] ABS32
@ 2016-02-24 14:07 sergiodj+buildbot
  2016-02-24 15:05 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-02-24 14:07 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 30bdf5c82e5734ac9f0b18eb7af631806d419270 ***

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

ABS32


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Set plt_got.offset to (bfd_vma) -1
@ 2016-02-24 13:54 sergiodj+buildbot
  2016-02-24 14:31 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-02-24 13:54 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 13f422778ff5307dad1f66d25a1d211bb8f76a8b ***

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

Set plt_got.offset to (bfd_vma) -1

Since plt_got.offset may be updated in x86 allocate_dynrelocs, set
plt_got.offset to (bfd_vma) -1 when setting needs_plt to 0.

	* elf32-i386.c (elf_i386_allocate_dynrelocs): Set plt_got.offset
	to (bfd_vma) -1 when setting needs_plt to 0.
	* elf64-x86-64.c (elf_x86_64_allocate_dynrelocs): Likewise.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Fix logic in exec_file_locate_attach
@ 2016-02-24 12:00 sergiodj+buildbot
  2016-02-24 12:43 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-02-24 12:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bf74e428bca61022bd5cdf6bf28789a184748b4d ***

Author: Gary Benson <gbenson@redhat.com>
Branch: master
Commit: bf74e428bca61022bd5cdf6bf28789a184748b4d

Fix logic in exec_file_locate_attach

This commit fixes an error in exec_file_locate_attach where
the main executable could be loaded from outside the sysroot
if a nonempty, non-"target:" sysroot was set but the discovered
executable filename did not exist in that sysroot and did exist
on the main filesystem.

gdb/ChangeLog:

	* exec.c (exec_file_locate_attach): Do not attempt to
	locate main executable locally if not found in sysroot.

gdb/testsuite/ChangeLog:

	* gdb.base/attach-pie-noexec.exp: Do not expect an error
	message on attach.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Build unavailable-stack frames for tracepoint.
@ 2016-02-24  3:22 sergiodj+buildbot
  2016-02-24  3:46 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-02-24  3:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 50ae56ec464580492a5f987f658acc6ad82131b6 ***

Author: Wei-cheng Wang <cole945@gmail.com>
Branch: master
Commit: 50ae56ec464580492a5f987f658acc6ad82131b6

Build unavailable-stack frames for tracepoint.

gdb/ChangeLog:

2016-02-24  Wei-cheng Wang  <cole945@gmail.com>

	* rs6000-tdep.c (rs6000_frame_cache, rs6000_frame_this_id): Handle
	unavailable PC/SP to build unavailable frame.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Extend "skip" command to support -file, -gfile, -function, -rfunction.
@ 2016-02-23 21:37 sergiodj+buildbot
  2016-02-23 23:04 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-02-23 21:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cce0e92333b872cfe036aae611b6b5d61cf58186 ***

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

Extend "skip" command to support -file, -gfile, -function, -rfunction.

gdb/ChangeLog:

	Extend "skip" command to support -file, -gfile, -function, -rfunction.
	* NEWS: Document new features.
	* skip.c: #include "fnmatch.h", "gdb_regex.h".
	(skiplist_entry) <file>: Renamed from filename.
	<function>: Renamed from function_name.
	<file_is_glob, function_is_regexp>: New members.
	<compiled_function_regexp, compiled_function_regexp_is_valid>:
	New members.
	(make_skip_entry): New function.
	(free_skiplist_entry, free_skiplist_entry_cleanup): New functions.
	(make_free_skiplist_entry_cleanup): New function.
	(skip_file_command): Update.
	(skip_function, skip_function_command): Update.
	(compile_skip_regexp): New functions.
	(skip_command): Add support for new options.
	(skip_info): Update.
	(skip_file_p, skip_gfile_p): New functions.
	(skip_function_p, skip_rfunction_p): New functions.
	(function_name_is_marked_for_skip): Update and simplify.
	(_initialize_step_skip): Update.
	* symtab.c: #include "fnmatch.h".
	(compare_glob_filenames_for_search): New function.
	* symtab.h (compare_glob_filenames_for_search): Declare.
	* utils.c (count_path_elements): New function.
	(strip_leading_path_elements): New function.
	* utils.h (count_path_elements): Declare.
	(strip_leading_path_elements): Declare.

gdb/doc/ChangeLog:

	* gdb.texinfo (Skipping Over Functions and Files): Document new
	options to "skip" command.  Update docs of output of "info skip".

gdb/testsuite/ChangeLog:

	* gdb.base/skip.c (test_skip): New function.
	(end_test_skip_file_and_function): New function.
	(test_skip_file_and_function): New function.
	* gdb.base/skip1.c (test_skip): New function.
	(skip1_test_skip_file_and_function): New function.
	* gdb.base/skip.exp: Add tests for new skip options.
	* gdb.base/skip-solib.exp: Update expected output.
	* gdb.perf/skip-command.cc: New file.
	* gdb.perf/skip-command.exp: New file.
	* gdb.perf/skip-command.py: New file.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] arm-tdep.c: Remove unused "to" parameters
@ 2016-02-23 18:34 sergiodj+buildbot
  2016-02-23 19:52 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-02-23 18:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1254566561957d2202d61e12881b0eb40d33a64c ***

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

arm-tdep.c: Remove unused "to" parameters

gdb/ChangeLog:

	* arm-tdep.c (arm_decode_svc_copro): Remove "to" parameter.
	(thumb_process_displaced_insn): Likewise.
	(arm_process_displaced_insn): Adjust calls.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Increment the ABIVERSION to 5 for MIPS objects with non-executable stacks.
@ 2016-02-23 13:10 sergiodj+buildbot
  2016-02-23 14:14 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-02-23 13:10 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 17733f5be961baa7a47fdf1471aa6948372293d6 ***

Author: Faraz Shahbazker <faraz.shahbazker@imgtec.com>
Branch: master
Commit: 17733f5be961baa7a47fdf1471aa6948372293d6

Increment the ABIVERSION to 5 for MIPS objects with non-executable stacks.

	* bfd/elfxx-mips.c (_bfd_mips_post_process_headers): Increment
	ABIVERSION for non-executable stack.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Fix the genetation of GOT entries for the Microblaze target.
@ 2016-02-23 10:48 sergiodj+buildbot
  2016-02-23 11:54 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-02-23 10:48 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 47993b4af18c6ef1cad300f6393bf896d3cb5e5c ***

Author: Rich Felker <bugdal@aerifal.cx>
Branch: master
Commit: 47993b4af18c6ef1cad300f6393bf896d3cb5e5c

Fix the genetation of GOT entries for the Microblaze target.

	PR target/19516
	* elf32-microblaze.c (microblaze_elf_finish_dynamic_symbol):
	Always produce a RELATIVE reloc for a local symbol.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
[parent not found: <4000e47e2f3860a85a9023f3fe5950c8cc6fa507@gdb-build>]
* [binutils-gdb] Remove BSF_COMMON from comments
@ 2016-02-22 13:15 sergiodj+buildbot
  2016-02-22 16:14 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-02-22 13:15 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 75c1920bb02f09534da55b98277a613b7cb430cc ***

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

Remove BSF_COMMON from comments

BSF_COMMON isn't defined in BFD.

	* syms.c: Remove BSF_COMMON from comments.
	* bfd-in2.h: Regenerated.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [AArch64] Remove redundant calculation of plt stub destination for veneer
@ 2016-02-22 12:34 sergiodj+buildbot
  2016-02-22 14:53 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-02-22 12:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9a2284679086e32c0c2a46e08b23edde6fc8be85 ***

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

[AArch64] Remove redundant calculation of plt stub destination for veneer

elfNN_aarch64_size_stubs, the caller of aarch64_type_stub has redirected
the final destination of long branch veneer to plt stub if the call
should go through it.

It's redundant to do the same check and redirect again from scratch
inside aarch64_type_stub.

bfd/
  * elfnn-aarch64. (aarch64_type_of_stub): Remove redundation calcuation
  for destination.  Remove useless function parameters.
  (elfNN_aarch64_size_stubs): Update parameters for aarch64_type_of_stub.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Also update recursive call to d_lookup_symbol_imports.
@ 2016-02-21 21:15 sergiodj+buildbot
  2016-02-21 22:52 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-02-21 21:15 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e08db6db1dd514f1c99f94bb6a9c1cfe02a1ab90 ***

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

Also update recursive call to d_lookup_symbol_imports.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Remove search_parents parameter from d_lookup_symbol_imports.
@ 2016-02-21 20:46 sergiodj+buildbot
  2016-02-21 21:25 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-02-21 20:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 30a6a7f035026d05b52c92c26d4cb7ea3c6d6e5c ***

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

Remove search_parents parameter from d_lookup_symbol_imports.

gdb/ChangeLog:

	* d-namespace.c (d_lookup_symbol_imports): Remove argument
	'search_parents'.  All callers updated.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Prevent a seg-fault in the linker when accessing a specially crafted, corrupt, aout binary.
@ 2016-02-19 16:10 sergiodj+buildbot
  2016-02-19 18:26 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-02-19 16:10 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e517df3dbf7556ddb389228d713a804594ee3c1f ***

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

Prevent a seg-fault in the linker when accessing a specially crafted, corrupt, aout binary.

	PR ld/19629
	* aoutx.h (aout_link_add_symbols): Check for out of range string
	table offsets.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Fix a seg-fault in the linker when it encounters a corrupt binary containing a reloc with no associated symbol.
@ 2016-02-19 15:34 sergiodj+buildbot
  2016-02-19 17:05 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-02-19 15:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 737684142b3f7dfa6d440c8363750911a8ac20ce ***

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

Fix a seg-fault in the linker when it encounters a corrupt binary containing a reloc with no associated symbol.

	PR ld/19628
	* reloc.c (bfd_generic_get_relocated_section_contents): Stop
	processing if we encounter a reloc without an associated symbol.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Add D support to gdb_default_target_compile.
@ 2016-02-18 21:14 sergiodj+buildbot
  2016-02-18 23:01 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-02-18 21:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 24f75eadabc519563ed119932c77874a016a799a ***

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

Add D support to gdb_default_target_compile.

gdb/testsuite/ChangeLog:

	* lib/future.exp: Add D support.
	(gdb_find_gdc): New proc.
	(gdb_default_target_compile): Add D support.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
[parent not found: <f79a3bae8725dfe0e11b04ddfc6e6bc8f23e4e4e@gdb-build>]
* [binutils-gdb] Determine the iteration count based on wallclock instead of user+system time.
@ 2016-02-18 19:38 sergiodj+buildbot
  2016-02-18 21:39 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-02-18 19:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fbb7bcbeaad3aebab8935cb4ee5706017b3b9e71 ***

Author: Wei-cheng Wang <cole945@gmail.com>
Branch: master
Commit: fbb7bcbeaad3aebab8935cb4ee5706017b3b9e71

Determine the iteration count based on wallclock instead of user+system time.

gdb/testsuite/ChangeLog:

2016-02-18  Wei-cheng Wang  <cole945@gmail.com>

	* gdb.trace/tspeed.c (myclock): Return wallclock instead of
	user+system time.
	(trace_speed_test): Determine the iteration count for a time
	between 15..30 seconds.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Intel MPX bound violation handling
@ 2016-02-18 16:46 sergiodj+buildbot
  2016-02-18 18:53 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-02-18 16:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 012b3a217a60cc74b802b059029c72a25d77808c ***

Author: Walfred Tedeschi <walfred.tedeschi@intel.com>
Branch: master
Commit: 012b3a217a60cc74b802b059029c72a25d77808c

Intel MPX bound violation handling

With Intel Memory Protection Extensions it was introduced the concept of
boundary violation.  A boundary violations is presented to the inferior as
a segmentation fault having SIGCODE 3.  This patch adds a
handler for a boundary violation extending the information displayed
when a bound violation is presented to the inferior.  In the stop mode
case the debugger will also display the kind of violation: "upper" or
"lower", bounds and the address accessed.
On no stop mode the information will still remain unchanged.  Additional
information about bound violations are not meaningful in that case user
does not know the line in which violation occurred as well.

When the segmentation fault handler is stop mode the out puts will be
changed as exemplified below.

The usual output of a segfault is:
Program received signal SIGSEGV, Segmentation fault
0x0000000000400d7c in upper (p=0x603010, a=0x603030, b=0x603050,
c=0x603070, d=0x603090, len=7) at i386-mpx-sigsegv.c:68
68        value = *(p + len);

In case it is a bound violation it will be presented as:
Program received signal SIGSEGV, Segmentation fault
Upper bound violation while accessing address 0x7fffffffc3b3
Bounds: [lower = 0x7fffffffc390, upper = 0x7fffffffc3a3]
0x0000000000400d7c in upper (p=0x603010, a=0x603030, b=0x603050,
c=0x603070, d=0x603090, len=7) at i386-mpx-sigsegv.c:68
68        value = *(p + len);

In mi mode the output of a segfault is:
*stopped,reason="signal-received",signal-name="SIGSEGV",
signal-meaning="Segmentation fault", frame={addr="0x0000000000400d7c",
func="upper",args=[{name="p", value="0x603010"},{name="a",value="0x603030"}
,{name="b",value="0x603050"}, {name="c",value="0x603070"},
{name="d",value="0x603090"},{name="len",value="7"}],
file="i386-mpx-sigsegv.c",fullname="i386-mpx-sigsegv.c",line="68"},
thread-id="1",stopped-threads="all",core="6"

in the case of a bound violation:
*stopped,reason="signal-received",signal-name="SIGSEGV",
signal-meaning="Segmentation fault",
sigcode-meaning="Upper bound violation",
lower-bound="0x603010",upper-bound="0x603023",bound-access="0x60302f",
frame={addr="0x0000000000400d7c",func="upper",args=[{name="p",
value="0x603010"},{name="a",value="0x603030"},{name="b",value="0x603050"},
{name="c",value="0x603070"},{name="d",value="0x603090"},
{name="len",value="7"}],file="i386-mpx-sigsegv.c",
fullname="i386-mpx-sigsegv.c",line="68"},thread-id="1",
stopped-threads="all",core="6"

2016-02-18  Walfred Tedeschi  <walfred.tedeschi@intel.com>

gdb/ChangeLog:

	* NEWS: Add entry for bound violation.
	* amd64-linux-tdep.c (amd64_linux_init_abi_common):
	Add handler for segmentation fault.
	* gdbarch.sh (handle_segmentation_fault): New.
	* gdbarch.c: Regenerate.
	* gdbarch.h: Regenerate.
	* i386-linux-tdep.c (i386_linux_handle_segmentation_fault): New.
	(SIG_CODE_BONDARY_FAULT): New define.
	(i386_linux_init_abi): Use i386_mpx_bound_violation_handler.
	* i386-linux-tdep.h (i386_linux_handle_segmentation_fault) New.
	* i386-tdep.c (i386_mpx_enabled): Add as external.
	* i386-tdep.c (i386_mpx_enabled): Add as external.
	* infrun.c (handle_segmentation_fault): New function.
	(print_signal_received_reason): Use handle_segmentation_fault.

gdb/testsuite/ChangeLog:

	* gdb.arch/i386-mpx-sigsegv.c: New file.
	* gdb.arch/i386-mpx-sigsegv.exp: New file.
	* gdb.arch/i386-mpx-simple_segv.c: New file.
	* gdb.arch/i386-mpx-simple_segv.exp: New file.

gdb/doc/ChangeLog:

	* gdb.texinfo (Signals): Add bound violation display hints for
	a SIGSEGV.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Remove setup_kfail server/13796 in disp-step-syscall.exp
@ 2016-02-18 13:17 sergiodj+buildbot
  2016-02-18 14:57 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-02-18 13:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2d5189bd3a6e2014b9b42a4bcb0df410eff1c2e1 ***

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

Remove setup_kfail server/13796 in disp-step-syscall.exp

This patch series add fork support in target remote,

  [PATCH v2 0/3] Target remote mode fork and exec support
  https://sourceware.org/ml/gdb-patches/2015-12/msg00144.html

so GDB can be informed about the child, and adjust child correctly in
displaced stepping.  The PR server/13796 was fixed by this patch
series actually.  Test results on buildbot show this KFAIL->KPASS
change https://sourceware.org/ml/gdb-testers/2015-q4/msg10128.html

gdb/testsuite:

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

	* gdb.base/disp-step-syscall.exp (disp_step_cross_syscall):
	Don't call setup_kfail.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Always create dynamic sections for -E/--dynamic-list
@ 2016-02-18 11:25 sergiodj+buildbot
  2016-02-18 12:31 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-02-18 11:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bf89386a862ace008f0152bca8bddf996d3993c8 ***

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

Always create dynamic sections for -E/--dynamic-list

In embedded environments, including boot loaders, the non-PIC executable
needs to export its symbols to modules loaded in the future.  We should
always create dynamic sections for -E/--dynamic-list.

bfd/

	PR ld/19617
	* elflink.c (elf_link_add_object_symbols): Always create dynamic
	sections for -E/--dynamic-list.

ld/

	PR ld/19617
	* testsuite/ld-elf/pr19617.s: New file.
	* testsuite/ld-elf/pr19617a.d: Likewise.
	* testsuite/ld-elf/pr19617b.d: Likewise.
	* testsuite/ld-elf/pr19617c.d: Likewise.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [x86-64] Omit dynamic sections symbols
@ 2016-02-17 19:31 sergiodj+buildbot
  2016-02-17 21:05 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-02-17 19:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8f79b794ce055b3b4041788182080f4ce3f9048e ***

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

[x86-64] Omit dynamic sections symbols

Define elf_backend_omit_section_dynsym to bfd_true for x86-64, similar
to i386, x86-64 doesn't need dynamic sections symbols.

bfd/

	* elf64-x86-64.c (elf_backend_omit_section_dynsym): New.  Defined
	to bfd_true.

ld/

	* testsuite/ld-ifunc/ifunc-1-local-x86.d: Updated.
	* testsuite/ld-ifunc/ifunc-1-x86.d: Likewise.
	* testsuite/ld-ifunc/ifunc-2-local-x86-64.d: Likewise.
	* testsuite/ld-ifunc/ifunc-2-x86-64.d: Likewise.
	* testsuite/ld-ifunc/ifunc-3a-x86.d: Likewise.
	* testsuite/ld-ifunc/pr17154-x86-64.d: Likewise.
	* testsuite/ld-x86-64/bnd-ifunc-1.d: Likewise.
	* testsuite/ld-x86-64/bnd-ifunc-2.d: Likewise.
	* testsuite/ld-x86-64/bnd-plt-1.d: Likewise.
	* testsuite/ld-x86-64/ilp32-4-nacl.d: Likewise.
	* testsuite/ld-x86-64/ilp32-4.d: Likewise.
	* testsuite/ld-x86-64/load1c-nacl.d: Likewise.
	* testsuite/ld-x86-64/load1c.d: Likewise.
	* testsuite/ld-x86-64/load1d-nacl.d: Likewise.
	* testsuite/ld-x86-64/load1d.d: Likewise.
	* testsuite/ld-x86-64/pr14207.d: Likewise.
	* testsuite/ld-x86-64/pr19162.d: Likewise.
	* testsuite/ld-x86-64/tlsdesc-nacl.rd: Likewise.
	* testsuite/ld-x86-64/tlsdesc.rd: Likewise.
	* testsuite/ld-x86-64/tlsgdesc-nacl.rd: Likewise.
	* testsuite/ld-x86-64/tlsgdesc.rd: Likewise.
	* testsuite/ld-x86-64/tlspic-nacl.rd: Likewise.
	* testsuite/ld-x86-64/tlspic.rd: Likewise.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Add missing cleanup in exec_file_locate_attach
@ 2016-02-17 17:04 sergiodj+buildbot
  2016-02-17 18:13 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-02-17 17:04 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 88178e828a0d1af133c19d6165e4d5ee59304adf ***

Author: Gary Benson <gbenson@redhat.com>
Branch: master
Commit: 88178e828a0d1af133c19d6165e4d5ee59304adf

Add missing cleanup in exec_file_locate_attach

exec_file_locate_attach allocates memory for full_exec_path (using
either exec_file_find, source_full_path_of or xstrdup) but this
memory is never freed.  This commit adds the necessary cleanup.

gdb/ChangeLog:

	* exec.c (exec_file_locate_attach): Add missing cleanup.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Fix cleanup in arm_linux_software_single_step
@ 2016-02-16 14:26 sergiodj+buildbot
  2016-02-16 20:43 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-02-16 14:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b442c911ee0e7444ee63edcc7da26089f6023cb6 ***

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

Fix cleanup in arm_linux_software_single_step

I see the following error in testing aarch64 GDB debugging arm
program.

(gdb) PASS: gdb.reverse/readv-reverse.exp: set breakpoint at marker2
continue
Continuing.
=================================================================
==32273==ERROR: AddressSanitizer: attempting free on address which was not malloc()-ed: 0x000000ce4c00 in thread T0
    #0 0x2ba5615645c7 in __interceptor_free (/usr/lib/x86_64-linux-gnu/libasan.so.1+0x545c7)^M
    #1 0x4be8b5 in VEC_CORE_ADDR_cleanup /home/yao/SourceCode/gnu/gdb/git/gdb/common/gdb_vecs.h:34^M
    #2 0x5e6d95 in do_my_cleanups /home/yao/SourceCode/gnu/gdb/git/gdb/common/cleanups.c:154^M
    #3 0x64c99a in fetch_inferior_event /home/yao/SourceCode/gnu/gdb/git/gdb/infrun.c:3975^M
    #4 0x678437 in inferior_event_handler /home/yao/SourceCode/gnu/gdb/git/gdb/inf-loop.c:44^M
    #5 0x5078f6 in remote_async_serial_handler /home/yao/SourceCode/gnu/gdb/git/gdb/remote.c:13223^M
    #6 0x4cecfd in run_async_handler_and_reschedule /home/yao/SourceCode/gnu/gdb/git/gdb/ser-base.c:137^M
    #7 0x676864 in gdb_wait_for_event /home/yao/SourceCode/gnu/gdb/git/gdb/event-loop.c:834^M
    #8 0x676a27 in gdb_do_one_event /home/yao/SourceCode/gnu/gdb/git/gdb/event-loop.c:323^M
    #9 0x676aed in start_event_loop /home/yao/SourceCode/gnu/gdb/git/gdb/event-loop.c:347^M
    #10 0x6706d2 in captured_command_loop /home/yao/SourceCode/gnu/gdb/git/gdb/main.c:318^M
    #11 0x66db8c in catch_errors /home/yao/SourceCode/gnu/gdb/git/gdb/exceptions.c:240^M
    #12 0x6716dd in captured_main /home/yao/SourceCode/gnu/gdb/git/gdb/main.c:1157^M
    #13 0x66db8c in catch_errors /home/yao/SourceCode/gnu/gdb/git/gdb/exceptions.c:240^M
    #14 0x671b7a in gdb_main /home/yao/SourceCode/gnu/gdb/git/gdb/main.c:1165^M
    #15 0x467684 in main /home/yao/SourceCode/gnu/gdb/git/gdb/gdb.c:32^M
    #16 0x2ba563ed7ec4 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21ec4)^M
    #17 0x4676b2 (/scratch/yao/gdb/build-git/aarch64-linux-gnu/gdb/gdb+0x4676b2)

looks we should discard cleanup if function
arm_linux_software_single_step returns early, or create cleanup when
it is needed.

gdb:

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

	* arm-linux-tdep.c (arm_linux_software_single_step): Assign
	'old_chain' later.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Add parentheses to prevent truncated addresses
@ 2016-02-16  0:16 sergiodj+buildbot
  2016-02-16 16:22 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-02-16  0:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4fd7268abff6f99dbbb78505f095bf1f54064db7 ***

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

Add parentheses to prevent truncated addresses

	* i386-dis.c (print_insn): Parenthesize expression to prevent
	truncated addresses.
	(OP_J): Likewise.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Fix more testcases with standard_output_file.
@ 2016-02-15 18:15 sergiodj+buildbot
  2016-02-16 12:45 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-02-15 18:15 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c99dbb4246fedd500dbdd50514589fc7f95d80c0 ***

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

Fix more testcases with standard_output_file.

Since
	commit 2151ccc56c74b55a8f0debf0724a495368f92591
	Author: Simon Marchi <simon.marchi@ericsson.com>
	Date:   Mon Feb 8 14:02:36 2016 -0500
	    Always organize test artifacts in a directory hierarchy
these testfiles could not build.

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

	* gdb.arch/i386-gnu-cfi.exp: Use standard_output_file.
	* gdb.arch/i386-prologue.exp: Likewise.
	* gdb.arch/i386-size.exp: Likewise.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Enhance GAS's .section directive so that it can take numeric values for the flags and type fields. (ELF only)
@ 2016-02-15 11:25 sergiodj+buildbot
  2016-02-15 13:06 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-02-15 11:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9fb71ee49fc37163697e4f34e16097928eb83d66 ***

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

Enhance GAS's .section directive so that it can take numeric values for the flags and type fields.  (ELF only)

gas	* doc/as.texinfo (.section): Document that numeric values can now
	be used for the flags and type fields of the ELF target's .section
	directive.  Add notes about the restrictions on setting flags and
	types.
	* config/obj-elf.c (obj_elf_change_section): Allow known sections
	to be given processor specific section types.  Allow processor and
	application specific flags of a section to be set after
	definition.
	(obj_elf_parse_section_letters): Handle parsing numeric values.
	(obj_elf_section_type): Handle parsing numeric values.
	(obj_elf_section): Allow numeric type values.
	* config/obj-elf.h (obj_elf_change_section): Update prototype.
	* testsuite/gas/elf/section10.d: New test.
	* testsuite/gas/elf/section10.s: Source file for new test.
	* testsuite/gas/elf/elf.exp: Run the new test.
	* testsuite/gas/i386/ilp32/x86-64-unwind.d: Remove dependency upon
	the description of the flags produced by readelf.
	* testsuite/gas/tic6x/scomm-directive-4.d: Likewise.
	* NEWS: Mention the new feature.

bfd	* elf-bfd.h (struct bfd_elf_special_section): Use unsigned values
	for length and type fields.  Use a signed value for the
	suffix_length field.

binutils* readelf.c (get_section_type_name): Add hex prefix to offsets
	printed for LOPROC and LOOS values.  Ensure that a result is
	always returned for the V850 target, even when an unrecognised
	processor specific value is encountered.
	(process_section_headers): Display key values in the order in
	which they appear to the user.  Add the "C (compressed)" value to
	the list.

ld	* testsuite/ld-i386/pr12718.d: Remove dependency upon the
	description of the flags produced by readelf.
	* testsuite/ld-i386/pr12921.d: Likewise.
	* testsuite/ld-i386/tlsbin-nacl.rd: Likewise.
	* testsuite/ld-i386/tlsbin.rd: Likewise.
	* testsuite/ld-i386/tlsbindesc-nacl.rd: Likewise.
	* testsuite/ld-i386/tlsbindesc.rd: Likewise.
	* testsuite/ld-i386/tlsdesc-nacl.rd: Likewise.
	* testsuite/ld-i386/tlsdesc.rd: Likewise.
	* testsuite/ld-i386/tlsgdesc-nacl.rd: Likewise.
	* testsuite/ld-i386/tlsgdesc.rd: Likewise.
	* testsuite/ld-i386/tlsnopic-nacl.rd: Likewise.
	* testsuite/ld-i386/tlsnopic.rd: Likewise.
	* testsuite/ld-i386/tlspic-nacl.rd: Likewise.
	* testsuite/ld-i386/tlspic.rd: Likewise.
	* testsuite/ld-s390/tlsbin.rd: Likewise.
	* testsuite/ld-s390/tlsbin_64.rd: Likewise.
	* testsuite/ld-s390/tlspic.rd: Likewise.
	* testsuite/ld-s390/tlspic_64.rd: Likewise.
	* testsuite/ld-sh/tlsbin-2.d: Likewise.
	* testsuite/ld-sh/tlspic-2.d: Likewise.
	* testsuite/ld-tic6x/common.d: Likewise.
	* testsuite/ld-tic6x/shlib-1.rd: Likewise.
	* testsuite/ld-tic6x/shlib-1b.rd: Likewise.
	* testsuite/ld-tic6x/shlib-1r.rd: Likewise.
	* testsuite/ld-tic6x/shlib-1rb.rd: Likewise.
	* testsuite/ld-tic6x/shlib-app-1.rd: Likewise.
	* testsuite/ld-tic6x/shlib-app-1b.rd: Likewise.
	* testsuite/ld-tic6x/shlib-app-1r.rd: Likewise.
	* testsuite/ld-tic6x/shlib-app-1rb.rd: Likewise.
	* testsuite/ld-tic6x/shlib-noindex.rd: Likewise.
	* testsuite/ld-tic6x/static-app-1.rd: Likewise.
	* testsuite/ld-tic6x/static-app-1b.rd: Likewise.
	* testsuite/ld-tic6x/static-app-1r.rd: Likewise.
	* testsuite/ld-tic6x/static-app-1rb.rd: Likewise.
	* testsuite/ld-x86-64/ilp32-4-nacl.d: Likewise.
	* testsuite/ld-x86-64/ilp32-4.d: Likewise.
	* testsuite/ld-x86-64/pr12718.d: Likewise.
	* testsuite/ld-x86-64/pr12921.d: Likewise.
	* testsuite/ld-x86-64/split-by-file-nacl.rd: Likewise.
	* testsuite/ld-x86-64/split-by-file.rd: Likewise.
	* testsuite/ld-x86-64/tlsbin-nacl.rd: Likewise.
	* testsuite/ld-x86-64/tlsbin.rd: Likewise.
	* testsuite/ld-x86-64/tlsbindesc-nacl.rd: Likewise.
	* testsuite/ld-x86-64/tlsbindesc.rd: Likewise.
	* testsuite/ld-x86-64/tlsdesc-nacl.rd: Likewise.
	* testsuite/ld-x86-64/tlsdesc.rd: Likewise.
	* testsuite/ld-x86-64/tlsgdesc-nacl.rd: Likewise.
	* testsuite/ld-x86-64/tlsgdesc.rd: Likewise.
	* testsuite/ld-x86-64/tlspic-nacl.rd: Likewise.
	* testsuite/ld-x86-64/tlspic.rd: Likewise.
	* testsuite/ld-xtensa/tlsbin.rd: Likewise.
	* testsuite/ld-xtensa/tlspic.rd: Likewise.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Don't print 0x for core_addr_to_string_nz
@ 2016-02-15 10:19 sergiodj+buildbot
  2016-02-15 11:36 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-02-15 10:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0a0da55626b632a8b8beb6c7878b866861e5daee ***

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

Don't print 0x for core_addr_to_string_nz

core_addr_to_string_nz returns string which has "0x" prefix, so don't
need to print "0x" again.  This patch is to remove the "0x".

gdb:

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

	* aarch64-tdep.c (aarch64_analyze_prologue): Remove "0x".


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] i386-biarch-core.exp: Use standard_output_file
@ 2016-02-12 19:08 sergiodj+buildbot
  2016-02-12 20:59 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-02-12 19:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 97e9415187158a9dfb3b662888a5d7b5e3bd8244 ***

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

i386-biarch-core.exp: Use standard_output_file

Fix the core file path to use the standard output directory.

gdb/testsuite/ChangeLog:

	* i386-biarch-core.exp: Define corefile using
	standard_output_file.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] stack: check frame_unwind_caller_id
@ 2016-02-12  9:10 sergiodj+buildbot
  2016-02-12 12:45 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-02-12  9:10 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a038fa3e14a477d4d72a26c2e139fa47d2774be2 ***

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

stack: check frame_unwind_caller_id

Callers of frame_unwind_caller_* functions are supposed to check
frame_unwind_caller_id.

Add such a check to frame_info and treat an invalid caller ID as if the caller
PC were not available.

gdb/
	* stack.c (frame_info): Check frame_unwind_caller_id.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
[parent not found: <9f5fed7852cae412443957862d759660cfcb3fd5@gdb-build>]
* [binutils-gdb] Add missing quotes to gdb/testsuite/README
@ 2016-02-11 20:15 sergiodj+buildbot
  2016-02-12  9:09 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-02-11 20:15 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT acc23c113ab9602707574e7df120f96170a9731c ***

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

Add missing quotes to gdb/testsuite/README

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

	* README (Parallel testing): Add missing double quotes.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
[parent not found: <18d3cec54e1b4fce278dba436484846f8048d7d6@gdb-build>]
* [binutils-gdb] arm-tdep.c: Change type of insn parameters
@ 2016-02-11 18:30 sergiodj+buildbot
  2016-02-12  4:31 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-02-11 18:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 615234c107e5dcdefff78596971266e9346b3f76 ***

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

arm-tdep.c: Change type of insn parameters

Almost obvious... change the type of some insn parameters, so that it
matches the rest of the code.

gdb/ChangeLog:

	* arm-tdep.c (thumb_copy_unmodified_16bit): Change type of insn.
	(thumb_copy_b): Likewise.
	(arm_decode_b_bl_ldmstm): Likewise.
	(thumb_copy_16bit_ldr_literal): Likewise.
	(thumb_copy_pop_pc_16bit): Likewise.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
[parent not found: <e909d859f5635d66e79fef467da70d6090bfae1b@gdb-build>]
* [binutils-gdb] Clear *VAL in regcache_raw_read_unsigned
@ 2016-02-10 17:06 sergiodj+buildbot
  2016-02-11 18:52 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-02-10 17:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9f6a71b4bfdad8fa2fe33e86f799fa0d362973dc ***

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

Clear *VAL in regcache_raw_read_unsigned

We have function regcache_raw_read_unsigned defined in both GDB and
GDBserver, so that it is used in common like this,

  ULONGEST value;
  status = regcache_raw_read_unsigned (regcache, regnum, &value);

'value' is correctly set in GDB side, but may not be correctly set
in GDBserver, because &value is passed in regcache_raw_read_unsigned
but collect_register may only set part of the whole variable.  In my
test, I see the top half of 'value' is garbage.  This patch fixes this
problem by clearing *VAL before calling collect_register.

gdb/gdbserver:

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

	* regcache.c (regcache_raw_read_unsigned): Clear *VAL.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Add support for ARC instruction relaxation in the assembler.
@ 2016-02-10 12:21 sergiodj+buildbot
  2016-02-11 11:37 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-02-10 12:21 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4670103e86f59a80259fd593a6949d693382e536 ***

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

Add support for ARC instruction relaxation in the assembler.

gas/
2016-01-26  Claudiu Zissulescu  <claziss@synopsys.com>
	    Janek van Oirschot <jvanoirs@synopsys.com>

        * config/tc-arc.h (TC_FRAG_TYPE, TC_PCREL_ADJUST, MAX_INSN_ARGS)
        (MAX_INSN_FLGS, MAX_FLAG_NAME_LENGHT, TC_GENERIC_RELAX_TABLE):
        Define.
        (arc_flags, arc_relax_type): New structure.
        * config/tc-arc.c (FRAG_MAX_GROWTH, RELAX_TABLE_ENTRY)
	(RELAX_TABLE_ENTRY_MAX): New define.
        (relaxation_state, md_relax_table, arc_relaxable_insns)
	(arc_num_relaxable_ins): New variable.
	(rlx_operand_type, arc_rlx_types): New enums.
	(arc_relaxable_ins): New structure.
        (OPTION_RELAX): New option.
        (arc_insn): New relax member.
        (arc_flags): Remove.
        (relax_insn_p): New function.
        (apply_fixups): Likewise.
        (relaxable_operand): Likewise.
        (may_relax_expr): Likewise.
        (relaxable_flag): Likewise.
        (arc_pcrel_adjust): Likewise.
        (md_estimate_size_before_relax): Implement.
        (md_convert_frag): Likewise.
        (md_parse_option): Handle new mrelax option.
        (md_show_usage): Likewise.
        (assemble_insn): Set relax member.
        (emit_insn0): New function.
        (emit_insn1): Likewise.
        (emit_insn): Handle relaxation case.
	* NEWS: Mention the new relaxation option.
	* doc/c-arc.texi (ARC Options): Document new mrelax option.

gas/testsuite
2016-01-26  Claudiu Zissulescu  <claziss@synopsys.com>

        * gas/arc/relax-avoid1.d: New file.
        * gas/arc/relax-avoid1.s: Likewise.
        * gas/arc/relax-avoid2.d: Likewise.
        * gas/arc/relax-avoid2.s: Likewise.
        * gas/arc/relax-avoid3.d: Likewise.
        * gas/arc/relax-avoid3.s: Likewise.
	* gas/arc/relax-b.d: Likewise.
        * gas/arc/relax-b.s: Likewise.

include/opcode/
2016-01-26  Claudiu Zissulescu  <claziss@synopsys.com>
	    Janek van Oirschot  <jvanoirs@synopsys.com>

        * arc.h (arc_opcode arc_relax_opcodes, arc_num_relax_opcodes):
        Declare.

opcodes/
2016-01-26  Claudiu Zissulescu  <claziss@synopsys.com>
	    Janek van Oirschot  <jvanoirs@synopsys.com>

        * arc-opc.c (arc_relax_opcodes, arc_num_relax_opcodes): New
        variable.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] breakpoints/19546: Fix crash after updating breakpoints
@ 2016-02-10  0:25 sergiodj+buildbot
  2016-02-10 12:32 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-02-10  0:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9ef9e6a6a0dd8f948708cb67c9afcfd0be40cb0a ***

Author: Keith Seitz <keiths@redhat.com>
Branch: master
Commit: 9ef9e6a6a0dd8f948708cb67c9afcfd0be40cb0a

breakpoints/19546: Fix crash after updating breakpoints

One of the last checks update_breakpoints_after_exec does while looping
over the list of breakpoints is check that the breakpoint has a valid
location spec. It uses event_location_empty_p to check if the location spec
is "empty", and if it is, the breakpoint is deleted.

momentary_breakpoint types rely on setting the breakpoint structure's
location spec to NULL, thereby causing an update to delete the breakpoint.
However, event_location_empty_p assumed that locations were never NULL.
As a result, GDB would crash dereferencing a NULL pointer whenever
update_breakpoints_after_exec would encounter a momentary_breakpoint.

This patch creates a new wrapper/helper function which tests that the given
breakpoint's location spec is non-NULL and if it is not "empty"
or "unspecified."

gdb/ChangeLog

	PR breakpoints/19546
	* breakpoint.c (breakpoint_event_location_empty_p): New function.
	(update_breakpoints_after_exec, bkpt_re_set): Use this new function
	instead of event_location_empty_p.

gdb/testsuite/ChangeLog

	PR breakpoints/19546
	* gdb.base/infcall-exec.c: New file.
	* gdb.base/infcall-exec2.c: New file.
	* gdb.base/infcall-exec.exp: New file.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Use string_to_event_location_basic in guile.
@ 2016-02-09 23:05 sergiodj+buildbot
  2016-02-10 10:08 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-02-09 23:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a96e36da2f5278949099b0b985b2fa6ce474b135 ***

Author: Keith Seitz <keiths@redhat.com>
Branch: master
Commit: a96e36da2f5278949099b0b985b2fa6ce474b135

Use string_to_event_location_basic in guile.

This patch, analogous to the previous python patch, implements proper
legacy linespec support in guile code using the newly introduced
string_to_event_location_basic.

gdb/ChangeLog

	* guile/scm-breakpoint.c (gdbscm_register_breakpoint_x): Skip
	leading whitespace and use string_to_event_location_basic instead
	of new_linespec_location.

gdb/testsuite/ChangeLog

	* gdb.guile/scm-breakpoint.exp (test_bkpt_address): New procedure.
	(toplevel): Call test_bkpt_address.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] python/19506 -- gdb.Breakpoint address location regression
@ 2016-02-09 22:56 sergiodj+buildbot
  2016-02-10  4:23 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-02-09 22:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9f61929fd82fb632ee7c3be883d7086afc5c65d0 ***

Author: Keith Seitz <keiths@redhat.com>
Branch: master
Commit: 9f61929fd82fb632ee7c3be883d7086afc5c65d0

python/19506 -- gdb.Breakpoint address location regression

Now that "legacy" linespecs benefit from consolidated support in
string_to_event_location_basic, python's Breakpoint command should use this
function to turn strings into event locations.

As a result, this patch fixes python/19506. Before:

(gdb) python gdb.Breakpoint("*main")
Traceback (most recent call last):
  File "<string>", line 1, in <module>
RuntimeError: Function "*main" not defined.
Error while executing Python code.

After:

(gdb) python gdb.Breakpoint("*main")
Breakpoint 1 at 0x4005fb: file ../../../src/gdb/testsuite/gdb.python/py-breakpoint.c, line 32.

gdb/ChangeLog

	PR python/19506
	* python/py-breakpoint.c (bppy_init): Use
	string_to_event_location_basic instead of new_linespec_location.

gdb/testsuite/ChangeLog

	PR python/19506
	* gdb.python/py-breakpoint.exp (test_bkpt_address): New procedure.
	(toplevel): Call test_bkpt_address.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
[parent not found: <8adce0342f5f50aba0154fc56ca59df45b219738@gdb-build>]
* [binutils-gdb] Fix PR19548: Breakpoint re-set inserts breakpoints when it shouldn't
@ 2016-02-09 12:41 sergiodj+buildbot
  2016-02-09 19:41 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-02-09 12:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2a7f3dffced7a20c992e1488d9f05fed8b8001fd ***

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

Fix PR19548: Breakpoint re-set inserts breakpoints when it shouldn't

PR19548 shows that we still have problems related to 13fd3ff34329:

 [PR17431: following execs with "breakpoint always-inserted on"]
 https://sourceware.org/ml/gdb-patches/2014-09/msg00733.html

The problem this time is that we currently update the global location
list and try to insert breakpoint locations after re-setting _each_
breakpoint in turn.

Say:

 - We have _more_ than one breakpoint set.  Let's assume 2.

 - There's a breakpoint with a pre-exec address that ends up being an
   unmapped address after the exec.

 - That breakpoint is NOT the first in the breakpoint list.

Then when handling an exec, and we re-set the first breakpoint in the
breakpoint list, we mistakently try to install the old pre-exec /
un-re-set locations of the other breakpoint, which fails:

 (gdb) continue
 Continuing.
 process 28295 is executing new program: (...)/execl-update-breakpoints2
 Error in re-setting breakpoint 1: Warning:
 Cannot insert breakpoint 2.
 Cannot access memory at address 0x1000764

 Breakpoint 1, main (argc=1, argv=0x7fffffffd368) at /home/pedro/gdb/mygit/src/gdb/testsuite/gdb.base/execl-update-breakpoints.c:34
 34        len = strlen (argv[0]);
 (gdb)

Fix this by deferring the global location list update till after all
breakpoints are re-set.

Tested on x86_64 Fedora 20, native and gdbserver.

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

	PR breakpoints/19548
	* breakpoint.c (create_overlay_event_breakpoint): Don't update
	global location list here.
	(create_longjmp_master_breakpoint)
	(create_std_terminate_master_breakpoint)
	(create_exception_master_breakpoint, create_jit_event_breakpoint)
	(update_breakpoint_locations):
	(breakpoint_re_set): Update global location list after all
	breakpoints are re-set.

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

	PR breakpoints/19548
	* gdb.base/execl-update-breakpoints.c (some_function): New
	function.
	(main): Call it.
	* gdb.base/execl-update-breakpoints.exp: Add a second breakpoint.
	Tighten expected GDB output.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Add a more helpful warning message to explain why some AArch64 relocations can overflow.
@ 2016-02-09 11:06 sergiodj+buildbot
  2016-02-09 16:08 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-02-09 11:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 027e9c750c20fe8031a2b6d6272cd57bbf445df5 ***

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

Add a more helpful warning message to explain why some AArch64 relocations can overflow.

bfd	* elfnn-aarch64.c (elfNN_aarch64_relocate_section): Add a more
	helpful warning message to explain why certain AArch64 relocs
	might overflow.

ld	* testsuite/ld-aarch64/reloc-overflow-bad.d: New test.
	* testsuite/ld-aarch64/reloc-overflow-1.s: New source file.
	* testsuite/ld-aarch64/reloc-overflow-2.s: New source file.
	* testsuite/ld-aarch64/aarch64-elf.exp: Run the new test.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Revert "Add a more helpful warning message to explain why some AArch64 relocations can overflow."
@ 2016-02-09 10:48 sergiodj+buildbot
  2016-02-09 13:35 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-02-09 10:48 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0635c8759326e9431604b3359185cbf96740521d ***

Author: Walfred Tedeschi <walfred.tedeschi@intel.com>
Branch: master
Commit: 0635c8759326e9431604b3359185cbf96740521d

Revert "Add a more helpful warning message to explain why some AArch64 relocations can overflow."

This reverts commit 2ea53e003163338a403d5afbb2046cafb8f3abe9.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Fix build breakage
@ 2016-02-09 10:38 sergiodj+buildbot
  2016-02-09 12:23 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-02-09 10:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 222cab58b7ed37df6e01dacb0932f400a2588137 ***

Author: Walfred Tedeschi <walfred.tedeschi@intel.com>
Branch: master
Commit: 222cab58b7ed37df6e01dacb0932f400a2588137

Fix build breakage

Add a cast to reinterpret a void* as a gdb_byte*.

2016-02-09  Walfred Tedeschi  <walfred.tedeschi@intel.com>

gdb/gdbserver/ChangeLog:

        * linux-x86-low.c (x86_siginfo_fixup): Add cast to gdb_byte*.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Fix macro redefinition error on Solaris
@ 2016-02-09  5:24 sergiodj+buildbot
  2016-02-09  6:28 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-02-09  5:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 24f5f69a8a1d09c317a5f28d324fca73a8a0b930 ***

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

Fix macro redefinition error on Solaris

	PR 16583
	* elf/common.h (AT_SUN_HWCAP): Undef before defining.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Fix in-tree, parallel running of Ada tests
@ 2016-02-08 19:12 sergiodj+buildbot
  2016-02-08 21:19 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-02-08 19:12 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 437277d47a15711f29e02e5265ce8bbb8c8ef4f5 ***

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

Fix in-tree, parallel running of Ada tests

While testing the following patch,

  [PATCH] Always organize test artifacts in a directory hierarchy
  https://sourceware.org/ml/gdb-patches/2016-01/msg00133.html

I noticed that it broke Ada testing.  This lead me to think that
parallel testing when building in-tree didn't work previously in Ada.
It is confirmed by this test:

$ make check TESTS="gdb.ada/fun_addr.exp" -j 2
...
Running ./gdb.ada/fun_addr.exp ...
FAIL: gdb.ada/fun_addr.exp: compilation foo.adb
...

This patch fixes in-tree parallel testing for Ada, and consequently
serial and parallel testing when the aforementioned patch is applied.

The problem originates from the fact that Ada support code cd's to the
builddir before compiling.  In itself it's not a problem, it allows to
place intermediate auto-generated files in that directory.  The Ada
compilation refers to the source file, which is in another directory,
only by its base name (e.g. foo.adb).  In serial mode, that worked
because builddir was the same as the source directory (e.g.
gdb.ada/fun_addr/).  In an out-of-tree build, it works because the
source directory is added as an include directory (note: this is not the
same $srcdir as autoconf's):

  set srcdir [file dirname $source]
  additional_flags=-I$srcdir

which becomes:

  additional_flags=-I/home/emaisin/build/binutils-gdb/gdb/testsuite/gdb.ada/fun_addr

However, when building in-tree, srcdir is relative: ./gdb.ada/fun_addr.
When using parallel or always-in-outputs-directory mode, we are cd'ed in
the outputs directory.  So -I$srcdir is relative to the current
directory, which is wrong.

To fix it, I made the TCL variable srcdir (set in site.exp, from which
everything else is derived) always absolute.  It is done by assigning
autoconf's abs_srcdir instead of autoconf's srcdir.  This way -I$srcdir
will always be good, regardless of where we cd'ed to.  A small apparent
change is that when running tests, DejaGnu will say:

  Running /tmp/binutils-gdb/gdb/testsuite/gdb.ada/fun_addr.exp ...

instead of

  Running ./gdb.ada/fun_addr.exp ...

I hope it's not too much of an annoyance.  I think that it should make
the testsuite a tiny bit more robust against other bugs of the same
class.

Regtested in & out of tree, only with native target.

gdb/testsuite/ChangeLog:

	* Makefile.in (abs_srcdir): Assign @abs_srcdir@.
	(site.exp): Assign abs_srcdir to tcl's srcdir.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Fix formatting of pe-mips.c file.
@ 2016-02-05 10:26 sergiodj+buildbot
  2016-02-05 12:20 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-02-05 10:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6f57d0469ae5e73643aa5ef96a10e6bae7a79a15 ***

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

Fix formatting of pe-mips.c file.

	* pe-mips.c (coff_mips_reloc): Fix formatting.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [testsuite] Remove BASEDIR
@ 2016-02-04 15:57 sergiodj+buildbot
  2016-02-04 17:30 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-02-04 15:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 31d913c7e4e84edf88b4324c3a9a8fb31c8206ec ***

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

[testsuite] Remove BASEDIR

BASEDIR was added by https://sourceware.org/ml/gdb-patches/2013-10/msg00587.html
in order to handle the different directory layout in serial testing
and parallel testing.  BASEDIR is "gdb.base" in serial testing and is
"outputs/gdb.base/TESTNAME" in parallel testing.  However, it doesn't
work if the GDBserver is in remote target, like this,

$ make check RUNTESTFLAGS='--target_board=remote-gdbserver-on-localhost foll-vfork.exp foll-exec.exp'
FAIL: gdb.base/foll-exec.exp: continue to first exec catchpoint (the program exited)
FAIL: gdb.base/foll-vfork.exp: exec: vfork and exec child follow, to main bp: continue to bp (the program exited)
FAIL: gdb.base/foll-vfork.exp: exec: vfork child follow, finish after tcatch vfork: finish (the program exited)
FAIL: gdb.base/foll-vfork.exp: exec: vfork relations in info inferiors: continue to bp (the program exited)

these tests fail because the executable can't be found.  With target
board native-gdbserver, the program is spawned this way,

 spawn ../gdbserver/gdbserver --once :2347 /scratch/yao/gdb/build-git/x86_64/gdb/testsuite/gdb.base/foll-vfork

so BASEDIR is correct.  However, with target board
remote-gdbserver-on-localhost, the program is spawned

  spawn /usr/bin/ssh -l yao localhost /scratch/yao/gdb/build-git/x86_64/gdb/testsuite/../gdbserver/gdbserver --once :2346 /scratch/yao/gdb/build-git/x86_64/gdb/testsuite/gdb.base/foll-vfork

so BASEDIR (either "gdb.base" or "outputs/gdb.base/TESTNAME") makes no
sense.

I had a fix that pass absolute directory to BASEDIR, but it assumes
that directory structure is the same on build and target, and it
doesn't work in remote host case.  The current fix in this patch is
to get the directory from argv[0].  In any case, the program to be
exec'ed is at the same directory with the main program.

Note that these tests do "next N" to let program stop at the desired
line, but it is fragile, because GDB for different targets may skip
function prologue slightly differently, so I replace some of them by
"tbreak on LINE NUMBER and continue".

gdb/testsuite:

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

	* gdb.base/foll-exec-mode.c: Include limits.h.
	(main): Add parameters argc and argv.  Get directory from
	argv[0].
	* gdb.base/foll-exec-mode.exp: Don't pass -DBASEDIR in
	compilation.
	* gdb.base/foll-exec.c: Include limits.h.
	(main): Add parameters argc and argv.
	Get directory from argv[0].
	* gdb.base/foll-exec.exp: Don't pass -DBASEDIR in compilation.
	Adjust tests on the number of lines as source code changed.
	* gdb.base/foll-vfork-exit.c: Include limits.h.
	(main): Add one line of statement before vfork.
	* gdb.base/foll-vfork.c: Include limits.h and string.h.
	(main): Add parameters argc and argv.  Get directory from
	argv[0].
	* gdb.base/foll-vfork.exp: Don't pass -DBASEDIR in compilation.
	(setup_gdb): Set tbreak to skip some source lines.
	* gdb.multi/bkpt-multi-exec.c: Include limits.h.
	(main): Add parameters argc and argv.  Get directory from
	argv[0].
	* gdb.multi/bkpt-multi-exec.exp: Don't pass -DBASEDIR in
	compilation.
	* gdb.multi/multi-arch-exec.c: Include limits.h and string.h.
	(main): Add parameters argc and argv.  Get directory from
	argv[0].
	* gdb.multi/multi-arch-exec.exp: Don't pass -DBASEDIR in
	compilation.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Fix the encoding of the MSP430's RRUX instruction.
@ 2016-02-04 10:06 sergiodj+buildbot
  2016-02-04 11:06 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-02-04 10:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c1d9289fef41b82aa22f63f74aa8e730ec898d3c ***

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

Fix the encoding of the MSP430's RRUX instruction.

	PR target/19561
opcdoe	* msp430-dis.c (print_insn_msp430): Add a special case for
	decoding an RRC instruction with the ZC bit set in the extension
	word.

include	* opcode/msp430.h (IGNORE_CARRY_BIT): New define.
	(RRUX): Synthesise using case 2 rather than 7.

gas	* config/tc-msp430.c (msp430_operands): Remove case 7.  Use case 2
	to handle encoding of RRUX instruction.
	* testsuite/gas/msp430/msp430x.s: Add more tests of the extended
	shift instructions.
	* testsuite/gas/msp430/msp430x.d: Update expected disassembly.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] MAINTAINERS: Add Thiemo Seufer back, as a past maintainer
@ 2016-02-03 22:03 sergiodj+buildbot
  2016-02-03 23:01 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-02-03 22:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3b8f2c8bcf7c6bf1339aa3c3f2d6f129b7878052 ***

Author: Maciej W. Rozycki <macro@linux-mips.org>
Branch: master
Commit: 3b8f2c8bcf7c6bf1339aa3c3f2d6f129b7878052

MAINTAINERS: Add Thiemo Seufer back, as a past maintainer

Complement commit 26e0f8dbd817 ("* MAINTAINERS: Remove Thiemo Seufer.").

	* MAINTAINERS (Past sim maintainers): Add Thiemo Seufer.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] ui-out.c: Remove unused enum
@ 2016-02-02 21:51 sergiodj+buildbot
  2016-02-03  0:17 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-02-02 21:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6456a18b717e7b1ae96d77a2549fbf4da60d6617 ***

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

ui-out.c: Remove unused enum

This is unused since 54eb231c4bca046e8b8cd73461f695e02c5620d5, where
static arrays of ui_out_levels were replaced with vectors.

gdb/ChangeLog:

	* ui-out.c (MAX_UI_OUT_LEVELS): Remove.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] PowerPC64 ELFv2 entry code
@ 2016-02-02 13:44 sergiodj+buildbot
  2016-02-02 20:52 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-02-02 13:44 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 85fabe715c441e1c90fe913e2a6d65f0e487e5e8 ***

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

PowerPC64 ELFv2 entry code

This tightens the condition under which ld optimizes PIC entry code
to non-PIC.

bfd/
	* elf64-ppc.c (ppc64_elf_relocate_section): Further restrict
	ELFv2 entry optimization.
gold/
	* powerpc.cc (relocate): Further restrict ELFv2 entry optimization.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Don't add DT_NEEDED for unmatched symbol
@ 2016-02-01 23:59 sergiodj+buildbot
  2016-02-02 10:29 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-02-01 23:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT aef28989904e92e391fee905e51abc6bb2fd4de0 ***

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

Don't add DT_NEEDED for unmatched symbol

Don't add DT_NEEDED if a symbol from a library loaded via DT_NEEDED
doesn't match the symbol referenced by regular object.

bfd/

	PR ld/19553
	* elflink.c (elf_link_add_object_symbols): Don't add DT_NEEDED
	if a symbol from a library loaded via DT_NEEDED doesn't match
	the symbol referenced by regular object.

ld/testsuite/

	PR ld/19553
	* testsuite/ld-elf/indirect.exp: Run tests for PR ld/19553.
	* testsuite/ld-elf/pr19553.map: New file.
	* testsuite/ld-elf/pr19553.map: Likewise.
	* testsuite/ld-elf/pr19553a.c: Likewise.
	* testsuite/ld-elf/pr19553b.c: Likewise.
	* testsuite/ld-elf/pr19553b.out: Likewise.
	* testsuite/ld-elf/pr19553c.c: Likewise.
	* testsuite/ld-elf/pr19553c.out: Likewise.
	* testsuite/ld-elf/pr19553d.c: Likewise.
	* testsuite/ld-elf/pr19553d.out: Likewise.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] gdb.base/skip.exp: Clean up multiple references to same test name.
@ 2016-02-01 23:33 sergiodj+buildbot
  2016-02-02  1:01 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-02-01 23:33 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9482b9fbb6414468228c618c165e397116a4a8f8 ***

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

gdb.base/skip.exp: Clean up multiple references to same test name.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] gdb: New set/show max-value-size command.
@ 2016-02-01 18:23 sergiodj+buildbot
  2016-02-01 19:24 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-02-01 18:23 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5fdf6324fafd60f967e2e8323fdacf84b1bfcea3 ***

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

gdb: New set/show max-value-size command.

For languages with dynamic types, an incorrect program, or uninitialised
variables within a program, could result in an incorrect, overly large
type being associated with a value.  Currently, attempting to print such
a variable will result in gdb trying to allocate an overly large buffer.

If this large memory allocation fails then the result can be gdb either
terminating, or (due to memory contention) becoming unresponsive for the
user.

A new user visible variable in gdb helps guard against such problems,
two new commands are available:

   set max-value-size
   show max-value-size

The 'max-value-size' is the maximum size of memory in bytes that gdb
will allocate for the contents of a value.  Any attempt to allocate a
value with a size greater than this will result in an error.  The
initial default for this limit is set at 64k, this is based on a similar
limit that exists within the ada specific code.

It is possible for the user to set max-value-size to unlimited, in which
case the old behaviour is restored.

gdb/ChangeLog:

	* value.c (max_value_size): New variable.
	(MIN_VALUE_FOR_MAX_VALUE_SIZE): New define.
	(show_max_value_size): New function.
	(check_type_length_before_alloc): New function.
	(allocate_value_contents): Call check_type_length_before_alloc.
	(set_value_enclosing_type): Likewise.
	(_initialize_values): Add set/show handler for max-value-size.
	* NEWS: Mention new set/show command.

gdb/doc/ChangeLog:

	* gdb.texinfo (Value Sizes): New section.
	(Data): Add the 'Value Sizes' node to the menu.

gdb/testsuite/ChangeLog:

	* gdb.base/max-value-size.c: New file.
	* gdb.base/max-value-size.exp: New file.
	* gdb.base/huge.exp: Disable max-value-size for this test.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Fix NetBSD build with BSD and GNU make(1).
@ 2016-02-01 10:48 sergiodj+buildbot
  2016-02-01 11:48 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-02-01 10:48 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b6471e6e2c88ae473453e3499d9cb6a607a3e068 ***

Author: Kamil Rytarowski <n54@gmx.com>
Branch: master
Commit: b6471e6e2c88ae473453e3499d9cb6a607a3e068

Fix NetBSD build with BSD and GNU make(1).

	* Makefile.am (OPTIONAL_BACKENDS): Add netbsd-core.lo.
	(OPTIONAL_BACKENDS_CFILES): Add netbsd-core.c.
	* Makefile.in: Regenerated.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Fix /usr/bin/ld: final link failed: File truncated error on hppa.
@ 2016-01-31 20:38 sergiodj+buildbot
  2016-01-31 21:39 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-01-31 20:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6d4b2867f8441c7bf75dfef6b3c95a10241f9709 ***

Author: John David Anglin <danglin@gcc.gnu.org>
Branch: master
Commit: 6d4b2867f8441c7bf75dfef6b3c95a10241f9709

Fix /usr/bin/ld: final link failed: File truncated error on hppa.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Fix two misleading indentation warnings
@ 2016-01-29 20:45 sergiodj+buildbot
  2016-01-29 22:01 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-01-29 20:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a2e3e93f4423899d99687da3ce4ac57cbed437f9 ***

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

Fix two misleading indentation warnings

Two small changes so everything builds with latest GCC and its
-Wmisleading-indentation.

In the aarch64-tdep.c case, the two misindented lines should actually be
part of the for loop.  It looks like the indentation is all done using
spaces in that file though...  I fixed it (changed for tabs + spaces) for
the lines I touched.

In the xcoffread.c case, we can simply remove the braces and fix the
indentation.

gdb/ChangeLog:

	* aarch64-tdep.c (aarch64_record_asimd_load_store): Add braces
	to for include additional lines.
	* xcoffread.c (scan_xcoff_symtab): Remove unnecessary braces.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Align dlang demangle tests with libiberty.
@ 2016-01-28 21:08 sergiodj+buildbot
  2016-01-28 23:29 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-01-28 21:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4324c94dd727bad65616817dacc5a75ede606967 ***

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

Align dlang demangle tests with libiberty.

gdb/testsuite/ChangeLog:
	* gdb.dlang/demangle.exp: Sync tests from libiberty testsuite.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Sync libiberty with GCC.
@ 2016-01-28 21:00 sergiodj+buildbot
  2016-01-28 21:58 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-01-28 21:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9d98de835cb018419e0ef97db37fcf9061247750 ***

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

Sync libiberty with GCC.

libiberty/ChangeLog:
	* d-demangle.c (dlang_call_convention): Handle extern Objective-C
	function calling convention.
	(dlang_call_convention_p): Likewise.
	(dlang_type): Likewise.
	* testsuite/d-demangle-expected: Add coverage tests.

	* d-demangle.c (dlang_function_args): Append ',' for variadic functions
	only if parameters were seen before the elipsis symbol.
	* testsuite/d-demangle-expected: Add coverage test for parameter-less
	variadic functions.

	* d-demangle.c (dlang_type): Handle function types only in the context
	of seeing a pointer type symbol.
	* testsuite/d-demangle-expected: Update function pointer tests.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [testsuite] Fix tiemout fail in gdb.fortran/vla-value.exp
@ 2016-01-28 14:39 sergiodj+buildbot
  2016-01-28 16:33 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-01-28 14:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7fe8399de97e50f631ce28ceb42515862a927556 ***

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

[testsuite] Fix tiemout fail in gdb.fortran/vla-value.exp

In vla.f90, this single line of source is compiled to many instructions,

  vla2(:, :, :) = 1311                ! vla2-allocated

it is quite slow (about several minutes in my testing) to step over this
source line without range stepping.  This patch is to increase the timeout
value by 15 times, which is a magic number to make sure timeout disappears
in my testing with a slow arm-linux board.

gdb/testsuite:

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

	* gdb.fortran/vla-value.exp: Wrap test with with_timeout_factor.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] rx: Treat scalars larger than 8 bytes as aggregates in rx_push_dummy_call.
@ 2016-01-27 19:48 sergiodj+buildbot
  2016-01-27 21:07 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-01-27 19:48 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 94715c179098ab86bf188fae4a32e2283c5f173f ***

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

rx: Treat scalars larger than 8 bytes as aggregates in rx_push_dummy_call.

This patch fixes the following failures (which are also GDB internal errors)
for the -m64bit-doubles multilib:

FAIL: gdb.base/callfuncs.exp: p t_double_complex_values(dc1, dc2) (GDB internal error)
FAIL: gdb.base/callfuncs.exp: p t_double_complex_values(dc3, dc4) (GDB internal error)
FAIL: gdb.base/callfuncs.exp: p t_double_complex_many_args(dc1, dc2, dc3, dc4, dc1, dc2, dc3, dc4, dc1, dc2, dc3, dc4, dc1, dc2, dc3, dc4) (GDB internal error)
FAIL: gdb.base/callfuncs.exp: p t_double_complex_many_args(dc1, dc1, dc1, dc1, dc1, dc1, dc1, dc1, dc1, dc1, dc1, dc1, dc1, dc1, dc1, dc1) (GDB internal error)
FAIL: gdb.base/callfuncs.exp: p t_long_double_complex_values(ldc1, ldc2) (GDB internal error)
FAIL: gdb.base/callfuncs.exp: p t_long_double_complex_values(ldc3, ldc4) (GDB internal error)
FAIL: gdb.base/callfuncs.exp: p t_long_double_complex_many_args(ldc1, ldc2, ldc3, ldc4, ldc1, ldc2, ldc3, ldc4, ldc1, ldc2, ldc3, ldc4, ldc1, ldc2, ldc3, ldc4) (GDB internal error)
FAIL: gdb.base/callfuncs.exp: p t_long_double_complex_many_args(ldc1, ldc1, ldc1, ldc1, ldc1, ldc1, ldc1,ldc1, ldc1, ldc1, ldc1, ldc1, ldc1, ldc1, ldc1, ldc1) (GDB internal error)
FAIL: gdb.base/callfuncs.exp: noproto: p t_double_complex_values(dc1, dc2) (GDB internal error)
FAIL: gdb.base/callfuncs.exp: noproto: p t_double_complex_values(dc3, dc4) (GDB internal error)
FAIL: gdb.base/callfuncs.exp: noproto: p t_double_complex_many_args(dc1, dc2, dc3, dc4, dc1, dc2, dc3, dc4, dc1, dc2, dc3, dc4, dc1, dc2, dc3, dc4) (GDB internal error)
FAIL: gdb.base/callfuncs.exp: noproto: p t_double_complex_many_args(dc1, dc1, dc1, dc1, dc1, dc1, dc1, dc1, dc1, dc1, dc1, dc1, dc1, dc1, dc1, dc1) (GDB internal error)
FAIL: gdb.base/callfuncs.exp: noproto: p t_long_double_complex_values(ldc1, ldc2) (GDB internal error)
FAIL: gdb.base/callfuncs.exp: noproto: p t_long_double_complex_values(ldc3, ldc4) (GDB internal error)
FAIL: gdb.base/callfuncs.exp: noproto: p t_long_double_complex_many_args(ldc1, ldc2, ldc3, ldc4, ldc1, ldc2, ldc3, ldc4, ldc1, ldc2, ldc3, ldc4, ldc1, ldc2, ldc3, ldc4) (GDB internal error)
FAIL: gdb.base/callfuncs.exp: noproto: p t_long_double_complex_many_args(ldc1, ldc1, ldc1, ldc1, ldc1, ldc1, ldc1,ldc1, ldc1, ldc1, ldc1, ldc1, ldc1, ldc1, ldc1, ldc1) (GDB internal error)
FAIL: gdb.base/varargs.exp: print find_max_double_real(4, dc1, dc2, dc3, dc4) (GDB internal error)
FAIL: gdb.base/varargs.exp: print find_max_long_double_real(4, ldc1, ldc2, ldc3, ldc4) (GDB internal error)

The assertion failure which is tripped is:

		  gdb_assert (arg_size <= 4);

While it may seem that the patch ought to disallow scalars larger than
4, scalars of size 8 are explicitly handled by the code elsewhere.

This came up because gcc has a complex type that is 16 bytes in length
when 64-bit doubles are used.

gdb/ChangeLog:

	* rx-tdep.c (rx_push_dummy_call): Treat scalars larger than 8
	bytes as aggregates.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [GDBserver] Use regcache_read_pc in install_software_single_step_breakpoints
@ 2016-01-26 14:40 sergiodj+buildbot
  2016-01-26 17:38 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-01-26 14:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d80209703ec2fc85e0a4b3d4d23e7ed448987aca ***

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

[GDBserver] Use regcache_read_pc in install_software_single_step_breakpoints

In install_software_single_step_breakpoints, we've got the regcache
of current_thread, so we don't have to bother get_pc to get pc,
instead we can get pc from regcache directly.  Note that the callers
of install_software_single_step_breakpoints have already switched
current_thread to LWP.

Since the pc is got from regcache_read_pc, in the next patch, we can
get pc inside the implementation of *the_low_target.get_next_pcs and
stop passing pc to *the_low_target.get_next_pcs.

gdb/gdbserver:

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

	* linux-low.c (install_software_single_step_breakpoints): Call
	regcache_read_pc instead of get_pc.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [GDBserver] Check input interrupt after reading in a packet
@ 2016-01-26 14:03 sergiodj+buildbot
  2016-01-26 15:04 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-01-26 14:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 18879fef1741464e522624bcc529048400453e0d ***

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

[GDBserver] Check input interrupt after reading in a packet

GDBserver may read some packet together with '\003' in one go.  We've
already checked '\003' first when reading packet by my patch,

  Check input interrupt first when reading packet
  https://sourceware.org/ml/gdb-patches/2016-01/msg00057.html

but if we don't check '\003' *after* each packet, the interrupt will
be processed next time GDBserver reads from the buffer, so that the
interrupt isn't processed in time.  For example, GDB sends vCont;c and
interrupt (see gdb.base/interrupt-noterm.exp), we'll resume the
inferior and wait once packet vCont;c is seen.  If we don't check the
interrupt character after vCont;c packet, interrupt character will stay
in the buffer unattended until GDBserver returns from the wait, which
may take a while.  Note that since we've read '\003' from file
descriptor, SIGIO signal handler input_interrupt doesn't help either.

This issue can be exposed by hacking the end of getpkt like
@@ -1041,6 +1050,9 @@ getpkt (char *buf)
        }
     }

+  if (readchar_bufcnt > 0)
+    gdb_assert (*readchar_bufp != '\003');
+
   return bp - buf;
 }

and this can trigger internal error,
(gdb) PASS: gdb.base/interrupt-noterm.exp: interrupt
Remote connection closed^M
(gdb) FAIL: gdb.base/interrupt-noterm.exp: inferior received SIGINT
Remote debugging from host 10.2.206.40^M
/home/yao/SourceCode/gnu/gdb/git/gdb/gdbserver/remote-utils.c:1054: A problem internal to GDBserver has been detected.^M
getpkt: Assertion `*readchar_bufp != '\003'' failed.^M

This patch is to peek the buffer, if it is '\003', consume it and call
*the_target->request_interrupt.

gdb/gdbserver:

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

	* remote-utils.c (getpkt): If the buffer isn't empty, and the
	first character is '\003', call *the_target->request_interrupt.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Remove new_thread_notify and dead_thread_notify
@ 2016-01-25 16:27 sergiodj+buildbot
  2016-01-25 20:17 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-01-25 16:27 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a0f8e08a3c357ae24d3244940e1c6b405a0c17cc ***

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

Remove new_thread_notify and dead_thread_notify

They were added by

  PATCH: Multithreaded debugging for gdbserver
  https://sourceware.org/ml/gdb-patches/2002-06/msg00157.html

but as a no-op, and the last usage of them was removed by

  [gdbserver/RFC/RFA] Implement multiprocess extensions, add linux multiproces support.
  https://sourceware.org/ml/gdb-patches/2009-03/msg00667.html

This patch is to remove them.

gdb/gdbserver:

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

	* remote-utils.c (new_thread_notify): Remove.
	(dead_thread_notify): Likewise.
	* remote-utils.h (new_thread_notify): Remove declaration.
	(dead_thread_notify): Likewise.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Fix PR 19461: strange "info thread" behavior in non-stop
@ 2016-01-25 13:48 sergiodj+buildbot
  2016-01-25 16:46 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-01-25 13:48 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a2077e254098828614ef6621cf8df28185e711d0 ***

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

Fix PR 19461: strange "info thread" behavior in non-stop

If you have "set follow-fork child" set, then if you do "info threads"
right after a fork, and before the child reports any other event to
GDB core, you'll see:

(gdb) info threads
  Id   Target Id         Frame
* 1.1  Thread 0x7ffff7fc1740 (LWP 31875) "fork-plus-threa" (running)
  2.1  process 31879 "fork-plus-threa" Selected thread is running.
(gdb)

The "Selected thread is running." bit is a bogus error.  That was GDB
trying to fetch the current frame of thread 2.1, because the external
runnning state is "stopped", and then throwing an error because the
thread is actually running.

This actually affects all-stop + schedule-multiple as well.

The problem here is that on a fork event, GDB doesn't update the
external parent/child running states.

New comprehensive test included.  The "kill inferior 1" / "kill
inferior 2" bits also trip on PR gdb/19494 (hang killing unfollowed
fork children), which was fixed by the previous patch.

gdb/ChangeLog:
2016-01-25  Pedro Alves  <palves@redhat.com>

	PR threads/19461
	* infrun.c (handle_inferior_event_1) <fork/vfork>: Update
	parent/child running states.

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

	PR threads/19461
	* gdb.base/fork-running-state.c: New file.
	* gdb.base/fork-running-state.exp: New file.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Move foreach_with_prefix to lib/gdb.exp
@ 2016-01-25 13:32 sergiodj+buildbot
  2016-01-25 14:34 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-01-25 13:32 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f1da4b11eef6dba04a1cfa579c6ba313718105b8 ***

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

Move foreach_with_prefix to lib/gdb.exp

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

	* gdb.base/step-sw-breakpoint-adjust-pc.exp (foreach_with_prefix):
	Delete, moved to lib/gdb.exp.
	* gdb.threads/forking-threads-plus-breakpoint.exp
	(foreach_with_prefix): Likewise.
	* gdb.threads/process-dies-while-handling-bp.exp
	(foreach_with_prefix): Likewise.
	* lib/gdb.exp (foreach_with_prefix): New procedure.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Add missing end-of-comment marker to previous delta. (Doh!)
@ 2016-01-25  9:54 sergiodj+buildbot
  2016-01-25 10:57 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-01-25  9:54 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c244074cb684302be1378a072b33cdb8dd0dff1f ***

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

Add missing end-of-comment marker to previous delta.  (Doh!)


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Fix memory corruption on Mach-O systems by suppressing a memory tidy up.
@ 2016-01-25  9:41 sergiodj+buildbot
  2016-01-25  9:50 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-01-25  9:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cf466c2ac5ac55bb9b30b96fbdcad564e8c1ccc8 ***

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

Fix memory corruption on Mach-O systems by suppressing a memory tidy up.

	PR target/19435
	* mach-o.c (bfd_mach_o_close_and_cleanup): Suppress code to free
	dsym filename buffer.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] testsuite: gdb.gdb/selftest.exp: Drop expected Thread number
@ 2016-01-22 21:00 sergiodj+buildbot
  2016-01-22 23:09 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-01-22 21:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 092127d743462e370fd1156cb746f814a7b46593 ***

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

testsuite: gdb.gdb/selftest.exp: Drop expected Thread number

Pedro Alves:
Looks like you forgot to amend before pushing though -- the version
checked in still had "Thread 1".

gdb/testsuite/ChangeLog
2016-01-22  Jan Kratochvil  <jan.kratochvil@redhat.com>
	    Pedro Alves  <palves@redhat.com>

	Fix testsuite compatibility with Guile.
	* gdb.gdb/selftest.exp (send ^C to child process): Drop expected Thread
	number.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Fix compile time errors building ARC target on a 32-bit host.
@ 2016-01-21 14:04 sergiodj+buildbot
  2016-01-21 22:46 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-01-21 14:04 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 23a42089156e63bbd2228675e78cdf1ffae63c51 ***

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

Fix compile time errors building ARC target on a 32-bit host.

	* elf32-arc.c (ADD_RELA): Fix compile time warning errors by
	changing the type of _loc to be bfd_byte *.
	(elf_arc_finish_dynamic_symbol): Likewise.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] gdb: Respect CXXFLAGS when building with C++ compiler
@ 2016-01-21 11:45 sergiodj+buildbot
  2016-01-21 20:35 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-01-21 11:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a994041db36c9a6058fe591c7ccd018ed7affc76 ***

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

gdb: Respect CXXFLAGS when building with C++ compiler

Currently, even when built with --enable-build-with-cxx, gdb uses
CFLAGS instead of CXXFLAGS.  This commit fixes it.

CXXFLAGS set in the environment when configure was run is now honored
in the generated gdb/Makefile, and you can also override CXXFLAGS in
the command like at make time, with the usual 'make CXXFLAGS="..."'

Objects built with a C compiler (e.g., gnulib) still honor CFLAGS
instead.

gdb/ChangeLog:
2016-01-21  Pedro Alves  <palves@redhat.com>

	* Makefile.in (COMPILER_CFLAGS): New.
	(CXXFLAGS): Get it from configure.
	(INTERNAL_CFLAGS_BASE, INTERNAL_LDFLAGS): Use COMPILER_CFLAGS
	instead of CFLAGS.
	* build-with-cxx.m4 (GDB_AC_BUILD_WITH_CXX): Set and AC_SUBST
	COMPILER_CFLAGS.
	* configure: Regenerate.

gdb/gdbserver/ChangeLog:
2016-01-21  Pedro Alves  <palves@redhat.com>

	* Makefile.in (COMPILER_CFLAGS, CXXFLAGS): New.
	(INTERNAL_CFLAGS_BASE): Use COMPILER_CFLAGS instead of CFLAGS.
	* configure: Regenerate.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Fix regression introduced in "break *<EXPR>" by explicit location patches.
@ 2016-01-21 10:33 sergiodj+buildbot
  2016-01-21 18:24 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-01-21 10:33 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 305e13e67faaf940ce6eb708847a655a0735a651 ***

Author: Joel Brobecker <brobecker@adacore.com>
Branch: master
Commit: 305e13e67faaf940ce6eb708847a655a0735a651

Fix regression introduced in "break *<EXPR>" by explicit location patches.

A relatively recent patch support for explicit locations, and part
of that patch cleaned up the way we parse breakpoint locations.
Unfortunatly, a small regression crept in for "*<EXPR>" breakpoint
locations. In particular, on PIE programs, one can see the issue by
doing the following, with any program:

    (gdb) b *main
    Breakpoint 1 at 0x51a: file hello.c, line 3.
    (gdb) run
    Starting program: /[...]/hello
    Error in re-setting breakpoint 1: Warning:
    Cannot insert breakpoint 1.
    Cannot access memory at address 0x51a

    Warning:
    Cannot insert breakpoint 1.
    Cannot access memory at address 0x51a

Just for the record, this regression was introduced by:

    commit a06efdd6effd149a1d392df8d62824e44872003a
    Date:   Tue Aug 11 17:09:35 2015 -0700
    Subject: Explicit locations: introduce address locations

What happens is that the patch makes the implicit assumption that
the address computed the first time is static, as if it was designed
to only support litteral expressions (Eg. "*0x1234"). This allows
the shortcut of not re-computing the breakpoint location's address
when re-setting breakpoints.

However, this does not work in general, as demonstrated in the example
above.

This patch plugs that hole simply by saving the original expression
used to compute the address as part of the address location, so as
to then re-evaluate that expression during breakpoint re-set.

gdb/ChangeLog:

        * location.h (new_address_location): Add new parameters
        "addr_string" and "addr_string_len".
        (get_address_string_location): Add declaration.
        * location.c (new_address_location): Add new parameters
        "addr_string" and "addr_string_len".  If not NULL, store
        a copy of the addr_string in the new location as well.
        (get_address_string_location): New function.
        (string_to_event_location): Update call to new_address_location.
        * linespec.c (event_location_to_sals) <ADDRESS_LOCATION>:
        Save the event location in the parser's state before
        passing it to convert_address_location_to_sals.
        * breakpoint.c (create_thread_event_breakpoint): Update call
        to new_address_location.
        (init_breakpoint_sal): Get the event location's string, if any,
        and use it to update call to new_address_location.
        * python/py-finishbreakpoint.c (bpfinishpy_init):
        Update call to new_address_location.
        * spu-tdep.c (spu_catch_start): Likewise.

        * config/djgpp/fnchange.lst: Add entries for
        gdb/testsuite/gdb.base/break-fun-addr1.c and
        gdb/testsuite/gdb.base/break-fun-addr2.c.

gdb/testsuite/ChangeLog:

        * gdb.base/break-fun-addr.exp: New file.
        * gdb.base/break-fun-addr1.c: New file.
        * gdb.base/break-fun-addr2.c: New file.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Convert macros in elf-linux-core.h to inline functions
@ 2016-01-21  9:57 sergiodj+buildbot
  2016-01-21 16:08 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-01-21  9:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT aeb7056972f1b383578204b9151b0ae6d8c1df81 ***

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

Convert macros in elf-linux-core.h to inline functions

Besides changing some macros into inline functions, this removes
redundant memsets and uses bfd_put_* rather than H_PUT_*.

	* elf-linux-core.h (swap_linux_prpsinfo32_out): New function.
	(swap_linux_prpsinfo64_out): New function.
	(LINUX_PRPSINFO32_SWAP_FIELDS): Delete.
	(LINUX_PRPSINFO64_SWAP_FIELDS): Delete.
	* elf.c (elfcore_write_linux_prpsinfo32): Adjust.  Don't memset.
	(elfcore_write_linux_prpsinfo64): Likewise.
	* elf32-ppc.c (swap_ppc_linux_prpsinfo32_out): New function.
	(PPC_LINUX_PRPSINFO32_SWAP_FIELDS): Delete.
	(elfcore_write_ppc_linux_prpsinfo32): Adjust.  Don't memset.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] gnu_vector.exp: Respect `should_kfail' for PR 8549
@ 2016-01-20 18:53 sergiodj+buildbot
  2016-01-21 10:06 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-01-20 18:53 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fd356fa28834fa3a9f22f9157a568264ad045010 ***

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

gnu_vector.exp: Respect `should_kfail' for PR 8549

The gnu_vector test case yields a new FAIL on s390x:

  FAIL: gdb.base/gnu_vector.exp: verify vector return value

It was introduced by commit 77ae9c1933b50 "gdb.base/gnu_vector.exp:
Don't test output from the inferior".  That commit dropped the special
handling for GDB's inability (on some targets) to set the return value.

This change re-establishes the logic from before, converting the above
FAIL to a KFAIL (PRMS gdb/8549).

gdb/testsuite/ChangeLog:

	* gdb.base/gnu_vector.exp: Re-establish handling for should_kfail
	when GDB can not set the vector return value.  Add more comments
	for clarification.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [AArch64] Reject invalid immediate operands to MSR UAO
@ 2016-01-20 14:43 sergiodj+buildbot
  2016-01-21  7:35 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-01-20 14:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0bff6e2d6942690d81ce1f33728de07835b0f5b7 ***

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

[AArch64] Reject invalid immediate operands to MSR UAO

In the instruction to write to the ARMv8.2 PSTATE field UAO,
MSR UAO, #<imm>, the immediate should be either 0 or 1 but GAS accepts
any unsigned 4-bit integer.

This patch implements the constraint on the immediate, generating an
error if the immediate operand is invalid, and adds tests for the
illegal forms.

opcodes/
2016-01-20  Matthew Wahab  <matthew.wahab@arm.com>

	* aarch64-opc.c (operand_general_constraint_met_p): Check validity
	of MSR UAO immediate operand.

gas/
2016-01-20  Matthew Wahab  <matthew.wahab@arm.com>

	* testsuite/gas/aarch64/armv8_2-a-illegal.d: New.
	* testsuite/gas/aarch64/armv8_2-a-illegal.l: New.
	* testsuite/gas/aarch64/armv8_2-a-illegal.s: New.

Change-Id: Ibdec4967c00b1ef3be9dbc43d23b2c70d1a0b28c


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Add support for an ARM specific 'y' section attribute flag to mark the section as NOREAD.
@ 2016-01-20 13:05 sergiodj+buildbot
  2016-01-21  2:22 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-01-20 13:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 91f68a68f992e3f6c3da26c616b5257230bd1eec ***

Author: Mickael Guene <mickael.guene@st.com>
Branch: master
Commit: 91f68a68f992e3f6c3da26c616b5257230bd1eec

Add support for an ARM specific 'y' section attribute flag to mark the section as NOREAD.

bfd/ChangeLog:
      * elf32-arm.c ((elf32_arm_special_sections): Remove catch of noread
      section using '.text.noread' pattern.

gas/ChangeLog:
      * config/obj-elf.c (obj_elf_change_section) : Allow arm section with
      SHF_ARM_NOREAD section flag.
      * config/tc-arm.h (md_elf_section_letter) : Implement this hook to
      handle letter 'y'.
     (arm_elf_section_letter) : Declare it.
      * config/tc-arm.c (arm_elf_section_letter): Handle letter 'y' to set
      SHF_ARM_NOREAD section flag.
      * doc/c-arm.texi (ARM section attribute 'y'): Document it.

gas/testsuite/ChangeLog:
      * gas/arm/section-execute-only.s: New test case.
      * gas/arm/section-execute-only.d: Expected output.

ld/testsuite/ChangeLog:
      * ld-arm/thumb1-noread-not-present-mixing-two-section.s: Add 'y'
      attribute usage.
      * ld-arm/thumb1-noread-present-one-section.s: Likewise.
      * ld-arm/thumb1-noread-present-two-section.s: Likewise.
      * ld-arm/thumb1-input-section-flag-match.s: Likewise.

binutils/ChangeLog:
      * readelf.c (get_elf_section_flags): Display y letter for section
      with SHF_ARM_NOREAD section flag in readelf section output.
      (process_section_headers): Add y letter in readelf section output
      key mapping for ARM architecture.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Add support to readelf for reading FreeBSD ELF core notes.
@ 2016-01-19 17:09 sergiodj+buildbot
  2016-01-19 23:02 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-01-19 17:09 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f4ddf30f1108b2c0b3eee5677c912383ac903256 ***

Author: John Baldwin <jhb@FreeBSD.org>
Branch: master
Commit: f4ddf30f1108b2c0b3eee5677c912383ac903256

Add support to readelf for reading FreeBSD ELF core notes.

binutils/ChangeLog:

	* readelf.c (get_freebsd_elfcore_note_type): New
	(process_note): Add support for FreeBSD core notes.

include/ChangeLog:

	* elf/common.h (NT_FREEBSD_THRMISC): Define.
	(NT_FREEBSD_PROCSTAT_PROC): Define.
	(NT_FREEBSD_PROCSTAT_FILES): Define.
	(NT_FREEBSD_PROCSTAT_VMMAP): Define.
	(NT_FREEBSD_PROCSTAT_GROUPS): Define.
	(NT_FREEBSD_PROCSTAT_UMASK): Define.
	(NT_FREEBSD_PROCSTAT_RLIMIT): Define.
	(NT_FREEBSD_PROCSTAT_OSREL): Define.
	(NT_FREEBSD_PROCSTAT_PSSTRINGS): Define.
	(NT_FREEBSD_PROCSTAT_AUXV): Define.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Add PIC and TLS support to the ARC target.
@ 2016-01-19 15:37 sergiodj+buildbot
  2016-01-19 16:35 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-01-19 15:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 34e967a5f3ac5fd0353731a259e358d462823290 ***

Author: Miranda Cupertino <Cupertino.Miranda@synopsys.com>
Branch: master
Commit: 34e967a5f3ac5fd0353731a259e358d462823290

Add PIC and TLS support to the ARC target.

bfd/ChangeLog:
	* arc-plt.def: New file.
	* arc-plt.h: Likewise.
	* elf32-arc.c (elf_arc_abs_plt0_entry, elf_arc_abs_pltn_entry,
		       elf_arcV2_abs_plt0_entry, elf_arcV2_abs_pltn_entry,
		       elf_arc_pic_plt0_entry, elf_arc_pic_pltn_entry,
		       elf_arcV2_pic_plt0_entry, elf_arcV2_pic_pltn_entry): Remove.
	(name_for_global_symbol): Added.
	(ADD_RELA): Helper to create dynamic relocs.
	(new_got_entry_to_list): Create a new got entry in linked list.
	(symbol_has_entry_of_type): Search for specific type of entry in
	list.
	(is_reloc_for_GOT): return FALSE for any TLS related relocs.
	(is_reloc_for_TLS, arc_elf_set_private_flags)
	(arc_elf_print_private_bfd_data, arc_elf_copy_private_bfd_data)
	(arc_elf_merge_private_bfd_data): New functions.
	(debug_arc_reloc): Cleaned debug info printing.
	(PDATA reloc): Changed not to perform address alignment.
	(reverse_me): Added. Fix for ARC_32 relocs.
	(arc_do_relocation): Return bfd_reloc_of when no relocation should
	occur.
	(arc_get_local_got_ents): Renamed from arc_get_local_got_offsets.
	Changed function to access an array of list of GOT entries instead
	of just an array of offsets.
	(elf_arc_relocate_section): Added support for PIC and TLS related relocations.
	(elf_arc_check_relocs): Likewise.
	(elf_arc_adjust_dynamic_symbol, elf_arc_finish_dynamic_symbol,
	(elf_arc_finish_dynamic_sections): Likewise
	(arc_create_dynamic_sections): Modified conditions to create
	dynamic sections.
	(ADD_SYMBOL_REF_SEC_AND_RELOC): New macro.
	(plt_do_relocs_for_symbol, relocate_plt_for_symbol)
	(relocate_plt_for_entry): Changed to support new way to define PLT
	related code.
	(add_symbol_to_plt): Likewise.
	(arc_elf_link_hash_table_create): New function.

include/ChangeLog:
	* elf/arc-reloc.def (ARC_32, ARC_GOTPC, ARC_TLS_GD_GOT)
	(ARC_TLS_IE_GOT, ARC_TLS_DTPOFF, ARC_TLS_DTPOFF_S9, ARC_TLS_LE_S9)
	(ARC_TLS_LE_32): Fixed formula.
	(ARC_TLS_GD_LD): Use new special function.
	* opcode/arc-func.h: Changed all the replacement
	functions to clear the patching bits before doing an or it with the value
	argument.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
[parent not found: <bd0a71fa16f668341a9361c695bc3ca44d27b322@gdb-build>]
* [binutils-gdb] Use a 32-bit value to hold the section number in the internal COFF symbol structure.
@ 2016-01-18 16:11 sergiodj+buildbot
  2016-01-18 20:23 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-01-18 16:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9ae678af999b8a692c4e6efbe493f39f0085d149 ***

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

Use a 32-bit value to hold the section number in the internal COFF symbol structure.

	PR ld/19440
inc	* coff/internal.h (internal_syment): Use int to hold section
	number.
	(N_UNDEF): Cast to int not short.
	(N_ABS): Likewise.
	(N_DEBUG): Likewise.
	(N_TV): Likewise.
	(P_TV): Likewise.

bfd	PR ld/19440
	* coff-rs6000.c (_bfd_xcoff_swap_sym_in): Sign extend external
	section number into internal section number.
	* coff64-rs6000.c (_bfd_xcoff64_swap_sym_in): Likewise.
	* coffswap.h (coff_swap_sym_in): Likewise.
	* peXXigen.c (_bfd_XXi_swap_sym_in): Likewise.
	* coffcode.h (_coff_bigobj_swap_sym_in): Make sure that internal
	section number field is big enough to hold the external value.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Fix PR threads/19422 - show which thread caused stop
@ 2016-01-18 16:03 sergiodj+buildbot
  2016-01-18 19:16 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-01-18 16:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f303dbd60d9c7984832446eeb9d4e4d89703c615 ***

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

Fix PR threads/19422 - show which thread caused stop

This commit changes GDB like this:

 - Program received signal SIGINT, Interrupt.
 + Thread 1 "main" received signal SIGINT, Interrupt.

 - Breakpoint 1 at 0x40087a: file threads.c, line 87.
 + Thread 3 "bar" hit Breakpoint 1 at 0x40087a: file threads.c, line 87.

 ... once the program goes multi-threaded.  Until GDB sees a second
thread spawn, the output is still the same as before, per the
discussion back in 2012:

  https://www.sourceware.org/ml/gdb/2012-11/msg00010.html

This helps non-stop mode, where you can't easily tell which thread hit
a breakpoint or received a signal:

 (gdb) info threads
   Id   Target Id         Frame
 * 1    Thread 0x7ffff7fc1740 (LWP 19362) "main" (running)
   2    Thread 0x7ffff7fc0700 (LWP 19366) "foo" (running)
   3    Thread 0x7ffff77bf700 (LWP 19367) "bar" (running)
 (gdb)
 Program received signal SIGUSR1, User defined signal 1.
 0x0000003616a09237 in pthread_join (threadid=140737353877248, thread_return=0x7fffffffd5b8) at pthread_join.c:92
 92          lll_wait_tid (pd->tid);
 (gdb) b threads.c:87
 Breakpoint 1 at 0x40087a: file threads.c, line 87.
 (gdb)
 Breakpoint 1, thread_function1 (arg=0x1) at threads.c:87
 87              usleep (1);  /* Loop increment.  */

The best the user can do is run "info threads" and try to figure
things out.

It actually also affects all-stop mode, in case of "handle SIG print
nostop":

...
  Program received signal SIGUSR1, User defined signal 1.

  Program received signal SIGUSR1, User defined signal 1.

  Program received signal SIGUSR1, User defined signal 1.

  Program received signal SIGUSR1, User defined signal 1.
...

The above doesn't give any clue that these were different threads
getting the SIGUSR1 signal.

I initially thought of lowercasing "breakpoint" in

  "Thread 3 hit Breakpoint 1"

but then after trying it I realized that leaving "Breakpoint"
uppercase helps the eye quickly find the relevant information.  It's
also easier to implement not showing anything about threads until the
program goes multi-threaded this way.

Here's a larger example session in non-stop mode:

  (gdb) c -a&
  Continuing.
  (gdb) interrupt -a
  (gdb)
  Thread 1 "main" stopped.
  0x0000003616a09237 in pthread_join (threadid=140737353877248, thread_return=0x7fffffffd5b8) at pthread_join.c:92
  92          lll_wait_tid (pd->tid);

  Thread 2 "foo" stopped.
  0x0000003615ebc6ed in nanosleep () at ../sysdeps/unix/syscall-template.S:81
  81      T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)

  Thread 3 "bar" stopped.
  0x0000003615ebc6ed in nanosleep () at ../sysdeps/unix/syscall-template.S:81
  81      T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
  b threads.c:87
  Breakpoint 4 at 0x40087a: file threads.c, line 87.
  (gdb) b threads.c:67
  Breakpoint 5 at 0x400811: file threads.c, line 67.
  (gdb) c -a&
  Continuing.
  (gdb)
  Thread 3 "bar" hit Breakpoint 4, thread_function1 (arg=0x1) at threads.c:87
  87              usleep (1);  /* Loop increment.  */

  Thread 2 "foo" hit Breakpoint 5, thread_function0 (arg=0x0) at threads.c:68
  68              (*myp) ++;
  info threads
    Id   Target Id         Frame
  * 1  Thread 0x7ffff7fc1740 (LWP 31957) "main" (running)
    2  Thread 0x7ffff7fc0700 (LWP 31961) "foo" thread_function0 (arg=0x0) at threads.c:68
    3  Thread 0x7ffff77bf700 (LWP 31962) "bar" thread_function1 (arg=0x1) at threads.c:87
  (gdb) shell kill -SIGINT 31957
  (gdb)
  Thread 1 "main" received signal SIGINT, Interrupt.
  0x0000003616a09237 in pthread_join (threadid=140737353877248, thread_return=0x7fffffffd5b8) at pthread_join.c:92
  92          lll_wait_tid (pd->tid);
  info threads
    Id   Target Id         Frame
  * 1  Thread 0x7ffff7fc1740 (LWP 31957) "main" 0x0000003616a09237 in pthread_join (threadid=140737353877248, thread_return=0x7fffffffd5b8) at pthread_join.c:92
    2  Thread 0x7ffff7fc0700 (LWP 31961) "foo" thread_function0 (arg=0x0) at threads.c:68
    3  Thread 0x7ffff77bf700 (LWP 31962) "bar" thread_function1 (arg=0x1) at threads.c:87
  (gdb) t 2
  [Switching to thread 2, Thread 0x7ffff7fc0700 (LWP 31961)]
  #0  thread_function0 (arg=0x0) at threads.c:68
  68              (*myp) ++;
  (gdb) catch syscall
  Catchpoint 6 (any syscall)
  (gdb) c&
  Continuing.
  (gdb)
  Thread 2 "foo" hit Catchpoint 6 (call to syscall nanosleep), 0x0000003615ebc6ed in nanosleep () at ../sysdeps/unix/syscall-template.S:81
  81      T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)

I'll work on documentation next if this looks agreeable.

This patch applies on top of the star wildcards thread IDs series:

  https://sourceware.org/ml/gdb-patches/2016-01/msg00291.html

For convenience, I've pushed this to the
users/palves/show-which-thread-caused-stop branch.

gdb/doc/ChangeLog:
2016-01-18  Pedro Alves  <palves@redhat.com>

	* gdb.texinfo (Threads): Mention that GDB displays the ID and name
	of the thread that hit a breakpoint or received a signal.

gdb/ChangeLog:
2016-01-18  Pedro Alves  <palves@redhat.com>

	* NEWS: Mention that GDB now displays the ID and name of the
	thread that hit a breakpoint or received a signal.
	* break-catch-sig.c (signal_catchpoint_print_it): Use
	maybe_print_thread_hit_breakpoint.
	* break-catch-syscall.c (print_it_catch_syscall): Likewise.
	* break-catch-throw.c (print_it_exception_catchpoint): Likewise.
	* breakpoint.c (maybe_print_thread_hit_breakpoint): New function.
	(print_it_catch_fork, print_it_catch_vfork, print_it_catch_solib)
	(print_it_catch_exec, print_it_ranged_breakpoint)
	(print_it_watchpoint, print_it_masked_watchpoint, bkpt_print_it):
	Use maybe_print_thread_hit_breakpoint.
	* breakpoint.h (maybe_print_thread_hit_breakpoint): Declare.
	* gdbthread.h (show_thread_that_caused_stop): Declare.
	* infrun.c (print_signal_received_reason): Print which thread
	received signal.
	* thread.c (show_thread_that_caused_stop): New function.

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

	* gdb.base/async-shell.exp: Adjust expected output.
	* gdb.base/dprintf-non-stop.exp: Adjust expected output.
	* gdb.base/siginfo-thread.exp: Adjust expected output.
	* gdb.base/watchpoint-hw-hit-once.exp: Adjust expected output.
	* gdb.java/jnpe.exp: Adjust expected output.
	* gdb.threads/clone-new-thread-event.exp: Adjust expected output.
	* gdb.threads/continue-pending-status.exp: Adjust expected output.
	* gdb.threads/leader-exit.exp: Adjust expected output.
	* gdb.threads/manythreads.exp: Adjust expected output.
	* gdb.threads/pthreads.exp: Adjust expected output.
	* gdb.threads/schedlock.exp: Adjust expected output.
	* gdb.threads/siginfo-threads.exp: Adjust expected output.
	* gdb.threads/signal-command-multiple-signals-pending.exp: Adjust
	expected output.
	* gdb.threads/signal-delivered-right-thread.exp: Adjust expected
	output.
	* gdb.threads/sigthread.exp: Adjust expected output.
	* gdb.threads/watchpoint-fork.exp: Adjust expected output.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Replace some $ARCH_{get, set}_pc with linux_{get, set}_pc_64bit
@ 2016-01-18 15:19 sergiodj+buildbot
  2016-01-18 17:55 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-01-18 15:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6f69e520676f5f434cf43c250865036b3d516429 ***

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

Replace some $ARCH_{get,set}_pc with linux_{get,set}_pc_64bit

This patch is the follow-up of
https://sourceware.org/ml/gdb-patches/2016-01/msg00164.html to provide
linux_{get,set}_pc_64bit functions.

Rebuild GDBserver with tilegx-linux-gcc.  Not tested.

I think about pc in Tile-GX a little bit.  Looks current Tile-GX
supports debugging 32-bit program (multi-arch), but PC is always
64-bit.  See this thread
https://sourceware.org/ml/gdb-patches/2013-02/msg00113.html
and GDBserver reads PC as 64-bit through ptrace.  However, if
the inferior is 32-bit, the PC in the target description and
regcache is 32-bit, so only 32-bit contents are sent back GDB.
Anyway, Tile-GX GDBserver may have some problems here, but this
patch doesn't change anything.

gdb/gdbserver:

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

	* linux-low.c (linux_set_pc_64bit): New function.
	(linux_get_pc_64bit): New function.
	* linux-low.h (linux_set_pc_64bit, linux_get_pc_64bit):
	Declare.
	* linux-sparc-low.c (debug_threads): Remove declaration.
	(sparc_get_pc): Remove.
	(the_low_target): Use linux_get_pc_64bit instead of
	sparc_get_pc.
	* linux-tile-low.c (tile_get_pc, tile_set_pc): Remove.
	(the_low_target): Use linux_get_pc_64bit and
	linux_set_pc_64bit.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Fix gdbserver build failure on targets without fork
@ 2016-01-18 11:57 sergiodj+buildbot
  2016-01-18 12:54 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-01-18 11:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT eb0edac83f82516bbbd5a0412bbdf7fd27c687f2 ***

Author: Gary Benson <gbenson@redhat.com>
Branch: master
Commit: eb0edac83f82516bbbd5a0412bbdf7fd27c687f2

Fix gdbserver build failure on targets without fork

This commit fixes nat/linux-namespaces.c to build correctly on
targets without fork.

gdb/ChangeLog:

	* nat/linux-namespaces.c (do_fork): New function.
	(linux_mntns_get_helper): Use the above.

gdb/gdbserver/ChangeLog:

	* configure.ac (AC_FUNC_FORK): New check.
	* config.in: Regenerate.
	* configure: Likewise.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] MAINTAINERS: Add Andreas Arnez as s390 target maintainer.
@ 2016-01-13 18:04 sergiodj+buildbot
  2016-01-13 21:41 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-01-13 18:04 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bc06e0b148dfc4f2e52003a17d48463150f72e7b ***

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

MAINTAINERS: Add Andreas Arnez as s390 target maintainer.

gdb/ChangeLog:

	* MAINTAINERS: Add Andreas Arnez as s390 target maintainer.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Implement "info threads -gid"
@ 2016-01-13 11:41 sergiodj+buildbot
  2016-01-13 18:12 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-01-13 11:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c84f6bbfe50ff13928360d3cc349d7c553867ce6 ***

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

Implement "info threads -gid"

This commit makes global thread IDs optionaly visible in "info
threads", with the new "-gid" switch:

 (gdb) info threads -gid
   Id   GId  Target Id         Frame
   1.1  1    Thread 0x7ffff7fc2740 (LWP 6022) "threads" (running)
   1.2  3    Thread 0x7ffff77c0700 (LWP 6028) "threads" (running)
   1.3  4    Thread 0x7ffff7fc2740 (LWP 6032) "threads" (running)
   2.1  2    Thread 0x7ffff7fc1700 (LWP 6037) "threads" (running)
   2.2  5    Thread 0x7ffff77c0700 (LWP 6038) "threads" (running)
 * 2.3  6    Thread 0x7ffff7fc2740 (LWP 6039) "threads" (running)

 (gdb) info threads
   Id   Target Id         Frame
   1.1  Thread 0x7ffff7fc2740 (LWP 6022) "threads" (running)
   1.2  Thread 0x7ffff77c0700 (LWP 6028) "threads" (running)
   1.3  Thread 0x7ffff7fc2740 (LWP 6032) "threads" (running)
   2.1  Thread 0x7ffff7fc1700 (LWP 6037) "threads" (running)
   2.2  Thread 0x7ffff77c0700 (LWP 6038) "threads" (running)
 * 2.3  Thread 0x7ffff7fc2740 (LWP 6039) "threads" (running)

No regressions on x86_64 Fedora 20.

gdb/ChangeLog:
2016-01-13  Pedro Alves  <palves@redhat.com>

	* NEWS: Mention "info threads -gid".
	* gdbthread.h (struct thread_info) <global_num>: Mention "info
	threads -gid".
	* thread.c (info_threads_command): Handle "-gid".
	(_initialize_thread): Adjust "info threads" help string to mention
	-gid.

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

	* gdb.multi/tids.exp: Test "info threads -gid".

gdb/doc/ChangeLog:
2016-01-13  Pedro Alves  <palves@redhat.com>

	* gdb.texinfo (Threads): Document "info threads -gid".


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Centralize thread ID printing
@ 2016-01-13 11:38 sergiodj+buildbot
  2016-01-13 15:04 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-01-13 11:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 43792cf0de3a49fb871d432343672bdf16270e99 ***

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

Centralize thread ID printing

Add a new function to print a thread ID, in the style of paddress,
plongest, etc. and adjust all CLI-reachable paths to use it.

This gives us a single place to tweak to print inferior-qualified
thread IDs later:

 - [Switching to thread 1 (Thread 0x7ffff7fc2740 (LWP 8155))]
 + [Switching to thread 1.1 (Thread 0x7ffff7fc2740 (LWP 8155))]

etc., though for now, this has no user-visible change.

No regressions on x86_64 Fedora 20.

gdb/ChangeLog:
2016-01-13  Pedro Alves  <palves@redhat.com>

	* breakpoint.c (remove_threaded_breakpoints)
	(print_one_breakpoint_location): Use print_thread_id.
	* btrace.c (btrace_enable, btrace_disable, btrace_teardown)
	(btrace_fetch, btrace_clear): Use print_thread_id.
	* common/print-utils.c (CELLSIZE): Delete.
	(get_cell): Rename to ...
	(get_print_cell): ... this and made extern.  Adjust call callers.
	Adjust to use PRINT_CELL_SIZE.
	* common/print-utils.h (get_print_cell): Declare.
	(PRINT_CELL_SIZE): New.
	* gdbthread.h (print_thread_id): Declare.
	* infcmd.c (signal_command): Use print_thread_id.
	* inferior.c (print_inferior): Use print_thread_id.
	* infrun.c (handle_signal_stop)
	(insert_exception_resume_breakpoint)
	(insert_exception_resume_from_probe)
	(print_signal_received_reason): Use print_thread_id.
	* record-btrace.c (record_btrace_info)
	(record_btrace_resume_thread, record_btrace_cancel_resume)
	(record_btrace_step_thread, record_btrace_wait): Use
	print_thread_id.
	* thread.c (thread_apply_all_command): Use print_thread_id.
	(print_thread_id): New function.
	(thread_apply_command): Use print_thread_id.
	(thread_command, thread_find_command, do_captured_thread_select):
	Use print_thread_id.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Implement 'catch syscall' for gdbserver
@ 2016-01-12 20:34 sergiodj+buildbot
  2016-01-13  3:38 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-01-12 20:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 82075af2c14b1f8a54fa5796fb63f7ef23f98d9d ***

Author: Josh Stone <jistone@redhat.com>
Branch: master
Commit: 82075af2c14b1f8a54fa5796fb63f7ef23f98d9d

Implement 'catch syscall' for gdbserver

This adds a new QCatchSyscalls packet to enable 'catch syscall', and new
stop reasons "syscall_entry" and "syscall_return" for those events.  It
is currently only supported on Linux x86 and x86_64.

gdb/ChangeLog:

2016-01-12  Josh Stone  <jistone@redhat.com>
	    Philippe Waroquiers  <philippe.waroquiers@skynet.be>

	* NEWS (Changes since GDB 7.10): Mention QCatchSyscalls and the
	syscall_entry and syscall_return stop reasons.  Mention GDB
	support for remote catch syscall.
	* remote.c (PACKET_QCatchSyscalls): New enum.
	(remote_set_syscall_catchpoint): New function.
	(remote_protocol_features): New element for QCatchSyscalls.
	(remote_parse_stop_reply): Parse syscall_entry/return stops.
	(init_remote_ops): Install remote_set_syscall_catchpoint.
	(_initialize_remote): Config QCatchSyscalls.
	* linux-nat.h (struct lwp_info) <syscall_state>: Comment typo.

gdb/doc/ChangeLog:

2016-01-12  Josh Stone  <jistone@redhat.com>
	    Philippe Waroquiers  <philippe.waroquiers@skynet.be>

	* gdb.texinfo (Remote Configuration): List the QCatchSyscalls packet.
	(Stop Reply Packets): List the syscall entry and return stop reasons.
	(General Query Packets): Describe QCatchSyscalls, and add it to the
	table and the detailed list of stub features.

gdb/gdbserver/ChangeLog:

2016-01-12  Josh Stone  <jistone@redhat.com>
	    Philippe Waroquiers  <philippe.waroquiers@skynet.be>

	* inferiors.h: Include "gdb_vecs.h".
	(struct process_info): Add syscalls_to_catch.
	* inferiors.c (remove_process): Free syscalls_to_catch.
	* remote-utils.c (prepare_resume_reply): Report syscall_entry and
	syscall_return stops.
	* server.h (UNKNOWN_SYSCALL, ANY_SYSCALL): Define.
	* server.c (handle_general_set): Handle QCatchSyscalls.
	(handle_query): Report support for QCatchSyscalls.
	* target.h (struct target_ops): Add supports_catch_syscall.
	(target_supports_catch_syscall): New macro.
	* linux-low.h (struct linux_target_ops): Add get_syscall_trapinfo.
	(struct lwp_info): Add syscall_state.
	* linux-low.c (handle_extended_wait): Mark syscall_state as an entry.
	Maintain syscall_state and syscalls_to_catch across exec.
	(get_syscall_trapinfo): New function, proxy to the_low_target.
	(linux_low_ptrace_options): Enable PTRACE_O_TRACESYSGOOD.
	(linux_low_filter_event): Toggle syscall_state entry/return for
	syscall traps, and set it ignored for all others.
	(gdb_catching_syscalls_p): New function.
	(gdb_catch_this_syscall_p): New function.
	(linux_wait_1): Handle SYSCALL_SIGTRAP.
	(linux_resume_one_lwp_throw): Add PTRACE_SYSCALL possibility.
	(linux_supports_catch_syscall): New function.
	(linux_target_ops): Install it.
	* linux-x86-low.c (x86_get_syscall_trapinfo): New function.
	(the_low_target): Install it.

gdb/testsuite/ChangeLog:

2016-01-12  Josh Stone  <jistone@redhat.com>
	    Philippe Waroquiers  <philippe.waroquiers@skynet.be>

	* gdb.base/catch-syscall.c (do_execve): New variable.
	(main): Conditionally trigger an execve.
	* gdb.base/catch-syscall.exp: Enable testing for remote targets.
	(test_catch_syscall_execve): New, check entry/return across execve.
	(do_syscall_tests): Call test_catch_syscall_execve.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Sync top-level btool.m4 with GCC
@ 2016-01-12 16:49 sergiodj+buildbot
  2016-01-13  2:27 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-01-12 16:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1985dc2d048a4134f20dc9cda61255eb33289476 ***

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

Sync top-level btool.m4 with GCC

	Sync with GCC
	2015-11-26  David Edelsohn  <dje.gcc@gmail.com>

	* m4/libtool.m4 (export_symbols_cmds) [AIX]: Add global TLS "L"
	symbols.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [ARM] Support ARMv8.2 RAS extension.
@ 2016-01-12 16:46 sergiodj+buildbot
  2016-01-13  0:01 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-01-12 16:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 105bde5771c1c1b26b69e3623c88f3caafa3a480 ***

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

[ARM] Support ARMv8.2 RAS extension.

The ARMv8.2 architecture includes the RAS extension which adds an
instruction, ESB, and a number of coprocessor registers. This patch adds
the instruction to binutils, making it available when -march=armv8.2-a
is selected. It also adds tests for the instruction and for the
coprocessor registers.

gas/
2016-01-12  Matthew Wahab  <matthew.wahab@arm.com>

	* config/tc-arm.c (arm_ext_v8_2): New.
	(insns): Add "esb".
	* testsuite/gas/arm/armv8_2-a.d: New.
	* testsuite/gas/arm/armv8_2-a.s: New.

opcodes/
2016-01-12  Matthew Wahab  <matthew.wahab@arm.com>

	* arm-dis.c (arm_opcodes): Add "esb".
	(thumb_opcodes): Likewise.

Change-Id: I67f3d70789db78d1c66a56c4994675f99ac15e34


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Add cantunwind when unwind info does not match start of section.
@ 2016-01-12 16:41 sergiodj+buildbot
  2016-01-12 22:54 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-01-12 16:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ac06903dcff237777c8d507a03aafd79c84129ae ***

Author: Yury Usishchev <y.usishchev@samsung.com>
Branch: master
Commit: ac06903dcff237777c8d507a03aafd79c84129ae

Add cantunwind when unwind info does not match start of section.

bfd     * elf32-arm.c (elf32_arm_fix_exidx_coverage): Insert cantunwind when
        address in first unwind entry does not match start of section.

tests   * ld-arm/arm-elf.exp: New test.
        * ld-arm/unwind-mix.d: New file.
        * ld-arm/unwind-mix1.s: New file.
        * ld-arm/unwind-mix2.s: New file.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] gdbserver: use the new gdb warning helpers
@ 2016-01-12 15:45 sergiodj+buildbot
  2016-01-12 19:18 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-01-12 15:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8f13a3ce8afc1144169a14c7704689e263316e70 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 8f13a3ce8afc1144169a14c7704689e263316e70

gdbserver: use the new gdb warning helpers

We need to use -Wno-missing-prototypes for now as much of the code
sticks externs in local files and not in common headers.

2016-01-11  Mike Frysinger  <vapier@gentoo.org>

	* acinclude.m4: Include new ../warning.m4 file.
	* configure: Regenerated.
	* configure.ac: Replace all warning logic with AM_GDB_WARNINGS.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] sim: mips: workaround 32-bit addr sign extensions
@ 2016-01-12  6:46 sergiodj+buildbot
  2016-01-12  8:08 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-01-12  6:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b36d953bced0a4fecdde1823abac70ed7038ee95 ***

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

sim: mips: workaround 32-bit addr sign extensions

The mips bfd will sign extend 32-bit addresses into 64-bit values,
so if the entry happens to be 0x80000000 or higher, it is turned to
0xffffffff80000000 which points to memory that doesn't exist.

This wasn't an issue until commit 26f8bf63bf36f9062a5cc1afacf71462a
as all addresses were automatically truncated there in the translate
function to 32-bits.  When we cleaned up that code, the full 64-bits
were checked leading to many test failures for mips-sde-elf targets
and such.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] testsuite: Fix false FAILs on too long base directory
@ 2016-01-11 21:16 sergiodj+buildbot
  2016-01-11 22:32 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-01-11 21:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c0ecb95f3dc0c3e8d1545f0a37c0c3e537e1ea96 ***

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

testsuite: Fix false FAILs on too long base directory

I was getting

gu (print arg0)^M
= 0x7fffffffdafb
"/unsafebuild-x86_64-redhat-linux-gnu/gdb/testsuite.unix.-m64/outputs/gdb.guile/scm-value/scm-"...^M
(gdb) FAIL: gdb.guile/scm-value.exp: verify dereferenced value
python print (arg0)^M
0x7fffffffdafd
"/unsafebuild-x86_64-redhat-linux-gnu/gdb/testsuite.unix.-m64/outputs/gdb.python/py-value/py-v"...^M
(gdb) FAIL: gdb.python/py-value.exp: verify dereferenced value

and also:

(gdb) p argv[0]^M
$2 = 0x7fffffffd832 "/home/jkratoch/redhat/gdb-test-", 'x' <repeats 169
times>...^M
(gdb) FAIL: gdb.guile/scm-value.exp: argv[0] should be available on this
target

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

	* gdb.guile/scm-value.exp (test_value_in_inferior): Set print elements
	and repeats to unlimited.
	* gdb.python/py-value.exp: Likewise.
	* lib/gdb.exp (gdb_has_argv0): Save and temporarily set print elements
	and repeats to unlimited.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] sim: move many common settings from CPPFLAGS to config.h
@ 2016-01-11  0:08 sergiodj+buildbot
  2016-01-11  6:04 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-01-11  0:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ce39bd389039d99458950b072550ab52f0a07a34 ***

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

sim: move many common settings from CPPFLAGS to config.h

Rather than stuffing the command line with a bunch of -D flags, start
moving things to config.h which is managed by autoheader.  This makes
the makefile a bit simpler and the build output tighter, and it makes
the migration to automake easier as there are fewer vars to juggle.

We'll want to move the other options out too, but it'll take more work.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] sim: allow the assert configure option everywhere
@ 2016-01-10 22:20 sergiodj+buildbot
  2016-01-10 23:19 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-01-10 22:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 35656e95217a20309c0a0f16bf0c89a49a549177 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 35656e95217a20309c0a0f16bf0c89a49a549177

sim: allow the assert configure option everywhere

Currently ports have to call SIM_AC_OPTION_ASSERT explicitly in order
to make the configure flag available, which none of them do.  There's
no real reason to not allow this flag for all ports, so move it to the
common sim macro.  This way we get standard behavior across all ports.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] sim: drop common/cconfig.h in favor of a single config.h
@ 2016-01-09  9:01 sergiodj+buildbot
  2016-01-09  9:56 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-01-09  9:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 936df7568a0e47547285a0dd57b81643264fef38 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 936df7568a0e47547285a0dd57b81643264fef38

sim: drop common/cconfig.h in favor of a single config.h

The common subdir sets up a cconfig.h file to hold checks for the common
code.  In practice, most files still end up using config.h instead which
just leads to confusion.

Merge all the configure checks that went into cconfig.h into SIM_AC_COMMON
so we can drop the cconfig.h file altogether.  Now there is only a single
config.h file like normal.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Fix gdb.multi/base.exp testsuite regression
@ 2016-01-08 19:16 sergiodj+buildbot
  2016-01-08 20:10 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-01-08 19:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6cfc1fcb515d1ecd8445905b4749b81b3ca69552 ***

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

Fix gdb.multi/base.exp testsuite regression

Regressed by:

commit 762f774785f4ef878ac4c831e1f4733dc957234d
Author: Pedro Alves <palves@redhat.com>
Date:   Thu Dec 10 16:21:06 2015 +0000
    Stop using nowarnings in gdb/testsuite/gdb.multi/

+gdb compile failed, gdb/testsuite/gdb.multi/hello.c: In function 'commonfun':
+gdb/testsuite/gdb.multi/hello.c:24:19: warning: implicit declaration of function 'bar' [-Wimplicit-function-declaration]
+ int commonfun() { bar(); } /* from hello */
+                   ^
+gdb/testsuite/gdb.multi/hello.c: At top level:
+gdb/testsuite/gdb.multi/hello.c:26:1: warning: return type defaults to 'int' [-Wimplicit-int]
+ bar()
+ ^
+gdb/testsuite/gdb.multi/hello.c:32:1: warning: return type defaults to 'int' [-Wimplicit-int]
+ hello(int x)
+ ^
+gdb/testsuite/gdb.multi/hello.c:38:1: warning: return type defaults to 'int' [-Wimplicit-int]
+ main()
+ ^
+UNTESTED: gdb.multi/base.exp: base.exp

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

	* gdb.multi/goodbye.c: Fix compilation warnings by adding return types
	and reordering the functions.
	* gdb.multi/hangout.c: Likewise.
	* gdb.multi/hello.c: Likewise.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [ARM] PR ld/19368: Add missing relocation type class for R_ARM_IRELATIVE
@ 2016-01-08  9:58 sergiodj+buildbot
  2016-01-08 10:52 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-01-08  9:58 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 109575d7ebac21a0eb67980001ecd4173d696f88 ***

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

[ARM] PR ld/19368: Add missing relocation type class for R_ARM_IRELATIVE

2016-01-08  Richard Sandiford  <richard.sandiford@arm.com>
	    Jiong Wang  <jiong.wang@arm.com>

	PR ld/19368
	bfd/
	* elf32-arm.c (elf32_arm_reloc_type_class): Map R_ARM_IRELATIVE to
	reloc_class_ifunc.

	ld/
	* testsuite/ld-arm/ifunc-3.rd: Update expected result.
	* testsuite/ld-arm/ifunc-4.rd: Likewise.
	* testsuite/ld-arm/ifunc-9.rd: Likewise.
	* testsuite/ld-arm/ifunc-10.rd: Likewise.
	* testsuite/ld-arm/ifunc-12.rd: Likewise.
	* testsuite/ld-arm/ifunc-13.rd: Likewise.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] MIPS/include: opcode/mips.h: Add a summary of MIPS16 operand codes
@ 2016-01-06 18:52 sergiodj+buildbot
  2016-01-06 19:48 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-01-06 18:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b31e4803316aa0635a6f9beaeceea3e18dbbe459 ***

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

MIPS/include: opcode/mips.h: Add a summary of MIPS16 operand codes

	include/
	* opcode/mips.h: Add a summary of MIPS16 operand codes.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Make {arm,thumb}_get_next_pcs_raw static
@ 2016-01-06 15:34 sergiodj+buildbot
  2016-01-06 17:49 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-01-06 15:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f5aa306929127aacf9890a949f9a21b38a0e0e7e ***

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

Make {arm,thumb}_get_next_pcs_raw static

This patch makes arm_get_next_pcs_raw and thumb_get_next_pcs_raw
static.

gdb:

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

	* arch/arm-get-next-pcs.c (arm_get_next_pcs): Move it to some
	lines below.
	(thumb_get_next_pcs_raw): Make it static.
	(arm_get_next_pcs_raw): Likewise.
	* arch/arm-get-next-pcs.h (thumb_get_next_pcs_raw): Remove the
	declaration.
	(arm_get_next_pcs_raw): Likewise.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] libiberty: {count, dup, write}argv: constify argv input slightly
@ 2016-01-05 23:03 sergiodj+buildbot
  2016-01-06  4:04 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-01-05 23:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b36c1ccb1feb678f7279b4a8d66c0125d4295078 ***

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

libiberty: {count,dup,write}argv: constify argv input slightly

Would be more useful if we could use "const char * const *", but there's
a long standing bug where gcc warns about incompatible pointers when you
try to pass in "char **".  We can at least constify the array itself as
gcc will not warn in that case.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] libiberty: Tweak the documentation of libiberty's xcrc32 function
@ 2016-01-05 22:29 sergiodj+buildbot
  2016-01-06  2:01 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-01-05 22:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4bec0ef03e91506caf60d8842786b29c2d2ff049 ***

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

libiberty: Tweak the documentation of libiberty's xcrc32 function

In some places the xcrc32 documentation refers to GDB's own crc32
implementation, but GDB no longer has its own crc32 implementation.
It now uses libiberty's xcrc32 throughout.  So this patch removes
these references to GDB's now-nonexistent crc32 implementation.

Also, there appears to be a bug in the table-generation program embedded
within the documentation.  When the variable "int i" is >= 128, the
computation "i << 24" shifts a one bit into the sign bit (assuming a
32-bit int), which is UB.  To avoid this UB, I think it is sufficient to
make the induction variables i and j have type unsigned int.  This bug
seems latent, however.  I ran the program before and after this change
and the table output is the same.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] sim: parse_args: polish getopt error message
@ 2016-01-04 11:04 sergiodj+buildbot
  2016-01-04 13:15 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-01-04 11:04 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8d7d784e23b5b2f8c7e28ece1bdb73b58199f16f ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 8d7d784e23b5b2f8c7e28ece1bdb73b58199f16f

sim: parse_args: polish getopt error message

The cris sim hit a few failures after the recent getopt logic, and the
expected output showed a few ways we can improve things to better match
other utils.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] sim: parse_args: display getopt error ourselves
@ 2016-01-04  3:17 sergiodj+buildbot
  2016-01-04  5:05 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-01-04  3:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 77cf2ef5dc9099501529151921a73be904757466 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 77cf2ef5dc9099501529151921a73be904757466

sim: parse_args: display getopt error ourselves

Fix a long standing todo where we let getopt write directly to stderr
when an invalid option is passed.  Use the sim io funcs instead as they
go through the filtered callbacks that gdb wants.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] sim: use libiberty countargv in more places
@ 2016-01-03  9:29 sergiodj+buildbot
  2016-01-03 11:12 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-01-03  9:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 34fed69938f1296b62354b2a825b49602fe7af50 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 34fed69938f1296b62354b2a825b49602fe7af50

sim: use libiberty countargv in more places

A bunch of places open code the countargv implementation, or outright
duplicate it (as count_argc).  Replace all of those w/countargv.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] sim: nrun: use lbasename
@ 2016-01-03  9:17 sergiodj+buildbot
  2016-01-03 10:10 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-01-03  9:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT aba6f46b235a3a139c04d5ed6a3310125aa9c982 ***

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

sim: nrun: use lbasename


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] sim: ppc: do not exit when parsing args w/gdb
@ 2016-01-02  8:50 sergiodj+buildbot
  2016-01-02  9:44 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2016-01-02  8:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT dea827fc5c3349dc0308d0e22ab2d6791282cf8b ***

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

sim: ppc: do not exit when parsing args w/gdb

When connecting to the simulator in gdb, we don't want it to exit on
us when we pass down unknown/invalid/help/etc... options.  Plumb down
the kind argument so we can handle both gdb & psim interfaces.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] opcodes/arc: Support dmb instruction with no operands
@ 2015-12-31 22:08 sergiodj+buildbot
  2015-12-31 23:21 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-12-31 22:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5ba8bc973cca60cb06bf41a2808ba6fa4ed02879 ***

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

opcodes/arc: Support dmb instruction with no operands

In this GCC commit:
  https://gcc.gnu.org/ml/gcc-patches/2015-12/msg00735.html
GCC started emitting dmb instructions with no operands.  The intention
was that dmb with no operands should be an alias for 'dmb 0'.

The following patch extends the arc opcodes library to support dmb with
no operands.

opcodes/ChangeLog:

	* arc-tbl.h (dmb): Add a no operand version of dmb.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] sim: cris/m68hc11: move default endian/alignment to configure
@ 2015-12-31  2:11 sergiodj+buildbot
  2015-12-31  3:20 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-12-31  2:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT eca4255a1a6c3603e05c4f3ca9c0849f529657c3 ***

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

sim: cris/m68hc11: move default endian/alignment to configure


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] sim: h8300: simplify h8300_reg_{fetch,store} funcs
@ 2015-12-30 11:14 sergiodj+buildbot
  2015-12-30 16:29 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-12-30 11:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2a2757ac7e849aa35fc519ddfcc8688a46b60448 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 2a2757ac7e849aa35fc519ddfcc8688a46b60448

sim: h8300: simplify h8300_reg_{fetch,store} funcs

We can leverage the cpu->regs array rather than going through the
function helpers to get nice compact code.

Further, fix up the return values: return -1 when we can't find a
register (and let the caller write out warnings), return 2/4 when
we actually write out that amount, and handle the zero reg.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] sim: arm/d10v/h8300/m68hc11/microblaze/mips/mn10300/moxie/sh/v850: convert to common sim_{fetch, store}_register
@ 2015-12-30  8:57 sergiodj+buildbot
  2015-12-30 11:38 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-12-30  8:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e1211e55062594679697d2175b7ea77dad173823 ***

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

sim: arm/d10v/h8300/m68hc11/microblaze/mips/mn10300/moxie/sh/v850: convert to common sim_{fetch,store}_register


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] sim: ppc: track closed state of file descriptors 0, 1, and 2.
@ 2015-12-30  0:30 sergiodj+buildbot
  2015-12-30  8:41 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-12-30  0:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 90d99f327063af7d87c61234896d4a1dbe073a43 ***

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

sim: ppc: track closed state of file descriptors 0, 1, and 2.

This change tracks the "closed" state of file descriptors 0, 1, and 2,
introducing the function fdbad() to emul_netbsd.c and emul_unix.c.
Note that a function of the same name and purpose exists in
sim/common/callback.c.

This patch eliminates all of the "unresolved testcases" when testing
GDB against the powerpc simulator.

This occurs because the powerpc simulator closes, on behalf of the
testcase, the file descriptors associated with stdin, stdout, and
stderr.  GDB still needs these descriptors to communicate with the
user or, in this case, with the testing framework.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Correct nios2 _gp address computation.
@ 2015-12-27 20:41 sergiodj+buildbot
  2015-12-27 21:51 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-12-27 20:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a7be2893a6449e64fe6cfcdd8700b0a367a69f19 ***

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

Correct nios2 _gp address computation.

2015-12-27  Sandra Loosemore  <sandra@codesourcery.com>

	bfd/
	* elf32-nios2.c (nios2_elf_assign_gp): Correct computation of _gp
	address.
	(nios2_elf32_relocate_section): Tidy code for R_NIOS2_GPREL error
	messages.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] sim: frv: punt WITH_DEVICE support
@ 2015-12-25 18:35 sergiodj+buildbot
  2015-12-26 17:12 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-12-25 18:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2023145711ca36f06258e07f4fa1c490efbbf37e ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 2023145711ca36f06258e07f4fa1c490efbbf37e

sim: frv: punt WITH_DEVICE support

The frv port used the device logic to support a single cache address,
and the comments around that are "these were merely copied from a diff
port and are unused", plus the code to attach the memory is "#if 0".
Just punt it all.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] sim: cris: migrate from WITH_DEVICES to WITH_HW
@ 2015-12-25 12:14 sergiodj+buildbot
  2015-12-26 15:24 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-12-25 12:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 34cf511206839b0f2b76870bf2d487c2dbcdbc1f ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 34cf511206839b0f2b76870bf2d487c2dbcdbc1f

sim: cris: migrate from WITH_DEVICES to WITH_HW

The cris port was using the device framework to handle two addresses when
the --cris-900000xx flag was specified.  That can be implemented using the
newer hardware framework instead which allows us to drop the device logic
entirely, as well as delete the tconfig.h file.  Basically we create a new
cris_900000xx device model and move the read logic out of devices.c and
into that.  The rest of the devices logic was callback to the hardware
framework already.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] sim: cris: set up sane default path to rvdummy
@ 2015-12-25 11:20 sergiodj+buildbot
  2015-12-26 13:19 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-12-25 11:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d4a587a4ed828eaf3273b435e328120e73bbb2cc ***

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

sim: cris: set up sane default path to rvdummy

Much like we autodetect the path to the run program when there is none
set explicitly, do the same for the rvdummy program.  Otherwise the
default make check fails to execute the helper properly.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] sim: drop WITH_ENGINE define
@ 2015-12-25 10:01 sergiodj+buildbot
  2015-12-26 11:46 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-12-25 10:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cf59f47ebeccf4ea82b6c529c882644e4c445323 ***

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

sim: drop WITH_ENGINE define

We enable this everywhere already, and all new ports should use the
engine logic, so no point in making it an option to disable.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] sim: device_error: punt
@ 2015-12-25  7:29 sergiodj+buildbot
  2015-12-26  0:52 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-12-25  7:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 42a3af5688cd41550e2b517f676f03f2842e615b ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 42a3af5688cd41550e2b517f676f03f2842e615b

sim: device_error: punt

Only four targets implement this function, and three of them do nothing.
The 4th merely calls abort.  Since calls to this function are followed
by calls to sim_hw_abort or sim_io_error, this is largely useless.  In
the two places where we don't, replace the call with sim_engine_abort.
We want to kill off the WITH_DEVICES logic in favor of WITH_HW, so this
is a good first step.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] sim: always enable callback memory
@ 2015-12-25  5:41 sergiodj+buildbot
  2015-12-26  0:18 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-12-25  5:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9e8e7dd966670c80f3b71f8cf7e07f2843b33e80 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 9e8e7dd966670c80f3b71f8cf7e07f2843b33e80

sim: always enable callback memory

We enable WITH_CALLBACK_MEMORY everywhere and don't provide a way to
turn it off, and no target does so.  Make it unconditional for all
to keep things simple.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] sim: mips: move SIM_QUIET_NAN_NEGATED to sim-main.h
@ 2015-12-25  3:41 sergiodj+buildbot
  2015-12-25 20:45 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-12-25  3:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cb379ede3cf6cf367b2bb58b85d8ee849a82a9b0 ***

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

sim: mips: move SIM_QUIET_NAN_NEGATED to sim-main.h

We want to kill off tconfig.h, so move the one define mips still uses
to sim-main.h.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] sim: cris: move option install to sim_open
@ 2015-12-25  2:24 sergiodj+buildbot
  2015-12-25 18:45 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-12-25  2:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9db2b719087eb42cfb31018fe87657243f6185c9 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 9db2b719087eb42cfb31018fe87657243f6185c9

sim: cris: move option install to sim_open

We've moved custom option install for other targets to sim_open, so update
cris too.  It's the last one using MODULE_LIST, so we can drop that from
the common code too.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] sim: h8300: move h8300-specific options out of common code
@ 2015-12-25  1:50 sergiodj+buildbot
  2015-12-25 17:23 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-12-25  1:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bd3fb5b8fb33adb751407a128e1f2240dfb215d9 ***

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

sim: h8300: move h8300-specific options out of common code

Register the options in sim_open like other arches to avoid having to hack
up the common modules.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [testsuite/Ada] stop using project files when building test programs
@ 2015-12-24  5:38 sergiodj+buildbot
  2015-12-24  6:48 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-12-24  5:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ab8314b3d99625c9a2125d39f4f3e74bf9e49cce ***

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

[testsuite/Ada] stop using project files when building test programs

The current approach when building Ada programs for testing is
based on the use of a project file (testsuite/gdb.ada/gnat_ada.gpr).
To do that, we pass a number of additional arguments to target_compile,
one of them being the project file (via "-P/path/to/gnat_ada.gpr").
This used to work well-enough, but AdaCore is currently working towards
removing project-file support from gnatmake (the prefered tool for
using project files is gprbuild). So, we need to either switch
the compilation to gprbuild, or stop using project files.

First, using gprbuild is not always what users will be using to
build their applications. So having the option of using gnatmake
provides more flexibility towards exactly reproducing past bugs.
If we ever need a testcase that requires the use of gprbuild, then
I believe support for a new target needs to be added to dejagnu's
target_compile.

Also, the only real reason behind using a project file in the first
place is that we wanted to make it easy to specify the directory
where all compilation artifacts get stored. This is a consequence
of the organization choice we made for gdb.ada to keep each testcase
well organized. It is very easy to achieve that goal without using
project files.

This is therefore what this patch does: It change gdb_compile_ada
to build any program using gnatmake without using a project file
(by temporarily changing the current working directory).

There is a small (beneficial) side-effect; in the situation where
GDB is built in-tree, gnatmake is called as...

        % gnatmake [...] unit.adb

... which means that the debugging info in unit.o will say contain
a filename whose name is 'unit.adb', rather than '/path/to/unit.adb'.
This also better matches what users might typically do. But the side-
effect is that the unit name in the GDB output is not always a full
path. This patch tweaks a couple of testcases to make the path part
optional.

gdb/testsuite:

        * lib/ada.exp (target_compile_ada_from_dir): New function.
        (gdb_compile_ada): Reimplement avoiding the use of project files.
        * gdb.ada/gnat_ada.gpr: Delete.
        * gdb.ada/cond_lang.exp: Adjust test to make path before
        filename optional.
        * gdb.ada/small_reg_param.exp: Likewise.

Tested on x86_64-linux, with both in-tree and out-of-tree builds.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Remove HP-UX reference in foll-vfork.exp
@ 2015-12-22 16:10 sergiodj+buildbot
  2015-12-22 22:39 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-12-22 16:10 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fe33faff35a8ee19db823149e764e3373e603bb9 ***

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

Remove HP-UX reference in foll-vfork.exp

One more I just found.

Tested with native, native-gdbserver and native-extended-gdbserver on
Linux.

gdb/testsuite/ChangeLog:

	* gdb.base/foll-vork.exp: Remove HP-UX special case.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] ARM: Fix exidx coverage for relocatable builds.
@ 2015-12-22 16:03 sergiodj+buildbot
  2015-12-22 20:59 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-12-22 16:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 491d01d3da18fb61fa6c7c61c091b4cb8c5773f7 ***

Author: Yury Usishchev <y.usishchev@samsung.com>
Branch: master
Commit: 491d01d3da18fb61fa6c7c61c091b4cb8c5773f7

ARM: Fix exidx coverage for relocatable builds.

bfd  * elf-bfd.h: Add callback to count additional relocations.
     * elf32-arm.c (_arm_elf_section_data): Add new counter.
     (insert_cantunwind_after): Increment relocations counter.
     (elf32_arm_fix_exidx_coverage): Remove exidx entries and add
     terminating CANTUNWIND entry only in final builds.
     (elf32_arm_add_relocation): New function.
     (elf32_arm_write_section): Add relocations in relocatable builds.
     (elf32_arm_count_additional_relocs): New function.
     (elf_backend_count_additional_relocs): New define.
     * bfd/elflink.c (bfd_elf_final_link): Use callback and adjust size of
     .rel section.
     * bfd/elfxx-target.h (elf_backend_count_additional_relocs): New define.

ld   * emultempl/armelf.em (gld${EMULATION_NAME}_after_allocation): Call
     elf32_arm_fix_exidx_coverage for relocatable builds.

ld/testsuite
     * ld-arm/arm-elf.exp: New test.
     * ld-arm/unwind-rel.d: New file.
     * ld-arm/unwind-rel1.s: New file.
     * ld-arm/unwind-rel2.s: New file.
     * ld-arm/unwind-rel3.s: New file.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] gdbserver crash in gdb/gdbserver/thread.c::thread_search_callback
@ 2015-12-22 15:43 sergiodj+buildbot
  2015-12-22 19:01 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-12-22 15:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0e50fe5ca6ed2ce780cbbfa516aec20b023433ce ***

Author: Joel Brobecker <brobecker@adacore.com>
Branch: master
Commit: 0e50fe5ca6ed2ce780cbbfa516aec20b023433ce

gdbserver crash in gdb/gdbserver/thread.c::thread_search_callback

Connecting GDB to a LynxOS-178 GDBserver causes GDBserver to crash:

    % gdbserver :4444 simple_main
    Process simple_main created; pid = 19
    Listening on port 4444
    Remote debugging from host 205.232.38.10
    Segmentation fault (core dumped)

The crash happens in thread_search_callback where the function
calls the_target->thread_stopped (via the thread_stopped macro)
without verifying whether the callback is NULL or not.

For the record, the regression was introduced by:

    commit a67a9faef0e32886c83611cc7a0ba61e91123063
    Date:   Mon Nov 30 16:05:26 2015 +0000
    Subject: gdbserver:prepare_access_memory: pick another thread

This patch avoids the crash by checking the value of the callback
first, before calling it.

gdb/gdbserver/ChangeLog:

        * target.c (thread_search_callback): Add check that
        the thread_stopped target callback is not NULL before
        calling it.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Remove HP-UX references fom testsuite
@ 2015-12-21 18:02 sergiodj+buildbot
  2015-12-21 18:57 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-12-21 18:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3ca22649a6dfeb71058c33be4d0542b98f1f0ff5 ***

Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: 3ca22649a6dfeb71058c33be4d0542b98f1f0ff5

Remove HP-UX references fom testsuite

This patch removes all special cases for HP-UX, for which support has
been removed earlier, that I found in the testsuite.  Note that the hppa
architecture != HP-UX, since other OSes can run on hppa, so I tried to
leave everything that is not HP-UX specific.

Two complete tests were completely HP-UX specific, so I removed them.

I ran the testsuite on Linux x86-64, native and native-gdbserver, and
noticed no regressions.

gdb/testsuite/ChangeLog:

	* gdb.asm/asm-source.exp: Remove HP-UX references.
	* gdb.base/annota1.exp: Likewise.
	* gdb.base/annota3.exp: Likewise.
	* gdb.base/attach.exp: Likewise.
	* gdb.base/bigcore.exp: Likewise.
	* gdb.base/break.exp: Likewise.
	* gdb.base/call-ar-st.exp: Likewise.
	* gdb.base/callfuncs.exp: Likewise.
	* gdb.base/catch-fork-static.exp: Likewise.
	* gdb.base/display.exp: Likewise.
	* gdb.base/foll-exec-mode.exp: Likewise.
	* gdb.base/foll-exec.exp: Likewise.
	* gdb.base/foll-fork.exp: Likewise.
	* gdb.base/foll-vfork.exp: Likewise.
	* gdb.base/funcargs.exp: Likewise.
	* gdb.base/hbreak2.exp: Likewise.
	* gdb.base/inferior-died.exp: Likewise.
	* gdb.base/interrupt.exp: Likewise.
	* gdb.base/multi-forks.exp: Likewise.
	* gdb.base/nodebug.exp: Likewise.
	* gdb.base/sepdebug.exp: Likewise.
	* gdb.base/solib1.c: Likewise.
	* gdb.base/step-test.exp: Likewise.
	* gdb.mi/non-stop.c: Likewise.
	* gdb.mi/pthreads.c: Likewise.
	* gdb.multi/bkpt-multi-exec.ex: Likewise.
	* gdb.threads/pthreads.c: Likewise.
	* gdb.threads/staticthreads.exp: Likewise.
	* lib/future.exp: Likewise.
	* lib/gdb.exp: Likewise.
	* gdb.base/so-indr-cl.c: Remove.
	* gdb.base/so-indr-cl.exp: Likewise.
	* gdb.base/solib.c: Likewise.
	* gdb.base/solib.exp: Likewise.
	* gdb.base/solib2.c: Likewise.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Remove references to HP CC/aCC compiler from testsuite
@ 2015-12-21 16:34 sergiodj+buildbot
  2015-12-21 17:52 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-12-21 16:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b6304613bf0bb1c188bed30eb3df6e3e154b4196 ***

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

Remove references to HP CC/aCC compiler from testsuite

The HP CC/aCC compiler is exclusive to HP-UX, for which support has been
explicitly removed.  Therefore, It does not make sense to keep tests
for these compilers' quirks.

gdb/testsuite/ChangeLog:

	* gdb.base/break.exp: Remove references to HP CC/aCC compilers.
	* gdb.base/call-ar-st.exp: Likewise.
	* gdb.base/callfuncs.exp: Likewise.
	* gdb.base/condbreak.exp: Likewise.
	* gdb.base/constvars.exp: Likewise.
	* gdb.base/hbreak2.exp: Likewise.
	* gdb.base/langs.exp: Likewise.
	* gdb.base/list.exp: Likewise.
	* gdb.base/long_long.exp: Likewise.
	* gdb.base/ptype.exp: Likewise.
	* gdb.base/scope.exp: Likewise.
	* gdb.base/signals.exp: Likewise.
	* gdb.base/so-impl-ld.exp: Likewise.
	* gdb.base/varargs.exp: Likewise.
	* gdb.base/volatile.exp: Likewise.
	* gdb.base/whatis.exp: Likewise.
	* gdb.cp/cplusfuncs.exp: Likewise.
	* gdb.cp/inherit.exp: Likewise.
	* gdb.cp/local.exp: Likewise.
	* gdb.cp/member-ptr.exp: Likewise.
	* gdb.cp/method.exp: Likewise.
	* gdb.cp/overload.exp: Likewise.
	* gdb.cp/templates.exp: Likewise.
	* gdb.stabs/weird.exp: Likewise.
	* lib/compiler.c: Likewise.
	* lib/compiler.cc: Likewise.
	* lib/cp-support.exp: Likewise.
	* lib/gdb.exp: Likewise.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
[parent not found: <a4e22a5df64a46bc99f737a982c0b9d1e8a45e2b@gdb-build>]
* [binutils-gdb] Add documentation to gdb_compile
@ 2015-12-18 18:50 sergiodj+buildbot
  2015-12-20  5:29 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-12-18 18:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT aff9c0f8ab32e4f2f7ff9700afe84a61d23a08c6 ***

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

Add documentation to gdb_compile

This patch adds some documentation to gdb_compile.  It describes the
various options that can influence compilation.  Most of them are
handled by DejaGnu, but are not really documented anywhere, so I think
it's good to have a quick reference.  Not all possible options are
described, that would add way to much noise.  I chose those that I think
are relevant in the context of writing a test case.

gdb/testsuite/ChangeLog:

	* lib/gdb.exp (gdb_compile): Add function doc.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Enable software single stepping for while-stepping actions in GDBServer
@ 2015-12-18 17:51 sergiodj+buildbot
  2015-12-20  3:31 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-12-18 17:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7fe5e27e9d63b065731b1b0b69ffd344942f4f39 ***

Author: Antoine Tremblay <antoine.tremblay@ericsson.com>
Branch: master
Commit: 7fe5e27e9d63b065731b1b0b69ffd344942f4f39

Enable software single stepping for while-stepping actions in GDBServer

This patch enables software single stepping if the targets support it,
to do while-stepping actions.

No regressions, tested on ubuntu 14.04 ARMv7 and x86.
With gdbserver-{native,extended} / { -marm -mthumb }

gdb/gdbserver/ChangeLog:

	* linux-low.c (single_step): New function.
	(linux_resume_one_lwp_throw): Call single_step.
	(start_step_over): Likewise.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Replace breakpoint_reinsert_addr by get_next_pcs operation in GDBServer
@ 2015-12-18 16:58 sergiodj+buildbot
  2015-12-19 22:25 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-12-18 16:58 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fa5308bdcc4967861d1277b45205c2623b154a64 ***

Author: Antoine Tremblay <antoine.tremblay@ericsson.com>
Branch: master
Commit: fa5308bdcc4967861d1277b45205c2623b154a64

Replace breakpoint_reinsert_addr by get_next_pcs operation in GDBServer

This patch in preparation for software single step support on ARM. It refactors
breakpoint_reinsert_addr into get_next_pcs so that multiple location can be
returned.

When software single stepping there can be multiple possible next addresses
because we're stepping over a conditional branch instruction, for example.

The operation get_next_pcs handles that by returning a vector of all the
possible next addresses.

Software breakpoints are installed at each location returned.

No regressions, tested on ubuntu 14.04 ARMv7 and x86.
With gdbserver-{native,extended} / { -marm -mthumb }

gdb/gdbserver/ChangeLog:

	* linux-aarch64-low.c (the_low_targets): Rename
	breakpoint_reinsert_addr to get_next_pcs.
	* linux-arm-low.c (the_low_targets): Likewise.
	* linux-bfin-low.c (the_low_targets): Likewise.
	* linux-cris-low.c (the_low_targets): Likewise.
	* linux-crisv32-low.c (the_low_targets): Likewise.
	* linux-low.c (can_software_single_step): Likewise.
	(install_software_single_step_breakpoints): New function.
	(start_step_over): Use install_software_single_step_breakpoints.
	* linux-low.h: New CORE_ADDR vector.
	(struct linux_target_ops) Rename breakpoint_reinsert_addr to
	get_next_pcs.
	* linux-mips-low.c (the_low_targets): Likewise.
	* linux-nios2-low.c (the_low_targets): Likewise.
	* linux-sparc-low.c (the_low_targets): Likewise.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Update the copyright notices in the affected files.
@ 2015-12-17 20:12 sergiodj+buildbot
  2015-12-19  8:12 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-12-17 20:12 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 08832196accd270fa053e8125c21e7a54ab19fe0 ***

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

Update the copyright notices in the affected files.

	PR 19339
	* elf-vxworks.h: Update copyright notice.
	* elf-vxworks.c: Update copyright notice.
	* elf-nacl.h: Update copyright notice.
	* elf-nacl.c: Update copyright notice.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Skip gdb.base/gdbinit-history.exp on remote hosts.
@ 2015-12-17 18:36 sergiodj+buildbot
  2015-12-19  4:06 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-12-17 18:36 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5d978e177217d8e9da8648498f0592b5cd885e69 ***

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

Skip gdb.base/gdbinit-history.exp on remote hosts.

2015-12-14  Sandra Loosemore  <sandra@codesourcery.com>

	gdb/testsuite/
	* gdb.base/gdbinit-history.exp: Skip for remote-host testing.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Target remote mode fork and exec test updates
@ 2015-12-17 16:37 sergiodj+buildbot
  2015-12-18 20:58 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-12-17 16:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a8f077dc25b1732fb272a7ff10f72b5ca6f67b70 ***

Author: Don Breazeal <donb@codesourcery.com>
Branch: master
Commit: a8f077dc25b1732fb272a7ff10f72b5ca6f67b70

Target remote mode fork and exec test updates

This patch updates tests for fork and exec events in target remote mode.
In the majority of cases this was a simple matter of removing some code
that disabled the test for target remote.  In a few cases the test needed
to be disabled; in those cases the gdb_protocol was checked instead of
using the [is_remote target] etc.

In a couple of cases we needed to use clean_restart, since target remote
doesn't support the run command, and in one case we had to modify an expect
expression to allow for a "multiprocess-style" ptid.

Tested with the patch that implemented target remote mode fork and exec
event support.

gdb/testsuite/ChangeLog:

	* gdb.base/execl-update-breakpoints.exp (main): Enable for target
	remote.
	* gdb.base/foll-exec-mode.exp (main): Disable for target remote.
	* gdb.base/foll-exec.exp (main): Enable for target remote.
	* gdb.base/foll-fork.exp (main): Likewise.
	* gdb.base/foll-vfork.exp (main): Likewise.
	* gdb.base/multi-forks.exp (main): Likewise, and use clean_restart.
	(proc continue_to_exit_bp_loc): Use clean_restart.
	* gdb.base/pie-execl.exp (main): Disable for target remote.
	* gdb.base/watch-vfork.exp (main): Enable for target remote.
	* gdb.mi/mi-nsthrexec.exp (main): Likewise.
	* gdb.threads/execl.exp (main): Likewise.
	* gdb.threads/fork-child-threads.exp (main): Likewise.
	* gdb.threads/fork-plus-threads.exp (main): Disable for target
	remote.
	* gdb.threads/fork-thread-pending.exp (main): Enable for target
	remote.
	* gdb.threads/linux-dp.exp (check_philosopher_stack): Allow
	pid.tid style ptids, instead of just tid.
	* gdb.threads/thread-execl.exp (main): Enable for target remote.
	* gdb.threads/watchpoint-fork.exp (main): Likewise.
	* gdb.trace/report.exp (use_collected_data): Allow pid.tid style
	ptids, instead of just tid.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Fix PR threads/19354: "info threads" error with multiple inferiors
@ 2015-12-17 15:38 sergiodj+buildbot
  2015-12-19 19:24 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-12-17 15:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a6904d5a6aa63e4bef7207407250d8b76b56f8a9 ***

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

Fix PR threads/19354: "info threads" error with multiple inferiors

Note: this applies on top of:
 [PATCH] Remove support for LinuxThreads and vendor 2.4 kernels w/ backported NPTL
 https://sourceware.org/ml/gdb-patches/2015-12/msg00214.html

We try to avoid using libthread_db.so to list threads in the inferior
when debugging live processes, but the code that decides whether to
use it decides incorrectly if you have more than one inferior, and the
current inferior doesn't have execution yet.  The result is visible
as:

 (gdb) add-inferior
 Added inferior 2
 (gdb) inferior 2
 [Switching to inferior 2 [<null>] (<noexec>)]
 (gdb) info inferiors
   Num  Description       Executable
   1    process 15397     /home/pedro/gdb/tests/threads
 * 2    <null>
 (gdb) info threads
 Cannot find new threads: generic error
 (gdb)

Fix this by checking whether each inferior has execution rather than
just the current inferior.

By moving the core updating to linux-nat.c's update_thread_list
implementation, this also ends up fixing the
lwp-last-seen-running-on-core updating in the case we're debugging a
program that uses raw clone rather than pthreads, as linux-thread-db.c
isn't pushed in the target stack in that scenario.

Tested on x86_64 Fedora 20.

gdb/ChangeLog:
2015-12-17  Pedro Alves  <palves@redhat.com>

	PR threads/19354
	* linux-nat.c (linux_nat_update_thread_list): Update process cores
	each lwp was last seen running on here.
	* linux-thread-db.c (update_thread_core): Delete.
	(thread_db_update_thread_list_td_ta_thr_iter): Rename to ...
	(thread_db_update_thread_list): ... this.  Skip inferiors with
	execution.  Also call the target beneath.
	(thread_db_update_thread_list): Delete.

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

	PR threads/19354
	* gdb.multi/info-threads.exp: New file.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [AArch64][PATCH 11/14] Add support for the 2H vector type.
@ 2015-12-17 15:02 sergiodj+buildbot
  2015-12-18 16:18 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-12-17 15:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3067d3b96cfb88e86acf94d2aa1575cff0e0110f ***

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

[AArch64][PATCH 11/14] Add support for the 2H vector type.

ARMv8.2 adds 16-bit floating point operations as an optional extension
to the floating point and Adv.SIMD support. The FP16 additions to the
scalar pairwise group introduce a new vector type, 2H. This patch adds
support for this vector type to binutils.

The patch adds a new operand qualifier to the enum
aarch64.h:aarch64_opnd_qualifier. This interferes with the calculation
used by aarch64-dis.c:get_vreg_qualifier_from_value, called when
decoding an instruction. Since the new vector type is only used in FP16
scalar pairwise instructions which do not require the function, this
patch adjusts the function to ignore the new qualifier.

gas/
2015-12-14  Matthew Wahab  <matthew.wahab@arm.com>

	* config/tc-aarch64.c (parse_neon_type_for_operand): Adjust to
	take into account new vector type 2H.
	(vectype_to_qualifier): Likewise.

include/opcode/
2015-12-14  Matthew Wahab  <matthew.wahab@arm.com>

	* aarch64.h (enum aarch64_opnd_qualifier): Add
	AARCH64_OPND_QLF_V_2H.

opcodes/
2015-12-14  Matthew Wahab  <matthew.wahab@arm.coM>

	* aarch64-dis.c (get_vreg_qualifier_from_value): Update comment
	and adjust calculation to ignore qualifier for type 2H.
	* aarch64-opc.c (aarch64_opnd_qualifier): Add "2H".

Change-Id: Idf9a3694732962c80fde04f08c7304de9164f126


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [ARM] Add support for thumb1 pcrop relocations.
@ 2015-12-17 10:05 sergiodj+buildbot
  2015-12-19 13:15 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-12-17 10:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 72d98d16ed09584660d0cbb759d90f8dfeef2343 ***

Author: Mickael Guene <mickael.guene@st.com>
Branch: master
Commit: 72d98d16ed09584660d0cbb759d90f8dfeef2343

[ARM] Add support for thumb1 pcrop relocations.

To support thumb1 execute-only code we need to support four new
relocations (R_ARM_THM_ALU_ABS_G0_NC, R_ARM_THM_ALU_ABS_G1_NC,
R_ARM_THM_ALU_ABS_G2_NC and  R_ARM_THM_ALU_ABS_G3_NC).
These relocations allow the static linker to finalize construction
of symbol address.
Typical sequence of code to get address of the symbol foo is then
the following :
	movs	r3, #:upper8_15:#foo
	lsls	r3, #8
	adds	r3, #:upper0_7:#foo
	lsls	r3, #8
	adds	r3, #:lower8_15:#foo
	lsls	r3, #8
	adds	r3, #:lower0_7:#foo
This will give following sequence of text and relocations after
assembly :
   4:	2300      	movs	r3, #0
			4: R_ARM_THM_ALU_ABS_G3_NC	foo
   6:	021b      	lsls	r3, r3, #8
   8:	3300      	adds	r3, #0
			8: R_ARM_THM_ALU_ABS_G2_NC	foo
   a:	021b      	lsls	r3, r3, #8
   c:	3300      	adds	r3, #0
			c: R_ARM_THM_ALU_ABS_G1_NC	foo
   e:	021b      	lsls	r3, r3, #8
  10:	3300      	adds	r3, #0
			10: R_ARM_THM_ALU_ABS_G0_NC	foo


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Tweak gdb.trace/ftrace.exp for aarch64
@ 2015-12-17  9:14 sergiodj+buildbot
  2015-12-19 11:05 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-12-17  9:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a22279dd83da7a0dd2b496c92dc2522427f74e37 ***

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

Tweak gdb.trace/ftrace.exp for aarch64

Some tests are skipped on aarch64 unexpectedly because arg0exp isn't
set.  This patch is to set arg0exp to "$x0" for aarch64.

gdb/testsuite:

2015-12-15  Yao Qi  <yao.qi@linaro.org>

	* gdb.trace/ftrace.exp: Set arg0exp to "$x0" if target
	is aarch64*-*-*.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Add support for RX V2 Instruction Set
@ 2015-12-17  7:40 sergiodj+buildbot
  2015-12-19  6:06 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-12-17  7:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a117b0a51cd3c768453c244a3754c1b9a77e74fc ***

Author: Yoshinori Sato <ysato@users.sourceforge.jp>
Branch: master
Commit: a117b0a51cd3c768453c244a3754c1b9a77e74fc

Add support for RX V2 Instruction Set

binutils
	* readelf.c(get_machine_flags): Add v2 flag.

gas
	* config/rx-defs.h(rx_cpu_type): Add RXV2 type.
	* config/tc-rx.c(cpu_type_list): New type lookup table.
	(md_parse_option): Use lookup table for choose cpu.
	(md_show_usage): Add rxv2 for mcpu option.
	* doc/c-rx.texi: Likewise.
	* config/rx-parse.y: Add v2 instructions and ACC register.
	(rx_check_v2): check v2 type.

include/elf
	* rx.h(E_FLAG_RX_V2): New RXv2 type.

include/opcode
	* rx.h: Add new instructions.

opcoes
	* rx-deocde.opc(rx_decode_opcode): Add new instructions pattern.
	* rx-dis.c(register_name): Add new register.

gas/testsuite
	* gas/rx/emaca.d: New.
	* gas/rx/emaca.sm: New.
	* gas/rx/emsba.d: New.
	* gas/rx/emsba.sm: New.
	* gas/rx/emula.d: New.
	* gas/rx/emula.sm: New.
	* gas/rx/fadd.d: Add new pattern.
	* gas/rx/fadd.sm: Add new pattern.
	* gas/rx/fmul.d: Add new pattern.
	* gas/rx/fmul.sm: Add new pattern.
	* gas/rx/fsqrt.d: New.
	* gas/rx/fsqrt.sm: New.
	* gas/rx/fsub.d: Add new pattern.
 	* gas/rx/fsub.sm: Add new pattern.
	* gas/rx/ftou.d: New.
	* gas/rx/ftou.sm: New.
	* gas/rx/maclh.d: New.
	* gas/rx/maclh.sm: New.
	* gas/rx/maclo.d: Add new pattern.
	* gas/rx/maclo.sm: Add new pattern.
	* gas/rx/macros.inc: Add new register.
	* gas/rx/movco.d: New.
	* gas/rx/movco.sm: New.
	* gas/rx/movli.d: New.
	* gas/rx/movli.sm: New.
	* gas/rx/msbhi.d: New.
	* gas/rx/msbhi.sm: New.
	* gas/rx/msblh.d: New.
	* gas/rx/msblh.sm: New.
	* gas/rx/msblo.d: New.
	* gas/rx/msblo.sm: New.
	* gas/rx/mullh.d: New.
	* gas/rx/mullh.sm: New.
	* gas/rx/mvfacgu.d: New.
	* gas/rx/mvfacgu.sm: New.
	* gas/rx/mvfachi.d: Add new pattern.
	* gas/rx/mvfachi.sm: Add new pattern.
	* gas/rx/mvfaclo.d: Add new pattern.
	* gas/rx/mvfaclo.sm: Add new pattern.
	* gas/rx/mvfacmi.d: Add new pattern.
	* gas/rx/mvfacmi.sm: Add new pattern.
	* gas/rx/mvfc.d: Add new pattern.
	* gas/rx/mvtacgu.d: New.
	* gas/rx/mvtacgu.sm: New.
	* gas/rx/mvtc.d: Add new pattern.
	* gas/rx/popc.d: Add new pattern.
	* gas/rx/pushc.d: Add new pattern.
	* gas/rx/racl.d: New.
	* gas/rx/racl.sm: New.
	* gas/rx/racw.d: Add new pattern.
	* gas/rx/racw.sm: Add new pattern.
	* gas/rx/rdacl.d: New.
	* gas/rx/rdacl.sm: New.
	* gas/rx/rdacw.d: New.
	* gas/rx/rdacw.sm: New.
	* gas/rx/rx.exp: Add option.
	* gas/rx/stnz.d: Add new pattern.
	* gas/rx/stnz.sm: Add new pattern.
	* gas/rx/stz.d: Add new pattern.
	* gas/rx/stz.sm: Add new pattern.
	* gas/rx/utof.d: New.
	* gas/rx/utof.sm: New.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Check for readline support in gdb.base/history-duplicates.exp.
@ 2015-12-17  7:33 sergiodj+buildbot
  2015-12-19  5:12 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-12-17  7:33 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0588c79688b061699500f317e193bbb3fe50c41d ***

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

Check for readline support in gdb.base/history-duplicates.exp.

2015-12-14  Sandra Loosemore  <sandra@codesourcery.com>

	gdb/testsuite/
	* gdb.base/history-duplicates.exp: Skip if no readline support.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Skip tests that send ctrl-c to GDB if nointerrupts target property is set.
@ 2015-12-17  7:08 sergiodj+buildbot
  2015-12-19  0:55 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-12-17  7:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 87a3a92c46c770e6aa2ca1209f46af16eae2c4e9 ***

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

Skip tests that send ctrl-c to GDB if nointerrupts target property is set.

2015-12-14  Sandra Loosemore  <sandra@codesourcery.com>

	gdb/testsuite/
	* gdb.base/completion.exp: Skip tests that interrupt GDB with
	ctrl-C if nointerrupts target property is set.
	* gdb.base/double-prompt-target-event-error.exp: Likewise.
	* gdb.base/paginate-after-ctrl-c-running.exp: Likewise.
	* gdb.base/paginate-bg-execution.exp: Likewise.
	* gdb.base/paginate-execution-startup.exp: Likewise.
	* gdb.base/random-signal.exp: Likewise.
	* gdb.base/range-stepping.exp: Likewise.
	* gdb.cp/annota2.exp: Likewise.
	* gdb.cp/annota3.exp: Likewise.
	* gdb.gdb/selftest.exp: Likewise.
	* gdb.threads/continue-pending-status.exp: Likewise.
	* gdb.threads/leader-exit.exp: Likewise.
	* gdb.threads/manythreads.exp: Likewise.
	* gdb.threads/pthreads.exp: Likewise.
	* gdb.threads/schedlock.exp: Likewise.
	* gdb.threads/sigthread.exp: Likewise.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Target remote mode fork and exec event support
@ 2015-12-17  6:17 sergiodj+buildbot
  2015-12-18 22:15 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-12-17  6:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8020350c5277e056e89b0ea5e14a8d09408f7fb3 ***

Author: Don Breazeal <donb@codesourcery.com>
Branch: master
Commit: 8020350c5277e056e89b0ea5e14a8d09408f7fb3

Target remote mode fork and exec event support

This patch implements support for fork and exec events with target remote
mode Linux targets.  For such targets with Linux kernels 2.5.46 and later,
this enables follow-fork-mode, detach-on-fork and fork and exec
catchpoints.

The changes required to implement this included:

 * Don't exit from gdbserver if there are still active inferiors.

 * Allow changing the active process in remote mode.

 * Enable fork and exec events in remote mode.

 * Print "Ending remote debugging" only when disconnecting.

 * Combine remote_kill and extended_remote_kill into a single function
   that can handle the multiple inferior case for target remote.  Also,
   the same thing for remote_mourn and extended_remote_mourn.

 * Enable process-style ptids in target remote.

 * Remove restriction on multiprocess mode in target remote.

gdb/gdbserver/ChangeLog:

	* server.c (process_serial_event): Don't exit from gdbserver
	in remote mode if there are still active inferiors.

gdb/ChangeLog:

	* inferior.c (number_of_live_inferiors): New function.
	(have_live_inferiors): Use number_of_live_inferiors in place
	of duplicate code.
	* inferior.h (number_of_live_inferiors): Declare new function.
	* remote.c (set_general_process): Remove restriction on target
	remote mode.
	(remote_query_supported): Likewise.
	(remote_detach_1): Exit in target remote mode only when there
	is just one live inferior left.
	(remote_disconnect): Unpush the target directly instead of
	calling remote_mourn.
	(remote_kill): Rewrite function to handle both target remote
	and extended-remote.  Call remote_kill_k.
	(remote_kill_k): New function.
	(extended_remote_kill): Delete function.
	(remote_mourn, extended_remote_mourn): Combine functions into
	one, remote_mourn, and enable extended functionality for target
	remote.
	(remote_pid_to_str): Enable "process" style ptid string for
	target remote.
	(remote_supports_multi_process): Remove restriction on target
	remote mode.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [AArch64][PATCH 8/14] Support FP16 Adv.SIMD Across Lanes instructions.
@ 2015-12-17  5:21 sergiodj+buildbot
  2015-12-18 13:46 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-12-17  5:21 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bb515fea4ac30f761c17dec701c95c0b54fabf30 ***

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

[AArch64][PATCH 8/14] Support FP16 Adv.SIMD Across Lanes instructions.

ARMv8.2 adds 16-bit floating point operations as an optional extension
to the floating point and Adv.SIMD support. This patch adds FP16
instructions to the group Adv.SIMD Across Lanes, making them available
when +simd+fp16 is enabled.

The instructions added are: FMAXNMV, FMAXV, FMINNMV and FMINV.

The general form for these instructions is
   <OP> <Hd>, <V>.<T>
   where T is 4h or 8h.

The new instructions valid make uses of the 8H and 4H that were
previously illegal. The patch adjusts a test for illegal uses of vector
types to take this into account.

gas/testsuite/
2015-12-14  Matthew Wahab  <matthew.wahab@arm.com>

	* gas/aarch64/advsimd-fp16.d: Update expected output.
	* gas/aarch64/advsimd-fp16.s: Add tests for Adv.SIMD across lanes
	instructions.
	* gas/aarch64/illegal.d: Update expected output.
	* gas/aarch64/illegal.s: Replace test for illegal use of 'h'
	specifier.

opcodes/
2015-12-14  Matthew Wahab  <matthew.wahab@arm.com>

	* aarch64-asm-2.c: Regenerate.
	* aarch64-dis-2.c: Regenerate.
	* aarch64-opc-2.c: Regenerate.
	* aarch64-tbl.h (QL_XLANES_FP_H): New.
	(aarch64_opcode_table): Add fp16 versions of fmaxnmv, fmaxv,
	fminnmv, fminv to the Adv.SIMD across lanes group.

Change-Id: Ib9a47e867f55e0272c2446eb7e16837503d2f94c


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [AArch64][PATCH 6/14] Support FP16 Vector Indexed Element instructions.
@ 2015-12-17  5:06 sergiodj+buildbot
  2015-12-18 12:03 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-12-17  5:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 42f23f6218262ae8488caab214b7f272c6758941 ***

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

[AArch64][PATCH 6/14] Support FP16 Vector Indexed Element instructions.

ARMv8.2 adds 16-bit floating point operations as an optional extension
to the floating point and Adv.SIMD support. This patch adds FP16
instructions to the group Vector Indexed Element, making them available
when +simd+fp16 is enabled.

The instructions added are: FMLA, FMLS, FMUL and FMULX.

The general form for these instructions is
  <OP> <V>.<T>, <V>.<T>, <V>.h[<idx>]
  where T is 4h or 8h

gas/testsuite/
2015-12-14  Matthew Wahab  <matthew.wahab@arm.com>

	* gas/aarch64/advsimd-fp16.d: Update expected output.
	* gas/aarch64/advsimd-fp16.s: Add tests for vector indexed element
	instructions.

opcodes/
2015-12-14  Matthew Wahab  <matthew.wahab@arm.com>

	* aarch64-asm-2.c: Regenerate.
	* aarch64-dis-2.c: Regenerate.
	* aarch64-opc-2.c: Regenerate.
	* aarch64-tbl.h (QL_ELEMENT_FP_H): New.
	(aarch64_opcode_table): Add fp16 versions of fmla, fmls, fmul and
	fmulx to the vector indexed element group.

Change-Id: Ib70cd4eaa6ea2938f84ac41f31d72644dbb0ceb4


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [AArch64][PATCH 5/14] Support FP16 Scalar Two Register Misc. instructions.
@ 2015-12-17  4:58 sergiodj+buildbot
  2015-12-18 10:44 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-12-17  4:58 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 80776b29d60ebdcd3631604858f144a72b8bcb8e ***

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

[AArch64][PATCH 5/14] Support FP16 Scalar Two Register Misc. instructions.

ARMv8.2 adds 16-bit floating point operations as an optional extension
to the floating point and Adv.SIMD support. This patch adds FP16
instructions to the group Scalar Two Register Misc, making them
available when +simd+fp16 is enabled.

The instructions added are: FCMGT, FCMGE, FCMEQ, FCMLE, FCMLT, FCVTNS,
FCVTNU, FCVTPS, FCVTPU, FCVTMS, FCVTMU, FCVTZS, FCVTZU, FCVTAS, FCVTAU,
SCVTF, UCVTF, FRECPE, FRSQRTE and FRECPX.

The general form for these instructions is
  <OP> <Hd>, <Hs>
or
  <OP> <Hd>, <Hs>, #0.0

Tested the series for aarch64-none-linux-gnu with cross-compiled
check-binutils and check-gas.

gas/testsuite/
2015-12-14  Matthew Wahab  <matthew.wahab@arm.com>

	* gas/aarch64/advsimd-fp16.d: Update expected output.
	* gas/aarch64/advsimd-fp16.s: Add tests for scalar two register misc.
	instructions.

opcodes/
2015-12-14  Matthew Wahab  <matthew.wahab@arm.com>

	* aarch64-asm-2.c: Regenerate.
	* aarch64-dis-2.c: Regenerate.
	* aarch64-opc-2.c: Regenerate.
	* aarch64-tbl.h (QL_SISD_FCMP_H_0): new.
	(QL_S_2SAMEH): New.
	(aarch64_opcode_table): Add fp16 versions of fcvtns, fcvtms,
	fcvtas, scvtf, fcmgt, fcmeq, fcmlt, fcvtps, fcvtzs, frecpe,
	frecpx, fcvtnu, fcvtmu, fcvtau, ucvtf, fcmge, fcmle, fcvtpu,
	fcvtzu and frsqrte to the scalar two register misc. group.

Change-Id: I19b25baae33027ce1bade68cc8dc47a4321d045c


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [AArch64][PATCH 4/14] Support FP16 Vector Two Register Misc. instructions.
@ 2015-12-17  4:50 sergiodj+buildbot
  2015-12-18  9:43 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-12-17  4:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f3aa142b8b04bfccef2cbc3233b565c2b3faa01a ***

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

[AArch64][PATCH 4/14] Support FP16 Vector Two Register Misc. instructions.

ARMv8.2 adds 16-bit floating point operations as an optional extension
to the floating point and Adv.SIMD support. This patch adds FP16
instructions to the group Vector Two Register Misc, making them
available when +simd+fp16 is enabled.

The instructions added are: FCMGT, FCMGE, FCMEQ, FCMLE, FCMLT, FABS,
FNEG, FRINTN, FRINTA, FRINTP, FRINTM, FRINTX, FRINTZ, FRINTI, FCVTNS,
FCVTNU, FCVTPS, FCVTPU, FCVTMS, FCVTMU, FCVTZS, FCVTZU, FCVTAS, FCVTAU,
SCVTF, UCVTF, FRECPE, FRSQRTE and FSQRT.

The general form for these instructions is
  <OP> <Vd>.<T>, <Vs>.<T>
  where T is 4h or 8h.

gas/testsuite/
2015-12-14  Matthew Wahab  <matthew.wahab@arm.com>

	* gas/aarch64/advsimd-fp16.d: Update expected output.
	* gas/aarch64/advsimd-fp16.s: Add tests for vector two register misc.
	instructions.

opcodes/
2015-12-14  Matthew Wahab  <matthew.wahab@arm.com>

	* aarch64-asm-2.c: Regenerate.
	* aarch64-dis-2.c: Regenerate.
	* aarch64-opc-2.c: Regenerate.
	* aarch64-tbl.h (QL_V2SAMEH): New.
	(aarch64_opcode_table): Add fp16 versions of frintn, frintm,
	fcvtns, fcvtms, fcvtas, scvtf, fcmgt, fcmeq, fcmlt, fabs, frintp,
	frintz, fcvtps, fcvtzs, frecpe, frinta, frintx, fcvtnu, fcvtmu,
	fcvtau, ucvtf, fcmge, fcmle, fneg, frinti, fcvtpu, fcvtzu, frsqrte
	and fsqrt to the vector register misc. group.

Change-Id: I0267511a7f7ea14247504d29fe4752e84c9af9ad


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [AArch64][PATCH 2/14] Support ARMv8.2 FP16 Vector Three Same instructions.
@ 2015-12-17  4:35 sergiodj+buildbot
  2015-12-18  7:12 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-12-17  4:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 51d543ed936c9ea7d045ecf80030e6bc8ffff29f ***

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

[AArch64][PATCH 2/14] Support ARMv8.2 FP16 Vector Three Same instructions.

ARMv8.2 adds 16-bit floating point operations as an optional extension
to floating point and Adv.SIMD support. This patch adds FP16
instructions to the group Vector Three Register Same, making them
available when +simd+fp16 is enabled.

The instructions added are: FMAXNM, FMAXNMP, FNMINNM, FMINNMP, FMLA,
FMLS, FADD, FADDP, FSUB, FABD, FMULX, FMUL, FCMEQ, FCMGE, FCMGT, FACGE,
FACGT, FMAX, FMAXP, FMIN, FMINP, FRECPS, FDIV and FRSQRTS.

The general form for these instructions is
  <OP> <Vd>.<T>, <Vs>.<T>, <Vm>.<T>
  where T is 4h or 8h.

gas/testsuite/
2015-12-14  Matthew Wahab  <matthew.wahab@arm.com>

	* gas/aarch64/advsimd-fp16.d: New.
	* gas/aarch64/advsimd-fp16.s: New.

opcodes/
2015-12-14  Matthew Wahab  <matthew.wahab@arm.com>

	* aarch64-asm-2.c: Regenerate.
	* aarch64-dis-2.c: Regenerate.
	* aarch64-opc-2.c: Regenerate.
	* aarch64-tbl.h (QL_V3SAMEH): New.
	(aarch64_opcode_table): Add fp16 versions of fmaxnm, fmla, fadd,
	fmulx, fcmeq, fmax, frecps, fminnm, fmls, fsub, fmin, frsqrts,
	fmaxnmp, faddp, fmul, fcmge, facge, fmaxp, fdiv, fminnmp, fabd,
	fcmgt, facgt and fminp to the vector three same group.

Change-Id: I3f1c5fe82ca73f7a17fe5329cf2b0de03c94328c


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [AArch64] Fix errors rebasing the ARMv8.2 AT and system registers patch
@ 2015-12-17  4:19 sergiodj+buildbot
  2015-12-18  5:22 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-12-17  4:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6351190792e586b5e80fe0efa0f254b4da0b6705 ***

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

[AArch64] Fix errors rebasing the ARMv8.2 AT and system registers patch

A mistake with rebasing the ARMv8.2 AT instruction patch left this part

+  /* AT S1E1RP, AT S1E1WP.  Values are from aarch64_sys_regs_at.  */
+  if ((reg->value == CPENS (0, C7, C9, 0)
+       || reg->value == CPENS (0, C7, C9, 1))
+      && !AARCH64_CPU_HAS_FEATURE (features, AARCH64_FEATURE_V8_2))
+    return FALSE;

in aarch64_pstatefield_supported_p rather than in
aarch64_sys_ins_reg_supported_p, where it was supposed to be.

The patch adding support for id_aa64mmfr2_el1, also had the effect of
removing a conditional branch in aarch64_sys_reg_supported_p.

The effect of both of these is to suppress an error if some ARMv8.2
system registers are used with the wrong -march settings.

This patch fixes these mistakes.

opcodes/
2015-12-14  Matthew Wahab  <matthew.wahab@arm.com>

	* aarch64-opc.c (aarch64_sys_reg_supported_p): Add mistakenly
	removed statement.
	(aarch64_pstatefield_supported_p): Move feature checks for AT
	registers ..
	(aarch64_sys_ins_reg_supported_p): .. to here.

Change-Id: I48783d118eaaf0f3312e8b08a8340ef7af4e36a4


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] gdb: 'list' command, tweak handling of +/- arguments.
@ 2015-12-17  3:37 sergiodj+buildbot
  2015-12-17 23:32 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-12-17  3:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a0def019aaf79adf3add2a0559ab75bb84d72085 ***

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

gdb: 'list' command, tweak handling of +/- arguments.

There is an inconsistency with the handling of the special +/- arguments
to the list command.

For the very first time that list is used (after the inferior has
changed locations) then only the first character of the argument string
is checked, so 'list +BLAH' will operate as 'list +' and 'list -----FOO'
will operate as 'list -'.  This compares to each subsequent use of list,
where the whole argument string is checked, so 'list +BLAH' will try to
list lines of code around the function '+BLAH'.

This commit unifies the behaviour so that the whole argument string is
checked, in order to list the next 10, or previous 10 lines from a file
only 'list +' and 'list -' are now valid.

gdb/ChangeLog:

	* cli/cli-cmds.c (list_command): Check that the argument string is
	a single character, either '+' or '-'.

gdb/testsuite/ChangeLog:

	* gdb.base/list.exp (test_list_invalid_args): New function,
	defined, and called.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] gdb: Small code restructure for list_command.
@ 2015-12-17  3:20 sergiodj+buildbot
  2015-12-17 20:47 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-12-17  3:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1a48ce76774633e9e27dd245ba275a714b2b339f ***

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

gdb: Small code restructure for list_command.

Move handling of special +/- arguments to the list_command function
inside a single if block, this helps group all related functionality
together.  There should be no user visible changes after this commit.

gdb/ChangeLog:

	* cli/cli-cmds.c (list_command): Move all handling of +/-
	arguments into a single if block.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] gdb: Use NULL instead of 0 for pointer comparison.
@ 2015-12-17  3:12 sergiodj+buildbot
  2015-12-17 19:26 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-12-17  3:12 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8c05462adbc01f0aba946c42422146ccca2ae4db ***

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

gdb: Use NULL instead of 0 for pointer comparison.

Small code cleanup, use NULL instead of 0 when checking pointers.  There
should be no user visible changes after this commit.

gdb/ChangeLog:

	* cli/cli-cmds.c (list_command): Use NULL instead of 0 when
	checking pointers.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] gdb: Make lines_to_list variable static.
@ 2015-12-17  3:07 sergiodj+buildbot
  2015-12-17 18:19 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-12-17  3:07 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f43f85715ac097b6ff4bfaed00879eb541428c1a ***

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

gdb: Make lines_to_list variable static.

Small clean up, make variable static.

gdb/ChangeLog:

	* source.c (lines_to_list): Make static.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [AArch64][Patch 5/5] Add instruction PSB CSYNC
@ 2015-12-17  2:31 sergiodj+buildbot
  2015-12-17 13:51 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-12-17  2:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1e6f4800fc01c7957d0688158385aba3bf5ce8de ***

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

[AArch64][Patch 5/5] Add instruction PSB CSYNC

The Statistical Profile Extension adds the instruction PSB CSYNC as an
alias for the HINT #17 instruction. This patch adds the instruction to
binutils as a HINT alias that takes an operand.

A new operand type, AARCH64_OPND_BARRIER_PSB, is added to represent the
operand to PSB. A parser for the operand type is added to the assembler
and a printer to the disassembler. The operand name "csync" is added to
the list of HINT options with HINT number #17. Encoding and decoding of
the operand is handled by the ins_hint/ext_hint functions added in the
preceding patches.

gas/
2015-12-11  Matthew Wahab  <matthew.wahab@arm.com>

	* config/tc-aarch64.c (aarch64_hint_opt_hsh): New.
	(parse_barrier_psb): New.
	(parse_operands): Add case for AARCH64_OPND_BARRIER_PSB.
	(md_begin): Set up aarch64_hint_opt_hsh.

gas/testsuite/
2015-12-11  Matthew Wahab  <matthew.wahab@arm.com>

	* gas/aarch64/system-2.d: Enable the statistical profiling
	extension.  Update the expected output.
	* gas/aarch64/system-2.s: Add tests for PSB CSYNC.
	* gas/aarch64/system.d: Update the expected output.

include/opcode/
2015-12-11  Matthew Wahab  <matthew.wahab@arm.com>

	* aarch64.h (aarch64_opnd): Add AARCH64_OPND_BARRIER_PSB.
	* aarch64-asm-2.c: Regenerate.
	* aarch64-dis-2.c: Regenerate.
	* aarch64-opc-2.c: Regenerate.
	* aarch64-opc.c (aarch64_hint_options): Add "csync".
	(aarch64_print_operands): Handle AARCH64_OPND_BARRIER_PSB.
	* aarch64-tbl.h (aarch64_feature_stat_profile): New.
	(STAT_PROFILE): New.
	(aarch64_opcode_table): Add "psb".
	(AARCH64_OPERANDS): Add "BARRIER_PSB".

Change-Id: I5ffb672d26a8b15b48785478d359350a9b70ca09


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [AArch64][Patch 4/5] Support HINT aliases taking operands.
@ 2015-12-17  2:22 sergiodj+buildbot
  2015-12-17 12:49 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-12-17  2:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9ed608f98b2c8c483c994f884429420e74835417 ***

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

[AArch64][Patch 4/5] Support HINT aliases taking operands.

The Statistical Profile Extension adds the instruction PSB CSYNC as an
alias for the HINT #17 instruction. This patch adds support for aliases
of HINT which take an operand, adding a table to store operand names and
their matching hint number as well as encoding and decoding functions
for such operands. Parsing and printing the operands are deferred to any
support added for aliases with such operands.

include/opcode/
2015-12-11  Matthew Wahab  <matthew.wahab@arm.com>

	* aarch64.h (aarch64_hint_options): Declare.
	(aarch64_opnd_info): Add field hint_option.

opcodes/
2015-12-11  Matthew Wahab  <matthew.wahab@arm.com>

	* aarch64-asm.c (aarch64_ins_hint): New.
	* aarch64-asm.h (aarch64_ins_hint): Declare.
	* aarch64-dis.c (aarch64_ext_hint): New.
	* aarch64-dis.h (aarch64_ext_hint): Declare.
	* aarch64-opc-2.c: Regenerate.
	* aarch64-opc.c (aarch64_hint_options): New.
	* aarch64-tbl.h (AARCH64_OPERANDS): Fix typos.

Change-Id: I2205038fc1c47d3025d1f0bc2fbf405b5575b287


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [AArch64][Patch 1/5] Support the ARMv8.2 Statistical Profiling Extension.
@ 2015-12-17  1:57 sergiodj+buildbot
  2015-12-17  9:44 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-12-17  1:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 73af8ed6b107040eb7488f6ec122cd05d5e2e903 ***

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

[AArch64][Patch 1/5] Support the ARMv8.2 Statistical Profiling Extension.

The Statistical Profile extension included in the ARMv8.2 architecture
adds a number of system registers and a new instruction. This patch set
adds support for the extension to binutils, enabled when
-march=armv8.2-a+profile is given.

The patches in this series:
- Add the new command line option and feature flags.
- Add the new system registers.
- Adjust the maximum number of aliases permitted for an instruction.
- Add support for HINT aliases which take operands.
- Add the new instruction, an alias of the HINT instruction.

This patch adds the option "profile" to the permitted architecture
extensions, disabling it by default.

gas/
2015-12-11  Matthew Wahab  <matthew.wahab@arm.com>

	* config/tc-aarch64.c (aarch64_features): Add "profile".
	* doc/c-aarch64.texi (AArch64 Extensions): Add "profile".

include/opcode/
2015-12-11  Matthew Wahab  <matthew.wahab@arm.com>

	* aarch64.h (AARCH64_FEATURE_PROFILE): New.

Change-Id: If9bb4a9b69a264180f96f8ffaf10b15ced273699


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [Aarch64] Support ARMv8.2 AT instructions
@ 2015-12-17  1:31 sergiodj+buildbot
  2015-12-17  6:42 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-12-17  1:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 22a5455c6ccaf6157095863f9e6da33a81541acf ***

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

[Aarch64] Support ARMv8.2 AT instructions

ARMv8.2 adds new instructions AT S1E1RP and AT S1E1WP to Aarch64. This
patch adds support for the instructions, making them available when
-march=armv8.2-a is selected.

gas/testsuite/
2015-12-10  Matthew Wahab  <matthew.wahab@arm.com>

	* gas/aarch64/sysreg-2.d: Update for new tests for AT S1E1RP and
	AT S1E1WP.
	* gas/aarch64/sysreg-2.s: Add tests for AT S1E1RP and AT S1E1WP.

opcodes/
2015-12-10  Matthew Wahab  <matthew.wahab@arm.com>

	* aarch64-opc.c (aarch64_sys_regs_at): Add "s1e1rp" and "s1e1wp".
	(aarch64_sys_ins_reg_supported_p): Add ARMv8.2 system register
	feature test for "s1e1rp" and "s1e1wp".

Change-Id: I09e1044b629ab0a34b03c423e8d4e71ff92daad4


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Remove support for thread events without PTRACE_EVENT_CLONE in GDB
@ 2015-12-10 16:00 sergiodj+buildbot
  2015-12-10 19:06 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-12-10 16:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c2c2a31fdb228d41ce3db62b268efea04bd39c18 ***

Author: Antoine Tremblay <antoine.tremblay@ericsson.com>
Branch: master
Commit: c2c2a31fdb228d41ce3db62b268efea04bd39c18

Remove support for thread events without PTRACE_EVENT_CLONE in GDB

Before, on systems that did not support PTRACE_EVENT_CLONE, both GDB and
GDBServer coordinated with libthread_db.so to insert breakpoints at magic
locations in libpthread.so, in order to break at thread creation and
thread death.

Support for thread events was removed from GDBServer as patch:
https://sourceware.org/ml/gdb-patches/2015-11/msg00466.html

This patch removes support for thread events in GDB.

No regressions found on Ubuntu 14.04 x86_64.

gdb/ChangeLog:

	* breakpoint.c (remove_thread_event_breakpoints): Remove.
	* breakpoint.h (remove_thread_event_breakpoints): Remove
	declaration.
	* linux-nat.c (in_pid_list_p): Remove.
	(lin_lwp_attach_lwp): Remove.
	* linux-nat.h (lin_lwp_attach_lwp): Remove declaration.
	* linux-thread-db.c (thread_db_use_events): Remove.
	(struct thread_db_info) <td_create_bp_addr>: Remove.
	<td_death_bp_addr>: Likewise.
	<td_ta_event_addr_p>: Likewise.
	<td_ta_set_event_p>: Likewise.
	<td_ta_clear_event_p>: Likewise.
	<td_ta_event_getmsg_p>: Likewise.
	<td_thr_event_enable_p>: Likewise.
	(attach_thread): Likewise.
	(detach_thread): Likewise.
	(have_threads_callback): Likewise.
	(have_threads): Likewise.
	(enable_thread_event): Likewise.
	(enable_thread_event_reporting): Likewise.
	(try_thread_db_load_1): Remove td_ta_event_addr, td_ta_set_event,
	td_ta_clear_event, td_ta_event_getmsg, td_thr_event_enable
	initializations.
	(try_thread_db_load_1): Remove enable_thread_event_reporting call.
	(disable_thread_event_reporting): Remove.
	(record_thread): Adapt to thread_db_use_event removal.
	(detach_thread): Remove.
	(thread_db_detach): Adapt to thread_db_use_event removal.
	(check_event): Remove.
	(thread_db_wait): Adapt to thread events support removal.
	(thread_db_mourn_inferior): Likewise.
	(find_new_threads_callback): Likewise.
	(find_new_threads_once): Likewise.
	(thread_db_update_thread_list): Likewise.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [AArch64][PATCH 1/2] Add support for RAS instruction ESB.
@ 2015-12-10 14:57 sergiodj+buildbot
  2015-12-10 16:28 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-12-10 14:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c8a6db6fa0b06b978e5b63593a6b0cb3300ad259 ***

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

[AArch64][PATCH 1/2] Add support for RAS instruction ESB.

The ARMv8.2 RAS extension adds a new barrier instruction ESB as an alias
and the preferred form of HINT 16.

This patch adds an architectural feature flag for the RAS extension and
includes it in the features selected enabled by -march=armv8.2-a. It
also adds the ESB instruction, making it available whenever the RAS
feature is enabled.

Because ESB is the preferred form and because the target architecture
isn't available to the disassembler, HINT 16 will be disassembled as ESB
even when the target has no support for the RAS extension.

gas/testsuite/
2015-12-10  Matthew Wahab  <matthew.wahab@arm.com>

	* gas/aarch64/system-2.d: New.
	* gas/aarch64/system-2.s: New.
	* gas/aarch64/system.d: Adjust expected output for HINT 16.

include/opcode/
2015-12-10  Matthew Wahab  <matthew.wahab@arm.com>

	* aarch64.h (AARCH64_FEATURE_RAS): New.
	(AARCH64_ARCH_V8_2): Add AARCH64_FEATURE_RAS.

opcodes/
2015-12-10  Matthew Wahab  <matthew.wahab@arm.com>

	* aarch64-asm-2.c: Regenerate.
	* aarch64-dis-2.c: Regenerate.
	* aarch64-tbl.h (aarch64_feature_ras): New.
	(RAS): New.
	(aarch64_opcode_table): Add "esb".

Change-Id: Id4713917da15cca3b977284f43febd1c9b3d9faf


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] gdb: Handle multiple base address in debug_ranges data.
@ 2015-12-10 10:15 sergiodj+buildbot
  2015-12-10 11:05 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-12-10 10:15 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 28d2bfb9c3e519a3b7619bbe5d061ebe520750ef ***

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

gdb: Handle multiple base address in debug_ranges data.

It is possible to use multiple base addresses within a single address
range series, within the .debug_ranges section.  The following is a
simplified example for 32-bit addresses:

  .section ".debug_ranges"
  .4byte	0xffffffff
  .4byte	BASE_1
  .4byte	START_OFFSET_1
  .4byte	END_OFFSET_1
  .4byte	START_OFFSET_2
  .4byte	END_OFFSET_2
  .4byte	0xffffffff
  .4byte	BASE_2
  .4byte	START_OFFSET_3
  .4byte	END_OFFSET_3
  .4byte	0
  .4byte	0

In this example START/END 1 and 2 are relative to BASE_1, while
START/END 3 are relative to BASE_2.

Currently gdb does not correctly parse this DWARF, resulting in
corrupted address range information.  This commit fixes this issue, and
adds a new test to cover this case.

In order to support testing of this feature extensions were made to the
testsuite dwarf assembler, additional functionality was added to the
.debug_line generation function, and a new function for generating the
.debug_ranges section was added.

gdb/ChangeLog:

	* dwarf2read.c (dwarf2_ranges_read): Unify and fix base address
	reading code.

gdb/testsuite/ChangeLog:

	* gdb.dwarf2/dw2-ranges-base.c: New file.
	* gdb.dwarf2/dw2-ranges-base.exp: New file.
	* lib/dwarf.exp (namespace eval Dwarf): Add new variables to
	support additional line table, and debug ranges generation.
	(Dwarf::ranges): New function, generate .debug_ranges.
	(Dwarf::lines): Support generating simple line table programs.
	(Dwarf::assemble): Initialise new namespace variables.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
[parent not found: <8eab413676a0222a863f45ff606f3db69bb7afc4@gdb-build>]
* [binutils-gdb] rl78: Enable MULU for all ISAs.
@ 2015-12-08  5:32 sergiodj+buildbot
  2015-12-08  6:27 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-12-08  5:32 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1eac08cc37b3d8a42a1b81de888b29d079b0608e ***

Author: DJ Delorie <dj@redhat.com>
Branch: master
Commit: 1eac08cc37b3d8a42a1b81de888b29d079b0608e

rl78: Enable MULU for all ISAs.

Unlike other mul/div opcodes, MULU is available on all variants
of the RL78.

* rl78-decode.opc: Enable MULU for all ISAs.
* rl78-decode.c: Regenerate.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Support Z0 packet in AArch64 multi-arch debugging
@ 2015-12-07 16:13 sergiodj+buildbot
  2015-12-08  3:05 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-12-07 16:13 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 17b1509aac6ff4205749c2626fddbb1c4d7255f4 ***

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

Support Z0 packet in AArch64 multi-arch debugging

In commit 6085d6f6, Z0 packet is disabled in aarch64 GDBserver if
the inferior is 32-bit or there may be multiple inferiors, because
Z0 packet isn't supported for arm then.  Recently, Z0 packet
is supported in arm target, so we don't have such limitation in
aarch64 GDBserver, that is to say, aarch64 GDBserver can use Z0
packet in multi-arch/multi-inferior debugging when the inferior's
arch is arm.

Part of this patch is to revert 6085d6f6, and the rest of the patch
is to move some breakpoint related arm_* functions into
linux-aarch32-low.c in order to share them between arm and aarch64.

This patch is regression tested on aarch64-linux for debugging both
aarch64 programs and arm programs respectively.

gdb/gdbserver:

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

	* configure.srv: Append arm.o to srv_tgtobj for
	aarch64*-*-linux* target.
	* linux-aarch32-low.c (arm_abi_breakpoint): New macro.  Moved
	from linux-arm-low.c.
	(arm_eabi_breakpoint, arm_breakpoint): Likewise.
	(arm_breakpoint_len, thumb_breakpoint): Likewise.
	(thumb_breakpoint_len, thumb2_breakpoint): Likewise.
	(thumb2_breakpoint_len): Likewise.
	(arm_is_thumb_mode, arm_breakpoint_at): Likewise.
	(arm_breakpoint_kinds): Likewise.
	(arm_breakpoint_kind_from_pc): Likewise.
	(arm_sw_breakpoint_from_kind): Likewise.
	(arm_breakpoint_kind_from_current_state): Likewise.
	* linux-aarch32-low.h (arm_breakpoint_kind_from_pc): Declare.
	(arm_sw_breakpoint_from_kind): Declare.
	(arm_breakpoint_kind_from_current_state): Declare.
	(arm_breakpoint_at): Declare.
	* linux-aarch64-low.c (aarch64_sw_breakpoint_from_kind): Call
	arm_sw_breakpoint_from_kind if process is 32-bit.
	(aarch64_breakpoint_kind_from_pc): New function.
	(aarch64_breakpoint_kind_from_current_state): New function.
	(the_low_target): Initialize fields breakpoint_kind_from_pc
	and breakpoint_kind_from_current_state.
	* linux-arm-low.c (arm_breakpoint_kinds): Move to
	linux-aarch32-low.c.
	(arm_abi_breakpoint, arm_eabi_breakpoint): Likewise.
	(arm_breakpoint, arm_breakpoint_len): Likewise.
	(thumb_breakpoint, thumb_breakpoint_len): Likewise.
	(thumb2_breakpoint, thumb2_breakpoint_len): Likewise.
	(arm_is_thumb_mode): Likewise.
	(arm_breakpoint_at): Likewise.
	(arm_breakpoint_kind_from_pc): Likewise.
	(arm_sw_breakpoint_from_kind): Likewise.
	(arm_breakpoint_kind_from_current_state): Likewise.

	Revert:
	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] 1132+ messages in thread
* [binutils-gdb] Add support for MSP430 F5 hardware multiply.
@ 2015-12-07 10:29 sergiodj+buildbot
  2015-12-07 21:06 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-12-07 10:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f7584f0560f36189ef9434d157e83ffcd988c098 ***

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

Add support for MSP430 F5 hardware multiply.

	* msp430-sim.c (sim_open): Check for needed memory at address
	0x500 not 0x200.
	(get_op): Add support for F5 hardware multiply addresses.
	(put_op): Likewise.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Remove duplicate arch/arm.h include in linux-arm-low.c.
@ 2015-12-03 19:14 sergiodj+buildbot
  2015-12-04 11:08 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-12-03 19:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e58c48b4c81f25ec08174f324990d021aad0e96e ***

Author: Antoine Tremblay <antoine.tremblay@ericsson.com>
Branch: master
Commit: e58c48b4c81f25ec08174f324990d021aad0e96e

Remove duplicate arch/arm.h include in linux-arm-low.c.

A duplicate include arm/arm.h was introduced, remove it.
Pushed as obvious.

gdb/gdbserver/ChangeLog:

	* linux-arm-low.c: Remove duplicate arch/arm.h include.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Run gdb.base/disp-step-syscall.exp for aarch64-linux
@ 2015-12-01 12:47 sergiodj+buildbot
  2015-12-02  8:14 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-12-01 12:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 99fd02d9fc9d6cc470d3b81c4cc3439b47bb9419 ***

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

Run gdb.base/disp-step-syscall.exp for aarch64-linux

This patch handles target aarch64*-*-linux* for syscall instruction.

gdb/testsuite:

2015-12-01  Yao Qi  <yao.qi@linaro.org>

	* gdb.base/disp-step-syscall.exp: Define syscall instruction
	for aarch64*-*-linux* target.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Trim unused params from aout adjust_sizes_and_vmas
@ 2015-12-01  7:49 sergiodj+buildbot
  2015-12-02  7:16 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-12-01  7:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3a8c4a5b428c1babd941606c2bbe9cf8a041d9d9 ***

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

Trim unused params from aout adjust_sizes_and_vmas

	* aoutx.h (adjust_sizes_and_vmas): Remove unused text_size and
	text_end parameters.  Update callers.
	* aout-tic30.c: Update adjust_sizes_and_vmas callers.
	* hp300hpux.c: Likewise.
	* i386lynx.c: Likewise.
	* libaout.h: Likewise.
	* netbsd.h: Likewise.
	* pdp11.c: Likewise.
	* riscix.c: Likewise.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Fix instruction skipping when using software single step in GDBServer
@ 2015-12-01  4:06 sergiodj+buildbot
  2015-12-01 18:48 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-12-01  4:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2d97cd356e0f0320ecb71cf6a10616ba4618f318 ***

Author: Antoine Tremblay <antoine.tremblay@ericsson.com>
Branch: master
Commit: 2d97cd356e0f0320ecb71cf6a10616ba4618f318

Fix instruction skipping when using software single step in GDBServer

Without this patch, when doing a software single step, with for example
a conditional breakpoint, gdbserver would wrongly avance the pc of
breakpoint_len and skips an instruction.

This is due to gdbserver assuming that it's hardware single stepping.
When it resumes from the breakpoint address it expects the trap to be
caused by ptrace and if it's rather caused by a software breakpoint
it assumes this is a permanent breakpoint and that it needs to skip
over it.

However when software single stepping, this breakpoint is legitimate as
it's the reinsert breakpoint gdbserver has put in place to break at
the next instruction. Thus gdbserver wrongly advances the pc and skips
an instruction.

This patch fixes this behavior so that gdbserver checks if it is a
reinsert breakpoint from software single stepping. If it is it won't
advance the pc. And if there's no reinsert breakpoint there we assume
then that it's a permanent breakpoint and advance the pc.

Here's a commented log of what would happen before and after the fix on
gdbserver :

/* Here there is a conditional breakpoint at 0x10428 that needs to be
stepped over. */

Need step over [LWP 11204]? yes, found breakpoint at 0x10428
...
/* e7f001f0 is a breakpoint instruction on arm
   Here gdbserver writes the software breakpoint we would like to hit
*/
Writing e7f001f0 to 0x0001042c in process 11204
...
Resuming lwp 11220 (continue, signal 0, stop not expected)
  pending reinsert at 0x10428
stop pc is 00010428
  continue from pc 0x10428
...

/* Here gdbserver hit the software breakpoint that was in place
   for the step over */

stop pc is 0001042c
pc is 0x1042c
step-over for LWP 11220.11220 executed software breakpoint
Finished step over.
Could not find fast tracepoint jump at 0x10428 in list (reinserting).

/* Here gdbserver writes back the original instruction */
Writing e50b3008 to 0x0001042c in process 11220
Step-over finished.
Need step over [LWP 11220]? No

/* Here because gdbserver assumes this is a permenant breakpoint it advances
the pc of breakpoint_len, in this case 4 bytes, so we have just skipped
the instruction that was written back here :
Writing e50b3008 to 0x0001042c in process 11220
*/

stop pc is 00010430
pc is 0x10430
Need step over [LWP 11220]? No, no breakpoint found at 0x10430
Proceeding, no step-over needed
proceed_one_lwp: lwp 11220
stop pc is 00010430

This patch fixes this situation and we get the right behavior :

Writing e50b3008 to 0x0001042c in process 11245
Hit a gdbserver breakpoint.
Hit a gdbserver breakpoint.
Step-over finished.
proceeding all threads.
Need step over [LWP 11245]? No
stop pc is 0001042c
pc is 0x1042c
Need step over [LWP 11245]? No, no breakpoint found at 0x1042c
Proceeding, no step-over needed
proceed_one_lwp: lwp 11245
stop pc is 0001042c
pc is 0x1042c
Resuming lwp 11245 (continue, signal 0, stop not expected)
stop pc is 0001042c
  continue from pc 0x1042c

It also works if the value at 0x0001042c is a permanent breakpoint.
If so gdbserver will finish the step over, remove the reinserted breakpoint,
resume at that location and on the next SIGTRAP gdbserver will trigger
the advance PC condition as reinsert_breakpoint_inserted_here will be false.

I also tested this against bp-permanent.exp on arm (with a work in progress
software single step patchset) without any regressions.

It's also tested against x86 bp-permanent.exp without any regression.

So both software and hardware single step are tested.

No regressions on Ubuntu 14.04 on ARMv7 and x86.
With gdbserver-{native,extended} / { -marm -mthumb }

gdb/gdbserver/ChangeLog:

	* linux-low.c (linux_wait_1): Fix pc advance condition.
	* mem-break.c (reinsert_breakpoint_inserted_here): New function.
	* mem-break.h (reinsert_breakpoint_inserted_here): New declaration.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] SRC-POTFILES.in update
@ 2015-12-01  3:33 sergiodj+buildbot
  2015-12-02  1:02 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-12-01  3:33 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 44c2e680824714fcbdb1d8151f1b0e842b91d42a ***

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

SRC-POTFILES.in update

	* po/SRC-POTFILES.in: Regenerate.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Re: ARC port broken reloc processing
@ 2015-12-01  3:20 sergiodj+buildbot
  2015-12-01 23:58 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-12-01  3:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f26dd30880bad7f75b5ed1b1683628c7c986bb34 ***

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

Re: ARC port broken reloc processing

	* elf32-arc.c (ARC_ELF_HOWTO): Delete.
	(arc_elf_howto): New function.
	(bfd_elf32_bfd_reloc_type_lookup): Use it in place of existing
	init code.
	(bfd_elf32_bfd_reloc_name_lookup): Use arc_elf_howto.
	(arc_info_to_howto_rel, elf_arc_relocate_section): Likwise.
	(elf_arc_check_relocs): Likewise.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] gdbserver crash if gdb attaches too fast
@ 2015-11-30 22:32 sergiodj+buildbot
  2015-12-01  6:06 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-11-30 22:32 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 500c1d8576ad5a5bdc791fc7f7c3518a4d3f4b39 ***

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

gdbserver crash if gdb attaches too fast

With "maint set target-non-stop on", the attach tests occasionally
crash gdbserver.

Basically, gdb attaches with vAttach;PID, and then shortly after reads
the xml target description for that process, to figure out the
process' architecture.  On the gdbserver side, the target description
is only filled in when the first process/thread in the thread group
reports its initial PTRACE_ATTACH SIGSTOP.  So if GDB is fast enough,
it can read the target description _before_ that initial stop, and
then gdbserver dies dereferencing a NULL tdesc pointer.

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

	* linux-low.c (linux_attach): In non-stop mode, wait for one stop
	before returning.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Implement TARGET_WAITKIND_NO_RESUMED in the remote protocol
@ 2015-11-30 21:45 sergiodj+buildbot
  2015-12-01 13:04 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-11-30 21:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f2faf941ae49653ff6e1485adfee299313d47c91 ***

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

Implement TARGET_WAITKIND_NO_RESUMED in the remote protocol

Testing with "maint set target-non-stop on" causes regressions in
tests that rely on TARGET_WAITKIND_NO_RESUMED, which isn't modelled on
the RSP.  In real all-stop, gdbserver detects the situation and
reporst error to GDB, and so the tests (e.g.,
gdb.threads/no-unwaited-for-left.exp) at fail quickly.  But with
"maint set target-non-stop on", GDB instead hangs forever waiting for
a stop reply that never comes, and so the tests take longer to time
out.

This adds a new "N" stop reply packet that maps 1-1 to
TARGET_WAITKIND_NO_RESUMED.

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

	PR 14618
	* NEWS (New remote packets): Mention the N stop reply.
	* remote.c (remote_protocol_features): Add "no-resumed" entry.
	(remote_query_supported): Report no-resumed+ support.
	(remote_parse_stop_reply): Handle 'N'.
	(process_stop_reply): Handle TARGET_WAITKIND_NO_RESUMED.
	(remote_wait_as): Handle 'N' / TARGET_WAITKIND_NO_RESUMED.
	(_initialize_remote): Register "set/show remote
	no-resumed-stop-reply" commands.

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

	PR 14618
	* gdb.texinfo (Stop Reply Packets): Document the N stop reply.
	(Remote Configuration): Add the "set/show remote
	no-resumed-stop-reply" to the available settings table.
	(General Query Packets): Document the "no-resumed" qSupported
	feature.

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

	PR 14618
	* linux-low.c (linux_wait_1): If the last resumed thread is gone,
	report TARGET_WAITKIND_NO_RESUMED.
	* remote-utils.c (prepare_resume_reply): Handle
	TARGET_WAITKIND_NO_RESUMED.
	* server.c (report_no_resumed): New global.
	(handle_query) <qSupported>: Handle "no-resumed+".  Report
	"no-resumed+" support.
	(resume): When the target reports TARGET_WAITKIND_NO_RESUMED, only
	return error if the client doesn't support no-resumed events.
	(push_stop_notification): New function.
	(handle_target_event): Use it.  Report TARGET_WAITKIND_NO_RESUMED
	events if the client supports them.

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

	* gdb.threads/no-unwaited-for-left.exp: Remove setup_kfail calls.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Remote thread create/exit events
@ 2015-11-30 21:14 sergiodj+buildbot
  2015-12-01  9:02 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-11-30 21:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 65706a29bac50c2c971227a1945e46502845766b ***

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

Remote thread create/exit events

When testing with "maint set target-non-stop on", a few
threading-related tests expose an issue that requires new RSP packets.

Say there are 3 threads running, 1-3.  If GDB tries to stop thread 1,
2 and 3, and then waits for their stops, but meanwhile say, thread 2
exits, GDB hangs forever waiting for a stop for thread 2 that won't
ever happen.

This patch fixes the issue by adding support for thread exit events to
the protocol.  However, we don't want these always enabled, as they're
useless most of the time, and would slow down remote debugging.  So I
made it so that GDB can enable/disable them, and then made gdb do that
around the cases that need it, which currently is only
infrun.c:stop_all_threads.

In turn, if we have thread exit events, then the extra "thread x
exited" traffic slows down attach-many-short-lived-threads.exp enough
that gdb has trouble keeping up with new threads that are spawned
while gdb tries to stop existing ones.  To fix that I added support
for the counterpart thread created events too.  Enabling those when we
try to stop threads ensures that new threads never get a chance to
themselves start new threads, killing the race.

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

	* gdb.texinfo (Remote Configuration): List "set/show remote
	thread-events" command in configuration table.
	(Stop Reply Packets): Document "T05 create" stop
	reason and 'w' stop reply.
	(General Query Packets): Document QThreadEvents packet.  Document
	QThreadEvents qSupported feature.

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

	* linux-low.c (handle_extended_wait): Assert that the LWP's
	waitstatus is TARGET_WAITKIND_IGNORE.  If GDB wants to hear about
	thread create events, leave the new child's status pending.
	(linux_low_filter_event): If GDB wants to hear about thread exit
	events, leave the LWP marked dead and don't delete it.
	(linux_wait_for_event_filtered): Don't check for thread exit.
	(filter_exit_event): New function.
	(linux_wait_1): Use it, when returning an exit event.
	(linux_resume_one_lwp_throw): Assert that the LWP's
	waitstatus is TARGET_WAITKIND_IGNORE.
	* remote-utils.c (prepare_resume_reply): Handle
	TARGET_WAITKIND_THREAD_CREATED and TARGET_WAITKIND_THREAD_EXITED.
	* server.c (report_thread_events): New global.
	(handle_general_set): Handle QThreadEvents.
	(handle_query) <qSupported>: Handle and report QThreadEvents+;
	(handle_target_event): Handle TARGET_WAITKIND_THREAD_CREATED and
	TARGET_WAITKIND_THREAD_EXITED.
	* server.h (report_thread_events): Declare.

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

	* NEWS (New commands): Mention "set/show remote thread-events"
	commands.
	(New remote packets): Mention thread created/exited stop reasons
	and QThreadEvents packet.
	* infrun.c (disable_thread_events): New function.
	(stop_all_threads): Disable/enable thread create/exit events.
	Handle TARGET_WAITKIND_THREAD_EXITED.
	(handle_inferior_event_1): Handle TARGET_WAITKIND_THREAD_CREATED
	and TARGET_WAITKIND_THREAD_EXITED.
	* remote.c (remove_child_of_pending_fork): Also remove threads of
	threads that have TARGET_WAITKIND_THREAD_EXITED events.
	(remote_parse_stop_reply): Handle "create" magic register.  Handle
	'w' stop reply.
	(initialize_remote): Install remote_thread_events as
	to_thread_events target hook.
	(remote_thread_events): New function.
	* target-delegates.c: Regenerate.
	* target.c (target_thread_events): New function.
	* target.h (struct target_ops) <to_thread_events>: New field.
	(target_thread_events): Declare.
	* target/waitstatus.c (target_waitstatus_to_string): Handle
	TARGET_WAITKIND_THREAD_CREATED and TARGET_WAITKIND_THREAD_EXITED.
	* target/waitstatus.h (enum target_waitkind)
	<TARGET_WAITKIND_THREAD_CREATED, TARGET_WAITKIND_THREAD_EXITED):
	New values.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] remote: stop reason and watchpoint data address per thread
@ 2015-11-30 20:36 sergiodj+buildbot
  2015-12-01  4:14 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-11-30 20:36 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 799a2abe613be0645b84f5aaa050f2f91e6ae3f7 ***

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

remote: stop reason and watchpoint data address per thread

Running local-watch-wrong-thread.exp with "maint set target-non-stop
on" exposes that gdb/remote.c only records whether the target stopped
for a breakpoint/watchpoint plus the watchpoint data address *for the
last reported remote event*.  But in non-stop mode, we need to keep
that info per-thread, as each thread can end up with its own
last-status pending.

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

	* remote.c (struct remote_state) <remote_watch_data_address,
	stop_reason>: Delete fields.
	(struct private_thread_info) <stop_reason, watch_data_address>:
	New fields.
	(resume_clear_thread_private_info): New function.
	(append_pending_thread_resumptions): Call it.
	(remote_resume): Clear all threads' private info.
	(process_stop_reply): Adjust.
	(remote_wait_as): Don't reference remote_state's stop_reason
	field.
	(remote_stopped_by_sw_breakpoint)
	(remote_stopped_by_hw_breakpoint, remote_stopped_by_watchpoint)
	(remote_stopped_data_address): Adjust to refer get data from the
	current thread.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Adjust GDB to demangler API change
@ 2015-11-28 18:15 sergiodj+buildbot
  2015-11-29  5:04 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-11-28 18:15 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 16807a48edfdfe89c8f8f745edeb938ef0b7e5eb ***

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

Adjust GDB to demangler API change

Before commit 3a8724032abf, DEMANGLE_COMPONENT_CAST was used for both
casts and conversion operators.  We now have
DEMANGLE_COMPONENT_CONVERSION for the latter.

gdb/ChangeLog:
2014-11-28  Pedro Alves  <palves@redhat.com>

	* cp-name-parser.y (conversion_op): Use
	DEMANGLE_COMPONENT_CONVERSION instead of DEMANGLE_COMPONENT_CAST.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] SH FDPIC backend support
@ 2015-11-28 18:00 sergiodj+buildbot
  2015-11-29  2:01 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-11-28 18:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f4936735c5ed55abd37062791f60ba2754c89c31 ***

Author: Rich Felker <dalias@libc.org>
Branch: master
Commit: f4936735c5ed55abd37062791f60ba2754c89c31

SH FDPIC backend support

	gcc/ChangeLog
	* config.gcc: Handle --enable-fdpic.
	* config/sh/constraints.md (Ccl): New constraint.
	* config/sh/linux.h (SUBTARGET_LINK_EMUL_SUFFIX): Handle -mfdpic.
	* config/sh/sh-c.c (sh_cpu_cpp_builtins): Add __FDPIC__ and
	__SH_FDPIC__.
	* config/sh/sh-mem.cc (expand_block_move): Support FDPIC for calls
	to library functions.
	* config/sh/sh-protos.h (function_symbol_result): New struct.
	(function_symbol): Return function_symbol_result.
	(sh_get_fdpic_reg_initial_val, sh_load_function_descriptor): New
	declarations.
	* config/sh/sh.c (TARGET_ASM_INTEGER, sh_assemble_integer):
	Implement target hook.
 	(TARGET_CANNOT_FORCE_CONST_MEM, sh_cannot_force_const_mem_p):
	Likewise.
	(sh_option_override): Force -fPIC if FDPIC is in effect.
 	(sh_asm_output_addr_const_extra): Add UNSPEC_GOTFUNCDESC and
	UNSPEC_GOTOFFFUNCDESC cases.
	(prepare_move_operands): Use FDPIC initial GOT register for
	TLS-related GOT access; inhibit cross-section address offset
	constants for FDPIC.
	(sh_assemble_integer): New function.
	(sh_cannot_copy_insn_p): Inhibit copying insns that are FDPIC
	PC-relative call sites.
	(expand_ashiftrt): Adapt invocation of function_symbol.
	(sh_expand_prologue): Inhibit PC-relative GOT address load for
	FDPIC.
	(nonpic_symbol_mentioned_p): Add cases for UNSPEC_GOTFUNCDESC and
	UNSPEC_GOTOFFFUNCDESC.
	(legitimize_pic_address): Resolve function symbols to function
	descriptors for FDPIC.  Do not use GOT-relative addressing for
	local data that may be read-only on FDPIC.
	(sh_emit_storesi, sh_emit_storehi): New functions.
	(sh_trampoline_init): Generate FDPIC trampolines.
	(sh_function_ok_for_sibcall): Add TARGET_FDPIC check.
	(sh_expand_sym_label2reg): Don't assume sibcalls are local.
	(sh_output_mi_thunk): Generate FDPIC call.
	(function_symbol): Return function_symbol_result.  For
	SFUNC_STATIC on FDPIC, generate call site labels to use
	PC-relative addressing rather than GOT-relative addressing.
	(sh_conditional_register_usage): Make PIC register fixed and call used
	when FDPIC is in effect.
	(sh_legitimate_constant_p): Impose FDPIC
	constant constraints.
	(sh_cannot_force_const_mem_p, sh_load_function_descriptor)
	(sh_get_fdpic_reg_initial_val): New functions.
	* config/sh/sh.h (SUBTARGET_ASM_SPEC, SUBTARGET_LINK_EMUL_SUFFIX):
	Handle -mfdpic.
	(FDPIC_SELF_SPECS, SUBTARGET_DRIVER_SELF_SPECS)
	(PIC_OFFSET_TABLE_REG_CALL_CLOBBERED)
	(SH_OFFSETS_MUST_BE_WITHIN_SECTIONS_P): New macros.
	(DRIVER_SELF_SPECS): Add SUBTARGET_DRIVER_SELF_SPECS and
	FDPIC_SELF_SPECS.
	(TRAMPOLINE_SIZE): Select trampoline size for FDPIC.
	(ASM_PREFERRED_EH_DATA_FORMAT): Add EH format constraints for
	FDPIC.
	(ASM_MAYBE_OUTPUT_ENCODED_ADDR_RTX): Handle FDPIC case.
	* config/sh/sh.md (UNSPEC_GOTFUNCDESC, UNSPEC_GOTOFFFUNCDESC): New
	constants.
	(calli_fdpic, call_valuei_fdpic, sibcalli_fdpic)
	(sibcalli_pcrel_fdpic, sibcall_pcrel_fdpic, sibcall_valuei_fdpic)
	(sibcall_valuei_pcrel_fdpic, sibcall_value_pcrel_fdpic)
	(sym2GOTFUNCDESC, symGOTFUNCDESC2reg, sym2GOTOFFFUNCDESC)
	(symGOTOFFFUNCDESC2reg): New patterns.
	(udivsi3_i1, udivsi3_i4, udivsi3_i4_single, udivsi3,
	*divsi_inv_call_combine, divsi3_i4, divsi3_i4_single, divsi3)
	(ashlsi3, ashlsi3_d_call, ashrsi3_n, lshrsi3, lshrsi3_d_call)
	(calli, call_valuei, call, call_value, sibcalli, sibcalli_pcrel)
	(sibcall_pcrel, sibcall, sibcall_valuei, sibcall_valuei_pcrel)
	(sibcall_value_pcrel, sibcall_value, GOTaddr2picreg, symGOT_load)
	(symGOTOFF2reg, block_move_real, block_lump_real)
	(block_move_real_i4, block_lump_real_i4): Add support for FDPIC
	calls.
	(mulsi3, ic_invalidate_line, initialize_trampoline, call_pop,
	call_value_pop): Adjust for new function_symbol signature.
	* config/sh/sh.opt (-mfdpic): New option.
	* doc/install.texi (Options specification): Document
	--enable-fdpic.
	* doc/invoke.texi (SH Options): Document -mfdpic.

include/ChangeLog:
	* longlong.h (udiv_qrnnd): Add FDPIC compatible version for SH.

libitm/ChangeLog:
	* config/sh/sjlj.S (_ITM_beginTransaction): Bypass PLT calling
	GTM_begin_transaction for compatibility with FDPIC.

git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@229438 138bc75d-0d04-0410-961f-82ee72b054a4


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] PR other/61321 - demangler crash on casts in template parameters
@ 2015-11-28 17:44 sergiodj+buildbot
  2015-11-29  0:57 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-11-28 17:44 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c4be264168ee2f6c38b6b9b3db0a166441be478b ***

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

PR other/61321 - demangler crash on casts in template parameters

The fix for bug 59195:

 [C++ demangler handles conversion operator incorrectly]
 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59195

unfortunately makes the demangler crash due to infinite recursion, in
case of casts in template parameters.

For example, with:

 template<int> struct A {};
 template <typename Y> void function_temp(A<sizeof ((Y)(999))>) {}
 template void function_temp<int>(A<sizeof (int)>);

The 'function_temp<int>' instantiation above mangles to:

  _Z13function_tempIiEv1AIXszcvT_Li999EEE

The demangler parses this as:

typed name
  template
    name 'function_temp'
    template argument list
      builtin type int
  function type
    builtin type void
    argument list
      template                          (*)
        name 'A'
        template argument list
          unary operator
            operator sizeof
            unary operator
              cast
                template parameter 0    (**)
              literal
                builtin type int
                name '999'

And after the fix for 59195, due to:

 static void
 d_print_cast (struct d_print_info *dpi, int options,
	       const struct demangle_component *dc)
 {
 ...
   /* For a cast operator, we need the template parameters from
      the enclosing template in scope for processing the type.  */
   if (dpi->current_template != NULL)
     {
       dpt.next = dpi->templates;
       dpi->templates = &dpt;
       dpt.template_decl = dpi->current_template;
     }

when printing the template argument list of A (what should be "<sizeof
(int)>"), the template parameter 0 (that is, "T_", the '**' above) now
refers to the first parameter of the the template argument list of the
'A' template (the '*' above), exactly what we were already trying to
print.  This leads to infinite recursion, and stack exaustion.  The
template parameter 0 should actually refer to the first parameter of
the 'function_temp' template.

Where it reads "for the cast operator" in the comment in d_print_cast
(above), it's really talking about a conversion operator, like:

  struct A { template <typename U> explicit operator U(); };

We don't want to inject the template parameters from the enclosing
template in scope when processing a cast _expression_, only when
handling a conversion operator.

The problem is that DEMANGLE_COMPONENT_CAST is currently ambiguous,
and means _both_ 'conversion operator' and 'cast expression'.

Fix this by adding a new DEMANGLE_COMPONENT_CONVERSION component type,
which does what DEMANGLE_COMPONENT_CAST does today, and making
DEMANGLE_COMPONENT_CAST just simply print its component subtree.

I think we could instead reuse DEMANGLE_COMPONENT_CAST and in
d_print_comp_inner still do:

 @@ -5001,9 +5013,9 @@ d_print_comp_inner (struct d_print_info *dpi, int options,
        d_print_comp (dpi, options, dc->u.s_extended_operator.name);
        return;

     case DEMANGLE_COMPONENT_CAST:
       d_append_string (dpi, "operator ");
 -     d_print_cast (dpi, options, dc);
 +     d_print_conversion (dpi, options, dc);
       return;

leaving the unary cast case below calling d_print_cast, but seems to
me that spliting the component types makes it easier to reason about
the code.

g++'s testsuite actually generates three symbols that crash the
demangler in the same way.  I've added those as tests in the demangler
testsuite as well.

And then this fixes PR other/61233 too, which happens to be a
demangler crash originally reported to GDB, at:
https://sourceware.org/bugzilla/show_bug.cgi?id=16957

Bootstrapped and regtested on x86_64 Fedora 20.

Also ran this through GDB's testsuite.  GDB will require a small
update to use DEMANGLE_COMPONENT_CONVERSION in one place it's using
DEMANGLE_COMPONENT_CAST in its sources.

libiberty/
2015-11-27  Pedro Alves  <palves@redhat.com>

        PR other/61321
        PR other/61233
        * demangle.h (enum demangle_component_type)
        <DEMANGLE_COMPONENT_CONVERSION>: New value.
        * cp-demangle.c (d_demangle_callback, d_make_comp): Handle
        DEMANGLE_COMPONENT_CONVERSION.
        (is_ctor_dtor_or_conversion): Handle DEMANGLE_COMPONENT_CONVERSION
        instead of DEMANGLE_COMPONENT_CAST.
        (d_operator_name): Return a DEMANGLE_COMPONENT_CONVERSION
        component if handling a conversion.
        (d_count_templates_scopes, d_print_comp_inner): Handle
        DEMANGLE_COMPONENT_CONVERSION.
        (d_print_comp_inner): Handle DEMANGLE_COMPONENT_CONVERSION instead
        of DEMANGLE_COMPONENT_CAST.
        (d_print_cast): Rename as ...
        (d_print_conversion): ... this.  Adjust comments.
        (d_print_cast): Rewrite - simply print the left subcomponent.
        * cp-demint.c (cplus_demangle_fill_component): Handle
        DEMANGLE_COMPONENT_CONVERSION.

        * testsuite/demangle-expected: Add tests.

git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@231020 138bc75d-0d04-0410-961f-82ee72b054a4


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Avoid "enum conversion when passing argument 1 of 'getrusage' is invalid in C++" warning
@ 2015-11-28 16:50 sergiodj+buildbot
  2015-11-28 17:49 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-11-28 16:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT aaae08a7e4ac526975403ebb5f93b7f24ea16b90 ***

Author: Uros Bizjak <ubizjak@gmail.com>
Branch: master
Commit: aaae08a7e4ac526975403ebb5f93b7f24ea16b90

Avoid "enum conversion when passing argument 1 of 'getrusage' is invalid in C++" warning

 	* getruntime.c (get_run_time) [__USE_GNU]: Use RUSAGE_SELF as
 	argument 1 of getrusage call.

git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@225534 138bc75d-0d04-0410-961f-82ee72b054a4


^ permalink raw reply	[flat|nested] 1132+ messages in thread
[parent not found: <e19616610d7327664f99215a69cb326682742dc3@gdb-build>]
* [binutils-gdb] [AArch64][PATCH 1/3] Support ARMv8.2 FP16 floating point instructions.
@ 2015-11-27 19:07 sergiodj+buildbot
  2015-11-28 14:40 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-11-27 19:07 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3bd894a7147feacf6a8ab388b1b1e0d685abfcdc ***

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

[AArch64][PATCH 1/3] Support ARMv8.2 FP16 floating point instructions.

ARMv8.2 adds 16-bit floating point operations as an optional extension
to the ARMv8 FP support. This patch set adds support for the 16-bit FP
instructions to binutils, enabling the instructions when both +fp and
+fp16 architecture extensions are enabled.

The patches in this series:
- Add a feature macro for use by the encoding/decoding mechanism.
- Adjust a utility function, used when disassembling, to support 16-bit
  floating point values.
- Add the new scalar floating-point instructions.

This patch adds the feature macro FP_F16 to the AArch64 encoding/decoding
mechanism, enabling it when both +fp and +fp16 are selected.

opcodes/
2015-11-27  Matthew Wahab  <matthew.wahab@arm.com>

	* aarch64-tbl.h (aarch64_feature_fp_f16): New.
	(FP_F16): New.

Change-Id: Ie370e43e3d77a7d54b4416b4be901b363a37f3d5


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [AArch64] Add ARMv8.2 instructions BFC and REV64.
@ 2015-11-27 18:23 sergiodj+buildbot
  2015-11-28 14:18 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-11-27 18:23 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d685192a58d4c198633bd0e69cfe0a114576e98a ***

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

[AArch64] Add ARMv8.2 instructions BFC and REV64.

ARMv8.2 adds two new instructions: BFC as an alias for BFM and REV64 as
an alias for REV. This patch set adds support for these to binutils,
enabled when the -march=armv8.2-a is given. It depends on the support
for an instruction being its preferred form which was added in an
earlier patch.

This patch adds the alias BFC <Rd>, #<imm>, #<width> as the preferred
form for BFM when the source is a zero register and the conditions for
using the BFI form are met (in other words, BFC is the preferred form
for BFI <Rd>, <Rs>, #<imm>, #<width> when the <Rs> is a zero register).

gas/testsuite/
2015-11-27  Matthew Wahab  <matthew.wahab@arm.com>

	* gas/aarch64/alias-2.d: New.
	* gas/aarch64/alias-2.s: New.

include/opcode/
2015-11-27  Matthew Wahab  <matthew.wahab@arm.com>

	* aarch64.h (aarch64_op): Add OP_BFC.

opcodes/
2015-11-27  Matthew Wahab  <matthew.wahab@arm.com>

	* aarch64-asm-2.c: Regenerate.
	* aarch64-asm.c (convert_bfc_to_bfm): New.
	(convert_to_real): Add case for OP_BFC.
	* aarch64-dis-2.c: Regenerate.
	* aarch64-dis.c: (convert_bfm_to_bfc): New.
	(convert_to_alias): Add case for OP_BFC.
	* aarch64-opc-2.c: Regenerate.
	* aarch64-opc.c (operand_general_constraint_met_p): Weaken assert
	to allow width operand in three-operand instructions.
	* aarch64-tbl.h (QL_BF1): New.
	(aarch64_feature_v8_2): New.
	(ARMV8_2): New.
	(aarch64_opcode_table): Add "bfc".

Change-Id: I6efe318b2538ba11f0caece7c6d70957441c872b


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [AArch64] Only check breakpoint alignment on inserting
@ 2015-11-27 15:57 sergiodj+buildbot
  2015-11-27 22:48 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-11-27 15:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 805035d70cd8637c169caf97800accdd267d1d8e ***

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

[AArch64] Only check breakpoint alignment on inserting

This patch fixes the GDB internal error on AArch64 when running
watchpoint-fork.exp

 top?bt 15
 internal_error (file=file@entry=0x79d558 "../../binutils-gdb/gdb/linux-nat.c", line=line@entry=4866, fmt=0x793b20 "%s: Assertion `%s' failed.")
    at ../../binutils-gdb/gdb/common/errors.c:51
 #1  0x0000000000495bc4 in linux_nat_thread_address_space (t=<optimized out>, ptid=<error reading variable: Cannot access memory at address 0x1302>)
    at ../../binutils-gdb/gdb/linux-nat.c:4866
 #2  0x00000000005db2c8 in delegate_thread_address_space (self=<optimized out>, arg1=<error reading variable: Cannot access memory at address 0x1302>)
    at ../../binutils-gdb/gdb/target-delegates.c:2447
 #3  0x00000000005e8c7c in target_thread_address_space (ptid=<error reading variable: Cannot access memory at address 0x1302>)
    at ../../binutils-gdb/gdb/target.c:2727
 #4  0x000000000054eef8 in get_thread_arch_regcache (ptid=..., gdbarch=0xad51e0) at ../../binutils-gdb/gdb/regcache.c:529
 #5  0x000000000054efcc in get_thread_regcache (ptid=...) at ../../binutils-gdb/gdb/regcache.c:546
 #6  0x000000000054f120 in get_thread_regcache_for_ptid (ptid=...) at ../../binutils-gdb/gdb/regcache.c:560
 #7  0x00000000004a2278 in aarch64_point_is_aligned (is_watchpoint=0, addr=34168, len=2) at ../../binutils-gdb/gdb/nat/aarch64-linux-hw-point.c:122
 #8  0x00000000004a2e68 in aarch64_handle_breakpoint (type=hw_execute, addr=34168, len=2, is_insert=0, state=0xae8880)
    at ../../binutils-gdb/gdb/nat/aarch64-linux-hw-point.c:465
 #9  0x000000000048edf0 in aarch64_linux_remove_hw_breakpoint (self=<optimized out>, gdbarch=<optimized out>, bp_tgt=<optimized out>)
    at ../../binutils-gdb/gdb/aarch64-linux-nat.c:657
 #10 0x00000000005da8dc in delegate_remove_hw_breakpoint (self=<optimized out>, arg1=<optimized out>, arg2=<optimized out>)
    at ../../binutils-gdb/gdb/target-delegates.c:492
 #11 0x0000000000536a24 in bkpt_remove_location (bl=<optimized out>) at ../../binutils-gdb/gdb/breakpoint.c:13065
 #12 0x000000000053351c in remove_breakpoint_1 (bl=0xb3fe70, is=is@entry=mark_inserted) at ../../binutils-gdb/gdb/breakpoint.c:4026
 #13 0x000000000053ccc0 in detach_breakpoints (ptid=...) at ../../binutils-gdb/gdb/breakpoint.c:3930
 #14 0x00000000005a3ac0 in handle_inferior_event_1 (ecs=0x7ffffff048) at ../../binutils-gdb/gdb/infrun.c:5042

After the fork, GDB will physically remove the breakpoints from the child
process (in frame #14), but at that time, GDB doesn't create an inferior
yet for child, but inferior_ptid is set to child's ptid (in frame #13).
In aarch64_point_is_aligned, we'll get the regcache of current_lwp_ptid
to determine if the current process is 32-bit or 64-bit, so the inferior
can't be found, and the internal error is caused.

I don't find a better fix other than not checking alignment on removing
breakpoint.

gdb:

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

	* nat/aarch64-linux-hw-point.c (aarch64_dr_state_remove_one_point):
	Don't assert on alignment.
	(aarch64_handle_breakpoint): Only check alignment when IS_INSERT
	is true.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Use multi_line to make pattern more human readable
@ 2015-11-27 15:24 sergiodj+buildbot
  2015-11-27 18:45 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-11-27 15:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT dfcb77a8d78462af49ebc42b41d6fc504f4c2cf0 ***

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

Use multi_line to make pattern more human readable

gdb/testsuite:

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

	* gdb.cp/annota2.exp: Rewrite the pattern using multi_line.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] btrace: diagnose "record btrace pt" without libipt
@ 2015-11-26 10:35 sergiodj+buildbot
  2015-11-26 12:29 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-11-26 10:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 46a3515b49ce30315e2b621525b29cd8263aed15 ***

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

btrace: diagnose "record btrace pt" without libipt

If GDB has been configured without libipt support, i.e. HAVE_LIBIPT is
undefined, and is running on a system that supports Intel(R) Processor Trace,
GDB will run into an internal error when trying to decode the trace.

    (gdb) record btrace
    (gdb) s
    usage (name=0x7fffffffe954 "fib-64")
        at src/fib.c:12
    12          fprintf(stderr, "usage: %s <num>\n", name);
    (gdb) info record
    Active record target: record-btrace
    Recording format: Intel(R) Processor Trace.
    Buffer size: 16kB.
    gdb/btrace.c:971: internal-error: Unexpected branch trace format.
    A problem internal to GDB has been detected,
    further debugging may prove unreliable.
    Quit this debugging session? (y or n)

This requires a system with Linux kernel 4.1 or later running on a 5th
Generation Intel Core processor or later.

The issue is documented as PR 19297.

When trying to enable branch tracing, in addition to checking the target
support for the requested branch tracing format, also check whether GDB
supports. it.

gdb/
	* btrace.c (btrace_enable): Check whether HAVE_LIBIPT is defined.

testsuite/
	* lib/gdb.exp (skip_btrace_pt_tests): Check for a "GDB does not
	support" error.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] NEWS: "info" commands now list in ascending order
@ 2015-11-24 19:29 sergiodj+buildbot
  2015-11-25 15:18 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-11-24 19:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT be81798bb66a6f2d007983f466ba4fdeb7141578 ***

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

NEWS: "info" commands now list in ascending order

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

	* NEWS: Mention that a few "info" commands now list the
	corresponding items in ascending ID order.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Linux: dump the signalled thread first
@ 2015-11-24 18:58 sergiodj+buildbot
  2015-11-24 21:02 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-11-24 18:58 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 050c224b67b0cb62a5620d294997254d5b6675f9 ***

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

Linux: dump the signalled thread first

... like the kernel does.

gcore-thread.exp has a check to make sure the signalled thread is the
current thread after loading the core back, but that just works by
accident, because the signalled thread happened to be the last thread
on the thread list, and gdb currently iterates over threads in reverse
order.

So this fixes gcore-thread.exp once we start walking threads in
ascending number.

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

	* linux-tdep.c (find_stop_signal): Delete.
	(struct linux_corefile_thread_data) <pid>: Remove field.
	(linux_corefile_thread_callback): Rename to ...
	(linux_corefile_thread): ... this.  Now takes a struct
	linux_corefile_thread_data pointer rather than a void pointer.
	Remove thread state and thread pid checks.
	(linux_make_corefile_notes): Prefer dumping the signalled thread
	first.  Use ALL_NON_EXITED_THREADS instead of
	iterate_over_threads.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Refactor gdb.trace/save-trace.exp
@ 2015-11-24  0:05 sergiodj+buildbot
  2015-11-24 12:58 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-11-24  0:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 045ccf910b4345a1cfa9f3d3af20ae4d8d1defa2 ***

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

Refactor gdb.trace/save-trace.exp

Some code is duplicated, to run the test twice with absolute and
relative paths, so I factored it out in a few procs.  It uses
with_test_prefix to differentiate between test runs.

I replaced usages of "save-tracepoints" with "save tracepoint", since
the former is deprecated.

I also removed the "10.x", as it doesn't make much sense anymore.  It
isn't used in general in the testsuite, and I don't think it's really
useful.

gdb/testsuite/ChangeLog:

	* save-trace.exp: Factor out code to these...
	(gdb_save_tracepoints): New.
	(gdb_load_tracepoints): New.
	(do_save_load_test): New.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] minsyms.c: Scan backwards over all zero sized symbols.
@ 2015-11-23 23:05 sergiodj+buildbot
  2015-11-24  8:03 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-11-23 23:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5506f9f67ec105b0059a0b3a66fbde82cb5a0a15 ***

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

minsyms.c: Scan backwards over all zero sized symbols.

The comment for the code in question says:

		  /* If the minimal symbol has a zero size, save it
		     but keep scanning backwards looking for one with
		     a non-zero size.  A zero size may mean that the
		     symbol isn't an object or function (e.g. a
		     label), or it may just mean that the size was not
		     specified.  */

As written, the code in question will only scan past the first symbol
of zero size.  My change fixes the implementation to match the
comment.

Having this correct is important when the compiler generates several
local labels that are left in place by the linker.  (I've been told
that the linker should eliminate these symbols, but I know of one
architecture for which this is not happening.)

I've created a test case called asmlabel.c.  It's pretty simple:

main (int argc, char **argv)
{
  asm ("L0:");
  v = 0;
  asm ("L1:");
  v = 1;		/* set L1 breakpoint here */
  asm ("L2:");
  v = 2;		/* set L2 breakpoint here */
  return 0;
}

If breakpoints are placed on the lines indicated by the comments,
this is the behavior of GDB built without my patch:

    (gdb) continue
    Continuing.

    Breakpoint 2, L1 () at asmlabel.c:26
    26	  v = 1;		/* set L1 breakpoint here */

Note that L1 appears as the function instead of main.  This is not
what we want to happen.  With my patch in place, we see the desired
behavior instead:

    (gdb) continue
    Continuing.

    Breakpoint 2, main (argc=1, argv=0x7fffffffdb88) at asmlabel.c:26
    26	  v = 1;		/* set L1 breakpoint here */

gdb/ChangeLog:

	* minsyms.c (lookup_minimal_symbol_by_pc_section_1): Scan backwards
	over all zero-sized symbols.

gdb/testsuite/ChangeLog:

	* gdb.base/asmlabel.exp: New test.
	* gdb.base/asmlabel.c: New test case.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [LynxOS] GDBserver crash debugging threaded program
@ 2015-11-23 18:24 sergiodj+buildbot
  2015-11-23 23:05 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-11-23 18:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 80d82c196402f6a61aa84452104b9aaed364eb42 ***

Author: Joel Brobecker <brobecker@adacore.com>
Branch: master
Commit: 80d82c196402f6a61aa84452104b9aaed364eb42

[LynxOS] GDBserver crash debugging threaded program

This crash is observable by debugging a threaded program on LynxOS.
On the GDB side, this is what we would see:

    % gdb q
    (gdb) target remote machine:4444
    (gdb) break q.adb:6
    (gdb) cont
    [gdb hits breakpoint]
    (gdb) cont
    Remote connection closed    <<<--- expected: [Inferior 1 (Remote target) exited normally]

On the gdbserver side, which was launched as usual:

    % gdbserver --once :4444 q
    Segmentation fault (core dumped)

Ooops!

The problem happens while GDB is trying to handle the thread termination
event of the thread that hit the breakpoint. It started happening after
the following change was made:

    commit 96e7a1eb6d09fda9e22e112e35e7d0085a8f4fd0
    Date:   Fri Oct 16 11:08:38 2015 -0400
    Subject: gdbserver: Reset current_thread when the thread is removed.

    Reset current_thread and make sure 'remove_process' is used
    after all associated threads have been removed first.

More precisely:

  . GDBserver receives the execution-resume order;

  . lynx-low resumes it succesfully, and then relies on lynx_wait_1
    to wait for the next event;

  . We quickly receive one, which lynx_wait_1 analyzes to be
    a "thread exit" event, and therefore does...

          case SIGTHREADEXIT:
            remove_thread (find_thread_ptid (new_ptid));
            lynx_continue (new_ptid);
            goto retry;

    => remove_thread causes current_thread to be set to NULL...
       (that's the recent change mentioned above)

    => ... which causes problems during lynx_continue, because
       it calls lynx_resume, which calls regcache_invalidate,
       which unfortunately assumes that CURRENT_THREAD is not NULL:

        void
        regcache_invalidate (void)
        {
          /* Only update the threads of the current process.  */
SEGV!-->  int pid = ptid_get_pid (current_thread->entry.id);

          find_inferior (&all_threads, regcache_invalidate_one, &pid);
        }

Since the problem at hand is caused by trying to figure out which
inferior to reset the regcache for, and since lynx_resume actually
had that info, this patch fixes the problem by introducing a new
routine called regcache_invalidate_pid, which invalidates the cache
of the given pid; and then modifies lynx_resume use that new routine
rather than relying on regcache_invalidate to invalidate the regcache
of the expected inferior.

gdb/gdbserver/ChangeLog:

        * regcache.h (regcache_invalidate_pid): Add declaration.
        * regcache.c (regcache_invalidate_pid): New function, extracted
        from regcache_invalidate.
        (regcache_invalidate): Reimplement using regcache_invalidate_pid.
        Add trivial documentation comment.
        * lynx-low.c: Use regcache_invalidate_pid instead of
        regcache_invalidate.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [gdbserver] disable Elf32_auxv_t/Elf64_auxv_t AC_CHECK_TYPES check on Android
@ 2015-11-23 18:03 sergiodj+buildbot
  2015-11-23 19:54 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-11-23 18:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 64da5dd5eaa60269a8070e0bdb740b3b2c6e9740 ***

Author: Joel Brobecker <brobecker@adacore.com>
Branch: master
Commit: 64da5dd5eaa60269a8070e0bdb740b3b2c6e9740

[gdbserver] disable Elf32_auxv_t/Elf64_auxv_t AC_CHECK_TYPES check on Android

See the comment added in configure.ac for more details behind
this change.

gdb/gdbserver/ChangeLog:

        * configure.ac: Do not call AC_CHECK_TYPES for Elf32_auxv_t
        and Elf64_auxv_t if the target is Android.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] darwin-nat: disable sstep cache.
@ 2015-11-23 14:42 sergiodj+buildbot
  2015-11-23 16:01 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-11-23 14:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT aa14fb50785c8ac8be5fbb148d7cdd88fcf8f896 ***

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

darwin-nat: disable sstep cache.

Was not reliable after inferior call.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] target.h: #include <sys/types.h>.
@ 2015-11-23  1:38 sergiodj+buildbot
  2015-11-23 10:41 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-11-23  1:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 37ce4055fe907b9edd25498dcda7a133dbd19784 ***

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

target.h: #include <sys/types.h>.

For musl.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] sim: ppc: avoid use of $< in ordinary rules [PR sim/13834]
@ 2015-11-22  7:11 sergiodj+buildbot
  2015-11-22 13:07 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-11-22  7:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7c125e3b10ac6f9222d24c76cdf31a5a9ec8dae0 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 7c125e3b10ac6f9222d24c76cdf31a5a9ec8dae0

sim: ppc: avoid use of $< in ordinary rules [PR sim/13834]

POSIX does not define $< behavior in ordinary rules, so avoid its use
to fix building on non-GNU make setups.

Reported-by: Christopher January <chris.january@allinea.com>


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] sim: sh: delete global callback/argv
@ 2015-11-22  7:00 sergiodj+buildbot
  2015-11-22  9:05 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-11-22  7:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6cc98856315993e8723fc2c6a2baabd8dc7fd360 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 6cc98856315993e8723fc2c6a2baabd8dc7fd360

sim: sh: delete global callback/argv

We can use the sim state everywhere now to get these values on the fly.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] sim: common: add PRI printf defines
@ 2015-11-22  6:50 sergiodj+buildbot
  2015-11-22 12:08 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-11-22  6:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 37258e9950490293bb00808a55d82dea640efe6c ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 37258e9950490293bb00808a55d82dea640efe6c

sim: common: add PRI printf defines

Keeping track of the right printf formats for the various types can be
a pretty big hassle, especially in common code which has to support a
variety of bitsizes.  Take a page from the existing standards and add
a set of PRI macros which hide the details in a common header.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] sim: mn10300: drop global callback handle
@ 2015-11-22  6:11 sergiodj+buildbot
  2015-11-22  7:04 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-11-22  6:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d320201dbe5a3677e96008738cb6cc754147e3bd ***

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

sim: mn10300: drop global callback handle

It's used in one place and can easily be replaced by using the sim state.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [AArch64] Add support for ARMv8.1 Virtulization Host Extensions.
@ 2015-11-20 16:23 sergiodj+buildbot
  2015-11-21  6:03 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-11-20 16:23 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 250aafa4773feafd5ca0a61f270b1e901dcd8987 ***

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

[AArch64] Add support for ARMv8.1 Virtulization Host Extensions.

The ARMv8.1 architecture includes the Virtualization Host Extensions
which add a number of system registers. This patch adds support for
these system registers, making them available when -march=armv8.1-a is
selected.

include/opcode/
2015-11-20  Matthew Wahab  <matthew.wahab@arm.com>

	* aarch64.h (AARCH64_FEATURE_V8_1): New.
	(AARCH64_ARCH_v8_1): Add AARCH64_FEATURE_V8_1.

opcodes/
2015-11-20  Matthew Wahab  <matthew.wahab@arm.com>

	* aarch64-opc.c (aarch64_sys_regs): Add spsr_el12, elr_el12,
	sctlr_el12, cpacr_el12, ttbr1_el2, ttbr0_el12, ttbr1_el12,
	tcr_el12, afsr0_el12, afsr1_el12, esr_el12, far_el12, mair_el12,
	amair_el12, vbar_el12, contextidr_el2, contextidr_el12,
	cntkctl_el12, cntp_tval_el02, cntp_ctl_el02, cntp_cval_el02,
	cntv_tval_el02, cntv_ctl_el02, cntv_cval_el02, cnthv_tval_el2,
	cnthv_ctl_el2, cnthv_cval_el2.
	(aarch64_sys_reg_supported_p): Update for the new system
	registers.

gas/testsuite/
2015-11-20  Matthew Wahab  <matthew.wahab@arm.com>

	* gas/aarch64/virthostext-directive.d: New.
	* gas/aarch64/virthostext.d: New.
	* gas/aarch64/virthostext.s: New.

Change-Id: Iecb370591b1b6e9e00d81c8ccd9ae3b0f71794a2


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] binutils: add support for arm-*-darwin and aarch64-*-darwin.
@ 2015-11-20 14:07 sergiodj+buildbot
  2015-11-21  0:37 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-11-20 14:07 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f075eb5e6b0dd850304f78cf4d5c94df7b44c7a3 ***

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

binutils: add support for arm-*-darwin and aarch64-*-darwin.

Currently only in bfd and binutils.

ChangeLog/
	* configure.ac: Add aarch64-*-darwin* and arm-*-darwin*.
	* configure: Regenerate.

bfd/ChangeLog/
	* targets.c (aarch64_mach_o_vec, arm_mach_o_vec): Declare.
	(_bfd_target_vector): Add new vectors.
	* reloc.c (BFD_RELOC_MACH_O_SUBTRACTOR32)
	(BFD_RELOC_MACH_O_SUBTRACTOR64, BFD_RELOC_MACH_O_ARM64_ADDEND)
	(BFD_RELOC_MACH_O_ARM64_GOT_LOAD_PAGE21)
	(BFD_RELOC_MACH_O_ARM64_GOT_LOAD_PAGEOFF12)
	(BFD_RELOC_MACH_O_ARM64_POINTER_TO_GOT): New relocations.
	(BFD_RELOC_MACH_O_X86_64_SUBTRACTOR32)
	(BFD_RELOC_MACH_O_X86_64_SUBTRACTOR64): Remove.
	* mach-o-x86-64.c (bfd_mach_o_x86_64_swap_reloc_out): Change
	name of subtractor relocations.
	* config.bfd: Handle aarch64-*-darwin*, arm-*-darwin*.
	* Makefile.am (BFD32_BACKENDS): Add mach-o-arm.lo.
	(BFD32_BACKENDS_CFILES): Add mach-o-arm.c.
	(BFD64_BACKENDS): Add mach-o-aarch64.lo.
	(BFD64_BACKENDS_CFILES): Add mach-o-aarch64.c.
	* configure.ac: Handle aarch64_mach_o_vec and arm_mach_o_vec.
	* mach-o-aarch64.c: New file.
	* mach-o-arm.c: New file.
	* Makefile.in: Regenerate.
	* bfd-in2.h: Regenerate.
	* configure: Regenerate.
	* libbfd.h: Regenerate.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
[parent not found: <bb82e93484cdd56c67efd52b869a6123b2623f6c@gdb-build>]
* [binutils-gdb] Synchronize PDP11 page size between BFD and LD.
@ 2015-11-20 13:08 sergiodj+buildbot
  2015-11-21  0:31 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-11-20 13:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 11b8aeb88174dd67ff8b7c58377e8ef94ccf274e ***

Author: David Bridgham <dab@froghouse.org>
Branch: master
Commit: 11b8aeb88174dd67ff8b7c58377e8ef94ccf274e

Synchronize PDP11 page size between BFD and LD.

	* pdp11.c (TARGET_PAGE_SIZE): Set to 256 to match definition in
	ld/emulparams/pdp11.sh.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] callfuncs.exp: avoid spurious register differences in sparc64 targets.
@ 2015-11-20 10:38 sergiodj+buildbot
  2015-11-20 22:46 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-11-20 10:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bb0974456ed6d421e8d0b257f1e108c242326afc ***

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

callfuncs.exp: avoid spurious register differences in sparc64 targets.

The Linux kernel disables the FPU upon returning to userland.  This
introduces spurious failures in the register preservation tests in
callfuncs.exp, since the pstate.PEF bit gets cleared after system
calls.

This patch filters out the pstate register in sparc64-*-linux-gnu
targets, so the relevant tests are no longer fooled and pass.

gdb/testsuite/ChangeLog:

2015-11-20  Jose E. Marchesi  <jose.marchesi@oracle.com>

        * gdb.base/callfuncs.exp (fetch_all_registers): Filter out the
          pstate register when comparing registers values in
          sparc64-*-linux-gnu targets to avoid spurious differences.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [C++] Drop -fpermissive hack
@ 2015-11-19 17:51 sergiodj+buildbot
  2015-11-20  0:24 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-11-19 17:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT dad44a1fbaa460e5ff80ce203196bc1c1317dc60 ***

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

[C++] Drop -fpermissive hack

Both x86_64 GNU/Linux and x86_64 mingw-w64 build cleanly with
--enable-targets=all.  Let's drop the -fpermissive hack, in order to
let the buildbot catch C++ build regressions for us.

gdb/ChangeLog:
2015-11-19  Pedro Alves  <palves@redhat.com>

	* build-with-cxx.m4 (GDB_AC_BUILD_WITH_CXX): Remove -fpermissive.
	* configure: Regenerate.

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

	* configure: Regenerate.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [C++] Default to -Werror in C++ mode too
@ 2015-11-19 15:28 sergiodj+buildbot
  2015-11-20  9:45 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-11-19 15:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9a0847060d5823ec520ebf0c3e307e26442e5b8c ***

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

[C++] Default to -Werror in C++ mode too

Both x86_64 GNU/Linux and x86_64 mingw-w64 build cleanly with
--enable-targets=all.  This enables -Werror by default in C++ mode
too, in order to let the buildbot catch C++ build regressions for us.

gdb/ChangeLog:
2015-11-19  Pedro Alves  <palves@redhat.com>

	* configure.ac (ERROR_ON_WARNING): Don't check whether in C++
	mode.
	* configure: Regenerate.

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

	* configure.ac (ERROR_ON_WARNING): Don't check whether in C++
	mode.
	* configure: Regenerate.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Define enum out of the scope of struct
@ 2015-11-19 14:27 sergiodj+buildbot
  2015-11-19 17:05 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-11-19 14:27 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6c1c9a8bbd2aa3fbc627525b452e7dbbaf40efc5 ***

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

Define enum out of the scope of struct

This patch moves the enum definition out of the scope of struct, and
fixes the following error.

gdb/gdbserver/linux-aarch64-low.c:681:18: error: 'OPERAND_REGISTER' was not declared in this scope
   operand.type = OPERAND_REGISTER;
                  ^
gdb/gdbserver:

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

	* linux-aarch64-low.c (enum aarch64_operand_type): New.
	(struct aarch64_operand): Move enum out.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [S/390] Add null ptr check + port GOTOFF handling from 32 bit over to 64 bit
@ 2015-11-19 10:20 sergiodj+buildbot
  2015-11-19 12:52 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-11-19 10:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d47b13e0e2286ef9e9444292bc5631f43cf226da ***

Author: Andreas Krebbel <krebbel@linux.vnet.ibm.com>
Branch: master
Commit: d47b13e0e2286ef9e9444292bc5631f43cf226da

[S/390] Add null ptr check + port GOTOFF handling from 32 bit over to 64 bit

bfd/ChangeLog:

2015-11-19  Andreas Krebbel  <krebbel@linux.vnet.ibm.com>

	PR ld/19263
	* elf32-s390.c (elf_s390_gc_sweep_hook): Add null ptr check.
	* elf64-s390.c (elf_s390_check_relocs): Port the GOTOFF handling
	over from the 32 bit code.
	(elf_s390_relocate_section): Likewise.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Constify value_string
@ 2015-11-18 16:29 sergiodj+buildbot
  2015-11-18 19:29 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-11-18 16:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7cc3f8e23b5c19a50722adefce986230b191e9cd ***

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

Constify value_string

If we constify value_cstring, we might as well constify this one.

gdb/ChangeLog:

	* valops.c (value_string): Constify 'ptr' parameter.
	* value.h (value_string): Constify 'ptr' parameter.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] mach-o: use a per-target reloc canonicalize function.
@ 2015-11-18 14:59 sergiodj+buildbot
  2015-11-18 16:11 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-11-18 14:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bcb51645d3ef1211efbce59f0935f5f0223602a3 ***

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

mach-o: use a per-target reloc canonicalize function.

bfd/
	* mach-o.h (bfd_mach_o_swap_in_non_scattered_reloc)
	(bfd_mach_o_canonicalize_non_scattered_reloc)
	(bfd_mach_o_pre_canonicalize_one_reloc): Declare.
	(bfd_mach_o_backend_data): Rename field
	_bfd_mach_o_swap_reloc_in to _bfd_mach_o_canonicalize_one_reloc.
	* mach-o.c (bfd_mach_o_swap_in_non_scattered_reloc): Now public.
	(bfd_mach_o_canonicalize_non_scattered_reloc): Renames from
	bfd_mach_o_canonicalize_one_reloc.
	(bfd_mach_o_pre_canonicalize_one_reloc): New function.
	(bfd_mach_o_canonicalize_relocs): Adjust.
	(bfd_mach_o_canonicalize_relocs): Rename define from
	bfd_mach_o_swap_reloc_in.
	* mach-o-target.c (TARGET_NAME_BACKEND): Use
	bfd_mach_o_canonicalize_one_reloc instead of
	bfd_mach_o_swap_reloc_in.
	* mach-o-i386.c (bfd_mach_o_i386_canonicalize_one_reloc): Renames
	from bfd_mach_o_i386_swap_reloc_in and adjust.
	(bfd_mach_o_canonicalize_one_reloc): Renames from
	bfd_mach_o_i386_canonicalize_one_reloc.
	* mach-o-x86_64.c (bfd_mach_o_x86_64_canonicalize_one_reloc): Renames
	from bfd_mach_o_x86_64_swap_reloc_in and adjust.
	(bfd_mach_o_canonicalize_one_reloc): Renames from
	bfd_mach_o_x86_64_canonicalize_one_reloc.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Fix out of boundary access in pass_in_v
@ 2015-11-18 12:02 sergiodj+buildbot
  2015-11-18 12:37 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-11-18 12:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0735fdddbc086291f6d2357e8fa57e5df6095e89 ***

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

Fix out of boundary access in pass_in_v

Hi,
I build GDB with -fsanitize=address, and run testsuite.  In
gdb.base/callfuncs.exp, I see the following error,

p t_float_values(0.0,0.0)
=================================================================
==8088==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x6020000cb650 at pc 0x6e195c bp 0x7fff164f9770 sp 0x7fff164f9768
READ of size 16 at 0x6020000cb650 thread T0^
    #0 0x6e195b in regcache_raw_write /home/yao/SourceCode/gnu/gdb/git/gdb/regcache.c:912
    #1 0x6e1e52 in regcache_cooked_write /home/yao/SourceCode/gnu/gdb/git/gdb/regcache.c:945
    #2 0x466d69 in pass_in_v /home/yao/SourceCode/gnu/gdb/git/gdb/aarch64-tdep.c:1101
    #3 0x467512 in pass_in_v_or_stack /home/yao/SourceCode/gnu/gdb/git/gdb/aarch64-tdep.c:1196
    #4 0x467d7d in aarch64_push_dummy_call /home/yao/SourceCode/gnu/gdb/git/gdb/aarch64-tdep.c:1335

The code in pass_in_v read contents from V registers (128 bit), but the
data passed through V registers can be less than 128 bit.  In this case,
float is passed.  So writing V registers contents into contents buff
will cause overflow.  In this patch, we add an array reg[V_REGISTER_SIZE],
which is to hold the contents from V registers, and then copy useful
bits to buf.

gdb:

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

	* aarch64-tdep.c (pass_in_v): Add argument len.  Add local array
	reg.  Callers updated.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Prevent looping in archives
@ 2015-11-18 11:52 sergiodj+buildbot
  2015-11-18 12:17 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-11-18 11:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4978e369fb75a8b7756bf4201668b2a9d9556286 ***

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

Prevent looping in archives

	PR 19256
	* archive.c (bfd_generic_openr_next_archived_file): Don't allow
	backward file movement via "negative" sizes.
	* coff-alpha.c (alpha_ecoff_openr_next_archived_file): Likewise.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] mach-o cleanup: remove useless calls to bfd_seek.
@ 2015-11-18 11:42 sergiodj+buildbot
  2015-11-18 12:02 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-11-18 11:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 47daa70fe08c57aaafa6fe1a7e762072909d0f8f ***

Author: Tristan Gingold <gingold@adacore.com>
Branch: master
Commit: 47daa70fe08c57aaafa6fe1a7e762072909d0f8f

mach-o cleanup: remove useless calls to bfd_seek.

Also support new commands.

bfd/
	* mach-o.h (struct mach_o_data_struct): Add hdr_offset field.
	(bfd_mach_o_fat_archive_p): Renames prototype.
	(bfd_mach_o_fat_openr_next_archived_file): Renames.
	(bfd_mach_o_header_p): Add argument.
	* mach-o.c (bfd_mach_o_read_header): Add hdr_off argument and
	use it.
	(bfd_mach_o_read_section_32, bfd_mach_o_read_section_64)
	(bfd_mach_o_read_section): Remove offset argument.
	(bfd_mach_o_read_dylinker): Remove bfd_seek call.
	(bfd_mach_o_read_dylib, bfd_mach_o_read_prebound_dylib)
	(bfd_mach_o_read_prebind_cksum, bfd_mach_o_read_twolevel_hints)
	(bfd_mach_o_read_fvmlib, bfd_mach_o_read_dysymtab)
	(bfd_mach_o_read_symtab, bfd_mach_o_read_uuid)
	(bfd_mach_o_read_linkedit, bfd_mach_o_read_str)
	(bfd_mach_o_read_dyld_info, bfd_mach_o_read_version_min)
	(bfd_mach_o_read_encryption_info): Likewise.
	(bfd_mach_o_read_encryption_info_64): New function.
	(bfd_mach_o_read_main, bfd_mach_o_read_source_version)
	(bfd_mach_o_read_segment): Remove call to bfd_seek.
	(bfd_mach_o_read_command): Use hdr_offset in bfd_seek.
	Handle BFD_MACH_O_LC_LINKER_OPTIMIZATION_HINT,
	BFD_MACH_O_LC_ENCRYPTION_INFO_64, BFD_MACH_O_LC_VERSION_MIN_WATCHOS.
	(bfd_mach_o_header_p): Add hdr_off argument.
	(bfd_mach_o_gen_object_p, bfd_mach_o_gen_core_p): Adjust calls.
	(bfd_mach_o_fat_archive_p): Renames.
	(bfd_mach_o_fat_openr_next_archived_file): Renames.
	(bfd_mach_o_close_and_cleanup): Remove useless code.
	(bfd_mach_o_close_and_cleanup): Define.
	* mach-o-x86-64.c (bfd_mach_o_x86_64_object_p)
	(bfd_mach_o_x86_64_core_p): Adjust calls.
	* mach-o-target.c: Move defines for archive from mach-o.c.
	Remove check on TARGET_ARCHIVE.
	* mach-o-i386.c (bfd_mach_o_i386_object_p)
	(bfd_mach_o_i386_core_p): Adjust calls.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] sim: mn10300/v850: drop unused WITH_CORE define
@ 2015-11-18  4:25 sergiodj+buildbot
  2015-11-18 10:40 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-11-18  4:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c389945b7a470aa328972026fe4a836c57ccb7ae ***

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

sim: mn10300/v850: drop unused WITH_CORE define

This was dropped from the sim core in 1997, so no point in having these
sim ports continue to define it.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] sim: always enable modulo memory
@ 2015-11-18  4:18 sergiodj+buildbot
  2015-11-18 10:02 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-11-18  4:18 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cdf850e9d953f765f600e1ecae61664eab5ae7f1 ***

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

sim: always enable modulo memory

Having this be a config option doesn't make sense: the code size is
pretty much the same (as all the logic is still active), and if it's
disabled, the sim throws an error if you try to use it.  That means
we can't break sims that weren't using it before by enabling it all
the time.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [sim/ppc] Fix printf_filtered reference
@ 2015-11-17 21:29 sergiodj+buildbot
  2015-11-18  9:44 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-11-17 21:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a6760b615451518704601cae9327d333fe4bec57 ***

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

[sim/ppc] Fix printf_filtered reference

Building a gdb that includes the PPC sim in C++ mode fails to link with:

(...)s.o compile-object-load.o compile-object-run.o compile-loc2c.o compile-c-support.o inflow.o    init.o \
          ../sim/ppc/libsim.a ../readline/libreadline.a ../opcodes/libopcodes.a ../bfd/libbfd.a -lz  ../libiberty/libiberty.a ../libdecnumber/libdecnumber.a    -ldl -ldl -lncurses -lm -ldl  -lguile-2.0 -lgc  -lpthread -ldl -lutil -lm -lpython2.7 -Xlinker -export-dynamic -lexpat -llzma -lbabeltrace -lbabeltrace-ctf  ../libiberty/libiberty.a  build-gnulib/import/libgnu.a
../sim/ppc/libsim.a(sim_calls.o): In function `sim_open':
/home/pedro/gdb/mygit/cxx-convertion/src/sim/ppc/sim_calls.c:73: undefined reference to `printf_filtered'
/home/pedro/gdb/mygit/cxx-convertion/src/sim/ppc/sim_calls.c:73: undefined reference to `printf_filtered'
../sim/ppc/libsim.a(sim_calls.o): In function `sim_close':
/home/pedro/gdb/mygit/cxx-convertion/src/sim/ppc/sim_calls.c:93: undefined reference to `printf_filtered'
/home/pedro/gdb/mygit/cxx-convertion/src/sim/ppc/sim_calls.c:93: undefined reference to `printf_filtered'
../sim/ppc/libsim.a(sim_calls.o): In function `sim_load':
/home/pedro/gdb/mygit/cxx-convertion/src/sim/ppc/sim_calls.c:102: undefined reference to `printf_filtered'
../sim/ppc/libsim.a(sim_calls.o):/home/pedro/gdb/mygit/cxx-convertion/src/sim/ppc/sim_calls.c:102: more undefined references to `printf_filtered' follow
collect2: error: ld returned 1 exit status

The undefined references come from TRACE macro calls, which expand to
calls to printf_filtered.

But note that the sim's 'printf_filtered' is actually a #define to
'sim_io_printf_filtered', in sim_callbacks.h :

 #define printf_filtered sim_io_printf_filtered

AFAICS, this is not meant to call gdb's printf_filtered function.  The
ChangeLog entry that added the printf_filtered macro reads:

 Tue Jul 30 21:12:24 1996  Andrew Cagney  <cagney@kremvax.highland.com.au>

	 * sim_callbacks.h (sim_io_printf_filtered): Replace
	 printf_filtered with a local simulator specific version.  Add
	 #define printf_filtered to simplify updating of existing code.

That is, just another incomplete/partial transition.  Maybe prior to
1996 this was really meant to call gdb's printf_filtered version.

The reference to printf_filtered appears because sim_calls.c, the
compilation unit that fails to link, has this at the top:

 #undef printf_filtered /* blow away the mapping */

presumably so that this further below:

 void
 sim_io_printf_filtered(const char *fmt,
			...)
 {
   (...)
   callbacks->printf_filtered(callbacks, "%s", message);
 }

works.  So those TRACE macros instances in sim_calls.c just happen to
work because gdb is linked in, which satisfies the 'printf_filtered'
reference, when GDB is built in C mode.  When built in C++ mode, the
problem is exposed, as GDB's printf_filtered is mangled.

The fix here is to make the TRACE macro call sim_io_printf_filtered
directly.

(Standalone "run" doesn't fail to link simply because the offending
routines are not part of its link.)

sim/ppc/ChangeLog
2015-11-17  Pedro Alves  <palves@redhat.com>

	* debug.h (TRACE, ITRACE, DTRACE, DITRACE, PTRACE): Call
	sim_io_printf_filtered instead of printf_filtered.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Fix gdb.threads/multiple-step-overs.exp fails on arm
@ 2015-11-17 17:26 sergiodj+buildbot
  2015-11-18  9:26 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-11-17 17:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1946c4ccca04e374acc040fc30c8b44d2c9ca0a8 ***

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

Fix gdb.threads/multiple-step-overs.exp fails on arm

Hi,
Some tests in gdb.threads/multiple-step-overs.exp fail on arm target
when the displaced stepping on, but they pass when displaced stepping
is off.

 FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: step: step
 FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: next: next
 FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: continue: continue
 FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: signal thr1: continue to sigusr1_handler

when displaced stepping is on,

Sending packet: $vCont;c#a8...infrun: infrun_async(1)^M <--- [1]
infrun: prepare_to_wait^M
infrun: target_wait (-1.0.0, status) =^M
infrun:   -1.0.0 [Thread 0],^M
infrun:   status->kind = ignore^M
infrun: TARGET_WAITKIND_IGNORE^M
infrun: prepare_to_wait^M
Packet received: T05swbreak:;0b:f8faffbe;0d:409ee7b6;0f:d0880000;thread:p635.636;core:0;^M
infrun: target_wait (-1.0.0, status) =^M
infrun:   1589.1590.0 [Thread 1590],^M
infrun:   status->kind = stopped, signal = GDB_SIGNAL_TRAP^M
infrun: TARGET_WAITKIND_STOPPED^M
infrun: stop_pc = 0x88d0^M
infrun: context switch^M
infrun: Switching context from Thread 1591 to Thread 1590^

GDB resumes the whole process (all threads) rather than the specific
thread for which GDB wants to step over the breakpoint (as shown in [1]).
That is wrong because we resume a single thread and leave others stopped
when doing a normal step over where we temporarily remove the breakpoint,
single-step, reinsert the breakpoint, is that if we let other threads run
in the period while the breakpoint is removed, then these other threads
could miss the breakpoint.  Since with displaced stepping, we don't ever
remove the breakpoint, it should be fine to let other threads run.  However,
there's another reason that we should not let other threads run: that is
the case where some of those threads are also stopped for a breakpoint that
itself needs to be stepped over.  If we just let those threads run, then
they immediately re-trap their breakpoint again.

when displaced stepping is off, GDB behaves correctly, only resumes
the specific thread (as shown in [2]).

Sending packet: $vCont;c:p611.613#b2...infrun: infrun_async(1)^M <-- [2]
infrun: prepare_to_wait^M
infrun: target_wait (-1.0.0, status) =^M
infrun:   -1.0.0 [Thread 0],^M
infrun:   status->kind = ignore^M
infrun: TARGET_WAITKIND_IGNORE^M
infrun: prepare_to_wait^M
Packet received: T05swbreak:;0b:f8faffbe;0d:409e67b6;0f:48880000;thread:p611.613;core:1;^M
infrun: target_wait (-1.0.0, status) =^M
infrun:   1553.1555.0 [Thread 1555],^M
infrun:   status->kind = stopped, signal = GDB_SIGNAL_TRAP^M
infrun: TARGET_WAITKIND_STOPPED^M
infrun: clear_step_over_info^M
infrun: stop_pc = 0x8848

The current logic in GDB on deciding the set of threads to resume is:

  /* Decide the set of threads to ask the target to resume.  */
  if ((step || thread_has_single_step_breakpoints_set (tp))
      && tp->control.trap_expected)
    {
      /* We're allowing a thread to run past a breakpoint it has
	 hit, by single-stepping the thread with the breakpoint
	 removed.  In which case, we need to single-step only this
	 thread, and keep others stopped, as they can miss this
	 breakpoint if allowed to run.  */
      resume_ptid = inferior_ptid;
    }
  else
    resume_ptid = internal_resume_ptid (user_step);

it doesn't handle the case correctly that GDB continue (instead of
single step) the thread for displaced stepping.

I also update the comment below to reflect the code.  I remove the
"with the breakpoint removed" comment, because GDB doesn't remove
breakpoints in displaced stepping, so we don't have to worry that
other threads may miss the breakpoint.

Patch is regression tested on both x86_64-linux and arm-linux.

gdb:

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

	* infrun.c (resume): Check control.trap_expected only
	when deciding the set of threads to resume.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Introduce null_block_symbol
@ 2015-11-17 17:18 sergiodj+buildbot
  2015-11-18  9:08 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-11-17 17:18 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b6b806729dd5c4c46981d59f351460b4d7989548 ***

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

Introduce null_block_symbol

... in the spirit of null_ptid, null_frame_id, etc.

Fixes two instances of:

  /root/binutils-gdb/gdb/cp-namespace.c: In function 'block_symbol cp_lookup_nested_symbol(type*, const char*, const block*, domain_enum)':
  /root/binutils-gdb/gdb/cp-namespace.c:1010: warning: jump to case label
  /root/binutils-gdb/gdb/cp-namespace.c:1008: error:   crosses initialization of 'block_symbol <anonymous>'

Compiler info:

  Reading specs from /usr/lib/gcc-lib/amd64-unknown-openbsd5.8/4.2.1/specs
  Target: amd64-unknown-openbsd5.8
  Configured with: OpenBSD/amd64 system compiler
  Thread model: posix
  gcc version 4.2.1 20070719

gdb/ChangeLog:
2015-11-17  Pedro Alves  <palves@redhat.com>

	* cp-namespace.c (cp_lookup_bare_symbol)
	(cp_search_static_and_baseclasses, cp_lookup_symbol_via_imports)
	(cp_lookup_symbol_via_all_imports, cp_lookup_nested_symbol_1)
	(cp_lookup_nested_symbol): Use null_block_symbol.
	* d-namespace.c (d_lookup_symbol, d_lookup_nested_symbol)
	(d_lookup_symbol_imports, d_lookup_symbol_module): Use
	null_block_symbol.
	* symtab.c (null_block_symbol): New global.
	* symtab.h (null_block_symbol): Declare.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [C++] Always use setjmp/longjmp for exceptions
@ 2015-11-17 17:09 sergiodj+buildbot
  2015-11-18  8:50 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-11-17 17:09 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT eec461d0a8e7ae14c7fe8f0196ab8d0e30285d83 ***

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

[C++] Always use setjmp/longjmp for exceptions

We currently throw exceptions from signal handlers (e.g., for
Quit/ctrl-c).  But throwing C++ exceptions from signal handlers is
undefined.  (That doesn't restore signal masks, like siglongjmp does,
and, because asynchronous signals can arrive at any instruction, we'd
have to build _everything_ with -fasync-unwind-tables to make it
reliable.)  It happens to work on x86_64 GNU/Linux at least, but it's
likely broken on other ports.

Until we stop throwing from signal handlers, use setjmp/longjmp based
exceptions in C++ mode as well.

gdb/ChangeLog:
2015-11-17  Pedro Alves  <palves@redhat.com>

	* common/common-exceptions.h (GDB_XCPT_SJMP, GDB_XCPT_TRY)
	(GDB_XCPT_RAW_TRY, GDB_XCPT): Define.
	Replace __cplusplus checks with GDB_XCPT checks throughout.
	* common/common-exceptions.c: Replace __cplusplus checks with
	GDB_XCPT checks throughout.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] MinGW and attribute format(printf/gnu_printf)
@ 2015-11-17 17:01 sergiodj+buildbot
  2015-11-18  8:32 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-11-17 17:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 91ee7171d0886731900ab0238ce3795241d877a4 ***

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

MinGW and attribute format(printf/gnu_printf)

Cross building gdbserver for --host=x86_64-w64-mingw32 with gcc 4.8.4
20141219 (Fedora MinGW 4.8.4-1.fc20), I get:

  src/gdb/gdbserver/tracepoint.c: In function 'cmd_qtdp':
  src/gdb/gdbserver/tracepoint.c:2577:7: error: unknown conversion type character 'l' in format [-Werror=format=]
	 trace_debug ("Defined %stracepoint %d at 0x%s, "
	 ^
  src/gdb/gdbserver/tracepoint.c:2577:7: error: unknown conversion type character 'l' in format [-Werror=format=]
  src/gdb/gdbserver/tracepoint.c:2577:7: error: too many arguments for format [-Werror=format-extra-args]
  src/gdb/gdbserver/tracepoint.c: In function 'stop_tracing':
  src/gdb/gdbserver/tracepoint.c:3447:7: error: unknown conversion type character 'l' in format [-Werror=format=]
	 trace_debug ("Stopping the trace because "
	 ^
  src/gdb/gdbserver/tracepoint.c:3447:7: error: too many arguments for format [-Werror=format-extra-args]
  src/gdb/gdbserver/tracepoint.c: In function 'collect_data_at_tracepoint':
  src/gdb/gdbserver/tracepoint.c:4651:3: error: unknown conversion type character 'l' in format [-Werror=format=]
     trace_debug ("Making new traceframe for tracepoint %d at 0x%s, hit %" PRIu64,
     ^
  src/gdb/gdbserver/tracepoint.c:4651:3: error: too many arguments for format [-Werror=format-extra-args]
  src/gdb/gdbserver/tracepoint.c: In function 'collect_data_at_step':
  src/gdb/gdbserver/tracepoint.c:4687:3: error: unknown conversion type character 'l' in format [-Werror=format=]
     trace_debug ("Making new step traceframe for "
     ^

trace_debug is a macro that calls:

  static void trace_vdebug (const char *, ...) ATTRIBUTE_PRINTF (1, 2);

The calls that fail checking use PRIu64, etc., like:

      trace_debug ("Defined %stracepoint %d at 0x%s, "
		   "enabled %d step %" PRIu64 " pass %" PRIu64,
		   tpoint->type == fast_tracepoint ? "fast "
		   : tpoint->type == static_tracepoint ? "static " : "",
		   tpoint->number, paddress (tpoint->address), tpoint->enabled,
		   tpoint->step_count, tpoint->pass_count);

gnulib's stdio/printf module replacements may make %llu, etc. work on
mingw, instead of the MS-specific %I64u, and thus may make PRIu64
expand to %llu.  However, gcc isn't aware of that, because libiberty's
ansidecl.h defines ATTRIBUTE_PRINTF as using attribute format(printf).
But, with that format, gcc checks for MS-style format strings (%I64u).
In order to have gcc expect gnu/standard formats, we need to use
gnu_printf format instead.  Which version to use (printf/gnu_printf)
depends on msvcrt and mingw version, and so gnulib has a
configure-time check, and defines _GL_ATTRIBUTE_FORMAT_PRINTF
accordingly.

Since _GL_ATTRIBUTE_FORMAT_PRINTF is compatible with ATTRIBUTE_PRINTF,
the fix is simply to make use of the former.

gdb/ChangeLog:
2015-11-17  Pedro Alves  <palves@redhat.com>

	* common/common-defs.h (ATTRIBUTE_PRINTF): Redefine in terms of
	_GL_ATTRIBUTE_FORMAT_PRINTF after including ansidecl.h.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [C++/mingw] gdbserver: gdb/host signal mixup
@ 2015-11-17 16:37 sergiodj+buildbot
  2015-11-18  6:17 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-11-17 16:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ce7715e2594db00b2f434f62aa264a1061221b72 ***

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

[C++/mingw] gdbserver: gdb/host signal mixup

Building in C++ caught a buglet here:

../../../src/gdb/gdbserver/win32-low.c: In function 'void win32_resume(thread_resume*, size_t)':
../../../src/gdb/gdbserver/win32-low.c:929:11: error: invalid conversion from 'int' to 'gdb_signal' [-fpermissive]
       sig = resume_info[0].sig;
           ^
../../../src/gdb/gdbserver/win32-low.c:934:11: error: invalid conversion from 'int' to 'gdb_signal' [-fpermissive]
       sig = 0;
           ^

Signals in the "struct thread_resume" structure are host signals, not
gdb signals.  The current code happens to work because the only
signals that the Windows port supports have the same number as the gdb
equivalent (see handle_exception for the win32 exception -> gdb signal
mapping).

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

	* win32-low.c (win32_resume): Use gdb_signal_from_host,
	GDB_SIGNAL_0 and gdb_signal_to_string.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [C++/mingw] gdb-dlfcn.c casts
@ 2015-11-17 15:51 sergiodj+buildbot
  2015-11-17 21:07 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-11-17 15:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2986367f8eea0dc5febab9c9fd1cf06b3a4a8fdb ***

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

[C++/mingw] gdb-dlfcn.c casts

Fixes:

../../src/gdb/gdb-dlfcn.c: In function 'void* gdb_dlsym(void*, const char*)':
../../src/gdb/gdb-dlfcn.c:105:49: error: invalid conversion from 'void*' to 'HMODULE {aka HINSTANCE__*}' [-fpermissive]
   return (void *) GetProcAddress (handle, symbol);
                                                 ^

gdb/ChangeLog:
2015-11-17  Pedro Alves  <palves@redhat.com>

	* gdb-dlfcn.c (gdb_dlsym, gdb_dlclose) [__MINGW32__]: Add casts to
	HMODULE.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [C++/mingw] ser-mingw.c casts
@ 2015-11-17 15:35 sergiodj+buildbot
  2015-11-17 19:07 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-11-17 15:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cd78b7a16778046c0cfa4818780ea94a9a90c32c ***

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

[C++/mingw] ser-mingw.c casts

2015-11-17  Pedro Alves  <palves@redhat.com>

	* ser-mingw.c (CancelIo_ftype): New typedef.
	(CancelIo): Use CancelIo_ftype.
	(ser_windows_close, ser_windows_wait_handle)
	(ser_windows_read_prim, stop_select_thread)
	(console_select_thread, pipe_select_thread, file_select_thread)
	(ser_console_wait_handle, ser_console_done_wait_handle)
	(ser_console_close, cleanup_pipe_state, pipe_windows_close)
	(pipe_windows_write, pipe_wait_handle, pipe_done_wait_handle)
	(net_windows_socket_check_pending, net_windows_select_thread)
	(net_windows_wait_handle, net_windows_done_wait_handle)
	(net_windows_close): Add casts.
	(_initialize_ser_windows): Cast to CancelIo_ftype* instead of
	void*.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Convert c_string_type to an enum flags type
@ 2015-11-17 14:43 sergiodj+buildbot
  2015-11-17 17:06 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-11-17 14:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0c801b966379f7826fdd793b26ae879c2edf78d1 ***

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

Convert c_string_type to an enum flags type

c_string_type contains values meant to be OR'ed together (even though
some bits are mutually exclusive), so it makes sense to make it an
enum flags type.

gdb/ChangeLog:
2015-11-17  Simon Marchi  <simon.marchi@ericsson.com>

	* c-exp.y (exp): Adjust, change enum c_string_type to
	c_string_type.
	(parse_string_or_char): Likewise.
	* c-lang.c (charset_for_string_type): Likewise.
	(classify_type): Likewise.
	(c_printchar): Likewise.
	(c_printstr): Likewise.
	(evaluate_subexp_c): Likewise.  And change cast to enum
	c_string_type_values.
	* c-lang.h: Include "common/enum_flags.h".
	(enum c_string_type): Rename to...
	(enum c_string_type_values): ...this.
	(c_string_type): Define new enum flags type.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] guile disassembly hardcode TARGET_XFER_E_IO
@ 2015-11-17 13:56 sergiodj+buildbot
  2015-11-17 15:06 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-11-17 13:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9a4073e20b2f1da74cb3b46707e4f6fc4e700950 ***

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

guile disassembly hardcode TARGET_XFER_E_IO

Instead of adding a cast at the memory_error call, as needed for C++,
and have the reader understand the indirection, make it simple and
hardcode the generic memory error at the memory_error call site.

gdb/ChangeLog:
2015-11-17  Pedro Alves  <palves@redhat.com>

	* guile/scm-disasm.c (gdbscm_disasm_read_memory): Return -1 on
	error instead of TARGET_XFER_E_IO.
	(gdbscm_disasm_memory_error): Always pass TARGET_XFER_E_IO to
	memory_error.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Fix stack buffer overflow in aarch64_extract_return_value
@ 2015-11-16 15:47 sergiodj+buildbot
  2015-11-16 22:06 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-11-16 15:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT db3516bbfabe710a0292f642cb83b95ea24c323a ***

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

Fix stack buffer overflow in aarch64_extract_return_value

Hi,
I build GDB with -fsanitize=address, and run testsuite.  In
gdb.base/callfuncs.exp, I see the following error,

p/c fun1()
=================================================================^M
==9601==ERROR: AddressSanitizer: stack-buffer-overflow on address 0x7fffee858530 at pc 0x6df079 bp 0x7fffee8583a0 sp 0x7fffee858398
WRITE of size 16 at 0x7fffee858530 thread T0
    #0 0x6df078 in regcache_raw_read /home/yao/SourceCode/gnu/gdb/git/gdb/regcache.c:673
    #1 0x6dfe1e in regcache_cooked_read /home/yao/SourceCode/gnu/gdb/git/gdb/regcache.c:751
    #2 0x4696a3 in aarch64_extract_return_value /home/yao/SourceCode/gnu/gdb/git/gdb/aarch64-tdep.c:1708
    #3 0x46ae57 in aarch64_return_value /home/yao/SourceCode/gnu/gdb/git/gdb/aarch64-tdep.c:1918

We are extracting return value from V registers (128 bit), but only
allocate X_REGISTER_SIZE-byte array, which isn't sufficient.  This
patch changes the array to V_REGISTER_SIZE.

gdb:

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

	* aarch64-tdep.c (aarch64_extract_return_value):  Change array
	buf's length to V_REGISTER_SIZE.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] sim: sim-stop/sim-reason/sim-reg: move to common obj list
@ 2015-11-16  7:53 sergiodj+buildbot
  2015-11-16 18:09 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-11-16  7:53 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 797eee4264d1b504aabcbcabb6de2f1108441261 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 797eee4264d1b504aabcbcabb6de2f1108441261

sim: sim-stop/sim-reason/sim-reg: move to common obj list

Now that all arches (for the most part) have moved over, move sim-stop.o,
sim-reason.o, and sim-reg.o to the common object list and out of all the
arch ports.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] sim: cr16: convert to common sim engine logic
@ 2015-11-16  3:55 sergiodj+buildbot
  2015-11-16 15:19 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-11-16  3:55 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0ef7f98177f610dbb503d87f405c54e3722d8b25 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 0ef7f98177f610dbb503d87f405c54e3722d8b25

sim: cr16: convert to common sim engine logic

Now that we have access to the sim state everywhere, we can convert to
the common engine logic for overall processing.  This frees us up from
tracking exception state ourselves.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] sim: cr16: convert to common sim memory modules
@ 2015-11-16  3:48 sergiodj+buildbot
  2015-11-16 14:22 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-11-16  3:48 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 761e171ad834a0d0adcd8712fde85ab1325afc3a ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 761e171ad834a0d0adcd8712fde85ab1325afc3a

sim: cr16: convert to common sim memory modules

The cr16 port has a lot of translation/offset logic baked into it, but
it all looks like copy & paste from the d10v port rather than something
the cr16 port wants.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] sim: cr16/d10v: drop redundant call to sim_create_inferior
@ 2015-11-16  3:24 sergiodj+buildbot
  2015-11-16 10:23 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-11-16  3:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7ea08e8cb74bc21fcfe5befc0f3c8de3762cb0d6 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 7ea08e8cb74bc21fcfe5befc0f3c8de3762cb0d6

sim: cr16/d10v: drop redundant call to sim_create_inferior

With the conversion to the nrun frontend, this call should no longer be
necessary.  It also actively crashes when trying to use the sd state.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] sim: d10v: convert to common sim engine logic
@ 2015-11-16  2:24 sergiodj+buildbot
  2015-11-16  8:19 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-11-16  2:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT aadc1740c74a65b916b7d9bb6efe588352326871 ***

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

sim: d10v: convert to common sim engine logic

Now that we have access to the sim state everywhere, we can convert to
the common engine logic for overall processing.  This frees us up from
tracking exception state ourselves.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] sim: mcore: pull cpu state out of global scope
@ 2015-11-15 13:49 sergiodj+buildbot
  2015-11-16  5:19 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-11-15 13:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7eed1055b89ad3207151734d34849dd8631d2da2 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 7eed1055b89ad3207151734d34849dd8631d2da2

sim: mcore: pull cpu state out of global scope

This avoids using global variables to hold the cpu state so we can
better integrate with the sim common code.

There's also a minor fix here where we move the pc register back into
the state that is accessible by the asints array.  When it was pulled
out previously, the reg store/fetch functions broke, but no one really
noticed as the mcore gdb port was dropped a while back.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] sim: testsuite: support basic vars in flags
@ 2015-11-15  6:14 sergiodj+buildbot
  2015-11-15 20:35 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-11-15  6:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9bea4d16a6f009585841c1134a024d10a61b8d56 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 9bea4d16a6f009585841c1134a024d10a61b8d56

sim: testsuite: support basic vars in flags

Sometimes in tests, we need supplemental files like linker scripts or
board helper files.  There's no way to set those flags in the tests
currently and relative paths don't work (breaks out of tree builds).

Update the main option parser to replace some strings on the fly.  Now
tests can do things like:

Long term we'll want to switch the framework to use the dejagnu helpers
like dg-xxx that gcc & gdb utilize.  But that'll require more rework.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] sim: drop extern C linkage from most sim interface headers
@ 2015-11-15  5:51 sergiodj+buildbot
  2015-11-15 16:45 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-11-15  5:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c4d4ed40834de8e2b493f83cf15291f2d2e38c6f ***

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

sim: drop extern C linkage from most sim interface headers

Since these headers merely have enum's, drop the extern C linkage
markings.  Helps to reduce the copy & paste spam.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Bump version to 2.26.51
@ 2015-11-15  0:35 sergiodj+buildbot
  2015-11-15 13:32 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-11-15  0:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d8bd95efd8119e06e6753c841f1bbc54bb09d5de ***

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

Bump version to 2.26.51

bfd/
2015-11-13  Tristan Gingold  <gingold@adacore.com>

	* version.m4: Bump version to 2.26.51
	* configure: Regenerate.

binutils/
2015-11-13  Tristan Gingold  <gingold@adacore.com>

	* configure: Regenerate.

gas/
2015-11-13  Tristan Gingold  <gingold@adacore.com>

	* configure: Regenerate.

gprof/
2015-11-13  Tristan Gingold  <gingold@adacore.com>

	* configure: Regenerate.

ld/
2015-11-13  Tristan Gingold  <gingold@adacore.com>

	* configure: Regenerate.

opcodes/
2015-11-13  Tristan Gingold  <gingold@adacore.com>

	* configure: Regenerate.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Remove d10v from testsuite
@ 2015-11-13 15:22 sergiodj+buildbot
  2015-11-13 17:03 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-11-13 15:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c1862d0f60ee6050e3d4add7bbb1a595b1758473 ***

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

Remove d10v from testsuite

This patch removes the leftover of the d10v stuff in the testsuite
directory. The d10v port was removed in GDB 6.7, but I happen to see
that there are still some leftovers about d10v in testsuite.

gdb/testsuite:

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

	* gdb.base/call-sc.exp (test_scalar_returns): Remove the
	comments about d10v.
	(test_scalar_returns): Likewise.
	* gdb.base/d10v.ld: Remove.
	* gdb.base/overlays.exp: Remove the target triplet checking for
	d10v-*-*.
	* gdb.base/structs.exp (test_struct_returns): Remove the
	comments about d10v.
	(test_struct_calls): Likewise.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Use gdb_byte * instead of void * in push_stack_item
@ 2015-11-12  9:25 sergiodj+buildbot
  2015-11-12 10:19 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-11-12  9:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT df3b6708fe2384913e66d90340b619190cc4530e ***

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

Use gdb_byte * instead of void * in push_stack_item

gdb:

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

	* arm-tdep.c (push_stack_item): Change contents type to
	const gdb_byte *.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
[parent not found: <430e004ef7ecb3f75fc3c6642c9fdfb1d85a3694@gdb-build>]
* [binutils-gdb] gdb: Make use of 'add_info' to create info sub-commands.
@ 2015-11-11 10:07 sergiodj+buildbot
  2015-11-11 11:53 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-11-11 10:07 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5f515954d10b69ba6c390e7b8bcfdba2ced7850b ***

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

gdb: Make use of 'add_info' to create info sub-commands.

Switch to using 'add_info' function for creating basic info
sub-commands.

gdb/ChangeLog:

	* avr-tdep.c (_initialize_avr_tdep): Switch to 'add_info' for creating
	info sub-commands.
	* gnu-nat.c (add_task_commands): Likewise.
	* macrocmd.c (_initialize_macrocmd): Likewise.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] gdb: Use class_info when creating info commands.
@ 2015-11-11  9:58 sergiodj+buildbot
  2015-11-11 10:52 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-11-11  9:58 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f3575e08379b36ab3a286c8fb5838a2d54424073 ***

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

gdb: Use class_info when creating info commands.

The 'add_info' function is used for creating info commands, these
commands should be created as 'class_info' rather than 'no_class'.

gdb/ChangeLog:

	* cli/cli-decode.c (add_info): Switch to class_info.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Update the RX simulator to handle the latest opcode types.
@ 2015-11-10 16:17 sergiodj+buildbot
  2015-11-10 17:18 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-11-10 16:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 634a9f67d95161fa0182fc38601832c98bf62ffa ***

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

Update the RX simulator to handle the latest opcode types.

	* rx.c (id_names): Add nop4, nop5, nop6 and nop7.
	(decode_opcode): Likewise.
	(get_op): Handle RX_Operand_Zero_Indirect.
	Handle RX_Bad_Size and RX_MAX_SIZE.
	(put_op): Likewise.
	(N_MAP): Increase to 90.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] sim: cr16/d10v: localize translation funcs
@ 2015-11-10  7:26 sergiodj+buildbot
  2015-11-10 10:33 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-11-10  7:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6637a4265e6144f5a9ad29e9fa08aba4bd959cb9 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 6637a4265e6144f5a9ad29e9fa08aba4bd959cb9

sim: cr16/d10v: localize translation funcs

These functions are only used in the interp module, so there's no point
in exporting them and declaring them in the external sim interface.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Use ELF_STRING_ARM_unwind in arm-tdep.c
@ 2015-11-09 16:07 sergiodj+buildbot
  2015-11-09 17:00 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-11-09 16:07 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a5eda10c7857581e6ee641937f99aa76fa8044eb ***

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

Use ELF_STRING_ARM_unwind in arm-tdep.c

We've already has the definition like this,

 #define ELF_STRING_ARM_unwind           ".ARM.exidx"

so it is better to use the macro rather than the string.

gdb:

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

	* arm-tdep.c (arm_exidx_new_objfile): Use
	ELF_STRING_ARM_unwind.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Move copy_u.w to MSA64 ASE, remove copy_u.d.
@ 2015-11-09  8:59 sergiodj+buildbot
  2015-11-09  9:52 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-11-09  8:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT be7fe1cddbd5463651e0dff3e8d2cd06455246fc ***

Author: Robert Suchanek <robert.suchanek@imgtec.com>
Branch: master
Commit: be7fe1cddbd5463651e0dff3e8d2cd06455246fc

Move copy_u.w to MSA64 ASE, remove copy_u.d.

opcodes/ChangeLog:

	* mips-opc.c (mips_builtin_opcodes): Change "copy_u.w" to MSA64 ASE,
	remove "copy_u.d".

gas/testsuite/ChangeLog:

	* gas/mips/micromips@msa.d: Remove "copy_u.w".
	* gas/mips/msa.d: Likewise.
	* gas/mips/msa.s: Likweise.
	* gas/mips/mipsr6@msa.d: Likewise.  Replace addresses with regex.
	* gas/mips/msa64.d: Add "copy_u.w".  Remove "copy_u.d".
	* gas/mips/msa64.s: Likewise.
	* gas/mips/micromips@msa64.d: Likewise.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Copy gnulib obstack files
@ 2015-11-09  5:01 sergiodj+buildbot
  2015-11-09  5:47 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-11-09  5:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 314dee8ea9be79a450d9f0b451619b67ebe0e017 ***

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

Copy gnulib obstack files

This copies obstack.[ch] from gnulib, and updates the docs.  The next
patch should be applied if someone repeats the import at a later date.

include/
	PR gdb/17133
	* obstack.h: Import current gnulib file.
libiberty/
	PR gdb/17133
	* obstack.c: Import current gnulib file.
	* obstacks.texi: Updated doc, from glibc's manual/memory.texi.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] gdb.dwarf2: Don't hardcode certain constants in Dwarf::assemble constructs
@ 2015-11-07 18:22 sergiodj+buildbot
  2015-11-07 20:24 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-11-07 18:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c6f0b406f56ac5232d08cbd88c0bddfb2f640e90 ***

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

gdb.dwarf2: Don't hardcode certain constants in Dwarf::assemble constructs

Two tests in gdb.dwarf2, data-loc.exp and dynarr-ptr.exp assume that
sizeof(int) is 4.  This patch looks up the integer size and uses this
constant for DW_AT_byte_size, DW_AT_lower_bound, and DW_AT_upper_bound.

I discovered this problem while looking at test results for this
msp430 multilib:

msp430-sim/-msim/-mcpu=msp430x/-mlarge/-mdata-region=either/-mcode-region=either

It fixes the following set of failures:

FAIL: gdb.dwarf2/dynarr-ptr.exp: print foo.three_ptr.all'first
FAIL: gdb.dwarf2/dynarr-ptr.exp: print foo.three_ptr'first
FAIL: gdb.dwarf2/dynarr-ptr.exp: print foo.three_ptr_tdef.all'first
FAIL: gdb.dwarf2/dynarr-ptr.exp: print foo.three_ptr_tdef'first
FAIL: gdb.dwarf2/dynarr-ptr.exp: print foo.five_ptr.all'first
FAIL: gdb.dwarf2/dynarr-ptr.exp: print foo.five_ptr'first
FAIL: gdb.dwarf2/dynarr-ptr.exp: print foo.five_ptr_tdef.all'first
FAIL: gdb.dwarf2/dynarr-ptr.exp: print foo.five_ptr_tdef'first
FAIL: gdb.dwarf2/data-loc.exp: print foo.three
FAIL: gdb.dwarf2/data-loc.exp: print foo.three(1)
FAIL: gdb.dwarf2/data-loc.exp: print foo.three(2)
FAIL: gdb.dwarf2/data-loc.exp: print foo.three(3)
FAIL: gdb.dwarf2/data-loc.exp: print foo.three_tdef
FAIL: gdb.dwarf2/data-loc.exp: print foo.three_tdef(1)
FAIL: gdb.dwarf2/data-loc.exp: print foo.three_tdef(2)
FAIL: gdb.dwarf2/data-loc.exp: print foo.three_tdef(3)
FAIL: gdb.dwarf2/data-loc.exp: print foo.five
FAIL: gdb.dwarf2/data-loc.exp: print foo.five(2)
FAIL: gdb.dwarf2/data-loc.exp: print foo.five(3)
FAIL: gdb.dwarf2/data-loc.exp: print foo.five(4)
FAIL: gdb.dwarf2/data-loc.exp: print foo.five(5)
FAIL: gdb.dwarf2/data-loc.exp: print foo.five(6)
FAIL: gdb.dwarf2/data-loc.exp: print foo.five_tdef
FAIL: gdb.dwarf2/data-loc.exp: print foo.five_tdef(2)
FAIL: gdb.dwarf2/data-loc.exp: print foo.five_tdef(3)
FAIL: gdb.dwarf2/data-loc.exp: print foo.five_tdef(4)
FAIL: gdb.dwarf2/data-loc.exp: print foo.five_tdef(5)
FAIL: gdb.dwarf2/data-loc.exp: print foo.five_tdef(6)
FAIL: gdb.dwarf2/data-loc.exp: print foo__three
FAIL: gdb.dwarf2/data-loc.exp: print foo__three_tdef
FAIL: gdb.dwarf2/data-loc.exp: print foo__five
FAIL: gdb.dwarf2/data-loc.exp: print foo__five_tdef

As I recall, there are still (other) problems with msp430 multilibs
which don't use -mlarge.

gdb/testsuite/ChangeLog:

	* gdb.dwarf2/data-loc.exp (Dwarf::assemble): Don't hardcode
	value associated with DW_AT_byte_size.
	* gdb.dwarf2/dynarr-ptr.exp (Dwarf::assemble): Don't hardcode
	constants for DW_AT_byte_size, DW_AT_lower_bound, and
	DW_AT_upper_bound.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Use aarch64_decode_insn in aarch64_analyze_prologue
@ 2015-11-05  9:59 sergiodj+buildbot
  2015-11-05 14:30 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-11-05  9:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d9ebcbce29f3621a687872270cc8952ba1501e56 ***

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

Use aarch64_decode_insn in aarch64_analyze_prologue

This patch convert aarch64_analyze_prologue to using aarch64_decode_insn
to decode instructions.  After this change, aarch64_analyze_prologue
looks much simple, and some aarch64_decode_* functions are removed
accordingly.

gdb:

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

	* aarch64-tdep.c (extract_signed_bitfield): Remove.
	(decode_masked_match): Remove.
	(aarch64_decode_add_sub_imm): Remove.
	(aarch64_decode_br): Remove.
	(aarch64_decode_eret): Remove.
	(aarch64_decode_movz): Remove.
	(aarch64_decode_orr_shifted_register_x): Remove.
	(aarch64_decode_ret): Remove.
	(aarch64_decode_stp_offset): Remove.
	(aarch64_decode_stur): Remove.
	(aarch64_analyze_prologue): Call aarch64_decode_insn
	and use aarch64_inst to decode instructions.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Combine aarch64_decode_stp_offset_wb and aarch64_decode_stp_offset
@ 2015-11-05  9:56 sergiodj+buildbot
  2015-11-05 14:00 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-11-05  9:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 93d960127c205918dbb69ab32e686b20ff365a25 ***

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

Combine aarch64_decode_stp_offset_wb and aarch64_decode_stp_offset

This patch combines both aarch64_decode_stp_offset_wb and
aarch64_decode_stp_offset together.

gdb:

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

	* aarch64-tdep.c (aarch64_decode_stp_offset): New argument
	wback.
	(aarch64_decode_stp_offset_wb): Removed.
	(aarch64_analyze_prologue): Don't use
	aarch64_decode_stp_offset_wb.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
[parent not found: <1c215b97f9a64d6ba9821e8a0cf0f44526f29d78@gdb-build>]
[parent not found: <cbec665beba8acf6393a8c93312bdd3a03a0846c@gdb-build>]
[parent not found: <04248ead1f57204119180022580626e31c165f60@gdb-build>]
* [binutils-gdb] Fix non stopping breakpoint on newer compilers.
@ 2015-11-04 10:35 sergiodj+buildbot
  2015-11-05  9:47 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-11-04 10:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 14cb1c0b38b120cf5325d9538cce1a0347e2b626 ***

Author: Walfred Tedeschi <walfred.tedeschi@intel.com>
Branch: master
Commit: 14cb1c0b38b120cf5325d9538cce1a0347e2b626

Fix non stopping breakpoint on newer compilers.

The breakpoint presented in the return statement was not activated while
compiling the test with gcc 4.9.2.  Added a dummy statement to allow the
breakpoint again.

2015-10-14  Walfred Tedeschi  <walfred.tedeschi@intel.com>

gdb/testsuite:

	* i386-mpx-map.c (foo): Add dummy statement to trigger breakpoint.

Change-Id: I5293ca1c7f82a631e1e41cb650c30dd2d09ef3c2
Signed-off-by: Walfred Tedeschi <walfred.tedeschi@intel.com>


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Changing compiler flags for MPX tests.
@ 2015-11-04 10:27 sergiodj+buildbot
  2015-11-05  8:11 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-11-04 10:27 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1a2ccd2e32ecf767973bf96b965e915bd0a04bf3 ***

Author: Walfred Tedeschi <walfred.tedeschi@intel.com>
Branch: master
Commit: 1a2ccd2e32ecf767973bf96b965e915bd0a04bf3

Changing compiler flags for MPX tests.

Adapts tests to use actual GCC flags, previous used flags were
related to an internal GCC release.

2015-06-18  Walfred Tedeschi  <walfred.tedeschi@intel.com>

gdb/testsuite:

	* gdb.arch/i386-mpx-map.exp (comp_flags): Use released GCC flags.
	* gdb.arch/i386-mpx.exp (comp_flags): Use released GCC flags.

Change-Id: Id4c4551693a8df071ed4b71bb5dfb46a526ed5db
Signed-off-by: Walfred Tedeschi <walfred.tedeschi@intel.com>


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] btrace: add instruction-history /s and fix documentation
@ 2015-11-04  8:49 sergiodj+buildbot
  2015-11-05  3:44 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-11-04  8:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0c532a298058669a72061ad94ba9e24170ae91ae ***

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

btrace: add instruction-history /s and fix documentation

Add support for the /s modifier of the "record instruction-history" command.  It
behaves exactly like /m and prints disassembled instructions in the order in
which they were recorded with interleaved sources.  We accept /s in addition
to /m to align with the "disassemble" command.

The "record instruction-history" modifiers were not documented.  Document
all of them.

gdb/
	* record.c (get_insn_history_modifiers): Set DISASSEMBLY_SOURCE
	instead of DISASSEMBLY_SOURCE_DEPRECATED.  Also accept /s.
	(_initialize_record): Document the /s modifier.
	* NEWS: Announce record instruction-history's new /s modifier.

doc/
	* gdb.texinfo (Process Record and Replay): Document "record
	instruction-history" modifiers.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
[parent not found: <b9559b8bc4b3c0dffaf08569704a0484e1fb8080@gdb-build>]
[parent not found: <10268a4c0d64b3892397aeaafbc4b91f6a1e0dc8@gdb-build>]
[parent not found: <c28ebe255ba37f4dcd295cf6a4608424aaeb699f@gdb-build>]
* [binutils-gdb] Simplify gdb.threads/wp-replication.exp on counting HW watchpoints
@ 2015-10-30 21:44 sergiodj+buildbot
  2015-10-31 20:52 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-10-30 21:44 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4081c0f1222810746068579c6fbbcd8a9b59cbb8 ***

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

Simplify gdb.threads/wp-replication.exp on counting HW watchpoints

Nowadays, test gdb.threads/wp-replication.exp uses a while loop to
repeatedly insert HW watchpoint, resume and check no error message
coming out, in order to count HW watchpoints  There are some
drawbacks in this way,

 - the loop could be endless.  I think this is use to making trouble
   to S/390, since we had such comment

      # Some targets (like S/390) behave as though supporting
      # unlimited hardware watchpoints.  In this case we just take a
      # safe exit out of the loop.

   I hit this today too because a GDB internal error is triggered
   on "continue" in the loop, and $done is 0 invariantly, so the loop
   can't end.
 - the code counting hardware watchpoint is too complicated.  We can
   use "set breakpoint always-inserted on" to get the result of inserting
   HW watchpoint without resuming the inferior.  In this way,
   watch_count_done and empty_cycle in c file is no longer needed.

In this patch, I change to use "set breakpoint always-inserted on" trick,
and only iterate $NR_THREADS times, to count the HW watchpoint.  In this
way, the loop can't be endless, and GDB doesn't need to resume the inferior.

gdb/testsuite:

2015-10-30  Yao Qi  <yao.qi@linaro.org>

	* gdb.threads/wp-replication.c (watch_count_done): Remove.
	(empty_cycle): Remove.
	(main): Don't call empty_cycle.  Don't use watch_count_done.
	* gdb.threads/wp-replication.exp: Don't set breakpoint on
	empty_cycle.  Rewrite the code counting HW watchpoints.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
[parent not found: <aefb52a69351517dbcfaafca1d21e5431d4119d1@gdb-build>]
* [binutils-gdb] Updated (simplified) Chinese translations for ld, bfd, binutils and gold.
@ 2015-10-30 12:57 sergiodj+buildbot
  2015-10-30 18:25 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-10-30 12:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 26f187cd169e484ac2b8ac3f9ece55a597caadf9 ***

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

Updated (simplified) Chinese translations for ld, bfd, binutils and gold.

	* po/zh_CN.po: Updated (simplified) Chinese translation.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
[parent not found: <968bc5cc86bff4ebf89e63bf99db7c7e777d4756@gdb-build>]
* [binutils-gdb] gdbserver/server.c: Cast return value of memmem
@ 2015-10-29 18:21 sergiodj+buildbot
  2015-10-30 11:57 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-10-29 18:21 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d6f85c8421acaf09fa5a25ae2621819889d54038 ***

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

gdbserver/server.c: Cast return value of memmem

gdb/gdbserver/ChangeLog:

	* server.c (handle_search_memory_1): Cast return value of
	memmem.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Disable paging when run by Emacs 25.1 and later.
@ 2015-10-29 17:42 sergiodj+buildbot
  2015-10-30  6:44 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-10-29 17:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e681cf3fe50d3c8d17dabde079bbd949a59ef53a ***

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

Disable paging when run by Emacs 25.1 and later.

gdb/ChangeLog:

	* utils.c (init_page_info): Disable paging if INSIDE_EMACS is set
	in the environment.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
[parent not found: <44a8b4df1d6f5b8096f01787751fd51c42e78fc6@gdb-build>]
[parent not found: <e3bdafe2bac1672da335fde734b337c5504e5437@gdb-build>]
[parent not found: <b80c3053162ec5533e120ee4e4ed30296d4c5fb2@gdb-build>]
* [binutils-gdb] Fix a typo in comment in elf32-i386.c
@ 2015-10-28 16:31 sergiodj+buildbot
  2015-10-29  0:12 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-10-28 16:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a3718e9efd2e0035dc0c008c754309edd8d5ae28 ***

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

Fix a typo in comment in elf32-i386.c

	* elf32-i386.c (elf_i386_relocate_section): Fix a typo in
	comment.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Fix recent STM324LXX patch to compile on 32-bit hosts.
@ 2015-10-28 14:07 sergiodj+buildbot
  2015-10-28 22:07 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-10-28 14:07 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 82188b295de579bee5f68de9f4d76ce4a3d41aa9 ***

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

Fix recent STM324LXX patch to compile on 32-bit hosts.

	* elf32-arm.c (create_instruction_branch_absolute): Replace
	pointer parameters with a simple integer parameter.
	(stm32l4xx_create_replacing_stub_ldmia): Update calls to
	create_instruction_branch_absolute.
	(stm32l4xx_create_replacing_stub_ldmdb): Likewise.
	(stm32l4xx_create_replacing_stub_vldm): Likewise.
	(elf32_arm_write_section): Use pointer type for veneer addresses.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] source.c:openp: save/restore errno
@ 2015-10-27 17:03 sergiodj+buildbot
  2015-10-28 16:00 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-10-27 17:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 79b289e2d8083691ccb2c943d4502e1af54e81e2 ***

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

source.c:openp: save/restore errno

openp's return is documented as:

~~~
   If a file is found, return the descriptor.
   Otherwise, return -1, with errno set for the last name we tried to open.  */
~~~

By inspection, I noticed that there are function calls after the ones
that first set errno, and those may clobber errno.  It's safer to save
errno when see an open fail, and restore it on exit.

Tested on x86_64 Fedora 20.

gdb/ChangeLog:
2015-10-27  Pedro Alves  <palves@redhat.com>

	* source.c (openp): New local 'last_errno'.  Use it to
	save/restore errno.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] psymtab.c: Add casts
@ 2015-10-27 15:17 sergiodj+buildbot
  2015-10-28 13:58 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-10-27 15:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 709b551853919f47b58aafbb95fd00a98bcaf76c ***

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

psymtab.c: Add casts

... as needed for C++.

gdb/ChangeLog:
2015-10-27  Pedro Alves  <palves@redhat.com>

	* psymtab.c (dump_psymtab_addrmap_1): Add casts.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Add scm_t_dynwind_flags casts
@ 2015-10-27 14:45 sergiodj+buildbot
  2015-10-28  9:59 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-10-27 14:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c6486df5f1400d90a13df5c6dbd96aeaccf8225b ***

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

Add scm_t_dynwind_flags casts

There is a handful of calls to

  scm_dynwind_begin (0);

where the parameter is an enum, scm_t_dynwind_flags.  In C++, we have no
choice but to add an explicit cast, since there is no enum value that
represents 0 (no flags set).

gdb/ChangeLog:

	* guile/scm-breakpoint.c (gdbscm_set_breakpoint_stop_x): Add
	scm_t_dynwind_flags casts.
	* guile/scm-cmd.c (gdbscm_parse_command_name): Likewise.
	* guile/scm-ports.c (gdbscm_open_memory): Likewise.
	* guile/scm-value.c (gdbscm_value_to_string): Likewise.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] ada-lang.h: Add cast in GROW_VECT
@ 2015-10-27 13:39 sergiodj+buildbot
  2015-10-28  0:28 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-10-27 13:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a480de357b17b1b2057b8375284079ccafae39db ***

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

ada-lang.h: Add cast in GROW_VECT

The assignment requires a cast in C++.  We only use this macro for
vectors of chars, so adding (char *) diretly will do for now.

gdb/ChangeLog:

	* ada-lang.h (GROW_VECT): Add cast.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Add --fix-stm32l4xx-629360 to the ARM linker to enable a link-time workaround for a bug in the bus matrix / memory controller for some of the STM32 Cortex-M4 based products (STM32L4xx).
@ 2015-10-27 13:32 sergiodj+buildbot
  2015-10-27 23:13 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-10-27 13:32 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a504d23a83d115b1b29a5b1fbfaeb2b09bc0e22c ***

Author: Laurent Alfonsi <laurent.alfonsi@st.com>
Branch: master
Commit: a504d23a83d115b1b29a5b1fbfaeb2b09bc0e22c

Add --fix-stm32l4xx-629360 to the ARM linker to enable a link-time workaround for a bug in the bus matrix / memory controller for some of the STM32 Cortex-M4 based products (STM32L4xx).

bfd  * bfd-in2.h: Regenerate.
     * bfd-in.h (bfd_arm_stm32l4xx_fix): New enum. Specify how
     STM32L4XX instruction scanning should be done.
     (bfd_elf32_arm_set_stm32l4xx_fix)
     (bfd_elf32_arm_stm32l4xx_erratum_scan)
     (bfd_elf32_arm_stm32l4xx_fix_veneer_locations): Add prototypes.
     (bfd_elf32_arm_set_target_relocs): Add stm32l4xx fix type argument
     to prototype.
     * elf32-arm.c (STM32L4XX_ERRATUM_VENEER_SECTION_NAME)
     (STM32L4XX_ERRATUM_VENEER_ENTRY_NAME): Define macros.
     (elf32_stm32l4xx_erratum_type): New enum.
     (elf32_stm32l4xx_erratum_list): New struct. List of veneers or
     jumps to veneers.
     (_arm_elf_section_data): Add stm32l4xx_erratumcount,
     stm32l4xx_erratumlist.
     (elf32_arm_link_hash_table): Add stm32l4xx_erratum_glue_size,
     stm32l4xx_fix and num_stm32l4xx_fixes fields.
     (ctz): New function.
     (popcount): New function.
     (elf32_arm_link_hash_table_create): Initialize stm32l4xx_fix.
     (put_thumb2_insn): New function.
     (STM32L4XX_ERRATUM_LDM_VENEER_SIZE): Define. Size of a veneer for
     LDM instructions.
     (STM32L4XX_ERRATUM_VLDM_VENEER_SIZE): Define. Size of a veneer for
     VLDM instructions.
     (bfd_elf32_arm_allocate_interworking_sections): Initialise erratum
     glue section.
     (record_stm32l4xx_erratum_veneer) : New function. Create a single
     veneer, and its associated symbols.
     (bfd_elf32_arm_add_glue_sections_to_bfd): Add STM32L4XX erratum glue.
     (bfd_elf32_arm_set_stm32l4xx_fix): New function. Set the type of
     erratum workaround required.
     (bfd_elf32_arm_stm32l4xx_fix_veneer_locations): New function. Find
     out where veneers and branches to veneers have been placed in
     virtual memory after layout.
     (is_thumb2_ldmia): New function.
     (is_thumb2_ldmdb): Likewise.
     (is_thumb2_vldm ): Likewise.
     (stm32l4xx_need_create_replacing_stub): New function. Decide if a
     veneer must be emitted.
     (bfd_elf32_arm_stm32l4xx_erratum_scan): Scan the sections of an
     input BFD for potential erratum-triggering insns. Record results.
     (bfd_elf32_arm_set_target_relocs): Set stm32l4xx_fix field in
     global hash table.
     (elf32_arm_size_dynamic_sections): Collect glue information.
     (create_instruction_branch_absolute): New function.
     (create_instruction_ldmia): Likewise.
     (create_instruction_ldmdb): Likewise.
     (create_instruction_mov): Likewise.
     (create_instruction_sub): Likewise.
     (create_instruction_vldmia): Likewise.
     (create_instruction_vldmdb): Likewise.
     (create_instruction_udf_w): Likewise.
     (create_instruction_udf): Likewise.
     (push_thumb2_insn32): Likewise.
     (push_thumb2_insn16): Likewise.
     (stm32l4xx_fill_stub_udf): Likewise.
     (stm32l4xx_create_replacing_stub_ldmia): New function. Expands the
     replacing stub for ldmia instructions.
     (stm32l4xx_create_replacing_stub_ldmdb): Likewise for ldmdb.
     (stm32l4xx_create_replacing_stub_vldm): Likewise for vldm.
     (stm32l4xx_create_replacing_stub): New function. Dispatches the
     stub emission to the appropriate functions.
     (elf32_arm_write_section): Output veneers, and branches to veneers.

ld   * ld.texinfo: Description of the STM32L4xx erratum workaround.
     * emultempl/armelf.em (stm32l4xx_fix): New.
     (arm_elf_before_allocation): Choose the type of fix, scan for
     erratum.
     (gld${EMULATION_NAME}_finish): Fix veneer locations.
     (arm_elf_create_output_section_statements): Propagate
     stm32l4xx_fix value.
     (PARSE_AND_LIST_PROLOGUE): Define OPTION_STM32L4XX_FIX.
     (PARSE_AND_LIST_LONGOPTS): Add entry for handling
     --fix-stm32l4xx-629360.
     (PARSE_AND_LIST_OPTION): Add entry for helping on
     --fix-stm32l4xx-629360.
     (PARSE_AND_LIST_ARGS_CASES): Treat OPTION_STM32L4XX_FIX.

tests * ld-arm/arm-elf.exp (armelftests_common): Add STM32L4XX
       tests.
     * ld-arm/stm32l4xx-cannot-fix-far-ldm.d: New.
     * ld-arm/stm32l4xx-cannot-fix-far-ldm.s: Likewise.
     * ld-arm/stm32l4xx-cannot-fix-it-block.d: Likewise.
     * ld-arm/stm32l4xx-cannot-fix-it-block.s: Likewise.
     * ld-arm/stm32l4xx-fix-all.d: Likewise.
     * ld-arm/stm32l4xx-fix-all.s: Likewise.
     * ld-arm/stm32l4xx-fix-it-block.d: Likewise.
     * ld-arm/stm32l4xx-fix-it-block.s: Likewise.
     * ld-arm/stm32l4xx-fix-ldm.d: Likewise.
     * ld-arm/stm32l4xx-fix-ldm.s: Likewise.
     * ld-arm/stm32l4xx-fix-vldm.d: Likewise.
     * ld-arm/stm32l4xx-fix-vldm.s: Likewise.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] symtab.h (struct general_symbol_info> <ada_mangled>: Update comment.
@ 2015-10-27  3:35 sergiodj+buildbot
  2015-10-27 18:55 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-10-27  3:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a04a15f586590f1969ab31478f0b04243f760769 ***

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

symtab.h (struct general_symbol_info> <ada_mangled>: Update comment.

gdb/ChangeLog:

	* symtab.h (struct general_symbol_info> <ada_mangled>: Update comment.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Check symbol defined by assignment in linker script
@ 2015-10-26 23:44 sergiodj+buildbot
  2015-10-27 14:42 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-10-26 23:44 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7b7e7f1da28585cfa49cbced50dbbd75a143cd20 ***

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

Check symbol defined by assignment in linker script

Symbol symbol defined by an assignment in a linker script has type
bfd_link_hash_new.  elf_i386_convert_load and elf_x86_64_convert_load
should check bfd_link_hash_new to see if a symbol is defined by a linker
script.

bfd/

	PR ld/19175
	* elf32-i386.c (elf_i386_convert_load): Check bfd_link_hash_new
	instead of calling bfd_link_get_defined_symbol.
	* elf64-x86-64.c (elf_x86_64_convert_load): Likewise.  Skip
	relocation overflow for bfd_link_hash_new.
	* linker.c (bfd_link_get_defined_symbol): Removed.
	* bfd-in2.h: Regenerated.

ld/testsuite/

	PR ld/19175
	* ld-i386/i386.exp: Run pr19175.
	* ld-x86-64/x86-64.exp: Likewise.
	* ld-i386/pr19175.d: New file.
	* ld-i386/pr19175.s: Likewise.
	* ld-i386/pr19175.t: Likewise.
	* ld-x86-64/pr19175.d: Likewise.
	* ld-x86-64/pr19175.s: Likewise.
	* ld-x86-64/pr19175.t: Likewise.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] PR python/18938: source -s foo.py with foo.py a symlink to foo.notpy fails
@ 2015-10-26 22:10 sergiodj+buildbot
  2015-10-27 12:45 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-10-26 22:10 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1a70ae976b673f7762f14734785b34fc5ba92eae ***

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

PR python/18938: source -s foo.py with foo.py a symlink to foo.notpy fails

gdb/ChangeLog:

	PR python/18938
	* cli/cli-cmds (source_script_fron_sctream): New arg file_to_open.
	All callers updated.

gdb/testsuite/ChangeLog:

	* gdb.python/python.exp: Add test for symlink from .py file to .notpy
	file.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Print address map in output of "mt print psymbols"
@ 2015-10-26 21:23 sergiodj+buildbot
  2015-10-27  8:05 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-10-26 21:23 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 372405a5e8adbe5affce56410b6d6048c63cac3f ***

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

Print address map in output of "mt print psymbols"

gdb/ChangeLog:

	* psymtab.c (struct dump_psymtab_addrmap_data): Define.
	(dump_psymtab_addrmap_1, dump_psymtab_addrmap): New functions.
	(maintenance_print_psymbols): Print address map.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Add some casts for building on musl.
@ 2015-10-26 20:31 sergiodj+buildbot
  2015-10-26 22:02 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-10-26 20:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d41401ace01c234f42697e190a2ac95991780626 ***

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

Add some casts for building on musl.

gdb/ChangeLog:

	* linux-thread-db.c (find_new_threads_callback): Cast ti.ti_tid to
	unsigned long for debug_printf.
	(thread_db_pid_to_str): Ditto.

gdb/gdbserver/ChangeLog:

	* thread-db.c (find_one_thread): Cast ti.ti_tid to unsigned long
	for debug_printf.
	(attach_thread, find_new_threads_callback): Ditto.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Properly convert address load of __start_XXX/__stop_XXX
@ 2015-10-26 15:26 sergiodj+buildbot
  2015-10-26 19:01 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-10-26 15:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a6af384b19c63bab4a1803c09592c5b5bd8674c2 ***

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

Properly convert address load of __start_XXX/__stop_XXX

Since __start_XXX and __stop_XXX symbols aren't defined when address
load is being converted, we need to check if there is an XXX output
section to get their section and value.  This patch adds a new function,
bfd_link_get_defined_symbol, to search for the XXX output section to
check if __start_XXX and __stop_XXX symbols are defined.

bfd/

	PR ld/19171
	* elf32-i386.c (elf_i386_convert_load): Call
	bfd_link_get_defined_symbol to check if a symbol is defined.
	* elf64-x86-64.c (elf_x86_64_convert_load): Call
	bfd_link_get_defined_symbol to get defined symbol section and
	value.
	* linker.c (bfd_link_get_defined_symbol): New function.
	* bfd-in2.h: Regenerated.

ld/testsuite/

	PR ld/19171
	* ld-i386/lea1.s: Add tests for address load of __start_XXX
	and __stop_XXX.
	* ld-i386/mov1.s: Likewise.
	* ld-x86-64/lea1.s: Likewise.
	* ld-x86-64/mov1.s: Likewise.
	* ld-i386/lea1a.d: Updated.
	* ld-i386/lea1b.d: Likewise.
	* ld-i386/lea1c.d: Likewise.
	* ld-i386/mov1a.d: Likewise.
	* ld-i386/mov1b.d: Likewise.
	* ld-x86-64/lea1a.d: Likewise.
	* ld-x86-64/lea1b.d: Likewise.
	* ld-x86-64/lea1c.d: Likewise.
	* ld-x86-64/lea1d.d: Likewise.
	* ld-x86-64/lea1e.d: Likewise.
	* ld-x86-64/lea1f.d: Likewise.
	* ld-x86-64/mov1a.d: Likewise.
	* ld-x86-64/mov1b.d: Likewise.
	* ld-x86-64/mov1c.d: Likewise.
	* ld-x86-64/mov1d.d: Likewise.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] gdbscm_memory_port_write: use local variable to avoid adding casts
@ 2015-10-26 13:08 sergiodj+buildbot
  2015-10-26 14:48 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-10-26 13:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e0dd41e9671fffc957c3d8f41adcd52274319f4f ***

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

gdbscm_memory_port_write: use local variable to avoid adding casts

By having a local variable of type (const gdb_byte *), we can avoid adding
two casts.

gdb/ChangeLog:

	* guile/scm-ports.c (gdbscm_memory_port_write): Declare new
	"data" local variable and use it.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] tui-data.c: Remove unnecessary casts
@ 2015-10-25  3:45 sergiodj+buildbot
  2015-10-25 20:17 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-10-25  3:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f4ee58bde946ec87c8ead17d7b47c1c7bcb7c3f6 ***

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

tui-data.c: Remove unnecessary casts

The (void *) casts make the build fail in C++ mode and are unnecessary.

gdb/ChangeLog:

	* tui/tui-data.c (tui_add_to_source_windows): Remove void *
	cast.
	(tui_add_content_elements): Likewise.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] ia64-tdep.c: Remove (void *) casts
@ 2015-10-24 22:47 sergiodj+buildbot
  2015-10-24 23:43 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-10-24 22:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ce746418ef15c5a47b9ab17c249ba5f7c273db4a ***

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

ia64-tdep.c: Remove (void *) casts

Remove these (void *) casts, which cause a build failure in C++ mode.

gdb/ChangeLog:

	* ia64-tdep.c (ia64_pseudo_register_write): Remove cast.
	(ia64_push_dummy_call): Remove cast and change type of "to" to
	array of gdb_byte.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Add cast to observer.sh
@ 2015-10-23 21:07 sergiodj+buildbot
  2015-10-23 22:00 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-10-23 21:07 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6ecf4e06a48cfc6dfbdf7c8f2969ffe7271f15da ***

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

Add cast to observer.sh

gdb/ChangeLog:

	* observer.h (observer_${event}_notification_stub): Add cast.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Initialize field insn_count correctly
@ 2015-10-23  8:38 sergiodj+buildbot
  2015-10-23 13:52 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-10-23  8:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 034f1a812d8f5655d08e2bdeb5ec7d56caa40d41 ***

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

Initialize field insn_count correctly

This patch initialize dsd.insn_count, otherwise, it triggers the assert
below on testings we did recently.

gdb:

2015-10-23  Yao Qi  <yao.qi@linaro.org>

	* aarch64-tdep.c (aarch64_displaced_step_copy_insn): Set
	dsd.insn_count to zero.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
[parent not found: <5af9928d44e302b7f68365a0c551f640895366ff@gdb-build>]
* [binutils-gdb] garbage collect gdb/infrun.c:stop_after_trap
@ 2015-10-22 16:53 sergiodj+buildbot
  2015-10-23 10:36 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-10-22 16:53 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d236ad1955a0a6b5203bc1474b989fd9dba668f8 ***

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

garbage collect gdb/infrun.c:stop_after_trap

No longer used anywhere.

gdb/ChangeLog:
2015-10-22  Pedro Alves  <palves@redhat.com>

	* infrun.c (stop_after_trap): Delete.
	(clear_proceed_status, handle_signal_stop, struct
	infcall_control_state, save_infcall_control_state)
	(restore_infcall_control_state): Remove references to
	stop_after_trap.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Add cast in nto-tdep.c
@ 2015-10-22 16:10 sergiodj+buildbot
  2015-10-23  7:24 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-10-22 16:10 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fb70bc1a74d371cc6cc07e018df436a17c26037e ***

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

Add cast in nto-tdep.c

gdb/ChangeLog:

	* nto-tdep.c (nto_inferior_data): Add cast.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] bfd/mmo.c: handle "objcopy --extract-symbols" generating and reading back.
@ 2015-10-22 14:30 sergiodj+buildbot
  2015-10-22 23:03 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-10-22 14:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c287bfe4297ec9c12db292fae5562be1758cf14f ***

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

bfd/mmo.c: handle "objcopy --extract-symbols" generating and reading back.

bfd:
	* mmo.c (struct mmo_data_struct): New members
	symbol_consistency_override_calculated and ignore_symbol_consistency.
	(mmo_section_has_contents, mmo_ignore_symbol_consistency): New
	functions.
	(mmo_create_symbol): Check with mmo_ignore_symbol_consistency if to
	report an error for unexpected value of Main.
	(mmo_write_symbols_and_terminator): Similar.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Add "-z call-nop=PADDING" option to ld
@ 2015-10-22 12:23 sergiodj+buildbot
  2015-10-22 17:47 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-10-22 12:23 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT caa65211bbbfd53c40c9ce1b79b97ccf2c679a52 ***

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

Add "-z call-nop=PADDING" option to ld

The ld linker can transform indirect call to a locally defined function,
foo, via its GOT slot, to either "NOP call foo" or "call foo NOP" where
NOP is a 1-byte NOP padding.  This patch adds a "-z call-nop=PADDING"
option to x86 ld to control 1-byte NOP padding for x86 call instruction.
PADDING is one of prefix-addr, prefix-nop, suffix-nop, prefix-NUMBER or
suffix-NUMBER.

bfd/

	* elf32-i386.c (elf_i386_convert_load): Use call_nop_byte and
	check call_nop_as_suffix for 1-byte NOP padding to pad call.
	* elf64-x86-64.c (elf_x86_64_convert_load): Likewise.

include/

	* bfdlink.h (bfd_link_info): Add call_nop_as_suffix and
	call_nop_byte.

ld/

	* ld/ld.texinfo: Document "-z call-nop=PADDING" option.
	* emulparams/call_nop.sh: New file.
	* emulparams/elf_i386_be.sh: Source
	${srcdir}/emulparams/call_nop.sh.
	* emulparams/elf_i386_chaos.sh: Likewise.
	* emulparams/elf_i386_ldso.sh: Likewise.
	* emulparams/elf_i386_vxworks.sh: Likewise.
	* emulparams/elf_iamcu.sh: Likewise.
	* emulparams/elf_k1om.sh: Likewise.
	* emulparams/elf_l1om.sh: Likewise.
	* emulparams/elf_x86_64.sh: Likewise.
	* emultempl/elf32.em (gld${EMULATION_NAME}_before_parse): Set
	link_info.call_nop_byte if $CALL_NOP_BYTE isn't empty.

ld/testsuite/

	* ld-i386/call3.s: New file.
	* ld-i386/call3a.d: Likewise.
	* ld-i386/call3b.d: Likewise.
	* ld-i386/call3c.d: Likewise.
	* ld-i386/call3d.d: Likewise.
	* ld-i386/call3e.d: Likewise.
	* ld-i386/call3f.d: Likewise.
	* ld-i386/call3g.d: Likewise.
	* ld-i386/call3h.d: Likewise.
	* ld-i386/load1-nacl.d: Likewise.
	* ld-x86-64/call1.s: Likewise.
	* ld-x86-64/call1a.d: Likewise.
	* ld-x86-64/call1b.d: Likewise.
	* ld-x86-64/call1c.d: Likewise.
	* ld-x86-64/call1d.d: Likewise.
	* ld-x86-64/call1e.d: Likewise.
	* ld-x86-64/call1f.d: Likewise.
	* ld-x86-64/call1g.d: Likewise.
	* ld-x86-64/call1h.d: Likewise.
	* ld-x86-64/call1i.d: Likewise.
	* ld-x86-64/load1a-nacl.d: Likewise.
	* ld-x86-64/load1b-nacl.d: Likewise.
	* ld-x86-64/load1c-nacl.d: Likewise.
	* ld-x86-64/load1d-nacl.d: Likewise.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Add R_386_GOT32X support to gas and ld
@ 2015-10-22 12:11 sergiodj+buildbot
  2015-10-22 15:44 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-10-22 12:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 02a866936de7e63ad4962ccba56c8cd05c231275 ***

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

Add R_386_GOT32X support to gas and ld

This patch adds support for the R_386_GOT32X relocation proposed in

https://groups.google.com/forum/#!topic/ia32-abi/GbJJskkid4I

to gas and ld.  It updates gas to generate R_386_GOT32X relocation for
memory operand, foo@GOT[(%reg)].  We must encode "mov foo@GOT, %eax"
with the 0x8b opcode, instead of the 0xb8 opcode, so that it can be
transformed to "lea foo, %eax".  With the locally defined symbol, foo,
we convert

   mov foo@GOT[(%reg1)], %reg2
to
   lea foo[@GOTOFF(%reg1)], %reg2

and convert

   call/jmp *foo@GOT[(%reg)]
to

   nop call foo/jmp foo nop

When PIC is false, convert

   test %reg1, foo@GOT[(%reg2)]
to
   test $foo, %reg1

and convert

binop foo@GOT[(%reg1)], %reg2

to

binop $foo, %reg2

where binop is one of adc, add, and, cmp, or, sbb, sub, xor instructions.

bfd/

	* elf32-i386.c: Include opcode/i386.h.
	(elf_howto_table): Add R_386_GOT32X.
	(R_386_ext2): Replace R_386_IRELATIVE with R_386_GOT32X.
	(elf_i386_reloc_type_lookup): Handle BFD_RELOC_386_GOT32X.
	(need_convert_mov_to_lea): Renamed to ...
	(need_convert_load): This.
	(elf_i386_check_relocs): Handle R_386_GOT32X.  Replace
	need_convert_mov_to_lea with need_convert_load.
	(elf_i386_gc_sweep_hook): Handle R_386_GOT32X.
	(elf_i386_size_dynamic_sections): Likewise.
	(elf_i386_relocate_section): Likewise.
	(elf_i386_convert_mov_to_lea): Renamed to ...
	(elf_i386_convert_load): This.  Replace need_convert_mov_to_lea
	with need_convert_load.  Support R_386_GOT32X transformations.
	* reloc.c (BFD_RELOC_386_GOT32X): New.
	* bfd-in2.h: Regenerated.
	* libbfd.h: Likewise.

gas/

	* config/tc-i386.c (tc_i386_fix_adjustable): Handle
	BFD_RELOC_386_GOT32X.
	(tc_gen_reloc): Likewise.
	(match_template): Force 0x8b encoding for "mov foo@GOT, %eax".
	(output_disp): Check for "call/jmp *mem", "mov mem, %reg",
	"test %reg, mem" and "binop mem, %reg" where binop is one of
	adc, add, and, cmp, or, sbb, sub, xor instructions.  Set
	fx_tcbit if the REX prefix is generated.  Set fx_tcbit2 if
	BFD_RELOC_386_GOT32X should be generated.
	(i386_validate_fix): Generate BFD_RELOC_386_GOT32X if fx_tcbit2
	is set.

gas/testsuite/

	* gas/i386/got.d: New file.
	* gas/i386/got.s: Likewise.
	* gas/i386/i386.exp: Run got.
	* gas/i386/localpic.d: Replace R_386_GOT32 with R_386_GOT32X.
	* gas/i386/mixed-mode-reloc32.d: Likewise.
	* gas/i386/reloc32.d: Likewise.

include/elf/

	* i386.h (R_386_GOT32X): New relocation.

ld/testsuite/

	* ld-i386/branch1.d: New file.
	* ld-i386/branch1.s: Likewise.
	* ld-i386/call1.d: Likewise.
	* ld-i386/call1.s: Likewise.
	* ld-i386/call2.d: Likewise.
	* ld-i386/call2.s: Likewise.
	* ld-i386/got1.dd: Likewise.
	* ld-i386/got1.out: Likewise.
	* ld-i386/got1a.S: Likewise.
	* ld-i386/got1b.c: Likewise.
	* ld-i386/got1c.c: Likewise.
	* ld-i386/got1d.S: Likewise.
	* ld-i386/jmp1.d: Likewise.
	* ld-i386/jmp1.s: Likewise.
	* ld-i386/jmp2.d: Likewise.
	* ld-i386/jmp2.s: Likewise.
	* ld-i386/load1.d: Likewise.
	* ld-i386/load1.s: Likewise.
	* ld-i386/load2.d: Likewise.
	* ld-i386/load2.s: Likewise.
	* ld-i386/load3.d: Likewise.
	* ld-i386/load3.s: Likewise.
	* ld-i386/load4.s: Likewise.
	* ld-i386/load4a.d: Likewise.
	* ld-i386/load4b.d: Likewise.
	* ld-i386/load5.s: Likewise.
	* ld-i386/load5a.d: Likewise.
	* ld-i386/load5b.d: Likewise.
	* ld-i386/load6.d: Likewise.
	* ld-i386/load6.s: Likewise.
	* ld-i386/i386.exp: Run branch1, call1, call2, jmp1, jmp2,
	load1, load2, load3, load4a, load4b, load5a, load5b and load6
	tests.  Run got1 test.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] S/390: ifunc: Fix PR18841.
@ 2015-10-22  9:17 sergiodj+buildbot
  2015-10-22 11:33 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-10-22  9:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0f042c67a04d5d0c8f879c27d651a7ed5aa6566f ***

Author: Andreas Krebbel <krebbel@linux.vnet.ibm.com>
Branch: master
Commit: 0f042c67a04d5d0c8f879c27d651a7ed5aa6566f

S/390: ifunc: Fix PR18841.

In order to get the ifunc relocs properly sorted the correct class
needs to be returned.  The code mimics what has been done for x86.

bfd/ChangeLog:

	PR ld/18841
	* elf32-s390.c (elf_s390_reloc_type_class): Return
	reloc_class_ifunc for ifunc symbols.
	* elf64-s390.c (elf_s390_reloc_type_class): Likewise.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] S/390: Get rid of superfluous parameter to s390_elf_allocate_ifunc_dyn_relocs.
@ 2015-10-22  8:26 sergiodj+buildbot
  2015-10-22  9:18 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-10-22  8:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 61643fbadb17932965e5c02db75ec3f8e211d7b1 ***

Author: Andreas Krebbel <krebbel@linux.vnet.ibm.com>
Branch: master
Commit: 61643fbadb17932965e5c02db75ec3f8e211d7b1

S/390: Get rid of superfluous parameter to s390_elf_allocate_ifunc_dyn_relocs.

bfd/ChangeLog:
	* elf-s390-common.c (s390_elf_allocate_ifunc_dyn_relocs): Remove
	`head' parameter.
	* elf32-s390.c (allocate_dynrelocs): Don't use last parameter.
	* elf64-s390.c (allocate_dynrelocs): Don't use last parameter.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Fix accessing a function's fields (parameters) from Python (PR 18073)
@ 2015-10-21 20:12 sergiodj+buildbot
  2015-10-22  5:46 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-10-21 20:12 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bed91f4da252b5f30d3cb4fd9f9febd61ad9560d ***

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

Fix accessing a function's fields (parameters) from Python (PR 18073)

Since 7.4, gdb doesn't allow calling .fields() on a function type, even
though the documentation states it should return a list corresponding to
the function's parameters.  This patch restores the intended behaviour
and adds a test for it.

Reg-tested on Arch Linux x86-64.

gdb/ChangeLog:

	PR python/18073
	* python/py-type.c (typy_get_composite): Allow returning a
	function type.

gdb/testsuite/ChangeLog:

	PR python/18073
	* gdb.python/py-type.c (C::a_method): New.
	(C::a_const_method): New.
	(C::a_static_method): New.
	(a_function): New.
	* gdb.python/py-type.exp (test_fields): Test getting fields
	from function and method.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Support software breakpoints for ARM linux in GDBServer.
@ 2015-10-21 17:31 sergiodj+buildbot
  2015-10-21 22:46 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-10-21 17:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT abeead094ef75fb896c9cabce8bf7b91da0a552c ***

Author: Antoine Tremblay <antoine.tremblay@ericsson.com>
Branch: master
Commit: abeead094ef75fb896c9cabce8bf7b91da0a552c

Support software breakpoints for ARM linux in GDBServer.

This patch enables software breakpoints via GDB's Z0 packets on ARM.

No regressions, tested on ubuntu 14.04 ARMv7 and x86.
With gdbserver-{native,extended} / { -marm -mthumb }

gdb/gdbserver/ChangeLog:

	* linux-arm-low.c (arm_supports_z_point_type): Add software
	breakpoint support.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Adjust timeout in gdb.base/freebpcmd.exp.
@ 2015-10-21 17:05 sergiodj+buildbot
  2015-10-21 23:37 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-10-21 17:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 27145d50705b46e213f5f261bd07572383c79e20 ***

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

Adjust timeout in gdb.base/freebpcmd.exp.

2015-10-21  Sandra Loosemore  <sandra@codesourcery.com>

	gdb/testsuite/
	* gdb.base/freebpcmd.exp: Use with_timeout_factor instead
	of hardwired timeout value.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Refactor the breakpoint definitions in linux-arm-low.c.
@ 2015-10-21 15:57 sergiodj+buildbot
  2015-10-21 21:37 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-10-21 15:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b0b4b5019484fbf1dd074527270f193703411498 ***

Author: Antoine Tremblay <antoine.tremblay@ericsson.com>
Branch: master
Commit: b0b4b5019484fbf1dd074527270f193703411498

Refactor the breakpoint definitions in linux-arm-low.c.

Before arm_sw_breakpoint_from_kind would use an #ifdef to return the right
arm_breakpoint from the abi or eabi breakpoint type.

arm_breakpoint_at would also check for the arm_breakpoint ||
arm_eabi_breakpoint.

Thus the selected arm_breakpoint would be what arm_sw_breakpoint_from_kind
returned and arm_breakpoint was arm_abi_breakpoint.

This patch makes it more clear by naming those for what they are : 2 separate
entities: arm_abi_breakpoint and arm_eabi_breakpoint and set the current used
one as arm_breakpoint.

This allows a cleaner arm_sw_breakpoint_from_kind as it just returns
arm_breakpoint rather than having the #ifdef in that function.

Any other reference to the arm_breakpoint can now also be clear of #ifdefs...

No regressions on Ubuntu 14.04 on ARMv7 and x86.
With gdbserver-{native,extended} / { -marm -mthumb }

gdb/gdbserver/ChangeLog:

	* linux-arm-low.c: Refactor breakpoint definitions.
	(arm_breakpoint_at): Adjust for arm_abi_breakpoint.
	(arm_sw_breakpoint_from_kind): Adjust for arm_breakpoint.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Support breakpoint kinds for software breakpoints in GDBServer.
@ 2015-10-21 15:42 sergiodj+buildbot
  2015-10-21 19:38 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-10-21 15:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2716529498941971b698f603e9aa0edc89905cb8 ***

Author: Antoine Tremblay <antoine.tremblay@ericsson.com>
Branch: master
Commit: 2716529498941971b698f603e9aa0edc89905cb8

Support breakpoint kinds for software breakpoints in GDBServer.

There's two ways to set breakpoints in GDBServer.

 - GDBServer setting its own breakpoints, through API set_breakpoint_at.

 - GDBServer setting breakpoints according to the information in Z
   packets, through API set_gdb_breakpoint.

Before this patch the breakpoint kinds were a concept unique to GDB and Z
packets, as GDBServer never had to set different kinds of breakpoint on its
own.

This patch teaches GDBServer to handle breakpoint kinds for its own
breakpoints. It generalizes the breakpoint kind as per Z packets to
represent different kinds of breakpoints directly set by GDBServer also.

GDBServer now querys breakpoint_kind_from_pc to know what breakpoint kind to
set on its own.

As the kind is now a differentiating factor equivalent to size for the
breakpoint struct and that it's size can be queried using
sw_breakpoint_from_kind, the size field has been replaced with the kind field.
All references to size are now replaced by kind or a call to bp_size that wraps
sw_breakpoing_from_kind and returns the size of the breakpoint in memory.

To fetch the software breakpoint data bp_opcode is called and wraps the
sw_breakpoint_from_kind call.

No regressions on Ubuntu 14.04 on ARMv7 and x86.
With gdbserver-{native,extended} / { -marm -mthumb }

gdb/gdbserver/ChangeLog:

	* linux-low.c (initialize_low): Ajdust for breakpoint global variables
	removal.
	* mem-break.c : Remove breakpoint_data/breakpoint_len global variables.
	(struct raw_breakpoint) <size>: Remove.
	(struct raw_breakpoint) <kind>: Add.
	(bp_size): New function.
	(bp_opcode): Likewise.
	(find_raw_breakpoint_at): Adjust for kind.
	(insert_memory_breakpoint): Adjust for kind call bp_size,bp_opcode.
	(remove_memory_breakpoint): Adjust for kind call bp_size.
	(set_raw_breakpoint_at): Adjust for kind.
	(set_breakpoint): Likewise.
	(set_breakpoint_at): Call breakpoint_kind_from_pc.
	(delete_raw_breakpoint): Adjust for kind.
	(delete_breakpoint): Likewise.
	(find_gdb_breakpoint): Likewise.
	(set_gdb_breakpoint_1): Likewise.
	(set_gdb_breakpoint): Likewise.
	(delete_gdb_breakpoint_1): Likewise.
	(delete_gdb_breakpoint): Likewise.
	(uninsert_raw_breakpoint): Likewise.
	(reinsert_raw_breakpoint): Likewise.
	(set_breakpoint_data): Remove.
	(validate_inserted_breakpoint): Adjust for kind call bp_size,bp_opcode.
	(check_mem_read): Adjust for kind call bp_size.
	(check_mem_write): Adjust for kind call bp_size,bp_opcode.
	(clone_one_breakpoint): Adjust for kind.
	* mem-break.h (set_gdb_breakpoint): Likewise.
	(delete_gdb_breakpoint): Likewise.
	* server.c (process_serial_event): Likewise.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Add the target_ops needed for software breakpoints in GDBServer.
@ 2015-10-21 15:35 sergiodj+buildbot
  2015-10-21 18:38 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-10-21 15:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT dd373349578df87396bc43e7ab00a1a5ceb16c8b ***

Author: Antoine Tremblay <antoine.tremblay@ericsson.com>
Branch: master
Commit: dd373349578df87396bc43e7ab00a1a5ceb16c8b

Add the target_ops needed for software breakpoints in GDBServer.

This patch is in preparation for software breakpoints on ARM linux.  It
refactors breakpoint and breakpoint_len into breakpoint_kind_from_pc and
sw_breakpoint_from kind to prepare the case where we have multiple types of
breakpoints.

Kind is the type of breakpoint (hardware or software) to be inserted, usually it
is the lenght of the software breakpoint but can be something else depending on
the target.

This patch introduces the linux_target_ops breakpoint_kind_from_pc and
sw_breakpoint_from_kind.

breakpoint_kind_from_pc returns the breakpoint kind and adjusts the PC to the
real memory location in case a flag was present in the PC. E.g the instruction
mode on ARM.

sw_breakpoint_from_kind returns the software breakpoint for this kind as a
string of bytes, the length of the breakpoint is adjusted for the breakpoint's
size in memory.

For targets that have only one kind of breakpoint, the default value 0 is
returned by linux_breakpoint_kind_from_pc so that not all targets need to
implement the breakpoint_kind_from_pc operation.

No regressions, tested on Ubuntu 14.04 on ARMv7 and x86
With gdbserver-{native,extended} / { -marm -mthumb }

Also since the target_ops have been changed compilation was tested on
affected archs namely : aarch64, arm, bfin, cris, crisv32, m32r,
m68k, mips, nios2, ppc, s390, sparc, tic6x, tile, x86, steins.

Not tested : sh

gdb/gdbserver/ChangeLog:

	* linux-aarch64-low.c (aarch64_sw_breakpoint_from_kind): New function.
	(struct linux_target_ops) <breakpoint>: Remove.
	(struct linux_target_ops) <breakpoint_len>: Remove.
	(struct linux_target_ops) <breakpoint_kind_from_pc>: Initialize field.
	(struct linux_target_ops) <sw_breakpoint_from_kind>: Initialize field.
	* linux-arm-low.c (arm_breakpoint_kind_from_pc): New function.
	(arm_sw_breakpoint_from_kind): New function.
	* linux-bfin-low.c (bfin_sw_breakpoint_from_kind): New function.
	(struct linux_target_ops) <breakpoint>: Remove.
	(struct linux_target_ops) <breakpoint_len>: Remove.
	(struct linux_target_ops) <breakpoint_kind_from_pc>: Initialize field.
	(struct linux_target_ops) <sw_breakpoint_from_kind>: Initialize field.
	* linux-cris-low.c (cris_sw_breakpoint_from_kind): New function.
	(struct linux_target_ops) <breakpoint>: Remove.
	(struct linux_target_ops) <breakpoint_len>: Remove.
	(struct linux_target_ops) <breakpoint_kind_from_pc>: Initialize field.
	(struct linux_target_ops) <sw_breakpoint_from_kind>: Initialize field.
	* linux-crisv32-low.c (cris_sw_breakpoint_from_kind): New function.
	(struct linux_target_ops) <breakpoint>: Remove.
	(struct linux_target_ops) <breakpoint_len>: Remove.
	(struct linux_target_ops) <breakpoint_kind_from_pc>: Initialize field.
	(struct linux_target_ops) <sw_breakpoint_from_kind>: Initialize field.
	* linux-low.c (linux_wait_1): Call breakpoint_kind_from_pc
	and sw_breakpoint_from_kind to increment the pc.
	(linux_breakpoint_kind_from_pc): New function.
	(linux_sw_breakpoint_from_kind): New function.
	(struct target_ops) <sw_breakpoint_from_kind>: Initialize field.
	(initialize_low): Call breakpoint_kind_from_pc and
	sw_breakpoint_from_kind to replace breakpoint_data/len.
	* linux-low.h (struct linux_target_ops) <breakpoint_kind_from_pc>:
	New field.
	(struct linux_target_ops) <sw_breakpoint_from_kind>: Likewise.
	* linux-m32r-low.c (m32r_sw_breakpoint_from_kind): New function.
	(struct linux_target_ops) <breakpoint>: Remove.
	(struct linux_target_ops) <breakpoint_len>: Remove.
	(struct linux_target_ops) <breakpoint_kind_from_pc>: Initialize field.
	(struct linux_target_ops) <sw_breakpoint_from_kind>: Initialize field.
	* linux-m68k-low.c (m68k_sw_breakpoint_from_kind): New function.
	(struct linux_target_ops) <breakpoint>: Remove.
	(struct linux_target_ops) <breakpoint_len>: Remove.
	(struct linux_target_ops) <breakpoint_kind_from_pc>: Initialize field.
	(struct linux_target_ops) <sw_breakpoint_from_kind>: Initialize field.
	* linux-mips-low.c (mips_sw_breakpoint_from_kind): New function.
	(struct linux_target_ops) <breakpoint>: Remove.
	(struct linux_target_ops) <breakpoint_len>: Remove.
	(struct linux_target_ops) <breakpoint_kind_from_pc>: Initialize field.
	(struct linux_target_ops) <sw_breakpoint_from_kind>: Initialize field.
	* linux-nios2-low.c (nios2_sw_breakpoint_from_kind): New function.
	(struct linux_target_ops) <breakpoint>: Remove.
	(struct linux_target_ops) <breakpoint_len>: Remove.
	(struct linux_target_ops) <breakpoint_kind_from_pc>: Initialize field.
	(struct linux_target_ops) <sw_breakpoint_from_kind>: Initialize field.
	* linux-ppc-low.c (ppc_sw_breakpoint_from_kind): New function.
	(struct linux_target_ops) <breakpoint>: Remove.
	(struct linux_target_ops) <breakpoint_len>: Remove.
	(struct linux_target_ops) <breakpoint_kind_from_pc>: Initialize field.
	(struct linux_target_ops) <sw_breakpoint_from_kind>: Initialize field.
	* linux-s390-low.c (s390_sw_breakpoint_from_kind): New function.
	(struct linux_target_ops) <breakpoint>: Remove.
	(struct linux_target_ops) <breakpoint_len>: Remove.
	(struct linux_target_ops) <breakpoint_kind_from_pc>: Initialize field.
	(struct linux_target_ops) <sw_breakpoint_from_kind>: Initialize field.
	* linux-sh-low.c (sh_sw_breakpoint_from_kind): New function.
	(struct linux_target_ops) <breakpoint>: Remove.
	(struct linux_target_ops) <breakpoint_len>: Remove.
	(struct linux_target_ops) <breakpoint_kind_from_pc>: Initialize field.
	(struct linux_target_ops) <sw_breakpoint_from_kind>: Initialize field.
	* linux-sparc-low.c (sparc_sw_breakpoint_from_kind): New function.
	(struct linux_target_ops) <breakpoint>: Remove.
	(struct linux_target_ops) <breakpoint_len>: Remove.
	(struct linux_target_ops) <breakpoint_kind_from_pc>: Initialize field.
	(struct linux_target_ops) <sw_breakpoint_from_kind>: Initialize field.
	* linux-tic6x-low.c (tic6x_sw_breakpoint_from_kind): New function.
	(struct linux_target_ops) <breakpoint>: Remove.
	(struct linux_target_ops) <breakpoint_len>: Remove.
	(struct linux_target_ops) <breakpoint_kind_from_pc>: Initialize field.
	(struct linux_target_ops) <sw_breakpoint_from_kind>: Initialize field.
	* linux-tile-low.c (tile_sw_breakpoint_from_kind): New function.
	* linux-x86-low.c (x86_sw_breakpoint_from_kind): New function.
	(struct linux_target_ops) <breakpoint>: Remove.
	(struct linux_target_ops) <breakpoint_len>: Remove.
	(struct linux_target_ops) <breakpoint_kind_from_pc>: Initialize field.
	(struct linux_target_ops) <sw_breakpoint_from_kind>: Initialize field.
	* linux-xtensa-low.c (xtensa_sw_breakpoint_from_kind) New function.
	(struct linux_target_ops) <breakpoint>: Remove.
	(struct linux_target_ops) <breakpoint_len>: Remove.
	(struct linux_target_ops) <breakpoint_kind_from_pc>: Initialize field.
	(struct linux_target_ops) <sw_breakpoint_from_kind>: Initialize field.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [nto] Fix nto target stopped by watchpoint.
@ 2015-10-21 14:47 sergiodj+buildbot
  2015-10-21 15:39 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-10-21 14:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a9889169e5b21efb8c42105fc62461be43968d64 ***

Author: Aleksandar Ristovski <aristovski@qnx.com>
Branch: master
Commit: a9889169e5b21efb8c42105fc62461be43968d64

[nto] Fix nto target stopped by watchpoint.

Fix 'stopped by watchpoint' detection: add inferior data, use inferior data
for storing last stopped flags needed for detection.

gdb/ChangeLog:

	* nto-procfs.c (procfs_wait): Set stopped_flags nad stopped_pc.
	(procfs_stopped_by_watchpoint): Use flags stored in inferior data.
	* nto-tdep.c (nto_new_inferior_data_reg): New definition.
	(nto_new_inferior_data, nto_inferior_data_cleanup, nto_inferior_data):
	New functions.
	(_initialize_nto_tdep): New forward declaration, new function.
	* nto-tdep.h (struct nto_inferior_data): New struct.
	(nto_inferior_data): New function declaration.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Fix internal error on DW_OP_bregx(-1)
@ 2015-10-20 18:50 sergiodj+buildbot
  2015-10-20 21:07 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-10-20 18:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5f3ff4f893d7d70f79cb2daf4001be7047cd126b ***

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

Fix internal error on DW_OP_bregx(-1)

https://bugzilla.redhat.com/show_bug.cgi?id=1270564#c15
https://bugzilla.redhat.com/attachment.cgi?id=1081772

clang-3.5.0-9.fc22.x86_64
 <3><22b2>: Abbrev Number: 69 (DW_TAG_variable)
    <22b3>   DW_AT_location    : 7 byte block: 92 ff ff ff ff f 0	(DW_OP_bregx: 4294967295 (r-1) 0)
    <22bb>   DW_AT_name        : (indirect string, offset: 0x2a36): texture_data
    <22c1>   DW_AT_type        : <0x1d3>

(gdb) p variable
warning: Unmapped DWARF Register #-1 encountered.
regcache.c:177: internal-error: register_size: Assertion `regnum >= 0 && regnum < (gdbarch_num_regs (gdbarch) + gdbarch_num_pseudo_regs
(gdbarch))' failed.
[...]
Quit this debugging session? (y or n) FAIL: gdb.dwarf2/dw2-regno-invalid.exp: p variable (GDB internal error)

-> (x86_64)
(gdb) p variable
warning: Unmapped DWARF Register #-1 encountered.
Invalid register #-1, expecting 0 <= # < 220
(gdb) PASS: gdb.dwarf2/dw2-regno-invalid.exp: p variable
-> (i386)
(gdb) p variable
Invalid register #104, expecting 0 <= # < 104
(gdb) PASS: gdb.dwarf2/dw2-regno-invalid.exp: p variable

GDB calls gdbarch_dwarf2_reg_to_regnum() first which returns -1 in the x86_64
case
  if (regnum == -1)
    warning (_("Unmapped DWARF Register #%d encountered."), reg);
but in i386 case it does:
  /* This will hopefully provoke a warning.  */
  return gdbarch_num_regs (gdbarch) + gdbarch_num_pseudo_regs (gdbarch);
and the default implementation is a nop, leaving whatever register number
the DWARF specified.

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

	* findvar.c (address_from_register): Check REGNUM validity.

gdb/testsuite/ChangeLog
2015-10-20  Jan Kratochvil  <jan.kratochvil@redhat.com>
	    Pedro Alves  <palves@redhat.com>

	* gdb.dwarf2/dw2-regno-invalid.exp: New file.
	* lib/dwarf.exp (Dwarf): Add DW_OP_bregx.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [nto] Fixes for nto procfs.
@ 2015-10-20 17:16 sergiodj+buildbot
  2015-10-20 18:08 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-10-20 17:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 609c3040c2df944239d4d96644d736df605a6831 ***

Author: Aleksandar Ristovski <aristovski@qnx.com>
Branch: master
Commit: 609c3040c2df944239d4d96644d736df605a6831

[nto] Fixes for nto procfs.

Fix errnoeus construction of procfs path. The issue is, after the first
info pidlist or first run, the path for local node (the most common node)
will be reset to empty which makes subsequent queries and runs impossible.

gdb/ChangeLog:

	* nto-procfs.c (nto_procfs_path): Rename to...
	(nodestr): ... this, and change type.
	(nto_node): Use new variable and logic accordingly.
	(procfs_open_1): Use new variable name. Use local buffer to construct
	procfrs path.
	(procfs_pidlist): Use NODESTR to construct procfs path.
	(procfs_files_info): Use NODESTR to output meaningful text.
	(do_attach): Construct procfs using NODESTR.
	(procfs_create_inferior): Compare pointer to NULL.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Make GDB wait for events after handling target File-I/O
@ 2015-10-19 13:46 sergiodj+buildbot
  2015-10-19 14:38 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-10-19 13:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 29090fb629734b7980f058f4a7e24a0369e9bb49 ***

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

Make GDB wait for events after handling target File-I/O

_ftext () at arm-vector.S:25
25              ldr pc, [pc, #24] @ reset
(gdb) load
Loading section .text, size 0xc01c lma 0x0
Loading section .eh_frame, size 0x48 lma 0xc01c
Loading section .ARM.exidx, size 0x8 lma 0xc064
Loading section .rodata, size 0x398 lma 0xc070
Loading section .data, size 0x8e0 lma 0xc408
Start address 0x40, load size 52452
Transfer rate: 17074 KB/sec, 1748 bytes/write.
(gdb) c
Continuing.
infrun: clear_proceed_status_thread (Thread 1)
infrun: proceed (addr=0xffffffff, signal=GDB_SIGNAL_DEFAULT)
infrun: resume (step=0, signal=GDB_SIGNAL_0), trap_expected=0, current thread [Thread 1] at 0x40
Sending packet: $vCont?#49...Ack
Packet received:
Packet vCont (verbose-resume) is NOT supported
Sending packet: $Hc0#db...Ack
Packet received: OK
Sending packet: $c#63...Ack
infrun: infrun_async(1)
infrun: prepare_to_wait
infrun: target_wait (-1.0.0, status) =
infrun:   -1.0.0 [Thread 0],
infrun:   status->kind = ignore
infrun: TARGET_WAITKIND_IGNORE
infrun: prepare_to_wait
Packet received: Ffstat,00000001,07fffdb0
Sending packet: $M7fffdb0,40:000000000000000000002080000000010000c336000001180000000000000000000000000000000000000200000000000000000055dfb11b55dfb11b55dfb11b#5a...Ack
Packet received: OK
Sending packet: $F0#76...Ack
infrun: target_wait (-1.0.0, status) =
infrun:   -1.0.0 [Thread 0],
infrun:   status->kind = ignore
infrun: TARGET_WAITKIND_IGNORE
infrun: prepare_to_wait
infrun: target_wait (-1.0.0, status) =
infrun:   -1.0.0 [Thread 0],
infrun:   status->kind = no-resumed
infrun: TARGET_WAITKIND_NO_RESUMED
infrun: stop_waiting
infrun: clear_step_over_info
Sending packet: $qfThreadInfo#bb...Ack
Packet received: m1
Sending packet: $qsThreadInfo#c8...Ack
Packet received: l
No unwaited-for children left.
infrun: infrun_async(0)
(gdb) c
Continuing.
Cannot execute this command while the selected thread is running.
(gdb)
Continuing.
Cannot execute this command while the selected thread is running.

This behavior shows up whenever GDB is in all-stop mode and is handling
target-initiated File-I/O requests, in the middle of, say, a continue
request.

When GDB is done handling the File-I/O request, it doesn't set
rs->waiting_for_stop_reply back to 1, meaning GDB should wait for
further target events.

This seems to be a latent bug, because in the past this didn't really
cause any issues. But it seems to have been uncovered by commit
567420d10895611e03d5ee65e6b24c16a69a6e99, which explicitly checks
for rs->waiting_for_stop_reply == 0, triggering the failures above.

The following patch fixes this by reorganizing the setting of
rs->waiting_for_stop_reply.

infrun: prepare_to_wait
Packet received: Ffstat,00000001,07fffdb0
Sending packet: $M7fffdb0,40:000000000000000000002080000000010000c336000001180000000000000000000000000000000000000200000000000000000055dfb19e55dfb19e55dfb19e#7b...Ack
Packet received: OK
Sending packet: $F0#76...Ack
infrun: target_wait (-1.0.0, status) =
infrun:   -1.0.0 [Thread 0],
infrun:   status->kind = ignore
infrun: TARGET_WAITKIND_IGNORE
infrun: prepare_to_wait
Packet received: Fisatty,00000001
Sending packet: $F1#77...Ack
infrun: target_wait (-1.0.0, status) =
infrun:   -1.0.0 [Thread 0],
infrun:   status->kind = ignore
infrun: TARGET_WAITKIND_IGNORE
infrun: prepare_to_wait
Packet received: Fwrite,00000001,0000d098,00000004
Sending packet: $md098,4#d2...Ack
Packet received: 3732300a
720
Sending packet: $F4#7a...Ack
infrun: target_wait (-1.0.0, status) =
infrun:   -1.0.0 [Thread 0],
infrun:   status->kind = ignore
infrun: TARGET_WAITKIND_IGNORE
infrun: prepare_to_wait
Packet received: Fwrite,00000001,07ffffac,00000011
Sending packet: $m7ffffac,11#8e...Ack
Packet received: 0a2a2a2a204558495420636f646520300a

*** EXIT code 0

Regression-tested on Ubuntu x86-64 and qemu-system-based debugging
for arm eabi.

gdb/ChangeLog:

2015-10-16  Luis Machado  <lgustavo@codesourcery.com>

	* remote.c (remote_wait_as): Set rs->waiting_for_stop_reply to 0
	when handling 'E', 'T', 'S', 'X' and 'W' packets.
	Do not set rs->waiting_for_stop_reply back to 1.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Robustify inherit.exp and virtbase.exp.
@ 2015-10-19 10:26 sergiodj+buildbot
  2015-10-19 11:18 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-10-19 10:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b32b93c614de5ef1319eaa002e481094357018ff ***

Author: Andrew Stubbs <ams@codesourcery.com>
Branch: master
Commit: b32b93c614de5ef1319eaa002e481094357018ff

Robustify inherit.exp and virtbase.exp.

2015-10-19  Andrew Stubbs  <ams@codesourcery.com>

	gdb/testsuite/
	* gdb.cp/inherit.exp (print g_vB, print g_vC, print g_vD,
	print g_vE): Add new pass patterns.
	* gdb.cp/virtbase.exp (print *this, print *(D *) e): Allow GDB to
	print various symbol names for vptr fields.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [nto] Fix nto build.
@ 2015-10-16 16:01 sergiodj+buildbot
  2015-10-16 17:51 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-10-16 16:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 774ee6d252eba19d3e23c936d14bfc1f7fa70651 ***

Author: Aleksandar Ristovski <aristovski@qnx.com>
Branch: master
Commit: 774ee6d252eba19d3e23c936d14bfc1f7fa70651

[nto] Fix nto build.

gdb/gdbserver/ChangeLog:

	* gdbserver/nto-low.c (nto_insert_point, nto_remove_point): Fix
	variable name.

gdb/ChangeLog:

	* nto-procfs.c (common/filestuff.h): Include.
	(procfs_can_use_hw_breakpoint): Fix enum name.
	(procfs_open_1): Fix compiler warning.
	(procfs_pidlist): Make static.
	(procfs_meminfo): Make static, fix type name, add missing argument.
	(procfs_store_registers): Make static.
	(procfs_thread_info): Remove unused function.
	(_initialize_procfs): Forward declare.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Convert mov to lea for loading address of local common symbol
@ 2015-10-16 12:22 sergiodj+buildbot
  2015-10-16 13:23 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-10-16 12:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b31bcacc489d6ede2e9bdfa9905de0ebfd919454 ***

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

Convert mov to lea for loading address of local common symbol

There is no need to check def_regular when converting mov to lea for
loading address of local symbols since def_regular may be false for
common symbols and SYMBOL_REFERENCES_LOCAL is sufficient.

bfd/

	* elf32-i386.c (elf_i386_convert_mov_to_lea): Don't check
	def_regular.
	* elf64-x86-64.c (elf_x86_64_convert_mov_to_lea): Likewise.

ld/testsuite/

	* ld-i386/lea1.s: Add a test for loading address of local common
	symbol.
	* ld-x86-64/lea1.s: Likewise.
	* ld-i386/lea1a.d: Updated.
	* ld-i386/lea1b.d: Likewise.
	* ld-i386/lea1c.d: Likewise.
	* ld-x86-64/lea1a.d: Likewise.
	* ld-x86-64/lea1b.d: Likewise.
	* ld-x86-64/lea1c.d: Likewise.
	* ld-x86-64/lea1d.d: Likewise.
	* ld-x86-64/lea1e.d: Likewise.
	* ld-x86-64/lea1f.d: Likewise.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Recognize a few more AIX XCOFF DWARF sections.
@ 2015-10-13 22:55 sergiodj+buildbot
  2015-10-14  4:01 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-10-13 22:55 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 33f914a197fa8cd4338396e7d62a5f26621f183c ***

Author: David Edelsohn <dje.gcc@gmail.com>
Branch: master
Commit: 33f914a197fa8cd4338396e7d62a5f26621f183c

Recognize a few more AIX XCOFF DWARF sections.

gdb/ChangeLog:

        * xcoffread.c (dwarf2_xcoff_names): Add .dwmac and .dwpbtyp.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] ada-lang.c:ada_value_primitive_packed_val: const correctness
@ 2015-10-13 18:58 sergiodj+buildbot
  2015-10-13 21:30 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-10-13 18:58 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bfb1c7963b15b31073c9adf2d97ff1cf953ec99c ***

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

ada-lang.c:ada_value_primitive_packed_val: const correctness

gdb/ChangeLog:
2015-10-13  Pedro Alves  <palves@redhat.com>

	* ada-lang.c (ada_value_primitive_packed_val): Constify
	locals.  Use value_contents_writeable.  Remove casts.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] ada-lang.c: malloc/alloca casts for C++
@ 2015-10-13 18:50 sergiodj+buildbot
  2015-10-13 20:30 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-10-13 18:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT aa5c10ce9b1bd04a7f4a619d5e956c977fcd60d3 ***

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

ada-lang.c: malloc/alloca casts for C++

gdb/ChangeLog:
2015-10-13  Pedro Alves  <palves@redhat.com>

	* ada-lang.c (ada_value_primitive_packed_val): Add casts to malloc
	and alloca calls.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Tidy code setting PT_GNU_RELRO p_flags
@ 2015-10-13  6:14 sergiodj+buildbot
  2015-10-13 13:10 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-10-13  6:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 341b8ee719163f7ae8528f2a7832381887fbf8d8 ***

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

Tidy code setting PT_GNU_RELRO p_flags

No functional changes here.

	* elf.c (_bfd_elf_map_sections_to_segments): Don't set
	PT_GNU_RELRO p_flags.
	(assign_file_positions_for_non_load_sections): Set PT_GNU_RELRO
	flags to PF_R here.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
[parent not found: <1f713e48f024e964f5a4f5468bc9506dac262763@gdb-build>]
* [binutils-gdb] Mention the change in NEWS
@ 2015-10-12 12:01 sergiodj+buildbot
  2015-10-12 22:33 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-10-12 12:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT eda14cf2590aaab147d298418a3b7773b8d63ce5 ***

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

Mention the change in NEWS

gdb:

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

	* NEWS: Mention the change.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Rename emit_load_store to  aarch64_emit_load_store
@ 2015-10-12 11:53 sergiodj+buildbot
  2015-10-12 21:33 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-10-12 11:53 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1c2e1515c45af104fc9b2aea6bd6b1471238dd98 ***

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

Rename emit_load_store to  aarch64_emit_load_store

Likewise, this patch renames emit_load_store to
aarch64_emit_load_store.

gdb:

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

	* arch/aarch64-insn.c (emit_load_store): Rename to ...
	(aarch64_emit_load_store): ... it.  All callers updated.

gdb/gdbserver:

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

	* linux-aarch64-low.c: Update all callers as emit_load_store
	is renamed to aarch64_emit_load_store.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] New test case gdb.arch/disp-step-insn-reloc.exp
@ 2015-10-12 11:36 sergiodj+buildbot
  2015-10-12 19:35 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-10-12 11:36 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0fd8ac1c450d340d0b11823107d9e990341e7e11 ***

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

New test case gdb.arch/disp-step-insn-reloc.exp

This patch adds a new test case which uses gdb.arch/insn-reloc.c too
to test displaced stepping.  Nowadays, tests are for x86, x86_64 and
aarch64.

gdb/testsuite:

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

	* gdb.arch/disp-step-insn-reloc.exp: New test case.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Move aarch64_relocate_instruction to arch/aarch64-insn.c
@ 2015-10-12 11:13 sergiodj+buildbot
  2015-10-12 16:39 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-10-12 11:13 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 246994ce350923199a4c952b38dcee5bcbe8c554 ***

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

Move aarch64_relocate_instruction to arch/aarch64-insn.c

This patch moves aarch64_relocate_instruction and visitor class to
arch/aarch64-insn.c, so that both GDB and GDBserver can use it.

gdb:

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

	* arch/aarch64-insn.c (aarch64_decode_ldr_literal): Moved from
	gdbserver/linux-aarch64-low.c.
	(aarch64_relocate_instruction): Likewise.
	* arch/aarch64-insn.h (aarch64_decode_ldr_literal): Declare.
	(struct aarch64_insn_data): Moved from
	gdbserver/linux-aarch64-low.c.
	(struct aarch64_insn_visitor): Likewise.
	(aarch64_relocate_instruction): Declare.

gdb/gdbserver:

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

	* linux-aarch64-low.c (extract_signed_bitfield): Remove.
	(aarch64_decode_ldr_literal): Move to gdb/arch/aarch64-insn.c.
	(aarch64_relocate_instruction): Likewise.
	(struct aarch64_insn_data): Move to gdb/arch/aarch64-insn.h.
	(struct aarch64_insn_visitor): Likewise.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Forward VALUE_LVAL when avoiding side effects for STRUCTOP_STRUCT
@ 2015-10-12 10:32 sergiodj+buildbot
  2015-10-12 11:23 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-10-12 10:32 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2520f728b710c0249cde01b8cfb4872a22ef10b6 ***

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

Forward VALUE_LVAL when avoiding side effects for STRUCTOP_STRUCT

Assume foo_array is a pointer to a C structure. GDB must evaluate the
following expression properly, but it does not currently:

    (gdb) print 1 && &foo_array[1].a
    Attempt to take address of value not located in memory.

The problem is that in EVAL_AVOID_SIDE_EFFECTS mode,
eval.c:evaluate_subexp_standard always returns a not_lval value as the
result for a STRUCTOP_STRUCT operation. As a consequence, the rest of
the code believes that one cannot take the address of the returned
value.

This patch fixes STRUCTOP_STRUCT handling so that the VALUE_LVAL
attribute for the returned value is properly initialized.  After this
change, the above session becomes:

    (gdb) print 1 && &foo_array[1].a
    $1 = 1

gdb/ChangeLog:

	* eval.c (evaluate_subexp_standard) <STRUCTOP_STRUCT>: If
	EVAL_AVOID_SIDE_EFFECTS mode, forward the VALUE_LVAL attribute
	to the returned value.

gdb/testsuite/ChangeLog:

	* gdb.base/nested-addr.c: New file.
	* gdb.base/nested-addr.exp: New testcase.

Tested on x86_64-linux, no regression.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Ignore references with relocs to discarded sections in .data.rel.ro.local on hppa-linux.
@ 2015-10-11 23:20 sergiodj+buildbot
  2015-10-12  0:58 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-10-11 23:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT da6e19a92645583da12dc2d15f54d2bd240fd3f2 ***

Author: John David Anglin <danglin@gcc.gnu.org>
Branch: master
Commit: da6e19a92645583da12dc2d15f54d2bd240fd3f2

Ignore references with relocs to discarded sections in .data.rel.ro.local on hppa-linux.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [Ada] ada_unpack_from_contents: Error if target buffer not large enough
@ 2015-10-09 22:39 sergiodj+buildbot
  2015-10-10 11:07 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-10-09 22:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5b639deae123db13af61e915807c0a1ab224e246 ***

Author: Joel Brobecker <brobecker@adacore.com>
Branch: master
Commit: 5b639deae123db13af61e915807c0a1ab224e246

[Ada] ada_unpack_from_contents: Error if target buffer not large enough

This adds a guard that the size of the "unpacked" buffer is large enough
to contain at least BIT_SIZE bits.  If not, report an error.  This is to
guard this routine from doing buffer overflows when called incorrectly.

gdb/ChangeLog:

        * ada-lang.c (ada_unpack_from_contents): Add guard that unpacked
        is large enough for BIT_SIZE.  Update function comment.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [Ada] Buffer overflow in ada_unpack_from_contents
@ 2015-10-09 22:31 sergiodj+buildbot
  2015-10-10 10:07 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-10-09 22:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0cafa88cc03786fb5794ca53e987e45fd09621f8 ***

Author: Joel Brobecker <brobecker@adacore.com>
Branch: master
Commit: 0cafa88cc03786fb5794ca53e987e45fd09621f8

[Ada] Buffer overflow in ada_unpack_from_contents

This patch fixes a buffer overflow in ada_unpack_from_contents
caused by one of the previous commits. This happens when trying
to print the value of an array of variant records.

The overflow happens while trying to print one element of the array.
Because the size of each element in the array is variable, the array
has a DWARF byte_stride attribute, which makes us treat the array
as if it was packed. And during the extraction of each array element,
we try to unpack an object using the array's byte stride as the size,
into an element whose size is actually less than the stride.

This patch fixes the issue by overriding the byte-stride with
the actual element's length.

gdb/ChangeLog:

        * ada-lang.c (ada_value_primitive_packed_val): Move
        src_len variable to local block where used.  Override
        BIT_SIZE if bigger than size of resolved type.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] make is_scalar_type non-static and use it in ada-lang.c
@ 2015-10-09 22:23 sergiodj+buildbot
  2015-10-10  9:10 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-10-09 22:23 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 220475ed8b0c1ef7b4eabf64bcc723e14fd78209 ***

Author: Joel Brobecker <brobecker@adacore.com>
Branch: master
Commit: 220475ed8b0c1ef7b4eabf64bcc723e14fd78209

make is_scalar_type non-static and use it in ada-lang.c

Just a small cleanup, to avoid code duplication...

gdb/ChangeLog:

        * gdbtypes.h (is_scalar_type): Add extern declaration.
        * gdbtypes.c (is_scalar_type): Make non-static.
        * ada-lang.c (ada_value_primitive_packed_val): Use is_scalar_type
        to compute IS_SCALAR instead of doing it ourselves.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Reorder variable declarations in ada_value_primitive_packed_val
@ 2015-10-09 22:00 sergiodj+buildbot
  2015-10-10  5:50 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-10-09 22:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a1c95e6b6ede168770664cdca8ae1568187554b4 ***

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

Reorder variable declarations in ada_value_primitive_packed_val

This patch just changes the order in which local variables are declared
so as to group the logically-related variables together.  No code
change otherwise.

gdb/ChangeLog:

        * ada-lang.c (ada_value_primitive_packed_val): Reorder local
        variable declarations.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] cris: Use enum bfd_endian to represent endianness
@ 2015-10-09 14:36 sergiodj+buildbot
  2015-10-09 20:03 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-10-09 14:36 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 78c5b882482b5435bb2dcf1c09a52683d54cb81e ***

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

cris: Use enum bfd_endian to represent endianness

gdb/ChangeLog:

	* cris-tdep.c (struct instruction_environment): Change type of
	byte_order to enum bfd_endian.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Fix typos in comments
@ 2015-10-09 13:32 sergiodj+buildbot
  2015-10-09 15:17 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-10-09 13:32 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f9acce4a4f411e78ebca90995c598ed231b104a3 ***

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

Fix typos in comments

gdb/

2015-10-09  Eli Zaretskii  <eliz@gnu.org>

	* stack.c (print_stack_frame):
	* utils.c (printchar): Fix typos in commentary.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Fix gdb.base/a2-run.exp race
@ 2015-10-09 12:07 sergiodj+buildbot
  2015-10-09 13:03 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-10-09 12:07 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 145e3ddb4b1657a1f29eb9f41f2d54d0bf26b6f0 ***

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

Fix gdb.base/a2-run.exp race

This patch fixes this racy failure, with the native-extended-gdbserver
board:

 (gdb) run
 Starting program: build/gdb/testsuite/outputs/gdb.base/a2-run/a2-run
 Remote debugging from host 127.0.0.1
 Process build/gdb/testsuite/outputs/gdb.base/a2-run/a2-run created; pid = 23832
 Reading /lib64/ld-linux-x86-64.so.2 from remote target...
 warning: File transfers from remote targets can be slow. Use "set sysroot" to access files locally instead.
 Reading /lib64/ld-linux-x86-64.so.2 from remote target...
 Reading /lib64/libm.so.6 from remote target...
 Reading /lib64/libc.so.6 from remote target...
 [Inferior 1 (process 23832) exited with code 01]
 (gdb) FAIL: gdb.base/a2-run.exp: run "a2-run" with no args
 PASS: gdb.base/a2-run.exp: no spurious messages at program exit
 run 5
 Starting program: build/gdb/testsuite/outputs/gdb.base/a2-run/a2-run 5
 Reading /lib64/ld-linux-x86-64.so.2 from remote target...
 usage:  factorial <number>

 Child exited with status 1

Note that the output is correct; it's just that inferior output
appeared after gdb's output, and the test doesn't handle that
correctly.

This comment isn't really correct, unfortunately:

	# waiting.  If we had already seen the status wrapper exit,
	# gdb_test_multiple/expect has no spawn ids left, and thus
	# returns.

That's true of expect in general, but I had missed / forgot that
gdb_test_multiple internally has extra matches using "-i
$gdb_spawn_id", so even if the caller clears all the indirect spawn id
lists, gdb_test_multiple will continue waiting.

So do a conditional exp_continue manually instead.

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

	* gdb.base/a2-run.exp (maybe_exp_continue): New procedure.
	(top level): Use it in the run with no args test.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Fix compile time warning compiling ARC port.
@ 2015-10-08 11:43 sergiodj+buildbot
  2015-10-08 12:35 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-10-08 11:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3f94e60d92d9bf67f1f8cbc19ffbfe5d28db7fcf ***

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

Fix compile time warning compiling ARC port.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] btrace: fix void return
@ 2015-10-08  7:41 sergiodj+buildbot
  2015-10-08  7:52 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-10-08  7:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 04c4fe8c59d3f2870a5df7be7f55fca60d88381f ***

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

btrace: fix void return

record_btrace_resume returns the void return from the to_resume method of the
target beneath.  Split this into calling to_resume and return.

gdb/
	* record-btrace.c (record_btrace_resume): Fix void return.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Avoid using 'template' C++ keyword
@ 2015-10-07 14:29 sergiodj+buildbot
  2015-10-07 14:39 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-10-07 14:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 875880c661e71a7622d8f7282f0dd1ef756040ff ***

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

Avoid using 'template' C++ keyword

'template' is used in include/opcode/aarch64.h as below,

 typedef struct
 {
   const char *template;
   uint32_t value;
   int has_xt;
 } aarch64_sys_ins_reg;

and it triggers compilation errors when GDB is built in C++ mode.

In file included from git/gdb/aarch64-tdep.c:62:0:
git/gdb/../include/opcode/aarch64.h:651:15: error: expected unqualified-id before 'template'
   const char *template;

This patch is to rename field template to name.

gas/

	* config/tc-aarch64.c (md_begin): Access field 'name' rather
	than 'template'.

include/opcode/

	* aarch64.h (aarch64_sys_ins_reg) <template>: Removed.
	<name>: New field.

opcodes/

	* aarch64-dis.c (aarch64_ext_sysins_op): Access field
	'name' rather than 'template'.
	* aarch64-opc.c (aarch64_print_operand): Likewise.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Wrap include/opcode/aarch64.h in extern "C" for C++
@ 2015-10-07 14:11 sergiodj+buildbot
  2015-10-07 14:21 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-10-07 14:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d3e12b29aef25bc9d1830b0a05643b11296f1b8f ***

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

Wrap include/opcode/aarch64.h in extern "C" for C++

This is sufficient to link an aarch64 GDB built in C++ mode.  Pedro
did something similar in Feb
https://sourceware.org/ml/binutils/2015-02/msg00176.html

include/opcode/

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

	* aarch64.h [__cplusplus]: Wrap in extern "C".


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] New ARC implementation.
@ 2015-10-07 13:26 sergiodj+buildbot
  2015-10-07 13:49 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-10-07 13:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 886a250647ac0c608f20a7007fc2167a70f64e20 ***

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

New ARC implementation.

bfd	* archures.c: Remove support for older ARC. Added support for new
	ARC cpus (ARC600, ARC601, ARC700, ARCV2).
	* bfd-in2.h: Likewise.
	* config.bfd: Likewise.
	* cpu-arc.c: Likewise.
	* elf32-arc.c: Totally changed file with a refactored
	inplementation of the ARC port.
	* libbfd.h: Added ARC specific relocation types.
	* reloc.c: Likewise.

gas     * config/tc-arc.c: Revamped file for ARC support.
        * config/tc-arc.h: Likewise.
        * doc/as.texinfo: Add new ARC options.
        * doc/c-arc.texi: Likewise.

ld	* configure.tgt: Added target arc-*-elf* and arc*-*-linux-uclibc*.
	* emulparams/arcebelf_prof.sh: New file
	* emulparams/arcebelf.sh: Likewise.
	* emulparams/arceblinux_prof.sh: Likewise.
	* emulparams/arceblinux.sh: Likewise.
	* emulparams/arcelf_prof.sh: Likewise.
	* emulparams/arcelf.sh: Likewise.
	* emulparams/arclinux_prof.sh: Likewise.
	* emulparams/arclinux.sh: Likewise.
	* emulparams/arcv2elfx.sh: Likewise.
	* emulparams/arcv2elf.sh: Likewise.
	* emultempl/arclinux.em: Likewise.
	* scripttempl/arclinux.sc: Likewise.
	* scripttempl/elfarc.sc: Likewise.
	* scripttempl/elfarcv2.sc: Likewise
	* Makefile.am: Add new ARC emulations.
	* Makefile.in: Regenerate.
	* NEWS: Mention the new feature.

opcodes * arc-dis.c: Revamped file for ARC support
	* arc-dis.h: Likewise.
	* arc-ext.c: Likewise.
	* arc-ext.h: Likewise.
	* arc-opc.c: Likewise.
	* arc-fxi.h: New file.
	* arc-regs.h: Likewise.
	* arc-tbl.h: Likewise.

binutils * readelf.c (get_machine_name): Remove A5 reference. Add ARCompact
	and ARCv2.
	(get_machine_flags): Handle EM_ARCV2 and EM_ARCOMPACT.
	(guess_is_rela): Likewise.
	(dump_relocations): Likewise.
	(is_32bit_abs_reloc): Likewise.
	(is_16bit_abs_reloc): Likewise.
	(is_none_reloc): Likewise.
	* NEWS: Mention the new feature.

include	* dis-asm.h (arc_get_disassembler): Correct declaration.
	* arc-reloc.def: Macro file with definition of all relocation
	types.
	* arc.h: Changed macros for the newly supported ARC cpus.  Altered
	enum defining the supported relocations.
	* common.h: Changed EM_ARC_A5 definition to EM_ARC_COMPACT. Added
	macro for EM_ARC_COMPACT2.
        * arc-func.h: New file.
        * arc.h: Likewise.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [GAS][AARCH64]Add TLSDESC large memory model support.
@ 2015-10-02 18:57 sergiodj+buildbot
  2015-10-03 16:49 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-10-02 18:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 43a357f99fc8c6535d064c5bce4b2865aa33bdd2 ***

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

[GAS][AARCH64]Add TLSDESC large memory model support.

bfd/

2015-10-02  Renlin Li <renlin.li@arm.com>

	* elfnn-aarch64.c (elfNN_aarch64_howto_table): Check overflow for
	BFD_RELOC_AARCH64_TLSDESC_OFF_G1.

gas/

2015-10-02  Renlin Li <renlin.li@arm.com>

	* config/tc-aarch64.c (s_tlsdescadd): New.
	(s_tlsdescldr): New.
	(md_pseudo_table): Handle tlsdescadd and tlsdescldr pseudo ops.
	(reloc_table): Add entries for BFD_RELOC_AARCH64_TLSDESC_OFF_G0_NC and
	BFD_RELOC_AARCH64_TLSDESC_OFF_G0_NC.
	(process_movw_reloc_info): Support AARCH64_TLSDESC_OFF_G1 and
	    AARCH64_TLSDESC_OFF_G0_NC.
	(md_apply_fix): Likewise.
	(aarch64_force_relocation): Likewise.

gas/testsuite/

2015-10-02  Renlin Li <renlin.li@arm.com>

	* gas/aarch64/reloc-tlsdesc_off_g0_nc.d: New.
	* gas/aarch64/reloc-tlsdesc_off_g0_nc.s: New.
	* gas/aarch64/reloc-tlsdesc_off_g1.d: New.
	* gas/aarch64/reloc-tlsdesc_off_g1.s: New.
	* gas/aarch64/tls-desc.d: New.
	* gas/aarch64/tls-desc.s: New.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [BFD][AARCH64]Add TLSGD relaxation support under large memory model.
@ 2015-10-02 18:50 sergiodj+buildbot
  2015-10-03 15:50 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-10-02 18:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ac734732481451698ee23990aaa64907e56dd082 ***

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

[BFD][AARCH64]Add TLSGD relaxation support under large memory model.

bfd/

2015-10-02  Renlin Li <renlin.li@arm.com>

	* elfnn-aarch64.c(IS_AARCH64_TLS_RELAX_RELOC):
	Add relaxation support for TLSGD_MOVW_G0_NC and TLSGD_MOVW_G1.
	(aarch64_tls_transition_without_check): Likewise
	(elfNN_aarch64_tls_relax): Likwise.

ld/testsuite/

2015-10-02  Renlin Li <renlin.li@arm.com>

	* ld-aarch64/aarch64-elf.exp: run new test
	* ld-aarch64/tls-relax-large-gd-ie.d: New.
	* ld-aarch64/tls-relax-large-gd-ie.s: New.
	* ld-aarch64/tls-relax-large-gd-le.d: New.
	* ld-aarch64/tls-relax-large-gd-le.s: New.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [GAS][AARCH64]Add BFD_RELOC_AARCH64_TLSGD_MOVW_G0_NC support.
@ 2015-10-02 18:19 sergiodj+buildbot
  2015-10-03 11:44 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-10-02 18:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3e8286c0d2f6f94fcbc38a2233d85b90ca4040c0 ***

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

[GAS][AARCH64]Add BFD_RELOC_AARCH64_TLSGD_MOVW_G0_NC support.

bfd/

2015-10-02  Renlin Li <renlin.li@arm.com>

	* reloc.c (BFD_RELOC_AARCH64_TLSGD_MOVW_G0_NC): New entry.
	* elfnn-aarch64.c (elfNN_aarch64_howto_table): New entry for
	BFD_RELOC_AARCH64_TLSGD_MOVW_G0_NC.
	* libbfd.h: Regenerate.
	* bfd-in2.h: Likewise

gas/

2015-10-02  Renlin Li <renlin.li@arm.com>

	* config/tc-aarch64.c (reloc_table): New relocation modifier tlsgd_g0_nc.
	(process_movw_reloc_info): Support BFD_RELOC_AARCH64_TLSGD_MOVW_G1.
	(md_apply_fix): Likewise.
	(aarch64_force_relocation): Likewise.

gas/testsuite/

2015-10-02  Renlin Li <renlin.li@arm.com>

	* gas/aarch64/reloc-tlsgd_g0_nc.d: New.
	* gas/aarch64/reloc-tlsgd_g0_nc.s: New.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [LD][AARCH64]Add BFD_RELOC_AARCH64_LD64_GOTOFF_LO15 Support.
@ 2015-10-02 17:40 sergiodj+buildbot
  2015-10-02 20:01 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-10-02 17:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a2e1db00c76bcad0594654d78af76d0e12a217ee ***

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

[LD][AARCH64]Add BFD_RELOC_AARCH64_LD64_GOTOFF_LO15 Support.

bfd/

2015-10-02  Renlin Li  <renlin.li@arm.com>

	* elfnn-aarch64.c (aarch64_reloc_got_type): Add
	BFD_RELOC_AARCH64_LD_64_GOTOFF_LO15 support.
	(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
	(elfNN_aarch64_final_link_relocate): Calculate offset within GOT.

ld/testsuite/

2015-10-02  Renlin Li  <renlin.li@arm.com>

	* ld-aarch64/emit-relocs-310.d: New.
	* ld-aarch64/emit-relocs-310.s: New.
	* ld-aarch64/aarch64-elf.exp: Run the test.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [GAS][AARCH64]Add BFD_RELOC_AARCH64_MOVW_GOTOFF_G1 Support.
@ 2015-10-02 17:31 sergiodj+buildbot
  2015-10-02 21:01 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-10-02 17:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 654248e7f702887c5a43bf402cd6080734f57819 ***

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

[GAS][AARCH64]Add BFD_RELOC_AARCH64_MOVW_GOTOFF_G1 Support.

bfd/

2015-10-02  Renlin Li  <renlin.li@arm.com>

	* reloc.c (BFD_RELOC_AARCH64_MOVW_GOTOFF_G1): New.
	* elfnn-aarch64.c (elfNN_aarch64_howto_table): New entry for
	MOVW_GOTOFF_G1.
	* libbfd.h: Regenerate.
	* bfd-in2.h: Regenerate.

gas/

2015-10-02  Renlin Li  <renlin.li@arm.com>

	* config/tc-aarch64.c (reloc_table): New relocation modifier
	gotoff_g1.
	(process_movw_reloc_info): Support newly added modifier.
	(md_apply_fix): Likewise.

gas/testsuite/

2015-10-02  Renlin Li  <renlin.li@arm.com>

	* gas/aarch64/reloc-gotoff_g1.s: New.
	* gas/aarch64/reloc-gotoff_g1.d: New.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Make aarch64_zero_register_p declaration starts from column one
@ 2015-10-02 15:25 sergiodj+buildbot
  2015-10-02 18:04 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-10-02 15:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e141d84e8986ad948fdc891fd7b8c4d7de53477c ***

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

Make aarch64_zero_register_p declaration starts from column one

include/opcode:

2015-10-02  Yao Qi  <yao.qi@linaro.org>

	* aarch64.h (aarch64_zero_register_p): Move the declaration
	to column one.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [aarch64] expose disas_aarch64_insn and rename it to aarch64_decode_insn
@ 2015-10-02 14:46 sergiodj+buildbot
  2015-10-02 16:51 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-10-02 14:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 36f4aab18ccf897b405f137d6cd4f9673bd947fc ***

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

[aarch64] expose disas_aarch64_insn and rename it to aarch64_decode_insn

We want to use disas_aarch64_insn inside GDB to decode instructions, so
this patch exposes it and rename it to aarch64_decode_insn to follow
the conventions of other interfaces.

include/opcode:

2015-10-02  Yao Qi  <yao.qi@linaro.org>

	* aarch64.h (aarch64_decode_insn): Declare it.

opcodes:

2015-10-02  Yao Qi  <yao.qi@linaro.org>

	* aarch64-dis.c	(disas_aarch64_insn): Remove static.  Change
	argument insn type to aarch64_insn.  Rename to ...
	(aarch64_decode_insn): ... it.
	(print_insn_aarch64_word): Caller updated.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [aarch64] Remove argument pc from disas_aarch64_insn
@ 2015-10-02 14:38 sergiodj+buildbot
  2015-10-02 15:31 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-10-02 14:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7232d38966babb802e9d8d0e9e591346a7b93d96 ***

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

[aarch64] Remove argument pc from disas_aarch64_insn

I happen to see that argument pc is not used inside disas_aarch64_insn
at all.  This patch is to remove it.

OK to apply?

opcodes:

2015-10-02  Yao Qi  <yao.qi@linaro.org>

	* aarch64-dis.c (disas_aarch64_insn): Remove argument PC.
	(print_insn_aarch64_word): Caller updated.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [BFD][AARCH64]Emit single AARCH64_MAP_INSN symbol for the whole plt.
@ 2015-10-01 13:47 sergiodj+buildbot
  2015-10-01 14:39 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-10-01 13:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 73524045d3a3b95bb0437386bba2a1583791ea42 ***

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

[BFD][AARCH64]Emit single AARCH64_MAP_INSN symbol for the whole plt.

bfd/

2015-10-01  Renlin Li  <renlin.li@arm.com>

	* elfnn-aarch64.c (elfNN_aarch64_output_plt_map): Remove.
	(elfNN_aarch64_output_arch_local_syms): Emit AARCH64_MAP_INSN once.

ld/testsuite/

2015-10-01  Renlin Li  <renlin.li@arm.com>

	* ld-aarch64/plt_mapping_symbol.d: New.
	* ld-aarch64/plt_mapping_symbol.s: New.
	* ld-aarch64/aarch64-elf.exp: Run the new test.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] bfd/config.bfd: Drop non-linux non-fdpic stuff from the last change of targ_selvecs of sh*-linux cases
@ 2015-10-01  5:31 sergiodj+buildbot
  2015-10-01  6:24 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-10-01  5:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT de48f481b1769866ad8da5923792a49420a2d157 ***

Author: Kaz Kojima <kkojima@rr.iij4u.or.jp>
Branch: master
Commit: de48f481b1769866ad8da5923792a49420a2d157

bfd/config.bfd: Drop non-linux non-fdpic stuff from the last change of targ_selvecs of sh*-linux cases


^ permalink raw reply	[flat|nested] 1132+ messages in thread
[parent not found: <017e6bceee1a96d4b57175687560b4d625fdb150@gdb-build>]
* [binutils-gdb] Call strprefix instead of strncmp in event parsing
@ 2015-09-30 18:38 sergiodj+buildbot
  2015-09-30 23:37 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-09-30 18:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6ab24463cb63af792c958ab4455d630b5936f1b1 ***

Author: Don Breazeal <donb@codesourcery.com>
Branch: master
Commit: 6ab24463cb63af792c958ab4455d630b5936f1b1

Call strprefix instead of strncmp in event parsing

This fixes a typo that used strncmp instead of strprefix when
checking for an exec event in a stop reply packet.

gdb/ChangeLog:

	* remote.c (remote_parse_stop_reply): Call strprefix instead
	of strncmp.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] py-type.exp: Do not run tests if binary fails to build
@ 2015-09-30 15:14 sergiodj+buildbot
  2015-09-30 17:32 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-09-30 15:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e019fd1d143061c703691b862f1e282be57b2983 ***

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

py-type.exp: Do not run tests if binary fails to build

I noticed this while working on the test case.  I believe it would make
sense to skip running the tests if the binary failed to build.  Although
I would understand the opposite argument: if the binary does not build
for some reason, we probably want to know about it, and some catastrophic
failures in the tests might alarm us better than a timid "UNTESTED".

gdb/testsuite/ChangeLog:

	* gdb.python/py-type.exp: Do not run tests if binaries fail to
	build.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Add fdpic and misc targets to config.bfd for sh*-*-linux*
@ 2015-09-30  6:50 sergiodj+buildbot
  2015-09-30 12:59 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-09-30  6:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6c4f2328aba04ffacce9a4033fd253222e2ea1aa ***

Author: Rich Felker <dalias@libc.org>
Branch: master
Commit: 6c4f2328aba04ffacce9a4033fd253222e2ea1aa

Add fdpic and misc targets to config.bfd for sh*-*-linux*


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] sim: ft32: correct simulation of MEMCPY and MEMSET
@ 2015-09-30  5:04 sergiodj+buildbot
  2015-09-30  6:49 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-09-30  5:04 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 395b0d8a3fdd8915a4897b9b925d56fa42745dcc ***

Author: James Bowman <james.bowman@ftdichip.com>
Branch: master
Commit: 395b0d8a3fdd8915a4897b9b925d56fa42745dcc

sim: ft32: correct simulation of MEMCPY and MEMSET

The MEMCPY and MEMSET instructions should only examine the low 15 bits of
their length arguments.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Don't use the output section size to copy input section
@ 2015-09-30  3:47 sergiodj+buildbot
  2015-09-30  4:27 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-09-30  3:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cbd44e247ede49688e1e1fa42e57d390ad141967 ***

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

Don't use the output section size to copy input section

We can't use the output section size to copy input section since
--interleave will shrink the output section.  Instead, we change
bfd_convert_section_contents to return the updated input section
size.  When we do that, we don't need to adjust the output section
size to skip gap fills.

bfd/

	PR binutils/19020
	* bfd.c (bfd_convert_section_contents): Add ptr_size parameter.
	* bfd-in2.h: Regenerated.

binutils/

	PR binutils/19020
	* objcopy.c (copy_object): Don't adjust the output section size
	when copying from input sections.
	(copy_section): Use input section size for the copy.  Get the
	updated section size from bfd_convert_section_contents.

binutils/testsuite/

	PR binutils/19020
	* binutils-all/objcopy.exp: Run pr19020a and pr19020b.
	* lib/utils-lib.exp (run_dump_test): Support binary input.
	* binutils-all/pr19020.in: New file.
	* binutils-all/pr19020a.d: Likewise.
	* binutils-all/pr19020b.d: Likewise.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Rebase patch #7
@ 2015-09-29 17:29 sergiodj+buildbot
  2015-09-29 21:09 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-09-29 17:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4f714dd43efde465c7f2272ee444ccd2f1b3a1b5 ***

Author: jamesbowman <jamesb@excamera.com>
Branch: master
Commit: 4f714dd43efde465c7f2272ee444ccd2f1b3a1b5

Rebase patch #7


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [FT32] Replace hard-coded instruction patterns with macros
@ 2015-09-29 17:05 sergiodj+buildbot
  2015-09-29 20:30 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-09-29 17:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 86feccb92092506f2a23a32345bc0f562ac4042b ***

Author: jamesbowman <jamesb@excamera.com>
Branch: master
Commit: 86feccb92092506f2a23a32345bc0f562ac4042b

[FT32] Replace hard-coded instruction patterns with macros

The stack unwinder can now use FT32_*() macros to interpet binary
instructions instead of local definitions.

2015-09-29  James Bowman  <james.bowman@ftdichip.com>

	* ft32-tdep.c: #include "opcode/ft32.h".
	Delete local macros IS_PUSH, PUSH_REG, IS_LINK, LINK_SIZE.
	(ft32_analyze_prologue): Use FT32_* macros.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Add support for extensions in the .machine pseudoop on S/390, e.g. ".machine zEC12+nohtm+vx"
@ 2015-09-29 13:41 sergiodj+buildbot
  2015-09-29 16:57 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-09-29 13:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7ecc513a44095d614f10e89c67d9be5826abacf9 ***

Author: Dominik Vogt <vogt@linux.vnet.ibm.com>
Branch: master
Commit: 7ecc513a44095d614f10e89c67d9be5826abacf9

Add support for extensions in the .machine pseudoop on S/390, e.g. ".machine zEC12+nohtm+vx"

gas	* doc/c-s390.texi: Add documentation.
	Add missing code markup.
	* config/tc-s390.c (current_flags): New static variable.
	(s390_parse_cpu): Parse cpu flags a la "+nohtm" etc.
	(s390_setup_opcodes): Use cpu flags to determine the set of opcodes.
	Fix indentation.
	(md_parse_option): Call s390_parse_cpu with the new signature.
	(s390_machine): Likewise.
	Keep track of current_flags.
	Simplify code a bit.
	undefine MAX_HISTORY at end of function.
	(s390_machinemode): undefine MAX_HISTORY at end of function.
	Update an error message.

tests	* gas/s390/s390.exp: Add new tests.
	* gas/s390/machine-parsing-1.s: New test file.
	* gas/s390/machine-parsing-1.l: Likewise.
	* gas/s390/machine-parsing-2.s: Likewise.
	* gas/s390/machine-parsing-2.l: Likewise.
	* gas/s390/machine-parsing-3.s: Likewise.
	* gas/s390/machine-parsing-3.l: Likewise.
	* gas/s390/machine-parsing-4.s: Likewise.
	* gas/s390/machine-parsing-4.l: Likewise.
	* gas/s390/machine-parsing-5.s: Likewise.
	* gas/s390/machine-parsing-5.l: Likewise.
	* gas/s390/machine-parsing-6.s: Likewise.
	* gas/s390/machine-parsing-6.l: Likewise.

opcode	* s390.h (S390_INSTR_FLAG_HTM): New flag.
	(S390_INSTR_FLAG_VX): New flag.
	(S390_INSTR_FLAG_FACILITY_MASK): New flag mask.

opcodes	* s390-mkopc.c (main): Parse htm and vx flag.
	* s390-opc.txt: Mark instructions from the hardware transactional
	memory and vector facilities with the "htm"/"vx" flag.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] gdb.base/gcore.c (array_func): Add reference to static_array.
@ 2015-09-28 22:09 sergiodj+buildbot
  2015-09-29 12:41 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-09-28 22:09 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c60eb31fb11129ee91b9f778b852f886db545381 ***

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

gdb.base/gcore.c (array_func): Add reference to static_array.

Otherwise clang will delete it: it's otherwise unused.

gdb/testsuite/ChangeLog:

	* gdb.base/gcore.c (array_func): Add reference to static_array.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] common/filestuff.c (make_cleanup_close): Update comment.
@ 2015-09-28 19:25 sergiodj+buildbot
  2015-09-28 22:47 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-09-28 19:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c402ef907a6c0600fc5dec79b6165afd49233124 ***

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

common/filestuff.c (make_cleanup_close): Update comment.

gdb/ChangeLog:

	* common/filestuff.c (make_cleanup_close): Update comment.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Updare French translation for binutils and German translation for opcodes.
@ 2015-09-28 18:35 sergiodj+buildbot
  2015-09-28 19:05 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-09-28 18:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b08b78e7d4bb56f395d3212eed6184ede236c760 ***

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

Updare French translation for binutils and German translation for opcodes.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Fix cast of xml_find_attribute's return value
@ 2015-09-28  2:50 sergiodj+buildbot
  2015-09-28  4:24 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-09-28  2:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bc84451b7af508ddd154a8793eaf0de68b7ca80a ***

Author: Simon Marchi <simark@nova.polymtl.ca>
Branch: master
Commit: bc84451b7af508ddd154a8793eaf0de68b7ca80a

Fix cast of xml_find_attribute's return value

The cast auto-insert script inserted long unsigned int, but we should
use the typedef ULONGEST.  Fixes build failures on i386.

gdb/ChangeLog:

	* btrace.c (parse_xml_btrace_block): Fix cast of
	xml_find_attribute's return value.
	* memory-map.c (memory_map_start_memory): Likewise.
	* solib-svr4.c (library_list_start_library): Likewise.
	* solib-target.c (library_list_start_segment): Likewise.
	(library_list_start_section): Likewise.
	* tracepoint.c (traceframe_info_start_memory): Likewise.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Correct the generation of OR1K pc-relative relocations.
@ 2015-09-25 15:17 sergiodj+buildbot
  2015-09-25 19:46 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-09-25 15:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8a9e7a9121490a8c64d8c17f5be510e43104f6d9 ***

Author: Peter Zotov <whitequark@whitequark.org>
Branch: master
Commit: 8a9e7a9121490a8c64d8c17f5be510e43104f6d9

Correct the generation of OR1K pc-relative relocations.

gas	PR ld/18759
	* config/tc-or1k.c (tc_gen_reloc): Correct computation of PC
	relative relocs.
	* config/tc-or1k.h (GAS_CGEN_PRCEL_R_TYPE): Delete.

bfd	* elf32-or1k.c (R_OR1K_32_PCREL): Set pcrel_offset to TRUE.
	(R_OR1K_16_PCREL): Likewise.
	(R_OR1K_8_PCREL): Likewise.

ld/tests * ld-elf/eh-frame-hdr: Expect to pass on the or1k-linux target.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Accidentally added file. Removed it.
@ 2015-09-25  0:35 sergiodj+buildbot
  2015-09-25 18:36 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-09-25  0:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6e15a7d88b346cd5dd6ea76d86121d29932c3c8d ***

Author: jamesbowman <jamesb@excamera.com>
Branch: master
Commit: 6e15a7d88b346cd5dd6ea76d86121d29932c3c8d

Accidentally added file. Removed it.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [FT32] Implement pointer to address conversion method.
@ 2015-09-24 23:46 sergiodj+buildbot
  2015-09-25 15:36 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-09-24 23:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 623fb77545da1272c7602cd51a4c187b66c366c8 ***

Author: jamesbowman <jamesb@excamera.com>
Branch: master
Commit: 623fb77545da1272c7602cd51a4c187b66c366c8

[FT32] Implement pointer to address conversion method.

FT32 is a Harvard architecture with two address spaces -- RAM and flash.
The patch properly implements the pointer to address conversion method.
There are some other small fixes to handle address spaces.

gdb/
	* ft32-tdep.c (ft32_register_type): Return gdbarch_tdep
	(gdbarch)->pc_type instead of builtin_func_ptr.
	(ft32_pointer_to_address): New function.
	(ft32_address_class_type_flags): New function.
	(ft32_address_class_type_flags_to_name): New function.
	(ft32_address_class_name_to_type_flags): New function.
	(ft32_gdbarch_init): Set tdep->pc_type.  Call
	set_gdbarch_pointer_to_address,
	set_gdbarch_address_class_type_flags
	set_gdbarch_address_class_name_to_type_flags,
	and set_gdbarch_address_class_type_flags_to_name.
	* ft32-tdep.h (struct gdbarch_tdep) <pc_type>: New field.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Allow any size enum in gdb.cp/var-tag.exp.
@ 2015-09-24  1:12 sergiodj+buildbot
  2015-09-24 23:41 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-09-24  1:12 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 938d3bf25b2f5bc1a9d955d86070e8bbee127f52 ***

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

Allow any size enum in gdb.cp/var-tag.exp.

2015-09-23 Sandra Loosemore <sandra@codesourcery.com>

	gdb/testsuite/
	* gdb.cp/var-tag.exp (do_global_tests): Generalize opt_underlying
	to allow any size enum.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [Ada] Fix handling of array renamings
@ 2015-09-23 21:13 sergiodj+buildbot
  2015-09-24  1:05 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-09-23 21:13 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e6c2c623f7736175e52fce2b61aab60c60eccdf5 ***

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

[Ada] Fix handling of array renamings

Compilers can materialize renamings of arrays (or of accesses to arrays)
in Ada into variables whose types are references to the actual array
types.  Before this change, trying to use such an array renaming yielded
an error in GDB:

    (gdb) print my_array(1)
    cannot subscript or call a record
    (gdb) print my_array_ptr(1)
    cannot subscript or call something of type `(null)'

This behavior comes from bad handling for array renamings, in particular
the OP_FUNCALL expression operator handling from ada-lang.c
(ada_evaluate_subexp): in one place we turn the reference into a
pointer, but the code that follows expect the value to be an array.

This patch fixes how we handle references in call/subscript evaluation
so that we turn these references into the actual array values instead of
pointers to them.

gdb/ChangeLog:

	* ada-lang.c (ada_evaluate_subexp) <OP_FUNCALL>: When the input
	value is a reference, actually dereference it in order to get
	the underlying value.

gdb/testsuite/ChangeLog:

	* gdb.ada/array_ptr_renaming.exp: New testcase.
	* gdb.ada/array_ptr_renaming/foo.adb: New file.
	* gdb.ada/array_ptr_renaming/pack.ads: New file.

Tested on x86_64-linux, no regression.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Enhance the RX disassembler to detect and report bad instructions.
@ 2015-09-22 17:51 sergiodj+buildbot
  2015-09-23  4:26 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-09-22 17:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f04265eceb78a33e452faa8727562e96af374f39 ***

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

Enhance the RX disassembler to detect and report bad instructions.

opcode	* rx.h (enum RX_Size): Add RX_Bad_Size entry.

opcodes	* rx-decode.opc (bwl): Use RX_Bad_Size.
	(sbwl): Likewise.
	(ubwl): Likewise.  Rename to ubw.
	(uBWL): Rename to uBW.
	Replace all references to uBWL with uBW.
	* rx-decode.c: Regenerate.
	* rx-dis.c (size_names): Add entry for RX_Bad_Size.
	(opsize_names): Likewise.
	(print_insn_rx): Detect and report RX_Bad_Size.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Use bfd_get_32 and bfd_put_32 to access ch_type
@ 2015-09-22  4:08 sergiodj+buildbot
  2015-09-22 16:05 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-09-22  4:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c8b187ea07f534bac147cbbc44dd08925f5734b0 ***

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

Use bfd_get_32 and bfd_put_32 to access ch_type

The ch_type field in Elf64_External_Chdr is 4 bytes.  We should use
bfd_get_32 and bfd_put_32 to access it.

	* bfd.c (bfd_update_compression_header): Use bfd_put_32 on
	ch_type.
	(bfd_check_compression_header): Use bfd_get_32 on ch_type.
	(bfd_convert_section_contents): Use bfd_get_32 and bfd_put_32
	on ch_type.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Add NEWS entry for fast tracepoint support on aarch64-linux
@ 2015-09-21 15:50 sergiodj+buildbot
  2015-09-22 10:24 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-09-21 15:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4d9d419e0e0512c301eb1ffcb793828451653024 ***

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

Add NEWS entry for fast tracepoint support on aarch64-linux

Here is a NEWS entry for this series:

gdb/ChangeLog:

	* NEWS: Mention support for fast tracepoints on aarch64-linux.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Add a gdb.trace test for instruction relocation
@ 2015-09-21 15:19 sergiodj+buildbot
  2015-09-22  7:52 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-09-21 15:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4f51c22aca0d53526e65954b99d1ab3abfbb8bc8 ***

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

Add a gdb.trace test for instruction relocation

This test case makes sure that relocating PC relative instructions does
not change their behaviors.  All PC relative AArch64 instructions are
covered.  While call and jump (32 bit relative) instructions are covered
on x86.

The test case creates a static array of function pointers for each
supported architecture.  Each function in this array tests a specific
instruction using inline assembly.  They all need to contain a symbol in
the form of 'set_point\[0-9\]+' and finish by either calling pass or
fail.  The number of 'set_pointN' needs to go from 0 to
(ARRAY_SIZE - 1).

The test will:
- look up the number of function pointers in the static array.
- set fast tracepoints on each 'set_point\[0-9\]+' symbol, one in each
  functions from 0 to (ARRAY_SIZE - 1).
- run the trace experiment and make sure the pass function is called for
  every function.

gdb/testsuite/ChangeLog:

	* gdb.arch/insn-reloc.c: New file.
	* gdb.arch/ftrace-insn-reloc.exp: New file.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Implement target_emit_ops
@ 2015-09-21 15:08 sergiodj+buildbot
  2015-09-22  5:50 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-09-21 15:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT afbe19f83ad1af46e7b1f1639d9fa0eb873dcbb5 ***

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

Implement target_emit_ops

This patch implements compiling agent expressions to native code for
AArch64.  This allows us to compile conditions set on fast tracepoints.

The compiled function has the following prologue:

High *------------------------------------------------------*
     | LR                                                   |
     | FP                                                   | <- FP
     | x1  (ULONGEST *value)                                |
     | x0  (unsigned char *regs)                            |
Low  *------------------------------------------------------*

We save the function's argument on the stack as well as the return
address and the frame pointer.  We then set the current frame pointer to
point to the previous one.

The generated code for the expression will freely update the stack
pointer so we use the frame pointer to refer to `*value' and `*regs'.
`*value' needs to be accessed in the epilogue of the function, in order
to set it to whatever is on top of the stack.  `*regs' needs to be passed
down to the `gdb_agent_get_raw_reg' function with the `reg' operation.

gdb/gdbserver/ChangeLog:

	* linux-aarch64-low-.c: Include ax.h and tracepoint.h.
	(enum aarch64_opcodes) <RET>, <SUBS>, <AND>, <ORR>, <ORN>,
	<EOR>, <LSLV>, <LSRV>, <ASRV>, <SBFM>, <UBFM>, <CSINC>, <MUL>,
	<NOP>: New.
	(enum aarch64_condition_codes): New enum.
	(w0): New static global.
	(fp): Likewise.
	(lr): Likewise.
	(struct aarch64_memory_operand) <type>: New
	MEMORY_OPERAND_POSTINDEX type.
	(postindex_memory_operand): New helper function.
	(emit_ret): New function.
	(emit_load_store_pair): New function, factored out of emit_stp
	with support for MEMORY_OPERAND_POSTINDEX.
	(emit_stp): Rewrite using emit_load_store_pair.
	(emit_ldp): New function.
	(emit_load_store): Likewise.
	(emit_ldr): Mention post-index instruction in comment.
	(emit_ldrh): New function.
	(emit_ldrb): New function.
	(emit_ldrsw): Mention post-index instruction in comment.
	(emit_str): Likewise.
	(emit_subs): New function.
	(emit_cmp): Likewise.
	(emit_and): Likewise.
	(emit_orr): Likewise.
	(emit_orn): Likewise.
	(emit_eor): Likewise.
	(emit_mvn): Likewise.
	(emit_lslv): Likewise.
	(emit_lsrv): Likewise.
	(emit_asrv): Likewise.
	(emit_mul): Likewise.
	(emit_sbfm): Likewise.
	(emit_sbfx): Likewise.
	(emit_ubfm): Likewise.
	(emit_ubfx): Likewise.
	(emit_csinc): Likewise.
	(emit_cset): Likewise.
	(emit_nop): Likewise.
	(emit_ops_insns): New helper function.
	(emit_pop): Likewise.
	(emit_push): Likewise.
	(aarch64_emit_prologue): New function.
	(aarch64_emit_epilogue): Likewise.
	(aarch64_emit_add): Likewise.
	(aarch64_emit_sub): Likewise.
	(aarch64_emit_mul): Likewise.
	(aarch64_emit_lsh): Likewise.
	(aarch64_emit_rsh_signed): Likewise.
	(aarch64_emit_rsh_unsigned): Likewise.
	(aarch64_emit_ext): Likewise.
	(aarch64_emit_log_not): Likewise.
	(aarch64_emit_bit_and): Likewise.
	(aarch64_emit_bit_or): Likewise.
	(aarch64_emit_bit_xor): Likewise.
	(aarch64_emit_bit_not): Likewise.
	(aarch64_emit_equal): Likewise.
	(aarch64_emit_less_signed): Likewise.
	(aarch64_emit_less_unsigned): Likewise.
	(aarch64_emit_ref): Likewise.
	(aarch64_emit_if_goto): Likewise.
	(aarch64_emit_goto): Likewise.
	(aarch64_write_goto_address): Likewise.
	(aarch64_emit_const): Likewise.
	(aarch64_emit_call): Likewise.
	(aarch64_emit_reg): Likewise.
	(aarch64_emit_pop): Likewise.
	(aarch64_emit_stack_flush): Likewise.
	(aarch64_emit_zero_ext): Likewise.
	(aarch64_emit_swap): Likewise.
	(aarch64_emit_stack_adjust): Likewise.
	(aarch64_emit_int_call_1): Likewise.
	(aarch64_emit_void_call_2): Likewise.
	(aarch64_emit_eq_goto): Likewise.
	(aarch64_emit_ne_goto): Likewise.
	(aarch64_emit_lt_goto): Likewise.
	(aarch64_emit_le_goto): Likewise.
	(aarch64_emit_gt_goto): Likewise.
	(aarch64_emit_ge_got): Likewise.
	(aarch64_emit_ops_impl): New static global variable.
	(aarch64_emit_ops): New target function, return
	&aarch64_emit_ops_impl.
	(struct linux_target_ops): Install it.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Make aarch64_decode_adrp handle both ADR and ADRP instructions
@ 2015-09-21 14:52 sergiodj+buildbot
  2015-09-21 23:18 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-09-21 14:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6ec5f4be052e594dc90b6677fec1c1e7727d9651 ***

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

Make aarch64_decode_adrp handle both ADR and ADRP instructions

We will need to decode both ADR and ADRP instructions in GDBserver.
This patch makes common code handle both cases, even if GDB only needs
to decode the ADRP instruction.

gdb/ChangeLog:

	* aarch64-tdep.c (aarch64_analyze_prologue): New is_adrp
	variable.  Call aarch64_decode_adr instead of
	aarch64_decode_adrp.
	* arch/aarch64-insn.h (aarch64_decode_adrp): Delete.
	(aarch64_decode_adr): New function declaration.
	* arch/aarch64-insn.c (aarch64_decode_adrp): Delete.
	(aarch64_decode_adr): New function, factored out from
	aarch64_decode_adrp to decode both adr and adrp instructions.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] dwarf2_compute_name: add fixme, don't use same name as parameter for local
@ 2015-09-20 22:27 sergiodj+buildbot
  2015-09-21 14:22 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-09-20 22:27 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2ee7123e5a54fba15b976a05bce173871eba8aba ***

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

dwarf2_compute_name: add fixme, don't use same name as parameter for local

gdb/ChangeLog:

	* dwarf2read.c (dwarf2_compute_name): Add FIXME.  Don't use a local
	variable name that collides with a parameter.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] crash printing non-local variable from nested subprogram
@ 2015-09-20 19:59 sergiodj+buildbot
  2015-09-21 12:18 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-09-20 19:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7d1c9c9b4c586ede0abecb7a0a47d8996aaf56da ***

Author: Joel Brobecker <brobecker@adacore.com>
Branch: master
Commit: 7d1c9c9b4c586ede0abecb7a0a47d8996aaf56da

crash printing non-local variable from nested subprogram

We have noticed that GDB would sometimes crash trying to print
from a nested function the value of a variable declared in an
enclosing scope. This appears to be target dependent, although
that correlation might only be fortuitious.  We noticed the issue
on x86_64-darwin, x86-vxworks6 and x86-solaris.  The investigation
was done on Darwin.

This is a new feature that was introduced by:

    commit 63e43d3aedb8b1112899c2d0ad74cbbee687e5d6
    Date:   Thu Feb 5 17:00:06 2015 +0100
    DWARF: handle non-local references in nested functions

We can reproduce the problem with one of the testcases that was
added with the patch (gdb.base/nested-subp1.exp), where we have...

    18 int
    19 foo (int i1)
    20 {
    21   int
    22   nested (int i2)
    23   {
    [...]
    27     return i1 * i2; /* STOP */
    28   }

...  After building the example program, and running until line 27,
try printing the value of "i1":

    % gdb gdb.base/nested-subp1
    (gdb) break foo.c:27
    (gdb) run
    Breakpoint 1, nested (i2=2) at /[...]/nested-subp1.c:27
    27          return i1 * i2; /* STOP */
    (gdb) p i1
    [1]    73090 segmentation fault  ../gdb -q gdb.base/nested-subp1

Ooops!

What happens is that, because the reference is non-local, we are trying
to follow the function's static link, which does...

    /* If we don't know how to compute FRAME's base address, don't give up:
       maybe the frame we are looking for is upper in the stace frame.  */
    if (framefunc != NULL
        && SYMBOL_BLOCK_OPS (framefunc)->get_frame_base != NULL
        && (SYMBOL_BLOCK_OPS (framefunc)->get_frame_base (framefunc, frame)
            == upper_frame_base))

... or, in other words, calls the get_frame_base "method" of
framefunc's struct symbol_block_ops data. This resolves to
the block_op_get_frame_base function.

Looking at the function's implementation, we see:

  struct dwarf2_locexpr_baton *dlbaton;
  [...]
  dlbaton = SYMBOL_LOCATION_BATON (framefunc);
  [...]
  result = dwarf2_evaluate_loc_desc (type, frame, start, length,
                                     dlbaton->per_cu);
                                     ^^^^^^^^^^^^^^^

Printing dlbaton->per_cu gives a value that seems fairly bogus for
a memory address (0x60). Because of it, dwarf2_evaluate_loc_desc
then crashes trying to dereference it.

What's different on Darwin compared to Linux is that the function's
frame base is encoded using the following form:

        .byte   0x40    # uleb128 0x40; (DW_AT_frame_base)
        .byte   0x6     # uleb128 0x6; (DW_FORM_data4)

... and so dwarf2_symbol_mark_computed ends up creating
a SYMBOL_LOCATION_BATON as a struct dwarf2_loclist_baton:

  if (attr_form_is_section_offset (attr)
      /* .debug_loc{,.dwo} may not exist at all, or the offset may be outside
         the section.  If so, fall through to the complaint in the
         other branch.  */
      && DW_UNSND (attr) < dwarf2_section_size (objfile, section))
    {
      struct dwarf2_loclist_baton *baton;
      [...]
      SYMBOL_LOCATION_BATON (sym) = baton;

However, if you look more closely at block_op_get_frame_base's
implementation, you'll notice that the function extracts the
symbol's SYMBOL_LOCATION_BATON as a dwarf2_locexpr_baton
(a DWARF _expression_ rather than a _location list_).
That's why we end up decoding the DLBATON improperly, and thus
pass a random dlbaton->per_cu when calling dwarf2_evaluate_loc_desc.

This works on x86_64-linux, because we indeed have the frame base
described using a different form:

        .uleb128 0x40   # (DW_AT_frame_base)
        .uleb128 0x18   # (DW_FORM_exprloc)

This patch fixes the issue by doing what we do for most (if not all)
other such methods: providing one implementation each for loc-list,
and loc-expr. Both implementations are nearly identical, so perhaps
we might later want to improve this. But this patch first tries to
fix the crash first, leaving the design issue for later.

gdb/ChangeLog:

        * dwarf2loc.c (locexpr_get_frame_base): Renames
        block_op_get_frame_base.
        (dwarf2_block_frame_base_locexpr_funcs): Replace reference to
        block_op_get_frame_base by reference to locexpr_get_frame_base.
        (loclist_get_frame_base): New function, near identical copy of
        locexpr_get_frame_base.
        (dwarf2_block_frame_base_loclist_funcs): Replace reference to
        block_op_get_frame_base by reference to loclist_get_frame_base.

Tested on x86_64-darwin (AdaCore testsuite), and x86_64-linux
(official testsuite).


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] symtab.h (general_symbol_info) <mangled_lang>: delete and move up only member.
@ 2015-09-19  6:25 sergiodj+buildbot
  2015-09-21  5:00 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-09-19  6:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 615b3f6299d95db8507b2a68dda2704d08bcd1d0 ***

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

symtab.h (general_symbol_info) <mangled_lang>: delete and move up only member.

gdb/ChangeLog:

	* symtab.h (general_symbol_info) <mangled_lang>: Delete struct,
	move only member demangled_name up.  All uses updated.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Fix directory prefix in gdb.base/dso2dso.exp.
@ 2015-09-19  0:15 sergiodj+buildbot
  2015-09-20 19:37 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-09-19  0:15 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 26b188a2db6345f70985d27ef91ebc30725424ea ***

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

Fix directory prefix in gdb.base/dso2dso.exp.

2015-09-18  Sandra Loosemore  <sandra@codesourcery.com>

	gdb/testsuite/
	* gdb.base/dso2dso.exp: Don't use directory prefix when setting
	the breakpoint.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] aarch64 multi-arch (part 3): get thread area
@ 2015-09-18 21:29 sergiodj+buildbot
  2015-09-20 12:49 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-09-18 21:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a0cc84cd15396df7752fe16659c01628ba729324 ***

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

aarch64 multi-arch (part 3): get thread area

With the kernle fix <http://lists.infradead.org/pipermail/linux-arm-kernel/2015-July/356511.html>,
aarch64 GDB is able to read the base of thread area of 32-bit arm
program through NT_ARM_TLS.

This patch is to teach both GDB and GDBserver to read the base of
thread area correctly in the multi-arch case.  A new function
aarch64_ps_get_thread_area is added, and is shared between GDB and
GDBserver.

With this patch applied, the following fails in multi-arch testing
(GDB is aarch64 but the test cases are arm) are fixed,

 -FAIL: gdb.threads/tls-nodebug.exp: thread local storage
 -FAIL: gdb.threads/tls-shared.exp: print thread local storage variable
 -FAIL: gdb.threads/tls-so_extern.exp: print thread local storage variable
 -FAIL: gdb.threads/tls-var.exp: print tls_var
 -FAIL: gdb.threads/tls.exp: first thread local storage
 -FAIL: gdb.threads/tls.exp: first another thread local storage
 -FAIL: gdb.threads/tls.exp: p a_thread_local
 -FAIL: gdb.threads/tls.exp: p file2_thread_local
 -FAIL: gdb.threads/tls.exp: p a_thread_local second time

gdb:

2015-09-18  Yao Qi  <yao.qi@linaro.org>

	* nat/aarch64-linux.c: Include elf/common.h,
	nat/gdb_ptrace.h, asm/ptrace.h and sys/uio.h.
	(aarch64_ps_get_thread_area): New function.
	* nat/aarch64-linux.h: Include gdb_proc_service.h.
	(aarch64_ps_get_thread_area): Declare.
	* aarch64-linux-nat.c (ps_get_thread_area): Call
	aarch64_ps_get_thread_area.

gdb/gdbserver:

2015-09-18  Yao Qi  <yao.qi@linaro.org>

	* linux-aarch64-low.c: Don't include sys/uio.h.
	(ps_get_thread_area): Call aarch64_ps_get_thread_area.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] btrace: temporarily set inferior_ptid in record_btrace_start_replaying
@ 2015-09-18 17:03 sergiodj+buildbot
  2015-09-19 11:25 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-09-18 17:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ec71cc2fc6d319ebe4aebbe65a6a56ea1376200e ***

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

btrace: temporarily set inferior_ptid in record_btrace_start_replaying

Get_current_frame uses inferior_ptid.  In record_btrace_start_replaying,
we need to get the current frame of the argument thread.  So far, this
has always been inferior_ptid.  With non-stop, this is not guaranteed.

Temporarily set inferior_ptid to the ptid of the argument thread.

We already temporarily set the argument thread's executing flag to false.

Move both into a new function get_thread_current_frame that does the temporary
adjustments, calls get_current_frame, and restores the previous values.

gdb/
	* record-btrace.c (get_thread_current_frame): New.
	(record_btrace_start_replaying): Call get_thread_current_frame.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Require readline for gdb.linespec/explicit.exp tab-completion tests.
@ 2015-09-18 16:29 sergiodj+buildbot
  2015-09-20 14:50 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-09-18 16:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 515b89b30c18dae6b91e57ec2dd336919bb4578d ***

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

Require readline for gdb.linespec/explicit.exp tab-completion tests.

2015-09-18  Sandra Loosemore  <sandra@codesourcery.com>

	gdb/testsuite/
	* gdb.linespec/explicit.exp: Check for readline support for
	tab-completion tests.  Fix obvious typo.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] target: add to_record_will_replay target method
@ 2015-09-18 15:12 sergiodj+buildbot
  2015-09-19 23:42 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-09-18 15:12 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7ff27e9babb1564a9c0e213c4a42396aa420f8cc ***

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

target: add to_record_will_replay target method

Add a new target method to_record_will_replay to query if there is a record
target that will replay at least one thread matching the argument PTID if it
were executed in the argument execution direction.

gdb/
	* record-btrace.c ((record_btrace_will_replay): New.
	(init_record_btrace_ops): Initialize to_record_will_replay.
	* record-full.c ((record_full_will_replay): New.
	(init_record_full_ops): Initialize to_record_will_replay.
	* target-delegates.c: Regenerated.
	* target.c (target_record_will_replay): New.
	* target.h (struct target_ops) <to_record_will_replay>: New.
	(target_record_will_replay): New.

Signed-off-by: Markus Metzger <markus.t.metzger@intel.com>


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] btrace: allow full memory and register access for non-replaying threads
@ 2015-09-18 15:02 sergiodj+buildbot
  2015-09-19 20:11 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-09-18 15:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4d10e986f499f330963c4641fd91046c57c94bd8 ***

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

btrace: allow full memory and register access for non-replaying threads

The record btrace target does not allow accessing memory and storing registers
while replaying.  For multi-threaded applications, this prevents those
accesses also for threads that are at the end of their execution history as
long as at least one thread is replaying.

Change this to only check if the selected thread is replaying.  This allows
threads that are at the end of their execution history to read and write
memory and to store registers.

Also change the error message to reflect this change.

gdb/
	* record-btrace.c (record_btrace_xfer_partial)
	(record_btrace_store_registers, record_btrace_prepare_to_store):
	Call record_btrace_is_replaying with inferior_ptid instead of
	minus_one_ptid.
	(record_btrace_store_registers): Change error message.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] btrace: non-stop
@ 2015-09-18 14:47 sergiodj+buildbot
  2015-09-19 16:29 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-09-18 14:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cbb55fa7a110e499dae0170060d762eb3f243768 ***

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

btrace: non-stop

Support non-stop mode in record btrace.

gdb/
	* record-btrace.c (record_btrace_open): Remove non_stop check.
	* NEWS: Announce that record btrace supports non-stop mode.

testsuite/
	* gdb.btrace/non-stop.c: New.
	* gdb.btrace/non-stop.exp: New.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] btrace: resume all requested threads
@ 2015-09-18 14:15 sergiodj+buildbot
  2015-09-19  9:43 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-09-18 14:15 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0ca912dfef6289f9d2cd7d70b7ec80883a9b4395 ***

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

btrace: resume all requested threads

The record targets are implicitly schedlocked.  They only step the current
thread and keep other threads where they are.

Change record btrace to step all requested threads in to_resume.

For maintenance and debugging, we keep the old behaviour when the target below
is not non-stop.  Enable with "maint set target-non-stop on".

gdb/
	* record-btrace.c (record_btrace_resume_thread): A move request
	overwrites a previous move request.
	(record_btrace_find_resume_thread): Removed.
	(record_btrace_resume): Resume all requested threads.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] btrace: split record_btrace_step_thread
@ 2015-09-18 13:50 sergiodj+buildbot
  2015-09-18 22:17 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-09-18 13:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d825d248105e1c9a13fef4a35e76b6f4912e3792 ***

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

btrace: split record_btrace_step_thread

The code for BTHR_STEP and BTHR_CONT is fairly similar.  Extract the common
parts into a new function record_btrace_single_step_forward.  The function
returns TARGET_WAITKIND_SPURIOUS to indicate that the single-step completed
without triggering a trap.

Same for BTHR_RSTEP and BTHR_RCONT.

gdb/
	* record-btrace.c (btrace_step_spurious)
	(record_btrace_single_step_forward)
	(record_btrace_single_step_backward): New.
	(record_btrace_step_thread): Call record_btrace_single_step_forward
	and record_btrace_single_step_backward.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Remove one unnecessary iteration in insertion sort
@ 2015-09-18  4:32 sergiodj+buildbot
  2015-09-18  8:58 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-09-18  4:32 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b29b8669ad250df649a0f02c5575e7163a2cd9e4 ***

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

Remove one unnecessary iteration in insertion sort

	PR 18867
	* elflink.c (elf_link_adjust_relocs): Correct start of insertion
	sort main loop.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Fix argument to compiled_cond, and add cases for compiled-condition.
@ 2015-09-16 17:26 sergiodj+buildbot
  2015-09-18  4:21 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-09-16 17:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d78908cff50f281dab6390646fb1b7c58236d83e ***

Author: Wei-cheng Wang <cole945@gmail.com>
Branch: master
Commit: d78908cff50f281dab6390646fb1b7c58236d83e

Fix argument to compiled_cond, and add cases for compiled-condition.

This patch fixes the argument passed to compiled_cond.  It should be
regs buffer instead of tracepoint_hit_ctx.  Test case is added as
well for testing compiled-cond.

gdb/gdbserver/ChangeLog

2015-09-16  Wei-cheng Wang  <cole945@gmail.com>

	* tracepoint.c (eval_result_type): Change prototype.
	(condition_true_at_tracepoint): Fix argument to compiled_cond.

gdb/testsuite/ChangeLog

2015-09-16  Wei-cheng Wang  <cole945@gmail.com>

	* gdb.trace/ftrace.exp: (test_ftrace_condition) New function
	for testing bytecode compilation.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Make it easier to debug non-stop-fair-events.exp
@ 2015-09-16 15:38 sergiodj+buildbot
  2015-09-18  4:09 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-09-16 15:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d136eff549649f23b12121575362dfa09343ea0a ***

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

Make it easier to debug non-stop-fair-events.exp

If we enable infrun debug running this test, it quickly fails with a
full expect buffer.  That can be simply handled with a couple
exp_continues.  As it's annoying to hack this every time we need to
debug the test, this patch adds bits to enable debugging support
easily, with a one-line change.

And then, if any iteration of the test fails, we end up with a long
cascade of time outs.  Just bail out when we see the first fail.

gdb/testsuite/
2015-09-16  Pedro Alves  <palves@redhat.com>

	* gdb.threads/non-stop-fair-events.exp (gdb_test_no_anchor)
	(enable_debug): New procedures.
	(test): Use them.  Bail out if waiting for threads fails.
	(top level): Bail out if a test fails.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Don't skip gdb.asm/asm-source.exp on aarch64
@ 2015-09-16 15:03 sergiodj+buildbot
  2015-09-18  3:51 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-09-16 15:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 991f019c506528fa94ac173db6f1120f8b2373bf ***

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

Don't skip gdb.asm/asm-source.exp on aarch64

This patch adds gdb.asm/aarch64.inc, so asm-source.exp isn't skipped
on aarch64 any more.

gdb/testsuite:

2015-09-16  Yao Qi  <yao.qi@linaro.org>

	* gdb.asm/asm-source.exp: Set asm-arch for
	aarch64*-*-* target.
	* gdb.asm/aarch64.inc: New file.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Handle clang naming of function static local variable.
@ 2015-09-15 21:24 sergiodj+buildbot
  2015-09-17 11:26 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-09-15 21:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b326e5870e54f52d52c32388f7f6e07454e2f2c2 ***

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

Handle clang naming of function static local variable.

clang names the local variable t_structs_a.buf.

gdb/testsuite/ChangeLog:

	* gdb.base/callfuncs.exp (do_function_calls): Handle clang naming
	of function static local variable.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [ppc64le] Use skip_entrypoint for skip_trampoline_code
@ 2015-09-15 18:25 sergiodj+buildbot
  2015-09-16 16:46 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-09-15 18:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 141c5cc4c44a6ce1a5c628c0f4849a8b1c91d383 ***

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

[ppc64le] Use skip_entrypoint for skip_trampoline_code

ppc64le loses control when stepping between two PLT-called functions inside
a shared library:

29        shlib_second (); /* first-hit */^M
(gdb) PASS: gdb.base/solib-intra-step.exp: first-hit
step^M
^M
Program received signal SIGABRT, Aborted.^M
0x00003fffb7cbe578 in __GI_raise (sig=<optimized out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56^M
56        return INLINE_SYSCALL (tgkill, 3, pid, selftid, sig);^M
(gdb) FAIL: gdb.base/solib-intra-step.exp: second-hit
->
29        shlib_second (); /* first-hit */^M
(gdb) PASS: gdb.base/solib-intra-step.exp: first-hit
step^M
shlib_second () at ./gdb.base/solib-intra-step-lib.c:23^M
23        abort (); /* second-hit */^M
(gdb) PASS: gdb.base/solib-intra-step.exp: second-hit

This is because gdbarch_skip_trampoline_code() will resolve the final function
as shlib_second+0 and place there the breakpoint, but ld.so will jump after
the breakpoint - at shlib_second+8 - as it is ELFv2 local symbol optimization:

Dump of assembler code for function shlib_second:
   0x0000000000000804 <+0>:     addis   r2,r12,2
   0x0000000000000808 <+4>:     addi    r2,r2,30668
   0x000000000000080c <+8>:     mflr    r0

Currently gdbarch_skip_entrypoint() has been called in skip_prologue_sal() and
fill_in_stop_func() but that is not enough.  I believe
gdbarch_skip_entrypoint() should be called after every
gdbarch_skip_trampoline_code().

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

	* linespec.c (minsym_found): Call gdbarch_skip_entrypoint.
	* ppc64-tdep.c (ppc64_skip_trampoline_code): Rename to ...
	(ppc64_skip_trampoline_code_1): ... here.
	(ppc64_skip_trampoline_code): New wrapper function.
	* symtab.c (find_function_start_sal): Call gdbarch_skip_entrypoint.

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

	* gdb.opt/solib-intra-step-lib.c: New file.
	* gdb.opt/solib-intra-step-main.c: New file.
	* gdb.opt/solib-intra-step.exp: New file.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Fix typo
@ 2015-09-15 17:18 sergiodj+buildbot
  2015-09-16  0:44 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-09-15 17:18 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7c5d0fad2e732bdea75f585b67fc1a0cc4d3107f ***

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

Fix typo

gdb/gdbserver:

2015-09-15  Yao Qi  <yao.qi@linaro.org>

	* server.c (handle_query): Check string comparison using
	"else if" instead of "if".


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [gdbserver] Rename supports_conditional_breakpoints to supports_hardware_single_step
@ 2015-09-15 13:45 sergiodj+buildbot
  2015-09-15 16:40 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-09-15 13:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 70b90b91bf77e72a36abdef039234359195b1942 ***

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

[gdbserver] Rename supports_conditional_breakpoints to supports_hardware_single_step

In my patch https://sourceware.org/ml/gdb-patches/2015-04/msg01110.html
a new target_ops hook supports_conditional_breakpoints was added to
disable conditional breakpoints if target doesn't have hardware single
step.  This patch is to generalize this hook from
supports_conditional_breakpoints to supports_hardware_single_step,
so that the following patch can use it.

gdb/gdbserver:

2015-09-15  Yao Qi  <yao.qi@linaro.org>

	* linux-low.c (linux_supports_conditional_breakpoints): Rename
	it to ...
	(linux_supports_hardware_single_step): ... New function.
	(linux_target_ops): Update.
	* lynx-low.c (lynx_target_ops): Set field
	supports_hardware_single_step to target_can_do_hardware_single_step.
	* nto-low.c (nto_target_ops): Likewise.
	* spu-low.c (spu_target_ops): Likewise.
	* win32-low.c (win32_target_ops): Likewise.
	* target.c (target_can_do_hardware_single_step): New function.
	* target.h (struct target_ops) <supports_conditional_breakpoints>:
	Remove.  <supports_hardware_single_step>: New field.
	(target_supports_conditional_breakpoints): Remove.
	(target_supports_hardware_single_step): New macro.
	(target_can_do_hardware_single_step): Declare.
	* server.c (handle_query): Use target_supports_hardware_single_step
	instead of target_supports_conditional_breakpoints.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] aarch64 multi-arch support (part 2): siginfo fixup
@ 2015-09-15 10:25 sergiodj+buildbot
  2015-09-15 13:40 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-09-15 10:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ade90bdeb78ccaeb294e34af04751f2f649a324f ***

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

aarch64 multi-arch support (part 2): siginfo fixup

This patch is to fixup the siginfo_t when aarch64 gdb or gdbserver
read from or write to the arm inferior.  It is to convert the
"struct siginfo_t" between aarch64 and arm, which is quite mechanical.

gdb/gdbserver:

2015-09-15  Yao Qi  <yao.qi@linaro.org>

	* linux-aarch64-low.c (aarch64_linux_siginfo_fixup): New
	function.
	(struct linux_target_ops the_low_target): Install
	aarch64_linux_siginfo_fixup.

gdb:

2015-09-15  Yao Qi  <yao.qi@linaro.org>

	* aarch64-linux-nat.c (aarch64_linux_siginfo_fixup): New function.
	(_initialize_aarch64_linux_nat): Call linux_nat_set_siginfo_fixup.
	* nat/aarch64-linux.c (aarch64_compat_siginfo_from_siginfo):
	New function.
	(aarch64_siginfo_from_compat_siginfo): New function.
	* nat/aarch64-linux.h: Include signal.h.
	(compat_int_t, compat_uptr_t, compat_time_t): Typedef.
	(compat_timer_t, compat_clock_t): Likewise.
	(struct compat_timeval): New.
	(union compat_sigval): New.
	(struct compat_siginfo): New.
	(cpt_si_pid, cpt_si_uid, cpt_si_timerid): New macros.
	(cpt_si_overrun, cpt_si_status, cpt_si_utime): Likewise.
	(cpt_si_stime, cpt_si_ptr, cpt_si_addr): Likewise.
	(cpt_si_band, cpt_si_fd): Likewise.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Fix the SH behavior for EF_SH_PIC flag in FDPIC ABI
@ 2015-09-15  9:41 sergiodj+buildbot
  2015-09-15 10:23 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-09-15  9:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fbedb42d07cdc97a5bc698d1f7732ee776763cbc ***

Author: Rich Felker <dalias@libc.org>
Branch: master
Commit: fbedb42d07cdc97a5bc698d1f7732ee776763cbc

Fix the SH behavior for EF_SH_PIC flag in FDPIC ABI

Fix it so that it's compatible with the kernel and other FDPIC targets.

* elf32-sh.c (sh_elf_relocate_section): Set EF_SH_PIC flag
instead of clearing it on cross-section relocations.
(sh_elf_merge_private_data): Clear EF_SH_PIC flag by default.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [Ada] Fix the evaluation of access to packed array subscript
@ 2015-09-14 15:05 sergiodj+buildbot
  2015-09-15  9:38 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-09-14 15:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 919e6dbe9b61a27e8f7f89121ba182907df461a3 ***

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

[Ada] Fix the evaluation of access to packed array subscript

This change is relevant only for standard DWARF (as opposed to the GNAT
encodings extensions): at the time of writing it only makes a difference
with GCC patches that are to be integrated: see in particular
<https://gcc.gnu.org/ml/gcc-patches/2015-07/msg01364.html>.

Given the following Ada declarations:

    type Small is mod 2 ** 6;
    type Array_Type is array (0 .. 9) of Small
       with Pack;
    type Array_Access is access all Array_Type;

    A  : aliased Array_Type := (1, 2, 3, 4, 5, 6, 7, 8, 9, 10);
    AA : constant Array_Type := A'Access;

Before this change, we would get the following GDB session:

    (gdb) print aa.all(2)
    $1 = 3
    (gdb) print aa(2)
    $2 = 16

This is wrong: both expression should yield the same value: 3.  The
problem is simply that the routine which handles accesses to arrays lack
general handling for packed arrays.  After this patch, we have the
expected output:

    (gdb) print aa.all(2)
    $1 = 3
    (gdb) print aa(2)
    $2 = 3

gdb/ChangeLog:

	* ada-lang.c (ada_value_ptr_subscript): Update the heading
	comment.  Handle packed arrays.

gdb/testsuite/ChangeLog:

	* gdb.ada/access_to_packed_array.exp: New testcase.
	* gdb.ada/access_to_packed_array/foo.adb: New file.
	* gdb.ada/access_to_packed_array/pack.adb: New file.
	* gdb.ada/access_to_packed_array/pack.ads: New file.

Tested on x86_64-linux, no regression.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] btrace, test: remove buffer-size test with unlimited buffer size
@ 2015-09-14 12:50 sergiodj+buildbot
  2015-09-14 15:27 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-09-14 12:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 157280a4d6b8c49703c698bda5546d7b2cc21e35 ***

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

btrace, test: remove buffer-size test with unlimited buffer size

The gdb.btrace/buffer-size.exp test starts recording with an unlimited
buffer size.  This will, for a short time, use up most if not all BTS
resources.

I don' think this test is necessary.  Remove it.

testsuite/
	* gdb.btrace/buffer-size.exp: Remove recording with unlimited BTS
	buffer size test.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Extended-remote follow-exec
@ 2015-09-11 18:33 sergiodj+buildbot
  2015-09-12 17:11 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-09-11 18:33 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 94585166dfea8232c248044f9f4b1c217dc4ac2e ***

Author: Don Breazeal <donb@codesourcery.com>
Branch: master
Commit: 94585166dfea8232c248044f9f4b1c217dc4ac2e

Extended-remote follow-exec

This patch implements support for exec events on extended-remote Linux
targets.  Follow-exec-mode and rerun behave as expected.  Catchpoints and
test updates are implemented in subsequent patches.

This patch was derived from a patch posted last October:
https://sourceware.org/ml/gdb-patches/2014-10/msg00877.html.
It was originally based on some work done by Luis Machado in 2013.

IMPLEMENTATION
----------------
Exec events are enabled via ptrace options.

When an exec event is detected by gdbserver, the existing process
data, along with all its associated lwp and thread data, is deleted
and replaced by data for a new single-threaded process.  The new
process data is initialized with the appropriate parts of the state
of the execing process.  This approach takes care of several potential
pitfalls, including:

 * deleting the data for an execing non-leader thread before any
   wait/sigsuspend occurs
 * correctly initializing the architecture of the execed process

We then report the exec event using a new RSP stop reason, "exec".

When GDB receives an "exec" event, it saves the status in the event
structure's target_waitstatus field, like what is done for remote fork
events.  Because the original and execed programs may have different
architectures, we skip parsing the section of the stop reply packet
that contains register data.  The register data will be retrieved
later after the inferior's architecture has been set up by
infrun.c:follow_exec.

At that point the exec event is handled by the existing event handling
in GDB.  However, a few changes were necessary so that
infrun.c:follow_exec could accommodate the remote target.

 * Where follow-exec-mode "new" is handled, we now call
   add_inferior_with_spaces instead of add_inferior with separate calls
   to set up the program and address spaces.  The motivation for this
   is that add_inferior_with_spaces also sets up the initial architecture
   for the inferior, which is needed later by target_find_description
   when it calls target_gdbarch.

 * We call a new target function, target_follow_exec.  This function
   allows us to store the execd_pathname in the inferior, instead of
   using the static string remote_exec_file from remote.c.  The static
   string didn't work for follow-exec-mode "new", since once you switched
   to the execed program, the original remote exec-file was lost.  The
   execd_pathname is now stored in the inferior's program space as a
   REGISTRY field.  All of the requisite mechanisms for this are
   defined in remote.c.

gdb/gdbserver/ChangeLog:

	* linux-low.c (linux_mourn): Static declaration.
	(linux_arch_setup): Move in front of
	handle_extended_wait.
	(linux_arch_setup_thread): New function.
	(handle_extended_wait): Handle exec events.  Call
	linux_arch_setup_thread.  Make event_lwp argument a
	pointer-to-a-pointer.
	(check_zombie_leaders): Do not check stopped threads.
	(linux_low_ptrace_options): Add PTRACE_O_TRACEEXEC.
	(linux_low_filter_event): Add lwp and thread for exec'ing
	non-leader thread if leader thread has been deleted.
	Refactor code into linux_arch_setup_thread and call it.
	Pass child lwp pointer by reference to handle_extended_wait.
	(linux_wait_for_event_filtered): Update comment.
	(linux_wait_1): Prevent clobbering exec event status.
	(linux_supports_exec_events): New function.
	(linux_target_ops) <supports_exec_events>: Initialize new member.
	* lynx-low.c (lynx_target_ops) <supports_exec_events>: Initialize
	new member.
	* remote-utils.c (prepare_resume_reply): New stop reason 'exec'.
	* server.c (report_exec_events): New global variable.
	(handle_query): Handle qSupported query for exec-events feature.
	(captured_main): Initialize report_exec_events.
	* server.h (report_exec_events): Declare new global variable.
	* target.h (struct target_ops) <supports_exec_events>: New
	member.
	(target_supports_exec_events): New macro.
	* win32-low.c (win32_target_ops) <supports_exec_events>:
	Initialize new member.

gdb/ChangeLog:

	* infrun.c (follow_exec): Use process-style ptid for
	exec message.  Call add_inferior_with_spaces and
	target_follow_exec.
	* nat/linux-ptrace.c (linux_supports_traceexec): New function.
	* nat/linux-ptrace.h (linux_supports_traceexec): Declare.
	* remote.c (remote_pspace_data): New static variable.
	(remote_pspace_data_cleanup): New function.
	(get_remote_exec_file): New function.
	(set_remote_exec_file_1): New function.
	(set_remote_exec_file): New function.
	(show_remote_exec_file): New function.
	(remote_exec_file): Delete static variable.
	(anonymous enum) <PACKET_exec_event_feature> New
	enumeration constant.
	(remote_protocol_features): Add entry for exec-events feature.
	(remote_query_supported): Add client side of qSupported query
	for exec-events feature.
	(remote_follow_exec): New function.
	(remote_parse_stop_reply): Handle 'exec' stop reason.
	(extended_remote_run, extended_remote_create_inferior): Call
	get_remote_exec_file and set_remote_exec_file_1.
	(init_extended_remote_ops) <to_follow_exec>: Initialize new
	member.
	(_initialize_remote): Call
	register_program_space_data_with_cleanup.  Call
	add_packet_config_cmd for remote exec-events feature.
	Modify call to add_setshow_string_noescape_cmd for exec-file
	to use new functions set_remote_exec_file and
	show_remote_exec_file.
	* target-debug.h, target-delegates.c: Regenerated.
	* target.c (target_follow_exec): New function.
	* target.h (struct target_ops) <to_follow_exec>: New member.
	(target_follow_exec): Declare new function.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] gdb/18947: [aarch64]Step into shared library is very slow.
@ 2015-09-11 14:43 sergiodj+buildbot
  2015-09-11 18:26 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-09-11 14:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6dcaef99fab7e59e3eeb16a95d4c29b7b499b408 ***

Author: Mihail-Marian Nistor <mihail.nistor@freescale.com>
Branch: master
Commit: 6dcaef99fab7e59e3eeb16a95d4c29b7b499b408

gdb/18947: [aarch64]Step into shared library is very slow.

Install gdbarch_skip_solib_resolver on aarch64 GNU/Linux

gdb/ChangeLog:

2015-09-11  Mihail-Marian Nistor  <mihail.nistor@freescale.com>

	PR gdb/18947
	* aarch64-linux-tdep.c: (aarch64_linux_init_abi): Install
	glibc_skip_solib_resolver as gdbarch_skip_solib_resolver callback.

Signed-off-by: Mihail-Marian Nistor <mihail.nistor@freescale.com>


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Constify variables in ada-lang.c
@ 2015-09-10 15:23 sergiodj+buildbot
  2015-09-11 14:39 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-09-10 15:23 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 108d56a48b0970a53e237af76440df4a75ff7329 ***

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

Constify variables in ada-lang.c

I found this const/not const mixup found by building in C++ mode.

gdb/ChangeLog:

	* ada-lang.c (ada_search_struct_field): Constify parameters
	and/or variables..
	(xget_renaming_scope): Likewise.
	(ada_is_redundant_range_encoding): Likewise.
	(scan_discrim_bound): Likewise.
	(to_fixed_range_type): Likewise.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] S/390: Fix MASK_RIE_R0PI and MASK_RIE_R0PU.
@ 2015-09-10 13:38 sergiodj+buildbot
  2015-09-11 14:35 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-09-10 13:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9c1c2a0bb14ff5f74e68a7f1d67b8a7021c71cdf ***

Author: Andreas Krebbel <krebbel@linux.vnet.ibm.com>
Branch: master
Commit: 9c1c2a0bb14ff5f74e68a7f1d67b8a7021c71cdf

S/390: Fix MASK_RIE_R0PI and MASK_RIE_R0PU.

This makes objdump to be able to recognize some of the extended
mnemonics more often.  It does not lead to wrong being generated.

opcodes/ChangeLog:

2015-09-10  Andreas Krebbel  <krebbel@linux.vnet.ibm.com>

	* s390-opc.c: Fix MASK_RIE_R0PI and MASK_RIE_R0PU.

gas/testsuite/ChangeLog:

2015-09-10  Andreas Krebbel  <krebbel@linux.vnet.ibm.com>

	* gas/s390/zarch-z10.d: Fix testcase for compare and branch
	extended mnemonics.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Garbage collect thread continuations
@ 2015-09-09 19:44 sergiodj+buildbot
  2015-09-10 15:32 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-09-09 19:44 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a85a3079233ddf4c5537ec90c03d3394b93ef355 ***

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

Garbage collect thread continuations

Nothing uses thread continuations anymore.

(inferior continuations are still used by the attach command.)

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

	* continuations.c (add_continuation, restore_thread_cleanup)
	(do_all_continuations_ptid, do_all_continuations_thread_callback)
	(do_all_continuations_thread, do_all_continuations)
	(discard_all_continuations_thread_callback)
	(discard_all_continuations_thread, discard_all_continuations)
	(add_intermediate_continuation)
	(do_all_intermediate_continuations_thread_callback)
	(do_all_intermediate_continuations_thread)
	(do_all_intermediate_continuations)
	(discard_all_intermediate_continuations_thread_callback)
	(discard_all_intermediate_continuations_thread)
	(discard_all_intermediate_continuations): Delete.
	* continuations.h (add_continuation, do_all_continuations)
	(do_all_continuations_thread, discard_all_continuations)
	(discard_all_continuations_thread, add_intermediate_continuation)
	(do_all_intermediate_continuations)
	(do_all_intermediate_continuations_thread)
	(discard_all_intermediate_continuations)
	(discard_all_intermediate_continuations_thread): Delete
	declarations.
	* event-top.c (stdin_event_handler): Delete references to
	continuations.
	* gdbthread.h (struct thread_info): Delete continuations and
	intermediate_continuations fields.
	* inf-loop.c (inferior_event_handler): Remove references to
	continuations.
	* infrun.c (infrun_thread_stop_requested_callback): Remove
	references to continuations.
	* target.h (enum inferior_event_type) <INF_EXEC_CONTINUE>: Delete.
	* thread.c: Don't include "continuations.h".
	(clear_thread_inferior_resources): Remove references to
	continuations.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] * gdb.python/py-prettyprint.exp: Check result of run_lang_tests.
@ 2015-09-09 18:53 sergiodj+buildbot
  2015-09-11  2:13 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-09-09 18:53 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e70b6e8eee4fc1ad1270a63ad000d11fd657d7a7 ***

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

* gdb.python/py-prettyprint.exp: Check result of run_lang_tests.

gdb/testsuite/ChangeLog:

	* gdb.python/py-prettyprint.exp: Check result of run_lang_tests.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Delete enum inferior_event_handler::INF_TIMER
@ 2015-09-09 18:25 sergiodj+buildbot
  2015-09-10 18:27 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-09-09 18:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cfe7570334fc9aefc64bdb0791fec03a736f2851 ***

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

Delete enum inferior_event_handler::INF_TIMER

Nothing ever uses this.

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

	* inf-loop.c (inferior_event_handler): Delete INF_TIMER case.
	* target.h (enum inferior_event_type) <INF_TIMER>: Delete.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Replace "struct continuation" mechanism by something more extensible
@ 2015-09-09 17:48 sergiodj+buildbot
  2015-09-10  6:30 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-09-09 17:48 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 243a925328f8e3184b2356bee497181049c0174f ***

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

Replace "struct continuation" mechanism by something more extensible

This adds an object oriented replacement for the "struct continuation"
mechanism, and converts the stepping commands (step, next, stepi,
nexti) and the "finish" commands to use it.

It adds a new thread "class" (struct thread_fsm) that contains the
necessary info and callbacks to manage the state machine of a thread's
execution command.

This allows getting rid of some hacks.  E.g., in fetch_inferior_event
and normal_stop we no longer need to know whether a thread is doing a
multi-step (e.g., step N).  This effectively makes the
intermediate_continuations unused -- they'll be garbage collected in a
separate patch.  (They were never a proper abstraction, IMO.  See how
fetch_inferior_event needs to check step_multi before knowing whether
to call INF_EXEC_CONTINUE or INF_EXEC_COMPLETE.)

The target async vs !async uiout hacks in mi_on_normal_stop go away
too.

print_stop_event is no longer called from normal_stop.  Instead it is
now called from within each interpreter's normal_stop observer.  This
clears the path to make each interpreter print a stop event the way it
sees fit.  Currently we have some hacks in common code to
differenciate CLI vs TUI vs MI around this area.

The "finish" command's FSM class stores the return value plus that
value's position in the value history, so that those can be printed to
both MI and CLI's streams.  This fixes the CLI "finish" command when
run from MI -- it now also includes the function's return value in the
CLI stream:

  (gdb)
  ~"callee3 (strarg=0x400730 \"A string argument.\") at src/gdb/testsuite/gdb.mi/basics.c:35\n"
  ~"35\t}\n"
 +~"Value returned is $1 = 0\n"
  *stopped,reason="function-finished",frame=...,gdb-result-var="$1",return-value="0",thread-id="1",stopped-threads="all",core="0"
 -FAIL: gdb.mi/mi-cli.exp: CLI finish: check CLI output
 +PASS: gdb.mi/mi-cli.exp: CLI finish: check CLI output

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

	* Makefile.in (COMMON_OBS): Add thread-fsm.o.
	* breakpoint.c (handle_jit_event): Print debug output.
	(bpstat_what): Split event callback handling to ...
	(bpstat_run_callbacks): ... this new function.
	(momentary_bkpt_print_it): No longer handle bp_finish here.
	* breakpoint.h (bpstat_run_callbacks): Declare.
	* gdbthread.h (struct thread_info) <step_multi>: Delete field.
	<thread_fsm>: New field.
	(thread_cancel_execution_command): Declare.
	* infcmd.c: Include thread-fsm.h.
	(struct step_command_fsm): New.
	(step_command_fsm_ops): New global.
	(new_step_command_fsm, step_command_fsm_prepare): New functions.
	(step_1): Adjust to use step_command_fsm_prepare and
	prepare_one_step.
	(struct step_1_continuation_args): Delete.
	(step_1_continuation): Delete.
	(step_command_fsm_should_stop): New function.
	(step_once): Delete.
	(step_command_fsm_clean_up, step_command_fsm_async_reply_reason)
	(prepare_one_step): New function, based on step_once.
	(until_next_command): Remove step_multi reference.
	(struct return_value_info): New.
	(print_return_value): Rename to ...
	(print_return_value_1): ... this.  New struct return_value_info
	parameter.  Adjust.
	(print_return_value): Reimplement as wrapper around
	print_return_value_1.
	(struct finish_command_fsm): New.
	(finish_command_continuation): Delete.
	(finish_command_fsm_ops): New global.
	(new_finish_command_fsm, finish_command_fsm_should_stop): New
	functions.
	(finish_command_fsm_clean_up, finish_command_fsm_return_value):
	New.
	(finish_command_continuation_free_arg): Delete.
	(finish_command_fsm_async_reply_reason): New.
	(finish_backward, finish_forward): Change symbol parameter to a
	finish_command_fsm.  Adjust.
	(finish_command): Create a finish_command_fsm.  Adjust.
	* infrun.c: Include "thread-fsm.h".
	(clear_proceed_status_thread): Delete the thread's FSM.
	(infrun_thread_stop_requested_callback): Cancel the thread's
	execution command.
	(clean_up_just_stopped_threads_fsms): New function.
	(fetch_inferior_event): Handle the event_thread's should_stop
	method saying the command isn't done yet.
	(process_event_stop_test): Run breakpoint callbacks here.
	(print_stop_event): Rename to ...
	(print_stop_location): ... this.
	(restore_current_uiout_cleanup): New function.
	(print_stop_event): Reimplement.
	(normal_stop): No longer notify the end_stepping_range observers
	here handle "step N" nor "finish" here.  No longer call
	print_stop_event here.
	* infrun.h (struct return_value_info): Forward declare.
	(print_return_value): Declare.
	(print_stop_event): Change prototype.
	* thread-fsm.c: New file.
	* thread-fsm.h: New file.
	* thread.c: Include "thread-fsm.h".
	(thread_cancel_execution_command): New function.
	(clear_thread_inferior_resources): Call it.
	* cli/cli-interp.c (cli_on_normal_stop): New function.
	(cli_interpreter_init): Install cli_on_normal_stop as normal_stop
	observer.
	* mi/mi-interp.c: Include "thread-fsm.h".
	(restore_current_uiout_cleanup): Delete.
	(mi_on_normal_stop): If the thread has an FSM associated, and it
	finished, ask it for the async-reply-reason to print.  Always call
	print_stop_event here, regardless of the top-level interpreter.
	Check bpstat_what to tell whether an asynchronous breakpoint hit
	triggered.
	* tui/tui-interp.c (tui_on_normal_stop): New function.
	(tui_init): Install tui_on_normal_stop as normal_stop observer.

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

	* gdb.mi/mi-cli.exp: Add CLI finish tests.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [AArch64] Sort IS_AARCH64_TLS_RELAX_RELOC in alphabetic order
@ 2015-09-09 13:36 sergiodj+buildbot
  2015-09-09 22:40 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-09-09 13:36 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4af68b9c78aad1b82bfd6e2e960747eb160bb4d8 ***

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

[AArch64] Sort IS_AARCH64_TLS_RELAX_RELOC in alphabetic order

This can also speedup the check as TLSDESC is the default model for
global/local dynamic that the big "||" check can finish more quickly
than putting them at the bottom.

2015-09-09  Jiong. Wang  <jiong.wang@arm.com>

bfd/
  * elfnn-aarch64.c (IS_AARCH64_TLS_RELAX_RELOC): Sort alphabetically.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] S/390: Remove trailing zeros on 4-bytes opcodes.
@ 2015-09-09 12:30 sergiodj+buildbot
  2015-09-09 16:42 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-09-09 12:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d660d56578248bf3bb56150295cecc763f112061 ***

Author: Andreas Krebbel <krebbel@linux.vnet.ibm.com>
Branch: master
Commit: d660d56578248bf3bb56150295cecc763f112061

S/390: Remove trailing zeros on 4-bytes opcodes.

This is a NOP change only relevant when reading the file or parsing it
with other tools.

opcodes/ChangeLog:

2015-09-09  Andreas Krebbel  <krebbel@linux.vnet.ibm.com>

	* s390-opc.c: Add OP32 definition.
	* s390-opc.txt: Reduce the opcode padding of some extended
	mnemonics from 6 to the actual length (which is 4).


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] S/390: Fix opcode of ppno.
@ 2015-09-09 12:23 sergiodj+buildbot
  2015-09-09 14:24 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-09-09 12:23 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c694bafc0bc795a63e607689cc35ad44047790e6 ***

Author: Andreas Krebbel <krebbel@linux.vnet.ibm.com>
Branch: master
Commit: c694bafc0bc795a63e607689cc35ad44047790e6

S/390: Fix opcode of ppno.

opcodes/ChangeLog:

2015-09-09  Andreas Krebbel  <krebbel@linux.vnet.ibm.com>

	* s390-opc.txt: Fix opcode of ppno instruction.

gas/testsuite/ChangeLog:

2015-09-09  Andreas Krebbel  <krebbel@linux.vnet.ibm.com>

	* gas/s390/zarch-z13.d: Fix opcode of ppno instruction.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Improve hand-call-in-threads.exp failure handling.
@ 2015-09-09  2:59 sergiodj+buildbot
  2015-09-09  5:39 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-09-09  2:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c0fa8fbd1c2f02921b90083e595a8452d3d51ba2 ***

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

Improve hand-call-in-threads.exp failure handling.

2015-09-08  Sandra Loosemore  <sandra@codesourcery.com>

	gdb/testsuite/
	* gdb.threads/hand-call-in-threads.exp: Make sure the thread
	command actually switches threads.  Give up on remaining
	tests if target fails to stop at breakpoint.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [Ada] Make string_char_type a true TYPE_CODE_CHAR type in Ada
@ 2015-09-03 16:02 sergiodj+buildbot
  2015-09-03 18:55 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-09-03 16:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cd7c1778e72ce29f7f42d91ab08ae855c7ef8f7a ***

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

[Ada] Make string_char_type a true TYPE_CODE_CHAR type in Ada

Before this change, trying to call an overloaded function with at least
one character literal in argument would fail.  For instance, given these
two functions:

   function F (C : Character) return Integer is
   begin
      return Character'Pos (C);
   end F;

   function F (I : Integer) return Integer is
   begin
      return -I;
   end F;

We would get the following GDB session:

    (gdb) p f('A')
    $1 = -65
    (gdb) p f(1)
    $1 = -1

This is wrong because the first call should select the first F function
and thus return 65.

The root problem is that ada-lang.c:ada_language_arch_info stores in
string_char_type a type whose code is TYPE_CODE_INT instead of
TYPE_CODE_CHAR.  As a result, all parsed character literals are turned
into integer values and during overload matching, the TYPE_CODE_CHAR
formal rejects the TYPE_CODE_INT actual.

This change turns string_char_type into a true TYPE_CODE_CHAR type in
ada-lang.c so that we have instead the expected:

    (gdb) p f('A')
    $1 = 65

gdb/ChangeLog:

	* ada-lang.c (ada_language_arch_info): Create a TYPE_CODE_CHAR
	type instead of a TYPE_CODE_INT one for the string_char_type
	and the ada_primitive_type_char types.

gdb/testsuite/ChangeLog:

	* gdb.ada/funcall_char.exp: New testcase.
	* gdb.ada/funcall_char/foo.adb: New file.

Tested on x86_64-linux, no regression.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Use gdbarch obstack to allocate the TYPE_NAME string in arch_type
@ 2015-09-03  1:19 sergiodj+buildbot
  2015-09-03  7:34 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-09-03  1:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6c214e7cb397bf0de539fec640e764f0131e9677 ***

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

Use gdbarch obstack to allocate the TYPE_NAME string in arch_type

Since the type whose name is being set is now being allocated on the
gdbarch obstack, we should allocate its TYPE_NAME on the obstack too.
This reduces the number of individual valgrind warnings for the command
"gdb gdb" from ~300 to ~150.

Tested on x86_64-unknown-linux-gnu.

gdb/ChangeLog:

	* gdb_obstack.h (obstack_strdup): Declare.
	* gdb_obstack.c (obstack_strdup): Define.
	* gdbarch.sh (gdbarch_obstack_strdup): Declare and define.
	* gdbarch.c: Regenerate.
	* gdbarch.h: Regenerate.
	* gdbtypes.c (arch_type): Use gdbarch_obstack_strdup.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Update documentation of function copy_type_recursive
@ 2015-09-03  1:11 sergiodj+buildbot
  2015-09-03  5:24 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-09-03  1:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT eed8b28a07c32f835dfb4ff21fb9c0bf33c738df ***

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

Update documentation of function copy_type_recursive

Following commit 8f57eec2fb3 ("Use gdbarch obstack to allocate types in
alloc_type_arch") it is no longer the case that the type returned by
copy_type_recursive is allocated using malloc.  Because the function
uses alloc_type_arch internally, the new type is now allocated on the
gdbarch associated with the type, and is thus owned by that gdbarch.

gdb/ChangeLog:

	* gdbtypes.c (copy_type_recursive): Update documentation.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Rename R_386_irelative to R_386_ext2
@ 2015-09-02 12:24 sergiodj+buildbot
  2015-09-02 13:59 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-09-02 12:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c74be520ba8ed2d013d43916b923b837294343cc ***

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

Rename R_386_irelative to R_386_ext2

	* elf32-i386.c (R_386_irelative): Renamed to ...
	(R_386_ext2): This.
	(R_386_vt_offset): Updated.
	(elf_i386_rtype_to_howto): Likewise.
	(elf_i386_relocate_section): Likewise.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Initialize variable and silence GCC warning from last commit
@ 2015-09-02  4:42 sergiodj+buildbot
  2015-09-02  7:56 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-09-02  4:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ad1c917a79e8c5aa67657f148415c1bee01b240f ***

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

Initialize variable and silence GCC warning from last commit

BuildBot e-mailed me to let me know that my last commit broke GDB on
RHEL-7.1 s390x.  On solib-svr4.c:svr4_handle_solib_event, 'val' now
needs to be initialized as NULL because it is inside a TRY..CATCH
block.  This patch does that.  Pushed as obvious.

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

	* solib-svr4.c (svr4_handle_solib_event): Initialize 'val' as NULL


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Catching errors on probes-based dynamic linker interface
@ 2015-09-02  4:28 sergiodj+buildbot
  2015-09-02  7:12 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-09-02  4:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3bd7e5b7ee5ea0b3bbb4030ca841f66faad74f0f ***

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

Catching errors on probes-based dynamic linker interface

This patch is intended to make the interaction between the
probes-based dynamic linker interface and the SystemTap SDT probe code
on GDB more robust.  It does that by wrapping the calls to the probe
API with TRY...CATCH'es, so that any exception thrown will be caught
and handled properly.

The idea for this patch came from
<https://bugzilla.redhat.com/show_bug.cgi?id=1196181>, which is a bug
initially filed against Fedora GDB (but now under Fedora GLIBC).  This
bug happens on armhfp (although it could happen on other targets as
well), and is triggered because GCC generates a strange argument for
one of the probes used by GDB in the dynamic linker interface.  As can
be seen in the bug, this argument is "-4@.L1052".

I don't want to discuss the reasons for this argument to be there
(this discussion belongs to the bug, or to another thread), but GDB
could definitely do a better error handling here.  Currently, one sees
the following message when there is an error in the probes-based
dynamic linker interface:

  (gdb) run
  Starting program: /bin/inferior
  warning: Probes-based dynamic linker interface failed.
  Reverting to original interface.

  Cannot parse expression `.L976 4@r4'.
  (gdb)

Which means that one needs to explicitly issue a "continue" command to
make GDB continue running the inferior, even though this error is not
fatal and GDB will fallback to the old interface automatically.

This is where this patch helps: it makes GDB still print the necessary
warnings or error messages, but it *also* does not stop the inferior
unnecessarily.

I have tested this patch on the systems where this error happens, but
I could not come up with a way to create a testcase for it.
Nevertheless, it should be straightforward to see that this patch does
improve the current situation.

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

	* solib-svr4.c (solib_event_probe_action): Call
	get_probe_argument_count using TRY...CATCH.
	(svr4_handle_solib_event): Likewise, for evaluate_probe_argument.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Skip PLT for function pointer initialization
@ 2015-09-01 12:28 sergiodj+buildbot
  2015-09-01 15:06 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-09-01 12:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 04ebc307f9601168c165fb63aa39a676e45454b7 ***

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

Skip PLT for function pointer initialization

We use its PLT entry to initialize function pointer at run-time.  If
there is no other usage for the PLT entry, we can generate run-time
function pointer relocations in read-write section, which can be
resolved by dynamic linker, to initialize function pointers.  It avoids
the extra indirect branch overhead in PLT.

bfd/

	PR ld/18900
	* elf32-i386.c (elf_i386_link_hash_entry): Add
	func_pointer_refcount.
	(elf_i386_link_hash_newfunc): Clear func_pointer_refcount.
	(elf_i386_get_local_sym_hash): Likewise.
	(elf_i386_copy_indirect_symbol): Also copy
	func_pointer_refcount.
	(elf_i386_check_relocs): Increment func_pointer_refcount.
	(elf_i386_gc_sweep_hook): Decrement func_pointer_refcount.
	(elf_i386_allocate_dynrelocs): Don't create the PLT entry if
	there are only function pointer relocations which can be
	resolved at run-time.  Keep dynanamic relocations for run-time
	function pointer initialization.
	(elf_i386_relocate_section): Copy dynamic function pointer
	relocations.
	* elf64-x86-64.c (elf_x86_64_link_hash_entry): Add
	func_pointer_refcount.
	(elf_x86_64_link_hash_newfunc): Clear func_pointer_refcount.
	(elf_x86_64_get_local_sym_hash): Likewise.
	(elf_x86_64_copy_indirect_symbol): Also copy
	func_pointer_refcount.
	(elf_x86_64_check_relocs): Increment func_pointer_refcount.
	(elf_x86_64_gc_sweep_hook): Decrement func_pointer_refcount.
	(elf_x86_64_allocate_dynrelocs): Don't create the PLT entry if
	there are only function pointer relocations which can be
	resolved at run-time.  Keep dynanamic relocations for run-time
	function pointer initialization.
	(elf_x86_64_relocate_section): Copy dynamic function pointer
	relocations.

ld/testsuite/

	PR ld/18900
	* ld-i386/i386.exp: Run tests for PR ld/18900.
	* ld-x86-64/x86-64.exp: Likewise.
	* ld-i386/pr18900.out: New file.
	* ld-i386/pr18900a.c: Likewise.
	* ld-i386/pr18900a.c: Likewise.
	* ld-i386/pr18900a.rd: Likewise.
	* ld-i386/pr18900b.c: Likewise.
	* ld-i386/pr18900b.rd: Likewise.
	* ld-i386/pr18900c.c: Likewise.
	* ld-x86-64/pr18900.out: Likewise.
	* ld-x86-64/pr18900a.c: Likewise.
	* ld-x86-64/pr18900a.rd: Likewise.
	* ld-x86-64/pr18900b.c: Likewise.
	* ld-x86-64/pr18900b.rd: Likewise.
	* ld-x86-64/pr18900c.c: Likewise.
	* ld-x86-64/mpx3.dd: Updated.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] NDS32 build fixes
@ 2015-08-31  5:16 sergiodj+buildbot
  2015-08-31 11:01 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-08-31  5:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6cae483a9dc8d07c2743067d32026650b7eb37a9 ***

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

NDS32 build fixes

	* elf32-nds32.c (nds32_convert_32_to_16_alu1): Warning fix.
	(find_relocs_at_address_addr): Make "reloc_type" an enum.
	(nds32_elf_relax_delete_blanks): Warning fix.
	(nds32_elf_relax_loadstore): Correct loop bound.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Make asection->id and asection->index unsigned
@ 2015-08-31  4:32 sergiodj+buildbot
  2015-08-31  6:47 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-08-31  4:32 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7292b3ac749b5d10e527f57f8caf27113b55e3cb ***

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

Make asection->id and asection->index unsigned

These int vars are really unsigned, so make them so.

	* section.c (struct bfd_section): Make "id" and "index" unsigned.
	* coff-rs6000.c (_bfd_xcoff_sizeof_headers): Adjust local var to suit.
	* elf.c (elf_map_symbols): Likewise.
	* elf64-ppc.c (sym_exists_at): Make "id" param unsigned.
	(struct ppc_link_hash_table): Make "top_id" and "top_index" unsigned.
	(ppc64_elf_setup_section_lists): Ditto for local vars.
	* elf32-arm.c: Similarly to elf64-ppc.c.
	* elf32-avr.c: Likewise.
	* elf32-hppa.c: Likewise.
	* elf32-m68hc1x.c: Likewise.
	* elf32-metag.c: Likewise.
	* elf32-nios2.c: Likewise.
	* elfnn-aarch64.c: Likewise.
	* simple.c (struct saved_offsets): Make "section_count" unsigned.
	* bfd-in2.h: Regenerate.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
[parent not found: <a40805d4a73532dffc61e33f913e62b93214c998@gdb-build>]
* [binutils-gdb] [Cell/B.E.] Make parse_spufs_run more robust
@ 2015-08-27 18:07 sergiodj+buildbot
  2015-08-29 23:30 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-08-27 18:07 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 791bb1f4a6310cd7f894e370607dfc05c9cb0727 ***

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

[Cell/B.E.] Make parse_spufs_run more robust

With recent changes to inferior handling, parse_spufs_run needs to be
more careful in assumptions it makes.  In particular, this patch:

- Bails out early if the current inferior has not yet been registered
  (e.g. during fork procession) to avoid assertion failures in register
  cache code.

- Sets inferior_ptid to the current ptid while calling target_read_memory
  to make sure the correct process is accessed if parse_spufs_run is
  called early when inferior_ptid has not yet been switched by the caller.

ChangeLog:

	* spu-multiarch.c (parse_spufs_run): Bail out if inferior is not
	registered yet.  Set inferior_ptid while calling target_read_memory.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Report UNRESOLVED on failures while detecting Cell/B.E.
@ 2015-08-27 17:43 sergiodj+buildbot
  2015-08-29 17:18 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-08-27 17:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4e83a1e776c0acdaca9e69be9576db9efcd5f511 ***

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

Report UNRESOLVED on failures while detecting Cell/B.E.

The gdb.cell testcases use the predicate skip_cell_tests defined in
lib/cell.exp to determine whether Cell/B.E. test cases ought to be
run. This tests verifies that we have a toolchain that supports
generating combined Cell/B.E. binaries, and that the target machine
actually is a Cell/B.E.

In order to do so, a small test program is built and run (under the
debugger).  Any failure is taken as a sign that we don't have a
Cell/B.E. machine and the tests are to be skipped.

This has the unfortunate effect that a serious bug in GDB that causes
internal compiler errors even on the trivial test program does not
lead to any failures in the testsuite, since now all gdb.cell test
are simply skipped.

This patch changes skip_cell_tests to at least report UNRESOLVED
in cases where execution of the test program fails in unexpected
ways.

testsuite/ChangeLog:

	* lib/cell.exp (skip_cell_tests): Report UNRESOLVED on unexpected
	failures to run the test program under GDB.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Document non-8-bits addressable memory support in NEWS
@ 2015-08-27 13:41 sergiodj+buildbot
  2015-08-29 12:25 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-08-27 13:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fd2ae5d6a3a5c4007be45f9b2f325955ac316f36 ***

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

Document non-8-bits addressable memory support in NEWS

I think it would be a good idea to document that gdb now has (basic)
support to read/write memory on architectures with non-8-bits memory.
Hopefully somebody will see it and say "Hey!  We can now (more easily)
port GDB to our strange DSP that has 32-bits-addressable memory!" and do
it.

gdb/ChangeLog:

	* NEWS: Document support for non-8-bits addressable memory.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Don't sort ld -r output relocs on alpha
@ 2015-08-27  1:37 sergiodj+buildbot
  2015-08-28 14:29 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-08-27  1:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6fc5bb5718b72250cffb9c09110515971f72e116 ***

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

Don't sort ld -r output relocs on alpha

LITERAL/LITUSE relocs must be kept together.

	* elf64-alpha.c (elf64_alpha_sort_relocs_p): New function.
	(elf_backend_sort_relocs_p): Define.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Replace some xmalloc-family functions with XNEW-family ones
@ 2015-08-26 21:30 sergiodj+buildbot
  2015-08-28  7:39 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-08-26 21:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8d7493201cf01c9836403695f67f7e157341bfd5 ***

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

Replace some xmalloc-family functions with XNEW-family ones

This patch is part of the make-gdb-buildable-in-C++ effort.  The idea is
to change some calls to the xmalloc family of functions to calls to the
equivalents in the XNEW family.  This avoids adding an explicit cast, so
it keeps the code a bit more readable.  Some of them also map relatively
well to a C++ equivalent (XNEW (struct foo) -> new foo), so it will be
possible to do scripted replacements if needed.

I only changed calls that were obviously allocating memory for one or
multiple "objects".  Allocation of variable sizes (such as strings or
buffer handling) will be for later (and won't use XNEW).

  - xmalloc (sizeof (struct foo)) -> XNEW (struct foo)
  - xmalloc (num * sizeof (struct foo)) -> XNEWVEC (struct foo, num)
  - xcalloc (1, sizeof (struct foo)) -> XCNEW (struct foo)
  - xcalloc (num, sizeof (struct foo)) -> XCNEWVEC (struct foo, num)
  - xrealloc (p, num * sizeof (struct foo) -> XRESIZEVEC (struct foo, p, num)
  - obstack_alloc (ob, sizeof (struct foo)) -> XOBNEW (ob, struct foo)
  - obstack_alloc (ob, num * sizeof (struct foo)) -> XOBNEWVEC (ob, struct foo, num)
  - alloca (sizeof (struct foo)) -> XALLOCA (struct foo)
  - alloca (num * sizeof (struct foo)) -> XALLOCAVEC (struct foo, num)

Some instances of xmalloc followed by memset to zero the buffer were
replaced by XCNEW or XCNEWVEC.

I regtested on x86-64, Ubuntu 14.04, but the patch touches many
architecture-specific files.  For those I'll have to rely on the
buildbot or people complaining that I broke their gdb.

gdb/ChangeLog:

	* aarch64-linux-nat.c (aarch64_add_process): Likewise.
	* aarch64-tdep.c (aarch64_gdbarch_init): Likewise.
	* ada-exp.y (write_ambiguous_var): Likewise.
	* ada-lang.c (resolve_subexp): Likewise.
	(user_select_syms): Likewise.
	(assign_aggregate): Likewise.
	(ada_evaluate_subexp): Likewise.
	(cache_symbol): Likewise.
	* addrmap.c (allocate_key): Likewise.
	(addrmap_create_mutable): Likewise.
	* aix-thread.c (sync_threadlists): Likewise.
	* alpha-tdep.c (alpha_push_dummy_call): Likewise.
	(alpha_gdbarch_init): Likewise.
	* amd64-windows-tdep.c (amd64_windows_push_arguments): Likewise.
	* arm-linux-nat.c (arm_linux_add_process): Likewise.
	* arm-linux-tdep.c (arm_linux_displaced_step_copy_insn): Likewise.
	* arm-tdep.c (push_stack_item): Likewise.
	(arm_displaced_step_copy_insn): Likewise.
	(arm_gdbarch_init): Likewise.
	(_initialize_arm_tdep): Likewise.
	* avr-tdep.c (push_stack_item): Likewise.
	* ax-general.c (new_agent_expr): Likewise.
	* block.c (block_initialize_namespace): Likewise.
	* breakpoint.c (alloc_counted_command_line): Likewise.
	(update_dprintf_command_list): Likewise.
	(parse_breakpoint_sals): Likewise.
	(decode_static_tracepoint_spec): Likewise.
	(until_break_command): Likewise.
	(clear_command): Likewise.
	(update_global_location_list): Likewise.
	(get_breakpoint_objfile_data) Likewise.
	* btrace.c (ftrace_new_function): Likewise.
	(btrace_set_insn_history): Likewise.
	(btrace_set_call_history): Likewise.
	* buildsym.c (add_symbol_to_list): Likewise.
	(record_pending_block): Likewise.
	(start_subfile): Likewise.
	(start_buildsym_compunit): Likewise.
	(push_subfile): Likewise.
	(end_symtab_get_static_block): Likewise.
	(buildsym_init): Likewise.
	* cli/cli-cmds.c (source_command): Likewise.
	* cli/cli-decode.c (add_cmd): Likewise.
	* cli/cli-script.c (build_command_line): Likewise.
	(setup_user_args): Likewise.
	(realloc_body_list): Likewise.
	(process_next_line): Likewise.
	(copy_command_lines): Likewise.
	* cli/cli-setshow.c (do_set_command): Likewise.
	* coff-pe-read.c (read_pe_exported_syms): Likewise.
	* coffread.c (coff_locate_sections): Likewise.
	(coff_symtab_read): Likewise.
	(coff_read_struct_type): Likewise.
	* common/cleanups.c (make_my_cleanup2): Likewise.
	* common/common-exceptions.c (throw_it): Likewise.
	* common/filestuff.c (make_cleanup_close): Likewise.
	* common/format.c (parse_format_string): Likewise.
	* common/queue.h (DEFINE_QUEUE_P): Likewise.
	* compile/compile-object-load.c (munmap_list_add): Likewise.
	(compile_object_load): Likewise.
	* compile/compile-object-run.c (compile_object_run): Likewise.
	* compile/compile.c (append_args): Likewise.
	* corefile.c (specify_exec_file_hook): Likewise.
	* cp-support.c (make_symbol_overload_list): Likewise.
	* cris-tdep.c (push_stack_item): Likewise.
	(cris_gdbarch_init): Likewise.
	* ctf.c (ctf_trace_file_writer_new): Likewise.
	* dbxread.c (init_header_files): Likewise.
	(add_new_header_file): Likewise.
	(init_bincl_list): Likewise.
	(dbx_end_psymtab): Likewise.
	(start_psymtab): Likewise.
	(dbx_end_psymtab): Likewise.
	* dcache.c (dcache_init): Likewise.
	* dictionary.c (dict_create_hashed): Likewise.
	(dict_create_hashed_expandable): Likewise.
	(dict_create_linear): Likewise.
	(dict_create_linear_expandable): Likewise.
	* dtrace-probe.c (dtrace_process_dof_probe): Likewise.
	* dummy-frame.c (register_dummy_frame_dtor): Likewise.
	* dwarf2-frame-tailcall.c (cache_new_ref1): Likewise.
	* dwarf2-frame.c (dwarf2_build_frame_info): Likewise.
	(decode_frame_entry_1): Likewise.
	* dwarf2expr.c (new_dwarf_expr_context): Likewise.
	* dwarf2loc.c (dwarf2_compile_expr_to_ax): Likewise.
	* dwarf2read.c (dwarf2_has_info): Likewise.
	(create_signatured_type_table_from_index): Likewise.
	(dwarf2_read_index): Likewise.
	(dw2_get_file_names_reader): Likewise.
	(create_all_type_units): Likewise.
	(read_cutu_die_from_dwo): Likewise.
	(init_tu_and_read_dwo_dies): Likewise.
	(init_cutu_and_read_dies): Likewise.
	(create_all_comp_units): Likewise.
	(queue_comp_unit): Likewise.
	(inherit_abstract_dies): Likewise.
	(read_call_site_scope): Likewise.
	(dwarf2_add_field): Likewise.
	(dwarf2_add_typedef): Likewise.
	(dwarf2_add_member_fn): Likewise.
	(attr_to_dynamic_prop): Likewise.
	(abbrev_table_alloc_abbrev): Likewise.
	(abbrev_table_read_table): Likewise.
	(add_include_dir): Likewise.
	(add_file_name): Likewise.
	(dwarf_decode_line_header): Likewise.
	(dwarf2_const_value_attr): Likewise.
	(dwarf_alloc_block): Likewise.
	(parse_macro_definition): Likewise.
	(set_die_type): Likewise.
	(write_psymtabs_to_index): Likewise.
	(create_cus_from_index): Likewise.
	(dwarf2_create_include_psymtab): Likewise.
	(process_psymtab_comp_unit_reader): Likewise.
	(build_type_psymtab_dependencies): Likewise.
	(read_comp_units_from_section): Likewise.
	(compute_compunit_symtab_includes): Likewise.
	(create_dwo_unit_in_dwp_v1): Likewise.
	(create_dwo_unit_in_dwp_v2): Likewise.
	(read_func_scope): Likewise.
	(process_structure_scope): Likewise.
	(mark_common_block_symbol_computed): Likewise.
	(load_partial_dies): Likewise.
	(dwarf2_symbol_mark_computed): Likewise.
	* elfread.c (elf_symfile_segments): Likewise.
	(elf_read_minimal_symbols): Likewise.
	* environ.c (make_environ): Likewise.
	* eval.c (evaluate_subexp_standard): Likewise.
	* event-loop.c (create_file_handler): Likewise.
	(create_async_signal_handler): Likewise.
	(create_async_event_handler): Likewise.
	(create_timer): Likewise.
	* exec.c (build_section_table): Likewise.
	* fbsd-nat.c (fbsd_remember_child): Likewise.
	* fork-child.c (fork_inferior): Likewise.
	* frv-tdep.c (new_variant): Likewise.
	* gdbarch.sh (gdbarch_alloc): Likewise.
	(append_name): Likewise.
	* gdbtypes.c (rank_function): Likewise.
	(copy_type_recursive): Likewise.
	(add_dyn_prop): Likewise.
	* gnu-nat.c (make_proc): Likewise.
	(make_inf): Likewise.
	(gnu_write_inferior): Likewise.
	* gnu-v3-abi.c (build_gdb_vtable_type): Likewise.
	(build_std_type_info_type): Likewise.
	* guile/scm-param.c (compute_enum_list): Likewise.
	* guile/scm-utils.c (gdbscm_parse_function_args): Likewise.
	* guile/scm-value.c (gdbscm_value_call): Likewise.
	* h8300-tdep.c (h8300_gdbarch_init): Likewise.
	* hppa-tdep.c (hppa_init_objfile_priv_data): Likewise.
	(read_unwind_info): Likewise.
	* ia64-tdep.c (ia64_gdbarch_init): Likewise.
	* infcall.c (dummy_frame_context_saver_setup): Likewise.
	(call_function_by_hand_dummy): Likewise.
	* infcmd.c (step_once): Likewise.
	(finish_forward): Likewise.
	(attach_command): Likewise.
	(notice_new_inferior): Likewise.
	* inferior.c (add_inferior_silent): Likewise.
	* infrun.c (add_displaced_stepping_state): Likewise.
	(save_infcall_control_state): Likewise.
	(save_inferior_ptid): Likewise.
	(_initialize_infrun): Likewise.
	* jit.c (bfd_open_from_target_memory): Likewise.
	(jit_gdbarch_data_init): Likewise.
	* language.c (add_language): Likewise.
	* linespec.c (decode_line_2): Likewise.
	* linux-nat.c (add_to_pid_list): Likewise.
	(add_initial_lwp): Likewise.
	* linux-thread-db.c (add_thread_db_info): Likewise.
	(record_thread): Likewise.
	(info_auto_load_libthread_db): Likewise.
	* m32c-tdep.c (m32c_gdbarch_init): Likewise.
	* m68hc11-tdep.c (m68hc11_gdbarch_init): Likewise.
	* m68k-tdep.c (m68k_gdbarch_init): Likewise.
	* m88k-tdep.c (m88k_analyze_prologue): Likewise.
	* macrocmd.c (macro_define_command): Likewise.
	* macroexp.c (gather_arguments): Likewise.
	* macroscope.c (sal_macro_scope): Likewise.
	* macrotab.c (new_macro_table): Likewise.
	* mdebugread.c (push_parse_stack): Likewise.
	(parse_partial_symbols): Likewise.
	(parse_symbol): Likewise.
	(psymtab_to_symtab_1): Likewise.
	(new_block): Likewise.
	(new_psymtab): Likewise.
	(mdebug_build_psymtabs): Likewise.
	(add_pending): Likewise.
	(elfmdebug_build_psymtabs): Likewise.
	* mep-tdep.c (mep_gdbarch_init): Likewise.
	* mi/mi-main.c (mi_execute_command): Likewise.
	* mi/mi-parse.c (mi_parse_argv): Likewise.
	* minidebug.c (lzma_open): Likewise.
	* minsyms.c (terminate_minimal_symbol_table): Likewise.
	* mips-linux-nat.c (mips_linux_insert_watchpoint): Likewise.
	* mips-tdep.c (mips_gdbarch_init): Likewise.
	* mn10300-tdep.c (mn10300_gdbarch_init): Likewise.
	* msp430-tdep.c (msp430_gdbarch_init): Likewise.
	* mt-tdep.c (mt_registers_info): Likewise.
	* nat/aarch64-linux.c (aarch64_linux_new_thread): Likewise.
	* nat/linux-btrace.c (linux_enable_bts): Likewise.
	(linux_enable_pt): Likewise.
	* nat/linux-osdata.c (linux_xfer_osdata_processes): Likewise.
	(linux_xfer_osdata_processgroups): Likewise.
	* nios2-tdep.c (nios2_gdbarch_init): Likewise.
	* nto-procfs.c (procfs_meminfo): Likewise.
	* objc-lang.c (start_msglist): Likewise.
	(selectors_info): Likewise.
	(classes_info): Likewise.
	(find_methods): Likewise.
	* objfiles.c (allocate_objfile): Likewise.
	(update_section_map): Likewise.
	* osabi.c (gdbarch_register_osabi): Likewise.
	(gdbarch_register_osabi_sniffer): Likewise.
	* parse.c (start_arglist): Likewise.
	* ppc-linux-nat.c (hwdebug_find_thread_points_by_tid): Likewise.
	(hwdebug_insert_point): Likewise.
	* printcmd.c (display_command): Likewise.
	(ui_printf): Likewise.
	* procfs.c (create_procinfo): Likewise.
	(load_syscalls): Likewise.
	(proc_get_LDT_entry): Likewise.
	(proc_update_threads): Likewise.
	* prologue-value.c (make_pv_area): Likewise.
	(pv_area_store): Likewise.
	* psymtab.c (extend_psymbol_list): Likewise.
	(init_psymbol_list): Likewise.
	(allocate_psymtab): Likewise.
	* python/py-inferior.c (add_thread_object): Likewise.
	* python/py-param.c (compute_enum_values): Likewise.
	* python/py-value.c (valpy_call): Likewise.
	* python/py-varobj.c (py_varobj_iter_next): Likewise.
	* python/python.c (ensure_python_env): Likewise.
	* record-btrace.c (record_btrace_start_replaying): Likewise.
	* record-full.c (record_full_reg_alloc): Likewise.
	(record_full_mem_alloc): Likewise.
	(record_full_end_alloc): Likewise.
	(record_full_core_xfer_partial): Likewise.
	* regcache.c (get_thread_arch_aspace_regcache): Likewise.
	* remote-fileio.c (remote_fileio_init_fd_map): Likewise.
	* remote-notif.c (remote_notif_state_allocate): Likewise.
	* remote.c (demand_private_info): Likewise.
	(remote_notif_stop_alloc_reply): Likewise.
	(remote_enable_btrace): Likewise.
	* reverse.c (save_bookmark_command): Likewise.
	* rl78-tdep.c (rl78_gdbarch_init): Likewise.
	* rx-tdep.c (rx_gdbarch_init): Likewise.
	* s390-linux-nat.c (s390_insert_watchpoint): Likewise.
	* ser-go32.c (dos_get_tty_state): Likewise.
	(dos_copy_tty_state): Likewise.
	* ser-mingw.c (ser_windows_open): Likewise.
	(ser_console_wait_handle): Likewise.
	(ser_console_get_tty_state): Likewise.
	(make_pipe_state): Likewise.
	(net_windows_open): Likewise.
	* ser-unix.c (hardwire_get_tty_state): Likewise.
	(hardwire_copy_tty_state): Likewise.
	* solib-aix.c (solib_aix_new_lm_info): Likewise.
	* solib-dsbt.c (dsbt_current_sos): Likewise.
	(dsbt_relocate_main_executable): Likewise.
	* solib-frv.c (frv_current_sos): Likewise.
	(frv_relocate_main_executable): Likewise.
	* solib-spu.c (spu_bfd_fopen): Likewise.
	* solib-svr4.c (lm_info_read): Likewise.
	(svr4_copy_library_list): Likewise.
	(svr4_default_sos): Likewise.
	* source.c (find_source_lines): Likewise.
	(line_info): Likewise.
	(add_substitute_path_rule): Likewise.
	* spu-linux-nat.c (spu_bfd_open): Likewise.
	* spu-tdep.c (info_spu_dma_cmdlist): Likewise.
	* stabsread.c (dbx_lookup_type): Likewise.
	(read_type): Likewise.
	(read_member_functions): Likewise.
	(read_struct_fields): Likewise.
	(read_baseclasses): Likewise.
	(read_args): Likewise.
	(_initialize_stabsread): Likewise.
	* stack.c (func_command): Likewise.
	* stap-probe.c (handle_stap_probe): Likewise.
	* symfile.c (addrs_section_sort): Likewise.
	(addr_info_make_relative): Likewise.
	(load_section_callback): Likewise.
	(add_symbol_file_command): Likewise.
	(init_filename_language_table): Likewise.
	* symtab.c (create_filename_seen_cache): Likewise.
	(sort_search_symbols_remove_dups): Likewise.
	(search_symbols): Likewise.
	* target.c (make_cleanup_restore_target_terminal): Likewise.
	* thread.c (new_thread): Likewise.
	(enable_thread_stack_temporaries): Likewise.
	(make_cleanup_restore_current_thread): Likewise.
	(thread_apply_all_command): Likewise.
	* tic6x-tdep.c (tic6x_gdbarch_init): Likewise.
	* top.c (gdb_readline_wrapper): Likewise.
	* tracefile-tfile.c (tfile_trace_file_writer_new): Likewise.
	* tracepoint.c (trace_find_line_command): Likewise.
	(all_tracepoint_actions_and_cleanup): Likewise.
	(make_cleanup_restore_current_traceframe): Likewise.
	(get_uploaded_tp): Likewise.
	(get_uploaded_tsv): Likewise.
	* tui/tui-data.c (tui_alloc_generic_win_info): Likewise.
	(tui_alloc_win_info): Likewise.
	(tui_alloc_content): Likewise.
	(tui_add_content_elements): Likewise.
	* tui/tui-disasm.c (tui_find_disassembly_address): Likewise.
	(tui_set_disassem_content): Likewise.
	* ui-file.c (ui_file_new): Likewise.
	(stdio_file_new): Likewise.
	(tee_file_new): Likewise.
	* utils.c (make_cleanup_restore_integer): Likewise.
	(add_internal_problem_command): Likewise.
	* v850-tdep.c (v850_gdbarch_init): Likewise.
	* valops.c (find_oload_champ): Likewise.
	* value.c (allocate_value_lazy): Likewise.
	(record_latest_value): Likewise.
	(create_internalvar): Likewise.
	* varobj.c (install_variable): Likewise.
	(new_variable): Likewise.
	(new_root_variable): Likewise.
	(cppush): Likewise.
	(_initialize_varobj): Likewise.
	* windows-nat.c (windows_make_so): Likewise.
	* x86-nat.c (x86_add_process): Likewise.
	* xcoffread.c (arrange_linetable): Likewise.
	(allocate_include_entry): Likewise.
	(process_linenos): Likewise.
	(SYMBOL_DUP): Likewise.
	(xcoff_start_psymtab): Likewise.
	(xcoff_end_psymtab): Likewise.
	* xml-support.c (gdb_xml_parse_attr_ulongest): Likewise.
	* xtensa-tdep.c (xtensa_register_type): Likewise.
	* gdbarch.c: Regenerate.
	* gdbarch.h: Regenerate.

gdb/gdbserver/ChangeLog:

	* ax.c (gdb_parse_agent_expr): Likewise.
	(compile_bytecodes): Likewise.
	* dll.c (loaded_dll): Likewise.
	* event-loop.c (append_callback_event): Likewise.
	(create_file_handler): Likewise.
	(create_file_event): Likewise.
	* hostio.c (handle_open): Likewise.
	* inferiors.c (add_thread): Likewise.
	(add_process): Likewise.
	* linux-aarch64-low.c (aarch64_linux_new_process): Likewise.
	* linux-arm-low.c (arm_new_process): Likewise.
	(arm_new_thread): Likewise.
	* linux-low.c (add_to_pid_list): Likewise.
	(linux_add_process): Likewise.
	(handle_extended_wait): Likewise.
	(add_lwp): Likewise.
	(enqueue_one_deferred_signal): Likewise.
	(enqueue_pending_signal): Likewise.
	(linux_resume_one_lwp_throw): Likewise.
	(linux_resume_one_thread): Likewise.
	(linux_read_memory): Likewise.
	(linux_write_memory): Likewise.
	* linux-mips-low.c (mips_linux_new_process): Likewise.
	(mips_linux_new_thread): Likewise.
	(mips_add_watchpoint): Likewise.
	* linux-x86-low.c (initialize_low_arch): Likewise.
	* lynx-low.c (lynx_add_process): Likewise.
	* mem-break.c (set_raw_breakpoint_at): Likewise.
	(set_breakpoint): Likewise.
	(add_condition_to_breakpoint): Likewise.
	(add_commands_to_breakpoint): Likewise.
	(clone_agent_expr): Likewise.
	(clone_one_breakpoint): Likewise.
	* regcache.c (new_register_cache): Likewise.
	* remote-utils.c (look_up_one_symbol): Likewise.
	* server.c (queue_stop_reply): Likewise.
	(start_inferior): Likewise.
	(queue_stop_reply_callback): Likewise.
	(handle_target_event): Likewise.
	* spu-low.c (fetch_ppc_memory): Likewise.
	(store_ppc_memory): Likewise.
	* target.c (set_target_ops): Likewise.
	* thread-db.c (thread_db_load_search): Likewise.
	(try_thread_db_load_1): Likewise.
	* tracepoint.c (add_tracepoint): Likewise.
	(add_tracepoint_action): Likewise.
	(create_trace_state_variable): Likewise.
	(cmd_qtdpsrc): Likewise.
	(cmd_qtro): Likewise.
	(add_while_stepping_state): Likewise.
	* win32-low.c (child_add_thread): Likewise.
	(get_image_name): Likewise.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Fix native follow-exec-mode "new"
@ 2015-08-26 21:28 sergiodj+buildbot
  2015-08-28  6:50 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-08-26 21:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 17d8546e6067d0133f19275d1ccc25cf93cfc7bc ***

Author: Don Breazeal <donb@codesourcery.com>
Branch: master
Commit: 17d8546e6067d0133f19275d1ccc25cf93cfc7bc

Fix native follow-exec-mode "new"

This patch fixes a segmentation fault in native GDB when
handling an exec event with follow-exec-mode set to "new".

The stack trace from the segfault was this:

 0  0x0000000000669594 in gdbarch_data (gdbarch=0x0, data=0x20da7a0)
    at /scratch/dbreazea/sandbox/exec-nat/binutils-gdb/gdb/gdbarch.c:4847
 1  0x00000000004d430e in get_remote_arch_state ()
    at /scratch/dbreazea/sandbox/exec-nat/binutils-gdb/gdb/remote.c:603
 2  0x00000000004d431e in get_remote_state ()
    at /scratch/dbreazea/sandbox/exec-nat/binutils-gdb/gdb/remote.c:616
 3  0x00000000004dda8b in discard_pending_stop_replies (inf=0x217c710)
    at /scratch/dbreazea/sandbox/exec-nat/binutils-gdb/gdb/remote.c:5775
 4  0x00000000006a5928 in observer_inferior_exit_notification_stub (
    data=0x4dda7a <discard_pending_stop_replies>, args_data=0x7fff12c258f0)
    at ./observer.inc:1137
 5  0x00000000006a419a in generic_observer_notify (subject=0x21dfbe0,
    args=0x7fff12c258f0)
    at /scratch/dbreazea/sandbox/exec-nat/binutils-gdb/gdb/observer.c:167
 6  0x00000000006a59ba in observer_notify_inferior_exit (inf=0x217c710)
    at ./observer.inc:1162
 7  0x00000000007981d5 in exit_inferior_1 (inftoex=0x217c710, silent=1)
    at /scratch/dbreazea/sandbox/exec-nat/binutils-gdb/gdb/inferior.c:244
 8  0x00000000007982f2 in exit_inferior_num_silent (num=1)
    at /scratch/dbreazea/sandbox/exec-nat/binutils-gdb/gdb/inferior.c:286
 9  0x000000000062f93d in follow_exec (ptid=...,
    execd_pathname=0x7fff12c259a0 "/scratch/dbreazea/sandbox/exec-nat/build/gdb/testsuite/gdb.base/execd-prog")
    at /scratch/dbreazea/sandbox/exec-nat/binutils-gdb/gdb/infrun.c:1195

In follow_exec we were creating a new inferior for the execd program,
as required by the exec mode, but we were doing it before calling
exit_inferior_num_silent on the original inferior.  So on entry to
exit_inferior_num_silent we had two inferiors with the same ptid.

In the calls made by exit_inferior_num_silent, the current inferior
is temporarily saved and replaced in order to make use of functions
that only operate on the current inferior (for example, in
do_all_continuations, called while deleting the threads of the original
inferior).  When we restored the original inferior, we just took the
first inferior that matched the ptid of the original and got the new
(wrong) one.  It hadn't been initialized yet and had no gdbarch
pointer, and GDB segfaulted.

The fix for that is to call exit_inferior_num_silent before adding the new
inferior, so that we never have two inferiors with the same ptid.  Then
exit_inferior_num_silent uses the original inferior as the current inferior
throughout, and can find a valid gdbarch pointer.

Once we have finished with the exit of the old inferior and added the
new one, we need to create a new thread for the new inferior.  In the
function that called follow_exec, handle_inferior_event_1,
ecs->event_thread now points to the thread that was deleted with the
exit of the original inferior.  To remedy this we create the new thread,
and once we return from follow_exec we reset ecs->event_thread.

Note that we are guaranteed that we can reset ecs->event_thread
safely using inferior_thread because we have set the current
inferior in follow_exec, and inferior_ptid was set by the call
to context_switch at the beginning of exec event handling.

gdb/ChangeLog:

	* infrun.c (follow_exec): Re-order operations for
	handling follow-exec-mode "new".
	(handle_inferior_event_1): Assign ecs->event_thread
	to the current thread.
	* remote.c (get_remote_arch_state): Add an assertion.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] New test for follow-exec-mode
@ 2015-08-26 21:20 sergiodj+buildbot
  2015-08-28  4:27 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-08-26 21:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8d37573b4356a38d091b0f18b69f91797a7cef26 ***

Author: Don Breazeal <donb@codesourcery.com>
Branch: master
Commit: 8d37573b4356a38d091b0f18b69f91797a7cef26

New test for follow-exec-mode

This patch implements a new GDB test for follow-exec-mode.  Although
there is a GDB test for debugging across an exec, there is no test for
follow-exec-mode.  This test is derived from gdb.base/foll-exec.exp,
and re-uses execd-prog.c as the program to exec.

The following behavior is tested:

follow-exec-mode == "same"
 - 'next' over the exec, check for one inferior
 - 'continue' past the exec to a breakpoint, check for one inferior
 - after the exec, use a 'run' command to run the current binary
follow-exec-mode == "new"
 - 'next' over the exec, check for two inferiors
 - 'continue' past the exec to a breakpoint, check for two inferiors
 - after the exec, use a 'run' command to run the current binary
 - after the exec, use the 'inferior' command to switch inferiors,
   then use a 'run' command to run the current binary

Note that single-step breakpoints do not survive across an exec.
There has to be a breakpoint in the execed program in order for
it to stop right after the exec.

gdb/testsuite/ChangeLog:

	* gdb.base/foll-exec-2.c: New test program.
	* gdb.base/foll-exec-2.exp: New test.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Use stable sort for ld -r relocs
@ 2015-08-26 14:22 sergiodj+buildbot
  2015-08-28  0:20 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-08-26 14:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0e28778672160ee57d12fcc4f0e631122088fe69 ***

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

Use stable sort for ld -r relocs

A number of targets emit multiple relocs at a given r_offset, and
depend on those relocs staying in their original order.

	PR 18867
	* elflink.c (cmp_ext32l_r_offset, cmp_ext32b_r_offset): Delete.
	(cmp_ext64l_r_offset, cmp_ext64b_r_offset): Delete.
	(ext32l_r_offset, ext32b_r_offset, ext64l_r_offset, ext64b_r_offset):
	New functions.
	(elf_link_adjust_relocs): Use an insertion sort to sort relocs.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Replace assertions with warning messages about ELF binaries containing multiple symbol tables.
@ 2015-08-25 17:18 sergiodj+buildbot
  2015-08-27 19:51 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-08-25 17:18 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 16ad13eca4a18139cd1dec214ec83fdc7c47ffda ***

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

Replace assertions with warning messages about ELF binaries containing multiple symbol tables.

	PR binutils/18854
	* elf.c (bfd_section_from_shdr): Replace assertions with warnings
	about multiple symbol tables.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Move aarch64_linux_new_thread to nat/aarch64-linux.c
@ 2015-08-25 16:03 sergiodj+buildbot
  2015-08-26 23:41 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-08-25 16:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ed8b7b421c98533b9b08995edd7363328b55921e ***

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

Move aarch64_linux_new_thread to nat/aarch64-linux.c

This patch moves aarch64_linux_new_thread in GDB and GDBserver to
nat/aarch64-linux.c.

gdb:

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

	* aarch64-linux-nat.c (aarch64_linux_new_thread): Move it to ...
	* nat/aarch64-linux.c (aarch64_linux_new_thread): ... here.
	* nat/aarch64-linux.h (aarch64_linux_new_thread): Declare.

gdb/gdbserver:

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

	* linux-aarch64-low.c (aarch64_linux_new_thread): Remove.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Print tid in debug output of debug_reg_change_callback
@ 2015-08-25 13:56 sergiodj+buildbot
  2015-08-27  5:52 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-08-25 13:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT dfe7f77c4aae3376c175d8af4d477124c8817427 ***

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

Print tid in debug output of debug_reg_change_callback

In debug_reg_change_callback, we change debug registers of each LWP.
It makes more sense to print LWP's pid rather than group leader's pid.

gdb:

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

	* nat/aarch64-linux-hw-point.c (debug_reg_change_callback):
	Rename local variable pid to tid, and get lwpid of lwp.  Update
	debug output.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Use debug_printf in debug_reg_change_callback
@ 2015-08-25 13:03 sergiodj+buildbot
  2015-08-26  7:37 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-08-25 13:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 32a271eeaf1b1be1367b6ea181a0f39a3da71d45 ***

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

Use debug_printf in debug_reg_change_callback

gdb:

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

	* aarch64-linux-nat.c (debug_reg_change_callback): Use
	debug_printf.

gdb/gdbserver:

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

	* linux-aarch64-low.c (debug_reg_change_callback): Use
	debug_printf.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Move aarch64_linux_prepare_to_resume to nat/aarch64-linux.c
@ 2015-08-25 12:13 sergiodj+buildbot
  2015-08-26 21:35 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-08-25 12:13 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT db3cb7cb3e51e5eb834412adbf90e81bb76846c6 ***

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

Move aarch64_linux_prepare_to_resume to nat/aarch64-linux.c

gdb:

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

	* Makefile.in (aarch64-liunx.o): New rule.
	(HFILES_NO_SRCDIR): Add aarch64-linux.h.
	* config/aarch64/linux.mh (NAT_FILE): Add aarch64-linux.o.
	* aarch64-linux-nat.c: Include nat/aarch64-linux.h.
	* aarch64-linux-nat.c (aarch64_get_debug_reg_state): Make it
	extern.
	(aarch64_linux_prepare_to_resume): Move it nat/aarch64-linux.c.
	* nat/aarch64-linux-hw-point.h (aarch64_debug_reg_state): Declare
	* nat/aarch64-linux.c: New file.
	* nat/aarch64-linux.h: New file.

gdb/gdbserver:

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

	* Makefile.in (aarch64-linux.o): New rule.
	* configure.srv (aarch64*-*-linux*): Append aarch64-linux.o to
	srv_tgtobj.
	* linux-aarch64-low.c: Include nat/aarch64-linux.h.
	(aarch64_init_debug_reg_state): Make it extern.
	(aarch64_linux_prepare_to_resume): Remove.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Make aarch64_linux_prepare_to_resume the same on GDB and GDBserver
@ 2015-08-25 12:05 sergiodj+buildbot
  2015-08-26 19:09 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-08-25 12:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f6011a1c84b1bd616617bfde84dca63f250c950d ***

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

Make aarch64_linux_prepare_to_resume the same on GDB and GDBserver

gdb:

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

	* aarch64-linux-nat.c (aarch64_linux_prepare_to_resume): Use
	lwp_arch_private_info and ptid_of_lwp.

gdb/gdbserver:

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

	* linux-aarch64-low.c (aarch64_linux_prepare_to_resume): Use
	lwp_arch_private_info and ptid_of_lwp.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Make debug_reg_change_callback the same on GDB and GDBserver
@ 2015-08-25 11:43 sergiodj+buildbot
  2015-08-26 12:19 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-08-25 11:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 75e1f0f7a0992835415e9bb924ec21a9aac6d5a1 ***

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

Make debug_reg_change_callback the same on GDB and GDBserver

This patch makes function debug_reg_change_callback in GDB and GDBserver
look the same, so that the following patch can move them to
nat/aarch64-linux-hw-point.c.

gdb:

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

	* aarch64-linux-nat.c (debug_reg_change_callback): Use
	ptid_of_lwp to get ptid of lwp.

gdb/gdbserver:

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

	* linux-aarch64-low.c (debug_reg_change_callback): Use
	ptid_of_lwp to get ptid of lwp.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Re-indent the code
@ 2015-08-25 11:27 sergiodj+buildbot
  2015-08-25 20:35 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-08-25 11:27 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8ee525679d030cd2c35eaee3b8d4ac545c5dc8ee ***

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

Re-indent the code

gdb/gdbserver:

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

	* linux-aarch64-low.c (debug_reg_change_callback): Re-indent
	the code.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Remove some comments in debug_reg_change_callback
@ 2015-08-25 11:05 sergiodj+buildbot
  2015-08-25 22:50 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-08-25 11:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 31a43dd5e1cfb8bb387885b3f641d6d2c04ac5dd ***

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

Remove some comments in debug_reg_change_callback

gdb/gdbserver:

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

	* linux-aarch64-low.c (debug_reg_change_callback): Remove comments.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [gdbserver] Use iterate_over_lwps in aarch64_notify_debug_reg_change
@ 2015-08-25 10:50 sergiodj+buildbot
  2015-08-25 18:29 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-08-25 10:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ff3f0f45c5ff3505d041eba81a999b55c55f4530 ***

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

[gdbserver] Use iterate_over_lwps in aarch64_notify_debug_reg_change

This patch makes more bits on aarch64 watchpoint between GDB and GDBserver
look similar.

gdb/gdbserver:

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

	* linux-aarch64-low.c (aarch64_dr_update_callback_param) <pid>:
	Remove.
	(debug_reg_change_callback): Remove argument entry and add argument
	lwp.  Remove local variable thread.  Don't print thread id in the
	debugging output.  Don't check whether pid of thread equals to pid.
	(aarch64_notify_debug_reg_change): Don't set param.pid.  Call
	iterate_over_lwps instead find_inferior.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] gdbserver crashes when multiprocess extensions aren't supported
@ 2015-08-24 19:25 sergiodj+buildbot
  2015-08-25 15:54 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-08-24 19:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3d40fbb53b4478d94b6fa5abad0796cec5d5db49 ***

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

gdbserver crashes when multiprocess extensions aren't supported

Ref: https://sourceware.org/ml/gdb-patches/2015-08/msg00675.html

If multiprocess extensions are off (because specific gdbserver port
doesn't support them), then when gdbserver doesn't have a thread
selected yet, and GDB sends Hg packet to select one, gdbserver
crashes.  That's because extracting the desired thread id out of the
packet that GDB sent depends on the current thread to fill in the
missing process id ...  Fix this by getting the process id from the
first (and only) process in the processes list instead.

The GNU/Linux port doesn't trip on this because it always runs with
multiprocess extensions enabled.  To make it easier to catch such
regressions going forward, this commit also adds a new smoke test that
spawns gdbserver, connects to it and runs to main with the
multiprocess extensions force-disabled.

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

	* inferiors.c (get_first_process): New function.
	* inferiors.h (get_first_process): New declaration.
	* remote-utils.c (read_ptid): Default to the first process in the
	list, instead of to the current thread's process.

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

	* gdb.server/connect-without-multi-process.c: New file.
	* gdb.server/connect-without-multi-process.exp: New file.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Add "set remote multiprocess-extensions-packet" command
@ 2015-08-24 19:17 sergiodj+buildbot
  2015-08-25 13:48 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-08-24 19:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 73b8c1fda9f3759874a9a1a7e7402276da057153 ***

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

Add "set remote multiprocess-extensions-packet" command

Being able to force-disable the RSP multiprocess extensions is useful
for testing.

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

	* NEWS (New commands): Mention set/show remote
	multiprocess-extensions-packet.
	* remote.c (remote_query_supported): Only tell the server to use
	the multiprocess extensions if the user hasn't force-disabled them
	with "set remote multiprocess-extensions-packet off".

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

	* gdb.texinfo (Remote Configuration): Document the "set/show
	remote multiprocess-extensions-packet" commands.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Update gnulib to current upstream master
@ 2015-08-24 18:23 sergiodj+buildbot
  2015-08-25 11:37 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-08-24 18:23 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4a626d0a0f451c3288a461f64a9f8a49790d422b ***

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

Update gnulib to current upstream master

2015-08-24  Pedro Alves  <palves@redhat.com>

	* gnulib/update-gnulib.sh (GNULIB_COMMIT_SHA1): Set to
	1029a8112290f6eee9d7878a391c49db42c999bd.
	* gnulib/configure, gnulib/config.in, gnulib/aclocal.m4:
	Regenerate.
	* gnulib/import/Makefile.am: Update.
	* gnulib/import/Makefile.in: Update.
	* gnulib/import/alloca.in.h: Update.
	* gnulib/import/basename-lgpl.c: Update.
	* gnulib/import/canonicalize-lgpl.c: Update.
	* gnulib/import/config.charset: Update.
	* gnulib/import/dirent.in.h: Update.
	* gnulib/import/dirfd.c: Update.
	* gnulib/import/dirname-lgpl.c: Update.
	* gnulib/import/dirname.h: Update.
	* gnulib/import/dosname.h: Update.
	* gnulib/import/errno.in.h: Update.
	* gnulib/import/extra/snippet/arg-nonnull.h: Update.
	* gnulib/import/extra/snippet/c++defs.h: Update.
	* gnulib/import/extra/snippet/warn-on-use.h: Update.
	* gnulib/import/extra/update-copyright: Update.
	* gnulib/import/float+.h: Update.
	* gnulib/import/float.c: Update.
	* gnulib/import/float.in.h: Update.
	* gnulib/import/fnmatch.c: Update.
	* gnulib/import/fnmatch.in.h: Update.
	* gnulib/import/fnmatch_loop.c: Update.
	* gnulib/import/fpucw.h: Update.
	* gnulib/import/frexp.c: Update.
	* gnulib/import/frexpl.c: Update.
	* gnulib/import/gettimeofday.c: Update.
	* gnulib/import/inttypes.in.h: Update.
	* gnulib/import/isnan.c: Update.
	* gnulib/import/isnand-nolibm.h: Update.
	* gnulib/import/isnand.c: Update.
	* gnulib/import/isnanl-nolibm.h: Update.
	* gnulib/import/isnanl.c: Update.
	* gnulib/import/itold.c: Update.
	* gnulib/import/localcharset.c: Update.
	* gnulib/import/localcharset.h: Update.
	* gnulib/import/lstat.c: Update.
	* gnulib/import/m4/00gnulib.m4: Update.
	* gnulib/import/m4/absolute-header.m4: Update.
	* gnulib/import/m4/alloca.m4: Update.
	* gnulib/import/m4/canonicalize.m4: Update.
	* gnulib/import/m4/codeset.m4: Update.
	* gnulib/import/m4/configmake.m4: Update.
	* gnulib/import/m4/dirent_h.m4: Update.
	* gnulib/import/m4/dirfd.m4: Update.
	* gnulib/import/m4/dirname.m4: Update.
	* gnulib/import/m4/double-slash-root.m4: Update.
	* gnulib/import/m4/eealloc.m4: Update.
	* gnulib/import/m4/errno_h.m4: Update.
	* gnulib/import/m4/exponentd.m4: Update.
	* gnulib/import/m4/exponentl.m4: Update.
	* gnulib/import/m4/extensions.m4: Update.
	* gnulib/import/m4/extern-inline.m4: Update.
	* gnulib/import/m4/fcntl-o.m4: Update.
	* gnulib/import/m4/float_h.m4: Update.
	* gnulib/import/m4/fnmatch.m4: Update.
	* gnulib/import/m4/fpieee.m4: Update.
	* gnulib/import/m4/frexp.m4: Update.
	* gnulib/import/m4/frexpl.m4: Update.
	* gnulib/import/m4/gettimeofday.m4: Update.
	* gnulib/import/m4/glibc21.m4: Update.
	* gnulib/import/m4/gnulib-cache.m4: Update.
	* gnulib/import/m4/gnulib-common.m4: Update.
	* gnulib/import/m4/gnulib-comp.m4: Update.
	* gnulib/import/m4/gnulib-tool.m4: Update.
	* gnulib/import/m4/include_next.m4: Update.
	* gnulib/import/m4/inttypes-pri.m4: Update.
	* gnulib/import/m4/inttypes.m4: Update.
	* gnulib/import/m4/isnand.m4: Update.
	* gnulib/import/m4/isnanl.m4: Update.
	* gnulib/import/m4/largefile.m4: Update.
	* gnulib/import/m4/localcharset.m4: Update.
	* gnulib/import/m4/locale-fr.m4: Update.
	* gnulib/import/m4/locale-ja.m4: Update.
	* gnulib/import/m4/locale-zh.m4: Update.
	* gnulib/import/m4/longlong.m4: Update.
	* gnulib/import/m4/lstat.m4: Update.
	* gnulib/import/m4/malloc.m4: Update.
	* gnulib/import/m4/malloca.m4: Update.
	* gnulib/import/m4/math_h.m4: Update.
	* gnulib/import/m4/mbrtowc.m4: Update.
	* gnulib/import/m4/mbsinit.m4: Update.
	* gnulib/import/m4/mbsrtowcs.m4: Update.
	* gnulib/import/m4/mbstate_t.m4: Update.
	* gnulib/import/m4/memchr.m4: Update.
	* gnulib/import/m4/memmem.m4: Update.
	* gnulib/import/m4/mmap-anon.m4: Update.
	* gnulib/import/m4/multiarch.m4: Update.
	* gnulib/import/m4/nocrash.m4: Update.
	* gnulib/import/m4/off_t.m4: Update.
	* gnulib/import/m4/pathmax.m4: Update.
	* gnulib/import/m4/readlink.m4: Update.
	* gnulib/import/m4/rename.m4: Update.
	* gnulib/import/m4/rmdir.m4: Update.
	* gnulib/import/m4/ssize_t.m4: Update.
	* gnulib/import/m4/stat.m4: Update.
	* gnulib/import/m4/stdbool.m4: Update.
	* gnulib/import/m4/stddef_h.m4: Update.
	* gnulib/import/m4/stdint.m4: Update.
	* gnulib/import/m4/stdio_h.m4: Update.
	* gnulib/import/m4/stdlib_h.m4: Update.
	* gnulib/import/m4/string_h.m4: Update.
	* gnulib/import/m4/strstr.m4: Update.
	* gnulib/import/m4/strtok_r.m4: Update.
	* gnulib/import/m4/sys_socket_h.m4: Update.
	* gnulib/import/m4/sys_stat_h.m4: Update.
	* gnulib/import/m4/sys_time_h.m4: Update.
	* gnulib/import/m4/sys_types_h.m4: Update.
	* gnulib/import/m4/time_h.m4: Update.
	* gnulib/import/m4/unistd_h.m4: Update.
	* gnulib/import/m4/warn-on-use.m4: Update.
	* gnulib/import/m4/wchar_h.m4: Update.
	* gnulib/import/m4/wchar_t.m4: Update.
	* gnulib/import/m4/wctype_h.m4: Update.
	* gnulib/import/m4/wint_t.m4: Update.
	* gnulib/import/malloc.c: Update.
	* gnulib/import/malloca.c: Update.
	* gnulib/import/malloca.h: Update.
	* gnulib/import/math.in.h: Update.
	* gnulib/import/mbrtowc.c: Update.
	* gnulib/import/mbsinit.c: Update.
	* gnulib/import/mbsrtowcs-impl.h: Update.
	* gnulib/import/mbsrtowcs-state.c: Update.
	* gnulib/import/mbsrtowcs.c: Update.
	* gnulib/import/memchr.c: Update.
	* gnulib/import/memmem.c: Update.
	* gnulib/import/pathmax.h: Update.
	* gnulib/import/readlink.c: Update.
	* gnulib/import/ref-add.sin: Update.
	* gnulib/import/ref-del.sin: Update.
	* gnulib/import/rename.c: Update.
	* gnulib/import/rmdir.c: Update.
	* gnulib/import/same-inode.h: Update.
	* gnulib/import/stat.c: Update.
	* gnulib/import/stdbool.in.h: Update.
	* gnulib/import/stddef.in.h: Update.
	* gnulib/import/stdint.in.h: Update.
	* gnulib/import/stdio.c: Update.
	* gnulib/import/stdio.in.h: Update.
	* gnulib/import/stdlib.in.h: Update.
	* gnulib/import/str-two-way.h: Update.
	* gnulib/import/streq.h: Update.
	* gnulib/import/string.in.h: Update.
	* gnulib/import/stripslash.c: Update.
	* gnulib/import/strnlen1.c: Update.
	* gnulib/import/strnlen1.h: Update.
	* gnulib/import/strstr.c: Update.
	* gnulib/import/strtok_r.c: Update.
	* gnulib/import/sys_stat.in.h: Update.
	* gnulib/import/sys_time.in.h: Update.
	* gnulib/import/sys_types.in.h: Update.
	* gnulib/import/time.in.h: Update.
	* gnulib/import/unistd.in.h: Update.
	* gnulib/import/verify.h: Update.
	* gnulib/import/wchar.in.h: Update.
	* gnulib/import/wctype.in.h: Update.
	* gnulib/import/gettimeofday.c: New file.
	* gnulib/import/m4/absolute-header.m4: New file.
	* gnulib/import/m4/gettimeofday.m4: New file.
	* gnulib/import/m4/sys_socket_h.m4: New file.
	* gnulib/import/m4/sys_time_h.m4: New file.
	* gnulib/import/stdio.c: Delete file.
	* gnulib/import/sys_time.in.h: New file.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Missing parts of fixes for in-tree libiconv
@ 2015-08-24 10:41 sergiodj+buildbot
  2015-08-24 12:55 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-08-24 10:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cfe101c6a8227b6b97ed2da85895db7d6083bfa6 ***

Author: Yaakov Selkowitz <yselkowi@redhat.com>
Branch: master
Commit: cfe101c6a8227b6b97ed2da85895db7d6083bfa6

Missing parts of fixes for in-tree libiconv

(Commit d23d1dff missed pushing the config/iconv.m4 change, and to
regenerate binutils' configure.)

Original description:

This is the second in a series of patches to make a build with an
in-tree GNU libiconv work as designed.

Currently GDB is the only toolchain component which actually uses an
in-tree libiconv.  This patch modifies the common AM_ICONV to use an
in-tree libiconv when present and not already provided by libc.
(GDB's workaround uses an in-tree libiconv even when libc provides
iconv(3); I'm not sure when or why that would be desirable.)

config/ChangeLog:
2015-08-24  Yaakov Selkowitz  <yselkowi@redhat.com>

	* iconv.m4 (AM_ICONV_LINK): Use in-tree libiconv when present.

binutils/ChangeLog:
2015-08-24  Yaakov Selkowitz  <yselkowi@redhat.com>

	* configure: Regenerate.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] tui: don't overwrite a secondary prompt that was given no input
@ 2015-08-21 20:38 sergiodj+buildbot
  2015-08-22 14:05 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-08-21 20:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 948578a989f8c666c9b0e92c9a50906724921f14 ***

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

tui: don't overwrite a secondary prompt that was given no input

This patch fixes the following bug in TUI:

  (gdb) break foo
  No symbol table is loaded.  Use the "file" command.
  Make breakpoint pending on future shared library load? (y or [n]) <ENTER>

By submitting an empty command line to a secondary prompt, the line
corresponding to the secondary prompt is undesirably cleared and
overwritten.  Outside of a secondary prompt, clearing the prompt line
after submitting an empty command line is intended behavior which
complements GDB's repeat-command shorthand.  But inside a secondary
prompt, this behavior is undesired since the shorthand is not applicable
in that case.  We should retain the secondary-prompt line even when it's
given no input.

This patch makes sure that a prompt that was given an empty command line
is cleared and overwritten only if it's not a secondary prompt.  To
acheive this, a new predicate is defined which informs us whether the
current input handler is a secondary prompt.

gdb/ChangeLog:

	* top.h (gdb_in_secondary_prompt_p): Declare.
	* top.c (gdb_secondary_prompt_depth): Define.
	(gdb_in_secondary_prompt_p): Define.
	(gdb_readline_wrapper_cleanup): Decrement
	gdb_secondary_prompt_depth.
	(gdb_readline_wrapper): Increment gdb_secondary_prompt_depth.
	* tui/tui-io.c (tui_getc): Don't clear the prompt line if we
	are in a secondary prompt.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Fix gdbserver crash exposed by gdb.threads/process-dies-while-handling-bp.exp
@ 2015-08-21 19:24 sergiodj+buildbot
  2015-08-22 10:37 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-08-21 19:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 465a859e0a991d3bfe8a9ee65a29a223c42e2ce7 ***

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

Fix gdbserver crash exposed by gdb.threads/process-dies-while-handling-bp.exp

Running that test in a loop, I found a gdbserver core dump with the
following back trace:

 Core was generated by `../gdbserver/gdbserver --once --multi :2346'.
 Program terminated with signal SIGSEGV, Segmentation fault.
 #0  0x0000000000406ab6 in inferior_regcache_data (inferior=0x0) at src/gdb/gdbserver/inferiors.c:236
 236       return inferior->regcache_data;
 (gdb) up
 #1  0x0000000000406d7f in get_thread_regcache (thread=0x0, fetch=1) at src/gdb/gdbserver/regcache.c:31
 31        regcache = (struct regcache *) inferior_regcache_data (thread);
 (gdb) bt
 #0  0x0000000000406ab6 in inferior_regcache_data (inferior=0x0) at src/gdb/gdbserver/inferiors.c:236
 #1  0x0000000000406d7f in get_thread_regcache (thread=0x0, fetch=1) at src/gdb/gdbserver/regcache.c:31
 #2  0x0000000000409271 in prepare_resume_reply (buf=0x20dd593 "", ptid=..., status=0x20edce0) at src/gdb/gdbserver/remote-utils.c:1147
 #3  0x000000000040ab0a in vstop_notif_reply (event=0x20edcc0, own_buf=0x20dd590 "T05") at src/gdb/gdbserver/server.c:183
 #4  0x0000000000426b38 in notif_write_event (notif=0x66e6c0 <notif_stop>, own_buf=0x20dd590 "T05") at src/gdb/gdbserver/notif.c:69
 #5  0x0000000000426c55 in handle_notif_ack (own_buf=0x20dd590 "T05", packet_len=8) at src/gdb/gdbserver/notif.c:113
 #6  0x000000000041118f in handle_v_requests (own_buf=0x20dd590 "T05", packet_len=8, new_packet_len=0x7fff742c77b8)
     at src/gdb/gdbserver/server.c:2862
 #7  0x0000000000413850 in process_serial_event () at src/gdb/gdbserver/server.c:4148
 #8  0x0000000000413945 in handle_serial_event (err=0, client_data=0x0) at src/gdb/gdbserver/server.c:4196
 #9  0x000000000041a1ef in handle_file_event (event_file_desc=5) at src/gdb/gdbserver/event-loop.c:429
 #10 0x00000000004199b6 in process_event () at src/gdb/gdbserver/event-loop.c:184
 #11 0x000000000041a735 in start_event_loop () at src/gdb/gdbserver/event-loop.c:547
 #12 0x00000000004123d2 in captured_main (argc=4, argv=0x7fff742c7ac8) at src/gdb/gdbserver/server.c:3562
 #13 0x000000000041252e in main (argc=4, argv=0x7fff742c7ac8) at src/gdb/gdbserver/server.c:3631

Clearly this means that a thread pushed a stop reply in the event
queue, and then before GDB confused the event, the whole process died,
along with its thread.  But the pending thread event was left
dangling.  When GDB fetched that event, gdbserver looked up the
corresponding thread, but found NULL; not expecting this, gdbserver
crashes when it tries to read this thread's registers.

gdb/gdbserver/
2015-08-21  Pedro Alves  <palves@redhat.com>

	PR gdb/18749
	* inferiors.c (remove_thread): Discard any pending stop reply for
	this thread.
	* server.c (remove_all_on_match_pid): Rename to ...
	(remove_all_on_match_ptid): ... this.  Work with a filter ptid
	instead of a pid.
	(discard_queued_stop_replies): Change parameter to a ptid.  Now
	extern.
	(handle_v_kill, kill_inferior_callback)
	(process_serial_event): Adjust.
	(captured_main): Call initialize_notif before starting the
	program, thus before threads are created.
	* server.h (discard_queued_stop_replies): Declare.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] gdbserver: don't pick a random thread if the current thread dies
@ 2015-08-21 18:54 sergiodj+buildbot
  2015-08-22  9:22 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-08-21 18:54 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f0db101d9897732d6556456e542d12ecf9e12e42 ***

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

gdbserver: don't pick a random thread if the current thread dies

In all-stop mode, if the current thread disappears while stopping all
threads, gdbserver calls set_desired_thread(0) ['0' means "I want the
continue thread"] which just picks the first thread in the list.

This looks like a dangerous thing to do.  GDBserver continues
processing whatever it was doing, but to the wrong thread.  If
debugging more than one process, we may even pick the wrong process.
Instead, GDBserver should detect the situation and bail out of
whatever is was doing.

The backends used to pay attention to the set 'cont_thread' (the Hc
thread, used in the old way to resume threads, before vCont), but all
such 'cont_thread' checks have been eliminated meanwhile.  The
remaining implicit dependencies that I found on there being a selected
thread in the backends are in the Ctrl-C handling, which some backends
use as thread to send a signal to.  Even that seems to me to be better
handled by always using the first thread in the list or by using the
signal_pid PID.

In order to make this a systematic approach, I'm making
set_desired_thread never fallback to a random thread, and instead end
up with current_thread == NULL, like already done in non-stop mode.
Then I updated all callers to handle the situation.

I stumbled on this while fixing other bugs exposed by
gdb.threads/fork-plus-threads.exp test.  The problems I saw were fixed
in a different way, but in any case, I think the potential for
problems is more or less obvious, and the resulting code looks a bit
less magical to me.

Tested on x86-64 Fedora 20, w/ native-extended-gdbserver board.

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

	* linux-low.c (wait_for_sigstop): Always switch to no thread
	selected if the previously current thread dies.
	* lynx-low.c (lynx_request_interrupt): Use the first thread's
	process instead of the current thread's.
	* remote-utils.c (input_interrupt): Don't check if there's no
	current thread.
	* server.c (gdb_read_memory, gdb_write_memory): If setting the
	current thread to the general thread fails, error out.
	(handle_qxfer_auxv, handle_qxfer_libraries)
	(handle_qxfer_libraries_svr4, handle_qxfer_siginfo)
	(handle_qxfer_spu, handle_qxfer_statictrace, handle_qxfer_fdpic)
	(handle_query): Check if there's a thread selected instead of
	checking whether there's any thread in the thread list.
	(handle_qxfer_threads, handle_qxfer_btrace)
	(handle_qxfer_btrace_conf): Don't error out early if there's no
	thread in the thread list.
	(handle_v_cont, myresume): Don't set the current thread to the
	continue thread.
	(process_serial_event) <Hg handling>: Also set thread_id if the
	previous general thread is still alive.
	(process_serial_event) <g/G handling>: If setting the current
	thread to the general thread fails, error out.
	* spu-low.c (spu_resume, spu_request_interrupt): Use the first
	thread's lwp instead of the current thread's.
	* target.c (set_desired_thread): If the desired thread was not
	found, leave the current thread pointing to NULL.  Return an int
	(boolean) indicating success.
	* target.h (set_desired_thread): Change return type to int.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] PR binutils/18257: Properly decode x86/Intel mask instructions.
@ 2015-08-21 11:57 sergiodj+buildbot
  2015-08-21 17:18 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-08-21 11:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ab4e4ed5dabc378c06ee647afd5793513393ae3f ***

Author: Alexander Fomin <alexander.fomin@intel.com>
Branch: master
Commit: ab4e4ed5dabc378c06ee647afd5793513393ae3f

PR binutils/18257: Properly decode x86/Intel mask instructions.

opcodes/

	PR binutils/18257
	* i386-dis.c: Use MOD_TABLE for most of mask instructions.
	(MOD enum): Add MOD_VEX_W_0_0F41_P_0_LEN_1, MOD_VEX_W_1_0F41_P_0_LEN_1,
	MOD_VEX_W_0_0F41_P_2_LEN_1, MOD_VEX_W_1_0F41_P_2_LEN_1,
	MOD_VEX_W_0_0F42_P_0_LEN_1, MOD_VEX_W_1_0F42_P_0_LEN_1,
	MOD_VEX_W_0_0F42_P_2_LEN_1, MOD_VEX_W_1_0F42_P_2_LEN_1,
	MOD_VEX_W_0_0F44_P_0_LEN_1, MOD_VEX_W_1_0F44_P_0_LEN_1,
	MOD_VEX_W_0_0F44_P_2_LEN_1, MOD_VEX_W_1_0F44_P_2_LEN_1,
	MOD_VEX_W_0_0F45_P_0_LEN_1, MOD_VEX_W_1_0F45_P_0_LEN_1,
	MOD_VEX_W_0_0F45_P_2_LEN_1, MOD_VEX_W_1_0F45_P_2_LEN_1,
	MOD_VEX_W_0_0F46_P_0_LEN_1, MOD_VEX_W_1_0F46_P_0_LEN_1,
	MOD_VEX_W_0_0F46_P_2_LEN_1, MOD_VEX_W_1_0F46_P_2_LEN_1,
	MOD_VEX_W_0_0F47_P_0_LEN_1, MOD_VEX_W_1_0F47_P_0_LEN_1,
	MOD_VEX_W_0_0F47_P_2_LEN_1, MOD_VEX_W_1_0F47_P_2_LEN_1,
	MOD_VEX_W_0_0F4A_P_0_LEN_1, MOD_VEX_W_1_0F4A_P_0_LEN_1,
	MOD_VEX_W_0_0F4A_P_2_LEN_1, MOD_VEX_W_1_0F4A_P_2_LEN_1,
	MOD_VEX_W_0_0F4B_P_0_LEN_1, MOD_VEX_W_1_0F4B_P_0_LEN_1,
	MOD_VEX_W_0_0F4B_P_2_LEN_1, MOD_VEX_W_0_0F91_P_0_LEN_0,
	MOD_VEX_W_1_0F91_P_0_LEN_0, MOD_VEX_W_0_0F91_P_2_LEN_0,
	MOD_VEX_W_1_0F91_P_2_LEN_0, MOD_VEX_W_0_0F92_P_0_LEN_0,
	MOD_VEX_W_0_0F92_P_2_LEN_0, MOD_VEX_W_0_0F92_P_3_LEN_0,
	MOD_VEX_W_1_0F92_P_3_LEN_0, MOD_VEX_W_0_0F93_P_0_LEN_0,
	MOD_VEX_W_0_0F93_P_2_LEN_0, MOD_VEX_W_0_0F93_P_3_LEN_0,
	MOD_VEX_W_1_0F93_P_3_LEN_0, MOD_VEX_W_0_0F98_P_0_LEN_0,
	MOD_VEX_W_1_0F98_P_0_LEN_0, MOD_VEX_W_0_0F98_P_2_LEN_0,
	MOD_VEX_W_1_0F98_P_2_LEN_0, MOD_VEX_W_0_0F99_P_0_LEN_0,
	MOD_VEX_W_1_0F99_P_0_LEN_0, MOD_VEX_W_0_0F99_P_2_LEN_0,
	MOD_VEX_W_1_0F99_P_2_LEN_0, MOD_VEX_W_0_0F3A30_P_2_LEN_0,
	MOD_VEX_W_1_0F3A30_P_2_LEN_0, MOD_VEX_W_0_0F3A31_P_2_LEN_0,
	MOD_VEX_W_1_0F3A31_P_2_LEN_0, MOD_VEX_W_0_0F3A32_P_2_LEN_0,
	MOD_VEX_W_1_0F3A32_P_2_LEN_0, MOD_VEX_W_0_0F3A33_P_2_LEN_0,
	MOD_VEX_W_1_0F3A33_P_2_LEN_0.
	(vex_w_table): Replace terminals with MOD_TABLE entries for
	most of mask instructions.

gas/testsuite

	PR binutils/18257
	* gas/i386/disassem.s: Add mask instructions with invalid ModR/M byte.
	* gas/i386/x86-64-disassem.s: Likewise.
	* gas/i386/disassem.d: Updated.
	* gas/i386/x86-64-disassem.d: Likewise.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Fix gdb.server/solib-list.exp native-extended-gdbserver regression
@ 2015-08-20 19:30 sergiodj+buildbot
  2015-08-20 21:14 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-08-20 19:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0e433b32028e65f1f2f13e7c0d26061a37b7d583 ***

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

Fix gdb.server/solib-list.exp native-extended-gdbserver regression

Commit 221e1a37 (remote non-stop: Process initially stopped threads
before other commands) caused a test regression when testing with the
native-extended-gdbserver board:

  FAIL: gdb.server/solib-list.exp: non-stop 1: non-stop interior stop (timeout)

This "interior stop" now happens before "target remote" prints the
prompt, so we should no longer explicitly expect it.

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

	* gdb.server/solib-list.exp: No longer expect an interior stop in
	non-stop mode.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Fix language of compilation unit with unknown file extension
@ 2015-08-20 11:45 sergiodj+buildbot
  2015-08-20 14:59 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-08-20 11:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 40e3ad0ebb0c71008b928d6d350e9258dc1dcf2a ***

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

Fix language of compilation unit with unknown file extension

Here, in dwarfread.c:process_full_comp_unit:

      /* Set symtab language to language from DW_AT_language.  If the
	 compilation is from a C file generated by language preprocessors, do
	 not set the language if it was already deduced by start_subfile.  */
      if (!(cu->language == language_c
	    && COMPUNIT_FILETABS (cust)->language != language_c))
	COMPUNIT_FILETABS (cust)->language = cu->language;

in case start_subfile doesn't manage to deduce a language
COMPUNIT_FILETABS(cust)->language ends up as language_unknown, not
language_c.  So the condition above evals false and we never set the
language from the cu's language.

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

	* dwarf2read.c (process_full_comp_unit): To tell whether
	start_subfile managed to deduce a language, test for
	language_unknown instead of language_c.

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

	* gdb.dwarf2/comp-unit-lang.exp: New file.
	* gdb.dwarf2/comp-unit-lang.c: New file.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [AArch64][4/6] LD support TLSLD move/add relocation types
@ 2015-08-19 17:46 sergiodj+buildbot
  2015-08-20  0:01 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-08-19 17:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6ffe9a1ba36f3a896ae323e35a207b6451e8f7f9 ***

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

[AArch64][4/6] LD support TLSLD move/add relocation types

2015-08-19  Jiong Wang  <jiong.wang@arm.com>

bfd/
  PR ld/18276
  * elfnn-aarch64.c (IS_AARCH64_TLS_RELOC): Recognize new relocation
  types, including BFD_RELOC_AARCH64_TLSLD_ADD_DTPREL_HI12,
  BFD_RELOC_AARCH64_TLSLD_MOVW_DTPREL_G0,
  BFD_RELOC_AARCH64_TLSLD_MOVW_DTPREL_G0_NC,
  BFD_RELOC_AARCH64_TLSLD_MOVW_DTPREL_G1,
  BFD_RELOC_AARCH64_TLSLD_MOVW_DTPREL_G1_NC,
  BFD_RELOC_AARCH64_TLSLD_MOVW_DTPREL_G2.
  (elfNN_aarch64_final_link_relocate): Likewise.
  * elfxx-aarch64.c (_bfd_aarch64_elf_put_addend): Likewise.
  (_bfd_aarch64_elf_resolve_relocation): Likewise.

ld/testsuite/
  * ld-aarch64/emit-relocs-87.s: New testcase.
  * ld-aarch64/emit-relocs-88.s: Likewise.
  * ld-aarch64/emit-relocs-88-overflow.s: Likewise.
  * ld-aarch64/emit-relocs-89.s: Likewise.
  * ld-aarch64/emit-relocs-90.s: Likewise.
  * ld-aarch64/emit-relocs-90-overflow.s: Likewise.
  * ld-aarch64/emit-relocs-523.s: Likewise.
  * ld-aarch64/emit-relocs-524.s: Likewise.
  * ld-aarch64/emit-relocs-525.s: Likewise.
  * ld-aarch64/emit-relocs-527.s: Likewise.
  * ld-aarch64/emit-relocs-526.s: Likewise.
  * ld-aarch64/emit-relocs-528.s: Likewise.
  * ld-aarch64/emit-relocs-528-overflow.s: Likewise.
  * ld-aarch64/emit-relocs-87.d: New expectation file.
  * ld-aarch64/emit-relocs-88.d: Likewise.
  * ld-aarch64/emit-relocs-88-overflow.d: Likewise.
  * ld-aarch64/emit-relocs-89.d: Likewise.
  * ld-aarch64/emit-relocs-90.d: Likewise.
  * ld-aarch64/emit-relocs-90-overflow.d: Likewise.
  * ld-aarch64/emit-relocs-91.d: Likewise.
  * ld-aarch64/emit-relocs-523.d: Likewise.
  * ld-aarch64/emit-relocs-524.d: Likewise.
  * ld-aarch64/emit-relocs-525.d: Likewise.
  * ld-aarch64/emit-relocs-526.d: Likewise.
  * ld-aarch64/emit-relocs-527.d: Likewise.
  * ld-aarch64/emit-relocs-528.d: Likewise.
  * ld-aarch64/emit-relocs-528-overflow.d: Likewise.
  * ld-aarch64/aarch64-elf.exp: Run new testcases.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [AArch64][3/6] GAS support TLSLD move/add relocation types
@ 2015-08-19 17:17 sergiodj+buildbot
  2015-08-19 22:10 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-08-19 17:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 49df5539f9070c01128135a7d63f44b2efc4de6a ***

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

[AArch64][3/6] GAS support TLSLD move/add relocation types

2015-08-19  Jiong Wang  <jiong.wang@arm.com>

bfd/
  * reloc.c (BFD_RELOC_AARCH64_TLSLD_ADD_DTPREL_HI12,
  BFD_RELOC_AARCH64_TLSLD_MOVW_DTPREL_G0,
  BFD_RELOC_AARCH64_TLSLD_MOVW_DTPREL_G0_NC,
  BFD_RELOC_AARCH64_TLSLD_MOVW_DTPREL_G1,
  BFD_RELOC_AARCH64_TLSLD_MOVW_DTPREL_G1_NC,
  BFD_RELOC_AARCH64_TLSLD_MOVW_DTPREL_G2): New entries.
  * elfnn-aarch64.c (elfNN_aarch64_howto_table): Likewise.
  * bfd-in2.h: Regenerate.
  * libbfd.h: Regenerate.

gas/
  * config/tc-aarch64.c (reloc_table): New relocation modifiers,
  "dtprel_hi12", "dtprel_g0", "dtprel_g0_nc", "dtprel_g1",
  "dtprel_g1_nc", "dtprel_g2".
  (md_apply_fix): Support new relocation types.
  (aarch64_force_relocation): Likewise.
  (process_movw_reloc_info): Likewise.

gas/testsuite/
  * gas/aarch64/reloc-dtprel_g0.s: New testcase.
  * gas/aarch64/reloc-dtprel_g0-ilp32.s: Likewise.
  * gas/aarch64/reloc-dtprel_g0_nc.s: Likewise.
  * gas/aarch64/reloc-dtprel_g0_nc-ilp32.s: Likewise.
  * gas/aarch64/reloc-dtprel_g1.s: Likewise.
  * gas/aarch64/reloc-dtprel_g1-ilp32.s: Likewise.
  * gas/aarch64/reloc-dtprel_g1_nc.s: Likewise.
  * gas/aarch64/reloc-dtprel_g2.s: Likewise.
  * gas/aarch64/reloc-dtprel_hi12.s: Likewise.
  * gas/aarch64/reloc-dtprel_hi12-ilp32.s: Likewise.
  * gas/aarch64/reloc-dtprel_g0.d: New expectation file.
  * gas/aarch64/reloc-dtprel_g0-ilp32.d: Likewise.
  * gas/aarch64/reloc-dtprel_g0_nc.d: Likewise.
  * gas/aarch64/reloc-dtprel_g0_nc-ilp32.d: Likewise.
  * gas/aarch64/reloc-dtprel_g1.d: Likewise.
  * gas/aarch64/reloc-dtprel_g1-ilp32.d: Likewise.
  * gas/aarch64/reloc-dtprel_g1_nc.d: Likewise.
  * gas/aarch64/reloc-dtprel_g2.d: Likewise.
  * gas/aarch64/reloc-dtprel_hi12.d: Likewise.
  * gas/aarch64/reloc-dtprel_hi12-ilp32.d: Likewise.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [AArch64][5/6] GAS support TLSLD load/store relocation types
@ 2015-08-19 16:42 sergiodj+buildbot
  2015-08-20  7:32 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-08-19 16:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4c5625238cccb048261d7ce0eb748ee5e0d67cf0 ***

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

[AArch64][5/6] GAS support TLSLD load/store relocation types

2015-08-19  Jiong Wang  <jiong.wang@arm.com>

bfd/
  * reloc.c: New entries, including
  BFD_RELOC_AARCH64_TLSLD_LDST16_DTPREL_LO12,
  BFD_RELOC_AARCH64_TLSLD_LDST16_DTPREL_LO12_NC,
  BFD_RELOC_AARCH64_TLSLD_LDST32_DTPREL_LO12,
  BFD_RELOC_AARCH64_TLSLD_LDST32_DTPREL_LO12_NC,
  BFD_RELOC_AARCH64_TLSLD_LDST64_DTPREL_LO12,
  BFD_RELOC_AARCH64_TLSLD_LDST64_DTPREL_LO12_NC.
  BFD_RELOC_AARCH64_TLSLD_LDST8_DTPREL_LO12,
  BFD_RELOC_AARCH64_TLSLD_LDST8_DTPREL_LO12_NC.
  * elfnn-aarch64.c (elfNN_aarch64_howto_table): Likewise.
  * bfd-in2.h: Regenerate.
  * libbfd.h: Regenerate.

gas/
  * config/tc-aarch64.c (reloc_table): New relocation types support for
  dtprel_lo12.
  (ldst_lo12_determine_real_reloc_type): Support
  BFD_RELOC_AARCH64_TLSLD_LDST16_DTPREL_LO12,
  BFD_RELOC_AARCH64_TLSLD_LDST16_DTPREL_LO12_NC,
  BFD_RELOC_AARCH64_TLSLD_LDST32_DTPREL_LO12,
  BFD_RELOC_AARCH64_TLSLD_LDST32_DTPREL_LO12_NC,
  BFD_RELOC_AARCH64_TLSLD_LDST64_DTPREL_LO12,
  BFD_RELOC_AARCH64_TLSLD_LDST64_DTPREL_LO12_NC,
  BFD_RELOC_AARCH64_TLSLD_LDST8_DTPREL_LO12,
  BFD_RELOC_AARCH64_TLSLD_LDST8_DTPREL_LO12_NC.
  (parse_operands): Likewise.
  (md_apply_fix): Likewise
  (aarch64_force_relocation): Likewise.
  (process_movw_reloc_info): Likewise.

gas/testsuite/
  * gas/aarch64/reloc-dtprel_lo12-ldst8.s: New testcase.
  * gas/aarch64/reloc-dtprel_lo12_nc-ldstc.s: Likewise.
  * gas/aarch64/reloc-dtprel_lo12-ldst16.s: Likewise.
  * gas/aarch64/reloc-dtprel_lo12_nc-ldst16.s: Likewise.
  * gas/aarch64/reloc-dtprel_lo12-ldst32.s: Likewise.
  * gas/aarch64/reloc-dtprel_lo12_nc-ldst32.s: Likewise.
  * gas/aarch64/reloc-dtprel_lo12-ldst64.s: Likewise.
  * gas/aarch64/reloc-dtprel_lo12_nc-ldst64.s: Likewise.
  * gas/aarch64/reloc-dtprel_lo12-ldst8.d: New expectation file.
  * gas/aarch64/reloc-dtprel_lo12_nc-ldst8.d: Likewise.
  * gas/aarch64/reloc-dtprel_lo12-ldst16.d: Likewise.
  * gas/aarch64/reloc-dtprel_lo12_nc-ldst16.d: Likewise.
  * gas/aarch64/reloc-dtprel_lo12-ldst32.d: Likewise.
  * gas/aarch64/reloc-dtprel_lo12_nc-ldst32.d: Likewise.
  * gas/aarch64/reloc-dtprel-lo12-ldst64.d: Likewise.
  * gas/aarch64/reloc-dtprel_lo12_nc-ldst64.d: Likewise.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [AArch64][1/6] GAS support BFD_RELOC_AARCH64_TLSLD_ADD_DTPREL_LO12_NC
@ 2015-08-19 16:10 sergiodj+buildbot
  2015-08-19 19:06 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-08-19 16:10 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 13289c10e20281adf480d9822861412a7ade721d ***

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

[AArch64][1/6] GAS support BFD_RELOC_AARCH64_TLSLD_ADD_DTPREL_LO12_NC

2015-08-19  Jiong Wang  <jiong.wang@arm.com>

bfd/
  * reloc.c (BFD_RELOC_AARCH64_TLSLD_ADD_DTPREL_LO12_NC): New entry.
  * bfd-in2.h: Regenerate.
  * libbfd.h: Regenerate.
  * elfnn-aarch64.c (elfNN_aarch64_howto_table): New entry for
  BFD_RELOC_AARCH64_TLSLD_ADD_DTPREL_LO12_NC.

gas/
  * config/tc-aarch64.c (reloc_table): New relocation modifiers.
  (md_apply_fix): Support BFD_RELOC_AARCH64_TLSLD_ADD_DTPREL_LO12_NC.
  (aarch64_force_relocation): Likewise.

gas/testsuite/
  * gas/aarch64/reloc-dtprel_lo12_nc.s: New testcase.
  * gas/aarch64/reloc-dtprel_lo12_nc-ilp32.s: Likewise.
  * gas/aarch64/reloc-dtprel_lo12_nc.d: New expectation file.
  * gas/aarch64/reloc-dtprel_lo12_nc-ilp32.d: Likewise.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Prelimit number of bytes to read in "vFile:pread:"
@ 2015-08-19 13:10 sergiodj+buildbot
  2015-08-19 14:54 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-08-19 13:10 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 45face3ba147a4c5f4f7e09cf10c95986b915002 ***

Author: Gary Benson <gbenson@redhat.com>
Branch: master
Commit: 45face3ba147a4c5f4f7e09cf10c95986b915002

Prelimit number of bytes to read in "vFile:pread:"

While handling "vFile:pread:" packets, gdbserver would read the
number of bytes requested regardless of whether this would fit
into the reply packet.  gdbserver would then return a packet's
worth of data and discard the remainder.  When accessing large
binaries GDB (via BFD) routinely makes large "vFile:pread:"
requests, resulting in gdbserver allocating large unnecessary
buffers and reading some portions of the file many times over.

This commit causes gdbserver to limit the number of bytes to be
read to a sensible maximum prior to allocating buffers and reading
data.

gdb/gdbserver/ChangeLog:

	* hostio.c (handle_pread): Do not attempt to read more data
	than hostio_reply_with_data can fit in a packet.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Remove link_info.pic
@ 2015-08-19  4:02 sergiodj+buildbot
  2015-08-19  9:38 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-08-19  4:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 64d94ba01a4f56ac10bb277e66bb00d82bd97f10 ***

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

Remove link_info.pic

Adding type_pie to output_type allows us to remove link_info.pic and
with some reordering of the enum, produces better code.

include/
	* bfdlink.h (enum output_type): Delete type_executable, add type_pde
	and type_pie.  Reorder.
	(struct bfd_link_info): Delete pic field.
	(bfd_link_executable, bfd_link_pde, bfd_link_pie, bfd_link_pic): Adjust.
ld/
	* emultempl/aix.em: Don't set link_info.pic.
	* emultempl/pe.em: Likewise.
	* emultempl/pep.em: Likewise.
	* emultempl/sunos.em: Likewise.
	* lexsup.c (parse_args): Likewise.  Set type_pie for -pie.
	* plugin.c (set_tv_header <LDPT_LINKER_OUTPUT>): Simplify.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Add bfd_link_pde, and simplify some tests of link_info.type
@ 2015-08-19  3:57 sergiodj+buildbot
  2015-08-19  7:46 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-08-19  3:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3cbc1e5e68341e53a03fe7e9d38fc02e0d78c418 ***

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

Add bfd_link_pde, and simplify some tests of link_info.type

include/
	* bfdlink.h (bfd_link_pde): Define.
bfd/
	* elf-s390-common.c: Simplify expressions using
	bfd_linke_executable, bfd_link_pie and bfd_link_pic.
	* elf32-arm.c: Likewise.
	* elf32-bfin.c: Likewise.
	* elf32-frv.c: Likewise.
	* elf32-m68k.c: Likewise.
	* elf32-nios2.c: Likewise.
	* elf32-ppc.c: Likewise.
	* elf32-s390.c: Likewise.
	* elf32-sh.c: Likewise.
	* elf64-alpha.c: Likewise.
	* elf64-ppc.c: Likewise.
	* elf64-s390.c: Likewise.
	* elflink.c: Likewise.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] gdbserver/linux-aarch32-low: build failure when NT_ARM_VFP not defined
@ 2015-08-18 22:51 sergiodj+buildbot
  2015-08-19  5:59 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-08-18 22:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 16d5f64295ccf2a8e9fe3ed350c94c38cee5a481 ***

Author: Joel Brobecker <brobecker@adacore.com>
Branch: master
Commit: 16d5f64295ccf2a8e9fe3ed350c94c38cee5a481

gdbserver/linux-aarch32-low: build failure when NT_ARM_VFP not defined

On some older versions of GNU/Linux, gdbserver now fails to build
due to an undefined reference to NT_ARM_VFP. Same issue on Android,
where this macros is undefined until Android API level 21 (Android
5.0 "Lollipop").

This patch modifies linux-aarch32-low.c to define that macros when
not already defined.

gdb/gdbserver/ChangeLog:

        * linux-aarch32-low.c (NT_ARM_VFP): Define if not already defined.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] PR mi/18833 gdb.execute ("set param value", to_string=True) will crash gdb if using MI
@ 2015-08-18 21:13 sergiodj+buildbot
  2015-08-19  3:55 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-08-18 21:13 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4d6cceb4e40a057dbe4d9ad94b0641d5f4725c09 ***

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

PR mi/18833 gdb.execute ("set param value", to_string=True) will crash gdb if using MI

gdb/ChangeLog:

	* cli/cli-logging.c (pop_output_files): Don't restore redirection
	if MI-like.
	* mi/mi-out.c: #include "vec.h".
	(ui_filep): New type.
	(DEV_VEC_P (ui_filep)): New type.
	(struct ui_out_data) <buffer, original_buffer>: Delete.
	(struct ui_out_data) <streams>: New member.
	(mi_ui_out_impl): Add data_destroy field.
	(mi_field_string, mi_field_fmt): Update.
	(mi_flush, mi_redirect, field_separator): Update.
	(mi_open, mi_close): Update.
	(mi_out_buffered, mi_out_rewind, mi_out_put): Update.
	(mi_out_data_ctor, mi_out_data_dtor): New functions.
	(mi_out_new): Call mi_out_data_ctor.

testsuite/gdb/ChangeLog:

	* lib/gdb.exp (skip_python_tests_prompt): Renamed from
	skip_python_tests.  New arg prompt_regexp.
	(skip_python_tests): New function.
	* lib/mi-support.exp (mi_skip_python_tests): New function.
	* gdb.python/py-mi-objfile-gdb.py: New file.
	* gdb.python/py-mi-objfile.c: New file.
	* gdb.python/py-mi-objfile.exp: New file.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Fix mis-parsing of hex register numbers in 'T' stop replies.
@ 2015-08-18 17:42 sergiodj+buildbot
  2015-08-19  0:28 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-08-18 17:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 26d56a939e9e54e09d46ea6e9678463ac344fa33 ***

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

Fix mis-parsing of hex register numbers in 'T' stop replies.

2015-08-18  Sandra Loosemore  <sandra@codesourcery.com>

	gdb/
	* remote.c (strprefix): New.
	(remote_parse_stop_reply): Use strprefix instead of strncmp
	to ensure exact match of keyword.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Return reloc_class_ifunc for reloc against IFUNC
@ 2015-08-18 17:09 sergiodj+buildbot
  2015-08-18 22:59 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-08-18 17:09 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cae1fbbb7e3d770702a0d7a5027b46835e6adc13 ***

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

Return reloc_class_ifunc for reloc against IFUNC

elf_XXX_reloc_type_class should return reloc_class_ifunc for relocation
against STT_GNU_IFUNC symbol.

bfd/

	PR ld/18841
	* elf-bfd.h (elf_link_hash_table): Add dynsym.
	* elf32-i386.c (elf_i386_reloc_type_class): Return
	reloc_class_ifunc for relocation against STT_GNU_IFUNC symbol.
	* elf64-x86-64.c (elf_x86_64_reloc_type_class): Likewise.
	* elflink.c (_bfd_elf_link_create_dynamic_sections): Set dynsym.
	(bfd_elf_size_dynsym_hash_dynstr): Use dynsym.
	(elf_final_link_info): Remove dynsym_sec.
	(elf_link_output_extsym): Replace dynsym_sec with dynsym.
	(bfd_elf_final_link): Remove reference to dynsym_sec.  Replace
	dynsym_sec with dynsym.

ld/testsuite/

	PR ld/18841
	* ld-ifunc/ifunc.exp: Add a test for PR ld/18841.
	* ld-ifunc/pr18841.out: New file.
	* ld-ifunc/pr18841a.c: Likewise.
	* ld-ifunc/pr18841b.c: Likewise.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] gdb: New maintenance command to disable bfd sharing.
@ 2015-08-18 13:56 sergiodj+buildbot
  2015-08-18 17:11 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-08-18 13:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 18989b3c5642e2ba533e02737797dcf06134229b ***

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

gdb: New maintenance command to disable bfd sharing.

In some rare maintainer cases it is desirable to be able to disable bfd
sharing.  This patch adds new commands maintenance set/show commands for
bfd-sharing, allowing gdb's bfd cache to be turned off.

gdb/ChangeLog:

	* gdb_bfd.c (bfd_sharing): New variable.
	(show_bfd_sharing): New function.
	(gdb_bfd_open): Check bfd_sharing variable.
	(_initialize_gdb_bfd): Add new set/show command.
	* NEWS: Mention new command.

gdb/doc/ChangeLog:

	* gdb.texinfo (Maintenance Commands): Move documentation of "main
	info bfds" to...
	(File Caching): A New section.  Outline bfd caching, and add new
	description for "main set/show bfd-sharing".


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] gdb: Improve cache matching criteria for the bfd cache.
@ 2015-08-18 13:12 sergiodj+buildbot
  2015-08-18 15:36 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-08-18 13:12 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c04fe68f6b94815d3f49c9aed64b2c388d45f4aa ***

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

gdb: Improve cache matching criteria for the bfd cache.

Within gdb open bfd objects are reused where possible if an attempt is
made to reopen a file that is already being debugged.  To spot if the on
disc file has changed gdb currently examines the mtime of the file and
compares it to the mtime of the open bfd in the cache.

A problem exists when the on disc file is being rapidly regenerated, as
happens, for example, with automated testing.  In some cases the file is
generated so quickly that the mtime appears not to change, while the on
disc file has changed.

This patch extends the bfd cache to also hold the file size of the file,
the inode of the file, and the device id of the file; gdb can then
compare filename, file size, mtime, inode, and device id to determine if
an existing bfd object can be reused.

gdb/ChangeLog:

	* gdb_bfd.c (struct gdb_bfd_data): Add size, inode, and device id
	field.
	(struct gdb_bfd_cache_search): Likewise.
	(eq_bfd): Compare the size, inode, and device id fields.
	(gdb_bfd_open): Initialise the size, inode, and device id fields.
	(gdb_bfd_ref): Likewise.
	(gdb_bfd_unref): Likewise.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Use $SED in bfd Makefile
@ 2015-08-18  8:05 sergiodj+buildbot
  2015-08-18 10:00 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-08-18  8:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fe875424a05df7c4055cd9382ab76f65e952c4dd ***

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

Use $SED in bfd Makefile

	PR 18667
	* Makefile.am: Use $(SED) in place of sed throughout.
	* Makefile.in: Regenerate.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] ui-out.c (default_ui_out_impl): Add comment.
@ 2015-08-17 20:18 sergiodj+buildbot
  2015-08-17 23:04 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-08-17 20:18 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 71b57e37fe94bbc17f57f8f9ca5e9c5400cedd6b ***

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

ui-out.c (default_ui_out_impl): Add comment.

gdb/ChangeLog:

	* ui-out.c (default_ui_out_impl): Add comment.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Move strace -m/explicit location test to strace.exp
@ 2015-08-17 19:21 sergiodj+buildbot
  2015-08-17 20:35 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-08-17 19:21 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ad89c2aa677c28c76ffd5a35e2b36eece4d82597 ***

Author: Keith Seitz <keiths@redhat.com>
Branch: master
Commit: ad89c2aa677c28c76ffd5a35e2b36eece4d82597

Move strace -m/explicit location test to strace.exp

One of the build slaves shows this error running explicit.exp:

(gdb) strace -m gdbfoobarbaz
Remote failure reply: E.In-process agent library not loaded in process.
Fast and static tracepoints unavailable.
(gdb) FAIL: gdb.linespec/explicit.exp: strace -m gdbfoobarbaz

There are two big problems with this test:
1) The expected output is actually not what the test is meant to test for.
2) This test should really only run where it is supported.

This is most easily fixed by moving the test to gdb.trace/strace.exp.

gdb/testsuite/ChangeLog

	* gdb.linespec/explicit.exp: Move strace test from here ...
	* gdb.trace/strace.exp: ... to here.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Add end_psymtab_common, have all debug info readers call it.
@ 2015-08-16  0:29 sergiodj+buildbot
  2015-08-17  9:10 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-08-16  0:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8763cedeec7f0a1daea41c2231bda165652e273b ***

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

Add end_psymtab_common, have all debug info readers call it.

gdb/ChangeLog:

	* dbxread.c (dbx_end_psymtab): Renamed from end_psymtab.  All callers
	updated.  Call end_psymtab_common.
	* dwarf2read.c (process_psymtab_comp_unit_reader): Call
	end_psymtab_common.
	(build_type_psymtabs_reader): Ditto.
	* psympriv.h (sort_pst_symbols): Delete.
	(end_psymtab_common): Declare.
	* psymtab.c (sort_pst_symbols): Make static.
	(end_psymtab_common): New function.
	* xcoffread.c (xcoff_end_psymtab): Call end_psymtab_common.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Fix invoking "[kill|detach] inferiors" on inferiors that are not running
@ 2015-08-15 18:05 sergiodj+buildbot
  2015-08-16 20:24 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ 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] 1132+ messages in thread
* [binutils-gdb] New /s modifier for the disassemble command.
@ 2015-08-15  4:59 sergiodj+buildbot
  2015-08-15 23:39 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ 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] 1132+ messages in thread
* [binutils-gdb] Rename location accessor macro parameters to silence ARI
@ 2015-08-14 22:33 sergiodj+buildbot
  2015-08-15 21:15 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ 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] 1132+ messages in thread
* [binutils-gdb] Add support for DT_MIPS_RLD_MAP_REL.
@ 2015-08-14 14:27 sergiodj+buildbot
  2015-08-15 17:37 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ 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] 1132+ messages in thread
* [binutils-gdb] Add myself to gdb MAINTAINERS
@ 2015-08-14 12:24 sergiodj+buildbot
  2015-08-15 15:46 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ 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] 1132+ messages in thread
* [binutils-gdb] Revert "Fix encoding or OpenRisk1000 PC relative relocations."
@ 2015-08-14  1:48 sergiodj+buildbot
  2015-08-15  9:25 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ 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] 1132+ messages in thread
* [binutils-gdb] [D] Support looking up symbols in the current and imported modules.
@ 2015-08-13 20:36 sergiodj+buildbot
  2015-08-14 23:57 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ 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] 1132+ messages in thread
* [binutils-gdb] Fix Python frame unwinder issue caught by Valgrind
@ 2015-08-13 18:17 sergiodj+buildbot
  2015-08-13 23:45 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ 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] 1132+ messages in thread
* [binutils-gdb] Mass rename `explicit' -> `explicit_loc'.
@ 2015-08-13 17:22 sergiodj+buildbot
  2015-08-13 22:34 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ 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] 1132+ messages in thread
* [binutils-gdb] Fixes for unpredictable nops and 26-bit versions of teq, tst, cmn, cmp.
@ 2015-08-13 10:53 sergiodj+buildbot
  2015-08-13 20:10 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ 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] 1132+ messages in thread
* [binutils-gdb] [Ada] Add support for subprogram renamings
@ 2015-08-13  7:47 sergiodj+buildbot
  2015-08-13 18:50 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ 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] 1132+ messages in thread
* [binutils-gdb] gdb.base/dso2dso.exp sometimes broken
@ 2015-08-13  2:02 sergiodj+buildbot
  2015-08-13 17:29 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ 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] 1132+ messages in thread
* [binutils-gdb] [amd64] Invalid return address after displaced stepping
@ 2015-08-12 20:32 sergiodj+buildbot
  2015-08-13 14:47 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ 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] 1132+ messages in thread
* [binutils-gdb] Initialize `location' in gdbpy_decode_line
@ 2015-08-12 18:48 sergiodj+buildbot
  2015-08-13 13:36 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ 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] 1132+ messages in thread
* [binutils-gdb] Guarantee save-and-restore of GDBFLAGS on gdb.base/checkpoint-ns.exp
@ 2015-08-12 16:46 sergiodj+buildbot
  2015-08-13 12:23 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ 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] 1132+ messages in thread
* [binutils-gdb] [MIPS] Map 'move' to 'or'.
@ 2015-08-12 16:23 sergiodj+buildbot
  2015-08-13 11:43 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ 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] 1132+ messages in thread
* [binutils-gdb] Use save_vars to replace existing manipulation of globals in tests
@ 2015-08-12 15:57 sergiodj+buildbot
  2015-08-13 11:03 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ 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] 1132+ messages in thread
* [binutils-gdb] Introduce save_vars, a testsuite proc for safely manipulating globals
@ 2015-08-12 13:24 sergiodj+buildbot
  2015-08-13 10:21 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ 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] 1132+ messages in thread
* [binutils-gdb] Sync ansidecl.h with GCC
@ 2015-08-12 12:58 sergiodj+buildbot
  2015-08-13  9:38 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ 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] 1132+ messages in thread
* [binutils-gdb] Remove trailing spaces in opcodes
@ 2015-08-12 12:26 sergiodj+buildbot
  2015-08-13  8:48 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ 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] 1132+ messages in thread
* [binutils-gdb] Remove trailing spaces in bfd
@ 2015-08-12 11:58 sergiodj+buildbot
  2015-08-13  7:43 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ 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] 1132+ messages in thread
* [binutils-gdb] [regression] Do not read from catchpoint/watchpoint locations' addresses when checking for a permanent breakpoint
@ 2015-08-12  8:50 sergiodj+buildbot
  2015-08-12 23:09 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ 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] 1132+ messages in thread
* [binutils-gdb] Properly skip IFUNC relocations in debug sections
@ 2015-08-12  5:48 sergiodj+buildbot
  2015-08-12 22:27 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ 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] 1132+ messages in thread
* [binutils-gdb] Explicit locations: documentation updates
@ 2015-08-12  5:23 sergiodj+buildbot
  2015-08-12 21:41 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ 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] 1132+ messages in thread
* [binutils-gdb] Explicit locations: MI support for explicit locations
@ 2015-08-12  4:59 sergiodj+buildbot
  2015-08-12 20:58 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ 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] 1132+ messages in thread
* [binutils-gdb] Explicit locations: add UI features for CLI
@ 2015-08-12  4:30 sergiodj+buildbot
  2015-08-12 20:16 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ 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] 1132+ messages in thread
* [binutils-gdb] Explicit locations: introduce explicit locations
@ 2015-08-12  4:04 sergiodj+buildbot
  2015-08-12 19:36 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ 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] 1132+ messages in thread
* [binutils-gdb] Explicit locations: introduce probe locations
@ 2015-08-12  3:38 sergiodj+buildbot
  2015-08-12 18:49 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ 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] 1132+ messages in thread
* [binutils-gdb] Explicit locations: introduce address locations
@ 2015-08-12  3:12 sergiodj+buildbot
  2015-08-12 18:06 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ 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] 1132+ messages in thread
* [binutils-gdb] Explicit locations: use new location API
@ 2015-08-12  2:47 sergiodj+buildbot
  2015-08-12 17:22 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ 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] 1132+ messages in thread
* [binutils-gdb] Explicit locations: introduce new struct event_location-based API
@ 2015-08-12  2:19 sergiodj+buildbot
  2015-08-12 16:42 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ 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] 1132+ messages in thread
* [binutils-gdb] Explicit locations: rename "address string"/"addr_string" to "location"
@ 2015-08-12  1:53 sergiodj+buildbot
  2015-08-12 15:25 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ 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] 1132+ messages in thread
* [binutils-gdb] [AArch64] PR18668, repair long branch veneer for plt stub
@ 2015-08-12  0:11 sergiodj+buildbot
  2015-08-12 10:13 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ 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] 1132+ messages in thread
* [binutils-gdb] [AArch64][7/8] GAS support BFD_RELOC_AARCH64_TLSLD_ADD_DTPREL_LO12
@ 2015-08-11 23:19 sergiodj+buildbot
  2015-08-12  7:38 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ 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] 1132+ messages in thread
* [binutils-gdb] [AArch64][1/8] Add R_AARCH64_P32_TLSLD_ADR_PAGE21 in elf header
@ 2015-08-11 20:42 sergiodj+buildbot
  2015-08-11 22:59 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ 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] 1132+ messages in thread
* [binutils-gdb] Fix the disassembly of the AArch64 SIMD EXT instruction.
@ 2015-08-11 17:19 sergiodj+buildbot
  2015-08-11 20:13 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ 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] 1132+ messages in thread
* [binutils-gdb] Fix encoding or OpenRisk1000 PC relative relocations.
@ 2015-08-11 16:46 sergiodj+buildbot
  2015-08-11 18:54 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ 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] 1132+ messages in thread
* [binutils-gdb] Fix typo in coff-sh.c.
@ 2015-08-11 16:13 sergiodj+buildbot
  2015-08-11 17:43 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ 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] 1132+ messages in thread
* [binutils-gdb] PR gdb/18669 libiberty demangle.test failure: strtod() on sparc-sun-solaris2.9
@ 2015-08-11  7:25 sergiodj+buildbot
  2015-08-11  8:33 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ 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] 1132+ messages in thread
* [binutils-gdb] PR gdb/17960 Internal error: tracker != NULL when completing on file:function
@ 2015-08-10 19:25 sergiodj+buildbot
  2015-08-10 20:35 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ 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] 1132+ messages in thread
* [binutils-gdb] Replace hidden with versioned in elf_link_hash_entry
@ 2015-08-10 15:08 sergiodj+buildbot
  2015-08-10 16:36 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ 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] 1132+ messages in thread
* [binutils-gdb] Add SIGRIE instruction for MIPS R6
@ 2015-08-10  8:27 sergiodj+buildbot
  2015-08-10 15:22 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ 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] 1132+ messages in thread
* [binutils-gdb] Check sh_type/sh_flags/sh_addralign/sh_entsize when copying sh_link/sh_info
@ 2015-08-08  0:51 sergiodj+buildbot
  2015-08-10 13:21 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ 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] 1132+ messages in thread
* [binutils-gdb] S/390: displaced stepping and PC-relative RIL-b/RIL-c instructions
@ 2015-08-07 23:57 sergiodj+buildbot
  2015-08-09 23:44 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ 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] 1132+ messages in thread
* [binutils-gdb] Fix step-over-{trips-on-watchpoint|lands-on-breakpoint}.exp race
@ 2015-08-07 22:44 sergiodj+buildbot
  2015-08-09 20:07 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ 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] 1132+ messages in thread
* [binutils-gdb] Fix interrupt-noterm.exp on targets always in non-stop
@ 2015-08-07 22:08 sergiodj+buildbot
  2015-08-09 18:58 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ 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] 1132+ messages in thread
* [binutils-gdb] Teach non-stop to do in-line step-overs (stop all, step, restart)
@ 2015-08-07 21:07 sergiodj+buildbot
  2015-08-09 15:21 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ 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] 1132+ messages in thread
* [binutils-gdb] Factor out code to re-resume stepped thread
@ 2015-08-07 20:23 sergiodj+buildbot
  2015-08-09 14:01 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ 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] 1132+ messages in thread
* [binutils-gdb] Add comments to currently_stepping and target_resume
@ 2015-08-07 19:58 sergiodj+buildbot
  2015-08-09 12:50 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ 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] 1132+ messages in thread
[parent not found: <33ebda9d6841e18d9ef18b94c3dcad7d0498ab3d@gdb-build>]
* [binutils-gdb] Use keep_going in proceed and start_step_over too
@ 2015-08-07 19:05 sergiodj+buildbot
  2015-08-09 10:28 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ 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] 1132+ messages in thread
* [binutils-gdb] Embed the pending step-over chain in thread_info objects
@ 2015-08-07 18:40 sergiodj+buildbot
  2015-08-09  8:47 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-08-07 18:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c2829269f5af8a860b54ceac3596610b1f51fee5 ***

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

Embed the pending step-over chain in thread_info objects

In order to teach non-stop mode to do in-line step-overs (pause all
threads, remove breakpoint, single-step, reinsert breakpoint, restart
threads), we'll need to be able to queue in-line step over requests,
much like we queue displaced stepping (out-of-line) requests.
Actually, the queue should be the same -- threads wait for their turn
to step past something (breakpoint, watchpoint), doesn't matter what
technique we end up using when the step over actually starts.

I found that the queue management ends up simpler and more efficient
if embedded in the thread objects themselves.  This commit converts
the existing displaced stepping queue to that.  Later patches will
make the in-line step-overs code paths use it too.

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

	* gdbthread.h (struct thread_info) <step_over_prev,
	step_over_next>: New fields.
	(thread_step_over_chain_enqueue, thread_step_over_chain_remove)
	(thread_step_over_chain_next, thread_is_in_step_over_chain): New
	declarations.
	* infrun.c (struct displaced_step_request): Delete.
	(struct displaced_step_inferior_state) <step_request_queue>:
	Delete field.
	(displaced_step_prepare): Assert that trap_expected is set.  Use
	thread_step_over_chain_enqueue.  Split starting a new displaced
	step to ...
	(start_step_over): ... this new function.
	(resume): Assert the thread isn't waiting for a step over already.
	(proceed): Assert the thread isn't waiting for a step over
	already.
	(infrun_thread_stop_requested): Adjust to remove threads from the
	embedded step-over chain.
	(handle_inferior_event) <fork/vfork>: Call start_step_over after
	displaced_step_fixup.
	(handle_signal_stop): Call start_step_over after
	displaced_step_fixup.
	* infrun.h (step_over_queue_head): New declaration.
	* thread.c (step_over_chain_enqueue, step_over_chain_remove)
	(thread_step_over_chain_next, thread_is_in_step_over_chain)
	(thread_step_over_chain_enqueue)
	(thread_step_over_chain_remove): New functions.
	(delete_thread_1): Remove thread from the step-over chain.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Change adjust_pc_after_break's prototype
@ 2015-08-07 17:20 sergiodj+buildbot
  2015-08-08 21:13 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ 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] 1132+ messages in thread
* [binutils-gdb] Sync config.sub and config.guess with GCC
@ 2015-08-07 15:10 sergiodj+buildbot
  2015-08-08 17:44 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-08-07 15:10 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5960642af99c6dc84b28e1bc69a617099b9dee97 ***

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

Sync config.sub and config.guess with GCC
	Sync with GCC
	2015-07-28  Ben Elliston  <bje@gnu.org>

	* config.sub, config.guess: Import from upstream.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Properly merge hidden versioned symbol
@ 2015-08-07 12:17 sergiodj+buildbot
  2015-08-08 15:19 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ 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] 1132+ messages in thread
* [binutils-gdb] gdb: get_frame_language now takes a frame parameter.
@ 2015-08-07 11:12 sergiodj+buildbot
  2015-08-08 12:02 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ 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] 1132+ messages in thread
* [binutils-gdb] configure: check for perf_event.h version
@ 2015-08-07  8:34 sergiodj+buildbot
  2015-08-08  8:16 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-08-07  8:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5599c404621b2d8ac021c1427aee6e8974572042 ***

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

configure: check for perf_event.h version
Intel(R) Processor Trace support requires a recent linux/perf_event.h header.

When GDB is built on an older system, Intel(R) Processor Trace will not be
available and there is no indication in the configure and build log as to
what went wrong.

Check for a compatible linux/perf_event.h at configure-time.

gdb/
	* configure.ac: Check for PERF_ATTR_SIZE_VER5 in linux/perf_event.h
	* configure: Regenerate.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Yaakov Selkowitz: fixes for in-tree libiconv
@ 2015-08-07  5:32 sergiodj+buildbot
  2015-08-07 23:49 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ 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] 1132+ messages in thread
* [binutils-gdb] Bump timeouts for a couple gdb.reverse/*-precsave.exp tests
@ 2015-08-06 23:28 sergiodj+buildbot
  2015-08-07 22:38 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ 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] 1132+ messages in thread
* [binutils-gdb] gdbserver: no point in hiding the regcache type nowadays
@ 2015-08-06 18:16 sergiodj+buildbot
  2015-08-07 17:52 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ 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] 1132+ messages in thread
* [binutils-gdb] gdbserver: fix silent error exit
@ 2015-08-06 16:55 sergiodj+buildbot
  2015-08-07 14:09 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-08-06 16:55 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 608a1e46394e9df951968c9112fbec3065da5fba ***

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

gdbserver: fix silent error exit
Running gdb.threads/process-dies-while-handling-bp.exp against
gdbserver sometimes FAILs because GDBserver drops the connection, but
the logs leave no clue on what the reason could be.  Running manually
a few times, I saw the same:

 $  ./gdbserver/gdbserver --multi :9999 testsuite/gdb.threads/process-dies-while-handling-bp
 Process testsuite/gdb.threads/process-dies-while-handling-bp created; pid = 12766
 Listening on port 9999
 Remote debugging from host 127.0.0.1
 Listening on port 9999

 Child exited with status 0

 Child exited with status 0

What happened is that an exception escaped and gdbserver reopened the
connection, which led to that second "Listening on port 9999" output.

The error was a failure to access registers from a now-dead thread.
The exception probably shouldn't have escaped here, but meanwhile,
this at least makes the issue less mysterious.

Tested on x86_64 Fedora 20.

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

	* server.c (captured_main): On error, print the exception message
	to stderr, and if run_once is set, throw a quit.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] gdbserver: Fix non-stop / fork / step-over issues
@ 2015-08-06 10:34 sergiodj+buildbot
  2015-08-06 16:17 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-08-06 10:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 863d01bde2725d009c45ab7e9ba1dbf3f5b923f8 ***

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

gdbserver: Fix non-stop / fork / step-over issues
Ref: https://sourceware.org/ml/gdb-patches/2015-07/msg00868.html

This adds a test that has a multithreaded program have several threads
continuously fork, while another thread continuously steps over a
breakpoint.

This exposes several intertwined issues, which this patch addresses:

 - When we're stopping and suspending threads, some thread may fork,
   and we missed setting its suspend count to 1, like we do when a new
   clone/thread is detected.  When we next unsuspend threads, the fork
   child's suspend count goes below 0, which is bogus and fails an
   assertion.

 - If a step-over is cancelled because a signal arrives, but then gdb
   is not interested in the signal, we pass the signal straight back
   to the inferior.  However, we miss that we need to re-increment the
   suspend counts of all other threads that had been paused for the
   step-over.  As a result, other threads indefinitely end up stuck
   stopped.

 - If a detach request comes in just while gdbserver is handling a
   step-over (in the test at hand, this is GDB detaching the fork
   child), gdbserver internal errors in stabilize_thread's helpers,
   which assert that all thread's suspend counts are 0 (otherwise we
   wouldn't be able to move threads out of the jump pads).  The
   suspend counts aren't 0 while a step-over is in progress, because
   all threads but the one stepping past the breakpoint must remain
   paused until the step-over finishes and the breakpoint can be
   reinserted.

 - Occasionally, we see "BAD - reinserting but not stepping." being
   output (from within linux_resume_one_lwp_throw).  That was because
   GDB pokes memory while gdbserver is busy with a step-over, and that
   suspends threads, and then re-resumes them with proceed_one_lwp,
   which missed another reason to tell linux_resume_one_lwp that the
   thread should be set back to stepping.

 - In a couple places, we were resuming threads that are meant to be
   suspended.  E.g., when a vCont;c/s request for thread B comes in
   just while gdbserver is stepping thread A past a breakpoint.  The
   resume for thread B must be deferred until the step-over finishes.

 - The test runs with both "set detach-on-fork" on and off.  When off,
   it exercises the case of GDB detaching the fork child explicitly.
   When on, it exercises the case of gdb resuming the child
   explicitly.  In the "off" case, gdb seems to exponentially become
   slower as new inferiors are created.  This is _very_ noticeable as
   with only 100 inferiors gdb is crawling already, which makes the
   test take quite a bit to run.  For that reason, I've disabled the
   "off" variant for now.

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

	* target/waitstatus.h (enum target_stop_reason)
	<TARGET_STOPPED_BY_SINGLE_STEP>: New value.

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

	* linux-low.c (handle_extended_wait): Set the fork child's suspend
	count if stopping and suspending threads.
	(check_stopped_by_breakpoint): If stopped by trace, set the LWP's
	stop reason to TARGET_STOPPED_BY_SINGLE_STEP.
	(linux_detach): Complete an ongoing step-over.
	(lwp_suspended_inc, lwp_suspended_decr): New functions.  Use
	throughout.
	(resume_stopped_resumed_lwps): Don't resume a suspended thread.
	(linux_wait_1): If passing a signal to the inferior after
	finishing a step-over, unsuspend and re-resume all lwps.  If we
	see a single-step event but the thread should be continuing, don't
	pass the trap to gdb.
	(stuck_in_jump_pad_callback, move_out_of_jump_pad_callback): Use
	internal_error instead of gdb_assert.
	(enqueue_pending_signal): New function.
	(check_ptrace_stopped_lwp_gone): Add debug output.
	(start_step_over): Use internal_error instead of gdb_assert.
	(complete_ongoing_step_over): New function.
	(linux_resume_one_thread): Don't resume a suspended thread.
	(proceed_one_lwp): If the LWP is stepping over a breakpoint, reset
	it stepping.

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

	* gdb.threads/forking-threads-plus-breakpoint.exp: New file.
	* gdb.threads/forking-threads-plus-breakpoint.c: New file.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] signal_command: Leftover cleanup chain regression
@ 2015-08-04 12:22 sergiodj+buildbot
  2015-08-04 20:40 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ 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] 1132+ messages in thread
* [binutils-gdb] Complete the previous commit (block_found refactoring)
@ 2015-08-02 18:22 sergiodj+buildbot
  2015-08-03 19:00 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ 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] 1132+ messages in thread
* [binutils-gdb] Replace the block_found global with explicit data-flow
@ 2015-08-01  9:01 sergiodj+buildbot
  2015-08-03 16:56 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ 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] 1132+ 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-03 16:13 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ 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] 1132+ messages in thread
* [binutils-gdb] Fix m32r_remove_watchpoint parameter type
@ 2015-07-31 18:24 sergiodj+buildbot
  2015-08-03 14:08 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ 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] 1132+ messages in thread
* [binutils-gdb] Mostly trivial enum fixes
@ 2015-07-31 17:25 sergiodj+buildbot
  2015-08-03 12:04 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ 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] 1132+ messages in thread
* [binutils-gdb] Move ARM register numbers enum to arch/arm.h
@ 2015-07-30 14:17 sergiodj+buildbot
  2015-08-02 13:11 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-07-30 14:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ec74129274bf2fb65aac9381a19731c570f7be29 ***

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

Move ARM register numbers enum to arch/arm.h
This patch moves ARM register numbers enum to arch/arm.h, so that it
can used by GDBserver too.

This patch also creates a new directory gdb/arch in which arch-specific
or target-specific files are placed.

gdb:

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

	* arm-tdep.h (enum gdb_regnum): Move it to ...
	* arch/arm.h: ... here.  New file.
	* Makefile.in (HFILES_NO_SRCDIR): Add arch/arm.h.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [AArch64] Rename boolean arguments in decoding functions
@ 2015-07-30 11:50 sergiodj+buildbot
  2015-08-02 10:02 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ 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] 1132+ messages in thread
* [binutils-gdb] Make gdb.base/multi-forks.exp work with the native-extended-gdbserver board
@ 2015-07-30  1:24 sergiodj+buildbot
  2015-08-01 17:55 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-07-30  1:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1eef6428112a1c1fe0295f36f92d7a3cf9908228 ***

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

Make gdb.base/multi-forks.exp work with the native-extended-gdbserver board
Now that we can expect inferior output with the gdbserver boards, this
is all it takes to have the test pass against extended-remote
gdbserver.

Don Breazeal originally wrong something like this:

 https://sourceware.org/ml/gdb-patches/2015-03/msg00506.html

which was what originally inspired the introduction of
$inferior_spawn_id.

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

	* gdb.base/multi-forks.exp (continue_to_exit_bp_loc): Expect
	output from both inferior_spawn_id and gdb_spawn_id.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Make gdb.base/shlib-call.exp use gdb_test_stdio
@ 2015-07-29 18:08 sergiodj+buildbot
  2015-07-31 21:22 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-07-29 18:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 39413b296f9eb92ae3936bf29397ac1d35ca803b ***

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

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

	* gdb.base/shlib-call.exp: Use gdb_test_stdio.


^ permalink raw reply	[flat|nested] 1132+ 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-31  8:53 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ 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] 1132+ 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-30 21:16 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ 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] 1132+ 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 23:15 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ 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] 1132+ messages in thread
* [binutils-gdb] Uniquify test names from gdb.python/{py-objfile.exp, py-pp-registration.exp}
@ 2015-07-28 21:47 sergiodj+buildbot
  2015-07-29 21:05 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ 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] 1132+ messages in thread
* [binutils-gdb] Consider addressable memory unit size in various value functions
@ 2015-07-28 16:24 sergiodj+buildbot
  2015-07-29 18:53 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ 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] 1132+ messages in thread
* [binutils-gdb] Factor out pointer printing code from generic_val_print
@ 2015-07-27 19:36 sergiodj+buildbot
  2015-07-28 10:37 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ 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] 1132+ 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 22:11 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ 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] 1132+ messages in thread
* [binutils-gdb] Remove REMOTE_EXAMPLES from gdb/Makefile.in
@ 2015-07-27 16:26 sergiodj+buildbot
  2015-07-27 20:58 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ 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] 1132+ messages in thread
* [binutils-gdb] Regenerate configure files
@ 2015-07-27 15:58 sergiodj+buildbot
  2015-07-27 19:55 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ 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] 1132+ 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:18 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ 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] 1132+ messages in thread
* [binutils-gdb] Add gmonster-{1,2} perf testcases.
@ 2015-07-25  1:28 sergiodj+buildbot
  2015-07-25 21:34 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ 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] 1132+ messages in thread
* [binutils-gdb] Add perf testcase generator.
@ 2015-07-25  1:05 sergiodj+buildbot
  2015-07-25 19:59 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ 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] 1132+ messages in thread
* [binutils-gdb] PerfTest::assemble functions return results.
@ 2015-07-25  0:40 sergiodj+buildbot
  2015-07-25 18:03 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ 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] 1132+ messages in thread
* [binutils-gdb] lib/gdb.exp (clean_restart): Make executable optional.
@ 2015-07-25  0:14 sergiodj+buildbot
  2015-07-25 16:26 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ 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] 1132+ messages in thread
* [binutils-gdb] Clean up testsuite compiler_info support.
@ 2015-07-24 23:49 sergiodj+buildbot
  2015-07-25 14:48 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ 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] 1132+ messages in thread
* [binutils-gdb] Add parallel build support for perf tests.
@ 2015-07-24 23:25 sergiodj+buildbot
  2015-07-25 13:13 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ 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] 1132+ messages in thread
* [binutils-gdb] bfd_get_section_by_name_if hash chain traversal
@ 2015-07-24  6:05 sergiodj+buildbot
  2015-07-24  7:26 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ 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] 1132+ messages in thread
* [binutils-gdb] Fix ppc64 ELFv1 assertion failure
@ 2015-07-22 10:11 sergiodj+buildbot
  2015-07-22 12:07 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ 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] 1132+ messages in thread
* [binutils-gdb] Make binutils abort message GDB friendly
@ 2015-07-20 13:07 sergiodj+buildbot
  2015-07-20 20:23 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ 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] 1132+ messages in thread
* [binutils-gdb] dwarf2read: Allow SEC_ALLOC sections to be located at address 0.
@ 2015-07-18 17:30 sergiodj+buildbot
  2015-07-18 19:09 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ 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] 1132+ messages in thread
* [binutils-gdb] Use debug_printf to print debug message
@ 2015-07-17 14:32 sergiodj+buildbot
  2015-07-17 20:58 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ 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] 1132+ messages in thread
* [binutils-gdb] Fix using uninitialised values
@ 2015-07-17 11:35 sergiodj+buildbot
  2015-07-17 12:56 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ 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] 1132+ messages in thread
* [binutils-gdb] [AArch64][1/3] Add R_AARCH64_P32_TLSLD_ADR_PREL21 in elf header
@ 2015-07-16 15:06 sergiodj+buildbot
  2015-07-16 17:15 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-07-16 15:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 53e8fd0f07cec1eb36149a64e4ed45923967453c ***

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

[AArch64][1/3] Add R_AARCH64_P32_TLSLD_ADR_PREL21 in elf header


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Unbreak nios2-*-linux* GDB testing.
@ 2015-07-15 15:43 sergiodj+buildbot
  2015-07-15 23:41 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-07-15 15:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 03346981fe6c11ab63b54a8d1919d6357e659684 ***

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

Unbreak nios2-*-linux* GDB testing.
2015-07-15  Sandra Loosemore  <sandra@codesourcery.com>

	gdb/testsuite/
	* gdb.base/sigaltstack.exp (finish_test): Add kfail for
	nios2-*-linux*.
	* gdb.base/sigbpt.exp (stepi_out): Likewise.
	* gdb.base/siginfo.exp: Likewise.
	* gdb.base/sigstep.exp (advance, advancei): Likewise.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Remove CHECK_TYPEDEF, use check_typedef instead
@ 2015-07-14 21:08 sergiodj+buildbot
  2015-07-15 16:35 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ 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] 1132+ messages in thread
* [binutils-gdb] Add support reading D modules from DWARF
@ 2015-07-14 19:13 sergiodj+buildbot
  2015-07-15 14:33 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ 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] 1132+ messages in thread
* [binutils-gdb] gdbserver/Linux: internal error when killing a process that is already gone
@ 2015-07-14 10:02 sergiodj+buildbot
  2015-07-14 11:03 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-07-14 10:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 586b02a96f744497c8921a558f1c386287849ab0 ***

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

gdbserver/Linux: internal error when killing a process that is already gone
If the process disappears (e.g., killed with "kill -9" from the shell)
while it was stopped under GDBserver's control, and the GDBserver
tries to kill it, GDBserver asserts:

 (gdb) shell kill -9 23084
 (gdb) kill
 ...
 Killing process(es): 23084
 /home/pedro/gdb/mygit/src/gdb/gdbserver/linux-low.c:972: A problem internal to GDBserver has been detected.
 kill_wait_lwp: Assertion `res > 0' failed.
 ...

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

	* linux-low.c (kill_wait_lwp): Don't assert if waitpid fails.
	Instead, ignore ECHILD, and throw an error for other errnos.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [GDBserver][AArch64] Cleanup comments for each linux_target_ops method
@ 2015-07-10 13:09 sergiodj+buildbot
  2015-07-11 11:48 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-07-10 13:09 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 421530db90312b605ce05d7cf883123a084f9af3 ***

Author: Pierre Langlois <pierre.langlois@arm.com>
Branch: master
Commit: 421530db90312b605ce05d7cf883123a084f9af3

[GDBserver][AArch64] Cleanup comments for each linux_target_ops method
This patch cleans up the comments for each linux_target_ops methods.  We
should mention which method each function implements but there is no
need to duplicate information already mentionned in the base target_ops
or linux_target_ops definitions.

gdb/gdbserver/ChangeLog:

	* linux-aarch64-low.c: Add comments for each linux_target_ops
	method.  Remove comments already covered in target_ops and
	linux_target_ops definitions.
	(the_low_target): Add comments for each unimplemented method.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] gdb/tui: Define tui window names once.
@ 2015-07-10 12:19 sergiodj+buildbot
  2015-07-11  8:55 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-07-10 12:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 150375dc7ac877d1dc6e8aaf73a23479b720306c ***

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

gdb/tui: Define tui window names once.
Don't duplicate the window names inside the completion function.
Instead make use of the existing defines, and the tui_win_name function
to obtain the window names.

gdb/ChangeLog:

	* tui/tui-win.c (focus_completer): Don't duplicate the tui window
	names in this function.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] record: set stop_pc in "record goto" command
@ 2015-07-10  7:25 sergiodj+buildbot
  2015-07-11  5:59 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-07-10  7:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 485668e5b3987456b44588c1f2fd8a0723909866 ***

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

record: set stop_pc in "record goto" command
When navigating in the recorded execution trace via "record goto", we do not
set stop_pc.  This may trigger an internal error in infrun.c when stepping
from that location.  Set it.

(gdb) rec full
(gdb) c
Continuing.

Breakpoint 1, foo (void) at foo.c:42
42             x = y
(gdb) rn
foo (void)
    at foo.c:41
41             y = x
(gdb) rec go end
Go forward to insn number 98724
    at foo.c:42
42             x = y
(gdb) n
infrun.c:2382: internal-error: resume: Assertion `sig != GDB_SIGNAL_0' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n)

This happens because there's a breakpoint at PC when the "next"
is issued, so that breapoint should be immediately stepped over.
That should have been detected/done by proceed, here:

  if (addr == (CORE_ADDR) -1)
    {
      if (pc == stop_pc
	  && breakpoint_here_p (aspace, pc) == ordinary_breakpoint_here
	  && execution_direction != EXEC_REVERSE)
	/* There is a breakpoint at the address we will resume at,
	   step one instruction before inserting breakpoints so that
	   we do not stop right away (and report a second hit at this
	   breakpoint).

	   Note, we don't do this in reverse, because we won't
	   actually be executing the breakpoint insn anyway.
	   We'll be (un-)executing the previous instruction.  */
	tp->stepping_over_breakpoint = 1;

But since stop_pc was stale, the pc == stop_pc check failed, and left the
breakpont at PC inserted.

gdb/
	* record-btrace.c (record_btrace_goto_begin, record_btrace_goto_end)
	record_btrace_goto): Move call to print_stack_frame ...
	(record_btrace_set_replay): ... here.  Set stop_pc.
	* record-full.c (record_full_goto_entry): Set stop_pc.

testsuite/
	* gdb.btrace/record_goto-step.exp: New.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [AArch64] Only access inferior registers when creating a frame cache
@ 2015-07-09 19:28 sergiodj+buildbot
  2015-07-10 14:33 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-07-09 19:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT db634143224dc7cb985d996bed15257f5cb86b25 ***

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

[AArch64] Only access inferior registers when creating a frame cache
This patch moves the address of the start of a function (func) and the
address from which it was called (prev_pc) into aarch64_prologue_cache.
The idea is to keep accesses to the inferior's registers into
aarch64_make_prologue_cache and aarch64_make_stub_cache.

gdb/ChangeLog:

	* aarch64-tdep.c (aarch64_prologue_cache) <func, prev_pc>: New
	fields.
	(aarch64_scan_prologue): Set prev_pc.
	(aarch64_make_prologue_cache): Set func.
	(aarch64_make_stub_cache): Set prev_pc.
	(aarch64_prologue_this_id): Remove local variables id, pc and
	func.  Read prev_pc and func from cache.
	(aarch64_stub_this_id): Read prev_pc from cache.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Factor out memberptr printing code from c_val_print
@ 2015-07-09 18:08 sergiodj+buildbot
  2015-07-10  9:08 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-07-09 18:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 938c69a11897acea85275b93b5bb376b589564fa ***

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

Factor out memberptr printing code from c_val_print
gdb/ChangeLog:

	* c-valprint.c (c_val_print): Factor out memberptr printing code
	from c_val_print to ...
	(c_val_print_memberptr): ... this new function.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Factor out array printing code from c_val_print
@ 2015-07-09 16:47 sergiodj+buildbot
  2015-07-09 20:16 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-07-09 16:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0b6ef777bd0b7918590da1bdbeab1ca97d753ba2 ***

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

Factor out array printing code from c_val_print
gdb/ChangeLog:

	* c-valprint.c (c_valprint): Factor our array printing code from
	c_val_print to ...
	(c_val_print_array): ... this new function.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] 2015-07-09  Catherine Moore  <clm@codesourcery.com>
@ 2015-07-09 15:28 sergiodj+buildbot
  2015-07-09 16:30 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-07-09 15:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT de231f2015ec537df22c60822c9adb1f2205c13e ***

Author: Catherine Moore <clm@codesourcery.com>
Branch: master
Commit: de231f2015ec537df22c60822c9adb1f2205c13e

2015-07-09  Catherine Moore  <clm@codesourcery.com>
        * elflink.c (bfd_elf_size_dynamic_sections): Call to
        _bfd_elf_maybe_strip_eh_frame_hdr should be before
        bed->elf_backend_size_dynamic_sections.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] btrace: fix build fail with 32-bit BFD
@ 2015-07-09  6:23 sergiodj+buildbot
  2015-07-09  7:23 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-07-09  6:23 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 80a2b330f7e719cd851242d6f976719586fb9295 ***

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

btrace: fix build fail with 32-bit BFD
When compiling GDB with 32-bit BFD, the build fails with:

In file included from btrace.h:33:0,
                 from btrace.c:23:
/usr/include/intel-pt.h:1643:51: note: expected 'int (*)(uint8_t *, size_t,
 const struct pt_asid *, uint64_t, void *)' but argument is of type 'int
 (*)(gdb_byte *, size_t, const struct pt_asid *, CORE_ADDR, void *)' extern
 pt_export int pt_image_set_callback(struct pt_image *image, ^

gdb/
	* btrace.c (btrace_pt_readmem_callback): Change type of PC argument.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Delete program spaces directly when removing inferiors
@ 2015-07-08 15:32 sergiodj+buildbot
  2015-07-08 15:54 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-07-08 15:32 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0560c645c02eba2828a053039dcfdf676cdd1d00 ***

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

Delete program spaces directly when removing inferiors
When deleting an inferior, delete the associated program space as well
if it becomes unused. This replaces the "pruning" approach, with which
you could forget to call prune_program_spaces (as seen, with the
-remove-inferior command, see [1]).

This allows to remove the prune_program_spaces function. At the same
time, I was able to clean up the delete_inferior* family.
delete_inferior_silent and delete_inferior were unused, which allowed
renaming delete_inferior_1 to delete_inferior. Also, since all calls to
it were with silent=1, I removed that parameter completely.

I renamed pspace_empty_p to program_space_empty_p. I prefer if the
"exported" functions have a more explicit and standard name.

Tested on Ubuntu 14.10.

This obsoletes my previous patch "Add call to prune_program_spaces in
mi_cmd_remove_inferior" [1].

[1] https://sourceware.org/ml/gdb-patches/2014-09/msg00717.html

gdb/Changelog:

	* inferior.c (delete_inferior_1): Rename to ...
	(delete_inferior): ..., remove 'silent' parameter, delete
	program space when unused and remove call to prune_program_spaces.
	Remove the old, unused, delete_inferior.
	(delete_inferior_silent): Remove.
	(prune_inferiors): Change call from delete_inferior_1 to
	delete_inferior and remove 'silent' parameter. Remove call to
	prune_program_spaces.
	(remove_inferior_command): Idem.
	* inferior.h (delete_inferior_1): Rename to...
	(delete_inferior): ..., remove 'silent' parameter and remove the
	original delete_inferior.
	(delete_inferior_silent): Remove.
	* mi/mi-main.c (mi_cmd_remove_inferior): Change call from
	delete_inferior_1 to delete_inferior and remove 'silent'
	parameter.
	* progspace.c (prune_program_spaces): Remove.
	(pspace_empty_p): Rename to...
	(program_space_empty_p): ... and make non-static.
	(delete_program_space): New.
	* progspace.h (prune_program_spaces): Remove declaration.
	(program_space_empty_p): New declaration.
	(delete_program_space): New declaration.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] add myself to write-after-approval list
@ 2015-07-08  8:40 sergiodj+buildbot
  2015-07-08 10:35 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-07-08  8:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e8643a4533a92e011dad97ea53c99d314c06513d ***

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

add myself to write-after-approval list
gdb/
	* MAINTAINERS (Write After Approval): Add Markus T. Metzger.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
[parent not found: <a844296a982bdff7c14dab355de0fca75486add6@kwanyin>]
[parent not found: <0561fea48c107b271308a013c485c29cbd5c13b5@kwanyin>]
[parent not found: <9be54cae43929ab989fcd44dfcf8d3313a55f7a0@kwanyin>]
[parent not found: <58bfce93438e1f936d4547bb9659b7d096e2823f@kwanyin>]
[parent not found: <e62803699d1a722460e8aaa63ef5c99f5580761a@kwanyin>]
[parent not found: <dfc87947b5ac6d6382c225449d4fdce411c7ee66@kwanyin>]
[parent not found: <b5fca6d7284b2cd2e90efc556eb6a29a1b177476@kwanyin>]
[parent not found: <a2efc14b81515aebd2b7e1f47fe4768e432493a9@kwanyin>]
* [binutils-gdb] Do not skip prologue for asm (.S) files
@ 2015-06-26 13:34 sergiodj+buildbot
  2015-06-26 15:53 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-06-26 13:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6e22494e5076e4d3c0b2c2785883162f83db499e ***

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

Do not skip prologue for asm (.S) files
GDB tries to skip prologue for .S files according to .debug_line but it then
places the breakpoint to a location where it is never hit.

This is because #defines in .S files cause prologue skipping which is
completely inappropriate, for s390x:

glibc/sysdeps/unix/syscall-template.S
78:/* This is a "normal" system call stub: if there is an error,
79:   it returns -1 and sets errno.  */
80:
81:T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
82:     ret

00000000000f4210 T __select
 Line Number Statements:
  Extended opcode 2: set Address to 0xf41c8
  Advance Line by 80 to 81
  Copy
  Advance PC by 102 to 0xf422e
  Special opcode 6: advance Address by 0 to 0xf422e and Line by 1 to 82
  Special opcode 34: advance Address by 2 to 0xf4230 and Line by 1 to 83
  Advance PC by 38 to 0xf4256
  Extended opcode 1: End of Sequence
  Compilation Unit @ offset 0x28b3e0:
 <0><28b3eb>: Abbrev Number: 1 (DW_TAG_compile_unit)
    <28b3ec>   DW_AT_stmt_list   : 0x7b439
    <28b3f0>   DW_AT_low_pc	 : 0xf41c8
    <28b3f8>   DW_AT_high_pc     : 0xf4256
    <28b400>   DW_AT_name        : ../sysdeps/unix/syscall-template.S
    <28b423>   DW_AT_comp_dir    : /usr/src/debug////////glibc-2.17-c758a686/misc
    <28b452>   DW_AT_producer    : GNU AS 2.23.52.0.1
    <28b465>   DW_AT_language    : 32769        (MIPS assembler)

without debuginfo or with debuginfo and the fix - correct address:
(gdb) b select
Breakpoint 1 at 0xf4210

It is also where .dynsym+.symtab point to:
00000000000f4210 T __select
00000000000f4210 W select

with debuginfo, without the fix:
(gdb) b select
Breakpoint 1 at 0xf41c8: file ../sysdeps/unix/syscall-template.S, line 81.

One part is to behave for asm files similar way like for 'locations_valid':
  /* Symtab has been compiled with both optimizations and debug info so that
     GDB may stop skipping prologues as variables locations are valid already
     at function entry points.  */
  unsigned int locations_valid : 1;

The other part is to extend the 'locations_valid'-like functionality more.

Both minsym_found and find_function_start_sal need to be patched, otherwise
their addresses do not match and GDB regresses on ppc64:

gdb/ChangeLog
2015-06-26  Jan Kratochvil  <jan.kratochvil@redhat.com>

	* linespec.c (minsym_found): Reset sal.PC for COMPUNIT_LOCATIONS_VALID
	and language_asm..
	* symtab.c (find_function_start_sal): Likewise.

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

	* gdb.arch/amd64-prologue-skip.S: New file.
	* gdb.arch/amd64-prologue-skip.exp: New file.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Don't set sh_size for .shstrtab twice
@ 2015-06-25 20:28 sergiodj+buildbot
  2015-06-26  0:22 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-06-25 20:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 946748d5ed1d218adfccd523be9fdf280adfe434 ***

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

Don't set sh_size for .shstrtab twice
_bfd_elf_assign_file_positions_for_non_load will set the sh_size
field for .shstrtab section.  There is need to initialize it in
_bfd_elf_compute_section_file_positions.

	* elf.c (_bfd_elf_compute_section_file_positions): Don't
	initialize sh_size for .shstrtab here.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Sync libiberty from GCC, replaying updates to configure scripts
@ 2015-06-24 20:10 sergiodj+buildbot
  2015-06-25  9:59 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-06-24 20:10 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f91ca6bc00c1e3c70c1d2f4527d4297b76e2eaca ***

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

Sync libiberty from GCC, replaying updates to configure scripts


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] gdb: sim: merge the sysroot update logic together
@ 2015-06-24 15:57 sergiodj+buildbot
  2015-06-24 20:30 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-06-24 15:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 87d1b30944783ae0efb49236c6d872d775a37417 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 87d1b30944783ae0efb49236c6d872d775a37417

gdb: sim: merge the sysroot update logic together
Initialize the local sysroot fully before we start using it.
This keeps it all a bit simpler.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Call set_gdbarch_get_siginfo_type in linux_init_abi
@ 2015-06-24 14:45 sergiodj+buildbot
  2015-06-24 17:08 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-06-24 14:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5cd867b414fe3609dbf596c373343474132775a8 ***

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

Call set_gdbarch_get_siginfo_type in linux_init_abi
linux_get_siginfo_type is installed to many linux gdbarch.  This patch
is to move this to a common area linux-tdep.c:linux_init_abi, so that
linux_get_siginfo_type is installed to every linux gdbarch.  If some
linux gdbarch needs its own version, please override it in
$ARCH_linux_init_abi.  In the testsuite, we enable siginfo related
tests for all linux targets.

gdb:

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

	* aarch64-linux-tdep.c (aarch64_linux_init_abi): Don't call
	set_gdbarch_get_siginfo_type.
	* amd64-linux-tdep.c (amd64_linux_init_abi_common): Likewise.
	* arm-linux-tdep.c (arm_linux_init_abi): Likewise.
	* i386-linux-tdep.c (i386_linux_init_abi): Likewise.
	* m68klinux-tdep.c (m68k_linux_init_abi): Likewise.
	* ppc-linux-tdep.c (ppc_linux_init_abi): Likewise.
	* s390-linux-tdep.c (s390_gdbarch_init): Likewise.
	* tilegx-linux-tdep.c (tilegx_linux_init_abi): Likewise.
	* linux-tdep.c (linux_get_siginfo_type): Change it to static.
	(linux_init_abi): Call set_gdbarch_get_siginfo_type.
	* linux-tdep.h (linux_get_siginfo_type): Remove the declaration.

gdb/testsuite:

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

	* lib/gdb.exp (supports_get_siginfo_type): Return 1 for all
	linux targets.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Fix GDBHISTSIZE test failure on i686
@ 2015-06-23 22:27 sergiodj+buildbot
  2015-06-24  8:55 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-06-23 22:27 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0fc26cafacfff9f53d898bb73495b384b80d6d31 ***

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

Fix GDBHISTSIZE test failure on i686
The test

  test_histsize_history_setting "99999999999999999999999999999999999" "unlimited"

was failing on i686 because the condition in init_history() for
determining whether to map a large GDBHISTSIZE value to infinity was

  long var = strtol (tmpenv);
  if (var > INT_MAX)
    history_size = unlimited;

but this condition is never true on i686 because INT_MAX == LONG_MAX.
So in order to properly map large out-of-range values of GDBHISTSIZE to
infinity on targets where LONG_MAX > INT_MAX as well as on i686, we have
to instead change the above condition to

  if (var > INT_MAX
      || (var == INT_MAX && errno == ERANGE))
    history_size = unlimited;

gdb/ChangeLog:

	* top.c (init_history): Look at errno after calling strtol to
	properly map large GDBHISTSIZE values to infinity.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] sim: trace: do not enable internal debug by default
@ 2015-06-23 20:03 sergiodj+buildbot
  2015-06-23 22:27 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-06-23 20:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4953dc20941a48eed02b575cec29d8de419f87eb ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 4953dc20941a48eed02b575cec29d8de419f87eb

sim: trace: do not enable internal debug by default
Since --trace-debug is for people hacking on the sim sources rather than
people just using the sim, default it to off.  This matches the behavior
of other debug knobs we have.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Convert have_ptrace_getregset to a tri-state boolean
@ 2015-06-23 13:26 sergiodj+buildbot
  2015-06-23 15:12 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-06-23 13:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0bdb2f78497a1b3be65d1428cc02f7d4e1d3a888 ***

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

Convert have_ptrace_getregset to a tri-state boolean
have_ptrace_getregset is a tri-state variable (-1, 0, 1), and we have
some conditions like "if (have_ptrace_getregset)", which is not correct.
I'll explain why it is not correct in the following example.  This fix
to this problem to replace the test (have_ptrace_getregset) to test
(have_ptrace_getregset == 1) or (have_ptrace_getregset == -1) etc.
However Doug thinks it hinders readability
https://sourceware.org/ml/gdb-patches/2015-05/msg00692.html so I decide
to add a new enum tribool and change have_ptrace_getregset to it, in
order to make these tests more readable.

have_ptrace_getregset is initialised to -1, and is adjusted to 0 or 1 in
$ARCH_linux_read_description according to the capability of the kernel.
However, it is possible that have_ptrace_getregset is used before it is
set to 0 or 1, which means it is still -1.  This is shown below.

(gdb) run
Starting program: gdb/testsuite/gdb.base/break

Breakpoint 2, amd64_linux_fetch_inferior_registers (ops=0xceaa80, regcache=0xe72000, regnum=16) at git/gdb/amd64-linux-nat.c:128
128	{
top?p have_ptrace_getregset
$1 = TRIBOOL_UNKNOWN
top?c
Continuing.

Breakpoint 2, amd64_linux_fetch_inferior_registers (ops=0xceaa80, regcache=0xe72000, regnum=16) at git/gdb/amd64-linux-nat.c:128
128	{
top?c
Continuing.

Breakpoint 1, x86_linux_read_description (ops=0xceaa80) at git/gdb/x86-linux-nat.c:117
117	{

PTRACE_GETREGSET command is used even GDB doesn't know whether
PTRACE_GETREGSET is supported or not.  It is wrong, but works on x86.
However it doesn't work on arm-linux if the kernel doesn't support
PTRACE_GETREGSET at all.  We'll get:

(gdb) run
Starting program: gdb/testsuite/gdb.base/break
warning: Unable to fetch general register.
PC register is not available

gdb:

2015-06-23  Yao Qi  <yao.qi@linaro.org>

	* amd64-linux-nat.c (amd64_linux_fetch_inferior_registers):
	Check whether have_ptrace_getregset is TRIBOOL_TRUE explicitly.
	(amd64_linux_store_inferior_registers): Likewise.
	* arm-linux-nat.c (fetch_fpregister): Likewise.
	(fetch_fpregs, store_fpregister): Likewise.
	(store_fpregister, store_fpregs): Likewise.
	(fetch_register, fetch_regs): Likewise.
	(store_register, store_regs): Likewise.
	(fetch_vfp_regs, store_vfp_regs): Likewise.
	(arm_linux_read_description): Check have_ptrace_getregset is
	TRIBOOL_UNKNOWN.  Set have_ptrace_getregset to TRIBOOL_TRUE
	or TRIBOOL_FALSE.
	* i386-linux-nat.c (fetch_xstateregs): Check
	have_ptrace_getregset is not TRIBOOL_TRUE.
	(store_xstateregs): Likewise.
	* linux-nat.c (have_ptrace_getregset): Change its type to
	enum tribool.
	* linux-nat.h (tribool): New enum.
	* x86-linux-nat.c (x86_linux_read_description): Use enum tribool.
	Check whether have_ptrace_getregset is TRIBOOL_TRUE.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Don't use $< in Makefiles
@ 2015-06-21  4:20 sergiodj+buildbot
  2015-06-21 17:56 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-06-21  4:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 02db4b0a9f80505adaef9f547e8c069adfe63e36 ***

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

Don't use $< in Makefiles
$< is a GNU make feature.

	* Makefile.am: Expand $<.
	* Makefile.in: Regenerate.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Test the interaction between GDBHISTSIZE and .gdbinit
@ 2015-06-18 17:01 sergiodj+buildbot
  2015-06-18 18:53 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-06-18 17:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 74bd41ce65c6c2c30ff67519bfc1d00b61826d96 ***

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

Test the interaction between GDBHISTSIZE and .gdbinit
The value inside the GDBHISTSIZE environment variable, only if valid,
should override setting the history size through one's .gdbinit file.

gdb/testsuite/ChangeLog:

	* gdb.base/gdbinit-history.exp: Test the interaction between
	setting GDBHISTSIZE and setting the history size via .gdbinit.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Fix problems with finishing a dummy function call on simulators.
@ 2015-06-18  0:11 sergiodj+buildbot
  2015-06-18 11:45 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-06-18  0:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6ae8866180bf90e9ec76c2dd34c07fd826d11a83 ***

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

Fix problems with finishing a dummy function call on simulators.
Some simulators don't handle permanent breakpoints properly and will
sometimes terminate when hitting such a breakpoint instruction or have
unwanted effects.

When a permanent breakpoint is inserted, GDB will not attempt to insert
other breakpoint locations on top of it, leading to the problem described
above.

By not marking permanent breakpoint locations as inserted, we allow the
insertion of breakpoint locations on top of the permanent ones, preventing
the simulators from running into that situation.

gdb/ChangeLog:

2015-06-17  Luis Machado  <lgustavo@codesourcery.com>

	* breakpoint.c (add_location_to_breakpoint): Don't mark permanent
	locations as inserted.
	Update and expand comment about permanent locations.
	(bp_loc_is_permanent): Don't return 0 for bp_call_dummy.
	Move comment to add_location_to_breakpoint.
	(update_global_location_list): Don't error out if a permanent
	breakpoint is not marked inserted.
	Don't error out if a non-permanent breakpoint location is inserted on
	top of a permanent breakpoint.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Add vector ABI tests to gnu_vector.exp
@ 2015-06-17  9:39 sergiodj+buildbot
  2015-06-17 10:53 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-06-17  9:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e6c693af14c0488998a784d560b8cfbcf15db99a ***

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

Add vector ABI tests to gnu_vector.exp
So far the gnu_vector test was limited to "static" aspects of GDB's
vector support, like evaluating vector-valued expressions.  This patch
enriches the test and adds checks for GDB's vector ABI support as well.
The new checks particularly verify inferior function calls with vector
arguments and GDB's handling of vector return values.

The test now attempts to compile for the target's "native" architecture,
such that a hardware vector ABI is used if available.

Since GDB has no vector ABI support for x86 and x86_64 targets, most of
the new checks are KFAILed there.

gdb/testsuite/ChangeLog:

	* gdb.base/gnu_vector.c: Include stdarg.h and stdio.h.
	(VECTOR): New macro.  Use it...
	(int4, uint4, char4, float4, int2, longlong2, float2, double2):
	...for these typedefs.
	(int8, char1, int1, double1): New typedefs.
	(struct just_int2, struct two_int2): New structures.
	(add_some_intvecs, add_many_charvecs, add_various_floatvecs)
	(add_structvecs, add_singlevecs): New functions.
	(main): Call add_some_intvecs twice.
	* gdb.base/gnu_vector.exp: Drop GCC version check; just attempt
	the compile and exit upon failure.  Try compiling for the "native"
	architecture.  Test inferior function calls with vector arguments
	and vector return value handling with "finish" and "return".


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Fix build when size_t is not available in bfd-in2.h
@ 2015-06-16 13:55 sergiodj+buildbot
  2015-06-16 16:23 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-06-16 13:55 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 56f4083249f4633084d4e8d89fc065e895f874cf ***

Author: Jon Turney <jon.turney@dronecode.org.uk>
Branch: master
Commit: 56f4083249f4633084d4e8d89fc065e895f874cf

Fix build when size_t is not available in bfd-in2.h
bfd/ChangeLog:

2015-06-15  Jon Turney  <jon.turney@dronecode.org.uk>

	* bfd.c: Change struct bfd_build_id to use bfd_size_type.
	* bfd-in2.h : Regenerate.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Fix compilation of gdb/arm-linux-nat.c on Raspbian GNU/Linux 7
@ 2015-06-16  9:49 sergiodj+buildbot
  2015-06-16 12:56 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-06-16  9:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 95855ca82ec3ced28916922d663106e61ce593b4 ***

Author: Martin Simmons <martin@lispworks.com>
Branch: master
Commit: 95855ca82ec3ced28916922d663106e61ce593b4

Fix compilation of gdb/arm-linux-nat.c on Raspbian GNU/Linux 7
GDB trunk fails to compile on Raspbian GNU/Linux 7 because
PTRACE_GETREGSET and PTRACE_SETREGSET are not defined in sys/ptrace.h.

gcc -g -O2   -I. -I. -I./common -I./config -DLOCALEDIR="\"/usr/local/share/locale\"" -DHAVE_CONFIG_H -I./../include/opcode -I./../opcodes/.. -I./../readline/.. -I./../zlib -I../bfd -I./../bfd -I./../include -I../libdecnumber -I./../libdecnumber  -I./gnulib/import -Ibuild-gnulib/import   -DTUI=1  -Wall -Wpointer-arith -Wno-unused -Wunused-value -Wunused-function -Wno-switch -Wno-char-subscripts -Wempty-body -Wpointer-sign -Wmissing-prototypes -Wdeclaration-after-statement -Wmissing-parameter-type -Wold-style-declaration -Wold-style-definition -Wformat-nonliteral -Werror -c -o arm-linux-nat.o -MT arm-linux-nat.o -MMD -MP -MF .deps/arm-linux-nat.Tpo arm-linux-nat.c
arm-linux-nat.c: In function 'fetch_fpregister':
arm-linux-nat.c:103:21: error: 'PTRACE_GETREGSET' undeclared (first use in this function)
arm-linux-nat.c:103:21: note: each undeclared identifier is reported only once for each function it appears in
arm-linux-nat.c: In function 'fetch_fpregs':
arm-linux-nat.c:144:21: error: 'PTRACE_GETREGSET' undeclared (first use in this function)
arm-linux-nat.c: In function 'store_fpregister':
arm-linux-nat.c:184:21: error: 'PTRACE_GETREGSET' undeclared (first use in this function)
arm-linux-nat.c:211:21: error: 'PTRACE_SETREGSET' undeclared (first use in this function)
...

This patch includes the gdb header file nat/linux-ptrace.h, which provides
fallback definitions.

2015-06-16  Martin Simmons  <martin@lispworks.com>  (tiny patch)

	* arm-linux-nat.c: Include nat/linux-ptrace.h.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Merge multiple hex conversions
@ 2015-06-15 16:18 sergiodj+buildbot
  2015-06-15 20:11 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-06-15 16:18 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 909c2cdaa78f5c33ce61a3b47e86f831025d0a02 ***

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

Merge multiple hex conversions
gdb/ChangeLog
2015-06-15  Aleksandar Ristovski  <aristovski@qnx.com
	    Jan Kratochvil  <jan.kratochvil@redhat.com>

	Merge multiple hex conversions.
	* monitor.c: Include rsp-low.h.
	(fromhex): Remove definition.

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

	Merge multiple hex conversions.
	* gdbreplay.c (tohex): Rename to 'fromhex'.
	(logchar): Use fromhex.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] windows-nat: Replace __COPY_CONTEXT_SIZE conditional with __CYGWIN__
@ 2015-06-15 11:29 sergiodj+buildbot
  2015-06-15 13:23 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-06-15 11:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f20c58f51f5735d1ba49efadc86b3ec67631410e ***

Author: Jon Turney <jon.turney@dronecode.org.uk>
Branch: master
Commit: f20c58f51f5735d1ba49efadc86b3ec67631410e

windows-nat: Replace __COPY_CONTEXT_SIZE conditional with __CYGWIN__
Replace __COPY_CONTEXT_SIZE conditional with __CYGWIN__

__COPY_CONTEXT_SIZE was added to Cygwin's headers in 2006.

Versions of Cygwin which don't define __COPY_CONTEXT_SIZE are long obsolete.

Also see the thread starting at
https://sourceware.org/ml/gdb-patches/2015-03/msg00989.html for some discussion

Note that __COPY_CONTEXT_SIZE should just be sizeof(CONTEXT) (which is a
platform constant), but isn't due to historical mistakes in Cygwin headers.

gdb/ChangeLog:

2015-06-03  Jon Turney  <jon.turney@dronecode.org.uk>

	* windows-nat.c (do_windows_fetch_inferior_registers)
	(handle_output_debug_string): Replace __COPY_CONTEXT_SIZE
	conditional with __CYGWIN__.

Signed-off-by: Jon Turney <jon.turney@dronecode.org.uk>


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] sim: bfin: expand CB_SYS_xxx comment
@ 2015-06-12 17:42 sergiodj+buildbot
  2015-06-13 15:17 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-06-12 17:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT aaa9dc0170d5a2c09712f65f38dd308e7cfd4df0 ***

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

sim: bfin: expand CB_SYS_xxx comment


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] sim: drop -DTRACE from configure
@ 2015-06-12 16:25 sergiodj+buildbot
  2015-06-13 11:14 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-06-12 16:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a34870829162e3276a9e0152efe2c7de5677a0c3 ***

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

sim: drop -DTRACE from configure
No code uses this anymore and the symbol conflicts with the new TRACE
helper.  Punt it from configure.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] sim: trace: centralize the system tracing
@ 2015-06-11 16:24 sergiodj+buildbot
  2015-06-12 13:29 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-06-11 16:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 83034798de7d11d2e26b3760e26b2c9cadec9fd4 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 83034798de7d11d2e26b3760e26b2c9cadec9fd4

sim: trace: centralize the system tracing
First we convert the ETRACE_P to STRACE_EVENTS_P.  This means we move from
using the sim_events.trace storage to the common sim_state_base.trace_data
array.  With that deleted, the common trace init code can be simplified so
the sim state works the same as the sim cpu.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Code cleanup: Use explicit NULL comparison
@ 2015-06-10 17:41 sergiodj+buildbot
  2015-06-11  6:20 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-06-10 17:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8847cac2f7ce6ff2c13fa611660c2dfc59c78272 ***

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

Code cleanup: Use explicit NULL comparison
gdb/ChangeLog
2015-06-10  Jan Kratochvil  <jan.kratochvil@redhat.com>

	Code cleanup.
	* solib-target.c (library_list_start_list): Use explicit NULL
	comparison.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Introduce nat/linux-namespaces.[ch]
@ 2015-06-10 13:47 sergiodj+buildbot
  2015-06-10 17:51 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-06-10 13:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4b8b5e72451d5b9da4000b8346b20035833aa087 ***

Author: Gary Benson <gbenson@redhat.com>
Branch: master
Commit: 4b8b5e72451d5b9da4000b8346b20035833aa087

Introduce nat/linux-namespaces.[ch]
This commit introduces new shared files nat/linux-namespaces.[ch]
containing code to support Linux namespaces that will be used by
both GDB and gdbserver.

gdb/ChangeLog:

	* configure.ac (AC_CHECK_FUNCS): Add setns.
	* config.in: Regenerate.
	* configure: Likewise.
	* nat/linux-namespaces.h: New file.
	* nat/linux-namespaces.c: Likewise.
	* Makefile.in (HFILES_NO_SRCDIR): Add nat/linux-namespaces.h.
	(linux-namespaces.o): New rule.
	* config/aarch64/linux.mh (NATDEPFILES): Add linux-namespaces.o.
	* config/alpha/alpha-linux.mh (NATDEPFILES): Likewise.
	* config/arm/linux.mh (NATDEPFILES): Likewise.
	* config/i386/linux.mh (NATDEPFILES): Likewise.
	* config/i386/linux64.mh (NATDEPFILES): Likewise.
	* config/ia64/linux.mh (NATDEPFILES): Likewise.
	* config/m32r/linux.mh (NATDEPFILES): Likewise.
	* config/m68k/linux.mh (NATDEPFILES): Likewise.
	* config/mips/linux.mh (NATDEPFILES): Likewise.
	* config/pa/linux.mh (NATDEPFILES): Likewise.
	* config/powerpc/linux.mh (NATDEPFILES): Likewise.
	* config/powerpc/ppc64-linux.mh (NATDEPFILES): Likewise.
	* config/powerpc/spu-linux.mh (NATDEPFILES): Likewise.
	* config/s390/linux.mh (NATDEPFILES): Likewise.
	* config/sparc/linux.mh (NATDEPFILES): Likewise.
	* config/sparc/linux64.mh (NATDEPFILES): Likewise.
	* config/tilegx/linux.mh (NATDEPFILES): Likewise.
	* config/xtensa/linux.mh (NATDEPFILES): Likewise.

gdb/gdbserver/ChangeLog:

	* configure.ac (AC_CHECK_FUNCS): Add setns.
	* config.in: Regenerate.
	* configure: Likewise.
	* Makefile.in (SFILES): Add nat/linux-namespaces.c.
	(linux-namespaces.o): New rule.
	* configure.srv (srv_linux_obj): Add linux-namespaces.o.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] windows-nat: Trim a trailing '\n' from OutputDebugString before echoing it
@ 2015-06-10 13:20 sergiodj+buildbot
  2015-06-10 14:22 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-06-10 13:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 040ea00bb02018cbe21ba732f68134ac91f370d2 ***

Author: Jon Turney <jon.turney@dronecode.org.uk>
Branch: master
Commit: 040ea00bb02018cbe21ba732f68134ac91f370d2

windows-nat: Trim a trailing '\n' from OutputDebugString before echoing it
For cosmetic purposes, trim a trailing '\n' from OutputDebugString before
echoing it, as warning() will add a '\n', anyhow.

gdb/ChangeLog:

2015-06-03  Jon Turney  <jon.turney@dronecode.org.uk>

	* windows-nat.c (handle_output_debug_string): Trim trailing '\n'
	from OutputDebugString.

Signed-off-by: Jon Turney <jon.turney@dronecode.org.uk>


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Add support for bound table in the Intel MPX context.
@ 2015-06-10 11:49 sergiodj+buildbot
  2015-06-10 13:16 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-06-10 11:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 29c1c24429a099eca297080dba56a8c090e3136a ***

Author: Walfred Tedeschi <walfred.tedeschi@intel.com>
Branch: master
Commit: 29c1c24429a099eca297080dba56a8c090e3136a

Add support for bound table in the Intel MPX context.
Intel(R) Memory protection bound information are located in register
to be tested using the MPX new instructions. Since the number of
bound registers are limited a table is used to provide storage for
bounds during run-time.

In order to investigate the contents of the MPX bound table two new
commands are added to GDB.  "show mpx bound" and "set mpx bound" are
used to display and set values on the MPX bound table.

2015-04-20  Walfred Tedeschi  <walfred.tedeschi@intel.com>
            Mircea Gherzan  <mircea.gherzan@intel.com>

	* i386-tdep.c (MPX_BASE_MASK, MPX_BD_MASK, MPX_BT_MASK, MPX_BD_MASK_32,
	MPX_BT_MASK_32): New macros.
	(i386_mpx_set_bounds): New function that implements
	the command "set-mpx-bound".
	(i386_mpx_enabled) Helper function to test MPX availability.
	(i386_mpx_bd_base) Helper function to calculate the base directory
	address. (i386_mpx_get_bt_entry) Helper function to access a bound
	table entry. (i386_mpx_print_bounds) Effectively display bound
	information. (_initialize_i386_tdep): Qdd new commands
	to commands "set mpx" and "show mpx". (_initialize_i386_tdep):
	Add "bound" to the commands "show mpx" and "set mpx" commands.
	(mpx_set_cmdlist and mpx_show_cmdlist):
	list for the new prefixed "set mpx" and "show mpx" commands.
	* NEWS: List new commands for MPX support.

testsuite:

	* gdb.arch/i386-mpx-map.c: New file.
	* gdb.arch/i386-mpx-map.exp: New File.

doc:
	* gdb.texinfo (i386): Add documentation about "show mpx bound"
	and "set mpx bound".


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Improve test for processor feature om MPX registers test.
@ 2015-06-10  9:48 sergiodj+buildbot
  2015-06-10 10:32 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-06-10  9:48 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 547a646d67e7a38b96d2a93b709e52c9461d017f ***

Author: Walfred Tedeschi <walfred.tedeschi@intel.com>
Branch: master
Commit: 547a646d67e7a38b96d2a93b709e52c9461d017f

Improve test for processor feature om MPX registers test.
Skips the MPX register test in case target is not Intel.
Improves the test for MPX feature making MPX and AVX512
tests more similar in terms of initialization.
Indentation was improved on sample file and final return added
to have_mpx.  On test file identation was improved and
gdb_send was exchanged by gdb_test_multiple.

2015-06-08  Walfred Tedeschi  <walfred.tedeschi@intel.com>

gdb/testsuite
	* gdb.arch/i386-mpx.c: Added final return to the have_mpx
	function and improved indentation.
	* gdb.arch/i386-mpx.exp: Exchanging gdb_send and gdb_expect for
	gdb_test_multiple. Added additional tests to skip the test.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Fix preprocessor conditional
@ 2015-06-09  9:40 sergiodj+buildbot
  2015-06-09 10:40 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-06-09  9:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ecef18c564bd609aa7640564747b807bfe1632c6 ***

Author: Gary Benson <gbenson@redhat.com>
Branch: master
Commit: ecef18c564bd609aa7640564747b807bfe1632c6

Fix preprocessor conditional
This commit fixes a typo in common/fileio.c where S_IWGRP was
misspelled as S_IWRGRP in a preprocessor conditional, causing
Host-I/O "vFile:fstat:" and File-I/O "Fstat" and "Ffstat"
responses to always indicate files were not group-writable
regardless of their actual status.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Regenerate gdbarch.c to sync with gdbarch.sh
@ 2015-06-04 17:04 sergiodj+buildbot
  2015-06-04 19:14 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-06-04 17:04 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5b74bf7d63e71e977fc9706b56499045035ea63a ***

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

Regenerate gdbarch.c to sync with gdbarch.sh
When I do something else, I find that gdbarch.c isn't sync'ed with
gdbarch.sh.  This patch just move some statements on
stack_frame_destroyed_p some lines below.

gdb:

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

	* gdbarch.c: Regenerate it.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Fix =thread-exited not showing up when detaching (PR 15564)
@ 2015-06-02 19:59 sergiodj+buildbot
  2015-06-02 20:54 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-06-02 19:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3b462ec2bedca7392bf4720db44fdf2a46ad8b4d ***

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

Fix =thread-exited not showing up when detaching (PR 15564)
I sent a patch in 2013 for this (incorrectly named =thread-created):

  https://cygwin.com/ml/gdb-patches/2013-06/msg00129.html

Tom Tromey was ok with the change, but suggested to add a test as well.
Then I forgot about this patch until today. So here it is again, with the
corresponding test.

The problem is that the =thread-exited event does not appear when detaching
from a local process. It does appear with remote though. It's not a really
big deal, but I'd like it to be consistent.

Tested with local and remote Linux on my Ubuntu 14.04.

gdb/ChangeLog:

	PR gdb/15564
	* inferior.c (detach_inferior): Call exit_inferior_1 with silent = 0.

gdb/testsuite/ChangeLog:

	PR gdb/15564
	* gdb.mi/mi-detach.exp: New file.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Check whether kernel supports PTRACE_GETREGSET
@ 2015-06-01 12:27 sergiodj+buildbot
  2015-06-01 17:21 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-06-01 12:27 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7efe48d196f3fb6f55fc53b8021a410848c0a677 ***

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

Check whether kernel supports PTRACE_GETREGSET
gdb:

2015-06-01  Yao Qi  <yao.qi@linaro.org>

	* arm-linux-nat.c (arm_linux_read_description): Check whether
	kernel supports PTRACE_GETREGSET.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Move PTRACE_GETREGSET and PTRACE_SETREGSET to nat/linux-ptrace.h
@ 2015-06-01 11:35 sergiodj+buildbot
  2015-06-01 13:17 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-06-01 11:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ca9b78ce906d588bb9aab0c6739c2dbdacd62612 ***

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

Move PTRACE_GETREGSET and PTRACE_SETREGSET to nat/linux-ptrace.h
Macros PTRACE_GETREGSET and PTRACE_SETREGSET are defined locally in
some places in GDB and GDBserver.  This patch is to move them to
nat/linux-ptrace.h to avoid duplication.

gdb:

2015-06-01  Yao Qi  <yao.qi@linaro.org>

	* amd64-linux-nat.c: Include "nat/linux-ptrace.h".
	* i386-linux-nat.c: Likewise.
	* nat/linux-ptrace.h (PTRACE_GETREGSET, PTRACE_SETREGSET): Define.
	* s390-linux-nat.c: Include "nat/linux-ptrace.h".
	(PTRACE_GETREGSET, PTRACE_SETREGSET): Remove.
	* x86-linux-nat.c: Include "nat/linux-ptrace.h".
	* x86-linux-nat.h (PTRACE_GETREGSET, PTRACE_SETREGSET): Remove.

gdb/gdbserver:

2015-06-01  Yao Qi  <yao.qi@linaro.org>

	* linux-s390-low.c (PTRACE_GETREGSET, PTRACE_SETREGSET): Remove.
	* linux-x86-low.c: Likewise.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [AArch64] BFD_RELOC_AARCH64_TLSLE_ADD_LO12 should enable overflow check
@ 2015-06-01  9:39 sergiodj+buildbot
  2015-06-01  9:59 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-06-01  9:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 36e6c1400b94b9da7ba0dff5b3900a8d3e3b0c75 ***

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

[AArch64] BFD_RELOC_AARCH64_TLSLE_ADD_LO12 should enable overflow check
BFD_RELOC_AARCH64_TLSLE_ADD_LO12 is used to generate simplest
one-instruction addressing for TLS LE model when tls size is smaller
4K. Linker need to make sure there is no TLS offset overflow.

2015-06-01  Jiong Wang  <jiong.wang@arm.com>

bfd/
  * elfnn-aarch64.c (elfNN_aarch64_howto_table): Set overflow type to
  complain_overflow_unsigned for BFD_RELOC_AARCH64_TLSLE_ADD_LO12.
  * elfxx-aarch64.c (_bfd_aarch64_elf_resolve_relocation): Don't use
  PGOFF for BFD_RELOC_AARCH64_TLSLE_ADD_LO12, that will mask off all
  potential high overflowed bits.

ld/testsuite/
  * ld-aarch64/tprel_add_lo12_overflow.s: New testcase.
  * ld-aarch64/tprel_add_lo12_overflow.d: Nex expectation file.
  * ld-aarch64/aarch64-elf.exp: Run new testcase.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [AArch64] BFD Support BFD_RELOC_AARCH64_LD64_GOTPAGE_LO15
@ 2015-06-01  9:32 sergiodj+buildbot
  2015-06-01  9:47 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-06-01  9:32 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 99ad26cb0d4f9152dbe5ed03b74020cc52d84d94 ***

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

[AArch64] BFD Support BFD_RELOC_AARCH64_LD64_GOTPAGE_LO15
2015-06-01  Jiong Wang  <jiong.wang@arm.com>
bfd/
	* elfnn-aarch64.c (aarch64_reloc_got_type): Support
	BFD_RELOC_AARCH64_LD64_GOTPAGE_LO15.
	(elfNN_aarch64_final_link_relocate): Ditto.
	(elfNN_aarch64_gc_swap_hook): Ditto.
	(elfNN_aarch64_check_relocs): Ditto.
	* elfxx-aarch64.c (_bfd_aarch64_elf_put_addend): Ditto.

ld/testsuite/
	* ld-aarch64/emit-relocs-313.s: New test file.
	* ld-aarch64/emit-relocs-313.d: Ditto.
	* ld-aarch64/aarch64-elf.exp: Run new test.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [AArch64] GAS Support BFD_RELOC_AARCH64_LD64_GOTPAGE_LO15
@ 2015-06-01  9:26 sergiodj+buildbot
  2015-06-01  9:36 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-06-01  9:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a921b5bd708cc6e8afa3cf33443cda54b4e8cae6 ***

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

[AArch64] GAS Support BFD_RELOC_AARCH64_LD64_GOTPAGE_LO15
2015-06-01 Jiong.Wang <jiong.wang@arm.com>

bfd/
  * reloc.c (BFD_RELOC_AARCH64_LD64_GOTPAGE_LO15): New entry.
  * bfd-in2.h: Regenerate.
  * libbfd.h: Regenerate.
  * elfnn-aarch64.c (elfNN_aarch64_howto_table): New entry for
  BFD_RELOC_AARCH64_LD64_GOTPAGE_LO15.

gas/
  * config/tc-aarch64.c (reloc_table): New relocation modifiers.
  (md_apply_fix): Support BFD_RELOC_AARCH64_LD64_GOTPAGE_LO15.
  (aarch64_force_relocation): Ditto.

gas/testsuite/
  * gas/aarch64/reloc-insn.s: New testcase.
  * gas/aarch64/reloc-insn.d: Ditto.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] x86/Intel: disassemble vcvt{, u}si2s{d, s} with correct operand order
@ 2015-06-01  8:05 sergiodj+buildbot
  2015-06-01  8:32 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-06-01  8:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3a8547d2fb5319890dda877fb313822053083c3a ***

Author: Jan Beulich <jbeulich@novell.com>
Branch: master
Commit: 3a8547d2fb5319890dda877fb313822053083c3a

x86/Intel: disassemble vcvt{,u}si2s{d,s} with correct operand order
As pointed out before, the documentation mandates the rounding mode to
follow the GPR, so disassembler should produce output accordingly.

gas/testsuite/
2015-06-01  Jan Beulich  <jbeulich@suse.com>

	* gas/i386/avx512f.s: Adjust operand order for Intel syntax
	vcvt{,u}si2ss.
	* gas/i386/x86-64-avx512f.s: Adjust operand order for Intel
	syntax vcvt{,u}si2s{d,s}.

opcodes/
2015-06-01  Jan Beulich  <jbeulich@suse.com>

	* i386-dis.c (print_insn): Swap rounding mode specifier and
	general purpose register in Intel mode.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] x86/Intel: accept mandated operand order for vcvt{, u}si2s{d, s}
@ 2015-06-01  8:00 sergiodj+buildbot
  2015-06-01  8:10 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-06-01  8:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 015c54d5a6a052f074fab168bc70296131276e80 ***

Author: Jan Beulich <jbeulich@novell.com>
Branch: master
Commit: 015c54d5a6a052f074fab168bc70296131276e80

x86/Intel: accept mandated operand order for vcvt{,u}si2s{d,s}
As pointed out before, the documentation mandates the rounding mode to
follow the GPR, so gas should accept such input. As the brojen code got
released already we sadly will need to continue to also accept the
badly ordered operands.

gas/testsuite/
2015-06-01  Jan Beulich  <jbeulich@suse.com>

	* gas/i386/avx512f-intel.d: Adjust expectations on operand order.
	* gas/i386/evex-lig256-intel.d: Likewise.
	* gas/i386/evex-lig512-intel.d: Likewise.
	* gas/i386/x86-64-avx512f-intel.d: Likewise.
	* gas/i386/x86-64-evex-lig256-intel.d: Likewise.
	* gas/i386/x86-64-evex-lig512-intel.d: Likewise.

opcodes/
2015-06-01  Jan Beulich  <jbeulich@suse.com>

	* i386-opc.tbl: New IntelSyntax entries for vcvt{,u}si2s{d,s}.
	* i386-tbl.h: Regenerate.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Disable exec-dependent follow vfork tests for remote
@ 2015-05-28 23:12 sergiodj+buildbot
  2015-05-29  7:08 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-05-28 23:12 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e970cb3401cf549accc92452f4888440fb983f39 ***

Author: Don Breazeal <donb@codesourcery.com>
Branch: master
Commit: e970cb3401cf549accc92452f4888440fb983f39

Disable exec-dependent follow vfork tests for remote
The native-extended-gdbserver target now supports fork events and
follow fork, but it does not yet support exec events.  Some of the
tests in gdb.base/foll-vfork.exp depend on exec events.  This patch
disables those tests for remote targets.  We can re-enable these
once the exec event support goes in.

gdb/testsuite/

	* gdb.base/foll-vfork.exp (main): Disable exec-dependent
	tests for remote targets by checking is_target_gdbserver.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] * dwarf2read.c (record_line_ftype): Remove, duplicate.
@ 2015-05-28 17:04 sergiodj+buildbot
  2015-05-28 18:17 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-05-28 17:04 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a051152b640c8bd1286ae71410f0b861ee158691 ***

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

* dwarf2read.c (record_line_ftype): Remove, duplicate.
gdb/Changelog:

	* dwarf2read.c (record_line_ftype): Remove, duplicate.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Fix ARI warnings in aarch64-tdep.c
@ 2015-05-27 10:48 sergiodj+buildbot
  2015-05-27 11:08 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-05-27 10:48 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5d98d3cd862ab5d463f71926788d52bf1b30ef79 ***

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

Fix ARI warnings in aarch64-tdep.c
This patch fixes some ARI warnings:

 $ bash ./gdb/contrib/ari/gdb_ari.sh -Wall -Werror -Wari gdb/aarch64-tdep.c
 gdb/aarch64-tdep.c:3009: code: Do not use &&, or || at the end of a line
 gdb/aarch64-tdep.c:3010: code: Do not use &&, or || at the end of a line
 gdb/aarch64-tdep.c:3413: code: Do not use &&, or || at the end of a line
 gdb/aarch64-tdep.c:3460: code: Do not use &&, or || at the end of a line

This patch moves && from the end of line to the start of the line.

gdb:

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

	* aarch64-tdep.c (aarch64_record_branch_except_sys): Split lines
	before operator &&.
	(aarch64_record_load_store): Likewise.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] PR c++/18141, c++/18417.
@ 2015-05-27  0:27 sergiodj+buildbot
  2015-05-27 10:48 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-05-27  0:27 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 82c7be3106bbbf753f441f8a8113f2cac5e7cba8 ***

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

PR c++/18141, c++/18417.
gdb/ChangeLog:

	* cp-support.c (cp_lookup_rtti_type): Handle the case of NAME being
	a typedef.

gdb/testsuite/ChangeLog:

	* gdb.cp/iostream.cc: New file.
	* gdb.cp/iostream.exp: New file.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Rename dwarf2 to dwarf in "set debug" and maintenance commands.
@ 2015-05-27  0:00 sergiodj+buildbot
  2015-05-27  3:47 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-05-27  0:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b4f5498457d0648811a9cc9d34d3c6635509dffc ***

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

Rename dwarf2 to dwarf in "set debug" and maintenance commands.
gdb/ChangeLog:

	* NEWS: Add entries for command renamings.
	* dwarf2read.c (dwarf_read_debug): Renamed from dwarf2_read_debug.
	All uses updated.
	(dwarf_die_debug): Renamed from dwarf2_die_debug.  All uses updated.
	(dwarf_max_cache_age): Renamed from dwarf2_max_cache_age.
	All uses updated.
	(show_dwarf_max_cache_age): Renamed from show_dwarf2_max_cache_age.
	All callers updated.  Fix spelling of DWARF in help text.
	(set_dwarf_cmdlist): Renamed from set_dwarf2_cmdlist.
	All uses updated.
	(show_dwarf_cmdlist): Renamed from show_dwarf2_cmdlist.
	All uses updated.
	(set_dwarf_cmd): Renamed from set_dwarf2_cmd.  All callers updated.
	(show_dwarf_cmd): Renamed from show_dwarf2_cmd.  All callers updated.
	(dwarf_always_disassemble): Renamed from dwarf_always_disassemble.
	All uses updated.
	(show_dwarf_always_disassemble): Renamed from
	show_dwarf2_always_disassemble.  All callers updated.
	(_initialize_dwarf2_read): Rename "set/show dwarf2" prefix to
	"set/show dwarf".  Rename "set/show dwarf2 max-cache-age" to
	"set/show dwarf max-cache-age".  Rename
	"set/show dwarf2 always-disassemble" to
	"set/show dwarf always-disassemble".  Rename
	"set/show debug dwarf2-read" to "set/show debug dwarf-read".  Rename
	"set/show debug dwarf2-die" to "set/show debug dwarf-die".

gdb/doc/ChangeLog:

	* gdb.texinfo (Debugging Output): Update for DWARF "set debug"
	command renamings.
	(Maintenance Commands): Update for DWARF "set debug" command renamings.

gdb/testsuite/ChangeLog:

	* gdb.dwarf2/dw2-op-call.exp: Update.
	* gdb.dwarf2/dw4-sig-types.exp: Update.
	* gdb.dwarf2/implptr.exp: Update.
	* gdb.mi/mi-cmd-param-changed.exp: Update.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] PR python/18438
@ 2015-05-26 23:21 sergiodj+buildbot
  2015-05-26 23:31 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-05-26 23:21 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4ea6efe9365f8a87723fe01a2dd8ddf5cdec1498 ***

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

PR python/18438
gdb/ChangeLog:

	* python/py-lazy-string.c (stpy_convert_to_value): Use
	gdbpy_gdb_memory_error not PyExc_MemoryError.
	(gdbpy_create_lazy_string_object): Ditto.

gdb/testsuite/ChangeLog:

	* gdb.python/py-lazy-string.c: New file.
	* gdb.python/py-lazy-string.exp: New file.
	* gdb.python/py-prettyprint.c (lazystring) <len>: New member.
	(main): Update.  Add estring3.
	* gdb.python/py-prettyprint.exp: Add tests for strings at address 0.
	* gdb.python/py-prettyprint.py (pp_ls): Handle length.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] gdb: tui: Minor fix to compare against NULL.
@ 2015-05-26 21:49 sergiodj+buildbot
  2015-05-26 22:04 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-05-26 21:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b93fd21dccc2cfa9a335ddba7435a341b49330ae ***

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

gdb: tui: Minor fix to compare against NULL.
Minor coding standard fix to compare against NULL.

gdb/ChangeLog:

	* tui/tui-regs.c (tui_reg_next_command): Compare against NULL.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] gdb: Add 'tui reg prev' command.
@ 2015-05-26 21:39 sergiodj+buildbot
  2015-05-26 21:50 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-05-26 21:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 55b400279267cad460ca62a8211f0b414f564e93 ***

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

gdb: Add 'tui reg prev' command.
There is already a 'tui reg next' command, this adds a symmetric 'tui
reg prev' command.

gdb/ChangeLog:

	* tui/tui-regs.c (tui_reg_prev_command): New function.
	(_initialize_tui_regs): Add 'prev' command for 'tui reg'.
	* reggroups.c (reggroup_prev): New function.
	* reggroups.h (reggroup_prev): Add declaration.  Update comment.

gdb/doc/ChangeLog:

	* gdb.texinfo (TUI Commands): Add 'tui reg prev' details.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] New gdb.reverse test case for aarch64 instructions
@ 2015-05-26 14:39 sergiodj+buildbot
  2015-05-26 17:41 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-05-26 14:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f6bb7db35da7b1d150a467f97c41d5bf72c3baf5 ***

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

New gdb.reverse test case for aarch64 instructions
This patch adds a test case to test the process record for some of
aarch64 instructions.

In each function, GDB turns on process record, and single step until
program goes to the end of the function.  Then, single step backward.
In each of forward single step and backward single step, the contents
of registers are saved, and test compares them.  If there is any
differences, a FAIL is emitted.

The test is flexible, and we can test other instructions easily in the
future.

gdb/testsuite:

2015-05-26  Omair Javaid  <omair.javaid@linaro.org>
	    Yao Qi  <yao.qi@linaro.org>

	* gdb.reverse/aarch64.c: New.
	* gdb.reverse/aarch64.exp: New.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Enables gdb.reverse testsuite for aarch64*-linux targets
@ 2015-05-26 14:29 sergiodj+buildbot
  2015-05-26 17:22 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-05-26 14:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a81bfbd06b949518055b21d19f47332edbd992e0 ***

Author: Omair Javaid <omair.javaid@linaro.org>
Branch: master
Commit: a81bfbd06b949518055b21d19f47332edbd992e0

Enables gdb.reverse testsuite for aarch64*-linux targets
This patch enable gdb.reverse tests for aarch64*-linux targets.

With this patch, there are 7 FAILs in gdb.reverse/ tests.

 FAIL: gdb.reverse/finish-reverse-bkpt.exp: reverse-finish from void_func trips breakpoint at entry
 FAIL: gdb.reverse/finish-reverse-bkpt.exp: no spurious proceed after breakpoint stop
 FAIL: gdb.reverse/next-reverse-bkpt-over-sr.exp: reverse-next over call trips user breakpoint at function entry
 FAIL: gdb.reverse/step-precsave.exp: reverse step into fn call
 FAIL: gdb.reverse/step-precsave.exp: reverse step out of called fn
 FAIL: gdb.reverse/step-reverse.exp: reverse step into fn call
 FAIL: gdb.reverse/step-reverse.exp: reverse step out of called fn

gdb/testsuite:

2015-05-26  Omair Javaid  <omair.javaid@linaro.org>

	* lib/gdb.exp (supports_process_record): Return true for aarch64*-linux*.
	(supports_reverse): Likewise.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Implements aarch64 process record and reverse debugging support
@ 2015-05-26 14:20 sergiodj+buildbot
  2015-05-26 17:03 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-05-26 14:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 99afc88b396045cfe3755bede41a45ad3bed021d ***

Author: Omair Javaid <omair.javaid@linaro.org>
Branch: master
Commit: 99afc88b396045cfe3755bede41a45ad3bed021d

Implements aarch64 process record and reverse debugging support
This patch adds the support of aarch64-linux process record and reverse
debugging.  The implementation is similar to ARM's counterpart.

2015-05-26  Omair Javaid  <omair.javaid@linaro.org>
	    Yao Qi  <yao.qi@linaro.org>

	* aarch64-linux-tdep.c: Include linux-record.h and
	record-full.h.
	(struct linux_record_tdep aarch64_linux_record_tdep): Declare.
	(aarch64_syscall): New enum.
	(aarch64_canonicalize_syscall): New function.
	(aarch64_all_but_pc_registers_record): New function.
	(aarch64_linux_syscall_record): New function.
	(aarch64_linux_init_abi): Install AArch64 process record
	handler.  Update to handle syscall recording.
	* aarch64-tdep.c: Include record.h and record-full.h.
	(submask, bit, bits, REG_ALLOC, MEM_ALLOC): New macros.
	(struct aarch64_mem_r): Define.
	(aarch64_record_result): New enum.
	(struct insn_decode_record): Define.
	(insn_decode_record): New typedef.
	(aarch64_record_data_proc_reg): New function.
	(aarch64_record_data_proc_imm): New function.
	(aarch64_record_branch_except_sys): New function.
	(aarch64_record_load_store): New function.
	(aarch64_record_data_proc_simd_fp): New function.
	(aarch64_record_asimd_load_store): New function.
	(aarch64_record_decode_insn_handler): New function.
	(deallocate_reg_mem): New function.
	(aarch64_process_record): New function.
	* aarch64-tdep.h (struct gdbarch_tdep) <aarch64_syscall_record>:
	New field.
	(aarch64_process_record): New extern declaration.
	* configure.tgt: Add linux-record.o to gdb_target_obs.
	* linux-record.h (struct linux_record_tdep) <arg7>: New field.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] NEWS entry about aarch64-linux record/replay support
@ 2015-05-26 14:10 sergiodj+buildbot
  2015-05-26 16:35 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-05-26 14:10 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c16a3f522a71a20ff6e26599d684a61ac6acecca ***

Author: Omair Javaid <omair.javaid@linaro.org>
Branch: master
Commit: c16a3f522a71a20ff6e26599d684a61ac6acecca

NEWS entry about aarch64-linux record/replay support
This patch adds the NEWS entry for aarch64-linux record replay
support.

It has been reviewed and approved.

gdb:

2015-05-26  Omair Javaid  <omair.javaid@linaro.org>

	* NEWS: Add a note on process record-replay support on aarch64*-linux*
	targets.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Make sure test names are unique in gdb.base/gdbinit-history.exp
@ 2015-05-22  1:22 sergiodj+buildbot
  2015-05-22  5:38 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-05-22  1:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 158bf1b4aacf7f184facdc184dc9585994f041a6 ***

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

Make sure test names are unique in gdb.base/gdbinit-history.exp
Use with_test_prefix to avoid duplicating test names when calling
the procedure test_gdbinit_history_setting multiple times.

gdb/testsuite/ChangeLog:

	* gdb.base/gdbinit-history.exp (test_gdbinit_history_setting):
	Use with_test_prefix.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] gdb: Don't call tui_enable too early.
@ 2015-05-21 21:14 sergiodj+buildbot
  2015-05-22  0:41 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-05-21 21:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 880d1e40c771e4a389d0b29bf196b50f1b696ea9 ***

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

gdb: Don't call tui_enable too early.
Calling tui_enable too early in tui_layout_command can leave the tui in
an enabled state if the user has entered an invalid layout name.
Instead postpone the call to tui_enable until later in
tui_set_layout_for_display_command just before the layout is changed.

gdb/ChangeLog:

	* tui/tui-layout.c (tui_layout_command): Move call to tui_enable
	into ...
	(tui_set_layout_for_display_command): ...here, before calling
	tui_set_layout.  Only set the layout if gdb has not already
	entered the TUI_FAILURE state.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] gdb: Add completer for layout command.
@ 2015-05-21 20:01 sergiodj+buildbot
  2015-05-21 22:28 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-05-21 20:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a014503004ad016d754bc9a4b143973ee18b0bbf ***

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

gdb: Add completer for layout command.
Add layout name completion for the layout command.

gdb/ChangeLog:

	* tui/tui-layout.c (layout_completer): New function.
	(_initialize_tui_layout): Set completer on layout command.

gdb/testsuite/ChangeLog:

	* gdb.base/completion.exp: Add test for completion of layout
	names.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Fix gdb.base/gdbinit-history.exp when HISTSIZE is set in the environment
@ 2015-05-19 10:23 sergiodj+buildbot
  2015-05-19 11:56 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-05-19 10:23 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 84204ed7c0ccaa790dff8e124e710277d9a8abc9 ***

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

Fix gdb.base/gdbinit-history.exp when HISTSIZE is set in the environment
Some buildslaves are showing that this test is failing.  E.g.,:

 https://sourceware.org/ml/gdb-testers/2015-q2/msg04164.html

The issue is that HISTSIZE is set to 1000 in the environment that runs
the tests (that's the default in Fedora, set in /etc/profile).

We can trivially reproduce it with:

 $ HISTSIZE=1000 make check RUNTESTFLAGS="gdbinit-history.exp"
 (...)
 Running /home/pedro/gdb/mygit/src/gdb/testsuite/gdb.base/gdbinit-history.exp ...
 FAIL: gdb.base/gdbinit-history.exp: show history size
 FAIL: gdb.base/gdbinit-history.exp: show history size
 FAIL: gdb.base/gdbinit-history.exp: show commands

gdb.log shows:
 ...
 (gdb) set height 0
 (gdb) set width 0
 (gdb) show history size
 The size of the command history is 1000.
 (gdb) FAIL: gdb.base/gdbinit-history.exp: show history size

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

	* gdb.base/gdbinit-history.exp (test_gdbinit_history_setting):
	Save the whole env array instead of just HOME.  Unset HISTSIZE in
	the environment while testing.  Restore whole environment
	afterwards.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] sim: erc32: restore attribution
@ 2015-05-17  9:35 sergiodj+buildbot
  2015-05-17 10:20 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-05-17  9:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 296730a52b06fe7dd658924acae1269a54015d52 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 296730a52b06fe7dd658924acae1269a54015d52

sim: erc32: restore attribution


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Add support for unbuffered and zero sized Guile ports.
@ 2015-05-16 19:57 sergiodj+buildbot
  2015-05-17  0:37 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-05-16 19:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 37442ce10aaa2f84d245631d38e25ee47e5057aa ***

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

Add support for unbuffered and zero sized Guile ports.
gdb/ChangeLog

	* NEWS: Mention support for unbuffered Guile memory ports.
	* scm-ports.c (ioscm_memory_port): Update comments on end, size.
	(ioscm_lseek_address): Improve overflow calculation.
	(gdbscm_memory_port_fill_input): Add assert.
	(gdbscm_memory_port_write): Handle unbuffered ports.
	Handle large writes identical to Guile's fport_write.
	(gdbscm_memory_port_seek): Fix seeking past end check.
	(gdbscm_memory_port_close): Handle closing unbuffered port.
	(ioscm_parse_mode_bits): Recognize "0" for unbuffered ports.
	(ioscm_init_memory_port): Handle unbuffered ports.
	(ioscm_reinit_memory_port): Ditto.
	(ioscm_init_memory_port): Update size calculation.
	(gdbscm_open_memory): Support zero sized ports.

gdb/testsuite/ChangeLog

	* gdb.guile/scm-ports.c: New file.
	* gdb.guile/scm-ports.exp: Add memory port tests.

gdb/doc/ChangeLog

	* guile.texi (Memory Ports in Guile): Document support for unbuffered
	memory ports.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Code cleanup: compile: func_addr -> func_sym
@ 2015-05-16 16:31 sergiodj+buildbot
  2015-05-16 20:02 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-05-16 16:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 83d3415ef530c41af7e1ae98a7add97adb0cf5e0 ***

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

Code cleanup: compile: func_addr -> func_sym
Currently the code fetches _gdb_expr address/types at multiple places, guessing
its parameters at multiple places etc.

Fetch it once, verify it has expected type and then rely on it.

While the patch tries to clean up the code it is still horrible due to the
missing C++ sub-classing.


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

	* compile/compile-object-load.c (get_regs_type): Add parameter func_sym.
	Rely on its parameter count.
	(compile_object_load): Replace lookup_minimal_symbol_text by
	lookup_global_symbol_from_objfile.  Verify FUNC_SYM.  Set it in the
	return value.
	* compile/compile-object-load.h (struct compile_module): Replace
	func_addr by func_sym.
	* compile/compile-object-run.c: Include block.h.
	(compile_object_run): Reset module variable after it is freed.  Use
	FUNC_SYM instead of FUNC_ADDR.  Rely on it.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Don't generate PLT relocations for now binding
@ 2015-05-16 15:35 sergiodj+buildbot
  2015-05-16 20:55 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-05-16 15:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 25070364b0ce33eed46aa5d78ebebbec6accec7e ***

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

Don't generate PLT relocations for now binding
There is no need for PLT relocations with -z now. We can use GOT
relocations, which take less space, instead and replace 16-byte .plt
entres with 8-byte .plt.got entries.

bfd/

	* elf32-i386.c (elf_i386_check_relocs): Create .plt.got section
	for now binding.
	(elf_i386_allocate_dynrelocs): Use .plt.got section for now
	binding.
	* elf64-x86-64.c (elf_x86_64_check_relocs): Create .plt.got
	section for now binding.
	(elf_x86_64_allocate_dynrelocs): Use .plt.got section for now
	binding.

ld/testsuite/

	* ld-i386/i386.exp: Run PR ld/17689 tests with -z now.
	* ld-x86-64/x86-64.exp: Likewise
	* ld-i386/pr17689now.rd: New file.
	* ld-x86-64/pr17689now.rd: Likewise


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] compile: Fix detected inferior type
@ 2015-05-16 15:20 sergiodj+buildbot
  2015-05-16 20:38 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-05-16 15:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4d18dfad9edf822df205edc2c1fe3fe9f1e467b8 ***

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

compile: Fix detected inferior type
gdb/ChangeLog
2015-05-16  Jan Kratochvil  <jan.kratochvil@redhat.com>

	* compile/compile-object-load.c (get_out_value_type): Fix returned type.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] compile: New 'compile print'
@ 2015-05-16 15:07 sergiodj+buildbot
  2015-05-16 20:20 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-05-16 15:07 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 36de76f9cc2eea0bd5f1b7ce74ef60e1aa0b27c2 ***

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

compile: New 'compile print'
It is planned the existing GDB command 'print' will be able to evaluate its
expressions using the compiler.  There will be some option to choose between
the existing GDB evaluation and the compiler evaluation.  But as an
intermediate step this patch provides the expression printing feature as a new
command.

I can imagine it could be also called 'maintenance compile print' as in the
future one should be able to use its functionality by the normal 'print'
command.

There was a discussion with Eli about the command name:
	https://sourceware.org/ml/gdb-patches/2015-03/msg00880.html
As there were no other comments yet I haven't renamed it yet, before there is
some confirmation about settlement on the final name.

Support for the GDB '@' operator to create arrays has been submitted for GCC:
	[gcc patch] libcc1: '@' GDB array operator
	https://gcc.gnu.org/ml/gcc-patches/2015-03/msg01451.html


gdb/ChangeLog
2015-05-16  Jan Kratochvil  <jan.kratochvil@redhat.com>
	    Phil Muldoon  <pmuldoon@redhat.com>

	* NEWS (Changes since GDB 7.9): Add compile print.
	* compile/compile-c-support.c (add_code_header, add_code_footer)
	(c_compute_program): Add COMPILE_I_PRINT_ADDRESS_SCOPE and
	COMPILE_I_PRINT_VALUE_SCOPE.
	* compile/compile-internal.h (COMPILE_I_PRINT_OUT_ARG_TYPE)
	(COMPILE_I_PRINT_OUT_ARG, COMPILE_I_EXPR_VAL, COMPILE_I_EXPR_PTR_TYPE):
	New.
	* compile/compile-object-load.c: Include block.h.
	(get_out_value_type): New function.
	(compile_object_load): Handle COMPILE_I_PRINT_ADDRESS_SCOPE and
	COMPILE_I_PRINT_VALUE_SCOPE.  Set compile_module's OUT_VALUE_ADDR and
	OUT_VALUE_TYPE.
	* compile/compile-object-load.h (struct compile_module): Add fields
	out_value_addr and out_value_type.
	* compile/compile-object-run.c: Include valprint.h and compile.h.
	(struct do_module_cleanup): Add fields out_value_addr and
	out_value_type.
	(do_module_cleanup): Handle COMPILE_I_PRINT_ADDRESS_SCOPE and
	COMPILE_I_PRINT_VALUE_SCOPE.
	(compile_object_run): Propagate out_value_addr and out_value_type.
	Pass OUT_VALUE_ADDR.
	* compile/compile.c: Include valprint.h.
	(compile_print_value, compile_print_command): New functions.
	(eval_compile_command): Handle failed COMPILE_I_PRINT_ADDRESS_SCOPE.
	(_initialize_compile): Update compile code help text.  Install
	compile_print_command.
	* compile/compile.h (compile_print_value): New prototype.
	* defs.h (enum compile_i_scope_types): Add
	COMPILE_I_PRINT_ADDRESS_SCOPE and COMPILE_I_PRINT_VALUE_SCOPE.

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

	* gdb.texinfo (Compiling and Injecting Code): Add compile print.

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

	* gdb.compile/compile-print.c: New file.
	* gdb.compile/compile-print.exp: New file.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Fix gdb.mi/mi-nsmoribund.exp timeouts
@ 2015-05-15 18:59 sergiodj+buildbot
  2015-05-15 21:12 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-05-15 18:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4e63d0ac896b6036edd8e2c09a4dac7aa16a46d1 ***

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

Fix gdb.mi/mi-nsmoribund.exp timeouts
The PPC64 buildbot has been showing timeouts in mi-nsmoribund.exp,
like this:

 (...)
 -thread-info
 FAIL: gdb.mi/mi-nsmoribund.exp: thread state: all running except the breakpoint thread (timeout)

... and I can reproduce this on gcc110 (PPC64) on the gcc compile
farm.

That is, the test sends "-thread-info" to GDB, but GDB never replies
back.

The problem is that these machines are too fast for gdb.  :-)

That test has a few threads running the same tight loop, and
constantly hitting a thread-specific breakpoint that needs to be
stepped over.  If threads trip on breakpoints fast enough that
linux-nat.c's event pipe associated with SIGCHLD is constantly being
written to, even if the stdin file descriptor also has an event to
handle, gdb never gets to it. because linux-nat.c's pipe comes first
in the set of descriptors served by the poll/select code in the event
loop.

Fix this by having the event loop serve file event sources in
round-robin-like fashion, similarly to how its done in
gdb_do_one_event.

Unfortunately, the poll and the select variants each need their own
fixing.

Tested on x86_64 Fedora 20 (poll and select variants), and PPC64
Fedora 18.  Fixes the timeout in the PPC64 machine in the compile farm
that times out without this, and I won't be surprised if it fixes
other random timeouts in other tests.

(gdbserver's copy of the event-loop doesn't need this (yet), as it
still pushes all ready events to an event queue.  That is, it hasn't
had 70b66289 merged yet.  We should really merge both event-loop.c
copies into a single shared file, but that's for another day.)

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

	* event-loop.c (gdb_notifier) <next_file_handler,
	next_poll_fds_index>: New fields.
	(get_next_file_handler_to_handle_and_advance): New function.
	(delete_file_handler): If deleting the next file handler to
	handle, advance to the next file handler.
	(gdb_wait_for_event): Bail early if no event fired.  Poll file
	handlers in round-robin fashion.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Fix a couple C++ build issues
@ 2015-05-15 15:31 sergiodj+buildbot
  2015-05-15 16:55 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-05-15 15:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 13fa0398d7dd8d2b468acf0aba5610ce014709a6 ***

Author: Yuanhui Zhang <asmwarrior@gmail.com>
Branch: master
Commit: 13fa0398d7dd8d2b468acf0aba5610ce014709a6

Fix a couple C++ build issues
Building mingw GDB with --enable-build-with-cxx shows:

../../binutils-gdb/gdb/python/py-unwind.c:500:45: error: cannot convert 'cached_frame_info::reg_info*' to 'pyuw_prev_register(frame_info*, void**, int)::reg_info*' in initialization
   struct reg_info *reg_info = cached_frame->reg;
                                             ^
../../binutils-gdb/gdb/python/py-unwind.c:501:60: error: invalid use of incomplete type 'struct pyuw_prev_register(frame_info*, void**, int)::reg_info'
   struct reg_info *reg_info_end = reg_info + cached_frame->reg_count;
                                                            ^
../../binutils-gdb/gdb/python/py-unwind.c:500:10: error: forward declaration of 'struct pyuw_prev_register(frame_info*, void**, int)::reg_info'
   struct reg_info *reg_info = cached_frame->reg;
          ^
../../binutils-gdb/gdb/python/py-unwind.c:505:37: error: cannot increment a pointer to incomplete type 'pyuw_prev_register(frame_info*, void**, int)::reg_info'
   for (; reg_info < reg_info_end; ++reg_info)
                                     ^
../../binutils-gdb/gdb/python/py-unwind.c:507:29: error: invalid use of incomplete type 'struct pyuw_prev_register(frame_info*, void**, int)::reg_info'
       if (regnum == reg_info->number)
                             ^
../../binutils-gdb/gdb/python/py-unwind.c:500:10: error: forward declaration of 'struct pyuw_prev_register(frame_info*, void**, int)::reg_info'
   struct reg_info *reg_info = cached_frame->reg;
          ^
../../binutils-gdb/gdb/python/py-unwind.c:508:68: error: invalid use of incomplete type 'struct pyuw_prev_register(frame_info*, void**, int)::reg_info'
         return frame_unwind_got_bytes (this_frame, regnum, reg_info->data);
                                                                    ^
../../binutils-gdb/gdb/python/py-unwind.c:500:10: error: forward declaration of 'struct pyuw_prev_register(frame_info*, void**, int)::reg_info'
   struct reg_info *reg_info = cached_frame->reg;
          ^
../../binutils-gdb/gdb/python/py-unwind.c: In function 'int pyuw_sniffer(const frame_unwind*, frame_info*, void**)':
../../binutils-gdb/gdb/python/py-unwind.c:574:70: warning: invalid conversion from 'void*' to 'cached_frame_info*' [-fpermissive]
                             reg_count * sizeof (cached_frame->reg[0]));
                                                                      ^
../../binutils-gdb/gdb/python/py-unwind.c: In function 'void pyuw_on_new_gdbarch(gdbarch*)':
../../binutils-gdb/gdb/python/py-unwind.c:636:47: warning: invalid conversion from 'void*' to 'pyuw_gdbarch_data_type*' [-fpermissive]
       gdbarch_data (newarch, pyuw_gdbarch_data);
                                               ^
../../binutils-gdb/gdb/python/py-unwind.c:647:29: warning: invalid conversion from 'void*' to 'const frame_data*' [-fpermissive]
       unwinder->unwind_data = (void *) newarch;
                             ^
../../binutils-gdb/gdb/python/py-unwind.c: At global scope:
../../binutils-gdb/gdb/python/py-unwind.c:699:21: error: redefinition of 'PyTypeObject pending_frame_object_type'
 static PyTypeObject pending_frame_object_type =
                     ^
../../binutils-gdb/gdb/python/py-unwind.c:96:21: error: 'PyTypeObject pending_frame_object_type' previously declared here
 static PyTypeObject pending_frame_object_type
                     ^
../../binutils-gdb/gdb/python/py-unwind.c:749:21: error: redefinition of 'PyTypeObject unwind_info_object_type'
 static PyTypeObject unwind_info_object_type =
                     ^
../../binutils-gdb/gdb/python/py-unwind.c:99:21: error: 'PyTypeObject unwind_info_object_type' previously declared here
 static PyTypeObject unwind_info_object_type
                     ^

The first kind of error is caused by the embedded struct definition,
so move it out of the parent struct.

The second kind of error is caused by forward declaring a static
global variable, which works in C, but not in C++ (or C with
-fno-common).  Make it using extern instead, like done in other
similar cases.

gdb/ChangeLog:
2015-05-15  Yuanhui Zhang  <asmwarrior@gmail.com>

	* python/py-unwind.c (struct reg_info): Move out of ...
	(struct cached_frame_info): ... this scope.
	(pending_frame_object_type, unwind_info_object_type): Make extern.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Fix build gdbserver build errors on arm, mips, aarch64.
@ 2015-05-14 20:35 sergiodj+buildbot
  2015-05-14 22:09 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-05-14 20:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 61a7418ccb7c2de12d4c4df79e193f32db938a11 ***

Author: Don Breazeal <donb@codesourcery.com>
Branch: master
Commit: 61a7418ccb7c2de12d4c4df79e193f32db938a11

Fix build gdbserver build errors on arm, mips, aarch64.
Fix build errors introduced by
https://sourceware.org/ml/gdb-patches/2015-05/msg00281.html, which
didn't account for the change of the name of the struct process_info
field 'private' to 'priv' made in
https://sourceware.org/ml/gdb-patches/2015-02/msg00829.html.

gdb/gdbserver/ChangeLog:

	* linux-aarch64-low.c (aarch64_linux_new_fork): Change reference
	to process_info.private to process_info.priv.
	* linux-arm-low.c (arm_new_fork): Likewise.
	* linux-mips-low.c (mips_linux_new_fork): Likewise.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Fix PR gdb/17820
@ 2015-05-13 13:29 sergiodj+buildbot
  2015-05-13 15:24 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-05-13 13:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ebfd00d210ca6190239140b250499e194fd5af20 ***

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

Fix PR gdb/17820
This patch is a comprehensive fix for PR 17820 which reports that
using "set history size unlimited" inside one's gdbinit file doesn't
really work.

There are three small changes in this patch.  The most important change
this patch makes is to decode the argument of the "size" subcommand
using add_setshow_zuinteger_unlimited_cmd() instead of using
add_setshow_uinteger_cmd().  The new decoder takes an int * and maps
unlimited to -1 whereas the old decoder takes an unsigned int * and maps
unlimited to UINT_MAX.  Using the new decoder simplifies our handling of
unlimited and makes it easier to interface with readline which itself
expects a signed-int history size.

The second change is the factoring of the [stifle|unstifle]_history logic
into a common function which is now used by both init_history() and
set_history_size_command().  This is technically the change that fixes
the PR itself.

Thirdly, this patch initializes history_size_setshow_var to -2 to mean
that the variable has not been set yet.  Now init_history() tests for -2
instead of 0 to determine whether to give the variable a default value.
This means that having "set history size 0" in one's gdbinit file will
actually keep the history size at 0 and not reset it to 256.

gdb/ChangeLog:

	PR gdb/17820
	* top.c (history_size_setshow_var): Change type to signed.
	Initialize to -2.  Update documentation.
	(set_readline_history_size): Define.
	(set_history_size_command): Use it.  Remove logic for handling
	out-of-range sizes.
	(init_history): Use set_readline_history_size().  Test for a
	value of -2 instead of 0 when determining whether to set a
	default history size.
	(init_main): Decode the argument of the "size" command as a
	zuinteger_unlimited.

gdb/testsuite/ChangeLog:

	PR gdb/17820
	* gdb.base/gdbinit-history.exp: New test.
	* gdb.base/gdbinit-history/unlimited/.gdbinit: New file.
	* gdb.base/gdbinit-history/zero/.gdbinit: New file.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [AArch64] Add R_AARCH64_P32_LD32_GOTPAGE_LO14 to elf header
@ 2015-05-12 12:50 sergiodj+buildbot
  2015-05-12 14:09 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-05-12 12:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 15eddee17fd772021fc3a331904e8f6b55b354c7 ***

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

[AArch64] Add R_AARCH64_P32_LD32_GOTPAGE_LO14 to elf header
2015-05-12  Jiong. Wang  <jiong.wang@arm.com>

include/
  * elf/aarch64.h (R_AARCH64_P32_LD32_GOTPAGE_LO14): New enumeration.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Replace input_bfd and output_bfd with abfd
@ 2015-05-10 14:04 sergiodj+buildbot
  2015-05-10 15:05 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-05-10 14:04 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4b71eec62785db0fe5f02b0da95f18b7b4a33df1 ***

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

Replace input_bfd and output_bfd with abfd
The first argument to bfd_get_8/bfd_put_8 isn't used.  But we should
use something real.  Replace input_bfd and output_bfd with abfd.

	* elf32-i386.c (elf_i386_convert_mov_to_lea): Replace input_bfd
	and output_bfd with abfd.
	* elf64-x86-64.c (elf_x86_64_convert_mov_to_lea): Likewise.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Avoid segfault on missing directory table.
@ 2015-05-09  0:26 sergiodj+buildbot
  2015-05-09 12:00 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-05-09  0:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT afa6c9abf2c12c8e6155d088ea45e5091ca79c57 ***

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

Avoid segfault on missing directory table.
2015-05-08  Yao Qi  <yao@codesourcery.com>
	    Sandra Loosemore  <sandra@codesourcery.com>

	gdb/
	* dwarf2read.c (setup_type_unit_groups): Do NULL pointer check
	to 'lh->include_dirs' before accessing to it.
	(psymtab_include_file_name): Likewise.
	(dwarf_decode_lines_1): Likewise.
	(dwarf_decode_lines): Likewise.
	(file_file_name): Likewise.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] gdb/copyright.py: Remove sim/erc32 files from NOT_FSF_LIST.
@ 2015-05-08 17:11 sergiodj+buildbot
  2015-05-08 18:48 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-05-08 17:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 80b0912bff495fd51e34050637357aeb243eefbb ***

Author: Joel Brobecker <brobecker@adacore.com>
Branch: master
Commit: 80b0912bff495fd51e34050637357aeb243eefbb

gdb/copyright.py: Remove sim/erc32 files from NOT_FSF_LIST.
Now that the erc32 files have been updated to contain an FSF copyright
header, these files should no longer be in the exclude list.

gdb/ChangeLog:

        * copyright.py (NOT_FSF_LIST): Remove sim/erc32 entries.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Further document ada-lang.c::value_assign_to_component & fix whitespaces.
@ 2015-05-05 22:44 sergiodj+buildbot
  2015-05-06  5:38 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-05-05 22:44 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7c5127443be1d3d0477b3b1d25875023992409bc ***

Author: Joel Brobecker <brobecker@adacore.com>
Branch: master
Commit: 7c5127443be1d3d0477b3b1d25875023992409bc

Further document ada-lang.c::value_assign_to_component & fix whitespaces.
This patch improves the documentation of ada-lang.c's
value_assign_to_component to publish the fact that it also works
with not_lval values.

And touching this area of the code showed that there were a number
of whitespace issues, as well as a formatting issue of the main comment
(no leading '*' on each line). This patch fixes those while at it.

No functional change, however.

gdb/ChangeLog:

        * ada-lang.c (value_assign_to_component): Reformat and improve
        documentation. Remove all trailing spaces.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] GDB crash trying to subscript array of variant record.
@ 2015-05-05 21:47 sergiodj+buildbot
  2015-05-05 22:55 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-05-05 21:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fc958966e47f622d738088509bacd0573a9db2c7 ***

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

GDB crash trying to subscript array of variant record.
Consider the following declarations:

   subtype Small_Type is Integer range 0 .. 10;
   type Record_Type (I : Small_Type := 0) is record
      S : String (1 .. I);
   end record;
   A2 : Array_Type := (1 => (I => 2, S => "AB"),
                       2 => (I => 1, S => "A"),
                       3 => (I => 0, S => <>));

Compiled with -fgnat-encodings=minimal, and trying to print
one element of our array, valgrind reports an invalid memory
access. On certain GNU/Linux boxes, malloc even reports it as
well, and causes GDB to crash.

    (gdb) print a2(1)
     *** glibc detected *** /[...]/gdb:
         malloc(): memory corruption: 0x0a30ba48 ***
    [crash]

The invalid memory access occurs because of a simple buffer
overflow in ada_value_primitive_packed_val. When this function
is called, it is given a bit_size of 128 (or 16 bytes), which
corresponds to the stride of our array. But the actual size of
each element depends on its value. In particular, A2(1) is a record
whose size is only 6 bytes.

What happens in our example is that we start building a new value
(v) where the element is to be unpacked, with any of its dynamic
properties getting resolved as well. We then unpack the data into
this value's buffer:

  unpacked = (unsigned char *) value_contents (v);
  [...]
  nsrc = len;
  [...]
  while (nsrc > 0)
    {
      [...]
          unpacked[targ] = accum & ~(~0L << HOST_CHAR_BIT);
          [...]
          targ += delta;
      [...]
      nsrc -= 1;
      [...]
    }

In the loop above, targ starts at zero (for LE architectures),
and len is 16. With delta being +1, we end up iterating 16 times,
writing 16 bytes into a 6-bytes buffer.

This patch fixes the issue by adjusting BIT_SIZE and recomputing
LEN after having resolved our type if the resolved type turns out
to be smaller than bit_size.

gdb/ChangeLog:

        * ada-lang.c (ada_value_primitive_packed_val): Recompute
        BIT_SIZE and LEN if the size of the resolved type is smaller
        than BIT_SIZE * HOST_CHAR_BIT.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] testsuite/gdb.ada/var_rec_arr: New testcase.
@ 2015-05-05 20:39 sergiodj+buildbot
  2015-05-06  0:38 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-05-05 20:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 87b8eff03fa5cd49c4829656c3d36bb3386dd6be ***

Author: Joel Brobecker <brobecker@adacore.com>
Branch: master
Commit: 87b8eff03fa5cd49c4829656c3d36bb3386dd6be

testsuite/gdb.ada/var_rec_arr: New testcase.
gdb/testsuite/ChangeLog:

        * gdb.ada/var_rec_arr: New testcase.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Add valaddr support in dynamic property resolution.
@ 2015-05-05 19:07 sergiodj+buildbot
  2015-05-05 19:53 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-05-05 19:07 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c3345124196f9d0439db35c16b5d24d1a305ccdd ***

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

Add valaddr support in dynamic property resolution.
This is the second part of enhancing the debugger to print the value
of arrays of records whose size is variable when only standard DWARF
info is available (no GNAT encoding). For instance:

   subtype Small_Type is Integer range 0 .. 10;
   type Record_Type (I : Small_Type := 0) is record
      S : String (1 .. I);
   end record;
   type Array_Type is array (Integer range <>) of Record_Type;

   A1 : Array_Type := (1 => (I => 0, S => <>),
                       2 => (I => 1, S => "A"),
                       3 => (I => 2, S => "AB"));

Currently, GDB prints the following output:

        (gdb) p a1
        $1 = (

The error happens while the ada-valprint module is trying to print
the value of an element of our array. Because of the fact that
the array's element (type Record_Type) has a variant size, the DWARF
info for our array provide the array's stride:

     <1><749>: Abbrev Number: 10 (DW_TAG_array_type)
        <74a>   DW_AT_name        : (indirect string, offset: 0xb6d): pck__T18s
        <74e>   DW_AT_byte_stride : 16
        <74f>   DW_AT_type        : <0x6ea>

And because our array has a stride, ada-valprint treats it the same
way as packed arrays (see ada-valprint.c::ada_val_print_array):

  if (TYPE_FIELD_BITSIZE (type, 0) > 0)
    val_print_packed_array_elements (type, valaddr, offset_aligned,
                                     0, stream, recurse,
                                     original_value, options);

The first thing that we should notice in the call above is that
the "valaddr" buffer and the associated offset (OFFSET_ALIGNED)
is passed, but that the corresponding array's address is not.
This can be explained by looking inside val_print_packed_array_elements,
where we see that the function unpacks each element of our array from
the buffer alone (ada_value_primitive_packed_val), and then prints
the resulting artificial value instead:

      v0 = ada_value_primitive_packed_val (NULL, valaddr + offset,
                                           (i0 * bitsize) / HOST_CHAR_BIT,
                                           (i0 * bitsize) % HOST_CHAR_BIT,
                                           bitsize, elttype);

      [...]
              val_print (elttype, value_contents_for_printing (v0),
                         value_embedded_offset (v0), 0, stream,
                         recurse + 1, v0, &opts, current_language);

Of particular interest, here, is the fact that we call val_print
with a null address, which is OK, since we're providing a buffer
instead (value_contents_for_printing). Also, providing an address
might not always possible, since packing could place elements at
boundaries that are not byte-aligned.

Things go south when val_print tries to see if there is a pretty-printer
that could be applied. In particular, one of the first things that
the Python pretty-printer does is to create a value using our buffer,
and the given address, which in this case is null (see call to
value_from_contents_and_address in gdbpy_apply_val_pretty_printer).

value_from_contents_and_address, in turn immediately tries to resolve
the type, using the given address, which is null. But, because our
array element is a record containing an array whose bound is the value
of one of its elements (the "s" component), the debugging info for
the array's upper bound is a reference...

 <3><71a>: Abbrev Number: 7 (DW_TAG_subrange_type)
    <71b>   DW_AT_type        : <0x724>
    <71f>   DW_AT_upper_bound : <0x703>

... to component "i" of our record...

 <2><703>: Abbrev Number: 5 (DW_TAG_member)
    <704>   DW_AT_name        : i
    <706>   DW_AT_decl_file   : 2
    <707>   DW_AT_decl_line   : 6
    <708>   DW_AT_type        : <0x6d1>
    <70c>   DW_AT_data_member_location: 0

... where that component is located at offset 0 of the start
of the record. dwarf2_evaluate_property correctly determines
the offset where to load the value of the bound from, but then
tries to read that value from inferior memory using the address
that was given, which is null. See case PROP_ADDR_OFFSET in
dwarf2_evaluate_property:

        val = value_at (baton->offset_info.type,
                        pinfo->addr + baton->offset_info.offset);

This triggers a memory error, which then causes the printing to terminate.

Since there are going to be situations where providing an address
alone is not going to be sufficient (packed arrays where array elements
are not stored at byte boundaries), this patch fixes the issue by
enhancing the type resolution to take both address and data. This
follows the same principle as the val_print module, where both
address and buffer ("valaddr") can be passed as arguments. If the data
has already been fetched from inferior memory (or provided by the
debugging info in some form -- Eg a constant), then use that data
instead of reading it from inferior memory.

Note that this should also be a good step towards being able to handle
dynamic types whose value is stored outside of inferior memory
(Eg: in a register).

With this patch, GDB isn't able to print all of A1, but does perform
a little better:

    (gdb) p a1
    $1 = ((i => 0, s => , (i => 1, s => , (i => 2, s => )

There is another issue which is independent of this one, and will
therefore be patched separately.

gdb/ChangeLog:

        * dwarf2loc.h (struct property_addr_info): Add "valaddr" field.
        * dwarf2loc.c (dwarf2_evaluate_property): Add handling of
        pinfo->valaddr.
        * gdbtypes.h (resolve_dynamic_type): Add "valaddr" parameter.
        * gdbtypes.c (resolve_dynamic_struct): Set pinfo.valaddr.
        (resolve_dynamic_type_internal): Set pinfo.valaddr.
        Add handling of addr_stack->valaddr.
        (resolve_dynamic_type): Add "valaddr" parameter.
        Set pinfo.valaddr field.
        * ada-lang.c (ada_discrete_type_high_bound): Update call to
        resolve_dynamic_type.
        (ada_discrete_type_low_bound): Likewise.
        * findvar.c (default_read_var_value): Likewise.
        * value.c (value_from_contents_and_address): Likewise.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Make RL78 disassembler and simulator respect ISA for mul/div
@ 2015-04-30 19:45 sergiodj+buildbot
  2015-04-30 20:28 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-30 19:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0952813b0b27abe7f53a8048c0218883412e54cd ***

Author: DJ Delorie <dj@redhat.com>
Branch: master
Commit: 0952813b0b27abe7f53a8048c0218883412e54cd

Make RL78 disassembler and simulator respect ISA for mul/div
[gas]
	* config/rl78-defs.h (rl78_isa_g10): New.
	(rl78_isa_g13): New.
	(rl78_isa_g14): New.
	* config/rl78-parse.y (ISA_G10): New.
	(ISA_G13): New.
	(ISA_G14): New.
	(MULHU, MULH, MULU, DIVHU, DIVWU, MACHU, MACH): Use them.
	* config/tc-rl78.c (rl78_isa_g10): New.
	(rl78_isa_g13): New.
	(rl78_isa_g14): New.

[gdb]
	* rl78-tdep.c (rl78_analyze_prologue): Pass RL78_ISA_DEFAULT to
	rl78_decode_opcode

[include]
	* dis-asm.h (print_insn_rl78_g10): New.
	(print_insn_rl78_g13): New.
	(print_insn_rl78_g14): New.
	(rl78_get_disassembler): New.
	* opcode/rl78.h (RL78_Dis_Isa): New.
	(rl78_decode_opcode): Add ISA parameter.

[opcodes]
	* disassemble.c (disassembler): Choose suitable disassembler based
	on E_ABI.
	* rl78-decode.opc (rl78_decode_opcode): Take ISA parameter.  Use
	it to decode mul/div insns.
	* rl78-decode.c: Regenerate.
	* rl78-dis.c (print_insn_rl78): Rename to...
	(print_insn_rl78_common): ...this, take ISA parameter.
	(print_insn_rl78): New.
	(print_insn_rl78_g10): New.
	(print_insn_rl78_g13): New.
	(print_insn_rl78_g14): New.
	(rl78_get_disassembler): New.

[sim]
	* rl78/cpu.c (g14_multiply): New.
	* rl78/cpu.h (g14_multiply): New.
	* rl78/load.c (rl78_load): Decode ISA completely.
	* rl78/main.c (main): Expand -M to include other ISAs.
	* rl78/rl78.c (decode_opcode): Decode based on ISA.
	* rl78/trace.c (rl78_disasm_fn): New.
	(sim_disasm_init): Reset it.
	(sim_disasm_one): Get correct disassembler for ISA.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Fix handling of relocs for the MeP target.
@ 2015-04-30 15:38 sergiodj+buildbot
  2015-04-30 16:00 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-30 15:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 153a27763ccc9979fdb5f342e21eb1666c8f117b ***

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

Fix handling of relocs for the MeP target.
bfd	PR 18317
	* elf32-mep.c (MEPREL): Use bfd_elf_generic_reloc instead of
	mep_reloc.
	(mep_reloc): Delete unused function.

bin	* readelf.c (get_machine_flags): Add description of MeP flags.

tests	* binutils-all/objdump.exp (cpus_expected): Add MeP CPU names.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Updated translations for various binutils components.
@ 2015-04-29 17:01 sergiodj+buildbot
  2015-04-29 20:11 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-29 17:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f9d3ecaa788c7969002f08459471a54a61b3c07f ***

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

Updated translations for various binutils components.
gold	* po/fi.po: Updated Finnish translation.

opcodes	* po/fr.po: Updated French translation.

gprof	* po/da.po: Update Danish translation.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Allow passing fd == NULL to exec_file_find and solib_find
@ 2015-04-29 14:34 sergiodj+buildbot
  2015-04-29 15:21 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-29 14:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 998d2a3ef31378d3d980972dc68f4926b720a7e9 ***

Author: Gary Benson <gbenson@redhat.com>
Branch: master
Commit: 998d2a3ef31378d3d980972dc68f4926b720a7e9

Allow passing fd == NULL to exec_file_find and solib_find
This commit allows NULL to be passed as the int *fd argument
to exec_file_find and solib_find to simplify use cases where
the caller does not require the file to be opened.

gdb/ChangeLog:

	* solib.c (solib_find_1): Allow fd argument to be NULL.
	(exec_file_find): Update comment.
	(solib_find): Likewise.
	* exec.c (exec_file_locate_attach): Use NULL as fd
	argument to exec_file_find to avoid having to close
	the opened file.
	* infrun.c (follow_exec): Likewise.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Use "gdb_wait.h" instead of <sys/wait.h>.
@ 2015-04-28 18:59 sergiodj+buildbot
  2015-04-29  1:45 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-28 18:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cea6e4f13a8df0eddbcdf643a4fc4727cbf770a7 ***

Author: John Baldwin <jhb@FreeBSD.org>
Branch: master
Commit: cea6e4f13a8df0eddbcdf643a4fc4727cbf770a7

Use "gdb_wait.h" instead of <sys/wait.h>.
gdb/ChangeLog:
	* fbsd-nat.c: Include "gdb_wait.h" instead of <sys/wait.h>.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Enable fork tracing for native FreeBSD targets.
@ 2015-04-27 23:43 sergiodj+buildbot
  2015-04-28 11:15 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-27 23:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e58e05d677d33da3646721bdd225ec6e90424000 ***

Author: John Baldwin <jhb@FreeBSD.org>
Branch: master
Commit: e58e05d677d33da3646721bdd225ec6e90424000

Enable fork tracing for native FreeBSD targets.
Enable PT_FOLLOW_FORK on all processes.  When this is enabled, both
the parent and child process stop when a fork or vfork occurs.

A target operation for wait uses PT_LWPINFO to fetch more detailed
information about the state of a stopped process.  A parent process
sets the PL_FLAG_FORKED flag in the pl_flags field of the structure
returned by PT_LWPINFO as well as the pid of the new child process.
The child process sets the PL_FLAG_CHILD flag in the pl_flags field.

When a fork is detected, the wait hook waits for both processes to
report their respective events.  It then reports the fork to GDB as
a single TARGET_WAITKIND_FORKED or TARGET_WAITKIND_VFORKED event.
The kernel does not guarantee the order the events are reported in.
If the parent process' event is reported first, then the wait hook
explicitly waits for the child process.  If the child process' event
is reported first, the event is recorded on an internal list of
pending child events and the wait hook waits for another event.
Later when the parent process' event is reported, the parent will
use the previously-recorded child process event instead of explicitly
waiting on the child process.

To distinguish vfork events from fork events, the external process
structure for the child process is extracted from the kernel.  The
P_PPWAIT flag is set in the ki_flags field of this structure if the
process was created via vfork, but it is not set for a regular fork.

gdb/ChangeLog:

	* fbsd-nat.c: [PT_LWPINFO] New variable super_wait.
	[TDP_RFPPWAIT] New variable fbsd_pending_children.
	[TDP_RFPPWAIT] (fbsd_remember_child): New function.
	[TDP_RFPPWAIT] (fbsd_is_child_pending): New function.
	[TDP_RFPPWAIT] (fbsd_fetch_kinfo_proc): New function.
	[PT_LWPINFO] (fbsd_wait): New function.
	[TDP_RFPPWAIT] (fbsd_follow_fork): New function.
	[TDP_RFPPWAIT] (fbsd_insert_fork_catchpoint): New function.
	[TDP_RFPPWAIT] (fbsd_remove_fork_catchpoint): New function.
	[TDP_RFPPWAIT] (fbsd_insert_vfork_catchpoint): New function.
	[TDP_RFPPWAIT] (fbsd_remove_vfork_catchpoint): New function.
	[TDP_RFPPWAIT] (fbsd_enable_follow_fork): New function.
	[TDP_RFPPWAIT] (fbsd_post_startup_inferior): New function.
	[TDP_RFPPWAIT] (fbsd_post_attach): New function.
	(fbsd_nat_add_target) [PT_LWPINFO] Set "to_wait" to
	"fbsd_wait".
	[TDP_RFPPWAIT] Set "to_follow_fork" to "fbsd_follow_fork".
	Set "to_insert_fork_catchpoint" to "fbsd_insert_fork_catchpoint".
	Set "to_remove_fork_catchpoint" to "fbsd_remove_fork_catchpoint".
	Set "to_insert_vfork_catchpoint" to "fbsd_insert_vfork_catchpoint".
	Set "to_remove_vfork_catchpoint" to "fbsd_remove_vfork_catchpoint".
	Set "to_post_startup_inferior" to "fbsd_post_startup_inferior".
	Set "to_post_attach" to "fbsd_post_attach".


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Add fbsd_nat_add_target.
@ 2015-04-27 23:34 sergiodj+buildbot
  2015-04-28  6:13 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-27 23:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8f60fe014dd0afdc1013fc22a3ef5ba01e94e331 ***

Author: John Baldwin <jhb@FreeBSD.org>
Branch: master
Commit: 8f60fe014dd0afdc1013fc22a3ef5ba01e94e331

Add fbsd_nat_add_target.
Add a wrapper for add_target in fbsd-nat.c to override target operations
common to all native FreeBSD targets.

gdb/ChangeLog:

	* fbsd-nat.c (fbsd_pid_to_exec_file): Mark static.
	(fbsd_find_memory_regions): Mark static.
	(fbsd_nat_add_target): New function.
	* fbsd-nat.h: Export fbsd_nat_add_target and remove prototypes for
	fbsd_pid_to_exec_file and fbsd_find_memory_regions.
	* amd64fbsd-nat.c (_initialize_amd64fbsd_nat): Use fbsd_nat_add_target.
	* i386fbsd-nat.c (_initialize_i386fbsd_nat): Likewise.
	* ppcfbsd-nat.c (_initialize_ppcfbsd_nat): Likewise.
	* sparc64fbsd-nat.c (_initialize_sparc64fbsd_nat): Likewise.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Clear variable "coredump_var_addr" before using it on gdb.base/coredump-filter.exp
@ 2015-04-26 19:52 sergiodj+buildbot
  2015-04-26 20:40 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-26 19:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2d369d8e973f1507689a7f200c16e154ec5d6c79 ***

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

Clear variable "coredump_var_addr" before using it on gdb.base/coredump-filter.exp
This commit is a continuation of the fix committed on:

  commit 8cd8f2f8ac49276437b7da37f275706ea1c1c925
  Author: Sergio Durigan Junior <sergiodj@redhat.com>
  Date:   Mon Apr 13 02:40:08 2015 -0400

      Rename variable "addr" to "coredump_var_addr" in gdb.base/coredump-filter.exp

Pedro pointed out that this fix was not complete, because the
testsuite could be run several times in a row (for example), which
means that it is not enough to just make the variable name unique: it
also needs to be cleared out if it is global.

This commit does that.  It is actually just a commit made to make
things totally correct; this specific test does not fail if you run it
several times in a row.

gdb/testsuite/ChangeLog:
2015-04-26  Sergio Durigan Junior  <sergiodj@redhat.com>

	* gdb.base/coredump-filter.exp: Clear variable "coredump_var_addr"
	before using it.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] gdb: Add internationalization support to a few strings.
@ 2015-04-25  0:02 sergiodj+buildbot
  2015-04-25 10:53 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-25  0:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6faec16b1c633a8043791e0d15d7e7f1c8d448c1 ***

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

gdb: Add internationalization support to a few strings.
Spotted a few strings that were missing internationalization support.

gdb/ChangeLog:

	* cli/cli-dump.c (srec_dump_command): Add internationalization
	mark ups.
	(ihex_dump_command): Likewise.
	(tekhex_dump_command): Likewise.
	(binary_dump_command): Likewise.
	(binary_append_command): Likewise.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Fix typos in sim sources exposed by static analysis.
@ 2015-04-24 16:12 sergiodj+buildbot
  2015-04-24 18:14 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-24 16:12 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT de7669bfa507d78f7abfe3d219b5aee9f346235e ***

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

Fix typos in sim sources exposed by static analysis.
bfin	PR 18273
	* bfin-sim.c (decode_dsp32alu_0): Remove spurious check for
	s == 1.

erc32	PR 18273
	* exec.c (add32): Fix typo in check for overflow.

igen	PR 18273
	* misc.c (a2i): Fix typos checking for uppercase letters.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Don't change compressed input debug section names
@ 2015-04-23 19:08 sergiodj+buildbot
  2015-04-23 20:14 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-23 19:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f6fe1ccd62e4492aabda6a9a9d12da438d0ebf2b ***

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

Don't change compressed input debug section names
Change compressed input debug section name for objdump is very confusing.
But we need to change it for linker so that linker will consider the
input section as a debug section.  This patch delays section rename to
elf_fake_sections for objcopy and avoids it for objdump.

bfd/

	PR binutils/18209
	* bfd.c (bfd): Add is_linker_input.
	* elf.c (convert_debug_to_zdebug): New.
	(convert_zdebug_to_debug): Likewise.
	(_bfd_elf_make_section_from_shdr): Don't convert .debug_* to
	.zdebug_* here.  Use convert_zdebug_to_debug.  Set SEC_ELF_RENAME.
	(_bfd_elf_init_reloc_shdr): Pass a pointer to section name
	instead of a pointer to section.
	(elf_fake_sections): Rename the section name if SEC_ELF_RENAME
	is set.
	* section.c (SEC_ELF_RENAME): New.
	* bfd-in2.h: Regenerated.

binutils/

	PR binutils/18209
	* objcopy.c (setup_section): Copy compress status.

binutils/testsuite/

	PR binutils/18209
	* binutils-all/compress.exp: Replace dw2-3.W with dw2-3gabi.W
	on zlib-gabi output.
	* binutils-all/dw2-1.W: Convert section names to .zdebug_*.
	* binutils-all/dw2-3.W: Likewise.
	* binutils-all/objdump.W: Likewise.
	* binutils-all/dw2-3gabi.W: New file.

ld/

	PR binutils/18209
	* ldfile.c (ldfile_try_open_bfd): Set is_linker_input to 1.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Fix gdb.base/interrupt.exp racy fail against gdbserver
@ 2015-04-23 16:47 sergiodj+buildbot
  2015-04-23 19:17 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-23 16:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4ef9fb2f075daec3885c63aa2056075bdd94384b ***

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

Fix gdb.base/interrupt.exp racy fail against gdbserver
Currently, against gdbserver, interrupt.exp occasionaly fails like
this:

 ERROR: Process no longer exists
 UNRESOLVED: gdb.base/interrupt.exp: send end of file

The problem is that we see gdbserver exiting before we match gdb's
output:

 expect: does "\r\n\r\nChild exited with status 0\r\nGDBserver exiting\r\n" (spawn_id exp8) match regular expression "end of file"? Gate "end of file"? gate=no
 expect: read eof
 expect: set expect_out(spawn_id) "exp8"
 expect: set expect_out(buffer) "\r\n\r\nChild exited with status 0\r\nGDBserver exiting\r\n"

Fix this by removing $inferior_spawn_id from the set of spawn ids
expect is watching as soon as we see the "end of file" string out of
the inferior spawn id, using an indirect spawn id list.

Tested on x86-64 Fedora 20, native and gdbserver (both target remote
and extended-remote).

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

	* gdb.base/interrupt.exp: Use an indirect spawn id list holding
	$inferior_spawn_id instead of $inferior_spawn_id directly.  On
	"end of file", remove $inferior_spawn_id from the indirect list.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] x86: disambiguate disassembly of certain AVX512 insns
@ 2015-04-23 14:57 sergiodj+buildbot
  2015-04-23 15:43 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-23 14:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 04d824a468650c632d228b977006139f17d646a4 ***

Author: Jan Beulich <jbeulich@novell.com>
Branch: master
Commit: 04d824a468650c632d228b977006139f17d646a4

x86: disambiguate disassembly of certain AVX512 insns
Certain conversion operations as well as vfpclassp{d,s} are ambiguous
when the input operand is in memory and no broadcast is being used.
While in Intel mode this gets resolved by printing suitable operand
size modifiers, AT&T mode need mnemonic suffixes to be added.

gas/testsuite/
2015-04-23  Jan Beulich  <jbeulich@suse.com>

	* gas/i386/avx512dq.d: Add 'z' suffix to vfpclassp{d,s} non-
	register, non-broadcast cases.
	* gas/i386/x86-64-avx512dq.d: Likewise.
	* gas/i386/avx512dq_vl.d: Add 'x' and 'y' suffixes to
	vcvt{,u}qq2ps and vfpclassp{d,s} non-register, non-broadcast
	cases.
	* gas/i386/x86-64-avx512dq_vl.d: Likewise.
	* gas/i386/avx512f_vl.d: Add 'x' and 'y' suffixes to
	vcvt{,t}pd2{,u}dq and vcvtpd2ps non-register, non-broadcast
	cases.
	* gas/i386/x86-64-avx512f_vl.d: Likewise.

opcodes/
2015-04-23  Jan Beulich  <jbeulich@suse.com>

	* i386-dis.c (putop): Extend "XY" handling to AVX512. Handle "XZ".
	* i386-dis-evex.h.c (vcvtpd2ps, vcvtqq2ps, vcvttpd2udq,
	vcvtpd2udq, vcvtuqq2ps, vcvttpd2dq, vcvtpd2dq): Add %XY.
	(vfpclasspd, vfpclassps): Add %XZ.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Align .TOC. for PowerPC64
@ 2015-04-23  0:56 sergiodj+buildbot
  2015-04-23  9:23 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-23  0:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a27e685fa0a6480bdb07e3be359558524cec89b7 ***

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

Align .TOC. for PowerPC64
This change, with prerequisite 0e5fabeb, provides a toc base aligned
to 256 bytes rather than 8 bytes.  This is necessary for a minor gcc
optimisation, allowing use of d-form instructions to correctly access
toc-relative items larger than 8 bytes.

bfd/
	* elf64-ppc.c (TOC_BASE_ALIGN): Define.
	(ppc64_elf_next_toc_section): Align multi-got toc base.
	(ppc64_elf_set_toc): Likewise initial toc base and .TOC. symbol.
ld/
	* emulparams/elf64ppc.sh (GOT): Align.
ld/testsuite/
	* ld-powerpc/ambiguousv1b.d: Update for aligned .got.
	* ld-powerpc/defsym.d: Likewise.
	* ld-powerpc/elfv2-2exe.d: Likewise.
	* ld-powerpc/elfv2exe.d: Likewise.
	* ld-powerpc/elfv2so.d: Likewise.
	* ld-powerpc/relbrlt.d: Likewise.
	* ld-powerpc/tls.g: Likewise.
	* ld-powerpc/tlsexe.d: Likewise.
	* ld-powerpc/tlsexe.g: Likewise.
	* ld-powerpc/tlsexe.r: Likewise.
	* ld-powerpc/tlsexetoc.d: Likewise.
	* ld-powerpc/tlsexetoc.g: Likewise.
	* ld-powerpc/tlsexetoc.r: Likewise.
	* ld-powerpc/tlsso.d: Likewise.
	* ld-powerpc/tlsso.g: Likewise.
	* ld-powerpc/tlsso.r: Likewise.
	* ld-powerpc/tlstoc.g: Likewise.
	* ld-powerpc/tlstocso.d: Likewise.
	* ld-powerpc/tlstocso.g: Likewise.
	* ld-powerpc/tlstocso.r: Likewise.
	* ld-powerpc/tocopt.d: Likewise.
	* ld-powerpc/tocopt2.d: Likewise.
	* ld-powerpc/tocopt3.d: Likewise.
	* ld-powerpc/tocopt4.d: Likewise.
	* ld-powerpc/tocopt5.d: Likewise.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] libiberty/setenv.c: Do not declare environ if defined as a macro.
@ 2015-04-22 20:56 sergiodj+buildbot
  2015-04-23  3:22 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-22 20:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT dfc0f57b741c12a94520c9ec7f726755eac1d2de ***

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

libiberty/setenv.c: Do not declare environ if defined as a macro.
Otherwise, it causes a build warning on some platforms such as MinGW.

libiberty/ChangeLog (Eli Zaretskii  <eliz@gnu.org>):

        * setenv.c <environ>: Declare only if not a macro.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] windows-nat: Fix misspelling in debug output
@ 2015-04-22 19:19 sergiodj+buildbot
  2015-04-22 21:03 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-22 19:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 23942819fca67effa062a9639be5df3fb074b322 ***

Author: Jon Turney <jon.turney@dronecode.org.uk>
Branch: master
Commit: 23942819fca67effa062a9639be5df3fb074b322

windows-nat: Fix misspelling in debug output
gdb/ChangeLog:

2015-04-16  Jon Turney  <jon.turney@dronecode.org.uk>

	* windows-nat.c (windows_resume): Fix misspelling in debug output.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] windows-nat: Cleanups in get_windows_debug_event
@ 2015-04-22 18:55 sergiodj+buildbot
  2015-04-22 20:04 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-22 18:55 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e6ad66bd097f17ec32c03462dd65b7f833fd49ab ***

Author: Jon Turney <jon.turney@dronecode.org.uk>
Branch: master
Commit: e6ad66bd097f17ec32c03462dd65b7f833fd49ab

windows-nat: Cleanups in get_windows_debug_event
gdb/ChangeLog:

2015-04-16  Jon Turney  <jon.turney@dronecode.org.uk>

	* windows-nat.c (get_windows_debug_event): Replace retval with
	thread_id throughout.  Update stale comment.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] i386: Allow copy relocs for building PIE
@ 2015-04-22 12:45 sergiodj+buildbot
  2015-04-22 13:55 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-22 12:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d5597ebccca6761fb641b7fc99b6e8b56fbac6e2 ***

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

i386: Allow copy relocs for building PIE
This patch allows copy relocs for R_386_GOTOFF relocations in PIE.  For

extern int glob_a;
int foo ()
{
  return glob_a;
}

compiler now can optimize it from

	call	__x86.get_pc_thunk.ax
	addl	$_GLOBAL_OFFSET_TABLE_, %eax
	movl	glob_a@GOT(%eax), %eax
	movl	(%eax), %eax
	ret

to

	call	__x86.get_pc_thunk.ax
	addl	$_GLOBAL_OFFSET_TABLE_, %eax
	movl	glob_a@GOTOFF(%eax), %eax
	ret

bfd/

	PR ld/18289
	* elf32-i386.c (elf_i386_link_hash_entry): Add gotoff_ref.
	(elf_i386_link_hash_newfunc): Initialize gotoff_ref to 0.
	(elf_i386_create_dynamic_sections): Always allow copy relocs for
	building executables.
	(elf_i386_copy_indirect_symbol): Also copy gotoff_ref.
	(elf_i386_check_relocs): Set gotoff_ref for R_386_GOTOFF.
	(elf_i386_adjust_dynamic_symbol): Also allocate copy relocs for
	PIE and R_386_GOTOFF.
	(elf_i386_relocate_section): Allow R_386_GOTOFF in executable.

ld/testsuite/

	PR ld/18289
	* ld-i386/copyreloc-lib.c: New file.
	* ld-i386/copyreloc-main.S: Likewise.
	* ld-i386/copyreloc-main.out: Likewise.
	* ld-i386/copyreloc-main1.rd: Likewise.
	* ld-i386/copyreloc-main2.rd: Likewise.
	* ld-i386/dummy.c: Likewise.
	* ld-i386/pr17689.out: Likewise.
	* ld-i386/pr17689.rd: Likewise.
	* ld-i386/pr17689a.c: Likewise.
	* ld-i386/pr17689b.S: Likewise.
	* ld-i386/pr17827.rd: Likewise.
	* ld-i386/pr17827ver.rd: Likewise.
	* ld-i386/i386.exp: Run copyreloc tests.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Fix pascal behavior for class fields with testcase
@ 2015-04-21 20:33 sergiodj+buildbot
  2015-04-21 21:21 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-21 20:33 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8aae434443df61440ff5228f5c8fe3e5d4a38798 ***

Author: Pierre Muller <muller@ics.u-strasbg.fr>
Branch: master
Commit: 8aae434443df61440ff5228f5c8fe3e5d4a38798

Fix pascal behavior for class fields with testcase
  Problem reported as PR pascal/17815

Part 1/3: Remember the case pattern that allowed finding a field of this.
File gdb/p-exp.y modified

  This is the fix in the pascal parser (p-exp.y),
to avoid the error that GDB does find normal variables
case insensitively, but not fields of this,
inside a class or object method.

Part 2/3: Add "class" option for pascal compiler
File gdb/testsuite/lib/pascal.exp

This part of the patch series is unchanged.
It adds class option to pascal compiler
which adds the required command line option to
accept pascal class types.

Part 3/3:
New file: gdb/testsuite/gdb.pascal/case-insensitive-symbols.exp
New file: gdb/testsuite/gdb.pascal/case-insensitive-symbols.pas

  Here is an updated version of this test, using Pedro's suggestions.
Test to check that PR 17815 is fixed.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] sim: mcore: clean up printf warnings
@ 2015-04-21 10:25 sergiodj+buildbot
  2015-04-21 14:24 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-21 10:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 43236bb2551a9783ff0de5e95bf75f905300eb06 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 43236bb2551a9783ff0de5e95bf75f905300eb06

sim: mcore: clean up printf warnings
These printf statements are showing "word" objects which are typedefed
from long, so make sure to use l with %x when printing them to avoid
warnings from gcc.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] sim: mcore: drop watchpoint/dumpmem/clearstats support
@ 2015-04-21  9:14 sergiodj+buildbot
  2015-04-21 11:48 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-21  9:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e53e5aab53a455c791fff754d72fd17cbbc6b4a8 ***

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

sim: mcore: drop watchpoint/dumpmem/clearstats support
In preparation for converting to the common memory framework, the custom
commands get in our way.  But when we realize that gdb support has been
dropped for mcore, it makes things a bit easier: the main runner does not
let you run arbitrary commands once simulation starts.

So lets disable watchpoint support until it can be converted to the common
watchpoint logic.  There's already an ifdef to let us do that.

We straight up drop support for the dumpmem command (no other sim supports
this, and if it's a feature people want, we can add a common func) and the
clearstats command (not a big deal -- just restart your simulation).

We leave in place the verbose check points as a follow up commit will cut
that over to common logic.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Extend rl78 prologue analyzer to recognize more complicated prologues
@ 2015-04-21  7:11 sergiodj+buildbot
  2015-04-21  8:09 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-21  7:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0bca7f99d8fa254b5e35a211ee306a46b95adc65 ***

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

Extend rl78 prologue analyzer to recognize more complicated prologues
This patch extends the rl78 prologue analyzer so that it can recognize
this kind of prologue:

   0x119f <main>:       movw    ax, sp
   0x11a1 <main+2>:     subw    ax, #0x1fa6
   0x11a4 <main+5>:     movw    sp, ax

The test case for gdb.base/miscexprs.exp is now compiled to generate
that sequence instead of a much longer and more inefficient sequence.

gdb/ChangeLog:

	* rl78-tdep.c (RL78_SP_ADDR): Define.
	(opc_reg_to_gdb_regnum): New static function.
	(rl78_analyze_prologue): Recognize instructions forming slightly
	more interesting prologues.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Always set up sh_name in assign_section_numbers
@ 2015-04-20 20:12 sergiodj+buildbot
  2015-04-20 20:53 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-20 20:12 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e97029632cfacf9d8b65e2cf3051a932f19f9ebf ***

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

Always set up sh_name in assign_section_numbers
commit 9ad5cbcfb23cb74d34bd04f88f4e47c0f5de5155 added the initial support
for more than 64k ELF sections with holes for reserved section indices in
section header table and set entries of reserved section indices in
section header table to index 0:

   for (secn = 1; secn < section_number; ++secn)
-    i_shdrp[secn]->sh_name = _bfd_elf_strtab_offset (elf_shstrtab (abfd),
-                                                    i_shdrp[secn]->sh_name);
-
+    if (i_shdrp[secn] == NULL)
+      i_shdrp[secn] = i_shdrp[0];
+    else
+      i_shdrp[secn]->sh_name = _bfd_elf_strtab_offset (elf_shstrtab (abfd),
+							i_shdrp[secn]->sh_name);

commit 4fbb74a6055f7d48f09c44064073d3b1e99c6642 removed holes in section
header table.  Check for i_shdrp[secn] == NULL is no longer needed now.
This patch removes it.

	* elf.c (assign_section_numbers): Always set up sh_name.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Fix three test failures with extended remote targets
@ 2015-04-20 10:51 sergiodj+buildbot
  2015-04-20 11:59 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-20 10:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1586c8fbaf0116931ffacd1746a6540c81c2d438 ***

Author: Gary Benson <gbenson@redhat.com>
Branch: master
Commit: 1586c8fbaf0116931ffacd1746a6540c81c2d438

Fix three test failures with extended remote targets
This commit fixes three gdb.base/attach.exp failures when using
extended remote targets.  The failures occurred because GDB now
locates and loads files when attaching on remote targets if the
remote target supports qXfer:exec-file:read; the filenames were
shown but with "target:" prefixes which the test has been updated
to handle.

gdb/testsuite/ChangeLog:

	* gdb.base/attach.exp: Fix three extended remote failures.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Remove duplicated xmalloc in update_dprintf_command_list
@ 2015-04-20  0:29 sergiodj+buildbot
  2015-04-20  3:49 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-20  0:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e31d7699a0b116025b48f1ab5214eddd2e56ef9f ***

Author: Gabriel Krisman Bertazi <gabriel@krisman.be>
Branch: master
Commit: e31d7699a0b116025b48f1ab5214eddd2e56ef9f

Remove duplicated xmalloc in update_dprintf_command_list
Code in update_dprintf_command_list performed a duplicated memory
allocation which caused an obvious memory leak.  This removes the
duplication.

gdb/
2015-04-19  Gabriel Krisman Bertazi  <gabriel@krisman.be>

	* breakpoint.c (update_dprintf_command_list): Remove duplicated
	xmalloc.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [GDB] Hurd: Simplify the reply_mig_hack.awk script.
@ 2015-04-19 23:00 sergiodj+buildbot
  2015-04-19 23:42 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-19 23:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d214e5e79e38b18bc3786b3e8ba0e55fdbba294b ***

Author: Thomas Schwinge <thomas@codesourcery.com>
Branch: master
Commit: d214e5e79e38b18bc3786b3e8ba0e55fdbba294b

[GDB] Hurd: Simplify the reply_mig_hack.awk script.
	gdb/
	* reply_mig_hack.awk: Don't bother to declare an intermediate
	function pointer variable.

... allowing us to simplify the parsing a little bit.  And, instead of
"warning: initialization from incompatible pointer type", we now get "warning:
function called through a non-compatible type".  Oh well.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] sim: clean up duplicate sim-engine hooks
@ 2015-04-18 10:30 sergiodj+buildbot
  2015-04-18 12:32 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-18 10:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3ebe2863f79e04d841e6b97594ec032d2bfad1b8 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 3ebe2863f79e04d841e6b97594ec032d2bfad1b8

sim: clean up duplicate sim-engine hooks
Now that we've unified sim-cpu, we can delete the duplicate sim-engine
hooks -- these targets defined these only because they didn't fully
implement the sim-cpu callbacks.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] sim: trim old USING_SIM_BASE_H define
@ 2015-04-18 10:18 sergiodj+buildbot
  2015-04-18 11:35 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-18 10:18 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e8d3a34fee495d7d44e6bf8e13d472b33f847635 ***

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

sim: trim old USING_SIM_BASE_H define
This doesn't appear to have been used since 1998, but wasn't cleaned
up since.  So much for being "quick" ;).


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] sim: unify sim_cia definition
@ 2015-04-18  8:40 sergiodj+buildbot
  2015-04-18  9:35 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-18  8:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7e83aa92f2d986ba60f124287a9fd1e534fbbcf8 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 7e83aa92f2d986ba60f124287a9fd1e534fbbcf8

sim: unify sim_cia definition
Almost every target defines sim_cia the same way -- either using the
address_word type directly, or a type of equivalent size.  The only
odd one out is sh64 (who has 32bit address_word and 64bit cia), and
even that case doesn't seem to make sense.  We'll put off clean up
though of sh64 and at least set up a sensible default for everyone.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] solib-svr4.c (svr4_exec_displacement): Rename outer "displacement".
@ 2015-04-17 18:36 sergiodj+buildbot
  2015-04-18  3:06 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-17 18:36 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8f61baf802b597c11fec288f840d9f7feb18eb0e ***

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

solib-svr4.c (svr4_exec_displacement): Rename outer "displacement".
gdb/ChangeLog:

	* solib-svr4.c (svr4_exec_displacement): Rename outer "displacement"
	to "exec_displacement" to avoid confusion with inner use of the name.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] gdbserver/xtensa: drop xtensa_usrregs_info
@ 2015-04-17 14:33 sergiodj+buildbot
  2015-04-17 21:41 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-17 14:33 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT deb44829ecc1dd38275af0fcf91acd319e227a89 ***

Author: Max Filippov <jcmvbkbc@gmail.com>
Branch: master
Commit: deb44829ecc1dd38275af0fcf91acd319e227a89

gdbserver/xtensa: drop xtensa_usrregs_info
xtensa_usrregs_info refers to undefined variables xtensa_num_regs and
xtensa_regmap. Drop xtensa_usrregs_info and replace pointer to usrregs
in regs_info with NULL since all registers are read/set through regsets.

2015-04-17  Max Filippov  <jcmvbkbc@gmail.com>
gdb/gdbserver/
	* linux-xtensa-low.c (xtensa_usrregs_info): Remove.
	(regs_info): Replace usrregs pointer with NULL.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Update comments to target_can_use_hardware_watchpoint
@ 2015-04-17 13:06 sergiodj+buildbot
  2015-04-17 19:23 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-17 13:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 059790a0c8f4672da9ed5a6289d1fd9edc0f169f ***

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

Update comments to target_can_use_hardware_watchpoint
The return value of target_can_use_hardware_watchpoint isn't well
documented, so this patch is to update the comments to reflect the
fact.  This patch also removes a trailing ";" which is picked up
from Pedro's patch https://sourceware.org/ml/gdb-patches/2015-04/msg00527.html

gdb:

2015-04-17  Yao Qi  <yao.qi@linaro.org>
	    Pedro Alves  <palves@redhat.com>

	* target.h (target_can_use_hardware_watchpoint): Update comments.
	Remove trailing ";".


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Introduce exec_file_find
@ 2015-04-17 11:01 sergiodj+buildbot
  2015-04-17 13:28 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-17 11:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT af1900b01b378126d8826591be7b7ec0d18271d7 ***

Author: Gary Benson <gbenson@redhat.com>
Branch: master
Commit: af1900b01b378126d8826591be7b7ec0d18271d7

Introduce exec_file_find
This commit adds a new function, exec_file_find, which computes the
full pathname of the main executable in much the same way solib_find
does for pathnames of shared libraries.  The bulk of the existing
solib_find was moved into a new static function solib_find_1, with
exec_file_find and solib_find being small wrappers for solib_find_1.

gdb/ChangeLog:

	* solist.h (exec_file_find): New declaration.
	* solib.c (solib_find_1): New function, factored out from...
	(solib_find): ...here.
	(exec_file_find): New function.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Introduce linux_proc_pid_to_exec_file
@ 2015-04-17 10:49 sergiodj+buildbot
  2015-04-17 15:26 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-17 10:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e0d86d2cbd168e083f3d077b8cfe67c3d03c1e5f ***

Author: Gary Benson <gbenson@redhat.com>
Branch: master
Commit: e0d86d2cbd168e083f3d077b8cfe67c3d03c1e5f

Introduce linux_proc_pid_to_exec_file
This commit introduces a new function linux_proc_pid_to_exec_file
that shared Linux code can use to discover the filename of the
executable that was run to create a process on the system.

gdb/ChangeLog:

	* nat/linux-procfs.h (linux_proc_pid_to_exec_file):
	New declaration.
	* nat/linux-procfs.c (linux_proc_pid_to_exec_file):
	New function, factored out from...
	* linux-nat.c (linux_child_pid_to_exec_file): ...here.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Introduce exec_file_locate_attach
@ 2015-04-17 10:45 sergiodj+buildbot
  2015-04-17 12:10 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-17 10:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a10de6046fbd50e99742af428a815dcd94e2fba8 ***

Author: Gary Benson <gbenson@redhat.com>
Branch: master
Commit: a10de6046fbd50e99742af428a815dcd94e2fba8

Introduce exec_file_locate_attach
This commit adds a new function, exec_file_locate_attach, which works
like exec_file_attach except that, instead of a filename argument, it
takes an integer process ID and attempts to determine the executable
filename from that.

gdb/ChangeLog:

	* gdbcore.h (exec_file_locate_attach): New declaration.
	* exec.c (exec_file_locate_attach): New function, factored
	out from...
	* infcmd.c (attach_command_post_wait): ...here.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] sim: replace CIA_{GET,SET} with CPU_PC_{GET,SET}
@ 2015-04-17  7:40 sergiodj+buildbot
  2015-04-17  8:55 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-17  7:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 034685f9ce92cf6dfb6656745365b6a5904a8e84 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 034685f9ce92cf6dfb6656745365b6a5904a8e84

sim: replace CIA_{GET,SET} with CPU_PC_{GET,SET}
The CIA_{GET,SET} macros serve the same function as CPU_PC_{GET,SET}
except the latter adds a layer of indirection via the sim state.  This
lets models set up different functions at runtime and doesn't reach so
directly into the arch-specific cpu state.

It also doesn't make sense to have two sets of macros that do exactly
the same thing, so lets standardize on the one that gets us more.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] sim: arm/cr16/d10v/h8300/microblaze/sh: fill out sim-cpu pc fetch/store helpers
@ 2015-04-17  6:45 sergiodj+buildbot
  2015-04-17  7:57 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-17  6:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 27b97b40bca216097d16d53fa9408a70cd281479 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 27b97b40bca216097d16d53fa9408a70cd281479

sim: arm/cr16/d10v/h8300/microblaze/sh: fill out sim-cpu pc fetch/store helpers
This makes the common sim-cpu logic work.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Fix gdbserver_reconnect_p handling
@ 2015-04-16 13:58 sergiodj+buildbot
  2015-04-16 15:33 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-16 13:58 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1ca99c4299f4deed8765fbb1eb4f9aea40d919b6 ***

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

Fix gdbserver_reconnect_p handling
Commit 6423214f (testsuite: Don't use expect_background to reap
gdbserver) broke a couple tests that set gdbserver_reconnect_p and
restart gdb before reconnecting, because a gdb_exit (e.g., through
clean_restart) exits gdbserver unconditionally.

Fixes, with --target_board=native-gdbserver:

 -FAIL: gdb.trace/mi-tracepoint-changed.exp: reconnect: break-info 1
 +PASS: gdb.trace/mi-tracepoint-changed.exp: reconnect: tracepoint created
 +PASS: gdb.trace/mi-tracepoint-changed.exp: reconnect: tracepoint on marker is installed
 +PASS: gdb.trace/mi-tracepoint-changed.exp: reconnect: break-info 1

 -FAIL: gdb.trace/mi-tsv-changed.exp: upload: tsv1 created
 -FAIL: gdb.trace/mi-tsv-changed.exp: upload: tsv2 created
 +PASS: gdb.trace/mi-tsv-changed.exp: upload: tsv1 created
 +PASS: gdb.trace/mi-tsv-changed.exp: upload: tsv2 created

gdb/testsuite/
2015-04-16  Pedro Alves  <palves@redhat.com>

	* lib/gdbserver-support.exp (gdb_exit): If gdbserver_reconnect_p
	is set, don't exit gdbserver.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] s390-vregs.exp: Avoid compile errors with older GCCs and on 31-bit targets
@ 2015-04-16 12:02 sergiodj+buildbot
  2015-04-16 13:36 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-16 12:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT af9fd6f863c9f184e2c84d8a4707b3ec7b8ca67b ***

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

s390-vregs.exp: Avoid compile errors with older GCCs and on 31-bit targets
The test case s390-vregs.exp yields compile errors on 31-bit targets
as well as when using a GCC that defaults to an older "-march=".  This
patch fixes these issues.

gdb/testsuite/ChangeLog:

	* gdb.arch/s390-vregs.S (change_vrs): Replace exrl by an
	appropriate .insn, such that an older assembler can be used.
	* gdb.arch/s390-vregs.exp: Add the compile flag -mzarch, to enable
	the z/Architecture instruction set on 31-bit targets as well.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] sim: avr/mcore/moxie: fill out sim-cpu pc fetch/store helpers
@ 2015-04-16  6:38 sergiodj+buildbot
  2015-04-16  9:13 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-16  6:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4c0cab1e212bd0f25879b00393bbb60e114ac724 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 4c0cab1e212bd0f25879b00393bbb60e114ac724

sim: avr/mcore/moxie: fill out sim-cpu pc fetch/store helpers
This makes the common sim-cpu logic work.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Make info fun|var|types interruptable for psyms.
@ 2015-04-15 22:09 sergiodj+buildbot
  2015-04-16  7:17 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-15 22:09 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 30b3dd9d4701834573e6a6c071941c25d825cab8 ***

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

Make info fun|var|types interruptable for psyms.
gdb/ChangeLog:

	* psymtab.c (psym_expand_symtabs_matching): Add QUIT call.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Make info fun|var|types interruptable.
@ 2015-04-15 20:39 sergiodj+buildbot
  2015-04-16  6:16 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-15 20:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 61d96d7e2e0a44336fc53eb79ccb59b41705cdb3 ***

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

Make info fun|var|types interruptable.
"info fun foo" can be a pain when it's not interruptable,
especially if you're not exactly sure of what you're looking for
and provide something that matches too much.

gdb/ChangeLog:

	* dwarf2read.c (dw2_expand_symtabs_matching): Add some QUIT calls.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Check dp->prefix_requirement instead
@ 2015-04-15 20:26 sergiodj+buildbot
  2015-04-16  5:12 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-15 20:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3888916da84288994be10d6ae1a2db5b45b3f8f8 ***

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

Check dp->prefix_requirement instead
This patch removes prefix_requirement and checks dp->prefix_requirement
instead.

	* i386-dis.c (prefix_requirement): Removed.
	(print_insn): Don't set prefix_requirement.  Check
	dp->prefix_requirement instead of prefix_requirement.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Handle invalid prefixes for rdrand and rdseed
@ 2015-04-15 18:36 sergiodj+buildbot
  2015-04-16  3:25 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-15 18:36 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f24bcbaa5a6e30556e2da20bfd78e7823741475a ***

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

Handle invalid prefixes for rdrand and rdseed
This patch puts rdrand and rdseed in prefix_table so that invalid
prefixes for rdrand and rdseed are handled properly.

gas/testsuite/

	PR binutils/17898
	* gas/i386/prefix.s: Add rdrand/rdseed prefix tests.
	* gas/i386/prefix.d: Updated.

opcodes/

	PR binutils/17898
	* i386-dis.c (PREFIX_0FC7_REG_6): Renamed to ...
	(PREFIX_MOD_0_0FC7_REG_6): This.
	(PREFIX_MOD_3_0FC7_REG_6): New.
	(PREFIX_MOD_3_0FC7_REG_7): Likewise.
	(prefix_table): Replace PREFIX_0FC7_REG_6 with
	PREFIX_MOD_0_0FC7_REG_6.  Add PREFIX_MOD_3_0FC7_REG_6 and
	PREFIX_MOD_3_0FC7_REG_7.
	(mod_table): Replace PREFIX_0FC7_REG_6 with
	PREFIX_MOD_0_0FC7_REG_6.  Use PREFIX_MOD_3_0FC7_REG_6 and
	PREFIX_MOD_3_0FC7_REG_7.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Some Python 3 fixes
@ 2015-04-15 16:28 sergiodj+buildbot
  2015-04-15 20:01 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-15 16:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 40d2f8d62e5474d984fb41e0229763ab93213fdb ***

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

Some Python 3 fixes
Some missing parentheses and one itertools.imap (Py2) vs map (Py3) issue.

gdb/ChangeLog:

	* python/lib/gdb/command/unwinders.py: Add parentheses.

gdb/testsuite/ChangeLog:

	* gdb.python/py-framefilter.py (ErrorFilter.filter): Use map function
	if itertools.imap is not present.
	* gdb.python/py-objfile.exp: Add parentheses.
	* gdb.python/py-type.exp: Same.
	* gdb.python/py-unwind-maint.py: Same.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Fix code indentation
@ 2015-04-15 15:08 sergiodj+buildbot
  2015-04-15 18:03 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-15 15:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2bb2dcab455295cc23dec46f0150b15892ab4933 ***

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

Fix code indentation
gdb:

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

	* arm-linux-tdep.c (arm_linux_copy_svc): Fix indentation.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [arm] Fix fails in gdb.base/disp-step-syscall.exp
@ 2015-04-15 14:45 sergiodj+buildbot
  2015-04-15 17:04 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-15 14:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 41f071ef337ac55b7bd5366ef003fe47b809cdee ***

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

[arm] Fix fails in gdb.base/disp-step-syscall.exp
Hi,
I see this fail on arm-linux target,

 FAIL: gdb.base/disp-step-syscall.exp: fork: single step over fork final pc

which is caused by the PC isn't expected after displaced stepping the
svc instruction.  The code is:

=> 0xb6ead9a4 <__libc_do_syscall+4>:    svc     0
   0xb6ead9a6 <__libc_do_syscall+6>:    pop     {r7, pc}
   0xb6ead9a8:  nop.w^M
   0xb6ead9ac:  nop.w

after single step svc instruction, pc should be 0xb6ead9a6, but the
actual value of pc is 0xb6ead9a8.  The problem is illustrated by
turning on debug message of displaced stepping,

stepi^M
displaced: stepping Thread 12031 now^M
displaced: saved 0x8574: 02 bc 6a 46 04 b4 01 b4 df f8 10 c0 4d f8 04 cd 03 48 04 4b ff f7 d2 ef ff f7 e8 ef 0d 87 00 00 ^M
displaced: process thumb insn df00 at b6ead9a4^M
displaced: copying svc insn df00^M
displaced: read r7 value 00000078^M
displaced: sigreturn/rt_sigreturn SVC call not in signal trampoline frame^M
displaced: writing insn df00 at 00008574^M
displaced: copy 0xb6ead9a4->0x8574: displaced: check mode of b6ead9a4 instead of 00008574^M
displaced: displaced pc to 0x8574^M
displaced: run 0x8574: 00 df 01 de ^M
displaced: restored Thread 12031 0x8574^M
displaced: PC is apparently 00008576 after SVC step (within scratch space)^M
displaced: writing pc b6ead9a8  <----- WRONG ADDRESS

GDB writes the wrong address back to pc because GDB thinks the
instruction size is 4, which isn't true for thumb instruction.
This patch is to replace 4 with dsc->insn_size.

gdb:

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

	* arm-linux-tdep.c (arm_linux_cleanup_svc): Use
	dsc->insn_size instead of 4.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Fix typo in commit 6ff71e76
@ 2015-04-15  2:15 sergiodj+buildbot
  2015-04-15  8:32 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-15  2:15 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 95b57adeb751b56a1192867f9f1e1be2fad608dd ***

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

Fix typo in commit 6ff71e76
	* elf32-rl78.c (rl78_elf_relocate_section): Typo fix.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Adds support to the RL78 port for linker relaxation affecting .debug sections.
@ 2015-04-14 15:29 sergiodj+buildbot
  2015-04-14 15:34 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-14 15:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6ff71e768112317de1236a429e7c88c9d3e32116 ***

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

Adds support to the RL78 port for linker relaxation affecting .debug sections.
gas	* config/tc-rl78.h (TC_LINKRELAX_FIXUP): Define.
	(TC_FORCE_RELOCATION_SUB_SAME): Define.
	(DWARF2_USE_FIXED_ADVANCE_PC): Define.

	* gas/lns/lns.exp: Add RL78 to list of targets using
	DW_LNS_fixed_advance_pc.

bfd	* elf32-rl78.c (RL78_OP_REL): New macro.
	(rl78_elf_howto_table): Use it for complex relocs.
	(get_symbol_value): Handle the cases when the info or status
	arguments are NULL.
	(get_romstart): Cache the status returned by get_symbol_value.
	(get_ramstart): Likewise.
	(RL78_STACK_PUSH): Generate an error message if the stack
	overflows.
	(RL78_STACK_POP): Likewise for underflows.
	(rl78_compute_complex_reloc): New function.  Contains the basic
	processing code for all RL78 complex relocs.
	(rl78_special_reloc): New function.  Provides special reloc
	handling for complex relocs.
	(rl78_elf_relocate_section): Use rl78_compute_complex_reloc.
	(rl78_offset_for_reloc): Likewise.

binutils* readelf.c (target_specific_reloc_handling): Add code to handle
	RL78 complex relocs.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Harden gdb.base/bp-permanent.exp
@ 2015-04-14 12:31 sergiodj+buildbot
  2015-04-14 14:51 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-14 12:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9e811bc379ef78f0e2beadda9ed3ce6679ded7ea ***

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

Harden gdb.base/bp-permanent.exp
Reinstate test message and replace hardcoded test command with a variable.

gdb/testsuite/ChangeLog:
2015-04-14  Luis Machado  <lgustavo@codesourcery.com>

	* gdb.base/bp-permanent.exp (test): Reinstate correct test message.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Add -z noextern-protected-data to ld for ELF/x86
@ 2015-04-14 11:19 sergiodj+buildbot
  2015-04-14 12:32 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-14 11:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 889c2a67967f7047c245779a0a0fd8ba8796846e ***

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

Add -z noextern-protected-data to ld for ELF/x86
Address of protected data defined in the shared library may be external,
i.e., due to copy relocation.  By default, linker backend checks if
relocations against protected data symbols are valid for building shared
library and issues an error if relocation isn't allowed.  The new option
override linker backend default.  When -z noextern-protected-data is used,
updates on protected data symbols by another module won't be visibile
to the resulting shared library.  This option is specific to ELF/i386
and ELF/x86-64.

bfd/

	PR ld/pr17709
	* elflink.c (_bfd_elf_adjust_dynamic_copy): Check
	info->extern_protected_data when warning copy relocs against
	protected symbols.
	(_bfd_elf_symbol_refs_local_p): Check info->extern_protected_data
	when checking protected non-function symbols.

include/

	PR ld/pr17709
	* bfdlink.h (bfd_link_info): Add extern_protected_data.

ld/

	PR ld/pr17709
	* ld.texinfo: Document "-z noextern-protected-data".
	* ldmain.c (main): Initialize link_info.extern_protected_data
	to -1.
	* lexsup.c (elf_shlib_list_options): Add
	"-z [no]extern-protected-data".
	* emulparams/elf32_x86_64.sh: Source extern_protected_data.sh.
	* emulparams/elf_i386.sh: Likewise.
	* emulparams/elf_i386_be.sh: Likewise.
	* emulparams/elf_i386_chaos.sh: Likewise.
	* emulparams/elf_i386_ldso.sh: Likewise.
	* emulparams/elf_i386_vxworks.sh: Likewise.
	* emulparams/elf_k1om.sh: Likewise.
	* emulparams/elf_l1om.sh: Likewise.
	* emulparams/elf_x86_64.sh: Source extern_protected_data.sh.
	(PARSE_AND_LIST_OPTIONS): Renamed to ...
	(PARSE_AND_LIST_OPTIONS_BNDPLT): This.
	(PARSE_AND_LIST_ARGS_CASE_Z): Renamed to ...
	(PARSE_AND_LIST_ARGS_CASE_Z_BNDPLT): This.
	(PARSE_AND_LIST_OPTIONS): Append $PARSE_AND_LIST_OPTIONS_BNDPLT.
	(PARSE_AND_LIST_ARGS_CASE_Z): Append
	$PARSE_AND_LIST_ARGS_CASE_Z_BNDPLT.
	* emulparams/extern_protected_data.sh: New file.

ld/testsuite/

	PR ld/pr17709
	* ld-i386/i386.exp: Run protected6b.
	* ld-i386/protected6b.d: New file.
	* ld-x86-64/protected6b.d: Likewise.
	* ld-x86-64/x86-64.exp:  Run protected6b.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] sim: ppc: fix up version script
@ 2015-04-14  3:25 sergiodj+buildbot
  2015-04-14  4:44 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-14  3:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 887bddbcad907021f4cb98168cd51f2631e6cfc8 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 887bddbcad907021f4cb98168cd51f2631e6cfc8

sim: ppc: fix up version script
The common sim code has switched to using gdb directly; update the
ppc copy too.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Add support for the x86 XSAVE extended state on FreeBSD/x86.
@ 2015-04-13 21:19 sergiodj+buildbot
  2015-04-13 22:33 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-13 21:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 97de3545ca6b690031cc00983346ed72f11e78a2 ***

Author: John Baldwin <jhb@FreeBSD.org>
Branch: master
Commit: 97de3545ca6b690031cc00983346ed72f11e78a2

Add support for the x86 XSAVE extended state on FreeBSD/x86.
Recognize NT_X86_XSTATE notes in FreeBSD process cores.  Recent
FreeBSD versions include a note containing the XSAVE state for each
thread in the process when XSAVE is in use.  The note stores a copy of
the current XSAVE mask in a reserved section of the machine-defined
XSAVE state at the same offset as Linux's NT_X86_XSTATE note.

For native processes, use the PT_GETXSTATE_INFO ptrace request to
determine if XSAVE is enabled, and if so the active XSAVE state mask
(that is, the value of %xcr0 for the target process) as well as the
size of XSAVE state area.  Use the PT_GETXSTATE and PT_SETXSTATE requests
to fetch and store the XSAVE state, respectively, in the BSD x86
native targets.

In addition, the FreeBSD amd64 and i386 native targets now include
"read_description" target methods to determine the correct x86 target
description for the current XSAVE mask.  On FreeBSD amd64 this also
properly returns an i386 target description for 32-bit binaries which
allows the 64-bit GDB to run 32-bit binaries.

Note that the ptrace changes are in the BSD native targets, not the
FreeBSD-specific native targets since that is where the other ptrace
register accesses occur.  Of the other BSDs, NetBSD and DragonFly use
XSAVE in the kernel but do not currently export the extended state via
ptrace(2).  OpenBSD does not currently support XSAVE.

bfd/ChangeLog:

	* elf.c (elfcore_grok_note): Recognize NT_X86_XSTATE on
	FreeBSD.
	(elfcore_write_xstatereg): Use correct note name on FreeBSD.

gdb/ChangeLog:

	* amd64-tdep.c (amd64_target_description): New function.
	* amd64-tdep.h: Export amd64_target_description and tdesc_amd64.
	* amd64bsd-nat.c [PT_GETXSTATE_INFO]: New variable amd64bsd_xsave_len.
	(amd64bsd_fetch_inferior_registers) [PT_GETXSTATE_INFO]: Handle
	x86 extended save area.
	(amd64bsd_store_inferior_registers) [PT_GETXSTATE_INFO]: Likewise.
	* amd64bsd-nat.h: Export amd64bsd_xsave_len.
	* amd64fbsd-nat.c (amd64fbsd_read_description): New function.
	(_initialize_amd64fbsd_nat): Set "to_read_description" to
	"amd64fbsd_read_description".
	* amd64fbsd-tdep.c (amd64fbsd_core_read_description): New function.
	(amd64fbsd_supply_xstateregset): New function.
	(amd64fbsd_collect_xstateregset): New function.
	Add "amd64fbsd_xstateregset".
	(amd64fbsd_iterate_over_regset_sections): New function.
	(amd64fbsd_init_abi): Set "xsave_xcr0_offset" to
	"I386_FBSD_XSAVE_XCR0_OFFSET".
	Add "iterate_over_regset_sections" gdbarch method.
	Add "core_read_description" gdbarch method.
	* i386-tdep.c (i386_target_description): New function.
	* i386-tdep.h: Export i386_target_description and tdesc_i386.
	* i386bsd-nat.c [PT_GETXSTATE_INFO]: New variable i386bsd_xsave_len.
	(i386bsd_fetch_inferior_registers) [PT_GETXSTATE_INFO]: Handle
	x86 extended save area.
	(i386bsd_store_inferior_registers) [PT_GETXSTATE_INFO]: Likewise.
	* i386bsd-nat.h: Export i386bsd_xsave_len.
	* i386fbsd-nat.c (i386fbsd_read_description): New function.
	(_initialize_i386fbsd_nat): Set "to_read_description" to
	"i386fbsd_read_description".
	* i386fbsd-tdep.c (i386fbsd_core_read_xcr0): New function.
	(i386fbsd_core_read_description): New function.
	(i386fbsd_supply_xstateregset): New function.
	(i386fbsd_collect_xstateregset): New function.
	Add "i386fbsd_xstateregset".
	(i386fbsd_iterate_over_regset_sections): New function.
	(i386fbsd4_init_abi): Set "xsave_xcr0_offset" to
	"I386_FBSD_XSAVE_XCR0_OFFSET".
	Add "iterate_over_regset_sections" gdbarch method.
	Add "core_read_description" gdbarch method.
	* i386fbsd-tdep.h: New file.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Harden gdb.base/coredump-filter.exp
@ 2015-04-13 17:49 sergiodj+buildbot
  2015-04-13 20:33 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-13 17:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7578d5f72c4abb6b49b0394bc810192b06088705 ***

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

Harden gdb.base/coredump-filter.exp
This testcase seems to assume the target is running Linux, so bare metal,
simulators and other debugging stubs running different OS' will have a
hard time executing some of the commands the testcase issues.

Even restricting the testcase to Linux systems (which the patch below does),
there are still problems with, say, QEMU not providing PID information when
"info inferior" is issued. As a consequence, the subsequent tests will either
fail or will not make much sense.

The attached patch checks if PID information is available. If not, it just
bails out and avoids running into a number of failures.

gdb/testsuite/ChangeLog:
2015-04-13  Luis Machado  <lgustavo@codesourcery.com>

	* gdb.base/coredump-filter.exp: Restrict test to Linux systems only.
	Handle the case of targets that do not provide PID information.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Catch exception in lib/gdbserver-support.exp:gdb_exit
@ 2015-04-13 14:52 sergiodj+buildbot
  2015-04-13 19:35 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-13 14:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2efe15c42872987ed5123f3a3952c8b379554840 ***

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

Catch exception in lib/gdbserver-support.exp:gdb_exit
I see the error when I run gdb-sigterm.exp with native-gdbserver
on x86_64-linux.

infrun: prepare_to_wait^M
Cannot execute this command while the target is running.^M
Use the "interrupt" command to stop the target^M
and then try again.^M
gdb.base/gdb-sigterm.exp: expect eof #0: got eof
gdb.base/gdb-sigterm.exp: expect eof #0: stepped 12 times
ERROR OCCURED: : spawn id exp8 not open
    while executing
"expect {
-i exp8 -timeout 10
            -re "$gdb_prompt $" {
                exp_continue
            }
            -i "$server_spawn_id" eof {
                wait -i $expect_out(spawn_id)
                unse..."
    ("uplevel" body line 1)
    invoked from within

In gdb-sigterm.exp, SIGTERM is sent to GDB and it exits.  However,
Dejagnu or tcl doesn't know this.

This patch is to catch the exception, but error messages are still
shown in the console and gdb.log.  In order to avoid this, we also
replace gdb_expect with expect.

gdb/testsuite:

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

	* lib/gdbserver-support.exp (gdb_exit): Catch exception
	and use expect instead of gdb_expect.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] sim: fix the PKGVERSION define
@ 2015-04-13 14:50 sergiodj+buildbot
  2015-04-13 16:14 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-13 14:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bf12d44ee075e694a2b0dca87b9e9ca0e685d319 ***

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

sim: fix the PKGVERSION define
This should be SIM, not GDB.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] sim: options: add --version support
@ 2015-04-13  9:36 sergiodj+buildbot
  2015-04-13 15:15 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-13  9:36 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a542beff945c1a416f85309d57b21d4a18422883 ***

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

sim: options: add --version support
The old run frontend had a --version option, but the new common
sim-options file does not.  Restore support for that so we can
get version info out of `run` when using the new frontend.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] sim: m68hc11: convert to sim-cpu
@ 2015-04-13  8:27 sergiodj+buildbot
  2015-04-13  9:23 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-13  8:27 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bea3f671c5734eb96a02055fbaa0c938ad535b66 ***

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

sim: m68hc11: convert to sim-cpu
Make cpu allocation fully dynamic so we can leverage the common
sim-cpu and its APIs.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] sim: v850: convert to sim-cpu
@ 2015-04-13  7:29 sergiodj+buildbot
  2015-04-13 11:50 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-13  7:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 14c9ad2edb6e0bb0b560fa45699b83d85aa28b94 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 14c9ad2edb6e0bb0b560fa45699b83d85aa28b94

sim: v850: convert to sim-cpu
Make cpu allocation fully dynamic so we can leverage the common
sim-cpu and its APIs.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] sim: mips: fix prototype warnings
@ 2015-04-13  7:25 sergiodj+buildbot
  2015-04-13  8:03 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-13  7:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8ac57fbde478b8e8fb0ba169f620d713be319260 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 8ac57fbde478b8e8fb0ba169f620d713be319260

sim: mips: fix prototype warnings
Convert a bunch of old style prototypes and tweak various casts
to match the function signatures.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Do unset_currtarget_info ldscript for all simulator testsuites.
@ 2015-04-13  0:18 sergiodj+buildbot
  2015-04-13  2:19 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-13  0:18 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a9d9677441e54816aa76ffd1736419ec096b4ef1 ***

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

Do unset_currtarget_info ldscript for all simulator testsuites.
sim/testsuite:
	* sim-defs.exp (sim_init): Unset target ldscript here.

sim/testsuite/sim/mips:
	* basic.exp: Don't unset target ldscript here.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] sim: arm/mips: fix sim_read/sim_write linkage errors
@ 2015-04-12 10:22 sergiodj+buildbot
  2015-04-12 11:51 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-12 10:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e787f858a43c9a6b54a74cec24f954b52619433e ***

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

sim: arm/mips: fix sim_read/sim_write linkage errors
With sim-hrw.o being built & linked in the common list, some people are
getting linking errors now for these targets.  Move the main objects that
provide these functions before the common list to avoid that.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] sim: ft32: delete sim_read/sim_write funcs
@ 2015-04-12  9:35 sergiodj+buildbot
  2015-04-12 10:16 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-12  9:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 29f1a5934a1b4b3b22aaeee2c4c471fbd95f0ba2 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 29f1a5934a1b4b3b22aaeee2c4c471fbd95f0ba2

sim: ft32: delete sim_read/sim_write funcs
The common sim-hrw.o provides both of these, so simply use them.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Don't call getpagesize more than once
@ 2015-04-12  0:12 sergiodj+buildbot
  2015-04-12  3:39 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-12  0:12 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 263b1a3c1f9be7a3bafdb26d69f808974f886680 ***

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

Don't call getpagesize more than once


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Initialize pagesize_m1 in bfd_cache_init
@ 2015-04-11 22:33 sergiodj+buildbot
  2015-04-11 23:18 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-11 22:33 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2c008f9a5b65fe8d9379e761b056fabeb34a5da6 ***

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

Initialize pagesize_m1 in bfd_cache_init
There is no need to check and initialize pagesize_m1 in cache_bmmap.

	* cache.c (cache_bmmap): Move pagesize_m1 ... to
	(pagesize_m1): Here.
	(bfd_cache_init): Initialize pagesize_m1.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Cleanup signal-while-stepping-over-bp-other-thread.exp
@ 2015-04-10 23:26 sergiodj+buildbot
  2015-04-11  4:04 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-10 23:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9ee417720b2f25c56a9738569b63f686cbc8584f ***

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

Cleanup signal-while-stepping-over-bp-other-thread.exp
gdb/testsuite/ChangeLog:
2015-04-10  Pedro Alves  <palves@redhat.com>

	* gdb.threads/signal-while-stepping-over-bp-other-thread.exp: Use
	gdb_test_sequence and gdb_assert.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] step-over-trips-on-watchpoint.exp: Don't put addresses in test messages
@ 2015-04-10 21:19 sergiodj+buildbot
  2015-04-11  2:54 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-10 21:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 07473109e11e41d979c33b839551ac1c6f8495b9 ***

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

step-over-trips-on-watchpoint.exp: Don't put addresses in test messages
Diffing test results, I noticed:

 -PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: with thread-specific bp: next: b *0x0000000000400811 thread 1
 +PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: with thread-specific bp: next: b *0x00000000004007d1 thread 1

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

	* gdb.threads/step-over-trips-on-watchpoint.exp (do_test): Use
	test messages that don't include the breakpoint address.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Add extern_protected_data and set it for x86
@ 2015-04-10 18:49 sergiodj+buildbot
  2015-04-10 23:18 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-10 18:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f74839702efcea048ac61374b1539ae81e7c86cc ***

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

Add extern_protected_data and set it for x86
Re-apply: commit ca3fe95e469b9daec153caa2c90665f5daaec2b5

With copy relocation, address of protected data defined in the shared
library may be external.  This patch adds extern_protected_data and
changes _bfd_elf_symbol_refs_local_p to return false for protected data
if extern_protected_data is true.

This patch will break building shared libraries with protected data
symbols using GCCs older than GCC 5 without the bug fix for

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65248

GCC backport request should be made in the GCC bug report above.

To get correct run-time behavior on Linux, glibc 2.22 or above are
required, which have the bug fix for

https://sourceware.org/bugzilla/show_bug.cgi?id=17711

Backports for glibc 2.21, 2.20, 2.19 and 2.18 are on hjl/pr17711/2.21,
hjl/pr17711/2.20, hjl/pr17711/2.19 and hjl/pr17711/2.18 branches,
respectively, at

https://sourceware.org/git/?p=glibc.git;a=summary

bfd/

	PR ld/pr15228
	PR ld/pr17709
	* elf-bfd.h (elf_backend_data): Add extern_protected_data.
	* elf32-i386.c (elf_backend_extern_protected_data): New.
	Defined to 1.
	* elf64-x86-64.c (elf_backend_extern_protected_data): Likewise.
	* elflink.c (_bfd_elf_adjust_dynamic_copy): Don't error on
	copy relocs against protected symbols if extern_protected_data
	is true.
	(_bfd_elf_symbol_refs_local_p): Don't return true on protected
	non-function symbols if extern_protected_data is true.
	* elfxx-target.h (elf_backend_extern_protected_data): New.
	Default to 0.
	(elfNN_bed): Initialize extern_protected_data with
	elf_backend_extern_protected_data.

ld/testsuite/

	PR ld/pr15228
	PR ld/pr17709
	* ld-i386/i386.exp (i386tests): Add a test for PR ld/17709.
	* ld-i386/pr17709-nacl.rd: New file.
	* ld-i386/pr17709.rd: Likewise.
	* ld-i386/pr17709a.s: Likewise.
	* ld-i386/pr17709b.s: Likewise.
	* ld-i386/protected3.d: Updated.
	* ld-i386/protected3.s: Likewise.
	* ld-x86-64/pr17709-nacl.rd: New file.
	* ld-x86-64/pr17709.rd: Likewise.
	* ld-x86-64/pr17709a.s: Likewise.
	* ld-x86-64/pr17709b.s: Likewise.
	* ld-x86-64/protected3.d: Updated.
	* ld-x86-64/protected3.s: Likewise.
	* ld-x86-64/x86-64.exp (x86_64tests): Add a test for PR ld/17709.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] PPC64: Fix step-over-trips-on-watchpoint.exp with displaced stepping on
@ 2015-04-10 16:17 sergiodj+buildbot
  2015-04-10 21:16 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-10 16:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cb71640d030500888726d54a310c434a4d23b7b3 ***

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

PPC64: Fix step-over-trips-on-watchpoint.exp with displaced stepping on
PPC64 currently fails this test like:

 FAIL: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: no thread-specific bp: step: step
 FAIL: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: no thread-specific bp: next: next
 FAIL: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: no thread-specific bp: continue: continue (the program exited)
 FAIL: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: with thread-specific bp: step: step
 FAIL: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: with thread-specific bp: next: next
 FAIL: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: with thread-specific bp: continue: continue (the program exited)

The problem is that PPC is a non-continuable watchpoints architecture
and the displaced stepping code isn't coping with that correctly.  On
such targets/architectures, a watchpoint traps _before_ the
instruction executes/completes.  On a watchpoint trap, the PC points
at the instruction that triggers the watchpoint (side effects haven't
happened yet).  In order to move past the watchpoint, GDB needs to
remove the watchpoint, single-step, and reinsert the watchpoint, just
like when stepping past a breakpoint.

The trouble is that if GDB is stepping over a breakpoint with
displaced stepping, and the instruction under the breakpoint triggers
a watchpoint, we get the watchpoint SIGTRAP, expecting a finished
(hard or software) step trap.  Even though the thread's PC hasn't
advanced yet (must remove watchpoint for that), since we get a
SIGTRAP, displaced_step_fixup thinks the single-step finished
successfuly anyway, and calls gdbarch_displaced_step_fixup, which then
adjusts the thread's registers incorrectly.

The fix is to cancel the displaced step if we trip on a watchpoint.
handle_inferior_event then processes the watchpoint event, and starts
a new step-over, here:

...
      /* At this point, we are stopped at an instruction which has
         attempted to write to a piece of memory under control of
         a watchpoint.  The instruction hasn't actually executed
         yet.  If we were to evaluate the watchpoint expression
         now, we would get the old value, and therefore no change
         would seem to have occurred.
...
      ecs->event_thread->stepping_over_watchpoint = 1;
      keep_going (ecs);
      return;
...

but this time, since we have a watchpoint to step over, watchpoints
are removed from the target, so the step-over succeeds.

The keep_going/resume changes are necessary because if we're stepping
over a watchpoint, we need to remove it from the target - displaced
stepping doesn't help, the copy of the instruction in the scratch pad
reads/writes to the same addresses, thus triggers the watchpoint
too...  So without those changes we keep triggering the watchpoint
forever, never making progress.  With non-stop that means we'll need
to pause all threads momentarily, which we can't today.  We could
avoid that by removing the watchpoint _only_ from the thread that is
moving past the watchpoint, but GDB is not prepared for that today
either.  For remote targets, that would need new packets, so good to
be able to step over it in-line as fallback anyway.

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

	* infrun.c (displaced_step_fixup): Switch to the event ptid
	earlier.  If the thread stopped for a watchpoint and the
	target/arch has non-continuable watchpoints, cancel the displaced
	step.
	(resume): Don't start a displaced step if in-line step-over info
	is valid.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Make gdb.threads/step-over-trips-on-watchpoint.exp effective on !x86
@ 2015-04-10 13:34 sergiodj+buildbot
  2015-04-10 19:17 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-10 13:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ebc90b50ce6377bf822c918eaf7c55bcd451ba45 ***

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

Make gdb.threads/step-over-trips-on-watchpoint.exp effective on !x86
This test is currently failing like this on (at least) PPC64 and s390x:

 FAIL: gdb.threads/step-over-trips-on-watchpoint.exp: no thread-specific bp: step: step
 FAIL: gdb.threads/step-over-trips-on-watchpoint.exp: no thread-specific bp: next: next
 FAIL: gdb.threads/step-over-trips-on-watchpoint.exp: with thread-specific bp: step: step
 FAIL: gdb.threads/step-over-trips-on-watchpoint.exp: with thread-specific bp: next: next

gdb.log:

 (gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: no thread-specific bp: step: set scheduler-locking off
 step
 wait_threads () at ../../../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

The problem is that the test assumes that both the "watch_me = 1;" and
the "other = 1;" lines compile to a single instruction each, which
happens to be true on x86, but no necessarily true everywhere else.
The result is that the test doesn't really test what it wants to test.

Fix it by looking for the instruction that triggers the watchpoint.

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

	* gdb.threads/step-over-trips-on-watchpoint.c (child_function):
	Remove comment.
	* gdb.threads/step-over-trips-on-watchpoint.exp (do_test): Find
	both the address of the instruction that triggers the watchpoint
	and the address of the instruction immediately after, and use
	those addresses for the test.  Fix comment.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Fix gdb.base/sigstep.exp with displaced stepping on software single-step targets
@ 2015-04-10 12:25 sergiodj+buildbot
  2015-04-10 15:55 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-10 12:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8f572e5c0f71fd6641768985855b2e0955a78f51 ***

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

Fix gdb.base/sigstep.exp with displaced stepping on software single-step targets
TL;DR:

When stepping over a breakpoint with displaced stepping, the core must
be notified of all signals, otherwise the displaced step fixup code
confuses a breakpoint trap in the signal handler for the expected trap
indicating the displaced instruction was single-stepped
normally/successfully.

Detailed version:

Running sigstep.exp with displaced stepping on, against my x86
software single-step branch, I got:

 FAIL: gdb.base/sigstep.exp: step on breakpoint, to handler: performing step
 FAIL: gdb.base/sigstep.exp: next on breakpoint, to handler: performing next
 FAIL: gdb.base/sigstep.exp: continue on breakpoint, to handler: performing continue

Turning on debug logs, we see:

 (gdb) step
 infrun: clear_proceed_status_thread (process 32147)
 infrun: proceed (addr=0xffffffffffffffff, signal=GDB_SIGNAL_DEFAULT)
 infrun: resume (step=1, signal=GDB_SIGNAL_0), trap_expected=1, current thread [process 32147] at 0x400842
 displaced: stepping process 32147 now
 displaced: saved 0x400622: 49 89 d1 5e 48 89 e2 48 83 e4 f0 50 54 49 c7 c0
 displaced: %rip-relative addressing used.
 displaced: using temp reg 2, old value 0x3615eafd37, new value 0x40084c
 displaced: copy 0x400842->0x400622: c7 81 1c 08 20 00 00 00 00 00
 displaced: displaced pc to 0x400622
 displaced: run 0x400622: c7 81 1c 08
 LLR: Preparing to resume process 32147, 0, inferior_ptid process 32147
 LLR: PTRACE_CONT process 32147, 0 (resume event thread)
 linux_nat_wait: [process -1], [TARGET_WNOHANG]
 LLW: enter
 LNW: waitpid(-1, ...) returned 32147, No child processes
 LLW: waitpid 32147 received Alarm clock (stopped)
 LLW: PTRACE_CONT process 32147, Alarm clock (preempt 'handle')
 LNW: waitpid(-1, ...) returned 0, No child processes
 LLW: exit (ignore)
 sigchld
 infrun: target_wait (-1.0.0, status) =
 infrun:   -1.0.0 [process -1],
 infrun:   status->kind = ignore
 infrun: TARGET_WAITKIND_IGNORE
 infrun: prepare_to_wait
 linux_nat_wait: [process -1], [TARGET_WNOHANG]
 LLW: enter
 LNW: waitpid(-1, ...) returned 32147, No child processes
 LLW: waitpid 32147 received Trace/breakpoint trap (stopped)
 CSBB: process 32147 stopped by software breakpoint
 LNW: waitpid(-1, ...) returned 0, No child processes
 LLW: trap ptid is process 32147.
 LLW: exit
 infrun: target_wait (-1.0.0, status) =
 infrun:   32147.32147.0 [process 32147],
 infrun:   status->kind = stopped, signal = GDB_SIGNAL_TRAP
 infrun: TARGET_WAITKIND_STOPPED
 displaced: restored process 32147 0x400622
 displaced: fixup (0x400842, 0x400622), insn = 0xc7 0x81 ...
 displaced: restoring reg 2 to 0x3615eafd37
 displaced: relocated %rip from 0x400717 to 0x400937
 infrun: stop_pc = 0x400937
 infrun: delayed software breakpoint trap, ignoring
 infrun: no line number info
 infrun: stop_waiting
 0x0000000000400937 in __dso_handle ()
 1: x/i $pc
 => 0x400937:    and    %ah,0xa0d64(%rip)        # 0x4a16a1
 (gdb) FAIL: gdb.base/sigstep.exp: displaced=on: step on breakpoint, to handler: performing step


What should have happened is that the breakpoint hit in the signal
handler should have been presented to the user.  But note that
"preempt 'handle'" -- what happened instead is that
displaced_step_fixup confused the breakpoint in the signal handler for
the expected SIGTRAP indicating the displaced instruction was
single-stepped normally/successfully.

This should be affecting all software single-step targets in the same
way.

The fix is to make sure the core sees all signals when displaced
stepping, just like we already must see all signals when doing an
stepping over a breakpoint in-line.  We now get:

 infrun: target_wait (-1.0.0, status) =
 infrun:   570.570.0 [process 570],
 infrun:   status->kind = stopped, signal = GDB_SIGNAL_ALRM
 infrun: TARGET_WAITKIND_STOPPED
 displaced: restored process 570 0x400622
 infrun: stop_pc = 0x400842
 infrun: random signal (GDB_SIGNAL_ALRM)
 infrun: signal arrived while stepping over breakpoint
 infrun: inserting step-resume breakpoint at 0x400842
 infrun: resume (step=0, signal=GDB_SIGNAL_ALRM), trap_expected=0, current thread [process 570] at 0x400842
 LLR: Preparing to resume process 570, Alarm clock, inferior_ptid process 570
 LLR: PTRACE_CONT process 570, Alarm clock (resume event thread)
 infrun: prepare_to_wait
 linux_nat_wait: [process -1], [TARGET_WNOHANG]
 LLW: enter
 LNW: waitpid(-1, ...) returned 0, No child processes
 LLW: exit (ignore)
 infrun: target_wait (-1.0.0, status) =
 infrun:   -1.0.0 [process -1],
 infrun:   status->kind = ignore
 sigchld
 infrun: TARGET_WAITKIND_IGNORE
 infrun: prepare_to_wait
 linux_nat_wait: [process -1], [TARGET_WNOHANG]
 LLW: enter
 LNW: waitpid(-1, ...) returned 570, No child processes
 LLW: waitpid 570 received Trace/breakpoint trap (stopped)
 CSBB: process 570 stopped by software breakpoint
 LNW: waitpid(-1, ...) returned 0, No child processes
 LLW: trap ptid is process 570.
 LLW: exit
 infrun: target_wait (-1.0.0, status) =
 infrun:   570.570.0 [process 570],
 infrun:   status->kind = stopped, signal = GDB_SIGNAL_TRAP
 infrun: TARGET_WAITKIND_STOPPED
 infrun: stop_pc = 0x400717
 infrun: BPSTAT_WHAT_STOP_NOISY
 infrun: stop_waiting

 Breakpoint 3, handler (sig=14) at /home/pedro/gdb/mygit/src/gdb/testsuite/gdb.base/sigstep.c:35
 35        done = 1;

Hardware single-step targets already behave this way, because the
Linux backends (both native and gdbserver) always report signals to
the core if the thread was single-stepping.

As mentioned in the new comment in do_target_resume, we can't fix this
by instead making the displaced_step_fixup phase skip fixing up the PC
if the single step stopped somewhere we didn't expect.  Here's what
the backtrace would look like if we did that:

 Breakpoint 3, handler (sig=14) at /home/pedro/gdb/mygit/src/gdb/testsuite/gdb.base/sigstep.c:35
 35        done = 1;
 1: x/i $pc
 => 0x400717 <handler+7>:        movl   $0x1,0x200943(%rip)        # 0x601064 <done>
 (gdb) bt
 #0  handler (sig=14) at /home/pedro/gdb/mygit/src/gdb/testsuite/gdb.base/sigstep.c:35
 #1  <signal handler called>
 #2  0x0000000000400622 in _start ()
 (gdb) FAIL: gdb.base/sigstep.exp: displaced=on: step on breakpoint, to handler: backtrace

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

	* infrun.c (displaced_step_in_progress): New function.
	(do_target_resume): Advise target to report all signals if
	displaced stepping.

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

	* gdb.base/sigstep.exp (breakpoint_to_handler)
	(breakpoint_to_handler_entry): New parameter 'displaced'.  Use it.
	Test "backtrace" in handler.
	(breakpoint_over_handler): New parameter 'displaced'.  Use it.
	(top level): Add new "displaced" test axis to
	breakpoint_to_handler, breakpoint_to_handler_entry and
	breakpoint_over_handler.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Revert "Add extern_protected_data and set it for x86"
@ 2015-04-10 11:30 sergiodj+buildbot
  2015-04-10 13:44 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-10 11:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8d2ea2a80abad66250f2f4a1d38e3b8c796147f8 ***

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

Revert "Add extern_protected_data and set it for x86"
This reverts commit ca3fe95e469b9daec153caa2c90665f5daaec2b5.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] PR13858 - Can't do displaced stepping with no symbols
@ 2015-04-10  9:24 sergiodj+buildbot
  2015-04-10 10:12 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-10  9:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 906d60cf467b2d5a20ff04dbc4805a84ef313229 ***

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

PR13858 - Can't do displaced stepping with no symbols
Running break-interp.exp with the target always in non-stop mode trips
on PR13858, as enabling non-stop also enables displaced stepping.

The problem is that when GDB doesn't know where the entry point is, it
doesn't know where to put the displaced stepping scratch pad.  The
test added by this commit exercises this.  Without the fix, we get:

 (gdb) PASS: gdb.base/step-over-no-symbols.exp: displaced=on: break *$pc
 set displaced-stepping on
 (gdb) PASS: gdb.base/step-over-no-symbols.exp: displaced=on: set displaced-stepping on
 stepi
 0x00000000004005be in ?? ()
 Entry point address is not known.
 (gdb) PASS: gdb.base/step-over-no-symbols.exp: displaced=on: stepi
 p /x $pc
 $2 = 0x4005be
 (gdb) PASS: gdb.base/step-over-no-symbols.exp: displaced=on: get after PC
 FAIL: gdb.base/step-over-no-symbols.exp: displaced=on: advanced

The fix switches all GNU/Linux ports to get the entry point from
AT_ENTRY in the target auxiliary vector instead of from symbols.  This
is currently only done by PPC when Cell debugging is enabled, but I
think all archs should be able to do the same.  Note that
ppc_linux_displaced_step_location cached the result, I'm guessing to
avoid constantly re-fetching the auxv out of remote targets, but
that's no longer necessary nowadays, as the auxv blob is itself cached
in the inferior object.  The ppc_linux_entry_point_addr global is
obviously bad for multi-process too nowadays.

Tested on x86-64 (-m64/-m32), PPC64 (-m64/-m32) and S/390 GNU/Linux.
Yao tested the new test on ARM as well.

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

	PR gdb/13858
	* amd64-linux-tdep.c (amd64_linux_init_abi_common): Install
	linux_displaced_step_location as gdbarch_displaced_step_location
	hook.
	* arm-linux-tdep.c (arm_linux_init_abi): Likewise.
	* i386-linux-tdep.c (i386_linux_init_abi): Likewise.
	* linux-tdep.c (linux_displaced_step_location): New function,
	based on ppc_linux_displaced_step_location.
	* linux-tdep.h (linux_displaced_step_location): New declaration.
	* ppc-linux-tdep.c (ppc_linux_entry_point_addr): Delete.
	(ppc_linux_inferior_created, ppc_linux_displaced_step_location):
	Delete.
	(ppc_linux_init_abi): Install linux_displaced_step_location as
	gdbarch_displaced_step_location hook, even without Cell/B.E..
	(_initialize_ppc_linux_tdep): Don't install
	ppc_linux_inferior_created as inferior_created observer.
	* s390-linux-tdep.c (s390_gdbarch_init): Install
	linux_displaced_step_location as gdbarch_displaced_step_location
	hook.

gdb/testsuite/
2015-04-10  Pedro Alves  <palves@redhat.com>

	PR gdb/13858
	* gdb.base/step-over-no-symbols.exp: New file.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Update comments in compress.c
@ 2015-04-09 20:03 sergiodj+buildbot
  2015-04-10  5:00 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-09 20:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 18ece1defb99cf50dc7769444e3394c26329d497 ***

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

Update comments in compress.c
	* compress.c (bfd_compress_section_contents): Update comments.
	(bfd_init_section_decompress_status): Likewise.
	(bfd_init_section_compress_status): Likewise.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] xtensa: optimize find_removed_literal
@ 2015-04-09 17:47 sergiodj+buildbot
  2015-04-09 22:49 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-09 17:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3439c466273378021821473d3fc84990e089ae34 ***

Author: Max Filippov <jcmvbkbc@gmail.com>
Branch: master
Commit: 3439c466273378021821473d3fc84990e089ae34

xtensa: optimize find_removed_literal
find_removed_literal uses linear search to find removed literal by its
VMA. The list of literals is fixed at that point, build an ordered index
array and use binary search instead.

Original profile:

% time    self  children    called     name
-----------------------------------------
         56.72    0.00  297578/669392      translate_reloc
         70.86    0.00  371814/669392      relax_section
  67.9  127.58    0.00  669392         find_removed_literal
-----------------------------------------

Same data, after optimization:

% time    self  children    called     name
-----------------------------------------
          0.00    0.00  297578/669392      translate_reloc
          0.00    0.00  371814/669392      relax_section
   0.0    0.00    0.00  669392         find_removed_literal
          0.00    0.00   23838/23838       map_removed_literal
-----------------------------------------

2015-04-03  Max Filippov  <jcmvbkbc@gmail.com>
bfd/
	* elf32-xtensa.c (removed_literal_map_entry): new typedef.
	(removed_literal_map_entry_struct): new structure.
	(removed_literal_list_struct): add new fields: n_map and map.
	(map_removed_literal, removed_literal_compare): new functions.
	(find_removed_literal): build index array for literals ordered
	by VMA, use binary search to find removed literal.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] xtensa: optimize check_section_ebb_pcrels_fit
@ 2015-04-09 16:54 sergiodj+buildbot
  2015-04-09 20:51 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-09 16:54 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b2b326d246f839ee218192ac88da2384d929a072 ***

Author: Max Filippov <jcmvbkbc@gmail.com>
Branch: master
Commit: b2b326d246f839ee218192ac88da2384d929a072

xtensa: optimize check_section_ebb_pcrels_fit
The original check_section_ebb_pcrels_fit algorithm checks that text
actions proposed for current EBB are OK for every relocation in a
section. There's no need to check every relocation, because text actions
for EBB can only change size of that EBB, thus only affecting
relocations that in any way cross that EBB. In addition EBBs are
iterated in ascending order of their VMA, making it easier to track
relevant relocations.

Introduce a structure that can track relocations that cross the range of
VMAs of EBB and use it to only check relocations relevant to current EBB
in check_section_ebb_pcrels_fit.
It takes O(N log N) operations to build it and O(N) operations to move
current EBB VMA window through its entire range, where N is the number
of relocations in a section. The resulting complexity of
compute_text_actions is thus reduced from O(N^2) to O(N log N + N * M),
where M is the average number of relocations crossing each EBB.

Original profile:

% time    self  children    called     name
-----------------------------------------
         44.26   71.53    6429/6429        compute_text_actions
  50.2   44.26   71.53    6429         check_section_ebb_pcrels_fit
          1.16   20.12 347506666/347576152     pcrel_reloc_fits
          2.95   16.52 347506666/348104944     get_relocation_opnd
          2.01    9.74 347575100/361252208     r_reloc_init
          0.55    7.53 347575100/363381467     r_reloc_get_section
          5.76    0.02 695013332/695013332     xlate_offset_with_removed_text
          0.68    3.89 347575100/363483827     bfd_octets_per_byte
          0.32    0.00 347506666/349910253     is_alt_relocation
          0.18    0.11    6391/6391        build_xlate_map
          0.00    0.00    6429/19417168     get_xtensa_relax_info
          0.00    0.00    6391/6391        free_xlate_map
-----------------------------------------

Same data, after optimization:

% time    self  children    called     name
-----------------------------------------
          2.56    3.08    6429/6429        compute_text_actions
   8.2    2.56    3.08    6429         check_section_ebb_pcrels_fit
          0.08    0.91 17721075/17790561     pcrel_reloc_fits
          0.17    0.47 17721075/31685977     r_reloc_init
          0.43    0.00 35442150/35442150     xlate_offset_with_removed_text
          0.02    0.37 17721075/33815236     r_reloc_get_section
          0.22    0.11    6391/6391        build_xlate_map
          0.05    0.22 17721075/33917596     bfd_octets_per_byte
          0.03    0.00 17721075/20405299     is_alt_relocation
          0.01    0.00    6429/6429        reloc_range_list_update_range
          0.00    0.00    6429/19417168     get_xtensa_relax_info
          0.00    0.00    6391/6391        free_xlate_map
-----------------------------------------

2015-04-01  Max Filippov  <jcmvbkbc@gmail.com>
bfd/
	* elf32-xtensa.c (reloc_range_list, reloc_range_list_entry,
	reloc_range): new typedef.
	(reloc_range_list_struct, reloc_range_list_entry_struct,
	reloc_range_struct): new structures.
	(reloc_range_compare, build_reloc_ranges,
	reloc_range_list_append, reloc_range_list_remove,
	reloc_range_list_update_range, free_reloc_range_list): new
	functions.
	(compute_text_actions): precompute relocation opcodes before the
	loop. Add relevant_relocs variable, initialize it before the
	loop, pass it to the check_section_ebb_pcrels_fit.
	(check_section_ebb_pcrels_fit): add new parameter:
	relevant_relocs. Update address range in the relevant_relocs if
	it's non-NULL and iterate only over relevant relocations.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Import strtok_r gnulib module
@ 2015-04-09 10:58 sergiodj+buildbot
  2015-04-09 13:17 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-09 10:58 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 421693b020bf6e306c6c795541d0bd9dad0db1f1 ***

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

Import strtok_r gnulib module
gdb/linux-tdep.c recently gained a strtok_r use.  That broke
--enable-targets=all with some versions of mingw64, which don't have
strtok_r:

  https://sourceware.org/ml/gdb-patches/2015-04/msg00266.html

Fix that by importing the strtok_r gnulib module.

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

	* gnulib/update-gnulib.sh (IMPORTED_GNULIB_MODULES): Add strtok_r.
	* gnulib/Makefile.in (aclocal_m4_deps): Add import/m4/strtok_r.m4.
	* gnulib/configure, gnulib/config.in, gnulib/aclocal.m4: Regenerate.
	* gnulib/import/Makefile.am: Update.
	* gnulib/import/Makefile.in: Update.
	* gnulib/import/m4/gnulib-cache.m4: Update.
	* gnulib/import/m4/gnulib-comp.m4: Update.
	* gnulib/import/m4/strtok_r.m4: New file.
	* gnulib/import/strtok_r.c: New file.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Fix Python completion when using the "complete" command
@ 2015-04-08 22:42 sergiodj+buildbot
  2015-04-08 23:49 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-08 22:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6d62641c832525382336c1b04731d85cb6c398e7 ***

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

Fix Python completion when using the "complete" command
This patch is related to PR python/16699, and is an improvement over the
patch posted here:

  <https://sourceware.org/ml/gdb-patches/2014-03/msg00301.html>

Keith noticed that, when using the "complete" command on GDB to complete
a Python command, some strange things could happen.  In order to
understand what can go wrong, I need to explain how the Python
completion mechanism works.

When the user requests a completion of a Python command by using TAB,
GDB will first try to determine the right set of "brkchars" that will be
used when doing the completion.  This is done by actually calling the
"complete" method of the Python class.  Then, when we already know the
"brkchars" that will be used, we call the "complete" method again, for
the same values.

If you read the thread mentioned above, you will see that one of the
design decisions was to make the "cmdpy_completer_helper" (which is the
function the does the actual calling of the "complete" method) cache the
first result of the completion, since this result will be used in the
second call, to do the actual completion.

The problem is that the "complete" command does not process the
brkchars, and the current Python completion mechanism (improved by the
patch mentioned above) relies on GDB trying to determine the brkchars,
and then doing the completion itself.  Therefore, when we use the
"complete" command instead of doing a TAB-completion on GDB, there is a
scenario where we can use the invalid cache of a previous Python command
that was completed before.  For example:

  (gdb) A <TAB>
  (gdb) complete B
  B value1
  B value10
  B value2
  B value3
  B value4
  B value5
  B value6
  B value7
  B value8
  B value9
  (gdb) B <TAB>
  comp1   comp2   comp4   comp6   comp8
  comp10  comp3   comp5   comp7   comp9

Here, we see that "complete B " gave a different result than "B <TAB>".
The reason for that is because "A <TAB>" was called before, and its
completion results were "value*", so when GDB tried to "complete B " it
wrongly answered with the results for A.  The problem here is using a
wrong cache (A's cache) for completing B.

We tried to come up with a solution that would preserve the caching
mechanism, but it wasn't really possible.  So I decided to completely
remove the cache, and doing the method calling twice for every
completion.  This is not optimal, but I do not think it will impact
users noticeably.

It is worth mentioning another small issue that I found.  The code was
doing:

  wordobj = PyUnicode_Decode (word, sizeof (word), host_charset (), NULL);

which is totally wrong, because using "sizeof" here will lead to always
the same result.  So I changed this to use "strlen".  The testcase also
catches this problem.

Keith kindly expanded the existing testcase to cover the problem
described above, and everything is passing.

gdb/ChangeLog:
2015-04-08  Sergio Durigan Junior  <sergiodj@redhat.com>

	PR python/16699
	* python/py-cmd.c (cmdpy_completer_helper): Adjust function to not
	use a caching mechanism.  Adjust comments and code to reflect
	that.  Replace 'sizeof' by 'strlen' when fetching 'wordobj'.
	(cmdpy_completer_handle_brkchars): Adjust call to
	cmdpy_completer_helper.  Call Py_XDECREF for 'resultobj'.
	(cmdpy_completer): Likewise.

gdb/testsuite/ChangeLog:
2015-04-08  Keith Seitz  <keiths@redhat.com>

	PR python/16699
	* gdb.python/py-completion.exp: New tests for completion.
	* gdb.python/py-completion.py (CompleteLimit1): New class.
	(CompleteLimit2): Likewise.
	(CompleteLimit3): Likewise.
	(CompleteLimit4): Likewise.
	(CompleteLimit5): Likewise.
	(CompleteLimit6): Likewise.
	(CompleteLimit7): Likewise.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [spu] Don't call set_gdbarch_cannot_step_breakpoint in spu_gdbarch_init
@ 2015-04-08 15:50 sergiodj+buildbot
  2015-04-08 17:21 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-08 15:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 85558555ec343f6e8ec32da409c838954e68132f ***

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

[spu] Don't call set_gdbarch_cannot_step_breakpoint in spu_gdbarch_init
Nowadays, in infrun.c:resume, the setting to 'step' variable is like:

  if (use_displaced_stepping (gdbarch)
      && tp->control.trap_expected
      && sig == GDB_SIGNAL_0
      && !current_inferior ()->waiting_for_vfork_done)
    {
    }
  /* Do we need to do it the hard way, w/temp breakpoints?  */
  else if (step)
    step = maybe_software_singlestep (gdbarch, pc); <-- [1]

  ...

  if (execution_direction != EXEC_REVERSE
      && step && breakpoint_inserted_here_p (aspace, pc))
    {
      ...
      if (gdbarch_cannot_step_breakpoint (gdbarch)) <-- [2]
        step = 0;
    }

spu doesn't have displaced stepping and uses software single step,
so 'step' is set to zero in [1], and [2] becomes unreachable as a
result.  So don't have to call set_gdbarch_cannot_step_breakpoint
in spu_gdbarch_init.

gdb:

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

	* spu-tdep.c (spu_gdbarch_init): Don't call
	set_gdbarch_cannot_step_breakpoint.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Initialize variable on gdb/linux-tdep.c:decode_vmflags
@ 2015-04-07 21:12 sergiodj+buildbot
  2015-04-08  4:35 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-07 21:12 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d249a14abe5c2ee3ba4dc6c47e68e41ddc2025a4 ***

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

Initialize variable on gdb/linux-tdep.c:decode_vmflags
This obvious commit initializes the 'saveptr' variable on
gdb/linux-tdep.c:decode_vmflags.  This was causing a build failure on
Fedora 21 x86_64, caught by the BuildBot here:

  <https://sourceware.org/ml/gdb-testers/2015-q2/msg00450.html>


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] gdb.base/interrupt.exp: Use send_inferior/$inferior_spawn_id
@ 2015-04-07 20:38 sergiodj+buildbot
  2015-04-07 23:58 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-07 20:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b97fde9213b9217499959f7aebbf076b00c7008b ***

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

gdb.base/interrupt.exp: Use send_inferior/$inferior_spawn_id
The gdb.base/interrupt.exp test is important for testing system call
restarting, but because it depends on inferior I/O, it ends up skipped
against gdbserver.  This patch adjusts the test to use send_inferior
and $inferior_spawn_id so it works against GDBserver.

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

	* gdb.base/interrupt.exp: Don't skip if $inferior_spawn_id !=
	$gdb_spawn_id.  Use send_inferior and $inferior_spawn_id to
	interact with inferior program.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] testsuite: Introduce $inferior_spawn_id
@ 2015-04-07 20:04 sergiodj+buildbot
  2015-04-07 22:58 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-07 20:04 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f71c18e755dac28c61a5e5c94fbc8a84eb573679 ***

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

testsuite: Introduce $inferior_spawn_id
Some important tests, like gdb.base/interrupt.exp end up skipped
against gdbserver, because they depend on inferior I/O, which
gdbserver doesn't do.

This patch adds a mechanism that makes it possible to make them work.
It adds a new "inferior_spawn_id" global that is the spawn ID used for
I/O interaction with the inferior.  By default, for native targets, or
remote targets that can do I/O through GDB (semi-hosting) this will be
the same as the gdb/host spawn ID.  Otherwise, the board may set this
to some other spawn ID.  When debugging with GDBserver, this will be
set to GDBserver's spawn ID.

Then tests can use send_inferior instead of send_gdb to send input to
the inferior, and use expect's "-i" switch to select which spawn ID to
use for matching input/output.  That is, something like this will now
work:

  send_inferior "echo me\n"
  gdb_test_multiple "continue" "test msg" {
    -i "$inferior_spawn_id" -re "echo me\r\necho\r\n" {
      ...
    }
  }

Or even:

  gdb_test_multiple "continue" "test msg" {
    -i "$inferior_spawn_id" -re "hello world" {
      ...
    }
    -i "$gdb_spawn_id" -re "error.*$gdb_prompt $" {
      ...
    }
  }

Of course, by default, gdb_test_multiple still matches with
$gdb_spawn_id.

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

	* lib/gdb.exp (inferior_spawn_id): New global.
	(gdb_test_multiple): Handle "-i".  Reset the spawn id to GDB's
	spawn id after processing the user code.
	(default_gdb_start): Set inferior_spawn_id.
	(send_inferior): New procedure.
	* lib/gdbserver-support.exp (gdbserver_start): Set
	inferior_spawn_id.
	(close_gdbserver, gdb_exit): Unset inferior_spawn_id.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] testsuite: Don't use expect_background to reap gdbserver
@ 2015-04-07 19:30 sergiodj+buildbot
  2015-04-07 21:39 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-07 19:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6423214fcb912a5d402ffcb84d6f61f2b900a900 ***

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

testsuite: Don't use expect_background to reap gdbserver
I adjusted a test to do 'expect -i $server_spawn_id -re ...', and saw
really strange behavior.  Whether that expect would work, depended on
whether GDB would also send output and the same expect matched it too
(on $gdb_spawn_id).  I was perplexed until I noticed that
gdbserver_spawn spawns gdbserver and then uses expect_background to
reap gdbserver.  That expect_background conflicts/races with any
"expect -i $server_spawn_id" done anywhere else in parallel...

In order to make it possible for tests to read inferior I/O out of
$server_spawn_id, we to get rid of that expect_background.  This patch
makes us instead reap gdbserver's spawn id when GDB exits.  If GDB is
still around, this gives a chance for gdbserver to exit cleanly.  The
current code in gdb_finish uses "kill", but that doesn't work with
extended-remote (gdbserver doesn't exit).  We now use "monitor exit"
instead which works in both remote and extended-remote modes.

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

	* lib/gdb.exp (gdb_finish): Delete persistent gdbserver handling.
	* lib/gdbserver-support.exp (gdbserver_start): Make
	$server_spawn_id global.
	(gdbserver_start): Don't wait for gdbserver's spawn id with
	expect_background.
	(close_gdbserver): New procedure.
	(gdb_exit): Rename the default version and reimplement.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] gdb_test_multiple: Fix user code argument processing
@ 2015-04-07 19:06 sergiodj+buildbot
  2015-04-07 20:42 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-07 19:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 71c0ee8cb9d7d77e8b480aaad715cc5343737993 ***

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

gdb_test_multiple: Fix user code argument processing
While teaching gdb_test_multiple to forward "-i" to gdb_expect, I
found that with:

      gdb_test_multiple (...) {
        -i $some_variable -re "..." {}
      }

$some_variable was not getting expanded in the gdb_test_multiple
caller's scope.  This is a bug inside gdb_test_multiple.  When
processing an argument in passed in user code, it was appending the
original argument literally, instead of appending the uplist'ed
argument.

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

        * lib/gdb.exp (gdb_test_multiple): When processing an argument,
	append the substituted item, not the original item.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Fix gdb.trace/actions.exp race
@ 2015-04-07 16:39 sergiodj+buildbot
  2015-04-07 17:51 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-07 16:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9f6dbe2bbbdcc3694f264878e10c6b80285b4608 ***

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

Fix gdb.trace/actions.exp race
I saw this on PPC64 once:

  not installed on target
  (gdb) PASS: gdb.trace/actions.exp: 5.10a: verify teval actions set for two tracepoints
  break main
  Breakpoint 4 at 0x10000c6c: file ../../../src/gdb/testsuite/gdb.trace/actions.c, line 139.
  (gdb) PASS: gdb.trace/actions.exp: break main
  run
  Starting program: /home/palves/gdb/build/gdb/testsuite/outputs/gdb.trace/actions/actions
  tstatus

  Breakpoint 4, main (argc=1, argv=0x3fffffffebb8, envp=0x3fffffffebc8) at ../../../src/gdb/testsuite/gdb.trace/actions.c:139
  139       begin ();
  (gdb) tstatus
  Trace can not be run on this target.
  (gdb) actions 1
  Enter actions for tracepoint 1, one per line.
  End with a line saying just "end".
  >collect $regs
  >end
  (gdb) PASS: gdb.trace/actions.exp: set actions for first tracepoint
  tstart
  You can't do that when your target is `native'
  (gdb) FAIL: gdb.trace/actions.exp: tstart
  info tracepoints 1
  Num     Type           Disp Enb Address            What
  1       tracepoint     keep y   0x00000000100007c8 in gdb_c_test at ../../../src/gdb/testsuite/gdb.trace/actions.c:74
	  collect $regs
	  not installed on target
  ...

followed by a cascade of FAILs.  The "tstatus" was supposed to detect
that this target (native) can't do tracepoints, but, alas, it didn't.

That detection failed because 'gdb_test "break main"' doesn't expect
anything, and then the output was slow enough that 'gdb_test ""
"Breakpoint .*"' matched the output of "break main"...

The fix is to use gdb_breakpoint instead.  Also check the result of
gdb_test while at it.

Tested on x86-64 Fedora 20, native and gdbserver.

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

	* gdb.trace/actions.exp: Use gdb_breakpoint instead of gdb_test
	that doesn't expect anything.  Return early if running to main
	fails.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Displaced stepping debug: fetch the right regcache
@ 2015-04-07 11:49 sergiodj+buildbot
  2015-04-07 13:23 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-07 11:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d9b67d9f4127191679c743d1f47d2421d6dcede7 ***

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

Displaced stepping debug: fetch the right regcache
Although not currently possible in practice when we get here,
'resume_ptid' can also be a wildcard throughout this function.  It's
clearer to fetch the regcache using the thread's ptid.

gdb/ChangeLog:
2015-04-07  Pedro Alves  <pedro@codesourcery.com>

	* infrun.c (resume) <displaced stepping debug output>: Get the
	leader thread's regcache, not resume_ptid's.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Properly set alarm value in gdb.threads/non-stop-fair-events.exp
@ 2015-04-07 11:17 sergiodj+buildbot
  2015-04-07 12:23 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-07 11:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 337532fab150dc531c92a31e179df96b98a619c0 ***

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

Properly set alarm value in gdb.threads/non-stop-fair-events.exp
Nowadays, the alarm value is 60, and alarm is generated on some slow
boards.  This patch is to pass DejaGNU timeout value to the program,
and move the alarm call before going to infinite loop.  If any thread
has activities, the alarm is reset.

gdb/testsuite:

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

	* gdb.threads/non-stop-fair-events.c (SECONDS): New macro.
	(child_function): Call alarm.
	(main): Move call to alarm into the loop.
	* gdb.threads/non-stop-fair-events.exp: Build program with
	-DTIMEOUT=$timeout.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] sim: move sim-engine.o/sim-hrw.o to the common list
@ 2015-04-07  4:06 sergiodj+buildbot
  2015-04-07  5:01 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-07  4:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 122bbfb52a7990dbed5f5da79cf8d9eb305ca7e3 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 122bbfb52a7990dbed5f5da79cf8d9eb305ca7e3

sim: move sim-engine.o/sim-hrw.o to the common list
This makes these two objects available to all sims by default.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] symtab.c (hash_symbol_entry): Hash STRUCT_DOMAIN symbols as VAR_DOMAIN.
@ 2015-04-06 15:43 sergiodj+buildbot
  2015-04-06 16:35 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-06 15:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2c26b84f4520591762dfb7f740fb85c15c21a2ea ***

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

symtab.c (hash_symbol_entry): Hash STRUCT_DOMAIN symbols as VAR_DOMAIN.
gdb/ChangeLog:

	* symtab.c (hash_symbol_entry): Hash STRUCT_DOMAIN symbols as
	VAR_DOMAIN.
	(symbol_cache_lookup): Clarify use of bsc_ptr, slot_ptr parameters.
	Include symbol domain in debugging output.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] sim: m68hc11: add a basic testsuite
@ 2015-04-05  8:49 sergiodj+buildbot
  2015-04-05  9:09 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-05  8:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT aad84fa6aec2c3fcfebaa322cfdea7b47365e8fb ***

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

sim: m68hc11: add a basic testsuite


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] sim: lm32: add a basic testsuite
@ 2015-04-05  6:30 sergiodj+buildbot
  2015-04-05  7:18 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-05  6:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e56dbbb92fdfa714e7b9ba9d70da8ab0ae3558be ***

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

sim: lm32: add a basic testsuite


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] gdbtypes.c: remove the usuned "top_level" parameter
@ 2015-04-04  0:13 sergiodj+buildbot
  2015-04-04 14:41 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-04  0:13 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 25755e2b85e2bd5b313ea87f32000bf9a47dbbf8 ***

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

gdbtypes.c: remove the usuned "top_level" parameter
This paramater is no longer useful after the previous commit, so remove
it as a cleanup.

gdb/ChangeLog:

	* gdbtypes.c (is_dynamic_type_internal): Remove the unused
	"top_level" parameter.
	(resolve_dynamic_type_internal): Remove the unused "top_level"
	parameter.  Update call to is_dynamic_type_internal.
	(is_dynamic_type): Update call to is_dynamic_type_internal.
	(resolve_dynamic_range): Update call to
	resolve_dynamic_type_internal.
	(resolve_dynamic_union): Likewise.
	(resolve_dynamic_struct): Likewise.
	(resolve_dynamic_type): Likewise.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Do not consider reference types as dynamic
@ 2015-04-03 13:39 sergiodj+buildbot
  2015-04-04 13:48 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-03 13:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 961f41602529c9cd4f88af6c02fb61fb55100e27 ***

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

Do not consider reference types as dynamic
Even when referenced types are dynamic, the corresponding referencing
type should not be considered as dynamic: it's only a pointer.  This
prevents reference type for values not in memory to be resolved.

gdb/ChangeLog:

	* gdbtypes.c (is_dynamic_type_internal): Remove special handling
	of TYPE_CODE_REF types so that they are not considered as
	dynamic depending on the referenced type.
	(resolve_dynamic_type_internal): Likewise.

gdb/testsuite/ChangeLog:

	* gdb.ada/funcall_ref.exp: New file.
	* gdb.ada/funcall_ref/foo.adb: New file.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] kfail two tests in no-unwaited-for-left.exp for remote target
@ 2015-04-03  1:12 sergiodj+buildbot
  2015-04-04 10:24 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-03  1:12 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cafda5977a98aef514ff86daca2fa94205bdd34e ***

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

kfail two tests in no-unwaited-for-left.exp for remote target
I see these two fails in no-unwaited-for-left.exp in remote testing
for aarch64-linux target.

...
continue
Continuing.
warning: Remote failure reply: E.No unwaited-for children left.

[Thread 1084] #2 stopped.
(gdb) FAIL: gdb.threads/no-unwaited-for-left.exp: continue stops when thread 2 exits

....
continue
Continuing.
warning: Remote failure reply: E.No unwaited-for children left.

[Thread 1081] #1 stopped.
(gdb) FAIL: gdb.threads/no-unwaited-for-left.exp: continue stops when the main thread exits

I checked the gdb.log on buildbot, and find that these two fails also
appear on Debian-i686-native-extended-gdbserver and Fedora-ppc64be-native-gdbserver-m64.
I recall that they are about local/remote parity, and related RSP is missing.
There has been already a PR 14618 about it.  This patch is to kfail them
on remote target.

gdb/testsuite:

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

	* gdb.threads/no-unwaited-for-left.exp: Set up kfail if target
	is remote.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Document "target:" sysroot changes
@ 2015-04-03  0:31 sergiodj+buildbot
  2015-04-04  6:44 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-03  0:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 599bd15cdae16c5c420c85cf4853fcfd769bce75 ***

Author: Gary Benson <gbenson@redhat.com>
Branch: master
Commit: 599bd15cdae16c5c420c85cf4853fcfd769bce75

Document "target:" sysroot changes
This commit documents the newly added "target:" sysroot feature.

gdb/ChangeLog:

	* NEWS: Announce the new default sysroot of "target:".

gdb/doc/ChangeLog:

	* gdb.texinfo (set sysroot): Document "target:".


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Set zlibdir/zlibinc with top_builddir/top_srcdir
@ 2015-04-02 23:49 sergiodj+buildbot
  2015-04-04  7:43 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-02 23:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT df7f7547a5cb6455ad07855482797860b71fb532 ***

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

Set zlibdir/zlibinc with top_builddir/top_srcdir
	* zlib.m4 (AM_ZLIB): Set zlibdir to -L\$(top_builddir)/../zlib
	and set zlibinc to -I\$(top_srcdir)/../zlib.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Update exec_file_attach to cope with "target:" filenames
@ 2015-04-02 23:24 sergiodj+buildbot
  2015-04-04  4:07 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-02 23:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 64c0b5de8dfd68c54060b07d54b1edf8d22fc52b ***

Author: Gary Benson <gbenson@redhat.com>
Branch: master
Commit: 64c0b5de8dfd68c54060b07d54b1edf8d22fc52b

Update exec_file_attach to cope with "target:" filenames
This commit adds support for filenames prefixed	with "target:" to
exec_file_attach.  This is required to correctly follow inferior
exec* calls when a gdb_sysroot prefixed with "target:" is set.

gdb/ChangeLog:

	* exec.c (exec_file_attach): Support "target:" filenames.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Rearrange symfile_bfd_open
@ 2015-04-02 22:09 sergiodj+buildbot
  2015-04-03 19:50 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-02 22:09 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 97a41605e2473c67e82ef5147b4866768bd5a566 ***

Author: Gary Benson <gbenson@redhat.com>
Branch: master
Commit: 97a41605e2473c67e82ef5147b4866768bd5a566

Rearrange symfile_bfd_open
symfile_bfd_open handled what were remote files as a special case.
Converting from "remote:" files to "target:" made symfile_bfd_open
look like this:

  if remote:
    open bfd, check format, etc
    return
  local-specific stuff
  open bfd, check format, etc
  return

This commit rearranges symfile_bfd_open to remove the duplicated
code, like this:

  if local:
      local-specific stuff
  open bfd, check format, etc
  return

gdb/ChangeLog:

	* symfile.c (symfile_bfd_open): Reorder to remove duplicated
	checks and error messages.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Strip "target:" prefix in solib_find if accessing local files
@ 2015-04-02 22:04 sergiodj+buildbot
  2015-04-03 23:25 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-02 22:04 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b57fbfba4b53434252fce55e323f08aeab556409 ***

Author: Gary Benson <gbenson@redhat.com>
Branch: master
Commit: b57fbfba4b53434252fce55e323f08aeab556409

Strip "target:" prefix in solib_find if accessing local files
This commit updates solib_find to strip the "target:" prefix from
gdb_sysroot when accessing local files.  This ensures that the same
search algorithm is used for local files regardless of whether a
"target:" prefix was used or not.  It also avoids cluttering GDB's
output with unnecessary "target:" prefixes on paths.

gdb/ChangeLog:

	* solib.c (solib_find): Strip "target:" prefix from sysroot
	if accessing local files.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Convert "remote:" sysroots to "target:" and remove "remote:"
@ 2015-04-02 21:12 sergiodj+buildbot
  2015-04-03  9:36 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-02 21:12 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2938e6cf0809cd81d1593f414ea5836812e68ed2 ***

Author: Gary Benson <gbenson@redhat.com>
Branch: master
Commit: 2938e6cf0809cd81d1593f414ea5836812e68ed2

Convert "remote:" sysroots to "target:" and remove "remote:"
The functionality of "target:" sysroots is a superset of the
functionality of "remote:" sysroots.  This commit causes the
"set sysroot" command to rewrite "remote:" sysroots as "target:"
sysroots and replaces "remote:" specific code with "target:"
specific code where still necessary.

gdb/ChangeLog:

	* remote.h (REMOTE_SYSROOT_PREFIX): Remove definition.
	(remote_filename_p): Remove declaration.
	(remote_bfd_open): Likewise.
	* remote.c (remote_bfd_iovec_open): Remove function.
	(remote_bfd_iovec_close): Likewise.
	(remote_bfd_iovec_pread): Likewise.
	(remote_bfd_iovec_stat): Likewise.
	(remote_filename_p): Likewise.
	(remote_bfd_open): Likewise.
	* symfile.h (gdb_bfd_open_maybe_remote): Remove declaration.
	* symfile.c (separate_debug_file_exists): Use gdb_bfd_open.
	(gdb_bfd_open_maybe_remote): Remove function.
	(symfile_bfd_open):  Replace remote filename check with
	target filename check.
	(reread_symbols): Use gdb_bfd_open.
	* build-id.c (gdbcore.h): New include.
	(build_id_to_debug_bfd): Use gdb_bfd_open.
	* infcmd.c (attach_command_post_wait): Remove remote filename
	check.
	* solib.c (solib_find): Replace remote-specific handling with
	target-specific handling.  Update comments where necessary.
	(solib_bfd_open): Replace remote-specific handling with
	target-specific handling.
	(gdb_sysroot_changed): New function.
	(_initialize_solib): Call the above when gdb_sysroot changes.
	* windows-tdep.c (gdbcore.h): New include.
	(windows_xfer_shared_library): Use gdb_bfd_open.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] sim: clean up SIM_EXTRA_OBJS references
@ 2015-04-02 19:26 sergiodj+buildbot
  2015-04-02 20:12 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-02 19:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1a8faa2aa652d8d6c6c3daa83b1dac35ee27e64e ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 1a8faa2aa652d8d6c6c3daa83b1dac35ee27e64e

sim: clean up SIM_EXTRA_OBJS references
This variable was deleted in previous commits and is not used anymore.
Prune any stray references to it.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] keep_going: Add missing discard_cleanups call
@ 2015-04-01 19:34 sergiodj+buildbot
  2015-04-02 13:05 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-01 19:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT de1fe8c8ab7f67856d9f2e2c5aa491cec01d3e85 ***

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

keep_going: Add missing discard_cleanups call
By inspection, I noticed a path where we return without discarding the
cleanups.

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

	* infrun.c (keep_going): Also discard cleanups if inserting
	breakpoints fails.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Use do_target_resume when stepping past permanent breakpoint too
@ 2015-04-01 16:39 sergiodj+buildbot
  2015-04-02 11:18 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-01 16:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1ac806b8a7d0c09a0052751262f37336fb06bf6f ***

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

Use do_target_resume when stepping past permanent breakpoint too
We can use the recently added do_target_resume do simplify the code a
bit here.

Tested on x86_64 Fedora 20.

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

	* infrun.c (resume) <step past permanent breakpoint>: Use
	do_target_resume.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Add --with-system-zlib to top level configure
@ 2015-04-01 13:45 sergiodj+buildbot
  2015-04-01 23:44 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-01 13:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cf39cfc52ebd683d55fc396a77355f34b5094c04 ***

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

Add --with-system-zlib to top level configure
The top level configure supports --with-system-zlib.  This patch makes
configure --help to display --with-system-zlib.

	* configure.ac: Add --with-system-zlib.
	* configure: Regenerated.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] GDBServer: give more complete usage information
@ 2015-04-01 10:55 sergiodj+buildbot
  2015-04-01 20:01 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-01 10:55 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 41f98f0276aede918c3aca37aa6371c8a3c9fbe7 ***

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

GDBServer: give more complete usage information
--attach/--multi are currently only mentioned on the usage info first
lines, the meaning of PROG is completely absent and the COMM text does
not mention '-/stdio'.

A few options are missing:

 . --disable-randomization / --no-disable-randomization is not mentioned.

Although the manual has a comment saying these are superceded by
QDisableRandomization, that only makes sense for "run" in
extended-remote mode.  When we start gdbserver passing it a PROG,
--disable-randomization / --no-disable-randomization do take effect.
So I think we should document these.

 . We show --debug / --remote-debug, so might as well show --disable-packet too.

GDB's --help has this "For more information, consult the GDB manual"
blurb that is missing in GDBserver's --help.

Then shuffle things around a bit into "Operating modes", "Other
options" and "Debug options" sections, similarly to GDB's --help
structure.

Before:

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
$ ./gdbserver/gdbserver --help
Usage:  gdbserver [OPTIONS] COMM PROG [ARGS ...]
        gdbserver [OPTIONS] --attach COMM PID
        gdbserver [OPTIONS] --multi COMM

COMM may either be a tty device (for serial debugging), or
HOST:PORT to listen for a TCP connection.

Options:
  --debug               Enable general debugging output.
  --debug-format=opt1[,opt2,...]
                        Specify extra content in debugging output.
                          Options:
                            all
                            none
                            timestamp
  --remote-debug        Enable remote protocol debugging output.
  --version             Display version information and exit.
  --wrapper WRAPPER --  Run WRAPPER to start new programs.
  --once                Exit after the first connection has closed.
Report bugs to "<http://www.gnu.org/software/gdb/bugs/>".
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

After:

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
$ ./gdbserver/gdbserver --help
Usage:  gdbserver [OPTIONS] COMM PROG [ARGS ...]
        gdbserver [OPTIONS] --attach COMM PID
        gdbserver [OPTIONS] --multi COMM

COMM may either be a tty device (for serial debugging),
HOST:PORT to listen for a TCP connection, or '-' or 'stdio' to use
stdin/stdout of gdbserver.
PROG is the executable program.  ARGS are arguments passed to inferior.
PID is the process ID to attach to, when --attach is specified.

Operating modes:

  --attach              Attach to running process PID.
  --multi               Start server without a specific program, and
                        only quit when explicitly commanded.
  --once                Exit after the first connection has closed.
  --help                Print this message and then exit.
  --version             Display version information and exit.

Other options:

  --wrapper WRAPPER --  Run WRAPPER to start new programs.
  --disable-randomization
                        Run PROG with address space randomization disabled.
  --no-disable-randomization
                        Don't disable address space randomization when
                        starting PROG.

Debug options:

  --debug               Enable general debugging output.
  --debug-format=opt1[,opt2,...]
                        Specify extra content in debugging output.
                          Options:
                            all
                            none
                            timestamp
  --remote-debug        Enable remote protocol debugging output.
  --disable-packet=opt1[,opt2,...]
                        Disable support for RSP packets or features.
                          Options:
                            vCont, Tthread, qC, qfThreadInfo and
                            threads (disable all threading packets).

For more information, consult the GDB manual (available as on-line
info or a printed manual).
Report bugs to "<http://www.gnu.org/software/gdb/bugs/>".
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

gdb/gdbserver/ChangeLog:
2015-04-01  Pedro Alves  <palves@redhat.com>
	    Cleber Rosa  <crosa@redhat.com>

	* server.c (gdbserver_usage): Reorganize and extend the usage
	message.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] sim: run: punt!
@ 2015-04-01  6:06 sergiodj+buildbot
  2015-04-01 17:44 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-01  6:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0fe84f3fbe9a740c38a8dbaa0150b8e4c25c69dd ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 0fe84f3fbe9a740c38a8dbaa0150b8e4c25c69dd

sim: run: punt!
Now that all targets have been converted to nrun, we can finally punt
this old inconsistent interface.

A few stray references to the old run were sprinkled about; clean them
up in the process.

We leave behind the run(1) man page mostly so that we get it updated for
the new nrun interface.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Implement support for checking /proc/PID/coredump_filter
@ 2015-04-01  0:32 sergiodj+buildbot
  2015-04-01 15:10 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-04-01  0:32 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT df8411da087dc05481926f4c4a82deabc5bc3859 ***

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

Implement support for checking /proc/PID/coredump_filter
This patch, as the subject says, extends GDB so that it is able to use
the contents of the file /proc/PID/coredump_filter when generating a
corefile.  This file contains a bit mask that is a representation of
the different types of memory mappings in the Linux kernel; the user
can choose to dump or not dump a certain type of memory mapping by
enabling/disabling the respective bit in the bit mask.  Currently,
here is what is supported:

  bit 0  Dump anonymous private mappings.
  bit 1  Dump anonymous shared mappings.
  bit 2  Dump file-backed private mappings.
  bit 3  Dump file-backed shared mappings.
  bit 4 (since Linux 2.6.24)
         Dump ELF headers.
  bit 5 (since Linux 2.6.28)
         Dump private huge pages.
  bit 6 (since Linux 2.6.28)
         Dump shared huge pages.

(This table has been taken from core(5), but you can also read about it
on Documentation/filesystems/proc.txt inside the Linux kernel source
tree).

The default value for this file, used by the Linux kernel, is 0x33,
which means that bits 0, 1, 4 and 5 are enabled.  This is also the
default for GDB implemented in this patch, FWIW.

Well, reading the file is obviously trivial.  The hard part, mind you,
is how to determine the types of the memory mappings.  For that, I
extended the code of gdb/linux-tdep.c:linux_find_memory_regions_full and
made it rely *much more* on the information gathered from
/proc/<PID>/smaps.  This file contains a "verbose dump" of the
inferior's memory mappings, and we were not using as much information as
we could from it.  If you want to read more about this file, take a look
at the proc(5) manpage (I will also write a blog post soon about
everything I had to learn to get this patch done, and when I it is ready
I will post it here).

With Oleg Nesterov's help, we could improve the current algorithm for
determining whether a memory mapping is anonymous/file-backed,
private/shared.  GDB now also respects the MADV_DONTDUMP flag and does
not dump the memory mapping marked as so, and will always dump
"[vsyscall]" or "[vdso]" mappings (just like the Linux kernel).

In a nutshell, what the new code is doing is:

- If the mapping is associated to a file whose name ends with
  " (deleted)", or if the file is "/dev/zero", or if it is "/SYSV%08x"
  (shared memory), or if there is no file associated with it, or if
  the AnonHugePages: or the Anonymous: fields in the /proc/PID/smaps
  have contents, then GDB considers this mapping to be anonymous.
  There is a special case in this, though: if the memory mapping is a
  file-backed one, but *also* contains "Anonymous:" or
  "AnonHugePages:" pages, then GDB considers this mapping to be *both*
  anonymous and file-backed, just like the Linux kernel does.  What
  that means is simple: this mapping will be dumped if the user
  requested anonymous mappings *or* if the user requested file-backed
  mappings to be present in the corefile.

  It is worth mentioning that, from all those checks described above,
  the most fragile is the one to see if the file name ends with
  " (deleted)".  This does not necessarily mean that the mapping is
  anonymous, because the deleted file associated with the mapping may
  have been a hard link to another file, for example.  The Linux
  kernel checks to see if "i_nlink == 0", but GDB cannot easily do
  this check (as it has been discussed, GDB would need to run as root,
  and would need to check the contents of the /proc/PID/map_files/
  directory in order to determine whether the deleted was a hardlink
  or not).  Therefore, we made a compromise here, and we assume that
  if the file name ends with " (deleted)", then the mapping is indeed
  anonymous.  FWIW, this is something the Linux kernel could do
  better: expose this information in a more direct way.

- If we see the flag "sh" in the VmFlags: field (in /proc/PID/smaps),
  then certainly the memory mapping is shared (VM_SHARED).  If we have
  access to the VmFlags, and we don't see the "sh" there, then
  certainly the mapping is private.  However, older Linux kernels (see
  the code for more details) do not have the VmFlags field; in that
  case, we use another heuristic: if we see 'p' in the permission
  flags, then we assume that the mapping is private, even though the
  presence of the 's' flag there would mean VM_MAYSHARE, which means
  the mapping could still be private.  This should work OK enough,
  however.

Finally, it is worth mentioning that I added a new command, 'set
use-coredump-filter on/off'.  When it is 'on', it will read the
coredump_filter' file (if it exists) and use its value; otherwise, it
will use the default value mentioned above (0x33) to decide which memory
mappings to dump.

gdb/ChangeLog:
2015-03-31  Sergio Durigan Junior  <sergiodj@redhat.com>
	    Jan Kratochvil  <jan.kratochvil@redhat.com>
	    Oleg Nesterov  <oleg@redhat.com>

	PR corefiles/16092
	* linux-tdep.c: Include 'gdbcmd.h' and 'gdb_regex.h'.
	New enum identifying the various options of the coredump_filter
	file.
	(struct smaps_vmflags): New struct.
	(use_coredump_filter): New variable.
	(decode_vmflags): New function.
	(mapping_is_anonymous_p): Likewise.
	(dump_mapping_p): Likewise.
	(linux_find_memory_regions_full): New variables
	'coredumpfilter_name', 'coredumpfilterdata', 'pid', 'filterflags'.
	Removed variable 'modified'.  Read /proc/<PID>/smaps file; improve
	parsing of its information.  Implement memory mapping filtering
	based on its contents.
	(show_use_coredump_filter): New function.
	(_initialize_linux_tdep): New command 'set use-coredump-filter'.
	* NEWS: Mention the possibility of using the
	'/proc/PID/coredump_filter' file when generating a corefile.
	Mention new command 'set use-coredump-filter'.

gdb/doc/ChangeLog:
2015-03-31  Sergio Durigan Junior  <sergiodj@redhat.com>

	PR corefiles/16092
	* gdb.texinfo (gcore): Mention new command 'set
	use-coredump-filter'.
	(set use-coredump-filter): Document new command.

gdb/testsuite/ChangeLog:
2015-03-31  Sergio Durigan Junior  <sergiodj@redhat.com>

	PR corefiles/16092
	* gdb.base/coredump-filter.c: New file.
	* gdb.base/coredump-filter.exp: Likewise.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Use AM_ENABLE_MULTILIB only if with_target_subdir isn't empty
@ 2015-03-31 22:54 sergiodj+buildbot
  2015-04-01 12:09 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-31 22:54 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f85997a697553fb7053de89bafe36e3d71c6f784 ***

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

Use AM_ENABLE_MULTILIB only if with_target_subdir isn't empty
	* configure.ac (AM_ENABLE_MULTILIB): Use only if
	${with_target_subdir} isn't empty.
	* configure: Regenerated.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Add support for Nuxi CloudABI on x86-64
@ 2015-03-31 19:58 sergiodj+buildbot
  2015-04-01  9:06 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-31 19:58 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6036f4862103dea22dcc1ee02cf31802872997b3 ***

Author: Ed Schouten <ed@nuxi.nl>
Branch: master
Commit: 6036f4862103dea22dcc1ee02cf31802872997b3

Add support for Nuxi CloudABI on x86-64
bfd/

	* config.bfd (targ_defvec): Set to x86_64_elf64_cloudabi_vec
	for x86_64-*-cloudabi*.
	* configure.ac: Handle x86_64_elf64_cloudabi_vec.
	* configure: Regenerated.
	* elf64-x86-64.c (TARGET_LITTLE_SYM): Support x86_64-*-cloudabi*.
	(TARGET_LITTLE_NAME): Likewise.
	(ELF_OSABI): Likewise.
	(elf64_bed): Likewise.
	* targets.c (x86_64_elf64_cloudabi_vec): New.
	(_bfd_target_vector): Add x86_64_elf64_cloudabi_vec.

gas/

	* configure.tgt (fmt): Set to elf for *-*-cloudabi*.

ld/

	* Makefile.am (ALL_64_EMULATION_SOURCES): Add
	eelf_x86_64_cloudabi.c.
	(eelf_x86_64_cloudabi.c): New.
	* configure.tgt (targ_emul): Set to elf_x86_64_cloudabi for
	x86_64-*-cloudabi*.
	* Makefile.in: Regenerated.
	* emulparams/elf_x86_64_cloudabi.sh: New file.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Add cpu information to the info os command on linux.
@ 2015-03-31 16:26 sergiodj+buildbot
  2015-03-31 23:50 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-31 16:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d33279b3bb1c89550b26e7b07e3610ab7f87e211 ***

Author: Antoine Tremblay <antoine.tremblay@ericsson.com>
Branch: master
Commit: d33279b3bb1c89550b26e7b07e3610ab7f87e211

Add cpu information to the info os command on linux.
This patch adds cpu information on linux based on /proc/cpuinfo as :
cpus       Listing of all cpus/cores on the system

This patch also reorders the info os commands so that they are listed
in alphabetical order.

gdb/ChangeLog:

	* NEWS: Mention info os cpus support.
	* gdb/nat/linux-osdata.c (linux_xfer_osdata_cpus): New function.
	(struct osdata_type): Add cpus entry, reorder the entries in
	alphabetical order.

gdb/doc/ChangeLog:

	* gdb.texinfo (Operating System Auxiliary Information): Add info os cpus
	documentation, reorder the info os entries in alphabetical order.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] sim: m68hc11: fix gcc-5 build error w/restrict keyword
@ 2015-03-31  8:20 sergiodj+buildbot
  2015-03-31 18:53 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-31  8:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2b6ca06237301286016acc4b7bbf5338a27fd5fc ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 2b6ca06237301286016acc4b7bbf5338a27fd5fc

sim: m68hc11: fix gcc-5 build error w/restrict keyword


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Update config.guess and config.sub to the latest upstream version
@ 2015-03-31  3:54 sergiodj+buildbot
  2015-03-31 16:01 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-31  3:54 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5675acd9d4a62c4d402da7a436d810b29832d0e0 ***

Author: Ed Schouten <ed@nuxi.nl>
Branch: master
Commit: 5675acd9d4a62c4d402da7a436d810b29832d0e0

Update config.guess and config.sub to the latest upstream version
This version adds support for a platform I'd like to add support for,
namely CloudABI.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] sim: arm: convert to nrun
@ 2015-03-30 22:00 sergiodj+buildbot
  2015-03-31 14:40 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-30 22:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 49d62f892578dab739391b7309bc60ea2baeafc4 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 49d62f892578dab739391b7309bc60ea2baeafc4

sim: arm: convert to nrun
A lot of cpu state is stored in global variables, as is memory handling.
The sim_size support needs unwinding at some point.  But at least this
is an improvement on the status quo.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] sim: arm: delete NEED_UI_LOOP_HOOK handling
@ 2015-03-30 20:01 sergiodj+buildbot
  2015-03-31 14:29 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-30 20:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT dbf8e8afcdf6bbec4ecaf911481b7fc9a4a01e87 ***

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

sim: arm: delete NEED_UI_LOOP_HOOK handling


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] sim: arm: use common configure options
@ 2015-03-30 19:16 sergiodj+buildbot
  2015-03-31 14:18 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-30 19:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c4c9c44f57763ef4acacb440cdf601f5ce087edb ***

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

sim: arm: use common configure options
In preparation for converting to nrun, call the common functions that
are needed.  This doesn't produce any new warnings, and the generated
code should be the same.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] sim: d10v: convert to nrun
@ 2015-03-30 14:54 sergiodj+buildbot
  2015-03-31  1:23 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-30 14:54 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 541ebcee679ccda568b49af01b1da74387623386 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 541ebcee679ccda568b49af01b1da74387623386

sim: d10v: convert to nrun
A lot of cpu state is stored in global variables, as is memory handling.
The sim_size support needs unwinding at some point.  But at least this
is an improvement on the status quo.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] sim: d10v: clean up misc warnings
@ 2015-03-30 10:55 sergiodj+buildbot
  2015-03-30 23:54 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-30 10:55 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 11558abc20f902a1fa3ea128809862787f642598 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 11558abc20f902a1fa3ea128809862787f642598

sim: d10v: clean up misc warnings


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] sim: d10v: link in missing testsuite
@ 2015-03-30 10:29 sergiodj+buildbot
  2015-03-30 19:10 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-30 10:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e8713c0f026199c327ba88ea6da4bcffebff6991 ***

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

sim: d10v: link in missing testsuite
Looks like historical restructuring in this dir lost the d10v-elf subdir
and no one noticed in the meantime.  Re-add it to the testsuite.

There are some failures, but better some tests get run than none at all.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] sim: d10v: use common configure options
@ 2015-03-30  9:55 sergiodj+buildbot
  2015-03-30 21:33 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-30  9:55 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ef9535c6bc7c5d50d03e9f98498e018ac56e366c ***

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

sim: d10v: use common configure options
In preparation for converting to nrun, call the common functions that
are needed.  This doesn't produce any new warnings, and the generated
code should be the same.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] sim: cr16: delete NEED_UI_LOOP_HOOK handling
@ 2015-03-30  8:19 sergiodj+buildbot
  2015-03-30 17:27 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-30  8:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4b0cc5edf489335509e155b5af0a0e754f4e3df9 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 4b0cc5edf489335509e155b5af0a0e754f4e3df9

sim: cr16: delete NEED_UI_LOOP_HOOK handling
This hook is used only when linked into gdb, and cr16 doesn't have a gdb
port anymore.  Punt it.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] sim: cr16: use common configure options
@ 2015-03-30  6:48 sergiodj+buildbot
  2015-03-30 13:18 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-30  6:48 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ca968da465a0d1fd153b158b7aa69730709f43db ***

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

sim: cr16: use common configure options
In preparation for converting to nrun, call the common functions that
are needed.  This doesn't produce any new warnings, and the generated
code should be the same.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] sim: microblaze: convert to nrun
@ 2015-03-30  3:46 sergiodj+buildbot
  2015-03-30 11:00 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-30  3:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2b4bc832a7668438827f5cdca9bf22adab85a915 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 2b4bc832a7668438827f5cdca9bf22adab85a915

sim: microblaze: convert to nrun
This port already was storing its cpu state in the sim_cpu structure, so
converting it over was pretty easy.  It is allocating memory itself still,
but we'll fix that up in the future at some point.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] sim: microblaze: start a testsuite
@ 2015-03-30  1:19 sergiodj+buildbot
  2015-03-30  7:28 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-30  1:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 191ec03314b005b8189ecea7296f2f6cad534d09 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 191ec03314b005b8189ecea7296f2f6cad534d09

sim: microblaze: start a testsuite
Since the sim doesn't have any debug support in it, we can only exit
cleanly.  But this is still better than nothing.

Change the default microblaze sim to not dump the debug load output
when running.  No other does this, and it breaks the testsuite.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] sim; testsuite: allow tests to set no output
@ 2015-03-29 22:47 sergiodj+buildbot
  2015-03-30  5:58 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-29 22:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 744b9a190b9b5b83d83f43d35b6ab6d20f49af8f ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 744b9a190b9b5b83d83f43d35b6ab6d20f49af8f

sim; testsuite: allow tests to set no output
If a test doesn't write anything at all to stdout, the current test
framework can't support that.  Even if you put a blank output line:
	# output:
the setup happily clobbers that with a default pass/fail string.

Tweak the parsing logic so we only set the output to pass/fail when
the test has no output marker.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] sim: testsuite: make subdir unconditional
@ 2015-03-29 19:00 sergiodj+buildbot
  2015-03-30  1:04 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-29 19:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6dae8a88bf814b8729ad883c92c7b75fdccc7be1 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 6dae8a88bf814b8729ad883c92c7b75fdccc7be1

sim: testsuite: make subdir unconditional
Since the testsuite subdir has to handle dynamic arch values already,
there's no real value in requiring arches to opt in to it.  Most have
a testsuite now anyways, and we're requiring it in the future.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] sim: microblaze: use common configure options
@ 2015-03-29 18:05 sergiodj+buildbot
  2015-03-29 22:41 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-29 18:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3c0ae3096245fcb94021f0ed61278aa89191ee59 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 3c0ae3096245fcb94021f0ed61278aa89191ee59

sim: microblaze: use common configure options
In preparation for converting to nrun, call the common functions that
are needed.  This doesn't produce any new warnings, and the generated
code should be the same.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] sim: mcore: convert to nrun
@ 2015-03-29 12:02 sergiodj+buildbot
  2015-03-29 21:21 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-29 12:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ea6b7543b422836409fe7848abbfcb452ad26398 ***

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

sim: mcore: convert to nrun
A lot of cpu state is stored in global variables, as is memory handling.
The sim_size support needs unwinding at some point.  But at least this
is an improvement on the status quo.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] sim: mcore: drop sbrk support
@ 2015-03-29 10:43 sergiodj+buildbot
  2015-03-29 16:34 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-29 10:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT aac18a6996e57cd1d1c32d3fd418c4950c5001bf ***

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

sim: mcore: drop sbrk support
The sbrk syscall assumes the sbrk region starts after the bss and the
current implementation requires a bss section to exist.  Since there
is no requirement for programs to have a bss in general, we want to
drop this check.  However, there is still the sbrk syscall that wants
to know about the region.

Since libgloss doesn't actually use the sbrk syscall (it implements
sbrk in its own way), and the sim really shouldn't enforce a specific
memory layout on programs, lets simply delete sbrk support.  Now it
always returns an error.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] sim: sh: convert to nrun
@ 2015-03-29  5:12 sergiodj+buildbot
  2015-03-29 15:58 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-29  5:12 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 62454d3da2aaabb266e49a4ba22948484e91edc1 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 62454d3da2aaabb266e49a4ba22948484e91edc1

sim: sh: convert to nrun
A lot of cpu state is stored in global variables, as is memory handling.
The sim_size support needs unwinding at some point.  But at least this
is an improvement on the status quo.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] sim: sh: clean up gencode
@ 2015-03-29  0:03 sergiodj+buildbot
  2015-03-29 11:58 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-29  0:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ed4d32c28adc5f00ee9bc0e4ac785eeff5e1dc74 ***

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

sim: sh: clean up gencode
The build line was missing the normal BUILD_xxx flags.  Once we added
that, we get warnings that weren't shown before.  As we fix those, we
notice that the -d option segfaults because it tries to write readonly
memory.  Fix that too as part of the const/prototype clean up.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] A zlib to tarball
@ 2015-03-28 18:34 sergiodj+buildbot
  2015-03-29  9:13 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-28 18:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 92c695a14f6a5a24b177e89624c13d7dbcbf9e1f ***

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

A zlib to tarball
	* src-release.sh (do_proto_toplev): Configure with --target
	--with-target-subdir and --disable-multilib.
	(BINUTILS_SUPPORT_DIRS): Add zlib.
	(GAS_SUPPORT_DIRS): Likewise.
	(GDB_SUPPORT_DIRS): Likewise.
	(SIM_SUPPORT_DIRS): Likewise.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] sim: avr: start a basic testsuite
@ 2015-03-28 10:38 sergiodj+buildbot
  2015-03-29  8:43 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-28 10:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT eca5fe422e2650fcb6a551af11bcf8de181f97e9 ***

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

sim: avr: start a basic testsuite
Just enough to know the sim isn't totally broken.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] sim: erc32: strip paren from return statements
@ 2015-03-28  9:01 sergiodj+buildbot
  2015-03-29  6:07 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-28  9:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5831e29bc1a17115b96141bf72fbc44200c6e014 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 5831e29bc1a17115b96141bf72fbc44200c6e014

sim: erc32: strip paren from return statements


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Fix gdb_bfd_section_index for special sections
@ 2015-03-27 13:20 sergiodj+buildbot
  2015-03-28 23:05 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-27 13:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ce9c0ca18fe50e1e5a87b135032e4aeba415e2ab ***

Author: Andrzej Kaczmarek <andrzej.kaczmarek@tieto.com>
Branch: master
Commit: ce9c0ca18fe50e1e5a87b135032e4aeba415e2ab

Fix gdb_bfd_section_index for special sections
Indexes returned for special sections are off by one, i.e. with N+4
sections last one has index N+4 returned which is outside allocated
obstack (at the same time index N is not used at all).

In worst case, if sections obstack is allocated up to end of chunk,
writing last section data will cause buffer overrun and some data
corruption.

Here's output from Valgrind::

==14630== Invalid write of size 8
==14630==    at 0x551B1A: add_to_objfile_sections_full (objfiles.c:225)
==14630==    by 0x552768: allocate_objfile (objfiles.c:324)
==14630==    by 0x4E8E2E: symbol_file_add_with_addrs (symfile.c:1171)
==14630==    by 0x4E9453: symbol_file_add_from_bfd (symfile.c:1280)
==14630==    by 0x4E9453: symbol_file_add (symfile.c:1295)
==14630==    by 0x4E94B7: symbol_file_add_main_1 (symfile.c:1320)
==14630==    by 0x514246: catch_command_errors_const (main.c:398)
==14630==    by 0x5150AA: captured_main (main.c:1061)
==14630==    by 0x51123C: catch_errors (exceptions.c:240)
==14630==    by 0x51569A: gdb_main (main.c:1164)
==14630==    by 0x408824: main (gdb.c:32)
==14630==  Address 0x635f3b8 is 8 bytes after a block of size 4,064 alloc'd
==14630==    at 0x4C2ABA0: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==14630==    by 0x60F797: xmalloc (common-utils.c:41)
==14630==    by 0x5E787FB: _obstack_begin (obstack.c:184)
==14630==    by 0x552679: allocate_objfile (objfiles.c:294)
==14630==    by 0x4E8E2E: symbol_file_add_with_addrs (symfile.c:1171)
==14630==    by 0x4E9453: symbol_file_add_from_bfd (symfile.c:1280)
==14630==    by 0x4E9453: symbol_file_add (symfile.c:1295)
==14630==    by 0x4E94B7: symbol_file_add_main_1 (symfile.c:1320)
==14630==    by 0x514246: catch_command_errors_const (main.c:398)
==14630==    by 0x5150AA: captured_main (main.c:1061)
==14630==    by 0x51123C: catch_errors (exceptions.c:240)
==14630==    by 0x51569A: gdb_main (main.c:1164)
==14630==    by 0x408824: main (gdb.c:32)

gdb/ChangeLog:
	* gdb_bfd.c (gdb_bfd_section_index): Fix off-by-one for special
	sections.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Relax PR 15228 protected visibility restriction
@ 2015-03-27  6:53 sergiodj+buildbot
  2015-03-28 22:40 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-27  6:53 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b84171287ffe60dd1e7c02262a0493862fa21a97 ***

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

Relax PR 15228 protected visibility restriction
Allows .dynbss copy of shared library protected visibility variables
if they are read-only.

To recap: Copying a variable from a shared library into an executable's
.dynbss is an old hack invented for non-PIC executables, to avoid the
text relocations you'd otherwise need to access a shared library
variable.  This works with ELF shared libraries because global
symbols can be overridden.  The trouble is that protected visibility
symbols can't be overridden.  A shared library will continue to access
it's own protected visibility variable while the executable accesses a
copy.  If either the shared library or the executable updates the
value then the copy diverges from the original.  This is wrong since
there is only one definition of the variable in the application.

So I made the linker report an error on attempting to copy protected
visibility variables into .dynbss.  However, you'll notice the above
paragraph contains an "If".  An application that does not modify the
variable value remains correct even though two copies of the variable
exist.  The linker can detect this situation if the variable was
defined in a read-only section.

	PR ld/15228
	PR ld/18167
	* elflink.c (elf_merge_st_other): Add "sec" parameter.  Don't set
	protected_def when symbol section is read-only.  Adjust all calls.
	* elf-bfd.h (struct elf_link_hash_entry): Update protected_def comment.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] testsuite: Don't set SYMBOL_PREFIX for x86_64_*_cygwin
@ 2015-03-26 23:51 sergiodj+buildbot
  2015-03-28 22:17 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-26 23:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7ec911b0fb0b27d66604c3f7951c146d94f4acc7 ***

Author: Jon Turney <jon.turney@dronecode.org.uk>
Branch: master
Commit: 7ec911b0fb0b27d66604c3f7951c146d94f4acc7

testsuite: Don't set SYMBOL_PREFIX for x86_64_*_cygwin
Exactly like x86_64-*-mingw, SYMBOL_PREFIX should not be set to "_" for
x86_64_*_cygwin

gdb/testuite/ChangeLog:

	* lib/gdb.exp (gdb_target_symbol_prefix_flags): Don't set
	SYMBOL_PREFIX for x86_64-*-cygwin.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] dtrace-probe: Handle error while parsing probe argument.
@ 2015-03-26 22:17 sergiodj+buildbot
  2015-03-28 21:24 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-26 22:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 429e1e811b400f07b5a514ea6b8a70b28e2d7ee9 ***

Author: Joel Brobecker <brobecker@adacore.com>
Branch: master
Commit: 429e1e811b400f07b5a514ea6b8a70b28e2d7ee9

dtrace-probe: Handle error while parsing probe argument.
The debugger on Solaris has been broken since the introduction of
DTrace probe support:

    (gdb) start
    Temporary breakpoint 1 at 0x80593bc: file simple_main.adb, line 4.
    Starting program: /[...]/simple_main
    [Thread debugging using libthread_db enabled]
    No definition of "mutex_t" in current context.

The problem occurs while trying to parse a probe's argument,
and the exception propagates all the way to the top. This patch
fixes the issue by containing the exception and falling back on
using the "long" builtin type if the argument's type could not
be determined.

Also, the parsing should be done using the C language parser.

gdb/ChangeLog:

        * dtrace-probe.c (dtrace_process_dof_probe): Contain any
        exception raised while parsing the probe arguments.
        Force parsing to be done using the C language parser.
        * expression.h (parse_expression_with_language): Declare.
        * parse.c (parse_expression_with_language): New function.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Add myself as a write-after-approval GDB maintainer
@ 2015-03-26 21:46 sergiodj+buildbot
  2015-03-28 20:59 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-26 21:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4593441bc5bcb7ec2e04b28591707cdebedd2e85 ***

Author: Jon Turney <jon.turney@dronecode.org.uk>
Branch: master
Commit: 4593441bc5bcb7ec2e04b28591707cdebedd2e85

Add myself as a write-after-approval GDB maintainer
gdb/ChangeLog:

	* MAINTAINERS (Write After Approval): Add "Jon Turney".


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Code cleanup: Make validate_format parameter const
@ 2015-03-26 18:51 sergiodj+buildbot
  2015-03-28 20:23 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-26 18:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8d89f51a70a9a3cf74562324fc0391e4872a93b1 ***

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

Code cleanup: Make validate_format parameter const
gdb/ChangeLog
2015-03-26  Jan Kratochvil  <jan.kratochvil@redhat.com>

	Code cleanup.
	* printcmd.c (validate_format): Make the parameter cmdname const.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Remove some hard-coded stuff in tests
@ 2015-03-26  9:30 sergiodj+buildbot
  2015-03-28 11:48 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-26  9:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2898689ba3a36451779ec526e14783c2aba9316b ***

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

Remove some hard-coded stuff in tests
There are some hard-coded stuff in .s files, such as .int 0 and
address offset, which isn't portable.  This patch is to replace
".int 0" with nop and address offset with labels.

gdb/testsuite:

2015-03-26  Yao Qi  <yao.qi@linaro.org>

	* gdb.linespec/break-asm-file0.s (func2): Use nop instead of
	.int 0.
	(func): Likewise.  Add .Lfunc_1 label.
	Use .Lfunc_1 label.
	* gdb.linespec/break-asm-file1.s (func3): Use nop instead of
	.int 0.
	(func): Likewise.
	Use .Lfunc_1 label.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Compile break-asm-file{0,1}.s without debug info
@ 2015-03-26  9:08 sergiodj+buildbot
  2015-03-28  9:37 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-26  9:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8518049884947da598e2f585bf9a4589df7096e9 ***

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

Compile break-asm-file{0,1}.s without debug info
If I add some nop into break-asm-file1.s like this,

--- INDEX:/gdb/testsuite/gdb.linespec/break-asm-file1.s
+++ WORKDIR:/gdb/testsuite/gdb.linespec/break-asm-file1.s
@@ -31,8 +31,8 @@ _func:
 	.type func, %function
 func:
 .Lbegin_func:
-	.int 0
-	.int 0
+	nop
+	nop
 .Lend_func:
 	.size func, .-func
 .Lend_text1:

I get the following error:

Running gdb/testsuite/gdb.linespec/break-asm-file.exp ...
gdb/testsuite/gdb.linespec/break-asm-file1.s: Assembler messages:^M
gdb/testsuite/gdb.linespec/break-asm-file1.s: Fatal error: duplicate .debug_line sections

break-asm-file0.s and break-asm-file1.s have already had debug information
(written manually), so don't need to generate debug infor for them.

gdb/testsuite:

2015-03-26  Yao Qi  <yao.qi@linaro.org>

	* gdb.linespec/break-asm-file.exp: Don't call prepare_for_testing.
	Call gdb_compile instead to compile each .s files without debug
	information.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] powerpc: Add slbfee. instruction
@ 2015-03-26  4:11 sergiodj+buildbot
  2015-03-28  7:39 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-26  4:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c4e676f196560500d41ff8652d6be0c735758001 ***

Author: Anton Blanchard <anton@samba.org>
Branch: master
Commit: c4e676f196560500d41ff8652d6be0c735758001

powerpc: Add slbfee. instruction
opcodes/ChangeLog:
2015-03-25  Anton Blanchard  <anton@samba.org>

	* ppc-opc.c (powerpc_opcodes): Add slbfee.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [AArch64] Implement branch over stub section.
@ 2015-03-26  3:24 sergiodj+buildbot
  2015-03-28  7:02 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-26  3:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 618655192fca05a9aaebbd395b0960626cbfdebe ***

Author: Marcus Shawcroft <marcus.shawcroft@gmail.com>
Branch: master
Commit: 618655192fca05a9aaebbd395b0960626cbfdebe

[AArch64] Implement branch over stub section.
Ensure that injection of a stub section does not break a link where
there is an xpectation that flow of control can pass from one input
section to another simply by linking the input sections in series.

The solution here is to allow stub sections to be inserted after any
input section (existing behaviour), but inject an additional branch at
the start of each stub section such that control flow falling into the
stub section will branch over the stub section.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [AArch64] Remove padding before stub sections.
@ 2015-03-26  2:05 sergiodj+buildbot
  2015-03-28  6:34 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-26  2:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d9ced15d6ea875aadd3e7395990eb37319454d71 ***

Author: Marcus Shawcroft <marcus.shawcroft@gmail.com>
Branch: master
Commit: d9ced15d6ea875aadd3e7395990eb37319454d71

[AArch64] Remove padding before stub sections.
Lower stub alignment from 8 to 4 bytes thus removing padding between
input section content and stub section content.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [AArch64] Adjust veneer count.
@ 2015-03-25 16:57 sergiodj+buildbot
  2015-03-28  3:58 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-25 16:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 357d1523b2e5b0427fe4133cc90658026a7fac2c ***

Author: Marcus Shawcroft <marcus.shawcroft@arm.com>
Branch: master
Commit: 357d1523b2e5b0427fe4133cc90658026a7fac2c

[AArch64] Adjust veneer count.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Fix mi-pending.exp test output to allow stable test diffing
@ 2015-03-25 16:36 sergiodj+buildbot
  2015-03-26 18:11 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-25 16:36 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ad235a410aebf08ca67589891388774aa1d03562 ***

Author: Antoine Tremblay <antoine.tremblay@ericsson.com>
Branch: master
Commit: ad235a410aebf08ca67589891388774aa1d03562

Fix mi-pending.exp test output to allow stable test diffing
gdb/testsuite/ChangeLog:

	* gdb.mi/mi-pending.exp: Fix output of breakpoint test.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Move low-level Linux x86 debug register code to a shared file
@ 2015-03-25 11:45 sergiodj+buildbot
  2015-03-25 23:03 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-25 11:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8e5d40700492597d103ebdb68eab733456b66fad ***

Author: Gary Benson <gbenson@redhat.com>
Branch: master
Commit: 8e5d40700492597d103ebdb68eab733456b66fad

Move low-level Linux x86 debug register code to a shared file
This commit moves the now-identical low-level Linux x86 debug register
code from gdb/x86-linux-nat.c and gdb/gdbserver/linux-x86-low.c into a
new shared file gdb/nat/x86-linux-dregs.c.

gdb/ChangeLog:

	* nat/x86-linux-dregs.h: New file.
	* nat/x86-linux-dregs.c: Likewise.
	* Makefile.in (HFILES_NO_SRCDIR): Add nat/x86-linux-dregs.h.
	(x86-linux-dregs.o): New rule.
	* config/i386/linux.mh (NATDEPFILES): Add x86-linux-dregs.o.
	* config/i386/linux64.mh (NATDEPFILES): Likewise.
	* x86-linux-nat.c: Include nat/x86-linux-dregs.h.
	(u_debugreg_offset): Moved to nat/x86-linux-dregs.c.
	(x86_linux_dr_get): Likewise.
	(x86_linux_dr_set): Likewise.
	(x86_linux_dr_get_addr): Likewise.
	(x86_linux_dr_get_control): Likewise.
	(x86_linux_dr_get_status): Likewise.
	(update_debug_registers_callback): Likewise.
	(x86_linux_dr_set_control): Likewise.
	(x86_linux_dr_set_addr): Likewise.
	(x86_linux_update_debug_registers): Likewise.

gdb/gdbserver/ChangeLog:

	* Makefile.in (x86-linux-dregs.o): New rule.
	* configure.srv: Add x86-linux-dregs.o to relevant targets.
	* linux-x86-low.c: Include nat/x86-linux-dregs.h.
	(u_debugreg_offset): Moved to nat/x86-linux-dregs.c.
	(x86_linux_dr_get): Likewise.
	(x86_linux_dr_set): Likewise.
	(update_debug_registers_callback): Likewise.
	(x86_linux_dr_set_addr): Likewise.
	(x86_linux_dr_get_addr): Likewise.
	(x86_linux_dr_set_control): Likewise.
	(x86_linux_dr_get_control): Likewise.
	(x86_linux_dr_get_status): Likewise.
	(x86_linux_update_debug_registers): Likewise.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Fix "thread apply all" with exited threads
@ 2015-03-25  4:46 sergiodj+buildbot
  2015-03-27 19:29 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-25  4:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a25d8bf9c5b2c9d3671f4508c9132485c65c3773 ***

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

Fix "thread apply all" with exited threads
I noticed that "thread apply all" sometimes crashes.

The problem is that thread_apply_all_command doesn take exited threads
into account, and we qsort and then walk more elements than there
really ever were put in the array.  Valgrind shows:

 The current thread <Thread ID 3> has terminated.  See `help thread'.
 (gdb) thread apply all p 1

 Thread 1 (Thread 0x7ffff7fc2740 (LWP 29579)):
 $1 = 1
 ==29576== Use of uninitialised value of size 8
 ==29576==    at 0x639CA8: set_thread_refcount (thread.c:1337)
 ==29576==    by 0x5C2C7B: do_my_cleanups (cleanups.c:155)
 ==29576==    by 0x5C2CE8: do_cleanups (cleanups.c:177)
 ==29576==    by 0x63A191: thread_apply_all_command (thread.c:1477)
 ==29576==    by 0x50374D: do_cfunc (cli-decode.c:105)
 ==29576==    by 0x506865: cmd_func (cli-decode.c:1893)
 ==29576==    by 0x7562CB: execute_command (top.c:476)
 ==29576==    by 0x647DA4: command_handler (event-top.c:494)
 ==29576==    by 0x648367: command_line_handler (event-top.c:692)
 ==29576==    by 0x7BF7C9: rl_callback_read_char (callback.c:220)
 ==29576==    by 0x64784C: rl_callback_read_char_wrapper (event-top.c:171)
 ==29576==    by 0x647CB5: stdin_event_handler (event-top.c:432)
 ==29576==
 ...

This can happen easily today as linux-nat.c/linux-thread-db.c are
forgetting to purge non-current exited threads.  But even with that
fixed, we can always do "thread apply all" with an exited thread
selected, which won't be deleted until the user switches to another
thread.  That's what the test added by this commit exercises.

Tested on x86_64 Fedora 20.

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

	* thread.c (thread_apply_all_command): Take exited threads into
	account.

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

	* gdb.threads/no-unwaited-for-left.exp: Test "thread apply all".


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Make linux_stop_lwp be a shared function
@ 2015-03-25  3:24 sergiodj+buildbot
  2015-03-25 15:19 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-25  3:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b2f7c7e8b7046bf3dd99e3fb7329feb962a6bc7d ***

Author: Gary Benson <gbenson@redhat.com>
Branch: master
Commit: b2f7c7e8b7046bf3dd99e3fb7329feb962a6bc7d

Make linux_stop_lwp be a shared function
Both GDB and gdbserver had linux_stop_lwp functions with identical
declarations.  This commit moves these to nat/linux-nat.h to allow
shared code to use the function.

gdb/ChangeLog:

	* linux-nat.h (linux_stop_lwp): Move declaration to...
	* nat/linux-nat.h (linux_stop_lwp): New declaration.

gdb/gdbserver/ChangeLog:

	* linux-low.h (linux_stop_lwp): Remove declaration.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Debug output tweaks in the Linux target backends
@ 2015-03-25  3:22 sergiodj+buildbot
  2015-03-27 12:36 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-25  3:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2bf6fb9d85394f90abb3e21ee037a732b6e4c983 ***

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

Debug output tweaks in the Linux target backends
This adds/tweaks a few debug logs I found useful recently.

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

	* linux-low.c (check_stopped_by_breakpoint): Tweak debug log
	output.  Also dump TRAP_TRACE.
	(linux_low_filter_event): In debug output, distinguish a
	resume_stop SIGSTOP from a delayed SIGSTOP.

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

	* linux-nat.c (linux_nat_resume): Output debug logs before trying
	to resume the event lwp.  Use the lwp's ptid instead of the passed
	in (maybe wildcard) ptid.
	(stop_wait_callback): Tweak debug log output.
	(check_stopped_by_breakpoint): Tweak debug log output.  Also dump
	TRAP_TRACE.
	(linux_nat_filter_event): In debug output, distinguish a
	resume_stop SIGSTOP from a delayed SIGSTOP.  Output debug logs
	before trying to resume the lwp.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Make step_start_function be per thread
@ 2015-03-25  0:47 sergiodj+buildbot
  2015-03-27  1:32 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-25  0:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 885eeb5b8ea021cc79ffebe8ec40122229c572f0 ***

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

Make step_start_function be per thread
I noticed that step_start_function is still a global, while it
obviously should be a per-thread field.

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

	* infrun.c (step_start_function): Delete and ...
	* gdbthread.h (struct thread_control_state) <step_start_function>:
	... now a field here.
	* infrun.c (clear_proceed_status_thread): Clear the thread's
	step_start_function.
	(proceed, process_event_stop_test, print_stop_event): Adjust.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] No longer handle negative 'step' in 'proceed'
@ 2015-03-24 23:58 sergiodj+buildbot
  2015-03-26 23:11 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-24 23:58 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3333f03ae1b02b321717b4bc4887201ed4fc6a26 ***

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

No longer handle negative 'step' in 'proceed'
Nothing ever passes a negative 'step' to proceed.
Gets rid of one of the few remaining stop_after_trap references.

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

	* infrun.c (proceed): No longer handle negative step.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Introduce current_lwp_ptid
@ 2015-03-24 23:49 sergiodj+buildbot
  2015-03-25 11:49 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-24 23:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7b6690874fa3a8afacd731b70a461d55a5b1311c ***

Author: Gary Benson <gbenson@redhat.com>
Branch: master
Commit: 7b6690874fa3a8afacd731b70a461d55a5b1311c

Introduce current_lwp_ptid
This commit introduces a new function, current_lwp_ptid, that
shared Linux code can use to obtain the ptid of the current
lightweight process.

gdb/ChangeLog:

	* nat/linux-nat.h (current_lwp_ptid): New declaration.
	* linux-nat.c (current_lwp_ptid): New function.
	* x86-linux-nat.c: Include nat/linux-nat.h.
	(x86_linux_dr_get_addr): Use current_lwp_ptid.
	(x86_linux_dr_get_control): Likewise.
	(x86_linux_dr_get_status): Likewise.
	(x86_linux_dr_set_control): Likewise.
	(x86_linux_dr_set_addr): Likewise.

gdb/gdbserver/ChangeLog:

	* linux-low.c (current_lwp_ptid): New function.
	* linux-x86-low.c: Include nat/linux-nat.h.
	(x86_dr_low_get_addr): Use current_lwp_ptid.
	(x86_dr_low_get_control): Likewise.
	(x86_dr_low_get_status): Likewise.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Fixes a bug introduced by the new ranges checks on COFF symbol tables.
@ 2015-03-24 23:00 sergiodj+buildbot
  2015-03-26 15:43 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-24 23:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fc42baf3cdc41bc8cf12e35ae78e4529c1470118 ***

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

Fixes a bug introduced by the new ranges checks on COFF symbol tables.
	PR binutils/17512
	* coffgen.c (coff_get_normalized_symtab): Fix test for out of
	range auxillary sections.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [AArch64] Factor out _bfd_aarch64_get_stub_for_link_section.
@ 2015-03-24 22:15 sergiodj+buildbot
  2015-03-26  8:49 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-24 22:15 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fc6d53be1893813f5017681a211dd20d560d8c58 ***

Author: Marcus Shawcroft <marcus.shawcroft@arm.com>
Branch: master
Commit: fc6d53be1893813f5017681a211dd20d560d8c58

[AArch64] Factor out _bfd_aarch64_get_stub_for_link_section.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Make lwp_info.arch_private handling shared
@ 2015-03-24 18:37 sergiodj+buildbot
  2015-03-25 18:54 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-24 18:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4b134ca10812e550d8d012cd6096f5229d59f7c6 ***

Author: Gary Benson <gbenson@redhat.com>
Branch: master
Commit: 4b134ca10812e550d8d012cd6096f5229d59f7c6

Make lwp_info.arch_private handling shared
This commit moves the code to handle lwp_info.arch_private for
Linux x86 into a new shared file, nat/x86-linux.c.

gdb/ChangeLog:

	* nat/x86-linux.h: New file.
	* nat/x86-linux.c: Likewise.
	* Makefile.in (HFILES_NO_SRCDIR): Add nat/x86-linux.h.
	(x86-linux.o): New rule.
	* config/i386/linux.mh (NATDEPFILES): Add x86-linux.o.
	* config/i386/linux64.mh (NATDEPFILES): Likewise.
	* nat/linux-nat.h (struct arch_lwp_info): New forward declaration.
	(lwp_set_arch_private_info): New declaration.
	(lwp_arch_private_info): Likewise.
	* linux-nat.c (lwp_set_arch_private_info): New function.
	(lwp_arch_private_info): Likewise.
	* x86-linux-nat.c: Include nat/x86-linux.h.
	(arch_lwp_info): Removed structure.
	(update_debug_registers_callback):
	Use lwp_set_debug_registers_changed.
	(x86_linux_prepare_to_resume): Use lwp_debug_registers_changed
	and lwp_set_debug_registers_changed.
	(x86_linux_new_thread): Use lwp_set_debug_registers_changed.

gdb/gdbserver/ChangeLog:

	* Makefile.in (x86-linux.o): New rule.
	* configure.srv: Add x86-linux.o to relevant targets.
	* linux-low.c (lwp_set_arch_private_info): New function.
	(lwp_arch_private_info): Likewise.
	* linux-x86-low.c: Include nat/x86-linux.h.
	(arch_lwp_info): Removed structure.
	(update_debug_registers_callback):
	Use lwp_set_debug_registers_changed.
	(x86_linux_prepare_to_resume): Use lwp_debug_registers_changed
	and lwp_set_debug_registers_changed.
	(x86_linux_new_thread): Use lwp_set_debug_registers_changed.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Introduce basic LWP accessors
@ 2015-03-24 17:32 sergiodj+buildbot
  2015-03-25 16:14 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-24 17:32 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cff068da9d13bc9fa8c04f42151b4e92bfff86a1 ***

Author: Gary Benson <gbenson@redhat.com>
Branch: master
Commit: cff068da9d13bc9fa8c04f42151b4e92bfff86a1

Introduce basic LWP accessors
This commit introduces three accessors that shared Linux code can
use to access fields of struct lwp_info.  The GDB and gdbserver
Linux x86 code is modified to use them.

gdb/ChangeLog:

	* nat/linux-nat.h (ptid_of_lwp): New declaration.
	(lwp_is_stopped): Likewise.
	(lwp_stop_reason): Likewise.
	* linux-nat.c (ptid_of_lwp): New function.
	(lwp_is_stopped): Likewise.
	(lwp_is_stopped_by_watchpoint): Likewise.
	* x86-linux-nat.c (update_debug_registers_callback):
	Use lwp_is_stopped.
	(x86_linux_prepare_to_resume): Use ptid_of_lwp and
	lwp_stop_reason.

gdb/gdbserver/ChangeLog:

	* linux-low.c (ptid_of_lwp): New function.
	(lwp_is_stopped): Likewise.
	(lwp_stop_reason): Likewise.
	* linux-x86-low.c (update_debug_registers_callback):
	Use lwp_is_stopped.
	(x86_linux_prepare_to_resume): Use ptid_of_lwp and
	lwp_stop_reason.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Extend arm_feature_set struct to provide more bits
@ 2015-03-24 17:08 sergiodj+buildbot
  2015-03-25  2:01 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-24 17:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 823d25713dd1d6aedc605e3da2007b54da9dff2d ***

Author: Terry Guo <terry.guo@arm.com>
Branch: master
Commit: 823d25713dd1d6aedc605e3da2007b54da9dff2d

Extend arm_feature_set struct to provide more bits
gas/ChangeLog:
2015-03-24  Terry Guo  <terry.guo@arm.com>

	* config/tc-arm.c (no_cpu_selected): Use new macro to compare
	features.
	(parse_psr): Likewise.
	(do_t_mrs): Likewise.
	(do_t_msr): Likewise.
	(static const arm_feature_set arm_ext_*): Defined with new
	macros.
	(static const arm_feature_set arm_cext_*): Likewise.
	(static const arm_feature_set fpu_fpa_ext_*): Likewise.
	(static const arm_feature_set fpu_vfp_ext_*): Likewise.
	(deprecated_coproc_regs): Likewise.
	(UL_BARRIER): Likewise.
	(barrier_opt_names): Likewise.
	(arm_cpus): Likewise.
	(arm_extensions): Likewise.

include/opcode/ChangeLog:
2015-03-24  Terry Guo  <terry.guo@arm.com>

	* arm.h (arm_feature_set): Extended to provide more available
	* bits.
	(ARM_ANY): Updated to follow above new definition.
	(ARM_CPU_HAS_FEATURE): Likewise.
	(ARM_CPU_IS_ANY): Likewise.
	(ARM_MERGE_FEATURE_SETS): Likewise.
	(ARM_CLEAR_FEATURE): Likewise.
	(ARM_FEATURE): Likewise.
	(ARM_FEATURE_COPY): New macro.
	(ARM_FEATURE_EQUAL): Likewise.
	(ARM_FEATURE_ZERO): Likewise.
	(ARM_FEATURE_CORE_EQUAL): Likewise.
	(ARM_FEATURE_LOW): Likewise.
	(ARM_FEATURE_CORE_LOW): Likewise.
	(ARM_FEATURE_CORE_COPROC): Likewise.

opcodes/ChangeLog:
2015-03-24  Terry Guo  <terry.guo@arm.com>

	* arm-dis.c (opcode32): Updated to use new arm feature struct.
	(opcode16): Likewise.
	(coprocessor_opcodes): Replace bit with feature struct.
	(neon_opcodes): Likewise.
	(arm_opcodes): Likewise.
	(thumb_opcodes): Likewise.
	(thumb32_opcodes): Likewise.
	(print_insn_coprocessor): Likewise.
	(print_insn_arm): Likewise.
	(select_arm_features): Follow new feature struct.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Add iterate_over_lwps to gdbserver
@ 2015-03-24 16:34 sergiodj+buildbot
  2015-03-25 13:50 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-24 16:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6d4ee8c6ad7d5b04e524b2b48ffe5639028594a5 ***

Author: Gary Benson <gbenson@redhat.com>
Branch: master
Commit: 6d4ee8c6ad7d5b04e524b2b48ffe5639028594a5

Add iterate_over_lwps to gdbserver
This commit introduces a new function, iterate_over_lwps, that
shared Linux code can use to call a function for each LWP that
matches certain criteria.  This function already existed in GDB
and was in use by GDB's various low-level Linux x86 debug register
setters.  An equivalent was written for gdbserver and gdbserver's
low-level Linux x86 debug register setters were modified to use
it.

gdb/ChangeLog:

	* linux-nat.h: Include nat/linux-nat.h.
	(iterate_over_lwps): Move declaration to nat/linux-nat.h.
	* nat/linux-nat.h (struct lwp_info): New forward declaration.
	(iterate_over_lwps_ftype): New typedef.
	(iterate_over_lwps): New declaration.
	* linux-nat.h (iterate_over_lwps): Update comment.  Use
	iterate_over_lwps_ftype.  Update callback return value check.

gdb/gdbserver/ChangeLog:

	* linux-low.h: Include nat/linux-nat.h.
	* linux-low.c (iterate_over_lwps_args): New structure.
	(iterate_over_lwps_filter): New function.
	(iterate_over_lwps): Likewise.
	* linux-x86-low.c (update_debug_registers_callback):
	Update signature to what iterate_over_lwps expects.
	Remove PID check that iterate_over_lwps now performs.
	(x86_dr_low_set_addr): Use iterate_over_lwps.
	(x86_dr_low_set_control): Likewise.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [AArch64] Refactor generation of 835769 workaround stubs.
@ 2015-03-24 14:50 sergiodj+buildbot
  2015-03-25  9:54 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-24 14:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5421cc6e55c7b3fba445c6085a05efb2a6f58505 ***

Author: Marcus Shawcroft <marcus.shawcroft@gmail.com>
Branch: master
Commit: 5421cc6e55c7b3fba445c6085a05efb2a6f58505

[AArch64] Refactor generation of 835769 workaround stubs.
This patch recognizes that we only need to perform one scan for the
835769 errata and that this scan can take place before we insert
branch stubs.  The erratum scan code is relocated and adjusted to
create stub entries directly rather than populating an intermediate
representation.  Since stub entries are created immediately we can
drop the adhoc stub size adjustment code and allow the generic stub
sizing code to deal with 835769 stub entries.

This patch restructures the code but does not change the workaround
used to deal with erratum 83679, the exact placement of workaround
stubs in the final image may change slightly after this patch due to
stubs being created in a different order.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [AArch64] Use _bfd_aarch64_add_stub_entry_in_group.
@ 2015-03-24 14:15 sergiodj+buildbot
  2015-03-25  8:10 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-24 14:15 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e572930b96d8080ec80e65cfe85aaa8c4f7b2603 ***

Author: Marcus Shawcroft <marcus.shawcroft@arm.com>
Branch: master
Commit: e572930b96d8080ec80e65cfe85aaa8c4f7b2603

[AArch64] Use _bfd_aarch64_add_stub_entry_in_group.
Adjust the 835769 workaround code to use
_bfd_aarch64_add_stub_entry_in_group rather than inspect the
underlying section_group structure directly.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] sim: erc32/h8300/m68hc11: trim unused functions
@ 2015-03-24 12:39 sergiodj+buildbot
  2015-03-24 21:28 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-24 12:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 523ba8f92e3ff4c49f65b582c89b4563b1b665ad ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 523ba8f92e3ff4c49f65b582c89b4563b1b665ad

sim: erc32/h8300/m68hc11: trim unused functions
These funcs are only used with the old run.o, and these sims use nrun.o,
so drop these stub funcs.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] sim: m32r: drop duplicate dv_sockser_install call
@ 2015-03-24 12:19 sergiodj+buildbot
  2015-03-24 18:52 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-24 12:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fe83b8a8d369e28dcfab42ee9f4b6d9cef3370c0 ***

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

sim: m32r: drop duplicate dv_sockser_install call
Since sim_module_install takes care of this for us, there's no need
to initialize the module twice.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] sim: drop support for requiring hw support
@ 2015-03-24  5:21 sergiodj+buildbot
  2015-03-24 15:25 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-24  5:21 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 64dd13dfc267b1d13f42519f220e89a4386591fd ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 64dd13dfc267b1d13f42519f220e89a4386591fd

sim: drop support for requiring hw support
Since no sim is using the "always" option to SIM_AC_OPTION_HARDWARE, and
we don't want to require hw support to always be enabled, drop the option.
This leads to a slight simplification in the macro too as we can collapse
the sim_hw_p variable.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] GDB: Add set/show serial parity command.
@ 2015-03-24  4:11 sergiodj+buildbot
  2015-03-24  8:29 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-24  4:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 236af5e336970a6b58cd17e0a2981bd96f3d09a0 ***

Author: Yury Grechishchev <yury.grechishchev@yotadevices.com>
Branch: master
Commit: 236af5e336970a6b58cd17e0a2981bd96f3d09a0

GDB: Add set/show serial parity command.
The "set serial parity" command allows the user to control which
parity to use when communicating over a serial connection, rather
than having the parity hardcoded to none.

gdb/ChangeLog:

        * NEWS: Mention set/show serial parity command.
        * monitor.c (monitor_open): Call serial_setparity.
        * remote.c (remote_open_1): Likewise.
        * ser-base.c (ser_base_serparity): New function.
        * ser-base.h (ser_base_setparity): Add  declaration.
        * ser-go32.c (dos_ops): Set "setparity" field.
        * ser-mingw.c (ser_windows_raw): Do not set state.fParity and
        state.Parity.
        (ser_windows_setparity): New function.
        (hardwire_ops): Add ser_windows_setparity.
        (tty_ops): Add NULL for setparity field.
        (pipe_ops): Add ser_base_setparity.
        (tcp_ops): Likewise.
        * ser-pipe.c (pipe_ops): Likewise.
        * ser-tcp.c (tcp_ops): Likewise.
        * ser-unix.c (hardwire_setparity): Add declaration.
        (hardwire_raw): Don't reset PARENB flag.
        (hardwire_setparity): New function.
        (hardwire_ops): Add hardwire_setparity.
        * serial.c (serial_setparity): New function.
        (serial_parity): New global.
        (parity_none, parity_odd, parity_even, parity_enums, parity):
        New static globals.
        (set_parity): New function.
        (_initialize_serial): Add set/show serial parity commands.
        * serial.h (GDBPARITY_NONE): Define.
        (GDBPARITY_ODD): Define.
        (GDBPARITY_EVEN): Define.
        (serial_setparity) Add declaration.
        (struct serial_ops): Add setparity field.
        * target.h (serial_parity): Add declaration.

gdb/doc/ChangeLog:

        * gdb.texinfo (Remote configuration): Document "set/show
        serial parity" command.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Update comment of linespec_lexer_lex_keyword.
@ 2015-03-23 22:22 sergiodj+buildbot
  2015-03-24  7:16 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-23 22:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 32b40af94e919e235c21486110311647cbeecf2e ***

Author: Keith Seitz <keiths@redhat.com>
Branch: master
Commit: 32b40af94e919e235c21486110311647cbeecf2e

Update comment of linespec_lexer_lex_keyword.
gdb/ChangeLog

       * linespec.c (linespec_lexer_lex_keyword): Update comment.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [AArch64] Drop unused argument to elf_aarch64_create_or_find_stub_sec
@ 2015-03-23 21:05 sergiodj+buildbot
  2015-03-23 21:21 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-23 21:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4c77202d000bab10f821a88c6da9664337f01f10 ***

Author: Marcus Shawcroft <marcus.shawcroft@arm.com>
Branch: master
Commit: 4c77202d000bab10f821a88c6da9664337f01f10

[AArch64] Drop unused argument to elf_aarch64_create_or_find_stub_sec


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [OBV] Fix build -- missing ';'
@ 2015-03-23 20:51 sergiodj+buildbot
  2015-03-24  1:17 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-23 20:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c53ed7cf577806c9d7d658dec5b70b2de00ec825 ***

Author: Keith Seitz <keiths@redhat.com>
Branch: master
Commit: c53ed7cf577806c9d7d658dec5b70b2de00ec825

[OBV] Fix build -- missing ';'
bfd/ChangeLog

	* elfnn-aarch64.c (_bfd_aarch64_create_or_find_stub_sec): Add
	missing ';'.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [AArch64] Factor out _bfd_aarch64_resize_stubs()
@ 2015-03-23 19:16 sergiodj+buildbot
  2015-03-23 23:38 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-23 19:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 13f622ec5967f0a56d5876e7c7305c260cb4928f ***

Author: Marcus Shawcroft <marcus.shawcroft@gmail.com>
Branch: master
Commit: 13f622ec5967f0a56d5876e7c7305c260cb4928f

[AArch64] Factor out _bfd_aarch64_resize_stubs()


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [AArch64] Factor stub creation code into _bfd_aarch64_create_stub_section.
@ 2015-03-23 19:09 sergiodj+buildbot
  2015-03-23 23:14 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-23 19:09 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 665856756517ff4eb0c31c07f5c7e1666ccd4445 ***

Author: Marcus Shawcroft <marcus.shawcroft@arm.com>
Branch: master
Commit: 665856756517ff4eb0c31c07f5c7e1666ccd4445

[AArch64] Factor stub creation code into _bfd_aarch64_create_stub_section.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [AArch64] Remove unused variable.
@ 2015-03-23 17:58 sergiodj+buildbot
  2015-03-23 20:49 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-23 17:58 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9b9971aac7b89596695f15ed4763d9fd2b876ca8 ***

Author: Marcus Shawcroft <marcus.shawcroft@gmail.com>
Branch: master
Commit: 9b9971aac7b89596695f15ed4763d9fd2b876ca8

[AArch64] Remove unused variable.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [AArch64] Tidy up in aarch64_mem_op_p().
@ 2015-03-23 16:27 sergiodj+buildbot
  2015-03-23 18:14 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-23 16:27 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3d14faea41888606f41466655aa1f0c6f0acf7e0 ***

Author: Marcus Shawcroft <marcus.shawcroft@arm.com>
Branch: master
Commit: 3d14faea41888606f41466655aa1f0c6f0acf7e0

[AArch64] Tidy up in aarch64_mem_op_p().


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [AArch64] Adjust layout of elfNN_aarch64_write_section.
@ 2015-03-23 16:02 sergiodj+buildbot
  2015-03-23 16:42 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-23 16:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f872121a87fe4c16ec43623b75804b39612e62ef ***

Author: Marcus Shawcroft <marcus.shawcroft@arm.com>
Branch: master
Commit: f872121a87fe4c16ec43623b75804b39612e62ef

[AArch64] Adjust layout of elfNN_aarch64_write_section.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] sim: bfin/msp430: drop run-sim.h include
@ 2015-03-23  9:49 sergiodj+buildbot
  2015-03-23 11:04 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-23  9:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 80fc77e6c14835462fca0b7adc15655ce2e4bb99 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 80fc77e6c14835462fca0b7adc15655ce2e4bb99

sim: bfin/msp430: drop run-sim.h include
This header is used only with run.o, and both of these use nrun.o.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] sim: sh64: delete dv-sockser references
@ 2015-03-23  8:38 sergiodj+buildbot
  2015-03-23 10:00 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-23  8:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8a863336bb768e5e26781e904a029eb1f65ed4ec ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 8a863336bb768e5e26781e904a029eb1f65ed4ec

sim: sh64: delete dv-sockser references
This sim doesn't actually use dv-sockser code anywhere, so drop references
to it in its build files.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] constify set_breakpoint_condition
@ 2015-03-21  3:23 sergiodj+buildbot
  2015-03-23  8:02 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-21  3:23 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7a26bd4d83e5549137943de5f2c7b1ae90821093 ***

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

constify set_breakpoint_condition
gdb:

2015-03-20  Pedro Alves  <palves@redhat.com>

	* breakpoint.c (set_breakpoint_condition): Make argument "exp" const.
	* breakpoint.h (set_breakpoint_condition): Update declaration.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] constify gdbserver/server.c
@ 2015-03-20 20:05 sergiodj+buildbot
  2015-03-20 22:04 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-20 20:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b2333d22e0ead2d6f354c69760b6c6e0db161f02 ***

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

constify gdbserver/server.c
gdb/gdbserver/

2015-03-20  Pedro Alves  <palves@redhat.com>

	* server.c (handle_general_set): Make "req_str" const.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] gdbserver/Linux: unbreak thread event randomization
@ 2015-03-19 16:51 sergiodj+buildbot
  2015-03-19 17:54 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-19 16:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8bf3b159e55b42bb084f9da1af400a285025618f ***

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

gdbserver/Linux: unbreak thread event randomization
Wanting to make sure the new continue-pending-status.exp test tests
both cases of threads 2 and 3 reporting an event, I added counters to
the test, to make it FAIL if events for both threads aren't seen.
Assuming a well behaved backend, and given a reasonable number of
iterations, it should PASS.

However, running that against GNU/Linux gdbserver, I found that
surprisingly, that FAILed.  GDBserver always reported the breakpoint
hit for the same thread.

Turns out that I broke gdbserver's thread event randomization
recently, with git commit 582511be ([gdbserver] linux-low.c: better
starvation avoidance, handle non-stop mode too).  In that commit I
missed that the thread structure also has a status_pending_p field...
The end result was that count_events_callback always returns 0, and
then if no thread is stepping, select_event_lwp always returns the
event thread.  IOW, no randomization is happening at all.  Quite
curious how all the other changes in that patch were sufficient to fix
non-stop-fair-events.exp anyway even with that broken.

Tested on x86_64 Fedora 20, native and gdbserver.

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

	* linux-low.c (count_events_callback, select_event_lwp_callback):
	Use the lwp's status_pending_p field, not the thread's.

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

	* gdb.threads/continue-pending-status.exp (saw_thread_2)
	(saw_thread_3): New globals.
	(top level): Increment them when an event for the corresponding
	thread is seen.
	(no thread starvation): New test.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Create gdb/break-catch-syscall.c
@ 2015-03-11 21:37 sergiodj+buildbot
  2015-03-12 19:57 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-11 21:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 10304ef3e85c6163f882757f58eb18f5178249ce ***

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

Create gdb/break-catch-syscall.c
This commits cleans up the gdb/breakpoint.c file and moves everything
that is related to the 'catch syscall' command to the new file
gdb/break-catch-syscall.c.  This is just code movement, and the only
new part is the adjustment needed on 'catching_syscall_number' to use
the new 'breakpoint_find_if' function insted of relying on the
ALL_BREAKPOINTS macro.

Tested by running the 'gdb.base/catch-syscall.exp' testcase.

gdb/ChangeLog:
2015-03-11  Sergio Durigan Junior  <sergiodj@redhat.com>

	* Makefile.in (SFILES): New source break-catch-syscall.c.
	(COMMON_OBS): New object break-catch-syscall.o.
	* break-catch-syscall.c: New file.
	* breakpoint.c: Remove inclusion of "xml-syscall.h".
	(syscall_catchpoint_p): Move declaration to break-catch-syscall.c
	(struct syscall_catchpoint): Likewise.
	(dtor_catch_syscall): Likewise.
	(catch_syscall_inferior_data): Likewise.
	(struct catch_syscall_inferior_data): Likewise.
	(get_catch_syscall_inferior_data): Likewise.
	(catch_syscall_inferior_data_cleanup): Likewise.
	(insert_catch_syscall): Likewise.
	(remove_catch_syscall): Likewise.
	(breakpoint_hit_catch_syscall): Likewise.
	(print_it_catch_syscall): Likewise.
	(print_one_catch_syscall): Likewise.
	(print_mention_catch_syscall): Likewise.
	(print_recreate_catch_syscall): Likewise.
	(catch_syscall_breakpoint_ops): Likewise.
	(syscall_catchpoint_p): Likewise.
	(create_syscall_event_catchpoint): Likewise.
	(catch_syscall_split_args): Likewise.
	(catch_syscall_command_1): Likewise.
	(is_syscall_catchpoint_enabled): Likewise.
	(catch_syscall_enabled): Likewise.
	(catching_syscall_number): Likewise.
	(catch_syscall_completer): Likewise.
	(clear_syscall_counts): Likewise.
	(initialize_breakpoint_ops): Move initialization of syscall
	catchpoints to break-catch-syscall.c.
	(_initialize_breakpoint): Move code related to syscall catchpoints
	to break-catch-syscall.c.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Split TRY_CATCH into TRY + CATCH
@ 2015-03-07 18:24 sergiodj+buildbot
  2015-03-07 20:31 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-07 18:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 492d29ea1c9a8b2c7d5193908119a4e27c045687 ***

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

Split TRY_CATCH into TRY + CATCH
This patch splits the TRY_CATCH macro into three, so that we go from
this:

~~~
  volatile gdb_exception ex;

  TRY_CATCH (ex, RETURN_MASK_ERROR)
    {
    }
  if (ex.reason < 0)
    {
    }
~~~

to this:

~~~
  TRY
    {
    }
  CATCH (ex, RETURN_MASK_ERROR)
    {
    }
  END_CATCH
~~~

Thus, we'll be getting rid of the local volatile exception object, and
declaring the caught exception in the catch block.

This allows reimplementing TRY/CATCH in terms of C++ exceptions when
building in C++ mode, while still allowing to build GDB in C mode
(using setjmp/longjmp), as a transition step.

TBC, after this patch, is it _not_ valid to have code between the TRY
and the CATCH blocks, like:

  TRY
    {
    }

  // some code here.

  CATCH (ex, RETURN_MASK_ERROR)
    {
    }
  END_CATCH

Just like it isn't valid to do that with C++'s native try/catch.

By switching to creating the exception object inside the CATCH block
scope, we can get rid of all the explicitly allocated volatile
exception objects all over the tree, and map the CATCH block more
directly to C++'s catch blocks.

The majority of the TRY_CATCH -> TRY+CATCH+END_CATCH conversion was
done with a script, rerun from scratch at every rebase, no manual
editing involved.  After the mechanical conversion, a few places
needed manual intervention, to fix preexisting cases where we were
using the exception object outside of the TRY_CATCH block, and cases
where we were using "else" after a 'if (ex.reason) < 0)' [a CATCH
after this patch].  The result was folded into this patch so that GDB
still builds at each incremental step.

END_CATCH is necessary for two reasons:

First, because we name the exception object in the CATCH block, which
requires creating a scope, which in turn must be closed somewhere.
Declaring the exception variable in the initializer field of a for
block, like:

  #define CATCH(EXCEPTION, mask) \
    for (struct gdb_exception EXCEPTION; \
         exceptions_state_mc_catch (&EXCEPTION, MASK); \
	 EXCEPTION = exception_none)

would avoid needing END_CATCH, but alas, in C mode, we build with C90,
which doesn't allow mixed declarations and code.

Second, because when TRY/CATCH are wired to real C++ try/catch, as
long as we need to handle cleanup chains, even if there's no CATCH
block that wants to catch the exception, we need for stop at every
frame in the unwind chain and run cleanups, then rethrow.  That will
be done in END_CATCH.

After we require C++, we'll still need TRY/CATCH/END_CATCH until
cleanups are completely phased out -- TRY/CATCH in C++ mode will
save/restore the current cleanup chain, like in C mode, and END_CATCH
catches otherwise uncaugh exceptions, runs cleanups and rethrows, so
that C++ cleanups and exceptions can coexist.

IMO, this still makes the TRY/CATCH code look a bit more like a
newcomer would expect, so IMO worth it even if we weren't considering
C++.

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

	* common/common-exceptions.c (struct catcher) <exception>: No
	longer a pointer to volatile exception.  Now an exception value.
	<mask>: Delete field.
	(exceptions_state_mc_init): Remove all parameters.  Adjust.
	(exceptions_state_mc): No longer pop the catcher here.
	(exceptions_state_mc_catch): New function.
	(throw_exception): Adjust.
	* common/common-exceptions.h (exceptions_state_mc_init): Remove
	all parameters.
	(exceptions_state_mc_catch): Declare.
	(TRY_CATCH): Rename to ...
	(TRY): ... this.  Remove EXCEPTION and MASK parameters.
	(CATCH, END_CATCH): New.
	All callers adjusted.

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

	Adjust all callers of TRY_CATCH to use TRY/CATCH/END_CATCH
	instead.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] gdbserver: Support the "swbreak"/"hwbreak" stop reasons
@ 2015-03-05  7:48 sergiodj+buildbot
  2015-03-06 10:15 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-05  7:48 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1ec68e26c982a256df03d22dce072b88ab117a73 ***

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

gdbserver: Support the "swbreak"/"hwbreak" stop reasons
This patch teaches the core of gdbserver about the new "swbreak" and
"hwbreak" stop reasons, and adds the necessary hooks a backend needs
to implement to support the feature.

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

	* remote-utils.c (prepare_resume_reply): Report swbreak/hbreak.
	* server.c (swbreak_feature, hwbreak_feature): New globals.
	(handle_query) <qSupported>: Handle "swbreak+" and "hwbreak+".
	(captured_main): Clear swbreak_feature and hwbreak_feature.
	* server.h (swbreak_feature, hwbreak_feature): Declare.
	* target.h (struct target_ops) <stopped_by_sw_breakpoint,
	supports_stopped_by_sw_breakpoint, stopped_by_hw_breakpoint,
	supports_stopped_by_hw_breakpoint>: New fields.
	(target_supports_stopped_by_sw_breakpoint)
	(target_stopped_by_sw_breakpoint)
	(target_supports_stopped_by_hw_breakpoint)
	(target_stopped_by_hw_breakpoint): Declare.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] remote+docs: software/hardware breakpoint traps
@ 2015-03-05  6:17 sergiodj+buildbot
  2015-03-06  7:24 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-05  6:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f7e6eed5283bb5c8a3598dd986dc922b9a794f58 ***

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

remote+docs: software/hardware breakpoint traps
This adjusts target remote to tell the core whether a trap was caused
by a breakpoint.

To that end, the patch teaches GDB about new RSP stop reasons "T05
swbreak" and "T05 hwbreak", that remote targets report back to GDB,
similarly to how "T05 watch" indicates a stop caused by a watchpoint.

Because targets that can report these events are expected to
themselves adjust the PC after a software breakpoint, these new stop
reasons must only be reported if the stub is talking to a GDB that
understands them.  Because of that, the use of the new stop reasons
needs to be handshaked on initial connection, using the qSupported
mechanism.  GDB simply sends "swbreak+" in its qSupports query, and
the stub reports back "swbreak+" too.

Because these new stop reasons are required to fix a fundamental
non-stop mode problem, this commit extends the remote non-stop intro
section in the manual, documenting the events as required.

To be clear, GDB will still cope with remote targets that don't
support these new stop reasons; it will behave just like today.

Tested on x86-64 Fedora 20, native and gdbserver.

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

	* NEWS: Mention the new "swbreak" and "hwbreak" stop reasons.
	* remote.c (struct remote_state) <remote_stopped_by_watchpoint_p>:
	Delete field.
	<stop_reason>: New field.
	(PACKET_swbreak_feature, PACKET_hwbreak_feature): New enum values.
	(packet_set_cmd_state): New function.
	(remote_protocol_features): Register the "swbreak" and "hwbreak"
	features.
	(remote_query_supported): If not disabled with the corresponding
	"set remote foo-packet" command, report support for the swbreak
	and hwbreak features.
	(struct stop_reply) <remote_stopped_by_watchpoint_p>: Delete
	field.
	<stop_reason>: New field.
	(remote_parse_stop_reply): Handle "swbreak" and "hwbreak".
	(remote_wait_as): Adjust.
	(remote_stopped_by_sw_breakpoint)
	(remote_supports_stopped_by_sw_breakpoint)
	(remote_stopped_by_hw_breakpoint)
	(remote_supports_stopped_by_hw_breakpoint): New functions.
	(remote_stopped_by_watchpoint): New function.
	(init_remote_ops): Install them.
	(_initialize_remote): Register new "set/show remote
	swbreak-feature-packet" and "set/show remote
	swbreak-feature-packet" commands.

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

	* gdb.texinfo (Remote Configuration): Document the "set/show
	remote swbreak-feature-packet" and "set/show remote
	hwbreak-feature-packet" commands.
	(Packets) <Z0>: Add cross link to the "swbreak" stop reason's
	decription.
	(Stop Reply Packets): Document the swbreak and hwbreak stop
	reasons.
	(General Query Packets): Document the swbreak and hwbreak
	qSupported features.
	(Remote Non-Stop): Explain that swbreak and hwbreak are required.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] record-full/record-btrace: software/hardware breakpoint trap
@ 2015-03-05  4:30 sergiodj+buildbot
  2015-03-06  6:24 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-05  4:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9e8915c6cee5c37637521b424d723e990e06d597 ***

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

record-full/record-btrace: software/hardware breakpoint trap
This adjusts the record targets to tell the core whether a trap was
caused by a breakpoint.  Targets that can do this should report
breakpoint traps with the PC already adjusted, so this removes the
re-incrementing record-full was doing.

These targets need to be adjusted before process_stratum targets
beneath are, otherwise target_supports_stopped_by_sw_breakpoint,
etc. would fall through to the target beneath while
recording/replaying, and the core would get confused.

Tested on x86-64 Fedora 20, native and gdbserver.

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

	* btrace.h: Include target/waitstatus.h.
	(struct btrace_thread_info) <stop_reason>: New field.
	* record-btrace.c (record_btrace_step_thread): Use
	record_check_stopped_by_breakpoint instead of breakpoint_here_p.
	(record_btrace_decr_pc_after_break): Delete.
	(record_btrace_stopped_by_sw_breakpoint)
	(record_btrace_supports_stopped_by_sw_breakpoint)
	(record_btrace_stopped_by_hw_breakpoint)
	(record_btrace_supports_stopped_by_hw_breakpoint): New functions.
	(init_record_btrace_ops): Install them.
	* record-full.c (record_full_hw_watchpoint): Delete and replace
	with ...
	(record_full_stop_reason): ... this throughout.
	(record_full_exec_insn): Adjust.
	(record_full_wait_1): Adjust.  No longer re-increment the PC.
	(record_full_wait_1): Adjust.  Use
	record_check_stopped_by_breakpoint instead of breakpoint_here_p.
	(record_full_stopped_by_watchpoint): Adjust.
	(record_full_stopped_by_sw_breakpoint)
	(record_full_supports_stopped_by_sw_breakpoint)
	(record_full_supports_stopped_by_sw_breakpoint)
	(record_full_stopped_by_hw_breakpoint)
	(record_full_supports_stopped_by_hw_breakpoint): New functions.
	(init_record_full_ops, init_record_full_core_ops): Install them.
	* record.c (record_check_stopped_by_breakpoint): New function.
	* record.h: Include target/waitstatus.h.
	(record_check_stopped_by_breakpoint): New declaration.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] enum lwp_stop_reason -> enum target_stop_reason
@ 2015-03-05  3:54 sergiodj+buildbot
  2015-03-06  4:54 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-05  3:54 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 15c66dd626380fbd7db6538b0c21d1fe86dda6c9 ***

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

enum lwp_stop_reason -> enum target_stop_reason
We're going to need the same enum as enum lwp_stop_reason in more
targets, so this promotes it to common code.

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

	enum lwp_stop_reason -> enum target_stop_reason
	* linux-low.c (check_stopped_by_breakpoint): Adjust.
	(thread_still_has_status_pending_p, check_stopped_by_watchpoint)
	(linux_wait_1, stuck_in_jump_pad_callback)
	(move_out_of_jump_pad_callback, linux_resume_one_lwp)
	(linux_stopped_by_watchpoint):
	* linux-low.h (enum lwp_stop_reason): Delete.
	(struct lwp_info) <stop_reason>: Now an enum target_stop_reason.
	* linux-x86-low.c (x86_linux_prepare_to_resume): Adjust.

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

	enum lwp_stop_reason -> enum target_stop_reason
	* linux-nat.c (linux_resume_one_lwp, check_stopped_by_watchpoint)
	(linux_nat_stopped_by_watchpoint, status_callback)
	(linux_nat_wait_1): Adjust.
	* linux-nat.h (enum lwp_stop_reason): Delete.
	(struct lwp_info) <stop_reason>: Now an enum target_stop_reason.
	* x86-linux-nat.c (x86_linux_prepare_to_resume): Adjust.
	* target/waitstatus.h (enum target_stop_reason): New.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Teach GDB about targets that can tell whether a trap is a breakpoint event
@ 2015-03-05  2:56 sergiodj+buildbot
  2015-03-06  1:06 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-05  2:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1cf4d9513af10d419c71099ae644f07b6724642b ***

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

Teach GDB about targets that can tell whether a trap is a breakpoint event
The moribund locations heuristics are problematic.  This patch teaches
GDB about targets that can reliably tell whether a trap was caused by
a software or hardware breakpoint, and thus don't need moribund
locations, thus bypassing all the problems that mechanism has.

The non-stop-fair-events.exp test is frequently failing currently.
E.g., see https://sourceware.org/ml/gdb-testers/2015-q1/msg03148.html.

The root cause is a fundamental problem with moribund locations.  For
example, the stepped_breakpoint logic added by af48d08f breaks in this
case (which is what happens with that test):

 - Step thread A, no breakpoint is set at PC.

 - The kernel doesn't schedule thread A yet.

 - Insert breakpoint at A's PC, for some reason (e.g., a step-resume
   breakpoint for thread B).

 - Kernel finally schedules thread A.

 - thread A's stepped_breakpoint flag is not set, even though it now
   stepped a breakpoint instruction.

 - adjust_pc_after_break gets the PC wrong, because PC == PREV_PC, but
   stepped_breakpoint is not set.

We needed the stepped_breakpoint logic to workaround moribund
locations, because otherwise adjust_pc_after_break could apply an
adjustment when it shouldn't just because there _used_ to be a
breakpoint at PC (a moribund breakpoint location).  For example, on
x86, that's wrong if the thread really hasn't executed an int3, but
instead executed some other 1-byte long instruction.  Getting the PC
adjustment wrong of course leads to the inferior executing the wrong
instruction.

Other problems with moribund locations are:

 - if a true SIGTRAP happens to be raised when the program is
   executing the PC that used to have a breakpoint, GDB will assume
   that is a trap for a breakpoint that has recently been removed, and
   thus we miss reporting the random signal to the user.

 - to minimize that, we get rid of moribund location after a while.
   That while is defined as just a certain number of events being
   processed.  That number of events sometimes passes by before a
   delayed breakpoint is processed, and GDB confuses the trap for a
   random signal, thus reporting the random trap.  Once the user
   resumes the thread, the program crashes because the PC was not
   adjusted...

The fix for all this is to bite the bullet and get rid of heuristics
and instead rely on the target knowing accurately what caused the
SIGTRAP.  The target/kernel/stub is in the best position to know what
that, because it can e.g. consult priviledged CPU flags GDB has no
access to, or by knowing which exception vector entry was called when
the instruction trapped, etc.  Most debug APIs I've seen to date
report breakpoint hits as a distinct event in some fashion.  For
example, on the Linux kernel, whether a breakpoint was executed is
exposed to userspace in the si_code field of the SIGTRAP's siginfo.
On Windows, the debug API reports a EXCEPTION_BREAKPOINT exception
code.

We needed to keep around deleted breakpoints in an on-the-side list
(the moribund locations) for two main reasons:

  - Know that a SIGTRAP actually is a delayed event for a hit of a
    breakpoint that was removed before the event was processed, and
    thus should not be reported as a random signal.

  - So we still do the decr_pc_after_break adjustment in that case, so
    that the thread is resumed at the correct address.

In the new model, if GDB processes an event the target tells is a
breakpoint trap, and GDB doesn't find the corresponding breakpoint in
its breakpoint tables, it means that event is a delayed event for a
breakpoint that has since been removed, and thus the event should be
ignored.

For the decr_pc_after_after issue, it ends up being much simpler that
on targets that can reliably tell whether a breakpoint trapped, for
the breakpoint trap to present the PC already adjusted.  Proper
multi-threading support already implies that targets needs to be doing
decr_pc_after_break adjustment themselves, otherwise for example, in
all-stop if two threads hit a breakpoint simultaneously, and the user
does "info threads", he'll see the non-event thread that hit the
breakpoint stopped at the wrong PC.

This way (target adjusts) also ends up eliminating the need for some
awkward re-incrementing of the PC in the record-full and Linux targets
that we do today, and the need for the target_decr_pc_after_break
hook.

If the target always adjusts, then there's a case where GDB needs to
re-increment the PC.  Say, on x86, an "int3" instruction that was
explicitly written in the program traps.  In this case, GDB should
report a random SIGTRAP signal to the user, with the PC pointing at
the instruction past the int3, just like if GDB was not debugging the
program.  The user may well decide to pass the SIGTRAP to the program
because the program being debugged has a SIGTRAP handler that handles
its own breakpoints, and expects the PC to be unadjusted.

Tested on x86-64 Fedora 20.

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

	* breakpoint.c (need_moribund_for_location_type): New function.
	(bpstat_stop_status): Don't skipping checking moribund locations
	of breakpoint types which the target tell caused a stop.
	(program_breakpoint_here_p): New function, factored out from ...
	(bp_loc_is_permanent): ... this.
	(update_global_location_list): Don't create a moribund location if
	the target supports reporting stops of the type of the removed
	breakpoint.
	* breakpoint.h (program_breakpoint_here_p): New declaration.
	* infrun.c (adjust_pc_after_break): Return early if the target has
	already adjusted the PC.  Add comments.
	(handle_signal_stop): If nothing explains a signal, and the target
	tells us the stop was caused by a software breakpoint, check if
	there's a breakpoint instruction in the memory.  If so, adjust the
	PC before presenting the stop to the user.  Otherwise, ignore the
	trap.  If nothing explains a signal, and the target tells us the
	stop was caused by a hardware breakpoint, ignore the trap.
	* target.h (struct target_ops) <to_stopped_by_sw_breakpoint,
	to_supports_stopped_by_sw_breakpoint, to_stopped_by_hw_breakpoint,
	to_supports_stopped_by_hw_breakpoint>: New fields.
	(target_stopped_by_sw_breakpoint)
	(target_supports_stopped_by_sw_breakpoint)
	(target_stopped_by_hw_breakpoint)
	(target_supports_stopped_by_hw_breakpoint): Define.
	* target-delegates.c: Regenerate.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] follow-fork: don't lose the ptids as set by the target
@ 2015-03-05  0:03 sergiodj+buildbot
  2015-03-06  0:11 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-05  0:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 79639e11323e209d3dfd1355abac3b83a87c6878 ***

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

follow-fork: don't lose the ptids as set by the target
This Linuxism has made its way into infrun.c, in the follow-fork code:

       inferior_ptid = ptid_build (child_pid, child_pid, 0);

The OS-specific code should fill in the LWPID, TID parts with the
appropriate values, if any, and the core code should not be peeking at
the components of the ptids.

gdb/
2015-03-04  Pedro Alves  <palves@redhat.com>

	* infrun.c (follow_fork_inferior): Use the whole of the
	inferior_ptid and pending_follow.related_pid ptids instead of
	building ptids from the process components.  Adjust verbose output
	to use target_pid_to_str.
	* linux-nat.c (linux_child_follow_fork): Use the whole of the
	inferior_ptid and pending_follow.related_pid ptids instead of
	building ptids from the process components.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Add linux-aarch64-low.c in SFILE
@ 2015-03-04 22:15 sergiodj+buildbot
  2015-03-05 19:11 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-04 22:15 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 98fc70d642895b7b43f196e19a004e07bd5f16e7 ***

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

Add linux-aarch64-low.c in SFILE
gdb/gdbserver:

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

	* Makefile.in (SFILES): Add linux-aarch64-low.c.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Enable gdb.base/foll-fork.exp on OpenBSD
@ 2015-03-04 20:53 sergiodj+buildbot
  2015-03-05 18:19 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-04 20:53 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4727d6136a997875c0f4a38bc7fde365474d4822 ***

Author: Mark Kettenis <kettenis@gnu.org>
Branch: master
Commit: 4727d6136a997875c0f4a38bc7fde365474d4822

Enable gdb.base/foll-fork.exp on OpenBSD
gdb/testsuite/
2015-03-04  Mark Kettenis  <kettenis@gnu.org>

        * gdb.base/foll-fork.exp: Enable on *-*-openbsd*.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Make "catch fork" work on systems with PT_GET_PROCESS_STATE
@ 2015-03-04 20:01 sergiodj+buildbot
  2015-03-05 16:54 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-04 20:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e85e8e5effcfa1a1834fdbf899e167da6dccd2cd ***

Author: Mark Kettenis <kettenis@gnu.org>
Branch: master
Commit: e85e8e5effcfa1a1834fdbf899e167da6dccd2cd

Make "catch fork" work on systems with PT_GET_PROCESS_STATE
These systems (OpenBSD and HP-UX 10.x) already support follow-fork
including the events needed to for "catch fork".  This just makes
the upper layers realize this.

gdb/
2015-03-04  Mark Kettenis  <kettenis@gnu.org>

        * inf-ptrace.c [PT_GET_PROCESS_STATE]
        (inf_ptrace_insert_fork_catchpoint): New function.
        (inf_ptrace_remove_fork_catchpoint): New function.
        (inf_ptrace_target) [PT_GET_PROCESS_STATE]: Install them.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [AArch64] Removing unused functions.
@ 2015-03-04 18:52 sergiodj+buildbot
  2015-03-05 15:43 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-04 18:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8ef229f32be156f374b8b5e3c63dba735a81fe55 ***

Author: Marcus Shawcroft <marcus.shawcroft@arm.com>
Branch: master
Commit: 8ef229f32be156f374b8b5e3c63dba735a81fe55

[AArch64] Removing unused functions.
Removing a group of unused functions from the AArch64 BFD backend.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [AArch64] Call abort() consistently in unhandled stub switch statements.
@ 2015-03-04 17:51 sergiodj+buildbot
  2015-03-05 15:08 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-04 17:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8e2fe09f70e721bfd8aaa0690537640a44538f25 ***

Author: Marcus Shawcroft <marcus.shawcroft@arm.com>
Branch: master
Commit: 8e2fe09f70e721bfd8aaa0690537640a44538f25

[AArch64] Call abort() consistently in unhandled stub switch statements.
Ensure we hard stop via abort() for unhandled stub types rather than
continuing either silently (or noisly with a BFD_FAIL()).

Call abort() giving a hard stop rather than BFD_FAIL () for unhandled
stub types.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] S390: Name "invisible" registers with the empty string instead of NULL
@ 2015-03-04 17:00 sergiodj+buildbot
  2015-03-05 12:43 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-04 17:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 87de11c05253566abb04479a4842cc934d0c822e ***

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

S390: Name "invisible" registers with the empty string instead of NULL
When adding vector register support to GDB, s390_register_name() was
added to suppress the right halves of the first 16 vector registers.
However, that function returned NULL instead of an empty string in such
a case.  This leads to an incomplete list of registers returned by
"complete info registers ", because completion stops at the first NULL
return value from user_reg_map_regnum_to_name().

gdb/ChangeLog:

	* s390-linux-tdep.c (s390_register_name): Return empty string
	instead of NULL for registers that shouldn't be visible.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] breakpoint-in-ro-region.exp: Support targets stopping in mid-line after "si"
@ 2015-03-04 15:54 sergiodj+buildbot
  2015-03-05 10:52 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-04 15:54 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c214c7cfd38006369e1da13644000ce2e180a5fa ***

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

breakpoint-in-ro-region.exp: Support targets stopping in mid-line after "si"
On some targets each of the assignments "i = 0" in the C source for
"breakpoint-in-ro-region.exp" are compiled to a single instruction.
Then each "si" stops at the beginning of the next source line.  But on
some other targets (like s390) such an assignment compiles to multiple
instructions.  Then "si" may stop in mid-line, and GDB displays the PC
address in addition to the source line number.  This was not considered
by the regexp for this case.

gdb/testsuite/ChangeLog:

	* gdb.base/breakpoint-in-ro-region.exp (test_single_step): In the
	regexps for GDB's current line display, accept a hex address
	preceding the line number.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] catch-syscall.exp: Fix missing architecture name for s390:31-bit
@ 2015-03-04 14:34 sergiodj+buildbot
  2015-03-05  8:52 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-04 14:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6d74a497ba4fc2ba67142310a9fad42e035ac9a7 ***

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

catch-syscall.exp: Fix missing architecture name for s390:31-bit
For the "multiple targets" test in catch-syscall.exp, set the 'arch1'
variable to a valid string.

gdb/testsuite/ChangeLog:

	* gdb.base/catch-syscall.exp (test_catch_syscall_multi_arch): Set
	the 'arch1' variable for "s390*-linux*" targets.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] S390: Place "s390:31-bit" after default arch in 64-bit arch list
@ 2015-03-04 12:24 sergiodj+buildbot
  2015-03-05  6:17 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-04 12:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT df88b70224175011abf2cd599d5eec6fb81a90b7 ***

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

S390: Place "s390:31-bit" after default arch in 64-bit arch list
On 64-bit platforms GDB did not include "s390:31-bit" in its list of
architecture names.  This patch fixes that.

To determine the list of architecture names for S390,
gdbarch_printable_names() walks through the linked list of BFD arches
starting with the default S390 arch, which is "s390:64-bit" on 64-bit
platforms.  But since "s390:64-bit" was at the end of that list, the
31-bit architecture was not reached.  The patch swaps the elements of
that list on 64-bit platforms.

bfd/ChangeLog:

	* cpu-s390.c (N): New macro.
	(bfd_s390_31_arch): New.  Define only if default target word size
	is 64 bits.  Otherwise define...
	(bfd_390_64_arch): ...this.  Make static.
	(bfd_s390_arch): Define according to the default target word size.
	Let the 'next' field point to the alternate arch.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] gdb.threads/clone-thread_db.c: Add missing includes and fix pthread_join call
@ 2015-03-04 11:36 sergiodj+buildbot
  2015-03-05  1:40 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-04 11:36 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 511aee7c3906063902415391f288460a2c116f26 ***

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

gdb.threads/clone-thread_db.c: Add missing includes and fix pthread_join call
This fixes:

> gdb compile failed, /gdb/testsuite/gdb.threads/clone-thread_db.c: In function 'main':
> /gdb/testsuite/gdb.threads/clone-thread_db.c:67:3: warning: implicit declaration of function 'alarm' [-Wimplicit-function-declaration]
>    alarm (300);
>    ^
> /gdb/testsuite/gdb.threads/clone-thread_db.c:69:3: warning: implicit declaration of function 'pthread_create' [-Wimplicit-function-declaration]
>    pthread_create (&child, NULL, thread_fn, NULL);
>    ^
> /gdb/testsuite/gdb.threads/clone-thread_db.c:70:3: warning: implicit declaration of function 'pthread_join' [-Wimplicit-function-declaration]
>    pthread_join (child);
>    ^

And then adding the missing headers revealed the pthread_join call was
incorrect.  This probably fixes the crash we see on ppc64be, e.g., at

 https://sourceware.org/ml/gdb-testers/2015-q1/msg04415.html

the logs there show:

 ...
 Program received signal SIGSEGV, Segmentation fault.
 [Switching to Thread 0x3fffb7ff54a0 (LWP 9275)]
 0x00003fffb7f3ce74 in .pthread_join () from /lib64/libpthread.so.0
 (gdb) FAIL: gdb.threads/clone-thread_db.exp: continue to end
 ...

Tested on x86_64 Fedora 20.

gdb/testsuite/
2015-03-04  Pedro Alves  <palves@redhat.com>

	* gdb.threads/clone-thread_db.c: Include unistd.h and pthread.h.
	(main): Pass missing retval argument to pthread_join call.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] RL78 - fix ADDR16 relax
@ 2015-03-04  2:54 sergiodj+buildbot
  2015-03-04 18:50 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-04  2:54 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 71eef2bd8dc3a37709908bf14a95c48b80c04c42 ***

Author: DJ Delorie <dj@redhat.com>
Branch: master
Commit: 71eef2bd8dc3a37709908bf14a95c48b80c04c42

RL78 - fix ADDR16 relax
* elf32-rl78.c (rl78_elf_relax_section): Only relax ADDR16's if
there's a symbol.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Remove unused function declarations in target.h
@ 2015-03-04  0:10 sergiodj+buildbot
  2015-03-04 16:53 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-04  0:10 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b072f6c163b25ec90d592ca42aeb56bc88e8da0c ***

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

Remove unused function declarations in target.h
find_default_create_inferior and find_default_attach were removed in b3ccfe11.

gdb/ChangeLog:

	* target.h (find_default_create_inferior): Remove declaration.
	(find_default_attach): Likewise.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] inf-ptrace.c: use ptid_get_pid when resuming all threads
@ 2015-03-03 20:04 sergiodj+buildbot
  2015-03-04 13:51 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-03 20:04 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c1593e4fa9901c65a32e85c3c5d3ec41598be887 ***

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

inf-ptrace.c: use ptid_get_pid when resuming all threads
In this case, we want to resume the entire process and not an
individual thread.

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

	* inf-ptrace.c (inf_ptrace_resume): Remove spurious whitespace.
	Use ptid_get_pid to get the overall process id when resuming all
	threads.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Fix GDB/MI doc: duplicate syscall-entry under *stopped
@ 2015-03-03 17:39 sergiodj+buildbot
  2015-03-04 10:42 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-03 17:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a64c9f7b850554956083678dd1ef330dd9a7cf22 ***

Author: Philippe Proulx <eeppeliteloop@gmail.com>
Branch: master
Commit: a64c9f7b850554956083678dd1ef330dd9a7cf22

Fix GDB/MI doc: duplicate syscall-entry under *stopped
gdb/doc/ChangeLog:

2015-03-03  Philippe Proulx  eeppeliteloop@gmail.com

	* gdb.texinfo (gdb/mi Async Records): Fix duplicate syscall-entry
	under *stopped.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] [ARM] Skip private symbol when doing objdump
@ 2015-03-03 16:36 sergiodj+buildbot
  2015-03-04 10:05 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-03 16:36 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d8282f0eb10a1a5759bcca4582098a8369f508f8 ***

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

[ARM] Skip private symbol when doing objdump
2015-03-03  Jiong Wang  <jiong.wang@arm.com>

  opcode/
    * arm-dis.c (arm_symbol_is_valid): Skip ARM private symbols.

  binutils/testsuite/
    * binutils-all/arm/rvct_symbol.s: New testcase.
    * binutils-all/arm/objdump.exp: Run it.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] btrace: support 32-bit inferior on 64-bit host
@ 2015-03-03 13:24 sergiodj+buildbot
  2015-03-04  0:05 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-03 13:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d68e53f47932eb7c374df9b90faed7aca2eed9d7 ***

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

btrace: support 32-bit inferior on 64-bit host
The heuristic for filtering out kernel addressess in BTS trace checks the
most significant bit in each address.  This works fine for 32-bit and 64-bit
mode.

For 32-bit compatibility mode, i.e. a 32-bit inferior running on 64-bit
host, we need to check bit 63 (or any bit bigger than 31), not bit 31.

Use the machine field in struct utsname provided by a uname call to
determine whether we are running on a 64-bit host.

Thanks to Jan Kratochvil for reporting the issue.

gdb/
	* nat/linux-btrace.c: Include sys/utsname.h.
	(linux_determine_kernel_ptr_bits): New.
	(linux_enable_bts): Call linux_determine_kernel_ptr_bits.
	* x86-linux-nat.c (x86_linux_enable_btrace): Do not overwrite non-zero
	ptr_bits.

gdbserver/
	* linux-low.c (linux_low_enable_btrace): Do not overwrite non-zero
	ptr_bits.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] btrace: work around _dl_runtime_resolve returning to resolved function
@ 2015-03-03 11:55 sergiodj+buildbot
  2015-03-03 23:37 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-03 11:55 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 986b66010c684a871f5606cb4f074d4e3d829e2f ***

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

btrace: work around _dl_runtime_resolve returning to resolved function
On some systems, _dl_runtime_resolve returns to the resolved function
instead of jumping to it.  Since btrace will not find the function in
the current stack back trace, it will start a new back trace on the
same level.  It will look the same to the user via the backtrace
command but the frames will have different id's which confuses stepping.

This fixes a test fail with 32-bit inferior reported by Jan Kratochvil.

gdb/
	* btrace.c (ftrace_update_function): Treat return as tailcall for
	"_dl_runtime_resolve".


^ permalink raw reply	[flat|nested] 1132+ messages in thread
[parent not found: <c966a859b96f78920c16e1161578405d88b425cf@kwanyin>]
* [binutils-gdb] follow-exec: delete all non-execing threads
@ 2015-03-03  2:59 sergiodj+buildbot
  2015-03-03 20:36 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-03  2:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 95e50b2723eba05ca34e9ea69c1de63e65ce9578 ***

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

follow-exec: delete all non-execing threads
This fixes invalid reads Valgrind first caught when debugging against
a GDBserver patched with a series that adds exec events to the remote
protocol.  Like these, using the gdb.threads/thread-execl.exp test:

$ valgrind ./gdb -data-directory=data-directory ./testsuite/gdb.threads/thread-execl  -ex "tar extended-remote :9999" -ex "b thread_execler" -ex "c" -ex "set scheduler-locking on"
...
Breakpoint 1, thread_execler (arg=0x0) at src/gdb/testsuite/gdb.threads/thread-execl.c:29
29        if (execl (image, image, NULL) == -1)
(gdb) n
Thread 32509.32509 is executing new program: build/gdb/testsuite/gdb.threads/thread-execl
[New Thread 32509.32532]
==32510== Invalid read of size 4
==32510==    at 0x5AA7D8: delete_breakpoint (breakpoint.c:13989)
==32510==    by 0x6285D3: delete_thread_breakpoint (thread.c:100)
==32510==    by 0x628603: delete_step_resume_breakpoint (thread.c:109)
==32510==    by 0x61622B: delete_thread_infrun_breakpoints (infrun.c:2928)
==32510==    by 0x6162EF: for_each_just_stopped_thread (infrun.c:2958)
==32510==    by 0x616311: delete_just_stopped_threads_infrun_breakpoints (infrun.c:2969)
==32510==    by 0x616C96: fetch_inferior_event (infrun.c:3267)
==32510==    by 0x63A2DE: inferior_event_handler (inf-loop.c:57)
==32510==    by 0x4E0E56: remote_async_serial_handler (remote.c:11877)
==32510==    by 0x4AF620: run_async_handler_and_reschedule (ser-base.c:137)
==32510==    by 0x4AF6F0: fd_event (ser-base.c:182)
==32510==    by 0x63806D: handle_file_event (event-loop.c:762)
==32510==  Address 0xcf333e0 is 16 bytes inside a block of size 200 free'd
==32510==    at 0x4A07577: free (in /usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so)
==32510==    by 0x77CB74: xfree (common-utils.c:98)
==32510==    by 0x5AA954: delete_breakpoint (breakpoint.c:14056)
==32510==    by 0x5988BD: update_breakpoints_after_exec (breakpoint.c:3765)
==32510==    by 0x61360F: follow_exec (infrun.c:1091)
==32510==    by 0x6186FA: handle_inferior_event (infrun.c:4061)
==32510==    by 0x616C55: fetch_inferior_event (infrun.c:3261)
==32510==    by 0x63A2DE: inferior_event_handler (inf-loop.c:57)
==32510==    by 0x4E0E56: remote_async_serial_handler (remote.c:11877)
==32510==    by 0x4AF620: run_async_handler_and_reschedule (ser-base.c:137)
==32510==    by 0x4AF6F0: fd_event (ser-base.c:182)
==32510==    by 0x63806D: handle_file_event (event-loop.c:762)
==32510==
[Switching to Thread 32509.32532]

Breakpoint 1, thread_execler (arg=0x0) at src/gdb/testsuite/gdb.threads/thread-execl.c:29
29        if (execl (image, image, NULL) == -1)
(gdb)

The breakpoint in question is the step-resume breakpoint of the
non-main thread, the one that was "next"ed.

The exact same issue can be seen on mainline with native debugging, by
running the thread-execl.exp test in non-stop mode, because the kernel
doesn't report a thread exit event for the execing thread.

Tested on x86_64 Fedora 20.

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

	* infrun.c (follow_exec): Delete all threads of the process except
	the event thread.  Extended comments.

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

	* gdb.threads/thread-execl.exp (do_test): Handle non-stop.
	(top level): Call do_test with non-stop as well.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Revert "Remove true and false ARI checks now that we use stdbool.h."
@ 2015-03-02 16:40 sergiodj+buildbot
  2015-03-03 15:23 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-02 16:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 00e474c2e96f9a56f128ee29fbdc36ac32d5e14a ***

Author: Joel Brobecker <brobecker@adacore.com>
Branch: master
Commit: 00e474c2e96f9a56f128ee29fbdc36ac32d5e14a

Revert "Remove true and false ARI checks now that we use stdbool.h."
As we cannot use type bool until conversion to C++ is official,
this patch re-instates the ARI checks for "true/false".

gdb/ChangeLog:

        * contrib/ari/gdb_ari.sh: Reinstate checks for "true" and "false".


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] S390: Vector register test case
@ 2015-03-02 14:22 sergiodj+buildbot
  2015-03-03 13:08 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-02 14:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4fa5d7b436815f58688ec9245f24fc83263364b9 ***

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

S390: Vector register test case
Add a test case for S/390 vector registers support.

gdb/testsuite/ChangeLog:

	* gdb.arch/s390-vregs.exp: New test.
	* gdb.arch/s390-vregs.S: New file.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
[parent not found: <8a526fa69afd8ea7d2e303f80c03f9eb46211390@kwanyin>]
* [binutils-gdb] S390: Add vector register support to gdbserver
@ 2015-03-02 13:16 sergiodj+buildbot
  2015-03-03 12:32 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-02 13:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bf2d68ab8c9da89a7caec2abdd2cc27c607f4a04 ***

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

S390: Add vector register support to gdbserver
On S/390 targets with vector registers, enable gdbserver to advertise
and handle the feature "org.gnu.gdb.s390.vx".

gdb/gdbserver/ChangeLog:

	* Makefile.in (s390-vx-linux64.c, s390-tevx-linux64.c)
	(s390x-vx-linux64.c, s390x-tevx-linux64.c): New rules.
	(clean): Add "rm -f" for above C files.
	* configure.srv (srv_regobj): Add s390-vx-linux64.o,
	s390-tevx-linux64.o, s390x-vx-linux64.o, and s390x-tevx-linux64.o.
	(srv_xmlfiles): Add s390-vx-linux64.xml, s390-tevx-linux64.xml,
	s390x-vx-linux64.xml, s390x-tevx-linux64.xml, and s390-vx.xml.
	* linux-s390-low.c (HWCAP_S390_VX): New macro.
	(init_registers_s390_vx_linux64, init_registers_s390_tevx_linux64)
	(init_registers_s390x_vx_linux64)
	(init_registers_s390x_tevx_linux64)
	(tdesc_s390_vx_linux64, tdesc_s390_tevx_linux64)
	(tdesc_s390x_vx_linux64, tdesc_s390x_tevx_linux64): New extern
	declarations.
	(s390_fill_vxrs_low, s390_store_vxrs_low, s390_fill_vxrs_high)
	(s390_store_vxrs_high): New functions.
	(s390_regsets): Add entries for NT_S390_VXRS_LOW and
	NT_S390_VXRS_HIGH.
	(s390_arch_setup): Add logic for selecting one of the new target
	descriptions.  Activate the new vector regsets if applicable.
	(initialize_low_arch): Also invoke init_registers_s390_vx_linux64,
	init_registers_s390_tevx_linux64, init_registers_s390x_vx_linux64,
	and init_registers_s390x_tevx_linux64.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
[parent not found: <0fa9c223ddc05a4b823bc7982dce8ba3b45d903f@kwanyin>]
* [binutils-gdb] S390: Add target descriptions for vector register sets
@ 2015-03-02 11:11 sergiodj+buildbot
  2015-03-03 10:11 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-02 11:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 446899e472025a04017064f5172105cec70eb357 ***

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

S390: Add target descriptions for vector register sets
The IBM z13 has new vector registers v0-v31 which are presented by the
Linux kernel as two additional register sets.  This patch adds XML
descriptions and the respective autogenerated .c and .dat files for
S390 targets with this feature.  Note that supported combinations
include targets with and without a transactional execution facility.

gdb/ChangeLog:

	* features/s390-tevx-linux64.xml: New file.
	* features/s390-vx-linux64.xml: New file.
	* features/s390-vx.xml: New file.
	* features/s390x-tevx-linux64.xml: New file.
	* features/s390x-vx-linux64.xml: New file.
	* features/Makefile (WHICH): Add s390-vx-linux64,
	s390x-vx-linux64, s390-tevx-linux64, and s390x-tevx-linux64.
	(s390-vx-linux64-expedite, s390-tevx-linux64-expedite)
	(s390x-vx-linux64-expedite, s390x-tevx-linux64-expedite): New
	macros.
	* features/s390-tevx-linux64.c: New generated file.
	* features/s390-vx-linux64.c: Likewise.
	* features/s390x-tevx-linux64.c: Likewise.
	* features/s390x-vx-linux64.c: Likewise.
	* regformats/s390-tevx-linux64.dat: Likewise.
	* regformats/s390-vx-linux64.dat: Likewise.
	* regformats/s390x-tevx-linux64.dat: Likewise.
	* regformats/s390x-vx-linux64.dat: Likewise.

gdb/doc/ChangeLog:

	* gdb.texinfo (S/390 and System z Features): Describe new feature
	"org.gnu.gdb.s390.vx".


^ permalink raw reply	[flat|nested] 1132+ messages in thread
[parent not found: <1424c16eab1a96de054991c346c2bbf3eac82dec@kwanyin>]
[parent not found: <10367c7c946a123597cbc5efaa44c18912e5e43a@kwanyin>]
[parent not found: <4180215b9db1549b88da2da2fcc320fe28233481@kwanyin>]
[parent not found: <68c14faadaf5bfd9816ac913dc8858116aa15a84@kwanyin>]
[parent not found: <3bc3d82a005466a66fa22f704c90f4486ca71344@kwanyin>]
[parent not found: <07697489f4587e41f4f63aa526c1bd7d2fcd5494@kwanyin>]
* [binutils-gdb] More redefinition errors in C++ mode
@ 2015-03-01  2:57 sergiodj+buildbot
  2015-03-02 21:05 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-03-01  2:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bf36a1e7df75608045be60a5d16a1df207df3464 ***

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

More redefinition errors in C++ mode
In C++, we can't forward declare objects like in C.  The compiler
complains about symbol redefinition.  Most cases of this were fixed in
e36122e9, but dtrace probes introduced a new one meanwhile.  This
patch fixes it the same way e36122e9 fixed the others.

gdb/
2015-02-27  Pedro Alves  <palves@redhat.com>

	* dtrace-probe.c (dtrace_probe_ops): Make extern.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] objcopy: Add --update-section option.
@ 2015-02-28 22:53 sergiodj+buildbot
  2015-03-03  9:23 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-02-28 22:53 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT acf1419f9c52d06ee70169b85c5f8980c7359f8f ***

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

objcopy: Add --update-section option.
New option for objcopy --update-section allows the contents of a section
to be updated while maintaining the section flags, and, for ELF files,
the section to segment mapping.

New test uses --dump-section and --update-section to check that a
section can be made larger and smaller with an update.

binutils/ChangeLog:

	* objcopy.c (update_sections): New list.
	(command_line_switch): Add OPTION_UPDATE_SECTION.
	(copy_options): Add update-section.
	(copy_usage): Document new option.
	(is_update_section): New function.
	(is_strip_section_1): Add check for attempt to update and remove
	the same section.
	(copy_object): Update size and content of requested sections.
	(skip_section): Don't copy for updated sections.
	(copy_main): Handle --update-section.
	* doc/binutils.texi (objcopy): Add description of --update-section
	option.
	* NEWS: Mention --update-section option.

binutils/testsuite/ChangeLog:

	* binutils-all/update-1.s: New file.
	* binutils-all/update-2.s: New file.
	* binutils-all/update-3.s: New file.
	* binutils-all/update-4.s: New file.
	* binutils-all/update-section.exp: New file.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] symtab.h (struct symtab) <next>: Fix comment.
@ 2015-02-28 21:50 sergiodj+buildbot
  2015-03-03  6:55 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-02-28 21:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b7236fbee40060bcf5e90740a5c5706317749f91 ***

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

symtab.h (struct symtab) <next>: Fix comment.
gdb/ChangeLog:

	* symtab.h (struct symtab) <next>: Fix comment.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Tweak ppc32 tls_get_addr optimisation
@ 2015-02-28 16:12 sergiodj+buildbot
  2015-03-03  2:01 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-02-28 16:12 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f01f1741df37f0330fbf2809df0ffddc992ff60c ***

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

Tweak ppc32 tls_get_addr optimisation
This patch is cosmetic.  It prevents references to __tls_get_addr_opt
(an alias for __tls_get_addr) when the optimisation isn't possible.

	* elf32-ppc.c (ppc_elf_tls_setup): Set no_tls_get_addr_opt if
	not PLT_NEW.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Fix Python 3 build: rename GdbMethods
@ 2015-02-28 15:42 sergiodj+buildbot
  2015-03-03  1:38 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-02-28 15:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 02e62830e26a0d3c0d47d4e09209cc04354765a6 ***

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

Fix Python 3 build: rename GdbMethods
Rename forgotten GdbMethods to python_GdbMethods.

gdb/ChangeLog:

	* python/python.c (python_GdbModuleDef): Rename GdbMethods to
	python_GdbMethods.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Move exception_none to common code, and use it
@ 2015-02-28 13:26 sergiodj+buildbot
  2015-03-02 19:36 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-02-28 13:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ad6aff7dead678cc0fa4f786fa59c6040c6fa758 ***

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

Move exception_none to common code, and use it
gdb/ChangeLog:
2015-02-27  Pedro Alves  <palves@redhat.com>

	* common/common-exceptions.h (exception_none): Declare.
	* common/common-exceptions.c (exception_none): Moved from
	exceptions.c.
	(exceptions_state_mc_init): Use exception_none.
	* exceptions.c (exception_none): Move to
	common/common-exceptions.c.
	* exceptions.h (exception_none): Move to
	common/common-exceptions.h.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Don't forward declare enum target_hw_bp_type
@ 2015-02-28  3:24 sergiodj+buildbot
  2015-03-02  9:05 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-02-28  3:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2f56f7c302c8d4012cc47d8bd261b151b2ddfa22 ***

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

Don't forward declare enum target_hw_bp_type
Can't do that in C++.

2015-02-27  Pedro Alves  <palves@redhat.com>

	* nat/x86-dregs.h (enum target_hw_bp_type): Remove forward
	declaration.
	Include break-common.h.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] proc-service, extern "C"
@ 2015-02-28  1:34 sergiodj+buildbot
  2015-03-02  2:25 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-02-28  1:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 749bab0110ddc56835bfe70765675577e3dea05a ***

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

proc-service, extern "C"
libthread_db.so calls symbols in the client (GDB), through the
proc-service interface.  These routines must have extern "C" linkage
so their symbol names are not mangled when GDB is built as a C++
program.  On the GDBserver side, we were missing fallback declarations for
all these symbols.

gdb/ChangeLog:
2015-02-27  Pedro Alves  <palves@redhat.com>

	* gdb_proc_service.h: Wrap with EXTERN_C_PUSH/EXTERN_C_POP.

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

	* gdb_proc_service.h: Wrap with EXTERN_C_PUSH/EXTERN_C_POP.
	[!HAVE_PROC_SERVICE_H] (struct ps_prochandle): Forward declare.
	[!HAVE_PROC_SERVICE_H] (ps_pdread, ps_pdwrite, ps_ptread)
	ps_ptwrite, ps_lgetregs, ps_lsetregs, ps_lgetfpregs)
	(ps_lsetfpregs, ps_getpid)
	(ps_get_thread_area, ps_pglobal_lookup, ps_pstop, ps_pcontinue)
	(ps_lstop, ps_lcontinue, ps_lgetxregsize, ps_lgetxregs)
	(ps_lsetxregs, ps_plog): Declare.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Make functions and variables exported by the IPA be extern "C"
@ 2015-02-28  0:39 sergiodj+buildbot
  2015-03-02  1:13 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-02-28  0:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3c14e5a39bb4fddd911ba49483c44a12294ae6ef ***

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

Make functions and variables exported by the IPA be extern "C"
Functions and variables that are exported by the IPA DSO (that
GDBserver needs to look up) should have "C" mangling, thus be declared
with extern "C".

Function and variable declarations need the extern "C" marker, but
variable definitions can't be marked extern, so the patch splits
IP_AGENT_EXPORT into three.

Building in C++ mode revealed that a few variables were missing
IP_AGENT_EXPORT, thus the IPA has been broken when stripped, even in C
mode...  So this ends being a bug fix as well.

gdb/ChangeLog:
2015-02-27  Pedro Alves  <palves@redhat.com>

	* common/agent.h (IPA_SYM_EXPORTED_NAME): New.
	(IPA_SYM): Use it.
	* common/common-defs.h (EXTERN_C_PUSH, EXTERN_C_POP): New macros.

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

	* linux-amd64-ipa.c (gdb_agent_get_raw_reg): Use
	IP_AGENT_EXPORT_FUNC.
	* linux-i386-ipa.c (gdb_agent_get_raw_reg): Use
	IP_AGENT_EXPORT_FUNC.
	* tracepoint.c (ATTR_USED, ATTR_NOINLINE, ATTR_CONSTRUCTOR)
	(IP_AGENT_EXPORT): Delete.
	(gdb_tp_heap_buffer, gdb_jump_pad_buffer, gdb_jump_pad_buffer_end)
	(gdb_trampoline_buffer, gdb_trampoline_buffer_end)
	(gdb_trampoline_buffer_error, collecting, gdb_collect)
	(stop_tracing, flush_trace_buffer, about_to_request_buffer_space)
	(trace_buffer_is_full, stopping_tracepoint, expr_eval_result)
	(error_tracepoint, tracepoints, tracing, trace_buffer_ctrl)
	(trace_buffer_ctrl_curr, trace_buffer_lo, trace_buffer_hi)
	(traceframe_read_count, traceframe_write_count)
	(traceframes_created, trace_state_variables, get_raw_reg)
	(get_trace_state_variable_value, set_trace_state_variable_value)
	(ust_loaded, helper_thread_id, cmd_buf): Use
	IPA_SYM_EXPORTED_NAME.
	(stop_tracing, flush_trace_buffer): Use IP_AGENT_EXPORT_FUNC.
	(tracepoints) Use IP_AGENT_EXPORT_VAR.
	(stopping_tracepoint, trace_buffer_is_full, expr_eval_result): Use
	IP_AGENT_EXPORT_VAR and wrap in EXTERN_C_PUSH/EXTERN_C_POP.
	(last_tracepoint): Move into !IN_PROCESS_AGENT block.
	(error_tracepoint): Use IP_AGENT_EXPORT_VAR and wrap in
	EXTERN_C_PUSH/EXTERN_C_POP.
	(trace_state_variables): Use IP_AGENT_EXPORT_VAR.
	(trace_buffer_lo, trace_buffer_hi): Use IP_AGENT_EXPORT_VAR and
	wrap in EXTERN_C_PUSH/EXTERN_C_POP.
	(trace_buffer_ctrl, trace_buffer_ctrl_curr)
	(traceframe_write_count, traceframe_read_count)
	(traceframes_created, tracing): Use IP_AGENT_EXPORT_VAR.
	(about_to_request_buffer_space, get_trace_state_variable_value)
	(set_trace_state_variable_value): Use IP_AGENT_EXPORT_FUNC.
	(collecting): Use IP_AGENT_EXPORT_VAR and wrap in
	EXTERN_C_PUSH/EXTERN_C_POP.
	(gdb_collect): Use IP_AGENT_EXPORT_FUNC.
	(ust_loaded, cmd_buf): Use IP_AGENT_EXPORT_VAR.
	(helper_thread_id, gdb_agent_capability): Use IP_AGENT_EXPORT_VAR
	and wrap in EXTERN_C_PUSH/EXTERN_C_POP.
	(gdb_tp_heap_buffer, gdb_jump_pad_buffer, gdb_jump_pad_buffer_end)
	(gdb_trampoline_buffer, gdb_trampoline_buffer_end)
	(gdb_trampoline_buffer_error): Use IP_AGENT_EXPORT_VAR.
	* tracepoint.h (ATTR_USED, ATTR_NOINLINE, EXPORTED_SYMBOL):
	Define.
	(IP_AGENT_EXPORT_FUNC, IP_AGENT_EXPORT_VAR)
	(IP_AGENT_EXPORT_VAR_DECL): Define.
	(tracing): Declare.
	(gdb_agent_get_raw_reg): Declare.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Add extern "C" to declarations of C symbols
@ 2015-02-27 23:46 sergiodj+buildbot
  2015-03-01 23:52 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-02-27 23:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 56000a9801956afa7622249f114da778afc8887f ***

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

Add extern "C" to declarations of C symbols
These symbols are defined in C code, so in C++ mode we need to use
extern "C" to declare them.  As extern "C" can't be used inside a
function's scope, we move the declarations to the global scope at the
same time.

gdb/ChangeLog:
2015-02-27  Pedro Alves  <palves@redhat.com>

	* cli-out.c (_rl_erase_entire_line): Move declaration out of
	cli_mld_erase_entire_line, and make it extern "C".
	* common/common-defs.h (EXTERN_C): New.
	* completer.c (_rl_completion_prefix_display_length)
	(_rl_print_completions_horizontally, QSFUNC): Move declarations
	out of gdb_display_match_list_1.
	(_rl_qsort_string_compare): Move declaration out of
	gdb_display_match_list_1, and make it extern "C".
	* defs.h (re_comp): Use EXTERN_C.
	* maint.c (_mcleanup): Move declaration out of mcleanup_wrapper,
	and make it extern "C".
	(monstartup): Move declaration out of maintenance_set_profile_cmd,
	and make it extern "C".
	(main): Move declaration out of maintenance_set_profile_cmd.
	* nat/linux-ptrace.c (linux_ptrace_attach_fail_reason_string): Use
	EXTERN_C.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] C++ keyword cleanliness, mostly auto-generated
@ 2015-02-27 20:01 sergiodj+buildbot
  2015-03-01 16:01 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-02-27 20:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fe978cb071b460b2d4aed2f9a71d895f84efce0e ***

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

C++ keyword cleanliness, mostly auto-generated
This patch renames symbols that happen to have names which are
reserved keywords in C++.

Most of this was generated with Tromey's cxx-conversion.el script.
Some places where later hand massaged a bit, to fix formatting, etc.
And this was rebased several times meanwhile, along with re-running
the script, so re-running the script from scratch probably does not
result in the exact same output.  I don't think that matters anyway.

gdb/
2015-02-27  Tom Tromey  <tromey@redhat.com>
	    Pedro Alves  <palves@redhat.com>

	Rename symbols whose names are reserved C++ keywords throughout.

gdb/gdbserver/
2015-02-27  Tom Tromey  <tromey@redhat.com>
	    Pedro Alves  <palves@redhat.com>

	Rename symbols whose names are reserved C++ keywords throughout.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Add "../lib/unbuffer_output.c" and use it in gdb.base/interrupt.c
@ 2015-02-27 15:49 sergiodj+buildbot
  2015-03-01  1:21 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-02-27 15:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6f98576f29a70ed947f102015df0388bccc6aa1a ***

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

Add "../lib/unbuffer_output.c" and use it in gdb.base/interrupt.c
In some scenarios, GDB or GDBserver can be spawned with input _not_
connected to a tty, and then tests that rely on stdio fail with
timeouts, because the inferior's stdout and stderr streams end up
fully buffered.

See discussion here:
  https://sourceware.org/ml/gdb-patches/2015-02/msg00809.html

We have a hack in place that works around this for Windows testing,
that forces every test program to link with an .o file that does
(lib/set_unbuffered_mode.c):

 static int __gdb_set_unbuffered_output (void) __attribute__ ((constructor));
 static int
 __gdb_set_unbuffered_output (void)
 {
   setvbuf (stdout, NULL, _IONBF, BUFSIZ);
   setvbuf (stderr, NULL, _IONBF, BUFSIZ);
 }

That's a bit hacky; it ends up done for _all_ tests.

This patch adds a way to do this unbuffering explicitly from the test
code itself, so it is done only when necessary, and for all
targets/hosts.  For starters, it adjusts gdb.base/interrupt.c to use
it.

Tested on x86_64 Fedora 20, native, and against a remote gdbserver
board file that connects to the target with ssh, with and without -t
(create pty).

gdb/testsuite/
2015-02-27  Pedro Alves  <palves@redhat.com>

	* lib/unbuffer_output.c: New file.
	* gdb.base/interrupt.c: Include "../lib/unbuffer_output.c".
	(main): Call gdb_unbuffer_output.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Don't skip catch-syscall.exp on hppa*-hp-hpux* target
@ 2015-02-27 15:33 sergiodj+buildbot
  2015-02-28 23:13 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-02-27 15:33 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT eba5ab56cf54396325f855a39654964bb9e28a9c ***

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

Don't skip catch-syscall.exp on hppa*-hp-hpux* target
As far as I know, "catch syscall" is supported on hppa*-hp-hpux*, but
the test catch-syscall.exp is skipped on this target by mistake.  This
patch is to fix it.  However, I don't have a hpux machine to test.

gdb/testsuite:

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

	* gdb.base/catch-syscall.exp: Don't skip it on hppa*-hp-hpux*
	target.


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Regenerate bfd-in2.h and libbfd.h
@ 2015-02-27 14:07 sergiodj+buildbot
  2015-02-28 21:37 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-02-27 14:07 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 96c20bc18d71ca5ae3335d48ff2b459d495032d3 ***

Author: Marcus Shawcroft <marcus.shawcroft@arm.com>
Branch: master
Commit: 96c20bc18d71ca5ae3335d48ff2b459d495032d3

Regenerate bfd-in2.h and libbfd.h


^ permalink raw reply	[flat|nested] 1132+ messages in thread
* [binutils-gdb] Fixes problems building the V850 simulator introduced with the previous delta.
@ 2015-02-27 10:42 sergiodj+buildbot
  2015-02-28 20:16 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1132+ messages in thread
From: sergiodj+buildbot @ 2015-02-27 10:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a3976a7c56ec803f6ba141576cc56afe02663a8a ***

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

Fixes problems building the V850 simulator introduced with the previous delta.
	* sim-main.h (reg64_t): New type.
	(v850_regs): Add selID_sregs field.
	(VR, SAT16, SAT32, ABS16, ABS32 ): New macros.
	* v850-dc: Add fields for v850e3v5 instructions.
	* v850.igen (cvtf.dl): Use correctly signed local value.
	(cvtf.dw, cvtf.sw, trncf.dul, trncf.dl, trncf.sul, trncf.sw):
	Likewise.
	* interp.c: Fix old style function declarations.
	* simops.c: Likewise.


^ permalink raw reply	[flat|nested] 1132+ messages in thread

end of thread, other threads:[~2016-03-19 14:41 UTC | newest]

Thread overview: 1132+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-03-17 10:26 [binutils-gdb] S390: Add syscall info for syscalls up to 374 sergiodj+buildbot
2016-03-17 10:29 ` Failures on AIX-POWER7-plain, branch master sergiodj+buildbot
2016-03-17 11:02 ` Failures on RHEL-s390x-m64, " sergiodj+buildbot
2016-03-17 19:38 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot
2016-03-17 19:43 ` Failures on Fedora-i686, " sergiodj+buildbot
2016-03-17 20:11 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot
2016-03-17 20:26 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot
2016-03-17 20:58 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-03-17 21:20 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot
2016-03-17 21:32 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot
2016-03-17 21:35 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot
2016-03-17 22:35 ` Failures on Fedora-s390x-m64, " sergiodj+buildbot
2016-03-17 23:47 ` Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot
2016-03-17 23:59 ` Failures on Debian-s390x-m64, " sergiodj+buildbot
2016-03-18  0:33 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-03-18  1:59 ` Failures on Fedora-ppc64be-cc-with-index, " sergiodj+buildbot
2016-03-18  2:20 ` Failures on Fedora-ppc64be-m64, " sergiodj+buildbot
2016-03-18  2:37 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj+buildbot
2016-03-18  3:14 ` Failures on Fedora-ppc64be-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-03-18  4:11 ` Failures on Debian-i686, " sergiodj+buildbot
2016-03-18  5:11 ` Failures on Debian-i686-native-extended-gdbserver, " sergiodj+buildbot
2016-03-18  5:31 ` Failures on Fedora-ppc64le-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-03-18  6:05 ` Failures on Fedora-ppc64le-native-gdbserver-m64, " sergiodj+buildbot
2016-03-18  6:57 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-03-18  7:45 ` Failures on Debian-x86_64-native-gdbserver-m64, " sergiodj+buildbot
  -- strict thread matches above, loose matches on Subject: below --
2016-03-18 16:52 [binutils-gdb] [spu] throw error when target_read_memory fails sergiodj+buildbot
2016-03-19 16:13 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-03-18 15:06 [binutils-gdb] Set signal to 0 after enqueue_pending_signal sergiodj+buildbot
2016-03-19 13:13 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-03-18 14:39 [binutils-gdb] Remove redundant WIFSTOPPED check sergiodj+buildbot
2016-03-19  3:58 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-03-17 23:01 [binutils-gdb] Add mips and s390 build targets for gold sergiodj+buildbot
2016-03-18 13:21 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-03-17 10:12 [binutils-gdb] S390: Fix output path for s390-multiarch test case sergiodj+buildbot
2016-03-18  6:48 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-03-17  9:34 [binutils-gdb] linux-record.c: Fix whitespace issues sergiodj+buildbot
2016-03-18  4:02 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-03-17  9:19 [binutils-gdb] linux-record: Fix bad fall-through for pipe/pipe2 sergiodj+buildbot
2016-03-18  2:47 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-03-16 22:29 [binutils-gdb] PR remote/19496, interrupted syscall in forking-threads-plus-bkpt sergiodj+buildbot
2016-03-18  1:16 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-03-16 19:42 [binutils-gdb] Process record: Fix arm-linux syscall arguments sergiodj+buildbot
2016-03-16 23:37 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-03-16 17:23 [binutils-gdb] PR 18303, Tolerate malformed input for lookup_symbol-called functions sergiodj+buildbot
2016-03-16 17:24 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-03-16 16:29 [binutils-gdb] [ARM] Support ARMv8.2 FP16 simd instructions sergiodj+buildbot
2016-03-17 10:58 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-03-15 17:14 [binutils-gdb] Fix PR gdb/19676: Internal error in linux-thread.db.c if /proc not mounted sergiodj+buildbot
2016-03-15 19:55 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-03-15 16:47 [binutils-gdb] Fix PR gdb/19676: Disable displaced stepping if /proc not mounted sergiodj+buildbot
2016-03-15 18:18 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-03-14 20:28 [binutils-gdb] Regenerate bfd-in2.h sergiodj+buildbot
2016-03-14 21:40 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-03-14 16:56 [binutils-gdb] gdb.base/default.exp: Add missing $_as_string to "show convenience" test sergiodj+buildbot
2016-03-14 18:30 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-03-11 10:15 [binutils-gdb] gdb/s390: Fill pseudo register agent expression hooks sergiodj+buildbot
2016-03-11 11:59 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-03-10 22:34 [binutils-gdb] Add $_as_string convenience function sergiodj+buildbot
2016-03-11  6:54 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-03-10 15:43 [binutils-gdb] Mark the i370 target as obsolete sergiodj+buildbot
2016-03-11  5:32 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-03-10  1:30 [binutils-gdb] gdb.trace/tfind.exp: Force call via global entry point on ppc64le sergiodj+buildbot
2016-03-10  7:29 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-03-09 23:54 [binutils-gdb] gdb: Add tracepoint support for powerpc sergiodj+buildbot
2016-03-10 10:10 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-03-09 22:03 [binutils-gdb] gdb.trace/change-loc.exp: Don't depend on tracepoint ordering sergiodj+buildbot
2016-03-10  6:17 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-03-09 21:55 [binutils-gdb] More "Program" -> "Thread NN received signal" testsuite adjustment sergiodj+buildbot
2016-03-11  4:19 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-03-09 21:09 [binutils-gdb] Simplify saved_command_line handling sergiodj+buildbot
2016-03-11  0:27 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-03-09 20:47 [binutils-gdb] Use struct buffer in gdb_readline_no_editing sergiodj+buildbot
2016-03-10 21:42 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-03-09 20:36 [binutils-gdb] gdb_readline -> gdb_readline_no_editing sergiodj+buildbot
2016-03-10 20:13 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-03-09 20:27 [binutils-gdb] Update prompt_for_continue comments sergiodj+buildbot
2016-03-10 18:44 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-03-09 20:06 [binutils-gdb] gdb_readline2 -> gdb_readline_no_editing_callback sergiodj+buildbot
2016-03-10 15:14 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-03-09 19:54 [binutils-gdb] Garbage collect window_hook sergiodj+buildbot
2016-03-10 13:26 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-03-09 18:40 [binutils-gdb] gdb/rs6000: Read backchain as unsigned sergiodj+buildbot
2016-03-10  3:57 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-03-09 18:28 [binutils-gdb] gdb: Add gen_return_address for powerpc sergiodj+buildbot
2016-03-10  2:49 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-03-09 18:02 [binutils-gdb] gdb: Add ax_pseudo_register_collect for powerpc sergiodj+buildbot
2016-03-10  1:31 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-03-09 16:30 [binutils-gdb] S390: Add use of unavailable-stack frame ID sergiodj+buildbot
2016-03-09 23:05 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-03-09 16:19 [binutils-gdb] Avoid spaces in osabi names sergiodj+buildbot
2016-03-09 21:29 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-03-09 16:08 [binutils-gdb] [FR-V] Handle FR300 sergiodj+buildbot
2016-03-09 19:57 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-03-09 15:43 [binutils-gdb] For COFF and COFF/PE targets, skip relocations against absolute symbols sergiodj+buildbot
2016-03-09 17:03 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-03-09  6:37 [binutils-gdb] Allow zero length archive elements sergiodj+buildbot
2016-03-09 10:31 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-03-09  4:57 [binutils-gdb] Don't create dynamic sections when relocatable sergiodj+buildbot
2016-03-09  9:38 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-03-09  4:23 [binutils-gdb] Fix floating conversion buffer overrun when host/target format matches sergiodj+buildbot
2016-03-09  6:48 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-03-09  3:19 [binutils-gdb] Assert that a floating type's length is at least as long as its format sergiodj+buildbot
2016-03-09  5:39 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-03-09  2:37 [binutils-gdb] Fix HP/PA GNU/Linux "long double" format sergiodj+buildbot
2016-03-09  4:14 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-03-08 13:50 [binutils-gdb] Group common symbol checking together sergiodj+buildbot
2016-03-08 16:03 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-03-07 17:40 [binutils-gdb] Allow zero length archive elements sergiodj+buildbot
2016-03-07 21:39 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-03-07 15:51 [binutils-gdb] [AArch64] Create .got section if _GLOBAL_OFFSET_TABLE_ referenced sergiodj+buildbot
2016-03-07 18:42 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-03-07 15:39 [binutils-gdb] Add const qualifiers at various places sergiodj+buildbot
2016-03-07 17:05 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-03-06 22:42 [binutils-gdb] Set executable bit on analyze-racy-logs.py sergiodj+buildbot
2016-03-06 23:54 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-03-06  1:57 [binutils-gdb] Improve analysis of racy testcases sergiodj+buildbot
2016-03-06  3:57 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-03-05 12:31 [binutils-gdb] Fix argument passing for call sergiodj+buildbot
2016-03-06  1:57 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-03-04 17:01 [binutils-gdb] ARM process record: VMOV sergiodj+buildbot
2016-03-04 20:35 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-03-04 16:10 [binutils-gdb] Tweak ARM process record sergiodj+buildbot
2016-03-04 18:57 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-03-04 15:16 [binutils-gdb] feature_to_c.sh: Print help when passing no arguments sergiodj+buildbot
2016-03-04 17:18 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-03-04 14:50 [binutils-gdb] Treat common symbol in executable as definition sergiodj+buildbot
2016-03-04 15:56 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-03-04 11:45 [binutils-gdb] [ARM] Add feature check for ARMv8.1 AdvSIMD instructions sergiodj+buildbot
2016-03-04 12:55 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-03-03 21:03 [binutils-gdb] get_symbols() plugin API tweak to support --start-lib/--end-lib sergiodj+buildbot
2016-03-04  1:20 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-03-03 15:34 [binutils-gdb] Fix bugs in the simulation of the AArch64's ADDP, FADDP, LD1, CCMP and CCMP instructions sergiodj+buildbot
2016-03-03 22:33 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-03-03 10:36 [binutils-gdb] Update comments to start_step_over sergiodj+buildbot
2016-03-03 21:03 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-03-03 10:20 [binutils-gdb] Reformat gdb.base/step-over-syscall.exp sergiodj+buildbot
2016-03-03 17:39 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-03-03 10:00 [binutils-gdb] Step over fork/vfork syscall insn in gdbserver sergiodj+buildbot
2016-03-03 15:08 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-03-03  9:51 [binutils-gdb] Step over syscalll insn with disp-step on and off sergiodj+buildbot
2016-03-03 13:28 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-03-03  9:42 [binutils-gdb] Refactor gdb.base/disp-step-syscall.exp for general step over test sergiodj+buildbot
2016-03-03 12:01 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-03-02 17:42 [binutils-gdb] Call enqueue_pending_signal in linux_resume_one_lwp_throw sergiodj+buildbot
2016-03-03  9:31 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-03-02 17:06 [binutils-gdb] testsuite: Fix timeout issues during print of vla-arrays sergiodj+buildbot
2016-03-03  0:30 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-03-02 16:31 [binutils-gdb] [OBV] gdbserver: Only write ipa_tdesc_idx if agent is actually loaded sergiodj+buildbot
2016-03-03  8:53 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-03-02 16:16 [binutils-gdb] testsuite: Remove unnecessary code in fortran vla-history test sergiodj+buildbot
2016-03-03  7:00 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-03-02 15:53 [binutils-gdb] testsuite: Fix run to main issue introduced by GCC 5.x sergiodj+buildbot
2016-03-02 22:36 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-03-02 15:43 [binutils-gdb] testsuite: Nullify pointers before first usage sergiodj+buildbot
2016-03-02 20:46 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-03-02 15:30 [binutils-gdb] Add new maintainer to Write After Approval sergiodj+buildbot
2016-03-02 18:53 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-03-02 14:03 [binutils-gdb] Regenerate or1k opcodes file sergiodj+buildbot
2016-03-02 15:36 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-03-02  4:03 [binutils-gdb] Regenerate bfd files sergiodj+buildbot
2016-03-02  7:42 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-03-02  3:46 [binutils-gdb] Regenerate rl78 opcodes file sergiodj+buildbot
2016-03-02 14:03 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-03-02  3:28 [binutils-gdb] Fix shift left warning at source sergiodj+buildbot
2016-03-02  5:54 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-03-01 18:47 [binutils-gdb] Fix gdb.trace/ftrace-lock.c compilation sergiodj+buildbot
2016-03-02  0:11 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-03-01 17:53 [binutils-gdb] Fix gdb.threads/watchpoint-fork*.c compilation sergiodj+buildbot
2016-03-01 21:59 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-03-01 17:26 [binutils-gdb] Fix gdb.base/catch-fork-kill.c compilation sergiodj+buildbot
2016-03-01 20:19 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-03-01 15:41 [binutils-gdb] Fix output path for arm-disp-step.exp sergiodj+buildbot
2016-03-01 18:32 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-03-01 15:31 [binutils-gdb] Compile gdb.arch/arm-neon.c with "quiet" sergiodj+buildbot
2016-03-01 17:01 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-03-01 12:05 [binutils-gdb] S390: Fix output path for s390-tdbregs test case sergiodj+buildbot
2016-03-01 15:19 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-02-29 17:29 [binutils-gdb] aarch64-linux process record: more syscalls sergiodj+buildbot
2016-02-29 21:29 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-02-29 16:04 [binutils-gdb] [ARC] Local symbols relocation cleanup sergiodj+buildbot
2016-02-29 18:22 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-02-29 15:24 [binutils-gdb] [ARC] General fixes sergiodj+buildbot
2016-02-29 16:49 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
     [not found] <1ed0c2a4bbe8ad5f5404014a6351b2b74db75577@gdb-build>
2016-02-28 15:24 ` sergiodj+buildbot
2016-02-26 20:30 [binutils-gdb] Add aarch64-*-rtems* target sergiodj+buildbot
2016-02-27 13:29 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-02-26 20:20 [binutils-gdb] Add x86_64-*-rtems* target sergiodj+buildbot
2016-02-27 11:59 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-02-26 18:19 [binutils-gdb] [BFD][AARCH64]Fix MOVW_SABS_G(0, 1, 2) relocation overflow check sergiodj+buildbot
2016-02-27 10:14 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-02-26 17:52 [binutils-gdb] Optimize x86 GOT32X/GOTPCRELX relocations sergiodj+buildbot
2016-02-27  8:35 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-02-26 16:01 [binutils-gdb] Rename gdb.reverse/aarch64.{exp, c} to gdb.reverse/insn-reverse.{exp, c} sergiodj+buildbot
2016-02-26 21:39 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-02-26 16:00 [binutils-gdb] Fix various bugs in arm_record_exreg_ld_st_insn sergiodj+buildbot
2016-02-27  1:31 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-02-26 15:51 [binutils-gdb] Record right reg num of thumb special data instructions sergiodj+buildbot
2016-02-26 23:24 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-02-26 14:51 [binutils-gdb] Properly implement STT_COMMON sergiodj+buildbot
2016-02-26 18:17 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-02-26 13:00 [binutils-gdb] Fix powerpc64 -r --save-restore-funcs sergiodj+buildbot
2016-02-26 14:49 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
     [not found] <ab50308758bfde9ab7b50e6def65e20f0b560702@gdb-build>
2016-02-26 13:00 ` sergiodj+buildbot
     [not found] <ae91f6253926e4dadebcae90772f4f5a5bd06056@gdb-build>
2016-02-25 21:12 ` sergiodj+buildbot
     [not found] <678b48b7cf0bd518ebc234bda98229cc602c2a45@gdb-build>
2016-02-25 18:16 ` sergiodj+buildbot
2016-02-25 17:42 [binutils-gdb] avoid compiler warnings in remote-m32r-sdi.c sergiodj+buildbot
2016-02-26  0:18 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-02-25 17:22 [binutils-gdb] Remove gdb.base/branches.c sergiodj+buildbot
2016-02-25 22:38 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
     [not found] <7337a6f2297cdd91bb852b479b284e5796d62cc9@gdb-build>
2016-02-25 17:04 ` sergiodj+buildbot
2016-02-25 14:46 [binutils-gdb] Map registers to remote numbers when encoding an ax_reg or ax_reg_mask operation sergiodj+buildbot
2016-02-25 15:53 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-02-24 23:37 [binutils-gdb] Update symbol version for symbol from linker script sergiodj+buildbot
2016-02-25  8:17 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-02-24 23:11 [binutils-gdb] Handle MIPS Linux SIGTRAP siginfo.si_code values sergiodj+buildbot
2016-02-25  0:31 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
     [not found] <338435ef105ff51e967571ad073830ec1eb5a4ab@gdb-build>
2016-02-24 22:27 ` sergiodj+buildbot
2016-02-24 19:30 [binutils-gdb] Move tfile-avx.exp to tracefile-pseudo-reg.exp sergiodj+buildbot
2016-02-24 19:50 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-02-24 18:24 [binutils-gdb] Move new skip features to proper section (post 7.11) sergiodj+buildbot
2016-02-24 18:36 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-02-24 17:45 [binutils-gdb] powerpc: Support z-point type in gdbserver sergiodj+buildbot
2016-02-24 17:57 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-02-24 15:09 [binutils-gdb] Revert "ABS32" sergiodj+buildbot
2016-02-24 16:15 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-02-24 14:22 [binutils-gdb] [OPCODES][ARM][1/3]Add armv8.2 fp16 instruction dissembler support sergiodj+buildbot
2016-02-24 16:03 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-02-24 14:12 [binutils-gdb] [OPCODES][ARM]Fix mask for a few coprocessor opcodes sergiodj+buildbot
2016-02-24 15:48 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-02-24 14:09 [binutils-gdb] [OPCODE][ARM]Correct disassembler for cdp/cdp2, mcr/mcr2, mrc/mrc2, ldc/ldc2, stc/stc2 sergiodj+buildbot
2016-02-24 15:30 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-02-24 14:07 [binutils-gdb] ABS32 sergiodj+buildbot
2016-02-24 15:05 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-02-24 13:54 [binutils-gdb] Set plt_got.offset to (bfd_vma) -1 sergiodj+buildbot
2016-02-24 14:31 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-02-24 12:00 [binutils-gdb] Fix logic in exec_file_locate_attach sergiodj+buildbot
2016-02-24 12:43 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-02-24  3:22 [binutils-gdb] Build unavailable-stack frames for tracepoint sergiodj+buildbot
2016-02-24  3:46 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-02-23 21:37 [binutils-gdb] Extend "skip" command to support -file, -gfile, -function, -rfunction sergiodj+buildbot
2016-02-23 23:04 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-02-23 18:34 [binutils-gdb] arm-tdep.c: Remove unused "to" parameters sergiodj+buildbot
2016-02-23 19:52 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-02-23 13:10 [binutils-gdb] Increment the ABIVERSION to 5 for MIPS objects with non-executable stacks sergiodj+buildbot
2016-02-23 14:14 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-02-23 10:48 [binutils-gdb] Fix the genetation of GOT entries for the Microblaze target sergiodj+buildbot
2016-02-23 11:54 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
     [not found] <4000e47e2f3860a85a9023f3fe5950c8cc6fa507@gdb-build>
2016-02-22 20:19 ` sergiodj+buildbot
2016-02-22 13:15 [binutils-gdb] Remove BSF_COMMON from comments sergiodj+buildbot
2016-02-22 16:14 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-02-22 12:34 [binutils-gdb] [AArch64] Remove redundant calculation of plt stub destination for veneer sergiodj+buildbot
2016-02-22 14:53 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-02-21 21:15 [binutils-gdb] Also update recursive call to d_lookup_symbol_imports sergiodj+buildbot
2016-02-21 22:52 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-02-21 20:46 [binutils-gdb] Remove search_parents parameter from d_lookup_symbol_imports sergiodj+buildbot
2016-02-21 21:25 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-02-19 16:10 [binutils-gdb] Prevent a seg-fault in the linker when accessing a specially crafted, corrupt, aout binary sergiodj+buildbot
2016-02-19 18:26 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-02-19 15:34 [binutils-gdb] Fix a seg-fault in the linker when it encounters a corrupt binary containing a reloc with no associated symbol sergiodj+buildbot
2016-02-19 17:05 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-02-18 21:14 [binutils-gdb] Add D support to gdb_default_target_compile sergiodj+buildbot
2016-02-18 23:01 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
     [not found] <f79a3bae8725dfe0e11b04ddfc6e6bc8f23e4e4e@gdb-build>
2016-02-18 20:05 ` sergiodj+buildbot
2016-02-18 19:38 [binutils-gdb] Determine the iteration count based on wallclock instead of user+system time sergiodj+buildbot
2016-02-18 21:39 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-02-18 16:46 [binutils-gdb] Intel MPX bound violation handling sergiodj+buildbot
2016-02-18 18:53 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-02-18 13:17 [binutils-gdb] Remove setup_kfail server/13796 in disp-step-syscall.exp sergiodj+buildbot
2016-02-18 14:57 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-02-18 11:25 [binutils-gdb] Always create dynamic sections for -E/--dynamic-list sergiodj+buildbot
2016-02-18 12:31 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-02-17 19:31 [binutils-gdb] [x86-64] Omit dynamic sections symbols sergiodj+buildbot
2016-02-17 21:05 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-02-17 17:04 [binutils-gdb] Add missing cleanup in exec_file_locate_attach sergiodj+buildbot
2016-02-17 18:13 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-02-16 14:26 [binutils-gdb] Fix cleanup in arm_linux_software_single_step sergiodj+buildbot
2016-02-16 20:43 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-02-16  0:16 [binutils-gdb] Add parentheses to prevent truncated addresses sergiodj+buildbot
2016-02-16 16:22 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-02-15 18:15 [binutils-gdb] Fix more testcases with standard_output_file sergiodj+buildbot
2016-02-16 12:45 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-02-15 11:25 [binutils-gdb] Enhance GAS's .section directive so that it can take numeric values for the flags and type fields. (ELF only) sergiodj+buildbot
2016-02-15 13:06 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-02-15 10:19 [binutils-gdb] Don't print 0x for core_addr_to_string_nz sergiodj+buildbot
2016-02-15 11:36 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-02-12 19:08 [binutils-gdb] i386-biarch-core.exp: Use standard_output_file sergiodj+buildbot
2016-02-12 20:59 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-02-12  9:10 [binutils-gdb] stack: check frame_unwind_caller_id sergiodj+buildbot
2016-02-12 12:45 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
     [not found] <9f5fed7852cae412443957862d759660cfcb3fd5@gdb-build>
2016-02-12  0:48 ` sergiodj+buildbot
2016-02-11 20:15 [binutils-gdb] Add missing quotes to gdb/testsuite/README sergiodj+buildbot
2016-02-12  9:09 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
     [not found] <18d3cec54e1b4fce278dba436484846f8048d7d6@gdb-build>
2016-02-11 20:01 ` sergiodj+buildbot
2016-02-11 18:30 [binutils-gdb] arm-tdep.c: Change type of insn parameters sergiodj+buildbot
2016-02-12  4:31 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
     [not found] <e909d859f5635d66e79fef467da70d6090bfae1b@gdb-build>
2016-02-11 13:58 ` sergiodj+buildbot
2016-02-10 17:06 [binutils-gdb] Clear *VAL in regcache_raw_read_unsigned sergiodj+buildbot
2016-02-11 18:52 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-02-10 12:21 [binutils-gdb] Add support for ARC instruction relaxation in the assembler sergiodj+buildbot
2016-02-11 11:37 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-02-10  0:25 [binutils-gdb] breakpoints/19546: Fix crash after updating breakpoints sergiodj+buildbot
2016-02-10 12:32 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-02-09 23:05 [binutils-gdb] Use string_to_event_location_basic in guile sergiodj+buildbot
2016-02-10 10:08 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-02-09 22:56 [binutils-gdb] python/19506 -- gdb.Breakpoint address location regression sergiodj+buildbot
2016-02-10  4:23 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
     [not found] <8adce0342f5f50aba0154fc56ca59df45b219738@gdb-build>
2016-02-09 17:53 ` sergiodj+buildbot
2016-02-09 12:41 [binutils-gdb] Fix PR19548: Breakpoint re-set inserts breakpoints when it shouldn't sergiodj+buildbot
2016-02-09 19:41 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-02-09 11:06 [binutils-gdb] Add a more helpful warning message to explain why some AArch64 relocations can overflow sergiodj+buildbot
2016-02-09 16:08 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-02-09 10:48 [binutils-gdb] Revert "Add a more helpful warning message to explain why some AArch64 relocations can overflow." sergiodj+buildbot
2016-02-09 13:35 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-02-09 10:38 [binutils-gdb] Fix build breakage sergiodj+buildbot
2016-02-09 12:23 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-02-09  5:24 [binutils-gdb] Fix macro redefinition error on Solaris sergiodj+buildbot
2016-02-09  6:28 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-02-08 19:12 [binutils-gdb] Fix in-tree, parallel running of Ada tests sergiodj+buildbot
2016-02-08 21:19 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-02-05 10:26 [binutils-gdb] Fix formatting of pe-mips.c file sergiodj+buildbot
2016-02-05 12:20 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-02-04 15:57 [binutils-gdb] [testsuite] Remove BASEDIR sergiodj+buildbot
2016-02-04 17:30 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-02-04 10:06 [binutils-gdb] Fix the encoding of the MSP430's RRUX instruction sergiodj+buildbot
2016-02-04 11:06 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-02-03 22:03 [binutils-gdb] MAINTAINERS: Add Thiemo Seufer back, as a past maintainer sergiodj+buildbot
2016-02-03 23:01 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-02-02 21:51 [binutils-gdb] ui-out.c: Remove unused enum sergiodj+buildbot
2016-02-03  0:17 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-02-02 13:44 [binutils-gdb] PowerPC64 ELFv2 entry code sergiodj+buildbot
2016-02-02 20:52 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-02-01 23:59 [binutils-gdb] Don't add DT_NEEDED for unmatched symbol sergiodj+buildbot
2016-02-02 10:29 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-02-01 23:33 [binutils-gdb] gdb.base/skip.exp: Clean up multiple references to same test name sergiodj+buildbot
2016-02-02  1:01 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-02-01 18:23 [binutils-gdb] gdb: New set/show max-value-size command sergiodj+buildbot
2016-02-01 19:24 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-02-01 10:48 [binutils-gdb] Fix NetBSD build with BSD and GNU make(1) sergiodj+buildbot
2016-02-01 11:48 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-01-31 20:38 [binutils-gdb] Fix /usr/bin/ld: final link failed: File truncated error on hppa sergiodj+buildbot
2016-01-31 21:39 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-01-29 20:45 [binutils-gdb] Fix two misleading indentation warnings sergiodj+buildbot
2016-01-29 22:01 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-01-28 21:08 [binutils-gdb] Align dlang demangle tests with libiberty sergiodj+buildbot
2016-01-28 23:29 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-01-28 21:00 [binutils-gdb] Sync libiberty with GCC sergiodj+buildbot
2016-01-28 21:58 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-01-28 14:39 [binutils-gdb] [testsuite] Fix tiemout fail in gdb.fortran/vla-value.exp sergiodj+buildbot
2016-01-28 16:33 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-01-27 19:48 [binutils-gdb] rx: Treat scalars larger than 8 bytes as aggregates in rx_push_dummy_call sergiodj+buildbot
2016-01-27 21:07 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-01-26 14:40 [binutils-gdb] [GDBserver] Use regcache_read_pc in install_software_single_step_breakpoints sergiodj+buildbot
2016-01-26 17:38 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-01-26 14:03 [binutils-gdb] [GDBserver] Check input interrupt after reading in a packet sergiodj+buildbot
2016-01-26 15:04 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-01-25 16:27 [binutils-gdb] Remove new_thread_notify and dead_thread_notify sergiodj+buildbot
2016-01-25 20:17 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-01-25 13:48 [binutils-gdb] Fix PR 19461: strange "info thread" behavior in non-stop sergiodj+buildbot
2016-01-25 16:46 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-01-25 13:32 [binutils-gdb] Move foreach_with_prefix to lib/gdb.exp sergiodj+buildbot
2016-01-25 14:34 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-01-25  9:54 [binutils-gdb] Add missing end-of-comment marker to previous delta. (Doh!) sergiodj+buildbot
2016-01-25 10:57 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-01-25  9:41 [binutils-gdb] Fix memory corruption on Mach-O systems by suppressing a memory tidy up sergiodj+buildbot
2016-01-25  9:50 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-01-22 21:00 [binutils-gdb] testsuite: gdb.gdb/selftest.exp: Drop expected Thread number sergiodj+buildbot
2016-01-22 23:09 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-01-21 14:04 [binutils-gdb] Fix compile time errors building ARC target on a 32-bit host sergiodj+buildbot
2016-01-21 22:46 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-01-21 11:45 [binutils-gdb] gdb: Respect CXXFLAGS when building with C++ compiler sergiodj+buildbot
2016-01-21 20:35 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-01-21 10:33 [binutils-gdb] Fix regression introduced in "break *<EXPR>" by explicit location patches sergiodj+buildbot
2016-01-21 18:24 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-01-21  9:57 [binutils-gdb] Convert macros in elf-linux-core.h to inline functions sergiodj+buildbot
2016-01-21 16:08 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-01-20 18:53 [binutils-gdb] gnu_vector.exp: Respect `should_kfail' for PR 8549 sergiodj+buildbot
2016-01-21 10:06 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-01-20 14:43 [binutils-gdb] [AArch64] Reject invalid immediate operands to MSR UAO sergiodj+buildbot
2016-01-21  7:35 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-01-20 13:05 [binutils-gdb] Add support for an ARM specific 'y' section attribute flag to mark the section as NOREAD sergiodj+buildbot
2016-01-21  2:22 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-01-19 17:09 [binutils-gdb] Add support to readelf for reading FreeBSD ELF core notes sergiodj+buildbot
2016-01-19 23:02 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-01-19 15:37 [binutils-gdb] Add PIC and TLS support to the ARC target sergiodj+buildbot
2016-01-19 16:35 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
     [not found] <bd0a71fa16f668341a9361c695bc3ca44d27b322@gdb-build>
2016-01-19 13:17 ` sergiodj+buildbot
2016-01-18 16:11 [binutils-gdb] Use a 32-bit value to hold the section number in the internal COFF symbol structure sergiodj+buildbot
2016-01-18 20:23 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-01-18 16:03 [binutils-gdb] Fix PR threads/19422 - show which thread caused stop sergiodj+buildbot
2016-01-18 19:16 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-01-18 15:19 [binutils-gdb] Replace some $ARCH_{get, set}_pc with linux_{get, set}_pc_64bit sergiodj+buildbot
2016-01-18 17:55 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-01-18 11:57 [binutils-gdb] Fix gdbserver build failure on targets without fork sergiodj+buildbot
2016-01-18 12:54 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-01-13 18:04 [binutils-gdb] MAINTAINERS: Add Andreas Arnez as s390 target maintainer sergiodj+buildbot
2016-01-13 21:41 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-01-13 11:41 [binutils-gdb] Implement "info threads -gid" sergiodj+buildbot
2016-01-13 18:12 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-01-13 11:38 [binutils-gdb] Centralize thread ID printing sergiodj+buildbot
2016-01-13 15:04 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-01-12 20:34 [binutils-gdb] Implement 'catch syscall' for gdbserver sergiodj+buildbot
2016-01-13  3:38 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-01-12 16:49 [binutils-gdb] Sync top-level btool.m4 with GCC sergiodj+buildbot
2016-01-13  2:27 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-01-12 16:46 [binutils-gdb] [ARM] Support ARMv8.2 RAS extension sergiodj+buildbot
2016-01-13  0:01 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-01-12 16:41 [binutils-gdb] Add cantunwind when unwind info does not match start of section sergiodj+buildbot
2016-01-12 22:54 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-01-12 15:45 [binutils-gdb] gdbserver: use the new gdb warning helpers sergiodj+buildbot
2016-01-12 19:18 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-01-12  6:46 [binutils-gdb] sim: mips: workaround 32-bit addr sign extensions sergiodj+buildbot
2016-01-12  8:08 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-01-11 21:16 [binutils-gdb] testsuite: Fix false FAILs on too long base directory sergiodj+buildbot
2016-01-11 22:32 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-01-11  0:08 [binutils-gdb] sim: move many common settings from CPPFLAGS to config.h sergiodj+buildbot
2016-01-11  6:04 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-01-10 22:20 [binutils-gdb] sim: allow the assert configure option everywhere sergiodj+buildbot
2016-01-10 23:19 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-01-09  9:01 [binutils-gdb] sim: drop common/cconfig.h in favor of a single config.h sergiodj+buildbot
2016-01-09  9:56 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-01-08 19:16 [binutils-gdb] Fix gdb.multi/base.exp testsuite regression sergiodj+buildbot
2016-01-08 20:10 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-01-08  9:58 [binutils-gdb] [ARM] PR ld/19368: Add missing relocation type class for R_ARM_IRELATIVE sergiodj+buildbot
2016-01-08 10:52 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-01-06 18:52 [binutils-gdb] MIPS/include: opcode/mips.h: Add a summary of MIPS16 operand codes sergiodj+buildbot
2016-01-06 19:48 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-01-06 15:34 [binutils-gdb] Make {arm,thumb}_get_next_pcs_raw static sergiodj+buildbot
2016-01-06 17:49 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-01-05 23:03 [binutils-gdb] libiberty: {count, dup, write}argv: constify argv input slightly sergiodj+buildbot
2016-01-06  4:04 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-01-05 22:29 [binutils-gdb] libiberty: Tweak the documentation of libiberty's xcrc32 function sergiodj+buildbot
2016-01-06  2:01 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-01-04 11:04 [binutils-gdb] sim: parse_args: polish getopt error message sergiodj+buildbot
2016-01-04 13:15 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-01-04  3:17 [binutils-gdb] sim: parse_args: display getopt error ourselves sergiodj+buildbot
2016-01-04  5:05 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-01-03  9:29 [binutils-gdb] sim: use libiberty countargv in more places sergiodj+buildbot
2016-01-03 11:12 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-01-03  9:17 [binutils-gdb] sim: nrun: use lbasename sergiodj+buildbot
2016-01-03 10:10 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2016-01-02  8:50 [binutils-gdb] sim: ppc: do not exit when parsing args w/gdb sergiodj+buildbot
2016-01-02  9:44 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-12-31 22:08 [binutils-gdb] opcodes/arc: Support dmb instruction with no operands sergiodj+buildbot
2015-12-31 23:21 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-12-31  2:11 [binutils-gdb] sim: cris/m68hc11: move default endian/alignment to configure sergiodj+buildbot
2015-12-31  3:20 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-12-30 11:14 [binutils-gdb] sim: h8300: simplify h8300_reg_{fetch,store} funcs sergiodj+buildbot
2015-12-30 16:29 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-12-30  8:57 [binutils-gdb] sim: arm/d10v/h8300/m68hc11/microblaze/mips/mn10300/moxie/sh/v850: convert to common sim_{fetch, store}_register sergiodj+buildbot
2015-12-30 11:38 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-12-30  0:30 [binutils-gdb] sim: ppc: track closed state of file descriptors 0, 1, and 2 sergiodj+buildbot
2015-12-30  8:41 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-12-27 20:41 [binutils-gdb] Correct nios2 _gp address computation sergiodj+buildbot
2015-12-27 21:51 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-12-25 18:35 [binutils-gdb] sim: frv: punt WITH_DEVICE support sergiodj+buildbot
2015-12-26 17:12 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-12-25 12:14 [binutils-gdb] sim: cris: migrate from WITH_DEVICES to WITH_HW sergiodj+buildbot
2015-12-26 15:24 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-12-25 11:20 [binutils-gdb] sim: cris: set up sane default path to rvdummy sergiodj+buildbot
2015-12-26 13:19 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-12-25 10:01 [binutils-gdb] sim: drop WITH_ENGINE define sergiodj+buildbot
2015-12-26 11:46 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-12-25  7:29 [binutils-gdb] sim: device_error: punt sergiodj+buildbot
2015-12-26  0:52 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-12-25  5:41 [binutils-gdb] sim: always enable callback memory sergiodj+buildbot
2015-12-26  0:18 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-12-25  3:41 [binutils-gdb] sim: mips: move SIM_QUIET_NAN_NEGATED to sim-main.h sergiodj+buildbot
2015-12-25 20:45 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-12-25  2:24 [binutils-gdb] sim: cris: move option install to sim_open sergiodj+buildbot
2015-12-25 18:45 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-12-25  1:50 [binutils-gdb] sim: h8300: move h8300-specific options out of common code sergiodj+buildbot
2015-12-25 17:23 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-12-24  5:38 [binutils-gdb] [testsuite/Ada] stop using project files when building test programs sergiodj+buildbot
2015-12-24  6:48 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-12-22 16:10 [binutils-gdb] Remove HP-UX reference in foll-vfork.exp sergiodj+buildbot
2015-12-22 22:39 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-12-22 16:03 [binutils-gdb] ARM: Fix exidx coverage for relocatable builds sergiodj+buildbot
2015-12-22 20:59 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-12-22 15:43 [binutils-gdb] gdbserver crash in gdb/gdbserver/thread.c::thread_search_callback sergiodj+buildbot
2015-12-22 19:01 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-12-21 18:02 [binutils-gdb] Remove HP-UX references fom testsuite sergiodj+buildbot
2015-12-21 18:57 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-12-21 16:34 [binutils-gdb] Remove references to HP CC/aCC compiler from testsuite sergiodj+buildbot
2015-12-21 17:52 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
     [not found] <a4e22a5df64a46bc99f737a982c0b9d1e8a45e2b@gdb-build>
2015-12-19 14:06 ` sergiodj+buildbot
2015-12-18 18:50 [binutils-gdb] Add documentation to gdb_compile sergiodj+buildbot
2015-12-20  5:29 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-12-18 17:51 [binutils-gdb] Enable software single stepping for while-stepping actions in GDBServer sergiodj+buildbot
2015-12-20  3:31 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-12-18 16:58 [binutils-gdb] Replace breakpoint_reinsert_addr by get_next_pcs operation in GDBServer sergiodj+buildbot
2015-12-19 22:25 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-12-17 20:12 [binutils-gdb] Update the copyright notices in the affected files sergiodj+buildbot
2015-12-19  8:12 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-12-17 18:36 [binutils-gdb] Skip gdb.base/gdbinit-history.exp on remote hosts sergiodj+buildbot
2015-12-19  4:06 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-12-17 16:37 [binutils-gdb] Target remote mode fork and exec test updates sergiodj+buildbot
2015-12-18 20:58 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-12-17 15:38 [binutils-gdb] Fix PR threads/19354: "info threads" error with multiple inferiors sergiodj+buildbot
2015-12-19 19:24 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-12-17 15:02 [binutils-gdb] [AArch64][PATCH 11/14] Add support for the 2H vector type sergiodj+buildbot
2015-12-18 16:18 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-12-17 10:05 [binutils-gdb] [ARM] Add support for thumb1 pcrop relocations sergiodj+buildbot
2015-12-19 13:15 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-12-17  9:14 [binutils-gdb] Tweak gdb.trace/ftrace.exp for aarch64 sergiodj+buildbot
2015-12-19 11:05 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-12-17  7:40 [binutils-gdb] Add support for RX V2 Instruction Set sergiodj+buildbot
2015-12-19  6:06 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-12-17  7:33 [binutils-gdb] Check for readline support in gdb.base/history-duplicates.exp sergiodj+buildbot
2015-12-19  5:12 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-12-17  7:08 [binutils-gdb] Skip tests that send ctrl-c to GDB if nointerrupts target property is set sergiodj+buildbot
2015-12-19  0:55 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-12-17  6:17 [binutils-gdb] Target remote mode fork and exec event support sergiodj+buildbot
2015-12-18 22:15 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-12-17  5:21 [binutils-gdb] [AArch64][PATCH 8/14] Support FP16 Adv.SIMD Across Lanes instructions sergiodj+buildbot
2015-12-18 13:46 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-12-17  5:06 [binutils-gdb] [AArch64][PATCH 6/14] Support FP16 Vector Indexed Element instructions sergiodj+buildbot
2015-12-18 12:03 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-12-17  4:58 [binutils-gdb] [AArch64][PATCH 5/14] Support FP16 Scalar Two Register Misc. instructions sergiodj+buildbot
2015-12-18 10:44 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-12-17  4:50 [binutils-gdb] [AArch64][PATCH 4/14] Support FP16 Vector Two Register Misc. instructions sergiodj+buildbot
2015-12-18  9:43 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-12-17  4:35 [binutils-gdb] [AArch64][PATCH 2/14] Support ARMv8.2 FP16 Vector Three Same instructions sergiodj+buildbot
2015-12-18  7:12 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-12-17  4:19 [binutils-gdb] [AArch64] Fix errors rebasing the ARMv8.2 AT and system registers patch sergiodj+buildbot
2015-12-18  5:22 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-12-17  3:37 [binutils-gdb] gdb: 'list' command, tweak handling of +/- arguments sergiodj+buildbot
2015-12-17 23:32 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-12-17  3:20 [binutils-gdb] gdb: Small code restructure for list_command sergiodj+buildbot
2015-12-17 20:47 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-12-17  3:12 [binutils-gdb] gdb: Use NULL instead of 0 for pointer comparison sergiodj+buildbot
2015-12-17 19:26 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-12-17  3:07 [binutils-gdb] gdb: Make lines_to_list variable static sergiodj+buildbot
2015-12-17 18:19 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-12-17  2:31 [binutils-gdb] [AArch64][Patch 5/5] Add instruction PSB CSYNC sergiodj+buildbot
2015-12-17 13:51 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-12-17  2:22 [binutils-gdb] [AArch64][Patch 4/5] Support HINT aliases taking operands sergiodj+buildbot
2015-12-17 12:49 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-12-17  1:57 [binutils-gdb] [AArch64][Patch 1/5] Support the ARMv8.2 Statistical Profiling Extension sergiodj+buildbot
2015-12-17  9:44 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-12-17  1:31 [binutils-gdb] [Aarch64] Support ARMv8.2 AT instructions sergiodj+buildbot
2015-12-17  6:42 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-12-10 16:00 [binutils-gdb] Remove support for thread events without PTRACE_EVENT_CLONE in GDB sergiodj+buildbot
2015-12-10 19:06 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-12-10 14:57 [binutils-gdb] [AArch64][PATCH 1/2] Add support for RAS instruction ESB sergiodj+buildbot
2015-12-10 16:28 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-12-10 10:15 [binutils-gdb] gdb: Handle multiple base address in debug_ranges data sergiodj+buildbot
2015-12-10 11:05 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
     [not found] <8eab413676a0222a863f45ff606f3db69bb7afc4@gdb-build>
2015-12-09 17:13 ` sergiodj+buildbot
2015-12-08  5:32 [binutils-gdb] rl78: Enable MULU for all ISAs sergiodj+buildbot
2015-12-08  6:27 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-12-07 16:13 [binutils-gdb] Support Z0 packet in AArch64 multi-arch debugging sergiodj+buildbot
2015-12-08  3:05 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-12-07 10:29 [binutils-gdb] Add support for MSP430 F5 hardware multiply sergiodj+buildbot
2015-12-07 21:06 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-12-03 19:14 [binutils-gdb] Remove duplicate arch/arm.h include in linux-arm-low.c sergiodj+buildbot
2015-12-04 11:08 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-12-01 12:47 [binutils-gdb] Run gdb.base/disp-step-syscall.exp for aarch64-linux sergiodj+buildbot
2015-12-02  8:14 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-12-01  7:49 [binutils-gdb] Trim unused params from aout adjust_sizes_and_vmas sergiodj+buildbot
2015-12-02  7:16 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-12-01  4:06 [binutils-gdb] Fix instruction skipping when using software single step in GDBServer sergiodj+buildbot
2015-12-01 18:48 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-12-01  3:33 [binutils-gdb] SRC-POTFILES.in update sergiodj+buildbot
2015-12-02  1:02 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-12-01  3:20 [binutils-gdb] Re: ARC port broken reloc processing sergiodj+buildbot
2015-12-01 23:58 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-11-30 22:32 [binutils-gdb] gdbserver crash if gdb attaches too fast sergiodj+buildbot
2015-12-01  6:06 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-11-30 21:45 [binutils-gdb] Implement TARGET_WAITKIND_NO_RESUMED in the remote protocol sergiodj+buildbot
2015-12-01 13:04 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-11-30 21:14 [binutils-gdb] Remote thread create/exit events sergiodj+buildbot
2015-12-01  9:02 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-11-30 20:36 [binutils-gdb] remote: stop reason and watchpoint data address per thread sergiodj+buildbot
2015-12-01  4:14 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-11-28 18:15 [binutils-gdb] Adjust GDB to demangler API change sergiodj+buildbot
2015-11-29  5:04 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-11-28 18:00 [binutils-gdb] SH FDPIC backend support sergiodj+buildbot
2015-11-29  2:01 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-11-28 17:44 [binutils-gdb] PR other/61321 - demangler crash on casts in template parameters sergiodj+buildbot
2015-11-29  0:57 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-11-28 16:50 [binutils-gdb] Avoid "enum conversion when passing argument 1 of 'getrusage' is invalid in C++" warning sergiodj+buildbot
2015-11-28 17:49 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
     [not found] <e19616610d7327664f99215a69cb326682742dc3@gdb-build>
2015-11-28  2:03 ` sergiodj+buildbot
2015-11-27 19:07 [binutils-gdb] [AArch64][PATCH 1/3] Support ARMv8.2 FP16 floating point instructions sergiodj+buildbot
2015-11-28 14:40 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-11-27 18:23 [binutils-gdb] [AArch64] Add ARMv8.2 instructions BFC and REV64 sergiodj+buildbot
2015-11-28 14:18 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-11-27 15:57 [binutils-gdb] [AArch64] Only check breakpoint alignment on inserting sergiodj+buildbot
2015-11-27 22:48 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-11-27 15:24 [binutils-gdb] Use multi_line to make pattern more human readable sergiodj+buildbot
2015-11-27 18:45 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-11-26 10:35 [binutils-gdb] btrace: diagnose "record btrace pt" without libipt sergiodj+buildbot
2015-11-26 12:29 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-11-24 19:29 [binutils-gdb] NEWS: "info" commands now list in ascending order sergiodj+buildbot
2015-11-25 15:18 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-11-24 18:58 [binutils-gdb] Linux: dump the signalled thread first sergiodj+buildbot
2015-11-24 21:02 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-11-24  0:05 [binutils-gdb] Refactor gdb.trace/save-trace.exp sergiodj+buildbot
2015-11-24 12:58 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-11-23 23:05 [binutils-gdb] minsyms.c: Scan backwards over all zero sized symbols sergiodj+buildbot
2015-11-24  8:03 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-11-23 18:24 [binutils-gdb] [LynxOS] GDBserver crash debugging threaded program sergiodj+buildbot
2015-11-23 23:05 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-11-23 18:03 [binutils-gdb] [gdbserver] disable Elf32_auxv_t/Elf64_auxv_t AC_CHECK_TYPES check on Android sergiodj+buildbot
2015-11-23 19:54 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-11-23 14:42 [binutils-gdb] darwin-nat: disable sstep cache sergiodj+buildbot
2015-11-23 16:01 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-11-23  1:38 [binutils-gdb] target.h: #include <sys/types.h> sergiodj+buildbot
2015-11-23 10:41 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-11-22  7:11 [binutils-gdb] sim: ppc: avoid use of $< in ordinary rules [PR sim/13834] sergiodj+buildbot
2015-11-22 13:07 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-11-22  7:00 [binutils-gdb] sim: sh: delete global callback/argv sergiodj+buildbot
2015-11-22  9:05 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-11-22  6:50 [binutils-gdb] sim: common: add PRI printf defines sergiodj+buildbot
2015-11-22 12:08 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-11-22  6:11 [binutils-gdb] sim: mn10300: drop global callback handle sergiodj+buildbot
2015-11-22  7:04 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-11-20 16:23 [binutils-gdb] [AArch64] Add support for ARMv8.1 Virtulization Host Extensions sergiodj+buildbot
2015-11-21  6:03 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-11-20 14:07 [binutils-gdb] binutils: add support for arm-*-darwin and aarch64-*-darwin sergiodj+buildbot
2015-11-21  0:37 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
     [not found] <bb82e93484cdd56c67efd52b869a6123b2623f6c@gdb-build>
2015-11-20 13:40 ` sergiodj+buildbot
2015-11-20 13:08 [binutils-gdb] Synchronize PDP11 page size between BFD and LD sergiodj+buildbot
2015-11-21  0:31 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-11-20 10:38 [binutils-gdb] callfuncs.exp: avoid spurious register differences in sparc64 targets sergiodj+buildbot
2015-11-20 22:46 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-11-19 17:51 [binutils-gdb] [C++] Drop -fpermissive hack sergiodj+buildbot
2015-11-20  0:24 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-11-19 15:28 [binutils-gdb] [C++] Default to -Werror in C++ mode too sergiodj+buildbot
2015-11-20  9:45 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-11-19 14:27 [binutils-gdb] Define enum out of the scope of struct sergiodj+buildbot
2015-11-19 17:05 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-11-19 10:20 [binutils-gdb] [S/390] Add null ptr check + port GOTOFF handling from 32 bit over to 64 bit sergiodj+buildbot
2015-11-19 12:52 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-11-18 16:29 [binutils-gdb] Constify value_string sergiodj+buildbot
2015-11-18 19:29 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-11-18 14:59 [binutils-gdb] mach-o: use a per-target reloc canonicalize function sergiodj+buildbot
2015-11-18 16:11 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-11-18 12:02 [binutils-gdb] Fix out of boundary access in pass_in_v sergiodj+buildbot
2015-11-18 12:37 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-11-18 11:52 [binutils-gdb] Prevent looping in archives sergiodj+buildbot
2015-11-18 12:17 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-11-18 11:42 [binutils-gdb] mach-o cleanup: remove useless calls to bfd_seek sergiodj+buildbot
2015-11-18 12:02 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-11-18  4:25 [binutils-gdb] sim: mn10300/v850: drop unused WITH_CORE define sergiodj+buildbot
2015-11-18 10:40 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-11-18  4:18 [binutils-gdb] sim: always enable modulo memory sergiodj+buildbot
2015-11-18 10:02 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-11-17 21:29 [binutils-gdb] [sim/ppc] Fix printf_filtered reference sergiodj+buildbot
2015-11-18  9:44 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-11-17 17:26 [binutils-gdb] Fix gdb.threads/multiple-step-overs.exp fails on arm sergiodj+buildbot
2015-11-18  9:26 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-11-17 17:18 [binutils-gdb] Introduce null_block_symbol sergiodj+buildbot
2015-11-18  9:08 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-11-17 17:09 [binutils-gdb] [C++] Always use setjmp/longjmp for exceptions sergiodj+buildbot
2015-11-18  8:50 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-11-17 17:01 [binutils-gdb] MinGW and attribute format(printf/gnu_printf) sergiodj+buildbot
2015-11-18  8:32 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-11-17 16:37 [binutils-gdb] [C++/mingw] gdbserver: gdb/host signal mixup sergiodj+buildbot
2015-11-18  6:17 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-11-17 15:51 [binutils-gdb] [C++/mingw] gdb-dlfcn.c casts sergiodj+buildbot
2015-11-17 21:07 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-11-17 15:35 [binutils-gdb] [C++/mingw] ser-mingw.c casts sergiodj+buildbot
2015-11-17 19:07 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-11-17 14:43 [binutils-gdb] Convert c_string_type to an enum flags type sergiodj+buildbot
2015-11-17 17:06 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-11-17 13:56 [binutils-gdb] guile disassembly hardcode TARGET_XFER_E_IO sergiodj+buildbot
2015-11-17 15:06 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-11-16 15:47 [binutils-gdb] Fix stack buffer overflow in aarch64_extract_return_value sergiodj+buildbot
2015-11-16 22:06 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-11-16  7:53 [binutils-gdb] sim: sim-stop/sim-reason/sim-reg: move to common obj list sergiodj+buildbot
2015-11-16 18:09 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-11-16  3:55 [binutils-gdb] sim: cr16: convert to common sim engine logic sergiodj+buildbot
2015-11-16 15:19 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-11-16  3:48 [binutils-gdb] sim: cr16: convert to common sim memory modules sergiodj+buildbot
2015-11-16 14:22 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-11-16  3:24 [binutils-gdb] sim: cr16/d10v: drop redundant call to sim_create_inferior sergiodj+buildbot
2015-11-16 10:23 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-11-16  2:24 [binutils-gdb] sim: d10v: convert to common sim engine logic sergiodj+buildbot
2015-11-16  8:19 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-11-15 13:49 [binutils-gdb] sim: mcore: pull cpu state out of global scope sergiodj+buildbot
2015-11-16  5:19 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-11-15  6:14 [binutils-gdb] sim: testsuite: support basic vars in flags sergiodj+buildbot
2015-11-15 20:35 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-11-15  5:51 [binutils-gdb] sim: drop extern C linkage from most sim interface headers sergiodj+buildbot
2015-11-15 16:45 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-11-15  0:35 [binutils-gdb] Bump version to 2.26.51 sergiodj+buildbot
2015-11-15 13:32 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-11-13 15:22 [binutils-gdb] Remove d10v from testsuite sergiodj+buildbot
2015-11-13 17:03 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-11-12  9:25 [binutils-gdb] Use gdb_byte * instead of void * in push_stack_item sergiodj+buildbot
2015-11-12 10:19 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
     [not found] <430e004ef7ecb3f75fc3c6642c9fdfb1d85a3694@gdb-build>
2015-11-11 22:20 ` sergiodj+buildbot
2015-11-11 10:07 [binutils-gdb] gdb: Make use of 'add_info' to create info sub-commands sergiodj+buildbot
2015-11-11 11:53 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-11-11  9:58 [binutils-gdb] gdb: Use class_info when creating info commands sergiodj+buildbot
2015-11-11 10:52 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-11-10 16:17 [binutils-gdb] Update the RX simulator to handle the latest opcode types sergiodj+buildbot
2015-11-10 17:18 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-11-10  7:26 [binutils-gdb] sim: cr16/d10v: localize translation funcs sergiodj+buildbot
2015-11-10 10:33 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-11-09 16:07 [binutils-gdb] Use ELF_STRING_ARM_unwind in arm-tdep.c sergiodj+buildbot
2015-11-09 17:00 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-11-09  8:59 [binutils-gdb] Move copy_u.w to MSA64 ASE, remove copy_u.d sergiodj+buildbot
2015-11-09  9:52 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-11-09  5:01 [binutils-gdb] Copy gnulib obstack files sergiodj+buildbot
2015-11-09  5:47 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-11-07 18:22 [binutils-gdb] gdb.dwarf2: Don't hardcode certain constants in Dwarf::assemble constructs sergiodj+buildbot
2015-11-07 20:24 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-11-05  9:59 [binutils-gdb] Use aarch64_decode_insn in aarch64_analyze_prologue sergiodj+buildbot
2015-11-05 14:30 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-11-05  9:56 [binutils-gdb] Combine aarch64_decode_stp_offset_wb and aarch64_decode_stp_offset sergiodj+buildbot
2015-11-05 14:00 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
     [not found] <1c215b97f9a64d6ba9821e8a0cf0f44526f29d78@gdb-build>
2015-11-04 20:47 ` sergiodj+buildbot
     [not found] <cbec665beba8acf6393a8c93312bdd3a03a0846c@gdb-build>
2015-11-04 18:46 ` sergiodj+buildbot
     [not found] <04248ead1f57204119180022580626e31c165f60@gdb-build>
2015-11-04 14:15 ` sergiodj+buildbot
2015-11-04 10:35 [binutils-gdb] Fix non stopping breakpoint on newer compilers sergiodj+buildbot
2015-11-05  9:47 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-11-04 10:27 [binutils-gdb] Changing compiler flags for MPX tests sergiodj+buildbot
2015-11-05  8:11 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-11-04  8:49 [binutils-gdb] btrace: add instruction-history /s and fix documentation sergiodj+buildbot
2015-11-05  3:44 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
     [not found] <b9559b8bc4b3c0dffaf08569704a0484e1fb8080@gdb-build>
2015-11-03 21:42 ` sergiodj+buildbot
     [not found] <10268a4c0d64b3892397aeaafbc4b91f6a1e0dc8@gdb-build>
2015-10-31 19:16 ` sergiodj+buildbot
     [not found] <c28ebe255ba37f4dcd295cf6a4608424aaeb699f@gdb-build>
2015-10-31 16:56 ` sergiodj+buildbot
2015-10-30 21:44 [binutils-gdb] Simplify gdb.threads/wp-replication.exp on counting HW watchpoints sergiodj+buildbot
2015-10-31 20:52 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
     [not found] <aefb52a69351517dbcfaafca1d21e5431d4119d1@gdb-build>
2015-10-30 21:27 ` sergiodj+buildbot
2015-10-30 12:57 [binutils-gdb] Updated (simplified) Chinese translations for ld, bfd, binutils and gold sergiodj+buildbot
2015-10-30 18:25 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
     [not found] <968bc5cc86bff4ebf89e63bf99db7c7e777d4756@gdb-build>
2015-10-29 22:12 ` sergiodj+buildbot
2015-10-29 18:21 [binutils-gdb] gdbserver/server.c: Cast return value of memmem sergiodj+buildbot
2015-10-30 11:57 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-10-29 17:42 [binutils-gdb] Disable paging when run by Emacs 25.1 and later sergiodj+buildbot
2015-10-30  6:44 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
     [not found] <44a8b4df1d6f5b8096f01787751fd51c42e78fc6@gdb-build>
2015-10-29 15:55 ` sergiodj+buildbot
     [not found] <e3bdafe2bac1672da335fde734b337c5504e5437@gdb-build>
2015-10-29 14:58 ` sergiodj+buildbot
     [not found] <b80c3053162ec5533e120ee4e4ed30296d4c5fb2@gdb-build>
2015-10-28 19:06 ` sergiodj+buildbot
2015-10-28 16:31 [binutils-gdb] Fix a typo in comment in elf32-i386.c sergiodj+buildbot
2015-10-29  0:12 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-10-28 14:07 [binutils-gdb] Fix recent STM324LXX patch to compile on 32-bit hosts sergiodj+buildbot
2015-10-28 22:07 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-10-27 17:03 [binutils-gdb] source.c:openp: save/restore errno sergiodj+buildbot
2015-10-28 16:00 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-10-27 15:17 [binutils-gdb] psymtab.c: Add casts sergiodj+buildbot
2015-10-28 13:58 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-10-27 14:45 [binutils-gdb] Add scm_t_dynwind_flags casts sergiodj+buildbot
2015-10-28  9:59 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-10-27 13:39 [binutils-gdb] ada-lang.h: Add cast in GROW_VECT sergiodj+buildbot
2015-10-28  0:28 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-10-27 13:32 [binutils-gdb] Add --fix-stm32l4xx-629360 to the ARM linker to enable a link-time workaround for a bug in the bus matrix / memory controller for some of the STM32 Cortex-M4 based products (STM32L4xx) sergiodj+buildbot
2015-10-27 23:13 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-10-27  3:35 [binutils-gdb] symtab.h (struct general_symbol_info> <ada_mangled>: Update comment sergiodj+buildbot
2015-10-27 18:55 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-10-26 23:44 [binutils-gdb] Check symbol defined by assignment in linker script sergiodj+buildbot
2015-10-27 14:42 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-10-26 22:10 [binutils-gdb] PR python/18938: source -s foo.py with foo.py a symlink to foo.notpy fails sergiodj+buildbot
2015-10-27 12:45 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-10-26 21:23 [binutils-gdb] Print address map in output of "mt print psymbols" sergiodj+buildbot
2015-10-27  8:05 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-10-26 20:31 [binutils-gdb] Add some casts for building on musl sergiodj+buildbot
2015-10-26 22:02 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-10-26 15:26 [binutils-gdb] Properly convert address load of __start_XXX/__stop_XXX sergiodj+buildbot
2015-10-26 19:01 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-10-26 13:08 [binutils-gdb] gdbscm_memory_port_write: use local variable to avoid adding casts sergiodj+buildbot
2015-10-26 14:48 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-10-25  3:45 [binutils-gdb] tui-data.c: Remove unnecessary casts sergiodj+buildbot
2015-10-25 20:17 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-10-24 22:47 [binutils-gdb] ia64-tdep.c: Remove (void *) casts sergiodj+buildbot
2015-10-24 23:43 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-10-23 21:07 [binutils-gdb] Add cast to observer.sh sergiodj+buildbot
2015-10-23 22:00 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-10-23  8:38 [binutils-gdb] Initialize field insn_count correctly sergiodj+buildbot
2015-10-23 13:52 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
     [not found] <5af9928d44e302b7f68365a0c551f640895366ff@gdb-build>
2015-10-22 20:46 ` sergiodj+buildbot
2015-10-22 16:53 [binutils-gdb] garbage collect gdb/infrun.c:stop_after_trap sergiodj+buildbot
2015-10-23 10:36 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-10-22 16:10 [binutils-gdb] Add cast in nto-tdep.c sergiodj+buildbot
2015-10-23  7:24 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-10-22 14:30 [binutils-gdb] bfd/mmo.c: handle "objcopy --extract-symbols" generating and reading back sergiodj+buildbot
2015-10-22 23:03 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-10-22 12:23 [binutils-gdb] Add "-z call-nop=PADDING" option to ld sergiodj+buildbot
2015-10-22 17:47 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-10-22 12:11 [binutils-gdb] Add R_386_GOT32X support to gas and ld sergiodj+buildbot
2015-10-22 15:44 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-10-22  9:17 [binutils-gdb] S/390: ifunc: Fix PR18841 sergiodj+buildbot
2015-10-22 11:33 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-10-22  8:26 [binutils-gdb] S/390: Get rid of superfluous parameter to s390_elf_allocate_ifunc_dyn_relocs sergiodj+buildbot
2015-10-22  9:18 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-10-21 20:12 [binutils-gdb] Fix accessing a function's fields (parameters) from Python (PR 18073) sergiodj+buildbot
2015-10-22  5:46 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-10-21 17:31 [binutils-gdb] Support software breakpoints for ARM linux in GDBServer sergiodj+buildbot
2015-10-21 22:46 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-10-21 17:05 [binutils-gdb] Adjust timeout in gdb.base/freebpcmd.exp sergiodj+buildbot
2015-10-21 23:37 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-10-21 15:57 [binutils-gdb] Refactor the breakpoint definitions in linux-arm-low.c sergiodj+buildbot
2015-10-21 21:37 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-10-21 15:42 [binutils-gdb] Support breakpoint kinds for software breakpoints in GDBServer sergiodj+buildbot
2015-10-21 19:38 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-10-21 15:35 [binutils-gdb] Add the target_ops needed for software breakpoints in GDBServer sergiodj+buildbot
2015-10-21 18:38 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-10-21 14:47 [binutils-gdb] [nto] Fix nto target stopped by watchpoint sergiodj+buildbot
2015-10-21 15:39 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-10-20 18:50 [binutils-gdb] Fix internal error on DW_OP_bregx(-1) sergiodj+buildbot
2015-10-20 21:07 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-10-20 17:16 [binutils-gdb] [nto] Fixes for nto procfs sergiodj+buildbot
2015-10-20 18:08 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-10-19 13:46 [binutils-gdb] Make GDB wait for events after handling target File-I/O sergiodj+buildbot
2015-10-19 14:38 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-10-19 10:26 [binutils-gdb] Robustify inherit.exp and virtbase.exp sergiodj+buildbot
2015-10-19 11:18 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-10-16 16:01 [binutils-gdb] [nto] Fix nto build sergiodj+buildbot
2015-10-16 17:51 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-10-16 12:22 [binutils-gdb] Convert mov to lea for loading address of local common symbol sergiodj+buildbot
2015-10-16 13:23 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-10-13 22:55 [binutils-gdb] Recognize a few more AIX XCOFF DWARF sections sergiodj+buildbot
2015-10-14  4:01 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-10-13 18:58 [binutils-gdb] ada-lang.c:ada_value_primitive_packed_val: const correctness sergiodj+buildbot
2015-10-13 21:30 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-10-13 18:50 [binutils-gdb] ada-lang.c: malloc/alloca casts for C++ sergiodj+buildbot
2015-10-13 20:30 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-10-13  6:14 [binutils-gdb] Tidy code setting PT_GNU_RELRO p_flags sergiodj+buildbot
2015-10-13 13:10 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
     [not found] <1f713e48f024e964f5a4f5468bc9506dac262763@gdb-build>
2015-10-13  4:57 ` sergiodj+buildbot
2015-10-12 12:01 [binutils-gdb] Mention the change in NEWS sergiodj+buildbot
2015-10-12 22:33 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-10-12 11:53 [binutils-gdb] Rename emit_load_store to aarch64_emit_load_store sergiodj+buildbot
2015-10-12 21:33 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-10-12 11:36 [binutils-gdb] New test case gdb.arch/disp-step-insn-reloc.exp sergiodj+buildbot
2015-10-12 19:35 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-10-12 11:13 [binutils-gdb] Move aarch64_relocate_instruction to arch/aarch64-insn.c sergiodj+buildbot
2015-10-12 16:39 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-10-12 10:32 [binutils-gdb] Forward VALUE_LVAL when avoiding side effects for STRUCTOP_STRUCT sergiodj+buildbot
2015-10-12 11:23 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-10-11 23:20 [binutils-gdb] Ignore references with relocs to discarded sections in .data.rel.ro.local on hppa-linux sergiodj+buildbot
2015-10-12  0:58 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-10-09 22:39 [binutils-gdb] [Ada] ada_unpack_from_contents: Error if target buffer not large enough sergiodj+buildbot
2015-10-10 11:07 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-10-09 22:31 [binutils-gdb] [Ada] Buffer overflow in ada_unpack_from_contents sergiodj+buildbot
2015-10-10 10:07 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-10-09 22:23 [binutils-gdb] make is_scalar_type non-static and use it in ada-lang.c sergiodj+buildbot
2015-10-10  9:10 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-10-09 22:00 [binutils-gdb] Reorder variable declarations in ada_value_primitive_packed_val sergiodj+buildbot
2015-10-10  5:50 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-10-09 14:36 [binutils-gdb] cris: Use enum bfd_endian to represent endianness sergiodj+buildbot
2015-10-09 20:03 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-10-09 13:32 [binutils-gdb] Fix typos in comments sergiodj+buildbot
2015-10-09 15:17 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-10-09 12:07 [binutils-gdb] Fix gdb.base/a2-run.exp race sergiodj+buildbot
2015-10-09 13:03 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-10-08 11:43 [binutils-gdb] Fix compile time warning compiling ARC port sergiodj+buildbot
2015-10-08 12:35 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-10-08  7:41 [binutils-gdb] btrace: fix void return sergiodj+buildbot
2015-10-08  7:52 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-10-07 14:29 [binutils-gdb] Avoid using 'template' C++ keyword sergiodj+buildbot
2015-10-07 14:39 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-10-07 14:11 [binutils-gdb] Wrap include/opcode/aarch64.h in extern "C" for C++ sergiodj+buildbot
2015-10-07 14:21 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-10-07 13:26 [binutils-gdb] New ARC implementation sergiodj+buildbot
2015-10-07 13:49 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-10-02 18:57 [binutils-gdb] [GAS][AARCH64]Add TLSDESC large memory model support sergiodj+buildbot
2015-10-03 16:49 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-10-02 18:50 [binutils-gdb] [BFD][AARCH64]Add TLSGD relaxation support under large memory model sergiodj+buildbot
2015-10-03 15:50 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-10-02 18:19 [binutils-gdb] [GAS][AARCH64]Add BFD_RELOC_AARCH64_TLSGD_MOVW_G0_NC support sergiodj+buildbot
2015-10-03 11:44 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-10-02 17:40 [binutils-gdb] [LD][AARCH64]Add BFD_RELOC_AARCH64_LD64_GOTOFF_LO15 Support sergiodj+buildbot
2015-10-02 20:01 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-10-02 17:31 [binutils-gdb] [GAS][AARCH64]Add BFD_RELOC_AARCH64_MOVW_GOTOFF_G1 Support sergiodj+buildbot
2015-10-02 21:01 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-10-02 15:25 [binutils-gdb] Make aarch64_zero_register_p declaration starts from column one sergiodj+buildbot
2015-10-02 18:04 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-10-02 14:46 [binutils-gdb] [aarch64] expose disas_aarch64_insn and rename it to aarch64_decode_insn sergiodj+buildbot
2015-10-02 16:51 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-10-02 14:38 [binutils-gdb] [aarch64] Remove argument pc from disas_aarch64_insn sergiodj+buildbot
2015-10-02 15:31 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-10-01 13:47 [binutils-gdb] [BFD][AARCH64]Emit single AARCH64_MAP_INSN symbol for the whole plt sergiodj+buildbot
2015-10-01 14:39 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-10-01  5:31 [binutils-gdb] bfd/config.bfd: Drop non-linux non-fdpic stuff from the last change of targ_selvecs of sh*-linux cases sergiodj+buildbot
2015-10-01  6:24 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
     [not found] <017e6bceee1a96d4b57175687560b4d625fdb150@gdb-build>
2015-10-01  3:27 ` sergiodj+buildbot
2015-09-30 18:38 [binutils-gdb] Call strprefix instead of strncmp in event parsing sergiodj+buildbot
2015-09-30 23:37 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-09-30 15:14 [binutils-gdb] py-type.exp: Do not run tests if binary fails to build sergiodj+buildbot
2015-09-30 17:32 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-09-30  6:50 [binutils-gdb] Add fdpic and misc targets to config.bfd for sh*-*-linux* sergiodj+buildbot
2015-09-30 12:59 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-09-30  5:04 [binutils-gdb] sim: ft32: correct simulation of MEMCPY and MEMSET sergiodj+buildbot
2015-09-30  6:49 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-09-30  3:47 [binutils-gdb] Don't use the output section size to copy input section sergiodj+buildbot
2015-09-30  4:27 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-09-29 17:29 [binutils-gdb] Rebase patch #7 sergiodj+buildbot
2015-09-29 21:09 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-09-29 17:05 [binutils-gdb] [FT32] Replace hard-coded instruction patterns with macros sergiodj+buildbot
2015-09-29 20:30 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-09-29 13:41 [binutils-gdb] Add support for extensions in the .machine pseudoop on S/390, e.g. ".machine zEC12+nohtm+vx" sergiodj+buildbot
2015-09-29 16:57 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-09-28 22:09 [binutils-gdb] gdb.base/gcore.c (array_func): Add reference to static_array sergiodj+buildbot
2015-09-29 12:41 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-09-28 19:25 [binutils-gdb] common/filestuff.c (make_cleanup_close): Update comment sergiodj+buildbot
2015-09-28 22:47 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-09-28 18:35 [binutils-gdb] Updare French translation for binutils and German translation for opcodes sergiodj+buildbot
2015-09-28 19:05 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-09-28  2:50 [binutils-gdb] Fix cast of xml_find_attribute's return value sergiodj+buildbot
2015-09-28  4:24 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-09-25 15:17 [binutils-gdb] Correct the generation of OR1K pc-relative relocations sergiodj+buildbot
2015-09-25 19:46 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-09-25  0:35 [binutils-gdb] Accidentally added file. Removed it sergiodj+buildbot
2015-09-25 18:36 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-09-24 23:46 [binutils-gdb] [FT32] Implement pointer to address conversion method sergiodj+buildbot
2015-09-25 15:36 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-09-24  1:12 [binutils-gdb] Allow any size enum in gdb.cp/var-tag.exp sergiodj+buildbot
2015-09-24 23:41 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-09-23 21:13 [binutils-gdb] [Ada] Fix handling of array renamings sergiodj+buildbot
2015-09-24  1:05 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-09-22 17:51 [binutils-gdb] Enhance the RX disassembler to detect and report bad instructions sergiodj+buildbot
2015-09-23  4:26 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-09-22  4:08 [binutils-gdb] Use bfd_get_32 and bfd_put_32 to access ch_type sergiodj+buildbot
2015-09-22 16:05 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-09-21 15:50 [binutils-gdb] Add NEWS entry for fast tracepoint support on aarch64-linux sergiodj+buildbot
2015-09-22 10:24 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-09-21 15:19 [binutils-gdb] Add a gdb.trace test for instruction relocation sergiodj+buildbot
2015-09-22  7:52 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-09-21 15:08 [binutils-gdb] Implement target_emit_ops sergiodj+buildbot
2015-09-22  5:50 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-09-21 14:52 [binutils-gdb] Make aarch64_decode_adrp handle both ADR and ADRP instructions sergiodj+buildbot
2015-09-21 23:18 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-09-20 22:27 [binutils-gdb] dwarf2_compute_name: add fixme, don't use same name as parameter for local sergiodj+buildbot
2015-09-21 14:22 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-09-20 19:59 [binutils-gdb] crash printing non-local variable from nested subprogram sergiodj+buildbot
2015-09-21 12:18 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-09-19  6:25 [binutils-gdb] symtab.h (general_symbol_info) <mangled_lang>: delete and move up only member sergiodj+buildbot
2015-09-21  5:00 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-09-19  0:15 [binutils-gdb] Fix directory prefix in gdb.base/dso2dso.exp sergiodj+buildbot
2015-09-20 19:37 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-09-18 21:29 [binutils-gdb] aarch64 multi-arch (part 3): get thread area sergiodj+buildbot
2015-09-20 12:49 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-09-18 17:03 [binutils-gdb] btrace: temporarily set inferior_ptid in record_btrace_start_replaying sergiodj+buildbot
2015-09-19 11:25 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-09-18 16:29 [binutils-gdb] Require readline for gdb.linespec/explicit.exp tab-completion tests sergiodj+buildbot
2015-09-20 14:50 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-09-18 15:12 [binutils-gdb] target: add to_record_will_replay target method sergiodj+buildbot
2015-09-19 23:42 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-09-18 15:02 [binutils-gdb] btrace: allow full memory and register access for non-replaying threads sergiodj+buildbot
2015-09-19 20:11 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-09-18 14:47 [binutils-gdb] btrace: non-stop sergiodj+buildbot
2015-09-19 16:29 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-09-18 14:15 [binutils-gdb] btrace: resume all requested threads sergiodj+buildbot
2015-09-19  9:43 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-09-18 13:50 [binutils-gdb] btrace: split record_btrace_step_thread sergiodj+buildbot
2015-09-18 22:17 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-09-18  4:32 [binutils-gdb] Remove one unnecessary iteration in insertion sort sergiodj+buildbot
2015-09-18  8:58 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-09-16 17:26 [binutils-gdb] Fix argument to compiled_cond, and add cases for compiled-condition sergiodj+buildbot
2015-09-18  4:21 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-09-16 15:38 [binutils-gdb] Make it easier to debug non-stop-fair-events.exp sergiodj+buildbot
2015-09-18  4:09 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-09-16 15:03 [binutils-gdb] Don't skip gdb.asm/asm-source.exp on aarch64 sergiodj+buildbot
2015-09-18  3:51 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-09-15 21:24 [binutils-gdb] Handle clang naming of function static local variable sergiodj+buildbot
2015-09-17 11:26 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-09-15 18:25 [binutils-gdb] [ppc64le] Use skip_entrypoint for skip_trampoline_code sergiodj+buildbot
2015-09-16 16:46 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-09-15 17:18 [binutils-gdb] Fix typo sergiodj+buildbot
2015-09-16  0:44 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-09-15 13:45 [binutils-gdb] [gdbserver] Rename supports_conditional_breakpoints to supports_hardware_single_step sergiodj+buildbot
2015-09-15 16:40 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-09-15 10:25 [binutils-gdb] aarch64 multi-arch support (part 2): siginfo fixup sergiodj+buildbot
2015-09-15 13:40 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-09-15  9:41 [binutils-gdb] Fix the SH behavior for EF_SH_PIC flag in FDPIC ABI sergiodj+buildbot
2015-09-15 10:23 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-09-14 15:05 [binutils-gdb] [Ada] Fix the evaluation of access to packed array subscript sergiodj+buildbot
2015-09-15  9:38 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-09-14 12:50 [binutils-gdb] btrace, test: remove buffer-size test with unlimited buffer size sergiodj+buildbot
2015-09-14 15:27 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-09-11 18:33 [binutils-gdb] Extended-remote follow-exec sergiodj+buildbot
2015-09-12 17:11 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-09-11 14:43 [binutils-gdb] gdb/18947: [aarch64]Step into shared library is very slow sergiodj+buildbot
2015-09-11 18:26 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-09-10 15:23 [binutils-gdb] Constify variables in ada-lang.c sergiodj+buildbot
2015-09-11 14:39 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-09-10 13:38 [binutils-gdb] S/390: Fix MASK_RIE_R0PI and MASK_RIE_R0PU sergiodj+buildbot
2015-09-11 14:35 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-09-09 19:44 [binutils-gdb] Garbage collect thread continuations sergiodj+buildbot
2015-09-10 15:32 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-09-09 18:53 [binutils-gdb] * gdb.python/py-prettyprint.exp: Check result of run_lang_tests sergiodj+buildbot
2015-09-11  2:13 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-09-09 18:25 [binutils-gdb] Delete enum inferior_event_handler::INF_TIMER sergiodj+buildbot
2015-09-10 18:27 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-09-09 17:48 [binutils-gdb] Replace "struct continuation" mechanism by something more extensible sergiodj+buildbot
2015-09-10  6:30 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-09-09 13:36 [binutils-gdb] [AArch64] Sort IS_AARCH64_TLS_RELAX_RELOC in alphabetic order sergiodj+buildbot
2015-09-09 22:40 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-09-09 12:30 [binutils-gdb] S/390: Remove trailing zeros on 4-bytes opcodes sergiodj+buildbot
2015-09-09 16:42 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-09-09 12:23 [binutils-gdb] S/390: Fix opcode of ppno sergiodj+buildbot
2015-09-09 14:24 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-09-09  2:59 [binutils-gdb] Improve hand-call-in-threads.exp failure handling sergiodj+buildbot
2015-09-09  5:39 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-09-03 16:02 [binutils-gdb] [Ada] Make string_char_type a true TYPE_CODE_CHAR type in Ada sergiodj+buildbot
2015-09-03 18:55 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-09-03  1:19 [binutils-gdb] Use gdbarch obstack to allocate the TYPE_NAME string in arch_type sergiodj+buildbot
2015-09-03  7:34 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-09-03  1:11 [binutils-gdb] Update documentation of function copy_type_recursive sergiodj+buildbot
2015-09-03  5:24 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-09-02 12:24 [binutils-gdb] Rename R_386_irelative to R_386_ext2 sergiodj+buildbot
2015-09-02 13:59 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-09-02  4:42 [binutils-gdb] Initialize variable and silence GCC warning from last commit sergiodj+buildbot
2015-09-02  7:56 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-09-02  4:28 [binutils-gdb] Catching errors on probes-based dynamic linker interface sergiodj+buildbot
2015-09-02  7:12 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-09-01 12:28 [binutils-gdb] Skip PLT for function pointer initialization sergiodj+buildbot
2015-09-01 15:06 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-31  5:16 [binutils-gdb] NDS32 build fixes sergiodj+buildbot
2015-08-31 11:01 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-31  4:32 [binutils-gdb] Make asection->id and asection->index unsigned sergiodj+buildbot
2015-08-31  6:47 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
     [not found] <a40805d4a73532dffc61e33f913e62b93214c998@gdb-build>
2015-08-29  5:49 ` sergiodj+buildbot
2015-08-27 18:07 [binutils-gdb] [Cell/B.E.] Make parse_spufs_run more robust sergiodj+buildbot
2015-08-29 23:30 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-27 17:43 [binutils-gdb] Report UNRESOLVED on failures while detecting Cell/B.E sergiodj+buildbot
2015-08-29 17:18 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-27 13:41 [binutils-gdb] Document non-8-bits addressable memory support in NEWS sergiodj+buildbot
2015-08-29 12:25 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-27  1:37 [binutils-gdb] Don't sort ld -r output relocs on alpha sergiodj+buildbot
2015-08-28 14:29 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-26 21:30 [binutils-gdb] Replace some xmalloc-family functions with XNEW-family ones sergiodj+buildbot
2015-08-28  7:39 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-26 21:28 [binutils-gdb] Fix native follow-exec-mode "new" sergiodj+buildbot
2015-08-28  6:50 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-26 21:20 [binutils-gdb] New test for follow-exec-mode sergiodj+buildbot
2015-08-28  4:27 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-26 14:22 [binutils-gdb] Use stable sort for ld -r relocs sergiodj+buildbot
2015-08-28  0:20 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-25 17:18 [binutils-gdb] Replace assertions with warning messages about ELF binaries containing multiple symbol tables sergiodj+buildbot
2015-08-27 19:51 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-25 16:03 [binutils-gdb] Move aarch64_linux_new_thread to nat/aarch64-linux.c sergiodj+buildbot
2015-08-26 23:41 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-25 13:56 [binutils-gdb] Print tid in debug output of debug_reg_change_callback sergiodj+buildbot
2015-08-27  5:52 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-25 13:03 [binutils-gdb] Use debug_printf in debug_reg_change_callback sergiodj+buildbot
2015-08-26  7:37 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-25 12:13 [binutils-gdb] Move aarch64_linux_prepare_to_resume to nat/aarch64-linux.c sergiodj+buildbot
2015-08-26 21:35 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-25 12:05 [binutils-gdb] Make aarch64_linux_prepare_to_resume the same on GDB and GDBserver sergiodj+buildbot
2015-08-26 19:09 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-25 11:43 [binutils-gdb] Make debug_reg_change_callback the same on GDB and GDBserver sergiodj+buildbot
2015-08-26 12:19 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-25 11:27 [binutils-gdb] Re-indent the code sergiodj+buildbot
2015-08-25 20:35 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-25 11:05 [binutils-gdb] Remove some comments in debug_reg_change_callback sergiodj+buildbot
2015-08-25 22:50 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-25 10:50 [binutils-gdb] [gdbserver] Use iterate_over_lwps in aarch64_notify_debug_reg_change sergiodj+buildbot
2015-08-25 18:29 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-24 19:25 [binutils-gdb] gdbserver crashes when multiprocess extensions aren't supported sergiodj+buildbot
2015-08-25 15:54 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-24 19:17 [binutils-gdb] Add "set remote multiprocess-extensions-packet" command sergiodj+buildbot
2015-08-25 13:48 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-24 18:23 [binutils-gdb] Update gnulib to current upstream master sergiodj+buildbot
2015-08-25 11:37 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-24 10:41 [binutils-gdb] Missing parts of fixes for in-tree libiconv sergiodj+buildbot
2015-08-24 12:55 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-21 20:38 [binutils-gdb] tui: don't overwrite a secondary prompt that was given no input sergiodj+buildbot
2015-08-22 14:05 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-21 19:24 [binutils-gdb] Fix gdbserver crash exposed by gdb.threads/process-dies-while-handling-bp.exp sergiodj+buildbot
2015-08-22 10:37 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-21 18:54 [binutils-gdb] gdbserver: don't pick a random thread if the current thread dies sergiodj+buildbot
2015-08-22  9:22 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-21 11:57 [binutils-gdb] PR binutils/18257: Properly decode x86/Intel mask instructions sergiodj+buildbot
2015-08-21 17:18 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-20 19:30 [binutils-gdb] Fix gdb.server/solib-list.exp native-extended-gdbserver regression sergiodj+buildbot
2015-08-20 21:14 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-20 11:45 [binutils-gdb] Fix language of compilation unit with unknown file extension sergiodj+buildbot
2015-08-20 14:59 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-19 17:46 [binutils-gdb] [AArch64][4/6] LD support TLSLD move/add relocation types sergiodj+buildbot
2015-08-20  0:01 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-19 17:17 [binutils-gdb] [AArch64][3/6] GAS support TLSLD move/add relocation types sergiodj+buildbot
2015-08-19 22:10 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-19 16:42 [binutils-gdb] [AArch64][5/6] GAS support TLSLD load/store relocation types sergiodj+buildbot
2015-08-20  7:32 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-19 16:10 [binutils-gdb] [AArch64][1/6] GAS support BFD_RELOC_AARCH64_TLSLD_ADD_DTPREL_LO12_NC sergiodj+buildbot
2015-08-19 19:06 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-19 13:10 [binutils-gdb] Prelimit number of bytes to read in "vFile:pread:" sergiodj+buildbot
2015-08-19 14:54 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-19  4:02 [binutils-gdb] Remove link_info.pic sergiodj+buildbot
2015-08-19  9:38 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-19  3:57 [binutils-gdb] Add bfd_link_pde, and simplify some tests of link_info.type sergiodj+buildbot
2015-08-19  7:46 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-18 22:51 [binutils-gdb] gdbserver/linux-aarch32-low: build failure when NT_ARM_VFP not defined sergiodj+buildbot
2015-08-19  5:59 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-18 21:13 [binutils-gdb] PR mi/18833 gdb.execute ("set param value", to_string=True) will crash gdb if using MI sergiodj+buildbot
2015-08-19  3:55 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-18 17:42 [binutils-gdb] Fix mis-parsing of hex register numbers in 'T' stop replies sergiodj+buildbot
2015-08-19  0:28 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-18 17:09 [binutils-gdb] Return reloc_class_ifunc for reloc against IFUNC sergiodj+buildbot
2015-08-18 22:59 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-18 13:56 [binutils-gdb] gdb: New maintenance command to disable bfd sharing sergiodj+buildbot
2015-08-18 17:11 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-18 13:12 [binutils-gdb] gdb: Improve cache matching criteria for the bfd cache sergiodj+buildbot
2015-08-18 15:36 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-18  8:05 [binutils-gdb] Use $SED in bfd Makefile sergiodj+buildbot
2015-08-18 10:00 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-17 20:18 [binutils-gdb] ui-out.c (default_ui_out_impl): Add comment sergiodj+buildbot
2015-08-17 23:04 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-17 19:21 [binutils-gdb] Move strace -m/explicit location test to strace.exp sergiodj+buildbot
2015-08-17 20:35 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-16  0:29 [binutils-gdb] Add end_psymtab_common, have all debug info readers call it sergiodj+buildbot
2015-08-17  9:10 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-15 18:05 [binutils-gdb] Fix invoking "[kill|detach] inferiors" on inferiors that are not running sergiodj+buildbot
2015-08-16 20:24 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-15  4:59 [binutils-gdb] New /s modifier for the disassemble command sergiodj+buildbot
2015-08-15 23:39 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-14 22:33 [binutils-gdb] Rename location accessor macro parameters to silence ARI sergiodj+buildbot
2015-08-15 21:15 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-14 14:27 [binutils-gdb] Add support for DT_MIPS_RLD_MAP_REL sergiodj+buildbot
2015-08-15 17:37 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-14 12:24 [binutils-gdb] Add myself to gdb MAINTAINERS sergiodj+buildbot
2015-08-15 15:46 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-14  1:48 [binutils-gdb] Revert "Fix encoding or OpenRisk1000 PC relative relocations." sergiodj+buildbot
2015-08-15  9:25 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-13 20:36 [binutils-gdb] [D] Support looking up symbols in the current and imported modules sergiodj+buildbot
2015-08-14 23:57 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-13 18:17 [binutils-gdb] Fix Python frame unwinder issue caught by Valgrind sergiodj+buildbot
2015-08-13 23:45 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-13 17:22 [binutils-gdb] Mass rename `explicit' -> `explicit_loc' sergiodj+buildbot
2015-08-13 22:34 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-13 10:53 [binutils-gdb] Fixes for unpredictable nops and 26-bit versions of teq, tst, cmn, cmp sergiodj+buildbot
2015-08-13 20:10 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-13  7:47 [binutils-gdb] [Ada] Add support for subprogram renamings sergiodj+buildbot
2015-08-13 18:50 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-13  2:02 [binutils-gdb] gdb.base/dso2dso.exp sometimes broken sergiodj+buildbot
2015-08-13 17:29 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-12 20:32 [binutils-gdb] [amd64] Invalid return address after displaced stepping sergiodj+buildbot
2015-08-13 14:47 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-12 18:48 [binutils-gdb] Initialize `location' in gdbpy_decode_line sergiodj+buildbot
2015-08-13 13:36 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-12 16:46 [binutils-gdb] Guarantee save-and-restore of GDBFLAGS on gdb.base/checkpoint-ns.exp sergiodj+buildbot
2015-08-13 12:23 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-12 16:23 [binutils-gdb] [MIPS] Map 'move' to 'or' sergiodj+buildbot
2015-08-13 11:43 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-12 15:57 [binutils-gdb] Use save_vars to replace existing manipulation of globals in tests sergiodj+buildbot
2015-08-13 11:03 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-12 13:24 [binutils-gdb] Introduce save_vars, a testsuite proc for safely manipulating globals sergiodj+buildbot
2015-08-13 10:21 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-12 12:58 [binutils-gdb] Sync ansidecl.h with GCC sergiodj+buildbot
2015-08-13  9:38 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-12 12:26 [binutils-gdb] Remove trailing spaces in opcodes sergiodj+buildbot
2015-08-13  8:48 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-12 11:58 [binutils-gdb] Remove trailing spaces in bfd sergiodj+buildbot
2015-08-13  7:43 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-12  8:50 [binutils-gdb] [regression] Do not read from catchpoint/watchpoint locations' addresses when checking for a permanent breakpoint sergiodj+buildbot
2015-08-12 23:09 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-12  5:48 [binutils-gdb] Properly skip IFUNC relocations in debug sections sergiodj+buildbot
2015-08-12 22:27 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-12  5:23 [binutils-gdb] Explicit locations: documentation updates sergiodj+buildbot
2015-08-12 21:41 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-12  4:59 [binutils-gdb] Explicit locations: MI support for explicit locations sergiodj+buildbot
2015-08-12 20:58 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-12  4:30 [binutils-gdb] Explicit locations: add UI features for CLI sergiodj+buildbot
2015-08-12 20:16 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-12  4:04 [binutils-gdb] Explicit locations: introduce explicit locations sergiodj+buildbot
2015-08-12 19:36 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-12  3:38 [binutils-gdb] Explicit locations: introduce probe locations sergiodj+buildbot
2015-08-12 18:49 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-12  3:12 [binutils-gdb] Explicit locations: introduce address locations sergiodj+buildbot
2015-08-12 18:06 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-12  2:47 [binutils-gdb] Explicit locations: use new location API sergiodj+buildbot
2015-08-12 17:22 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-12  2:19 [binutils-gdb] Explicit locations: introduce new struct event_location-based API sergiodj+buildbot
2015-08-12 16:42 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-12  1:53 [binutils-gdb] Explicit locations: rename "address string"/"addr_string" to "location" sergiodj+buildbot
2015-08-12 15:25 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-12  0:11 [binutils-gdb] [AArch64] PR18668, repair long branch veneer for plt stub sergiodj+buildbot
2015-08-12 10:13 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-11 23:19 [binutils-gdb] [AArch64][7/8] GAS support BFD_RELOC_AARCH64_TLSLD_ADD_DTPREL_LO12 sergiodj+buildbot
2015-08-12  7:38 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-11 20:42 [binutils-gdb] [AArch64][1/8] Add R_AARCH64_P32_TLSLD_ADR_PAGE21 in elf header sergiodj+buildbot
2015-08-11 22:59 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-11 17:19 [binutils-gdb] Fix the disassembly of the AArch64 SIMD EXT instruction sergiodj+buildbot
2015-08-11 20:13 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-11 16:46 [binutils-gdb] Fix encoding or OpenRisk1000 PC relative relocations sergiodj+buildbot
2015-08-11 18:54 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-11 16:13 [binutils-gdb] Fix typo in coff-sh.c sergiodj+buildbot
2015-08-11 17:43 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-11  7:25 [binutils-gdb] PR gdb/18669 libiberty demangle.test failure: strtod() on sparc-sun-solaris2.9 sergiodj+buildbot
2015-08-11  8:33 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-10 19:25 [binutils-gdb] PR gdb/17960 Internal error: tracker != NULL when completing on file:function sergiodj+buildbot
2015-08-10 20:35 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-10 15:08 [binutils-gdb] Replace hidden with versioned in elf_link_hash_entry sergiodj+buildbot
2015-08-10 16:36 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-10  8:27 [binutils-gdb] Add SIGRIE instruction for MIPS R6 sergiodj+buildbot
2015-08-10 15:22 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-08  0:51 [binutils-gdb] Check sh_type/sh_flags/sh_addralign/sh_entsize when copying sh_link/sh_info sergiodj+buildbot
2015-08-10 13:21 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-07 23:57 [binutils-gdb] S/390: displaced stepping and PC-relative RIL-b/RIL-c instructions sergiodj+buildbot
2015-08-09 23:44 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-07 22:44 [binutils-gdb] Fix step-over-{trips-on-watchpoint|lands-on-breakpoint}.exp race sergiodj+buildbot
2015-08-09 20:07 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-07 22:08 [binutils-gdb] Fix interrupt-noterm.exp on targets always in non-stop sergiodj+buildbot
2015-08-09 18:58 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-07 21:07 [binutils-gdb] Teach non-stop to do in-line step-overs (stop all, step, restart) sergiodj+buildbot
2015-08-09 15:21 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-07 20:23 [binutils-gdb] Factor out code to re-resume stepped thread sergiodj+buildbot
2015-08-09 14:01 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-07 19:58 [binutils-gdb] Add comments to currently_stepping and target_resume sergiodj+buildbot
2015-08-09 12:50 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
     [not found] <33ebda9d6841e18d9ef18b94c3dcad7d0498ab3d@gdb-build>
2015-08-07 19:05 ` sergiodj+buildbot
2015-08-07 19:05 [binutils-gdb] Use keep_going in proceed and start_step_over too sergiodj+buildbot
2015-08-09 10:28 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-07 18:40 [binutils-gdb] Embed the pending step-over chain in thread_info objects sergiodj+buildbot
2015-08-09  8:47 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-07 17:20 [binutils-gdb] Change adjust_pc_after_break's prototype sergiodj+buildbot
2015-08-08 21:13 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-07 15:10 [binutils-gdb] Sync config.sub and config.guess with GCC sergiodj+buildbot
2015-08-08 17:44 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-07 12:17 [binutils-gdb] Properly merge hidden versioned symbol sergiodj+buildbot
2015-08-08 15:19 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-07 11:12 [binutils-gdb] gdb: get_frame_language now takes a frame parameter sergiodj+buildbot
2015-08-08 12:02 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-07  8:34 [binutils-gdb] configure: check for perf_event.h version sergiodj+buildbot
2015-08-08  8:16 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-07  5:32 [binutils-gdb] Yaakov Selkowitz: fixes for in-tree libiconv sergiodj+buildbot
2015-08-07 23:49 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-06 23:28 [binutils-gdb] Bump timeouts for a couple gdb.reverse/*-precsave.exp tests sergiodj+buildbot
2015-08-07 22:38 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-06 18:16 [binutils-gdb] gdbserver: no point in hiding the regcache type nowadays sergiodj+buildbot
2015-08-07 17:52 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-06 16:55 [binutils-gdb] gdbserver: fix silent error exit sergiodj+buildbot
2015-08-07 14:09 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-06 10:34 [binutils-gdb] gdbserver: Fix non-stop / fork / step-over issues sergiodj+buildbot
2015-08-06 16:17 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-04 12:22 [binutils-gdb] signal_command: Leftover cleanup chain regression sergiodj+buildbot
2015-08-04 20:40 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-02 18:22 [binutils-gdb] Complete the previous commit (block_found refactoring) sergiodj+buildbot
2015-08-03 19:00 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-08-01  9:01 [binutils-gdb] Replace the block_found global with explicit data-flow sergiodj+buildbot
2015-08-03 16:56 ` Failures on Debian-x86_64-native-gdbserver-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-03 16:13 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-07-31 18:24 [binutils-gdb] Fix m32r_remove_watchpoint parameter type sergiodj+buildbot
2015-08-03 14:08 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-07-31 17:25 [binutils-gdb] Mostly trivial enum fixes sergiodj+buildbot
2015-08-03 12:04 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-07-30 14:17 [binutils-gdb] Move ARM register numbers enum to arch/arm.h sergiodj+buildbot
2015-08-02 13:11 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-07-30 11:50 [binutils-gdb] [AArch64] Rename boolean arguments in decoding functions sergiodj+buildbot
2015-08-02 10:02 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-07-30  1:24 [binutils-gdb] Make gdb.base/multi-forks.exp work with the native-extended-gdbserver board sergiodj+buildbot
2015-08-01 17:55 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-07-29 18:08 [binutils-gdb] Make gdb.base/shlib-call.exp use gdb_test_stdio sergiodj+buildbot
2015-07-31 21:22 ` Failures on Debian-x86_64-native-gdbserver-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-31  8:53 ` Failures on Debian-x86_64-native-gdbserver-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-30 21:16 ` Failures on Debian-x86_64-native-gdbserver-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 23:15 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-07-28 21:47 [binutils-gdb] Uniquify test names from gdb.python/{py-objfile.exp, py-pp-registration.exp} sergiodj+buildbot
2015-07-29 21:05 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-07-28 16:24 [binutils-gdb] Consider addressable memory unit size in various value functions sergiodj+buildbot
2015-07-29 18:53 ` Failures on Debian-x86_64-native-gdbserver-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 10:37 ` Failures on Debian-x86_64-native-gdbserver-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 22:11 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-07-27 16:26 [binutils-gdb] Remove REMOTE_EXAMPLES from gdb/Makefile.in sergiodj+buildbot
2015-07-27 20:58 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-07-27 15:58 [binutils-gdb] Regenerate configure files sergiodj+buildbot
2015-07-27 19:55 ` Failures on Debian-x86_64-native-gdbserver-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:18 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-07-25  1:28 [binutils-gdb] Add gmonster-{1,2} perf testcases sergiodj+buildbot
2015-07-25 21:34 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-07-25  1:05 [binutils-gdb] Add perf testcase generator sergiodj+buildbot
2015-07-25 19:59 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-07-25  0:40 [binutils-gdb] PerfTest::assemble functions return results sergiodj+buildbot
2015-07-25 18:03 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-07-25  0:14 [binutils-gdb] lib/gdb.exp (clean_restart): Make executable optional sergiodj+buildbot
2015-07-25 16:26 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-07-24 23:49 [binutils-gdb] Clean up testsuite compiler_info support sergiodj+buildbot
2015-07-25 14:48 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-07-24 23:25 [binutils-gdb] Add parallel build support for perf tests sergiodj+buildbot
2015-07-25 13:13 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-07-24  6:05 [binutils-gdb] bfd_get_section_by_name_if hash chain traversal sergiodj+buildbot
2015-07-24  7:26 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-07-22 10:11 [binutils-gdb] Fix ppc64 ELFv1 assertion failure sergiodj+buildbot
2015-07-22 12:07 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-07-20 13:07 [binutils-gdb] Make binutils abort message GDB friendly sergiodj+buildbot
2015-07-20 20:23 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-07-18 17:30 [binutils-gdb] dwarf2read: Allow SEC_ALLOC sections to be located at address 0 sergiodj+buildbot
2015-07-18 19:09 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-07-17 14:32 [binutils-gdb] Use debug_printf to print debug message sergiodj+buildbot
2015-07-17 20:58 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-07-17 11:35 [binutils-gdb] Fix using uninitialised values sergiodj+buildbot
2015-07-17 12:56 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-07-16 15:06 [binutils-gdb] [AArch64][1/3] Add R_AARCH64_P32_TLSLD_ADR_PREL21 in elf header sergiodj+buildbot
2015-07-16 17:15 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-07-15 15:43 [binutils-gdb] Unbreak nios2-*-linux* GDB testing sergiodj+buildbot
2015-07-15 23:41 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-07-14 21:08 [binutils-gdb] Remove CHECK_TYPEDEF, use check_typedef instead sergiodj+buildbot
2015-07-15 16:35 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-07-14 19:13 [binutils-gdb] Add support reading D modules from DWARF sergiodj+buildbot
2015-07-15 14:33 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-07-14 10:02 [binutils-gdb] gdbserver/Linux: internal error when killing a process that is already gone sergiodj+buildbot
2015-07-14 11:03 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-07-10 13:09 [binutils-gdb] [GDBserver][AArch64] Cleanup comments for each linux_target_ops method sergiodj+buildbot
2015-07-11 11:48 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-07-10 12:19 [binutils-gdb] gdb/tui: Define tui window names once sergiodj+buildbot
2015-07-11  8:55 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-07-10  7:25 [binutils-gdb] record: set stop_pc in "record goto" command sergiodj+buildbot
2015-07-11  5:59 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-07-09 19:28 [binutils-gdb] [AArch64] Only access inferior registers when creating a frame cache sergiodj+buildbot
2015-07-10 14:33 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-07-09 18:08 [binutils-gdb] Factor out memberptr printing code from c_val_print sergiodj+buildbot
2015-07-10  9:08 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-07-09 16:47 [binutils-gdb] Factor out array printing code from c_val_print sergiodj+buildbot
2015-07-09 20:16 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-07-09 15:28 [binutils-gdb] 2015-07-09 Catherine Moore <clm@codesourcery.com> sergiodj+buildbot
2015-07-09 16:30 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-07-09  6:23 [binutils-gdb] btrace: fix build fail with 32-bit BFD sergiodj+buildbot
2015-07-09  7:23 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-07-08 15:32 [binutils-gdb] Delete program spaces directly when removing inferiors sergiodj+buildbot
2015-07-08 15:54 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-07-08  8:40 [binutils-gdb] add myself to write-after-approval list sergiodj+buildbot
2015-07-08 10:35 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
     [not found] <a844296a982bdff7c14dab355de0fca75486add6@kwanyin>
2015-07-06 18:13 ` sergiodj+buildbot
     [not found] <0561fea48c107b271308a013c485c29cbd5c13b5@kwanyin>
2015-07-03  2:25 ` sergiodj+buildbot
     [not found] <9be54cae43929ab989fcd44dfcf8d3313a55f7a0@kwanyin>
2015-07-02 17:24 ` sergiodj+buildbot
     [not found] <58bfce93438e1f936d4547bb9659b7d096e2823f@kwanyin>
2015-07-02 12:37 ` sergiodj+buildbot
     [not found] <e62803699d1a722460e8aaa63ef5c99f5580761a@kwanyin>
2015-07-02  6:43 ` sergiodj+buildbot
     [not found] <dfc87947b5ac6d6382c225449d4fdce411c7ee66@kwanyin>
2015-07-01 19:36 ` sergiodj+buildbot
     [not found] <b5fca6d7284b2cd2e90efc556eb6a29a1b177476@kwanyin>
2015-07-01  4:31 ` sergiodj+buildbot
     [not found] <a2efc14b81515aebd2b7e1f47fe4768e432493a9@kwanyin>
2015-06-30 21:58 ` sergiodj+buildbot
2015-06-26 13:34 [binutils-gdb] Do not skip prologue for asm (.S) files sergiodj+buildbot
2015-06-26 15:53 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-06-25 20:28 [binutils-gdb] Don't set sh_size for .shstrtab twice sergiodj+buildbot
2015-06-26  0:22 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-06-24 20:10 [binutils-gdb] Sync libiberty from GCC, replaying updates to configure scripts sergiodj+buildbot
2015-06-25  9:59 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-06-24 15:57 [binutils-gdb] gdb: sim: merge the sysroot update logic together sergiodj+buildbot
2015-06-24 20:30 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-06-24 14:45 [binutils-gdb] Call set_gdbarch_get_siginfo_type in linux_init_abi sergiodj+buildbot
2015-06-24 17:08 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-06-23 22:27 [binutils-gdb] Fix GDBHISTSIZE test failure on i686 sergiodj+buildbot
2015-06-24  8:55 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-06-23 20:03 [binutils-gdb] sim: trace: do not enable internal debug by default sergiodj+buildbot
2015-06-23 22:27 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-06-23 13:26 [binutils-gdb] Convert have_ptrace_getregset to a tri-state boolean sergiodj+buildbot
2015-06-23 15:12 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-06-21  4:20 [binutils-gdb] Don't use $< in Makefiles sergiodj+buildbot
2015-06-21 17:56 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-06-18 17:01 [binutils-gdb] Test the interaction between GDBHISTSIZE and .gdbinit sergiodj+buildbot
2015-06-18 18:53 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-06-18  0:11 [binutils-gdb] Fix problems with finishing a dummy function call on simulators sergiodj+buildbot
2015-06-18 11:45 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-06-17  9:39 [binutils-gdb] Add vector ABI tests to gnu_vector.exp sergiodj+buildbot
2015-06-17 10:53 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-06-16 13:55 [binutils-gdb] Fix build when size_t is not available in bfd-in2.h sergiodj+buildbot
2015-06-16 16:23 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-06-16  9:49 [binutils-gdb] Fix compilation of gdb/arm-linux-nat.c on Raspbian GNU/Linux 7 sergiodj+buildbot
2015-06-16 12:56 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-06-15 16:18 [binutils-gdb] Merge multiple hex conversions sergiodj+buildbot
2015-06-15 20:11 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-06-15 11:29 [binutils-gdb] windows-nat: Replace __COPY_CONTEXT_SIZE conditional with __CYGWIN__ sergiodj+buildbot
2015-06-15 13:23 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-06-12 17:42 [binutils-gdb] sim: bfin: expand CB_SYS_xxx comment sergiodj+buildbot
2015-06-13 15:17 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-06-12 16:25 [binutils-gdb] sim: drop -DTRACE from configure sergiodj+buildbot
2015-06-13 11:14 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-06-11 16:24 [binutils-gdb] sim: trace: centralize the system tracing sergiodj+buildbot
2015-06-12 13:29 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-06-10 17:41 [binutils-gdb] Code cleanup: Use explicit NULL comparison sergiodj+buildbot
2015-06-11  6:20 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-06-10 13:47 [binutils-gdb] Introduce nat/linux-namespaces.[ch] sergiodj+buildbot
2015-06-10 17:51 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-06-10 13:20 [binutils-gdb] windows-nat: Trim a trailing '\n' from OutputDebugString before echoing it sergiodj+buildbot
2015-06-10 14:22 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-06-10 11:49 [binutils-gdb] Add support for bound table in the Intel MPX context sergiodj+buildbot
2015-06-10 13:16 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-06-10  9:48 [binutils-gdb] Improve test for processor feature om MPX registers test sergiodj+buildbot
2015-06-10 10:32 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-06-09  9:40 [binutils-gdb] Fix preprocessor conditional sergiodj+buildbot
2015-06-09 10:40 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-06-04 17:04 [binutils-gdb] Regenerate gdbarch.c to sync with gdbarch.sh sergiodj+buildbot
2015-06-04 19:14 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-06-02 19:59 [binutils-gdb] Fix =thread-exited not showing up when detaching (PR 15564) sergiodj+buildbot
2015-06-02 20:54 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-06-01 12:27 [binutils-gdb] Check whether kernel supports PTRACE_GETREGSET sergiodj+buildbot
2015-06-01 17:21 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-06-01 11:35 [binutils-gdb] Move PTRACE_GETREGSET and PTRACE_SETREGSET to nat/linux-ptrace.h sergiodj+buildbot
2015-06-01 13:17 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-06-01  9:39 [binutils-gdb] [AArch64] BFD_RELOC_AARCH64_TLSLE_ADD_LO12 should enable overflow check sergiodj+buildbot
2015-06-01  9:59 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-06-01  9:32 [binutils-gdb] [AArch64] BFD Support BFD_RELOC_AARCH64_LD64_GOTPAGE_LO15 sergiodj+buildbot
2015-06-01  9:47 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-06-01  9:26 [binutils-gdb] [AArch64] GAS Support BFD_RELOC_AARCH64_LD64_GOTPAGE_LO15 sergiodj+buildbot
2015-06-01  9:36 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-06-01  8:05 [binutils-gdb] x86/Intel: disassemble vcvt{, u}si2s{d, s} with correct operand order sergiodj+buildbot
2015-06-01  8:32 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-06-01  8:00 [binutils-gdb] x86/Intel: accept mandated operand order for vcvt{, u}si2s{d, s} sergiodj+buildbot
2015-06-01  8:10 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-05-28 23:12 [binutils-gdb] Disable exec-dependent follow vfork tests for remote sergiodj+buildbot
2015-05-29  7:08 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-05-28 17:04 [binutils-gdb] * dwarf2read.c (record_line_ftype): Remove, duplicate sergiodj+buildbot
2015-05-28 18:17 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-05-27 10:48 [binutils-gdb] Fix ARI warnings in aarch64-tdep.c sergiodj+buildbot
2015-05-27 11:08 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-05-27  0:27 [binutils-gdb] PR c++/18141, c++/18417 sergiodj+buildbot
2015-05-27 10:48 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-05-27  0:00 [binutils-gdb] Rename dwarf2 to dwarf in "set debug" and maintenance commands sergiodj+buildbot
2015-05-27  3:47 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-05-26 23:21 [binutils-gdb] PR python/18438 sergiodj+buildbot
2015-05-26 23:31 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-05-26 21:49 [binutils-gdb] gdb: tui: Minor fix to compare against NULL sergiodj+buildbot
2015-05-26 22:04 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-05-26 21:39 [binutils-gdb] gdb: Add 'tui reg prev' command sergiodj+buildbot
2015-05-26 21:50 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-05-26 14:39 [binutils-gdb] New gdb.reverse test case for aarch64 instructions sergiodj+buildbot
2015-05-26 17:41 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-05-26 14:29 [binutils-gdb] Enables gdb.reverse testsuite for aarch64*-linux targets sergiodj+buildbot
2015-05-26 17:22 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-05-26 14:20 [binutils-gdb] Implements aarch64 process record and reverse debugging support sergiodj+buildbot
2015-05-26 17:03 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-05-26 14:10 [binutils-gdb] NEWS entry about aarch64-linux record/replay support sergiodj+buildbot
2015-05-26 16:35 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-05-22  1:22 [binutils-gdb] Make sure test names are unique in gdb.base/gdbinit-history.exp sergiodj+buildbot
2015-05-22  5:38 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-05-21 21:14 [binutils-gdb] gdb: Don't call tui_enable too early sergiodj+buildbot
2015-05-22  0:41 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-05-21 20:01 [binutils-gdb] gdb: Add completer for layout command sergiodj+buildbot
2015-05-21 22:28 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-05-19 10:23 [binutils-gdb] Fix gdb.base/gdbinit-history.exp when HISTSIZE is set in the environment sergiodj+buildbot
2015-05-19 11:56 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-05-17  9:35 [binutils-gdb] sim: erc32: restore attribution sergiodj+buildbot
2015-05-17 10:20 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-05-16 19:57 [binutils-gdb] Add support for unbuffered and zero sized Guile ports sergiodj+buildbot
2015-05-17  0:37 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-05-16 16:31 [binutils-gdb] Code cleanup: compile: func_addr -> func_sym sergiodj+buildbot
2015-05-16 20:02 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-05-16 15:35 [binutils-gdb] Don't generate PLT relocations for now binding sergiodj+buildbot
2015-05-16 20:55 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-05-16 15:20 [binutils-gdb] compile: Fix detected inferior type sergiodj+buildbot
2015-05-16 20:38 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-05-16 15:07 [binutils-gdb] compile: New 'compile print' sergiodj+buildbot
2015-05-16 20:20 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-05-15 18:59 [binutils-gdb] Fix gdb.mi/mi-nsmoribund.exp timeouts sergiodj+buildbot
2015-05-15 21:12 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-05-15 15:31 [binutils-gdb] Fix a couple C++ build issues sergiodj+buildbot
2015-05-15 16:55 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-05-14 20:35 [binutils-gdb] Fix build gdbserver build errors on arm, mips, aarch64 sergiodj+buildbot
2015-05-14 22:09 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-05-13 13:29 [binutils-gdb] Fix PR gdb/17820 sergiodj+buildbot
2015-05-13 15:24 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-05-12 12:50 [binutils-gdb] [AArch64] Add R_AARCH64_P32_LD32_GOTPAGE_LO14 to elf header sergiodj+buildbot
2015-05-12 14:09 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-05-10 14:04 [binutils-gdb] Replace input_bfd and output_bfd with abfd sergiodj+buildbot
2015-05-10 15:05 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-05-09  0:26 [binutils-gdb] Avoid segfault on missing directory table sergiodj+buildbot
2015-05-09 12:00 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-05-08 17:11 [binutils-gdb] gdb/copyright.py: Remove sim/erc32 files from NOT_FSF_LIST sergiodj+buildbot
2015-05-08 18:48 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-05-05 22:44 [binutils-gdb] Further document ada-lang.c::value_assign_to_component & fix whitespaces sergiodj+buildbot
2015-05-06  5:38 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-05-05 21:47 [binutils-gdb] GDB crash trying to subscript array of variant record sergiodj+buildbot
2015-05-05 22:55 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-05-05 20:39 [binutils-gdb] testsuite/gdb.ada/var_rec_arr: New testcase sergiodj+buildbot
2015-05-06  0:38 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-05-05 19:07 [binutils-gdb] Add valaddr support in dynamic property resolution sergiodj+buildbot
2015-05-05 19:53 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-30 19:45 [binutils-gdb] Make RL78 disassembler and simulator respect ISA for mul/div sergiodj+buildbot
2015-04-30 20:28 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-30 15:38 [binutils-gdb] Fix handling of relocs for the MeP target sergiodj+buildbot
2015-04-30 16:00 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-29 17:01 [binutils-gdb] Updated translations for various binutils components sergiodj+buildbot
2015-04-29 20:11 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-29 14:34 [binutils-gdb] Allow passing fd == NULL to exec_file_find and solib_find sergiodj+buildbot
2015-04-29 15:21 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-28 18:59 [binutils-gdb] Use "gdb_wait.h" instead of <sys/wait.h> sergiodj+buildbot
2015-04-29  1:45 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-27 23:43 [binutils-gdb] Enable fork tracing for native FreeBSD targets sergiodj+buildbot
2015-04-28 11:15 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-27 23:34 [binutils-gdb] Add fbsd_nat_add_target sergiodj+buildbot
2015-04-28  6:13 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-26 19:52 [binutils-gdb] Clear variable "coredump_var_addr" before using it on gdb.base/coredump-filter.exp sergiodj+buildbot
2015-04-26 20:40 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-25  0:02 [binutils-gdb] gdb: Add internationalization support to a few strings sergiodj+buildbot
2015-04-25 10:53 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-24 16:12 [binutils-gdb] Fix typos in sim sources exposed by static analysis sergiodj+buildbot
2015-04-24 18:14 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-23 19:08 [binutils-gdb] Don't change compressed input debug section names sergiodj+buildbot
2015-04-23 20:14 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-23 16:47 [binutils-gdb] Fix gdb.base/interrupt.exp racy fail against gdbserver sergiodj+buildbot
2015-04-23 19:17 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-23 14:57 [binutils-gdb] x86: disambiguate disassembly of certain AVX512 insns sergiodj+buildbot
2015-04-23 15:43 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-23  0:56 [binutils-gdb] Align .TOC. for PowerPC64 sergiodj+buildbot
2015-04-23  9:23 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-22 20:56 [binutils-gdb] libiberty/setenv.c: Do not declare environ if defined as a macro sergiodj+buildbot
2015-04-23  3:22 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-22 19:19 [binutils-gdb] windows-nat: Fix misspelling in debug output sergiodj+buildbot
2015-04-22 21:03 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-22 18:55 [binutils-gdb] windows-nat: Cleanups in get_windows_debug_event sergiodj+buildbot
2015-04-22 20:04 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-22 12:45 [binutils-gdb] i386: Allow copy relocs for building PIE sergiodj+buildbot
2015-04-22 13:55 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-21 20:33 [binutils-gdb] Fix pascal behavior for class fields with testcase sergiodj+buildbot
2015-04-21 21:21 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-21 10:25 [binutils-gdb] sim: mcore: clean up printf warnings sergiodj+buildbot
2015-04-21 14:24 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-21  9:14 [binutils-gdb] sim: mcore: drop watchpoint/dumpmem/clearstats support sergiodj+buildbot
2015-04-21 11:48 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-21  7:11 [binutils-gdb] Extend rl78 prologue analyzer to recognize more complicated prologues sergiodj+buildbot
2015-04-21  8:09 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-20 20:12 [binutils-gdb] Always set up sh_name in assign_section_numbers sergiodj+buildbot
2015-04-20 20:53 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-20 10:51 [binutils-gdb] Fix three test failures with extended remote targets sergiodj+buildbot
2015-04-20 11:59 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-20  0:29 [binutils-gdb] Remove duplicated xmalloc in update_dprintf_command_list sergiodj+buildbot
2015-04-20  3:49 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-19 23:00 [binutils-gdb] [GDB] Hurd: Simplify the reply_mig_hack.awk script sergiodj+buildbot
2015-04-19 23:42 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-18 10:30 [binutils-gdb] sim: clean up duplicate sim-engine hooks sergiodj+buildbot
2015-04-18 12:32 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-18 10:18 [binutils-gdb] sim: trim old USING_SIM_BASE_H define sergiodj+buildbot
2015-04-18 11:35 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-18  8:40 [binutils-gdb] sim: unify sim_cia definition sergiodj+buildbot
2015-04-18  9:35 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-17 18:36 [binutils-gdb] solib-svr4.c (svr4_exec_displacement): Rename outer "displacement" sergiodj+buildbot
2015-04-18  3:06 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-17 14:33 [binutils-gdb] gdbserver/xtensa: drop xtensa_usrregs_info sergiodj+buildbot
2015-04-17 21:41 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-17 13:06 [binutils-gdb] Update comments to target_can_use_hardware_watchpoint sergiodj+buildbot
2015-04-17 19:23 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-17 11:01 [binutils-gdb] Introduce exec_file_find sergiodj+buildbot
2015-04-17 13:28 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-17 10:49 [binutils-gdb] Introduce linux_proc_pid_to_exec_file sergiodj+buildbot
2015-04-17 15:26 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-17 10:45 [binutils-gdb] Introduce exec_file_locate_attach sergiodj+buildbot
2015-04-17 12:10 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-17  7:40 [binutils-gdb] sim: replace CIA_{GET,SET} with CPU_PC_{GET,SET} sergiodj+buildbot
2015-04-17  8:55 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-17  6:45 [binutils-gdb] sim: arm/cr16/d10v/h8300/microblaze/sh: fill out sim-cpu pc fetch/store helpers sergiodj+buildbot
2015-04-17  7:57 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-16 13:58 [binutils-gdb] Fix gdbserver_reconnect_p handling sergiodj+buildbot
2015-04-16 15:33 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-16 12:02 [binutils-gdb] s390-vregs.exp: Avoid compile errors with older GCCs and on 31-bit targets sergiodj+buildbot
2015-04-16 13:36 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-16  6:38 [binutils-gdb] sim: avr/mcore/moxie: fill out sim-cpu pc fetch/store helpers sergiodj+buildbot
2015-04-16  9:13 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-15 22:09 [binutils-gdb] Make info fun|var|types interruptable for psyms sergiodj+buildbot
2015-04-16  7:17 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-15 20:39 [binutils-gdb] Make info fun|var|types interruptable sergiodj+buildbot
2015-04-16  6:16 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-15 20:26 [binutils-gdb] Check dp->prefix_requirement instead sergiodj+buildbot
2015-04-16  5:12 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-15 18:36 [binutils-gdb] Handle invalid prefixes for rdrand and rdseed sergiodj+buildbot
2015-04-16  3:25 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-15 16:28 [binutils-gdb] Some Python 3 fixes sergiodj+buildbot
2015-04-15 20:01 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-15 15:08 [binutils-gdb] Fix code indentation sergiodj+buildbot
2015-04-15 18:03 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-15 14:45 [binutils-gdb] [arm] Fix fails in gdb.base/disp-step-syscall.exp sergiodj+buildbot
2015-04-15 17:04 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-15  2:15 [binutils-gdb] Fix typo in commit 6ff71e76 sergiodj+buildbot
2015-04-15  8:32 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-14 15:29 [binutils-gdb] Adds support to the RL78 port for linker relaxation affecting .debug sections sergiodj+buildbot
2015-04-14 15:34 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-14 12:31 [binutils-gdb] Harden gdb.base/bp-permanent.exp sergiodj+buildbot
2015-04-14 14:51 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-14 11:19 [binutils-gdb] Add -z noextern-protected-data to ld for ELF/x86 sergiodj+buildbot
2015-04-14 12:32 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-14  3:25 [binutils-gdb] sim: ppc: fix up version script sergiodj+buildbot
2015-04-14  4:44 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-13 21:19 [binutils-gdb] Add support for the x86 XSAVE extended state on FreeBSD/x86 sergiodj+buildbot
2015-04-13 22:33 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-13 17:49 [binutils-gdb] Harden gdb.base/coredump-filter.exp sergiodj+buildbot
2015-04-13 20:33 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-13 14:52 [binutils-gdb] Catch exception in lib/gdbserver-support.exp:gdb_exit sergiodj+buildbot
2015-04-13 19:35 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-13 14:50 [binutils-gdb] sim: fix the PKGVERSION define sergiodj+buildbot
2015-04-13 16:14 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-13  9:36 [binutils-gdb] sim: options: add --version support sergiodj+buildbot
2015-04-13 15:15 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-13  8:27 [binutils-gdb] sim: m68hc11: convert to sim-cpu sergiodj+buildbot
2015-04-13  9:23 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-13  7:29 [binutils-gdb] sim: v850: convert to sim-cpu sergiodj+buildbot
2015-04-13 11:50 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-13  7:25 [binutils-gdb] sim: mips: fix prototype warnings sergiodj+buildbot
2015-04-13  8:03 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-13  0:18 [binutils-gdb] Do unset_currtarget_info ldscript for all simulator testsuites sergiodj+buildbot
2015-04-13  2:19 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-12 10:22 [binutils-gdb] sim: arm/mips: fix sim_read/sim_write linkage errors sergiodj+buildbot
2015-04-12 11:51 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-12  9:35 [binutils-gdb] sim: ft32: delete sim_read/sim_write funcs sergiodj+buildbot
2015-04-12 10:16 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-12  0:12 [binutils-gdb] Don't call getpagesize more than once sergiodj+buildbot
2015-04-12  3:39 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-11 22:33 [binutils-gdb] Initialize pagesize_m1 in bfd_cache_init sergiodj+buildbot
2015-04-11 23:18 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-10 23:26 [binutils-gdb] Cleanup signal-while-stepping-over-bp-other-thread.exp sergiodj+buildbot
2015-04-11  4:04 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-10 21:19 [binutils-gdb] step-over-trips-on-watchpoint.exp: Don't put addresses in test messages sergiodj+buildbot
2015-04-11  2:54 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-10 18:49 [binutils-gdb] Add extern_protected_data and set it for x86 sergiodj+buildbot
2015-04-10 23:18 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-10 16:17 [binutils-gdb] PPC64: Fix step-over-trips-on-watchpoint.exp with displaced stepping on sergiodj+buildbot
2015-04-10 21:16 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-10 13:34 [binutils-gdb] Make gdb.threads/step-over-trips-on-watchpoint.exp effective on !x86 sergiodj+buildbot
2015-04-10 19:17 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-10 12:25 [binutils-gdb] Fix gdb.base/sigstep.exp with displaced stepping on software single-step targets sergiodj+buildbot
2015-04-10 15:55 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-10 11:30 [binutils-gdb] Revert "Add extern_protected_data and set it for x86" sergiodj+buildbot
2015-04-10 13:44 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-10  9:24 [binutils-gdb] PR13858 - Can't do displaced stepping with no symbols sergiodj+buildbot
2015-04-10 10:12 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-09 20:03 [binutils-gdb] Update comments in compress.c sergiodj+buildbot
2015-04-10  5:00 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-09 17:47 [binutils-gdb] xtensa: optimize find_removed_literal sergiodj+buildbot
2015-04-09 22:49 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-09 16:54 [binutils-gdb] xtensa: optimize check_section_ebb_pcrels_fit sergiodj+buildbot
2015-04-09 20:51 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-09 10:58 [binutils-gdb] Import strtok_r gnulib module sergiodj+buildbot
2015-04-09 13:17 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-08 22:42 [binutils-gdb] Fix Python completion when using the "complete" command sergiodj+buildbot
2015-04-08 23:49 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-08 15:50 [binutils-gdb] [spu] Don't call set_gdbarch_cannot_step_breakpoint in spu_gdbarch_init sergiodj+buildbot
2015-04-08 17:21 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-07 21:12 [binutils-gdb] Initialize variable on gdb/linux-tdep.c:decode_vmflags sergiodj+buildbot
2015-04-08  4:35 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-07 20:38 [binutils-gdb] gdb.base/interrupt.exp: Use send_inferior/$inferior_spawn_id sergiodj+buildbot
2015-04-07 23:58 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-07 20:04 [binutils-gdb] testsuite: Introduce $inferior_spawn_id sergiodj+buildbot
2015-04-07 22:58 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-07 19:30 [binutils-gdb] testsuite: Don't use expect_background to reap gdbserver sergiodj+buildbot
2015-04-07 21:39 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-07 19:06 [binutils-gdb] gdb_test_multiple: Fix user code argument processing sergiodj+buildbot
2015-04-07 20:42 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-07 16:39 [binutils-gdb] Fix gdb.trace/actions.exp race sergiodj+buildbot
2015-04-07 17:51 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-07 11:49 [binutils-gdb] Displaced stepping debug: fetch the right regcache sergiodj+buildbot
2015-04-07 13:23 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-07 11:17 [binutils-gdb] Properly set alarm value in gdb.threads/non-stop-fair-events.exp sergiodj+buildbot
2015-04-07 12:23 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-07  4:06 [binutils-gdb] sim: move sim-engine.o/sim-hrw.o to the common list sergiodj+buildbot
2015-04-07  5:01 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-06 15:43 [binutils-gdb] symtab.c (hash_symbol_entry): Hash STRUCT_DOMAIN symbols as VAR_DOMAIN sergiodj+buildbot
2015-04-06 16:35 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-05  8:49 [binutils-gdb] sim: m68hc11: add a basic testsuite sergiodj+buildbot
2015-04-05  9:09 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-05  6:30 [binutils-gdb] sim: lm32: add a basic testsuite sergiodj+buildbot
2015-04-05  7:18 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-04  0:13 [binutils-gdb] gdbtypes.c: remove the usuned "top_level" parameter sergiodj+buildbot
2015-04-04 14:41 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-03 13:39 [binutils-gdb] Do not consider reference types as dynamic sergiodj+buildbot
2015-04-04 13:48 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-03  1:12 [binutils-gdb] kfail two tests in no-unwaited-for-left.exp for remote target sergiodj+buildbot
2015-04-04 10:24 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-03  0:31 [binutils-gdb] Document "target:" sysroot changes sergiodj+buildbot
2015-04-04  6:44 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-02 23:49 [binutils-gdb] Set zlibdir/zlibinc with top_builddir/top_srcdir sergiodj+buildbot
2015-04-04  7:43 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-02 23:24 [binutils-gdb] Update exec_file_attach to cope with "target:" filenames sergiodj+buildbot
2015-04-04  4:07 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-02 22:09 [binutils-gdb] Rearrange symfile_bfd_open sergiodj+buildbot
2015-04-03 19:50 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-02 22:04 [binutils-gdb] Strip "target:" prefix in solib_find if accessing local files sergiodj+buildbot
2015-04-03 23:25 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-02 21:12 [binutils-gdb] Convert "remote:" sysroots to "target:" and remove "remote:" sergiodj+buildbot
2015-04-03  9:36 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-02 19:26 [binutils-gdb] sim: clean up SIM_EXTRA_OBJS references sergiodj+buildbot
2015-04-02 20:12 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-01 19:34 [binutils-gdb] keep_going: Add missing discard_cleanups call sergiodj+buildbot
2015-04-02 13:05 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-01 16:39 [binutils-gdb] Use do_target_resume when stepping past permanent breakpoint too sergiodj+buildbot
2015-04-02 11:18 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-01 13:45 [binutils-gdb] Add --with-system-zlib to top level configure sergiodj+buildbot
2015-04-01 23:44 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-01 10:55 [binutils-gdb] GDBServer: give more complete usage information sergiodj+buildbot
2015-04-01 20:01 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-01  6:06 [binutils-gdb] sim: run: punt! sergiodj+buildbot
2015-04-01 17:44 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-04-01  0:32 [binutils-gdb] Implement support for checking /proc/PID/coredump_filter sergiodj+buildbot
2015-04-01 15:10 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-03-31 22:54 [binutils-gdb] Use AM_ENABLE_MULTILIB only if with_target_subdir isn't empty sergiodj+buildbot
2015-04-01 12:09 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-03-31 19:58 [binutils-gdb] Add support for Nuxi CloudABI on x86-64 sergiodj+buildbot
2015-04-01  9:06 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-03-31 16:26 [binutils-gdb] Add cpu information to the info os command on linux sergiodj+buildbot
2015-03-31 23:50 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-03-31  8:20 [binutils-gdb] sim: m68hc11: fix gcc-5 build error w/restrict keyword sergiodj+buildbot
2015-03-31 18:53 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-03-31  3:54 [binutils-gdb] Update config.guess and config.sub to the latest upstream version sergiodj+buildbot
2015-03-31 16:01 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-03-30 22:00 [binutils-gdb] sim: arm: convert to nrun sergiodj+buildbot
2015-03-31 14:40 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-03-30 20:01 [binutils-gdb] sim: arm: delete NEED_UI_LOOP_HOOK handling sergiodj+buildbot
2015-03-31 14:29 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-03-30 19:16 [binutils-gdb] sim: arm: use common configure options sergiodj+buildbot
2015-03-31 14:18 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-03-30 14:54 [binutils-gdb] sim: d10v: convert to nrun sergiodj+buildbot
2015-03-31  1:23 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-03-30 10:55 [binutils-gdb] sim: d10v: clean up misc warnings sergiodj+buildbot
2015-03-30 23:54 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-03-30 10:29 [binutils-gdb] sim: d10v: link in missing testsuite sergiodj+buildbot
2015-03-30 19:10 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-03-30  9:55 [binutils-gdb] sim: d10v: use common configure options sergiodj+buildbot
2015-03-30 21:33 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-03-30  8:19 [binutils-gdb] sim: cr16: delete NEED_UI_LOOP_HOOK handling sergiodj+buildbot
2015-03-30 17:27 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-03-30  6:48 [binutils-gdb] sim: cr16: use common configure options sergiodj+buildbot
2015-03-30 13:18 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-03-30  3:46 [binutils-gdb] sim: microblaze: convert to nrun sergiodj+buildbot
2015-03-30 11:00 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-03-30  1:19 [binutils-gdb] sim: microblaze: start a testsuite sergiodj+buildbot
2015-03-30  7:28 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-03-29 22:47 [binutils-gdb] sim; testsuite: allow tests to set no output sergiodj+buildbot
2015-03-30  5:58 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-03-29 19:00 [binutils-gdb] sim: testsuite: make subdir unconditional sergiodj+buildbot
2015-03-30  1:04 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-03-29 18:05 [binutils-gdb] sim: microblaze: use common configure options sergiodj+buildbot
2015-03-29 22:41 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-03-29 12:02 [binutils-gdb] sim: mcore: convert to nrun sergiodj+buildbot
2015-03-29 21:21 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-03-29 10:43 [binutils-gdb] sim: mcore: drop sbrk support sergiodj+buildbot
2015-03-29 16:34 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-03-29  5:12 [binutils-gdb] sim: sh: convert to nrun sergiodj+buildbot
2015-03-29 15:58 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-03-29  0:03 [binutils-gdb] sim: sh: clean up gencode sergiodj+buildbot
2015-03-29 11:58 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-03-28 18:34 [binutils-gdb] A zlib to tarball sergiodj+buildbot
2015-03-29  9:13 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-03-28 10:38 [binutils-gdb] sim: avr: start a basic testsuite sergiodj+buildbot
2015-03-29  8:43 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-03-28  9:01 [binutils-gdb] sim: erc32: strip paren from return statements sergiodj+buildbot
2015-03-29  6:07 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-03-27 13:20 [binutils-gdb] Fix gdb_bfd_section_index for special sections sergiodj+buildbot
2015-03-28 23:05 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-03-27  6:53 [binutils-gdb] Relax PR 15228 protected visibility restriction sergiodj+buildbot
2015-03-28 22:40 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-03-26 23:51 [binutils-gdb] testsuite: Don't set SYMBOL_PREFIX for x86_64_*_cygwin sergiodj+buildbot
2015-03-28 22:17 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-03-26 22:17 [binutils-gdb] dtrace-probe: Handle error while parsing probe argument sergiodj+buildbot
2015-03-28 21:24 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-03-26 21:46 [binutils-gdb] Add myself as a write-after-approval GDB maintainer sergiodj+buildbot
2015-03-28 20:59 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-03-26 18:51 [binutils-gdb] Code cleanup: Make validate_format parameter const sergiodj+buildbot
2015-03-28 20:23 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-03-26  9:30 [binutils-gdb] Remove some hard-coded stuff in tests sergiodj+buildbot
2015-03-28 11:48 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-03-26  9:08 [binutils-gdb] Compile break-asm-file{0,1}.s without debug info sergiodj+buildbot
2015-03-28  9:37 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-03-26  4:11 [binutils-gdb] powerpc: Add slbfee. instruction sergiodj+buildbot
2015-03-28  7:39 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-03-26  3:24 [binutils-gdb] [AArch64] Implement branch over stub section sergiodj+buildbot
2015-03-28  7:02 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-03-26  2:05 [binutils-gdb] [AArch64] Remove padding before stub sections sergiodj+buildbot
2015-03-28  6:34 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-03-25 16:57 [binutils-gdb] [AArch64] Adjust veneer count sergiodj+buildbot
2015-03-28  3:58 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-03-25 16:36 [binutils-gdb] Fix mi-pending.exp test output to allow stable test diffing sergiodj+buildbot
2015-03-26 18:11 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-03-25 11:45 [binutils-gdb] Move low-level Linux x86 debug register code to a shared file sergiodj+buildbot
2015-03-25 23:03 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-03-25  4:46 [binutils-gdb] Fix "thread apply all" with exited threads sergiodj+buildbot
2015-03-27 19:29 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-03-25  3:24 [binutils-gdb] Make linux_stop_lwp be a shared function sergiodj+buildbot
2015-03-25 15:19 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-03-25  3:22 [binutils-gdb] Debug output tweaks in the Linux target backends sergiodj+buildbot
2015-03-27 12:36 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-03-25  0:47 [binutils-gdb] Make step_start_function be per thread sergiodj+buildbot
2015-03-27  1:32 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-03-24 23:58 [binutils-gdb] No longer handle negative 'step' in 'proceed' sergiodj+buildbot
2015-03-26 23:11 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-03-24 23:49 [binutils-gdb] Introduce current_lwp_ptid sergiodj+buildbot
2015-03-25 11:49 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-03-24 23:00 [binutils-gdb] Fixes a bug introduced by the new ranges checks on COFF symbol tables sergiodj+buildbot
2015-03-26 15:43 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-03-24 22:15 [binutils-gdb] [AArch64] Factor out _bfd_aarch64_get_stub_for_link_section sergiodj+buildbot
2015-03-26  8:49 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-03-24 18:37 [binutils-gdb] Make lwp_info.arch_private handling shared sergiodj+buildbot
2015-03-25 18:54 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-03-24 17:32 [binutils-gdb] Introduce basic LWP accessors sergiodj+buildbot
2015-03-25 16:14 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-03-24 17:08 [binutils-gdb] Extend arm_feature_set struct to provide more bits sergiodj+buildbot
2015-03-25  2:01 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-03-24 16:34 [binutils-gdb] Add iterate_over_lwps to gdbserver sergiodj+buildbot
2015-03-25 13:50 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-03-24 14:50 [binutils-gdb] [AArch64] Refactor generation of 835769 workaround stubs sergiodj+buildbot
2015-03-25  9:54 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-03-24 14:15 [binutils-gdb] [AArch64] Use _bfd_aarch64_add_stub_entry_in_group sergiodj+buildbot
2015-03-25  8:10 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-03-24 12:39 [binutils-gdb] sim: erc32/h8300/m68hc11: trim unused functions sergiodj+buildbot
2015-03-24 21:28 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-03-24 12:19 [binutils-gdb] sim: m32r: drop duplicate dv_sockser_install call sergiodj+buildbot
2015-03-24 18:52 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-03-24  5:21 [binutils-gdb] sim: drop support for requiring hw support sergiodj+buildbot
2015-03-24 15:25 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-03-24  4:11 [binutils-gdb] GDB: Add set/show serial parity command sergiodj+buildbot
2015-03-24  8:29 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-03-23 22:22 [binutils-gdb] Update comment of linespec_lexer_lex_keyword sergiodj+buildbot
2015-03-24  7:16 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-03-23 21:05 [binutils-gdb] [AArch64] Drop unused argument to elf_aarch64_create_or_find_stub_sec sergiodj+buildbot
2015-03-23 21:21 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-03-23 20:51 [binutils-gdb] [OBV] Fix build -- missing ';' sergiodj+buildbot
2015-03-24  1:17 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-03-23 19:16 [binutils-gdb] [AArch64] Factor out _bfd_aarch64_resize_stubs() sergiodj+buildbot
2015-03-23 23:38 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-03-23 19:09 [binutils-gdb] [AArch64] Factor stub creation code into _bfd_aarch64_create_stub_section sergiodj+buildbot
2015-03-23 23:14 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-03-23 17:58 [binutils-gdb] [AArch64] Remove unused variable sergiodj+buildbot
2015-03-23 20:49 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-03-23 16:27 [binutils-gdb] [AArch64] Tidy up in aarch64_mem_op_p() sergiodj+buildbot
2015-03-23 18:14 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-03-23 16:02 [binutils-gdb] [AArch64] Adjust layout of elfNN_aarch64_write_section sergiodj+buildbot
2015-03-23 16:42 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-03-23  9:49 [binutils-gdb] sim: bfin/msp430: drop run-sim.h include sergiodj+buildbot
2015-03-23 11:04 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-03-23  8:38 [binutils-gdb] sim: sh64: delete dv-sockser references sergiodj+buildbot
2015-03-23 10:00 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-03-21  3:23 [binutils-gdb] constify set_breakpoint_condition sergiodj+buildbot
2015-03-23  8:02 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-03-20 20:05 [binutils-gdb] constify gdbserver/server.c sergiodj+buildbot
2015-03-20 22:04 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-03-19 16:51 [binutils-gdb] gdbserver/Linux: unbreak thread event randomization sergiodj+buildbot
2015-03-19 17:54 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-03-11 21:37 [binutils-gdb] Create gdb/break-catch-syscall.c sergiodj+buildbot
2015-03-12 19:57 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-03-07 18:24 [binutils-gdb] Split TRY_CATCH into TRY + CATCH sergiodj+buildbot
2015-03-07 20:31 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-03-05  7:48 [binutils-gdb] gdbserver: Support the "swbreak"/"hwbreak" stop reasons sergiodj+buildbot
2015-03-06 10:15 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-03-05  6:17 [binutils-gdb] remote+docs: software/hardware breakpoint traps sergiodj+buildbot
2015-03-06  7:24 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-03-05  4:30 [binutils-gdb] record-full/record-btrace: software/hardware breakpoint trap sergiodj+buildbot
2015-03-06  6:24 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-03-05  3:54 [binutils-gdb] enum lwp_stop_reason -> enum target_stop_reason sergiodj+buildbot
2015-03-06  4:54 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-03-05  2:56 [binutils-gdb] Teach GDB about targets that can tell whether a trap is a breakpoint event sergiodj+buildbot
2015-03-06  1:06 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-03-05  0:03 [binutils-gdb] follow-fork: don't lose the ptids as set by the target sergiodj+buildbot
2015-03-06  0:11 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-03-04 22:15 [binutils-gdb] Add linux-aarch64-low.c in SFILE sergiodj+buildbot
2015-03-05 19:11 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-03-04 20:53 [binutils-gdb] Enable gdb.base/foll-fork.exp on OpenBSD sergiodj+buildbot
2015-03-05 18:19 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-03-04 20:01 [binutils-gdb] Make "catch fork" work on systems with PT_GET_PROCESS_STATE sergiodj+buildbot
2015-03-05 16:54 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-03-04 18:52 [binutils-gdb] [AArch64] Removing unused functions sergiodj+buildbot
2015-03-05 15:43 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-03-04 17:51 [binutils-gdb] [AArch64] Call abort() consistently in unhandled stub switch statements sergiodj+buildbot
2015-03-05 15:08 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-03-04 17:00 [binutils-gdb] S390: Name "invisible" registers with the empty string instead of NULL sergiodj+buildbot
2015-03-05 12:43 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-03-04 15:54 [binutils-gdb] breakpoint-in-ro-region.exp: Support targets stopping in mid-line after "si" sergiodj+buildbot
2015-03-05 10:52 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-03-04 14:34 [binutils-gdb] catch-syscall.exp: Fix missing architecture name for s390:31-bit sergiodj+buildbot
2015-03-05  8:52 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-03-04 12:24 [binutils-gdb] S390: Place "s390:31-bit" after default arch in 64-bit arch list sergiodj+buildbot
2015-03-05  6:17 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-03-04 11:36 [binutils-gdb] gdb.threads/clone-thread_db.c: Add missing includes and fix pthread_join call sergiodj+buildbot
2015-03-05  1:40 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-03-04  2:54 [binutils-gdb] RL78 - fix ADDR16 relax sergiodj+buildbot
2015-03-04 18:50 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-03-04  0:10 [binutils-gdb] Remove unused function declarations in target.h sergiodj+buildbot
2015-03-04 16:53 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-03-03 20:04 [binutils-gdb] inf-ptrace.c: use ptid_get_pid when resuming all threads sergiodj+buildbot
2015-03-04 13:51 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-03-03 17:39 [binutils-gdb] Fix GDB/MI doc: duplicate syscall-entry under *stopped sergiodj+buildbot
2015-03-04 10:42 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-03-03 16:36 [binutils-gdb] [ARM] Skip private symbol when doing objdump sergiodj+buildbot
2015-03-04 10:05 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-03-03 13:24 [binutils-gdb] btrace: support 32-bit inferior on 64-bit host sergiodj+buildbot
2015-03-04  0:05 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-03-03 11:55 [binutils-gdb] btrace: work around _dl_runtime_resolve returning to resolved function sergiodj+buildbot
2015-03-03 23:37 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
     [not found] <c966a859b96f78920c16e1161578405d88b425cf@kwanyin>
2015-03-03  9:48 ` sergiodj+buildbot
2015-03-03  2:59 [binutils-gdb] follow-exec: delete all non-execing threads sergiodj+buildbot
2015-03-03 20:36 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-03-02 16:40 [binutils-gdb] Revert "Remove true and false ARI checks now that we use stdbool.h." sergiodj+buildbot
2015-03-03 15:23 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-03-02 14:22 [binutils-gdb] S390: Vector register test case sergiodj+buildbot
2015-03-03 13:08 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
     [not found] <8a526fa69afd8ea7d2e303f80c03f9eb46211390@kwanyin>
2015-03-02 14:07 ` sergiodj+buildbot
2015-03-02 13:16 [binutils-gdb] S390: Add vector register support to gdbserver sergiodj+buildbot
2015-03-03 12:32 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
     [not found] <0fa9c223ddc05a4b823bc7982dce8ba3b45d903f@kwanyin>
2015-03-02 12:59 ` sergiodj+buildbot
2015-03-02 11:11 [binutils-gdb] S390: Add target descriptions for vector register sets sergiodj+buildbot
2015-03-03 10:11 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
     [not found] <1424c16eab1a96de054991c346c2bbf3eac82dec@kwanyin>
2015-03-02 10:50 ` sergiodj+buildbot
     [not found] <10367c7c946a123597cbc5efaa44c18912e5e43a@kwanyin>
2015-03-02 10:18 ` sergiodj+buildbot
     [not found] <4180215b9db1549b88da2da2fcc320fe28233481@kwanyin>
2015-03-02  9:21 ` sergiodj+buildbot
     [not found] <68c14faadaf5bfd9816ac913dc8858116aa15a84@kwanyin>
2015-03-02  6:11 ` sergiodj+buildbot
     [not found] <3bc3d82a005466a66fa22f704c90f4486ca71344@kwanyin>
2015-03-01 15:21 ` sergiodj+buildbot
     [not found] <07697489f4587e41f4f63aa526c1bd7d2fcd5494@kwanyin>
2015-03-01 12:42 ` sergiodj+buildbot
2015-03-01  2:57 [binutils-gdb] More redefinition errors in C++ mode sergiodj+buildbot
2015-03-02 21:05 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-02-28 22:53 [binutils-gdb] objcopy: Add --update-section option sergiodj+buildbot
2015-03-03  9:23 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-02-28 21:50 [binutils-gdb] symtab.h (struct symtab) <next>: Fix comment sergiodj+buildbot
2015-03-03  6:55 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-02-28 16:12 [binutils-gdb] Tweak ppc32 tls_get_addr optimisation sergiodj+buildbot
2015-03-03  2:01 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-02-28 15:42 [binutils-gdb] Fix Python 3 build: rename GdbMethods sergiodj+buildbot
2015-03-03  1:38 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-02-28 13:26 [binutils-gdb] Move exception_none to common code, and use it sergiodj+buildbot
2015-03-02 19:36 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-02-28  3:24 [binutils-gdb] Don't forward declare enum target_hw_bp_type sergiodj+buildbot
2015-03-02  9:05 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-02-28  1:34 [binutils-gdb] proc-service, extern "C" sergiodj+buildbot
2015-03-02  2:25 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-02-28  0:39 [binutils-gdb] Make functions and variables exported by the IPA be extern "C" sergiodj+buildbot
2015-03-02  1:13 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-02-27 23:46 [binutils-gdb] Add extern "C" to declarations of C symbols sergiodj+buildbot
2015-03-01 23:52 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-02-27 20:01 [binutils-gdb] C++ keyword cleanliness, mostly auto-generated sergiodj+buildbot
2015-03-01 16:01 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-02-27 15:49 [binutils-gdb] Add "../lib/unbuffer_output.c" and use it in gdb.base/interrupt.c sergiodj+buildbot
2015-03-01  1:21 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-02-27 15:33 [binutils-gdb] Don't skip catch-syscall.exp on hppa*-hp-hpux* target sergiodj+buildbot
2015-02-28 23:13 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-02-27 14:07 [binutils-gdb] Regenerate bfd-in2.h and libbfd.h sergiodj+buildbot
2015-02-28 21:37 ` Failures on Debian-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot
2015-02-27 10:42 [binutils-gdb] Fixes problems building the V850 simulator introduced with the previous delta sergiodj+buildbot
2015-02-28 20:16 ` Failures on Debian-x86_64-native-gdbserver-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).