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

No thread number upper bound leads to crash #31

Open
hongxuchen opened this issue Feb 7, 2019 · 0 comments
Open

No thread number upper bound leads to crash #31

hongxuchen opened this issue Feb 7, 2019 · 0 comments

Comments

@hongxuchen
Copy link

Since several occurrences of memory allocation malloc_safe are dependent on thread number (-T), but there is no upper bound limit for thread number, this may lead to segfault. An example is like:

./pxz -k -T 2000 -q -f /tmp/test.in
[1]    72116 segmentation fault  ./pxz -k -T 2000 -q -f /tmp/test.in

Where /tmp/test.in is an empty file.

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

No branches or pull requests

1 participant