help-octave
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Octave Run Failure


From: Andrew Janke
Subject: Re: Octave Run Failure
Date: Wed, 5 Sep 2018 23:05:16 -0400
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.9.1



On 9/5/18 9:51 PM, Ben Abbott wrote:
On Sep 5, 2018, at 6:28 PM, Christopher Keller <address@hidden <mailto:address@hidden>> wrote:

Looking for some assistance. My son is required to use Octave for his physics class and after install the file continues to fail at Thread 9. What can i do to fix the issue? Thanks for any assistance that you can provide - Chris

System: 3.2 GHz Intel Core i5: 32 GB 1600 MHz DDR3
iMac OS High Sierra 10.13.6

Thread 9 Crashed:: QThread
0   liboctave.5.dylib 0x0000000104971458 void octave_sort<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > >::binarysort<bool (*)(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&)>(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >*, long long, long long, bool (*)(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&)) + 38 1   liboctave.5.dylib 0x0000000104965801 void octave_sort<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > >::sort<bool (*)(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&)>(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >*, long long, bool (*)(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&)) + 369
2   liboctave.5.dylib 0x0000000104dbbf3e string_vector::sort(bool) + 50
3   liboctinterp.5.dylib 0x000000010406c921 octave::genpath(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, string_vector const&) + 130 4   liboctinterp.5.dylib 0x000000010406378e maybe_add_path_elts(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >&, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&) + 51 5   liboctinterp.5.dylib 0x00000001040633cd octave::load_path::initialize(bool) + 255 6   liboctinterp.5.dylib 0x000000010405c31c octave::interpreter::initialize_load_path(bool) + 344 7   liboctinterp.5.dylib 0x000000010405c527 octave::interpreter::initialize() + 49 8   liboctgui.3.dylib 0x0000000103698d33 octave::octave_interpreter::execute() + 57
9   org.qt-project.QtCore 0x0000000106458201 QObject::event(QEvent*) + 801
10  org.qt-project.QtWidgets 0x0000000106d6ad2d QApplicationPrivate::notify_helper(QObject*, QEvent*) + 301 11  org.qt-project.QtWidgets 0x0000000106d6c131 QApplication::notify(QObject*, QEvent*) + 529 12  org.qt-project.QtCore 0x000000010642dd04 QCoreApplication::notifyInternal2(QObject*, QEvent*) + 164 13  org.qt-project.QtCore 0x000000010642eebb QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) + 891 14  org.qt-project.QtCore 0x0000000106486119 QEventDispatcherUNIX::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 73 15  org.qt-project.QtCore 0x0000000106429671 QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) + 417
16  org.qt-project.QtCore 0x0000000106269383 QThread::exec() + 115
17  org.qt-project.QtCore 0x0000000106272c67 0x106244000 + 191591
18  libsystem_pthread.dylib 0x00007fff6419f661 _pthread_body + 340
19  libsystem_pthread.dylib 0x00007fff6419f50d _pthread_start + 377
20  libsystem_pthread.dylib 0x00007fff6419ebf9 thread_start + 13

Recently, there has been a lot of effort to improve Octave on macOS. Thanks go out to Sebastian and Andrew.

https://octave-app.org

http://www.schoeps.org/home/tag/octave/

Please tell us how Octave was installed. If there is an old dmg bundle being linked to we may be able remove it and provide an updated link.

Ben



You're welcome! Thanks for the shout-out, Ben.

This use case - a student who's first discovering Octave and doesn't have institutional tech support - is exactly the use case we want to support with Octave.app, so I hope we can get this sorted out.

Christopher, could you also provide a description of the code you were running that caused Octave to crash, or if you weren't running M-code, maybe a description of what you had recently done in the GUI?

This stack trace doesn't look familiar to me, so it may not be something we've encountered before.

That "initialize_load_path(...)" in the stacktrace looks like this might be happening during Octave's startup sequence; is that the case?

Cheers,
Andrew




reply via email to

[Prev in Thread] Current Thread [Next in Thread]