octave-maintainers
[Top][All Lists]
Advanced

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

Re: error building GUI on Mac OS-X 10.6.8


From: Michael Goffioul
Subject: Re: error building GUI on Mac OS-X 10.6.8
Date: Sun, 12 Aug 2012 09:54:49 +0100

On Sun, Aug 12, 2012 at 12:00 AM, Ben Abbott <address@hidden> wrote:
On Aug 11, 2012, at 6:28 PM, Ben Abbott wrote:

> On Aug 11, 2012, at 6:01 PM, John W. Eaton wrote:
>
>> On 11-Aug-2012, Ben Abbott wrote:
>>
>> | With that change ...
>> |
>> | $ ./run-octave
>> | panic: Segmentation fault: 11 -- stopping myself...
>> | attempting to save variables to `octave-workspace'...
>>
>> I have no clue.  What does gdb tell you about where it is crashing?
>>
>> jwe
>
> Nothing useful.
>
> panic: Segmentation fault: 11 -- stopping myself...
> attempting to save variables to `octave-workspace'...
> save to `octave-workspace' complete
>
> Program exited normally.
> (gdb) bt
> No stack.
> (gdb)
>
> I saw this earlier, but it mysteriously corrected itself when I deleted a moc_xxxx.cc file and ran make again. I'll make a fresh start with a "make clean; make" and see what happens.  If the problem persists I'll try deleting the moc file and see if that makes any difference.
>
> Ben

After "make clean" I had to remove the references to the "thread" subdirectory again.  Once the build complete, I still see the crash.  Previously that disappeared after I deleted gui/qterminal/libqterminal/moc_QTerminal.cpp and ran "make" again.  However, as was the case the first time, the new moc_QTerminal.cpp did not contain the "thread" subdirectory reference.


Sorry, but I'm confused by what you're actually doing. First, may I suggest that you build out of the source tree; so a simple "rm -rf <build_dir>" is enough to restart from scratch and avoid any leftovers. Second, I don't get how the moc file could be different, if yo do something like:

make
rm gui/src/qterminal/libqterminal/moc_QTerminal.cpp
make

Michael.


reply via email to

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