[
https://issues.apache.org/jira/browse/PROTON-2543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17541594#comment-17541594
]
Clifford Jansen commented on PROTON-2543:
-----------------------------------------
https://rr-project.org/
The related package name is "rr" on Fedora and Ubuntu.
If you can catch the failure in rr, you can reproduce exactly the run that
failed and multi threaded bugs can be debugged more easily (you can move
backwards and forwards in time in the debugger).
However, you may find that your reproducer fails easily outside of rr but
stubbornly refuses to do so with rr in the mix.
> Crash in epoll.c resched_pop_front
> ----------------------------------
>
> Key: PROTON-2543
> URL: https://issues.apache.org/jira/browse/PROTON-2543
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-c
> Reporter: Fredrik Hallenberg
> Assignee: Clifford Jansen
> Priority: Major
> Attachments: qpid-epoll-crash.patch
>
>
> During stress testing it is fairly easy to reproduce a segfault in
> resched_pop_front. Using gdb it is easy to see that polled_resched_front can
> be zero when entering this function which causes the value to wrap and then a
> crash in later calls.
> polled_resched_front is not checked when calling this function in one
> instance, the trivial fix to check this value is seen in the attached patch
> seems to work.
> Tested with Qpid Proton C++ 0.37.
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
