Binary packages for 3.8

classic Classic list List threaded Threaded
86 messages Options
12345
Reply | Threaded
Open this post in threaded view
|

Re: Binary packages for 3.8

c.-2

On 27 Oct 2013, at 18:58, Benjamin Abbott <[hidden email]> wrote:


> I suspect there is a problem with macports qscintilla 2.7 port
>
> Ben

Ben,
I prepared a port for qscintilla 2.6.2 which is older than the latest release but already includes the octave lexer, could you please try it out?

Torsten,
With qscintilla 2.6.2 I am able to build and run your minimal example, I'm now building Octave against it.

c.


qscintilla.port.tgz (3K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Binary packages for 3.8

Pantxo
In reply to this post by Alexander Hansen-2



2013/10/27 Alexander Hansen <[hidden email]>
On 10/27/13 12:04 PM, c. wrote:

On 27 Oct 2013, at 19:56, Alexander Hansen <[hidden email]> wrote:

Nobody can access our database.  The server it's on is out--we're hopefully going to get a new one up soonish.  The VCS browser works:

http://fink.cvs.sourceforge.net/viewvc/fink/dists/10.7/stable/main/finkinfo/devel/

According to

http://fink.cvs.sourceforge.net/viewvc/fink/dists/10.7/stable/main/finkinfo/devel/qscintilla2.8-qt4.info?revision=1.2&view=markup

the configure options just include the  default (--prefix=%p, where %p is the Fink tree), and the build-time patch is to append the full path to the library to its install_name:

perl -pi -e 's|install_name\t|install_name\t%p\/lib\/qt4-%type_pkg[qt]\/lib\/|' Makefile

Thanks Alexander,

That seems not to be any different from macports, which just uses all defaults as well ...
Except I see the Fink package is named "qscintilla2.8-qt4" are you using qscintilla 2.8?
I was not aware of the existence of that version ...

c.


The package is version 2.6.2. "2.8" refers to the version attached to its dynamic library.


--
Alexander Hansen, Ph.D.
Fink User Liaison
My package updates: http://finkakh.wordpress.com/

I finally managed to compile octave using fink dependencies (qt 4.7.3, qscintilla 2.6.2). For some reason I had to append `pkg-config --libs QtWebKit` (which also adds QtCore and QtGui) to LDFLAGS at configure time.

Trying to open a new file in the editor crashes octave as with macports. The backtrace is attached.

Pantxo

bt_crash_mac.txt (3K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Binary packages for 3.8

Torsten
On 27.10.2013 21:55, Pantxo Diribarne wrote:

>
>
>
> 2013/10/27 Alexander Hansen <[hidden email]
> <mailto:[hidden email]>>
>
>     On 10/27/13 12:04 PM, c. wrote:
>
>
>         On 27 Oct 2013, at 19:56, Alexander Hansen
>         <[hidden email]
>         <mailto:[hidden email]>> wrote:
>
>             Nobody can access our database.  The server it's on is
>             out--we're hopefully going to get a new one up soonish.  The
>             VCS browser works:
>
>             http://fink.cvs.sourceforge.__net/viewvc/fink/dists/10.7/__stable/main/finkinfo/devel/
>             <http://fink.cvs.sourceforge.net/viewvc/fink/dists/10.7/stable/main/finkinfo/devel/>
>
>             According to
>
>             http://fink.cvs.sourceforge.__net/viewvc/fink/dists/10.7/__stable/main/finkinfo/devel/__qscintilla2.8-qt4.info?__revision=1.2&view=markup
>             <http://fink.cvs.sourceforge.net/viewvc/fink/dists/10.7/stable/main/finkinfo/devel/qscintilla2.8-qt4.info?revision=1.2&view=markup>
>
>             the configure options just include the  default
>             (--prefix=%p, where %p is the Fink tree), and the build-time
>             patch is to append the full path to the library to its
>             install_name:
>
>             perl -pi -e
>             's|install_name\t|install___name\t%p\/lib\/qt4-%type_pkg[__qt]\/lib\/|'
>             Makefile
>
>
>         Thanks Alexander,
>
>         That seems not to be any different from macports, which just
>         uses all defaults as well ...
>         Except I see the Fink package is named "qscintilla2.8-qt4" are
>         you using qscintilla 2.8?
>         I was not aware of the existence of that version ...
>
>         c.
>
>
>     The package is version 2.6.2. "2.8" refers to the version attached
>     to its dynamic library.
>
>
>     --
>     Alexander Hansen, Ph.D.
>     Fink User Liaison
>     My package updates: http://finkakh.wordpress.com/
>
>
> I finally managed to compile octave using fink dependencies (qt 4.7.3,
> qscintilla 2.6.2). For some reason I had to append `pkg-config --libs
> QtWebKit` (which also adds QtCore and QtGui) to LDFLAGS at configure time.
>
> Trying to open a new file in the editor crashes octave as with macports.
> The backtrace is attached.
>
> Pantxo
Attached a patch that removes the apis (needed for auto completion) of
the lexer. This does not exist in the minimal example. Cpuld you please
test this?

Torsten



qsci_2_7_mac_p04.diff (2K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Binary packages for 3.8

bpabbott
Administrator
In reply to this post by c.-2
On Oct 27, 2013, at 3:59 PM, c. wrote:

> On 27 Oct 2013, at 18:58, Benjamin Abbott <[hidden email]> wrote:
>
>> I suspect there is a problem with macports qscintilla 2.7 port
>>
>> Ben
>
> Ben,
> I prepared a port for qscintilla 2.6.2 which is older than the latest release but already includes the octave lexer, could you please try it out?
>
> Torsten,
> With qscintilla 2.6.2 I am able to build and run your minimal example, I'm now building Octave against it.
>
> c.
>
> <qscintilla.port.tgz>

I'm on to building Octave.  The one problem I found with your port is that the designer.diff includes the line below

+LIBS += -L../Qt4 -l$$QSCI_LIB

But should point to Qt4Qt5

+LIBS += -L../Qt4Qt5 -l$$QSCI_LIB

Ben

Reply | Threaded
Open this post in threaded view
|

Re: Binary packages for 3.8

c.-2

On 27 Oct 2013, at 22:43, Ben Abbott <[hidden email]> wrote:

> On Oct 27, 2013, at 3:59 PM, c. wrote:
>
>> On 27 Oct 2013, at 18:58, Benjamin Abbott <[hidden email]> wrote:
>>
>>> I suspect there is a problem with macports qscintilla 2.7 port
>>>
>>> Ben
>>
>> Ben,
>> I prepared a port for qscintilla 2.6.2 which is older than the latest release but already includes the octave lexer, could you please try it out?
>>
>> Torsten,
>> With qscintilla 2.6.2 I am able to build and run your minimal example, I'm now building Octave against it.
>>
>> c.
>>
>> <qscintilla.port.tgz>
>
> I'm on to building Octave.  The one problem I found with your port is that the designer.diff includes the line below
>
> +LIBS += -L../Qt4 -l$$QSCI_LIB
>
> But should point to Qt4Qt5
>
> +LIBS += -L../Qt4Qt5 -l$$QSCI_LIB
>
> Ben
>
Thanks for nothing that, here's the corrected port.
c.


qscintilla.port.tgz (3K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Binary packages for 3.8

bpabbott
Administrator

On Oct 27, 2013, at 6:02 PM, c. wrote:

>
> On 27 Oct 2013, at 22:43, Ben Abbott <[hidden email]> wrote:
>
>> On Oct 27, 2013, at 3:59 PM, c. wrote:
>>
>>> On 27 Oct 2013, at 18:58, Benjamin Abbott <[hidden email]> wrote:
>>>
>>>> I suspect there is a problem with macports qscintilla 2.7 port
>>>>
>>>> Ben
>>>
>>> Ben,
>>> I prepared a port for qscintilla 2.6.2 which is older than the latest release but already includes the octave lexer, could you please try it out?
>>>
>>> Torsten,
>>> With qscintilla 2.6.2 I am able to build and run your minimal example, I'm now building Octave against it.
>>>
>>> c.
>>>
>>> <qscintilla.port.tgz>
>>
>> I'm on to building Octave.  The one problem I found with your port is that the designer.diff includes the line below
>>
>> +LIBS += -L../Qt4 -l$$QSCI_LIB
>>
>> But should point to Qt4Qt5
>>
>> +LIBS += -L../Qt4Qt5 -l$$QSCI_LIB
>>
>> Ben
>>
>
> Thanks for nothing that, here's the corrected port.
> c.
>
> <qscintilla.port.tgz>
My build completed.  I tried "edit foo.m" (foo.m does  not exist) and Octave crashed.  The log is attached.

Ben


crash.log (47K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Binary packages for 3.8

c.-2
In reply to this post by Torsten

On 27 Oct 2013, at 22:23, Torsten <[hidden email]> wrote:

> Attached a patch that removes the apis (needed for auto completion) of
> the lexer. This does not exist in the minimal example. Cpuld you please
> test this?
>
> Torsten

With QScintilla 2.6.2 installed and your patch applied I get the usual crash in Octave.
The minimal example works.
c.

* thread #1: tid = 0x23ffab, 0x00007fff894a0212 libsystem_kernel.dylib`__pthread_kill + 10, queue = 'com.apple.main-thread, stop reason = signal SIGABRT
    frame #0: 0x00007fff894a0212 libsystem_kernel.dylib`__pthread_kill + 10
    frame #1: 0x00007fff84a92b24 libsystem_c.dylib`pthread_kill + 90
    frame #2: 0x00007fff84ad6f61 libsystem_c.dylib`abort + 143
    frame #3: 0x00007fff84aaa989 libsystem_c.dylib`free + 392
    frame #4: 0x00007fff81c25b49 libstdc++.6.dylib`std::string::assign(std::string const&) + 77
    frame #5: 0x000000010254785d libqscintilla2.8.dylib`PropSetSimple::Set(char const*, char const*, int, int) + 141
    frame #6: 0x000000010258543e libqscintilla2.8.dylib`ScintillaBase::WndProc(unsigned int, unsigned long, long) + 1070
    frame #7: 0x0000000102459ba2 libqscintilla2.8.dylib`QsciScintilla::setLexer(QsciLexer*) + 466
    frame #8: 0x000000010004a06e liboctgui.0.dylib`file_editor_tab::update_lexer() + 1006
    frame #9: 0x000000010004aae8 liboctgui.0.dylib`file_editor_tab::notice_settings(QSettings const*) + 24
    frame #10: 0x000000010004d77e liboctgui.0.dylib`file_editor_tab::file_editor_tab(QString const&) + 1230
    frame #11: 0x0000000100050902 liboctgui.0.dylib`file_editor::request_new_file(QString const&) + 50
    frame #12: 0x00000001000a4693 liboctgui.0.dylib`file_editor_interface::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) + 563
    frame #13: 0x00000001023aa150 QtCore`qDetectCPUFeatures()::features + 8


Reply | Threaded
Open this post in threaded view
|

Re: Binary packages for 3.8

c.-2
In reply to this post by bpabbott

On 27 Oct 2013, at 18:58, Benjamin Abbott <[hidden email]> wrote:

> I suspect there is a problem with macports qscintilla 2.7 port
>
> Ben

In order to check that, I tried building and installing another qscintilla based IDE, "eric4".
Eric4 seems to work fine (it can create, save and load files with no crashes) with the macports
qscintilla 2.7 so I doubt the crash is due to that port itself ...
c.
Reply | Threaded
Open this post in threaded view
|

Re: Binary packages for 3.8

Torsten
In reply to this post by c.-2
On 27.10.2013 23:27, c. wrote:

>
> On 27 Oct 2013, at 22:23, Torsten <[hidden email]> wrote:
>
>> Attached a patch that removes the apis (needed for auto completion) of
>> the lexer. This does not exist in the minimal example. Cpuld you please
>> test this?
>>
>> Torsten
>
> With QScintilla 2.6.2 installed and your patch applied I get the usual crash in Octave.
> The minimal example works.
> c.
Attached another patch where all "extra" configurations of the
qscintilla editor is deleted. In principle a qscintilla editor is
created and the lexer is set, like in the minimal example. If the editor
is now able to open a file we have to go back step by step in order to
find out what is the problem.

Torsten



qsci_2_6_mac_p05.diff (10K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Binary packages for 3.8

c.-2

On 28 Oct 2013, at 08:07, Torsten <[hidden email]> wrote:

>
> Attached another patch where all "extra" configurations of the
> qscintilla editor is deleted. In principle a qscintilla editor is
> created and the lexer is set, like in the minimal example. If the editor
> is now able to open a file we have to go back step by step in order to
> find out what is the problem.
>
> Torsten

Hi,
Is this patch to be applied in addition or in place of the previous one?
Thank you,
c.
Reply | Threaded
Open this post in threaded view
|

Re: Binary packages for 3.8

c.-2

On 28 Oct 2013, at 09:32, c. <[hidden email]> wrote:

>
> On 28 Oct 2013, at 08:07, Torsten <[hidden email]> wrote:
>
>>
>> Attached another patch where all "extra" configurations of the
>> qscintilla editor is deleted. In principle a qscintilla editor is
>> created and the lexer is set, like in the minimal example. If the editor
>> is now able to open a file we have to go back step by step in order to
>> find out what is the problem.
>>
>> Torsten
>
> Hi,
> Is this patch to be applied in addition or in place of the previous one?
> Thank you,
> c.

Torsten, with this patch the crash does not occur anymore!!!
So what's the next step?

Thanks,
c.
Reply | Threaded
Open this post in threaded view
|

Re: Binary packages for 3.8

Torsten
On 28.10.2013 12:50, c. wrote:

>
> On 28 Oct 2013, at 09:32, c. <[hidden email]> wrote:
>
>>
>> On 28 Oct 2013, at 08:07, Torsten <[hidden email]> wrote:
>>
>>>
>>> Attached another patch where all "extra" configurations of the
>>> qscintilla editor is deleted. In principle a qscintilla editor is
>>> created and the lexer is set, like in the minimal example. If the editor
>>> is now able to open a file we have to go back step by step in order to
>>> find out what is the problem.
>>>
>>> Torsten
>>
>> Hi,
>> Is this patch to be applied in addition or in place of the previous one?
>> Thank you,
>> c.
>
> Torsten, with this patch the crash does not occur anymore!!!
> So what's the next step?
>
> Thanks,
> c.
Carlo, please apply this next patch in place of the previous one. It
re-adds the class octave_qscintilla which is derived from qscintilla in
order to get a custom context menu.

Torsten



qsci_2_6_mac_p06.diff (7K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Binary packages for 3.8

c.-2

On 28 Oct 2013, at 17:25, Torsten <[hidden email]> wrote:

> On 28.10.2013 12:50, c. wrote:
>>
>> On 28 Oct 2013, at 09:32, c. <[hidden email]> wrote:
>>
>>>
>>> On 28 Oct 2013, at 08:07, Torsten <[hidden email]> wrote:
>>>
>>>>
>>>> Attached another patch where all "extra" configurations of the
>>>> qscintilla editor is deleted. In principle a qscintilla editor is
>>>> created and the lexer is set, like in the minimal example. If the editor
>>>> is now able to open a file we have to go back step by step in order to
>>>> find out what is the problem.
>>>>
>>>> Torsten
>>>
>>> Hi,
>>> Is this patch to be applied in addition or in place of the previous one?
>>> Thank you,
>>> c.
>>
>> Torsten, with this patch the crash does not occur anymore!!!
>> So what's the next step?
>>
>> Thanks,
>> c.
>
> Carlo, please apply this next patch in place of the previous one. It
> re-adds the class octave_qscintilla which is derived from qscintilla in
> order to get a custom context menu.
>
> Torsten

Torsten,

With this patch opening an editor window works but, if I right-click in that window,
the gui crashes leaving a background octave process that hogs up 95% CPU time ...

The backtrace in the debugger is the following:

* thread #1: tid = 0x2cab3e, 0x0000000100057a0d liboctgui.0.dylib`octave_qscintilla::contextMenuEvent(QContextMenuEvent*) + 109, queue = 'com.apple.main-thread, stop reason = EXC_BAD_ACCESS (code=1, address=0x0)
    frame #0: 0x0000000100057a0d liboctgui.0.dylib`octave_qscintilla::contextMenuEvent(QContextMenuEvent*) + 109
    frame #1: 0x00000001014704db QtGui`QWidget::event(QEvent*) + 1739
    frame #2: 0x0000000101798ed7 QtGui`QFrame::event(QEvent*) + 183
    frame #3: 0x000000010181ba18 QtGui`QAbstractScrollArea::viewportEvent(QEvent*) + 120
    frame #4: 0x000000010181c1a5 QtGui`QAbstractScrollAreaFilter::eventFilter(QObject*, QEvent*) + 37
    frame #5: 0x0000000102228309 QtCore`QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) + 105
    frame #6: 0x00000001014231fa QtGui`QApplicationPrivate::notify_helper(QObject*, QEvent*) + 234
    frame #7: 0x000000010142534c QtGui`QApplication::notify(QObject*, QEvent*) + 3692
    frame #8: 0x0000000102228041 QtCore`QCoreApplication::notifyInternal(QObject*, QEvent*) + 113
    frame #9: 0x00000001014268fc QtGui`qt_sendSpontaneousEvent(QObject*, QEvent*) + 44
    frame #10: 0x00000001013d4864 QtGui`qt_mac_handleMouseEvent(NSEvent*, QEvent::Type, Qt::MouseButton, QWidget*, bool) + 1092
    frame #11: 0x00007fff8b120b81 AppKit`-[NSWindow sendEvent:] + 8504
    frame #12: 0x00000001013cc1de QtGui`-[QCocoaWindow sendEvent:] + 110
    frame #13: 0x00007fff8b11c644 AppKit`-[NSApplication sendEvent:] + 5761
    frame #14: 0x00000001013d0dae QtGui`-[QNSApplication sendEvent:] + 78
    frame #15: 0x00007fff8b03221a AppKit`-[NSApplication run] + 636
    frame #16: 0x00000001013d9963 QtGui`QEventDispatcherMac::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 1219
    frame #17: 0x00000001022255b5 QtCore`QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) + 501
    frame #18: 0x000000010222857e QtCore`QCoreApplication::exec() + 206
    frame #19: 0x0000000100067789 liboctgui.0.dylib`octave_start_gui(int, char**, bool) + 505
    frame #20: 0x00007fff81cb97e1 libdyld.dylib`start + 1

With the previous patch I had not tried to right-click, do you need me to try that?
c.




Reply | Threaded
Open this post in threaded view
|

Re: Binary packages for 3.8

Torsten
On 28.10.2013 18:12, c. wrote:

>
> On 28 Oct 2013, at 17:25, Torsten <[hidden email]> wrote:
>
>> On 28.10.2013 12:50, c. wrote:
>>>
>>> On 28 Oct 2013, at 09:32, c. <[hidden email]> wrote:
>>>
>>>>
>>>> On 28 Oct 2013, at 08:07, Torsten <[hidden email]> wrote:
>>>>
>>>>>
>>>>> Attached another patch where all "extra" configurations of the
>>>>> qscintilla editor is deleted. In principle a qscintilla editor is
>>>>> created and the lexer is set, like in the minimal example. If the editor
>>>>> is now able to open a file we have to go back step by step in order to
>>>>> find out what is the problem.
>>>>>
>>>>> Torsten
>>>>
>>>> Hi,
>>>> Is this patch to be applied in addition or in place of the previous one?
>>>> Thank you,
>>>> c.
>>>
>>> Torsten, with this patch the crash does not occur anymore!!!
>>> So what's the next step?
>>>
>>> Thanks,
>>> c.
>>
>> Carlo, please apply this next patch in place of the previous one. It
>> re-adds the class octave_qscintilla which is derived from qscintilla in
>> order to get a custom context menu.
>>
>> Torsten
>
> Torsten,
>
> With this patch opening an editor window works but, if I right-click in that window,
> the gui crashes leaving a background octave process that hogs up 95% CPU time ...
>
> The backtrace in the debugger is the following:
>
> * thread #1: tid = 0x2cab3e, 0x0000000100057a0d liboctgui.0.dylib`octave_qscintilla::contextMenuEvent(QContextMenuEvent*) + 109, queue = 'com.apple.main-thread, stop reason = EXC_BAD_ACCESS (code=1, address=0x0)
>     frame #0: 0x0000000100057a0d liboctgui.0.dylib`octave_qscintilla::contextMenuEvent(QContextMenuEvent*) + 109
>     frame #1: 0x00000001014704db QtGui`QWidget::event(QEvent*) + 1739
>     frame #2: 0x0000000101798ed7 QtGui`QFrame::event(QEvent*) + 183
>     frame #3: 0x000000010181ba18 QtGui`QAbstractScrollArea::viewportEvent(QEvent*) + 120
>     frame #4: 0x000000010181c1a5 QtGui`QAbstractScrollAreaFilter::eventFilter(QObject*, QEvent*) + 37
>     frame #5: 0x0000000102228309 QtCore`QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) + 105
>     frame #6: 0x00000001014231fa QtGui`QApplicationPrivate::notify_helper(QObject*, QEvent*) + 234
>     frame #7: 0x000000010142534c QtGui`QApplication::notify(QObject*, QEvent*) + 3692
>     frame #8: 0x0000000102228041 QtCore`QCoreApplication::notifyInternal(QObject*, QEvent*) + 113
>     frame #9: 0x00000001014268fc QtGui`qt_sendSpontaneousEvent(QObject*, QEvent*) + 44
>     frame #10: 0x00000001013d4864 QtGui`qt_mac_handleMouseEvent(NSEvent*, QEvent::Type, Qt::MouseButton, QWidget*, bool) + 1092
>     frame #11: 0x00007fff8b120b81 AppKit`-[NSWindow sendEvent:] + 8504
>     frame #12: 0x00000001013cc1de QtGui`-[QCocoaWindow sendEvent:] + 110
>     frame #13: 0x00007fff8b11c644 AppKit`-[NSApplication sendEvent:] + 5761
>     frame #14: 0x00000001013d0dae QtGui`-[QNSApplication sendEvent:] + 78
>     frame #15: 0x00007fff8b03221a AppKit`-[NSApplication run] + 636
>     frame #16: 0x00000001013d9963 QtGui`QEventDispatcherMac::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 1219
>     frame #17: 0x00000001022255b5 QtCore`QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) + 501
>     frame #18: 0x000000010222857e QtCore`QCoreApplication::exec() + 206
>     frame #19: 0x0000000100067789 liboctgui.0.dylib`octave_start_gui(int, char**, bool) + 505
>     frame #20: 0x00007fff81cb97e1 libdyld.dylib`start + 1
>
> With the previous patch I had not tried to right-click, do you need me to try that?

No, this is not necessary.
I am not sure how to preceed now: trying to find the cause for this new
crash or the old one?

Torsten

Reply | Threaded
Open this post in threaded view
|

Re: Binary packages for 3.8

fgnievinski
In reply to this post by c.-2
A preview binary for Windows too would be sweet...
-FGN.
Reply | Threaded
Open this post in threaded view
|

Re: Binary packages for 3.8

Torsten
In reply to this post by c.-2
On 28.10.2013 18:12, c. wrote:

> With this patch opening an editor window works but, if I right-click in that window,
> the gui crashes leaving a background octave process that hogs up 95% CPU time ...
>
> The backtrace in the debugger is the following:
>
> * thread #1: tid = 0x2cab3e, 0x0000000100057a0d liboctgui.0.dylib`octave_qscintilla::contextMenuEvent(QContextMenuEvent*) + 109, queue = 'com.apple.main-thread, stop reason = EXC_BAD_ACCESS (code=1, address=0x0)
>     frame #0: 0x0000000100057a0d liboctgui.0.dylib`octave_qscintilla::contextMenuEvent(QContextMenuEvent*) + 109
>     frame #1: 0x00000001014704db QtGui`QWidget::event(QEvent*) + 1739
>     frame #2: 0x0000000101798ed7 QtGui`QFrame::event(QEvent*) + 183
>     frame #3: 0x000000010181ba18 QtGui`QAbstractScrollArea::viewportEvent(QEvent*) + 120
>     frame #4: 0x000000010181c1a5 QtGui`QAbstractScrollAreaFilter::eventFilter(QObject*, QEvent*) + 37
>     frame #5: 0x0000000102228309 QtCore`QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) + 105
>     frame #6: 0x00000001014231fa QtGui`QApplicationPrivate::notify_helper(QObject*, QEvent*) + 234
>     frame #7: 0x000000010142534c QtGui`QApplication::notify(QObject*, QEvent*) + 3692
>     frame #8: 0x0000000102228041 QtCore`QCoreApplication::notifyInternal(QObject*, QEvent*) + 113
>     frame #9: 0x00000001014268fc QtGui`qt_sendSpontaneousEvent(QObject*, QEvent*) + 44
>     frame #10: 0x00000001013d4864 QtGui`qt_mac_handleMouseEvent(NSEvent*, QEvent::Type, Qt::MouseButton, QWidget*, bool) + 1092
>     frame #11: 0x00007fff8b120b81 AppKit`-[NSWindow sendEvent:] + 8504
>     frame #12: 0x00000001013cc1de QtGui`-[QCocoaWindow sendEvent:] + 110
>     frame #13: 0x00007fff8b11c644 AppKit`-[NSApplication sendEvent:] + 5761
>     frame #14: 0x00000001013d0dae QtGui`-[QNSApplication sendEvent:] + 78
>     frame #15: 0x00007fff8b03221a AppKit`-[NSApplication run] + 636
>     frame #16: 0x00000001013d9963 QtGui`QEventDispatcherMac::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 1219
>     frame #17: 0x00000001022255b5 QtCore`QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) + 501
>     frame #18: 0x000000010222857e QtCore`QCoreApplication::exec() + 206
>     frame #19: 0x0000000100067789 liboctgui.0.dylib`octave_start_gui(int, char**, bool) + 505
>     frame #20: 0x00007fff81cb97e1 libdyld.dylib`start + 1
>
> With the previous patch I had not tried to right-click, do you need me to try that?
> c.
Here is another patch disabling the custom context menu and enabling
other stuff for the editor.
Is there a way to get the (approximate) code line from the backtrace?
AFAIK the backtrace's last column is the actual address expressed by the
function name (start address) and an offset.

Torsten


qsci_2_6_mac_p07.diff (8K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Binary packages for 3.8

c.-2
Torsten,

Thanks for your new attempt!


On 29 Oct 2013, at 18:59, Torsten <[hidden email]> wrote:

> Here is another patch disabling the custom context menu and enabling
> other stuff for the editor.

With this patch I can open a new document in the editor and type into it.
There is no syntax highlighting,
If I open the editor styles pane in the preferences I see an Octave style
and I can edit the corresponding options, but when I save the preferences
the interface crashes (see attached log).

The interface also crashes if I try to save a file to disk (crash log also attached).

> Is there a way to get the (approximate) code line from the backtrace?
> AFAIK the backtrace's last column is the actual address expressed by the
> function name (start address) and an offset.

Maybe the crash reporter log provides more useful information?

> Torsten
c.



preferences.log (44K) Download Attachment
savefile.log (47K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Binary packages for 3.8

c.-2

On 29 Oct 2013, at 21:55, c. <[hidden email]> wrote:

> Torsten,
>
> Thanks for your new attempt!
>
>
> On 29 Oct 2013, at 18:59, Torsten <[hidden email]> wrote:
>
>> Here is another patch disabling the custom context menu and enabling
>> other stuff for the editor.
>
> With this patch I can open a new document in the editor and type into it.
> There is no syntax highlighting,
> If I open the editor styles pane in the preferences I see an Octave style
> and I can edit the corresponding options, but when I save the preferences
> the interface crashes (see attached log).
>
> The interface also crashes if I try to save a file to disk (crash log also attached).
>
>> Is there a way to get the (approximate) code line from the backtrace?
>> AFAIK the backtrace's last column is the actual address expressed by the
>> function name (start address) and an offset.
>
> Maybe the crash reporter log provides more useful information?
>
>> Torsten
> c.

Torsten,
Yust to be sure I tried again building Octave linked with qscintilla 2.4.
The crash does not happen there when saving either  editor files or preference settings.
c.
Reply | Threaded
Open this post in threaded view
|

Re: Binary packages for 3.8

Torsten
On 30.10.2013 08:20, c. wrote:

>
> On 29 Oct 2013, at 21:55, c. <[hidden email]> wrote:
>
>> Torsten,
>>
>> Thanks for your new attempt!
>>
>>
>> On 29 Oct 2013, at 18:59, Torsten <[hidden email]> wrote:
>>
>>> Here is another patch disabling the custom context menu and enabling
>>> other stuff for the editor.
>>
>> With this patch I can open a new document in the editor and type into it.
>> There is no syntax highlighting,
>> If I open the editor styles pane in the preferences I see an Octave style
>> and I can edit the corresponding options, but when I save the preferences
>> the interface crashes (see attached log).
>>
>> The interface also crashes if I try to save a file to disk (crash log also attached).
>>
>>> Is there a way to get the (approximate) code line from the backtrace?
>>> AFAIK the backtrace's last column is the actual address expressed by the
>>> function name (start address) and an offset.
>>
>> Maybe the crash reporter log provides more useful information?
>>
>>> Torsten
>> c.
>
> Torsten,
> Yust to be sure I tried again building Octave linked with qscintilla 2.4.
> The crash does not happen there when saving either  editor files or preference settings.
> c.
>
The crashes occur at the same point (setLexer ()) but obviously not the
first time this function is called. Here is the next patch applied
(replaces previous one). Does it change anything?
What context menu do you see when right clicking into an editor tab?

Torsten

qsci_2_6_mac_p08.diff (8K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Binary packages for 3.8

c.-2

On 30 Oct 2013, at 08:26, Torsten <[hidden email]> wrote:
>
>
> The crashes occur at the same point (setLexer ()) but obviously not the
> first time this function is called. Here is the next patch applied
> (replaces previous one). Does it change anything?

Saving a file still causes a crash, log is attached.

> What context menu do you see when right clicking into an editor tab?

a picture of the context menu is also attached.

> Torsten

Thanks,
c.


Screen Shot 2013-10-30 at 09.01.26.png (65K) Download Attachment
savefile.log (47K) Download Attachment
12345