public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
* [binutils-gdb/gdb-7.11-branch] testsuite: Fix false Fortran regressions with recent gcc
@ 2016-02-14  8:52 sergiodj+buildbot
  2016-02-14  8:52 ` Failures on RHEL-s390x-m64, branch gdb-7.11-branch sergiodj+buildbot
                   ` (15 more replies)
  0 siblings, 16 replies; 27+ messages in thread
From: sergiodj+buildbot @ 2016-02-14  8:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 46e42194d8d2585b6860b1267c2b3e24ba9c589c ***

Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Branch: gdb-7.11-branch
Commit: 46e42194d8d2585b6860b1267c2b3e24ba9c589c

testsuite: Fix false Fortran regressions with recent gcc

gcc-4.9.2-6.fc21.x86_64 -> gcc-5.3.1-2.fc23.x86_64

-PASS: gdb.fortran/vla-ptype.exp: ptype pvla not initialized
+FAIL: gdb.fortran/vla-ptype.exp: ptype pvla not initialized
-PASS: gdb.fortran/vla-history.exp: print vla1 allocated
+FAIL: gdb.fortran/vla-history.exp: print vla1 allocated
-PASS: gdb.fortran/vla-history.exp: print $2
+FAIL: gdb.fortran/vla-history.exp: print $2
-PASS: gdb.fortran/vla-value.exp: print undefined pvla
+FAIL: gdb.fortran/vla-value.exp: print undefined pvla
-PASS: gdb.fortran/vla-value.exp: print non-associated &pvla
+FAIL: gdb.fortran/vla-value.exp: print non-associated &pvla
-PASS: gdb.fortran/vla-value.exp: print undefined pvla(1,3,8)
+FAIL: gdb.fortran/vla-value.exp: print undefined pvla(1,3,8)

These issues get fixed (or removed if no longer applicable) by attached patch.

It is based on Googled:
	http://www.cs.rpi.edu/~szymansk/OOF90/bugs.html#5
	When a pointer is declared its status is undefined, and cannot be
	safely queried with the associated intrinsic.
	-> nullify(VARNAME)
+
	https://software.intel.com/en-us/forums/intel-fortran-compiler-for-linux-and-mac-os-x/topic/268786
	ALLOCATE is not supposed to initialize the array.
	-> Remove checks like an initial print is: \\( *0, *0, *0...\\)

These regressions remain:
	-PASS: gdb.fortran/library-module.exp: print var_i in lib
	+FAIL: gdb.fortran/library-module.exp: print var_i in lib
	-PASS: gdb.fortran/library-module.exp: print var_i in main
	+FAIL: gdb.fortran/library-module.exp: print var_i in main
I believe it is more a GDB bug (in a code contributed by me), filed:
	gdb.fortran/library-module.exp false regression on GCC upgrade
	https://sourceware.org/bugzilla/show_bug.cgi?id=19635

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

	Fix compatibility with recent gfortran-5.3.1.
	* gdb.fortran/vla-history.exp (print vla1 allocated)
	(print vla2 allocated, print $2, print $3): Remove
	(print $4): Rename to ...
	(print $2): ... here.
	(print $9): Rename to ...
	(print $5): ... here.
	(print $10): Rename to ...
	(print $6): ... here.
	* gdb.fortran/vla.f90: Add pvla initialization.


^ permalink raw reply	[flat|nested] 27+ messages in thread
* [binutils-gdb/gdb-7.11-branch] Sync proc_service definition with GLIBC
@ 2016-08-25 17:45 sergiodj+buildbot
  2016-08-25 19:15 ` Failures on Debian-s390x-m64, branch gdb-7.11-branch sergiodj+buildbot
  0 siblings, 1 reply; 27+ messages in thread
From: sergiodj+buildbot @ 2016-08-25 17:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 140bf80050b34f0947b34dba93b830ea2bfc5040 ***

Author: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Branch: gdb-7.11-branch
Commit: 140bf80050b34f0947b34dba93b830ea2bfc5040

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] 27+ messages in thread
* [binutils-gdb/gdb-7.11-branch] Make gdb/linux-nat.c consider a waitstatus pending on the infrun side
@ 2016-05-25 17:52 sergiodj+buildbot
  2016-05-25 22:47 ` Failures on Debian-s390x-m64, branch gdb-7.11-branch sergiodj+buildbot
  0 siblings, 1 reply; 27+ messages in thread
From: sergiodj+buildbot @ 2016-05-25 17:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a0de87e7be6a58dfeb9bfb00172dbd975dabb72e ***

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

Make gdb/linux-nat.c consider a waitstatus pending on the infrun side

Working on the fix for gdb/19828, I saw
gdb.threads/attach-many-short-lived-threads.exp fail once in an
unusual way.  Unfortunately I didn't keep debug logs, but it's an
issue similar to what's been fixed in remote.c a while ago --
linux-nat.c was not fetching the pending status from the right place.

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

	PR gdb/19828
	* linux-nat.c (get_pending_status): If the thread reported the
	event to the core and it's pending, use the pending status signal
	number.


^ permalink raw reply	[flat|nested] 27+ messages in thread
* [binutils-gdb/gdb-7.11-branch] Add mi-threads-interrupt.exp test (PR 20039)
@ 2016-05-18 14:59 sergiodj+buildbot
  2016-05-18 18:49 ` Failures on Debian-s390x-m64, branch gdb-7.11-branch sergiodj+buildbot
  0 siblings, 1 reply; 27+ messages in thread
From: sergiodj+buildbot @ 2016-05-18 14:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cf2cd51217c0b99f5370708cc3932c12a1f4edad ***

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

Add mi-threads-interrupt.exp test (PR 20039)

Add a new test for PR 20039.  The test spawns new threads, then tries to
interrupt, continue, and interrupt again.  This use case was fixed by
commit 5fe966540d6b748f825774868463003700f0c878 in master, but gdb 7.11
is affected (so if you try it on the gdb-7.11-branch right now, the test
will fail).

New in v2, the test now handles mi-async on mode properly.  The failure
was specific to mi-async off, but I don't think it's bad to test the
same thing under async on mode.  I added a little hack when running in
async mode to work around bug 20045.

I also removed one continue/interrupt pair, as a single one was enough to
trigger the problem.

gdb/testsuite/ChangeLog:

	* gdb.mi/mi-threads-interrupt.c: New file.
	* gdb.mi/mi-threads-interrupt.exp: New file.


^ permalink raw reply	[flat|nested] 27+ messages in thread
* [binutils-gdb/gdb-7.11-branch] Fix double prompt output after run control MI commands with mi-async on (PR 20045)
@ 2016-05-18 14:48 sergiodj+buildbot
  2016-05-18 17:13 ` Failures on Debian-s390x-m64, branch gdb-7.11-branch sergiodj+buildbot
  0 siblings, 1 reply; 27+ messages in thread
From: sergiodj+buildbot @ 2016-05-18 14:48 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f0a8d0dc70eddbf1e323e8c07f5092ff5e327548 ***

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

Fix double prompt output after run control MI commands with mi-async on (PR 20045)

When you use a run control command (-exec-run, -exec-continue,
-exec-next, ...) with mi-async on, an extra (gdb) prompt is displayed:

  -exec-continue
  ^running
  *running,thread-id="all"
  (gdb)
  (gdb)

It doesn't seem to be a big problem for front-ends, since this behavior
started in gdb 7.9 and we haven't heard anything about that.  However,
it caused me some trouble while writing a test for PR 20039 [1].

The problem comes from an extra (gdb) prompt that we write when running
in mi-async off mode to emulate a past buggy behavior.  When executing a
run control command synchronously, previous gdbs always printed a prompt
right away, even though they are not ready to accept new MI commands
until the target stops.  Only at this time should they display a prompt.
But to keep backwards compatibility apparently, we print it anyway.
Since commit 198297aaf, the condition that decides whether we should
print that "bogus" prompt or not has become true, even when running with
mi-async on.  Since we already print a prompt at the end of the
asynchronous command execution, it results in two prompts for one
command.

The proposed fix is to call target_can_async_p instead of
target_is_async_p, to make the condition:

  if (!target_can_async_p () || sync_execution)
    ... show prompt ...

That shows the prompt if we are emulating a synchronous command on top
of an asynchronous target (sync_execution) or if the target simply can't
run asynchronously (!target_can_async_p ()).

Note that this code is changed and this bug fixed by Pedro's separate
console series, but I think it would be nice to have it fixed in the
mean time.

I ran the gdb.mi directory of the testsuite with mi-async on and off, I
didn't see any regressions.

gdb/ChangeLog:

	* mi/mi-main.c (mi_on_resume): Call target_can_async_p instead
	of target_is_async_p.

[1] https://sourceware.org/ml/gdb-patches/2016-05/msg00075.html


^ permalink raw reply	[flat|nested] 27+ messages in thread
* [binutils-gdb/gdb-7.11-branch] [gdb] Fix -Wparentheses warnings
@ 2016-05-03  9:05 sergiodj+buildbot
  2016-05-03 10:06 ` Failures on Debian-s390x-m64, branch gdb-7.11-branch sergiodj+buildbot
  0 siblings, 1 reply; 27+ messages in thread
From: sergiodj+buildbot @ 2016-05-03  9:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 386c90348551eb089124d64c9bc6ab17cbefb016 ***

Author: Kyrylo Tkachov <kyrylo.tkachov@arm.com>
Branch: gdb-7.11-branch
Commit: 386c90348551eb089124d64c9bc6ab17cbefb016

[gdb] Fix -Wparentheses warnings

2016-05-03  Kyrylo Tkachov  <kyrylo.tkachov@arm.com>

	* symfile.c (find_pc_overlay): Add braces to avoid -Wparentheses
	warning.
	(find_pc_mapped_section): Likewise.
	(list_overlays_command): Likewise.


^ permalink raw reply	[flat|nested] 27+ messages in thread
* [binutils-gdb/gdb-7.11-branch] Handle MIPS Linux SIGTRAP siginfo.si_code values
@ 2016-04-15 23:43 sergiodj+buildbot
  2016-04-16  0:40 ` Failures on Debian-s390x-m64, branch gdb-7.11-branch sergiodj+buildbot
  0 siblings, 1 reply; 27+ messages in thread
From: sergiodj+buildbot @ 2016-04-15 23:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 619f36aa006c4263ec17b1d2a73613f840042c16 ***

Author: Pedro Alves <palves@redhat.com>
Branch: gdb-7.11-branch
Commit: 619f36aa006c4263ec17b1d2a73613f840042c16

Handle MIPS Linux SIGTRAP siginfo.si_code values

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

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

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

Basically, this commit:

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

- Adds GDB_ARCH_IS_TRAP_HWBKPT.

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

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

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

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

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

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


^ permalink raw reply	[flat|nested] 27+ messages in thread
* [binutils-gdb/gdb-7.11-branch] btrace: fix PR gdb/19829
@ 2016-03-17 11:28 sergiodj+buildbot
  2016-03-18  1:50 ` Failures on Debian-s390x-m64, branch gdb-7.11-branch sergiodj+buildbot
  0 siblings, 1 reply; 27+ messages in thread
From: sergiodj+buildbot @ 2016-03-17 11:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2ef34d11f61d79dcb152713aa059051d8cd3295d ***

Author: Markus Metzger <markus.t.metzger@intel.com>
Branch: gdb-7.11-branch
Commit: 2ef34d11f61d79dcb152713aa059051d8cd3295d

btrace: fix PR gdb/19829

This is a backport of

33b4777ca1b7 btrace, frame: fix crash in get_frame_type
a038fa3e14a4 stack: check frame_unwind_caller_id
2f3ef606b912 frame: add skip_tailcall_frames

In skip_artificial_frames we repeatedly call get_prev_frame_always until we get
a non-inline and non-tailcall frame assuming that there must be such a frame
eventually.

For record targets, however, we may have a frame chain that consists only of
artificial frames.  This leads to a crash in get_frame_type when dereferencing a
NULL frame pointer.

Change skip_artificial_frames and skip_tailcall_frames to return NULL in such a
case and modify each caller to cope with a NULL return.

In frame_unwind_caller_pc and frame_unwind_caller_arch, we simply assert that
the returned value is not NULL.  Their caller was supposed to check
frame_unwind_caller_id before calling those functions.

In other cases, we thrown an error.

In infcmd further move the skip_tailcall_frames call to the forward-stepping
case since we don't need a frame for reverse execution and we don't want to fail
because of that.  Reverse-finish does make sense for a tailcall frame.

gdb/
	* frame.h (skip_tailcall_frames): New.
	* infcmd.c (finish_command): Call skip_tailcall_frames.
	* frame.c (skip_artificial_frames): Return NULL if only artificial frames
	are found.  Update comment.
	(frame_pop): Call skip_tailcall_frames.
	(frame_unwind_caller_id): Handle NULL return.
	(frame_unwind_caller_pc, frame_unwind_caller_arch): Assert that
	skip_artificial_frames does not return NULL.
	(frame_pop): Add an error if only tailcall frames are found.
	* infcmd.c (finish_command): Move skip_tailcall_frames call into forward-
	execution case.  Add an error if only tailcall frames are found.
	* stack.c (frame_info): Check frame_unwind_caller_id.

testsuite/
	* gdb.btrace/tailcall-only.exp: New.
	* gdb.btrace/tailcall-only.c: New.
	* gdb.btrace/x86_64-tailcall-only.S: New.
	* gdb.btrace/i686-tailcall-only.S: New.


^ permalink raw reply	[flat|nested] 27+ messages in thread
* [binutils-gdb/gdb-7.11-branch] Add missing gdb.arch/i386-prologue.c prototypes
@ 2016-02-15 18:24 sergiodj+buildbot
  2016-02-15 20:20 ` Failures on Debian-s390x-m64, branch gdb-7.11-branch sergiodj+buildbot
  0 siblings, 1 reply; 27+ messages in thread
From: sergiodj+buildbot @ 2016-02-15 18:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 906c69d06a46cec2f55941f7dc3a5323261796d5 ***

Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Branch: gdb-7.11-branch
Commit: 906c69d06a46cec2f55941f7dc3a5323261796d5

Add missing gdb.arch/i386-prologue.c prototypes

The testfile has not ran because:
gdb.arch/i386-prologue.c:34:3: warning: implicit declaration of function 'standard' [-Wimplicit-function-declaration]
   standard ();
   ^
gdb.arch/i386-prologue.c:35:3: warning: implicit declaration of function 'stack_align_ecx' [-Wimplicit-function-declaration]
   stack_align_ecx ();
   ^
gdb.arch/i386-prologue.c:36:3: warning: implicit declaration of function 'stack_align_edx' [-Wimplicit-function-declaration]
   stack_align_edx ();
   ^
gdb.arch/i386-prologue.c:37:3: warning: implicit declaration of function 'stack_align_eax' [-Wimplicit-function-declaration]
   stack_align_eax ();
   ^

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

	* gdb.arch/i386-prologue.c: Add missing prototypes.


^ permalink raw reply	[flat|nested] 27+ messages in thread
* [binutils-gdb/gdb-7.11-branch] gdb/version.in: Replace -cvs suffix by -git suffix
@ 2016-02-10  9:41 sergiodj+buildbot
  2016-02-10 10:14 ` Failures on Debian-s390x-m64, branch gdb-7.11-branch sergiodj+buildbot
  0 siblings, 1 reply; 27+ messages in thread
From: sergiodj+buildbot @ 2016-02-10  9:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7bcc056ca977328fa96a24fd747834f100be863a ***

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

gdb/version.in: Replace -cvs suffix by -git suffix

gdb/ChangeLog:

        * version.in: Replace -cvs suffix by -git suffix.


^ permalink raw reply	[flat|nested] 27+ messages in thread
* [binutils-gdb/gdb-7.11-branch] Set GDB version number to 7.10.90.
@ 2016-02-10  4:23 sergiodj+buildbot
  2016-02-10  8:22 ` Failures on Debian-s390x-m64, branch gdb-7.11-branch sergiodj+buildbot
  0 siblings, 1 reply; 27+ messages in thread
From: sergiodj+buildbot @ 2016-02-10  4:23 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8e1043a37a176f07f0e06d29fe2f54752c8976e5 ***

Author: Joel Brobecker <brobecker@adacore.com>
Branch: gdb-7.11-branch
Commit: 8e1043a37a176f07f0e06d29fe2f54752c8976e5

Set GDB version number to 7.10.90.

gdb/ChangeLog:

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


^ permalink raw reply	[flat|nested] 27+ messages in thread
end of thread, other threads:[~2016-08-25  9:48 UTC | newest]

Thread overview: 27+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-02-14  8:52 [binutils-gdb/gdb-7.11-branch] testsuite: Fix false Fortran regressions with recent gcc sergiodj+buildbot
2016-02-14  8:52 ` Failures on RHEL-s390x-m64, branch gdb-7.11-branch sergiodj+buildbot
2016-02-14  9:48 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot
2016-02-14 10:03 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot
2016-02-14 10:17 ` Failures on Fedora-s390x-m64, " sergiodj+buildbot
2016-02-14 10:21 ` Failures on AIX-POWER7-plain, " sergiodj+buildbot
2016-02-14 11:14 ` Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot
2016-02-14 11:23 ` Failures on Debian-s390x-m64, " sergiodj+buildbot
2016-02-14 12:00 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-02-14 12:27 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-02-14 12:38 ` Failures on Fedora-ppc64be-cc-with-index, " sergiodj+buildbot
2016-02-14 12:51 ` Failures on Debian-i686-native-extended-gdbserver, " sergiodj+buildbot
2016-02-14 13:16 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj+buildbot
2016-02-14 13:36 ` Failures on Fedora-ppc64be-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-02-14 14:38 ` Failures on Fedora-ppc64le-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-02-14 14:58 ` Failures on Fedora-ppc64le-cc-with-index, " sergiodj+buildbot
2016-02-14 15:15 ` Failures on Fedora-ppc64le-native-gdbserver-m64, " sergiodj+buildbot
  -- strict thread matches above, loose matches on Subject: below --
2016-08-25 17:45 [binutils-gdb/gdb-7.11-branch] Sync proc_service definition with GLIBC sergiodj+buildbot
2016-08-25 19:15 ` Failures on Debian-s390x-m64, branch gdb-7.11-branch sergiodj+buildbot
2016-05-25 17:52 [binutils-gdb/gdb-7.11-branch] Make gdb/linux-nat.c consider a waitstatus pending on the infrun side sergiodj+buildbot
2016-05-25 22:47 ` Failures on Debian-s390x-m64, branch gdb-7.11-branch sergiodj+buildbot
2016-05-18 14:59 [binutils-gdb/gdb-7.11-branch] Add mi-threads-interrupt.exp test (PR 20039) sergiodj+buildbot
2016-05-18 18:49 ` Failures on Debian-s390x-m64, branch gdb-7.11-branch sergiodj+buildbot
2016-05-18 14:48 [binutils-gdb/gdb-7.11-branch] Fix double prompt output after run control MI commands with mi-async on (PR 20045) sergiodj+buildbot
2016-05-18 17:13 ` Failures on Debian-s390x-m64, branch gdb-7.11-branch sergiodj+buildbot
2016-05-03  9:05 [binutils-gdb/gdb-7.11-branch] [gdb] Fix -Wparentheses warnings sergiodj+buildbot
2016-05-03 10:06 ` Failures on Debian-s390x-m64, branch gdb-7.11-branch sergiodj+buildbot
2016-04-15 23:43 [binutils-gdb/gdb-7.11-branch] Handle MIPS Linux SIGTRAP siginfo.si_code values sergiodj+buildbot
2016-04-16  0:40 ` Failures on Debian-s390x-m64, branch gdb-7.11-branch sergiodj+buildbot
2016-03-17 11:28 [binutils-gdb/gdb-7.11-branch] btrace: fix PR gdb/19829 sergiodj+buildbot
2016-03-18  1:50 ` Failures on Debian-s390x-m64, branch gdb-7.11-branch sergiodj+buildbot
2016-02-15 18:24 [binutils-gdb/gdb-7.11-branch] Add missing gdb.arch/i386-prologue.c prototypes sergiodj+buildbot
2016-02-15 20:20 ` Failures on Debian-s390x-m64, branch gdb-7.11-branch sergiodj+buildbot
2016-02-10  9:41 [binutils-gdb/gdb-7.11-branch] gdb/version.in: Replace -cvs suffix by -git suffix sergiodj+buildbot
2016-02-10 10:14 ` Failures on Debian-s390x-m64, branch gdb-7.11-branch sergiodj+buildbot
2016-02-10  4:23 [binutils-gdb/gdb-7.11-branch] Set GDB version number to 7.10.90 sergiodj+buildbot
2016-02-10  8:22 ` Failures on Debian-s390x-m64, branch gdb-7.11-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).