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

fix bug: coredump if set linger and immediate together #2591

Merged
merged 1 commit into from
Jun 2, 2017

Conversation

laplaceyang
Copy link
Contributor

In function session_base_t::reconnect, if we set immediate to 1 and set linger, we will get into first block of reconnect function, and set pipe to NULL, but we forget to cancel timer of linger. Once timer tiggered, we will get coredump.

Solution: In function session_base_t::reconnect cancel timer in the end of set pipe to NULL

ref #2590

In function session_base_t::reconnect, if we set immediate to 1 and set linger, we will get into first block of reconnect function, and set pipe to NULL, but we forget to cancel timer of linger. Once timer tiggered, we will get coredump. Solution: cancel timer in the end of set pipe to NULL
@bjovke bjovke merged commit 9980593 into zeromq:master Jun 2, 2017
@bluca
Copy link
Member

bluca commented Aug 31, 2019

@laplaceyang could you please send a new pull request or an email with a relicense statement? As explained in https://github.com/zeromq/libzmq/blob/master/.github/CONTRIBUTING.md and https://github.com/zeromq/libzmq/tree/master/RELICENSE we are trying to relicense libzmq under MPL-2. Thank you!

@bluca
Copy link
Member

bluca commented Feb 3, 2020

@laplaceyang another ping. Please consider helping us with the relicense. Thank you!

@laplaceyang
Copy link
Contributor Author

laplaceyang commented Apr 22, 2020

@bluca I'm sorry for late reply.
I add a pr for relicense
#3882

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 this pull request may close these issues.

3 participants