public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
* [binutils-gdb/gdb-7.11-branch] Remove gdb/python/python.c code that handles strlen failing with -1
@ 2016-05-03 11:46 sergiodj+buildbot
  2016-05-03 11:47 ` Failures on RHEL-s390x-m64, branch gdb-7.11-branch sergiodj+buildbot
                   ` (16 more replies)
  0 siblings, 17 replies; 31+ messages in thread
From: sergiodj+buildbot @ 2016-05-03 11:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT aaa3178dfb979f8ec476a326aca273125a1e3ee9 ***

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

Remove gdb/python/python.c code that handles strlen failing with -1

This makes no sense -- strlen doesn't really ever fail with -1.

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

	* python/python.c (_initialize_python) [IS_PY3K]: Remove dead
	code.


^ permalink raw reply	[flat|nested] 31+ messages in thread
* [binutils-gdb/gdb-7.11-branch] Bump GDB version number to 7.11.1.DATE-git.
@ 2016-06-01  1:18 sergiodj+buildbot
  2016-06-01  2:14 ` Failures on Fedora-ppc64be-m64, branch gdb-7.11-branch sergiodj+buildbot
  0 siblings, 1 reply; 31+ messages in thread
From: sergiodj+buildbot @ 2016-06-01  1:18 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d03dfbf66983602a4cdb97c37edd54c420ceed40 ***

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

Bump GDB version number to 7.11.1.DATE-git.

gdb/ChangeLog:

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


^ permalink raw reply	[flat|nested] 31+ messages in thread
* [binutils-gdb/gdb-7.11-branch] Set GDB version number to 7.11.1.
@ 2016-06-01  0:54 sergiodj+buildbot
  2016-06-01  1:08 ` Failures on Fedora-ppc64be-m64, branch gdb-7.11-branch sergiodj+buildbot
  0 siblings, 1 reply; 31+ messages in thread
From: sergiodj+buildbot @ 2016-06-01  0:54 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 41d82368c333de4f7ec3fd7734ee683055e8c35c ***

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

Set GDB version number to 7.11.1.

gdb/ChangeLog:

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


^ permalink raw reply	[flat|nested] 31+ 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-26 14:52 ` Failures on Fedora-ppc64be-m64, branch gdb-7.11-branch sergiodj+buildbot
  0 siblings, 1 reply; 31+ 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] 31+ 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-19  4:07 ` Failures on Fedora-ppc64be-m64, branch gdb-7.11-branch sergiodj+buildbot
  0 siblings, 1 reply; 31+ 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] 31+ 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-19  2:40 ` Failures on Fedora-ppc64be-m64, branch gdb-7.11-branch sergiodj+buildbot
  0 siblings, 1 reply; 31+ 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] 31+ messages in thread
* [binutils-gdb/gdb-7.11-branch] Fix -exec-run not running asynchronously with mi-async on (PR gdb/18077)
@ 2016-05-17 22:13 sergiodj+buildbot
  2016-05-18 14:57 ` Failures on Fedora-ppc64be-m64, branch gdb-7.11-branch sergiodj+buildbot
  0 siblings, 1 reply; 31+ messages in thread
From: sergiodj+buildbot @ 2016-05-17 22:13 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b5f0db46b3057bcb64243e7da0943717abd6459b ***

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

Fix -exec-run not running asynchronously with mi-async on (PR gdb/18077)

When doing -exec-run on a freshly started GDB, the only target on the
target stack at the time the dummy one.  When mi_async_p is called to
know whether the run should be async, it queries whether the current
target (dummy) supports async, and the answer is no.  The fix is to make
the code query the target that will be used for the run, which is not
necessarily the current target.

No regressions in the gdb.mi directory using the unix, native-gdbserver
and native-extended-gdbserver boards.  The test doesn't pass when
forcing maint set target-async off, obviously, since it makes mi-async
have no effect.  It doesn't seem like other tests are checking for that
eventuality, so I didn't in the new test.

gdb/ChangeLog:

	* mi/mi-main.c (run_one_inferior): Use run target to determine
	whether to run async or not.
	(mi_cmd_exec_run): Likewise.

gdb/testsuite/ChangeLog:

	* gdb.mi/mi-async-run.exp: New file.
	* gdb.mi/mi-async-run.c: New file.


^ permalink raw reply	[flat|nested] 31+ messages in thread
* [binutils-gdb/gdb-7.11-branch] Workaround gdbserver<7.7 for setfs
@ 2016-04-27 19:52 sergiodj+buildbot
  2016-04-28  0:40 ` Failures on Fedora-ppc64be-m64, branch gdb-7.11-branch sergiodj+buildbot
  0 siblings, 1 reply; 31+ messages in thread
From: sergiodj+buildbot @ 2016-04-27 19:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a6ff23076f49c6322d96a76e0098f8019139bc4e ***

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

Workaround gdbserver<7.7 for setfs

With current FSF GDB HEAD and old FSF gdbserver I expected I could do:
	gdb -ex 'file target:/root/redhat/threadit' -ex 'target remote :1234'
(supplying that unsupported qXfer:exec-file:read by "file")
But that does not work because:
	Sending packet: $vFile:setfs:0#bf...Packet received: OK
	Packet vFile:setfs (hostio-setfs) is supported
	...
	Sending packet: $vFile:setfs:104#24...Packet received: OK
	"target:/root/redhat/threadit": could not open as an executable file: Invalid argument

GDB documentation says:
	The valid responses to Host I/O packets are:
	An empty response indicates that this operation is not recognized.

This "empty response" vs. "OK" was a bug in gdbserver < 7.7.  It was fixed by:
	commit e7f0d979dd5cc4f8b658df892e93db69d6d660b7
	Author: Yao Qi <yao@codesourcery.com>
	Date:   Tue Dec 10 21:59:20 2013 +0800
	    Fix a bug in matching notifications.
	Message-ID: <1386684626-11415-1-git-send-email-yao@codesourcery.com>
	https://sourceware.org/ml/gdb-patches/2013-12/msg00373.html
	2013-12-10  Yao Qi  <yao@codesourcery.com>
		* notif.c (handle_notif_ack): Return 0 if no notification
		matches.

with unpatched old FSF gdbserver and patched FSF GDB HEAD:
	gdb -ex 'file target:/root/redhat/threadit' -ex 'target remote :1234'
	Sending packet: $vFile:setfs:0#bf...Packet received: OK
	Packet vFile:setfs (hostio-setfs) is NOT supported
	...
	(gdb) info sharedlibrary
	From                To                  Syms Read   Shared Object Library
	0x00007ffff7ddbae0  0x00007ffff7df627a  Yes (*)     target:/lib64/ld-linux-x86-64.so.2
	0x00007ffff7bc48a0  0x00007ffff7bcf514  Yes (*)     target:/lib64/libpthread.so.0

gdb/ChangeLog
2016-04-27  Jan Kratochvil  <jan.kratochvil@redhat.com>

	* remote.c (remote_start_remote): Detect PACKET_vFile_setfs.support.


^ permalink raw reply	[flat|nested] 31+ messages in thread
* [binutils-gdb/gdb-7.11-branch] Add regression test for PR gdb/19858 (JIT code registration on attach)
@ 2016-03-31 19:43 sergiodj+buildbot
  2016-04-01  8:47 ` Failures on Fedora-ppc64be-m64, branch gdb-7.11-branch sergiodj+buildbot
  0 siblings, 1 reply; 31+ messages in thread
From: sergiodj+buildbot @ 2016-03-31 19:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 85af34ee0211eedf8d30a5c44dfc59dddf8b512a ***

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

Add regression test for PR gdb/19858 (JIT code registration on attach)

This test would fail without the previous gdb/jit.c fix:

  (gdb) attach 23031
  Attaching to program: .../build/gdb/testsuite/outputs/gdb.base/jit/jit-main, process 23031
  [...]
  207           WAIT_FOR_GDB; i = 0;  /* gdb break here 1 */
  (gdb) PASS: gdb.base/jit.exp: attach: one_jit_test-2: attach
  set var wait_for_gdb = 0
  (gdb) PASS: gdb.base/jit.exp: attach: one_jit_test-2: set var wait_for_gdb = 0
  info function ^jit_function
  All functions matching regular expression "^jit_function":
  (gdb) FAIL: gdb.base/jit.exp: attach: one_jit_test-2: info function ^jit_function

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

	PR gdb/19858
	* gdb.base/jit-main.c: Include unistd.h.
	(ATTACH): Define to 0 if not already defined.
	(wait_for_gdb, mypid): New globals.
	(WAIT_FOR_GDB): New macro.
	(MAIN): Set an alarm.  Store the process's pid.  Wait for GDB at
	some breakpoint locations.
	* gdb.base/jit.exp (clean_reattach, continue_to_test_location):
	New procedures.
	(one_jit_test): Add REATTACH parameter, and handle it.  Use
	continue_to_test_location.
	(top level): Test attach, and adjusts calls to one_jit_test.


^ permalink raw reply	[flat|nested] 31+ messages in thread
* [binutils-gdb/gdb-7.11-branch] Set GDB version number to 7.11.
@ 2016-02-24 10:07 sergiodj+buildbot
  2016-02-24 11:10 ` Failures on Fedora-ppc64be-m64, branch gdb-7.11-branch sergiodj+buildbot
  0 siblings, 1 reply; 31+ messages in thread
From: sergiodj+buildbot @ 2016-02-24 10:07 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ac6c80b22321afd27328828f2e4a67220ffed2d5 ***

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

Set GDB version number to 7.11.

gdb/ChangeLog:

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


^ permalink raw reply	[flat|nested] 31+ messages in thread
* [binutils-gdb/gdb-7.11-branch] i386-biarch-core.exp: Use standard_output_file
@ 2016-02-15 16:29 sergiodj+buildbot
  2016-02-15 17:01 ` Failures on Fedora-ppc64be-m64, branch gdb-7.11-branch sergiodj+buildbot
  0 siblings, 1 reply; 31+ messages in thread
From: sergiodj+buildbot @ 2016-02-15 16:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2d059a33d890c017c8105b102a6b56ccbd6128b2 ***

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

i386-biarch-core.exp: Use standard_output_file

Fix the core file path to use the standard output directory.

gdb/testsuite/ChangeLog:

	* i386-biarch-core.exp: Define corefile using
	standard_output_file.


^ permalink raw reply	[flat|nested] 31+ messages in thread
* [binutils-gdb/gdb-7.11-branch] Bump GDB version number to 7.10.90.DATE-cvs.
@ 2016-02-10  4:32 sergiodj+buildbot
  2016-02-10 14:42 ` Failures on Fedora-ppc64be-m64, branch gdb-7.11-branch sergiodj+buildbot
  0 siblings, 1 reply; 31+ messages in thread
From: sergiodj+buildbot @ 2016-02-10  4:32 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 45e8913772c2db1235b3a0eb113d804cb254af13 ***

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

Bump GDB version number to 7.10.90.DATE-cvs.

gdb/ChangeLog:

	* version.in: Set GDB version number to 7.10.90.DATE-cvs.


^ permalink raw reply	[flat|nested] 31+ messages in thread
* [binutils-gdb/gdb-7.11-branch] Set development mode to "off" by default.
@ 2016-02-10  3:49 sergiodj+buildbot
  2016-02-10  8:04 ` Failures on Fedora-ppc64be-m64, branch gdb-7.11-branch sergiodj+buildbot
  0 siblings, 1 reply; 31+ messages in thread
From: sergiodj+buildbot @ 2016-02-10  3:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4ad0fc283ce48b60624007f81134704b6837152c ***

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

Set development mode to "off" by default.

bfd/ChangeLog:

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


^ permalink raw reply	[flat|nested] 31+ messages in thread
* [binutils-gdb/gdb-7.11-branch] Bump version to 7.10.90.DATE-git.
@ 2016-02-10  3:41 sergiodj+buildbot
  2016-02-10  6:46 ` Failures on Fedora-ppc64be-m64, branch gdb-7.11-branch sergiodj+buildbot
  0 siblings, 1 reply; 31+ messages in thread
From: sergiodj+buildbot @ 2016-02-10  3:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d5d168eef1464c735c5dba0cf76d638bd27970b9 ***

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

Bump version to 7.10.90.DATE-git.

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

gdb/ChangeLog:

	GDB 7.11 branch created (9ef9e6a6a0dd8f948708cb67c9afcfd0be40cb0a):
	* version.in: Bump version to 7.10.90.DATE-git.


^ permalink raw reply	[flat|nested] 31+ messages in thread
end of thread, other threads:[~2016-06-01  2:06 UTC | newest]

Thread overview: 31+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-05-03 11:46 [binutils-gdb/gdb-7.11-branch] Remove gdb/python/python.c code that handles strlen failing with -1 sergiodj+buildbot
2016-05-03 11:47 ` Failures on RHEL-s390x-m64, branch gdb-7.11-branch sergiodj+buildbot
2016-05-03 13:08 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot
2016-05-03 13:21 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-05-03 13:25 ` Failures on AIX-POWER7-plain, " sergiodj+buildbot
2016-05-03 13:32 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot
2016-05-03 13:40 ` Failures on Fedora-s390x-m64, " sergiodj+buildbot
2016-05-03 14:13 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot
2016-05-03 18:09 ` Failures on Debian-i686-native-extended-gdbserver, " sergiodj+buildbot
2016-05-03 19:09 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-05-03 19:32 ` Failures on Debian-x86_64-m64, " sergiodj+buildbot
2016-05-04  0:08 ` Failures on Fedora-ppc64be-m64, " sergiodj+buildbot
2016-05-04  0:28 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj+buildbot
2016-05-04  0:51 ` Failures on Fedora-ppc64be-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-05-04  1:23 ` Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot
2016-05-04  2:10 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-05-04  2:34 ` Failures on Fedora-ppc64le-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-05-04  3:11 ` Failures on Fedora-ppc64le-native-gdbserver-m64, " sergiodj+buildbot
  -- strict thread matches above, loose matches on Subject: below --
2016-06-01  1:18 [binutils-gdb/gdb-7.11-branch] Bump GDB version number to 7.11.1.DATE-git sergiodj+buildbot
2016-06-01  2:14 ` Failures on Fedora-ppc64be-m64, branch gdb-7.11-branch sergiodj+buildbot
2016-06-01  0:54 [binutils-gdb/gdb-7.11-branch] Set GDB version number to 7.11.1 sergiodj+buildbot
2016-06-01  1:08 ` Failures on Fedora-ppc64be-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-26 14:52 ` Failures on Fedora-ppc64be-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-19  4:07 ` Failures on Fedora-ppc64be-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-19  2:40 ` Failures on Fedora-ppc64be-m64, branch gdb-7.11-branch sergiodj+buildbot
2016-05-17 22:13 [binutils-gdb/gdb-7.11-branch] Fix -exec-run not running asynchronously with mi-async on (PR gdb/18077) sergiodj+buildbot
2016-05-18 14:57 ` Failures on Fedora-ppc64be-m64, branch gdb-7.11-branch sergiodj+buildbot
2016-04-27 19:52 [binutils-gdb/gdb-7.11-branch] Workaround gdbserver<7.7 for setfs sergiodj+buildbot
2016-04-28  0:40 ` Failures on Fedora-ppc64be-m64, branch gdb-7.11-branch sergiodj+buildbot
2016-03-31 19:43 [binutils-gdb/gdb-7.11-branch] Add regression test for PR gdb/19858 (JIT code registration on attach) sergiodj+buildbot
2016-04-01  8:47 ` Failures on Fedora-ppc64be-m64, branch gdb-7.11-branch sergiodj+buildbot
2016-02-24 10:07 [binutils-gdb/gdb-7.11-branch] Set GDB version number to 7.11 sergiodj+buildbot
2016-02-24 11:10 ` Failures on Fedora-ppc64be-m64, branch gdb-7.11-branch sergiodj+buildbot
2016-02-15 16:29 [binutils-gdb/gdb-7.11-branch] i386-biarch-core.exp: Use standard_output_file sergiodj+buildbot
2016-02-15 17:01 ` Failures on Fedora-ppc64be-m64, branch gdb-7.11-branch sergiodj+buildbot
2016-02-10  4:32 [binutils-gdb/gdb-7.11-branch] Bump GDB version number to 7.10.90.DATE-cvs sergiodj+buildbot
2016-02-10 14:42 ` Failures on Fedora-ppc64be-m64, branch gdb-7.11-branch sergiodj+buildbot
2016-02-10  3:49 [binutils-gdb/gdb-7.11-branch] Set development mode to "off" by default sergiodj+buildbot
2016-02-10  8:04 ` Failures on Fedora-ppc64be-m64, branch gdb-7.11-branch sergiodj+buildbot
2016-02-10  3:41 [binutils-gdb/gdb-7.11-branch] Bump version to 7.10.90.DATE-git sergiodj+buildbot
2016-02-10  6:46 ` Failures on Fedora-ppc64be-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).