Hi David,
On 07/01/18 14:22, David Kastrup wrote:
> Since a crash is a pretty bad kind of problem, wouldn't that warrant a
> backport?
>
Backports are not for bug fixes. What is needed is a Stable Release Update:
https://wiki.ubuntu.com/StableReleaseUpdates
It is on my to do list, but I don't ha
Since a crash is a pretty bad kind of problem, wouldn't that warrant a
backport?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1708027
Title:
aeolus crashed with SIGSEGV in memset()
To manage notif
Fons's fix was included in v0.9.5 (I only checked that version) which is
now in the development release (Bionic).
** Changed in: aeolus (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
>From the Linux audio users list:
From: Fons Adriaensen
Subject: Re: [LAU] Trying to start Aeous gives me seg faults
Newsgroups: gmane.linux.audio.users
To: linux-audio-user-cunTk1MwBs/cejeg2xfrv2d2fqjk+...@public.gmane.org
Date: Mon, 18 Sep 2017 16:39:21 + (31 minutes, 45 seconds ago)
On Mo
#6 also would be consistent with me seeing this problem only after
converting my system to 64 bits: it is perfectly conceivable that this
would increase the stack size requirements.
When I started computing, 128kB would have been double the total address
space (let alone local variables). Sigh.
