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

Segmentation fault on exit on Linux and osx #284

Closed
marshmellow42 opened this issue Apr 21, 2017 · 4 comments · Fixed by #302
Closed

Segmentation fault on exit on Linux and osx #284

marshmellow42 opened this issue Apr 21, 2017 · 4 comments · Fixed by #302
Labels

Comments

@marshmellow42
Copy link
Contributor

Seems to be an issue with the exit routine and associated with the qt graphing code.
@holiman when you find a little time can you take a look?

@iceman1001 iceman1001 added the bug label Apr 21, 2017
@holiman
Copy link
Contributor

holiman commented Apr 21, 2017

Could do that, if I find some time. Any more info? Only when exiting, or at other times aswell ?

@marshmellow42
Copy link
Contributor Author

Seems to only appear when sending the exit cmd from the Pm3 cli

@marshmellow42
Copy link
Contributor Author

marshmellow42 commented Apr 23, 2017

ubuntu error example:

user@ubuntuvm:~/master$ ./client/proxmark3 /dev/ttyACM0
ERROR: invalid serial port
proxmark3> exit
Segmentation fault (core dumped)
user@ubuntuvm:~/master$ 

@digitalentropy
Copy link

digitalentropy commented May 3, 2017

I can confirm on macOS 10.12.4 that the actual segfault appears only when exiting via the exit command. When breaking via Ctrl-C the issue does not appear.

I have also observed that I can tell when it's going to happen because when executing the client the focus will be taken away from my command window and I have to manually click back into it. Whenever things start off that way, exiting will result in a segfault. If I don't notice the focus change, then I do not get a segfault.

Edit: In retrospect I suppose this makes sense if it's a graphing issue. Most of the builds that didn't have this problem had no GUI due to QT library issues. It's certainly related.

marshmellow42 added a commit that referenced this issue Jun 4, 2017
fixing the crash on exit (issue #284)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants