[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #38840] glibc malloc error
From: |
John W. Eaton |
Subject: |
[Octave-bug-tracker] [bug #38840] glibc malloc error |
Date: |
Sun, 28 Apr 2013 01:33:17 +0000 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:10.0.12) Gecko/20100101 Firefox/10.0.12 Iceweasel/10.0.12 |
Update of bug #38840 (project octave):
Status: None => Fixed
Open/Closed: Open => Closed
_______________________________________________________
Follow-up Comment #1:
The octave-core file is not a core dump file. It contains the top-level
Octave workspace in a format that Octave can load so that you might recover
work that you've done before the crash.
I can duplicate the crash with Octave 3.6.4, but I doubt that there will be
another 3.6.x release.
With the current sources I see:
octave-cli:1> function = f(a)
parse error:
syntax error
>>> function = f(a)
^
octave-cli:1> function f(a)
> printf("%d", a)
> endfunction
octave-cli:2> f(42)
error: 'f' undefined near line 1 column 1
So the initial syntax error causes some trouble and apparently makes it
impossible to define a function at the command line. Hmm.
I checked in the following change.
http://hg.savannah.gnu.org/hgweb/octave/rev/b678d2d10e53
This patch will not apply to the stable branch (3.6.x) so if you want the fix,
you'll need to build the default development branch or wait for the next
release.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?38840>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/