public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
* [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 10:31 ` Failures on RHEL-s390x-m64, branch gdb-7.11-branch sergiodj+buildbot
                   ` (18 more replies)
  0 siblings, 19 replies; 35+ 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] 35+ messages in thread
* [binutils-gdb/gdb-7.11-branch] btrace: fix PR gdb/19829
@ 2016-03-17 11:28 sergiodj+buildbot
  2016-03-18  6:55 ` Failures on Debian-i686-native-gdbserver, branch gdb-7.11-branch sergiodj+buildbot
  0 siblings, 1 reply; 35+ 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] 35+ 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:05 ` Failures on Debian-i686-native-gdbserver, branch gdb-7.11-branch sergiodj+buildbot
  0 siblings, 1 reply; 35+ 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] 35+ messages in thread
* [binutils-gdb/gdb-7.11-branch] Fix PR gdb/19676: Disable displaced stepping if /proc not mounted
@ 2016-03-15 17:24 sergiodj+buildbot
  2016-03-15 19:49 ` Failures on Debian-i686-native-gdbserver, branch gdb-7.11-branch sergiodj+buildbot
  0 siblings, 1 reply; 35+ messages in thread
From: sergiodj+buildbot @ 2016-03-15 17:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4e57eb7028442f0e771c815d755b64daf7394e68 ***

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

Fix PR gdb/19676: Disable displaced stepping if /proc not mounted

On GNU/Linux archs that support displaced stepping, if /proc is not
mounted, GDB gets stuck not able to step past breakpoints:

 (gdb) c
 Continuing.
 dl_main (phdr=<optimized out>, phnum=<optimized out>, user_entry=<optimized out>, auxv=<optimized out>) at rtld.c:2163
 2163      LIBC_PROBE (init_complete, 2, LM_ID_BASE, r);
 Cannot find AT_ENTRY auxiliary vector entry.
 (gdb) c
 Continuing.
 dl_main (phdr=<optimized out>, phnum=<optimized out>, user_entry=<optimized out>, auxv=<optimized out>) at rtld.c:2163
 2163      LIBC_PROBE (init_complete, 2, LM_ID_BASE, r);
 Cannot find AT_ENTRY auxiliary vector entry.
 (gdb)

That's because GDB can't figure out where the scratch pad is.

This is a regression introduced by the earlier changes to make the
Linux native target always work in non-stop mode.

This commit makes GDB detect the case and fallback to stepping over
breakpoints in-line.

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

	PR gdb/19676
	* infrun.c (displaced_step_prepare): Also disable displaced
	stepping on NOT_SUPPORTED_ERROR.
	* linux-tdep.c (linux_displaced_step_location): If reading auxv
	fails, throw NOT_SUPPORTED_ERROR instead of generic error.


^ permalink raw reply	[flat|nested] 35+ messages in thread
* [binutils-gdb/gdb-7.11-branch] PR remote/19496, internal err forking-threads-plus-bkpt
@ 2016-02-16 17:31 sergiodj+buildbot
  2016-02-16 22:41 ` Failures on Debian-i686-native-gdbserver, branch gdb-7.11-branch sergiodj+buildbot
  0 siblings, 1 reply; 35+ messages in thread
From: sergiodj+buildbot @ 2016-02-16 17:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e993d610a980ea8df9200f158bfae69308c2138d ***

Author: Don Breazeal <donb@codesourcery.com>
Branch: gdb-7.11-branch
Commit: e993d610a980ea8df9200f158bfae69308c2138d

PR remote/19496, internal err forking-threads-plus-bkpt

This patch fixes an internal error that occurs in
gdb.threads/forking-threads-plus-breakpoint.exp:

/blah/binutils-gdb/gdb/target.c:2723: internal-error: Can't determine the
current address space of thread Thread 3170.3170

In default_thread_address_space, find_inferior_ptid couldn't find 3170.3170
because it had been overwritten in inferior_appeared, called as follows:

inferior_appeared
  remote_add_inferior
    remote_notice_new_inferior
      remote_update_thread_list

The cause of the problem was the following sequence of events:

* GDB knows only about the main thread

* the first fork event is reported to GDB, saved as pending_event

* qXfer:threads:read gets the threads from the remote.
  remove_new_fork_children id's the fork child from the pending event
  and removes it from the list reported to GDB.  All the rest of the
  threads, including the fork parent, are added to the GDB thread list.

* GDB stops all the threads.  All the stop events are pushed onto the
  stop reply queue behind the pending fork event.  The fork waitstatus
  is saved in the fork parent thread's pending status field
  thread_info.suspend.

* remote_wait_ns calls queued_stop_reply and process_stop_reply to
  remove the fork event from the front of the stop reply queue and save
  event information in the thread_info structure for the fork parent
  thread.  Unfortunately, none of the information saved in this way is
  the fork-specific information.

* A subsequent qXfer:threads:read packet gets the thread list including
  the fork parent and fork child.  remove_new_fork_children checks the
  thread list to see if there is a fork parent, doesn't find one, checks
  the stop reply queue for a pending fork event, doesn't find one, and
  allows the fork child thread to be reported to GDB before the fork
  event has been handled.  remote_update_thread_list calls
  remote_notice_new_thread and overwrites the current (main) thread in
  inferior_appeared.

So the fork event has been reported out of target_wait but it was left
pending on the infrun side (infrun.c:save_waitstatus).  IOW, the fork
event hasn't been processed by handle_inferior_event yet, so it hasn't
made it to tp->pending_follow yet.

The fix is to check thread_info.suspend along with the
thread_info.pending_follow in remote.c:remove_new_fork_children, to
prevent premature reporting of the fork child thread creation.

gdb/ChangeLog:

	PR remote/19496
	* remote.c (remove_new_fork_children): Check for pending
	fork status in thread_info.suspend.

gdb/testsuite/ChangeLog:

	PR remote/19496
	* gdb.threads/forking-threads-plus-breakpoint.exp (do_test):
	Remove kfail for PR remote/19496.


^ permalink raw reply	[flat|nested] 35+ messages in thread
* [binutils-gdb/gdb-7.11-branch] Fix cleanup in arm_linux_software_single_step
@ 2016-02-16 14:55 sergiodj+buildbot
  2016-02-16 18:01 ` Failures on Debian-i686-native-gdbserver, branch gdb-7.11-branch sergiodj+buildbot
  0 siblings, 1 reply; 35+ messages in thread
From: sergiodj+buildbot @ 2016-02-16 14:55 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 523f1dab16b5c8706bbb81c6fdbac741b3fffb19 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: gdb-7.11-branch
Commit: 523f1dab16b5c8706bbb81c6fdbac741b3fffb19

Fix cleanup in arm_linux_software_single_step

I see the following error in testing aarch64 GDB debugging arm
program.

(gdb) PASS: gdb.reverse/readv-reverse.exp: set breakpoint at marker2
continue
Continuing.
=================================================================
==32273==ERROR: AddressSanitizer: attempting free on address which was not malloc()-ed: 0x000000ce4c00 in thread T0
    #0 0x2ba5615645c7 in __interceptor_free (/usr/lib/x86_64-linux-gnu/libasan.so.1+0x545c7)^M
    #1 0x4be8b5 in VEC_CORE_ADDR_cleanup /home/yao/SourceCode/gnu/gdb/git/gdb/common/gdb_vecs.h:34^M
    #2 0x5e6d95 in do_my_cleanups /home/yao/SourceCode/gnu/gdb/git/gdb/common/cleanups.c:154^M
    #3 0x64c99a in fetch_inferior_event /home/yao/SourceCode/gnu/gdb/git/gdb/infrun.c:3975^M
    #4 0x678437 in inferior_event_handler /home/yao/SourceCode/gnu/gdb/git/gdb/inf-loop.c:44^M
    #5 0x5078f6 in remote_async_serial_handler /home/yao/SourceCode/gnu/gdb/git/gdb/remote.c:13223^M
    #6 0x4cecfd in run_async_handler_and_reschedule /home/yao/SourceCode/gnu/gdb/git/gdb/ser-base.c:137^M
    #7 0x676864 in gdb_wait_for_event /home/yao/SourceCode/gnu/gdb/git/gdb/event-loop.c:834^M
    #8 0x676a27 in gdb_do_one_event /home/yao/SourceCode/gnu/gdb/git/gdb/event-loop.c:323^M
    #9 0x676aed in start_event_loop /home/yao/SourceCode/gnu/gdb/git/gdb/event-loop.c:347^M
    #10 0x6706d2 in captured_command_loop /home/yao/SourceCode/gnu/gdb/git/gdb/main.c:318^M
    #11 0x66db8c in catch_errors /home/yao/SourceCode/gnu/gdb/git/gdb/exceptions.c:240^M
    #12 0x6716dd in captured_main /home/yao/SourceCode/gnu/gdb/git/gdb/main.c:1157^M
    #13 0x66db8c in catch_errors /home/yao/SourceCode/gnu/gdb/git/gdb/exceptions.c:240^M
    #14 0x671b7a in gdb_main /home/yao/SourceCode/gnu/gdb/git/gdb/main.c:1165^M
    #15 0x467684 in main /home/yao/SourceCode/gnu/gdb/git/gdb/gdb.c:32^M
    #16 0x2ba563ed7ec4 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21ec4)^M
    #17 0x4676b2 (/scratch/yao/gdb/build-git/aarch64-linux-gnu/gdb/gdb+0x4676b2)

looks we should discard cleanup if function
arm_linux_software_single_step returns early, or create cleanup when
it is needed.

gdb:

2016-02-16  Yao Qi  <yao.qi@linaro.org>

	* arm-linux-tdep.c (arm_linux_software_single_step): Assign
	'old_chain' later.


^ permalink raw reply	[flat|nested] 35+ 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-16 11:08 ` Failures on Debian-i686-native-gdbserver, branch gdb-7.11-branch sergiodj+buildbot
  0 siblings, 1 reply; 35+ 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] 35+ 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-16  8:45 ` Failures on Debian-i686-native-gdbserver, branch gdb-7.11-branch sergiodj+buildbot
  0 siblings, 1 reply; 35+ 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] 35+ 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:09 ` Failures on Debian-i686-native-gdbserver, branch gdb-7.11-branch sergiodj+buildbot
  0 siblings, 1 reply; 35+ 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] 35+ messages in thread
* [binutils-gdb/gdb-7.11-branch] Clear *VAL in regcache_raw_read_unsigned
@ 2016-02-10 16:55 sergiodj+buildbot
  2016-02-11  1:25 ` Failures on Debian-i686-native-gdbserver, branch gdb-7.11-branch sergiodj+buildbot
  0 siblings, 1 reply; 35+ messages in thread
From: sergiodj+buildbot @ 2016-02-10 16:55 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 83d9e733abe9cc0553f899064a955a6255550ade ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: gdb-7.11-branch
Commit: 83d9e733abe9cc0553f899064a955a6255550ade

Clear *VAL in regcache_raw_read_unsigned

We have function regcache_raw_read_unsigned defined in both GDB and
GDBserver, so that it is used in common like this,

  ULONGEST value;
  status = regcache_raw_read_unsigned (regcache, regnum, &value);

'value' is correctly set in GDB side, but may not be correctly set
in GDBserver, because &value is passed in regcache_raw_read_unsigned
but collect_register may only set part of the whole variable.  In my
test, I see the top half of 'value' is garbage.  This patch fixes this
problem by clearing *VAL before calling collect_register.

gdb/gdbserver:

2016-02-10  Yao Qi  <yao.qi@linaro.org>

	* regcache.c (regcache_raw_read_unsigned): Clear *VAL.


^ permalink raw reply	[flat|nested] 35+ 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:10 ` Failures on Debian-i686-native-gdbserver, branch gdb-7.11-branch sergiodj+buildbot
  0 siblings, 1 reply; 35+ 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] 35+ 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:02 ` Failures on Debian-i686-native-gdbserver, branch gdb-7.11-branch sergiodj+buildbot
  0 siblings, 1 reply; 35+ 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] 35+ 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 13:54 ` Failures on Debian-i686-native-gdbserver, branch gdb-7.11-branch sergiodj+buildbot
  0 siblings, 1 reply; 35+ 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] 35+ 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:47 ` Failures on Debian-i686-native-gdbserver, branch gdb-7.11-branch sergiodj+buildbot
  0 siblings, 1 reply; 35+ 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] 35+ 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  9:04 ` Failures on Debian-i686-native-gdbserver, branch gdb-7.11-branch sergiodj+buildbot
  0 siblings, 1 reply; 35+ 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] 35+ 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:24 ` Failures on Debian-i686-native-gdbserver, branch gdb-7.11-branch sergiodj+buildbot
  0 siblings, 1 reply; 35+ 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] 35+ messages in thread
end of thread, other threads:[~2016-03-18  6:48 UTC | newest]

Thread overview: 35+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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 10:31 ` Failures on RHEL-s390x-m64, branch gdb-7.11-branch sergiodj+buildbot
2016-02-24 10:32 ` Failures on Fedora-i686, " sergiodj+buildbot
2016-02-24 10:38 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot
2016-02-24 10:54 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot
2016-02-24 11:02 ` Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot
2016-02-24 11:06 ` Failures on AIX-POWER7-plain, " sergiodj+buildbot
2016-02-24 11:24 ` Failures on Fedora-s390x-m64, " sergiodj+buildbot
2016-02-24 11:28 ` Failures on Debian-i686, " sergiodj+buildbot
2016-02-24 11:42 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-02-24 11:49 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-02-24 11:50 ` Failures on Debian-i686-native-gdbserver, " sergiodj+buildbot
2016-02-24 12:16 ` Failures on Fedora-ppc64be-cc-with-index, " sergiodj+buildbot
2016-02-24 12:23 ` Failures on Debian-i686-native-extended-gdbserver, " sergiodj+buildbot
2016-02-24 12:25 ` Failures on Fedora-ppc64le-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-02-24 12:29 ` Failures on Debian-x86_64-native-gdbserver-m64, " sergiodj+buildbot
2016-02-24 12:43 ` Failures on Fedora-ppc64le-cc-with-index, " sergiodj+buildbot
2016-02-24 12:53 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj+buildbot
2016-02-24 13:16 ` Failures on Fedora-ppc64be-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-02-24 13:24 ` Failures on Fedora-ppc64le-m64, " sergiodj+buildbot
  -- strict thread matches above, loose matches on Subject: below --
2016-03-17 11:28 [binutils-gdb/gdb-7.11-branch] btrace: fix PR gdb/19829 sergiodj+buildbot
2016-03-18  6:55 ` Failures on Debian-i686-native-gdbserver, 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:05 ` Failures on Debian-i686-native-gdbserver, branch gdb-7.11-branch sergiodj+buildbot
2016-03-15 17:24 [binutils-gdb/gdb-7.11-branch] Fix PR gdb/19676: Disable displaced stepping if /proc not mounted sergiodj+buildbot
2016-03-15 19:49 ` Failures on Debian-i686-native-gdbserver, branch gdb-7.11-branch sergiodj+buildbot
2016-02-16 17:31 [binutils-gdb/gdb-7.11-branch] PR remote/19496, internal err forking-threads-plus-bkpt sergiodj+buildbot
2016-02-16 22:41 ` Failures on Debian-i686-native-gdbserver, branch gdb-7.11-branch sergiodj+buildbot
2016-02-16 14:55 [binutils-gdb/gdb-7.11-branch] Fix cleanup in arm_linux_software_single_step sergiodj+buildbot
2016-02-16 18:01 ` Failures on Debian-i686-native-gdbserver, 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-16 11:08 ` Failures on Debian-i686-native-gdbserver, 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-16  8:45 ` Failures on Debian-i686-native-gdbserver, 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:09 ` Failures on Debian-i686-native-gdbserver, branch gdb-7.11-branch sergiodj+buildbot
2016-02-10 16:55 [binutils-gdb/gdb-7.11-branch] Clear *VAL in regcache_raw_read_unsigned sergiodj+buildbot
2016-02-11  1:25 ` Failures on Debian-i686-native-gdbserver, 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:10 ` Failures on Debian-i686-native-gdbserver, 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:02 ` Failures on Debian-i686-native-gdbserver, 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 13:54 ` Failures on Debian-i686-native-gdbserver, 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:47 ` Failures on Debian-i686-native-gdbserver, 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  9:04 ` Failures on Debian-i686-native-gdbserver, 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:24 ` Failures on Debian-i686-native-gdbserver, 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).