The package octave-3.6.3-1 as been flagged as broken

[pack...@chakra-project.org]

Package details:
http://chakra-project.org/packages/index.php?act=show&subdir=platform/x86_64&sortby=date&file=octave-3.6.3-1-x86_64.pkg.tar.xz


---
The package octave-3.6.3-1 as been flagged as broken
by: yngve.l...@gmail.com

Additional information:
Hi,

This package is segfaulting on my laptop (but working just fine on my
desktop). Below you find the information from my laptop:

$ pacman -Qo `which octave`
/usr/bin/octave is owned by octave 3.6.3-1
$ octave --quiet
panic: Segmentation fault -- stopping myself...
attempting to save variables to `octave-core''...
save to `octave-core'' complete
zsh: segmentation fault (core dumped) octave --quiet
$ uname -a
Linux yngve-chakra-mbp 3.6.6-1-CHAKRA #1 SMP PREEMPT Sun Nov 18
01:49:19 UTC 2012 x86_64 GNU/Linux
$ lscpu
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 2
On-line CPU(s) list: 0,1
Thread(s) per core: 1
Core(s) per socket: 2
Socket(s): 1
NUMA node(s): 1
Vendor ID: GenuineIntel
CPU family: 6
Model: 23
Stepping: 6
CPU MHz: 1596.000
BogoMIPS: 4777.60
Virtualization: VT-x
L1d cache: 32K
L1i cache: 32K
L2 cache: 3072K
NUMA node0 CPU(s): 0,1

My machine is a Macbook Pro 5. gen. Let me know if you need more info
to track this down.

Funny enough, if I start it in gdb it starts without problems.. Not
sure how that can be but it is.

Cheers,
Yngve (eothred)

[Yngve Inntjore Levinsen]

I tried to build the package myself on my laptop but did not succeed. I
thought then that perhaps it was due to some of the optimizations in
/etc/makepkg.conf, so I commented out LDFLAGS, CFLAGS, and CXXFLAGS in
that file. No success. Output is found below. Looks like this octave
version is not playing nicely with my laptop at all! :(

Cheers,
Yngve

$ makepkg
...
if /bin/sh
/home/ylevinse/chakra-packages/octave/src/octave-3.6.3/build-aux/missing
--run makeinfo -I . \
-o octave.info octave.texi; \
then \
rc=0; \
CDPATH="${ZSH_VERSION+.}:" && cd .; \
else \
rc=$?; \
CDPATH="${ZSH_VERSION+.}:" && cd . && \
$restore $backupdir/* `echo "./octave.info" | sed 's|[^/]*$||'`; \
fi; \
rm -rf $backupdir; exit $rc
../../run-octave -f -q -H ./mk_doc_cache.m doc-cache
../../scripts/DOCSTRINGS ../../src/DOCSTRINGS || { rm -f doc-cache; exit
1; }

panic: Segmentation fault -- stopping myself...
attempting to save variables to `octave-core'...
save to `octave-core' complete

/bin/sh: line 1: 24320 Segmentation fault (core dumped)
../../run-octave -f -q -H ./mk_doc_cache.m doc-cache
../../scripts/DOCSTRINGS ../../src/DOCSTRINGS
make[3]: *** [doc-cache] Error 1
make[3]: Leaving directory
`/home/ylevinse/chakra-packages/octave/src/octave-3.6.3/doc/interpreter'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory
`/home/ylevinse/chakra-packages/octave/src/octave-3.6.3/doc'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory
`/home/ylevinse/chakra-packages/octave/src/octave-3.6.3'
make: *** [all] Error 2
==> ERROR: A failure occurred in build().
Aborting...

[abveritas]

Segmentation fault is usually due to running out of resources (RAM mostly).  Could that be your issue too when running octave on that system?  Checked RAM?  No issues with the CPU?  

Not possible to call a package broken, if just one system is effected, need confirmation it is octave, not your system/setup.

[Daniele]

Actually, segmentation fault is actually not directly related to memory usage, but rather to incorrect accesses to the memory made by some software.

2013/1/11 abveritas <verit...@gmail.com>

[Yngve Inntjore Levinsen]

Sorry, I guess perhaps I should have made a thread on the forum instead.

I have 4 GB of ram on this machine so I would be surprised, and this is not a problem I have  experienced with other programs as far as I can remember. It is crashing immediately on startup, so I don't think it has time to take up that much memory. Finally it was somehow working when I ran it inside GDB, where you normally use more memory than usual... So I think I answer no, there should still be free memory left. I rather think it is something along the lines of what Daniele suggests. I am not familiar using memory debugging tools, what should I try? valgrind?

As for issues with CPU being partly broken/old or something like that, I simply don't know, and don't know how to figure out. Feel free to suggest tools I can use to investigate.

I did maintain the octave30 package in the past, and I remember then that one of the flags in makepkg.conf was causing problems (been a while so I don't remember which). I do have one of these packages still available so I can use that one on my laptop for the time being (but it is suboptimal, a lot has changed in octave since 3.0).

Cheers,
Yngve

[abveritas]

Sorry, I thought the segmentation fault output was on compiling, not running.  The output you posted, with error 1 and 2, did not look like outputs from running the app.

[Yngve Inntjore Levinsen]

No you were right, that was during compiling (though I think that looks like a test of the binary?). It is segfaulting both when I try to run the installed package (shown in first mail), and when I try to compile it (which was shown in previous mail).

I moved the discussion to a forum thread instead: http://chakra-project.org/bbs/viewtopic.php?pid=65004

Sorry for the inconvenience! Feel free to unflag this package (at least until the problem is confirmed by anyone else).

Cheers,
Yngve