Re: dev (gui) build does not run on MacOSX

[Torsten]

On 18.08.2013 22:26, Ben Abbott wrote:
> On Aug 18, 2013, at 10:03 AM, Ben Abbott wrote:
> 
>> On Aug 18, 2013, at 9:05 AM, Torsten wrote:
>>
>>> On 18.08.2013 14:36, Ben Abbott wrote:
>>>>
>>>> On Aug 18, 2013, at 4:54 AM, Kirill Fuior wrote:
>>>>
>>>>> Hi all,
>>>>>
>>>>> I'm trying to build and run octave from dev sources (according to 
>>>>> etc/HACKING and wiki instructions), but I face a problem -- after 
>>>>> successful build it simply does not start.
>>>>>
>>>>> My actions step-by-step:
>>>>> * install build-dep octave and bison (it isn't included)
>>>>> * clone hg repository
>>>>> * bootstrap, configure (without custom options) and make.
>>>>> make is passed without errors (with only some compile warnings)
>>>>> * then I try ./run-octave or .build/src/octave script and it simply does 
>>>>> nothing, without any output.
>>>>> Only once it showed me wizard "It seems you are running octave gui first 
>>>>> time..." with only 1 active button "finish". When I click it, wizard has 
>>>>> been closed and again -- nothing else happen.
>>>>>
>>>>> But src/octave-cli runs octave in terminal.
>>>>> Also, if I install latest (3.6.4) octave from the repository, it works.
>>>>>
>>>>> So it seems problem is in gui.
>>>>>
>>>>> I use Kubuntu 13.04 with latest recommended updates (kde 4.10.5, Qt 
>>>>> 4.8.4).
>>>>>
>>>>> Note:
>>>>> It worked few month ago, on Kubuntu 12.10.
>>>>>
>>>>> I haven't found this issue neither in the known issues list, nor on bug 
>>>>> tracker.
>>>>> I haven't report this as a bug yet, because it may be that I'm doing 
>>>>> something wrong (?).
>>>>>
>>>>> I really don't know what to do.
>>>>> Could anyone help me with this?
>>>>>
>>>>> Thanks in advance,
>>>>> Kirill Fuior.
>>>>
>>>> I may be able to confirm a problem.
>>>>
>>>> I haven't tried the gui in a while.  Today with "hg id" -> "1c21f264d26f+ 
>>>> tip @", Octave exists with "Abort trap: 6".  The log from MacOSX is 
>>>> attached.
>>>>
>>>> From gdb, the gui intially runs and allows me to enter a command.  After 
>>>> entering "plot (rand (3))" ...
>>>>
>>>> Program received signal EXC_BAD_ACCESS, Could not access memory.
>>>> Reason: KERN_INVALID_ADDRESS at address: 0x0000000000000218
>>>> 0x00007fff89926b06 in glDrawBuffer ()
>>>> (gdb) bt
>>>> #0  0x00007fff89926b06 in glDrawBuffer ()
>>>> #1  0x0000000116888164 in Fl_Gl_Window::flush ()
>>>> #2  0x0000000116ccf1e5 in -[FLView drawRect:] ()
>>>> #3  0x00007fff8d4602ce in -[NSView _drawRect:clip:] ()
>>>> #4  0x00007fff8d48d49b in -[NSView 
>>>> _recursiveDisplayAllDirtyWithLockFocus:visRect:] ()
>>>> #5  0x00007fff8d48d8c7 in -[NSView 
>>>> _recursiveDisplayAllDirtyWithLockFocus:visRect:] ()
>>>> #6  0x00007fff8d45d8a9 in -[NSView 
>>>> _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topView:]
>>>>  ()
>>>> #7  0x00007fff8d45cda3 in -[NSThemeFrame 
>>>> _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topView:]
>>>>  ()
>>>> #8  0x00007fff8d4581bb in -[NSView 
>>>> _displayRectIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:] ()
>>>> #9  0x00007fff8d450c35 in -[NSView displayIfNeeded] ()
>>>> #10 0x00007fff8d450375 in 
>>>> _handleWindowNeedsDisplayOrLayoutOrUpdateConstraints ()
>>>> #11 0x00007fff85e2a8e7 in 
>>>> __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ ()
>>>> #12 0x00007fff85e2a846 in __CFRunLoopDoObservers ()
>>>> #13 0x00007fff85dffaf9 in __CFRunLoopRun ()
>>>> #14 0x00007fff85dff486 in CFRunLoopRunSpecific ()
>>>> #15 0x00007fff8a9cd2bf in RunCurrentEventLoopInMode ()
>>>> #16 0x00007fff8a9d44bf in ReceiveNextEventCommon ()
>>>> #17 0x00007fff8a9d43fa in BlockUntilNextEventMatchingListInMode ()
>>>> #18 0x00007fff8d414779 in _DPSNextEvent ()
>>>> #19 0x00007fff8d41407d in -[NSApplication 
>>>> nextEventMatchingMask:untilDate:inMode:dequeue:] ()
>>>> #20 0x00007fff8d4109b9 in -[NSApplication run] ()
>>>> #21 0x0000000103e16a6f in QEventDispatcherMac::processEvents ()
>>>> #22 0x0000000104c906f8 in QEventLoop::exec ()
>>>> #23 0x0000000104c93a23 in QCoreApplication::exec ()
>>>> #24 0x000000010008c009 in octave_start_gui ()
>>>> #25 0x000000010000aa4f in main ()
>>>>
>>>> Ben
>>>
>>> Can you say how long ago the gui was working correctly?
>>>
>>> Torsten
>>
>> I did some testing.  If I run gnuplot then there is no problem.
>>
>> However, Octave crashes immediately when an FLTK plot is created.  The 
>> position on the screen where the window would show up becomes solid white, 
>> but nothing is rendered.
>>
>> Ben
> 
> I've changed the subject (just in case the Kubuntu problem is unrelated to 
> the MacOSX one).
> 
> I reverted the last GUI related change (?)
> 
>       hg revert -a -r aa09b746fa16
> 
> When I tried a plot, the plot renders, but then Octave hangs (some 
> improvement, but still not working).  Next I reverted the next gui related 
> changeset (?).
> 
>       hg revert -a -r e993fa124b46
> 
> Same behavior as for "-r aa09b746fa16"
> 
> Next ...
> 
>       hg revert -a -r 4407606d0939
> 
> Same behavior, so ....
> 
>       hg revert -a -r 36fd98b9ce48
> 
> And still the same behavior.  I seldom try fltk from the gui, so this may not 
> have been working for a long time.  I'll keep backup further and report back 
> later.
> 
> Ben
> 

aa09b746fa16 is related to the teminal window in Windows. I am surprised
that this has influence on fltk rendering on MacOSX.

Torsten