From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: pedro@codesourcery.com
Cc: gdb@sourceware.org, brobecker@adacore.com
Subject: Re: Help with solaris testing
Date: Tue, 29 Jul 2008 15:43:00 -0000 [thread overview]
Message-ID: <200807291539.m6TFdFAd007825@brahms.sibelius.xs4all.nl> (raw)
In-Reply-To: <200807291558.22228.pedro@codesourcery.com> (message from Pedro Alves on Tue, 29 Jul 2008 15:58:21 +0100)
> From: Pedro Alves <pedro@codesourcery.com>
> Date: Tue, 29 Jul 2008 15:58:21 +0100
>
> Hi guys!
>
> (Mark, Joel, CCing you, as you're the usual suspects when we
> talk about either BSD or (!linux && !windows) testing :-) )
>
> I wonder if you could give me a little help with this.
>
> I've setup a bunch of VMWare VMs (x86) to be able to test changes I'm
> making to BSD targets. I've got FreeBSD 6,7, OpenBSD 4.3, and
> OpenSolaris 10 all set up. I set up an NFS mount on the host,
> so all VMs share the same source tree. All cool, and great
> for easy testing. FreeBSD and OpenBSD are OK, but ...
>
> ... solaris is giving be the troubles.
>
> When running the testsuite under Solaris, I get a bunch of failures
> and they appear to be related to something translating "\r" -> "\r\n".
> The eols end up being "\r\r\n" instead of "\r\n", and a lot of test
> patterns don't expect that.
>
> How do people test under solaris? Is this perhaps a well known
> issue with an easy well known fix?
This is strange; I've tested GDB on Solaris in the past and never
encountered this problem.
What does stty -a say on the system? Could it be that one of ocrnl or
onlret is set?
next prev parent reply other threads:[~2008-07-29 15:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-29 15:38 Pedro Alves
2008-07-29 15:43 ` Mark Kettenis [this message]
2008-08-05 13:49 ` Pedro Alves
2008-08-05 14:04 ` Daniel Jacobowitz
2008-08-05 14:33 ` Mark Kettenis
2008-08-07 22:32 ` 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=200807291539.m6TFdFAd007825@brahms.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=brobecker@adacore.com \
--cc=gdb@sourceware.org \
--cc=pedro@codesourcery.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