public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
* Test results for commit 7b582627bc42922de3b75792472f5223f1910277 on branch gdb-7.9-branch
@ 2015-02-20  5:01 sergiodj
  2015-02-20  5:21 ` Failures on Fedora-ppc64be-cc-with-index, " sergiodj
                   ` (13 more replies)
  0 siblings, 14 replies; 36+ messages in thread
From: sergiodj @ 2015-02-20  5:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7b582627bc42922de3b75792472f5223f1910277 ***

Author: David Taylor <dtaylor@emc.com>
Branch: gdb-7.9-branch
Commit: 7b582627bc42922de3b75792472f5223f1910277

[gdb/ax] small "setv" fix and documentation's adjustment.
gdb/doc/agentexpr.texi documents the "setv" opcode as follow:

    @item @code{setv} (0x2d) @var{n}: @result{} @var{v}
    Set trace state variable number @var{n} to the value found on the top
    of the stack.  The stack is unchanged, so that the value is readily
    available if the assignment is part of a larger expression.  The
    handling of @var{n} is as described for @code{getv}.

The @item line is incorrect (and does not match with its
description), so this patch fixes it.

Additionally, in gdb/common/ax.def we find the line:

    DEFOP (setv, 2, 0, 0, 1, 0x2d)

>From the comment earlier in the file:

       Each line is of the form:

       DEFOP (name, size, data_size, consumed, produced, opcode)
[...]
       CONSUMED is the number of stack elements consumed.
       PRODUCED is the number of stack elements produced.

which is saying that nothing is consumed and one item is produced.
Both should be 0 or both should be 1.

This patch sets them both to 1, which seems better since if nothing
is on the stack an error will occur.

gdb/ChangeLog:

        * common/ax.def (setv): Fix consumed entry in setv DEFOP.

gdb/doc/ChangeLog:

        * agentexpr.texi (Bytecode Descriptions): Fix summary line for setv.

Tested on x86_64-linux.


^ permalink raw reply	[flat|nested] 36+ messages in thread
* [binutils-gdb/gdb-7.9-branch] Fix the triplet regexp to recognize triplets, not only quadruplets
@ 2015-03-31 15:30 sergiodj+buildbot
  2015-03-31 16:01 ` Failures on Fedora-ppc64be-native-gdbserver-m64, branch gdb-7.9-branch sergiodj+buildbot
  0 siblings, 1 reply; 36+ messages in thread
From: sergiodj+buildbot @ 2015-03-31 15:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2e9f68f0cf32bad824100dfb5d05c4235cf59ff3 ***

Author: Matthias Klose <doko@ubuntu.com>
Branch: gdb-7.9-branch
Commit: 2e9f68f0cf32bad824100dfb5d05c4235cf59ff3

Fix the triplet regexp to recognize triplets, not only quadruplets
This allows triplets where the vendor is not set.

gdb/ChangeLog:
2015-03-31  Matthias Klose  <doko@ubuntu.com>

	* compile/compile.c (compile_to_object): Allow triplets with or
	without vendor set.


^ permalink raw reply	[flat|nested] 36+ messages in thread
* [binutils-gdb/gdb-7.9-branch] Change // comment in gdb/compile/
@ 2015-02-26 14:38 sergiodj+buildbot
  2015-02-26 14:41 ` Failures on Fedora-ppc64be-native-gdbserver-m64, branch gdb-7.9-branch sergiodj+buildbot
  0 siblings, 1 reply; 36+ messages in thread
From: sergiodj+buildbot @ 2015-02-26 14:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 09de64b93c2402e068daf0bce1c4a1dda833b646 ***

Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Branch: gdb-7.9-branch
Commit: 09de64b93c2402e068daf0bce1c4a1dda833b646

Change // comment in gdb/compile/
gdb/ChangeLog
2015-02-26  Jan Kratochvil  <jan.kratochvil@redhat.com>

	PR build/18033
	* compile/compile-c-support.c (c_compute_program): Change // comment.
	* compile/compile-object-load.c (setup_sections): Change // comment.


^ permalink raw reply	[flat|nested] 36+ messages in thread
* [binutils-gdb/gdb-7.9-branch] Remove // comment in gdb/iq2000-tdep.c
@ 2015-02-26 12:11 sergiodj+buildbot
  2015-02-26 12:22 ` Failures on Fedora-ppc64be-native-gdbserver-m64, branch gdb-7.9-branch sergiodj+buildbot
  0 siblings, 1 reply; 36+ messages in thread
From: sergiodj+buildbot @ 2015-02-26 12:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f57347efc0338cf65539f965f171a318c4a4e523 ***

Author: Joel Brobecker <brobecker@adacore.com>
Branch: gdb-7.9-branch
Commit: f57347efc0338cf65539f965f171a318c4a4e523

Remove // comment in gdb/iq2000-tdep.c
gdb/ChangeLog:

	PR build/18033:
	* iq2000-tdep.c (iq2000_frame_cache): Delete C++-style comment.


^ permalink raw reply	[flat|nested] 36+ messages in thread
* Test results for commit c9ae55c9597064a8fe9a20899a17a394ac4ee3f8 on branch gdb-7.9-branch
@ 2015-02-20 19:31 sergiodj
  2015-02-20 20:14 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj
  0 siblings, 1 reply; 36+ messages in thread
From: sergiodj @ 2015-02-20 19:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c9ae55c9597064a8fe9a20899a17a394ac4ee3f8 ***

Author: Joel Brobecker <brobecker@adacore.com>
Branch: gdb-7.9-branch
Commit: c9ae55c9597064a8fe9a20899a17a394ac4ee3f8

Bump GDB version number to 7.9.0.DATE-cvs.
gdb/ChangeLog:

	* version.in: Set GDB version number to 7.9.0.DATE-cvs.


^ permalink raw reply	[flat|nested] 36+ messages in thread
* Test results for commit 1435f081d10098b0bff7e30273c1c2611c35c4f9 on branch gdb-7.9-branch
@ 2015-02-20 18:08 sergiodj
  2015-02-20 18:47 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj
  0 siblings, 1 reply; 36+ messages in thread
From: sergiodj @ 2015-02-20 18:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1435f081d10098b0bff7e30273c1c2611c35c4f9 ***

Author: Joel Brobecker <brobecker@adacore.com>
Branch: gdb-7.9-branch
Commit: 1435f081d10098b0bff7e30273c1c2611c35c4f9

Document the GDB 7.9 release in gdb/ChangeLog
gdb/ChangeLog:

	GDB 7.9 released.


^ permalink raw reply	[flat|nested] 36+ messages in thread
* Test results for commit 3b7a39661610038aad32563069b10fb2cfc55fab on branch gdb-7.9-branch
@ 2015-02-20  4:06 sergiodj
  2015-02-20  4:52 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj
  0 siblings, 1 reply; 36+ messages in thread
From: sergiodj @ 2015-02-20  4:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3b7a39661610038aad32563069b10fb2cfc55fab ***

Author: Andreas Arnez <arnez@linux.vnet.ibm.com>
Branch: gdb-7.9-branch
Commit: 3b7a39661610038aad32563069b10fb2cfc55fab

Fix internal error when core file section is too big
As reported in PR 17808, a test case with a forged (invalid) core file
can crash GDB with an assertion failure.  In that particular case the
prstatus of an i386 core file looks like that from an AMD64 core file.
Consequently the respective regset supply function i386_supply_gregset
is invoked with a larger buffer than usual.  But i386_supply_gregset
asserts a specific buffer size, and this assertion fails.

The patch relaxes all buffer size assertions in regset supply
functions such that they merely check for a sufficiently large buffer.
For consistency the regset collect functions are adjusted as well.

gdb/ChangeLog:

	PR corefiles/17808:
	* gdbarch.sh (iterate_over_regset_sections_cb): Document this
	function type, particularly its SIZE parameter.
	* gdbarch.h: Regenerate.
	* amd64-tdep.c (amd64_supply_fpregset): In gdb_assert, compare
	actual against required size using ">=" instead of "==".
	(amd64_collect_fpregset): Likewise.
	* i386-tdep.c (i386_supply_gregset): Likewise.
	(i386_collect_gregset): Likewise.
	(i386_supply_fpregset): Likewise.
	(i386_collect_fpregset): Likewise.
	* mips-linux-tdep.c (mips_supply_gregset_wrapper): Likewise.
	(mips_fill_gregset_wrapper): Likewise.
	(mips_supply_fpregset_wrapper): Likewise.
	(mips_fill_fpregset_wrapper): Likewise.
	(mips64_supply_gregset_wrapper): Likewise.
	(mips64_fill_gregset_wrapper): Likewise.
	(mips64_supply_fpregset_wrapper): Likewise.
	(mips64_fill_fpregset_wrapper): Likewise.
	* mn10300-linux-tdep.c (am33_supply_gregset_method): Likewise.
	(am33_supply_fpregset_method): Likewise.
	(am33_collect_gregset_method): Likewise.
	(am33_collect_fpregset_method): Likewise.


^ permalink raw reply	[flat|nested] 36+ messages in thread
* Test results for commit 3b41352824ddc32dabca2d3281a03b4a0b8c7a27 on branch gdb-7.9-branch
@ 2015-02-19 15:26 sergiodj
  2015-02-19 16:09 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj
  0 siblings, 1 reply; 36+ messages in thread
From: sergiodj @ 2015-02-19 15:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3b41352824ddc32dabca2d3281a03b4a0b8c7a27 ***

Author: Joel Brobecker <brobecker@adacore.com>
Branch: gdb-7.9-branch
Commit: 3b41352824ddc32dabca2d3281a03b4a0b8c7a27

Fix the gdb version number ("7.9" instead of "str 7.9").
This fixes an obvious error in the previous change to this file.

gdb/ChangeLog:

        * version.in: Change to "7.9" instead of "str 7.9".


^ permalink raw reply	[flat|nested] 36+ messages in thread
* Test results for commit 77ef543e9e7861214232c63c960eddf19674cf61 on branch gdb-7.9-branch
@ 2015-02-19 14:13 sergiodj
  2015-02-19 15:05 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj
  0 siblings, 1 reply; 36+ messages in thread
From: sergiodj @ 2015-02-19 14:13 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 77ef543e9e7861214232c63c960eddf19674cf61 ***

Author: Joel Brobecker <brobecker@adacore.com>
Branch: gdb-7.9-branch
Commit: 77ef543e9e7861214232c63c960eddf19674cf61

Set GDB version number to str 7.9.
gdb/ChangeLog:

	* version.in: Set GDB version number to str 7.9.


^ permalink raw reply	[flat|nested] 36+ messages in thread
* Test results for commit 90ca3b45da1c08eff31605b2af7cec9979a95bde on branch gdb-7.9-branch
@ 2015-02-19 13:35 sergiodj
  2015-02-19 13:46 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj
  0 siblings, 1 reply; 36+ messages in thread
From: sergiodj @ 2015-02-19 13:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 90ca3b45da1c08eff31605b2af7cec9979a95bde ***

Author: Joel Brobecker <brobecker@adacore.com>
Branch: gdb-7.9-branch
Commit: 90ca3b45da1c08eff31605b2af7cec9979a95bde

gdb/NEWS: "Changes since GDB 7.8" -> "Changes in GDB 7.9".
gdb/ChangeLog:

        * NEWS: Rewrite "Changes since GDB 7.8" into "Changes in GDB 7.9".


^ permalink raw reply	[flat|nested] 36+ messages in thread
* Test results for commit 5991bec1d4dbd23b476dc90bc6d1ba70e044898e on branch gdb-7.9-branch
@ 2015-02-17 15:08 sergiodj
  2015-02-17 15:37 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj
  0 siblings, 1 reply; 36+ messages in thread
From: sergiodj @ 2015-02-17 15:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5991bec1d4dbd23b476dc90bc6d1ba70e044898e ***

Author: Pedro Alves <palves@redhat.com>
Branch: gdb-7.9-branch
Commit: 5991bec1d4dbd23b476dc90bc6d1ba70e044898e

Simplify event-loop core, remove two-step event processing
Even with the previous patch installed, we'll still see
sigall-reverse.exp occasionally fail.  The problem is that the event
loop's event handling processing is done in two steps:

 #1 - poll all event sources, and push new event objects to the event
  queue, until all event sources are drained.

 #2 - go through the event queue, processing each event object at a
  time.  For each event, call the associated callback, and deletes the
  event object from the queue.

and then bad things happen if between #1 and #2 something decides that
events from an event source that has already queued events shouldn't
be processed yet.  To do that, we either remove the event source from
the list of event sources, or clear its "have events" flag.  However,
if an event for that source has meanwhile already been pushed in the
event queue, #2 will still process it and call the associated
callback...

One way to fix it that I considered was to do something to the event
objects already in the event queue when an event source is no longer
interesting.  But then I couldn't find any good reason for the
two-step process in the first place.  It's much simpler (and less
code) to call the event source callbacks as we poll the sources and
find events.

Tested on x86-64 Fedora 20, native and gdbserver.

gdb/
2015-02-17  Pedro Alves  <palves@redhat.com>

	* event-loop.c: Don't declare nor define a queue type for
	gdb_event_p.
	(event_queue): Delete.
	(create_event, create_file_event, gdb_event_xfree)
	(initialize_event_loop, process_event): Delete.
	(gdb_do_one_event): Return as soon as one event is handled.
	(handle_file_event): Change prototype.  Used the passed in
	file_handler pointer and ready_mask instead of looping over all
	file handlers.
	(gdb_wait_for_event): Update the poll/select timeouts before
	blocking.  Run event handlers directly instead of queueing events.
	Return as soon as one event is handled.
	(struct async_event_handler_data): Delete.
	(invoke_async_event_handler): Delete.
	(check_async_event_handlers): Change return type to int.  Run
	event handlers directly instead of queueing events.  Return as
	soon as one event is handled.
	(handle_timer_event): Delete.
	(update_wait_timeout): New function, factored out from
	poll_timers.
	(poll_timers): Reimplement.
	* event-loop.h (initialize_event_loop): Delete declaration.
	* top.c (gdb_init): Don't call initialize_event_loop.


^ permalink raw reply	[flat|nested] 36+ messages in thread
* Test results for commit 140e2c62fd7a46b4500dbd442964543587c0337b on branch gdb-7.9-branch
@ 2015-02-17 12:43 sergiodj
  2015-02-17 13:12 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj
  0 siblings, 1 reply; 36+ messages in thread
From: sergiodj @ 2015-02-17 12:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 140e2c62fd7a46b4500dbd442964543587c0337b ***

Author: Pedro Alves <palves@redhat.com>
Branch: gdb-7.9-branch
Commit: 140e2c62fd7a46b4500dbd442964543587c0337b

Fix up some target is-async vs can-async confusions
In all these cases we're interested in whether the target is currently
async, with its event sources installed in the event loop, not whether
it can async if needed.  Also, I'm not seeing the point of the
target_async call from within linux_nat_wait.  That's normally done on
resume instead, which this target already does.

Tested on x86_64 Fedora 20, native and gdbserver.

gdb/
2015-02-17  Pedro Alves  <palves@redhat.com>

	* linux-nat.c (linux_child_follow_fork, linux_nat_wait_1): Use
	target_is_async_p instead of target_can_async.
	(linux_nat_wait): Use target_is_async_p instead of
	target_can_async.  Don't enable async here.
	* remote.c (interrupt_query, remote_wait, putpkt_binary): Use
	target_is_async_p instead of target_can_async.


^ permalink raw reply	[flat|nested] 36+ messages in thread
* Test results for commit 211e7f3c26b39159df2dedd8198148cec60307f9 on branch gdb-7.9-branch
@ 2015-02-11 17:07 sergiodj
  2015-02-12  9:39 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj
  0 siblings, 1 reply; 36+ messages in thread
From: sergiodj @ 2015-02-11 17:07 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 211e7f3c26b39159df2dedd8198148cec60307f9 ***

Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Branch: gdb-7.9-branch
Commit: 211e7f3c26b39159df2dedd8198148cec60307f9

framefilter quit: New test
It definitely does not test all the RETURN_MASK_ERROR cases.  But it tests at
least two of them.

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

	* gdb.python/py-framefilter.exp (pagination quit - *): New tests.


^ permalink raw reply	[flat|nested] 36+ messages in thread
* Test results for commit cf3f71d273c607ecd1e912ce9fe8121da320c6a9 on branch gdb-7.9-branch
@ 2015-02-11 16:34 sergiodj
  2015-02-12  7:47 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj
  0 siblings, 1 reply; 36+ messages in thread
From: sergiodj @ 2015-02-11 16:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cf3f71d273c607ecd1e912ce9fe8121da320c6a9 ***

Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Branch: gdb-7.9-branch
Commit: cf3f71d273c607ecd1e912ce9fe8121da320c6a9

framefilter quit: Use RETURN_MASK_ERROR
Now when the code is exception safe we can let RETURN_QUIT to pass through as
all the installed cleanups with handle that.

gdb/ChangeLog
2015-02-11  Jan Kratochvil  <jan.kratochvil@redhat.com>

	* python/py-framefilter.c (py_print_single_arg, enumerate_locals)
	(py_print_frame): Use RETURN_MASK_ERROR.


^ permalink raw reply	[flat|nested] 36+ messages in thread
* Test results for commit 5dea9fe2285fee5d53691856750a0c8960fca04d on branch gdb-7.9-branch
@ 2015-02-11 15:42 sergiodj
  2015-02-12  3:55 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj
  0 siblings, 1 reply; 36+ messages in thread
From: sergiodj @ 2015-02-11 15:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5dea9fe2285fee5d53691856750a0c8960fca04d ***

Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Branch: gdb-7.9-branch
Commit: 5dea9fe2285fee5d53691856750a0c8960fca04d

framefilter quit: Make it exception safe
gdb/ChangeLog
2015-02-11  Jan Kratochvil  <jan.kratochvil@redhat.com>

	* python/py-framefilter.c (py_print_frame): Mention RETURN_QUIT in
	function comment.  Wrap all function that can throw in cleanups.
	(gdbpy_apply_frame_filter): Wrap all function that can throw in
	cleanups.


^ permalink raw reply	[flat|nested] 36+ messages in thread
* Test results for commit 46d020960241fcafd7d0ab483746a206829620ea on branch gdb-7.9-branch
@ 2015-02-11 15:19 sergiodj
  2015-02-12  2:39 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj
  0 siblings, 1 reply; 36+ messages in thread
From: sergiodj @ 2015-02-11 15:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 46d020960241fcafd7d0ab483746a206829620ea ***

Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Branch: gdb-7.9-branch
Commit: 46d020960241fcafd7d0ab483746a206829620ea

framefilter quit: Code cleanup: Avoid gotos
goto error patters are sometimes AFAIK used in C for the cases like:
	int retval=-1;
	if (!(a=malloc())) goto error;
	if (!(b=malloc())) goto error_a;
	if (!(c=malloc())) goto error_b;
	retval=0;
	error_c: free(c);
	error_b: free(b);
	error_a: free(a);
	error: return retval;

But here there is single error label with one do_cleanups() which I do not find
it worth the goto complication.  Without goto one can then furher merge code in
the exit paths in the next patches and ... after all it is all the same, just
without a goto.

gdb/ChangeLog
2015-02-11  Jan Kratochvil  <jan.kratochvil@redhat.com>

	* python/py-framefilter.c (py_print_frame): Substitute goto error.
	Remove the error label.


^ permalink raw reply	[flat|nested] 36+ messages in thread
* Test results for commit a9189a245363137825ce02a23202df45b04db179 on branch gdb-7.9-branch
@ 2015-02-11 14:32 sergiodj
  2015-02-12  0:18 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj
  0 siblings, 1 reply; 36+ messages in thread
From: sergiodj @ 2015-02-11 14:32 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a9189a245363137825ce02a23202df45b04db179 ***

Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Branch: gdb-7.9-branch
Commit: a9189a245363137825ce02a23202df45b04db179

framefilter quit: Code cleanup: Reindentation
Nothing significant but I find code more clear with less deep indentation.

gdb/ChangeLog
2015-02-11  Jan Kratochvil  <jan.kratochvil@redhat.com>

	* python/py-framefilter.c (py_print_frame): Put conditional code paths
	with goto first, indent the former else codepath left.  Put variable
	'elided' to a new inner block.


^ permalink raw reply	[flat|nested] 36+ messages in thread
* Test results for commit 25a0672ba8b7f4badc682eaf08a1e342b496b483 on branch gdb-7.9-branch
@ 2015-02-11 14:04 sergiodj
  2015-02-11 20:57 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj
  0 siblings, 1 reply; 36+ messages in thread
From: sergiodj @ 2015-02-11 14:04 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 25a0672ba8b7f4badc682eaf08a1e342b496b483 ***

Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Branch: gdb-7.9-branch
Commit: 25a0672ba8b7f4badc682eaf08a1e342b496b483

framefilter quit: Obvious whitespacing fixes
gdb/ChangeLog
2015-02-11  Jan Kratochvil  <jan.kratochvil@redhat.com>

	* python/py-framefilter.c (py_print_frame): Whitespacing fixes.


^ permalink raw reply	[flat|nested] 36+ messages in thread
* Failures on Fedora-ppc64be-native-gdbserver-m64, branch gdb-7.9-branch
@ 2015-02-05  1:25 sergiodj
  0 siblings, 0 replies; 36+ messages in thread
From: sergiodj @ 2015-02-05  1:25 UTC (permalink / raw)
  To: gdb-testers

Buildslave:
	fedora-21-ppc64be-2

Full Build URL:
	<http://gdb-build.sergiodj.net/builders/Fedora-ppc64be-native-gdbserver-m64/builds/73>

Commit(s) tested:
	2b7d5144a58e63cb9517f6a8b31dd7c5e05a7ffe

Author(s) (in the same order as the commits):
	Doug Evans <dje@google.com>

Testsuite log (gdb.sum and gdb.log) URL(s):
	<http://gdb-build.sergiodj.net/cgit/Fedora-ppc64be-native-gdbserver-m64/.git/tree/?h=gdb-7.9-branch&id=ce4c29927a36f6c105a1ed064a6231e13fef70f4>

*** Regressions found ***
============================
PASS -> FAIL: gdb.ada/str_uninit.exp: print my_str
PASS -> FAIL: gdb.base/break-idempotent.exp: always-inserted off: awatch: twice: awatch global
PASS -> FAIL: gdb.base/break-idempotent.exp: always-inserted off: rwatch: twice: rwatch global
new FAIL: gdb.base/break-idempotent.exp: always-inserted on: awatch: twice: awatch global
new FAIL: gdb.base/break-idempotent.exp: always-inserted on: rwatch: twice: rwatch global
new FAIL: gdb.base/gdb-sigterm.exp: expect eof #1 (stepping inside range 201 times)
new FAIL: gdb.base/gdb-sigterm.exp: expect eof #10 (stepping inside range 201 times)
new FAIL: gdb.base/gdb-sigterm.exp: expect eof #11 (stepping inside range 201 times)
new FAIL: gdb.base/gdb-sigterm.exp: expect eof #12 (stepping inside range 201 times)
new FAIL: gdb.base/gdb-sigterm.exp: expect eof #20 (stepping inside range 201 times)
new FAIL: gdb.base/gdb-sigterm.exp: expect eof #26 (stepping inside range 201 times)
new FAIL: gdb.base/gdb-sigterm.exp: expect eof #35 (stepping inside range 201 times)
new FAIL: gdb.base/gdb-sigterm.exp: expect eof #36 (stepping inside range 201 times)
new FAIL: gdb.base/gdb-sigterm.exp: expect eof #37 (stepping inside range 201 times)
new FAIL: gdb.base/gdb-sigterm.exp: expect eof #38 (stepping inside range 201 times)
new FAIL: gdb.base/gdb-sigterm.exp: expect eof #39 (stepping inside range 201 times)
new FAIL: gdb.base/gdb-sigterm.exp: expect eof #40 (stepping inside range 201 times)
new FAIL: gdb.base/gdb-sigterm.exp: expect eof #43 (stepping inside range 201 times)
new FAIL: gdb.base/gdb-sigterm.exp: expect eof #44 (stepping inside range 201 times)
new FAIL: gdb.base/gdb-sigterm.exp: expect eof #47 (stepping inside range 201 times)
new FAIL: gdb.base/solib-search.exp: backtrace (with wrong libs)
new FAIL: gdb.cp/annota2.exp: annotate-quit
new FAIL: gdb.cp/annota2.exp: watch triggered on a.x (timeout)
new FAIL: gdb.mi/mi-watch-nonstop.exp: delete watchpoint
new FAIL: gdb.mi/pr11022.exp: data-write-memory-bytes &x "01": watchpoint hit 2 (unknown output after running)
new FAIL: gdb.threads/watchpoint-fork.exp: child: multithreaded: breakpoint (A) after the first fork (GDB internal error)
new FAIL: gdb.threads/watchpoint-fork.exp: child: multithreaded: breakpoint (A) after the second fork
new FAIL: gdb.threads/watchpoint-fork.exp: child: multithreaded: finish
new FAIL: gdb.threads/watchpoint-fork.exp: child: multithreaded: watchpoint A after the first fork
new FAIL: gdb.threads/watchpoint-fork.exp: child: multithreaded: watchpoint A after the second fork (GDB internal error)
new FAIL: gdb.threads/watchpoint-fork.exp: child: multithreaded: watchpoint B after the first fork
new FAIL: gdb.threads/watchpoint-fork.exp: child: multithreaded: watchpoint B after the second fork
new FAIL: gdb.threads/watchpoint-fork.exp: child: singlethreaded: breakpoint after the first fork (GDB internal error)
new FAIL: gdb.threads/watchpoint-fork.exp: child: singlethreaded: breakpoint after the second fork
new FAIL: gdb.threads/watchpoint-fork.exp: child: singlethreaded: finish
new FAIL: gdb.threads/watchpoint-fork.exp: child: singlethreaded: watchpoint after the first fork
new FAIL: gdb.threads/watchpoint-fork.exp: child: singlethreaded: watchpoint after the second fork (GDB internal error)
new FAIL: gdb.threads/watchpoint-fork.exp: parent: multithreaded: breakpoint (A) after the first fork (GDB internal error)
new FAIL: gdb.threads/watchpoint-fork.exp: parent: multithreaded: breakpoint (A) after the second fork (GDB internal error)
new FAIL: gdb.threads/watchpoint-fork.exp: parent: singlethreaded: breakpoint after the first fork (GDB internal error)
new FAIL: gdb.threads/watchpoint-fork.exp: parent: singlethreaded: breakpoint after the second fork (GDB internal error)
============================




^ permalink raw reply	[flat|nested] 36+ messages in thread
* Failures on Fedora-ppc64be-native-gdbserver-m64, branch gdb-7.9-branch
@ 2015-01-26 16:36 sergiodj
  0 siblings, 0 replies; 36+ messages in thread
From: sergiodj @ 2015-01-26 16:36 UTC (permalink / raw)
  To: gdb-testers

Buildslave:
	fedora-20-ppc64be-1

Full Build URL:
	<http://gdb-build.sergiodj.net/builders/Fedora-ppc64be-native-gdbserver-m64/builds/13>

Commit(s) tested:
	6446dae3969acfffd8bbd779980227439d9c4cbb
	4e1e1ad808e8620d34a0e6da5dba87d5dfb01f59
	1ab1f5f9160f1fce8129820b1c95aa7bb64cc90d
	6c3e7fa837c0885fbf1f5a9203c3cb720d55ab76
	936fc1158df657607b318e05e41a25e600ec3e33

Author(s) (in the same order as the commits):
	Wei-cheng Wang <cole945@gmail.com>
	Wei-cheng Wang <cole945@gmail.com>
	Wei-cheng Wang <cole945@gmail.com>
	Wei-cheng Wang <cole945@gmail.com>
	Wei-cheng Wang <cole945@gmail.com>

Testsuite log (gdb.sum and gdb.log) URL(s):
	<Error fetching commit ID for 936fc1158df657607b318e05e41a25e600ec3e33>

*** Failed to update GDB git repository.  This is probably a timeout problem with sourceware. ***




^ permalink raw reply	[flat|nested] 36+ messages in thread
* Failures on Fedora-ppc64be-native-gdbserver-m64, branch gdb-7.9-branch
@ 2015-01-26  2:24 sergiodj
  0 siblings, 0 replies; 36+ messages in thread
From: sergiodj @ 2015-01-26  2:24 UTC (permalink / raw)
  To: gdb-testers

Buildslave:
	fedora-20-ppc64be-1

Full Build URL:
	<http://gdb-build.sergiodj.net/builders/Fedora-ppc64be-native-gdbserver-m64/builds/8>

Commit(s) tested:
	81d293741a30b144317d97930c7633beeae758fe

Author(s) (in the same order as the commits):
	GDB Administrator <gdbadmin@sourceware.org>

Testsuite log (gdb.sum and gdb.log) URL(s):
	<Error fetching commit ID for 81d293741a30b144317d97930c7633beeae758fe>

*** Failed to update GDB git repository.  This is probably a timeout problem with sourceware. ***




^ permalink raw reply	[flat|nested] 36+ messages in thread
* Failures on Fedora-ppc64be-native-gdbserver-m64, branch gdb-7.9-branch
@ 2015-01-25  8:03 sergiodj
  0 siblings, 0 replies; 36+ messages in thread
From: sergiodj @ 2015-01-25  8:03 UTC (permalink / raw)
  To: gdb-testers

Buildslave:
	fedora-20-ppc64be-1

Full Build URL:
	<http://gdb-build.sergiodj.net/builders/Fedora-ppc64be-native-gdbserver-m64/builds/6>

Commit(s) tested:
	c8f66196de03935d0d0dca7a5e16054262a38561

Author(s) (in the same order as the commits):
	Jan Kratochvil <jan.kratochvil@redhat.com>

Testsuite log (gdb.sum and gdb.log) URL(s):
	<Error fetching commit ID for c8f66196de03935d0d0dca7a5e16054262a38561>

*** Failed to update GDB git repository.  This is probably a timeout problem with sourceware. ***




^ permalink raw reply	[flat|nested] 36+ messages in thread
end of thread, other threads:[~2015-03-31 14:50 UTC | newest]

Thread overview: 36+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-02-20  5:01 Test results for commit 7b582627bc42922de3b75792472f5223f1910277 on branch gdb-7.9-branch sergiodj
2015-02-20  5:21 ` Failures on Fedora-ppc64be-cc-with-index, " sergiodj
2015-02-20  5:43 ` Failures on Fedora-ppc64be-m64, " sergiodj
2015-02-20  6:09 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj
2015-02-20  6:45 ` Failures on Fedora-ppc64be-native-extended-gdbserver-m64, " sergiodj
2015-02-20  8:14 ` Failures on Fedora-ppc64le-native-extended-gdbserver-m64, " sergiodj
2015-02-20  8:22 ` Failures on Fedora-ppc64le-cc-with-index, " sergiodj
2015-02-20  9:25 ` Failures on Fedora-ppc64le-native-gdbserver-m64, " sergiodj
2015-02-20  9:28 ` Failures on Fedora-ppc64le-m64, " sergiodj
2015-02-20  9:32 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj
2015-02-20  9:48 ` Failures on Fedora-x86_64-m64, " sergiodj
2015-02-20  9:50 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj
2015-02-20 10:09 ` Failures on Debian-i686-native-extended-gdbserver, " sergiodj
2015-02-20 17:44 ` Failures on Debian-x86_64-m64, " sergiodj
2015-02-20 17:44 ` Failures on Debian-x86_64-native-gdbserver-m64, " sergiodj
  -- strict thread matches above, loose matches on Subject: below --
2015-03-31 15:30 [binutils-gdb/gdb-7.9-branch] Fix the triplet regexp to recognize triplets, not only quadruplets sergiodj+buildbot
2015-03-31 16:01 ` Failures on Fedora-ppc64be-native-gdbserver-m64, branch gdb-7.9-branch sergiodj+buildbot
2015-02-26 14:38 [binutils-gdb/gdb-7.9-branch] Change // comment in gdb/compile/ sergiodj+buildbot
2015-02-26 14:41 ` Failures on Fedora-ppc64be-native-gdbserver-m64, branch gdb-7.9-branch sergiodj+buildbot
2015-02-26 12:11 [binutils-gdb/gdb-7.9-branch] Remove // comment in gdb/iq2000-tdep.c sergiodj+buildbot
2015-02-26 12:22 ` Failures on Fedora-ppc64be-native-gdbserver-m64, branch gdb-7.9-branch sergiodj+buildbot
2015-02-20 19:31 Test results for commit c9ae55c9597064a8fe9a20899a17a394ac4ee3f8 on " sergiodj
2015-02-20 20:14 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj
2015-02-20 18:08 Test results for commit 1435f081d10098b0bff7e30273c1c2611c35c4f9 on " sergiodj
2015-02-20 18:47 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj
2015-02-20  4:06 Test results for commit 3b7a39661610038aad32563069b10fb2cfc55fab on " sergiodj
2015-02-20  4:52 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj
2015-02-19 15:26 Test results for commit 3b41352824ddc32dabca2d3281a03b4a0b8c7a27 on " sergiodj
2015-02-19 16:09 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj
2015-02-19 14:13 Test results for commit 77ef543e9e7861214232c63c960eddf19674cf61 on " sergiodj
2015-02-19 15:05 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj
2015-02-19 13:35 Test results for commit 90ca3b45da1c08eff31605b2af7cec9979a95bde on " sergiodj
2015-02-19 13:46 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj
2015-02-17 15:08 Test results for commit 5991bec1d4dbd23b476dc90bc6d1ba70e044898e on " sergiodj
2015-02-17 15:37 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj
2015-02-17 12:43 Test results for commit 140e2c62fd7a46b4500dbd442964543587c0337b on " sergiodj
2015-02-17 13:12 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj
2015-02-11 17:07 Test results for commit 211e7f3c26b39159df2dedd8198148cec60307f9 on " sergiodj
2015-02-12  9:39 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj
2015-02-11 16:34 Test results for commit cf3f71d273c607ecd1e912ce9fe8121da320c6a9 on " sergiodj
2015-02-12  7:47 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj
2015-02-11 15:42 Test results for commit 5dea9fe2285fee5d53691856750a0c8960fca04d on " sergiodj
2015-02-12  3:55 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj
2015-02-11 15:19 Test results for commit 46d020960241fcafd7d0ab483746a206829620ea on " sergiodj
2015-02-12  2:39 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj
2015-02-11 14:32 Test results for commit a9189a245363137825ce02a23202df45b04db179 on " sergiodj
2015-02-12  0:18 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj
2015-02-11 14:04 Test results for commit 25a0672ba8b7f4badc682eaf08a1e342b496b483 on " sergiodj
2015-02-11 20:57 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj
2015-02-05  1:25 sergiodj
2015-01-26 16:36 sergiodj
2015-01-26  2:24 sergiodj
2015-01-25  8:03 sergiodj

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).