Integration test that causes a segmentation fault #461
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This was referenced Aug 9, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request adds
segfaultintegration test to thetestsdirectory and a test scriptrun-segfault-integration-test-repeatedly.shthat runs said integration test 100 times in a loop. The integration test is used to reproduce a segmentation fault. For the segmentation fault to occur the test usually needs to be run repeatedly.This pull request relates to the issue #460. The issue describes the segmentation fault in more detail. It also explains the motivation behind creating this pull request.
This pull request is not intended to be merged. It is simply used to demonstrate the segmentation fault and to prove that a fix introduced in another pull request #462 does indeed prevent the segmentation fault. The test code in this pull request can be freely modified and used to create a much more refined regression test.
The integration test makes multiple HTTP requests concurrently to an HTTP server. The client-side code of the test is straightforward enough, but the server-side code is bizarre. The server-side code needs to do all kinds of network I/O, filesystem I/O and thread synchronisation operations to reproduce the conditions in which a panic and the subsequent segmentation fault can occur. In my project, where I originally discovered the issue, I could get the panic to occur pretty easily, but creating an integration test that reproduces the conditions in which the panic occurs was quite difficult. Eventually I just started removing code piece by piece and when the segfault stopped occuring I added the removed code back in more or less altered form.
I hope that the integration test reproduces the panic and the segmentation fault for you.