Skip to content

Conversation

@bagder
Copy link
Member

@bagder bagder commented Nov 6, 2025

Instead of happily ignoring return codes.

Calls that allocate data, like duplicating strings, can fail because of lack of memory which could then leave the option unset and curl would unknowingly continue (if the memory shortage was momentary).

@testclutch

This comment was marked as outdated.

@bagder

This comment was marked as resolved.

@bagder bagder force-pushed the bagder/setopt-error branch from f5e0d94 to 1731d74 Compare November 7, 2025 07:16
@bagder bagder marked this pull request as ready for review November 7, 2025 09:12
Instead of happily ignoring return codes.

Calls that allocate data, like duplicating strings, can fail because of
lack of memory which could then leave the option unset and curl would
unknowingly continue (if the memory shortage was momentary).

Closes #19385
@bagder bagder force-pushed the bagder/setopt-error branch from d5cb638 to 685a11e Compare November 7, 2025 09:28
@bagder bagder closed this in 40b1724 Nov 7, 2025
@bagder bagder deleted the bagder/setopt-error branch November 7, 2025 10:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Development

Successfully merging this pull request may close these issues.

2 participants