public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
* [binutils-gdb/gdb-7.11-branch] Set GDB version number to 7.10.90.
@ 2016-02-10  4:23 sergiodj+buildbot
  2016-02-10  4:24 ` Failures on RHEL-s390x-m64, branch gdb-7.11-branch sergiodj+buildbot
                   ` (16 more replies)
  0 siblings, 17 replies; 44+ 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] 44+ 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:29 ` Failures on Fedora-ppc64be-native-gdbserver-m64, branch gdb-7.11-branch sergiodj+buildbot
  0 siblings, 1 reply; 44+ 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] 44+ 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:21 ` Failures on Fedora-ppc64be-native-gdbserver-m64, branch gdb-7.11-branch sergiodj+buildbot
  0 siblings, 1 reply; 44+ 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] 44+ 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 15:35 ` Failures on Fedora-ppc64be-native-gdbserver-m64, branch gdb-7.11-branch sergiodj+buildbot
  0 siblings, 1 reply; 44+ 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] 44+ 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  3:01 ` Failures on Fedora-ppc64be-native-gdbserver-m64, branch gdb-7.11-branch sergiodj+buildbot
  0 siblings, 1 reply; 44+ 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] 44+ 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 15:18 ` Failures on Fedora-ppc64be-native-gdbserver-m64, branch gdb-7.11-branch sergiodj+buildbot
  0 siblings, 1 reply; 44+ 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] 44+ messages in thread
* [binutils-gdb/gdb-7.11-branch] Use target_terminal_ours_for_output in MI
@ 2016-05-16 21:17 sergiodj+buildbot
  2016-05-16 22:08 ` Failures on Fedora-ppc64be-native-gdbserver-m64, branch gdb-7.11-branch sergiodj+buildbot
  0 siblings, 1 reply; 44+ messages in thread
From: sergiodj+buildbot @ 2016-05-16 21:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7f8e34d8604098e221f342cf162898fb25499900 ***

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

Use target_terminal_ours_for_output in MI

The MI code only does output, so leave raw/cooked mode alone, as well
as the SIGINT handler.  Restore terminal settings after output, while
at it.  Also, a couple events missed calling target_terminal_ours
before output, even.

[Backported to the 7.11 branch by Simon Marchi, as it fixes PR 20039.]

gdb/ChangeLog:
YYYY-MM-DD  Pedro Alves  <palves@redhat.com>

	* mi/mi-interp.c (mi_new_thread): Put
	target_terminal_ours_for_output in effect while outputting.
	(mi_thread_exit): Use target_terminal_ours_for_output instead of
	target_terminal_ours.
	(mi_record_changed, mi_inferior_added, mi_inferior_appeared)
	(mi_inferior_exit, mi_inferior_removed, mi_traceframe_changed)
	(mi_tsv_created, mi_tsv_deleted, mi_tsv_modified)
	(mi_breakpoint_created, mi_breakpoint_deleted)
	(mi_breakpoint_modified, mi_solib_loaded, mi_solib_unloaded)
	(mi_command_param_changed, mi_memory_changed)
	(report_initial_inferior): Use target_terminal_ours_for_output
	instead of target_terminal_ours.  Restore terminal settings.
	* mi/mi-main.c (mi_execute_command): Use
	target_terminal_ours_for_output instead of target_terminal_ours.
	Restore terminal settings.


^ permalink raw reply	[flat|nested] 44+ messages in thread
* [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-04  0:28 ` Failures on Fedora-ppc64be-native-gdbserver-m64, branch gdb-7.11-branch sergiodj+buildbot
  0 siblings, 1 reply; 44+ 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] 44+ 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  1:00 ` Failures on Fedora-ppc64be-native-gdbserver-m64, branch gdb-7.11-branch sergiodj+buildbot
  0 siblings, 1 reply; 44+ 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] 44+ messages in thread
* [binutils-gdb/gdb-7.11-branch] MIPS/Linux: Also recognize TRAP_BRKPT and TRAP_HWBKPT
@ 2016-04-16  0:19 sergiodj+buildbot
  2016-04-16  3:14 ` Failures on Fedora-ppc64be-native-gdbserver-m64, branch gdb-7.11-branch sergiodj+buildbot
  0 siblings, 1 reply; 44+ messages in thread
From: sergiodj+buildbot @ 2016-04-16  0:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT da611eed9a74de742e9436b6fdd92041b6e9bbf1 ***

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

MIPS/Linux: Also recognize TRAP_BRKPT and TRAP_HWBKPT

This makes the MIPS Linux backends recognize TRAP_BRKPT and
TRAP_HWBKPT in siginfo.si_code in addition to SI_KERNEL, since Linux
4.6 now reports the finer-grained si_code values too.

Refs:
 https://sourceware.org/ml/gdb-patches/2016-02/msg00756.html
 https://sourceware.org/ml/gdb-patches/2016-04/msg00090.html

On kernels that report SI_KERNEL (<= 4.5), we'll enter the "ambiguous"
path of save_stop_reason:

	  if (GDB_ARCH_IS_TRAP_BRKPT (siginfo.si_code)
	      && GDB_ARCH_IS_TRAP_HWBKPT (siginfo.si_code))
	    {
	      /* The si_code is ambiguous on this arch -- check debug
		 registers.  */
	      if (!check_stopped_by_watchpoint (lp))
		lp->stop_reason = TARGET_STOPPED_BY_SW_BREAKPOINT;
	    }

while on kernels that report the finer-grained si_code values (>= 4.6),
we'll enter the corresponding branches:

	  else if (GDB_ARCH_IS_TRAP_BRKPT (siginfo.si_code))
	    {
	    }
	  else if (GDB_ARCH_IS_TRAP_HWBKPT (siginfo.si_code))
	    {
	      ...

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

	* nat/linux-ptrace.h [__mips__] (GDB_ARCH_IS_TRAP_BRKPT): Also
	accept TRAP_BRKPT.
	 [__mips__] (GDB_ARCH_IS_TRAP_HWBKPT): Also accept TRAP_HWBKPT.


^ permalink raw reply	[flat|nested] 44+ messages in thread
* [binutils-gdb/gdb-7.11-branch] Fix PR remote/19840: gdb crashes on reverse-stepi
@ 2016-04-13 13:51 sergiodj+buildbot
  2016-04-14 17:29 ` Failures on Fedora-ppc64be-native-gdbserver-m64, branch gdb-7.11-branch sergiodj+buildbot
  0 siblings, 1 reply; 44+ messages in thread
From: sergiodj+buildbot @ 2016-04-13 13:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6b9ef0d488c556339aea7b095ef7a9b6bf6b1af1 ***

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

Fix PR remote/19840: gdb crashes on reverse-stepi

Reverse debugging against a remote target that does reverse debugging
itself (with the bs/bc packets) always trips on:

 (gdb) target remote localhost:...
 (gdb) reverse-stepi
 ../../gdb/target.c:602: internal-error: default_execution_direction: to_execution_direction must be implemented for reverse async

I missed adding a to_execution_direction method to remote.c in commit
3223143295b5 (Adds target_execution_direction to make record targets
support async mode), GDB 7.4 time.  Later, GDB 7.8 switched to
target-async on by default, making the regression user-visible by
default too.

Fix is simply to add the missing to_execution_direction implementation
to target remote.

Tested by Andi Kleen against Simics.

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

	PR remote/19840
	* remote.c (struct remote_state) <last_resume_exec_dir>: New
	field.
	(new_remote_state): Default last_resume_exec_dir to EXEC_FORWARD.
	(remote_open_1): Reset last_resume_exec_dir to EXEC_FORWARD.
	(remote_resume): Store the last execution direction.
	(remote_execution_direction): New function.
	(init_remote_ops): Install it as to_execution_direction target_ops
	method.


^ permalink raw reply	[flat|nested] 44+ 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  9:06 ` Failures on Fedora-ppc64be-native-gdbserver-m64, branch gdb-7.11-branch sergiodj+buildbot
  0 siblings, 1 reply; 44+ 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] 44+ messages in thread
* [binutils-gdb/gdb-7.11-branch] Fix PR gdb/19858: GDB doesn't register the JIT libraries on attach
@ 2016-03-31 19:23 sergiodj+buildbot
  2016-04-01  6:27 ` Failures on Fedora-ppc64be-native-gdbserver-m64, branch gdb-7.11-branch sergiodj+buildbot
  0 siblings, 1 reply; 44+ messages in thread
From: sergiodj+buildbot @ 2016-03-31 19:23 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cd64cabb8c66a5565fc33bf66a07c08bc767e413 ***

Author: Yichao Yu <yyc1992@gmail.com>
Branch: gdb-7.11-branch
Commit: cd64cabb8c66a5565fc33bf66a07c08bc767e413

Fix PR gdb/19858: GDB doesn't register the JIT libraries on attach

Ref: https://sourceware.org/ml/gdb/2016-03/msg00023.html

GDB currently fails to fetch the list of already-registered JIT
modules on attach.

Nothing is calling jit_inferior_init, which is what is responsible for
walking the JIT object list at init time.

Despite the misleading naming, jit_inferior_created_hook ->
jit_inferior_init is only called when the inferior execs.

This regressed with the fix for PR gdb/13431 (03bef283c2d3):
 https://sourceware.org/ml/gdb-patches/2012-02/msg00023.html which
removed the inferior_created (jit_inferior_created_observer)
observer.

Adding an inferior_created observer back fixes the issue.

In turn, this exposes a bug in jit_breakpoint_re_set_internal as well,
which is returning the wrong result when we already have the
breakpoint at the right address.

gdb/ChangeLog:
2016-03-31  Yichao Yu  <yyc1992@gmail.com>

	PR gdb/19858
	* jit.c (jit_breakpoint_re_set_internal): Return 0 if we already
	got the breakpoint at the right address.
	(jit_inferior_created): New function.
	(_initialize_jit): Install jit_inferior_created as
	inferior_created observer.

Signed-off-by: Pedro Alves <palves@redhat.com>


^ permalink raw reply	[flat|nested] 44+ messages in thread
* [binutils-gdb/gdb-7.11-branch] btrace: fix PR gdb/19829
@ 2016-03-17 11:28 sergiodj+buildbot
  2016-03-18  5:14 ` Failures on Fedora-ppc64be-native-gdbserver-m64, branch gdb-7.11-branch sergiodj+buildbot
  0 siblings, 1 reply; 44+ 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] 44+ messages in thread
* [binutils-gdb/gdb-7.11-branch] Fix PR gdb/19676: Internal error in linux-thread.db.c if /proc not mounted
@ 2016-03-15 17:34 sergiodj+buildbot
  2016-03-15 21:42 ` Failures on Fedora-ppc64be-native-gdbserver-m64, branch gdb-7.11-branch sergiodj+buildbot
  0 siblings, 1 reply; 44+ messages in thread
From: sergiodj+buildbot @ 2016-03-15 17:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9312893c8d63934f7855451c6a78503e69a47453 ***

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

Fix PR gdb/19676: Internal error in linux-thread.db.c if /proc not mounted

If /proc is not mounted, GDB fails an assertion in find_new_threads_once:

 Continuing.
 .../src/gdb/linux-thread-db.c:1249: internal-error: find_new_threads_once: Assertion `!target_has_execution' failed.
 A problem internal to GDB has been detected,
 further debugging may prove unreliable.
 Quit this debugging session? (y or n)

That was supposed to catch misuses of td_ta_thr_iter, which is unsafe
for live debugging.  However, if /proc is not mounted, we still
fallback to using it.

I didn't bother with a warning, because GDB already prints several
others related to failing to open /proc files.

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

	PR gdb/19676
	* linux-thread-db.c (try_thread_db_load_1): Leave
	info->td_ta_thr_iter_p NULL iff debugging a live process and we
	have /proc access.
	(find_new_threads_once): Assert that we have a non-NULL
	info->td_ta_thr_iter_p instead of checking whether the target has
	execution.


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

*** TEST RESULTS FOR COMMIT 63a034c19fa2a0c09aeb1ae3575daa57edf19d0c ***

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

Bump GDB version number to 7.11.0.DATE-git.

gdb/ChangeLog:

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


^ permalink raw reply	[flat|nested] 44+ 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:29 ` Failures on Fedora-ppc64be-native-gdbserver-m64, branch gdb-7.11-branch sergiodj+buildbot
  0 siblings, 1 reply; 44+ 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] 44+ messages in thread
* [binutils-gdb/gdb-7.11-branch] gdb-gdb.py: SyntaxError: Missing parentheses in call to 'print'
@ 2016-02-22 16:28 sergiodj+buildbot
  2016-02-22 17:22 ` Failures on Fedora-ppc64be-native-gdbserver-m64, branch gdb-7.11-branch sergiodj+buildbot
  0 siblings, 1 reply; 44+ messages in thread
From: sergiodj+buildbot @ 2016-02-22 16:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3d58f8997229b9045899dd306a47a3c27d03a9fd ***

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

gdb-gdb.py: SyntaxError: Missing parentheses in call to 'print'

After building GDB
	--with-python=/usr/bin/python3
and for example stripping ./gdb and running:
	./gdb -data-directory data-directory/ -iex "add-auto-load-safe-path $PWD/gdb-gdb.gdb" -iex "add-auto-load-safe-path $PWD/gdb-gdb.
py" ./gdb
I get:
	Make breakpoint pending on future shared library load? (y or [n]) [answered N; input not from terminal]
	  File "/home/jkratoch/redhat/gdb-test-python3/gdb/gdb-gdb.py", line 91
	    print "Warning: Cannot find enum type_flag_value type."
								  ^
	SyntaxError: Missing parentheses in call to 'print'
	(top-gdb) q

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

	* gdb-gdb.py (class TypeFlagsPrinter): Use parentheses for print.


^ permalink raw reply	[flat|nested] 44+ 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 23:05 ` Failures on Fedora-ppc64be-native-gdbserver-m64, branch gdb-7.11-branch sergiodj+buildbot
  0 siblings, 1 reply; 44+ 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] 44+ messages in thread
* [binutils-gdb/gdb-7.11-branch] Fix more testcases with standard_output_file.
@ 2016-02-15 18:07 sergiodj+buildbot
  2016-02-15 20:27 ` Failures on Fedora-ppc64be-native-gdbserver-m64, branch gdb-7.11-branch sergiodj+buildbot
  0 siblings, 1 reply; 44+ messages in thread
From: sergiodj+buildbot @ 2016-02-15 18:07 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8b6bd5aca63189590498195a7a2696cde021c9cd ***

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

Fix more testcases with standard_output_file.

Since
	commit 2151ccc56c74b55a8f0debf0724a495368f92591
	Author: Simon Marchi <simon.marchi@ericsson.com>
	Date:   Mon Feb 8 14:02:36 2016 -0500
	    Always organize test artifacts in a directory hierarchy
these testfiles could not build.

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

	* gdb.arch/i386-gnu-cfi.exp: Use standard_output_file.
	* gdb.arch/i386-prologue.exp: Likewise.
	* gdb.arch/i386-size.exp: Likewise.


^ permalink raw reply	[flat|nested] 44+ 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:19 ` Failures on Fedora-ppc64be-native-gdbserver-m64, branch gdb-7.11-branch sergiodj+buildbot
  0 siblings, 1 reply; 44+ 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] 44+ messages in thread
* [binutils-gdb/gdb-7.11-branch] testsuite: Fix false Fortran regressions with recent gcc
@ 2016-02-14  8:52 sergiodj+buildbot
  2016-02-14 13:16 ` Failures on Fedora-ppc64be-native-gdbserver-m64, branch gdb-7.11-branch sergiodj+buildbot
  0 siblings, 1 reply; 44+ 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] 44+ messages in thread
* [binutils-gdb/gdb-7.11-branch] testsuite regression: gdb.fortran/vla-value-sub.exp gdb.fortran/vla-value-sub-finish.exp
@ 2016-02-14  8:35 sergiodj+buildbot
  2016-02-14 10:37 ` Failures on Fedora-ppc64be-native-gdbserver-m64, branch gdb-7.11-branch sergiodj+buildbot
  0 siblings, 1 reply; 44+ messages in thread
From: sergiodj+buildbot @ 2016-02-14  8:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 307c2facb242da4fc557baea06e63d8e8a621142 ***

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

testsuite regression: gdb.fortran/vla-value-sub.exp gdb.fortran/vla-value-sub-finish.exp

> +static int max_value_size = 65536; /* 64k bytes */

FAIL: gdb.fortran/vla-value-sub.exp: print array2 in foo after it was filled (passed fixed array)
FAIL: gdb.fortran/vla-value-sub.exp: print array2 in foo after it was mofified in debugger (passed fixed array)
FAIL: gdb.fortran/vla-value-sub-finish.exp: print array2 in foo after it was filled
FAIL: gdb.fortran/vla-value-sub-finish.exp: print array2 in foo after it was mofified in debugger

print array2
value requires 296352 bytes, which is more than max-value-size
(gdb) FAIL: gdb.fortran/vla-value-sub.exp: print array2 in foo after it was filled (passed fixed array)

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

	* gdb.fortran/vla-value-sub-finish.exp (set max-value-size 1024*1024):
	New test.
	* gdb.fortran/vla-value-sub.exp: Likewise.


^ permalink raw reply	[flat|nested] 44+ 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 16:19 ` Failures on Fedora-ppc64be-native-gdbserver-m64, branch gdb-7.11-branch sergiodj+buildbot
  0 siblings, 1 reply; 44+ 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] 44+ 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 15:00 ` Failures on Fedora-ppc64be-native-gdbserver-m64, branch gdb-7.11-branch sergiodj+buildbot
  0 siblings, 1 reply; 44+ 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] 44+ messages in thread
* [binutils-gdb/gdb-7.11-branch] gdb/NEWS: Change "since GDB 7.10" -> "in GDB 7.11".
@ 2016-02-10  4:15 sergiodj+buildbot
  2016-02-10 12:21 ` Failures on Fedora-ppc64be-native-gdbserver-m64, branch gdb-7.11-branch sergiodj+buildbot
  0 siblings, 1 reply; 44+ messages in thread
From: sergiodj+buildbot @ 2016-02-10  4:15 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4fd877f0a54fbdfc28680aa24f3133f14648ee10 ***

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

gdb/NEWS: Change "since GDB 7.10" -> "in GDB 7.11".

gdb/ChangeLog:

        * NEWS: Change "Changes since GDB version 7.10" into "Changes
        in GDB version 7.11".


^ permalink raw reply	[flat|nested] 44+ 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  7:04 ` Failures on Fedora-ppc64be-native-gdbserver-m64, branch gdb-7.11-branch sergiodj+buildbot
  0 siblings, 1 reply; 44+ 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] 44+ messages in thread
end of thread, other threads:[~2016-06-01  2:19 UTC | newest]

Thread overview: 44+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-02-10  4:23 [binutils-gdb/gdb-7.11-branch] Set GDB version number to 7.10.90 sergiodj+buildbot
2016-02-10  4:24 ` Failures on RHEL-s390x-m64, branch gdb-7.11-branch sergiodj+buildbot
2016-02-10  5:41 ` Failures on Fedora-i686, " sergiodj+buildbot
2016-02-10  5:52 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot
2016-02-10  6:07 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot
2016-02-10  7:36 ` Failures on Fedora-s390x-m64, " sergiodj+buildbot
2016-02-10  8:13 ` Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot
2016-02-10  8:22 ` Failures on Debian-s390x-m64, " sergiodj+buildbot
2016-02-10  9:00 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-02-10  9:09 ` Failures on AIX-POWER7-plain, " sergiodj+buildbot
2016-02-10 13:33 ` Failures on Debian-i686, " sergiodj+buildbot
2016-02-10 13:39 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj+buildbot
2016-02-10 13:54 ` Failures on Debian-i686-native-gdbserver, " sergiodj+buildbot
2016-02-10 14:00 ` Failures on Fedora-ppc64be-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-02-10 20:13 ` Failures on Debian-x86_64-native-gdbserver-m64, " sergiodj+buildbot
2016-02-10 20:49 ` Failures on Fedora-ppc64le-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-02-10 21:49 ` Failures on Fedora-ppc64le-cc-with-index, " sergiodj+buildbot
2016-02-10 22:38 ` Failures on Fedora-ppc64le-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:29 ` Failures on Fedora-ppc64be-native-gdbserver-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:21 ` Failures on Fedora-ppc64be-native-gdbserver-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 15:35 ` Failures on Fedora-ppc64be-native-gdbserver-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  3:01 ` Failures on Fedora-ppc64be-native-gdbserver-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 15:18 ` Failures on Fedora-ppc64be-native-gdbserver-m64, branch gdb-7.11-branch sergiodj+buildbot
2016-05-16 21:17 [binutils-gdb/gdb-7.11-branch] Use target_terminal_ours_for_output in MI sergiodj+buildbot
2016-05-16 22:08 ` Failures on Fedora-ppc64be-native-gdbserver-m64, branch gdb-7.11-branch sergiodj+buildbot
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-04  0:28 ` Failures on Fedora-ppc64be-native-gdbserver-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  1:00 ` Failures on Fedora-ppc64be-native-gdbserver-m64, branch gdb-7.11-branch sergiodj+buildbot
2016-04-16  0:19 [binutils-gdb/gdb-7.11-branch] MIPS/Linux: Also recognize TRAP_BRKPT and TRAP_HWBKPT sergiodj+buildbot
2016-04-16  3:14 ` Failures on Fedora-ppc64be-native-gdbserver-m64, branch gdb-7.11-branch sergiodj+buildbot
2016-04-13 13:51 [binutils-gdb/gdb-7.11-branch] Fix PR remote/19840: gdb crashes on reverse-stepi sergiodj+buildbot
2016-04-14 17:29 ` Failures on Fedora-ppc64be-native-gdbserver-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  9:06 ` Failures on Fedora-ppc64be-native-gdbserver-m64, branch gdb-7.11-branch sergiodj+buildbot
2016-03-31 19:23 [binutils-gdb/gdb-7.11-branch] Fix PR gdb/19858: GDB doesn't register the JIT libraries on attach sergiodj+buildbot
2016-04-01  6:27 ` Failures on Fedora-ppc64be-native-gdbserver-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  5:14 ` Failures on Fedora-ppc64be-native-gdbserver-m64, branch gdb-7.11-branch sergiodj+buildbot
2016-03-15 17:34 [binutils-gdb/gdb-7.11-branch] Fix PR gdb/19676: Internal error in linux-thread.db.c if /proc not mounted sergiodj+buildbot
2016-03-15 21:42 ` Failures on Fedora-ppc64be-native-gdbserver-m64, branch gdb-7.11-branch sergiodj+buildbot
2016-02-24 10:31 [binutils-gdb/gdb-7.11-branch] Bump GDB version number to 7.11.0.DATE-git sergiodj+buildbot
2016-02-24 12:53 ` Failures on Fedora-ppc64be-native-gdbserver-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:29 ` Failures on Fedora-ppc64be-native-gdbserver-m64, branch gdb-7.11-branch sergiodj+buildbot
2016-02-22 16:28 [binutils-gdb/gdb-7.11-branch] gdb-gdb.py: SyntaxError: Missing parentheses in call to 'print' sergiodj+buildbot
2016-02-22 17:22 ` Failures on Fedora-ppc64be-native-gdbserver-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 23:05 ` Failures on Fedora-ppc64be-native-gdbserver-m64, branch gdb-7.11-branch sergiodj+buildbot
2016-02-15 18:07 [binutils-gdb/gdb-7.11-branch] Fix more testcases with standard_output_file sergiodj+buildbot
2016-02-15 20:27 ` Failures on Fedora-ppc64be-native-gdbserver-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:19 ` Failures on Fedora-ppc64be-native-gdbserver-m64, branch gdb-7.11-branch sergiodj+buildbot
2016-02-14  8:52 [binutils-gdb/gdb-7.11-branch] testsuite: Fix false Fortran regressions with recent gcc sergiodj+buildbot
2016-02-14 13:16 ` Failures on Fedora-ppc64be-native-gdbserver-m64, branch gdb-7.11-branch sergiodj+buildbot
2016-02-14  8:35 [binutils-gdb/gdb-7.11-branch] testsuite regression: gdb.fortran/vla-value-sub.exp gdb.fortran/vla-value-sub-finish.exp sergiodj+buildbot
2016-02-14 10:37 ` Failures on Fedora-ppc64be-native-gdbserver-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 16:19 ` Failures on Fedora-ppc64be-native-gdbserver-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 15:00 ` Failures on Fedora-ppc64be-native-gdbserver-m64, branch gdb-7.11-branch sergiodj+buildbot
2016-02-10  4:15 [binutils-gdb/gdb-7.11-branch] gdb/NEWS: Change "since GDB 7.10" -> "in GDB 7.11" sergiodj+buildbot
2016-02-10 12:21 ` Failures on Fedora-ppc64be-native-gdbserver-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  7:04 ` Failures on Fedora-ppc64be-native-gdbserver-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).