|
From: | John Marino |
Subject: | [Octave-bug-tracker] [bug #38175] 3.6.4rc1 doesn't build with gfortran from gcc 4.7, script never exits after segfault |
Date: | Mon, 28 Jan 2013 17:14:24 +0000 |
User-agent: | Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.17 (KHTML, like Gecko) Chrome/24.0.1312.56 Safari/537.17 |
Follow-up Comment #3, bug #38175 (project octave): "I very much don't see this. Are you sure it's genuinely hanging or is Octave just taking a long time to save the workspace? Do you see any CPU activity? (It's not really a core dump, when Octave crashes, it tries to save the current workspace.) Furthermore, run-octave is a very simple bash script for running Octave in the build dir, you can read it yourself. This should not be the source of trouble with the build hanging." To address this closer: 1. long time? How long is long? is 30 minutes normal? An hour? I've seen this package locked at least that long. 2. CPU activity? CPU is at 97%+ without change until it is killed How big can the workspace be during this build step? Yes, I assume 30 - 60 minutes more than enough time to save its workspace. _______________________________________________________ Reply to this item at: <http://savannah.gnu.org/bugs/?38175> _______________________________________________ Message sent via/by Savannah http://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |