From: Manfred Hollstein <manfred@s-direktnet.de>
To: bfd@cygnus.com, gas2@cygnus.com
Cc: Manfred.Hollstein@ks.sel.alcatel.de
Subject: Bugs in recent snapshots on Solaris
Date: Fri, 13 Mar 1998 00:47:00 -0000 [thread overview]
Message-ID: <13576.61624.313896.482781@slsvhmt> (raw)
Didn't anybody else see this? When make check is running the shared
tests in the ld directory, it'll never stop. Instead I'll get a CPU
hungry process tmpdir/shp running and running and ... I have no idea
what it's doing, size won't change (increase or decrease), but it
really hogs my CPU (top reports right now 0.0% idle!).
This is with yesterday's snapshot (gas-980312), but I've observed it
with 0303 as well. I haven't investigated, when this problem has been
introduced, but at least 980219 is working without problems.
Interestingly, this only happens on sparc-sun-solaris2.5.1, not on
sparc-sun-sunos4.1.4.
Thanks for you time.
manfred
next reply other threads:[~1998-03-13 0:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-03-13 0:47 Manfred Hollstein [this message]
1998-03-13 1:21 ` Manfred Hollstein
1998-03-13 16:09 ` Ken Raeburn
1998-03-20 2:30 ` Richard Henderson
1998-03-20 8:19 ` H.J. Lu
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=13576.61624.313896.482781@slsvhmt \
--to=manfred@s-direktnet.de \
--cc=Manfred.Hollstein@ks.sel.alcatel.de \
--cc=bfd@cygnus.com \
--cc=gas2@cygnus.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).