From: "woodard at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/18890] libabigail hangs while processing DWARF
Date: Thu, 01 Jan 2015 00:00:00 -0000 [thread overview]
Message-ID: <bug-18890-9487-lCTBEOpe0h@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-18890-9487@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=18890
--- Comment #9 from Ben Woodard <woodard at redhat dot com> ---
Dodji maybe you can grab a machine with more memory to track this one down or
just add a big swap file. It appears to need about 8GB of RAM for this to run.
It has been using 8GB for more than an hour now and it hasn't seemed to budge.
6599 ben 20 0 8337m 8.0g 148m R 99.9 6.4 121:51.45 abidw
As you can see it has been running for more than 2 hours now on a fast CPU a
Intel(R) Xeon(R) CPU E5-2670 0 @ 2.60GHz and so I think that there is a problem
here.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2015-10-20 21:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-01 0:00 [Bug default/18890] New: " woodard at redhat dot com
2015-01-01 0:00 ` [Bug default/18890] " woodard at redhat dot com
2015-01-01 0:00 ` woodard at redhat dot com
2015-01-01 0:00 ` woodard at redhat dot com
2015-01-01 0:00 ` dodji at redhat dot com
2015-01-01 0:00 ` woodard at redhat dot com
2015-01-01 0:00 ` woodard at redhat dot com
2015-01-01 0:00 ` woodard at redhat dot com
2015-01-01 0:00 ` woodard at redhat dot com
2015-01-01 0:00 ` woodard at redhat dot com
2015-01-01 0:00 ` woodard at redhat dot com
2015-01-01 0:00 ` dodji at seketeli dot org
2015-01-01 0:00 ` woodard at redhat dot com [this message]
2020-11-24 21:02 ` woodard at redhat dot com
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=bug-18890-9487-lCTBEOpe0h@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=libabigail@sourceware.org \
/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).