|
From: | Rik |
Subject: | [Octave-bug-tracker] [bug #44360] segfault in test ov-class.cc-tst |
Date: | Thu, 30 Apr 2015 16:13:29 +0000 |
User-agent: | Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:37.0) Gecko/20100101 Firefox/37.0 |
Update of bug #44360 (project octave): Open/Closed: Closed => Open _______________________________________________________ Follow-up Comment #23: Re-opening this bug report since it is evidently still reproducible. Could the original reporter run the following: ./run-octave -g -f --no-gui-libs (gdb) run octave:1> test ov-class.cc (gdb) bt # Only execute the backtrace if Octave has segfaulted above I want to confirm that the problem is solely an interaction between the JVM and Octave's class files. The other possibility is that there has been a memory leak in some of the previous tests executed by make check which is only later resulting in a segfault. _______________________________________________________ Reply to this item at: <http://savannah.gnu.org/bugs/?44360> _______________________________________________ Message sent via/by Savannah http://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |