public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
* [binutils-gdb] gdb/18947: [aarch64]Step into shared library is very slow.
@ 2015-09-11 14:43 sergiodj+buildbot
  2015-09-11 15:59 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-09-11 14:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6dcaef99fab7e59e3eeb16a95d4c29b7b499b408 ***

Author: Mihail-Marian Nistor <mihail.nistor@freescale.com>
Branch: master
Commit: 6dcaef99fab7e59e3eeb16a95d4c29b7b499b408

gdb/18947: [aarch64]Step into shared library is very slow.

Install gdbarch_skip_solib_resolver on aarch64 GNU/Linux

gdb/ChangeLog:

2015-09-11  Mihail-Marian Nistor  <mihail.nistor@freescale.com>

	PR gdb/18947
	* aarch64-linux-tdep.c: (aarch64_linux_init_abi): Install
	glibc_skip_solib_resolver as gdbarch_skip_solib_resolver callback.

Signed-off-by: Mihail-Marian Nistor <mihail.nistor@freescale.com>


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [AArch64] Fix incorrect mask when decoding b.cond instruction
@ 2015-09-11 16:06 sergiodj+buildbot
  2015-09-11 17:38 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-09-11 16:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4d50586db70d366d7d9eaf42062bf23bb6073695 ***

Author: Pierre Langlois <pierre.langlois@arm.com>
Branch: master
Commit: 4d50586db70d366d7d9eaf42062bf23bb6073695

[AArch64] Fix incorrect mask when decoding b.cond instruction

The encoding of the b.cond instruction is described in the architecture
reference manual as:

b.cond  0101 0100 iiii iiii iiii iiii iii0 cccc

So the mask should be 0xff000010.

gdb/ChangeLog:

	* aarch64-tdep.c (decode_bcond): Fix incorrect mask.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [AArch64] Cleanup comments in instruction decoding functions
@ 2015-09-11 16:41 sergiodj+buildbot
  2015-09-11 18:59 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-09-11 16:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 669e74e8295e8aef1dc052f30ff30bad624eb0f6 ***

Author: Pierre Langlois <pierre.langlois@arm.com>
Branch: master
Commit: 669e74e8295e8aef1dc052f30ff30bad624eb0f6

[AArch64] Cleanup comments in instruction decoding functions

gdb/ChangeLog:

	* aarch64-tdep.c (decode_cb): Move up comment describing the
	encoding.
	(decode_tb): Fix a typo in comment above the function.  Move up
	comment describing the encoding.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Extended-remote follow-exec
@ 2015-09-11 18:33 sergiodj+buildbot
  2015-09-11 21:19 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-09-11 18:33 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 94585166dfea8232c248044f9f4b1c217dc4ac2e ***

Author: Don Breazeal <donb@codesourcery.com>
Branch: master
Commit: 94585166dfea8232c248044f9f4b1c217dc4ac2e

Extended-remote follow-exec

This patch implements support for exec events on extended-remote Linux
targets.  Follow-exec-mode and rerun behave as expected.  Catchpoints and
test updates are implemented in subsequent patches.

This patch was derived from a patch posted last October:
https://sourceware.org/ml/gdb-patches/2014-10/msg00877.html.
It was originally based on some work done by Luis Machado in 2013.

IMPLEMENTATION
----------------
Exec events are enabled via ptrace options.

When an exec event is detected by gdbserver, the existing process
data, along with all its associated lwp and thread data, is deleted
and replaced by data for a new single-threaded process.  The new
process data is initialized with the appropriate parts of the state
of the execing process.  This approach takes care of several potential
pitfalls, including:

 * deleting the data for an execing non-leader thread before any
   wait/sigsuspend occurs
 * correctly initializing the architecture of the execed process

We then report the exec event using a new RSP stop reason, "exec".

When GDB receives an "exec" event, it saves the status in the event
structure's target_waitstatus field, like what is done for remote fork
events.  Because the original and execed programs may have different
architectures, we skip parsing the section of the stop reply packet
that contains register data.  The register data will be retrieved
later after the inferior's architecture has been set up by
infrun.c:follow_exec.

At that point the exec event is handled by the existing event handling
in GDB.  However, a few changes were necessary so that
infrun.c:follow_exec could accommodate the remote target.

 * Where follow-exec-mode "new" is handled, we now call
   add_inferior_with_spaces instead of add_inferior with separate calls
   to set up the program and address spaces.  The motivation for this
   is that add_inferior_with_spaces also sets up the initial architecture
   for the inferior, which is needed later by target_find_description
   when it calls target_gdbarch.

 * We call a new target function, target_follow_exec.  This function
   allows us to store the execd_pathname in the inferior, instead of
   using the static string remote_exec_file from remote.c.  The static
   string didn't work for follow-exec-mode "new", since once you switched
   to the execed program, the original remote exec-file was lost.  The
   execd_pathname is now stored in the inferior's program space as a
   REGISTRY field.  All of the requisite mechanisms for this are
   defined in remote.c.

gdb/gdbserver/ChangeLog:

	* linux-low.c (linux_mourn): Static declaration.
	(linux_arch_setup): Move in front of
	handle_extended_wait.
	(linux_arch_setup_thread): New function.
	(handle_extended_wait): Handle exec events.  Call
	linux_arch_setup_thread.  Make event_lwp argument a
	pointer-to-a-pointer.
	(check_zombie_leaders): Do not check stopped threads.
	(linux_low_ptrace_options): Add PTRACE_O_TRACEEXEC.
	(linux_low_filter_event): Add lwp and thread for exec'ing
	non-leader thread if leader thread has been deleted.
	Refactor code into linux_arch_setup_thread and call it.
	Pass child lwp pointer by reference to handle_extended_wait.
	(linux_wait_for_event_filtered): Update comment.
	(linux_wait_1): Prevent clobbering exec event status.
	(linux_supports_exec_events): New function.
	(linux_target_ops) <supports_exec_events>: Initialize new member.
	* lynx-low.c (lynx_target_ops) <supports_exec_events>: Initialize
	new member.
	* remote-utils.c (prepare_resume_reply): New stop reason 'exec'.
	* server.c (report_exec_events): New global variable.
	(handle_query): Handle qSupported query for exec-events feature.
	(captured_main): Initialize report_exec_events.
	* server.h (report_exec_events): Declare new global variable.
	* target.h (struct target_ops) <supports_exec_events>: New
	member.
	(target_supports_exec_events): New macro.
	* win32-low.c (win32_target_ops) <supports_exec_events>:
	Initialize new member.

gdb/ChangeLog:

	* infrun.c (follow_exec): Use process-style ptid for
	exec message.  Call add_inferior_with_spaces and
	target_follow_exec.
	* nat/linux-ptrace.c (linux_supports_traceexec): New function.
	* nat/linux-ptrace.h (linux_supports_traceexec): Declare.
	* remote.c (remote_pspace_data): New static variable.
	(remote_pspace_data_cleanup): New function.
	(get_remote_exec_file): New function.
	(set_remote_exec_file_1): New function.
	(set_remote_exec_file): New function.
	(show_remote_exec_file): New function.
	(remote_exec_file): Delete static variable.
	(anonymous enum) <PACKET_exec_event_feature> New
	enumeration constant.
	(remote_protocol_features): Add entry for exec-events feature.
	(remote_query_supported): Add client side of qSupported query
	for exec-events feature.
	(remote_follow_exec): New function.
	(remote_parse_stop_reply): Handle 'exec' stop reason.
	(extended_remote_run, extended_remote_create_inferior): Call
	get_remote_exec_file and set_remote_exec_file_1.
	(init_extended_remote_ops) <to_follow_exec>: Initialize new
	member.
	(_initialize_remote): Call
	register_program_space_data_with_cleanup.  Call
	add_packet_config_cmd for remote exec-events feature.
	Modify call to add_setshow_string_noescape_cmd for exec-file
	to use new functions set_remote_exec_file and
	show_remote_exec_file.
	* target-debug.h, target-delegates.c: Regenerated.
	* target.c (target_follow_exec): New function.
	* target.h (struct target_ops) <to_follow_exec>: New member.
	(target_follow_exec): Declare new function.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Extended-remote catch exec
@ 2015-09-11 18:42 sergiodj+buildbot
  2015-09-11 23:29 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-09-11 18:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d46addbb52a1f6d970bcac583b0b00ff4326e116 ***

Author: Don Breazeal <donb@codesourcery.com>
Branch: master
Commit: d46addbb52a1f6d970bcac583b0b00ff4326e116

Extended-remote catch exec

This patch implements exec catchpoints for extended-remote Linux
targets.  The implementation follows the same approach used for
fork catchpoints, implementing extended-remote target routines for
inserting and removing the catchpoints by just checking if exec events
are supported.  Existing host-side code and previous support for
extended-remote exec events takes care of the rest.

gdb/ChangeLog:

	* remote.c (remote_exec_event_p): New function.
	(remote_insert_exec_catchpoint): New function.
	(remote_remove_exec_catchpoint): New function.
	(init_extended_remote_ops): Initialize extended_remote_ops
	members to_insert_exec_catchpoint and
	to_remove_exec_catchpoint.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Extended-remote exec test
@ 2015-09-11 18:47 sergiodj+buildbot
  2015-09-12  1:16 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-09-11 18:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2fd33e94480fc2c662d1ad28f83e522cc5dbdc2e ***

Author: Don Breazeal <donb@codesourcery.com>
Branch: master
Commit: 2fd33e94480fc2c662d1ad28f83e522cc5dbdc2e

Extended-remote exec test

This patch updates several exec-related tests and some of the library
functions in order to get them running with extended-remote.  There were
three changes that were required, as follows:

In gdb.base/foll-exec.exp, use 'clean_start' in place of proc 'zap_session'
to reset the state of the debugger between tests.  This sets 'remote
exec-file' to execute the correct binary file in each subsequent test.

In gdb.base/pie-execl.exp, there is an expect statement with an expression
that is used to match output from both gdb and the program under debug.
For the remote target, this had to be split into two expressions, using
$inferior_spawn_id to match the output from the program.

Because I had encountered problems with extended-remote exec events in
non-stop mode in my manual testing, I added non-stop testing to the
non-ldr-exc-[1234].exp tests.  In order to set non-stop mode for remote
targets, it is necessary to 'set non-stop on' after gdb has started, but
before it connects to gdbserver.  This is done using 'save_vars' to set
non-stop mode in GDBFLAGS, so GDB sets non-stop mode on startup.

gdb/testsuite/ChangeLog:

	* gdb.base/foll-exec.c: Add copyright header.  Fix
	formatting issues.
	* gdb.base/foll-exec.exp (zap_session): Delete proc.
	(do_exec_tests): Use clean_restart in place of zap_session,
	and for test initialization.  Fix formatting issues.  Use
	fail in place of perror.
	* gdb.base/pie-execl.exp (main): Use 'inferior_spawn_id' in
	an expect statement to match an expression with output from
	the program under debug.
	* gdb.threads/non-ldr-exc-1.exp (do_test, main): Add
	non-stop tests and pass stop mode argument to clean_restart.
	Use save_vars to enable non-stop in GDBFLAGS.
	* gdb.threads/non-ldr-exc-2.exp: Likewise.
	* gdb.threads/non-ldr-exc-3.exp: Likewise.
	* gdb.threads/non-ldr-exc-4.exp: Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Extended-remote exec documentation
@ 2015-09-11 19:53 sergiodj+buildbot
  2015-09-12  6:55 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-09-11 19:53 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b459a59be3a9b92a27b71790f5e3f3be38595cb3 ***

Author: Don Breazeal <donb@codesourcery.com>
Branch: master
Commit: b459a59be3a9b92a27b71790f5e3f3be38595cb3

Extended-remote exec documentation

This patch adds documentation of support for exec events on
extended-remote Linux targets.

gdb/ChangeLog:

	* NEWS: Announce new remote packets for the exec-events
	feature and the exec-events feature and associated commands.

gdb/doc/ChangeLog:

	* gdb.texinfo (Remote Configuration): Add exec event
	feature to table of packet settings.
	(Stop Reply Packets): Add exec events to the list of stop
	reasons.
	(General Query Packets): Add exec events to tables of
	'gdbfeatures' and 'stub features' supported in the qSupported
	packet, as well as to the list containing stub feature
	details.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Set .plt entry size to 0 in elf32-hppa.c
@ 2015-09-12 17:42 sergiodj+buildbot
  2015-09-14 10:44 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-09-12 17:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f3c3938c1c1a57f78e1be9d2dbb9ea0cda12edf6 ***

Author: John David Anglin <danglin@gcc.gnu.org>
Branch: master
Commit: f3c3938c1c1a57f78e1be9d2dbb9ea0cda12edf6

Set .plt entry size to 0 in elf32-hppa.c


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] btrace, test: remove buffer-size test with unlimited buffer size
@ 2015-09-14 12:50 sergiodj+buildbot
  2015-09-14 14:36 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-09-14 12:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 157280a4d6b8c49703c698bda5546d7b2cc21e35 ***

Author: Markus Metzger <markus.t.metzger@intel.com>
Branch: master
Commit: 157280a4d6b8c49703c698bda5546d7b2cc21e35

btrace, test: remove buffer-size test with unlimited buffer size

The gdb.btrace/buffer-size.exp test starts recording with an unlimited
buffer size.  This will, for a short time, use up most if not all BTS
resources.

I don' think this test is necessary.  Remove it.

testsuite/
	* gdb.btrace/buffer-size.exp: Remove recording with unlimited BTS
	buffer size test.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [Ada] Fix the evaluation of access to packed array subscript
@ 2015-09-14 15:05 sergiodj+buildbot
  2015-09-14 18:42 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-09-14 15:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 919e6dbe9b61a27e8f7f89121ba182907df461a3 ***

Author: Pierre-Marie de Rodat <derodat@adacore.com>
Branch: master
Commit: 919e6dbe9b61a27e8f7f89121ba182907df461a3

[Ada] Fix the evaluation of access to packed array subscript

This change is relevant only for standard DWARF (as opposed to the GNAT
encodings extensions): at the time of writing it only makes a difference
with GCC patches that are to be integrated: see in particular
<https://gcc.gnu.org/ml/gcc-patches/2015-07/msg01364.html>.

Given the following Ada declarations:

    type Small is mod 2 ** 6;
    type Array_Type is array (0 .. 9) of Small
       with Pack;
    type Array_Access is access all Array_Type;

    A  : aliased Array_Type := (1, 2, 3, 4, 5, 6, 7, 8, 9, 10);
    AA : constant Array_Type := A'Access;

Before this change, we would get the following GDB session:

    (gdb) print aa.all(2)
    $1 = 3
    (gdb) print aa(2)
    $2 = 16

This is wrong: both expression should yield the same value: 3.  The
problem is simply that the routine which handles accesses to arrays lack
general handling for packed arrays.  After this patch, we have the
expected output:

    (gdb) print aa.all(2)
    $1 = 3
    (gdb) print aa(2)
    $2 = 3

gdb/ChangeLog:

	* ada-lang.c (ada_value_ptr_subscript): Update the heading
	comment.  Handle packed arrays.

gdb/testsuite/ChangeLog:

	* gdb.ada/access_to_packed_array.exp: New testcase.
	* gdb.ada/access_to_packed_array/foo.adb: New file.
	* gdb.ada/access_to_packed_array/pack.adb: New file.
	* gdb.ada/access_to_packed_array/pack.ads: New file.

Tested on x86_64-linux, no regression.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Bail out of processing stop if hook-stop resumes target / changes context
@ 2015-09-14 15:40 sergiodj+buildbot
  2015-09-15  0:53 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-09-14 15:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4c2f2a792a5971fcc7fe6511725eaf50d19d302b ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 4c2f2a792a5971fcc7fe6511725eaf50d19d302b

Bail out of processing stop if hook-stop resumes target / changes context

This patch, relative to a tree with
https://sourceware.org/ml/gdb-patches/2015-08/msg00295.html, fixes
issues/crashes that trigger if something unexpected happens during a
hook-stop.

E.g., if the inferior disappears while running the hook-stop, we hit
failed assertions:

 (gdb) define hook-stop
 Type commands for definition of "hook-stop".
 End with a line saying just "end".
 >kill
 >end
 (gdb) si
 Kill the program being debugged? (y or n) [answered Y; input not from terminal]
 /home/pedro/gdb/mygit/build/../src/gdb/thread.c:88: internal-error: inferior_thread: Assertion `tp' failed.
 A problem internal to GDB has been detected,
 further debugging may prove unreliable.
 Quit this debugging session? (y or n)

I noticed that if a hook-stop issues a synchronous execution command,
we print the same stop event twice:

 (gdb) define hook-stop
 Type commands for definition of "hook-stop".
 End with a line saying just "end".
 >si
 >end
 (gdb) si
 0x000000000040074a      42          args[i] = 1; /* Init value.  */  <<<<<<< once
 0x000000000040074a      42          args[i] = 1; /* Init value.  */  <<<<<<< twice
 (gdb)

In MI:

 *stopped,reason="end-stepping-range",frame={addr="0x000000000040074a",func="main",args=[],file="threads.c",fullname="/home/pedro/gdb/tests/threads.c",line="42"},thread-id="1",stopped-threads="all",core="0"
 *stopped,reason="end-stepping-range",frame={addr="0x000000000040074a",func="main",args=[],file="threads.c",fullname="/home/pedro/gdb/tests/threads.c",line="42"},thread-id="1",stopped-threads="all",core="0"
 (gdb)

The fix has GDB stop processing the event if the context changed.  I
don't expect people to be doing crazy things from the hook-stop.
E.g., it gives me headaches to try to come up a proper behavior for
handling a thread change from a hook-stop... (E.g., imagine the
hook-stop does thread N; step, with scheduler-locing on).  I think the
most important bit here is preventing crashes.

The patch adds a new hook-stop.exp test that covers the above and also
merges in the old hook-stop-continue.exp and hook-stop-frame.exp into
the same framework.

gdb/ChangeLog:
2015-09-14  Pedro Alves  <palves@redhat.com>

	* infrun.c (current_stop_id): New global.
	(get_stop_id, new_stop_id): New functions.
	(fetch_inferior_event): Handle normal_stop proceeding the target.
	(struct stop_context): New.
	(save_stop_context, release_stop_context_cleanup)
	(stop_context_changed): New functions.
	(normal_stop): Return true if the hook-stop changes the stop
	context.
	* infrun.h (get_stop_id): Declare.
	(normal_stop): Now returns int.  Add documentation.

gdb/testsuite/ChangeLog:
2015-09-14  Pedro Alves  <palves@redhat.com>

	* gdb.base/hook-stop-continue.c: Delete.
	* gdb.base/hook-stop-continue.exp: Delete.
	* gdb.base/hook-stop-frame.c: Delete.
	* gdb.base/hook-stop-frame.exp: Delete.
	* gdb.base/hook-stop.c: New file.
	* gdb.base/hook-stop.exp: New file.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix the SH behavior for EF_SH_PIC flag in FDPIC ABI
@ 2015-09-15  9:41 sergiodj+buildbot
  2015-09-15 10:01 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-09-15  9:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fbedb42d07cdc97a5bc698d1f7732ee776763cbc ***

Author: Rich Felker <dalias@libc.org>
Branch: master
Commit: fbedb42d07cdc97a5bc698d1f7732ee776763cbc

Fix the SH behavior for EF_SH_PIC flag in FDPIC ABI

Fix it so that it's compatible with the kernel and other FDPIC targets.

* elf32-sh.c (sh_elf_relocate_section): Set EF_SH_PIC flag
instead of clearing it on cross-section relocations.
(sh_elf_merge_private_data): Clear EF_SH_PIC flag by default.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] aarch64 multi-arch support (part 2): siginfo fixup
@ 2015-09-15 10:25 sergiodj+buildbot
  2015-09-15 13:27 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-09-15 10:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ade90bdeb78ccaeb294e34af04751f2f649a324f ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: ade90bdeb78ccaeb294e34af04751f2f649a324f

aarch64 multi-arch support (part 2): siginfo fixup

This patch is to fixup the siginfo_t when aarch64 gdb or gdbserver
read from or write to the arm inferior.  It is to convert the
"struct siginfo_t" between aarch64 and arm, which is quite mechanical.

gdb/gdbserver:

2015-09-15  Yao Qi  <yao.qi@linaro.org>

	* linux-aarch64-low.c (aarch64_linux_siginfo_fixup): New
	function.
	(struct linux_target_ops the_low_target): Install
	aarch64_linux_siginfo_fixup.

gdb:

2015-09-15  Yao Qi  <yao.qi@linaro.org>

	* aarch64-linux-nat.c (aarch64_linux_siginfo_fixup): New function.
	(_initialize_aarch64_linux_nat): Call linux_nat_set_siginfo_fixup.
	* nat/aarch64-linux.c (aarch64_compat_siginfo_from_siginfo):
	New function.
	(aarch64_siginfo_from_compat_siginfo): New function.
	* nat/aarch64-linux.h: Include signal.h.
	(compat_int_t, compat_uptr_t, compat_time_t): Typedef.
	(compat_timer_t, compat_clock_t): Likewise.
	(struct compat_timeval): New.
	(union compat_sigval): New.
	(struct compat_siginfo): New.
	(cpt_si_pid, cpt_si_uid, cpt_si_timerid): New macros.
	(cpt_si_overrun, cpt_si_status, cpt_si_utime): Likewise.
	(cpt_si_stime, cpt_si_ptr, cpt_si_addr): Likewise.
	(cpt_si_band, cpt_si_fd): Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [gdbserver] Rename supports_conditional_breakpoints to supports_hardware_single_step
@ 2015-09-15 13:45 sergiodj+buildbot
  2015-09-15 15:42 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-09-15 13:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 70b90b91bf77e72a36abdef039234359195b1942 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 70b90b91bf77e72a36abdef039234359195b1942

[gdbserver] Rename supports_conditional_breakpoints to supports_hardware_single_step

In my patch https://sourceware.org/ml/gdb-patches/2015-04/msg01110.html
a new target_ops hook supports_conditional_breakpoints was added to
disable conditional breakpoints if target doesn't have hardware single
step.  This patch is to generalize this hook from
supports_conditional_breakpoints to supports_hardware_single_step,
so that the following patch can use it.

gdb/gdbserver:

2015-09-15  Yao Qi  <yao.qi@linaro.org>

	* linux-low.c (linux_supports_conditional_breakpoints): Rename
	it to ...
	(linux_supports_hardware_single_step): ... New function.
	(linux_target_ops): Update.
	* lynx-low.c (lynx_target_ops): Set field
	supports_hardware_single_step to target_can_do_hardware_single_step.
	* nto-low.c (nto_target_ops): Likewise.
	* spu-low.c (spu_target_ops): Likewise.
	* win32-low.c (win32_target_ops): Likewise.
	* target.c (target_can_do_hardware_single_step): New function.
	* target.h (struct target_ops) <supports_conditional_breakpoints>:
	Remove.  <supports_hardware_single_step>: New field.
	(target_supports_conditional_breakpoints): Remove.
	(target_supports_hardware_single_step): New macro.
	(target_can_do_hardware_single_step): Declare.
	* server.c (handle_query): Use target_supports_hardware_single_step
	instead of target_supports_conditional_breakpoints.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Support single step by arch or target
@ 2015-09-15 14:02 sergiodj+buildbot
  2015-09-15 16:55 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-09-15 14:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 750ce8d1caf237464dd663de54ad055c0e58409d ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 750ce8d1caf237464dd663de54ad055c0e58409d

Support single step by arch or target

Nowadays, GDB only knows whether architecture supports hardware single
step or software single step (through gdbarch hook software_single_step),
and for a given instruction or instruction sequence, GDB knows how to
do single step (hardware or software).  However, GDB doesn't know whether
the target supports hardware single step.  It is possible that the
architecture doesn't support hardware single step, such as arm, but
the target supports, such as simulator.  This was discussed in this
thread https://www.sourceware.org/ml/gdb/2009-12/msg00033.html before.

I encounter this problem for aarch64 multi-arch support.  When aarch64
debugs arm program, gdbarch is arm, so software single step is still
used.  However, the underneath linux kernel does support hardware
single step, so IWBN to use it.

This patch is to add a new target_ops hook to_can_do_single_step, and
only use it in arm_linux_software_single_step to decide whether or not
to use hardware single step.  On the native aarch64 linux target, 1 is
returned.  On other targets, -1 is returned.  On the remote target, if
the target supports s and S actions in the vCont? reply, then target
can do single step.  However,  old GDBserver will send s and S in the
reply to vCont?, which will confuse new GDB.  For example, old GDBserver
on arm-linux will send s and S in the reply to vCont?, but it doesn't
support hardware single step.  On the other hand, new GDBserver, on
arm-linux for example, will not send s and S in the reply to vCont?,
but old GDB thinks it doesn't support vCont packet at all.  In order
to address this problem, I add a new qSupported feature vContSupported,
which indicates GDB wants to know the supported actions in the reply
to vCont?, and qSupported response contains vContSupported if the
stub is able tell supported vCont actions in the reply of vCont?.

If the patched GDB talks with patched GDBserver on x86, the RSP traffic
is like this:

 -> $qSupported:...+;vContSupported+
 <- ...+;vContSupported+
 ...
 -> $vCont?
 <- vCont;c;C;t;s;S;r

then, GDB knows the stub can do single step, and may stop using software
single step even the architecture doesn't support hardware single step.

If the patched GDB talks with patched GDBserver on arm, the last vCont?
reply will become:

 <- vCont;c;C;t

GDB thinks the target doesn't support single step, so it will use software
single step.

If the patched GDB talks with unpatched GDBserver, the RSP traffic is like
this:

 -> $qSupported:...+;vContSupported+
 <- ...+
 ...
 -> $vCont?
 <- vCont;c;C;t;s;S;r

although GDBserver returns s and S, GDB still thinks GDBserver may not
support single step because it doesn't support vContSupported.

If the unpatched GDB talks with patched GDBserver on x86, the RSP traffic
is like:

 -> $qSupported:...+;
 <- ...+;vContSupported+
 ...
 -> $vCont?
 <- vCont;c;C;t;s;S;r

Since GDB doesn't sent vContSupported in the qSupported feature, GDBserver
sends s and S regardless of the support of hardware single step.

gdb:

2015-09-15  Yao Qi  <yao.qi@linaro.org>

	* aarch64-linux-nat.c (aarch64_linux_can_do_single_step): New
	function.
	(_initialize_aarch64_linux_nat): Install it to to_can_do_single_step.
	* arm-linux-tdep.c (arm_linux_software_single_step): Return 0
	if target_can_do_single_step returns 1.
	* remote.c (struct vCont_action_support) <s, S>: New fields.
	(PACKET_vContSupported): New enum.
	(remote_protocol_features): New element for vContSupported.
	(remote_query_supported): Append "vContSupported+".
	(remote_vcont_probe): Remove support_s and support_S, use
	rs->supports_vCont.s and rs->supports_vCont.S instead.  Disable
	vCont packet if c and C actions are not supported.
	(remote_can_do_single_step): New function.
	(init_remote_ops): Install it to to_can_do_single_step.
	(_initialize_remote): Call add_packet_config_cmd.
	* target.h (struct target_ops) <to_can_do_single_step>: New field.
	(target_can_do_single_step): New macro.
	* target-delegates.c: Re-generated.

gdb/gdbserver:

2015-09-15  Yao Qi  <yao.qi@linaro.org>

	* server.c (vCont_supported): New global variable.
	(handle_query): Set vCont_supported to 1 if "vContSupported+"
	matches.  Append ";vContSupported+" to own_buf.
	(handle_v_requests): Append ";s;S" to own_buf if target supports
	hardware single step or vCont_supported is false.
	(capture_main): Set vCont_supported to zero.

gdb/doc:

2015-09-15  Yao Qi  <yao.qi@linaro.org>

	* gdb.texinfo (General Query Packets): Add vContSupported to
	tables of 'gdbfeatures' and 'stub features' supported in the
	qSupported packet, as well as to the list containing stub
	feature details.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix gdb.threads/non-ldr-exc-3.exp race
@ 2015-09-15 16:59 sergiodj+buildbot
  2015-09-15 18:43 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-09-15 16:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d15dcecdee0f07b0b088dd3a8ebb50826c5b7bc5 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: d15dcecdee0f07b0b088dd3a8ebb50826c5b7bc5

Fix gdb.threads/non-ldr-exc-3.exp race

gdb.threads/non-ldr-exc-3.exp is sometimes failing like this:

 [Switching to Thread 6831.6832]

 Breakpoint 2, thread_execler (arg=0x0) at /home/pedro/gdb/mygit/build/../src/gdb/testsuite/gdb.threads/non-ldr-exc-3.c:41
 41        if (execl (image, image, argv1, NULL) == -1) /* break-here */
 PASS: gdb.threads/non-ldr-exc-3.exp: lock-sched=on,non-stop=off: continue to breakpoint
 (gdb) set scheduler-locking on
 (gdb) FAIL: gdb.threads/non-ldr-exc-3.exp: lock-sched=on,non-stop=off: set scheduler-locking on

The problem is that the gdb_test_multiple is missing the prompt
anchor.  The problem was introduced by 2fd33e9448.  This reverts the
hunk that introduced the problem, reverting back to
gdb_continue_to_breakpoint.

gdb/testsuite/ChangeLog:
2015-09-15  Pedro Alves  <palves@redhat.com>

	* gdb.threads/non-ldr-exc-3.exp (do_test): Use
	gdb_continue_to_breakpoint instead of gdb_test_multiple.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix typo
@ 2015-09-15 17:18 sergiodj+buildbot
  2015-09-15 20:46 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-09-15 17:18 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7c5d0fad2e732bdea75f585b67fc1a0cc4d3107f ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 7c5d0fad2e732bdea75f585b67fc1a0cc4d3107f

Fix typo

gdb/gdbserver:

2015-09-15  Yao Qi  <yao.qi@linaro.org>

	* server.c (handle_query): Check string comparison using
	"else if" instead of "if".


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] PR remote/18965: vforkdone stop reply should indicate parent PID
@ 2015-09-15 17:23 sergiodj+buildbot
  2015-09-15 21:56 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-09-15 17:23 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8228463cbca8d629572dbad99286c4e05886350b ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 8228463cbca8d629572dbad99286c4e05886350b

PR remote/18965: vforkdone stop reply should indicate parent PID

The vforkdone stop reply misses indicating the thread ID of the vfork
parent which the event relates to:

 @cindex vfork events, remote reply
 @item vfork
 The packet indicates that @code{vfork} was called, and @var{r}
 is the thread ID of the new child process. Refer to
 @ref{thread-id syntax} for the format of the @var{thread-id}
 field.  This packet is only applicable to targets that support
 vfork events.

 @cindex vforkdone events, remote reply
 @item vforkdone
 The packet indicates that a child process created by a vfork
 has either called @code{exec} or terminated, so that the
 address spaces of the parent and child process are no longer
 shared. The @var{r} part is ignored.  This packet is only
 applicable to targets that support vforkdone events.

Unfortunately, this is not just a documentation issue.  GDBserver
is really not specifying the thread ID.  I noticed because
in non-stop mode, gdb complains:

 [Thread 6089.6089] #1 stopped.
 #0  0x0000003615a011f0 in ?? ()
 0x0000003615a011f0 in ?? ()
 (gdb) set debug remote 1
 (gdb) c
 Continuing.
 Sending packet: $QPassSignals:e;10;14;17;1a;1b;1c;21;24;25;2c;4c;#5f...Packet received: OK
 Sending packet: $vCont;c:p17c9.17c9#88...Packet received: OK
   Notification received: Stop:T05vfork:p17ce.17ce;06:40d7ffffff7f0000;07:30d7ffffff7f0000;10:e4c9eb1536000000;thread:p17c9.17c9;core:2;
 Sending packet: $vStopped#55...Packet received: OK
 Sending packet: $D;17ce#af...Packet received: OK
 Sending packet: $vCont;c:p17c9.17c9#88...Packet received: OK
   Notification received: Stop:T05vforkdone:;
 No process or thread specified in stop reply: T05vforkdone:;
 (gdb)

This is not non-stop-mode-specific, however.  Consider e.g., that in
all-stop, you may be debugging more than one process at the same time.
You continue, and both processes vfork.  So when you next get a
T05vforkdone, there's no way to tell which of the parent processes is
done with the vfork.

Tests will be added later.

Tested on x86_64 Fedora 20.

gdb/ChangeLog:
2015-09-15  Pedro Alves  <palves@redhat.com>

	PR remote/18965
	* remote-utils.c (prepare_resume_reply): Merge
	TARGET_WAITKIND_VFORK_DONE switch case with the
	TARGET_WAITKIND_FORKED case.

gdb/doc/ChangeLog:
2015-09-15  Pedro Alves  <palves@redhat.com>

	PR remote/18965
	* gdb.texinfo (Stop Reply Packets): Explain that vforkdone's 'r'
	part indicates the thread ID of the parent process.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [AArch64] Use debug_printf instead of fprintf_unfiltered
@ 2015-09-15 18:41 sergiodj+buildbot
  2015-09-16 12:35 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-09-15 18:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b277c936e06479f38ec21dbd6322463c9435bad3 ***

Author: Pierre Langlois <pierre.langlois@arm.com>
Branch: master
Commit: b277c936e06479f38ec21dbd6322463c9435bad3

[AArch64] Use debug_printf instead of fprintf_unfiltered

GDBserver uses debug_printf to print debugging output.  This patch makes
GDB use this too so we can share some of this code with GDBserver later.

gdb/ChangeLog:

	* aarch64-tdep.c (decode_add_sub_imm): Use debug_printf.
	(decode_adrp): Likewise.
	(decode_b): Likewise.
	(decode_bcond): Likewise.
	(decode_br): Likewise.
	(decode_cb): Likewise.
	(decode_eret): Likewise.
	(decode_movz): Likewise.
	(decode_orr_shifted_register_x): Likewise.
	(decode_ret): Likewise.
	(decode_stp_offset): Likewise.
	(decode_stp_offset_wb): Likewise.
	(decode_stur): Likewise.
	(decode_tb): Likewise.
	(aarch64_analyze_prologue): Likewise.
	(pass_in_x): Likewise.
	(pass_in_v): Likewise.
	(pass_on_stack): Likewise.
	(aarch64_push_dummy_call): Likewise.
	(aarch64_extract_return_value): Likewise.
	(aarch64_store_return_value): Likewise.
	(aarch64_return_value): Likewise.
	(aarch64_record_asimd_load_store): Likewise.
	(aarch64_record_load_store): Likewise.
	(aarch64_record_data_proc_simd_fp): Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix PR/18564 - regression in showing __thread so extern variable
@ 2015-09-15 19:46 sergiodj+buildbot
  2015-09-16 13:03 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-09-15 19:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5382cfab6110741b8ba36965b30334c00d8f9409 ***

Author: Philippe Waroquiers <philippe.waroquiers@skynet.be>
Branch: master
Commit: 5382cfab6110741b8ba36965b30334c00d8f9409

Fix PR/18564 - regression in showing __thread so extern variable

Ensure tls variable address is not relocated, as the msym addr
is an offset in the thread local storage of the shared library/object.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] xtensa: generate PLT entries for call0 ABI
@ 2015-09-15 20:19 sergiodj+buildbot
  2015-09-16 13:29 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-09-15 20:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 92b3f0082674ecdb4dad89d722acd069aef0dafa ***

Author: Max Filippov <jcmvbkbc@gmail.com>
Branch: master
Commit: 92b3f0082674ecdb4dad89d722acd069aef0dafa

xtensa: generate PLT entries for call0 ABI

2015-09-15  Max Filippov  <jcmvbkbc@gmail.com>
bfd/
	* elf32-xtensa.c (elf_xtensa_be_plt_entry)
	(elf_xtensa_le_plt_entry): Emit 'entry' instruction only for
	windowed ABI.
	(elf_xtensa_create_plt_entry): Generate 'l32r' offsets and fix
	up instructions according to ABI.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Handle clang naming of function static local variable.
@ 2015-09-15 21:24 sergiodj+buildbot
  2015-09-16 15:03 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-09-15 21:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b326e5870e54f52d52c32388f7f6e07454e2f2c2 ***

Author: Doug Evans <dje@google.com>
Branch: master
Commit: b326e5870e54f52d52c32388f7f6e07454e2f2c2

Handle clang naming of function static local variable.

clang names the local variable t_structs_a.buf.

gdb/testsuite/ChangeLog:

	* gdb.base/callfuncs.exp (do_function_calls): Handle clang naming
	of function static local variable.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [Ada] Enhance type printing for arrays with variable-sized elements
@ 2015-09-15 22:14 sergiodj+buildbot
  2015-09-16 16:25 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-09-15 22:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bfca584fae65570fa8ed052f662948763f3ccfa8 ***

Author: Pierre-Marie de Rodat <derodat@adacore.com>
Branch: master
Commit: bfca584fae65570fa8ed052f662948763f3ccfa8

[Ada] Enhance type printing for arrays with variable-sized elements

This change is relevant only for standard DWARF (as opposed to the GNAT
encodings extensions): at the time of writing it only makes a difference
with GCC patches that are to be integrated: see the patch series
submission at
<https://gcc.gnu.org/ml/gcc-patches/2015-07/msg01353.html>.

Given the following Ada declarations:

   subtype Small_Int is Natural range 0 .. 100;
   type R_Type (L : Small_Int := 0) is record
      S : String (1 .. L);
   end record;
   type A_Type is array (Natural range <>) of R_Type;

   A : A_Type := (1 => (L => 0, S => ""),
                  2 => (L => 2, S => "ab"));

Before this change, we would get the following GDB session:

    (gdb) ptype a
    type = array (1 .. 2) of foo.r_type <packed: 838-bit elements>

This is wrong: "a" is not a packed array.  This output comes from the
fact that, because R_Type has a dynamic size (with a maximum), the
compiler has to describe in the debugging information the size allocated
for each array element (i.e. the stride, in DWARF parlance: see
DW_AT_byte_stride).  Ada type printing currently assumes that arrays
with a stride are packed, hence the above output.

In practice, GNAT never performs bit-packing for arrays that contain
variable-sized elements.  Leveraging this fact, this patch enhances type
printing so that ptype does not pretend that arrays are packed when they
have a stride and they contain dynamic elements.  After this change, we
get the following expected output:

    (gdb) ptype a
    type = array (1 .. 2) of foo.r_type

gdb/ChangeLog:

	* ada-typeprint.c (print_array_type): Do not describe arrays as
	packed when they embed dynamic elements.

gdb/testsuite/ChangeLog:

	* gdb.ada/array_of_variable_length.exp: New testcase.
	* gdb.ada/array_of_variable_length/foo.adb: New file.
	* gdb.ada/array_of_variable_length/pck.adb: New file.
	* gdb.ada/array_of_variable_length/pck.ads: New file.

Tested on x86_64-linux, no regression.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix slowdown in ld -r for most common case of out-of-order relocs
@ 2015-09-16 13:43 sergiodj+buildbot
  2015-09-16 20:47 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-09-16 13:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bca6d0e3195217576b39fa1205469e1d578b386a ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: bca6d0e3195217576b39fa1205469e1d578b386a

Fix slowdown in ld -r for most common case of out-of-order relocs

I chose insertion sort since relocs are mostly sorted, but there is a
common case we can handle better;  A run of relocs put out of order
due to not linking input files in order.

	PR 18867
	* elflink.c (elf_link_adjust_relocs): Modify insertion sort to
	insert a run.  Return status in case of malloc failure.
	Adjust callers.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Make it easier to debug non-stop-fair-events.exp
@ 2015-09-16 15:38 sergiodj+buildbot
  2015-09-17 10:51 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-09-16 15:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d136eff549649f23b12121575362dfa09343ea0a ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: d136eff549649f23b12121575362dfa09343ea0a

Make it easier to debug non-stop-fair-events.exp

If we enable infrun debug running this test, it quickly fails with a
full expect buffer.  That can be simply handled with a couple
exp_continues.  As it's annoying to hack this every time we need to
debug the test, this patch adds bits to enable debugging support
easily, with a one-line change.

And then, if any iteration of the test fails, we end up with a long
cascade of time outs.  Just bail out when we see the first fail.

gdb/testsuite/
2015-09-16  Pedro Alves  <palves@redhat.com>

	* gdb.threads/non-stop-fair-events.exp (gdb_test_no_anchor)
	(enable_debug): New procedures.
	(test): Use them.  Bail out if waiting for threads fails.
	(top level): Bail out if a test fails.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix argument to compiled_cond, and add cases for compiled-condition.
@ 2015-09-16 17:26 sergiodj+buildbot
  2015-09-17 11:13 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-09-16 17:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d78908cff50f281dab6390646fb1b7c58236d83e ***

Author: Wei-cheng Wang <cole945@gmail.com>
Branch: master
Commit: d78908cff50f281dab6390646fb1b7c58236d83e

Fix argument to compiled_cond, and add cases for compiled-condition.

This patch fixes the argument passed to compiled_cond.  It should be
regs buffer instead of tracepoint_hit_ctx.  Test case is added as
well for testing compiled-cond.

gdb/gdbserver/ChangeLog

2015-09-16  Wei-cheng Wang  <cole945@gmail.com>

	* tracepoint.c (eval_result_type): Change prototype.
	(condition_true_at_tracepoint): Fix argument to compiled_cond.

gdb/testsuite/ChangeLog

2015-09-16  Wei-cheng Wang  <cole945@gmail.com>

	* gdb.trace/ftrace.exp: (test_ftrace_condition) New function
	for testing bytecode compilation.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Add test case for tracepoints with conditions
@ 2015-09-17 11:54 sergiodj+buildbot
  2015-09-18  3:23 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-09-17 11:54 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 43691ca179b1e573ca01e7bff87404519d4a3d75 ***

Author: Pierre Langlois <pierre.langlois@arm.com>
Branch: master
Commit: 43691ca179b1e573ca01e7bff87404519d4a3d75

Add test case for tracepoints with conditions

This patch adds a test case for tracepoints with a condition expression.
Each case will test a condition against the number of frames that should
have been traced.  Some of these tests fail on x86_64 and others on
i386, which have been marked as known failures for now, see PR/18955.

gdb/testsuite/ChangeLog:

2015-09-17  Pierre Langlois  <pierre.langlois@arm.com>
	    Yao Qi  <yao.qi@linaro.org>

	* gdb.trace/trace-condition.c: New file.
	* gdb.trace/trace-condition.exp: New file.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] btrace: improve stepping debugging
@ 2015-09-18 13:17 sergiodj+buildbot
  2015-09-18 17:28 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-09-18 13:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 987e68b1a38ad9116f309bff006e794c7e6f85e8 ***

Author: Markus Metzger <markus.t.metzger@intel.com>
Branch: master
Commit: 987e68b1a38ad9116f309bff006e794c7e6f85e8

btrace: improve stepping debugging

gdb/
	* record-btrace.c (btrace_thread_flag_to_str)
	(record_btrace_cancel_resume): New.
	(record_btrace_step_thread): Call btrace_thread_flag_to_str.
	(record_btrace_resume): Print execution direction.
	(record_btrace_resume_thread): Call btrace_thread_flag_to_str.
	(record_btrace_wait): Call record_btrace_cancel_resume.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] btrace: extract the breakpoint check from record_btrace_step_thread
@ 2015-09-18 13:30 sergiodj+buildbot
  2015-09-18 19:02 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-09-18 13:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3c615f99d3923df7dfa94c6587733c682efbbc78 ***

Author: Markus Metzger <markus.t.metzger@intel.com>
Branch: master
Commit: 3c615f99d3923df7dfa94c6587733c682efbbc78

btrace: extract the breakpoint check from record_btrace_step_thread

There are two places where record_btrace_step_thread checks for a breakpoint
at the current replay position.  Move this code into its own function.

gdb/
	* record-btrace.c (record_btrace_replay_at_breakpoint): New.
	(record_btrace_step_thread): Call record_btrace_replay_at_breakpoint.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] btrace: split record_btrace_step_thread
@ 2015-09-18 13:50 sergiodj+buildbot
  2015-09-18 21:00 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-09-18 13:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d825d248105e1c9a13fef4a35e76b6f4912e3792 ***

Author: Markus Metzger <markus.t.metzger@intel.com>
Branch: master
Commit: d825d248105e1c9a13fef4a35e76b6f4912e3792

btrace: split record_btrace_step_thread

The code for BTHR_STEP and BTHR_CONT is fairly similar.  Extract the common
parts into a new function record_btrace_single_step_forward.  The function
returns TARGET_WAITKIND_SPURIOUS to indicate that the single-step completed
without triggering a trap.

Same for BTHR_RSTEP and BTHR_RCONT.

gdb/
	* record-btrace.c (btrace_step_spurious)
	(record_btrace_single_step_forward)
	(record_btrace_single_step_backward): New.
	(record_btrace_step_thread): Call record_btrace_single_step_forward
	and record_btrace_single_step_backward.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] btrace: add missing NO_HISTORY
@ 2015-09-18 14:04 sergiodj+buildbot
  2015-09-18 23:59 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-09-18 14:04 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cf8f8f0c4244b4980ce538680f81de3738ba08d6 ***

Author: Markus Metzger <markus.t.metzger@intel.com>
Branch: master
Commit: cf8f8f0c4244b4980ce538680f81de3738ba08d6

btrace: add missing NO_HISTORY

If a single-step ended right at the end of the execution history, we forgot
to announce that.  Fix it.

gdb/
	* record-btrace.c (record_btrace_single_step_forward): Return
	NO_HISTORY if a step brings us to the end of the execution history.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] btrace: lock-step
@ 2015-09-18 14:13 sergiodj+buildbot
  2015-09-19  3:21 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-09-18 14:13 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e3cfc1c76d89f904659b106d78b352884797967b ***

Author: Markus Metzger <markus.t.metzger@intel.com>
Branch: master
Commit: e3cfc1c76d89f904659b106d78b352884797967b

btrace: lock-step

Record btrace's to_wait method picks a single thread to step.  When passed
minus_one_ptid, it picks the current thread.  All other threads remain where
they are.

Change this to step all resumed threads together, one step at a time, until
the first thread reports an event.

We do delay reporting NO_HISTORY events until there are no other events to
report to prevent threads at the end of their execution history from starving
other threads.

We keep threads at the end of their execution history moving and replaying
until we announce their stop in to_wait.  This shouldn't really be user-visible
but its a detail worth mentioning.

Since record btrace's to_resume method also picks only a single thread to
resume, there shouldn't be a difference with the current all-stop.

With non-stop or all-stop on top of non-stop, we will see differences.  The
behaviour should be more natural as we're moving all threads.

gdb/
	* record-btrace.c: Include vec.h.
	(record_btrace_find_thread_to_move): Removed.
	(btrace_step_no_resumed, btrace_step_again)
	(record_btrace_stop_replaying_at_end): New.
	(record_btrace_cancel_resume): Call record_btrace_stop_replaying_at_end.
	(record_btrace_single_step_forward): Remove calls to
	record_btrace_stop_replaying.
	(record_btrace_step_thread): Do only one step for BTHR_CONT and
	BTHR_RCONT.  Keep threads at the end of their history moving.
	(record_btrace_wait): Call record_btrace_step_thread for all threads
	until one reports an event.  Call record_btrace_stop_replaying_at_end
	for the eventing thread.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] btrace: resume all requested threads
@ 2015-09-18 14:15 sergiodj+buildbot
  2015-09-19  6:20 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-09-18 14:15 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0ca912dfef6289f9d2cd7d70b7ec80883a9b4395 ***

Author: Markus Metzger <markus.t.metzger@intel.com>
Branch: master
Commit: 0ca912dfef6289f9d2cd7d70b7ec80883a9b4395

btrace: resume all requested threads

The record targets are implicitly schedlocked.  They only step the current
thread and keep other threads where they are.

Change record btrace to step all requested threads in to_resume.

For maintenance and debugging, we keep the old behaviour when the target below
is not non-stop.  Enable with "maint set target-non-stop on".

gdb/
	* record-btrace.c (record_btrace_resume_thread): A move request
	overwrites a previous move request.
	(record_btrace_find_resume_thread): Removed.
	(record_btrace_resume): Resume all requested threads.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] btrace: async
@ 2015-09-18 14:30 sergiodj+buildbot
  2015-09-19 11:15 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-09-18 14:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a6b5be76f94664406def040d79ac8bc4d4aa8bd0 ***

Author: Markus Metzger <markus.t.metzger@intel.com>
Branch: master
Commit: a6b5be76f94664406def040d79ac8bc4d4aa8bd0

btrace: async

The record btrace target runs synchronous with GDB.  That is, GDB steps
resumed threads in record btrace's to_wait method.  Without GDB calling
to_wait, nothing happens 'on the target'.

Check for further expected events in to_wait before reporting the current
event and mark record btrace's async event handler in async mode.

gdb/
	* record-btrace.c (record_btrace_maybe_mark_async_event): New.
	(record_btrace_wait): Call record_btrace_maybe_mark_async_event.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] infrun: switch to NO_HISTORY thread
@ 2015-09-18 14:37 sergiodj+buildbot
  2015-09-19 14:24 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-09-18 14:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d1988021e345c990f4272843577529a123f8943d ***

Author: Markus Metzger <markus.t.metzger@intel.com>
Branch: master
Commit: d1988021e345c990f4272843577529a123f8943d

infrun: switch to NO_HISTORY thread

A thread that runs out of its execution history is stopped.  We already set
stop_pc and call stop_waiting.  But we do not switch to the stopped thread.

In normal_stop, we call finish_thread_state_cleanup to set a thread's running
state.  In all-stop mode, we call it with minus_one_ptid; in non-stop mode, we
only call it for inferior_ptid.

If in non-stop mode normal_stop is called on behalf of a thread that is not
inferior_ptid, that other thread will still be reported as running.  If it is
actually stopped it can't be resumed again.

Record targets traditionally don't support non-stop and only resume
inferior_ptid.  So this has not been a problem, so far.

Switch to the eventing thread for NO_HISTORY events as preparation to support
non-stop for the record btrace target.

gdb/
	* infrun.c (handle_inferior_event_1): Switch to the eventing thread
	in the TARKET_WAITKIND_NO_HISTORY case.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] btrace: non-stop
@ 2015-09-18 14:47 sergiodj+buildbot
  2015-09-19 15:41 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-09-18 14:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cbb55fa7a110e499dae0170060d762eb3f243768 ***

Author: Markus Metzger <markus.t.metzger@intel.com>
Branch: master
Commit: cbb55fa7a110e499dae0170060d762eb3f243768

btrace: non-stop

Support non-stop mode in record btrace.

gdb/
	* record-btrace.c (record_btrace_open): Remove non_stop check.
	* NEWS: Announce that record btrace supports non-stop mode.

testsuite/
	* gdb.btrace/non-stop.c: New.
	* gdb.btrace/non-stop.exp: New.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] target, record: add PTID argument to to_record_is_replaying
@ 2015-09-18 14:54 sergiodj+buildbot
  2015-09-19 16:07 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-09-18 14:54 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a52eab48080f29feaa56421481cfea221ee6346e ***

Author: Markus Metzger <markus.t.metzger@intel.com>
Branch: master
Commit: a52eab48080f29feaa56421481cfea221ee6346e

target, record: add PTID argument to to_record_is_replaying

The to_record_is_replaying target method is used to query record targets if
they are replaying.  This is currently interpreted as "is any thread being
replayed".

Add a PTID argument and change the interpretation to "is any thread matching
PTID being replayed".

Change all users to pass minus_one_ptid to preserve the old meaning.

The record full target does not really support multi-threading and ignores
the PTID argument.

gdb/
	* record-btrace.c (record_btrace_is_replaying): Add ptid argument.
	Update users to pass minus_one_ptid.
	* record-full.c (record_full_is_replaying): Add ptid argument (ignored).
	* record.c (cmd_record_delete): Pass inferior_ptid to
	target_record_is_replaying.
	* target-delegates.c: Regenerated.
	* target.c (target_record_is_replaying): Add ptid argument.
	* target.h (struct target_ops) <to_record_is_replaying>: Add ptid
	argument.
	(target_record_is_replaying): Add ptid argument.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] btrace: allow full memory and register access for non-replaying threads
@ 2015-09-18 15:02 sergiodj+buildbot
  2015-09-19 17:35 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-09-18 15:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4d10e986f499f330963c4641fd91046c57c94bd8 ***

Author: Markus Metzger <markus.t.metzger@intel.com>
Branch: master
Commit: 4d10e986f499f330963c4641fd91046c57c94bd8

btrace: allow full memory and register access for non-replaying threads

The record btrace target does not allow accessing memory and storing registers
while replaying.  For multi-threaded applications, this prevents those
accesses also for threads that are at the end of their execution history as
long as at least one thread is replaying.

Change this to only check if the selected thread is replaying.  This allows
threads that are at the end of their execution history to read and write
memory and to store registers.

Also change the error message to reflect this change.

gdb/
	* record-btrace.c (record_btrace_xfer_partial)
	(record_btrace_store_registers, record_btrace_prepare_to_store):
	Call record_btrace_is_replaying with inferior_ptid instead of
	minus_one_ptid.
	(record_btrace_store_registers): Change error message.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] target: add to_record_stop_replaying target method
@ 2015-09-18 15:02 sergiodj+buildbot
  2015-09-19 20:00 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-09-18 15:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 797094dddfbcc3ea1d0efc900185ba3857d30226 ***

Author: Markus Metzger <markus.t.metzger@intel.com>
Branch: master
Commit: 797094dddfbcc3ea1d0efc900185ba3857d30226

target: add to_record_stop_replaying target method

Add a new target method to_record_stop_replaying to stop replaying.

gdb/
	* record-btrace.c (record_btrace_resume): Call
	target_record_stop_replaying.
	(record_btrace_stop_replaying_all): New.
	(init_record_btrace_ops): Initialize to_record_stop_replaying.
	* record-full.c (record_full_stop_replaying): New.
	(init_record_full_ops ): Initialize to_record_stop_replaying.
	* target-delegates.c: Regenerated.
	* target.c (target_record_stop_replaying): New.
	* target.h (struct target_ops) <to_record_stop_replaying>: New.
	(target_record_stop_replaying): New.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] target: add to_record_will_replay target method
@ 2015-09-18 15:12 sergiodj+buildbot
  2015-09-19 21:34 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-09-18 15:12 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7ff27e9babb1564a9c0e213c4a42396aa420f8cc ***

Author: Markus Metzger <markus.t.metzger@intel.com>
Branch: master
Commit: 7ff27e9babb1564a9c0e213c4a42396aa420f8cc

target: add to_record_will_replay target method

Add a new target method to_record_will_replay to query if there is a record
target that will replay at least one thread matching the argument PTID if it
were executed in the argument execution direction.

gdb/
	* record-btrace.c ((record_btrace_will_replay): New.
	(init_record_btrace_ops): Initialize to_record_will_replay.
	* record-full.c ((record_full_will_replay): New.
	(init_record_full_ops): Initialize to_record_will_replay.
	* target-delegates.c: Regenerated.
	* target.c (target_record_will_replay): New.
	* target.h (struct target_ops) <to_record_will_replay>: New.
	(target_record_will_replay): New.

Signed-off-by: Markus Metzger <markus.t.metzger@intel.com>


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] btrace: move breakpoint checking into stepping functions
@ 2015-09-18 15:19 sergiodj+buildbot
  2015-09-18 22:24 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-09-18 15:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 011c71b6cbda4ecd856a08cf3124330d7f4342de ***

Author: Markus Metzger <markus.t.metzger@intel.com>
Branch: master
Commit: 011c71b6cbda4ecd856a08cf3124330d7f4342de

btrace: move breakpoint checking into stepping functions

Breakpoints are only checked for BTHR_CONT and BTHR_RCONT stepping requests.
A BTHR_STEP and BTHR_RSTEP request will always report stopped without reason.
Since breakpoints are reported correctly, I assume infrun is handling this.

Move the breakpoint check into the btrace single stepping functions.  This
will cause us to report breakpoint hits now also for single-step requests.

One thing to notice is that

  - when executing forwards, the breakpoint is checked before 'executing'
    the instruction, i.e. before moving the PC to the next instruction.

  - when executing backwards,  the breakpoint is checked after 'executing'
    the instruction, i.e. after moving the PC to the preceding instruction
    in the recorded execution.

There is code in infrun (see, for example proceed and adjust_pc_after_break)
that handles this and also depends on this behaviour.

gdb/
	* record-btrace.c (record_btrace_step_thread): Move breakpoint check
	to ...
	(record_btrace_single_step_forward): ... here and
	(record_btrace_single_step_backward): ... here.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] infrun: scheduler-locking replay
@ 2015-09-18 15:44 sergiodj+buildbot
  2015-09-19 23:38 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-09-18 15:44 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f2665db5f2c20f3f47673ad5343738b10ce81dde ***

Author: Markus Metzger <markus.t.metzger@intel.com>
Branch: master
Commit: f2665db5f2c20f3f47673ad5343738b10ce81dde

infrun: scheduler-locking replay

Record targets behave as if scheduler-locking were on in replay mode.  Add a
new scheduler-locking option "replay" to make this implicit behaviour explicit.
It behaves like "on" in replay mode and like "off" in record mode.

By making the current behaviour a scheduler-locking option, we allow the user
to change it.  Since it is the current behaviour, this new option is also
the new default.

One caveat is that when resuming a thread that is at the end of its execution
history, record btrace implicitly stops replaying other threads and resumes
the entire process.  This is a convenience feature to not require the user
to explicitly move all other threads to the end of their execution histories
before being able to resume the process.

We mimick this behaviour with scheduler-locking replay and move it from
record-btrace into infrun.  With all-stop on top of non-stop, we can't do
this in record-btrace anymore.

Record full does not really support multi-threading and is therefore not
impacted.  If it were extended to support multi-threading, it would 'benefit'
from this change.  The good thing is that all record targets will behave the
same with respect to scheduler-locking.

I put the code for this into clear_proceed_status.  It also sends the
about_to_proceed notification.

gdb/
	* NEWS: Announce new scheduler-locking mode.
	* infrun.c (schedlock_replay): New.
	(scheduler_enums): Add schedlock_replay.
	(scheduler_mode): Change default to schedlock_replay.
	(user_visible_resume_ptid): Handle schedlock_replay.
	(clear_proceed_status_thread): Stop replaying if resumed thread is
	not replaying.
	(schedlock_applies): Handle schedlock_replay.
	(_initialize_infrun): Document new scheduler-locking mode.
	* record-btrace.c (record_btrace_resume): Remove code to stop other
	threads when not replaying the resumed thread.

doc/
	* gdb.texinfo (All-Stop Mode): Describe new scheduler-locking mode.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Require readline for gdb.linespec/explicit.exp tab-completion tests.
@ 2015-09-18 16:29 sergiodj+buildbot
  2015-09-20  6:51 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-09-18 16:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 515b89b30c18dae6b91e57ec2dd336919bb4578d ***

Author: Sandra Loosemore <sandra@codesourcery.com>
Branch: master
Commit: 515b89b30c18dae6b91e57ec2dd336919bb4578d

Require readline for gdb.linespec/explicit.exp tab-completion tests.

2015-09-18  Sandra Loosemore  <sandra@codesourcery.com>

	gdb/testsuite/
	* gdb.linespec/explicit.exp: Check for readline support for
	tab-completion tests.  Fix obvious typo.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix shared library load in gdb.base/global-var-nested-by-dso.exp.
@ 2015-09-18 16:46 sergiodj+buildbot
  2015-09-20 10:28 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-09-18 16:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7800dbe4301d831dd81a469107eb5f0e1bd0b927 ***

Author: Sandra Loosemore <sandra@codesourcery.com>
Branch: master
Commit: 7800dbe4301d831dd81a469107eb5f0e1bd0b927

Fix shared library load in gdb.base/global-var-nested-by-dso.exp.

2015-09-18  Sandra Loosemore  <sandra@codesourcery.com>

	gdb/testsuite/
	* gdb.base/global-var-nested-by-dso.exp: Call gdb_load_shlibs.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Generalize breakpoint pattern in gdb.mi/mi-cli.exp.
@ 2015-09-18 17:29 sergiodj+buildbot
  2015-09-20 14:25 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-09-18 17:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f57929f229c97462650cef4086bb930290ba92af ***

Author: Sandra Loosemore <sandra@codesourcery.com>
Branch: master
Commit: f57929f229c97462650cef4086bb930290ba92af

Generalize breakpoint pattern in gdb.mi/mi-cli.exp.

2015-09-18  Sandra Loosemore  <sandra@codesourcery.com>

	gdb/testsuite/
	* gdb.mi/mi-cli.exp: Don't require directory prefix in breakpoint
	filename pattern.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix pathname prefix and timeout issues in gdb.mi/mi-pending.exp.
@ 2015-09-18 19:46 sergiodj+buildbot
  2015-09-20 18:26 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-09-18 19:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 79dc332ba2db30e02e816f6ecbffca548f2f6c30 ***

Author: Sandra Loosemore <sandra@codesourcery.com>
Branch: master
Commit: 79dc332ba2db30e02e816f6ecbffca548f2f6c30

Fix pathname prefix and timeout issues in gdb.mi/mi-pending.exp.

2015-09-18  Sandra Loosemore  <sandra@codesourcery.com>

	gdb/testsuite/
	* gdb.mi/mi-pending.exp: Don't use directory prefix when setting
	the pending breakpoint.  Remove timeout override for "Run till
	MI pending breakpoint on pendfunc3 on thread 2" test.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] aarch64 multi-arch (part 3): get thread area
@ 2015-09-18 21:29 sergiodj+buildbot
  2015-09-20  4:11 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-09-18 21:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a0cc84cd15396df7752fe16659c01628ba729324 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: a0cc84cd15396df7752fe16659c01628ba729324

aarch64 multi-arch (part 3): get thread area

With the kernle fix <http://lists.infradead.org/pipermail/linux-arm-kernel/2015-July/356511.html>,
aarch64 GDB is able to read the base of thread area of 32-bit arm
program through NT_ARM_TLS.

This patch is to teach both GDB and GDBserver to read the base of
thread area correctly in the multi-arch case.  A new function
aarch64_ps_get_thread_area is added, and is shared between GDB and
GDBserver.

With this patch applied, the following fails in multi-arch testing
(GDB is aarch64 but the test cases are arm) are fixed,

 -FAIL: gdb.threads/tls-nodebug.exp: thread local storage
 -FAIL: gdb.threads/tls-shared.exp: print thread local storage variable
 -FAIL: gdb.threads/tls-so_extern.exp: print thread local storage variable
 -FAIL: gdb.threads/tls-var.exp: print tls_var
 -FAIL: gdb.threads/tls.exp: first thread local storage
 -FAIL: gdb.threads/tls.exp: first another thread local storage
 -FAIL: gdb.threads/tls.exp: p a_thread_local
 -FAIL: gdb.threads/tls.exp: p file2_thread_local
 -FAIL: gdb.threads/tls.exp: p a_thread_local second time

gdb:

2015-09-18  Yao Qi  <yao.qi@linaro.org>

	* nat/aarch64-linux.c: Include elf/common.h,
	nat/gdb_ptrace.h, asm/ptrace.h and sys/uio.h.
	(aarch64_ps_get_thread_area): New function.
	* nat/aarch64-linux.h: Include gdb_proc_service.h.
	(aarch64_ps_get_thread_area): Declare.
	* aarch64-linux-nat.c (ps_get_thread_area): Call
	aarch64_ps_get_thread_area.

gdb/gdbserver:

2015-09-18  Yao Qi  <yao.qi@linaro.org>

	* linux-aarch64-low.c: Don't include sys/uio.h.
	(ps_get_thread_area): Call aarch64_ps_get_thread_area.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] symtab.h (general_symbol_info) <mangled_lang>: delete and move up only member.
@ 2015-09-19  6:25 sergiodj+buildbot
  2015-09-20 19:05 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-09-19  6:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 615b3f6299d95db8507b2a68dda2704d08bcd1d0 ***

Author: Doug Evans <xdje42@gmail.com>
Branch: master
Commit: 615b3f6299d95db8507b2a68dda2704d08bcd1d0

symtab.h (general_symbol_info) <mangled_lang>: delete and move up only member.

gdb/ChangeLog:

	* symtab.h (general_symbol_info) <mangled_lang>: Delete struct,
	move only member demangled_name up.  All uses updated.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Replace current_inferior ()->gdbarch with its wrapper target_gdbarch.
@ 2015-09-19 17:02 sergiodj+buildbot
  2015-09-20 22:02 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-09-19 17:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7dc7c195f31657186dac0c4d6521200da11311fa ***

Author: Doug Evans <xdje42@gmail.com>
Branch: master
Commit: 7dc7c195f31657186dac0c4d6521200da11311fa

Replace current_inferior ()->gdbarch with its wrapper target_gdbarch.

gdb/ChangeLog:

	* ravenscar-thread.c (ravenscar_inferior_created): Replace
	current_inferior ()->gdbarch with its wrapper target_gdbarch.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Add --no-dynamic-linker option to ld, for static PIE use
@ 2015-09-20  7:58 sergiodj+buildbot
  2015-09-20 22:45 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-09-20  7:58 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9b8b325a1f4cdaf235e7d803849dde6ededec865 ***

Author: Rich Felker <dalias@libc.org>
Branch: master
Commit: 9b8b325a1f4cdaf235e7d803849dde6ededec865

Add --no-dynamic-linker option to ld, for static PIE use

Inhibits output of .interp section in ELF executables.

include/
	* bfdlink.h (struct bfd_link_info): Add "nointerp" field.
bfd/
	* elflink.c (_bfd_elf_link_create_dynamic_sections): Don't create
	.interp when info->nointerp.
	(bfd_elf_size_dynamic_sections): Adjust assert.
	* elf32-arm.c (elf32_arm_size_dynamic_sections): Don't size .interp
	when info->nointerp.
	* elf32-bfin.c (elf32_bfinfdpic_size_dynamic_sections): Likewise.
	* elf32-cr16.c (_bfd_cr16_elf_size_dynamic_sections): Likewise.
	* elf32-cris.c (elf_cris_size_dynamic_sections): Likewise.
	* elf32-frv.c (elf32_frvfdpic_size_dynamic_sections): Likewise.
	* elf32-hppa.c (elf32_hppa_size_dynamic_sections): Likewise.
	* elf32-i370.c (i370_elf_size_dynamic_sections): Likewise.
	* elf32-i386.c (elf_i386_size_dynamic_sections): Likewise.
	* elf32-lm32.c (lm32_elf_size_dynamic_sections): Likewise.
	* elf32-m32r.c (m32r_elf_size_dynamic_sections): Likewise.
	* elf32-m68k.c (elf_m68k_size_dynamic_sections): Likewise.
	* elf32-metag.c (elf_metag_size_dynamic_sections): Likewise.
	* elf32-nds32.c (nds32_elf_size_dynamic_sections): Likewise.
	* elf32-nios2.c (nios2_elf32_size_dynamic_sections): Likewise.
	* elf32-or1k.c (or1k_elf_size_dynamic_sections): Likewise.
	* elf32-ppc.c (ppc_elf_size_dynamic_sections): Likewise.
	* elf32-s390.c (elf_s390_size_dynamic_sections): Likewise.
	* elf32-score.c (s3_bfd_score_elf_size_dynamic_sections): Likewise.
	* elf32-score7.c (s7_bfd_score_elf_size_dynamic_sections): Likewise.
	* elf32-sh.c (sh_elf_size_dynamic_sections): Likewise.
	* elf32-tic6x.c (elf32_tic6x_size_dynamic_sections): Likewise.
	* elf32-tilepro.c (tilepro_elf_size_dynamic_sections): Likewise.
	* elf32-vax.c (elf_vax_size_dynamic_sections): Likewise.
	* elf32-xtensa.c (elf_xtensa_size_dynamic_sections): Likewise.
	* elf64-alpha.c (elf64_alpha_size_dynamic_sections): Likewise.
	* elf64-hppa.c (elf64_hppa_size_dynamic_sections): Likewise.
	* elf64-ppc.c (ppc64_elf_size_dynamic_sections): Likewise.
	* elf64-s390.c (elf_s390_size_dynamic_sections): Likewise.
	* elf64-sh64.c (sh64_elf64_size_dynamic_sections): Likewise.
	* elf64-x86-64.c (elf_x86_64_size_dynamic_sections): Likewise.
	* elfnn-aarch64.c (elfNN_aarch64_size_dynamic_sections): Likewise.
	* elfnn-ia64.c (elfNN_ia64_size_dynamic_sections): Likewise.
	* elfxx-mips.c (_bfd_mips_elf_size_dynamic_sections): Likewise.
	* elfxx-sparc.c (_bfd_sparc_elf_size_dynamic_sections): Likewise.
	* elfxx-tilegx.c (tilegx_elf_size_dynamic_sections): Likewise.
ld/
	* ld.texinfo (--no-dynamic-linker): Document.
	* ldlex.h (enum option_values): Add OPTION_NO_DYNAMIC_LINKER.
	* lexsup.c (ld_options, parse_args): Handle --no-dynamic-linker.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] crash printing non-local variable from nested subprogram
@ 2015-09-20 19:59 sergiodj+buildbot
  2015-09-21  5:27 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-09-20 19:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7d1c9c9b4c586ede0abecb7a0a47d8996aaf56da ***

Author: Joel Brobecker <brobecker@adacore.com>
Branch: master
Commit: 7d1c9c9b4c586ede0abecb7a0a47d8996aaf56da

crash printing non-local variable from nested subprogram

We have noticed that GDB would sometimes crash trying to print
from a nested function the value of a variable declared in an
enclosing scope. This appears to be target dependent, although
that correlation might only be fortuitious.  We noticed the issue
on x86_64-darwin, x86-vxworks6 and x86-solaris.  The investigation
was done on Darwin.

This is a new feature that was introduced by:

    commit 63e43d3aedb8b1112899c2d0ad74cbbee687e5d6
    Date:   Thu Feb 5 17:00:06 2015 +0100
    DWARF: handle non-local references in nested functions

We can reproduce the problem with one of the testcases that was
added with the patch (gdb.base/nested-subp1.exp), where we have...

    18 int
    19 foo (int i1)
    20 {
    21   int
    22   nested (int i2)
    23   {
    [...]
    27     return i1 * i2; /* STOP */
    28   }

...  After building the example program, and running until line 27,
try printing the value of "i1":

    % gdb gdb.base/nested-subp1
    (gdb) break foo.c:27
    (gdb) run
    Breakpoint 1, nested (i2=2) at /[...]/nested-subp1.c:27
    27          return i1 * i2; /* STOP */
    (gdb) p i1
    [1]    73090 segmentation fault  ../gdb -q gdb.base/nested-subp1

Ooops!

What happens is that, because the reference is non-local, we are trying
to follow the function's static link, which does...

    /* If we don't know how to compute FRAME's base address, don't give up:
       maybe the frame we are looking for is upper in the stace frame.  */
    if (framefunc != NULL
        && SYMBOL_BLOCK_OPS (framefunc)->get_frame_base != NULL
        && (SYMBOL_BLOCK_OPS (framefunc)->get_frame_base (framefunc, frame)
            == upper_frame_base))

... or, in other words, calls the get_frame_base "method" of
framefunc's struct symbol_block_ops data. This resolves to
the block_op_get_frame_base function.

Looking at the function's implementation, we see:

  struct dwarf2_locexpr_baton *dlbaton;
  [...]
  dlbaton = SYMBOL_LOCATION_BATON (framefunc);
  [...]
  result = dwarf2_evaluate_loc_desc (type, frame, start, length,
                                     dlbaton->per_cu);
                                     ^^^^^^^^^^^^^^^

Printing dlbaton->per_cu gives a value that seems fairly bogus for
a memory address (0x60). Because of it, dwarf2_evaluate_loc_desc
then crashes trying to dereference it.

What's different on Darwin compared to Linux is that the function's
frame base is encoded using the following form:

        .byte   0x40    # uleb128 0x40; (DW_AT_frame_base)
        .byte   0x6     # uleb128 0x6; (DW_FORM_data4)

... and so dwarf2_symbol_mark_computed ends up creating
a SYMBOL_LOCATION_BATON as a struct dwarf2_loclist_baton:

  if (attr_form_is_section_offset (attr)
      /* .debug_loc{,.dwo} may not exist at all, or the offset may be outside
         the section.  If so, fall through to the complaint in the
         other branch.  */
      && DW_UNSND (attr) < dwarf2_section_size (objfile, section))
    {
      struct dwarf2_loclist_baton *baton;
      [...]
      SYMBOL_LOCATION_BATON (sym) = baton;

However, if you look more closely at block_op_get_frame_base's
implementation, you'll notice that the function extracts the
symbol's SYMBOL_LOCATION_BATON as a dwarf2_locexpr_baton
(a DWARF _expression_ rather than a _location list_).
That's why we end up decoding the DLBATON improperly, and thus
pass a random dlbaton->per_cu when calling dwarf2_evaluate_loc_desc.

This works on x86_64-linux, because we indeed have the frame base
described using a different form:

        .uleb128 0x40   # (DW_AT_frame_base)
        .uleb128 0x18   # (DW_FORM_exprloc)

This patch fixes the issue by doing what we do for most (if not all)
other such methods: providing one implementation each for loc-list,
and loc-expr. Both implementations are nearly identical, so perhaps
we might later want to improve this. But this patch first tries to
fix the crash first, leaving the design issue for later.

gdb/ChangeLog:

        * dwarf2loc.c (locexpr_get_frame_base): Renames
        block_op_get_frame_base.
        (dwarf2_block_frame_base_locexpr_funcs): Replace reference to
        block_op_get_frame_base by reference to locexpr_get_frame_base.
        (loclist_get_frame_base): New function, near identical copy of
        locexpr_get_frame_base.
        (dwarf2_block_frame_base_loclist_funcs): Replace reference to
        block_op_get_frame_base by reference to loclist_get_frame_base.

Tested on x86_64-darwin (AdaCore testsuite), and x86_64-linux
(official testsuite).


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] dwarf2_compute_name: add fixme, don't use same name as parameter for local
@ 2015-09-20 22:27 sergiodj+buildbot
  2015-09-21  6:05 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-09-20 22:27 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2ee7123e5a54fba15b976a05bce173871eba8aba ***

Author: Doug Evans <xdje42@gmail.com>
Branch: master
Commit: 2ee7123e5a54fba15b976a05bce173871eba8aba

dwarf2_compute_name: add fixme, don't use same name as parameter for local

gdb/ChangeLog:

	* dwarf2read.c (dwarf2_compute_name): Add FIXME.  Don't use a local
	variable name that collides with a parameter.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] dwarf2read.c (add_partial_symbol): Remove outdated comments.
@ 2015-09-21  6:23 sergiodj+buildbot
  2015-09-21 11:42 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-09-21  6:23 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 183dc7ecf69a92653e0a72e0bbc02732bac9ec8c ***

Author: Doug Evans <xdje42@gmail.com>
Branch: master
Commit: 183dc7ecf69a92653e0a72e0bbc02732bac9ec8c

dwarf2read.c (add_partial_symbol): Remove outdated comments.

gdb/ChangeLog:

	* dwarf2read.c (add_partial_symbol): Remove outdated comments.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Wrap gdb_agent_op_sizes by #ifndef IN_PROCESS_AGENT
@ 2015-09-21 14:29 sergiodj+buildbot
  2015-09-21 15:37 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-09-21 14:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9812b2e60750cc7bbfa252d9ae8d85a72a399e01 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 9812b2e60750cc7bbfa252d9ae8d85a72a399e01

Wrap gdb_agent_op_sizes by #ifndef IN_PROCESS_AGENT

Hi,
I see the following build warning with recent GCC built from mainline,

aarch64-none-linux-gnu-gcc -g -O2    -I. -I/home/yao/SourceCode/gnu/gdb/git/gdb/gdbserver -I/home/yao/SourceCode/gnu/gdb/git/gdb/gdbserver/../common -I/home/yao/SourceCode/gnu/gdb/git/gdb/gdbserver/../regformats -I/home/yao/SourceCode/gnu/gdb/git/gdb/gdbserver/.. -I/home/yao/SourceCode/gnu/gdb/git/gdb/gdbserver/../../include -I/home/yao/SourceCode/gnu/gdb/git/gdb/gdbserver/../gnulib/import -Ibuild-gnulib-gdbserver/import  -Wall -Wpointer-arith -Wformat-nonliteral -Wno-char-subscripts -Wempty-body -Wdeclaration-after-statement -Werror -DGDBSERVER  -DCONFIG_UST_GDB_INTEGRATION -fPIC -DIN_PROCESS_AGENT -fvisibility=hidden -c -o ax-ipa.o -MT ax-ipa.o -MMD -MP -MF .deps/ax-ipa.Tpo `echo " -Wall -Wpointer-arith -Wformat-nonliteral -Wno-char-subscripts -Wempty-body -Wdeclaration-after-statement " | sed "s/ -Wformat-nonliteral / -Wno-format-nonliteral /g"` /home/yao/SourceCode/gnu/gdb/git/gdb/gdbserver/ax.c
/home/yao/SourceCode/gnu/gdb/git/gdb/gdbserver/ax.c:73:28: error: 'gdb_agent_op_sizes' defined but not used [-Werror=unused-const-variable]
 static const unsigned char gdb_agent_op_sizes [gdb_agent_op_last] =
                            ^
cc1: all warnings being treated as errors

gdb_agent_op_sizes is only used in function is_goto_target, which is
defined inside #ifndef IN_PROCESS_AGENT.  This warning is not arch
specific, so GCC mainline for other targets should produce this warning
too, although this warning is triggered by enabling aarch64 fast
tracepoint.  The fix is to move gdb_agent_op_sizes to

gdb/gdbserver:

2015-09-21  Yao Qi  <yao.qi@linaro.org>

	* ax.c [!IN_PROCESS_AGENT] (gdb_agent_op_sizes): Define it.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Move instruction decoding into new arch/ directory
@ 2015-09-21 14:42 sergiodj+buildbot
  2015-09-21 17:16 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-09-21 14:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 787749ead66eee8c20754c160bd79404b2109553 ***

Author: Pierre Langlois <pierre.langlois@arm.com>
Branch: master
Commit: 787749ead66eee8c20754c160bd79404b2109553

Move instruction decoding into new arch/ directory

This patch moves the following functions into the arch/ common
directory, in new files arch/aarch64-insn.{h,c}.  They are prefixed with
'aarch64_':

 - aarch64_decode_adrp
 - aarch64_decode_b
 - aarch64_decode_cb
 - aarch64_decode_tb

We will need them to implement fast tracepoints in GDBserver.

For consistency, this patch also adds the 'aarch64_' prefix to static
decoding functions that do not need to be shared right now.

V2:
 make sure the formatting issues propagated
 fix `gdbserver/configure.srv'.

gdb/ChangeLog:

	* Makefile.in (ALL_64_TARGET_OBS): Add aarch64-insn.o.
	(HFILES_NO_SRCDIR): Add arch/aarch64-insn.h.
	(aarch64-insn.o): New rule.
	* configure.tgt (aarch64*-*-elf): Add aarch64-insn.o.
	(aarch64*-*-linux*): Likewise.
	* arch/aarch64-insn.c: New file.
	* arch/aarch64-insn.h: New file.
	* aarch64-tdep.c: Include arch/aarch64-insn.h.
	(aarch64_debug): Move to arch/aarch64-insn.c.  Declare in
	arch/aarch64-insn.h.
	(decode_add_sub_imm): Rename to ...
	(aarch64_decode_add_sub_imm): ... this.
	(decode_adrp): Rename to ...
	(aarch64_decode_adrp): ... this.  Move to arch/aarch64-insn.c.
	Declare in arch/aarch64-insn.h.
	(decode_b): Rename to ...
	(aarch64_decode_b): ... this.  Move to arch/aarch64-insn.c.
	Declare in arch/aarch64-insn.h.
	(decode_bcond): Rename to ...
	(aarch64_decode_bcond): ... this.  Move to arch/aarch64-insn.c.
	Declare in arch/aarch64-insn.h.
	(decode_br): Rename to ...
	(aarch64_decode_br): ... this.
	(decode_cb): Rename to ...
	(aarch64_decode_cb): ... this.  Move to arch/aarch64-insn.c.
	Declare in arch/aarch64-insn.h.
	(decode_eret): Rename to ...
	(aarch64_decode_eret): ... this.
	(decode_movz): Rename to ...
	(aarch64_decode_movz): ... this.
	(decode_orr_shifted_register_x): Rename to ...
	(aarch64_decode_orr_shifted_register_x): ... this.
	(decode_ret): Rename to ...
	(aarch64_decode_ret): ... this.
	(decode_stp_offset): Rename to ...
	(aarch64_decode_stp_offset): ... this.
	(decode_stp_offset_wb): Rename to ...
	(aarch64_decode_stp_offset_wb): ... this.
	(decode_stur): Rename to ...
	(aarch64_decode_stur): ... this.
	(decode_tb): Rename to ...
	(aarch64_decode_tb): ... this.  Move to arch/aarch64-insn.c.
	Declare in arch/aarch64-insn.h.
	(aarch64_analyze_prologue): Adjust calls to renamed functions.

gdb/gdbserver/ChangeLog:

	* Makefile.in (aarch64-insn.o): New rule.
	* configure.srv (aarch64*-*-linux*): Add aarch64-insn.o.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Make aarch64_decode_adrp handle both ADR and ADRP instructions
@ 2015-09-21 14:52 sergiodj+buildbot
  2015-09-21 19:33 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-09-21 14:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6ec5f4be052e594dc90b6677fec1c1e7727d9651 ***

Author: Pierre Langlois <pierre.langlois@arm.com>
Branch: master
Commit: 6ec5f4be052e594dc90b6677fec1c1e7727d9651

Make aarch64_decode_adrp handle both ADR and ADRP instructions

We will need to decode both ADR and ADRP instructions in GDBserver.
This patch makes common code handle both cases, even if GDB only needs
to decode the ADRP instruction.

gdb/ChangeLog:

	* aarch64-tdep.c (aarch64_analyze_prologue): New is_adrp
	variable.  Call aarch64_decode_adr instead of
	aarch64_decode_adrp.
	* arch/aarch64-insn.h (aarch64_decode_adrp): Delete.
	(aarch64_decode_adr): New function declaration.
	* arch/aarch64-insn.c (aarch64_decode_adrp): Delete.
	(aarch64_decode_adr): New function, factored out from
	aarch64_decode_adrp to decode both adr and adrp instructions.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Implement target_emit_ops
@ 2015-09-21 15:08 sergiodj+buildbot
  2015-09-21 23:08 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-09-21 15:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT afbe19f83ad1af46e7b1f1639d9fa0eb873dcbb5 ***

Author: Pierre Langlois <pierre.langlois@arm.com>
Branch: master
Commit: afbe19f83ad1af46e7b1f1639d9fa0eb873dcbb5

Implement target_emit_ops

This patch implements compiling agent expressions to native code for
AArch64.  This allows us to compile conditions set on fast tracepoints.

The compiled function has the following prologue:

High *------------------------------------------------------*
     | LR                                                   |
     | FP                                                   | <- FP
     | x1  (ULONGEST *value)                                |
     | x0  (unsigned char *regs)                            |
Low  *------------------------------------------------------*

We save the function's argument on the stack as well as the return
address and the frame pointer.  We then set the current frame pointer to
point to the previous one.

The generated code for the expression will freely update the stack
pointer so we use the frame pointer to refer to `*value' and `*regs'.
`*value' needs to be accessed in the epilogue of the function, in order
to set it to whatever is on top of the stack.  `*regs' needs to be passed
down to the `gdb_agent_get_raw_reg' function with the `reg' operation.

gdb/gdbserver/ChangeLog:

	* linux-aarch64-low-.c: Include ax.h and tracepoint.h.
	(enum aarch64_opcodes) <RET>, <SUBS>, <AND>, <ORR>, <ORN>,
	<EOR>, <LSLV>, <LSRV>, <ASRV>, <SBFM>, <UBFM>, <CSINC>, <MUL>,
	<NOP>: New.
	(enum aarch64_condition_codes): New enum.
	(w0): New static global.
	(fp): Likewise.
	(lr): Likewise.
	(struct aarch64_memory_operand) <type>: New
	MEMORY_OPERAND_POSTINDEX type.
	(postindex_memory_operand): New helper function.
	(emit_ret): New function.
	(emit_load_store_pair): New function, factored out of emit_stp
	with support for MEMORY_OPERAND_POSTINDEX.
	(emit_stp): Rewrite using emit_load_store_pair.
	(emit_ldp): New function.
	(emit_load_store): Likewise.
	(emit_ldr): Mention post-index instruction in comment.
	(emit_ldrh): New function.
	(emit_ldrb): New function.
	(emit_ldrsw): Mention post-index instruction in comment.
	(emit_str): Likewise.
	(emit_subs): New function.
	(emit_cmp): Likewise.
	(emit_and): Likewise.
	(emit_orr): Likewise.
	(emit_orn): Likewise.
	(emit_eor): Likewise.
	(emit_mvn): Likewise.
	(emit_lslv): Likewise.
	(emit_lsrv): Likewise.
	(emit_asrv): Likewise.
	(emit_mul): Likewise.
	(emit_sbfm): Likewise.
	(emit_sbfx): Likewise.
	(emit_ubfm): Likewise.
	(emit_ubfx): Likewise.
	(emit_csinc): Likewise.
	(emit_cset): Likewise.
	(emit_nop): Likewise.
	(emit_ops_insns): New helper function.
	(emit_pop): Likewise.
	(emit_push): Likewise.
	(aarch64_emit_prologue): New function.
	(aarch64_emit_epilogue): Likewise.
	(aarch64_emit_add): Likewise.
	(aarch64_emit_sub): Likewise.
	(aarch64_emit_mul): Likewise.
	(aarch64_emit_lsh): Likewise.
	(aarch64_emit_rsh_signed): Likewise.
	(aarch64_emit_rsh_unsigned): Likewise.
	(aarch64_emit_ext): Likewise.
	(aarch64_emit_log_not): Likewise.
	(aarch64_emit_bit_and): Likewise.
	(aarch64_emit_bit_or): Likewise.
	(aarch64_emit_bit_xor): Likewise.
	(aarch64_emit_bit_not): Likewise.
	(aarch64_emit_equal): Likewise.
	(aarch64_emit_less_signed): Likewise.
	(aarch64_emit_less_unsigned): Likewise.
	(aarch64_emit_ref): Likewise.
	(aarch64_emit_if_goto): Likewise.
	(aarch64_emit_goto): Likewise.
	(aarch64_write_goto_address): Likewise.
	(aarch64_emit_const): Likewise.
	(aarch64_emit_call): Likewise.
	(aarch64_emit_reg): Likewise.
	(aarch64_emit_pop): Likewise.
	(aarch64_emit_stack_flush): Likewise.
	(aarch64_emit_zero_ext): Likewise.
	(aarch64_emit_swap): Likewise.
	(aarch64_emit_stack_adjust): Likewise.
	(aarch64_emit_int_call_1): Likewise.
	(aarch64_emit_void_call_2): Likewise.
	(aarch64_emit_eq_goto): Likewise.
	(aarch64_emit_ne_goto): Likewise.
	(aarch64_emit_lt_goto): Likewise.
	(aarch64_emit_le_goto): Likewise.
	(aarch64_emit_gt_goto): Likewise.
	(aarch64_emit_ge_got): Likewise.
	(aarch64_emit_ops_impl): New static global variable.
	(aarch64_emit_ops): New target function, return
	&aarch64_emit_ops_impl.
	(struct linux_target_ops): Install it.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Add a gdb.trace test for instruction relocation
@ 2015-09-21 15:19 sergiodj+buildbot
  2015-09-22  3:18 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-09-21 15:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4f51c22aca0d53526e65954b99d1ab3abfbb8bc8 ***

Author: Pierre Langlois <pierre.langlois@arm.com>
Branch: master
Commit: 4f51c22aca0d53526e65954b99d1ab3abfbb8bc8

Add a gdb.trace test for instruction relocation

This test case makes sure that relocating PC relative instructions does
not change their behaviors.  All PC relative AArch64 instructions are
covered.  While call and jump (32 bit relative) instructions are covered
on x86.

The test case creates a static array of function pointers for each
supported architecture.  Each function in this array tests a specific
instruction using inline assembly.  They all need to contain a symbol in
the form of 'set_point\[0-9\]+' and finish by either calling pass or
fail.  The number of 'set_pointN' needs to go from 0 to
(ARRAY_SIZE - 1).

The test will:
- look up the number of function pointers in the static array.
- set fast tracepoints on each 'set_point\[0-9\]+' symbol, one in each
  functions from 0 to (ARRAY_SIZE - 1).
- run the trace experiment and make sure the pass function is called for
  every function.

gdb/testsuite/ChangeLog:

	* gdb.arch/insn-reloc.c: New file.
	* gdb.arch/ftrace-insn-reloc.exp: New file.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Add a test case for fast tracepoints' locking mechanism
@ 2015-09-21 15:44 sergiodj+buildbot
  2015-09-22  6:19 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-09-21 15:44 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 06da0f77c2a447348127e072e34bf541597154a2 ***

Author: Pierre Langlois <pierre.langlois@arm.com>
Branch: master
Commit: 06da0f77c2a447348127e072e34bf541597154a2

Add a test case for fast tracepoints' locking mechanism

When installing a fast tracepoint, we create a jump pad with a
spin-lock.  This way, only one thread can collect a given tracepoint at
any time.  This test case checks that this lock actually works as
expected.

This test works by creating a function which overrides the in-process
agent library's gdb_collect function.  On start up, GDBserver will ask
GDB with the 'qSymbol' packet about symbols present in the inferior.
GDB will reply with the gdb_agent_gdb_collect function from the test
case instead of the one from the agent.

gdb/testsuite/ChangeLog:

	* gdb.trace/ftrace-lock.c: New file.
	* gdb.trace/ftrace-lock.exp: New file.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Add NEWS entry for fast tracepoint support on aarch64-linux
@ 2015-09-21 15:50 sergiodj+buildbot
  2015-09-22  6:36 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-09-21 15:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4d9d419e0e0512c301eb1ffcb793828451653024 ***

Author: Pierre Langlois <pierre.langlois@arm.com>
Branch: master
Commit: 4d9d419e0e0512c301eb1ffcb793828451653024

Add NEWS entry for fast tracepoint support on aarch64-linux

Here is a NEWS entry for this series:

gdb/ChangeLog:

	* NEWS: Mention support for fast tracepoints on aarch64-linux.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Enable fast tracepoint tests
@ 2015-09-21 16:34 sergiodj+buildbot
  2015-09-22  2:10 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-09-21 16:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7041adf41fc291659fa4d102b50539946403f97e ***

Author: Pierre Langlois <pierre.langlois@arm.com>
Branch: master
Commit: 7041adf41fc291659fa4d102b50539946403f97e

Enable fast tracepoint tests

gdb/testsuite/ChangeLog:

	* gdb.trace/change-loc.h (func4) [__aarch64__]: Add a nop
	instruction.
	* gdb.trace/pendshr1.c (pendfunc): Likewise.
	* gdb.trace/pendshr2.c (pendfunc2): Likewise.
	* gdb.trace/range-stepping.c: Likewise.
	* gdb.trace/trace-break.c: Likewise.
	* gdb.trace/trace-mt.c (thread_function): Likewise.
	* gdb.trace/ftrace.c (marker): Likewise.
	* gdb.trace/trace-condition.c (marker): Likewise.
	* gdb.trace/ftrace.exp: Enable ftrace test if is_aarch64_target.
	* gdb.trace/trace-condition.exp: Set pcreg to "\$pc" if
	is_aarch64_target.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Change ch_type in Elf64_External_Chdr to 4 bytes
@ 2015-09-21 18:09 sergiodj+buildbot
  2015-09-22  9:26 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-09-21 18:09 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7f7a1bce250bc286d23a4b895d684748bec03a71 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 7f7a1bce250bc286d23a4b895d684748bec03a71

Change ch_type in Elf64_External_Chdr to 4 bytes

The ch_type field in Elf64_External_Chdr is 4 bytes, followed by a
4-byte padding.  This change doesn't introduce any functional change
since only the lower 32 bits of the ch_type field are used.

	* external.h (Elf64_External_Chdr): Change ch_type to 4 bytes
	and add ch_reserved.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Add two missing consts
@ 2015-09-22  0:01 sergiodj+buildbot
  2015-09-22 10:05 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-09-22  0:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT acaa662f29836ce4d4c3a0abc2132f285f9df585 ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: acaa662f29836ce4d4c3a0abc2132f285f9df585

Add two missing consts

Two missing consts, found while doing cxx-conversion work.  We end up
with a char*, even though we pass a const char* to strstr.  I am pushing
this as obvious.

gdb/ChangeLog:

	* cli/cli-setshow.c (cmd_show_list): Constify a variable.
	* linespec.c (linespec_lexer_lex_string): Same.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] opcodes/ppc-opc.c: Add dscr and ctrl SPR mnemonics
@ 2015-09-22  7:22 sergiodj+buildbot
  2015-09-22 15:29 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-09-22  7:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6dca4fd141fd0b9fe0ea662295833b8ed43cb4e8 ***

Author: Anton Blanchard <anton@samba.org>
Branch: master
Commit: 6dca4fd141fd0b9fe0ea662295833b8ed43cb4e8

opcodes/ppc-opc.c: Add dscr and ctrl SPR mnemonics

opcodes/
	* ppc-opc.c (powerpc_opcodes): Add mfdscr, mfctrl, mtdscr and mtctrl.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Solaris PIE support
@ 2015-09-22 10:26 sergiodj+buildbot
  2015-09-22 15:59 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-09-22 10:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5c383f026242d25a3c21fdfda42e5ca218b346c8 ***

Author: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
Branch: master
Commit: 5c383f026242d25a3c21fdfda42e5ca218b346c8

Solaris PIE support

	include/elf:
	* common.h (DF_1_STUB, DF_1_PIE): Define.

	ld:
	* emulparams/solaris2.sh (GENERATE_PIE_SCRIPT): Set to yes.

	* emultempl/elf32.em: Include ldlex.h.
	(gld${EMULATION_NAME}_handle_option) [GENERATE_PIE_SCRIPT]
	<OPTION_PIE>: Set DF_1_PIE.

	binutils:
	* readelf.c (process_dynamic_section): Handle DF_1_STUB, DF_1_PIE.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Enhance the RX disassembler to detect and report bad instructions.
@ 2015-09-22 17:51 sergiodj+buildbot
  2015-09-23  3:36 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-09-22 17:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f04265eceb78a33e452faa8727562e96af374f39 ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: f04265eceb78a33e452faa8727562e96af374f39

Enhance the RX disassembler to detect and report bad instructions.

opcode	* rx.h (enum RX_Size): Add RX_Bad_Size entry.

opcodes	* rx-decode.opc (bwl): Use RX_Bad_Size.
	(sbwl): Likewise.
	(ubwl): Likewise.  Rename to ubw.
	(uBWL): Rename to uBW.
	Replace all references to uBWL with uBW.
	* rx-decode.c: Regenerate.
	* rx-dis.c (size_names): Add entry for RX_Bad_Size.
	(opsize_names): Likewise.
	(print_insn_rx): Detect and report RX_Bad_Size.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [Ada] Fix handling of array renamings
@ 2015-09-23 21:13 sergiodj+buildbot
  2015-09-24  0:51 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-09-23 21:13 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e6c2c623f7736175e52fce2b61aab60c60eccdf5 ***

Author: Pierre-Marie de Rodat <derodat@adacore.com>
Branch: master
Commit: e6c2c623f7736175e52fce2b61aab60c60eccdf5

[Ada] Fix handling of array renamings

Compilers can materialize renamings of arrays (or of accesses to arrays)
in Ada into variables whose types are references to the actual array
types.  Before this change, trying to use such an array renaming yielded
an error in GDB:

    (gdb) print my_array(1)
    cannot subscript or call a record
    (gdb) print my_array_ptr(1)
    cannot subscript or call something of type `(null)'

This behavior comes from bad handling for array renamings, in particular
the OP_FUNCALL expression operator handling from ada-lang.c
(ada_evaluate_subexp): in one place we turn the reference into a
pointer, but the code that follows expect the value to be an array.

This patch fixes how we handle references in call/subscript evaluation
so that we turn these references into the actual array values instead of
pointers to them.

gdb/ChangeLog:

	* ada-lang.c (ada_evaluate_subexp) <OP_FUNCALL>: When the input
	value is a reference, actually dereference it in order to get
	the underlying value.

gdb/testsuite/ChangeLog:

	* gdb.ada/array_ptr_renaming.exp: New testcase.
	* gdb.ada/array_ptr_renaming/foo.adb: New file.
	* gdb.ada/array_ptr_renaming/pack.ads: New file.

Tested on x86_64-linux, no regression.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Allow any size enum in gdb.cp/var-tag.exp.
@ 2015-09-24  1:12 sergiodj+buildbot
  2015-09-24 23:23 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-09-24  1:12 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 938d3bf25b2f5bc1a9d955d86070e8bbee127f52 ***

Author: Sandra Loosemore <sandra@codesourcery.com>
Branch: master
Commit: 938d3bf25b2f5bc1a9d955d86070e8bbee127f52

Allow any size enum in gdb.cp/var-tag.exp.

2015-09-23 Sandra Loosemore <sandra@codesourcery.com>

	gdb/testsuite/
	* gdb.cp/var-tag.exp (do_global_tests): Generalize opt_underlying
	to allow any size enum.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [FT32] Implement pointer to address conversion method.
@ 2015-09-24 23:46 sergiodj+buildbot
  2015-09-25  0:14 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-09-24 23:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 623fb77545da1272c7602cd51a4c187b66c366c8 ***

Author: jamesbowman <jamesb@excamera.com>
Branch: master
Commit: 623fb77545da1272c7602cd51a4c187b66c366c8

[FT32] Implement pointer to address conversion method.

FT32 is a Harvard architecture with two address spaces -- RAM and flash.
The patch properly implements the pointer to address conversion method.
There are some other small fixes to handle address spaces.

gdb/
	* ft32-tdep.c (ft32_register_type): Return gdbarch_tdep
	(gdbarch)->pc_type instead of builtin_func_ptr.
	(ft32_pointer_to_address): New function.
	(ft32_address_class_type_flags): New function.
	(ft32_address_class_type_flags_to_name): New function.
	(ft32_address_class_name_to_type_flags): New function.
	(ft32_gdbarch_init): Set tdep->pc_type.  Call
	set_gdbarch_pointer_to_address,
	set_gdbarch_address_class_type_flags
	set_gdbarch_address_class_name_to_type_flags,
	and set_gdbarch_address_class_type_flags_to_name.
	* ft32-tdep.h (struct gdbarch_tdep) <pc_type>: New field.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Test case, disassembler not showing RIMM literals correctly #14
@ 2015-09-25  0:05 sergiodj+buildbot
  2015-09-25  5:10 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-09-25  0:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c7c9216298b3c8e380d348f8be6e03a48dbe5918 ***

Author: jamesbowman <jamesb@excamera.com>
Branch: master
Commit: c7c9216298b3c8e380d348f8be6e03a48dbe5918

Test case, disassembler not showing RIMM literals correctly #14


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Accidentally added file. Removed it.
@ 2015-09-25  0:35 sergiodj+buildbot
  2015-09-25 14:57 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-09-25  0:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6e15a7d88b346cd5dd6ea76d86121d29932c3c8d ***

Author: jamesbowman <jamesb@excamera.com>
Branch: master
Commit: 6e15a7d88b346cd5dd6ea76d86121d29932c3c8d

Accidentally added file. Removed it.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Generalize enum regexp in gdb.cp/classes.exp.
@ 2015-09-25  2:06 sergiodj+buildbot
  2015-09-25 15:08 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-09-25  2:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9720e656055e5b906649c9f506a6de5a31337d07 ***

Author: Sandra Loosemore <sandra@codesourcery.com>
Branch: master
Commit: 9720e656055e5b906649c9f506a6de5a31337d07

Generalize enum regexp in gdb.cp/classes.exp.

2015-09-24 Sandra Loosemore <sandra@codesourcery.com>

	gdb/testsuite/
	* gdb.cp/classes.exp (test_enums): Generalize regexp to allow
	short or char as base type.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Correct the generation of OR1K pc-relative relocations.
@ 2015-09-25 15:17 sergiodj+buildbot
  2015-09-25 18:30 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-09-25 15:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8a9e7a9121490a8c64d8c17f5be510e43104f6d9 ***

Author: Peter Zotov <whitequark@whitequark.org>
Branch: master
Commit: 8a9e7a9121490a8c64d8c17f5be510e43104f6d9

Correct the generation of OR1K pc-relative relocations.

gas	PR ld/18759
	* config/tc-or1k.c (tc_gen_reloc): Correct computation of PC
	relative relocs.
	* config/tc-or1k.h (GAS_CGEN_PRCEL_R_TYPE): Delete.

bfd	* elf32-or1k.c (R_OR1K_32_PCREL): Set pcrel_offset to TRUE.
	(R_OR1K_16_PCREL): Likewise.
	(R_OR1K_8_PCREL): Likewise.

ld/tests * ld-elf/eh-frame-hdr: Expect to pass on the or1k-linux target.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Add casts to memory allocation related calls
@ 2015-09-25 18:49 sergiodj+buildbot
  2015-09-25 19:20 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-09-25 18:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 224c3ddb89a43bf8db06c373d4ff429477833c0f ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: 224c3ddb89a43bf8db06c373d4ff429477833c0f

Add casts to memory allocation related calls

Most allocation functions (if not all) return a void* pointing to the
allocated memory.  In C++, we need to add an explicit cast when
assigning the result to a pointer to another type (which is the case
more often than not).

The content of this patch is taken from Pedro's branch, from commit
"(mostly) auto-generated patch to insert casts needed for C++".  I
validated that the changes make sense and manually reflowed the code to
make it respect the coding style.  I also found multiple places where I
could use XNEW/XNEWVEC/XRESIZEVEC/etc.

Thanks a lot to whoever did that automated script to insert casts, doing
it completely by hand would have taken a ridiculous amount of time.

Only files built on x86 with --enable-targets=all are modified.  This
means that all other -nat.c files are untouched and will have to be
dealt with later by using appropiate compilers.  Or maybe we can try to
build them with a regular g++ just to know where to add casts, I don't
know.

I built-tested this with --enable-targets=all and reg-tested.

Here's the changelog entry, which was not too bad to make despite the
size, thanks to David Malcom's script.  I fixed some bits by hand, but
there might be some wrong parts left (hopefully not).

gdb/ChangeLog:

	* aarch64-linux-tdep.c (aarch64_stap_parse_special_token): Add cast
	to allocation result assignment.
	* ada-exp.y (write_object_renaming): Likewise.
	(write_ambiguous_var): Likewise.
	(ada_nget_field_index): Likewise.
	(write_var_or_type): Likewise.
	* ada-lang.c (ada_decode_symbol): Likewise.
	(ada_value_assign): Likewise.
	(value_pointer): Likewise.
	(cache_symbol): Likewise.
	(add_nonlocal_symbols): Likewise.
	(ada_name_for_lookup): Likewise.
	(symbol_completion_add): Likewise.
	(ada_to_fixed_type_1): Likewise.
	(ada_get_next_arg): Likewise.
	(defns_collected): Likewise.
	* ada-lex.l (processId): Likewise.
	(processString): Likewise.
	* ada-tasks.c (read_known_tasks_array): Likewise.
	(read_known_tasks_list): Likewise.
	* ada-typeprint.c (decoded_type_name): Likewise.
	* addrmap.c (addrmap_mutable_create_fixed): Likewise.
	* amd64-tdep.c (amd64_push_arguments): Likewise.
	(amd64_displaced_step_copy_insn): Likewise.
	(amd64_classify_insn_at): Likewise.
	(amd64_relocate_instruction): Likewise.
	* amd64obsd-tdep.c (amd64obsd_sigtramp_p): Likewise.
	* arch-utils.c (simple_displaced_step_copy_insn): Likewise.
	(initialize_current_architecture): Likewise.
	* arm-linux-tdep.c (arm_stap_parse_special_token): Likewise.
	* arm-symbian-tdep.c (arm_symbian_osabi_sniffer): Likewise.
	* arm-tdep.c (arm_exidx_new_objfile): Likewise.
	(arm_push_dummy_call): Likewise.
	(extend_buffer_earlier): Likewise.
	(arm_adjust_breakpoint_address): Likewise.
	(arm_skip_stub): Likewise.
	* auto-load.c (filename_is_in_pattern): Likewise.
	(maybe_add_script_file): Likewise.
	(maybe_add_script_text): Likewise.
	(auto_load_objfile_script_1): Likewise.
	* auxv.c (ld_so_xfer_auxv): Likewise.
	* ax-general.c (new_agent_expr): Likewise.
	(grow_expr): Likewise.
	(ax_reg_mask): Likewise.
	* bcache.c (bcache_full): Likewise.
	* breakpoint.c (program_breakpoint_here_p): Likewise.
	* btrace.c (parse_xml_raw): Likewise.
	* build-id.c (build_id_to_debug_bfd): Likewise.
	* buildsym.c (end_symtab_with_blockvector): Likewise.
	* c-exp.y (string_exp): Likewise.
	(qualified_name): Likewise.
	(write_destructor_name): Likewise.
	(operator_stoken): Likewise.
	(parse_number): Likewise.
	(scan_macro_expansion): Likewise.
	(yylex): Likewise.
	(c_print_token): Likewise.
	* c-lang.c (c_get_string): Likewise.
	(emit_numeric_character): Likewise.
	* charset.c (wchar_iterate): Likewise.
	* cli/cli-cmds.c (complete_command): Likewise.
	(make_command): Likewise.
	* cli/cli-dump.c (restore_section_callback): Likewise.
	(restore_binary_file): Likewise.
	* cli/cli-interp.c (cli_interpreter_exec): Likewise.
	* cli/cli-script.c (execute_control_command): Likewise.
	* cli/cli-setshow.c (do_set_command): Likewise.
	* coff-pe-read.c (add_pe_forwarded_sym): Likewise.
	(read_pe_exported_syms): Likewise.
	* coffread.c (coff_read_struct_type): Likewise.
	(coff_read_enum_type): Likewise.
	* common/btrace-common.c (btrace_data_append): Likewise.
	* common/buffer.c (buffer_grow): Likewise.
	* common/filestuff.c (gdb_fopen_cloexec): Likewise.
	* common/format.c (parse_format_string): Likewise.
	* common/gdb_vecs.c (delim_string_to_char_ptr_vec_append): Likewise.
	* common/xml-utils.c (xml_escape_text): Likewise.
	* compile/compile-object-load.c (copy_sections): Likewise.
	(compile_object_load): Likewise.
	* compile/compile-object-run.c (compile_object_run): Likewise.
	* completer.c (filename_completer): Likewise.
	* corefile.c (read_memory_typed_address): Likewise.
	(write_memory_unsigned_integer): Likewise.
	(write_memory_signed_integer): Likewise.
	(complete_set_gnutarget): Likewise.
	* corelow.c (get_core_register_section): Likewise.
	* cp-name-parser.y (d_grab): Likewise.
	(allocate_info): Likewise.
	(cp_new_demangle_parse_info): Likewise.
	* cp-namespace.c (cp_scan_for_anonymous_namespaces): Likewise.
	(cp_lookup_symbol_in_namespace): Likewise.
	(lookup_namespace_scope): Likewise.
	(find_symbol_in_baseclass): Likewise.
	(cp_lookup_nested_symbol): Likewise.
	(cp_lookup_transparent_type_loop): Likewise.
	* cp-support.c (copy_string_to_obstack): Likewise.
	(make_symbol_overload_list): Likewise.
	(make_symbol_overload_list_namespace): Likewise.
	(make_symbol_overload_list_adl_namespace): Likewise.
	(first_component_command): Likewise.
	* cp-valprint.c (cp_print_value): Likewise.
	* ctf.c (ctf_xfer_partial): Likewise.
	* d-exp.y (StringExp): Likewise.
	* d-namespace.c (d_lookup_symbol_in_module): Likewise.
	(lookup_module_scope): Likewise.
	(find_symbol_in_baseclass): Likewise.
	(d_lookup_nested_symbol): Likewise.
	* dbxread.c (find_stab_function_addr): Likewise.
	(read_dbx_symtab): Likewise.
	(dbx_end_psymtab): Likewise.
	(cp_set_block_scope): Likewise.
	* dcache.c (dcache_alloc): Likewise.
	* demangle.c (_initialize_demangler): Likewise.
	* dicos-tdep.c (dicos_load_module_p): Likewise.
	* dictionary.c (dict_create_hashed_expandable): Likewise.
	(dict_create_linear_expandable): Likewise.
	(expand_hashtable): Likewise.
	(add_symbol_linear_expandable): Likewise.
	* dwarf2-frame.c (add_cie): Likewise.
	(add_fde): Likewise.
	(dwarf2_build_frame_info): Likewise.
	* dwarf2expr.c (dwarf_expr_grow_stack): Likewise.
	(dwarf_expr_fetch_address): Likewise.
	(add_piece): Likewise.
	(execute_stack_op): Likewise.
	* dwarf2loc.c (chain_candidate): Likewise.
	(dwarf_entry_parameter_to_value): Likewise.
	(read_pieced_value): Likewise.
	(write_pieced_value): Likewise.
	* dwarf2read.c (dwarf2_read_section): Likewise.
	(add_type_unit): Likewise.
	(read_comp_units_from_section): Likewise.
	(fixup_go_packaging): Likewise.
	(dwarf2_compute_name): Likewise.
	(dwarf2_physname): Likewise.
	(create_dwo_unit_in_dwp_v1): Likewise.
	(create_dwo_unit_in_dwp_v2): Likewise.
	(read_func_scope): Likewise.
	(read_call_site_scope): Likewise.
	(dwarf2_attach_fields_to_type): Likewise.
	(process_structure_scope): Likewise.
	(mark_common_block_symbol_computed): Likewise.
	(read_common_block): Likewise.
	(abbrev_table_read_table): Likewise.
	(guess_partial_die_structure_name): Likewise.
	(fixup_partial_die): Likewise.
	(add_file_name): Likewise.
	(dwarf2_const_value_data): Likewise.
	(dwarf2_const_value_attr): Likewise.
	(build_error_marker_type): Likewise.
	(guess_full_die_structure_name): Likewise.
	(anonymous_struct_prefix): Likewise.
	(typename_concat): Likewise.
	(dwarf2_canonicalize_name): Likewise.
	(dwarf2_name): Likewise.
	(write_constant_as_bytes): Likewise.
	(dwarf2_fetch_constant_bytes): Likewise.
	(copy_string): Likewise.
	(parse_macro_definition): Likewise.
	* elfread.c (elf_symfile_segments): Likewise.
	(elf_rel_plt_read): Likewise.
	(elf_gnu_ifunc_resolve_by_cache): Likewise.
	(elf_gnu_ifunc_resolve_by_got): Likewise.
	(elf_read_minimal_symbols): Likewise.
	(elf_gnu_ifunc_record_cache): Likewise.
	* event-top.c (top_level_prompt): Likewise.
	(command_line_handler): Likewise.
	* exec.c (resize_section_table): Likewise.
	* expprint.c (print_subexp_standard): Likewise.
	* fbsd-tdep.c (fbsd_collect_regset_section_cb): Likewise.
	* findcmd.c (parse_find_args): Likewise.
	* findvar.c (address_from_register): Likewise.
	* frame.c (get_prev_frame_always): Likewise.
	* gdb_bfd.c (gdb_bfd_ref): Likewise.
	(get_section_descriptor): Likewise.
	* gdb_obstack.c (obconcat): Likewise.
	(obstack_strdup): Likewise.
	* gdbtypes.c (lookup_function_type_with_arguments): Likewise.
	(create_set_type): Likewise.
	(lookup_unsigned_typename): Likewise.
	(lookup_signed_typename): Likewise.
	(resolve_dynamic_union): Likewise.
	(resolve_dynamic_struct): Likewise.
	(add_dyn_prop): Likewise.
	(copy_dynamic_prop_list): Likewise.
	(arch_flags_type): Likewise.
	(append_composite_type_field_raw): Likewise.
	* gdbtypes.h (INIT_FUNC_SPECIFIC): Likewise.
	* gnu-v3-abi.c (gnuv3_rtti_type): Likewise.
	* go-exp.y (string_exp): Likewise.
	* go-lang.c (go_demangle): Likewise.
	* guile/guile.c (compute_scheme_string): Likewise.
	* guile/scm-cmd.c (gdbscm_parse_command_name): Likewise.
	(gdbscm_canonicalize_command_name): Likewise.
	* guile/scm-ports.c (ioscm_init_stdio_buffers): Likewise.
	(ioscm_init_memory_port): Likewise.
	(ioscm_reinit_memory_port): Likewise.
	* guile/scm-utils.c (gdbscm_gc_xstrdup): Likewise.
	(gdbscm_gc_dup_argv): Likewise.
	* h8300-tdep.c (h8300_push_dummy_call): Likewise.
	* hppa-tdep.c (internalize_unwinds): Likewise.
	(read_unwind_info): Likewise.
	* i386-cygwin-tdep.c (core_process_module_section): Likewise.
	(windows_core_xfer_shared_libraries): Likewise.
	* i386-tdep.c (i386_displaced_step_copy_insn): Likewise.
	(i386_stap_parse_special_token_triplet): Likewise.
	(i386_stap_parse_special_token_three_arg_disp): Likewise.
	* i386obsd-tdep.c (i386obsd_sigtramp_p): Likewise.
	* inf-child.c (inf_child_fileio_readlink): Likewise.
	* inf-ptrace.c (inf_ptrace_fetch_register): Likewise.
	(inf_ptrace_store_register): Likewise.
	* infrun.c (follow_exec): Likewise.
	(displaced_step_prepare_throw): Likewise.
	(save_stop_context): Likewise.
	(save_infcall_suspend_state): Likewise.
	* jit.c (jit_read_descriptor): Likewise.
	(jit_read_code_entry): Likewise.
	(jit_symtab_line_mapping_add_impl): Likewise.
	(finalize_symtab): Likewise.
	(jit_unwind_reg_get_impl): Likewise.
	* jv-exp.y (QualifiedName): Likewise.
	* jv-lang.c (get_java_utf8_name): Likewise.
	(type_from_class): Likewise.
	(java_demangle_type_signature): Likewise.
	(java_class_name_from_physname): Likewise.
	* jv-typeprint.c (java_type_print_base): Likewise.
	* jv-valprint.c (java_value_print): Likewise.
	* language.c (add_language): Likewise.
	* linespec.c (add_sal_to_sals_basic): Likewise.
	(add_sal_to_sals): Likewise.
	(decode_objc): Likewise.
	(find_linespec_symbols): Likewise.
	* linux-fork.c (fork_save_infrun_state): Likewise.
	* linux-nat.c (linux_nat_detach): Likewise.
	(linux_nat_fileio_readlink): Likewise.
	* linux-record.c (record_linux_sockaddr): Likewise.
	(record_linux_msghdr): Likewise.
	(Do): Likewise.
	* linux-tdep.c (linux_core_info_proc_mappings): Likewise.
	(linux_collect_regset_section_cb): Likewise.
	(linux_get_siginfo_data): Likewise.
	* linux-thread-db.c (try_thread_db_load_from_pdir_1): Likewise.
	(try_thread_db_load_from_dir): Likewise.
	(thread_db_load_search): Likewise.
	(info_auto_load_libthread_db): Likewise.
	* m32c-tdep.c (m32c_m16c_address_to_pointer): Likewise.
	(m32c_m16c_pointer_to_address): Likewise.
	* m68hc11-tdep.c (m68hc11_pseudo_register_write): Likewise.
	* m68k-tdep.c (m68k_get_longjmp_target): Likewise.
	* machoread.c (macho_check_dsym): Likewise.
	* macroexp.c (resize_buffer): Likewise.
	(gather_arguments): Likewise.
	(maybe_expand): Likewise.
	* macrotab.c (new_macro_key): Likewise.
	(new_source_file): Likewise.
	(new_macro_definition): Likewise.
	* mdebugread.c (parse_symbol): Likewise.
	(parse_type): Likewise.
	(parse_partial_symbols): Likewise.
	(psymtab_to_symtab_1): Likewise.
	* mem-break.c (default_memory_insert_breakpoint): Likewise.
	* mi/mi-cmd-break.c (mi_argv_to_format): Likewise.
	* mi/mi-main.c (mi_cmd_data_read_memory): Likewise.
	(mi_cmd_data_read_memory_bytes): Likewise.
	(mi_cmd_data_write_memory_bytes): Likewise.
	(mi_cmd_trace_frame_collected): Likewise.
	* mi/mi-parse.c (mi_parse_argv): Likewise.
	(mi_parse): Likewise.
	* minidebug.c (lzma_open): Likewise.
	(lzma_pread): Likewise.
	* mips-tdep.c (mips_read_fp_register_single): Likewise.
	(mips_print_fp_register): Likewise.
	* mipsnbsd-tdep.c (mipsnbsd_get_longjmp_target): Likewise.
	* mipsread.c (read_alphacoff_dynamic_symtab): Likewise.
	* mt-tdep.c (mt_register_name): Likewise.
	(mt_registers_info): Likewise.
	(mt_push_dummy_call): Likewise.
	* namespace.c (add_using_directive): Likewise.
	* nat/linux-btrace.c (perf_event_read): Likewise.
	(linux_enable_bts): Likewise.
	* nat/linux-osdata.c (linux_common_core_of_thread): Likewise.
	* nat/linux-ptrace.c (linux_ptrace_test_ret_to_nx): Likewise.
	* nto-tdep.c (nto_find_and_open_solib): Likewise.
	(nto_parse_redirection): Likewise.
	* objc-lang.c (objc_demangle): Likewise.
	(find_methods): Likewise.
	* objfiles.c (get_objfile_bfd_data): Likewise.
	(set_objfile_main_name): Likewise.
	(allocate_objfile): Likewise.
	(objfile_relocate): Likewise.
	(update_section_map): Likewise.
	* osabi.c (generic_elf_osabi_sniff_abi_tag_sections): Likewise.
	* p-exp.y (exp): Likewise.
	(yylex): Likewise.
	* p-valprint.c (pascal_object_print_value): Likewise.
	* parse.c (initialize_expout): Likewise.
	(mark_completion_tag): Likewise.
	(copy_name): Likewise.
	(parse_float): Likewise.
	(type_stack_reserve): Likewise.
	* ppc-linux-tdep.c (ppc_stap_parse_special_token): Likewise.
	(ppu2spu_prev_register): Likewise.
	* ppc-ravenscar-thread.c (supply_register_at_address): Likewise.
	* printcmd.c (printf_wide_c_string): Likewise.
	(printf_pointer): Likewise.
	* probe.c (parse_probes): Likewise.
	* python/py-cmd.c (gdbpy_parse_command_name): Likewise.
	(cmdpy_init): Likewise.
	* python/py-gdb-readline.c (gdbpy_readline_wrapper): Likewise.
	* python/py-symtab.c (set_sal): Likewise.
	* python/py-unwind.c (pyuw_sniffer): Likewise.
	* python/python.c (python_interactive_command): Likewise.
	(compute_python_string): Likewise.
	* ravenscar-thread.c (get_running_thread_id): Likewise.
	* record-full.c (record_full_exec_insn): Likewise.
	(record_full_core_open_1): Likewise.
	* regcache.c (regcache_raw_read_signed): Likewise.
	(regcache_raw_read_unsigned): Likewise.
	(regcache_cooked_read_signed): Likewise.
	(regcache_cooked_read_unsigned): Likewise.
	* remote-fileio.c (remote_fileio_func_open): Likewise.
	(remote_fileio_func_rename): Likewise.
	(remote_fileio_func_unlink): Likewise.
	(remote_fileio_func_stat): Likewise.
	(remote_fileio_func_system): Likewise.
	* remote-mips.c (mips_xfer_memory): Likewise.
	(mips_load_srec): Likewise.
	(pmon_end_download): Likewise.
	* remote.c (new_remote_state): Likewise.
	(map_regcache_remote_table): Likewise.
	(remote_register_number_and_offset): Likewise.
	(init_remote_state): Likewise.
	(get_memory_packet_size): Likewise.
	(remote_pass_signals): Likewise.
	(remote_program_signals): Likewise.
	(remote_start_remote): Likewise.
	(remote_check_symbols): Likewise.
	(remote_query_supported): Likewise.
	(extended_remote_attach): Likewise.
	(process_g_packet): Likewise.
	(store_registers_using_G): Likewise.
	(putpkt_binary): Likewise.
	(read_frame): Likewise.
	(compare_sections_command): Likewise.
	(remote_hostio_pread): Likewise.
	(remote_hostio_readlink): Likewise.
	(remote_file_put): Likewise.
	(remote_file_get): Likewise.
	(remote_pid_to_exec_file): Likewise.
	(_initialize_remote): Likewise.
	* rs6000-aix-tdep.c (rs6000_aix_ld_info_to_xml): Likewise.
	(rs6000_aix_core_xfer_shared_libraries_aix): Likewise.
	* rs6000-tdep.c (ppc_displaced_step_copy_insn): Likewise.
	(bfd_uses_spe_extensions): Likewise.
	* s390-linux-tdep.c (s390_displaced_step_copy_insn): Likewise.
	* score-tdep.c (score7_malloc_and_get_memblock): Likewise.
	* solib-dsbt.c (decode_loadmap): Likewise.
	(fetch_loadmap): Likewise.
	(scan_dyntag): Likewise.
	(enable_break): Likewise.
	(dsbt_relocate_main_executable): Likewise.
	* solib-frv.c (fetch_loadmap): Likewise.
	(enable_break2): Likewise.
	(frv_relocate_main_executable): Likewise.
	* solib-spu.c (spu_relocate_main_executable): Likewise.
	(spu_bfd_open): Likewise.
	* solib-svr4.c (lm_info_read): Likewise.
	(read_program_header): Likewise.
	(find_program_interpreter): Likewise.
	(scan_dyntag): Likewise.
	(elf_locate_base): Likewise.
	(open_symbol_file_object): Likewise.
	(read_program_headers_from_bfd): Likewise.
	(svr4_relocate_main_executable): Likewise.
	* solib-target.c (solib_target_relocate_section_addresses): Likewise.
	* solib.c (solib_find_1): Likewise.
	(exec_file_find): Likewise.
	(solib_find): Likewise.
	* source.c (openp): Likewise.
	(print_source_lines_base): Likewise.
	(forward_search_command): Likewise.
	* sparc-ravenscar-thread.c (supply_register_at_address): Likewise.
	* spu-tdep.c (spu2ppu_prev_register): Likewise.
	(spu_get_overlay_table): Likewise.
	* stabsread.c (patch_block_stabs): Likewise.
	(define_symbol): Likewise.
	(again:): Likewise.
	(read_member_functions): Likewise.
	(read_one_struct_field): Likewise.
	(read_enum_type): Likewise.
	(common_block_start): Likewise.
	* stack.c (read_frame_arg): Likewise.
	(backtrace_command): Likewise.
	* stap-probe.c (stap_parse_register_operand): Likewise.
	* symfile.c (syms_from_objfile_1): Likewise.
	(find_separate_debug_file): Likewise.
	(load_command): Likewise.
	(load_progress): Likewise.
	(load_section_callback): Likewise.
	(reread_symbols): Likewise.
	(add_filename_language): Likewise.
	(allocate_compunit_symtab): Likewise.
	(read_target_long_array): Likewise.
	(simple_read_overlay_table): Likewise.
	* symtab.c (symbol_set_names): Likewise.
	(resize_symbol_cache): Likewise.
	(rbreak_command): Likewise.
	(completion_list_add_name): Likewise.
	(completion_list_objc_symbol): Likewise.
	(add_filename_to_list): Likewise.
	* target-descriptions.c (maint_print_c_tdesc_cmd): Likewise.
	* target-memory.c (target_write_memory_blocks): Likewise.
	* target.c (target_read_string): Likewise.
	(read_whatever_is_readable): Likewise.
	(target_read_alloc_1): Likewise.
	(simple_search_memory): Likewise.
	(target_fileio_read_alloc_1): Likewise.
	* tilegx-tdep.c (tilegx_push_dummy_call): Likewise.
	* top.c (command_line_input): Likewise.
	* tracefile-tfile.c (tfile_fetch_registers): Likewise.
	* tracefile.c (tracefile_fetch_registers): Likewise.
	* tracepoint.c (add_memrange): Likewise.
	(init_collection_list): Likewise.
	(add_aexpr): Likewise.
	(trace_dump_actions): Likewise.
	(parse_trace_status): Likewise.
	(parse_tracepoint_definition): Likewise.
	(parse_tsv_definition): Likewise.
	(parse_static_tracepoint_marker_definition): Likewise.
	* tui/tui-file.c (tui_sfileopen): Likewise.
	(tui_file_adjust_strbuf): Likewise.
	* tui/tui-io.c (tui_expand_tabs): Likewise.
	* tui/tui-source.c (tui_set_source_content): Likewise.
	* typeprint.c (find_global_typedef): Likewise.
	* ui-file.c (do_ui_file_xstrdup): Likewise.
	(ui_file_obsavestring): Likewise.
	(mem_file_write): Likewise.
	* utils.c (make_hex_string): Likewise.
	(get_regcomp_error): Likewise.
	(puts_filtered_tabular): Likewise.
	(gdb_realpath_keepfile): Likewise.
	(ldirname): Likewise.
	(gdb_bfd_errmsg): Likewise.
	(substitute_path_component): Likewise.
	* valops.c (search_struct_method): Likewise.
	(find_oload_champ_namespace_loop): Likewise.
	* valprint.c (print_decimal_chars): Likewise.
	(read_string): Likewise.
	(generic_emit_char): Likewise.
	* varobj.c (varobj_delete): Likewise.
	(varobj_value_get_print_value): Likewise.
	* vaxobsd-tdep.c (vaxobsd_sigtramp_sniffer): Likewise.
	* windows-tdep.c (display_one_tib): Likewise.
	* xcoffread.c (read_xcoff_symtab): Likewise.
	(process_xcoff_symbol): Likewise.
	(swap_sym): Likewise.
	(scan_xcoff_symtab): Likewise.
	(xcoff_initial_scan): Likewise.
	* xml-support.c (gdb_xml_end_element): Likewise.
	(xml_process_xincludes): Likewise.
	(xml_fetch_content_from_file): Likewise.
	* xml-syscall.c (xml_list_of_syscalls): Likewise.
	* xstormy16-tdep.c (xstormy16_push_dummy_call): Likewise.

gdb/gdbserver/ChangeLog:

	* ax.c (gdb_parse_agent_expr): Add cast to allocation result
	assignment.
	(gdb_unparse_agent_expr): Likewise.
	* hostio.c (require_data): Likewise.
	(handle_pread): Likewise.
	* linux-low.c (disable_regset): Likewise.
	(fetch_register): Likewise.
	(store_register): Likewise.
	(get_dynamic): Likewise.
	(linux_qxfer_libraries_svr4): Likewise.
	* mem-break.c (delete_fast_tracepoint_jump): Likewise.
	(set_fast_tracepoint_jump): Likewise.
	(uninsert_fast_tracepoint_jumps_at): Likewise.
	(reinsert_fast_tracepoint_jumps_at): Likewise.
	(validate_inserted_breakpoint): Likewise.
	(clone_agent_expr): Likewise.
	* regcache.c (init_register_cache): Likewise.
	* remote-utils.c (putpkt_binary_1): Likewise.
	(decode_M_packet): Likewise.
	(decode_X_packet): Likewise.
	(look_up_one_symbol): Likewise.
	(relocate_instruction): Likewise.
	(monitor_output): Likewise.
	* server.c (handle_search_memory): Likewise.
	(handle_qxfer_exec_file): Likewise.
	(handle_qxfer_libraries): Likewise.
	(handle_qxfer): Likewise.
	(handle_query): Likewise.
	(handle_v_cont): Likewise.
	(handle_v_run): Likewise.
	(captured_main): Likewise.
	* target.c (write_inferior_memory): Likewise.
	* thread-db.c (try_thread_db_load_from_dir): Likewise.
	* tracepoint.c (init_trace_buffer): Likewise.
	(add_tracepoint_action): Likewise.
	(add_traceframe): Likewise.
	(add_traceframe_block): Likewise.
	(cmd_qtdpsrc): Likewise.
	(cmd_qtdv): Likewise.
	(cmd_qtstatus): Likewise.
	(response_source): Likewise.
	(response_tsv): Likewise.
	(cmd_qtnotes): Likewise.
	(gdb_collect): Likewise.
	(initialize_tracepoint): Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Add some more casts (1/2)
@ 2015-09-25 19:00 sergiodj+buildbot
  2015-09-25 19:48 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-09-25 19:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9a3c826307ae6ad4dd6fbd72431e7d9d4947f1dd ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: 9a3c826307ae6ad4dd6fbd72431e7d9d4947f1dd

Add some more casts (1/2)

Note: I needed to split this patch in two, otherwise it's too big for
the mailing list.

This patch adds explicit casts to situations where a void pointer is
assigned to a pointer to the "real" type.  Building in C++ mode requires
those assignments to use an explicit cast.  This includes, for example:

 - callback arguments (cleanups, comparison functions, ...)
 - data attached to some object (objfile, program space, etc) in the form
   of a void pointer
 - "user data" passed to some function

This patch comes from the commit "(mostly) auto-generated patch to insert
casts needed for C++", taken from Pedro's C++ branch.

Only files built on x86 with --enable-targets=all are modified, so the
native files for other arches will need to be dealt with separately.

I built-tested this with --enable-targets=all and reg-tested.  To my
surprise, a test case (selftest.exp) had to be adjusted.

Here's the ChangeLog entry.  Again, this was relatively quick to make
despite the length, thanks to David Malcom's script, although I don't
believe it's very useful information in that particular case...

gdb/ChangeLog:

	* aarch64-tdep.c (aarch64_make_prologue_cache): Add cast(s).
	(aarch64_make_stub_cache): Likewise.
	(value_of_aarch64_user_reg): Likewise.
	* ada-lang.c (ada_inferior_data_cleanup): Likewise.
	(get_ada_inferior_data): Likewise.
	(get_ada_pspace_data): Likewise.
	(ada_pspace_data_cleanup): Likewise.
	(ada_complete_symbol_matcher): Likewise.
	(ada_exc_search_name_matches): Likewise.
	* ada-tasks.c (get_ada_tasks_pspace_data): Likewise.
	(get_ada_tasks_inferior_data): Likewise.
	* addrmap.c (addrmap_mutable_foreach_worker): Likewise.
	(splay_obstack_alloc): Likewise.
	(splay_obstack_free): Likewise.
	* alpha-linux-tdep.c (alpha_linux_supply_gregset): Likewise.
	(alpha_linux_collect_gregset): Likewise.
	(alpha_linux_supply_fpregset): Likewise.
	(alpha_linux_collect_fpregset): Likewise.
	* alpha-mdebug-tdep.c (alpha_mdebug_frame_unwind_cache): Likewise.
	* alpha-tdep.c (alpha_lds): Likewise.
	(alpha_sts): Likewise.
	(alpha_sigtramp_frame_unwind_cache): Likewise.
	(alpha_heuristic_frame_unwind_cache): Likewise.
	(alpha_supply_int_regs): Likewise.
	(alpha_fill_int_regs): Likewise.
	(alpha_supply_fp_regs): Likewise.
	(alpha_fill_fp_regs): Likewise.
	* alphanbsd-tdep.c (alphanbsd_supply_fpregset): Likewise.
	(alphanbsd_aout_supply_gregset): Likewise.
	(alphanbsd_supply_gregset): Likewise.
	* amd64-linux-tdep.c (amd64_linux_init_abi): Likewise.
	(amd64_x32_linux_init_abi): Likewise.
	* amd64-nat.c (amd64_supply_native_gregset): Likewise.
	(amd64_collect_native_gregset): Likewise.
	* amd64-tdep.c (amd64_frame_cache): Likewise.
	(amd64_sigtramp_frame_cache): Likewise.
	(amd64_epilogue_frame_cache): Likewise.
	(amd64_supply_fxsave): Likewise.
	(amd64_supply_xsave): Likewise.
	(amd64_collect_fxsave): Likewise.
	(amd64_collect_xsave): Likewise.
	* amd64-windows-tdep.c (amd64_windows_frame_cache): Likewise.
	* amd64obsd-tdep.c (amd64obsd_trapframe_cache): Likewise.
	* arm-linux-tdep.c (arm_linux_supply_gregset): Likewise.
	(arm_linux_collect_gregset): Likewise.
	(arm_linux_supply_nwfpe): Likewise.
	(arm_linux_collect_nwfpe): Likewise.
	(arm_linux_supply_vfp): Likewise.
	(arm_linux_collect_vfp): Likewise.
	* arm-tdep.c (arm_find_mapping_symbol): Likewise.
	(arm_prologue_unwind_stop_reason): Likewise.
	(arm_prologue_this_id): Likewise.
	(arm_prologue_prev_register): Likewise.
	(arm_exidx_data_free): Likewise.
	(arm_find_exidx_entry): Likewise.
	(arm_stub_this_id): Likewise.
	(arm_m_exception_this_id): Likewise.
	(arm_m_exception_prev_register): Likewise.
	(arm_normal_frame_base): Likewise.
	(gdb_print_insn_arm): Likewise.
	(arm_objfile_data_free): Likewise.
	(arm_record_special_symbol): Likewise.
	(value_of_arm_user_reg): Likewise.
	* armbsd-tdep.c (armbsd_supply_fpregset): Likewise.
	(armbsd_supply_gregset): Likewise.
	* auto-load.c (auto_load_pspace_data_cleanup): Likewise.
	(get_auto_load_pspace_data): Likewise.
	(hash_loaded_script_entry): Likewise.
	(eq_loaded_script_entry): Likewise.
	(clear_section_scripts): Likewise.
	(collect_matching_scripts): Likewise.
	* auxv.c (auxv_inferior_data_cleanup): Likewise.
	(get_auxv_inferior_data): Likewise.
	* avr-tdep.c (avr_frame_unwind_cache): Likewise.
	* ax-general.c (do_free_agent_expr_cleanup): Likewise.
	* bfd-target.c (target_bfd_xfer_partial): Likewise.
	(target_bfd_xclose): Likewise.
	(target_bfd_get_section_table): Likewise.
	* bfin-tdep.c (bfin_frame_cache): Likewise.
	* block.c (find_block_in_blockvector): Likewise.
	(call_site_for_pc): Likewise.
	(block_find_non_opaque_type_preferred): Likewise.
	* break-catch-sig.c (signal_catchpoint_insert_location): Likewise.
	(signal_catchpoint_remove_location): Likewise.
	(signal_catchpoint_breakpoint_hit): Likewise.
	(signal_catchpoint_print_one): Likewise.
	(signal_catchpoint_print_mention): Likewise.
	(signal_catchpoint_print_recreate): Likewise.
	* break-catch-syscall.c (get_catch_syscall_inferior_data): Likewise.
	* breakpoint.c (do_cleanup_counted_command_line): Likewise.
	(bp_location_compare_addrs): Likewise.
	(get_first_locp_gte_addr): Likewise.
	(check_tracepoint_command): Likewise.
	(do_map_commands_command): Likewise.
	(get_breakpoint_objfile_data): Likewise.
	(free_breakpoint_probes): Likewise.
	(do_captured_breakpoint_query): Likewise.
	(compare_breakpoints): Likewise.
	(bp_location_compare): Likewise.
	(bpstat_remove_breakpoint_callback): Likewise.
	(do_delete_breakpoint_cleanup): Likewise.
	* bsd-uthread.c (bsd_uthread_set_supply_uthread): Likewise.
	(bsd_uthread_set_collect_uthread): Likewise.
	(bsd_uthread_activate): Likewise.
	(bsd_uthread_fetch_registers): Likewise.
	(bsd_uthread_store_registers): Likewise.
	* btrace.c (check_xml_btrace_version): Likewise.
	(parse_xml_btrace_block): Likewise.
	(parse_xml_btrace_pt_config_cpu): Likewise.
	(parse_xml_btrace_pt_raw): Likewise.
	(parse_xml_btrace_pt): Likewise.
	(parse_xml_btrace_conf_bts): Likewise.
	(parse_xml_btrace_conf_pt): Likewise.
	(do_btrace_data_cleanup): Likewise.
	* c-typeprint.c (find_typedef_for_canonicalize): Likewise.
	* charset.c (cleanup_iconv): Likewise.
	(do_cleanup_iterator): Likewise.
	* cli-out.c (cli_uiout_dtor): Likewise.
	(cli_table_begin): Likewise.
	(cli_table_body): Likewise.
	(cli_table_end): Likewise.
	(cli_table_header): Likewise.
	(cli_begin): Likewise.
	(cli_end): Likewise.
	(cli_field_int): Likewise.
	(cli_field_skip): Likewise.
	(cli_field_string): Likewise.
	(cli_field_fmt): Likewise.
	(cli_spaces): Likewise.
	(cli_text): Likewise.
	(cli_message): Likewise.
	(cli_wrap_hint): Likewise.
	(cli_flush): Likewise.
	(cli_redirect): Likewise.
	(out_field_fmt): Likewise.
	(field_separator): Likewise.
	(cli_out_set_stream): Likewise.
	* cli/cli-cmds.c (compare_symtabs): Likewise.
	* cli/cli-dump.c (call_dump_func): Likewise.
	(restore_section_callback): Likewise.
	* cli/cli-script.c (clear_hook_in_cleanup): Likewise.
	(do_restore_user_call_depth): Likewise.
	(do_free_command_lines_cleanup): Likewise.
	* coff-pe-read.c (get_section_vmas): Likewise.
	(pe_as16): Likewise.
	(pe_as32): Likewise.
	* coffread.c (coff_symfile_read): Likewise.
	* common/agent.c (agent_look_up_symbols): Likewise.
	* common/filestuff.c (do_close_cleanup): Likewise.
	* common/format.c (free_format_pieces_cleanup): Likewise.
	* common/vec.c (vec_o_reserve): Likewise.
	* compile/compile-c-support.c (print_one_macro): Likewise.
	* compile/compile-c-symbols.c (hash_symbol_error): Likewise.
	(eq_symbol_error): Likewise.
	(del_symbol_error): Likewise.
	(error_symbol_once): Likewise.
	(gcc_convert_symbol): Likewise.
	(gcc_symbol_address): Likewise.
	(hash_symname): Likewise.
	(eq_symname): Likewise.
	* compile/compile-c-types.c (hash_type_map_instance): Likewise.
	(eq_type_map_instance): Likewise.
	(insert_type): Likewise.
	(convert_type): Likewise.
	* compile/compile-object-load.c (munmap_listp_free_cleanup): Likewise.
	(setup_sections): Likewise.
	(link_hash_table_free): Likewise.
	(copy_sections): Likewise.
	* compile/compile-object-run.c (do_module_cleanup): Likewise.
	* compile/compile.c (compile_print_value): Likewise.
	(do_rmdir): Likewise.
	(cleanup_compile_instance): Likewise.
	(cleanup_unlink_file): Likewise.
	* completer.c (free_completion_tracker): Likewise.
	* corelow.c (add_to_spuid_list): Likewise.
	* cp-namespace.c (reset_directive_searched): Likewise.
	* cp-support.c (reset_directive_searched): Likewise.
	* cris-tdep.c (cris_sigtramp_frame_unwind_cache): Likewise.
	(cris_frame_unwind_cache): Likewise.
	* d-lang.c (builtin_d_type): Likewise.
	* d-namespace.c (reset_directive_searched): Likewise.
	* dbxread.c (dbx_free_symfile_info): Likewise.
	(do_free_bincl_list_cleanup): Likewise.
	* disasm.c (hash_dis_line_entry): Likewise.
	(eq_dis_line_entry): Likewise.
	(dis_asm_print_address): Likewise.
	(fprintf_disasm): Likewise.
	(do_ui_file_delete): Likewise.
	* doublest.c (convert_floatformat_to_doublest): Likewise.
	* dummy-frame.c (pop_dummy_frame_bpt): Likewise.
	(dummy_frame_prev_register): Likewise.
	(dummy_frame_this_id): Likewise.
	* dwarf2-frame-tailcall.c (cache_hash): Likewise.
	(cache_eq): Likewise.
	(cache_find): Likewise.
	(tailcall_frame_this_id): Likewise.
	(dwarf2_tailcall_prev_register_first): Likewise.
	(tailcall_frame_prev_register): Likewise.
	(tailcall_frame_dealloc_cache): Likewise.
	(tailcall_frame_prev_arch): Likewise.
	* dwarf2-frame.c (dwarf2_frame_state_free): Likewise.
	(dwarf2_frame_set_init_reg): Likewise.
	(dwarf2_frame_init_reg): Likewise.
	(dwarf2_frame_set_signal_frame_p): Likewise.
	(dwarf2_frame_signal_frame_p): Likewise.
	(dwarf2_frame_set_adjust_regnum): Likewise.
	(dwarf2_frame_adjust_regnum): Likewise.
	(clear_pointer_cleanup): Likewise.
	(dwarf2_frame_cache): Likewise.
	(find_cie): Likewise.
	(dwarf2_frame_find_fde): Likewise.
	* dwarf2expr.c (dwarf_expr_address_type): Likewise.
	(free_dwarf_expr_context_cleanup): Likewise.
	* dwarf2loc.c (locexpr_find_frame_base_location): Likewise.
	(locexpr_get_frame_base): Likewise.
	(loclist_find_frame_base_location): Likewise.
	(loclist_get_frame_base): Likewise.
	(dwarf_expr_dwarf_call): Likewise.
	(dwarf_expr_get_base_type): Likewise.
	(dwarf_expr_push_dwarf_reg_entry_value): Likewise.
	(dwarf_expr_get_obj_addr): Likewise.
	(entry_data_value_coerce_ref): Likewise.
	(entry_data_value_copy_closure): Likewise.
	(entry_data_value_free_closure): Likewise.
	(get_frame_address_in_block_wrapper): Likewise.
	(dwarf2_evaluate_property): Likewise.
	(dwarf2_compile_property_to_c): Likewise.
	(needs_frame_read_addr_from_reg): Likewise.
	(needs_frame_get_reg_value): Likewise.
	(needs_frame_frame_base): Likewise.
	(needs_frame_frame_cfa): Likewise.
	(needs_frame_tls_address): Likewise.
	(needs_frame_dwarf_call): Likewise.
	(needs_dwarf_reg_entry_value): Likewise.
	(get_ax_pc): Likewise.
	(locexpr_read_variable): Likewise.
	(locexpr_read_variable_at_entry): Likewise.
	(locexpr_read_needs_frame): Likewise.
	(locexpr_describe_location): Likewise.
	(locexpr_tracepoint_var_ref): Likewise.
	(locexpr_generate_c_location): Likewise.
	(loclist_read_variable): Likewise.
	(loclist_read_variable_at_entry): Likewise.
	(loclist_describe_location): Likewise.
	(loclist_tracepoint_var_ref): Likewise.
	(loclist_generate_c_location): Likewise.
	* dwarf2read.c (line_header_hash_voidp): Likewise.
	(line_header_eq_voidp): Likewise.
	(dwarf2_has_info): Likewise.
	(dwarf2_get_section_info): Likewise.
	(locate_dwz_sections): Likewise.
	(hash_file_name_entry): Likewise.
	(eq_file_name_entry): Likewise.
	(delete_file_name_entry): Likewise.
	(dw2_setup): Likewise.
	(dw2_get_file_names_reader): Likewise.
	(dw2_find_pc_sect_compunit_symtab): Likewise.
	(hash_signatured_type): Likewise.
	(eq_signatured_type): Likewise.
	(add_signatured_type_cu_to_table): Likewise.
	(create_debug_types_hash_table): Likewise.
	(lookup_dwo_signatured_type): Likewise.
	(lookup_dwp_signatured_type): Likewise.
	(lookup_signatured_type): Likewise.
	(hash_type_unit_group): Likewise.
	(eq_type_unit_group): Likewise.
	(get_type_unit_group): Likewise.
	(process_psymtab_comp_unit_reader): Likewise.
	(sort_tu_by_abbrev_offset): Likewise.
	(process_skeletonless_type_unit): Likewise.
	(psymtabs_addrmap_cleanup): Likewise.
	(dwarf2_read_symtab): Likewise.
	(psymtab_to_symtab_1): Likewise.
	(die_hash): Likewise.
	(die_eq): Likewise.
	(load_full_comp_unit_reader): Likewise.
	(reset_die_in_process): Likewise.
	(free_cu_line_header): Likewise.
	(handle_DW_AT_stmt_list): Likewise.
	(hash_dwo_file): Likewise.
	(eq_dwo_file): Likewise.
	(hash_dwo_unit): Likewise.
	(eq_dwo_unit): Likewise.
	(create_dwo_cu_reader): Likewise.
	(create_dwo_unit_in_dwp_v1): Likewise.
	(create_dwo_unit_in_dwp_v2): Likewise.
	(lookup_dwo_unit_in_dwp): Likewise.
	(dwarf2_locate_dwo_sections): Likewise.
	(dwarf2_locate_common_dwp_sections): Likewise.
	(dwarf2_locate_v2_dwp_sections): Likewise.
	(hash_dwp_loaded_cutus): Likewise.
	(eq_dwp_loaded_cutus): Likewise.
	(lookup_dwo_cutu): Likewise.
	(abbrev_table_free_cleanup): Likewise.
	(dwarf2_free_abbrev_table): Likewise.
	(find_partial_die_in_comp_unit): Likewise.
	(free_line_header_voidp): Likewise.
	(follow_die_offset): Likewise.
	(follow_die_sig_1): Likewise.
	(free_heap_comp_unit): Likewise.
	(free_stack_comp_unit): Likewise.
	(dwarf2_free_objfile): Likewise.
	(per_cu_offset_and_type_hash): Likewise.
	(per_cu_offset_and_type_eq): Likewise.
	(get_die_type_at_offset): Likewise.
	(partial_die_hash): Likewise.
	(partial_die_eq): Likewise.
	(dwarf2_per_objfile_free): Likewise.
	(hash_strtab_entry): Likewise.
	(eq_strtab_entry): Likewise.
	(add_string): Likewise.
	(hash_symtab_entry): Likewise.
	(eq_symtab_entry): Likewise.
	(delete_symtab_entry): Likewise.
	(cleanup_mapped_symtab): Likewise.
	(add_indices_to_cpool): Likewise.
	(hash_psymtab_cu_index): Likewise.
	(eq_psymtab_cu_index): Likewise.
	(add_address_entry_worker): Likewise.
	(unlink_if_set): Likewise.
	(write_one_signatured_type): Likewise.
	(save_gdb_index_command): Likewise.
	* elfread.c (elf_symtab_read): Likewise.
	(elf_gnu_ifunc_cache_hash): Likewise.
	(elf_gnu_ifunc_cache_eq): Likewise.
	(elf_gnu_ifunc_record_cache): Likewise.
	(elf_gnu_ifunc_resolve_by_cache): Likewise.
	(elf_get_probes): Likewise.
	(probe_key_free): Likewise.
	* f-lang.c (builtin_f_type): Likewise.
	* frame-base.c (frame_base_append_sniffer): Likewise.
	(frame_base_set_default): Likewise.
	(frame_base_find_by_frame): Likewise.
	* frame-unwind.c (frame_unwind_prepend_unwinder): Likewise.
	(frame_unwind_append_unwinder): Likewise.
	(frame_unwind_find_by_frame): Likewise.
	* frame.c (frame_addr_hash): Likewise.
	(frame_addr_hash_eq): Likewise.
	(frame_stash_find): Likewise.
	(do_frame_register_read): Likewise.
	(unwind_to_current_frame): Likewise.
	(frame_cleanup_after_sniffer): Likewise.
	* frv-linux-tdep.c (frv_linux_sigtramp_frame_cache): Likewise.
	* frv-tdep.c (frv_frame_unwind_cache): Likewise.
	* ft32-tdep.c (ft32_frame_cache): Likewise.
	* gcore.c (do_bfd_delete_cleanup): Likewise.
	(gcore_create_callback): Likewise.
	* gdb_bfd.c (hash_bfd): Likewise.
	(eq_bfd): Likewise.
	(gdb_bfd_open): Likewise.
	(free_one_bfd_section): Likewise.
	(gdb_bfd_ref): Likewise.
	(gdb_bfd_unref): Likewise.
	(get_section_descriptor): Likewise.
	(gdb_bfd_map_section): Likewise.
	(gdb_bfd_crc): Likewise.
	(gdb_bfd_mark_parent): Likewise.
	(gdb_bfd_record_inclusion): Likewise.
	(gdb_bfd_requires_relocations): Likewise.
	(print_one_bfd): Likewise.
	* gdbtypes.c (type_pair_hash): Likewise.
	(type_pair_eq): Likewise.
	(builtin_type): Likewise.
	(objfile_type): Likewise.
	* gnu-v3-abi.c (vtable_ptrdiff_type): Likewise.
	(vtable_address_point_offset): Likewise.
	(gnuv3_get_vtable): Likewise.
	(hash_value_and_voffset): Likewise.
	(eq_value_and_voffset): Likewise.
	(compare_value_and_voffset): Likewise.
	(compute_vtable_size): Likewise.
	(gnuv3_get_typeid_type): Likewise.
	* go-lang.c (builtin_go_type): Likewise.
	* guile/scm-block.c (bkscm_hash_block_smob): Likewise.
	(bkscm_eq_block_smob): Likewise.
	(bkscm_objfile_block_map): Likewise.
	(bkscm_del_objfile_blocks): Likewise.
	* guile/scm-breakpoint.c (bpscm_build_bp_list): Likewise.
	* guile/scm-disasm.c (gdbscm_disasm_read_memory_worker): Likewise.
	(gdbscm_disasm_print_address): Likewise.
	* guile/scm-frame.c (frscm_hash_frame_smob): Likewise.
	(frscm_eq_frame_smob): Likewise.
	(frscm_inferior_frame_map): Likewise.
	(frscm_del_inferior_frames): Likewise.
	* guile/scm-gsmob.c (gdbscm_add_objfile_ref): Likewise.
	* guile/scm-objfile.c (ofscm_handle_objfile_deleted): Likewise.
	(ofscm_objfile_smob_from_objfile): Likewise.
	* guile/scm-ports.c (ioscm_write): Likewise.
	(ioscm_file_port_delete): Likewise.
	(ioscm_file_port_rewind): Likewise.
	(ioscm_file_port_put): Likewise.
	(ioscm_file_port_write): Likewise.
	* guile/scm-progspace.c (psscm_handle_pspace_deleted): Likewise.
	(psscm_pspace_smob_from_pspace): Likewise.
	* guile/scm-safe-call.c (scscm_recording_pre_unwind_handler): Likewise.
	(scscm_recording_unwind_handler): Likewise.
	(gdbscm_with_catch): Likewise.
	(scscm_call_0_body): Likewise.
	(scscm_call_1_body): Likewise.
	(scscm_call_2_body): Likewise.
	(scscm_call_3_body): Likewise.
	(scscm_call_4_body): Likewise.
	(scscm_apply_1_body): Likewise.
	(scscm_eval_scheme_string): Likewise.
	(gdbscm_safe_eval_string): Likewise.
	(scscm_source_scheme_script): Likewise.
	(gdbscm_safe_source_script): Likewise.
	* guile/scm-string.c (gdbscm_call_scm_to_stringn): Likewise.
	(gdbscm_call_scm_from_stringn): Likewise.
	* guile/scm-symbol.c (syscm_hash_symbol_smob): Likewise.
	(syscm_eq_symbol_smob): Likewise.
	(syscm_get_symbol_map): Likewise.
	(syscm_del_objfile_symbols): Likewise.
	* guile/scm-symtab.c (stscm_hash_symtab_smob): Likewise.
	(stscm_eq_symtab_smob): Likewise.
	(stscm_objfile_symtab_map): Likewise.
	(stscm_del_objfile_symtabs): Likewise.
	* guile/scm-type.c (tyscm_hash_type_smob): Likewise.
	(tyscm_eq_type_smob): Likewise.
	(tyscm_type_map): Likewise.
	(tyscm_copy_type_recursive): Likewise.
	(save_objfile_types): Likewise.
	* guile/scm-utils.c (extract_arg): Likewise.
	* h8300-tdep.c (h8300_frame_cache): Likewise.
	* hppa-linux-tdep.c (hppa_linux_sigtramp_frame_unwind_cache): Likewise.
	* hppa-tdep.c (compare_unwind_entries): Likewise.
	(find_unwind_entry): Likewise.
	(hppa_frame_cache): Likewise.
	(hppa_stub_frame_unwind_cache): Likewise.
	* hppanbsd-tdep.c (hppanbsd_supply_gregset): Likewise.
	* hppaobsd-tdep.c (hppaobsd_supply_gregset): Likewise.
	(hppaobsd_supply_fpregset): Likewise.
	* i386-cygwin-tdep.c (core_process_module_section): Likewise.
	* i386-linux-tdep.c (i386_linux_init_abi): Likewise.
	* i386-tdep.c (i386_frame_cache): Likewise.
	(i386_epilogue_frame_cache): Likewise.
	(i386_sigtramp_frame_cache): Likewise.
	(i386_supply_gregset): Likewise.
	(i386_collect_gregset): Likewise.
	(i386_gdbarch_init): Likewise.
	* i386obsd-tdep.c (i386obsd_aout_supply_regset): Likewise.
	(i386obsd_trapframe_cache): Likewise.
	* i387-tdep.c (i387_supply_fsave): Likewise.
	(i387_collect_fsave): Likewise.
	(i387_supply_fxsave): Likewise.
	(i387_collect_fxsave): Likewise.
	(i387_supply_xsave): Likewise.
	(i387_collect_xsave): Likewise.
	* ia64-tdep.c (ia64_frame_cache): Likewise.
	(ia64_sigtramp_frame_cache): Likewise.
	* infcmd.c (attach_command_continuation): Likewise.
	(attach_command_continuation_free_args): Likewise.
	* inferior.c (restore_inferior): Likewise.
	(delete_thread_of_inferior): Likewise.
	* inflow.c (inflow_inferior_data_cleanup): Likewise.
	(get_inflow_inferior_data): Likewise.
	(inflow_inferior_exit): Likewise.
	* infrun.c (displaced_step_clear_cleanup): Likewise.
	(restore_current_uiout_cleanup): Likewise.
	(release_stop_context_cleanup): Likewise.
	(do_restore_infcall_suspend_state_cleanup): Likewise.
	(do_restore_infcall_control_state_cleanup): Likewise.
	(restore_inferior_ptid): Likewise.
	* inline-frame.c (block_starting_point_at): Likewise.
	* iq2000-tdep.c (iq2000_frame_cache): Likewise.
	* jit.c (get_jit_objfile_data): Likewise.
	(get_jit_program_space_data): Likewise.
	(jit_object_close_impl): Likewise.
	(jit_find_objf_with_entry_addr): Likewise.
	(jit_breakpoint_deleted): Likewise.
	(jit_unwind_reg_set_impl): Likewise.
	(jit_unwind_reg_get_impl): Likewise.
	(jit_dealloc_cache): Likewise.
	(jit_frame_sniffer): Likewise.
	(jit_frame_prev_register): Likewise.
	(jit_prepend_unwinder): Likewise.
	(jit_inferior_exit_hook): Likewise.
	(free_objfile_data): Likewise.
	* jv-lang.c (jv_per_objfile_free): Likewise.
	(get_dynamics_objfile): Likewise.
	(get_java_class_symtab): Likewise.
	(builtin_java_type): Likewise.
	* language.c (language_string_char_type): Likewise.
	(language_bool_type): Likewise.
	(language_lookup_primitive_type): Likewise.
	(language_lookup_primitive_type_as_symbol): Likewise.
	* linespec.c (hash_address_entry): Likewise.
	(eq_address_entry): Likewise.
	(iterate_inline_only): Likewise.
	(iterate_name_matcher): Likewise.
	(decode_line_2_compare_items): Likewise.
	(collect_one_symbol): Likewise.
	(compare_symbols): Likewise.
	(compare_msymbols): Likewise.
	(add_symtabs_to_list): Likewise.
	(collect_symbols): Likewise.
	(compare_msyms): Likewise.
	(add_minsym): Likewise.
	(cleanup_linespec_result): Likewise.
	* linux-fork.c (inferior_call_waitpid_cleanup): Likewise.
	* linux-nat.c (delete_lwp_cleanup): Likewise.
	(count_events_callback): Likewise.
	(select_event_lwp_callback): Likewise.
	(resume_stopped_resumed_lwps): Likewise.
	* linux-tdep.c (get_linux_gdbarch_data): Likewise.
	(invalidate_linux_cache_inf): Likewise.
	(get_linux_inferior_data): Likewise.
	(linux_find_memory_regions_thunk): Likewise.
	(linux_make_mappings_callback): Likewise.
	(linux_corefile_thread_callback): Likewise.
	(find_mapping_size): Likewise.
	* linux-thread-db.c (find_new_threads_callback): Likewise.
	* lm32-tdep.c (lm32_frame_cache): Likewise.
	* m2-lang.c (builtin_m2_type): Likewise.
	* m32c-tdep.c (m32c_analyze_frame_prologue): Likewise.
	* m32r-linux-tdep.c (m32r_linux_sigtramp_frame_cache): Likewise.
	(m32r_linux_supply_gregset): Likewise.
	(m32r_linux_collect_gregset): Likewise.
	* m32r-tdep.c (m32r_frame_unwind_cache): Likewise.
	* m68hc11-tdep.c (m68hc11_frame_unwind_cache): Likewise.
	* m68k-tdep.c (m68k_frame_cache): Likewise.
	* m68kbsd-tdep.c (m68kbsd_supply_fpregset): Likewise.
	(m68kbsd_supply_gregset): Likewise.
	* m68klinux-tdep.c (m68k_linux_sigtramp_frame_cache): Likewise.
	* m88k-tdep.c (m88k_frame_cache): Likewise.
	(m88k_supply_gregset): Likewise.

gdb/gdbserver/ChangeLog:

	* dll.c (match_dll): Add cast(s).
	(unloaded_dll): Likewise.
	* linux-low.c (second_thread_of_pid_p): Likewise.
	(delete_lwp_callback): Likewise.
	(count_events_callback): Likewise.
	(select_event_lwp_callback): Likewise.
	(linux_set_resume_request): Likewise.
	* server.c (accumulate_file_name_length): Likewise.
	(emit_dll_description): Likewise.
	(handle_qxfer_threads_worker): Likewise.
	(visit_actioned_threads): Likewise.
	* thread-db.c (any_thread_of): Likewise.
	* tracepoint.c (same_process_p): Likewise.
	(match_blocktype): Likewise.
	(build_traceframe_info_xml): Likewise.

gdb/testsuite/ChangeLog:

	* gdb.gdb/selftest.exp (do_steps_and_nexts): Adjust expected
	source line.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Add some more casts (2/2)
@ 2015-09-25 19:30 sergiodj+buildbot
  2015-09-25 19:54 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-09-25 19:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 19ba03f49581e407097a3e4821a957c422551ae5 ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: 19ba03f49581e407097a3e4821a957c422551ae5

Add some more casts (2/2)

See previous patch's description.

gdb/ChangeLog:

	* macrocmd.c (print_macro_callback): Add cast(s).
	* macrotab.c (macro_bcache_str): Likewise.
	(new_macro_definition): Likewise.
	* main.c (captured_main): Likewise.
	* maint.c (print_bfd_section_info): Likewise.
	* mdebugread.c (mdebug_build_psymtabs): Likewise.
	(basic_type): Likewise.
	* memattr.c (mem_region_cmp): Likewise.
	* memory-map.c (memory_map_start_memory): Likewise.
	(memory_map_end_memory): Likewise.
	(memory_map_start_property): Likewise.
	(memory_map_end_property): Likewise.
	(clear_result): Likewise.
	* memrange.c (compare_mem_ranges): Likewise.
	* mep-tdep.c (mep_analyze_frame_prologue): Likewise.
	* mi/mi-cmd-var.c (mi_cmd_var_update_iter): Likewise.
	* mi/mi-console.c (mi_console_file_delete): Likewise.
	(mi_console_file_fputs): Likewise.
	(mi_console_raw_packet): Likewise.
	(mi_console_file_flush): Likewise.
	(mi_console_set_raw): Likewise.
	* mi/mi-interp.c (mi_interpreter_resume): Likewise.
	(mi_new_thread): Likewise.
	(mi_thread_exit): Likewise.
	(mi_record_changed): Likewise.
	(mi_inferior_added): Likewise.
	(mi_inferior_appeared): Likewise.
	(mi_inferior_exit): Likewise.
	(mi_inferior_removed): Likewise.
	(mi_interp_data): Likewise.
	(mi_on_normal_stop): Likewise.
	(mi_traceframe_changed): Likewise.
	(mi_tsv_created): Likewise.
	(mi_tsv_deleted): Likewise.
	(mi_tsv_modified): Likewise.
	(mi_breakpoint_created): Likewise.
	(mi_breakpoint_deleted): Likewise.
	(mi_breakpoint_modified): Likewise.
	(mi_output_running_pid): Likewise.
	(mi_inferior_count): Likewise.
	(mi_solib_loaded): Likewise.
	(mi_solib_unloaded): Likewise.
	(mi_command_param_changed): Likewise.
	(mi_memory_changed): Likewise.
	(report_initial_inferior): Likewise.
	(mi_ui_out): Likewise.
	(mi_set_logging): Likewise.
	* mi/mi-main.c (collect_cores): Likewise.
	(print_one_inferior): Likewise.
	(free_vector_of_ints): Likewise.
	(free_splay_tree): Likewise.
	(mi_execute_command): Likewise.
	* mi/mi-out.c (mi_table_body): Likewise.
	(mi_table_end): Likewise.
	(mi_table_header): Likewise.
	(mi_begin): Likewise.
	(mi_end): Likewise.
	(mi_field_int): Likewise.
	(mi_field_string): Likewise.
	(mi_field_fmt): Likewise.
	(mi_flush): Likewise.
	(mi_redirect): Likewise.
	(field_separator): Likewise.
	(mi_open): Likewise.
	(mi_close): Likewise.
	(mi_out_buffered): Likewise.
	(mi_out_rewind): Likewise.
	(mi_out_put): Likewise.
	(mi_version): Likewise.
	(mi_out_data_dtor): Likewise.
	* mi/mi-parse.c (mi_parse_cleanup): Likewise.
	* microblaze-tdep.c (microblaze_frame_cache): Likewise.
	* minidebug.c (lzma_open): Likewise.
	(lzma_pread): Likewise.
	(lzma_close): Likewise.
	(lzma_stat): Likewise.
	* mips-linux-tdep.c (mips_linux_init_abi): Likewise.
	* mips-sde-tdep.c (mips_sde_frame_cache): Likewise.
	(mips_sde_elf_osabi_sniff_abi_tag_sections): Likewise.
	* mips-tdep.c (mips_insn16_frame_cache): Likewise.
	(mips_micro_frame_cache): Likewise.
	(mips_insn32_frame_cache): Likewise.
	(mips_stub_frame_cache): Likewise.
	(gdb_print_insn_mips): Likewise.
	(value_of_mips_user_reg): Likewise.
	(mips_gdbarch_init): Likewise.
	* mips64obsd-tdep.c (mips64obsd_supply_gregset): Likewise.
	* mipsnbsd-tdep.c (mipsnbsd_supply_fpregset): Likewise.
	(mipsnbsd_supply_gregset): Likewise.
	* mn10300-linux-tdep.c (am33_supply_fpregset_method): Likewise.
	(am33_collect_gregset_method): Likewise.
	(am33_collect_fpregset_method): Likewise.
	* mn10300-tdep.c (mn10300_analyze_frame_prologue): Likewise.
	* moxie-tdep.c (moxie_frame_cache): Likewise.
	* msp430-tdep.c (msp430_get_opcode_byte): Likewise.
	(msp430_analyze_frame_prologue): Likewise.
	* mt-tdep.c (mt_frame_unwind_cache): Likewise.
	* nios2-linux-tdep.c (nios2_supply_gregset): Likewise.
	(nios2_collect_gregset): Likewise.
	* nios2-tdep.c (nios2_frame_unwind_cache): Likewise.
	(nios2_stub_frame_cache): Likewise.
	* objc-lang.c (find_methods): Likewise.
	* objfiles.c (objfiles_pspace_data_cleanup): Likewise.
	(get_objfile_pspace_data): Likewise.
	(get_objfile_bfd_data): Likewise.
	(objfile_bfd_data_free): Likewise.
	(add_to_objfile_sections): Likewise.
	(do_free_objfile_cleanup): Likewise.
	(resume_section_map_updates_cleanup): Likewise.
	* opencl-lang.c (builtin_opencl_type): Likewise.
	* osabi.c (generic_elf_osabi_sniff_abi_tag_sections): Likewise.
	* osdata.c (osdata_start_osdata): Likewise.
	(osdata_start_item): Likewise.
	(osdata_start_column): Likewise.
	(osdata_end_column): Likewise.
	(clear_parsing_data): Likewise.
	(osdata_free_cleanup): Likewise.
	* parse.c (type_stack_cleanup): Likewise.
	(exp_uses_objfile_iter): Likewise.
	* ppc-linux-tdep.c (ppc_linux_supply_gregset): Likewise.
	(ppc_linux_collect_gregset): Likewise.
	(ppu2spu_prev_arch): Likewise.
	(ppu2spu_this_id): Likewise.
	(ppu2spu_prev_register): Likewise.
	(ppu2spu_unwind_register): Likewise.
	(ppu2spu_sniffer): Likewise.
	(ppu2spu_dealloc_cache): Likewise.
	(ppc_linux_init_abi): Likewise.
	* ppcfbsd-tdep.c (ppcfbsd_sigtramp_frame_cache): Likewise.
	* ppcobsd-tdep.c (ppcobsd_sigtramp_frame_cache): Likewise.
	* progspace.c (restore_program_space): Likewise.
	* psymtab.c (find_pc_sect_psymtab): Likewise.
	(compare_psymbols): Likewise.
	(psymbol_bcache_full): Likewise.
	(allocate_psymtab): Likewise.
	(discard_psymtabs_upto): Likewise.
	* python/py-block.c (set_block): Likewise.
	(del_objfile_blocks): Likewise.
	* python/py-breakpoint.c (build_bp_list): Likewise.
	* python/py-inferior.c (inferior_to_inferior_object): Likewise.
	(build_inferior_list): Likewise.
	(py_free_inferior): Likewise.
	* python/py-objfile.c (py_free_objfile): Likewise.
	(objfile_to_objfile_object): Likewise.
	* python/py-prettyprint.c (py_restore_tstate): Likewise.
	* python/py-progspace.c (py_free_pspace): Likewise.
	(pspace_to_pspace_object): Likewise.
	* python/py-symbol.c (set_symbol): Likewise.
	(del_objfile_symbols): Likewise.
	* python/py-symtab.c (set_sal): Likewise.
	(set_symtab): Likewise.
	(del_objfile_symtab): Likewise.
	(del_objfile_sal): Likewise.
	* python/py-type.c (save_objfile_types): Likewise.
	(set_type): Likewise.
	* python/py-unwind.c (pyuw_prev_register): Likewise.
	(pyuw_on_new_gdbarch): Likewise.
	* python/py-utils.c (py_decref): Likewise.
	(py_xdecref): Likewise.
	(gdb_py_generic_dict): Likewise.
	* python/py-xmethods.c (gdbpy_free_xmethod_worker_data): Likewise.
	(gdbpy_clone_xmethod_worker_data): Likewise.
	(gdbpy_get_xmethod_arg_types): Likewise.
	(gdbpy_get_xmethod_result_type): Likewise.
	(gdbpy_invoke_xmethod): Likewise.
	* python/python.c (gdbpy_apply_type_printers): Likewise.
	(gdbpy_free_type_printers): Likewise.
	* record-btrace.c (record_btrace_disable_callback): Likewise.
	(bfcache_hash): Likewise.
	(bfcache_eq): Likewise.
	(btrace_get_frame_function): Likewise.
	(record_btrace_frame_unwind_stop_reason): Likewise.
	(record_btrace_frame_this_id): Likewise.
	(record_btrace_frame_prev_register): Likewise.
	(record_btrace_frame_dealloc_cache): Likewise.
	* record-full.c (record_full_message_wrapper): Likewise.
	(record_full_save_cleanups): Likewise.
	* regcache.c (regcache_descr): Likewise.
	(do_regcache_xfree): Likewise.
	(do_regcache_invalidate): Likewise.
	(do_cooked_read): Likewise.
	(regcache_transfer_regset): Likewise.
	* reggroups.c (reggroup_add): Likewise.
	(reggroup_next): Likewise.
	(reggroup_prev): Likewise.
	* remote-fileio.c (do_remote_fileio_request): Likewise.
	* remote-notif.c (remote_async_get_pending_events_handler): Likewise.
	(do_notif_event_xfree): Likewise.
	* remote.c (get_remote_arch_state): Likewise.
	(remote_pspace_data_cleanup): Likewise.
	(get_remote_exec_file): Likewise.
	(set_pspace_remote_exec_file): Likewise.
	(compare_pnums): Likewise.
	(clear_threads_listing_context): Likewise.
	(remote_newthread_step): Likewise.
	(start_thread): Likewise.
	(end_thread): Likewise.
	(remove_child_of_pending_fork): Likewise.
	(remove_stop_reply_for_inferior): Likewise.
	(remove_stop_reply_of_remote_state): Likewise.
	(remote_notif_remove_once_on_match): Likewise.
	(stop_reply_match_ptid_and_ws): Likewise.
	(kill_child_of_pending_fork): Likewise.
	(register_remote_g_packet_guess): Likewise.
	(remote_read_description_p): Likewise.
	(remote_read_description): Likewise.
	(free_actions_list_cleanup_wrapper): Likewise.
	(remote_async_serial_handler): Likewise.
	* rl78-tdep.c (rl78_get_opcode_byte): Likewise.
	(rl78_analyze_frame_prologue): Likewise.
	* rs6000-tdep.c (ppc_supply_gregset): Likewise.
	(ppc_supply_fpregset): Likewise.
	(ppc_supply_vsxregset): Likewise.
	(ppc_supply_vrregset): Likewise.
	(ppc_collect_gregset): Likewise.
	(ppc_collect_fpregset): Likewise.
	(ppc_collect_vsxregset): Likewise.
	(ppc_collect_vrregset): Likewise.
	(e500_move_ev_register): Likewise.
	(do_regcache_raw_write): Likewise.
	(rs6000_frame_cache): Likewise.
	(rs6000_epilogue_frame_cache): Likewise.
	(rs6000_gdbarch_init): Likewise.
	* rx-tdep.c (rx_get_opcode_byte): Likewise.
	(rx_analyze_frame_prologue): Likewise.
	(rx_frame_type): Likewise.
	(rx_frame_sniffer_common): Likewise.
	* s390-linux-tdep.c (s390_check_for_saved): Likewise.
	(s390_frame_unwind_cache): Likewise.
	(s390_stub_frame_unwind_cache): Likewise.
	(s390_sigtramp_frame_unwind_cache): Likewise.
	* score-tdep.c (score_make_prologue_cache): Likewise.
	* sentinel-frame.c (sentinel_frame_prev_register): Likewise.
	(sentinel_frame_prev_arch): Likewise.
	* ser-base.c (fd_event): Likewise.
	(push_event): Likewise.
	(ser_base_write): Likewise.
	* ser-pipe.c (pipe_close): Likewise.
	* serial.c (serial_write): Likewise.
	* sh-tdep.c (sh_frame_cache): Likewise.
	(sh_stub_this_id): Likewise.
	* sh64-tdep.c (sh64_frame_cache): Likewise.
	* solib-aix.c (get_solib_aix_inferior_data): Likewise.
	(library_list_start_library): Likewise.
	(library_list_start_list): Likewise.
	(solib_aix_free_library_list): Likewise.
	* solib-darwin.c (get_darwin_info): Likewise.
	* solib-dsbt.c (get_dsbt_info): Likewise.
	* solib-spu.c (append_ocl_sos): Likewise.
	* solib-svr4.c (svr4_pspace_data_cleanup): Likewise.
	(get_svr4_info): Likewise.
	(library_list_start_library): Likewise.
	(svr4_library_list_start_list): Likewise.
	(hash_probe_and_action): Likewise.
	(equal_probe_and_action): Likewise.
	(svr4_update_solib_event_breakpoint): Likewise.
	(set_solib_svr4_fetch_link_map_offsets): Likewise.
	(svr4_fetch_link_map_offsets): Likewise.
	(svr4_have_link_map_offsets): Likewise.
	* solib-target.c (library_list_start_segment): Likewise.
	(library_list_start_section): Likewise.
	(library_list_start_library): Likewise.
	(library_list_end_library): Likewise.
	(library_list_start_list): Likewise.
	(solib_target_free_library_list): Likewise.
	* solib.c (solib_ops): Likewise.
	(set_solib_ops): Likewise.
	* sparc-sol2-tdep.c (sparc32_sol2_sigtramp_frame_cache): Likewise.
	* sparc-tdep.c (sparc_frame_cache): Likewise.
	(sparc32_frame_cache): Likewise.
	(sparc32_supply_gregset): Likewise.
	(sparc32_collect_gregset): Likewise.
	(sparc32_supply_fpregset): Likewise.
	(sparc32_collect_fpregset): Likewise.
	* sparc64-sol2-tdep.c (sparc64_sol2_sigtramp_frame_cache): Likewise.
	* sparc64-tdep.c (sparc64_supply_gregset): Likewise.
	(sparc64_collect_gregset): Likewise.
	(sparc64_supply_fpregset): Likewise.
	(sparc64_collect_fpregset): Likewise.
	* sparc64fbsd-tdep.c (sparc64fbsd_sigtramp_frame_cache): Likewise.
	* sparc64nbsd-tdep.c (sparc64nbsd_sigcontext_frame_cache): Likewise.
	* sparc64obsd-tdep.c (sparc64obsd_frame_cache): Likewise.
	(sparc64obsd_trapframe_cache): Likewise.
	* sparcnbsd-tdep.c (sparc32nbsd_sigcontext_frame_cache): Likewise.
	* sparcobsd-tdep.c (sparc32obsd_sigtramp_frame_cache): Likewise.
	* spu-multiarch.c (spu_gdbarch): Likewise.
	* spu-tdep.c (spu_frame_unwind_cache): Likewise.
	(spu2ppu_prev_arch): Likewise.
	(spu2ppu_this_id): Likewise.
	(spu2ppu_prev_register): Likewise.
	(spu2ppu_dealloc_cache): Likewise.
	(spu_dis_asm_print_address): Likewise.
	(gdb_print_insn_spu): Likewise.
	(spu_get_overlay_table): Likewise.
	* stabsread.c (rs6000_builtin_type): Likewise.
	* stack.c (do_print_variable_and_value): Likewise.
	* stap-probe.c (get_stap_base_address_1): Likewise.
	* symfile-debug.c (debug_qf_has_symbols): Likewise.
	(debug_qf_find_last_source_symtab): Likewise.
	(debug_qf_forget_cached_source_info): Likewise.
	(debug_qf_map_symtabs_matching_filename): Likewise.
	(debug_qf_lookup_symbol): Likewise.
	(debug_qf_print_stats): Likewise.
	(debug_qf_dump): Likewise.
	(debug_qf_relocate): Likewise.
	(debug_qf_expand_symtabs_for_function): Likewise.
	(debug_qf_expand_all_symtabs): Likewise.
	(debug_qf_expand_symtabs_with_fullname): Likewise.
	(debug_qf_map_matching_symbols): Likewise.
	(debug_qf_expand_symtabs_matching): Likewise.
	(debug_qf_find_pc_sect_compunit_symtab): Likewise.
	(debug_qf_map_symbol_filenames): Likewise.
	(debug_sym_get_probes): Likewise.
	(debug_sym_new_init): Likewise.
	(debug_sym_init): Likewise.
	(debug_sym_read): Likewise.
	(debug_sym_read_psymbols): Likewise.
	(debug_sym_finish): Likewise.
	(debug_sym_offsets): Likewise.
	(debug_sym_read_linetable): Likewise.
	(debug_sym_relocate): Likewise.
	(uninstall_symfile_debug_logging): Likewise.
	* symfile-mem.c (symbol_file_add_from_memory_wrapper): Likewise.
	* symfile.c (place_section): Likewise.
	(add_section_size_callback): Likewise.
	(load_progress): Likewise.
	(load_section_callback): Likewise.
	(clear_memory_write_data): Likewise.
	(allocate_symtab): Likewise.
	* symmisc.c (maintenance_expand_file_matcher): Likewise.
	* symtab.c (lookup_symtab_callback): Likewise.
	(hash_demangled_name_entry): Likewise.
	(eq_demangled_name_entry): Likewise.
	(get_symbol_cache): Likewise.
	(symbol_cache_cleanup): Likewise.
	(set_symbol_cache_size): Likewise.
	(symbol_cache_flush): Likewise.
	(maintenance_print_symbol_cache): Likewise.
	(maintenance_print_symbol_cache_statistics): Likewise.
	(delete_filename_seen_cache): Likewise.
	(output_partial_symbol_filename): Likewise.
	(search_symbols_file_matches): Likewise.
	(search_symbols_name_matches): Likewise.
	(do_free_completion_list): Likewise.
	(maybe_add_partial_symtab_filename): Likewise.
	(get_main_info): Likewise.
	(main_info_cleanup): Likewise.
	* target-dcache.c (target_dcache_cleanup): Likewise.
	(target_dcache_init_p): Likewise.
	(target_dcache_invalidate): Likewise.
	(target_dcache_get): Likewise.
	(target_dcache_get_or_init): Likewise.
	* target-descriptions.c (target_find_description): Likewise.
	(tdesc_find_type): Likewise.
	(tdesc_data_cleanup): Likewise.
	(tdesc_find_arch_register): Likewise.
	(tdesc_register_name): Likewise.
	(tdesc_register_type): Likewise.
	(tdesc_register_reggroup_p): Likewise.
	(set_tdesc_pseudo_register_name): Likewise.
	(set_tdesc_pseudo_register_type): Likewise.
	(set_tdesc_pseudo_register_reggroup_p): Likewise.
	(tdesc_use_registers): Likewise.
	(free_target_description): Likewise.
	* target-memory.c (compare_block_starting_address): Likewise.
	(cleanup_request_data): Likewise.
	(cleanup_write_requests_vector): Likewise.
	* target.c (open_target): Likewise.
	(cleanup_restore_target_terminal): Likewise.
	(free_memory_read_result_vector): Likewise.
	* thread.c (disable_thread_stack_temporaries): Likewise.
	(finish_thread_state_cleanup): Likewise.
	(do_restore_current_thread_cleanup): Likewise.
	(restore_current_thread_cleanup_dtor): Likewise.
	(set_thread_refcount): Likewise.
	(tp_array_compar): Likewise.
	(do_captured_thread_select): Likewise.
	* tic6x-tdep.c (tic6x_frame_unwind_cache): Likewise.
	(tic6x_stub_this_id): Likewise.
	* tilegx-tdep.c (tilegx_frame_cache): Likewise.
	* top.c (do_restore_instream_cleanup): Likewise.
	(gdb_readline_wrapper_cleanup): Likewise.
	(kill_or_detach): Likewise.
	(print_inferior_quit_action): Likewise.
	* tracefile-tfile.c (match_blocktype): Likewise.
	(build_traceframe_info): Likewise.
	* tracefile.c (trace_file_writer_xfree): Likewise.
	* tracepoint.c (memrange_cmp): Likewise.
	(do_collect_symbol): Likewise.
	(do_clear_collection_list): Likewise.
	(do_restore_current_traceframe_cleanup): Likewise.
	(restore_current_traceframe_cleanup_dtor): Likewise.
	(free_current_marker): Likewise.
	(traceframe_info_start_memory): Likewise.
	(traceframe_info_start_tvar): Likewise.
	(free_result): Likewise.
	* tramp-frame.c (tramp_frame_cache): Likewise.
	* tui/tui-file.c (tui_file_delete): Likewise.
	(tui_fileopen): Likewise.
	(tui_sfileopen): Likewise.
	(tui_file_isatty): Likewise.
	(tui_file_rewind): Likewise.
	(tui_file_put): Likewise.
	(tui_file_fputs): Likewise.
	(tui_file_get_strbuf): Likewise.
	(tui_file_adjust_strbuf): Likewise.
	(tui_file_flush): Likewise.
	* tui/tui-layout.c (make_command_window): Likewise.
	(make_data_window): Likewise.
	(show_source_disasm_command): Likewise.
	(show_data): Likewise.
	(make_source_or_disasm_window): Likewise.
	(show_source_or_disasm_and_command): Likewise.
	* tui/tui-out.c (tui_field_int): Likewise.
	(tui_field_string): Likewise.
	(tui_field_fmt): Likewise.
	(tui_text): Likewise.
	* typeprint.c (hash_typedef_field): Likewise.
	(eq_typedef_field): Likewise.
	(do_free_typedef_hash): Likewise.
	(copy_typedef_hash_element): Likewise.
	(do_free_global_table): Likewise.
	(find_global_typedef): Likewise.
	(find_typedef_in_hash): Likewise.
	* ui-file.c (ui_file_write_for_put): Likewise.
	(do_ui_file_xstrdup): Likewise.
	(mem_file_delete): Likewise.
	(mem_file_rewind): Likewise.
	(mem_file_put): Likewise.
	(mem_file_write): Likewise.
	(stdio_file_delete): Likewise.
	(stdio_file_flush): Likewise.
	(stdio_file_read): Likewise.
	(stdio_file_write): Likewise.
	(stdio_file_write_async_safe): Likewise.
	(stdio_file_fputs): Likewise.
	(stdio_file_isatty): Likewise.
	(stdio_file_fseek): Likewise.
	(tee_file_delete): Likewise.
	(tee_file_flush): Likewise.
	(tee_file_write): Likewise.
	(tee_file_fputs): Likewise.
	(tee_file_isatty): Likewise.
	* ui-out.c (do_cleanup_table_end): Likewise.
	(do_cleanup_end): Likewise.
	* user-regs.c (user_reg_add): Likewise.
	(user_reg_map_name_to_regnum): Likewise.
	(usernum_to_user_reg): Likewise.
	(maintenance_print_user_registers): Likewise.
	* utils.c (do_bfd_close_cleanup): Likewise.
	(do_fclose_cleanup): Likewise.
	(do_obstack_free): Likewise.
	(do_ui_file_delete): Likewise.
	(do_ui_out_redirect_pop): Likewise.
	(do_free_section_addr_info): Likewise.
	(restore_integer): Likewise.
	(do_unpush_target): Likewise.
	(do_htab_delete_cleanup): Likewise.
	(do_restore_ui_file): Likewise.
	(do_value_free): Likewise.
	(do_free_so): Likewise.
	(free_current_contents): Likewise.
	(do_regfree_cleanup): Likewise.
	(core_addr_hash): Likewise.
	(core_addr_eq): Likewise.
	(do_free_char_ptr_vec): Likewise.
	* v850-tdep.c (v850_frame_cache): Likewise.
	* varobj.c (do_free_variable_cleanup): Likewise.
	* vax-tdep.c (vax_supply_gregset): Likewise.
	(vax_frame_cache): Likewise.
	* vaxobsd-tdep.c (vaxobsd_sigtramp_frame_cache): Likewise.
	* xml-support.c (gdb_xml_body_text): Likewise.
	(gdb_xml_values_cleanup): Likewise.
	(gdb_xml_start_element): Likewise.
	(gdb_xml_start_element_wrapper): Likewise.
	(gdb_xml_end_element): Likewise.
	(gdb_xml_end_element_wrapper): Likewise.
	(gdb_xml_cleanup): Likewise.
	(gdb_xml_fetch_external_entity): Likewise.
	(gdb_xml_parse_attr_enum): Likewise.
	(xinclude_start_include): Likewise.
	(xinclude_end_include): Likewise.
	(xml_xinclude_default): Likewise.
	(xml_xinclude_start_doctype): Likewise.
	(xml_xinclude_end_doctype): Likewise.
	(xml_xinclude_cleanup): Likewise.
	(xml_fetch_content_from_file): Likewise.
	* xml-syscall.c (free_syscalls_info): Likewise.
	(syscall_start_syscall): Likewise.
	* xml-tdesc.c (tdesc_end_arch): Likewise.
	(tdesc_end_osabi): Likewise.
	(tdesc_end_compatible): Likewise.
	(tdesc_start_target): Likewise.
	(tdesc_start_feature): Likewise.
	(tdesc_start_reg): Likewise.
	(tdesc_start_union): Likewise.
	(tdesc_start_struct): Likewise.
	(tdesc_start_flags): Likewise.
	(tdesc_start_field): Likewise.
	(tdesc_start_vector): Likewise.
	(fetch_available_features_from_target): Likewise.
	* xstormy16-tdep.c (xstormy16_frame_cache): Likewise.
	* xtensa-tdep.c (xtensa_supply_gregset): Likewise.
	(xtensa_frame_cache): Likewise.
	(xtensa_frame_prev_register): Likewise.
	(xtensa_extract_return_value): Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] The FT32's disassembly of 10-bit literals has the incorrect mask.
@ 2015-09-25 20:12 sergiodj+buildbot
  2015-09-25 20:29 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-09-25 20:12 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9a09557a93b9f11371e4213589878437e567f897 ***

Author: jamesbowman <jamesb@excamera.com>
Branch: master
Commit: 9a09557a93b9f11371e4213589878437e567f897

The FT32's disassembly of 10-bit literals has the incorrect mask.

[opcodes]
	* ft32-dis.c (print_insn_ft32): Fix incorrect data field mask.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [D] Fix regression in py-lookup-type.exp
@ 2015-09-26  8:11 sergiodj+buildbot
  2015-09-26  8:37 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-09-26  8:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ba587d55a56db16e9e47d1e0975f5125fbafc6db ***

Author: Iain Buclaw <ibuclaw@gdcproject.org>
Branch: master
Commit: ba587d55a56db16e9e47d1e0975f5125fbafc6db

[D] Fix regression in py-lookup-type.exp

In the console interpreter, primitive types are resolved in the expression
parser.  However that didn't take into consideration the script interface.

gdb/ChangeLog:

	* d-namespace.c (d_lookup_symbol): New arg langdef.
	All callers updated.  Support looking up symbol as a primitive type.
	(lookup_module_scope): New arg langdef.  All callers updated.
	Call d_lookup_symbol directly for simple bare symbols.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix cast of xml_find_attribute's return value
@ 2015-09-28  2:50 sergiodj+buildbot
  2015-09-28  3:34 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-09-28  2:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bc84451b7af508ddd154a8793eaf0de68b7ca80a ***

Author: Simon Marchi <simark@nova.polymtl.ca>
Branch: master
Commit: bc84451b7af508ddd154a8793eaf0de68b7ca80a

Fix cast of xml_find_attribute's return value

The cast auto-insert script inserted long unsigned int, but we should
use the typedef ULONGEST.  Fixes build failures on i386.

gdb/ChangeLog:

	* btrace.c (parse_xml_btrace_block): Fix cast of
	xml_find_attribute's return value.
	* memory-map.c (memory_map_start_memory): Likewise.
	* solib-svr4.c (library_list_start_library): Likewise.
	* solib-target.c (library_list_start_segment): Likewise.
	(library_list_start_section): Likewise.
	* tracepoint.c (traceframe_info_start_memory): Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Patches for illegal ppc 500 instructions
@ 2015-09-28 15:45 sergiodj+buildbot
  2015-09-28 16:07 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-09-28 15:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 36f7a9411dcd7dbeb3483bc83a1acbb3dd235deb ***

Author: Tom Rix <tom@bumblecow.com>
Branch: master
Commit: 36f7a9411dcd7dbeb3483bc83a1acbb3dd235deb

Patches for illegal ppc 500 instructions

This change marks a few opcodes as invalid for ppc e500 as well as adds
a test to verify the change.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Updare French translation for binutils and German translation for opcodes.
@ 2015-09-28 18:35 sergiodj+buildbot
  2015-09-28 19:03 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-09-28 18:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b08b78e7d4bb56f395d3212eed6184ede236c760 ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: b08b78e7d4bb56f395d3212eed6184ede236c760

Updare French translation for binutils and German translation for opcodes.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] FT32: define macros for instruction recognition.
@ 2015-09-28 19:11 sergiodj+buildbot
  2015-09-28 20:00 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-09-28 19:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 71f4ed30fe331d062703e803f29a67b558e8e22d ***

Author: jamesbowman <jamesb@excamera.com>
Branch: master
Commit: 71f4ed30fe331d062703e803f29a67b558e8e22d

FT32: define macros for instruction recognition.

Other places (e.g. the gdb stack unwinder) can use these instead of
hard-coded patterns.

[include/Changelog]

2015-09-26  James Bowman  <james.bowman@ftdichip.com>

	* opcode/ft32.h: Add instruction macros FT32_*()


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] common/filestuff.c (make_cleanup_close): Update comment.
@ 2015-09-28 19:25 sergiodj+buildbot
  2015-09-28 20:59 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-09-28 19:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c402ef907a6c0600fc5dec79b6165afd49233124 ***

Author: Doug Evans <dje@google.com>
Branch: master
Commit: c402ef907a6c0600fc5dec79b6165afd49233124

common/filestuff.c (make_cleanup_close): Update comment.

gdb/ChangeLog:

	* common/filestuff.c (make_cleanup_close): Update comment.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] gdb.base/gcore.c (array_func): Add reference to static_array.
@ 2015-09-28 22:09 sergiodj+buildbot
  2015-09-28 23:25 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-09-28 22:09 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c60eb31fb11129ee91b9f778b852f886db545381 ***

Author: Doug Evans <dje@google.com>
Branch: master
Commit: c60eb31fb11129ee91b9f778b852f886db545381

gdb.base/gcore.c (array_func): Add reference to static_array.

Otherwise clang will delete it: it's otherwise unused.

gdb/testsuite/ChangeLog:

	* gdb.base/gcore.c (array_func): Add reference to static_array.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] cli-script.c: Fix read_next_line's comment
@ 2015-09-29  0:39 sergiodj+buildbot
  2015-09-29 12:51 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-09-29  0:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2181a6c6267eb62cc4feebb82a44907ae3c1ee2c ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: 2181a6c6267eb62cc4feebb82a44907ae3c1ee2c

cli-script.c: Fix read_next_line's comment

It seems obvious to me that stdout should in fact be stdin.

gdb/ChangeLog:

	* cli/cli-script.c (read_next_line): Fix stdout -> stdout in
	comment.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [FT32] Replace hard-coded instruction patterns with macros
@ 2015-09-29 17:05 sergiodj+buildbot
  2015-09-29 18:01 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-09-29 17:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 86feccb92092506f2a23a32345bc0f562ac4042b ***

Author: jamesbowman <jamesb@excamera.com>
Branch: master
Commit: 86feccb92092506f2a23a32345bc0f562ac4042b

[FT32] Replace hard-coded instruction patterns with macros

The stack unwinder can now use FT32_*() macros to interpet binary
instructions instead of local definitions.

2015-09-29  James Bowman  <james.bowman@ftdichip.com>

	* ft32-tdep.c: #include "opcode/ft32.h".
	Delete local macros IS_PUSH, PUSH_REG, IS_LINK, LINK_SIZE.
	(ft32_analyze_prologue): Use FT32_* macros.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Rebase patch #7
@ 2015-09-29 17:29 sergiodj+buildbot
  2015-09-29 20:44 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-09-29 17:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4f714dd43efde465c7f2272ee444ccd2f1b3a1b5 ***

Author: jamesbowman <jamesb@excamera.com>
Branch: master
Commit: 4f714dd43efde465c7f2272ee444ccd2f1b3a1b5

Rebase patch #7


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Undo accidental commit
@ 2015-09-29 18:14 sergiodj+buildbot
  2015-09-29 21:10 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-09-29 18:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0bcf3dd6905d67936815411b42dab6fd4c47b4db ***

Author: jamesbowman <jamesb@excamera.com>
Branch: master
Commit: 0bcf3dd6905d67936815411b42dab6fd4c47b4db

Undo accidental commit


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] sim: ft32: correct simulation of MEMCPY and MEMSET
@ 2015-09-30  5:04 sergiodj+buildbot
  2015-09-30  6:11 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-09-30  5:04 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 395b0d8a3fdd8915a4897b9b925d56fa42745dcc ***

Author: James Bowman <james.bowman@ftdichip.com>
Branch: master
Commit: 395b0d8a3fdd8915a4897b9b925d56fa42745dcc

sim: ft32: correct simulation of MEMCPY and MEMSET

The MEMCPY and MEMSET instructions should only examine the low 15 bits of
their length arguments.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Add fdpic and misc targets to config.bfd for sh*-*-linux*
@ 2015-09-30  6:50 sergiodj+buildbot
  2015-09-30 12:48 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-09-30  6:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6c4f2328aba04ffacce9a4033fd253222e2ea1aa ***

Author: Rich Felker <dalias@libc.org>
Branch: master
Commit: 6c4f2328aba04ffacce9a4033fd253222e2ea1aa

Add fdpic and misc targets to config.bfd for sh*-*-linux*


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Also check e_machine when merging sections
@ 2015-09-30 13:26 sergiodj+buildbot
  2015-09-30 14:00 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-09-30 13:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9865bd0da6e59c3a1c55605b5a6a9283ed4d542c ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 9865bd0da6e59c3a1c55605b5a6a9283ed4d542c

Also check e_machine when merging sections

When we check consistency for merge ELF sections, we should not only
check EI_CLASS, but also compatible e_machine.

bfd/

	PR ld/19013
	* elflink.c (_bfd_elf_merge_sections): Only merge input bfds
	that have the compatible ELF machine code with the output bfd.

ld/testsuite/

	PR ld/19013
	* ld-x86-64/pr19013-nacl.d: New file.
	* ld-x86-64/pr19013-x32.d: Likewise.
	* ld-x86-64/pr19013.d: Likewise.
	* ld-x86-64/pr19013.s: Likewise.
	* ld-x86-64/x86-64.exp: Run PR ld/19013 tests.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] btrace, testsuite: fix spurious gdb.btrace/tsx.exp fails
@ 2015-09-30 13:35 sergiodj+buildbot
  2015-09-30 15:27 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-09-30 13:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 77ba2a67960d05991a3e3641049cac649ca04c96 ***

Author: Markus Metzger <markus.t.metzger@intel.com>
Branch: master
Commit: 77ba2a67960d05991a3e3641049cac649ca04c96

btrace, testsuite: fix spurious gdb.btrace/tsx.exp fails

If the atomic section in x86-tsx.S is aborted, the tsx.exp test will fail
even if the traced output is actually correct.

Consider abort scenarios in the test.

testsuite/
	* gdb.btrace/tsx.exp: Consider multiple correct outputs in the record
	instruction-history test.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] infcmd.c: Don't attempt to record a NULL value after a finish command.
@ 2015-09-30 13:51 sergiodj+buildbot
  2015-09-30 15:56 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-09-30 13:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT aca20ec47359776488863193660cf9fd2fe3cfe7 ***

Author: Kevin Buettner <kevinb@redhat.com>
Branch: master
Commit: aca20ec47359776488863193660cf9fd2fe3cfe7

infcmd.c: Don't attempt to record a NULL value after a finish command.

Architectures which use RETURN_VALUE_STRUCT_CONVENTION will have a
NULL return value after executing a finish command.  See get_return_value()
in infcmd.c.

This patch avoids an eventual SIGSEV (caused by attempting to
derefrence a NULL pointer) by adding a suitable test to
finish_command_fsm_should_stop().

I encountered this problem while testing msp430:

(gdb) PASS: gdb.base/structs.exp: zed L<n> for finish; return 1 structs-tc
finish
Run till exit from #0  fun1 () at /ironwood1/sourceware-git/msp430-elf/../binutils-gdb/gdb/testsuite/gdb.base/structs.c:125
ERROR: Process no longer exists

gdb/ChangeLog:
    	* infcmd.c (finish_command_fsm_should_stop): Don't attempt to
    	record a NULL value.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] py-type.exp: Do not run tests if binary fails to build
@ 2015-09-30 15:14 sergiodj+buildbot
  2015-09-30 17:17 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-09-30 15:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e019fd1d143061c703691b862f1e282be57b2983 ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: e019fd1d143061c703691b862f1e282be57b2983

py-type.exp: Do not run tests if binary fails to build

I noticed this while working on the test case.  I believe it would make
sense to skip running the tests if the binary failed to build.  Although
I would understand the opposite argument: if the binary does not build
for some reason, we probably want to know about it, and some catastrophic
failures in the tests might alarm us better than a timid "UNTESTED".

gdb/testsuite/ChangeLog:

	* gdb.python/py-type.exp: Do not run tests if binaries fail to
	build.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Shorten long lines in linux-aarch64-low.c
@ 2015-09-30 15:42 sergiodj+buildbot
  2015-09-30 18:03 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-09-30 15:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7781c06f6e735e92fcf597c578540c2f925a9f05 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 7781c06f6e735e92fcf597c578540c2f925a9f05

Shorten long lines in linux-aarch64-low.c

Happen to see these lines are too long.  This patch shortens them.

gdb/gdbserver:

2015-09-30  Yao Qi  <yao.qi@linaro.org>

	* linux-aarch64-low.c (emit_movk): Shorten a long line.
	(emit_load_store_pair): Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Create a PLT entry for R_386_PC32 in non-code sections
@ 2015-09-30 16:59 sergiodj+buildbot
  2015-09-30 20:14 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-09-30 16:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4b627c18440f51077f8fd4c18adaa3919c3a373e ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 4b627c18440f51077f8fd4c18adaa3919c3a373e

Create a PLT entry for R_386_PC32 in non-code sections

Since something like ".long foo - ." may be used as pointer, we make
sure that PLT is used if foo is a function defined in a shared library.

bfd/

	PR ld/19031
	* elf32-i386.c (elf_i386_check_relocs): Set
	pointer_equality_needed for R_386_PC32 reloc in non-code
	sections.

ld/testsuite/

	PR ld/19031
	* ld-i386/i386.exp: Run PR ld/19031 test.
	* ld/testsuite/ld-i386/pr19031.out: New file.
	* ld/testsuite/ld-i386/pr19031a.c: Likewise.
	* ld/testsuite/ld-i386/pr19031b.S: Likewise.
	* ld/testsuite/ld-i386/pr19031c.c: Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Resync files in the binutils repository that are maintained in the gcc repository.
@ 2015-09-30 17:44 sergiodj+buildbot
  2015-09-30 22:23 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-09-30 17:44 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6899683948c66a81ae470efc0869ea01e489e9cd ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: 6899683948c66a81ae470efc0869ea01e489e9cd

Resync files in the binutils repository that are maintained in the gcc repository.

.	2015-08-23  Francois-Xavier Coudert  <fxcoudert@gcc.gnu.org>

	PR libfortran/54572
	* Makefile.def: Make libgfortran depend on libbacktrace.
	* Makefile.in: Regenerate.

	2015-08-12  Tom de Vries  <tom@codesourcery.com>

	PR other/67092
	PR other/67098
	* configure.ac: Remove --with_host_libstdcxx support.
	* configure: Regenerate.

	2015-08-10  Thomas Schwinge  <thomas@codesourcery.com>
	    Jakub Jelinek  <jakub@redhat.com>

	* configure.ac (noconfigdirs): Don't add "target-libgomp" for target
	nvptx*-*-*.
	* configure: Regenerate.

include	2015-08-14  Pierre-Marie de Rodat  <derodat@adacore.com>

	* dwarf2.def (DW_AT_GNU_bias): New attribute.

	2015-08-14  Pierre-Marie de Rodat  <derodat@adacore.com>

	* dwarf2.def (DW_AT_GNU_numerator, DW_AT_GNU_denominator): New
	attributes.

libiberty  2015-08-15  Ian Lance Taylor  <iant@google.com>

	* cp-demangle.c (d_abi_tags): Preserve di->last_name across any
	ABI tags.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Call strprefix instead of strncmp in event parsing
@ 2015-09-30 18:38 sergiodj+buildbot
  2015-09-30 22:55 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-09-30 18:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6ab24463cb63af792c958ab4455d630b5936f1b1 ***

Author: Don Breazeal <donb@codesourcery.com>
Branch: master
Commit: 6ab24463cb63af792c958ab4455d630b5936f1b1

Call strprefix instead of strncmp in event parsing

This fixes a typo that used strncmp instead of strprefix when
checking for an exec event in a stop reply packet.

gdb/ChangeLog:

	* remote.c (remote_parse_stop_reply): Call strprefix instead
	of strncmp.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] bfd/config.bfd: Drop non-linux non-fdpic stuff from the last change of targ_selvecs of sh*-linux cases
@ 2015-10-01  5:31 sergiodj+buildbot
  2015-10-01  6:00 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-01  5:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT de48f481b1769866ad8da5923792a49420a2d157 ***

Author: Kaz Kojima <kkojima@rr.iij4u.or.jp>
Branch: master
Commit: de48f481b1769866ad8da5923792a49420a2d157

bfd/config.bfd: Drop non-linux non-fdpic stuff from the last change of targ_selvecs of sh*-linux cases


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] vec.h: Add casts for C++ compat
@ 2015-10-01 15:37 sergiodj+buildbot
  2015-10-01 16:06 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-01 15:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT dd0a637a3d8f5ca7229131c085ef6b8e255d01f6 ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: dd0a637a3d8f5ca7229131c085ef6b8e255d01f6

vec.h: Add casts for C++ compat

gdb/ChangeLog:

	* common/vec.h (VEC_OP (T,cleanup)): Add pointer cast.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [aarch64] Remove argument pc from disas_aarch64_insn
@ 2015-10-02 14:38 sergiodj+buildbot
  2015-10-02 15:06 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-02 14:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7232d38966babb802e9d8d0e9e591346a7b93d96 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 7232d38966babb802e9d8d0e9e591346a7b93d96

[aarch64] Remove argument pc from disas_aarch64_insn

I happen to see that argument pc is not used inside disas_aarch64_insn
at all.  This patch is to remove it.

OK to apply?

opcodes:

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

	* aarch64-dis.c (disas_aarch64_insn): Remove argument PC.
	(print_insn_aarch64_word): Caller updated.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [aarch64] expose disas_aarch64_insn and rename it to aarch64_decode_insn
@ 2015-10-02 14:46 sergiodj+buildbot
  2015-10-02 16:08 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-02 14:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 36f4aab18ccf897b405f137d6cd4f9673bd947fc ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 36f4aab18ccf897b405f137d6cd4f9673bd947fc

[aarch64] expose disas_aarch64_insn and rename it to aarch64_decode_insn

We want to use disas_aarch64_insn inside GDB to decode instructions, so
this patch exposes it and rename it to aarch64_decode_insn to follow
the conventions of other interfaces.

include/opcode:

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

	* aarch64.h (aarch64_decode_insn): Declare it.

opcodes:

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

	* aarch64-dis.c	(disas_aarch64_insn): Remove static.  Change
	argument insn type to aarch64_insn.  Rename to ...
	(aarch64_decode_insn): ... it.
	(print_insn_aarch64_word): Caller updated.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [BFD][AARCH64]Refactor to facilitate further large memory model support patches.
@ 2015-10-02 17:14 sergiodj+buildbot
  2015-10-02 18:11 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-02 17:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a0becb8948afaf3dcb7c39884464a51aa35a9cd9 ***

Author: Renlin Li <renlin.li@arm.com>
Branch: master
Commit: a0becb8948afaf3dcb7c39884464a51aa35a9cd9

[BFD][AARCH64]Refactor to facilitate further large memory model support patches.

bfd/

2015-10-02  Renlin Li  <renlin.li@arm.com>

	* elfnn-aarch64.c (elfNN_aarch64_final_link_relocate): Change if to
	switch statement.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [GAS][AARCH64]Add BFD_RELOC_AARCH64_MOVW_GOTOFF_G1 Support.
@ 2015-10-02 17:31 sergiodj+buildbot
  2015-10-02 20:09 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-02 17:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 654248e7f702887c5a43bf402cd6080734f57819 ***

Author: Renlin Li <renlin.li@arm.com>
Branch: master
Commit: 654248e7f702887c5a43bf402cd6080734f57819

[GAS][AARCH64]Add BFD_RELOC_AARCH64_MOVW_GOTOFF_G1 Support.

bfd/

2015-10-02  Renlin Li  <renlin.li@arm.com>

	* reloc.c (BFD_RELOC_AARCH64_MOVW_GOTOFF_G1): New.
	* elfnn-aarch64.c (elfNN_aarch64_howto_table): New entry for
	MOVW_GOTOFF_G1.
	* libbfd.h: Regenerate.
	* bfd-in2.h: Regenerate.

gas/

2015-10-02  Renlin Li  <renlin.li@arm.com>

	* config/tc-aarch64.c (reloc_table): New relocation modifier
	gotoff_g1.
	(process_movw_reloc_info): Support newly added modifier.
	(md_apply_fix): Likewise.

gas/testsuite/

2015-10-02  Renlin Li  <renlin.li@arm.com>

	* gas/aarch64/reloc-gotoff_g1.s: New.
	* gas/aarch64/reloc-gotoff_g1.d: New.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [LD][AARCH64]Add BFD_RELOC_AARCH64_MOVW_GOTOFF_G1 Support.
@ 2015-10-02 17:39 sergiodj+buildbot
  2015-10-02 21:09 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-02 17:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 74a1bfe1d6e7e85fffad518f50575a44630d9293 ***

Author: Renlin Li <renlin.li@arm.com>
Branch: master
Commit: 74a1bfe1d6e7e85fffad518f50575a44630d9293

[LD][AARCH64]Add BFD_RELOC_AARCH64_MOVW_GOTOFF_G1 Support.

bfd/

2015-10-02  Renlin Li  <renlin.li@arm.com>

	* elfnn-aarch64.c (aarch64_reloc_got_type): Add support
	for BFD_RELOC_AARCH64_MOVW_GOTOFF_G1.
	(elfNN_aarch64_gc_sweep_hook): Likewise.
	(elfNN_aarch64_check_relocs): Likewise
	* elfxx-aarch64.c (_bfd_aarch64_elf_put_addend): Likewise.
	(_bfd_aarch64_elf_resolve_relocation): Likewise
	(elfNN_aarch64_final_link_relocate): Calculate offset within GOT.

ld/testsuite/

2015-10-02  Renlin Li  <renlin.li@arm.com>

	* ld-aarch64/emit-relocs-302.d: New.
	* ld-aarch64/emit-relocs-302.s: New.
	* ld-aarch64/aarch64-elf.exp: Run the new test.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [LD][AARCH64]Add BFD_RELOC_AARCH64_LD64_GOTOFF_LO15 Support.
@ 2015-10-02 17:40 sergiodj+buildbot
  2015-10-02 19:10 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-02 17:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a2e1db00c76bcad0594654d78af76d0e12a217ee ***

Author: Renlin Li <renlin.li@arm.com>
Branch: master
Commit: a2e1db00c76bcad0594654d78af76d0e12a217ee

[LD][AARCH64]Add BFD_RELOC_AARCH64_LD64_GOTOFF_LO15 Support.

bfd/

2015-10-02  Renlin Li  <renlin.li@arm.com>

	* elfnn-aarch64.c (aarch64_reloc_got_type): Add
	BFD_RELOC_AARCH64_LD_64_GOTOFF_LO15 support.
	(elfNN_aarch64_gc_sweep_hook): Likewise.
	(elfNN_aarch64_check_relocs): Likewise
	* elfxx-aarch64.c (_bfd_aarch64_elf_put_addend): Likewise.
	(_bfd_aarch64_elf_resolve_relocation): Likewise
	(elfNN_aarch64_final_link_relocate): Calculate offset within GOT.

ld/testsuite/

2015-10-02  Renlin Li  <renlin.li@arm.com>

	* ld-aarch64/emit-relocs-310.d: New.
	* ld-aarch64/emit-relocs-310.s: New.
	* ld-aarch64/aarch64-elf.exp: Run the test.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [GAS][AARCH64]Add BFD_RELOC_AARCH64_MOVW_GOTOFF_G0_NC Support.
@ 2015-10-02 17:47 sergiodj+buildbot
  2015-10-02 22:09 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-02 17:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ca632371cebf83eb9b5ce951bbe734e7636aa614 ***

Author: Renlin Li <renlin.li@arm.com>
Branch: master
Commit: ca632371cebf83eb9b5ce951bbe734e7636aa614

[GAS][AARCH64]Add BFD_RELOC_AARCH64_MOVW_GOTOFF_G0_NC Support.

bfd/

2015-10-02  Renlin Li <renlin.li@arm.com>

	* reloc.c (BFD_RELOC_AARCH64_MOVW_GOTOFF_G0_NC): New.
	* elfnn-aarch64.c (elfNN_aarch64_howto_table): New entry
	MOVW_GOTOFF_G0_NC.
	* libbfd.h: Regnerate.
	* bfd-in2.h: Regenerate.

gas/

2015-10-02  Renlin Li <renlin.li@arm.com>

	* config/tc-aarch64.c (reloc_table): New relocation modifier
	gotoff_g0_nc.
	(process_movw_reloc_info): Support gotoff_g0_nc.
	(md_apply_fix): Likewise.

gas/testsuite/

2015-10-02  Renlin Li <renlin.li@arm.com>

	* gas/aarch64/reloc-gotoff_g0_nc.s: New.
	* gas/aarch64/reloc-gotoff_g0_nc.d: New.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [LD][AARCH64]Add BFD_RELOC_AARCH64_MOVW_GOTOFF_G0_NC Support.
@ 2015-10-02 17:55 sergiodj+buildbot
  2015-10-02 23:09 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-02 17:55 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT dc8008f508bb39ccbca49ea71a7d5c70571c4685 ***

Author: Renlin Li <renlin.li@arm.com>
Branch: master
Commit: dc8008f508bb39ccbca49ea71a7d5c70571c4685

[LD][AARCH64]Add BFD_RELOC_AARCH64_MOVW_GOTOFF_G0_NC Support.

bfd/

2015-10-02  Renlin Li <renlin.li@arm.com>

	* elfnn-aarch64.c (aarch64_reloc_got_type): Add
	BFD_RELOC_AARCH64_MOVW_GOTOFF_G0_NC support.
	(elfNN_aarch64_final_link_relocate): Likewise.
	(elfNN_aarch64_gc_sweep_hook): Likewise.
	(elfNN_aarch64_check_relocs): Likewise.
	* elfxx-aarch64.c (_bfd_aarch64_elf_put_addend): Likewise.
	(_bfd_aarch64_elf_resolve_relocation): Likewise.

ld/testsuite/

2015-10-02  Renlin Li <renlin.li@arm.com>

	* ld-aarch64/aarch64-elf.exp: Run new test.
	* ld-aarch64/emit-relocs-301.d: New.
	* ld-aarch64/emit-relocs-301.s: New.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [GAS][AARCH64]Add BFD_RELOC_AARCH64_TLSGD_MOVW_G1 support.
@ 2015-10-02 18:03 sergiodj+buildbot
  2015-10-03  0:10 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-02 18:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1aa66fb1527c3c81fef2a39a3a3ec9d36f1cfdec ***

Author: Renlin Li <renlin.li@arm.com>
Branch: master
Commit: 1aa66fb1527c3c81fef2a39a3a3ec9d36f1cfdec

[GAS][AARCH64]Add BFD_RELOC_AARCH64_TLSGD_MOVW_G1 support.

bfd/

2015-10-02  Renlin Li <renlin.li@arm.com>

	* reloc.c (BFD_RELOC_AARCH64_TLSGD_MOVW_G1): New entry.
	* elfnn-aarch64.c (elfNN_aarch64_howto_table): New entry for
	BFD_RELOC_AARCH64_TLSGD_MOVW_G1.
	* bfd-in2.h: Regenerate.
	* libbfd.h: Likewise.

gas/

2015-10-02  Renlin Li <renlin.li@arm.com>

	* config/tc-aarch64.c (reloc_table): New relocation modifier tlsgd_g1.
	(process_movw_reloc_info): Support BFD_RELOC_AARCH64_TLSGD_MOVW_G1.
	(md_apply_fix): Likewise.
	(aarch64_force_relocation): Likewise.

gas/testsuite/

2015-10-02  Renlin Li <renlin.li@arm.com>

	* gas/aarch64/reloc-tlsgd_g1.s: New.
	* gas/aarch64/reloc-tlsgd_g1.s: New.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [LD][AARCH64]Add BFD_RELOC_AARCH64_TLSGD_MOVW_G1 support.
@ 2015-10-02 18:11 sergiodj+buildbot
  2015-10-03  2:54 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-02 18:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 94facae3374655816798d1d505b447f81db4759d ***

Author: Renlin Li <renlin.li@arm.com>
Branch: master
Commit: 94facae3374655816798d1d505b447f81db4759d

[LD][AARCH64]Add BFD_RELOC_AARCH64_TLSGD_MOVW_G1 support.

bfd/

2015-10-02  Renlin Li <renlin.li@arm.com>

	* elfnn-aarch64.c (aarch64_reloc_got_type): Add
	BFD_RELOC_AARCH64_TLSGD_MOVW_G1 support.
	(elfNN_aarch64_final_link_relocate): Likewise.
	(elfNN_aarch64_relocate_section): Likewise.
	(elfNN_aarch64_gc_sweep_hook): Likewise.
	(elfNN_aarch64_check_relocs): Likewise.
	* elfxx-aarch64.c (_bfd_aarch64_elf_put_addend): Likewise.
	(_bfd_aarch64_elf_resolve_relocation): Likewise.

ld/testsuite

2015-10-02  Renlin Li <renlin.li@arm.com>

	* ld-aarch64/emit-relocs-515.d: New.
	* ld-aarch64/emit-relocs-515.s: New.
	* ld-aarch64/aarch64-elf.exp: Run new test.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [GAS][AARCH64]Add BFD_RELOC_AARCH64_TLSGD_MOVW_G0_NC support.
@ 2015-10-02 18:19 sergiodj+buildbot
  2015-10-03  4:55 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-02 18:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3e8286c0d2f6f94fcbc38a2233d85b90ca4040c0 ***

Author: Renlin Li <renlin.li@arm.com>
Branch: master
Commit: 3e8286c0d2f6f94fcbc38a2233d85b90ca4040c0

[GAS][AARCH64]Add BFD_RELOC_AARCH64_TLSGD_MOVW_G0_NC support.

bfd/

2015-10-02  Renlin Li <renlin.li@arm.com>

	* reloc.c (BFD_RELOC_AARCH64_TLSGD_MOVW_G0_NC): New entry.
	* elfnn-aarch64.c (elfNN_aarch64_howto_table): New entry for
	BFD_RELOC_AARCH64_TLSGD_MOVW_G0_NC.
	* libbfd.h: Regenerate.
	* bfd-in2.h: Likewise

gas/

2015-10-02  Renlin Li <renlin.li@arm.com>

	* config/tc-aarch64.c (reloc_table): New relocation modifier tlsgd_g0_nc.
	(process_movw_reloc_info): Support BFD_RELOC_AARCH64_TLSGD_MOVW_G1.
	(md_apply_fix): Likewise.
	(aarch64_force_relocation): Likewise.

gas/testsuite/

2015-10-02  Renlin Li <renlin.li@arm.com>

	* gas/aarch64/reloc-tlsgd_g0_nc.d: New.
	* gas/aarch64/reloc-tlsgd_g0_nc.s: New.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [LD][AARCH64]Add BFD_RELOC_AARCH64_TLSGD_MOVW_G0_NC support.
@ 2015-10-02 18:27 sergiodj+buildbot
  2015-10-03  6:49 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-02 18:27 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7ba7cfe43195305f5efa887ebbffb53a724aaac6 ***

Author: Renlin Li <renlin.li@arm.com>
Branch: master
Commit: 7ba7cfe43195305f5efa887ebbffb53a724aaac6

[LD][AARCH64]Add BFD_RELOC_AARCH64_TLSGD_MOVW_G0_NC support.

bfd/

2015-10-02  Renlin Li <renlin.li@arm.com>

	* elfnn-aarch64.c (aarch64_reloc_got_type): Add
	BFD_RELOC_AARCH64_TLSGD_MOVW_G0_NC support.
	(elfNN_aarch64_final_link_relocate): Likewise.
	(elfNN_aarch64_relocate_section): Likewise.
	(elfNN_aarch64_gc_sweep_hook): Likewise.
	(elfNN_aarch64_check_relocs): Likewise.
	* elfxx-aarch64.c (_bfd_aarch64_elf_put_addend): Likewise.
	(_bfd_aarch64_elf_resolve_relocation): Likewise.

ld/testsuite/

2015-10-02  Renlin Li <renlin.li@arm.com>

	* ld-aarch64/emit-relocs-516.d: New.
	* ld-aarch64/emit-relocs-516.s: New.
	* ld-aarch64/aarch64-elf.exp: Run new test.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [BFD][AARCH64]Create GOT section for TLSLE_MOVW_TPREL_G(1, 1_NC, 2).
@ 2015-10-02 18:42 sergiodj+buildbot
  2015-10-03  9:37 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-02 18:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b7a944fea3a0194d81f6de4d958f3a1d2c6ad03a ***

Author: Renlin Li <renlin.li@arm.com>
Branch: master
Commit: b7a944fea3a0194d81f6de4d958f3a1d2c6ad03a

[BFD][AARCH64]Create GOT section for TLSLE_MOVW_TPREL_G(1, 1_NC, 2).

bfd/

2015-10-02  Renlin Li <renlin.li@arm.com>

	* elfnn-aarch64.c (elfNN_aarch64_check_relocs): Create GOT section
	for TLSLE_MOVW_TPREL_G(1, 1_NC, 2) relocation.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [GAS][AARCH64]Add TLSDESC large memory model support.
@ 2015-10-02 18:57 sergiodj+buildbot
  2015-10-03 11:41 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-02 18:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 43a357f99fc8c6535d064c5bce4b2865aa33bdd2 ***

Author: Renlin Li <renlin.li@arm.com>
Branch: master
Commit: 43a357f99fc8c6535d064c5bce4b2865aa33bdd2

[GAS][AARCH64]Add TLSDESC large memory model support.

bfd/

2015-10-02  Renlin Li <renlin.li@arm.com>

	* elfnn-aarch64.c (elfNN_aarch64_howto_table): Check overflow for
	BFD_RELOC_AARCH64_TLSDESC_OFF_G1.

gas/

2015-10-02  Renlin Li <renlin.li@arm.com>

	* config/tc-aarch64.c (s_tlsdescadd): New.
	(s_tlsdescldr): New.
	(md_pseudo_table): Handle tlsdescadd and tlsdescldr pseudo ops.
	(reloc_table): Add entries for BFD_RELOC_AARCH64_TLSDESC_OFF_G0_NC and
	BFD_RELOC_AARCH64_TLSDESC_OFF_G0_NC.
	(process_movw_reloc_info): Support AARCH64_TLSDESC_OFF_G1 and
	    AARCH64_TLSDESC_OFF_G0_NC.
	(md_apply_fix): Likewise.
	(aarch64_force_relocation): Likewise.

gas/testsuite/

2015-10-02  Renlin Li <renlin.li@arm.com>

	* gas/aarch64/reloc-tlsdesc_off_g0_nc.d: New.
	* gas/aarch64/reloc-tlsdesc_off_g0_nc.s: New.
	* gas/aarch64/reloc-tlsdesc_off_g1.d: New.
	* gas/aarch64/reloc-tlsdesc_off_g1.s: New.
	* gas/aarch64/tls-desc.d: New.
	* gas/aarch64/tls-desc.s: New.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [LD][AARCH64]Add TLSIE relaxation support under large memory model.
@ 2015-10-02 19:13 sergiodj+buildbot
  2015-10-03 13:41 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-02 19:13 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3ebe65c0ff9f8f76c9971b1cc078273298f0c693 ***

Author: Renlin Li <renlin.li@arm.com>
Branch: master
Commit: 3ebe65c0ff9f8f76c9971b1cc078273298f0c693

[LD][AARCH64]Add TLSIE relaxation support under large memory model.

bfd/
2015-10-02  Renlin Li <renlin.li@arm.com>

	* elfnn-aarch64.c (IS_AARCH64_TLS_RELAX_RELOC): Add
	TLSIE_MOVW_GOTTPREL_G1.
	(aarch64_tls_transition_without_check): Add
	TLSIE_MOVW_GOTTPREL_G1 to TLSLE_MOVW_TPREL_G2
	transition for local symbol.
	(elfNN_aarch64_tls_relax): Add a argument to pass tp offset.
	Add TLSIE_MOVW_GOTTPREL_G1 relaxation.
	(elfNN_aarch64_relocate_section): Call elfNN_aarch64_tls_relax
	with new argument.

ld/testsuite/
2015-10-02  Renlin Li <renlin.li@arm.com>

	* ld-aarch64/aarch64-elf.exp (tls-relax-large-le-ie): Run new test.
	* ld-aarch64/tls-relax-large-ie-le.d: New.
	* ld-aarch64/tls-relax-large-ie-le.s: New.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [Binutils][AARCH64]Add TLS IE large memory support.
@ 2015-10-02 21:25 sergiodj+buildbot
  2015-10-03  8:35 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-02 21:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3b957e5b074407e18782a9592754c732671df8ed ***

Author: Renlin Li <renlin.li@arm.com>
Branch: master
Commit: 3b957e5b074407e18782a9592754c732671df8ed

[Binutils][AARCH64]Add TLS IE large memory support.

bfd/

2015-10-02  Renlin Li <renlin.li@arm.com>

	* reloc.c: Make AARCH64_TLSIE_MOVW_GOTTPREL_G1 and
	AARCH64_TLSIE_MOVW_GOTTPREL_G0_NC defined in alphabetical order.
	* libbfd.h: Regenerate.
	* bfd-in2.h: Likewise.
	* elfnn-aarch64.c (elfNN_aarch64_howto_table): Make
	TLSIE_MOVW_GOTTPREL_G1 check overflow.
	(aarch64_reloc_got_type): Add support for TLSIE_MOVW_GOTTPREL_G1
	and TLSIE_MOVW_GOTTPREL_G0_NC.
	(elfNN_aarch64_final_link_relocate): Likewise.
	(elfNN_aarch64_relocate_section): Likewise.
	(elfNN_aarch64_gc_sweep_hook): Likewise.
	(elfNN_aarch64_check_relocs): Likewise.
	* elfxx-aarch64.c (_bfd_aarch64_elf_put_addend): Likewise.
	(_bfd_aarch64_elf_resolve_relocation): Likewise.

gas/

2015-10-02  Renlin Li <renlin.li@arm.com>

	* config/tc-aarch64.c (reloc_table): Add two entries for
	gottprel_g0_nc and gottprel_g1.
	(process_movw_reloc_info): Add support.
	(md_apply_fix): Likewise.
	(aarch64_force_relocation): Likewise.

gas/testsuite/

2015-10-02  Renlin Li <renlin.li@arm.com>

	* gas/aarch64/reloc-gottprel_g0_nc.d: New.
	* gas/aarch64/reloc-gottprel_g0_nc.s: New.
	* gas/aarch64/reloc-gottprel_g1.d: New.
	* gas/aarch64/reloc-gottprel_g1.s: New.

ld/testsuite/

2015-10-02  Renlin Li <renlin.li@arm.com>

	* ld-aarch64/tls-large-ie.d: New.
	* ld-aarch64/tls-large-ie.s: New.
	* ld-aarch64/aarch64-elf.exp: Run new test.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix gdb.dwarf2/staticvirtual.exp regexp.
@ 2015-10-02 23:54 sergiodj+buildbot
  2015-10-03 14:41 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-02 23:54 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 06e635ef635f61c5f5c3b9ff16d4c813e3db2452 ***

Author: Sandra Loosemore <sandra@codesourcery.com>
Branch: master
Commit: 06e635ef635f61c5f5c3b9ff16d4c813e3db2452

Fix gdb.dwarf2/staticvirtual.exp regexp.

2015-10-02  Sandra Loosemore  <sandra@codesourcery.com>

	gdb/testsuite/
	* gdb.dwarf2/staticvirtual.exp: Generalize regexp so it can match
	whether or not address 0x1000 is mapped on the target.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [FT32] gdb: Correctly interpret function prologs
@ 2015-10-03  0:44 sergiodj+buildbot
  2015-10-03 15:40 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-03  0:44 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ae4e25019d53d38b2ad50475c80fa99ecab94c5c ***

Author: jamesbowman <jamesb@excamera.com>
Branch: master
Commit: ae4e25019d53d38b2ad50475c80fa99ecab94c5c

[FT32] gdb: Correctly interpret function prologs

The stack unwinder did not understand the function prologs
generated by gcc with -Os. Add code to recognize and interpret the
prolog calls.

[gdb]

2015-10-02  James Bowman  <james.bowman@ftdichip.com>

	* ft32-tdep.c (ft32_analyze_prologue): Add function prolog
	subroutine handling.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Enable IAMCU and PEI for Solaris2/x86
@ 2015-10-04 14:52 sergiodj+buildbot
  2015-10-04 15:21 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-04 14:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d00c2bc9c0567b6eb7d64ac4dee27b8a8dc2cedb ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: d00c2bc9c0567b6eb7d64ac4dee27b8a8dc2cedb

Enable IAMCU and PEI for Solaris2/x86

bfd/

	* config.bfd (targ_selvecs, targ64_selvecs): Add iamcu_elf32_vec,
	i386_pei_vec and x86_64_pei_vec for Solaris2/x86.

ld/

	* configure.tgt (targ_extra_emuls): Add elf_iamcu for Solaris2/x86.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] parse load_offset (bias) of restore command as long
@ 2015-10-06 16:41 sergiodj+buildbot
  2015-10-06 17:09 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-06 16:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cbd641edf3323ce354c0bc7eb54496057040b564 ***

Author: Pitchumani Sivanupandi <pitchumani.s@atmel.com>
Branch: master
Commit: cbd641edf3323ce354c0bc7eb54496057040b564

parse load_offset (bias) of restore command as long

Following failures are noticed for avr-gdb. This may be the case
for targets like AVR which has integer_to_address hook defined.

FAIL: gdb.base/dump.exp: struct copy, srec; value restored ok
FAIL: gdb.base/dump.exp: struct copy, ihex; value restored ok
FAIL: gdb.base/dump.exp: struct copy, tekhex; value restored ok

These tests are failed because load_offset(bias) of restore command
parsed as address.

command: restore filename [binary] bias start end

Except binary, other BFDs have a built-in location; gdb restores content
at offset 'bias' from that location. So, 'bias' of 'restore' command should
be parsed as address only when the file is binary.

Below patch changes gdb to parse 'bias' as long if the file is not binary.

gdb/ChangeLog

2015-10-06  Pitchumani Sivanupandi  <pitchumani.s@atmel.com>

	* cli/cli-dump.c (restore_command): Parse load_offset (bias) as address
	only when the file is binary.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] New ARC implementation.
@ 2015-10-07 13:26 sergiodj+buildbot
  2015-10-07 14:00 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-07 13:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 886a250647ac0c608f20a7007fc2167a70f64e20 ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: 886a250647ac0c608f20a7007fc2167a70f64e20

New ARC implementation.

bfd	* archures.c: Remove support for older ARC. Added support for new
	ARC cpus (ARC600, ARC601, ARC700, ARCV2).
	* bfd-in2.h: Likewise.
	* config.bfd: Likewise.
	* cpu-arc.c: Likewise.
	* elf32-arc.c: Totally changed file with a refactored
	inplementation of the ARC port.
	* libbfd.h: Added ARC specific relocation types.
	* reloc.c: Likewise.

gas     * config/tc-arc.c: Revamped file for ARC support.
        * config/tc-arc.h: Likewise.
        * doc/as.texinfo: Add new ARC options.
        * doc/c-arc.texi: Likewise.

ld	* configure.tgt: Added target arc-*-elf* and arc*-*-linux-uclibc*.
	* emulparams/arcebelf_prof.sh: New file
	* emulparams/arcebelf.sh: Likewise.
	* emulparams/arceblinux_prof.sh: Likewise.
	* emulparams/arceblinux.sh: Likewise.
	* emulparams/arcelf_prof.sh: Likewise.
	* emulparams/arcelf.sh: Likewise.
	* emulparams/arclinux_prof.sh: Likewise.
	* emulparams/arclinux.sh: Likewise.
	* emulparams/arcv2elfx.sh: Likewise.
	* emulparams/arcv2elf.sh: Likewise.
	* emultempl/arclinux.em: Likewise.
	* scripttempl/arclinux.sc: Likewise.
	* scripttempl/elfarc.sc: Likewise.
	* scripttempl/elfarcv2.sc: Likewise
	* Makefile.am: Add new ARC emulations.
	* Makefile.in: Regenerate.
	* NEWS: Mention the new feature.

opcodes * arc-dis.c: Revamped file for ARC support
	* arc-dis.h: Likewise.
	* arc-ext.c: Likewise.
	* arc-ext.h: Likewise.
	* arc-opc.c: Likewise.
	* arc-fxi.h: New file.
	* arc-regs.h: Likewise.
	* arc-tbl.h: Likewise.

binutils * readelf.c (get_machine_name): Remove A5 reference. Add ARCompact
	and ARCv2.
	(get_machine_flags): Handle EM_ARCV2 and EM_ARCOMPACT.
	(guess_is_rela): Likewise.
	(dump_relocations): Likewise.
	(is_32bit_abs_reloc): Likewise.
	(is_16bit_abs_reloc): Likewise.
	(is_none_reloc): Likewise.
	* NEWS: Mention the new feature.

include	* dis-asm.h (arc_get_disassembler): Correct declaration.
	* arc-reloc.def: Macro file with definition of all relocation
	types.
	* arc.h: Changed macros for the newly supported ARC cpus.  Altered
	enum defining the supported relocations.
	* common.h: Changed EM_ARC_A5 definition to EM_ARC_COMPACT. Added
	macro for EM_ARC_COMPACT2.
        * arc-func.h: New file.
        * arc.h: Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Wrap include/opcode/aarch64.h in extern "C" for C++
@ 2015-10-07 14:11 sergiodj+buildbot
  2015-10-07 14:59 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-07 14:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d3e12b29aef25bc9d1830b0a05643b11296f1b8f ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: d3e12b29aef25bc9d1830b0a05643b11296f1b8f

Wrap include/opcode/aarch64.h in extern "C" for C++

This is sufficient to link an aarch64 GDB built in C++ mode.  Pedro
did something similar in Feb
https://sourceware.org/ml/binutils/2015-02/msg00176.html

include/opcode/

2015-10-07  Yao Qi  <yao.qi@linaro.org>

	* aarch64.h [__cplusplus]: Wrap in extern "C".


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] btrace: fix void return
@ 2015-10-08  7:41 sergiodj+buildbot
  2015-10-08  8:15 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-08  7:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 04c4fe8c59d3f2870a5df7be7f55fca60d88381f ***

Author: Markus Metzger <markus.t.metzger@intel.com>
Branch: master
Commit: 04c4fe8c59d3f2870a5df7be7f55fca60d88381f

btrace: fix void return

record_btrace_resume returns the void return from the to_resume method of the
target beneath.  Split this into calling to_resume and return.

gdb/
	* record-btrace.c (record_btrace_resume): Fix void return.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix compile time warning compiling ARC port.
@ 2015-10-08 11:43 sergiodj+buildbot
  2015-10-08 12:12 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-08 11:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3f94e60d92d9bf67f1f8cbc19ffbfe5d28db7fcf ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: 3f94e60d92d9bf67f1f8cbc19ffbfe5d28db7fcf

Fix compile time warning compiling ARC port.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] MAINTAINERS: Update my email address
@ 2015-10-08 18:17 sergiodj+buildbot
  2015-10-08 18:50 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-08 18:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4e7de1556a25a3a31c53ea2242b1d9a5c103dd16 ***

Author: Maciej W. Rozycki <macro@imgtec.com>
Branch: master
Commit: 4e7de1556a25a3a31c53ea2242b1d9a5c103dd16

MAINTAINERS: Update my email address

	gdb/
	* MAINTAINERS: Update my email address.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [D] Support D style sizeof and typeof expressions.
@ 2015-10-08 19:56 sergiodj+buildbot
  2015-10-08 20:26 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-08 19:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d5d8c4e12b220068fb0b2047b63562d3f9903e91 ***

Author: Iain Buclaw <ibuclaw@gdcproject.org>
Branch: master
Commit: d5d8c4e12b220068fb0b2047b63562d3f9903e91

[D] Support D style sizeof and typeof expressions.

gdb/ChangeLog:

	* d-exp.y: (UnaryExpression): Support `type.sizeof' expressions.
	(PostfixExpression): Support `expr.sizeof' expressions.
	(PrimaryExpression): Support `typeof(expr)' expressions.

gdb/testsuite/ChangeLog:

	* gdb.dlang/properties.exp: New file.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix gdb.base/a2-run.exp race
@ 2015-10-09 12:07 sergiodj+buildbot
  2015-10-09 12:36 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-09 12:07 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 145e3ddb4b1657a1f29eb9f41f2d54d0bf26b6f0 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 145e3ddb4b1657a1f29eb9f41f2d54d0bf26b6f0

Fix gdb.base/a2-run.exp race

This patch fixes this racy failure, with the native-extended-gdbserver
board:

 (gdb) run
 Starting program: build/gdb/testsuite/outputs/gdb.base/a2-run/a2-run
 Remote debugging from host 127.0.0.1
 Process build/gdb/testsuite/outputs/gdb.base/a2-run/a2-run created; pid = 23832
 Reading /lib64/ld-linux-x86-64.so.2 from remote target...
 warning: File transfers from remote targets can be slow. Use "set sysroot" to access files locally instead.
 Reading /lib64/ld-linux-x86-64.so.2 from remote target...
 Reading /lib64/libm.so.6 from remote target...
 Reading /lib64/libc.so.6 from remote target...
 [Inferior 1 (process 23832) exited with code 01]
 (gdb) FAIL: gdb.base/a2-run.exp: run "a2-run" with no args
 PASS: gdb.base/a2-run.exp: no spurious messages at program exit
 run 5
 Starting program: build/gdb/testsuite/outputs/gdb.base/a2-run/a2-run 5
 Reading /lib64/ld-linux-x86-64.so.2 from remote target...
 usage:  factorial <number>

 Child exited with status 1

Note that the output is correct; it's just that inferior output
appeared after gdb's output, and the test doesn't handle that
correctly.

This comment isn't really correct, unfortunately:

	# waiting.  If we had already seen the status wrapper exit,
	# gdb_test_multiple/expect has no spawn ids left, and thus
	# returns.

That's true of expect in general, but I had missed / forgot that
gdb_test_multiple internally has extra matches using "-i
$gdb_spawn_id", so even if the caller clears all the indirect spawn id
lists, gdb_test_multiple will continue waiting.

So do a conditional exp_continue manually instead.

gdb/testsuite/ChangeLog:
2015-10-09  Pedro Alves  <palves@redhat.com>

	* gdb.base/a2-run.exp (maybe_exp_continue): New procedure.
	(top level): Use it in the run with no args test.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] btrace, test: avoid gdb.btrace/vdso.exp fail
@ 2015-10-09 12:40 sergiodj+buildbot
  2015-10-09 13:37 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-09 12:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT abcef95aa511a845f0599178be09403348ba4bad ***

Author: Markus Metzger <markus.t.metzger@intel.com>
Branch: master
Commit: abcef95aa511a845f0599178be09403348ba4bad

btrace, test: avoid gdb.btrace/vdso.exp fail

The vdso.exp test checks that we can access the VDSO memory when replaying.

Depending on the line information generated by the compiler, runto_main may run
to the line marked with bp.1 or stop before that line.  The test incorrectly
assumes that it will always run to the marked line and fails if it doesn't.

The test does not really care about what is traced.  It does care that GDB is
replaying when capturing the second disassemble output.

Reflect that in the test by ignoring the output of the stepping and record goto
begin commands and by checking that GDB is actually replaying.

testsuite/
	* gdb.btrace/vdso.c (main): Remove breakpoint markers.
	* gdb.btrace/vdso.exp: Change stepping command to "next" and ignore
	its output.  Ignore the output of "record goto begin" and instead
	check that GDB is replaying.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] arm-linux-tdep: Add explicit cast for int to gdb_syscall conversion
@ 2015-10-09 14:28 sergiodj+buildbot
  2015-10-09 17:37 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-09 14:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f9fa37b32501f173a37891fb1a8f9013af38a098 ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: f9fa37b32501f173a37891fb1a8f9013af38a098

arm-linux-tdep: Add explicit cast for int to gdb_syscall conversion

This patch is taken from Pedro's branch.

gdb/ChangeLog:

	* arm-linux-tdep.c (arm_canonicalize_syscall): Add
	enum gdb_syscall casts.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] cris: Use enum bfd_endian to represent endianness
@ 2015-10-09 14:36 sergiodj+buildbot
  2015-10-09 18:39 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-09 14:36 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 78c5b882482b5435bb2dcf1c09a52683d54cb81e ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: 78c5b882482b5435bb2dcf1c09a52683d54cb81e

cris: Use enum bfd_endian to represent endianness

gdb/ChangeLog:

	* cris-tdep.c (struct instruction_environment): Change type of
	byte_order to enum bfd_endian.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] i386: Fix type of gdbarch_tdep::register_reggroup_p
@ 2015-10-09 14:44 sergiodj+buildbot
  2015-10-09 19:42 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-09 14:44 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c5bcd27856f388ae4935b525b1016e812803ddf5 ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: c5bcd27856f388ae4935b525b1016e812803ddf5

i386: Fix type of gdbarch_tdep::register_reggroup_p

gdb/ChangeLog:

	* i386-tdep.h (struct gdbarch_tdep): Change type of
	register_reggroup_p to gdbarch_register_reggroup_p_ftype.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] use gdb_byte in ada-lang.c::ada_value_primitive_packed_val...
@ 2015-10-09 21:52 sergiodj+buildbot
  2015-10-09 23:13 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-09 21:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fbd000da7c05ea751f47a678936de706733ea6e3 ***

Author: Joel Brobecker <brobecker@adacore.com>
Branch: master
Commit: fbd000da7c05ea751f47a678936de706733ea6e3

use gdb_byte in ada-lang.c::ada_value_primitive_packed_val...

... instead of "unsigned char".

gdb/Changelog:

        * ada-lang.c (ada_value_primitive_packed_val): Change the type
        of local variables src and unpacked to "gdb_type *" instead of
        "unsigned char *".


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [Ada] split data unpacking code out of ada_value_primitive_packed_val.
@ 2015-10-09 22:07 sergiodj+buildbot
  2015-10-10  2:59 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-09 22:07 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f93fca700f0fd70532132ae535f48c1a936abb0a ***

Author: Joel Brobecker <brobecker@adacore.com>
Branch: master
Commit: f93fca700f0fd70532132ae535f48c1a936abb0a

[Ada] split data unpacking code out of ada_value_primitive_packed_val.

This patch is just preparation work which splits the function
ada_value_primitive_packed_val into two function: one which unpacks
the data, and the other which now uses it to implement
ada_value_primitive_packed_val.

This simplifies a bit ada_value_primitive_packed_val, but will also
allow us to use the new function to unpack data without actually creating
a struct value as a result.

gdb/ChangeLog:

        * ada-lang.c (ada_unpack_from_contents): New function,
        extracted from ada_value_primitive_packed_val.
        (ada_value_primitive_packed_val): Replace extracted out code
        by call to ada_unpack_from_contents.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] make is_scalar_type non-static and use it in ada-lang.c
@ 2015-10-09 22:23 sergiodj+buildbot
  2015-10-10  6:00 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-09 22:23 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 220475ed8b0c1ef7b4eabf64bcc723e14fd78209 ***

Author: Joel Brobecker <brobecker@adacore.com>
Branch: master
Commit: 220475ed8b0c1ef7b4eabf64bcc723e14fd78209

make is_scalar_type non-static and use it in ada-lang.c

Just a small cleanup, to avoid code duplication...

gdb/ChangeLog:

        * gdbtypes.h (is_scalar_type): Add extern declaration.
        * gdbtypes.c (is_scalar_type): Make non-static.
        * ada-lang.c (ada_value_primitive_packed_val): Use is_scalar_type
        to compute IS_SCALAR instead of doing it ourselves.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [Ada] Buffer overflow in ada_unpack_from_contents
@ 2015-10-09 22:31 sergiodj+buildbot
  2015-10-10  7:02 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-09 22:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0cafa88cc03786fb5794ca53e987e45fd09621f8 ***

Author: Joel Brobecker <brobecker@adacore.com>
Branch: master
Commit: 0cafa88cc03786fb5794ca53e987e45fd09621f8

[Ada] Buffer overflow in ada_unpack_from_contents

This patch fixes a buffer overflow in ada_unpack_from_contents
caused by one of the previous commits. This happens when trying
to print the value of an array of variant records.

The overflow happens while trying to print one element of the array.
Because the size of each element in the array is variable, the array
has a DWARF byte_stride attribute, which makes us treat the array
as if it was packed. And during the extraction of each array element,
we try to unpack an object using the array's byte stride as the size,
into an element whose size is actually less than the stride.

This patch fixes the issue by overriding the byte-stride with
the actual element's length.

gdb/ChangeLog:

        * ada-lang.c (ada_value_primitive_packed_val): Move
        src_len variable to local block where used.  Override
        BIT_SIZE if bigger than size of resolved type.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [Ada] ada_unpack_from_contents: Error if target buffer not large enough
@ 2015-10-09 22:39 sergiodj+buildbot
  2015-10-10  8:03 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-09 22:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5b639deae123db13af61e915807c0a1ab224e246 ***

Author: Joel Brobecker <brobecker@adacore.com>
Branch: master
Commit: 5b639deae123db13af61e915807c0a1ab224e246

[Ada] ada_unpack_from_contents: Error if target buffer not large enough

This adds a guard that the size of the "unpacked" buffer is large enough
to contain at least BIT_SIZE bits.  If not, report an error.  This is to
guard this routine from doing buffer overflows when called incorrectly.

gdb/ChangeLog:

        * ada-lang.c (ada_unpack_from_contents): Add guard that unpacked
        is large enough for BIT_SIZE.  Update function comment.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] sim: bfin: handle negative left saturated shifts as ashifts [BZ #18407]
@ 2015-10-11  7:54 sergiodj+buildbot
  2015-10-11  8:22 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-11  7:54 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3f946aa82518e878aea2cba4b6a9bcc651412c5c ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 3f946aa82518e878aea2cba4b6a9bcc651412c5c

sim: bfin: handle negative left saturated shifts as ashifts [BZ #18407]

When handling left saturated ashifts with negative immediates, they
should be treated as right ashifts.  This matches hardware behavior.

Reported-by: Igor Rayak <igorr@gitatechnologies.com>


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] sim: moxie: fix leakage in error path [BZ #18273]
@ 2015-10-11  8:08 sergiodj+buildbot
  2015-10-11  9:22 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-11  8:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7d8a636c9a234354c9b2ecf01b6e405bece190a1 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 7d8a636c9a234354c9b2ecf01b6e405bece190a1

sim: moxie: fix leakage in error path [BZ #18273]

Reported-by: dcb <dcb314@hotmail.com>


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Ignore references with relocs to discarded sections in .data.rel.ro.local on hppa-linux.
@ 2015-10-11 23:20 sergiodj+buildbot
  2015-10-11 23:48 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-11 23:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT da6e19a92645583da12dc2d15f54d2bd240fd3f2 ***

Author: John David Anglin <danglin@gcc.gnu.org>
Branch: master
Commit: da6e19a92645583da12dc2d15f54d2bd240fd3f2

Ignore references with relocs to discarded sections in .data.rel.ro.local on hppa-linux.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] PR19083 S/390: Fix garbage collection of some GOT relocs.
@ 2015-10-12  8:32 sergiodj+buildbot
  2015-10-12  9:00 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-12  8:32 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ef05be83b7e1e10e7cba51aeafc879ca3a66826d ***

Author: Andreas Krebbel <krebbel@linux.vnet.ibm.com>
Branch: master
Commit: ef05be83b7e1e10e7cba51aeafc879ca3a66826d

PR19083 S/390: Fix garbage collection of some GOT relocs.

bfd/ChangeLog:

2015-10-12  Andreas Krebbel  <krebbel@linux.vnet.ibm.com>

	PR ld/19083
	* elf32-s390.c (elf_s390_gc_sweep_hook): Do not reduce got
	refcount for relocs not really requiring a got slot.
	* elf64-s390.c (elf_s390_gc_sweep_hook): Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Forward VALUE_LVAL when avoiding side effects for STRUCTOP_STRUCT
@ 2015-10-12 10:32 sergiodj+buildbot
  2015-10-12 11:00 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-12 10:32 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2520f728b710c0249cde01b8cfb4872a22ef10b6 ***

Author: Pierre-Marie de Rodat <derodat@adacore.com>
Branch: master
Commit: 2520f728b710c0249cde01b8cfb4872a22ef10b6

Forward VALUE_LVAL when avoiding side effects for STRUCTOP_STRUCT

Assume foo_array is a pointer to a C structure. GDB must evaluate the
following expression properly, but it does not currently:

    (gdb) print 1 && &foo_array[1].a
    Attempt to take address of value not located in memory.

The problem is that in EVAL_AVOID_SIDE_EFFECTS mode,
eval.c:evaluate_subexp_standard always returns a not_lval value as the
result for a STRUCTOP_STRUCT operation. As a consequence, the rest of
the code believes that one cannot take the address of the returned
value.

This patch fixes STRUCTOP_STRUCT handling so that the VALUE_LVAL
attribute for the returned value is properly initialized.  After this
change, the above session becomes:

    (gdb) print 1 && &foo_array[1].a
    $1 = 1

gdb/ChangeLog:

	* eval.c (evaluate_subexp_standard) <STRUCTOP_STRUCT>: If
	EVAL_AVOID_SIDE_EFFECTS mode, forward the VALUE_LVAL attribute
	to the returned value.

gdb/testsuite/ChangeLog:

	* gdb.base/nested-addr.c: New file.
	* gdb.base/nested-addr.exp: New testcase.

Tested on x86_64-linux, no regression.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] More tests in gdb.arch/insn-reloc.c
@ 2015-10-12 10:41 sergiodj+buildbot
  2015-10-12 11:59 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-12 10:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8240f4421f7ab761ff5476d16090789d2332b676 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 8240f4421f7ab761ff5476d16090789d2332b676

More tests in gdb.arch/insn-reloc.c

This patch adds more tests in gdb.arch/insn-reloc.c to cover
instruction BL and cover B.CON when CON is false.  These new added
tests can be used for displaced stepping too.

gdb/testsuite:

2015-10-12  Yao Qi  <yao.qi@linaro.org>

	* gdb.arch/insn-reloc.c (can_relocate_bcond): Rename to ...
	(can_relocate_bcond_true): ... it.
	(can_relocate_bcond_false): New function.
	(foo): Likewise.
	(can_relocate_bl): Likewise.
	(testcases) [__aarch64__]: Add can_relocate_bcond_false and
	can_relocate_bl.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Move append_insns out of aarch64_relocate_instruction
@ 2015-10-12 10:57 sergiodj+buildbot
  2015-10-12 13:59 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-12 10:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT dfaffe9d93dec5c23cc71b74789221ce97a132ef ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: dfaffe9d93dec5c23cc71b74789221ce97a132ef

Move append_insns out of aarch64_relocate_instruction

aarch64_relocate_instruction should only decode instructions, and other
operations should be done out side of it.  This patch moves append_insns
out of aarch64_relocate_instruction, to its caller.

gdb/gdbserver:

2015-10-12  Yao Qi  <yao.qi@linaro.org>

	* linux-aarch64-low.c (aarch64_relocate_instruction): Return
	int.  Add argument buf.
	(aarch64_install_fast_tracepoint_jump_pad): Pass buf to
	aarch64_relocate_instruction.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Move aarch64_relocate_instruction to arch/aarch64-insn.c
@ 2015-10-12 11:13 sergiodj+buildbot
  2015-10-12 15:57 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-12 11:13 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 246994ce350923199a4c952b38dcee5bcbe8c554 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 246994ce350923199a4c952b38dcee5bcbe8c554

Move aarch64_relocate_instruction to arch/aarch64-insn.c

This patch moves aarch64_relocate_instruction and visitor class to
arch/aarch64-insn.c, so that both GDB and GDBserver can use it.

gdb:

2015-10-12  Yao Qi  <yao.qi@linaro.org>

	* arch/aarch64-insn.c (aarch64_decode_ldr_literal): Moved from
	gdbserver/linux-aarch64-low.c.
	(aarch64_relocate_instruction): Likewise.
	* arch/aarch64-insn.h (aarch64_decode_ldr_literal): Declare.
	(struct aarch64_insn_data): Moved from
	gdbserver/linux-aarch64-low.c.
	(struct aarch64_insn_visitor): Likewise.
	(aarch64_relocate_instruction): Declare.

gdb/gdbserver:

2015-10-12  Yao Qi  <yao.qi@linaro.org>

	* linux-aarch64-low.c (extract_signed_bitfield): Remove.
	(aarch64_decode_ldr_literal): Move to gdb/arch/aarch64-insn.c.
	(aarch64_relocate_instruction): Likewise.
	(struct aarch64_insn_data): Move to gdb/arch/aarch64-insn.h.
	(struct aarch64_insn_visitor): Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Support displaced stepping in support_displaced_stepping for aarch64*-*-linux*
@ 2015-10-12 11:28 sergiodj+buildbot
  2015-10-12 17:56 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-12 11:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 34240514b58b7e8d2b444b69345d13db2695fef6 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 34240514b58b7e8d2b444b69345d13db2695fef6

Support displaced stepping in support_displaced_stepping for aarch64*-*-linux*

gdb/testsuite:

2015-10-12  Yao Qi  <yao.qi@linaro.org>

	* lib/gdb.exp (support_displaced_stepping): Return 1 if target
	is aarch64*-*-linux*.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] New test case gdb.arch/disp-step-insn-reloc.exp
@ 2015-10-12 11:36 sergiodj+buildbot
  2015-10-12 18:56 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-12 11:36 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0fd8ac1c450d340d0b11823107d9e990341e7e11 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 0fd8ac1c450d340d0b11823107d9e990341e7e11

New test case gdb.arch/disp-step-insn-reloc.exp

This patch adds a new test case which uses gdb.arch/insn-reloc.c too
to test displaced stepping.  Nowadays, tests are for x86, x86_64 and
aarch64.

gdb/testsuite:

2015-10-12  Yao Qi  <yao.qi@linaro.org>

	* gdb.arch/disp-step-insn-reloc.exp: New test case.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Move target_read_uint32 out of aarch64_relocate_instruction
@ 2015-10-12 11:38 sergiodj+buildbot
  2015-10-12 12:59 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-12 11:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 70b439f0a87b6c42901e49a71b1dbd09300e8260 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 70b439f0a87b6c42901e49a71b1dbd09300e8260

Move target_read_uint32 out of aarch64_relocate_instruction

This patch is to move target_read_uint32 out of
aarch64_relocate_instruction and pass INSN to
aarch64_relocate_instruction, so that it is cleaner, only decode
instructions.

gdb/gdbserver:

2015-10-12  Yao Qi  <yao.qi@linaro.org>

	* linux-aarch64-low.c (aarch64_relocate_instruction): Add
	argument insn.  Remove local variable insn.  Don't call
	target_read_uint32.
	(aarch64_install_fast_tracepoint_jump_pad): Call
	target_read_uint32.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Rename emit_load_store to  aarch64_emit_load_store
@ 2015-10-12 11:53 sergiodj+buildbot
  2015-10-12 20:55 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-12 11:53 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1c2e1515c45af104fc9b2aea6bd6b1471238dd98 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 1c2e1515c45af104fc9b2aea6bd6b1471238dd98

Rename emit_load_store to  aarch64_emit_load_store

Likewise, this patch renames emit_load_store to
aarch64_emit_load_store.

gdb:

2015-10-12  Yao Qi  <yao.qi@linaro.org>

	* arch/aarch64-insn.c (emit_load_store): Rename to ...
	(aarch64_emit_load_store): ... it.  All callers updated.

gdb/gdbserver:

2015-10-12  Yao Qi  <yao.qi@linaro.org>

	* linux-aarch64-low.c: Update all callers as emit_load_store
	is renamed to aarch64_emit_load_store.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Support displaced stepping in aarch64-linux
@ 2015-10-12 13:05 sergiodj+buildbot
  2015-10-12 16:57 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-12 13:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b6542f81d0894d69e7f12a73b94bf4adead75a5c ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: b6542f81d0894d69e7f12a73b94bf4adead75a5c

Support displaced stepping in aarch64-linux

This patch is to support displaced stepping in aarch64-linux.  A
visitor is implemented for displaced stepping, and used to record
information to fixup pc after displaced stepping if needed.  Some
emit_* functions are converted to macros, and moved to
arch/aarch64-insn.{c,h} so that they can be shared.

gdb:

2015-10-12  Yao Qi  <yao.qi@linaro.org>

	* aarch64-linux-tdep.c: Include arch-utils.h.
	(aarch64_linux_init_abi): Call set_gdbarch_max_insn_length,
	set_gdbarch_displaced_step_copy_insn,
	set_gdbarch_displaced_step_fixup,
	set_gdbarch_displaced_step_free_closure,
	set_gdbarch_displaced_step_location,
	and set_gdbarch_displaced_step_hw_singlestep.
	* aarch64-tdep.c (struct displaced_step_closure): New.
	(struct aarch64_displaced_step_data): New.
	(aarch64_displaced_step_b): New function.
	(aarch64_displaced_step_b_cond): Likewise.
	(aarch64_register): Likewise.
	(aarch64_displaced_step_cb): Likewise.
	(aarch64_displaced_step_tb): Likewise.
	(aarch64_displaced_step_adr): Likewise.
	(aarch64_displaced_step_ldr_literal): Likewise.
	(aarch64_displaced_step_others): Likewise.
	(aarch64_displaced_step_copy_insn): Likewise.
	(aarch64_displaced_step_fixup): Likewise.
	(aarch64_displaced_step_hw_singlestep): Likewise.
	* aarch64-tdep.h (DISPLACED_MODIFIED_INSNS): New macro.
	(aarch64_displaced_step_copy_insn): Declare.
	(aarch64_displaced_step_fixup): Declare.
	(aarch64_displaced_step_hw_singlestep): Declare.
	* arch/aarch64-insn.c (emit_insn): Moved from
	gdbserver/linux-aarch64-low.c.
	(emit_load_store): Likewise.
	* arch/aarch64-insn.h (enum aarch64_opcodes): Moved from
	gdbserver/linux-aarch64-low.c.
	(struct aarch64_register): Likewise.
	(struct aarch64_memory_operand): Likewise.
	(ENCODE): Likewise.
	(can_encode_int32): New macro.
	(emit_b, emit_bcond, emit_cb, emit_ldr, emit_ldrsw): Likewise.
	(emit_tb, emit_nop): Likewise.
	(emit_insn): Declare.
	(emit_load_store): Declare.

gdb/gdbserver:

2015-10-12  Yao Qi  <yao.qi@linaro.org>

	* linux-aarch64-low.c (enum aarch64_opcodes): Move to
	arch/aarch64-insn.h.
	(struct aarch64_memory_operand): Likewise.
	(ENCODE): Likewise.
	(emit_insn): Move to arch/aarch64-insn.c.
	(emit_b, emit_bcond, emit_cb, emit_tb): Remove.
	(emit_load_store): Move to arch/aarch64-insn.c.
	(emit_ldr, emit_ldrb, emit_ldrsw, emit_nop): Remove.
	(can_encode_int32): Remove.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Skip the unversioned definition after the default version
@ 2015-10-12 15:35 sergiodj+buildbot
  2015-10-12 22:55 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-12 15:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4373f8af3ddbc301227e883d5cbed8302c107e59 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 4373f8af3ddbc301227e883d5cbed8302c107e59

Skip the unversioned definition after the default version

We may see an unversioned definition after the default version.  We
should skip the unversioned definition in this case.

bfd/

	PR ld/19073
	* elflink.c (_bfd_elf_add_default_symbol): Skip the unversioned
	definition after the default version.

ld/testsuite/

	PR ld/19073
	* ld-elf/pr19073.map: New file.
	* ld-elf/pr19073.rd: Likewise.
	* ld-elf/pr19073.s: Likewise.
	* ld-elf/shared.exp (build_tests): Add tests for PR ld/19073.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] aarch64: Use gdb_sys_no_syscall enum instead of -1
@ 2015-10-12 16:35 sergiodj+buildbot
  2015-10-12 23:55 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-12 16:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cb65d272fd09b79b7911cc00b5262d4fe14a40d7 ***

Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: cb65d272fd09b79b7911cc00b5262d4fe14a40d7

aarch64: Use gdb_sys_no_syscall enum instead of -1

Fixes:

/home/simark/src/binutils-gdb/gdb/aarch64-linux-tdep.c: In function "gdb_syscall aarch64_canonicalize_syscall(aarch64_syscall)":
/home/simark/src/binutils-gdb/gdb/aarch64-linux-tdep.c:874:13: error: invalid conversion from "int" to "gdb_syscall" [-fpermissive]
     return -1;
             ^

gdb/ChangeLog:

	* aarch64-linux-tdep.c (aarch64_canonicalize_syscall): Return
	gdb_sys_no_syscall instead of -1.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] m32c: Split m32c_move_reg_t in read/write variants
@ 2015-10-12 17:23 sergiodj+buildbot
  2015-10-13  3:43 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-12 17:23 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6da660c76dd7c2998d847d2c978a293f13105eea ***

Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: 6da660c76dd7c2998d847d2c978a293f13105eea

m32c: Split m32c_move_reg_t in read/write variants

This allows to avoid casting away the const qualification in
m32c_pseudo_register_write (which is the entry points for all other
register read/write functions).

Also, use gdb_byte* instead of void* to avoid casts when calling gdb
common memory functions.  It also allows to remove those "For adderss
arithmetic" local variables.

gdb/ChangeLog:

	* m32c-tdep.c (m32c_move_reg_t): Replace with...
	(m32c_write_reg_t): ...this and...
	(m32c_read_reg_t): ...this.
	(struct m32c_reg): Update types of read and write.
	(m32c_raw_read): Change declaration type to m32c_read_reg_t and
	adjust definition.
	(m32c_banked_read): Likewise.
	(m32c_sb_read): Likewise.
	(m32c_part_read): Likewise.
	(m32c_cat_read): Likewise.
	(m32c_r3r2r1r0_read): Likewise.
	(m32c_raw_write): Change declaration type to m32c_write_reg_t
	and adjust definition.
	(m32c_banked_write): Likewise.
	(m32c_sb_write): Likewise.
	(m32c_part_write): Likewise.
	(m32c_cat_write): Likewise.
	(m32c_r3r2r1r0_write): Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] gdb: Make use of safe-ctype.h header.
@ 2015-10-12 21:41 sergiodj+buildbot
  2015-10-13  5:49 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-12 21:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8d3fea161a8e1d280d207406ba3fee0d44776ce6 ***

Author: Andrew Burgess <andrew.burgess@embecosm.com>
Branch: master
Commit: 8d3fea161a8e1d280d207406ba3fee0d44776ce6

gdb: Make use of safe-ctype.h header.

In stack.c switch to using safe-ctype.h instead of ctype.h, update code
as required.

gdb/ChangeLog:

	* stack.c: Include safe-ctype.h not ctype.h.
	(parse_frame_specification): Use ISSPACE not isspace.
	(backtrace_command): Use TOLOWER not tolower.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] gdb: Fix bug with dbx style func command.
@ 2015-10-12 21:49 sergiodj+buildbot
  2015-10-13  6:49 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-12 21:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9d622bda566a4980b045631f500c29717ede8186 ***

Author: Andrew Burgess <andrew.burgess@embecosm.com>
Branch: master
Commit: 9d622bda566a4980b045631f500c29717ede8186

gdb: Fix bug with dbx style func command.

The func command, available when starting gdb in dbx mode, is supposed
to take a function name and locate the frame for that function in the
stack.  This has been broken for a while due to an invalid check of the
arguments within the worker function.  Fixed in this commit.

gdb/ChangeLog:

	* stack.c (func_command): Return early when there is no ARG
	string.

gdb/testsuite/ChangeLog:

	* gdb.base/dbx.exp (test_func): Remove xfails, update expected
	results.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] gdb: Avoid unneeded calls to parse_frame_specification.
@ 2015-10-12 21:57 sergiodj+buildbot
  2015-10-13  7:49 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-12 21:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT edbbff4a22154a4b155ac987436c6498947cf8b4 ***

Author: Andrew Burgess <andrew.burgess@embecosm.com>
Branch: master
Commit: edbbff4a22154a4b155ac987436c6498947cf8b4

gdb: Avoid unneeded calls to parse_frame_specification.

Within the stack command there are a couple of places where fixed
strings are passed into functions that are really intended for
processing user input.  These fixed strings are then processed and the
result returned.

Given that the input strings in these cases are fixed, and are always
"0", then the result will always be the same, the current frame.  By
switching to using get_current_frame instead the code can be simplified,
and the intention of the code is clearer.

gdb/ChangeLog:

	* stack.c (parse_frame_specification): Delete.
	(parse_frame_specification_1): Rename to
	parse_frame_specification.
	(frame_info): Use parse_frame_specification.
	(select_frame_command): Likewise.
	(return_command): Use select_frame and print_stack_frame rather
	than frame_command and select_frame_command.
	(func_command): Use get_current_frame rather than
	parse_frame_specification.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] gdb: Simplify parse_frame_specification.
@ 2015-10-12 22:05 sergiodj+buildbot
  2015-10-13  8:48 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-12 22:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a0d34a3956f504e755638cadb2bac2b03e4e37e7 ***

Author: Andrew Burgess <andrew.burgess@embecosm.com>
Branch: master
Commit: a0d34a3956f504e755638cadb2bac2b03e4e37e7

gdb: Simplify parse_frame_specification.

Remove an unneeded parameter from parse_frame_specification, replace
with a fixed string within parse_frame_specification.  The message was
the same in every place that parse_frame_specification was used anyway.

gdb/ChangeLog:

	* stack.c (parse_frame_specification): Remove message parameter,
	replace with fixed string in function body, update function
	comment.
	(frame_info): Remove message to parse_frame_specification.
	(select_frame_command): Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] sim: ft32: test coverage for link parameters and PM write port
@ 2015-10-13  0:32 sergiodj+buildbot
  2015-10-13  9:48 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-13  0:32 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8173c2a3c46efd8b12983b6095ff7bed4cda1c90 ***

Author: James Bowman <james.bowman@ftdichip.com>
Branch: master
Commit: 8173c2a3c46efd8b12983b6095ff7bed4cda1c90

sim: ft32: test coverage for link parameters and PM write port

Adds test coverage for recent features.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Tidy code setting PT_GNU_RELRO p_flags
@ 2015-10-13  6:14 sergiodj+buildbot
  2015-10-13 10:49 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-13  6:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 341b8ee719163f7ae8528f2a7832381887fbf8d8 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 341b8ee719163f7ae8528f2a7832381887fbf8d8

Tidy code setting PT_GNU_RELRO p_flags

No functional changes here.

	* elf.c (_bfd_elf_map_sections_to_segments): Don't set
	PT_GNU_RELRO p_flags.
	(assign_file_positions_for_non_load_sections): Set PT_GNU_RELRO
	flags to PF_R here.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
[parent not found: <4666fec3b414c7880e9629f3c9b0a5b584235c6d@gdb-build>]
* [binutils-gdb] ada-lang.c: malloc/alloca casts for C++
@ 2015-10-13 18:50 sergiodj+buildbot
  2015-10-13 19:28 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-13 18:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT aa5c10ce9b1bd04a7f4a619d5e956c977fcd60d3 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: aa5c10ce9b1bd04a7f4a619d5e956c977fcd60d3

ada-lang.c: malloc/alloca casts for C++

gdb/ChangeLog:
2015-10-13  Pedro Alves  <palves@redhat.com>

	* ada-lang.c (ada_value_primitive_packed_val): Add casts to malloc
	and alloca calls.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] ada-lang.c:ada_value_primitive_packed_val: const correctness
@ 2015-10-13 18:58 sergiodj+buildbot
  2015-10-13 20:31 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-13 18:58 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bfb1c7963b15b31073c9adf2d97ff1cf953ec99c ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: bfb1c7963b15b31073c9adf2d97ff1cf953ec99c

ada-lang.c:ada_value_primitive_packed_val: const correctness

gdb/ChangeLog:
2015-10-13  Pedro Alves  <palves@redhat.com>

	* ada-lang.c (ada_value_primitive_packed_val): Constify
	locals.  Use value_contents_writeable.  Remove casts.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
[parent not found: <170742de5dd5be2156f938e00e2451526ef57d5c@gdb-build>]
[parent not found: <e6a959d68b8181c816851dcfc91ae0b2b9296df3@gdb-build>]
* [binutils-gdb] Recognize a few more AIX XCOFF DWARF sections.
@ 2015-10-13 22:55 sergiodj+buildbot
  2015-10-13 23:37 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-13 22:55 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 33f914a197fa8cd4338396e7d62a5f26621f183c ***

Author: David Edelsohn <dje.gcc@gmail.com>
Branch: master
Commit: 33f914a197fa8cd4338396e7d62a5f26621f183c

Recognize a few more AIX XCOFF DWARF sections.

gdb/ChangeLog:

        * xcoffread.c (dwarf2_xcoff_names): Add .dwmac and .dwpbtyp.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Define enum out of struct
@ 2015-10-14  8:47 sergiodj+buildbot
  2015-10-14  8:59 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-14  8:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6448a3e4daecbdba25e5c76b0fbb0c21583a1347 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 6448a3e4daecbdba25e5c76b0fbb0c21583a1347

Define enum out of struct

This patch moves the definition of enum out of the scope of struct
aarch64_memory_operand, otherwise it breaks GDB build in c++ mode.

gdb:

2015-10-14  Yao Qi  <yao.qi@linaro.org>

	* arch/aarch64-insn.h (struct aarch64_memory_operand): Move enum
	out of it.
	(enum aarch64_memory_operand_type): New.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] S/390: Fix instruction type of troo, trot, trto, and trtt.
@ 2015-10-14  9:08 sergiodj+buildbot
  2015-10-14 10:17 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-14  9:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c46eb7b88a1261bc079bfbe2339060152bdf3527 ***

Author: Andreas Krebbel <krebbel@linux.vnet.ibm.com>
Branch: master
Commit: c46eb7b88a1261bc079bfbe2339060152bdf3527

S/390: Fix instruction type of troo, trot, trto, and trtt.

opcodes/ChangeLog:

2015-10-14  Andreas Krebbel  <krebbel@linux.vnet.ibm.com>

	* s390-opc.c: Fix comment.
	* s390-opc.txt: Change instruction type for troo, trot, trto, and
	trtt to RRF_U0RER since the second parameter does not need to be a
	register pair.

gas/testsuite/ChangeLog:

2015-10-14  Andreas Krebbel  <krebbel@linux.vnet.ibm.com>

	* gas/s390/esa-g5.d: Use odd GPR for the second operand.
	* gas/s390/esa-g5.s: Likewise.
	* gas/s390/esa-z9-109.d: Likewise.
	* gas/s390/esa-z9-109.s: Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] bfd: [SH] Emit DT_PLTGOT for FDPIC output unconditionally
@ 2015-10-14 22:32 sergiodj+buildbot
  2015-10-14 23:00 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-14 22:32 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b4b0e149fa667b3907382e3492b53759665fe979 ***

Author: Rich Felker <dalias@libc.org>
Branch: master
Commit: b4b0e149fa667b3907382e3492b53759665fe979

bfd: [SH] Emit DT_PLTGOT for FDPIC output unconditionally

PR ld/19091
* elf32-sh.c (sh_elf_size_dynamic_sections): Always emit DT_PLTGOT for FDPIC output.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] objcopy --extract-symbol
@ 2015-10-15 13:20 sergiodj+buildbot
  2015-10-15 14:36 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-15 13:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e43fb83166ca5610e34cfba1dcf1216d0953aa8c ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: e43fb83166ca5610e34cfba1dcf1216d0953aa8c

objcopy --extract-symbol

Calling bfd_copy_private_bfd_data is necessary to copy ELF file header
info.

binutils/
	* objcopy.c (copy_object): Don't omit bfd_copy_private_bfd_data
	call when extract_symbol.
bfd/
	* elf32-v850.c (v850_elf_copy_private_bfd_data): Remove assertion
	that input and output .note.renesas sections are same size.
	Instead, only copy input to output if they are.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] aarch64 multi-arch part 6: HW breakpoint on unaligned address
@ 2015-10-15 14:19 sergiodj+buildbot
  2015-10-15 15:36 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-15 14:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8d689ee570e7c4c61231b919d5b6a34c20414c43 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 8d689ee570e7c4c61231b919d5b6a34c20414c43

aarch64 multi-arch part 6: HW breakpoint on unaligned address

Nowadays, both aarch64 GDB and linux kernel assumes that address for
setting breakpoint should be 4-byte aligned.  However that is not true
after we support multi-arch, because thumb instruction can be at 2-byte
aligned address.  Patch http://lists.infradead.org/pipermail/linux-arm-kernel/2015-October/375141.html
to linux kernel is to teach kernel to handle 2-byte aligned address for
HW breakpoint, while this patch is to teach aarch64 GDB handle 2-byte
aligned address.

First of all, we call gdbarch_breakpoint_from_pc to get the instruction
length rather than using hard-coded 4.  Secondly, in GDBserver, we set
length back to 2 if it is 3, because GDB encode 3 in it to indicate it
is a 32-bit thumb breakpoint.  Then we relax the address alignment
check from 4-byte aligned to 2-byte aligned.

This patch enables some tests (such as gdb.base/break-idempotent.exp,
gdb.base/cond-eval-mode.exp, gdb.base/watchpoint-reuse-slot.exp,) and
fixes many fails (such as gdb.base/hbreak2.exp) when the program is
compiled in thumb mode on aarch64.

Regression tested on aarch64-linux, both native and gdbserver.  This
is the last patch of multi-arch work.

gdb:

2015-10-15  Yao Qi  <yao.qi@linaro.org>

	* aarch64-linux-nat.c (aarch64_linux_insert_hw_breakpoint):
	Call gdbarch_breakpoint_from_pc to instruction length.
	(aarch64_linux_remove_hw_breakpoint): Likewise.
	* common/common-regcache.h (regcache_register_size): Declare.
	* nat/aarch64-linux-hw-point.c: Include "common-regcache.h".
	(aarch64_point_is_aligned): Set alignment to 2 for breakpoint if
	the process is 32bit, otherwise set alignment to 4.
	(aarch64_handle_breakpoint): Update comments.
	* regcache.c (regcache_register_size): New function.

gdb/gdbserver:

2015-10-15  Yao Qi  <yao.qi@linaro.org>

	* linux-aarch64-low.c (aarch64_insert_point): Set len to 2
	if it is 3.
	(aarch64_remove_point): Likewise.
	* regcache.c (regcache_register_size): New function.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix typos in comments in _bfd_elf_merge_symbol
@ 2015-10-15 18:10 sergiodj+buildbot
  2015-10-15 18:39 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-15 18:10 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ae7683d2389973fbd368ee1ac77413a3cd1e4a7a ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: ae7683d2389973fbd368ee1ac77413a3cd1e4a7a

Fix typos in comments in _bfd_elf_merge_symbol

	* elflink.c (_bfd_elf_merge_symbol): Fix typos in comments


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Convert mov to lea for loading address of local common symbol
@ 2015-10-16 12:22 sergiodj+buildbot
  2015-10-16 12:49 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-16 12:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b31bcacc489d6ede2e9bdfa9905de0ebfd919454 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: b31bcacc489d6ede2e9bdfa9905de0ebfd919454

Convert mov to lea for loading address of local common symbol

There is no need to check def_regular when converting mov to lea for
loading address of local symbols since def_regular may be false for
common symbols and SYMBOL_REFERENCES_LOCAL is sufficient.

bfd/

	* elf32-i386.c (elf_i386_convert_mov_to_lea): Don't check
	def_regular.
	* elf64-x86-64.c (elf_x86_64_convert_mov_to_lea): Likewise.

ld/testsuite/

	* ld-i386/lea1.s: Add a test for loading address of local common
	symbol.
	* ld-x86-64/lea1.s: Likewise.
	* ld-i386/lea1a.d: Updated.
	* ld-i386/lea1b.d: Likewise.
	* ld-i386/lea1c.d: Likewise.
	* ld-x86-64/lea1a.d: Likewise.
	* ld-x86-64/lea1b.d: Likewise.
	* ld-x86-64/lea1c.d: Likewise.
	* ld-x86-64/lea1d.d: Likewise.
	* ld-x86-64/lea1e.d: Likewise.
	* ld-x86-64/lea1f.d: Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Check if symbol is defined when converting mov to lea
@ 2015-10-16 12:29 sergiodj+buildbot
  2015-10-16 13:50 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-16 12:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 75a06c790f96f07e859be95d3c3c084a718afeef ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 75a06c790f96f07e859be95d3c3c084a718afeef

Check if symbol is defined when converting mov to lea

We need to check if symbol is defined when converting mov to lea since
SYMBOL_REFERENCES_LOCAL may return true on hidden undefined symbols.

	* elf32-i386.c (elf_i386_convert_mov_to_lea): Check if symbol
	is defined.
	* elf64-x86-64.c (elf_x86_64_convert_mov_to_lea): Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] MAINTAINERS: Fix my inconsistent email address
@ 2015-10-16 12:37 sergiodj+buildbot
  2015-10-16 14:49 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-16 12:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e66acfb155e75c1909a6f29702ed6ba3762e36b4 ***

Author: Yao Qi <yao.qi@arm.com>
Branch: master
Commit: e66acfb155e75c1909a6f29702ed6ba3762e36b4

MAINTAINERS: Fix my inconsistent email address

Hi,
This patch fixes inconsistency in my email address.

2015-10-16  Yao Qi  <yao.qi@arm.com>

	* MAINTAINERS: Update my email address.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] gdbserver: Reset current_thread when the thread is removed.
@ 2015-10-16 15:20 sergiodj+buildbot
  2015-10-16 15:49 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-16 15:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 96e7a1eb6d09fda9e22e112e35e7d0085a8f4fd0 ***

Author: Aleksandar Ristovski <aristovski@qnx.com>
Branch: master
Commit: 96e7a1eb6d09fda9e22e112e35e7d0085a8f4fd0

gdbserver: Reset current_thread when the thread is removed.

Reset current_thread and make sure 'remove_process' is used
after all associated threads have been removed first.

gdb/gdbserver/ChangeLog:
	* inferiors.c (thread_pid_matches_callback): New function.
	(find_thread_process): New function.
	(remove_thread): Reset current_thread.
	(remove_process): Assert threads have been removed first.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] targets.c (bfd_flavour_name): "MMO" is spelled "mmo".
@ 2015-10-18 20:26 sergiodj+buildbot
  2015-10-18 21:05 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-18 20:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 434d28e01bd23b7a61128bacbe66ff09e1fed336 ***

Author: Doug Evans <xdje42@gmail.com>
Branch: master
Commit: 434d28e01bd23b7a61128bacbe66ff09e1fed336

targets.c (bfd_flavour_name): "MMO" is spelled "mmo".

bfd/ChangeLog:

	* targets.c (bfd_flavour_name): "MMO" is spelled "mmo".


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Robustify inherit.exp and virtbase.exp.
@ 2015-10-19 10:26 sergiodj+buildbot
  2015-10-19 10:56 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-19 10:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b32b93c614de5ef1319eaa002e481094357018ff ***

Author: Andrew Stubbs <ams@codesourcery.com>
Branch: master
Commit: b32b93c614de5ef1319eaa002e481094357018ff

Robustify inherit.exp and virtbase.exp.

2015-10-19  Andrew Stubbs  <ams@codesourcery.com>

	gdb/testsuite/
	* gdb.cp/inherit.exp (print g_vB, print g_vC, print g_vD,
	print g_vE): Add new pass patterns.
	* gdb.cp/virtbase.exp (print *this, print *(D *) e): Allow GDB to
	print various symbol names for vptr fields.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Make GDB wait for events after handling target File-I/O
@ 2015-10-19 13:46 sergiodj+buildbot
  2015-10-19 14:23 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-19 13:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 29090fb629734b7980f058f4a7e24a0369e9bb49 ***

Author: Luis Machado <lgustavo@codesourcery.com>
Branch: master
Commit: 29090fb629734b7980f058f4a7e24a0369e9bb49

Make GDB wait for events after handling target File-I/O

_ftext () at arm-vector.S:25
25              ldr pc, [pc, #24] @ reset
(gdb) load
Loading section .text, size 0xc01c lma 0x0
Loading section .eh_frame, size 0x48 lma 0xc01c
Loading section .ARM.exidx, size 0x8 lma 0xc064
Loading section .rodata, size 0x398 lma 0xc070
Loading section .data, size 0x8e0 lma 0xc408
Start address 0x40, load size 52452
Transfer rate: 17074 KB/sec, 1748 bytes/write.
(gdb) c
Continuing.
infrun: clear_proceed_status_thread (Thread 1)
infrun: proceed (addr=0xffffffff, signal=GDB_SIGNAL_DEFAULT)
infrun: resume (step=0, signal=GDB_SIGNAL_0), trap_expected=0, current thread [Thread 1] at 0x40
Sending packet: $vCont?#49...Ack
Packet received:
Packet vCont (verbose-resume) is NOT supported
Sending packet: $Hc0#db...Ack
Packet received: OK
Sending packet: $c#63...Ack
infrun: infrun_async(1)
infrun: prepare_to_wait
infrun: target_wait (-1.0.0, status) =
infrun:   -1.0.0 [Thread 0],
infrun:   status->kind = ignore
infrun: TARGET_WAITKIND_IGNORE
infrun: prepare_to_wait
Packet received: Ffstat,00000001,07fffdb0
Sending packet: $M7fffdb0,40:000000000000000000002080000000010000c336000001180000000000000000000000000000000000000200000000000000000055dfb11b55dfb11b55dfb11b#5a...Ack
Packet received: OK
Sending packet: $F0#76...Ack
infrun: target_wait (-1.0.0, status) =
infrun:   -1.0.0 [Thread 0],
infrun:   status->kind = ignore
infrun: TARGET_WAITKIND_IGNORE
infrun: prepare_to_wait
infrun: target_wait (-1.0.0, status) =
infrun:   -1.0.0 [Thread 0],
infrun:   status->kind = no-resumed
infrun: TARGET_WAITKIND_NO_RESUMED
infrun: stop_waiting
infrun: clear_step_over_info
Sending packet: $qfThreadInfo#bb...Ack
Packet received: m1
Sending packet: $qsThreadInfo#c8...Ack
Packet received: l
No unwaited-for children left.
infrun: infrun_async(0)
(gdb) c
Continuing.
Cannot execute this command while the selected thread is running.
(gdb)
Continuing.
Cannot execute this command while the selected thread is running.

This behavior shows up whenever GDB is in all-stop mode and is handling
target-initiated File-I/O requests, in the middle of, say, a continue
request.

When GDB is done handling the File-I/O request, it doesn't set
rs->waiting_for_stop_reply back to 1, meaning GDB should wait for
further target events.

This seems to be a latent bug, because in the past this didn't really
cause any issues. But it seems to have been uncovered by commit
567420d10895611e03d5ee65e6b24c16a69a6e99, which explicitly checks
for rs->waiting_for_stop_reply == 0, triggering the failures above.

The following patch fixes this by reorganizing the setting of
rs->waiting_for_stop_reply.

infrun: prepare_to_wait
Packet received: Ffstat,00000001,07fffdb0
Sending packet: $M7fffdb0,40:000000000000000000002080000000010000c336000001180000000000000000000000000000000000000200000000000000000055dfb19e55dfb19e55dfb19e#7b...Ack
Packet received: OK
Sending packet: $F0#76...Ack
infrun: target_wait (-1.0.0, status) =
infrun:   -1.0.0 [Thread 0],
infrun:   status->kind = ignore
infrun: TARGET_WAITKIND_IGNORE
infrun: prepare_to_wait
Packet received: Fisatty,00000001
Sending packet: $F1#77...Ack
infrun: target_wait (-1.0.0, status) =
infrun:   -1.0.0 [Thread 0],
infrun:   status->kind = ignore
infrun: TARGET_WAITKIND_IGNORE
infrun: prepare_to_wait
Packet received: Fwrite,00000001,0000d098,00000004
Sending packet: $md098,4#d2...Ack
Packet received: 3732300a
720
Sending packet: $F4#7a...Ack
infrun: target_wait (-1.0.0, status) =
infrun:   -1.0.0 [Thread 0],
infrun:   status->kind = ignore
infrun: TARGET_WAITKIND_IGNORE
infrun: prepare_to_wait
Packet received: Fwrite,00000001,07ffffac,00000011
Sending packet: $m7ffffac,11#8e...Ack
Packet received: 0a2a2a2a204558495420636f646520300a

*** EXIT code 0

Regression-tested on Ubuntu x86-64 and qemu-system-based debugging
for arm eabi.

gdb/ChangeLog:

2015-10-16  Luis Machado  <lgustavo@codesourcery.com>

	* remote.c (remote_wait_as): Set rs->waiting_for_stop_reply to 0
	when handling 'E', 'T', 'S', 'X' and 'W' packets.
	Do not set rs->waiting_for_stop_reply back to 1.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Correct printed value of Main in mmo.c consistency error message.
@ 2015-10-20  5:08 sergiodj+buildbot
  2015-10-20  5:42 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-20  5:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f9c62303d87da9c766ca67d01f602130c2777951 ***

Author: Hans-Peter Nilsson <hp@bitrange.com>
Branch: master
Commit: f9c62303d87da9c766ca67d01f602130c2777951

Correct printed value of Main in mmo.c consistency error message.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Add --enable-compressed-debug-sections={all, gas, gold, ld}
@ 2015-10-20 16:11 sergiodj+buildbot
  2015-10-20 16:47 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-20 16:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT edeefb679201858453502e21446d7a65fedeaf0e ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: edeefb679201858453502e21446d7a65fedeaf0e

Add --enable-compressed-debug-sections={all,gas,gold,ld}

This patch removes the gas configure option:

--enable-compressed-debug-sections

and adds a toplevel configure option:

--enable-compressed-debug-sections={all,gas,gold,ld}

to enable compressed debug sections for gas, gold or ld by default.  At
the moment, this configure option is ignored by gold and ld.  For x86
Linux targets, default to compressing debug sections in gas.

	PR gas/19109
	* configure.ac: Add
	--enable-compressed-debug-sections={all,gas,gold,ld}.
	* configure: Regenerated.

gas/

	PR gas/19109
	* NEWS: Update --enable-compressed-debug-sections=.
	* configure.ac: Remove --enable-compressed-debug-sections.
	(DEFAULT_FLAG_COMPRESS_DEBUG): Check
	--enable-compressed-debug-sections={all,gas} instead of
	--enable-compressed-debug-sections.  For x86 Linux targets,
	default to compressing debug sections.
	* configure: Regenerated.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [nto] Fixes for nto procfs.
@ 2015-10-20 17:16 sergiodj+buildbot
  2015-10-20 17:47 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-20 17:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 609c3040c2df944239d4d96644d736df605a6831 ***

Author: Aleksandar Ristovski <aristovski@qnx.com>
Branch: master
Commit: 609c3040c2df944239d4d96644d736df605a6831

[nto] Fixes for nto procfs.

Fix errnoeus construction of procfs path. The issue is, after the first
info pidlist or first run, the path for local node (the most common node)
will be reset to empty which makes subsequent queries and runs impossible.

gdb/ChangeLog:

	* nto-procfs.c (nto_procfs_path): Rename to...
	(nodestr): ... this, and change type.
	(nto_node): Use new variable and logic accordingly.
	(procfs_open_1): Use new variable name. Use local buffer to construct
	procfrs path.
	(procfs_pidlist): Use NODESTR to construct procfs path.
	(procfs_files_info): Use NODESTR to output meaningful text.
	(do_attach): Construct procfs using NODESTR.
	(procfs_create_inferior): Compare pointer to NULL.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [nto] Implement procfs_pid_to_exec_file.
@ 2015-10-20 17:32 sergiodj+buildbot
  2015-10-20 19:54 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-20 17:32 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e5343fde2046fbc19b9ac91326d5829d40066872 ***

Author: Aleksandar Ristovski <aristovski@qnx.com>
Branch: master
Commit: e5343fde2046fbc19b9ac91326d5829d40066872

[nto] Implement procfs_pid_to_exec_file.

gdb/ChangeLog:

	* gdb/nto-procfs.c (procfs_pid_to_exec_file): New function.
	(init_procfs_targets): Wire new function.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [nto] Implement TARGET_OBJECT_AUXV.
@ 2015-10-20 17:40 sergiodj+buildbot
  2015-10-20 18:50 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-20 17:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8a6c0ccdd27188047da2be9c2a49544c27dcade3 ***

Author: Aleksandar Ristovski <aristovski@qnx.com>
Branch: master
Commit: 8a6c0ccdd27188047da2be9c2a49544c27dcade3

[nto] Implement TARGET_OBJECT_AUXV.

Fix 'info auxv' for nto.

gdb/ChangeLog:

	* nto-procfs.c (sys/auxv.h): Include.
	(procfs_xfer_partial): Implement TARGET_OBJECT_AUXV.
	* nto-tdep.c (nto_read_auxv_from_initial_stack): New function.
	* nto-tdep.h (nto_read_auxv_from_initial_stack): New declaration.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix internal error on DW_OP_bregx(-1)
@ 2015-10-20 18:50 sergiodj+buildbot
  2015-10-20 20:50 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-20 18:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5f3ff4f893d7d70f79cb2daf4001be7047cd126b ***

Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Branch: master
Commit: 5f3ff4f893d7d70f79cb2daf4001be7047cd126b

Fix internal error on DW_OP_bregx(-1)

https://bugzilla.redhat.com/show_bug.cgi?id=1270564#c15
https://bugzilla.redhat.com/attachment.cgi?id=1081772

clang-3.5.0-9.fc22.x86_64
 <3><22b2>: Abbrev Number: 69 (DW_TAG_variable)
    <22b3>   DW_AT_location    : 7 byte block: 92 ff ff ff ff f 0	(DW_OP_bregx: 4294967295 (r-1) 0)
    <22bb>   DW_AT_name        : (indirect string, offset: 0x2a36): texture_data
    <22c1>   DW_AT_type        : <0x1d3>

(gdb) p variable
warning: Unmapped DWARF Register #-1 encountered.
regcache.c:177: internal-error: register_size: Assertion `regnum >= 0 && regnum < (gdbarch_num_regs (gdbarch) + gdbarch_num_pseudo_regs
(gdbarch))' failed.
[...]
Quit this debugging session? (y or n) FAIL: gdb.dwarf2/dw2-regno-invalid.exp: p variable (GDB internal error)

-> (x86_64)
(gdb) p variable
warning: Unmapped DWARF Register #-1 encountered.
Invalid register #-1, expecting 0 <= # < 220
(gdb) PASS: gdb.dwarf2/dw2-regno-invalid.exp: p variable
-> (i386)
(gdb) p variable
Invalid register #104, expecting 0 <= # < 104
(gdb) PASS: gdb.dwarf2/dw2-regno-invalid.exp: p variable

GDB calls gdbarch_dwarf2_reg_to_regnum() first which returns -1 in the x86_64
case
  if (regnum == -1)
    warning (_("Unmapped DWARF Register #%d encountered."), reg);
but in i386 case it does:
  /* This will hopefully provoke a warning.  */
  return gdbarch_num_regs (gdbarch) + gdbarch_num_pseudo_regs (gdbarch);
and the default implementation is a nop, leaving whatever register number
the DWARF specified.

gdb/ChangeLog
2015-10-20  Jan Kratochvil  <jan.kratochvil@redhat.com>

	* findvar.c (address_from_register): Check REGNUM validity.

gdb/testsuite/ChangeLog
2015-10-20  Jan Kratochvil  <jan.kratochvil@redhat.com>
	    Pedro Alves  <palves@redhat.com>

	* gdb.dwarf2/dw2-regno-invalid.exp: New file.
	* lib/dwarf.exp (Dwarf): Add DW_OP_bregx.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Reset x86 Linux targets to not compressing debug sections by default. Enable compression of debug sections by default in the linker, if so configured.
@ 2015-10-21 12:27 sergiodj+buildbot
  2015-10-21 13:37 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-21 12:27 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6c3bc0f82c625d425b09c01f96b64946abe4118e ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: 6c3bc0f82c625d425b09c01f96b64946abe4118e

Reset x86 Linux targets to not compressing debug sections by default.  Enable compression of debug sections by default in the linker, if so configured.

	PR gas/19109
.	* configure.ac: Note the 'none' is an acceptable argument to
	--enable-compressed-debug-sections.
	* configure: Regenerate.

gas	* configure.ac: Restore --enable-compressed-debug-sections.
	Do not enable compressed debug sections by default for x86 Linux
	targets.
	* configure: Regenerate.

ld	* configure.ac: Add --enable-compressed-debug-sections.
	* configure: Regenerate.
	* config.in: Regenerate.
	* ld.texinfo: Document how to determine the default action for
	debug sections.
	* ldmain.c (main): If DEFAULT_FLAG_COMPRESS_DEBUG is defined then
	set the compress_debug field of the link_info structure to
	zlib-gabi.
	* lexsup.c (elf_static_list_options): Output the default setting
	for the --compress-debug-sections option.
	* NEWS: Mention the new configure option.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [nto] Fix nto target stopped by watchpoint.
@ 2015-10-21 14:47 sergiodj+buildbot
  2015-10-21 15:15 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-21 14:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a9889169e5b21efb8c42105fc62461be43968d64 ***

Author: Aleksandar Ristovski <aristovski@qnx.com>
Branch: master
Commit: a9889169e5b21efb8c42105fc62461be43968d64

[nto] Fix nto target stopped by watchpoint.

Fix 'stopped by watchpoint' detection: add inferior data, use inferior data
for storing last stopped flags needed for detection.

gdb/ChangeLog:

	* nto-procfs.c (procfs_wait): Set stopped_flags nad stopped_pc.
	(procfs_stopped_by_watchpoint): Use flags stored in inferior data.
	* nto-tdep.c (nto_new_inferior_data_reg): New definition.
	(nto_new_inferior_data, nto_inferior_data_cleanup, nto_inferior_data):
	New functions.
	(_initialize_nto_tdep): New forward declaration, new function.
	* nto-tdep.h (struct nto_inferior_data): New struct.
	(nto_inferior_data): New function declaration.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [nto] Improve ABI sniffing.
@ 2015-10-21 14:54 sergiodj+buildbot
  2015-10-21 16:14 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-21 14:54 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d7161de46af80e460d432d8dbb1c42f8cbacf6dc ***

Author: Aleksandar Ristovski <aristovski@qnx.com>
Branch: master
Commit: d7161de46af80e460d432d8dbb1c42f8cbacf6dc

[nto] Improve ABI sniffing.

Use qnx specific notes to figure out the OS.

gdb/ChangeLog:
	* gdb/nto-tdep.c (QNX_NOTE_NAME, QNX_INFO_SECT_NAME): New defines.
	(nto_sniff_abi_note_section): New function.
	(nto_elf_osabi_sniffer): Use new function to recognize nto specific
	binary.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Add the target_ops needed for software breakpoints in GDBServer.
@ 2015-10-21 15:35 sergiodj+buildbot
  2015-10-21 18:15 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-21 15:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT dd373349578df87396bc43e7ab00a1a5ceb16c8b ***

Author: Antoine Tremblay <antoine.tremblay@ericsson.com>
Branch: master
Commit: dd373349578df87396bc43e7ab00a1a5ceb16c8b

Add the target_ops needed for software breakpoints in GDBServer.

This patch is in preparation for software breakpoints on ARM linux.  It
refactors breakpoint and breakpoint_len into breakpoint_kind_from_pc and
sw_breakpoint_from kind to prepare the case where we have multiple types of
breakpoints.

Kind is the type of breakpoint (hardware or software) to be inserted, usually it
is the lenght of the software breakpoint but can be something else depending on
the target.

This patch introduces the linux_target_ops breakpoint_kind_from_pc and
sw_breakpoint_from_kind.

breakpoint_kind_from_pc returns the breakpoint kind and adjusts the PC to the
real memory location in case a flag was present in the PC. E.g the instruction
mode on ARM.

sw_breakpoint_from_kind returns the software breakpoint for this kind as a
string of bytes, the length of the breakpoint is adjusted for the breakpoint's
size in memory.

For targets that have only one kind of breakpoint, the default value 0 is
returned by linux_breakpoint_kind_from_pc so that not all targets need to
implement the breakpoint_kind_from_pc operation.

No regressions, tested on Ubuntu 14.04 on ARMv7 and x86
With gdbserver-{native,extended} / { -marm -mthumb }

Also since the target_ops have been changed compilation was tested on
affected archs namely : aarch64, arm, bfin, cris, crisv32, m32r,
m68k, mips, nios2, ppc, s390, sparc, tic6x, tile, x86, steins.

Not tested : sh

gdb/gdbserver/ChangeLog:

	* linux-aarch64-low.c (aarch64_sw_breakpoint_from_kind): New function.
	(struct linux_target_ops) <breakpoint>: Remove.
	(struct linux_target_ops) <breakpoint_len>: Remove.
	(struct linux_target_ops) <breakpoint_kind_from_pc>: Initialize field.
	(struct linux_target_ops) <sw_breakpoint_from_kind>: Initialize field.
	* linux-arm-low.c (arm_breakpoint_kind_from_pc): New function.
	(arm_sw_breakpoint_from_kind): New function.
	* linux-bfin-low.c (bfin_sw_breakpoint_from_kind): New function.
	(struct linux_target_ops) <breakpoint>: Remove.
	(struct linux_target_ops) <breakpoint_len>: Remove.
	(struct linux_target_ops) <breakpoint_kind_from_pc>: Initialize field.
	(struct linux_target_ops) <sw_breakpoint_from_kind>: Initialize field.
	* linux-cris-low.c (cris_sw_breakpoint_from_kind): New function.
	(struct linux_target_ops) <breakpoint>: Remove.
	(struct linux_target_ops) <breakpoint_len>: Remove.
	(struct linux_target_ops) <breakpoint_kind_from_pc>: Initialize field.
	(struct linux_target_ops) <sw_breakpoint_from_kind>: Initialize field.
	* linux-crisv32-low.c (cris_sw_breakpoint_from_kind): New function.
	(struct linux_target_ops) <breakpoint>: Remove.
	(struct linux_target_ops) <breakpoint_len>: Remove.
	(struct linux_target_ops) <breakpoint_kind_from_pc>: Initialize field.
	(struct linux_target_ops) <sw_breakpoint_from_kind>: Initialize field.
	* linux-low.c (linux_wait_1): Call breakpoint_kind_from_pc
	and sw_breakpoint_from_kind to increment the pc.
	(linux_breakpoint_kind_from_pc): New function.
	(linux_sw_breakpoint_from_kind): New function.
	(struct target_ops) <sw_breakpoint_from_kind>: Initialize field.
	(initialize_low): Call breakpoint_kind_from_pc and
	sw_breakpoint_from_kind to replace breakpoint_data/len.
	* linux-low.h (struct linux_target_ops) <breakpoint_kind_from_pc>:
	New field.
	(struct linux_target_ops) <sw_breakpoint_from_kind>: Likewise.
	* linux-m32r-low.c (m32r_sw_breakpoint_from_kind): New function.
	(struct linux_target_ops) <breakpoint>: Remove.
	(struct linux_target_ops) <breakpoint_len>: Remove.
	(struct linux_target_ops) <breakpoint_kind_from_pc>: Initialize field.
	(struct linux_target_ops) <sw_breakpoint_from_kind>: Initialize field.
	* linux-m68k-low.c (m68k_sw_breakpoint_from_kind): New function.
	(struct linux_target_ops) <breakpoint>: Remove.
	(struct linux_target_ops) <breakpoint_len>: Remove.
	(struct linux_target_ops) <breakpoint_kind_from_pc>: Initialize field.
	(struct linux_target_ops) <sw_breakpoint_from_kind>: Initialize field.
	* linux-mips-low.c (mips_sw_breakpoint_from_kind): New function.
	(struct linux_target_ops) <breakpoint>: Remove.
	(struct linux_target_ops) <breakpoint_len>: Remove.
	(struct linux_target_ops) <breakpoint_kind_from_pc>: Initialize field.
	(struct linux_target_ops) <sw_breakpoint_from_kind>: Initialize field.
	* linux-nios2-low.c (nios2_sw_breakpoint_from_kind): New function.
	(struct linux_target_ops) <breakpoint>: Remove.
	(struct linux_target_ops) <breakpoint_len>: Remove.
	(struct linux_target_ops) <breakpoint_kind_from_pc>: Initialize field.
	(struct linux_target_ops) <sw_breakpoint_from_kind>: Initialize field.
	* linux-ppc-low.c (ppc_sw_breakpoint_from_kind): New function.
	(struct linux_target_ops) <breakpoint>: Remove.
	(struct linux_target_ops) <breakpoint_len>: Remove.
	(struct linux_target_ops) <breakpoint_kind_from_pc>: Initialize field.
	(struct linux_target_ops) <sw_breakpoint_from_kind>: Initialize field.
	* linux-s390-low.c (s390_sw_breakpoint_from_kind): New function.
	(struct linux_target_ops) <breakpoint>: Remove.
	(struct linux_target_ops) <breakpoint_len>: Remove.
	(struct linux_target_ops) <breakpoint_kind_from_pc>: Initialize field.
	(struct linux_target_ops) <sw_breakpoint_from_kind>: Initialize field.
	* linux-sh-low.c (sh_sw_breakpoint_from_kind): New function.
	(struct linux_target_ops) <breakpoint>: Remove.
	(struct linux_target_ops) <breakpoint_len>: Remove.
	(struct linux_target_ops) <breakpoint_kind_from_pc>: Initialize field.
	(struct linux_target_ops) <sw_breakpoint_from_kind>: Initialize field.
	* linux-sparc-low.c (sparc_sw_breakpoint_from_kind): New function.
	(struct linux_target_ops) <breakpoint>: Remove.
	(struct linux_target_ops) <breakpoint_len>: Remove.
	(struct linux_target_ops) <breakpoint_kind_from_pc>: Initialize field.
	(struct linux_target_ops) <sw_breakpoint_from_kind>: Initialize field.
	* linux-tic6x-low.c (tic6x_sw_breakpoint_from_kind): New function.
	(struct linux_target_ops) <breakpoint>: Remove.
	(struct linux_target_ops) <breakpoint_len>: Remove.
	(struct linux_target_ops) <breakpoint_kind_from_pc>: Initialize field.
	(struct linux_target_ops) <sw_breakpoint_from_kind>: Initialize field.
	* linux-tile-low.c (tile_sw_breakpoint_from_kind): New function.
	* linux-x86-low.c (x86_sw_breakpoint_from_kind): New function.
	(struct linux_target_ops) <breakpoint>: Remove.
	(struct linux_target_ops) <breakpoint_len>: Remove.
	(struct linux_target_ops) <breakpoint_kind_from_pc>: Initialize field.
	(struct linux_target_ops) <sw_breakpoint_from_kind>: Initialize field.
	* linux-xtensa-low.c (xtensa_sw_breakpoint_from_kind) New function.
	(struct linux_target_ops) <breakpoint>: Remove.
	(struct linux_target_ops) <breakpoint_len>: Remove.
	(struct linux_target_ops) <breakpoint_kind_from_pc>: Initialize field.
	(struct linux_target_ops) <sw_breakpoint_from_kind>: Initialize field.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Support breakpoint kinds for software breakpoints in GDBServer.
@ 2015-10-21 15:42 sergiodj+buildbot
  2015-10-21 19:16 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-21 15:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2716529498941971b698f603e9aa0edc89905cb8 ***

Author: Antoine Tremblay <antoine.tremblay@ericsson.com>
Branch: master
Commit: 2716529498941971b698f603e9aa0edc89905cb8

Support breakpoint kinds for software breakpoints in GDBServer.

There's two ways to set breakpoints in GDBServer.

 - GDBServer setting its own breakpoints, through API set_breakpoint_at.

 - GDBServer setting breakpoints according to the information in Z
   packets, through API set_gdb_breakpoint.

Before this patch the breakpoint kinds were a concept unique to GDB and Z
packets, as GDBServer never had to set different kinds of breakpoint on its
own.

This patch teaches GDBServer to handle breakpoint kinds for its own
breakpoints. It generalizes the breakpoint kind as per Z packets to
represent different kinds of breakpoints directly set by GDBServer also.

GDBServer now querys breakpoint_kind_from_pc to know what breakpoint kind to
set on its own.

As the kind is now a differentiating factor equivalent to size for the
breakpoint struct and that it's size can be queried using
sw_breakpoint_from_kind, the size field has been replaced with the kind field.
All references to size are now replaced by kind or a call to bp_size that wraps
sw_breakpoing_from_kind and returns the size of the breakpoint in memory.

To fetch the software breakpoint data bp_opcode is called and wraps the
sw_breakpoint_from_kind call.

No regressions on Ubuntu 14.04 on ARMv7 and x86.
With gdbserver-{native,extended} / { -marm -mthumb }

gdb/gdbserver/ChangeLog:

	* linux-low.c (initialize_low): Ajdust for breakpoint global variables
	removal.
	* mem-break.c : Remove breakpoint_data/breakpoint_len global variables.
	(struct raw_breakpoint) <size>: Remove.
	(struct raw_breakpoint) <kind>: Add.
	(bp_size): New function.
	(bp_opcode): Likewise.
	(find_raw_breakpoint_at): Adjust for kind.
	(insert_memory_breakpoint): Adjust for kind call bp_size,bp_opcode.
	(remove_memory_breakpoint): Adjust for kind call bp_size.
	(set_raw_breakpoint_at): Adjust for kind.
	(set_breakpoint): Likewise.
	(set_breakpoint_at): Call breakpoint_kind_from_pc.
	(delete_raw_breakpoint): Adjust for kind.
	(delete_breakpoint): Likewise.
	(find_gdb_breakpoint): Likewise.
	(set_gdb_breakpoint_1): Likewise.
	(set_gdb_breakpoint): Likewise.
	(delete_gdb_breakpoint_1): Likewise.
	(delete_gdb_breakpoint): Likewise.
	(uninsert_raw_breakpoint): Likewise.
	(reinsert_raw_breakpoint): Likewise.
	(set_breakpoint_data): Remove.
	(validate_inserted_breakpoint): Adjust for kind call bp_size,bp_opcode.
	(check_mem_read): Adjust for kind call bp_size.
	(check_mem_write): Adjust for kind call bp_size,bp_opcode.
	(clone_one_breakpoint): Adjust for kind.
	* mem-break.h (set_gdb_breakpoint): Likewise.
	(delete_gdb_breakpoint): Likewise.
	* server.c (process_serial_event): Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Implement breakpoint_kind_from_pc and sw_breakpoint_from_kind for ARM in GDBServer.
@ 2015-10-21 16:43 sergiodj+buildbot
  2015-10-21 20:17 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-21 16:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8689682cc375f6f30d65f1583b3aaa3e6a1e4d63 ***

Author: Antoine Tremblay <antoine.tremblay@ericsson.com>
Branch: master
Commit: 8689682cc375f6f30d65f1583b3aaa3e6a1e4d63

Implement breakpoint_kind_from_pc and sw_breakpoint_from_kind for ARM in GDBServer.

ARM can have multiple breakpoint types based on the instruction set
it's currently in: arm, thumb or thumb2.

GDBServer needs to know what breakpoint is to be inserted at location
when inserting a breakpoint.

This is handled by the breakpoint_kind_from_pc and sw_breakpoint_from_kind
target ops introduced in a previous patch, this patch adds the
arm_breakpoint_kind_from_pc and arm_sw_breakpoint_from_kind implementation so
that the proper breakpoint type is returned based on the pc.

Also in order to share some code with GDB a new file called arm.c have been
introduced in arch/.

While this file does not contain much yet future patches will add more
to it thus the inclusion at this stage.

No regressions on Ubuntu 14.04 on ARMv7 and x86.
With gdbserver-{native,extended} / { -marm -mthumb }

gdb/ChangeLog:

	* Makefile.in: Add arm.c/o.
	* arch/arm.c: New file.
	* arch/arm.h: (IS_THUMB_ADDR): Move macro from arm-tdep.c.
	(MAKE_THUMB_ADDR): Likewise.
	(UNMAKE_THUMB_ADDR): Likewise.
	* arm-tdep.c (int thumb_insn_size): Move to arm.c.
	(IS_THUMB_ADDR): Move to arm.h.
	(MAKE_THUMB_ADDR): Likewise.
	(UNMAKE_THUMB_ADDR): Likewise.
	* configure.tgt: Add arm.o to all ARM configs.

gdb/gdbserver/ChangeLog:

	* Makefile.in: Add arm.c/o.
	* configure.srv: Likewise.
	* linux-arm-low.c (arm_breakpoint_kinds): New enum.
	(arm_breakpoint_kind_from_pc): New function.
	(arm_sw_breakpoint_from_kind): Return proper kind.
	(struct linux_target_ops) <breakpoint_kind_from_pc>: Initialize.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Adjust timeout in gdb.base/freebpcmd.exp.
@ 2015-10-21 17:05 sergiodj+buildbot
  2015-10-21 23:22 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-21 17:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 27145d50705b46e213f5f261bd07572383c79e20 ***

Author: Sandra Loosemore <sandra@codesourcery.com>
Branch: master
Commit: 27145d50705b46e213f5f261bd07572383c79e20

Adjust timeout in gdb.base/freebpcmd.exp.

2015-10-21  Sandra Loosemore  <sandra@codesourcery.com>

	gdb/testsuite/
	* gdb.base/freebpcmd.exp: Use with_timeout_factor instead
	of hardwired timeout value.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] fort_dyn_array: add basic fortran dyn array support
@ 2015-10-21 19:47 sergiodj+buildbot
  2015-10-22  1:01 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-21 19:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3f2f83ddcba5b04389dd3c666ce7d4cace7e5b63 ***

Author: Keven Boell <keven.boell@linux.intel.com>
Branch: master
Commit: 3f2f83ddcba5b04389dd3c666ce7d4cace7e5b63

fort_dyn_array: add basic fortran dyn array support

Fortran provide types whose values may be dynamically allocated
or associated with a variable under explicit program control.
The purpose of this commit is:

  * to read allocated/associated DWARF tags and store them in
    the dynamic property list of main_type.

  * enable GDB to print the value of a dynamic array in Fortran
    in case the type is allocated or associated (pointer to
    dynamic array).

Examples:
    (gdb) p vla_not_allocated
    $1 = <not allocated>

    (gdb) p vla_allocated
    $1 = (1, 2, 3)

    (gdb) p vla_ptr_not_associated
    $1 = <not associated>

    (gdb) p vla_ptr_associated
    $1 = (1, 2, 3)

Add basic test coverage for most dynamic array use-cases in Fortran.
The commit contains the following tests:
  * Ensure that values of Fortran dynamic arrays
    can be evaluated correctly in various ways and states.
  * Ensure that Fortran primitives can be evaluated
    correctly when used as a dynamic array.
  * Dynamic arrays passed to subroutines and handled
    in different ways inside the routine.
  * Ensure that the ptype of dynamic arrays in
    Fortran can be printed in GDB correctly.
  * Ensure that dynamic arrays in different states
    (allocated/associated) can be evaluated.
  * Dynamic arrays passed to functions and returned from
    functions.
  * History values of dynamic arrays can be accessed and
    printed again with the correct values.
  * Dynamic array evaluations using MI protocol.
  * Sizeof output of dynamic arrays in various states.

The patch was tested using the test suite on Ubuntu 12.04 64bit.

gdb/ChangeLog:

        * dwarf2read.c (set_die_type): Add read of
        DW_AT_allocated and DW_AT_associated.
        * f-typeprint.c: New include of typeprint.h
        (f_print_type): Add check for allocated/associated
        status of type.
        (f_type_print_varspec_suffix): Add check for
        allocated/associated status of type.
        * gdbtypes.c (create_array_type_with_stride):
        Add check for valid data location of type in
        case allocated or associated attributes are set.
        Length of an array should be only calculated if
        allocated or associated is resolved as true.
        (is_dynamic_type_internal): Add check for allocated/
        associated.
        (resolve_dynamic_array): Evaluate allocated/associated
        properties.
        * gdbtypes.h (enum dynamic_prop_node_kind): <DYN_PROP_ALLOCATED>
        <DYN_PROP_ASSOCIATED>: New enums.
        (TYPE_ALLOCATED_PROP, TYPE_ASSOCIATED_PROP): New macros.
        (type_not_allocated): New function.
        (type_not_associated): New function.
        * valarith.c (value_subscripted_rvalue): Add check for
        allocated/associated.
        * valprint.c: New include of typeprint.h.
        (valprint_check_validity): Add check for allocated/associated.
        (value_check_printable): Add check for allocated/
        associated.
        * typeprint.h (val_print_not_allocated): New function.
        (val_print_not_associated): New function.
        * typeprint.c (val_print_not_allocated): New function.
        (val_print_not_associated): New function.

gdb/testsuite/ChangeLog:

        * gdb.fortran/vla-alloc-assoc.exp: New file.
        * gdb.fortran/vla-datatypes.exp: New file.
        * gdb.fortran/vla-datatypes.f90: New file.
        * gdb.fortran/vla-history.exp: New file.
        * gdb.fortran/vla-ptype-sub.exp: New file.
        * gdb.fortran/vla-ptype.exp: New file.
        * gdb.fortran/vla-sizeof.exp: New file.
        * gdb.fortran/vla-sub.f90: New file.
        * gdb.fortran/vla-value-sub-arbitrary.exp: New file.
        * gdb.fortran/vla-value-sub-finish.exp: New file.
        * gdb.fortran/vla-value-sub.exp: New file.
        * gdb.fortran/vla-value.exp: New file.
        * gdb.fortran/vla-ptr-info.exp: New file.
        * gdb.mi/mi-vla-fortran.exp: New file.
        * gdb.mi/vla.f90: New file.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix accessing a function's fields (parameters) from Python (PR 18073)
@ 2015-10-21 20:12 sergiodj+buildbot
  2015-10-22  3:10 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-21 20:12 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bed91f4da252b5f30d3cb4fd9f9febd61ad9560d ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: bed91f4da252b5f30d3cb4fd9f9febd61ad9560d

Fix accessing a function's fields (parameters) from Python (PR 18073)

Since 7.4, gdb doesn't allow calling .fields() on a function type, even
though the documentation states it should return a list corresponding to
the function's parameters.  This patch restores the intended behaviour
and adds a test for it.

Reg-tested on Arch Linux x86-64.

gdb/ChangeLog:

	PR python/18073
	* python/py-type.c (typy_get_composite): Allow returning a
	function type.

gdb/testsuite/ChangeLog:

	PR python/18073
	* gdb.python/py-type.c (C::a_method): New.
	(C::a_const_method): New.
	(C::a_static_method): New.
	(a_function): New.
	* gdb.python/py-type.exp (test_fields): Test getting fields
	from function and method.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] S/390: ifunc: Fix for undefined ifunc symbols.
@ 2015-10-22  8:43 sergiodj+buildbot
  2015-10-22  9:54 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-22  8:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0a511368e2b896fe84f3b4bce5390e6269bcc57b ***

Author: Andreas Krebbel <krebbel@linux.vnet.ibm.com>
Branch: master
Commit: 0a511368e2b896fe84f3b4bce5390e6269bcc57b

S/390: ifunc: Fix for undefined ifunc symbols.

bfd/ChangeLog:

	* elf32-s390.c (elf_s390_finish_dynamic_symbol): Call
	elf_s390_finish_ifunc_symbol only for actually defined symbols.
	* elf64-s390.c (elf_s390_finish_dynamic_symbol): Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] S/390: ifunc: Fix function pointers to hidden ifunc symbols.
@ 2015-10-22  8:59 sergiodj+buildbot
  2015-10-22 12:56 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-22  8:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d8ee9e44cc9a986b063a6ea6c91d39217cce65a1 ***

Author: Andreas Krebbel <krebbel@linux.vnet.ibm.com>
Branch: master
Commit: d8ee9e44cc9a986b063a6ea6c91d39217cce65a1

S/390: ifunc: Fix function pointers to hidden ifunc symbols.

bfd/ChangeLog:
	* elf32-s390.c (elf_s390_adjust_dynamic_symbol): Set the PLT
	reference counters for local IFUNC calls.
	* elf64-s390.c (elf_s390_adjust_dynamic_symbol): Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] S/390: ifunc: Redirect local function calls to the IPLT.
@ 2015-10-22  9:07 sergiodj+buildbot
  2015-10-22 13:57 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-22  9:07 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 99ba51255402201c6e193d803ee1f1fc3f2de0e6 ***

Author: Andreas Krebbel <krebbel@linux.vnet.ibm.com>
Branch: master
Commit: 99ba51255402201c6e193d803ee1f1fc3f2de0e6

S/390: ifunc: Redirect local function calls to the IPLT.

bfd/ChangeLog:

	* elf32-s390.c (elf_s390_check_relocs): Set the non_got_ref marker
	only when linking an executable.
	(elf_s390_relocate_section): Redirect PC-relative relocs to a IPLT
	slot.
	* elf64-s390.c (elf_s390_check_relocs): Set the non_got_ref marker
	only when linking an executable.
	(elf_s390_relocate_section): Redirect PC-relative relocs to a IPLT
	slot.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] S/390: ifunc: Handle GOTOFF relocs on ifunc symbols.
@ 2015-10-22  9:43 sergiodj+buildbot
  2015-10-22 12:08 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-22  9:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 01a53584798606cf6329e8a86134cb9b47d1de11 ***

Author: Andreas Krebbel <krebbel@linux.vnet.ibm.com>
Branch: master
Commit: 01a53584798606cf6329e8a86134cb9b47d1de11

S/390: ifunc: Handle GOTOFF relocs on ifunc symbols.

Normally a GOTOFF reloc only uses the GOT pointer to address something
relativ to it without actually requiring a GOT or PLT slot.  Things
change if the target is an ifunc symbol though.

bfd/ChangeLog:

	* elf32-s390.c (elf_s390_check_relocs): Fallthrough to the PLT
	slot allocating code for GOTOFF relocs on ifunc symbols.
	(elf_s390_gc_sweep_hook): Decrement plt refcount for GOTOFF relocs
	on ifunc symbols.
	(elf_s390_relocate_section): Redirect a GOTOFF reloc to an iplt
	slot.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Add "-z call-nop=PADDING" option to ld
@ 2015-10-22 12:23 sergiodj+buildbot
  2015-10-22 16:58 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-22 12:23 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT caa65211bbbfd53c40c9ce1b79b97ccf2c679a52 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: caa65211bbbfd53c40c9ce1b79b97ccf2c679a52

Add "-z call-nop=PADDING" option to ld

The ld linker can transform indirect call to a locally defined function,
foo, via its GOT slot, to either "NOP call foo" or "call foo NOP" where
NOP is a 1-byte NOP padding.  This patch adds a "-z call-nop=PADDING"
option to x86 ld to control 1-byte NOP padding for x86 call instruction.
PADDING is one of prefix-addr, prefix-nop, suffix-nop, prefix-NUMBER or
suffix-NUMBER.

bfd/

	* elf32-i386.c (elf_i386_convert_load): Use call_nop_byte and
	check call_nop_as_suffix for 1-byte NOP padding to pad call.
	* elf64-x86-64.c (elf_x86_64_convert_load): Likewise.

include/

	* bfdlink.h (bfd_link_info): Add call_nop_as_suffix and
	call_nop_byte.

ld/

	* ld/ld.texinfo: Document "-z call-nop=PADDING" option.
	* emulparams/call_nop.sh: New file.
	* emulparams/elf_i386_be.sh: Source
	${srcdir}/emulparams/call_nop.sh.
	* emulparams/elf_i386_chaos.sh: Likewise.
	* emulparams/elf_i386_ldso.sh: Likewise.
	* emulparams/elf_i386_vxworks.sh: Likewise.
	* emulparams/elf_iamcu.sh: Likewise.
	* emulparams/elf_k1om.sh: Likewise.
	* emulparams/elf_l1om.sh: Likewise.
	* emulparams/elf_x86_64.sh: Likewise.
	* emultempl/elf32.em (gld${EMULATION_NAME}_before_parse): Set
	link_info.call_nop_byte if $CALL_NOP_BYTE isn't empty.

ld/testsuite/

	* ld-i386/call3.s: New file.
	* ld-i386/call3a.d: Likewise.
	* ld-i386/call3b.d: Likewise.
	* ld-i386/call3c.d: Likewise.
	* ld-i386/call3d.d: Likewise.
	* ld-i386/call3e.d: Likewise.
	* ld-i386/call3f.d: Likewise.
	* ld-i386/call3g.d: Likewise.
	* ld-i386/call3h.d: Likewise.
	* ld-i386/load1-nacl.d: Likewise.
	* ld-x86-64/call1.s: Likewise.
	* ld-x86-64/call1a.d: Likewise.
	* ld-x86-64/call1b.d: Likewise.
	* ld-x86-64/call1c.d: Likewise.
	* ld-x86-64/call1d.d: Likewise.
	* ld-x86-64/call1e.d: Likewise.
	* ld-x86-64/call1f.d: Likewise.
	* ld-x86-64/call1g.d: Likewise.
	* ld-x86-64/call1h.d: Likewise.
	* ld-x86-64/call1i.d: Likewise.
	* ld-x86-64/load1a-nacl.d: Likewise.
	* ld-x86-64/load1b-nacl.d: Likewise.
	* ld-x86-64/load1c-nacl.d: Likewise.
	* ld-x86-64/load1d-nacl.d: Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] mips: fix void*/gdb_byte* compilation errors
@ 2015-10-22 13:59 sergiodj+buildbot
  2015-10-22 17:57 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-22 13:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 709476c3c595fb61f155ba453733809d3e76ed51 ***

Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: 709476c3c595fb61f155ba453733809d3e76ed51

mips: fix void*/gdb_byte* compilation errors

The error in mips64_linux_get_longjmp_target is fixed by changing "buf"
to be a gdb_byte*, as usual.  supply_32bit_reg and mips64_fill_gregset
do some more complicated things however, so it's safer just to add the
explicit cast and avoid changing the code too much.

gdb/ChangeLog:

	* mips-linux-tdep.c (mips64_linux_get_longjmp_target): Change type of
	buf to gdb_byte*.
	(supply_32bit_reg): Add cast.
	(mips64_fill_gregset): Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Add cast in nto-tdep.c
@ 2015-10-22 16:10 sergiodj+buildbot
  2015-10-23  0:02 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-22 16:10 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fb70bc1a74d371cc6cc07e018df436a17c26037e ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: fb70bc1a74d371cc6cc07e018df436a17c26037e

Add cast in nto-tdep.c

gdb/ChangeLog:

	* nto-tdep.c (nto_inferior_data): Add cast.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Add cast in python.c
@ 2015-10-22 16:23 sergiodj+buildbot
  2015-10-23  2:01 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-22 16:23 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT db0f0d0c1d0541b6c2f81d655cd5420e059c91d4 ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: db0f0d0c1d0541b6c2f81d655cd5420e059c91d4

Add cast in python.c

gdb/ChangeLog:

	* python/python.c (_initialize_python): Add cast.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix inconsistent breakpoint kinds between breakpoints and tracepoints in GDBServer.
@ 2015-10-22 16:35 sergiodj+buildbot
  2015-10-23  4:05 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-22 16:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1652a98612a20443c0e17fd90e7f6941b7bc3ad8 ***

Author: Antoine Tremblay <antoine.tremblay@ericsson.com>
Branch: master
Commit: 1652a98612a20443c0e17fd90e7f6941b7bc3ad8

Fix inconsistent breakpoint kinds between breakpoints and tracepoints in GDBServer.

This patch fixes a regression introduced by :
https://sourceware.org/ml/gdb-patches/2015-10/msg00369.html

Tests : gdb.trace/trace-break.exp and gdb.trace/trace-mt.exp would fail on x86
with gdbserver-{native,extended}.

Before this patch, the breakpoint kind set by GDB with a Z packet and the one
set in the case of a tracepoint would be inconsistent on targets that did not
implement breakpoint_kind_from_pc. On x86 for example a breakpoint set by GDB
would have a kind of 1 but a breakpoint set by a tracepoint would have a kind of
0.

This created a missmatch when trying to insert a tracepoint and a breakpoint at
the same location. One of the two breakpoints would be removed with debug
message : "Inconsistent breakpoint kind".

This patch fixes the issue by changing the default 0 breakpoint kind to be
the size of the breakpoint according to sw_breakpoint_from_kind.

The default breakpoint kind must be the breakpoint length to keep consistency
between breakpoints set via GDB and the ones set internally by GDBServer.

No regression on Ubuntu 14.04 x86-64 with gdbserver-{native-extended}

gdb/gdbserver/ChangeLog:

	* linux-low.c (default_breakpoint_kind_from_pc): New function.
	(linux_breakpoint_kind_from_pc): Use default_breakpoint_kind_from_pc for
	the default breakpoint kind.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] garbage collect gdb/infrun.c:stop_after_trap
@ 2015-10-22 16:53 sergiodj+buildbot
  2015-10-23  6:04 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-22 16:53 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d236ad1955a0a6b5203bc1474b989fd9dba668f8 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: d236ad1955a0a6b5203bc1474b989fd9dba668f8

garbage collect gdb/infrun.c:stop_after_trap

No longer used anywhere.

gdb/ChangeLog:
2015-10-22  Pedro Alves  <palves@redhat.com>

	* infrun.c (stop_after_trap): Delete.
	(clear_proceed_status, handle_signal_stop, struct
	infcall_control_state, save_infcall_control_state)
	(restore_infcall_control_state): Remove references to
	stop_after_trap.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
[parent not found: <3e45d68b7088df39d0520d1a92005cfdf4e2b922@gdb-build>]
* [binutils-gdb] Always keep sections marked with SEC_KEEP
@ 2015-10-22 19:35 sergiodj+buildbot
  2015-10-23  7:14 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-22 19:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bba037e0aef1f3b17cc6cf6fd041ed6110cc375a ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: bba037e0aef1f3b17cc6cf6fd041ed6110cc375a

Always keep sections marked with SEC_KEEP

SEC_KEEP check in elf_gc_sweep was missing in commit:

commit bde6f3eb6dff94cea1d471e15c6154d55d49820f
Author: H.J. Lu <hjl.tools@gmail.com>
Date:   Fri Jan 8 01:43:23 2010 +0000

    Set SEC_KEEP on section XXX for undefined __start_XXX/__stop_XXX

    bfd/

    2010-01-07  H.J. Lu  <hongjiu.lu@intel.com>

      PR ld/11133
      * elflink.c (_bfd_elf_gc_mark_hook): Check section XXX for
      undefined __start_XXX/__stop_XXX in all input files and set
      SEC_KEEP.

This patch adds SEC_KEEP check to elf_gc_sweep.

bfd/

	PR ld/19161
	* elflink.c (elf_gc_sweep): Always keep sections marked with
	SEC_KEEP.

ld/testsuite/

	PR ld/19161
	* ld-gc/gc.exp: Run pr19161 test.
	* ld-gc/pr19161-1.c: New file.
	* ld-gc/pr19161-2.c: Likewise.
	* ld-gc/pr19161.d: Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
[parent not found: <5af9928d44e302b7f68365a0c551f640895366ff@gdb-build>]
[parent not found: <60905b1e2a5fbd734bfd026cd77b9641cc5f3e66@gdb-build>]
* [binutils-gdb] Re: Always keep sections marked with SEC_KEEP
@ 2015-10-23  0:02 sergiodj+buildbot
  2015-10-23  8:36 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-23  0:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1e7eae0dcc0e5473dda573b30107ffdd501b0d73 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 1e7eae0dcc0e5473dda573b30107ffdd501b0d73

Re: Always keep sections marked with SEC_KEEP

Revert bba037e0, it breaks the gc-sections model.  Instead fix the
underlying problem which is that _bfd_elf_gc_mark_hook is too late to
be setting SEC_KEEP.

	PR ld/11133
	PR ld/19161
	* elflink.c (elf_gc_sweep): Revert last patch.
	(_bfd_elf_gc_mark_hook): Don't set SEC_KEEP here.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Initialize field insn_count correctly
@ 2015-10-23  8:38 sergiodj+buildbot
  2015-10-23  9:29 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-23  8:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 034f1a812d8f5655d08e2bdeb5ec7d56caa40d41 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 034f1a812d8f5655d08e2bdeb5ec7d56caa40d41

Initialize field insn_count correctly

This patch initialize dsd.insn_count, otherwise, it triggers the assert
below on testings we did recently.

gdb:

2015-10-23  Yao Qi  <yao.qi@linaro.org>

	* aarch64-tdep.c (aarch64_displaced_step_copy_insn): Set
	dsd.insn_count to zero.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Handle __start_* and __stop_* symbols in --gc-sections
@ 2015-10-23 12:05 sergiodj+buildbot
  2015-10-23 12:35 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-23 12:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1cce69b9dc8c58884c3cc4a8928fb234294e6886 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 1cce69b9dc8c58884c3cc4a8928fb234294e6886

Handle __start_* and __stop_* symbols in --gc-sections

	PR ld/11133
	PR ld/19161
	PR ld/19167
	* elflink.c (_bfd_elf_gc_mark_hook): Delete code handling __start_*
	and __stop_* symbol refs.
	(_bfd_elf_gc_mark_rsec): Add start_stop parameter.  Handle __start_*
	and __stop_* symbol refs here..
	(_bfd_elf_gc_mark_reloc): ..and here.
	* elf-bfd.h (_bfd_elf_gc_mark_hook): Update prototype.
	* elf-eh-frame.c (_bfd_elf_parse_eh_frame): Update
	_bfd_elf_gc_mark_rsec call.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Refactor default_breakpoint_kind_from_pc to be used by all targets in GDBServer.
@ 2015-10-23 17:33 sergiodj+buildbot
  2015-10-23 18:03 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-23 17:33 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2e6ee069ae81f3b5140059f6b997ccb0dcd1684e ***

Author: Antoine Tremblay <antoine.tremblay@ericsson.com>
Branch: master
Commit: 2e6ee069ae81f3b5140059f6b997ccb0dcd1684e

Refactor default_breakpoint_kind_from_pc to be used by all targets in GDBServer.

This patch moves default_breakpoint_kind_from_pc to target.c and creates a macro
so that all targets can easily use it.

This allows the breakpoint_kind_from_pc operation to be left unimplemented in
targets that do not need it.

This is preparation to fix the win32/nto/spu build that was broken by this
patch: https://sourceware.org/ml/gdb-patches/2015-10/msg00369.html

No regression on Ubuntu 14.04 x86-64 with gdbserver-{native-extended}

gdb/gdbserver/ChangeLog:

	* linux-low.c (default_breakpoint_kind_from_pc): Move to target.c.
	* mem-break.c (set_breakpoint_at): Use target_breakpoint_kind_from_pc.
	* target.c (default_breakpoint_kind_from_pc): Moved from linux-low.c
	* target.h (target_breakpoint_kind_from_pc): New macro.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix nto,spu and win32 builds of GDBServer.
@ 2015-10-23 17:40 sergiodj+buildbot
  2015-10-23 19:04 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-23 17:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fb78e89c56db8fddf3044cdc644d6e799ae97b3a ***

Author: Antoine Tremblay <antoine.tremblay@ericsson.com>
Branch: master
Commit: fb78e89c56db8fddf3044cdc644d6e799ae97b3a

Fix nto,spu and win32 builds of GDBServer.

This patch fixes the build that was broken by :
https://sourceware.org/ml/gdb-patches/2015-10/msg00369.html

It implements the sw_breakpoint_from_kind operation on these targets and removes
the calls to set_breakpoint_data.

Compiliation tested on win32.

Not tested : nto, spu.

gdb/gdbserver/ChangeLog:

	* nto-low.c (nto_sw_breakpoint_from_kind): New function.
	(struct target_ops) <sw_breakpoint_from_kind>: Initialize.
	(initialize_low): Remove set_breakpoint_data call.
	* spu-low.c (spu_sw_breakpoint_from_kind): New function.
	(struct target_ops) <sw_breakpoint_from_kind>: Iniitalize.
	(initialize_low): Remove set_breakpoint_data call.
	* win32-low.c (win32_sw_breakpoint_from_kind): New function.
	(struct target_ops) <sw_breakpoint_from_kind>: Initialize.
	(initialize_low): Remove set_breakpoint_data call.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Remove set_breakpoint_data definition in GDBServer.
@ 2015-10-23 17:48 sergiodj+buildbot
  2015-10-23 20:05 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-23 17:48 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3db2885585b1c4172d1534f96f4bf97f5f6c465f ***

Author: Antoine Tremblay <antoine.tremblay@ericsson.com>
Branch: master
Commit: 3db2885585b1c4172d1534f96f4bf97f5f6c465f

Remove set_breakpoint_data definition in GDBServer.

This patch removes the now unused set_breakpoint_data function from mem_break.h

gdb/gdbserver/ChangeLog:

	* mem-break.h (set_breakpoint_data): Remove.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Add cast to observer.sh
@ 2015-10-23 21:07 sergiodj+buildbot
  2015-10-23 21:39 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-23 21:07 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6ecf4e06a48cfc6dfbdf7c8f2969ffe7271f15da ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: 6ecf4e06a48cfc6dfbdf7c8f2969ffe7271f15da

Add cast to observer.sh

gdb/ChangeLog:

	* observer.h (observer_${event}_notification_stub): Add cast.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Add mmap casts in linux-btrace.c
@ 2015-10-24  0:05 sergiodj+buildbot
  2015-10-24  0:45 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-24  0:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a55515eecb1c8edb875e30a411afc55f304e88d9 ***

Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: a55515eecb1c8edb875e30a411afc55f304e88d9

Add mmap casts in linux-btrace.c

gdb/ChangeLog:

	* linux-btrace.c (linux_enable_pt): Add cast to mmap return.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] ia64-tdep.c: Remove (void *) casts
@ 2015-10-24 22:47 sergiodj+buildbot
  2015-10-24 23:20 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-24 22:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ce746418ef15c5a47b9ab17c249ba5f7c273db4a ***

Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: ce746418ef15c5a47b9ab17c249ba5f7c273db4a

ia64-tdep.c: Remove (void *) casts

Remove these (void *) casts, which cause a build failure in C++ mode.

gdb/ChangeLog:

	* ia64-tdep.c (ia64_pseudo_register_write): Remove cast.
	(ia64_push_dummy_call): Remove cast and change type of "to" to
	array of gdb_byte.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] proc-service.c: Add (gdb_byte *) cast
@ 2015-10-24 23:02 sergiodj+buildbot
  2015-10-25  3:00 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-24 23:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 49e66b4debebff088958077201eabab36df168f0 ***

Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: 49e66b4debebff088958077201eabab36df168f0

proc-service.c: Add (gdb_byte *) cast

A cast here is necessary, just as it's necessary in ps_pdwrite just
below.  The type of buf can't be changed, since it's fixed in the ps_pd*
API.

gdb/ChangeLog:

	* proc-service.c (ps_pdread): Add cast.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] sparc64-tdep.c: Don't assign using memcpy return
@ 2015-10-24 23:13 sergiodj+buildbot
  2015-10-25  0:29 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-24 23:13 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cfcb22a541ab8f783bf667cf7afbbfd9cd243cce ***

Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: cfcb22a541ab8f783bf667cf7afbbfd9cd243cce

sparc64-tdep.c: Don't assign using memcpy return

This:

  valbuf = memcpy (buf, valbuf, len);

causes a build failure in C++, because memcpy returns the value of
"buf" as a void *.  Instead of adding a cast, we can just do the
assignment separately.

gdb/ChangeLog:

	* sparc64-tdep.c (sparc64_store_arguments): Split assignment of
	valbuf.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] tui-data.c: Remove unnecessary casts
@ 2015-10-25  3:45 sergiodj+buildbot
  2015-10-25  8:45 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-25  3:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f4ee58bde946ec87c8ead17d7b47c1c7bcb7c3f6 ***

Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: f4ee58bde946ec87c8ead17d7b47c1c7bcb7c3f6

tui-data.c: Remove unnecessary casts

The (void *) casts make the build fail in C++ mode and are unnecessary.

gdb/ChangeLog:

	* tui/tui-data.c (tui_add_to_source_windows): Remove void *
	cast.
	(tui_add_content_elements): Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
[parent not found: <1650ca11248ca377a6c8b6f7e21ec2aa8e7b3fd5@gdb-build>]
* [binutils-gdb] Re-apply change for handling non-local references in nested functions.
@ 2015-10-25  8:29 sergiodj+buildbot
  2015-10-25 11:25 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-25  8:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2d5a88dc5005a4f4b0584d02719e479645409e92 ***

Author: Iain Buclaw <ibuclaw@gdcproject.org>
Branch: master
Commit: 2d5a88dc5005a4f4b0584d02719e479645409e92

Re-apply change for handling non-local references in nested functions.

gdb/ChangeLog:

	* d-exp.y: Remove an obsolete comment and propagate the block
	information to the produced expression.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] scm-symbol.c: Add (domain_enum) casts
@ 2015-10-26 12:52 sergiodj+buildbot
  2015-10-26 13:24 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-26 12:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 74ef968fbaab0bd52335314abdb3e0eb04020fb1 ***

Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: 74ef968fbaab0bd52335314abdb3e0eb04020fb1

scm-symbol.c: Add (domain_enum) casts

We currently pass integers as domain_enums to lookup_symbol.  The
most obvious fix is to add casts there.

I first thought of changing the type of the domain variables to
domain_enum.  However, because we pass a pointer to them to
gdbscm_parse_function_args, which expects them to be integers (because
of the format string), I don't think it would be correct.  If the enum
does not have the same size as an int, gdbscm_parse_function_args could
write past the memory of domain, overwriting something else on the
stack.

gdb/ChangeLog:

	* guile/scm-symbol.c (gdbscm_lookup_global_symbol): Add
	domain_enum cast.
	(gdbscm_lookup_symbol): Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] symtab.c: Add cast
@ 2015-10-26 13:08 sergiodj+buildbot
  2015-10-26 15:26 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-26 13:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 585a269afbfdb71b99ae72c22ef5101a800d565c ***

Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: 585a269afbfdb71b99ae72c22ef5101a800d565c

symtab.c: Add cast

gdb/ChangeLog:

	* symtab.c (default_make_symbol_completion_list_break_on_1): Add
	cast.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] gdbscm_memory_port_write: use local variable to avoid adding casts
@ 2015-10-26 13:08 sergiodj+buildbot
  2015-10-26 14:33 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-26 13:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e0dd41e9671fffc957c3d8f41adcd52274319f4f ***

Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: e0dd41e9671fffc957c3d8f41adcd52274319f4f

gdbscm_memory_port_write: use local variable to avoid adding casts

By having a local variable of type (const gdb_byte *), we can avoid adding
two casts.

gdb/ChangeLog:

	* guile/scm-ports.c (gdbscm_memory_port_write): Declare new
	"data" local variable and use it.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix constness problem in ioscm_make_gdb_stdio_port
@ 2015-10-26 13:17 sergiodj+buildbot
  2015-10-26 16:29 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-26 13:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 48ffa2b8cd986527a41654c3b27755bbf6762048 ***

Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: 48ffa2b8cd986527a41654c3b27755bbf6762048

Fix constness problem in ioscm_make_gdb_stdio_port

ioscm_make_gdb_stdio_port passes const char pointers (literal strings) to
scm_mode_bits, which takes a non-const char pointer.  Ideally, we would
change scm_mode_bits to take a const char pointer, but it's not part of
an API we control.

Instead, it's easy enough to build the string to pass to scm_mode_bits in
a (non-const) char array and pass that.

gdb/ChangeLog:

	* guile/scm-ports.c (ioscm_make_gdb_stdio_port): Pass non-const
	char pointer to scm_mode_bits.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Do not pass NULL for the string in catch_errors
@ 2015-10-26 13:29 sergiodj+buildbot
  2015-10-26 17:27 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-26 13:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7cc53fba0a4e5c316a6e86fdae28f8cc9d0f9a68 ***

Author: Luis Machado <lgustavo@codesourcery.com>
Branch: master
Commit: 7cc53fba0a4e5c316a6e86fdae28f8cc9d0f9a68

Do not pass NULL for the string in catch_errors

I caught a segmentation fault while running gdb.reverse/sigall-reverse.exp,
in a mingw32 GDB, in this code path. It boils down to the code trying to
strlen () a NULL pointer. I tracked things down and it looks like
record_full_message_wrapper_safe is the only offender.

gdb/ChangeLog:

2015-10-26  Luis Machado  <lgustavo@codesourcery.com>

	* record-full.c (record_full_message_wrapper_safe): Pass empty string to
	catch_errors call instead of NULL.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Properly convert address load of __start_XXX/__stop_XXX
@ 2015-10-26 15:26 sergiodj+buildbot
  2015-10-26 18:30 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-26 15:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a6af384b19c63bab4a1803c09592c5b5bd8674c2 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: a6af384b19c63bab4a1803c09592c5b5bd8674c2

Properly convert address load of __start_XXX/__stop_XXX

Since __start_XXX and __stop_XXX symbols aren't defined when address
load is being converted, we need to check if there is an XXX output
section to get their section and value.  This patch adds a new function,
bfd_link_get_defined_symbol, to search for the XXX output section to
check if __start_XXX and __stop_XXX symbols are defined.

bfd/

	PR ld/19171
	* elf32-i386.c (elf_i386_convert_load): Call
	bfd_link_get_defined_symbol to check if a symbol is defined.
	* elf64-x86-64.c (elf_x86_64_convert_load): Call
	bfd_link_get_defined_symbol to get defined symbol section and
	value.
	* linker.c (bfd_link_get_defined_symbol): New function.
	* bfd-in2.h: Regenerated.

ld/testsuite/

	PR ld/19171
	* ld-i386/lea1.s: Add tests for address load of __start_XXX
	and __stop_XXX.
	* ld-i386/mov1.s: Likewise.
	* ld-x86-64/lea1.s: Likewise.
	* ld-x86-64/mov1.s: Likewise.
	* ld-i386/lea1a.d: Updated.
	* ld-i386/lea1b.d: Likewise.
	* ld-i386/lea1c.d: Likewise.
	* ld-i386/mov1a.d: Likewise.
	* ld-i386/mov1b.d: Likewise.
	* ld-x86-64/lea1a.d: Likewise.
	* ld-x86-64/lea1b.d: Likewise.
	* ld-x86-64/lea1c.d: Likewise.
	* ld-x86-64/lea1d.d: Likewise.
	* ld-x86-64/lea1e.d: Likewise.
	* ld-x86-64/lea1f.d: Likewise.
	* ld-x86-64/mov1a.d: Likewise.
	* ld-x86-64/mov1b.d: Likewise.
	* ld-x86-64/mov1c.d: Likewise.
	* ld-x86-64/mov1d.d: Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] tui: Simplify tui_alloc_content
@ 2015-10-26 17:08 sergiodj+buildbot
  2015-10-26 19:28 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-26 17:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7acd011bef4e461e9caef644f20379f41ddfd631 ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: 7acd011bef4e461e9caef644f20379f41ddfd631

tui: Simplify tui_alloc_content

I stumbled upon this while doing some cxx-conversion work.  Since the
x-family alloc functions throw on failure, it is useless to test their
result for failure.  The else branch of != NULL is basically dead code.

I changed the type of element_block_ptr to struct tui_win_element, which
seems obvious (this is actually what raised the flag, casting the result
of xmalloc to struct tui_win_element* wouldn't work).

gdb/ChangeLog:

	* tui/tui-data.c (tui_alloc_content): Don't check xmalloc
	result.  Change type of element_block_ptr.  Change allocation to
	use XNEWVEC.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Add some casts for building on musl.
@ 2015-10-26 20:31 sergiodj+buildbot
  2015-10-26 21:28 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-26 20:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d41401ace01c234f42697e190a2ac95991780626 ***

Author: Doug Evans <dje@google.com>
Branch: master
Commit: d41401ace01c234f42697e190a2ac95991780626

Add some casts for building on musl.

gdb/ChangeLog:

	* linux-thread-db.c (find_new_threads_callback): Cast ti.ti_tid to
	unsigned long for debug_printf.
	(thread_db_pid_to_str): Ditto.

gdb/gdbserver/ChangeLog:

	* thread-db.c (find_one_thread): Cast ti.ti_tid to unsigned long
	for debug_printf.
	(attach_thread, find_new_threads_callback): Ditto.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] musl: Move W_STOPCODE to common/gdb_wait.h.
@ 2015-10-26 20:39 sergiodj+buildbot
  2015-10-26 22:27 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-26 20:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 963843d4d07aef6caa296dacf191f8adc9518596 ***

Author: Doug Evans <dje@google.com>
Branch: master
Commit: 963843d4d07aef6caa296dacf191f8adc9518596

musl: Move W_STOPCODE to common/gdb_wait.h.

gdb/ChangeLog:

	* common/gdb_wait.h (W_STOPCODE): Define, moved here from
	gdbserver/linux-low.c.
	(WSETSTOP): Simplify.

gdb/gdbserver/ChangeLog:

	* linux-low.c (W_STOPCODE): Moved to common/gdb_wait.h.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Move __SIGRTMIN.
@ 2015-10-26 20:47 sergiodj+buildbot
  2015-10-26 23:28 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-26 20:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 682b25469e66ea45b214e95962671373983c118f ***

Author: Doug Evans <dje@google.com>
Branch: master
Commit: 682b25469e66ea45b214e95962671373983c118f

Move __SIGRTMIN.

gdb/ChangeLog:

	* nat/linux-nat.h (__SIGRTMIN): Move here from gdbserver/linux-low.c.

gdb/gdbserver/ChangeLog:

	* linux-low.c (__SIGRTMIN): Move to nat/linux-nat.h.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] PR python/18938: source -s foo.py with foo.py a symlink to foo.notpy fails
@ 2015-10-26 22:10 sergiodj+buildbot
  2015-10-27  1:38 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-26 22:10 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1a70ae976b673f7762f14734785b34fc5ba92eae ***

Author: Doug Evans <dje@google.com>
Branch: master
Commit: 1a70ae976b673f7762f14734785b34fc5ba92eae

PR python/18938: source -s foo.py with foo.py a symlink to foo.notpy fails

gdb/ChangeLog:

	PR python/18938
	* cli/cli-cmds (source_script_fron_sctream): New arg file_to_open.
	All callers updated.

gdb/testsuite/ChangeLog:

	* gdb.python/python.exp: Add test for symlink from .py file to .notpy
	file.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] PR symtab/17391 gdb internal error: assertion fails in regcache.c:178
@ 2015-10-26 23:16 sergiodj+buildbot
  2015-10-27  3:50 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-26 23:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0fde2c536bc483baa4baa2990ebebfb3a7c00415 ***

Author: Doug Evans <dje@google.com>
Branch: master
Commit: 0fde2c536bc483baa4baa2990ebebfb3a7c00415

PR symtab/17391 gdb internal error: assertion fails in regcache.c:178

gdb/ChangeLog:

	* dwarf2-frame.c (dwarf2_restore_rule): Call dwarf_reg_to_regnum
	instead of gdbarch_dwarf2_reg_to_regnum.
	(dwarf2_frame_cache): Ditto.
	(read_addr_from_reg): Call dwarf_reg_to_regnum_or_error instead of
	gdbarch_dwarf2_reg_to_regnum.
	(get_reg_value): Ditto.
	(dwarf2_fetch_cfa_info): Ditto.
	(dwarf2_frame_prev_register): Ditto.
	* dwarf2loc.c: #include "complaints.h".
	(dwarf_expr_read_addr_from_reg): Call dwarf_reg_to_regnum_or_error
	instead of gdbarch_dwarf2_reg_to_regnum.
	(dwarf_expr_get_reg_value): Ditto.
	(read_pieced_value): Ditto.
	(write_pieced_value): Ditto.
	(dwarf2_evaluate_loc_desc_full): Ditto.
	(dwarf_reg_to_regnum): New function.
	(throw_bad_regnum_error): New function.
	(dwarf_reg_to_regnum_or_error): Renamed from
	dwarf2_reg_to_regnum_or_errorChange to take a ULONGEST regnum.
	All callers updated.  Call throw_bad_regnum_error.
	(locexpr_regname): Improve text of bad register number.
	* dwarf2loc.h (dwarf_reg_to_regnum): Declare.
	(dwarf_reg_to_regnum_or_error): Update prototype.
	* dwarf2expr.c: #include "dwarf2loc.h".
	(dwarf_block_to_sp_offset): Call dwarf_reg_to_regnum instead of
	gdbarch_dwarf2_reg_to_regnum.
	* gdbarch.sh (dwarf2_reg_to_regnum): Add comment.
	* gdbarch.h: Regenerate.
	* amd64-tdep.c (amd64_dwarf_reg_to_regnum): Remove warning for bad
	register.
	* avr-tdep.c (avr_dwarf_reg_to_regnum): Ditto.
	* cris-tdep.c (cris_dwarf2_reg_to_regnum): Ditto.
	* bfin-tdep.c (bfin_reg_to_regnum): Fix error checking.
	* hppa-linux-tdep.c (hppa_dwarf_reg_to_regnum): Improve error checking.
	Remove warning for bad register.
	* hppa-tdep.c (hppa64_dwarf_reg_to_regnum): Ditto.
	* i386-tdep.c (i386_svr4_dwarf_reg_to_regnum): Renamed from
	i386_svr4_reg_to_regnum.  Return -1 for bad registers.
	(i386_svr4_reg_to_regnum): New function.
	(i386_gdbarch_init): Update call to set_gdbarch_dwarf2_reg_to_regnum.
	* microblaze-tdep.c (microblaze_dwarf2_reg_to_regnum): Don't assert
	on bad registers, return -1.
	* msp430-tdep.c (msp430_dwarf2_reg_to_regnum): Improve error checking.
	Remove warning for bad register.
	* nios2-tdep.c: Add static assert for NIOS2_NUM_REGS.
	(nios2_dwarf_reg_to_regnum): Fix off-by-one error.
	Remove warning for bad register.  Return -1 for bad register.
	* rl78-tdep.c (rl78_dwarf_reg_to_regnum): Don't flag an internal error
	for bad register, return -1.
	* rx-tdep.c (rx_dwarf_reg_to_regnum): Ditto.
	* m68k-tdep.c (m68k_dwarf_reg_to_regnum): Fix error result.
	* mep-tdep.c (mep_debug_reg_to_regnum): Ditto.
	* mips-tdep.c (mips_stab_reg_to_regnum): Ditto.
	(mips_dwarf_dwarf2_ecoff_reg_to_regnum): Ditto.
	* mn10300-tdep.c (mn10300_dwarf2_reg_to_regnum): Remove warning
	for bad regs.
	* xtensa-tdep.c (xtensa_reg_to_regnum): Remove internal error for
	bad regs.  Fix error result.
	* stabsread.c (stab_reg_to_regnum): Watch for negative regno.
	(reg_value_complaint): Update complaint text.
	* mdebugread.c (reg_value_complaint): New function.
	(mdebug_reg_to_regnum): Rewrite to watch for bad reg numbers.

gdb/testsuite/ChangeLog:

	* lib/dwarf.exp (_location): Add support for DW_OP_regx.
	* gdb.dwarf2/bad-regnum.c: New file.
	* gdb.dwarf2/bad-regnum.exp: New file.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Check symbol defined by assignment in linker script
@ 2015-10-26 23:44 sergiodj+buildbot
  2015-10-27  6:16 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-26 23:44 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7b7e7f1da28585cfa49cbced50dbbd75a143cd20 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 7b7e7f1da28585cfa49cbced50dbbd75a143cd20

Check symbol defined by assignment in linker script

Symbol symbol defined by an assignment in a linker script has type
bfd_link_hash_new.  elf_i386_convert_load and elf_x86_64_convert_load
should check bfd_link_hash_new to see if a symbol is defined by a linker
script.

bfd/

	PR ld/19175
	* elf32-i386.c (elf_i386_convert_load): Check bfd_link_hash_new
	instead of calling bfd_link_get_defined_symbol.
	* elf64-x86-64.c (elf_x86_64_convert_load): Likewise.  Skip
	relocation overflow for bfd_link_hash_new.
	* linker.c (bfd_link_get_defined_symbol): Removed.
	* bfd-in2.h: Regenerated.

ld/testsuite/

	PR ld/19175
	* ld-i386/i386.exp: Run pr19175.
	* ld-x86-64/x86-64.exp: Likewise.
	* ld-i386/pr19175.d: New file.
	* ld-i386/pr19175.s: Likewise.
	* ld-i386/pr19175.t: Likewise.
	* ld-x86-64/pr19175.d: Likewise.
	* ld-x86-64/pr19175.s: Likewise.
	* ld-x86-64/pr19175.t: Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] stap-probe.c: Add casts
@ 2015-10-27  2:18 sergiodj+buildbot
  2015-10-27 10:55 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-27  2:18 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bf6778dab2b3efc5a0ab01ee41e62e966ef08069 ***

Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: bf6778dab2b3efc5a0ab01ee41e62e966ef08069

stap-probe.c: Add casts

gdb/ChangeLog:

	* stap-probe.c (handle_stap_probe): Add (const char *) casts.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] target.c: Add a cast and change a type
@ 2015-10-27  2:26 sergiodj+buildbot
  2015-10-27 12:38 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-27  2:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d7f3ff3ea7830389f458be7c5eadb5d4a4e0a90b ***

Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: d7f3ff3ea7830389f458be7c5eadb5d4a4e0a90b

target.c: Add a cast and change a type

Fixes some errors in C++ build.

gdb/ChangeLog:

	* target.c (memory_xfer_partial): Change type of buf to gdb_byte
	pointer.
	(simple_search_memory): Cast return of memmem.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix access_to_packed_array.exp typos/errors
@ 2015-10-27  5:19 sergiodj+buildbot
  2015-10-27 14:37 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-27  5:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5e2e7507b4ef8410501452224d98071657ea2d53 ***

Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Branch: master
Commit: 5e2e7507b4ef8410501452224d98071657ea2d53

Fix access_to_packed_array.exp typos/errors

Running ./gdb.ada/access_to_packed_array.exp ...
ERROR: tcl error sourcing ./gdb.ada/access_to_packed_array.exp.
ERROR: extra characters after close-quote
    while executing
"gdb_test "print pack.a" "\\(0 => 1, 2, 3, 4, 5, 6, 7, 8, 9, 10\\)")"
    (file "./gdb.ada/access_to_packed_array.exp" line 29)
    invoked from within
"source ./gdb.ada/access_to_packed_array.exp"
    ("uplevel" body line 1)
    invoked from within
"uplevel #0 source ./gdb.ada/access_to_packed_array.exp"
    invoked from within
"catch "uplevel #0 source $test_file_name""

Unrelated to the typos I have changed the print expectations s/"x"/" = x"/
as for example expectation "3" should not match " = 43".

2015-10-27  Jan Kratochvil  <jan.kratochvil@redhat.com>

	* gdb.ada/access_to_packed_array.exp: Fix typos erroring the testfile.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Add support for 32-bit and 64-bit PowerPC AIX core files.
@ 2015-10-27 10:40 sergiodj+buildbot
  2015-10-27 15:39 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-27 10:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d6867a7559ceb7380fc229f948fd5fd910404643 ***

Author: Sangamesh Mallayya <nickc@redhat.com>
Branch: master
Commit: d6867a7559ceb7380fc229f948fd5fd910404643

Add support for 32-bit and 64-bit PowerPC AIX core files.

	* configure.ac (powerpc64-*-aix[5-9].*): Match powerpc64 running
	aix for core file support.
	* configure: Regenerate.
	* rs6000-core.c: Check for __ld_info64 if compiling 64-bit gdb.
	Added BFD64 check if we are using old core file format for 32-bit gdb.
	Set sizeof CORE_COMMONSZ appropriately in case of either new or
	old core file format.
	(read_hdr): Added BFD64 check for 64-bit support.
	(rs6000coff_core_p): Likewise.
	(rs6000coff_core_file_matches_executable_p): Likewise.
	(rs6000coff_core_file_failing_command): Likewise.
	(rs6000coff_core_file_failing_signal): Likewise.
	Add support for debugging core files generated by binaries in
	Large Memory model.
	(rs6000coff_core_p): If Large Memory Model is used, then the .data
	segment should start from BDATAORG which has been defined in the
	system header files.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] ada-lang.h: Add cast in GROW_VECT
@ 2015-10-27 13:39 sergiodj+buildbot
  2015-10-27 18:47 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-27 13:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a480de357b17b1b2057b8375284079ccafae39db ***

Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: a480de357b17b1b2057b8375284079ccafae39db

ada-lang.h: Add cast in GROW_VECT

The assignment requires a cast in C++.  We only use this macro for
vectors of chars, so adding (char *) diretly will do for now.

gdb/ChangeLog:

	* ada-lang.h (GROW_VECT): Add cast.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix RL78 disassembly so that SP+OFFSET addressing always shows the offset, even when zero.
@ 2015-10-27 14:11 sergiodj+buildbot
  2015-10-27 21:44 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-27 14:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 02f12cd4669463a1b2346145808213adeb303e2d ***

Author: Vinay Kumar <vinay.g@kpit.com>
Branch: master
Commit: 02f12cd4669463a1b2346145808213adeb303e2d

Fix RL78 disassembly so that SP+OFFSET addressing always shows the offset, even when zero.

	PR binutils/19157
opcodes	* rl78-decode.opc: Add 'a' print operator to mov instructions
	using stack pointer plus index addressing.
	* rl78-decode.c: Regenerate.

tests	* gas/rl78: New directory.
	* gas/rl78/rl78.exp: New test driver.
	* gas/rl78/pr19157.s: New test source file.
	* gas/rl78/pr19157.d: New test case.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Add scm_t_dynwind_flags casts
@ 2015-10-27 14:45 sergiodj+buildbot
  2015-10-27 20:48 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-27 14:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c6486df5f1400d90a13df5c6dbd96aeaccf8225b ***

Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: c6486df5f1400d90a13df5c6dbd96aeaccf8225b

Add scm_t_dynwind_flags casts

There is a handful of calls to

  scm_dynwind_begin (0);

where the parameter is an enum, scm_t_dynwind_flags.  In C++, we have no
choice but to add an explicit cast, since there is no enum value that
represents 0 (no flags set).

gdb/ChangeLog:

	* guile/scm-breakpoint.c (gdbscm_set_breakpoint_stop_x): Add
	scm_t_dynwind_flags casts.
	* guile/scm-cmd.c (gdbscm_parse_command_name): Likewise.
	* guile/scm-ports.c (gdbscm_open_memory): Likewise.
	* guile/scm-value.c (gdbscm_value_to_string): Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Display system registers by their names when disassembling RL78 instructions.
@ 2015-10-27 15:01 sergiodj+buildbot
  2015-10-27 22:48 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-27 15:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4666280441d1a8d3479d45f1ec5b67cf83d58f35 ***

Author: Vinay Kumar <vinay.g@kpit.com>
Branch: master
Commit: 4666280441d1a8d3479d45f1ec5b67cf83d58f35

Display system registers by their names when disassembling RL78 instructions.

	PR binutils/19158
opcodes	* rl78-decode.opc: Add 's' print operator to instructions that
	access system registers.
	* rl78-decode.c: Regenerate.
	* rl78-dis.c (print_insn_rl78_common): Decode all system
	registers.

tests	* gas/rl78/pr19158.s: New test source file.
	* gas/rl78/pr19158.d: New test case.
	* gas/rl78/rl78.exp: Run the new test.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] ctf.c: Fix int/enum implicit cast
@ 2015-10-27 15:06 sergiodj+buildbot
  2015-10-27 23:45 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-27 15:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e0d13cbd4bcec3e8136925a3a07f85e58187da06 ***

Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: e0d13cbd4bcec3e8136925a3a07f85e58187da06

ctf.c: Fix int/enum implicit cast

This patch was taken directly from Pedro's branch.

Right now, SET_INT32_FIELD is used to set enum fields.  This works in C,
but not C++.  Therefore, define the new SET_ENUM_FIELD, which casts the
value to the right enum type.

gdb/ChangeLog:

	* ctf.c (SET_ENUM_FIELD): New macro.
	(ctf_read_status): Use it.
	(ctf_read_tp): Use it.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix RL78 disassembly of DE+offset addressing to always show the offset, even when zero.
@ 2015-10-27 15:37 sergiodj+buildbot
  2015-10-28  2:57 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-27 15:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c2f2875869a3e427435ea04bcd416ee2f99e7ee9 ***

Author: Vinay Kumar <vinay.g@kpit.com>
Branch: master
Commit: c2f2875869a3e427435ea04bcd416ee2f99e7ee9

Fix RL78 disassembly of DE+offset addressing to always show the offset, even when zero.

	PR binutils/19159
opcodes	* rl78-decode.opc (MOV): Added offset to DE register in index
	addressing mode.
	* rl78-decode.c: Regenerate.

test	* gas/rl78/pr19159.s: New test source file.
	* gas/rl78/pr19159.d: New test case.
	* gas/rl78/rl78.exp: Run the new test.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] source.c:openp: save/restore errno
@ 2015-10-27 17:03 sergiodj+buildbot
  2015-10-28  5:31 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-27 17:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 79b289e2d8083691ccb2c943d4502e1af54e81e2 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 79b289e2d8083691ccb2c943d4502e1af54e81e2

source.c:openp: save/restore errno

openp's return is documented as:

~~~
   If a file is found, return the descriptor.
   Otherwise, return -1, with errno set for the last name we tried to open.  */
~~~

By inspection, I noticed that there are function calls after the ones
that first set errno, and those may clobber errno.  It's safer to save
errno when see an open fail, and restore it on exit.

Tested on x86_64 Fedora 20.

gdb/ChangeLog:
2015-10-27  Pedro Alves  <palves@redhat.com>

	* source.c (openp): New local 'last_errno'.  Use it to
	save/restore errno.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
[parent not found: <c5192092506e52a5f075b137a36933e42db64563@gdb-build>]
[parent not found: <d09f2c3fc15dd4491e9cfa455191045c0729a3c3@gdb-build>]
[parent not found: <b80c3053162ec5533e120ee4e4ed30296d4c5fb2@gdb-build>]
* [binutils-gdb] Fix errors in the gas testsuite for the ARC target.
@ 2015-10-28 13:58 sergiodj+buildbot
  2015-10-28 14:32 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-28 13:58 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6f4b1afcdc8317280669d020765b8215110c4584 ***

Author: Cupertino Miranda <cmiranda@synopsys.com>
Branch: master
Commit: 6f4b1afcdc8317280669d020765b8215110c4584

Fix errors in the gas testsuite for the ARC target.

bfd	* reloc.c (BFD_RELOC_ARC_32_PCREL): New entry.
	(ARC_TLS_DTPOFF): Arrange it in order.
	* elf32-arc.c (arc_elf_howto_ini): Update formula.
	(get_middle_endian_relocation): New function.
	(PDATA): Define.
	* bfd-in2.h: Regenerate.
	* libbfd.h: Likewise.

elf	* arc-reloc.def (ARC_32_PCREL): New definition.

gas	* config/tc-arc.c (tokenize_arguments): Avoid creating unused
	symbols when parsing relocation types.
	(md_apply_fix): Handle TLS relocations. Fix BFD_RELOC_ARC_32_PCREL
	relocation.
	(arc_check_reloc): Emit BFD_RELOC_ARC_32_PCREL relocation.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix recent STM324LXX patch to compile on 32-bit hosts.
@ 2015-10-28 14:07 sergiodj+buildbot
  2015-10-28 15:28 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-28 14:07 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 82188b295de579bee5f68de9f4d76ce4a3d41aa9 ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: 82188b295de579bee5f68de9f4d76ce4a3d41aa9

Fix recent STM324LXX patch to compile on 32-bit hosts.

	* elf32-arm.c (create_instruction_branch_absolute): Replace
	pointer parameters with a simple integer parameter.
	(stm32l4xx_create_replacing_stub_ldmia): Update calls to
	create_instruction_branch_absolute.
	(stm32l4xx_create_replacing_stub_ldmdb): Likewise.
	(stm32l4xx_create_replacing_stub_vldm): Likewise.
	(elf32_arm_write_section): Use pointer type for veneer addresses.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Pass noaliases_p to aarch64_decode_insn
@ 2015-10-28 14:49 sergiodj+buildbot
  2015-10-28 16:31 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-28 14:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 43cdf5aeb8ae6ac2ec3bdbf636cbb2731ccbbb2a ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 43cdf5aeb8ae6ac2ec3bdbf636cbb2731ccbbb2a

Pass noaliases_p to aarch64_decode_insn

Nowadays aarch64_decode_insn is a public interface used by both
opcodes and gdb.  However, its behaviour relies on a global variable
no_aliases, which isn't a good practise.  On the other hand, In default,
no_aliases is zero, but in GDB, we do want no alias when decoding
instructions for prologue analysis (patches to be posted), so that we
can handle both instructions "add" and "mov" (an alias of "add") as
"add".  The code in GDB can be simplified.

This patch adds a new argument in aarch64_decode_insn, and pass no_aliases
to it.  In GDB side, always pass 1 to it.

include/opcode:

2015-10-28  Yao Qi  <yao.qi@linaro.org>

	* aarch64.h (aarch64_decode_insn): Update declaration.

opcodes:

2015-10-28  Yao Qi  <yao.qi@linaro.org>

	* aarch64-dis.c	(aarch64_decode_insn): Add one argument
	noaliases_p.  Update comments.  Pass noaliases_p rather than
	no_aliases to aarch64_opcode_decode.
	(print_insn_aarch64_word): Pass no_aliases to
	aarch64_decode_insn.

gdb:

2015-10-28  Yao Qi  <yao.qi@linaro.org>

	* aarch64-tdep.c (aarch64_software_single_step): Pass 1 to
	aarch64_decode_insn.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] gdbserver: enum gdb_signal casts
@ 2015-10-29 14:16 sergiodj+buildbot
  2015-10-29 18:36 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-29 14:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e053fbc44f32c12a67f4bcd9f01142b4e043496c ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: e053fbc44f32c12a67f4bcd9f01142b4e043496c

gdbserver: enum gdb_signal casts

This is code parsing RSP signal numbers, checking whether the numbers
are indeed valid/known GDB signals, and then converting to host signal
numbers.  I considered adding temporary enum gdb_signal variables
instead, but didn't really like the result.

gdb/gdbserver/ChangeLog:
2015-10-29  Pedro Alves  <palves@redhat.com>

	* server.c (handle_v_cont, process_serial_event): Add enum
	gdb_signal casts to signal parsing code.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] gdbserver/mem-break.c: Add cast
@ 2015-10-29 14:31 sergiodj+buildbot
  2015-10-29 20:33 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-29 14:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d2412fa5d0051f7eb7b13aaf98173b5d9a55d132 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: d2412fa5d0051f7eb7b13aaf98173b5d9a55d132

gdbserver/mem-break.c: Add cast

... for C++.

Fixes:

 gdb/gdbserver/mem-break.c:204:28: error: invalid conversion from 'int' to 'bkpt_type' [-fpermissive]

gdb/gdbserver/ChangeLog:
2015-10-29  Pedro Alves  <palves@redhat.com>

	* mem-break.c (Z_packet_to_bkpt_type): Add cast.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
[parent not found: <e3bdafe2bac1672da335fde734b337c5504e5437@gdb-build>]
* [binutils-gdb] gdbserver/Linux: Introduce NULL_REGSET
@ 2015-10-29 14:48 sergiodj+buildbot
  2015-10-29 16:45 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-29 14:48 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 50bc912a2074c974c9c5074e674e9149a33b64c2 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 50bc912a2074c974c9c5074e674e9149a33b64c2

gdbserver/Linux: Introduce NULL_REGSET

Fixes errors like:

 src/gdb/gdbserver/linux-x86-low.c:477:1: error: invalid conversion from 'int' to 'regset_type' [-fpermissive]

gdb/gdbserver/ChangeLog:
2015-10-29  Pedro Alves  <palves@redhat.com>

	* linux-low.h (NULL_REGSET): Define.
	* linux-aarch64-low.c (aarch64_regsets): Use NULL_REGSET.
	* linux-arm-low.c (arm_regsets): Likewise.
	* linux-crisv32-low.c (cris_regsets): Likewise.
	* linux-m68k-low.c (m68k_regsets): Likewise.
	* linux-mips-low.c (mips_regsets): Likewise.
	* linux-nios2-low.c (nios2_regsets): Likewise.
	* linux-ppc-low.c (ppc_regsets): Likewise.
	* linux-s390-low.c (s390_regsets): Likewise.
	* linux-sh-low.c (sh_regsets): Likewise.
	* linux-sparc-low.c (sparc_regsets): Likewise.
	* linux-tic6x-low.c (tic6x_regsets): Likewise.
	* linux-tile-low.c (tile_regsets): Likewise.
	* linux-x86-low.c (x86_regsets): Likewise.
	* linux-xtensa-low.c (xtensa_regsets): Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] 2015-10-29  Catherine Moore  <clm@codesourcery.com>
@ 2015-10-29 14:54 sergiodj+buildbot
  2015-10-29 23:34 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-29 14:54 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ca9584fb9b4a54232d2538de9f75b1916bda00fe ***

Author: Catherine Moore <clm@codesourcery.com>
Branch: master
Commit: ca9584fb9b4a54232d2538de9f75b1916bda00fe

2015-10-29  Catherine Moore  <clm@codesourcery.com>

    	bfd/
    	* elfxx-mips.c (mips_elf_check_mips16_stubs): Set a stub's output
    	section to bfd_abs_section_ptr if the stub is discarded.

    	ld/testsuite/
    	* ld-mips-elf/mips16-fp-stub-1.s: New.
    	* ld-mips-elf/mips16-fp-stub-2.s: New.
    	* ld-mips-elf/mips16-fp-stub.d: New.
    	* ld-mips-elf/mips-elf.exp: Run new tests.
    	* ld-mips-elf/mips16-intermix.d: Update expected output.

	https://sourceware.org/ml/binutils/2015-10/msg00137.html


^ permalink raw reply	[flat|nested] 2113+ messages in thread
[parent not found: <44a8b4df1d6f5b8096f01787751fd51c42e78fc6@gdb-build>]
* [binutils-gdb] Add support for AArch64 CloudABI binaries.
@ 2015-10-29 16:32 sergiodj+buildbot
  2015-10-29 22:33 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-29 16:32 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a75cf613fd7d0a48d526a996ff5c250c599d3ab7 ***

Author: Ed Schouten <ed@nuxi.nl>
Branch: master
Commit: a75cf613fd7d0a48d526a996ff5c250c599d3ab7

Add support for AArch64 CloudABI binaries.

ld	* Makefile.am (ALL_64_EMULATION_SOURCES): Add support for
	CloudABI on aarch64. For this target we have to make sure we use
	ELFOSABI_CLOUDABI instead of ELFOSABI_NONE.
	* configure.tgt (targ_emul): Likewise.
	* emulparams/aarch64cloudabi.sh: New file.
	* emulparams/aarch64cloudabib.sh: New file.
	* Makefile.in: Regenerate.

bfd	* config.bfd (targ_defvec): Add support for CloudABI on aarch64.
	For this target we have to make sure we use ELFOSABI_CLOUDABI
	instead of ELFOSABI_NONE.
	* configure.ac (tb): Likewise.
	* elfnn-aarch64.c: Likewise.
	* targets.c (_bfd_target_vector): Likewise.
	* configure: Regenerate.

gas	* config/tc-aarch64.c (elf64_aarch64_target_format): Select the
	cloudabi format if the TARGET_OS is cloudabi.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
[parent not found: <add67df84c59a6c28111d65e8d0a7e6b4994cdb1@gdb-build>]
* [binutils-gdb] Disable paging when run by Emacs 25.1 and later.
@ 2015-10-29 17:42 sergiodj+buildbot
  2015-10-30  2:37 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-29 17:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e681cf3fe50d3c8d17dabde079bbd949a59ef53a ***

Author: Eli Zaretskii <eliz@gnu.org>
Branch: master
Commit: e681cf3fe50d3c8d17dabde079bbd949a59ef53a

Disable paging when run by Emacs 25.1 and later.

gdb/ChangeLog:

	* utils.c (init_page_info): Disable paging if INSIDE_EMACS is set
	in the environment.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] dwarf2read.c: Add cast
@ 2015-10-29 18:06 sergiodj+buildbot
  2015-10-30  7:14 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-29 18:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b40699581c0d390e653f36a5bba99f13cf9763a0 ***

Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: b40699581c0d390e653f36a5bba99f13cf9763a0

dwarf2read.c: Add cast

There is no enum value representing 0.  It seems like the value of the
name field is irrelevant here.

gdb/ChangeLog:

	* dwarf2read.c (partial_die_full_name): Add cast.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] gdbserver/server.c: Cast return value of memmem
@ 2015-10-29 18:21 sergiodj+buildbot
  2015-10-30  9:13 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-29 18:21 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d6f85c8421acaf09fa5a25ae2621819889d54038 ***

Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: d6f85c8421acaf09fa5a25ae2621819889d54038

gdbserver/server.c: Cast return value of memmem

gdb/gdbserver/ChangeLog:

	* server.c (handle_search_memory_1): Cast return value of
	memmem.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] gdbserver: Move pointer dereference to after assert checks.
@ 2015-10-29 18:59 sergiodj+buildbot
  2015-10-30 13:17 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-29 18:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 692916105d13be0ca5588bf8aa94b8ba04239269 ***

Author: Henrik Wallin <henrik.wallin@windriver.com>
Branch: master
Commit: 692916105d13be0ca5588bf8aa94b8ba04239269

gdbserver: Move pointer dereference to after assert checks.

gdb/gdbserver/ChangeLog:

	* linux-arm-low.c (arm_new_thread): Move pointer dereference
	to after assert checks.

Signed-off-by: Henrik Wallin <henrik.wallin@windriver.com>


^ permalink raw reply	[flat|nested] 2113+ messages in thread
[parent not found: <7535d5edeaa5cfa5ba369e8d3ffb47972483394a@gdb-build>]
[parent not found: <f98cd059076c64cdb94b9743c544458b2b91716c@gdb-build>]
[parent not found: <d2242e347a25dc15fbf7286975e3baba143deea9@gdb-build>]
* [binutils-gdb] Updated (simplified) Chinese translations for ld, bfd, binutils and gold.
@ 2015-10-30 12:57 sergiodj+buildbot
  2015-10-30 13:26 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-30 12:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 26f187cd169e484ac2b8ac3f9ece55a597caadf9 ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: 26f187cd169e484ac2b8ac3f9ece55a597caadf9

Updated (simplified) Chinese translations for ld, bfd, binutils and gold.

	* po/zh_CN.po: Updated (simplified) Chinese translation.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
[parent not found: <b42945fd28b881e23016ce2efaf5fd83d5038f34@gdb-build>]
[parent not found: <452b4ba5f70df5b8b2332bcadd46eec95273b50b@gdb-build>]
[parent not found: <aefb52a69351517dbcfaafca1d21e5431d4119d1@gdb-build>]
[parent not found: <7571f7f297c8d8b4fb4657f84437b1d156957e16@gdb-build>]
[parent not found: <72aded8673d6cb2d0e33696e010a778e9bbfa817@gdb-build>]
* [binutils-gdb] Don't displaced step when there's a breakpoint in the scratch pad range
@ 2015-10-30 22:03 sergiodj+buildbot
  2015-10-31 14:29 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-10-30 22:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d35ae83384324ec7a03a56600174b5e925510b74 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: d35ae83384324ec7a03a56600174b5e925510b74

Don't displaced step when there's a breakpoint in the scratch pad range

Assuming displaced stepping is enabled, and a breakpoint is set in the
memory region of the scratch pad, things break.  One of two cases can
happen:

#1 - The breakpoint wasn't inserted yet (all threads were stopped), so
     after setting up the displaced stepping scratch pad with the
     adjusted copy of the instruction we're trying to single-step, we
     insert the breakpoint, which corrupts the scratch pad, and the
     inferior executes the wrong instruction.  (Example below.)
     This is clearly unacceptable.

#2 - The breakpoint was already inserted, so setting up the displaced
     stepping scratch pad overwrites the breakpoint.  This is OK in
     the sense that we already assume that no thread is going to
     executes the code in the scratch pad range (after initial
     startup) anyway.

This commit addresses both cases by simply punting on displaced
stepping if we have a breakpoint in the scratch pad range.

The #1 case above explains a few regressions exposed by the AS/NS
series on x86:

 Running ./gdb.dwarf2/callframecfa.exp ...
 FAIL: gdb.dwarf2/callframecfa.exp: set display for call-frame-cfa
 FAIL: gdb.dwarf2/callframecfa.exp: step 1 for call-frame-cfa
 FAIL: gdb.dwarf2/callframecfa.exp: step 2 for call-frame-cfa
 FAIL: gdb.dwarf2/callframecfa.exp: step 3 for call-frame-cfa
 FAIL: gdb.dwarf2/callframecfa.exp: step 4 for call-frame-cfa
 Running ./gdb.dwarf2/typeddwarf.exp ...
 FAIL: gdb.dwarf2/typeddwarf.exp: continue to breakpoint: continue to typeddwarf.c:53
 FAIL: gdb.dwarf2/typeddwarf.exp: check value of x at typeddwarf.c:53
 FAIL: gdb.dwarf2/typeddwarf.exp: check value of y at typeddwarf.c:53
 FAIL: gdb.dwarf2/typeddwarf.exp: check value of z at typeddwarf.c:53
 FAIL: gdb.dwarf2/typeddwarf.exp: continue to breakpoint: continue to typeddwarf.c:73
 FAIL: gdb.dwarf2/typeddwarf.exp: check value of w at typeddwarf.c:73
 FAIL: gdb.dwarf2/typeddwarf.exp: check value of x at typeddwarf.c:73
 FAIL: gdb.dwarf2/typeddwarf.exp: check value of y at typeddwarf.c:73
 FAIL: gdb.dwarf2/typeddwarf.exp: check value of z at typeddwarf.c:73

Enabling "maint set target-non-stop on" implies displaced stepping
enabled as well, and it's the latter that's to blame here.  We can see
the same failures with "maint set target-non-stop off + set displaced
on".

Diffing (good/bad) gdb.log for callframecfa.exp shows:

 @@ -99,29 +99,29 @@ Breakpoint 2 at 0x80481b0: file q.c, lin
  continue
  Continuing.

 -Breakpoint 2, func (arg=77) at q.c:2
 +Breakpoint 2, func (arg=52301) at q.c:2
  2      in q.c
  (gdb) PASS: gdb.dwarf2/callframecfa.exp: continue to breakpoint: continue to breakpoint for call-frame-cfa
  display arg
 -1: arg = 77
 -(gdb) PASS: gdb.dwarf2/callframecfa.exp: set display for call-frame-cfa
 +1: arg = 52301
 +(gdb) FAIL: gdb.dwarf2/callframecfa.exp: set display for call-frame-cfa

The problem is here, when setting up the func call:

 Breakpoint 1, main (argc=-13345, argv=0x0) at q.c:7
 7       in q.c

 (gdb) disassemble
 Dump of assembler code for function main:
    0x080481bb <+0>:     push   %ebp
    0x080481bc <+1>:     mov    %esp,%ebp
    0x080481be <+3>:     sub    $0x4,%esp
 => 0x080481c1 <+6>:     movl   $0x4d,(%esp)
    0x080481c8 <+13>:    call   0x80481b0 <func>
    0x080481cd <+18>:    leave
    0x080481ce <+19>:    ret
 End of assembler dump.
 (gdb) disassemble /r
 Dump of assembler code for function main:
    0x080481bb <+0>:     55      push   %ebp
    0x080481bc <+1>:     89 e5   mov    %esp,%ebp
    0x080481be <+3>:     83 ec 04        sub    $0x4,%esp
 => 0x080481c1 <+6>:     c7 04 24 4d 00 00 00    movl   $0x4d,(%esp)
    0x080481c8 <+13>:    e8 e3 ff ff ff  call   0x80481b0 <func>
    0x080481cd <+18>:    c9      leave
    0x080481ce <+19>:    c3      ret
 End of assembler dump.

Note the breakpoint at main is set at 0x080481c1.  Right at the
instruction that sets up func's argument.  Executing that instruction
should write 0x4d to the address pointed at by $esp.  However, if we
stepi, the program manages to write 52301/0xcc4d there instead (0xcc
is int3, the x86 breakpoint instruction), because the breakpoint
address is 4 bytes inside the scratch pad location, which is
0x080481bd:

 (gdb) p 0x080481c1 - 0x080481bd
 $1 = 4

IOW, instead of executing:

  "c7 04 24 4d 00 00 00" [ movl $0x4d,(%esp) ]

the inferior executes:

  "c7 04 24 4d cc 00 00" [ movl $0xcc4d,(%esp) ]

gdb/ChangeLog:
2015-10-30  Pedro Alves  <palves@redhat.com>

	* breakpoint.c (breakpoint_in_range_p)
	(breakpoint_location_address_range_overlap): New functions.
	* breakpoint.h (breakpoint_in_range_p): New declaration.
	* infrun.c (displaced_step_prepare_throw): If there's a breakpoint
	in the scratch pad range, don't displaced step.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
[parent not found: <933c5a623f247c63b642988a2984f5ce9b558d27@gdb-build>]
[parent not found: <b80d067ff0a7d2fcca3f8c01abf4b7201e71b8f0@gdb-build>]
[parent not found: <cb658d218b873a69b1f19971695f92d5db17a388@gdb-build>]
[parent not found: <d2de23ad3916c9d6f6102688fdbd5fdc73053c43@gdb-build>]
[parent not found: <ff83a547feacaea9263c04f527aba4faae77035f@gdb-build>]
[parent not found: <c28ebe255ba37f4dcd295cf6a4608424aaeb699f@gdb-build>]
[parent not found: <d9b19c4992e7384f12441bc13c0e22d4054b0487@gdb-build>]
[parent not found: <10268a4c0d64b3892397aeaafbc4b91f6a1e0dc8@gdb-build>]
* [binutils-gdb] Disassemble RX NOP instructions as such.
@ 2015-11-03 18:52 sergiodj+buildbot
  2015-11-03 20:18 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-03 18:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 854eb72b00ba46d65ce36dc3432f01e223ce44cb ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: 854eb72b00ba46d65ce36dc3432f01e223ce44cb

Disassemble RX NOP instructions as such.

opcode	* rx.h (enum RX_Opcode_ID): Add more NOP opcodes.

opcodes	* rx-decode.opc (rx_decode_opcode): Decode extra NOP
	instructions.
	* rx-decode.c: Regenerate.

tests	* gas/rx/max.d: Update expecetd disassembly.
	* gas/rx/nod.d: Likewise.
	* gas/rx/nop.sm: Add tests of more NOP instructions.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] remote-sim.c: Add casts
@ 2015-11-03 19:40 sergiodj+buildbot
  2015-11-04  3:23 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-03 19:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 653090d3219377766f1d4597819fa3c805ce49eb ***

Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: 653090d3219377766f1d4597819fa3c805ce49eb

remote-sim.c: Add casts

Mostly some casts from "generic arg" void* to the actual type.

There are two (enum gdb_signal) casts.  I tried to see if it would have
been better to change the type of sigrc, but it has a double role, as an
enum and as an integer, so I left it as is.

gdb/ChangeLog:

	* remote-sim.c (check_for_duplicate_sim_descriptor): Add casts.
	(get_sim_inferior_data): Likewise.
	(sim_inferior_data_cleanup): Likewise.
	(gdbsim_close_inferior): Likewise.
	(gdbsim_resume_inferior): Likewise.
	(gdbsim_wait): Likewise.
	(simulator_command): Likewise.
	(sim_command_completer): Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] linux-ppc-low.c: Add casts
@ 2015-11-03 21:16 sergiodj+buildbot
  2015-11-04  1:30 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-03 21:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2bc84e8a6d94d9d7ead1bc4febf0fb331394406e ***

Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: 2bc84e8a6d94d9d7ead1bc4febf0fb331394406e

linux-ppc-low.c: Add casts

Trivial casts for C++.

gdb/gdbserver/ChangeLog:

	* linux-ppc-low.c (ppc_get_hwcap): Add cast.
	(ppc_fill_vsxregset): Likewise.
	(ppc_store_vsxregset): Likewise.
	(ppc_fill_vrregset): Likewise.
	(ppc_store_vrregset): Likewise.
	(ppc_fill_evrregset): Likewise.
	(ppc_store_evrregset): Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
[parent not found: <7ad8b86c674ed941b354322f608cd964ca0affb2@gdb-build>]
[parent not found: <d5f0636bf6fb6b5e54cd405811cfbfcc98fa667b@gdb-build>]
[parent not found: <f4b0a6714adb7371e3b7a0f47589c3dfd958cd09@gdb-build>]
[parent not found: <04b3479c3f92e102c5a7d1158ab608e0015252c6@gdb-build>]
* [binutils-gdb] disasm: split dump_insns
@ 2015-11-04  8:26 sergiodj+buildbot
  2015-11-04 16:26 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-04  8:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT af70908dc41c8bf21680aeb2f849ce4043b2031a ***

Author: Markus Metzger <markus.t.metzger@intel.com>
Branch: master
Commit: af70908dc41c8bf21680aeb2f849ce4043b2031a

disasm: split dump_insns

Split disasm.c's dump_insn into two parts:

  - print a single instruction
  - loop over the specified address range

The first part will be refined in subsequent patches so it can be reused.

gdb/
	* disasm.c (dump_insns):  Split into this and ...
	(gdb_pretty_print_insn): ... this.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] disasm: add struct disasm_insn to describe to-be-disassembled instruction
@ 2015-11-04  8:34 sergiodj+buildbot
  2015-11-04 17:39 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-04  8:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a50a40267668422e60901cc7fb949050caceb90c ***

Author: Markus Metzger <markus.t.metzger@intel.com>
Branch: master
Commit: a50a40267668422e60901cc7fb949050caceb90c

disasm: add struct disasm_insn to describe to-be-disassembled instruction

The "record instruction-history" command prints for each instruction in
addition to the instruction's disassembly:

  - the instruction number in the recorded execution trace
  - a '?' before the instruction if it was executed speculatively

To allow the "record instruction-history" command to use GDB's disassembly
infrastructure, we extend gdb_pretty_print_insn to optionally print those
additional fields and export the function.

Add a new struct disasm_insn to add additional fields describing the
to-be-disassembled instruction.  The additional fields are:

  number            an optional instruction number, zero if omitted.
  is_speculative    a predicate saying whether the instruction was
                    executed speculatively.

If non-zero, the instruction number is printed first.  It will also appear
as a new optional field "insn-number" in MI.  The field will be present if
insn_num is non-zero.

If is_speculative is set, speculative execution will be indicated by a "?"
following the new instruction number field.  Unless the PC is omitted, it
will overwrite the first byte of the PC prefix.  It will appear as a new
optional field "is-speculative" in MI.  The field will contain "?" and will
be present if is_speculative is set.

The speculative execution indication is guarded by a new flag
DISASSEMBLY_SPECULATION.

Replace the PC parameter of gdb_pretty_print_insn with a pointer to the above
struct.  GDB's "disassemble" command does not use the new fields.

gdb/
	* disasm.h (DISASSEMBLY_SPECULATION): New.
	(struct disasm_insn): New.
	(gdb_pretty_print_insn): New.
	* disasm.c (gdb_pretty_print_insn): Replace parameter PC with INSN.
	Update users.  Print instruction number and indicate speculative
	execution, if requested.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] btrace: change record instruction-history /m
@ 2015-11-04  8:43 sergiodj+buildbot
  2015-11-04 18:29 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-04  8:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f94cc8975cfcf8625833eba0c0077bb878f0cbaa ***

Author: Markus Metzger <markus.t.metzger@intel.com>
Branch: master
Commit: f94cc8975cfcf8625833eba0c0077bb878f0cbaa

btrace: change record instruction-history /m

The /m modifier interleaves source lines with the disassembly of recorded
instructions.  This calls disasm.c's gdb_disassembly once for each recorded
instruction to be printed.

This doesn't really work because gdb_disassembly may choose not to print
anything in some situations.  And if it does print something, the output
interferes with btrace_insn_history's output around it.

It further results in a separate asm_insns list for each instruction in MI.
Even though there is no MI support for target record, yet, we fix this obvious
issue.

Change record instruction-history /m to use the new gdb_pretty_print_insn
function for printing a single instruction and interleave source lines as
appropriate.

We cannot reuse the new disasm.c do_mixed_source_and_assembly function without
significant changes to it.

gdb/
	* record-btrace.c (struct btrace_line_range): New.
	(btrace_mk_line_range, btrace_line_range_add)
	(btrace_line_range_is_empty, btrace_line_range_contains_range)
	(btrace_find_line_range, btrace_print_lines): New.
	(btrace_insn_history): Add source interleaving algorithm.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] btrace: add instruction-history /s and fix documentation
@ 2015-11-04  8:49 sergiodj+buildbot
  2015-11-04 19:31 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-04  8:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0c532a298058669a72061ad94ba9e24170ae91ae ***

Author: Markus Metzger <markus.t.metzger@intel.com>
Branch: master
Commit: 0c532a298058669a72061ad94ba9e24170ae91ae

btrace: add instruction-history /s and fix documentation

Add support for the /s modifier of the "record instruction-history" command.  It
behaves exactly like /m and prints disassembled instructions in the order in
which they were recorded with interleaved sources.  We accept /s in addition
to /m to align with the "disassemble" command.

The "record instruction-history" modifiers were not documented.  Document
all of them.

gdb/
	* record.c (get_insn_history_modifiers): Set DISASSEMBLY_SOURCE
	instead of DISASSEMBLY_SOURCE_DEPRECATED.  Also accept /s.
	(_initialize_record): Document the /s modifier.
	* NEWS: Announce record instruction-history's new /s modifier.

doc/
	* gdb.texinfo (Process Record and Replay): Document "record
	instruction-history" modifiers.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
[parent not found: <04248ead1f57204119180022580626e31c165f60@gdb-build>]
* [binutils-gdb] Fix non stopping breakpoint on newer compilers.
@ 2015-11-04 10:35 sergiodj+buildbot
  2015-11-04 22:49 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-04 10:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 14cb1c0b38b120cf5325d9538cce1a0347e2b626 ***

Author: Walfred Tedeschi <walfred.tedeschi@intel.com>
Branch: master
Commit: 14cb1c0b38b120cf5325d9538cce1a0347e2b626

Fix non stopping breakpoint on newer compilers.

The breakpoint presented in the return statement was not activated while
compiling the test with gcc 4.9.2.  Added a dummy statement to allow the
breakpoint again.

2015-10-14  Walfred Tedeschi  <walfred.tedeschi@intel.com>

gdb/testsuite:

	* i386-mpx-map.c (foo): Add dummy statement to trigger breakpoint.

Change-Id: I5293ca1c7f82a631e1e41cb650c30dd2d09ef3c2
Signed-off-by: Walfred Tedeschi <walfred.tedeschi@intel.com>


^ permalink raw reply	[flat|nested] 2113+ messages in thread
[parent not found: <f844cf0ec3887110375e9c1d4c48a68cb6a8b141@gdb-build>]
[parent not found: <cbec665beba8acf6393a8c93312bdd3a03a0846c@gdb-build>]
* [binutils-gdb] Fortran: allocate()d memory is uninitialized
@ 2015-11-04 15:04 sergiodj+buildbot
  2015-11-05  3:56 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-04 15:04 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6f2f1a3a706e56b3fddd7ab1fc9a313343c85d4a ***

Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Branch: master
Commit: 6f2f1a3a706e56b3fddd7ab1fc9a313343c85d4a

Fortran: allocate()d memory is uninitialized

  allocate (vla1 (5))         ! vla1-not-allocated
  l = allocated(vla1)         ! vla1-allocated     <------------------

Expecting: ^(510-data-evaluate-expression vla1[^M
]+)?(510\^done,value="\(0, 0, 0, 0, 0\)"[^M
]+[(]gdb[)] ^M
[ ]*)
510-data-evaluate-expression vla1^M
510^done,value="(1.82987403e-09, 7.8472714e-44, 1.82987403e-09, 7.8472714e-44, 2.67929926e+20)"^M
(gdb) ^M
FAIL: gdb.mi/mi-vla-fortran.exp: evaluate allocated vla

gcc-4.9.2-6.fc21.x86_64

I think some older gfortran did initialize allocated memory but that is an
unspecified behavior.  I haven't found any initialization mentioned
in Fortran 90 standard (draft) and it is also clearly stated here:
        https://software.intel.com/en-us/forums/intel-fortran-compiler-for-linux-and-mac-os-x/topic/268786
        Initialization to 0 of allocated arrays (of integers) is an
        implementation issue. i.e. do not rely on it.

Joel Brobecker wrote:
I am wondering if it might be better to just relax instead the regexp to allow
any number rather than just remove the test altogether. The test allows us to
verify that, as soon as we're past the "allocate" call, we no longer say "not
allocated".

gdb/testsuite/ChangeLog
2015-11-03  Jan Kratochvil  <jan.kratochvil@redhat.com>
	    Joel Brobecker  <brobecker@adacore.com>

	* gdb.mi/mi-vla-fortran.exp (evaluate allocated vla): Permit any data.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
[parent not found: <1c215b97f9a64d6ba9821e8a0cf0f44526f29d78@gdb-build>]
[parent not found: <394816ee10a85e3e0fa7c9b0a4ca29e7e160e63c@gdb-build>]
[parent not found: <566c56c91116321f48573a0a4274cc5244330490@gdb-build>]
[parent not found: <6df55226405d626059f81bec3078a70db41dec9f@gdb-build>]
* [binutils-gdb] Use aarch64_decode_insn in aarch64_displaced_step_copy_insn
@ 2015-11-05 10:06 sergiodj+buildbot
  2015-11-05 12:34 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-05 10:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c86a40c6c2902b73ec6f601176820c760524afd2 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: c86a40c6c2902b73ec6f601176820c760524afd2

Use aarch64_decode_insn in aarch64_displaced_step_copy_insn

gdb:

2015-11-05  Yao Qi  <yao.qi@linaro.org>

	* aarch64-tdep.c (aarch64_displaced_step_copy_insn): Call
	aarch64_decode_insn and decode instruction by aarch64_inst.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] gdb.dwarf2: Define and use gdb_target_symbol for symbol prefixes
@ 2015-11-05 22:32 sergiodj+buildbot
  2015-11-05 23:09 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-05 22:32 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2223449a47a8908db2a1992379f54294128a7ee4 ***

Author: Kevin Buettner <kevinb@redhat.com>
Branch: master
Commit: 2223449a47a8908db2a1992379f54294128a7ee4

gdb.dwarf2: Define and use gdb_target_symbol for symbol prefixes

Some of the tests in gdb.dwarf2 which use Dwarf::assemble refer to
(minimal/linker) symbols created in the course of building a small
test program.  Some targets use a prefix such as underscore ("_") on
these symbols.  Many of the tests in gdb.dwarf2 do not take this into
account.  As a consequence, these tests fail to build, resulting
either in failures or untested testcases.

Here is an example from gdb.dwarf2/dw2-regno-invalid.exp:

    Dwarf::assemble $asm_file {
        cu {} {
            compile_unit {
                {low_pc main DW_FORM_addr}
                {high_pc main+0x10000 DW_FORM_addr}
            } {
            ...
            }

For targets which require an underscore prefix on linker symbols,
the two occurrences of "main" would have to have a prepended underscore,
i.e. _main instead of main.

For the above case, a call to the new proc gdb_target_symbol is used
prepend the correct prefix to the symbol.  I.e. the above code is
rewritten (as shown in the patch) as follows:

    Dwarf::assemble $asm_file {
        cu {} {
            compile_unit {
                {low_pc [gdb_target_symbol main] DW_FORM_addr}
                {high_pc [gdb_target_symbol main]+0x10000 DW_FORM_addr}
            } {
            ...
            }

I also found it necessary to make an adjustment to lib/dwarf.exp so that
expressions of more than just one list element can be used in DW_TAG_...
constructs.  Both atomic-type.exp and dw2-bad-mips-linkage-name.exp require
this new functionality.

gdb/testsuite/ChangeLog:

	* lib/gdb.exp (gdb_target_symbol_prefix, gdb_target_symbol):
	New procs.
	* lib/dwarf.exp (_handle_DW_TAG): Handle attribute values,
	representing expressions, of more than one list element.
	* gdb.dwarf2/atomic-type.exp (Dwarf::assemble): Use gdb_target_symbol
	to prepend linker symbol prefix to f.
	* gdb.dwarf2/data-loc.exp (Dwarf::assemble): Likewise, for
	table_1 and table_2.
	* gdb.dwarf2/dw2-bad-mips-linkage-name.exp (Dwarf::assemble):
	Likewise, for f and g.
	* gdb.dwarf2/dw2-ifort-parameter.exp (Dwarf::assemble): Likewise,
	for ptr.
	* gdb.dwarf2/dw2-regno-invalid.exp (Dwarf::assemble): Likewise,
	for main.
	* gdb.dwarf2/dynarr-ptr.exp (Dwarf::assemble): Likewise, for
	table_1_ptr and table_2_ptr.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] testsuite: Define and use gdb_target_symbol_prefix_flags_asm.
@ 2015-11-07 18:17 sergiodj+buildbot
  2015-11-07 18:49 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-07 18:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f01dcfd9a7954462ea08d2c7b24dad0ca5e07db2 ***

Author: Kevin Buettner <kevinb@redhat.com>
Branch: master
Commit: f01dcfd9a7954462ea08d2c7b24dad0ca5e07db2

testsuite: Define and use gdb_target_symbol_prefix_flags_asm.

Some of the source code for the test cases in the GDB testsuite
reside in .S files containing assembly code.  These files typically
define a symbol - such as main - which may, depending on the target,
require a prefix such as underscore.

For example, gdb.dwarf2/dw-compdir-oldgcc.S defines the symbol main:

main:	.globl main

Some targets, such as rx-elf, require main to have an underscore
prefix.  (If it doesn't, a linker error results due to not being able
to find _main required by crt0.o.) So, instead, the above should look
like this for rx-elf and other targets with this same requirement:

_main:	.globl	_main

This patch defines a new tcl proc in lib/gdb named
gdb_target_symbol_prefix_flags_asm.  This proc returns a string
which will - assuming everything else is wired up correctly - cause
-DSYMBOL_PREFIX=_ to be passed on the command line to the compiler.

The test cases are augmented with a macro definition for SYMBOL
as follows:

    #define CONCAT1(a, b) CONCAT2(a, b)
    #define CONCAT2(a, b) a ## b

    #ifdef SYMBOL_PREFIX
    # define SYMBOL(str)     CONCAT1(SYMBOL_PREFIX, str)
    #else
    # define SYMBOL(str)     str
    #endif

Symbols, such as main shown in the example earlier are then wrapped
with SYMBOL like this:

SYMBOL(main):	.globl SYMBOL(main)

The net effect will be to add a prefix for those targets which need
it and add no prefix for those targets which do not.

It should be noted that there was already a proc in lib/gdb.exp
called gdb_target_symbol_prefix_flags.  It still exists, but has
been significantly rewritten.  (There is only one small difference
between the two versions.)

That proc used to explicitly list targets which were known to
require an underscore prefix.  This is no longer done; the recently
added proc, gdb_target_symbol_prefix, is now invoked to dynamically
discover whether or not a prefix is required for that particular
target.

The difference between gdb_target_symbol_prefix_flags_asm
and gdb_target_symbol_prefix_flags is that the former returns
a bare prefix while the latter returns the prefix enclosed in
double quotes.  I.e. assuming that the discovered prefix is
underscore, gdb_target_symbol_prefix_flags_asm returns:

    additional_flags=-DSYMBOL_PREFIX=_

while gdb_target_symbol_prefix_flags returns:

    additional_flags=-DSYMBOL_PREFIX="_"

The double-quoted version is not suitable for using with .S files
containing assembly code; there is no way to strip the double quotes
using C preprocessor constructs.

It would be possible to use the bare (non double quoted) version in
C source code.  However, the supporting macros become more complicated
and therefore more difficult to maintain.

gdb/testsuite/ChangeLog:

	* lib/gdb (gdb_target_symbol_prefix_flags_asm): New proc.
	(gdb_target_symbol_prefix_flags): Define in terms of _asm
	version.
	* gdb.arch/i386-float.exp, gdb.arch/i386-permbkpt.exp,
	gdb.dwarf2/dw2-canonicalize-type.exp,
	gdb.dwarf2/dw2-compdir-oldgcc.exp, gdb.dwarf2/dw2-minsym-in-cu.exp,
	gdb.dwarf2/dw2-op-stack-value.exp, gdb.dwarf2/dw2-unresolved.exp,
	gdb.dwarf2/fission-reread.exp, gdb.dwarf2/pr13961.exp: Use flags
	provided by gdb_target_symbol_prefix_flags_asm.
	* gdb.dwarf2/dw2-canonicalize-type.S, gdb.dwarf2/dw2-compdir-oldgcc.S,
	testsuite/gdb.dwarf2/dw2-minsym-in-cu.S,
	testsuite/gdb.dwarf2/dw2-unresolved-main.c,
	testsuite/gdb.dwarf2/dw2-unresolved.S, gdb.dwarf2/fission-reread.S,
	gdb.dwarf2/pr13961.S: Define and use SYMBOL macro (and supporting
	macros where needed).  Use this macro for symbols which require
	the prefix provided by SYMBOL_PREFIX.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] gdb.dwarf2: Don't hardcode certain constants in Dwarf::assemble constructs
@ 2015-11-07 18:22 sergiodj+buildbot
  2015-11-07 19:47 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-07 18:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c6f0b406f56ac5232d08cbd88c0bddfb2f640e90 ***

Author: Kevin Buettner <kevinb@redhat.com>
Branch: master
Commit: c6f0b406f56ac5232d08cbd88c0bddfb2f640e90

gdb.dwarf2: Don't hardcode certain constants in Dwarf::assemble constructs

Two tests in gdb.dwarf2, data-loc.exp and dynarr-ptr.exp assume that
sizeof(int) is 4.  This patch looks up the integer size and uses this
constant for DW_AT_byte_size, DW_AT_lower_bound, and DW_AT_upper_bound.

I discovered this problem while looking at test results for this
msp430 multilib:

msp430-sim/-msim/-mcpu=msp430x/-mlarge/-mdata-region=either/-mcode-region=either

It fixes the following set of failures:

FAIL: gdb.dwarf2/dynarr-ptr.exp: print foo.three_ptr.all'first
FAIL: gdb.dwarf2/dynarr-ptr.exp: print foo.three_ptr'first
FAIL: gdb.dwarf2/dynarr-ptr.exp: print foo.three_ptr_tdef.all'first
FAIL: gdb.dwarf2/dynarr-ptr.exp: print foo.three_ptr_tdef'first
FAIL: gdb.dwarf2/dynarr-ptr.exp: print foo.five_ptr.all'first
FAIL: gdb.dwarf2/dynarr-ptr.exp: print foo.five_ptr'first
FAIL: gdb.dwarf2/dynarr-ptr.exp: print foo.five_ptr_tdef.all'first
FAIL: gdb.dwarf2/dynarr-ptr.exp: print foo.five_ptr_tdef'first
FAIL: gdb.dwarf2/data-loc.exp: print foo.three
FAIL: gdb.dwarf2/data-loc.exp: print foo.three(1)
FAIL: gdb.dwarf2/data-loc.exp: print foo.three(2)
FAIL: gdb.dwarf2/data-loc.exp: print foo.three(3)
FAIL: gdb.dwarf2/data-loc.exp: print foo.three_tdef
FAIL: gdb.dwarf2/data-loc.exp: print foo.three_tdef(1)
FAIL: gdb.dwarf2/data-loc.exp: print foo.three_tdef(2)
FAIL: gdb.dwarf2/data-loc.exp: print foo.three_tdef(3)
FAIL: gdb.dwarf2/data-loc.exp: print foo.five
FAIL: gdb.dwarf2/data-loc.exp: print foo.five(2)
FAIL: gdb.dwarf2/data-loc.exp: print foo.five(3)
FAIL: gdb.dwarf2/data-loc.exp: print foo.five(4)
FAIL: gdb.dwarf2/data-loc.exp: print foo.five(5)
FAIL: gdb.dwarf2/data-loc.exp: print foo.five(6)
FAIL: gdb.dwarf2/data-loc.exp: print foo.five_tdef
FAIL: gdb.dwarf2/data-loc.exp: print foo.five_tdef(2)
FAIL: gdb.dwarf2/data-loc.exp: print foo.five_tdef(3)
FAIL: gdb.dwarf2/data-loc.exp: print foo.five_tdef(4)
FAIL: gdb.dwarf2/data-loc.exp: print foo.five_tdef(5)
FAIL: gdb.dwarf2/data-loc.exp: print foo.five_tdef(6)
FAIL: gdb.dwarf2/data-loc.exp: print foo__three
FAIL: gdb.dwarf2/data-loc.exp: print foo__three_tdef
FAIL: gdb.dwarf2/data-loc.exp: print foo__five
FAIL: gdb.dwarf2/data-loc.exp: print foo__five_tdef

As I recall, there are still (other) problems with msp430 multilibs
which don't use -mlarge.

gdb/testsuite/ChangeLog:

	* gdb.dwarf2/data-loc.exp (Dwarf::assemble): Don't hardcode
	value associated with DW_AT_byte_size.
	* gdb.dwarf2/dynarr-ptr.exp (Dwarf::assemble): Don't hardcode
	constants for DW_AT_byte_size, DW_AT_lower_bound, and
	DW_AT_upper_bound.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Copy gnulib obstack files
@ 2015-11-09  5:01 sergiodj+buildbot
  2015-11-09  5:42 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-09  5:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 314dee8ea9be79a450d9f0b451619b67ebe0e017 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 314dee8ea9be79a450d9f0b451619b67ebe0e017

Copy gnulib obstack files

This copies obstack.[ch] from gnulib, and updates the docs.  The next
patch should be applied if someone repeats the import at a later date.

include/
	PR gdb/17133
	* obstack.h: Import current gnulib file.
libiberty/
	PR gdb/17133
	* obstack.c: Import current gnulib file.
	* obstacks.texi: Updated doc, from glibc's manual/memory.texi.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Modify obstack.[hc] to avoid having to include other gnulib files
@ 2015-11-09  5:43 sergiodj+buildbot
  2015-11-09  5:44 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-09  5:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e9f40d7d68ecc03c8c32ec0acd07c35359fdb4a3 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: e9f40d7d68ecc03c8c32ec0acd07c35359fdb4a3

Modify obstack.[hc] to avoid having to include other gnulib files

Using the standard gnulib obstack source requires importing quite a
lot of other files from gnulib, and requires build changes.

include/
	PR gdb/17133
	* obstack.h (__attribute_pure__): Expand _GL_ATTRIBUTE_PURE.
libiberty/
	PR gdb/17133
	* obstack.c (__alignof__): Expand alignof_type from alignof.h.
	(obstack_exit_failure): Don't use exitfail.h.
	(_): Include libintl.h when HAVE_LIBINTL_H and nls enabled.
	Provide default.  Don't include gettext.h.
	(_Noreturn): Define.
	* obstacks.texi: Adjust node references to external libc info files.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Configury changes for obstack optimization
@ 2015-11-09  5:57 sergiodj+buildbot
  2015-11-09  7:53 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-09  5:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c20a0642333655311b1f5b6f78adfeb8ec9fe1d4 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: c20a0642333655311b1f5b6f78adfeb8ec9fe1d4

Configury changes for obstack optimization

Provides defines used to determine whether glibc obstacks are
compatible.  Generally speaking, 32-bit targets won't need to use
obstack.o from libiberty if glibc is used, while 64-bit targets will,
until glibc gets the new obstack code.

libiberty/
	* configure.ac: Get size of size_t.
	* config.in: Regenerate.
	* configure: Regenerate.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
[parent not found: <78d14d2b9325fb4d25034eccf5650ef967d19640@gdb-build>]
* [binutils-gdb] Move copy_u.w to MSA64 ASE, remove copy_u.d.
@ 2015-11-09  8:59 sergiodj+buildbot
  2015-11-09  9:45 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-09  8:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT be7fe1cddbd5463651e0dff3e8d2cd06455246fc ***

Author: Robert Suchanek <robert.suchanek@imgtec.com>
Branch: master
Commit: be7fe1cddbd5463651e0dff3e8d2cd06455246fc

Move copy_u.w to MSA64 ASE, remove copy_u.d.

opcodes/ChangeLog:

	* mips-opc.c (mips_builtin_opcodes): Change "copy_u.w" to MSA64 ASE,
	remove "copy_u.d".

gas/testsuite/ChangeLog:

	* gas/mips/micromips@msa.d: Remove "copy_u.w".
	* gas/mips/msa.d: Likewise.
	* gas/mips/msa.s: Likweise.
	* gas/mips/mipsr6@msa.d: Likewise.  Replace addresses with regex.
	* gas/mips/msa64.d: Add "copy_u.w".  Remove "copy_u.d".
	* gas/mips/msa64.s: Likewise.
	* gas/mips/micromips@msa64.d: Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] New function displaced_step_in_progress_thread
@ 2015-11-09 14:49 sergiodj+buildbot
  2015-11-09 15:26 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-09 14:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c098766357b77f0553ec017b48abdd563de0281e ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: c098766357b77f0553ec017b48abdd563de0281e

New function displaced_step_in_progress_thread

This patch adds a new function displaced_step_in_progress_thread,
which returns whether the thread is in progress of displaced
stepping.

gdb:

2015-11-09  Yao Qi  <yao.qi@linaro.org>

	* infrun.c (displaced_step_in_progress_thread): New function.
	(handle_inferior_event_1): Call it.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Use ELF_STRING_ARM_unwind in arm-tdep.c
@ 2015-11-09 16:07 sergiodj+buildbot
  2015-11-09 16:44 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-09 16:07 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a5eda10c7857581e6ee641937f99aa76fa8044eb ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: a5eda10c7857581e6ee641937f99aa76fa8044eb

Use ELF_STRING_ARM_unwind in arm-tdep.c

We've already has the definition like this,

 #define ELF_STRING_ARM_unwind           ".ARM.exidx"

so it is better to use the macro rather than the string.

gdb:

2015-11-09  Yao Qi  <yao.qi@linaro.org>

	* arm-tdep.c (arm_exidx_new_objfile): Use
	ELF_STRING_ARM_unwind.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] bfd: Fix left shift of negative value.
@ 2015-11-09 16:23 sergiodj+buildbot
  2015-11-09 18:02 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-09 16:23 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 29f628db8835fd86b85ffb40d4a9ed5b1c28f1e6 ***

Author: Dominik Vogt <vogt@linux.vnet.ibm.com>
Branch: master
Commit: 29f628db8835fd86b85ffb40d4a9ed5b1c28f1e6

bfd: Fix left shift of negative value.

This patch fixes all occurences of left-shifting negative constants in C code
which is undefined by the C standard.

bfd/ChangeLog:

        * elf64-ppc.c (ppc64_elf_size_stubs, ppc64_elf_build_stubs): Fix left
        shift of negative value.
        * libbfd.c (safe_read_leb128): Likewise.
        * dwarf2.c (place_sections): Likewise.
        * bfd-in.h (align_power): Likewise.
        * bfd-in2.h (align_power): Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [Ada] GDB crash during "finish" of function with out parameters
@ 2015-11-09 18:08 sergiodj+buildbot
  2015-11-09 19:03 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-09 18:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT dddc0e16ef5d77e4f97d02ee0e2d4234c97dae0e ***

Author: Joel Brobecker <brobecker@adacore.com>
Branch: master
Commit: dddc0e16ef5d77e4f97d02ee0e2d4234c97dae0e

[Ada] GDB crash during "finish" of function with out parameters

Consider a function with the following signature...

   function F (R : out Rec_Type) return Enum_Type;

... where Rec_Type is a simple record:

   type Rec_Type is record
      Cur : Integer;
   end record;

Trying to "finish" from that function causes GDB to SEGV:

    (gdb) fin
    Run till exit from #0  bar.f (r=...) at bar.adb:5
    0x00000000004022fe in foo () at foo.adb:5
    5          I : Enum_Type := F (R);
    [1]    18949 segmentation fault (core dumped)  /[..]/gdb

This is related to the fact that funtion F has a parameter (R)
which is an "out" parameter being passed by copy. For those,
GNAT transforms the return value to be a record with multiple
fields: The first one is called "RETVAL" and contains the return
value shown in the source, and the remaining fields have the same
name as the "out" or "in out" parameters which are passed by copy.
So, in the example above, function F returns a struct that has
one field who name is "r".

Because "RETVAL" starts with "R", GDB thinks it's a wrapper field,
because it looks like the encoding used for  variant records:

   --    member_name ::= {choice} | others_choice
   --    choice ::= simple_choice | range_choice
   --    simple_choice ::= S number
   --    range_choice  ::= R number T number   <<<<<-----  here
   --    number ::= {decimal_digit} [m]
   --    others_choice ::= O (upper case letter O)

See ada_is_wrapper_field:

  return (name != NULL
          && (startswith (name, "PARENT")
              || strcmp (name, "REP") == 0
              || startswith (name, "_parent")
              || name[0] == 'S' || name[0] == 'R' || name[0] == 'O'));

As a result of this, when trying to print the RETURN value,
we think that RETVAL is a wrapper, and thus recurse into
print_field_values...

      if (ada_is_wrapper_field (type, i))
        {
          comma_needed =
            print_field_values (TYPE_FIELD_TYPE (type, i),
                                valaddr,
                                (offset
                                 + TYPE_FIELD_BITPOS (type, i) / HOST_CHAR_BIT),
                                stream, recurse, val, options,
                                comma_needed, type, offset, language);

... which is a problem since print_field_values assumes that
the type it is given ("TYPE_FIELD_TYPE (type, i)" here), is also
a record type. However, that's not the case, since RETVAL is
an enum. That eventually leads GDB to a NULL type when trying to
extract fields out of the enum, which then leads to a SEGV when
trying to dereference it.

Ideally, we'd want to be a little more careful in identifying
wrapper fields, by enhancing ada_is_wrapper_field to be a little
more complete in its analysis of the field name before declaring
it a variant record wrapper. However, it's not super easy to do
so, considering that the choices can be combined together when
complex choices are used. Eg:

   -- [...] the choice 1 .. 4 | 7 | -10 would be represented by
   --    R1T4S7S10m

Given that we are working towards getting rid of GNAT encodings,
which means that the above will eventually disappear, we took
the more pragmatic approach is just treating  RETVAL as a special
case.

gdb/ChangeLog:

        * ada-lang.c (ada_is_wrapper_field): Add special handling
        for fields called "RETVAL".

gdb/testsuite/ChangeLog:

        * gdb.ada/fin_fun_out: New testcase.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] sim: h8300: drop unused littleendian variable
@ 2015-11-10  5:19 sergiodj+buildbot
  2015-11-10  5:46 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-10  5:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5697b730e2da25240068ad935b9074bac2d15b60 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 5697b730e2da25240068ad935b9074bac2d15b60

sim: h8300: drop unused littleendian variable


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] sim: m32c: drop redundant dependency info
@ 2015-11-10  5:24 sergiodj+buildbot
  2015-11-10  7:01 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-10  5:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9b4888d5161e540f2f60f1c537cc66577094eac1 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 9b4888d5161e540f2f60f1c537cc66577094eac1

sim: m32c: drop redundant dependency info


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] sim: m32c: move test code to testsuite
@ 2015-11-10  5:32 sergiodj+buildbot
  2015-11-10  7:51 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-10  5:32 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1057567ea711d80f9937653179b06507827d5819 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 1057567ea711d80f9937653179b06507827d5819

sim: m32c: move test code to testsuite

Various target code belongs in the testsuite/ subdir, so move the m32c
code to match all the other targets.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix performance regression due to ld -r memmove
@ 2015-11-10  7:01 sergiodj+buildbot
  2015-11-10  8:46 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-10  7:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c316a17c40e44e8798b34ff84130904f2e7a53de ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: c316a17c40e44e8798b34ff84130904f2e7a53de

Fix performance regression due to ld -r memmove

The idea here is that instead of using memmove to shuffle the relocs
array every time one is deleted, to add a "wrel" pointer and copy from
rel[0] to wrel[0] as we go.

	* elf64-ppc.c (ppc64_elf_relocate_section): Use read and write
	pointers to reloc array, rather than memmove when deleting a
	reloc.  Don't use RELOC_AGAINST_DISCARDED_SECTION.  Adjust
	reloc counts at end of loop.
	* elf32-ppc.c (ppc_elf_relocate_section): Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix performance regression on x86 with ld -r
@ 2015-11-10  8:11 sergiodj+buildbot
  2015-11-10 10:53 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-10  8:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 60f2e42e00083accdcdbdda399534082bf309d1e ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 60f2e42e00083accdcdbdda399534082bf309d1e

Fix performance regression on x86 with ld -r

Similar fix to "commit c316a17c40e44e8798b34ff84130904f2e7a53de".

	* elf32-i386.c (elf_i386_relocate_section): Use read and write
	pointers to reloc array, rather than memmove when deleting a
	reloc.  Don't use RELOC_AGAINST_DISCARDED_SECTION.  Adjust
	reloc counts at end of loop.
	* elf64-x86-64.c (elf_x86_64_relocate_section): Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Handle x86 VTINHERIT/VTENTRY relocs when deleting relocations
@ 2015-11-10 12:38 sergiodj+buildbot
  2015-11-10 13:27 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-10 12:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 18954b29a1b49c9ffbfef925fdac4a23194ef82d ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 18954b29a1b49c9ffbfef925fdac4a23194ef82d

Handle x86 VTINHERIT/VTENTRY relocs when deleting relocations

	* elf32-i386.c (elf_i386_relocate_section): Handle VTINHERIT
	and VTENTRY relocations when deleting relocations.
	* elf64-x86-64.c (elf_x86_64_relocate_section): Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
[parent not found: <6e7675a70f5a375159f94354fb6f38519303a73d@gdb-build>]
* [binutils-gdb] gdb: Make use of 'add_info' to create info sub-commands.
@ 2015-11-11 10:07 sergiodj+buildbot
  2015-11-11 11:30 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-11 10:07 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5f515954d10b69ba6c390e7b8bcfdba2ced7850b ***

Author: Andrew Burgess <andrew.burgess@embecosm.com>
Branch: master
Commit: 5f515954d10b69ba6c390e7b8bcfdba2ced7850b

gdb: Make use of 'add_info' to create info sub-commands.

Switch to using 'add_info' function for creating basic info
sub-commands.

gdb/ChangeLog:

	* avr-tdep.c (_initialize_avr_tdep): Switch to 'add_info' for creating
	info sub-commands.
	* gnu-nat.c (add_task_commands): Likewise.
	* macrocmd.c (_initialize_macrocmd): Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Replace long int * cast with PTRACE_TYPE_RET *
@ 2015-11-11 20:26 sergiodj+buildbot
  2015-11-11 21:02 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-11 20:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4397c913d5640ba61316d3e631d544cf768b5a36 ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: 4397c913d5640ba61316d3e631d544cf768b5a36

Replace long int * cast with PTRACE_TYPE_RET *

These casts uses the typedef target type (long int *) instead of the
typedef name.  This was a little mistake in one of the big C++ cast
patches.

gdb/ChangeLog:

	* inf-ptrace.c (inf_ptrace_fetch_register): Change long int *
	cast to PTRACE_TYPE_RET *.
	(inf_ptrace_store_register): Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
[parent not found: <430e004ef7ecb3f75fc3c6642c9fdfb1d85a3694@gdb-build>]
* [binutils-gdb] Use gdb_byte * instead of void * in push_stack_item
@ 2015-11-12  9:25 sergiodj+buildbot
  2015-11-12 10:02 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-12  9:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT df3b6708fe2384913e66d90340b619190cc4530e ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: df3b6708fe2384913e66d90340b619190cc4530e

Use gdb_byte * instead of void * in push_stack_item

gdb:

2015-11-12  Yao Qi  <yao.qi@linaro.org>

	* arm-tdep.c (push_stack_item): Change contents type to
	const gdb_byte *.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] gdb.base/gnu_vector.exp: Don't test output from the inferior
@ 2015-11-13 15:14 sergiodj+buildbot
  2015-11-13 15:50 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-13 15:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 77ae9c1933b5007fdcbd222b0eaa2d775ea6ae43 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 77ae9c1933b5007fdcbd222b0eaa2d775ea6ae43

gdb.base/gnu_vector.exp: Don't test output from the inferior

gdb.base/gnu_vector.c printf the vector and gdb.base/gnu_vector.exp
expects the output by gdb_test_multiple.  Nowadays, the test doesn't
expect the output from inferior_spawn_id, which is wrong.  Even we
change the test to expect from inferior_spawn_id for the inferior
output, it is still possible the inferior exit before tcl/expect gets
the inferior output.  We see this fail on both s390x-linux and
ppc-linux on buildbot,

  FAIL: gdb.base/gnu_vector.exp: verify vector return value (the program exited)

https://sourceware.org/ml/gdb-testers/2015-q4/msg04922.html
https://sourceware.org/ml/gdb-testers/2015-q4/msg04952.html

In order to address these two shortcomings above in gnu_vector.exp,
this patch rewrites the test a little bit.  Get rid of checking the
inferior output, and instead checking them by printing them.  In this
way, the test can also be run on the target without inferior io
(gdb,noinferiorio is set in the board file).

gdb/testsuite:

2015-11-13  Yao Qi  <yao.qi@linaro.org>

	* gdb.base/gnu_vector.exp: Check the return value by "p res".
	* gdb.base/gnu_vector.c: Don't include stdio.h.
	(main): Don't print res and call add_some_intvecs.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Remove d10v from testsuite
@ 2015-11-13 15:22 sergiodj+buildbot
  2015-11-13 16:50 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-13 15:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c1862d0f60ee6050e3d4add7bbb1a595b1758473 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: c1862d0f60ee6050e3d4add7bbb1a595b1758473

Remove d10v from testsuite

This patch removes the leftover of the d10v stuff in the testsuite
directory. The d10v port was removed in GDB 6.7, but I happen to see
that there are still some leftovers about d10v in testsuite.

gdb/testsuite:

2015-11-13  Yao Qi  <yao.qi@linaro.org>

	* gdb.base/call-sc.exp (test_scalar_returns): Remove the
	comments about d10v.
	(test_scalar_returns): Likewise.
	* gdb.base/d10v.ld: Remove.
	* gdb.base/overlays.exp: Remove the target triplet checking for
	d10v-*-*.
	* gdb.base/structs.exp (test_struct_returns): Remove the
	comments about d10v.
	(test_struct_calls): Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] PR 19051: support of inferior call with gnu vector support on ARM
@ 2015-11-13 15:37 sergiodj+buildbot
  2015-11-13 18:47 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-13 15:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c4312b1985f4f3c567546f82e7f26f9b8e914b6f ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: c4312b1985f4f3c567546f82e7f26f9b8e914b6f

PR 19051: support of inferior call with gnu vector support on ARM

This patch teaches GDB to support gnu vector in inferior calls.  As a
result, fails in gdb.base/gnu_vector.exp are fixed.  The calling
convention of gnu vector isn't documented in the AAPCS, because it
is the GCC extension.  I checked the gcc/config/arm/arm.c, understand
how GCC pass arguments and return values, and do the same in GDB side.

The patch is tested with both hard float and soft float on arm-linux.

gdb:

2015-11-13  Yao Qi  <yao.qi@linaro.org>

	PR tdep/19051
	* arm-tdep.c (arm_type_align): Return the right alignment
	value for vector.
	(arm_vfp_cprc_sub_candidate): Return true for 64-bit and
	128-bit vector types.
	(arm_return_in_memory): Handel vector type.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] sim: drop extern C linkage from most sim interface headers
@ 2015-11-15  5:51 sergiodj+buildbot
  2015-11-15  6:55 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-15  5:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c4d4ed40834de8e2b493f83cf15291f2d2e38c6f ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: c4d4ed40834de8e2b493f83cf15291f2d2e38c6f

sim: drop extern C linkage from most sim interface headers

Since these headers merely have enum's, drop the extern C linkage
markings.  Helps to reduce the copy & paste spam.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] sim: testsuite: support basic vars in flags
@ 2015-11-15  6:14 sergiodj+buildbot
  2015-11-15  9:11 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-15  6:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9bea4d16a6f009585841c1134a024d10a61b8d56 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 9bea4d16a6f009585841c1134a024d10a61b8d56

sim: testsuite: support basic vars in flags

Sometimes in tests, we need supplemental files like linker scripts or
board helper files.  There's no way to set those flags in the tests
currently and relative paths don't work (breaks out of tree builds).

Update the main option parser to replace some strings on the fly.  Now
tests can do things like:

Long term we'll want to switch the framework to use the dejagnu helpers
like dg-xxx that gcc & gdb utilize.  But that'll require more rework.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] sim: sim-close: unify sim_close logic
@ 2015-11-15  7:40 sergiodj+buildbot
  2015-11-15 12:46 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-15  7:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6e4f085c7f459e0777a71bcb61ed3aa8257fa386 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 6e4f085c7f459e0777a71bcb61ed3aa8257fa386

sim: sim-close: unify sim_close logic

Other than the nice advantage of all sims having to declare one fewer
common function, this also fixes leakage in pretty much every sim.
Many were not freeing any resources, and a few were inconsistent as
to the ones they did.  Now we have a single module that takes care of
all the logic for us.

Most of the non-cgen based ones could be deleted outright.  The cgen
ones required adding a callback to the arch-specific cleanup func.
The few that still have close callbacks are to manage their internal
state.

We do not convert erc32, m32c, ppc, rl78, or rx as they do not use
the common sim core.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] sim: clean up redundant objects
@ 2015-11-15  7:53 sergiodj+buildbot
  2015-11-15 13:47 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-15  7:53 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d2dfd2424284bedaade2a203a51ea82364270a92 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: d2dfd2424284bedaade2a203a51ea82364270a92

sim: clean up redundant objects

Some of the target makefiles listed objects that were already pulled in
via SIM_NEW_COMMON_OBJS.  Clean those up.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] sim: mcore: switch to common sim-reg
@ 2015-11-15 13:41 sergiodj+buildbot
  2015-11-15 17:26 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-15 13:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9ef4651c4930423f9678832f793343059d4ef9ad ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 9ef4651c4930423f9678832f793343059d4ef9ad

sim: mcore: switch to common sim-reg

This is not entirely useful as mcore doesn't (yet) store its register
state in the cpu state, but it does allow for switching to the common
code for these functions.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] sim: mcore: add a fail testcase
@ 2015-11-15 13:49 sergiodj+buildbot
  2015-11-15 16:24 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-15 13:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5809534fe153fbbf925424716eb2e295f2217c65 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 5809534fe153fbbf925424716eb2e295f2217c65

sim: mcore: add a fail testcase


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] sim: mcore: pull cpu state out of global scope
@ 2015-11-15 13:49 sergiodj+buildbot
  2015-11-15 18:57 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-15 13:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7eed1055b89ad3207151734d34849dd8631d2da2 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 7eed1055b89ad3207151734d34849dd8631d2da2

sim: mcore: pull cpu state out of global scope

This avoids using global variables to hold the cpu state so we can
better integrate with the sim common code.

There's also a minor fix here where we move the pc register back into
the state that is accessible by the asints array.  When it was pulled
out previously, the reg store/fetch functions broke, but no one really
noticed as the mcore gdb port was dropped a while back.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] sim: d10v: push down sd/cpu vars
@ 2015-11-16  1:59 sergiodj+buildbot
  2015-11-16  2:33 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-16  1:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 679546067e1f3e1617bff22d03e483fb2beeed24 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 679546067e1f3e1617bff22d03e483fb2beeed24

sim: d10v: push down sd/cpu vars

By itself, this commit doesn't really change anything.  It lays the
groundwork for using the cpu state in follow up commits, both for
engine state and for cpu state.  Splitting things up this way so it
is easier to see how things have changed.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] sim: d10v: drop global callback state
@ 2015-11-16  2:15 sergiodj+buildbot
  2015-11-16  4:41 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-16  2:15 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e9b0081f986716eca364580fdfeb1034c5da76c9 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: e9b0081f986716eca364580fdfeb1034c5da76c9

sim: d10v: drop global callback state

Now that we have access to the sim state in all the right places,
use existing sim helpers in place of d10v_callback directly.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] sim: d10v: convert to common sim engine logic
@ 2015-11-16  2:24 sergiodj+buildbot
  2015-11-16  3:37 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-16  2:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT aadc1740c74a65b916b7d9bb6efe588352326871 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: aadc1740c74a65b916b7d9bb6efe588352326871

sim: d10v: convert to common sim engine logic

Now that we have access to the sim state everywhere, we can convert to
the common engine logic for overall processing.  This frees us up from
tracking exception state ourselves.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] sim: cr16/d10v: drop redundant call to sim_create_inferior
@ 2015-11-16  3:24 sergiodj+buildbot
  2015-11-16  5:41 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-16  3:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7ea08e8cb74bc21fcfe5befc0f3c8de3762cb0d6 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 7ea08e8cb74bc21fcfe5befc0f3c8de3762cb0d6

sim: cr16/d10v: drop redundant call to sim_create_inferior

With the conversion to the nrun frontend, this call should no longer be
necessary.  It also actively crashes when trying to use the sd state.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] sim: cr16: delete unused memory helpers
@ 2015-11-16  3:31 sergiodj+buildbot
  2015-11-16  7:46 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-16  3:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 137fbfd2818b5d1443f5f628e28b55b4e23037d1 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 137fbfd2818b5d1443f5f628e28b55b4e23037d1

sim: cr16: delete unused memory helpers

These aren't used anywhere and are just leftover from the d10v port.
Delete them so follow up commits are easier to follow.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] sim: cr16: convert to common sim memory modules
@ 2015-11-16  3:48 sergiodj+buildbot
  2015-11-16 10:05 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-16  3:48 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 761e171ad834a0d0adcd8712fde85ab1325afc3a ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 761e171ad834a0d0adcd8712fde85ab1325afc3a

sim: cr16: convert to common sim memory modules

The cr16 port has a lot of translation/offset logic baked into it, but
it all looks like copy & paste from the d10v port rather than something
the cr16 port wants.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] sim: cr16: convert to common sim engine logic
@ 2015-11-16  3:55 sergiodj+buildbot
  2015-11-16 10:47 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-16  3:55 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0ef7f98177f610dbb503d87f405c54e3722d8b25 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 0ef7f98177f610dbb503d87f405c54e3722d8b25

sim: cr16: convert to common sim engine logic

Now that we have access to the sim state everywhere, we can convert to
the common engine logic for overall processing.  This frees us up from
tracking exception state ourselves.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] sim: cr16: drop global callback state
@ 2015-11-16  4:03 sergiodj+buildbot
  2015-11-16 11:56 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-16  4:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9db36cf86d58f93def38a94ed05e1854beda3b20 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 9db36cf86d58f93def38a94ed05e1854beda3b20

sim: cr16: drop global callback state

Now that we have access to the sim state in all the right places,
use existing sim helpers in place of cr16_callback directly.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] sim: cr16: push down sd/cpu vars
@ 2015-11-16  4:30 sergiodj+buildbot
  2015-11-16  8:53 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-16  4:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 267b3b8e068f5043419991175bdbc56eb7a575be ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 267b3b8e068f5043419991175bdbc56eb7a575be

sim: cr16: push down sd/cpu vars

By itself, this commit doesn't really change anything.  It lays the
groundwork for using the cpu state in follow up commits, both for
engine state and for cpu state.  Splitting things up this way so it
is easier to see how things have changed.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] sim: sim-stop/sim-reason/sim-reg: move to common obj list
@ 2015-11-16  7:53 sergiodj+buildbot
  2015-11-16 12:52 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-16  7:53 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 797eee4264d1b504aabcbcabb6de2f1108441261 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 797eee4264d1b504aabcbcabb6de2f1108441261

sim: sim-stop/sim-reason/sim-reg: move to common obj list

Now that all arches (for the most part) have moved over, move sim-stop.o,
sim-reason.o, and sim-reg.o to the common object list and out of all the
arch ports.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix bug in arm_push_dummy_call by -fsanitize=address
@ 2015-11-16 14:53 sergiodj+buildbot
  2015-11-16 15:23 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-16 14:53 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ef9bd0b8d7d0a70f9fa9b239a03099c57eb5ceea ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: ef9bd0b8d7d0a70f9fa9b239a03099c57eb5ceea

Fix bug in arm_push_dummy_call by -fsanitize=address

When I build GDB with -fsanitize=address, and run testsuite,
some gdb.base/*.exp test triggers the ERROR below,

=================================================================
==7646==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x603000242810 at pc 0x487844 bp 0x7fffe32e84e0 sp 0x7fffe32e84d8
READ of size 4 at 0x603000242810 thread T0
    #0 0x487843 in push_stack_item /home/yao/SourceCode/gnu/gdb/git/gdb/arm-tdep.c:3405
    #1 0x48998a in arm_push_dummy_call /home/yao/SourceCode/gnu/gdb/git/gdb/arm-tdep.c:3960

In that path, GDB passes value on stack, in an INT_REGISTER_SIZE slot,
but the value contents' length can be less than INT_REGISTER_SIZE, so
the contents will be accessed out of the bound.  This patch adds an
array buf[INT_REGISTER_SIZE], and copy val to buf before writing them
to stack.

gdb:

2015-11-16  Yao Qi  <yao.qi@linaro.org>

	* arm-tdep.c (arm_push_dummy_call): New array buf.  Store regval
	to buf.  Pass buf instead of val to push_stack_item.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Use value_contents instead of value_contents_writeable
@ 2015-11-16 15:03 sergiodj+buildbot
  2015-11-16 16:25 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-16 15:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0d1993c072e5617b69204aef641acd2385b080ec ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 0d1993c072e5617b69204aef641acd2385b080ec

Use value_contents instead of value_contents_writeable

Both aarch64_push_dummy_call and bfin_push_dummy_call only use args[i]
contents but then never write to them, so that we can use
value_contents instead.

gdb:

2015-11-16  Yao Qi  <yao.qi@linaro.org>

	* aarch64-tdep.c (aarch64_push_dummy_call): Call value_contents instead
	of value_contents_writeable.
	* bfin-tdep.c (bfin_push_dummy_call): Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Pass value * instead of bfd_byte * to pass_* functions in aarch64-tdep.c
@ 2015-11-16 15:12 sergiodj+buildbot
  2015-11-16 17:25 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-16 15:12 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8e80f9d1d5cc0884ea1e677f796c69c36a5893cd ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 8e80f9d1d5cc0884ea1e677f796c69c36a5893cd

Pass value * instead of bfd_byte * to pass_* functions in aarch64-tdep.c

This patch changes the last argument of functions pass_in_x_or_stack,
pass_in_v_or_stack, pass_on_stack, and pass_in_x to type value *.

gdb:

2015-11-16  Yao Qi  <yao.qi@linaro.org>

	* aarch64-tdep.c (pass_in_x_or_stack): Change argument type
	from bfd_byte * to value *.  Caller updated.
	(pass_in_x): Likewise.
	(pass_in_v_or_stack): Likewise.
	(pass_on_stack): Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix stack buffer overflow in aarch64_extract_return_value
@ 2015-11-16 15:47 sergiodj+buildbot
  2015-11-16 21:05 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-16 15:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT db3516bbfabe710a0292f642cb83b95ea24c323a ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: db3516bbfabe710a0292f642cb83b95ea24c323a

Fix stack buffer overflow in aarch64_extract_return_value

Hi,
I build GDB with -fsanitize=address, and run testsuite.  In
gdb.base/callfuncs.exp, I see the following error,

p/c fun1()
=================================================================^M
==9601==ERROR: AddressSanitizer: stack-buffer-overflow on address 0x7fffee858530 at pc 0x6df079 bp 0x7fffee8583a0 sp 0x7fffee858398
WRITE of size 16 at 0x7fffee858530 thread T0
    #0 0x6df078 in regcache_raw_read /home/yao/SourceCode/gnu/gdb/git/gdb/regcache.c:673
    #1 0x6dfe1e in regcache_cooked_read /home/yao/SourceCode/gnu/gdb/git/gdb/regcache.c:751
    #2 0x4696a3 in aarch64_extract_return_value /home/yao/SourceCode/gnu/gdb/git/gdb/aarch64-tdep.c:1708
    #3 0x46ae57 in aarch64_return_value /home/yao/SourceCode/gnu/gdb/git/gdb/aarch64-tdep.c:1918

We are extracting return value from V registers (128 bit), but only
allocate X_REGISTER_SIZE-byte array, which isn't sufficient.  This
patch changes the array to V_REGISTER_SIZE.

gdb:

2015-11-16  Yao Qi  <yao.qi@linaro.org>

	* aarch64-tdep.c (aarch64_extract_return_value):  Change array
	buf's length to V_REGISTER_SIZE.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] gdb: Fix left shift of negative value.
@ 2015-11-17 10:11 sergiodj+buildbot
  2015-11-17 10:41 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-17 10:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 66c6502d7a457057683f56fd6d606fd9b2da0655 ***

Author: Dominik Vogt <vogt@linux.vnet.ibm.com>
Branch: master
Commit: 66c6502d7a457057683f56fd6d606fd9b2da0655

gdb: Fix left shift of negative value.

This patch fixes all occurences of left-shifting negative constants in C cod
which is undefined by the C standard.

gdb/ChangeLog:

        * hppa-tdep.c (hppa_sign_extend, hppa_low_hppa_sign_extend)
        (prologue_inst_adjust_sp, hppa_frame_cache): Fix left shift of negative
        value.
        * dwarf2read.c (read_subrange_type): Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix a problematic message with the STM32L4XX fixup on 32-bit hosts.
@ 2015-11-17 11:55 sergiodj+buildbot
  2015-11-17 13:42 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-17 11:55 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT eee926f28e8745dcd03adcb1113f3e4a7b79b1e5 ***

Author: Christophe Lyon <christophe.lyon@linaro.org>
Branch: master
Commit: eee926f28e8745dcd03adcb1113f3e4a7b79b1e5

Fix a problematic message with the STM32L4XX fixup on 32-bit hosts.

	* elf32-arm.c (elf32_arm_write_section): Force offset output as
	long (%ld).


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] guile disassembly hardcode TARGET_XFER_E_IO
@ 2015-11-17 13:56 sergiodj+buildbot
  2015-11-17 14:43 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-17 13:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9a4073e20b2f1da74cb3b46707e4f6fc4e700950 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 9a4073e20b2f1da74cb3b46707e4f6fc4e700950

guile disassembly hardcode TARGET_XFER_E_IO

Instead of adding a cast at the memory_error call, as needed for C++,
and have the reader understand the indirection, make it simple and
hardcode the generic memory error at the memory_error call site.

gdb/ChangeLog:
2015-11-17  Pedro Alves  <palves@redhat.com>

	* guile/scm-disasm.c (gdbscm_disasm_read_memory): Return -1 on
	error instead of TARGET_XFER_E_IO.
	(gdbscm_disasm_memory_error): Always pass TARGET_XFER_E_IO to
	memory_error.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Mach-O: add new defines and struct for darwin 14.5
@ 2015-11-17 14:19 sergiodj+buildbot
  2015-11-17 17:45 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-17 14:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c25b1ab690ddeeba239a044c8d0086867de30f93 ***

Author: Tristan Gingold <gingold@adacore.com>
Branch: master
Commit: c25b1ab690ddeeba239a044c8d0086867de30f93

Mach-O: add new defines and struct for darwin 14.5

include/mach-o/
	* arm64.h: New file.
	* unwind.h: Add arm64 encodings.
	* loader.h (bfd_mach_o_cpu_subtype): Add arm64 literals.
	(BFD_MACH_O_LC_ENCRYPTION_INFO_64, BFD_MACH_O_LC_LINKER_OPTIONS)
	(BFD_MACH_O_LC_LINKER_OPTIMIZATION_HINT)
	(BFD_MACH_O_LC_VERSION_MIN_WATCHOS): Define.
	* external.h (mach_o_encryption_info_64_command_external):
	(mach_o_linker_option_command_external)
	(mach_o_dyld_cache_header_external)
	(mach_o_dyld_cache_mapping_info_external)
	(mach_o_dyld_cache_image_info_external): New types.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [C++/mingw] Misc alloca casts
@ 2015-11-17 15:43 sergiodj+buildbot
  2015-11-17 19:47 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-17 15:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0ae1c716a162ce43a63c16c37aa8c6caaa484650 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 0ae1c716a162ce43a63c16c37aa8c6caaa484650

[C++/mingw] Misc alloca casts

gdb/ChangeLog:
2015-11-17  Pedro Alves  <palves@redhat.com>

	* exec.c (exec_file_attach, symfile_bfd_open) [__GO32__ || _WIN32
	|| __CYGWIN__]: Add casts.
	* utils.c (gdb_filename_fnmatch): Add cast.
	* windows-nat.c (windows_create_inferior): Add cast.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
[parent not found: <8d297bbf604c8318ffc72d5a7b3db654409c5ed9@gdb-build>]
* [binutils-gdb] [C++/mingw] gdb-dlfcn.c casts
@ 2015-11-17 15:51 sergiodj+buildbot
  2015-11-17 20:50 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-17 15:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2986367f8eea0dc5febab9c9fd1cf06b3a4a8fdb ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 2986367f8eea0dc5febab9c9fd1cf06b3a4a8fdb

[C++/mingw] gdb-dlfcn.c casts

Fixes:

../../src/gdb/gdb-dlfcn.c: In function 'void* gdb_dlsym(void*, const char*)':
../../src/gdb/gdb-dlfcn.c:105:49: error: invalid conversion from 'void*' to 'HMODULE {aka HINSTANCE__*}' [-fpermissive]
   return (void *) GetProcAddress (handle, symbol);
                                                 ^

gdb/ChangeLog:
2015-11-17  Pedro Alves  <palves@redhat.com>

	* gdb-dlfcn.c (gdb_dlsym, gdb_dlclose) [__MINGW32__]: Add casts to
	HMODULE.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [C++/mingw] windows-nat.c casts
@ 2015-11-17 15:58 sergiodj+buildbot
  2015-11-17 21:53 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-17 15:58 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 43499ea30db2a866412c86952c7e1d7b158d806f ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 43499ea30db2a866412c86952c7e1d7b158d806f

[C++/mingw] windows-nat.c casts

Fixes a set of errors like:

../../src/gdb/windows-nat.c: In function 'void _initialize_loadable()':
../../src/gdb/windows-nat.c:2778:30: error: invalid conversion from 'void*' to 'BOOL (*)(DWORD) {aka int (*)(long unsigned int)}' [-fpermissive]
       DebugActiveProcessStop = (void *)
                              ^

gdb/ChangeLog:
2015-11-17  Pedro Alves  <palves@redhat.com>

	* windows-nat.c (AdjustTokenPrivileges_ftype)
	(DebugActiveProcessStop_ftype, DebugBreakProcess_ftype)
	(DebugSetProcessKillOnExit_ftype, EnumProcessModules_ftype)
	(GetCurrentConsoleFont_ftype, GetModuleInformation_ftype)
	(LookupPrivilegeValueA_ftype, OpenProcessToken_ftype)
	(GetConsoleFontSize_ftype): New typedefs.
	(AdjustTokenPrivileges, DebugActiveProcessStop)
	(DebugBreakProcess, DebugSetProcessKillOnExit, EnumProcessModules)
	(GetConsoleFontSize, GetCurrentConsoleFont, GetModuleInformation)
	(LookupPrivilegeValueA, OpenProcessToken, GetConsoleFontSize):
	Adjust.
	(GetModuleFileNameEx_ftype): New typedef.
	(GetModuleFileNameEx): Use it.
	(_initialize_loadable): Define GPA macro and use it.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [C++/mingw] ser-tcp.c casts
@ 2015-11-17 16:14 sergiodj+buildbot
  2015-11-17 23:50 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-17 16:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 69e976f8cc902adc5ee8aec24e4a208f4afd51b3 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 69e976f8cc902adc5ee8aec24e4a208f4afd51b3

[C++/mingw] ser-tcp.c casts

Fixes a few errors like these:

../../src/gdb/ser-tcp.c: In function 'int net_open(serial*, const char*)':
../../src/gdb/ser-tcp.c:286:73: error: invalid conversion from 'void*' to 'char*' [-fpermissive]
     res = getsockopt (scb->fd, SOL_SOCKET, SO_ERROR, (void *) &err, &len);
                                                                         ^

gdb/ChangeLog:
2015-11-17  Pedro Alves  <palves@redhat.com>

	* ser-tcp.c (net_open) : Cast getsockopt argument to char *
	instead of void *.  Update comment.
	(net_read_prim): Cast recv argument to char * instead of void *.
	(net_write_prim): Cast send argument to char *.  Add comment.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [C++/mingw] handle_output_debug_string
@ 2015-11-17 16:22 sergiodj+buildbot
  2015-11-18  1:08 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-17 16:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c08790597c54c015ecfcd7ea56ebe30fa1d9e946 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: c08790597c54c015ecfcd7ea56ebe30fa1d9e946

[C++/mingw] handle_output_debug_string

Fixes:

 ../../../src/gdb/gdbserver/win32-low.c: In function 'int win32_kill(int)':
 ../../../src/gdb/gdbserver/win32-low.c:823:46: error: invalid conversion from 'int' to 'target_waitkind' [-fpermissive]
     struct target_waitstatus our_status = { 0 };
					       ^

handle_output_debug_string doesn't use the parameter for anything
(it's an output parameter in the gdb version), so just remove it.

gdb/gdbserver/ChangeLog:
2015-11-17  Pedro Alves  <palves@redhat.com>

	* win32-low.c (handle_output_debug_string): Remove parameter.
	(win32_kill): Remove our_status local and adjust call to
	handle_output_debug_string.
	(get_child_debug_event): Adjust call to
	handle_output_debug_string.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [C++/mingw] Fix windows-nat.c::xlate
@ 2015-11-17 16:29 sergiodj+buildbot
  2015-11-18  2:43 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-17 16:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 56db1d676cf48a3d90174f212379679d84bc3118 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 56db1d676cf48a3d90174f212379679d84bc3118

[C++/mingw] Fix windows-nat.c::xlate

Fixes:

../../src/gdb/windows-nat.c:287:11: error: invalid conversion from 'int' to 'gdb_signal' [-fpermissive]
   {-1, -1}};
           ^

The signal number here doesn't really matter.

gdb/ChangeLog:
2015-11-17  Pedro Alves  <palves@redhat.com>

	* windows-nat.c (xslate): Use GDB_SIGNAL_UNKNOWN instead of -1 as
	signal number for terminator.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [C++/mingw] gdbserver: gdb/host signal mixup
@ 2015-11-17 16:37 sergiodj+buildbot
  2015-11-18  3:54 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-17 16:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ce7715e2594db00b2f434f62aa264a1061221b72 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: ce7715e2594db00b2f434f62aa264a1061221b72

[C++/mingw] gdbserver: gdb/host signal mixup

Building in C++ caught a buglet here:

../../../src/gdb/gdbserver/win32-low.c: In function 'void win32_resume(thread_resume*, size_t)':
../../../src/gdb/gdbserver/win32-low.c:929:11: error: invalid conversion from 'int' to 'gdb_signal' [-fpermissive]
       sig = resume_info[0].sig;
           ^
../../../src/gdb/gdbserver/win32-low.c:934:11: error: invalid conversion from 'int' to 'gdb_signal' [-fpermissive]
       sig = 0;
           ^

Signals in the "struct thread_resume" structure are host signals, not
gdb signals.  The current code happens to work because the only
signals that the Windows port supports have the same number as the gdb
equivalent (see handle_exception for the win32 exception -> gdb signal
mapping).

gdb/gdbserver/ChangeLog:
2015-11-17  Pedro Alves  <palves@redhat.com>

	* win32-low.c (win32_resume): Use gdb_signal_from_host,
	GDB_SIGNAL_0 and gdb_signal_to_string.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [C++/mingw] Simplify first chance exception handling
@ 2015-11-17 16:45 sergiodj+buildbot
  2015-11-18  5:04 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-17 16:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 95824559df96a53ddeccbaacd91617f83c8d52cd ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 95824559df96a53ddeccbaacd91617f83c8d52cd

[C++/mingw] Simplify first chance exception handling

Building in C++ errors out with:

../../src/gdb/windows-nat.c: In function 'int get_windows_debug_event(target_ops*, int, target_waitstatus*)':
../../src/gdb/windows-nat.c:1503:13: warning: invalid conversion from 'int' to 'gdb_signal' [-fpermissive]
    last_sig = 1;
             ^
../../src/gdb/windows-nat.c:1533:43: warning: invalid conversion from 'int' to 'gdb_signal' [-fpermissive]
  windows_resume (ops, minus_one_ptid, 0, 1);
                                           ^
../../src/gdb/windows-nat.c:1228:1: warning:   initializing argument 4 of 'void windows_resume(target_ops*, ptid_t, int, gdb_signal)' [-fpermissive]
 windows_resume (struct target_ops *ops,
 ^

Looking at the code, I can't figure out why we treat first chance
exceptions any different here.

AFAICS, we set last_sig to 1, and then call windows_resume passing
signal==1, so the DBG_EXCEPTION_NOT_HANDLED code path in win32_resume
is taken:

~~~
  if (sig != GDB_SIGNAL_0)
    {
      if (current_event.dwDebugEventCode != EXCEPTION_DEBUG_EVENT)
	{
	  OUTMSG (("Cannot continue with signal %d here.\n", sig));
	}
      else if (sig == last_sig)
	continue_status = DBG_EXCEPTION_NOT_HANDLED;
      else
	OUTMSG (("Can only continue with recieved signal %d.\n", last_sig));
    }
~~~

Fix this by removing this special casing.  gdbserver also goes
straight to continuing with DBG_EXCEPTION_NOT_HANDLED, AFAICS.

gdb/ChangeLog:
2015-11-17  Pedro Alves  <palves@redhat.com>

	* windows-nat.c (handle_exception): Return 0 for first chance
	exceptions.
	(get_windows_debug_event): Adjust.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] MinGW and attribute format(printf/gnu_printf)
@ 2015-11-17 17:01 sergiodj+buildbot
  2015-11-18  6:26 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-17 17:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 91ee7171d0886731900ab0238ce3795241d877a4 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 91ee7171d0886731900ab0238ce3795241d877a4

MinGW and attribute format(printf/gnu_printf)

Cross building gdbserver for --host=x86_64-w64-mingw32 with gcc 4.8.4
20141219 (Fedora MinGW 4.8.4-1.fc20), I get:

  src/gdb/gdbserver/tracepoint.c: In function 'cmd_qtdp':
  src/gdb/gdbserver/tracepoint.c:2577:7: error: unknown conversion type character 'l' in format [-Werror=format=]
	 trace_debug ("Defined %stracepoint %d at 0x%s, "
	 ^
  src/gdb/gdbserver/tracepoint.c:2577:7: error: unknown conversion type character 'l' in format [-Werror=format=]
  src/gdb/gdbserver/tracepoint.c:2577:7: error: too many arguments for format [-Werror=format-extra-args]
  src/gdb/gdbserver/tracepoint.c: In function 'stop_tracing':
  src/gdb/gdbserver/tracepoint.c:3447:7: error: unknown conversion type character 'l' in format [-Werror=format=]
	 trace_debug ("Stopping the trace because "
	 ^
  src/gdb/gdbserver/tracepoint.c:3447:7: error: too many arguments for format [-Werror=format-extra-args]
  src/gdb/gdbserver/tracepoint.c: In function 'collect_data_at_tracepoint':
  src/gdb/gdbserver/tracepoint.c:4651:3: error: unknown conversion type character 'l' in format [-Werror=format=]
     trace_debug ("Making new traceframe for tracepoint %d at 0x%s, hit %" PRIu64,
     ^
  src/gdb/gdbserver/tracepoint.c:4651:3: error: too many arguments for format [-Werror=format-extra-args]
  src/gdb/gdbserver/tracepoint.c: In function 'collect_data_at_step':
  src/gdb/gdbserver/tracepoint.c:4687:3: error: unknown conversion type character 'l' in format [-Werror=format=]
     trace_debug ("Making new step traceframe for "
     ^

trace_debug is a macro that calls:

  static void trace_vdebug (const char *, ...) ATTRIBUTE_PRINTF (1, 2);

The calls that fail checking use PRIu64, etc., like:

      trace_debug ("Defined %stracepoint %d at 0x%s, "
		   "enabled %d step %" PRIu64 " pass %" PRIu64,
		   tpoint->type == fast_tracepoint ? "fast "
		   : tpoint->type == static_tracepoint ? "static " : "",
		   tpoint->number, paddress (tpoint->address), tpoint->enabled,
		   tpoint->step_count, tpoint->pass_count);

gnulib's stdio/printf module replacements may make %llu, etc. work on
mingw, instead of the MS-specific %I64u, and thus may make PRIu64
expand to %llu.  However, gcc isn't aware of that, because libiberty's
ansidecl.h defines ATTRIBUTE_PRINTF as using attribute format(printf).
But, with that format, gcc checks for MS-style format strings (%I64u).
In order to have gcc expect gnu/standard formats, we need to use
gnu_printf format instead.  Which version to use (printf/gnu_printf)
depends on msvcrt and mingw version, and so gnulib has a
configure-time check, and defines _GL_ATTRIBUTE_FORMAT_PRINTF
accordingly.

Since _GL_ATTRIBUTE_FORMAT_PRINTF is compatible with ATTRIBUTE_PRINTF,
the fix is simply to make use of the former.

gdb/ChangeLog:
2015-11-17  Pedro Alves  <palves@redhat.com>

	* common/common-defs.h (ATTRIBUTE_PRINTF): Redefine in terms of
	_GL_ATTRIBUTE_FORMAT_PRINTF after including ansidecl.h.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [C++] Always use setjmp/longjmp for exceptions
@ 2015-11-17 17:09 sergiodj+buildbot
  2015-11-18  6:35 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-17 17:09 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT eec461d0a8e7ae14c7fe8f0196ab8d0e30285d83 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: eec461d0a8e7ae14c7fe8f0196ab8d0e30285d83

[C++] Always use setjmp/longjmp for exceptions

We currently throw exceptions from signal handlers (e.g., for
Quit/ctrl-c).  But throwing C++ exceptions from signal handlers is
undefined.  (That doesn't restore signal masks, like siglongjmp does,
and, because asynchronous signals can arrive at any instruction, we'd
have to build _everything_ with -fasync-unwind-tables to make it
reliable.)  It happens to work on x86_64 GNU/Linux at least, but it's
likely broken on other ports.

Until we stop throwing from signal handlers, use setjmp/longjmp based
exceptions in C++ mode as well.

gdb/ChangeLog:
2015-11-17  Pedro Alves  <palves@redhat.com>

	* common/common-exceptions.h (GDB_XCPT_SJMP, GDB_XCPT_TRY)
	(GDB_XCPT_RAW_TRY, GDB_XCPT): Define.
	Replace __cplusplus checks with GDB_XCPT checks throughout.
	* common/common-exceptions.c: Replace __cplusplus checks with
	GDB_XCPT checks throughout.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Introduce null_block_symbol
@ 2015-11-17 17:18 sergiodj+buildbot
  2015-11-18  6:44 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-17 17:18 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b6b806729dd5c4c46981d59f351460b4d7989548 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: b6b806729dd5c4c46981d59f351460b4d7989548

Introduce null_block_symbol

... in the spirit of null_ptid, null_frame_id, etc.

Fixes two instances of:

  /root/binutils-gdb/gdb/cp-namespace.c: In function 'block_symbol cp_lookup_nested_symbol(type*, const char*, const block*, domain_enum)':
  /root/binutils-gdb/gdb/cp-namespace.c:1010: warning: jump to case label
  /root/binutils-gdb/gdb/cp-namespace.c:1008: error:   crosses initialization of 'block_symbol <anonymous>'

Compiler info:

  Reading specs from /usr/lib/gcc-lib/amd64-unknown-openbsd5.8/4.2.1/specs
  Target: amd64-unknown-openbsd5.8
  Configured with: OpenBSD/amd64 system compiler
  Thread model: posix
  gcc version 4.2.1 20070719

gdb/ChangeLog:
2015-11-17  Pedro Alves  <palves@redhat.com>

	* cp-namespace.c (cp_lookup_bare_symbol)
	(cp_search_static_and_baseclasses, cp_lookup_symbol_via_imports)
	(cp_lookup_symbol_via_all_imports, cp_lookup_nested_symbol_1)
	(cp_lookup_nested_symbol): Use null_block_symbol.
	* d-namespace.c (d_lookup_symbol, d_lookup_nested_symbol)
	(d_lookup_symbol_imports, d_lookup_symbol_module): Use
	null_block_symbol.
	* symtab.c (null_block_symbol): New global.
	* symtab.h (null_block_symbol): Declare.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix gdb.threads/multiple-step-overs.exp fails on arm
@ 2015-11-17 17:26 sergiodj+buildbot
  2015-11-18  6:54 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-17 17:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1946c4ccca04e374acc040fc30c8b44d2c9ca0a8 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 1946c4ccca04e374acc040fc30c8b44d2c9ca0a8

Fix gdb.threads/multiple-step-overs.exp fails on arm

Hi,
Some tests in gdb.threads/multiple-step-overs.exp fail on arm target
when the displaced stepping on, but they pass when displaced stepping
is off.

 FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: step: step
 FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: next: next
 FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: continue: continue
 FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: signal thr1: continue to sigusr1_handler

when displaced stepping is on,

Sending packet: $vCont;c#a8...infrun: infrun_async(1)^M <--- [1]
infrun: prepare_to_wait^M
infrun: target_wait (-1.0.0, status) =^M
infrun:   -1.0.0 [Thread 0],^M
infrun:   status->kind = ignore^M
infrun: TARGET_WAITKIND_IGNORE^M
infrun: prepare_to_wait^M
Packet received: T05swbreak:;0b:f8faffbe;0d:409ee7b6;0f:d0880000;thread:p635.636;core:0;^M
infrun: target_wait (-1.0.0, status) =^M
infrun:   1589.1590.0 [Thread 1590],^M
infrun:   status->kind = stopped, signal = GDB_SIGNAL_TRAP^M
infrun: TARGET_WAITKIND_STOPPED^M
infrun: stop_pc = 0x88d0^M
infrun: context switch^M
infrun: Switching context from Thread 1591 to Thread 1590^

GDB resumes the whole process (all threads) rather than the specific
thread for which GDB wants to step over the breakpoint (as shown in [1]).
That is wrong because we resume a single thread and leave others stopped
when doing a normal step over where we temporarily remove the breakpoint,
single-step, reinsert the breakpoint, is that if we let other threads run
in the period while the breakpoint is removed, then these other threads
could miss the breakpoint.  Since with displaced stepping, we don't ever
remove the breakpoint, it should be fine to let other threads run.  However,
there's another reason that we should not let other threads run: that is
the case where some of those threads are also stopped for a breakpoint that
itself needs to be stepped over.  If we just let those threads run, then
they immediately re-trap their breakpoint again.

when displaced stepping is off, GDB behaves correctly, only resumes
the specific thread (as shown in [2]).

Sending packet: $vCont;c:p611.613#b2...infrun: infrun_async(1)^M <-- [2]
infrun: prepare_to_wait^M
infrun: target_wait (-1.0.0, status) =^M
infrun:   -1.0.0 [Thread 0],^M
infrun:   status->kind = ignore^M
infrun: TARGET_WAITKIND_IGNORE^M
infrun: prepare_to_wait^M
Packet received: T05swbreak:;0b:f8faffbe;0d:409e67b6;0f:48880000;thread:p611.613;core:1;^M
infrun: target_wait (-1.0.0, status) =^M
infrun:   1553.1555.0 [Thread 1555],^M
infrun:   status->kind = stopped, signal = GDB_SIGNAL_TRAP^M
infrun: TARGET_WAITKIND_STOPPED^M
infrun: clear_step_over_info^M
infrun: stop_pc = 0x8848

The current logic in GDB on deciding the set of threads to resume is:

  /* Decide the set of threads to ask the target to resume.  */
  if ((step || thread_has_single_step_breakpoints_set (tp))
      && tp->control.trap_expected)
    {
      /* We're allowing a thread to run past a breakpoint it has
	 hit, by single-stepping the thread with the breakpoint
	 removed.  In which case, we need to single-step only this
	 thread, and keep others stopped, as they can miss this
	 breakpoint if allowed to run.  */
      resume_ptid = inferior_ptid;
    }
  else
    resume_ptid = internal_resume_ptid (user_step);

it doesn't handle the case correctly that GDB continue (instead of
single step) the thread for displaced stepping.

I also update the comment below to reflect the code.  I remove the
"with the breakpoint removed" comment, because GDB doesn't remove
breakpoints in displaced stepping, so we don't have to worry that
other threads may miss the breakpoint.

Patch is regression tested on both x86_64-linux and arm-linux.

gdb:

2015-11-17  Yao Qi  <yao.qi@linaro.org>

	* infrun.c (resume): Check control.trap_expected only
	when deciding the set of threads to resume.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [sim/ppc] Fix printf_filtered reference
@ 2015-11-17 21:29 sergiodj+buildbot
  2015-11-18  7:03 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-17 21:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a6760b615451518704601cae9327d333fe4bec57 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: a6760b615451518704601cae9327d333fe4bec57

[sim/ppc] Fix printf_filtered reference

Building a gdb that includes the PPC sim in C++ mode fails to link with:

(...)s.o compile-object-load.o compile-object-run.o compile-loc2c.o compile-c-support.o inflow.o    init.o \
          ../sim/ppc/libsim.a ../readline/libreadline.a ../opcodes/libopcodes.a ../bfd/libbfd.a -lz  ../libiberty/libiberty.a ../libdecnumber/libdecnumber.a    -ldl -ldl -lncurses -lm -ldl  -lguile-2.0 -lgc  -lpthread -ldl -lutil -lm -lpython2.7 -Xlinker -export-dynamic -lexpat -llzma -lbabeltrace -lbabeltrace-ctf  ../libiberty/libiberty.a  build-gnulib/import/libgnu.a
../sim/ppc/libsim.a(sim_calls.o): In function `sim_open':
/home/pedro/gdb/mygit/cxx-convertion/src/sim/ppc/sim_calls.c:73: undefined reference to `printf_filtered'
/home/pedro/gdb/mygit/cxx-convertion/src/sim/ppc/sim_calls.c:73: undefined reference to `printf_filtered'
../sim/ppc/libsim.a(sim_calls.o): In function `sim_close':
/home/pedro/gdb/mygit/cxx-convertion/src/sim/ppc/sim_calls.c:93: undefined reference to `printf_filtered'
/home/pedro/gdb/mygit/cxx-convertion/src/sim/ppc/sim_calls.c:93: undefined reference to `printf_filtered'
../sim/ppc/libsim.a(sim_calls.o): In function `sim_load':
/home/pedro/gdb/mygit/cxx-convertion/src/sim/ppc/sim_calls.c:102: undefined reference to `printf_filtered'
../sim/ppc/libsim.a(sim_calls.o):/home/pedro/gdb/mygit/cxx-convertion/src/sim/ppc/sim_calls.c:102: more undefined references to `printf_filtered' follow
collect2: error: ld returned 1 exit status

The undefined references come from TRACE macro calls, which expand to
calls to printf_filtered.

But note that the sim's 'printf_filtered' is actually a #define to
'sim_io_printf_filtered', in sim_callbacks.h :

 #define printf_filtered sim_io_printf_filtered

AFAICS, this is not meant to call gdb's printf_filtered function.  The
ChangeLog entry that added the printf_filtered macro reads:

 Tue Jul 30 21:12:24 1996  Andrew Cagney  <cagney@kremvax.highland.com.au>

	 * sim_callbacks.h (sim_io_printf_filtered): Replace
	 printf_filtered with a local simulator specific version.  Add
	 #define printf_filtered to simplify updating of existing code.

That is, just another incomplete/partial transition.  Maybe prior to
1996 this was really meant to call gdb's printf_filtered version.

The reference to printf_filtered appears because sim_calls.c, the
compilation unit that fails to link, has this at the top:

 #undef printf_filtered /* blow away the mapping */

presumably so that this further below:

 void
 sim_io_printf_filtered(const char *fmt,
			...)
 {
   (...)
   callbacks->printf_filtered(callbacks, "%s", message);
 }

works.  So those TRACE macros instances in sim_calls.c just happen to
work because gdb is linked in, which satisfies the 'printf_filtered'
reference, when GDB is built in C mode.  When built in C++ mode, the
problem is exposed, as GDB's printf_filtered is mangled.

The fix here is to make the TRACE macro call sim_io_printf_filtered
directly.

(Standalone "run" doesn't fail to link simply because the offending
routines are not part of its link.)

sim/ppc/ChangeLog
2015-11-17  Pedro Alves  <palves@redhat.com>

	* debug.h (TRACE, ITRACE, DTRACE, DITRACE, PTRACE): Call
	sim_io_printf_filtered instead of printf_filtered.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] sim: always enable modulo memory
@ 2015-11-18  4:18 sergiodj+buildbot
  2015-11-18  7:12 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-18  4:18 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cdf850e9d953f765f600e1ecae61664eab5ae7f1 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: cdf850e9d953f765f600e1ecae61664eab5ae7f1

sim: always enable modulo memory

Having this be a config option doesn't make sense: the code size is
pretty much the same (as all the logic is still active), and if it's
disabled, the sim throws an error if you try to use it.  That means
we can't break sims that weren't using it before by enabling it all
the time.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] sim: mn10300/v850: drop unused WITH_CORE define
@ 2015-11-18  4:25 sergiodj+buildbot
  2015-11-18  7:21 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-18  4:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c389945b7a470aa328972026fe4a836c57ccb7ae ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: c389945b7a470aa328972026fe4a836c57ccb7ae

sim: mn10300/v850: drop unused WITH_CORE define

This was dropped from the sim core in 1997, so no point in having these
sim ports continue to define it.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] mach-o cleanup: remove useless calls to bfd_seek.
@ 2015-11-18 11:42 sergiodj+buildbot
  2015-11-18 11:47 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-18 11:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 47daa70fe08c57aaafa6fe1a7e762072909d0f8f ***

Author: Tristan Gingold <gingold@adacore.com>
Branch: master
Commit: 47daa70fe08c57aaafa6fe1a7e762072909d0f8f

mach-o cleanup: remove useless calls to bfd_seek.

Also support new commands.

bfd/
	* mach-o.h (struct mach_o_data_struct): Add hdr_offset field.
	(bfd_mach_o_fat_archive_p): Renames prototype.
	(bfd_mach_o_fat_openr_next_archived_file): Renames.
	(bfd_mach_o_header_p): Add argument.
	* mach-o.c (bfd_mach_o_read_header): Add hdr_off argument and
	use it.
	(bfd_mach_o_read_section_32, bfd_mach_o_read_section_64)
	(bfd_mach_o_read_section): Remove offset argument.
	(bfd_mach_o_read_dylinker): Remove bfd_seek call.
	(bfd_mach_o_read_dylib, bfd_mach_o_read_prebound_dylib)
	(bfd_mach_o_read_prebind_cksum, bfd_mach_o_read_twolevel_hints)
	(bfd_mach_o_read_fvmlib, bfd_mach_o_read_dysymtab)
	(bfd_mach_o_read_symtab, bfd_mach_o_read_uuid)
	(bfd_mach_o_read_linkedit, bfd_mach_o_read_str)
	(bfd_mach_o_read_dyld_info, bfd_mach_o_read_version_min)
	(bfd_mach_o_read_encryption_info): Likewise.
	(bfd_mach_o_read_encryption_info_64): New function.
	(bfd_mach_o_read_main, bfd_mach_o_read_source_version)
	(bfd_mach_o_read_segment): Remove call to bfd_seek.
	(bfd_mach_o_read_command): Use hdr_offset in bfd_seek.
	Handle BFD_MACH_O_LC_LINKER_OPTIMIZATION_HINT,
	BFD_MACH_O_LC_ENCRYPTION_INFO_64, BFD_MACH_O_LC_VERSION_MIN_WATCHOS.
	(bfd_mach_o_header_p): Add hdr_off argument.
	(bfd_mach_o_gen_object_p, bfd_mach_o_gen_core_p): Adjust calls.
	(bfd_mach_o_fat_archive_p): Renames.
	(bfd_mach_o_fat_openr_next_archived_file): Renames.
	(bfd_mach_o_close_and_cleanup): Remove useless code.
	(bfd_mach_o_close_and_cleanup): Define.
	* mach-o-x86-64.c (bfd_mach_o_x86_64_object_p)
	(bfd_mach_o_x86_64_core_p): Adjust calls.
	* mach-o-target.c: Move defines for archive from mach-o.c.
	Remove check on TARGET_ARCHIVE.
	* mach-o-i386.c (bfd_mach_o_i386_object_p)
	(bfd_mach_o_i386_core_p): Adjust calls.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Prevent looping in archives
@ 2015-11-18 11:52 sergiodj+buildbot
  2015-11-18 11:56 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-18 11:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4978e369fb75a8b7756bf4201668b2a9d9556286 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 4978e369fb75a8b7756bf4201668b2a9d9556286

Prevent looping in archives

	PR 19256
	* archive.c (bfd_generic_openr_next_archived_file): Don't allow
	backward file movement via "negative" sizes.
	* coff-alpha.c (alpha_ecoff_openr_next_archived_file): Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix out of boundary access in pass_in_v
@ 2015-11-18 12:02 sergiodj+buildbot
  2015-11-18 12:05 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-18 12:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0735fdddbc086291f6d2357e8fa57e5df6095e89 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 0735fdddbc086291f6d2357e8fa57e5df6095e89

Fix out of boundary access in pass_in_v

Hi,
I build GDB with -fsanitize=address, and run testsuite.  In
gdb.base/callfuncs.exp, I see the following error,

p t_float_values(0.0,0.0)
=================================================================
==8088==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x6020000cb650 at pc 0x6e195c bp 0x7fff164f9770 sp 0x7fff164f9768
READ of size 16 at 0x6020000cb650 thread T0^
    #0 0x6e195b in regcache_raw_write /home/yao/SourceCode/gnu/gdb/git/gdb/regcache.c:912
    #1 0x6e1e52 in regcache_cooked_write /home/yao/SourceCode/gnu/gdb/git/gdb/regcache.c:945
    #2 0x466d69 in pass_in_v /home/yao/SourceCode/gnu/gdb/git/gdb/aarch64-tdep.c:1101
    #3 0x467512 in pass_in_v_or_stack /home/yao/SourceCode/gnu/gdb/git/gdb/aarch64-tdep.c:1196
    #4 0x467d7d in aarch64_push_dummy_call /home/yao/SourceCode/gnu/gdb/git/gdb/aarch64-tdep.c:1335

The code in pass_in_v read contents from V registers (128 bit), but the
data passed through V registers can be less than 128 bit.  In this case,
float is passed.  So writing V registers contents into contents buff
will cause overflow.  In this patch, we add an array reg[V_REGISTER_SIZE],
which is to hold the contents from V registers, and then copy useful
bits to buf.

gdb:

2015-11-18  Yao Qi  <yao.qi@linaro.org>

	* aarch64-tdep.c (pass_in_v): Add argument len.  Add local array
	reg.  Callers updated.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [gdbserver/ipa] Fix build dependencies
@ 2015-11-18 13:17 sergiodj+buildbot
  2015-11-18 13:46 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-18 13:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1798301e20d5c5be69a362bbec149abce446c215 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 1798301e20d5c5be69a362bbec149abce446c215

[gdbserver/ipa] Fix build dependencies

Commit 91ee7171d088 (MinGW and attribute format(printf/gnu_printf))
made common/common-defs.h depend on gnulib's substitute headers.
Turns out that that broke the gdbserver/ipa build (as the buildbots
discovered) because nothing is making sure that gnulib is built before
the ipa is.

gdb/gdbserver/ChangeLog:
2015-11-18  Pedro Alves  <palves@redhat.com>

	* Makefile.in (all_object_files): Add $IPA_OBJS.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Constify value_cstring
@ 2015-11-18 16:11 sergiodj+buildbot
  2015-11-18 16:45 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-18 16:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e3a3797ee558f4f84c67a65e1d9abce845f15abd ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: e3a3797ee558f4f84c67a65e1d9abce845f15abd

Constify value_cstring

gdb/ChangeLog:
2015-11-18  Simon Marchi  <simon.marchi@ericsson.com>

	* valops.c (value_cstring): Constify 'ptr' parameter.
	* value.h (value_cstring): Constify 'ptr' parameter.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [ARM] Add ARMv8.2 architecture feature and command line option.
@ 2015-11-19  9:35 sergiodj+buildbot
  2015-11-19 11:08 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-19  9:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 56a1b672f4b97b10b093f02540dff1c855a69855 ***

Author: Matthew Wahab <matthew.wahab@arm.com>
Branch: master
Commit: 56a1b672f4b97b10b093f02540dff1c855a69855

[ARM] Add ARMv8.2 architecture feature and command line option.

ARMv8.2 is an architectural extension of ARMv8. This patch adds an
architecture feature macro for ARMv8.2 to the binutils ARM target
with GAS command line option -march=armv8.2-a.

gas/
2015-11-19  Matthew Wahab  <matthew.wahab@arm.com>

	* config/tc-arm.c (arm_archs): Add "armv8.2-a".
	* doc/c-arm.texi (-march): Add "armv8.2-a".

include/opcode/
2015-11-19  Matthew Wahab  <matthew.wahab@arm.com>

	* arm.h (ARM_EXT2_V8_2A): New.
	(ARM_ARCH_V8_2A): New.

Change-Id: I9e0f50e3c6cea24e6b87b8b862fd4e1cdcc1052e


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [S/390] Add null ptr check + port GOTOFF handling from 32 bit over to 64 bit
@ 2015-11-19 10:20 sergiodj+buildbot
  2015-11-19 12:03 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-19 10:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d47b13e0e2286ef9e9444292bc5631f43cf226da ***

Author: Andreas Krebbel <krebbel@linux.vnet.ibm.com>
Branch: master
Commit: d47b13e0e2286ef9e9444292bc5631f43cf226da

[S/390] Add null ptr check + port GOTOFF handling from 32 bit over to 64 bit

bfd/ChangeLog:

2015-11-19  Andreas Krebbel  <krebbel@linux.vnet.ibm.com>

	PR ld/19263
	* elf32-s390.c (elf_s390_gc_sweep_hook): Add null ptr check.
	* elf64-s390.c (elf_s390_check_relocs): Port the GOTOFF handling
	over from the 32 bit code.
	(elf_s390_relocate_section): Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Cast void * to struct user_pt_regs *
@ 2015-11-19 14:11 sergiodj+buildbot
  2015-11-19 14:42 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-19 14:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6a69a054f7581d16d4f65f80c45b92176311e1ef ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 6a69a054f7581d16d4f65f80c45b92176311e1ef

Cast void * to struct user_pt_regs *

This patch fixes the following GDBserver build errors in C++.

gdb/gdbserver/linux-aarch64-low.c:108:33: error: invalid conversion from 'void*' to 'user_pt_regs*' [-fpermissive]
   struct user_pt_regs *regset = buf;
                                 ^
gdb/gdbserver/linux-aarch64-low.c: In function 'void aarch64_store_gregset(regcache*, const void*)':
gdb/gdbserver/linux-aarch64-low.c:121:39: error: invalid conversion from 'const void*' to 'const user_pt_regs*' [-fpermissive]
   const struct user_pt_regs *regset = buf;

gdb/gdbserver:

2015-11-19  Yao Qi  <yao.qi@linaro.org>

	* linux-aarch64-low.c (aarch64_fill_gregset): Cast buf to
	struct user_pt_regs *.
	(aarch64_store_gregset): Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Cast void * to user_fpsimd_state *.
@ 2015-11-19 14:21 sergiodj+buildbot
  2015-11-19 15:43 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-19 14:21 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9caa33114e9195b0d28ad46d21a11a8f838ffb07 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 9caa33114e9195b0d28ad46d21a11a8f838ffb07

Cast void * to user_fpsimd_state *.

This patch fixes the following build error in GDBserver,

gdb/gdbserver/linux-aarch64-low.c: In function 'void aarch64_fill_fpregset(regcache*, void*)':
gdb/gdbserver/linux-aarch64-low.c:134:38: error: invalid conversion from 'void*' to 'user_fpsimd_state*' [-fpermissive]
   struct user_fpsimd_state *regset = buf;
                                      ^
gdb/gdbserver/linux-aarch64-low.c: In function 'void aarch64_store_fpregset(regcache*, const void*)':
gdb/gdbserver/linux-aarch64-low.c:146:44: error: invalid conversion from 'const void*' to 'const user_fpsimd_state*' [-fpermissive]
   const struct user_fpsimd_state *regset = buf;
                                            ^
gdb/gdbserver:

2015-11-19  Yao Qi  <yao.qi@linaro.org>

	* linux-aarch64-low.c (aarch64_fill_fpregset): Cast buf to
	struct user_fpsimd_state *.
	(aarch64_store_fpregset): Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Change argument opcode type from enum aarch64_opcodes to uint32_t
@ 2015-11-19 14:34 sergiodj+buildbot
  2015-11-19 17:43 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-19 14:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 231c0592639d6f5c1796feb4a6375eab202a4acb ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 231c0592639d6f5c1796feb4a6375eab202a4acb

Change argument opcode type from enum aarch64_opcodes to uint32_t

The patch fixes the following errors in C++ build,

gdb/gdbserver/linux-aarch64-low.c: In function 'int emit_data_processing(uint32_t*, aarch64_opcodes, aarch64_register, aarch64_register, aarch64_operand)':
gdb/gdbserver/linux-aarch64-low.c:1071:52: error: invalid conversion from 'unsigned int' to 'aarch64_opcodes' [-fpermissive]
       return emit_data_processing_reg (buf, opcode | operand_opcode, rd,
                                                    ^
gdb/gdbserver:

2015-11-19  Yao Qi  <yao.qi@linaro.org>

	* linux-aarch64-low.c (emit_data_processing_reg): Change opcode
	type to uint32_t.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [AArch64] Reject invalid immediate operands to MSR PAN
@ 2015-11-19 14:46 sergiodj+buildbot
  2015-11-19 18:47 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-19 14:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c2825638b6784179f191c6ee8ebbda1c49ae5271 ***

Author: Matthew Wahab <matthew.wahab@arm.com>
Branch: master
Commit: c2825638b6784179f191c6ee8ebbda1c49ae5271

[AArch64] Reject invalid immediate operands to MSR PAN

The support for accessing the ARMv8.1 PSTATE field PAN allows
instructions of the form MSR PAN, #<imm> with <imm> any unsigned 4-bit
integer. However, the architecture specification requires that the
immediate is either 0 or 1.

This patch implements the constraint on the immediate, generating an
error if the immediate operand is invalid, and adds tests for the
illegal forms.

opcodes/
2015-11-19  Matthew Wahab  <matthew.wahab@arm.com>

	* aarch64-opc.c (operand_general_constraint_met_p): Check validity
	of MSR PAN immediate operand.

gas/testsuite/
2015-11-19  Matthew Wahab  <matthew.wahab@arm.com>

	* gas/aarch64/pan-illegal.d: New.
	* gas/aarch64/pan-illegal.l: New.
	* gas/aarch64/pan.s: Add tests for invalid immediates.

Change-Id: Ibb3056c975eb792104da138d94594224f56a993e


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [C++] Default to -Werror in C++ mode too
@ 2015-11-19 15:28 sergiodj+buildbot
  2015-11-20  0:57 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-19 15:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9a0847060d5823ec520ebf0c3e307e26442e5b8c ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 9a0847060d5823ec520ebf0c3e307e26442e5b8c

[C++] Default to -Werror in C++ mode too

Both x86_64 GNU/Linux and x86_64 mingw-w64 build cleanly with
--enable-targets=all.  This enables -Werror by default in C++ mode
too, in order to let the buildbot catch C++ build regressions for us.

gdb/ChangeLog:
2015-11-19  Pedro Alves  <palves@redhat.com>

	* configure.ac (ERROR_ON_WARNING): Don't check whether in C++
	mode.
	* configure: Regenerate.

gdb/gdbserver/ChangeLog:
2015-11-19  Pedro Alves  <palves@redhat.com>

	* configure.ac (ERROR_ON_WARNING): Don't check whether in C++
	mode.
	* configure: Regenerate.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] gdb: Workaround bad gdbserver qSupported:xmlRegisters=i386; UnknwnFeat+ handling
@ 2015-11-19 18:47 sergiodj+buildbot
  2015-11-20  4:01 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-19 18:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b35d5edb03798388d503d922d8f909a133bf93dd ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: b35d5edb03798388d503d922d8f909a133bf93dd

gdb: Workaround bad gdbserver qSupported:xmlRegisters=i386;UnknwnFeat+ handling

gdbserver's target_process_qsupported is called for each feature that
the gdbserver common code does not recognize.  The only current
implementation, for x86 Linux, does this:

  static void
  x86_linux_process_qsupported (const char *query)
  {
    /* Return if gdb doesn't support XML.  If gdb sends "xmlRegisters="
       with "i386" in qSupported query, it supports x86 XML target
       descriptions.  */
    use_xml = 0;
    if (query != NULL && startswith (query, "xmlRegisters="))
      {
	char *copy = xstrdup (query + 13);
	char *p;

	for (p = strtok (copy, ","); p != NULL; p = strtok (NULL, ","))
	  {
	    if (strcmp (p, "i386") == 0)
	      {
		use_xml = 1;
		break;
	      }
	  }

	free (copy);
      }

    x86_linux_update_xmltarget ();
  }

Notice that this clears use_xml and calls x86_linux_update_xmltarget
each time target_process_qsupported is called.  So if gdb sends in any
unknown feature after "xmlRegisters=i386", like e.g.,
"xmlRegisters=i386;UnknownFeature+" gdbserver ends up not reporting a
XML description...

Work around this by having GDB send the "xmlRegisters=" feature last.

gdb/ChangeLog:
2015-11-19  Pedro Alves  <palves@redhat.com>

	* remote.c (remote_query_supported): Send the "xmlRegisters="
	feature last.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] gdbserver: Fix qSupported:xmlRegisters=i386; UnknownFeature+ handling
@ 2015-11-19 18:55 sergiodj+buildbot
  2015-11-20  6:25 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-19 18:55 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 06e03fff313dfcc5f344280f8ac70b0ec8521f3a ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 06e03fff313dfcc5f344280f8ac70b0ec8521f3a

gdbserver: Fix qSupported:xmlRegisters=i386;UnknownFeature+ handling

The target_process_qsupported method is called for each qSupported
feature that the common code does not recognize.  The only current
implementation, for x86 Linux (x86_linux_process_qsupported), assumes
that it either is called with the "xmlRegisters=i386" feature, or that
it is isn't called at all, indicating the connected GDB predates x86
XML descriptions.

That's a bad assumption however.  If GDB sends in a new/unknown (to
core gdbserver) feature after "xmlRegisters=i386", say, something like
qSupported:xmlRegisters=i386;UnknownFeature+, then when
target_process_qsupported is called for "UnknownFeature+",
x86_linux_process_qsupported clears the 'use_xml' global and calls
x86_linux_update_xmltarget, and gdbserver ends up _not_ reporting a
XML description...

This commit changes the target_process_qsupported API to instead pass
down a vector of unprocessed qSupported features in one go.

(There's an early call to target_process_qsupported(NULL) that
indicates "starting qSupported processing".  There's no matching call
to mark the end of processing, though.  I first fixed this by passing
(char *)-1 to indicate that, and adjusted the x86 backend to only
clear 'use_xml' when qSupported processing starts, and then only call
x86_linux_update_xmltarget() when (char *)-1 was passed.  However, I
wasn't that happy with the hack and came up this alternative version.)

gdb/gdbserver/ChangeLog:
2015-11-19  Pedro Alves  <palves@redhat.com>

	* linux-low.c (linux_process_qsupported): Change prototype.
	Adjust.
	* linux-low.h (struct linux_target_ops) <process_qsupported>:
	Change prototype.
	* linux-x86-low.c (x86_linux_process_qsupported): Change prototype
	and adjust to loop over all features.
	* server.c (handle_query) <qSupported>: Adjust to call
	target_process_qsupported once, passing it a vector of unprocessed
	features.
	* target.h (struct target_ops) <process_qsupported>: Change
	prototype.
	(target_process_qsupported): Adjust.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
[parent not found: <915ef8b18e28e6418216a582067b9fbdd6395e6a@gdb-build>]
[parent not found: <c6d811243634c84e185a25faf33491ee1a5f900a@gdb-build>]
[parent not found: <bb82e93484cdd56c67efd52b869a6123b2623f6c@gdb-build>]
* [binutils-gdb] sparc: fix build of gdb/testsuite/gdb.arch/sparc-sysstep.c
@ 2015-11-20  9:53 sergiodj+buildbot
  2015-11-20 10:30 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-20  9:53 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9c88ed8f116dc5f9471280c73f9ab08c81a86f2d ***

Author: Jose E. Marchesi <jose.marchesi@oracle.com>
Branch: master
Commit: 9c88ed8f116dc5f9471280c73f9ab08c81a86f2d

sparc: fix build of gdb/testsuite/gdb.arch/sparc-sysstep.c

This patch adds a missing include that makes the test program to not
be built (--Wimplicit-function-declaration).

gdb/testsuite/ChangeLog:

2015-11-20  Jose E. Marchesi  <jose.marchesi@oracle.com>

    	* gdb.arch/sparc-sysstep.c: Include unistd.h for getpid.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] callfuncs.exp: avoid spurious register differences in sparc64 targets.
@ 2015-11-20 10:38 sergiodj+buildbot
  2015-11-20 11:44 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-20 10:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bb0974456ed6d421e8d0b257f1e108c242326afc ***

Author: Jose E. Marchesi <jose.marchesi@oracle.com>
Branch: master
Commit: bb0974456ed6d421e8d0b257f1e108c242326afc

callfuncs.exp: avoid spurious register differences in sparc64 targets.

The Linux kernel disables the FPU upon returning to userland.  This
introduces spurious failures in the register preservation tests in
callfuncs.exp, since the pstate.PEF bit gets cleared after system
calls.

This patch filters out the pstate register in sparc64-*-linux-gnu
targets, so the relevant tests are no longer fooled and pass.

gdb/testsuite/ChangeLog:

2015-11-20  Jose E. Marchesi  <jose.marchesi@oracle.com>

        * gdb.base/callfuncs.exp (fetch_all_registers): Filter out the
          pstate register when comparing registers values in
          sparc64-*-linux-gnu targets to avoid spurious differences.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Update translations.
@ 2015-11-20 12:50 sergiodj+buildbot
  2015-11-20 13:23 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-20 12:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f8c2a96547f690bb6308f1dbdf174679afd01b2b ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: f8c2a96547f690bb6308f1dbdf174679afd01b2b

Update translations.

binutils * po/ca.po: New Catalan translation.
	* configure.ac (ALL_LINGUAS): Add ca.
	* configure: Regenerate.

gas	* po/fr.po: Updated French translation.
	* po/uk.po: Updated Ukraninan translation.
	* po/zh_CN.po: New simplified Chinese translation.
	* configure.ac (ALL_LINGUAS): Add zh_CN.
	* configure: Regenerate.

opcodes	* po/zh_CN.po: Updated simplified Chinese translation.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Synchronize PDP11 page size between BFD and LD.
@ 2015-11-20 13:08 sergiodj+buildbot
  2015-11-20 14:31 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-20 13:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 11b8aeb88174dd67ff8b7c58377e8ef94ccf274e ***

Author: David Bridgham <dab@froghouse.org>
Branch: master
Commit: 11b8aeb88174dd67ff8b7c58377e8ef94ccf274e

Synchronize PDP11 page size between BFD and LD.

	* pdp11.c (TARGET_PAGE_SIZE): Set to 256 to match definition in
	ld/emulparams/pdp11.sh.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix missing update in previous patch.
@ 2015-11-20 14:25 sergiodj+buildbot
  2015-11-20 16:45 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-20 14:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9b334a2ccd0ba00d67ae590b3bab470836f79269 ***

Author: Tristan Gingold <gingold@adacore.com>
Branch: master
Commit: 9b334a2ccd0ba00d67ae590b3bab470836f79269

Fix missing update in previous patch.

bfd/
	* mach-o-x86-64.c (x86_64_howto_table): Change name here too.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Remove a if-clause that is redundant because the same test has been performed earlier on.
@ 2015-11-20 15:13 sergiodj+buildbot
  2015-11-20 17:55 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-20 15:13 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a915c10f7f1cd8ed433554f05a7281995ae9a540 ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: a915c10f7f1cd8ed433554f05a7281995ae9a540

Remove a if-clause that is redundant because the same test has been performed earlier on.

	PR binutils/19224
	* h8300-dis.c (bfd_h8_disassemble): Remove redundant if clause.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix a problem with the maximum number of open files held in the cache when running on a 32-bit Solaris host.
@ 2015-11-20 15:38 sergiodj+buildbot
  2015-11-20 19:05 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-20 15:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0b1fa2880c60dcb97d15e5d96e5640f3672dae48 ***

Author: Stefan Teleman <stefan.teleman@oracle.com>
Branch: master
Commit: 0b1fa2880c60dcb97d15e5d96e5640f3672dae48

Fix a problem with the maximum number of open files held in the cache when running on a 32-bit Solaris host.

	PR ld/19260
	* cache.c (bfd_cache_max_open): Avoid using getrlimit on 32-bit
	Solaris as the result is unreliable.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [AArch64] Add support for ARMv8.1 Virtulization Host Extensions.
@ 2015-11-20 16:23 sergiodj+buildbot
  2015-11-20 20:29 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-20 16:23 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 250aafa4773feafd5ca0a61f270b1e901dcd8987 ***

Author: Matthew Wahab <matthew.wahab@arm.com>
Branch: master
Commit: 250aafa4773feafd5ca0a61f270b1e901dcd8987

[AArch64] Add support for ARMv8.1 Virtulization Host Extensions.

The ARMv8.1 architecture includes the Virtualization Host Extensions
which add a number of system registers. This patch adds support for
these system registers, making them available when -march=armv8.1-a is
selected.

include/opcode/
2015-11-20  Matthew Wahab  <matthew.wahab@arm.com>

	* aarch64.h (AARCH64_FEATURE_V8_1): New.
	(AARCH64_ARCH_v8_1): Add AARCH64_FEATURE_V8_1.

opcodes/
2015-11-20  Matthew Wahab  <matthew.wahab@arm.com>

	* aarch64-opc.c (aarch64_sys_regs): Add spsr_el12, elr_el12,
	sctlr_el12, cpacr_el12, ttbr1_el2, ttbr0_el12, ttbr1_el12,
	tcr_el12, afsr0_el12, afsr1_el12, esr_el12, far_el12, mair_el12,
	amair_el12, vbar_el12, contextidr_el2, contextidr_el12,
	cntkctl_el12, cntp_tval_el02, cntp_ctl_el02, cntp_cval_el02,
	cntv_tval_el02, cntv_ctl_el02, cntv_cval_el02, cnthv_tval_el2,
	cnthv_ctl_el2, cnthv_cval_el2.
	(aarch64_sys_reg_supported_p): Update for the new system
	registers.

gas/testsuite/
2015-11-20  Matthew Wahab  <matthew.wahab@arm.com>

	* gas/aarch64/virthostext-directive.d: New.
	* gas/aarch64/virthostext.d: New.
	* gas/aarch64/virthostext.s: New.

Change-Id: Iecb370591b1b6e9e00d81c8ccd9ae3b0f71794a2


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] sim: mn10300: drop global callback handle
@ 2015-11-22  6:11 sergiodj+buildbot
  2015-11-22  6:42 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-22  6:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d320201dbe5a3677e96008738cb6cc754147e3bd ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: d320201dbe5a3677e96008738cb6cc754147e3bd

sim: mn10300: drop global callback handle

It's used in one place and can easily be replaced by using the sim state.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] sim: h8300: delete global callback/kind/name
@ 2015-11-22  6:19 sergiodj+buildbot
  2015-11-22  7:41 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-22  6:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c1fc4b4d17ee89a2f3d1a2b23eb84ffdc02ada2f ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: c1fc4b4d17ee89a2f3d1a2b23eb84ffdc02ada2f

sim: h8300: delete global callback/kind/name

We can use the sim state everywhere now to get these values on the fly.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] sim: avr: switch to common sim-reg
@ 2015-11-22  6:40 sergiodj+buildbot
  2015-11-22  9:46 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-22  6:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 807eaf04cb4ba3c1e5529069ac78af6d9969a5b0 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 807eaf04cb4ba3c1e5529069ac78af6d9969a5b0

sim: avr: switch to common sim-reg

This is not entirely useful as avr doesn't (yet) store its register
state in the cpu state, but it does allow for switching to the common
code for these functions.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] sim: common: add PRI printf defines
@ 2015-11-22  6:50 sergiodj+buildbot
  2015-11-22 11:53 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-22  6:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 37258e9950490293bb00808a55d82dea640efe6c ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 37258e9950490293bb00808a55d82dea640efe6c

sim: common: add PRI printf defines

Keeping track of the right printf formats for the various types can be
a pretty big hassle, especially in common code which has to support a
variety of bitsizes.  Take a page from the existing standards and add
a set of PRI macros which hide the details in a common header.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] sim: sh: delete global callback/argv
@ 2015-11-22  7:00 sergiodj+buildbot
  2015-11-22  8:48 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-22  7:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6cc98856315993e8723fc2c6a2baabd8dc7fd360 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 6cc98856315993e8723fc2c6a2baabd8dc7fd360

sim: sh: delete global callback/argv

We can use the sim state everywhere now to get these values on the fly.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] sim: ppc: avoid use of $< in ordinary rules [PR sim/13834]
@ 2015-11-22  7:11 sergiodj+buildbot
  2015-11-22 12:48 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-22  7:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7c125e3b10ac6f9222d24c76cdf31a5a9ec8dae0 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 7c125e3b10ac6f9222d24c76cdf31a5a9ec8dae0

sim: ppc: avoid use of $< in ordinary rules [PR sim/13834]

POSIX does not define $< behavior in ordinary rules, so avoid its use
to fix building on non-GNU make setups.

Reported-by: Christopher January <chris.january@allinea.com>


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] sim: common: set up CPPFLAGS/CXXFLAGS/LDFLAGS from configure [PR sim/18762]
@ 2015-11-22  8:08 sergiodj+buildbot
  2015-11-22 14:57 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-22  8:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT dc11500a11e5ef1068182886007fccd4d7ad1c70 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: dc11500a11e5ef1068182886007fccd4d7ad1c70

sim: common: set up CPPFLAGS/CXXFLAGS/LDFLAGS from configure [PR sim/18762]

Make sure we pass down the CPP/CXX/LD flags that configure set up for us
like we already do for C flags.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] darwin-nat: rewrite darwin_read_write_inferior
@ 2015-11-23 10:41 sergiodj+buildbot
  2015-11-23 11:15 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-23 10:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3eb831e0ca5aa3035845fc039c58c6340fd51c31 ***

Author: Tristan Gingold <tristan.gingold@adacore.com>
Branch: master
Commit: 3eb831e0ca5aa3035845fc039c58c6340fd51c31

darwin-nat: rewrite darwin_read_write_inferior

This is a little bit more efficient.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] solib-darwin: support PIE for spawned processes.
@ 2015-11-23 14:05 sergiodj+buildbot
  2015-11-23 14:39 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-23 14:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ad2073b0b48e23028ca9b4d348970690d4501933 ***

Author: Tristan Gingold <gingold@adacore.com>
Branch: master
Commit: ad2073b0b48e23028ca9b4d348970690d4501933

solib-darwin: support PIE for spawned processes.

solib-darwin is now able to read the load address of the executable
before any inferior execution.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] darwin-nat: disable sstep cache.
@ 2015-11-23 14:42 sergiodj+buildbot
  2015-11-23 15:37 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-23 14:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT aa14fb50785c8ac8be5fbb148d7cdd88fcf8f896 ***

Author: Tristan Gingold <gingold@adacore.com>
Branch: master
Commit: aa14fb50785c8ac8be5fbb148d7cdd88fcf8f896

darwin-nat: disable sstep cache.

Was not reliable after inferior call.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] opcodes: handle mach-o for thumb/arm disambiguation.
@ 2015-11-23 14:59 sergiodj+buildbot
  2015-11-23 16:44 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-23 14:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e49d43ff73a309548dd2b576bb7b602f62be66d6 ***

Author: Tristan Gingold <gingold@adacore.com>
Branch: master
Commit: e49d43ff73a309548dd2b576bb7b602f62be66d6

opcodes: handle mach-o for thumb/arm disambiguation.

opcodes/
	* arm-dis.c (print_insn): Also set is_thumb for Mach-O.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] gdb/dwarf2read: Minimal handling of non-constant struct sizes.
@ 2015-11-23 17:53 sergiodj+buildbot
  2015-11-23 18:23 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-23 17:53 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 155bfbd30aacd4e01a9ac8ca8032d804ed7ece47 ***

Author: Joel Brobecker <brobecker@adacore.com>
Branch: master
Commit: 155bfbd30aacd4e01a9ac8ca8032d804ed7ece47

gdb/dwarf2read: Minimal handling of non-constant struct sizes.

Using the gdb.ada/var_rec_arr.exp test, where the program declares
an array of variant records...

   type Record_Type (I : Small_Type := 0) is record
      S : String (1 .. I);
   end record;
   type Array_Type is array (Integer range <>) of Record_Type;

... and then a variable A1 of type Array_Type, the following command
ocassionally trigger an internal error trying to allocate more memory
than we have left:

    (gdb) ptype a1(1)
    [...]/utils.c:1089: internal-error: virtual memory exhausted.
    A problem internal to GDB has been detected,
    [...]

What happens is that recent versions of GNAT are able to generate
DWARF expressions for type Record_Type, and therefore the record's
DW_AT_byte_size is not a constant, which unfortunately breaks
an assumption made by dwarf2read.c:read_structure_type when it does:

   attr = dwarf2_attr (die, DW_AT_byte_size, cu);
   if (attr)
     {
       TYPE_LENGTH (type) = DW_UNSND (attr);
     }

As a result of this, when ada_evaluate_subexp tries to create
a value_zero for a1(1) while processing the OP_FUNCALL operator
as part of evaluating the subscripting operation in no-side-effect
mode, we try to allocate a value with a bogus size, potentially
triggering the out-of-memory internal error.

This patch avoids this issue by setting the length to zero in
this case.  Until we decide to start supporting dynamic type
lengths in GDB's type struct, and it's not clear yet that
this is worth the effort (see added comment), that's probably
the best we can do.

gdb/ChangeLog:

        * dwarf2read.c (read_structure_type): Set the type's length
        to zero if it has a DW_AT_byte_size attribute which is not
        a constant.

gdb/testsuite/ChangeLog:

        * testsuite/gdb.ada/var_rec_arr.exp: Add "ptype a1(1)" test.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [ARM] "svc" insn check at irrelevant address in ARM unwind info sniffer
@ 2015-11-23 18:09 sergiodj+buildbot
  2015-11-23 20:28 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-23 18:09 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 416dc9c6e9acd57255015d255799ac031a262182 ***

Author: Joel Brobecker <brobecker@adacore.com>
Branch: master
Commit: 416dc9c6e9acd57255015d255799ac031a262182

[ARM] "svc" insn check at irrelevant address in ARM unwind info sniffer

The following issue has been observed on arm-android, trying to step
over the following line of code:

        Put_Line (">>> " & Integer'Image (Message (I)));

Below is a copy of the GDB transcript:

    (gdb) cont
    Breakpoint 1, q.dump (message=...) at q.adb:11
    11               Put_Line (">>> " & Integer'Image (Message (I)));
    (gdb) next
    0x00016000 in system.concat_2.str_concat_2 ()

The expected behavior for the "next" command is to step over
the call to Put_Line and stop at line 12:

    (gdb) next
    12               I := I + 1;

What happens during the next step is that the code for line 11
above make a call to system.concat_2.str_concat_2 (to implement
the '&' string concatenation operator) before making the call
to Put_Line. While stepping, GDB stops eventually stops at the
first instruction of that function, and fails to detect that
it's a function call from where we were before, and so decides
to stop stepping.

And the reason why it fails to detect that we landed inside a function
call is because it fails to unwind from that function:

    (gdb) bt
    #0  0x00016000 in system.concat_2.str_concat_2 ()
    #1  0x0001bc74 in ?? ()

Debugging GDB, I found that GDB decides to use the ARM unwind info
for that function, which contains the following data:

    0x16000 <system__concat_2__str_concat_2>: 0x80acb0b0
      Compact model index: 0
      0xac      pop {r4, r5, r6, r7, r8, r14}
      0xb0      finish
      0xb0      finish

But, in fact, using that data is wrong, in this case, because
it mentions a pop of 6 registers, and therefore hints at a frame
size of 24 bytes. The problem is that, because we're at the first
instruction of the function, the 6 registers haven't been pushed
to the stack yet. In other words, using the ARM unwind entry above,
GDB is tricked into thinking that the frame size is 24 bytes, and
that the return address (r14) is available on the stack.

One visible manifestation of this issue can been seen by looking
at the value of the stack pointer, and the frame's base address:

    (gdb) p /x $sp
    $2 = 0xbee427b0
    (gdb) info frame
    Stack level 0, frame at 0xbee427c8:
                            ^^^^^^^^^^
                            ||||||||||

The frame's base address should be equal to the value of the stack
pointer at entry. And you eventually get the correct frame address,
as well as the correct backtrace if you just single-step one additional
instruction, past the push:

    (gdb) x /i $pc
    => 0x16000 <system__concat_2__str_concat_2>:
        push        {r4, r5, r6, r7, r8, lr}
    (gdb) stepi
    (gdb) bt
    #0  0x00016004 in system.concat_2.str_concat_2 ()
    #1  0x00012b6c in q.dump (message=...) at q.adb:11
    #2  0x00012c3c in q () at q.adb:19

Digging further, I found that GDB tries to use the ARM unwind info
only when sure that it is relevant, as explained in the following
comment:

  /* The ARM exception table does not describe unwind information
     for arbitrary PC values, but is guaranteed to be correct only
     at call sites.  We have to decide here whether we want to use
     ARM exception table information for this frame, or fall back [...]

There is one case where it decides that the info is relevant,
described in the following comment:

      /* We also assume exception information is valid if we're currently
         blocked in a system call.  The system library is supposed to
         ensure this, so that e.g. pthread cancellation works.

For that, it just parses the instruction at the address it believes
to be the point of call, and matches it against an "svc" instruction.
For instance, for a non-thumb instruction, it is at...

    get_frame_pc (this_frame) - 4

... and the code checking looks like the following.

              if (safe_read_memory_integer (get_frame_pc (this_frame) - 4, 4,
                                            byte_order_for_code, &insn)
                  && (insn & 0x0f000000) == 0x0f000000 /* svc */)
                exc_valid = 1;

However, the reason why this doesn't work in our case is that
because we are at the first instruction of a function in the innermost
frame. That frame can't possibly be making a call, and therefore
be stuck on a system call.

What the code above ends up doing is checking the instruction
just before the start of our function, which in our case is not
even an actual instruction, but unlucky for us, happens to match
the pattern it is looking for, thus leading GDB to improperly
trust the ARM unwinding data.

gdb/ChangeLog:

        * arm-tdep.c (arm_exidx_unwind_sniffer): Do not check for a frame
        stuck on a system call if the given frame is the innermost frame.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [LynxOS] GDBserver crash debugging threaded program
@ 2015-11-23 18:24 sergiodj+buildbot
  2015-11-23 22:37 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-23 18:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 80d82c196402f6a61aa84452104b9aaed364eb42 ***

Author: Joel Brobecker <brobecker@adacore.com>
Branch: master
Commit: 80d82c196402f6a61aa84452104b9aaed364eb42

[LynxOS] GDBserver crash debugging threaded program

This crash is observable by debugging a threaded program on LynxOS.
On the GDB side, this is what we would see:

    % gdb q
    (gdb) target remote machine:4444
    (gdb) break q.adb:6
    (gdb) cont
    [gdb hits breakpoint]
    (gdb) cont
    Remote connection closed    <<<--- expected: [Inferior 1 (Remote target) exited normally]

On the gdbserver side, which was launched as usual:

    % gdbserver --once :4444 q
    Segmentation fault (core dumped)

Ooops!

The problem happens while GDB is trying to handle the thread termination
event of the thread that hit the breakpoint. It started happening after
the following change was made:

    commit 96e7a1eb6d09fda9e22e112e35e7d0085a8f4fd0
    Date:   Fri Oct 16 11:08:38 2015 -0400
    Subject: gdbserver: Reset current_thread when the thread is removed.

    Reset current_thread and make sure 'remove_process' is used
    after all associated threads have been removed first.

More precisely:

  . GDBserver receives the execution-resume order;

  . lynx-low resumes it succesfully, and then relies on lynx_wait_1
    to wait for the next event;

  . We quickly receive one, which lynx_wait_1 analyzes to be
    a "thread exit" event, and therefore does...

          case SIGTHREADEXIT:
            remove_thread (find_thread_ptid (new_ptid));
            lynx_continue (new_ptid);
            goto retry;

    => remove_thread causes current_thread to be set to NULL...
       (that's the recent change mentioned above)

    => ... which causes problems during lynx_continue, because
       it calls lynx_resume, which calls regcache_invalidate,
       which unfortunately assumes that CURRENT_THREAD is not NULL:

        void
        regcache_invalidate (void)
        {
          /* Only update the threads of the current process.  */
SEGV!-->  int pid = ptid_get_pid (current_thread->entry.id);

          find_inferior (&all_threads, regcache_invalidate_one, &pid);
        }

Since the problem at hand is caused by trying to figure out which
inferior to reset the regcache for, and since lynx_resume actually
had that info, this patch fixes the problem by introducing a new
routine called regcache_invalidate_pid, which invalidates the cache
of the given pid; and then modifies lynx_resume use that new routine
rather than relying on regcache_invalidate to invalidate the regcache
of the expected inferior.

gdb/gdbserver/ChangeLog:

        * regcache.h (regcache_invalidate_pid): Add declaration.
        * regcache.c (regcache_invalidate_pid): New function, extracted
        from regcache_invalidate.
        (regcache_invalidate): Reimplement using regcache_invalidate_pid.
        Add trivial documentation comment.
        * lynx-low.c: Use regcache_invalidate_pid instead of
        regcache_invalidate.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] error/internal-error printing local variable during "bt full".
@ 2015-11-23 19:54 sergiodj+buildbot
  2015-11-23 23:38 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-23 19:54 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 16c3b12f199a7ec99a0b51bd83b66942547bba87 ***

Author: Joel Brobecker <brobecker@adacore.com>
Branch: master
Commit: 16c3b12f199a7ec99a0b51bd83b66942547bba87

error/internal-error printing local variable during "bt full".

One of our users reported an internal error using the "bt full"
command. In their situation, reproducing involved the following
scenario:

    (gdb) frame 1
    (gdb) bt full
    #0  0xf7783430 in __kernel_vsyscall ()
    No symbol table info available.
    #1  0xf5550aeb in waitpid () at ../sysdeps/unix/syscall-template.S:81
    No locals.
    [...]
    #6  0x0fe83139 in xxxx (arg=...)
    [...some locals printed, and then...]
    <S17b> =
    [...]/dwarf2loc.c:364: internal-error: dwarf_expr_frame_base: Assertion
    `framefunc != NULL' failed.

As shown above, the error happens while GDB is trying to print the value
of <S17b>, which is a local string internally generated by the compiler.
For that, it finds that the array lives in memory, and therefore tries
to create a struct value for it via:

        case DWARF_VALUE_MEMORY:
          {
            CORE_ADDR address = dwarf_expr_fetch_address (ctx, 0);
            [...]
            retval = value_at_lazy (type, address + byte_offset);

Unfortunately for us, TYPE happens to be an array whose bounds
are dynamic. More precisely, the bounds of our arrays are described
in the debugging info as being...

 <4><2c1985e>: Abbrev Number: 33 (DW_TAG_subrange_type)
    <2c1985f>   DW_AT_type        : <0x2c1989c>
    <2c19863>   DW_AT_lower_bound : <0x2c19835>
    <2c19867>   DW_AT_upper_bound : <0x2c19841>

... which are references to a pair of local variables. For instance,
the lower bound is a reference to the following DIE

 <3><2c19835>: Abbrev Number: 32 (DW_TAG_variable)
    <2c19836>   DW_AT_name        : [...]
    <2c1983a>   DW_AT_type        : <0x2c198b4>
    <2c1983e>   DW_AT_artificial  : 1
    <2c1983e>   DW_AT_location    : 2 byte block: 91 58         (DW_OP_fbreg: -40)

As a result of the above, value_at_lazy indirectly triggers
a resolution of TYPE (via value_from_contents_and_address),
which means a resolution of TYPE's bounds, and as seen in
the DW_AT_location attribute above for our bounds, computing
the bound's location requires the frame (its location expression
uses DW_OP_fbreg).

Unfortunately for us, value_at_lazy does not get passed a frame,
we've lost the relevant frame when we try to resolve the array's
bounds. Instead, resolve_dynamic_range gets calls dwarf2_evaluate_property
with NULL as the frame:

    static struct type *
    resolve_dynamic_range (struct type *dyn_range_type,
                           struct property_addr_info *addr_stack)
    {
      [...]
      if (dwarf2_evaluate_property (prop, NULL, addr_stack, &value))
                                          ^^^^

... which then handles this by using the selected frame instead:

    if (frame == NULL && has_stack_frames ())
      frame = get_selected_frame (NULL);

In our case, the selected frame happens to be frame #1, which is
a frame where we have a minimal amount of debugging info, and in
particular, no debug info for the function itself. And because of that,
when we try to determine the frame's base...

    static void
    dwarf_expr_frame_base (void *baton, const gdb_byte **start,
                           size_t * length)
    {
      struct dwarf_expr_baton *debaton = (struct dwarf_expr_baton *) baton;
      const struct block *bl = get_frame_block (debaton->frame, NULL);
      [...]
      framefunc = block_linkage_function (bl);

... framefunc ends up being NULL, which triggers the assert
in that same function:

      gdb_assert (framefunc != NULL);

This patches avoids the issue by temporarily setting the selected_frame
before printing the locals of each frames.

This patch also adds a small testcase, which reproduces the same
issue, but with a slightly different outcome:

    (gdb) bt full
    #0  0x000000000040049a in opaque_routine ()
    No symbol table info available.
    #1  0x0000000000400532 in main () at wrong_frame_bt_full-main.c:20
            my_table_size = 3
            my_table = <error reading variable my_table (frame address is not available.)>

With this patch, the output becomes:

    (gdb) bt full
    [...]
            my_table = {0, 1, 2}

gdb/ChangeLog:

        * stack.c (print_frame_local_vars): Temporarily set the selected
        frame to FRAME while printing the frame's local variables.

gdb/testsuite/ChangeLog:

        * gdb.base/wrong_frame_bt_full-main.c: New file.
        * gdb.base/wrong_frame_bt_full-opaque.c: New file.
        * gdb.base/wrong_frame_bt_full.exp: New file.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] minsyms.c: Scan backwards over all zero sized symbols.
@ 2015-11-23 23:05 sergiodj+buildbot
  2015-11-24  0:29 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-23 23:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5506f9f67ec105b0059a0b3a66fbde82cb5a0a15 ***

Author: Kevin Buettner <kevinb@redhat.com>
Branch: master
Commit: 5506f9f67ec105b0059a0b3a66fbde82cb5a0a15

minsyms.c: Scan backwards over all zero sized symbols.

The comment for the code in question says:

		  /* If the minimal symbol has a zero size, save it
		     but keep scanning backwards looking for one with
		     a non-zero size.  A zero size may mean that the
		     symbol isn't an object or function (e.g. a
		     label), or it may just mean that the size was not
		     specified.  */

As written, the code in question will only scan past the first symbol
of zero size.  My change fixes the implementation to match the
comment.

Having this correct is important when the compiler generates several
local labels that are left in place by the linker.  (I've been told
that the linker should eliminate these symbols, but I know of one
architecture for which this is not happening.)

I've created a test case called asmlabel.c.  It's pretty simple:

main (int argc, char **argv)
{
  asm ("L0:");
  v = 0;
  asm ("L1:");
  v = 1;		/* set L1 breakpoint here */
  asm ("L2:");
  v = 2;		/* set L2 breakpoint here */
  return 0;
}

If breakpoints are placed on the lines indicated by the comments,
this is the behavior of GDB built without my patch:

    (gdb) continue
    Continuing.

    Breakpoint 2, L1 () at asmlabel.c:26
    26	  v = 1;		/* set L1 breakpoint here */

Note that L1 appears as the function instead of main.  This is not
what we want to happen.  With my patch in place, we see the desired
behavior instead:

    (gdb) continue
    Continuing.

    Breakpoint 2, main (argc=1, argv=0x7fffffffdb88) at asmlabel.c:26
    26	  v = 1;		/* set L1 breakpoint here */

gdb/ChangeLog:

	* minsyms.c (lookup_minimal_symbol_by_pc_section_1): Scan backwards
	over all zero-sized symbols.

gdb/testsuite/ChangeLog:

	* gdb.base/asmlabel.exp: New test.
	* gdb.base/asmlabel.c: New test case.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Refactor gdb.trace/save-trace.exp
@ 2015-11-24  0:05 sergiodj+buildbot
  2015-11-24  1:37 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-24  0:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 045ccf910b4345a1cfa9f3d3af20ae4d8d1defa2 ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: 045ccf910b4345a1cfa9f3d3af20ae4d8d1defa2

Refactor gdb.trace/save-trace.exp

Some code is duplicated, to run the test twice with absolute and
relative paths, so I factored it out in a few procs.  It uses
with_test_prefix to differentiate between test runs.

I replaced usages of "save-tracepoints" with "save tracepoint", since
the former is deprecated.

I also removed the "10.x", as it doesn't make much sense anymore.  It
isn't used in general in the testsuite, and I don't think it's really
useful.

gdb/testsuite/ChangeLog:

	* save-trace.exp: Factor out code to these...
	(gdb_save_tracepoints): New.
	(gdb_load_tracepoints): New.
	(do_save_load_test): New.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Add an AArch64 simulator to GDB.
@ 2015-11-24  8:59 sergiodj+buildbot
  2015-11-24  9:35 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-24  8:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2e8cf49e1387eba9c4ce062885b99a6eb76c01f8 ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: 2e8cf49e1387eba9c4ce062885b99a6eb76c01f8

Add an AArch64 simulator to GDB.

sim	* configure.tgt: Add aarch64 entry.
	* configure: Regenerate.
	* sim/aarch64/configure.ac: New configure template.
	* sim/aarch64/aclocal.m4: Generate.
	* sim/aarch64/config.in: Generate.
	* sim/aarch64/configure: Generate.
	* sim/aarch64/cpustate.c: New file - functions for accessing
	AArch64 registers.
	* sim/aarch64/cpustate.h: New header.
	* sim/aarch64/decode.h: New header.
	* sim/aarch64/interp.c: New file - interface between GDB and
	simulator.
	* sim/aarch64/Makefile.in: New makefile template.
	* sim/aarch64/memory.c: New file - functions for simulating
	aarch64 memory accesses.
	* sim/aarch64/memory.h: New header.
	* sim/aarch64/sim-main.h: New header.
	* sim/aarch64/simulator.c: New file - aarch64 simulator
	functions.
	* sim/aarch64/simulator.h: New header.

include/gdb * sim-aarch64.h: New file.

sim/test * configure: Regenerate.
	* sim/aarch64: New directory.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Make gdb.python/py-inferior.exp test names unique
@ 2015-11-24 18:51 sergiodj+buildbot
  2015-11-24 19:21 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-24 18:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2cc57ad8d14499775e4b9de4a3ffaf73ac728781 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 2cc57ad8d14499775e4b9de4a3ffaf73ac728781

Make gdb.python/py-inferior.exp test names unique

Before we had:

      $ cat testsuite/gdb.sum | grep "PASS" | sort | uniq -c | sort -n
      ...
      1 PASS: gdb.python/py-inferior.exp: write str
      2 PASS: gdb.python/py-inferior.exp: Get inferior list length
      2 PASS: gdb.python/py-inferior.exp: py start_addr = gdb.selected_frame ().read_var ('search_buf')
      2 PASS: gdb.python/py-inferior.exp: Switch to first inferior
      3 PASS: gdb.python/py-inferior.exp: find mixed-sized pattern
      4 PASS: gdb.python/py-inferior.exp: py length = search_buf.type.sizeof
      4 PASS: gdb.python/py-inferior.exp: py start_addr = search_buf.address
      5 PASS: gdb.python/py-inferior.exp: Check inferior validity
      $

gdb/testsuite/ChangeLog:
2015-11-24  Pedro Alves  <palves@redhat.com>

	* gdb.python/py-inferior.exp: Use with_test_prefix.  Consistently
	use lowercase.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Linux: dump the signalled thread first
@ 2015-11-24 18:58 sergiodj+buildbot
  2015-11-24 20:20 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-24 18:58 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 050c224b67b0cb62a5620d294997254d5b6675f9 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 050c224b67b0cb62a5620d294997254d5b6675f9

Linux: dump the signalled thread first

... like the kernel does.

gcore-thread.exp has a check to make sure the signalled thread is the
current thread after loading the core back, but that just works by
accident, because the signalled thread happened to be the last thread
on the thread list, and gdb currently iterates over threads in reverse
order.

So this fixes gcore-thread.exp once we start walking threads in
ascending number.

gdb/ChangeLog:
2015-11-24  Pedro Alves  <palves@redhat.com>

	* linux-tdep.c (find_stop_signal): Delete.
	(struct linux_corefile_thread_data) <pid>: Remove field.
	(linux_corefile_thread_callback): Rename to ...
	(linux_corefile_thread): ... this.  Now takes a struct
	linux_corefile_thread_data pointer rather than a void pointer.
	Remove thread state and thread pid checks.
	(linux_make_corefile_notes): Prefer dumping the signalled thread
	first.  Use ALL_NON_EXITED_THREADS instead of
	iterate_over_threads.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] List checkpoints in ascending order
@ 2015-11-24 19:13 sergiodj+buildbot
  2015-11-24 22:20 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-24 19:13 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2f341b6e28e27fadd8160d95337c3aa854bcba3b ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 2f341b6e28e27fadd8160d95337c3aa854bcba3b

List checkpoints in ascending order

Before:
     (gdb) info checkpoints
       3 process 29132 at 0x4008ad, file foo.c, line 81
       2 process 29131 at 0x4008ad, file foo.c, line 81
       1 process 29130 at 0x4008ad, file foo.c, line 81
     * 0 Thread 0x7ffff7fc5740 (LWP 29128) (main process) at 0x4008ad, file foo.c, line 81

After:
     (gdb) info checkpoints
     * 0 Thread 0x7ffff7fc5740 (LWP 29128) (main process) at 0x4008ad, file foo.c, line 81
       1 process 29130 at 0x4008ad, file foo.c, line 81
       2 process 29131 at 0x4008ad, file foo.c, line 81
       3 process 29132 at 0x4008ad, file foo.c, line 81

gdb/ChangeLog:
2015-11-24  Pedro Alves  <palves@redhat.com>

	PR 17539
        * printcmd.c (display_command): Append new display at the end of
        the list.

gdb/testsuite/ChangeLog:
2015-11-24  Pedro Alves  <palves@redhat.com>

	PR 17539
        * gdb.base/display.exp: Expect displays to be sorted in ascending
        order.  Use multi_line.
        * gdb.base/solib-display.exp: Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] List displays in ascending order
@ 2015-11-24 19:21 sergiodj+buildbot
  2015-11-24 23:22 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-24 19:21 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 62147a2265e322c758743edf13a1377fdcb62479 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 62147a2265e322c758743edf13a1377fdcb62479

List displays in ascending order

Before:
      (gdb) info display
      Auto-display expressions now in effect:
      Num Enb Expression
      3:   y  1
      2:   y  1
      1:   y  1

After:
      (gdb) info display
      Auto-display expressions now in effect:
      Num Enb Expression
      1:   y  1
      2:   y  1
      3:   y  1

gdb/ChangeLog:
2015-11-24  Pedro Alves  <palves@redhat.com>

	PR 17539
	* printcmd.c (display_command): Append new display at the end of
	the list.

gdb/testsuite/ChangeLog:
2015-11-24  Pedro Alves  <palves@redhat.com>

	PR 17539
	* gdb.base/display.exp: Expect displays to be sorted in ascending
	order.  Use multi_line.
	* gdb.base/solib-display.exp: Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] btrace: diagnose "record btrace pt" without libipt
@ 2015-11-26 10:35 sergiodj+buildbot
  2015-11-26 11:09 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-26 10:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 46a3515b49ce30315e2b621525b29cd8263aed15 ***

Author: Markus Metzger <markus.t.metzger@intel.com>
Branch: master
Commit: 46a3515b49ce30315e2b621525b29cd8263aed15

btrace: diagnose "record btrace pt" without libipt

If GDB has been configured without libipt support, i.e. HAVE_LIBIPT is
undefined, and is running on a system that supports Intel(R) Processor Trace,
GDB will run into an internal error when trying to decode the trace.

    (gdb) record btrace
    (gdb) s
    usage (name=0x7fffffffe954 "fib-64")
        at src/fib.c:12
    12          fprintf(stderr, "usage: %s <num>\n", name);
    (gdb) info record
    Active record target: record-btrace
    Recording format: Intel(R) Processor Trace.
    Buffer size: 16kB.
    gdb/btrace.c:971: internal-error: Unexpected branch trace format.
    A problem internal to GDB has been detected,
    further debugging may prove unreliable.
    Quit this debugging session? (y or n)

This requires a system with Linux kernel 4.1 or later running on a 5th
Generation Intel Core processor or later.

The issue is documented as PR 19297.

When trying to enable branch tracing, in addition to checking the target
support for the requested branch tracing format, also check whether GDB
supports. it.

gdb/
	* btrace.c (btrace_enable): Check whether HAVE_LIBIPT is defined.

testsuite/
	* lib/gdb.exp (skip_btrace_pt_tests): Check for a "GDB does not
	support" error.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Display names of remote threads
@ 2015-11-26 16:04 sergiodj+buildbot
  2015-11-26 17:41 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-26 16:04 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 79efa585c51f0657b319beb1e213d5721eaacdcc ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: 79efa585c51f0657b319beb1e213d5721eaacdcc

Display names of remote threads

This patch adds support for thread names in the remote protocol, and
updates gdb/gdbserver to use it.  The information is added to the XML
description sent in response to the qXfer:threads:read packet.

gdb/ChangeLog:

	* linux-nat.c (linux_nat_thread_name): Replace implementation by call
	to linux_proc_tid_get_name.
	* nat/linux-procfs.c (linux_proc_tid_get_name): New function,
	implementation inspired by linux_nat_thread_name.
	* nat/linux-procfs.h (linux_proc_tid_get_name): New declaration.
	* remote.c (struct private_thread_info) <name>: New field.
	(free_private_thread_info): Free name field.
	(remote_thread_name): New function.
	(thread_item_t) <name>: New field.
	(clear_threads_listing_context): Free name field.
	(start_thread): Get name xml attribute.
	(thread_attributes): Add "name" attribute.
	(remote_update_thread_list): Copy name field.
	(init_remote_ops): Assign remote_thread_name callback.
	* target.h (target_thread_name): Update comment.
	* NEWS: Mention remote thread name support.

gdb/gdbserver/ChangeLog:

	* linux-low.c (linux_target_ops): Use linux_proc_tid_get_name.
	* server.c (handle_qxfer_threads_worker): Refactor to include thread
	name in reply.
	* target.h (struct target_ops) <thread_name>: New field.
	(target_thread_name): New macro.

gdb/doc/ChangeLog:

	* gdb.texinfo (Thread List Format): Mention thread names.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Add test for thread names
@ 2015-11-26 18:28 sergiodj+buildbot
  2015-11-26 19:06 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-26 18:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f6512a69cd414a31e302daf107f5959ef06bcbec ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: f6512a69cd414a31e302daf107f5959ef06bcbec

Add test for thread names

I couldn't find a test that verified the thread name functionality, so I
created a new one.

A target board can define gdb,no_thread_names if it doesn't support thread
names and wants to skip the tests that uses them.

This test has been made with Linux in mind.  Not all platforms use
pthread_setname_np to set the thread name, but some #ifdefs can be added
later in order to support other platforms.

Tested on x86-64 Ubuntu 14.04, native and remote.

gdb/testsuite/ChangeLog:

	* gdb.threads/names.exp: New file.
	* gdb.threads/names.c: New file.
	* README: Mention gdb,no_thread_names.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [AArch64] Add feature flags and command line for ARMv8.2 FP16 support.
@ 2015-11-27 13:32 sergiodj+buildbot
  2015-11-27 14:07 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-27 13:32 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 870181955b565b4fbbf4efcbec4a43d687703d1a ***

Author: Matthew Wahab <matthew.wahab@arm.com>
Branch: master
Commit: 870181955b565b4fbbf4efcbec4a43d687703d1a

[AArch64] Add feature flags and command line for ARMv8.2 FP16 support.

ARMv8.2 adds optional support for 16-bit operations to the FP and
Adv.SIMD instructions. This patch adds a feature macro for this support
with a new command line option "+fp16" to enable/disable it.

Although the command line option is added as an architecture extension,
it only affects instructions available with when +fp or +simd is
enabled. If +fp16 is specified then it will also enable +fp.

There are currently no FP16 instructions implemented in binutils, this
patch is to enable subsequent work on supporting the extension.

gas/
2015-11-27  Matthew Wahab  <matthew.wahab@arm.com>

	* config/tc-aarch64.c (aarch64_features): Add "fp16".
	* doc/c-aarch64.texi (Architecture Extensions): Add "fp16".

include/opcode/
2015-11-27  Matthew Wahab  <matthew.wahab@arm.com>

	* aarch64.h (AARCH64_FEATURE_F16): New.
	(AARCH64_ARCH_V8_2): Add AARCH64_FEATURE_F16 to ARMv8.2
	features.

Change-Id: Id2021e0513946e16d0935c2a5b9605574cdff95a


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Use ${frames_invalid} in gdb.cp/annota2.exp
@ 2015-11-27 14:32 sergiodj+buildbot
  2015-11-27 16:04 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-27 14:32 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bfde72c275bff9d5be21cf51ba790cf38ecd0d59 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: bfde72c275bff9d5be21cf51ba790cf38ecd0d59

Use ${frames_invalid} in gdb.cp/annota2.exp

Variable frames_invalid was defined, but wasn't used much.  This patch
is to replace the literals in the regexp with ${frames_invalid}.

gdb/testsuite:

2015-11-27  Yao Qi  <yao.qi@linaro.org>

	* gdb.cp/annota2.exp: Use ${frames_invalid}.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [AArch64] Support gnu vector in inferior call
@ 2015-11-27 15:00 sergiodj+buildbot
  2015-11-27 19:07 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-27 15:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 238f2452e6d94f7b227a9d132f5ae887299d96c6 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 238f2452e6d94f7b227a9d132f5ae887299d96c6

[AArch64] Support gnu vector in inferior call

As defined in AArch64 AAPCS, short vectors are passed through V
registers, and its maximum alignment is 16-byte.  This patch is
to reflect these rules in GDB.  This patch fixes some fails in
gdb.base/gnu_vector.exp.

gdb:

2015-11-27  Yao Qi  <yao.qi@linaro.org>

	* aarch64-tdep.c (aarch64_type_align): For vector type, return
	its length, but with the maximum of 16 bytes.
	(is_hfa): Return zero for vector type.
	(aarch64_push_dummy_call): Handle short vectors.
	(aarch64_extract_return_value): Likewise.
	(aarch64_store_return_value): Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [AArch64] Handle HFA and HVA together
@ 2015-11-27 15:08 sergiodj+buildbot
  2015-11-27 20:12 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-27 15:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cd635f74a3b71043d35501db31b3acac956018cd ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: cd635f74a3b71043d35501db31b3acac956018cd

[AArch64] Handle HFA and HVA together

AArch64 AAPCS defined HFA (homogeneous floating-point aggregate)
and HVF (homogeneous short vector aggregate), bug GDB only handles the
former.  In the AAPCS doc, both types are treated exactly the same
in terms of alignment and passing locations (on registers or stack).
This patch is to extend is_hfa to handle both HFA and HVA.

gdb:

2015-11-27  Yao Qi  <yao.qi@linaro.org>

	* aarch64-tdep.c (is_hfa): Rename to ...
	(is_hfa_or_hva): ... this.  Handle vector type.  All callers
	updated.
	(aarch64_extract_return_value): Update debugging message.
	(aarch64_store_return_value): Likewise.
	(aarch64_return_in_memory): Update comments.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Use multi_line to make pattern more human readable
@ 2015-11-27 15:24 sergiodj+buildbot
  2015-11-27 18:10 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-27 15:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT dfcb77a8d78462af49ebc42b41d6fc504f4c2cf0 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: dfcb77a8d78462af49ebc42b41d6fc504f4c2cf0

Use multi_line to make pattern more human readable

gdb/testsuite:

2015-11-27  Yao Qi  <yao.qi@linaro.org>

	* gdb.cp/annota2.exp: Rewrite the pattern using multi_line.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [AArch64] Let aliased instructions be their preferred form.
@ 2015-11-27 16:04 sergiodj+buildbot
  2015-11-27 23:31 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-27 16:04 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 35822b3812f74319dfad28876d37645589b83a80 ***

Author: Matthew Wahab <matthew.wahab@arm.com>
Branch: master
Commit: 35822b3812f74319dfad28876d37645589b83a80

[AArch64] Let aliased instructions be their preferred form.

Although the AArch64 backend supports aliased instructions, the aliasing
forms are always preferred over the real instruction. This makes it
awkward to handle instructions which have aliases but which are their
own preferred form.

This patch includes the instruction being aliased in the list of
alternatives which is searched when considering which form to use.

opcodes/
2015-11-27  Matthew Wahab  <matthew.wahab@arm.com>

	* aarch64-asm-2.c: Regenerate.
	* aarch64-dis-2.c: Regenerate.
	* aarch64-dis.c: Weaken assert.
	* aarch64-gen.c: Include the instruction in the list of its
	possible aliases.

Change-Id: I1f23eb25fccef76a64d3d732d58761bd25fad94e


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] New test gdb.arch/arm-neon.exp
@ 2015-11-27 16:37 sergiodj+buildbot
  2015-11-27 21:13 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-27 16:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 58b584afe6ed6949c10b3049167c66cc070e0e81 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 58b584afe6ed6949c10b3049167c66cc070e0e81

New test gdb.arch/arm-neon.exp

Both ARM and AArch64 have defined some SIMD data types in arm_neon.h,
but we don't have a test case for passing them and returning them in
inferior call.  This test also covers passing and returning
homogeneous short vector aggregate (defined by AArch64 ABI document)
in inferior call too.

gdb/testsuite:

	* gdb.arch/arm-neon.exp: New.
	* gdb.arch/arm-neon.c: New.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [AArch64][PATCH 2/3] Adjust a utility function for floating point values.
@ 2015-11-27 16:42 sergiodj+buildbot
  2015-11-28  9:05 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-27 16:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cf86120bae8973340583a0613ad622f0ca013efd ***

Author: Matthew Wahab <matthew.wahab@arm.com>
Branch: master
Commit: cf86120bae8973340583a0613ad622f0ca013efd

[AArch64][PATCH 2/3] Adjust a utility function for floating point values.

ARMv8.2 adds 16-bit floating point operations as an optional
extension. This patch adjusts the utility function expand_fp_imm to
support 16-bit values.

The function is intended to convert an 8-bit immediate representing a
floating point value to a representation that can be passed to
fprintf. Because of the limited use of the results, the only change made
to the function is to treat a request for a 16-bit float as a request
for a 32-bit float.

opcodes/
2015-11-27  Matthew Wahab  <matthew.wahab@arm.com>

	* aarch64-opc.c (half_conv_t): New.
	(expand_fp_imm): Replace is_dp flag with the parameter size to
	specify the number of bytes for the required expansion.  Treat
	a 16-bit expansion like a 32-bit expansion.  Add check for an
	unsupported size request.  Update comment.
	(aarch64_print_operand): Update to support 16-bit floating point
	values.  Update for changes to expand_fp_imm.

Change-Id: I1ae3df3864be375d71925197ab03397ed1ad2d15


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [AArch64] Add ARMv8.2 instructions BFC and REV64.
@ 2015-11-27 18:23 sergiodj+buildbot
  2015-11-28  1:18 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-27 18:23 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d685192a58d4c198633bd0e69cfe0a114576e98a ***

Author: Matthew Wahab <matthew.wahab@arm.com>
Branch: master
Commit: d685192a58d4c198633bd0e69cfe0a114576e98a

[AArch64] Add ARMv8.2 instructions BFC and REV64.

ARMv8.2 adds two new instructions: BFC as an alias for BFM and REV64 as
an alias for REV. This patch set adds support for these to binutils,
enabled when the -march=armv8.2-a is given. It depends on the support
for an instruction being its preferred form which was added in an
earlier patch.

This patch adds the alias BFC <Rd>, #<imm>, #<width> as the preferred
form for BFM when the source is a zero register and the conditions for
using the BFI form are met (in other words, BFC is the preferred form
for BFI <Rd>, <Rs>, #<imm>, #<width> when the <Rs> is a zero register).

gas/testsuite/
2015-11-27  Matthew Wahab  <matthew.wahab@arm.com>

	* gas/aarch64/alias-2.d: New.
	* gas/aarch64/alias-2.s: New.

include/opcode/
2015-11-27  Matthew Wahab  <matthew.wahab@arm.com>

	* aarch64.h (aarch64_op): Add OP_BFC.

opcodes/
2015-11-27  Matthew Wahab  <matthew.wahab@arm.com>

	* aarch64-asm-2.c: Regenerate.
	* aarch64-asm.c (convert_bfc_to_bfm): New.
	(convert_to_real): Add case for OP_BFC.
	* aarch64-dis-2.c: Regenerate.
	* aarch64-dis.c: (convert_bfm_to_bfc): New.
	(convert_to_alias): Add case for OP_BFC.
	* aarch64-opc-2.c: Regenerate.
	* aarch64-opc.c (operand_general_constraint_met_p): Weaken assert
	to allow width operand in three-operand instructions.
	* aarch64-tbl.h (QL_BF1): New.
	(aarch64_feature_v8_2): New.
	(ARMV8_2): New.
	(aarch64_opcode_table): Add "bfc".

Change-Id: I6efe318b2538ba11f0caece7c6d70957441c872b


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [AArch64][PATCH 1/3] Support ARMv8.2 FP16 floating point instructions.
@ 2015-11-27 19:07 sergiodj+buildbot
  2015-11-28  7:00 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-27 19:07 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3bd894a7147feacf6a8ab388b1b1e0d685abfcdc ***

Author: Matthew Wahab <matthew.wahab@arm.com>
Branch: master
Commit: 3bd894a7147feacf6a8ab388b1b1e0d685abfcdc

[AArch64][PATCH 1/3] Support ARMv8.2 FP16 floating point instructions.

ARMv8.2 adds 16-bit floating point operations as an optional extension
to the ARMv8 FP support. This patch set adds support for the 16-bit FP
instructions to binutils, enabling the instructions when both +fp and
+fp16 architecture extensions are enabled.

The patches in this series:
- Add a feature macro for use by the encoding/decoding mechanism.
- Adjust a utility function, used when disassembling, to support 16-bit
  floating point values.
- Add the new scalar floating-point instructions.

This patch adds the feature macro FP_F16 to the AArch64 encoding/decoding
mechanism, enabling it when both +fp and +fp16 are selected.

opcodes/
2015-11-27  Matthew Wahab  <matthew.wahab@arm.com>

	* aarch64-tbl.h (aarch64_feature_fp_f16): New.
	(FP_F16): New.

Change-Id: Ie370e43e3d77a7d54b4416b4be901b363a37f3d5


^ permalink raw reply	[flat|nested] 2113+ messages in thread
[parent not found: <e19616610d7327664f99215a69cb326682742dc3@gdb-build>]
* [binutils-gdb] Avoid "enum conversion when passing argument 1 of 'getrusage' is invalid in C++" warning
@ 2015-11-28 16:50 sergiodj+buildbot
  2015-11-28 17:25 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-28 16:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT aaae08a7e4ac526975403ebb5f93b7f24ea16b90 ***

Author: Uros Bizjak <ubizjak@gmail.com>
Branch: master
Commit: aaae08a7e4ac526975403ebb5f93b7f24ea16b90

Avoid "enum conversion when passing argument 1 of 'getrusage' is invalid in C++" warning

 	* getruntime.c (get_run_time) [__USE_GNU]: Use RUSAGE_SELF as
 	argument 1 of getrusage call.

git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@225534 138bc75d-0d04-0410-961f-82ee72b054a4


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix several crashes of C++ demangler on fuzzed input.
@ 2015-11-28 17:05 sergiodj+buildbot
  2015-11-28 19:41 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-28 17:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d81bf7ddc2ad497037fbfde5d15cfa8d81a9e959 ***

Author: Mikhail Maltsev <maltsevm@gmail.com>
Branch: master
Commit: d81bf7ddc2ad497037fbfde5d15cfa8d81a9e959

Fix several crashes of C++ demangler on fuzzed input.

libiberty/
	* cp-demangle.c (d_dump): Fix syntax error.
	(d_identifier): Adjust type of len to match d_source_name.
	(d_expression_1): Fix out-of-bounds access.  Check code variable for
	NULL before dereferencing it.
	(d_find_pack): Do not recurse for FIXED_TYPE, DEFAULT_ARG and NUMBER.
	(d_print_comp_inner): Add NULL pointer check.
	* cp-demangle.h (d_peek_next_char): Define as inline function when
	CHECK_DEMANGLER is defined.
	(d_advance): Likewise.
	* testsuite/demangle-expected: Add new testcases.

git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@225727 138bc75d-0d04-0410-961f-82ee72b054a4


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix PR63758 by using the _NSGetEnviron() API on Darwin
@ 2015-11-28 17:21 sergiodj+buildbot
  2015-11-28 21:31 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-28 17:21 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 35a88fa501ff2e2fe133e7c0f38768ae703a43b7 ***

Author: Iain Sandoe <iain@codesourcery.com>
Branch: master
Commit: 35a88fa501ff2e2fe133e7c0f38768ae703a43b7

Fix PR63758 by using the _NSGetEnviron() API on Darwin

include/

	Roland McGrath  <roland@gnu.org>

	PR other/63758
	* environ.h: New file.

libiberty/

	Roland McGrath  <roland@gnu.org>
	Iain Sandoe  <iain@codesourcery.com>

	PR other/63758
	* pex-unix.c: Obtain the environment interface from settings in environ.h
	rather than in-line code.  Update copyright date.
	* setenv.c: Likewise.
	* xmalloc.c: Likewise.




git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@228942 138bc75d-0d04-0410-961f-82ee72b054a4


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] (Makefiles): PATCH to include libcpp and libiberty in GCC etags
@ 2015-11-28 17:28 sergiodj+buildbot
  2015-11-28 22:32 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-28 17:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1e924157387421d45ccf2aafd33a886abda05420 ***

Author: Jason Merrill <jason@redhat.com>
Branch: master
Commit: 1e924157387421d45ccf2aafd33a886abda05420

(Makefiles): PATCH to include libcpp and libiberty in GCC etags

	gcc/c/
	* Make-lang.in (c.tags): Also include libcpp TAGS.
	gcc/cp/
	* Make-lang.in (c++.tags): Also include libcpp TAGS.

git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@229504 138bc75d-0d04-0410-961f-82ee72b054a4


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] PR other/61321 - demangler crash on casts in template parameters
@ 2015-11-28 17:44 sergiodj+buildbot
  2015-11-29  0:37 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-28 17:44 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c4be264168ee2f6c38b6b9b3db0a166441be478b ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: c4be264168ee2f6c38b6b9b3db0a166441be478b

PR other/61321 - demangler crash on casts in template parameters

The fix for bug 59195:

 [C++ demangler handles conversion operator incorrectly]
 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59195

unfortunately makes the demangler crash due to infinite recursion, in
case of casts in template parameters.

For example, with:

 template<int> struct A {};
 template <typename Y> void function_temp(A<sizeof ((Y)(999))>) {}
 template void function_temp<int>(A<sizeof (int)>);

The 'function_temp<int>' instantiation above mangles to:

  _Z13function_tempIiEv1AIXszcvT_Li999EEE

The demangler parses this as:

typed name
  template
    name 'function_temp'
    template argument list
      builtin type int
  function type
    builtin type void
    argument list
      template                          (*)
        name 'A'
        template argument list
          unary operator
            operator sizeof
            unary operator
              cast
                template parameter 0    (**)
              literal
                builtin type int
                name '999'

And after the fix for 59195, due to:

 static void
 d_print_cast (struct d_print_info *dpi, int options,
	       const struct demangle_component *dc)
 {
 ...
   /* For a cast operator, we need the template parameters from
      the enclosing template in scope for processing the type.  */
   if (dpi->current_template != NULL)
     {
       dpt.next = dpi->templates;
       dpi->templates = &dpt;
       dpt.template_decl = dpi->current_template;
     }

when printing the template argument list of A (what should be "<sizeof
(int)>"), the template parameter 0 (that is, "T_", the '**' above) now
refers to the first parameter of the the template argument list of the
'A' template (the '*' above), exactly what we were already trying to
print.  This leads to infinite recursion, and stack exaustion.  The
template parameter 0 should actually refer to the first parameter of
the 'function_temp' template.

Where it reads "for the cast operator" in the comment in d_print_cast
(above), it's really talking about a conversion operator, like:

  struct A { template <typename U> explicit operator U(); };

We don't want to inject the template parameters from the enclosing
template in scope when processing a cast _expression_, only when
handling a conversion operator.

The problem is that DEMANGLE_COMPONENT_CAST is currently ambiguous,
and means _both_ 'conversion operator' and 'cast expression'.

Fix this by adding a new DEMANGLE_COMPONENT_CONVERSION component type,
which does what DEMANGLE_COMPONENT_CAST does today, and making
DEMANGLE_COMPONENT_CAST just simply print its component subtree.

I think we could instead reuse DEMANGLE_COMPONENT_CAST and in
d_print_comp_inner still do:

 @@ -5001,9 +5013,9 @@ d_print_comp_inner (struct d_print_info *dpi, int options,
        d_print_comp (dpi, options, dc->u.s_extended_operator.name);
        return;

     case DEMANGLE_COMPONENT_CAST:
       d_append_string (dpi, "operator ");
 -     d_print_cast (dpi, options, dc);
 +     d_print_conversion (dpi, options, dc);
       return;

leaving the unary cast case below calling d_print_cast, but seems to
me that spliting the component types makes it easier to reason about
the code.

g++'s testsuite actually generates three symbols that crash the
demangler in the same way.  I've added those as tests in the demangler
testsuite as well.

And then this fixes PR other/61233 too, which happens to be a
demangler crash originally reported to GDB, at:
https://sourceware.org/bugzilla/show_bug.cgi?id=16957

Bootstrapped and regtested on x86_64 Fedora 20.

Also ran this through GDB's testsuite.  GDB will require a small
update to use DEMANGLE_COMPONENT_CONVERSION in one place it's using
DEMANGLE_COMPONENT_CAST in its sources.

libiberty/
2015-11-27  Pedro Alves  <palves@redhat.com>

        PR other/61321
        PR other/61233
        * demangle.h (enum demangle_component_type)
        <DEMANGLE_COMPONENT_CONVERSION>: New value.
        * cp-demangle.c (d_demangle_callback, d_make_comp): Handle
        DEMANGLE_COMPONENT_CONVERSION.
        (is_ctor_dtor_or_conversion): Handle DEMANGLE_COMPONENT_CONVERSION
        instead of DEMANGLE_COMPONENT_CAST.
        (d_operator_name): Return a DEMANGLE_COMPONENT_CONVERSION
        component if handling a conversion.
        (d_count_templates_scopes, d_print_comp_inner): Handle
        DEMANGLE_COMPONENT_CONVERSION.
        (d_print_comp_inner): Handle DEMANGLE_COMPONENT_CONVERSION instead
        of DEMANGLE_COMPONENT_CAST.
        (d_print_cast): Rename as ...
        (d_print_conversion): ... this.  Adjust comments.
        (d_print_cast): Rewrite - simply print the left subcomponent.
        * cp-demint.c (cplus_demangle_fill_component): Handle
        DEMANGLE_COMPONENT_CONVERSION.

        * testsuite/demangle-expected: Add tests.

git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@231020 138bc75d-0d04-0410-961f-82ee72b054a4


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Port libvtv to Solaris
@ 2015-11-28 18:00 sergiodj+buildbot
  2015-11-29  3:07 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-28 18:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 87746c154ae96bd3b632198273061eb6879f20a5 ***

Author: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
Branch: master
Commit: 87746c154ae96bd3b632198273061eb6879f20a5

Port libvtv to Solaris

	libstdc++-v3:
	* acinclude.m4 (GLIBCXX_ENABLE_VTABLE_VERIFY) <solaris2*>: Use
	-Wl,-R in VTV_CXXLINKFLAGS.
	* configure: Regenerate.

	* testsuite/18_support/bad_exception/23591_thread-1.c: Use
	-fvtable-verify=none on Solaris 12+.

	libgcc:
	* Makefile.in (VTV_CFLAGS): New variable.
	(vtv_start$(objext), vtv_end$(objext), vtv_end$(objext))
	(vtv_start_preinit$(objext), vtv_end_preinit$(objext)): Use it.
	* config.host (*-*-solaris2*): Add t-crtstuff-pic to tmake_file.
	Add vtv_start.o, vtv_end.o, vtv_start_preinit.o, vtv_end_preinit.o
	to extra_parts if $enable_vtable_verify = yes.

	libvtv:
	* configure.tgt (*-*-solaris2.[1-9]*): Declare supported.
	* configure.ac: Call AC_USE_SYSTEM_EXTENSIONS.
	<*-*-solaris2*>: Check for init priority support.
	Check for getexecname, __fortify_fail, _obstack_begin.
	(VTV_NO_OBSTACK): New conditional.
	* configure: Regenerate.
	* Makefile.am [VTV_NO_OBSTACK] (obstack.c): Use new condition.
	Create empty config.h
	* Makefile.in: Regenerate.

	* vtv_rts.cc [HAVE_GETEXECNAME] (program_invocation_name): New
	variable.
	(read_section_offset_and_length) [HAVE_GETEXECNAME]: Set it.
	(dl_iterate_phdr_callback) [HAVE_GETEXECNAME]: Set it.

	(__fortify_fail): Wrap in HAVE___FORTIFY_FAIL
	[!HAVE___FORTIFY_FAIL]: Provide non-Cygwin implementation.

	(read_section_offset_and_length): Assert sh_size >= VTV_PAGE_SIZE.
	(iterate_modules): Fix typo.
	Use VTV_PAGE_SIZE.
	(dl_iterate_phdr_callback): Fix typo.
	Use VTV_PAGE_SIZE.
	(__VLTChangePermission): Fix typos.

	include:
	* vtv-change-permission.h (VTV_PAGE_SIZE) [__sun__ && __svr4__ &&
	__sparc__]: Define.

	gcc:
	* config/sol2.h (SUPPORTS_INIT_PRIORITY): Move up.
	(STARTFILE_VTV_SPEC, ENDFILE_VTV_SPEC): Define.
	(STARTFILE_SPEC): Use %(startfile_vtv).
	(ENDFILE_SPEC): Use %(endfile_vtv).
	(SUBTARGET_EXTRA_SPECS): Handle STARTFILE_VTV_SPEC,
	ENDFILE_VTV_SPEC.

	* gcc.c (LINK_COMMAND_SPEC): Move VTABLE_VERIFICATION_SPEC after %{L*}.

git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@230865 138bc75d-0d04-0410-961f-82ee72b054a4


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] libsanitizer merge from upstream r250806, compiler part.
@ 2015-11-28 18:08 sergiodj+buildbot
  2015-11-29  4:03 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-28 18:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3b16c5514a2e01d47295e8d82cecd6b62db62955 ***

Author: Maxim Ostapenko <m.ostapenko@partner.samsung.com>
Branch: master
Commit: 3b16c5514a2e01d47295e8d82cecd6b62db62955

libsanitizer merge from upstream r250806, compiler part.

gcc/

	* asan.c (asan_emit_stack_protection): Don't pass local stack to
	asan_stack_malloc_[n] anymore. Check if asan_stack_malloc_[n] returned
	NULL and use local stack than.
	(asan_finish_file): Insert __asan_version_mismatch_check_v[n] call
	in addition to __asan_init.
	* sanitizer.def (BUILT_IN_ASAN_INIT): Rename to __asan_init.
	(BUILT_IN_ASAN_VERSION_MISMATCH_CHECK): Add new builtin call.
	* asan.h (asan_intercepted_p): Handle new string builtins.
	* ubsan.c (ubsan_use_new_style_p): New function.
	(ubsan_instrument_float_cast): If location is unknown, assign
	input_location to loc. Propagate loc to ubsan_create_data if
	ubsan_use_new_style_p returned true.

config/

	* bootstrap-asan.mk: Replace ASAN_OPTIONS=detect_leaks with
	LSAN_OPTIONS=detect_leaks.

gcc/testsuite/

	* c-c++-common/ubsan/float-cast-overflow-10.c: Adjust test.
	* c-c++-common/ubsan/float-cast-overflow-8.c: Likewise.
	* c-c++-common/ubsan/float-cast-overflow-9.c: Likewise.
	* g++.dg/asan/default-options-1.C: Likewise.


git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@229112 138bc75d-0d04-0410-961f-82ee72b054a4


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Implement N4514, C++ Extensions for Transactional Memory.
@ 2015-11-28 18:09 sergiodj+buildbot
  2015-11-28 20:34 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-28 18:09 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e9a3881624886dc523a500a86bfdac6dc58fd0db ***

Author: Jason Merrill <jason@redhat.com>
Branch: master
Commit: e9a3881624886dc523a500a86bfdac6dc58fd0db

Implement N4514, C++ Extensions for Transactional Memory.

gcc/
	* builtins.def (BUILT_IN_ABORT): Add transaction_pure attribute.
gcc/c-family/
	* c-common.c (c_common_reswords): Add C++ TM TS keywords.
	(c_common_attribute_table): Add transaction_safe_dynamic.
	transaction_safe now affects type identity.
	(handle_tm_attribute): Handle transaction_safe_dynamic.
	* c-common.h (enum rid): Add RID_ATOMIC_NOEXCEPT,
	RID_ATOMIC_CANCEL, RID_SYNCHRONIZED.
	(OBJC_IS_CXX_KEYWORD): Add RID_SYNCHRONIZED.
	(D_TRANSMEM): New.
	* c-cppbuiltin.c (c_cpp_builtins): Define __cpp_transactional_memory.
	* c-pretty-print.c (pp_c_attributes_display): Don't print
	transaction_safe in C++.
gcc/c/
	* c-parser.c (c_lex_one_token): Handle @synchronized.
	* c-decl.c (match_builtin_function_types): A declaration of a built-in
	can change whether the function is transaction_safe.
gcc/cp/
	* cp-tree.h (struct cp_declarator): Add tx_qualifier field.
	(BCS_NORMAL, BCS_TRANSACTION): New enumerators.
	* lex.c (init_reswords): Limit TM kewords to -fgnu-tm.
	* parser.c (cp_lexer_get_preprocessor_token): Fix @synchronized.
	(make_call_declarator): Take tx_qualifier.
	(cp_parser_tx_qualifier_opt): New.
	(cp_parser_lambda_declarator_opt): Use it.
	(cp_parser_direct_declarator): Likewise.
	(cp_parser_statement): Handle atomic_noexcept, atomic_cancel.
	(cp_parser_compound_statement): Change in_try parameter to bcs_flags.
	(cp_parser_std_attribute): Map optimize_for_synchronized to
	transaction_callable.
	(cp_parser_transaction): Take the token.  Handle atomic_noexcept.
	* lambda.c (maybe_add_lambda_conv_op): Handle transaction-safety.
	* call.c (enum conversion_kind): Add ck_tsafe.
	(standard_conversion): Handle transaction-safety conversion.
	(convert_like_real, resolve_address_of_overloaded_function): Likewise.
	(check_methods): Diagnose transaction_safe_dynamic on non-virtual
	function.
	(look_for_tm_attr_overrides): Don't inherit transaction_safe_dynamic.
	* cvt.c (tx_safe_fn_type_p, tx_unsafe_fn_variant)
	(can_convert_tx_safety): New.
	* typeck.c (composite_pointer_type): Handle transaction-safety.
	* name-lookup.h (enum scope_kind): Add sk_transaction.
	* name-lookup.c (begin_scope): Handle it.
	* semantics.c (begin_compound_stmt): Pass it.
	* decl.c (check_previous_goto_1): Check it.
	(struct named_label_entry): Add in_transaction_scope.
	(poplevel_named_label_1): Set it.
	(check_goto): Check it.
	(duplicate_decls): A specialization can be transaction_safe
	independently of its template.
	(grokdeclarator): Handle tx-qualifier.
	* rtti.c (ptr_initializer): Handle transaction-safe.
	* search.c (check_final_overrider): Check transaction_safe_dynamic.
	Don't check transaction_safe.
	* mangle.c (write_function_type): Mangle transaction_safe here.
	(write_CV_qualifiers_for_type): Not here.
	(write_type): Preserve transaction_safe when stripping attributes.
	* error.c (dump_type_suffix): Print transaction_safe.
libiberty/
	* cp-demangle.c (d_cv_qualifiers): Dx means transaction_safe.
	(cplus_demangle_type): Let d_cv_qualifiers handle it.
	(d_dump, d_make_comp, has_return_type, d_encoding)
	(d_count_templates_scopes, d_print_comp_inner)
	(d_print_mod_list, d_print_mod, d_print_function_type)
	(is_ctor_or_dtor): Handle DEMANGLE_COMPONENT_TRANSACTION_SAFE.

git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@228462 138bc75d-0d04-0410-961f-82ee72b054a4


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix mi-nonstop.exp with extended-remote
@ 2015-11-30 20:05 sergiodj+buildbot
  2015-11-30 20:40 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-30 20:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f015c27b5294eaf87d0aa814d94972e65c7cc90e ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: f015c27b5294eaf87d0aa814d94972e65c7cc90e

Fix mi-nonstop.exp with extended-remote

Testing with "maint set target-non-stop on" makes mi-nonstop.exp run
with the extended-remote board.  That reveals that mi-nonstop.exp is
using the wrong predicate to check for "using remote protocol".

This is not visible today because non-stop tests all fail to run with
extended-remote board, because they spawn gdb and then do "set
non-stop on".  However, with that board, gdb connects to the gdbserver
from within mi_gdb_start, and changing non-stop when already connected
doesn't work.  Fix that by instead enabling non-stop mode on gdb's
command line.

gdb/testsuite/ChangeLog:
2015-11-30  Pedro Alves  <palves@redhat.com>

	* gdb.mi/mi-nonstop.exp: Append "set non-stop on" to GDBFLAGS
	instead of issuing "-gdb-set non-stop 1" after starting gdb.
	Use mi_is_target_remote instead of checking "is_remote target".
	* lib/gdb.exp (gdb_is_target_remote): Rename to ...
	(gdb_is_target_remote_prompt): ... this, and add 'prompt_regexp'
	parameter.
	(gdb_is_target_remote): Reimplement.
	* lib/mi-support.exp (mi_is_target_remote): New procedure.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Remote all-stop-on-top-of-non-stop
@ 2015-11-30 20:13 sergiodj+buildbot
  2015-11-30 21:42 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-30 20:13 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6efcd9a8b3dc6a01cd1f212a2d854e5f8896715e ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 6efcd9a8b3dc6a01cd1f212a2d854e5f8896715e

Remote all-stop-on-top-of-non-stop

This is the first pass at implementing support for all-stop mode
running against the remote target using the non-stop variant of the
protocol.

The trickiest part here is the initial connection setup/synching.  We
need to fetch all inferiors' target descriptions etc. before stopping
threads, because stop_all_threads needs to read the threads' registers
(to record each thread's stop_pc).  But OTOH, the initial inferior
setup (target_post_attach, post_create_inferior, etc.), only works
correctly if the inferior is stopped...  So I've split that initial
setup part from attach_command_post_wait to a separate function, and
added a "still needs setup" flag to the inferior structure.  This is
similar to gdbserver/linux-low.c's handling of discovering the
process's target description).  Then if on connection all threads of
the remote inferior are running, when we go about stopping them, as
soon as they stop we call setup_inferior, from within
stop_all_threads.

Also, in all-stop, we need to process all the initial stop replies to
learn about all the pending signal the threads may already be stopped
for, and pick the one to report as current.  This is exposed by
gdb.threads/reconnect-signal.exp.

gdb/
2015-11-30  Pedro Alves  <palves@redhat.com>

	* gdbthread.h (switch_to_thread_no_regs): Declare.
	* infcmd.c (setup_inferior): New function, factored out from ...
	(attach_command_post_wait): ... this.  Rename to ...
	(attach_post_wait): ... this.  Replace parameter async_exec with
	attach_post_wait_mode parameter.  Adjust.
	(enum attach_post_wait_mode): New enum.
	(struct attach_command_continuation_args): Replace 'async_exec'
	field with 'mode' field.
	(attach_command_continuation): Adjust.
	(attach_command): Add comment.  Mark the inferior as needing
	setup.  Adjust to use enum attach_post_wait_mode.
	(notice_new_inferior): Use switch_to_thread_no_regs.  Adjust to
	use enum attach_post_wait_mode.
	* inferior.h (setup_inferior): Declare.
	(struct inferior) <needs_setup>: New field.
	* infrun.c (set_last_target_status): Make extern.
	(stop_all_threads): Make extern.  Setup inferior, if necessary.
	* infrun.h (set_last_target_status, stop_all_threads): Declare.
	* remote-notif.c (remote_async_get_pending_events_handler)
	(handle_notification): Replace non_stop checks with
	target_is_non_stop_p() checks.
	* remote.c (remote_notice_new_inferior): Remove non_stop check.
	(remote_update_thread_list): Replace non_stop check with
	target_is_non_stop_p() check.
	(print_one_stopped_thread): New function.
	(process_initial_stop_replies): New 'from_tty' parameter.
	"Notice" all new live inferiors after storing initial stops as
	pending status in each corresponding thread.  If all-stop, stop
	all threads, try picking a signalled thread as current, and print
	the status of that one thread.  Record the last target status.
	(remote_start_remote): Replace non_stop checks with
	target_is_non_stop_p() checks.  Don't query for the remote current
	thread of use qOffsets here.  Pass from_tty to
	process_initial_stop_replies.
	(extended_remote_attach): Replace non_stop checks with
	target_is_non_stop_p() checks.
	(extended_remote_post_attach): Send qOffsets here.
	(remote_vcont_resume, remote_resume, remote_stop)
	(remote_interrupt, remote_parse_stop_reply, remote_wait): Replace
	non_stop checks with target_is_non_stop_p() checks.
	(remote_async): If target is non-stop, mark/clear the pending
	events token.
	* thread.c (switch_to_thread_no_regs): New function.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] gdbserver crash running gdb.threads/non-ldr-exc-1.exp
@ 2015-11-30 20:28 sergiodj+buildbot
  2015-11-30 23:48 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-30 20:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 34c6591498f4363ef2c71d683cdaaa33d6a6ad64 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 34c6591498f4363ef2c71d683cdaaa33d6a6ad64

gdbserver crash running gdb.threads/non-ldr-exc-1.exp

This fixes a gdbserver crash when running
gdb.threads/non-ldr-exc-1.exp with "maint set target-non-stop on".
The problem is that qSymbol is called when gdbserver has
current_thread == NULL.

gdb/gdbserver/ChangeLog:
2015-11-30  Pedro Alves  <palves@redhat.com>

	* gdbthread.h (find_any_thread_of_pid): Declare.
	* inferiors.c (thread_of_pid, find_any_thread_of_pid): New
	functions.
	* server.c (handle_query): If current_thread is NULL, look for
	another thread of the selected process.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] remote: stop reason and watchpoint data address per thread
@ 2015-11-30 20:36 sergiodj+buildbot
  2015-12-01  0:47 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-30 20:36 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 799a2abe613be0645b84f5aaa050f2f91e6ae3f7 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 799a2abe613be0645b84f5aaa050f2f91e6ae3f7

remote: stop reason and watchpoint data address per thread

Running local-watch-wrong-thread.exp with "maint set target-non-stop
on" exposes that gdb/remote.c only records whether the target stopped
for a breakpoint/watchpoint plus the watchpoint data address *for the
last reported remote event*.  But in non-stop mode, we need to keep
that info per-thread, as each thread can end up with its own
last-status pending.

gdb/ChangeLog:
2015-11-30  Pedro Alves  <palves@redhat.com>

	* remote.c (struct remote_state) <remote_watch_data_address,
	stop_reason>: Delete fields.
	(struct private_thread_info) <stop_reason, watch_data_address>:
	New fields.
	(resume_clear_thread_private_info): New function.
	(append_pending_thread_resumptions): Call it.
	(remote_resume): Clear all threads' private info.
	(process_stop_reply): Adjust.
	(remote_wait_as): Don't reference remote_state's stop_reason
	field.
	(remote_stopped_by_sw_breakpoint)
	(remote_stopped_by_hw_breakpoint, remote_stopped_by_watchpoint)
	(remote_stopped_data_address): Adjust to refer get data from the
	current thread.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] gdbserver resume_stop handling bug
@ 2015-11-30 21:00 sergiodj+buildbot
  2015-12-01  5:11 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-30 21:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 56cf4bed5354769d7352c5cf4e054a346d2553cd ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 56cf4bed5354769d7352c5cf4e054a346d2553cd

gdbserver resume_stop handling bug

Running attach-many-short-lived-threads.exp with the extended-remote
board with "maint set target-non-stop on" times out -- the attach
never completes.  Enabling infrun debug logs, we see that GDB is stuck
stopping all threads:

 infrun: target_wait (-1.0.0, status) =
 infrun:   1639.22213.0 [Thread 1639.22213],
 infrun:   status->kind = stopped, signal = GDB_SIGNAL_0
 infrun:   Thread 1639.22260 not executing
 infrun:   Thread 1639.22256 not executing
 infrun:   Thread 1639.22258 not executing
 infrun:   Thread 1639.22257 not executing
 infrun:   Thread 1639.22259 not executing
 infrun:   Thread 1639.22255 not executing
 infrun:   Thread 1639.22253 executing, already stopping
 infrun:   Thread 1639.22251 executing, already stopping
 infrun:   Thread 1639.22252 executing, already stopping
 infrun:   Thread 1639.22250 executing, already stopping
 infrun:   Thread 1639.22254 executing, already stopping
 infrun:   Thread 1639.22247 executing, already stopping
 infrun:   Thread 1639.22213 not executing
 infrun:   Thread 1639.22207 not executing
 infrun:   Thread 1639.22201 not executing
 infrun:   Thread 1639.22219 not executing
 infrun:   Thread 1639.1639 not executing
 ** HANG HERE **

GDB is waiting for the stop replies of any of those "already stopping"
threads.  Take 22253 for example.  On the gdbserver logs we see:

 ...
 resume_stop request for LWP 22253
 stopping LWP 22253
 Sending sigstop to lwp 22253
 linux_resume done
 ...

and:

 my_waitpid (-1, 0x40000001)
 my_waitpid (-1, 0x80000001): status(3057f), 22253
 LWFE: waitpid(-1, ...) returned 22253, ERRNO-OK
 LLW: waitpid 22253 received Trace/breakpoint trap (stopped)
 pc is 0x3615ef4ce1
 HEW: Got clone event from LWP 22253, new child is LWP 22259

but from here on, we never see any other event for LWP 22253.  In
particular, we never see the expected SIGSTOP (from "Sending sigstop"
above).  The issue is that linux_resume_stopped_resumed_lwps never
re-resumes the 22253 after the clone event.

gdb/gdbserver/ChangeLog:
2015-11-30  Pedro Alves  <palves@redhat.com>

	* linux-low.c (resume_stopped_resumed_lwps): Don't check whether
	the thread's last_resume_kind was resume_stop.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Make dprintf-non-stop.exp cope with remote testing
@ 2015-11-30 21:07 sergiodj+buildbot
  2015-12-01  6:06 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-30 21:07 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 09df4675f2e4f8f098954f9a38f44d12089f1c4e ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 09df4675f2e4f8f098954f9a38f44d12089f1c4e

Make dprintf-non-stop.exp cope with remote testing

Testing with the extended-remote board with "maint set target-non-stop
on" shows a dprintf-non-stop.exp regression.  The issue is simply that
the test is expecting output that is only valid for the native target:

 native:

  [process 8676] #1 stopped.

 remote:

  [Thread 8900.8900] #1 stopped.

In order to expose this without "maint set target-non-stop on", this
restarts gdb with non-stop mode already enabled.

gdb/testsuite/ChangeLog:
2015-11-30  Pedro Alves  <palves@redhat.com>

	* gdb.base/dprintf-non-stop.exp: Use build_executable instead of
	prepare_for_testing.  Start gdb with "set non-stop on" appended to
	GDBFLAGS.  Lax expected stop output.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Remote thread create/exit events
@ 2015-11-30 21:14 sergiodj+buildbot
  2015-12-01  7:08 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-30 21:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 65706a29bac50c2c971227a1945e46502845766b ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 65706a29bac50c2c971227a1945e46502845766b

Remote thread create/exit events

When testing with "maint set target-non-stop on", a few
threading-related tests expose an issue that requires new RSP packets.

Say there are 3 threads running, 1-3.  If GDB tries to stop thread 1,
2 and 3, and then waits for their stops, but meanwhile say, thread 2
exits, GDB hangs forever waiting for a stop for thread 2 that won't
ever happen.

This patch fixes the issue by adding support for thread exit events to
the protocol.  However, we don't want these always enabled, as they're
useless most of the time, and would slow down remote debugging.  So I
made it so that GDB can enable/disable them, and then made gdb do that
around the cases that need it, which currently is only
infrun.c:stop_all_threads.

In turn, if we have thread exit events, then the extra "thread x
exited" traffic slows down attach-many-short-lived-threads.exp enough
that gdb has trouble keeping up with new threads that are spawned
while gdb tries to stop existing ones.  To fix that I added support
for the counterpart thread created events too.  Enabling those when we
try to stop threads ensures that new threads never get a chance to
themselves start new threads, killing the race.

gdb/doc/ChangeLog:
2015-11-30  Pedro Alves  <palves@redhat.com>

	* gdb.texinfo (Remote Configuration): List "set/show remote
	thread-events" command in configuration table.
	(Stop Reply Packets): Document "T05 create" stop
	reason and 'w' stop reply.
	(General Query Packets): Document QThreadEvents packet.  Document
	QThreadEvents qSupported feature.

gdb/gdbserver/ChangeLog:
2015-11-30  Pedro Alves  <palves@redhat.com>

	* linux-low.c (handle_extended_wait): Assert that the LWP's
	waitstatus is TARGET_WAITKIND_IGNORE.  If GDB wants to hear about
	thread create events, leave the new child's status pending.
	(linux_low_filter_event): If GDB wants to hear about thread exit
	events, leave the LWP marked dead and don't delete it.
	(linux_wait_for_event_filtered): Don't check for thread exit.
	(filter_exit_event): New function.
	(linux_wait_1): Use it, when returning an exit event.
	(linux_resume_one_lwp_throw): Assert that the LWP's
	waitstatus is TARGET_WAITKIND_IGNORE.
	* remote-utils.c (prepare_resume_reply): Handle
	TARGET_WAITKIND_THREAD_CREATED and TARGET_WAITKIND_THREAD_EXITED.
	* server.c (report_thread_events): New global.
	(handle_general_set): Handle QThreadEvents.
	(handle_query) <qSupported>: Handle and report QThreadEvents+;
	(handle_target_event): Handle TARGET_WAITKIND_THREAD_CREATED and
	TARGET_WAITKIND_THREAD_EXITED.
	* server.h (report_thread_events): Declare.

gdb/ChangeLog:
2015-11-30  Pedro Alves  <palves@redhat.com>

	* NEWS (New commands): Mention "set/show remote thread-events"
	commands.
	(New remote packets): Mention thread created/exited stop reasons
	and QThreadEvents packet.
	* infrun.c (disable_thread_events): New function.
	(stop_all_threads): Disable/enable thread create/exit events.
	Handle TARGET_WAITKIND_THREAD_EXITED.
	(handle_inferior_event_1): Handle TARGET_WAITKIND_THREAD_CREATED
	and TARGET_WAITKIND_THREAD_EXITED.
	* remote.c (remove_child_of_pending_fork): Also remove threads of
	threads that have TARGET_WAITKIND_THREAD_EXITED events.
	(remote_parse_stop_reply): Handle "create" magic register.  Handle
	'w' stop reply.
	(initialize_remote): Install remote_thread_events as
	to_thread_events target hook.
	(remote_thread_events): New function.
	* target-delegates.c: Regenerate.
	* target.c (target_thread_events): New function.
	* target.h (struct target_ops) <to_thread_events>: New field.
	(target_thread_events): Declare.
	* target/waitstatus.c (target_waitstatus_to_string): Handle
	TARGET_WAITKIND_THREAD_CREATED and TARGET_WAITKIND_THREAD_EXITED.
	* target/waitstatus.h (enum target_waitkind)
	<TARGET_WAITKIND_THREAD_CREATED, TARGET_WAITKIND_THREAD_EXITED):
	New values.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Implement TARGET_WAITKIND_NO_RESUMED in the remote protocol
@ 2015-11-30 21:45 sergiodj+buildbot
  2015-12-01 11:08 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-30 21:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f2faf941ae49653ff6e1485adfee299313d47c91 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: f2faf941ae49653ff6e1485adfee299313d47c91

Implement TARGET_WAITKIND_NO_RESUMED in the remote protocol

Testing with "maint set target-non-stop on" causes regressions in
tests that rely on TARGET_WAITKIND_NO_RESUMED, which isn't modelled on
the RSP.  In real all-stop, gdbserver detects the situation and
reporst error to GDB, and so the tests (e.g.,
gdb.threads/no-unwaited-for-left.exp) at fail quickly.  But with
"maint set target-non-stop on", GDB instead hangs forever waiting for
a stop reply that never comes, and so the tests take longer to time
out.

This adds a new "N" stop reply packet that maps 1-1 to
TARGET_WAITKIND_NO_RESUMED.

gdb/ChangeLog:
2015-11-30  Pedro Alves  <palves@redhat.com>

	PR 14618
	* NEWS (New remote packets): Mention the N stop reply.
	* remote.c (remote_protocol_features): Add "no-resumed" entry.
	(remote_query_supported): Report no-resumed+ support.
	(remote_parse_stop_reply): Handle 'N'.
	(process_stop_reply): Handle TARGET_WAITKIND_NO_RESUMED.
	(remote_wait_as): Handle 'N' / TARGET_WAITKIND_NO_RESUMED.
	(_initialize_remote): Register "set/show remote
	no-resumed-stop-reply" commands.

gdb/doc/ChangeLog:
2015-11-30  Pedro Alves  <palves@redhat.com>

	PR 14618
	* gdb.texinfo (Stop Reply Packets): Document the N stop reply.
	(Remote Configuration): Add the "set/show remote
	no-resumed-stop-reply" to the available settings table.
	(General Query Packets): Document the "no-resumed" qSupported
	feature.

gdb/gdbserver/ChangeLog:
2015-11-30  Pedro Alves  <palves@redhat.com>

	PR 14618
	* linux-low.c (linux_wait_1): If the last resumed thread is gone,
	report TARGET_WAITKIND_NO_RESUMED.
	* remote-utils.c (prepare_resume_reply): Handle
	TARGET_WAITKIND_NO_RESUMED.
	* server.c (report_no_resumed): New global.
	(handle_query) <qSupported>: Handle "no-resumed+".  Report
	"no-resumed+" support.
	(resume): When the target reports TARGET_WAITKIND_NO_RESUMED, only
	return error if the client doesn't support no-resumed events.
	(push_stop_notification): New function.
	(handle_target_event): Use it.  Report TARGET_WAITKIND_NO_RESUMED
	events if the client supports them.

gdb/testsuite/ChangeLog:
2015-11-30  Pedro Alves  <palves@redhat.com>

	* gdb.threads/no-unwaited-for-left.exp: Remove setup_kfail calls.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] gdbserver:prepare_access_memory: pick another thread
@ 2015-11-30 21:53 sergiodj+buildbot
  2015-12-01 12:09 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-30 21:53 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a67a9faef0e32886c83611cc7a0ba61e91123063 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: a67a9faef0e32886c83611cc7a0ba61e91123063

gdbserver:prepare_access_memory: pick another thread

Say GDB wants to access the inferior process's memory.  The current
remote general thread is 3, but GDB's switched to thread 2.  Because
both threads are of the same process, GDB skips making the remote
thread be thread 2 as well (sending an Hg packet) before accessing
memory (remote.c:set_general_process).  However, if thread 3 has
exited meanwhile, thread 3 no longer exists on the server and
gdbserver points current_thread to NULL.  The result is the memory
access fails, even through the process still exists.

Fix this by making prepare_to_access memory select the thread to
access memory through.

gdb/gdbserver/ChangeLog:
2015-11-30  Pedro Alves  <palves@redhat.com>

	* mem-break.c (check_gdb_bp_preconditions): Remove current_thread
	check.
	(set_gdb_breakpoint): If prepare_to_access_memory fails, set *ERR
	to -1.
	* target.c (struct thread_search): New structure.
	(thread_search_callback): New function.
	(prev_general_thread): New global.
	(prepare_to_access_memory, done_accessing_memory): New functions.
	* target.h (prepare_to_access_memory, done_accessing_memory):
	Replace macros with function declarations.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] gdbserver: don't exit until GDB disconnects
@ 2015-11-30 22:08 sergiodj+buildbot
  2015-12-01 14:11 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-30 22:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fddedbe665db9cb9824150e454c89abdc750957a ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: fddedbe665db9cb9824150e454c89abdc750957a

gdbserver: don't exit until GDB disconnects

When testing with "target remote" with "maint set target-non-stop on",
we regressions like this:

  Running /home/pedro/gdb/mygit/build/../src/gdb/testsuite/gdb.threads/continue-pending-after-query.exp ...
  FAIL: gdb.threads/continue-pending-after-query.exp: iter 4: continue until exit
  FAIL: gdb.threads/continue-pending-after-query.exp: iter 6: continue until exit
  FAIL: gdb.threads/continue-pending-after-query.exp: iter 10: continue until exit

		  === gdb Summary ===

  # of expected passes            28
  # of unexpected failures        3

where gdb.log shows:

  continue
  Continuing.
  Remote communication error.  Target disconnected.: Connection reset by peer.
  (gdb) FAIL: gdb.threads/continue-pending-after-query.exp: iter 4: continue until exit

Enabling gdb + gdbserver debug logs we see:

  gdbserver:  <<<< exiting linux_wait_1
  gdbserver: handling possible serial event
  gdbserver: Writing resume reply for LWP 11089.11089:0
  gdbserver: handling possible serial event
  gdbserver: GDBserver exiting

	GDB: Packet received: OK
	GDB: infrun: prepare_to_wait
	GDB: Sending packet: $vStopped#55...Packet received: W0;process:2b51
	GDB: Sending packet: $vStopped#55...Packet received: OK
	GDB: infrun: target_wait (-1.0.0, status) =
	GDB: infrun:   -1.0.0 [Thread 0],
	GDB: infrun:   status->kind = no-resumed
	GDB: Sending packet: $Hgp2b51.2b51#41...Remote connection closed
    (gdb) FAIL: gdb.threads/continue-pending-after-query.exp: iter 1: continue until exit

Notice the "Packet received: W0;process:2b51" followed by
vStopped->OK.

That means the process exit notification was successfully sent to GDB
and GDB fetched it.  That makes gdbserver exit, in
server.c:process_serial_event:

  if (!extended_protocol && have_ran && !target_running ())
    {
      /* In non-stop, defer exiting until GDB had a chance to query
	 the whole vStopped list (until it gets an OK).  */
      if (QUEUE_is_empty (notif_event_p, notif_stop.queue))
	{
	  /* Be transparent when GDB is connected through stdio -- no
	     need to spam GDB's console.  */
	  if (!remote_connection_is_stdio ())
	    fprintf (stderr, "GDBserver exiting\n");
	  remote_close ();
	  exit (0);
	}
    }

However, GDB is still busy processing an earlier "no-resumed" event,
and sends a "Hg" packet, which errors out with "Remote connection
closed".  IOW, it's not enough to wait for GDB to query the whole
vStopped list, gdbserver needs to wait until the exit event is really
processed.

The fix is to make gdbserver not disconnect until gdb does.

Tested on x86_64 Fedora, native gdbserver, remote + extended-remote +
with and without "maint set target-non-stop on".

gdb/gdbserver/ChangeLog:
2015-10-14  Pedro Alves  <palves@redhat.com>

	* remote-utils.c (readchar): Don't print "Got EOF" unless
	debugging gdbserver.
	* server.c (captured_main): Exit gdbserver if gdb disconnects when
	in "target remote" mode and there are no processes left to debug.
	(process_serial_event): Remove 'have_ran' static local and remove
	logic that exits gdbserver in "target remote" mode.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Refactor queries for hardware and software single stepping support in GDBServer.
@ 2015-11-30 22:31 sergiodj+buildbot
  2015-12-01 17:25 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-30 22:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7d00775ece9e2364da5cfd65ebbfce515859667f ***

Author: Antoine Tremblay <antoine.tremblay@ericsson.com>
Branch: master
Commit: 7d00775ece9e2364da5cfd65ebbfce515859667f

Refactor queries for hardware and software single stepping support in GDBServer.

Before this patch there was only one call: can_hardware_single_step. Its
implementation was a check on breakpoint_reinsert_addr if NULL it assumed
that the target could hardware single step.

This patch prepares for the case where this is not true anymore.

In order to improve software single stepping in GDBServer the
breakpoint_reinsert_addr operation of targets that had a very simple
software implementation used only for stepping over thread creation events
will be removed.

This will create a case where a target does not support hardware single
step and has the operation breakpoint_reinsert_addr set to NULL, thus
can_hardware_single_step needs to be implemented another way.

A new target operation supports_hardware_single_step is introduced and is
to return true if the target does support such a feature, support for the
feature is manually hardcoded.

Note that the hardware single step support was enabled as per the current
behavior, I did not check if tile for example really has ptrace singlestep
support but since the current implementation assumed it had, I kept it
that way.

No regressions on Ubuntu 14.04 on ARMv7 and x86.
With gdbserver-{native,extended} / { -marm -mthumb }

Compilation tested on: aarch64,arm,bfind,crisv32,m32r,ppc,s390,tic6x,tile,
xtensa.
Not tested : sh.

gdb/gdbserver/ChangeLog:

	* linux-aarch64-low.c (aarch64_supports_hardware_single_step):
	New function.
	(struct linux_target_ops) <supports_hardware_single_step>: Initialize.
	* linux-arm-low.c (arm_supports_hardware_single_step): New function.
	(struct linux_target_ops) <supports_hardware_single_step>: Initialize.
	* linux-bfin-low.c (bfin_supports_hardware_single_step): New function.
	(struct linux_target_ops) <bfin_supports_hardware_single_step>:
	Initialize.
	* linux-crisv32-low.c (cris_supports_hardware_single_step):
	New function.
	(struct linux_target_ops) <supports_hardware_single_step>: Initialize.
	* linux-low.c (can_hardware_single_step): Use
	supports_hardware_single_step.
	(can_software_single_step): New function.
	(start_step_over): Call can_software_single_step.
	(linux_supports_hardware_single_step): New function.
	(struct target_ops) <supports_software_single_step>: Initialize.
	* linux-low.h (struct linux_target_ops)
	<supports_hardware_single_step>: Initialize.
	* linux-m32r-low.c (m32r_supports_hardware_single_step): New function.
	(struct linux_target_ops) <supports_hardware_single_step>: Initialize.
	* linux-ppc-low.c (ppc_supports_hardware_single_step): New function.
	(struct linux_target_ops) <supports_hardware_single_step> Initialize.
	* linux-s390-low.c (s390_supports_hardware_single_step): New function.
	(struct linux_target_ops) <supports_hardware_single_step>: Initialize.
	* linux-sh-low.c (sh_supports_hardware_single_step): New function.
	(struct linux_target_ops) <supports_hardware_single_step>: Initialize.
	* linux-tic6x-low.c (tic6x_supports_hardware_single_step): New function.
	(struct linux_target_ops) <tic6x_supports_hardware_single_step>:
	Initialize.
	* linux-tile-low.c (tile_supports_hardware_single_step): New function.
	(struct linux_target_ops) <tile_supports_hardware_single_step>:
	Initialize.
	* linux-x86-low.c (x86_supports_hardware_single_step) New function.
	(struct linux_target_ops) <supports_hardware_single_step>: Initialize.
	* linux-xtensa-low.c (xtensa_supports_hardware_single_step):
	New function.
	(struct linux_target_ops) <supports_hardware_single_step>: Initialize.
	* target.h (struct target_ops): <supports_software_single_step>:
	New field.
	(target_supports_software_single_step): New macro.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Remove support for thread events without PTRACE_EVENT_CLONE in GDBServer.
@ 2015-11-30 22:39 sergiodj+buildbot
  2015-12-01 18:23 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-11-30 22:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9b4c5f878ff39e04127a1ad95f6b3832afe6d278 ***

Author: Antoine Tremblay <antoine.tremblay@ericsson.com>
Branch: master
Commit: 9b4c5f878ff39e04127a1ad95f6b3832afe6d278

Remove support for thread events without PTRACE_EVENT_CLONE in GDBServer.

This patch removes support for thread events if PTRACE_EVENT_CLONE is not
supported in GDBServer.

Before, on systems that did not support PTRACE_EVENT_CLONE, both GDB and
GDBServer coordinated with libthread_db.so to insert breakpoints at magic
locations in libpthread.so, in order to break at thread creation and thread
death.

Simple software single stepping support was implemented to step over these
breakpoints in case there was no hardware single stepping support. However,
these simple software single stepping implementations were not fit for any other
use as discussed in :
https://sourceware.org/ml/gdb-patches/2015-04/msg01110.html

These too simple implementations conflict with ongoing work to make proper
implementations of software single stepping in GDBServer.

The problem is that if some implementations are correct and others are not and
only there for the thread magic breakpoint, we can't enable features based
solely software single step support since some would be broken.

To keep the incorrect implementations and allow the new proper ones at the same
time we would need to implement fallback code and it quickly becomes ugly and
confusing with multiple checks for legacy software single step or proper
software single step.

However, PTRACE_EVENT_CLONE was first introduced in Linux 2.5.46,
released in November 2002.

So I think it's reasonable to just remove support for kernels that don't support
PTRACE_EVENT_CLONE, and sidestep the libthread_db breakpoints issues entirely.

This thread on the mailling list discusses the issue :
https://sourceware.org/ml/gdb/2015-10/msg00078.html

No regressions, tested on ubuntu 14.04 ARMv7 and x86.
With gdbserver-{native,extended} / { -marm -mthumb }

gdb/gdbserver/ChangeLog:

	* linux-low.c (linux_look_up_symbols): Don't call
	linux_supports_traceclone.
	* linux-low.h (thread_db_init): Remove use_events argument.
	* thread-db.c (thread_db_use_event): Remove global variable.
	(struct thread_db) <td_thr_event_enable_p>: Remove field.
	(struct thread_db) <td_create_bp>: Remove field.
	(thread_db_create_event): Remove function.
	(thread_db_enable_reporting): Likewise.
	(find_one_thread): Don't check for thread_db_use_events.
	(attach_thread): Likewise.
	(thread_db_load_search): Remove td_thr_event_enable_p initialization.
	(try_thread_db_load_1): Don't check for thread_db_use_events.
	(thread_db_init): Remove use_events argument and thread events
	handling.
	(remove_thread_event_breakpoints): Remove function.
	(thread_db_detach): Remove call to remove_thred_event_breakpoints.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] testsuite: Range stepping and non-stop mode
@ 2015-12-01  0:43 sergiodj+buildbot
  2015-12-01  9:07 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-01  0:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 04bf20c5687b102b9a2c2a915d4c400788296a3b ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 04bf20c5687b102b9a2c2a915d4c400788296a3b

testsuite: Range stepping and non-stop mode

The range-stepping tests fail with "maint set target-non-stop on" mode
because exec_cmd_expect_vCont_count doesn't know that in non-stop
mode, vCont's reply is simply "OK".

gdb/testsuite/ChangeLog:
2015-11-30  Pedro Alves  <palves@redhat.com>

	* lib/range-stepping-support.exp (exec_cmd_expect_vCont_count):
	Handle non-stop mode vCont replies.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Re: ARC port broken reloc processing
@ 2015-12-01  3:20 sergiodj+buildbot
  2015-12-01 21:27 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-01  3:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f26dd30880bad7f75b5ed1b1683628c7c986bb34 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: f26dd30880bad7f75b5ed1b1683628c7c986bb34

Re: ARC port broken reloc processing

	* elf32-arc.c (ARC_ELF_HOWTO): Delete.
	(arc_elf_howto): New function.
	(bfd_elf32_bfd_reloc_type_lookup): Use it in place of existing
	init code.
	(bfd_elf32_bfd_reloc_name_lookup): Use arc_elf_howto.
	(arc_info_to_howto_rel, elf_arc_relocate_section): Likwise.
	(elf_arc_check_relocs): Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Invoke aout N_* macros with pointer to struct internal_exec
@ 2015-12-01  3:43 sergiodj+buildbot
  2015-12-02  0:39 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-01  3:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bbb1afc89b5cfa2f09b6a7c25fbfef745fbdd724 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: bbb1afc89b5cfa2f09b6a7c25fbfef745fbdd724

Invoke aout N_* macros with pointer to struct internal_exec

No functional changes here.

BTW, some of these headers don't seem to be used anywhere:
include/aout/dynix3.h, include/aout/encap.h, include/aout/hp.h,
gas/config/aout_gnu.h

bfd/
	* aout-adobe.c: Invoke aout N_* macros with pointer to
	struct internal_exec.
	* aout-arm.c: Likewise.
	* aout-cris.c: Likewise.
	* aout-target.h: Likewise.
	* aout-tic30.c: Likewise.
	* aoutf1.h: Likewise.
	* aoutx.h: Likewise.
	* bout.c: Likewise.
	* freebsd.h: Likewise.
	* gen-aout.c: Likewise.
	* hp300hpux.c: Likewise.
	* i386aout.c: Likewise.
	* i386linux.c: Likewise.
	* i386lynx.c: Likewise.
	* i386mach3.c: Likewise.
	* i386os9k.c: Likewise.
	* libaout.h: Likewise.
	* m68klinux.c: Likewise.
	* m88kmach3.c: Likewise.
	* mipsbsd.c: Likewise.
	* netbsd.h: Likewise.
	* pc532-mach.c: Likewise.
	* pdp11.c: Likewise.
	* riscix.c: Likewise.
	* sparclinux.c: Likewise.
	* sparclynx.c: Likewise.
gas/
	* config/aout_gnu.h: Invoke aout N_* macros with pointer to
	struct internal_exec.
include/
	* bout.h: Invoke aout N_* macros with pointer to
	struct internal_exec.
	* os9k.h: Likewise.
include/aout/
	* adobe.h: Invoke aout N_* macros with pointer to
	struct internal_exec.
	* aout64.h: Likewise.
	* dynix3.h: Likewise.
	* encap.h: Likewise.
	* hp.h: Likewise.
	* hp300hpux.h: Likewise.
	* sun4.h: Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] ARC port broken reloc processing
@ 2015-12-01  5:47 sergiodj+buildbot
  2015-12-01 20:26 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-01  5:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0a5ff21b13783cef3b26680d1673b1ae37697aeb ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 0a5ff21b13783cef3b26680d1673b1ae37697aeb

ARC port broken reloc processing

This initialises howto.dst_mask so that relocations in debug sections
are applied by the generic reloc processing used by objdump to display
debug sections.

	* elf32-arc.c (arc_elf_howto_init): Init dst_mask.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Trim unused params from aout adjust_sizes_and_vmas
@ 2015-12-01  7:49 sergiodj+buildbot
  2015-12-02  1:41 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-01  7:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3a8c4a5b428c1babd941606c2bbe9cf8a041d9d9 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 3a8c4a5b428c1babd941606c2bbe9cf8a041d9d9

Trim unused params from aout adjust_sizes_and_vmas

	* aoutx.h (adjust_sizes_and_vmas): Remove unused text_size and
	text_end parameters.  Update callers.
	* aout-tic30.c: Update adjust_sizes_and_vmas callers.
	* hp300hpux.c: Likewise.
	* i386lynx.c: Likewise.
	* libaout.h: Likewise.
	* netbsd.h: Likewise.
	* pdp11.c: Likewise.
	* riscix.c: Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Run gdb.base/disp-step-syscall.exp for aarch64-linux
@ 2015-12-01 12:47 sergiodj+buildbot
  2015-12-02  3:55 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-01 12:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 99fd02d9fc9d6cc470d3b81c4cc3439b47bb9419 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 99fd02d9fc9d6cc470d3b81c4cc3439b47bb9419

Run gdb.base/disp-step-syscall.exp for aarch64-linux

This patch handles target aarch64*-*-linux* for syscall instruction.

gdb/testsuite:

2015-12-01  Yao Qi  <yao.qi@linaro.org>

	* gdb.base/disp-step-syscall.exp: Define syscall instruction
	for aarch64*-*-linux* target.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix uninitialized variable warnings in remote.c
@ 2015-12-01 17:17 sergiodj+buildbot
  2015-12-02  5:10 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-01 17:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2e3b657e3a811087533cec33307eb8bbf454cd1c ***

Author: Ulrich Weigand <ulrich.weigand@de.ibm.com>
Branch: master
Commit: 2e3b657e3a811087533cec33307eb8bbf454cd1c

Fix uninitialized variable warnings in remote.c

Fix a couple of places where a struct thread_item was added to a
vector while the item.name field was uninitialized.

gdb/
	* remote.c (remote_newthread_step): Initialize item.name.
	(remote_get_threads_with_qthreadinfo): Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Avoid "operation may be undefined" warning in remote.c
@ 2015-12-01 17:41 sergiodj+buildbot
  2015-12-02  6:12 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-01 17:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 974eac9d7694ca14dcdf6d1a74777a265fffdb95 ***

Author: Ulrich Weigand <ulrich.weigand@de.ibm.com>
Branch: master
Commit: 974eac9d7694ca14dcdf6d1a74777a265fffdb95

Avoid "operation may be undefined" warning in remote.c

GCC 4.1 gives the following warning:
gdb/remote.c: In function 'remote_parse_stop_reply':
gdb/remote.c:6549: warning: operation on 'p' may be undefined
on this line of code:

	event->ptid = read_ptid (++p, &p);

Since p actually isn't used afterwards anyway, simply use NULL.

gdb/
	* remote.c (remote_parse_stop_reply): Avoid GCC 4.1 "operation
	may be undefined" warning.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix ldah being disassembled as ldaexh
@ 2015-12-02  1:41 sergiodj+buildbot
  2015-12-02  7:54 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-02  1:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3395762edd7232d976179b232c93cd901b739367 ***

Author: Andre Vieira <Andre dot SimoesDiasVieira at arm dot com>
Branch: master
Commit: 3395762edd7232d976179b232c93cd901b739367

Fix ldah being disassembled as ldaexh

2015-12-02  Andre Vieira  <andre.simoesdiasvieira@arm.com>

opcodes/
    * arm-dis.c (arm_opcodes): <ldaexh>: Fix typo...
    <ldah>: ... to this.

gas/testsuite/
    * gas/arm/armv8-a.d: <ldaexh>: Rename mismatched mnemonics ...
    <ldah>: ... to this.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix powerpc64 segfault caused by zero r_symndx relocs.
@ 2015-12-02  9:02 sergiodj+buildbot
  2015-12-02  9:47 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-02  9:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c27b8c2aeb369972f4f9f98f390607694c56a127 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: c27b8c2aeb369972f4f9f98f390607694c56a127

Fix powerpc64 segfault caused by zero r_symndx relocs.

Fixes a segfault in ppc64_elf_tls_optimize found when testing
R_PPC64_ENTRY, and potential for trouble in other places found by
code inspection.

	* elf64-ppc.c (ppc64_elf_tls_optimize): Don't segfault on NULL
	symbol section or output section.
	(ppc64_elf_edit_toc): Similarly for ld -R objects.
	(ppc64_elf_size_stubs): Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Run gdb.base/sizeof.exp with board having gdb, noinferiorio
@ 2015-12-03 17:23 sergiodj+buildbot
  2015-12-03 18:19 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-03 17:23 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 41d0efca578f03db2787246a4e0c7bf9b085007c ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 41d0efca578f03db2787246a4e0c7bf9b085007c

Run gdb.base/sizeof.exp with board having gdb,noinferiorio

In my remote cross testing (x86_64 host and aarch64 target), the test
gdb.base/sizeof.exp is skipped because gdb,noinferiorio is defined in
my gdbserver board file.  Tests are skipped because the test checks
the expected value from the program's output, but I don't see why must
do it this way.  With my patch applied, we can save the result in variable
in the program, and check the variable then.  Then, the test doesn't rely
on inferiorio.

gdb/testsuite:

2015-12-03  Yao Qi  <yao.qi@linaro.org>

	* gdb.base/sizeof.c: Don't include stdio.h and
	../lib/unbuffer_output.c.
	(main): New variable 'size' and 'value'.  Remove printf and
	gdb_unbuffer_output.  Assign return value to size and value.
	* gdb.base/sizeof.exp: Remove the checking to gdb,noinferiorio
	at the beginning.
	(check_sizeof): Check the result by printing variable 'size'.
	(check_valueof): Check the result by printing variable 'value'.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Remove duplicate arch/arm.h include in linux-arm-low.c.
@ 2015-12-03 19:14 sergiodj+buildbot
  2015-12-03 20:09 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-03 19:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e58c48b4c81f25ec08174f324990d021aad0e96e ***

Author: Antoine Tremblay <antoine.tremblay@ericsson.com>
Branch: master
Commit: e58c48b4c81f25ec08174f324990d021aad0e96e

Remove duplicate arch/arm.h include in linux-arm-low.c.

A duplicate include arm/arm.h was introduced, remove it.
Pushed as obvious.

gdb/gdbserver/ChangeLog:

	* linux-arm-low.c: Remove duplicate arch/arm.h include.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix failures in the GAS testsuite for the ARC architecture.
@ 2015-12-04 11:08 sergiodj+buildbot
  2015-12-04 12:02 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-04 11:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 24b368f8532b4775f9fd5bcc7958a84d4218aa46 ***

Author: Claudiu Zissulescu <claziss@synopsys.com>
Branch: master
Commit: 24b368f8532b4775f9fd5bcc7958a84d4218aa46

Fix failures in the GAS testsuite for the ARC architecture.

gas	* config/tc-arc.c (arc_option): Sets all internal gas options when
	parsing .cpu directive.
	(declare_register_set): Declare all 64 registers.
	(md_section_align): Refactor.
	(md_pcrel_from_section): Remove assert.
	(pseudo_operand_match): Fix pseudo operand match.
	(find_reloc): Use flags filed, extend matching.
	* config/tc-arc.h (TC_VALIDATE_FIX): Don't fixup any PLT
	relocation.

testsuite	* gas/arc/bic.d: Update test.
	* gas/arc/add_s-err.s: New file.
	* gas/arc/cpu-warn1.s: Likewise.
	* gas/arc/pcl-relocs.d: Likewise.
	* gas/arc/pcl-relocs.s: Likewise.
	* gas/arc/pcrel-relocs.d: Likewise.
	* gas/arc/pcrel-relocs.s: Likewise.
	* gas/arc/pic-relocs.d: Likewise.
	* gas/arc/pic-relocs.s: Likewise.
	* gas/arc/plt-relocs.d: Likewise.
	* gas/arc/plt-relocs.s: Likewise.
	* gas/arc/pseudos.d: Likewise.
	* gas/arc/pseudos.s: Likewise.
	* gas/arc/sda-relocs.d: Likewise.
	* gas/arc/sda-relocs.s: Likewise.
	* gas/arc/sda-relocs2.d: Likewise.
	* gas/arc/sda-relocs2.s: Likewise.
	* gas/arc/tls-relocs.d: Likewise.
	* gas/arc/tls-relocs.s: Likewise.

opcode	* arc.h (arc_reloc_equiv_tab): Replace flagcode with flags[32].

opcodes	* arc-dis.c (special_flag_p): Match full mnemonic.
	* arc-opc.c (print_insn_arc): Check section size to read
	appropriate number of bytes. Fix printing.
	* arc-tbl.h: Fix instruction table. Allow clri/seti instruction without
	arguments.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Remove useless loop in elf.c
@ 2015-12-04 12:02 sergiodj+buildbot
  2015-12-04 13:03 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-04 12:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 461c4b2edee2f0a4ee7dec0001a6fabf46454a24 ***

Author: Tristan Gingold <gingold@adacore.com>
Branch: master
Commit: 461c4b2edee2f0a4ee7dec0001a6fabf46454a24

Remove useless loop in elf.c


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Optimize R_386_GOT32/R_386_GOT32X only if addend is 0
@ 2015-12-04 17:20 sergiodj+buildbot
  2015-12-04 18:13 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-04 17:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 02e2aef89bb58e8e0cc4390db41c5f775e1b7c3e ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 02e2aef89bb58e8e0cc4390db41c5f775e1b7c3e

Optimize R_386_GOT32/R_386_GOT32X only if addend is 0

Linker can't optimize R_386_GOT32 and R_386_GOT32X relocations if addend
isn't 0.  It isn't valid to convert

movl	foo@GOT+1(%ecx), %eax

to

leal	foo@GOTOFF+1(%ecx), %eax

nor to convert

movq	foo@GOTPCREL+1(%rip), %rax

to

leaq	foo(%rip), %rax

for x86-64.  We should check if addend is 0 before optimizing R_386_GOT32
and R_386_GOT32X relocations.  Testcases are added for i386 and x86-64.

bfd/

	* elf32-i386.c (elf_i386_convert_load): Skip if addend isn't 0.
	(elf_i386_relocate_section): Skip R_386_GOT32X optimization if
	addend isn't 0.

ld/testsuite/

	* ld-i386/i386.exp: Run mov2a, mov2b and mov3.
	* ld-i386/mov2.s: New file.
	* ld-i386/mov2a.d: Likewise.
	* ld-i386/mov2b.d: Likewise.
	* ld-i386/mov3.d: Likewise.
	* ld-i386/mov3.s: Likewise.
	* ld-x86-64/mov2.s: Likewise.
	* ld-x86-64/mov2a.d: Likewise.
	* ld-x86-64/mov2b.d: Likewise.
	* ld-x86-64/mov2c.d: Likewise.
	* ld-x86-64/mov2d.d: Likewise.
	* ld-x86-64/x86-64.exp: Run mov2a, mov2b, mov2c and mov2d.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] gdbserver: set ptrace flags after creating inferiors
@ 2015-12-05  2:39 sergiodj+buildbot
  2015-12-05 13:56 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-05  2:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ece66d651004eac0210217c4d48babf4e80d1f2e ***

Author: Josh Stone <jistone@redhat.com>
Branch: master
Commit: ece66d651004eac0210217c4d48babf4e80d1f2e

gdbserver: set ptrace flags after creating inferiors

Rename target_ops.arch_setup to .post_create_inferior.  In the Linux
hook, continue calling the low arch setup, then also set ptrace flags.
This corrects the possibility of running without flags, demonstrated by
a new test that would fail to catch a fork before.

gdb/gdbserver/ChangeLog:

2015-12-04  Josh Stone  <jistone@redhat.com>

	* target.h (struct target_ops) <arch_setup>: Rename to ...
	(struct target_ops) <post_create_inferior>: ... this.
	(target_arch_setup): Rename to ...
	(target_post_create_inferior): ... this, calling post_create_inferior.
	* server.c (start_inferior): Update target_arch_setup calls to
	target_post_create_inferior.
	* linux-low.c (linux_low_ptrace_options): Forward declare.
	(linux_arch_setup): Update its comment for general use.
	(linux_post_create_inferior): New, run arch_setup and setup ptrace.
	(struct linux_target_ops): Use linux_post_create_inferior.
	* lynx-low.c (struct lynx_target_ops): Update arch_setup stub comment
	to post_create_inferior.
	* nto-low.c (struct nto_target_ops): Likewise.
	* spu-low.c (struct spu_target_ops): Likewise.
	* win32-low.c (struct win32_target_ops): Likewise.

gdb/testsuite/ChangeLog:

2015-12-04  Josh Stone  <jistone@redhat.com>

	* gdb.base/catch-fork-static.exp: New.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] bfd: Mark sh5*-*-* and sh64*-*-* targets as obsolete.
@ 2015-12-07  1:11 sergiodj+buildbot
  2015-12-07  2:45 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-07  1:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2b213129c51f4a6c4525120319d9aceb04483ab4 ***

Author: Kaz Kojima <kkojima@rr.iij4u.or.jp>
Branch: master
Commit: 2b213129c51f4a6c4525120319d9aceb04483ab4

bfd: Mark sh5*-*-* and sh64*-*-* targets as obsolete.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Reorder some power9 insns
@ 2015-12-07  3:17 sergiodj+buildbot
  2015-12-07  5:11 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-07  3:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT dd2887fc3de48f6261d34208a0132122f05d7ef4 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: dd2887fc3de48f6261d34208a0132122f05d7ef4

Reorder some power9 insns

The idea being to put instructions that have the same encoding adjacent
to each other.

	* opcodes/ppc-opc.c (powerpc_opcodes): Sort power9 insns by
	major opcode/xop.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] PR19323 memory allocation greater than 4G
@ 2015-12-07  3:33 sergiodj+buildbot
  2015-12-07 10:06 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-07  3:33 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c20f6f63eda61348326a861a155716b8d9073307 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: c20f6f63eda61348326a861a155716b8d9073307

PR19323 memory allocation greater than 4G

On 32-bit targets, memory requested for program/section headers on a
fuzzed binary can wrap to 0.  A bfd_alloc of zero bytes actually
returns a one byte allocation rather than a NULL pointer.  This then
leads to buffer overflows.

Making this check unconditional triggers an extremely annoying gcc-5
warning.

	PR19323
	* elfcode.h (elf_object_p): Check for ridiculous e_shnum and
	e_phnum values.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Add support for MSP430 F5 hardware multiply.
@ 2015-12-07 10:29 sergiodj+buildbot
  2015-12-07 14:47 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-07 10:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f7584f0560f36189ef9434d157e83ffcd988c098 ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: f7584f0560f36189ef9434d157e83ffcd988c098

Add support for MSP430 F5 hardware multiply.

	* msp430-sim.c (sim_open): Check for needed memory at address
	0x500 not 0x200.
	(get_op): Add support for F5 hardware multiply addresses.
	(put_op): Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Enhance the menu to select function overloads with signatures
@ 2015-12-07 12:41 sergiodj+buildbot
  2015-12-07 16:27 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-07 12:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d72413e64a3444868e72e315ba2ceaf5a9d2bf6f ***

Author: Pierre-Marie de Rodat <derodat@adacore.com>
Branch: master
Commit: d72413e64a3444868e72e315ba2ceaf5a9d2bf6f

Enhance the menu to select function overloads with signatures

So far, trying to evaluate an expression involving a function call for
which GDB could find multiple function candidates outputs a menu so that
the user can select the one to run.  For instance, with the two
following functions:

    type New_Integer is new Integer;

    function F (I : Integer) return Boolean;
    function F (I : New_Integer) return Boolean;

Then we get the following GDB session:

    (gdb) print f(1)
    Multiple matches for f
    [0] cancel
    [1] foo.f at foo.adb:23
    [2] foo.f at foo.adb.28
    >

While the source location information is sufficient in order to
determine which one to select, one has to look for them in source files,
which is not convenient.

This commit tunes this menu in order to also include the list of formal
and return types (if any) in each entry.  The above then becomes:

    (gdb) print f(1)
    Multiple matches for f
    [0] cancel
    [1] foo.f (integer) return boolean at foo.adb:23
    [2] foo.f (foo.new_integer) return boolean at foo.adb.28
    >

Since this output is more verbose than previously, this change also
introduces an option (set/show ada print-signatures) to get the original
output.

gdb/ChangeLog:

	* ada-lang.c (print_signatures): New.
	(ada_print_symbol_signature): New.
	(user_select_syms): Add signatures to the output of candidate
	symbols using ada_print_symbol_signature.
	(_initialize_ada_language): Add a "set/show ada
	print-signatures" boolean option.

gdb/testsuite/ChangeLog:

	* gdb.ada/fun_overload_menu.exp: New testcase.
	* gdb.ada/fun_overload_menu/foo.adb: New testcase.

Tested on x86_64-linux, no regression.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix relaxation in RX linker when --no-keep-memory is specified.
@ 2015-12-07 14:59 sergiodj+buildbot
  2015-12-07 17:52 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-07 14:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5ee4a06adea76e607f47eceff65c6bd4a98c49ff ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: 5ee4a06adea76e607f47eceff65c6bd4a98c49ff

Fix relaxation in RX linker when --no-keep-memory is specified.

	* elf32-rx.c (elf32_rx_relax_delete_bytes): Add extra parameter -
	the start of the relocs for the section.  Delete code to load in
	the relocs.
	(elf32_rx_relax_section): Do not free the loaded relocs.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Support Z0 packet in AArch64 multi-arch debugging
@ 2015-12-07 16:13 sergiodj+buildbot
  2015-12-07 18:56 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-07 16:13 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 17b1509aac6ff4205749c2626fddbb1c4d7255f4 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 17b1509aac6ff4205749c2626fddbb1c4d7255f4

Support Z0 packet in AArch64 multi-arch debugging

In commit 6085d6f6, Z0 packet is disabled in aarch64 GDBserver if
the inferior is 32-bit or there may be multiple inferiors, because
Z0 packet isn't supported for arm then.  Recently, Z0 packet
is supported in arm target, so we don't have such limitation in
aarch64 GDBserver, that is to say, aarch64 GDBserver can use Z0
packet in multi-arch/multi-inferior debugging when the inferior's
arch is arm.

Part of this patch is to revert 6085d6f6, and the rest of the patch
is to move some breakpoint related arm_* functions into
linux-aarch32-low.c in order to share them between arm and aarch64.

This patch is regression tested on aarch64-linux for debugging both
aarch64 programs and arm programs respectively.

gdb/gdbserver:

2015-12-07  Yao Qi  <yao.qi@linaro.org>

	* configure.srv: Append arm.o to srv_tgtobj for
	aarch64*-*-linux* target.
	* linux-aarch32-low.c (arm_abi_breakpoint): New macro.  Moved
	from linux-arm-low.c.
	(arm_eabi_breakpoint, arm_breakpoint): Likewise.
	(arm_breakpoint_len, thumb_breakpoint): Likewise.
	(thumb_breakpoint_len, thumb2_breakpoint): Likewise.
	(thumb2_breakpoint_len): Likewise.
	(arm_is_thumb_mode, arm_breakpoint_at): Likewise.
	(arm_breakpoint_kinds): Likewise.
	(arm_breakpoint_kind_from_pc): Likewise.
	(arm_sw_breakpoint_from_kind): Likewise.
	(arm_breakpoint_kind_from_current_state): Likewise.
	* linux-aarch32-low.h (arm_breakpoint_kind_from_pc): Declare.
	(arm_sw_breakpoint_from_kind): Declare.
	(arm_breakpoint_kind_from_current_state): Declare.
	(arm_breakpoint_at): Declare.
	* linux-aarch64-low.c (aarch64_sw_breakpoint_from_kind): Call
	arm_sw_breakpoint_from_kind if process is 32-bit.
	(aarch64_breakpoint_kind_from_pc): New function.
	(aarch64_breakpoint_kind_from_current_state): New function.
	(the_low_target): Initialize fields breakpoint_kind_from_pc
	and breakpoint_kind_from_current_state.
	* linux-arm-low.c (arm_breakpoint_kinds): Move to
	linux-aarch32-low.c.
	(arm_abi_breakpoint, arm_eabi_breakpoint): Likewise.
	(arm_breakpoint, arm_breakpoint_len): Likewise.
	(thumb_breakpoint, thumb_breakpoint_len): Likewise.
	(thumb2_breakpoint, thumb2_breakpoint_len): Likewise.
	(arm_is_thumb_mode): Likewise.
	(arm_breakpoint_at): Likewise.
	(arm_breakpoint_kind_from_pc): Likewise.
	(arm_sw_breakpoint_from_kind): Likewise.
	(arm_breakpoint_kind_from_current_state): Likewise.

	Revert:
	2015-08-04  Yao Qi  <yao.qi@linaro.org>

	* linux-aarch64-low.c (aarch64_supports_z_point_type): Return
	0 for Z_PACKET_SW_BP if it may be used in multi-arch debugging.
	* server.c (extended_protocol): Remove "static".
	* server.h (extended_protocol): Declare it.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] rl78: Enable MULU for all ISAs.
@ 2015-12-08  5:32 sergiodj+buildbot
  2015-12-08  5:57 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-08  5:32 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1eac08cc37b3d8a42a1b81de888b29d079b0608e ***

Author: DJ Delorie <dj@redhat.com>
Branch: master
Commit: 1eac08cc37b3d8a42a1b81de888b29d079b0608e

rl78: Enable MULU for all ISAs.

Unlike other mul/div opcodes, MULU is available on all variants
of the RL78.

* rl78-decode.opc: Enable MULU for all ISAs.
* rl78-decode.c: Regenerate.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] rl78: relaxation fixes
@ 2015-12-08  7:01 sergiodj+buildbot
  2015-12-08  8:09 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-08  7:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e896287c1643b8b47080c4a8ddbe9a92d9fa585b ***

Author: DJ Delorie <dj@redhat.com>
Branch: master
Commit: e896287c1643b8b47080c4a8ddbe9a92d9fa585b

rl78: relaxation fixes

Various fixes to linker relaxation.  In general, we need to support
relaxing every branch, even if we don't relax it in the assembler,
so we can optionally defer relaxation to the linker.

* elf32-rl78.c (rl78_offset_for_reloc): Add more relocs.
(rl78_elf_relax_section): Add bc/bz/bnc/bnz/bh/bnh.  Fix reloc
choices.

* config/rl78-parse.y: Make all branches relaxable via
rl78_linkrelax_branch().
* config/tc-rl78.c (rl78_linkrelax_branch): Mark all relaxable
branches with relocs.
(options): Add OPTION_NORELAX.
(md_longopts): Add -mnorelax.
(md_parse_option): Support OPTION_NORELAX.
(op_type_T): Add bh, sk, call, and br.
(rl78_opcode_type): Likewise.
(rl78_relax_frag): Fix not-relaxing logic.  Add sk.
(md_convert_frag): Fix relocation handling.
(tc_gen_reloc): Strip relax relocs when not linker relaxing.
(md_apply_fix): Defer overflow handling for anything that needs a
PLT, to the linker.
* config/tc-rl78.h (TC_FORCE_RELOCATION): Force all relocations to
the linker when linker relaxing.
* doc/c-rl78.texi (norelax): Add.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] DOCO: Enhance the menu to select function overloads with signatures
@ 2015-12-08  9:14 sergiodj+buildbot
  2015-12-08  9:46 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-08  9:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3685b09fb85dc279762e19df310dc2f30e64b044 ***

Author: Pierre-Marie de Rodat <derodat@adacore.com>
Branch: master
Commit: 3685b09fb85dc279762e19df310dc2f30e64b044

DOCO: Enhance the menu to select function overloads with signatures

gdb/ChangeLog:

	* NEWS: Announce this enhancement and the corresponding new
	option.

gdb/doc/ChangeLog:

	* gdb.texinfo (Ada Mode Into): Move overloading support
	description to its own node.
	(Overloading support for Ada): New node.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] varobj zero-padded hexadecimal format
@ 2015-12-09 13:15 sergiodj+buildbot
  2015-12-09 14:02 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-09 13:15 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1c35a88f1d8399902c08a8334d3e3303df833538 ***

Author: Luis Machado <lgustavo@codesourcery.com>
Branch: master
Commit: 1c35a88f1d8399902c08a8334d3e3303df833538

varobj zero-padded hexadecimal format

This set of patches add support for the zero-padded hexadecimal format for
varobj's, defined as "zero-hexadecimal".  We currently only support regular
non-zero-padded hexadecimal.

Talking with IDE developers, they would like to have this option that is
already available to GDB's print/x commands, in the CLI, as 'z'.

gdb/ChangeLog:

2015-12-09  Luis Machado  <lgustavo@codesourcery.com>

	* gdb/mi/mi-cmd-var.c (mi_parse_format): Handle new "zero-hexadecimal"
	format.
	* gdb/varobj.c (varobj_format_string): Add "zero-hexadecimal" entry.
	(format_code): Add 'z' entry.
	(varobj_set_display_format): Handle FORMAT_ZHEXADECIMAL.
	* gdb/varobj.h (varobj_display_formats) <FORMAT_ZHEXADECIMAL>: New enum
	field.
	* NEWS: Add new note to MI changes citing the new zero-hexadecimal
	format for -var-set-format.

gdb/doc/ChangeLog:

2015-12-09  Luis Machado  <lgustavo@codesourcery.com>

	* gdb.texinfo (GDB/MI Variable Objects): Update text to mention
	-var-set-format's new zero-hexadecimal format.

gdb/testsuite/ChangeLog:

2015-12-09  Luis Machado  <lgustavo@codesourcery.com>

	* gdb.mi/mi-var-display.exp: Add new checks for the zero-hexadecimal
	  format and change test names to make them unique.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
[parent not found: <8eab413676a0222a863f45ff606f3db69bb7afc4@gdb-build>]
* [binutils-gdb] gdb.base/async.exp: Handle "asynchronous execution not supported"
@ 2015-12-09 16:51 sergiodj+buildbot
  2015-12-09 18:13 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-09 16:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5fc2beac27f81d0840e717e3dd8d6524f9c2e890 ***

Author: Kevin Buettner <kevinb@redhat.com>
Branch: master
Commit: 5fc2beac27f81d0840e717e3dd8d6524f9c2e890

gdb.base/async.exp: Handle "asynchronous execution not supported"

This change eliminates some failures on simulator targets and makes
the test run a bit quicker too - without this change, we have to wait
for timeouts.

gdb/testsuite/ChangeLog:

	* gdb.base/async.exp (proc test_background): Add case
	for asynchronous execution not supported.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix GOT address computations in initial PLT entries for nios2.
@ 2015-12-10  0:31 sergiodj+buildbot
  2015-12-10  1:15 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-10  0:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 33d4099fc891760ea1f080746dee4dcfc36c757c ***

Author: Sandra Loosemore <sandra@codesourcery.com>
Branch: master
Commit: 33d4099fc891760ea1f080746dee4dcfc36c757c

Fix GOT address computations in initial PLT entries for nios2.

2015-12-09  Sandra Loosemore  <sandra@codesourcery.com>

	bfd/
	* elf32-nios2.c (nios2_elf32_finish_dynamic_sections): Correct
	%hiadj/%lo computations for _GLOBAL_OFFSET_TABLE_ in initial
	PLT entries.  Assert alignment requirements.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] gdb: Handle multiple base address in debug_ranges data.
@ 2015-12-10 10:15 sergiodj+buildbot
  2015-12-10 10:54 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-10 10:15 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 28d2bfb9c3e519a3b7619bbe5d061ebe520750ef ***

Author: Andrew Burgess <andrew.burgess@embecosm.com>
Branch: master
Commit: 28d2bfb9c3e519a3b7619bbe5d061ebe520750ef

gdb: Handle multiple base address in debug_ranges data.

It is possible to use multiple base addresses within a single address
range series, within the .debug_ranges section.  The following is a
simplified example for 32-bit addresses:

  .section ".debug_ranges"
  .4byte	0xffffffff
  .4byte	BASE_1
  .4byte	START_OFFSET_1
  .4byte	END_OFFSET_1
  .4byte	START_OFFSET_2
  .4byte	END_OFFSET_2
  .4byte	0xffffffff
  .4byte	BASE_2
  .4byte	START_OFFSET_3
  .4byte	END_OFFSET_3
  .4byte	0
  .4byte	0

In this example START/END 1 and 2 are relative to BASE_1, while
START/END 3 are relative to BASE_2.

Currently gdb does not correctly parse this DWARF, resulting in
corrupted address range information.  This commit fixes this issue, and
adds a new test to cover this case.

In order to support testing of this feature extensions were made to the
testsuite dwarf assembler, additional functionality was added to the
.debug_line generation function, and a new function for generating the
.debug_ranges section was added.

gdb/ChangeLog:

	* dwarf2read.c (dwarf2_ranges_read): Unify and fix base address
	reading code.

gdb/testsuite/ChangeLog:

	* gdb.dwarf2/dw2-ranges-base.c: New file.
	* gdb.dwarf2/dw2-ranges-base.exp: New file.
	* lib/dwarf.exp (namespace eval Dwarf): Add new variables to
	support additional line table, and debug ranges generation.
	(Dwarf::ranges): New function, generate .debug_ranges.
	(Dwarf::lines): Support generating simple line table programs.
	(Dwarf::assemble): Initialise new namespace variables.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [AArch64] Fix ARMv8.1 and ARMv8.2 feature settings.
@ 2015-12-10 14:24 sergiodj+buildbot
  2015-12-10 14:57 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-10 14:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT af117b3cf1877da805d081b93f606f3dd8153502 ***

Author: Matthew Wahab <matthew.wahab@arm.com>
Branch: master
Commit: af117b3cf1877da805d081b93f606f3dd8153502

[AArch64] Fix ARMv8.1 and ARMv8.2 feature settings.

ARMv8.1 includes CRC as a required extension but this isn't reflected in
the features enabled by -march=armv8.1-a. The FP16 feature modifier also
clashes with AARCH64_FEATURE_V8_1 and the list of features for ARMv8.2
is missing ARMv8.1 features.

This patch enables +crc for -march values of armv8.1-a and later. It
also fixes the values for AARCH64_FEATURE_F16 and makes
AARCH64_ARCH_V8_2 and superset of AARCH64_ARCH_V8_2.

gas/
2015-12-10  Matthew Wahab  <matthew.wahab@arm.com>

	* doc/c-aarch64.texi (AArch64 Extensions): Update entry for crc.

include/opcode
2015-12-10  Matthew Wahab  <matthew.wahab@arm.com>

	* aarch64.h (AARCH64_FEATURE_F16): Fix clash with
	AARCH64_FEATURE_V8_1.
	(AARCH64_ARCH_V8_1): Add AARCH64_FEATURE_CRC.
	(AARCH64_ARCH_V8_2): Add AARCH64_FEATURE_CRC and
	AARCH64_FEATURE_V8_1.

Change-Id: I8af5369f6df2430b28f6cec92870d2a4d14a7431


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [AArch64][PATCH 1/2] Add support for RAS instruction ESB.
@ 2015-12-10 14:57 sergiodj+buildbot
  2015-12-10 16:00 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-10 14:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c8a6db6fa0b06b978e5b63593a6b0cb3300ad259 ***

Author: Matthew Wahab <matthew.wahab@arm.com>
Branch: master
Commit: c8a6db6fa0b06b978e5b63593a6b0cb3300ad259

[AArch64][PATCH 1/2] Add support for RAS instruction ESB.

The ARMv8.2 RAS extension adds a new barrier instruction ESB as an alias
and the preferred form of HINT 16.

This patch adds an architectural feature flag for the RAS extension and
includes it in the features selected enabled by -march=armv8.2-a. It
also adds the ESB instruction, making it available whenever the RAS
feature is enabled.

Because ESB is the preferred form and because the target architecture
isn't available to the disassembler, HINT 16 will be disassembled as ESB
even when the target has no support for the RAS extension.

gas/testsuite/
2015-12-10  Matthew Wahab  <matthew.wahab@arm.com>

	* gas/aarch64/system-2.d: New.
	* gas/aarch64/system-2.s: New.
	* gas/aarch64/system.d: Adjust expected output for HINT 16.

include/opcode/
2015-12-10  Matthew Wahab  <matthew.wahab@arm.com>

	* aarch64.h (AARCH64_FEATURE_RAS): New.
	(AARCH64_ARCH_V8_2): Add AARCH64_FEATURE_RAS.

opcodes/
2015-12-10  Matthew Wahab  <matthew.wahab@arm.com>

	* aarch64-asm-2.c: Regenerate.
	* aarch64-dis-2.c: Regenerate.
	* aarch64-tbl.h (aarch64_feature_ras): New.
	(RAS): New.
	(aarch64_opcode_table): Add "esb".

Change-Id: Id4713917da15cca3b977284f43febd1c9b3d9faf


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [AArch64][PATCH 2/2] Add RAS system registers.
@ 2015-12-10 15:18 sergiodj+buildbot
  2015-12-10 17:05 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-10 15:18 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 47f8114261a50dcb44bd3be355b705e37d920944 ***

Author: Matthew Wahab <matthew.wahab@arm.com>
Branch: master
Commit: 47f8114261a50dcb44bd3be355b705e37d920944

[AArch64][PATCH 2/2] Add RAS system registers.

The ARMv8.2 RAS extension adds a number of new registers. This patch
adds the registers and makes them available whenever the RAS extension
is enabled, as it is when -march=armv8.2-a is selected.

The new registers are:
    erridr_el1, errselr_el1, erxfr_el1, erxctlr, erxaddr_el1,
    erxmisc0_el1, erxmisc1_el1, vsesr_el2, disr_el1 and
    vdisr_el2.

gas/testsuite/
2015-12-10  Matthew Wahab  <matthew.wahab@arm.com>

	* gas/aarch64/sysreg-2.d: Add tests for new registers.
	* gas/aarch64/sysreg-2.s: Likewise.  Also replace some spaces with
	tabs.

opcodes/
2015-12-10  Matthew Wahab  <matthew.wahab@arm.com>

	* aarch64-opc.c (aarch64_sys_regs): Add "vsesr_el2", "erridr_el1",
	"errselr_el1", "erxfr_el1", "erxctlr", "erxaddr_el1",
	"erxmisc0_el1", "erxmisc1_el1", "disr_el1" and "vdisr_el2".
	(aarch64_sys_reg_supported_p): Add architecture feature tests for
	new registers.

Change-Id: I8a01a0f0ee7987f89eead32650f6afcc749b3c74


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Remove support for thread events without PTRACE_EVENT_CLONE in GDB
@ 2015-12-10 16:00 sergiodj+buildbot
  2015-12-10 18:14 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-10 16:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c2c2a31fdb228d41ce3db62b268efea04bd39c18 ***

Author: Antoine Tremblay <antoine.tremblay@ericsson.com>
Branch: master
Commit: c2c2a31fdb228d41ce3db62b268efea04bd39c18

Remove support for thread events without PTRACE_EVENT_CLONE in GDB

Before, on systems that did not support PTRACE_EVENT_CLONE, both GDB and
GDBServer coordinated with libthread_db.so to insert breakpoints at magic
locations in libpthread.so, in order to break at thread creation and
thread death.

Support for thread events was removed from GDBServer as patch:
https://sourceware.org/ml/gdb-patches/2015-11/msg00466.html

This patch removes support for thread events in GDB.

No regressions found on Ubuntu 14.04 x86_64.

gdb/ChangeLog:

	* breakpoint.c (remove_thread_event_breakpoints): Remove.
	* breakpoint.h (remove_thread_event_breakpoints): Remove
	declaration.
	* linux-nat.c (in_pid_list_p): Remove.
	(lin_lwp_attach_lwp): Remove.
	* linux-nat.h (lin_lwp_attach_lwp): Remove declaration.
	* linux-thread-db.c (thread_db_use_events): Remove.
	(struct thread_db_info) <td_create_bp_addr>: Remove.
	<td_death_bp_addr>: Likewise.
	<td_ta_event_addr_p>: Likewise.
	<td_ta_set_event_p>: Likewise.
	<td_ta_clear_event_p>: Likewise.
	<td_ta_event_getmsg_p>: Likewise.
	<td_thr_event_enable_p>: Likewise.
	(attach_thread): Likewise.
	(detach_thread): Likewise.
	(have_threads_callback): Likewise.
	(have_threads): Likewise.
	(enable_thread_event): Likewise.
	(enable_thread_event_reporting): Likewise.
	(try_thread_db_load_1): Remove td_ta_event_addr, td_ta_set_event,
	td_ta_clear_event, td_ta_event_getmsg, td_thr_event_enable
	initializations.
	(try_thread_db_load_1): Remove enable_thread_event_reporting call.
	(disable_thread_event_reporting): Remove.
	(record_thread): Adapt to thread_db_use_event removal.
	(detach_thread): Remove.
	(thread_db_detach): Adapt to thread_db_use_event removal.
	(check_event): Remove.
	(thread_db_wait): Adapt to thread events support removal.
	(thread_db_mourn_inferior): Likewise.
	(find_new_threads_callback): Likewise.
	(find_new_threads_once): Likewise.
	(thread_db_update_thread_list): Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Stop using nowarnings in gdb/testsuite/gdb.multi/
@ 2015-12-17  0:22 sergiodj+buildbot
  2015-12-17  0:58 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-17  0:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 762f774785f4ef878ac4c831e1f4733dc957234d ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 762f774785f4ef878ac4c831e1f4733dc957234d

Stop using nowarnings in gdb/testsuite/gdb.multi/

Several of the gdb.multi tests use the "nowarnings" option to suppress
warnings.  The warnings in question all come from missing headers,
like e.g.:

 src/gdb/testsuite/gdb.multi/multi-arch-exec.c:28:3: warning: incompatible implicit declaration of built-in function 'exit' [enabled by default]
    exit (1);
    ^

There's no point in trying to avoid to include standard headers.  In
gdb.base/hangout.c's case, it's even dangerous, as that file calls
printf.  In order to compile a call to a variatic function correctly,
a declaration must be visible.

gdb/testsuite/ChangeLog:
2015-12-10  Pedro Alves  <palves@redhat.com>

	* gdb.multi/base.exp: Don't use nowarnings.
	* gdb.multi/bkpt-multi-exec.exp: Don't use nowarnings.
	* gdb.multi/hangout.c: Include stdio.h.
	* gdb.multi/hello.c: Include stdlib.h.
	* gdb.multi/multi-arch-exec.c: Include stdlib.h.
	* gdb.multi/multi-arch-exec.exp: Don't use nowarnings.
	* gdb.multi/multi-arch.exp: Don't use nowarnings.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [AArch64][PATCH 2/2] Support ARMv8.2 DC CVAP instruction.
@ 2015-12-17  1:10 sergiodj+buildbot
  2015-12-17  3:12 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-17  1:10 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d6bf7ce6c26cd31fe744419269dea999a3faaf8c ***

Author: Matthew Wahab <matthew.wahab@arm.com>
Branch: master
Commit: d6bf7ce6c26cd31fe744419269dea999a3faaf8c

[AArch64][PATCH 2/2] Support ARMv8.2 DC CVAP instruction.

ARMv8.2 adds the new system instruction DC CVAP. This patch adds support
for the instruction to binutils, enabled when -march=armv8.2-a is
selected.

gas/
2015-12-10  Matthew Wahab  <matthew.wahab@arm.com>

	* config/tc-aarch64.c (parse_sys_ins_reg): Add check of
	architectural support for system register.

gas/testsuite/
2015-12-10  Matthew Wahab  <matthew.wahab@arm.com>

	* gas/aarch64/sysreg-2.d: Add tests for dc instruction.
	* gas/aarch64/sysreg-2.s: Add uses of dc instruction.

include/opcode/
2015-12-10  Matthew Wahab  <matthew.wahab@arm.com>

	* aarch64.h (aarch64_sys_ins_reg_supported_p): Declare.

opcodes/
2015-12-10  Matthew Wahab  <matthew.wahab@arm.com>

	* aarch64-opc.c (aarch64_sys_regs_dc): Add "cvap".
	(aarch64_sys_ins_reg_supported_p): New.

Change-Id: I3158b97d9bbee9644c2d0e2986db807412ef1053


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix regression revealed by corethreads.exp
@ 2015-12-17  1:39 sergiodj+buildbot
  2015-12-17  6:17 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-17  1:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 60269a4a36a78063d7563a32a6d34107cb52cca5 ***

Author: Antoine Tremblay <antoine.tremblay@ericsson.com>
Branch: master
Commit: 60269a4a36a78063d7563a32a6d34107cb52cca5

Fix regression revealed by corethreads.exp

This patch fixes a regression introduced by:
https://sourceware.org/ml/gdb-patches/2015-12/msg00192.html

We can't use thread_from_lwp with core files.  As mentioned in a comment,
td_ta_map_lwp2thr uses ps_get_thread_area, but we can't use that
currently on core targets, as it uses ptrace directly.

Use directly record_thread instead.

This fixes :
PASS -> FAIL: gdb.threads/corethreads.exp: thread0 found
PASS -> FAIL: gdb.threads/corethreads.exp: thread1 found

gdb/ChangeLog:

	* linux-thread-db.c (find_new_threads_callback): Use record_thread.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [AArch64][Patch 2/5] Add Statistical Profiling Extension system registers.
@ 2015-12-17  2:06 sergiodj+buildbot
  2015-12-17  9:20 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-17  2:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 55c144e691ec05a7b8231b5c58dc6d6659a1c4eb ***

Author: Matthew Wahab <matthew.wahab@arm.com>
Branch: master
Commit: 55c144e691ec05a7b8231b5c58dc6d6659a1c4eb

[AArch64][Patch 2/5] Add Statistical Profiling Extension system registers.

The Statistical Profile extension included in the ARMv8.2 architecture
adds a number of system registers. This patch adds the registers to
binutils, making them available when the architecture extension
"+profile" is enabled.

opcodes/
2015-12-11  Matthew Wahab  <matthew.wahab@arm.com>

	* aarch64-opc.c (aarch64_sys_reg): Add pbmlimitr_el1, pmbptr_el1,
	pmbsr_el1, pmbidr_el1, pmscr_el1, pmsicr_el1, pmsirr_el1,
	pmsfcr_el1, pmsevfr_el1, pmslatfr_el1, pmsidr_el1, pmscr_el2 and
	pmscr_el2.
	(aarch64_sys_reg_supported_p): Add architecture feature tests for
	the new registers.

gas/testsuite/
2015-12-11  Matthew Wahab  <matthew.wahab@arm.com>

	* gas/aarch64/sysreg-2.s: Add tests for the statistical profiling
	system registers.
	* gas/aarch64/sysreg-2.d: Enable the statistical profiling
	extension and update the expected output.

Change-Id: Ibf23ad34db7c33f0fcd30010b796748b38be6efb


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [AArch64][Patch 4/5] Support HINT aliases taking operands.
@ 2015-12-17  2:22 sergiodj+buildbot
  2015-12-17 11:23 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-17  2:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9ed608f98b2c8c483c994f884429420e74835417 ***

Author: Matthew Wahab <matthew.wahab@arm.com>
Branch: master
Commit: 9ed608f98b2c8c483c994f884429420e74835417

[AArch64][Patch 4/5] Support HINT aliases taking operands.

The Statistical Profile Extension adds the instruction PSB CSYNC as an
alias for the HINT #17 instruction. This patch adds support for aliases
of HINT which take an operand, adding a table to store operand names and
their matching hint number as well as encoding and decoding functions
for such operands. Parsing and printing the operands are deferred to any
support added for aliases with such operands.

include/opcode/
2015-12-11  Matthew Wahab  <matthew.wahab@arm.com>

	* aarch64.h (aarch64_hint_options): Declare.
	(aarch64_opnd_info): Add field hint_option.

opcodes/
2015-12-11  Matthew Wahab  <matthew.wahab@arm.com>

	* aarch64-asm.c (aarch64_ins_hint): New.
	* aarch64-asm.h (aarch64_ins_hint): Declare.
	* aarch64-dis.c (aarch64_ext_hint): New.
	* aarch64-dis.h (aarch64_ext_hint): Declare.
	* aarch64-opc-2.c: Regenerate.
	* aarch64-opc.c (aarch64_hint_options): New.
	* aarch64-tbl.h (AARCH64_OPERANDS): Fix typos.

Change-Id: I2205038fc1c47d3025d1f0bc2fbf405b5575b287


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [AArch64][Patch 5/5] Add instruction PSB CSYNC
@ 2015-12-17  2:31 sergiodj+buildbot
  2015-12-17 12:33 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-17  2:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1e6f4800fc01c7957d0688158385aba3bf5ce8de ***

Author: Matthew Wahab <matthew.wahab@arm.com>
Branch: master
Commit: 1e6f4800fc01c7957d0688158385aba3bf5ce8de

[AArch64][Patch 5/5] Add instruction PSB CSYNC

The Statistical Profile Extension adds the instruction PSB CSYNC as an
alias for the HINT #17 instruction. This patch adds the instruction to
binutils as a HINT alias that takes an operand.

A new operand type, AARCH64_OPND_BARRIER_PSB, is added to represent the
operand to PSB. A parser for the operand type is added to the assembler
and a printer to the disassembler. The operand name "csync" is added to
the list of HINT options with HINT number #17. Encoding and decoding of
the operand is handled by the ins_hint/ext_hint functions added in the
preceding patches.

gas/
2015-12-11  Matthew Wahab  <matthew.wahab@arm.com>

	* config/tc-aarch64.c (aarch64_hint_opt_hsh): New.
	(parse_barrier_psb): New.
	(parse_operands): Add case for AARCH64_OPND_BARRIER_PSB.
	(md_begin): Set up aarch64_hint_opt_hsh.

gas/testsuite/
2015-12-11  Matthew Wahab  <matthew.wahab@arm.com>

	* gas/aarch64/system-2.d: Enable the statistical profiling
	extension.  Update the expected output.
	* gas/aarch64/system-2.s: Add tests for PSB CSYNC.
	* gas/aarch64/system.d: Update the expected output.

include/opcode/
2015-12-11  Matthew Wahab  <matthew.wahab@arm.com>

	* aarch64.h (aarch64_opnd): Add AARCH64_OPND_BARRIER_PSB.
	* aarch64-asm-2.c: Regenerate.
	* aarch64-dis-2.c: Regenerate.
	* aarch64-opc-2.c: Regenerate.
	* aarch64-opc.c (aarch64_hint_options): Add "csync".
	(aarch64_print_operands): Handle AARCH64_OPND_BARRIER_PSB.
	* aarch64-tbl.h (aarch64_feature_stat_profile): New.
	(STAT_PROFILE): New.
	(aarch64_opcode_table): Add "psb".
	(AARCH64_OPERANDS): Add "BARRIER_PSB".

Change-Id: I5ffb672d26a8b15b48785478d359350a9b70ca09


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Use arm_eabi_breakpoint on aarch32
@ 2015-12-17  2:39 sergiodj+buildbot
  2015-12-17 13:27 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-17  2:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b37a6290beb90f4f65f1513626205f7bac695624 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: b37a6290beb90f4f65f1513626205f7bac695624

Use arm_eabi_breakpoint on aarch32

Nowdays, GDBserver chooses arm breakpoint instructions by checking
macro __ARM_EABI__.  When aarch64 GDBserver debugs arm program,
arm_eabi_breakpoint is still needed, but __ARM_EABI__ isn't defined
in aarch64 compiler.  This causes GDBserver chooses the wrong
breakpoint instruction for arm program.  This patch fixes it.

gdb/gdbserver:

2015-12-11  Yao Qi  <yao.qi@linaro.org>

	* linux-aarch32-low.c [__aarch64__]: Use arm_abi_breakpoint
	arm breakpoint.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Understand arm breakpoints in aarch64_breakpoint_at
@ 2015-12-17  2:47 sergiodj+buildbot
  2015-12-17 14:31 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-17  2:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT db91f50261d30e66350281d18759aa7490672a34 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: db91f50261d30e66350281d18759aa7490672a34

Understand arm breakpoints in aarch64_breakpoint_at

AArch64 GDBserver can debug ARM program, and it should recognize
various arm breakpoint instructions.  This patch should be included
in 17b1509a.

gdb/gdbserver:

2015-12-11  Yao Qi  <yao.qi@linaro.org>

	* linux-aarch64-low.c (aarch64_breakpoint_at): Call
	arm_breakpoint_at if the process is 32-bit.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] ld -r doesn't need plugin for slim lto object
@ 2015-12-17  2:50 sergiodj+buildbot
  2015-12-17  7:19 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-17  2:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c5847ba7267b6eedd4b750f5eeece3ec037a27fd ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: c5847ba7267b6eedd4b750f5eeece3ec037a27fd

ld -r doesn't need plugin for slim lto object

Plugin isn't required on slim lto object for relocatable link.

bfd/

	PR ld/19317
	* linker.c (_bfd_generic_link_add_one_symbol): Don't complain
	plugin needed to handle slim lto object for relocatable link.

ld/testsuite/

	PR ld/19317
	* ld-plugin/lto.exp (lto_no_fat): New.
	(lto_link_tests): Add a test for PR ld/19317.
	(lto_run_tests): Likewise.
	(run_ld_link_tests): Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] gdb: Make lines_to_list variable static.
@ 2015-12-17  3:07 sergiodj+buildbot
  2015-12-17 16:31 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-17  3:07 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f43f85715ac097b6ff4bfaed00879eb541428c1a ***

Author: Andrew Burgess <andrew.burgess@embecosm.com>
Branch: master
Commit: f43f85715ac097b6ff4bfaed00879eb541428c1a

gdb: Make lines_to_list variable static.

Small clean up, make variable static.

gdb/ChangeLog:

	* source.c (lines_to_list): Make static.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] gdb: Use NULL instead of 0 for pointer comparison.
@ 2015-12-17  3:12 sergiodj+buildbot
  2015-12-17 17:40 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-17  3:12 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8c05462adbc01f0aba946c42422146ccca2ae4db ***

Author: Andrew Burgess <andrew.burgess@embecosm.com>
Branch: master
Commit: 8c05462adbc01f0aba946c42422146ccca2ae4db

gdb: Use NULL instead of 0 for pointer comparison.

Small code cleanup, use NULL instead of 0 when checking pointers.  There
should be no user visible changes after this commit.

gdb/ChangeLog:

	* cli/cli-cmds.c (list_command): Use NULL instead of 0 when
	checking pointers.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] gdb: Small code restructure for list_command.
@ 2015-12-17  3:20 sergiodj+buildbot
  2015-12-17 18:45 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-17  3:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1a48ce76774633e9e27dd245ba275a714b2b339f ***

Author: Andrew Burgess <andrew.burgess@embecosm.com>
Branch: master
Commit: 1a48ce76774633e9e27dd245ba275a714b2b339f

gdb: Small code restructure for list_command.

Move handling of special +/- arguments to the list_command function
inside a single if block, this helps group all related functionality
together.  There should be no user visible changes after this commit.

gdb/ChangeLog:

	* cli/cli-cmds.c (list_command): Move all handling of +/-
	arguments into a single if block.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] gdb: 'list' command, tweak handling of +/- arguments.
@ 2015-12-17  3:37 sergiodj+buildbot
  2015-12-17 20:50 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-17  3:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a0def019aaf79adf3add2a0559ab75bb84d72085 ***

Author: Andrew Burgess <andrew.burgess@embecosm.com>
Branch: master
Commit: a0def019aaf79adf3add2a0559ab75bb84d72085

gdb: 'list' command, tweak handling of +/- arguments.

There is an inconsistency with the handling of the special +/- arguments
to the list command.

For the very first time that list is used (after the inferior has
changed locations) then only the first character of the argument string
is checked, so 'list +BLAH' will operate as 'list +' and 'list -----FOO'
will operate as 'list -'.  This compares to each subsequent use of list,
where the whole argument string is checked, so 'list +BLAH' will try to
list lines of code around the function '+BLAH'.

This commit unifies the behaviour so that the whole argument string is
checked, in order to list the next 10, or previous 10 lines from a file
only 'list +' and 'list -' are now valid.

gdb/ChangeLog:

	* cli/cli-cmds.c (list_command): Check that the argument string is
	a single character, either '+' or '-'.

gdb/testsuite/ChangeLog:

	* gdb.base/list.exp (test_list_invalid_args): New function,
	defined, and called.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] gdb: Add an error when 'list -' reaches the start of a file.
@ 2015-12-17  3:46 sergiodj+buildbot
  2015-12-17 21:53 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-17  3:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3b2464a8d39b8b787664438253b8fdf7625cac32 ***

Author: Andrew Burgess <andrew.burgess@embecosm.com>
Branch: master
Commit: 3b2464a8d39b8b787664438253b8fdf7625cac32

gdb: Add an error when 'list -' reaches the start of a file.

When a a user uses 'list +' to list forward through a source file they
eventually reach the end of the source file.  Subsequent uses of 'list
+' result in an error message like this, that let the user know they are
at the end of the source file:

  Line number XXX out of range; FILENAME has YYY lines.

Compare this to the current behaviour of 'list -' which lists backwards
through a source file.  When the user reaches the beginning of the
source file, subsequent uses of 'list -' result in the command silently
returning.  This can be confusing if the previous uses of 'list -' have
scrolled off the users display, the user receives no reminder that the
have already seen the start of the file.

After this commit a use of 'list -' when the user has already seen the
start of a file will receive the following error:

   Already at the start of FILENAME.

gdb/ChangeLog:

	* cli/cli-cmds.c (list_command): Add an error when trying to use
	'-' to scan read off the start of the source file.

gdb/testsuite/ChangeLog:

	* gdb.base/list.exp (test_list_forward): Add end of file error
	test.
	(test_repeat_list_command): Add end of file error test.
	(test_list_backwards): Add beginning of file error test.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Enable 2 operand form of powerpc mfcr with -many
@ 2015-12-17  4:03 sergiodj+buildbot
  2015-12-18  0:01 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-17  4:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b817670b52b7414d592cbfd96fd77cf725a33413 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: b817670b52b7414d592cbfd96fd77cf725a33413

Enable 2 operand form of powerpc mfcr with -many

This is a workaround for a gcc bug.

	PR 19359
	* ppc-opc.c (insert_fxm): Remove "ignored" from error message.
	(powerpc_opcodes): Remove single-operand mfcr.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] gdb: Use TYPE_LENGTH macro
@ 2015-12-17  4:11 sergiodj+buildbot
  2015-12-18  1:04 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-17  4:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 132874d7e3c94d8cc6f865b57f286cf62e5ad0b8 ***

Author: Andrew Burgess <andrew.burgess@embecosm.com>
Branch: master
Commit: 132874d7e3c94d8cc6f865b57f286cf62e5ad0b8

gdb: Use TYPE_LENGTH macro

Fixes a couple of places where we access the length field of the type
structure directly, rather than using the TYPE_LENGTH macro.

gdb/ChangeLog:

	* i386-tdep.c (i386_mpx_info_bounds): Use TYPE_LENGTH.
	(i386_mpx_set_bounds): Likewise.
	* solib-darwin.c (darwin_load_image_infos): Likewise.
	(darwin_solib_read_all_image_info_addr): Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [AArch64] Fix errors rebasing the ARMv8.2 AT and system registers patch
@ 2015-12-17  4:19 sergiodj+buildbot
  2015-12-18  2:27 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-17  4:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6351190792e586b5e80fe0efa0f254b4da0b6705 ***

Author: Matthew Wahab <matthew.wahab@arm.com>
Branch: master
Commit: 6351190792e586b5e80fe0efa0f254b4da0b6705

[AArch64] Fix errors rebasing the ARMv8.2 AT and system registers patch

A mistake with rebasing the ARMv8.2 AT instruction patch left this part

+  /* AT S1E1RP, AT S1E1WP.  Values are from aarch64_sys_regs_at.  */
+  if ((reg->value == CPENS (0, C7, C9, 0)
+       || reg->value == CPENS (0, C7, C9, 1))
+      && !AARCH64_CPU_HAS_FEATURE (features, AARCH64_FEATURE_V8_2))
+    return FALSE;

in aarch64_pstatefield_supported_p rather than in
aarch64_sys_ins_reg_supported_p, where it was supposed to be.

The patch adding support for id_aa64mmfr2_el1, also had the effect of
removing a conditional branch in aarch64_sys_reg_supported_p.

The effect of both of these is to suppress an error if some ARMv8.2
system registers are used with the wrong -march settings.

This patch fixes these mistakes.

opcodes/
2015-12-14  Matthew Wahab  <matthew.wahab@arm.com>

	* aarch64-opc.c (aarch64_sys_reg_supported_p): Add mistakenly
	removed statement.
	(aarch64_pstatefield_supported_p): Move feature checks for AT
	registers ..
	(aarch64_sys_ins_reg_supported_p): .. to here.

Change-Id: I48783d118eaaf0f3312e8b08a8340ef7af4e36a4


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [AArch64][PATCH 3/14] Support ARMv8.2 FP16 Scalar Three Same instructions.
@ 2015-12-17  4:43 sergiodj+buildbot
  2015-12-18  5:41 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-17  4:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6b4680fbd08221530ad3d541cd51a866eefef6fc ***

Author: Matthew Wahab <matthew.wahab@arm.com>
Branch: master
Commit: 6b4680fbd08221530ad3d541cd51a866eefef6fc

[AArch64][PATCH 3/14] Support ARMv8.2 FP16 Scalar Three Same instructions.

ARMv8.2 adds 16-bit floating point operations as an optional extension
to the floating point and Adv.SIMD support. This patch adds FP16
instructions to the group Scalar Three Register Same, making them
available when +simd+fp16 is enabled.

The instructions added are: FABD, FMULX, FCMEQ, FCMGE, FCMGT, FACGE,
FACGT, FRECPS and FRSQRTS.

The general form for these instructions is
  <OP> <Hd>, <Hs>, <Hm>

gas/testsuite/
2015-12-14  Matthew Wahab  <matthew.wahab@arm.com>

	* gas/aarch64/advsimd-fp16.d: Update expected output.
	* gas/aarch64/advsimd-fp16.s: Add tests for scalar three register same
	instructions.

opcodes/
2015-12-14  Matthew Wahab  <matthew.wahab@arm.com>

	* aarch64-asm-2.c: Regenerate.
	* aarch64-dis-2.c: Regenerate.
	* aarch64-opc-2.c: Regenerate.
	* aarch64-tbl.h (aarch64_opcode_table): Add fp16 versions of
	fmulx, fcmeq, frecps, frsqrts, fcmge, facge, fabd, fcmgt and
	facgt to the scalar three same group.

Change-Id: I155eb8d7c1e9a7c89d691d7e4aae83be51ff1238


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [AArch64][PATCH 7/14] Support FP16 Scalar Indexed Element instructions.
@ 2015-12-17  5:14 sergiodj+buildbot
  2015-12-18  9:39 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-17  5:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5f7728b7413b3bed576f8dd11d1343c20b3a2333 ***

Author: Matthew Wahab <matthew.wahab@arm.com>
Branch: master
Commit: 5f7728b7413b3bed576f8dd11d1343c20b3a2333

[AArch64][PATCH 7/14] Support FP16 Scalar Indexed Element instructions.

ARMv8.2 adds 16-bit floating point operations as an optional extension
to the floating point and Adv.SIMD support. This patch adds FP16
instructions to the group Scalar Indexed Element, making them available
when +simd+fp16 is enabled.

The instructions added are: FMLA, FMLS, FMUL and FMULX.

The general form for these instructions is
  <OP> <Hd>, <Hs>, <V>.h[<idx>]

gas/testsuite/
2015-12-14  Matthew Wahab  <matthew.wahab@arm.com>

	* gas/aarch64/advsimd-fp16.d: Update expected output.
	* gas/aarch64/advsimd-fp16.s: Add tests for scalar indexed element
	instructions.

opcodes/
2015-12-14  Matthew Wahab  <matthew.wahab@arm.com>

	* aarch64-asm-2.c: Regenerate.
	* aarch64-dis-2.c: Regenerate.
	* aarch64-opc-2.c: Regenerate.
	* aarch64-tbl.h (aarch64_opcode_table): Add fp16 versions of fmla,
	fmls, fmul and fmulx to the scalar indexed element group.

Change-Id: I6a4ee20a9ae1019b89d0fd05da55222f267c5627


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [AArch64][PATCH 12/14] Support FP16 Adv.SIMD Scalar Pairwise instructions.
@ 2015-12-17  5:45 sergiodj+buildbot
  2015-12-18 13:52 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-17  5:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b195470dd29e8a5c8810209fb2d22c30004fe6ab ***

Author: Matthew Wahab <matthew.wahab@arm.com>
Branch: master
Commit: b195470dd29e8a5c8810209fb2d22c30004fe6ab

[AArch64][PATCH 12/14] Support FP16 Adv.SIMD Scalar Pairwise instructions.

ARMv8.2 adds 16-bit floating point operations as an optional extension
to the floating point and Adv.SIMD support. This patch adds FP16
instructions to the group Adv.SIMD Scalar Pairwise, making them
available when +simd+fp16 is enabled.

The instructions added are: FMAXNMP, FADDP, FMAXP, FMINNMP and FMINP

The general form for these instructions is
   <OP> <Hd>, <V>.<T>
   where T is 4h or 8h.

gas/testsuite/
2015-12-14  Matthew Wahab  <matthew.wahab@arm.com>

	* gas/aarch64/advsimd-fp16.d: Update expected output.
	* gas/aarch64/advsimd-fp16.s: Add tests for Adv.SIMD Scalar
	Pairwise instructions.

opcodes/
2015-12-14  Matthew Wahab  <matthew.wahab@arm.com>

	* aarch64-asm-2.c: Regenerate.
	* aarch64-dis-2.c: Regenerate.
	* aarch64-opc-2.c: Regenerate.
	* aarch64-tbl.h (QL_SISD_PAIR_H): New.
	(aarch64_opcode_table): Add fp16 versions of fmaxnmp, faddp,
	fmaxp, fminnmp, fminp to the Adv.SIMD scalar pairwise group.

Change-Id: I19937ede3441b66dd0f940269ece895b17d3c345


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [AArch64][PATCH 13/14] Support FP16 Adv.SIMD Shift By Immediate instructions.
@ 2015-12-17  5:53 sergiodj+buildbot
  2015-12-18 14:48 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-17  5:53 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b5b0f34c669a91b9d873221ea3d688cf7f495ab5 ***

Author: Matthew Wahab <matthew.wahab@arm.com>
Branch: master
Commit: b5b0f34c669a91b9d873221ea3d688cf7f495ab5

[AArch64][PATCH 13/14] Support FP16 Adv.SIMD Shift By Immediate instructions.

ARMv8.2 adds 16-bit floating point operations as an optional extension
to the floating point and Adv.SIMD support. This patch extends
instructions in the group Adv.SIMD Shift By Immediate to support FP16,
making this support available when +simd+fp16 is enabled.

The new instructions legal make some uses of the 4h vector type that had
been invalid. This patch adjusts a test that checks for these uses.

The extended instructions are: SCVTF, FCVTZS, UCVTF and FCVTZU.

The general form for these instructions is
   <OP> <Vd>.<T>, <Vs>.<T>, #<imm>
   where T is 4h or 8h.

gas/testsuite/
2015-12-14  Matthew Wahab  <matthew.wahab@arm.com>

	* gas/aarch64/advsimd-fp16.d: Update expected output.
	* gas/aarch64/advsimd-fp16.s: Add tests for Adv.SIMD across lanes
	instructions.
	* gas/aarch64/illegal.d: Update expected output.
	* gas/aarch64/illegal.s: Replace tests for illegal use of 'h'
	specifier.

opcodes/
2015-12-14  Matthew Wahab  <matthew.wahab@arm.com>

	* aarch64-asm-2.c: Regenerate.
	* aarch64-dis-2.c: Regenerate.
	* aarch64-opc-2.c: Regenerate.
	* aarch64-tbl.h (QL_VSHIFT_H): New.
	(aarch64_opcode_table): Add fp16 versions of scvtf, fcvtzs, ucvtf
	and fcvtzu to the Adv.SIMD shift by immediate group.

Change-Id: I3480f63883d54db46562573185da6982f2365ee8


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [AArch64][PATCH 14/14] Support FP16 Adv.SIMD Scalar Shift By Immediate instructions.
@ 2015-12-17  6:02 sergiodj+buildbot
  2015-12-18 15:55 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-17  6:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4fd0a9fd005ea3affe8e61f6ec82817055a3bc2b ***

Author: Matthew Wahab <matthew.wahab@arm.com>
Branch: master
Commit: 4fd0a9fd005ea3affe8e61f6ec82817055a3bc2b

[AArch64][PATCH 14/14] Support FP16 Adv.SIMD Scalar Shift By Immediate instructions.

ARMv8.2 adds 16-bit floating point operations as an optional extension
to the floating point and Adv.SIMD support. This patch extends
instructions in the group Adv.SIMD Scalar Shift By Immediate to support
FP16, making this support available when +simd+fp16 is enabled.

The extended instructions are: SCVTF, FCVTZS, UCVTF and FCVTZU.

The general form for these instructions is
   <OP> <Hd>, <Hs>, #<imm>

gas/testsuite/
2015-12-14  Matthew Wahab  <matthew.wahab@arm.com>

	* gas/aarch64/advsimd-fp16.d: Update expected output.
	* gas/aarch64/advsimd-fp16: Add tests for Adv.SIMD scalar shift
	by immediate instructions.

opcodes/
2015-12-14  Matthew Wahab  <matthew.wahab@arm.com>

	* aarch64-asm-2.c: Regenerate.
	* aarch64-dis-2.c: Regenerate.
	* aarch64-opc-2.c: Regenerate.
	* aarch64-tbl.h (QL_SSHIFT_H): New.
	(aarch64_opcode_table): Add fp16 versions of scvtf, fcvtzs, ucvtf
	and fcvtzu to the Adv.SIMD scalar shift by immediate group.

Change-Id: I40506496f52dd96909e7344f243b38a1870df7ff


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Target remote mode fork and exec event support
@ 2015-12-17  6:17 sergiodj+buildbot
  2015-12-18 18:09 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-17  6:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8020350c5277e056e89b0ea5e14a8d09408f7fb3 ***

Author: Don Breazeal <donb@codesourcery.com>
Branch: master
Commit: 8020350c5277e056e89b0ea5e14a8d09408f7fb3

Target remote mode fork and exec event support

This patch implements support for fork and exec events with target remote
mode Linux targets.  For such targets with Linux kernels 2.5.46 and later,
this enables follow-fork-mode, detach-on-fork and fork and exec
catchpoints.

The changes required to implement this included:

 * Don't exit from gdbserver if there are still active inferiors.

 * Allow changing the active process in remote mode.

 * Enable fork and exec events in remote mode.

 * Print "Ending remote debugging" only when disconnecting.

 * Combine remote_kill and extended_remote_kill into a single function
   that can handle the multiple inferior case for target remote.  Also,
   the same thing for remote_mourn and extended_remote_mourn.

 * Enable process-style ptids in target remote.

 * Remove restriction on multiprocess mode in target remote.

gdb/gdbserver/ChangeLog:

	* server.c (process_serial_event): Don't exit from gdbserver
	in remote mode if there are still active inferiors.

gdb/ChangeLog:

	* inferior.c (number_of_live_inferiors): New function.
	(have_live_inferiors): Use number_of_live_inferiors in place
	of duplicate code.
	* inferior.h (number_of_live_inferiors): Declare new function.
	* remote.c (set_general_process): Remove restriction on target
	remote mode.
	(remote_query_supported): Likewise.
	(remote_detach_1): Exit in target remote mode only when there
	is just one live inferior left.
	(remote_disconnect): Unpush the target directly instead of
	calling remote_mourn.
	(remote_kill): Rewrite function to handle both target remote
	and extended-remote.  Call remote_kill_k.
	(remote_kill_k): New function.
	(extended_remote_kill): Delete function.
	(remote_mourn, extended_remote_mourn): Combine functions into
	one, remote_mourn, and enable extended functionality for target
	remote.
	(remote_pid_to_str): Enable "process" style ptid string for
	target remote.
	(remote_supports_multi_process): Remove restriction on target
	remote mode.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Remove gdb.base/coremaker2.c
@ 2015-12-17  6:35 sergiodj+buildbot
  2015-12-17 15:31 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-17  6:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f1637ebed142eabd96cbc009edda8ec903c71fd6 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: f1637ebed142eabd96cbc009edda8ec903c71fd6

Remove gdb.base/coremaker2.c

I happen to find that coremaker2.c isn't used in the testsuite (if I
don't miss anything).  I don't believe it until I see this ChangeLog
entry,

1999-11-18  Fred Fish  <fnf@cygnus.com>

        * gdb.base/coremaker2.c: Add sample program for generating
        cores that is more self contained than coremaker.c.  Eventually
        I'll add more code to this and tie it into the testsuite.

looks Fred didn't "tie it into testsuite" later.

gdb/testsuite:

2015-12-11  Yao Qi  <yao.qi@linaro.org>

	* gdb.base/coremaker2.c: Remove.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Skip tests that send ctrl-c to GDB if nointerrupts target property is set.
@ 2015-12-17  7:08 sergiodj+buildbot
  2015-12-18 20:17 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-17  7:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 87a3a92c46c770e6aa2ca1209f46af16eae2c4e9 ***

Author: Sandra Loosemore <sandra@codesourcery.com>
Branch: master
Commit: 87a3a92c46c770e6aa2ca1209f46af16eae2c4e9

Skip tests that send ctrl-c to GDB if nointerrupts target property is set.

2015-12-14  Sandra Loosemore  <sandra@codesourcery.com>

	gdb/testsuite/
	* gdb.base/completion.exp: Skip tests that interrupt GDB with
	ctrl-C if nointerrupts target property is set.
	* gdb.base/double-prompt-target-event-error.exp: Likewise.
	* gdb.base/paginate-after-ctrl-c-running.exp: Likewise.
	* gdb.base/paginate-bg-execution.exp: Likewise.
	* gdb.base/paginate-execution-startup.exp: Likewise.
	* gdb.base/random-signal.exp: Likewise.
	* gdb.base/range-stepping.exp: Likewise.
	* gdb.cp/annota2.exp: Likewise.
	* gdb.cp/annota3.exp: Likewise.
	* gdb.gdb/selftest.exp: Likewise.
	* gdb.threads/continue-pending-status.exp: Likewise.
	* gdb.threads/leader-exit.exp: Likewise.
	* gdb.threads/manythreads.exp: Likewise.
	* gdb.threads/pthreads.exp: Likewise.
	* gdb.threads/schedlock.exp: Likewise.
	* gdb.threads/sigthread.exp: Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Add support for RX V2 Instruction Set
@ 2015-12-17  7:40 sergiodj+buildbot
  2015-12-19  0:49 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-17  7:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a117b0a51cd3c768453c244a3754c1b9a77e74fc ***

Author: Yoshinori Sato <ysato@users.sourceforge.jp>
Branch: master
Commit: a117b0a51cd3c768453c244a3754c1b9a77e74fc

Add support for RX V2 Instruction Set

binutils
	* readelf.c(get_machine_flags): Add v2 flag.

gas
	* config/rx-defs.h(rx_cpu_type): Add RXV2 type.
	* config/tc-rx.c(cpu_type_list): New type lookup table.
	(md_parse_option): Use lookup table for choose cpu.
	(md_show_usage): Add rxv2 for mcpu option.
	* doc/c-rx.texi: Likewise.
	* config/rx-parse.y: Add v2 instructions and ACC register.
	(rx_check_v2): check v2 type.

include/elf
	* rx.h(E_FLAG_RX_V2): New RXv2 type.

include/opcode
	* rx.h: Add new instructions.

opcoes
	* rx-deocde.opc(rx_decode_opcode): Add new instructions pattern.
	* rx-dis.c(register_name): Add new register.

gas/testsuite
	* gas/rx/emaca.d: New.
	* gas/rx/emaca.sm: New.
	* gas/rx/emsba.d: New.
	* gas/rx/emsba.sm: New.
	* gas/rx/emula.d: New.
	* gas/rx/emula.sm: New.
	* gas/rx/fadd.d: Add new pattern.
	* gas/rx/fadd.sm: Add new pattern.
	* gas/rx/fmul.d: Add new pattern.
	* gas/rx/fmul.sm: Add new pattern.
	* gas/rx/fsqrt.d: New.
	* gas/rx/fsqrt.sm: New.
	* gas/rx/fsub.d: Add new pattern.
 	* gas/rx/fsub.sm: Add new pattern.
	* gas/rx/ftou.d: New.
	* gas/rx/ftou.sm: New.
	* gas/rx/maclh.d: New.
	* gas/rx/maclh.sm: New.
	* gas/rx/maclo.d: Add new pattern.
	* gas/rx/maclo.sm: Add new pattern.
	* gas/rx/macros.inc: Add new register.
	* gas/rx/movco.d: New.
	* gas/rx/movco.sm: New.
	* gas/rx/movli.d: New.
	* gas/rx/movli.sm: New.
	* gas/rx/msbhi.d: New.
	* gas/rx/msbhi.sm: New.
	* gas/rx/msblh.d: New.
	* gas/rx/msblh.sm: New.
	* gas/rx/msblo.d: New.
	* gas/rx/msblo.sm: New.
	* gas/rx/mullh.d: New.
	* gas/rx/mullh.sm: New.
	* gas/rx/mvfacgu.d: New.
	* gas/rx/mvfacgu.sm: New.
	* gas/rx/mvfachi.d: Add new pattern.
	* gas/rx/mvfachi.sm: Add new pattern.
	* gas/rx/mvfaclo.d: Add new pattern.
	* gas/rx/mvfaclo.sm: Add new pattern.
	* gas/rx/mvfacmi.d: Add new pattern.
	* gas/rx/mvfacmi.sm: Add new pattern.
	* gas/rx/mvfc.d: Add new pattern.
	* gas/rx/mvtacgu.d: New.
	* gas/rx/mvtacgu.sm: New.
	* gas/rx/mvtc.d: Add new pattern.
	* gas/rx/popc.d: Add new pattern.
	* gas/rx/pushc.d: Add new pattern.
	* gas/rx/racl.d: New.
	* gas/rx/racl.sm: New.
	* gas/rx/racw.d: Add new pattern.
	* gas/rx/racw.sm: Add new pattern.
	* gas/rx/rdacl.d: New.
	* gas/rx/rdacl.sm: New.
	* gas/rx/rdacw.d: New.
	* gas/rx/rdacw.sm: New.
	* gas/rx/rx.exp: Add option.
	* gas/rx/stnz.d: Add new pattern.
	* gas/rx/stnz.sm: Add new pattern.
	* gas/rx/stz.d: Add new pattern.
	* gas/rx/stz.sm: Add new pattern.
	* gas/rx/utof.d: New.
	* gas/rx/utof.sm: New.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Add support for the MRS instruction to the AArch64 simulator.
@ 2015-12-17  7:48 sergiodj+buildbot
  2015-12-19  2:31 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-17  7:48 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT caa8d70005e4e12392683c799b30790fc4c62166 ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: caa8d70005e4e12392683c799b30790fc4c62166

Add support for the MRS instruction to the AArch64 simulator.

	* aarch64/simulator.c (system_get): New function.  Provides read
	access to the dczid system register.
	(do_mrs): New function - implements the MRS instruction.
	(dexSystem): Call do_mrs for the MRS instruction.  Halt on
	unimplemented system instructions.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] gdb: Make test names unique in list.exp.
@ 2015-12-17  8:42 sergiodj+buildbot
  2015-12-17 19:45 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-17  8:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5c000dff26b7c5159ca1a6d562e7ab50656f4b73 ***

Author: Andrew Burgess <andrew.burgess@embecosm.com>
Branch: master
Commit: 5c000dff26b7c5159ca1a6d562e7ab50656f4b73

gdb: Make test names unique in list.exp.

gdb/testsuite/ChangeLog:

	* gdb.base/list.exp (test_list): Make test names unique.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix invalid left shift of negative value
@ 2015-12-17  8:58 sergiodj+buildbot
  2015-12-19  4:58 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-17  8:58 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1d19cae752a7b032b8253feb4fa3b9f1dc162823 ***

Author: Dominik Vogt <vogt@linux.vnet.ibm.com>
Branch: master
Commit: 1d19cae752a7b032b8253feb4fa3b9f1dc162823

Fix invalid left shift of negative value

Fix occurrences of left-shifting negative constants in C code.

sim/arm/ChangeLog:

	* thumbemu.c (handle_T2_insn): Fix left shift of negative value.
	* armemu.c (handle_v6_insn): Likewise.

sim/avr/ChangeLog:

	* interp.c (sign_ext): Fix left shift of negative value.

sim/mips/ChangeLog:

	* micromips.igen (process_isa_mode): Fix left shift of negative
	value.

sim/msp430/ChangeLog:

	* msp430-sim.c (get_op, put_op): Fix left shift of negative value.

sim/v850/ChangeLog:

	* simops.c (v850_bins): Fix left shift of negative value.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] bfd: don't produce corrupt COFF symbol table due to long ELF file name symbols
@ 2015-12-17  9:06 sergiodj+buildbot
  2015-12-19  5:43 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-17  9:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 270f824531ceef276616a5d2f3027fa9f537c10b ***

Author: Jan Beulich <jbeulich@novell.com>
Branch: master
Commit: 270f824531ceef276616a5d2f3027fa9f537c10b

bfd: don't produce corrupt COFF symbol table due to long ELF file name symbols

The re-writing logic in _bfd_coff_final_link() overwrote the ".file"
part of the symbol table entry, due to not coping with the auxiliary
entry generated in all cases.

Note that while I would have wanted to add a test case,
(a) I didn't spot any one testing the base functionality here, and
(b) I wasn't able to figure out proper conditionals to use in e.g.
    ld-elf/elf.exp to check for the necessary PE/PE+ support (which
    varies by target).


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Tweak gdb.trace/ftrace.exp for aarch64
@ 2015-12-17  9:14 sergiodj+buildbot
  2015-12-19  6:58 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-17  9:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a22279dd83da7a0dd2b496c92dc2522427f74e37 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: a22279dd83da7a0dd2b496c92dc2522427f74e37

Tweak gdb.trace/ftrace.exp for aarch64

Some tests are skipped on aarch64 unexpectedly because arg0exp isn't
set.  This patch is to set arg0exp to "$x0" for aarch64.

gdb/testsuite:

2015-12-15  Yao Qi  <yao.qi@linaro.org>

	* gdb.trace/ftrace.exp: Set arg0exp to "$x0" if target
	is aarch64*-*-*.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] gdb: Extend help text for 'list' command.
@ 2015-12-17  9:52 sergiodj+buildbot
  2015-12-17 22:58 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-17  9:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4fdd372d502d241eb42032844836ae031830237a ***

Author: Andrew Burgess <andrew.burgess@embecosm.com>
Branch: master
Commit: 4fdd372d502d241eb42032844836ae031830237a

gdb: Extend help text for 'list' command.

Reference the 'listsize' setting in the help text for the 'list' command
to help users find this setting.

gdb/ChangeLog:

	* cli/cli-cmds.c (_initialize_cli_cmds): Extend help text for
	'list' command.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [ARM] Add support for thumb1 pcrop relocations.
@ 2015-12-17 10:05 sergiodj+buildbot
  2015-12-19  8:52 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-17 10:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 72d98d16ed09584660d0cbb759d90f8dfeef2343 ***

Author: Mickael Guene <mickael.guene@st.com>
Branch: master
Commit: 72d98d16ed09584660d0cbb759d90f8dfeef2343

[ARM] Add support for thumb1 pcrop relocations.

To support thumb1 execute-only code we need to support four new
relocations (R_ARM_THM_ALU_ABS_G0_NC, R_ARM_THM_ALU_ABS_G1_NC,
R_ARM_THM_ALU_ABS_G2_NC and  R_ARM_THM_ALU_ABS_G3_NC).
These relocations allow the static linker to finalize construction
of symbol address.
Typical sequence of code to get address of the symbol foo is then
the following :
	movs	r3, #:upper8_15:#foo
	lsls	r3, #8
	adds	r3, #:upper0_7:#foo
	lsls	r3, #8
	adds	r3, #:lower8_15:#foo
	lsls	r3, #8
	adds	r3, #:lower0_7:#foo
This will give following sequence of text and relocations after
assembly :
   4:	2300      	movs	r3, #0
			4: R_ARM_THM_ALU_ABS_G3_NC	foo
   6:	021b      	lsls	r3, r3, #8
   8:	3300      	adds	r3, #0
			8: R_ARM_THM_ALU_ABS_G2_NC	foo
   a:	021b      	lsls	r3, r3, #8
   c:	3300      	adds	r3, #0
			c: R_ARM_THM_ALU_ABS_G1_NC	foo
   e:	021b      	lsls	r3, r3, #8
  10:	3300      	adds	r3, #0
			10: R_ARM_THM_ALU_ABS_G0_NC	foo


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix -Wno-unknown-warning support detection
@ 2015-12-17 10:22 sergiodj+buildbot
  2015-12-19 11:02 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-17 10:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7544db951abbb5dca5373dcc7ae83ed60c0782ad ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 7544db951abbb5dca5373dcc7ae83ed60c0782ad

Fix -Wno-unknown-warning support detection

Ref: https://sourceware.org/ml/gdb/2015-12/msg00024.html

We have code in configure.ac that tries to detect whether the compiler
supports each warning and suppress it if not, but that doesn't work
with "-Wno-" options, because gcc doesn't error out for
-Wno-unknown-warning unless other diagnostics are being produced.

See https://gcc.gnu.org/onlinedocs/gcc/Warning-Options.html.

Handle this by checking whether -Wfoo works when we actually want
-Wno-foo.

gdb/ChangeLog:
2015-12-16  Pedro Alves  <palves@redhat.com>

	* configure.ac (compiler warning flags): When testing a
	-Wno-foo option, check whether -Wfoo works instead.
	* configure: Regenerate.

gdb/gdbserver/ChangeLog:
2015-12-16  Pedro Alves  <palves@redhat.com>

	* configure.ac (compiler warning flags): When testing a
	-Wno-foo option, check whether -Wfoo works instead.
	* configure: Regenerate.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [AArch64][PATCH 1/14] Support ARMv8.2 FP16 Adv.SIMD instructions.
@ 2015-12-17 11:31 sergiodj+buildbot
  2015-12-18  3:26 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-17 11:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 40d16a76c781bc9951d22ee359e07c6c240b81ba ***

Author: Matthew Wahab <matthew.wahab@arm.com>
Branch: master
Commit: 40d16a76c781bc9951d22ee359e07c6c240b81ba

[AArch64][PATCH 1/14] Support ARMv8.2 FP16 Adv.SIMD instructions.

ARMv8.2 adds 16-bit floating point operations as an optional extension
to floating point and Adv.SIMD support. This patch set adds the 16-bit
Adv.SIMD vector and scalar instructions to binutils, making them
available when both +simd and +fp16 architecture extensions are enabled.
The series also adds support for a new vector type, 2H, used by the FP16
scalar pairwise instructions.

The patches in this series:
- Add a FP16 Adv.SIMD feature macro for use by the encoding/decoding
  routines.
- Add FP16 instructions in the group Vector Three Register Same.
- Add FP16 instructions in the group Scalar Three Register Same.
- Add FP16 instructions in the group Vector Two Register Misc.
- Add FP16 instructions in the group Scalar Two Register Misc.
- Add FP16 instructions in the group Vector Indexed Element.
- Add FP16 instructions in the group Scalar Indexed Element.
- Add FP16 instructions in the group Adv.SIMD Across Lanes.
- Add FP16 instructions in the group Adv.SIMD Modified Immediate.
- Rework some code for handling vector types to weaken its assumptions
  about available vector-types.
- Add support for the 2H vector type.
- Add FP16 instructions in the group Adv.SIMD Scalar Pairwise.
- Add FP16 instructions in the group Adv.SIMD Shift By Immediate.
- Add a FP16 instructions in the group Adv.SIMD Scalar Shift By
  Immediate.

This patch adds the feature macro SIMD_F16 to the AArch64
encoding/decoding routines. It is used to decide when the new
instructions are available to the assembler and is true when both +simd
and +fp16 are selected.

opcodes/
2015-12-14  Matthew Wahab  <matthew.wahab@arm.com>

	* aarch64-tbl.h (aarch64_feature_simd_f16): New.
	(SIMD_F16): New.

Change-Id: Iee5a37928418f15e51dfaa927b24cafef7295e8f


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [Patch ARM] Fix build attributes for armv8-a in case of assembler files that contain no directives.
@ 2015-12-17 11:45 sergiodj+buildbot
  2015-12-19 12:08 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-17 11:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 10c9892b66d56de0aab3fbaec3d59a0304dc0a21 ***

Author: Ramana Radhakrishnan <ramana.radhakrishnan@arm.com>
Branch: master
Commit: 10c9892b66d56de0aab3fbaec3d59a0304dc0a21

[Patch ARM] Fix build attributes for armv8-a in case of assembler files that contain no directives.

There is currently a problem in the way in which we produce
build attributes for simple assembler files that have armv8-a
instructions.

In these case we need to generate TAG_ISA_THUMB_Use to be Thumb-2
and set the architecture profile to be 'A' rather than not
setting architecture profile to be 'A' and setting TAG_ISA_THUMB_Use
to be Thumb-1.

This is a pre-requisite for any v8-m patches that have been posted.
arm-none-eabi gas testsuite run. no regressions.

2015-12-17  Ramana Radhakrishnan  <ramana.radhakrishnan@arm.com>

	* gas/config/tc-arm.c (aeabi_set_public_attributes): Adjust
	TAG_ARCH_profile for armv8-a.
	* gas/testsuite/gas/arm/armv8a-automatic-hlt.d: New test.
	* gas/testsuite/gas/arm/armv8a-automatic-hlt.s: New test.
	* gas/testsuite/gas/arm/armv8a-automatic-lda.d: New test.
	* gas/testsuite/gas/arm/armv8a-automatic-lda.s: New test.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix one heap buffer overflow in aarch64_push_dummy_call
@ 2015-12-17 13:20 sergiodj+buildbot
  2015-12-19 13:04 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-17 13:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c3c874459bf57a70ccbf71a39a3a7dc3c472a201 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: c3c874459bf57a70ccbf71a39a3a7dc3c472a201

Fix one heap buffer overflow in aarch64_push_dummy_call

Hi,
AddressSanitizer reports an error like this,

(gdb) PASS: gdb.base/call-ar-st.exp: continue to tbreak9
print print_long_arg_list(a, b, c, d, e, f, *struct1, *struct2, *struct3, *struct4, *flags, *flags_combo, *three_char, *five_char, *int_char_combo, *d1, *d2, *d3, *f1, *f2, *f3)
=================================================================
==6236==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x60200008eb50 at pc 0x89e432 bp 0x7fffa3df9080 sp 0x7fffa3df9078
READ of size 5 at 0x60200008eb50 thread T0
    #0 0x89e431 in memory_xfer_partial gdb/target.c:1264
    #1 0x89e6c7 in target_xfer_partial gdb/target.c:1320
    #2 0x89f267 in target_write_partial gdb/target.c:1595^M
    #3 0x8a014b in target_write_with_progress gdb/target.c:1889^M
    #4 0x8a0262 in target_write gdb/target.c:1914^M
    #5 0x89ee59 in target_write_memory gdb/target.c:1492^M
    #6 0x9a1c74 in write_memory gdb/corefile.c:393^M
    #7 0x467ea5 in aarch64_push_dummy_call gdb/aarch64-tdep.c:1388

The problem is that an instance of stack_item_t is created to adjust
stack for alignment, the item.len is correct, but item.data is buf,
which is wrong, because item.len can be greater than the length of
buf.  This patch sets item.data to NULL, and only update sp (no
inferior memory writes on stack for this item).

gdb:

2015-12-17  Yao Qi  <yao.qi@linaro.org>

	* aarch64-tdep.c (struct stack_item_t): Update comments.
	(pass_on_stack): Set item.data to NULL.
	(aarch64_push_dummy_call): Call write_memory if si->data
	isn't NULL.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [AArch64][PATCH 11/14] Add support for the 2H vector type.
@ 2015-12-17 15:02 sergiodj+buildbot
  2015-12-18 13:08 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-17 15:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3067d3b96cfb88e86acf94d2aa1575cff0e0110f ***

Author: Matthew Wahab <matthew.wahab@arm.com>
Branch: master
Commit: 3067d3b96cfb88e86acf94d2aa1575cff0e0110f

[AArch64][PATCH 11/14] Add support for the 2H vector type.

ARMv8.2 adds 16-bit floating point operations as an optional extension
to the floating point and Adv.SIMD support. The FP16 additions to the
scalar pairwise group introduce a new vector type, 2H. This patch adds
support for this vector type to binutils.

The patch adds a new operand qualifier to the enum
aarch64.h:aarch64_opnd_qualifier. This interferes with the calculation
used by aarch64-dis.c:get_vreg_qualifier_from_value, called when
decoding an instruction. Since the new vector type is only used in FP16
scalar pairwise instructions which do not require the function, this
patch adjusts the function to ignore the new qualifier.

gas/
2015-12-14  Matthew Wahab  <matthew.wahab@arm.com>

	* config/tc-aarch64.c (parse_neon_type_for_operand): Adjust to
	take into account new vector type 2H.
	(vectype_to_qualifier): Likewise.

include/opcode/
2015-12-14  Matthew Wahab  <matthew.wahab@arm.com>

	* aarch64.h (enum aarch64_opnd_qualifier): Add
	AARCH64_OPND_QLF_V_2H.

opcodes/
2015-12-14  Matthew Wahab  <matthew.wahab@arm.coM>

	* aarch64-dis.c (get_vreg_qualifier_from_value): Update comment
	and adjust calculation to ignore qualifier for type 2H.
	* aarch64-opc.c (aarch64_opnd_qualifier): Add "2H".

Change-Id: Idf9a3694732962c80fde04f08c7304de9164f126


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Remove support for LinuxThreads and vendor 2.4 kernels w/ backported NPTL
@ 2015-12-17 15:14 sergiodj+buildbot
  2015-12-19 14:31 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-17 15:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4a6ed09b0f70c79b11bc1e0973a7333d9316a287 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 4a6ed09b0f70c79b11bc1e0973a7333d9316a287

Remove support for LinuxThreads and vendor 2.4 kernels w/ backported NPTL

Since we now rely on PTRACE_EVENT_CLONE being available (added in
Linux 2.5.46), we're relying on NPTL.

This commit removes the support for older LinuxThreads, as well as the
workarounds for vendor 2.4 kernels with NPTL backported.

 - Rely on tkill being available.

 - Assume gdb doesn't get cancel signals.

 - Remove code that checks the LinuxThreads restart and cancel signals
   in the inferior.

 - Assume that __WALL is available.

 - Assume that non-leader threads report WIFEXITED.

 - Thus, no longer need to send signal 0 to check whether threads are
   still alive.

 - Update comments throughout.

Tested on x86_64 Fedora 20, native and gdbserver.

gdb/ChangeLog:

	* configure.ac: Remove tkill checks.
	* configure, config.in: Regenerate.
	* linux-nat.c: Remove HAVE_TKILL_SYSCALL check.  Update top level
	comments.
	(linux_nat_post_attach_wait): Remove 'cloned' parameter.  Use
	__WALL.
	(attach_proc_task_lwp_callback): Don't set the cloned flag.
	(linux_nat_attach): Adjust.
	(kill_lwp): Remove HAVE_TKILL_SYSCALL check.  No longer fall back
	to 'kill'.
	(linux_handle_extended_wait): Use __WALL.  Don't set the cloned
	flag.
	(wait_lwp): Use __WALL.  Update comments.
	(running_callback, stop_and_resume_callback): Delete.
	(linux_nat_filter_event): Don't stop and resume all lwps. Don't
	check if the event LWP has previously exited.
	(check_zombie_leaders): Update comments.
	(linux_nat_wait_1): Use __WALL.
	(kill_wait_callback): Don't handle clone processes separately.
	Use __WALL instead.
	(linux_thread_alive): Delete.
	(linux_nat_thread_alive): Return true as long as the LWP is in the
	LWP list.
	(linux_nat_update_thread_list): Assume the kernel supports
	PTRACE_EVENT_CLONE.
	(get_signo): Delete.
	(lin_thread_get_thread_signals): Remove LinuxThreads references.
	No longer check __pthread_sig_restart / __pthread_sig_cancel in
	the inferior.
	* linux-nat.h (struct lwp_info) <cloned>: Delete field.
	* linux-thread-db.c: Update comments.
	(_initialize_thread_db): Remove LinuxThreads references.
	* nat/linux-waitpid.c (my_waitpid): No longer emulate __WALL.
	Pass down flags unmodified.
	* linux-waitpid.h (my_waitpid): Update documentation.

gdb/gdbserver/ChangeLog:

	* linux-low.c (linux_kill_one_lwp): Remove references to
	LinuxThreads.
	(kill_lwp): Remove HAVE_TKILL_SYSCALL check.  No longer fall back
	to 'kill'.
	(linux_init_signals): Delete.
	(initialize_low): Adjust.
	* thread-db.c (thread_db_init): Remove LinuxThreads reference.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix PR threads/19354: "info threads" error with multiple inferiors
@ 2015-12-17 15:38 sergiodj+buildbot
  2015-12-19 15:27 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-17 15:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a6904d5a6aa63e4bef7207407250d8b76b56f8a9 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: a6904d5a6aa63e4bef7207407250d8b76b56f8a9

Fix PR threads/19354: "info threads" error with multiple inferiors

Note: this applies on top of:
 [PATCH] Remove support for LinuxThreads and vendor 2.4 kernels w/ backported NPTL
 https://sourceware.org/ml/gdb-patches/2015-12/msg00214.html

We try to avoid using libthread_db.so to list threads in the inferior
when debugging live processes, but the code that decides whether to
use it decides incorrectly if you have more than one inferior, and the
current inferior doesn't have execution yet.  The result is visible
as:

 (gdb) add-inferior
 Added inferior 2
 (gdb) inferior 2
 [Switching to inferior 2 [<null>] (<noexec>)]
 (gdb) info inferiors
   Num  Description       Executable
   1    process 15397     /home/pedro/gdb/tests/threads
 * 2    <null>
 (gdb) info threads
 Cannot find new threads: generic error
 (gdb)

Fix this by checking whether each inferior has execution rather than
just the current inferior.

By moving the core updating to linux-nat.c's update_thread_list
implementation, this also ends up fixing the
lwp-last-seen-running-on-core updating in the case we're debugging a
program that uses raw clone rather than pthreads, as linux-thread-db.c
isn't pushed in the target stack in that scenario.

Tested on x86_64 Fedora 20.

gdb/ChangeLog:
2015-12-17  Pedro Alves  <palves@redhat.com>

	PR threads/19354
	* linux-nat.c (linux_nat_update_thread_list): Update process cores
	each lwp was last seen running on here.
	* linux-thread-db.c (update_thread_core): Delete.
	(thread_db_update_thread_list_td_ta_thr_iter): Rename to ...
	(thread_db_update_thread_list): ... this.  Skip inferiors with
	execution.  Also call the target beneath.
	(thread_db_update_thread_list): Delete.

gdb/testsuite/ChangeLog:
2015-12-17  Pedro Alves  <palves@redhat.com>

	PR threads/19354
	* gdb.multi/info-threads.exp: New file.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Target remote mode fork and exec test updates
@ 2015-12-17 16:37 sergiodj+buildbot
  2015-12-18 17:01 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-17 16:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a8f077dc25b1732fb272a7ff10f72b5ca6f67b70 ***

Author: Don Breazeal <donb@codesourcery.com>
Branch: master
Commit: a8f077dc25b1732fb272a7ff10f72b5ca6f67b70

Target remote mode fork and exec test updates

This patch updates tests for fork and exec events in target remote mode.
In the majority of cases this was a simple matter of removing some code
that disabled the test for target remote.  In a few cases the test needed
to be disabled; in those cases the gdb_protocol was checked instead of
using the [is_remote target] etc.

In a couple of cases we needed to use clean_restart, since target remote
doesn't support the run command, and in one case we had to modify an expect
expression to allow for a "multiprocess-style" ptid.

Tested with the patch that implemented target remote mode fork and exec
event support.

gdb/testsuite/ChangeLog:

	* gdb.base/execl-update-breakpoints.exp (main): Enable for target
	remote.
	* gdb.base/foll-exec-mode.exp (main): Disable for target remote.
	* gdb.base/foll-exec.exp (main): Enable for target remote.
	* gdb.base/foll-fork.exp (main): Likewise.
	* gdb.base/foll-vfork.exp (main): Likewise.
	* gdb.base/multi-forks.exp (main): Likewise, and use clean_restart.
	(proc continue_to_exit_bp_loc): Use clean_restart.
	* gdb.base/pie-execl.exp (main): Disable for target remote.
	* gdb.base/watch-vfork.exp (main): Enable for target remote.
	* gdb.mi/mi-nsthrexec.exp (main): Likewise.
	* gdb.threads/execl.exp (main): Likewise.
	* gdb.threads/fork-child-threads.exp (main): Likewise.
	* gdb.threads/fork-plus-threads.exp (main): Disable for target
	remote.
	* gdb.threads/fork-thread-pending.exp (main): Enable for target
	remote.
	* gdb.threads/linux-dp.exp (check_philosopher_stack): Allow
	pid.tid style ptids, instead of just tid.
	* gdb.threads/thread-execl.exp (main): Enable for target remote.
	* gdb.threads/watchpoint-fork.exp (main): Likewise.
	* gdb.trace/report.exp (use_collected_data): Allow pid.tid style
	ptids, instead of just tid.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Skip gdb.base/gdbinit-history.exp on remote hosts.
@ 2015-12-17 18:36 sergiodj+buildbot
  2015-12-18 22:44 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-17 18:36 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5d978e177217d8e9da8648498f0592b5cd885e69 ***

Author: Sandra Loosemore <sandra@codesourcery.com>
Branch: master
Commit: 5d978e177217d8e9da8648498f0592b5cd885e69

Skip gdb.base/gdbinit-history.exp on remote hosts.

2015-12-14  Sandra Loosemore  <sandra@codesourcery.com>

	gdb/testsuite/
	* gdb.base/gdbinit-history.exp: Skip for remote-host testing.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [ARM] Enable CRC by default for ARMv8.1 and later.
@ 2015-12-17 21:47 sergiodj+buildbot
  2015-12-19  7:53 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-17 21:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 29b1539538f5f285e017adbc64b8d72b45c104a8 ***

Author: Matthew Wahab <matthew.wahab@arm.com>
Branch: master
Commit: 29b1539538f5f285e017adbc64b8d72b45c104a8

[ARM] Enable CRC by default for ARMv8.1 and later.

ARMv8.1 includes CRC as a required extension but the +crc feature isn't
enabled by -march=armv8.1-a as it should be. This patch fixes that.

opcode/include
2015-12-15  Matthew Wahab  <matthew.wahab@arm.com>

	* arm.h (ARM_ARCH_V8_1A): Add the CRC_EXT_ARMV8 co-processor
	feature macro.
	(ARM_ARCH_V8_2A): Likewise.

Change-Id: Id1fe0e6fa51dede19d61e1fd08e68628ea1b1e9e


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix formatting of coff-i386.c
@ 2015-12-18  8:59 sergiodj+buildbot
  2015-12-19 16:38 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-18  8:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ec70be9f6162aca5fb14876e232e68c64b1faa7f ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: ec70be9f6162aca5fb14876e232e68c64b1faa7f

Fix formatting of coff-i386.c

	* coff-i386.c (coff_i386_reloc): Fix formatting.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix formatting in coff-x86_64.c
@ 2015-12-18 16:26 sergiodj+buildbot
  2015-12-19 17:42 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-18 16:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c9f203207d418f72217f4bc0997acd809a0479ce ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: c9f203207d418f72217f4bc0997acd809a0479ce

Fix formatting in coff-x86_64.c

	* coff-x86_64.c (coff_amd64_reloc): Fix formatting.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Share some ARM target dependent code from GDB with GDBServer
@ 2015-12-18 17:01 sergiodj+buildbot
  2015-12-19 19:48 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-18 17:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cba7e83fda349cbf423fab274f5b8677d8148947 ***

Author: Antoine Tremblay <antoine.tremblay@ericsson.com>
Branch: master
Commit: cba7e83fda349cbf423fab274f5b8677d8148947

Share some ARM target dependent code from GDB with GDBServer

This patch is in preparation for software single stepping support on ARM
it shares some functions and definitions that will be needed.

No regressions, tested on ubuntu 14.04 ARMv7 and x86.
With gdbserver-{native,extended} / { -marm -mthumb }

Not tested: wince/bsd build.

gdb/ChangeLog:

	* arch/arm.c (bitcount): Move from arm-tdep.c.
	(condition_true): Likewise.
	* arch/arm.h (Instruction Definitions): Move form arm-tdep.h.
	(condition_true): Move defenition from arm-tdep.h.
	(bitcount): Likewise.
	* arm-tdep.c (condition_true): Move to arch/arm.c.
	(bitcount): Likewise.
	* arm-tdep.h (Instruction Definitions): Move to arch/arm.h.
	* arm-wince-tdep.c: Include arch/arm.h.
	* armnbsd-tdep.c: Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Refactor arm_software_single_step to use regcache
@ 2015-12-18 17:27 sergiodj+buildbot
  2015-12-19 20:39 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-18 17:27 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d0e59a68884ad3a346ff0f6f763636c7245e4cb3 ***

Author: Antoine Tremblay <antoine.tremblay@ericsson.com>
Branch: master
Commit: d0e59a68884ad3a346ff0f6f763636c7245e4cb3

Refactor arm_software_single_step to use regcache

This patch is in preparation for software single step support on ARM in
GDBServer. It refactors arm_*_software_single_step and sub-functions to
use regcache instead of frame to access registers so that the code can be
shared more easily between GDB and GDBServer.

Note also that since the intention is at some point to get rid of frame
completely in that function, memory reads have also been replaced by
read_memory_unsigned_integer rather than get_frame_memory_unsigned.

No regressions, tested on ubuntu 14.04 ARMv7 and x86.
With gdbserver-{native,extended} / { -marm -mthumb }

gdb/ChangeLog:

	* arm-linux-tdep.c (arm_linux_sigreturn_next_pc_offset): New function.
	(arm_linux_sigreturn_next_pc): Likewise.
	(arm_linux_syscall_next_pc): Use regcache instead of frame.
	(arm_linux_software_single_step): Likewise.
	* arm-tdep.c (arm_is_thumb): New function.
	(shifted_reg_va): Use regcache instead of frame.
	(thumb_get_next_pc_raw): Likewise.
	(arm_get_next_pc_raw): Likewise.
	(arm_get_next_pc): Likewise.
	(thumb_deal_with_atomic_sequence_raw): Likewise.
	(arm_deal_with_atomic_sequence_raw): Likewise.
	(arm_deal_with_atomic_sequence): Likewise.
	(arm_software_single_step): Likewise.
	* arm-tdep.h (struct gdbarch_tdep): Use regcache for syscall_next_pc.
	(arm_get_next_pc): Use regcache.
	(arm_deal_with_atomic_sequence): Likewise.
	(arm_is_thumb): New declaration.
	* regcache.c (regcache_raw_get_unsigned): New function.
	* regcache.h (regcache_raw_get_unsigned): New function declaration.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Share regcache function regcache_raw_read_unsigned
@ 2015-12-18 17:35 sergiodj+buildbot
  2015-12-19 21:39 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-18 17:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 68ce205943e0821eacd8028881ced3607cc83c0d ***

Author: Antoine Tremblay <antoine.tremblay@ericsson.com>
Branch: master
Commit: 68ce205943e0821eacd8028881ced3607cc83c0d

Share regcache function regcache_raw_read_unsigned

This patch is in preparation for software single step support on ARM in
GDBServer. It adds a new shared function regcache_raw_read_unsigned and
regcache_raw_get_unsigned so that GDB and GDBServer can use the same call
to fetch a raw register into an integer.

No regressions, tested on ubuntu 14.04 ARMv7 and x86.
With gdbserver-{native,extended} / { -marm -mthumb }

gdb/ChangeLog:

	* Makefile.in (SFILES): Append common/common-regcache.c.
	(COMMON_OBS): Append common/common-regcache.o.
	(common-regcache.o): New rule.
	* common/common-regcache.h (register_status) New enum.
	(regcache_raw_read_unsigned): New declaration.
	* common/common-regcache.c: New file.
	* regcache.h (enum register_status): Move to common-regcache.h.
	(regcache_raw_read_unsigned): Likewise.
	(regcache_raw_get_unsigned): Likewise.

gdb/gdbserver/ChangeLog:

	* Makefile.in (SFILES): Append common/common-regcache.c.
	(OBS): Append common-regcache.o.
	(common-regcache.o): New rule.
	* regcache.c (init_register_cache): Initialize cache to
	REG_UNAVAILABLE.
	(regcache_raw_read_unsigned): New function.
	* regcache.h (REG_UNAVAILABLE, REG_VALID): Replaced by shared
	register_status enum.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Support software single step on ARM in GDBServer
@ 2015-12-18 17:43 sergiodj+buildbot
  2015-12-19 22:43 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-18 17:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d9311bfaf572cf14af577a66e79c51c491553552 ***

Author: Antoine Tremblay <antoine.tremblay@ericsson.com>
Branch: master
Commit: d9311bfaf572cf14af577a66e79c51c491553552

Support software single step on ARM in GDBServer

This patch teaches GDBServer how to software single step on ARM
linux by sharing code with GDB.

The arm_get_next_pcs function in GDB is now shared with GDBServer.  So
that GDBServer can use the function to return the possible addresses of
the next PC.

A proper shared context was also needed so that we could share the code,
this context is described in the arm_get_next_pcs structure.

Testing :

No regressions, tested on ubuntu 14.04 ARMv7 and x86.
With gdbserver-{native,extended} / { -marm -mthumb }

gdb/ChangeLog:

	* Makefile.in (ALL_TARGET_OBS): Append arm-get-next-pcs.o,
	arm-linux.o.
	(ALLDEPFILES): Append arm-get-next-pcs.c, arm-linux.c
	(arm-linux.o): New rule.
	(arm-get-next-pcs.o): New rule.
	* arch/arm-get-next-pcs.c: New file.
	* arch/arm-get-next-pcs.h: New file.
	* arch/arm-linux.h: New file.
	* arch/arm-linux.c: New file.
	* arm.c: Include common-regcache.c.
	(thumb_advance_itstate): Moved from arm-tdep.c.
	(arm_instruction_changes_pc): Likewise.
	(thumb_instruction_changes_pc): Likewise.
	(thumb2_instruction_changes_pc): Likewise.
	(shifted_reg_val): Likewise.
	* arm.h (submask): Move macro from arm-tdep.h
	(bit): Likewise.
	(bits): Likewise.
	(sbits): Likewise.
	(BranchDest): Likewise.
	(thumb_advance_itstate): Moved declaration from arm-tdep.h
	(arm_instruction_changes_pc): Likewise.
	(thumb_instruction_changes_pc): Likewise.
	(thumb2_instruction_changes_pc): Likewise.
	(shifted_reg_val): Likewise.
	* arm-linux-tdep.c: Include arch/arm.h, arch/arm-get-next-pcs.h
	arch/arm-linux.h.
	(arm_linux_get_next_pcs_ops): New struct.
	(ARM_SIGCONTEXT_R0, ARM_UCONTEXT_SIGCONTEXT,
	ARM_OLD_RT_SIGFRAME_SIGINFO, ARM_OLD_RT_SIGFRAME_UCONTEXT,
	ARM_NEW_RT_SIGFRAME_UCONTEXT, ARM_NEW_SIGFRAME_MAGIC): Move stack
	layout defines to arch/arm-linux.h.
	(arm_linux_sigreturn_next_pc_offset): Move to arch/arm-linux.c.
	(arm_linux_software_single_step): Adjust for arm_get_next_pcs
	implementation.
	* arm-tdep.c: Include arch/arm-get-next-pcs.h.
	(arm_get_next_pcs_ops): New struct.
	(submask): Move macro to arm.h.
	(bit): Likewise.
	(bits): Likewise.
	(sbits): Likewise.
	(BranchDest): Likewise.
	(thumb_instruction_changes_pc): Move to arm.c
	(thumb2_instruction_changes_pc): Likewise.
	(arm_instruction_changes_pc): Likewise.
	(shifted_reg_val): Likewise.
	(thumb_advance_itstate): Likewise.
	(thumb_get_next_pc_raw): Move to arm-get-next-pcs.c.
	(arm_get_next_pc_raw): Likewise.
	(arm_get_next_pc): Likewise.
	(thumb_deal_with_atomic_sequence_raw): Likewise.
	(arm_deal_with_atomic_sequence_raw): Likewise.
	(arm_deal_with_atomic_sequence): Likewise.
	(arm_get_next_pcs_read_memory_unsigned_integer): New function.
	(arm_get_next_pcs_addr_bits_remove): Likewise.
	(arm_get_next_pcs_syscall_next_pc): Likewise.
	(arm_get_next_pcs_is_thumb): Likewise.
	(arm_software_single_step): Adjust for arm_get_next_pcs
	implementation.
	* arm-tdep.h: (arm_get_next_pc): Remove declaration.
	(arm_get_next_pcs_read_memory_unsigned_integer):
	New declaration.
	(arm_get_next_pcs_addr_bits_remove): Likewise.
	(arm_get_next_pcs_syscall_next_pc): Likewise.
	(arm_get_next_pcs_is_thumb): Likewise.
	(arm_deal_with_atomic_sequence: Remove declaration.
	* common/gdb_vecs.h: Add CORE_ADDR vector definition.
	* configure.tgt (aarch64*-*-linux): Add arm-get-next-pcs.o,
	arm-linux.o.
	(arm*-wince-pe): Add arm-get-next-pcs.o.
	(arm*-*-linux*): Add arm-get-next-pcs.o, arm-linux.o,
	arm-get-next-pcs.o
	(arm*-*-netbsd*,arm*-*-knetbsd*-gnu): Add arm-get-next-pcs.o.
	(arm*-*-openbsd*): Likewise.
	(arm*-*-symbianelf*): Likewise.
	(arm*-*-*): Likewise.
	* symtab.h: Move CORE_ADDR vector definition to gdb_vecs.h.

gdb/gdbserver/ChangeLog:

	* Makefile.in (SFILES): Append arch/arm-linux.c,
	arch/arm-get-next-pcs.c.
	(arm-linux.o): New rule.
	(arm-get-next-pcs.o): New rule.
	* configure.srv (arm*-*-linux*): Add arm-get-next-pcs.o,
	arm-linux.o.
	* linux-aarch32-low.c (arm_abi_breakpoint): Remove macro.  Moved
	to linux-aarch32-low.c.
	(arm_eabi_breakpoint, arm_breakpoint): Likewise.
	(arm_breakpoint_len, thumb_breakpoint): Likewise.
	(thumb_breakpoint_len, thumb2_breakpoint): Likewise.
	(thumb2_breakpoint_len): Likewise.
	(arm_is_thumb_mode): Make non-static.
	* linux-aarch32-low.h (arm_abi_breakpoint): New macro.  Moved
	from linux-aarch32-low.c.
	(arm_eabi_breakpoint, arm_breakpoint): Likewise.
	(arm_breakpoint_len, thumb_breakpoint): Likewise.
	(thumb_breakpoint_len, thumb2_breakpoint): Likewise.
	(thumb2_breakpoint_len): Likewise.
	(arm_is_thumb_mode): New declaration.
	* linux-arm-low.c: Include arch/arm-linux.h
	aarch/arm-get-next-pcs.h, sys/syscall.h.
	(get_next_pcs_ops): New struct.
	(get_next_pcs_addr_bits_remove): New function.
	(get_next_pcs_is_thumb): New function.
	(get_next_pcs_read_memory_unsigned_integer): Likewise.
	(arm_sigreturn_next_pc): Likewise.
	(get_next_pcs_syscall_next_pc): Likewise.
	(arm_gdbserver_get_next_pcs): Likewise.
	(struct linux_target_ops) <arm_gdbserver_get_next_pcs>:
	Initialize.
	* linux-low.h: Move CORE_ADDR vector definition to gdb_vecs.h.
	* server.h: Include gdb_vecs.h.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Enable software single stepping for while-stepping actions in GDBServer
@ 2015-12-18 17:51 sergiodj+buildbot
  2015-12-19 23:51 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-18 17:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7fe5e27e9d63b065731b1b0b69ffd344942f4f39 ***

Author: Antoine Tremblay <antoine.tremblay@ericsson.com>
Branch: master
Commit: 7fe5e27e9d63b065731b1b0b69ffd344942f4f39

Enable software single stepping for while-stepping actions in GDBServer

This patch enables software single stepping if the targets support it,
to do while-stepping actions.

No regressions, tested on ubuntu 14.04 ARMv7 and x86.
With gdbserver-{native,extended} / { -marm -mthumb }

gdb/gdbserver/ChangeLog:

	* linux-low.c (single_step): New function.
	(linux_resume_one_lwp_throw): Call single_step.
	(start_step_over): Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Enable conditional breakpoints for targets that support software single step in GDBServer
@ 2015-12-18 17:59 sergiodj+buildbot
  2015-12-20  0:47 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-18 17:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bd2b290956e9a1931cf593b0f2cc934867da1d45 ***

Author: Antoine Tremblay <antoine.tremblay@ericsson.com>
Branch: master
Commit: bd2b290956e9a1931cf593b0f2cc934867da1d45

Enable conditional breakpoints for targets that support software single step in GDBServer

This patch enables support for conditional breakpoints if the target supports
software single step.

This was disabled before as the implementations of software single step were too
simple as discussed in
https://sourceware.org/ml/gdb-patches/2015-04/msg01110.html.

Since these issues are now fixed support can be added back.

New tests passing :
PASS: gdb.base/cond-eval-mode.exp: set breakpoint condition-evaluation
target and related...

No regressions, tested on ubuntu 14.04 ARMv7 and x86.
With gdbserver-{native,extended} / { -marm -mthumb }

gdb/gdbserver/ChangeLog:

	* server.c (handle_query): Call target_supports_software_single_step.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Add documentation to gdb_compile
@ 2015-12-18 18:50 sergiodj+buildbot
  2015-12-20  1:45 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-18 18:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT aff9c0f8ab32e4f2f7ff9700afe84a61d23a08c6 ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: aff9c0f8ab32e4f2f7ff9700afe84a61d23a08c6

Add documentation to gdb_compile

This patch adds some documentation to gdb_compile.  It describes the
various options that can influence compilation.  Most of them are
handled by DejaGnu, but are not really documented anywhere, so I think
it's good to have a quick reference.  Not all possible options are
described, that would add way to much noise.  I chose those that I think
are relevant in the context of writing a test case.

gdb/testsuite/ChangeLog:

	* lib/gdb.exp (gdb_compile): Add function doc.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Cast to enum bfd_endian in arm_get_next_pcs_read_memory_unsigned_integer
@ 2015-12-18 20:40 sergiodj+buildbot
  2015-12-20  3:03 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-18 20:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5f2dfcfdb5def494d13bff72275f6ff75fe75f40 ***

Author: Antoine Tremblay <antoine.tremblay@ericsson.com>
Branch: master
Commit: 5f2dfcfdb5def494d13bff72275f6ff75fe75f40

Cast to enum bfd_endian in arm_get_next_pcs_read_memory_unsigned_integer

This patch fixes the cxx build broken by commit : d9311bfaf572cf14af577a66e79c51c491553552.

Pushed as obvious.

gdb/ChangeLog:

	* arm-tdep.c (arm_get_next_pcs_read_memory_unsigned_integer): Cast
	to enum bfd_endian)


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Make prompt_for_continue call throw_quit directly.
@ 2015-12-19  2:04 sergiodj+buildbot
  2015-12-20  3:53 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-19  2:04 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1690b6163c6546305cb5f8811d4c7348d8f435e0 ***

Author: Sandra Loosemore <sandra@codesourcery.com>
Branch: master
Commit: 1690b6163c6546305cb5f8811d4c7348d8f435e0

Make prompt_for_continue call throw_quit directly.

2015-12-18  Sandra Loosemore  <sandra@codesourcery.com>

	gdb/
	* utils.c (prompt_for_continue): Call throw_quit directly on 'q'.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Reset pagination counts even when stdin is not a tty.
@ 2015-12-19  2:13 sergiodj+buildbot
  2015-12-20  4:57 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-19  2:13 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bc008695f5f9c72d2eac80d5dc125659ca106fad ***

Author: Sandra Loosemore <sandra@codesourcery.com>
Branch: master
Commit: bc008695f5f9c72d2eac80d5dc125659ca106fad

Reset pagination counts even when stdin is not a tty.

2015-12-18  Sandra Loosemore  <sandra@codesourcery.com>

	gdb/
	* event-top.c (command_handler): Don't require stdin to be a tty
	for call to reinitialize_more_filter.
	* top.c (command_loop): Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
[parent not found: <a4e22a5df64a46bc99f737a982c0b9d1e8a45e2b@gdb-build>]
* [binutils-gdb] Remove HP-UX reference in testsuite/configure.ac
@ 2015-12-20 15:11 sergiodj+buildbot
  2015-12-20 15:58 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-20 15:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bf401b072ea4eaff1af425df69f32cad8d52b57c ***

Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: bf401b072ea4eaff1af425df69f32cad8d52b57c

Remove HP-UX reference in testsuite/configure.ac

gdb/testsuite/ChangeLog:

	* configure.ac: Remove HP-UX case.
	* configure: Regenerate.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Minor reformatting fix in gdbtypes.c::create_array_type_with_stride
@ 2015-12-21  3:05 sergiodj+buildbot
  2015-12-21  3:41 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-21  3:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b4a7fcab76dc6162a4db4b93d878a212553b722a ***

Author: Joel Brobecker <brobecker@adacore.com>
Branch: master
Commit: b4a7fcab76dc6162a4db4b93d878a212553b722a

Minor reformatting fix in gdbtypes.c::create_array_type_with_stride

gdb/ChangeLog:

        * gdbtypes.c (create_array_type_with_stride): Fix indentation.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Use arm_eabi_breakpoint on aarch32
@ 2015-12-21 14:08 sergiodj+buildbot
  2015-12-21 14:41 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-21 14:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 35adc03f3787405297259a1706608bdeaab4fda9 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 35adc03f3787405297259a1706608bdeaab4fda9

Use arm_eabi_breakpoint on aarch32

This patch is to get b37a6290 back again, which was removed by
d9311bfa by mistake.

gdb/gdbserver:

2015-12-21  Yao Qi  <yao.qi@linaro.org>

	* linux-aarch32-low.h [__aarch64__]: Use arm_abi_breakpoint
	arm breakpoint.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Remove references to HP CC/aCC compiler from testsuite
@ 2015-12-21 16:34 sergiodj+buildbot
  2015-12-21 17:32 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-21 16:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b6304613bf0bb1c188bed30eb3df6e3e154b4196 ***

Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: b6304613bf0bb1c188bed30eb3df6e3e154b4196

Remove references to HP CC/aCC compiler from testsuite

The HP CC/aCC compiler is exclusive to HP-UX, for which support has been
explicitly removed.  Therefore, It does not make sense to keep tests
for these compilers' quirks.

gdb/testsuite/ChangeLog:

	* gdb.base/break.exp: Remove references to HP CC/aCC compilers.
	* gdb.base/call-ar-st.exp: Likewise.
	* gdb.base/callfuncs.exp: Likewise.
	* gdb.base/condbreak.exp: Likewise.
	* gdb.base/constvars.exp: Likewise.
	* gdb.base/hbreak2.exp: Likewise.
	* gdb.base/langs.exp: Likewise.
	* gdb.base/list.exp: Likewise.
	* gdb.base/long_long.exp: Likewise.
	* gdb.base/ptype.exp: Likewise.
	* gdb.base/scope.exp: Likewise.
	* gdb.base/signals.exp: Likewise.
	* gdb.base/so-impl-ld.exp: Likewise.
	* gdb.base/varargs.exp: Likewise.
	* gdb.base/volatile.exp: Likewise.
	* gdb.base/whatis.exp: Likewise.
	* gdb.cp/cplusfuncs.exp: Likewise.
	* gdb.cp/inherit.exp: Likewise.
	* gdb.cp/local.exp: Likewise.
	* gdb.cp/member-ptr.exp: Likewise.
	* gdb.cp/method.exp: Likewise.
	* gdb.cp/overload.exp: Likewise.
	* gdb.cp/templates.exp: Likewise.
	* gdb.stabs/weird.exp: Likewise.
	* lib/compiler.c: Likewise.
	* lib/compiler.cc: Likewise.
	* lib/cp-support.exp: Likewise.
	* lib/gdb.exp: Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Remove HP-UX references fom testsuite
@ 2015-12-21 18:02 sergiodj+buildbot
  2015-12-21 18:36 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-21 18:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3ca22649a6dfeb71058c33be4d0542b98f1f0ff5 ***

Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: 3ca22649a6dfeb71058c33be4d0542b98f1f0ff5

Remove HP-UX references fom testsuite

This patch removes all special cases for HP-UX, for which support has
been removed earlier, that I found in the testsuite.  Note that the hppa
architecture != HP-UX, since other OSes can run on hppa, so I tried to
leave everything that is not HP-UX specific.

Two complete tests were completely HP-UX specific, so I removed them.

I ran the testsuite on Linux x86-64, native and native-gdbserver, and
noticed no regressions.

gdb/testsuite/ChangeLog:

	* gdb.asm/asm-source.exp: Remove HP-UX references.
	* gdb.base/annota1.exp: Likewise.
	* gdb.base/annota3.exp: Likewise.
	* gdb.base/attach.exp: Likewise.
	* gdb.base/bigcore.exp: Likewise.
	* gdb.base/break.exp: Likewise.
	* gdb.base/call-ar-st.exp: Likewise.
	* gdb.base/callfuncs.exp: Likewise.
	* gdb.base/catch-fork-static.exp: Likewise.
	* gdb.base/display.exp: Likewise.
	* gdb.base/foll-exec-mode.exp: Likewise.
	* gdb.base/foll-exec.exp: Likewise.
	* gdb.base/foll-fork.exp: Likewise.
	* gdb.base/foll-vfork.exp: Likewise.
	* gdb.base/funcargs.exp: Likewise.
	* gdb.base/hbreak2.exp: Likewise.
	* gdb.base/inferior-died.exp: Likewise.
	* gdb.base/interrupt.exp: Likewise.
	* gdb.base/multi-forks.exp: Likewise.
	* gdb.base/nodebug.exp: Likewise.
	* gdb.base/sepdebug.exp: Likewise.
	* gdb.base/solib1.c: Likewise.
	* gdb.base/step-test.exp: Likewise.
	* gdb.mi/non-stop.c: Likewise.
	* gdb.mi/pthreads.c: Likewise.
	* gdb.multi/bkpt-multi-exec.ex: Likewise.
	* gdb.threads/pthreads.c: Likewise.
	* gdb.threads/staticthreads.exp: Likewise.
	* lib/future.exp: Likewise.
	* lib/gdb.exp: Likewise.
	* gdb.base/so-indr-cl.c: Remove.
	* gdb.base/so-indr-cl.exp: Likewise.
	* gdb.base/solib.c: Likewise.
	* gdb.base/solib.exp: Likewise.
	* gdb.base/solib2.c: Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Add an expect for running commands with CLI jump
@ 2015-12-22  3:04 sergiodj+buildbot
  2015-12-22  3:38 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-22  3:04 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6d265cb4a956310d2cae231ac63a37e11fe376e1 ***

Author: Thomas Preud'homme <thomas.preudhomme@arm.com>
Branch: master
Commit: 6d265cb4a956310d2cae231ac63a37e11fe376e1

Add an expect for running commands with CLI jump

2015-12-22  Thomas Preud'homme  <thomas.preudhomme@arm.com>

gdb/testsuite/
    * lib/mi-support.exp (mi_run_cmd_full): Add an expect for the CLI jump
    case.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Add support for ARM's NOREAD section flag.
@ 2015-12-22 14:23 sergiodj+buildbot
  2015-12-22 14:54 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-22 14:23 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ac4c9b0459fe89f2b84bf8b18a3bf86bf569b7d1 ***

Author: Mickael Guene <mickael.guene@st.com>
Branch: master
Commit: ac4c9b0459fe89f2b84bf8b18a3bf86bf569b7d1

Add support for ARM's NOREAD section flag.

include/elf
     * arm.h: Add arm SHF_ARM_NOREAD section flag.

bfd  * bfd-in2.h: Regenerate.
     * section.c: Add SEC_ELF_NOREAD.
     * elf32-arm.c (elf32_arm_post_process_headers): Only set
     PF_X attribute if a segment only contains section with
     SHF_ARM_NOREAD flag.
     (elf32_arm_fake_sections): Add SEC_ELF_NOREAD conversion.
     (elf32_arm_section_flags): New function to convert SHF_ARM_NOREAD
     to bfd flag.
     (elf32_arm_lookup_section_flags): New function to allow
     INPUT_SECTION_FLAGS directive with SHF_ARM_NOREAD flag.
     (elf32_arm_special_sections): Add special sections array
     to catch section prefix by '.text.noread' pattern.

ld/testsuite
     * ld-arm/arm-elf.exp: New tests.
     * ld-arm/thumb1-input-section-flag-match.d: New
     * ld-arm/thumb1-input-section-flag-match.s: New
     * ld-arm/thumb1-noread-not-present-mixing-two-section.d: New
     * ld-arm/thumb1-noread-not-present-mixing-two-section.s: New
     * ld-arm/thumb1-noread-present-one-section.d: New
     * ld-arm/thumb1-noread-present-one-section.s: New
     * ld-arm/thumb1-noread-present-two-section.d: New
     * ld-arm/thumb1-noread-present-two-section.s: New

binutils
	* readelf.c (get_elf_section_flags): Add support for ARM specific
	section flags.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] RXv2 support update
@ 2015-12-22 14:38 sergiodj+buildbot
  2015-12-22 15:57 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-22 14:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 239efab16429cad466591ccd1c57bba786171765 ***

Author: Yoshinori Sato <ysato@users.sourceforge.jp>
Branch: master
Commit: 239efab16429cad466591ccd1c57bba786171765

RXv2 support update

2015-12-22  Yoshinori Sato <ysato@users.sourceforge.jp>

opcodes/
	* rx-decode.opc (movco): Use uniqe id.
	(movli): Likewise.
	(stnz): Condition fix.
	(mvtacgu): Destination fix.
	* rx-decode.c: Regenerate.

bfd/
	* archures.c: Add bfd_mach_rx_v2.
	* bfd-in2.h: Regenerate.
	* cpu-rx.c (arch_info_struct): Add v2 information.
	* elf32-rx.c (elf32_rx_machine): Add v2 support.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [win32] cannot automatically find executable file [...] warning at GDB startup
@ 2015-12-22 15:35 sergiodj+buildbot
  2015-12-22 17:02 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-22 15:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT aec47d1d54be415050bbd3ccb93c0157d60ed92d ***

Author: Joel Brobecker <brobecker@adacore.com>
Branch: master
Commit: aec47d1d54be415050bbd3ccb93c0157d60ed92d

[win32] cannot automatically find executable file [...] warning at GDB startup

The following change...

    commit 43499ea30db2a866412c86952c7e1d7b158d806f
    Date:   Tue Nov 17 15:17:44 2015 +0000
    Subject: [C++/mingw] windows-nat.c casts

... causes a small regression in GDB, where we get the following
warning at startup:

    % gdb
    C:\[...]\gdb.exe: warning: cannot automatically find executable file or library to read symbols.
    Use "file" or "dll" command to load executable/libraries directly.
    GNU gdb (GDB) 7.10.50.20151218-cvs (with AdaCore local changes)
    [...]
    (gdb)

The warning comes from _initialize_loadable which tries to dynamically
load some symbols from kernel32.dll and psapi.dll, and in particular:

  hm = LoadLibrary ("psapi.dll");
  if (hm)
    {
      GPA (hm, EnumProcessModules);
      GPA (hm, GetModuleInformation);
      GPA (hm, GetModuleFileNameEx);
    }

The problem is that the new GPA macro assumes that the name of
the variable we use to point to the function, and the name of
its associated symbol are the same. This is mostly the case,
except for GetModuleFileNameEx, where the name is provided by
the GetModuleFileNameEx_name macro (defined differently depending
on whether we are on cygwin or not). As a result, the dynamic
resolution for GetModuleFileNameEx returns NULL, and we trip
the following check which leads to the warning:

  if (!EnumProcessModules || !GetModuleInformation || !GetModuleFileNameEx)
    {
      [...]
      warning(_("[...]"));
    }

This patch fixes the problem by calling GetProcAddress directly,
rather than through the GPA macro, but in a way which hopefully
avoids the C++ compilation warning that the previous patch was
trying to get rid of.

gdb/ChangeLog:

	* windows-nat.c (_initialize_loadable): Fix computing of
	GetModuleFileNameEx.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] gdbserver crash in gdb/gdbserver/thread.c::thread_search_callback
@ 2015-12-22 15:43 sergiodj+buildbot
  2015-12-22 18:17 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-22 15:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0e50fe5ca6ed2ce780cbbfa516aec20b023433ce ***

Author: Joel Brobecker <brobecker@adacore.com>
Branch: master
Commit: 0e50fe5ca6ed2ce780cbbfa516aec20b023433ce

gdbserver crash in gdb/gdbserver/thread.c::thread_search_callback

Connecting GDB to a LynxOS-178 GDBserver causes GDBserver to crash:

    % gdbserver :4444 simple_main
    Process simple_main created; pid = 19
    Listening on port 4444
    Remote debugging from host 205.232.38.10
    Segmentation fault (core dumped)

The crash happens in thread_search_callback where the function
calls the_target->thread_stopped (via the thread_stopped macro)
without verifying whether the callback is NULL or not.

For the record, the regression was introduced by:

    commit a67a9faef0e32886c83611cc7a0ba61e91123063
    Date:   Mon Nov 30 16:05:26 2015 +0000
    Subject: gdbserver:prepare_access_memory: pick another thread

This patch avoids the crash by checking the value of the callback
first, before calling it.

gdb/gdbserver/ChangeLog:

        * target.c (thread_search_callback): Add check that
        the thread_stopped target callback is not NULL before
        calling it.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [lynxos] gdbserver hangs when killing inferior from GDB
@ 2015-12-22 15:50 sergiodj+buildbot
  2015-12-22 19:17 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-22 15:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4abd5ed2221c826bcb843794286777452de5c50b ***

Author: Joel Brobecker <brobecker@adacore.com>
Branch: master
Commit: 4abd5ed2221c826bcb843794286777452de5c50b

[lynxos] gdbserver hangs when killing inferior from GDB

With any program under GDBserver control on LynxOS, killing
the program from the debugger (using the "kill" command) causes
GDBserver to properly kill the inferior but GDBserver then hangs.

This change of behavior occured after the following change was
applied:

    commit f0ea042932e6922c90df3fd0001497d287b97677
    Date:   Mon Nov 30 16:05:27 2015 +0000
    Subject: gdbserver: don't exit until GDB disconnects

One of the changes introduced by the commit above is that
process_serial_event no longer calls exit after handling
the vKill packet. Instead, what happens is that we wait
until captured_main finds that we no longer have any inferior
to debug, at which point it throws_quit. This (normal) exception
is then expected to propagate all the way to the exception handle
in function "main", which calls exit.

However, before the exception gets propagated, the cleanups
are first executed, and one of the cleanups in question is
detach_or_kill_for_exit_cleanup, which was put in place by
captured_main. detach_or_kill_for_exit_cleanup is basically
a wrapper around detach_or_kill_for_exit, which iterates
over all inferiors, and kills them all.

In our case, we have only one inferior, which we have already
killed during the handling for the "vKill" packet. Unfortunately,
we did not properly clean our internal data for that inferior up,
and so detach_or_kill_for_exit thinks that we still have one inferior,
and therefore tries to kill it. This results in lynx_kill being
called, doing the following:

    lynx_ptrace (PTRACE_KILL, ptid, 0, 0, 0);
    lynx_wait (ptid, &status, 0);
    the_target->mourn (process);

The hang is caused by the call to lynx_wait, which waits for
an event from a process which does not exist...

This patch fixes the issue by enhancing lynx_mourn to clean
the threads and process list up.

gdb/gdbserver/ChangeLog:

        * lynx-low.c (lynx_delete_thread_callback): New function.
        (lynx_mourn): Properly delete our process and all of its
        threads.  Remove call to clear_inferiors.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Remove HP-UX reference in foll-vfork.exp
@ 2015-12-22 16:10 sergiodj+buildbot
  2015-12-22 21:23 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-22 16:10 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fe33faff35a8ee19db823149e764e3373e603bb9 ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: fe33faff35a8ee19db823149e764e3373e603bb9

Remove HP-UX reference in foll-vfork.exp

One more I just found.

Tested with native, native-gdbserver and native-extended-gdbserver on
Linux.

gdb/testsuite/ChangeLog:

	* gdb.base/foll-vork.exp: Remove HP-UX special case.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [testsuite/Ada] stop using project files when building test programs
@ 2015-12-24  5:38 sergiodj+buildbot
  2015-12-24  6:11 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-24  5:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ab8314b3d99625c9a2125d39f4f3e74bf9e49cce ***

Author: Joel Brobecker <brobecker@adacore.com>
Branch: master
Commit: ab8314b3d99625c9a2125d39f4f3e74bf9e49cce

[testsuite/Ada] stop using project files when building test programs

The current approach when building Ada programs for testing is
based on the use of a project file (testsuite/gdb.ada/gnat_ada.gpr).
To do that, we pass a number of additional arguments to target_compile,
one of them being the project file (via "-P/path/to/gnat_ada.gpr").
This used to work well-enough, but AdaCore is currently working towards
removing project-file support from gnatmake (the prefered tool for
using project files is gprbuild). So, we need to either switch
the compilation to gprbuild, or stop using project files.

First, using gprbuild is not always what users will be using to
build their applications. So having the option of using gnatmake
provides more flexibility towards exactly reproducing past bugs.
If we ever need a testcase that requires the use of gprbuild, then
I believe support for a new target needs to be added to dejagnu's
target_compile.

Also, the only real reason behind using a project file in the first
place is that we wanted to make it easy to specify the directory
where all compilation artifacts get stored. This is a consequence
of the organization choice we made for gdb.ada to keep each testcase
well organized. It is very easy to achieve that goal without using
project files.

This is therefore what this patch does: It change gdb_compile_ada
to build any program using gnatmake without using a project file
(by temporarily changing the current working directory).

There is a small (beneficial) side-effect; in the situation where
GDB is built in-tree, gnatmake is called as...

        % gnatmake [...] unit.adb

... which means that the debugging info in unit.o will say contain
a filename whose name is 'unit.adb', rather than '/path/to/unit.adb'.
This also better matches what users might typically do. But the side-
effect is that the unit name in the GDB output is not always a full
path. This patch tweaks a couple of testcases to make the path part
optional.

gdb/testsuite:

        * lib/ada.exp (target_compile_ada_from_dir): New function.
        (gdb_compile_ada): Reimplement avoiding the use of project files.
        * gdb.ada/gnat_ada.gpr: Delete.
        * gdb.ada/cond_lang.exp: Adjust test to make path before
        filename optional.
        * gdb.ada/small_reg_param.exp: Likewise.

Tested on x86_64-linux, with both in-tree and out-of-tree builds.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Consolidate Thumb-1/Thumb-2 ISA detection
@ 2015-12-24  9:44 sergiodj+buildbot
  2015-12-24 10:13 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-24  9:44 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fc289b0a832c536a2ec324634cb420f39b212696 ***

Author: Thomas Preud'homme <thomas.preudhomme@arm.com>
Branch: master
Commit: fc289b0a832c536a2ec324634cb420f39b212696

Consolidate Thumb-1/Thumb-2 ISA detection

2015-12-24  Thomas Preud'homme  <thomas.preudhomme@arm.com>

gas/
    * config/tc-arm.c (move_or_literal_pool): Check mov.w, mvm and movw
    availability against arm_ext_v6t2 instead of checking arm_arch_t2,
    fixing comments along the way.
    (handle_it_state): Check arm_ext_v6t2 instead of arm_arch_t2 to
    generate IT instruction.
    (t1_isa_t32_only_insn): New function.
    (md_assemble): Use above new function to check for invalid wide
    instruction for CPU Thumb ISA and to determine what Thumb extension
    bit is necessary for that instruction.
    (md_apply_fix): Use arm_ext_v6t2 instead of arm_arch_t2 to decide if
    branch is out of range.

include/opcode/
    * arm.h (ARM_ARCH_THUMB2): Add comment explaining its meaning and
    remove extension bit not including any Thumb-2 instruction.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Add assembler support for ARMv8-M Mainline
@ 2015-12-24  9:52 sergiodj+buildbot
  2015-12-24 11:13 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-24  9:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4ed7ed8db2289a9cd61312c14344cb210dc229b7 ***

Author: Thomas Preud'homme <thomas.preudhomme@arm.com>
Branch: master
Commit: 4ed7ed8db2289a9cd61312c14344cb210dc229b7

Add assembler support for ARMv8-M Mainline

2015-12-24  Thomas Preud'homme  <thomas.preudhomme@arm.com>

bfd/
    (tag_cpu_arch_combine): Adjust v4t_plus_v6_m and comb array to account
    for new TAG_CPU_ARCH_V4T_PLUS_V6_M value.  Deal with NULL values in
    comb array.

binutils/
    * readelf.c (arm_attr_tag_CPU_arch): Add ARMv8-M Mainline Tag_CPU_arch
    value.
    (arm_attr_tag_THUMB_ISA_use): Add ARMv8-M Mainline Tag_THUMB_ISA_use
    value.

gas/
    * config/tc-arm.c (arm_ext_m): Include ARMv8-M.
    (arm_ext_v8m): New feature for ARMv8-M.
    (arm_ext_atomics): New feature for ARMv8 atomics.
    (do_tt): New encoding function for TT* instructions.
    (insns): Add new entries for ARMv8-M specific instructions and
    reorganize the ones shared by ARMv8-M Mainline and ARMv8-A.
    (arm_archs): Define armv8-m.main architecture.
    (cpu_arch_ver): Define ARM_ARCH_V8M_MAIN architecture version and
    clarify the ordering rule.
    (aeabi_set_public_attributes): Use TAG_CPU_ARCH_* macro to refer to
    Tag_CPU_arch values for ARMv7e-M detection.  Add logic to keep setting
    Tag_CPU_arch to ARMv8-A for -march=all.  Also set Tag_CPU_arch_profile
    to 'A' if extension bit for atomic instructions is set, unless it is
    ARMv8-M.  Set Tag_THUMB_ISA_use to 3 for ARMv8-M.  Set Tag_DIV_use to 0
    for ARMv8-M Mainline.

gas/testsuite/
    * gas/arm/archv8m.s: New file.
    * gas/arm/archv8m-main.d: Likewise.
    * gas/arm/attr-march-armv8m.main.d: Likewise.
    * gas/arm/any-armv8m.s: Likewise.
    * gas/arm/any-armv8m.d: Likewise.

include/elf/
    * arm.h (TAG_CPU_ARCH_V8M_MAIN): Declare.
    (MAX_TAG_CPU_ARCH): Define to TAG_CPU_ARCH_V8M_MAIN.
    (TAG_CPU_ARCH_V4T_PLUS_V6_M): Define to unused value 15.

include/opcode/
    * arm.h (ARM_EXT2_ATOMICS): New extension bit.
    (ARM_EXT2_V8M): Likewise.
    (ARM_EXT_V8): Adjust comment with regards to atomics and remove
    mention of legacy use for that bit.
    (ARM_AEXT2_V8_1A): New architecture extension bitfield.
    (ARM_AEXT2_V8_2A): Likewise.
    (ARM_AEXT_V8M_MAIN): Likewise.
    (ARM_AEXT2_V8M): Likewise.
    (ARM_ARCH_V8A): Use ARM_EXT2_ATOMICS for features in second bitfield.
    (ARM_ARCH_V8_1A): Likewise with ARM_AEXT2_V8_1A.
    (ARM_ARCH_V8_2A): Likewise with ARM_AEXT2_V8_2A.
    (ARM_ARCH_V8M_MAIN): New architecture feature bitfield.
    (ARM_ARCH_V8A_FP): Use ARM_EXT2_ATOMICS for features in second bitfield
    and reindent.
    (ARM_ARCH_V8A_SIMD): Likewise.
    (ARM_ARCH_V8A_CRYPTOV1): Likewise.
    (ARM_ARCH_V8_1A_FP): Use ARM_AEXT2_V8_1A to set second bitfield of
    feature bits.
    (ARM_ARCH_V8_1A_SIMD): Likewise.
    (ARM_ARCH_V8_1A_CRYPTOV1): Likewise.

opcodes/
    * arm-dis.c (arm_opcodes): Guard lda, ldab, ldaex, ldaexb, ldaexh, stl,
    stlb, stlh, stlex, stlexb and stlexh by ARM_EXT2_ATOMICS instead of
    ARM_EXT_V8.
    (thumb32_opcodes): Add entries for wide ARMv8-M instructions.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Add assembler support for ARMv8-M Baseline
@ 2015-12-24 10:35 sergiodj+buildbot
  2015-12-24 12:20 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-24 10:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ff8646eef8bdef6fe3091eb79627929c1c100c6a ***

Author: Thomas Preud'homme <thomas.preudhomme@arm.com>
Branch: master
Commit: ff8646eef8bdef6fe3091eb79627929c1c100c6a

Add assembler support for ARMv8-M Baseline

2015-12-24  Thomas Preud'homme  <thomas.preudhomme@arm.com>

bfd/
    (tag_cpu_arch_combine): Adjust comment in v4t_plus_v6_m with regards
    to merging with ARMv8-M Baseline.

binutils/
    * readelf.c (arm_attr_tag_CPU_arch): Add ARMv8-M Baseline Tag_CPU_arch
    value.

gas/
    * config/tc-arm.c (arm_ext_v6t2_v8m): New feature for instructions
    shared between ARMv6T2 and ARMv8-M.
    (move_or_literal_pool): Check mov.w/mvn and movw availability against
    arm_ext_v6t2 and arm_ext_v6t2_v8m respectively instead of checking
    arm_arch_t2.
    (do_t_branch): Error out for wide conditional branch instructions if
    targetting ARMv8-M Baseline.
    (non_v6t2_wide_only_insn): Add the logic for new wide-only instructions
    in ARMv8-M Baseline.
    (wide_insn_ok): New function.
    (md_assemble): Use wide_insn_ok instead of non_v6t2_wide_only_insn and
    adapt error message for unsupported wide instruction to ARMv8-M
    Baseline.
    (insns): Reorganize instructions shared by ARMv8-M Baseline and
    ARMv6t2 architecture.
    (arm_cpus): Set feature bit ARM_EXT2_V6T2_V8M for marvell-pj4 and
    marvell-whitney cores.
    (arm_archs): Define armv8-m.base architecture.
    (cpu_arch_ver): Define ARM_ARCH_V8M_BASE architecture version.
    (aeabi_set_public_attributes): Add logic to set Tag_CPU_arch to 17 for
    ARMv8-M Mainline.  Set Tag_DIV_use for ARMv8-M Baseline as well.

gas/testsuite/
    * gas/arm/archv8m-base.d: New file.
    * gas/arm/attr-march-armv8m.base.d: Likewise.
    * gas/arm/armv8m.base-idiv.d: Likewise.
    * gas/arm/any-armv8m.d: Adapt to deal with ARMv8-M Baseline.

include/elf/
    * arm.h (TAG_CPU_ARCH_V8M_BASE): Declare.

include/opcode/
    * arm.h (ARM_EXT2_V6T2_V8M): New extension bit.
    (ARM_AEXT2_V8A): New architecture extension bitfield.
    (ARM_AEXT2_V8_1A): Use ARM_AEXT2_V8A instead of ARM_EXT2_ATOMICS.
    (ARM_AEXT_V8M_BASE): New architecture extension bitfield.
    (ARM_AEXT2_V8M): Add extension bit ARM_EXT2_V6T2_V8M.
    (ARM_ARCH_V6T2): Use ARM_EXT2_V6T2_V8M for the second extension
    bitfield.
    (ARM_ARCH_V6KT2): Likewise.
    (ARM_ARCH_V6ZT2): Likewise.
    (ARM_ARCH_V6KZT2): Likewise.
    (ARM_ARCH_V7): Likewise.
    (ARM_ARCH_V7A): Likewise.
    (ARM_ARCH_V7VE): Likewise.
    (ARM_ARCH_V7R): Likewise.
    (ARM_ARCH_V7M): Likewise.
    (ARM_ARCH_V7EM): Likewise.
    (ARM_ARCH_V8A): Likewise.
    (ARM_ARCH_V8M_BASE): New architecture bitfield.
    (ARM_ARCH_THUMB2): Include instructions shared by ARMv6t2 and ARMv8-M.
    (ARM_ARCH_V7A_SEC): Use ARM_EXT2_V6T2_V8M for the second extension
    bitfield and reindent.
    (ARM_ARCH_V7A_MP_SEC): Likewise.
    (ARM_ARCH_V7R_IDIV): Likewise.
    (ARM_ARCH_V8A_FP): Use ARM_AEXT2_V8A instead of ARM_EXT2_ATOMICS.
    (ARM_ARCH_V8A_SIMD): Likewise.
    (ARM_ARCH_V8A_CRYPTOV1): Likewise.

opcodes/
    * arm-dis.c (arm_opcodes): Guard movw, movt cbz, cbnz, clrex, ldrex,
    ldrexb, ldrexh, strex, strexb, strexh shared by ARMv6T2 and ARMv8-M by
    ARM_EXT2_V6T2_V8M instead of ARM_EXT_V6T2.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] sim: delete SIM_HAVE_SIMCACHE
@ 2015-12-25  0:34 sergiodj+buildbot
  2015-12-25  1:08 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-25  0:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8abe6c668e9336418277e64983587f121c8534e6 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 8abe6c668e9336418277e64983587f121c8534e6

sim: delete SIM_HAVE_SIMCACHE

This was used by the old run interface, but we punted that awhile ago,
so drop this define too.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] sim: delete SIM_HAVE_MEM_SIZE
@ 2015-12-25  1:00 sergiodj+buildbot
  2015-12-25  3:30 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-25  1:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b1af947345ccba81244d3370756d0047d3bc8b6e ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: b1af947345ccba81244d3370756d0047d3bc8b6e

sim: delete SIM_HAVE_MEM_SIZE

This define isn't used anywhere (doesn't seem to ever have been used by
versions committed), so delete the commented out code as it's dead.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] sim: delete SIM_HAVE_FLATMEM support
@ 2015-12-25  1:25 sergiodj+buildbot
  2015-12-25  5:56 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-25  1:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3cabaf66d6ec7343bd3badc5c44c2ddd06221913 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 3cabaf66d6ec7343bd3badc5c44c2ddd06221913

sim: delete SIM_HAVE_FLATMEM support

No target has used this, and it's a cheap hack in place in using the
common memory module.  We want everyone using that though, so drop
support for flatmem entirely.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] sim: enable watchpoint module everywhere
@ 2015-12-25  1:42 sergiodj+buildbot
  2015-12-25  8:39 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-25  1:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 84e8e361dd3a3dd7314759f7f07927dac401d0e6 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 84e8e361dd3a3dd7314759f7f07927dac401d0e6

sim: enable watchpoint module everywhere

We build & bundle the watchpoint module everywhere, but we don't make
the command line flags available by default.  A few targets opted in,
but most did not.  Just enable the flag for everyone.  Not all targets
will respect the flags (making them nops), but shouldn't be a big deal.
This is how we handle other common modules already.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] sim: h8300: move h8300-specific options out of common code
@ 2015-12-25  1:50 sergiodj+buildbot
  2015-12-25 10:50 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-25  1:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bd3fb5b8fb33adb751407a128e1f2240dfb215d9 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: bd3fb5b8fb33adb751407a128e1f2240dfb215d9

sim: h8300: move h8300-specific options out of common code

Register the options in sim_open like other arches to avoid having to hack
up the common modules.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] sim: delete old breakpoint code
@ 2015-12-25  2:16 sergiodj+buildbot
  2015-12-25 12:30 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-25  2:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cec19744887931294e9d4a1dfa4fa8bd42e57ae5 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: cec19744887931294e9d4a1dfa4fa8bd42e57ae5

sim: delete old breakpoint code

This code relies on the old sim-break module, but that was deleted in 2003.
The module only existed for gdb to tell the sim to set breakpoints on its
behalf, but then that logic was abandoned in favor of gdb knowing all about
proper breakpoints (since it does already for non-sim targets).  Some dead
code lived on in the older ports though -- clean it up now.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] sim: cris: move option install to sim_open
@ 2015-12-25  2:24 sergiodj+buildbot
  2015-12-25 14:12 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-25  2:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9db2b719087eb42cfb31018fe87657243f6185c9 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 9db2b719087eb42cfb31018fe87657243f6185c9

sim: cris: move option install to sim_open

We've moved custom option install for other targets to sim_open, so update
cris too.  It's the last one using MODULE_LIST, so we can drop that from
the common code too.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] sim: mips: delete TARGET_TX3904 define
@ 2015-12-25  3:50 sergiodj+buildbot
  2015-12-25 17:03 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-25  3:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ef04e3719831b50e62cb97cd0ac10548a35cef40 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: ef04e3719831b50e62cb97cd0ac10548a35cef40

sim: mips: delete TARGET_TX3904 define

With the LMA cleanup, we no longer need this define.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] sim: always enable callback memory
@ 2015-12-25  5:41 sergiodj+buildbot
  2015-12-25 19:02 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-25  5:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9e8e7dd966670c80f3b71f8cf7e07f2843b33e80 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 9e8e7dd966670c80f3b71f8cf7e07f2843b33e80

sim: always enable callback memory

We enable WITH_CALLBACK_MEMORY everywhere and don't provide a way to
turn it off, and no target does so.  Make it unconditional for all
to keep things simple.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] sim: device_error: punt
@ 2015-12-25  7:29 sergiodj+buildbot
  2015-12-25 20:05 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-25  7:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 42a3af5688cd41550e2b517f676f03f2842e615b ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 42a3af5688cd41550e2b517f676f03f2842e615b

sim: device_error: punt

Only four targets implement this function, and three of them do nothing.
The 4th merely calls abort.  Since calls to this function are followed
by calls to sim_hw_abort or sim_io_error, this is largely useless.  In
the two places where we don't, replace the call with sim_engine_abort.
We want to kill off the WITH_DEVICES logic in favor of WITH_HW, so this
is a good first step.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] sim: arm: delete unused code
@ 2015-12-25  8:19 sergiodj+buildbot
  2015-12-25 22:02 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-25  8:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 91d6df784db745df2b0a6827de8306246083bc94 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 91d6df784db745df2b0a6827de8306246083bc94

sim: arm: delete unused code

These vestiges of the 20 year old emulator are just getting in the way.
Punt all the dead code we either don't compile or don't use.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] sim: drop WITH_ENGINE define
@ 2015-12-25 10:01 sergiodj+buildbot
  2015-12-26  1:11 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-25 10:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cf59f47ebeccf4ea82b6c529c882644e4c445323 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: cf59f47ebeccf4ea82b6c529c882644e4c445323

sim: drop WITH_ENGINE define

We enable this everywhere already, and all new ports should use the
engine logic, so no point in making it an option to disable.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] sim: hw-properties: delete trace calls
@ 2015-12-25 10:59 sergiodj+buildbot
  2015-12-26  2:13 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-25 10:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 49aef5a5b8873b80f43ca79edd5755d28cab53b3 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 49aef5a5b8873b80f43ca79edd5755d28cab53b3

sim: hw-properties: delete trace calls

These trace calls don't seem to add anything useful and break the cris
hw tests, so punt them.  They were disabled before commit 6d519a4606b9
but were re-enabled as part of TRACE macro cleanups.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] sim: cris: clean up rvdummy a bit
@ 2015-12-25 11:46 sergiodj+buildbot
  2015-12-26  5:25 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-25 11:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 13e49fd6364e94625985b9eb15da5b1decd6a196 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 13e49fd6364e94625985b9eb15da5b1decd6a196

sim: cris: clean up rvdummy a bit

This fixes a few warnings when compiling the rvdummy tool.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] sim: cris: migrate from WITH_DEVICES to WITH_HW
@ 2015-12-25 12:14 sergiodj+buildbot
  2015-12-26  7:09 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-25 12:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 34cf511206839b0f2b76870bf2d487c2dbcdbc1f ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 34cf511206839b0f2b76870bf2d487c2dbcdbc1f

sim: cris: migrate from WITH_DEVICES to WITH_HW

The cris port was using the device framework to handle two addresses when
the --cris-900000xx flag was specified.  That can be implemented using the
newer hardware framework instead which allows us to drop the device logic
entirely, as well as delete the tconfig.h file.  Basically we create a new
cris_900000xx device model and move the read logic out of devices.c and
into that.  The rest of the devices logic was callback to the hardware
framework already.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] sim: m32r: migrate from WITH_DEVICES to WITH_HW
@ 2015-12-25 18:20 sergiodj+buildbot
  2015-12-26  8:29 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-25 18:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9c0c156bb7ddca2d3fce7bea96631715f8c67390 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 9c0c156bb7ddca2d3fce7bea96631715f8c67390

sim: m32r: migrate from WITH_DEVICES to WITH_HW

The m32r port was using the device framework to handle two devices: the
cache and uart registers.  Both can be implemented in the newer hardware
framework instead which allows us to drop the device logic entirely, as
well as delete the tconfig.h file.

While creating the new uart device model, I also added support for using
stdin to read/write data rather than only supporting sockets.

This has been lightly tested as there doesn't appear to be test coverage
for the code already.  If anyone still cares about this port, then they
should (hopefully) file bug reports.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] sim: frv: punt WITH_DEVICE support
@ 2015-12-25 18:35 sergiodj+buildbot
  2015-12-26  9:22 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-25 18:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2023145711ca36f06258e07f4fa1c490efbbf37e ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 2023145711ca36f06258e07f4fa1c490efbbf37e

sim: frv: punt WITH_DEVICE support

The frv port used the device logic to support a single cache address,
and the comments around that are "these were merely copied from a diff
port and are unused", plus the code to attach the memory is "#if 0".
Just punt it all.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Document that the PATTERN argument to gdb_test is optional.
@ 2015-12-25 19:47 sergiodj+buildbot
  2015-12-26 10:31 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-25 19:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 79fad5b803e22798bcb087066234a954d0ccdc60 ***

Author: Sandra Loosemore <sandra@codesourcery.com>
Branch: master
Commit: 79fad5b803e22798bcb087066234a954d0ccdc60

Document that the PATTERN argument to gdb_test is optional.

2015-12-25  Sandra Loosemore  <sandra@codesourcery.com>

	gdb/testsuite/
	* lib/gdb.exp (gdb_test): Update comments to clarify that the
	PATTERN argument is optional.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] sim: standardize sim_create_inferior handling of argv a bit more
@ 2015-12-26 12:29 sergiodj+buildbot
  2015-12-26 13:09 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-26 12:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0e9672991e9346d5c2cb9cd33e30fb3e573f88b8 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 0e9672991e9346d5c2cb9cd33e30fb3e573f88b8

sim: standardize sim_create_inferior handling of argv a bit more

For targets that process argv in sim_create_inferior, improve the code:
- provide more details in the comment
- make the check for when to re-init more robust
- clean out legacy sim_copy_argv code

This will be cleaned up more in the future when we have a common inferior
creation function, but at least help new ports get it right until then.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] sim: cris: do not pass cpu when writing memory during init
@ 2015-12-26 13:41 sergiodj+buildbot
  2015-12-26 14:29 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-26 13:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8b494522f9f20e1e1d29089067d51fc141c33558 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 8b494522f9f20e1e1d29089067d51fc141c33558

sim: cris: do not pass cpu when writing memory during init

The point of passing down the cpu to core reads/writes is to signal which
cpu is making the access.  For system accesses (such as internal memory
initialization), passing the cpu down doesn't make sense, and in the case
of early init like cris, can cause crashes.  Since the cpu isn't fully set
up at this point, if the core code tries to access some fields (like the
PC reg), it'll crash.  While cris shouldn't be doing this setup here (it
should be in the inferior stage), we'll deal with that later.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] sim: sim-core: pass down cpu to hw accesses when available
@ 2015-12-26 19:56 sergiodj+buildbot
  2015-12-26 20:36 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-26 19:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT dea10706e9159ba6e94eab4c25010f3006d033a0 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: dea10706e9159ba6e94eab4c25010f3006d033a0

sim: sim-core: pass down cpu to hw accesses when available

The bfin port has been using the device callback largely so it could be
passed the cpu when available.  Add this logic to the common core code
so all ports get access to the active cpu.

The semantics of these buffer functions are changed slightly in that
errors halt the engine synchronously rather than returning the length
to the caller.  We'll probably adjust this in a follow up commit.

The bfin code isn't updated just yet as it has a bit more logic in the
device layer that needs to be unwound at which point we can delete it
entirely.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] sim: bfin: avoid stack error under asan
@ 2015-12-26 23:35 sergiodj+buildbot
  2015-12-27  0:07 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-26 23:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 236bf91febaa3a7b0c2231a8740968e90aa497c6 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 236bf91febaa3a7b0c2231a8740968e90aa497c6

sim: bfin: avoid stack error under asan

We set up an array of 3 elements and then index into it with a 2bit
value.  We check the range before we actually use the pointer, but
the indexing is enough to make asan upset, so just stuff a fourth
value in there to keep things simple.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] sim: bfin: push down mmr address/size checks
@ 2015-12-27  0:20 sergiodj+buildbot
  2015-12-27  1:25 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-27  0:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 466b619e95908dc073b78413f0d0d0b1cb97e4b5 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 466b619e95908dc073b78413f0d0d0b1cb97e4b5

sim: bfin: push down mmr address/size checks

The bfin port is using the WITH_DEVICES framework for two reasons:
- get access to the cpu making the request (if available)
- check the alignment & size for core & system MMRs

We addressed the first part with commit dea10706e9159ba6e94eab4c25010f3,
and we handle the second part with this commit.  Arguably this is more
correct too because trying to do bad reads/writes directly (when devices
support is disabled) often results in bad memory accesses.

As part of this clean up, we also adjust all of the existing logic that
would reject invalid accesses: the code was relying on the checks never
returning, but that's not the case when things like gdb (via the user's
commands) are making the requests.  Thus we'd still end up with bad mem
accesses, or sometimes gdb being hung due to while(1) loops.

Now we can connect (most of) these models into any address and have them
work correctly.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] sim: punt WITH_DEVICES & tconfig.h support
@ 2015-12-27  1:50 sergiodj+buildbot
  2015-12-27  3:12 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-27  1:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1b393626cef48974502e7077b191555b56680ee6 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 1b393626cef48974502e7077b191555b56680ee6

sim: punt WITH_DEVICES & tconfig.h support

No arch is using this anymore, and we want all new ports using the
hardware framework instead.  Punt WITH_DEVICES and the two callbacks
device_io_{read,write}_buffer.

We can also punt the tconfig.h file as no port is using it anymore.
This fixes in-tree builds that get confused by picking up the wrong
one (common/ vs <port>/) caused by commit ae7d0cac8ce971f7108d270c.

Any port that needs to set up a global define can use their own
sim-main.h file that they must provide regardless.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] sim: unify sim-hload
@ 2015-12-27  6:09 sergiodj+buildbot
  2015-12-27  6:41 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-27  6:09 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5e744ef887c1e879052cb30783638807190275f8 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 5e744ef887c1e879052cb30783638807190275f8

sim: unify sim-hload

Pretty much all targets are using this module already, so add it to the
common list of objects.  The only oddball out here is cris and that's
because it supports loading via an offset for all the phdrs.  We drop
support for that.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] sim: aarch64/msp430: fix disassembler usage
@ 2015-12-27  6:56 sergiodj+buildbot
  2015-12-27  7:39 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-27  6:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5d01527536684c75235f2ed288b11d253572b570 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 5d01527536684c75235f2ed288b11d253572b570

sim: aarch64/msp430: fix disassembler usage

The disasm framework reserves the private_data field for the disassemblers
themselves, not for people who use the disassembler.  Instead, there is an
application_data field for callers such as the sim.  Switch to it to avoid
random corruption/crashes when the disassemblers use private_data.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Correct nios2 _gp address computation.
@ 2015-12-27 20:41 sergiodj+buildbot
  2015-12-27 21:14 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-27 20:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a7be2893a6449e64fe6cfcdd8700b0a367a69f19 ***

Author: Sandra Loosemore <sandra@codesourcery.com>
Branch: master
Commit: a7be2893a6449e64fe6cfcdd8700b0a367a69f19

Correct nios2 _gp address computation.

2015-12-27  Sandra Loosemore  <sandra@codesourcery.com>

	bfd/
	* elf32-nios2.c (nios2_elf_assign_gp): Correct computation of _gp
	address.
	(nios2_elf32_relocate_section): Tidy code for R_NIOS2_GPREL error
	messages.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] sim: h8300: drop unused inst.h
@ 2015-12-30  8:41 sergiodj+buildbot
  2015-12-30  9:11 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-30  8:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f2089a69c164c789bcfd06b5eb9e0878f5520e13 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: f2089a69c164c789bcfd06b5eb9e0878f5520e13

sim: h8300: drop unused inst.h

We can also drop the compile.o rule since the common dep generation
logic takes care of this for us.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] sim: simplify STATE_MY_NAME setup
@ 2015-12-30  9:52 sergiodj+buildbot
  2015-12-30 12:10 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-30  9:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9950eccba15155dda9ef8025a5a1685dd9db53b7 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 9950eccba15155dda9ef8025a5a1685dd9db53b7

sim: simplify STATE_MY_NAME setup

No point in writing basename ourselves when libiberty provides one.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] sim: h8300: move default endian/alignment to configure
@ 2015-12-30 10:32 sergiodj+buildbot
  2015-12-30 13:12 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-30 10:32 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5658c2571f34fcf7f0f10dbd45ddc6680aa57576 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 5658c2571f34fcf7f0f10dbd45ddc6680aa57576

sim: h8300: move default endian/alignment to configure


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] sim: h8300: switch to common sim-resume
@ 2015-12-30 10:40 sergiodj+buildbot
  2015-12-30 14:16 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-30 10:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4ca9d09e826e959f382ab45b2e1dfa8125135124 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 4ca9d09e826e959f382ab45b2e1dfa8125135124

sim: h8300: switch to common sim-resume


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] sim: h8300: simplify h8300_reg_{fetch,store} funcs
@ 2015-12-30 11:14 sergiodj+buildbot
  2015-12-30 15:11 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-30 11:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2a2757ac7e849aa35fc519ddfcc8688a46b60448 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 2a2757ac7e849aa35fc519ddfcc8688a46b60448

sim: h8300: simplify h8300_reg_{fetch,store} funcs

We can leverage the cpu->regs array rather than going through the
function helpers to get nice compact code.

Further, fix up the return values: return -1 when we can't find a
register (and let the caller write out warnings), return 2/4 when
we actually write out that amount, and handle the zero reg.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] sim: h8300: inline sim_state_initialize
@ 2015-12-30 11:24 sergiodj+buildbot
  2015-12-30 16:10 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-30 11:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cec99e6b2c28d3d32d770ad645c4b0c26f2e1685 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: cec99e6b2c28d3d32d770ad645c4b0c26f2e1685

sim: h8300: inline sim_state_initialize

All the state is handled already by the common cpu allocation which
zeros out the entire state.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] sim: m68hc11: fix default endian
@ 2015-12-31  4:59 sergiodj+buildbot
  2015-12-31  5:30 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-31  4:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8e26d677a240d3b495b7c565006d75646a15ed53 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 8e26d677a240d3b495b7c565006d75646a15ed53

sim: m68hc11: fix default endian

The previous commit here set the default to little instead of big.
A typo lost when reviewing the different targets in parallel.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] opcodes/arc: Support dmb instruction with no operands
@ 2015-12-31 22:08 sergiodj+buildbot
  2015-12-31 22:40 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2015-12-31 22:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5ba8bc973cca60cb06bf41a2808ba6fa4ed02879 ***

Author: Andrew Burgess <andrew.burgess@embecosm.com>
Branch: master
Commit: 5ba8bc973cca60cb06bf41a2808ba6fa4ed02879

opcodes/arc: Support dmb instruction with no operands

In this GCC commit:
  https://gcc.gnu.org/ml/gcc-patches/2015-12/msg00735.html
GCC started emitting dmb instructions with no operands.  The intention
was that dmb with no operands should be an alias for 'dmb 0'.

The following patch extends the arc opcodes library to support dmb with
no operands.

opcodes/ChangeLog:

	* arc-tbl.h (dmb): Add a no operand version of dmb.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Rotate the GDB ChangeLog
@ 2016-01-01  4:32 sergiodj+buildbot
  2016-01-01  5:01 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-01  4:32 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0f7b3ef4dc9e4abf0bd85bb759f620c6302dfacf ***

Author: Joel Brobecker <brobecker@adacore.com>
Branch: master
Commit: 0f7b3ef4dc9e4abf0bd85bb759f620c6302dfacf

Rotate the GDB ChangeLog

Per GDB the "Start of New Year Procedure", this patch
  - renames the current ChangeLog into ChangeLog-2015;
  - starts a new ChangeLog file.

gdb/ChangeLog:

        * config/djgpp/fnchange.lst: Add entry for gdb/ChangeLog-2015.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] update copyright year printed by GDB, GDBserver and gdbreplay.
@ 2016-01-01  4:41 sergiodj+buildbot
  2016-01-01  6:01 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-01  4:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT edd88788349db3bd2af5fc9a38e2ea9cc220757f ***

Author: Joel Brobecker <brobecker@adacore.com>
Branch: master
Commit: edd88788349db3bd2af5fc9a38e2ea9cc220757f

update copyright year printed by GDB, GDBserver and gdbreplay.

gdb/ChangeLog:

        * top.c (print_gdb_version): Change copyright year in version
        message.

gdb/gdbserver/ChangeLog:

        * gdbreplay.c (gdbreplay_version): Change copyright year in
        version message.
        * server.c (gdbserver_version): Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] GDB copyright headers update after running GDB's copyright.py script.
@ 2016-01-01  4:56 sergiodj+buildbot
  2016-01-01  7:01 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-01  4:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 618f726fcb851883a0094aa7fa17003889b7189f ***

Author: Joel Brobecker <brobecker@adacore.com>
Branch: master
Commit: 618f726fcb851883a0094aa7fa17003889b7189f

GDB copyright headers update after running GDB's copyright.py script.

gdb/ChangeLog:

        Update year range in copyright notice of all files.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Copyright update for binutils
@ 2016-01-01 12:44 sergiodj+buildbot
  2016-01-01 13:14 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-01 12:44 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6f2750feaf2827ef8a1a0a5b2f90c1e9a6cabbd1 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 6f2750feaf2827ef8a1a0a5b2f90c1e9a6cabbd1

Copyright update for binutils


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] gdb: ppc: drop unnecessary sim file check
@ 2016-01-02  8:58 sergiodj+buildbot
  2016-01-02 10:18 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-02  8:58 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 32273fe68f3d1288b2eef6b96beda3732d0ac25e ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 32273fe68f3d1288b2eef6b96beda3732d0ac25e

gdb: ppc: drop unnecessary sim file check

We don't do this for other ppc targets in this file (we assume the sim
subdir exists), and it has existed for over a decade at this point.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] sim: delete dead current_state globals
@ 2016-01-02 15:38 sergiodj+buildbot
  2016-01-02 16:06 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-02 15:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d47f5b30d8481272e9480118bdcb283690070349 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: d47f5b30d8481272e9480118bdcb283690070349

sim: delete dead current_state globals

The global current_state handle to the current simulator state is a
design idea that was half implemented, but never really cleaned up.
The point was to have a global variable pointing to the state so that
funcs could more quickly & easily access the state anywhere.  We've
instead moved in the direction of passing state around everywhere and
don't have any intention of moving back.

I also can't find any references to gdb using this variable, or to
cgen related "dump_regs" functions, both of which were used in the
comments related to this code.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] sim: iq2000/m32r/lm32/sh64: delete dead option code
@ 2016-01-02 16:02 sergiodj+buildbot
  2016-01-02 17:05 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-02 16:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 027e73b217ec5ed334015b5484ff8d281258b6bb ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 027e73b217ec5ed334015b5484ff8d281258b6bb

sim: iq2000/m32r/lm32/sh64: delete dead option code

The iq2000/m32r/sh64 option parsing logic appears to have always been
dead.  At least iq2000/sh64 are simply copy & paste rot from m32r.

The lm32 option parsing hack here hasn't been needed for a while -- this
was fixed back in commit 11409fac6b95d71a92848a4499b02d60a4f4c5bb in the
common code.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] sim: cris: use standard output helpers
@ 2016-01-02 19:11 sergiodj+buildbot
  2016-01-02 19:39 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-02 19:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b3fbb288afd9071523b61b3222869cfed0f95ab8 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: b3fbb288afd9071523b61b3222869cfed0f95ab8

sim: cris: use standard output helpers

The sim-io module provides output helpers, so no need to define local
ones anymore.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] sim: convert to bfd_endian
@ 2016-01-03  5:29 sergiodj+buildbot
  2016-01-03  5:57 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-03  5:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1ac72f0659d64d6a14da862242db0d841d2878d0 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 1ac72f0659d64d6a14da862242db0d841d2878d0

sim: convert to bfd_endian

Rather than re-invent endian defines, as well as maintain our own list
of OS & arch-specific includes, punt all that logic in favor of the bfd
ones already set up and maintained elsewhere.  We already rely on the
bfd library, so leveraging the endian aspect should be fine.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] sim: drop host endian configure option
@ 2016-01-03  6:05 sergiodj+buildbot
  2016-01-03  6:58 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-03  6:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0cb8d8513cf44a102953ff5cf93e9dd399f42e9a ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 0cb8d8513cf44a102953ff5cf93e9dd399f42e9a

sim: drop host endian configure option

The --enable-sim-hostendian flag was purely so people had an escape route
for when cross-compiling.  This is because historically, AC_C_BIGENDIAN
did not work in those cases.  That was fixed a while ago though, so we can
require that macro everywhere now and simplify a good bit of code.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] sim: nrun: use lbasename
@ 2016-01-03  9:17 sergiodj+buildbot
  2016-01-03  9:45 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-03  9:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT aba6f46b235a3a139c04d5ed6a3310125aa9c982 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: aba6f46b235a3a139c04d5ed6a3310125aa9c982

sim: nrun: use lbasename


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] sim: clean up some more device detritus
@ 2016-01-03  9:56 sergiodj+buildbot
  2016-01-03 11:43 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-03  9:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 61971b86bb897dc333fccffb7518056c83b99f45 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 61971b86bb897dc333fccffb7518056c83b99f45

sim: clean up some more device detritus

Clean up some more remains of WITH_DEVICES that escaped notice.

We also clean up GETTWI/SETTWI defines in a few ports where they
were copied & pasted and are unused as they happen to be near the
device code.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] btrace: do not return out of TRY/CATCH
@ 2016-01-04  8:52 sergiodj+buildbot
  2016-01-04  9:21 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-04  8:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 43368e1d9ab8437079001f7a5f6ae2241acaece3 ***

Author: Markus Metzger <markus.t.metzger@intel.com>
Branch: master
Commit: 43368e1d9ab8437079001f7a5f6ae2241acaece3

btrace: do not return out of TRY/CATCH

In btrace_pt_readmem_callback, we read memory inside TRY/CATCH and return in
case of an error return value.  This corrupts the cleanup chain, which
eventually results in a SEGV when doing or discarding cleanups later on.

gdb/
	* btrace.c (btrace_pt_readmem_callback): Do not return in TRY/CATCH.

testsuite/
	* gdb.btrace/dlopen.exp: New.
	* gdb.btrace/dlopen.c: New.
	* gdb.btrace/dlopen-dso.c: New.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] sim: d10v: gut endian logic
@ 2016-01-04 10:17 sergiodj+buildbot
  2016-01-04 10:45 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-04 10:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 13adda68c54abf2654d01fa6523c379a13e418da ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 13adda68c54abf2654d01fa6523c379a13e418da

sim: d10v: gut endian logic

The compiler should produce reasonable code here in general, so punt the
various arch checks and bswap defines.  This code will eventually go away
entirely when we convert it to the common memory code.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] sim: punt x86-specific bswap logic
@ 2016-01-04 10:45 sergiodj+buildbot
  2016-01-04 11:45 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-04 10:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9bbf6f91c6e85ca916ec2c266009167f20f5ecfd ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 9bbf6f91c6e85ca916ec2c266009167f20f5ecfd

sim: punt x86-specific bswap logic

The compiler/C library should produce reasonable code for htonl/ntohl,
and at least glibc tries pretty hard to always produce good code for
them.  This logic only had support for 32-bit x86 systems anymore, and
it's unlikely people were even opting into this, so drop it all.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] sim: parse_args: polish getopt error message
@ 2016-01-04 11:04 sergiodj+buildbot
  2016-01-04 12:44 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-04 11:04 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8d7d784e23b5b2f8c7e28ece1bdb73b58199f16f ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 8d7d784e23b5b2f8c7e28ece1bdb73b58199f16f

sim: parse_args: polish getopt error message

The cris sim hit a few failures after the recent getopt logic, and the
expected output showed a few ways we can improve things to better match
other utils.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] sim: msp430: switch to common disassembler tracing
@ 2016-01-05 20:31 sergiodj+buildbot
  2016-01-05 21:16 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-05 20:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 70d394483206f5afe911fa21c8456b852c12da74 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 70d394483206f5afe911fa21c8456b852c12da74

sim: msp430: switch to common disassembler tracing

The output format is a bit different, but the new form matches all the
other trace lines.  Otherwise, it should be functionally equivalent.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] sim: bfin: add support disasm tracing
@ 2016-01-05 20:39 sergiodj+buildbot
  2016-01-05 22:15 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-05 20:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 824c862804128f6d31ae5f80fb741d12419da943 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 824c862804128f6d31ae5f80fb741d12419da943

sim: bfin: add support disasm tracing


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] sim: aarch64: switch to common disassembler tracing
@ 2016-01-05 21:02 sergiodj+buildbot
  2016-01-05 23:14 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-05 21:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1a846c62626357f9e966ef50917dca3a357c9644 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 1a846c62626357f9e966ef50917dca3a357c9644

sim: aarch64: switch to common disassembler tracing

The output should largely be the same.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] gdb: score: drop sim file check
@ 2016-01-05 22:13 sergiodj+buildbot
  2016-01-06  1:15 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-05 22:13 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6675033211e145ecd094b6803ed4a3427b3fd21e ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 6675033211e145ecd094b6803ed4a3427b3fd21e

gdb: score: drop sim file check

There has never been a GNU/sim port for the S+Core architecture.
It was added to support private code that has (and most likely
never will) see the light of day [1].  Punt this as we don't do
this for other people.  If you want to maintain a proprietary
internal build, then that's not really our problem.

[1] https://sourceware.org/ml/gdb-patches/2009-03/msg00390.html


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] libiberty: fix warnings about left shifting a negative value.
@ 2016-01-05 22:21 sergiodj+buildbot
  2016-01-06  2:34 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-05 22:21 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 13b356b2b5c1857490b7911dbbb48e17a3a92b04 ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: 13b356b2b5c1857490b7911dbbb48e17a3a92b04

libiberty: fix warnings about left shifting a negative value.

  GCC PR 66827 reports some problems with left shifting a negative
  value:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66827

  Of the problems reported only two remain - in libiberty/regex.c:

libiberty/regex.c:6970:11: runtime error: left shift of negative value -1
libiberty/regex.c:7165:4: runtime error: left shift of negative value -1

  The patch below fixes these errors by casting the value to be shifted
  to unsigned before the shift occurs.

  No regressions were found in the libiberty testsuite or bootstrapping
  gcc (on an x86_64 target).


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] libiberty: Tweak the documentation of libiberty's xcrc32 function
@ 2016-01-05 22:29 sergiodj+buildbot
  2016-01-06  3:33 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-05 22:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4bec0ef03e91506caf60d8842786b29c2d2ff049 ***

Author: Patrick Palka <patrick@parcs.ath.cx>
Branch: master
Commit: 4bec0ef03e91506caf60d8842786b29c2d2ff049

libiberty: Tweak the documentation of libiberty's xcrc32 function

In some places the xcrc32 documentation refers to GDB's own crc32
implementation, but GDB no longer has its own crc32 implementation.
It now uses libiberty's xcrc32 throughout.  So this patch removes
these references to GDB's now-nonexistent crc32 implementation.

Also, there appears to be a bug in the table-generation program embedded
within the documentation.  When the variable "int i" is >= 128, the
computation "i << 24" shifts a one bit into the sign bit (assuming a
32-bit int), which is UB.  To avoid this UB, I think it is sufficient to
make the induction variables i and j have type unsigned int.  This bug
seems latent, however.  I ran the program before and after this change
and the table output is the same.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] libiberty: {count, dup, write}argv: constify argv input slightly
@ 2016-01-05 23:03 sergiodj+buildbot
  2016-01-06  5:33 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-05 23:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b36c1ccb1feb678f7279b4a8d66c0125d4295078 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: b36c1ccb1feb678f7279b4a8d66c0125d4295078

libiberty: {count,dup,write}argv: constify argv input slightly

Would be more useful if we could use "const char * const *", but there's
a long standing bug where gcc warns about incompatible pointers when you
try to pass in "char **".  We can at least constify the array itself as
gcc will not warn in that case.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] libiberty: dupargv: rewrite to use xstrdup
@ 2016-01-05 23:23 sergiodj+buildbot
  2016-01-06  4:33 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-05 23:23 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 203217665139943a4f0d1797b9a5f913b3acf184 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 203217665139943a4f0d1797b9a5f913b3acf184

libiberty: dupargv: rewrite to use xstrdup

This func is basically open coding the xstrdup function, so gut it
and use it directly.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] gdb: change version stamp to git
@ 2016-01-06  4:40 sergiodj+buildbot
  2016-01-06  6:32 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-06  4:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bf69ad5a189db1dca362723a3b0a7a1b545219a9 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: bf69ad5a189db1dca362723a3b0a7a1b545219a9

gdb: change version stamp to git


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Change copyright owner to FSF in sim/testsuite/sim/mips/hilo-hazard-4.s
@ 2016-01-06  5:52 sergiodj+buildbot
  2016-01-06  7:31 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-06  5:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 68477034727ad85aeed248ec995da746f7639e53 ***

Author: Joel Brobecker <brobecker@adacore.com>
Branch: master
Commit: 68477034727ad85aeed248ec995da746f7639e53

Change copyright owner to FSF in sim/testsuite/sim/mips/hilo-hazard-4.s

sim/testsuite/sim/mips/ChangeLog:

        * hilo-hazard-4.s: Change copyright ownder to FSF.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix gdb.python/py-infthread.exp test message typo
@ 2016-01-06 11:46 sergiodj+buildbot
  2016-01-06 12:15 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-06 11:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 79bc59cb349fdbb8d3fa81804eb121af3c340c22 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 79bc59cb349fdbb8d3fa81804eb121af3c340c22

Fix gdb.python/py-infthread.exp test message typo

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

	* gdb.python/py-infthread.exp: Fix typo.  Expect t0.num to be 1.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [ARM/AArch64] Fix -Werror=unused-const-variable warnings in GDBserver
@ 2016-01-06 15:10 sergiodj+buildbot
  2016-01-06 15:57 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-06 15:10 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b2ca446f682854c2b187178358b97174bf313fa7 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: b2ca446f682854c2b187178358b97174bf313fa7

[ARM/AArch64] Fix -Werror=unused-const-variable warnings in GDBserver

This patch fixes gcc warning when build ARM GDBserver and AArch64
GDBserver,

AArch64 GDBserver:

gdb/gdbserver/linux-aarch32-low.h:36:29: error: 'thumb2_breakpoint' defined but not used [-Werror=unused-const-variable]
 static const unsigned short thumb2_breakpoint[] = { 0xf7f0, 0xa000 };
                             ^
gdb/gdbserver/linux-aarch32-low.h:34:29: error: 'thumb_breakpoint' defined but not used [-Werror=unused-const-variable]
 static const unsigned short thumb_breakpoint = 0xde01;
                             ^
gdb/gdbserver/linux-aarch32-low.h:28:28: error: 'arm_breakpoint' defined but not used [-Werror=unused-const-variable]
 static const unsigned long arm_breakpoint = arm_eabi_breakpoint;
                            ^
cc1: all warnings being treated as errors

ARM GDBserver:

gdb/gdbserver/linux-aarch32-low.h:34:29: error: 'thumb_breakpoint' defined but not used [-Werror=unused-const-variable]
 static const unsigned short thumb_breakpoint = 0xde01;
                             ^~~~~~~~~~~~~~~~

gdb/gdbserver/linux-aarch32-low.h:28:28: error: 'arm_breakpoint' defined but not used [-Werror=unused-const-variable]
 static const unsigned long arm_breakpoint = arm_eabi_breakpoint;
                            ^~~~~~~~~~~~~~

by simply moving these macros and variables to
linux-aarch32-low.c and only declare thumb2_breakpoint in
linux-aarch32-low.h, which is not perfect, and reveals some issues
in recent arm GDBserver software single step changes.  I'll post
follow-up patches.

gdb/gdbserver:

2016-01-06  Yao Qi  <yao.qi@linaro.org>

	* linux-aarch32-low.h (arm_abi_breakpoint): Move to
	linux-aarch32-low.c.
	(arm_eabi_breakpoint, arm_breakpoint): Likewise.
	(arm_breakpoint_len, thumb_breakpoint_len): Likewise.
	(thumb2_breakpoint, thumb2_breakpoint_len): Likewise.
	(thumb2_breakpoint): Declare.
	* linux-aarch32-low.c (arm_abi_breakpoint): Moved from
	linux-aarch32-low.h.
	(arm_eabi_breakpoint, arm_breakpoint): Likewise.
	(arm_breakpoint_len, thumb_breakpoint_len): Likewise.
	(thumb2_breakpoint, thumb2_breakpoint_len): Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Make {arm,thumb}_get_next_pcs_raw static
@ 2016-01-06 15:34 sergiodj+buildbot
  2016-01-06 16:59 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-06 15:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f5aa306929127aacf9890a949f9a21b38a0e0e7e ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: f5aa306929127aacf9890a949f9a21b38a0e0e7e

Make {arm,thumb}_get_next_pcs_raw static

This patch makes arm_get_next_pcs_raw and thumb_get_next_pcs_raw
static.

gdb:

2016-01-06  Yao Qi  <yao.qi@linaro.org>

	* arch/arm-get-next-pcs.c (arm_get_next_pcs): Move it to some
	lines below.
	(thumb_get_next_pcs_raw): Make it static.
	(arm_get_next_pcs_raw): Likewise.
	* arch/arm-get-next-pcs.h (thumb_get_next_pcs_raw): Remove the
	declaration.
	(arm_get_next_pcs_raw): Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] MIPS/include: opcode/mips.h: Add a summary of MIPS16 operand codes
@ 2016-01-06 18:52 sergiodj+buildbot
  2016-01-06 19:21 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-06 18:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b31e4803316aa0635a6f9beaeceea3e18dbbe459 ***

Author: Maciej W. Rozycki <macro@imgtec.com>
Branch: master
Commit: b31e4803316aa0635a6f9beaeceea3e18dbbe459

MIPS/include: opcode/mips.h: Add a summary of MIPS16 operand codes

	include/
	* opcode/mips.h: Add a summary of MIPS16 operand codes.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] sim: sim_{create_inferior, open, parse_args}: constify argv/env slightly
@ 2016-01-07  2:58 sergiodj+buildbot
  2016-01-07  3:27 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-07  2:58 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2e3d4f4d5d386995e99d035354a9e411d1dc0331 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 2e3d4f4d5d386995e99d035354a9e411d1dc0331

sim: sim_{create_inferior,open,parse_args}: constify argv/env slightly

2016-01-03  Mike Frysinger  <vapier@gentoo.org>

	* sim-options.c (sim_parse_args): Mark argv array const.
	* sim-options.h (sim_parse_args): Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] MIPS: Complete `status' to `err' renaming in `mips_breakpoint_from_pc'
@ 2016-01-07 19:37 sergiodj+buildbot
  2016-01-07 20:06 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-07 19:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5dd0563088b3ca9f5fd66daa0ffe823b60e4b92e ***

Author: Maciej W. Rozycki <macro@imgtec.com>
Branch: master
Commit: 5dd0563088b3ca9f5fd66daa0ffe823b60e4b92e

MIPS: Complete `status' to `err' renaming in `mips_breakpoint_from_pc'

Complement commit d09f2c3f [target_read_memory&co: no longer return
target_xfer_status] and apply the same change made to the big-endian leg
of the function to the little-endian leg as well.

	gdb/
	* mips-tdep.c (mips_breakpoint_from_pc): Rename local `status'
	to `err' in the little-endian leg.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [ARM] PR ld/19368: Add missing relocation type class for R_ARM_IRELATIVE
@ 2016-01-08  9:58 sergiodj+buildbot
  2016-01-08 10:27 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-08  9:58 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 109575d7ebac21a0eb67980001ecd4173d696f88 ***

Author: Jiong Wang <jiong.wang@arm.com>
Branch: master
Commit: 109575d7ebac21a0eb67980001ecd4173d696f88

[ARM] PR ld/19368: Add missing relocation type class for R_ARM_IRELATIVE

2016-01-08  Richard Sandiford  <richard.sandiford@arm.com>
	    Jiong Wang  <jiong.wang@arm.com>

	PR ld/19368
	bfd/
	* elf32-arm.c (elf32_arm_reloc_type_class): Map R_ARM_IRELATIVE to
	reloc_class_ifunc.

	ld/
	* testsuite/ld-arm/ifunc-3.rd: Update expected result.
	* testsuite/ld-arm/ifunc-4.rd: Likewise.
	* testsuite/ld-arm/ifunc-9.rd: Likewise.
	* testsuite/ld-arm/ifunc-10.rd: Likewise.
	* testsuite/ld-arm/ifunc-12.rd: Likewise.
	* testsuite/ld-arm/ifunc-13.rd: Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] m68k: fix constraints of move.[bw] for ISA_B/C
@ 2016-01-08 10:52 sergiodj+buildbot
  2016-01-08 11:28 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-08 10:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 83c3256ef5afe10625fd55dda2df5fc56b9b7393 ***

Author: Andreas Schwab <schwab@linux-m68k.org>
Branch: master
Commit: 83c3256ef5afe10625fd55dda2df5fc56b9b7393

m68k: fix constraints of move.[bw] for ISA_B/C

For ISA_B/C only the combination #,d(An) is allowed in addition to the
ISA_A combinations for move.b and move.w (and pc-relative is never
allowed as destination).

opcodes/
	PR gas/13050
	* m68k-opc.c (moveb, movew): For ISA_B/C only allow #,d(An) in
	addition to ISA_A.

gas/
	PR gas/13050
	* testsuite/gas/m68k/all.exp: Add tests p13050-1 and p13050-2.
	* testsuite/gas/m68k/p13050-1.s: New file.
	* testsuite/gas/m68k/p13050-2.d: New file.
	* testsuite/gas/m68k/p13050-2.s: New file.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Check input interrupt first when reading packet
@ 2016-01-08 11:16 sergiodj+buildbot
  2016-01-08 12:30 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-08 11:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5a0dd67a459338efb77f8d82bb3650d801ff0dd5 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 5a0dd67a459338efb77f8d82bb3650d801ff0dd5

Check input interrupt first when reading packet

Hi,
I see timeout in one of several runs of random-signal.exp like this,

 $ (set -e; while true; do make check RUNTESTFLAGS="--target_board=native-gdbserver random-signal.exp"; done)

In about every five runs, we can see a fail,

PASS: gdb.base/random-signal.exp: continue
^CFAIL: gdb.base/random-signal.exp: stop with control-c (timeout)

after some investigation, I find '\003' may be discarded by GDBserver when
it is expecting '$'.  In GDB side, both normal packets and '\003' are sent
via function send, but GDBserver may receive them at any time, that is to
say, in the receive buffer in GDBserver, '\003' may appear before or after
normal packet.  However, current GDBserver doesn't handle this case.

With this patch applied, I don't see this fail in multiple runs.
Although there is still timeout fail, that is a different problem, the
next patch will fix it.

gdb/gdbserver:

2016-01-08  Yao Qi  <yao.qi@linaro.org>

	* remote-utils.c (getpkt): If c is '\003', call target hook
	request_interrupt.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Change SIGINT handler for extension languages only when target terminal is ours
@ 2016-01-08 11:25 sergiodj+buildbot
  2016-01-08 13:32 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-08 11:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2f99e8fc9cb84ca80cfca6c119f1f22bbfd2a314 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 2f99e8fc9cb84ca80cfca6c119f1f22bbfd2a314

Change SIGINT handler for extension languages only when target terminal is ours

I see a timeout in gdb.base/random-signal.exp,

 Continuing.^M
 PASS: gdb.base/random-signal.exp: continue
 ^CPython Exception <type 'exceptions.KeyboardInterrupt'> <type
 exceptions.KeyboardInterrupt'>: ^M
 FAIL: gdb.base/random-signal.exp: stop with control-c (timeout)

it can be reproduced by running random-signal.exp with native-gdbserver
in a loop, like this, and the fail will be shown in about 20 runs,

$ (set -e; while true; do make check RUNTESTFLAGS="--target_board=native-gdbserver random-signal.exp"; done)

In the test, the program is being single-stepped for software watchpoint,
and in each internal stop, python unwinder sniffer is used,

 #0  pyuw_sniffer (self=<optimised out>, this_frame=<optimised out>, cache_ptr=0xd554f8) at /home/yao/SourceCode/gnu/gdb/git/gdb/python/py-unwind.c:608
 #1  0x00000000006a10ae in frame_unwind_try_unwinder (this_frame=this_frame@entry=0xd554e0, this_cache=this_cache@entry=0xd554f8, unwinder=0xecd540)
     at /home/yao/SourceCode/gnu/gdb/git/gdb/frame-unwind.c:107
 #2  0x00000000006a143f in frame_unwind_find_by_frame (this_frame=this_frame@entry=0xd554e0, this_cache=this_cache@entry=0xd554f8)
     at /home/yao/SourceCode/gnu/gdb/git/gdb/frame-unwind.c:163
 #3  0x000000000069dc6b in compute_frame_id (fi=0xd554e0) at /home/yao/SourceCode/gnu/gdb/git/gdb/frame.c:454
 #4  get_prev_frame_if_no_cycle (this_frame=this_frame@entry=0xd55410) at /home/yao/SourceCode/gnu/gdb/git/gdb/frame.c:1781
 #5  0x000000000069fdb9 in get_prev_frame_always_1 (this_frame=0xd55410) at /home/yao/SourceCode/gnu/gdb/git/gdb/frame.c:1955
 #6  get_prev_frame_always (this_frame=this_frame@entry=0xd55410) at /home/yao/SourceCode/gnu/gdb/git/gdb/frame.c:1971
 #7  0x00000000006a04b1 in get_prev_frame (this_frame=this_frame@entry=0xd55410) at /home/yao/SourceCode/gnu/gdb/git/gdb/frame.c:2213

when GDB goes to python extension, or other language extension, the
SIGINT handler is changed, and is restored when GDB leaves extension
language.  GDB only stays in extension language for a very short period
in this case, but if ctrl-c is pressed at that moment, python extension
will handle the SIGINT, and exceptions.KeyboardInterrupt is shown.

Language extension is used in GDB side rather than inferior side,
so GDB should only change SIGINT handler for extension language when
the terminal is ours (not inferior's).  This is what this patch does.
With this patch applied, I run random-signal.exp in a loop for 18
hours, and no fail is shown.

gdb:

2016-01-08  Yao Qi  <yao.qi@linaro.org>

	* extension.c: Include target.h.
	(set_active_ext_lang): Only call install_gdb_sigint_handler,
	check_quit_flag, and set_quit_flag if target_terminal_is_ours
	returns false.
	(restore_active_ext_lang): Likewise.
	* target.c (target_terminal_is_ours): New function.
	* target.h (target_terminal_is_ours): Declare.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] perf testsuite: python 3 fixes
@ 2016-01-08 15:34 sergiodj+buildbot
  2016-01-08 16:03 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-08 15:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 582a1b0064b14cb12b18f48678876d32c59c11c8 ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: 582a1b0064b14cb12b18f48678876d32c59c11c8

perf testsuite: python 3 fixes

There are a few errors when trying to run the performance testsuite with
Python 3.  This commit fixes them.

In Python 2, it was possible to use relative imports (importing a module
relative to the current one).  In Python 3 it isn't.  So I use
absolute_import from the __future__ module, which allows Python 2 to
behave like Python 3, and use the Python 3 syntax.

In Python 3, dict.iterkeys doesn't exist anymore.  Using dict.keys is a
good compromise in this case.

gdb/testsuite/ChangeLog:

	* gdb.perf/lib/perftest/perftest.py: Change relative imports to
	absolute.
	(SingleStatisticTestResult.report): Use dict.keys instead of
	dict.iterkeys.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix gdb.multi/base.exp testsuite regression
@ 2016-01-08 19:16 sergiodj+buildbot
  2016-01-08 19:45 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-08 19:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6cfc1fcb515d1ecd8445905b4749b81b3ca69552 ***

Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Branch: master
Commit: 6cfc1fcb515d1ecd8445905b4749b81b3ca69552

Fix gdb.multi/base.exp testsuite regression

Regressed by:

commit 762f774785f4ef878ac4c831e1f4733dc957234d
Author: Pedro Alves <palves@redhat.com>
Date:   Thu Dec 10 16:21:06 2015 +0000
    Stop using nowarnings in gdb/testsuite/gdb.multi/

+gdb compile failed, gdb/testsuite/gdb.multi/hello.c: In function 'commonfun':
+gdb/testsuite/gdb.multi/hello.c:24:19: warning: implicit declaration of function 'bar' [-Wimplicit-function-declaration]
+ int commonfun() { bar(); } /* from hello */
+                   ^
+gdb/testsuite/gdb.multi/hello.c: At top level:
+gdb/testsuite/gdb.multi/hello.c:26:1: warning: return type defaults to 'int' [-Wimplicit-int]
+ bar()
+ ^
+gdb/testsuite/gdb.multi/hello.c:32:1: warning: return type defaults to 'int' [-Wimplicit-int]
+ hello(int x)
+ ^
+gdb/testsuite/gdb.multi/hello.c:38:1: warning: return type defaults to 'int' [-Wimplicit-int]
+ main()
+ ^
+UNTESTED: gdb.multi/base.exp: base.exp

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

	* gdb.multi/goodbye.c: Fix compilation warnings by adding return types
	and reordering the functions.
	* gdb.multi/hangout.c: Likewise.
	* gdb.multi/hello.c: Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] sim: drop common/cconfig.h in favor of a single config.h
@ 2016-01-09  9:01 sergiodj+buildbot
  2016-01-09  9:29 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-09  9:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 936df7568a0e47547285a0dd57b81643264fef38 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 936df7568a0e47547285a0dd57b81643264fef38

sim: drop common/cconfig.h in favor of a single config.h

The common subdir sets up a cconfig.h file to hold checks for the common
code.  In practice, most files still end up using config.h instead which
just leads to confusion.

Merge all the configure checks that went into cconfig.h into SIM_AC_COMMON
so we can drop the cconfig.h file altogether.  Now there is only a single
config.h file like normal.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] sim: stop configuring common subdir
@ 2016-01-09  9:24 sergiodj+buildbot
  2016-01-09 10:29 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-09  9:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5295724cdc94a09713b021728b02163dad128e9e ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 5295724cdc94a09713b021728b02163dad128e9e

sim: stop configuring common subdir

Now that cconfig.h doesn't exist, there's no need to build in the common
subdir anymore.  We leave the configure/Makefile files in there as there
is a helper for developers to generate the nltvals.def file.  Once that
gets cleaned up in the future though, we can drop the build logic too.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] sim: drop --enable-sim-cflags option
@ 2016-01-10  8:17 sergiodj+buildbot
  2016-01-10  8:46 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-10  8:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 22be3fbeaccf50e3c0f58d0f7e9f7ed77effeaab ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 22be3fbeaccf50e3c0f58d0f7e9f7ed77effeaab

sim: drop --enable-sim-cflags option

No other sub directory provides such a configuration option, so
drop it from the sim dir as well.  This cleans up a good bit of
code in the process.

If people want to use custom flags for just the sim, they can
still run configure+make by hand in the sim subdir and use the
normal CFLAGS settings.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] sim: drop --enable-sim-{regparm,stdcall} options
@ 2016-01-10  8:33 sergiodj+buildbot
  2016-01-10 10:02 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-10  8:33 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0dc73ef7c304e6ffc9ce43b2131c77553a74e1d4 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 0dc73ef7c304e6ffc9ce43b2131c77553a74e1d4

sim: drop --enable-sim-{regparm,stdcall} options

These options were never exposed for most sims (just the ppc one),
and they are really only useful on 32-bit x86 systems.  Considering
modern systems tend to be 64-bit x86_64 and how well modern compilers
are at optimizing code, these have outlived their usefulness.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] sim: drop targ-vals.def->nltvals.def indirection
@ 2016-01-10  9:12 sergiodj+buildbot
  2016-01-10 13:01 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-10  9:12 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 99d8e879938c947588332a9cc579d378ccc2a855 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 99d8e879938c947588332a9cc579d378ccc2a855

sim: drop targ-vals.def->nltvals.def indirection

We don't have alternative nltvals.def files, so always symlinking
the targ-vals.def file to it doesn't gain us anything.  It does
make the build more complicated though and a pain to convert to
something newer (like automake).  Drop the symlinking entirely.

In the future, we'll want to explode this file anyways into the
respective arch dirs so things can be selected dynamically at
runtime, so it's not like we'll be bringing this back.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] sim: allow the assert configure option everywhere
@ 2016-01-10 22:20 sergiodj+buildbot
  2016-01-10 22:51 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-10 22:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 35656e95217a20309c0a0f16bf0c89a49a549177 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 35656e95217a20309c0a0f16bf0c89a49a549177

sim: allow the assert configure option everywhere

Currently ports have to call SIM_AC_OPTION_ASSERT explicitly in order
to make the configure flag available, which none of them do.  There's
no real reason to not allow this flag for all ports, so move it to the
common sim macro.  This way we get standard behavior across all ports.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] sim: allow the environment configure option everywhere
@ 2016-01-10 22:28 sergiodj+buildbot
  2016-01-10 23:53 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-10 22:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 16f7876d71604f835aefe48f0bf230c028c05d99 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 16f7876d71604f835aefe48f0bf230c028c05d99

sim: allow the environment configure option everywhere

Currently ports have to call SIM_AC_OPTION_ENVIRONMENT explicitly in
order to make the configure flag available.  There's no real reason
to not allow this flag for all ports, so move it to the common sim
macro.  This way we get standard behavior across all ports too.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] sim: drop unused SIM_AC_OPTION_PACKAGES
@ 2016-01-10 23:15 sergiodj+buildbot
  2016-01-11  0:56 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-10 23:15 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e19418e02e25ae4c62eb95547220897fa6aaf2e0 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: e19418e02e25ae4c62eb95547220897fa6aaf2e0

sim: drop unused SIM_AC_OPTION_PACKAGES

This was imported from the ppc sim, but that was only used to control
a single file, and that is already governed by the hw models.  There's
no need to have a sep configure option here, especially since none of
the other sims are using it.  Even when the code is enabled, there's
no runtime overhead.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] sim: move many common settings from CPPFLAGS to config.h
@ 2016-01-11  0:08 sergiodj+buildbot
  2016-01-11  2:23 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-11  0:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ce39bd389039d99458950b072550ab52f0a07a34 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: ce39bd389039d99458950b072550ab52f0a07a34

sim: move many common settings from CPPFLAGS to config.h

Rather than stuffing the command line with a bunch of -D flags, start
moving things to config.h which is managed by autoheader.  This makes
the makefile a bit simpler and the build output tighter, and it makes
the migration to automake easier as there are fewer vars to juggle.

We'll want to move the other options out too, but it'll take more work.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Import changes made to files shared with the FSF GCC project.
@ 2016-01-11 11:18 sergiodj+buildbot
  2016-01-11 11:47 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-11 11:18 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4849dfd8f454b9c595e6ee7477f6b7b25c31a499 ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: 4849dfd8f454b9c595e6ee7477f6b7b25c31a499

Import changes made to files shared with the FSF GCC project.

	Import the following changes from the GCC mainline:

	2015-11-13  Tsvetkova Alexandra  <aleksandra.tsvetkova@intel.com>

	* configure.ac: Enable libmpx by default.
	* configure: Regenerated.

	2015-11-19  Martin Liska  <mliska@suse.cz>

	* .gitignore: Add .clang-format to ignored files.
	* Makefile.tpl: Add clang-format.
	* Makefile.in: Regenerate.

	2015-12-01  Andreas Tobler  <andreast@gcc.gnu.org>

	PR libffi/65726
	* Makefile.def (lang_env_dependencies): Make libffi depend
	on cxx.
	* Makefile.in: Regenerate.

	2015-12-02  Ian Lance Taylor  <iant@google.com>

	PR go/66147
	* Makefile.tpl (HOST_EXPORTS): Add XGCC_FLAGS_FOR_TARGET.
	* Makefile.in: Regenerate.

	2015-12-17  Nathan Sidwell  <nathan@acm.org>

	* config/isl.m4 (ISL_CHECK_VERSION): Add gmp libs.
	* configure: Regenerate.

	2015-12-17  Sebastian Pop  <s.pop@samsung.com>

	* Makefile.in: Replace ISL with isl.
	* Makefile.tpl: Same.
	* config/isl.m4: Same.
	* configure.ac: Same.
	* contrib/download_prerequisites: Same.
	* configure: Regenerate.

	2016-01-01  Ben Elliston  <bje@gnu.org>

	* config.guess: Import version 2016-01-01.
	* config.sub: Likewise.

include	2016-01-07  Mike Frysinger  <vapier@gentoo.org>

	* longlong.h: Change !__SHMEDIA__ to
	(!defined (__SHMEDIA__) || !__SHMEDIA__).
	Change __SHMEDIA__ to defined (__SHMEDIA__) && __SHMEDIA__.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Delete opcodes that have been removed from ISA 3.0.
@ 2016-01-11 18:06 sergiodj+buildbot
  2016-01-11 18:37 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-11 18:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT afa8d4054b8e0b1384f2d07f1c15163c0699d660 ***

Author: Peter Bergner <bergner@vnet.ibm.com>
Branch: master
Commit: afa8d4054b8e0b1384f2d07f1c15163c0699d660

Delete opcodes that have been removed from ISA 3.0.

opcodes/
	* ppc-opc.c <xscmpnedp>: Delete.
	<xvcmpnedp>: Likewise.
	<xvcmpnedp.>: Likewise.
	<xvcmpnesp>: Likewise.
	<xvcmpnesp.>: Likewise.

gas/
	* testsuite/gas/ppc/power9.d <xscmpnedp, xvcmpnedp, xvcmpnedp.,
	xvcmpnesp, xvcmpnesp.>: Delete tests.
	* testsuite/gas/ppc/power9.s: Likewise.
	* testsuite/gas/ppc/vsx3.d: Likewise.
	* testsuite/gas/ppc/vsx3.s: Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] gdb: split out warnings helpers
@ 2016-01-11 19:13 sergiodj+buildbot
  2016-01-11 19:50 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-11 19:13 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b835bb5265d614fd8a4759f284b987b365292c36 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: b835bb5265d614fd8a4759f284b987b365292c36

gdb: split out warnings helpers

This will allow the sim tree to use the same set of warnings.
The new code in warning.m4 is exactly the same (other than the
AC_DEFUN wrapping).


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] testsuite: Fix false FAILs on too long base directory
@ 2016-01-11 21:16 sergiodj+buildbot
  2016-01-11 21:53 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-11 21:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c0ecb95f3dc0c3e8d1545f0a37c0c3e537e1ea96 ***

Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Branch: master
Commit: c0ecb95f3dc0c3e8d1545f0a37c0c3e537e1ea96

testsuite: Fix false FAILs on too long base directory

I was getting

gu (print arg0)^M
= 0x7fffffffdafb
"/unsafebuild-x86_64-redhat-linux-gnu/gdb/testsuite.unix.-m64/outputs/gdb.guile/scm-value/scm-"...^M
(gdb) FAIL: gdb.guile/scm-value.exp: verify dereferenced value
python print (arg0)^M
0x7fffffffdafd
"/unsafebuild-x86_64-redhat-linux-gnu/gdb/testsuite.unix.-m64/outputs/gdb.python/py-value/py-v"...^M
(gdb) FAIL: gdb.python/py-value.exp: verify dereferenced value

and also:

(gdb) p argv[0]^M
$2 = 0x7fffffffd832 "/home/jkratoch/redhat/gdb-test-", 'x' <repeats 169
times>...^M
(gdb) FAIL: gdb.guile/scm-value.exp: argv[0] should be available on this
target

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

	* gdb.guile/scm-value.exp (test_value_in_inferior): Set print elements
	and repeats to unlimited.
	* gdb.python/py-value.exp: Likewise.
	* lib/gdb.exp (gdb_has_argv0): Save and temporarily set print elements
	and repeats to unlimited.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] testsuite: i386 regression for funcargs.exp
@ 2016-01-11 21:31 sergiodj+buildbot
  2016-01-11 23:53 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-11 21:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 01d8c27e4f77375c0e157d115266129b76ff6734 ***

Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Branch: master
Commit: 01d8c27e4f77375c0e157d115266129b76ff6734

testsuite: i386 regression for funcargs.exp

3ca22649a6dfeb71058c33be4d0542b98f1f0ff5 is the first bad commit
commit 3ca22649a6dfeb71058c33be4d0542b98f1f0ff5
Author: Simon Marchi <simon.marchi@polymtl.ca>
Date:   Mon Dec 21 12:51:54 2015 -0500
    Remove HP-UX references fom testsuite
@@ -1013,13 +1013,6 @@ proc localvars_in_indirect_call { } {
     #

     gdb_test_multiple "finish" "finish from indirectly called function" {
-       -re "\\(\\*pointer_to_call0a\\) \\(c, s, i, l\\);.*First.*$gdb_prompt $" {
-           #On hppa2.0w-hp-hpux11.00, gdb finishes at one line earlier than
-           #hppa1.1-hp-hpux11.00. Therefore, an extra "step" is necessary
-           #to continue the test.
-           send_gdb "step\n"
-           exp_continue
-	}
        -re ".*\\(\\*pointer_to_call0a\\) \\(c, s, i, l\\);.*Second.*$gdb_prompt $" {
            pass "finish from indirectly called function"
       	}

->

 finish^M
 Run till exit from #0  call0a (c=97 'a', s=1, i=2, l=3) at ./gdb.base/funcargs.c:82^M
 0x0804a189 in main () at ./gdb.base/funcargs.c:583^M
 583	  (*pointer_to_call0a) (c, s, i, l);    /* First step into call0a.  */^M
-(gdb) step^M
-584	  (*pointer_to_call0a) (c, s, i, l);    /* Second step into call0a.  */^M
-(gdb) PASS: gdb.base/funcargs.exp: finish from indirectly called function
+(gdb) FAIL: gdb.base/funcargs.exp: finish from indirectly called function
 step^M
-call0a (c=97 'a', s=1, i=2, l=3) at ./gdb.base/funcargs.c:82^M
-82	  c = 'a';^M
-(gdb) PASS: gdb.base/funcargs.exp: stepping into indirectly called function
+584	  (*pointer_to_call0a) (c, s, i, l);    /* Second step into call0a.  */^M
+(gdb) FAIL: gdb.base/funcargs.exp: stepping into indirectly called function

At least on x86_64 with testsuite in -m32 (expecting native i386 would be the
same).

Pedro Alves:

The difference is that with newer GCC there's an extra instruction
after the call which is still assigned to line 583:

$ diff -up /tmp/4.8.3 /tmp/6.0.0 -U 1000
--- /tmp/4.8.3  2016-01-11 12:37:39.611089156 +0000
+++ /tmp/6.0.0  2016-01-11 13:21:00.021127976 +0000
@@ -1,27 +1,30 @@
 583       (*pointer_to_call0a) (c, s, i, l);    /* First step into call0a.  */
    mov    0x804d060,%ebx
    mov    0x804d050,%ecx
    movzwl 0x804d040,%eax
    movswl %ax,%edx
    movzbl 0x804d030,%eax
    movsbl %al,%eax
-   mov    %ebx,0xc(%esp)
-   mov    %ecx,0x8(%esp)
-   mov    %edx,0x4(%esp)
-   mov    %eax,(%esp)
-   mov    0x7c(%esp),%eax
+   push   %ebx
+   push   %ecx
+   push   %edx
+   push   %eax
+   mov    -0x1c(%ebp),%eax
    call   *%eax
+   add    $0x10,%esp

 584	   (*pointer_to_call0a) (c, s, i, l);    /* Second step into call0a.  */
    mov    0x804d060,%ebx
    mov    0x804d050,%ecx
    movzwl 0x804d040,%eax
    movswl %ax,%edx
    movzbl 0x804d030,%eax
    movsbl %al,%eax
-   mov    %ebx,0xc(%esp)
-   mov    %ecx,0x8(%esp)
-   mov    %edx,0x4(%esp)
-   mov    %eax,(%esp)
-   mov    0x7c(%esp),%eax
+   push   %ebx
+   push   %ecx
+   push   %edx
+   push   %eax
+   mov    -0x1c(%ebp),%eax
    call   *%eax
+   add    $0x10,%esp
+

I don't know why -m32 changed to push/add instead of mov while 64-bit hasn't.

This is most likely needed on non-x86 ports as well.

gdb/testsuite/ChangeLog
2016-01-11  Jan Kratochvil  <jan.kratochvil@redhat.com>
	    Pedro Alves  <palves@redhat.com>

	* gdb.base/funcargs.exp (finish from indirectly called function):
	Reintroduce the case for 'First'.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Reapply: List inferiors/threads/pspaces in ascending order
@ 2016-01-12  1:37 sergiodj+buildbot
  2016-01-12  2:39 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-12  1:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b05b120205e697db6291abb95a8cd2be054f99e9 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: b05b120205e697db6291abb95a8cd2be054f99e9

Reapply: List inferiors/threads/pspaces in ascending order

[This reapplies a change that was accidentally reverted with c0ecb95f3d.]

Before:
  (gdb) info threads
    Id   Target Id         Frame
    3    Thread 0x7ffff77c3700 (LWP 29035) callme () at foo.c:30
    2    Thread 0x7ffff7fc4700 (LWP 29034) 0x000000000040087b in child_function_2 (arg=0x0) at foo.c:60
  * 1    Thread 0x7ffff7fc5740 (LWP 29030) 0x0000003b37209237 in pthread_join (threadid=140737353893632, thread_return=0x0) at pthread_join.c:92

After:
  (gdb) info threads
    Id   Target Id         Frame
  * 1    Thread 0x7ffff7fc5740 (LWP 29030) 0x0000003b37209237 in pthread_join (threadid=140737353893632, thread_return=0x0) at pthread_join.c:92
    2    Thread 0x7ffff7fc4700 (LWP 29034) 0x000000000040087b in child_function_2 (arg=0x0) at foo.c:60
    3    Thread 0x7ffff77c3700 (LWP 29035) callme () at foo.c:30

gdb/doc/ChangeLog:
2015-11-24  Pedro Alves  <palves@redhat.com>

	PR 17539
	* gdb.texinfo (Inferiors and Programs): Adjust "maint info
	program-spaces" example to ascending order listing.
	(Threads): Adjust "info threads" example to ascending order
	listing.
	(Forks): Adjust "info inferiors" example to ascending order
	listing.

gdb/ChangeLog:
2015-11-24  Pedro Alves  <palves@redhat.com>

	PR 17539
	* inferior.c (add_inferior_silent): Append the new inferior to the
	end of the list.
	* progspace.c (add_program_space): Append the new pspace to the
	end of the list.
	* thread.c (new_thread): Append the new thread to the end of the
	list.

gdb/testsuite/ChangeLog:
2015-11-24  Pedro Alves  <palves@redhat.com>

	PR 17539
	* gdb.base/foll-exec-mode.exp: Adjust to GDB listing inferiors and
	threads in ascending order.
	* gdb.base/foll-fork.exp: Likewise.
	* gdb.base/foll-vfork.exp: Likewise.
	* gdb.base/multi-forks.exp: Likewise.
	* gdb.mi/mi-nonstop.exp: Likewise.
	* gdb.mi/mi-nsintrall.exp: Likewise.
	* gdb.multi/base.exp: Likewise.
	* gdb.multi/multi-arch.exp: Likewise.
	* gdb.python/py-inferior.exp: Likewise.
	* gdb.threads/break-while-running.exp: Likewise.
	* gdb.threads/execl.exp: Likewise.
	* gdb.threads/gcore-thread.exp: Likewise.
	* gdb.threads/info-threads-cur-sal.exp: Likewise.
	* gdb.threads/kill.exp: Likewise.
	* gdb.threads/linux-dp.exp: Likewise.
	* gdb.threads/multiple-step-overs.exp: Likewise.
	* gdb.threads/next-bp-other-thread.exp: Likewise.
	* gdb.threads/step-bg-decr-pc-switch-thread.exp: Likewise.
	* gdb.threads/step-over-lands-on-breakpoint.exp: Likewise.
	* gdb.threads/step-over-trips-on-watchpoint.exp: Likewise.
	* gdb.threads/thread-find.exp: Likewise.
	* gdb.threads/tls.exp: Likewise.
	* lib/mi-support.exp (mi_reverse_list): Delete.
	(mi_check_thread_states): No longer reverse list.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] sim: mips: workaround 32-bit addr sign extensions
@ 2016-01-12  6:46 sergiodj+buildbot
  2016-01-12  7:22 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-12  6:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b36d953bced0a4fecdde1823abac70ed7038ee95 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: b36d953bced0a4fecdde1823abac70ed7038ee95

sim: mips: workaround 32-bit addr sign extensions

The mips bfd will sign extend 32-bit addresses into 64-bit values,
so if the entry happens to be 0x80000000 or higher, it is turned to
0xffffffff80000000 which points to memory that doesn't exist.

This wasn't an issue until commit 26f8bf63bf36f9062a5cc1afacf71462a
as all addresses were automatically truncated there in the translate
function to 32-bits.  When we cleaned up that code, the full 64-bits
were checked leading to many test failures for mips-sde-elf targets
and such.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Hurd: Make gdb/reply_mig_hack.awk script compatible to "mawk"
@ 2016-01-12 12:01 sergiodj+buildbot
  2016-01-12 12:39 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-12 12:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5eddd57823971bdb54f957d10c11ff3fc9f97b1e ***

Author: Thomas Schwinge <thomas@codesourcery.com>
Branch: master
Commit: 5eddd57823971bdb54f957d10c11ff3fc9f97b1e

Hurd: Make gdb/reply_mig_hack.awk script compatible to "mawk"

The "mawk" AWK implementation did't like that regular expression:

    mawk: [...]/gdb/reply_mig_hack.awk: line 98: regular expression compile failed (missing operand)

	gdb/
	* reply_mig_hack.awk: Rewrite one regular expression.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Test gdb.base/random-signal.exp with "attach"
@ 2016-01-12 13:13 sergiodj+buildbot
  2016-01-12 13:49 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-12 13:13 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e46eeeddfb308cacd863f11a433c10ff1d403827 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: e46eeeddfb308cacd863f11a433c10ff1d403827

Test gdb.base/random-signal.exp with "attach"

This exposes the issued fixed by 2f99e8fc9cb8:

  https://sourceware.org/ml/gdb-patches/2015-12/msg00423.html

to native debugging as well.

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

	* gdb.base/random-signal.exp (do_test): New procedure, with body
	of testcase moved in.
	(top level) Call it twice, once with "run" and once with "attach".


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Remove trademark acknowledgements throughout
@ 2016-01-12 15:09 sergiodj+buildbot
  2016-01-12 15:46 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-12 15:09 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bc504a311794145e7aef2011f31ea87aa64bea4c ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: bc504a311794145e7aef2011f31ea87aa64bea4c

Remove trademark acknowledgements throughout

The GNU Coding Standards say:

  "Please do not include any trademark acknowledgements in GNU
  software packages or documentation."

gdb/ChangeLog:
2016-01-12  Pedro Alves  <palves@redhat.com>

	Remove use of the registered trademark symbol throughout.

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

	Remove use of the registered trademark symbol throughout.

gdb/doc/ChangeLog:
2016-01-12  Pedro Alves  <palves@redhat.com>

	Remove use of the registered trademark symbol throughout.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Change function signature passed to clone
@ 2016-01-12 15:22 sergiodj+buildbot
  2016-01-12 16:46 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-12 15:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ba4dd7c4a1d99c62a1c2edd68f511a82f8fe041e ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: ba4dd7c4a1d99c62a1c2edd68f511a82f8fe041e

Change function signature passed to clone

I see the following compile error with an old bfin-uclinux gcc to
build GDBserver,

 cc1: warnings being treated as errors
 gdb/gdbserver/../nat/linux-ptrace.c: In function 'linux_fork_to_function':
 gdb/gdbserver/../nat/linux-ptrace.c:283: error: passing argument 1 of 'clone' from incompatible pointer type

in glibc, clone's prototype is like this, and in uClibc, it is the same,

       int clone(int (*fn)(void *), void *child_stack,
                 int flags, void *arg, ...
                 /* pid_t *ptid, struct user_desc *tls, pid_t *ctid */ );

so this patch changes function signature from 'void (*function) (gdb_byte *)'
to 'int (*function) (void *)'.

Note that I find Pedro advised to change argument type from 'void *'
to 'gdb_byte *' during the patch review
https://sourceware.org/ml/gdb-patches/2013-08/msg00611.html  however,
I think fix compile error can justify the change back to 'void *'.

gdb:

2016-01-12  Yao Qi  <yao.qi@linaro.org>

	* nat/linux-ptrace.c (linux_fork_to_function): Change type
	of argument 'function'.
	(linux_grandchild_function): Change return type to 'int'.
	Change child_stack's type to 'void *'.
	(linux_child_function): Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] gdbserver: fix various warnings
@ 2016-01-12 15:44 sergiodj+buildbot
  2016-01-12 17:47 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-12 15:44 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5b3da067f0893be637f9e992b409e36682ea081a ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 5b3da067f0893be637f9e992b409e36682ea081a

gdbserver: fix various warnings

Delete unused funcs, update old prototypes, and mark local funcs
as static.  This doesn't cover all missing prototype warnings.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] gdbserver: use the new gdb warning helpers
@ 2016-01-12 15:45 sergiodj+buildbot
  2016-01-12 18:47 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-12 15:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8f13a3ce8afc1144169a14c7704689e263316e70 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 8f13a3ce8afc1144169a14c7704689e263316e70

gdbserver: use the new gdb warning helpers

We need to use -Wno-missing-prototypes for now as much of the code
sticks externs in local files and not in common headers.

2016-01-11  Mike Frysinger  <vapier@gentoo.org>

	* acinclude.m4: Include new ../warning.m4 file.
	* configure: Regenerated.
	* configure.ac: Replace all warning logic with AM_GDB_WARNINGS.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix invalid conversion from void * to gdb_byte *
@ 2016-01-12 16:34 sergiodj+buildbot
  2016-01-12 19:47 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-12 16:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d18547d8b08615a58db18ad3e43f721dc92ae298 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: d18547d8b08615a58db18ad3e43f721dc92ae298

Fix invalid conversion from void * to gdb_byte *

This patch fixes the following GDB build error in C++ mode.

gdb/nat/linux-ptrace.c: In function 'int linux_child_function(void*)':
gdb/nat/linux-ptrace.c:323:65: error: invalid conversion from 'void*' to 'gdb_byte* {aka unsigned char*}' [-fpermissive]
   linux_fork_to_function (child_stack, linux_grandchild_function);
                                                                 ^

gdb:

2016-01-12  Yao Qi  <yao.qi@linaro.org>

	* nat/linux-ptrace.c (linux_child_function): Cast child_stack
	to gdb_byte * and pass to linux_fork_to_function.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Sync top-level Makefile.def with GCC
@ 2016-01-12 16:37 sergiodj+buildbot
  2016-01-12 20:48 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-12 16:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ce5e165eae8925f64da52172f3e67ad8010a1aa0 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: ce5e165eae8925f64da52172f3e67ad8010a1aa0

Sync top-level Makefile.def with GCC

2016-01-12  Bernd Edlinger  <bernd.edlinger@hotmail.de>

	PR bootstrap/69134
	* Makefile.def (mpfr): Disable assembler.
	* Makefile.in: Regenerate.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [ARM] Support ARMv8.2 RAS extension.
@ 2016-01-12 16:46 sergiodj+buildbot
  2016-01-12 22:49 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-12 16:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 105bde5771c1c1b26b69e3623c88f3caafa3a480 ***

Author: Matthew Wahab <matthew.wahab@arm.com>
Branch: master
Commit: 105bde5771c1c1b26b69e3623c88f3caafa3a480

[ARM] Support ARMv8.2 RAS extension.

The ARMv8.2 architecture includes the RAS extension which adds an
instruction, ESB, and a number of coprocessor registers. This patch adds
the instruction to binutils, making it available when -march=armv8.2-a
is selected. It also adds tests for the instruction and for the
coprocessor registers.

gas/
2016-01-12  Matthew Wahab  <matthew.wahab@arm.com>

	* config/tc-arm.c (arm_ext_v8_2): New.
	(insns): Add "esb".
	* testsuite/gas/arm/armv8_2-a.d: New.
	* testsuite/gas/arm/armv8_2-a.s: New.

opcodes/
2016-01-12  Matthew Wahab  <matthew.wahab@arm.com>

	* arm-dis.c (arm_opcodes): Add "esb".
	(thumb_opcodes): Likewise.

Change-Id: I67f3d70789db78d1c66a56c4994675f99ac15e34


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Sync top-level btool.m4 with GCC
@ 2016-01-12 16:49 sergiodj+buildbot
  2016-01-12 23:50 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-12 16:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1985dc2d048a4134f20dc9cda61255eb33289476 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 1985dc2d048a4134f20dc9cda61255eb33289476

Sync top-level btool.m4 with GCC

	Sync with GCC
	2015-11-26  David Edelsohn  <dje.gcc@gmail.com>

	* m4/libtool.m4 (export_symbols_cmds) [AIX]: Add global TLS "L"
	symbols.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Implement 'catch syscall' for gdbserver
@ 2016-01-12 20:34 sergiodj+buildbot
  2016-01-13  0:53 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-12 20:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 82075af2c14b1f8a54fa5796fb63f7ef23f98d9d ***

Author: Josh Stone <jistone@redhat.com>
Branch: master
Commit: 82075af2c14b1f8a54fa5796fb63f7ef23f98d9d

Implement 'catch syscall' for gdbserver

This adds a new QCatchSyscalls packet to enable 'catch syscall', and new
stop reasons "syscall_entry" and "syscall_return" for those events.  It
is currently only supported on Linux x86 and x86_64.

gdb/ChangeLog:

2016-01-12  Josh Stone  <jistone@redhat.com>
	    Philippe Waroquiers  <philippe.waroquiers@skynet.be>

	* NEWS (Changes since GDB 7.10): Mention QCatchSyscalls and the
	syscall_entry and syscall_return stop reasons.  Mention GDB
	support for remote catch syscall.
	* remote.c (PACKET_QCatchSyscalls): New enum.
	(remote_set_syscall_catchpoint): New function.
	(remote_protocol_features): New element for QCatchSyscalls.
	(remote_parse_stop_reply): Parse syscall_entry/return stops.
	(init_remote_ops): Install remote_set_syscall_catchpoint.
	(_initialize_remote): Config QCatchSyscalls.
	* linux-nat.h (struct lwp_info) <syscall_state>: Comment typo.

gdb/doc/ChangeLog:

2016-01-12  Josh Stone  <jistone@redhat.com>
	    Philippe Waroquiers  <philippe.waroquiers@skynet.be>

	* gdb.texinfo (Remote Configuration): List the QCatchSyscalls packet.
	(Stop Reply Packets): List the syscall entry and return stop reasons.
	(General Query Packets): Describe QCatchSyscalls, and add it to the
	table and the detailed list of stub features.

gdb/gdbserver/ChangeLog:

2016-01-12  Josh Stone  <jistone@redhat.com>
	    Philippe Waroquiers  <philippe.waroquiers@skynet.be>

	* inferiors.h: Include "gdb_vecs.h".
	(struct process_info): Add syscalls_to_catch.
	* inferiors.c (remove_process): Free syscalls_to_catch.
	* remote-utils.c (prepare_resume_reply): Report syscall_entry and
	syscall_return stops.
	* server.h (UNKNOWN_SYSCALL, ANY_SYSCALL): Define.
	* server.c (handle_general_set): Handle QCatchSyscalls.
	(handle_query): Report support for QCatchSyscalls.
	* target.h (struct target_ops): Add supports_catch_syscall.
	(target_supports_catch_syscall): New macro.
	* linux-low.h (struct linux_target_ops): Add get_syscall_trapinfo.
	(struct lwp_info): Add syscall_state.
	* linux-low.c (handle_extended_wait): Mark syscall_state as an entry.
	Maintain syscall_state and syscalls_to_catch across exec.
	(get_syscall_trapinfo): New function, proxy to the_low_target.
	(linux_low_ptrace_options): Enable PTRACE_O_TRACESYSGOOD.
	(linux_low_filter_event): Toggle syscall_state entry/return for
	syscall traps, and set it ignored for all others.
	(gdb_catching_syscalls_p): New function.
	(gdb_catch_this_syscall_p): New function.
	(linux_wait_1): Handle SYSCALL_SIGTRAP.
	(linux_resume_one_lwp_throw): Add PTRACE_SYSCALL possibility.
	(linux_supports_catch_syscall): New function.
	(linux_target_ops): Install it.
	* linux-x86-low.c (x86_get_syscall_trapinfo): New function.
	(the_low_target): Install it.

gdb/testsuite/ChangeLog:

2016-01-12  Josh Stone  <jistone@redhat.com>
	    Philippe Waroquiers  <philippe.waroquiers@skynet.be>

	* gdb.base/catch-syscall.c (do_execve): New variable.
	(main): Conditionally trigger an execve.
	* gdb.base/catch-syscall.exp: Enable testing for remote targets.
	(test_catch_syscall_execve): New, check entry/return across execve.
	(do_syscall_tests): Call test_catch_syscall_execve.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Add a new $_inferior convenience variable
@ 2016-01-13 11:35 sergiodj+buildbot
  2016-01-13 12:36 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-13 11:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e3940304fe75c91f99e260a89fe8c45ece7e373f ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: e3940304fe75c91f99e260a89fe8c45ece7e373f

Add a new $_inferior convenience variable

Like $_thread, but holds the current inferior number.

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

	* NEWS: Mention $_inferior.
	* inferior.c (inferior_id_make_value): New.
	(inferior_funcs): New.
	(_initialize_inferior): Create $_inferior variable.

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

	* gdb.base/default.exp: Expect $_inferior as well.
	* gdb.multi/base.exp: Test $_inferior.

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

	* gdb.texinfo (Inferiors and Programs): Document the $_inferior
	convenience variable.
	(Convenience Vars): Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Add Python InferiorThread.inferior attribute
@ 2016-01-13 11:36 sergiodj+buildbot
  2016-01-13 13:37 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-13 11:36 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8465445732dc04c3fb6cf954274e12d06b274f08 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 8465445732dc04c3fb6cf954274e12d06b274f08

Add Python InferiorThread.inferior attribute

So a script can easily get at a thread's inferior and its number.

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

	* NEWS: Mention InferiorThread.inferior.
	* python/py-infthread.c (thpy_get_inferior): New.
	(thread_object_getset): Register "inferior".

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

	* gdb.python/py-infthread.exp: Test InferiorThread.inferior.

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

	* python.texi (Threads In Python): Document
	InferiorThread.inferior.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Per-inferior/Inferior-qualified thread IDs
@ 2016-01-13 11:39 sergiodj+buildbot
  2016-01-13 15:37 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-13 11:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5d5658a1d3c3eb2a09c03f2f0662a1c01963c869 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 5d5658a1d3c3eb2a09c03f2f0662a1c01963c869

Per-inferior/Inferior-qualified thread IDs

This commit changes GDB to track thread numbers per-inferior.  Then,
if you're debugging multiple inferiors, GDB displays
"inferior-num.thread-num" instead of just "thread-num" whenever it
needs to display a thread:

 (gdb) info inferiors
   Num  Description       Executable
   1    process 6022     /home/pedro/gdb/tests/threads
 * 2    process 6037     /home/pedro/gdb/tests/threads
 (gdb) info threads
   Id   Target Id         Frame
   1.1  Thread 0x7ffff7fc2740 (LWP 6022) "threads" (running)
   1.2  Thread 0x7ffff77c0700 (LWP 6028) "threads" (running)
   1.3  Thread 0x7ffff7fc2740 (LWP 6032) "threads" (running)
   2.1  Thread 0x7ffff7fc1700 (LWP 6037) "threads" (running)
   2.2  Thread 0x7ffff77c0700 (LWP 6038) "threads" (running)
 * 2.3  Thread 0x7ffff7fc2740 (LWP 6039) "threads" (running)
 (gdb)
...
 (gdb) thread 1.1
 [Switching to thread 1.1 (Thread 0x7ffff7fc2740 (LWP 8155))]
 (gdb)
...

etc.

You can still use "thread NUM", in which case GDB infers you're
referring to thread NUM of the current inferior.

The $_thread convenience var and Python's InferiorThread.num attribute
are remapped to the new per-inferior thread number.  It's a backward
compatibility break, but since it only matters when debugging multiple
inferiors, I think it's worth doing.

Because MI thread IDs need to be a single integer, we keep giving
threads a global identifier, _in addition_ to the per-inferior number,
and make MI always refer to the global thread IDs.  IOW, nothing
changes from a MI frontend's perspective.

Similarly, since Python's Breakpoint.thread and Guile's
breakpoint-thread/set-breakpoint-thread breakpoint methods need to
work with integers, those are adjusted to work with global thread IDs
too.  Follow up patches will provide convenient means to access
threads' global IDs.

To avoid potencially confusing users (which also avoids updating much
of the testsuite), if there's only one inferior and its ID is "1",
IOW, the user hasn't done anything multi-process/inferior related,
then the "INF." part of thread IDs is not shown.  E.g,.:

 (gdb) info inferiors
   Num  Description       Executable
 * 1    process 15275     /home/pedro/gdb/tests/threads
 (gdb) info threads
   Id   Target Id         Frame
 * 1    Thread 0x7ffff7fc1740 (LWP 15275) "threads" main () at threads.c:40
 (gdb) add-inferior
 Added inferior 2
 (gdb) info threads
   Id   Target Id         Frame
 * 1.1  Thread 0x7ffff7fc1740 (LWP 15275) "threads" main () at threads.c:40
 (gdb)

No regressions on x86_64 Fedora 20.

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

	* NEWS: Mention that thread IDs are now per inferior and global
	thread IDs.
	* Makefile.in (SFILES): Add tid-parse.c.
	(COMMON_OBS): Add tid-parse.o.
	(HFILES_NO_SRCDIR): Add tid-parse.h.
	* ada-tasks.c: Adjust to use ptid_to_global_thread_id.
	* breakpoint.c (insert_breakpoint_locations)
	(remove_threaded_breakpoints, bpstat_check_breakpoint_conditions)
	(print_one_breakpoint_location, set_longjmp_breakpoint)
	(check_longjmp_breakpoint_for_call_dummy)
	(set_momentary_breakpoint): Adjust to use global IDs.
	(find_condition_and_thread, watch_command_1): Use parse_thread_id.
	(until_break_command, longjmp_bkpt_dtor)
	(breakpoint_re_set_thread, insert_single_step_breakpoint): Adjust
	to use global IDs.
	* dummy-frame.c (pop_dummy_frame_bpt): Adjust to use
	ptid_to_global_thread_id.
	* elfread.c (elf_gnu_ifunc_resolver_stop): Likewise.
	* gdbthread.h (struct thread_info): Rename field 'num' to
	'global_num.  Add new fields 'per_inf_num' and 'inf'.
	(thread_id_to_pid): Rename thread_id_to_pid to
	global_thread_id_to_ptid.
	(pid_to_thread_id): Rename to ...
	(ptid_to_global_thread_id): ... this.
	(valid_thread_id): Rename to ...
	(valid_global_thread_id): ... this.
	(find_thread_id): Rename to ...
	(find_thread_global_id): ... this.
	(ALL_THREADS, ALL_THREADS_BY_INFERIOR): Declare.
	(print_thread_info): Add comment.
	* tid-parse.h: New file.
	* tid-parse.c: New file.
	* infcmd.c (step_command_fsm_prepare)
	(step_command_fsm_should_stop): Adjust to use the global thread
	ID.
	(until_next_command, until_next_command)
	(finish_command_fsm_should_stop): Adjust to use the global thread
	ID.
	(attach_post_wait): Adjust to check the inferior number too.
	* inferior.h (struct inferior) <highest_thread_num>: New field.
	* infrun.c (handle_signal_stop)
	(insert_exception_resume_breakpoint)
	(insert_exception_resume_from_probe): Adjust to use the global
	thread ID.
	* record-btrace.c (record_btrace_open): Use global thread IDs.
	* remote.c (process_initial_stop_replies): Also consider the
	inferior number.
	* target.c (target_pre_inferior): Clear the inferior's highest
	thread num.
	* thread.c (clear_thread_inferior_resources): Adjust to use the
	global thread ID.
	(new_thread): New inferior parameter.  Adjust to use it.  Set both
	the thread's global ID and the thread's per-inferior ID.
	(add_thread_silent): Adjust.
	(find_thread_global_id): New.
	(find_thread_id): Make static.  Adjust to rename.
	(valid_thread_id): Rename to ...
	(valid_global_thread_id): ... this.
	(pid_to_thread_id): Rename to ...
	(ptid_to_global_thread_id): ... this.
	(thread_id_to_pid): Rename to ...
	(global_thread_id_to_ptid): ... this.  Adjust.
	(first_thread_of_process): Adjust.
	(do_captured_list_thread_ids): Adjust to use global thread IDs.
	(should_print_thread): New function.
	(print_thread_info): Rename to ...
	(print_thread_info_1): ... this, and add new show_global_ids
	parameter.  Handle it.  Iterate over inferiors.
	(print_thread_info): Reimplement as wrapper around
	print_thread_info_1.
	(show_inferior_qualified_tids): New function.
	(print_thread_id): Use it.
	(tp_array_compar): Compare inferior numbers too.
	(thread_apply_command): Use tid_range_parser.
	(do_captured_thread_select): Use parse_thread_id.
	(thread_id_make_value): Adjust.
	(_initialize_thread): Adjust "info threads" help string.
	* varobj.c (struct varobj_root): Update comment.
	(varobj_create): Adjust to use global thread IDs.
	(value_of_root_1): Adjust to use global_thread_id_to_ptid.
	* windows-tdep.c (display_tib): No longer accept an argument.
	* cli/cli-utils.c (get_number_trailer): Make extern.
	* cli/cli-utils.h (get_number_trailer): Declare.
	(get_number_const): Adjust documentation.
	* mi/mi-cmd-var.c (mi_cmd_var_update_iter): Adjust to use global
	thread IDs.
	* mi/mi-interp.c (mi_new_thread, mi_thread_exit)
	(mi_on_normal_stop, mi_output_running_pid, mi_on_resume):
	* mi/mi-main.c (mi_execute_command, mi_cmd_execute): Likewise.
	* guile/scm-breakpoint.c (gdbscm_set_breakpoint_thread_x):
	Likewise.
	* python/py-breakpoint.c (bppy_set_thread): Likewise.
	* python/py-finishbreakpoint.c (bpfinishpy_init): Likewise.
	* python/py-infthread.c (thpy_get_num): Add comment and return the
	per-inferior thread ID.
	(thread_object_getset): Update comment of "num".

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

	* gdb.base/break.exp: Adjust to output changes.
	* gdb.base/hbreak2.exp: Likewise.
	* gdb.base/sepdebug.exp: Likewise.
	* gdb.base/watch_thread_num.exp: Likewise.
	* gdb.linespec/keywords.exp: Likewise.
	* gdb.multi/info-threads.exp: Likewise.
	* gdb.threads/thread-find.exp: Likewise.
	* gdb.multi/tids.c: New file.
	* gdb.multi/tids.exp: New file.

gdb/doc/ChangeLog:
2016-01-07  Pedro Alves  <palves@redhat.com>

	* gdb.texinfo (Threads): Document per-inferior thread IDs,
	qualified thread IDs, global thread IDs and thread ID lists.
	(Set Watchpoints, Thread-Specific Breakpoints): Adjust to refer to
	thread IDs.
	(Convenience Vars): Document the $_thread convenience variable.
	(Ada Tasks): Adjust to refer to thread IDs.
	(GDB/MI Async Records, GDB/MI Thread Commands, GDB/MI Ada Tasking
	Commands, GDB/MI Variable Objects): Update to mention global
	thread IDs.
	* guile.texi (Breakpoints In Guile)
	<breakpoint-thread/set-breakpoint-thread breakpoint>: Mention
	global thread IDs instead of thread IDs.
	* python.texi (Threads In Python): Adjust documentation of
	InferiorThread.num.
	(Breakpoint.thread): Mention global thread IDs instead of thread
	IDs.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Add Python InferiorThread.global_num attribute
@ 2016-01-13 11:40 sergiodj+buildbot
  2016-01-13 16:39 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-13 11:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 22a0232400ea09c57ab70d97cffc1f25e6320da7 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 22a0232400ea09c57ab70d97cffc1f25e6320da7

Add Python InferiorThread.global_num attribute

This commit adds a new Python InferiorThread.global_num attribute.
This can be used to pass the correct thread ID to Breakpoint.thread,
which takes a global thread ID, not a per-inferior thread number.

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

	* NEWS: Mention InferiorThread.global_num.
	* python/py-infthread.c (thpy_get_global_num): New function.
	(thread_object_getset): Register "global_num".

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

	* gdb.multi/tids.exp: Test InferiorThread.global_num and
	Breakpoint.thread.
	* gdb.python/py-infthread.exp: Test InferiorThread.global_num.

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

	* python.texi (Breakpoints In Python) <Breakpoint.thread>: Add
	anchor.
	(Threads In Python): Document new InferiorThread.global_num
	attribute.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Implement "info threads -gid"
@ 2016-01-13 11:41 sergiodj+buildbot
  2016-01-13 17:39 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-13 11:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c84f6bbfe50ff13928360d3cc349d7c553867ce6 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: c84f6bbfe50ff13928360d3cc349d7c553867ce6

Implement "info threads -gid"

This commit makes global thread IDs optionaly visible in "info
threads", with the new "-gid" switch:

 (gdb) info threads -gid
   Id   GId  Target Id         Frame
   1.1  1    Thread 0x7ffff7fc2740 (LWP 6022) "threads" (running)
   1.2  3    Thread 0x7ffff77c0700 (LWP 6028) "threads" (running)
   1.3  4    Thread 0x7ffff7fc2740 (LWP 6032) "threads" (running)
   2.1  2    Thread 0x7ffff7fc1700 (LWP 6037) "threads" (running)
   2.2  5    Thread 0x7ffff77c0700 (LWP 6038) "threads" (running)
 * 2.3  6    Thread 0x7ffff7fc2740 (LWP 6039) "threads" (running)

 (gdb) info threads
   Id   Target Id         Frame
   1.1  Thread 0x7ffff7fc2740 (LWP 6022) "threads" (running)
   1.2  Thread 0x7ffff77c0700 (LWP 6028) "threads" (running)
   1.3  Thread 0x7ffff7fc2740 (LWP 6032) "threads" (running)
   2.1  Thread 0x7ffff7fc1700 (LWP 6037) "threads" (running)
   2.2  Thread 0x7ffff77c0700 (LWP 6038) "threads" (running)
 * 2.3  Thread 0x7ffff7fc2740 (LWP 6039) "threads" (running)

No regressions on x86_64 Fedora 20.

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

	* NEWS: Mention "info threads -gid".
	* gdbthread.h (struct thread_info) <global_num>: Mention "info
	threads -gid".
	* thread.c (info_threads_command): Handle "-gid".
	(_initialize_thread): Adjust "info threads" help string to mention
	-gid.

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

	* gdb.multi/tids.exp: Test "info threads -gid".

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

	* gdb.texinfo (Threads): Document "info threads -gid".


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Add $_gthread convenience variable
@ 2016-01-13 11:42 sergiodj+buildbot
  2016-01-13 18:41 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-13 11:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 663f6d42f47265d2deaa86c8a976e658fb13f820 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 663f6d42f47265d2deaa86c8a976e658fb13f820

Add $_gthread convenience variable

This commit adds a new $_gthread convenience variable, that is like
$_thread, but holds the current thread's global thread id.

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

	* NEWS: Mention $_gthread.
	* gdbthread.h (struct thread_info) <global_num>: Mention
	$_gthread.
	* thread.c (thread_num_make_value_helper): New function.
	(thread_id_make_value): Delete.
	(thread_id_per_inf_num_make_value, global_thread_id_make_value):
	New.
	(thread_funcs): Adjust.
	(gthread_funcs): New.
	(_initialize_thread): Register $_gthread variable.

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

	* gdb.base/default.exp: Expect $_gthread as well.
	* gdb.multi/tids.exp: Test $_gthread.
	* gdb.threads/thread-specific.exp: Test $_gthread.

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

	* gdb.texinfo (Threads): Document the $_gthread convenience
	variable.
	(Convenience Vars): Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] MAINTAINERS: Add Andreas Arnez as s390 target maintainer.
@ 2016-01-13 18:04 sergiodj+buildbot
  2016-01-13 20:43 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-13 18:04 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bc06e0b148dfc4f2e52003a17d48463150f72e7b ***

Author: Ulrich Weigand <ulrich.weigand@de.ibm.com>
Branch: master
Commit: bc06e0b148dfc4f2e52003a17d48463150f72e7b

MAINTAINERS: Add Andreas Arnez as s390 target maintainer.

gdb/ChangeLog:

	* MAINTAINERS: Add Andreas Arnez as s390 target maintainer.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [AArch64] Fix missing architecture checks for ARMv8.2 system registers.
@ 2016-01-14 11:03 sergiodj+buildbot
  2016-01-14 11:40 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-14 11:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 651657fa61aa0a2946d56063295a7ce8d73f803b ***

Author: Matthew Wahab <matthew.wahab@arm.com>
Branch: master
Commit: 651657fa61aa0a2946d56063295a7ce8d73f803b

[AArch64] Fix missing architecture checks for ARMv8.2 system registers.

Some of the RAS system registers added to binutils as part of the ARMv8.2
support are missing the feature checks to warn when they aren't
supported by the target.

This patch adds the missing feature checks with a test to check that
the correct warnings are given for all the ARMv8.2 system registers.

gas/
2016-01-14  Matthew Wahab  <matthew.wahab@arm.com>

	* testsuite/gas/aarch64/illegal-sysreg-2.l: New.
	* testsuite/gas/aarch64/illegal-sysreg-2.d: New.

opcodes/
2016-01-14  Matthew Wahab  <matthew.wahab@arm.com>

	* aarch64-opc.c (aarch64_sys_reg_supported_p): Merge conditionals
	testing for RAS support.  Add checks for erxfr_el1, erxctlr_el1,
	erxtatus_el1 and erxaddr_el1.

Change-Id: I66b590ea49c1eb6b0e5c93e0dc2bc9c4e79a52fe


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix C++ build error by casting void *
@ 2016-01-14 12:30 sergiodj+buildbot
  2016-01-14 13:06 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-14 12:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c0518081f09298c67d1e74e0cc592fde8e0c6571 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: c0518081f09298c67d1e74e0cc592fde8e0c6571

Fix C++ build error by casting void *

Two recent patches breaks GDB C++ mode build,

  https://sourceware.org/ml/gdb-patches/2016-01/msg00150.html
  https://sourceware.org/ml/gdb-patches/2016-01/msg00086.html

gdb/remote.c: In function 'int remote_set_syscall_catchpoint(target_ops*, int, int, int, int, int*)':
gdb/remote.c:2036:39: error: invalid conversion from 'void*' to 'char*' [-fpermissive]
       catch_packet = xmalloc (maxpktsz);
                                       ^

gdb/thread.c: In function 'int do_captured_thread_select(ui_out*, void*)':
gdb/git/gdb/thread.c:1999:24: error: invalid conversion from 'void*' to 'const char*' [-fpermissive]
   const char *tidstr = tidstr_v;
                        ^

this patch fixes them by casting void * to the right type.

gdb:

2016-01-14  Yao Qi  <yao.qi@linaro.org>

	* remote.c (remote_set_syscall_catchpoint): Cast to char *.
	* thread.c (do_captured_thread_select): Cast to const char *.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [ARM] Remove field syscall_next_pc in struct gdbarch_tdep
@ 2016-01-14 14:57 sergiodj+buildbot
  2016-01-14 15:33 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-14 14:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e7cf25a8ab54cd02b48e7443ef25764475f02315 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: e7cf25a8ab54cd02b48e7443ef25764475f02315

[ARM] Remove field syscall_next_pc in struct gdbarch_tdep

Field syscall_next_pc in struct gdbarch_tdep was to calculate the
next pc of syscall instruction.  On linux target, syscall_next_pc
is set to arm_linux_syscall_next_pc, to do linux specific things.
However, after we have struct arm_get_next_pcs_ops, we can do the
same thing in struct arm_get_next_pcs_ops field syscall_next_pc,
so syscall_next_pc in struct gdbarch_tdep is not needed any more.

gdb:

2016-01-14  Yao Qi  <yao.qi@linaro.org>

	* arm-linux-tdep.c (arm_linux_get_next_pcs_syscall_next_pc):
	Declare.
	(arm_linux_get_next_pcs_ops): Install
	arm_linux_get_next_pcs_syscall_next_pc.
	(arm_linux_syscall_next_pc): Change to ...
	(arm_linux_get_next_pcs_syscall_next_pc): ... it.
	(arm_linux_init_abi): Don't set tdep->syscall_next_pc.
	* arm-tdep.c (arm_get_next_pcs_syscall_next_pc): Declare.
	(arm_get_next_pcs_syscall_next_pc): Make it static.  Don't
	call tdep->syscall_next_pc.
	* arm-tdep.h (struct gdbarch_tdep) <syscall_next_pc>: Remove.
	(arm_get_next_pcs_syscall_next_pc): Remove.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix display of RL78 MOVW instructions that use the stack pointer.
@ 2016-01-14 16:27 sergiodj+buildbot
  2016-01-14 17:03 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-14 16:27 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4d82fe66e8d38b20ad429cb99a99ed8741336d72 ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: 4d82fe66e8d38b20ad429cb99a99ed8741336d72

Fix display of RL78 MOVW instructions that use the stack pointer.

	* rl78-decode.opc (rl78_decode_opcode): Add 's' operand to movw
	instructions that can support stack pointer operations.
	* rl78-decode.c: Regenerate.
	* rl78-dis.c: Fix display of stack pointer in MOVW based
	instructions.

	* testsuite/gas/rl78/sp-relative-movw.s: New test.
	* testsuite/gas/rl78/sp-relative-movw.d: Expected disassembly.
	* testsuite/gas/rl78/rl78.exp: Run the new test.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix "thread apply $conv_var" and misc other related problems
@ 2016-01-15 21:59 sergiodj+buildbot
  2016-01-15 22:30 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-15 21:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3f5b7598805c8253c43c989a540a2408c8b685ad ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 3f5b7598805c8253c43c989a540a2408c8b685ad

Fix "thread apply $conv_var" and misc other related problems

This fixes a few bugs in "thread apply".

While this works:

 (gdb) thread apply 1 p 1234

 Thread 1 (Thread 0x7ffff7fc1740 (LWP 14048)):
 $1 = 1234

This doesn't:

 (gdb) thread apply $thr p 1234

 Thread 1 (Thread 0x7ffff7fc1740 (LWP 12039)):
 Invalid thread ID: p 1234
 (gdb)

~~~~

Also, while this works:
 (gdb) thread apply 1
 Please specify a command following the thread ID list

This doesn't:
 (gdb) thread apply $thr
 Thread 1 (Thread 0x7ffff7fc1740 (LWP 12039)):
 [Current thread is 1 (Thread 0x7ffff7fc1740 (LWP 12039))]
 (gdb)

~~~~

And, while this works:
 (gdb) thread apply
 Please specify a thread ID list

This obviously bogus invocation is just silent:
 (gdb) thread apply bt
 (gdb)

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

	* thread.c (thread_apply_command): Use the tid range parser to
	advance past the thread ID list.
	* tid-parse.c (get_positive_number_trailer): New function.
	(parse_thread_id): Use it.
	(get_tid_or_range): Use it.  Return 0 instead of throwing invalid
	thread ID error.
	(get_tid_or_range): Detect negative values.  Return 0 instead of
	throwing invalid thread ID error.

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

	* gdb.multi/tids.exp (thr_apply_info_thr_error): Remove "p 1234"
	command from "thread apply" invocation.
	(thr_apply_info_thr_invalid): Default the expected output to the
	input tid list.
	(top level): Add tests that use convenience variables.  Add tests
	for "thread apply" with a valid TID list, but missing the command.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Star wildcard ranges (e.g., "info thread 2.*")
@ 2016-01-15 22:25 sergiodj+buildbot
  2016-01-15 23:33 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-15 22:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 71ef29a86b252a4780517fc9b2bf9f7d3dd2d991 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 71ef29a86b252a4780517fc9b2bf9f7d3dd2d991

Star wildcard ranges (e.g., "info thread 2.*")

Add support for specifying "all threads of inferior N", by writing "*"
as thread number/range in thread ID lists.

E.g., "info threads 2.*" or "thread apply 2.* bt".

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

	* NEWS: Mention star wildcard ranges.
	* cli/cli-utils.c (get_number_or_range): Check state->in_range first.
	(number_range_setup_range): New function.
	* cli/cli-utils.h (number_range_setup_range): New declaration.
	* thread.c (thread_apply_command): Support star TID ranges.
	* tid-parse.c (tid_range_parser_finished)
	(tid_range_parser_string, tid_range_parser_skip)
	(get_tid_or_range, get_tid_or_range): Handle
	TID_RANGE_STATE_STAR_RANGE.
	(tid_range_parser_star_range): New function.
	* tid-parse.h (enum tid_range_state) <TID_RANGE_STATE_STAR_RANGE>:
	New value.
	(tid_range_parser_star_range): New declaration.

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

	* gdb.texinfo (Threads) <thread ID lists>: Document star ranges.

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

	* gdb.multi/tids.exp: Test star wildcard ranges.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix phony_iconv wide character support.
@ 2016-01-15 22:55 sergiodj+buildbot
  2016-01-16  0:36 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-15 22:55 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f74f61cbf72dc158832d81d6ecd6f970f93798cc ***

Author: Sandra Loosemore <sandra@codesourcery.com>
Branch: master
Commit: f74f61cbf72dc158832d81d6ecd6f970f93798cc

Fix phony_iconv wide character support.

2016-01-15  Sandra Loosemore  <sandra@codesourcery.com>

	gdb/
	* charset.c [PHONY_ICONV] (GDB_DEFAULT_HOST_CHARSET):
	Conditionalize for Windows host.
	(GDB_DEFAULT_TARGET_CHARSET): Match GDB_DEFAULT_HOST_CHARSET.
	(GDB_DEFAULT_TARGET_WIDE_CHARSET): Use UTF-32.
	(phony_iconv_open): Handle both UTF-32 endiannesses.
	(phony_iconv): Likewise.  Check for output overflow and clean up
	out-of-input cases.  Correct adjustment to input buffer pointer.
	(set_be_le_names) [PHONY_ICONV]: Use hard-wired names to match
	phony_iconv_open.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Regen configure
@ 2016-01-17  3:05 sergiodj+buildbot
  2016-01-17  3:42 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-17  3:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5c14705fb3dfb359235314f22392e7a5ce6d4085 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 5c14705fb3dfb359235314f22392e7a5ce6d4085

Regen configure

Picks up 2016-01-12 libtool.m4 change.

bfd/
	* configure: Regenerate.
binutils/
	* configure: Regenerate.
gas/
	* configure: Regenerate.
gprof/
	* configure: Regenerate.
ld/
	* configure: Regenerate.
opcodes/
	* configure: Regenerate.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] minor reformatting in sim/common/sim-fpu.c.
@ 2016-01-17  5:43 sergiodj+buildbot
  2016-01-17  6:14 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-17  5:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3c8e93b7fab5b9d8ddb786772ab00d65ec127159 ***

Author: Joel Brobecker <brobecker@adacore.com>
Branch: master
Commit: 3c8e93b7fab5b9d8ddb786772ab00d65ec127159

minor reformatting in sim/common/sim-fpu.c.

This patch just makes a copy of formatting changes to better conform
with the GNU Coding Style.

sim/common/ChangeLog:

        * sim-fpu.c (print_bits): Minor reformatting (no code change).
        (sim_fpu_map): Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Minor comment fixes in sim/common/sim-fpu.c.
@ 2016-01-17  6:14 sergiodj+buildbot
  2016-01-17  7:14 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-17  6:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f749ed6079486300a65d7407e9fa3a7a296827f6 ***

Author: Joel Brobecker <brobecker@adacore.com>
Branch: master
Commit: f749ed6079486300a65d7407e9fa3a7a296827f6

Minor comment fixes in sim/common/sim-fpu.c.

This patch makes a fair number of fixes in the various comments of
sim-fpu.c, mostly to either better conform to the GNU Coding Standards
(sentences start with a capital letter, end with a period), or to
fix spelling mistakes.

sim/common/ChangeLog:

        * sim-fpu.c: Minor comment fixes throughout.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] fix gdb version parsing in src-release.sh
@ 2016-01-17  6:17 sergiodj+buildbot
  2016-01-17  8:14 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-17  6:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b677098d4e086c093554a064076e021fec0399e8 ***

Author: Joel Brobecker <brobecker@adacore.com>
Branch: master
Commit: b677098d4e086c093554a064076e021fec0399e8

fix gdb version parsing in src-release.sh

Small change required after we switched the gdb version scheme to
using a -git suffix rather than a -cvs one.

ChangeLog:

        * src-release.sh: Compute the gdb tarball name by stripping
        '-git' rather than '-cvs'.

Tested by running "src-release.sh gdb" and verifying the tarball
name as well as its contents.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] GDB SIGSEGV opening a Fortran program compiled with ifort
@ 2016-01-17  7:04 sergiodj+buildbot
  2016-01-17  9:14 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-17  7:04 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT dc365182240722969f044918ecd3cab00da55502 ***

Author: Jonas Hahnfeld <Hahnfeld@itc.rwth-aachen.de>
Branch: master
Commit: dc365182240722969f044918ecd3cab00da55502

GDB SIGSEGV opening a Fortran program compiled with ifort

This patch fixes a SIGSEGV when trying to open a Fortran program
compiled with ifort (reproduced using version using version 16.0.1.150).
The error can be reproduce with most, if not any program. For instance,
a single file only containing "end", compiled with no additional flag,
suffices.

gdb/ChangeLog:

       PR gdb/19208
       * dwarf2read.c (read_partial_die): Do not call set_objfile_main_name
       if the function has no name.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix gdbserver build failure on targets without fork
@ 2016-01-18 11:57 sergiodj+buildbot
  2016-01-18 12:31 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-18 11:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT eb0edac83f82516bbbd5a0412bbdf7fd27c687f2 ***

Author: Gary Benson <gbenson@redhat.com>
Branch: master
Commit: eb0edac83f82516bbbd5a0412bbdf7fd27c687f2

Fix gdbserver build failure on targets without fork

This commit fixes nat/linux-namespaces.c to build correctly on
targets without fork.

gdb/ChangeLog:

	* nat/linux-namespaces.c (do_fork): New function.
	(linux_mntns_get_helper): Use the above.

gdb/gdbserver/ChangeLog:

	* configure.ac (AC_FUNC_FORK): New check.
	* config.in: Regenerate.
	* configure: Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Provide AC_PROG_LEX that copes with LEX=missing from top-level
@ 2016-01-18 12:05 sergiodj+buildbot
  2016-01-18 13:32 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-18 12:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3d961d0d3a797b4d463024a11131e96c213dee27 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 3d961d0d3a797b4d463024a11131e96c213dee27

Provide AC_PROG_LEX that copes with LEX=missing from top-level

config/
	PR binutils/19481
	* override.m4 (AC_PROG_LEX): Define.
binutils/
	* configure: Regenerate.
gas/
	* configure: Regenerate.
ld/
	* configure: Regenerate.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [testsuite] @progbits -> %progbits
@ 2016-01-18 14:40 sergiodj+buildbot
  2016-01-18 15:10 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-18 14:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b27896961a641e92a642b352627208233dfeb7f1 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: b27896961a641e92a642b352627208233dfeb7f1

[testsuite] @progbits -> %progbits

The ARM assembler has "@" as a comment character, so there are compile
errors in {py,scm}-section-script.c,

 gdb compile failed, /tmp/ccHEzYqy.s: Assembler messages:
 /tmp/ccHEzYqy.s:19: Error: junk at end of line, first unrecognized character is `,'
 /tmp/ccHEzYqy.s:24: Error: junk at end of line, first unrecognized character is `,'
 /tmp/ccHEzYqy.s:29: Error: junk at end of line, first unrecognized character is `,'
 /tmp/ccHEzYqy.s:41: Error: junk at end of line, first unrecognized character is `,'

This patch replaces @progbits with %progbits.

gdb/testsuite:

2016-01-18  Yao Qi  <yao.qi@linaro.org>

	* gdb.guile/scm-section-script.c: Replace @progbits with
	%progbits.
	* gdb.python/py-section-script.c: Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Replace some $ARCH_{get, set}_pc with linux_{get, set}_pc_32bit
@ 2016-01-18 15:11 sergiodj+buildbot
  2016-01-18 16:10 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-18 15:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 276d4552dfc2dc3906fa2bd8690ea85b3d8ec055 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 276d4552dfc2dc3906fa2bd8690ea85b3d8ec055

Replace some $ARCH_{get,set}_pc with linux_{get,set}_pc_32bit

This patch adds a pair of new functions linux_get_pc_32bit and
linux_set_pc_32bit which get and set 32-bit register "pc" from
regcache.  This function can be used some targets and these own
$ARCH_{get,set}_pc are replaced by linux_{get,set}_pc_32bit
respectively.

This patch touches many targets, but I only have arm board to
test and no regression.  I also rebuilt nios2-linux GDBserver.
If it is right to go, I'll post the 64-bit counterpart later.

gdb/gdbserver:

2016-01-18  Yao Qi  <yao.qi@linaro.org>

	* linux-arm-low.c (debug_threads): Remove declaration.
	(arm_get_pc, arm_set_pc): Remove.
	(the_low_target): Use linux_get_pc_32bit and
	linux_set_pc_32bit.
	* linux-bfin-low.c (bfin_get_pc, bfin_set_pc): Remove.
	(the_low_target): Use linux_get_pc_32bit and
	linux_set_pc_32bit.
	* linux-cris-low.c (debug_threads): Remove declaration.
	(cris_get_pc, cris_set_pc,): Remove.
	(the_low_target): Use linux_get_pc_32bit and
	linux_set_pc_32bit.
	* linux-crisv32-low.c (debug_threads): Remove declaration.
	(cris_get_pc, cris_set_pc): Remove.
	(the_low_target): Use linux_get_pc_32bit and
	linux_set_pc_32bit.
	* linux-low.c: Include inttypes.h.
	(linux_get_pc_32bit, linux_set_pc_32bit): New functions.
	* linux-low.h (linux_get_pc_32bit, linux_set_pc_32bit): Declare.
	* linux-m32r-low.c (m32r_get_pc, m32r_set_pc): Remove.
	(the_low_target): Use linux_get_pc_32bit and
	linux_set_pc_32bit.
	* linux-m68k-low.c (m68k_get_pc, m68k_set_pc): Remove.
	(the_low_target): Use linux_get_pc_32bit and
	linux_set_pc_32bit.
	* linux-nios2-low.c (nios2_get_pc, nios2_set_pc): Remove.
	(the_low_target): Use linux_get_pc_32bit and
	linux_set_pc_32bit.
	* linux-sh-low.c (sh_get_pc, sh_set_pc): Remove.
	(the_low_target): Use linux_get_pc_32bit and
	linux_set_pc_32bit.
	* linux-xtensa-low.c (xtensa_get_pc, xtensa_set_pc): Remove.
	(the_low_target): Use linux_get_pc_32bit and
	linux_set_pc_32bit.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Replace some $ARCH_{get, set}_pc with linux_{get, set}_pc_64bit
@ 2016-01-18 15:19 sergiodj+buildbot
  2016-01-18 17:10 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-18 15:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6f69e520676f5f434cf43c250865036b3d516429 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 6f69e520676f5f434cf43c250865036b3d516429

Replace some $ARCH_{get,set}_pc with linux_{get,set}_pc_64bit

This patch is the follow-up of
https://sourceware.org/ml/gdb-patches/2016-01/msg00164.html to provide
linux_{get,set}_pc_64bit functions.

Rebuild GDBserver with tilegx-linux-gcc.  Not tested.

I think about pc in Tile-GX a little bit.  Looks current Tile-GX
supports debugging 32-bit program (multi-arch), but PC is always
64-bit.  See this thread
https://sourceware.org/ml/gdb-patches/2013-02/msg00113.html
and GDBserver reads PC as 64-bit through ptrace.  However, if
the inferior is 32-bit, the PC in the target description and
regcache is 32-bit, so only 32-bit contents are sent back GDB.
Anyway, Tile-GX GDBserver may have some problems here, but this
patch doesn't change anything.

gdb/gdbserver:

2016-01-18  Yao Qi  <yao.qi@linaro.org>

	* linux-low.c (linux_set_pc_64bit): New function.
	(linux_get_pc_64bit): New function.
	* linux-low.h (linux_set_pc_64bit, linux_get_pc_64bit):
	Declare.
	* linux-sparc-low.c (debug_threads): Remove declaration.
	(sparc_get_pc): Remove.
	(the_low_target): Use linux_get_pc_64bit instead of
	sparc_get_pc.
	* linux-tile-low.c (tile_get_pc, tile_set_pc): Remove.
	(the_low_target): Use linux_get_pc_64bit and
	linux_set_pc_64bit.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix PR threads/19422 - show which thread caused stop
@ 2016-01-18 16:03 sergiodj+buildbot
  2016-01-18 18:13 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-18 16:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f303dbd60d9c7984832446eeb9d4e4d89703c615 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: f303dbd60d9c7984832446eeb9d4e4d89703c615

Fix PR threads/19422 - show which thread caused stop

This commit changes GDB like this:

 - Program received signal SIGINT, Interrupt.
 + Thread 1 "main" received signal SIGINT, Interrupt.

 - Breakpoint 1 at 0x40087a: file threads.c, line 87.
 + Thread 3 "bar" hit Breakpoint 1 at 0x40087a: file threads.c, line 87.

 ... once the program goes multi-threaded.  Until GDB sees a second
thread spawn, the output is still the same as before, per the
discussion back in 2012:

  https://www.sourceware.org/ml/gdb/2012-11/msg00010.html

This helps non-stop mode, where you can't easily tell which thread hit
a breakpoint or received a signal:

 (gdb) info threads
   Id   Target Id         Frame
 * 1    Thread 0x7ffff7fc1740 (LWP 19362) "main" (running)
   2    Thread 0x7ffff7fc0700 (LWP 19366) "foo" (running)
   3    Thread 0x7ffff77bf700 (LWP 19367) "bar" (running)
 (gdb)
 Program received signal SIGUSR1, User defined signal 1.
 0x0000003616a09237 in pthread_join (threadid=140737353877248, thread_return=0x7fffffffd5b8) at pthread_join.c:92
 92          lll_wait_tid (pd->tid);
 (gdb) b threads.c:87
 Breakpoint 1 at 0x40087a: file threads.c, line 87.
 (gdb)
 Breakpoint 1, thread_function1 (arg=0x1) at threads.c:87
 87              usleep (1);  /* Loop increment.  */

The best the user can do is run "info threads" and try to figure
things out.

It actually also affects all-stop mode, in case of "handle SIG print
nostop":

...
  Program received signal SIGUSR1, User defined signal 1.

  Program received signal SIGUSR1, User defined signal 1.

  Program received signal SIGUSR1, User defined signal 1.

  Program received signal SIGUSR1, User defined signal 1.
...

The above doesn't give any clue that these were different threads
getting the SIGUSR1 signal.

I initially thought of lowercasing "breakpoint" in

  "Thread 3 hit Breakpoint 1"

but then after trying it I realized that leaving "Breakpoint"
uppercase helps the eye quickly find the relevant information.  It's
also easier to implement not showing anything about threads until the
program goes multi-threaded this way.

Here's a larger example session in non-stop mode:

  (gdb) c -a&
  Continuing.
  (gdb) interrupt -a
  (gdb)
  Thread 1 "main" stopped.
  0x0000003616a09237 in pthread_join (threadid=140737353877248, thread_return=0x7fffffffd5b8) at pthread_join.c:92
  92          lll_wait_tid (pd->tid);

  Thread 2 "foo" stopped.
  0x0000003615ebc6ed in nanosleep () at ../sysdeps/unix/syscall-template.S:81
  81      T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)

  Thread 3 "bar" stopped.
  0x0000003615ebc6ed in nanosleep () at ../sysdeps/unix/syscall-template.S:81
  81      T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
  b threads.c:87
  Breakpoint 4 at 0x40087a: file threads.c, line 87.
  (gdb) b threads.c:67
  Breakpoint 5 at 0x400811: file threads.c, line 67.
  (gdb) c -a&
  Continuing.
  (gdb)
  Thread 3 "bar" hit Breakpoint 4, thread_function1 (arg=0x1) at threads.c:87
  87              usleep (1);  /* Loop increment.  */

  Thread 2 "foo" hit Breakpoint 5, thread_function0 (arg=0x0) at threads.c:68
  68              (*myp) ++;
  info threads
    Id   Target Id         Frame
  * 1  Thread 0x7ffff7fc1740 (LWP 31957) "main" (running)
    2  Thread 0x7ffff7fc0700 (LWP 31961) "foo" thread_function0 (arg=0x0) at threads.c:68
    3  Thread 0x7ffff77bf700 (LWP 31962) "bar" thread_function1 (arg=0x1) at threads.c:87
  (gdb) shell kill -SIGINT 31957
  (gdb)
  Thread 1 "main" received signal SIGINT, Interrupt.
  0x0000003616a09237 in pthread_join (threadid=140737353877248, thread_return=0x7fffffffd5b8) at pthread_join.c:92
  92          lll_wait_tid (pd->tid);
  info threads
    Id   Target Id         Frame
  * 1  Thread 0x7ffff7fc1740 (LWP 31957) "main" 0x0000003616a09237 in pthread_join (threadid=140737353877248, thread_return=0x7fffffffd5b8) at pthread_join.c:92
    2  Thread 0x7ffff7fc0700 (LWP 31961) "foo" thread_function0 (arg=0x0) at threads.c:68
    3  Thread 0x7ffff77bf700 (LWP 31962) "bar" thread_function1 (arg=0x1) at threads.c:87
  (gdb) t 2
  [Switching to thread 2, Thread 0x7ffff7fc0700 (LWP 31961)]
  #0  thread_function0 (arg=0x0) at threads.c:68
  68              (*myp) ++;
  (gdb) catch syscall
  Catchpoint 6 (any syscall)
  (gdb) c&
  Continuing.
  (gdb)
  Thread 2 "foo" hit Catchpoint 6 (call to syscall nanosleep), 0x0000003615ebc6ed in nanosleep () at ../sysdeps/unix/syscall-template.S:81
  81      T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)

I'll work on documentation next if this looks agreeable.

This patch applies on top of the star wildcards thread IDs series:

  https://sourceware.org/ml/gdb-patches/2016-01/msg00291.html

For convenience, I've pushed this to the
users/palves/show-which-thread-caused-stop branch.

gdb/doc/ChangeLog:
2016-01-18  Pedro Alves  <palves@redhat.com>

	* gdb.texinfo (Threads): Mention that GDB displays the ID and name
	of the thread that hit a breakpoint or received a signal.

gdb/ChangeLog:
2016-01-18  Pedro Alves  <palves@redhat.com>

	* NEWS: Mention that GDB now displays the ID and name of the
	thread that hit a breakpoint or received a signal.
	* break-catch-sig.c (signal_catchpoint_print_it): Use
	maybe_print_thread_hit_breakpoint.
	* break-catch-syscall.c (print_it_catch_syscall): Likewise.
	* break-catch-throw.c (print_it_exception_catchpoint): Likewise.
	* breakpoint.c (maybe_print_thread_hit_breakpoint): New function.
	(print_it_catch_fork, print_it_catch_vfork, print_it_catch_solib)
	(print_it_catch_exec, print_it_ranged_breakpoint)
	(print_it_watchpoint, print_it_masked_watchpoint, bkpt_print_it):
	Use maybe_print_thread_hit_breakpoint.
	* breakpoint.h (maybe_print_thread_hit_breakpoint): Declare.
	* gdbthread.h (show_thread_that_caused_stop): Declare.
	* infrun.c (print_signal_received_reason): Print which thread
	received signal.
	* thread.c (show_thread_that_caused_stop): New function.

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

	* gdb.base/async-shell.exp: Adjust expected output.
	* gdb.base/dprintf-non-stop.exp: Adjust expected output.
	* gdb.base/siginfo-thread.exp: Adjust expected output.
	* gdb.base/watchpoint-hw-hit-once.exp: Adjust expected output.
	* gdb.java/jnpe.exp: Adjust expected output.
	* gdb.threads/clone-new-thread-event.exp: Adjust expected output.
	* gdb.threads/continue-pending-status.exp: Adjust expected output.
	* gdb.threads/leader-exit.exp: Adjust expected output.
	* gdb.threads/manythreads.exp: Adjust expected output.
	* gdb.threads/pthreads.exp: Adjust expected output.
	* gdb.threads/schedlock.exp: Adjust expected output.
	* gdb.threads/siginfo-threads.exp: Adjust expected output.
	* gdb.threads/signal-command-multiple-signals-pending.exp: Adjust
	expected output.
	* gdb.threads/signal-delivered-right-thread.exp: Adjust expected
	output.
	* gdb.threads/sigthread.exp: Adjust expected output.
	* gdb.threads/watchpoint-fork.exp: Adjust expected output.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Use a 32-bit value to hold the section number in the internal COFF symbol structure.
@ 2016-01-18 16:11 sergiodj+buildbot
  2016-01-18 19:17 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-18 16:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9ae678af999b8a692c4e6efbe493f39f0085d149 ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: 9ae678af999b8a692c4e6efbe493f39f0085d149

Use a 32-bit value to hold the section number in the internal COFF symbol structure.

	PR ld/19440
inc	* coff/internal.h (internal_syment): Use int to hold section
	number.
	(N_UNDEF): Cast to int not short.
	(N_ABS): Likewise.
	(N_DEBUG): Likewise.
	(N_TV): Likewise.
	(P_TV): Likewise.

bfd	PR ld/19440
	* coff-rs6000.c (_bfd_xcoff_swap_sym_in): Sign extend external
	section number into internal section number.
	* coff64-rs6000.c (_bfd_xcoff64_swap_sym_in): Likewise.
	* coffswap.h (coff_swap_sym_in): Likewise.
	* peXXigen.c (_bfd_XXi_swap_sym_in): Likewise.
	* coffcode.h (_coff_bigobj_swap_sym_in): Make sure that internal
	section number field is big enough to hold the external value.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] testsuite: Remove unused global references in gdb_test
@ 2016-01-18 17:08 sergiodj+buildbot
  2016-01-18 20:17 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-18 17:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8bcbad33671aa67a0079fe4f8f448458de8cc05f ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: 8bcbad33671aa67a0079fe4f8f448458de8cc05f

testsuite: Remove unused global references in gdb_test

Those are unused since gdb_test_multiple was added, factoring out most
of the content of gdb_test.

gdb/testsuite/ChangeLog:

	* lib/gdb.exp (gdb_test): Remove unused global references.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] MIPS: Fix microMIPS instruction size determination
@ 2016-01-18 21:22 sergiodj+buildbot
  2016-01-18 21:51 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-18 21:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3f7f365076a112313870e2a321452bfda6d40914 ***

Author: Maciej W. Rozycki <macro@imgtec.com>
Branch: master
Commit: 3f7f365076a112313870e2a321452bfda6d40914

MIPS: Fix microMIPS instruction size determination

Fix a bug in `micromips_insn_at_pc_has_delay_slot' in instruction size
determination via `mips_insn_size'.  In the microMIPS case the latter
function expects a lone 16-bit instruction word containing the major
opcode regardless of whether the opcode requires another 16-bit word to
follow, to form a complete 32-bit instruction.  Code however passes the
16-bit word previously retrieved shifted left by 16 bits.  Consequently
`mips_insn_size', which examines the low 16-bit only, always sees 0.

By pure coincidence a major opcode of 0 denotes a 32-bit instruction in
the microMIPS instruction set, so the size of 4 is always returned here,
and the following 16-bit word is then merged in the low 16 bits of the
instruction previously shifted by 16 bits.  The resulting 32-bit value
is then passed to `micromips_instruction_has_delay_slot' for delay slot
presence determination.  This function in turn first examines the high
16 bits of the instruction word received and ignores the low 16 bits for
16-bit instructions.

Consequently the only effect of this bug is an extraneous memory read
issued to retrieve a subsequent 16-bit word where a 16-bit instruction
is being examined.  Which in turn may fail if the instruction is located
right at the end of a readable memory area, in which case the lack of a
delay slot will be reported to the caller, which may be incorrect.

This code is used in breakpoint maintenance, for delay slot avoidance,
so the bug would only trigger for the unlikely case of someone placing
a breakpoint in a delay slot of an instruction which is at the end of
readable memory.  Which explains why the bug remained unnoticed so long.

	gdb/
	* mips-tdep.c (micromips_insn_at_pc_has_delay_slot): Pass
	unshifted 16-bit microMIPS instruction word to `mips_insn_size'.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] MIPS: Only build microMIPS specific simulator functions if microMIPS support is required.
@ 2016-01-18 22:01 sergiodj+buildbot
  2016-01-18 22:52 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-18 22:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3d304f48cafbff4b7a1c0a9d338fb20aa4e4934b ***

Author: Andrew Bennett <andrew.bennett@imgtec.com>
Branch: master
Commit: 3d304f48cafbff4b7a1c0a9d338fb20aa4e4934b

MIPS: Only build microMIPS specific simulator functions if microMIPS support is required.

This fixes PR sim/19441.  In the MIPS simulator the microMIPS
functions in micromips.igen were not predicated on the microMIPS
models.  This was causing build issues for some target triples.
This patch sets all the microMIPS specific functions to only be built if
the micromips32, micromips64 or micromipsdsp models are used.

	PR sim/19441
	* micromips.igen (delayslot_micromips): Enable for `micromips32',
	`micromips64' and `micromipsdsp' only.
	(process_isa_mode): Enable for `micromips32' and `micromips64' only.
	(do_micromips_jalr, do_micromips_jal): Likewise.
	(compute_movep_src_reg): Likewise.
	(compute_andi16_imm): Likewise.
	(convert_fmt_micromips): Likewise.
	(convert_fmt_micromips_cvt_d): Likewise.
	(convert_fmt_micromips_cvt_s): Likewise.
	(FMT_MICROMIPS): Likewise.
	(FMT_MICROMIPS_CVT_D): Likewise.
	(FMT_MICROMIPS_CVT_S): Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] MIPS: Remove remnants of 48-bit microMIPS instruction support
@ 2016-01-18 22:31 sergiodj+buildbot
  2016-01-18 23:53 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-18 22:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 100b4f2e9f65565e3e3e484162c4474effc54be8 ***

Author: Maciej W. Rozycki <macro@imgtec.com>
Branch: master
Commit: 100b4f2e9f65565e3e3e484162c4474effc54be8

MIPS: Remove remnants of 48-bit microMIPS instruction support

The POOL48A major opcode was defined in early revisions of the 64-bit
microMIPS ISA, has never been implemented, and was removed before the
64-bit microMIPS ISA specification[1] has been finalized.

This complements commit a6c7053929dd ("MIPS/opcodes: Remove microMIPS
48-bit LI instruction").

References:

[1] "MIPS Architecture for Programmers, Volume II-B: The microMIPS64
    Instruction Set", MIPS Technologies, Inc., Document Number: MD00594,
    Revision 3.06, October 17, 2012, Table 6.2 "microMIPS64 Encoding of
    Major Opcode Field", p. 578

	gas/
	* config/tc-mips.c (micromips_insn_length): Remove the mention
	of 48-bit microMIPS instructions.

	gdb/
	* mips-tdep.c (mips_insn_size): Remove 48-bit microMIPS
	instruction support.
	(micromips_next_pc): Likewise.
	(micromips_scan_prologue): Likewise.
	(micromips_deal_with_atomic_sequence): Likewise.
	(micromips_stack_frame_destroyed_p): Likewise.
	(mips_breakpoint_from_pc): Likewise.

	opcodes/
	* mips-dis.c (print_insn_micromips): Remove 48-bit microMIPS
	instruction support.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Limit breakpoint re-set to the current program space
@ 2016-01-19 12:38 sergiodj+buildbot
  2016-01-19 13:50 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-19 12:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c2f4122d5cc2a21a441470336c8637b6a6965c6e ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: c2f4122d5cc2a21a441470336c8637b6a6965c6e

Limit breakpoint re-set to the current program space

Currently, we always re-set all locations of all breakpoints.  This
commit makes us re-set only locations of the current program space.

If we loaded symbols to a program space (e.g., "file" command or some
shared library was loaded), GDB must run through all breakpoints and
determine if any new locations need to be added to the breakpoint.
However, there's no reason to recreate locations for _other_ program
spaces, as those haven't changed.

Similarly, when we create a new inferior, through e.g., a fork, GDB
must run through all breakpoints and determine if any new locations
need to be added to the breakpoint.  There's no reason to destroy the
locations of the parent inferior and other inferiors.  We know those
won't change.

In addition to being inneficient, resetting breakpoints of inferiors
that are currently running is problematic, because:

 - some targets can't read memory while the inferior is running.

 - the inferior might exit while we're re-setting its breakpoints,
   which may confuse prologue skipping.

I went through all the places where we call breakpoint_re_set, and it
seems to me that all can be changed to only re-set locations of the
current program space.

The patch that reversed threads order in "info threads" etc. happened
to make gdb.threads/fork-plus-thread.exp expose this problem when
testing on x86/-m32.  The problem was latent and masked out by chance
by the code-cache:

 https://sourceware.org/ml/gdb-patches/2016-01/msg00213.html

Tested on x86-64 F20, native (-m64/-m32) and extended-remote
gdbserver.

Fixes the regression discussed in the url above with --target_board=unix/-m32:

 -FAIL: gdb.threads/fork-plus-threads.exp: detach-on-fork=off: inferior 1 exited
 +PASS: gdb.threads/fork-plus-threads.exp: detach-on-fork=off: inferior 1 exited
 -FAIL: gdb.threads/fork-plus-threads.exp: detach-on-fork=off: no threads left (timeout)
 -FAIL: gdb.threads/fork-plus-threads.exp: detach-on-fork=off: only inferior 1 left (the program exited)
 +PASS: gdb.threads/fork-plus-threads.exp: detach-on-fork=off: no threads left
 +PASS: gdb.threads/fork-plus-threads.exp: detach-on-fork=off: only inferior 1 left

gdb/ChangeLog:
2016-01-19  Pedro Alves  <palves@redhat.com>

	* ax-gdb.c (agent_command_1): Adjust call to decode_line_full.
	* break-catch-throw.c (re_set_exception_catchpoint): Pass the
	current program space down to linespec decoding and breakpoint
	location updating.
	* breakpoint.c (parse_breakpoint_sals): Adjust calls to
	decode_line_full.
	(until_break_command): Adjust calls to decode_line_1.
	(base_breakpoint_decode_location, bkpt_decode_location): Add
	'search_pspace' parameter.  Pass it along.
	(bkpt_probe_create_sals_from_location): Adjust calls to
	parse_probes.
	(tracepoint_decode_location, tracepoint_probe_decode_location)
	(strace_marker_decode_location): Add 'search_pspace' parameter.
	Pass it along.
	(all_locations_are_pending): Rewrite to take a breakpoint and
	program space as arguments instead.
	(hoist_existing_locations): New function.
	(update_breakpoint_locations): Add 'filter_pspace' parameter.  Use
	hoist_existing_locations instead of always removing all locations,
	and adjust to all_locations_are_pending change.
	(location_to_sals): Add 'search_pspace' parameter.  Pass it along.
	Don't disable the breakpoint if there are other locations in
	another program space.
	(breakpoint_re_set_default): Adjust to pass down the current
	program space as filter program space.
	(decode_location_default): Add 'search_pspace' parameter and pass
	it along.
	(prepare_re_set_context): Don't switch program space here.
	(breakpoint_re_set): Use save_current_space_and_thread instead of
	save_current_program_space.
	* breakpoint.h (struct breakpoint_ops) <decode_location>: Add
	'search_pspace' parameter.
	(update_breakpoint_locations): Add 'filter_pspace' parameter.
	* cli/cli-cmds.c (edit_command, list_command): Adjust calls to
	decode_line_1.
	* elfread.c (elf_gnu_ifunc_resolver_return_stop): Pass the current
	program space as filter program space.
	* linespec.c (struct linespec_state) <search_pspace>: New field.
	(create_sals_line_offset, convert_explicit_location_to_sals)
	(parse_linespec): Pass the search program space down.
	(linespec_state_constructor): Add 'search_pspace' parameter.
	Store it.
	(linespec_parser_new): Add 'search_pspace' parameter and pass it
	along.
	(linespec_lex_to_end): Adjust.
	(decode_line_full, decode_line_1): Add 'search_pspace' parameter
	and pass it along.
	(decode_line_with_last_displayed): Adjust.
	(collect_symtabs_from_filename, symtabs_from_filename): New
	'search_pspace' parameter.  Use it.
	(find_function_symbols): Pass the search program space down.
	* linespec.h (decode_line_1, decode_line_full): Add
	'search_pspace' parameter.
	* probe.c (parse_probes_in_pspace): New function, factored out
	from ...
	(parse_probes): ... this.  Add 'search_pspace' parameter and use
	it.
	* probe.h (parse_probes): Add pspace' parameter.
	* python/python.c (gdbpy_decode_line): Adjust.
	* tracepoint.c (scope_info): Adjust.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
[parent not found: <bd0a71fa16f668341a9361c695bc3ca44d27b322@gdb-build>]
* [binutils-gdb] Add PIC and TLS support to the ARC target.
@ 2016-01-19 15:37 sergiodj+buildbot
  2016-01-19 16:06 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-19 15:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 34e967a5f3ac5fd0353731a259e358d462823290 ***

Author: Miranda Cupertino <Cupertino.Miranda@synopsys.com>
Branch: master
Commit: 34e967a5f3ac5fd0353731a259e358d462823290

Add PIC and TLS support to the ARC target.

bfd/ChangeLog:
	* arc-plt.def: New file.
	* arc-plt.h: Likewise.
	* elf32-arc.c (elf_arc_abs_plt0_entry, elf_arc_abs_pltn_entry,
		       elf_arcV2_abs_plt0_entry, elf_arcV2_abs_pltn_entry,
		       elf_arc_pic_plt0_entry, elf_arc_pic_pltn_entry,
		       elf_arcV2_pic_plt0_entry, elf_arcV2_pic_pltn_entry): Remove.
	(name_for_global_symbol): Added.
	(ADD_RELA): Helper to create dynamic relocs.
	(new_got_entry_to_list): Create a new got entry in linked list.
	(symbol_has_entry_of_type): Search for specific type of entry in
	list.
	(is_reloc_for_GOT): return FALSE for any TLS related relocs.
	(is_reloc_for_TLS, arc_elf_set_private_flags)
	(arc_elf_print_private_bfd_data, arc_elf_copy_private_bfd_data)
	(arc_elf_merge_private_bfd_data): New functions.
	(debug_arc_reloc): Cleaned debug info printing.
	(PDATA reloc): Changed not to perform address alignment.
	(reverse_me): Added. Fix for ARC_32 relocs.
	(arc_do_relocation): Return bfd_reloc_of when no relocation should
	occur.
	(arc_get_local_got_ents): Renamed from arc_get_local_got_offsets.
	Changed function to access an array of list of GOT entries instead
	of just an array of offsets.
	(elf_arc_relocate_section): Added support for PIC and TLS related relocations.
	(elf_arc_check_relocs): Likewise.
	(elf_arc_adjust_dynamic_symbol, elf_arc_finish_dynamic_symbol,
	(elf_arc_finish_dynamic_sections): Likewise
	(arc_create_dynamic_sections): Modified conditions to create
	dynamic sections.
	(ADD_SYMBOL_REF_SEC_AND_RELOC): New macro.
	(plt_do_relocs_for_symbol, relocate_plt_for_symbol)
	(relocate_plt_for_entry): Changed to support new way to define PLT
	related code.
	(add_symbol_to_plt): Likewise.
	(arc_elf_link_hash_table_create): New function.

include/ChangeLog:
	* elf/arc-reloc.def (ARC_32, ARC_GOTPC, ARC_TLS_GD_GOT)
	(ARC_TLS_IE_GOT, ARC_TLS_DTPOFF, ARC_TLS_DTPOFF_S9, ARC_TLS_LE_S9)
	(ARC_TLS_LE_32): Fixed formula.
	(ARC_TLS_GD_LD): Use new special function.
	* opcode/arc-func.h: Changed all the replacement
	functions to clear the patching bits before doing an or it with the value
	argument.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix detection of "r_fs" and "r_gs" on FreeBSD.
@ 2016-01-19 15:50 sergiodj+buildbot
  2016-01-19 17:07 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-19 15:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a6e69c1f1de84549d99792031dd05d5ba70bd8a5 ***

Author: John Baldwin <jhb@FreeBSD.org>
Branch: master
Commit: a6e69c1f1de84549d99792031dd05d5ba70bd8a5

Fix detection of "r_fs" and "r_gs" on FreeBSD.

Include <sys/types.h> as a prerequisite for <machine/reg.h> when checking
for the r_fs and r_gs members in struct reg.  Note that the previous test
for <machine/reg.h> already includes <sys/types.h> as a prerequisite.

gdb/ChangeLog:

	* configure.ac: Include <sys/types.h when checking for "r_fs" in
	"struct reg".
	* configure: Regenerate.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] testsuite: Make check-parallel return non-zero if a test failed
@ 2016-01-19 15:58 sergiodj+buildbot
  2016-01-19 18:08 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-19 15:58 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bef95aacb8501edb086381b3d413485d732f00f3 ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: bef95aacb8501edb086381b3d413485d732f00f3

testsuite: Make check-parallel return non-zero if a test failed

When using the check-parallel target, the return code of make is always 0,
regardless of test results.  This patch makes it return the same code as
the "make do-check-parallel" sub-command.  So if there is a FAIL somewhere,
non-zero will be returned by make.

For the sake of example, I introduced a failure in gdb.base/break.exp.

  $ make check-single TESTS="gdb.base/break.exp gdb.python/py-value.exp" && echo 'Success :D' || echo 'Fail :('
  ...
  FAIL: gdb.base/break.exp: allo
  ...
  Fail :(

I think the parallel run should do the same.  Currently:

  $ make check-parallel TESTS="gdb.base/break.exp gdb.python/py-value.exp" && echo 'Success :D' || echo 'Fail :('
  ...
  FAIL: gdb.base/break.exp: allo
  ...
  Success :D

And with the patch (no big surprises there):

  $ make check-parallel TESTS="gdb.base/break.exp gdb.python/py-value.exp" && echo 'Success :D' || echo 'Fail :('
  ...
  FAIL: gdb.base/break.exp: allo
  ...
  Fail :(

What do you think?

gdb/testsuite/ChangeLog:

	* Makefile.in (check-parallel): Propagate return code from make
	do-check-parallel.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] testsuite: Add --status to runtest invocation
@ 2016-01-19 16:07 sergiodj+buildbot
  2016-01-19 19:08 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-19 16:07 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 10eadbcc2866f11bd93ef379c76524521abdc218 ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: 10eadbcc2866f11bd93ef379c76524521abdc218

testsuite: Add --status to runtest invocation

By default, if a test driver (a test .exp) ends with an uncaught
error/exception, the runtest command will still have a return code of 0
(success).  However, if a test (or the environment) is broken and does
not work properly, it should be considered as failed so that we can
notice it and fix it.

Passing the --status flag to runtest will make it return an error if one
of the test it runs ends up with an uncaught error.

gdb/testsuite/ChangeLog:

	* Makefile.in (check-single): Pass --status to runtest.
	(check/%.exp): Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] testsuite: Factor out --status in DO_RUNTEST
@ 2016-01-19 16:35 sergiodj+buildbot
  2016-01-19 20:09 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-19 16:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 41d1845edace3cf5dabd0aa7fa376b801fd5f675 ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: 41d1845edace3cf5dabd0aa7fa376b801fd5f675

testsuite: Factor out --status in DO_RUNTEST

gdb/testsuite/ChangeLog:

	* Makefile.in (DO_RUNTEST): Add --status and update usages.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Add support to readelf for reading FreeBSD ELF core notes.
@ 2016-01-19 17:09 sergiodj+buildbot
  2016-01-19 22:10 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-19 17:09 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f4ddf30f1108b2c0b3eee5677c912383ac903256 ***

Author: John Baldwin <jhb@FreeBSD.org>
Branch: master
Commit: f4ddf30f1108b2c0b3eee5677c912383ac903256

Add support to readelf for reading FreeBSD ELF core notes.

binutils/ChangeLog:

	* readelf.c (get_freebsd_elfcore_note_type): New
	(process_note): Add support for FreeBSD core notes.

include/ChangeLog:

	* elf/common.h (NT_FREEBSD_THRMISC): Define.
	(NT_FREEBSD_PROCSTAT_PROC): Define.
	(NT_FREEBSD_PROCSTAT_FILES): Define.
	(NT_FREEBSD_PROCSTAT_VMMAP): Define.
	(NT_FREEBSD_PROCSTAT_GROUPS): Define.
	(NT_FREEBSD_PROCSTAT_UMASK): Define.
	(NT_FREEBSD_PROCSTAT_RLIMIT): Define.
	(NT_FREEBSD_PROCSTAT_OSREL): Define.
	(NT_FREEBSD_PROCSTAT_PSSTRINGS): Define.
	(NT_FREEBSD_PROCSTAT_AUXV): Define.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Add a pseudosection for the NT_FREEBSD_THRMISC note.
@ 2016-01-19 17:18 sergiodj+buildbot
  2016-01-19 23:10 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-19 17:18 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5b2c414df12bb61ab1e40099b92fc8f00983b930 ***

Author: John Baldwin <jhb@FreeBSD.org>
Branch: master
Commit: 5b2c414df12bb61ab1e40099b92fc8f00983b930

Add a pseudosection for the NT_FREEBSD_THRMISC note.

bfd/ChangeLog:

	* elf.c (elfcore_grok_note): Recognize NT_FREEBSD_THRMISC notes.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Add support for extracting thread names from cores.
@ 2016-01-19 17:26 sergiodj+buildbot
  2016-01-20  0:12 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-19 17:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4dfc5dbc4e1b267d440dd515a42fe6fd96a8d860 ***

Author: John Baldwin <jhb@FreeBSD.org>
Branch: master
Commit: 4dfc5dbc4e1b267d440dd515a42fe6fd96a8d860

Add support for extracting thread names from cores.

Add a new gdbarch method to extract a thread name from a core for a
given thread.  Use this new method in core_thread_name to implement the
to_thread_name target op.

gdb/ChangeLog:

	* corelow.c (core_thread_name): New function.
	(init_core_ops): Use "core_thread_name" for the "to_thread_name"
	target op.
	* gdbarch.sh (core_thread_name): New gdbarch callback.
	* gdbarch.h: Re-generate.
	* gdbarch.c: Re-generate.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Display per-thread information for threads in FreeBSD cores.
@ 2016-01-19 17:34 sergiodj+buildbot
  2016-01-20  1:14 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-19 17:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 791174281c341539fab650bd934cc0060b7c9720 ***

Author: John Baldwin <jhb@FreeBSD.org>
Branch: master
Commit: 791174281c341539fab650bd934cc0060b7c9720

Display per-thread information for threads in FreeBSD cores.

Display the LWP ID of each thread in a FreeBSD core.  Extract thread
names from the per-thread THRMISC note.

gdb/ChangeLog:

	* fbsd_tdep.c (fbsd_core_pid_to_str): New function.
	(fbsd_core_thread_name): New function.
	(fbsd_init_abi): Add "core_pid_to_str" gdbarch method.
	Add "core_thread_name" gdbarch method.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Dump register notes for each thread when generating a FreeBSD core.
@ 2016-01-19 18:00 sergiodj+buildbot
  2016-01-20  8:04 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-19 18:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 20a0aab3ed0f4bb5c304e560751b09b7b82a3e65 ***

Author: John Baldwin <jhb@FreeBSD.org>
Branch: master
Commit: 20a0aab3ed0f4bb5c304e560751b09b7b82a3e65

Dump register notes for each thread when generating a FreeBSD core.

gdb/ChangeLog:

	* fbsd-tdep.c (find_stop_signal): Remove.
	(struct fbsd_collect_regset_section_cb) <lwp>: New field.
	<stop_signal>: New field.
	<abort_iteration>: New field.
	(fbsd_collect_regset_section_cb): Use new fields.
	(fbsd_collect_thread_registers): New function.
	(struct fbsd_corefile_thread_data): New structure.
	(fbsd_corefile_thread): New function.
	(fbsd_make_corefile_notes): Use new function to dump notes for each
	non-exited thread in a process.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] minor reformatting in printcmd.c::print_scalar_formatted
@ 2016-01-20  4:14 sergiodj+buildbot
  2016-01-20 10:46 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-20  4:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT be56871ee8f65c51b9eee611532ed036a71a72e0 ***

Author: Joel Brobecker <brobecker@adacore.com>
Branch: master
Commit: be56871ee8f65c51b9eee611532ed036a71a72e0

minor reformatting in printcmd.c::print_scalar_formatted

(GNU Coding Standard...)

gdb/ChangeLog:

        * printcmd.c (print_scalar_formatted): move binary operator from
        end of line to beginning of next line.  Adjust formatting
        accordingly.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Add support for an ARM specific 'y' section attribute flag to mark the section as NOREAD.
@ 2016-01-20 13:05 sergiodj+buildbot
  2016-01-20 13:43 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-20 13:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 91f68a68f992e3f6c3da26c616b5257230bd1eec ***

Author: Mickael Guene <mickael.guene@st.com>
Branch: master
Commit: 91f68a68f992e3f6c3da26c616b5257230bd1eec

Add support for an ARM specific 'y' section attribute flag to mark the section as NOREAD.

bfd/ChangeLog:
      * elf32-arm.c ((elf32_arm_special_sections): Remove catch of noread
      section using '.text.noread' pattern.

gas/ChangeLog:
      * config/obj-elf.c (obj_elf_change_section) : Allow arm section with
      SHF_ARM_NOREAD section flag.
      * config/tc-arm.h (md_elf_section_letter) : Implement this hook to
      handle letter 'y'.
     (arm_elf_section_letter) : Declare it.
      * config/tc-arm.c (arm_elf_section_letter): Handle letter 'y' to set
      SHF_ARM_NOREAD section flag.
      * doc/c-arm.texi (ARM section attribute 'y'): Document it.

gas/testsuite/ChangeLog:
      * gas/arm/section-execute-only.s: New test case.
      * gas/arm/section-execute-only.d: Expected output.

ld/testsuite/ChangeLog:
      * ld-arm/thumb1-noread-not-present-mixing-two-section.s: Add 'y'
      attribute usage.
      * ld-arm/thumb1-noread-present-one-section.s: Likewise.
      * ld-arm/thumb1-noread-present-two-section.s: Likewise.
      * ld-arm/thumb1-input-section-flag-match.s: Likewise.

binutils/ChangeLog:
      * readelf.c (get_elf_section_flags): Display y letter for section
      with SHF_ARM_NOREAD section flag in readelf section output.
      (process_section_headers): Add y letter in readelf section output
      key mapping for ARM architecture.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [AArch64] Reject invalid immediate operands to MSR UAO
@ 2016-01-20 14:43 sergiodj+buildbot
  2016-01-20 15:19 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-20 14:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0bff6e2d6942690d81ce1f33728de07835b0f5b7 ***

Author: Matthew Wahab <matthew.wahab@arm.com>
Branch: master
Commit: 0bff6e2d6942690d81ce1f33728de07835b0f5b7

[AArch64] Reject invalid immediate operands to MSR UAO

In the instruction to write to the ARMv8.2 PSTATE field UAO,
MSR UAO, #<imm>, the immediate should be either 0 or 1 but GAS accepts
any unsigned 4-bit integer.

This patch implements the constraint on the immediate, generating an
error if the immediate operand is invalid, and adds tests for the
illegal forms.

opcodes/
2016-01-20  Matthew Wahab  <matthew.wahab@arm.com>

	* aarch64-opc.c (operand_general_constraint_met_p): Check validity
	of MSR UAO immediate operand.

gas/
2016-01-20  Matthew Wahab  <matthew.wahab@arm.com>

	* testsuite/gas/aarch64/armv8_2-a-illegal.d: New.
	* testsuite/gas/aarch64/armv8_2-a-illegal.l: New.
	* testsuite/gas/aarch64/armv8_2-a-illegal.s: New.

Change-Id: Ibdec4967c00b1ef3be9dbc43d23b2c70d1a0b28c


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix missing IPA lib in tspeed.exp in some configurations.
@ 2016-01-20 17:40 sergiodj+buildbot
  2016-01-20 18:23 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-20 17:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9df22175e153e1a8784afb85fc24983adf346171 ***

Author: Antoine Tremblay <antoine.tremblay@ericsson.com>
Branch: master
Commit: 9df22175e153e1a8784afb85fc24983adf346171

Fix missing IPA lib in tspeed.exp in some configurations.

On Ubuntu 14.04 the following failure would be seen when running the
tspeed.exp test on a target that supports fast tracepoints like x86_64:

Target returns error code '.In-process agent library not loaded in
process.  Fast and static tracepoints unavailable.'.
(gdb) FAIL: gdb.trace/tspeed.exp: start trace experiment

This is because the default is to link with --as-needed and the
gdb_compile for the test is using the libs argument instead of shlib which
corrects this issue since 6ebea266fd0a7a56c90db3ab6237ff9f6c919747 by
adding -Wl,--no-as-needed.

This patch fixes the issue by passing the lib as the shlib argument to
gdb_compile.

Tested on Ubuntu 14.04 x86_64.

gdb/testsuite/ChangeLog:

	* gdb.trace/tspeed.exp:  Use shlib instead of libs in gdb_compile
	command.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] gnu_vector.exp: Respect `should_kfail' for PR 8549
@ 2016-01-20 18:53 sergiodj+buildbot
  2016-01-20 19:37 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-20 18:53 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fd356fa28834fa3a9f22f9157a568264ad045010 ***

Author: Andreas Arnez <arnez@linux.vnet.ibm.com>
Branch: master
Commit: fd356fa28834fa3a9f22f9157a568264ad045010

gnu_vector.exp: Respect `should_kfail' for PR 8549

The gnu_vector test case yields a new FAIL on s390x:

  FAIL: gdb.base/gnu_vector.exp: verify vector return value

It was introduced by commit 77ae9c1933b50 "gdb.base/gnu_vector.exp:
Don't test output from the inferior".  That commit dropped the special
handling for GDB's inability (on some targets) to set the return value.

This change re-establishes the logic from before, converting the above
FAIL to a KFAIL (PRMS gdb/8549).

gdb/testsuite/ChangeLog:

	* gdb.base/gnu_vector.exp: Re-establish handling for should_kfail
	when GDB can not set the vector return value.  Add more comments
	for clarification.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix sorting of enum values in FlagEnumerationPrinter
@ 2016-01-20 19:03 sergiodj+buildbot
  2016-01-20 20:53 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-20 19:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5f5dfff63f31511db45278f97dc22059325ec4d6 ***

Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: 5f5dfff63f31511db45278f97dc22059325ec4d6

Fix sorting of enum values in FlagEnumerationPrinter

The lambda function used to sort the enumerator list does not work
properly.  This list consists of tuples, (enum label, enum value).  The
key function returns x.enumval.  enumval not being defined for a tuple,
we see this exception in the test log:

  Python Exception <class 'AttributeError'> 'tuple' object has no attribute 'enumval'

The function should return the second item of the tuple, which is the
enumval.

The pretty-printer still worked mostly correctly, except that the
enumeration values were not sorted.  The test still passed because the
enumeration values are already sorted where they are defined.  The test
also passed despite the exception being printed, because the right output
was printed after the exception:

  print (enum flag_enum) (FLAG_1)
  Python Exception <type 'exceptions.AttributeError'> 'tuple' objecthas no attribute 'enumval':M
  $7 = 0x1 [FLAG_1]
  (gdb) PASS: gdb.python/py-pp-maint.exp: print FLAG_1

New in v2:

- Improved test case, I stole Pedro's example directly.  It verifies
  that the sorting of enumerators by value works, by checking that
  printing FOO_MASK appears as FOO_1 | FOO_2 | FOO_3.

  I noticed that I could change the regexps to almost anything and the
  tests would still pass.  I think it was because of the | in there.  I
  made them more robust by using string_to_regexp.  I used curly braces
  { } instead of quoting marks " " for strings, so that I could use
  square brackets [ ] in them without having to escape them all.  I also
  removed the "message" part of the tests, since they are redundant with
  the command, and it's just more maintenance to have to update them.

  Tested with Python 2.7 and 3.5.

gdb/ChangeLog:

	* python/lib/gdb/printing.py (FlagEnumerationPrinter.__call__):
	Fix enumerators sort key function.

gdb/testsuite/ChangeLog:

	* gdb.python/py-pp-maint.exp: Change/add enum flag tests.
	* gdb.python/py-pp-maint.c (enum flag_enum): Use more complex
	enum flag values.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Detect the arm/thumb mode of code SIGRETURN or RT_SIGRETURN returns to
@ 2016-01-21  8:17 sergiodj+buildbot
  2016-01-21  8:48 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-21  8:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f7a6a40dbc279f0a54bdf947077cbad8ad52564c ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: f7a6a40dbc279f0a54bdf947077cbad8ad52564c

Detect the arm/thumb mode of code SIGRETURN or RT_SIGRETURN returns to

This patch fixes the following regression introduced by commit d0e59a68

step^M
39      } /* handler */^M
1: x/i $pc^M
=> 0x8740 <handler+80>: sub     sp, r11, #0^M
(gdb) step^M
^M
Program received signal SIGSEGV, Segmentation fault.^M
setitimer () at ../sysdeps/unix/syscall-template.S:81^M
81      ../sysdeps/unix/syscall-template.S: No such file or directory.^M
1: x/i $pc^M
=> 0xb6eff9c0 <setitimer>:      push    {r7}^M
(gdb) FAIL: gdb.base/sigstep.exp: continue to handler, si+advance in handler, step from handler: leave handler

in my test setting, program is compiled in arm mode, but the glibc
is built in thumb mode, so when we do 'step' to step over syscall
instruction svc for SIGRETURN, GDB should set breakpoint for arm mode
in the program, even though the current program in glibc is in thumb
mode.  Current GDB doesn't consider the case that the mode of program
SIGRETURN goes to can be different from current program mode.

In fact, GDB has taken care of this arm/thumb mode changes already,
see

/* Copy the value of next pc of sigreturn and rt_sigrturn into PC,
   return 1.  In addition, set IS_THUMB depending on whether we
   will return to ARM or Thumb code.  Return 0 if it is not a
   rt_sigreturn/sigreturn syscall.  */
static int
arm_linux_sigreturn_return_addr (struct frame_info *frame,
				 unsigned long svc_number,
				 CORE_ADDR *pc, int *is_thumb)

but in the commit d0e59a68

> -  arm_linux_sigreturn_return_addr (frame, svc_number, &return_addr, &is_thumb);
> +  if (svc_number == ARM_SIGRETURN || svc_number == ARM_RT_SIGRETURN)
> +    next_pc = arm_linux_sigreturn_next_pc (regcache, svc_number);

the IS_THUMB setting is lost, so it is a regression.

gdb:

2016-01-21  Yao Qi  <yao.qi@linaro.org>

	* arm-linux-tdep.c (arm_linux_sigreturn_next_pc): Add parameter
	is_thumb and set it according to CPSR saved on the stack.
	(arm_linux_get_next_pcs_syscall_next_pc): Pass is_thumb to
	arm_linux_sigreturn_next_pc.

gdb/gdbserver:

2016-01-21  Yao Qi  <yao.qi@linaro.org>

	* linux-arm-low.c (arm_sigreturn_next_pc): Add parameter
	is_thumb and set it according to CPSR saved on the stack.
	(get_next_pcs_syscall_next_pc): Pass is_thumb to
	arm_sigreturn_next_pc.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Convert macros in elf-linux-core.h to inline functions
@ 2016-01-21  9:57 sergiodj+buildbot
  2016-01-21 12:18 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-21  9:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT aeb7056972f1b383578204b9151b0ae6d8c1df81 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: aeb7056972f1b383578204b9151b0ae6d8c1df81

Convert macros in elf-linux-core.h to inline functions

Besides changing some macros into inline functions, this removes
redundant memsets and uses bfd_put_* rather than H_PUT_*.

	* elf-linux-core.h (swap_linux_prpsinfo32_out): New function.
	(swap_linux_prpsinfo64_out): New function.
	(LINUX_PRPSINFO32_SWAP_FIELDS): Delete.
	(LINUX_PRPSINFO64_SWAP_FIELDS): Delete.
	* elf.c (elfcore_write_linux_prpsinfo32): Adjust.  Don't memset.
	(elfcore_write_linux_prpsinfo64): Likewise.
	* elf32-ppc.c (swap_ppc_linux_prpsinfo32_out): New function.
	(PPC_LINUX_PRPSINFO32_SWAP_FIELDS): Delete.
	(elfcore_write_ppc_linux_prpsinfo32): Adjust.  Don't memset.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Rename elf-linux-psinfo.h to elf-linux-core.h
@ 2016-01-21 10:09 sergiodj+buildbot
  2016-01-21 11:15 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-21 10:09 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT de64ce13a78669f094d6909fce51d210e2f9d2c0 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: de64ce13a78669f094d6909fce51d210e2f9d2c0

Rename elf-linux-psinfo.h to elf-linux-core.h

Since it will sometime have more than just prpsinfo.  Also,
elf32-ppc.c needlessly includes this header.

	* elf-linux-core.h: Rename from elf-linux-psinfo.h.
	* elf.c: Adjust #include.
	* elf32-ppc.c: Don't #include elf-linux-psinfo.h
	* Makefile.am (SOURCE_HFILES): Update.
	* Makefile.in: Regenerate.
	* po/SRC-PORFILES.in: Regenerate.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [AArch64] Relax long branch veneer insertion for non STT_FUNC symbol
@ 2016-01-21 10:14 sergiodj+buildbot
  2016-01-21 13:19 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-21 10:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2f340668a9a7c00f8813b097b157b07fba8cfa82 ***

Author: Jiong Wang <jiong.wang@arm.com>
Branch: master
Commit: 2f340668a9a7c00f8813b097b157b07fba8cfa82

[AArch64] Relax long branch veneer insertion for non STT_FUNC symbol

  As defined at AArch64 ELF Specification (4.6.7 Call and Jump
  relocations), symbol with type of non STT_FUNC but in different input
  section with relocation place should insert long branch veneer also.

  Meanwhile the current long branch veneer infrastructure havn't considered
  the situation where the branch destination is "sym_value + rela->addend".

  This was OK because we only insert veneer for long call destination is
  STT_FUNC symbol for which the addend is always zero. But as we relax the
  support to other situations by this patch, we need to handle addend be
  non-zero value. For example, for static function, relocation against
  "local symbol" are turned into relocation against "section symbol + offset"
  where there is a valid addend.

  bfd/
	* elfnn-aarch64.c (aarch64_type_of_stub): Allow insert long branch
	veneer for sym_sec != input_sec.
	(elfNN_aarch64_size_stub): Support STT_SECTION symbol.
	(elfNN_aarch64_final_link_relocate): Take rela addend into account when
	calculation destination.

  ld/
	* testsuite/ld-aarch64/farcall-section.d: Delete.
	* testsuite/ld-aarch64/farcall-section.s: Delete.
	* testsuite/ld-aarch64/farcall-b-section.d: New expectation file.
	* testsuite/ld-aarch64/farcall-bl-section.d: Likewise.
	* testsuite/ld-aarch64/farcall-b-section.s: New testcase.
	* testsuite/ld-aarch64/farcall-bl-section.s: Likewise.
	* testsuite/ld-aarch64/aarch64-elf.exp: Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix regression introduced in "break *<EXPR>" by explicit location patches.
@ 2016-01-21 10:33 sergiodj+buildbot
  2016-01-21 14:19 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-21 10:33 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 305e13e67faaf940ce6eb708847a655a0735a651 ***

Author: Joel Brobecker <brobecker@adacore.com>
Branch: master
Commit: 305e13e67faaf940ce6eb708847a655a0735a651

Fix regression introduced in "break *<EXPR>" by explicit location patches.

A relatively recent patch support for explicit locations, and part
of that patch cleaned up the way we parse breakpoint locations.
Unfortunatly, a small regression crept in for "*<EXPR>" breakpoint
locations. In particular, on PIE programs, one can see the issue by
doing the following, with any program:

    (gdb) b *main
    Breakpoint 1 at 0x51a: file hello.c, line 3.
    (gdb) run
    Starting program: /[...]/hello
    Error in re-setting breakpoint 1: Warning:
    Cannot insert breakpoint 1.
    Cannot access memory at address 0x51a

    Warning:
    Cannot insert breakpoint 1.
    Cannot access memory at address 0x51a

Just for the record, this regression was introduced by:

    commit a06efdd6effd149a1d392df8d62824e44872003a
    Date:   Tue Aug 11 17:09:35 2015 -0700
    Subject: Explicit locations: introduce address locations

What happens is that the patch makes the implicit assumption that
the address computed the first time is static, as if it was designed
to only support litteral expressions (Eg. "*0x1234"). This allows
the shortcut of not re-computing the breakpoint location's address
when re-setting breakpoints.

However, this does not work in general, as demonstrated in the example
above.

This patch plugs that hole simply by saving the original expression
used to compute the address as part of the address location, so as
to then re-evaluate that expression during breakpoint re-set.

gdb/ChangeLog:

        * location.h (new_address_location): Add new parameters
        "addr_string" and "addr_string_len".
        (get_address_string_location): Add declaration.
        * location.c (new_address_location): Add new parameters
        "addr_string" and "addr_string_len".  If not NULL, store
        a copy of the addr_string in the new location as well.
        (get_address_string_location): New function.
        (string_to_event_location): Update call to new_address_location.
        * linespec.c (event_location_to_sals) <ADDRESS_LOCATION>:
        Save the event location in the parser's state before
        passing it to convert_address_location_to_sals.
        * breakpoint.c (create_thread_event_breakpoint): Update call
        to new_address_location.
        (init_breakpoint_sal): Get the event location's string, if any,
        and use it to update call to new_address_location.
        * python/py-finishbreakpoint.c (bpfinishpy_init):
        Update call to new_address_location.
        * spu-tdep.c (spu_catch_start): Likewise.

        * config/djgpp/fnchange.lst: Add entries for
        gdb/testsuite/gdb.base/break-fun-addr1.c and
        gdb/testsuite/gdb.base/break-fun-addr2.c.

gdb/testsuite/ChangeLog:

        * gdb.base/break-fun-addr.exp: New file.
        * gdb.base/break-fun-addr1.c: New file.
        * gdb.base/break-fun-addr2.c: New file.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix unexpected failures in the linker testsuite for ARM VxWorks targets.
@ 2016-01-21 11:03 sergiodj+buildbot
  2016-01-21 15:21 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-21 11:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT aebf9be7089c1903581740851ae9ae67ffee2f4b ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: aebf9be7089c1903581740851ae9ae67ffee2f4b

Fix unexpected failures in the linker testsuite for ARM VxWorks targets.

	PR ld/19455
	* elf32-arm.c (elf32_arm_create_dynamic_sections): Set the ELF
	class of the linker stub bfd.
	(elf32_arm_check_relocs): Skip check for pic format after
	processing a vxWorks R_ARM_ABS12 reloc.
	* elflink.c (bfd_elf_final_link): Check for ELFCLASSNONE when
	reporting a class mismatch.

	* testsuite/ld-arm/vxworks1-lib.dd: Update for current
	disassmebler output.
	* testsuite/ld-arm/vxworks1-lib.rd: Likewise.
	* testsuite/ld-arm/vxworks1.dd: Likewise.
	* testsuite/ld-arm/vxworks1.rd: Likewise.
	* testsuite/ld-arm/vxworks1.ld: Set the output format.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] gdb: Respect CXXFLAGS when building with C++ compiler
@ 2016-01-21 11:45 sergiodj+buildbot
  2016-01-21 16:25 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-21 11:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a994041db36c9a6058fe591c7ccd018ed7affc76 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: a994041db36c9a6058fe591c7ccd018ed7affc76

gdb: Respect CXXFLAGS when building with C++ compiler

Currently, even when built with --enable-build-with-cxx, gdb uses
CFLAGS instead of CXXFLAGS.  This commit fixes it.

CXXFLAGS set in the environment when configure was run is now honored
in the generated gdb/Makefile, and you can also override CXXFLAGS in
the command like at make time, with the usual 'make CXXFLAGS="..."'

Objects built with a C compiler (e.g., gnulib) still honor CFLAGS
instead.

gdb/ChangeLog:
2016-01-21  Pedro Alves  <palves@redhat.com>

	* Makefile.in (COMPILER_CFLAGS): New.
	(CXXFLAGS): Get it from configure.
	(INTERNAL_CFLAGS_BASE, INTERNAL_LDFLAGS): Use COMPILER_CFLAGS
	instead of CFLAGS.
	* build-with-cxx.m4 (GDB_AC_BUILD_WITH_CXX): Set and AC_SUBST
	COMPILER_CFLAGS.
	* configure: Regenerate.

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

	* Makefile.in (COMPILER_CFLAGS, CXXFLAGS): New.
	(INTERNAL_CFLAGS_BASE): Use COMPILER_CFLAGS instead of CFLAGS.
	* configure: Regenerate.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix compile time errors building ARC target on a 32-bit host.
@ 2016-01-21 14:04 sergiodj+buildbot
  2016-01-21 18:31 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-21 14:04 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 23a42089156e63bbd2228675e78cdf1ffae63c51 ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: 23a42089156e63bbd2228675e78cdf1ffae63c51

Fix compile time errors building ARC target on a 32-bit host.

	* elf32-arc.c (ADD_RELA): Fix compile time warning errors by
	changing the type of _loc to be bfd_byte *.
	(elf_arc_finish_dynamic_symbol): Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
[parent not found: <f906b857015513af81f94db8e11b1e334c767def@gdb-build>]
* [binutils-gdb] * breakpoint.c (init_breakpoint_sal): Add comment.
@ 2016-01-22  1:15 sergiodj+buildbot
  2016-01-22  3:37 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-22  1:15 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b35a8b2f1f44c6ea48aeb6f7a74de01f6f5016fb ***

Author: Doug Evans <dje@google.com>
Branch: master
Commit: b35a8b2f1f44c6ea48aeb6f7a74de01f6f5016fb

* breakpoint.c (init_breakpoint_sal): Add comment.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [testsuite] Unbuffer the output in gdb.base/multi-forks.c
@ 2016-01-22  9:39 sergiodj+buildbot
  2016-01-22 10:49 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-22  9:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1ac78c044471fa65b952c2e5c47dcf4d0ccf9b79 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 1ac78c044471fa65b952c2e5c47dcf4d0ccf9b79

[testsuite] Unbuffer the output in gdb.base/multi-forks.c

This patch unbuffer the output of the program so that the test harness
can count the number of "done" from output correctly.

gdb/testsuite:

2016-01-22  Yao Qi  <yao.qi@linaro.org>

	PR testsuite/19491
	* gdb.base/multi-forks.c: Include
	../lib/unbuffer_output.c
	(main): Call gdb_unbuffer_output.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
[parent not found: <99e8eb11cfcdde8cba6755ed4613c3cb079dfaa4@gdb-build>]
* [binutils-gdb] Reword the string description of native FreeBSD ptids.
@ 2016-01-22 17:04 sergiodj+buildbot
  2016-01-22 17:35 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-22 17:04 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b2bae2f79b11a87af3dbc2a6ca3c0c4987ecfbba ***

Author: John Baldwin <jhb@FreeBSD.org>
Branch: master
Commit: b2bae2f79b11a87af3dbc2a6ca3c0c4987ecfbba

Reword the string description of native FreeBSD ptids.

The prior format led to confusing messages when threads were created
or added such as "[New process 14757, LWP 100537]".  The new format
reports this as "[New LWP 100434 of process 15652]".

gdb/ChangeLog:

	* fbsd-nat.c (fbsd_pid_to_str): Adjust string format.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] testsuite: Fix PR threads/19422 regression + Guile regression
@ 2016-01-22 20:50 sergiodj+buildbot
  2016-01-22 21:21 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-22 20:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 31d765d3801c63a66312023181edb3af25c03598 ***

Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Branch: master
Commit: 31d765d3801c63a66312023181edb3af25c03598

testsuite: Fix PR threads/19422 regression + Guile regression

The PR threads/19422 patchset added a new regression.

Additionally below it there was already a regression if --with-guile (which is
default if Guile is found) was used.

racy case #1:

(xgdb) PASS: gdb.gdb/selftest.exp: Set xgdb_prompt
^M
Thread 1 "xgdb" received signal SIGINT, Interrupt.^M
0x00007ffff583bfdd in poll () from /lib64/libc.so.6^M
(gdb) FAIL: gdb.gdb/selftest.exp: send ^C to child process
signal SIGINT^M
Continuing with signal SIGINT.^M
^C^M
Thread 1 "xgdb" received signal SIGINT, Interrupt.^M
0x00007ffff5779da0 in sigprocmask () from /lib64/libc.so.6^M
(gdb) PASS: gdb.gdb/selftest.exp: send SIGINT signal to child process
backtrace^M
errstring=errstring@entry=0x7e0e6c "", mask=mask@entry=RETURN_MASK_ALL) at exceptions.c:240^M
errstring=errstring@entry=0x7e0e6c "", mask=mask@entry=RETURN_MASK_ALL) at exceptions.c:240^M
(gdb) PASS: gdb.gdb/selftest.exp: backtrace through signal handler

racy case #2:

(xgdb) PASS: gdb.gdb/selftest.exp: Set xgdb_prompt
^M
Thread 1 "xgdb" received signal SIGINT, Interrupt.^M
0x00007ffff583bfdd in poll () from /lib64/libc.so.6^M
(gdb) FAIL: gdb.gdb/selftest.exp: send ^C to child process
signal SIGINT^M
Continuing with signal SIGINT.^M
^C^M
Thread 2 "xgdb" received signal SIGINT, Interrupt.^M
[Switching to Thread 0x7ffff3b7f700 (LWP 13227)]^M
0x00007ffff6b88b10 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0^M
(gdb) PASS: gdb.gdb/selftest.exp: send SIGINT signal to child process
backtrace^M
(gdb) FAIL: gdb.gdb/selftest.exp: backtrace through signal handler

Pedro Alves:
Not all targets support thread names, and even those that do, not all
use the program name as default thread name -- I think that's only true
for GNU/Linux, actually.  So I think it's best to not expect that, like:
            -re "(Thread .*|Program) received signal SIGINT.*$gdb_prompt $" {

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

	Fix testsuite compatibility with Guile.
	* gdb.gdb/selftest.exp (send ^C to child process): Accept also Thread.
	(thread 1): New test for backtrace through signal handler.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] testsuite: gdb.gdb/selftest.exp: Drop expected Thread number
@ 2016-01-22 21:00 sergiodj+buildbot
  2016-01-22 22:26 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-22 21:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 092127d743462e370fd1156cb746f814a7b46593 ***

Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Branch: master
Commit: 092127d743462e370fd1156cb746f814a7b46593

testsuite: gdb.gdb/selftest.exp: Drop expected Thread number

Pedro Alves:
Looks like you forgot to amend before pushing though -- the version
checked in still had "Thread 1".

gdb/testsuite/ChangeLog
2016-01-22  Jan Kratochvil  <jan.kratochvil@redhat.com>
	    Pedro Alves  <palves@redhat.com>

	Fix testsuite compatibility with Guile.
	* gdb.gdb/selftest.exp (send ^C to child process): Drop expected Thread
	number.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
[parent not found: <cc5fd9abe4980e48e2cc27b0225f3c6ba7c0756b@gdb-build>]
[parent not found: <dc29a1ce6a25233e608f90511e67af3c18e19a98@gdb-build>]
* [binutils-gdb] MIPS/BFD: Correct register index calculation in BZ16_REG
@ 2016-01-24  1:16 sergiodj+buildbot
  2016-01-24  2:02 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-24  1:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e67f83e590b8ce7a9912f665aa559cbc98c05de6 ***

Author: Maciej W. Rozycki <macro@imgtec.com>
Branch: master
Commit: e67f83e590b8ce7a9912f665aa559cbc98c05de6

MIPS/BFD: Correct register index calculation in BZ16_REG

For the 3-bit register encodings of { 0, 1, 2, 3, 4, 5, 6, 7 } return
the 5-bit encodings of { 16, 17, 2, 3, 4, 5, 6, 7 } respectively rather
than { 24, 25, 2, 3, 4, 5, 6, 7 }.

	bfd/
	* elfxx-mips.c (BZ16_REG): Correct calculation.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] MIPS/BFD: Simplify register index calculation in BZ16_REG_FIELD
@ 2016-01-24  1:27 sergiodj+buildbot
  2016-01-24  4:51 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-24  1:27 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT eb6b0cf45d7588eb147d90ce790254309a69613e ***

Author: Maciej W. Rozycki <macro@imgtec.com>
Branch: master
Commit: eb6b0cf45d7588eb147d90ce790254309a69613e

MIPS/BFD: Simplify register index calculation in BZ16_REG_FIELD

Just mask higher bits off, which returns the same set of 3-bit register
encodings of { 0, 1, 2, 3, 4, 5, 6, 7 } for the allowed 5-bit encodings
of { 16, 17, 2, 3, 4, 5, 6, 7 }.  Input has already been validated with
OP16_VALID_REG.

	bfd/
	* elfxx-mips.c (BZ16_REG_FIELD): Simplify calculation.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix memory corruption on Mach-O systems by suppressing a memory tidy up.
@ 2016-01-25  9:41 sergiodj+buildbot
  2016-01-25  9:46 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-25  9:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cf466c2ac5ac55bb9b30b96fbdcad564e8c1ccc8 ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: cf466c2ac5ac55bb9b30b96fbdcad564e8c1ccc8

Fix memory corruption on Mach-O systems by suppressing a memory tidy up.

	PR target/19435
	* mach-o.c (bfd_mach_o_close_and_cleanup): Suppress code to free
	dsym filename buffer.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Add missing end-of-comment marker to previous delta. (Doh!)
@ 2016-01-25  9:54 sergiodj+buildbot
  2016-01-25 10:26 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-25  9:54 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c244074cb684302be1378a072b33cdb8dd0dff1f ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: c244074cb684302be1378a072b33cdb8dd0dff1f

Add missing end-of-comment marker to previous delta.  (Doh!)


^ permalink raw reply	[flat|nested] 2113+ messages in thread
[parent not found: <45f3854667c659ab053f51f96e1923f36e6e20ba@gdb-build>]
* [binutils-gdb] Move foreach_with_prefix to lib/gdb.exp
@ 2016-01-25 13:32 sergiodj+buildbot
  2016-01-25 14:06 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-25 13:32 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f1da4b11eef6dba04a1cfa579c6ba313718105b8 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: f1da4b11eef6dba04a1cfa579c6ba313718105b8

Move foreach_with_prefix to lib/gdb.exp

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

	* gdb.base/step-sw-breakpoint-adjust-pc.exp (foreach_with_prefix):
	Delete, moved to lib/gdb.exp.
	* gdb.threads/forking-threads-plus-breakpoint.exp
	(foreach_with_prefix): Likewise.
	* gdb.threads/process-dies-while-handling-bp.exp
	(foreach_with_prefix): Likewise.
	* lib/gdb.exp (foreach_with_prefix): New procedure.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix PR 19461: strange "info thread" behavior in non-stop
@ 2016-01-25 13:48 sergiodj+buildbot
  2016-01-25 16:14 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-25 13:48 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a2077e254098828614ef6621cf8df28185e711d0 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: a2077e254098828614ef6621cf8df28185e711d0

Fix PR 19461: strange "info thread" behavior in non-stop

If you have "set follow-fork child" set, then if you do "info threads"
right after a fork, and before the child reports any other event to
GDB core, you'll see:

(gdb) info threads
  Id   Target Id         Frame
* 1.1  Thread 0x7ffff7fc1740 (LWP 31875) "fork-plus-threa" (running)
  2.1  process 31879 "fork-plus-threa" Selected thread is running.
(gdb)

The "Selected thread is running." bit is a bogus error.  That was GDB
trying to fetch the current frame of thread 2.1, because the external
runnning state is "stopped", and then throwing an error because the
thread is actually running.

This actually affects all-stop + schedule-multiple as well.

The problem here is that on a fork event, GDB doesn't update the
external parent/child running states.

New comprehensive test included.  The "kill inferior 1" / "kill
inferior 2" bits also trip on PR gdb/19494 (hang killing unfollowed
fork children), which was fixed by the previous patch.

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

	PR threads/19461
	* infrun.c (handle_inferior_event_1) <fork/vfork>: Update
	parent/child running states.

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

	PR threads/19461
	* gdb.base/fork-running-state.c: New file.
	* gdb.base/fork-running-state.exp: New file.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] ARC/BFD: Fix a build error from `index' shadowing a global declaration
@ 2016-01-25 16:18 sergiodj+buildbot
  2016-01-25 18:24 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-25 16:18 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 840855c5edfb840a97fb063fd8f44a7e9e537b87 ***

Author: Maciej W. Rozycki <macro@imgtec.com>
Branch: master
Commit: 840855c5edfb840a97fb063fd8f44a7e9e537b87

ARC/BFD: Fix a build error from `index' shadowing a global declaration

	bfd/
	* elf32-arc.c (elf_arc_finish_dynamic_symbol): Rename `index' to
	`dynindx'.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Remove new_thread_notify and dead_thread_notify
@ 2016-01-25 16:27 sergiodj+buildbot
  2016-01-25 19:29 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-25 16:27 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a0f8e08a3c357ae24d3244940e1c6b405a0c17cc ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: a0f8e08a3c357ae24d3244940e1c6b405a0c17cc

Remove new_thread_notify and dead_thread_notify

They were added by

  PATCH: Multithreaded debugging for gdbserver
  https://sourceware.org/ml/gdb-patches/2002-06/msg00157.html

but as a no-op, and the last usage of them was removed by

  [gdbserver/RFC/RFA] Implement multiprocess extensions, add linux multiproces support.
  https://sourceware.org/ml/gdb-patches/2009-03/msg00667.html

This patch is to remove them.

gdb/gdbserver:

2016-01-25  Yao Qi  <yao.qi@linaro.org>

	* remote-utils.c (new_thread_notify): Remove.
	(dead_thread_notify): Likewise.
	* remote-utils.h (new_thread_notify): Remove declaration.
	(dead_thread_notify): Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
[parent not found: <a579cd9aa8c57c8a54833f26452a1afef38e5d20@gdb-build>]
* [binutils-gdb] [GDBserver] Check input interrupt after reading in a packet
@ 2016-01-26 14:03 sergiodj+buildbot
  2016-01-26 14:36 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-26 14:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 18879fef1741464e522624bcc529048400453e0d ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 18879fef1741464e522624bcc529048400453e0d

[GDBserver] Check input interrupt after reading in a packet

GDBserver may read some packet together with '\003' in one go.  We've
already checked '\003' first when reading packet by my patch,

  Check input interrupt first when reading packet
  https://sourceware.org/ml/gdb-patches/2016-01/msg00057.html

but if we don't check '\003' *after* each packet, the interrupt will
be processed next time GDBserver reads from the buffer, so that the
interrupt isn't processed in time.  For example, GDB sends vCont;c and
interrupt (see gdb.base/interrupt-noterm.exp), we'll resume the
inferior and wait once packet vCont;c is seen.  If we don't check the
interrupt character after vCont;c packet, interrupt character will stay
in the buffer unattended until GDBserver returns from the wait, which
may take a while.  Note that since we've read '\003' from file
descriptor, SIGIO signal handler input_interrupt doesn't help either.

This issue can be exposed by hacking the end of getpkt like
@@ -1041,6 +1050,9 @@ getpkt (char *buf)
        }
     }

+  if (readchar_bufcnt > 0)
+    gdb_assert (*readchar_bufp != '\003');
+
   return bp - buf;
 }

and this can trigger internal error,
(gdb) PASS: gdb.base/interrupt-noterm.exp: interrupt
Remote connection closed^M
(gdb) FAIL: gdb.base/interrupt-noterm.exp: inferior received SIGINT
Remote debugging from host 10.2.206.40^M
/home/yao/SourceCode/gnu/gdb/git/gdb/gdbserver/remote-utils.c:1054: A problem internal to GDBserver has been detected.^M
getpkt: Assertion `*readchar_bufp != '\003'' failed.^M

This patch is to peek the buffer, if it is '\003', consume it and call
*the_target->request_interrupt.

gdb/gdbserver:

2016-01-26  Yao Qi  <yao.qi@linaro.org>

	* remote-utils.c (getpkt): If the buffer isn't empty, and the
	first character is '\003', call *the_target->request_interrupt.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [GDBserver] Block and unblock SIGIO
@ 2016-01-26 14:13 sergiodj+buildbot
  2016-01-26 15:42 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-26 14:13 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8b2073398477b33d425b0570236fe4e4222fe2c4 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 8b2073398477b33d425b0570236fe4e4222fe2c4

[GDBserver] Block and unblock SIGIO

Nowadays, GDBserver disables async io (by ignoring SIGIO) when process
a serial event, and enables async io (by installing signal handler) when
resume the inferior and wait.  GDBserver may miss SIGIO (by interrupt)
and doesn't process SIGIO in time, which is shown by
gdb.base/interrupt-noterm.exp.  In the test, GDB sends "continue &" and
then "interrupt".  if '\003' arrives at a period between GDBserver
receives vCont;c and enables async io, SIGIO is ignored because signal
handler isn't installed.  GDBserver waits for the inferior and can not
notice '\003' until it returns from wait.

This patch changes the code to install SIGIO handler early, but block
and unblock SIGIO as needed.  In this way, we don't remove SIGIO
handler, so SIGIO can't be ignored.  However, GDBserver needs to
remove the signal handler when connection is closed.

gdb/gdbserver:

2016-01-26  Yao Qi  <yao.qi@linaro.org>

	* remote-utils.c (remote_close) [!USE_WIN32API]: Ignore SIGIO.
	(unblock_async_io): Rename to ...
	(block_unblock_async_io): ... it.  New function.
	(enable_async_io): Don't install SIGIO handler.  Unblock it
	instead.
	(disable_async_io): Don't ignore SIGIO.  Block it instead.
	(initialize_async_io): Install SIGIO handler.  Don't call
	unblock_async_io.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [GDBserver] Use regcache_read_pc in install_software_single_step_breakpoints
@ 2016-01-26 14:40 sergiodj+buildbot
  2016-01-26 16:47 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-26 14:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d80209703ec2fc85e0a4b3d4d23e7ed448987aca ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: d80209703ec2fc85e0a4b3d4d23e7ed448987aca

[GDBserver] Use regcache_read_pc in install_software_single_step_breakpoints

In install_software_single_step_breakpoints, we've got the regcache
of current_thread, so we don't have to bother get_pc to get pc,
instead we can get pc from regcache directly.  Note that the callers
of install_software_single_step_breakpoints have already switched
current_thread to LWP.

Since the pc is got from regcache_read_pc, in the next patch, we can
get pc inside the implementation of *the_low_target.get_next_pcs and
stop passing pc to *the_low_target.get_next_pcs.

gdb/gdbserver:

2016-01-26  Yao Qi  <yao.qi@linaro.org>

	* linux-low.c (install_software_single_step_breakpoints): Call
	regcache_read_pc instead of get_pc.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Remove argument pc in get_next_pcs
@ 2016-01-26 14:48 sergiodj+buildbot
  2016-01-26 17:57 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-26 14:48 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4d18591be953e2faeaaa280484d375fe05857770 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 4d18591be953e2faeaaa280484d375fe05857770

Remove argument pc in get_next_pcs

Nowadays, get_next_pcs in linux_target_ops has two parameters PC
and REGCACHE.  Parameter PC looks redundant because it can be go
from REGCACHE.  The patch is to remove PC from the arguments for
various functions.

gdb:

2016-01-26  Yao Qi  <yao.qi@linaro.org>

	* arch/arm-get-next-pcs.c (thumb_deal_with_atomic_sequence_raw):
	Remove argument pc.  Get pc by regcache_read_pc.  Callers updated.
	(arm_deal_with_atomic_sequence_raw): Likewise.
	(thumb_get_next_pcs_raw): Likewise.
	(arm_get_next_pcs_raw): Likewise.
	(arm_get_next_pcs): Remove argument pc.  Callers updated.
	* arch/arm-get-next-pcs.h (arm_get_next_pcs): Update declaration.

gdb/gdbserver:

2016-01-26  Yao Qi  <yao.qi@linaro.org>

	* linux-arm-low.c (arm_gdbserver_get_next_pcs): Remove argument pc.
	* linux-low.c (install_software_single_step_breakpoints): Don't
	call regcache_read_pc.
	* linux-low.h (struct linux_target_ops) <get_next_pcs>: Remove
	argument pc.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix function comments
@ 2016-01-26 21:41 sergiodj+buildbot
  2016-01-26 22:13 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-26 21:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 41548caa9b7ffba43e856bd288b98cc1ab8c3e8f ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: 41548caa9b7ffba43e856bd288b98cc1ab8c3e8f

Fix function comments

Two obvious fixes.

gdb/ChangeLog:

	* common/common-utils.c (skip_spaces): Fix comment.
	(skip_to_space_const): Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] rx: Treat scalars larger than 8 bytes as aggregates in rx_push_dummy_call.
@ 2016-01-27 19:48 sergiodj+buildbot
  2016-01-27 20:25 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-27 19:48 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 94715c179098ab86bf188fae4a32e2283c5f173f ***

Author: Kevin Buettner <kevinb@redhat.com>
Branch: master
Commit: 94715c179098ab86bf188fae4a32e2283c5f173f

rx: Treat scalars larger than 8 bytes as aggregates in rx_push_dummy_call.

This patch fixes the following failures (which are also GDB internal errors)
for the -m64bit-doubles multilib:

FAIL: gdb.base/callfuncs.exp: p t_double_complex_values(dc1, dc2) (GDB internal error)
FAIL: gdb.base/callfuncs.exp: p t_double_complex_values(dc3, dc4) (GDB internal error)
FAIL: gdb.base/callfuncs.exp: p t_double_complex_many_args(dc1, dc2, dc3, dc4, dc1, dc2, dc3, dc4, dc1, dc2, dc3, dc4, dc1, dc2, dc3, dc4) (GDB internal error)
FAIL: gdb.base/callfuncs.exp: p t_double_complex_many_args(dc1, dc1, dc1, dc1, dc1, dc1, dc1, dc1, dc1, dc1, dc1, dc1, dc1, dc1, dc1, dc1) (GDB internal error)
FAIL: gdb.base/callfuncs.exp: p t_long_double_complex_values(ldc1, ldc2) (GDB internal error)
FAIL: gdb.base/callfuncs.exp: p t_long_double_complex_values(ldc3, ldc4) (GDB internal error)
FAIL: gdb.base/callfuncs.exp: p t_long_double_complex_many_args(ldc1, ldc2, ldc3, ldc4, ldc1, ldc2, ldc3, ldc4, ldc1, ldc2, ldc3, ldc4, ldc1, ldc2, ldc3, ldc4) (GDB internal error)
FAIL: gdb.base/callfuncs.exp: p t_long_double_complex_many_args(ldc1, ldc1, ldc1, ldc1, ldc1, ldc1, ldc1,ldc1, ldc1, ldc1, ldc1, ldc1, ldc1, ldc1, ldc1, ldc1) (GDB internal error)
FAIL: gdb.base/callfuncs.exp: noproto: p t_double_complex_values(dc1, dc2) (GDB internal error)
FAIL: gdb.base/callfuncs.exp: noproto: p t_double_complex_values(dc3, dc4) (GDB internal error)
FAIL: gdb.base/callfuncs.exp: noproto: p t_double_complex_many_args(dc1, dc2, dc3, dc4, dc1, dc2, dc3, dc4, dc1, dc2, dc3, dc4, dc1, dc2, dc3, dc4) (GDB internal error)
FAIL: gdb.base/callfuncs.exp: noproto: p t_double_complex_many_args(dc1, dc1, dc1, dc1, dc1, dc1, dc1, dc1, dc1, dc1, dc1, dc1, dc1, dc1, dc1, dc1) (GDB internal error)
FAIL: gdb.base/callfuncs.exp: noproto: p t_long_double_complex_values(ldc1, ldc2) (GDB internal error)
FAIL: gdb.base/callfuncs.exp: noproto: p t_long_double_complex_values(ldc3, ldc4) (GDB internal error)
FAIL: gdb.base/callfuncs.exp: noproto: p t_long_double_complex_many_args(ldc1, ldc2, ldc3, ldc4, ldc1, ldc2, ldc3, ldc4, ldc1, ldc2, ldc3, ldc4, ldc1, ldc2, ldc3, ldc4) (GDB internal error)
FAIL: gdb.base/callfuncs.exp: noproto: p t_long_double_complex_many_args(ldc1, ldc1, ldc1, ldc1, ldc1, ldc1, ldc1,ldc1, ldc1, ldc1, ldc1, ldc1, ldc1, ldc1, ldc1, ldc1) (GDB internal error)
FAIL: gdb.base/varargs.exp: print find_max_double_real(4, dc1, dc2, dc3, dc4) (GDB internal error)
FAIL: gdb.base/varargs.exp: print find_max_long_double_real(4, ldc1, ldc2, ldc3, ldc4) (GDB internal error)

The assertion failure which is tripped is:

		  gdb_assert (arg_size <= 4);

While it may seem that the patch ought to disallow scalars larger than
4, scalars of size 8 are explicitly handled by the code elsewhere.

This came up because gcc has a complex type that is 16 bytes in length
when 64-bit doubles are used.

gdb/ChangeLog:

	* rx-tdep.c (rx_push_dummy_call): Treat scalars larger than 8
	bytes as aggregates.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix GDB crash in dprintf.exp
@ 2016-01-28 14:27 sergiodj+buildbot
  2016-01-28 15:00 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-28 14:27 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4a6a1ed4a113d386b131938bbc7d66e7b495e73f ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 4a6a1ed4a113d386b131938bbc7d66e7b495e73f

Fix GDB crash in dprintf.exp

I see GDB crashes in dprintf.exp on aarch64-linux testing,

(gdb) PASS: gdb.base/dprintf.exp: agent: break 29
set dprintf-style agent^M
(gdb) PASS: gdb.base/dprintf.exp: agent: set dprintf style to agent
continue^M
Continuing.
ASAN:SIGSEGV
=================================================================
==22475==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000008 (pc 0x000000494820 sp 0x7fff389b83a0 bp 0x62d000082417 T0)
    #0 0x49481f in remote_add_target_side_commands /home/yao/SourceCode/gnu/gdb/git/gdb/remote.c:9190^M
    #1 0x49e576 in remote_add_target_side_commands /home/yao/SourceCode/gnu/gdb/git/gdb/remote.c:9174^M
    #2 0x49e576 in remote_insert_breakpoint /home/yao/SourceCode/gnu/gdb/git/gdb/remote.c:9240^M
    #3 0x5278b7 in insert_bp_location /home/yao/SourceCode/gnu/gdb/git/gdb/breakpoint.c:2734^M
    #4 0x52ac09 in insert_breakpoint_locations /home/yao/SourceCode/gnu/gdb/git/gdb/breakpoint.c:3159^M
    #5 0x52ac09 in update_global_location_list /home/yao/SourceCode/gnu/gdb/git/gdb/breakpoint.c:12686

the root cause of this problem in this case is about linespec and
symtab which produces additional incorrect location and a NULL is added to
bp_tgt->tcommands.  I posted a patch
https://sourceware.org/ml/gdb-patches/2015-12/msg00321.html to fix it
in linespec (the fix causes regression), but GDB still shouldn't add
NULL into bp_tgt->tcommands.  The logic of build_target_command_list
looks odd to me.  If we get something wrong in parse_cmd_to_aexpr (it
returns NULL), we shouldn't continue, instead we should set flag
null_command_or_parse_error.  This is what this patch does.  In the
meantime, we find build_target_condition_list has the same problem, so
fix it too.

gdb:

2016-01-28  Yao Qi  <yao.qi@linaro.org>

	* breakpoint.c (build_target_command_list): Don't call continue
	if aexpr is NULL.
	(build_target_condition_list): Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [testsuite] Fix tiemout fail in gdb.fortran/vla-value.exp
@ 2016-01-28 14:39 sergiodj+buildbot
  2016-01-28 16:06 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-28 14:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7fe8399de97e50f631ce28ceb42515862a927556 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 7fe8399de97e50f631ce28ceb42515862a927556

[testsuite] Fix tiemout fail in gdb.fortran/vla-value.exp

In vla.f90, this single line of source is compiled to many instructions,

  vla2(:, :, :) = 1311                ! vla2-allocated

it is quite slow (about several minutes in my testing) to step over this
source line without range stepping.  This patch is to increase the timeout
value by 15 times, which is a magic number to make sure timeout disappears
in my testing with a slow arm-linux board.

gdb/testsuite:

2016-01-28  Yao Qi  <yao.qi@linaro.org>

	* gdb.fortran/vla-value.exp: Wrap test with with_timeout_factor.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Add rawmemchr to imported gnulib modules
@ 2016-01-28 19:00 sergiodj+buildbot
  2016-01-28 19:32 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-28 19:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 56e374a6bcc87f7ac8aeb09887628a3286908545 ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: 56e374a6bcc87f7ac8aeb09887628a3286908545

Add rawmemchr to imported gnulib modules

rawmemchr is a dependency of strchrnul, so it should be explicitly
listed.

gdb/ChangeLog:

	* gnulib/import/Makefile.am: Regenerate.
	* gnulib/import/Makefile.in: Regenerate.
	* gnulib/import/m4/gnulib-cache.m4: Regenerate.
	* gnulib/update-gnulib.sh (IMPORTED_GNULIB_MODULES): Add rawmemchr.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Sync libiberty with GCC.
@ 2016-01-28 21:00 sergiodj+buildbot
  2016-01-28 21:31 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-28 21:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9d98de835cb018419e0ef97db37fcf9061247750 ***

Author: Iain Buclaw <ibuclaw@gdcproject.org>
Branch: master
Commit: 9d98de835cb018419e0ef97db37fcf9061247750

Sync libiberty with GCC.

libiberty/ChangeLog:
	* d-demangle.c (dlang_call_convention): Handle extern Objective-C
	function calling convention.
	(dlang_call_convention_p): Likewise.
	(dlang_type): Likewise.
	* testsuite/d-demangle-expected: Add coverage tests.

	* d-demangle.c (dlang_function_args): Append ',' for variadic functions
	only if parameters were seen before the elipsis symbol.
	* testsuite/d-demangle-expected: Add coverage test for parameter-less
	variadic functions.

	* d-demangle.c (dlang_type): Handle function types only in the context
	of seeing a pointer type symbol.
	* testsuite/d-demangle-expected: Update function pointer tests.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Set BFD_DECOMPRESS to decompress debug sections
@ 2016-01-28 21:41 sergiodj+buildbot
  2016-01-28 23:44 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-28 21:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bf150a0bad8d3fcfa17f5d6b5a5ca75efae855ed ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: bf150a0bad8d3fcfa17f5d6b5a5ca75efae855ed

Set BFD_DECOMPRESS to decompress debug sections

We should set BFD_DECOMPRESS to decompress debug sections when reading in
DWARF debug sections.

bfd/

	PR binutils/19523
	* dwarf2.c (_bfd_dwarf2_slurp_debug_info): Set BFD_DECOMPRESS to
	decompress debug sections.

binutils/

	PR binutils/19523
	* Makefile.am (check-DEJAGNU): Pass CC and CC_FOR_BUILD to
	runtest.
	* Makefile.in: Regenerated.
	* testsuite/binutils-all/compress.exp (test_gnu_debuglink): New
	proc.
	Run test_gnu_debuglink for native ELF build.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix two misleading indentation warnings
@ 2016-01-29 20:45 sergiodj+buildbot
  2016-01-29 21:22 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-29 20:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a2e3e93f4423899d99687da3ce4ac57cbed437f9 ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: a2e3e93f4423899d99687da3ce4ac57cbed437f9

Fix two misleading indentation warnings

Two small changes so everything builds with latest GCC and its
-Wmisleading-indentation.

In the aarch64-tdep.c case, the two misindented lines should actually be
part of the for loop.  It looks like the indentation is all done using
spaces in that file though...  I fixed it (changed for tabs + spaces) for
the lines I touched.

In the xcoffread.c case, we can simply remove the braces and fix the
indentation.

gdb/ChangeLog:

	* aarch64-tdep.c (aarch64_record_asimd_load_store): Add braces
	to for include additional lines.
	* xcoffread.c (scan_xcoff_symtab): Remove unnecessary braces.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Check reloc against IFUNC symbol only with dynamic symbols
@ 2016-01-31  0:17 sergiodj+buildbot
  2016-01-31  0:57 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-31  0:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d9e3b590692e62d83c21e39ec6641c4c09e70e4c ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: d9e3b590692e62d83c21e39ec6641c4c09e70e4c

Check reloc against IFUNC symbol only with dynamic symbols

There is no need to check relocation IFUNC symbol if there are no
dynamic symbols.

bfd/

	PR ld/19539
	* elf32-i386.c (elf_i386_reloc_type_class): Check relocation
	against STT_GNU_IFUNC symbol only with dynamic symbols.
	* elf64-x86-64.c (elf_x86_64_reloc_type_class): Likewise.

ld/

	PR ld/19539
	* testsuite/ld-elf/pr19539.d: New file.
	* testsuite/ld-elf/pr19539.s: Likewise.
	* testsuite/ld-elf/pr19539.t: Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix /usr/bin/ld: final link failed: File truncated error on hppa.
@ 2016-01-31 20:38 sergiodj+buildbot
  2016-01-31 21:13 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-01-31 20:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6d4b2867f8441c7bf75dfef6b3c95a10241f9709 ***

Author: John David Anglin <danglin@gcc.gnu.org>
Branch: master
Commit: 6d4b2867f8441c7bf75dfef6b3c95a10241f9709

Fix /usr/bin/ld: final link failed: File truncated error on hppa.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] elf64-s390.c: Fix -Werror=misleading-indentation
@ 2016-02-01  3:01 sergiodj+buildbot
  2016-02-01  3:36 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-01  3:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0bc7245a3a6da700ed13bace22cdc157dc80f58d ***

Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Branch: master
Commit: 0bc7245a3a6da700ed13bace22cdc157dc80f58d

elf64-s390.c: Fix -Werror=misleading-indentation

../../bfd/elf64-s390.c: In function 'elf_s390_reloc_name_lookup':
../../bfd/elf64-s390.c:340:5: error: statement is indented as if it were guarded by... [-Werror=misleading-indentation]
     if (strcasecmp (elf64_s390_vtinherit_howto.name, r_name) == 0)
     ^~
../../bfd/elf64-s390.c:333:3: note: ...this 'for' clause, but it is not
   for (i = 0;
   ^~~

bfd/
	* elf64-s390.c (elf_s390_reloc_name_lookup): Fix indentation.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix some comments in varobj.{c,h}
@ 2016-02-01  3:36 sergiodj+buildbot
  2016-02-01  4:44 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-01  3:36 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5fa1307022c1278575846faba5f3391b70d64b16 ***

Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: 5fa1307022c1278575846faba5f3391b70d64b16

Fix some comments in varobj.{c,h}

A few typos.  The comment about varobj_create has been misplaced since
the dawn of time.

gdb/ChangeLog:

	* varobj.h (struct varobj): Fix typos in comments.
	(struct lang_varobj_ops): Likewise.
	* varobj.c (VAROBJ_TABLE_SIZE): Likewise.
	(varobj_create): Move misplaced comment.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix NetBSD build with BSD and GNU make(1).
@ 2016-02-01 10:48 sergiodj+buildbot
  2016-02-01 11:21 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-01 10:48 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b6471e6e2c88ae473453e3499d9cb6a607a3e068 ***

Author: Kamil Rytarowski <n54@gmx.com>
Branch: master
Commit: b6471e6e2c88ae473453e3499d9cb6a607a3e068

Fix NetBSD build with BSD and GNU make(1).

	* Makefile.am (OPTIONAL_BACKENDS): Add netbsd-core.lo.
	(OPTIONAL_BACKENDS_CFILES): Add netbsd-core.c.
	* Makefile.in: Regenerated.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] x86 synthetic plt symbols
@ 2016-02-01 11:43 sergiodj+buildbot
  2016-02-01 13:30 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-01 11:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ec1f73bb0be7482f2dffd9bbca2f93fc74eca172 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: ec1f73bb0be7482f2dffd9bbca2f93fc74eca172

x86 synthetic plt symbols

Changing "pushq $1" in the following to "pushq $too_big" results in an
abort.  BFD shouldn't abort on (deliberately) bad user input.

 400480:       ff 25 9a 0b 20 00       jmpq   *0x200b9a(%rip)
 400486:       68 01 00 00 00          pushq  $0x1
 40048b:       e9 d0 ff ff ff          jmpq   400460 <_init+0x20>

	* elf64-x86-64.c (elf_x86_64_get_plt_sym_val): Don't abort on
	an out of range reloc_index.
	* elf32-i386.c (elf_i386_get_plt_sym_val): Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Add support for importing data from ILF images.
@ 2016-02-01 13:53 sergiodj+buildbot
  2016-02-01 14:35 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-01 13:53 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 655ed9ea1703173cb796070ed9843ea90bb74e58 ***

Author: Nathaniel Smith <njs@pobox.com>
Branch: master
Commit: 655ed9ea1703173cb796070ed9843ea90bb74e58

Add support for importing data from ILF images.

	* peicode.h (pe_ILF_build_a_bfd): Create an import symbol for both
	CODE and DATA.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] gdb: New set/show max-value-size command.
@ 2016-02-01 18:23 sergiodj+buildbot
  2016-02-01 18:54 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-01 18:23 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5fdf6324fafd60f967e2e8323fdacf84b1bfcea3 ***

Author: Andrew Burgess <andrew.burgess@embecosm.com>
Branch: master
Commit: 5fdf6324fafd60f967e2e8323fdacf84b1bfcea3

gdb: New set/show max-value-size command.

For languages with dynamic types, an incorrect program, or uninitialised
variables within a program, could result in an incorrect, overly large
type being associated with a value.  Currently, attempting to print such
a variable will result in gdb trying to allocate an overly large buffer.

If this large memory allocation fails then the result can be gdb either
terminating, or (due to memory contention) becoming unresponsive for the
user.

A new user visible variable in gdb helps guard against such problems,
two new commands are available:

   set max-value-size
   show max-value-size

The 'max-value-size' is the maximum size of memory in bytes that gdb
will allocate for the contents of a value.  Any attempt to allocate a
value with a size greater than this will result in an error.  The
initial default for this limit is set at 64k, this is based on a similar
limit that exists within the ada specific code.

It is possible for the user to set max-value-size to unlimited, in which
case the old behaviour is restored.

gdb/ChangeLog:

	* value.c (max_value_size): New variable.
	(MIN_VALUE_FOR_MAX_VALUE_SIZE): New define.
	(show_max_value_size): New function.
	(check_type_length_before_alloc): New function.
	(allocate_value_contents): Call check_type_length_before_alloc.
	(set_value_enclosing_type): Likewise.
	(_initialize_values): Add set/show handler for max-value-size.
	* NEWS: Mention new set/show command.

gdb/doc/ChangeLog:

	* gdb.texinfo (Value Sizes): New section.
	(Data): Add the 'Value Sizes' node to the menu.

gdb/testsuite/ChangeLog:

	* gdb.base/max-value-size.c: New file.
	* gdb.base/max-value-size.exp: New file.
	* gdb.base/huge.exp: Disable max-value-size for this test.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] gdb: Guard against undefined behaviour in mi-vla-fortran.exp
@ 2016-02-01 18:40 sergiodj+buildbot
  2016-02-01 20:01 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-01 18:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 37a8db1a336ce78a46bf7f303e47e17b2a1bf694 ***

Author: Andrew Burgess <andrew.burgess@embecosm.com>
Branch: master
Commit: 37a8db1a336ce78a46bf7f303e47e17b2a1bf694

gdb: Guard against undefined behaviour in mi-vla-fortran.exp

The test gdb.mi/mi-vla-fortran.exp reveals an issue with the DWARF
generated by gfortran.

In the test a pointer variable 'pvla2' is created:
    real, pointer :: pvla2 (:, :)

Initially this variable will be unassociated, so something like this:
    l = associated(pvla2)

should return false.

In the test gdb stops at a point _before_ pvla2 is associated with
anything, and we then try to print pvla2, the expectation is that gdb
should reply <not associated>.

The problem is that the data the DWARF directs gdb to read (to identify
if the variable is associated or not) is not initialised until the first
time pvla2 is accessed.

As a result gdb ends up reading uninitialised memory, sometimes this
uninitialised memory indicates the variable is associated (when it's
not).  This first mistake can lead to a cascade of errors, reading
uninitialised memory, with the result that gdb builds an invalid type to
associate with the variable pvla2.

In some cases, this invalid type can be very large, which when we try to
print pvla2 causes gdb to allocate a large amount of memory.

A recent commit added a new gdb variable 'max-value-size', which
prevents gdb from allocating values of extreme size.  As a result
directly trying to print pvla2 will now now error rather than allocate a
large amount of memory.

However, some of the later tests create a varobj for pvla2, and then
ask for the children of that varobj to be displayed.  In the case where
an invalid type has been computed for pvla2 then the number of children
can be wrong, and very big, in which case trying to display all of these
children can cause gdb to consume an excessive amount of memory.

This commit first detects if printing pvla2 triggers the max-value-size
error, if it does then we avoid all the follow on tests relating to the
unassociated pvla2, which avoids the second error printing the varobj
children.

gdb/testsuite/ChangeLog:

	* gdb.mi/mi-vla-fortran.exp: Add XFAIL for accessing unassociated
	pointer.  Don't perform further tests on the unassociated pointer
	if the first test fails.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Test gdb.threads/forking-threads-plus-breakpoint.exp with displaced stepping off
@ 2016-02-01 19:35 sergiodj+buildbot
  2016-02-01 21:09 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-01 19:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6b2e4f10aeb64868720de06d3b2da3cc2d908f10 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 6b2e4f10aeb64868720de06d3b2da3cc2d908f10

Test gdb.threads/forking-threads-plus-breakpoint.exp with displaced stepping off

This exposes the internal error Don mentioned in PR19496:

  (1) internal error --  gdb/target.c:2713: internal-error: Can't determine the current address space of thread

More analysis here:

  https://sourceware.org/ml/gdb-patches/2016-01/msg00685.html

The (now kfailed) internal error looks like:

 continue &
 Continuing.
 (gdb) PASS: gdb.threads/forking-threads-plus-breakpoint.exp: cond_bp_target=1: detach_on_fork=on: displaced=off: continue &
 [New Thread 2846.2847]
 (...)
 [New Thread 2867.2867]
 /home/pedro/gdb/mygit/src/gdb/target.c:2723: internal-error: Can't determine the current address space of thread Thread 2846.2846

 A problem internal to GDB has been detected,
 further debugging may prove unreliable.
 Quit this debugging session? (y or n) KFAIL: gdb.threads/forking-threads-plus-breakpoint.exp: cond_bp_target=1: detach_on_fork=on: displaced=off: inferior 1 exited (GDB internal error) (PRMS: remote/19496)
 Resyncing due to internal error.

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

	PR remote/19496
	* gdb.threads/forking-threads-plus-breakpoint.exp
	(displaced_stepping_supported): New global.
	(probe_displaced_stepping_support): New procedure.
	(do_test): Add 'displaced' parameter, and use it.
	(top level): Check for displaced stepping support.  Add displaced
	stepping on/off testing axis.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] gdb.base/skip.exp: Clean up multiple references to same test name.
@ 2016-02-01 23:33 sergiodj+buildbot
  2016-02-02  0:10 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-01 23:33 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9482b9fbb6414468228c618c165e397116a4a8f8 ***

Author: Doug Evans <dje@google.com>
Branch: master
Commit: 9482b9fbb6414468228c618c165e397116a4a8f8

gdb.base/skip.exp: Clean up multiple references to same test name.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Don't add DT_NEEDED for unmatched symbol
@ 2016-02-01 23:59 sergiodj+buildbot
  2016-02-02  1:18 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-01 23:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT aef28989904e92e391fee905e51abc6bb2fd4de0 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: aef28989904e92e391fee905e51abc6bb2fd4de0

Don't add DT_NEEDED for unmatched symbol

Don't add DT_NEEDED if a symbol from a library loaded via DT_NEEDED
doesn't match the symbol referenced by regular object.

bfd/

	PR ld/19553
	* elflink.c (elf_link_add_object_symbols): Don't add DT_NEEDED
	if a symbol from a library loaded via DT_NEEDED doesn't match
	the symbol referenced by regular object.

ld/testsuite/

	PR ld/19553
	* testsuite/ld-elf/indirect.exp: Run tests for PR ld/19553.
	* testsuite/ld-elf/pr19553.map: New file.
	* testsuite/ld-elf/pr19553.map: Likewise.
	* testsuite/ld-elf/pr19553a.c: Likewise.
	* testsuite/ld-elf/pr19553b.c: Likewise.
	* testsuite/ld-elf/pr19553b.out: Likewise.
	* testsuite/ld-elf/pr19553c.c: Likewise.
	* testsuite/ld-elf/pr19553c.out: Likewise.
	* testsuite/ld-elf/pr19553d.c: Likewise.
	* testsuite/ld-elf/pr19553d.out: Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Merge gdb and gdbserver implementations for siginfo
@ 2016-02-02 10:56 sergiodj+buildbot
  2016-02-02 11:30 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-02 10:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 93813b37c86a70fbd4d8c9d63f95cf8b87bbf425 ***

Author: Walfred Tedeschi <walfred.tedeschi@intel.com>
Branch: master
Commit: 93813b37c86a70fbd4d8c9d63f95cf8b87bbf425

Merge gdb and gdbserver implementations for siginfo

Extract the compatible siginfo handling from amd64-linux-nat.c and
gdbserver/linux-x86-low to a new file nat/amd64-linux-siginfo.c.

2016-02-02  Walfred Tedeschi  <walfred.tedeschi@intel.com>

gdb/ChangeLog:

	* nat/amd64-linux-siginfo.c: New file.
	* nat/amd64-linux-siginfo.h: New file.
	* Makefile.in (HFILES_NO_SRCDIR): Add nat/amd64-linux-siginfo.h.
	(amd64-linux-siginfo.o): New rule.
	* config/i386/linux64.mh (NATDEPFILES): Add amd64-linux-siginfo.o.
	* amd64-linux-nat.c (nat/amd64-linux-siginfo.h): New include.
	(compat_siginfo_from_siginfo, siginfo_from_compat_siginfo)
	(compat_x32_siginfo_from_siginfo, siginfo_from_compat_x32_siginfo)
	(compat_timeval, compat_sigval, compat_x32_clock, cpt_si_pid)
	(cpt_si_uid, cpt_si_timerid, cpt_si_overrun, cpt_si_status)
	(cpt_si_utime, cpt_si_stime, cpt_si_ptr, cpt_si_addr, cpt_si_band)
	(cpt_si_fd, si_timerid, si_overrun): Move to nat/amd64-linux-siginfo.c.

gdb/gdbserver/ChangeLog:

	* configure.srv (x86_64-*-linux*): Add amd64-linux-siginfo.o
	to srv_tgtobj.
	(i[34567]86-*-linux*): Add amd64-linux-siginfo.o
	to srv_tgtobj.
	* linux-x86-low.c [__x86_64__]: Include
	"nat/amd64-linux-siginfo.h".
	(compat_siginfo_from_siginfo, siginfo_from_compat_siginfo)
	(compat_x32_siginfo_from_siginfo, siginfo_from_compat_x32_siginfo)
	(compat_timeval, compat_sigval, compat_x32_clock, cpt_si_pid)
	(cpt_si_uid, cpt_si_timerid, cpt_si_overrun, cpt_si_status)
	(cpt_si_utime, cpt_si_stime, cpt_si_ptr, cpt_si_addr, cpt_si_band)
	(cpt_si_fd, si_timerid, si_overrun): Move from
	nat/amd64-linux-siginfo.c.
	* Makefile.in (amd64-linux-siginfo.o:): New rule.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Preparation for new siginfo on Linux
@ 2016-02-02 11:05 sergiodj+buildbot
  2016-02-02 12:34 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-02 11:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 43564574f1de367f537a37bf6ec83bb4c29627c6 ***

Author: Walfred Tedeschi <walfred.tedeschi@intel.com>
Branch: master
Commit: 43564574f1de367f537a37bf6ec83bb4c29627c6

Preparation for new siginfo on Linux

First add new structure and function to allow architecture customization
for the siginfo structure.

2016-01-15  Walfred Tedeschi  <walfred.tedeschi@intel.com>

gdb/ChangeLog:

	* linux-tdep.h (linux_siginfo_extra_field_values): New enum values.
	(linux_siginfo_extra_fields): New enum type.
	* linux-tdep.c (linux_get_siginfo_type_with_fields): New function.
	(linux_get_siginfo_type): Use new function.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Add bound related fields to the siginfo structure
@ 2016-02-02 11:21 sergiodj+buildbot
  2016-02-02 14:42 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-02 11:21 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 96b5c49fb18ba7ad070b0c3ad36388d56c5897fb ***

Author: Walfred Tedeschi <walfred.tedeschi@intel.com>
Branch: master
Commit: 96b5c49fb18ba7ad070b0c3ad36388d56c5897fb

Add bound related fields to the siginfo structure

Both Linux and glibc have introduced bound related fields in the
segmentation fault fields of the siginfo_t type. Add the new fields
to our x86's siginfo_t type too.

Kernel patch:
http://git.kernel.org/cgit/linux/kernel/git/tip/tip.git/commit/?id=ee1b58d36aa1b5a79eaba11f5c3633c88231da83

Glibc patch:
http://repo.or.cz/w/glibc.git/commit/d4358b51c26a634eb885955aea06cad26af6f696

2016-02-02  Walfred Tedeschi  <walfred.tedeschi@intel.com>

gdb/ChangeLog:

	* linux-tdep.c (linux_get_siginfo_type): Add the _addr_bnd
	structure to the siginfo if extra_fields contains
	LINUX_SIGINFO_FIELD_ADDR_BND.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] epiphany/disassembler: Improve alignment of output.
@ 2016-02-02 11:38 sergiodj+buildbot
  2016-02-02 16:51 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-02 11:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b89807c67baf4f31125d151f2dc3532b3420964d ***

Author: Andrew Burgess <andrew.burgess@embecosm.com>
Branch: master
Commit: b89807c67baf4f31125d151f2dc3532b3420964d

epiphany/disassembler: Improve alignment of output.

Always set the bytes_per_line field (of struct disassemble_info) to the
same constant value, this is inline with the advice contained within
include/dis-asm.h.

Setting this field to a constant value will cause the disassembler
output to be better aligned.

cpu/ChangeLog:

	* epiphany.opc (epiphany_print_insn): Set info->bytes_per_line to
	a constant to better align disassembler output.

opcodes/ChangeLog:

	* epiphany-dis.c: Regenerated from latest cpu files.

gas/ChangeLog:

	* testsuite/gas/epiphany/sample.d: Update expected output.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] opcodes/cgen: Rework calculation of shift when inserting fields
@ 2016-02-02 12:04 sergiodj+buildbot
  2016-02-02 17:57 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-02 12:04 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a143b0045ca8a7024a8515b5dda3ceab5f832e83 ***

Author: Andrew Burgess <andrew.burgess@embecosm.com>
Branch: master
Commit: a143b0045ca8a7024a8515b5dda3ceab5f832e83

opcodes/cgen: Rework calculation of shift when inserting fields

The calculation of the shift amount, used to insert fields into the
instruction buffer, is not correct when the following conditions are all
true:
  - CGEN_INT_INSN_P is defined, and true.
  - CGEN_INSN_LSB0_P is true
  - Total instruction length is greater than the length of a single
    instruction word (the instruction is made of multiple words)
  - The word offset is non-zero (the field is outside the first word)

When the above conditions are all true, the calculated shift fails to
take account of the total instruction length.

After this commit the calculation of the shift amount is split into two
parts, first we calculate the shift required to get to BIT0 of the word
in which the field lives, then we calculate the shift required to place
the field within the instruction word.

The change in this commit only effects the CGEN_INT_INSN_P defined true
case, but changes the code for both CGEN_INSN_LSB0_P true, and false.

In the case of CGEN_INSN_LSB0_P being false, the code used to say:

	shift = total_length - (word_offset + start + length);

Now it says:

	shift_to_word = total_length - (word_offset + word_length);
	shift_within_word = word_length - start - length;
	shift = shift_to_word + shift_within_word;

>From which we can see that in all cases the computed shift value should
be unchanged.

In the case of CGEN_INSN_LSB0_P being true, the code used to say:

	shift = (word_offset + start + 1) - length;

Now it says:

	shift_to_word = total_length - (word_offset + word_length);
	shift_within_word = start + 1 - length;
	shift = shift_to_word + shift_within_word;

In the case where 'total_length == word_length' AND 'word_offset ==
0' (which indicates an instruction of a single word), we see that the
computed shift value will be unchanged.  However, when the total_length
and word_length are different, and the word_offset is non-zero then the
computed shift value will be different (and correct).

opcodes/ChangeLog:

	* cgen-ibld.in (insert_normal): Rework calculation of shift.
	* epiphany-ibld.c: Regenerate.
	* fr30-ibld.c: Regenerate.
	* frv-ibld.c: Regenerate.
	* ip2k-ibld.c: Regenerate.
	* iq2000-ibld.c: Regenerate.
	* lm32-ibld.c: Regenerate.
	* m32c-ibld.c: Regenerate.
	* m32r-ibld.c: Regenerate.
	* mep-ibld.c: Regenerate.
	* mt-ibld.c: Regenerate.
	* or1k-ibld.c: Regenerate.
	* xc16x-ibld.c: Regenerate.
	* xstormy16-ibld.c: Regenerate.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Adaptation of siginfo fixup for the new bnd fields
@ 2016-02-02 12:26 sergiodj+buildbot
  2016-02-02 15:47 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-02 12:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3f2f6cb5e8922b680de9d67ad83d3b571d3b2a46 ***

Author: Walfred Tedeschi <walfred.tedeschi@intel.com>
Branch: master
Commit: 3f2f6cb5e8922b680de9d67ad83d3b571d3b2a46

Adaptation of siginfo fixup for the new bnd fields

New bnds fields will be always present for x86 architecture.
Fixup for compatibility layer 32bits has to be fixed.

It was added the nat_siginfo to serving as intermediate step
between kernel provided siginfo and the fix up routine.

When executing compat_siginfo_from_siginfo or
compat_x32_siginfo_from_siginfo first the buffer read from the kernel are
converted into the nat_signfo for homogenization, then the fields of
nat_siginfo are use to set the compat and compat_x32 siginfo fields.

In other to make this conversion independent of the system where gdb
is compiled the most complete version of the siginfo, named as native
siginfo, is used internally as an intermediate step.

Conversion using nat_siginfo is exemplified below:

compat_siginfo_from_siginfo or compat_x32_siginfo_from_siginfo:

buffer (from the kernel) -> nat_siginfo -> 32 / X32 siginfo
                      (memcpy)       (field by field)

siginfo_from_compat_x32_siginfo or siginfo_from_compat_siginfo:

32 / X32 siginfo -> nat_siginfo -> buffer (to the kernel)
          (field by field)    (memcpy)

Caveat: No support for MPX on x32.

2016-02-02  Walfred Tedeschi  <walfred.tedeschi@intel.com>

gdb/ChangeLog:

	* amd64-linux-siginfo.c (nat_siginfo_t, nat_sigval_t, nat_timeval):
	New types.
	(compat_siginfo): New bound fields added.
	(compat_x32_siginfo): New field added.
	(cpt_si_addr_lsb): New define.
	(compat_siginfo_from_siginfo): Use nat_siginfo.
	(siginfo_from_compat_siginfo): Use nat_siginfo.
	(compat_x32_siginfo_from_siginfo): Likewise.
	(siginfo_from_compat_x32_siginfo): Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Clear HAS_RELOC if there are no relocations
@ 2016-02-02 12:31 sergiodj+buildbot
  2016-02-02 19:02 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-02 12:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 14f2c699ddca1e2f706342dffc59a6c7e23e844c ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 14f2c699ddca1e2f706342dffc59a6c7e23e844c

Clear HAS_RELOC if there are no relocations

The HAS_RELOC bit should be cleared when relocations are removed from
relocatable files.

bfd/

	PR binutils/19547
	* elf.c (assign_section_numbers): Clear HAS_RELOC if there are
	no relocations in relocatable files.

binutils/

	PR binutils/19547
	* testsuite/binutils-all/objcopy.exp
	(objcopy_test_without_global_symbol): New proc.
	Run objcopy_test_without_global_symbol.
	* testsuite/binutils-all/pr19547.c: New file.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] PowerPC64 ELFv2 entry code
@ 2016-02-02 13:44 sergiodj+buildbot
  2016-02-02 20:07 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-02 13:44 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 85fabe715c441e1c90fe913e2a6d65f0e487e5e8 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 85fabe715c441e1c90fe913e2a6d65f0e487e5e8

PowerPC64 ELFv2 entry code

This tightens the condition under which ld optimizes PIC entry code
to non-PIC.

bfd/
	* elf64-ppc.c (ppc64_elf_relocate_section): Further restrict
	ELFv2 entry optimization.
gold/
	* powerpc.cc (relocate): Further restrict ELFv2 entry optimization.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Store estimated istrances in compressed_size
@ 2016-02-02 16:34 sergiodj+buildbot
  2016-02-02 21:12 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-02 16:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4a539596f5d54d3116c5fdebd8be56998757288b ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 4a539596f5d54d3116c5fdebd8be56998757288b

Store estimated istrances in compressed_size

elf_x86_64_convert_load is very time consuming since it is called on
each input section and has a loop over input text sections to estimate
the branch distrance.  We can store the estimated distrances in the
compressed_size field of the output section, which is only used to
decompress the compressed input section.

Before the patch, linking clang 3.9 takes 52 seconds.  After the patch,
it only takes 2.5 seconds.

	PR ld/19542
	* elf64-x86-64.c (elf_x86_64_convert_load): Store the estimated
	distrances in the compressed_size field of the output section.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix typos in bfd/ChangeLog and bfd/elf64-x86-64.c
@ 2016-02-02 21:21 sergiodj+buildbot
  2016-02-02 22:16 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-02 21:21 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fb06f1c0f25d27006b28a94e54273a6bb35b5926 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: fb06f1c0f25d27006b28a94e54273a6bb35b5926

Fix typos in bfd/ChangeLog and bfd/elf64-x86-64.c


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] ui-out.c: Remove unused enum
@ 2016-02-02 21:51 sergiodj+buildbot
  2016-02-02 23:21 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-02 21:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6456a18b717e7b1ae96d77a2549fbf4da60d6617 ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: 6456a18b717e7b1ae96d77a2549fbf4da60d6617

ui-out.c: Remove unused enum

This is unused since 54eb231c4bca046e8b8cd73461f695e02c5620d5, where
static arrays of ui_out_levels were replaced with vectors.

gdb/ChangeLog:

	* ui-out.c (MAX_UI_OUT_LEVELS): Remove.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix "PowerPC64 ELFv2 entry code" for big-endian
@ 2016-02-03 14:16 sergiodj+buildbot
  2016-02-03 14:46 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-03 14:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4f038ee5d22f04a16a413cf2e3d8ddeecdc75639 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 4f038ee5d22f04a16a413cf2e3d8ddeecdc75639

Fix "PowerPC64 ELFv2 entry code" for big-endian

bfd/
	* elf64-ppc.c (ppc64_elf_relocate_section): Adjust last patch
	for big-endian.
gold/
	* powerpc.cc (relocate): Adjust last patch for big-endian.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] MAINTAINERS: Add Thiemo Seufer back, as a past maintainer
@ 2016-02-03 22:03 sergiodj+buildbot
  2016-02-03 22:34 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-03 22:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3b8f2c8bcf7c6bf1339aa3c3f2d6f129b7878052 ***

Author: Maciej W. Rozycki <macro@linux-mips.org>
Branch: master
Commit: 3b8f2c8bcf7c6bf1339aa3c3f2d6f129b7878052

MAINTAINERS: Add Thiemo Seufer back, as a past maintainer

Complement commit 26e0f8dbd817 ("* MAINTAINERS: Remove Thiemo Seufer.").

	* MAINTAINERS (Past sim maintainers): Add Thiemo Seufer.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix the encoding of the MSP430's RRUX instruction.
@ 2016-02-04 10:06 sergiodj+buildbot
  2016-02-04 10:38 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-04 10:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c1d9289fef41b82aa22f63f74aa8e730ec898d3c ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: c1d9289fef41b82aa22f63f74aa8e730ec898d3c

Fix the encoding of the MSP430's RRUX instruction.

	PR target/19561
opcdoe	* msp430-dis.c (print_insn_msp430): Add a special case for
	decoding an RRC instruction with the ZC bit set in the extension
	word.

include	* opcode/msp430.h (IGNORE_CARRY_BIT): New define.
	(RRUX): Synthesise using case 2 rather than 7.

gas	* config/tc-msp430.c (msp430_operands): Remove case 7.  Use case 2
	to handle encoding of RRUX instruction.
	* testsuite/gas/msp430/msp430x.s: Add more tests of the extended
	shift instructions.
	* testsuite/gas/msp430/msp430x.d: Update expected disassembly.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] waiting_for_stop_reply around remote_fileio_request
@ 2016-02-04 15:22 sergiodj+buildbot
  2016-02-04 15:52 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-04 15:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e42e5352d1d1e8a262178f606a5df3d0d988f78a ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: e42e5352d1d1e8a262178f606a5df3d0d988f78a

waiting_for_stop_reply around remote_fileio_request

Hi,
I see this error when GDB connects with qemu,

(gdb) n
....
Sending packet: $vCont;c#a8...Ack
Packet received: Ffstat,00000001,f6fff038
Cannot execute this command while the target is running.
Use the "interrupt" command to stop the target
and then try again.

looks we don't set rs->waiting_for_stop_reply to zero
before handle fileio request,

 #10 0x00000000005edb64 in target_write (len=64, offset=4143968312, buf=0x7fffffffd570 "\375\377\377\377", annex=0x0, object=TARGET_OBJECT_MEMORY,
    ops=<optimised out>) at /home/yao/SourceCode/gnu/gdb/git/gdb/target.c:1922
 #11 target_write_memory (memaddr=memaddr@entry=4143968312, myaddr=myaddr@entry=0x7fffffffd6a0 "", len=len@entry=64)
    at /home/yao/SourceCode/gnu/gdb/git/gdb/target.c:1500
 #12 0x00000000004b2b41 in remote_fileio_func_fstat (buf=0x127b258 "") at /home/yao/SourceCode/gnu/gdb/git/gdb/remote-fileio.c:1037
 #13 0x00000000004b1878 in do_remote_fileio_request (uiout=<optimised out>, buf_arg=buf_arg@entry=0x127b240)
    at /home/yao/SourceCode/gnu/gdb/git/gdb/remote-fileio.c:1204
 #14 0x00000000005b8c7c in catch_exceptions_with_msg (func_uiout=<optimised out>, func=func@entry=0x4b1800 <do_remote_fileio_request>,
    func_args=func_args@entry=0x127b240, gdberrmsg=gdberrmsg@entry=0x0, mask=mask@entry=RETURN_MASK_ALL)
    at /home/yao/SourceCode/gnu/gdb/git/gdb/exceptions.c:187
 #15 0x00000000005b8dea in catch_exceptions (uiout=<optimised out>, func=func@entry=0x4b1800 <do_remote_fileio_request>, func_args=func_args@entry=0x127b240,
    mask=mask@entry=RETURN_MASK_ALL) at /home/yao/SourceCode/gnu/gdb/git/gdb/exceptions.c:167
 #16 0x00000000004b2fff in remote_fileio_request (buf=0x127b240 "Xf6fff038,0:", ctrlc_pending_p=0) at /home/yao/SourceCode/gnu/gdb/git/gdb/remote-fileio.c:1255
 #17 0x0000000000496f12 in remote_wait_as (ptid=..., status=0x7fffffffdb20, options=1) at /home/yao/SourceCode/gnu/gdb/git/gdb/remote.c:6997

however, we did set rs->waiting_for_stop_reply to zero before Luis's
patch https://sourceware.org/ml/gdb-patches/2015-10/msg00336.html

In fact, Luis's patch v1
https://sourceware.org/ml/gdb-patches/2015-08/msg00809.html is about
setting rs->waiting_for_stop_reply back to one after
remote_fileio_request, which is correct.  However during the review, the
patch is changed and ends up with "not setting rs->waiting_for_stop_reply
to zero".

I manually test GDB, but I don't have a way to run regression tests.

gdb:

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

	* remote.c (remote_wait_as): Set rs->waiting_for_stop_reply to
	0 before handling 'F' and set it back afterwards.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [testsuite] Remove BASEDIR
@ 2016-02-04 15:57 sergiodj+buildbot
  2016-02-04 16:57 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-04 15:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 31d913c7e4e84edf88b4324c3a9a8fb31c8206ec ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 31d913c7e4e84edf88b4324c3a9a8fb31c8206ec

[testsuite] Remove BASEDIR

BASEDIR was added by https://sourceware.org/ml/gdb-patches/2013-10/msg00587.html
in order to handle the different directory layout in serial testing
and parallel testing.  BASEDIR is "gdb.base" in serial testing and is
"outputs/gdb.base/TESTNAME" in parallel testing.  However, it doesn't
work if the GDBserver is in remote target, like this,

$ make check RUNTESTFLAGS='--target_board=remote-gdbserver-on-localhost foll-vfork.exp foll-exec.exp'
FAIL: gdb.base/foll-exec.exp: continue to first exec catchpoint (the program exited)
FAIL: gdb.base/foll-vfork.exp: exec: vfork and exec child follow, to main bp: continue to bp (the program exited)
FAIL: gdb.base/foll-vfork.exp: exec: vfork child follow, finish after tcatch vfork: finish (the program exited)
FAIL: gdb.base/foll-vfork.exp: exec: vfork relations in info inferiors: continue to bp (the program exited)

these tests fail because the executable can't be found.  With target
board native-gdbserver, the program is spawned this way,

 spawn ../gdbserver/gdbserver --once :2347 /scratch/yao/gdb/build-git/x86_64/gdb/testsuite/gdb.base/foll-vfork

so BASEDIR is correct.  However, with target board
remote-gdbserver-on-localhost, the program is spawned

  spawn /usr/bin/ssh -l yao localhost /scratch/yao/gdb/build-git/x86_64/gdb/testsuite/../gdbserver/gdbserver --once :2346 /scratch/yao/gdb/build-git/x86_64/gdb/testsuite/gdb.base/foll-vfork

so BASEDIR (either "gdb.base" or "outputs/gdb.base/TESTNAME") makes no
sense.

I had a fix that pass absolute directory to BASEDIR, but it assumes
that directory structure is the same on build and target, and it
doesn't work in remote host case.  The current fix in this patch is
to get the directory from argv[0].  In any case, the program to be
exec'ed is at the same directory with the main program.

Note that these tests do "next N" to let program stop at the desired
line, but it is fragile, because GDB for different targets may skip
function prologue slightly differently, so I replace some of them by
"tbreak on LINE NUMBER and continue".

gdb/testsuite:

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

	* gdb.base/foll-exec-mode.c: Include limits.h.
	(main): Add parameters argc and argv.  Get directory from
	argv[0].
	* gdb.base/foll-exec-mode.exp: Don't pass -DBASEDIR in
	compilation.
	* gdb.base/foll-exec.c: Include limits.h.
	(main): Add parameters argc and argv.
	Get directory from argv[0].
	* gdb.base/foll-exec.exp: Don't pass -DBASEDIR in compilation.
	Adjust tests on the number of lines as source code changed.
	* gdb.base/foll-vfork-exit.c: Include limits.h.
	(main): Add one line of statement before vfork.
	* gdb.base/foll-vfork.c: Include limits.h and string.h.
	(main): Add parameters argc and argv.  Get directory from
	argv[0].
	* gdb.base/foll-vfork.exp: Don't pass -DBASEDIR in compilation.
	(setup_gdb): Set tbreak to skip some source lines.
	* gdb.multi/bkpt-multi-exec.c: Include limits.h.
	(main): Add parameters argc and argv.  Get directory from
	argv[0].
	* gdb.multi/bkpt-multi-exec.exp: Don't pass -DBASEDIR in
	compilation.
	* gdb.multi/multi-arch-exec.c: Include limits.h and string.h.
	(main): Add parameters argc and argv.  Get directory from
	argv[0].
	* gdb.multi/multi-arch-exec.exp: Don't pass -DBASEDIR in
	compilation.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Prevent possible undefined behaviour computing the size of the scache by usingunsigned integers instead of signed integers.
@ 2016-02-04 16:40 sergiodj+buildbot
  2016-02-04 18:02 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-04 16:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 13754e4c3d1b78945ecba225216f29d71334b77d ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: 13754e4c3d1b78945ecba225216f29d71334b77d

Prevent possible undefined behaviour computing the size of the scache by usingunsigned integers instead of signed integers.

	* cgen-scache.c (scache_option_handler): Prevent possible
	undefined behaviour computing the size of the scache by using
	unsigned integers instead of signed integers.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Change the default architecture value for ARC bfds so that they have the lowest possible value, and hence can be merged with other ARC binaries wihtout changing their architecture value.
@ 2016-02-05 10:11 sergiodj+buildbot
  2016-02-05 10:43 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-05 10:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bdbca4e6f805c73796c14c79102a8f1ea541d633 ***

Author: Cupertino Miranda <Cupertino.Miranda@synopsys.com>
Branch: master
Commit: bdbca4e6f805c73796c14c79102a8f1ea541d633

Change the default architecture value for ARC bfds so that they have the lowest possible value, and hence can be merged with other ARC binaries wihtout changing their architecture value.

bfd	* cpu-arc.c: Change default archure from bfd_mach_arc_arcv2
	to bfd_mach_arc_arc600.

binutils * testsuite/binutils-all/objdump.exp: Update expected default
	architecture value for ARC binaries.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] sim: mips: fix prog_bfd usage
@ 2016-02-06  1:39 sergiodj+buildbot
  2016-02-06  3:21 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-06  1:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1554f758410c4307103120424d35050e88433d85 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 1554f758410c4307103120424d35050e88433d85

sim: mips: fix prog_bfd usage

We do not want to reference the "base" member directly.  We have the
STATE_PROG_BFD macro instead to look up the prog_bfd member.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] varobj: Cleanup dead code
@ 2016-02-07 14:56 sergiodj+buildbot
  2016-02-07 15:28 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-07 14:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 30914ca8c030eedc4a7e1f1acc878211639cc1ca ***

Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: 30914ca8c030eedc4a7e1f1acc878211639cc1ca

varobj: Cleanup dead code

This patch removes some dead code.

I noticed that varobj_delete was always called with dellist == NULL, so
I started removing that parameter.  That allows removing a good chunk of
the code in varobj_delete, making it almost trivial.  We can also remove
the resultp parameters in that whole trail.  In turn, this shows that
struct cpstack, cppush and cppop were only used fo that mechanism, so
they can be removed as well.

I also moved the function comment to the header file to comply with
today's guideline, even though the rest of the file does not respect it
(yet).

gdb/ChangeLog:

	* varobj.h (varobj_delete): Remove dellist parameter, update and
	move documentation here.
	* varobj.c (struct cpstack, cppush, cppop): Remove.
	(delete_variable): Remove resultp (first) parameter.
	(delete_variable_1): Likewise.
	(varobj_delete): Remove dellist parameter and unused code.
	(update_dynamic_varobj_children): Adjust varobj_delete call.
	(update_type_if_necessary): Likewise.
	(varobj_set_visualizer): Likewise.
	(varobj_update): Likewise.
	(value_of_root): Likewise.
	(varobj_invalidate_iter): Likewise.
	* mi/mi-cmd-var.c (mi_cmd_var_delete): Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] remote.c: Cleanup unused variables
@ 2016-02-08 18:12 sergiodj+buildbot
  2016-02-08 18:45 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-08 18:12 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5488790363bf8f338e7aec4731f8bed472a2fcf9 ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: 5488790363bf8f338e7aec4731f8bed472a2fcf9

remote.c: Cleanup unused variables

I built remote.c with -Wunused, to check a function I was working on,
turns out there is a bunch of unused variables.

gdb/ChangeLog:

	* remote.c (remote_register_number_and_offset): Remove unused
	variable(s).
	(remote_thread_always_alive): Likewise.
	(remote_update_thread_list): Likewise.
	(process_initial_stop_replies): Likewise.
	(remote_start_remote): Likewise.
	(remote_check_symbols): Likewise.
	(discard_pending_stop_replies): Likewise.
	(process_stop_reply): Likewise.
	(putpkt_binary): Likewise.
	(getpkt): Likewise.
	(remote_add_target_side_condition): Likewise.
	(remote_insert_breakpoint): Likewise.
	(remote_supports_stopped_by_sw_breakpoint): Likewise.
	(remote_supports_stopped_by_hw_breakpoint): Likewise.
	(remote_xfer_partial): Likewise.
	(remote_read_btrace): Likewise.
	(remote_async_serial_handler): Likewise.
	(remote_thread_events): Likewise.
	(_initialize_remote): Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix in-tree, parallel running of Ada tests
@ 2016-02-08 19:12 sergiodj+buildbot
  2016-02-08 19:55 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-08 19:12 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 437277d47a15711f29e02e5265ce8bbb8c8ef4f5 ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: 437277d47a15711f29e02e5265ce8bbb8c8ef4f5

Fix in-tree, parallel running of Ada tests

While testing the following patch,

  [PATCH] Always organize test artifacts in a directory hierarchy
  https://sourceware.org/ml/gdb-patches/2016-01/msg00133.html

I noticed that it broke Ada testing.  This lead me to think that
parallel testing when building in-tree didn't work previously in Ada.
It is confirmed by this test:

$ make check TESTS="gdb.ada/fun_addr.exp" -j 2
...
Running ./gdb.ada/fun_addr.exp ...
FAIL: gdb.ada/fun_addr.exp: compilation foo.adb
...

This patch fixes in-tree parallel testing for Ada, and consequently
serial and parallel testing when the aforementioned patch is applied.

The problem originates from the fact that Ada support code cd's to the
builddir before compiling.  In itself it's not a problem, it allows to
place intermediate auto-generated files in that directory.  The Ada
compilation refers to the source file, which is in another directory,
only by its base name (e.g. foo.adb).  In serial mode, that worked
because builddir was the same as the source directory (e.g.
gdb.ada/fun_addr/).  In an out-of-tree build, it works because the
source directory is added as an include directory (note: this is not the
same $srcdir as autoconf's):

  set srcdir [file dirname $source]
  additional_flags=-I$srcdir

which becomes:

  additional_flags=-I/home/emaisin/build/binutils-gdb/gdb/testsuite/gdb.ada/fun_addr

However, when building in-tree, srcdir is relative: ./gdb.ada/fun_addr.
When using parallel or always-in-outputs-directory mode, we are cd'ed in
the outputs directory.  So -I$srcdir is relative to the current
directory, which is wrong.

To fix it, I made the TCL variable srcdir (set in site.exp, from which
everything else is derived) always absolute.  It is done by assigning
autoconf's abs_srcdir instead of autoconf's srcdir.  This way -I$srcdir
will always be good, regardless of where we cd'ed to.  A small apparent
change is that when running tests, DejaGnu will say:

  Running /tmp/binutils-gdb/gdb/testsuite/gdb.ada/fun_addr.exp ...

instead of

  Running ./gdb.ada/fun_addr.exp ...

I hope it's not too much of an annoyance.  I think that it should make
the testsuite a tiny bit more robust against other bugs of the same
class.

Regtested in & out of tree, only with native target.

gdb/testsuite/ChangeLog:

	* Makefile.in (abs_srcdir): Assign @abs_srcdir@.
	(site.exp): Assign abs_srcdir to tcl's srcdir.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Always organize test artifacts in a directory hierarchy
@ 2016-02-08 19:40 sergiodj+buildbot
  2016-02-08 21:03 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-08 19:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2151ccc56c74b55a8f0debf0724a495368f92591 ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: 2151ccc56c74b55a8f0debf0724a495368f92591

Always organize test artifacts in a directory hierarchy

When running tests in parallel, each test puts its generated files in a
different directory, under "outputs".  I think it would be nice if it
was always the case, as it would isolate the test cases a bit more.  An
artifact created by a test wouldn't get overwritten by another test.

Also, it makes it easier to clean up.  A lot of executables are left all
over the place because their names do not appear in gdb.*/Makefile.  If
everything is in "outputs", then we just have to delete that directory
(which we already do).

At the same time it makes the gdb.foo directories and their Makefiles
useless in the build directory, since they are pretty much only used for
cleaning.

What do you think?

gdb/testsuite/ChangeLog:

	* Makefile.in (ALL_SUBDIRS): Remove.
	(clean mostlyclean): Do not recurse in ALL_SUBDIRS.
	(distclean maintainer-clean realclean): Likewise.
	* configure.ac (AC_OUTPUT): Remove gdb.*/Makefile.
	* configure: Regenerate.
	* gdb.ada/Makefile.in: Delete.
	* gdb.arch/Makefile.in: Likewise.
	* gdb.asm/Makefile.in: Likewise.
	* gdb.base/Makefile.in: Likewise.
	* gdb.btrace/Makefile.in: Likewise.
	* gdb.cell/Makefile.in: Likewise.
	* gdb.compile/Makefile.in: Likewise.
	* gdb.cp/Makefile.in: Likewise.
	* gdb.disasm/Makefile.in: Likewise.
	* gdb.dlang/Makefile.in: Likewise.
	* gdb.dwarf2/Makefile.in: Likewise.
	* gdb.fortran/Makefile.in: Likewise.
	* gdb.gdb/Makefile.in: Likewise.
	* gdb.go/Makefile.in: Likewise.
	* gdb.guile/Makefile.in: Likewise.
	* gdb.java/Makefile.in: Likewise.
	* gdb.linespec/Makefile.in: Likewise.
	* gdb.mi/Makefile.in: Likewise.
	* gdb.modula2/Makefile.in: Likewise.
	* gdb.multi/Makefile.in: Likewise.
	* gdb.objc/Makefile.in: Likewise.
	* gdb.opencl/Makefile.in: Likewise.
	* gdb.opt/Makefile.in: Likewise.
	* gdb.pascal/Makefile.in: Likewise.
	* gdb.perf/Makefile.in: Likewise.
	* gdb.python/Makefile.in: Likewise.
	* gdb.reverse/Makefile.in: Likewise.
	* gdb.server/Makefile.in: Likewise.
	* gdb.stabs/Makefile.in: Likewise.
	* gdb.threads/Makefile.in: Likewise.
	* gdb.trace/Makefile.in: Likewise.
	* gdb.xml/Makefile.in: Likewise.
	* lib/gdb.exp (make_gdb_parallel_path): Add check for
	GDB_PARALLEL.
	(standard_output_file): Remove check for GDB_PARALLEL, always
	return path in outputs/$subdir/$testname.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix macro redefinition error on Solaris
@ 2016-02-09  5:24 sergiodj+buildbot
  2016-02-09  5:57 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-09  5:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 24f5f69a8a1d09c317a5f28d324fca73a8a0b930 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 24f5f69a8a1d09c317a5f28d324fca73a8a0b930

Fix macro redefinition error on Solaris

	PR 16583
	* elf/common.h (AT_SUN_HWCAP): Undef before defining.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix build breakage
@ 2016-02-09 10:38 sergiodj+buildbot
  2016-02-09 11:50 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-09 10:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 222cab58b7ed37df6e01dacb0932f400a2588137 ***

Author: Walfred Tedeschi <walfred.tedeschi@intel.com>
Branch: master
Commit: 222cab58b7ed37df6e01dacb0932f400a2588137

Fix build breakage

Add a cast to reinterpret a void* as a gdb_byte*.

2016-02-09  Walfred Tedeschi  <walfred.tedeschi@intel.com>

gdb/gdbserver/ChangeLog:

        * linux-x86-low.c (x86_siginfo_fixup): Add cast to gdb_byte*.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Revert "Add a more helpful warning message to explain why some AArch64 relocations can overflow."
@ 2016-02-09 10:48 sergiodj+buildbot
  2016-02-09 12:58 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-09 10:48 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0635c8759326e9431604b3359185cbf96740521d ***

Author: Walfred Tedeschi <walfred.tedeschi@intel.com>
Branch: master
Commit: 0635c8759326e9431604b3359185cbf96740521d

Revert "Add a more helpful warning message to explain why some AArch64 relocations can overflow."

This reverts commit 2ea53e003163338a403d5afbb2046cafb8f3abe9.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Revert "Fix build breakage"
@ 2016-02-09 10:57 sergiodj+buildbot
  2016-02-09 14:06 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-09 10:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c23bbc1cdae6149de4175a75aa9bf9bcbc936fa4 ***

Author: Walfred Tedeschi <walfred.tedeschi@intel.com>
Branch: master
Commit: c23bbc1cdae6149de4175a75aa9bf9bcbc936fa4

Revert "Fix build breakage"

This reverts commit 222cab58b7ed37df6e01dacb0932f400a2588137.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Add a more helpful warning message to explain why some AArch64 relocations can overflow.
@ 2016-02-09 11:06 sergiodj+buildbot
  2016-02-09 15:14 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-09 11:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 027e9c750c20fe8031a2b6d6272cd57bbf445df5 ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: 027e9c750c20fe8031a2b6d6272cd57bbf445df5

Add a more helpful warning message to explain why some AArch64 relocations can overflow.

bfd	* elfnn-aarch64.c (elfNN_aarch64_relocate_section): Add a more
	helpful warning message to explain why certain AArch64 relocs
	might overflow.

ld	* testsuite/ld-aarch64/reloc-overflow-bad.d: New test.
	* testsuite/ld-aarch64/reloc-overflow-1.s: New source file.
	* testsuite/ld-aarch64/reloc-overflow-2.s: New source file.
	* testsuite/ld-aarch64/aarch64-elf.exp: Run the new test.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix PR19548: Breakpoint re-set inserts breakpoints when it shouldn't
@ 2016-02-09 12:41 sergiodj+buildbot
  2016-02-09 17:37 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-09 12:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2a7f3dffced7a20c992e1488d9f05fed8b8001fd ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 2a7f3dffced7a20c992e1488d9f05fed8b8001fd

Fix PR19548: Breakpoint re-set inserts breakpoints when it shouldn't

PR19548 shows that we still have problems related to 13fd3ff34329:

 [PR17431: following execs with "breakpoint always-inserted on"]
 https://sourceware.org/ml/gdb-patches/2014-09/msg00733.html

The problem this time is that we currently update the global location
list and try to insert breakpoint locations after re-setting _each_
breakpoint in turn.

Say:

 - We have _more_ than one breakpoint set.  Let's assume 2.

 - There's a breakpoint with a pre-exec address that ends up being an
   unmapped address after the exec.

 - That breakpoint is NOT the first in the breakpoint list.

Then when handling an exec, and we re-set the first breakpoint in the
breakpoint list, we mistakently try to install the old pre-exec /
un-re-set locations of the other breakpoint, which fails:

 (gdb) continue
 Continuing.
 process 28295 is executing new program: (...)/execl-update-breakpoints2
 Error in re-setting breakpoint 1: Warning:
 Cannot insert breakpoint 2.
 Cannot access memory at address 0x1000764

 Breakpoint 1, main (argc=1, argv=0x7fffffffd368) at /home/pedro/gdb/mygit/src/gdb/testsuite/gdb.base/execl-update-breakpoints.c:34
 34        len = strlen (argv[0]);
 (gdb)

Fix this by deferring the global location list update till after all
breakpoints are re-set.

Tested on x86_64 Fedora 20, native and gdbserver.

gdb/ChangeLog:
2016-02-09  Pedro Alves  <palves@redhat.com>

	PR breakpoints/19548
	* breakpoint.c (create_overlay_event_breakpoint): Don't update
	global location list here.
	(create_longjmp_master_breakpoint)
	(create_std_terminate_master_breakpoint)
	(create_exception_master_breakpoint, create_jit_event_breakpoint)
	(update_breakpoint_locations):
	(breakpoint_re_set): Update global location list after all
	breakpoints are re-set.

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

	PR breakpoints/19548
	* gdb.base/execl-update-breakpoints.c (some_function): New
	function.
	(main): Call it.
	* gdb.base/execl-update-breakpoints.exp: Add a second breakpoint.
	Tighten expected GDB output.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
[parent not found: <8adce0342f5f50aba0154fc56ca59df45b219738@gdb-build>]
* [binutils-gdb] Refactor string_to_event_location for legacy linespec support.
@ 2016-02-09 22:48 sergiodj+buildbot
  2016-02-09 23:23 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-09 22:48 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT eeb1af437c6f1ca111bc31b63eefc5344b553681 ***

Author: Keith Seitz <keiths@redhat.com>
Branch: master
Commit: eeb1af437c6f1ca111bc31b63eefc5344b553681

Refactor string_to_event_location for legacy linespec support.

This patch refactors string_to_event_location, breaking it into two
separate functions:

1) string_to_event_location_basic
A "basic" string parser that implements support for "legacy" linespecs
(linespec, address, and probe locations).  This function is intended to
be used by any UI wishing/needing to support this legacy behavior.

2) string_to_event_location
This is now intended as a CLI-only function which adds explicit location
parsing in a CLI-appropriate manner (in the form of traditional option/value
pairs).

Together these patches serve to simplify string-to-event location parsing
for all existing non-CLI interfaces (MI, guile, and python).

gdb/ChangeLog

	* location.c (string_to_explicit_location): Note that "-p" is
	reserved for probe locations and return NULL for any input
	that starts with that.
	(string_to_event_location): Move "legacy" linespec code to ...
	(string_to_event_location_basic): ... here.
	* location.h (string_to_event_location): Update comment.
	(string_to_event_location_basic): New function.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] python/19506 -- gdb.Breakpoint address location regression
@ 2016-02-09 22:56 sergiodj+buildbot
  2016-02-10  0:34 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-09 22:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9f61929fd82fb632ee7c3be883d7086afc5c65d0 ***

Author: Keith Seitz <keiths@redhat.com>
Branch: master
Commit: 9f61929fd82fb632ee7c3be883d7086afc5c65d0

python/19506 -- gdb.Breakpoint address location regression

Now that "legacy" linespecs benefit from consolidated support in
string_to_event_location_basic, python's Breakpoint command should use this
function to turn strings into event locations.

As a result, this patch fixes python/19506. Before:

(gdb) python gdb.Breakpoint("*main")
Traceback (most recent call last):
  File "<string>", line 1, in <module>
RuntimeError: Function "*main" not defined.
Error while executing Python code.

After:

(gdb) python gdb.Breakpoint("*main")
Breakpoint 1 at 0x4005fb: file ../../../src/gdb/testsuite/gdb.python/py-breakpoint.c, line 32.

gdb/ChangeLog

	PR python/19506
	* python/py-breakpoint.c (bppy_init): Use
	string_to_event_location_basic instead of new_linespec_location.

gdb/testsuite/ChangeLog

	PR python/19506
	* gdb.python/py-breakpoint.exp (test_bkpt_address): New procedure.
	(toplevel): Call test_bkpt_address.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Use string_to_event_location_basic in guile.
@ 2016-02-09 23:05 sergiodj+buildbot
  2016-02-10  1:45 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-09 23:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a96e36da2f5278949099b0b985b2fa6ce474b135 ***

Author: Keith Seitz <keiths@redhat.com>
Branch: master
Commit: a96e36da2f5278949099b0b985b2fa6ce474b135

Use string_to_event_location_basic in guile.

This patch, analogous to the previous python patch, implements proper
legacy linespec support in guile code using the newly introduced
string_to_event_location_basic.

gdb/ChangeLog

	* guile/scm-breakpoint.c (gdbscm_register_breakpoint_x): Skip
	leading whitespace and use string_to_event_location_basic instead
	of new_linespec_location.

gdb/testsuite/ChangeLog

	* gdb.guile/scm-breakpoint.exp (test_bkpt_address): New procedure.
	(toplevel): Call test_bkpt_address.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] breakpoints/19546: Fix crash after updating breakpoints
@ 2016-02-10  0:25 sergiodj+buildbot
  2016-02-10  5:32 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-10  0:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9ef9e6a6a0dd8f948708cb67c9afcfd0be40cb0a ***

Author: Keith Seitz <keiths@redhat.com>
Branch: master
Commit: 9ef9e6a6a0dd8f948708cb67c9afcfd0be40cb0a

breakpoints/19546: Fix crash after updating breakpoints

One of the last checks update_breakpoints_after_exec does while looping
over the list of breakpoints is check that the breakpoint has a valid
location spec. It uses event_location_empty_p to check if the location spec
is "empty", and if it is, the breakpoint is deleted.

momentary_breakpoint types rely on setting the breakpoint structure's
location spec to NULL, thereby causing an update to delete the breakpoint.
However, event_location_empty_p assumed that locations were never NULL.
As a result, GDB would crash dereferencing a NULL pointer whenever
update_breakpoints_after_exec would encounter a momentary_breakpoint.

This patch creates a new wrapper/helper function which tests that the given
breakpoint's location spec is non-NULL and if it is not "empty"
or "unspecified."

gdb/ChangeLog

	PR breakpoints/19546
	* breakpoint.c (breakpoint_event_location_empty_p): New function.
	(update_breakpoints_after_exec, bkpt_re_set): Use this new function
	instead of event_location_empty_p.

gdb/testsuite/ChangeLog

	PR breakpoints/19546
	* gdb.base/infcall-exec.c: New file.
	* gdb.base/infcall-exec2.c: New file.
	* gdb.base/infcall-exec.exp: New file.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Bump version to 7.11.50.DATE-git.
@ 2016-02-10  3:58 sergiodj+buildbot
  2016-02-10 10:30 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-10  3:58 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d1dc0942695f0d18a923d6bbc1f5f31b39d17b33 ***

Author: Joel Brobecker <brobecker@adacore.com>
Branch: master
Commit: d1dc0942695f0d18a923d6bbc1f5f31b39d17b33

Bump version to 7.11.50.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.11.50.DATE-git.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Update NEWS post GDB 7.11 branch creation.
@ 2016-02-10  4:06 sergiodj+buildbot
  2016-02-10 11:38 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-10  4:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1233c0bae644451922bda07d03f1a66f3439dd20 ***

Author: Joel Brobecker <brobecker@adacore.com>
Branch: master
Commit: 1233c0bae644451922bda07d03f1a66f3439dd20

Update NEWS post GDB 7.11 branch creation.

gdb/ChangeLog:

	* NEWS: Create a new section for the next release branch.
	Rename the section of the current branch, now that it has
	been cut.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Sync top level files with gcc.
@ 2016-02-10 11:05 sergiodj+buildbot
  2016-02-10 17:19 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-10 11:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 52cf9762c53f5de7070a3951a3a6156082839d35 ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: 52cf9762c53f5de7070a3951a3a6156082839d35

Sync top level files with gcc.

	Import these patches from the GCC mainline:

	2016-01-12  Andris Pavenis  <andris.pavenis@iki.fi>

	* configure.ac: Enable LTO for DJGPP
	* configure: Regenerate

	2016-01-24  Mikhail Maltsev  <maltsevm@gmail.com>

	PR bootstrap/69329
	* Makefile.tpl (BASE_FLAGS_TO_PASS): Add LSAN_OPTIONS.
	* Makefile.in: Regenerate.

	2016-01-25  Aditya Kumar  <aditya.k7@samsung.com>
	            Sebastian Pop  <s.pop@samsung.com>

	* Makefile.in: Regenerate.
	* Makefile.tpl: Export ISLVER.
	* configure: Regenerate.
	* config/isl.m4: Detect isl-0.15.

	2016-01-29  Sebastian Pop  <s.pop@samsung.com>

	* config/isl.m4: Add comments about isl-0.16.
	* configure: Regenerate.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Correct assertion in NIOS2 linker to allow signed 16-buit immediate values.
@ 2016-02-10 11:38 sergiodj+buildbot
  2016-02-10 18:28 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-10 11:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 83da6e748c8f105f07e17f53aa6b99ed7867ff5f ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: 83da6e748c8f105f07e17f53aa6b99ed7867ff5f

Correct assertion in NIOS2 linker to allow signed 16-buit immediate values.

	PR 19405
	* elf32-nios2.c (nios2_elf32_install_imm16): Allow for signed
	immediate values.
	* elf-eh-frame.c (_bfd_elf_discard_section_eh_frame): Limit the
	number of messages about FDE encoding preventing .eh_frame_hdr
	generation.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] arm-tdep.c: Fix typo
@ 2016-02-10 15:50 sergiodj+buildbot
  2016-02-11  0:16 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-10 15:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 550dc4e26630c9b9a2bb95cd51250762fc89fe16 ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: 550dc4e26630c9b9a2bb95cd51250762fc89fe16

arm-tdep.c: Fix typo

unpriveleged -> unprivileged

gdb/ChangeLog:

	* arm-tdep.c (arm_copy_extra_ld_st): Fix "unpriveleged" typo.
	(arm_decode_dp_misc): Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Clear *VAL in regcache_raw_read_unsigned
@ 2016-02-10 17:06 sergiodj+buildbot
  2016-02-11  3:29 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-10 17:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9f6a71b4bfdad8fa2fe33e86f799fa0d362973dc ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 9f6a71b4bfdad8fa2fe33e86f799fa0d362973dc

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] 2113+ messages in thread
[parent not found: <473b99e5721ad623cc5826e03a73e2cf6cef4eb5@gdb-build>]
[parent not found: <e909d859f5635d66e79fef467da70d6090bfae1b@gdb-build>]
* [binutils-gdb] Mask off the least significant bit in GOT offset
@ 2016-02-11  3:48 sergiodj+buildbot
  2016-02-11  9:51 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-11  3:48 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 32875eb1f3b928dfe63c5752e8152a9dc09928f3 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 32875eb1f3b928dfe63c5752e8152a9dc09928f3

Mask off the least significant bit in GOT offset

The least significant bit in GOT offset is to record whether we have
initialized the GOT entry in R_386_GOT32 processing.  We need to mask
it off for R_386_GOT32X.

	PR ld/19601
	* elf32-i386.c (elf_i386_relocate_section): Mask off the least
	significant bit in GOT offset for R_386_GOT32X.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
[parent not found: <18d3cec54e1b4fce278dba436484846f8048d7d6@gdb-build>]
[parent not found: <5ac87a997fca849c654fffdf1c3e1991ea3f81d1@gdb-build>]
* [binutils-gdb] Use the target architecture when encoding tracepoint actions
@ 2016-02-11 13:31 sergiodj+buildbot
  2016-02-11 14:04 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-11 13:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 82e9becd8afe1d7c9971096592bf312637d9437f ***

Author: Antoine Tremblay <antoine.tremblay@ericsson.com>
Branch: master
Commit: 82e9becd8afe1d7c9971096592bf312637d9437f

Use the target architecture when encoding tracepoint actions

This patch uses the target architecture rather then the objfile
architecture when encoding tracepoint actions.

The target architecture may contain additional registers. E.g. ARM VFP
registers. This information is needed to allow their collection. Since we
can never know whether the registers numbers in the target match the
binary's we have to use tdesc here.

One note about combined debuggers / multi-inferior from Pedro Alves:

In the combined debugger case taking Cell as the practical example that
gdb supports currently:

In that case, the main target_gdbarch() will be powerpc, but you may have set a
tracepoint on _spu_ code, which has a different gdbarch.  so for that case,
target_gdbarch would be wrong.  I think that in that case, we'd need to
find __the_ target/tdesc gdbarch that is (bfd) compatible with the
objfile's gdbarch.

I think cell/spu gdbserver doesn't support tracepoints, so we can ignore
this for now.

The multi-inferior/process case is somewhat related, but its simpler.
each inferior has its own gdbarch.

That is, target_gdbarch depends on the current inferior selected.
In fact, that just returns inferior->gdbarch nowaways.

No regressions, tested on ubuntu 14.04 ARMv7 and x86.
With gdbserver-{native,extended} / { -marm -mthumb }

gdb/ChangeLog:

	* tracepoint.c (encode_actions_1): Use target_gdbarch () rather
	than loc->gdbarch.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] arm-tdep.c: Change type of insn parameters
@ 2016-02-11 18:30 sergiodj+buildbot
  2016-02-11 19:11 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-11 18:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 615234c107e5dcdefff78596971266e9346b3f76 ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: 615234c107e5dcdefff78596971266e9346b3f76

arm-tdep.c: Change type of insn parameters

Almost obvious... change the type of some insn parameters, so that it
matches the rest of the code.

gdb/ChangeLog:

	* arm-tdep.c (thumb_copy_unmodified_16bit): Change type of insn.
	(thumb_copy_b): Likewise.
	(arm_decode_b_bl_ldmstm): Likewise.
	(thumb_copy_16bit_ldr_literal): Likewise.
	(thumb_copy_pop_pc_16bit): Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] arm-tdep.c: Remove unused arm_displaced_step_copy_insn
@ 2016-02-11 19:25 sergiodj+buildbot
  2016-02-11 20:20 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-11 19:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2ba163c8d19971010e22176cf688b3de80bd8f08 ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: 2ba163c8d19971010e22176cf688b3de80bd8f08

arm-tdep.c: Remove unused arm_displaced_step_copy_insn

This function is never used, since it is superseded by
arm_linux_displaced_step_copy_insn.

gdb/ChangeLog:

	* arm-tdep.c (arm_displaced_step_copy_insn): Remove.
	(ARM displaced stepping support): Remove reference to
	arm_displaced_step_copy_insn in comment.
	* arm-tdep.h (arm_displaced_step_copy_insn): Remove.
	* arm-linux-tdep.c (arm_linux_displaced_step_copy_insn): Remove
	reference to arm_displaced_step_copy_insn in comment.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] arm-tdep.c: Remove unused variables
@ 2016-02-11 19:37 sergiodj+buildbot
  2016-02-11 21:28 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-11 19:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bec2ab5a15d96026d9f5470f7997fd48f7330fb2 ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: bec2ab5a15d96026d9f5470f7997fd48f7330fb2

arm-tdep.c: Remove unused variables

Just a little bit of cleanup.

gdb/ChangeLog:

	* arm-tdep.c (arm_skip_prologue): Remove unused variables.
	(arm_analyze_prologue): Likewise.
	(arm_scan_prologue): Likewise.
	(arm_m_exception_prev_register): Likewise.
	(arm_copy_block_xfer): Likewise.
	(thumb2_copy_block_xfer): Likewise.
	(arm_decode_miscellaneous): Likewise.
	(arm_decode_ld_st_word_ubyte): Likewise.
	(arm_decode_svc_copro): Likewise.
	(thumb2_decode_svc_copro): Likewise.
	(thumb_copy_16bit_ldr_literal): Likewise.
	(thumb_copy_pop_pc_16bit): Likewise.
	(decode_thumb_32bit_ld_mem_hints): Likewise.
	(arm_show_force_mode): Likewise.
	(_initialize_arm_tdep): Likewise.
	(arm_record_strx): Likewise.
	(arm_record_extension_space): Likewise.
	(arm_record_data_proc_misc_ld_str): Likewise.
	(arm_record_exreg_ld_st_insn): Likewise.
	(arm_record_vfp_data_proc_insn): Likewise.
	(arm_record_coproc_data_proc): Likewise.
	(thumb_record_misc): Likewise.
	(thumb_record_ldm_stm_swi): Likewise.
	(thumb2_record_ld_st_dual_ex_tbb): Likewise.
	(thumb2_record_ld_mem_hints): Likewise.
	(thumb2_record_lmul_lmla_div): Likewise.
	(thumb2_record_asimd_struct_ld_st): Likewise.
	(arm_process_record): Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Support 'make check-parallel' in gdb's build dir
@ 2016-02-11 20:04 sergiodj+buildbot
  2016-02-11 22:36 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-11 20:04 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e352bf0a3c8430aeab9d6f3781c7b31b09c8b8b9 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: e352bf0a3c8430aeab9d6f3781c7b31b09c8b8b9

Support 'make check-parallel' in gdb's build dir

Currently, you can cd to the gdb/testsuite/ dir and use
make check-parallel, instead of using FORCE_PARALLEL:

 $ make -j8 check-parallel RUNTESTFLAGS="--target_board=native-gdbserver"
 $ make -j8 check RUNTESTFLAGS="--target_board=native-gdbserver" FORCE_PARALLEL=1

But you can't do that in the build/gdb/ dir:

 $ make check-parallel RUNTESTFLAGS="--target_board=native-gdbserver"
 make: *** No rule to make target `check-parallel'.  Stop.

I find check-parallel a bit more convenient, and more typo-proof, so
this patch makes it work from the gdb build dir too.

While documenting this in testsuite/README, I found that the parallel
testing mode would better be pulled out to its own section and
extended.

gdb/ChangeLog:
2016-02-11  Pedro Alves  <palves@redhat.com>

	* Makefile.in (check-parallel): New rule.

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

	* README (Parallel testing): New section.
	(GDB_PARALLEL): Rewrite.
	(FORCE_PARALLEL): Document.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Add missing quotes to gdb/testsuite/README
@ 2016-02-11 20:15 sergiodj+buildbot
  2016-02-11 23:46 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-11 20:15 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT acc23c113ab9602707574e7df120f96170a9731c ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: acc23c113ab9602707574e7df120f96170a9731c

Add missing quotes to gdb/testsuite/README

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

	* README (Parallel testing): Add missing double quotes.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
[parent not found: <7cae9051edc2e3b11b5c79c08edfb91ee7f4e2e4@gdb-build>]
* [binutils-gdb] frame: add skip_tailcall_frames
@ 2016-02-12  9:01 sergiodj+buildbot
  2016-02-12  9:34 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-12  9:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2f3ef606b91298855e9ea13ae0e0316c23f06c9b ***

Author: Markus Metzger <markus.t.metzger@intel.com>
Branch: master
Commit: 2f3ef606b91298855e9ea13ae0e0316c23f06c9b

frame: add skip_tailcall_frames

Add a new function skip_tailcall_frames to skip TAILCALL_FRAME frames.

gdb/
	* frame.h (skip_tailcall_frames): New.
	* frame.c (skip_tailcall_frames): New.
	(frame_pop): Call skip_tailcall_frames.
	* infcmd.c (finish_command): Call skip_tailcall_frames.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] stack: check frame_unwind_caller_id
@ 2016-02-12  9:10 sergiodj+buildbot
  2016-02-12 10:43 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-12  9:10 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a038fa3e14a477d4d72a26c2e139fa47d2774be2 ***

Author: Markus Metzger <markus.t.metzger@intel.com>
Branch: master
Commit: a038fa3e14a477d4d72a26c2e139fa47d2774be2

stack: check frame_unwind_caller_id

Callers of frame_unwind_caller_* functions are supposed to check
frame_unwind_caller_id.

Add such a check to frame_info and treat an invalid caller ID as if the caller
PC were not available.

gdb/
	* stack.c (frame_info): Check frame_unwind_caller_id.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] btrace, frame: fix crash in get_frame_type
@ 2016-02-12  9:19 sergiodj+buildbot
  2016-02-12 11:52 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-12  9:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 33b4777ca1b7b456af8201b98eda27d1b272cbab ***

Author: Markus Metzger <markus.t.metzger@intel.com>
Branch: master
Commit: 33b4777ca1b7b456af8201b98eda27d1b272cbab

btrace, frame: fix crash in get_frame_type

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): Update comment.
	* frame.c (skip_artificial_frames, skip_tailcall_frames): Return NULL
	if only	artificial frames are found.  Update comment.
	(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.

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] 2113+ messages in thread
[parent not found: <d21b5f15d92bc1902b9e57198f67550326c887d7@gdb-build>]
[parent not found: <020ecd38e74681cb14987baf1a4d3c3ee3be0006@gdb-build>]
* [binutils-gdb] [ARM] Fixup PC in software single step
@ 2016-02-12 16:11 sergiodj+buildbot
  2016-02-12 16:43 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-12 16:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ed443b61e1f6e4eb7919fe9122dd947d1e87e767 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: ed443b61e1f6e4eb7919fe9122dd947d1e87e767

[ARM] Fixup PC in software single step

When I exercise GDBserver software single step, I see the following
error, which has been already handled by GDB properly.

In GDBserver log, we can see, GDBserver tries to single step instruction
on 0xb6e0a6e4, and destination address is 0xffff0fe0,

 stop pc is 0xb6e0a6e4
 Writing f001f0e7 to 0xffff0fe0 in process 7132
 Failed to insert breakpoint at 0xffff0fe0 (Input/output error).
 Failed to insert breakpoint at 0xffff0fe0 (-1).

(gdb) disassemble __aeabi_read_tp,+8
Dump of assembler code from 0xb6e0a6e0 to 0xb6e0a6e8:
   0xb6e0a6e0 <__aeabi_read_tp+0>:	mvn	r0, #61440	; 0xf000
   0xb6e0a6e4 <__aeabi_read_tp+4>:	sub	pc, r0, #31

however, it fails inserting breakpoint there.  This problem has already
fixed by GDB, see comments in arm-linux-tdep.c:arm_linux_software_single_step

      /* The Linux kernel offers some user-mode helpers in a high page.  We can
	 not read this page (as of 2.6.23), and even if we could then we
	 couldn't set breakpoints in it, and even if we could then the atomic
	 operations would fail when interrupted.  They are all called as
	 functions and return to the address in LR, so step to there
	 instead.  */

so we need to do the same thing in GDB side as well.  This patch adds
a new field fixup in arm_get_next_pcs_ops, so that we can fix up PC
for arm-linux target.  In this way, both GDB and GDBserver can single
step instructions going to kernel helpers.

gdb:

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

	* arch/arm-get-next-pcs.c (arm_get_next_pcs): Call
	self->ops->fixup if it isn't NULL.
	* arch/arm-get-next-pcs.h: Include gdb_vecs.h.
	(struct arm_get_next_pcs_ops) <fixup>: New field.
	* arch/arm-linux.c: Include common-regcache.h and
	arch/arm-get-next-pcs.h.
	(arm_linux_get_next_pcs_fixup): New function.
	* arch/arm-linux.h (arm_linux_get_next_pcs_fixup): Declare.
	* arm-linux-tdep.c (arm_linux_get_next_pcs_ops): Initialize
	it with arm_linux_get_next_pcs_fixup.
	(arm_linux_software_single_step): Move code to
	arm_linux_get_next_pcs_fixup.
	* arm-tdep.c (arm_get_next_pcs_ops): Initialize it.

gdb/gdbserver:

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

	* linux-arm-low.c (get_next_pcs_ops): Initialize it with
	arm_linux_get_next_pcs_fixup.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [ARM] Software single step cross kernel helpers
@ 2016-02-12 16:22 sergiodj+buildbot
  2016-02-12 17:53 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-12 16:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 01113bc1c50ff1202517377afd7162861e66846f ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 01113bc1c50ff1202517377afd7162861e66846f

[ARM] Software single step cross kernel helpers

GDB step cross kernel helpers only works if the kernel helpers are tail
called, which is the case how it is used in glibc.  See __aeabi_read_tp
in sysdeps/unix/sysv/linux/arm/aeabi_read_tp.S.  In __aeabi_read_tp,
branch/jump to the kernel helper is the last instruction, and the next
instruction address is in LR, which is in caller function.  GDB can
handle this correctly.  For example, glibc function __GI___ctype_init
calls __aeabi_read_tp

   0xb6e19b30 <__GI___ctype_init+4>:	ldr	r3, [pc, #80]	;
   0xb6e19b34 <__GI___ctype_init+8>:	bl	0xb6e0a6e0 <__aeabi_read_tp>
   0xb6e19b38 <__GI___ctype_init+12>:	ldr	r3, [pc, r3]

and __aeabi_read_tp calls kernel helper,

(gdb) disassemble __aeabi_read_tp
   0xb6fef5d0 <+0>:	mvn	r0, #61440	; 0xf000
   0xb6fef5d4 <+4>:	sub	pc, r0, #31

once GDB or GDBserver single step instruction on 0xb6fef5d4, LR is
0xb6e19b38, which is right address of next instruction to set breakpoint
on.

However, if the kernel helpers are not tail-called, the LR is still the
address in the caller function of kernel helper's caller, which isn't
the right address of next instruction to set breakpoint on.  For example,
we use kernel helper in main,

(gdb) disassemble main
....
   0x00008624 <+32>:    mov     r3, #4064       ; 0xfe0^M
   0x00008628 <+36>:    movt    r3, #65535      ; 0xffff^M
   0x0000862c <+40>:    blx     r3
   0x00008630 <+44>:    ldr     r3, [r11, #-8]

kernel helper is called on 0x0000862c and the expected next instruction
address is 0x00008630, but the LR now is the return address of main.
The problem here is LR may not have the right address because when we
single step the instruction, it isn't executed yet, so the LR isn't
updated.  This patch fix this problem by decoding instruction, if the
instruction updates LR (BL and BLX), the next instruction address is
PC + INSN_SIZE, otherwise, get the address of next instruction from LR.

gdb:

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

	* arch/arm-linux.c (arm_linux_get_next_pcs_fixup): Calculate
	nextpc according to instruction.

gdb/testsuite:

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

	* gdb.arch/arm-single-step-kernel-helper.c: New.
	* gdb.arch/arm-single-step-kernel-helper.exp: New.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [gdbserver, aarch64] Use linux_{set, get}_pc_{64, 32}bit
@ 2016-02-12 16:32 sergiodj+buildbot
  2016-02-12 19:02 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-12 16:32 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a5652c21a829088da97a525fbcd9c9912b64c9dc ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: a5652c21a829088da97a525fbcd9c9912b64c9dc

[gdbserver, aarch64] Use linux_{set,get}_pc_{64,32}bit

We can use shared functions linux_{set,get}_pc_{64,32}bit in
linux-aarch64-low.c to write and read pc.

gdb/gdbserver:

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

	* linux-aarch64-low.c (aarch64_get_pc): Call linux_get_pc_64bit
	or linux_get_pc_32bit.
	(aarch64_set_pc): Call linux_set_pc_64bit or linux_set_pc_32bit.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] i386-biarch-core.exp: Use standard_output_file
@ 2016-02-12 19:08 sergiodj+buildbot
  2016-02-12 20:11 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-12 19:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 97e9415187158a9dfb3b662888a5d7b5e3bd8244 ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: 97e9415187158a9dfb3b662888a5d7b5e3bd8244

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] 2113+ messages in thread
[parent not found: <e44e00ffffe358d91df0ec4a11563eef0c14beb4@gdb-build>]
* [binutils-gdb] testsuite regression: gdb.fortran/vla-value-sub.exp gdb.fortran/vla-value-sub-finish.exp
@ 2016-02-14  8:25 sergiodj+buildbot
  2016-02-14  8:59 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-14  8:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e9fb005c0e95e642c2e5a65c02d026b4223082e6 ***

Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Branch: master
Commit: e9fb005c0e95e642c2e5a65c02d026b4223082e6

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] 2113+ messages in thread
* [binutils-gdb] testsuite: Fix false Fortran regressions with recent gcc
@ 2016-02-14  8:44 sergiodj+buildbot
  2016-02-14 11:17 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-14  8:44 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ba881f505ba211ffee59e68617cd1a02a7b4737b ***

Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Branch: master
Commit: ba881f505ba211ffee59e68617cd1a02a7b4737b

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] 2113+ messages in thread
* [binutils-gdb] Don't print 0x for core_addr_to_string_nz
@ 2016-02-15 10:19 sergiodj+buildbot
  2016-02-15 10:52 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-15 10:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0a0da55626b632a8b8beb6c7878b866861e5daee ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 0a0da55626b632a8b8beb6c7878b866861e5daee

Don't print 0x for core_addr_to_string_nz

core_addr_to_string_nz returns string which has "0x" prefix, so don't
need to print "0x" again.  This patch is to remove the "0x".

gdb:

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

	* aarch64-tdep.c (aarch64_analyze_prologue): Remove "0x".


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Enhance GAS's .section directive so that it can take numeric values for the flags and type fields. (ELF only)
@ 2016-02-15 11:25 sergiodj+buildbot
  2016-02-15 12:03 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-15 11:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9fb71ee49fc37163697e4f34e16097928eb83d66 ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: 9fb71ee49fc37163697e4f34e16097928eb83d66

Enhance GAS's .section directive so that it can take numeric values for the flags and type fields.  (ELF only)

gas	* doc/as.texinfo (.section): Document that numeric values can now
	be used for the flags and type fields of the ELF target's .section
	directive.  Add notes about the restrictions on setting flags and
	types.
	* config/obj-elf.c (obj_elf_change_section): Allow known sections
	to be given processor specific section types.  Allow processor and
	application specific flags of a section to be set after
	definition.
	(obj_elf_parse_section_letters): Handle parsing numeric values.
	(obj_elf_section_type): Handle parsing numeric values.
	(obj_elf_section): Allow numeric type values.
	* config/obj-elf.h (obj_elf_change_section): Update prototype.
	* testsuite/gas/elf/section10.d: New test.
	* testsuite/gas/elf/section10.s: Source file for new test.
	* testsuite/gas/elf/elf.exp: Run the new test.
	* testsuite/gas/i386/ilp32/x86-64-unwind.d: Remove dependency upon
	the description of the flags produced by readelf.
	* testsuite/gas/tic6x/scomm-directive-4.d: Likewise.
	* NEWS: Mention the new feature.

bfd	* elf-bfd.h (struct bfd_elf_special_section): Use unsigned values
	for length and type fields.  Use a signed value for the
	suffix_length field.

binutils* readelf.c (get_section_type_name): Add hex prefix to offsets
	printed for LOPROC and LOOS values.  Ensure that a result is
	always returned for the V850 target, even when an unrecognised
	processor specific value is encountered.
	(process_section_headers): Display key values in the order in
	which they appear to the user.  Add the "C (compressed)" value to
	the list.

ld	* testsuite/ld-i386/pr12718.d: Remove dependency upon the
	description of the flags produced by readelf.
	* testsuite/ld-i386/pr12921.d: Likewise.
	* testsuite/ld-i386/tlsbin-nacl.rd: Likewise.
	* testsuite/ld-i386/tlsbin.rd: Likewise.
	* testsuite/ld-i386/tlsbindesc-nacl.rd: Likewise.
	* testsuite/ld-i386/tlsbindesc.rd: Likewise.
	* testsuite/ld-i386/tlsdesc-nacl.rd: Likewise.
	* testsuite/ld-i386/tlsdesc.rd: Likewise.
	* testsuite/ld-i386/tlsgdesc-nacl.rd: Likewise.
	* testsuite/ld-i386/tlsgdesc.rd: Likewise.
	* testsuite/ld-i386/tlsnopic-nacl.rd: Likewise.
	* testsuite/ld-i386/tlsnopic.rd: Likewise.
	* testsuite/ld-i386/tlspic-nacl.rd: Likewise.
	* testsuite/ld-i386/tlspic.rd: Likewise.
	* testsuite/ld-s390/tlsbin.rd: Likewise.
	* testsuite/ld-s390/tlsbin_64.rd: Likewise.
	* testsuite/ld-s390/tlspic.rd: Likewise.
	* testsuite/ld-s390/tlspic_64.rd: Likewise.
	* testsuite/ld-sh/tlsbin-2.d: Likewise.
	* testsuite/ld-sh/tlspic-2.d: Likewise.
	* testsuite/ld-tic6x/common.d: Likewise.
	* testsuite/ld-tic6x/shlib-1.rd: Likewise.
	* testsuite/ld-tic6x/shlib-1b.rd: Likewise.
	* testsuite/ld-tic6x/shlib-1r.rd: Likewise.
	* testsuite/ld-tic6x/shlib-1rb.rd: Likewise.
	* testsuite/ld-tic6x/shlib-app-1.rd: Likewise.
	* testsuite/ld-tic6x/shlib-app-1b.rd: Likewise.
	* testsuite/ld-tic6x/shlib-app-1r.rd: Likewise.
	* testsuite/ld-tic6x/shlib-app-1rb.rd: Likewise.
	* testsuite/ld-tic6x/shlib-noindex.rd: Likewise.
	* testsuite/ld-tic6x/static-app-1.rd: Likewise.
	* testsuite/ld-tic6x/static-app-1b.rd: Likewise.
	* testsuite/ld-tic6x/static-app-1r.rd: Likewise.
	* testsuite/ld-tic6x/static-app-1rb.rd: Likewise.
	* testsuite/ld-x86-64/ilp32-4-nacl.d: Likewise.
	* testsuite/ld-x86-64/ilp32-4.d: Likewise.
	* testsuite/ld-x86-64/pr12718.d: Likewise.
	* testsuite/ld-x86-64/pr12921.d: Likewise.
	* testsuite/ld-x86-64/split-by-file-nacl.rd: Likewise.
	* testsuite/ld-x86-64/split-by-file.rd: Likewise.
	* testsuite/ld-x86-64/tlsbin-nacl.rd: Likewise.
	* testsuite/ld-x86-64/tlsbin.rd: Likewise.
	* testsuite/ld-x86-64/tlsbindesc-nacl.rd: Likewise.
	* testsuite/ld-x86-64/tlsbindesc.rd: Likewise.
	* testsuite/ld-x86-64/tlsdesc-nacl.rd: Likewise.
	* testsuite/ld-x86-64/tlsdesc.rd: Likewise.
	* testsuite/ld-x86-64/tlsgdesc-nacl.rd: Likewise.
	* testsuite/ld-x86-64/tlsgdesc.rd: Likewise.
	* testsuite/ld-x86-64/tlspic-nacl.rd: Likewise.
	* testsuite/ld-x86-64/tlspic.rd: Likewise.
	* testsuite/ld-xtensa/tlsbin.rd: Likewise.
	* testsuite/ld-xtensa/tlspic.rd: Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix more testcases with standard_output_file.
@ 2016-02-15 18:15 sergiodj+buildbot
  2016-02-16  9:57 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-15 18:15 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c99dbb4246fedd500dbdd50514589fc7f95d80c0 ***

Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Branch: master
Commit: c99dbb4246fedd500dbdd50514589fc7f95d80c0

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] 2113+ messages in thread
* [binutils-gdb] Add missing gdb.arch/i386-prologue.c prototypes
@ 2016-02-15 19:08 sergiodj+buildbot
  2016-02-16 12:18 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-15 19:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a7a0a6a95bc111776129374c46edec3c3c2785cc ***

Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Branch: master
Commit: a7a0a6a95bc111776129374c46edec3c3c2785cc

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] 2113+ messages in thread
* [binutils-gdb] Add parentheses to prevent truncated addresses
@ 2016-02-16  0:16 sergiodj+buildbot
  2016-02-16 13:27 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-16  0:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4fd7268abff6f99dbbb78505f095bf1f54064db7 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 4fd7268abff6f99dbbb78505f095bf1f54064db7

Add parentheses to prevent truncated addresses

	* i386-dis.c (print_insn): Parenthesize expression to prevent
	truncated addresses.
	(OP_J): Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Remove PC from syscall_next_pc
@ 2016-02-16 13:59 sergiodj+buildbot
  2016-02-16 15:43 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-16 13:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 553cb5270f28725de86636340574644e45318fe1 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 553cb5270f28725de86636340574644e45318fe1

Remove PC from syscall_next_pc

Method syscall_next_pc of struct arm_get_next_pcs_ops has an argument
PC, which is not necessary, because PC can be got from regcache in
'struct arm_get_next_pcs'.  This patch removes the PC argument of
syscall_next_pc.

gdb:

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

	* arch/arm-get-next-pcs.h (struct arm_get_next_pcs_ops)
	<syscall_next_pc>: Remove argument PC.  Callers updated.
	* arm-linux-tdep.c (arm_linux_get_next_pcs_syscall_next_pc):
	Remove argument PC.  Get pc from regcache_read_pc.
	* arm-tdep.c (arm_get_next_pcs_syscall_next_pc): Remove
	argument PC.

gdb/gdbserver:

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

	* linux-arm-low.c (get_next_pcs_syscall_next_pc): Remove argument
	PC.  Get pc from regcache_read_pc.


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

*** TEST RESULTS FOR COMMIT b442c911ee0e7444ee63edcc7da26089f6023cb6 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: b442c911ee0e7444ee63edcc7da26089f6023cb6

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] 2113+ messages in thread
* [binutils-gdb] testsuite: Fix save-trace.exp writing outside standard output directory
@ 2016-02-16 15:12 sergiodj+buildbot
  2016-02-16 19:12 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-16 15:12 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 266b65b33e23c916e5e698d24c37f65d90645a19 ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: 266b65b33e23c916e5e698d24c37f65d90645a19

testsuite: Fix save-trace.exp writing outside standard output directory

In save-trace.exp, we want to test loading of a tracepoint definition
file with a relative path (I am not sure why in fact).  We currently use
"savetrace-relative.tr", which ends up directly in testsuite/.  If we
use [standard_output_file] on that path, it becomes absolute.  I decided
to just replace [pwd] with . (a dot) in the path given by
standard_output_file to make it relative.  However, this trick only
works because [pwd] is a prefix of the standard output directory.  So I
added a check to verify that precondition.

gdb/testsuite/ChangeLog:

	* gdb.trace/save-trace.exp: Change relative path to be in the
	standard output directory.


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

*** TEST RESULTS FOR COMMIT 4041ed778095ed74f7cb9cdaac4115597f35147c ***

Author: Don Breazeal <donb@codesourcery.com>
Branch: master
Commit: 4041ed778095ed74f7cb9cdaac4115597f35147c

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] 2113+ messages in thread
* [binutils-gdb] Whitespace cleanup for skip testcase.
@ 2016-02-16 20:52 sergiodj+buildbot
  2016-02-16 23:51 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-16 20:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 21b1f8d2fc29b7e0585dbdca72c0b8a8bf070a2e ***

Author: Doug Evans <dje@google.com>
Branch: master
Commit: 21b1f8d2fc29b7e0585dbdca72c0b8a8bf070a2e

Whitespace cleanup for skip testcase.

gdb/testsuite/ChangeLog:

	* gdb.base/skip.c: Add copyright.  Whitespace cleanup.
	* gdb.base/skip1.c: Ditto.
	* gdb.base/skip.exp: Whitespace cleanup.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
[parent not found: <b00b61e1fd95b778ec85bf314baddd1be9040d25@gdb-build>]
* [binutils-gdb] Add missing cleanup in exec_file_locate_attach
@ 2016-02-17 17:04 sergiodj+buildbot
  2016-02-17 17:37 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-17 17:04 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 88178e828a0d1af133c19d6165e4d5ee59304adf ***

Author: Gary Benson <gbenson@redhat.com>
Branch: master
Commit: 88178e828a0d1af133c19d6165e4d5ee59304adf

Add missing cleanup in exec_file_locate_attach

exec_file_locate_attach allocates memory for full_exec_path (using
either exec_file_find, source_full_path_of or xstrdup) but this
memory is never freed.  This commit adds the necessary cleanup.

gdb/ChangeLog:

	* exec.c (exec_file_locate_attach): Add missing cleanup.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Always create dynamic sections for -E/--dynamic-list
@ 2016-02-18 11:25 sergiodj+buildbot
  2016-02-18 11:57 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-18 11:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bf89386a862ace008f0152bca8bddf996d3993c8 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: bf89386a862ace008f0152bca8bddf996d3993c8

Always create dynamic sections for -E/--dynamic-list

In embedded environments, including boot loaders, the non-PIC executable
needs to export its symbols to modules loaded in the future.  We should
always create dynamic sections for -E/--dynamic-list.

bfd/

	PR ld/19617
	* elflink.c (elf_link_add_object_symbols): Always create dynamic
	sections for -E/--dynamic-list.

ld/

	PR ld/19617
	* testsuite/ld-elf/pr19617.s: New file.
	* testsuite/ld-elf/pr19617a.d: Likewise.
	* testsuite/ld-elf/pr19617b.d: Likewise.
	* testsuite/ld-elf/pr19617c.d: Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Set breakpoint condition-evaluation in forking-threads-plus-breakpoint.exp
@ 2016-02-18 12:18 sergiodj+buildbot
  2016-02-18 13:06 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-18 12:18 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 40fb20d037581bc9d4b17b6ab64ee98825cfacab ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 40fb20d037581bc9d4b17b6ab64ee98825cfacab

Set breakpoint condition-evaluation in forking-threads-plus-breakpoint.exp

Proc do_test in forking-threads-plus-breakpoint.exp has an argument
cond_bp_target, but the test doesn't use it to set
"breakpoint condition-evaluation", which is an oversight in the test.

This patch fixes it by setting "breakpoint condition-evaluation" per
$cond_bp_target.

gdb/testsuite:

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

	* gdb.threads/forking-threads-plus-breakpoint.exp (do_test):
	Set "set breakpoint condition-evaluation" per $cond_bp_target.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Remove setup_kfail server/13796 in disp-step-syscall.exp
@ 2016-02-18 13:17 sergiodj+buildbot
  2016-02-18 14:14 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-18 13:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2d5189bd3a6e2014b9b42a4bcb0df410eff1c2e1 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 2d5189bd3a6e2014b9b42a4bcb0df410eff1c2e1

Remove setup_kfail server/13796 in disp-step-syscall.exp

This patch series add fork support in target remote,

  [PATCH v2 0/3] Target remote mode fork and exec support
  https://sourceware.org/ml/gdb-patches/2015-12/msg00144.html

so GDB can be informed about the child, and adjust child correctly in
displaced stepping.  The PR server/13796 was fixed by this patch
series actually.  Test results on buildbot show this KFAIL->KPASS
change https://sourceware.org/ml/gdb-testers/2015-q4/msg10128.html

gdb/testsuite:

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

	* gdb.base/disp-step-syscall.exp (disp_step_cross_syscall):
	Don't call setup_kfail.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Intel MPX bound violation handling
@ 2016-02-18 16:46 sergiodj+buildbot
  2016-02-18 18:23 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-18 16:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 012b3a217a60cc74b802b059029c72a25d77808c ***

Author: Walfred Tedeschi <walfred.tedeschi@intel.com>
Branch: master
Commit: 012b3a217a60cc74b802b059029c72a25d77808c

Intel MPX bound violation handling

With Intel Memory Protection Extensions it was introduced the concept of
boundary violation.  A boundary violations is presented to the inferior as
a segmentation fault having SIGCODE 3.  This patch adds a
handler for a boundary violation extending the information displayed
when a bound violation is presented to the inferior.  In the stop mode
case the debugger will also display the kind of violation: "upper" or
"lower", bounds and the address accessed.
On no stop mode the information will still remain unchanged.  Additional
information about bound violations are not meaningful in that case user
does not know the line in which violation occurred as well.

When the segmentation fault handler is stop mode the out puts will be
changed as exemplified below.

The usual output of a segfault is:
Program received signal SIGSEGV, Segmentation fault
0x0000000000400d7c in upper (p=0x603010, a=0x603030, b=0x603050,
c=0x603070, d=0x603090, len=7) at i386-mpx-sigsegv.c:68
68        value = *(p + len);

In case it is a bound violation it will be presented as:
Program received signal SIGSEGV, Segmentation fault
Upper bound violation while accessing address 0x7fffffffc3b3
Bounds: [lower = 0x7fffffffc390, upper = 0x7fffffffc3a3]
0x0000000000400d7c in upper (p=0x603010, a=0x603030, b=0x603050,
c=0x603070, d=0x603090, len=7) at i386-mpx-sigsegv.c:68
68        value = *(p + len);

In mi mode the output of a segfault is:
*stopped,reason="signal-received",signal-name="SIGSEGV",
signal-meaning="Segmentation fault", frame={addr="0x0000000000400d7c",
func="upper",args=[{name="p", value="0x603010"},{name="a",value="0x603030"}
,{name="b",value="0x603050"}, {name="c",value="0x603070"},
{name="d",value="0x603090"},{name="len",value="7"}],
file="i386-mpx-sigsegv.c",fullname="i386-mpx-sigsegv.c",line="68"},
thread-id="1",stopped-threads="all",core="6"

in the case of a bound violation:
*stopped,reason="signal-received",signal-name="SIGSEGV",
signal-meaning="Segmentation fault",
sigcode-meaning="Upper bound violation",
lower-bound="0x603010",upper-bound="0x603023",bound-access="0x60302f",
frame={addr="0x0000000000400d7c",func="upper",args=[{name="p",
value="0x603010"},{name="a",value="0x603030"},{name="b",value="0x603050"},
{name="c",value="0x603070"},{name="d",value="0x603090"},
{name="len",value="7"}],file="i386-mpx-sigsegv.c",
fullname="i386-mpx-sigsegv.c",line="68"},thread-id="1",
stopped-threads="all",core="6"

2016-02-18  Walfred Tedeschi  <walfred.tedeschi@intel.com>

gdb/ChangeLog:

	* NEWS: Add entry for bound violation.
	* amd64-linux-tdep.c (amd64_linux_init_abi_common):
	Add handler for segmentation fault.
	* gdbarch.sh (handle_segmentation_fault): New.
	* gdbarch.c: Regenerate.
	* gdbarch.h: Regenerate.
	* i386-linux-tdep.c (i386_linux_handle_segmentation_fault): New.
	(SIG_CODE_BONDARY_FAULT): New define.
	(i386_linux_init_abi): Use i386_mpx_bound_violation_handler.
	* i386-linux-tdep.h (i386_linux_handle_segmentation_fault) New.
	* i386-tdep.c (i386_mpx_enabled): Add as external.
	* i386-tdep.c (i386_mpx_enabled): Add as external.
	* infrun.c (handle_segmentation_fault): New function.
	(print_signal_received_reason): Use handle_segmentation_fault.

gdb/testsuite/ChangeLog:

	* gdb.arch/i386-mpx-sigsegv.c: New file.
	* gdb.arch/i386-mpx-sigsegv.exp: New file.
	* gdb.arch/i386-mpx-simple_segv.c: New file.
	* gdb.arch/i386-mpx-simple_segv.exp: New file.

gdb/doc/ChangeLog:

	* gdb.texinfo (Signals): Add bound violation display hints for
	a SIGSEGV.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
[parent not found: <5f034a78b986d30a90030b2409c61a8660b9b48c@gdb-build>]
[parent not found: <f79a3bae8725dfe0e11b04ddfc6e6bc8f23e4e4e@gdb-build>]
* [binutils-gdb] Determine the iteration count based on wallclock instead of user+system time.
@ 2016-02-18 19:38 sergiodj+buildbot
  2016-02-18 20:32 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-18 19:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fbb7bcbeaad3aebab8935cb4ee5706017b3b9e71 ***

Author: Wei-cheng Wang <cole945@gmail.com>
Branch: master
Commit: fbb7bcbeaad3aebab8935cb4ee5706017b3b9e71

Determine the iteration count based on wallclock instead of user+system time.

gdb/testsuite/ChangeLog:

2016-02-18  Wei-cheng Wang  <cole945@gmail.com>

	* gdb.trace/tspeed.c (myclock): Return wallclock instead of
	user+system time.
	(trace_speed_test): Determine the iteration count for a time
	between 15..30 seconds.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [ARM] Add FP16 feature extension for ARMv8.2 architecture
@ 2016-02-19 14:40 sergiodj+buildbot
  2016-02-19 15:14 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-19 14:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b8ec4e871ef7650b852df9956841ee414766de59 ***

Author: Jiong Wang <jiong.wang@arm.com>
Branch: master
Commit: b8ec4e871ef7650b852df9956841ee414766de59

[ARM] Add FP16 feature extension for ARMv8.2 architecture

include/
  * opcode/arm.h (ARM_EXT2_FP16_INSN): New.

gas/
  * config/tc-arm.c (arm_ext_fp16): New.
  (arm_extensions): New entry for "fp16".


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix a seg-fault in the linker when it encounters a corrupt binary containing a reloc with no associated symbol.
@ 2016-02-19 15:34 sergiodj+buildbot
  2016-02-19 16:23 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-19 15:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 737684142b3f7dfa6d440c8363750911a8ac20ce ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: 737684142b3f7dfa6d440c8363750911a8ac20ce

Fix a seg-fault in the linker when it encounters a corrupt binary containing a reloc with no associated symbol.

	PR ld/19628
	* reloc.c (bfd_generic_get_relocated_section_contents): Stop
	processing if we encounter a reloc without an associated symbol.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Prevent a seg-fault in the linker when accessing a specially crafted, corrupt, aout binary.
@ 2016-02-19 16:10 sergiodj+buildbot
  2016-02-19 17:32 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-19 16:10 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e517df3dbf7556ddb389228d713a804594ee3c1f ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: e517df3dbf7556ddb389228d713a804594ee3c1f

Prevent a seg-fault in the linker when accessing a specially crafted, corrupt, aout binary.

	PR ld/19629
	* aoutx.h (aout_link_add_symbols): Check for out of range string
	table offsets.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Remove search_parents parameter from d_lookup_symbol_imports.
@ 2016-02-21 20:46 sergiodj+buildbot
  2016-02-21 20:50 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-21 20:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 30a6a7f035026d05b52c92c26d4cb7ea3c6d6e5c ***

Author: Iain Buclaw <ibuclaw@gdcproject.org>
Branch: master
Commit: 30a6a7f035026d05b52c92c26d4cb7ea3c6d6e5c

Remove search_parents parameter from d_lookup_symbol_imports.

gdb/ChangeLog:

	* d-namespace.c (d_lookup_symbol_imports): Remove argument
	'search_parents'.  All callers updated.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Also update recursive call to d_lookup_symbol_imports.
@ 2016-02-21 21:15 sergiodj+buildbot
  2016-02-21 21:49 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-21 21:15 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e08db6db1dd514f1c99f94bb6a9c1cfe02a1ab90 ***

Author: Iain Buclaw <ibuclaw@gdcproject.org>
Branch: master
Commit: e08db6db1dd514f1c99f94bb6a9c1cfe02a1ab90

Also update recursive call to d_lookup_symbol_imports.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix arm process record code format
@ 2016-02-22 12:26 sergiodj+buildbot
  2016-02-22 13:01 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-22 12:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 01e57735b0e8e6a613c58c271350dac2c416bb03 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 01e57735b0e8e6a613c58c271350dac2c416bb03

Fix arm process record code format

This patch fixes the various code format issues in arm process record
in arm-tdep.c, such as using tab instead of spaces.

gdb:

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

	* arm-tdep.c: Fix code format issues.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [AArch64] Remove redundant calculation of plt stub destination for veneer
@ 2016-02-22 12:34 sergiodj+buildbot
  2016-02-22 14:11 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-22 12:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9a2284679086e32c0c2a46e08b23edde6fc8be85 ***

Author: Jiong Wang <jiong.wang@arm.com>
Branch: master
Commit: 9a2284679086e32c0c2a46e08b23edde6fc8be85

[AArch64] Remove redundant calculation of plt stub destination for veneer

elfNN_aarch64_size_stubs, the caller of aarch64_type_stub has redirected
the final destination of long branch veneer to plt stub if the call
should go through it.

It's redundant to do the same check and redirect again from scratch
inside aarch64_type_stub.

bfd/
  * elfnn-aarch64. (aarch64_type_of_stub): Remove redundation calcuation
  for destination.  Remove useless function parameters.
  (elfNN_aarch64_size_stubs): Update parameters for aarch64_type_of_stub.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] gdb-gdb.py: SyntaxError: Missing parentheses in call to 'print'
@ 2016-02-22 16:37 sergiodj+buildbot
  2016-02-22 18:11 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-22 16:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ac46107c5c781894e013b10cd9fb5c98a8393d26 ***

Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Branch: master
Commit: ac46107c5c781894e013b10cd9fb5c98a8393d26

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] 2113+ messages in thread
[parent not found: <4000e47e2f3860a85a9023f3fe5950c8cc6fa507@gdb-build>]
* [binutils-gdb] Always create dynsym section with dynamic sections
@ 2016-02-23  0:43 sergiodj+buildbot
  2016-02-23  1:19 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-23  0:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1a6e6083b69dcb695e175b5dc02342391da6ba22 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 1a6e6083b69dcb695e175b5dc02342391da6ba22

Always create dynsym section with dynamic sections

We should always create the dynsym section, even if it is empty, with
dynamic sections.

	* elflink.c (_bfd_elf_link_renumber_dynsyms): Always create the
	dynsym section, even if it is empty, with dynamic sections.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix test-case ld-elf/pr19617b
@ 2016-02-23  1:19 sergiodj+buildbot
  2016-02-23  3:45 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-23  1:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2d8dcb8135e454c47bc8609e3f9d89b29ef0b8d2 ***

Author: Hans-Peter Nilsson <hp@bitrange.com>
Branch: master
Commit: 2d8dcb8135e454c47bc8609e3f9d89b29ef0b8d2

Fix test-case ld-elf/pr19617b

	* elf32-cris.c (elf_cris_discard_excess_program_dynamics): Don't
	discard unused non-function symbols when --dynamic-list-data.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix the genetation of GOT entries for the Microblaze target.
@ 2016-02-23 10:48 sergiodj+buildbot
  2016-02-23 11:23 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-23 10:48 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 47993b4af18c6ef1cad300f6393bf896d3cb5e5c ***

Author: Rich Felker <bugdal@aerifal.cx>
Branch: master
Commit: 47993b4af18c6ef1cad300f6393bf896d3cb5e5c

Fix the genetation of GOT entries for the Microblaze target.

	PR target/19516
	* elf32-microblaze.c (microblaze_elf_finish_dynamic_symbol):
	Always produce a RELATIVE reloc for a local symbol.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Increment the ABIVERSION to 5 for MIPS objects with non-executable stacks.
@ 2016-02-23 13:10 sergiodj+buildbot
  2016-02-23 13:43 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-23 13:10 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 17733f5be961baa7a47fdf1471aa6948372293d6 ***

Author: Faraz Shahbazker <faraz.shahbazker@imgtec.com>
Branch: master
Commit: 17733f5be961baa7a47fdf1471aa6948372293d6

Increment the ABIVERSION to 5 for MIPS objects with non-executable stacks.

	* bfd/elfxx-mips.c (_bfd_mips_post_process_headers): Increment
	ABIVERSION for non-executable stack.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Make linker assigned symbol dynamic only for shared object
@ 2016-02-23 13:32 sergiodj+buildbot
  2016-02-23 14:53 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-23 13:32 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6b3b0ab89663306d17927d630304dbbd36e84570 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 6b3b0ab89663306d17927d630304dbbd36e84570

Make linker assigned symbol dynamic only for shared object

Linker assigned symbols should be made dynamic by default only when
creating shared object or relocatable executable.

bfd/

	* elflink.c (bfd_elf_record_link_assignment): Check for shared
	library, instead of PIC, and don't check PDE when making linker
	assigned symbol dynamic.

ld/

	* testsuite/ld-frv/fdpic-pie-6.d: Updated.
	* testsuite/ld-mips-elf/pie-n32.d: Likewise.
	* testsuite/ld-mips-elf/pie-n64.d: Likewise.
	* testsuite/ld-mips-elf/pie-o32.d: Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] arm-tdep.c: Remove unused "to" parameters
@ 2016-02-23 18:34 sergiodj+buildbot
  2016-02-23 19:08 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-23 18:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1254566561957d2202d61e12881b0eb40d33a64c ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: 1254566561957d2202d61e12881b0eb40d33a64c

arm-tdep.c: Remove unused "to" parameters

gdb/ChangeLog:

	* arm-tdep.c (arm_decode_svc_copro): Remove "to" parameter.
	(thumb_process_displaced_insn): Likewise.
	(arm_process_displaced_insn): Adjust calls.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Extend "skip" command to support -file, -gfile, -function, -rfunction.
@ 2016-02-23 21:37 sergiodj+buildbot
  2016-02-23 22:12 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-23 21:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cce0e92333b872cfe036aae611b6b5d61cf58186 ***

Author: Doug Evans <dje@google.com>
Branch: master
Commit: cce0e92333b872cfe036aae611b6b5d61cf58186

Extend "skip" command to support -file, -gfile, -function, -rfunction.

gdb/ChangeLog:

	Extend "skip" command to support -file, -gfile, -function, -rfunction.
	* NEWS: Document new features.
	* skip.c: #include "fnmatch.h", "gdb_regex.h".
	(skiplist_entry) <file>: Renamed from filename.
	<function>: Renamed from function_name.
	<file_is_glob, function_is_regexp>: New members.
	<compiled_function_regexp, compiled_function_regexp_is_valid>:
	New members.
	(make_skip_entry): New function.
	(free_skiplist_entry, free_skiplist_entry_cleanup): New functions.
	(make_free_skiplist_entry_cleanup): New function.
	(skip_file_command): Update.
	(skip_function, skip_function_command): Update.
	(compile_skip_regexp): New functions.
	(skip_command): Add support for new options.
	(skip_info): Update.
	(skip_file_p, skip_gfile_p): New functions.
	(skip_function_p, skip_rfunction_p): New functions.
	(function_name_is_marked_for_skip): Update and simplify.
	(_initialize_step_skip): Update.
	* symtab.c: #include "fnmatch.h".
	(compare_glob_filenames_for_search): New function.
	* symtab.h (compare_glob_filenames_for_search): Declare.
	* utils.c (count_path_elements): New function.
	(strip_leading_path_elements): New function.
	* utils.h (count_path_elements): Declare.
	(strip_leading_path_elements): Declare.

gdb/doc/ChangeLog:

	* gdb.texinfo (Skipping Over Functions and Files): Document new
	options to "skip" command.  Update docs of output of "info skip".

gdb/testsuite/ChangeLog:

	* gdb.base/skip.c (test_skip): New function.
	(end_test_skip_file_and_function): New function.
	(test_skip_file_and_function): New function.
	* gdb.base/skip1.c (test_skip): New function.
	(skip1_test_skip_file_and_function): New function.
	* gdb.base/skip.exp: Add tests for new skip options.
	* gdb.base/skip-solib.exp: Update expected output.
	* gdb.perf/skip-command.cc: New file.
	* gdb.perf/skip-command.exp: New file.
	* gdb.perf/skip-command.py: New file.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Build unavailable-stack frames for tracepoint.
@ 2016-02-24  3:22 sergiodj+buildbot
  2016-02-24  4:03 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-24  3:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 50ae56ec464580492a5f987f658acc6ad82131b6 ***

Author: Wei-cheng Wang <cole945@gmail.com>
Branch: master
Commit: 50ae56ec464580492a5f987f658acc6ad82131b6

Build unavailable-stack frames for tracepoint.

gdb/ChangeLog:

2016-02-24  Wei-cheng Wang  <cole945@gmail.com>

	* rs6000-tdep.c (rs6000_frame_cache, rs6000_frame_this_id): Handle
	unavailable PC/SP to build unavailable frame.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Set plt_got.offset to (bfd_vma) -1
@ 2016-02-24 13:54 sergiodj+buildbot
  2016-02-24 14:38 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-24 13:54 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 13f422778ff5307dad1f66d25a1d211bb8f76a8b ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 13f422778ff5307dad1f66d25a1d211bb8f76a8b

Set plt_got.offset to (bfd_vma) -1

Since plt_got.offset may be updated in x86 allocate_dynrelocs, set
plt_got.offset to (bfd_vma) -1 when setting needs_plt to 0.

	* elf32-i386.c (elf_i386_allocate_dynrelocs): Set plt_got.offset
	to (bfd_vma) -1 when setting needs_plt to 0.
	* elf64-x86-64.c (elf_x86_64_allocate_dynrelocs): Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [OPCODE][ARM]Correct disassembler for cdp/cdp2, mcr/mcr2, mrc/mrc2, ldc/ldc2, stc/stc2
@ 2016-02-24 14:09 sergiodj+buildbot
  2016-02-24 16:56 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-24 14:09 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8afc7bea4018bf535902503c9a25dd4a96dfa3ca ***

Author: Renlin Li <renlin.li@arm.com>
Branch: master
Commit: 8afc7bea4018bf535902503c9a25dd4a96dfa3ca

[OPCODE][ARM]Correct disassembler for cdp/cdp2, mcr/mcr2, mrc/mrc2, ldc/ldc2, stc/stc2

opcodes/

2016-02-24  Renlin Li  <renlin.li@arm.com>

	* arm-dis.c (print_insn_coprocessor): Check co-processor number for
	cpd/cpd2, mcr/mcr2, mrc/mrc2, ldc/ldc2, stc/stc2.

gas/

2016-02-24  Renlin Li  <renlin.li@arm.com>

	* testsuite/gas/arm/copro.s: Use coprocessor other than 10, 11.
	* testsuite/gas/arm/copro.d: Update.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [OPCODES][ARM][1/3]Add armv8.2 fp16 instruction dissembler support.
@ 2016-02-24 14:22 sergiodj+buildbot
  2016-02-24 19:52 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-24 14:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b0c11777665276f8e9b590bbe4832a7c66f5093d ***

Author: Renlin Li <renlin.li@arm.com>
Branch: master
Commit: b0c11777665276f8e9b590bbe4832a7c66f5093d

[OPCODES][ARM][1/3]Add armv8.2 fp16 instruction dissembler support.

opcodes/

2016-02-24  Renlin Li  <renlin.li@arm.com>

	* arm-dis.c (coprocessor_opcodes): Add fp16 instruction entries.
	(print_insn_coprocessor): Support fp16 instruction.

gas/

2016-02-24  Renlin Li  <renlin.li@arm.com>

	* testsuite/gas/arm/copro.d: Adjust output.
	* testsuite/gas/arm/copro.s: Adjust co-processor num.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Revert "ABS32"
@ 2016-02-24 15:09 sergiodj+buildbot
  2016-02-24 20:29 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-24 15:09 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 92d77487b3dbfd934c5565bab09e0f3051e0b08d ***

Author: Renlin Li <renlin.li@arm.com>
Branch: master
Commit: 92d77487b3dbfd934c5565bab09e0f3051e0b08d

Revert "ABS32"

This reverts commit 30bdf5c82e5734ac9f0b18eb7af631806d419270.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] powerpc: Support z-point type in gdbserver.
@ 2016-02-24 17:45 sergiodj+buildbot
  2016-02-24 21:31 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-24 17:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 657f9cde9d531c9929bef9e02a8064101d568f50 ***

Author: Wei-cheng Wang <cole945@gmail.com>
Branch: master
Commit: 657f9cde9d531c9929bef9e02a8064101d568f50

powerpc: Support z-point type in gdbserver.

Support z-point, so tracepoints and breakpoints can be inserted at the same
location.

gdb/gdbserver/ChangeLog:

2016-02-24  Wei-cheng Wang  <cole945@gmail.com>

	* linux-ppc-low.c (ppc_supports_z_point_type): New function:
	(ppc_insert_point, ppc_remove_point): Insert/remove z-packet breakpoints.
	(ppc64_emit_ops_vector): Add target ops - ppc_supports_z_point_type,
	ppc_insert_point, ppc_remove_point.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Move new skip features to proper section (post 7.11).
@ 2016-02-24 18:24 sergiodj+buildbot
  2016-02-24 22:49 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-24 18:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d2dffb8d3be366d4d02de06e92c24c9abdb0adfc ***

Author: Doug Evans <dje@google.com>
Branch: master
Commit: d2dffb8d3be366d4d02de06e92c24c9abdb0adfc

Move new skip features to proper section (post 7.11).


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Move tfile-avx.exp to tracefile-pseudo-reg.exp
@ 2016-02-24 19:30 sergiodj+buildbot
  2016-02-24 23:50 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-24 19:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 861ca91fc65b9a53b807f6d5c5253fc33f92e7d8 ***

Author: Antoine Tremblay <antoine.tremblay@ericsson.com>
Branch: master
Commit: 861ca91fc65b9a53b807f6d5c5253fc33f92e7d8

Move tfile-avx.exp to tracefile-pseudo-reg.exp

As it is planned to add more architectures to this test, rename to a more
generic name.

gdb/testsuite/ChangeLog:

	* gdb.trace/tfile-avx.c: Move to...
	* gdb.trace/tracefile-pseudo-reg.c: Here.
	* gdb.trace/tfile-avx.exp: Move to...
	* gdb.trace/tracefile-pseudo-reg.exp: Here.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Handle MIPS Linux SIGTRAP siginfo.si_code values
@ 2016-02-24 23:11 sergiodj+buildbot
  2016-02-25  3:16 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-24 23:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e7ad2f145c05bc60b1cd2796c8f3b72f02e3e730 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: e7ad2f145c05bc60b1cd2796c8f3b72f02e3e730

Handle MIPS Linux SIGTRAP siginfo.si_code values

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

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

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

Basically, this commit:

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

- Adds GDB_ARCH_IS_TRAP_HWBKPT.

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

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

gdb/ChangeLog:
2016-02-24  Pedro Alves  <palves@redhat.com>

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

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

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


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Update symbol version for symbol from linker script
@ 2016-02-24 23:37 sergiodj+buildbot
  2016-02-25  4:56 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-24 23:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0f550b3df1d4ae31d12505cf93981313c9c6dd25 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 0f550b3df1d4ae31d12505cf93981313c9c6dd25

Update symbol version for symbol from linker script

We need to update symbol version for symbols from linker script.

bfd/

	PR ld/19698
	* elflink.c (bfd_elf_record_link_assignment): Set versioned if
	symbol version is unknown.

ld/

	PR ld/19698
	* testsuite/ld-elf/pr19698.d: New file.
	* testsuite/ld-elf/pr19698.s: Likewise.
	* testsuite/ld-elf/pr19698.t: Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Add elf_x86_64_need_pic
@ 2016-02-25 12:24 sergiodj+buildbot
  2016-02-25 12:59 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-25 12:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ef77d6af7cade17c566e4d1ecff098b841972f17 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: ef77d6af7cade17c566e4d1ecff098b841972f17

Add elf_x86_64_need_pic

Add elf_x86_64_need_pic and replace x86_64_elf_howto_table[r_type].name
with howto->name.

	* elf64-x86-64.c (elf_x86_64_need_pic): New function.
	(elf_x86_64_relocate_section): Use it.  Replace
	x86_64_elf_howto_table[r_type] with howto.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Map registers to remote numbers when encoding an ax_reg or ax_reg_mask operation
@ 2016-02-25 14:46 sergiodj+buildbot
  2016-02-25 15:22 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-25 14:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1eb7c2d886c0faac42d2b68862b0e6b0d3182d98 ***

Author: Antoine Tremblay <antoine.tremblay@ericsson.com>
Branch: master
Commit: 1eb7c2d886c0faac42d2b68862b0e6b0d3182d98

Map registers to remote numbers when encoding an ax_reg or ax_reg_mask operation

When encoding the agent expression operation ax_reg or ax_reg_mask, the
register number used is internal to GDB. However GDBServer expects a tdesc
based number.

This usually does not cause a problem since at the moment, for raw
registers GDBServer R trace action ignores the register mask and just
collects all registers.

It can be a problem, however with pseudo registers on some platforms if the
tdesc number doesn't match the GDB internal register number.

This is the case with ARM, the upcoming ARM tracepoint support, fails
these test cases without this patch:

gdb.trace/collection.exp: collect register locals collectively:*

GDBSever would exit with: unhandled register size
Since the register number is not mapped.

This patch fixes these issues by calling gdbarch_remote_register_number
before encoding the register number in the ax_reg or ax_reg_mask operation.

Tested on x86 native-gdbserver no regressions observed.

gdb/ChangeLog:

	* ax-general.c (ax_reg): Call gdbarch_remote_register_number.
	(ax_reg_mask): Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
[parent not found: <7337a6f2297cdd91bb852b479b284e5796d62cc9@gdb-build>]
* [binutils-gdb] Remove gdb.base/branches.c
@ 2016-02-25 17:22 sergiodj+buildbot
  2016-02-25 21:44 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-25 17:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6cb59ff1111c1d5e955ca0eeddab6f03db0fbfb7 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 6cb59ff1111c1d5e955ca0eeddab6f03db0fbfb7

Remove gdb.base/branches.c

This patch removes gdb.base/branches.c which was added by the following
commit, but it is not used at all.

commit ea8122af1432abdeb256b2c669eb3d0cf8cb97bf
Author: John Metzler <jmetzler@cygnus>
Date:   Thu Apr 16 17:56:11 1998 +0000

    Thu Apr 16 10:52:34 1998  John Metzler  <jmetzler@cygnus.com>

        * gdb.base/branches.c: Code with lots of loops and
        subroutines. Used to test gdbs ability to single step through PC
        changes, especially to test mips-tdep.c:mips_next_pc

gdb/testsuite:

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

	* gdb.base/branches.c: Remove.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
[parent not found: <678b48b7cf0bd518ebc234bda98229cc602c2a45@gdb-build>]
* [binutils-gdb] avoid compiler warnings in remote-m32r-sdi.c
@ 2016-02-25 17:42 sergiodj+buildbot
  2016-02-25 23:25 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-25 17:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1547ef64562ebbfcdc768ce93979f09bdd119b11 ***

Author: Doug Evans <dje@google.com>
Branch: master
Commit: 1547ef64562ebbfcdc768ce93979f09bdd119b11

avoid compiler warnings in remote-m32r-sdi.c

gdb/ChangeLog:

	* remote-m32r-sdi.c (recv_char_data): Initialize val to avoid
	compiler warning.
	(recv_long_data): Ditto.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
[parent not found: <ae91f6253926e4dadebcae90772f4f5a5bd06056@gdb-build>]
[parent not found: <ab50308758bfde9ab7b50e6def65e20f0b560702@gdb-build>]
* [binutils-gdb] Fix powerpc64 -r --save-restore-funcs
@ 2016-02-26 13:00 sergiodj+buildbot
  2016-02-26 13:48 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-26 13:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b32547cd11bec3baf53e0dedf3c733cd3e0839f6 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: b32547cd11bec3baf53e0dedf3c733cd3e0839f6

Fix powerpc64 -r --save-restore-funcs

	* elf64-ppc.c (create_linkage_sections): Create sfpr when
	save_restore_funcs, rest of sections when not relocatable.
	(ppc64_elf_init_stub_bfd): Always call create_linkage_sections.
	(sfpr_define): Define all symbols on emitted code.
	(ppc64_elf_func_desc_adjust): Adjust for sfpr now being created
	when relocatable.  Move sfpr_define loop earlier.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [x86] Resolve non-PIC undefweak symbols in executable
@ 2016-02-26 13:10 sergiodj+buildbot
  2016-02-26 15:29 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-26 13:10 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT aec6b87e0b66d707ead62ca40d220ee78b4cf5a5 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: aec6b87e0b66d707ead62ca40d220ee78b4cf5a5

[x86] Resolve non-PIC undefweak symbols in executable

For i386 and x86-64, non-PIC references to undefined weak symbols are
resolved without dynamic relocation when creating executable.  Resolved
undefined weak symbols are removed from the dynamic symbol table in
executable.  One exception is on i386, we need resolved undefined weak
symbols in the dynamic symbol table in PIE if input relocatable files
contain branchs without PLT so that we can branch to 0 with dynamic
relocation in text section.

This makes behaviors of dynamic executable and position independent
executable predictable with mixed PIC and non-PIC references to undefined
weak symbols.  If all references to undefined weak symbols are PIC,
dynamic relocations against undefined weak symbols will be generated
in executable unless -z nodynamic-undefined-weak is passed to linker.

bfd/

	PR ld/19636
	PR ld/19704
	PR ld/19719
	* elf32-i386.c (UNDEFINED_WEAK_RESOLVED_TO_ZERO): New.
	(elf_i386_link_hash_entry): Add has_got_reloc and
	has_non_got_reloc.
	(elf_i386_link_hash_table): Add interp.
	(elf_i386_link_hash_newfunc): Initialize has_got_reloc and
	has_non_got_reloc.
	(elf_i386_copy_indirect_symbol): Copy has_got_reloc and
	has_non_got_reloc.
	(elf_i386_check_relocs): Set has_got_reloc and has_non_got_reloc.
	(elf_i386_fixup_symbol): New function.
	(elf_i386_pie_finish_undefweak_symbol): Likewise.
	(elf_i386_allocate_dynrelocs): Don't allocate space for dynamic
	relocations and discard relocations against resolved undefined
	weak symbols in executable.  Don't make resolved undefined weak
	symbols in executable dynamic.  Keep dynamic non-GOT/non-PLT
	relocation against undefined weak symbols in PIE.
	(elf_i386_size_dynamic_sections): Set interp to .interp section.
	(elf_i386_relocate_section): Don't generate dynamic relocations
	against resolved undefined weak symbols in PIE, except for
	R_386_PC32.
	(elf_i386_finish_dynamic_symbol): Keep PLT/GOT entries without
	dynamic PLT/GOT relocations for resolved undefined weak symbols.
	Don't generate dynamic relocation against resolved undefined weak
	symbol in executable.
	(elf_i386_finish_dynamic_sections): Call
	elf_i386_pie_finish_undefweak_symbol on all symbols in PIE.
	(elf_backend_fixup_symbol): New.
	* elf64-x86-64.c (UNDEFINED_WEAK_RESOLVED_TO_ZERO): New.
	(elf_x86_64_link_hash_entry): Add has_got_reloc and
	has_non_got_reloc.
	(elf_x86_64_link_hash_table): Add interp.
	(elf_x86_64_link_hash_newfunc): Initialize has_got_reloc and
	has_non_got_reloc.
	(elf_x86_64_copy_indirect_symbol): Copy has_got_reloc and
	has_non_got_reloc.
	(elf_x86_64_check_relocs): Set has_got_reloc and
	has_non_got_reloc.
	(elf_x86_64_fixup_symbol): New function.
	(elf_x86_64_pie_finish_undefweak_symbol): Likewise.
	(elf_x86_64_allocate_dynrelocs): Don't allocate space for dynamic
	relocations and discard relocations against resolved undefined
	weak symbols in executable.  Don't make resolved undefined weak
	symbols in executable dynamic.
	(elf_x86_64_size_dynamic_sections): Set interp to .interp section.
	(elf_x86_64_relocate_section): Check relocation overflow for
	dynamic relocations against unresolved weak undefined symbols.
	Don't generate dynamic relocations against resolved weak
	undefined symbols in PIE.
	(elf_x86_64_finish_dynamic_symbol): Keep PLT/GOT entries without
	dynamic PLT/GOT relocations for resolved undefined weak symbols.
	Don't generate dynamic relocation against resolved undefined weak
	symbol in executable.
	(elf_x86_64_finish_dynamic_sections): Call
	elf_x86_64_pie_finish_undefweak_symbol on all symbols in PIE.
	(elf_backend_fixup_symbol): New.

include/

	PR ld/19636
	PR ld/19704
	PR ld/19719
	* bfdlink.h (bfd_link_info): Add dynamic_undefined_weak.

ld/

	PR ld/19636
	PR ld/19704
	PR ld/19719
	* Makefile.am (ELF_X86_DEPS): Add dynamic_undefined_weak.sh.
	* Makefile.in: Regenerated.
	* NEWS: Mention -z nodynamic-undefined-weak.
	* ld.texinfo: Document -z nodynamic-undefined-weak.
	* ldmain.c (main): Initialize dynamic_undefined_weak to -1.
	* emulparams/dynamic_undefined_weak.sh: New file.
	* emulparams/elf32_x86_64.sh: Source dynamic_undefined_weak.sh.
	* emulparams/elf_i386.sh: Likewise.
	* emulparams/elf_i386_be.sh: Likewise.
	* emulparams/elf_i386_chaos.sh: Likewise.
	* emulparams/elf_i386_ldso.sh: Likewise.
	* emulparams/elf_i386_vxworks.sh: Likewise.
	* emulparams/elf_iamcu.sh: Likewise.
	* emulparams/elf_k1om.sh: Likewise.
	* emulparams/elf_l1om.sh: Likewise.
	* emulparams/elf_x86_64.sh: Likewise.
	* emulparams/extern_protected_data.sh (PARSE_AND_LIST_OPTIONS):
	Append.
	(PARSE_AND_LIST_ARGS_CASE_Z): Likewise.
	* testsuite/ld-elf/pr19719a.c: New file.
	* testsuite/ld-elf/pr19719b.c: Likewise.
	* testsuite/ld-elf/pr19719c.c: Likewise.
	* testsuite/ld-elf/pr19719d.c: Likewise.
	* testsuite/ld-i386/pr19636-1.s: Likewise.
	* testsuite/ld-i386/pr19636-1a.d: Likewise.
	* testsuite/ld-i386/pr19636-1b.d: Likewise.
	* testsuite/ld-i386/pr19636-1c.d: Likewise.
	* testsuite/ld-i386/pr19636-1d-nacl.d: Likewise.
	* testsuite/ld-i386/pr19636-1d.d: Likewise.
	* testsuite/ld-i386/pr19636-1e.d: Likewise.
	* testsuite/ld-i386/pr19636-1f.d: Likewise.
	* testsuite/ld-i386/pr19636-1g.d: Likewise.
	* testsuite/ld-i386/pr19636-1h.d: Likewise.
	* testsuite/ld-i386/pr19636-1i.d: Likewise.
	* testsuite/ld-i386/pr19636-2.s: Likewise.
	* testsuite/ld-i386/pr19636-2a.d: Likewise.
	* testsuite/ld-i386/pr19636-2b.d: Likewise.
	* testsuite/ld-i386/pr19636-2c-nacl.d: Likewise.
	* testsuite/ld-i386/pr19636-2c.d: Likewise.
	* testsuite/ld-i386/pr19636-2d-nacl.d: Likewise.
	* testsuite/ld-i386/pr19636-2d.d: Likewise.
	* testsuite/ld-i386/pr19636-2e-nacl.d: Likewise.
	* testsuite/ld-i386/pr19636-2e.d: Likewise.
	* testsuite/ld-i386/pr19636-3.s: Likewise.
	* testsuite/ld-i386/pr19636-3a.d: Likewise.
	* testsuite/ld-i386/pr19636-3b.d: Likewise.
	* testsuite/ld-i386/pr19636-3c.d: Likewise.
	* testsuite/ld-i386/pr19636-3d.d: Likewise.
	* testsuite/ld-i386/pr19636-3e.d: Likewise.
	* testsuite/ld-i386/pr19636-3f.d: Likewise.
	* testsuite/ld-i386/pr19636-3g.d: Likewise.
	* testsuite/ld-i386/pr19636-4.s: Likewise.
	* testsuite/ld-i386/pr19636-4a.d: Likewise.
	* testsuite/ld-i386/pr19636-4b.d: Likewise.
	* testsuite/ld-i386/pr19636-4c.d: Likewise.
	* testsuite/ld-i386/pr19636-4d.d: Likewise.
	* testsuite/ld-i386/pr19704.out: Likewise.
	* testsuite/ld-i386/pr19704a.c: Likewise.
	* testsuite/ld-i386/pr19704b.c: Likewise.
	* testsuite/ld-x86-64/pr19636-1.s: Likewise.
	* testsuite/ld-x86-64/pr19636-1a.d: Likewise.
	* testsuite/ld-x86-64/pr19636-1b.d: Likewise.
	* testsuite/ld-x86-64/pr19636-1c.d: Likewise.
	* testsuite/ld-x86-64/pr19636-1d.d: Likewise.
	* testsuite/ld-x86-64/pr19636-1e.d: Likewise.
	* testsuite/ld-x86-64/pr19636-1f.d: Likewise.
	* testsuite/ld-x86-64/pr19636-1g.d: Likewise.
	* testsuite/ld-x86-64/pr19636-2.s: Likewise.
	* testsuite/ld-x86-64/pr19636-2a.d: Likewise.
	* testsuite/ld-x86-64/pr19636-2b.d: Likewise.
	* testsuite/ld-x86-64/pr19636-2c.d: Likewise.
	* testsuite/ld-x86-64/pr19636-2d-nacl.d: Likewise.
	* testsuite/ld-x86-64/pr19636-2d.d: Likewise.
	* testsuite/ld-x86-64/pr19636-2e.d: Likewise.
	* testsuite/ld-x86-64/pr19636-2f.d: Likewise.
	* testsuite/ld-x86-64/pr19636-2g.d: Likewise.
	* testsuite/ld-x86-64/pr19636-2h.d: Likewise.
	* testsuite/ld-x86-64/pr19636-2i.d: Likewise.
	* testsuite/ld-x86-64/pr19636-3.s: Likewise.
	* testsuite/ld-x86-64/pr19636-3a.d: Likewise.
	* testsuite/ld-x86-64/pr19636-3b.d: Likewise.
	* testsuite/ld-x86-64/pr19636-3c.d: Likewise.
	* testsuite/ld-x86-64/pr19636-3d.d: Likewise.
	* testsuite/ld-x86-64/pr19704.out: Likewise.
	* testsuite/ld-x86-64/pr19704a.c: Likewise.
	* testsuite/ld-x86-64/pr19704b.c: Likewise.
	* testsuite/ld-elf/shared.exp (mix_pic_and_non_pic): New.
	Run mix_pic_and_non_pic.
	* testsuite/ld-i386/i386.exp (undefined_weak): New.
	Run undefined_weak and PR ld/19636 tests.
	* testsuite/ld-x86-64/x86-64.exp: Likewise.
	* testsuite/ld-x86-64/pr13082-3b.d: Updated.
	* testsuite/ld-x86-64/pr13082-4b.d: Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Record right reg num of thumb special data instructions
@ 2016-02-26 15:51 sergiodj+buildbot
  2016-02-26 21:43 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-26 15:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1f33efec7c6d1357d7e867176cfb88942fc513a8 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 1f33efec7c6d1357d7e867176cfb88942fc513a8

Record right reg num of thumb special data instructions

When GDB decodes these thumb special data instructions, such as 'mov sp, r7'
the Rd is got incorrectly.  According to the arch reference manual, the Rd
is DN:Rdn, in which DN is bit 7 and Rdn is bits 0 to 2.  This patch fixes it.

gdb:

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

	* arm-tdep.c (thumb_record_ld_st_reg_offset): Fix the register
	number of Rd.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix various bugs in arm_record_exreg_ld_st_insn
@ 2016-02-26 16:00 sergiodj+buildbot
  2016-02-26 23:29 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-26 16:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9fde51ed303ea3ecbaa7c0084ea417e775a5db29 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 9fde51ed303ea3ecbaa7c0084ea417e775a5db29

Fix various bugs in arm_record_exreg_ld_st_insn

This patch fixes various bugs in arm_record_exreg_ld_st_insn, and use
gdb.reverse/insn-reverse.c to test more arm instructions.

 - Set flag SINGLE_REG correctly.  In the arch reference manual,
   SING_REG is true when the bit 8 of instruction is zero.
 - Record the right D registers for instructions changing S registers.
 - Fix the order of length and address in record_buf_mem array.
 - Shift the offset by 2 instead of by 24.

This patch also fixes one internal error,

(gdb) PASS: gdb.reverse/finish-precsave.exp: BP at end of main
continue^M
Continuing.^M
../../binutils-gdb/gdb/utils.c:1072: internal-error: virtual memory exhausted.^M
A problem internal to GDB has been detected,FAIL: gdb.reverse/finish-precsave.exp: run to end of main (GDB internal error)

gdb:

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

	* arm-tdep.c (arm_record_exreg_ld_st_insn): Set 'single_reg'
	per bit 8.  Check bit 20 instead of bit 4 for VMOV
	instruction.  Record D registers for instructions changing
	S registers.  Change of the order of length and address
	in record_buf_mem array.

gdb/testsuite:

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

	* gdb.reverse/insn-reverse.c [__arm__] (ext_reg_load): New.
	[__arm__] (ext_reg_mov, ext_reg_push_pop): New.
	(testcases): Update.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Rename gdb.reverse/aarch64.{exp, c} to gdb.reverse/insn-reverse.{exp, c}
@ 2016-02-26 16:01 sergiodj+buildbot
  2016-02-26 20:01 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-26 16:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ce90fefec908ee50ae5a3b22b03447df638a54c1 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: ce90fefec908ee50ae5a3b22b03447df638a54c1

Rename gdb.reverse/aarch64.{exp,c} to gdb.reverse/insn-reverse.{exp,c}

gdb/testsuite:

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

	* gdb.reverse/aarch64.c: Rename to ...
	* gdb.reverse/insn-reverse.c: ... it.
	* gdb.reverse/aarch64.exp: Rename to ...
	* gdb.reverse/insn-reverse.exp: ... it.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Optimize x86 GOT32X/GOTPCRELX relocations
@ 2016-02-26 17:52 sergiodj+buildbot
  2016-02-27  1:12 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-26 17:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bae420ef26f4331415b0503141c5931318025906 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: bae420ef26f4331415b0503141c5931318025906

Optimize x86 GOT32X/GOTPCRELX relocations

R_386_GOT32X, R_X86_64_GOTPCRELX and R_X86_64_REX_GOTPCRELX relocations
retrieve the symbol address via its GOT slot.  If the symbol address is
known at the link-time, we can use it directly by changing instruction
encoding.  Indirect branch can only be converted to PC relative direct
branch.  MOV can be changed to LEA or encoded differently with signed
address.  The subset of binary operations can be encoded only with
signed address.

If undefined weak symbol is resolved to zero link-time, we can use it
as address.  Zero addresss can't used with PC relative direct branch
when PIC is true since the current PC is unknown.  In 64-bit, 32-bit
relocation for PC relatiave direct branch to zero may also overflow.

If this optimization causes relocation overflow, --no-relax can be used
to work around it.

bfd/

	PR ld/19609
	* elf32-i386.c (elf_i386_convert_load): Convert to R_386_32 for
	load with locally bound symbols if PIC is false or there is no
	base register.  Optimize branch to 0 if PIC is false.
	(elf_i386_relocate_section): Don't generate dynamic relocations
	against undefined weak symbols if PIC is false.
	* elf64-x86-64.c (elf_x86_64_convert_load): Disable optimization
	if we can't estimate relocation overflow with --no-relax.
	Convert to R_X86_64_32S/R_X86_64_32 for load with locally bound
	symbols if PIC is false.  Optimize branch to 0 if PIC is false.
	(elf_x86_64_relocate_section): Don't generate dynamic relocations
	against undefined weak symbols if PIC is false.

ld/

	PR ld/19609
	* testsuite/ld-i386/got1.dd: Updated.
	* testsuite/ld-i386/lea1c.d: Likewise.
	* testsuite/ld-i386/load1-nacl.d: Likewise.
	* testsuite/ld-i386/load1.d: Likewise.
	* testsuite/ld-i386/load4b.d: Likewise.
	* testsuite/ld-i386/load5b.d: Likewise.
	* testsuite/ld-i386/mov1b.d: Likewise.
	* testsuite/ld-x86-64/mov1b.d: Likewise.
	* testsuite/ld-x86-64/mov1d.d: Likewise.
	* testsuite/ld-ifunc/ifunc-21-i386.d: Likewise.
	* testsuite/ld-ifunc/ifunc-21-x86-64.d: Likewise.
	* testsuite/ld-ifunc/ifunc-22-i386.d: Likewise.
	* testsuite/ld-ifunc/ifunc-22-x86-64.d: Likewise.
	* testsuite/ld-x86-64/gotpcrel1.dd: Likewise.
	* testsuite/ld-x86-64/lea1a.d: Likewise.
	* testsuite/ld-x86-64/lea1b.d: Likewise.
	* testsuite/ld-x86-64/lea1c.d: Likewise.
	* testsuite/ld-x86-64/lea1d.d: Likewise.
	* testsuite/ld-x86-64/lea1e.d: Likewise.
	* testsuite/ld-x86-64/lea1f.d: Likewise.
	* testsuite/ld-x86-64/mov1b.d: Likewise.
	* testsuite/ld-x86-64/mov1d.d: Likewise.
	* testsuite/ld-x86-64/pr13082-3b.d: Likewise.
	* testsuite/ld-x86-64/pr13082-4b.d: Likewise.
	* testsuite/ld-x86-64/lea1.s: Add tests for 32-bit registers.
	* testsuite/ld-i386/pr19609-1.s: New file.
	* testsuite/ld-i386/pr19609-1a.d: Likewise.
	* testsuite/ld-i386/pr19609-1b.d: Likewise.
	* testsuite/ld-i386/pr19609-1c.d: Likewise.
	* testsuite/ld-i386/pr19609-1d.d: Likewise.
	* testsuite/ld-i386/pr19609-1e.d: Likewise.
	* testsuite/ld-i386/pr19609-1f.d: Likewise.
	* testsuite/ld-i386/pr19609-1g.d: Likewise.
	* testsuite/ld-i386/pr19609-1h.d: Likewise.
	* testsuite/ld-i386/pr19609-1i.d: Likewise.
	* testsuite/ld-i386/pr19609-2.s: Likewise.
	* testsuite/ld-i386/pr19609-2a.d: Likewise.
	* testsuite/ld-i386/pr19609-2b.d: Likewise.
	* testsuite/ld-i386/pr19609-2c.d: Likewise.
	* testsuite/ld-i386/undefweak.s: Likewise.
	* testsuite/ld-i386/undefweaka.d: Likewise.
	* testsuite/ld-i386/undefweakb.d: Likewise.
	* testsuite/ld-x86-64/pr13082-3c.d: Likewise.
	* testsuite/ld-x86-64/pr13082-3d.d: Likewise.
	* testsuite/ld-x86-64/pr19609-1.s: Likewise.
	* testsuite/ld-x86-64/pr19609-1a.d: Likewise.
	* testsuite/ld-x86-64/pr19609-1b.d: Likewise.
	* testsuite/ld-x86-64/pr19609-1c.d: Likewise.
	* testsuite/ld-x86-64/pr19609-1d.d: Likewise.
	* testsuite/ld-x86-64/pr19609-1e.d: Likewise.
	* testsuite/ld-x86-64/pr19609-1f.d: Likewise.
	* testsuite/ld-x86-64/pr19609-1g.d: Likewise.
	* testsuite/ld-x86-64/pr19609-1h.d: Likewise.
	* testsuite/ld-x86-64/pr19609-1i.d: Likewise.
	* testsuite/ld-x86-64/pr19609-1j.d: Likewise.
	* testsuite/ld-x86-64/pr19609-1k.d: Likewise.
	* testsuite/ld-x86-64/pr19609-1l.d: Likewise.
	* testsuite/ld-x86-64/pr19609-1m.d: Likewise.
	* testsuite/ld-x86-64/pr19609-2.s: Likewise.
	* testsuite/ld-x86-64/pr19609-2a.d: Likewise.
	* testsuite/ld-x86-64/pr19609-2b.d: Likewise.
	* testsuite/ld-x86-64/pr19609-2c.d: Likewise.
	* testsuite/ld-x86-64/pr19609-2d.d: Likewise.
	* testsuite/ld-x86-64/pr19609-3.s: Likewise.
	* testsuite/ld-x86-64/pr19609-3a.d: Likewise.
	* testsuite/ld-x86-64/pr19609-3b.d: Likewise.
	* testsuite/ld-x86-64/pr19609-4.s: Likewise.
	* testsuite/ld-x86-64/pr19609-4a.d: Likewise.
	* testsuite/ld-x86-64/pr19609-4b.d: Likewise.
	* testsuite/ld-x86-64/pr19609-4c.d: Likewise.
	* testsuite/ld-x86-64/pr19609-4d.d: Likewise.
	* testsuite/ld-x86-64/pr19609-4e.d: Likewise.
	* testsuite/ld-x86-64/pr19609-5.s: Likewise.
	* testsuite/ld-x86-64/pr19609-5a.d: Likewise.
	* testsuite/ld-x86-64/pr19609-5b.d: Likewise.
	* testsuite/ld-x86-64/pr19609-5c.d: Likewise.
	* testsuite/ld-x86-64/pr19609-5d.d: Likewise.
	* testsuite/ld-x86-64/pr19609-5e.d: Likewise.
	* testsuite/ld-x86-64/pr19609-6.s: Likewise.
	* testsuite/ld-x86-64/pr19609-6a.d: Likewise.
	* testsuite/ld-x86-64/pr19609-6b.d: Likewise.
	* testsuite/ld-x86-64/pr19609-6c.d: Likewise.
	* testsuite/ld-x86-64/pr19609-6d.d: Likewise.
	* testsuite/ld-x86-64/pr19609-7.s: Likewise.
	* testsuite/ld-x86-64/pr19609-7a.d: Likewise.
	* testsuite/ld-x86-64/pr19609-7b.d: Likewise.
	* testsuite/ld-x86-64/pr19609-7c.d: Likewise.
	* testsuite/ld-x86-64/pr19609-7d.d: Likewise.
	* testsuite/ld-i386/i386.exp: Run undefweak tests and tests for
	PR ld/19609.
	* testsuite/ld-x86-64/x86-64.exp: Run pr13082-3c, pr13082-3d
	and tests for PR ld/19609.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [BFD][AARCH64]Fix MOVW_SABS_G(0, 1, 2) relocation overflow check.
@ 2016-02-26 18:19 sergiodj+buildbot
  2016-02-27  3:19 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-26 18:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c5e3a3641ea9d6ed2918021fd77925825d24e9be ***

Author: Renlin Li <renlin.li@arm.com>
Branch: master
Commit: c5e3a3641ea9d6ed2918021fd77925825d24e9be

[BFD][AARCH64]Fix MOVW_SABS_G(0,1,2) relocation overflow check.

For these three relocations, 17 bit signed value should be used, instead of
16 bit. The bitsize field is changed from 16 to 17, this field in aarch64
backend is used for overflow check only.

bfd/

2016-02-26  Renlin Li  <renlin.li@arm.com>

    * elfnn-aarch64.c (elfNN_aarch64_howto_table): Fix signed overflow
    check for MOVW_SABS_G0, MOVW_SABS_G1, MOVW_SABS_G2.

ld/

2016-02-26  Renlin Li  <renlin.li@arm.com>

    * testsuite/ld-aarch64/aarch64-elf.exp: Run new testcases.
    * testsuite/ld-aarch64/emit-relocs-270.d: Update to use new boundary.
    * testsuite/ld-aarch64/emit-relocs-271.d: Likewise.
    * testsuite/ld-aarch64/emit-relocs-272.d: Likewise.
    * testsuite/ld-aarch64/emit-relocs-270-overflow.d: New.
    * testsuite/ld-aarch64/emit-relocs-270-overflow.s: New.
    * testsuite/ld-aarch64/emit-relocs-271-overflow.d: New.
    * testsuite/ld-aarch64/emit-relocs-271-overflow.s: New.
    * testsuite/ld-aarch64/emit-relocs-272-overflow.d: New.
    * testsuite/ld-aarch64/emit-relocs-272-overflow.s: New.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Add x86_64-*-rtems* target
@ 2016-02-26 20:20 sergiodj+buildbot
  2016-02-27  6:18 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-26 20:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f73dbb0e48ef50d2743fed89b68530b731329f05 ***

Author: Joel Sherrill <joel.sherrill@oarcorp.com>
Branch: master
Commit: f73dbb0e48ef50d2743fed89b68530b731329f05

Add x86_64-*-rtems* target

	ld/configure.tgt: Also add stanza for x86_64-*-elf.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Add aarch64-*-rtems* target
@ 2016-02-26 20:30 sergiodj+buildbot
  2016-02-27  8:20 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-26 20:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 12a132db164ea95e9e457427c2c97005f94c5a70 ***

Author: Joel Sherrill <joel@rtems.org>
Branch: master
Commit: 12a132db164ea95e9e457427c2c97005f94c5a70

Add aarch64-*-rtems* target


^ permalink raw reply	[flat|nested] 2113+ messages in thread
[parent not found: <1ed0c2a4bbe8ad5f5404014a6351b2b74db75577@gdb-build>]
* [binutils-gdb] Don't recursively look for a symbol in all imports of imported modules.
@ 2016-02-28 15:25 sergiodj+buildbot
  2016-02-28 16:12 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-28 15:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 38899f16e1560ce3020bab8a6a0b3a0c017d7925 ***

Author: Iain Buclaw <ibuclaw@gdcproject.org>
Branch: master
Commit: 38899f16e1560ce3020bab8a6a0b3a0c017d7925

Don't recursively look for a symbol in all imports of imported modules.

Given two or more modules that import each other's scope, the current symbol
lookup routines would go round in circles looking through each import from
each module, possibly checking the same module twice or more until all possible
paths are marked as "searched".

Given enough modules, this causes an exponential slowdown in time taken to find
symbols that do exist, and infinite recursion when they don't.

gdb/ChangeLog:
	* d-namespace.c (d_lookup_symbol_imports): Avoid recursive lookups from
	cyclic imports.

gdb/testsuite/ChangeLog:
	* gdb.dlang/circular.c: New file.
	* gdb.dlang/circular.exp: New file.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [ARC] General fixes.
@ 2016-02-29 15:24 sergiodj+buildbot
  2016-02-29 16:23 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-29 15:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7e4588997ebdddefc48d8be2d51a715822817c0e ***

Author: Claudiu Zissulescu <claziss@synopsys.com>
Branch: master
Commit: 7e4588997ebdddefc48d8be2d51a715822817c0e

[ARC] General fixes.

bfd/
2016-02-29  Cupertino Miranda <Cupertino.Miranda@synopsys.com>

	* elf32-arc.c (arc_elf_final_write_processing): Add condition to
	the flag change.
        (elf_arc_relocate_section): Fixes and conditions to support PIE.
	Assert for code sections dynamic relocs.

gas/
2016-02-29  Claudiu Zissulescu  <Claudiu.Zissulescu@synopsys.com>

	* config/tc-arc.c: Enable code density instructions for ARC EM.

ld/
2016-02-29  Cupertino Miranda  <Cupertino.Miranda@synopsys.com>

	* scripttempl/arclinux.sc: Force .tdata and .tbss to always be
	generated.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [ARC] Local symbols relocation cleanup
@ 2016-02-29 16:04 sergiodj+buildbot
  2016-02-29 17:46 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-29 16:04 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 841fdfcdd9caa69f3ad7560a2806d421e23f598a ***

Author: Claudiu Zissulescu <claziss@synopsys.com>
Branch: master
Commit: 841fdfcdd9caa69f3ad7560a2806d421e23f598a

[ARC] Local symbols relocation cleanup

bfd/
2016-02-29  Cupertino Miranda  <cmiranda@synopsys.com>

	* elf32-arc.c (elf_arc_relocate_section): Added rules to fix the
	relocation addend when sections get merged.

gas/
2016-02-29  Cupertino Miranda  <cmiranda@synopsys.com>
	    Claudiu Zissulescu  <Claudiu.Zissulescu@synopsys.com>

        * config/tc-arc.c (arc_extra_reloc): Change size to 0.
        (tc_arc_fix_adjustable): Changed default return value to 1.
        * testsuite/gas/arc/j.d: Updated expected symbol
        * testsuite/gas/arc/jl.d: Likewise
        * testsuite/gas/arc/relax-avoid1.d: Likewise
        * testsuite/gas/arc/st.d: Likewise

ld/
2016-02-29 Cupertino Miranda  <cmiranda@synopsys.com>

	* testsuite/ld-elf/merge.d: Removed xfail for ARC.
	* testsuite/ld-elf/merge2.d: Likewise.
	* testsuite/ld-elf/merge3.d: Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Support more syscalls in linux-record: pipe2 epoll_create1 eventfd2 fallocate dup3 and inotify_init1
@ 2016-02-29 16:58 sergiodj+buildbot
  2016-02-29 19:28 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-29 16:58 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 253b4d3a09e9edbb72d21127fbc85934ab1b7c07 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 253b4d3a09e9edbb72d21127fbc85934ab1b7c07

Support more syscalls in linux-record: pipe2 epoll_create1 eventfd2 fallocate dup3 and inotify_init1

This patch adds more syscalls in linux-record.

gdb:

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

	* linux-record.h (enum gdb_syscall) <gdb_sys_fallocate>: New.
	<gdb_sys_eventfd2, gdb_sys_epoll_create1, gdb_sys_dup3>: New.
	<gdb_sys_pipe2, gdb_sys_inotify_init1>: New.
	* linux-record.c (record_linux_system_call): Handle them.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] aarch64-linux process record: more syscalls
@ 2016-02-29 17:29 sergiodj+buildbot
  2016-02-29 21:25 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-02-29 17:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d521906965b3e94648a723a13576236aaba301d0 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: d521906965b3e94648a723a13576236aaba301d0

aarch64-linux process record: more syscalls

The last patch supports several syscalls in linux-record.c, so now
GDB aarch64-linux backend can return these canonicalized syscall numbers
per aarch64 syscall number.

This patch fixes the following fails,

Process record and replay target doesn't support syscall number 59^M
Process record: failed to record execution log.^M
^M
Program stopped.^M
0x00000020000eab28 in pipe () from /lib/aarch64-linux-gnu/libc.so.6^M
(gdb) FAIL: gdb.reverse/pipe-reverse.exp: continue to breakpoint: marker2

Process record and replay target doesn't support syscall number 59^M
Process record: failed to record execution log.^M
^M
Program stopped.^M
0x00000020000eab28 in pipe () from /lib/aarch64-linux-gnu/libc.so.6^M
(gdb) FAIL: gdb.reverse/readv-reverse.exp: continue to breakpoint: marker2

gdb:

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

	* aarch64-linux-tdep.c (aarch64_canonicalize_syscall): Support
	eventfd2, eventfd2, dup3, inotify_init1, fallocate and pipe2.
	Return gdb_sys_epoll_create1 instead of gdb_sys_epoll_create
	for aarch64_sys_epoll_create1.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] S390: Fix internal error with stackless inferior
@ 2016-03-01 11:55 sergiodj+buildbot
  2016-03-01 12:54 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-01 11:55 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f24894771e384b1bc60dc0f2c104d7e7fad3c865 ***

Author: Andreas Arnez <arnez@linux.vnet.ibm.com>
Branch: master
Commit: f24894771e384b1bc60dc0f2c104d7e7fad3c865

S390: Fix internal error with stackless inferior

This fixes a GDB internal error that may occur when the inferior has no
valid stack pointer in r15.

gdb/testsuite/ChangeLog:

	* gdb.arch/s390-stackless.S: New.
	* gdb.arch/s390-stackless.exp: New.

gdb/ChangeLog:

	* s390-linux-tdep.c (s390_backchain_frame_unwind_cache): Avoid
	exception when attempting to access the inferior's backchain.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] S390: Fix output path for s390-tdbregs test case
@ 2016-03-01 12:05 sergiodj+buildbot
  2016-03-01 14:51 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-01 12:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4a9321595003d86dd4794d0edab071f91989808e ***

Author: Andreas Arnez <arnez@linux.vnet.ibm.com>
Branch: master
Commit: 4a9321595003d86dd4794d0edab071f91989808e

S390: Fix output path for s390-tdbregs test case

Since test artifacts are always organized in a directory hierarchy, the
s390-tdbregs test case is not executed correctly any more.  This is
because it uses an obsolete way of constructing the executable's path.

This change invokes prepare_for_testing instead.

gdb/testsuite/ChangeLog:

	* gdb.arch/s390-tdbregs.exp: Use prepare_for_testing instead of
	manually constructing the output path.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Compile gdb.arch/arm-neon.c with "quiet"
@ 2016-03-01 15:31 sergiodj+buildbot
  2016-03-01 16:19 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-01 15:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT dc856b382065cdfab3f9bb484c07e182950eb4d4 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: dc856b382065cdfab3f9bb484c07e182950eb4d4

Compile gdb.arch/arm-neon.c with "quiet"

When we compile gdb.arch/arm-neon.c with options that don't enable NEON,
there are many error/warnings emitted into gdb.sum, which is annoying.
This patch fixes it by passing quiet to prepare_for_testing.

gdb/testsuite:

2016-03-01  Yao Qi  <yao.qi@linaro.org>

	* gdb.arch/arm-neon.exp: Pass quiet to prepare_for_testing.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix output path for arm-disp-step.exp
@ 2016-03-01 15:41 sergiodj+buildbot
  2016-03-01 17:53 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-01 15:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 30ca9da1193ec4c82cc67a2ec2e6fb6adac7ab84 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 30ca9da1193ec4c82cc67a2ec2e6fb6adac7ab84

Fix output path for arm-disp-step.exp

This patch fixes the following error,

ERROR: (/scratch/yao/gdb/build-git/arm-linux-gnueabihf/gdb/testsuite/outputs/gdb.arch/arm-disp-step/arm-disp-step) No such file or directory
FAIL: gdb.arch/arm-disp-step.exp: Can't run to main

gdb/testsuite:

2016-03-01  Yao Qi  <yao.qi@linaro.org>

	* gdb.arch/arm-disp-step.exp: Use standard_testfile and
	prepare_for_testing.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix gdb.base/catch-fork-kill.c compilation
@ 2016-03-01 17:26 sergiodj+buildbot
  2016-03-01 19:14 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-01 17:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6ccb54e2a82ca934f6d430b87ab015b7bfecc413 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 6ccb54e2a82ca934f6d430b87ab015b7bfecc413

Fix gdb.base/catch-fork-kill.c compilation

Fixes:

 Running .../src/gdb/testsuite/gdb.base/catch-fork-kill.exp ...
 gdb compile failed, .../src/gdb/testsuite/gdb.base/catch-fork-kill.c: In function 'main':
 .../src/gdb/testsuite/gdb.base/catch-fork-kill.c:81:4: warning: implicit declaration of function 'wait' [-Wimplicit-function-declaration]
     wait (NULL);
     ^

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

	* gdb.base/catch-fork-kill.c: Include <sys/wait.h>.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix gdb.threads/watchpoint-fork*.c compilation
@ 2016-03-01 17:53 sergiodj+buildbot
  2016-03-01 20:53 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-01 17:53 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1e903e320352db86233e1dd2d10fd140f5d4a887 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 1e903e320352db86233e1dd2d10fd140f5d4a887

Fix gdb.threads/watchpoint-fork*.c compilation

This testcase currently fails to compile on Fedora 23:

 .../src/gdb/testsuite/gdb.threads/watchpoint-fork-mt.c: In function 'start':
 .../src/gdb/testsuite/gdb.threads/watchpoint-fork-mt.c:70:11: warning: implicit declaration of function 'pthread_yield' [-Wimplicit-function-declaration]
	i = pthread_yield ();
	    ^
 .../src/gdb/testsuite/gdb.threads/watchpoint-fork-child.c: In function 'forkoff':
 .../src/gdb/testsuite/gdb.threads/watchpoint-fork-child.c:114:8: warning: implicit declaration of function 'pthread_yield' [-Wimplicit-function-declaratio
 n]
     i = pthread_yield ();
	 ^
 /tmp/ccUkNIsI.o: In function `start':
 .../src/gdb/testsuite/gdb.threads/watchpoint-fork-mt.c:70: undefined reference to `pthread_yield'
 (...)
 collect2: error: ld returned 1 exit status

 UNSUPPORTED: gdb.threads/watchpoint-fork.exp: child: multithreaded: Couldn't compile watchpoint-fork-child.c: unrecognized error
 UNTESTED: gdb.threads/watchpoint-fork.exp: child: multithreaded: watchpoint-fork.exp
 testcase .../src/gdb/testsuite/gdb.threads/watchpoint-fork.exp completed i

The glibc manual says, on _GNU_SOURCE:

 "You should define these macros by using #define preprocessor
 directives at the top of your source code files. These directives must
 come before any #include of a system header file."

I instead put it in the header all the .c files of the testcase must
include anyway.

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

	* gdb.threads/watchpoint-fork-child.c: Include "watchpoint-fork.h"
	before anything else.
	* gdb.threads/watchpoint-fork-mt.c: Likewise.  Don't define
	_GNU_SOURCE here.
	* gdb.threads/watchpoint-fork-st.c: Include "watchpoint-fork.h"
	before anything else.
	* gdb.threads/watchpoint-fork.h: Define _GNU_SOURCE.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix gdb.trace/ftrace-lock.c compilation
@ 2016-03-01 18:47 sergiodj+buildbot
  2016-03-01 22:16 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-01 18:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 86e501afd46d7f0d31738bd62457593401d79bad ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 86e501afd46d7f0d31738bd62457593401d79bad

Fix gdb.trace/ftrace-lock.c compilation

Fixes, on F23:

 .../src/gdb/testsuite/gdb.trace/ftrace-lock.c: In function 'gdb_agent_gdb_collect':
 .../src/gdb/testsuite/gdb.trace/ftrace-lock.c:50:3: warning: implicit declaration of function 'sleep' [-Wimplicit-function-declaration]
    sleep (1);
    ^

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

	* gdb.trace/ftrace-lock.c: Include <unistd.h>.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix shift left warning at source
@ 2016-03-02  3:28 sergiodj+buildbot
  2016-03-02  4:14 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-02  3:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 62de1c630f16c21418464727692bcd29e23ef1b0 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 62de1c630f16c21418464727692bcd29e23ef1b0

Fix shift left warning at source

cpu/
	* fr30.cpu (f-m4): Replace -1 << 4 with -16.
opcodes/
	* fr30-ibld.c: Regenerate.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Regenerate rl78 opcodes file
@ 2016-03-02  3:46 sergiodj+buildbot
  2016-03-02  7:58 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-02  3:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c697cf0b2b85cb1231e2c76c52cfed43770aa04a ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: c697cf0b2b85cb1231e2c76c52cfed43770aa04a

Regenerate rl78 opcodes file

For newer comments.

	* rl78-decode.c: Regenerate.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Regenerate bfd files.
@ 2016-03-02  4:03 sergiodj+buildbot
  2016-03-02  6:02 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-02  4:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 70a5df4fe30fd37166c3b62071fd816e49082d2e ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 70a5df4fe30fd37166c3b62071fd816e49082d2e

Regenerate bfd files.

	* Makefile.in: Regenerate.
	* po/SRC-POTFILES.in: Regenerate.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Regenerate or1k opcodes file
@ 2016-03-02 14:03 sergiodj+buildbot
  2016-03-02 14:47 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-02 14:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d11698cd0d9bb22b51598ee37af0aaf1d44ec5c7 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: d11698cd0d9bb22b51598ee37af0aaf1d44ec5c7

Regenerate or1k opcodes file

CGEN patch now committed upstream to use hex numbers for large enums.

	* or1k-desc.h: Regenerate.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix detection of gfortran compilers.
@ 2016-03-02 14:37 sergiodj+buildbot
  2016-03-02 16:16 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-02 14:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 285866651cd0d404087438668012289d278e4179 ***

Author: Bernhard Heckel <bernhard.heckel@intel.com>
Branch: master
Commit: 285866651cd0d404087438668012289d278e4179

Fix detection of gfortran compilers.

Newer gfortran compilers changed naming convention in DW_AT_producer tag.
For example "GNU Fortran 4.6.3" vs "GNU Fortran2008 5.3.0"

2016-03-02  Bernhard Heckel  <bernhard.heckel@intel.com>

gdb/Changelog:

     * dwarf2read.c (new_symbol_full): Fix detection of gfortran compilers.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Add new maintainer to Write After Approval.
@ 2016-03-02 15:30 sergiodj+buildbot
  2016-03-02 18:00 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-02 15:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 650beae39d31e5ce2680649e2fb697e0e4a9e3eb ***

Author: Bernhard Heckel <bernhard.heckel@intel.com>
Branch: master
Commit: 650beae39d31e5ce2680649e2fb697e0e4a9e3eb

Add new maintainer to Write After Approval.

Add new maintainer to Write After Approval.

2016-03-02  Bernhard Heckel  <bernhard.heckel@intel.com>

    * MAINTAINERS (Write After Approval): Add Bernhard Heckel.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] testsuite: Fix run to main issue introduced by GCC 5.x.
@ 2016-03-02 15:53 sergiodj+buildbot
  2016-03-02 20:57 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-02 15:53 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9ac2d526d9ae70272bf7fc436f2e3ad11a84d58b ***

Author: bernhard.heckel <bernhard.heckel@intel.com>
Branch: master
Commit: 9ac2d526d9ae70272bf7fc436f2e3ad11a84d58b

testsuite: Fix run to main issue introduced by GCC 5.x.

Adding a dummy assignment as a new breakpoint anchor because
breakpoint on return statement doesn't work for GCC 5.x.

2016-03-02  Bernhard Heckel  <bernhard.heckel@intel.com>

gdb/testsuite/Changelog:

     * gdb.cp/vla-cxx.cc: Insert dummy assignment as anchor for an breakpoint.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] testsuite: Remove unnecessary code in fortran vla-history test.
@ 2016-03-02 16:16 sergiodj+buildbot
  2016-03-03  0:38 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-02 16:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 065ab6dc804575bce7df58477b2cfcb2b2a6eafb ***

Author: Bernhard Heckel <bernhard.heckel@intel.com>
Branch: master
Commit: 065ab6dc804575bce7df58477b2cfcb2b2a6eafb

testsuite: Remove unnecessary code in fortran vla-history test.

testsuite: Remove unnecessary code in fortran vla-history test.

2016-03-02  Bernhard Heckel  <bernhard.heckel@intel.com>

gdb/testsuite/Changelog:

     * gdb.fortran/vla-history.exp: Remove breakpoint.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [OBV] gdbserver: Only write ipa_tdesc_idx if agent is actually loaded.
@ 2016-03-02 16:31 sergiodj+buildbot
  2016-03-03  2:18 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-02 16:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6896a8fa1e1d24a8fcc9b30efc0b195246b46029 ***

Author: Marcin Kocielnicki <koriakin@0x04.net>
Branch: master
Commit: 6896a8fa1e1d24a8fcc9b30efc0b195246b46029

[OBV] gdbserver: Only write ipa_tdesc_idx if agent is actually loaded.

Fixes rather embarassing gdb.trace regressions.

gdb/gdbserver/ChangeLog:

	* tracepoint.c (cmd_qtstart): Only set ipa_tdesc_idx if agent
	is actually loaded.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] testsuite: Fix timeout issues during print of vla-arrays.
@ 2016-03-02 17:06 sergiodj+buildbot
  2016-03-02 22:40 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-02 17:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 07e448ade17bc8fb52469a5b2184017f94669bd6 ***

Author: bernhard.heckel <bernhard.heckel@intel.com>
Branch: master
Commit: 07e448ade17bc8fb52469a5b2184017f94669bd6

testsuite: Fix timeout issues during print of vla-arrays.

Printing and resolving of dynamic array's causes sporadic timeout issues on loaded systems.

2016-03-02  Bernhard Heckel  <bernhard.heckel@intel.com>

gdb/testsuite/Changelog:

     * gdb.fortran/vla-history.exp: Lookup array elements and printing exceeds timeout.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Call enqueue_pending_signal in linux_resume_one_lwp_throw
@ 2016-03-02 17:42 sergiodj+buildbot
  2016-03-03  3:58 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-02 17:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fdbd04a8adef3a48eeac7702e9243c7c31e47256 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: fdbd04a8adef3a48eeac7702e9243c7c31e47256

Call enqueue_pending_signal in linux_resume_one_lwp_throw

Replace the code which is exactly what enqueue_pending_signal does.

gdb/gdbserver:

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

	* linux-low.c (linux_resume_one_lwp_throw): Replace code with
	enqueue_pending_signal.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [GDBserver] Leave child suspended when step over parent
@ 2016-03-03  9:31 sergiodj+buildbot
  2016-03-03 10:09 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-03  9:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0f8288ae82bf5bdb33d46d7447cd3132393a1bd2 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 0f8288ae82bf5bdb33d46d7447cd3132393a1bd2

[GDBserver] Leave child suspended when step over parent

I see the following GDBserver internal error in two cases,

 gdb/gdbserver/linux-low.c:1922: A problem internal to GDBserver has been detected.
 unsuspend LWP 17200, suspended=-1

 1. step over a breakpoint on fork/vfork syscall instruction,
 2. step over a breakpoint on clone syscall instruction and child
    threads hits a breakpoint,

the stack backtrace is

 #0  internal_error (file=file@entry=0x44c4c0 "gdb/gdbserver/linux-low.c", line=line@entry=1922,
    fmt=fmt@entry=0x44c7d0 "unsuspend LWP %ld, suspended=%d\n") at gdb/gdbserver/../common/errors.c:51
 #1  0x0000000000424014 in lwp_suspended_decr (lwp=<optimised out>, lwp=<optimised out>) at gdb/gdbserver/linux-low.c:1922
 #2  0x000000000042403a in unsuspend_one_lwp (entry=<optimised out>, except=0x66e8c0) at gdb/gdbserver/linux-low.c:2885
 #3  0x0000000000405f45 in find_inferior (list=<optimised out>, func=func@entry=0x424020 <unsuspend_one_lwp>, arg=arg@entry=0x66e8c0)
    at gdb/gdbserver/inferiors.c:243
 #4  0x00000000004297de in unsuspend_all_lwps (except=0x66e8c0) at gdb/gdbserver/linux-low.c:2895
 #5  linux_wait_1 (ptid=..., ourstatus=ourstatus@entry=0x665ec0 <last_status>, target_options=target_options@entry=0)
    at gdb/gdbserver/linux-low.c:3632
 #6  0x000000000042a764 in linux_wait (ptid=..., ourstatus=0x665ec0 <last_status>, target_options=0)
    at gdb/gdbserver/linux-low.c:3770
 #7  0x0000000000411163 in mywait (ptid=..., ourstatus=ourstatus@entry=0x665ec0 <last_status>, options=options@entry=0, connected_wait=connected_wait@entry=1)
    at gdb/gdbserver/target.c:214
 #8  0x000000000040b1f2 in resume (actions=0x66f800, num_actions=1) at gdb/gdbserver/server.c:2757
 #9  0x000000000040f660 in handle_v_cont (own_buf=0x66a630 "vCont;c:p45e9.-1") at gdb/gdbserver/server.c:2719

when GDBserver steps over a thread, other threads have been suspended,
the "stepping" thread may create new thread, but GDBserver doesn't set
it suspend count to 1.  When GDBserver unsuspend threads, the child's
suspend count goes to -1, and the assert is triggered.  In fact, GDBserver
has already taken care of suspend count of new thread when GDBserver is
suspending all threads except the one GDBserver wants to step over by
https://sourceware.org/ml/gdb-patches/2015-07/msg00946.html

+	  /* If we're suspending all threads, leave this one suspended
+	     too.  */
+	  if (stopping_threads == STOPPING_AND_SUSPENDING_THREADS)
+	    {
+	      if (debug_threads)
+		debug_printf ("HEW: leaving child suspended\n");
+	      child_lwp->suspended = 1;
+	    }

but that is not enough, because new thread is still can be spawned in
the thread which is being stepped over.  This patch extends the
condition that GDBserver set child's suspend count to one if it is
suspending threads or stepping over the thread.

gdb/gdbserver:

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

	PR server/19736
	* linux-low.c (handle_extended_wait): Set child suspended
	if event_lwp->bp_reinsert isn't zero.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Refactor gdb.base/disp-step-syscall.exp for general step over test
@ 2016-03-03  9:42 sergiodj+buildbot
  2016-03-03 11:20 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-03  9:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0b47da9f176aa73854f1ff8ae00afda11a4f338a ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 0b47da9f176aa73854f1ff8ae00afda11a4f338a

Refactor gdb.base/disp-step-syscall.exp for general step over test

This patch moves some code out of disp_step_cross_syscall to a new proc
check_pc_after_cross_syscall and setup.  Procedure setup is to start a
fresh GDB and compute the syscall instruction address.

gdb/testsuite:

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

	* gdb.base/disp-step-syscall.exp (check_pc_after_cross_syscall): New
	proc.
	(setup): New proc.
	(disp_step_cross_syscall): Move code to check_pc_after_cross_syscall
	and setup.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Step over syscalll insn with disp-step on and off
@ 2016-03-03  9:51 sergiodj+buildbot
  2016-03-03 12:26 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-03  9:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e197ad3c87723a2bdf383d38fcfa3eaa4fa1ba12 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: e197ad3c87723a2bdf383d38fcfa3eaa4fa1ba12

Step over syscalll insn with disp-step on and off

disp-step-syscall.exp was added to test displaced stepping over syscall
instructions, in which we set breakpoint on syscall instruction, and
step over it.  In fact, we can extend the test to non-displaced-stepping
case.  This patch wraps the test with displaced stepping on and off.
Note that the indentation and format isn't adjusted here to make this
patch easy to read.  The following patch will fix the format separately.

gdb/testsuite:

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

	* gdb.base/disp-step-syscall.exp: Don't invoke
	support_displaced_stepping.
	(disp_step_cross_syscall): Test with displaced stepping off and
	on if supported.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Step over fork/vfork syscall insn in gdbserver
@ 2016-03-03 10:00 sergiodj+buildbot
  2016-03-03 13:38 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-03 10:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 92fa70b0bd8690d979357ebcdb501a9e4aa42ea6 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 92fa70b0bd8690d979357ebcdb501a9e4aa42ea6

Step over fork/vfork syscall insn in gdbserver

We can also extend disp-step-syscall.exp to test GDBserver step over
breakpoint on syscall instruction.  That is, we set a breakpoint
with a false condition on syscall instruction, so that GDBserver will
step over it.

This test triggers a GDBserver internal error, which can be fixed by
this series.

(gdb) PASS: gdb.base/disp-step-syscall.exp: fork: break cond on target: break on syscall insns
continue^M
Continuing.^M
Remote connection closed^M
(gdb) FAIL: gdb.base/disp-step-syscall.exp: fork: break cond on target: continue to fork again

In GDBserver, there is an internal error,

/home/yao/SourceCode/gnu/gdb/git/gdb/gdbserver/linux-low.c:1922: A problem internal to GDBserver has been detected.
unsuspend LWP 25554, suspended=-1

the simplified reproducer is like,

$ ./gdb ./testsuite/outputs/gdb.base/disp-step-syscall/disp-step-fork
(gdb) b main
(gdb) c
(gdb) disassemble fork // in order to find the address of insn 'syscall'
....
   0x00007ffff7ad6023 <+179>:	syscall
(gdb) b *0x00007ffff7ad6023 if main == 0
(gdb) c

gdb/testsuite:

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

	* gdb.base/disp-step-syscall.exp (break_cond_on_syscall): New.
	If target supports condition evaluation on target, invoke
	break_cond_on_syscall for fork and vfork.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Rename disp-step-syscall.exp to step-over-syscall.exp
@ 2016-03-03 10:09 sergiodj+buildbot
  2016-03-03 14:52 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-03 10:09 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8fc8cbdaf698ed042d859d5749cff66937bbb57c ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 8fc8cbdaf698ed042d859d5749cff66937bbb57c

Rename disp-step-syscall.exp to step-over-syscall.exp

disp-step-syscall.exp is extended for stepping over syscall instruction
in different cases, with or without displaced stepping, and stepping
over by GDBserver.

This patch rename disp-step-syscall.exp to step-over-syscall.exp to
reflect this.

gdb/testsuite:

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

	* gdb.base/disp-step-fork.c: Rename to ...
	* gdb.base/step-over-fork.c: ... it.  New file.
	* gdb.base/disp-step-vfork.c: Rename to ...
	* gdb.base/step-over-vfork.c: ... it.  New file.
	* gdb.base/disp-step-syscall.exp: Rename to ...
	* gdb.base/step-over-syscall.exp: ... it.  New file.
	(disp_step_cross_syscall): Rename to ...
	(step_over_syscall): ... it.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Reformat gdb.base/step-over-syscall.exp
@ 2016-03-03 10:20 sergiodj+buildbot
  2016-03-03 15:55 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-03 10:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ea50786226737509a8f4c2734699a5fc15cc63c4 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: ea50786226737509a8f4c2734699a5fc15cc63c4

Reformat gdb.base/step-over-syscall.exp

gdb/testsuite:

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

	* gdb.base/step-over-syscall.exp (disp_step_cross_syscall): Fix
	code format.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] New test about step over clone syscall
@ 2016-03-03 10:27 sergiodj+buildbot
  2016-03-03 17:08 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-03 10:27 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4719d415b9908d3c7981163b47be5096d03656f9 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 4719d415b9908d3c7981163b47be5096d03656f9

New test about step over clone syscall

This patch adds a new test for stepping over clone syscall.

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

	* gdb.base/step-over-syscall.exp (step_over_syscall): Kfail.
	Invoke step_over_syscall "clone" and break_cond_on_syscall
	"clone".
	* gdb.base/step-over-clone.c: New file.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Update comments to start_step_over
@ 2016-03-03 10:36 sergiodj+buildbot
  2016-03-03 18:28 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-03 10:36 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c40c8d4b6793b71eed7cf9fa7467edda2271dc86 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: c40c8d4b6793b71eed7cf9fa7467edda2271dc86

Update comments to start_step_over

I happen to see that comments to start_step_over isn't in sync with
code, so this patch is to update the comments.

gdb/gdbserver:

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

	* linux-low.c: Update comments to start_step_over.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix bugs in the simulation of the AArch64's ADDP, FADDP, LD1, CCMP and CCMP instructions.
@ 2016-03-03 15:34 sergiodj+buildbot
  2016-03-03 19:41 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-03 15:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 57aa17424380be1c3e362a5601071f1f3a6f74f6 ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: 57aa17424380be1c3e362a5601071f1f3a6f74f6

Fix bugs in the simulation of the AArch64's ADDP, FADDP, LD1, CCMP and CCMP instructions.

	* simulator.c (set_flags_for_sub32): Correct type of signbit.
	(CondCompare): Swap interpretation of bit 30.
	(DO_ADDP): Delete macro.
	(do_vec_ADDP): Copy source registers before starting to update
	destination register.
	(do_vec_FADDP): Likewise.
	(do_vec_load_store): Fix computation of sizeof_operation.
	(rbit64): Fix type of constant.
	(aarch64_step): When displaying insn value, display all 32 bits.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] gdb.base/skip.exp: Use with_test_prefix.
@ 2016-03-03 19:03 sergiodj+buildbot
  2016-03-03 21:24 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-03 19:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bdf7e23048b68171c01f2498cc46670a76e68c4d ***

Author: Doug Evans <dje@google.com>
Branch: master
Commit: bdf7e23048b68171c01f2498cc46670a76e68c4d

gdb.base/skip.exp: Use with_test_prefix.

gdb/testsuite/ChangeLog:

	* gdb.base/skip.exp: Use with_test_prefix.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Add new plugin hooks to support querying section alignment and size.
@ 2016-03-03 21:12 sergiodj+buildbot
  2016-03-03 23:53 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-03 21:12 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 82838bd626b10f1a82b0de29728c26f4458ec514 ***

Author: Cary Coutant <ccoutant@gmail.com>
Branch: master
Commit: 82838bd626b10f1a82b0de29728c26f4458ec514

Add new plugin hooks to support querying section alignment and size.

include/
2016-03-03  Than McIntosh <thanm@google.com>

	* plugin-api.h: Add new hooks to the plugin transfer vector to
	to support querying section alignment and section size.
	(ld_plugin_get_input_section_alignment): New hook.
	(ld_plugin_get_input_section_size): New hook.
	(ld_plugin_tag): Add LDPT_GET_INPUT_SECTION_ALIGNMENT
	and LDPT_GET_INPUT_SECTION_SIZE.
	(ld_plugin_tv): Add tv_get_input_section_alignment and
	tv_get_input_section_size.

gold/
2016-03-03  Than McIntosh  <thanm@google.com>

	* plugin.cc (Plugin::load): Include hooks for get_input_section_size
	and get_input_section_alignment in transfer vector.
	(get_input_section_alignment): New function.
	(get_input_section_size): New function.
	* testsuite/Makefile.am: Add plugin_layout_with_alignment.sh test.
	* testsuite/Makefile.in: [Regenerate.]
	* testsuite/plugin_section_alignment.cc: New test file.
	* testsuite/plugin_layout_with_alignment.cc: New test file.
	* testsuite/plugin_layout_with_alignment.sh: New test file.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [ARM] Add feature check for ARMv8.1 AdvSIMD instructions.
@ 2016-03-04 11:45 sergiodj+buildbot
  2016-03-04 12:22 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-04 11:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 643afb90da9066e9d3c6dc721920b14ed343bec9 ***

Author: Matthew Wahab <matthew.wahab@arm.com>
Branch: master
Commit: 643afb90da9066e9d3c6dc721920b14ed343bec9

[ARM] Add feature check for ARMv8.1 AdvSIMD instructions.

gas/
2016-03-04  Matthew Wahab  <matthew.wahab@arm.com>

	* config/gas/tc-arm.c (fpu_neon_ext_v8_1): Restrict to the ARMv8.1 RDMA
	feature.
	(record_feature_use): New.
	(mark_feature_used): Use record_feature_use.
	(do_neon_qrdmlah): New.
	(insns): Use do_neon_qrdmlah for vqrdmlah and vqrdmlsh and
	variants.
	(arm_extensions): Put into alphabetical order.  Re-indent "simd"
	and "rdma" entries.  Fix the incorrect merge value for "+rdma".
	* testsuite/gas/arm/armv8-a+rdma-warning.d: New.
	* testsuite/gas/arm/armv8-a+rdma.d: Add assembler command line options.
	Make source file explicit.
	* testsuite/gas/arm/armv8-a+rdma.l: New.
	* testsuite/gas/arm/armv8-a+rdma.s: Remove .arch and .arch_extension
	directives.  Fix white-space.
	* testsuite/gas/arm/armv8_1-a+simd.d: New.

include/opcode
2016-03-04  Matthew Wahab  <matthew.wahab@arm.com>

	* arm.h (ARM_ARCH_V8_1A): Add FPU_NEON_EXT_RDMA.
	(ARM_CPU_HAS_FEATURE): Add comment.

Change-Id: Ie19250e8fa50aed44e44ab40ff30b04b38bc1a3d


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Treat common symbol in executable as definition
@ 2016-03-04 14:50 sergiodj+buildbot
  2016-03-04 15:25 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-04 14:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 07492f668d2173da7a2bda3707ff0985e0f460b6 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 07492f668d2173da7a2bda3707ff0985e0f460b6

Treat common symbol in executable as definition

Common symbol in executable is a definition, which overrides definition
from shared objects.  When linker sees a new definition from a shared
object, the new dynamic definition should be overridden by the previous
common symbol in executable.

bfd/

	PR ld/19579
	* elflink.c (_bfd_elf_merge_symbol): Treat common symbol in
	executable as definition if the new definition comes from a
	shared library.

ld/

	PR ld/19579
	* testsuite/ld-elf/pr19579a.c: New file.
	* testsuite/ld-elf/pr19579b.c: Likewise.
	* testsuite/ld-elf/shared.exp: Run PR ld/19579 test.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] feature_to_c.sh: Print help when passing no arguments
@ 2016-03-04 15:16 sergiodj+buildbot
  2016-03-04 16:33 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-04 15:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 73519cce7cbe31609a2aa9c27955555237a0c51f ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: 73519cce7cbe31609a2aa9c27955555237a0c51f

feature_to_c.sh: Print help when passing no arguments

I found that odd that passing no arguments to feature_to_c.sh produces
this:

$ ./feature_to_c.sh
./feature_to_c.sh: 23: shift: can't shift that many

but passing one argument shows the help:

$ ./feature_to_c.sh hello
Usage: ./feature_to_c.sh OUTPUTFILE INPUTFILE...

This patch changes the script to show the help in both cases.

gdb/ChangeLog:

	* features/feature_to_c.sh: Print the help when passing no
	argument.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Tweak ARM process record
@ 2016-03-04 16:10 sergiodj+buildbot
  2016-03-04 17:51 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-04 16:10 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ca92db2d5885c03d3e0ed23c96b5c6ab336d908d ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: ca92db2d5885c03d3e0ed23c96b5c6ab336d908d

Tweak ARM process record

This patch removes the printing "Process record does not support",
and do the print by calling arm_record_unsupported_insn in the
caller.  Also, call arm_record_extension_space only when condition
is 0xf.

gdb:

2016-03-04  Yao Qi  <yao.qi@linaro.org>

	* arm-tdep.c (arm_record_extension_space): Remove code
	printing "Process record does not support".
	(arm_record_data_proc_misc_ld_str): Likewise.
	(decode_insn): Call arm_record_extension_space if condition
	is 0xf.  Call arm_record_unsupported_insn if ret isn't
	ARM_RECORD_SUCCESS.  Use 'ret' instead of 'insn_id' to hold
	the value of thumb2_record_decode_insn_handler.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Add missing ChangeLog entries for commit 82838
@ 2016-03-04 16:41 sergiodj+buildbot
  2016-03-04 20:11 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-04 16:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3f1f41f55f2fa5d390e57074477b6407302c8c46 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 3f1f41f55f2fa5d390e57074477b6407302c8c46

Add missing ChangeLog entries for commit 82838

Fix gold/testsuite/plugin_layout_with_alignment.sh permission.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] ARM process record: VMOV
@ 2016-03-04 17:01 sergiodj+buildbot
  2016-03-04 19:08 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-04 17:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f1771dcebf80c75a13ca456491ddfb9b43fcaddf ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: f1771dcebf80c75a13ca456491ddfb9b43fcaddf

ARM process record: VMOV

ARM process record gets the wrong register number for VMOV (from core
register to single-precision register).  That is, we should record
the D register rather than the S pseudo register.  The patch also
removes the condition "bit (arm_insn_r->arm_insn, 20)" check, which
has been checked above.

It fixes the following internal error,

(gdb) PASS: gdb.reverse/finish-precsave.exp: BP at end of main
continue^M
Continuing.^M
../../binutils-gdb/gdb/regcache.c:649: internal-error: regcache_raw_read: Assertion `regnum >= 0 && regnum < regcache->descr->nr_raw_registers' failed.^M
A problem internal to GDB has been detected,FAIL: gdb.reverse/finish-precsave.exp: run to end of main (GDB internal error)

gdb:

2016-03-04  Yao Qi  <yao.qi@linaro.org>

	* arm-tdep.c (arm_record_vdata_transfer_insn): Simplify the
	condition check.  Record the right D register number.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix argument passing for call
@ 2016-03-05 12:31 sergiodj+buildbot
  2016-03-05 13:06 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-05 12:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cb86f3880e61c79e59b9225e79c3544a1fcd8005 ***

Author: Denis Chertykov <chertykov@gmail.com>
Branch: master
Commit: cb86f3880e61c79e59b9225e79c3544a1fcd8005

Fix argument passing for call

When calling function with argument of size more than 8 bytes fails with
an error "That operation is not available on integers of more than 8 bytes.".
avr-gdb considers only 8 bytes (sizeof(long long)) in case of passing the
argument in registers. When the argument is of size more than 8 byte
then the utility function to extract bytes failed with the above error.

    gdb/
	* avr-tdep.c (AVR_LAST_ARG_REGNUM): Define.
        (avr_push_dummy_call): Correct last needed argument register.
        Write MSB of argument into register and subsequent bytes into
        other registers in decreasing order.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Improve analysis of racy testcases
@ 2016-03-06  1:57 sergiodj+buildbot
  2016-03-06  2:46 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-06  1:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fb6a751f5f1fe7912e84dd90d06395c357da47c2 ***

Author: Sergio Durigan Junior <sergiodj@redhat.com>
Branch: master
Commit: fb6a751f5f1fe7912e84dd90d06395c357da47c2

Improve analysis of racy testcases

This is an initial attempt to introduce some mechanisms to identify
racy testcases present in our testsuite.  As can be seen in previous
discussions, racy tests are really bothersome and cause our BuildBot
to pollute the gdb-testers mailing list with hundreds of
false-positives messages every month.  Hopefully, identifying these
racy tests in advance (and automatically) will contribute to the
reduction of noise traffic to gdb-testers, maybe to the point where we
will be able to send the failure messages directly to the authors of
the commits.

I spent some time trying to decide the best way to tackle this
problem, and decided that there is no silver bullet.  Racy tests are
tricky and it is difficult to catch them, so the best solution I could
find (for now?) is to run our testsuite a number of times in a row,
and then compare the results (i.e., the gdb.sum files generated during
each run).  The more times you run the tests, the more racy tests you
are likely to detect (at the expense of waiting longer and longer).
You can also run the tests in parallel, which makes things faster (and
contribute to catching more racy tests, because your machine will have
less resources for each test and some of them are likely to fail when
this happens).  I did some tests in my machine (8-core i7, 16GB RAM),
and running the whole GDB testsuite 5 times using -j6 took 23 minutes.
Not bad.

In order to run the racy test machinery, you need to specify the
RACY_ITER environment variable.  You will assign a number to this
variable, which represents the number of times you want to run the
tests.  So, for example, if you want to run the whole testsuite 3
times in parallel (using 2 cores), you will do:

  make check RACY_ITER=3 -j2

It is also possible to use the TESTS variable and specify which tests
you want to run:

  make check TEST='gdb.base/default.exp' RACY_ITER=3 -j2

And so on.  The output files will be put at the directory
gdb/testsuite/racy_outputs/.

After make invokes the necessary rules to run the tests, it finally
runs a Python script that will analyze the resulting gdb.sum files.
This Python script will read each file, and construct a series of sets
based on the results of the tests (one set for FAIL's, one for
PASS'es, one for KFAIL's, etc.).  It will then do some set operations
and come up with a list of unique, sorted testcases that are racy.
The algorithm behind this is:

  for state in PASS, FAIL, XFAIL, XPASS...; do
    if a test's state in every sumfile is $state; then
      it is not racy
    else
      it is racy

(The algorithm is actually a bit more complex than that, because it
takes into account other things in order to decide whether the test
should be ignored or not).

IOW, a test must have the same state in every sumfile.

After processing everything, the script prints the racy tests it could
identify on stdout.  I am redirecting this to a file named racy.sum.

Something else that I wasn't sure how to deal with was non-unique
messages in our testsuite.  I decided to do the same thing I do in our
BuildBot: include a unique identifier in the end of message, like:

  gdb.base/xyz.exp: non-unique message
  gdb.base/xyz.exp: non-unique message <<2>>

This means that you will have to be careful about them when you use
the racy.sum file.

I ran the script several times here, and it did a good job catching
some well-known racy tests.  Overall, I am satisfied with this
approach and I think it will be helpful to have it upstream'ed.  I
also intend to extend our BuildBot and create new, specialized
builders that will be responsible for detecting the racy tests every X
number of days.

2016-03-05  Sergio Durigan Junior  <sergiodj@redhat.com>

	* Makefile.in (DEFAULT_RACY_ITER): New variable.
	(CHECK_TARGET_TMP): Likewise.
	(check-single-racy): New rule.
	(check-parallel-racy): Likewise.
	(TEST_TARGETS): Adjust rule to account for RACY_ITER.
	(do-check-parallel-racy): New rule.
	(check-racy/%.exp): Likewise.
	* README (Racy testcases): New section.
	* analyze-racy-logs.py: New file.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Set executable bit on analyze-racy-logs.py
@ 2016-03-06 22:42 sergiodj+buildbot
  2016-03-06 23:21 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-06 22:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5eb264df40e1e3ffeb2627456889a1dc5df00f16 ***

Author: Sergio Durigan Junior <sergiodj@redhat.com>
Branch: master
Commit: 5eb264df40e1e3ffeb2627456889a1dc5df00f16

Set executable bit on analyze-racy-logs.py

I forgot to do it in my previous commit.  This is necessary because we
execute the script directly on gdb/testsuite/Makefile.in.

gdb/testsuite/ChangeLog:
2016-03-06  Sergio Durigan Junior  <sergiodj@redhat.com>

	* analyze-racy-logs.py: Set executable bit.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Add const qualifiers at various places.
@ 2016-03-07 15:39 sergiodj+buildbot
  2016-03-07 16:07 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-07 15:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f86f586366275bbb5ae77520eb990769f05a3030 ***

Author: Trevor Saunders <tbsaunde+binutils@tbsaunde.org>
Branch: master
Commit: f86f586366275bbb5ae77520eb990769f05a3030

Add const qualifiers at various places.

opcodes	* mcore-opc.h: Add const qualifiers.
	* microblaze-opc.h (struct op_code_struct): Likewise.
	* sh-opc.h: Likewise.
	* tic4x-dis.c (tic4x_print_indirect): Likewise.
	(tic4x_print_op): Likewise.

include	* opcode/dlx.h (struct dlx_opcode): Add const qualifiers.
	* opcode/h8300.h (struct h8_opcode): Likewise.
	* opcode/hppa.h (struct pa_opcode): Likewise.
	* opcode/msp430.h: Likewise.
	* opcode/spu.h (struct spu_opcode): Likewise.
	* opcode/tic30.h (struct _register): Likewise.
	* opcode/tic4x.h (struct tic4x_register): Likewise.
	(struct tic4x_cond): Likewise.
	(struct tic4x_indirect): Likewise.
	(struct tic4x_inst): Likewise.
	* opcode/visium.h (struct reg_entry): Likewise.

gas	* config/tc-arc.c: Add const qualifiers.
	* config/tc-h8300.c (md_begin): Likewise.
	* config/tc-ia64.c (print_prmask): Likewise.
	* config/tc-msp430.c (msp430_operands): Likewise.
	* config/tc-nds32.c (struct suffix_name): Likewise.
	(struct nds32_parse_option_table): Likewise.
	(struct nds32_set_option_table): Likewise.
	(do_pseudo_pushpopm): Likewise.
	(do_pseudo_pushpop_stack): Likewise.
	(nds32_relax_relocs): Likewise.
	(nds32_flag): Likewise.
	(struct nds32_hint_map): Likewise.
	(nds32_find_reloc_table): Likewise.
	(nds32_match_hint_insn): Likewise.
	* config/tc-s390.c: Likewise.
	* config/tc-sh.c (get_specific): Likewise.
	* config/tc-tic30.c: Likewise.
	* config/tc-tic4x.c (tic4x_inst_add): Likewise.
	(tic4x_indirect_parse): Likewise.
	* config/tc-vax.c (vax_cons): Likewise.
	* config/tc-z80.c (struct reg_entry): Likewise.
	* config/tc-epiphany.c (md_assemble): Adjust.
	(epiphany_assemble): New function.
	(epiphany_elf_section_rtn): Call do_align directly.
	(epiphany_elf_section_text): Likewise.
	* config/tc-ip2k.c (ip2k_elf_section_rtn): Likewise.
	(ip2k_elf_section_text): Likewise.
	* read.c (do_align): Make it not static.
	* read.h (do_align): New prototype.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [AArch64] Create .got section if _GLOBAL_OFFSET_TABLE_ referenced
@ 2016-03-07 15:51 sergiodj+buildbot
  2016-03-07 17:27 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-07 15:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 18f822a08fd5cb8fed8b0b318e7945545c255081 ***

Author: Jiong Wang <jiong.wang@arm.com>
Branch: master
Commit: 18f822a08fd5cb8fed8b0b318e7945545c255081

[AArch64] Create .got section if _GLOBAL_OFFSET_TABLE_ referenced

2016-03-07  Jiong Wang  <jiong.wang@arm.com>

bfd/
  * elfnn-aarch64.c (elfNN_aarch64_check_relocs): Always create .got section
  if the symbol "_GLOBAL_OFFSET_TABLE_" referenced.

ld/
  * testsuite/ld-aarch64/implicit_got_section_1.s: New test source file.
  * testsuite/ld-aarch64/implicit_got_section_1.d: New test expected result.
  * testsuite/ld-aarch64/aarch64-elf.exp: Run new test.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix "set architecture mips:10000" crash
@ 2016-03-07 16:52 sergiodj+buildbot
  2016-03-07 18:39 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-07 16:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e6c2f47b45315ba13f25fb57e51389d0c5ed0701 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: e6c2f47b45315ba13f25fb57e51389d0c5ed0701

Fix "set architecture mips:10000" crash

Fix this GDB crash:

  $ gdb -ex "set architecture mips:10000"
  Segmentation fault (core dumped)

Backtrace:

  Program received signal SIGSEGV, Segmentation fault.
  0x0000000000495b1b in mips_gdbarch_init (info=..., arches=0x0) at /home/pedro/gdb/mygit/cxx-convertion/src/gdb/mips-tdep.c:8436
  8436              if (bfd_get_flavour (info.abfd) == bfd_target_elf_flavour
  (top-gdb) bt
  #0  0x0000000000495b1b in mips_gdbarch_init (info=..., arches=0x0) at .../src/gdb/mips-tdep.c:8436
  #1  0x00000000007348a6 in gdbarch_find_by_info (info=...) at .../src/gdb/gdbarch.c:5155
  #2  0x000000000073563c in gdbarch_update_p (info=...) at .../src/gdb/arch-utils.c:522
  #3  0x0000000000735585 in set_architecture (ignore_args=0x0, from_tty=1, c=0x26bc870) at .../src/gdb/arch-utils.c:496
  #4  0x00000000005f29fd in do_sfunc (c=0x26bc870, args=0x0, from_tty=1) at .../src/gdb/cli/cli-decode.c:121
  #5  0x00000000005fd3f3 in do_set_command (arg=0x7fffffffdcdd "mips:10000", from_tty=1, c=0x26bc870) at .../src/gdb/cli/cli-setshow.c:455
  #6  0x0000000000836157 in execute_command (p=0x7fffffffdcdd "mips:10000", from_tty=1) at .../src/gdb/top.c:460
  #7  0x000000000071abfb in catch_command_errors (command=0x835f6b <execute_command>, arg=0x7fffffffdccc "set architecture mips:10000", from_tty=1)
      at .../src/gdb/main.c:368
  #8  0x000000000071bf4f in captured_main (data=0x7fffffffd750) at .../src/gdb/main.c:1132
  #9  0x0000000000716737 in catch_errors (func=0x71af44 <captured_main>, func_args=0x7fffffffd750, errstring=0x106b9a1 "", mask=RETURN_MASK_ALL)
      at .../src/gdb/exceptions.c:240
  #10 0x000000000071bfe6 in gdb_main (args=0x7fffffffd750) at .../src/gdb/main.c:1164
  #11 0x000000000040a6ad in main (argc=4, argv=0x7fffffffd858) at .../src/gdb/gdb.c:32
  (top-gdb)

We already check whether info.abfd is NULL before all other
bfd_get_flavour calls in the same function.  Just this one case was
missing.

(This was exposed by a WIP test that tries all "set architecture ARCH"
values.)

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

	* mips-tdep.c (mips_gdbarch_init): Check whether info.abfd is NULL
	before calling bfd_get_flavour.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Allow zero length archive elements.
@ 2016-03-07 17:40 sergiodj+buildbot
  2016-03-07 19:44 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-07 17:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4fc874242f8f1bf17cf6e65b159dd804e793e6cd ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: 4fc874242f8f1bf17cf6e65b159dd804e793e6cd

Allow zero length archive elements.

bfd	PR binutils/19775
	* archive.c (bfd_generic_openr_next_archived_file): Allow zero
	length elements in the archive.

binutils PR binutils/19775
	* testsuite/binutils-all/ar.exp (proc empty_archive): New proc.
	Run the new proc.
	* testsuite/binutils-all/empty: New, empty, file.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [ARC] Allow non-instruction relocations within .text sections
@ 2016-03-08 13:41 sergiodj+buildbot
  2016-03-08 14:19 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-08 13:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 72f3b6aae734d8cdcded38aca94e379848bec7ef ***

Author: Claudiu Zissulescu <claziss@synopsys.com>
Branch: master
Commit: 72f3b6aae734d8cdcded38aca94e379848bec7ef

[ARC] Allow non-instruction relocations within .text sections

bfd/
2016-03-08  Cupertino Miranda  <Cupertino.Miranda@synopsys.com>
	    Andrew Burgess  <andrew.burgess@embecosm.com>

	* elf32-arc.c (arc_bfd_get_32): Becomes an alias for bfd_get_32.
	(arc_bfd_put_32): Becomes an alias for bfd_put_32.
	(arc_elf_howto_init): Added assert to validate relocations.
	(get_middle_endian_relocation): Delete.
	(middle_endian_convert): New function.
	(ME): Redefine, now does nothing.
	(IS_ME): New define.
	(arc_do_relocation): Extend the attached 'ARC_RELOC_HOWTO'
	definition to call middle_endian_convert.  Add a new local
	variable and make use of this throughout. Added call to
	arc_bfd_get_8 and arc_bfd_put_8 for 8 bit relocations.

gas/
2016-03-08  Andrew Burgess  <andrew.burgess@embecosm.com>

	* testsuite/gas/arc/inline-data-1.d: New file.
	* testsuite/gas/arc/inline-data-1.s: New file.

include/
2016-03-08  Cupertino Miranda  <Cupertino.Miranda@synopsys.com>
	    Andrew Burgess  <andrew.burgess@embecosm.com>

	* elf/arc-reloc.def: Add a call to ME within the formula for each
	relocation that requires middle-endian correction.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Group common symbol checking together
@ 2016-03-08 13:50 sergiodj+buildbot
  2016-03-08 15:43 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-08 13:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 202ac193bbbecc96a4978d1ac3d17148253f9b01 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 202ac193bbbecc96a4978d1ac3d17148253f9b01

Group common symbol checking together

	PR ld/19579
	* elflink.c (_bfd_elf_merge_symbol): Group common symbol checking
	together.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Handle local IFUNC symbols in shared object
@ 2016-03-08 17:47 sergiodj+buildbot
  2016-03-08 18:38 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-08 17:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d1ed1c7d69e6656de213b12594e702afec31a66d ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: d1ed1c7d69e6656de213b12594e702afec31a66d

Handle local IFUNC symbols in shared object

Increment PLT reference count for locally defined local IFUNC symbols
in shared object since STT_GNU_IFUNC symbol must go through PLT even
if it is locally defined and undefined symbol may turn out to be a
STT_GNU_IFUNC symbol later.

bfd/

	PR ld/19784
	* elf32-i386.c (elf_i386_check_relocs): Increment PLT reference
	count for locally defined local IFUNC symbols in shared object.
	* elf64-x86-64.c (elf_x86_64_check_relocs): Likewise.

ld/

	PR ld/19784
	* testsuite/ld-i386/i386.exp: Remove pr19636-2e-nacl test.
	* testsuite/ld-i386/pr19636-2e-nacl.d: Moved to ...
	* testsuite/ld-i386/pr19636-2e.d: Here.  Remove notarget.
	* testsuite/ld-ifunc/ifunc.exp: Run PR ld/19784 tests.
	* testsuite/ld-ifunc/pass.out: New file.
	* testsuite/ld-ifunc/pr19784a.c: Likewise.
	* testsuite/ld-ifunc/pr19784b.c: Likewise.
	* testsuite/ld-ifunc/pr19784c.c: Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix HP/PA GNU/Linux "long double" format
@ 2016-03-09  2:37 sergiodj+buildbot
  2016-03-09  3:16 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-09  2:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT aacca8a7a9c7f93955fa9dbf796b030ffce1b956 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: aacca8a7a9c7f93955fa9dbf796b030ffce1b956

Fix HP/PA GNU/Linux "long double" format

This:

 $ ./gdb -ex "set architecture hppa1.0" -ex "set osabi GNU/Linux" -ex "ptype 1.0L"

Shows that HPPA/Linux support for long doubles is broken.  It causes
GDB to access memory out of bounds.  With Valgrind, we see:

 The target architecture is assumed to be hppa1.0
 ==4371== Invalid write of size 8
 ==4371==    at 0x4C2F21F: memset (vg_replace_strmem.c:1224)
 ==4371==    by 0x8451C4: convert_doublest_to_floatformat (doublest.c:362)
 ==4371==    by 0x845F86: floatformat_from_doublest (doublest.c:769)
 ==4371==    by 0x84628E: store_typed_floating (doublest.c:873)
 ==4371==    by 0x6A7C3D: value_from_double (value.c:3662)
 ==4371==    by 0x6AA211: evaluate_subexp_standard (eval.c:745)
 ==4371==    by 0x7F306D: evaluate_subexp_c (c-lang.c:716)
 ==4371==    by 0x6A8C6A: evaluate_subexp (eval.c:79)
 ==4371==    by 0x6A8E87: evaluate_type (eval.c:174)
 ==4371==    by 0x817B8D: whatis_exp (typeprint.c:456)
 ==4371==    by 0x817D68: ptype_command (typeprint.c:508)
 ==4371==    by 0x5F2977: do_cfunc (cli-decode.c:105)
 ==4371==  Address 0x8998d18 is 0 bytes after a block of size 8 alloc'd
 ==4371==    at 0x4C2AA98: calloc (vg_replace_malloc.c:711)
 ==4371==    by 0x8732B6: xcalloc (common-utils.c:83)
 ==4371==    by 0x8732F5: xzalloc (common-utils.c:93)
 ==4371==    by 0x6A37AF: allocate_value_contents (value.c:1036)
 ==4371==    by 0x6A37E5: allocate_value (value.c:1047)
 ==4371==    by 0x6A7BEE: value_from_double (value.c:3656)
 ==4371==    by 0x6AA211: evaluate_subexp_standard (eval.c:745)
 ==4371==    by 0x7F306D: evaluate_subexp_c (c-lang.c:716)
 ==4371==    by 0x6A8C6A: evaluate_subexp (eval.c:79)
 ==4371==    by 0x6A8E87: evaluate_type (eval.c:174)
 ==4371==    by 0x817B8D: whatis_exp (typeprint.c:456)
 ==4371==    by 0x817D68: ptype_command (typeprint.c:508)

The trouble is that hppa_linux_init_abi overrides the default
long_double_bit set by the generic hppa-tdep.c:

  set_gdbarch_long_double_bit (gdbarch, 128);
  set_gdbarch_long_double_format (gdbarch, floatformats_ia64_quad);

with:

  /* On hppa-linux, currently, sizeof(long double) == 8.  There has been
     some discussions to support 128-bit long double, but it requires some
     more work in gcc and glibc first.  */
  set_gdbarch_long_double_bit (gdbarch, 64);

which misses overriding the long_double_format, so we end with a weird
combination of:

  set_gdbarch_long_double_bit (gdbarch, 64);
  set_gdbarch_long_double_format (gdbarch, floatformats_ia64_quad);

Weird because floatformats_ia64_quad's totalsize is longer than 64-bits.

The floatformat conversion routines use the struct floatformat's
totalsize (in bits) to know how much to copy/convert, thus the buffer
overruns.

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

	* hppa-linux-tdep.c (hppa_linux_init_abi): Set the long double
	format to floatformats_ieee_double.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Assert that a floating type's length is at least as long as its format
@ 2016-03-09  3:19 sergiodj+buildbot
  2016-03-09  4:35 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-09  3:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b79497cb1cdc9b3053e5f0387bf3056c08c9bbdd ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: b79497cb1cdc9b3053e5f0387bf3056c08c9bbdd

Assert that a floating type's length is at least as long as its format

This would have caught the HP/PA bug fixed in the previous patch:

 .../src/gdb/gdbtypes.c:4690: internal-error: arch_float_type: Assertion `len >= floatformat_totalsize_bytes (floatformats[0])' failed.
 A problem internal to GDB has been detected,
 further debugging may prove unreliable.
 Quit this debugging session? (y or n)

Tested on x86-64 Fedora 23, --enable-targets=all.

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

	* doublest.c (floatformat_totalsize_bytes): New function.
	(floatformat_from_type): Assert that the type's length is at least
	as long as the floatformat's totalsize.
	* doublest.h (floatformat_totalsize_bytes): New declaration.
	* gdbtypes.c (arch_float_type): Assert that the type's length is
	at least as long as the floatformat's totalsize.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [CRIS] Don't internal error if forced big endian
@ 2016-03-09  3:39 sergiodj+buildbot
  2016-03-09  6:48 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-09  3:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 114d7832b0e07452277d748c81d8bc0c5675a1bc ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 114d7832b0e07452277d748c81d8bc0c5675a1bc

[CRIS] Don't internal error if forced big endian

This fixes:

  $ ./gdb -q -ex "set endian big" -ex "set architecture cris"
  The target is assumed to be big endian
  .../src/gdb/cris-tdep.c:4051: internal-error: cris_gdbarch_init: big endian byte order in info
  A problem internal to GDB has been detected,
  further debugging may prove unreliable.
  Quit this debugging session? (y or n)

The "set cris-version" command can likewise cause internal errors.

The gdbarch init routine should be returning 0 to reject the
architecture instead of internal erroring on user input.

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

	* cris-tdep.c (cris_gdbarch_init): Return 0 if the info's byte
	order is BFD_ENDIAN_BIG or if the cris version is unsupported.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix floating conversion buffer overrun when host/target format matches
@ 2016-03-09  4:23 sergiodj+buildbot
  2016-03-09  5:45 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-09  4:23 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d7a87b5e4343467db23b70e73b156c9cc79c50ea ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: d7a87b5e4343467db23b70e73b156c9cc79c50ea

Fix floating conversion buffer overrun when host/target format matches

Running the testsuite with a gdb configured with --enable-libmcheck
reveals a problem:

  (gdb) ptype 3 * 2.0
  type = <12-byte float>
  memory clobbered past end of allocated block
  ERROR: Process no longer exists
  UNRESOLVED: gdb.ada/ptype_arith_binop.exp: ptype 3 * 2.0

  (gdb) PASS: gdb.dlang/expression.exp: ptype 0x1.FFFFFFFFFFFFFp1023
  ptype 0x1p-52L
  type = real
  memory clobbered past end of allocated block
  ERROR: Process no longer exists
  UNRESOLVED: gdb.dlang/expression.exp: ptype 0x1p-52L

Even though this shows up with Ada and D, it's easy to reproduce in C
too.  We just need to print a long double, when the current arch is
32-bit, which is the default when gdb starts up:

 $ ./gdb -q -ex "ptype 1.0L"
 type = long double
 memory clobbered past end of allocated block
 Aborted (core dumped)

Valgrind shows:

 ==22159== Invalid write of size 8
 ==22159==    at 0x8464A9: floatformat_from_doublest (doublest.c:756)
 ==22159==    by 0x846822: store_typed_floating (doublest.c:867)
 ==22159==    by 0x6A7959: value_from_double (value.c:3662)
 ==22159==    by 0x6A9F2D: evaluate_subexp_standard (eval.c:745)
 ==22159==    by 0x7F31AF: evaluate_subexp_c (c-lang.c:716)
 ==22159==    by 0x6A8986: evaluate_subexp (eval.c:79)
 ==22159==    by 0x6A8BA3: evaluate_type (eval.c:174)
 ==22159==    by 0x817CCF: whatis_exp (typeprint.c:456)
 ==22159==    by 0x817EAA: ptype_command (typeprint.c:508)
 ==22159==    by 0x5F267B: do_cfunc (cli-decode.c:105)
 ==22159==    by 0x5F5618: cmd_func (cli-decode.c:1885)
 ==22159==    by 0x83622A: execute_command (top.c:475)
 ==22159==  Address 0x8c6cb28 is 8 bytes inside a block of size 12 alloc'd
 ==22159==    at 0x4C2AA98: calloc (vg_replace_malloc.c:711)
 ==22159==    by 0x87384A: xcalloc (common-utils.c:83)
 ==22159==    by 0x873889: xzalloc (common-utils.c:93)
 ==22159==    by 0x6A34CB: allocate_value_contents (value.c:1036)
 ==22159==    by 0x6A3501: allocate_value (value.c:1047)
 ==22159==    by 0x6A790A: value_from_double (value.c:3656)
 ==22159==    by 0x6A9F2D: evaluate_subexp_standard (eval.c:745)
 ==22159==    by 0x7F31AF: evaluate_subexp_c (c-lang.c:716)
 ==22159==    by 0x6A8986: evaluate_subexp (eval.c:79)
 ==22159==    by 0x6A8BA3: evaluate_type (eval.c:174)
 ==22159==    by 0x817CCF: whatis_exp (typeprint.c:456)
 ==22159==    by 0x817EAA: ptype_command (typeprint.c:508)
 ==22159==
 type = long double
 (gdb)

Even if the target and host floating-point formats match, the length
of the types might still be different.  On x86, long double is the
80-bit extended precision type on both 32-bit and 64-bit ABIs, but by
default it is stored as 12 bytes on 32-bit, and 16 bytes on 64-bit,
for alignment reasons.  Several places in doublest.c already consider
this, but floatformat_to_doublest and floatformat_from_doublest miss
it.  E.g., convert_typed_floating and store_typed_floating,

Tested on x86-64 Fedora 23 with --enable-libmcheck, where it fixes the
crashed above.

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

	* doublest.c: Extend comments.
	(floatformat_to_doublest, floatformat_from_doublest): Copy the
	floatformat's total size, not the host type's size.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Don't create dynamic sections when relocatable
@ 2016-03-09  4:57 sergiodj+buildbot
  2016-03-09  8:15 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-09  4:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9c1d7a087682074d585253ad38719ec2363eb2b7 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 9c1d7a087682074d585253ad38719ec2363eb2b7

Don't create dynamic sections when relocatable

Since dynamic sections aren't applicable to relocatable file, don't
create dynamic sections for -E/--dynamic-list when relocatable.

bfd/

	PR ld/19789
	* elflink.c (elf_link_add_object_symbols): Create dynamic sections
	for -E/--dynamic-list only when not relocatable.

ld/

	PR ld/19789
	* testsuite/ld-elf/pr19789.d: New file.
	* testsuite/ld-elf/pr19789.s: Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Allow zero length archive elements
@ 2016-03-09  6:37 sergiodj+buildbot
  2016-03-09  9:10 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-09  6:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 03ee85837ec2e10f7b67c417b17ab3ffa97a98d2 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 03ee85837ec2e10f7b67c417b17ab3ffa97a98d2

Allow zero length archive elements

	PR binutils/19775
	* coff-alpha.c (alpha_ecoff_openr_next_archived_file): Allow zero
	length elements in the archive.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] For COFF and COFF/PE targets, skip relocations against absolute symbols.
@ 2016-03-09 15:43 sergiodj+buildbot
  2016-03-09 16:18 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-09 15:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 26c62da040fb9d602da269a3bdffdea13a4367c7 ***

Author: Leon Winter <winter-gcc@bfw-online.de>
Branch: master
Commit: 26c62da040fb9d602da269a3bdffdea13a4367c7

For COFF and COFF/PE targets, skip relocations against absolute symbols.

	PR ld/19623
	* cofflink.c (_bfd_coff_generic_relocate_section): Do not apply
	relocations against absolute symbols.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix v850 bfd arch info printable names
@ 2016-03-09 15:59 sergiodj+buildbot
  2016-03-09 17:36 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-09 15:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4b05e0a74b3fb21b56e821423b8a334e4be9cfe7 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 4b05e0a74b3fb21b56e821423b8a334e4be9cfe7

Fix v850 bfd arch info printable names

Currently, it's not possible to manually set some of the v850 archs in
gdb:

 (gdb) set architecture v850<TAB>
 v850 (using old gcc ABI)
 v850-rh850
 v850e
 v850e (using old gcc ABI)
 v850e1
 [...]
 (gdb) set architecture v850 (using old gcc ABI)
 Ambiguous item "v850 (using old gcc ABI)".

The problem is that "set architecture" is a GDB "enum command", and
GDB only considers an enum value to be the string up until the first
space.  So writing "v850 (using old gcc ABI)" is the same as writing
"v850", and then that's not an unambiguous arch printable name prefix.

v850 is actually the only arch that has spaces in its printable name.
One can conveniently see that with e.g.:

 (gdb) set max-completions unlimited
 (gdb) complete set architecture
 ...

Rather than hack GDB into accepting this somehow, make v850 arch
printable names more like the printable names of the other archs, and
put the abi variant in the "machine" part, after a ':'.

We now get:

 (gdb) set architecture v850<TAB>
 v850:old-gcc-abi
 v850:rh850
 v850e
 v850e1
 v850e1:old-gcc-abi
 v850e2
 v850e2:old-gcc-abi
 [...]

And now "set architecture v850:old-gcc-abi" works as expected.

I ran the binutils/gas/ld testsuites, and found no regressions.  I
don't have a cross compiler handy, but I ran the gdb tests anyway,
which covers at least some snoke testing.

I think that the OUTPUT_ARCH in ld/scripttempl/v850.sc may have got
broken with the previous 2012 change, since I hacked v850_rh850.sc to
output "v850" and ld failed to grok it.  I think it only works if the
old GCC ABI is the configured v850 default ABI.  That's now fixed by
changing to use explicit v850:old-gcc-abi.

Also, this actually "fixes" an existing GDB test, which isn't likewise
expecting spaces in arch names, when GDB is configured for
--target=v850:

  (gdb) FAIL: gdb.xml/tdesc-arch.exp: read valid architectures

bfd/ChangeLog:
2016-03-09  Pedro Alves  <palves@redhat.com>

	* cpu-v850.c (N): Append ":old-gcc-abi" instead of " (using old
	gcc ABI)" to printable name.
	* cpu-v850_rh850.c (bfd_v850_rh850_arch): Use "v850:rh850" instead
	of "v850-rh850" as printable name.

ld/ChangeLog:
2016-03-09  Pedro Alves  <palves@redhat.com>

	* scripttempl/v850.sc: Use "v850:old-gcc-abi" as OUTPUT_ARCH.
	* scripttempl/v850_rh850.sc: Use "v850:rh850" as OUTPUT_ARCH.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [FR-V] Handle FR300
@ 2016-03-09 16:08 sergiodj+buildbot
  2016-03-09 18:47 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-09 16:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 087ccc6a4f8c754a4f4d31810839a631dbeabe0d ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 087ccc6a4f8c754a4f4d31810839a631dbeabe0d

[FR-V] Handle FR300

Even though "set architecture" presents fr300 as option:

 (gdb) set architecture fr<TAB>
 fr300  fr400  fr450  fr500  fr550  frv

Actually selecting fr300 doesn't work:

 (gdb) set architecture fr300
 Architecture `fr300' not recognized.
 The target architecture is set automatically (currently i386)
 (gdb)

This just looks like an obvious oversight.  Looking around gcc and
binutils sources, FR300 is basically a FR500 specialized for DSP and
low power.

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

	* frv-tdep.c (frv_gdbarch_init): Handle bfd_mach_fr300.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Avoid spaces in osabi names
@ 2016-03-09 16:19 sergiodj+buildbot
  2016-03-09 19:53 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-09 16:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f7990f1690e9ef0471634c871c790f6cf706866d ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: f7990f1690e9ef0471634c871c790f6cf706866d

Avoid spaces in osabi names

It's not possible today to select some of the osabis by name.
Specifically, those that have spaces in their names and then the first
word is ambiguous...

For example:
 (gdb) set osabi <TAB>
 [...]
 FreeBSD ELF
 FreeBSD a.out
 [...]
 (gdb) set osabi FreeBSD ELF
 Ambiguous item "FreeBSD ELF".

In reality, because "set osabi" is an enum command, that was
equivalent to trying "set osabi FreeBSD", which is then obviously
ambiguous, because of "FreeBSD ELF" and "FreeBSD a.out".

Also, even if the first word is not ambiguous, we actually ignore
whatever comes after the first word:

 (gdb) set osabi GNU/Linux
 (gdb) show osabi
 The current OS ABI is "GNU/Linux".
 The default OS ABI is "GNU/Linux".
 (gdb) set osabi Windows SomeNonsense
                         ^^^^^^^^^^^^
 (gdb) show osabi
 The current OS ABI is "Windows CE".
 The default OS ABI is "GNU/Linux".
 (gdb)

Fix this by avoiding spaces in osabi names.

We could instead make "set osabi" have a custom set hook, or
alternatively make the enum set hook (in cli-setshow.c) handle values
with spaces, but OTOH, I have a feeling that could cause trouble.
E.g., in cases where we might want to write more than one enum value
in the same line.  We could support quoting as workaround, but, not
sure we want that.  "No spaces" seems like a simpler rule.

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

	* osabi.c (gdb_osabi_names): Avoid spaces in osabi names.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] S390: Add use of unavailable-stack frame ID
@ 2016-03-09 16:30 sergiodj+buildbot
  2016-03-09 21:09 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-09 16:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6d53bec88f4c1576f74e918400aa2ccac2d129db ***

Author: Andreas Arnez <arnez@linux.vnet.ibm.com>
Branch: master
Commit: 6d53bec88f4c1576f74e918400aa2ccac2d129db

S390: Add use of unavailable-stack frame ID

When determining the frame ID of an inline frame, GDB currently asserts
that a valid ID of the underlying real frame is found, and that it does
not match outer_frame_id.  From inline_frame_this_id():

  /* For now, require we don't match outer_frame_id either (see
     comment above).  */
  gdb_assert (!frame_id_eq (*this_id, outer_frame_id));

However, this assertion may fail when the real frame's unwinder can not
determine the frame ID.  This happened on an s390x target with a binary
that lacked call frame information and also confused the prologue
analyzer, because then s390_frame_this_id() left the frame ID at its
default.

To fix this, this change enhances s390_frame_this_id such that an
unavailable-stack frame ID is built if no frame base can be determined
but the function address is available.

gdb/ChangeLog:

	* s390-linux-tdep.c (s390_prologue_frame_unwind_cache): Store
	frame func's PC in info->func before any other failure can occur.
	(s390_frame_this_id): Use frame_id_build_unavailable_stack if
	info->func has been filled out.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] S390: Recognize special jumps in prologue parser
@ 2016-03-09 16:41 sergiodj+buildbot
  2016-03-09 22:21 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-09 16:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bc0e3f49c84055034cae31bba169100d107b28f4 ***

Author: Andreas Arnez <arnez@linux.vnet.ibm.com>
Branch: master
Commit: bc0e3f49c84055034cae31bba169100d107b28f4

S390: Recognize special jumps in prologue parser

Functions compiled with the gcc option `-mhotpatch' may start with a
branch-never BRCL instruction as a 6-byte NOP.  And functions compiled
with `-mstack-size' contain a BRC instruction in their prologue that is
actually a conditional trap.  Both of these special jumps cause the
prologue parser to stop and yield bad unwinding results.

This change makes the prologue analyzer recognize such special jumps and
ignore them.

gdb/ChangeLog:

	* s390-linux-tdep.c (s390_analyze_prologue): Ignore BRC and BRCL
	instructions that do nothing or are conditional traps.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] gdb: Add ax_pseudo_register_collect for powerpc.
@ 2016-03-09 18:02 sergiodj+buildbot
  2016-03-09 23:32 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-09 18:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2a2fa07bd121498a492f84312a36629383fc9445 ***

Author: Marcin Kocielnicki <koriakin@0x04.net>
Branch: master
Commit: 2a2fa07bd121498a492f84312a36629383fc9445

gdb: Add ax_pseudo_register_collect for powerpc.

gdb/ChangeLog:

	* rs6000-tdep.c (rs6000_ax_pseudo_register_collect): New function.
	(rs6000_gdbarch_init): Wire in the above.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] gdb: Add gen_return_address for powerpc.
@ 2016-03-09 18:28 sergiodj+buildbot
  2016-03-10  0:40 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-09 18:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a67914defbe57290c714975d7c1ccefa787fd635 ***

Author: Marcin Kocielnicki <koriakin@0x04.net>
Branch: master
Commit: a67914defbe57290c714975d7c1ccefa787fd635

gdb: Add gen_return_address for powerpc.

gdb/ChangeLog:

	* rs6000-tdep.c: Add "ax.h" and "ax-gdb.h" includes.
	(rs6000_gen_return_address): New function.
	(rs6000_gdbarch_init): Wire in the above.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] gdb/rs6000: Read backchain as unsigned.
@ 2016-03-09 18:40 sergiodj+buildbot
  2016-03-10  1:49 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-09 18:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cc2c4da8813b980a4e68272bb43583f4af6fe89c ***

Author: Marcin Kocielnicki <koriakin@0x04.net>
Branch: master
Commit: cc2c4da8813b980a4e68272bb43583f4af6fe89c

gdb/rs6000: Read backchain as unsigned.

Previously, backchain was read as a signed quantity, resulting in
addresses like 0xfffffffffffeded0 instead of 0xfffeded0 returned by
unwinder on 32-bit powerpc.  While normally such addresses are masked
off, this causes problems for tracepoints, since 0xfffffffffffeded0
is considered unavailable.

Fixes a test failure in gdb.trace/entry-values.exp.

gdb/ChangeLog:

	* corefile.c (safe_read_memory_unsigned_integer): New function.
	* gdbcore.h (safe_read_memory_unsigned_integer): New prototype.
	* rs6000-tdep.c (rs6000_frame_cache): Read backchain as unsigned.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] gdb.trace: Use manually-defined start labels in unavailable-dwarf-piece.exp
@ 2016-03-09 18:50 sergiodj+buildbot
  2016-03-10  2:58 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-09 18:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4366d36e467bf81274edccbea026a91188cc67e3 ***

Author: Marcin Kocielnicki <koriakin@0x04.net>
Branch: master
Commit: 4366d36e467bf81274edccbea026a91188cc67e3

gdb.trace: Use manually-defined start labels in unavailable-dwarf-piece.exp

On powerpc64, foo/bar point to a function descriptor, not to function code.
Since there are no global labels pointing at the actual function code,
let's make our own.

Regression-tested on x86_64.

gdb/testsuite/ChangeLog:

	* gdb.trace/unavailable-dwarf-piece.c (foo): Add foo_start_lbl label.
	(bar): Add bar_start_lbl label.
	* gdb.trace/unavailable-dwarf-piece.exp: Use foo/bar_start_lbl instead
	of foo/bar for emitting DWARF and tracing.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] gdb.trace/entry-values.exp: Fixes for powerpc64.
@ 2016-03-09 19:21 sergiodj+buildbot
  2016-03-10  6:52 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-09 19:21 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 98fa59e9b06fa479cafb852ef87e5a9bfd87ae54 ***

Author: Marcin Kocielnicki <koriakin@0x04.net>
Branch: master
Commit: 98fa59e9b06fa479cafb852ef87e5a9bfd87ae54

gdb.trace/entry-values.exp: Fixes for powerpc64.

On powerpc64, "disassemble foo" doesn't work properly on object files
(it can't process the relocations in .opd section) - instead, let's
link it into an executable and load that.

Also, backtrace displays .main, not main.  Accept both.

gdb/testsuite/ChangeLog:

	* gdb.trace/entry-values.exp: Link ${binfile}1.o to ${binfile}1 and
	use it for disassembly; accept .main in addition to main in backtrace.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Test issuing a command split in multiple lines with continuation chars
@ 2016-03-09 19:42 sergiodj+buildbot
  2016-03-10  9:03 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-09 19:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c32e87066a216dbcd9daa36100975a5ecb471bb9 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: c32e87066a216dbcd9daa36100975a5ecb471bb9

Test issuing a command split in multiple lines with continuation chars

I happened to break this locally and the testsuite didn't notice it.
Add some tests.

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

	* gdb.base/command-line-input.exp: New file.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] gdb_readline2 -> gdb_readline_no_editing_callback
@ 2016-03-09 20:06 sergiodj+buildbot
  2016-03-10 11:51 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-09 20:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c70061cf94691182484924c79cbbdd2203ef92d5 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: c70061cf94691182484924c79cbbdd2203ef92d5

gdb_readline2 -> gdb_readline_no_editing_callback

The "2" in "gdb_readline2" doesn't really convey much.  Rename for
clarity.

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

	* event-top.c (gdb_readline2): Rename to ...
	(gdb_readline_no_editing_callback): ... this.
	(change_line_handler, stdin_event_handler)
	(gdb_setup_readline): Adjust.
	* event-top.h (gdb_readline2): Rename to ...
	(gdb_readline_no_editing_callback): ... this, and move closer to
	other readline-related declarations.
	* mi/mi-interp.c (mi_interpreter_resume): Adjust.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Eliminate async_annotation_suffix
@ 2016-03-09 20:15 sergiodj+buildbot
  2016-03-10 12:57 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-09 20:15 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 608ff013aae02e3ac4687691db57bbcb8984fe18 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 608ff013aae02e3ac4687691db57bbcb8984fe18

Eliminate async_annotation_suffix

The comments and existence of this global are a bit of misleading
obfuscation, since this is only ever used to print the prompt
annotation, and never changes.  Just hardcode "prompt" where
necessary, as done for most other annotations.

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

	* event-top.c (async_annotation_suffix): Delete.
	(top_level_prompt, command_line_handler): Don't use
	'async_annotation_suffix' and simplify.
	* event-top.h (async_annotation_suffix): Delete declaration.
	(init_main): Remove reference to 'async_annotation_suffix'.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Use struct buffer in gdb_readline_no_editing
@ 2016-03-09 20:47 sergiodj+buildbot
  2016-03-10 16:47 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-09 20:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7a3bde34bc61af108556c74b661533dadddcb178 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 7a3bde34bc61af108556c74b661533dadddcb178

Use struct buffer in gdb_readline_no_editing

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

	* common/buffer.h (buffer_grow_char): New function.
	* top.c: Include buffer.h.
	(gdb_readline_no_editing): Rename 'prompt_arg' parameter to
	'prompt'.  Use struct buffer instead of xrealloc.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Use struct buffer in gdb_readline_no_editing_callback
@ 2016-03-09 20:57 sergiodj+buildbot
  2016-03-10 17:43 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-09 20:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 187212b3c1aa55d9a5b544a6af3af0b5ce457403 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 187212b3c1aa55d9a5b544a6af3af0b5ce457403

Use struct buffer in gdb_readline_no_editing_callback

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

	* event-top.c: Include buffer.h.
	(gdb_readline_no_editing_callback): Use struct buffer instead
	of xrealloc.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Simplify saved_command_line handling
@ 2016-03-09 21:09 sergiodj+buildbot
  2016-03-10 18:55 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-09 21:09 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2669cade3dcebf5d572bcd535cf21934cbc1633c ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 2669cade3dcebf5d572bcd535cf21934cbc1633c

Simplify saved_command_line handling

There doesn't seem to be much point in trying to reuse this buffer.
Prefer simplicity instead.

(In case you're wondering whether this fixes an off-by-one: linelength
is misnamed; it's really a size including terminating null char.)

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

	* event-top.c (command_line_handler): Use xfree + xstrdup instead
	of xrealloc + strcpy.
	* main.c (captured_main): Use xstrdup instead of xmalloc plus
	manual clear.
	* top.c (saved_command_line): Rewrite comment.
	(saved_command_line_size): Delete.
	(command_line_input): Use xfree + xstrdup instead of xrealloc +
	strcpy.
	* top.h (saved_command_line_size): Delete declaration.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] gdb: fix doc string of target_can_use_hardware_watchpoint.
@ 2016-03-09 21:46 sergiodj+buildbot
  2016-03-10 21:38 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-09 21:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2343b78a778af9fe496c521bd49ba027cb8b48ae ***

Author: Jose E. Marchesi <jose.marchesi@oracle.com>
Branch: master
Commit: 2343b78a778af9fe496c521bd49ba027cb8b48ae

gdb: fix doc string of target_can_use_hardware_watchpoint.

gdb/ChangeLog

2016-03-09  Jose E. Marchesi  <jose.marchesi@oracle.com>

	* target.h: Fix doc string of target_can_use_hardware_watchpoint.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] More "Program" -> "Thread NN received signal" testsuite adjustment
@ 2016-03-09 21:55 sergiodj+buildbot
  2016-03-10 22:29 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-09 21:55 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 00dbd492e462565366a2691e0579b510ce4c3733 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 00dbd492e462565366a2691e0579b510ce4c3733

More "Program" -> "Thread NN received signal" testsuite adjustment

These tests should have been adjusted by f303dbd60d9c (Fix PR
threads/19422 - show which thread caused stop), but clearly I had
missed grepping for potential-fail cases.

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

	* gdb.threads/attach-into-signal.exp: Adjust to "Program received
	signal" -> "Thread NN received signal" output change.
	* gdb.threads/ia64-sigill.exp: Likewise.
	* gdb.threads/linux-dp.exp: Likewise.
	* gdb.threads/manythreads.exp: Likewise.
	* gdb.threads/pending-step.exp: Likewise.
	* gdb.threads/print-threads.exp: Likewise.
	* gdb.threads/sigstep-threads.exp: Likewise.
	* gdb.threads/staticthreads.exp: Likewise.
	* gdb.threads/tls.exp: Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] gdb.trace/change-loc.exp: Don't depend on tracepoint ordering.
@ 2016-03-09 22:03 sergiodj+buildbot
  2016-03-10  4:26 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-09 22:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ba84e0da35d29dd8969a4bcdd84e3eaa48927a84 ***

Author: Marcin Kocielnicki <koriakin@0x04.net>
Branch: master
Commit: ba84e0da35d29dd8969a4bcdd84e3eaa48927a84

gdb.trace/change-loc.exp: Don't depend on tracepoint ordering.

powerpc (32-bit) loads shared libraries below the main executable, so
the PENDING location is the first one, which the current regex doesn't
match.  Split it into two tests instead, one looking for the pending
tracepoint location, and the other for two installed locations.

gdb/testsuite/ChangeLog:

	* gdb.trace/change-loc.exp: Don't depend on tracepoint location
	ordering.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] gdb: Add tracepoint support for powerpc.
@ 2016-03-09 23:54 sergiodj+buildbot
  2016-03-10  7:54 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-09 23:54 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b04fd3bec955560e00fb0cf6b75e36187a207113 ***

Author: Marcin Kocielnicki <koriakin@0x04.net>
Branch: master
Commit: b04fd3bec955560e00fb0cf6b75e36187a207113

gdb: Add tracepoint support for powerpc.

gdb/gdbserver/ChangeLog:

	* linux-ppc-low.c (ppc_supports_tracepoints): New function.
	(struct linux_target_ops): Wire in the above.

gdb/testsuite/ChangeLog:

	* gdb.trace/ftrace.exp: Set arg0exp for ppc.
	* gdb.trace/mi-trace-unavailable.exp: Set pcnum for ppc.
	* gdb.trace/pending.exp: Accept leading dot before function name.
	* gdb.trace/trace-common.h: Add fast tracepoint dummy insn for ppc.
	* lib/trace-support.exp: Set registers for ppc.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] gdb.trace/tfind.exp: Force call via global entry point on ppc64le.
@ 2016-03-10  1:30 sergiodj+buildbot
  2016-03-10  5:36 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-10  1:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f77198c878424891f11d6550370f8d9382f412de ***

Author: Marcin Kocielnicki <koriakin@0x04.net>
Branch: master
Commit: f77198c878424891f11d6550370f8d9382f412de

gdb.trace/tfind.exp: Force call via global entry point on ppc64le.

tfind.exp sets a breakpoint on *gdb_recursion_test, which is the global
entry point on ppc64le, and won't be hit, since the call uses
the local entry.  Fix by calling the function via a pointer in a global
variable, forcing use of the global entry.

This patch is a slightly modified hunk extracted from
https://sourceware.org/ml/gdb-patches/2015-07/msg00353.html

gdb/testsuite/ChangeLog:

2016-03-09  Wei-cheng Wang  <cole945@gmail.com>
	    Marcin Kocielnicki  <koriakin@0x04.net>

	* gdb.trace/actions.c (gdb_recursion_test_fp): New typedef.
	(gdb_recursion_test_ptr): New global variable.
	(gdb_recursion_test): Call gdb_recursion_test_ptr instead of
	gdb_recursion_test.
	(gdb_c_test): Ditto.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Mark the i370 target as obsolete.
@ 2016-03-10 15:43 sergiodj+buildbot
  2016-03-10 23:44 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-10 15:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3ed4ff97cbbeeb2658286769ac9e8a6a35390f26 ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: 3ed4ff97cbbeeb2658286769ac9e8a6a35390f26

Mark the i370 target as obsolete.

	* config.bfd: Mark the i370 target as obsolete.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Add $_as_string convenience function
@ 2016-03-10 22:34 sergiodj+buildbot
  2016-03-11  0:50 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-10 22:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f2f3ccb9f81255fd1b4f877600f39979c2d7ece5 ***

Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: f2f3ccb9f81255fd1b4f877600f39979c2d7ece5

Add $_as_string convenience function

This patch is a follow-up to "Add printf format specifier for printing
enumerator":

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

Instead of having a solution specific to the printf command, Pedro
suggested adding a general purpose function $_as_string() that would
cover this use case and more.

So, in order to print the textual label of an enum, one can use:

  (gdb) printf "Visiting node of type %s\n", $_as_string(node)
  Visiting node of type NODE_INTEGER

gdb/ChangeLog:

	* data-directory/Makefile.in (PYTHON_FILE_LIST): Install
	gdb/function/as_string.py.
	* python/lib/gdb/function/as_string.py: New file.
	* NEWS: Mention the new $_as_string function.

gdb/testsuite/ChangeLog:

	* gdb.python/py-as-string.exp: New file.
	* gdb.python/py-as-string.c: New file.

gdb/doc/ChangeLog:

	* gdb.texinfo (Convenience Functions): Document $_as_string.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix some places where octet to byte conversions are needed.
@ 2016-03-11  9:28 sergiodj+buildbot
  2016-03-11 10:08 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-11  9:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 37b01f6a13f21f274bf9758ecbf5d9efd6153444 ***

Author: Dan Gissel <dgisselq@ieee.org>
Branch: master
Commit: 37b01f6a13f21f274bf9758ecbf5d9efd6153444

Fix some places where octet to byte conversions are needed.

	PR 19713
	* elf.c (_bfd_elf_section_offset): Ensure that the returned offset
	uses bytes not octets.
	* elflink.c (resolve_section): Likewise.
	Add a bfd parameter.
	(eval_section): Pass the input_bfd to resolve_section.
	(bfd_elf_perform_complex_relocation): Convert byte offset to
	octets before read and writing values.
	(elf_link_input_bfd): Add byte to octet conversions.
	(elf_reloc_link_order): Likewise.
	(elf_fixup_link_order): Likewise.
	(bfd_elf_final_link): Likewise.
	* reloc.c (_bfd_final_link_relocate): Likewise.
	* syms.c (_bfd_stab_section_find_nearest_line): Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] gdb/s390: Fill pseudo register agent expression hooks.
@ 2016-03-11 10:15 sergiodj+buildbot
  2016-03-11 11:21 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-11 10:15 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c4b3e547d50b01dcf909498119ff6c0af482f2c8 ***

Author: Marcin Kocielnicki <koriakin@0x04.net>
Branch: master
Commit: c4b3e547d50b01dcf909498119ff6c0af482f2c8

gdb/s390: Fill pseudo register agent expression hooks.

gdb/ChangeLog:

	* s390-linux-tdep.c (s390_ax_pseudo_register_collect): New function.
	(s390_ax_pseudo_register_push_stack): New function.
	(s390_gdbarch_init): Fill ax_pseudo_register_collect and
	ax_pseudo_register_push_stack hooks.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] gdb/s390: Fill gen_return_address hook.
@ 2016-03-13 10:06 sergiodj+buildbot
  2016-03-13 10:51 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-13 10:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 70104a908773d7df0af48ca5c48856886bafea13 ***

Author: Marcin Kocielnicki <koriakin@0x04.net>
Branch: master
Commit: 70104a908773d7df0af48ca5c48856886bafea13

gdb/s390: Fill gen_return_address hook.

gdb/ChangeLog:

	* s390-linux-tdep.c (s390_gen_return_address): New function.
	(s390_gdbarch_init): Fill gen_return_address hook.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] gdb.base/default.exp: Add missing $_as_string to "show convenience" test
@ 2016-03-14 16:56 sergiodj+buildbot
  2016-03-14 17:35 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-14 16:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fa4ff313317d6234bbd818b09332e7d85349a56a ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: fa4ff313317d6234bbd818b09332e7d85349a56a

gdb.base/default.exp: Add missing $_as_string to "show convenience" test

When adding the $_as_string convenience function, I missed a new test
failure in default.exp.  The tests lists the convenience functions, so
$_as_string should be added to the expected list.

Fixes:

+FAIL: gdb.base/default.exp: show convenience ($_caller_is = <internal function _caller_is> not found)

gdb/testsuite/ChangeLog:

	* gdb.base/default.exp: Add $_as_string to the list of expected
	convenience functions.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Regenerate bfd-in2.h
@ 2016-03-14 20:28 sergiodj+buildbot
  2016-03-14 21:05 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-14 20:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fbe48798204180aa11c55e5377c1e23700b9c280 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: fbe48798204180aa11c55e5377c1e23700b9c280

Regenerate bfd-in2.h

	* bfd-in2.h: Regenerated.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix PR gdb/19676: Internal error in linux-thread.db.c if /proc not mounted
@ 2016-03-15 17:14 sergiodj+buildbot
  2016-03-15 18:38 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-15 17:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1eb2dbb8d73c344e199fd04531ec3f649e2835b2 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 1eb2dbb8d73c344e199fd04531ec3f649e2835b2

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] 2113+ messages in thread
* [binutils-gdb] Add -z noreloc-overflow option to x86-64 ld
@ 2016-03-15 18:19 sergiodj+buildbot
  2016-03-15 22:16 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-15 18:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4c10bbaa0912742322f10d9d5bb630ba4e15dfa7 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 4c10bbaa0912742322f10d9d5bb630ba4e15dfa7

Add -z noreloc-overflow option to x86-64 ld

Add -z noreloc-overflow command-line option to the x86-64 ELF linker to
disable relocation overflow check.  This can be used to avoid relocation
overflow check if there will be no dynamic relocation overflow at
run-time.

bfd/

	PR ld/19807
	* elf64-x86-64.c (elf_x86_64_relocate_section): Check
	no_reloc_overflow_check to diable R_X86_64_32/R_X86_64_32S
	relocation overflow check.

include/

	PR ld/19807
	* bfdlink.h (bfd_link_info): Add no_reloc_overflow_check.

ld/

	PR ld/19807
	* Makefile.am (ELF_X86_DEPS): Add
	$(srcdir)/emulparams/reloc_overflow.sh.
	* Makefile.in: Regenerated.
	* NEWS: Mention -z noreloc-overflow.
	* ld.texinfo: Document -z noreloc-overflow.
	* emulparams/elf32_x86_64.sh: Source
	${srcdir}/emulparams/reloc_overflow.sh.
	* emulparams/elf_x86_64.sh: Likewise.
	* emulparams/reloc_overflow.sh: New file.
	* testsuite/ld-x86-64/pr19807-1.s: New file.
	* testsuite/ld-x86-64/pr19807-1a.d: Likewise.
	* testsuite/ld-x86-64/pr19807-1b.d: Likewise.
	* testsuite/ld-x86-64/pr19807-2.s: Likewise.
	* testsuite/ld-x86-64/pr19807-2a.d: Likewise.
	* testsuite/ld-x86-64/pr19807-2b.d: Likewise.
	* testsuite/ld-x86-64/pr19807-2c.d: Likewise.
	* testsuite/ld-x86-64/pr19807-2d.d: Likewise.
	* testsuite/ld-x86-64/pr19807-2e.d: Likewise.
	* testsuite/ld-x86-64/x86-64.exp: Run PR ld/19807 tests.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [ARM] Support ARMv8.2 FP16 simd instructions
@ 2016-03-16 16:29 sergiodj+buildbot
  2016-03-16 17:23 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-16 16:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cc9333013723880949a1e07a3e04bdbc1a3c3032 ***

Author: Jiong Wang <jiong.wang@arm.com>
Branch: master
Commit: cc9333013723880949a1e07a3e04bdbc1a3c3032

[ARM] Support ARMv8.2 FP16 simd instructions

gas/
	* config/tc-arm.c (N_S_32): New.
	(N_F_16_32): Likewise.
	(N_SUF_32): Support N_F16.
	(N_IF_32): Likewise.
	(neon_dyadic_misc): Likewise.
	(do_neon_cmp): Likewise.
	(do_neon_cmp_inv): Likewise.
	(do_neon_mul): Likewise.
	(do_neon_fcmp_absolute): Likewise.
	(do_neon_step): Likewise.
	(do_neon_abs_neg): Likewise.
	(CVT_FLAVOR_VAR): Likewise.
	(do_neon_cvt_1): Likewise.
	(do_neon_recip_est): Likewise.
	(do_vmaxnm): Likewise.
	(do_vrint_1): Likewise.
	(neon_check_type): Check architecture support for FP16 extension.
	(insns): Update comments.
	* testsuite/gas/arm/armv8-2-fp16-simd.s: New test source.
	* testsuite/gas/arm/armv8-2-fp16-simd.d: New testcase for arm mode.
	* testsuite/gas/arm/armv8-2-fp16-simd-thumb.d: Likewise for thumb mode.
	* testsuite/gas/arm/armv8-2-fp16-simd-warning.d: New rejection test for
	arm mode.
	* testsuite/gas/arm/armv8-2-fp16-simd-warning-thumb.d: Likewise for
	thumb mode.
	* testsuite/gas/arm/armv8-2-fp16-simd-warning.l: New expected rejection
	error file.

opcode/
	* arm-dis.c (neon_opcodes): Support new FP16 instructions.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] xml-tdesc.c (tdesc_start_enum): Fix c++ build.
@ 2016-03-16 17:48 sergiodj+buildbot
  2016-03-17 12:16 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-16 17:48 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bfeeb14b8468ab3f60d719f2cde697d1b537eba8 ***

Author: Doug Evans <dje@google.com>
Branch: master
Commit: bfeeb14b8468ab3f60d719f2cde697d1b537eba8

xml-tdesc.c (tdesc_start_enum): Fix c++ build.

gdb/ChangeLog:

	* xml-tdesc.c (tdesc_start_enum): Fix c++ build.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] PR remote/19496, interrupted syscall in forking-threads-plus-bkpt
@ 2016-03-16 22:29 sergiodj+buildbot
  2016-03-17 17:24 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-16 22:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7868401b7b63d851eea5de3b780591238d579bd1 ***

Author: Don Breazeal <donb@codesourcery.com>
Branch: master
Commit: 7868401b7b63d851eea5de3b780591238d579bd1

PR remote/19496, interrupted syscall in forking-threads-plus-bkpt

This patch addresses "fork:Interrupted system call" (or wait:) failures
in gdb.threads/forking-threads-plus-breakpoint.exp.

The test program spawns ten threads, each of which do ten fork/waitpid
sequences.  The cause of the problem was that when one of the fork
children exited before the corresponding fork parent could initiate its
waitpid for that child, a SIGCHLD and/or SIGSTOP was delivered and
interrupted a fork or waitpid in another thread.

The fix was to wrap the system calls in a loop to retry the call if
it was interrupted, like:

do
  {
    pid = fork ();
  }
while (pid == -1 && errno == EINTR);

Since this is a Linux-only test I figure it is OK to use errno and EINTR.
I tried a number of alternative fixes using SIG_IGN, SA_RESTART,
pthread_sigblock, and bsd_signal, but none of these worked as well.

Tested on Nios II Linux target with x86 Linux host.

gdb/testsuite/ChangeLog:
2016-03-16  Don Breazeal  <donb@codesourcery.com>

	* gdb.threads/forking-threads-plus-breakpoint.c (thread_forks):
	Retry fork and waitpid on interrupted system call errors.
	* gdb.threads/forking-threads-plus-breakpoint.exp: (do_test):
	Use with_timeout_factor to increase timeout to 90.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] linux-record: Fix bad fall-through for pipe/pipe2
@ 2016-03-17  9:19 sergiodj+buildbot
  2016-03-17 22:40 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-17  9:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT afdab9165435e17169b4984eeb29ea751319aa74 ***

Author: Andreas Arnez <arnez@linux.vnet.ibm.com>
Branch: master
Commit: afdab9165435e17169b4984eeb29ea751319aa74

linux-record: Fix bad fall-through for pipe/pipe2

This patch added handling for some syscalls to linux-record.c:

  https://sourceware.org/ml/gdb-patches/2015-10/msg00452.html

But for both `pipe' and `pipe2' the patch lacks a statement after an
`if', such that the following `break' is interpreted as the `if'-body
instead.

This adds the missing (return-) statements for the conditionals.

gdb/ChangeLog:

	* linux-record.c (record_linux_system_call): Add missing return
	statements to handling of pipe and pipe2 syscalls.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] linux-record.c: Fix whitespace issues
@ 2016-03-17  9:34 sergiodj+buildbot
  2016-03-18  0:55 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-17  9:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0fc8f115fd95a88ff2ce4c839b634b39d200c734 ***

Author: Andreas Arnez <arnez@linux.vnet.ibm.com>
Branch: master
Commit: 0fc8f115fd95a88ff2ce4c839b634b39d200c734

linux-record.c: Fix whitespace issues

This patch changes whitespace only, fixing whitespace issues in
linux-record.c.

gdb/ChangeLog:

	* linux-record.c: Fix whitespace issues; tabify, remove trailing
	spaces.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] S390: Fix output path for s390-multiarch test case
@ 2016-03-17 10:12 sergiodj+buildbot
  2016-03-18  3:17 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-17 10:12 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 64bcd522de3ae1b88d042986de8e36e44b9f2e42 ***

Author: Andreas Arnez <arnez@linux.vnet.ibm.com>
Branch: master
Commit: 64bcd522de3ae1b88d042986de8e36e44b9f2e42

S390: Fix output path for s390-multiarch test case

Since test artifacts are organized in a directory hierarchy, the
s390-multiarch test case is not executed correctly any more.  This is
because it uses an obsolete way of constructing the output paths.

This fix invokes standard_testfile instead.

gdb/testsuite/ChangeLog:

	* gdb.arch/s390-multiarch.exp: Use standard_testfile instead of
	maintaining separate logic for constructing the output path.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] PR remote/19496, timeout in forking-threads-plus-bkpt
@ 2016-03-17 10:43 sergiodj+buildbot
  2016-03-18  5:41 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-17 10:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0d5b594f86aa7c8f38487802f75841460ab705bf ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 0d5b594f86aa7c8f38487802f75841460ab705bf

PR remote/19496, timeout in forking-threads-plus-bkpt

This patch addresses a failure in
gdb.threads/forking-threads-plus-breakpoint.exp:

FAIL: gdb.threads/forking-threads-plus-breakpoint.exp: cond_bp_target=1:
detach_on_fork=on: inferior 1 exited (timeout)

Cause:

A fork event was reported to GDB before GDB knew about the parent
thread, followed immediately by a breakpoint event in a different
thread.  The parent thread was subsequently added via
remote_notice_new_inferior in process_stop_reply, but when the thread
was added the thread_info.state was set to THREAD_STOPPED.  The fork
event was then handled correctly, but when the fork parent was resumed
via a call to keep_going, the state was unchanged.

The breakpoint event was then handled, which caused all the
non-breakpoint threads to be stopped.  When the breakpoint thread was
resumed, all the non-breakpoint threads were resumed via
infrun.c:restart_threads.  Our old fork parent wasn't restarted,
because it still had thread_info.state set to THREAD_STOPPED.
Ultimately the program under debug hung waiting for a pthread_join
while the old fork parent was stopped forever by GDB.

Fix:

Since this is non-stop, then the bug is that the thread should have
been added in THREAD_RUNNING state.  Consider that infrun may be
pulling target events out of the target_ops backend into its own event
queue, but, not process them immediately.  E.g., infrun may be
stopping all threads temporarily for a step-over-breakpoint operation
for thread A (stop_all_threads).  The waitstatus of all threads is
thus left pending in the thread structure (save_status), including the
fork event of thread B.  Right at this point, if the user does "info
threads", that should show thread B (the fork parent) running, not
stopped, even if internally, gdb is holding it paused for a little
bit.

Thus if in non-stop mode, always add new threads in the external
user-visible THREAD_RUNNING state.  Change remote_notice_new_inferior
to accept the internal executing state of the thread instead, with
EXECUTING set to 1 when we discover a thread that is running on the
target (such as through remote_update_thread_list), and 0 when the
thread is really paused (such as when we see a stop reply).

Tested on x86_64 Linux and Nios II Linux target with x86 Linux host.

gdb/ChangeLog:
2016-03-17  Pedro Alves  <palves@redhat.com>
	    Don Breazeal  <donb@codesourcery.com>

	PR remote/19496
	* infcmd.c (notice_new_inferior): Use the 'leave_running' argument
	instead of checking the 'non_stop' global.
	* remote.c (remote_add_thread): New parameter 'executing'.  Use it
	to set the new thread's executing state.
	(remote_notice_new_inferior): Rename parameter 'running' to
	'executing'.  Always set the thread state to THREAD_RUNNING in
	non-stop mode, and to THREAD_STOPPED in all-stop mode.  Pass
	EXECUTING to remote_add_thread and notice_new_inferior.
	(remote_update_thread_list): Update to pass executing state, not
	running state.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Suggest running gdbserver for a PID in container
@ 2016-03-17 17:33 sergiodj+buildbot
  2016-03-18  8:19 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-17 17:33 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 708bf0a14b10d801a600759f3ef6d272978ae854 ***

Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Branch: master
Commit: 708bf0a14b10d801a600759f3ef6d272978ae854

Suggest running gdbserver for a PID in container

currently
	gdb -p <pid from a container>
will print:
	warning: Target and debugger are in different PID namespaces; thread lists and other data are likely unreliable

It correctly states the problem but it does not say how to solve it.

Originally I wanted to suggest also the Docker "-p 1234:1234" parameter but
I see the containers are more general topic than just Docker (even LxC etc.).

According to Gary future GDBs should be able to work even without gdbserver.
But currently gdbserver is still required.

gdb/ChangeLog
2016-03-17  Jan Kratochvil  <jan.kratochvil@redhat.com>

	* linux-thread-db.c (check_pid_namespace_match): Extend the message.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Add mips and s390 build targets for gold.
@ 2016-03-17 23:01 sergiodj+buildbot
  2016-03-18  9:10 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-17 23:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ea01647092eefeca9336b36809962ff097306b41 ***

Author: Cary Coutant <ccoutant@gmail.com>
Branch: master
Commit: ea01647092eefeca9336b36809962ff097306b41

Add mips and s390 build targets for gold.

	* configure.ac: Add mips and s390 to the gold target check.
	* configure: Regenerate.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Add simulation of MUL and NEG instructions to AArch64 simulator.
@ 2016-03-18  9:45 sergiodj+buildbot
  2016-03-18 15:36 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-18  9:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e101a78be9388651099af079899b8654292d24f6 ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: e101a78be9388651099af079899b8654292d24f6

Add simulation of MUL and NEG instructions to AArch64 simulator.

	* cpustate.c: Remove spurious spaces from TRACE strings.
	Print hex equivalents of floats and doubles.
	Check element number against array size when accessing vector
	registers.
	* memory.c: Trace memory reads when --trace-memory is enabled.
	Remove float and double load and store functions.
	* memory.h (aarch64_get_mem_float): Delete prototype.
	(aarch64_get_mem_double): Likewise.
	(aarch64_set_mem_float): Likewise.
	(aarch64_set_mem_double): Likewise.
	* simulator (IS_SET): Always return either 0 or 1.
	(IS_CLEAR): Likewise.
	(fldrs_pcrel): Load and store floats using 32-bit memory accesses
	and doubles using 64-bit memory accesses.
	(fldrd_pcrel, fldrs_wb, fldrs_abs, fldrs_scale_ext): Likewise.
	(fldrd_wb, fldrd_abs, fsturs, fsturd, fldurs, fldurd): Likewise.
	(fstrs_abs, fstrs_wb, fstrs_scale_ext, fstrd_abs): Likewise.
	(fstrd_wb, fstrd_scale_ext, store_pair_float): Likewise.
	(store_pair_double, load_pair_float, load_pair_double): Likewise.
	(do_vec_MUL_by_element): New function.
	(do_vec_op2): Call do_vec_MUL_by_element.
	(do_scalar_NEG): New function.
	(do_double_add): Call do_scalar_NEG.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Remove redundant WIFSTOPPED check
@ 2016-03-18 14:39 sergiodj+buildbot
  2016-03-18 18:04 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-18 14:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 80aea927cc7bf97a2bc22e1fb2111c52be295e8b ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 80aea927cc7bf97a2bc22e1fb2111c52be295e8b

Remove redundant WIFSTOPPED check

WIFSTOPPED is checked linux_wstatus_maybe_breakpoint, so WIFSTOPPED
in "WIFSTOPPED (wstat) && linux_wstatus_maybe_breakpoint (wstat)"
is redundant.  This patch removes WIFSTOPPED check.

gdb/gdbserver:

2016-03-18  Yao Qi  <yao.qi@linaro.org>

	* linux-low.c (linux_low_filter_event): Remove redundant
	WIFSTOPPED check together with linux_wstatus_maybe_breakpoint.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Set signal to 0 after enqueue_pending_signal
@ 2016-03-18 15:06 sergiodj+buildbot
  2016-03-18 20:41 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-18 15:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 94610ec4ee630e677d15361353796cac17339c53 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 94610ec4ee630e677d15361353796cac17339c53

Set signal to 0 after enqueue_pending_signal

Today, we enqueue signal in linux_resume_one_lwp_throw, but set
variable 'signal' many lines below with the comment

      /* Postpone any pending signal.  It was enqueued above.  */
      signal = 0;

I feel difficult to associate code across many lines, and we should
move the code close to enqueue_pending_signal call.  This is what
this patch does in general.  After this change, variable 'signal'
is set to zero very early, so the 'signal' value in the following
debugging message makes no sense, so I remove it from the debugging
message.  The function returns early if lwp->status_pending_p is
true, so 'signal' value in the debugging message doesn't matter,
AFAICS.  Also, I move one debugging message several lines below to
make it close the real ptrace call,

  if (debug_threads)
    debug_printf ("Resuming lwp %ld (%s, signal %d, stop %s)\n",
		  lwpid_of (thread), step ? "step" : "continue", signal,
		  lwp->stop_expected ? "expected" : "not expected");

so that the debugging message can reflect what GDBserver does.  This
is a code refactor and only debugging messages are affected.

gdb/gdbserver:

2016-03-18  Yao Qi  <yao.qi@linaro.org>

	* linux-low.c (linux_resume_one_lwp_throw): Set 'signal' to
	0 if signal is enqueued.  Remove 'signal' from one debugging
	message.  Move one debugging message to some lines below.
	Remove code setting 'signal' to 0.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Check lwp_signal_can_be_delivered for enqueue/dequeue pending signals
@ 2016-03-18 15:17 sergiodj+buildbot
  2016-03-18 21:45 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-18 15:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 35ac8b3e2dbbe1fcd107dfcc6bbc4faed6bdc63f ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 35ac8b3e2dbbe1fcd107dfcc6bbc4faed6bdc63f

Check lwp_signal_can_be_delivered for enqueue/dequeue pending signals

The enqueue and dequeue signals in linux_resume_one_lwp_throw use one
condition and its inverted one.  This patch is to move the condition
into a function lwp_signal_can_be_delivered, so that the next patch can
change the condition in one place.

gdb/gdbserver:

2016-03-18  Yao Qi  <yao.qi@linaro.org>

	* linux-low.c (lwp_signal_can_be_delivered): New function.
	(linux_resume_one_lwp_throw): Use lwp_signal_can_be_delivered.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix code to check for illegal element numbers when accessing AArch64 vector registers in AArch64 sim.
@ 2016-03-18 15:36 sergiodj+buildbot
  2016-03-19  0:23 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-18 15:36 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4c0ca98e58fc409c93b41bb6c42f3e873db47725 ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: 4c0ca98e58fc409c93b41bb6c42f3e873db47725

Fix code to check for illegal element numbers when accessing AArch64 vector registers in AArch64 sim.

	* cpustate.c (GET_VEC_ELEMENT): Fix off by one error checking
	for an invalid element index.
	(SET_VEC_ELEMENT): Likewise.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Make sparc_software_single_step static
@ 2016-03-18 15:45 sergiodj+buildbot
  2016-03-19  1:43 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-18 15:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9c3f22346dd632201807c0718d5281ed1eea329f ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 9c3f22346dd632201807c0718d5281ed1eea329f

Make sparc_software_single_step static

sparc_software_single_step is not used out of sparc-tdep.c, so this
patch makes it static.

gdb:

2016-03-18  Yao Qi  <yao.qi@linaro.org>

	* sparc-tdep.c (sparc_software_single_step): Make it static.
	* sparc-tdep.h (sparc_software_single_step): Remove declaration.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] [spu] throw error when target_read_memory fails
@ 2016-03-18 16:52 sergiodj+buildbot
  2016-03-18 23:00 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-18 16:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 941319d15194580a047484a53f232d374dc2d712 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 941319d15194580a047484a53f232d374dc2d712

[spu] throw error when target_read_memory fails

I happen to see that 1 is returned in spu_software_single_step when
target_read_memory returns 1.  It must be wrong.  That patch changes
it to throwing an error.  Note that I choose to throw error because I
find the code in the end of spu_software_single_step throws errors.

gdb:

2016-03-18  Yao Qi  <yao.qi@linaro.org>

	* spu-tdep.c (spu_software_single_step): Throw error when
	target_read_memory fails.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix thinko in new GET_VEC_ELEMENT macro.
@ 2016-03-18 17:25 sergiodj+buildbot
  2016-03-19  5:40 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-18 17:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 87bba7a5e0858048c9b8702c147094d1a7eba92f ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: 87bba7a5e0858048c9b8702c147094d1a7eba92f

Fix thinko in new GET_VEC_ELEMENT macro.

	* cpustate.c: (GET_VEC_ELEMENT): And fix thinko using macro arguments.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
* [binutils-gdb] Fix the disassembly of the AArch64's OOR instruction as a MOV instruction.
@ 2016-03-18 18:39 sergiodj+buildbot
  2016-03-19  3:43 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
  0 siblings, 1 reply; 2113+ messages in thread
From: sergiodj+buildbot @ 2016-03-18 18:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8678914fcb40e4c620a33e6b38a14df928fa780a ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: 8678914fcb40e4c620a33e6b38a14df928fa780a

Fix the disassembly of the AArch64's OOR instruction as a MOV instruction.

	PR target/19721
opcodes	* aarch64-tbl.h (aarch64_opcode_table): Fix type of second operand
	of MOV insn that aliases an ORR insn.

gas	* testsuite/gas/aarch64/pr19721.s: New test source file.
	* testsuite/gas/aarch64/pr19721.d: New test driver file.


^ permalink raw reply	[flat|nested] 2113+ messages in thread
end of thread, other threads:[~2016-03-19  5:37 UTC | newest]

Thread overview: 2113+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <dfc87947b5ac6d6382c225449d4fdce411c7ee66@kwanyin>
2015-07-01 17:12 ` Failures on AIX-POWER7-plain, branch master sergiodj+buildbot
2015-07-01 17:27 ` Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot
2015-07-01 17:50 ` Failures on Debian-i686, " sergiodj+buildbot
2015-07-01 18:02 ` Failures on Fedora-ppc64be-cc-with-index, " sergiodj+buildbot
2015-07-01 18:06 ` Failures on Debian-i686-native-gdbserver, " sergiodj+buildbot
2015-07-01 18:23 ` Failures on Fedora-ppc64be-m64, " sergiodj+buildbot
2015-07-01 18:31 ` Failures on Debian-i686-native-extended-gdbserver, " sergiodj+buildbot
2015-07-01 18:36 ` Failures on Fedora-i686, " sergiodj+buildbot
2015-07-01 18:41 ` Failures on Fedora-ppc64le-native-extended-gdbserver-m64, " sergiodj+buildbot
2015-07-01 19:02 ` Failures on Fedora-ppc64be-native-extended-gdbserver-m64, " sergiodj+buildbot
2015-07-01 19:10 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot
2015-07-01 19:36 ` Failures on Debian-x86_64-native-gdbserver-m64, " sergiodj+buildbot
2015-07-01 20:03 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot
2015-09-11 14:43 [binutils-gdb] gdb/18947: [aarch64]Step into shared library is very slow sergiodj+buildbot
2015-09-11 15:59 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-09-11 16:06 [binutils-gdb] [AArch64] Fix incorrect mask when decoding b.cond instruction sergiodj+buildbot
2015-09-11 17:38 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-09-11 16:41 [binutils-gdb] [AArch64] Cleanup comments in instruction decoding functions sergiodj+buildbot
2015-09-11 18:59 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-09-11 18:33 [binutils-gdb] Extended-remote follow-exec sergiodj+buildbot
2015-09-11 21:19 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-09-11 18:42 [binutils-gdb] Extended-remote catch exec sergiodj+buildbot
2015-09-11 23:29 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-09-11 18:47 [binutils-gdb] Extended-remote exec test sergiodj+buildbot
2015-09-12  1:16 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-09-11 19:53 [binutils-gdb] Extended-remote exec documentation sergiodj+buildbot
2015-09-12  6:55 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-09-12 17:42 [binutils-gdb] Set .plt entry size to 0 in elf32-hppa.c sergiodj+buildbot
2015-09-14 10:44 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-09-14 12:50 [binutils-gdb] btrace, test: remove buffer-size test with unlimited buffer size sergiodj+buildbot
2015-09-14 14:36 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-09-14 15:05 [binutils-gdb] [Ada] Fix the evaluation of access to packed array subscript sergiodj+buildbot
2015-09-14 18:42 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-09-14 15:40 [binutils-gdb] Bail out of processing stop if hook-stop resumes target / changes context sergiodj+buildbot
2015-09-15  0:53 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-09-15  9:41 [binutils-gdb] Fix the SH behavior for EF_SH_PIC flag in FDPIC ABI sergiodj+buildbot
2015-09-15 10:01 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-09-15 10:25 [binutils-gdb] aarch64 multi-arch support (part 2): siginfo fixup sergiodj+buildbot
2015-09-15 13:27 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-09-15 13:45 [binutils-gdb] [gdbserver] Rename supports_conditional_breakpoints to supports_hardware_single_step sergiodj+buildbot
2015-09-15 15:42 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-09-15 14:02 [binutils-gdb] Support single step by arch or target sergiodj+buildbot
2015-09-15 16:55 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-09-15 16:59 [binutils-gdb] Fix gdb.threads/non-ldr-exc-3.exp race sergiodj+buildbot
2015-09-15 18:43 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-09-15 17:18 [binutils-gdb] Fix typo sergiodj+buildbot
2015-09-15 20:46 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-09-15 17:23 [binutils-gdb] PR remote/18965: vforkdone stop reply should indicate parent PID sergiodj+buildbot
2015-09-15 21:56 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-09-15 18:41 [binutils-gdb] [AArch64] Use debug_printf instead of fprintf_unfiltered sergiodj+buildbot
2015-09-16 12:35 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-09-15 19:46 [binutils-gdb] Fix PR/18564 - regression in showing __thread so extern variable sergiodj+buildbot
2015-09-16 13:03 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-09-15 20:19 [binutils-gdb] xtensa: generate PLT entries for call0 ABI sergiodj+buildbot
2015-09-16 13:29 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-09-15 21:24 [binutils-gdb] Handle clang naming of function static local variable sergiodj+buildbot
2015-09-16 15:03 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-09-15 22:14 [binutils-gdb] [Ada] Enhance type printing for arrays with variable-sized elements sergiodj+buildbot
2015-09-16 16:25 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-09-16 13:43 [binutils-gdb] Fix slowdown in ld -r for most common case of out-of-order relocs sergiodj+buildbot
2015-09-16 20:47 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-09-16 15:38 [binutils-gdb] Make it easier to debug non-stop-fair-events.exp sergiodj+buildbot
2015-09-17 10:51 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-09-16 17:26 [binutils-gdb] Fix argument to compiled_cond, and add cases for compiled-condition sergiodj+buildbot
2015-09-17 11:13 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-09-17 11:54 [binutils-gdb] Add test case for tracepoints with conditions sergiodj+buildbot
2015-09-18  3:23 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-09-18 13:17 [binutils-gdb] btrace: improve stepping debugging sergiodj+buildbot
2015-09-18 17:28 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-09-18 13:30 [binutils-gdb] btrace: extract the breakpoint check from record_btrace_step_thread sergiodj+buildbot
2015-09-18 19:02 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-09-18 13:50 [binutils-gdb] btrace: split record_btrace_step_thread sergiodj+buildbot
2015-09-18 21:00 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-09-18 14:04 [binutils-gdb] btrace: add missing NO_HISTORY sergiodj+buildbot
2015-09-18 23:59 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-09-18 14:13 [binutils-gdb] btrace: lock-step sergiodj+buildbot
2015-09-19  3:21 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-09-18 14:15 [binutils-gdb] btrace: resume all requested threads sergiodj+buildbot
2015-09-19  6:20 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-09-18 14:30 [binutils-gdb] btrace: async sergiodj+buildbot
2015-09-19 11:15 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-09-18 14:37 [binutils-gdb] infrun: switch to NO_HISTORY thread sergiodj+buildbot
2015-09-19 14:24 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-09-18 14:47 [binutils-gdb] btrace: non-stop sergiodj+buildbot
2015-09-19 15:41 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-09-18 14:54 [binutils-gdb] target, record: add PTID argument to to_record_is_replaying sergiodj+buildbot
2015-09-19 16:07 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-09-18 15:02 [binutils-gdb] btrace: allow full memory and register access for non-replaying threads sergiodj+buildbot
2015-09-19 17:35 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-09-18 15:02 [binutils-gdb] target: add to_record_stop_replaying target method sergiodj+buildbot
2015-09-19 20:00 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-09-18 15:12 [binutils-gdb] target: add to_record_will_replay target method sergiodj+buildbot
2015-09-19 21:34 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-09-18 15:19 [binutils-gdb] btrace: move breakpoint checking into stepping functions sergiodj+buildbot
2015-09-18 22:24 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-09-18 15:44 [binutils-gdb] infrun: scheduler-locking replay sergiodj+buildbot
2015-09-19 23:38 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-09-18 16:29 [binutils-gdb] Require readline for gdb.linespec/explicit.exp tab-completion tests sergiodj+buildbot
2015-09-20  6:51 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-09-18 16:46 [binutils-gdb] Fix shared library load in gdb.base/global-var-nested-by-dso.exp sergiodj+buildbot
2015-09-20 10:28 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-09-18 17:29 [binutils-gdb] Generalize breakpoint pattern in gdb.mi/mi-cli.exp sergiodj+buildbot
2015-09-20 14:25 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-09-18 19:46 [binutils-gdb] Fix pathname prefix and timeout issues in gdb.mi/mi-pending.exp sergiodj+buildbot
2015-09-20 18:26 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-09-18 21:29 [binutils-gdb] aarch64 multi-arch (part 3): get thread area sergiodj+buildbot
2015-09-20  4:11 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-09-19  6:25 [binutils-gdb] symtab.h (general_symbol_info) <mangled_lang>: delete and move up only member sergiodj+buildbot
2015-09-20 19:05 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-09-19 17:02 [binutils-gdb] Replace current_inferior ()->gdbarch with its wrapper target_gdbarch sergiodj+buildbot
2015-09-20 22:02 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-09-20  7:58 [binutils-gdb] Add --no-dynamic-linker option to ld, for static PIE use sergiodj+buildbot
2015-09-20 22:45 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-09-20 19:59 [binutils-gdb] crash printing non-local variable from nested subprogram sergiodj+buildbot
2015-09-21  5:27 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-09-20 22:27 [binutils-gdb] dwarf2_compute_name: add fixme, don't use same name as parameter for local sergiodj+buildbot
2015-09-21  6:05 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-09-21  6:23 [binutils-gdb] dwarf2read.c (add_partial_symbol): Remove outdated comments sergiodj+buildbot
2015-09-21 11:42 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-09-21 14:29 [binutils-gdb] Wrap gdb_agent_op_sizes by #ifndef IN_PROCESS_AGENT sergiodj+buildbot
2015-09-21 15:37 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-09-21 14:42 [binutils-gdb] Move instruction decoding into new arch/ directory sergiodj+buildbot
2015-09-21 17:16 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-09-21 14:52 [binutils-gdb] Make aarch64_decode_adrp handle both ADR and ADRP instructions sergiodj+buildbot
2015-09-21 19:33 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-09-21 15:08 [binutils-gdb] Implement target_emit_ops sergiodj+buildbot
2015-09-21 23:08 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-09-21 15:19 [binutils-gdb] Add a gdb.trace test for instruction relocation sergiodj+buildbot
2015-09-22  3:18 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-09-21 15:44 [binutils-gdb] Add a test case for fast tracepoints' locking mechanism sergiodj+buildbot
2015-09-22  6:19 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-09-21 15:50 [binutils-gdb] Add NEWS entry for fast tracepoint support on aarch64-linux sergiodj+buildbot
2015-09-22  6:36 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-09-21 16:34 [binutils-gdb] Enable fast tracepoint tests sergiodj+buildbot
2015-09-22  2:10 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-09-21 18:09 [binutils-gdb] Change ch_type in Elf64_External_Chdr to 4 bytes sergiodj+buildbot
2015-09-22  9:26 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-09-22  0:01 [binutils-gdb] Add two missing consts sergiodj+buildbot
2015-09-22 10:05 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-09-22  7:22 [binutils-gdb] opcodes/ppc-opc.c: Add dscr and ctrl SPR mnemonics sergiodj+buildbot
2015-09-22 15:29 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-09-22 10:26 [binutils-gdb] Solaris PIE support sergiodj+buildbot
2015-09-22 15:59 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-09-22 17:51 [binutils-gdb] Enhance the RX disassembler to detect and report bad instructions sergiodj+buildbot
2015-09-23  3:36 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-09-23 21:13 [binutils-gdb] [Ada] Fix handling of array renamings sergiodj+buildbot
2015-09-24  0:51 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-09-24  1:12 [binutils-gdb] Allow any size enum in gdb.cp/var-tag.exp sergiodj+buildbot
2015-09-24 23:23 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-09-24 23:46 [binutils-gdb] [FT32] Implement pointer to address conversion method sergiodj+buildbot
2015-09-25  0:14 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-09-25  0:05 [binutils-gdb] Test case, disassembler not showing RIMM literals correctly #14 sergiodj+buildbot
2015-09-25  5:10 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-09-25  0:35 [binutils-gdb] Accidentally added file. Removed it sergiodj+buildbot
2015-09-25 14:57 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-09-25  2:06 [binutils-gdb] Generalize enum regexp in gdb.cp/classes.exp sergiodj+buildbot
2015-09-25 15:08 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-09-25 15:17 [binutils-gdb] Correct the generation of OR1K pc-relative relocations sergiodj+buildbot
2015-09-25 18:30 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-09-25 18:49 [binutils-gdb] Add casts to memory allocation related calls sergiodj+buildbot
2015-09-25 19:20 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-09-25 19:00 [binutils-gdb] Add some more casts (1/2) sergiodj+buildbot
2015-09-25 19:48 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-09-25 19:30 [binutils-gdb] Add some more casts (2/2) sergiodj+buildbot
2015-09-25 19:54 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-09-25 20:12 [binutils-gdb] The FT32's disassembly of 10-bit literals has the incorrect mask sergiodj+buildbot
2015-09-25 20:29 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-09-26  8:11 [binutils-gdb] [D] Fix regression in py-lookup-type.exp sergiodj+buildbot
2015-09-26  8:37 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-09-28  2:50 [binutils-gdb] Fix cast of xml_find_attribute's return value sergiodj+buildbot
2015-09-28  3:34 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-09-28 15:45 [binutils-gdb] Patches for illegal ppc 500 instructions sergiodj+buildbot
2015-09-28 16:07 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-09-28 18:35 [binutils-gdb] Updare French translation for binutils and German translation for opcodes sergiodj+buildbot
2015-09-28 19:03 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-09-28 19:11 [binutils-gdb] FT32: define macros for instruction recognition sergiodj+buildbot
2015-09-28 20:00 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-09-28 19:25 [binutils-gdb] common/filestuff.c (make_cleanup_close): Update comment sergiodj+buildbot
2015-09-28 20:59 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-09-28 22:09 [binutils-gdb] gdb.base/gcore.c (array_func): Add reference to static_array sergiodj+buildbot
2015-09-28 23:25 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-09-29  0:39 [binutils-gdb] cli-script.c: Fix read_next_line's comment sergiodj+buildbot
2015-09-29 12:51 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-09-29 17:05 [binutils-gdb] [FT32] Replace hard-coded instruction patterns with macros sergiodj+buildbot
2015-09-29 18:01 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-09-29 17:29 [binutils-gdb] Rebase patch #7 sergiodj+buildbot
2015-09-29 20:44 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-09-29 18:14 [binutils-gdb] Undo accidental commit sergiodj+buildbot
2015-09-29 21:10 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-09-30  5:04 [binutils-gdb] sim: ft32: correct simulation of MEMCPY and MEMSET sergiodj+buildbot
2015-09-30  6:11 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-09-30  6:50 [binutils-gdb] Add fdpic and misc targets to config.bfd for sh*-*-linux* sergiodj+buildbot
2015-09-30 12:48 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-09-30 13:26 [binutils-gdb] Also check e_machine when merging sections sergiodj+buildbot
2015-09-30 14:00 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-09-30 13:35 [binutils-gdb] btrace, testsuite: fix spurious gdb.btrace/tsx.exp fails sergiodj+buildbot
2015-09-30 15:27 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-09-30 13:51 [binutils-gdb] infcmd.c: Don't attempt to record a NULL value after a finish command sergiodj+buildbot
2015-09-30 15:56 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-09-30 15:14 [binutils-gdb] py-type.exp: Do not run tests if binary fails to build sergiodj+buildbot
2015-09-30 17:17 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-09-30 15:42 [binutils-gdb] Shorten long lines in linux-aarch64-low.c sergiodj+buildbot
2015-09-30 18:03 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-09-30 16:59 [binutils-gdb] Create a PLT entry for R_386_PC32 in non-code sections sergiodj+buildbot
2015-09-30 20:14 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-09-30 17:44 [binutils-gdb] Resync files in the binutils repository that are maintained in the gcc repository sergiodj+buildbot
2015-09-30 22:23 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-09-30 18:38 [binutils-gdb] Call strprefix instead of strncmp in event parsing sergiodj+buildbot
2015-09-30 22:55 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-01  5:31 [binutils-gdb] bfd/config.bfd: Drop non-linux non-fdpic stuff from the last change of targ_selvecs of sh*-linux cases sergiodj+buildbot
2015-10-01  6:00 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-01 15:37 [binutils-gdb] vec.h: Add casts for C++ compat sergiodj+buildbot
2015-10-01 16:06 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-02 14:38 [binutils-gdb] [aarch64] Remove argument pc from disas_aarch64_insn sergiodj+buildbot
2015-10-02 15:06 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-02 14:46 [binutils-gdb] [aarch64] expose disas_aarch64_insn and rename it to aarch64_decode_insn sergiodj+buildbot
2015-10-02 16:08 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-02 17:14 [binutils-gdb] [BFD][AARCH64]Refactor to facilitate further large memory model support patches sergiodj+buildbot
2015-10-02 18:11 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-02 17:31 [binutils-gdb] [GAS][AARCH64]Add BFD_RELOC_AARCH64_MOVW_GOTOFF_G1 Support sergiodj+buildbot
2015-10-02 20:09 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-02 17:39 [binutils-gdb] [LD][AARCH64]Add BFD_RELOC_AARCH64_MOVW_GOTOFF_G1 Support sergiodj+buildbot
2015-10-02 21:09 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-02 17:40 [binutils-gdb] [LD][AARCH64]Add BFD_RELOC_AARCH64_LD64_GOTOFF_LO15 Support sergiodj+buildbot
2015-10-02 19:10 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-02 17:47 [binutils-gdb] [GAS][AARCH64]Add BFD_RELOC_AARCH64_MOVW_GOTOFF_G0_NC Support sergiodj+buildbot
2015-10-02 22:09 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-02 17:55 [binutils-gdb] [LD][AARCH64]Add BFD_RELOC_AARCH64_MOVW_GOTOFF_G0_NC Support sergiodj+buildbot
2015-10-02 23:09 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-02 18:03 [binutils-gdb] [GAS][AARCH64]Add BFD_RELOC_AARCH64_TLSGD_MOVW_G1 support sergiodj+buildbot
2015-10-03  0:10 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-02 18:11 [binutils-gdb] [LD][AARCH64]Add BFD_RELOC_AARCH64_TLSGD_MOVW_G1 support sergiodj+buildbot
2015-10-03  2:54 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-02 18:19 [binutils-gdb] [GAS][AARCH64]Add BFD_RELOC_AARCH64_TLSGD_MOVW_G0_NC support sergiodj+buildbot
2015-10-03  4:55 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-02 18:27 [binutils-gdb] [LD][AARCH64]Add BFD_RELOC_AARCH64_TLSGD_MOVW_G0_NC support sergiodj+buildbot
2015-10-03  6:49 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-02 18:42 [binutils-gdb] [BFD][AARCH64]Create GOT section for TLSLE_MOVW_TPREL_G(1, 1_NC, 2) sergiodj+buildbot
2015-10-03  9:37 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-02 18:57 [binutils-gdb] [GAS][AARCH64]Add TLSDESC large memory model support sergiodj+buildbot
2015-10-03 11:41 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-02 19:13 [binutils-gdb] [LD][AARCH64]Add TLSIE relaxation support under large memory model sergiodj+buildbot
2015-10-03 13:41 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-02 21:25 [binutils-gdb] [Binutils][AARCH64]Add TLS IE large memory support sergiodj+buildbot
2015-10-03  8:35 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-02 23:54 [binutils-gdb] Fix gdb.dwarf2/staticvirtual.exp regexp sergiodj+buildbot
2015-10-03 14:41 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-03  0:44 [binutils-gdb] [FT32] gdb: Correctly interpret function prologs sergiodj+buildbot
2015-10-03 15:40 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-04 14:52 [binutils-gdb] Enable IAMCU and PEI for Solaris2/x86 sergiodj+buildbot
2015-10-04 15:21 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-06 16:41 [binutils-gdb] parse load_offset (bias) of restore command as long sergiodj+buildbot
2015-10-06 17:09 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-07 13:26 [binutils-gdb] New ARC implementation sergiodj+buildbot
2015-10-07 14:00 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-07 14:11 [binutils-gdb] Wrap include/opcode/aarch64.h in extern "C" for C++ sergiodj+buildbot
2015-10-07 14:59 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-08  7:41 [binutils-gdb] btrace: fix void return sergiodj+buildbot
2015-10-08  8:15 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-08 11:43 [binutils-gdb] Fix compile time warning compiling ARC port sergiodj+buildbot
2015-10-08 12:12 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-08 18:17 [binutils-gdb] MAINTAINERS: Update my email address sergiodj+buildbot
2015-10-08 18:50 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-08 19:56 [binutils-gdb] [D] Support D style sizeof and typeof expressions sergiodj+buildbot
2015-10-08 20:26 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-09 12:07 [binutils-gdb] Fix gdb.base/a2-run.exp race sergiodj+buildbot
2015-10-09 12:36 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-09 12:40 [binutils-gdb] btrace, test: avoid gdb.btrace/vdso.exp fail sergiodj+buildbot
2015-10-09 13:37 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-09 14:28 [binutils-gdb] arm-linux-tdep: Add explicit cast for int to gdb_syscall conversion sergiodj+buildbot
2015-10-09 17:37 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-09 14:36 [binutils-gdb] cris: Use enum bfd_endian to represent endianness sergiodj+buildbot
2015-10-09 18:39 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-09 14:44 [binutils-gdb] i386: Fix type of gdbarch_tdep::register_reggroup_p sergiodj+buildbot
2015-10-09 19:42 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-09 21:52 [binutils-gdb] use gdb_byte in ada-lang.c::ada_value_primitive_packed_val sergiodj+buildbot
2015-10-09 23:13 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-09 22:07 [binutils-gdb] [Ada] split data unpacking code out of ada_value_primitive_packed_val sergiodj+buildbot
2015-10-10  2:59 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-09 22:23 [binutils-gdb] make is_scalar_type non-static and use it in ada-lang.c sergiodj+buildbot
2015-10-10  6:00 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-09 22:31 [binutils-gdb] [Ada] Buffer overflow in ada_unpack_from_contents sergiodj+buildbot
2015-10-10  7:02 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-09 22:39 [binutils-gdb] [Ada] ada_unpack_from_contents: Error if target buffer not large enough sergiodj+buildbot
2015-10-10  8:03 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-11  7:54 [binutils-gdb] sim: bfin: handle negative left saturated shifts as ashifts [BZ #18407] sergiodj+buildbot
2015-10-11  8:22 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-11  8:08 [binutils-gdb] sim: moxie: fix leakage in error path [BZ #18273] sergiodj+buildbot
2015-10-11  9:22 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-11 23:20 [binutils-gdb] Ignore references with relocs to discarded sections in .data.rel.ro.local on hppa-linux sergiodj+buildbot
2015-10-11 23:48 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-12  8:32 [binutils-gdb] PR19083 S/390: Fix garbage collection of some GOT relocs sergiodj+buildbot
2015-10-12  9:00 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-12 10:32 [binutils-gdb] Forward VALUE_LVAL when avoiding side effects for STRUCTOP_STRUCT sergiodj+buildbot
2015-10-12 11:00 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-12 10:41 [binutils-gdb] More tests in gdb.arch/insn-reloc.c sergiodj+buildbot
2015-10-12 11:59 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-12 10:57 [binutils-gdb] Move append_insns out of aarch64_relocate_instruction sergiodj+buildbot
2015-10-12 13:59 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-12 11:13 [binutils-gdb] Move aarch64_relocate_instruction to arch/aarch64-insn.c sergiodj+buildbot
2015-10-12 15:57 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-12 11:28 [binutils-gdb] Support displaced stepping in support_displaced_stepping for aarch64*-*-linux* sergiodj+buildbot
2015-10-12 17:56 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-12 11:36 [binutils-gdb] New test case gdb.arch/disp-step-insn-reloc.exp sergiodj+buildbot
2015-10-12 18:56 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-12 11:38 [binutils-gdb] Move target_read_uint32 out of aarch64_relocate_instruction sergiodj+buildbot
2015-10-12 12:59 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-12 11:53 [binutils-gdb] Rename emit_load_store to aarch64_emit_load_store sergiodj+buildbot
2015-10-12 20:55 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-12 13:05 [binutils-gdb] Support displaced stepping in aarch64-linux sergiodj+buildbot
2015-10-12 16:57 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-12 15:35 [binutils-gdb] Skip the unversioned definition after the default version sergiodj+buildbot
2015-10-12 22:55 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-12 16:35 [binutils-gdb] aarch64: Use gdb_sys_no_syscall enum instead of -1 sergiodj+buildbot
2015-10-12 23:55 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-12 17:23 [binutils-gdb] m32c: Split m32c_move_reg_t in read/write variants sergiodj+buildbot
2015-10-13  3:43 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-12 21:41 [binutils-gdb] gdb: Make use of safe-ctype.h header sergiodj+buildbot
2015-10-13  5:49 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-12 21:49 [binutils-gdb] gdb: Fix bug with dbx style func command sergiodj+buildbot
2015-10-13  6:49 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-12 21:57 [binutils-gdb] gdb: Avoid unneeded calls to parse_frame_specification sergiodj+buildbot
2015-10-13  7:49 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-12 22:05 [binutils-gdb] gdb: Simplify parse_frame_specification sergiodj+buildbot
2015-10-13  8:48 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-13  0:32 [binutils-gdb] sim: ft32: test coverage for link parameters and PM write port sergiodj+buildbot
2015-10-13  9:48 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-13  6:14 [binutils-gdb] Tidy code setting PT_GNU_RELRO p_flags sergiodj+buildbot
2015-10-13 10:49 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
     [not found] <4666fec3b414c7880e9629f3c9b0a5b584235c6d@gdb-build>
2015-10-13 18:25 ` sergiodj+buildbot
2015-10-13 18:50 [binutils-gdb] ada-lang.c: malloc/alloca casts for C++ sergiodj+buildbot
2015-10-13 19:28 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-13 18:58 [binutils-gdb] ada-lang.c:ada_value_primitive_packed_val: const correctness sergiodj+buildbot
2015-10-13 20:31 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
     [not found] <170742de5dd5be2156f938e00e2451526ef57d5c@gdb-build>
2015-10-13 21:31 ` sergiodj+buildbot
     [not found] <e6a959d68b8181c816851dcfc91ae0b2b9296df3@gdb-build>
2015-10-13 22:34 ` sergiodj+buildbot
2015-10-13 22:55 [binutils-gdb] Recognize a few more AIX XCOFF DWARF sections sergiodj+buildbot
2015-10-13 23:37 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-14  8:47 [binutils-gdb] Define enum out of struct sergiodj+buildbot
2015-10-14  8:59 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-14  9:08 [binutils-gdb] S/390: Fix instruction type of troo, trot, trto, and trtt sergiodj+buildbot
2015-10-14 10:17 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-14 22:32 [binutils-gdb] bfd: [SH] Emit DT_PLTGOT for FDPIC output unconditionally sergiodj+buildbot
2015-10-14 23:00 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-15 13:20 [binutils-gdb] objcopy --extract-symbol sergiodj+buildbot
2015-10-15 14:36 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-15 14:19 [binutils-gdb] aarch64 multi-arch part 6: HW breakpoint on unaligned address sergiodj+buildbot
2015-10-15 15:36 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-15 18:10 [binutils-gdb] Fix typos in comments in _bfd_elf_merge_symbol sergiodj+buildbot
2015-10-15 18:39 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-16 12:22 [binutils-gdb] Convert mov to lea for loading address of local common symbol sergiodj+buildbot
2015-10-16 12:49 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-16 12:29 [binutils-gdb] Check if symbol is defined when converting mov to lea sergiodj+buildbot
2015-10-16 13:50 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-16 12:37 [binutils-gdb] MAINTAINERS: Fix my inconsistent email address sergiodj+buildbot
2015-10-16 14:49 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-16 15:20 [binutils-gdb] gdbserver: Reset current_thread when the thread is removed sergiodj+buildbot
2015-10-16 15:49 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-18 20:26 [binutils-gdb] targets.c (bfd_flavour_name): "MMO" is spelled "mmo" sergiodj+buildbot
2015-10-18 21:05 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-19 10:26 [binutils-gdb] Robustify inherit.exp and virtbase.exp sergiodj+buildbot
2015-10-19 10:56 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-19 13:46 [binutils-gdb] Make GDB wait for events after handling target File-I/O sergiodj+buildbot
2015-10-19 14:23 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-20  5:08 [binutils-gdb] Correct printed value of Main in mmo.c consistency error message sergiodj+buildbot
2015-10-20  5:42 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-20 16:11 [binutils-gdb] Add --enable-compressed-debug-sections={all, gas, gold, ld} sergiodj+buildbot
2015-10-20 16:47 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-20 17:16 [binutils-gdb] [nto] Fixes for nto procfs sergiodj+buildbot
2015-10-20 17:47 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-20 17:32 [binutils-gdb] [nto] Implement procfs_pid_to_exec_file sergiodj+buildbot
2015-10-20 19:54 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-20 17:40 [binutils-gdb] [nto] Implement TARGET_OBJECT_AUXV sergiodj+buildbot
2015-10-20 18:50 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-20 18:50 [binutils-gdb] Fix internal error on DW_OP_bregx(-1) sergiodj+buildbot
2015-10-20 20:50 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-21 12:27 [binutils-gdb] Reset x86 Linux targets to not compressing debug sections by default. Enable compression of debug sections by default in the linker, if so configured sergiodj+buildbot
2015-10-21 13:37 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-21 14:47 [binutils-gdb] [nto] Fix nto target stopped by watchpoint sergiodj+buildbot
2015-10-21 15:15 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-21 14:54 [binutils-gdb] [nto] Improve ABI sniffing sergiodj+buildbot
2015-10-21 16:14 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-21 15:35 [binutils-gdb] Add the target_ops needed for software breakpoints in GDBServer sergiodj+buildbot
2015-10-21 18:15 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-21 15:42 [binutils-gdb] Support breakpoint kinds for software breakpoints in GDBServer sergiodj+buildbot
2015-10-21 19:16 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-21 16:43 [binutils-gdb] Implement breakpoint_kind_from_pc and sw_breakpoint_from_kind for ARM in GDBServer sergiodj+buildbot
2015-10-21 20:17 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-21 17:05 [binutils-gdb] Adjust timeout in gdb.base/freebpcmd.exp sergiodj+buildbot
2015-10-21 23:22 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-21 19:47 [binutils-gdb] fort_dyn_array: add basic fortran dyn array support sergiodj+buildbot
2015-10-22  1:01 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-21 20:12 [binutils-gdb] Fix accessing a function's fields (parameters) from Python (PR 18073) sergiodj+buildbot
2015-10-22  3:10 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-22  8:43 [binutils-gdb] S/390: ifunc: Fix for undefined ifunc symbols sergiodj+buildbot
2015-10-22  9:54 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-22  8:59 [binutils-gdb] S/390: ifunc: Fix function pointers to hidden ifunc symbols sergiodj+buildbot
2015-10-22 12:56 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-22  9:07 [binutils-gdb] S/390: ifunc: Redirect local function calls to the IPLT sergiodj+buildbot
2015-10-22 13:57 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-22  9:43 [binutils-gdb] S/390: ifunc: Handle GOTOFF relocs on ifunc symbols sergiodj+buildbot
2015-10-22 12:08 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-22 12:23 [binutils-gdb] Add "-z call-nop=PADDING" option to ld sergiodj+buildbot
2015-10-22 16:58 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-22 13:59 [binutils-gdb] mips: fix void*/gdb_byte* compilation errors sergiodj+buildbot
2015-10-22 17:57 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-22 16:10 [binutils-gdb] Add cast in nto-tdep.c sergiodj+buildbot
2015-10-23  0:02 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-22 16:23 [binutils-gdb] Add cast in python.c sergiodj+buildbot
2015-10-23  2:01 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-22 16:35 [binutils-gdb] Fix inconsistent breakpoint kinds between breakpoints and tracepoints in GDBServer sergiodj+buildbot
2015-10-23  4:05 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-22 16:53 [binutils-gdb] garbage collect gdb/infrun.c:stop_after_trap sergiodj+buildbot
2015-10-23  6:04 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
     [not found] <3e45d68b7088df39d0520d1a92005cfdf4e2b922@gdb-build>
2015-10-22 18:58 ` sergiodj+buildbot
2015-10-22 19:35 [binutils-gdb] Always keep sections marked with SEC_KEEP sergiodj+buildbot
2015-10-23  7:14 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
     [not found] <5af9928d44e302b7f68365a0c551f640895366ff@gdb-build>
2015-10-22 19:58 ` sergiodj+buildbot
     [not found] <60905b1e2a5fbd734bfd026cd77b9641cc5f3e66@gdb-build>
2015-10-22 21:02 ` sergiodj+buildbot
2015-10-23  0:02 [binutils-gdb] Re: Always keep sections marked with SEC_KEEP sergiodj+buildbot
2015-10-23  8:36 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-23  8:38 [binutils-gdb] Initialize field insn_count correctly sergiodj+buildbot
2015-10-23  9:29 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-23 12:05 [binutils-gdb] Handle __start_* and __stop_* symbols in --gc-sections sergiodj+buildbot
2015-10-23 12:35 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-23 17:33 [binutils-gdb] Refactor default_breakpoint_kind_from_pc to be used by all targets in GDBServer sergiodj+buildbot
2015-10-23 18:03 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-23 17:40 [binutils-gdb] Fix nto,spu and win32 builds of GDBServer sergiodj+buildbot
2015-10-23 19:04 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-23 17:48 [binutils-gdb] Remove set_breakpoint_data definition in GDBServer sergiodj+buildbot
2015-10-23 20:05 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-23 21:07 [binutils-gdb] Add cast to observer.sh sergiodj+buildbot
2015-10-23 21:39 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-24  0:05 [binutils-gdb] Add mmap casts in linux-btrace.c sergiodj+buildbot
2015-10-24  0:45 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-24 22:47 [binutils-gdb] ia64-tdep.c: Remove (void *) casts sergiodj+buildbot
2015-10-24 23:20 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-24 23:02 [binutils-gdb] proc-service.c: Add (gdb_byte *) cast sergiodj+buildbot
2015-10-25  3:00 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-24 23:13 [binutils-gdb] sparc64-tdep.c: Don't assign using memcpy return sergiodj+buildbot
2015-10-25  0:29 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-25  3:45 [binutils-gdb] tui-data.c: Remove unnecessary casts sergiodj+buildbot
2015-10-25  8:45 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
     [not found] <1650ca11248ca377a6c8b6f7e21ec2aa8e7b3fd5@gdb-build>
2015-10-25  7:38 ` sergiodj+buildbot
2015-10-25  8:29 [binutils-gdb] Re-apply change for handling non-local references in nested functions sergiodj+buildbot
2015-10-25 11:25 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-26 12:52 [binutils-gdb] scm-symbol.c: Add (domain_enum) casts sergiodj+buildbot
2015-10-26 13:24 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-26 13:08 [binutils-gdb] symtab.c: Add cast sergiodj+buildbot
2015-10-26 15:26 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-26 13:08 [binutils-gdb] gdbscm_memory_port_write: use local variable to avoid adding casts sergiodj+buildbot
2015-10-26 14:33 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-26 13:17 [binutils-gdb] Fix constness problem in ioscm_make_gdb_stdio_port sergiodj+buildbot
2015-10-26 16:29 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-26 13:29 [binutils-gdb] Do not pass NULL for the string in catch_errors sergiodj+buildbot
2015-10-26 17:27 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-26 15:26 [binutils-gdb] Properly convert address load of __start_XXX/__stop_XXX sergiodj+buildbot
2015-10-26 18:30 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-26 17:08 [binutils-gdb] tui: Simplify tui_alloc_content sergiodj+buildbot
2015-10-26 19:28 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-26 20:31 [binutils-gdb] Add some casts for building on musl sergiodj+buildbot
2015-10-26 21:28 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-26 20:39 [binutils-gdb] musl: Move W_STOPCODE to common/gdb_wait.h sergiodj+buildbot
2015-10-26 22:27 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-26 20:47 [binutils-gdb] Move __SIGRTMIN sergiodj+buildbot
2015-10-26 23:28 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-26 22:10 [binutils-gdb] PR python/18938: source -s foo.py with foo.py a symlink to foo.notpy fails sergiodj+buildbot
2015-10-27  1:38 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-26 23:16 [binutils-gdb] PR symtab/17391 gdb internal error: assertion fails in regcache.c:178 sergiodj+buildbot
2015-10-27  3:50 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-26 23:44 [binutils-gdb] Check symbol defined by assignment in linker script sergiodj+buildbot
2015-10-27  6:16 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-27  2:18 [binutils-gdb] stap-probe.c: Add casts sergiodj+buildbot
2015-10-27 10:55 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-27  2:26 [binutils-gdb] target.c: Add a cast and change a type sergiodj+buildbot
2015-10-27 12:38 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-27  5:19 [binutils-gdb] Fix access_to_packed_array.exp typos/errors sergiodj+buildbot
2015-10-27 14:37 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-27 10:40 [binutils-gdb] Add support for 32-bit and 64-bit PowerPC AIX core files sergiodj+buildbot
2015-10-27 15:39 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-27 13:39 [binutils-gdb] ada-lang.h: Add cast in GROW_VECT sergiodj+buildbot
2015-10-27 18:47 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-27 14:11 [binutils-gdb] Fix RL78 disassembly so that SP+OFFSET addressing always shows the offset, even when zero sergiodj+buildbot
2015-10-27 21:44 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-27 14:45 [binutils-gdb] Add scm_t_dynwind_flags casts sergiodj+buildbot
2015-10-27 20:48 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-27 15:01 [binutils-gdb] Display system registers by their names when disassembling RL78 instructions sergiodj+buildbot
2015-10-27 22:48 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-27 15:06 [binutils-gdb] ctf.c: Fix int/enum implicit cast sergiodj+buildbot
2015-10-27 23:45 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-27 15:37 [binutils-gdb] Fix RL78 disassembly of DE+offset addressing to always show the offset, even when zero sergiodj+buildbot
2015-10-28  2:57 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-27 17:03 [binutils-gdb] source.c:openp: save/restore errno sergiodj+buildbot
2015-10-28  5:31 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
     [not found] <c5192092506e52a5f075b137a36933e42db64563@gdb-build>
2015-10-28  7:17 ` sergiodj+buildbot
     [not found] <d09f2c3fc15dd4491e9cfa455191045c0729a3c3@gdb-build>
2015-10-28  9:17 ` sergiodj+buildbot
     [not found] <b80c3053162ec5533e120ee4e4ed30296d4c5fb2@gdb-build>
2015-10-28 10:59 ` sergiodj+buildbot
2015-10-28 13:58 [binutils-gdb] Fix errors in the gas testsuite for the ARC target sergiodj+buildbot
2015-10-28 14:32 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-28 14:07 [binutils-gdb] Fix recent STM324LXX patch to compile on 32-bit hosts sergiodj+buildbot
2015-10-28 15:28 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-28 14:49 [binutils-gdb] Pass noaliases_p to aarch64_decode_insn sergiodj+buildbot
2015-10-28 16:31 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-29 14:16 [binutils-gdb] gdbserver: enum gdb_signal casts sergiodj+buildbot
2015-10-29 18:36 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-29 14:31 [binutils-gdb] gdbserver/mem-break.c: Add cast sergiodj+buildbot
2015-10-29 20:33 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
     [not found] <e3bdafe2bac1672da335fde734b337c5504e5437@gdb-build>
2015-10-29 14:34 ` sergiodj+buildbot
2015-10-29 14:48 [binutils-gdb] gdbserver/Linux: Introduce NULL_REGSET sergiodj+buildbot
2015-10-29 16:45 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-29 14:54 [binutils-gdb] 2015-10-29 Catherine Moore <clm@codesourcery.com> sergiodj+buildbot
2015-10-29 23:34 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
     [not found] <44a8b4df1d6f5b8096f01787751fd51c42e78fc6@gdb-build>
2015-10-29 15:40 ` sergiodj+buildbot
2015-10-29 16:32 [binutils-gdb] Add support for AArch64 CloudABI binaries sergiodj+buildbot
2015-10-29 22:33 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
     [not found] <add67df84c59a6c28111d65e8d0a7e6b4994cdb1@gdb-build>
2015-10-29 17:34 ` sergiodj+buildbot
2015-10-29 17:42 [binutils-gdb] Disable paging when run by Emacs 25.1 and later sergiodj+buildbot
2015-10-30  2:37 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-29 18:06 [binutils-gdb] dwarf2read.c: Add cast sergiodj+buildbot
2015-10-30  7:14 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-29 18:21 [binutils-gdb] gdbserver/server.c: Cast return value of memmem sergiodj+buildbot
2015-10-30  9:13 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-10-29 18:59 [binutils-gdb] gdbserver: Move pointer dereference to after assert checks sergiodj+buildbot
2015-10-30 13:17 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
     [not found] <7535d5edeaa5cfa5ba369e8d3ffb47972483394a@gdb-build>
2015-10-30  6:11 ` sergiodj+buildbot
     [not found] <f98cd059076c64cdb94b9743c544458b2b91716c@gdb-build>
2015-10-30  8:16 ` sergiodj+buildbot
     [not found] <d2242e347a25dc15fbf7286975e3baba143deea9@gdb-build>
2015-10-30 12:34 ` sergiodj+buildbot
2015-10-30 12:57 [binutils-gdb] Updated (simplified) Chinese translations for ld, bfd, binutils and gold sergiodj+buildbot
2015-10-30 13:26 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
     [not found] <b42945fd28b881e23016ce2efaf5fd83d5038f34@gdb-build>
2015-10-30 13:06 ` sergiodj+buildbot
     [not found] <452b4ba5f70df5b8b2332bcadd46eec95273b50b@gdb-build>
2015-10-30 17:30 ` sergiodj+buildbot
     [not found] <aefb52a69351517dbcfaafca1d21e5431d4119d1@gdb-build>
2015-10-30 18:30 ` sergiodj+buildbot
     [not found] <7571f7f297c8d8b4fb4657f84437b1d156957e16@gdb-build>
2015-10-30 20:33 ` sergiodj+buildbot
     [not found] <72aded8673d6cb2d0e33696e010a778e9bbfa817@gdb-build>
2015-10-30 21:31 ` sergiodj+buildbot
2015-10-30 22:03 [binutils-gdb] Don't displaced step when there's a breakpoint in the scratch pad range sergiodj+buildbot
2015-10-31 14:29 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
     [not found] <933c5a623f247c63b642988a2984f5ce9b558d27@gdb-build>
2015-10-30 22:34 ` sergiodj+buildbot
     [not found] <b80d067ff0a7d2fcca3f8c01abf4b7201e71b8f0@gdb-build>
2015-10-30 23:42 ` sergiodj+buildbot
     [not found] <cb658d218b873a69b1f19971695f92d5db17a388@gdb-build>
2015-10-31  0:38 ` sergiodj+buildbot
     [not found] <d2de23ad3916c9d6f6102688fdbd5fdc73053c43@gdb-build>
2015-10-31  2:25 ` sergiodj+buildbot
     [not found] <ff83a547feacaea9263c04f527aba4faae77035f@gdb-build>
2015-10-31  4:48 ` sergiodj+buildbot
     [not found] <c28ebe255ba37f4dcd295cf6a4608424aaeb699f@gdb-build>
2015-10-31  7:41 ` sergiodj+buildbot
     [not found] <d9b19c4992e7384f12441bc13c0e22d4054b0487@gdb-build>
2015-10-31 10:09 ` sergiodj+buildbot
     [not found] <10268a4c0d64b3892397aeaafbc4b91f6a1e0dc8@gdb-build>
2015-10-31 11:52 ` sergiodj+buildbot
2015-11-03 18:52 [binutils-gdb] Disassemble RX NOP instructions as such sergiodj+buildbot
2015-11-03 20:18 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-03 19:40 [binutils-gdb] remote-sim.c: Add casts sergiodj+buildbot
2015-11-04  3:23 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-03 21:16 [binutils-gdb] linux-ppc-low.c: Add casts sergiodj+buildbot
2015-11-04  1:30 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
     [not found] <7ad8b86c674ed941b354322f608cd964ca0affb2@gdb-build>
2015-11-03 22:18 ` sergiodj+buildbot
     [not found] <d5f0636bf6fb6b5e54cd405811cfbfcc98fa667b@gdb-build>
2015-11-03 23:15 ` sergiodj+buildbot
     [not found] <f4b0a6714adb7371e3b7a0f47589c3dfd958cd09@gdb-build>
2015-11-04  5:43 ` sergiodj+buildbot
     [not found] <04b3479c3f92e102c5a7d1158ab608e0015252c6@gdb-build>
2015-11-04  7:33 ` sergiodj+buildbot
2015-11-04  8:26 [binutils-gdb] disasm: split dump_insns sergiodj+buildbot
2015-11-04 16:26 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-04  8:34 [binutils-gdb] disasm: add struct disasm_insn to describe to-be-disassembled instruction sergiodj+buildbot
2015-11-04 17:39 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-04  8:43 [binutils-gdb] btrace: change record instruction-history /m sergiodj+buildbot
2015-11-04 18:29 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-04  8:49 [binutils-gdb] btrace: add instruction-history /s and fix documentation sergiodj+buildbot
2015-11-04 19:31 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
     [not found] <04248ead1f57204119180022580626e31c165f60@gdb-build>
2015-11-04  9:13 ` sergiodj+buildbot
2015-11-04 10:35 [binutils-gdb] Fix non stopping breakpoint on newer compilers sergiodj+buildbot
2015-11-04 22:49 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
     [not found] <f844cf0ec3887110375e9c1d4c48a68cb6a8b141@gdb-build>
2015-11-04 11:19 ` sergiodj+buildbot
     [not found] <cbec665beba8acf6393a8c93312bdd3a03a0846c@gdb-build>
2015-11-04 13:21 ` sergiodj+buildbot
2015-11-04 15:04 [binutils-gdb] Fortran: allocate()d memory is uninitialized sergiodj+buildbot
2015-11-05  3:56 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
     [not found] <1c215b97f9a64d6ba9821e8a0cf0f44526f29d78@gdb-build>
2015-11-04 15:22 ` sergiodj+buildbot
     [not found] <394816ee10a85e3e0fa7c9b0a4ca29e7e160e63c@gdb-build>
2015-11-04 23:40 ` sergiodj+buildbot
     [not found] <566c56c91116321f48573a0a4274cc5244330490@gdb-build>
2015-11-05  0:30 ` sergiodj+buildbot
     [not found] <6df55226405d626059f81bec3078a70db41dec9f@gdb-build>
2015-11-05  1:47 ` sergiodj+buildbot
2015-11-05 10:06 [binutils-gdb] Use aarch64_decode_insn in aarch64_displaced_step_copy_insn sergiodj+buildbot
2015-11-05 12:34 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-05 22:32 [binutils-gdb] gdb.dwarf2: Define and use gdb_target_symbol for symbol prefixes sergiodj+buildbot
2015-11-05 23:09 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-07 18:17 [binutils-gdb] testsuite: Define and use gdb_target_symbol_prefix_flags_asm sergiodj+buildbot
2015-11-07 18:49 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-07 18:22 [binutils-gdb] gdb.dwarf2: Don't hardcode certain constants in Dwarf::assemble constructs sergiodj+buildbot
2015-11-07 19:47 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-09  5:01 [binutils-gdb] Copy gnulib obstack files sergiodj+buildbot
2015-11-09  5:42 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-09  5:43 [binutils-gdb] Modify obstack.[hc] to avoid having to include other gnulib files sergiodj+buildbot
2015-11-09  5:44 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-09  5:57 [binutils-gdb] Configury changes for obstack optimization sergiodj+buildbot
2015-11-09  7:53 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
     [not found] <78d14d2b9325fb4d25034eccf5650ef967d19640@gdb-build>
2015-11-09  6:54 ` sergiodj+buildbot
2015-11-09  8:59 [binutils-gdb] Move copy_u.w to MSA64 ASE, remove copy_u.d sergiodj+buildbot
2015-11-09  9:45 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-09 14:49 [binutils-gdb] New function displaced_step_in_progress_thread sergiodj+buildbot
2015-11-09 15:26 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-09 16:07 [binutils-gdb] Use ELF_STRING_ARM_unwind in arm-tdep.c sergiodj+buildbot
2015-11-09 16:44 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-09 16:23 [binutils-gdb] bfd: Fix left shift of negative value sergiodj+buildbot
2015-11-09 18:02 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-09 18:08 [binutils-gdb] [Ada] GDB crash during "finish" of function with out parameters sergiodj+buildbot
2015-11-09 19:03 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-10  5:19 [binutils-gdb] sim: h8300: drop unused littleendian variable sergiodj+buildbot
2015-11-10  5:46 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-10  5:24 [binutils-gdb] sim: m32c: drop redundant dependency info sergiodj+buildbot
2015-11-10  7:01 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-10  5:32 [binutils-gdb] sim: m32c: move test code to testsuite sergiodj+buildbot
2015-11-10  7:51 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-10  7:01 [binutils-gdb] Fix performance regression due to ld -r memmove sergiodj+buildbot
2015-11-10  8:46 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-10  8:11 [binutils-gdb] Fix performance regression on x86 with ld -r sergiodj+buildbot
2015-11-10 10:53 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-10 12:38 [binutils-gdb] Handle x86 VTINHERIT/VTENTRY relocs when deleting relocations sergiodj+buildbot
2015-11-10 13:27 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
     [not found] <6e7675a70f5a375159f94354fb6f38519303a73d@gdb-build>
2015-11-10 19:53 ` sergiodj+buildbot
2015-11-11 10:07 [binutils-gdb] gdb: Make use of 'add_info' to create info sub-commands sergiodj+buildbot
2015-11-11 11:30 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-11 20:26 [binutils-gdb] Replace long int * cast with PTRACE_TYPE_RET * sergiodj+buildbot
2015-11-11 21:02 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
     [not found] <430e004ef7ecb3f75fc3c6642c9fdfb1d85a3694@gdb-build>
2015-11-11 22:17 ` sergiodj+buildbot
2015-11-12  9:25 [binutils-gdb] Use gdb_byte * instead of void * in push_stack_item sergiodj+buildbot
2015-11-12 10:02 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-13 15:14 [binutils-gdb] gdb.base/gnu_vector.exp: Don't test output from the inferior sergiodj+buildbot
2015-11-13 15:50 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-13 15:22 [binutils-gdb] Remove d10v from testsuite sergiodj+buildbot
2015-11-13 16:50 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-13 15:37 [binutils-gdb] PR 19051: support of inferior call with gnu vector support on ARM sergiodj+buildbot
2015-11-13 18:47 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-15  5:51 [binutils-gdb] sim: drop extern C linkage from most sim interface headers sergiodj+buildbot
2015-11-15  6:55 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-15  6:14 [binutils-gdb] sim: testsuite: support basic vars in flags sergiodj+buildbot
2015-11-15  9:11 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-15  7:40 [binutils-gdb] sim: sim-close: unify sim_close logic sergiodj+buildbot
2015-11-15 12:46 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-15  7:53 [binutils-gdb] sim: clean up redundant objects sergiodj+buildbot
2015-11-15 13:47 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-15 13:41 [binutils-gdb] sim: mcore: switch to common sim-reg sergiodj+buildbot
2015-11-15 17:26 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-15 13:49 [binutils-gdb] sim: mcore: add a fail testcase sergiodj+buildbot
2015-11-15 16:24 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-15 13:49 [binutils-gdb] sim: mcore: pull cpu state out of global scope sergiodj+buildbot
2015-11-15 18:57 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-16  1:59 [binutils-gdb] sim: d10v: push down sd/cpu vars sergiodj+buildbot
2015-11-16  2:33 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-16  2:15 [binutils-gdb] sim: d10v: drop global callback state sergiodj+buildbot
2015-11-16  4:41 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-16  2:24 [binutils-gdb] sim: d10v: convert to common sim engine logic sergiodj+buildbot
2015-11-16  3:37 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-16  3:24 [binutils-gdb] sim: cr16/d10v: drop redundant call to sim_create_inferior sergiodj+buildbot
2015-11-16  5:41 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-16  3:31 [binutils-gdb] sim: cr16: delete unused memory helpers sergiodj+buildbot
2015-11-16  7:46 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-16  3:48 [binutils-gdb] sim: cr16: convert to common sim memory modules sergiodj+buildbot
2015-11-16 10:05 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-16  3:55 [binutils-gdb] sim: cr16: convert to common sim engine logic sergiodj+buildbot
2015-11-16 10:47 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-16  4:03 [binutils-gdb] sim: cr16: drop global callback state sergiodj+buildbot
2015-11-16 11:56 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-16  4:30 [binutils-gdb] sim: cr16: push down sd/cpu vars sergiodj+buildbot
2015-11-16  8:53 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-16  7:53 [binutils-gdb] sim: sim-stop/sim-reason/sim-reg: move to common obj list sergiodj+buildbot
2015-11-16 12:52 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-16 14:53 [binutils-gdb] Fix bug in arm_push_dummy_call by -fsanitize=address sergiodj+buildbot
2015-11-16 15:23 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-16 15:03 [binutils-gdb] Use value_contents instead of value_contents_writeable sergiodj+buildbot
2015-11-16 16:25 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-16 15:12 [binutils-gdb] Pass value * instead of bfd_byte * to pass_* functions in aarch64-tdep.c sergiodj+buildbot
2015-11-16 17:25 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-16 15:47 [binutils-gdb] Fix stack buffer overflow in aarch64_extract_return_value sergiodj+buildbot
2015-11-16 21:05 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-17 10:11 [binutils-gdb] gdb: Fix left shift of negative value sergiodj+buildbot
2015-11-17 10:41 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-17 11:55 [binutils-gdb] Fix a problematic message with the STM32L4XX fixup on 32-bit hosts sergiodj+buildbot
2015-11-17 13:42 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-17 13:56 [binutils-gdb] guile disassembly hardcode TARGET_XFER_E_IO sergiodj+buildbot
2015-11-17 14:43 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-17 14:19 [binutils-gdb] Mach-O: add new defines and struct for darwin 14.5 sergiodj+buildbot
2015-11-17 17:45 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-17 15:43 [binutils-gdb] [C++/mingw] Misc alloca casts sergiodj+buildbot
2015-11-17 19:47 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
     [not found] <8d297bbf604c8318ffc72d5a7b3db654409c5ed9@gdb-build>
2015-11-17 15:43 ` sergiodj+buildbot
2015-11-17 15:51 [binutils-gdb] [C++/mingw] gdb-dlfcn.c casts sergiodj+buildbot
2015-11-17 20:50 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-17 15:58 [binutils-gdb] [C++/mingw] windows-nat.c casts sergiodj+buildbot
2015-11-17 21:53 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-17 16:14 [binutils-gdb] [C++/mingw] ser-tcp.c casts sergiodj+buildbot
2015-11-17 23:50 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-17 16:22 [binutils-gdb] [C++/mingw] handle_output_debug_string sergiodj+buildbot
2015-11-18  1:08 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-17 16:29 [binutils-gdb] [C++/mingw] Fix windows-nat.c::xlate sergiodj+buildbot
2015-11-18  2:43 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-17 16:37 [binutils-gdb] [C++/mingw] gdbserver: gdb/host signal mixup sergiodj+buildbot
2015-11-18  3:54 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-17 16:45 [binutils-gdb] [C++/mingw] Simplify first chance exception handling sergiodj+buildbot
2015-11-18  5:04 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-17 17:01 [binutils-gdb] MinGW and attribute format(printf/gnu_printf) sergiodj+buildbot
2015-11-18  6:26 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-17 17:09 [binutils-gdb] [C++] Always use setjmp/longjmp for exceptions sergiodj+buildbot
2015-11-18  6:35 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-17 17:18 [binutils-gdb] Introduce null_block_symbol sergiodj+buildbot
2015-11-18  6:44 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-17 17:26 [binutils-gdb] Fix gdb.threads/multiple-step-overs.exp fails on arm sergiodj+buildbot
2015-11-18  6:54 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-17 21:29 [binutils-gdb] [sim/ppc] Fix printf_filtered reference sergiodj+buildbot
2015-11-18  7:03 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-18  4:18 [binutils-gdb] sim: always enable modulo memory sergiodj+buildbot
2015-11-18  7:12 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-18  4:25 [binutils-gdb] sim: mn10300/v850: drop unused WITH_CORE define sergiodj+buildbot
2015-11-18  7:21 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-18 11:42 [binutils-gdb] mach-o cleanup: remove useless calls to bfd_seek sergiodj+buildbot
2015-11-18 11:47 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-18 11:52 [binutils-gdb] Prevent looping in archives sergiodj+buildbot
2015-11-18 11:56 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-18 12:02 [binutils-gdb] Fix out of boundary access in pass_in_v sergiodj+buildbot
2015-11-18 12:05 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-18 13:17 [binutils-gdb] [gdbserver/ipa] Fix build dependencies sergiodj+buildbot
2015-11-18 13:46 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-18 16:11 [binutils-gdb] Constify value_cstring sergiodj+buildbot
2015-11-18 16:45 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-19  9:35 [binutils-gdb] [ARM] Add ARMv8.2 architecture feature and command line option sergiodj+buildbot
2015-11-19 11:08 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-19 10:20 [binutils-gdb] [S/390] Add null ptr check + port GOTOFF handling from 32 bit over to 64 bit sergiodj+buildbot
2015-11-19 12:03 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-19 14:11 [binutils-gdb] Cast void * to struct user_pt_regs * sergiodj+buildbot
2015-11-19 14:42 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-19 14:21 [binutils-gdb] Cast void * to user_fpsimd_state * sergiodj+buildbot
2015-11-19 15:43 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-19 14:34 [binutils-gdb] Change argument opcode type from enum aarch64_opcodes to uint32_t sergiodj+buildbot
2015-11-19 17:43 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-19 14:46 [binutils-gdb] [AArch64] Reject invalid immediate operands to MSR PAN sergiodj+buildbot
2015-11-19 18:47 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-19 15:28 [binutils-gdb] [C++] Default to -Werror in C++ mode too sergiodj+buildbot
2015-11-20  0:57 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-19 18:47 [binutils-gdb] gdb: Workaround bad gdbserver qSupported:xmlRegisters=i386; UnknwnFeat+ handling sergiodj+buildbot
2015-11-20  4:01 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-19 18:55 [binutils-gdb] gdbserver: Fix qSupported:xmlRegisters=i386; UnknownFeature+ handling sergiodj+buildbot
2015-11-20  6:25 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
     [not found] <915ef8b18e28e6418216a582067b9fbdd6395e6a@gdb-build>
2015-11-19 19:44 ` sergiodj+buildbot
     [not found] <c6d811243634c84e185a25faf33491ee1a5f900a@gdb-build>
2015-11-19 22:55 ` sergiodj+buildbot
     [not found] <bb82e93484cdd56c67efd52b869a6123b2623f6c@gdb-build>
2015-11-20  2:15 ` sergiodj+buildbot
2015-11-20  9:53 [binutils-gdb] sparc: fix build of gdb/testsuite/gdb.arch/sparc-sysstep.c sergiodj+buildbot
2015-11-20 10:30 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-20 10:38 [binutils-gdb] callfuncs.exp: avoid spurious register differences in sparc64 targets sergiodj+buildbot
2015-11-20 11:44 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-20 12:50 [binutils-gdb] Update translations sergiodj+buildbot
2015-11-20 13:23 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-20 13:08 [binutils-gdb] Synchronize PDP11 page size between BFD and LD sergiodj+buildbot
2015-11-20 14:31 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-20 14:25 [binutils-gdb] Fix missing update in previous patch sergiodj+buildbot
2015-11-20 16:45 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-20 15:13 [binutils-gdb] Remove a if-clause that is redundant because the same test has been performed earlier on sergiodj+buildbot
2015-11-20 17:55 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-20 15:38 [binutils-gdb] Fix a problem with the maximum number of open files held in the cache when running on a 32-bit Solaris host sergiodj+buildbot
2015-11-20 19:05 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-20 16:23 [binutils-gdb] [AArch64] Add support for ARMv8.1 Virtulization Host Extensions sergiodj+buildbot
2015-11-20 20:29 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-22  6:11 [binutils-gdb] sim: mn10300: drop global callback handle sergiodj+buildbot
2015-11-22  6:42 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-22  6:19 [binutils-gdb] sim: h8300: delete global callback/kind/name sergiodj+buildbot
2015-11-22  7:41 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-22  6:40 [binutils-gdb] sim: avr: switch to common sim-reg sergiodj+buildbot
2015-11-22  9:46 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-22  6:50 [binutils-gdb] sim: common: add PRI printf defines sergiodj+buildbot
2015-11-22 11:53 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-22  7:00 [binutils-gdb] sim: sh: delete global callback/argv sergiodj+buildbot
2015-11-22  8:48 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-22  7:11 [binutils-gdb] sim: ppc: avoid use of $< in ordinary rules [PR sim/13834] sergiodj+buildbot
2015-11-22 12:48 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-22  8:08 [binutils-gdb] sim: common: set up CPPFLAGS/CXXFLAGS/LDFLAGS from configure [PR sim/18762] sergiodj+buildbot
2015-11-22 14:57 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-23 10:41 [binutils-gdb] darwin-nat: rewrite darwin_read_write_inferior sergiodj+buildbot
2015-11-23 11:15 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-23 14:05 [binutils-gdb] solib-darwin: support PIE for spawned processes sergiodj+buildbot
2015-11-23 14:39 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-23 14:42 [binutils-gdb] darwin-nat: disable sstep cache sergiodj+buildbot
2015-11-23 15:37 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-23 14:59 [binutils-gdb] opcodes: handle mach-o for thumb/arm disambiguation sergiodj+buildbot
2015-11-23 16:44 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-23 17:53 [binutils-gdb] gdb/dwarf2read: Minimal handling of non-constant struct sizes sergiodj+buildbot
2015-11-23 18:23 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-23 18:09 [binutils-gdb] [ARM] "svc" insn check at irrelevant address in ARM unwind info sniffer sergiodj+buildbot
2015-11-23 20:28 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-23 18:24 [binutils-gdb] [LynxOS] GDBserver crash debugging threaded program sergiodj+buildbot
2015-11-23 22:37 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-23 19:54 [binutils-gdb] error/internal-error printing local variable during "bt full" sergiodj+buildbot
2015-11-23 23:38 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-23 23:05 [binutils-gdb] minsyms.c: Scan backwards over all zero sized symbols sergiodj+buildbot
2015-11-24  0:29 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-24  0:05 [binutils-gdb] Refactor gdb.trace/save-trace.exp sergiodj+buildbot
2015-11-24  1:37 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-24  8:59 [binutils-gdb] Add an AArch64 simulator to GDB sergiodj+buildbot
2015-11-24  9:35 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-24 18:51 [binutils-gdb] Make gdb.python/py-inferior.exp test names unique sergiodj+buildbot
2015-11-24 19:21 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-24 18:58 [binutils-gdb] Linux: dump the signalled thread first sergiodj+buildbot
2015-11-24 20:20 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-24 19:13 [binutils-gdb] List checkpoints in ascending order sergiodj+buildbot
2015-11-24 22:20 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-24 19:21 [binutils-gdb] List displays in ascending order sergiodj+buildbot
2015-11-24 23:22 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-26 10:35 [binutils-gdb] btrace: diagnose "record btrace pt" without libipt sergiodj+buildbot
2015-11-26 11:09 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-26 16:04 [binutils-gdb] Display names of remote threads sergiodj+buildbot
2015-11-26 17:41 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-26 18:28 [binutils-gdb] Add test for thread names sergiodj+buildbot
2015-11-26 19:06 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-27 13:32 [binutils-gdb] [AArch64] Add feature flags and command line for ARMv8.2 FP16 support sergiodj+buildbot
2015-11-27 14:07 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-27 14:32 [binutils-gdb] Use ${frames_invalid} in gdb.cp/annota2.exp sergiodj+buildbot
2015-11-27 16:04 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-27 15:00 [binutils-gdb] [AArch64] Support gnu vector in inferior call sergiodj+buildbot
2015-11-27 19:07 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-27 15:08 [binutils-gdb] [AArch64] Handle HFA and HVA together sergiodj+buildbot
2015-11-27 20:12 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-27 15:24 [binutils-gdb] Use multi_line to make pattern more human readable sergiodj+buildbot
2015-11-27 18:10 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-27 16:04 [binutils-gdb] [AArch64] Let aliased instructions be their preferred form sergiodj+buildbot
2015-11-27 23:31 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-27 16:37 [binutils-gdb] New test gdb.arch/arm-neon.exp sergiodj+buildbot
2015-11-27 21:13 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-27 16:42 [binutils-gdb] [AArch64][PATCH 2/3] Adjust a utility function for floating point values sergiodj+buildbot
2015-11-28  9:05 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-27 18:23 [binutils-gdb] [AArch64] Add ARMv8.2 instructions BFC and REV64 sergiodj+buildbot
2015-11-28  1:18 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-27 19:07 [binutils-gdb] [AArch64][PATCH 1/3] Support ARMv8.2 FP16 floating point instructions sergiodj+buildbot
2015-11-28  7:00 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
     [not found] <e19616610d7327664f99215a69cb326682742dc3@gdb-build>
2015-11-28  0:16 ` sergiodj+buildbot
2015-11-28 16:50 [binutils-gdb] Avoid "enum conversion when passing argument 1 of 'getrusage' is invalid in C++" warning sergiodj+buildbot
2015-11-28 17:25 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-28 17:05 [binutils-gdb] Fix several crashes of C++ demangler on fuzzed input sergiodj+buildbot
2015-11-28 19:41 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-28 17:21 [binutils-gdb] Fix PR63758 by using the _NSGetEnviron() API on Darwin sergiodj+buildbot
2015-11-28 21:31 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-28 17:28 [binutils-gdb] (Makefiles): PATCH to include libcpp and libiberty in GCC etags sergiodj+buildbot
2015-11-28 22:32 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-28 17:44 [binutils-gdb] PR other/61321 - demangler crash on casts in template parameters sergiodj+buildbot
2015-11-29  0:37 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-28 18:00 [binutils-gdb] Port libvtv to Solaris sergiodj+buildbot
2015-11-29  3:07 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-28 18:08 [binutils-gdb] libsanitizer merge from upstream r250806, compiler part sergiodj+buildbot
2015-11-29  4:03 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-28 18:09 [binutils-gdb] Implement N4514, C++ Extensions for Transactional Memory sergiodj+buildbot
2015-11-28 20:34 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-30 20:05 [binutils-gdb] Fix mi-nonstop.exp with extended-remote sergiodj+buildbot
2015-11-30 20:40 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-30 20:13 [binutils-gdb] Remote all-stop-on-top-of-non-stop sergiodj+buildbot
2015-11-30 21:42 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-30 20:28 [binutils-gdb] gdbserver crash running gdb.threads/non-ldr-exc-1.exp sergiodj+buildbot
2015-11-30 23:48 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-30 20:36 [binutils-gdb] remote: stop reason and watchpoint data address per thread sergiodj+buildbot
2015-12-01  0:47 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-30 21:00 [binutils-gdb] gdbserver resume_stop handling bug sergiodj+buildbot
2015-12-01  5:11 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-30 21:07 [binutils-gdb] Make dprintf-non-stop.exp cope with remote testing sergiodj+buildbot
2015-12-01  6:06 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-30 21:14 [binutils-gdb] Remote thread create/exit events sergiodj+buildbot
2015-12-01  7:08 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-30 21:45 [binutils-gdb] Implement TARGET_WAITKIND_NO_RESUMED in the remote protocol sergiodj+buildbot
2015-12-01 11:08 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-30 21:53 [binutils-gdb] gdbserver:prepare_access_memory: pick another thread sergiodj+buildbot
2015-12-01 12:09 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-30 22:08 [binutils-gdb] gdbserver: don't exit until GDB disconnects sergiodj+buildbot
2015-12-01 14:11 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-30 22:31 [binutils-gdb] Refactor queries for hardware and software single stepping support in GDBServer sergiodj+buildbot
2015-12-01 17:25 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-11-30 22:39 [binutils-gdb] Remove support for thread events without PTRACE_EVENT_CLONE in GDBServer sergiodj+buildbot
2015-12-01 18:23 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-01  0:43 [binutils-gdb] testsuite: Range stepping and non-stop mode sergiodj+buildbot
2015-12-01  9:07 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-01  3:20 [binutils-gdb] Re: ARC port broken reloc processing sergiodj+buildbot
2015-12-01 21:27 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-01  3:43 [binutils-gdb] Invoke aout N_* macros with pointer to struct internal_exec sergiodj+buildbot
2015-12-02  0:39 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-01  5:47 [binutils-gdb] ARC port broken reloc processing sergiodj+buildbot
2015-12-01 20:26 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-01  7:49 [binutils-gdb] Trim unused params from aout adjust_sizes_and_vmas sergiodj+buildbot
2015-12-02  1:41 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-01 12:47 [binutils-gdb] Run gdb.base/disp-step-syscall.exp for aarch64-linux sergiodj+buildbot
2015-12-02  3:55 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-01 17:17 [binutils-gdb] Fix uninitialized variable warnings in remote.c sergiodj+buildbot
2015-12-02  5:10 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-01 17:41 [binutils-gdb] Avoid "operation may be undefined" warning in remote.c sergiodj+buildbot
2015-12-02  6:12 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-02  1:41 [binutils-gdb] Fix ldah being disassembled as ldaexh sergiodj+buildbot
2015-12-02  7:54 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-02  9:02 [binutils-gdb] Fix powerpc64 segfault caused by zero r_symndx relocs sergiodj+buildbot
2015-12-02  9:47 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-03 17:23 [binutils-gdb] Run gdb.base/sizeof.exp with board having gdb, noinferiorio sergiodj+buildbot
2015-12-03 18:19 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-03 19:14 [binutils-gdb] Remove duplicate arch/arm.h include in linux-arm-low.c sergiodj+buildbot
2015-12-03 20:09 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-04 11:08 [binutils-gdb] Fix failures in the GAS testsuite for the ARC architecture sergiodj+buildbot
2015-12-04 12:02 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-04 12:02 [binutils-gdb] Remove useless loop in elf.c sergiodj+buildbot
2015-12-04 13:03 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-04 17:20 [binutils-gdb] Optimize R_386_GOT32/R_386_GOT32X only if addend is 0 sergiodj+buildbot
2015-12-04 18:13 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-05  2:39 [binutils-gdb] gdbserver: set ptrace flags after creating inferiors sergiodj+buildbot
2015-12-05 13:56 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-07  1:11 [binutils-gdb] bfd: Mark sh5*-*-* and sh64*-*-* targets as obsolete sergiodj+buildbot
2015-12-07  2:45 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-07  3:17 [binutils-gdb] Reorder some power9 insns sergiodj+buildbot
2015-12-07  5:11 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-07  3:33 [binutils-gdb] PR19323 memory allocation greater than 4G sergiodj+buildbot
2015-12-07 10:06 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-07 10:29 [binutils-gdb] Add support for MSP430 F5 hardware multiply sergiodj+buildbot
2015-12-07 14:47 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-07 12:41 [binutils-gdb] Enhance the menu to select function overloads with signatures sergiodj+buildbot
2015-12-07 16:27 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-07 14:59 [binutils-gdb] Fix relaxation in RX linker when --no-keep-memory is specified sergiodj+buildbot
2015-12-07 17:52 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-07 16:13 [binutils-gdb] Support Z0 packet in AArch64 multi-arch debugging sergiodj+buildbot
2015-12-07 18:56 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-08  5:32 [binutils-gdb] rl78: Enable MULU for all ISAs sergiodj+buildbot
2015-12-08  5:57 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-08  7:01 [binutils-gdb] rl78: relaxation fixes sergiodj+buildbot
2015-12-08  8:09 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-08  9:14 [binutils-gdb] DOCO: Enhance the menu to select function overloads with signatures sergiodj+buildbot
2015-12-08  9:46 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-09 13:15 [binutils-gdb] varobj zero-padded hexadecimal format sergiodj+buildbot
2015-12-09 14:02 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
     [not found] <8eab413676a0222a863f45ff606f3db69bb7afc4@gdb-build>
2015-12-09 16:46 ` sergiodj+buildbot
2015-12-09 16:51 [binutils-gdb] gdb.base/async.exp: Handle "asynchronous execution not supported" sergiodj+buildbot
2015-12-09 18:13 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-10  0:31 [binutils-gdb] Fix GOT address computations in initial PLT entries for nios2 sergiodj+buildbot
2015-12-10  1:15 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-10 10:15 [binutils-gdb] gdb: Handle multiple base address in debug_ranges data sergiodj+buildbot
2015-12-10 10:54 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-10 14:24 [binutils-gdb] [AArch64] Fix ARMv8.1 and ARMv8.2 feature settings sergiodj+buildbot
2015-12-10 14:57 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-10 14:57 [binutils-gdb] [AArch64][PATCH 1/2] Add support for RAS instruction ESB sergiodj+buildbot
2015-12-10 16:00 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-10 15:18 [binutils-gdb] [AArch64][PATCH 2/2] Add RAS system registers sergiodj+buildbot
2015-12-10 17:05 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-10 16:00 [binutils-gdb] Remove support for thread events without PTRACE_EVENT_CLONE in GDB sergiodj+buildbot
2015-12-10 18:14 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-17  0:22 [binutils-gdb] Stop using nowarnings in gdb/testsuite/gdb.multi/ sergiodj+buildbot
2015-12-17  0:58 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-17  1:10 [binutils-gdb] [AArch64][PATCH 2/2] Support ARMv8.2 DC CVAP instruction sergiodj+buildbot
2015-12-17  3:12 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-17  1:39 [binutils-gdb] Fix regression revealed by corethreads.exp sergiodj+buildbot
2015-12-17  6:17 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-17  2:06 [binutils-gdb] [AArch64][Patch 2/5] Add Statistical Profiling Extension system registers sergiodj+buildbot
2015-12-17  9:20 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-17  2:22 [binutils-gdb] [AArch64][Patch 4/5] Support HINT aliases taking operands sergiodj+buildbot
2015-12-17 11:23 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-17  2:31 [binutils-gdb] [AArch64][Patch 5/5] Add instruction PSB CSYNC sergiodj+buildbot
2015-12-17 12:33 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-17  2:39 [binutils-gdb] Use arm_eabi_breakpoint on aarch32 sergiodj+buildbot
2015-12-17 13:27 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-17  2:47 [binutils-gdb] Understand arm breakpoints in aarch64_breakpoint_at sergiodj+buildbot
2015-12-17 14:31 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-17  2:50 [binutils-gdb] ld -r doesn't need plugin for slim lto object sergiodj+buildbot
2015-12-17  7:19 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-17  3:07 [binutils-gdb] gdb: Make lines_to_list variable static sergiodj+buildbot
2015-12-17 16:31 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-17  3:12 [binutils-gdb] gdb: Use NULL instead of 0 for pointer comparison sergiodj+buildbot
2015-12-17 17:40 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-17  3:20 [binutils-gdb] gdb: Small code restructure for list_command sergiodj+buildbot
2015-12-17 18:45 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-17  3:37 [binutils-gdb] gdb: 'list' command, tweak handling of +/- arguments sergiodj+buildbot
2015-12-17 20:50 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-17  3:46 [binutils-gdb] gdb: Add an error when 'list -' reaches the start of a file sergiodj+buildbot
2015-12-17 21:53 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-17  4:03 [binutils-gdb] Enable 2 operand form of powerpc mfcr with -many sergiodj+buildbot
2015-12-18  0:01 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-17  4:11 [binutils-gdb] gdb: Use TYPE_LENGTH macro sergiodj+buildbot
2015-12-18  1:04 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-17  4:19 [binutils-gdb] [AArch64] Fix errors rebasing the ARMv8.2 AT and system registers patch sergiodj+buildbot
2015-12-18  2:27 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-17  4:43 [binutils-gdb] [AArch64][PATCH 3/14] Support ARMv8.2 FP16 Scalar Three Same instructions sergiodj+buildbot
2015-12-18  5:41 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-17  5:14 [binutils-gdb] [AArch64][PATCH 7/14] Support FP16 Scalar Indexed Element instructions sergiodj+buildbot
2015-12-18  9:39 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-17  5:45 [binutils-gdb] [AArch64][PATCH 12/14] Support FP16 Adv.SIMD Scalar Pairwise instructions sergiodj+buildbot
2015-12-18 13:52 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-17  5:53 [binutils-gdb] [AArch64][PATCH 13/14] Support FP16 Adv.SIMD Shift By Immediate instructions sergiodj+buildbot
2015-12-18 14:48 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-17  6:02 [binutils-gdb] [AArch64][PATCH 14/14] Support FP16 Adv.SIMD Scalar Shift By Immediate instructions sergiodj+buildbot
2015-12-18 15:55 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-17  6:17 [binutils-gdb] Target remote mode fork and exec event support sergiodj+buildbot
2015-12-18 18:09 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-17  6:35 [binutils-gdb] Remove gdb.base/coremaker2.c sergiodj+buildbot
2015-12-17 15:31 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-17  7:08 [binutils-gdb] Skip tests that send ctrl-c to GDB if nointerrupts target property is set sergiodj+buildbot
2015-12-18 20:17 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-17  7:40 [binutils-gdb] Add support for RX V2 Instruction Set sergiodj+buildbot
2015-12-19  0:49 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-17  7:48 [binutils-gdb] Add support for the MRS instruction to the AArch64 simulator sergiodj+buildbot
2015-12-19  2:31 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-17  8:42 [binutils-gdb] gdb: Make test names unique in list.exp sergiodj+buildbot
2015-12-17 19:45 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-17  8:58 [binutils-gdb] Fix invalid left shift of negative value sergiodj+buildbot
2015-12-19  4:58 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-17  9:06 [binutils-gdb] bfd: don't produce corrupt COFF symbol table due to long ELF file name symbols sergiodj+buildbot
2015-12-19  5:43 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-17  9:14 [binutils-gdb] Tweak gdb.trace/ftrace.exp for aarch64 sergiodj+buildbot
2015-12-19  6:58 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-17  9:52 [binutils-gdb] gdb: Extend help text for 'list' command sergiodj+buildbot
2015-12-17 22:58 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-17 10:05 [binutils-gdb] [ARM] Add support for thumb1 pcrop relocations sergiodj+buildbot
2015-12-19  8:52 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-17 10:22 [binutils-gdb] Fix -Wno-unknown-warning support detection sergiodj+buildbot
2015-12-19 11:02 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-17 11:31 [binutils-gdb] [AArch64][PATCH 1/14] Support ARMv8.2 FP16 Adv.SIMD instructions sergiodj+buildbot
2015-12-18  3:26 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-17 11:45 [binutils-gdb] [Patch ARM] Fix build attributes for armv8-a in case of assembler files that contain no directives sergiodj+buildbot
2015-12-19 12:08 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-17 13:20 [binutils-gdb] Fix one heap buffer overflow in aarch64_push_dummy_call sergiodj+buildbot
2015-12-19 13:04 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-17 15:02 [binutils-gdb] [AArch64][PATCH 11/14] Add support for the 2H vector type sergiodj+buildbot
2015-12-18 13:08 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-17 15:14 [binutils-gdb] Remove support for LinuxThreads and vendor 2.4 kernels w/ backported NPTL sergiodj+buildbot
2015-12-19 14:31 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-17 15:38 [binutils-gdb] Fix PR threads/19354: "info threads" error with multiple inferiors sergiodj+buildbot
2015-12-19 15:27 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-17 16:37 [binutils-gdb] Target remote mode fork and exec test updates sergiodj+buildbot
2015-12-18 17:01 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-17 18:36 [binutils-gdb] Skip gdb.base/gdbinit-history.exp on remote hosts sergiodj+buildbot
2015-12-18 22:44 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-17 21:47 [binutils-gdb] [ARM] Enable CRC by default for ARMv8.1 and later sergiodj+buildbot
2015-12-19  7:53 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-18  8:59 [binutils-gdb] Fix formatting of coff-i386.c sergiodj+buildbot
2015-12-19 16:38 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-18 16:26 [binutils-gdb] Fix formatting in coff-x86_64.c sergiodj+buildbot
2015-12-19 17:42 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-18 17:01 [binutils-gdb] Share some ARM target dependent code from GDB with GDBServer sergiodj+buildbot
2015-12-19 19:48 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-18 17:27 [binutils-gdb] Refactor arm_software_single_step to use regcache sergiodj+buildbot
2015-12-19 20:39 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-18 17:35 [binutils-gdb] Share regcache function regcache_raw_read_unsigned sergiodj+buildbot
2015-12-19 21:39 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-18 17:43 [binutils-gdb] Support software single step on ARM in GDBServer sergiodj+buildbot
2015-12-19 22:43 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-18 17:51 [binutils-gdb] Enable software single stepping for while-stepping actions in GDBServer sergiodj+buildbot
2015-12-19 23:51 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-18 17:59 [binutils-gdb] Enable conditional breakpoints for targets that support software single step in GDBServer sergiodj+buildbot
2015-12-20  0:47 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-18 18:50 [binutils-gdb] Add documentation to gdb_compile sergiodj+buildbot
2015-12-20  1:45 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-18 20:40 [binutils-gdb] Cast to enum bfd_endian in arm_get_next_pcs_read_memory_unsigned_integer sergiodj+buildbot
2015-12-20  3:03 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-19  2:04 [binutils-gdb] Make prompt_for_continue call throw_quit directly sergiodj+buildbot
2015-12-20  3:53 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-19  2:13 [binutils-gdb] Reset pagination counts even when stdin is not a tty sergiodj+buildbot
2015-12-20  4:57 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
     [not found] <a4e22a5df64a46bc99f737a982c0b9d1e8a45e2b@gdb-build>
2015-12-19 10:18 ` sergiodj+buildbot
2015-12-20 15:11 [binutils-gdb] Remove HP-UX reference in testsuite/configure.ac sergiodj+buildbot
2015-12-20 15:58 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-21  3:05 [binutils-gdb] Minor reformatting fix in gdbtypes.c::create_array_type_with_stride sergiodj+buildbot
2015-12-21  3:41 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-21 14:08 [binutils-gdb] Use arm_eabi_breakpoint on aarch32 sergiodj+buildbot
2015-12-21 14:41 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-21 16:34 [binutils-gdb] Remove references to HP CC/aCC compiler from testsuite sergiodj+buildbot
2015-12-21 17:32 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-21 18:02 [binutils-gdb] Remove HP-UX references fom testsuite sergiodj+buildbot
2015-12-21 18:36 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-22  3:04 [binutils-gdb] Add an expect for running commands with CLI jump sergiodj+buildbot
2015-12-22  3:38 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-22 14:23 [binutils-gdb] Add support for ARM's NOREAD section flag sergiodj+buildbot
2015-12-22 14:54 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-22 14:38 [binutils-gdb] RXv2 support update sergiodj+buildbot
2015-12-22 15:57 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-22 15:35 [binutils-gdb] [win32] cannot automatically find executable file [...] warning at GDB startup sergiodj+buildbot
2015-12-22 17:02 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-22 15:43 [binutils-gdb] gdbserver crash in gdb/gdbserver/thread.c::thread_search_callback sergiodj+buildbot
2015-12-22 18:17 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-22 15:50 [binutils-gdb] [lynxos] gdbserver hangs when killing inferior from GDB sergiodj+buildbot
2015-12-22 19:17 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-22 16:10 [binutils-gdb] Remove HP-UX reference in foll-vfork.exp sergiodj+buildbot
2015-12-22 21:23 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-24  5:38 [binutils-gdb] [testsuite/Ada] stop using project files when building test programs sergiodj+buildbot
2015-12-24  6:11 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-24  9:44 [binutils-gdb] Consolidate Thumb-1/Thumb-2 ISA detection sergiodj+buildbot
2015-12-24 10:13 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-24  9:52 [binutils-gdb] Add assembler support for ARMv8-M Mainline sergiodj+buildbot
2015-12-24 11:13 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-24 10:35 [binutils-gdb] Add assembler support for ARMv8-M Baseline sergiodj+buildbot
2015-12-24 12:20 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-25  0:34 [binutils-gdb] sim: delete SIM_HAVE_SIMCACHE sergiodj+buildbot
2015-12-25  1:08 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-25  1:00 [binutils-gdb] sim: delete SIM_HAVE_MEM_SIZE sergiodj+buildbot
2015-12-25  3:30 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-25  1:25 [binutils-gdb] sim: delete SIM_HAVE_FLATMEM support sergiodj+buildbot
2015-12-25  5:56 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-25  1:42 [binutils-gdb] sim: enable watchpoint module everywhere sergiodj+buildbot
2015-12-25  8:39 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-25  1:50 [binutils-gdb] sim: h8300: move h8300-specific options out of common code sergiodj+buildbot
2015-12-25 10:50 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-25  2:16 [binutils-gdb] sim: delete old breakpoint code sergiodj+buildbot
2015-12-25 12:30 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-25  2:24 [binutils-gdb] sim: cris: move option install to sim_open sergiodj+buildbot
2015-12-25 14:12 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-25  3:50 [binutils-gdb] sim: mips: delete TARGET_TX3904 define sergiodj+buildbot
2015-12-25 17:03 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-25  5:41 [binutils-gdb] sim: always enable callback memory sergiodj+buildbot
2015-12-25 19:02 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-25  7:29 [binutils-gdb] sim: device_error: punt sergiodj+buildbot
2015-12-25 20:05 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-25  8:19 [binutils-gdb] sim: arm: delete unused code sergiodj+buildbot
2015-12-25 22:02 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-25 10:01 [binutils-gdb] sim: drop WITH_ENGINE define sergiodj+buildbot
2015-12-26  1:11 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-25 10:59 [binutils-gdb] sim: hw-properties: delete trace calls sergiodj+buildbot
2015-12-26  2:13 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-25 11:46 [binutils-gdb] sim: cris: clean up rvdummy a bit sergiodj+buildbot
2015-12-26  5:25 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-25 12:14 [binutils-gdb] sim: cris: migrate from WITH_DEVICES to WITH_HW sergiodj+buildbot
2015-12-26  7:09 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-25 18:20 [binutils-gdb] sim: m32r: migrate from WITH_DEVICES to WITH_HW sergiodj+buildbot
2015-12-26  8:29 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-25 18:35 [binutils-gdb] sim: frv: punt WITH_DEVICE support sergiodj+buildbot
2015-12-26  9:22 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-25 19:47 [binutils-gdb] Document that the PATTERN argument to gdb_test is optional sergiodj+buildbot
2015-12-26 10:31 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-26 12:29 [binutils-gdb] sim: standardize sim_create_inferior handling of argv a bit more sergiodj+buildbot
2015-12-26 13:09 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-26 13:41 [binutils-gdb] sim: cris: do not pass cpu when writing memory during init sergiodj+buildbot
2015-12-26 14:29 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-26 19:56 [binutils-gdb] sim: sim-core: pass down cpu to hw accesses when available sergiodj+buildbot
2015-12-26 20:36 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-26 23:35 [binutils-gdb] sim: bfin: avoid stack error under asan sergiodj+buildbot
2015-12-27  0:07 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-27  0:20 [binutils-gdb] sim: bfin: push down mmr address/size checks sergiodj+buildbot
2015-12-27  1:25 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-27  1:50 [binutils-gdb] sim: punt WITH_DEVICES & tconfig.h support sergiodj+buildbot
2015-12-27  3:12 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-27  6:09 [binutils-gdb] sim: unify sim-hload sergiodj+buildbot
2015-12-27  6:41 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-27  6:56 [binutils-gdb] sim: aarch64/msp430: fix disassembler usage sergiodj+buildbot
2015-12-27  7:39 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-27 20:41 [binutils-gdb] Correct nios2 _gp address computation sergiodj+buildbot
2015-12-27 21:14 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-30  8:41 [binutils-gdb] sim: h8300: drop unused inst.h sergiodj+buildbot
2015-12-30  9:11 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-30  9:52 [binutils-gdb] sim: simplify STATE_MY_NAME setup sergiodj+buildbot
2015-12-30 12:10 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-30 10:32 [binutils-gdb] sim: h8300: move default endian/alignment to configure sergiodj+buildbot
2015-12-30 13:12 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-30 10:40 [binutils-gdb] sim: h8300: switch to common sim-resume sergiodj+buildbot
2015-12-30 14:16 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-30 11:14 [binutils-gdb] sim: h8300: simplify h8300_reg_{fetch,store} funcs sergiodj+buildbot
2015-12-30 15:11 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-30 11:24 [binutils-gdb] sim: h8300: inline sim_state_initialize sergiodj+buildbot
2015-12-30 16:10 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-31  4:59 [binutils-gdb] sim: m68hc11: fix default endian sergiodj+buildbot
2015-12-31  5:30 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2015-12-31 22:08 [binutils-gdb] opcodes/arc: Support dmb instruction with no operands sergiodj+buildbot
2015-12-31 22:40 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-01  4:32 [binutils-gdb] Rotate the GDB ChangeLog sergiodj+buildbot
2016-01-01  5:01 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-01  4:41 [binutils-gdb] update copyright year printed by GDB, GDBserver and gdbreplay sergiodj+buildbot
2016-01-01  6:01 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-01  4:56 [binutils-gdb] GDB copyright headers update after running GDB's copyright.py script sergiodj+buildbot
2016-01-01  7:01 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-01 12:44 [binutils-gdb] Copyright update for binutils sergiodj+buildbot
2016-01-01 13:14 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-02  8:58 [binutils-gdb] gdb: ppc: drop unnecessary sim file check sergiodj+buildbot
2016-01-02 10:18 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-02 15:38 [binutils-gdb] sim: delete dead current_state globals sergiodj+buildbot
2016-01-02 16:06 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-02 16:02 [binutils-gdb] sim: iq2000/m32r/lm32/sh64: delete dead option code sergiodj+buildbot
2016-01-02 17:05 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-02 19:11 [binutils-gdb] sim: cris: use standard output helpers sergiodj+buildbot
2016-01-02 19:39 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-03  5:29 [binutils-gdb] sim: convert to bfd_endian sergiodj+buildbot
2016-01-03  5:57 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-03  6:05 [binutils-gdb] sim: drop host endian configure option sergiodj+buildbot
2016-01-03  6:58 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-03  9:17 [binutils-gdb] sim: nrun: use lbasename sergiodj+buildbot
2016-01-03  9:45 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-03  9:56 [binutils-gdb] sim: clean up some more device detritus sergiodj+buildbot
2016-01-03 11:43 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-04  8:52 [binutils-gdb] btrace: do not return out of TRY/CATCH sergiodj+buildbot
2016-01-04  9:21 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-04 10:17 [binutils-gdb] sim: d10v: gut endian logic sergiodj+buildbot
2016-01-04 10:45 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-04 10:45 [binutils-gdb] sim: punt x86-specific bswap logic sergiodj+buildbot
2016-01-04 11:45 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-04 11:04 [binutils-gdb] sim: parse_args: polish getopt error message sergiodj+buildbot
2016-01-04 12:44 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-05 20:31 [binutils-gdb] sim: msp430: switch to common disassembler tracing sergiodj+buildbot
2016-01-05 21:16 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-05 20:39 [binutils-gdb] sim: bfin: add support disasm tracing sergiodj+buildbot
2016-01-05 22:15 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-05 21:02 [binutils-gdb] sim: aarch64: switch to common disassembler tracing sergiodj+buildbot
2016-01-05 23:14 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-05 22:13 [binutils-gdb] gdb: score: drop sim file check sergiodj+buildbot
2016-01-06  1:15 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-05 22:21 [binutils-gdb] libiberty: fix warnings about left shifting a negative value sergiodj+buildbot
2016-01-06  2:34 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-05 22:29 [binutils-gdb] libiberty: Tweak the documentation of libiberty's xcrc32 function sergiodj+buildbot
2016-01-06  3:33 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-05 23:03 [binutils-gdb] libiberty: {count, dup, write}argv: constify argv input slightly sergiodj+buildbot
2016-01-06  5:33 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-05 23:23 [binutils-gdb] libiberty: dupargv: rewrite to use xstrdup sergiodj+buildbot
2016-01-06  4:33 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-06  4:40 [binutils-gdb] gdb: change version stamp to git sergiodj+buildbot
2016-01-06  6:32 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-06  5:52 [binutils-gdb] Change copyright owner to FSF in sim/testsuite/sim/mips/hilo-hazard-4.s sergiodj+buildbot
2016-01-06  7:31 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-06 11:46 [binutils-gdb] Fix gdb.python/py-infthread.exp test message typo sergiodj+buildbot
2016-01-06 12:15 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-06 15:10 [binutils-gdb] [ARM/AArch64] Fix -Werror=unused-const-variable warnings in GDBserver sergiodj+buildbot
2016-01-06 15:57 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-06 15:34 [binutils-gdb] Make {arm,thumb}_get_next_pcs_raw static sergiodj+buildbot
2016-01-06 16:59 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-06 18:52 [binutils-gdb] MIPS/include: opcode/mips.h: Add a summary of MIPS16 operand codes sergiodj+buildbot
2016-01-06 19:21 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-07  2:58 [binutils-gdb] sim: sim_{create_inferior, open, parse_args}: constify argv/env slightly sergiodj+buildbot
2016-01-07  3:27 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-07 19:37 [binutils-gdb] MIPS: Complete `status' to `err' renaming in `mips_breakpoint_from_pc' sergiodj+buildbot
2016-01-07 20:06 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-08  9:58 [binutils-gdb] [ARM] PR ld/19368: Add missing relocation type class for R_ARM_IRELATIVE sergiodj+buildbot
2016-01-08 10:27 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-08 10:52 [binutils-gdb] m68k: fix constraints of move.[bw] for ISA_B/C sergiodj+buildbot
2016-01-08 11:28 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-08 11:16 [binutils-gdb] Check input interrupt first when reading packet sergiodj+buildbot
2016-01-08 12:30 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-08 11:25 [binutils-gdb] Change SIGINT handler for extension languages only when target terminal is ours sergiodj+buildbot
2016-01-08 13:32 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-08 15:34 [binutils-gdb] perf testsuite: python 3 fixes sergiodj+buildbot
2016-01-08 16:03 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-08 19:16 [binutils-gdb] Fix gdb.multi/base.exp testsuite regression sergiodj+buildbot
2016-01-08 19:45 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-09  9:01 [binutils-gdb] sim: drop common/cconfig.h in favor of a single config.h sergiodj+buildbot
2016-01-09  9:29 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-09  9:24 [binutils-gdb] sim: stop configuring common subdir sergiodj+buildbot
2016-01-09 10:29 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-10  8:17 [binutils-gdb] sim: drop --enable-sim-cflags option sergiodj+buildbot
2016-01-10  8:46 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-10  8:33 [binutils-gdb] sim: drop --enable-sim-{regparm,stdcall} options sergiodj+buildbot
2016-01-10 10:02 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-10  9:12 [binutils-gdb] sim: drop targ-vals.def->nltvals.def indirection sergiodj+buildbot
2016-01-10 13:01 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-10 22:20 [binutils-gdb] sim: allow the assert configure option everywhere sergiodj+buildbot
2016-01-10 22:51 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-10 22:28 [binutils-gdb] sim: allow the environment configure option everywhere sergiodj+buildbot
2016-01-10 23:53 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-10 23:15 [binutils-gdb] sim: drop unused SIM_AC_OPTION_PACKAGES sergiodj+buildbot
2016-01-11  0:56 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-11  0:08 [binutils-gdb] sim: move many common settings from CPPFLAGS to config.h sergiodj+buildbot
2016-01-11  2:23 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-11 11:18 [binutils-gdb] Import changes made to files shared with the FSF GCC project sergiodj+buildbot
2016-01-11 11:47 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-11 18:06 [binutils-gdb] Delete opcodes that have been removed from ISA 3.0 sergiodj+buildbot
2016-01-11 18:37 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-11 19:13 [binutils-gdb] gdb: split out warnings helpers sergiodj+buildbot
2016-01-11 19:50 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-11 21:16 [binutils-gdb] testsuite: Fix false FAILs on too long base directory sergiodj+buildbot
2016-01-11 21:53 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-11 21:31 [binutils-gdb] testsuite: i386 regression for funcargs.exp sergiodj+buildbot
2016-01-11 23:53 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-12  1:37 [binutils-gdb] Reapply: List inferiors/threads/pspaces in ascending order sergiodj+buildbot
2016-01-12  2:39 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-12  6:46 [binutils-gdb] sim: mips: workaround 32-bit addr sign extensions sergiodj+buildbot
2016-01-12  7:22 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-12 12:01 [binutils-gdb] Hurd: Make gdb/reply_mig_hack.awk script compatible to "mawk" sergiodj+buildbot
2016-01-12 12:39 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-12 13:13 [binutils-gdb] Test gdb.base/random-signal.exp with "attach" sergiodj+buildbot
2016-01-12 13:49 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-12 15:09 [binutils-gdb] Remove trademark acknowledgements throughout sergiodj+buildbot
2016-01-12 15:46 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-12 15:22 [binutils-gdb] Change function signature passed to clone sergiodj+buildbot
2016-01-12 16:46 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-12 15:44 [binutils-gdb] gdbserver: fix various warnings sergiodj+buildbot
2016-01-12 17:47 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-12 15:45 [binutils-gdb] gdbserver: use the new gdb warning helpers sergiodj+buildbot
2016-01-12 18:47 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-12 16:34 [binutils-gdb] Fix invalid conversion from void * to gdb_byte * sergiodj+buildbot
2016-01-12 19:47 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-12 16:37 [binutils-gdb] Sync top-level Makefile.def with GCC sergiodj+buildbot
2016-01-12 20:48 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-12 16:46 [binutils-gdb] [ARM] Support ARMv8.2 RAS extension sergiodj+buildbot
2016-01-12 22:49 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-12 16:49 [binutils-gdb] Sync top-level btool.m4 with GCC sergiodj+buildbot
2016-01-12 23:50 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-12 20:34 [binutils-gdb] Implement 'catch syscall' for gdbserver sergiodj+buildbot
2016-01-13  0:53 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-13 11:35 [binutils-gdb] Add a new $_inferior convenience variable sergiodj+buildbot
2016-01-13 12:36 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-13 11:36 [binutils-gdb] Add Python InferiorThread.inferior attribute sergiodj+buildbot
2016-01-13 13:37 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-13 11:39 [binutils-gdb] Per-inferior/Inferior-qualified thread IDs sergiodj+buildbot
2016-01-13 15:37 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-13 11:40 [binutils-gdb] Add Python InferiorThread.global_num attribute sergiodj+buildbot
2016-01-13 16:39 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-13 11:41 [binutils-gdb] Implement "info threads -gid" sergiodj+buildbot
2016-01-13 17:39 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-13 11:42 [binutils-gdb] Add $_gthread convenience variable sergiodj+buildbot
2016-01-13 18:41 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-13 18:04 [binutils-gdb] MAINTAINERS: Add Andreas Arnez as s390 target maintainer sergiodj+buildbot
2016-01-13 20:43 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-14 11:03 [binutils-gdb] [AArch64] Fix missing architecture checks for ARMv8.2 system registers sergiodj+buildbot
2016-01-14 11:40 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-14 12:30 [binutils-gdb] Fix C++ build error by casting void * sergiodj+buildbot
2016-01-14 13:06 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-14 14:57 [binutils-gdb] [ARM] Remove field syscall_next_pc in struct gdbarch_tdep sergiodj+buildbot
2016-01-14 15:33 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-14 16:27 [binutils-gdb] Fix display of RL78 MOVW instructions that use the stack pointer sergiodj+buildbot
2016-01-14 17:03 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-15 21:59 [binutils-gdb] Fix "thread apply $conv_var" and misc other related problems sergiodj+buildbot
2016-01-15 22:30 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-15 22:25 [binutils-gdb] Star wildcard ranges (e.g., "info thread 2.*") sergiodj+buildbot
2016-01-15 23:33 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-15 22:55 [binutils-gdb] Fix phony_iconv wide character support sergiodj+buildbot
2016-01-16  0:36 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-17  3:05 [binutils-gdb] Regen configure sergiodj+buildbot
2016-01-17  3:42 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-17  5:43 [binutils-gdb] minor reformatting in sim/common/sim-fpu.c sergiodj+buildbot
2016-01-17  6:14 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-17  6:14 [binutils-gdb] Minor comment fixes in sim/common/sim-fpu.c sergiodj+buildbot
2016-01-17  7:14 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-17  6:17 [binutils-gdb] fix gdb version parsing in src-release.sh sergiodj+buildbot
2016-01-17  8:14 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-17  7:04 [binutils-gdb] GDB SIGSEGV opening a Fortran program compiled with ifort sergiodj+buildbot
2016-01-17  9:14 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-18 11:57 [binutils-gdb] Fix gdbserver build failure on targets without fork sergiodj+buildbot
2016-01-18 12:31 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-18 12:05 [binutils-gdb] Provide AC_PROG_LEX that copes with LEX=missing from top-level sergiodj+buildbot
2016-01-18 13:32 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-18 14:40 [binutils-gdb] [testsuite] @progbits -> %progbits sergiodj+buildbot
2016-01-18 15:10 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-18 15:11 [binutils-gdb] Replace some $ARCH_{get, set}_pc with linux_{get, set}_pc_32bit sergiodj+buildbot
2016-01-18 16:10 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-18 15:19 [binutils-gdb] Replace some $ARCH_{get, set}_pc with linux_{get, set}_pc_64bit sergiodj+buildbot
2016-01-18 17:10 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-18 16:03 [binutils-gdb] Fix PR threads/19422 - show which thread caused stop sergiodj+buildbot
2016-01-18 18:13 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-18 16:11 [binutils-gdb] Use a 32-bit value to hold the section number in the internal COFF symbol structure sergiodj+buildbot
2016-01-18 19:17 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-18 17:08 [binutils-gdb] testsuite: Remove unused global references in gdb_test sergiodj+buildbot
2016-01-18 20:17 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-18 21:22 [binutils-gdb] MIPS: Fix microMIPS instruction size determination sergiodj+buildbot
2016-01-18 21:51 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-18 22:01 [binutils-gdb] MIPS: Only build microMIPS specific simulator functions if microMIPS support is required sergiodj+buildbot
2016-01-18 22:52 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-18 22:31 [binutils-gdb] MIPS: Remove remnants of 48-bit microMIPS instruction support sergiodj+buildbot
2016-01-18 23:53 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-19 12:38 [binutils-gdb] Limit breakpoint re-set to the current program space sergiodj+buildbot
2016-01-19 13:50 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
     [not found] <bd0a71fa16f668341a9361c695bc3ca44d27b322@gdb-build>
2016-01-19 12:49 ` sergiodj+buildbot
2016-01-19 15:37 [binutils-gdb] Add PIC and TLS support to the ARC target sergiodj+buildbot
2016-01-19 16:06 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-19 15:50 [binutils-gdb] Fix detection of "r_fs" and "r_gs" on FreeBSD sergiodj+buildbot
2016-01-19 17:07 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-19 15:58 [binutils-gdb] testsuite: Make check-parallel return non-zero if a test failed sergiodj+buildbot
2016-01-19 18:08 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-19 16:07 [binutils-gdb] testsuite: Add --status to runtest invocation sergiodj+buildbot
2016-01-19 19:08 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-19 16:35 [binutils-gdb] testsuite: Factor out --status in DO_RUNTEST sergiodj+buildbot
2016-01-19 20:09 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-19 17:09 [binutils-gdb] Add support to readelf for reading FreeBSD ELF core notes sergiodj+buildbot
2016-01-19 22:10 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-19 17:18 [binutils-gdb] Add a pseudosection for the NT_FREEBSD_THRMISC note sergiodj+buildbot
2016-01-19 23:10 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-19 17:26 [binutils-gdb] Add support for extracting thread names from cores sergiodj+buildbot
2016-01-20  0:12 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-19 17:34 [binutils-gdb] Display per-thread information for threads in FreeBSD cores sergiodj+buildbot
2016-01-20  1:14 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-19 18:00 [binutils-gdb] Dump register notes for each thread when generating a FreeBSD core sergiodj+buildbot
2016-01-20  8:04 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-20  4:14 [binutils-gdb] minor reformatting in printcmd.c::print_scalar_formatted sergiodj+buildbot
2016-01-20 10:46 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-20 13:05 [binutils-gdb] Add support for an ARM specific 'y' section attribute flag to mark the section as NOREAD sergiodj+buildbot
2016-01-20 13:43 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-20 14:43 [binutils-gdb] [AArch64] Reject invalid immediate operands to MSR UAO sergiodj+buildbot
2016-01-20 15:19 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-20 17:40 [binutils-gdb] Fix missing IPA lib in tspeed.exp in some configurations sergiodj+buildbot
2016-01-20 18:23 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-20 18:53 [binutils-gdb] gnu_vector.exp: Respect `should_kfail' for PR 8549 sergiodj+buildbot
2016-01-20 19:37 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-20 19:03 [binutils-gdb] Fix sorting of enum values in FlagEnumerationPrinter sergiodj+buildbot
2016-01-20 20:53 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-21  8:17 [binutils-gdb] Detect the arm/thumb mode of code SIGRETURN or RT_SIGRETURN returns to sergiodj+buildbot
2016-01-21  8:48 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-21  9:57 [binutils-gdb] Convert macros in elf-linux-core.h to inline functions sergiodj+buildbot
2016-01-21 12:18 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-21 10:09 [binutils-gdb] Rename elf-linux-psinfo.h to elf-linux-core.h sergiodj+buildbot
2016-01-21 11:15 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-21 10:14 [binutils-gdb] [AArch64] Relax long branch veneer insertion for non STT_FUNC symbol sergiodj+buildbot
2016-01-21 13:19 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-21 10:33 [binutils-gdb] Fix regression introduced in "break *<EXPR>" by explicit location patches sergiodj+buildbot
2016-01-21 14:19 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-21 11:03 [binutils-gdb] Fix unexpected failures in the linker testsuite for ARM VxWorks targets sergiodj+buildbot
2016-01-21 15:21 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-21 11:45 [binutils-gdb] gdb: Respect CXXFLAGS when building with C++ compiler sergiodj+buildbot
2016-01-21 16:25 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-21 14:04 [binutils-gdb] Fix compile time errors building ARC target on a 32-bit host sergiodj+buildbot
2016-01-21 18:31 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
     [not found] <f906b857015513af81f94db8e11b1e334c767def@gdb-build>
2016-01-21 19:35 ` sergiodj+buildbot
2016-01-22  1:15 [binutils-gdb] * breakpoint.c (init_breakpoint_sal): Add comment sergiodj+buildbot
2016-01-22  3:37 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-22  9:39 [binutils-gdb] [testsuite] Unbuffer the output in gdb.base/multi-forks.c sergiodj+buildbot
2016-01-22 10:49 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
     [not found] <99e8eb11cfcdde8cba6755ed4613c3cb079dfaa4@gdb-build>
2016-01-22 14:49 ` sergiodj+buildbot
2016-01-22 17:04 [binutils-gdb] Reword the string description of native FreeBSD ptids sergiodj+buildbot
2016-01-22 17:35 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-22 20:50 [binutils-gdb] testsuite: Fix PR threads/19422 regression + Guile regression sergiodj+buildbot
2016-01-22 21:21 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-22 21:00 [binutils-gdb] testsuite: gdb.gdb/selftest.exp: Drop expected Thread number sergiodj+buildbot
2016-01-22 22:26 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
     [not found] <cc5fd9abe4980e48e2cc27b0225f3c6ba7c0756b@gdb-build>
2016-01-23 12:04 ` sergiodj+buildbot
     [not found] <dc29a1ce6a25233e608f90511e67af3c18e19a98@gdb-build>
2016-01-23 14:37 ` sergiodj+buildbot
2016-01-24  1:16 [binutils-gdb] MIPS/BFD: Correct register index calculation in BZ16_REG sergiodj+buildbot
2016-01-24  2:02 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-24  1:27 [binutils-gdb] MIPS/BFD: Simplify register index calculation in BZ16_REG_FIELD sergiodj+buildbot
2016-01-24  4:51 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-25  9:41 [binutils-gdb] Fix memory corruption on Mach-O systems by suppressing a memory tidy up sergiodj+buildbot
2016-01-25  9:46 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-25  9:54 [binutils-gdb] Add missing end-of-comment marker to previous delta. (Doh!) sergiodj+buildbot
2016-01-25 10:26 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
     [not found] <45f3854667c659ab053f51f96e1923f36e6e20ba@gdb-build>
2016-01-25 13:02 ` sergiodj+buildbot
2016-01-25 13:32 [binutils-gdb] Move foreach_with_prefix to lib/gdb.exp sergiodj+buildbot
2016-01-25 14:06 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-25 13:48 [binutils-gdb] Fix PR 19461: strange "info thread" behavior in non-stop sergiodj+buildbot
2016-01-25 16:14 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-25 16:18 [binutils-gdb] ARC/BFD: Fix a build error from `index' shadowing a global declaration sergiodj+buildbot
2016-01-25 18:24 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-25 16:27 [binutils-gdb] Remove new_thread_notify and dead_thread_notify sergiodj+buildbot
2016-01-25 19:29 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
     [not found] <a579cd9aa8c57c8a54833f26452a1afef38e5d20@gdb-build>
2016-01-25 23:48 ` sergiodj+buildbot
2016-01-26 14:03 [binutils-gdb] [GDBserver] Check input interrupt after reading in a packet sergiodj+buildbot
2016-01-26 14:36 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-26 14:13 [binutils-gdb] [GDBserver] Block and unblock SIGIO sergiodj+buildbot
2016-01-26 15:42 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-26 14:40 [binutils-gdb] [GDBserver] Use regcache_read_pc in install_software_single_step_breakpoints sergiodj+buildbot
2016-01-26 16:47 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-26 14:48 [binutils-gdb] Remove argument pc in get_next_pcs sergiodj+buildbot
2016-01-26 17:57 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-26 21:41 [binutils-gdb] Fix function comments sergiodj+buildbot
2016-01-26 22:13 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-27 19:48 [binutils-gdb] rx: Treat scalars larger than 8 bytes as aggregates in rx_push_dummy_call sergiodj+buildbot
2016-01-27 20:25 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-28 14:27 [binutils-gdb] Fix GDB crash in dprintf.exp sergiodj+buildbot
2016-01-28 15:00 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-28 14:39 [binutils-gdb] [testsuite] Fix tiemout fail in gdb.fortran/vla-value.exp sergiodj+buildbot
2016-01-28 16:06 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-28 19:00 [binutils-gdb] Add rawmemchr to imported gnulib modules sergiodj+buildbot
2016-01-28 19:32 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-28 21:00 [binutils-gdb] Sync libiberty with GCC sergiodj+buildbot
2016-01-28 21:31 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-28 21:41 [binutils-gdb] Set BFD_DECOMPRESS to decompress debug sections sergiodj+buildbot
2016-01-28 23:44 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-29 20:45 [binutils-gdb] Fix two misleading indentation warnings sergiodj+buildbot
2016-01-29 21:22 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-31  0:17 [binutils-gdb] Check reloc against IFUNC symbol only with dynamic symbols sergiodj+buildbot
2016-01-31  0:57 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-01-31 20:38 [binutils-gdb] Fix /usr/bin/ld: final link failed: File truncated error on hppa sergiodj+buildbot
2016-01-31 21:13 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-01  3:01 [binutils-gdb] elf64-s390.c: Fix -Werror=misleading-indentation sergiodj+buildbot
2016-02-01  3:36 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-01  3:36 [binutils-gdb] Fix some comments in varobj.{c,h} sergiodj+buildbot
2016-02-01  4:44 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-01 10:48 [binutils-gdb] Fix NetBSD build with BSD and GNU make(1) sergiodj+buildbot
2016-02-01 11:21 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-01 11:43 [binutils-gdb] x86 synthetic plt symbols sergiodj+buildbot
2016-02-01 13:30 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-01 13:53 [binutils-gdb] Add support for importing data from ILF images sergiodj+buildbot
2016-02-01 14:35 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-01 18:23 [binutils-gdb] gdb: New set/show max-value-size command sergiodj+buildbot
2016-02-01 18:54 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-01 18:40 [binutils-gdb] gdb: Guard against undefined behaviour in mi-vla-fortran.exp sergiodj+buildbot
2016-02-01 20:01 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-01 19:35 [binutils-gdb] Test gdb.threads/forking-threads-plus-breakpoint.exp with displaced stepping off sergiodj+buildbot
2016-02-01 21:09 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-01 23:33 [binutils-gdb] gdb.base/skip.exp: Clean up multiple references to same test name sergiodj+buildbot
2016-02-02  0:10 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-01 23:59 [binutils-gdb] Don't add DT_NEEDED for unmatched symbol sergiodj+buildbot
2016-02-02  1:18 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-02 10:56 [binutils-gdb] Merge gdb and gdbserver implementations for siginfo sergiodj+buildbot
2016-02-02 11:30 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-02 11:05 [binutils-gdb] Preparation for new siginfo on Linux sergiodj+buildbot
2016-02-02 12:34 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-02 11:21 [binutils-gdb] Add bound related fields to the siginfo structure sergiodj+buildbot
2016-02-02 14:42 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-02 11:38 [binutils-gdb] epiphany/disassembler: Improve alignment of output sergiodj+buildbot
2016-02-02 16:51 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-02 12:04 [binutils-gdb] opcodes/cgen: Rework calculation of shift when inserting fields sergiodj+buildbot
2016-02-02 17:57 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-02 12:26 [binutils-gdb] Adaptation of siginfo fixup for the new bnd fields sergiodj+buildbot
2016-02-02 15:47 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-02 12:31 [binutils-gdb] Clear HAS_RELOC if there are no relocations sergiodj+buildbot
2016-02-02 19:02 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-02 13:44 [binutils-gdb] PowerPC64 ELFv2 entry code sergiodj+buildbot
2016-02-02 20:07 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-02 16:34 [binutils-gdb] Store estimated istrances in compressed_size sergiodj+buildbot
2016-02-02 21:12 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-02 21:21 [binutils-gdb] Fix typos in bfd/ChangeLog and bfd/elf64-x86-64.c sergiodj+buildbot
2016-02-02 22:16 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-02 21:51 [binutils-gdb] ui-out.c: Remove unused enum sergiodj+buildbot
2016-02-02 23:21 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-03 14:16 [binutils-gdb] Fix "PowerPC64 ELFv2 entry code" for big-endian sergiodj+buildbot
2016-02-03 14:46 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-03 22:03 [binutils-gdb] MAINTAINERS: Add Thiemo Seufer back, as a past maintainer sergiodj+buildbot
2016-02-03 22:34 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-04 10:06 [binutils-gdb] Fix the encoding of the MSP430's RRUX instruction sergiodj+buildbot
2016-02-04 10:38 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-04 15:22 [binutils-gdb] waiting_for_stop_reply around remote_fileio_request sergiodj+buildbot
2016-02-04 15:52 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-04 15:57 [binutils-gdb] [testsuite] Remove BASEDIR sergiodj+buildbot
2016-02-04 16:57 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-04 16:40 [binutils-gdb] Prevent possible undefined behaviour computing the size of the scache by usingunsigned integers instead of signed integers sergiodj+buildbot
2016-02-04 18:02 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-05 10:11 [binutils-gdb] Change the default architecture value for ARC bfds so that they have the lowest possible value, and hence can be merged with other ARC binaries wihtout changing their architecture value sergiodj+buildbot
2016-02-05 10:43 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-06  1:39 [binutils-gdb] sim: mips: fix prog_bfd usage sergiodj+buildbot
2016-02-06  3:21 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-07 14:56 [binutils-gdb] varobj: Cleanup dead code sergiodj+buildbot
2016-02-07 15:28 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-08 18:12 [binutils-gdb] remote.c: Cleanup unused variables sergiodj+buildbot
2016-02-08 18:45 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-08 19:12 [binutils-gdb] Fix in-tree, parallel running of Ada tests sergiodj+buildbot
2016-02-08 19:55 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-08 19:40 [binutils-gdb] Always organize test artifacts in a directory hierarchy sergiodj+buildbot
2016-02-08 21:03 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-09  5:24 [binutils-gdb] Fix macro redefinition error on Solaris sergiodj+buildbot
2016-02-09  5:57 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-09 10:38 [binutils-gdb] Fix build breakage sergiodj+buildbot
2016-02-09 11:50 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-09 10:48 [binutils-gdb] Revert "Add a more helpful warning message to explain why some AArch64 relocations can overflow." sergiodj+buildbot
2016-02-09 12:58 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-09 10:57 [binutils-gdb] Revert "Fix build breakage" sergiodj+buildbot
2016-02-09 14:06 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-09 11:06 [binutils-gdb] Add a more helpful warning message to explain why some AArch64 relocations can overflow sergiodj+buildbot
2016-02-09 15:14 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-09 12:41 [binutils-gdb] Fix PR19548: Breakpoint re-set inserts breakpoints when it shouldn't sergiodj+buildbot
2016-02-09 17:37 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
     [not found] <8adce0342f5f50aba0154fc56ca59df45b219738@gdb-build>
2016-02-09 16:26 ` sergiodj+buildbot
2016-02-09 22:48 [binutils-gdb] Refactor string_to_event_location for legacy linespec support sergiodj+buildbot
2016-02-09 23:23 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-09 22:56 [binutils-gdb] python/19506 -- gdb.Breakpoint address location regression sergiodj+buildbot
2016-02-10  0:34 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-09 23:05 [binutils-gdb] Use string_to_event_location_basic in guile sergiodj+buildbot
2016-02-10  1:45 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-10  0:25 [binutils-gdb] breakpoints/19546: Fix crash after updating breakpoints sergiodj+buildbot
2016-02-10  5:32 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-10  3:58 [binutils-gdb] Bump version to 7.11.50.DATE-git sergiodj+buildbot
2016-02-10 10:30 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-10  4:06 [binutils-gdb] Update NEWS post GDB 7.11 branch creation sergiodj+buildbot
2016-02-10 11:38 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-10 11:05 [binutils-gdb] Sync top level files with gcc sergiodj+buildbot
2016-02-10 17:19 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-10 11:38 [binutils-gdb] Correct assertion in NIOS2 linker to allow signed 16-buit immediate values sergiodj+buildbot
2016-02-10 18:28 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-10 15:50 [binutils-gdb] arm-tdep.c: Fix typo sergiodj+buildbot
2016-02-11  0:16 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-10 17:06 [binutils-gdb] Clear *VAL in regcache_raw_read_unsigned sergiodj+buildbot
2016-02-11  3:29 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
     [not found] <473b99e5721ad623cc5826e03a73e2cf6cef4eb5@gdb-build>
2016-02-10 20:47 ` sergiodj+buildbot
     [not found] <e909d859f5635d66e79fef467da70d6090bfae1b@gdb-build>
2016-02-10 21:59 ` sergiodj+buildbot
2016-02-11  3:48 [binutils-gdb] Mask off the least significant bit in GOT offset sergiodj+buildbot
2016-02-11  9:51 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
     [not found] <18d3cec54e1b4fce278dba436484846f8048d7d6@gdb-build>
2016-02-11  5:49 ` sergiodj+buildbot
     [not found] <5ac87a997fca849c654fffdf1c3e1991ea3f81d1@gdb-build>
2016-02-11  7:51 ` sergiodj+buildbot
2016-02-11 13:31 [binutils-gdb] Use the target architecture when encoding tracepoint actions sergiodj+buildbot
2016-02-11 14:04 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-11 18:30 [binutils-gdb] arm-tdep.c: Change type of insn parameters sergiodj+buildbot
2016-02-11 19:11 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-11 19:25 [binutils-gdb] arm-tdep.c: Remove unused arm_displaced_step_copy_insn sergiodj+buildbot
2016-02-11 20:20 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-11 19:37 [binutils-gdb] arm-tdep.c: Remove unused variables sergiodj+buildbot
2016-02-11 21:28 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-11 20:04 [binutils-gdb] Support 'make check-parallel' in gdb's build dir sergiodj+buildbot
2016-02-11 22:36 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-11 20:15 [binutils-gdb] Add missing quotes to gdb/testsuite/README sergiodj+buildbot
2016-02-11 23:46 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
     [not found] <7cae9051edc2e3b11b5c79c08edfb91ee7f4e2e4@gdb-build>
2016-02-12  0:54 ` sergiodj+buildbot
2016-02-12  9:01 [binutils-gdb] frame: add skip_tailcall_frames sergiodj+buildbot
2016-02-12  9:34 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-12  9:10 [binutils-gdb] stack: check frame_unwind_caller_id sergiodj+buildbot
2016-02-12 10:43 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-12  9:19 [binutils-gdb] btrace, frame: fix crash in get_frame_type sergiodj+buildbot
2016-02-12 11:52 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
     [not found] <d21b5f15d92bc1902b9e57198f67550326c887d7@gdb-build>
2016-02-12 13:01 ` sergiodj+buildbot
     [not found] <020ecd38e74681cb14987baf1a4d3c3ee3be0006@gdb-build>
2016-02-12 14:09 ` sergiodj+buildbot
2016-02-12 16:11 [binutils-gdb] [ARM] Fixup PC in software single step sergiodj+buildbot
2016-02-12 16:43 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-12 16:22 [binutils-gdb] [ARM] Software single step cross kernel helpers sergiodj+buildbot
2016-02-12 17:53 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-12 16:32 [binutils-gdb] [gdbserver, aarch64] Use linux_{set, get}_pc_{64, 32}bit sergiodj+buildbot
2016-02-12 19:02 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-12 19:08 [binutils-gdb] i386-biarch-core.exp: Use standard_output_file sergiodj+buildbot
2016-02-12 20:11 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
     [not found] <e44e00ffffe358d91df0ec4a11563eef0c14beb4@gdb-build>
2016-02-12 21:37 ` sergiodj+buildbot
2016-02-14  8:25 [binutils-gdb] testsuite regression: gdb.fortran/vla-value-sub.exp gdb.fortran/vla-value-sub-finish.exp sergiodj+buildbot
2016-02-14  8:59 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-14  8:44 [binutils-gdb] testsuite: Fix false Fortran regressions with recent gcc sergiodj+buildbot
2016-02-14 11:17 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-15 10:19 [binutils-gdb] Don't print 0x for core_addr_to_string_nz sergiodj+buildbot
2016-02-15 10:52 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-15 11:25 [binutils-gdb] Enhance GAS's .section directive so that it can take numeric values for the flags and type fields. (ELF only) sergiodj+buildbot
2016-02-15 12:03 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-15 18:15 [binutils-gdb] Fix more testcases with standard_output_file sergiodj+buildbot
2016-02-16  9:57 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-15 19:08 [binutils-gdb] Add missing gdb.arch/i386-prologue.c prototypes sergiodj+buildbot
2016-02-16 12:18 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-16  0:16 [binutils-gdb] Add parentheses to prevent truncated addresses sergiodj+buildbot
2016-02-16 13:27 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-16 13:59 [binutils-gdb] Remove PC from syscall_next_pc sergiodj+buildbot
2016-02-16 15:43 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-16 14:26 [binutils-gdb] Fix cleanup in arm_linux_software_single_step sergiodj+buildbot
2016-02-16 16:51 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-16 15:12 [binutils-gdb] testsuite: Fix save-trace.exp writing outside standard output directory sergiodj+buildbot
2016-02-16 19:12 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-16 17:09 [binutils-gdb] PR remote/19496, internal err forking-threads-plus-bkpt sergiodj+buildbot
2016-02-16 21:33 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-16 20:52 [binutils-gdb] Whitespace cleanup for skip testcase sergiodj+buildbot
2016-02-16 23:51 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
     [not found] <b00b61e1fd95b778ec85bf314baddd1be9040d25@gdb-build>
2016-02-17 10:34 ` sergiodj+buildbot
2016-02-17 17:04 [binutils-gdb] Add missing cleanup in exec_file_locate_attach sergiodj+buildbot
2016-02-17 17:37 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-18 11:25 [binutils-gdb] Always create dynamic sections for -E/--dynamic-list sergiodj+buildbot
2016-02-18 11:57 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-18 12:18 [binutils-gdb] Set breakpoint condition-evaluation in forking-threads-plus-breakpoint.exp sergiodj+buildbot
2016-02-18 13:06 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-18 13:17 [binutils-gdb] Remove setup_kfail server/13796 in disp-step-syscall.exp sergiodj+buildbot
2016-02-18 14:14 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-18 16:46 [binutils-gdb] Intel MPX bound violation handling sergiodj+buildbot
2016-02-18 18:23 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
     [not found] <5f034a78b986d30a90030b2409c61a8660b9b48c@gdb-build>
2016-02-18 17:07 ` sergiodj+buildbot
     [not found] <f79a3bae8725dfe0e11b04ddfc6e6bc8f23e4e4e@gdb-build>
2016-02-18 19:23 ` sergiodj+buildbot
2016-02-18 19:38 [binutils-gdb] Determine the iteration count based on wallclock instead of user+system time sergiodj+buildbot
2016-02-18 20:32 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-19 14:40 [binutils-gdb] [ARM] Add FP16 feature extension for ARMv8.2 architecture sergiodj+buildbot
2016-02-19 15:14 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-19 15:34 [binutils-gdb] Fix a seg-fault in the linker when it encounters a corrupt binary containing a reloc with no associated symbol sergiodj+buildbot
2016-02-19 16:23 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-19 16:10 [binutils-gdb] Prevent a seg-fault in the linker when accessing a specially crafted, corrupt, aout binary sergiodj+buildbot
2016-02-19 17:32 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-21 20:46 [binutils-gdb] Remove search_parents parameter from d_lookup_symbol_imports sergiodj+buildbot
2016-02-21 20:50 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-21 21:15 [binutils-gdb] Also update recursive call to d_lookup_symbol_imports sergiodj+buildbot
2016-02-21 21:49 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-22 12:26 [binutils-gdb] Fix arm process record code format sergiodj+buildbot
2016-02-22 13:01 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-22 12:34 [binutils-gdb] [AArch64] Remove redundant calculation of plt stub destination for veneer sergiodj+buildbot
2016-02-22 14:11 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-22 16:37 [binutils-gdb] gdb-gdb.py: SyntaxError: Missing parentheses in call to 'print' sergiodj+buildbot
2016-02-22 18:11 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
     [not found] <4000e47e2f3860a85a9023f3fe5950c8cc6fa507@gdb-build>
2016-02-22 19:22 ` sergiodj+buildbot
2016-02-23  0:43 [binutils-gdb] Always create dynsym section with dynamic sections sergiodj+buildbot
2016-02-23  1:19 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-23  1:19 [binutils-gdb] Fix test-case ld-elf/pr19617b sergiodj+buildbot
2016-02-23  3:45 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-23 10:48 [binutils-gdb] Fix the genetation of GOT entries for the Microblaze target sergiodj+buildbot
2016-02-23 11:23 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-23 13:10 [binutils-gdb] Increment the ABIVERSION to 5 for MIPS objects with non-executable stacks sergiodj+buildbot
2016-02-23 13:43 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-23 13:32 [binutils-gdb] Make linker assigned symbol dynamic only for shared object sergiodj+buildbot
2016-02-23 14:53 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-23 18:34 [binutils-gdb] arm-tdep.c: Remove unused "to" parameters sergiodj+buildbot
2016-02-23 19:08 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-23 21:37 [binutils-gdb] Extend "skip" command to support -file, -gfile, -function, -rfunction sergiodj+buildbot
2016-02-23 22:12 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-24  3:22 [binutils-gdb] Build unavailable-stack frames for tracepoint sergiodj+buildbot
2016-02-24  4:03 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-24 13:54 [binutils-gdb] Set plt_got.offset to (bfd_vma) -1 sergiodj+buildbot
2016-02-24 14:38 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-24 14:09 [binutils-gdb] [OPCODE][ARM]Correct disassembler for cdp/cdp2, mcr/mcr2, mrc/mrc2, ldc/ldc2, stc/stc2 sergiodj+buildbot
2016-02-24 16:56 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-24 14:22 [binutils-gdb] [OPCODES][ARM][1/3]Add armv8.2 fp16 instruction dissembler support sergiodj+buildbot
2016-02-24 19:52 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-24 15:09 [binutils-gdb] Revert "ABS32" sergiodj+buildbot
2016-02-24 20:29 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-24 17:45 [binutils-gdb] powerpc: Support z-point type in gdbserver sergiodj+buildbot
2016-02-24 21:31 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-24 18:24 [binutils-gdb] Move new skip features to proper section (post 7.11) sergiodj+buildbot
2016-02-24 22:49 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-24 19:30 [binutils-gdb] Move tfile-avx.exp to tracefile-pseudo-reg.exp sergiodj+buildbot
2016-02-24 23:50 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-24 23:11 [binutils-gdb] Handle MIPS Linux SIGTRAP siginfo.si_code values sergiodj+buildbot
2016-02-25  3:16 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-24 23:37 [binutils-gdb] Update symbol version for symbol from linker script sergiodj+buildbot
2016-02-25  4:56 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-25 12:24 [binutils-gdb] Add elf_x86_64_need_pic sergiodj+buildbot
2016-02-25 12:59 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-25 14:46 [binutils-gdb] Map registers to remote numbers when encoding an ax_reg or ax_reg_mask operation sergiodj+buildbot
2016-02-25 15:22 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
     [not found] <7337a6f2297cdd91bb852b479b284e5796d62cc9@gdb-build>
2016-02-25 16:28 ` sergiodj+buildbot
2016-02-25 17:22 [binutils-gdb] Remove gdb.base/branches.c sergiodj+buildbot
2016-02-25 21:44 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
     [not found] <678b48b7cf0bd518ebc234bda98229cc602c2a45@gdb-build>
2016-02-25 17:40 ` sergiodj+buildbot
2016-02-25 17:42 [binutils-gdb] avoid compiler warnings in remote-m32r-sdi.c sergiodj+buildbot
2016-02-25 23:25 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
     [not found] <ae91f6253926e4dadebcae90772f4f5a5bd06056@gdb-build>
2016-02-25 20:31 ` sergiodj+buildbot
     [not found] <ab50308758bfde9ab7b50e6def65e20f0b560702@gdb-build>
2016-02-26  1:27 ` sergiodj+buildbot
2016-02-26 13:00 [binutils-gdb] Fix powerpc64 -r --save-restore-funcs sergiodj+buildbot
2016-02-26 13:48 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-26 13:10 [binutils-gdb] [x86] Resolve non-PIC undefweak symbols in executable sergiodj+buildbot
2016-02-26 15:29 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-26 15:51 [binutils-gdb] Record right reg num of thumb special data instructions sergiodj+buildbot
2016-02-26 21:43 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-26 16:00 [binutils-gdb] Fix various bugs in arm_record_exreg_ld_st_insn sergiodj+buildbot
2016-02-26 23:29 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-26 16:01 [binutils-gdb] Rename gdb.reverse/aarch64.{exp, c} to gdb.reverse/insn-reverse.{exp, c} sergiodj+buildbot
2016-02-26 20:01 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-26 17:52 [binutils-gdb] Optimize x86 GOT32X/GOTPCRELX relocations sergiodj+buildbot
2016-02-27  1:12 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-26 18:19 [binutils-gdb] [BFD][AARCH64]Fix MOVW_SABS_G(0, 1, 2) relocation overflow check sergiodj+buildbot
2016-02-27  3:19 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-26 20:20 [binutils-gdb] Add x86_64-*-rtems* target sergiodj+buildbot
2016-02-27  6:18 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-26 20:30 [binutils-gdb] Add aarch64-*-rtems* target sergiodj+buildbot
2016-02-27  8:20 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
     [not found] <1ed0c2a4bbe8ad5f5404014a6351b2b74db75577@gdb-build>
2016-02-27  9:52 ` sergiodj+buildbot
2016-02-28 15:25 [binutils-gdb] Don't recursively look for a symbol in all imports of imported modules sergiodj+buildbot
2016-02-28 16:12 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-29 15:24 [binutils-gdb] [ARC] General fixes sergiodj+buildbot
2016-02-29 16:23 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-29 16:04 [binutils-gdb] [ARC] Local symbols relocation cleanup sergiodj+buildbot
2016-02-29 17:46 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-29 16:58 [binutils-gdb] Support more syscalls in linux-record: pipe2 epoll_create1 eventfd2 fallocate dup3 and inotify_init1 sergiodj+buildbot
2016-02-29 19:28 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-02-29 17:29 [binutils-gdb] aarch64-linux process record: more syscalls sergiodj+buildbot
2016-02-29 21:25 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-01 11:55 [binutils-gdb] S390: Fix internal error with stackless inferior sergiodj+buildbot
2016-03-01 12:54 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-01 12:05 [binutils-gdb] S390: Fix output path for s390-tdbregs test case sergiodj+buildbot
2016-03-01 14:51 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-01 15:31 [binutils-gdb] Compile gdb.arch/arm-neon.c with "quiet" sergiodj+buildbot
2016-03-01 16:19 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-01 15:41 [binutils-gdb] Fix output path for arm-disp-step.exp sergiodj+buildbot
2016-03-01 17:53 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-01 17:26 [binutils-gdb] Fix gdb.base/catch-fork-kill.c compilation sergiodj+buildbot
2016-03-01 19:14 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-01 17:53 [binutils-gdb] Fix gdb.threads/watchpoint-fork*.c compilation sergiodj+buildbot
2016-03-01 20:53 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-01 18:47 [binutils-gdb] Fix gdb.trace/ftrace-lock.c compilation sergiodj+buildbot
2016-03-01 22:16 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-02  3:28 [binutils-gdb] Fix shift left warning at source sergiodj+buildbot
2016-03-02  4:14 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-02  3:46 [binutils-gdb] Regenerate rl78 opcodes file sergiodj+buildbot
2016-03-02  7:58 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-02  4:03 [binutils-gdb] Regenerate bfd files sergiodj+buildbot
2016-03-02  6:02 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-02 14:03 [binutils-gdb] Regenerate or1k opcodes file sergiodj+buildbot
2016-03-02 14:47 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-02 14:37 [binutils-gdb] Fix detection of gfortran compilers sergiodj+buildbot
2016-03-02 16:16 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-02 15:30 [binutils-gdb] Add new maintainer to Write After Approval sergiodj+buildbot
2016-03-02 18:00 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-02 15:53 [binutils-gdb] testsuite: Fix run to main issue introduced by GCC 5.x sergiodj+buildbot
2016-03-02 20:57 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-02 16:16 [binutils-gdb] testsuite: Remove unnecessary code in fortran vla-history test sergiodj+buildbot
2016-03-03  0:38 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-02 16:31 [binutils-gdb] [OBV] gdbserver: Only write ipa_tdesc_idx if agent is actually loaded sergiodj+buildbot
2016-03-03  2:18 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-02 17:06 [binutils-gdb] testsuite: Fix timeout issues during print of vla-arrays sergiodj+buildbot
2016-03-02 22:40 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-02 17:42 [binutils-gdb] Call enqueue_pending_signal in linux_resume_one_lwp_throw sergiodj+buildbot
2016-03-03  3:58 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-03  9:31 [binutils-gdb] [GDBserver] Leave child suspended when step over parent sergiodj+buildbot
2016-03-03 10:09 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-03  9:42 [binutils-gdb] Refactor gdb.base/disp-step-syscall.exp for general step over test sergiodj+buildbot
2016-03-03 11:20 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-03  9:51 [binutils-gdb] Step over syscalll insn with disp-step on and off sergiodj+buildbot
2016-03-03 12:26 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-03 10:00 [binutils-gdb] Step over fork/vfork syscall insn in gdbserver sergiodj+buildbot
2016-03-03 13:38 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-03 10:09 [binutils-gdb] Rename disp-step-syscall.exp to step-over-syscall.exp sergiodj+buildbot
2016-03-03 14:52 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-03 10:20 [binutils-gdb] Reformat gdb.base/step-over-syscall.exp sergiodj+buildbot
2016-03-03 15:55 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-03 10:27 [binutils-gdb] New test about step over clone syscall sergiodj+buildbot
2016-03-03 17:08 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-03 10:36 [binutils-gdb] Update comments to start_step_over sergiodj+buildbot
2016-03-03 18:28 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-03 15:34 [binutils-gdb] Fix bugs in the simulation of the AArch64's ADDP, FADDP, LD1, CCMP and CCMP instructions sergiodj+buildbot
2016-03-03 19:41 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-03 19:03 [binutils-gdb] gdb.base/skip.exp: Use with_test_prefix sergiodj+buildbot
2016-03-03 21:24 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-03 21:12 [binutils-gdb] Add new plugin hooks to support querying section alignment and size sergiodj+buildbot
2016-03-03 23:53 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-04 11:45 [binutils-gdb] [ARM] Add feature check for ARMv8.1 AdvSIMD instructions sergiodj+buildbot
2016-03-04 12:22 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-04 14:50 [binutils-gdb] Treat common symbol in executable as definition sergiodj+buildbot
2016-03-04 15:25 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-04 15:16 [binutils-gdb] feature_to_c.sh: Print help when passing no arguments sergiodj+buildbot
2016-03-04 16:33 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-04 16:10 [binutils-gdb] Tweak ARM process record sergiodj+buildbot
2016-03-04 17:51 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-04 16:41 [binutils-gdb] Add missing ChangeLog entries for commit 82838 sergiodj+buildbot
2016-03-04 20:11 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-04 17:01 [binutils-gdb] ARM process record: VMOV sergiodj+buildbot
2016-03-04 19:08 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-05 12:31 [binutils-gdb] Fix argument passing for call sergiodj+buildbot
2016-03-05 13:06 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-06  1:57 [binutils-gdb] Improve analysis of racy testcases sergiodj+buildbot
2016-03-06  2:46 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-06 22:42 [binutils-gdb] Set executable bit on analyze-racy-logs.py sergiodj+buildbot
2016-03-06 23:21 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-07 15:39 [binutils-gdb] Add const qualifiers at various places sergiodj+buildbot
2016-03-07 16:07 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-07 15:51 [binutils-gdb] [AArch64] Create .got section if _GLOBAL_OFFSET_TABLE_ referenced sergiodj+buildbot
2016-03-07 17:27 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-07 16:52 [binutils-gdb] Fix "set architecture mips:10000" crash sergiodj+buildbot
2016-03-07 18:39 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-07 17:40 [binutils-gdb] Allow zero length archive elements sergiodj+buildbot
2016-03-07 19:44 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-08 13:41 [binutils-gdb] [ARC] Allow non-instruction relocations within .text sections sergiodj+buildbot
2016-03-08 14:19 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-08 13:50 [binutils-gdb] Group common symbol checking together sergiodj+buildbot
2016-03-08 15:43 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-08 17:47 [binutils-gdb] Handle local IFUNC symbols in shared object sergiodj+buildbot
2016-03-08 18:38 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-09  2:37 [binutils-gdb] Fix HP/PA GNU/Linux "long double" format sergiodj+buildbot
2016-03-09  3:16 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-09  3:19 [binutils-gdb] Assert that a floating type's length is at least as long as its format sergiodj+buildbot
2016-03-09  4:35 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-09  3:39 [binutils-gdb] [CRIS] Don't internal error if forced big endian sergiodj+buildbot
2016-03-09  6:48 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-09  4:23 [binutils-gdb] Fix floating conversion buffer overrun when host/target format matches sergiodj+buildbot
2016-03-09  5:45 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-09  4:57 [binutils-gdb] Don't create dynamic sections when relocatable sergiodj+buildbot
2016-03-09  8:15 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-09  6:37 [binutils-gdb] Allow zero length archive elements sergiodj+buildbot
2016-03-09  9:10 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-09 15:43 [binutils-gdb] For COFF and COFF/PE targets, skip relocations against absolute symbols sergiodj+buildbot
2016-03-09 16:18 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-09 15:59 [binutils-gdb] Fix v850 bfd arch info printable names sergiodj+buildbot
2016-03-09 17:36 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-09 16:08 [binutils-gdb] [FR-V] Handle FR300 sergiodj+buildbot
2016-03-09 18:47 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-09 16:19 [binutils-gdb] Avoid spaces in osabi names sergiodj+buildbot
2016-03-09 19:53 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-09 16:30 [binutils-gdb] S390: Add use of unavailable-stack frame ID sergiodj+buildbot
2016-03-09 21:09 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-09 16:41 [binutils-gdb] S390: Recognize special jumps in prologue parser sergiodj+buildbot
2016-03-09 22:21 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-09 18:02 [binutils-gdb] gdb: Add ax_pseudo_register_collect for powerpc sergiodj+buildbot
2016-03-09 23:32 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-09 18:28 [binutils-gdb] gdb: Add gen_return_address for powerpc sergiodj+buildbot
2016-03-10  0:40 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-09 18:40 [binutils-gdb] gdb/rs6000: Read backchain as unsigned sergiodj+buildbot
2016-03-10  1:49 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-09 18:50 [binutils-gdb] gdb.trace: Use manually-defined start labels in unavailable-dwarf-piece.exp sergiodj+buildbot
2016-03-10  2:58 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-09 19:21 [binutils-gdb] gdb.trace/entry-values.exp: Fixes for powerpc64 sergiodj+buildbot
2016-03-10  6:52 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-09 19:42 [binutils-gdb] Test issuing a command split in multiple lines with continuation chars sergiodj+buildbot
2016-03-10  9:03 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-09 20:06 [binutils-gdb] gdb_readline2 -> gdb_readline_no_editing_callback sergiodj+buildbot
2016-03-10 11:51 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-09 20:15 [binutils-gdb] Eliminate async_annotation_suffix sergiodj+buildbot
2016-03-10 12:57 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-09 20:47 [binutils-gdb] Use struct buffer in gdb_readline_no_editing sergiodj+buildbot
2016-03-10 16:47 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-09 20:57 [binutils-gdb] Use struct buffer in gdb_readline_no_editing_callback sergiodj+buildbot
2016-03-10 17:43 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-09 21:09 [binutils-gdb] Simplify saved_command_line handling sergiodj+buildbot
2016-03-10 18:55 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-09 21:46 [binutils-gdb] gdb: fix doc string of target_can_use_hardware_watchpoint sergiodj+buildbot
2016-03-10 21:38 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-09 21:55 [binutils-gdb] More "Program" -> "Thread NN received signal" testsuite adjustment sergiodj+buildbot
2016-03-10 22:29 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-09 22:03 [binutils-gdb] gdb.trace/change-loc.exp: Don't depend on tracepoint ordering sergiodj+buildbot
2016-03-10  4:26 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-09 23:54 [binutils-gdb] gdb: Add tracepoint support for powerpc sergiodj+buildbot
2016-03-10  7:54 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-10  1:30 [binutils-gdb] gdb.trace/tfind.exp: Force call via global entry point on ppc64le sergiodj+buildbot
2016-03-10  5:36 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-10 15:43 [binutils-gdb] Mark the i370 target as obsolete sergiodj+buildbot
2016-03-10 23:44 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-10 22:34 [binutils-gdb] Add $_as_string convenience function sergiodj+buildbot
2016-03-11  0:50 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-11  9:28 [binutils-gdb] Fix some places where octet to byte conversions are needed sergiodj+buildbot
2016-03-11 10:08 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-11 10:15 [binutils-gdb] gdb/s390: Fill pseudo register agent expression hooks sergiodj+buildbot
2016-03-11 11:21 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-13 10:06 [binutils-gdb] gdb/s390: Fill gen_return_address hook sergiodj+buildbot
2016-03-13 10:51 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-14 16:56 [binutils-gdb] gdb.base/default.exp: Add missing $_as_string to "show convenience" test sergiodj+buildbot
2016-03-14 17:35 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-14 20:28 [binutils-gdb] Regenerate bfd-in2.h sergiodj+buildbot
2016-03-14 21:05 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-15 17:14 [binutils-gdb] Fix PR gdb/19676: Internal error in linux-thread.db.c if /proc not mounted sergiodj+buildbot
2016-03-15 18:38 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-15 18:19 [binutils-gdb] Add -z noreloc-overflow option to x86-64 ld sergiodj+buildbot
2016-03-15 22:16 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-16 16:29 [binutils-gdb] [ARM] Support ARMv8.2 FP16 simd instructions sergiodj+buildbot
2016-03-16 17:23 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-16 17:48 [binutils-gdb] xml-tdesc.c (tdesc_start_enum): Fix c++ build sergiodj+buildbot
2016-03-17 12:16 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-16 22:29 [binutils-gdb] PR remote/19496, interrupted syscall in forking-threads-plus-bkpt sergiodj+buildbot
2016-03-17 17:24 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-17  9:19 [binutils-gdb] linux-record: Fix bad fall-through for pipe/pipe2 sergiodj+buildbot
2016-03-17 22:40 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-17  9:34 [binutils-gdb] linux-record.c: Fix whitespace issues sergiodj+buildbot
2016-03-18  0:55 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-17 10:12 [binutils-gdb] S390: Fix output path for s390-multiarch test case sergiodj+buildbot
2016-03-18  3:17 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-17 10:43 [binutils-gdb] PR remote/19496, timeout in forking-threads-plus-bkpt sergiodj+buildbot
2016-03-18  5:41 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-17 17:33 [binutils-gdb] Suggest running gdbserver for a PID in container sergiodj+buildbot
2016-03-18  8:19 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-17 23:01 [binutils-gdb] Add mips and s390 build targets for gold sergiodj+buildbot
2016-03-18  9:10 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-18  9:45 [binutils-gdb] Add simulation of MUL and NEG instructions to AArch64 simulator sergiodj+buildbot
2016-03-18 15:36 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-18 14:39 [binutils-gdb] Remove redundant WIFSTOPPED check sergiodj+buildbot
2016-03-18 18:04 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-18 15:06 [binutils-gdb] Set signal to 0 after enqueue_pending_signal sergiodj+buildbot
2016-03-18 20:41 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-18 15:17 [binutils-gdb] Check lwp_signal_can_be_delivered for enqueue/dequeue pending signals sergiodj+buildbot
2016-03-18 21:45 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-18 15:36 [binutils-gdb] Fix code to check for illegal element numbers when accessing AArch64 vector registers in AArch64 sim sergiodj+buildbot
2016-03-19  0:23 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-18 15:45 [binutils-gdb] Make sparc_software_single_step static sergiodj+buildbot
2016-03-19  1:43 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-18 16:52 [binutils-gdb] [spu] throw error when target_read_memory fails sergiodj+buildbot
2016-03-18 23:00 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-18 17:25 [binutils-gdb] Fix thinko in new GET_VEC_ELEMENT macro sergiodj+buildbot
2016-03-19  5:40 ` Failures on Debian-i686-native-gdbserver, branch master sergiodj+buildbot
2016-03-18 18:39 [binutils-gdb] Fix the disassembly of the AArch64's OOR instruction as a MOV instruction sergiodj+buildbot
2016-03-19  3:43 ` Failures on Debian-i686-native-gdbserver, branch master 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).