Skip to content

Avoid segfault when OSM object constructer is interrupted - #326

Merged
lonvia merged 1 commit into
osmcode:masterfrom
lonvia:segfault-in-constructor
Oct 16, 2026
Merged

lonvia merged 1 commit into
osmcode:masterfrom
lonvia:segfault-in-constructor

Conversation

@lonvia

@lonvia lonvia commented Oct 15, 2026 •

Copy link
Copy Markdown
Member

Thanks to @t-miller for catching the issue and proposing a test. This takes a slightly different approach to testing the issue, using the multiprocessing module to avoid having Python code defined in a string.

Closes #323.

Thanks to @t-miller for catching the issue and proposing a test.
@lonvia
lonvia merged commit 40a39c2 into osmcode:master Oct 16, 2026
29 checks passed
@lonvia
lonvia deleted the segfault-in-constructor branch October 16, 2026 10:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

OSM wrapper construction exceptions can cause a null-object dereference during destruction

1 participant