From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Obsolete/remove Solaris < 10 [was: Re: Fix gdb 8.1 Solaris compilation]
Date: Tue, 03 Oct 2017 13:01:00 -0000 [thread overview]
Message-ID: <yddy3os9yht.fsf@CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <db845c9a-49cf-b676-53fd-fa9718c588e3@redhat.com> (Pedro Alves's message of "Tue, 26 Sep 2017 15:21:20 +0100")
Hi Pedro,
> On 09/26/2017 03:18 PM, Pedro Alves wrote:
>>
>> On 09/26/2017 12:20 PM, Rainer Orth wrote:
>>>
>>> Testing is very weird, though: Linux/x86_64 only shows a few failures,
>>> but Solaris is a mess: on Solaris 10, the vast majority of tests time
>>> out (although gdb seems to work reasonably well interactively), while
>>> many more work on Solaris 11.4 until testing runs into what seems an
>>> infinite loop of
>>>
>>> FAIL: gdb.mi/mi-exec-run.exp: inferior-tty=main: mi=main: force-fail=1:
>>> run failure detected (timeout)
>>
>> I recall once trying to run the testsuite on OpenSolaris
>> (several years ago, maybe 2008.11, though I don't really
>> recall exactly), and running into lots and lots of timeouts.
>> I think it had something to do with gdb + expect + dejagnu not
>> agreeing over end lines, \r\n vs \n, etc. ISTR trying to
>> work around it with stty settings.
>>
>> I'm having trouble finding the email in the archives, though.
>
> Bah, I was looking in the wrong list, that's why...
>
> Here it is:
> https://sourceware.org/ml/gdb/2008-07/msg00292.html
> and the workaround:
> https://sourceware.org/ml/gdb/2008-08/msg00144.html
thanks for looking this up. However, further digging revealed that the
issue is slightly different for me. When I run a single testcase
(alias.exp), gdb.log shows
(gdb) ^M^[[K(gdb) alias -a set2=set^M
(gdb) ^M^[[K(gdb) FAIL: gdb.base/alias.exp: alias -a set2=set (timeout)
i.e. I get clr_eol/el (clear to end of line) after the prompt which
confuses the test framework. I haven't yet found what causes this.
However, I managed to hack around the issue for testing purposes by
configuring with --disable-tui: this way at least a vast majority of the
tests PASS.
The same issue still happens when I use a locally built libncurses 5.7
instead of the native libcurses.
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
next prev parent reply other threads:[~2017-10-03 13:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-21 13:02 Fix gdb 8.1 Solaris compilation Rainer Orth
2017-09-21 13:17 ` Andreas Schwab
2017-09-21 14:14 ` Rainer Orth
2017-09-21 14:31 ` Obsolete/remove Solaris < 10 [was: Re: Fix gdb 8.1 Solaris compilation] Rainer Orth
2017-09-21 14:39 ` Pedro Alves
2017-09-22 14:45 ` Rainer Orth
2017-09-22 15:40 ` Pedro Alves
2017-09-26 11:20 ` Rainer Orth
2017-09-26 11:26 ` Pedro Alves
2017-09-26 13:25 ` Rainer Orth
2017-09-26 13:45 ` Pedro Alves
2017-09-26 13:55 ` Rainer Orth
2017-09-26 14:18 ` Pedro Alves
2017-09-26 14:21 ` Pedro Alves
2017-10-03 13:01 ` Rainer Orth [this message]
2017-09-29 11:53 ` Eli Zaretskii
2017-09-21 14:21 ` Fix gdb 8.1 Solaris compilation Pedro Alves
2017-09-21 14:23 ` Rainer Orth
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=yddy3os9yht.fsf@CeBiTec.Uni-Bielefeld.DE \
--to=ro@cebitec.uni-bielefeld.de \
--cc=gdb-patches@sourceware.org \
--cc=palves@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