[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #57182] [octave forge] (signal) decimate cause
|
From: |
Mike Miller |
|
Subject: |
[Octave-bug-tracker] [bug #57182] [octave forge] (signal) decimate causes octave to be killed |
|
Date: |
Wed, 6 Nov 2019 17:05:41 -0500 (EST) |
|
User-agent: |
Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/78.0.3904.87 Safari/537.36 |
Update of bug #57182 (project octave):
Status: None => Need Info
Summary: signal function decimate causes octave to be killed
=> [octave forge] (signal) decimate causes octave to be killed
_______________________________________________________
Follow-up Comment #1:
This example works for me on my system
y = rand (1, 1e8);
d = decimate (y, 8, 'fir');
Is there any example that reproduces this error for you on a system that is
not a chromebook?
What is the exact error? Is Octave killed by the operating system, perhaps
because of a memory usage limitation? Or does Octave exit with an error or a
fatal signal? Are you able to share a call stack trace at the location where
Octave is killed?
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?57182>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/