[BuildBot] Notifications disabled for Debian-s390x-* and Fedora-ppc64*-* builders

[BuildBot] Notifications disabled for Debian-s390x-* and Fedora-ppc64*-* builders

[Sergio Durigan Junior]

Hi there,

This is a small announcemente to let you know that I have disabled
e-mail notifications for a few builders.

All of the Fedora-ppc*-* builders:

  Fedora-ppc64be-m64
  Fedora-ppc64be-native-gdbserver-m64
  Fedora-ppc64be-native-extended-gdbserver-m64
  Fedora-ppc64be-cc-with-index
  Fedora-ppc64le-m64
  Fedora-ppc64le-native-gdbserver-m64
  Fedora-ppc64le-native-extended-gdbserver-m64
  Fedora-ppc64le-cc-with-index

All of the Debian-s390x-* builders:

  Debian-s390x-m64
  Debian-s390x-native-gdbserver-m64
  Debian-s390x-native-extended-gdbserver-m64

I have also removed them from the list of Try Builders, so if you use
the try build, please update your config file.  An updated list can be
found here:

  <https://sourceware.org/gdb/wiki/BuildBot#Available_Builders>

I took this decision after noticing that these builders have been
lagging behind for quite some time.  Some of them have more than 900
queued builds!

I've been talking with Edjunior Machado about the PPC64* machines.
Unfortunately it appears that Minicloud, the project that provided the
machines, is going through some difficulties right now.  We're now
investigating the possibility to move these resources to the GCC Compile
Farm.

As for the s390x machine, I haven't had the chance to investigate
further what is happening.

I would like to take this opportunity to invite more people/companies to
join our BuildBot effort!  There's always opportunity for improvement,
and we're always looking for more machines and architectures to add to
our infrastructure.  If you have interest, please get in touch (in
private) with me and we'll get the ball rolling.

Thanks,

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/

Re: [BuildBot] Notifications disabled for Debian-s390x-* and Fedora-ppc64*-* builders

[David Edelsohn]

On Fri, Dec 15, 2017 at 8:45 AM, Sergio Durigan Junior
<sergiodj@redhat.com> wrote:
> Hi there,
>
> This is a small announcemente to let you know that I have disabled
> e-mail notifications for a few builders.
>
> All of the Fedora-ppc*-* builders:
>
>   Fedora-ppc64be-m64
>   Fedora-ppc64be-native-gdbserver-m64
>   Fedora-ppc64be-native-extended-gdbserver-m64
>   Fedora-ppc64be-cc-with-index
>   Fedora-ppc64le-m64
>   Fedora-ppc64le-native-gdbserver-m64
>   Fedora-ppc64le-native-extended-gdbserver-m64
>   Fedora-ppc64le-cc-with-index
>
> All of the Debian-s390x-* builders:
>
>   Debian-s390x-m64
>   Debian-s390x-native-gdbserver-m64
>   Debian-s390x-native-extended-gdbserver-m64
>
> I have also removed them from the list of Try Builders, so if you use
> the try build, please update your config file.  An updated list can be
> found here:
>
>   <https://sourceware.org/gdb/wiki/BuildBot#Available_Builders>
>
> I took this decision after noticing that these builders have been
> lagging behind for quite some time.  Some of them have more than 900
> queued builds!
>
> I've been talking with Edjunior Machado about the PPC64* machines.
> Unfortunately it appears that Minicloud, the project that provided the
> machines, is going through some difficulties right now.  We're now
> investigating the possibility to move these resources to the GCC Compile
> Farm.
>
> As for the s390x machine, I haven't had the chance to investigate
> further what is happening.
>
> I would like to take this opportunity to invite more people/companies to
> join our BuildBot effort!  There's always opportunity for improvement,
> and we're always looking for more machines and architectures to add to
> our infrastructure.  If you have interest, please get in touch (in
> private) with me and we'll get the ball rolling.

This decision is beyond stupid and completely negates the purpose of
the buildbots.  GDB testsuite now requieres 9 hours to complete on
s390x.  Something is fundamentally broken.  Instead of the GDB
community noticing the issue, investigating, and fixing, it chooses to
ignore the problem.

And yet you ask for more companies to participate and contribute build
bots. Why should any company participate when the response is pathetic
and issues that the buildbots raise are ignored?  Companies should not
participate until the GDB community shows some interest in utilizing
and showing appreciation for the valuable resources contributed to the
program.  Otherwise this is just a vanity project for Sergio  with no
real benefit to the stability of GDB on the architectures, nor to the
companies.

Thanks, David

Re: [BuildBot] Notifications disabled for Debian-s390x-* and Fedora-ppc64*-* builders

[Sergio Durigan Junior]

On Friday, December 15 2017, David Edelsohn wrote:

> On Fri, Dec 15, 2017 at 8:45 AM, Sergio Durigan Junior
> <sergiodj@redhat.com> wrote:
>> Hi there,
>>
>> This is a small announcemente to let you know that I have disabled
>> e-mail notifications for a few builders.
>>
>> All of the Fedora-ppc*-* builders:
>>
>>   Fedora-ppc64be-m64
>>   Fedora-ppc64be-native-gdbserver-m64
>>   Fedora-ppc64be-native-extended-gdbserver-m64
>>   Fedora-ppc64be-cc-with-index
>>   Fedora-ppc64le-m64
>>   Fedora-ppc64le-native-gdbserver-m64
>>   Fedora-ppc64le-native-extended-gdbserver-m64
>>   Fedora-ppc64le-cc-with-index
>>
>> All of the Debian-s390x-* builders:
>>
>>   Debian-s390x-m64
>>   Debian-s390x-native-gdbserver-m64
>>   Debian-s390x-native-extended-gdbserver-m64
>>
>> I have also removed them from the list of Try Builders, so if you use
>> the try build, please update your config file.  An updated list can be
>> found here:
>>
>>   <https://sourceware.org/gdb/wiki/BuildBot#Available_Builders>
>>
>> I took this decision after noticing that these builders have been
>> lagging behind for quite some time.  Some of them have more than 900
>> queued builds!
>>
>> I've been talking with Edjunior Machado about the PPC64* machines.
>> Unfortunately it appears that Minicloud, the project that provided the
>> machines, is going through some difficulties right now.  We're now
>> investigating the possibility to move these resources to the GCC Compile
>> Farm.
>>
>> As for the s390x machine, I haven't had the chance to investigate
>> further what is happening.
>>
>> I would like to take this opportunity to invite more people/companies to
>> join our BuildBot effort!  There's always opportunity for improvement,
>> and we're always looking for more machines and architectures to add to
>> our infrastructure.  If you have interest, please get in touch (in
>> private) with me and we'll get the ball rolling.
>
> This decision is beyond stupid and completely negates the purpose of
> the buildbots.  GDB testsuite now requieres 9 hours to complete on
> s390x.  Something is fundamentally broken.  Instead of the GDB
> community noticing the issue, investigating, and fixing, it chooses to
> ignore the problem.

Hi David,

Perhaps I should have explained better.  The only thing that I did was
to disable the email notifications, that's all.  The builders are still
going to keep building the commits, and the results are still going to
be displayed in the website.  This is hopefully a temporary action to
avoid the report of false positives (like we're seeing with PPC64BE, for
example), and to give us more time to investigate what is going on with
the machines/GDB and take necessary actions.

> And yet you ask for more companies to participate and contribute build
> bots. Why should any company participate when the response is pathetic
> and issues that the buildbots raise are ignored?  Companies should not
> participate until the GDB community shows some interest in utilizing
> and showing appreciation for the valuable resources contributed to the
> program.  Otherwise this is just a vanity project for Sergio  with no
> real benefit to the stability of GDB on the architectures, nor to the
> companies.

I find this part very offensive.  Even though I run the BuildBot with my
own resources, I cannot keep track of all the failures that happen all
the time, and I also cannot monitor the machines attached to the
BuildBot master.  What I try to do is to look, from time to time, at the
status of each buildslave and get in touch with the owner of the machine
if there's something strange.  This is not the first time I have had to
disable e-mail notifications for specific builders, for example.  So
far, we managed to solve all the problems that appeared with the
buildslaves.  I hope we can keep working together and doing that.

Our BuildBot sends the testsuite reports to the gdb-testers mailing
list.  It is somewhat hard to keep track of the messages there, but it
would be good if we had more eyes looking at the list.  Aside from that,
I consider that the Try Builds and the breakage emails are nice features
that have helped us.

So yeah, it would be good to see more people interested in the project.
I personally don't consider this a vanity project, but by all means, if
the community doesn't see value in this then please tell me, because I
certainly could find other uses for the resources I dedicate to this.

Cheers,

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/

Re: [BuildBot] Notifications disabled for Debian-s390x-* and Fedora-ppc64*-* builders

[David Edelsohn]

On Fri, Dec 15, 2017 at 9:20 AM, Sergio Durigan Junior
<sergiodj@redhat.com> wrote:
> On Friday, December 15 2017, David Edelsohn wrote:
>
>> On Fri, Dec 15, 2017 at 8:45 AM, Sergio Durigan Junior
>> <sergiodj@redhat.com> wrote:
>>> Hi there,
>>>
>>> This is a small announcemente to let you know that I have disabled
>>> e-mail notifications for a few builders.
>>>
>>> All of the Fedora-ppc*-* builders:
>>>
>>>   Fedora-ppc64be-m64
>>>   Fedora-ppc64be-native-gdbserver-m64
>>>   Fedora-ppc64be-native-extended-gdbserver-m64
>>>   Fedora-ppc64be-cc-with-index
>>>   Fedora-ppc64le-m64
>>>   Fedora-ppc64le-native-gdbserver-m64
>>>   Fedora-ppc64le-native-extended-gdbserver-m64
>>>   Fedora-ppc64le-cc-with-index
>>>
>>> All of the Debian-s390x-* builders:
>>>
>>>   Debian-s390x-m64
>>>   Debian-s390x-native-gdbserver-m64
>>>   Debian-s390x-native-extended-gdbserver-m64
>>>
>>> I have also removed them from the list of Try Builders, so if you use
>>> the try build, please update your config file.  An updated list can be
>>> found here:
>>>
>>>   <https://sourceware.org/gdb/wiki/BuildBot#Available_Builders>
>>>
>>> I took this decision after noticing that these builders have been
>>> lagging behind for quite some time.  Some of them have more than 900
>>> queued builds!
>>>
>>> I've been talking with Edjunior Machado about the PPC64* machines.
>>> Unfortunately it appears that Minicloud, the project that provided the
>>> machines, is going through some difficulties right now.  We're now
>>> investigating the possibility to move these resources to the GCC Compile
>>> Farm.
>>>
>>> As for the s390x machine, I haven't had the chance to investigate
>>> further what is happening.
>>>
>>> I would like to take this opportunity to invite more people/companies to
>>> join our BuildBot effort!  There's always opportunity for improvement,
>>> and we're always looking for more machines and architectures to add to
>>> our infrastructure.  If you have interest, please get in touch (in
>>> private) with me and we'll get the ball rolling.
>>
>> This decision is beyond stupid and completely negates the purpose of
>> the buildbots.  GDB testsuite now requieres 9 hours to complete on
>> s390x.  Something is fundamentally broken.  Instead of the GDB
>> community noticing the issue, investigating, and fixing, it chooses to
>> ignore the problem.
>
> Hi David,
>
> Perhaps I should have explained better.  The only thing that I did was
> to disable the email notifications, that's all.  The builders are still
> going to keep building the commits, and the results are still going to
> be displayed in the website.  This is hopefully a temporary action to
> avoid the report of false positives (like we're seeing with PPC64BE, for
> example), and to give us more time to investigate what is going on with
> the machines/GDB and take necessary actions.
>
>> And yet you ask for more companies to participate and contribute build
>> bots. Why should any company participate when the response is pathetic
>> and issues that the buildbots raise are ignored?  Companies should not
>> participate until the GDB community shows some interest in utilizing
>> and showing appreciation for the valuable resources contributed to the
>> program.  Otherwise this is just a vanity project for Sergio  with no
>> real benefit to the stability of GDB on the architectures, nor to the
>> companies.
>
> I find this part very offensive.  Even though I run the BuildBot with my
> own resources, I cannot keep track of all the failures that happen all
> the time, and I also cannot monitor the machines attached to the
> BuildBot master.  What I try to do is to look, from time to time, at the
> status of each buildslave and get in touch with the owner of the machine
> if there's something strange.  This is not the first time I have had to
> disable e-mail notifications for specific builders, for example.  So
> far, we managed to solve all the problems that appeared with the
> buildslaves.  I hope we can keep working together and doing that.
>
> Our BuildBot sends the testsuite reports to the gdb-testers mailing
> list.  It is somewhat hard to keep track of the messages there, but it
> would be good if we had more eyes looking at the list.  Aside from that,
> I consider that the Try Builds and the breakage emails are nice features
> that have helped us.
>
> So yeah, it would be good to see more people interested in the project.
> I personally don't consider this a vanity project, but by all means, if
> the community doesn't see value in this then please tell me, because I
> certainly could find other uses for the resources I dedicate to this.

Sergio,

I believe that the GDB buildbots should be useful to the GDB community
and I appreciate your efforts to maintain it.

But the irony in your message should not be ignored.  You implicitly
express that the buildbots are ignored, except possibly x86 and Try
Builds on x86, while you proceed to ask for additional participation.
This is fundamentally inconsistent.  Actions speak louder than words
and this demonstrates the priorities of the GDB community.

Thanks, David

Re: [BuildBot] Notifications disabled for Debian-s390x-* and Fedora-ppc64*-* builders

[Pedro Alves]

On 12/15/2017 02:34 PM, David Edelsohn wrote:

> I believe that the GDB buildbots should be useful to the GDB community
> and I appreciate your efforts to maintain it.
> 
> But the irony in your message should not be ignored.  You implicitly
> express that the buildbots are ignored, except possibly x86 and Try
> Builds on x86, while you proceed to ask for additional participation.
> This is fundamentally inconsistent.  Actions speak louder than words
> and this demonstrates the priorities of the GDB community.

I think there must be some misunderstanding here.  IIUC, the problem with
the builders is not related at all to the quality of the PPC64 or s390
gdb ports.  The problems are something else beyond GDB's control, they're
network, oversubscription, etc. problems, something like that.  The builder
machines have simply not been able to exercise their basic function stably
enough, in turn causing problems for developers, instead of helping.  What
can the community, as in, GDB maintainers, do, then?  I for one have no
idea what I (just a developer) can do here.  I think that the best course
of action is to disable reporting while investigations proceed, which I
understood it being exactly what is being done here.  I don't think
Sergio deserved the reaction.

Thanks,
Pedro Alves

Re: [BuildBot] Notifications disabled for Debian-s390x-* and Fedora-ppc64*-* builders

[David Edelsohn]

On Fri, Dec 15, 2017 at 9:48 AM, Pedro Alves <palves@redhat.com> wrote:
> On 12/15/2017 02:34 PM, David Edelsohn wrote:
>
>> I believe that the GDB buildbots should be useful to the GDB community
>> and I appreciate your efforts to maintain it.
>>
>> But the irony in your message should not be ignored.  You implicitly
>> express that the buildbots are ignored, except possibly x86 and Try
>> Builds on x86, while you proceed to ask for additional participation.
>> This is fundamentally inconsistent.  Actions speak louder than words
>> and this demonstrates the priorities of the GDB community.
>
> I think there must be some misunderstanding here.  IIUC, the problem with
> the builders is not related at all to the quality of the PPC64 or s390
> gdb ports.  The problems are something else beyond GDB's control, they're
> network, oversubscription, etc. problems, something like that.  The builder
> machines have simply not been able to exercise their basic function stably
> enough, in turn causing problems for developers, instead of helping.  What
> can the community, as in, GDB maintainers, do, then?  I for one have no
> idea what I (just a developer) can do here.  I think that the best course
> of action is to disable reporting while investigations proceed, which I
> understood it being exactly what is being done here.  I don't think
> Sergio deserved the reaction.

This is an incorrect analysis of the problem and the status.

First, a problem with the buildbot that started in September should
not be reported and addressed in December.  That clearly shows that
the community is ignoring the buildbots (at least for targets other
than x86).

Second, the s390 VM is not under-sized and should be equivalent to any
x86 VM running a buildslave.

Third, the testsuite summaries that no one from the GDB community
monitored show that the testsuite runtime jumped from a relatively
short amount of time to over 9 hours for each run, which points to a
newly introduced problem in GDB or in the testsuite (timeouts?).

Fourth, the same s390 VM runs buildbots for other projects, such as
Python, that were not adversely affected and have not seen a huge jump
in cycle time or delays.

Again, everything points to a problem in GDB, its testsuite, or its
infrastructure, not in the buildslave.  Yes, it's ironic to announce
that annoying warning emails of problems will not be ignored while
asking for more resources and participation.

Thanks, David

Re: [BuildBot] Notifications disabled for Debian-s390x-* and Fedora-ppc64*-* builders

[Pedro Alves]

On 12/15/2017 03:06 PM, David Edelsohn wrote:

> Third, the testsuite summaries that no one from the GDB community
> monitored show that the testsuite runtime jumped from a relatively
> short amount of time to over 9 hours for each run, which points to a
> newly introduced problem in GDB or in the testsuite (timeouts?).

That may well be.  Can you point at some representative builds,
before/after the jump?

Thanks,
Pedro Alves

Re: [BuildBot] Notifications disabled for Debian-s390x-* and Fedora-ppc64*-* builders

[David Edelsohn]

On Fri, Dec 15, 2017 at 10:42 AM, Pedro Alves <palves@redhat.com> wrote:
> On 12/15/2017 03:06 PM, David Edelsohn wrote:
>
>> Third, the testsuite summaries that no one from the GDB community
>> monitored show that the testsuite runtime jumped from a relatively
>> short amount of time to over 9 hours for each run, which points to a
>> newly introduced problem in GDB or in the testsuite (timeouts?).
>
> That may well be.  Can you point at some representative builds,
> before/after the jump?

The testsuite runs for 6 minutes on RHEL7 s390x buildslave and 9 hours
on Debian Jessie s390x buildslave.

The Debian Jessie system also runs a Python buildslave without
problem.  The system has 4 virtual cpus and 16GB of memory, which
should be more than adequately sized.

Thanks, David

Re: [BuildBot] Notifications disabled for Debian-s390x-* and Fedora-ppc64*-* builders

[Pedro Alves]

On 12/15/2017 03:53 PM, David Edelsohn wrote:
> On Fri, Dec 15, 2017 at 10:42 AM, Pedro Alves <palves@redhat.com> wrote:
>> On 12/15/2017 03:06 PM, David Edelsohn wrote:
>>
>>> Third, the testsuite summaries that no one from the GDB community
>>> monitored show that the testsuite runtime jumped from a relatively
>>> short amount of time to over 9 hours for each run, which points to a
>>> newly introduced problem in GDB or in the testsuite (timeouts?).
>>
>> That may well be.  Can you point at some representative builds,
>> before/after the jump?
> 
> The testsuite runs for 6 minutes on RHEL7 s390x buildslave and 9 hours
> on Debian Jessie s390x buildslave.

Those are separate machines.  I'd like to see the jump on the same
machine, so we can maybe pinpoint what caused it.

I was really asking for URLs.  Here looks like there's some:

 https://gdb-build.sergiodj.net/builders/Debian-s390x-native-gdbserver-m64

Here, for example:

 https://gdb-build.sergiodj.net/builders/Debian-s390x-native-gdbserver-m64/builds/4351

"test gdb tested GDB failed (9 hrs, 2 mins, 56 secs)"

That's definitely too long.

I downloaded the gdb.log file, and did:

$ grep FAIL gdb.log  | grep timeout | sed 's/.exp.*/.exp/g' | sort | uniq -c | sort -n
      1 FAIL: gdb.base/watch-cond.exp
      1 FAIL: gdb.multi/watchpoint-multi-exit.exp
      1 FAIL: gdb.threads/interrupted-hand-call.exp
      1 FAIL: gdb.threads/thread-unwindonsignal.exp
      2 FAIL: gdb.base/value-double-free.exp
      3 FAIL: gdb.mi/mi-async.exp
      3 FAIL: gdb.threads/process-dies-while-detaching.exp
      4 FAIL: gdb.base/pr11022.exp
     10 FAIL: gdb.base/watch-bitfields.exp
     15 FAIL: gdb.base/watchpoints.exp
     20 FAIL: gdb.threads/interrupt-while-step-over.exp
     32 FAIL: gdb.threads/watchpoint-fork.exp
     45 FAIL: gdb.threads/step-over-trips-on-watchpoint.exp
     46 FAIL: gdb.base/display.exp
     51 FAIL: gdb.base/watchpoint.exp

Not _that_ many.  Could they explain the long time?  I suspect not.

We see this:

 $ grep "Test run by" gdb.log | head -n 3
 Test run by dje on Tue Nov 21 03:23:01 2017
 Test run by dje on Tue Nov 21 03:23:01 2017
 Test run by dje on Tue Nov 21 03:23:01 2017

 $ grep "Test run by" gdb.log | tail -n 3
 Test run by dje on Tue Nov 21 03:29:54 2017
 Test run by dje on Tue Nov 21 03:29:54 2017
 Test run by dje on Tue Nov 21 03:29:54 2017

So most of the testsuite actually ran for 7 minutes.  And then
something hung for 9 hours?  I have no idea how that
could happen from the existing logs.  The tail end of the log has:

~~~
FAIL: gdb.base/watchpoint.exp: delete all breakpoints in delete_breakpoints (timeout)
ERROR: breakpoints not deleted
ERROR: breakpoints not deleted

command timed out: 1200 seconds without output running ['make', '-k', 'check', 'RUNTESTFLAGS=--target_board native-gdbserver', '-j8', 'FORCE_PARALLEL=1'], attempting to kill
process killed by signal 9
program finished with exit code -1
elapsedTime=32576.210392
~~~

I don't understand how 7 minutes plus 1200 seconds (~20min)
resulted in "elapsedTime=32576.210392" (~9h).  Maybe that number
isn't to be trusted.

Anyway, I'm sorry, but I really don't have the time to be
looking at this.  Someone with the motivation and access to
the machine could try running the testsuite manually,
for example, see how long that takes, and where the hang is.

> The Debian Jessie system also runs a Python buildslave without
> problem.  The system has 4 virtual cpus and 16GB of memory, which
> should be more than adequately sized.

Thanks,
Pedro Alves

Re: [BuildBot] Notifications disabled for Debian-s390x-* and Fedora-ppc64*-* builders

[David Edelsohn]

On Fri, Dec 15, 2017 at 11:20 AM, Pedro Alves <palves@redhat.com> wrote:
> On 12/15/2017 03:53 PM, David Edelsohn wrote:
>> On Fri, Dec 15, 2017 at 10:42 AM, Pedro Alves <palves@redhat.com> wrote:
>>> On 12/15/2017 03:06 PM, David Edelsohn wrote:
>>>
>>>> Third, the testsuite summaries that no one from the GDB community
>>>> monitored show that the testsuite runtime jumped from a relatively
>>>> short amount of time to over 9 hours for each run, which points to a
>>>> newly introduced problem in GDB or in the testsuite (timeouts?).
>>>
>>> That may well be.  Can you point at some representative builds,
>>> before/after the jump?
>>
>> The testsuite runs for 6 minutes on RHEL7 s390x buildslave and 9 hours
>> on Debian Jessie s390x buildslave.
>
> Those are separate machines.  I'd like to see the jump on the same
> machine, so we can maybe pinpoint what caused it.
>
> I was really asking for URLs.  Here looks like there's some:
>
>  https://gdb-build.sergiodj.net/builders/Debian-s390x-native-gdbserver-m64
>
> Here, for example:
>
>  https://gdb-build.sergiodj.net/builders/Debian-s390x-native-gdbserver-m64/builds/4351
>
> "test gdb tested GDB failed (9 hrs, 2 mins, 56 secs)"
>
> That's definitely too long.
>
> I downloaded the gdb.log file, and did:
>
> $ grep FAIL gdb.log  | grep timeout | sed 's/.exp.*/.exp/g' | sort | uniq -c | sort -n
>       1 FAIL: gdb.base/watch-cond.exp
>       1 FAIL: gdb.multi/watchpoint-multi-exit.exp
>       1 FAIL: gdb.threads/interrupted-hand-call.exp
>       1 FAIL: gdb.threads/thread-unwindonsignal.exp
>       2 FAIL: gdb.base/value-double-free.exp
>       3 FAIL: gdb.mi/mi-async.exp
>       3 FAIL: gdb.threads/process-dies-while-detaching.exp
>       4 FAIL: gdb.base/pr11022.exp
>      10 FAIL: gdb.base/watch-bitfields.exp
>      15 FAIL: gdb.base/watchpoints.exp
>      20 FAIL: gdb.threads/interrupt-while-step-over.exp
>      32 FAIL: gdb.threads/watchpoint-fork.exp
>      45 FAIL: gdb.threads/step-over-trips-on-watchpoint.exp
>      46 FAIL: gdb.base/display.exp
>      51 FAIL: gdb.base/watchpoint.exp
>
> Not _that_ many.  Could they explain the long time?  I suspect not.
>
> We see this:
>
>  $ grep "Test run by" gdb.log | head -n 3
>  Test run by dje on Tue Nov 21 03:23:01 2017
>  Test run by dje on Tue Nov 21 03:23:01 2017
>  Test run by dje on Tue Nov 21 03:23:01 2017
>
>  $ grep "Test run by" gdb.log | tail -n 3
>  Test run by dje on Tue Nov 21 03:29:54 2017
>  Test run by dje on Tue Nov 21 03:29:54 2017
>  Test run by dje on Tue Nov 21 03:29:54 2017
>
> So most of the testsuite actually ran for 7 minutes.  And then
> something hung for 9 hours?  I have no idea how that
> could happen from the existing logs.  The tail end of the log has:
>
> ~~~
> FAIL: gdb.base/watchpoint.exp: delete all breakpoints in delete_breakpoints (timeout)
> ERROR: breakpoints not deleted
> ERROR: breakpoints not deleted
>
> command timed out: 1200 seconds without output running ['make', '-k', 'check', 'RUNTESTFLAGS=--target_board native-gdbserver', '-j8', 'FORCE_PARALLEL=1'], attempting to kill
> process killed by signal 9
> program finished with exit code -1
> elapsedTime=32576.210392
> ~~~
>
> I don't understand how 7 minutes plus 1200 seconds (~20min)
> resulted in "elapsedTime=32576.210392" (~9h).  Maybe that number
> isn't to be trusted.
>
> Anyway, I'm sorry, but I really don't have the time to be
> looking at this.  Someone with the motivation and access to
> the machine could try running the testsuite manually,
> for example, see how long that takes, and where the hang is.

I will try reverting to an older version of DejaGNU framework.

Thanks, David

Re: [BuildBot] Notifications disabled for Debian-s390x-* and Fedora-ppc64*-* builders

[David Edelsohn]

On Fri, Dec 15, 2017 at 12:29 PM, David Edelsohn <dje.gcc@gmail.com> wrote:
> On Fri, Dec 15, 2017 at 11:20 AM, Pedro Alves <palves@redhat.com> wrote:
>> On 12/15/2017 03:53 PM, David Edelsohn wrote:
>>> On Fri, Dec 15, 2017 at 10:42 AM, Pedro Alves <palves@redhat.com> wrote:
>>>> On 12/15/2017 03:06 PM, David Edelsohn wrote:
>>>>
>>>>> Third, the testsuite summaries that no one from the GDB community
>>>>> monitored show that the testsuite runtime jumped from a relatively
>>>>> short amount of time to over 9 hours for each run, which points to a
>>>>> newly introduced problem in GDB or in the testsuite (timeouts?).
>>>>
>>>> That may well be.  Can you point at some representative builds,
>>>> before/after the jump?
>>>
>>> The testsuite runs for 6 minutes on RHEL7 s390x buildslave and 9 hours
>>> on Debian Jessie s390x buildslave.
>>
>> Those are separate machines.  I'd like to see the jump on the same
>> machine, so we can maybe pinpoint what caused it.
>>
>> I was really asking for URLs.  Here looks like there's some:
>>
>>  https://gdb-build.sergiodj.net/builders/Debian-s390x-native-gdbserver-m64
>>
>> Here, for example:
>>
>>  https://gdb-build.sergiodj.net/builders/Debian-s390x-native-gdbserver-m64/builds/4351
>>
>> "test gdb tested GDB failed (9 hrs, 2 mins, 56 secs)"
>>
>> That's definitely too long.
>>
>> I downloaded the gdb.log file, and did:
>>
>> $ grep FAIL gdb.log  | grep timeout | sed 's/.exp.*/.exp/g' | sort | uniq -c | sort -n
>>       1 FAIL: gdb.base/watch-cond.exp
>>       1 FAIL: gdb.multi/watchpoint-multi-exit.exp
>>       1 FAIL: gdb.threads/interrupted-hand-call.exp
>>       1 FAIL: gdb.threads/thread-unwindonsignal.exp
>>       2 FAIL: gdb.base/value-double-free.exp
>>       3 FAIL: gdb.mi/mi-async.exp
>>       3 FAIL: gdb.threads/process-dies-while-detaching.exp
>>       4 FAIL: gdb.base/pr11022.exp
>>      10 FAIL: gdb.base/watch-bitfields.exp
>>      15 FAIL: gdb.base/watchpoints.exp
>>      20 FAIL: gdb.threads/interrupt-while-step-over.exp
>>      32 FAIL: gdb.threads/watchpoint-fork.exp
>>      45 FAIL: gdb.threads/step-over-trips-on-watchpoint.exp
>>      46 FAIL: gdb.base/display.exp
>>      51 FAIL: gdb.base/watchpoint.exp
>>
>> Not _that_ many.  Could they explain the long time?  I suspect not.
>>
>> We see this:
>>
>>  $ grep "Test run by" gdb.log | head -n 3
>>  Test run by dje on Tue Nov 21 03:23:01 2017
>>  Test run by dje on Tue Nov 21 03:23:01 2017
>>  Test run by dje on Tue Nov 21 03:23:01 2017
>>
>>  $ grep "Test run by" gdb.log | tail -n 3
>>  Test run by dje on Tue Nov 21 03:29:54 2017
>>  Test run by dje on Tue Nov 21 03:29:54 2017
>>  Test run by dje on Tue Nov 21 03:29:54 2017
>>
>> So most of the testsuite actually ran for 7 minutes.  And then
>> something hung for 9 hours?  I have no idea how that
>> could happen from the existing logs.  The tail end of the log has:
>>
>> ~~~
>> FAIL: gdb.base/watchpoint.exp: delete all breakpoints in delete_breakpoints (timeout)
>> ERROR: breakpoints not deleted
>> ERROR: breakpoints not deleted
>>
>> command timed out: 1200 seconds without output running ['make', '-k', 'check', 'RUNTESTFLAGS=--target_board native-gdbserver', '-j8', 'FORCE_PARALLEL=1'], attempting to kill
>> process killed by signal 9
>> program finished with exit code -1
>> elapsedTime=32576.210392
>> ~~~
>>
>> I don't understand how 7 minutes plus 1200 seconds (~20min)
>> resulted in "elapsedTime=32576.210392" (~9h).  Maybe that number
>> isn't to be trusted.
>>
>> Anyway, I'm sorry, but I really don't have the time to be
>> looking at this.  Someone with the motivation and access to
>> the machine could try running the testsuite manually,
>> for example, see how long that takes, and where the hang is.
>
> I will try reverting to an older version of DejaGNU framework.

Older DejaGNU does not seem to have an effect.  All of the processes
are stuck in "gdb.threads/process-dies-while-handling-bp"

Thanks, David

Re: [BuildBot] Notifications disabled for Debian-s390x-* and Fedora-ppc64*-* builders

[Pedro Alves]

On 12/15/2017 06:55 PM, David Edelsohn wrote:

> Older DejaGNU does not seem to have an effect.  All of the processes
> are stuck in "gdb.threads/process-dies-while-handling-bp"
> 

Strange, I'm not seeing any potential infinite loop in the
testcase, so I'd expect that it least it should timeout properly.
Can you run the testcase alone, with

make check TESTS="gdb.threads/process-dies-while-handling-bp"

and send the resulting gdb.sum/gdb.log.

Thanks,
Pedro Alves

Re: [BuildBot] Notifications disabled for Debian-s390x-* and Fedora-ppc64*-* builders

[David Edelsohn]

[-- Attachment #1: Type: text/plain, Size: 907 bytes --]

On Fri, Dec 15, 2017 at 2:19 PM, Pedro Alves <palves@redhat.com> wrote:
> On 12/15/2017 06:55 PM, David Edelsohn wrote:
>
>> Older DejaGNU does not seem to have an effect.  All of the processes
>> are stuck in "gdb.threads/process-dies-while-handling-bp"
>>
>
> Strange, I'm not seeing any potential infinite loop in the
> testcase, so I'd expect that it least it should timeout properly.
> Can you run the testcase alone, with
>
> make check TESTS="gdb.threads/process-dies-while-handling-bp"
>
> and send the resulting gdb.sum/gdb.log.

Reverting to an earlier revision of the DejaGNU Framework did not help.

I also updated all of the packages installed on the Debian system,
including the kernel, but the problem still remains.  make check is
reporting a large number of timeouts in gdb.base and gdb.thread. At
300s per timeout, it adds up -- eventually to 9 hours.  Some of the
log files are attached.

[-- Attachment #2: display.log --]
[-- Type: application/octet-stream, Size: 7082 bytes --]

Test Run By dje on Fri Dec 15 17:43:52 2017
Native configuration is s390x-ibm-linux-gnu

		=== gdb tests ===

Schedule of variations:
    native-gdbserver

Running target native-gdbserver
Using /home/dje/src/binutils-gdb/gdb/testsuite/boards/../boards/native-gdbserver.exp as board description file for target.
Using /home/dje/src/binutils-gdb/gdb/testsuite/boards/../boards/gdbserver-base.exp as board description file for target.
Using /home/dje/src/binutils-gdb/gdb/testsuite/boards/../boards/local-board.exp as board description file for target.
Using /home/dje/src/binutils-gdb/gdb/testsuite/config/gdbserver.exp as tool-and-target-specific interface file.
Running /home/dje/src/binutils-gdb/gdb/testsuite/gdb.base/display.exp ...
get_compiler_info: gcc-4-9-2
Executing on host: gcc   -w -c -g  -o /home/dje/build/GDB/gdb/testsuite/outputs/gdb.base/display/display0.o /home/dje/src/binutils-gdb/gdb/testsuite/gdb.base/display.c    (timeout = 300)
spawn -ignore SIGHUP gcc -w -c -g -o /home/dje/build/GDB/gdb/testsuite/outputs/gdb.base/display/display0.o /home/dje/src/binutils-gdb/gdb/testsuite/gdb.base/display.c
Executing on host: gcc  /home/dje/build/GDB/gdb/testsuite/outputs/gdb.base/display/display0.o  -w -g  -lm   -o /home/dje/build/GDB/gdb/testsuite/outputs/gdb.base/display/display    (timeout = 300)
spawn -ignore SIGHUP gcc /home/dje/build/GDB/gdb/testsuite/outputs/gdb.base/display/display0.o -w -g -lm -o /home/dje/build/GDB/gdb/testsuite/outputs/gdb.base/display/display
spawn /home/dje/build/GDB/gdb/testsuite/../../gdb/gdb -nw -nx -data-directory /home/dje/build/GDB/gdb/testsuite/../data-directory -ex set auto-connect-native-target off
GNU gdb (GDB) 8.0.50.20171215-git
Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "s390x-ibm-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word".
(gdb) set height 0
(gdb) set width 0
(gdb) dir
Reinitialize source path to empty? (y or n) y
Source directories searched: $cdir:$cwd
(gdb) dir /home/dje/src/binutils-gdb/gdb/testsuite/gdb.base
Source directories searched: /home/dje/src/binutils-gdb/gdb/testsuite/gdb.base:$cdir:$cwd
(gdb) kill
The program is not being run.
(gdb) file /home/dje/build/GDB/gdb/testsuite/outputs/gdb.base/display/display
Reading symbols from /home/dje/build/GDB/gdb/testsuite/outputs/gdb.base/display/display...done.
(gdb) delete breakpoints
(gdb) info breakpoints
No breakpoints or watchpoints.
(gdb) break main
Breakpoint 1 at 0x800007a6: file /home/dje/src/binutils-gdb/gdb/testsuite/gdb.base/display.c, line 55.
(gdb) kill
The program is not being run.
(gdb) spawn /home/dje/build/GDB/gdb/testsuite/../gdbserver/gdbserver --once :2346 /home/dje/build/GDB/gdb/testsuite/outputs/gdb.base/display/display
Process /home/dje/build/GDB/gdb/testsuite/outputs/gdb.base/display/display created; pid = 17018
Listening on port 2346
target remote localhost:2346
Remote debugging using localhost:2346
Reading /lib/ld64.so.1 from remote target...
warning: File transfers from remote targets can be slow. Use "set sysroot" to access files locally instead.
Reading /lib/ld64.so.1 from remote target...
Reading symbols from target:/lib/ld64.so.1...Reading /lib/ld-2.19.so from remote target...
Reading /lib/.debug/ld-2.19.so from remote target...
(no debugging symbols found)...done.
0x000003fffdfd9280 in ?? () from target:/lib/ld64.so.1
(gdb) continue
Continuing.
Reading /lib/s390x-linux-gnu/libm.so.6 from remote target...
Reading /lib/s390x-linux-gnu/libc.so.6 from remote target...
Reading /lib/s390x-linux-gnu/libm-2.19.so from remote target...
Reading /lib/s390x-linux-gnu/.debug/libm-2.19.so from remote target...
Reading /lib/s390x-linux-gnu/libc-2.19.so from remote target...
Reading /lib/s390x-linux-gnu/.debug/libc-2.19.so from remote target...

Breakpoint 1, main () at /home/dje/src/binutils-gdb/gdb/testsuite/gdb.base/display.c:55
55	    do_loops();
(gdb) break 19
Breakpoint 2 at 0x80000602: file /home/dje/src/binutils-gdb/gdb/testsuite/gdb.base/display.c, line 19.
(gdb) PASS: gdb.base/display.exp: break  do_loops
cont
Continuing.

Breakpoint 2, do_loops () at /home/dje/src/binutils-gdb/gdb/testsuite/gdb.base/display.c:19
19	    for( i = 0; i < LOOP; i++ ) { /* set breakpoint 1 here */
(gdb) PASS: gdb.base/display.exp: get to do_loops
watch sum
Hardware watchpoint 3: sum
(gdb) PASS: gdb.base/display.exp: set watch
break 26
Breakpoint 4 at 0x800006a8: file /home/dje/src/binutils-gdb/gdb/testsuite/gdb.base/display.c, line 26.
(gdb) PASS: gdb.base/display.exp: break loop end
info disp
There are no auto-display expressions now.
(gdb) PASS: gdb.base/display.exp: inf disp
disp i
1: i = 0
(gdb) PASS: gdb.base/display.exp: display i
disp/x j
2: /x j = 0x0
(gdb) PASS: gdb.base/display.exp: display j
disp/i &k
3: x/i &k
   0x3ffffffdde8:	.long	0x00000000
(gdb) PASS: gdb.base/display.exp: display &k
disp/f f
4: /f f = 3.1415
(gdb) PASS: gdb.base/display.exp: display/f f
disp/s &sum
5: x/s &sum  0x80001c5c <sum>:	""
(gdb) PASS: gdb.base/display.exp: display/s &sum
cont
Continuing.
Warning:
Could not insert hardware watchpoint 3.
Could not insert hardware breakpoints:
You may have requested too many hardware breakpoints/watchpoints.

Command aborted.
(gdb) FAIL: gdb.base/display.exp: first disp
cont
Continuing.
FAIL: gdb.base/display.exp: second disp (timeout)
enab  disp 6
FAIL: gdb.base/display.exp: catch err (timeout)
disab disp 1
FAIL: gdb.base/display.exp: disab disp 1 (timeout)
disab disp 2
FAIL: gdb.base/display.exp: disab disp 2 (timeout)
enab disp 1
FAIL: gdb.base/display.exp: re-enab (timeout)
enab disp 1
FAIL: gdb.base/display.exp: re-enab of enab (timeout)
undisp 5
FAIL: gdb.base/display.exp: undisp (timeout)
info disp
FAIL: gdb.base/display.exp: info disp (timeout)
cont
FAIL: gdb.base/display.exp: next hit (timeout)
undisp
FAIL: gdb.base/display.exp: undisp all (timeout)
disp *p_i
FAIL: gdb.base/display.exp: disp *p_i (timeout)
p p_i = 0x0
FAIL: gdb.base/display.exp: p p_i = 0x0 (timeout)
display
FAIL: gdb.base/display.exp: display bad address (timeout)
p p_i = &i
FAIL: gdb.base/display.exp: p p_i = &i (timeout)
display
FAIL: gdb.base/display.exp: display good address (timeout)
undisp
FAIL: gdb.base/display.exp: undisp all again (timeout)
disab 3
FAIL: gdb.base/display.exp: disab 3 (timeout)
cont
FAIL: gdb.base/display.exp: watch off (timeout)
finish
FAIL: gdb.base/display.exp: finish (timeout)
step
FAIL: gdb.base/display.exp: step (timeout)
tbreak 42

[-- Attachment #3: step-over-trips-on-watchpoint.log --]
[-- Type: application/octet-stream, Size: 125006 bytes --]

Test Run By dje on Fri Dec 15 17:47:31 2017
Native configuration is s390x-ibm-linux-gnu

		=== gdb tests ===

Schedule of variations:
    native-gdbserver

Running target native-gdbserver
Using /home/dje/src/binutils-gdb/gdb/testsuite/boards/../boards/native-gdbserver.exp as board description file for target.
Using /home/dje/src/binutils-gdb/gdb/testsuite/boards/../boards/gdbserver-base.exp as board description file for target.
Using /home/dje/src/binutils-gdb/gdb/testsuite/boards/../boards/local-board.exp as board description file for target.
Using /home/dje/src/binutils-gdb/gdb/testsuite/config/gdbserver.exp as tool-and-target-specific interface file.
Running /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.exp ...
Executing on host: gcc  /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c  -I/home/dje/build/GDB/gdb/testsuite -g  -lpthreads -lm   -o /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/step-over-trips-on-watchpoint/step-over-trips-on-watchpoint    (timeout = 300)
spawn -ignore SIGHUP gcc /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c -I/home/dje/build/GDB/gdb/testsuite -g -lpthreads -lm -o /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/step-over-trips-on-watchpoint/step-over-trips-on-watchpoint
/usr/bin/ld: cannot find -lpthreads
collect2: error: ld returned 1 exit status
compiler exited with status 1
output is:
/usr/bin/ld: cannot find -lpthreads
collect2: error: ld returned 1 exit status

Executing on host: gcc  /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c  -I/home/dje/build/GDB/gdb/testsuite -g  -lpthread -lm   -o /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/step-over-trips-on-watchpoint/step-over-trips-on-watchpoint    (timeout = 300)
spawn -ignore SIGHUP gcc /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c -I/home/dje/build/GDB/gdb/testsuite -g -lpthread -lm -o /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/step-over-trips-on-watchpoint/step-over-trips-on-watchpoint
PASS: gdb.threads/step-over-trips-on-watchpoint.exp: successfully compiled posix threads test case
spawn /home/dje/build/GDB/gdb/testsuite/../../gdb/gdb -nw -nx -data-directory /home/dje/build/GDB/gdb/testsuite/../data-directory -ex set auto-connect-native-target off
GNU gdb (GDB) 8.0.50.20171215-git
Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "s390x-ibm-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word".
(gdb) set height 0
(gdb) set width 0
(gdb) dir
Reinitialize source path to empty? (y or n) y
Source directories searched: $cdir:$cwd
(gdb) dir /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads
Source directories searched: /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads:$cdir:$cwd
(gdb) kill
The program is not being run.
(gdb) file /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/step-over-trips-on-watchpoint/step-over-trips-on-watchpoint
Reading symbols from /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/step-over-trips-on-watchpoint/step-over-trips-on-watchpoint...done.
(gdb) delete breakpoints
(gdb) info breakpoints
No breakpoints or watchpoints.
(gdb) break main
Breakpoint 1 at 0x800008b6: file /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c, line 52.
(gdb) kill
The program is not being run.
(gdb) spawn /home/dje/build/GDB/gdb/testsuite/../gdbserver/gdbserver --once :2346 /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/step-over-trips-on-watchpoint/step-over-trips-on-watchpoint
Process /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/step-over-trips-on-watchpoint/step-over-trips-on-watchpoint created; pid = 10058
Listening on port 2346
target remote localhost:2346
Remote debugging using localhost:2346
Reading /lib/ld64.so.1 from remote target...
warning: File transfers from remote targets can be slow. Use "set sysroot" to access files locally instead.
Reading /lib/ld64.so.1 from remote target...
Reading symbols from target:/lib/ld64.so.1...Reading /lib/ld-2.19.so from remote target...
Reading /lib/.debug/ld-2.19.so from remote target...
(no debugging symbols found)...done.
0x000003fffdfd9280 in ?? () from target:/lib/ld64.so.1
(gdb) continue
Continuing.
Reading /lib/s390x-linux-gnu/libpthread.so.0 from remote target...
Reading /lib/s390x-linux-gnu/libm.so.6 from remote target...
Reading /lib/s390x-linux-gnu/libc.so.6 from remote target...
Reading /lib/s390x-linux-gnu/libpthread-2.19.so from remote target...
Reading /lib/s390x-linux-gnu/.debug/libpthread-2.19.so from remote target...
Reading /lib/s390x-linux-gnu/libm-2.19.so from remote target...
Reading /lib/s390x-linux-gnu/.debug/libm-2.19.so from remote target...
Reading /lib/s390x-linux-gnu/libc-2.19.so from remote target...
Reading /lib/s390x-linux-gnu/.debug/libc-2.19.so from remote target...

Breakpoint 1, main () at /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c:52
52	  alarm (300);
(gdb) set displaced-stepping off
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: no thread-specific bp: step: set displaced-stepping off
break 65
Breakpoint 2 at 0x80000902: file /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c, line 65.
(gdb) continue
Continuing.
[New Thread 10058.10139]

Thread 1 "step-over-trips" hit Breakpoint 2, main () at /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c:65
65	  while (1); /* set wait-thread breakpoint here */
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: no thread-specific bp: step: continue to breakpoint: run to wait-thread breakpoint
info threads
  Id   Target Id         Frame 
* 1    Thread 10058.10058 "step-over-trips" main () at /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c:65
  2    Thread 10058.10139 "step-over-trips" 0x000003fffde21c30 in ?? () at ../sysdeps/unix/syscall-template.S:81 from target:/lib/s390x-linux-gnu/libc.so.6
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: no thread-specific bp: step: info threads shows all threads
set scheduler-locking on
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: no thread-specific bp: step: set scheduler-locking on
delete breakpoints
Delete all breakpoints? (y or n) y
(gdb) info breakpoints
No breakpoints or watchpoints.
(gdb) break 38
Breakpoint 3 at 0x80000866: file /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c, line 38.
(gdb) thread 2
[Switching to thread 2 (Thread 10058.10139)]
#0  0x000003fffde21c30 in ?? () at ../sysdeps/unix/syscall-template.S:81 from target:/lib/s390x-linux-gnu/libc.so.6
81	../sysdeps/unix/syscall-template.S: No such file or directory.
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: no thread-specific bp: step: thread 2
continue
Continuing.

Thread 2 "step-over-trips" hit Breakpoint 3, child_function (arg=0x0) at /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c:38
38	      watch_me = 1; /* set breakpoint child here */
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: no thread-specific bp: step: continue to breakpoint: run to breakpoint in thread 2
p watch_me = 0
$1 = 0
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: no thread-specific bp: step: find addresses: clear watch_me
watch watch_me
Hardware watchpoint 4: watch_me
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: no thread-specific bp: step: find addresses: watch watch_me
continue
Continuing.
Warning:
Could not insert hardware watchpoint 4.
Could not insert hardware breakpoints:
You may have requested too many hardware breakpoints/watchpoints.

Command aborted.
(gdb) FAIL: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: no thread-specific bp: step: find addresses: continue to watchpoint
disassemble
Dump of assembler code for function child_function:
   0x0000000080000828 <+0>:	stmg	%r11,%r15,88(%r15)
   0x000000008000082e <+6>:	aghi	%r15,-168
   0x0000000080000832 <+10>:	lgr	%r11,%r15
   0x0000000080000836 <+14>:	stg	%r2,160(%r11)
   0x000000008000083c <+20>:	larl	%r2,0x80001d40 <barrier>
   0x0000000080000842 <+26>:	brasl	%r14,0x80000620 <pthread_barrier_wait@plt>
   0x0000000080000848 <+32>:	j	0x8000088c <child_function+100>
   0x000000008000084c <+36>:	larl	%r1,0x80001d30 <counter>
   0x0000000080000852 <+42>:	l	%r1,0(%r1)
   0x0000000080000856 <+46>:	ahi	%r1,1
   0x000000008000085a <+50>:	lr	%r2,%r1
   0x000000008000085c <+52>:	larl	%r1,0x80001d30 <counter>
   0x0000000080000862 <+58>:	st	%r2,0(%r1)
=> 0x0000000080000866 <+62>:	larl	%r1,0x80001d6c <watch_me>
   0x000000008000086c <+68>:	lhi	%r2,1
   0x0000000080000870 <+72>:	st	%r2,0(%r1)
   0x0000000080000874 <+76>:	larl	%r1,0x80001d68 <other>
   0x000000008000087a <+82>:	lhi	%r2,1
   0x000000008000087e <+86>:	st	%r2,0(%r1)
   0x0000000080000882 <+90>:	lghi	%r2,1
   0x0000000080000886 <+94>:	brasl	%r14,0x80000660 <usleep@plt>
   0x000000008000088c <+100>:	larl	%r1,0x80001d30 <counter>
   0x0000000080000892 <+106>:	l	%r1,0(%r1)
   0x0000000080000896 <+110>:	ltr	%r1,%r1
   0x0000000080000898 <+112>:	jne	0x8000084c <child_function+36>
   0x000000008000089c <+116>:	lghi	%r2,0
   0x00000000800008a0 <+120>:	brasl	%r14,0x800006c0 <pthread_exit@plt>
End of assembler dump.
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: no thread-specific bp: step: find addresses: find addresses
delete breakpoints
Delete all breakpoints? (y or n) y
(gdb) info breakpoints
No breakpoints or watchpoints.
(gdb) break *0x0000000080000862
Breakpoint 5 at 0x80000862: file /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c, line 36.
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: no thread-specific bp: step: set breakpoint at address that triggers watch
continue
Continuing.
FAIL: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: no thread-specific bp: step: continue to breakpoint: run to instruction that triggers watch in thread 2 (timeout)
p counter = 0
FAIL: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: no thread-specific bp: step: unbreak loop in thread 2 (timeout)
p watch_me = 0
FAIL: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: no thread-specific bp: step: clear watch_me (timeout)
watch watch_me
FAIL: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: no thread-specific bp: step: watch watch_me (timeout)
thread 1
FAIL: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: no thread-specific bp: step: thread 1 (timeout)
set scheduler-locking off
FAIL: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: no thread-specific bp: step: set scheduler-locking off (timeout)
step
FAIL: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: no thread-specific bp: step: step (timeout)
Remote debugging from host 127.0.0.1
monitor exit
spawn /home/dje/build/GDB/gdb/testsuite/../../gdb/gdb -nw -nx -data-directory /home/dje/build/GDB/gdb/testsuite/../data-directory -ex set auto-connect-native-target off
GNU gdb (GDB) 8.0.50.20171215-git
Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "s390x-ibm-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word".
(gdb) set height 0
(gdb) set width 0
(gdb) dir
Reinitialize source path to empty? (y or n) y
Source directories searched: $cdir:$cwd
(gdb) dir /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads
Source directories searched: /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads:$cdir:$cwd
(gdb) kill
The program is not being run.
(gdb) file /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/step-over-trips-on-watchpoint/step-over-trips-on-watchpoint
Reading symbols from /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/step-over-trips-on-watchpoint/step-over-trips-on-watchpoint...done.
(gdb) delete breakpoints
(gdb) info breakpoints
No breakpoints or watchpoints.
(gdb) break main
Breakpoint 1 at 0x800008b6: file /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c, line 52.
(gdb) kill
The program is not being run.
(gdb) spawn /home/dje/build/GDB/gdb/testsuite/../gdbserver/gdbserver --once :2347 /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/step-over-trips-on-watchpoint/step-over-trips-on-watchpoint
Process /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/step-over-trips-on-watchpoint/step-over-trips-on-watchpoint created; pid = 11163
Listening on port 2347
target remote localhost:2347
Remote debugging using localhost:2347
Reading /lib/ld64.so.1 from remote target...
warning: File transfers from remote targets can be slow. Use "set sysroot" to access files locally instead.
Reading /lib/ld64.so.1 from remote target...
Reading symbols from target:/lib/ld64.so.1...Reading /lib/ld-2.19.so from remote target...
Reading /lib/.debug/ld-2.19.so from remote target...
(no debugging symbols found)...done.
0x000003fffdfd9280 in ?? () from target:/lib/ld64.so.1
(gdb) continue
Continuing.
Reading /lib/s390x-linux-gnu/libpthread.so.0 from remote target...
Reading /lib/s390x-linux-gnu/libm.so.6 from remote target...
Reading /lib/s390x-linux-gnu/libc.so.6 from remote target...
Reading /lib/s390x-linux-gnu/libpthread-2.19.so from remote target...
Reading /lib/s390x-linux-gnu/.debug/libpthread-2.19.so from remote target...
Reading /lib/s390x-linux-gnu/libm-2.19.so from remote target...
Reading /lib/s390x-linux-gnu/.debug/libm-2.19.so from remote target...
Reading /lib/s390x-linux-gnu/libc-2.19.so from remote target...
Reading /lib/s390x-linux-gnu/.debug/libc-2.19.so from remote target...

Breakpoint 1, main () at /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c:52
52	  alarm (300);
(gdb) set displaced-stepping off
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: no thread-specific bp: next: set displaced-stepping off
break 65
Breakpoint 2 at 0x80000902: file /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c, line 65.
(gdb) continue
Continuing.
[New Thread 11163.11182]

Thread 1 "step-over-trips" hit Breakpoint 2, main () at /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c:65
65	  while (1); /* set wait-thread breakpoint here */
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: no thread-specific bp: next: continue to breakpoint: run to wait-thread breakpoint
info threads
  Id   Target Id         Frame 
* 1    Thread 11163.11163 "step-over-trips" main () at /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c:65
  2    Thread 11163.11182 "step-over-trips" 0x000003fffde21c30 in ?? () at ../sysdeps/unix/syscall-template.S:81 from target:/lib/s390x-linux-gnu/libc.so.6
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: no thread-specific bp: next: info threads shows all threads
set scheduler-locking on
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: no thread-specific bp: next: set scheduler-locking on
delete breakpoints
Delete all breakpoints? (y or n) y
(gdb) info breakpoints
No breakpoints or watchpoints.
(gdb) break 38
Breakpoint 3 at 0x80000866: file /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c, line 38.
(gdb) thread 2
[Switching to thread 2 (Thread 11163.11182)]
#0  0x000003fffde21c30 in ?? () at ../sysdeps/unix/syscall-template.S:81 from target:/lib/s390x-linux-gnu/libc.so.6
81	../sysdeps/unix/syscall-template.S: No such file or directory.
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: no thread-specific bp: next: thread 2
continue
Continuing.

Thread 2 "step-over-trips" hit Breakpoint 3, child_function (arg=0x0) at /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c:38
38	      watch_me = 1; /* set breakpoint child here */
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: no thread-specific bp: next: continue to breakpoint: run to breakpoint in thread 2
p watch_me = 0
$1 = 0
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: no thread-specific bp: next: find addresses: clear watch_me
watch watch_me
Hardware watchpoint 4: watch_me
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: no thread-specific bp: next: find addresses: watch watch_me
continue
Continuing.
Warning:
Could not insert hardware watchpoint 4.
Could not insert hardware breakpoints:
You may have requested too many hardware breakpoints/watchpoints.

Command aborted.
(gdb) FAIL: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: no thread-specific bp: next: find addresses: continue to watchpoint
disassemble
Dump of assembler code for function child_function:
   0x0000000080000828 <+0>:	stmg	%r11,%r15,88(%r15)
   0x000000008000082e <+6>:	aghi	%r15,-168
   0x0000000080000832 <+10>:	lgr	%r11,%r15
   0x0000000080000836 <+14>:	stg	%r2,160(%r11)
   0x000000008000083c <+20>:	larl	%r2,0x80001d40 <barrier>
   0x0000000080000842 <+26>:	brasl	%r14,0x80000620 <pthread_barrier_wait@plt>
   0x0000000080000848 <+32>:	j	0x8000088c <child_function+100>
   0x000000008000084c <+36>:	larl	%r1,0x80001d30 <counter>
   0x0000000080000852 <+42>:	l	%r1,0(%r1)
   0x0000000080000856 <+46>:	ahi	%r1,1
   0x000000008000085a <+50>:	lr	%r2,%r1
   0x000000008000085c <+52>:	larl	%r1,0x80001d30 <counter>
   0x0000000080000862 <+58>:	st	%r2,0(%r1)
=> 0x0000000080000866 <+62>:	larl	%r1,0x80001d6c <watch_me>
   0x000000008000086c <+68>:	lhi	%r2,1
   0x0000000080000870 <+72>:	st	%r2,0(%r1)
   0x0000000080000874 <+76>:	larl	%r1,0x80001d68 <other>
   0x000000008000087a <+82>:	lhi	%r2,1
   0x000000008000087e <+86>:	st	%r2,0(%r1)
   0x0000000080000882 <+90>:	lghi	%r2,1
   0x0000000080000886 <+94>:	brasl	%r14,0x80000660 <usleep@plt>
   0x000000008000088c <+100>:	larl	%r1,0x80001d30 <counter>
   0x0000000080000892 <+106>:	l	%r1,0(%r1)
   0x0000000080000896 <+110>:	ltr	%r1,%r1
   0x0000000080000898 <+112>:	jne	0x8000084c <child_function+36>
   0x000000008000089c <+116>:	lghi	%r2,0
   0x00000000800008a0 <+120>:	brasl	%r14,0x800006c0 <pthread_exit@plt>
End of assembler dump.
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: no thread-specific bp: next: find addresses: find addresses
delete breakpoints
Delete all breakpoints? (y or n) y
(gdb) info breakpoints
No breakpoints or watchpoints.
(gdb) break *0x0000000080000862
Breakpoint 5 at 0x80000862: file /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c, line 36.
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: no thread-specific bp: next: set breakpoint at address that triggers watch
continue
Continuing.
FAIL: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: no thread-specific bp: next: continue to breakpoint: run to instruction that triggers watch in thread 2 (timeout)
p counter = 0
FAIL: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: no thread-specific bp: next: unbreak loop in thread 2 (timeout)
p watch_me = 0
FAIL: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: no thread-specific bp: next: clear watch_me (timeout)
watch watch_me
FAIL: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: no thread-specific bp: next: watch watch_me (timeout)
thread 1
FAIL: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: no thread-specific bp: next: thread 1 (timeout)
set scheduler-locking off
FAIL: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: no thread-specific bp: next: set scheduler-locking off (timeout)
next
FAIL: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: no thread-specific bp: next: next (timeout)
Remote debugging from host 127.0.0.1
monitor exit
spawn /home/dje/build/GDB/gdb/testsuite/../../gdb/gdb -nw -nx -data-directory /home/dje/build/GDB/gdb/testsuite/../data-directory -ex set auto-connect-native-target off
GNU gdb (GDB) 8.0.50.20171215-git
Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "s390x-ibm-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word".
(gdb) set height 0
(gdb) set width 0
(gdb) dir
Reinitialize source path to empty? (y or n) y
Source directories searched: $cdir:$cwd
(gdb) dir /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads
Source directories searched: /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads:$cdir:$cwd
(gdb) kill
The program is not being run.
(gdb) file /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/step-over-trips-on-watchpoint/step-over-trips-on-watchpoint
Reading symbols from /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/step-over-trips-on-watchpoint/step-over-trips-on-watchpoint...done.
(gdb) delete breakpoints
(gdb) info breakpoints
No breakpoints or watchpoints.
(gdb) break main
Breakpoint 1 at 0x800008b6: file /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c, line 52.
(gdb) kill
The program is not being run.
(gdb) spawn /home/dje/build/GDB/gdb/testsuite/../gdbserver/gdbserver --once :2348 /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/step-over-trips-on-watchpoint/step-over-trips-on-watchpoint
Process /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/step-over-trips-on-watchpoint/step-over-trips-on-watchpoint created; pid = 16816
Listening on port 2348
target remote localhost:2348
Remote debugging using localhost:2348
Reading /lib/ld64.so.1 from remote target...
warning: File transfers from remote targets can be slow. Use "set sysroot" to access files locally instead.
Reading /lib/ld64.so.1 from remote target...
Reading symbols from target:/lib/ld64.so.1...Reading /lib/ld-2.19.so from remote target...
Reading /lib/.debug/ld-2.19.so from remote target...
(no debugging symbols found)...done.
0x000003fffdfd9280 in ?? () from target:/lib/ld64.so.1
(gdb) continue
Continuing.
Reading /lib/s390x-linux-gnu/libpthread.so.0 from remote target...
Reading /lib/s390x-linux-gnu/libm.so.6 from remote target...
Reading /lib/s390x-linux-gnu/libc.so.6 from remote target...
Reading /lib/s390x-linux-gnu/libpthread-2.19.so from remote target...
Reading /lib/s390x-linux-gnu/.debug/libpthread-2.19.so from remote target...
Reading /lib/s390x-linux-gnu/libm-2.19.so from remote target...
Reading /lib/s390x-linux-gnu/.debug/libm-2.19.so from remote target...
Reading /lib/s390x-linux-gnu/libc-2.19.so from remote target...
Reading /lib/s390x-linux-gnu/.debug/libc-2.19.so from remote target...

Breakpoint 1, main () at /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c:52
52	  alarm (300);
(gdb) set displaced-stepping off
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: no thread-specific bp: continue: set displaced-stepping off
break 65
Breakpoint 2 at 0x80000902: file /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c, line 65.
(gdb) continue
Continuing.
[New Thread 16816.16818]

Thread 1 "step-over-trips" hit Breakpoint 2, main () at /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c:65
65	  while (1); /* set wait-thread breakpoint here */
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: no thread-specific bp: continue: continue to breakpoint: run to wait-thread breakpoint
info threads
  Id   Target Id         Frame 
* 1    Thread 16816.16816 "step-over-trips" main () at /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c:65
  2    Thread 16816.16818 "step-over-trips" 0x000003fffde21c30 in ?? () at ../sysdeps/unix/syscall-template.S:81 from target:/lib/s390x-linux-gnu/libc.so.6
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: no thread-specific bp: continue: info threads shows all threads
set scheduler-locking on
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: no thread-specific bp: continue: set scheduler-locking on
delete breakpoints
Delete all breakpoints? (y or n) y
(gdb) info breakpoints
No breakpoints or watchpoints.
(gdb) break 38
Breakpoint 3 at 0x80000866: file /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c, line 38.
(gdb) thread 2
[Switching to thread 2 (Thread 16816.16818)]
#0  0x000003fffde21c30 in ?? () at ../sysdeps/unix/syscall-template.S:81 from target:/lib/s390x-linux-gnu/libc.so.6
81	../sysdeps/unix/syscall-template.S: No such file or directory.
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: no thread-specific bp: continue: thread 2
continue
Continuing.

Thread 2 "step-over-trips" hit Breakpoint 3, child_function (arg=0x0) at /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c:38
38	      watch_me = 1; /* set breakpoint child here */
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: no thread-specific bp: continue: continue to breakpoint: run to breakpoint in thread 2
p watch_me = 0
$1 = 0
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: no thread-specific bp: continue: find addresses: clear watch_me
watch watch_me
Hardware watchpoint 4: watch_me
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: no thread-specific bp: continue: find addresses: watch watch_me
continue
Continuing.
Warning:
Could not insert hardware watchpoint 4.
Could not insert hardware breakpoints:
You may have requested too many hardware breakpoints/watchpoints.

Command aborted.
(gdb) FAIL: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: no thread-specific bp: continue: find addresses: continue to watchpoint
disassemble
Dump of assembler code for function child_function:
   0x0000000080000828 <+0>:	stmg	%r11,%r15,88(%r15)
   0x000000008000082e <+6>:	aghi	%r15,-168
   0x0000000080000832 <+10>:	lgr	%r11,%r15
   0x0000000080000836 <+14>:	stg	%r2,160(%r11)
   0x000000008000083c <+20>:	larl	%r2,0x80001d40 <barrier>
   0x0000000080000842 <+26>:	brasl	%r14,0x80000620 <pthread_barrier_wait@plt>
   0x0000000080000848 <+32>:	j	0x8000088c <child_function+100>
   0x000000008000084c <+36>:	larl	%r1,0x80001d30 <counter>
   0x0000000080000852 <+42>:	l	%r1,0(%r1)
   0x0000000080000856 <+46>:	ahi	%r1,1
   0x000000008000085a <+50>:	lr	%r2,%r1
   0x000000008000085c <+52>:	larl	%r1,0x80001d30 <counter>
   0x0000000080000862 <+58>:	st	%r2,0(%r1)
=> 0x0000000080000866 <+62>:	larl	%r1,0x80001d6c <watch_me>
   0x000000008000086c <+68>:	lhi	%r2,1
   0x0000000080000870 <+72>:	st	%r2,0(%r1)
   0x0000000080000874 <+76>:	larl	%r1,0x80001d68 <other>
   0x000000008000087a <+82>:	lhi	%r2,1
   0x000000008000087e <+86>:	st	%r2,0(%r1)
   0x0000000080000882 <+90>:	lghi	%r2,1
   0x0000000080000886 <+94>:	brasl	%r14,0x80000660 <usleep@plt>
   0x000000008000088c <+100>:	larl	%r1,0x80001d30 <counter>
   0x0000000080000892 <+106>:	l	%r1,0(%r1)
   0x0000000080000896 <+110>:	ltr	%r1,%r1
   0x0000000080000898 <+112>:	jne	0x8000084c <child_function+36>
   0x000000008000089c <+116>:	lghi	%r2,0
   0x00000000800008a0 <+120>:	brasl	%r14,0x800006c0 <pthread_exit@plt>
End of assembler dump.
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: no thread-specific bp: continue: find addresses: find addresses
delete breakpoints
Delete all breakpoints? (y or n) y
(gdb) info breakpoints
No breakpoints or watchpoints.
(gdb) break *0x0000000080000862
Breakpoint 5 at 0x80000862: file /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c, line 36.
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: no thread-specific bp: continue: set breakpoint at address that triggers watch
continue
Continuing.
FAIL: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: no thread-specific bp: continue: continue to breakpoint: run to instruction that triggers watch in thread 2 (timeout)
p counter = 0
FAIL: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: no thread-specific bp: continue: unbreak loop in thread 2 (timeout)
p watch_me = 0
FAIL: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: no thread-specific bp: continue: clear watch_me (timeout)
watch watch_me
FAIL: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: no thread-specific bp: continue: watch watch_me (timeout)
thread 1
FAIL: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: no thread-specific bp: continue: thread 1 (timeout)
set scheduler-locking off
FAIL: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: no thread-specific bp: continue: set scheduler-locking off (timeout)
continue
FAIL: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: no thread-specific bp: continue: continue (timeout)
Remote debugging from host 127.0.0.1
monitor exit
spawn /home/dje/build/GDB/gdb/testsuite/../../gdb/gdb -nw -nx -data-directory /home/dje/build/GDB/gdb/testsuite/../data-directory -ex set auto-connect-native-target off
GNU gdb (GDB) 8.0.50.20171215-git
Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "s390x-ibm-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word".
(gdb) set height 0
(gdb) set width 0
(gdb) dir
Reinitialize source path to empty? (y or n) y
Source directories searched: $cdir:$cwd
(gdb) dir /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads
Source directories searched: /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads:$cdir:$cwd
(gdb) kill
The program is not being run.
(gdb) file /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/step-over-trips-on-watchpoint/step-over-trips-on-watchpoint
Reading symbols from /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/step-over-trips-on-watchpoint/step-over-trips-on-watchpoint...done.
(gdb) delete breakpoints
(gdb) info breakpoints
No breakpoints or watchpoints.
(gdb) break main
Breakpoint 1 at 0x800008b6: file /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c, line 52.
(gdb) kill
The program is not being run.
(gdb) spawn /home/dje/build/GDB/gdb/testsuite/../gdbserver/gdbserver --once :2349 /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/step-over-trips-on-watchpoint/step-over-trips-on-watchpoint
Process /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/step-over-trips-on-watchpoint/step-over-trips-on-watchpoint created; pid = 16893
Listening on port 2349
target remote localhost:2349
Remote debugging using localhost:2349
Reading /lib/ld64.so.1 from remote target...
warning: File transfers from remote targets can be slow. Use "set sysroot" to access files locally instead.
Reading /lib/ld64.so.1 from remote target...
Reading symbols from target:/lib/ld64.so.1...Reading /lib/ld-2.19.so from remote target...
Reading /lib/.debug/ld-2.19.so from remote target...
(no debugging symbols found)...done.
0x000003fffdfd9280 in ?? () from target:/lib/ld64.so.1
(gdb) continue
Continuing.
Reading /lib/s390x-linux-gnu/libpthread.so.0 from remote target...
Reading /lib/s390x-linux-gnu/libm.so.6 from remote target...
Reading /lib/s390x-linux-gnu/libc.so.6 from remote target...
Reading /lib/s390x-linux-gnu/libpthread-2.19.so from remote target...
Reading /lib/s390x-linux-gnu/.debug/libpthread-2.19.so from remote target...
Reading /lib/s390x-linux-gnu/libm-2.19.so from remote target...
Reading /lib/s390x-linux-gnu/.debug/libm-2.19.so from remote target...
Reading /lib/s390x-linux-gnu/libc-2.19.so from remote target...
Reading /lib/s390x-linux-gnu/.debug/libc-2.19.so from remote target...

Breakpoint 1, main () at /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c:52
52	  alarm (300);
(gdb) set displaced-stepping off
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: with thread-specific bp: step: set displaced-stepping off
break 65
Breakpoint 2 at 0x80000902: file /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c, line 65.
(gdb) continue
Continuing.
[New Thread 16893.16894]

Thread 1 "step-over-trips" hit Breakpoint 2, main () at /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c:65
65	  while (1); /* set wait-thread breakpoint here */
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: with thread-specific bp: step: continue to breakpoint: run to wait-thread breakpoint
info threads
  Id   Target Id         Frame 
* 1    Thread 16893.16893 "step-over-trips" main () at /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c:65
  2    Thread 16893.16894 "step-over-trips" 0x000003fffde21c30 in ?? () at ../sysdeps/unix/syscall-template.S:81 from target:/lib/s390x-linux-gnu/libc.so.6
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: with thread-specific bp: step: info threads shows all threads
set scheduler-locking on
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: with thread-specific bp: step: set scheduler-locking on
delete breakpoints
Delete all breakpoints? (y or n) y
(gdb) info breakpoints
No breakpoints or watchpoints.
(gdb) break 38
Breakpoint 3 at 0x80000866: file /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c, line 38.
(gdb) thread 2
[Switching to thread 2 (Thread 16893.16894)]
#0  0x000003fffde21c30 in ?? () at ../sysdeps/unix/syscall-template.S:81 from target:/lib/s390x-linux-gnu/libc.so.6
81	../sysdeps/unix/syscall-template.S: No such file or directory.
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: with thread-specific bp: step: thread 2
continue
Continuing.

Thread 2 "step-over-trips" hit Breakpoint 3, child_function (arg=0x0) at /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c:38
38	      watch_me = 1; /* set breakpoint child here */
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: with thread-specific bp: step: continue to breakpoint: run to breakpoint in thread 2
p watch_me = 0
$1 = 0
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: with thread-specific bp: step: find addresses: clear watch_me
watch watch_me
Hardware watchpoint 4: watch_me
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: with thread-specific bp: step: find addresses: watch watch_me
continue
Continuing.
Warning:
Could not insert hardware watchpoint 4.
Could not insert hardware breakpoints:
You may have requested too many hardware breakpoints/watchpoints.

Command aborted.
(gdb) FAIL: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: with thread-specific bp: step: find addresses: continue to watchpoint
disassemble
Dump of assembler code for function child_function:
   0x0000000080000828 <+0>:	stmg	%r11,%r15,88(%r15)
   0x000000008000082e <+6>:	aghi	%r15,-168
   0x0000000080000832 <+10>:	lgr	%r11,%r15
   0x0000000080000836 <+14>:	stg	%r2,160(%r11)
   0x000000008000083c <+20>:	larl	%r2,0x80001d40 <barrier>
   0x0000000080000842 <+26>:	brasl	%r14,0x80000620 <pthread_barrier_wait@plt>
   0x0000000080000848 <+32>:	j	0x8000088c <child_function+100>
   0x000000008000084c <+36>:	larl	%r1,0x80001d30 <counter>
   0x0000000080000852 <+42>:	l	%r1,0(%r1)
   0x0000000080000856 <+46>:	ahi	%r1,1
   0x000000008000085a <+50>:	lr	%r2,%r1
   0x000000008000085c <+52>:	larl	%r1,0x80001d30 <counter>
   0x0000000080000862 <+58>:	st	%r2,0(%r1)
=> 0x0000000080000866 <+62>:	larl	%r1,0x80001d6c <watch_me>
   0x000000008000086c <+68>:	lhi	%r2,1
   0x0000000080000870 <+72>:	st	%r2,0(%r1)
   0x0000000080000874 <+76>:	larl	%r1,0x80001d68 <other>
   0x000000008000087a <+82>:	lhi	%r2,1
   0x000000008000087e <+86>:	st	%r2,0(%r1)
   0x0000000080000882 <+90>:	lghi	%r2,1
   0x0000000080000886 <+94>:	brasl	%r14,0x80000660 <usleep@plt>
   0x000000008000088c <+100>:	larl	%r1,0x80001d30 <counter>
   0x0000000080000892 <+106>:	l	%r1,0(%r1)
   0x0000000080000896 <+110>:	ltr	%r1,%r1
   0x0000000080000898 <+112>:	jne	0x8000084c <child_function+36>
   0x000000008000089c <+116>:	lghi	%r2,0
   0x00000000800008a0 <+120>:	brasl	%r14,0x800006c0 <pthread_exit@plt>
End of assembler dump.
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: with thread-specific bp: step: find addresses: find addresses
delete breakpoints
Delete all breakpoints? (y or n) y
(gdb) info breakpoints
No breakpoints or watchpoints.
(gdb) break *0x0000000080000862
Breakpoint 5 at 0x80000862: file /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c, line 36.
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: with thread-specific bp: step: set breakpoint at address that triggers watch
continue
Continuing.
FAIL: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: with thread-specific bp: step: continue to breakpoint: run to instruction that triggers watch in thread 2 (timeout)
p counter = 0
FAIL: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: with thread-specific bp: step: unbreak loop in thread 2 (timeout)
p watch_me = 0
FAIL: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: with thread-specific bp: step: clear watch_me (timeout)
watch watch_me
FAIL: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: with thread-specific bp: step: watch watch_me (timeout)
b *0x0000000080000866 thread 1
FAIL: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: with thread-specific bp: step: set breakpoint specific to thread 1 (timeout)
thread 1
FAIL: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: with thread-specific bp: step: thread 1 (timeout)
set scheduler-locking off
FAIL: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: with thread-specific bp: step: set scheduler-locking off (timeout)
step
FAIL: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: with thread-specific bp: step: step (timeout)
Remote debugging from host 127.0.0.1
monitor exit
spawn /home/dje/build/GDB/gdb/testsuite/../../gdb/gdb -nw -nx -data-directory /home/dje/build/GDB/gdb/testsuite/../data-directory -ex set auto-connect-native-target off
GNU gdb (GDB) 8.0.50.20171215-git
Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "s390x-ibm-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word".
(gdb) set height 0
(gdb) set width 0
(gdb) dir
Reinitialize source path to empty? (y or n) y
Source directories searched: $cdir:$cwd
(gdb) dir /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads
Source directories searched: /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads:$cdir:$cwd
(gdb) kill
The program is not being run.
(gdb) file /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/step-over-trips-on-watchpoint/step-over-trips-on-watchpoint
Reading symbols from /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/step-over-trips-on-watchpoint/step-over-trips-on-watchpoint...done.
(gdb) delete breakpoints
(gdb) info breakpoints
No breakpoints or watchpoints.
(gdb) break main
Breakpoint 1 at 0x800008b6: file /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c, line 52.
(gdb) kill
The program is not being run.
(gdb) spawn /home/dje/build/GDB/gdb/testsuite/../gdbserver/gdbserver --once :2350 /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/step-over-trips-on-watchpoint/step-over-trips-on-watchpoint
Process /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/step-over-trips-on-watchpoint/step-over-trips-on-watchpoint created; pid = 16945
Listening on port 2350
target remote localhost:2350
Remote debugging using localhost:2350
Reading /lib/ld64.so.1 from remote target...
warning: File transfers from remote targets can be slow. Use "set sysroot" to access files locally instead.
Reading /lib/ld64.so.1 from remote target...
Reading symbols from target:/lib/ld64.so.1...Reading /lib/ld-2.19.so from remote target...
Reading /lib/.debug/ld-2.19.so from remote target...
(no debugging symbols found)...done.
0x000003fffdfd9280 in ?? () from target:/lib/ld64.so.1
(gdb) continue
Continuing.
Reading /lib/s390x-linux-gnu/libpthread.so.0 from remote target...
Reading /lib/s390x-linux-gnu/libm.so.6 from remote target...
Reading /lib/s390x-linux-gnu/libc.so.6 from remote target...
Reading /lib/s390x-linux-gnu/libpthread-2.19.so from remote target...
Reading /lib/s390x-linux-gnu/.debug/libpthread-2.19.so from remote target...
Reading /lib/s390x-linux-gnu/libm-2.19.so from remote target...
Reading /lib/s390x-linux-gnu/.debug/libm-2.19.so from remote target...
Reading /lib/s390x-linux-gnu/libc-2.19.so from remote target...
Reading /lib/s390x-linux-gnu/.debug/libc-2.19.so from remote target...

Breakpoint 1, main () at /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c:52
52	  alarm (300);
(gdb) set displaced-stepping off
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: with thread-specific bp: next: set displaced-stepping off
break 65
Breakpoint 2 at 0x80000902: file /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c, line 65.
(gdb) continue
Continuing.
[New Thread 16945.16946]

Thread 1 "step-over-trips" hit Breakpoint 2, main () at /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c:65
65	  while (1); /* set wait-thread breakpoint here */
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: with thread-specific bp: next: continue to breakpoint: run to wait-thread breakpoint
info threads
  Id   Target Id         Frame 
* 1    Thread 16945.16945 "step-over-trips" main () at /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c:65
  2    Thread 16945.16946 "step-over-trips" 0x000003fffde21c30 in ?? () at ../sysdeps/unix/syscall-template.S:81 from target:/lib/s390x-linux-gnu/libc.so.6
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: with thread-specific bp: next: info threads shows all threads
set scheduler-locking on
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: with thread-specific bp: next: set scheduler-locking on
delete breakpoints
Delete all breakpoints? (y or n) y
(gdb) info breakpoints
No breakpoints or watchpoints.
(gdb) break 38
Breakpoint 3 at 0x80000866: file /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c, line 38.
(gdb) thread 2
[Switching to thread 2 (Thread 16945.16946)]
#0  0x000003fffde21c30 in ?? () at ../sysdeps/unix/syscall-template.S:81 from target:/lib/s390x-linux-gnu/libc.so.6
81	../sysdeps/unix/syscall-template.S: No such file or directory.
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: with thread-specific bp: next: thread 2
continue
Continuing.

Thread 2 "step-over-trips" hit Breakpoint 3, child_function (arg=0x0) at /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c:38
38	      watch_me = 1; /* set breakpoint child here */
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: with thread-specific bp: next: continue to breakpoint: run to breakpoint in thread 2
p watch_me = 0
$1 = 0
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: with thread-specific bp: next: find addresses: clear watch_me
watch watch_me
Hardware watchpoint 4: watch_me
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: with thread-specific bp: next: find addresses: watch watch_me
continue
Continuing.
Warning:
Could not insert hardware watchpoint 4.
Could not insert hardware breakpoints:
You may have requested too many hardware breakpoints/watchpoints.

Command aborted.
(gdb) FAIL: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: with thread-specific bp: next: find addresses: continue to watchpoint
disassemble
Dump of assembler code for function child_function:
   0x0000000080000828 <+0>:	stmg	%r11,%r15,88(%r15)
   0x000000008000082e <+6>:	aghi	%r15,-168
   0x0000000080000832 <+10>:	lgr	%r11,%r15
   0x0000000080000836 <+14>:	stg	%r2,160(%r11)
   0x000000008000083c <+20>:	larl	%r2,0x80001d40 <barrier>
   0x0000000080000842 <+26>:	brasl	%r14,0x80000620 <pthread_barrier_wait@plt>
   0x0000000080000848 <+32>:	j	0x8000088c <child_function+100>
   0x000000008000084c <+36>:	larl	%r1,0x80001d30 <counter>
   0x0000000080000852 <+42>:	l	%r1,0(%r1)
   0x0000000080000856 <+46>:	ahi	%r1,1
   0x000000008000085a <+50>:	lr	%r2,%r1
   0x000000008000085c <+52>:	larl	%r1,0x80001d30 <counter>
   0x0000000080000862 <+58>:	st	%r2,0(%r1)
=> 0x0000000080000866 <+62>:	larl	%r1,0x80001d6c <watch_me>
   0x000000008000086c <+68>:	lhi	%r2,1
   0x0000000080000870 <+72>:	st	%r2,0(%r1)
   0x0000000080000874 <+76>:	larl	%r1,0x80001d68 <other>
   0x000000008000087a <+82>:	lhi	%r2,1
   0x000000008000087e <+86>:	st	%r2,0(%r1)
   0x0000000080000882 <+90>:	lghi	%r2,1
   0x0000000080000886 <+94>:	brasl	%r14,0x80000660 <usleep@plt>
   0x000000008000088c <+100>:	larl	%r1,0x80001d30 <counter>
   0x0000000080000892 <+106>:	l	%r1,0(%r1)
   0x0000000080000896 <+110>:	ltr	%r1,%r1
   0x0000000080000898 <+112>:	jne	0x8000084c <child_function+36>
   0x000000008000089c <+116>:	lghi	%r2,0
   0x00000000800008a0 <+120>:	brasl	%r14,0x800006c0 <pthread_exit@plt>
End of assembler dump.
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: with thread-specific bp: next: find addresses: find addresses
delete breakpoints
Delete all breakpoints? (y or n) y
(gdb) info breakpoints
No breakpoints or watchpoints.
(gdb) break *0x0000000080000862
Breakpoint 5 at 0x80000862: file /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c, line 36.
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: with thread-specific bp: next: set breakpoint at address that triggers watch
continue
Continuing.
FAIL: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: with thread-specific bp: next: continue to breakpoint: run to instruction that triggers watch in thread 2 (timeout)
p counter = 0
FAIL: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: with thread-specific bp: next: unbreak loop in thread 2 (timeout)
p watch_me = 0
FAIL: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: with thread-specific bp: next: clear watch_me (timeout)
watch watch_me
FAIL: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: with thread-specific bp: next: watch watch_me (timeout)
b *0x0000000080000866 thread 1
FAIL: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: with thread-specific bp: next: set breakpoint specific to thread 1 (timeout)
thread 1
FAIL: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: with thread-specific bp: next: thread 1 (timeout)
set scheduler-locking off
FAIL: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: with thread-specific bp: next: set scheduler-locking off (timeout)
next
FAIL: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: with thread-specific bp: next: next (timeout)
Remote debugging from host 127.0.0.1
monitor exit
spawn /home/dje/build/GDB/gdb/testsuite/../../gdb/gdb -nw -nx -data-directory /home/dje/build/GDB/gdb/testsuite/../data-directory -ex set auto-connect-native-target off
GNU gdb (GDB) 8.0.50.20171215-git
Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "s390x-ibm-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word".
(gdb) set height 0
(gdb) set width 0
(gdb) dir
Reinitialize source path to empty? (y or n) y
Source directories searched: $cdir:$cwd
(gdb) dir /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads
Source directories searched: /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads:$cdir:$cwd
(gdb) kill
The program is not being run.
(gdb) file /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/step-over-trips-on-watchpoint/step-over-trips-on-watchpoint
Reading symbols from /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/step-over-trips-on-watchpoint/step-over-trips-on-watchpoint...done.
(gdb) delete breakpoints
(gdb) info breakpoints
No breakpoints or watchpoints.
(gdb) break main
Breakpoint 1 at 0x800008b6: file /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c, line 52.
(gdb) kill
The program is not being run.
(gdb) spawn /home/dje/build/GDB/gdb/testsuite/../gdbserver/gdbserver --once :2351 /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/step-over-trips-on-watchpoint/step-over-trips-on-watchpoint
Process /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/step-over-trips-on-watchpoint/step-over-trips-on-watchpoint created; pid = 16976
Listening on port 2351
target remote localhost:2351
Remote debugging using localhost:2351
Reading /lib/ld64.so.1 from remote target...
warning: File transfers from remote targets can be slow. Use "set sysroot" to access files locally instead.
Reading /lib/ld64.so.1 from remote target...
Reading symbols from target:/lib/ld64.so.1...Reading /lib/ld-2.19.so from remote target...
Reading /lib/.debug/ld-2.19.so from remote target...
(no debugging symbols found)...done.
0x000003fffdfd9280 in ?? () from target:/lib/ld64.so.1
(gdb) continue
Continuing.
Reading /lib/s390x-linux-gnu/libpthread.so.0 from remote target...
Reading /lib/s390x-linux-gnu/libm.so.6 from remote target...
Reading /lib/s390x-linux-gnu/libc.so.6 from remote target...
Reading /lib/s390x-linux-gnu/libpthread-2.19.so from remote target...
Reading /lib/s390x-linux-gnu/.debug/libpthread-2.19.so from remote target...
Reading /lib/s390x-linux-gnu/libm-2.19.so from remote target...
Reading /lib/s390x-linux-gnu/.debug/libm-2.19.so from remote target...
Reading /lib/s390x-linux-gnu/libc-2.19.so from remote target...
Reading /lib/s390x-linux-gnu/.debug/libc-2.19.so from remote target...

Breakpoint 1, main () at /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c:52
52	  alarm (300);
(gdb) set displaced-stepping off
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: with thread-specific bp: continue: set displaced-stepping off
break 65
Breakpoint 2 at 0x80000902: file /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c, line 65.
(gdb) continue
Continuing.
[New Thread 16976.16977]

Thread 1 "step-over-trips" hit Breakpoint 2, main () at /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c:65
65	  while (1); /* set wait-thread breakpoint here */
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: with thread-specific bp: continue: continue to breakpoint: run to wait-thread breakpoint
info threads
  Id   Target Id         Frame 
* 1    Thread 16976.16976 "step-over-trips" main () at /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c:65
  2    Thread 16976.16977 "step-over-trips" 0x000003fffde21c30 in ?? () at ../sysdeps/unix/syscall-template.S:81 from target:/lib/s390x-linux-gnu/libc.so.6
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: with thread-specific bp: continue: info threads shows all threads
set scheduler-locking on
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: with thread-specific bp: continue: set scheduler-locking on
delete breakpoints
Delete all breakpoints? (y or n) y
(gdb) info breakpoints
No breakpoints or watchpoints.
(gdb) break 38
Breakpoint 3 at 0x80000866: file /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c, line 38.
(gdb) thread 2
[Switching to thread 2 (Thread 16976.16977)]
#0  0x000003fffde21c30 in ?? () at ../sysdeps/unix/syscall-template.S:81 from target:/lib/s390x-linux-gnu/libc.so.6
81	../sysdeps/unix/syscall-template.S: No such file or directory.
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: with thread-specific bp: continue: thread 2
continue
Continuing.

Thread 2 "step-over-trips" hit Breakpoint 3, child_function (arg=0x0) at /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c:38
38	      watch_me = 1; /* set breakpoint child here */
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: with thread-specific bp: continue: continue to breakpoint: run to breakpoint in thread 2
p watch_me = 0
$1 = 0
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: with thread-specific bp: continue: find addresses: clear watch_me
watch watch_me
Hardware watchpoint 4: watch_me
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: with thread-specific bp: continue: find addresses: watch watch_me
continue
Continuing.
Warning:
Could not insert hardware watchpoint 4.
Could not insert hardware breakpoints:
You may have requested too many hardware breakpoints/watchpoints.

Command aborted.
(gdb) FAIL: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: with thread-specific bp: continue: find addresses: continue to watchpoint
disassemble
Dump of assembler code for function child_function:
   0x0000000080000828 <+0>:	stmg	%r11,%r15,88(%r15)
   0x000000008000082e <+6>:	aghi	%r15,-168
   0x0000000080000832 <+10>:	lgr	%r11,%r15
   0x0000000080000836 <+14>:	stg	%r2,160(%r11)
   0x000000008000083c <+20>:	larl	%r2,0x80001d40 <barrier>
   0x0000000080000842 <+26>:	brasl	%r14,0x80000620 <pthread_barrier_wait@plt>
   0x0000000080000848 <+32>:	j	0x8000088c <child_function+100>
   0x000000008000084c <+36>:	larl	%r1,0x80001d30 <counter>
   0x0000000080000852 <+42>:	l	%r1,0(%r1)
   0x0000000080000856 <+46>:	ahi	%r1,1
   0x000000008000085a <+50>:	lr	%r2,%r1
   0x000000008000085c <+52>:	larl	%r1,0x80001d30 <counter>
   0x0000000080000862 <+58>:	st	%r2,0(%r1)
=> 0x0000000080000866 <+62>:	larl	%r1,0x80001d6c <watch_me>
   0x000000008000086c <+68>:	lhi	%r2,1
   0x0000000080000870 <+72>:	st	%r2,0(%r1)
   0x0000000080000874 <+76>:	larl	%r1,0x80001d68 <other>
   0x000000008000087a <+82>:	lhi	%r2,1
   0x000000008000087e <+86>:	st	%r2,0(%r1)
   0x0000000080000882 <+90>:	lghi	%r2,1
   0x0000000080000886 <+94>:	brasl	%r14,0x80000660 <usleep@plt>
   0x000000008000088c <+100>:	larl	%r1,0x80001d30 <counter>
   0x0000000080000892 <+106>:	l	%r1,0(%r1)
   0x0000000080000896 <+110>:	ltr	%r1,%r1
   0x0000000080000898 <+112>:	jne	0x8000084c <child_function+36>
   0x000000008000089c <+116>:	lghi	%r2,0
   0x00000000800008a0 <+120>:	brasl	%r14,0x800006c0 <pthread_exit@plt>
End of assembler dump.
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: with thread-specific bp: continue: find addresses: find addresses
delete breakpoints
Delete all breakpoints? (y or n) y
(gdb) info breakpoints
No breakpoints or watchpoints.
(gdb) break *0x0000000080000862
Breakpoint 5 at 0x80000862: file /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c, line 36.
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: with thread-specific bp: continue: set breakpoint at address that triggers watch
continue
Continuing.
FAIL: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: with thread-specific bp: continue: continue to breakpoint: run to instruction that triggers watch in thread 2 (timeout)
p counter = 0
FAIL: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: with thread-specific bp: continue: unbreak loop in thread 2 (timeout)
p watch_me = 0
FAIL: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: with thread-specific bp: continue: clear watch_me (timeout)
watch watch_me
FAIL: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: with thread-specific bp: continue: watch watch_me (timeout)
b *0x0000000080000866 thread 1
FAIL: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: with thread-specific bp: continue: set breakpoint specific to thread 1 (timeout)
thread 1
FAIL: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: with thread-specific bp: continue: thread 1 (timeout)
set scheduler-locking off
FAIL: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: with thread-specific bp: continue: set scheduler-locking off (timeout)
continue
FAIL: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=off: with thread-specific bp: continue: continue (timeout)
Remote debugging from host 127.0.0.1
monitor exit
spawn /home/dje/build/GDB/gdb/testsuite/../../gdb/gdb -nw -nx -data-directory /home/dje/build/GDB/gdb/testsuite/../data-directory -ex set auto-connect-native-target off
GNU gdb (GDB) 8.0.50.20171215-git
Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "s390x-ibm-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word".
(gdb) set height 0
(gdb) set width 0
(gdb) dir
Reinitialize source path to empty? (y or n) y
Source directories searched: $cdir:$cwd
(gdb) dir /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads
Source directories searched: /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads:$cdir:$cwd
(gdb) kill
The program is not being run.
(gdb) file /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/step-over-trips-on-watchpoint/step-over-trips-on-watchpoint
Reading symbols from /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/step-over-trips-on-watchpoint/step-over-trips-on-watchpoint...done.
(gdb) delete breakpoints
(gdb) info breakpoints
No breakpoints or watchpoints.
(gdb) break main
Breakpoint 1 at 0x800008b6: file /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c, line 52.
(gdb) kill
The program is not being run.
(gdb) spawn /home/dje/build/GDB/gdb/testsuite/../gdbserver/gdbserver --once :2352 /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/step-over-trips-on-watchpoint/step-over-trips-on-watchpoint
Process /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/step-over-trips-on-watchpoint/step-over-trips-on-watchpoint created; pid = 16995
Listening on port 2352
target remote localhost:2352
Remote debugging using localhost:2352
Reading /lib/ld64.so.1 from remote target...
warning: File transfers from remote targets can be slow. Use "set sysroot" to access files locally instead.
Reading /lib/ld64.so.1 from remote target...
Reading symbols from target:/lib/ld64.so.1...Reading /lib/ld-2.19.so from remote target...
Reading /lib/.debug/ld-2.19.so from remote target...
(no debugging symbols found)...done.
0x000003fffdfd9280 in ?? () from target:/lib/ld64.so.1
(gdb) continue
Continuing.
Reading /lib/s390x-linux-gnu/libpthread.so.0 from remote target...
Reading /lib/s390x-linux-gnu/libm.so.6 from remote target...
Reading /lib/s390x-linux-gnu/libc.so.6 from remote target...
Reading /lib/s390x-linux-gnu/libpthread-2.19.so from remote target...
Reading /lib/s390x-linux-gnu/.debug/libpthread-2.19.so from remote target...
Reading /lib/s390x-linux-gnu/libm-2.19.so from remote target...
Reading /lib/s390x-linux-gnu/.debug/libm-2.19.so from remote target...
Reading /lib/s390x-linux-gnu/libc-2.19.so from remote target...
Reading /lib/s390x-linux-gnu/.debug/libc-2.19.so from remote target...

Breakpoint 1, main () at /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c:52
52	  alarm (300);
(gdb) set displaced-stepping on
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: no thread-specific bp: step: set displaced-stepping on
break 65
Breakpoint 2 at 0x80000902: file /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c, line 65.
(gdb) continue
Continuing.
[New Thread 16995.16996]

Thread 1 "step-over-trips" hit Breakpoint 2, main () at /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c:65
65	  while (1); /* set wait-thread breakpoint here */
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: no thread-specific bp: step: continue to breakpoint: run to wait-thread breakpoint
info threads
  Id   Target Id         Frame 
* 1    Thread 16995.16995 "step-over-trips" main () at /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c:65
  2    Thread 16995.16996 "step-over-trips" 0x000003fffde21c30 in ?? () at ../sysdeps/unix/syscall-template.S:81 from target:/lib/s390x-linux-gnu/libc.so.6
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: no thread-specific bp: step: info threads shows all threads
set scheduler-locking on
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: no thread-specific bp: step: set scheduler-locking on
delete breakpoints
Delete all breakpoints? (y or n) y
(gdb) info breakpoints
No breakpoints or watchpoints.
(gdb) break 38
Breakpoint 3 at 0x80000866: file /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c, line 38.
(gdb) thread 2
[Switching to thread 2 (Thread 16995.16996)]
#0  0x000003fffde21c30 in ?? () at ../sysdeps/unix/syscall-template.S:81 from target:/lib/s390x-linux-gnu/libc.so.6
81	../sysdeps/unix/syscall-template.S: No such file or directory.
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: no thread-specific bp: step: thread 2
continue
Continuing.

Thread 2 "step-over-trips" hit Breakpoint 3, child_function (arg=0x0) at /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c:38
38	      watch_me = 1; /* set breakpoint child here */
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: no thread-specific bp: step: continue to breakpoint: run to breakpoint in thread 2
p watch_me = 0
$1 = 0
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: no thread-specific bp: step: find addresses: clear watch_me
watch watch_me
Hardware watchpoint 4: watch_me
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: no thread-specific bp: step: find addresses: watch watch_me
continue
Continuing.
Warning:
Could not insert hardware watchpoint 4.
Could not insert hardware breakpoints:
You may have requested too many hardware breakpoints/watchpoints.

Command aborted.
(gdb) FAIL: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: no thread-specific bp: step: find addresses: continue to watchpoint
disassemble
Dump of assembler code for function child_function:
   0x0000000080000828 <+0>:	stmg	%r11,%r15,88(%r15)
   0x000000008000082e <+6>:	aghi	%r15,-168
   0x0000000080000832 <+10>:	lgr	%r11,%r15
   0x0000000080000836 <+14>:	stg	%r2,160(%r11)
   0x000000008000083c <+20>:	larl	%r2,0x80001d40 <barrier>
   0x0000000080000842 <+26>:	brasl	%r14,0x80000620 <pthread_barrier_wait@plt>
   0x0000000080000848 <+32>:	j	0x8000088c <child_function+100>
   0x000000008000084c <+36>:	larl	%r1,0x80001d30 <counter>
   0x0000000080000852 <+42>:	l	%r1,0(%r1)
   0x0000000080000856 <+46>:	ahi	%r1,1
   0x000000008000085a <+50>:	lr	%r2,%r1
   0x000000008000085c <+52>:	larl	%r1,0x80001d30 <counter>
   0x0000000080000862 <+58>:	st	%r2,0(%r1)
=> 0x0000000080000866 <+62>:	larl	%r1,0x80001d6c <watch_me>
   0x000000008000086c <+68>:	lhi	%r2,1
   0x0000000080000870 <+72>:	st	%r2,0(%r1)
   0x0000000080000874 <+76>:	larl	%r1,0x80001d68 <other>
   0x000000008000087a <+82>:	lhi	%r2,1
   0x000000008000087e <+86>:	st	%r2,0(%r1)
   0x0000000080000882 <+90>:	lghi	%r2,1
   0x0000000080000886 <+94>:	brasl	%r14,0x80000660 <usleep@plt>
   0x000000008000088c <+100>:	larl	%r1,0x80001d30 <counter>
   0x0000000080000892 <+106>:	l	%r1,0(%r1)
   0x0000000080000896 <+110>:	ltr	%r1,%r1
   0x0000000080000898 <+112>:	jne	0x8000084c <child_function+36>
   0x000000008000089c <+116>:	lghi	%r2,0
   0x00000000800008a0 <+120>:	brasl	%r14,0x800006c0 <pthread_exit@plt>
End of assembler dump.
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: no thread-specific bp: step: find addresses: find addresses
delete breakpoints
Delete all breakpoints? (y or n) y
(gdb) info breakpoints
No breakpoints or watchpoints.
(gdb) break *0x0000000080000862
Breakpoint 5 at 0x80000862: file /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c, line 36.
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: no thread-specific bp: step: set breakpoint at address that triggers watch
continue
Continuing.

Thread 2 "step-over-trips" hit Breakpoint 5, 0x0000000080000862 in child_function (arg=0x0) at /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c:36
36	      counter++;
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: no thread-specific bp: step: continue to breakpoint: run to instruction that triggers watch in thread 2
p counter = 0
$2 = 0
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: no thread-specific bp: step: unbreak loop in thread 2
p watch_me = 0
$3 = 0
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: no thread-specific bp: step: clear watch_me
watch watch_me
Hardware watchpoint 6: watch_me
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: no thread-specific bp: step: watch watch_me
thread 1
[Switching to thread 1 (Thread 16995.16995)]
#0  main () at /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c:65
65	  while (1); /* set wait-thread breakpoint here */
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: no thread-specific bp: step: thread 1
set scheduler-locking off
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: no thread-specific bp: step: set scheduler-locking off
step
Warning:
Could not insert hardware watchpoint 6.
Could not insert hardware breakpoints:
You may have requested too many hardware breakpoints/watchpoints.

Command aborted.
(gdb) FAIL: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: no thread-specific bp: step: step
Remote debugging from host 127.0.0.1
monitor exit
Killing process(es): 16995
spawn /home/dje/build/GDB/gdb/testsuite/../../gdb/gdb -nw -nx -data-directory /home/dje/build/GDB/gdb/testsuite/../data-directory -ex set auto-connect-native-target off
GNU gdb (GDB) 8.0.50.20171215-git
Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "s390x-ibm-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word".
(gdb) set height 0
(gdb) set width 0
(gdb) dir
Reinitialize source path to empty? (y or n) y
Source directories searched: $cdir:$cwd
(gdb) dir /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads
Source directories searched: /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads:$cdir:$cwd
(gdb) kill
The program is not being run.
(gdb) file /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/step-over-trips-on-watchpoint/step-over-trips-on-watchpoint
Reading symbols from /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/step-over-trips-on-watchpoint/step-over-trips-on-watchpoint...done.
(gdb) delete breakpoints
(gdb) info breakpoints
No breakpoints or watchpoints.
(gdb) break main
Breakpoint 1 at 0x800008b6: file /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c, line 52.
(gdb) kill
The program is not being run.
(gdb) spawn /home/dje/build/GDB/gdb/testsuite/../gdbserver/gdbserver --once :2353 /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/step-over-trips-on-watchpoint/step-over-trips-on-watchpoint
Process /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/step-over-trips-on-watchpoint/step-over-trips-on-watchpoint created; pid = 17015
Listening on port 2353
target remote localhost:2353
Remote debugging using localhost:2353
Reading /lib/ld64.so.1 from remote target...
warning: File transfers from remote targets can be slow. Use "set sysroot" to access files locally instead.
Reading /lib/ld64.so.1 from remote target...
Reading symbols from target:/lib/ld64.so.1...Reading /lib/ld-2.19.so from remote target...
Reading /lib/.debug/ld-2.19.so from remote target...
(no debugging symbols found)...done.
0x000003fffdfd9280 in ?? () from target:/lib/ld64.so.1
(gdb) continue
Continuing.
Reading /lib/s390x-linux-gnu/libpthread.so.0 from remote target...
Reading /lib/s390x-linux-gnu/libm.so.6 from remote target...
Reading /lib/s390x-linux-gnu/libc.so.6 from remote target...
Reading /lib/s390x-linux-gnu/libpthread-2.19.so from remote target...
Reading /lib/s390x-linux-gnu/.debug/libpthread-2.19.so from remote target...
Reading /lib/s390x-linux-gnu/libm-2.19.so from remote target...
Reading /lib/s390x-linux-gnu/.debug/libm-2.19.so from remote target...
Reading /lib/s390x-linux-gnu/libc-2.19.so from remote target...
Reading /lib/s390x-linux-gnu/.debug/libc-2.19.so from remote target...

Breakpoint 1, main () at /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c:52
52	  alarm (300);
(gdb) set displaced-stepping on
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: no thread-specific bp: next: set displaced-stepping on
break 65
Breakpoint 2 at 0x80000902: file /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c, line 65.
(gdb) continue
Continuing.
[New Thread 17015.17016]

Thread 1 "step-over-trips" hit Breakpoint 2, main () at /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c:65
65	  while (1); /* set wait-thread breakpoint here */
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: no thread-specific bp: next: continue to breakpoint: run to wait-thread breakpoint
info threads
  Id   Target Id         Frame 
* 1    Thread 17015.17015 "step-over-trips" main () at /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c:65
  2    Thread 17015.17016 "step-over-trips" 0x000003fffde21c30 in ?? () at ../sysdeps/unix/syscall-template.S:81 from target:/lib/s390x-linux-gnu/libc.so.6
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: no thread-specific bp: next: info threads shows all threads
set scheduler-locking on
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: no thread-specific bp: next: set scheduler-locking on
delete breakpoints
Delete all breakpoints? (y or n) y
(gdb) info breakpoints
No breakpoints or watchpoints.
(gdb) break 38
Breakpoint 3 at 0x80000866: file /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c, line 38.
(gdb) thread 2
[Switching to thread 2 (Thread 17015.17016)]
#0  0x000003fffde21c30 in ?? () at ../sysdeps/unix/syscall-template.S:81 from target:/lib/s390x-linux-gnu/libc.so.6
81	../sysdeps/unix/syscall-template.S: No such file or directory.
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: no thread-specific bp: next: thread 2
continue
Continuing.

Thread 2 "step-over-trips" hit Breakpoint 3, child_function (arg=0x0) at /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c:38
38	      watch_me = 1; /* set breakpoint child here */
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: no thread-specific bp: next: continue to breakpoint: run to breakpoint in thread 2
p watch_me = 0
$1 = 0
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: no thread-specific bp: next: find addresses: clear watch_me
watch watch_me
Hardware watchpoint 4: watch_me
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: no thread-specific bp: next: find addresses: watch watch_me
continue
Continuing.
Warning:
Could not insert hardware watchpoint 4.
Could not insert hardware breakpoints:
You may have requested too many hardware breakpoints/watchpoints.

Command aborted.
(gdb) FAIL: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: no thread-specific bp: next: find addresses: continue to watchpoint
disassemble
Dump of assembler code for function child_function:
   0x0000000080000828 <+0>:	stmg	%r11,%r15,88(%r15)
   0x000000008000082e <+6>:	aghi	%r15,-168
   0x0000000080000832 <+10>:	lgr	%r11,%r15
   0x0000000080000836 <+14>:	stg	%r2,160(%r11)
   0x000000008000083c <+20>:	larl	%r2,0x80001d40 <barrier>
   0x0000000080000842 <+26>:	brasl	%r14,0x80000620 <pthread_barrier_wait@plt>
   0x0000000080000848 <+32>:	j	0x8000088c <child_function+100>
   0x000000008000084c <+36>:	larl	%r1,0x80001d30 <counter>
   0x0000000080000852 <+42>:	l	%r1,0(%r1)
   0x0000000080000856 <+46>:	ahi	%r1,1
   0x000000008000085a <+50>:	lr	%r2,%r1
   0x000000008000085c <+52>:	larl	%r1,0x80001d30 <counter>
   0x0000000080000862 <+58>:	st	%r2,0(%r1)
=> 0x0000000080000866 <+62>:	larl	%r1,0x80001d6c <watch_me>
   0x000000008000086c <+68>:	lhi	%r2,1
   0x0000000080000870 <+72>:	st	%r2,0(%r1)
   0x0000000080000874 <+76>:	larl	%r1,0x80001d68 <other>
   0x000000008000087a <+82>:	lhi	%r2,1
   0x000000008000087e <+86>:	st	%r2,0(%r1)
   0x0000000080000882 <+90>:	lghi	%r2,1
   0x0000000080000886 <+94>:	brasl	%r14,0x80000660 <usleep@plt>
   0x000000008000088c <+100>:	larl	%r1,0x80001d30 <counter>
   0x0000000080000892 <+106>:	l	%r1,0(%r1)
   0x0000000080000896 <+110>:	ltr	%r1,%r1
   0x0000000080000898 <+112>:	jne	0x8000084c <child_function+36>
   0x000000008000089c <+116>:	lghi	%r2,0
   0x00000000800008a0 <+120>:	brasl	%r14,0x800006c0 <pthread_exit@plt>
End of assembler dump.
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: no thread-specific bp: next: find addresses: find addresses
delete breakpoints
Delete all breakpoints? (y or n) y
(gdb) info breakpoints
No breakpoints or watchpoints.
(gdb) break *0x0000000080000862
Breakpoint 5 at 0x80000862: file /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c, line 36.
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: no thread-specific bp: next: set breakpoint at address that triggers watch
continue
Continuing.

Thread 2 "step-over-trips" hit Breakpoint 5, 0x0000000080000862 in child_function (arg=0x0) at /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c:36
36	      counter++;
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: no thread-specific bp: next: continue to breakpoint: run to instruction that triggers watch in thread 2
p counter = 0
$2 = 0
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: no thread-specific bp: next: unbreak loop in thread 2
p watch_me = 0
$3 = 0
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: no thread-specific bp: next: clear watch_me
watch watch_me
Hardware watchpoint 6: watch_me
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: no thread-specific bp: next: watch watch_me
thread 1
[Switching to thread 1 (Thread 17015.17015)]
#0  main () at /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c:65
65	  while (1); /* set wait-thread breakpoint here */
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: no thread-specific bp: next: thread 1
set scheduler-locking off
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: no thread-specific bp: next: set scheduler-locking off
next
Warning:
Could not insert hardware watchpoint 6.
Could not insert hardware breakpoints:
You may have requested too many hardware breakpoints/watchpoints.

Command aborted.
(gdb) FAIL: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: no thread-specific bp: next: next
Remote debugging from host 127.0.0.1
monitor exit
Killing process(es): 17015
spawn /home/dje/build/GDB/gdb/testsuite/../../gdb/gdb -nw -nx -data-directory /home/dje/build/GDB/gdb/testsuite/../data-directory -ex set auto-connect-native-target off
GNU gdb (GDB) 8.0.50.20171215-git
Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "s390x-ibm-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word".
(gdb) set height 0
(gdb) set width 0
(gdb) dir
Reinitialize source path to empty? (y or n) y
Source directories searched: $cdir:$cwd
(gdb) dir /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads
Source directories searched: /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads:$cdir:$cwd
(gdb) kill
The program is not being run.
(gdb) file /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/step-over-trips-on-watchpoint/step-over-trips-on-watchpoint
Reading symbols from /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/step-over-trips-on-watchpoint/step-over-trips-on-watchpoint...done.
(gdb) delete breakpoints
(gdb) info breakpoints
No breakpoints or watchpoints.
(gdb) break main
Breakpoint 1 at 0x800008b6: file /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c, line 52.
(gdb) kill
The program is not being run.
(gdb) spawn /home/dje/build/GDB/gdb/testsuite/../gdbserver/gdbserver --once :2354 /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/step-over-trips-on-watchpoint/step-over-trips-on-watchpoint
Process /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/step-over-trips-on-watchpoint/step-over-trips-on-watchpoint created; pid = 17034
Listening on port 2354
target remote localhost:2354
Remote debugging using localhost:2354
Reading /lib/ld64.so.1 from remote target...
warning: File transfers from remote targets can be slow. Use "set sysroot" to access files locally instead.
Reading /lib/ld64.so.1 from remote target...
Reading symbols from target:/lib/ld64.so.1...Reading /lib/ld-2.19.so from remote target...
Reading /lib/.debug/ld-2.19.so from remote target...
(no debugging symbols found)...done.
0x000003fffdfd9280 in ?? () from target:/lib/ld64.so.1
(gdb) continue
Continuing.
Reading /lib/s390x-linux-gnu/libpthread.so.0 from remote target...
Reading /lib/s390x-linux-gnu/libm.so.6 from remote target...
Reading /lib/s390x-linux-gnu/libc.so.6 from remote target...
Reading /lib/s390x-linux-gnu/libpthread-2.19.so from remote target...
Reading /lib/s390x-linux-gnu/.debug/libpthread-2.19.so from remote target...
Reading /lib/s390x-linux-gnu/libm-2.19.so from remote target...
Reading /lib/s390x-linux-gnu/.debug/libm-2.19.so from remote target...
Reading /lib/s390x-linux-gnu/libc-2.19.so from remote target...
Reading /lib/s390x-linux-gnu/.debug/libc-2.19.so from remote target...

Breakpoint 1, main () at /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c:52
52	  alarm (300);
(gdb) set displaced-stepping on
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: no thread-specific bp: continue: set displaced-stepping on
break 65
Breakpoint 2 at 0x80000902: file /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c, line 65.
(gdb) continue
Continuing.
[New Thread 17034.17035]

Thread 1 "step-over-trips" hit Breakpoint 2, main () at /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c:65
65	  while (1); /* set wait-thread breakpoint here */
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: no thread-specific bp: continue: continue to breakpoint: run to wait-thread breakpoint
info threads
  Id   Target Id         Frame 
* 1    Thread 17034.17034 "step-over-trips" main () at /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c:65
  2    Thread 17034.17035 "step-over-trips" 0x000003fffde21c30 in ?? () at ../sysdeps/unix/syscall-template.S:81 from target:/lib/s390x-linux-gnu/libc.so.6
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: no thread-specific bp: continue: info threads shows all threads
set scheduler-locking on
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: no thread-specific bp: continue: set scheduler-locking on
delete breakpoints
Delete all breakpoints? (y or n) y
(gdb) info breakpoints
No breakpoints or watchpoints.
(gdb) break 38
Breakpoint 3 at 0x80000866: file /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c, line 38.
(gdb) thread 2
[Switching to thread 2 (Thread 17034.17035)]
#0  0x000003fffde21c30 in ?? () at ../sysdeps/unix/syscall-template.S:81 from target:/lib/s390x-linux-gnu/libc.so.6
81	../sysdeps/unix/syscall-template.S: No such file or directory.
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: no thread-specific bp: continue: thread 2
continue
Continuing.

Thread 2 "step-over-trips" hit Breakpoint 3, child_function (arg=0x0) at /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c:38
38	      watch_me = 1; /* set breakpoint child here */
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: no thread-specific bp: continue: continue to breakpoint: run to breakpoint in thread 2
p watch_me = 0
$1 = 0
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: no thread-specific bp: continue: find addresses: clear watch_me
watch watch_me
Hardware watchpoint 4: watch_me
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: no thread-specific bp: continue: find addresses: watch watch_me
continue
Continuing.
Warning:
Could not insert hardware watchpoint 4.
Could not insert hardware breakpoints:
You may have requested too many hardware breakpoints/watchpoints.

Command aborted.
(gdb) FAIL: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: no thread-specific bp: continue: find addresses: continue to watchpoint
disassemble
Dump of assembler code for function child_function:
   0x0000000080000828 <+0>:	stmg	%r11,%r15,88(%r15)
   0x000000008000082e <+6>:	aghi	%r15,-168
   0x0000000080000832 <+10>:	lgr	%r11,%r15
   0x0000000080000836 <+14>:	stg	%r2,160(%r11)
   0x000000008000083c <+20>:	larl	%r2,0x80001d40 <barrier>
   0x0000000080000842 <+26>:	brasl	%r14,0x80000620 <pthread_barrier_wait@plt>
   0x0000000080000848 <+32>:	j	0x8000088c <child_function+100>
   0x000000008000084c <+36>:	larl	%r1,0x80001d30 <counter>
   0x0000000080000852 <+42>:	l	%r1,0(%r1)
   0x0000000080000856 <+46>:	ahi	%r1,1
   0x000000008000085a <+50>:	lr	%r2,%r1
   0x000000008000085c <+52>:	larl	%r1,0x80001d30 <counter>
   0x0000000080000862 <+58>:	st	%r2,0(%r1)
=> 0x0000000080000866 <+62>:	larl	%r1,0x80001d6c <watch_me>
   0x000000008000086c <+68>:	lhi	%r2,1
   0x0000000080000870 <+72>:	st	%r2,0(%r1)
   0x0000000080000874 <+76>:	larl	%r1,0x80001d68 <other>
   0x000000008000087a <+82>:	lhi	%r2,1
   0x000000008000087e <+86>:	st	%r2,0(%r1)
   0x0000000080000882 <+90>:	lghi	%r2,1
   0x0000000080000886 <+94>:	brasl	%r14,0x80000660 <usleep@plt>
   0x000000008000088c <+100>:	larl	%r1,0x80001d30 <counter>
   0x0000000080000892 <+106>:	l	%r1,0(%r1)
   0x0000000080000896 <+110>:	ltr	%r1,%r1
   0x0000000080000898 <+112>:	jne	0x8000084c <child_function+36>
   0x000000008000089c <+116>:	lghi	%r2,0
   0x00000000800008a0 <+120>:	brasl	%r14,0x800006c0 <pthread_exit@plt>
End of assembler dump.
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: no thread-specific bp: continue: find addresses: find addresses
delete breakpoints
Delete all breakpoints? (y or n) y
(gdb) info breakpoints
No breakpoints or watchpoints.
(gdb) break *0x0000000080000862
Breakpoint 5 at 0x80000862: file /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c, line 36.
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: no thread-specific bp: continue: set breakpoint at address that triggers watch
continue
Continuing.

Thread 2 "step-over-trips" hit Breakpoint 5, 0x0000000080000862 in child_function (arg=0x0) at /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c:36
36	      counter++;
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: no thread-specific bp: continue: continue to breakpoint: run to instruction that triggers watch in thread 2
p counter = 0
$2 = 0
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: no thread-specific bp: continue: unbreak loop in thread 2
p watch_me = 0
$3 = 0
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: no thread-specific bp: continue: clear watch_me
watch watch_me
Hardware watchpoint 6: watch_me
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: no thread-specific bp: continue: watch watch_me
thread 1
[Switching to thread 1 (Thread 17034.17034)]
#0  main () at /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c:65
65	  while (1); /* set wait-thread breakpoint here */
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: no thread-specific bp: continue: thread 1
set scheduler-locking off
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: no thread-specific bp: continue: set scheduler-locking off
continue
Continuing.
Warning:
Could not insert hardware watchpoint 6.
Could not insert hardware breakpoints:
You may have requested too many hardware breakpoints/watchpoints.

Command aborted.
(gdb) FAIL: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: no thread-specific bp: continue: continue
Remote debugging from host 127.0.0.1
Killing process(es): 17034
monitor exit
(gdb) spawn /home/dje/build/GDB/gdb/testsuite/../../gdb/gdb -nw -nx -data-directory /home/dje/build/GDB/gdb/testsuite/../data-directory -ex set auto-connect-native-target off
GNU gdb (GDB) 8.0.50.20171215-git
Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "s390x-ibm-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word".
(gdb) set height 0
(gdb) set width 0
(gdb) dir
Reinitialize source path to empty? (y or n) y
Source directories searched: $cdir:$cwd
(gdb) dir /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads
Source directories searched: /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads:$cdir:$cwd
(gdb) kill
The program is not being run.
(gdb) file /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/step-over-trips-on-watchpoint/step-over-trips-on-watchpoint
Reading symbols from /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/step-over-trips-on-watchpoint/step-over-trips-on-watchpoint...done.
(gdb) delete breakpoints
(gdb) info breakpoints
No breakpoints or watchpoints.
(gdb) break main
Breakpoint 1 at 0x800008b6: file /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c, line 52.
(gdb) kill
The program is not being run.
(gdb) spawn /home/dje/build/GDB/gdb/testsuite/../gdbserver/gdbserver --once :2355 /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/step-over-trips-on-watchpoint/step-over-trips-on-watchpoint
Process /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/step-over-trips-on-watchpoint/step-over-trips-on-watchpoint created; pid = 17052
Listening on port 2355
target remote localhost:2355
Remote debugging using localhost:2355
Reading /lib/ld64.so.1 from remote target...
warning: File transfers from remote targets can be slow. Use "set sysroot" to access files locally instead.
Reading /lib/ld64.so.1 from remote target...
Reading symbols from target:/lib/ld64.so.1...Reading /lib/ld-2.19.so from remote target...
Reading /lib/.debug/ld-2.19.so from remote target...
(no debugging symbols found)...done.
0x000003fffdfd9280 in ?? () from target:/lib/ld64.so.1
(gdb) continue
Continuing.
Reading /lib/s390x-linux-gnu/libpthread.so.0 from remote target...
Reading /lib/s390x-linux-gnu/libm.so.6 from remote target...
Reading /lib/s390x-linux-gnu/libc.so.6 from remote target...
Reading /lib/s390x-linux-gnu/libpthread-2.19.so from remote target...
Reading /lib/s390x-linux-gnu/.debug/libpthread-2.19.so from remote target...
Reading /lib/s390x-linux-gnu/libm-2.19.so from remote target...
Reading /lib/s390x-linux-gnu/.debug/libm-2.19.so from remote target...
Reading /lib/s390x-linux-gnu/libc-2.19.so from remote target...
Reading /lib/s390x-linux-gnu/.debug/libc-2.19.so from remote target...

Breakpoint 1, main () at /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c:52
52	  alarm (300);
(gdb) set displaced-stepping on
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: with thread-specific bp: step: set displaced-stepping on
break 65
Breakpoint 2 at 0x80000902: file /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c, line 65.
(gdb) continue
Continuing.
[New Thread 17052.17053]

Thread 1 "step-over-trips" hit Breakpoint 2, main () at /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c:65
65	  while (1); /* set wait-thread breakpoint here */
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: with thread-specific bp: step: continue to breakpoint: run to wait-thread breakpoint
info threads
  Id   Target Id         Frame 
* 1    Thread 17052.17052 "step-over-trips" main () at /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c:65
  2    Thread 17052.17053 "step-over-trips" 0x000003fffde21c30 in ?? () at ../sysdeps/unix/syscall-template.S:81 from target:/lib/s390x-linux-gnu/libc.so.6
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: with thread-specific bp: step: info threads shows all threads
set scheduler-locking on
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: with thread-specific bp: step: set scheduler-locking on
delete breakpoints
Delete all breakpoints? (y or n) y
(gdb) info breakpoints
No breakpoints or watchpoints.
(gdb) break 38
Breakpoint 3 at 0x80000866: file /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c, line 38.
(gdb) thread 2
[Switching to thread 2 (Thread 17052.17053)]
#0  0x000003fffde21c30 in ?? () at ../sysdeps/unix/syscall-template.S:81 from target:/lib/s390x-linux-gnu/libc.so.6
81	../sysdeps/unix/syscall-template.S: No such file or directory.
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: with thread-specific bp: step: thread 2
continue
Continuing.

Thread 2 "step-over-trips" hit Breakpoint 3, child_function (arg=0x0) at /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c:38
38	      watch_me = 1; /* set breakpoint child here */
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: with thread-specific bp: step: continue to breakpoint: run to breakpoint in thread 2
p watch_me = 0
$1 = 0
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: with thread-specific bp: step: find addresses: clear watch_me
watch watch_me
Hardware watchpoint 4: watch_me
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: with thread-specific bp: step: find addresses: watch watch_me
continue
Continuing.
Warning:
Could not insert hardware watchpoint 4.
Could not insert hardware breakpoints:
You may have requested too many hardware breakpoints/watchpoints.

Command aborted.
(gdb) FAIL: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: with thread-specific bp: step: find addresses: continue to watchpoint
disassemble
Dump of assembler code for function child_function:
   0x0000000080000828 <+0>:	stmg	%r11,%r15,88(%r15)
   0x000000008000082e <+6>:	aghi	%r15,-168
   0x0000000080000832 <+10>:	lgr	%r11,%r15
   0x0000000080000836 <+14>:	stg	%r2,160(%r11)
   0x000000008000083c <+20>:	larl	%r2,0x80001d40 <barrier>
   0x0000000080000842 <+26>:	brasl	%r14,0x80000620 <pthread_barrier_wait@plt>
   0x0000000080000848 <+32>:	j	0x8000088c <child_function+100>
   0x000000008000084c <+36>:	larl	%r1,0x80001d30 <counter>
   0x0000000080000852 <+42>:	l	%r1,0(%r1)
   0x0000000080000856 <+46>:	ahi	%r1,1
   0x000000008000085a <+50>:	lr	%r2,%r1
   0x000000008000085c <+52>:	larl	%r1,0x80001d30 <counter>
   0x0000000080000862 <+58>:	st	%r2,0(%r1)
=> 0x0000000080000866 <+62>:	larl	%r1,0x80001d6c <watch_me>
   0x000000008000086c <+68>:	lhi	%r2,1
   0x0000000080000870 <+72>:	st	%r2,0(%r1)
   0x0000000080000874 <+76>:	larl	%r1,0x80001d68 <other>
   0x000000008000087a <+82>:	lhi	%r2,1
   0x000000008000087e <+86>:	st	%r2,0(%r1)
   0x0000000080000882 <+90>:	lghi	%r2,1
   0x0000000080000886 <+94>:	brasl	%r14,0x80000660 <usleep@plt>
   0x000000008000088c <+100>:	larl	%r1,0x80001d30 <counter>
   0x0000000080000892 <+106>:	l	%r1,0(%r1)
   0x0000000080000896 <+110>:	ltr	%r1,%r1
   0x0000000080000898 <+112>:	jne	0x8000084c <child_function+36>
   0x000000008000089c <+116>:	lghi	%r2,0
   0x00000000800008a0 <+120>:	brasl	%r14,0x800006c0 <pthread_exit@plt>
End of assembler dump.
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: with thread-specific bp: step: find addresses: find addresses
delete breakpoints
Delete all breakpoints? (y or n) y
(gdb) info breakpoints
No breakpoints or watchpoints.
(gdb) break *0x0000000080000862
Breakpoint 5 at 0x80000862: file /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c, line 36.
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: with thread-specific bp: step: set breakpoint at address that triggers watch
continue
Continuing.

Thread 2 "step-over-trips" hit Breakpoint 5, 0x0000000080000862 in child_function (arg=0x0) at /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c:36
36	      counter++;
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: with thread-specific bp: step: continue to breakpoint: run to instruction that triggers watch in thread 2
p counter = 0
$2 = 0
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: with thread-specific bp: step: unbreak loop in thread 2
p watch_me = 0
$3 = 0
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: with thread-specific bp: step: clear watch_me
watch watch_me
Hardware watchpoint 6: watch_me
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: with thread-specific bp: step: watch watch_me
b *0x0000000080000866 thread 1
Breakpoint 7 at 0x80000866: file /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c, line 38.
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: with thread-specific bp: step: set breakpoint specific to thread 1
thread 1
[Switching to thread 1 (Thread 17052.17052)]
#0  main () at /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c:65
65	  while (1); /* set wait-thread breakpoint here */
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: with thread-specific bp: step: thread 1
set scheduler-locking off
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: with thread-specific bp: step: set scheduler-locking off
step
Warning:
Could not insert hardware watchpoint 6.
Could not insert hardware breakpoints:
You may have requested too many hardware breakpoints/watchpoints.

Command aborted.
(gdb) FAIL: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: with thread-specific bp: step: step
Remote debugging from host 127.0.0.1
monitor exit
Killing process(es): 17052
spawn /home/dje/build/GDB/gdb/testsuite/../../gdb/gdb -nw -nx -data-directory /home/dje/build/GDB/gdb/testsuite/../data-directory -ex set auto-connect-native-target off
GNU gdb (GDB) 8.0.50.20171215-git
Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "s390x-ibm-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word".
(gdb) set height 0
(gdb) set width 0
(gdb) dir
Reinitialize source path to empty? (y or n) y
Source directories searched: $cdir:$cwd
(gdb) dir /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads
Source directories searched: /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads:$cdir:$cwd
(gdb) kill
The program is not being run.
(gdb) file /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/step-over-trips-on-watchpoint/step-over-trips-on-watchpoint
Reading symbols from /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/step-over-trips-on-watchpoint/step-over-trips-on-watchpoint...done.
(gdb) delete breakpoints
(gdb) info breakpoints
No breakpoints or watchpoints.
(gdb) break main
Breakpoint 1 at 0x800008b6: file /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c, line 52.
(gdb) kill
The program is not being run.
(gdb) spawn /home/dje/build/GDB/gdb/testsuite/../gdbserver/gdbserver --once :2356 /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/step-over-trips-on-watchpoint/step-over-trips-on-watchpoint
Process /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/step-over-trips-on-watchpoint/step-over-trips-on-watchpoint created; pid = 17070
Listening on port 2356
target remote localhost:2356
Remote debugging using localhost:2356
Reading /lib/ld64.so.1 from remote target...
warning: File transfers from remote targets can be slow. Use "set sysroot" to access files locally instead.
Reading /lib/ld64.so.1 from remote target...
Reading symbols from target:/lib/ld64.so.1...Reading /lib/ld-2.19.so from remote target...
Reading /lib/.debug/ld-2.19.so from remote target...
(no debugging symbols found)...done.
0x000003fffdfd9280 in ?? () from target:/lib/ld64.so.1
(gdb) continue
Continuing.
Reading /lib/s390x-linux-gnu/libpthread.so.0 from remote target...
Reading /lib/s390x-linux-gnu/libm.so.6 from remote target...
Reading /lib/s390x-linux-gnu/libc.so.6 from remote target...
Reading /lib/s390x-linux-gnu/libpthread-2.19.so from remote target...
Reading /lib/s390x-linux-gnu/.debug/libpthread-2.19.so from remote target...
Reading /lib/s390x-linux-gnu/libm-2.19.so from remote target...
Reading /lib/s390x-linux-gnu/.debug/libm-2.19.so from remote target...
Reading /lib/s390x-linux-gnu/libc-2.19.so from remote target...
Reading /lib/s390x-linux-gnu/.debug/libc-2.19.so from remote target...

Breakpoint 1, main () at /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c:52
52	  alarm (300);
(gdb) set displaced-stepping on
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: with thread-specific bp: next: set displaced-stepping on
break 65
Breakpoint 2 at 0x80000902: file /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c, line 65.
(gdb) continue
Continuing.
[New Thread 17070.17071]

Thread 1 "step-over-trips" hit Breakpoint 2, main () at /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c:65
65	  while (1); /* set wait-thread breakpoint here */
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: with thread-specific bp: next: continue to breakpoint: run to wait-thread breakpoint
info threads
  Id   Target Id         Frame 
* 1    Thread 17070.17070 "step-over-trips" main () at /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c:65
  2    Thread 17070.17071 "step-over-trips" 0x000003fffde21c30 in ?? () at ../sysdeps/unix/syscall-template.S:81 from target:/lib/s390x-linux-gnu/libc.so.6
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: with thread-specific bp: next: info threads shows all threads
set scheduler-locking on
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: with thread-specific bp: next: set scheduler-locking on
delete breakpoints
Delete all breakpoints? (y or n) y
(gdb) info breakpoints
No breakpoints or watchpoints.
(gdb) break 38
Breakpoint 3 at 0x80000866: file /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c, line 38.
(gdb) thread 2
[Switching to thread 2 (Thread 17070.17071)]
#0  0x000003fffde21c30 in ?? () at ../sysdeps/unix/syscall-template.S:81 from target:/lib/s390x-linux-gnu/libc.so.6
81	../sysdeps/unix/syscall-template.S: No such file or directory.
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: with thread-specific bp: next: thread 2
continue
Continuing.

Thread 2 "step-over-trips" hit Breakpoint 3, child_function (arg=0x0) at /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c:38
38	      watch_me = 1; /* set breakpoint child here */
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: with thread-specific bp: next: continue to breakpoint: run to breakpoint in thread 2
p watch_me = 0
$1 = 0
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: with thread-specific bp: next: find addresses: clear watch_me
watch watch_me
Hardware watchpoint 4: watch_me
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: with thread-specific bp: next: find addresses: watch watch_me
continue
Continuing.
Warning:
Could not insert hardware watchpoint 4.
Could not insert hardware breakpoints:
You may have requested too many hardware breakpoints/watchpoints.

Command aborted.
(gdb) FAIL: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: with thread-specific bp: next: find addresses: continue to watchpoint
disassemble
Dump of assembler code for function child_function:
   0x0000000080000828 <+0>:	stmg	%r11,%r15,88(%r15)
   0x000000008000082e <+6>:	aghi	%r15,-168
   0x0000000080000832 <+10>:	lgr	%r11,%r15
   0x0000000080000836 <+14>:	stg	%r2,160(%r11)
   0x000000008000083c <+20>:	larl	%r2,0x80001d40 <barrier>
   0x0000000080000842 <+26>:	brasl	%r14,0x80000620 <pthread_barrier_wait@plt>
   0x0000000080000848 <+32>:	j	0x8000088c <child_function+100>
   0x000000008000084c <+36>:	larl	%r1,0x80001d30 <counter>
   0x0000000080000852 <+42>:	l	%r1,0(%r1)
   0x0000000080000856 <+46>:	ahi	%r1,1
   0x000000008000085a <+50>:	lr	%r2,%r1
   0x000000008000085c <+52>:	larl	%r1,0x80001d30 <counter>
   0x0000000080000862 <+58>:	st	%r2,0(%r1)
=> 0x0000000080000866 <+62>:	larl	%r1,0x80001d6c <watch_me>
   0x000000008000086c <+68>:	lhi	%r2,1
   0x0000000080000870 <+72>:	st	%r2,0(%r1)
   0x0000000080000874 <+76>:	larl	%r1,0x80001d68 <other>
   0x000000008000087a <+82>:	lhi	%r2,1
   0x000000008000087e <+86>:	st	%r2,0(%r1)
   0x0000000080000882 <+90>:	lghi	%r2,1
   0x0000000080000886 <+94>:	brasl	%r14,0x80000660 <usleep@plt>
   0x000000008000088c <+100>:	larl	%r1,0x80001d30 <counter>
   0x0000000080000892 <+106>:	l	%r1,0(%r1)
   0x0000000080000896 <+110>:	ltr	%r1,%r1
   0x0000000080000898 <+112>:	jne	0x8000084c <child_function+36>
   0x000000008000089c <+116>:	lghi	%r2,0
   0x00000000800008a0 <+120>:	brasl	%r14,0x800006c0 <pthread_exit@plt>
End of assembler dump.
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: with thread-specific bp: next: find addresses: find addresses
delete breakpoints
Delete all breakpoints? (y or n) y
(gdb) info breakpoints
No breakpoints or watchpoints.
(gdb) break *0x0000000080000862
Breakpoint 5 at 0x80000862: file /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c, line 36.
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: with thread-specific bp: next: set breakpoint at address that triggers watch
continue
Continuing.

Thread 2 "step-over-trips" hit Breakpoint 5, 0x0000000080000862 in child_function (arg=0x0) at /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c:36
36	      counter++;
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: with thread-specific bp: next: continue to breakpoint: run to instruction that triggers watch in thread 2
p counter = 0
$2 = 0
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: with thread-specific bp: next: unbreak loop in thread 2
p watch_me = 0
$3 = 0
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: with thread-specific bp: next: clear watch_me
watch watch_me
Hardware watchpoint 6: watch_me
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: with thread-specific bp: next: watch watch_me
b *0x0000000080000866 thread 1
Breakpoint 7 at 0x80000866: file /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c, line 38.
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: with thread-specific bp: next: set breakpoint specific to thread 1
thread 1
[Switching to thread 1 (Thread 17070.17070)]
#0  main () at /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c:65
65	  while (1); /* set wait-thread breakpoint here */
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: with thread-specific bp: next: thread 1
set scheduler-locking off
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: with thread-specific bp: next: set scheduler-locking off
next
Warning:
Could not insert hardware watchpoint 6.
Could not insert hardware breakpoints:
You may have requested too many hardware breakpoints/watchpoints.

Command aborted.
(gdb) FAIL: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: with thread-specific bp: next: next
Remote debugging from host 127.0.0.1
monitor exit
(gdb) Killing process(es): 17070
spawn /home/dje/build/GDB/gdb/testsuite/../../gdb/gdb -nw -nx -data-directory /home/dje/build/GDB/gdb/testsuite/../data-directory -ex set auto-connect-native-target off
GNU gdb (GDB) 8.0.50.20171215-git
Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "s390x-ibm-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word".
(gdb) set height 0
(gdb) set width 0
(gdb) dir
Reinitialize source path to empty? (y or n) y
Source directories searched: $cdir:$cwd
(gdb) dir /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads
Source directories searched: /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads:$cdir:$cwd
(gdb) kill
The program is not being run.
(gdb) file /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/step-over-trips-on-watchpoint/step-over-trips-on-watchpoint
Reading symbols from /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/step-over-trips-on-watchpoint/step-over-trips-on-watchpoint...done.
(gdb) delete breakpoints
(gdb) info breakpoints
No breakpoints or watchpoints.
(gdb) break main
Breakpoint 1 at 0x800008b6: file /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c, line 52.
(gdb) kill
The program is not being run.
(gdb) spawn /home/dje/build/GDB/gdb/testsuite/../gdbserver/gdbserver --once :2357 /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/step-over-trips-on-watchpoint/step-over-trips-on-watchpoint
Process /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/step-over-trips-on-watchpoint/step-over-trips-on-watchpoint created; pid = 17088
Listening on port 2357
target remote localhost:2357
Remote debugging using localhost:2357
Reading /lib/ld64.so.1 from remote target...
warning: File transfers from remote targets can be slow. Use "set sysroot" to access files locally instead.
Reading /lib/ld64.so.1 from remote target...
Reading symbols from target:/lib/ld64.so.1...Reading /lib/ld-2.19.so from remote target...
Reading /lib/.debug/ld-2.19.so from remote target...
(no debugging symbols found)...done.
0x000003fffdfd9280 in ?? () from target:/lib/ld64.so.1
(gdb) continue
Continuing.
Reading /lib/s390x-linux-gnu/libpthread.so.0 from remote target...
Reading /lib/s390x-linux-gnu/libm.so.6 from remote target...
Reading /lib/s390x-linux-gnu/libc.so.6 from remote target...
Reading /lib/s390x-linux-gnu/libpthread-2.19.so from remote target...
Reading /lib/s390x-linux-gnu/.debug/libpthread-2.19.so from remote target...
Reading /lib/s390x-linux-gnu/libm-2.19.so from remote target...
Reading /lib/s390x-linux-gnu/.debug/libm-2.19.so from remote target...
Reading /lib/s390x-linux-gnu/libc-2.19.so from remote target...
Reading /lib/s390x-linux-gnu/.debug/libc-2.19.so from remote target...

Breakpoint 1, main () at /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c:52
52	  alarm (300);
(gdb) set displaced-stepping on
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: with thread-specific bp: continue: set displaced-stepping on
break 65
Breakpoint 2 at 0x80000902: file /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c, line 65.
(gdb) continue
Continuing.
[New Thread 17088.17089]

Thread 1 "step-over-trips" hit Breakpoint 2, main () at /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c:65
65	  while (1); /* set wait-thread breakpoint here */
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: with thread-specific bp: continue: continue to breakpoint: run to wait-thread breakpoint
info threads
  Id   Target Id         Frame 
* 1    Thread 17088.17088 "step-over-trips" main () at /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c:65
  2    Thread 17088.17089 "step-over-trips" 0x000003fffde21c30 in ?? () at ../sysdeps/unix/syscall-template.S:81 from target:/lib/s390x-linux-gnu/libc.so.6
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: with thread-specific bp: continue: info threads shows all threads
set scheduler-locking on
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: with thread-specific bp: continue: set scheduler-locking on
delete breakpoints
Delete all breakpoints? (y or n) y
(gdb) info breakpoints
No breakpoints or watchpoints.
(gdb) break 38
Breakpoint 3 at 0x80000866: file /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c, line 38.
(gdb) thread 2
[Switching to thread 2 (Thread 17088.17089)]
#0  0x000003fffde21c30 in ?? () at ../sysdeps/unix/syscall-template.S:81 from target:/lib/s390x-linux-gnu/libc.so.6
81	../sysdeps/unix/syscall-template.S: No such file or directory.
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: with thread-specific bp: continue: thread 2
continue
Continuing.

Thread 2 "step-over-trips" hit Breakpoint 3, child_function (arg=0x0) at /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c:38
38	      watch_me = 1; /* set breakpoint child here */
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: with thread-specific bp: continue: continue to breakpoint: run to breakpoint in thread 2
p watch_me = 0
$1 = 0
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: with thread-specific bp: continue: find addresses: clear watch_me
watch watch_me
Hardware watchpoint 4: watch_me
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: with thread-specific bp: continue: find addresses: watch watch_me
continue
Continuing.
Warning:
Could not insert hardware watchpoint 4.
Could not insert hardware breakpoints:
You may have requested too many hardware breakpoints/watchpoints.

Command aborted.
(gdb) FAIL: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: with thread-specific bp: continue: find addresses: continue to watchpoint
disassemble
Dump of assembler code for function child_function:
   0x0000000080000828 <+0>:	stmg	%r11,%r15,88(%r15)
   0x000000008000082e <+6>:	aghi	%r15,-168
   0x0000000080000832 <+10>:	lgr	%r11,%r15
   0x0000000080000836 <+14>:	stg	%r2,160(%r11)
   0x000000008000083c <+20>:	larl	%r2,0x80001d40 <barrier>
   0x0000000080000842 <+26>:	brasl	%r14,0x80000620 <pthread_barrier_wait@plt>
   0x0000000080000848 <+32>:	j	0x8000088c <child_function+100>
   0x000000008000084c <+36>:	larl	%r1,0x80001d30 <counter>
   0x0000000080000852 <+42>:	l	%r1,0(%r1)
   0x0000000080000856 <+46>:	ahi	%r1,1
   0x000000008000085a <+50>:	lr	%r2,%r1
   0x000000008000085c <+52>:	larl	%r1,0x80001d30 <counter>
   0x0000000080000862 <+58>:	st	%r2,0(%r1)
=> 0x0000000080000866 <+62>:	larl	%r1,0x80001d6c <watch_me>
   0x000000008000086c <+68>:	lhi	%r2,1
   0x0000000080000870 <+72>:	st	%r2,0(%r1)
   0x0000000080000874 <+76>:	larl	%r1,0x80001d68 <other>
   0x000000008000087a <+82>:	lhi	%r2,1
   0x000000008000087e <+86>:	st	%r2,0(%r1)
   0x0000000080000882 <+90>:	lghi	%r2,1
   0x0000000080000886 <+94>:	brasl	%r14,0x80000660 <usleep@plt>
   0x000000008000088c <+100>:	larl	%r1,0x80001d30 <counter>
   0x0000000080000892 <+106>:	l	%r1,0(%r1)
   0x0000000080000896 <+110>:	ltr	%r1,%r1
   0x0000000080000898 <+112>:	jne	0x8000084c <child_function+36>
   0x000000008000089c <+116>:	lghi	%r2,0
   0x00000000800008a0 <+120>:	brasl	%r14,0x800006c0 <pthread_exit@plt>
End of assembler dump.
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: with thread-specific bp: continue: find addresses: find addresses
delete breakpoints
Delete all breakpoints? (y or n) y
(gdb) info breakpoints
No breakpoints or watchpoints.
(gdb) break *0x0000000080000862
Breakpoint 5 at 0x80000862: file /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c, line 36.
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: with thread-specific bp: continue: set breakpoint at address that triggers watch
continue
Continuing.

Thread 2 "step-over-trips" hit Breakpoint 5, 0x0000000080000862 in child_function (arg=0x0) at /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c:36
36	      counter++;
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: with thread-specific bp: continue: continue to breakpoint: run to instruction that triggers watch in thread 2
p counter = 0
$2 = 0
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: with thread-specific bp: continue: unbreak loop in thread 2
p watch_me = 0
$3 = 0
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: with thread-specific bp: continue: clear watch_me
watch watch_me
Hardware watchpoint 6: watch_me
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: with thread-specific bp: continue: watch watch_me
b *0x0000000080000866 thread 1
Breakpoint 7 at 0x80000866: file /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c, line 38.
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: with thread-specific bp: continue: set breakpoint specific to thread 1
thread 1
[Switching to thread 1 (Thread 17088.17088)]
#0  main () at /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.c:65
65	  while (1); /* set wait-thread breakpoint here */
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: with thread-specific bp: continue: thread 1
set scheduler-locking off
(gdb) PASS: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: with thread-specific bp: continue: set scheduler-locking off
continue
Continuing.
Warning:
Could not insert hardware watchpoint 6.
Could not insert hardware breakpoints:
You may have requested too many hardware breakpoints/watchpoints.

Command aborted.
(gdb) FAIL: gdb.threads/step-over-trips-on-watchpoint.exp: displaced=on: with thread-specific bp: continue: continue
Remote debugging from host 127.0.0.1
monitor exit
Killing process(es): 17088
testcase /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.exp completed in 513 seconds

		=== gdb Summary ===

# of expected passes		160
# of unexpected failures	63
Executing on host: /home/dje/build/GDB/gdb/testsuite/../../gdb/gdb -nw -nx -data-directory /home/dje/build/GDB/gdb/testsuite/../data-directory --version    (timeout = 300)
spawn -ignore SIGHUP /home/dje/build/GDB/gdb/testsuite/../../gdb/gdb -nw -nx -data-directory /home/dje/build/GDB/gdb/testsuite/../data-directory --version
GNU gdb (GDB) 8.0.50.20171215-git
Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "s390x-ibm-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word".
/home/dje/build/GDB/gdb/testsuite/../../gdb/gdb version  8.0.50.20171215-git -nw -nx -data-directory /home/dje/build/GDB/gdb/testsuite/../data-directory  -ex "set auto-connect-native-target off"

runtest completed at Fri Dec 15 17:56:05 2017

[-- Attachment #4: thread-specific-bp.log --]
[-- Type: application/octet-stream, Size: 16974 bytes --]

Test Run By dje on Fri Dec 15 17:47:20 2017
Native configuration is s390x-ibm-linux-gnu

		=== gdb tests ===

Schedule of variations:
    native-gdbserver

Running target native-gdbserver
Using /home/dje/src/binutils-gdb/gdb/testsuite/boards/../boards/native-gdbserver.exp as board description file for target.
Using /home/dje/src/binutils-gdb/gdb/testsuite/boards/../boards/gdbserver-base.exp as board description file for target.
Using /home/dje/src/binutils-gdb/gdb/testsuite/boards/../boards/local-board.exp as board description file for target.
Using /home/dje/src/binutils-gdb/gdb/testsuite/config/gdbserver.exp as tool-and-target-specific interface file.
Running /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/thread-specific-bp.exp ...
Executing on host: gcc  /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/thread-specific-bp.c  -g  -lpthreads -lm   -o /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/thread-specific-bp/thread-specific-bp    (timeout = 300)
spawn -ignore SIGHUP gcc /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/thread-specific-bp.c -g -lpthreads -lm -o /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/thread-specific-bp/thread-specific-bp
/usr/bin/ld: cannot find -lpthreads
collect2: error: ld returned 1 exit status
compiler exited with status 1
output is:
/usr/bin/ld: cannot find -lpthreads
collect2: error: ld returned 1 exit status

Executing on host: gcc  /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/thread-specific-bp.c  -g  -lpthread -lm   -o /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/thread-specific-bp/thread-specific-bp    (timeout = 300)
spawn -ignore SIGHUP gcc /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/thread-specific-bp.c -g -lpthread -lm -o /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/thread-specific-bp/thread-specific-bp
PASS: gdb.threads/thread-specific-bp.exp: successfully compiled posix threads test case
spawn /home/dje/build/GDB/gdb/testsuite/../../gdb/gdb -nw -nx -data-directory /home/dje/build/GDB/gdb/testsuite/../data-directory -ex set auto-connect-native-target off
GNU gdb (GDB) 8.0.50.20171215-git
Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "s390x-ibm-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word".
(gdb) set height 0
(gdb) set width 0
(gdb) dir
Reinitialize source path to empty? (y or n) y
Source directories searched: $cdir:$cwd
(gdb) dir /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads
Source directories searched: /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads:$cdir:$cwd
(gdb) kill
The program is not being run.
(gdb) file /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/thread-specific-bp/thread-specific-bp
Reading symbols from /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/thread-specific-bp/thread-specific-bp...done.
(gdb) delete breakpoints
(gdb) info breakpoints
No breakpoints or watchpoints.
(gdb) break main
Breakpoint 1 at 0x800006e6: file /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/thread-specific-bp.c, line 36.
(gdb) kill
The program is not being run.
(gdb) spawn /home/dje/build/GDB/gdb/testsuite/../gdbserver/gdbserver --once :2346 /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/thread-specific-bp/thread-specific-bp
Process /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/thread-specific-bp/thread-specific-bp created; pid = 7962
Listening on port 2346
target remote localhost:2346
Remote debugging using localhost:2346
Reading /lib/ld64.so.1 from remote target...
warning: File transfers from remote targets can be slow. Use "set sysroot" to access files locally instead.
Reading /lib/ld64.so.1 from remote target...
Reading symbols from target:/lib/ld64.so.1...Reading /lib/ld-2.19.so from remote target...
Reading /lib/.debug/ld-2.19.so from remote target...
(no debugging symbols found)...done.
0x000003fffdfd9280 in ?? () from target:/lib/ld64.so.1
(gdb) continue
Continuing.
Reading /lib/s390x-linux-gnu/libpthread.so.0 from remote target...
Reading /lib/s390x-linux-gnu/libm.so.6 from remote target...
Reading /lib/s390x-linux-gnu/libc.so.6 from remote target...
Reading /lib/s390x-linux-gnu/libpthread-2.19.so from remote target...
Reading /lib/s390x-linux-gnu/.debug/libpthread-2.19.so from remote target...
Reading /lib/s390x-linux-gnu/libm-2.19.so from remote target...
Reading /lib/s390x-linux-gnu/.debug/libm-2.19.so from remote target...
Reading /lib/s390x-linux-gnu/libc-2.19.so from remote target...
Reading /lib/s390x-linux-gnu/.debug/libc-2.19.so from remote target...

Breakpoint 1, main () at /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/thread-specific-bp.c:36
36	  pthread_create (&thread, NULL, start, NULL);
(gdb) info threads
  Id   Target Id         Frame 
* 1    Thread 7962.7962 "thread-specific" main () at /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/thread-specific-bp.c:36
(gdb) PASS: gdb.threads/thread-specific-bp.exp: all-stop: get main thread id
break start
Breakpoint 2 at 0x800006ac: file /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/thread-specific-bp.c, line 23.
(gdb) continue
Continuing.
[New Thread 7962.7981]
[Switching to Thread 7962.7981]

Thread 2 "thread-specific" hit Breakpoint 2, start (arg=0x0) at /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/thread-specific-bp.c:23
23	  return NULL;
(gdb) PASS: gdb.threads/thread-specific-bp.exp: all-stop: continue to breakpoint: start
info threads
  Id   Target Id         Frame 
  1    Thread 7962.7962 "thread-specific" 0x000003fffdfafc42 in pthread_join (threadid=4398010173712, thread_return=0x0) at pthread_join.c:92
* 2    Thread 7962.7981 "thread-specific" start (arg=0x0) at /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/thread-specific-bp.c:23
(gdb) PASS: gdb.threads/thread-specific-bp.exp: all-stop: get start thread id
break main thread 2
Note: breakpoint 1 (all threads) also set at pc 0x800006e6.
Breakpoint 3 at 0x800006e6: file /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/thread-specific-bp.c, line 36.
(gdb) info break
Num     Type           Disp Enb Address            What
1       breakpoint     keep y   0x00000000800006e6 in main at /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/thread-specific-bp.c:36
	breakpoint already hit 1 time
2       breakpoint     keep y   0x00000000800006ac in start at /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/thread-specific-bp.c:23
	breakpoint already hit 1 time
3       breakpoint     keep y   0x00000000800006e6 in main at /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/thread-specific-bp.c:36 thread 2
	stop only in thread 2
(gdb) PASS: gdb.threads/thread-specific-bp.exp: all-stop: breakpoint set
break end
Breakpoint 4 at 0x800006ca: file /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/thread-specific-bp.c, line 29.
(gdb) thread 1
[Switching to thread 1 (Thread 7962.7962)]
#0  0x000003fffdfafc42 in pthread_join (threadid=4398010173712, thread_return=0x0) at pthread_join.c:92
92	pthread_join.c: No such file or directory.
(gdb) PASS: gdb.threads/thread-specific-bp.exp: all-stop: thread 1 selected
continue
Continuing.
Thread-specific breakpoint 3 deleted - thread 2 no longer in the thread list.

Thread 1 "thread-specific" hit Breakpoint 4, end () at /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/thread-specific-bp.c:29
29	}
(gdb) PASS: gdb.threads/thread-specific-bp.exp: all-stop: continue to end
info breakpoint
Num     Type           Disp Enb Address            What
1       breakpoint     keep y   0x00000000800006e6 in main at /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/thread-specific-bp.c:36
	breakpoint already hit 1 time
2       breakpoint     keep y   0x00000000800006ac in start at /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/thread-specific-bp.c:23
	breakpoint already hit 1 time
4       breakpoint     keep y   0x00000000800006ca in end at /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/thread-specific-bp.c:29
	breakpoint already hit 1 time
(gdb) PASS: gdb.threads/thread-specific-bp.exp: all-stop: thread-specific breakpoint was deleted
Remote debugging from host 127.0.0.1
monitor exit
Killing process(es): 7962
spawn /home/dje/build/GDB/gdb/testsuite/../../gdb/gdb -nw -nx -data-directory /home/dje/build/GDB/gdb/testsuite/../data-directory -ex set auto-connect-native-target off
GNU gdb (GDB) 8.0.50.20171215-git
Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "s390x-ibm-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word".
(gdb) set height 0
(gdb) set width 0
(gdb) dir
Reinitialize source path to empty? (y or n) y
Source directories searched: $cdir:$cwd
(gdb) dir /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads
Source directories searched: /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads:$cdir:$cwd
(gdb) kill
The program is not being run.
(gdb) file /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/thread-specific-bp/thread-specific-bp
Reading symbols from /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/thread-specific-bp/thread-specific-bp...done.
(gdb) set non-stop on
(gdb) PASS: gdb.threads/thread-specific-bp.exp: set non-stop mode
delete breakpoints
(gdb) info breakpoints
No breakpoints or watchpoints.
(gdb) break main
Breakpoint 1 at 0x800006e6: file /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/thread-specific-bp.c, line 36.
(gdb) kill
The program is not being run.
(gdb) spawn /home/dje/build/GDB/gdb/testsuite/../gdbserver/gdbserver --once :2347 /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/thread-specific-bp/thread-specific-bp
Process /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/thread-specific-bp/thread-specific-bp created; pid = 7997
Listening on port 2347
target remote localhost:2347
Remote debugging using localhost:2347
Reading /lib/ld64.so.1 from remote target...
warning: File transfers from remote targets can be slow. Use "set sysroot" to access files locally instead.
Reading /lib/ld64.so.1 from remote target...
Reading symbols from target:/lib/ld64.so.1...Reading /lib/ld-2.19.so from remote target...
Reading /lib/.debug/ld-2.19.so from remote target...
(no debugging symbols found)...done.

Program stopped.
0x000003fffdfd9280 in ?? () from target:/lib/ld64.so.1
(gdb) continue
Continuing.
Reading /lib/s390x-linux-gnu/libpthread.so.0 from remote target...
Reading /lib/s390x-linux-gnu/libm.so.6 from remote target...
Reading /lib/s390x-linux-gnu/libc.so.6 from remote target...
Reading /lib/s390x-linux-gnu/libpthread-2.19.so from remote target...
Reading /lib/s390x-linux-gnu/.debug/libpthread-2.19.so from remote target...
Reading /lib/s390x-linux-gnu/libm-2.19.so from remote target...
Reading /lib/s390x-linux-gnu/.debug/libm-2.19.so from remote target...
Reading /lib/s390x-linux-gnu/libc-2.19.so from remote target...
Reading /lib/s390x-linux-gnu/.debug/libc-2.19.so from remote target...

Breakpoint 1, main () at /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/thread-specific-bp.c:36
36	  pthread_create (&thread, NULL, start, NULL);
(gdb) info threads
  Id   Target Id         Frame 
* 1    Thread 7997.7997 "thread-specific" main () at /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/thread-specific-bp.c:36
(gdb) PASS: gdb.threads/thread-specific-bp.exp: non-stop: get main thread id
break start
Breakpoint 2 at 0x800006ac: file /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/thread-specific-bp.c, line 23.
(gdb) continue
Continuing.
[New Thread 7997.8014]

Thread 2 "thread-specific" hit Breakpoint 2, start (arg=0x0) at /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/thread-specific-bp.c:23
23	  return NULL;
(gdb) PASS: gdb.threads/thread-specific-bp.exp: non-stop: continue to breakpoint: start
info threads
  Id   Target Id         Frame 
* 1    Thread 7997.7997 "thread-specific" (running)
  2    Thread 7997.8014 "thread-specific" start (arg=0x0) at /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/thread-specific-bp.c:23
(gdb) PASS: gdb.threads/thread-specific-bp.exp: non-stop: get start thread id
break main thread 2
Note: breakpoint 1 (all threads) also set at pc 0x800006e6.
Breakpoint 3 at 0x800006e6: file /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/thread-specific-bp.c, line 36.
(gdb) info break
Num     Type           Disp Enb Address            What
1       breakpoint     keep y   0x00000000800006e6 in main at /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/thread-specific-bp.c:36
	breakpoint already hit 1 time
2       breakpoint     keep y   0x00000000800006ac in start at /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/thread-specific-bp.c:23
	breakpoint already hit 1 time
3       breakpoint     keep y   0x00000000800006e6 in main at /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/thread-specific-bp.c:36 thread 2
	stop only in thread 2
(gdb) PASS: gdb.threads/thread-specific-bp.exp: non-stop: breakpoint set
break end
Breakpoint 4 at 0x800006ca: file /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/thread-specific-bp.c, line 29.
(gdb) thread 1
[Switching to thread 1 (Thread 7997.7997)](running)
(gdb) PASS: gdb.threads/thread-specific-bp.exp: non-stop: thread 1 selected
continue -a
Continuing.
Thread-specific breakpoint 3 deleted - thread 2 no longer in the thread list.

Thread 1 "thread-specific" hit Breakpoint 4, end () at /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/thread-specific-bp.c:29
29	}
(gdb) PASS: gdb.threads/thread-specific-bp.exp: non-stop: continue to end
info breakpoint
Num     Type           Disp Enb Address            What
1       breakpoint     keep y   0x00000000800006e6 in main at /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/thread-specific-bp.c:36
	breakpoint already hit 1 time
2       breakpoint     keep y   0x00000000800006ac in start at /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/thread-specific-bp.c:23
	breakpoint already hit 1 time
4       breakpoint     keep y   0x00000000800006ca in end at /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/thread-specific-bp.c:29
	breakpoint already hit 1 time
(gdb) PASS: gdb.threads/thread-specific-bp.exp: non-stop: thread-specific breakpoint was deleted
Remote debugging from host 127.0.0.1
monitor exit
Killing process(es): 7997
testcase /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/thread-specific-bp.exp completed in 1 seconds

		=== gdb Summary ===

# of expected passes		16
Executing on host: /home/dje/build/GDB/gdb/testsuite/../../gdb/gdb -nw -nx -data-directory /home/dje/build/GDB/gdb/testsuite/../data-directory --version    (timeout = 300)
spawn -ignore SIGHUP /home/dje/build/GDB/gdb/testsuite/../../gdb/gdb -nw -nx -data-directory /home/dje/build/GDB/gdb/testsuite/../data-directory --version
GNU gdb (GDB) 8.0.50.20171215-git
Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "s390x-ibm-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word".
/home/dje/build/GDB/gdb/testsuite/../../gdb/gdb version  8.0.50.20171215-git -nw -nx -data-directory /home/dje/build/GDB/gdb/testsuite/../data-directory  -ex "set auto-connect-native-target off"

runtest completed at Fri Dec 15 17:47:22 2017

[-- Attachment #5: watchpoint-fork.log --]
[-- Type: application/octet-stream, Size: 31141 bytes --]

Test Run By dje on Fri Dec 15 17:47:29 2017
Native configuration is s390x-ibm-linux-gnu

		=== gdb tests ===

Schedule of variations:
    native-gdbserver

Running target native-gdbserver
Using /home/dje/src/binutils-gdb/gdb/testsuite/boards/../boards/native-gdbserver.exp as board description file for target.
Using /home/dje/src/binutils-gdb/gdb/testsuite/boards/../boards/gdbserver-base.exp as board description file for target.
Using /home/dje/src/binutils-gdb/gdb/testsuite/boards/../boards/local-board.exp as board description file for target.
Using /home/dje/src/binutils-gdb/gdb/testsuite/config/gdbserver.exp as tool-and-target-specific interface file.
Running /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/watchpoint-fork.exp ...
get_compiler_info: gcc-4-9-2
Executing on host: gcc   -DFOLLOW_PARENT -c -g  -o /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/watchpoint-fork/watchpoint-fork-parent-st0.o /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/watchpoint-fork-st.c    (timeout = 300)
spawn -ignore SIGHUP gcc -DFOLLOW_PARENT -c -g -o /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/watchpoint-fork/watchpoint-fork-parent-st0.o /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/watchpoint-fork-st.c
Executing on host: gcc   -DFOLLOW_PARENT -c -g  -o /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/watchpoint-fork/watchpoint-fork-parent-st1.o /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/watchpoint-fork-parent.c    (timeout = 300)
spawn -ignore SIGHUP gcc -DFOLLOW_PARENT -c -g -o /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/watchpoint-fork/watchpoint-fork-parent-st1.o /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/watchpoint-fork-parent.c
Executing on host: gcc  /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/watchpoint-fork/watchpoint-fork-parent-st0.o /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/watchpoint-fork/watchpoint-fork-parent-st1.o  -DFOLLOW_PARENT -g  -lm   -o /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/watchpoint-fork/watchpoint-fork-parent-st    (timeout = 300)
spawn -ignore SIGHUP gcc /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/watchpoint-fork/watchpoint-fork-parent-st0.o /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/watchpoint-fork/watchpoint-fork-parent-st1.o -DFOLLOW_PARENT -g -lm -o /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/watchpoint-fork/watchpoint-fork-parent-st
spawn /home/dje/build/GDB/gdb/testsuite/../../gdb/gdb -nw -nx -data-directory /home/dje/build/GDB/gdb/testsuite/../data-directory -ex set auto-connect-native-target off
GNU gdb (GDB) 8.0.50.20171215-git
Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "s390x-ibm-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word".
(gdb) set height 0
(gdb) set width 0
(gdb) dir
Reinitialize source path to empty? (y or n) y
Source directories searched: $cdir:$cwd
(gdb) dir /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads
Source directories searched: /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads:$cdir:$cwd
(gdb) kill
The program is not being run.
(gdb) file /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/watchpoint-fork/watchpoint-fork-parent-st
Reading symbols from /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/watchpoint-fork/watchpoint-fork-parent-st...done.
(gdb) show detach-on-fork
Whether gdb will detach the child of a fork is on.
(gdb) PASS: gdb.threads/watchpoint-fork.exp: parent: singlethreaded: show detach-on-fork
set follow-fork-mode parent
(gdb) PASS: gdb.threads/watchpoint-fork.exp: parent: singlethreaded: set follow-fork-mode parent
show follow-fork-mode
Debugger response to a program call of fork or vfork is "parent".
(gdb) PASS: gdb.threads/watchpoint-fork.exp: parent: singlethreaded: show follow-fork-mode
handle SIGUSR1 nostop noprint pass
Signal        Stop	Print	Pass to program	Description
SIGUSR1       No	No	Yes		User defined signal 1
(gdb) PASS: gdb.threads/watchpoint-fork.exp: parent: singlethreaded: handle SIGUSR1 nostop noprint pass
delete breakpoints
(gdb) info breakpoints
No breakpoints or watchpoints.
(gdb) break main
Breakpoint 1 at 0x80000926: file /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/watchpoint-fork-st.c, line 43.
(gdb) kill
The program is not being run.
(gdb) spawn /home/dje/build/GDB/gdb/testsuite/../gdbserver/gdbserver --once :2346 /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/watchpoint-fork/watchpoint-fork-parent-st
Process /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/watchpoint-fork/watchpoint-fork-parent-st created; pid = 8984
Listening on port 2346
target remote localhost:2346
Remote debugging using localhost:2346
Reading /lib/ld64.so.1 from remote target...
warning: File transfers from remote targets can be slow. Use "set sysroot" to access files locally instead.
Reading /lib/ld64.so.1 from remote target...
Reading symbols from target:/lib/ld64.so.1...Reading /lib/ld-2.19.so from remote target...
Reading /lib/.debug/ld-2.19.so from remote target...
(no debugging symbols found)...done.
0x000003fffdfd9280 in ?? () from target:/lib/ld64.so.1
(gdb) continue
Continuing.
Reading /lib/s390x-linux-gnu/libm.so.6 from remote target...
Reading /lib/s390x-linux-gnu/libc.so.6 from remote target...
Reading /lib/s390x-linux-gnu/libm-2.19.so from remote target...
Reading /lib/s390x-linux-gnu/.debug/libm-2.19.so from remote target...
Reading /lib/s390x-linux-gnu/libc-2.19.so from remote target...
Reading /lib/s390x-linux-gnu/.debug/libc-2.19.so from remote target...

Breakpoint 1, main () at /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/watchpoint-fork-st.c:43
43	  setbuf (stdout, NULL);
(gdb) watch var
Hardware watchpoint 2: var
(gdb) PASS: gdb.threads/watchpoint-fork.exp: parent: singlethreaded: set the watchpoint
hbreak marker
Hardware assisted breakpoint 3 at 0x800008f2: file /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/watchpoint-fork-st.c, line 33.
(gdb) PASS: gdb.threads/watchpoint-fork.exp: parent: singlethreaded: hbreak marker
break mark_exit
Breakpoint 4 at 0x8000090a: file /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/watchpoint-fork-st.c, line 38.
(gdb) continue
Continuing.
Warning:
Cannot insert hardware breakpoint 3.
Could not insert hardware watchpoint 2.
Could not insert hardware breakpoints:
You may have requested too many hardware breakpoints/watchpoints.

Command aborted.
(gdb) FAIL: gdb.threads/watchpoint-fork.exp: parent: singlethreaded: hardware breakpoints work
continue
Continuing.
FAIL: gdb.threads/watchpoint-fork.exp: parent: singlethreaded: watchpoints work (timeout)
continue
FAIL: gdb.threads/watchpoint-fork.exp: parent: singlethreaded: breakpoint after the first fork (timeout)
continue
FAIL: gdb.threads/watchpoint-fork.exp: parent: singlethreaded: watchpoint after the first fork (timeout)
continue
FAIL: gdb.threads/watchpoint-fork.exp: parent: singlethreaded: breakpoint after the second fork (timeout)
continue
FAIL: gdb.threads/watchpoint-fork.exp: parent: singlethreaded: watchpoint after the second fork (timeout)
continue
FAIL: gdb.threads/watchpoint-fork.exp: parent: singlethreaded: finish (timeout)
Executing on host: gcc  /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/watchpoint-fork-mt.c /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/watchpoint-fork-parent.c  -DFOLLOW_PARENT -DTHREAD -g  -lpthreads -lm   -o /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/watchpoint-fork/watchpoint-fork-parent-mt    (timeout = 300)
spawn -ignore SIGHUP gcc /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/watchpoint-fork-mt.c /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/watchpoint-fork-parent.c -DFOLLOW_PARENT -DTHREAD -g -lpthreads -lm -o /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/watchpoint-fork/watchpoint-fork-parent-mt
/usr/bin/ld: cannot find -lpthreads
collect2: error: ld returned 1 exit status
compiler exited with status 1
output is:
/usr/bin/ld: cannot find -lpthreads
collect2: error: ld returned 1 exit status

Executing on host: gcc  /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/watchpoint-fork-mt.c /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/watchpoint-fork-parent.c  -DFOLLOW_PARENT -DTHREAD -g  -lpthread -lm   -o /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/watchpoint-fork/watchpoint-fork-parent-mt    (timeout = 300)
spawn -ignore SIGHUP gcc /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/watchpoint-fork-mt.c /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/watchpoint-fork-parent.c -DFOLLOW_PARENT -DTHREAD -g -lpthread -lm -o /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/watchpoint-fork/watchpoint-fork-parent-mt
PASS: gdb.threads/watchpoint-fork.exp: parent: multithreaded: successfully compiled posix threads test case
Remote debugging from host 127.0.0.1
monitor exit
spawn /home/dje/build/GDB/gdb/testsuite/../../gdb/gdb -nw -nx -data-directory /home/dje/build/GDB/gdb/testsuite/../data-directory -ex set auto-connect-native-target off
GNU gdb (GDB) 8.0.50.20171215-git
Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "s390x-ibm-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word".
(gdb) set height 0
(gdb) set width 0
(gdb) dir
Reinitialize source path to empty? (y or n) y
Source directories searched: $cdir:$cwd
(gdb) dir /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads
Source directories searched: /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads:$cdir:$cwd
(gdb) kill
The program is not being run.
(gdb) file /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/watchpoint-fork/watchpoint-fork-parent-mt
Reading symbols from /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/watchpoint-fork/watchpoint-fork-parent-mt...done.
(gdb) set follow-fork-mode parent
(gdb) PASS: gdb.threads/watchpoint-fork.exp: parent: multithreaded: set follow-fork-mode parent
handle SIGUSR1 nostop noprint pass
Signal        Stop	Print	Pass to program	Description
SIGUSR1       No	No	Yes		User defined signal 1
(gdb) PASS: gdb.threads/watchpoint-fork.exp: parent: multithreaded: handle SIGUSR1 nostop noprint pass
delete breakpoints
(gdb) info breakpoints
No breakpoints or watchpoints.
(gdb) break main
Breakpoint 1 at 0x80000d06: file /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/watchpoint-fork-mt.c, line 117.
(gdb) kill
The program is not being run.
(gdb) spawn /home/dje/build/GDB/gdb/testsuite/../gdbserver/gdbserver --once :2347 /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/watchpoint-fork/watchpoint-fork-parent-mt
Process /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/watchpoint-fork/watchpoint-fork-parent-mt created; pid = 9447
Listening on port 2347
target remote localhost:2347
Remote debugging using localhost:2347
Reading /lib/ld64.so.1 from remote target...
warning: File transfers from remote targets can be slow. Use "set sysroot" to access files locally instead.
Reading /lib/ld64.so.1 from remote target...
Reading symbols from target:/lib/ld64.so.1...Reading /lib/ld-2.19.so from remote target...
Reading /lib/.debug/ld-2.19.so from remote target...
(no debugging symbols found)...done.
0x000003fffdfd9280 in ?? () from target:/lib/ld64.so.1
(gdb) continue
Continuing.
Reading /lib/s390x-linux-gnu/libpthread.so.0 from remote target...
Reading /lib/s390x-linux-gnu/libm.so.6 from remote target...
Reading /lib/s390x-linux-gnu/libc.so.6 from remote target...
Reading /lib/s390x-linux-gnu/libpthread-2.19.so from remote target...
Reading /lib/s390x-linux-gnu/.debug/libpthread-2.19.so from remote target...
Reading /lib/s390x-linux-gnu/libm-2.19.so from remote target...
Reading /lib/s390x-linux-gnu/.debug/libm-2.19.so from remote target...
Reading /lib/s390x-linux-gnu/libc-2.19.so from remote target...
Reading /lib/s390x-linux-gnu/.debug/libc-2.19.so from remote target...

Breakpoint 1, main () at /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/watchpoint-fork-mt.c:117
117	  setbuf (stdout, NULL);
(gdb) watch var
Hardware watchpoint 2: var
(gdb) PASS: gdb.threads/watchpoint-fork.exp: parent: multithreaded: set the watchpoint
hbreak marker
Hardware assisted breakpoint 3 at 0x80000ab2: file /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/watchpoint-fork-mt.c, line 42.
(gdb) PASS: gdb.threads/watchpoint-fork.exp: parent: multithreaded: hbreak marker
break mark_exit
Breakpoint 4 at 0x80000ae2: file /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/watchpoint-fork-mt.c, line 52.
(gdb) continue
Continuing.
Warning:
Cannot insert hardware breakpoint 3.
Could not insert hardware watchpoint 2.
Could not insert hardware breakpoints:
You may have requested too many hardware breakpoints/watchpoints.

Command aborted.
(gdb) FAIL: gdb.threads/watchpoint-fork.exp: parent: multithreaded: hardware breakpoints work
continue
Continuing.
FAIL: gdb.threads/watchpoint-fork.exp: parent: multithreaded: singlethread watchpoints work (timeout)
continue
FAIL: gdb.threads/watchpoint-fork.exp: parent: multithreaded: multithreaded watchpoints work at A (timeout)
continue
FAIL: gdb.threads/watchpoint-fork.exp: parent: multithreaded: multithreaded watchpoints work at B (timeout)
continue
FAIL: gdb.threads/watchpoint-fork.exp: parent: multithreaded: breakpoint (A) after the first fork (timeout)
continue
FAIL: gdb.threads/watchpoint-fork.exp: parent: multithreaded: watchpoint A after the first fork (timeout)
continue
FAIL: gdb.threads/watchpoint-fork.exp: parent: multithreaded: watchpoint B after the first fork (timeout)
continue
FAIL: gdb.threads/watchpoint-fork.exp: parent: multithreaded: breakpoint (A) after the second fork (timeout)
continue
FAIL: gdb.threads/watchpoint-fork.exp: parent: multithreaded: watchpoint A after the second fork (timeout)
continue
FAIL: gdb.threads/watchpoint-fork.exp: parent: multithreaded: watchpoint B after the second fork (timeout)
continue
FAIL: gdb.threads/watchpoint-fork.exp: parent: multithreaded: finish (timeout)
Executing on host: gcc   -DFOLLOW_CHILD -c -g  -o /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/watchpoint-fork/watchpoint-fork-child-st0.o /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/watchpoint-fork-st.c    (timeout = 300)
spawn -ignore SIGHUP gcc -DFOLLOW_CHILD -c -g -o /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/watchpoint-fork/watchpoint-fork-child-st0.o /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/watchpoint-fork-st.c
Executing on host: gcc   -DFOLLOW_CHILD -c -g  -o /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/watchpoint-fork/watchpoint-fork-child-st1.o /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/watchpoint-fork-child.c    (timeout = 300)
spawn -ignore SIGHUP gcc -DFOLLOW_CHILD -c -g -o /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/watchpoint-fork/watchpoint-fork-child-st1.o /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/watchpoint-fork-child.c
Executing on host: gcc  /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/watchpoint-fork/watchpoint-fork-child-st0.o /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/watchpoint-fork/watchpoint-fork-child-st1.o  -DFOLLOW_CHILD -g  -lm   -o /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/watchpoint-fork/watchpoint-fork-child-st    (timeout = 300)
spawn -ignore SIGHUP gcc /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/watchpoint-fork/watchpoint-fork-child-st0.o /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/watchpoint-fork/watchpoint-fork-child-st1.o -DFOLLOW_CHILD -g -lm -o /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/watchpoint-fork/watchpoint-fork-child-st
Remote debugging from host 127.0.0.1
monitor exit
spawn /home/dje/build/GDB/gdb/testsuite/../../gdb/gdb -nw -nx -data-directory /home/dje/build/GDB/gdb/testsuite/../data-directory -ex set auto-connect-native-target off
GNU gdb (GDB) 8.0.50.20171215-git
Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "s390x-ibm-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word".
(gdb) set height 0
(gdb) set width 0
(gdb) dir
Reinitialize source path to empty? (y or n) y
Source directories searched: $cdir:$cwd
(gdb) dir /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads
Source directories searched: /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads:$cdir:$cwd
(gdb) kill
The program is not being run.
(gdb) file /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/watchpoint-fork/watchpoint-fork-child-st
Reading symbols from /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/watchpoint-fork/watchpoint-fork-child-st...done.
(gdb) show detach-on-fork
Whether gdb will detach the child of a fork is on.
(gdb) PASS: gdb.threads/watchpoint-fork.exp: child: singlethreaded: show detach-on-fork
set follow-fork-mode child
(gdb) PASS: gdb.threads/watchpoint-fork.exp: child: singlethreaded: set follow-fork-mode child
show follow-fork-mode
Debugger response to a program call of fork or vfork is "child".
(gdb) PASS: gdb.threads/watchpoint-fork.exp: child: singlethreaded: show follow-fork-mode
handle SIGUSR1 nostop noprint pass
Signal        Stop	Print	Pass to program	Description
SIGUSR1       No	No	Yes		User defined signal 1
(gdb) PASS: gdb.threads/watchpoint-fork.exp: child: singlethreaded: handle SIGUSR1 nostop noprint pass
delete breakpoints
(gdb) info breakpoints
No breakpoints or watchpoints.
(gdb) break main
Breakpoint 1 at 0x80000aa6: file /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/watchpoint-fork-st.c, line 43.
(gdb) kill
The program is not being run.
(gdb) spawn /home/dje/build/GDB/gdb/testsuite/../gdbserver/gdbserver --once :2348 /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/watchpoint-fork/watchpoint-fork-child-st
Process /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/watchpoint-fork/watchpoint-fork-child-st created; pid = 16855
Listening on port 2348
target remote localhost:2348
Remote debugging using localhost:2348
Reading /lib/ld64.so.1 from remote target...
warning: File transfers from remote targets can be slow. Use "set sysroot" to access files locally instead.
Reading /lib/ld64.so.1 from remote target...
Reading symbols from target:/lib/ld64.so.1...Reading /lib/ld-2.19.so from remote target...
Reading /lib/.debug/ld-2.19.so from remote target...
(no debugging symbols found)...done.
0x000003fffdfd9280 in ?? () from target:/lib/ld64.so.1
(gdb) continue
Continuing.
Reading /lib/s390x-linux-gnu/libm.so.6 from remote target...
Reading /lib/s390x-linux-gnu/libc.so.6 from remote target...
Reading /lib/s390x-linux-gnu/libm-2.19.so from remote target...
Reading /lib/s390x-linux-gnu/.debug/libm-2.19.so from remote target...
Reading /lib/s390x-linux-gnu/libc-2.19.so from remote target...
Reading /lib/s390x-linux-gnu/.debug/libc-2.19.so from remote target...

Breakpoint 1, main () at /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/watchpoint-fork-st.c:43
43	  setbuf (stdout, NULL);
(gdb) watch var
Hardware watchpoint 2: var
(gdb) PASS: gdb.threads/watchpoint-fork.exp: child: singlethreaded: set the watchpoint
hbreak marker
Hardware assisted breakpoint 3 at 0x80000a72: file /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/watchpoint-fork-st.c, line 33.
(gdb) PASS: gdb.threads/watchpoint-fork.exp: child: singlethreaded: hbreak marker
break mark_exit
Breakpoint 4 at 0x80000a8a: file /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/watchpoint-fork-st.c, line 38.
(gdb) continue
Continuing.
Warning:
Cannot insert hardware breakpoint 3.
Could not insert hardware watchpoint 2.
Could not insert hardware breakpoints:
You may have requested too many hardware breakpoints/watchpoints.

Command aborted.
(gdb) FAIL: gdb.threads/watchpoint-fork.exp: child: singlethreaded: hardware breakpoints work
continue
Continuing.
FAIL: gdb.threads/watchpoint-fork.exp: child: singlethreaded: watchpoints work (timeout)
continue
FAIL: gdb.threads/watchpoint-fork.exp: child: singlethreaded: breakpoint after the first fork (timeout)
continue
FAIL: gdb.threads/watchpoint-fork.exp: child: singlethreaded: watchpoint after the first fork (timeout)
continue
FAIL: gdb.threads/watchpoint-fork.exp: child: singlethreaded: breakpoint after the second fork (timeout)
continue
FAIL: gdb.threads/watchpoint-fork.exp: child: singlethreaded: watchpoint after the second fork (timeout)
continue
FAIL: gdb.threads/watchpoint-fork.exp: child: singlethreaded: finish (timeout)
Executing on host: gcc  /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/watchpoint-fork-mt.c /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/watchpoint-fork-child.c  -DFOLLOW_CHILD -DTHREAD -g  -lpthreads -lm   -o /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/watchpoint-fork/watchpoint-fork-child-mt    (timeout = 300)
spawn -ignore SIGHUP gcc /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/watchpoint-fork-mt.c /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/watchpoint-fork-child.c -DFOLLOW_CHILD -DTHREAD -g -lpthreads -lm -o /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/watchpoint-fork/watchpoint-fork-child-mt
/usr/bin/ld: cannot find -lpthreads
collect2: error: ld returned 1 exit status
compiler exited with status 1
output is:
/usr/bin/ld: cannot find -lpthreads
collect2: error: ld returned 1 exit status

Executing on host: gcc  /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/watchpoint-fork-mt.c /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/watchpoint-fork-child.c  -DFOLLOW_CHILD -DTHREAD -g  -lpthread -lm   -o /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/watchpoint-fork/watchpoint-fork-child-mt    (timeout = 300)
spawn -ignore SIGHUP gcc /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/watchpoint-fork-mt.c /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/watchpoint-fork-child.c -DFOLLOW_CHILD -DTHREAD -g -lpthread -lm -o /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/watchpoint-fork/watchpoint-fork-child-mt
PASS: gdb.threads/watchpoint-fork.exp: child: multithreaded: successfully compiled posix threads test case
Remote debugging from host 127.0.0.1
monitor exit
spawn /home/dje/build/GDB/gdb/testsuite/../../gdb/gdb -nw -nx -data-directory /home/dje/build/GDB/gdb/testsuite/../data-directory -ex set auto-connect-native-target off
GNU gdb (GDB) 8.0.50.20171215-git
Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "s390x-ibm-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word".
(gdb) set height 0
(gdb) set width 0
(gdb) dir
Reinitialize source path to empty? (y or n) y
Source directories searched: $cdir:$cwd
(gdb) dir /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads
Source directories searched: /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads:$cdir:$cwd
(gdb) kill
The program is not being run.
(gdb) file /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/watchpoint-fork/watchpoint-fork-child-mt
Reading symbols from /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/watchpoint-fork/watchpoint-fork-child-mt...done.
(gdb) set follow-fork-mode child
(gdb) PASS: gdb.threads/watchpoint-fork.exp: child: multithreaded: set follow-fork-mode child
handle SIGUSR1 nostop noprint pass
Signal        Stop	Print	Pass to program	Description
SIGUSR1       No	No	Yes		User defined signal 1
(gdb) PASS: gdb.threads/watchpoint-fork.exp: child: multithreaded: handle SIGUSR1 nostop noprint pass
delete breakpoints
(gdb) info breakpoints
No breakpoints or watchpoints.
(gdb) break main
Breakpoint 1 at 0x80000ebe: file /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/watchpoint-fork-mt.c, line 117.
(gdb) kill
The program is not being run.
(gdb) spawn /home/dje/build/GDB/gdb/testsuite/../gdbserver/gdbserver --once :2349 /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/watchpoint-fork/watchpoint-fork-child-mt
Process /home/dje/build/GDB/gdb/testsuite/outputs/gdb.threads/watchpoint-fork/watchpoint-fork-child-mt created; pid = 16922
Listening on port 2349
target remote localhost:2349
Remote debugging using localhost:2349
Reading /lib/ld64.so.1 from remote target...
warning: File transfers from remote targets can be slow. Use "set sysroot" to access files locally instead.
Reading /lib/ld64.so.1 from remote target...
Reading symbols from target:/lib/ld64.so.1...Reading /lib/ld-2.19.so from remote target...
Reading /lib/.debug/ld-2.19.so from remote target...
(no debugging symbols found)...done.
0x000003fffdfd9280 in ?? () from target:/lib/ld64.so.1
(gdb) continue
Continuing.
Reading /lib/s390x-linux-gnu/libpthread.so.0 from remote target...
Reading /lib/s390x-linux-gnu/libm.so.6 from remote target...
Reading /lib/s390x-linux-gnu/libc.so.6 from remote target...
Reading /lib/s390x-linux-gnu/libpthread-2.19.so from remote target...
Reading /lib/s390x-linux-gnu/.debug/libpthread-2.19.so from remote target...
Reading /lib/s390x-linux-gnu/libm-2.19.so from remote target...
Reading /lib/s390x-linux-gnu/.debug/libm-2.19.so from remote target...
Reading /lib/s390x-linux-gnu/libc-2.19.so from remote target...
Reading /lib/s390x-linux-gnu/.debug/libc-2.19.so from remote target...

Breakpoint 1, main () at /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/watchpoint-fork-mt.c:117
117	  setbuf (stdout, NULL);
(gdb) watch var
Hardware watchpoint 2: var
(gdb) PASS: gdb.threads/watchpoint-fork.exp: child: multithreaded: set the watchpoint
hbreak marker
Hardware assisted breakpoint 3 at 0x80000c6a: file /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/watchpoint-fork-mt.c, line 42.
(gdb) PASS: gdb.threads/watchpoint-fork.exp: child: multithreaded: hbreak marker
break mark_exit
Breakpoint 4 at 0x80000c9a: file /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/watchpoint-fork-mt.c, line 52.
(gdb) continue
Continuing.
Warning:
Cannot insert hardware breakpoint 3.
Could not insert hardware watchpoint 2.
Could not insert hardware breakpoints:
You may have requested too many hardware breakpoints/watchpoints.

Command aborted.
(gdb) FAIL: gdb.threads/watchpoint-fork.exp: child: multithreaded: hardware breakpoints work
continue
Continuing.
FAIL: gdb.threads/watchpoint-fork.exp: child: multithreaded: singlethread watchpoints work (timeout)
continue
FAIL: gdb.threads/watchpoint-fork.exp: child: multithreaded: multithreaded watchpoints work at A (timeout)
continue
FAIL: gdb.threads/watchpoint-fork.exp: child: multithreaded: multithreaded watchpoints work at B (timeout)
continue
FAIL: gdb.threads/watchpoint-fork.exp: child: multithreaded: breakpoint (A) after the first fork (timeout)
continue
FAIL: gdb.threads/watchpoint-fork.exp: child: multithreaded: watchpoint A after the first fork (timeout)
continue
FAIL: gdb.threads/watchpoint-fork.exp: child: multithreaded: watchpoint B after the first fork (timeout)
continue
FAIL: gdb.threads/watchpoint-fork.exp: child: multithreaded: breakpoint (A) after the second fork (timeout)
continue
FAIL: gdb.threads/watchpoint-fork.exp: child: multithreaded: watchpoint A after the second fork (timeout)
continue
FAIL: gdb.threads/watchpoint-fork.exp: child: multithreaded: watchpoint B after the second fork (timeout)
continue
FAIL: gdb.threads/watchpoint-fork.exp: child: multithreaded: finish (timeout)
Remote debugging from host 127.0.0.1
monitor exit
testcase /home/dje/src/binutils-gdb/gdb/testsuite/gdb.threads/watchpoint-fork.exp completed in 361 seconds

		=== gdb Summary ===

# of expected passes		22
# of unexpected failures	36
Executing on host: /home/dje/build/GDB/gdb/testsuite/../../gdb/gdb -nw -nx -data-directory /home/dje/build/GDB/gdb/testsuite/../data-directory --version    (timeout = 300)
spawn -ignore SIGHUP /home/dje/build/GDB/gdb/testsuite/../../gdb/gdb -nw -nx -data-directory /home/dje/build/GDB/gdb/testsuite/../data-directory --version
GNU gdb (GDB) 8.0.50.20171215-git
Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "s390x-ibm-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word".
/home/dje/build/GDB/gdb/testsuite/../../gdb/gdb version  8.0.50.20171215-git -nw -nx -data-directory /home/dje/build/GDB/gdb/testsuite/../data-directory  -ex "set auto-connect-native-target off"

runtest completed at Fri Dec 15 17:53:30 2017

[-- Attachment #6: watchpoints.log --]
[-- Type: application/octet-stream, Size: 7105 bytes --]

Test Run By dje on Fri Dec 15 17:43:42 2017
Native configuration is s390x-ibm-linux-gnu

		=== gdb tests ===

Schedule of variations:
    native-gdbserver

Running target native-gdbserver
Using /home/dje/src/binutils-gdb/gdb/testsuite/boards/../boards/native-gdbserver.exp as board description file for target.
Using /home/dje/src/binutils-gdb/gdb/testsuite/boards/../boards/gdbserver-base.exp as board description file for target.
Using /home/dje/src/binutils-gdb/gdb/testsuite/boards/../boards/local-board.exp as board description file for target.
Using /home/dje/src/binutils-gdb/gdb/testsuite/config/gdbserver.exp as tool-and-target-specific interface file.
Running /home/dje/src/binutils-gdb/gdb/testsuite/gdb.base/watchpoints.exp ...
get_compiler_info: gcc-4-9-2
Executing on host: gcc   -c -g  -o /home/dje/build/GDB/gdb/testsuite/outputs/gdb.base/watchpoints/watchpoints0.o /home/dje/src/binutils-gdb/gdb/testsuite/gdb.base/watchpoints.c    (timeout = 300)
spawn -ignore SIGHUP gcc -c -g -o /home/dje/build/GDB/gdb/testsuite/outputs/gdb.base/watchpoints/watchpoints0.o /home/dje/src/binutils-gdb/gdb/testsuite/gdb.base/watchpoints.c
Executing on host: gcc  /home/dje/build/GDB/gdb/testsuite/outputs/gdb.base/watchpoints/watchpoints0.o  -g  -lm   -o /home/dje/build/GDB/gdb/testsuite/outputs/gdb.base/watchpoints/watchpoints    (timeout = 300)
spawn -ignore SIGHUP gcc /home/dje/build/GDB/gdb/testsuite/outputs/gdb.base/watchpoints/watchpoints0.o -g -lm -o /home/dje/build/GDB/gdb/testsuite/outputs/gdb.base/watchpoints/watchpoints
spawn /home/dje/build/GDB/gdb/testsuite/../../gdb/gdb -nw -nx -data-directory /home/dje/build/GDB/gdb/testsuite/../data-directory -ex set auto-connect-native-target off
GNU gdb (GDB) 8.0.50.20171215-git
Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "s390x-ibm-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word".
(gdb) set height 0
(gdb) set width 0
(gdb) dir
Reinitialize source path to empty? (y or n) y
Source directories searched: $cdir:$cwd
(gdb) dir /home/dje/src/binutils-gdb/gdb/testsuite/gdb.base
Source directories searched: /home/dje/src/binutils-gdb/gdb/testsuite/gdb.base:$cdir:$cwd
(gdb) kill
The program is not being run.
(gdb) file /home/dje/build/GDB/gdb/testsuite/outputs/gdb.base/watchpoints/watchpoints
Reading symbols from /home/dje/build/GDB/gdb/testsuite/outputs/gdb.base/watchpoints/watchpoints...done.
(gdb) set can-use-hw-watchpoints 0
(gdb) watch ival1
Watchpoint 1: ival1
(gdb) PASS: gdb.base/watchpoints.exp: before inferior start: create watchpoint
awatch ival1
Can't set read/access watchpoint when hardware watchpoints are disabled.
(gdb) PASS: gdb.base/watchpoints.exp: before inferior start: create access watchpoint
rwatch ival1
Can't set read/access watchpoint when hardware watchpoints are disabled.
(gdb) PASS: gdb.base/watchpoints.exp: before inferior start: create read watchpoint
spawn /home/dje/build/GDB/gdb/testsuite/../../gdb/gdb -nw -nx -data-directory /home/dje/build/GDB/gdb/testsuite/../data-directory -ex set auto-connect-native-target off
GNU gdb (GDB) 8.0.50.20171215-git
Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "s390x-ibm-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word".
(gdb) set height 0
(gdb) set width 0
(gdb) dir
Reinitialize source path to empty? (y or n) y
Source directories searched: $cdir:$cwd
(gdb) dir /home/dje/src/binutils-gdb/gdb/testsuite/gdb.base
Source directories searched: /home/dje/src/binutils-gdb/gdb/testsuite/gdb.base:$cdir:$cwd
(gdb) kill
The program is not being run.
(gdb) file /home/dje/build/GDB/gdb/testsuite/outputs/gdb.base/watchpoints/watchpoints
Reading symbols from /home/dje/build/GDB/gdb/testsuite/outputs/gdb.base/watchpoints/watchpoints...done.
(gdb) delete breakpoints
(gdb) info breakpoints
No breakpoints or watchpoints.
(gdb) break main
Breakpoint 1 at 0x800005aa: file /home/dje/src/binutils-gdb/gdb/testsuite/gdb.base/watchpoints.c, line 33.
(gdb) kill
The program is not being run.
(gdb) spawn /home/dje/build/GDB/gdb/testsuite/../gdbserver/gdbserver --once :2346 /home/dje/build/GDB/gdb/testsuite/outputs/gdb.base/watchpoints/watchpoints
Process /home/dje/build/GDB/gdb/testsuite/outputs/gdb.base/watchpoints/watchpoints created; pid = 14063
Listening on port 2346
target remote localhost:2346
Remote debugging using localhost:2346
Reading /lib/ld64.so.1 from remote target...
warning: File transfers from remote targets can be slow. Use "set sysroot" to access files locally instead.
Reading /lib/ld64.so.1 from remote target...
Reading symbols from target:/lib/ld64.so.1...Reading /lib/ld-2.19.so from remote target...
Reading /lib/.debug/ld-2.19.so from remote target...
(no debugging symbols found)...done.
0x000003fffdfd9280 in ?? () from target:/lib/ld64.so.1
(gdb) continue
Continuing.
Reading /lib/s390x-linux-gnu/libm.so.6 from remote target...
Reading /lib/s390x-linux-gnu/libc.so.6 from remote target...
Reading /lib/s390x-linux-gnu/libm-2.19.so from remote target...
Reading /lib/s390x-linux-gnu/.debug/libm-2.19.so from remote target...
Reading /lib/s390x-linux-gnu/libc-2.19.so from remote target...
Reading /lib/s390x-linux-gnu/.debug/libc-2.19.so from remote target...

Breakpoint 1, main () at /home/dje/src/binutils-gdb/gdb/testsuite/gdb.base/watchpoints.c:33
33	  for (count = 0; count < 4; count++) {
(gdb) watch ival1
Hardware watchpoint 2: ival1
(gdb) watch ival3
Hardware watchpoint 3: ival3
(gdb) cont
Continuing.
Warning:
Could not insert hardware watchpoint 2.
Could not insert hardware watchpoint 3.
Could not insert hardware breakpoints:
You may have requested too many hardware breakpoints/watchpoints.

Command aborted.
(gdb) FAIL: gdb.base/watchpoints.exp: watchpoint hit, first time
cont
Continuing.
FAIL: gdb.base/watchpoints.exp: watchpoint hit, first time (timeout)
info break
FAIL: gdb.base/watchpoints.exp: watchpoint hit count is 1 (timeout)
cont

Re: [BuildBot] Notifications disabled for Debian-s390x-* and Fedora-ppc64*-* builders

[Andreas Arnez]

On Fri, Dec 15 2017, David Edelsohn wrote:

> Reverting to an earlier revision of the DejaGNU Framework did not help.
>
> I also updated all of the packages installed on the Debian system,
> including the kernel, but the problem still remains.  make check is
> reporting a large number of timeouts in gdb.base and gdb.thread. At
> 300s per timeout, it adds up -- eventually to 9 hours.  Some of the
> log files are attached.

I can reproduce the hangs with native-gdbserver on s390x; at least for:

  display.exp
  step-over-trips-on-watchpoint.exp
  watchpoint-fork.exp
  watchpoints.exp

A bisect shows the culprit:

  https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=commit;h=c65d6b55

Before this commit I see many FAILs with these tests, but no hangs.
(The FAILs are due to lack of hardware watchpoint support for gdbserver
on s390.  At some time I had started a patch for that; maybe I should
revive it...)

Even knowing the first broken commit, I'm not sure yet what causes the
hangs.  I'll look more into that tomorrow.

--
Andreas

Re: [BuildBot] Notifications disabled for Debian-s390x-* and Fedora-ppc64*-* builders

[Sergio Durigan Junior]

On Friday, December 15 2017, David Edelsohn wrote:

> On Fri, Dec 15, 2017 at 9:20 AM, Sergio Durigan Junior
> <sergiodj@redhat.com> wrote:
>> On Friday, December 15 2017, David Edelsohn wrote:
>>
>>> On Fri, Dec 15, 2017 at 8:45 AM, Sergio Durigan Junior
>>> <sergiodj@redhat.com> wrote:
>>>> Hi there,
>>>>
>>>> This is a small announcemente to let you know that I have disabled
>>>> e-mail notifications for a few builders.
>>>>
>>>> All of the Fedora-ppc*-* builders:
>>>>
>>>>   Fedora-ppc64be-m64
>>>>   Fedora-ppc64be-native-gdbserver-m64
>>>>   Fedora-ppc64be-native-extended-gdbserver-m64
>>>>   Fedora-ppc64be-cc-with-index
>>>>   Fedora-ppc64le-m64
>>>>   Fedora-ppc64le-native-gdbserver-m64
>>>>   Fedora-ppc64le-native-extended-gdbserver-m64
>>>>   Fedora-ppc64le-cc-with-index
>>>>
>>>> All of the Debian-s390x-* builders:
>>>>
>>>>   Debian-s390x-m64
>>>>   Debian-s390x-native-gdbserver-m64
>>>>   Debian-s390x-native-extended-gdbserver-m64
>>>>
>>>> I have also removed them from the list of Try Builders, so if you use
>>>> the try build, please update your config file.  An updated list can be
>>>> found here:
>>>>
>>>>   <https://sourceware.org/gdb/wiki/BuildBot#Available_Builders>
>>>>
>>>> I took this decision after noticing that these builders have been
>>>> lagging behind for quite some time.  Some of them have more than 900
>>>> queued builds!
>>>>
>>>> I've been talking with Edjunior Machado about the PPC64* machines.
>>>> Unfortunately it appears that Minicloud, the project that provided the
>>>> machines, is going through some difficulties right now.  We're now
>>>> investigating the possibility to move these resources to the GCC Compile
>>>> Farm.
>>>>
>>>> As for the s390x machine, I haven't had the chance to investigate
>>>> further what is happening.
>>>>
>>>> I would like to take this opportunity to invite more people/companies to
>>>> join our BuildBot effort!  There's always opportunity for improvement,
>>>> and we're always looking for more machines and architectures to add to
>>>> our infrastructure.  If you have interest, please get in touch (in
>>>> private) with me and we'll get the ball rolling.
>>>
>>> This decision is beyond stupid and completely negates the purpose of
>>> the buildbots.  GDB testsuite now requieres 9 hours to complete on
>>> s390x.  Something is fundamentally broken.  Instead of the GDB
>>> community noticing the issue, investigating, and fixing, it chooses to
>>> ignore the problem.
>>
>> Hi David,
>>
>> Perhaps I should have explained better.  The only thing that I did was
>> to disable the email notifications, that's all.  The builders are still
>> going to keep building the commits, and the results are still going to
>> be displayed in the website.  This is hopefully a temporary action to
>> avoid the report of false positives (like we're seeing with PPC64BE, for
>> example), and to give us more time to investigate what is going on with
>> the machines/GDB and take necessary actions.
>>
>>> And yet you ask for more companies to participate and contribute build
>>> bots. Why should any company participate when the response is pathetic
>>> and issues that the buildbots raise are ignored?  Companies should not
>>> participate until the GDB community shows some interest in utilizing
>>> and showing appreciation for the valuable resources contributed to the
>>> program.  Otherwise this is just a vanity project for Sergio  with no
>>> real benefit to the stability of GDB on the architectures, nor to the
>>> companies.
>>
>> I find this part very offensive.  Even though I run the BuildBot with my
>> own resources, I cannot keep track of all the failures that happen all
>> the time, and I also cannot monitor the machines attached to the
>> BuildBot master.  What I try to do is to look, from time to time, at the
>> status of each buildslave and get in touch with the owner of the machine
>> if there's something strange.  This is not the first time I have had to
>> disable e-mail notifications for specific builders, for example.  So
>> far, we managed to solve all the problems that appeared with the
>> buildslaves.  I hope we can keep working together and doing that.
>>
>> Our BuildBot sends the testsuite reports to the gdb-testers mailing
>> list.  It is somewhat hard to keep track of the messages there, but it
>> would be good if we had more eyes looking at the list.  Aside from that,
>> I consider that the Try Builds and the breakage emails are nice features
>> that have helped us.
>>
>> So yeah, it would be good to see more people interested in the project.
>> I personally don't consider this a vanity project, but by all means, if
>> the community doesn't see value in this then please tell me, because I
>> certainly could find other uses for the resources I dedicate to this.
>
> Sergio,
>
> I believe that the GDB buildbots should be useful to the GDB community
> and I appreciate your efforts to maintain it.
>
> But the irony in your message should not be ignored.  You implicitly
> express that the buildbots are ignored, except possibly x86 and Try
> Builds on x86, while you proceed to ask for additional participation.
> This is fundamentally inconsistent.  Actions speak louder than words
> and this demonstrates the priorities of the GDB community.

David,

There is absolutely no irony in my message, and please do not take my
words as being the official GDB community position.

Perhaps I should have explained it better in my e-mail, but again, I am
absolutely not disabling anything other than e-mail notifications, and
again, this is a temporary action until we figure things out with these
machines.

The only reason I also asked for more participation in my e-mail is
because I do not want to send two e-mails regarding BuildBot things to
gdb-patches.  I try to keep the "noise" about the project to a minimum
here (perhaps I should be more vocal and report whenever there's a
change, but that's another question).

Anyway, I do hope that things are more clear right now.  This has
nothing to do with "not caring about these architectures" or "blindly
ignoring the failures" or "the world doesn't like my contributions".  It
is just a temporary thing.

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/

Re: [BuildBot] Notifications disabled for Debian-s390x-* and Fedora-ppc64*-* builders

[Yao Qi]

On Fri, Dec 15, 2017 at 2:34 PM, David Edelsohn <dje.gcc@gmail.com> wrote:
>
> But the irony in your message should not be ignored.  You implicitly
> express that the buildbots are ignored, except possibly x86 and Try
> Builds on x86, while you proceed to ask for additional participation.

How do you get such implicit message?  That is your bias.  We still have
aarch64 and aarch32 buildslaves, they are quite stable, and catches
some build failures with g++ 4.8 and regressions.

These builders are disabled because they are useless.  Sergio asks for
participation to make these builders useful.  If no one wants to make these
builders better, or cares about them, it is reasonable to disable them.  It
is equivalent to code/feature/port deprecation, if nobody maintains the
code/feature/port, we'll deprecate it.

> This is fundamentally inconsistent.  Actions speak louder than words
> and this demonstrates the priorities of the GDB community.

I don't see the inconsistency here.  We need more participation or contribution
to make these builders more useful, it is simple, isn't?

-- 
Yao (齐尧)

Re: [BuildBot] Notifications disabled for Debian-s390x-* and Fedora-ppc64*-* builders

[David Edelsohn]

On Fri, Dec 15, 2017 at 4:19 PM, Yao Qi <qiyaoltc@gmail.com> wrote:
> On Fri, Dec 15, 2017 at 2:34 PM, David Edelsohn <dje.gcc@gmail.com> wrote:
>>
>> But the irony in your message should not be ignored.  You implicitly
>> express that the buildbots are ignored, except possibly x86 and Try
>> Builds on x86, while you proceed to ask for additional participation.
>
> How do you get such implicit message?  That is your bias.  We still have
> aarch64 and aarch32 buildslaves, they are quite stable, and catches
> some build failures with g++ 4.8 and regressions.
>
> These builders are disabled because they are useless.  Sergio asks for
> participation to make these builders useful.  If no one wants to make these
> builders better, or cares about them, it is reasonable to disable them.  It
> is equivalent to code/feature/port deprecation, if nobody maintains the
> code/feature/port, we'll deprecate it.
>
>> This is fundamentally inconsistent.  Actions speak louder than words
>> and this demonstrates the priorities of the GDB community.
>
> I don't see the inconsistency here.  We need more participation or contribution
> to make these builders more useful, it is simple, isn't?

The buildbots are the responsibility of both the organization
providing the servers and the community. No one from the community
noticed anything wrong with the s390x debian buildbot for months. And
no one said: "Hey, it looks like something is wrong with this
buildbot, can the s390x community take a look?"  The message was: "The
warning messages from the buildbot are annoying, so we're disabling
them."

ARM is running their own CI. If they are the ones noticing the
problems and reporting the problems from the buildbot, they don't need
a public buildbot infrastructure to accomplish that.

It's not a good message to ask companies to contribute more resources
while rationalizing why the current resources are ignored or
under-utilized.  The GDB community apparently is overwhelmed by the
current resources, so additional resources would not help.

Thanks, David

Re: [BuildBot] Notifications disabled for Debian-s390x-* and Fedora-ppc64*-* builders

[Sergio Durigan Junior]

On Friday, December 15 2017, David Edelsohn wrote:

> On Fri, Dec 15, 2017 at 4:19 PM, Yao Qi <qiyaoltc@gmail.com> wrote:
>> On Fri, Dec 15, 2017 at 2:34 PM, David Edelsohn <dje.gcc@gmail.com> wrote:
>>>
>>> But the irony in your message should not be ignored.  You implicitly
>>> express that the buildbots are ignored, except possibly x86 and Try
>>> Builds on x86, while you proceed to ask for additional participation.
>>
>> How do you get such implicit message?  That is your bias.  We still have
>> aarch64 and aarch32 buildslaves, they are quite stable, and catches
>> some build failures with g++ 4.8 and regressions.
>>
>> These builders are disabled because they are useless.  Sergio asks for
>> participation to make these builders useful.  If no one wants to make these
>> builders better, or cares about them, it is reasonable to disable them.  It
>> is equivalent to code/feature/port deprecation, if nobody maintains the
>> code/feature/port, we'll deprecate it.
>>
>>> This is fundamentally inconsistent.  Actions speak louder than words
>>> and this demonstrates the priorities of the GDB community.
>>
>> I don't see the inconsistency here.  We need more participation or contribution
>> to make these builders more useful, it is simple, isn't?
>
> The buildbots are the responsibility of both the organization
> providing the servers and the community. No one from the community
> noticed anything wrong with the s390x debian buildbot for months. And
> no one said: "Hey, it looks like something is wrong with this
> buildbot, can the s390x community take a look?"  The message was: "The
> warning messages from the buildbot are annoying, so we're disabling
> them."

David,

I contacted you back in private in October and let you know that your
buildslave was having issues.  The same way, by the way, that I also
contacted Edjunior about problems I was seeing with the PPC64 machines.

You replied to me with the same line you used here: "The machine is
fine, has lots of resources, there's nothing wrong".  Unfortunately I
could not dedicate more time to the issue I was seeing, but as Yao said,
s390x is not my priority and I thought it would be better to ask someone
else to have a look.  I assume you have more contact with the s390x
community than I do, but I don't know if you relayed my message to them
as well.

I will repeat: I did not disable the email notifications "because they
are annoying".  I disabled them because the Debian s390x, under your
supervision, have a backlog of more than 900 builds.  It is
counterproductive to let the notifications enabled in this case, because
(a) there is something clearly wrong happening, and (b) when a developer
asks for a Try Build, he/she expects the results e-mail to arrive in a
timely manner.

Anyway, I can't believe I'm having to explain these things again here.
So this will be my last post on this subject.

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/

Re: [BuildBot] Notifications disabled for Debian-s390x-* and Fedora-ppc64*-* builders

[Joel Brobecker]

> Anyway, I can't believe I'm having to explain these things again here.
> So this will be my last post on this subject.

It seems to me that the root of the discussion comes from conflicting
expectations as to who should be caring about what. In particular,
should the entire responsibility of caring for a given platform be
transfered over to "the community" as soon as a build bot is
contributed?

The GDB project being a volunteer-based community-driven project,
a port, and the associated resources, can only survive if there is
a group of people with time and motivation to match both the port
and the available resources. When resources are put in place for
those platforms, and those resources fail to be useful, the people
to turn to for answers are those who pushed for them to be put
in place. Asking the community in general to be responsible does
not seem like an attainable goal, nor is it attractive to me.

That is not to say that the community is entirely care free either.
I think we see nearly every day people cooperating on subjects
that do not directly matter to them, and as far as I am concerned
going well beyond the call of duty. But there has to be a reasonable
limit to what we ask of people to help for other platforms.
Contributing hardware is not a fire-and-forget thing. For the issues
with the buildbots, there has to be someone who has a stake in
those platforms, and willing to drive the effort in getting those
back in shape. These are the people we should turn to, not the
person who provides the service for those who want to. And if there
are none and the resource becomes a nuisance rather than a help,
then the logical answer is to remove it.

If anything, what this discussion leads me to, is that the lessons
learned here is that we should be clearer about an identified group
who would be responsible for what before a new buildbot is being put
in place, and also about what level of "service" can be expected
from the people maintaining the infrastructure, vs what concerns
the platforms the buildbots build and test.

Hopefully this will reconcile the idea of silencing a couple of
buildbots with the idea of calling for additional participation.
For me, there is no conflict in adding buildbots while silencing
others if there is a fully motivated group beind some, and not
enough behind others.

And finally, I felt the attacks on Sergio were really no way
to communicate with someone we're supposed to cooperate with.
I hope we all understand that, and we all know that there are
other ways to express contradicting opinions that are just
as effective and may even gain you a bit of extra goodwill.

-- 
Joel

Re: [BuildBot] Notifications disabled for Debian-s390x-* and Fedora-ppc64*-* builders

[Yao Qi]

On Fri, Dec 15, 2017 at 10:40 PM, David Edelsohn <dje.gcc@gmail.com> wrote:
>
> ARM is running their own CI. If they are the ones noticing the
> problems and reporting the problems from the buildbot, they don't need
> a public buildbot infrastructure to accomplish that.

No, I am talking about aarch64 and aarch32 buildslaves in *public* GDB
buildbot.

https://gdb-build.sergiodj.net/buildslaves/ubuntu-aarch64-1
https://gdb-build.sergiodj.net/buildslaves/ubuntu-trusty-aarch32-1

The public aarch64/aarch32 buildslaves are helpful to everyone, that is
the reason why Sergio spent much effort setting public gdb buildbot.

-- 
Yao (齐尧)

[BuildBot] Notifications re-enabled for the Debian-s390x-* builders (was: Re: [BuildBot] Notifications disabled for Debian-s390x-* and Fedora-ppc64*-* builders)

[Sergio Durigan Junior]

On Friday, December 15 2017, I wrote:

> Hi there,
>
> This is a small announcemente to let you know that I have disabled
> e-mail notifications for a few builders.
>
> All of the Fedora-ppc*-* builders:
>
>   Fedora-ppc64be-m64
>   Fedora-ppc64be-native-gdbserver-m64
>   Fedora-ppc64be-native-extended-gdbserver-m64
>   Fedora-ppc64be-cc-with-index
>   Fedora-ppc64le-m64
>   Fedora-ppc64le-native-gdbserver-m64
>   Fedora-ppc64le-native-extended-gdbserver-m64
>   Fedora-ppc64le-cc-with-index
>
> All of the Debian-s390x-* builders:
>
>   Debian-s390x-m64
>   Debian-s390x-native-gdbserver-m64
>   Debian-s390x-native-extended-gdbserver-m64

Hi,

This is just to confirm that I've reenabled the e-mail notifications for
the Debian-s390x* builders.  Thanks to Andreas's patch, the full build +
testsuite run now takes less than 20 minutes, instead of the 7+ hours we
were seeing before.  Thanks, Andreas!

I've also updated the list of available builders for the Try Build:

  https://sourceware.org/gdb/wiki/BuildBot#Available_Builders

So go ahead and update your list, please.

I'm waiting for the results on the PPC builders, but apparently things
are looking good on that front too.

Thanks,

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/