New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Calling waitpid() on Windows can result in "panic: memory wrap" #16529
Comments
From eajspm@gmail.comCreated by eajspm@gmail.comThis is a bug report for perl from eajspm@gmail.com, ----------------------------------------------------------------- panic: memory wrap at script.pl line xx The bug appears to be in either win32_internal_wait() or win32_msgwait() in When this happens, the result WAIT_OBJECT_0 + count is returned to I put in a local fix to make win32_internal_wait() return 0 when There are several other places that call win32_msgwait(). They should all Below is a simple program that I used to reproduce the problem and verify my ================================================================= use POSIX ":sys_wait_h"; # This is a simple program that spawns new "processes" with fork() as fast
|
waitpid(-1, WNOHANG) would panic or segfault if called when the thread's message queue is not empty. Thanks to Erik Jezierski for the report and diagnosis. [gh Perl#16529]
waitpid(-1, WNOHANG) would panic or segfault if called when the thread's message queue is not empty. Thanks to Erik Jezierski for the report and diagnosis. [gh #16529]
Fixed in 08e55ec. |
Reopening to get in 5.32.1 |
This fix caused another bug fixed in 81295a4, and that should go into 5.30.1 |
(cherry picked from commit df667af)
Fixed in all supported releases. |
Migrated from rt.perl.org#133145 (status was 'new')
Searchable as RT133145$
The text was updated successfully, but these errors were encountered: