public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
* [binutils-gdb/gdb-7.12-branch] [GDBserver] Fix conversion warning
@ 2016-10-25  3:26 sergiodj+buildbot
  2016-10-25  3:26 ` Failures on Debian-s390x-native-extended-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
                   ` (17 more replies)
  0 siblings, 18 replies; 50+ 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] 50+ messages in thread
* [binutils-gdb/gdb-7.12-branch] update copyright year range in GDB files
@ 2017-01-01  8:58 sergiodj+buildbot
  2017-01-01 17:09 ` Failures on Fedora-ppc64be-cc-with-index, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 50+ messages in thread
From: sergiodj+buildbot @ 2017-01-01  8:58 UTC (permalink / raw)
  To: gdb-testers

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

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

update copyright year range in GDB files

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

gdb/ChangeLog:

        Update copyright year range in all GDB files.


^ permalink raw reply	[flat|nested] 50+ 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-23  9:08 ` Failures on Fedora-ppc64be-cc-with-index, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 50+ 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] 50+ messages in thread
* [binutils-gdb/gdb-7.12-branch] Create tdep->rl78_psw_type lazily
@ 2016-12-09 17:42 sergiodj+buildbot
  2016-12-16 11:02 ` Failures on Fedora-ppc64be-cc-with-index, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 50+ 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] 50+ 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 16:05 ` Failures on Fedora-ppc64be-cc-with-index, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 50+ 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] 50+ messages in thread
* [binutils-gdb/gdb-7.12-branch] Include strings.h where available
@ 2016-10-14  7:58 sergiodj+buildbot
  2016-10-14 22:34 ` Failures on Fedora-ppc64be-cc-with-index, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 50+ messages in thread
From: sergiodj+buildbot @ 2016-10-14  7:58 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9e7fe25aebc4fe4a2c1af15447b44f50c3c97b2f ***

Author: Eli Zaretskii <eliz@gnu.org>
Branch: gdb-7.12-branch
Commit: 9e7fe25aebc4fe4a2c1af15447b44f50c3c97b2f

Include strings.h where available

gdb/ChangeLog

2016-10-14  Eli Zaretskii  <eliz@gnu.org>

	* common/common-defs.h [HAVE_STRINGS_H]: Include strings.h if
	available, to get prototypes of 'strcasecmp' and 'strncasecmp'.

(cherry picked from commit 8ffc1bb12a22e548835c9291871ad0eb68b7f6f0)


^ permalink raw reply	[flat|nested] 50+ 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:47 ` Failures on Fedora-ppc64be-cc-with-index, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 50+ 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] 50+ 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-09  6:41 ` Failures on Fedora-ppc64be-cc-with-index, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 50+ 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] 50+ 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-08  5:50 ` Failures on Fedora-ppc64be-cc-with-index, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 50+ 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] 50+ 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-08 21:41 ` Failures on Fedora-ppc64be-cc-with-index, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 50+ 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] 50+ 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 20:42 ` Failures on Fedora-ppc64be-cc-with-index, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 50+ 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] 50+ 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 20:37 ` Failures on Fedora-ppc64be-cc-with-index, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 50+ 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] 50+ messages in thread
* [binutils-gdb/gdb-7.12-branch] xtensa: Avoid designated inits, for C++ compliance
@ 2016-08-26 19:14 sergiodj+buildbot
  2016-08-29 14:57 ` Failures on Fedora-ppc64be-cc-with-index, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 50+ messages in thread
From: sergiodj+buildbot @ 2016-08-26 19:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e529eb722d213875230dbcd0c856390f840f1863 ***

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

xtensa: Avoid designated inits, for C++ compliance

C++ does not officially support designators in initializer lists.  Thus
some compilers may issue errors when encountering them.  Modern versions
of GCC seem to allow them by default, as a GCC extension, even though
the GCC documentation explicitly states otherwise: "[...] This extension
is not implemented in GNU C++."  But some older GCC versions (like
4.4.7) did indeed emit an error instead, like this:

  .../gdb/xtensa-config.c:219: error: expected primary-expression before
			       . token

This patch removes the only such instance I've seen when building with
'--enable-targets=all'.

gdb/ChangeLog:

	* xtensa-tdep.h (XTENSA_GDBARCH_TDEP_INSTANTIATE): Replace
	designated initializer list by plain initializer list, for C++
	compliance.


^ permalink raw reply	[flat|nested] 50+ messages in thread
* [binutils-gdb/gdb-7.12-branch] Sync proc_service definition with GLIBC
@ 2016-08-25 13:07 sergiodj+buildbot
  2016-08-25 23:50 ` Failures on Fedora-ppc64be-cc-with-index, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 50+ 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] 50+ 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:42 ` Failures on Fedora-ppc64be-cc-with-index, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 50+ 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] 50+ 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 18:18 ` Failures on Fedora-ppc64be-cc-with-index, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 50+ 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] 50+ 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 Fedora-ppc64be-cc-with-index, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 50+ 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] 50+ 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-24  0:34 ` Failures on Fedora-ppc64be-cc-with-index, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 50+ 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] 50+ 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-22 13:40 ` Failures on Fedora-ppc64be-cc-with-index, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 50+ 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] 50+ 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-16 14:18 ` Failures on Fedora-ppc64be-cc-with-index, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 50+ 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] 50+ 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:36 ` Failures on Fedora-ppc64be-cc-with-index, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 50+ 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] 50+ 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:41 ` Failures on Fedora-ppc64be-cc-with-index, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 50+ 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] 50+ messages in thread
* [binutils-gdb/gdb-7.12-branch] Simplify remove_breakpoint interface
@ 2016-08-11  1:57 sergiodj+buildbot
  2016-08-11 18:49 ` Failures on Fedora-ppc64be-cc-with-index, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 50+ 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] 50+ messages in thread
* [binutils-gdb/gdb-7.12-branch] Quiet ARI gettext checks
@ 2016-08-10 19:27 sergiodj+buildbot
  2016-08-10 23:45 ` Failures on Fedora-ppc64be-cc-with-index, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 50+ 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] 50+ 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:23 ` Failures on Fedora-ppc64be-cc-with-index, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 50+ 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] 50+ messages in thread
* [binutils-gdb/gdb-7.12-branch] Fix PR gdb/18653: gdb disturbs inferior's inherited signal dispositions
@ 2016-08-09 22:55 sergiodj+buildbot
  2016-08-10  6:39 ` Failures on Fedora-ppc64be-cc-with-index, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 50+ messages in thread
From: sergiodj+buildbot @ 2016-08-09 22:55 UTC (permalink / raw)
  To: gdb-testers

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

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

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

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

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

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

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

And neither does it reset signal masks or flags.

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

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

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

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

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

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

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


^ permalink raw reply	[flat|nested] 50+ 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 22:10 ` Failures on Fedora-ppc64be-cc-with-index, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 50+ 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] 50+ 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 20:50 ` Failures on Fedora-ppc64be-cc-with-index, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 50+ 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] 50+ messages in thread
* [binutils-gdb/gdb-7.12-branch] gdb/configure --help: suggest --disable-build-with-cxx instead of --enable...
@ 2016-08-05 17:24 sergiodj+buildbot
  2016-08-05 22:04 ` Failures on Fedora-ppc64be-cc-with-index, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 50+ messages in thread
From: sergiodj+buildbot @ 2016-08-05 17:24 UTC (permalink / raw)
  To: gdb-testers

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

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

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

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

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

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

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

	* configure: Regenerate.


^ permalink raw reply	[flat|nested] 50+ messages in thread
* [binutils-gdb/gdb-7.12-branch] Quiet ptrace error ESRCH in regsets_fetch_inferior_registers
@ 2016-08-04 11:11 sergiodj+buildbot
  2016-08-04 15:47 ` Failures on Fedora-ppc64be-cc-with-index, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 50+ messages in thread
From: sergiodj+buildbot @ 2016-08-04 11:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 367ed8910ee791720f99a28ad0320f430bd910d9 ***

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

Quiet ptrace error ESRCH in regsets_fetch_inferior_registers

When I run process-dies-while-detaching.exp with GDBserver, I see many
warnings printed by GDBserver,

ptrace(regsets_fetch_inferior_registers) PID=26183: No such process
ptrace(regsets_fetch_inferior_registers) PID=26183: No such process
ptrace(regsets_fetch_inferior_registers) PID=26184: No such process
ptrace(regsets_fetch_inferior_registers) PID=26184: No such process

regsets_fetch_inferior_registers is called when GDBserver resumes each
lwp.

 #2  0x0000000000428260 in regsets_fetch_inferior_registers (regsets_info=0x4690d0 <aarch64_regsets_info>, regcache=0x31832020)
    at /home/yao/SourceCode/gnu/gdb/git/gdb/gdbserver/linux-low.c:5412
 #3  0x00000000004070e8 in get_thread_regcache (thread=0x31832940, fetch=fetch@entry=1) at /home/yao/SourceCode/gnu/gdb/git/gdb/gdbserver/regcache.c:58
 #4  0x0000000000429c40 in linux_resume_one_lwp_throw (info=<optimized out>, signal=0, step=0, lwp=0x31832830)
    at /home/yao/SourceCode/gnu/gdb/git/gdb/gdbserver/linux-low.c:4463
 #5  linux_resume_one_lwp (lwp=0x31832830, step=<optimized out>, signal=<optimized out>, info=<optimized out>)
    at /home/yao/SourceCode/gnu/gdb/git/gdb/gdbserver/linux-low.c:4573

The is the case that threads are disappeared when GDB/GDBserver resumes
them.  We check errno for ESRCH, and don't print error messages, like
what we are doing in regsets_store_inferior_registers.

gdb/gdbserver:

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

	* linux-low.c (regsets_fetch_inferior_registers): Check
	errno is ESRCH or not.


^ permalink raw reply	[flat|nested] 50+ messages in thread
* [binutils-gdb/gdb-7.12-branch] Bump GDB version number to 7.11.90.DATE-git.
@ 2016-08-01 19:25 sergiodj+buildbot
  2016-08-02 11:17 ` Failures on Fedora-ppc64be-cc-with-index, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 50+ messages in thread
From: sergiodj+buildbot @ 2016-08-01 19:25 UTC (permalink / raw)
  To: gdb-testers

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

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

Bump GDB version number to 7.11.90.DATE-git.

gdb/ChangeLog:

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


^ permalink raw reply	[flat|nested] 50+ messages in thread
* [binutils-gdb/gdb-7.12-branch] gdb/NEWS: rename "since GDB 7.11" into "in GDB 7.12".
@ 2016-08-01 18:28 sergiodj+buildbot
  2016-08-02  6:10 ` Failures on Fedora-ppc64be-cc-with-index, branch gdb-7.12-branch sergiodj+buildbot
  0 siblings, 1 reply; 50+ messages in thread
From: sergiodj+buildbot @ 2016-08-01 18:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ad08bd595b31907b8cd414fa900055bacd68e112 ***

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

gdb/NEWS: rename "since GDB 7.11" into "in GDB 7.12".

gdb/ChangeLog:

        * NEWS: Rename "since GDB 7.11" section into "in GDB 7.12" section.


^ permalink raw reply	[flat|nested] 50+ messages in thread

end of thread, other threads:[~2017-01-01 17:09 UTC | newest]

Thread overview: 50+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-10-25  3:26 [binutils-gdb/gdb-7.12-branch] [GDBserver] Fix conversion warning sergiodj+buildbot
2016-10-25  3:26 ` Failures on Debian-s390x-native-extended-gdbserver-m64, branch gdb-7.12-branch sergiodj+buildbot
2016-10-25  4:22 ` Failures on Debian-s390x-m64, " sergiodj+buildbot
2016-10-25  6:01 ` Failures on Debian-i686-native-extended-gdbserver, " sergiodj+buildbot
2016-10-25  6:42 ` Failures on Fedora-s390x-m64, " sergiodj+buildbot
2016-10-25  6:49 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot
2016-10-25  6:50 ` Failures on Debian-i686, " sergiodj+buildbot
2016-10-25  6:55 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot
2016-10-25  7:04 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot
2016-10-25  7:09 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot
2016-10-25  7:24 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-10-25  7:27 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot
2016-10-25  7:32 ` Failures on Fedora-i686, " sergiodj+buildbot
2016-10-25 11:31 ` Failures on Fedora-ppc64be-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-10-25 12:39 ` Failures on Fedora-ppc64be-cc-with-index, " sergiodj+buildbot
2016-10-25 13:43 ` Failures on Fedora-ppc64le-native-gdbserver-m64, " sergiodj+buildbot
2016-10-25 14:17 ` Failures on Fedora-ppc64le-m64, " sergiodj+buildbot
2016-10-25 15:27 ` Failures on Fedora-ppc64le-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-10-25 16:01 ` Failures on Fedora-ppc64le-cc-with-index, " sergiodj+buildbot
  -- strict thread matches above, loose matches on Subject: below --
2017-01-01  8:58 [binutils-gdb/gdb-7.12-branch] update copyright year range in GDB files sergiodj+buildbot
2017-01-01 17:09 ` Failures on Fedora-ppc64be-cc-with-index, 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-23  9:08 ` Failures on Fedora-ppc64be-cc-with-index, 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-16 11:02 ` Failures on Fedora-ppc64be-cc-with-index, 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 16:05 ` Failures on Fedora-ppc64be-cc-with-index, branch gdb-7.12-branch sergiodj+buildbot
2016-10-14  7:58 [binutils-gdb/gdb-7.12-branch] Include strings.h where available sergiodj+buildbot
2016-10-14 22:34 ` Failures on Fedora-ppc64be-cc-with-index, 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:47 ` Failures on Fedora-ppc64be-cc-with-index, 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-09  6:41 ` Failures on Fedora-ppc64be-cc-with-index, 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-08  5:50 ` Failures on Fedora-ppc64be-cc-with-index, 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-08 21:41 ` Failures on Fedora-ppc64be-cc-with-index, 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 20:42 ` Failures on Fedora-ppc64be-cc-with-index, 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 20:37 ` Failures on Fedora-ppc64be-cc-with-index, branch gdb-7.12-branch sergiodj+buildbot
2016-08-26 19:14 [binutils-gdb/gdb-7.12-branch] xtensa: Avoid designated inits, for C++ compliance sergiodj+buildbot
2016-08-29 14:57 ` Failures on Fedora-ppc64be-cc-with-index, branch gdb-7.12-branch sergiodj+buildbot
2016-08-25 13:07 [binutils-gdb/gdb-7.12-branch] Sync proc_service definition with GLIBC sergiodj+buildbot
2016-08-25 23:50 ` Failures on Fedora-ppc64be-cc-with-index, 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:42 ` Failures on Fedora-ppc64be-cc-with-index, 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 18:18 ` Failures on Fedora-ppc64be-cc-with-index, 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 Fedora-ppc64be-cc-with-index, 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-24  0:34 ` Failures on Fedora-ppc64be-cc-with-index, 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-22 13:40 ` Failures on Fedora-ppc64be-cc-with-index, 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-16 14:18 ` Failures on Fedora-ppc64be-cc-with-index, 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:36 ` Failures on Fedora-ppc64be-cc-with-index, 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:41 ` Failures on Fedora-ppc64be-cc-with-index, 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 18:49 ` Failures on Fedora-ppc64be-cc-with-index, 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 23:45 ` Failures on Fedora-ppc64be-cc-with-index, 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:23 ` Failures on Fedora-ppc64be-cc-with-index, branch gdb-7.12-branch sergiodj+buildbot
2016-08-09 22:55 [binutils-gdb/gdb-7.12-branch] Fix PR gdb/18653: gdb disturbs inferior's inherited signal dispositions sergiodj+buildbot
2016-08-10  6:39 ` Failures on Fedora-ppc64be-cc-with-index, 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 22:10 ` Failures on Fedora-ppc64be-cc-with-index, 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 20:50 ` Failures on Fedora-ppc64be-cc-with-index, branch gdb-7.12-branch sergiodj+buildbot
2016-08-05 17:24 [binutils-gdb/gdb-7.12-branch] gdb/configure --help: suggest --disable-build-with-cxx instead of --enable sergiodj+buildbot
2016-08-05 22:04 ` Failures on Fedora-ppc64be-cc-with-index, branch gdb-7.12-branch sergiodj+buildbot
2016-08-04 11:11 [binutils-gdb/gdb-7.12-branch] Quiet ptrace error ESRCH in regsets_fetch_inferior_registers sergiodj+buildbot
2016-08-04 15:47 ` Failures on Fedora-ppc64be-cc-with-index, branch gdb-7.12-branch sergiodj+buildbot
2016-08-01 19:25 [binutils-gdb/gdb-7.12-branch] Bump GDB version number to 7.11.90.DATE-git sergiodj+buildbot
2016-08-02 11:17 ` Failures on Fedora-ppc64be-cc-with-index, branch gdb-7.12-branch sergiodj+buildbot
2016-08-01 18:28 [binutils-gdb/gdb-7.12-branch] gdb/NEWS: rename "since GDB 7.11" into "in GDB 7.12" sergiodj+buildbot
2016-08-02  6:10 ` Failures on Fedora-ppc64be-cc-with-index, 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).