public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
* [binutils-gdb] Switch current_thread to lwp's thread in install_software_single_step_breakpoints
@ 2016-07-21 14:58 sergiodj+buildbot
  2016-07-21 15:01 ` *** COMPILATION FAILED *** Failures on Fedora-x86_64-c-build-m64, branch master *** BREAKAGE *** sergiodj+buildbot
                   ` (7 more replies)
  0 siblings, 8 replies; 22+ messages in thread
From: sergiodj+buildbot @ 2016-07-21 14:58 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 984a2c042e82f2306183d9d165c5cb99e4341503 ***

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

Switch current_thread to lwp's thread in install_software_single_step_breakpoints

install_software_single_step_breakpoints has parameter lwp, but still
need to switch to current_thread.  In order to simplify its caller,
we do the current_thread save/restore inside install_software_single_step_breakpoints.

gdb/gdbserver:

2016-07-21  Yao Qi  <yao.qi@linaro.org>

	* gdbthread.h (make_cleanup_restore_current_thread): Declare.
	* inferiors.c (do_restore_current_thread_cleanup): New function.
	(make_cleanup_restore_current_thread): Likewise.
	* linux-low.c (install_software_single_step_breakpoints): Call
	make_cleanup_restore_current_thread.  Switch current_thread to
	thread.


^ permalink raw reply	[flat|nested] 22+ messages in thread
* [binutils-gdb] Support vCont s and S actions with software single step
@ 2016-07-21 17:54 sergiodj+buildbot
  2016-07-21 17:54 ` *** COMPILATION FAILED *** Failures on Fedora-x86_64-c-build-m64, branch master *** BREAKAGE *** sergiodj+buildbot
  0 siblings, 1 reply; 22+ messages in thread
From: sergiodj+buildbot @ 2016-07-21 17:54 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 21536b367ce73eed103e1389b5f45010f0c96bbb ***

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

Support vCont s and S actions with software single step

GDBserver with software single step should be able to claim supporting
vCont s and S actions, so that GDB knows the remote target can do
single step.  It doesn't matter to GDB that the single step in the
remote target is done via hardware or software.

gdb/gdbserver:

2016-07-21  Yao Qi  <yao.qi@linaro.org>

	* server.c (handle_v_requests): Support s and S actions
	if target_supports_software_single_step return true.


^ permalink raw reply	[flat|nested] 22+ messages in thread
* [binutils-gdb] Use reinsert_breakpoint for vCont;s
@ 2016-07-21 17:08 sergiodj+buildbot
  2016-07-21 17:12 ` *** COMPILATION FAILED *** Failures on Fedora-x86_64-c-build-m64, branch master *** BREAKAGE *** sergiodj+buildbot
  0 siblings, 1 reply; 22+ messages in thread
From: sergiodj+buildbot @ 2016-07-21 17:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8901d1936e4e691f0b3b976f5626ac5a8f27aa7f ***

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

Use reinsert_breakpoint for vCont;s

This patch is to teach GDBserver using software single step to handle
vCont;s.  Simply speaking, if the thread's resume request is resume_step,
install reinsert breakpoint at the next pcs when GDBserver is about to
resume threads.  These reinsert breakpoints of a thread are removed,
when GDBserver gets an event from that thread and reports it back to
GDB.

gdb/gdbserver:

2016-07-21  Yao Qi  <yao.qi@linaro.org>

	* linux-low.c (resume_stopped_resumed_lwps): If resume request
	is resume_step, call maybe_hw_step.
	(linux_wait_1): Stop all threads, remove reinsert breakpoints,
	and unstop them.
	(linux_resume_one_lwp_throw): Don't assert the thread has reinsert
	breakpoints or not.
	(proceed_one_lwp): If resume request is resume_step, install
	reinsert breakpoints and call maybe_hw_step.


^ permalink raw reply	[flat|nested] 22+ messages in thread
* [binutils-gdb] Enqueue signal even when resuming threads
@ 2016-07-21 15:58 sergiodj+buildbot
  2016-07-21 16:23 ` *** COMPILATION FAILED *** Failures on Fedora-x86_64-c-build-m64, branch master *** BREAKAGE *** sergiodj+buildbot
  0 siblings, 1 reply; 22+ messages in thread
From: sergiodj+buildbot @ 2016-07-21 15:58 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0e9a339ec8ffab80fdbe97adaf888fe03b73fe22 ***

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

Enqueue signal even when resuming threads

Nowadays, we only enqueue signal when we leave thread pending in
linux_resume_one_thread.  If lwp->resume->sig isn't zero (GDB wants
to resume with signal), we pass lwp->resume->sig to
linux_resume_one_lwp.

In order to reduce the difference between resuming thread with signal
and proceeding thread with signal, when we resume thread, we can
enqueue signal too, and proceed thread.  The signal will be consumed in
linux_resume_one_lwp_throw from lwp->pending_signals.

gdb/gdbserver:

2016-07-21  Yao Qi  <yao.qi@linaro.org>

	* linux-low.c (proceed_one_lwp): Declare.
	(linux_resume_one_thread): Remove local variable 'step'.
	Lift code enqueue signal.  Call proceed_one_lwp instead of
	linux_resume_one_lwp.


^ permalink raw reply	[flat|nested] 22+ messages in thread
* [binutils-gdb] Use enqueue_pending_signal in linux_resume_one_thread
@ 2016-07-21 15:20 sergiodj+buildbot
  2016-07-21 15:35 ` *** COMPILATION FAILED *** Failures on Fedora-x86_64-c-build-m64, branch master *** BREAKAGE *** sergiodj+buildbot
  0 siblings, 1 reply; 22+ messages in thread
From: sergiodj+buildbot @ 2016-07-21 15:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4281b351bfa3b646ab531cf73c56e49366fef108 ***

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

Use enqueue_pending_signal in linux_resume_one_thread

gdb/gdbserver:

2016-07-21  Yao Qi  <yao.qi@linaro.org>

	* linux-low.c (linux_resume_one_thread): Call
	enqueue_pending_signal.


^ permalink raw reply	[flat|nested] 22+ messages in thread
* [binutils-gdb] Make reinsert_breakpoint thread specific
@ 2016-07-21 14:36 sergiodj+buildbot
  2016-07-21 14:36 ` *** COMPILATION FAILED *** Failures on Fedora-x86_64-c-build-m64, branch master *** BREAKAGE *** sergiodj+buildbot
  0 siblings, 1 reply; 22+ messages in thread
From: sergiodj+buildbot @ 2016-07-21 14:36 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bec903c96bc5119e357b4ad2cab99bbee7de628e ***

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

Make reinsert_breakpoint thread specific

This patch makes reinsert_breakpoint thread specific, which means we
insert and remove reinsert_breakpoint breakpoints for a specific
thread.  This motivation of this change is that I'll use
reinsert_breakpoint for vCont;s on software single step target, so that
GDBserver may insert one reinsert_breakpoint for one thread doing
step-over, and insert one reinsert_breakpoint for another thread doing
vCont;s.  After the operation of one thread is finished, GDBserver must
remove reinsert_breakpoint for that thread only.

On the other hand, reinsert_breakpoint is used for step-over nowadays.
GDBserver inserts reinsert_breakpoint, and wait only from the thread
doing step-over.  After the step-over is done, GDBserver removes the
reinsert_breakpoint.  If there is still any threads need step-over, do
the same again until all threads are finished step-over.  In other words,
reinsert_breakpoint is globally thread specific, but in an implicit way.
It is natural to make it explicitly thread specific.

gdb/gdbserver:

2016-07-21  Yao Qi  <yao.qi@linaro.org>

	* mem-break.c (struct reinsert_breakpoint) <ptid>: New field.
	(set_reinsert_breakpoint): New parameter ptid.  Callers updated.
	(clone_one_breakpoint): Likewise.
	(delete_reinsert_breakpoints): Change parameter to thread.
	Callers updated.
	(has_reinsert_breakpoints): Likewise.
	(uninsert_reinsert_breakpoints): Likewise.
	(reinsert_reinsert_breakpoints): Likewise.
	* mem-break.h (set_reinsert_breakpoint): Update declaration.
	(delete_reinsert_breakpoints): Likewise.
	(reinsert_reinsert_breakpoints): Likewise.
	(uninsert_reinsert_breakpoints): Likewise.
	(has_reinsert_breakpoints): Likewise.


^ permalink raw reply	[flat|nested] 22+ messages in thread
* [binutils-gdb] Refactor clone_all_breakpoints
@ 2016-07-21 13:37 sergiodj+buildbot
  2016-07-21 13:39 ` *** COMPILATION FAILED *** Failures on Fedora-x86_64-c-build-m64, branch master *** BREAKAGE *** sergiodj+buildbot
  0 siblings, 1 reply; 22+ messages in thread
From: sergiodj+buildbot @ 2016-07-21 13:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 63c40ec727109e2bb2956ab95968350df00c1aa1 ***

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

Refactor clone_all_breakpoints

This patch is to change the interface of clone_all_breakpoints, from
lists of breakpoints and raw_breakpoints to child thread and parent
thread.  I choose child thread to pass because we need the ptid of
the child thread in the following patch.

gdb/gdbserver:

2016-07-21  Yao Qi  <yao.qi@linaro.org>

	* inferiors.c (get_thread_process): Make parameter const.
	* inferiors.h (get_thread_process): Update declaration.
	* mem-break.c (clone_all_breakpoints): Remove all parameters.
	Add new parameters child_thread and parent_thread.  Callers
	updated.
	* mem-break.h (clone_all_breakpoints): Update declaration.


^ permalink raw reply	[flat|nested] 22+ messages in thread
* [binutils-gdb] Create sub classes of 'struct breakpoint'
@ 2016-07-21 12:41 sergiodj+buildbot
  2016-07-21 12:47 ` *** COMPILATION FAILED *** Failures on Fedora-x86_64-c-build-m64, branch master *** BREAKAGE *** sergiodj+buildbot
  0 siblings, 1 reply; 22+ messages in thread
From: sergiodj+buildbot @ 2016-07-21 12:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9aa76cd0a7b2cfdcc9da31e7763a695fac89f569 ***

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

Create sub classes of 'struct breakpoint'

Nowadays, there are three types of breakpoint in GDBserver,

 - gdb breakpoints,
 - reinsert breakpoints, used for software single step,
 - other breakpoints, used for tracepoint,

but we only have one 'struct breakpoint' for all of them.  Some fields
are only useful to one type of breakpoint.  For example, cond_list
and command_list are only used by gdb breakpoints, while handler is
only used by other breakpoints.

This patch changes 'struct breakpoint' to a base class, which has fields
needed by all breakpoint types, also add three sub-classes to
'struct breakpoint' to these three types of breakpoints.

gdb/gdbserver:

2016-07-21  Yao Qi  <yao.qi@linaro.org>

	* mem-break.c (struct breakpoint) <cond_list>: Remove.
	<command_list, handler>: Remove.
	(struct gdb_breakpoint): New.
	(struct other_breakpoint): New.
	(struct reinsert_breakpoint): New.
	(is_gdb_breakpoint): New function.
	(any_persistent_commands): Update command_list if
	is_gdb_breakpoint returns true.
	(set_breakpoint): Create breakpoints according to their types.
	(find_gdb_breakpoint): Return 'struct gdb_breakpoint *'.
	(set_gdb_breakpoint_1): Likewise.
	(set_gdb_breakpoint): Likewise.
	(clear_breakpoint_conditions): Change parameter type to
	'struct gdb_breakpoint *'.
	(clear_breakpoint_commands): Likewise.
	(clear_breakpoint_conditions_and_commands): Likewise.
	(add_condition_to_breakpoint): Likewise.
	(add_breakpoint_condition): Likewise.
	(add_commands_to_breakpoint): Likewise.
	(check_breakpoints): Check other_breakpoint.
	(clone_one_breakpoint): Clone breakpopint according to its type.
	* mem-break.h (struct gdb_breakpoint): Declare.
	(set_gdb_breakpoint): Update declaration.
	(clear_breakpoint_conditions_and_commands): Likewise.
	(add_breakpoint_condition): Likewise.
	(add_breakpoint_commands): Likewise.
	* server.c (process_point_options): Change parameter type to
	'struct gdb_breakpoint *'.


^ permalink raw reply	[flat|nested] 22+ messages in thread
* [binutils-gdb] Fix of default lookup for "this" symbol.
@ 2016-07-07 15:52 sergiodj+buildbot
  2016-07-07 15:57 ` *** COMPILATION FAILED *** Failures on Fedora-x86_64-c-build-m64, branch master *** BREAKAGE *** sergiodj+buildbot
  0 siblings, 1 reply; 22+ messages in thread
From: sergiodj+buildbot @ 2016-07-07 15:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4f19a0e6b45c63c0b4afe27a19d144cca412d4ae ***

Author: Walfred Tedeschi <walfred.tedeschi@intel.com>
Branch: master
Commit: 4f19a0e6b45c63c0b4afe27a19d144cca412d4ae

Fix of default lookup for "this" symbol.

Using the default lookup for the symbol "this" might lead to segmentation
fault in GDB.
Some languages, e.g. Fortran, use as default lookup routine the C++
routines.
For those languages "this" can be the instance of a class or even the
definition of a class.
When an instance of a class having the name "this" is evaluated
in GDB a segmentation fault was observed.

As example of the issue take into consideration the Fortran code:
  type foo
    real :: a
    type(bar) :: x
    character*7 :: b
  end type foo
  type(foo) :: this

Issue appears when evaluating the variable "this" in GDB.

Within the language definition structure there is a field that represents
the name of the special symbol used for the C++ "this" for the language
being described.
The fix presented here takes into account the aforementioned field. In the
case the aforementioned field is NULL "this" is not represented in the
language described and the lookup should return a null_block_symbol.

Tests: Performed tests with gfortran and ifort.

Reviewed:
https://sourceware.org/ml/gdb-patches/2016-04/msg00068.html

After the commited patch:
https://sourceware.org/ml/gdb-patches/2016-06/msg00364.html
Patch can be applied.

2016-06-16  Walfred Tedeschi  <walfred.tedeschi@intel.com>

gdb/ChangeLog:

	* cp-namespace.c (cp_lookup_bare_symbol): Use language passed as
	parameter to look for the symbol "this".

gdb/testsuite/ChangeLog:

	* gdb.fortran/derived-types.exp (result_line, result_line_2):
	New variables.
	(print this%a, print this%b, print this): New tests.
	* gdb.fortran/derived-types.f90 (this): New object and
	initialization.


^ permalink raw reply	[flat|nested] 22+ messages in thread
* [binutils-gdb] Set unknown_syscall differently on arm linux
@ 2016-06-29 14:20 sergiodj+buildbot
  2016-06-29 14:23 ` *** COMPILATION FAILED *** Failures on Fedora-x86_64-c-build-m64, branch master *** BREAKAGE *** sergiodj+buildbot
  0 siblings, 1 reply; 22+ messages in thread
From: sergiodj+buildbot @ 2016-06-29 14:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 28244707d9e4f35cab1f9069cee1d44b38be095f ***

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

Set unknown_syscall differently on arm linux

Currently, we use 123456789 as unknown or illegal syscall number, and
expect program return ENOSYS.  Although 123456789 is an illegal syscall
number on arm linux, kernel sends SIGILL rather than returns -ENOSYS.
However, arm linux kernel returns -ENOSYS if syscall number is within
0xf0001..0xf07ff, so we can use 0xf07ff for unknown_syscall in test.

gdb/testsuite:

2016-06-29  Yao Qi  <yao.qi@linaro.org>

	* gdb.base/catch-syscall.c [__arm__]: Set unknown_syscall to
	0x0f07ff.


^ permalink raw reply	[flat|nested] 22+ messages in thread
* [binutils-gdb] sparc: make SPARC_OPCODE_ARCH_MAX part of its enum
@ 2016-06-29 12:11 sergiodj+buildbot
  2016-06-29 12:34 ` *** COMPILATION FAILED *** Failures on Fedora-x86_64-c-build-m64, branch master *** BREAKAGE *** sergiodj+buildbot
  0 siblings, 1 reply; 22+ messages in thread
From: sergiodj+buildbot @ 2016-06-29 12:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 042c94de565ae62640c064f1cb33d28484aeb9d3 ***

Author: Trevor Saunders <tbsaunde+binutils@tbsaunde.org>
Branch: master
Commit: 042c94de565ae62640c064f1cb33d28484aeb9d3

sparc: make SPARC_OPCODE_ARCH_MAX part of its enum

include/ChangeLog:

2016-06-29  Trevor Saunders  <tbsaunde+binutils@tbsaunde.org>

	* opcode/sparc.h (enum sparc_opcode_arch_val): Move
	SPARC_OPCODE_ARCH_MAX into the enum.


^ permalink raw reply	[flat|nested] 22+ messages in thread
* [binutils-gdb] Use strtok_r instead of strsep in rust_get_disr_info
@ 2016-06-29 11:32 sergiodj+buildbot
  2016-06-29 11:34 ` *** COMPILATION FAILED *** Failures on Fedora-x86_64-c-build-m64, branch master *** BREAKAGE *** sergiodj+buildbot
  0 siblings, 1 reply; 22+ messages in thread
From: sergiodj+buildbot @ 2016-06-29 11:32 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a405c2281ad29b5c7f9f2a4d58b7cfef2b74ba99 ***

Author: Manish Goregaokar <manish@mozilla.com>
Branch: master
Commit: a405c2281ad29b5c7f9f2a4d58b7cfef2b74ba99

Use strtok_r instead of strsep in rust_get_disr_info

strsep doesn't exist on Windows.

2016-06-29  Manish Goregaokar  <manish@mozilla.com>

gdb/ChangeLog:
    * rust-lang.c (rust_get_disr_info): Use strtok_r instead of strsep.


^ permalink raw reply	[flat|nested] 22+ messages in thread
* [binutils-gdb] Skip version check for unreferenced and undefined symbol
@ 2016-06-28 15:16 sergiodj+buildbot
  2016-06-28 16:00 ` *** COMPILATION FAILED *** Failures on Fedora-x86_64-c-build-m64, branch master *** BREAKAGE *** sergiodj+buildbot
  0 siblings, 1 reply; 22+ messages in thread
From: sergiodj+buildbot @ 2016-06-28 15:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f4ab0e2d1d4e14cfdddf46ac846c48ae55f4e14a ***

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

Skip version check for unreferenced and undefined symbol

No need to check version if symbol is unreferenced and undefined.

bfd/

	PR ld/20306
	* elflink.c (elf_link_check_versioned_symbol): Return false
	for unreferenced undefined symbol.

ld/testsuite/

	* testsuite/ld-gc/gc.exp: Run pr20306 test.
	* ld-gc/pr20306.c: New file.
	* ld-gc/pr20306.d: Likewise.


^ permalink raw reply	[flat|nested] 22+ messages in thread
* [binutils-gdb] Fix more linker testsuite failures.
@ 2016-06-28 15:13 sergiodj+buildbot
  2016-06-28 15:15 ` *** COMPILATION FAILED *** Failures on Fedora-x86_64-c-build-m64, branch master *** BREAKAGE *** sergiodj+buildbot
  0 siblings, 1 reply; 22+ messages in thread
From: sergiodj+buildbot @ 2016-06-28 15:13 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1b857aeed3f5cfddc4b5b1f5836ccd341aeb9f5d ***

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

Fix more linker testsuite failures.

bfin	* elf32-bfin.c (bfin_adjust_dynamic_symbol): Fail if a COPY reloc
	is needed.

ld	* testsuite/ld-elf/comm-data.exp: Expect comm-data2 test to fail
	for bfin.
	* testsuite/ld-elf/elf.exp: Expect pr14170 and symbolic function
	tests to fail for bfin.
	* testsuite/ld-elf/endsym.d: Expect to fail with cr16, crx, dlx,
	nds32 and visium.
	* testsuite/ld-elf/var1.d: Expect to fail with d30v, dlx, ft32 and
	microblaze.
	* testsuite/ld-pe/pe.exp: Expect foreign symbol test to fail for
	mcore-pe.


^ permalink raw reply	[flat|nested] 22+ messages in thread

end of thread, other threads:[~2016-07-26  0:47 UTC | newest]

Thread overview: 22+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-07-21 14:58 [binutils-gdb] Switch current_thread to lwp's thread in install_software_single_step_breakpoints sergiodj+buildbot
2016-07-21 15:01 ` *** COMPILATION FAILED *** Failures on Fedora-x86_64-c-build-m64, branch master *** BREAKAGE *** sergiodj+buildbot
2016-07-21 17:39 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-07-21 17:44 ` Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot
2016-07-21 18:11 ` Failures on Debian-i686-native-extended-gdbserver, " sergiodj+buildbot
2016-07-22  5:09 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj+buildbot
2016-07-22  6:28 ` Failures on Fedora-ppc64be-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-07-26  1:52 ` Failures on Fedora-ppc64le-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-07-26  2:27 ` Failures on Fedora-ppc64le-native-gdbserver-m64, " sergiodj+buildbot
  -- strict thread matches above, loose matches on Subject: below --
2016-07-21 17:54 [binutils-gdb] Support vCont s and S actions with software single step sergiodj+buildbot
2016-07-21 17:54 ` *** COMPILATION FAILED *** Failures on Fedora-x86_64-c-build-m64, branch master *** BREAKAGE *** sergiodj+buildbot
2016-07-21 17:08 [binutils-gdb] Use reinsert_breakpoint for vCont;s sergiodj+buildbot
2016-07-21 17:12 ` *** COMPILATION FAILED *** Failures on Fedora-x86_64-c-build-m64, branch master *** BREAKAGE *** sergiodj+buildbot
2016-07-21 15:58 [binutils-gdb] Enqueue signal even when resuming threads sergiodj+buildbot
2016-07-21 16:23 ` *** COMPILATION FAILED *** Failures on Fedora-x86_64-c-build-m64, branch master *** BREAKAGE *** sergiodj+buildbot
2016-07-21 15:20 [binutils-gdb] Use enqueue_pending_signal in linux_resume_one_thread sergiodj+buildbot
2016-07-21 15:35 ` *** COMPILATION FAILED *** Failures on Fedora-x86_64-c-build-m64, branch master *** BREAKAGE *** sergiodj+buildbot
2016-07-21 14:36 [binutils-gdb] Make reinsert_breakpoint thread specific sergiodj+buildbot
2016-07-21 14:36 ` *** COMPILATION FAILED *** Failures on Fedora-x86_64-c-build-m64, branch master *** BREAKAGE *** sergiodj+buildbot
2016-07-21 13:37 [binutils-gdb] Refactor clone_all_breakpoints sergiodj+buildbot
2016-07-21 13:39 ` *** COMPILATION FAILED *** Failures on Fedora-x86_64-c-build-m64, branch master *** BREAKAGE *** sergiodj+buildbot
2016-07-21 12:41 [binutils-gdb] Create sub classes of 'struct breakpoint' sergiodj+buildbot
2016-07-21 12:47 ` *** COMPILATION FAILED *** Failures on Fedora-x86_64-c-build-m64, branch master *** BREAKAGE *** sergiodj+buildbot
2016-07-07 15:52 [binutils-gdb] Fix of default lookup for "this" symbol sergiodj+buildbot
2016-07-07 15:57 ` *** COMPILATION FAILED *** Failures on Fedora-x86_64-c-build-m64, branch master *** BREAKAGE *** sergiodj+buildbot
2016-06-29 14:20 [binutils-gdb] Set unknown_syscall differently on arm linux sergiodj+buildbot
2016-06-29 14:23 ` *** COMPILATION FAILED *** Failures on Fedora-x86_64-c-build-m64, branch master *** BREAKAGE *** sergiodj+buildbot
2016-06-29 12:11 [binutils-gdb] sparc: make SPARC_OPCODE_ARCH_MAX part of its enum sergiodj+buildbot
2016-06-29 12:34 ` *** COMPILATION FAILED *** Failures on Fedora-x86_64-c-build-m64, branch master *** BREAKAGE *** sergiodj+buildbot
2016-06-29 11:32 [binutils-gdb] Use strtok_r instead of strsep in rust_get_disr_info sergiodj+buildbot
2016-06-29 11:34 ` *** COMPILATION FAILED *** Failures on Fedora-x86_64-c-build-m64, branch master *** BREAKAGE *** sergiodj+buildbot
2016-06-28 15:16 [binutils-gdb] Skip version check for unreferenced and undefined symbol sergiodj+buildbot
2016-06-28 16:00 ` *** COMPILATION FAILED *** Failures on Fedora-x86_64-c-build-m64, branch master *** BREAKAGE *** sergiodj+buildbot
2016-06-28 15:13 [binutils-gdb] Fix more linker testsuite failures sergiodj+buildbot
2016-06-28 15:15 ` *** COMPILATION FAILED *** Failures on Fedora-x86_64-c-build-m64, branch master *** BREAKAGE *** 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).