public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
* [binutils-gdb/gdb-7.12-branch] ppc: Fix record of HTM instructions
@ 2016-08-18 23:09 sergiodj+buildbot
  2016-08-18 23:05 ` Failures on Fedora-x86_64-native-gdbserver-m32, branch gdb-7.12-branch sergiodj+buildbot
                   ` (13 more replies)
  0 siblings, 14 replies; 62+ messages in thread
From: sergiodj+buildbot @ 2016-08-18 23:09 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1c9c56667193b56ad5fa30ac0ae731f1d63cd6c5 ***

Author: Edjunior Barbosa Machado <emachado@linux.vnet.ibm.com>
Branch: gdb-7.12-branch
Commit: 1c9c56667193b56ad5fa30ac0ae731f1d63cd6c5

ppc: Fix record of HTM instructions

The patch fixes the record support of Hardware Transactional Memory
instructions on Power. It also solves a large number of unexpected failures
from gdb.reverse testcases sigall-precsave.exp and sigall-reverse.exp that
occur on distros which glibc uses HTM instructions.

gdb/ChangeLog
2016-08-18  Edjunior Barbosa Machado  <emachado@linux.vnet.ibm.com>

	* rs6000-tdep.c (ppc_process_record_op31): Handle HTM instructions.


^ permalink raw reply	[flat|nested] 62+ 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 16:17 ` Failures on Debian-s390x-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 62+ 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] 62+ messages in thread
* [binutils-gdb/gdb-7.12-branch] Set GDB version number to 7.12.1.
@ 2017-01-21 14:06 sergiodj+buildbot
  2017-01-21 15:03 ` Failures on Debian-s390x-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 62+ messages in thread
From: sergiodj+buildbot @ 2017-01-21 14:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 59b102452f0bdab7a9b19d9fdbb8ce5253f0ce9f ***

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

Set GDB version number to 7.12.1.

gdb/ChangeLog:

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


^ permalink raw reply	[flat|nested] 62+ messages in thread
* [binutils-gdb/gdb-7.12-branch] Fix python-interactive with Python 3.6
@ 2017-01-21  2:29 sergiodj+buildbot
  2017-01-21  4:18 ` Failures on Debian-s390x-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 62+ messages in thread
From: sergiodj+buildbot @ 2017-01-21  2:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3fc6097b073698a50d0ab70c6c8205a83cd9383c ***

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

Fix python-interactive with Python 3.6

New in v2:

 - Define PyMem_RawMalloc as PyMem_Malloc for Python < 3.4 and use
   PyMem_RawMalloc in the code.

Since Python 3.4, the callback installed in PyOS_ReadlineFunctionPointer
should return a value allocated with PyMem_RawMalloc instead of
PyMem_Malloc.  The reason is that PyMem_Malloc must be called with the
Python Global Interpreter Lock (GIL) held, which is not the case in the
context where this function is called.  PyMem_RawMalloc was introduced
for cases like this.

In Python 3.6, it looks like they added an assert to verify that
PyMem_Malloc was not called without the GIL.  The consequence is that
typing anything in the python-interactive mode of gdb crashes the
process.  The same behavior was observed with the official package on
Arch Linux as well as with a manual Python build on Ubuntu 14.04.

This is what is shown with a debug build of Python 3.6 (the error with a
non-debug build is far less clear):

  (gdb) pi
  >>> print(1)
  Fatal Python error: Python memory allocator called without holding the GIL

  Current thread 0x00007f1459af8780 (most recent call first):
  [1]    21326 abort      ./gdb

and the backtrace:

  #0  0x00007ffff618bc37 in raise () from /lib/x86_64-linux-gnu/libc.so.6
  #1  0x00007ffff618f028 in abort () from /lib/x86_64-linux-gnu/libc.so.6
  #2  0x00007ffff6b104d6 in Py_FatalError (msg=msg@entry=0x7ffff6ba15b8 "Python memory allocator called without holding the GIL") at Python/pylifecycle.c:1457
  #3  0x00007ffff6a37a68 in _PyMem_DebugCheckGIL () at Objects/obmalloc.c:1972
  #4  0x00007ffff6a3804e in _PyMem_DebugFree (ctx=0x7ffff6e65290 <_PyMem_Debug+48>, ptr=0x24f8830) at Objects/obmalloc.c:1994
  #5  0x00007ffff6a38e1d in PyMem_Free (ptr=<optimized out>) at Objects/obmalloc.c:442
  #6  0x00007ffff6b866c6 in _PyFaulthandler_Fini () at ./Modules/faulthandler.c:1369
  #7  0x00007ffff6b104bd in Py_FatalError (msg=msg@entry=0x7ffff6ba15b8 "Python memory allocator called without holding the GIL") at Python/pylifecycle.c:1431
  #8  0x00007ffff6a37a68 in _PyMem_DebugCheckGIL () at Objects/obmalloc.c:1972
  #9  0x00007ffff6a37aa3 in _PyMem_DebugMalloc (ctx=0x7ffff6e65290 <_PyMem_Debug+48>, nbytes=5) at Objects/obmalloc.c:1980
  #10 0x00007ffff6a38d91 in PyMem_Malloc (size=<optimized out>) at Objects/obmalloc.c:418
  #11 0x000000000064dbe2 in gdbpy_readline_wrapper (sys_stdin=0x7ffff6514640 <_IO_2_1_stdin_>, sys_stdout=0x7ffff6514400 <_IO_2_1_stdout_>, prompt=0x7ffff4d4f7d0 ">>> ")
    at /home/emaisin/src/binutils-gdb/gdb/python/py-gdb-readline.c:75

The documentation is very clear about it [1] and it was also mentioned
in the "What's New In Python 3.4" page [2].

[1] https://docs.python.org/3/c-api/veryhigh.html#c.PyOS_ReadlineFunctionPointer
[2] https://docs.python.org/3/whatsnew/3.4.html#changes-in-the-c-api

gdb/ChangeLog:

	* python/python-internal.h (PyMem_RawMalloc): Define for
	Python < 3.4.
	* python/py-gdb-readline.c (gdbpy_readline_wrapper): Use
	PyMem_RawMalloc instead of PyMem_Malloc.


^ permalink raw reply	[flat|nested] 62+ 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:54 ` Failures on Debian-s390x-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 62+ 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] 62+ messages in thread
* [binutils-gdb/gdb-7.12-branch] gdb: Fix C and C++03 builds
@ 2016-12-20 20:16 sergiodj+buildbot
  2016-12-25  6:40 ` Failures on Debian-s390x-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 62+ messages in thread
From: sergiodj+buildbot @ 2016-12-20 20:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9bfe0298332782a9c082fb475bdf8eeeef8cf45e ***

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

gdb: Fix C and C++03 builds

The readline/sjlj-exceptions fix added an unconditional use of
noexcept, but that's only valid C++11, and 7.12 must build with C and
C++03 too.  Fix this by adding a GDB_EXCEPT macro that compiles away
to nothing in C, and to throw() in C++03, which I've confirmed fixes
the original issue just the same as noexcept, with GCC 7 + -std=gnu+03
+ sjlj-exceptions.

gdb/ChangeLog:
2016-12-20  Pedro Alves  <palves@redhat.com>

	PR gdb/20977
	* event-top.c (GDB_NOEXCEPT): Define.
	(gdb_rl_callback_read_char_wrapper_noexcept): Use GDB_NOEXCEPT
	instead of noexcept and use (void) instead of ().
	(gdb_rl_callback_handler): Use GDB_NOEXCEPT instead of noexcept.


^ permalink raw reply	[flat|nested] 62+ messages in thread
* [binutils-gdb/gdb-7.12-branch] Create tdep->rx_psw_type and tdep->rx_fpsw_type lazily
@ 2016-12-09 18:16 sergiodj+buildbot
  2016-12-09 19:25 ` Failures on Debian-s390x-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 62+ messages in thread
From: sergiodj+buildbot @ 2016-12-09 18:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fa897675de62473e5c04330c5d5b782cd1ae04e9 ***

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

Create tdep->rx_psw_type and tdep->rx_fpsw_type lazily

I build GDB with all targets enabled, and "set architecture rx",
GDB crashes,

(gdb) set architecture rx

Program received signal SIGSEGV, Segmentation fault.
append_flags_type_flag (type=0x20cc360, bitpos=bitpos@entry=0, name=name@entry=0xd27529 "C") at ../../binutils-gdb/gdb/gdbtypes.c:4926
4926                               name);
(gdb) bt 10
 #0  append_flags_type_flag (type=0x20cc360, bitpos=bitpos@entry=0, name=name@entry=0xd27529 "C") at ../../binutils-gdb/gdb/gdbtypes.c:4926
 #1  0x00000000004ce725 in rx_gdbarch_init (info=..., arches=<optimized out>) at ../../binutils-gdb/gdb/rx-tdep.c:1051
 #2  0x00000000006b05a4 in gdbarch_find_by_info (info=...) at ../../binutils-gdb/gdb/gdbarch.c:5269
 #3  0x000000000060eee4 in gdbarch_update_p (info=...) at ../../binutils-gdb/gdb/arch-utils.c:557
 #4  0x000000000060f8a8 in set_architecture (ignore_args=<optimized out>, from_tty=1, c=<optimized out>) at ../../binutils-gdb/gdb/arch-utils.c:531
 #5  0x0000000000593d0b in do_set_command (arg=<optimized out>, arg@entry=0x20bee81 "rx ", from_tty=from_tty@entry=1, c=c@entry=0x20b1540)
    at ../../binutils-gdb/gdb/cli/cli-setshow.c:455
 #6  0x00000000007665c3 in execute_command (p=<optimized out>, p@entry=0x20bee70 "set architecture rx ", from_tty=1) at ../../binutils-gdb/gdb/top.c:666
 #7  0x00000000006935f4 in command_handler (command=0x20bee70 "set architecture rx ") at ../../binutils-gdb/gdb/event-top.c:577
 #8  0x00000000006938d8 in command_line_handler (rl=<optimized out>) at ../../binutils-gdb/gdb/event-top.c:767
 #9  0x0000000000692c2c in gdb_rl_callback_handler (rl=0x20be7f0 "") at ../../binutils-gdb/gdb/event-top.c:200

The cause is that we want to access some builtin types in gdbarch init, but
it is not initialized yet.  I fix it by creating the type when it is to be
used.  We've already done this in sparc, sparc64 and m68k.

gdb:

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

	PR tdep/20954
	* rx-tdep.c (rx_psw_type): New function.
	(rx_fpsw_type): New function.
	(rx_register_type): Call rx_psw_type and rx_fpsw_type.
	(rx_gdbarch_init): Move code to rx_psw_type and
	rx_fpsw_type.


^ permalink raw reply	[flat|nested] 62+ messages in thread
* [binutils-gdb/gdb-7.12-branch] Create tdep->rl78_psw_type lazily
@ 2016-12-09 17:42 sergiodj+buildbot
  2016-12-09 18:19 ` Failures on Debian-s390x-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 62+ messages in thread
From: sergiodj+buildbot @ 2016-12-09 17:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 68647b569da041a33a6504cd80f51fbd43bfa134 ***

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

Create tdep->rl78_psw_type lazily

I build GDB for all targets enabled.  When I "set architecture rl78",
GDB crashes,

(gdb) set architecture rl78

Program received signal SIGSEGV, Segmentation fault.
append_flags_type_flag (type=0x20cc0e0, bitpos=bitpos@entry=0, name=name@entry=0x11dba3f "CY") at ../../binutils-gdb/gdb/gdbtypes.c:4926
4926                               name);
(gdb) bt 10
 #0  append_flags_type_flag (type=0x20cc0e0, bitpos=bitpos@entry=0, name=name@entry=0x11dba3f "CY") at ../../binutils-gdb/gdb/gdbtypes.c:4926
 #1  0x00000000004aaca8 in rl78_gdbarch_init (info=..., arches=<optimized out>) at ../../binutils-gdb/gdb/rl78-tdep.c:1410
 #2  0x00000000006b05a4 in gdbarch_find_by_info (info=...) at ../../binutils-gdb/gdb/gdbarch.c:5269
 #3  0x000000000060eee4 in gdbarch_update_p (info=...) at ../../binutils-gdb/gdb/arch-utils.c:557
 #4  0x000000000060f8a8 in set_architecture (ignore_args=<optimized out>, from_tty=1, c=<optimized out>) at ../../binutils-gdb/gdb/arch-utils.c:531
 #5  0x0000000000593d0b in do_set_command (arg=<optimized out>, arg@entry=0x20be851 "rl78", from_tty=from_tty@entry=1, c=c@entry=0x20b1540)
    at ../../binutils-gdb/gdb/cli/cli-setshow.c:455
 #6  0x00000000007665c3 in execute_command (p=<optimized out>, p@entry=0x20be840 "set architecture rl78", from_tty=1) at ../../binutils-gdb/gdb/top.c:666
 #7  0x00000000006935f4 in command_handler (command=0x20be840 "set architecture rl78") at ../../binutils-gdb/gdb/event-top.c:577
 #8  0x00000000006938d8 in command_line_handler (rl=<optimized out>) at ../../binutils-gdb/gdb/event-top.c:767
 #9  0x0000000000692c2c in gdb_rl_callback_handler (rl=0x20be890 "") at ../../binutils-gdb/gdb/event-top.c:200

The cause is that we want to access some builtin types in gdbarch init, but
it is not initialized yet.  I fix it by creating the type when it is to be
used.  We've already done this in sparc, sparc64 and m68k.

gdb:

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

	PR tdep/20953
	* rl78-tdep.c (rl78_psw_type): New function.
	(rl78_register_type): Call rl78_psw_type.
	(rl78_gdbarch_init): Move code to rl78_psw_type.


^ permalink raw reply	[flat|nested] 62+ messages in thread
* [binutils-gdb/gdb-7.12-branch] PR gdb/20653 - small cleanup in string_to_explicit_location
@ 2016-10-25  4:37 sergiodj+buildbot
  2016-10-25  5:02 ` Failures on Debian-s390x-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 62+ messages in thread
From: sergiodj+buildbot @ 2016-10-25  4:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 909de2c5cc91b815d671f7018da2a925fbd19aaf ***

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

PR gdb/20653 - small cleanup in string_to_explicit_location

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

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

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


^ permalink raw reply	[flat|nested] 62+ messages in thread
* [binutils-gdb/gdb-7.12-branch] [GDBserver] Fix conversion warning
@ 2016-10-25  3:26 sergiodj+buildbot
  2016-10-25  4:22 ` Failures on Debian-s390x-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 62+ 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] 62+ 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 13:19 ` Failures on Debian-s390x-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 62+ 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] 62+ 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 19:01 ` Failures on Debian-s390x-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 62+ 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] 62+ messages in thread
* [binutils-gdb/gdb-7.12-branch] frame.h: Forward-declare struct ui_out
@ 2016-10-06 21:39 sergiodj+buildbot
  2016-10-07  3:30 ` Failures on Debian-s390x-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 62+ messages in thread
From: sergiodj+buildbot @ 2016-10-06 21:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f2ddf8f6caffc513751ebfb3608c3a453aed5103 ***

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

frame.h: Forward-declare struct ui_out

Fixes this failure when building in C mode.  I think it's relevant for master
as well, since it's a good practice to include (or forward-declare) what you
use.

In file included from ../../binutils-gdb/gdb/gdbarch.h:38:0,
                 from ../../binutils-gdb/gdb/defs.h:653,
                 from ../../binutils-gdb/gdb/dictionary.c:23:
../../binutils-gdb/gdb/frame.h:710:48: warning: struct ui_out declared inside parameter list will not be visible outside of this definition or declaration
 extern void print_stack_frame_to_uiout (struct ui_out *uiout,

gdb/ChangeLog:

	* frame.h: Forward-declare struct ui_out.


^ permalink raw reply	[flat|nested] 62+ 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-07  1:00 ` Failures on Debian-s390x-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 62+ 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] 62+ 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 23:23 ` Failures on Debian-s390x-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 62+ 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] 62+ messages in thread
* [binutils-gdb/gdb-7.12-branch] Fix PR11094: JIT breakpoint is not properly recreated on reruns
@ 2016-10-06 13:29 sergiodj+buildbot
  2016-10-06 16:28 ` Failures on Debian-s390x-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 62+ messages in thread
From: sergiodj+buildbot @ 2016-10-06 13:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f8da6fe399c8dafa98e7dbed36d3562a919768f5 ***

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

Fix PR11094: JIT breakpoint is not properly recreated on reruns

Even though this was supposedly in the gdb 7.2 timeframe, the testcase
in PR11094 crashes current GDB with a segfault:

  Program received signal SIGSEGV, Segmentation fault.
  0x00000000005ee894 in event_location_to_string (location=0x0) at
  src/gdb/location.c:412
  412       if (EL_STRING (location) == NULL)
  (top-gdb) bt
  #0  0x00000000005ee894 in event_location_to_string (location=0x0) at
  src/gdb/location.c:412
  #1  0x000000000057411a in print_breakpoint_location (b=0x18288e0, loc=0x0) at
  src/gdb/breakpoint.c:6201
  #2  0x000000000057483f in print_one_breakpoint_location (b=0x18288e0,
  loc=0x182cf10, loc_number=0, last_loc=0x7fffffffd258, allflag=1)
      at src/gdb/breakpoint.c:6473
  #3  0x00000000005751e1 in print_one_breakpoint (b=0x18288e0,
  last_loc=0x7fffffffd258, allflag=1) at
  src/gdb/breakpoint.c:6707
  #4  0x000000000057589c in breakpoint_1 (args=0x0, allflag=1, filter=0x0) at
  src/gdb/breakpoint.c:6947
  #5  0x0000000000575aa8 in maintenance_info_breakpoints (args=0x0, from_tty=0)
  at src/gdb/breakpoint.c:7026
  [...]

This is GDB trying to print the location spec of the JIT event
breakpoint, but that's an internal breakpoint without one.

If I add a NULL check, then we see that the JIT breakpoint is now
pending (because its location has shlib_disabled set):

  (gdb) maint info breakpoints
  Num     Type           Disp Enb Address            What
  [...]
  -8      jit events     keep y   <PENDING>           inf 1
  [...]

But that's incorrect.  GDB should have managed to recreate the JIT
breakpoint's location for the second run.  So the problem is
elsewhere.

The problem is that if the JIT loads at the same address on the second
run, we never recreate the JIT breakpoint, because we hit this early
return:

  static int
  jit_breakpoint_re_set_internal (struct gdbarch *gdbarch,
				  struct jit_program_space_data *ps_data)
  {
    [...]
    if (ps_data->cached_code_address == addr)
      return 0;

    [...]
      delete_breakpoint (ps_data->jit_breakpoint);
    [...]
    ps_data->jit_breakpoint = create_jit_event_breakpoint (gdbarch, addr);

Fix this by deleting the breakpoint and discarding the cached code
address when the objfile where the previous JIT breakpoint was found
is deleted/unloaded in the first place.

The test that was originally added for PR11094 doesn't trip on this
because:

  #1 - It doesn't test the case of the JIT descriptor's address _not_
       changing between reruns.

  #2 - And then it doesn't do "maint info breakpoints", or really
       anything with the JIT at all.

  #3 - and even then, to trigger the problem the JIT descriptor needs
       to be in a separate library, while the current test puts it in
       the main program.

The patch extends the test to cover all combinations of these
scenarios.

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

	* jit.c (free_objfile_data): Delete the JIT breakpoint and clear
	the cached code address.

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

	* gdb.base/jit-simple-dl.c: New file.
	* gdb.base/jit-simple-jit.c: New file, factored out from ...
	* gdb.base/jit-simple.c: ... this.
	* gdb.base/jit-simple.exp (jit_run): Delete.
	(build_jit): New proc.
	(jit_test_reread): Recompile either the main program or the shared
	library, depending on what is being tested.  Skip changing address
	if caller wants to.  Compare before/after addresses.  If testing
	standalone, explicitly load the binary.  Test "maint info
	breakpoints".
	(top level): Add "standalone vs shared lib" and "change address"
	vs "same address" axes.


^ permalink raw reply	[flat|nested] 62+ messages in thread
* [binutils-gdb/gdb-7.12-branch] Fix a few gdb.base/jit-simple.exp problems
@ 2016-10-06 13:25 sergiodj+buildbot
  2016-10-06 15:36 ` Failures on Debian-s390x-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 62+ messages in thread
From: sergiodj+buildbot @ 2016-10-06 13:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e027976f02ce8ed4cf0da79238226c03a640f2b3 ***

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

Fix a few gdb.base/jit-simple.exp problems

I noticed that we sometimes get this:

  (gdb) print &__jit_debug_descriptor
  $1 = (struct jit_descriptor *) 0x601040 <__jit_debug_descriptor>
  (gdb) PASS: gdb.base/jit-simple.exp: blah 1
  [...]
  (gdb) run
  [...]
  Starting program: build/gdb/testsuite/outputs/gdb.base/jit-simple/jit-simple
  Unsupported JIT protocol version 4 in descriptor (expected 1)

  Breakpoint 2, main () at src/gdb/testsuite/gdb.base/jit-simple.c:36
  36        return 0;
  (gdb) print &__jit_debug_descriptor
  $2 = (struct jit_descriptor *) 0x601040 <__jit_debug_descriptor>
  (gdb) PASS: gdb.base/jit-simple.exp: blah 1

All tests PASSed, but note the "Unsupported JIT protocol version 4"
message.

Also notice that "__jit_debug_descriptor" has the same address before
and after the rerun, while the test is built in a way that should make
that address change between runs.

The test doesn't catch any of this because it doesn't compare
before/after addresses.

And then notice the "blah 1" test messages.  "blah" is clearly a WIP
message, but it should be at least "blah 2" the second time.  :-)

The reason this sometimes happens is that the test recompiles the
program and expects gdb to reload it automaticallyt on "run".  However,
if the original program and the new recompilation happen to be in the
same second, then gdb does not realize that the binary needs to be
reloaded.  (This is an old problem out of scope of this series.)  If
that happens, then GDB ends up using the wrong symbols for the program
that it spawns, reads the JIT descriptor out of the wrong address,
finds garbage, and prints that "unsupported version" notice.

Fix that in the same way gdb.base/reread.exp handles it -- by sleeping
one second before recompiling.

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

	* gdb.base/jit-simple.exp (top level) Delete get_compiler_info
	call.
	(jit_run): Delete.
	(jit_test_reread): Use with_test_prefix.  Reload the main binary
	explicitly.  Compare the before/after addresses of the JIT
	descriptor.


^ permalink raw reply	[flat|nested] 62+ messages in thread
* [binutils-gdb/gdb-7.12-branch] Introduce cleanup to restore current_uiout
@ 2016-10-03 23:07 sergiodj+buildbot
  2016-10-04  0:44 ` Failures on Debian-s390x-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 62+ 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] 62+ messages in thread
* [binutils-gdb/gdb-7.12-branch] PR gdb/20609 - attach of JIT-debug-enabled inf 7.11.1 regression
@ 2016-09-29 22:19 sergiodj+buildbot
  2016-09-30 10:08 ` Failures on Debian-s390x-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 62+ messages in thread
From: sergiodj+buildbot @ 2016-09-29 22:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b31567caa5d7ed8e9ad69f59a562c0494c0b3cbe ***

Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Branch: gdb-7.12-branch
Commit: b31567caa5d7ed8e9ad69f59a562c0494c0b3cbe

PR gdb/20609 - attach of JIT-debug-enabled inf 7.11.1 regression

Regression: gdb --pid $(pidof qemu-system-x86_64) stopped working with gdb 7.11.1
https://sourceware.org/bugzilla/show_bug.cgi?id=20609

It was reported for qemu-system-x86_64 but it happens for any multithreaded
inferior with a JIT debugging hook.

136613ef0c6850427317e57be1b644080ff6decb is the first bad commit
Author: Pedro Alves <palves@redhat.com>
    Fix PR gdb/19828: gdb -p <process from a container>: internal error
Message-ID: <cbdf2e04-4fa8-872a-2a23-08c9c1b26e00@redhat.com>
https://sourceware.org/ml/gdb-patches/2016-05/msg00450.html

jit_breakpoint_re_set() is specific by trying to insert a breakpoint into the
main executable, not into a shared library.  During attachment GDB thinks it
needs to use 'breakpoint always-inserted' from
breakpoints_should_be_inserted_now() as a newly attached thread is
'thread_info->executing' due to 'lwp_info->must_set_ptrace_flags' enabled and
the task not yet stopped.  This did not happen before the 'bad commit' above
which adds tracking of such thread.

GDB then fails to insert the breakpoints to invalid address as PIE executable
gets properly relocated during later phase of attachment.  One can see in the
backtraces below:
 -> jit_breakpoint_re_set_internal()
later:
 -> svr4_exec_displacement()

One can suppress the initial breakpoint_re_set() call as there will be another
breakpoint_re_set() done from the final post_create_inferior() call in
setup_inferior().

BTW additionally 'threads_executing' cache bool is somehow stale (somewhere is
missing update_threads_executing()).  I was trying to deal with that in my
first/second attempt below but in my final third attempt (attached) I have
left it as it is.

First attempt trying not to falsely require 'breakpoint always-inserted':
  https://people.redhat.com/jkratoch/rhbz1375553-fix1.patch
Reduced first attempt:
  https://people.redhat.com/jkratoch/rhbz1375553-fix2.patch

The third attempt suppresses breakpoint insertion until PIE executable gets
relocated by svr4_exec_displacement().  Applied.

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

	PR gdb/20609 - attach of JIT-debug-enabled inf 7.11.1 regression
	* exec.c (exec_file_locate_attach): Add parameter defer_bp_reset.
	Use it.
	* gdbcore.h (exec_file_locate_attach): Add parameter defer_bp_reset.
	* infcmd.c (setup_inferior): Update caller.
	* remote.c (remote_add_inferior): Likewise.

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

	PR gdb/20609 - attach of JIT-debug-enabled inf 7.11.1 regression
	* gdb.base/jit-attach-pie.c: New file.
	* gdb.base/jit-attach-pie.exp: New file.


^ permalink raw reply	[flat|nested] 62+ 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 18:38 ` Failures on Debian-s390x-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 62+ 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] 62+ messages in thread
* [binutils-gdb/gdb-7.12-branch] ppc: Fix record support of Store String Word instructions
@ 2016-09-21 13:28 sergiodj+buildbot
  2016-09-21 14:25 ` Failures on Debian-s390x-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 62+ messages in thread
From: sergiodj+buildbot @ 2016-09-21 13:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4e2b3c62a39b99edcd20c25774c1eee01ea6fad5 ***

Author: Edjunior Barbosa Machado <emachado@linux.vnet.ibm.com>
Branch: gdb-7.12-branch
Commit: 4e2b3c62a39b99edcd20c25774c1eee01ea6fad5

ppc: Fix record support of Store String Word instructions

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

	* rs6000-tdep.c (ppc_process_record_op31): Fix record of Store String
	Word instructions.


^ permalink raw reply	[flat|nested] 62+ 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 11:37 ` Failures on Debian-s390x-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 62+ 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] 62+ messages in thread
* [binutils-gdb/gdb-7.12-branch] new-ui command: gdb internal errors if input is already pending
@ 2016-09-07  3:24 sergiodj+buildbot
  2016-09-07 16:34 ` Failures on Debian-s390x-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 62+ messages in thread
From: sergiodj+buildbot @ 2016-09-07  3:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f9a7ee181f7500b2f87687bf0c72b4b963e06acb ***

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

new-ui command: gdb internal errors if input is already pending

I noticed that if input is already pending on the new-ui TTY, gdb
internal-errors.

E.g., create /dev/pts/2, and type anything there (even just <return>
is sufficient).

Now start GDB creating a new UI on that TTY, while at the same time,
running a synchronous execution command.  Something like:

$ gdb program -ex "new-ui console /dev/pts/2" -ex "start"

Back on /dev/pts/2, we get:

  (gdb) .../src/gdb/event-top.c:360: internal-error: double prompt
  A problem internal to GDB has been detected,
  further debugging may prove unreliable.

While the main UI was waiting for "start" to finish, gdb kepts pumping
events, including the input fd of the extra console.  The problem is
that stdin_event_handler doesn't restore the current UI back to what
it was, assuming that it's only ever called from the top level event
loop.  However, in this case, it's being called from the nested event
loop from within maybe_wait_sync_command_done.

When finally the "start" command is done, we reach the code that
prints the prompt in the main UI, just before starting the main event
loop.  Since now the current UI is pointing at the extra console (by
mistake), we find ourselves printing a double prompt on the extra
console.  This is caught by the assertion that fails, as shown above.

Since other event handlers also don't restore the UI (e.g., signal
event handlers), I think it's better if whatever is pumping events to
take care to restore the UI, if it cares.  That's what this patch
does.  New test included.

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

	* top.c (wait_sync_command_done): Don't assume current_ui doesn't
	change across events.  Restore the current UI before returning.
	(gdb_readline_wrapper): Restore the current UI before returning.

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

	* gdb.base/new-ui-pending-input.c: New file.
	* gdb.base/new-ui-pending-input.exp: New file.
	* gdb.exp (clear_gdb_spawn_id): New procedure.
	(with_spawn_id): Check whether gdb_spawn_id exists before
	referencing it.  If gdb_spawn_id didn't exist on entry, clear it
	on exit.


^ permalink raw reply	[flat|nested] 62+ 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 19:20 ` Failures on Debian-s390x-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 62+ 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] 62+ 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 14:16 ` Failures on Debian-s390x-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 62+ 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] 62+ 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:15 ` Failures on Debian-s390x-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 62+ 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] 62+ messages in thread
* [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  7:00 ` Failures on Debian-s390x-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 62+ 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] 62+ 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:29 ` Failures on Debian-s390x-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 62+ 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] 62+ messages in thread
* [binutils-gdb/gdb-7.12-branch] x32 Fast tracepoints: IPA target descriptions
@ 2016-08-24  0:49 sergiodj+buildbot
  2016-08-24  1:17 ` Failures on Debian-s390x-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 62+ messages in thread
From: sergiodj+buildbot @ 2016-08-24  0:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7157552b0f8b4bb74910d85808244029c89229ff ***

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

x32 Fast tracepoints: IPA target descriptions

Building GDB for x32 fails building the IPA, with:

   .../src/gdb/gdbserver/linux-amd64-ipa.c: In function const target_desc* get_ipa_tdesc(int):
   .../src/gdb/gdbserver/linux-amd64-ipa.c:182:14: error: tdesc_amd64_avx_linux was not declared in this scope
	  return tdesc_amd64_avx_linux;
		 ^
   .../src/gdb/gdbserver/linux-amd64-ipa.c:184:14: error: tdesc_amd64_mpx_linux was not declared in this scope
	  return tdesc_amd64_mpx_linux;
		 ^
   .../src/gdb/gdbserver/linux-amd64-ipa.c:186:14: error: tdesc_amd64_avx_mpx_linux was not declared in this scope
	  return tdesc_amd64_avx_mpx_linux;
		 ^
  [...]

The problem is that the IPA is trying to use the 64-bit descriptions,
when it should be using the x32 ones.

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

	PR gdb/20415
	* Makefile.in (x32-linux-ipa.o, x32-avx-linux-ipa.o)
	(x32-avx512-linux-ipa.o): New rules.
	* configure.ac (x86_64-*-linux*): New x32 check.
	* configure.srv (ipa_x32_linux_regobj): New.
	(x86_64-*-linux*): Use $ipa_x32_linux_regobj if building for x32.
	* linux-amd64-ipa.c (get_ipa_tdesc) [__ILP32__]: Return x32
	descriptions.
	(initialize_low_tracepoint) [__ILP32__]: Initialize x32
	descriptions.
	* configure: Regenerate.


^ permalink raw reply	[flat|nested] 62+ 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 23:33 ` Failures on Debian-s390x-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 62+ 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] 62+ 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 18:42 ` Failures on Debian-s390x-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 62+ 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] 62+ messages in thread
* [binutils-gdb/gdb-7.12-branch] Fix PR gdb/20505 - Make vDSO detection work with core files
@ 2016-08-23  8:36 sergiodj+buildbot
  2016-08-23 10:20 ` Failures on Debian-s390x-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 62+ messages in thread
From: sergiodj+buildbot @ 2016-08-23  8:36 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 601a2a8f639f9ef6dab86118a87fa67861f2091e ***

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

Fix PR gdb/20505 - Make vDSO detection work with core files

Loading a core dump that was either generated on a system running
pristine glibc master, or on a Fedora/RHEL system with LD_DEBUG=unused
set in the environment, solib-svr4.c:svr4_current_sos fails to filter
out the vDSO, resulting in:

  (gdb) core-file corefile.core^M
  [New LWP 2362]^M
  warning: Could not load shared library symbols for linux-vdso.so.1.^M
  Do you need "set solib-search-path" or "set sysroot"?^M
  Core was generated by `build-gdb/gdb/testsuite/outputs/gdb.base/corefile/'.^M
  ...

The problem is that gdbarch_vsyscall_range does not support core
inferiors at all.

When live debugging, we're finding the vDSO's start address with
auxv/AT_SYSINFO_EHDR, and then we find the vDSO's size by look for the
corresponding mapping, by parsing /proc/PID/maps.  When debugging a
core dump, we can also determine the starting address from
auxv/AT_SYSINFO_EHDR.  However, we obviously can't read the core
mappings out of the host's /proc.  But we can instead look for a
corresponding load segment in the core's bfd.

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

	PR gdb/20505
	* linux-tdep.c (linux_vsyscall_range_raw): For core inferiors,
	find the vDSO's start address with AT_SYSINFO_EHDR too, and
	determine the vDSO's size by finding the PT_LOAD segment that
	matches AT_SYSINFO_EHDR.

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

	PR gdb/20505
	* gdb.base/vdso-warning.exp: Test core dumps too.  Use
	with_test_prefix.  Factor out bits to ...
	(test_no_vdso): ... this new procedure.


^ permalink raw reply	[flat|nested] 62+ 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  6:37 ` Failures on Debian-s390x-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 62+ 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] 62+ messages in thread
* [binutils-gdb/gdb-7.12-branch] Make "end" field in feature specs required again.
@ 2016-08-17 15:30 sergiodj+buildbot
  2016-08-17 20:30 ` Failures on Debian-s390x-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 62+ messages in thread
From: sergiodj+buildbot @ 2016-08-17 15:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 951b1f2c88fcd6735392af0d1553f28db9c6b7ea ***

Author: Doug Evans <dje@google.com>
Branch: gdb-7.12-branch
Commit: 951b1f2c88fcd6735392af0d1553f28db9c6b7ea

Make "end" field in feature specs required again.

Newer gdbservers may be talking to older gdbs,
and older gdbs will flag a missing "end" as an error.
So just make "end" required again, and for compatibility
change the default field type to "bool".

gdb/ChangeLog:

	* features/aarch64-core.xml (cpsr_flags): Elide "type" and specify
	"end" in all fields.
	* features/aarch64.c: Regenerate.
	* features/i386/32bit-mpx.xml (_bndcfgu): Specify type of "preserved"
	and "enabled" fields. Correct size of "enabled" field.
	* features/i386/64bit-mpx.xml (_bndcfgu): Specify type of "preserved"
	and "enabled" fields.
	* features/i386/i386-avx-mpx-linux.c: Regenerate.
	* features/i386/i386-avx-mpx.c: Regenerate.
	* features/i386/i386-avx512-linux.c: Regenerate.
	* features/i386/i386-avx512.c: Regenerate.
	* features/i386/i386-mpx-linux.c: Regenerate.
	* features/i386/i386-mpx.c: Regenerate.
	* xml-tdesc.c (tdesc_start_field): Require "end" spec.  Single bit
	fields default to "bool" type.

	Revert 2016-03-15  Doug Evans  <dje@google.com>
	* features/i386/32bit-core.xml (i386_eflags): Remove "end" spec.
	* features/i386/32bit-sse.xml (i386_eflags): Ditto.
	* features/i386/64bit-core.xml (i386_eflags): Ditto.
	* features/i386/64bit-sse.xml (i386_eflags): Ditto.
	* features/i386/x32-core.xml (i386_eflags): Ditto.

gdb/doc/ChangeLog:

	* gdb.texinfo (Target Description Format): Update docs on "end"
	field spec and field default type.

gdb/testsuite/ChangeLog:

	* gdb.xml/extra-regs.xml: Update, end field now required, default type
	for single bitfields is bool.
	* gdb.xml/tdesc-regs.exp: Ditto.


^ permalink raw reply	[flat|nested] 62+ messages in thread
* [binutils-gdb/gdb-7.12-branch] Fix PR gdb/19187 (process record over a fork causes internal error)
@ 2016-08-11  4:18 sergiodj+buildbot
  2016-08-11  6:43 ` Failures on Debian-s390x-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 62+ messages in thread
From: sergiodj+buildbot @ 2016-08-11  4:18 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4dfacf706adacbefbc38d7ba59212566f77bd051 ***

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

Fix PR gdb/19187 (process record over a fork causes internal error)

Right after a fork is detected, we detach breakpoints from the child
(detach_breakpoints), which calls into target_remove_breakpoint with
inferior_ptid pointing at the child process, but leaves the breakpoint
marked inserted (in the parent).

The problem is that record-full.c always deletes all knowledge of the
breakpoint.  Then when we later really delete the breakpoint from the
parent, we fail the assertion, since the breakpoint is unexpectedly
not found in the record-full.c breakpoint table.

The fix is simply to not forget about the breakpoint if we're
detaching it from a fork child.

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

	PR gdb/19187
	* record-full.c (record_full_remove_breakpoint): Don't remove the
	breakpoint from the record_full_breakpoints VEC if we're detaching
	the breakpoint from a fork child.

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

	PR gdb/19187
	* gdb.reverse/waitpid-reverse.exp: Add comment and remove
	setup_kfails.


^ permalink raw reply	[flat|nested] 62+ messages in thread
* [binutils-gdb/gdb-7.12-branch] Simplify remove_breakpoint interface
@ 2016-08-11  1:57 sergiodj+buildbot
  2016-08-11  2:36 ` Failures on Debian-s390x-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 62+ messages in thread
From: sergiodj+buildbot @ 2016-08-11  1:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7c50accb20e77971c775fdb7f5f1bfa605397e80 ***

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

Simplify remove_breakpoint interface

All callers pass mark_uninserted, so there's no need for the 'is'
parameter.

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

	PR gdb/19187
	* breakpoint.c (remove_breakpoint): Remove 'is' parameter and
	always pass mark_uninserted to remove_breakpoint_1.
	(insert_breakpoint_locations, remove_breakpoints)
	(remove_breakpoints_pid, update_global_location_list): Update
	callers.


^ permalink raw reply	[flat|nested] 62+ messages in thread
* [binutils-gdb/gdb-7.12-branch] Quiet ARI gettext checks
@ 2016-08-10 19:27 sergiodj+buildbot
  2016-08-10 21:43 ` Failures on Debian-s390x-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 62+ messages in thread
From: sergiodj+buildbot @ 2016-08-10 19:27 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9be00a778d646d92b7940d74425b58d93cb73d0d ***

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

Quiet ARI gettext checks

The ARI complains about this new file:

 common/signals-state-save-restore.c:46: warning: gettext: All messages should be marked up with _.
 common/signals-state-save-restore.c:59: warning: gettext: All messages should be marked up with _.
 common/signals-state-save-restore.c:87: warning: gettext: All messages should be marked up with _.
 common/signals-state-save-restore.c:92: warning: gettext: All messages should be marked up with _.

Since these are untranslatable strings, use () instead of _().

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

	* common/signals-state-save-restore.c
	(save_original_signals_state, restore_original_signals_state):
	Wrap perror_with_name arguments with '()'.


^ permalink raw reply	[flat|nested] 62+ messages in thread
* [binutils-gdb/gdb-7.12-branch] Fix PR gdb/20418 - Problems with synchronous commands and new-ui
@ 2016-08-10  4:56 sergiodj+buildbot
  2016-08-10 15:56 ` Failures on Debian-s390x-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 62+ messages in thread
From: sergiodj+buildbot @ 2016-08-10  4:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b24bdfa398beba87b48fffeb3b1f9bcfe7bf924d ***

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

Fix PR gdb/20418 - Problems with synchronous commands and new-ui

When executing commands on a secondary UI running the MI interpreter,
some commands that should be synchronous are not.  MI incorrectly
continues processing input right after the synchronous command is
sent, before the target stops.

The problem happens when we emit MI async events (=library-loaded,
etc.), and we go about restoring the previous terminal state, we end
up calling target_terminal_ours, which incorrectly always installs the
current UI's input_fd in the event loop...  That is, code like this:

   old_chain = make_cleanup_restore_target_terminal ();
   target_terminal_ours_for_output ();

   fprintf_unfiltered (mi->event_channel, "library-loaded");

...

   do_cleanups (old_chain);

The fix is to move the add_file_handler/delete_file_handler calls out
of target_terminal_$foo, making these completely no-ops unless called
with the main UI as current UI.

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

	PR gdb/20418
	* event-top.c (ui_register_input_event_handler)
	(ui_unregister_input_event_handler): New functions.
	(async_enable_stdin): Register input in the event loop.
	(async_disable_stdin): Unregister input from the event loop.
	(gdb_setup_readline): Register input in the event loop.
	* infrun.c (check_curr_ui_sync_execution_done): Register input in
	the event loop.
	* target.c (target_terminal_inferior): Don't unregister input from
	the event loop.
	(target_terminal_ours): Don't register input in the event loop.
	* target.h (target_terminal_inferior)
	(target_terminal_ours_for_output, target_terminal_ours): Update
	comments.
	* top.h (ui_register_input_event_handler)
	(ui_unregister_input_event_handler): New declarations.
	* utils.c (ui_unregister_input_event_handler_cleanup)
	(prepare_to_handle_input): New functions.
	(defaulted_query, prompt_for_continue): Use
	prepare_to_handle_input.

gdb/testsuite/ChangeLog:
2016-08-09  Pedro Alves  <palves@redhat.com>
	    Simon Marchi  <simon.marchi@ericsson.com>

	PR gdb/20418
	* gdb.mi/new-ui-mi-sync.c, gdb.mi/new-ui-mi-sync.exp: New files.
	* lib/mi-support.exp (mi_expect_interrupt): Remove anchors.


^ permalink raw reply	[flat|nested] 62+ 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 15:24 ` Failures on Debian-s390x-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 62+ 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] 62+ messages in thread
* [binutils-gdb/gdb-7.12-branch] Synchronize libiberty sources with FSF GCC mainline version.
@ 2016-08-09 16:53 sergiodj+buildbot
  2016-08-09 20:05 ` Failures on Debian-s390x-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 62+ messages in thread
From: sergiodj+buildbot @ 2016-08-09 16:53 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1b6ec8ead3bce335087d6a2a6dc92c3d80d57a98 ***

Author: Nick Clifton <nickc@redhat.com>
Branch: gdb-7.12-branch
Commit: 1b6ec8ead3bce335087d6a2a6dc92c3d80d57a98

Synchronize libiberty sources with FSF GCC mainline version.

include	* libiberty.h (MAX_ALLOCA_SIZE): New macro.

libiberty * make-relative-prefix.c (make_relative_prefix_1): Fall back to
	malloc if alloca argument is greater than MAX_ALLOCA_SIZE.

	* cp-demangle.c (cplus_demangle_operators): Add f[lrLR].
	(d_expression_1): Handle them.
	(d_maybe_print_fold_expression): New.
	(d_print_comp_inner): Use it.
	(d_index_template_argument): Handle negative index.

	* cp-demangle.c (cplus_demangle_operators): Add sP and sZ.
	(d_print_comp_inner): Handle them.
	(d_template_args_1): Split out from d_template_args.
	(d_args_length): New.

	PR c++/70926
	* cplus-dem.c: Handle large values and overflow when demangling
	length variables.
	(demangle_template_value_parm): Read only until end of mangled string.
	(do_hpacc_template_literal): Likewise.
	(do_type): Handle overflow when demangling array indices.

	* cp-demangle.c (cplus_demangle_print_callback): Avoid zero-length
	  VLAs.

	PR c++/70498
	* cp-demangle.c (d_expression_1): Formatting fix.

	* cplus-dem.c (enum type_kind_t): Add tk_rvalue_reference
	constant.
	(demangle_template_value_parm): Handle tk_rvalue_reference
	type kind.
	(do_type): Support 'O' type id (rvalue references).

	* testsuite/demangle-expected: Add tests.

	PR c++/70498
	* cp-demangle.c: Parse numbers as integer instead of long to avoid
	overflow after sanity checks. Include <limits.h> if available.
	(INT_MAX): Define if necessary.
	(d_make_template_param): Takes integer argument instead of long.
	(d_make_function_param): Likewise.
	(d_append_num): Likewise.
	(d_identifier): Likewise.
	(d_number): Parse as and return integer.
	(d_compact_number): Handle overflow.
	(d_source_name): Change variable type to integer for parsed number.
	(d_java_resource): Likewise.
	(d_special_name): Likewise.
	(d_discriminator): Likewise.
	(d_unnamed_type): Likewise.
	* testsuite/demangle-expected: Add regression test cases.

	* configure: Remove SH5 support.

	PR c++/69687
	* cplus-dem.c: Include <limits.h> if available.
	(INT_MAX): Define if necessary.
	(remember_type, remember_Ktype, register_Btype, string_need):
	Abort if we detect cases where we the size of the allocation would
	overflow.

	PR c++/70492
	* cplus-dem.c (gnu_special): Handle case where consume_count returns
	-1.

	PR c++/67394
	PR c++/70481
	* cplus-dem.c (squangle_mop_up): Zero bsize/ksize after freeing
	btypevec/ktypevec.
	* testsuite/demangle-expected: Add coverage tests.


^ permalink raw reply	[flat|nested] 62+ messages in thread
* [binutils-gdb/gdb-7.12-branch] Fix PR gdb/20295: GDB segfaults printing bitfield member of optimized out value
@ 2016-08-09 15:04 sergiodj+buildbot
  2016-08-09 16:31 ` Failures on Debian-s390x-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 62+ messages in thread
From: sergiodj+buildbot @ 2016-08-09 15:04 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT def1145e5b736f7b50179a967d83211251153692 ***

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

Fix PR gdb/20295: GDB segfaults printing bitfield member of optimized out value

With something like:

  struct A { int bitfield:4; } var;

If 'var' ends up wholly-optimized out, printing 'var.bitfield' crashes
gdb here:

 (top-gdb) bt
 #0  0x000000000058b89f in extract_unsigned_integer (addr=0x2 <error: Cannot access memory at address 0x2>, len=2, byte_order=BFD_ENDIAN_LITTLE)
     at /home/pedro/gdb/mygit/src/gdb/findvar.c:109
 #1  0x00000000005a187a in unpack_bits_as_long (field_type=0x16cff70, valaddr=0x0, bitpos=16, bitsize=12) at /home/pedro/gdb/mygit/src/gdb/value.c:3347
 #2  0x00000000005a1b9d in unpack_value_bitfield (dest_val=0x1b5d9d0, bitpos=16, bitsize=12, valaddr=0x0, embedded_offset=0, val=0x1b5d8d0)
     at /home/pedro/gdb/mygit/src/gdb/value.c:3441
 #3  0x00000000005a2a5f in value_fetch_lazy (val=0x1b5d9d0) at /home/pedro/gdb/mygit/src/gdb/value.c:3958
 #4  0x00000000005a10a7 in value_primitive_field (arg1=0x1b5d8d0, offset=0, fieldno=0, arg_type=0x16d04c0) at /home/pedro/gdb/mygit/src/gdb/value.c:3161
 #5  0x00000000005b01e5 in do_search_struct_field (name=0x1727c60 "bitfield", arg1=0x1b5d8d0, offset=0, type=0x16d04c0, looking_for_baseclass=0, result_ptr=0x7fffffffcaf8,
 [...]

unpack_value_bitfield is already optimized-out/unavailable -aware:

   (...) VALADDR points to the contents of VAL.  If the VAL's contents
   required to extract the bitfield from are unavailable/optimized
   out, DEST_VAL is correspondingly marked unavailable/optimized out.

however, it is not considering the case of the value having no
contents buffer at all, as can happen through
allocate_optimized_out_value.

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

	* value.c (unpack_value_bitfield): Skip unpacking if the parent
	has no contents buffer to begin with.

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

	* gdb.dwarf2/bitfield-parent-optimized-out.exp: New file.


^ permalink raw reply	[flat|nested] 62+ messages in thread
* [binutils-gdb/gdb-7.12-branch] Regenerate some target description files
@ 2016-08-09 11:33 sergiodj+buildbot
  2016-08-09 12:06 ` Failures on Debian-s390x-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 62+ messages in thread
From: sergiodj+buildbot @ 2016-08-09 11:33 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d3437d69a3d3fcc28ddb1c17cf2938a422e26222 ***

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

Regenerate some target description files

I regenerated all target description .c files from scratch, and got
this spurious diff.

It's a simple mid-air collision - these files were clearly generated
before commit 73b4f516a037 ("maint_print_c_tdesc_cmd: Use type for
TYPE_CODE_FLAGS instead of field_type."), which did the global
s/field_type/type/, and pushed to master afterwards.

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

	* features/i386/amd64-avx-mpx-linux.c: Regenerate.
	* features/i386/amd64-avx-mpx.c: Regenerate.
	* features/i386/i386-avx-mpx-linux.c: Regenerate.
	* features/i386/i386-avx-mpx.c: Regenerate.


^ permalink raw reply	[flat|nested] 62+ 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:10 ` Failures on Debian-s390x-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 62+ 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] 62+ 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 12:57 ` Failures on Debian-s390x-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 62+ 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] 62+ messages in thread
* [binutils-gdb/gdb-7.12-branch] PR python/18565 - make Frame.function work for inline frames
@ 2016-08-03 19:43 sergiodj+buildbot
  2016-08-03 21:49 ` Failures on Debian-s390x-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 62+ messages in thread
From: sergiodj+buildbot @ 2016-08-03 19:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ff4a25a115a0f477174eb0b4763d186a590c035a ***

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

PR python/18565 - make Frame.function work for inline frames

PR python/18565 notes that calling frame filters don't work properly for
inlined functions.  This happens because Frame.function on an inline
frame will yield the wrong result.  This patch changes this code to use
find_frame_funname instead, which handles inline frames properly.

Built and regtested on x86-64 Fedora 24.

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

	PR python/18565:
	* python/py-frame.c (frapy_function): Use find_frame_funname.

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

	PR python/18565:
	* gdb.python/py-frame-inline.exp: Add Frame.function test.


^ permalink raw reply	[flat|nested] 62+ messages in thread
* [binutils-gdb/gdb-7.12-branch] Avoid potential memory leak in find_frame_funname
@ 2016-08-03 19:10 sergiodj+buildbot
  2016-08-03 20:04 ` Failures on Debian-s390x-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 62+ messages in thread
From: sergiodj+buildbot @ 2016-08-03 19:10 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d2ed2edaf76fc10505214290d04c3cf312acfbca ***

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

Avoid potential memory leak in find_frame_funname

The PR 18565 thread pointed out that, if cp_remove_params can throw
(we aren't quite sure), then find_frame_funname could leak some
memory.  This patch avoids any potential issue by rearranging some
code in find_frame_funname.

Built and regtested on x86-64 Fedora 24.

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

	* stack.c (find_frame_funname): Avoid any possible leak in case
	cp_remove_params can throw.


^ permalink raw reply	[flat|nested] 62+ 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 23:02 ` Failures on Debian-s390x-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 62+ 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] 62+ messages in thread
* [binutils-gdb/gdb-7.12-branch] Set development mode to "off" by default.
@ 2016-08-01 16:47 sergiodj+buildbot
  2016-08-01 18:01 ` Failures on Debian-s390x-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 62+ messages in thread
From: sergiodj+buildbot @ 2016-08-01 16:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b5346540576559e0ec59b61962eacfa17fc395df ***

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

Set development mode to "off" by default.

bfd/ChangeLog:

	* development.sh (development): Set to false.


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

Thread overview: 62+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-08-18 23:09 [binutils-gdb/gdb-7.12-branch] ppc: Fix record of HTM instructions sergiodj+buildbot
2016-08-18 23:05 ` Failures on Fedora-x86_64-native-gdbserver-m32, branch gdb-7.12-branch sergiodj+buildbot
2016-08-18 23:47 ` Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot
2016-08-19  2:12 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot
2016-08-19  2:26 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot
2016-08-19  2:31 ` Failures on Debian-i686, " sergiodj+buildbot
2016-08-19  2:31 ` Failures on Fedora-i686, " sergiodj+buildbot
2016-08-19  2:51 ` Failures on Debian-s390x-m64, " sergiodj+buildbot
2016-08-19  3:34 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-08-19  3:34 ` Failures on Debian-i686-native-extended-gdbserver, " sergiodj+buildbot
2016-08-19  3:49 ` Failures on Fedora-s390x-m64, " sergiodj+buildbot
2016-08-19  4:09 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj+buildbot
2016-08-19  4:11 ` Failures on Fedora-ppc64le-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-08-19  4:39 ` Failures on Fedora-ppc64be-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-08-19  4:58 ` Failures on Fedora-ppc64le-native-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 16:17 ` Failures on Debian-s390x-m64, branch gdb-7.12-branch sergiodj+buildbot
2017-01-21 14:06 [binutils-gdb/gdb-7.12-branch] Set GDB version number to 7.12.1 sergiodj+buildbot
2017-01-21 15:03 ` Failures on Debian-s390x-m64, branch gdb-7.12-branch sergiodj+buildbot
2017-01-21  2:29 [binutils-gdb/gdb-7.12-branch] Fix python-interactive with Python 3.6 sergiodj+buildbot
2017-01-21  4:18 ` Failures on Debian-s390x-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:54 ` Failures on Debian-s390x-m64, branch gdb-7.12-branch sergiodj+buildbot
2016-12-20 20:16 [binutils-gdb/gdb-7.12-branch] gdb: Fix C and C++03 builds sergiodj+buildbot
2016-12-25  6:40 ` Failures on Debian-s390x-m64, branch gdb-7.12-branch sergiodj+buildbot
2016-12-09 18:16 [binutils-gdb/gdb-7.12-branch] Create tdep->rx_psw_type and tdep->rx_fpsw_type lazily sergiodj+buildbot
2016-12-09 19:25 ` Failures on Debian-s390x-m64, branch gdb-7.12-branch sergiodj+buildbot
2016-12-09 17:42 [binutils-gdb/gdb-7.12-branch] Create tdep->rl78_psw_type lazily sergiodj+buildbot
2016-12-09 18:19 ` Failures on Debian-s390x-m64, branch gdb-7.12-branch sergiodj+buildbot
2016-10-25  4:37 [binutils-gdb/gdb-7.12-branch] PR gdb/20653 - small cleanup in string_to_explicit_location sergiodj+buildbot
2016-10-25  5:02 ` Failures on Debian-s390x-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  4:22 ` Failures on Debian-s390x-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 13:19 ` Failures on Debian-s390x-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 19:01 ` Failures on Debian-s390x-m64, branch gdb-7.12-branch sergiodj+buildbot
2016-10-06 21:39 [binutils-gdb/gdb-7.12-branch] frame.h: Forward-declare struct ui_out sergiodj+buildbot
2016-10-07  3:30 ` Failures on Debian-s390x-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-07  1:00 ` Failures on Debian-s390x-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 23:23 ` Failures on Debian-s390x-m64, branch gdb-7.12-branch sergiodj+buildbot
2016-10-06 13:29 [binutils-gdb/gdb-7.12-branch] Fix PR11094: JIT breakpoint is not properly recreated on reruns sergiodj+buildbot
2016-10-06 16:28 ` Failures on Debian-s390x-m64, branch gdb-7.12-branch sergiodj+buildbot
2016-10-06 13:25 [binutils-gdb/gdb-7.12-branch] Fix a few gdb.base/jit-simple.exp problems sergiodj+buildbot
2016-10-06 15:36 ` Failures on Debian-s390x-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-04  0:44 ` Failures on Debian-s390x-m64, branch gdb-7.12-branch sergiodj+buildbot
2016-09-29 22:19 [binutils-gdb/gdb-7.12-branch] PR gdb/20609 - attach of JIT-debug-enabled inf 7.11.1 regression sergiodj+buildbot
2016-09-30 10:08 ` Failures on Debian-s390x-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 18:38 ` Failures on Debian-s390x-m64, branch gdb-7.12-branch sergiodj+buildbot
2016-09-21 13:28 [binutils-gdb/gdb-7.12-branch] ppc: Fix record support of Store String Word instructions sergiodj+buildbot
2016-09-21 14:25 ` Failures on Debian-s390x-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 11:37 ` Failures on Debian-s390x-m64, branch gdb-7.12-branch sergiodj+buildbot
2016-09-07  3:24 [binutils-gdb/gdb-7.12-branch] new-ui command: gdb internal errors if input is already pending sergiodj+buildbot
2016-09-07 16:34 ` Failures on Debian-s390x-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 19:20 ` Failures on Debian-s390x-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 14:16 ` Failures on Debian-s390x-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:15 ` Failures on Debian-s390x-m64, branch gdb-7.12-branch sergiodj+buildbot
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  7:00 ` Failures on Debian-s390x-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:29 ` Failures on Debian-s390x-m64, branch gdb-7.12-branch sergiodj+buildbot
2016-08-24  0:49 [binutils-gdb/gdb-7.12-branch] x32 Fast tracepoints: IPA target descriptions sergiodj+buildbot
2016-08-24  1:17 ` Failures on Debian-s390x-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 23:33 ` Failures on Debian-s390x-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 18:42 ` Failures on Debian-s390x-m64, branch gdb-7.12-branch sergiodj+buildbot
2016-08-23  8:36 [binutils-gdb/gdb-7.12-branch] Fix PR gdb/20505 - Make vDSO detection work with core files sergiodj+buildbot
2016-08-23 10:20 ` Failures on Debian-s390x-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  6:37 ` Failures on Debian-s390x-m64, branch gdb-7.12-branch sergiodj+buildbot
2016-08-17 15:30 [binutils-gdb/gdb-7.12-branch] Make "end" field in feature specs required again sergiodj+buildbot
2016-08-17 20:30 ` Failures on Debian-s390x-m64, branch gdb-7.12-branch sergiodj+buildbot
2016-08-11  4:18 [binutils-gdb/gdb-7.12-branch] Fix PR gdb/19187 (process record over a fork causes internal error) sergiodj+buildbot
2016-08-11  6:43 ` Failures on Debian-s390x-m64, branch gdb-7.12-branch sergiodj+buildbot
2016-08-11  1:57 [binutils-gdb/gdb-7.12-branch] Simplify remove_breakpoint interface sergiodj+buildbot
2016-08-11  2:36 ` Failures on Debian-s390x-m64, branch gdb-7.12-branch sergiodj+buildbot
2016-08-10 19:27 [binutils-gdb/gdb-7.12-branch] Quiet ARI gettext checks sergiodj+buildbot
2016-08-10 21:43 ` Failures on Debian-s390x-m64, branch gdb-7.12-branch sergiodj+buildbot
2016-08-10  4:56 [binutils-gdb/gdb-7.12-branch] Fix PR gdb/20418 - Problems with synchronous commands and new-ui sergiodj+buildbot
2016-08-10 15:56 ` Failures on Debian-s390x-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 15:24 ` Failures on Debian-s390x-m64, branch gdb-7.12-branch sergiodj+buildbot
2016-08-09 16:53 [binutils-gdb/gdb-7.12-branch] Synchronize libiberty sources with FSF GCC mainline version sergiodj+buildbot
2016-08-09 20:05 ` Failures on Debian-s390x-m64, branch gdb-7.12-branch sergiodj+buildbot
2016-08-09 15:04 [binutils-gdb/gdb-7.12-branch] Fix PR gdb/20295: GDB segfaults printing bitfield member of optimized out value sergiodj+buildbot
2016-08-09 16:31 ` Failures on Debian-s390x-m64, branch gdb-7.12-branch sergiodj+buildbot
2016-08-09 11:33 [binutils-gdb/gdb-7.12-branch] Regenerate some target description files sergiodj+buildbot
2016-08-09 12:06 ` Failures on Debian-s390x-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:10 ` Failures on Debian-s390x-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 12:57 ` Failures on Debian-s390x-m64, branch gdb-7.12-branch sergiodj+buildbot
2016-08-03 19:43 [binutils-gdb/gdb-7.12-branch] PR python/18565 - make Frame.function work for inline frames sergiodj+buildbot
2016-08-03 21:49 ` Failures on Debian-s390x-m64, branch gdb-7.12-branch sergiodj+buildbot
2016-08-03 19:10 [binutils-gdb/gdb-7.12-branch] Avoid potential memory leak in find_frame_funname sergiodj+buildbot
2016-08-03 20:04 ` Failures on Debian-s390x-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 23:02 ` Failures on Debian-s390x-m64, branch gdb-7.12-branch sergiodj+buildbot
2016-08-01 16:47 [binutils-gdb/gdb-7.12-branch] Set development mode to "off" by default sergiodj+buildbot
2016-08-01 18:01 ` Failures on Debian-s390x-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).