Re: gui branch: bus error

[Jacob Dawid]

Fritz,

thank you for your help! I will check that with QTranslator again, but I guess that it can't find the appropriate language file and therefore is trying to set an invalid QTranslator object (which is not checked).

I am glad that you like the GUI. Currently we face some threading problems when executing an octave script, these have to be fixed before we can "release" the GUI for productive use. It is very important for us to receive feature requests, but the safest method for proposing them is to create a feature request in the Savannah bugtracker:

http://savannah.gnu.org/bugs/?group=octave

However, to me it sounds as if you are potentially able to make some adjustments yourself. Keep in mind that we are always open to patches that you send us.

Thank you for your efforts!

Jacob

Am 24. Februar 2012 10:24 schrieb deraltefritz <address@hidden>:

Okay, I've found the source of error. Something goes wrong with QTranslator.


The gdp output is as follows:

Reading symbols from /home/fritz/lib/octave/gui/bin/octave-gui...done.
(gdb) r
Starting program: /home/fritz/lib/octave/gui/bin/octave-gui
[Thread debugging using libthread_db enabled]

Program received signal SIGBUS, Bus error.
0x00007ffff3136e14 in QTranslatorPrivate::do_load (this=0x707be0,
   data="" <Address 0x7ffff7fcf000 out of bounds>, len=4096) at
kernel/qtranslator.cpp:537
537     kernel/qtranslator.cpp: No such file or directory.
       in kernel/qtranslator.cpp


If I comment out  (int in OctaveGui.cpp) the following lines:

/* QString translatorFile = ResourceManager::instance ()->findTranslatorFile
(language);
QTranslator translator;
translator.load (translatorFile);
application.installTranslator (&translator); */

octave-gui starts up without any problems.

Thanks again,
Fritz


PS This might belong in a different thread, but I've noticed that the
"Current directory" window doesn't update the path when I "cd" somewhere
using the terminal, and vice-versa.

PPS And would it be possible to jump to the corresponding line/file where an
error occurs. Right now when I call a script from the terminal, and there's
an error in there, I still have to manually switch to that file and scroll
to the corresponding line. This, for me, is one of the most important things
in a GUI, as otherwise using a command prompt and my favorite text editor
does basically the same things.

If those two points could be corrected, I'd be switching from Matlab to
OctaveGui immediately !

--
View this message in context: http://octave.1599824.n4.nabble.com/gui-branch-bus-error-tp4413251p4416608.html

Sent from the Octave - Maintainers mailing list archive at Nabble.com.

--
„Alle sagten: Das geht nicht. Da kam einer, der wusste das nicht und hat's gemacht.“ - Unbekannt