-
-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Master branch: Segmentation fault at startup #1329
Comments
@psilhavy, is this from source or from a repository? (if a repo, which one?) What OS? We have received word that KXStudio may be packaging an unstable release. Any information you can provide will be of assistance to properly categorize this bug. |
from repository , master branch IIRC cloned today. linux 3.17.3 glibc-2.20 gcc 4.9.2:/usr/src/lmms# git statusOn branch masterYour branch is up-to-date with 'origin/master'. -- Petr Silhavy |
Ok, master is unstable and the versioning in the title is misleading in the bug report as it conflicts with our soon to be released stable. I'll fix the title and change the milestone. |
Just for fun I cloned stable-1.1 and the crash is nearby the same
|
On 11/20/2014 10:45 AM, psilhavy wrote:
Looks like something to do with ALSA... try another backend maybe |
cmake -DWANT_ALSA=OFF -DWANT_PORTAUDIO=OFF -DWANT_PULSEAUDIO=OFF .. |
Now I understand why some issues is connected to 10+ other issues. |
For those that may be confused... Stian's comment is in response to the Unfortunately, there's no easy way to fix it retroactively. We just need to be more careful to "preview" before submitting a new bug report. In this case, the stack trace should have been in a code box, or moved to an external gist file. |
On version 1.0.99 for Mac OS X, I get this:
|
@soycamo which distro? We currently build on Mavericks and test on Mavericks and Yosemite. |
Lion, which is 10.7 as seen above. I don't own a machine that will run Mavericks, currently. |
How old is this machine? @tres would him bumping to 10.8 if its possible On Tue, Dec 16, 2014 at 6:21 AM, Cameron notifications@github.com wrote:
Jonathan Aquilina |
Was this issue fixed? Since #1270 looks like a duplicate and was closed we may be able to close this one as well. |
@badosu it appears that way, but the fix in 1270 was for Apple only. 👍 |
Since version 1.1.0 ( branch stable-1.1, last commit 62df768) bug disappears . |
👍 |
linux 3.17.3 glibc-2.20 gcc 4.9.2
The text was updated successfully, but these errors were encountered: