Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Broken, SIGSEGV #161

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

Closed
williammortl opened this issue Feb 8, 2022 · 3 comments · Fixed by #162
Closed

Broken, SIGSEGV #161

williammortl opened this issue Feb 8, 2022 · 3 comments · Fixed by #162

Comments

@williammortl
Copy link

The current repo is broken...

after "go build"

wmortl@Discovery:/mnt/e/Code/gpython$ ./gpython
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x5986b1]

goroutine 1 [running]:
main.main()
        /mnt/e/Code/gpython/main.go:49 +0x171

Seems to be context related from line 49

sbinet added a commit to sbinet-gonum/gpython that referenced this issue Feb 8, 2022
@sbinet
Copy link
Member

sbinet commented Feb 8, 2022

thanls for the report.
this should be fixed w/ #162.

we ought to do a better job at testing the gpython binary...

@williammortl
Copy link
Author

@sbinet no worries! I'm going to be around here a lot, as I am packaging gpython into a plugin as part of a new type of compute cluster that I am creating for my PhD dissertation!

@sbinet
Copy link
Member

sbinet commented Feb 8, 2022

sounds fun :)
(and welcome)

@sbinet sbinet closed this as completed in c9f2d8b Feb 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants