Re: Bus-error

[Jaroslav Hajek]

On Thu, Sep 30, 2010 at 9:44 PM, John W. Eaton <address@hidden> wrote:
> On 30-Sep-2010, bpabbott wrote:
>
> | With that change I still have a problem.
> |
> | ../../run-octave -f -q -H ./mk_doc_cache.m doc-cache 
> ../../scripts/DOCSTRINGS
> | ../../src/DOCSTRINGS || { rm -f doc-cache; exit 1; }
> | octave(54771,0xa07db500) malloc: *** error for object 0xe48fb8: pointer 
> being
> | freed was not allocated
> | *** set a breakpoint in malloc_error_break to debug
> | error: octave_map::setfield: internal error
> | error: octave_map::setfield: internal error
> | octave(54771,0xa07db500) malloc: *** error for object 0xe48fb8: pointer 
> being
> | freed was not allocated
> | *** set a breakpoint in malloc_error_break to debug
> |
> | panic: Segmentation fault -- stopping myself...
> | attempting to save variables to `octave-core'...
> | panic: attempted clean up apparently failed -- aborting...
> | /bin/sh: line 1: 54771 Abort trap              ../../run-octave -f -q -H ./
> | mk_doc_cache.m doc-cache ../../scripts/DOCSTRINGS ../../src/DOCSTRINGS
> | make[3]: *** [doc-cache] Error 1
> | make[2]: *** [all-recursive] Error 1
> | make[1]: *** [all-recursive] Error 1
> | make: *** [all] Error 2
>
> This does not fail for me, and running the mk_doc_cache script with
> Octave under valgrind doesn't show anything unusual, so I have no
> clue where to look.  Unless Jaroslav sees what the problem is, I guess
> the next step would be to bisect and find which of the recent changes
> related to Octave_map -> octave_(scalar_|)map caused the problem to
> appear for you.  That might point us in the right direction.
>
> jwe
>

I suspect this is another SID. Ben's Mac OS is apparently good at
catching those :)
Ben, please pull this patch and try again:
http://hg.savannah.gnu.org/hgweb/octave/rev/b0eec300d3fc

hth
-- 
RNDr. Jaroslav Hajek, PhD
computing expert & GNU Octave developer
Aeronautical Research and Test Institute (VZLU)
Prague, Czech Republic
url: www.highegg.matfyz.cz