octave-maintainers
[Top][All Lists]
Advanced

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

Re: gplot.txt


From: Ben Abbott
Subject: Re: gplot.txt
Date: Thu, 03 Mar 2016 06:48:09 -0500

> On Mar 3, 2016, at 02:00, Daniel J Sebald <address@hidden> wrote:
> 
> On 03/02/2016 09:07 PM, Ben Abbott wrote:
>>> On Mar 2, 2016, at 9:41 PM, Daniel J Sebald<address@hidden>  wrote:
>>> 
>>> On 03/02/2016 08:03 PM, Ben Abbott wrote:
>>>>> On Mar 2, 2016, at 3:02 PM, Daniel J Sebald<address@hidden>   wrote:
>>> [snip]
>>>>> Or, there is a more elegant Mercurial feature that will display the log 
>>>>> history for just a particular file.  In this case, try the Sparse.cc file:
>>>>> 
>>>>> http://hg.savannah.gnu.org/hgweb/octave/log/40de9f8f23a6/liboctave/array/Sparse.cc
>>>>> 
>>>>> From the list one revision I would think to look at is this changeset:
>>>>> 
>>>>> http://hg.savannah.gnu.org/hgweb/octave/rev/af8118df8292
>>>> 
>>>> I’ve just reverted the changeset …
>>>> 
>>>>    hg revert —all -r af8118df8292
>>>> 
>>>> … and the problem persists.
>>> 
>>> That revert may include the changeset itself.  You might need to revert to 
>>> one of the changeset's parents or grandparents depending on how far back 
>>> the related changes go.  Follow the link to the parent in the link listed 
>>> above.
>>> 
>>> Dan
>> 
>> Ok. Meanwhile I reverted dd6345fd8a97 ...
>> 
>>     hg revert --all -r dd6345fd8a97
>> 
>> … the build still encounters seg-fauls, but speye() works.
> 
> Ben,
> 
> On the more recent versions that fail speye(10), does
> 
> speye(10);
> 
> with the semicolon seg-fault?
> 
> Dan

Yes 


reply via email to

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