octave-bug-tracker
[Top][All Lists]
Advanced

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

[Octave-bug-tracker] [bug #43710] io-2.2.5 causes panic


From: Philip Nienhuis
Subject: [Octave-bug-tracker] [bug #43710] io-2.2.5 causes panic
Date: Thu, 27 Nov 2014 17:08:52 +0000
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:33.0) Gecko/20100101 Firefox/33.0 SeaMonkey/2.30

Follow-up Comment #3, bug #43710 (project octave):

I wouldn't know, sorry.

io-2.2.5 uses two compiled .oct files to manipulate cell addresses, "num2col"
and "col2num". My guess is those functions suffer from the same pickyness of
your compiler.

Try:

calccelladdress (1, 2)

and see what happens. You can even try to step through it (debug mode) by
setting a breakpoint in L. 41 (click to the left of the line number in the
Octave editor) and then click the leftmost blue button or press <F10>).
If it crashes in L. 50 it is indeed the binary modules that seem to have been
miscompiled.

BTW 'pickyness": on my boxes (Linux Mageia 4 & Windows 7 Professional &
Enterprise) it works fine. So while it may be that your compiler on OSX is
essentially correct, I see no reason for it to be so very alarmed.
Does "mkoctfile" (the function that is invoked by pkg.m command to compile the
binary modules) pick up the right C++ compiler version? Maybe there's a
mismatch between C++ compilers on your box (i.e., the one Octave was built
with and the one installed on your box). 
Mind you, I know virtually nothing about developing on OSX.


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?43710>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/




reply via email to

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