octave-maintainers
[Top][All Lists]
Advanced

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

Re: pkg.m is busted, gen_doc_cache sematics changed


From: Jason Riedy
Subject: Re: pkg.m is busted, gen_doc_cache sematics changed
Date: Wed, 25 Feb 2009 14:40:45 -0500
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.90 (gnu/linux)

And John W. Eaton writes:
> Using a copy of Octave built from the latest sources I don't see any
> error with mlock called from pkg.  What is the error that you see?

The fun part is that it isn't the mlock in pkg. Commenting that call
out doesn't change anything, and I haven't had time to
single-step through everything...

The text, from an empty ~/octave:
> octave:1> pkg install osdbi-0.0.3.tar.gz
> warning: creating installation directory /home/ejr/octave
> warning: load_path: 
> /home/ejr/octave/osdbi-0.0.3/x86_64-unknown-linux-gnu-api-v34+: No such file 
> or directory
> Invalid call to mlock.  Correct usage is:
> 
>  -- Built-in Function:  mlock ()
> 
> 
> Additional help for built-in functions and operators is
> available in the on-line version of the manual.  Use the command
> `doc <topic>' to search the manual index.
> 
> Help and information about Octave is also available on the WWW
> at http://www.octave.org and via the address@hidden
> mailing list.
> error: called from `print_usage' in file 
> /home/ejr/.local/x86_64-unknown-linux-gnu/stow/octave-hg/share/octave/3.1.52+/m/help/print_usage.m
>  near line 64, column 3
> error: called from:
> error:   
> /home/ejr/.local/x86_64-unknown-linux-gnu/stow/octave-hg/share/octave/3.1.52+/m/pkg/pkg.m
>  at line 756, column 5
> error:   
> /home/ejr/.local/x86_64-unknown-linux-gnu/stow/octave-hg/share/octave/3.1.52+/m/pkg/pkg.m
>  at line 287, column 7

The second run works just fine, although it too warns that
/home/ejr/octave/osdbi-0.0.3/x86_64-unknown-linux-gnu-api-v34+
doesn't exist. So the erroneous mlock must be called before it's
created.

The first pkg load osdbi also yells about mlock (in a fresh run
of Octave), while the second works.

So I don't think it's a pkg issue.

I'm also running into a segfault on quit with some combination of
atexit, global, and a type defined in a DLD... Haven't narrowed
it down enough yet to guarantee it's not my fault, but it *may*
be related if mlock is having issues.

Jason


reply via email to

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