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

SIGSEGV (Address boundary error) on Mac OS X #33

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

SIGSEGV (Address boundary error) on Mac OS X #33

GoogleCodeExporter opened this issue Mar 15, 2015 · 3 comments

Comments

@GoogleCodeExporter
Copy link

Hi. I installed gource on Mac OS X 10.6 via MacPorts and tried
to visualize an SVN repository with the steps given in the gource Wiki.

Sadly I just get a small message saying that gource terminated with SIGSEGV. 

fish: Job 1, 'gource --log-format custom my-project-gource.log' terminated by 
signal SIGSEGV 
(Address boundary error)


What steps will reproduce the problem?
1. convert xml-log to gource log format
2. startup gource with the parameters given in the Wiki
3. bang


What version of the product are you using? On what operating system?
Gource v0.23 / Mac OS X 10.6.2

Feel free to contact me, if I should give more information.
(I've attached the trace that Mac OS displayed)


Original issue reported on code.google.com by unmerk...@googlemail.com on 14 Jan 2010 at 9:13

Attachments:

@GoogleCodeExporter
Copy link
Author

Ok thanks for the report.

Original comment by acaudw...@gmail.com on 14 Jan 2010 at 10:05

@GoogleCodeExporter
Copy link
Author

Hi. I've just had a go installing Gource from Macports on a Macbook with 10.6.2 
(Core
2 Duo, Intel GMA 950 video card) and didn't have any issues.

You could maybe try uninstalling your ports and then try installing gource from
macports again, incase you have some broken ports?

Original comment by acaudw...@gmail.com on 16 Jan 2010 at 8:51

@GoogleCodeExporter
Copy link
Author

http://code.google.com/p/gource/issues/detail?id=51#makechanges

A user with a very similar report was able to get Gource working by building it 
from
source, so it seems like it might be a problem with how it's built from 
Macports.

Original comment by acaudw...@gmail.com on 9 Mar 2010 at 4:33

  • Changed state: Done

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

1 participant