[MacPorts] #41238: Octave parcellfun panics
MacPorts
noreply at macports.org
Wed Nov 6 15:19:45 PST 2013
#41238: Octave parcellfun panics
---------------------------+-------------------------
Reporter: tom_olin@… | Owner: michaelld@…
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version: 2.2.1
Resolution: | Keywords:
Port: octave-devel |
---------------------------+-------------------------
Changes (by macsforever2000@…):
* owner: macports-tickets@… => michaelld@…
* keywords: parcellfun, malloc =>
Old description:
> I updated MacPorts yesterday, and now the parcellfun function from the
> general package is unusable. Here's a simple test file:
>
> function foo()
> parcellfun(2, @myfunc, {pi; e});
> end
> function myfunc(val)
> end
>
> When I run it, I get:
>
> parcellfun: 0/2 jobs doneoctave(17310,0x7fff7c400180) malloc: *** error
> for object 0x108b93220: pointer being freed was not allocated
> *** set a breakpoint in malloc_error_break to debug
> panic: Abort trap: 6 -- stopping myself...
> attempting to save variables to 'octave-core'...
> save to 'octave-core' complete
> Abort trap: 6
>
> I've found mention of this error going back some months on various
> forums, but I've found no clear explanation nor solution/workaround. It
> worked fine since I last updated MacPorts within the last week or two.
>
> octave-devel @3.6.4_9+atlas+docs+fltk+gcc47+x11 (active)
New description:
I updated MacPorts yesterday, and now the parcellfun function from the
general package is unusable. Here's a simple test file:
{{{
function foo()
parcellfun(2, @myfunc, {pi; e});
end
function myfunc(val)
end
}}}
When I run it, I get:
{{{
parcellfun: 0/2 jobs doneoctave(17310,0x7fff7c400180) malloc: *** error
for object 0x108b93220: pointer being freed was not allocated
*** set a breakpoint in malloc_error_break to debug
panic: Abort trap: 6 -- stopping myself...
attempting to save variables to 'octave-core'...
save to 'octave-core' complete
Abort trap: 6
}}}
I've found mention of this error going back some months on various forums,
but I've found no clear explanation nor solution/workaround. It worked
fine since I last updated MacPorts within the last week or two.
{{{
octave-devel @3.6.4_9+atlas+docs+fltk+gcc47+x11 (active)
}}}
--
Comment:
In the future, please use WikiFormatting and Cc the port maintainers (port
info --maintainers octave-devel).
--
Ticket URL: <https://trac.macports.org/ticket/41238#comment:1>
MacPorts <http://www.macports.org/>
Ports system for OS X
More information about the macports-tickets
mailing list