public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
* [binutils-gdb/gdb-7.12-branch] Sync proc_service definition with GLIBC
@ 2016-08-25 13:07 sergiodj+buildbot
  2016-08-25 13:08 ` Failures on Fedora-x86_64-native-gdbserver-m32, branch gdb-7.12-branch sergiodj+buildbot
                   ` (16 more replies)
  0 siblings, 17 replies; 55+ messages in thread
From: sergiodj+buildbot @ 2016-08-25 13:07 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f2f45a7252a4bd977c135cc77536cbc0e9669cf2 ***

Author: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Branch: gdb-7.12-branch
Commit: f2f45a7252a4bd977c135cc77536cbc0e9669cf2

Sync proc_service definition with GLIBC

GLIBC BZ#20311 [1] proc_service.h install patch also remove 'const'
attributes from ps_get_thread_area and comment #15 discuss why to remove
the const attribute (basically since it a callback with the struct
ps_prochandle owned by the client it should be able to modify it if
it the case).

On default build this is not the issue and current g++ does not trigger
any issue with this mismatch declaration.  However, on some bootstrap
build configuration where gdbserver is build with gcc instead this
triggers:

error: conflicting types for 'ps_get_thread_area'

This patch fixes it by syncing the declaration with GLIBC.

[1] https://sourceware.org/bugzilla/show_bug.cgi?id=20311

gdb/ChangeLog:

2016-08-25  Adhemerval Zanella  <adhemerval.zanella@linaro.org>

	* aarch64-linux-nat.c (ps_get_thread_area): Remove const from
	struct ps_prochandle.
	* amd64-linux-nat.c (ps_get_thread_area): Likewise.
	* arm-linux-nat.c (ps_get_thread_area): Likewise.
	* gdb_proc_service.h (ps_get_thread_area): Likewise.
	* i386-linux-nat.c (ps_get_thread_area): Likewise.
	* m68klinux-nat.c (ps_get_thread_area): Likewise.
	* mips-linux-nat.c (ps_get_thread_area): Likewise.
	* nat/aarch64-linux.c (aarch64_ps_get_thread_area): Likewise.
	* nat/aarch64-linux.h (aarch64_ps_get_thread_area): Likewise.
	* xtensa-linux-nat.c (ps_get_thread_area): Likewise.

gdb/gdbserver/ChangeLog:

2016-08-25  Adhemerval Zanella  <adhemerval.zanella@linaro.org>

	PR server/20491
	* gdb_proc_service.h (ps_get_thread_area): Remove const from struct
	ps_prochandle.
	* linux-aarch64-low.c (ps_get_thread_area): Likewise.
	* linux-arm-low.c (ps_get_thread_area): Likewise.
	* linux-crisv32-low.c (ps_get_thread_area): Likewise.
	* linux-m68k-low.c (ps_get_thread_area): Likewise.
	* linux-mips-low.c (ps_get_thread_area): Likewise.
	* linux-nios2-low.c (ps_get_thread_area): Likewise.
	* linux-tic6x-low.c (ps_get_thread_area): Likewise.
	* linux-x86-low.c (ps_get_thread_area): Likewise.
	* linux-xtensa-low.c (ps_get_thread_area): Likewise.


^ permalink raw reply	[flat|nested] 55+ messages in thread
[parent not found: <@gdb-build>]
* [binutils-gdb] Don't add PHDR for objcopy/strip or ld script specifying PHDRS
@ 2016-12-13  0:21 sergiodj+buildbot
  2016-12-23 16:27 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 55+ messages in thread
From: sergiodj+buildbot @ 2016-12-13  0:21 UTC (permalink / raw)
  To: gdb-testers

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

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

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

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

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


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

*** TEST RESULTS FOR COMMIT cd48ce152d6710af146ffc7897a82586513fc534 ***

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

sim: mips: fix dv-tx3904cpu build error

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

This was broken by the clean up in commit d47f5b30d8481272e9480118bdcb.

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


^ permalink raw reply	[flat|nested] 55+ 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 14:28 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 55+ 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] 55+ messages in thread
* [binutils-gdb/gdb-7.12-branch] mips-tdep: Make FCRs always 32-bit
@ 2016-10-06 19:26 sergiodj+buildbot
  2016-10-07  0:11 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 55+ messages in thread
From: sergiodj+buildbot @ 2016-10-06 19:26 UTC (permalink / raw)
  To: gdb-testers

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

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

mips-tdep: Make FCRs always 32-bit

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

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

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

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

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

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

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

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


^ permalink raw reply	[flat|nested] 55+ messages in thread
* [binutils-gdb/gdb-7.12-branch] mips-tdep: Rearrange comments in `mips_pseudo_register_type'
@ 2016-10-06 19:23 sergiodj+buildbot
  2016-10-06 23:14 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 55+ 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] 55+ messages in thread
* [binutils-gdb/gdb-7.12-branch] stack: fix gdb.dwarf2/dw2-undefined-ret-addr.exp regression
@ 2016-10-06 15:41 sergiodj+buildbot
  2016-10-06 17:58 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 55+ messages in thread
From: sergiodj+buildbot @ 2016-10-06 15:41 UTC (permalink / raw)
  To: gdb-testers

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

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

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

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

Treat a missing frame_id as OPTIMIZED_OUT_ERROR instead.

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


^ permalink raw reply	[flat|nested] 55+ 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  6:06 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 55+ 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] 55+ 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:05 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 55+ 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] 55+ 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 15:13 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 55+ 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] 55+ 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-19  5:17 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 55+ 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] 55+ messages in thread
* [binutils-gdb/gdb-7.12-branch] Introduce make_cleanup_restore_current_ui
@ 2016-09-07  2:09 sergiodj+buildbot
  2016-09-07 18:06 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 55+ messages in thread
From: sergiodj+buildbot @ 2016-09-07  2:09 UTC (permalink / raw)
  To: gdb-testers

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

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

Introduce make_cleanup_restore_current_ui

Just a tidy, no functional changes.

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

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


^ permalink raw reply	[flat|nested] 55+ 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:40 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 55+ 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] 55+ 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:50 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 55+ 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] 55+ 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  9:28 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 55+ 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] 55+ 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-25  6:49 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 55+ 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] 55+ messages in thread
* [binutils-gdb/gdb-7.12-branch] x32: Avoid unsigned long when installing fast tracepoint jump pads
@ 2016-08-24  2:15 sergiodj+buildbot
  2016-08-25  3:32 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 55+ messages in thread
From: sergiodj+buildbot @ 2016-08-24  2:15 UTC (permalink / raw)
  To: gdb-testers

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

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

x32: Avoid unsigned long when installing fast tracepoint jump pads

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

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

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

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


^ permalink raw reply	[flat|nested] 55+ 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 17:28 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 55+ 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] 55+ 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 19:12 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 55+ 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] 55+ 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 10:09 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 55+ 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] 55+ messages in thread
* [binutils-gdb/gdb-7.12-branch] null-terminate string in linespec_location_completer
@ 2016-08-19 19:27 sergiodj+buildbot
  2016-08-20  3:47 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 55+ messages in thread
From: sergiodj+buildbot @ 2016-08-19 19:27 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d71004b8fe2ab0f3e1fc6dede74821f7c287f521 ***

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

null-terminate string in linespec_location_completer

If I build gdb with -fsanitize=address and run tests, I get error,

malformed linespec error: unexpected colon^M
(gdb) PASS: gdb.linespec/ls-errs.exp: lang=C: break     :
break   :=================================================================^M
==3266==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x602000051451 at pc 0x2b5797a972a8 bp 0x7fffd8e0f3c0 sp 0x7fffd8e0f398^M
READ of size 2 at 0x602000051451 thread T0
    #0 0x2b5797a972a7 in __interceptor_strlen (/usr/lib/x86_64-linux-gnu/libasan.so.1+0x322a7)^M
    #1 0x7bd004 in compare_filenames_for_search(char const*, char const*) /home/yao/SourceCode/gnu/gdb/git/gdb/symtab.c:316^M
    #2 0x7bd310 in iterate_over_some_symtabs(char const*, char const*, int (*)(symtab*, void*), void*, compunit_symtab*, compunit_symtab*) /home/yao/SourceCode/gnu/gdb/git/gdb/symtab.c:411^M
    #3 0x7bd775 in iterate_over_symtabs(char const*, int (*)(symtab*, void*), void*) /home/yao/SourceCode/gnu/gdb/git/gdb/symtab.c:481^M
    #4 0x7bda15 in lookup_symtab(char const*) /home/yao/SourceCode/gnu/gdb/git/gdb/symtab.c:527^M
    #5 0x7d5e2a in make_file_symbol_completion_list_1 /home/yao/SourceCode/gnu/gdb/git/gdb/symtab.c:5635^M
    #6 0x7d61e1 in make_file_symbol_completion_list(char const*, char const*, char const*) /home/yao/SourceCode/gnu/gdb/git/gdb/symtab.c:5684^M
    #7 0x88dc06 in linespec_location_completer /home/yao/SourceCode/gnu/gdb/git/gdb/completer.c:288
....
0x602000051451 is located 0 bytes to the right of 1-byte region [0x602000051450,0x602000051451)^M
mallocated by thread T0 here:
    #0 0x2b5797ab97ef in __interceptor_malloc (/usr/lib/x86_64-linux-gnu/libasan.so.1+0x547ef)^M
    #1 0xbbfb8d in xmalloc /home/yao/SourceCode/gnu/gdb/git/gdb/common/common-utils.c:43^M
    #2 0x88dabd in linespec_location_completer /home/yao/SourceCode/gnu/gdb/git/gdb/completer.c:273^M
    #3 0x88e5ef in location_completer(cmd_list_element*, char const*, char const*) /home/yao/SourceCode/gnu/gdb/git/gdb/completer.c:531^M
    #4 0x8902e7 in complete_line_internal /home/yao/SourceCode/gnu/gdb/git/gdb/completer.c:964^

The code in question is here

       file_to_match = (char *) xmalloc (colon - text + 1);
       strncpy (file_to_match, text, colon - text + 1);

it is likely that file_to_match is not null-terminated.  The patch is
to strncpy 'colon - text' bytes and explicitly set '\0'.

gdb:

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

	* completer.c (linespec_location_completer): Make file_to_match
	null-terminated.


^ permalink raw reply	[flat|nested] 55+ messages in thread
* [binutils-gdb/gdb-7.12-branch] ppc: Fix record of HTM instructions
@ 2016-08-18 23:09 sergiodj+buildbot
  2016-08-19  3:34 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 55+ 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] 55+ messages in thread
* [binutils-gdb/gdb-7.12-branch] [GDB] Fix builds broken by proc-service changes.
@ 2016-08-15 21:31 sergiodj+buildbot
  2016-08-16 14:36 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 55+ messages in thread
From: sergiodj+buildbot @ 2016-08-15 21:31 UTC (permalink / raw)
  To: gdb-testers

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

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

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

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

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

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

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

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

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

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

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


^ permalink raw reply	[flat|nested] 55+ messages in thread
* [binutils-gdb/gdb-7.12-branch] Fix heap-buffer-overflow in explicit_location_lex_one
@ 2016-08-15 15:08 sergiodj+buildbot
  2016-08-15 19:27 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 55+ messages in thread
From: sergiodj+buildbot @ 2016-08-15 15:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 23d4200c35e9325436f8bb3f9382dd5e4847a21f ***

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

Fix heap-buffer-overflow in explicit_location_lex_one

I build GDB with -fsanitize=address, and see the error in tests,

(gdb) PASS: gdb.linespec/ls-errs.exp: lang=C++: break 3 foo
break -line 3 foo^M
=================================================================^M
==4401==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x603000047487 at pc 0x819d8e bp 0x7fff4e4e6bb0 sp 0x7fff4e4e6ba8^M
READ of size 1 at 0x603000047487 thread T0^[[1m^[[0m^M
    #0 0x819d8d in explicit_location_lex_one /home/yao/SourceCode/gnu/gdb/git/gdb/location.c:502^M
    #1 0x81a185 in string_to_explicit_location(char const**, language_defn const*, int) /home/yao/SourceCode/gnu/gdb/git/gdb/location.c:556^M
    #2 0x81ac10 in string_to_event_location(char**, language_defn const*) /home/yao/SourceCode/gnu/gdb/git/gdb/location.c:687^

the code in question is:

>         /* Special case: C++ operator,.  */
>         if (language->la_language == language_cplus
>             && strncmp (*inp, "operator", 8)  <--- [1]
>             && (*inp)[9] == ',')
>           (*inp) += 9;
>         ++(*inp);

The error is caused by the access to (*inp)[9] if 9 is out of its bounds.
However [1] looks odd to me, because if strncmp returns true (non-zero),
the following check "(*inp)[9] == ','" makes no sense any more.  I
suspect it was a typo in the code we meant to "strncmp () == 0".  Another
problem in the code above is that if *inp is "operator,", we first
increment *inp by 9, and then increment it by one again, which is wrong
to me.  We should only increment *inp by 8 to skip "operator", and go
back to the loop header to decide where we stop.

gdb:

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

	* location.c (explicit_location_lex_one): Compare the return
	value of strncmp with zero.  Don't check (*inp)[9].  Increment
	*inp by 8.


^ permalink raw reply	[flat|nested] 55+ messages in thread
* [binutils-gdb/gdb-7.12-branch] sim: bfin: split out common mach/model defines into arch.h [PR sim/20438]
@ 2016-08-14  2:03 sergiodj+buildbot
  2016-08-14  7:26 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 55+ messages in thread
From: sergiodj+buildbot @ 2016-08-14  2:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 253daf2f8e1d136d8bfd591d711e63832f507235 ***

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

sim: bfin: split out common mach/model defines into arch.h [PR sim/20438]

The current machs.h mixes common enums with Blackfin-specific defines.
This causes us troubles with header inclusion order such that we can't
drop the old SIM_CPU typedef (which is duplicated in common code).  By
splitting the two up, we can unwind this dependency chain, and drop the
old typedef.  It also fixes building with older gcc versions.


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

*** TEST RESULTS FOR COMMIT c0c8e5aea12c938a1e73c1d32912b094c3329288 ***

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

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

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

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

this patch is to remove the argument from fprintf.

gdb/testsuite:

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

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


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

*** TEST RESULTS FOR COMMIT e565c44e294111fdc2b84396917b0c4ffed916fb ***

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

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

Fixes, on NIOS GNU/Linux:

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

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

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

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


^ permalink raw reply	[flat|nested] 55+ 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-12  1:47 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 55+ 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] 55+ messages in thread
* [binutils-gdb/gdb-7.12-branch] Plumb enum remove_bp_reason all the way to target_remove_breakpoint
@ 2016-08-11  3:36 sergiodj+buildbot
  2016-08-12  1:21 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 55+ messages in thread
From: sergiodj+buildbot @ 2016-08-11  3:36 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT aac9c6220f36cea74d13cd02cce6c64d49f41f34 ***

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

Plumb enum remove_bp_reason all the way to target_remove_breakpoint

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

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

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


^ permalink raw reply	[flat|nested] 55+ messages in thread
* [binutils-gdb/gdb-7.12-branch] Simplify remove_breakpoint interface
@ 2016-08-11  1:57 sergiodj+buildbot
  2016-08-12  0:25 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 55+ 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] 55+ 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 17:47 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 55+ 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] 55+ messages in thread
* [binutils-gdb/gdb-7.12-branch] Fix PR remote/20398: File-IO write always outputs "Quit"
@ 2016-08-05 19:41 sergiodj+buildbot
  2016-08-05 23:30 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 55+ messages in thread
From: sergiodj+buildbot @ 2016-08-05 19:41 UTC (permalink / raw)
  To: gdb-testers

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

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

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

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

Failed output:

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

Expected output:

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

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

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

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


^ permalink raw reply	[flat|nested] 55+ 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 22:05 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 55+ 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] 55+ 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 15:47 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 55+ 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] 55+ 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 23:05 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 55+ 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] 55+ 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 21:45 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 55+ 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] 55+ messages in thread
* [binutils-gdb/gdb-7.12-branch] Bump version to 7.11.90.DATE-git.
@ 2016-08-01 16:14 sergiodj+buildbot
  2016-08-01 16:48 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 55+ messages in thread
From: sergiodj+buildbot @ 2016-08-01 16:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d1c4e52ec0c8d13a04588e3abfb3d6b1df942905 ***

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

Bump version to 7.11.90.DATE-git.

Now that the GDB 7.12 branch has been created, we can
bump the version number.

gdb/ChangeLog:

	GDB 7.12 branch created (41bfcd638a4e0e48b96ce4de2845372dea481322):
	* version.in: Bump version to 7.11.90.DATE-git.


^ permalink raw reply	[flat|nested] 55+ messages in thread
end of thread, other threads:[~2016-12-23 16:27 UTC | newest]

Thread overview: 55+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-08-25 13:07 [binutils-gdb/gdb-7.12-branch] Sync proc_service definition with GLIBC sergiodj+buildbot
2016-08-25 13:08 ` Failures on Fedora-x86_64-native-gdbserver-m32, branch gdb-7.12-branch sergiodj+buildbot
2016-08-25 16:00 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot
2016-08-25 17:06 ` Failures on Ubuntu-AArch64-m64, " sergiodj+buildbot
2016-08-25 17:42 ` Failures on Fedora-i686, " sergiodj+buildbot
2016-08-25 17:51 ` Failures on Debian-x86_64-m64, " sergiodj+buildbot
2016-08-25 18:16 ` Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot
2016-08-25 18:40 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot
2016-08-25 18:53 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-08-25 18:53 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-08-25 19:04 ` Failures on Fedora-s390x-m64, " sergiodj+buildbot
2016-08-25 20:08 ` Failures on Debian-i686, " sergiodj+buildbot
2016-08-25 21:19 ` Failures on Debian-i686-native-extended-gdbserver, " sergiodj+buildbot
2016-08-25 22:29 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj+buildbot
2016-08-25 23:31 ` Failures on Fedora-ppc64be-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-08-25 23:50 ` Failures on Fedora-ppc64be-cc-with-index, " sergiodj+buildbot
2016-08-26 10:27 ` Failures on Fedora-ppc64le-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-08-26 10:57 ` Failures on Fedora-ppc64le-native-gdbserver-m64, " sergiodj+buildbot
     [not found] <@gdb-build>
2016-12-23 16:53 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot
  -- strict thread matches above, loose matches on Subject: below --
2016-12-13  0:21 [binutils-gdb] Don't add PHDR for objcopy/strip or ld script specifying PHDRS sergiodj+buildbot
2016-12-23 16:27 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
2016-11-11  7:48 [binutils-gdb/gdb-7.12-branch] sim: mips: fix dv-tx3904cpu build error sergiodj+buildbot
2016-11-11  8:42 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
2016-10-12 12:26 [binutils-gdb/gdb-7.12-branch] [AArch64] Track FP registers in prologue analyzer sergiodj+buildbot
2016-10-12 14:28 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
2016-10-06 19:26 [binutils-gdb/gdb-7.12-branch] mips-tdep: Make FCRs always 32-bit sergiodj+buildbot
2016-10-07  0:11 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
2016-10-06 19:23 [binutils-gdb/gdb-7.12-branch] mips-tdep: Rearrange comments in `mips_pseudo_register_type' sergiodj+buildbot
2016-10-06 23:14 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
2016-10-06 15:41 [binutils-gdb/gdb-7.12-branch] stack: fix gdb.dwarf2/dw2-undefined-ret-addr.exp regression sergiodj+buildbot
2016-10-06 17:58 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
2016-10-03 23:07 [binutils-gdb/gdb-7.12-branch] Introduce cleanup to restore current_uiout sergiodj+buildbot
2016-10-04  6:06 ` Failures on Debian-x86_64-native-extended-gdbserver-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:05 ` Failures on Debian-x86_64-native-extended-gdbserver-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 15:13 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
2016-09-17  5:25 [binutils-gdb/gdb-7.12-branch] Backport lastest POWER9 support to match final ISA 3.0 documentation sergiodj+buildbot
2016-09-19  5:17 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
2016-09-07  2:09 [binutils-gdb/gdb-7.12-branch] Introduce make_cleanup_restore_current_ui sergiodj+buildbot
2016-09-07 18:06 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
2016-09-01  8:54 [binutils-gdb/gdb-7.12-branch] Fix lwp_suspend/unsuspend imbalance in linux_wait_1 sergiodj+buildbot
2016-09-01 19:40 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
2016-08-31 10:26 [binutils-gdb/gdb-7.12-branch] Fix order of inferiors in "thread apply all" sergiodj+buildbot
2016-08-31 14:50 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
2016-08-24 22:31 [binutils-gdb/gdb-7.12-branch] Allow resetting an empty inferior-tty sergiodj+buildbot
2016-08-25  9:28 ` Failures on Debian-x86_64-native-extended-gdbserver-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-25  6:49 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
2016-08-24  2:15 [binutils-gdb/gdb-7.12-branch] x32: Avoid unsigned long when installing fast tracepoint jump pads sergiodj+buildbot
2016-08-25  3:32 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
2016-08-24  1:34 [binutils-gdb/gdb-7.12-branch] x32 Fast tracepoints: Customize jump pad address sergiodj+buildbot
2016-08-24 17:28 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
2016-08-23 17:02 [binutils-gdb/gdb-7.12-branch] Fix signals-state-child.exp in remote testing sergiodj+buildbot
2016-08-23 19:12 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
2016-08-19 21:36 [binutils-gdb/gdb-7.12-branch] [AArch64] Match instruction "STP with base register" in prologue sergiodj+buildbot
2016-08-20 10:09 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
2016-08-19 19:27 [binutils-gdb/gdb-7.12-branch] null-terminate string in linespec_location_completer sergiodj+buildbot
2016-08-20  3:47 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
2016-08-18 23:09 [binutils-gdb/gdb-7.12-branch] ppc: Fix record of HTM instructions sergiodj+buildbot
2016-08-19  3:34 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
2016-08-15 21:31 [binutils-gdb/gdb-7.12-branch] [GDB] Fix builds broken by proc-service changes sergiodj+buildbot
2016-08-16 14:36 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
2016-08-15 15:08 [binutils-gdb/gdb-7.12-branch] Fix heap-buffer-overflow in explicit_location_lex_one sergiodj+buildbot
2016-08-15 19:27 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
2016-08-14  2:03 [binutils-gdb/gdb-7.12-branch] sim: bfin: split out common mach/model defines into arch.h [PR sim/20438] sergiodj+buildbot
2016-08-14  7:26 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
2016-08-12 15:06 [binutils-gdb/gdb-7.12-branch] Fix warning in gdb.base/signals-state-child.c sergiodj+buildbot
2016-08-13 21:32 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
2016-08-12  6:37 [binutils-gdb/gdb-7.12-branch] Fix fallout from gdb/20413's fix (x32: linux_ptrace_test_ret_to_nx: Cannot PTRACE_PEEKUSER) sergiodj+buildbot
2016-08-12 13:17 ` Failures on Debian-x86_64-native-extended-gdbserver-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-12  1:47 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
2016-08-11  3:36 [binutils-gdb/gdb-7.12-branch] Plumb enum remove_bp_reason all the way to target_remove_breakpoint sergiodj+buildbot
2016-08-12  1:21 ` Failures on Debian-x86_64-native-extended-gdbserver-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-12  0:25 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
2016-08-10  2:14 [binutils-gdb/gdb-7.12-branch] Fix PR mi/20431 - Missing MI prompts after sync execution MI command (-exec-continue, etc.) errors sergiodj+buildbot
2016-08-10 17:47 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
2016-08-05 19:41 [binutils-gdb/gdb-7.12-branch] Fix PR remote/20398: File-IO write always outputs "Quit" sergiodj+buildbot
2016-08-05 23:30 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
2016-08-05 18:42 [binutils-gdb/gdb-7.12-branch] gdb/NEWS: Mention that C++ is now the default sergiodj+buildbot
2016-08-05 22:05 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
2016-08-04 12:07 [binutils-gdb/gdb-7.12-branch] Determine target description for native aarch64 sergiodj+buildbot
2016-08-04 15:47 ` Failures on Debian-x86_64-native-extended-gdbserver-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 23:05 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
2016-08-01 19:05 [binutils-gdb/gdb-7.12-branch] Set GDB version number to 7.11.90 sergiodj+buildbot
2016-08-01 21:45 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
2016-08-01 16:14 [binutils-gdb/gdb-7.12-branch] Bump version to 7.11.90.DATE-git sergiodj+buildbot
2016-08-01 16:48 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).