public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
* [binutils-gdb/gdb-7.11-branch] Workaround gdbserver<7.7 for setfs
@ 2016-04-27 19:52 sergiodj+buildbot
  2016-04-27 19:52 ` Failures on RHEL-s390x-m64, branch gdb-7.11-branch sergiodj+buildbot
                   ` (16 more replies)
  0 siblings, 17 replies; 33+ 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] 33+ 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:56 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch gdb-7.11-branch sergiodj+buildbot
  0 siblings, 1 reply; 33+ 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] 33+ 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:52 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch gdb-7.11-branch sergiodj+buildbot
  0 siblings, 1 reply; 33+ 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] 33+ 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  7:25 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch gdb-7.11-branch sergiodj+buildbot
  0 siblings, 1 reply; 33+ 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] 33+ 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-19  1:45 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch gdb-7.11-branch sergiodj+buildbot
  0 siblings, 1 reply; 33+ 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] 33+ messages in thread
* [binutils-gdb/gdb-7.11-branch] Fix gdb/python/python.c use-after-free
@ 2016-05-03 11:55 sergiodj+buildbot
  2016-05-03 20:00 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch gdb-7.11-branch sergiodj+buildbot
  0 siblings, 1 reply; 33+ messages in thread
From: sergiodj+buildbot @ 2016-05-03 11:55 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 329dec6fc5f2efa83d626583135081b53abe8729 ***

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

Fix gdb/python/python.c use-after-free

Valgrind shows:

 ==26964== Invalid read of size 1
 ==26964==    at 0x6E14100: __GI_strcmp (strcmp.S:180)
 ==26964==    by 0x6DB55AA: setlocale (setlocale.c:238)
 ==26964==    by 0x4E0455: _initialize_python() (python.c:1731)
 ==26964==    by 0x786731: initialize_all_files() (init.c:319)
 ==26964==    by 0x72EF0A: gdb_init(char*) (top.c:1929)
 ==26964==    by 0x60BCAC: captured_main(void*) (main.c:863)
 ==26964==    by 0x606AD5: catch_errors(int (*)(void*), void*, char*, return_mask) (exceptions.c:234)
 ==26964==    by 0x60C608: gdb_main(captured_main_args*) (main.c:1165)
 ==26964==    by 0x40CAEC: main (gdb.c:32)
 ==26964==  Address 0x81d30a0 is 0 bytes inside a block of size 181 free'd
 ==26964==    at 0x4C29CF0: free (vg_replace_malloc.c:530)
 ==26964==    by 0x6DB5B65: setname (setlocale.c:201)
 ==26964==    by 0x6DB5B65: setlocale (setlocale.c:388)
 ==26964==    by 0x4E037F: _initialize_python() (python.c:1712)
 ==26964==    by 0x786731: initialize_all_files() (init.c:319)
 ==26964==    by 0x72EF0A: gdb_init(char*) (top.c:1929)
 ==26964==    by 0x60BCAC: captured_main(void*) (main.c:863)
 ==26964==    by 0x606AD5: catch_errors(int (*)(void*), void*, char*, return_mask) (exceptions.c:234)
 ==26964==    by 0x60C608: gdb_main(captured_main_args*) (main.c:1165)
 ==26964==    by 0x40CAEC: main (gdb.c:32)

The problem is doing this:

  oldloc = setlocale (LC_ALL, NULL);
  setlocale (LC_ALL, "");
  ...
  setlocale (LC_ALL, oldloc);

I.e., the second setlocale call frees 'oldloc'.

>From http://pubs.opengroup.org/onlinepubs/9699919799/functions/setlocale.html :

 "The returned string pointer might be invalidated or the string
 content might be overwritten by a subsequent call to setlocale()."

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

	PR python/20037
	* python/python.c (_initialize_python) [IS_PY3K]: xstrdup/xfree
	oldloc.


^ permalink raw reply	[flat|nested] 33+ 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-03 19:09 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch gdb-7.11-branch sergiodj+buildbot
  0 siblings, 1 reply; 33+ 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] 33+ messages in thread
* [binutils-gdb/gdb-7.11-branch] [gdb] Fix -Wparentheses warnings
@ 2016-05-03  9:05 sergiodj+buildbot
  2016-05-03 10:29 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch gdb-7.11-branch sergiodj+buildbot
  0 siblings, 1 reply; 33+ messages in thread
From: sergiodj+buildbot @ 2016-05-03  9:05 UTC (permalink / raw)
  To: gdb-testers

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

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

[gdb] Fix -Wparentheses warnings

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

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


^ permalink raw reply	[flat|nested] 33+ messages in thread
* [binutils-gdb/gdb-7.11-branch] btrace: fix PR gdb/19829
@ 2016-03-17 11:28 sergiodj+buildbot
  2016-03-18  9:26 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch gdb-7.11-branch sergiodj+buildbot
  0 siblings, 1 reply; 33+ 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] 33+ 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:43 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch gdb-7.11-branch sergiodj+buildbot
  0 siblings, 1 reply; 33+ 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] 33+ 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 11:42 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch gdb-7.11-branch sergiodj+buildbot
  0 siblings, 1 reply; 33+ 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] 33+ 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 10:42 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch gdb-7.11-branch sergiodj+buildbot
  0 siblings, 1 reply; 33+ 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] 33+ 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 12:27 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch gdb-7.11-branch sergiodj+buildbot
  0 siblings, 1 reply; 33+ 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] 33+ 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 16:54 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch gdb-7.11-branch sergiodj+buildbot
  0 siblings, 1 reply; 33+ 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] 33+ 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 22:54 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch gdb-7.11-branch sergiodj+buildbot
  0 siblings, 1 reply; 33+ 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] 33+ 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 20:48 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch gdb-7.11-branch sergiodj+buildbot
  0 siblings, 1 reply; 33+ 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] 33+ messages in thread
end of thread, other threads:[~2016-06-01  2:48 UTC | newest]

Thread overview: 33+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-04-27 19:52 [binutils-gdb/gdb-7.11-branch] Workaround gdbserver<7.7 for setfs sergiodj+buildbot
2016-04-27 19:52 ` Failures on RHEL-s390x-m64, branch gdb-7.11-branch sergiodj+buildbot
2016-04-27 20:09 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot
2016-04-27 20:09 ` Failures on Fedora-i686, " sergiodj+buildbot
2016-04-27 20:15 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot
2016-04-27 20:22 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot
2016-04-27 20:24 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-04-27 20:30 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot
2016-04-27 20:36 ` Failures on AIX-POWER7-plain, " sergiodj+buildbot
2016-04-27 20:42 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-04-27 21:17 ` Failures on Debian-i686-native-extended-gdbserver, " sergiodj+buildbot
2016-04-27 21:23 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot
2016-04-27 21:28 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-04-28  0:40 ` Failures on Fedora-ppc64be-m64, " sergiodj+buildbot
2016-04-28  1:00 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj+buildbot
2016-04-28  1:21 ` Failures on Fedora-ppc64be-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-04-28  2:57 ` Failures on Fedora-ppc64le-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-04-28  3:14 ` 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:56 ` Failures on Debian-x86_64-native-extended-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:52 ` Failures on Debian-x86_64-native-extended-gdbserver-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  7:25 ` Failures on Debian-x86_64-native-extended-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-19  1:45 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch gdb-7.11-branch sergiodj+buildbot
2016-05-03 11:55 [binutils-gdb/gdb-7.11-branch] Fix gdb/python/python.c use-after-free sergiodj+buildbot
2016-05-03 20:00 ` Failures on Debian-x86_64-native-extended-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-03 19:09 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch gdb-7.11-branch sergiodj+buildbot
2016-05-03  9:05 [binutils-gdb/gdb-7.11-branch] [gdb] Fix -Wparentheses warnings sergiodj+buildbot
2016-05-03 10:29 ` Failures on Debian-x86_64-native-extended-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  9:26 ` Failures on Debian-x86_64-native-extended-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:43 ` Failures on Debian-x86_64-native-extended-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 11:42 ` Failures on Debian-x86_64-native-extended-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-16 10:42 ` Failures on Debian-x86_64-native-extended-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 12:27 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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 16:54 ` Failures on Debian-x86_64-native-extended-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 22:54 ` Failures on Debian-x86_64-native-extended-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 20:48 ` Failures on Debian-x86_64-native-extended-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).