public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
* [binutils-gdb/gdb-7.12-branch] x32: gdbserver's agent bytecode JIT: fix "call" emission
@ 2016-08-24  3:01 sergiodj+buildbot
  2016-08-24  3:10 ` Failures on Fedora-x86_64-native-gdbserver-m32, branch gdb-7.12-branch sergiodj+buildbot
                   ` (17 more replies)
  0 siblings, 18 replies; 59+ messages in thread
From: sergiodj+buildbot @ 2016-08-24  3:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7b42e25f7cac78821b6efea2890fe725c59250fc ***

Author: Pedro Alves <palves@redhat.com>
Branch: gdb-7.12-branch
Commit: 7b42e25f7cac78821b6efea2890fe725c59250fc

x32: gdbserver's agent bytecode JIT: fix "call" emission

Running fast tracepoint tests on x32 exposes a latent bug in the agent
bytecode jitting.  There's a code path that forgets to emit the call
opcode...  Whoops.  Fixes a bunch of gdb.trace/trace-condition.exp
FAILs, like:

  (gdb)
  continue
  Continuing.

  Thread 1 "trace-condition" received signal SIGSEGV, Segmentation fault.
  0x7ffec016 in ?? ()
  (gdb) FAIL: gdb.trace/trace-condition.exp: ftrace: $rip == *set_point: advance through tracing

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

	* linux-x86-low.c (amd64_emit_call): Emit missing call opcode.


^ permalink raw reply	[flat|nested] 59+ messages in thread
* [binutils-gdb/gdb-7.12-branch] Bump GDB version number to 7.12.1.DATE-git.
@ 2017-01-21 14:20 sergiodj+buildbot
  2017-01-21 15:06 ` Failures on Fedora-x86_64-native-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 59+ messages in thread
From: sergiodj+buildbot @ 2017-01-21 14:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5d3cbab1816758ecb3060367de6c1cd079fe8cb1 ***

Author: Joel Brobecker <brobecker@adacore.com>
Branch: gdb-7.12-branch
Commit: 5d3cbab1816758ecb3060367de6c1cd079fe8cb1

Bump GDB version number to 7.12.1.DATE-git.

gdb/ChangeLog:

	* version.in: Set GDB version number to 7.12.1.DATE-git.
	* PROBLEMS: Likewise.


^ permalink raw reply	[flat|nested] 59+ messages in thread
* [binutils-gdb/gdb-7.12-branch] Throw SJ/LJ exception on error in disassembly
@ 2017-01-20 13:17 sergiodj+buildbot
  2017-01-20 13:38 ` Failures on Fedora-x86_64-native-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 59+ messages in thread
From: sergiodj+buildbot @ 2017-01-20 13:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e2285602341fff057a9b4687b465a9d9cde1303f ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: gdb-7.12-branch
Commit: e2285602341fff057a9b4687b465a9d9cde1303f

Throw SJ/LJ exception on error in disassembly

PR 20939 reports that GDB will abort on memory error in disassembly,

(gdb) disassemble 0x0,+4
Dump of assembler code from 0x0 to 0x4:
terminate called after throwing an instance of 'gdb_exception_RETURN_MASK_ERROR'
   0x0000000000000000:	Aborted

(gdb) guile (print (arch-disassemble arch 0 #:size 4))^M
terminate called after throwing an instance of 'gdb_exception_RETURN_MASK_ERROR'^M
ERROR: Process no longer exists

This patch fixes PR 20939 by catching C++ exception, throwing SJ/LJ
exception in the call back passed to C functions of opcodes, and
catching SJ/LJ exception in gdb, and throw exception.

The patch follows this commit

 89525768cd086a0798a504c81fdf7ebcd4c904e1
 Propagate GDB/C++ exceptions across readline using sj/lj-based TRY/CATCH

rather than "backport" the fix to this PR I posted for mainline
https://sourceware.org/ml/gdb-patches/2017-01/msg00288.html because the
fix for mainline includes 1) some changes to opcodes, 2) some refactors
in C++.  All of them are risky to backport to 7.12 branch.

With this patch applied to 7.12 branch, GDB doesn't abort on memory error
in disassembly.  It fixes some test failures in gdb.guile/scm-disasm.exp
and gdb.python/py-arch.exp on aarch64-linux.

-ERROR: Process no longer exists
-UNRESOLVED: gdb.guile/scm-disasm.exp: test bad memory access
+PASS: gdb.guile/scm-disasm.exp: test bad memory access

-ERROR: Process no longer exists
-UNRESOLVED: gdb.python/py-arch.exp: test bad memory access
+PASS: gdb.python/py-arch.exp: test bad memory access

I'll add the scm-disasm test to master later.

gdb:

2017-01-20  Yao Qi  <yao.qi@linaro.org>

	PR gdb/20939
	* disasm.c (dis_asm_memory_error): Catch the error and rethrow
	it as a SJ/LJ exception.  Add GDB_NOEXCEPT.
	(disasm_print_insn_noexcept): New function.
	(disasm_print_insn): New function.
	(gdb_pretty_print_insn): Call disasm_print_insn instead of
	gdbarch_print_insn.
	(gdb_print_insn): Likewise.
	(gdb_buffered_insn_length): Likewise.
	* event-top.c (GDB_NOEXCEPT): Move it to ...
	* exceptions.h (GDB_NOEXCEPT): ... here.
	* guile/scm-disasm.c (gdbscm_disasm_memory_error): Remove.
	(gdbscm_print_insn_from_port): Don't set di.memory_errro_func.
	Call disasm_print_insn rather than gdbarch_print_insn.


^ permalink raw reply	[flat|nested] 59+ messages in thread
* [binutils-gdb/gdb-7.12-branch] update copyright year range in GDB files
@ 2017-01-01  8:58 sergiodj+buildbot
  2017-01-01  9:38 ` Failures on Fedora-x86_64-native-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 59+ messages in thread
From: sergiodj+buildbot @ 2017-01-01  8:58 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 16d400ab4a742988aad12f6476323bb234efb3e3 ***

Author: Joel Brobecker <brobecker@adacore.com>
Branch: gdb-7.12-branch
Commit: 16d400ab4a742988aad12f6476323bb234efb3e3

update copyright year range in GDB files

This applies the second part of GDB's End of Year Procedure, which
updates the copyright year range in all of GDB's files (the first
part is ommitted on this branch).

gdb/ChangeLog:

        Update copyright year range in all GDB files.


^ permalink raw reply	[flat|nested] 59+ messages in thread
* [binutils-gdb/gdb-7.12-branch] Fix longjmp across readline w/ --enable-sjlj-exceptions toolchains
@ 2016-12-20 17:36 sergiodj+buildbot
  2016-12-20 19:00 ` Failures on Fedora-x86_64-native-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 59+ messages in thread
From: sergiodj+buildbot @ 2016-12-20 17:36 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ada8ff522ce970e11dae4a3463c899b64e6f5006 ***

Author: Pedro Alves <palves@redhat.com>
Branch: gdb-7.12-branch
Commit: ada8ff522ce970e11dae4a3463c899b64e6f5006

Fix longjmp across readline w/ --enable-sjlj-exceptions toolchains

Nowadays, GDB propagates C++ exceptions across readline using
setjmp/longjmp 89525768cd08 ("Propagate GDB/C++ exceptions across
readline using sj/lj-based TRY/CATCH") because DWARF-based unwinding
can't cross C functions compiled without -fexceptions (see details
from the commit above).

Unfortunately, toolchains that use SjLj-based C++ exceptions got
broken with that fix, because _Unwind_SjLj_Unregister, which is put at
the exit of a function, is not executed due to the longjmp added by
that commit.

 (gdb) [New Thread 2936.0xb80]
 kill

 Thread 1 received signal SIGSEGV, Segmentation fault.
 0x03ff662b in ?? ()
 top?bt 15
 #0  0x03ff662b in ?? ()
 #1  0x00526b92 in stdin_event_handler (error=0, client_data=0x172ed8)
    at ../../binutils-gdb/gdb/event-top.c:555
 #2  0x00525a94 in handle_file_event (ready_mask=<optimized out>,
    file_ptr=0x3ff5cb8) at ../../binutils-gdb/gdb/event-loop.c:733
 #3  gdb_wait_for_event (block=block@entry=1)
    at ../../binutils-gdb/gdb/event-loop.c:884
 #4  0x00525bfb in gdb_do_one_event ()
    at ../../binutils-gdb/gdb/event-loop.c:347
 #5  0x00525ce5 in start_event_loop ()
    at ../../binutils-gdb/gdb/event-loop.c:371
 #6  0x0051fada in captured_command_loop (data=0x0)
    at ../../binutils-gdb/gdb/main.c:324
 #7  0x0051cf5d in catch_errors (
    func=func@entry=0x51fab0 <captured_command_loop(void*)>,
    func_args=func_args@entry=0x0,
    errstring=errstring@entry=0x7922bf <VEC_interp_factory_p_quick_push(VEC_inte rp_factory_p*, interp_factory*, char const*, unsigned int)::__PRETTY_FUNCTION__+351> "", mask=mask@entry=RETURN_MASK_ALL)
    at ../../binutils-gdb/gdb/exceptions.c:236
 #8  0x00520f0c in captured_main (data=0x328feb4)
    at ../../binutils-gdb/gdb/main.c:1149
 #9  gdb_main (args=args@entry=0x328feb4) at ../../binutils-gdb/gdb/main.c:1159
 #10 0x0071e400 in main (argc=1, argv=0x171220)
    at ../../binutils-gdb/gdb/gdb.c:32

Fix this by making the functions involved in setjmp/longjmp as
noexcept, so that the compiler knows it doesn't need to emit the
_Unwind_SjLj_Register / _Unwind_SjLj_Unregister calls for C++
exceptions.

Tested on x86_64 Fedora 23 with:
 - GCC 5.3.1 w/ DWARF-based exceptions.
 - GCC 7 built with --enable-sjlj-exceptions.

gdb/ChangeLog:
2016-12-20  Pedro Alves  <palves@redhat.com>
	    Yao Qi  <yao.qi@linaro.org>

	PR gdb/20977
	* event-top.c (gdb_rl_callback_read_char_wrapper_noexcept): New
	noexcept function, factored out from ...
	(gdb_rl_callback_read_char_wrapper): ... this.
	(gdb_rl_callback_handler): Mark noexcept.


^ permalink raw reply	[flat|nested] 59+ messages in thread
* [binutils-gdb/gdb-7.12-branch] sim: mips: fix dv-tx3904cpu build error
@ 2016-11-11  7:48 sergiodj+buildbot
  2016-11-11 10:07 ` Failures on Fedora-x86_64-native-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 59+ messages in thread
From: sergiodj+buildbot @ 2016-11-11  7:48 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cd48ce152d6710af146ffc7897a82586513fc534 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: gdb-7.12-branch
Commit: cd48ce152d6710af146ffc7897a82586513fc534

sim: mips: fix dv-tx3904cpu build error

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

This was broken by the clean up in commit d47f5b30d8481272e9480118bdcb.

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


^ permalink raw reply	[flat|nested] 59+ messages in thread
* [binutils-gdb/gdb-7.12-branch] [GDBserver] Fix conversion warning
@ 2016-10-25  3:26 sergiodj+buildbot
  2016-10-25  7:27 ` Failures on Fedora-x86_64-native-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 59+ messages in thread
From: sergiodj+buildbot @ 2016-10-25  3:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a945860b6cb4f8a26343ac5dcb0b42fe5fb2f68a ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: gdb-7.12-branch
Commit: a945860b6cb4f8a26343ac5dcb0b42fe5fb2f68a

[GDBserver] Fix conversion warning

I got the following warning if I build GDBserver for aarch64_be-linux-gnu,

git/gdb/gdbserver/linux-aarch64-low.c:1539:39: error: invalid conversion from 'void*' to 'uint32_t* {aka unsigned int*}' [-fpermissive]
   uint32_t *le_buf = xmalloc (byte_len);
                                       ^
The patch is to fix the warning.

gdb/gdbserver:

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

	PR server/20733
	* linux-aarch64-low.c (append_insns): Cast the return value to
	'uint32_t *'.


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

*** TEST RESULTS FOR COMMIT 8268cfa384409770cd6988e54b386ae286c0f3d1 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: gdb-7.12-branch
Commit: 8268cfa384409770cd6988e54b386ae286c0f3d1

[AArch64] Track FP registers in prologue analyzer

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

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

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

gdb:

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

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


^ permalink raw reply	[flat|nested] 59+ messages in thread
* [binutils-gdb/gdb-7.12-branch] Bump GDB version number to 7.12.0.DATE-git.
@ 2016-10-07 18:04 sergiodj+buildbot
  2016-10-07 18:23 ` Failures on Fedora-x86_64-native-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 59+ messages in thread
From: sergiodj+buildbot @ 2016-10-07 18:04 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 856c9a7506cb86bedeb1402f03266b5b6fb2c431 ***

Author: Joel Brobecker <brobecker@adacore.com>
Branch: gdb-7.12-branch
Commit: 856c9a7506cb86bedeb1402f03266b5b6fb2c431

Bump GDB version number to 7.12.0.DATE-git.

gdb/ChangeLog:

	* version.in: Set GDB version number to 7.12.0.DATE-git.


^ permalink raw reply	[flat|nested] 59+ messages in thread
* [binutils-gdb/gdb-7.12-branch] Set GDB version number to 7.12.
@ 2016-10-07 17:29 sergiodj+buildbot
  2016-10-07 17:53 ` Failures on Fedora-x86_64-native-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 59+ messages in thread
From: sergiodj+buildbot @ 2016-10-07 17:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 013fd7c2f84387f218364f6cc95e16708dfba28e ***

Author: Joel Brobecker <brobecker@adacore.com>
Branch: gdb-7.12-branch
Commit: 013fd7c2f84387f218364f6cc95e16708dfba28e

Set GDB version number to 7.12.

gdb/ChangeLog:

	* version.in: Set GDB version number to 7.12.


^ permalink raw reply	[flat|nested] 59+ messages in thread
* [binutils-gdb/gdb-7.12-branch] mips-tdep: Make FCRs always 32-bit
@ 2016-10-06 19:26 sergiodj+buildbot
  2016-10-06 21:23 ` Failures on Fedora-x86_64-native-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 59+ messages in thread
From: sergiodj+buildbot @ 2016-10-06 19:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1ce1f6debf17be7a5121efa0684f0ec1449f8fc4 ***

Author: Maciej W. Rozycki <macro@imgtec.com>
Branch: gdb-7.12-branch
Commit: 1ce1f6debf17be7a5121efa0684f0ec1449f8fc4

mips-tdep: Make FCRs always 32-bit

Fix a regression from commit f8b73d13b7ca ("Target-described register
support for MIPS"),
<https://sourceware.org/ml/gdb-patches/2007-05/msg00340.html>,
<https://sourceware.org/ml/gdb-patches/2007-06/msg00256.html>, which
caused Floating Point Control Registers (FCRs) to be shown as 64-bit
with 64-bit targets.

This came from the legacy register format where all raw registers
matched the width of the architecture regardless of their actual size.
The correct size was then set in `mips_register_type' for cooked
registers presented to the user, which in the case of FCRs meant the
cooked size was always forced to 32 bits, reflecting their actual
hardware size, even though the raw format carried them in 64-bit
quantities on 64-bit targets.  The upper 32 bits carried in the raw FCR
format have always been don't-cares, not actually retrieved from
hardware and never written back.

With the introduction of XML register descriptions the layout of
previously defined raw registers has been preserved, so as to keep
existing register handling code unchanged and make it easier for GDB and
`gdbserver' to interact with each other whether neither, either or both
parties talking over RSP support XML register descriptions.  For the
XML-described case however `mips_register_type' is not used in raw to
cooked register conversion, so any special cases coded there are not
taken into account.

Instead a new function, `mips_pseudo_register_type', has been introduced
to handle size conversion, however lacking the special case for FCRs for
the Linux and the now defunct IRIX target.  The correct size has been
maintained for embedded targets however, due to the bundling of FCRs
with the embedded registers under the `rawnum >= MIPS_EMBED_FP0_REGNUM +
32' condition.

Add the missing case to `mips_pseudo_register_type' then, referring to
the FCR indices explicitly, and observing that between
`MIPS_EMBED_FP0_REGNUM + 32' and `MIPS_FIRST_EMBED_REGNUM' there is an
unused register slot whose contents are ignored so with the removal of
embedded FCRs from under that condition we don't have to care about it
and we can refer to the embedded registers starting from
MIPS_FIRST_EMBED_REGNUM instead.

Add a test case too so that we have means to check automatically that
the correct user-visible size of FCRs is maintained.

	gdb/
	* mips-tdep.c (mips_pseudo_register_type): Make FCRs always
	32-bit.

	gdb/testsuite/
	* gdb.arch/mips-fcr.exp: New test.
	* gdb.arch/mips-fcr.c: Source for the new test.
(cherry picked from commit 78b86327b5301231005b08a7c589b2b58e6b4322)


^ permalink raw reply	[flat|nested] 59+ messages in thread
* [binutils-gdb/gdb-7.12-branch] mips-tdep: Rearrange comments in `mips_pseudo_register_type'
@ 2016-10-06 19:23 sergiodj+buildbot
  2016-10-06 20:34 ` Failures on Fedora-x86_64-native-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 59+ messages in thread
From: sergiodj+buildbot @ 2016-10-06 19:23 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f92cb42932ec343d328f7dbd54d9ca5b542e322e ***

Author: Maciej W. Rozycki <macro@imgtec.com>
Branch: gdb-7.12-branch
Commit: f92cb42932ec343d328f7dbd54d9ca5b542e322e

mips-tdep: Rearrange comments in `mips_pseudo_register_type'

Rearrange comments throughout `mips_pseudo_register_type', placing them
ahead the condtionals they apply to consistently.

	gdb/
	* mips-tdep.c (mips_pseudo_register_type): Rearrange comments
	throughout.
(cherry picked from commit a6912260f813b1493efefd27cbcb6a73d933accc)


^ permalink raw reply	[flat|nested] 59+ messages in thread
* [binutils-gdb/gdb-7.12-branch] testsuite: solib-disc: Use `standard_output_file'
@ 2016-10-06 19:21 sergiodj+buildbot
  2016-10-06 19:58 ` Failures on Fedora-x86_64-native-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 59+ messages in thread
From: sergiodj+buildbot @ 2016-10-06 19:21 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8ff5432c0c9912efc43f92837243aecfcf1c1098 ***

Author: Maciej W. Rozycki <macro@imgtec.com>
Branch: gdb-7.12-branch
Commit: 8ff5432c0c9912efc43f92837243aecfcf1c1098

testsuite: solib-disc: Use `standard_output_file'

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

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

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

	gdb/testsuite/
	* gdb.base/solib-disc.exp: Use `standard_output_file'
	throughout.
(cherry picked from commit 7470adbb872d5363580eb5e0a8dbb231c286ee4c)


^ permalink raw reply	[flat|nested] 59+ messages in thread
* [binutils-gdb/gdb-7.12-branch] stack: fix gdb.dwarf2/dw2-undefined-ret-addr.exp regression
@ 2016-10-06 15:41 sergiodj+buildbot
  2016-10-06 16:05 ` Failures on Fedora-x86_64-native-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 59+ messages in thread
From: sergiodj+buildbot @ 2016-10-06 15:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3929b7e909b48a20d5dac6631e519f3b6b2ac84e ***

Author: Markus Metzger <markus.t.metzger@intel.com>
Branch: gdb-7.12-branch
Commit: 3929b7e909b48a20d5dac6631e519f3b6b2ac84e

stack: fix gdb.dwarf2/dw2-undefined-ret-addr.exp regression

Commit a038fa3e14a4 stack: check frame_unwind_caller_id adds a frame_id check to
frame_info and treats a missing frame_id as NOT_AVAILABLE_ERROR.  This causes a
regression in gdb.dwarf2/dw2-undefined-ret-addr.exp.

Treat a missing frame_id as OPTIMIZED_OUT_ERROR instead.

See also https://sourceware.org/ml/gdb-patches/2016-07/msg00273.html.


^ permalink raw reply	[flat|nested] 59+ messages in thread
* [binutils-gdb/gdb-7.12-branch] Introduce cleanup to restore current_uiout
@ 2016-10-03 23:07 sergiodj+buildbot
  2016-10-03 23:26 ` Failures on Fedora-x86_64-native-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 59+ messages in thread
From: sergiodj+buildbot @ 2016-10-03 23:07 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 33de0b1741b1939dd5384e54a858e71d2029a365 ***

Author: Simon Marchi <simark@simark.ca>
Branch: gdb-7.12-branch
Commit: 33de0b1741b1939dd5384e54a858e71d2029a365

Introduce cleanup to restore current_uiout

Make a globally available cleanup from a pre-existing one in infrun.c.
This is used in a following patch.

gdb/ChangeLog:

	* infrun.c (restore_current_uiout_cleanup): Move to ui-out.c.
	(print_stop_event): Use make_cleanup_restore_current_uiout.
	* python/python.c (execute_gdb_command): Likewise.
	* ui-out.c (restore_current_uiout_cleanup): Move from infrun.c.
	(make_cleanup_restore_current_uiout): New function definition.
	* ui-out.h (make_cleanup_restore_current_uiout): New function
	declaration.
	* utils.c (do_restore_ui_out): Remove.
	(make_cleanup_restore_ui_out): Remove.
	* utils.h (make_cleanup_restore_ui_out): Remove.


^ permalink raw reply	[flat|nested] 59+ messages in thread
* [binutils-gdb/gdb-7.12-branch] Fix PR 20345 - call_function_by_hand_dummy: Assertion `tp->thread_fsm == &sm->thread_fsm' failed
@ 2016-09-29  7:11 sergiodj+buildbot
  2016-09-29  8:20 ` Failures on Fedora-x86_64-native-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 59+ messages in thread
From: sergiodj+buildbot @ 2016-09-29  7:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 629ad95de4e61ac78f49e1abf4592dbc1fe84d96 ***

Author: Pedro Alves <palves@redhat.com>
Branch: gdb-7.12-branch
Commit: 629ad95de4e61ac78f49e1abf4592dbc1fe84d96

Fix PR 20345 - call_function_by_hand_dummy: Assertion `tp->thread_fsm == &sm->thread_fsm' failed

If you run an infcall from the command line, and immediately after run
some other command, GDB incorrectly processes the other command before
the infcall finishes.

The problem is that the fix for PR gdb/20418 (Problems with
synchronous commands and new-ui, git 3eb7562a983b) moved the
add_file_handler/delete_file_handler calls out of
target_terminal_$foo, and missed adjusting the infcall code.

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

	* infcall.c (run_inferior_call): Remove input from the event
	loop while running the infcall.

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

	* gdb.base/infcall-input.c: New file.
	* gdb.base/infcall-input.exp: New file.


^ permalink raw reply	[flat|nested] 59+ messages in thread
* [binutils-gdb/gdb-7.12-branch] Keep reserved bits in CPSR on write
@ 2016-09-21 16:27 sergiodj+buildbot
  2016-09-21 16:56 ` Failures on Fedora-x86_64-native-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 59+ messages in thread
From: sergiodj+buildbot @ 2016-09-21 16:27 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 61f97a2f940e36d4b4c87ef5b28a49e6834f8e68 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: gdb-7.12-branch
Commit: 61f97a2f940e36d4b4c87ef5b28a49e6834f8e68

Keep reserved bits in CPSR on write

In patch https://sourceware.org/ml/gdb-patches/2016-04/msg00529.html
I cleared reserved bits when reading CPSR.  It makes a problem that
these bits (zero) are written back to kernel through ptrace, and it
changes the state of the processor on some recent kernel, which is
unexpected.

In this patch, I keep these reserved bits when write CPSR back to
hardware.

gdb:

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

	* aarch32-linux-nat.c (aarch32_gp_regcache_collect): Keep
	bits 20 to 23.

gdb/gdbserver:

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

	* linux-aarch32-low.c (arm_fill_gregset): Keep bits 20 to
	23.


^ permalink raw reply	[flat|nested] 59+ messages in thread
* [binutils-gdb/gdb-7.12-branch] Backport lastest POWER9 support to match final ISA 3.0 documentation.
@ 2016-09-17  5:25 sergiodj+buildbot
  2016-09-17  5:50 ` Failures on Fedora-x86_64-native-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 59+ messages in thread
From: sergiodj+buildbot @ 2016-09-17  5:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 36d46af3d3e7dadcbac433ea42d0247a517cd782 ***

Author: Peter Bergner <bergner@vnet.ibm.com>
Branch: gdb-7.12-branch
Commit: 36d46af3d3e7dadcbac433ea42d0247a517cd782

Backport lastest POWER9 support to match final ISA 3.0 documentation.

opcodes/
	Apply from master.
	2016-09-14  Peter Bergner <bergner@vnet.ibm.com>

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

gas/
	Apply from master.
	2016-09-14  Peter Bergner <bergner@vnet.ibm.com>

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


^ permalink raw reply	[flat|nested] 59+ messages in thread
* [binutils-gdb/gdb-7.12-branch] Introduce make_cleanup_restore_current_ui
@ 2016-09-07  2:09 sergiodj+buildbot
  2016-09-07  2:47 ` Failures on Fedora-x86_64-native-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 59+ messages in thread
From: sergiodj+buildbot @ 2016-09-07  2:09 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 751b0f7dcfee83f60c1224790b9665c92be50fd8 ***

Author: Pedro Alves <palves@redhat.com>
Branch: gdb-7.12-branch
Commit: 751b0f7dcfee83f60c1224790b9665c92be50fd8

Introduce make_cleanup_restore_current_ui

Just a tidy, no functional changes.

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

	* event-top.c (restore_ui_cleanup): Now static.
	(make_cleanup_restore_current_ui): New function.
	(switch_thru_all_uis_init): Use it.
	* infcall.c (call_thread_fsm_should_stop): Use it.
	* infrun.c (fetch_inferior_event): Use it.
	* top.c (new_ui_command): Use it.
	* top.h (restore_ui_cleanup): Delete declaration.
	(make_cleanup_restore_current_ui): New declaration.


^ permalink raw reply	[flat|nested] 59+ messages in thread
* [binutils-gdb/gdb-7.12-branch] Fix lwp_suspend/unsuspend imbalance in linux_wait_1
@ 2016-09-01  8:54 sergiodj+buildbot
  2016-09-01  9:43 ` Failures on Fedora-x86_64-native-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 59+ messages in thread
From: sergiodj+buildbot @ 2016-09-01  8:54 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 305a161d11c4b5801a0e135fec5d77f3d64f121f ***

Author: Antoine Tremblay <antoine.tremblay@ericsson.com>
Branch: gdb-7.12-branch
Commit: 305a161d11c4b5801a0e135fec5d77f3d64f121f

Fix lwp_suspend/unsuspend imbalance in linux_wait_1

This patch fixes imbalanced lwp_suspend/unsuspend calls caused by the
premature choosing of another event for fairness.

select_event_lwp would switch the event before a call to
unsuspend_all_lwps, thus it would be called with the wrong event.

This caused an assertion failure: unsuspend LWP xx, suspended=-1 when
testing  gdb.threads/non-stop-fair-events.exp with ARM range stepping in
GDBServer.

This patch moves the switch of event after the unsuspend/unstop calls.

No regressions, tested on ubuntu 14.04 ARMv7 and x86.
With gdbserver-native.

gdb/gdbserver/ChangeLog:

	* linux-low.c (linux_wait_1): Move event switch after unsuspend_lwps.


^ permalink raw reply	[flat|nested] 59+ messages in thread
* [binutils-gdb/gdb-7.12-branch] Fix order of inferiors in "thread apply all"
@ 2016-08-31 10:26 sergiodj+buildbot
  2016-08-31 11:43 ` Failures on Fedora-x86_64-native-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 59+ messages in thread
From: sergiodj+buildbot @ 2016-08-31 10:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bb109f2e48adf783a861eb0d1de6f495e6b5288a ***

Author: Andreas Arnez <arnez@linux.vnet.ibm.com>
Branch: gdb-7.12-branch
Commit: bb109f2e48adf783a861eb0d1de6f495e6b5288a

Fix order of inferiors in "thread apply all"

This inserts missing parentheses in the calculation of the comparison
result between two different inferior numbers.  The problem was found by
Philipp Rudo.

gdb/ChangeLog:

	* thread.c (tp_array_compar): Insert missing parentheses.

gdb/testsuite/ChangeLog:

	* gdb.multi/tids.exp: Test "thread apply all".


^ permalink raw reply	[flat|nested] 59+ messages in thread
* [binutils-gdb/gdb-7.12-branch] Allow resetting an empty inferior-tty
@ 2016-08-24 22:31 sergiodj+buildbot
  2016-08-25  1:56 ` Failures on Fedora-x86_64-native-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 59+ messages in thread
From: sergiodj+buildbot @ 2016-08-24 22:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2b3eaab2c3eadd12bbd56499c00dca8cefb81552 ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: gdb-7.12-branch
Commit: 2b3eaab2c3eadd12bbd56499c00dca8cefb81552

Allow resetting an empty inferior-tty

This patch allows the user to set the inferior-tty to "empty", in order
to come back to the default behaviour of using the same tty as gdb is
using.

This is already supported in MI (and tested in gdb.mi/mi-basics.exp).

I added a new test, set-inferior-tty.exp, where I test only the setting
and unsetting of the parameter.  It would be nice to actually test that
the inferior output properly goes to the separate tty, but that will be
for another day.

gdb/ChangeLog:

	* infcmd.c (set_inferior_io_terminal): Set inferior terminal to
	NULL if terminal_name is an empty string.
	(_initialize_infcmd): Make the argument of "set inferior-tty"
	optional, mention it in the help doc.

gdb/doc/ChangeLog:

	* gdb.texinfo (Input/Output): Mention possibility to unset
	inferior-tty.

gdb/testsuite/ChangeLog:

	* gdb.base/set-inferior-tty.exp: New file.
	* gdb.base/set-inferior-tty.c: New file.


^ permalink raw reply	[flat|nested] 59+ messages in thread
* [binutils-gdb/gdb-7.12-branch] x32: Fix gdb.trace/mi-trace-frame-collected.exp
@ 2016-08-24  8:29 sergiodj+buildbot
  2016-08-24 11:26 ` Failures on Fedora-x86_64-native-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 59+ messages in thread
From: sergiodj+buildbot @ 2016-08-24  8:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 644e90fe669bbfe1d15d1018b4fc136af3aab424 ***

Author: Pedro Alves <palves@redhat.com>
Branch: gdb-7.12-branch
Commit: 644e90fe669bbfe1d15d1018b4fc136af3aab424

x32: Fix gdb.trace/mi-trace-frame-collected.exp

gdb.trace/mi-trace-frame-collected.exp has a couple failures on x32:

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

gdb.log:

 -trace-frame-collected
 ^done,explicit-variables=[{name="gdb_char_test",value="0 '\\000'"}],computed-expressions=[],registers=[{number="16",value="0x4004dc"},{number="204",value="0x4004dc"}],tvars
 =[],memory=[{address="0x00601060",length="1"}]
 (gdb)
 FAIL: gdb.trace/mi-trace-frame-collected.exp: live: -trace-frame-collected (register)
[...]
 -trace-frame-collected
 ^done,explicit-variables=[{name="gdb_char_test",value="0 '\\000'"}],computed-expressions=[],registers=[{number="16",value="0x4004dc"},{number="204",value="0x4004dc"}],tvars
 =[],memory=[{address="0x00601060",length="1"}]
 (gdb)
 FAIL: gdb.trace/mi-trace-frame-collected.exp: tfile: -trace-frame-collected (register)

This test only collects the PC, and thus expects to only see one
register in the output of -trace-frame-collected.  However, while on
the 64-bit ABI gdb only exposes 64-bit $pc/$rip (register 16 above),
on x32, GDB exposes 32-bit $eip as well, as a pseudo-register
(register 204 above).  Thus, collecting $pc/$rip automatically always
collects $eip as well.

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

	* gdb.trace/mi-trace-frame-collected.exp
	(test_trace_frame_collected): On x32, expect two registers.


^ permalink raw reply	[flat|nested] 59+ messages in thread
* [binutils-gdb/gdb-7.12-branch] x32: Avoid unsigned long when installing fast tracepoint jump pads
@ 2016-08-24  2:15 sergiodj+buildbot
  2016-08-24  2:46 ` Failures on Fedora-x86_64-native-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 59+ messages in thread
From: sergiodj+buildbot @ 2016-08-24  2:15 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 53e8498437380263d5321bf841c6de526e676347 ***

Author: Pedro Alves <palves@redhat.com>
Branch: gdb-7.12-branch
Commit: 53e8498437380263d5321bf841c6de526e676347

x32: Avoid unsigned long when installing fast tracepoint jump pads

We're casting through unsigned long to write a 64-bit immediate
operand of movabs (the comment said movl, but that was incorrect).
The problem is that unsigned long is 32-bit on x32, so we were writing
fewer bytes than necessary.

Fix this by using an 8 byte memcpy like in other similar places in the
function.

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

	* linux-x86-low.c (amd64_install_fast_tracepoint_jump_pad): Fix
	comment.  Use memcpy instead of casting through unsigned long.


^ permalink raw reply	[flat|nested] 59+ messages in thread
* [binutils-gdb/gdb-7.12-branch] x32 Fast tracepoints: Customize jump pad address
@ 2016-08-24  1:34 sergiodj+buildbot
  2016-08-24  2:03 ` Failures on Fedora-x86_64-native-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 59+ messages in thread
From: sergiodj+buildbot @ 2016-08-24  1:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 69389fd9fba29ab078f63d366612028fd1de25ab ***

Author: Pedro Alves <palves@redhat.com>
Branch: gdb-7.12-branch
Commit: 69389fd9fba29ab078f63d366612028fd1de25ab

x32 Fast tracepoints: Customize jump pad address

MAP_32BIT is ignored on x32, meaning the jump pad can end up somewhere
between 2GB and 4GB, too far away from the executable for 5-byte
relative jumps (JMP rel32).  So on x32, try explicitly placing the
jump pad near the middle of the available address space.

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

	* linux-amd64-ipa.c (alloc_jump_pad_buffer) [__ILP32__]: Try
	allocating around 0x80000000.


^ permalink raw reply	[flat|nested] 59+ messages in thread
* [binutils-gdb/gdb-7.12-branch] Fix PR20494 - User input stops being echoed in CLI
@ 2016-08-23 19:14 sergiodj+buildbot
  2016-08-23 21:40 ` Failures on Fedora-x86_64-native-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 59+ messages in thread
From: sergiodj+buildbot @ 2016-08-23 19:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e24e88f9de8e4d34c052864c42aed10778f0174a ***

Author: Pedro Alves <palves@redhat.com>
Branch: gdb-7.12-branch
Commit: e24e88f9de8e4d34c052864c42aed10778f0174a

Fix PR20494 - User input stops being echoed in CLI

This patch fixes a problem that problem triggers if you start an
inferior, e.g., with the "start" command, in a UI created with the
new-ui command, and then run a foreground execution command in the
main UI.  Once the program stops for the latter command, typing in the
main UI no longer echoes back to the user.

The problem revolves around this:

- gdb_has_a_terminal computes its result lazily, on first call.

  that is what saves gdb's initial main UI terminal state (the UI
  associated with stdin):

          our_terminal_info.ttystate = serial_get_tty_state (stdin_serial);

  This is the state that target_terminal_ours() restores.

- In this scenario, the gdb_has_a_terminal function happens to be
  first ever called from within the target_terminal_init call in
  startup_inferior:

      (top-gdb) bt
      #0  gdb_has_a_terminal () at src/gdb/inflow.c:157
      #1  0x000000000079db22 in child_terminal_init_with_pgrp () at src/gdb/inflow.c:217
       [...]
      #4  0x000000000065bacb in target_terminal_init () at src/gdb/target.c:456
      #5  0x00000000004676d2 in startup_inferior () at src/gdb/fork-child.c:531
       [...]
      #7  0x000000000046b168 in linux_nat_create_inferior () at src/gdb/linux-nat.c:1112
       [...]
      #9  0x00000000005f20c9 in start_command (args=0x0, from_tty=1) at src/gdb/infcmd.c:657

If the command to start the inferior is issued on the main UI, then
readline will have deprepped the terminal when we reach the above, and
the problem doesn't appear.

If however the command is issued on a non-main UI, then when we reach
that gdb_has_a_terminal call, the main UI's terminal state is still
set to whatever readline has sets it to in rl_prep_terminal, which
happens to have echo disabled.  Later, when the following synchronous
execution command finishes, we'll call target_terminal_ours to restore
gdb's the main UI's terminal settings, and that restores the terminal
state with echo disabled...

Conceptually, the fix is to move the gdb_has_a_terminal call earlier,
to someplace during GDB initialization, before readline/ncurses have
had a chance to change terminal settings.  Turns out that
"set_initial_gdb_ttystate" is exactly such a place.

I say conceptually, because the fix actually inlines the
gdb_has_a_terminal part that saves the terminal state in
set_initial_gdb_ttystate and then simplifies gdb_has_a_terminal, since
there's no point in making gdb_has_a_terminal do lazy computation.

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

	PR gdb/20494
	* inflow.c (our_terminal_info, initial_gdb_ttystate): Update
	comments.
	(enum gdb_has_a_terminal_flag_enum, gdb_has_a_terminal_flag):
	Delete.
	(set_initial_gdb_ttystate): Record our_terminal_info here too,
	instead of ...
	(gdb_has_a_terminal): ... here.  Reimplement in terms of
	initial_gdb_ttystate.  Make static.
	* terminal.h (gdb_has_a_terminal): Delete declaration.
	(set_initial_gdb_ttystate): Add comment.
	* top.c (show_interactive_mode): Use input_interactive_p instead
	of gdb_has_a_terminal.

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

	PR gdb/20494
	* gdb.base/new-ui-echo.c: New file.
	* gdb.base/new-ui-echo.exp: New file.


^ permalink raw reply	[flat|nested] 59+ messages in thread
* [binutils-gdb/gdb-7.12-branch] Fix signals-state-child.exp in remote testing
@ 2016-08-23 17:02 sergiodj+buildbot
  2016-08-23 17:27 ` Failures on Fedora-x86_64-native-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 59+ messages in thread
From: sergiodj+buildbot @ 2016-08-23 17:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 22dc25f77bdff5954af60abd7a098ea6e76ad1f9 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: gdb-7.12-branch
Commit: 22dc25f77bdff5954af60abd7a098ea6e76ad1f9

Fix signals-state-child.exp in remote testing

Remote testing isn't considered in signals-state-child.exp, so the it
fails like

shell diff -s /scratch/yao/gdb/build-git/aarch64-linux-gnu/gdb/testsuite/outputs/gdb.base/signals-state-child/standalone.txt /scratch/yao/gdb/build-git/aarch64-linux-gnu/gdb/testsuite/outputs/gdb.base/signals-state-child/gdb.txt^M
diff: /scratch/yao/gdb/build-git/aarch64-linux-gnu/gdb/testsuite/outputs/gdb.base/signals-state-child/standalone.txt: No such file or directory^M
(gdb) FAIL: gdb.base/signals-state-child.exp: signals states are identical

This patch is to fix it.

gdb/testsuite:

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

	* gdb.base/signals-state-child.exp: Set variables gdb_txt and
	standalone_txt.  Delete gdb_txt and standalone_txt on host
	and target.  Spawn the binary on target.  Copy files from
	target to host.


^ permalink raw reply	[flat|nested] 59+ messages in thread
* [binutils-gdb/gdb-7.12-branch] [AArch64] Match instruction "STP with base register" in prologue
@ 2016-08-19 21:36 sergiodj+buildbot
  2016-08-20  0:14 ` Failures on Fedora-x86_64-native-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 59+ messages in thread
From: sergiodj+buildbot @ 2016-08-19 21:36 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ded7f5d81cab3eb02cca835f0c9bd9525f35f268 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: gdb-7.12-branch
Commit: ded7f5d81cab3eb02cca835f0c9bd9525f35f268

[AArch64] Match instruction "STP with base register" in prologue

Nowadays, we only match pre-indexed STP in prologue.  Due to the change
in gcc, https://gcc.gnu.org/ml/gcc-patches/2016-07/msg01933.html, it
may generate "STP with base register" in prologue, which GDB doesn't
handle.  That is to say, previously GCC generates prologue like this,

 sub sp, sp, #490
 stp x29, x30, [sp, #-96]!
 mov x29, sp

with the gcc patch above, GCC generates prologue like like this,

 sub sp, sp, #4f0
 stp x29, x30, [sp]
 mov x29, sp

This patch is to teach GDB to recognize this instruction in prologue
analysis.

gdb:

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

	* aarch64-tdep.c (aarch64_analyze_prologue): Handle register
	based STP instruction.


^ permalink raw reply	[flat|nested] 59+ messages in thread
* [binutils-gdb/gdb-7.12-branch] [GDB] Fix builds broken by proc-service changes.
@ 2016-08-15 21:31 sergiodj+buildbot
  2016-08-15 23:40 ` Failures on Fedora-x86_64-native-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 59+ messages in thread
From: sergiodj+buildbot @ 2016-08-15 21:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2e9ffae9c70279ba7b226b9bf5f2f9b20968375c ***

Author: Matthew Wahab <matthew.wahab@arm.com>
Branch: gdb-7.12-branch
Commit: 2e9ffae9c70279ba7b226b9bf5f2f9b20968375c

[GDB] Fix builds broken by proc-service changes.

GLIBC BZ#20311 introduced a change to install proc_service.h so that gdb
didn't have to use the version it embeds in gdb_proc_service.h. The
embedded version is guarded by HAVE_PROC_SERVICE_H and
gdb_proc_service.h has a number other of includes and definitions, all
of which are uncondional except for an include for gregset.h. This is
only included if HAVE_PROC_SERIVCE_H is not defined.

This causes a build failure when cross compiling gdb with the latest
glibc because type definitions in gregset are used independently of
HAVE_PROC_SERIVCE_H. In particular, they are used in gdb_proc_service.h
when PRFPREGSET_T_BROKEN is set.

The error messages on the failure are
----
binutils-gdb/gdb/gdb_proc_service.h:173:9: error: gdb_fpregset_t does
not name a type; did you mean elf_fpregset_t?
 typedef gdb_fpregset_t gdb_prfpregset_t;
         ^~~~~~~~~~~~~~
         elf_fpregset_t

binutils-gdb/gdb/gdb_proc_service.h:173:9: error: gdb_fpregset_t does
not name a type; did you mean elf_fpregset_t?
 typedef gdb_fpregset_t gdb_prfpregset_t;
         ^~~~~~~~~~~~~~
         elf_fpregset_t

binutils-gdb/gdb/proc-service.c:218:15: error: gdb_prfpregset_t does
not name a type; did you mean gdb_fpregset_t?
         const gdb_prfpregset_t *fpregset)
               ^~~~~~~~~~~~~~~~
               gdb_fpregset_t
----

This patch moves the include for gregset.h to before the code guarded by
HAVE_PROC_SERIVCE_H, so that it is always included. This is enough to
fix the build.

2016-08-15  Matthew Wahab  <matthew.wahab@arm.com>

	PR gdb/20457
	* gdb_proc_service.h: Add an include of gregset.h
        [!HAVE_PROC_SERVICE_H]: Remove the include of gregset.h.


^ permalink raw reply	[flat|nested] 59+ messages in thread
* [binutils-gdb/gdb-7.12-branch] Fix warning in gdb.base/signals-state-child.c
@ 2016-08-12 15:06 sergiodj+buildbot
  2016-08-12 16:07 ` Failures on Fedora-x86_64-native-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 59+ messages in thread
From: sergiodj+buildbot @ 2016-08-12 15:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c0c8e5aea12c938a1e73c1d32912b094c3329288 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: gdb-7.12-branch
Commit: c0c8e5aea12c938a1e73c1d32912b094c3329288

Fix warning in gdb.base/signals-state-child.c

I see the following warning when running signals-state-child.exp.

gdb/testsuite/gdb.base/signals-state-child.c:77:4: warning: too many arguments for format [-Wformat-extra-args]
    fprintf (out, "sigaction={sa_handler=", i);
    ^

this patch is to remove the argument from fprintf.

gdb/testsuite:

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

	* gdb.base/signals-state-child.c (main): Remove "i" from fprintf's
	argument list.


^ permalink raw reply	[flat|nested] 59+ messages in thread
* [binutils-gdb/gdb-7.12-branch] Fix fallout from gdb/20413's fix (x32: linux_ptrace_test_ret_to_nx: Cannot PTRACE_PEEKUSER)
@ 2016-08-12  6:37 sergiodj+buildbot
  2016-08-12 10:19 ` Failures on Fedora-x86_64-native-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 59+ messages in thread
From: sergiodj+buildbot @ 2016-08-12  6:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e565c44e294111fdc2b84396917b0c4ffed916fb ***

Author: Pedro Alves <palves@redhat.com>
Branch: gdb-7.12-branch
Commit: e565c44e294111fdc2b84396917b0c4ffed916fb

Fix fallout from gdb/20413's fix (x32: linux_ptrace_test_ret_to_nx: Cannot PTRACE_PEEKUSER)

Fixes, on NIOS GNU/Linux:

  In file included from
  /scratch/mbilal/nois-lite/src/gdb-trunk/gdb/gdbserver/../nat/linux-ptrace.c:26:0:
  /scratch/mbilal/nois-lite/src/gdb-trunk/gdb/gdbserver/../gregset.h:27:23:
  error: unknown type name 'gregset_t'
   #define GDB_GREGSET_T gregset_t
			 ^

Fix this by including sys/procfs.h directly.  We shouldn't really be
including a gdb-only header in a gdb/nat/ file, anyway.  Whoops.

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

	PR gdb/20413
	* nat/linux-ptrace.c: Include <sys/procfs.h> instead of
	"gregset.h".


^ permalink raw reply	[flat|nested] 59+ messages in thread
* [binutils-gdb/gdb-7.12-branch] Plumb enum remove_bp_reason all the way to target_remove_breakpoint
@ 2016-08-11  3:36 sergiodj+buildbot
  2016-08-11  4:05 ` Failures on Fedora-x86_64-native-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 59+ messages in thread
From: sergiodj+buildbot @ 2016-08-11  3:36 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT aac9c6220f36cea74d13cd02cce6c64d49f41f34 ***

Author: Pedro Alves <palves@redhat.com>
Branch: gdb-7.12-branch
Commit: aac9c6220f36cea74d13cd02cce6c64d49f41f34

Plumb enum remove_bp_reason all the way to target_remove_breakpoint

So the target knows whether we're detaching breakpoints.
Nothing uses the parameter in this patch yet.

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

	PR gdb/19187
	* break-catch-sig.c (signal_catchpoint_remove_location): Adjust
	interface.
	* break-catch-syscall.c (remove_catch_syscall):
	* breakpoint.c (enum remove_bp_reason): Moved to breakpoint.h.
	(remove_breakpoint_1): Pass 'reason' down.
	(remove_catch_fork, remove_catch_vfork, remove_catch_solib)
	(remove_catch_exec, remove_watchpoint, remove_masked_watchpoint)
	(base_breakpoint_remove_location, bkpt_remove_location)
	(bkpt_probe_remove_location, bkpt_probe_remove_location): Adjust
	interface.
	* breakpoint.h (enum remove_bp_reason): Moved here from
	breakpoint.c.
	(struct breakpoint_ops) <remove_location>: Add 'reason' parameter.
	* corelow.c (core_remove_breakpoint): New function.
	(init_core_ops): Install it as to_remove_breakpoint method.
	* exec.c (exec_remove_breakpoint): New function.
	(init_exec_ops): Install it as to_remove_breakpoint method.
	* mem-break.c (memory_remove_breakpoint): Adjust interface.
	* record-btrace.c (record_btrace_remove_breakpoint): Adjust
	interface.
	* record-full.c (record_full_remove_breakpoint)
	(record_full_core_remove_breakpoint): Adjust interface.
	* remote.c (remote_remove_breakpoint): Adjust interface.
	* target-debug.h (target_debug_print_enum_remove_bp_reason): New
	macro.
	* target-delegates.c: Regenerate.
	* target.c (target_remove_breakpoint): Add 'reason' parameter.
	* target.h (struct target_ops) <to_remove_breakpoint>: Add
	'reason' parameter.
	(target_remove_breakpoint, memory_remove_breakpoint): Add 'reason'
	parameter.


^ permalink raw reply	[flat|nested] 59+ messages in thread
* [binutils-gdb/gdb-7.12-branch] Fix PR mi/20431 - Missing MI prompts after sync execution MI command (-exec-continue, etc.) errors
@ 2016-08-10  2:14 sergiodj+buildbot
  2016-08-10  3:46 ` Failures on Fedora-x86_64-native-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 59+ messages in thread
From: sergiodj+buildbot @ 2016-08-10  2:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4d38db46f6f6480ee33844164383ce40e5fc2440 ***

Author: Pedro Alves <palves@redhat.com>
Branch: gdb-7.12-branch
Commit: 4d38db46f6f6480ee33844164383ce40e5fc2440

Fix PR mi/20431 - Missing MI prompts after sync execution MI command (-exec-continue, etc.) errors

gdb 7.11 introduced an MI regression: a failing MI sync execution
command misses printing the MI prompt, and then all subsequent command
miss it too:

 $ gdb-7.11.1 -i=mi
 [...]
 p 1
 &"p 1\n"
 ~"$1 = 1"
 ~"\n"
 ^done
 (gdb)                                        <<< prompted ok
 -exec-continue
 ^error,msg="The program is not being run."   <<< missing prompt after this
 print 1
 &"print 1\n"
 ~"$2 = 1"
 ~"\n"
 ^done                                        <<< missing prompt after this


gdb 7.10.1 behaved correctly, even with "set mi-async on":

 -exec-continue
 ^error,msg="The program is not being run."
 (gdb)                                        <<< prompted ok

etc.

Bisecting points at:

  commit 0b333c5e7d6c
  Author: Pedro Alves <palves@redhat.com>
  Date:   Wed Sep 9 18:23:23 2015 +0100

      Merge async and sync code paths some more
  [...]

The problem is that when an exception is thrown, we leave the prompt
state set to PROMPT_BLOCKED, and then mi_execute_command_input_handler
doesn't print the prompt.  It used to work because before that patch,
we happened to skip disabling stdin if the current target didn't do
async (which it never does before execution).

I was surprised to find that this bug isn't caught by the testsuite,
so I made a thorough test that tests all combinations of pairs of:

 - a failing synchronous execution command
 - a failing non-execution command
 - a non-failing command

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

	PR mi/20431
	* mi/mi-main.c (mi_execute_command): Enable input and set prompt
	state to PROMPT_NEEDED.

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

	PR mi/20431
	* gdb.mi/mi-cmd-error.exp: New file.


^ permalink raw reply	[flat|nested] 59+ messages in thread
* [binutils-gdb/gdb-7.12-branch] Fix PR gdb/18653: gdb disturbs inferior's inherited signal dispositions
@ 2016-08-09 22:55 sergiodj+buildbot
  2016-08-09 23:32 ` Failures on Fedora-x86_64-native-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 59+ messages in thread
From: sergiodj+buildbot @ 2016-08-09 22:55 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 35fcb4fc81e51295d14125785765e0ea3e132cd9 ***

Author: Pedro Alves <palves@redhat.com>
Branch: gdb-7.12-branch
Commit: 35fcb4fc81e51295d14125785765e0ea3e132cd9

Fix PR gdb/18653: gdb disturbs inferior's inherited signal dispositions

gdb's (or gdbserver's) own signal handling should not interfere with
the signal dispositions their spawned children inherit.  However, it
currently does.  For example, some paths in gdb cause SIGPIPE to be
set to SIG_IGN, and as consequence, the child starts with SIGPIPE to
set to SIG_IGN too, even though gdb was started with SIGPIPE set to
SIG_DFL.

This is because the exec family of functions does not reset the signal
disposition of signals that are set to SIG_IGN:

  http://pubs.opengroup.org/onlinepubs/7908799/xsh/execve.html

  Signals set to the default action (SIG_DFL) in the calling process
  image are set to the default action in the new process
  image. Signals set to be ignored (SIG_IGN) by the calling process
  image are set to be ignored by the new process image. Signals set to
  be caught by the calling process image are set to the default action
  in the new process image (see <signal.h>).

And neither does it reset signal masks or flags.

In order to be transparent, when spawning new child processes to debug
(with "run", etc.), reset signal actions and mask back to what was
originally inherited from gdb/gdbserver's parent, just before execing
the target program to debug.

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

	PR gdb/18653
	* Makefile.in (SFILES): Add
	common/signals-state-save-restore.c.
	(HFILES_NO_SRCDIR): Add common/signals-state-save-restore.h.
	(COMMON_OBS): Add signals-state-save-restore.o.
	(signals-state-save-restore.o): New rule.
	* configure: Regenerate.
	* fork-child.c: Include "signals-state-save-restore.h".
	(fork_inferior): Call restore_original_signals_state.
	* main.c: Include "signals-state-save-restore.h".
	(captured_main): Call save_original_signals_state.
	* common/common.m4: Add sigaction to AC_CHECK_FUNCS checks.
	* common/signals-state-save-restore.c: New file.
	* common/signals-state-save-restore.h: New file.

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

	PR gdb/18653
	* Makefile.in (OBS): Add signals-state-save-restore.o.
	(signals-state-save-restore.o): New rule.
	* config.in: Regenerate.
	* configure: Regenerate.
	* linux-low.c: Include "signals-state-save-restore.h".
	(linux_create_inferior): Call
	restore_original_signals_state.
	* server.c: Include "dispositions-save-restore.h".
	(captured_main): Call save_original_signals_state.

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

	PR gdb/18653
	* gdb.base/signals-state-child.c: New file.
	* gdb.base/signals-state-child.exp: New file.
	* gdb.gdb/selftest.exp (do_steps_and_nexts): Add new pattern.


^ permalink raw reply	[flat|nested] 59+ messages in thread
* [binutils-gdb/gdb-7.12-branch] Fix PR remote/20398: File-IO write always outputs "Quit"
@ 2016-08-05 19:41 sergiodj+buildbot
  2016-08-05 20:11 ` Failures on Fedora-x86_64-native-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 59+ messages in thread
From: sergiodj+buildbot @ 2016-08-05 19:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 26fdfd0a18cf9032183a498a6c68b16f5042b1a4 ***

Author: Pedro Alves <palves@redhat.com>
Branch: gdb-7.12-branch
Commit: 26fdfd0a18cf9032183a498a6c68b16f5042b1a4

Fix PR remote/20398: File-IO write always outputs "Quit"

Commit bb7c96deb1a1 ("gdb/remote-fileio.c: Eliminate custom SIGINT
signal handler") regressed the File-IO support.

Failed output:

  (gdb) target remote :8888
  Remote debugging using :8888
  0x00008098 in _start ()
  (gdb) c
  Continuing.
  Quit
  Quit
  Quit
  Quit
  Quit
  Quit
  Quit
  Quit
  Quit
  Quit
  Quit
  [Inferior 1 (Remote target) exited normally]

Expected output:

  (gdb) target remote :8888
  Remote debugging using :8888
  0x00008098 in _start ()
  (gdb) c
  Continuing.
  i: 0
  i: 1
  i: 2
  i: 3
  i: 4
  i: 5
  i: 6
  i: 7
  i: 8
  i: 9
  [Inferior 1 (Remote target) exited normally]

The problem that the new File-IO quit handler forgets to check the
quit flag before calling throwing a quit.

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

	PR remote/20398
	* remote-fileio.c (remote_fileio_quit_handler): Check the quit
	flag before calling quit.


^ permalink raw reply	[flat|nested] 59+ messages in thread
* [binutils-gdb/gdb-7.12-branch] gdb/NEWS: Mention that C++ is now the default
@ 2016-08-05 18:42 sergiodj+buildbot
  2016-08-05 19:24 ` Failures on Fedora-x86_64-native-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 59+ messages in thread
From: sergiodj+buildbot @ 2016-08-05 18:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 842b243cf65277bca93740df9905a3c221bb1973 ***

Author: Pedro Alves <palves@redhat.com>
Branch: gdb-7.12-branch
Commit: 842b243cf65277bca93740df9905a3c221bb1973

gdb/NEWS: Mention that C++ is now the default

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

	* NEWS: Mention that GDB and GDBserver build with a C++ compiler
	by default.


^ permalink raw reply	[flat|nested] 59+ messages in thread
* [binutils-gdb/gdb-7.12-branch] gdb/configure --help: suggest --disable-build-with-cxx instead of --enable...
@ 2016-08-05 17:24 sergiodj+buildbot
  2016-08-05 17:48 ` Failures on Fedora-x86_64-native-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 59+ messages in thread
From: sergiodj+buildbot @ 2016-08-05 17:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2b8c86008c05d4ca21971fe4f680288cd28108c1 ***

Author: Pedro Alves <palves@redhat.com>
Branch: gdb-7.12-branch
Commit: 2b8c86008c05d4ca21971fe4f680288cd28108c1

gdb/configure --help: suggest --disable-build-with-cxx instead of --enable...

We build by default with a C++ compiler, but "configure --help" still
says "--enable-build-with-cxx", which hints that it is by default
disabled.  Update the --help text.

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

	* build-with-cxx.m4: Change help string to be in terms of
	--disable-build-with-cxx.
	* configure: Regenerate.

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

	* configure: Regenerate.


^ permalink raw reply	[flat|nested] 59+ messages in thread
* [binutils-gdb/gdb-7.12-branch] Determine target description for native aarch64
@ 2016-08-04 12:07 sergiodj+buildbot
  2016-08-04 13:34 ` Failures on Fedora-x86_64-native-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 59+ messages in thread
From: sergiodj+buildbot @ 2016-08-04 12:07 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f2b5d52a1d4484e55cd36de24554b51c2133386b ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: gdb-7.12-branch
Commit: f2b5d52a1d4484e55cd36de24554b51c2133386b

Determine target description for native aarch64

I find the following test fail when I test native aarch64 gdb with
arm program,

(gdb) PASS: gdb.base/attach-pie-noexec.exp: attach
set architecture arm^M
warning: Selected architecture arm is not compatible with reported target architecture aarch64^M
Architecture `arm' not recognized.^M
The target architecture is set automatically (currently aarch64)^M
(gdb) FAIL: gdb.base/attach-pie-noexec.exp: set architecture arm

GDB thinks the target is aarch64, but it isn't.  Nowadays, we are
using some entries AT_PHENT and AT_HWCAP in auxv to determine whether
the process is a 32-bit arm one or 64-bit aarch64 one, and get the
right gdbarch.  However, in the process of parsing auxv (in
inf_ptrace_auxv_parse), the size of int and data pointer of
target_gdbarch is used.  If debug program exists (in most of cases),
target_gdbarch is already set according to the debug program, which
is arm in my case.  Then, GDB can parse auxv successfully.  However,
in gdb.base/attach-pie-noexec.exp, the debug program is removed,
target_gdbarch is aarch64 when GDB parse auxv, so GDB can't parse
it successfully.

Instead of using auxv, we check the return value of ptrace NT_ARM_VFP.
If the program is an arm process, NT_ARM_VFP is OK, otherwise, error
is returned.

Additionally, we only return tdesc_arm_with_neon for arm process,
because neon is mandatory on ARMv8.

gdb:

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

	* aarch64-linux-nat.c (tdesc_arm_with_vfpv3): Remove the
	declaration.
	(aarch64_linux_read_description): Remove code on getting
	auxv and select target description on it.  Select target
	description by the result of NT_ARM_VFP ptrace request.


^ permalink raw reply	[flat|nested] 59+ messages in thread
* [binutils-gdb/gdb-7.12-branch] Update NEWS to mention Python breakpoint events
@ 2016-08-03 16:56 sergiodj+buildbot
  2016-08-03 17:21 ` Failures on Fedora-x86_64-native-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 59+ messages in thread
From: sergiodj+buildbot @ 2016-08-03 16:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 10bb85f1e551930724e87e636659b36500f44a0c ***

Author: Tom Tromey <tom@tromey.com>
Branch: gdb-7.12-branch
Commit: 10bb85f1e551930724e87e636659b36500f44a0c

Update NEWS to mention Python breakpoint events

An earlier patch added three new breakpoint-related events to the
Python API.  However, at that time, I forgot to update NEWS.  This
patch supplies the missing entry.

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

	* NEWS: Mention new Python breakpoint events.


^ permalink raw reply	[flat|nested] 59+ messages in thread
* [binutils-gdb/gdb-7.12-branch] Bump GDB version number to 7.11.90.DATE-git.
@ 2016-08-01 19:25 sergiodj+buildbot
  2016-08-01 20:23 ` Failures on Fedora-x86_64-native-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 59+ messages in thread
From: sergiodj+buildbot @ 2016-08-01 19:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7ff72836aecd3e64f3d5ef4e5e444c82ad2c7086 ***

Author: Joel Brobecker <brobecker@adacore.com>
Branch: gdb-7.12-branch
Commit: 7ff72836aecd3e64f3d5ef4e5e444c82ad2c7086

Bump GDB version number to 7.11.90.DATE-git.

gdb/ChangeLog:

	* version.in: Set GDB version number to 7.11.90.DATE-git.


^ permalink raw reply	[flat|nested] 59+ messages in thread
* [binutils-gdb/gdb-7.12-branch] Set GDB version number to 7.11.90.
@ 2016-08-01 19:05 sergiodj+buildbot
  2016-08-01 19:24 ` Failures on Fedora-x86_64-native-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 59+ messages in thread
From: sergiodj+buildbot @ 2016-08-01 19:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT aa485aad155831ed57df0eeca78b82aa6ea9b0ce ***

Author: Joel Brobecker <brobecker@adacore.com>
Branch: gdb-7.12-branch
Commit: aa485aad155831ed57df0eeca78b82aa6ea9b0ce

Set GDB version number to 7.11.90.

gdb/ChangeLog:

	* version.in: Set GDB version number to 7.11.90.


^ permalink raw reply	[flat|nested] 59+ messages in thread
end of thread, other threads:[~2017-01-21 15:06 UTC | newest]

Thread overview: 59+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-08-24  3:01 [binutils-gdb/gdb-7.12-branch] x32: gdbserver's agent bytecode JIT: fix "call" emission sergiodj+buildbot
2016-08-24  3:10 ` Failures on Fedora-x86_64-native-gdbserver-m32, branch gdb-7.12-branch sergiodj+buildbot
2016-08-24  3:40 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot
2016-08-24  4:29 ` Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot
2016-08-24  4:41 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot
2016-08-24  5:03 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot
2016-08-24  6:41 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot
2016-08-24  7:00 ` Failures on Debian-s390x-m64, " sergiodj+buildbot
2016-08-24  7:01 ` Failures on Fedora-i686, " sergiodj+buildbot
2016-08-24  7:24 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-08-24 14:09 ` Failures on Debian-i686, " sergiodj+buildbot
2016-08-24 14:47 ` Failures on Debian-i686-native-extended-gdbserver, " sergiodj+buildbot
2016-08-24 17:46 ` Failures on Fedora-ppc64be-m64, " sergiodj+buildbot
2016-08-24 17:50 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj+buildbot
2016-08-24 18:12 ` Failures on Fedora-ppc64be-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-08-24 18:18 ` Failures on Fedora-ppc64be-cc-with-index, " sergiodj+buildbot
2016-08-24 18:34 ` Failures on Fedora-ppc64le-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-08-24 19:04 ` Failures on Fedora-ppc64le-native-gdbserver-m64, " sergiodj+buildbot
2016-08-25  6:49 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot
  -- strict thread matches above, loose matches on Subject: below --
2017-01-21 14:20 [binutils-gdb/gdb-7.12-branch] Bump GDB version number to 7.12.1.DATE-git sergiodj+buildbot
2017-01-21 15:06 ` Failures on Fedora-x86_64-native-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
2017-01-20 13:17 [binutils-gdb/gdb-7.12-branch] Throw SJ/LJ exception on error in disassembly sergiodj+buildbot
2017-01-20 13:38 ` Failures on Fedora-x86_64-native-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
2017-01-01  8:58 [binutils-gdb/gdb-7.12-branch] update copyright year range in GDB files sergiodj+buildbot
2017-01-01  9:38 ` Failures on Fedora-x86_64-native-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
2016-12-20 17:36 [binutils-gdb/gdb-7.12-branch] Fix longjmp across readline w/ --enable-sjlj-exceptions toolchains sergiodj+buildbot
2016-12-20 19:00 ` Failures on Fedora-x86_64-native-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
2016-11-11  7:48 [binutils-gdb/gdb-7.12-branch] sim: mips: fix dv-tx3904cpu build error sergiodj+buildbot
2016-11-11 10:07 ` Failures on Fedora-x86_64-native-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
2016-10-25  3:26 [binutils-gdb/gdb-7.12-branch] [GDBserver] Fix conversion warning sergiodj+buildbot
2016-10-25  7:27 ` Failures on Fedora-x86_64-native-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
2016-10-12 12:26 [binutils-gdb/gdb-7.12-branch] [AArch64] Track FP registers in prologue analyzer sergiodj+buildbot
2016-10-12 12:48 ` Failures on Fedora-x86_64-native-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
2016-10-07 18:04 [binutils-gdb/gdb-7.12-branch] Bump GDB version number to 7.12.0.DATE-git sergiodj+buildbot
2016-10-07 18:23 ` Failures on Fedora-x86_64-native-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
2016-10-07 17:29 [binutils-gdb/gdb-7.12-branch] Set GDB version number to 7.12 sergiodj+buildbot
2016-10-07 17:53 ` Failures on Fedora-x86_64-native-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
2016-10-06 19:26 [binutils-gdb/gdb-7.12-branch] mips-tdep: Make FCRs always 32-bit sergiodj+buildbot
2016-10-06 21:23 ` Failures on Fedora-x86_64-native-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
2016-10-06 19:23 [binutils-gdb/gdb-7.12-branch] mips-tdep: Rearrange comments in `mips_pseudo_register_type' sergiodj+buildbot
2016-10-06 20:34 ` Failures on Fedora-x86_64-native-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
2016-10-06 19:21 [binutils-gdb/gdb-7.12-branch] testsuite: solib-disc: Use `standard_output_file' sergiodj+buildbot
2016-10-06 19:58 ` Failures on Fedora-x86_64-native-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
2016-10-06 15:41 [binutils-gdb/gdb-7.12-branch] stack: fix gdb.dwarf2/dw2-undefined-ret-addr.exp regression sergiodj+buildbot
2016-10-06 16:05 ` Failures on Fedora-x86_64-native-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
2016-10-03 23:07 [binutils-gdb/gdb-7.12-branch] Introduce cleanup to restore current_uiout sergiodj+buildbot
2016-10-03 23:26 ` Failures on Fedora-x86_64-native-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
2016-09-29  7:11 [binutils-gdb/gdb-7.12-branch] Fix PR 20345 - call_function_by_hand_dummy: Assertion `tp->thread_fsm == &sm->thread_fsm' failed sergiodj+buildbot
2016-09-29  8:20 ` Failures on Fedora-x86_64-native-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
2016-09-21 16:27 [binutils-gdb/gdb-7.12-branch] Keep reserved bits in CPSR on write sergiodj+buildbot
2016-09-21 16:56 ` Failures on Fedora-x86_64-native-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
2016-09-17  5:25 [binutils-gdb/gdb-7.12-branch] Backport lastest POWER9 support to match final ISA 3.0 documentation sergiodj+buildbot
2016-09-17  5:50 ` Failures on Fedora-x86_64-native-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
2016-09-07  2:09 [binutils-gdb/gdb-7.12-branch] Introduce make_cleanup_restore_current_ui sergiodj+buildbot
2016-09-07  2:47 ` Failures on Fedora-x86_64-native-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
2016-09-01  8:54 [binutils-gdb/gdb-7.12-branch] Fix lwp_suspend/unsuspend imbalance in linux_wait_1 sergiodj+buildbot
2016-09-01  9:43 ` Failures on Fedora-x86_64-native-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
2016-08-31 10:26 [binutils-gdb/gdb-7.12-branch] Fix order of inferiors in "thread apply all" sergiodj+buildbot
2016-08-31 11:43 ` Failures on Fedora-x86_64-native-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
2016-08-24 22:31 [binutils-gdb/gdb-7.12-branch] Allow resetting an empty inferior-tty sergiodj+buildbot
2016-08-25  1:56 ` Failures on Fedora-x86_64-native-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
2016-08-24  8:29 [binutils-gdb/gdb-7.12-branch] x32: Fix gdb.trace/mi-trace-frame-collected.exp sergiodj+buildbot
2016-08-24 11:26 ` Failures on Fedora-x86_64-native-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
2016-08-24  2:15 [binutils-gdb/gdb-7.12-branch] x32: Avoid unsigned long when installing fast tracepoint jump pads sergiodj+buildbot
2016-08-24  2:46 ` Failures on Fedora-x86_64-native-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
2016-08-24  1:34 [binutils-gdb/gdb-7.12-branch] x32 Fast tracepoints: Customize jump pad address sergiodj+buildbot
2016-08-24  2:03 ` Failures on Fedora-x86_64-native-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
2016-08-23 19:14 [binutils-gdb/gdb-7.12-branch] Fix PR20494 - User input stops being echoed in CLI sergiodj+buildbot
2016-08-23 21:40 ` Failures on Fedora-x86_64-native-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
2016-08-23 17:02 [binutils-gdb/gdb-7.12-branch] Fix signals-state-child.exp in remote testing sergiodj+buildbot
2016-08-23 17:27 ` Failures on Fedora-x86_64-native-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
2016-08-19 21:36 [binutils-gdb/gdb-7.12-branch] [AArch64] Match instruction "STP with base register" in prologue sergiodj+buildbot
2016-08-20  0:14 ` Failures on Fedora-x86_64-native-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
2016-08-15 21:31 [binutils-gdb/gdb-7.12-branch] [GDB] Fix builds broken by proc-service changes sergiodj+buildbot
2016-08-15 23:40 ` Failures on Fedora-x86_64-native-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
2016-08-12 15:06 [binutils-gdb/gdb-7.12-branch] Fix warning in gdb.base/signals-state-child.c sergiodj+buildbot
2016-08-12 16:07 ` Failures on Fedora-x86_64-native-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
2016-08-12  6:37 [binutils-gdb/gdb-7.12-branch] Fix fallout from gdb/20413's fix (x32: linux_ptrace_test_ret_to_nx: Cannot PTRACE_PEEKUSER) sergiodj+buildbot
2016-08-12 10:19 ` Failures on Fedora-x86_64-native-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
2016-08-11  3:36 [binutils-gdb/gdb-7.12-branch] Plumb enum remove_bp_reason all the way to target_remove_breakpoint sergiodj+buildbot
2016-08-11  4:05 ` Failures on Fedora-x86_64-native-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
2016-08-10  2:14 [binutils-gdb/gdb-7.12-branch] Fix PR mi/20431 - Missing MI prompts after sync execution MI command (-exec-continue, etc.) errors sergiodj+buildbot
2016-08-10  3:46 ` Failures on Fedora-x86_64-native-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
2016-08-09 22:55 [binutils-gdb/gdb-7.12-branch] Fix PR gdb/18653: gdb disturbs inferior's inherited signal dispositions sergiodj+buildbot
2016-08-09 23:32 ` Failures on Fedora-x86_64-native-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
2016-08-05 19:41 [binutils-gdb/gdb-7.12-branch] Fix PR remote/20398: File-IO write always outputs "Quit" sergiodj+buildbot
2016-08-05 20:11 ` Failures on Fedora-x86_64-native-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
2016-08-05 18:42 [binutils-gdb/gdb-7.12-branch] gdb/NEWS: Mention that C++ is now the default sergiodj+buildbot
2016-08-05 19:24 ` Failures on Fedora-x86_64-native-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
2016-08-05 17:24 [binutils-gdb/gdb-7.12-branch] gdb/configure --help: suggest --disable-build-with-cxx instead of --enable sergiodj+buildbot
2016-08-05 17:48 ` Failures on Fedora-x86_64-native-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
2016-08-04 12:07 [binutils-gdb/gdb-7.12-branch] Determine target description for native aarch64 sergiodj+buildbot
2016-08-04 13:34 ` Failures on Fedora-x86_64-native-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
2016-08-03 16:56 [binutils-gdb/gdb-7.12-branch] Update NEWS to mention Python breakpoint events sergiodj+buildbot
2016-08-03 17:21 ` Failures on Fedora-x86_64-native-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
2016-08-01 19:25 [binutils-gdb/gdb-7.12-branch] Bump GDB version number to 7.11.90.DATE-git sergiodj+buildbot
2016-08-01 20:23 ` Failures on Fedora-x86_64-native-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
2016-08-01 19:05 [binutils-gdb/gdb-7.12-branch] Set GDB version number to 7.11.90 sergiodj+buildbot
2016-08-01 19:24 ` Failures on Fedora-x86_64-native-gdbserver-m64, branch gdb-7.12-branch 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).