From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: Pedro Alves <palves@redhat.com>
Cc: Sergio Durigan Junior <sergiodj@redhat.com>, gdb-patches@sourceware.org
Subject: Re: Breakage on builder Solaris11-amd64-m64, revision 080363310650c93ad8e93018bcb6760ba5d32d1c
Date: Sun, 25 Nov 2018 14:55:00 -0000 [thread overview]
Message-ID: <yddh8g5fbqb.fsf@CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <f765ee45-eaaa-eebc-c1f4-11aa6651b79b@redhat.com> (Pedro Alves's message of "Fri, 23 Nov 2018 16:39:07 +0000")
Hi Pedro,
>>> And the actual commit failed with another reason:
>>>
>>> https://gdb-build.sergiodj.net/builders/Solaris11-amd64-m64/builds/411/steps/compile%20gdb/logs/stdio
>>>
>>> ../../binutils-gdb/gdb/procfs.c: In function ‘int procfs_notice_thread(procinfo*, procinfo*, void*)’:
>>> ../../binutils-gdb/gdb/procfs.c:3136:41: error: ‘is_exited’ was not declared in this scope
>>> if (!in_thread_list (gdb_threadid) || is_exited (gdb_threadid))
>>> ^~~~~~~~~
>>> ../../binutils-gdb/gdb/procfs.c:3136:41: note: suggested alternative: ‘inf_exited’
>>> if (!in_thread_list (gdb_threadid) || is_exited (gdb_threadid))
>>> ^~~~~~~~~
>>> inf_exited
>>
>> this is weird: I still see a declaration in gdbthread.h (and also
>> is_running and is_stopped), which should go as well.
>
>That's because I meanwhile pushed this:
> https://sourceware.org/ml/gdb-patches/2018-11/msg00380.html
I only saw that commit after I'd sent my mail.
>So before that we got a link error, and now we get a compile
>error, which is expected.
>
>>
>> With just the typo above fixed, a local build on amd64-pc-solaris2.11
>> has just finished; make check running...
It took me a bit to double-check, but the differences in testsuite
results are within the (usual, mostly thread-related) variations.
So the patch is ok with the missing parenthesis added.
Thanks.
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
next prev parent reply other threads:[~2018-11-25 14:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-22 16:39 Oh dear. I regret to inform you that commit 080363310650c93ad8e93018bcb6760ba5d32d1c might be unfortunate gdb-buildbot
2018-11-22 16:39 ` Breakage on builder Solaris11-sparcv9-m64, revision 080363310650c93ad8e93018bcb6760ba5d32d1c gdb-buildbot
2018-11-22 16:49 ` Breakage on builder Solaris11-amd64-m64, " gdb-buildbot
2018-11-23 13:34 ` Pedro Alves
2018-11-23 14:06 ` Sergio Durigan Junior
2018-11-23 14:12 ` Sergio Durigan Junior
2018-11-23 14:16 ` Rainer Orth
2018-11-23 16:39 ` Pedro Alves
2018-11-25 14:55 ` Rainer Orth [this message]
2018-11-26 13:26 ` Pedro Alves
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=yddh8g5fbqb.fsf@CeBiTec.Uni-Bielefeld.DE \
--to=ro@cebitec.uni-bielefeld.de \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=sergiodj@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox