Skip to content
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

Crash on OSX 10.5.8 #3

Closed
GoogleCodeExporter opened this issue Jul 15, 2015 · 3 comments
Closed

Crash on OSX 10.5.8 #3

GoogleCodeExporter opened this issue Jul 15, 2015 · 3 comments

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
1. Just open a library with File -> Open...

What is the expected output? What do you see instead?

I presume I should see the main app window. Instead, I get a message from the 
Operating System (OSX 10.5.8) saying that the app has crashed


What version of the product are you using? On what operating system?

version 1.0.0, on Mac OSX 10.5.8

Please provide any additional information below.

It looks like it is a segmentation fault. Attached you may find the crash 
report text from the system.

Original issue reported on code.google.com by ludola...@gmail.com on 18 Jun 2012 at 2:20

Attachments:

@GoogleCodeExporter
Copy link
Author

Crashed here too. Application opens OK, but using File/Open makes it crash. My 
symptoms are as posted in the comment before mine.

Original comment by lubodia...@gmail.com on 15 Sep 2013 at 1:03

Attachments:

kwin added a commit that referenced this issue Nov 20, 2016
Overhaul of the app + icon - boost and more
This fixes #2 #3 #4 and #9
@kwin kwin added this to the 1.1 milestone Nov 20, 2016
@kwin
Copy link
Owner

kwin commented Nov 20, 2016

The first crash is probably be resolved with 972fcb3 the 2nd one is resolved with the same commit as well, as boost process is no longer being used for demangling the function names.

@kwin kwin closed this as completed Nov 20, 2016
@barracuda156
Copy link

@kwin A switch to 10.7 target and C++11 (which is not supported by Xcode of 10.5) cannot possibly fix the app on 10.5.8, it will just break the build.

(As such, C++11 and later standards can be supported on 10.5 without issues, but not via Xcode build system.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants