Fixed crash when stub with very long data and no delay for response #57
Conversation
This file contains 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
|
Ok merci je regarde ça Par contre un |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Salut Olivier,
J'ai rencontré un crash en voulant faire un stub avec un gros fichier (environ 610ko).
Du coup j'ai corrigé la ligne ou le crash avait lieu : j'ai simplement utilisé un malloc plutôt qu'une allocation statique pour le buffer.
Je n'ai pas compris exactement pourquoi l'allocation statique faisait craché une ligne plus loin et encore moins pourquoi ça crash quand responseTime vaut 0s et pas quand responseTime vaut 5s.
Je t'ai rajouté un test case pour que tu puisses troubleshooter ça.
Bon weekend !