in reply to Re^3: Event module and threads/fork segfault on Win32
in thread Event module and threads/fork segfault on Win32
The OS is WinXP Professional SP2 running in a VMWare VM v5.5.51 build-19175C:\>perl -v This is perl, v5.8.8 built for MSWin32-x86-multi-thread (with 50 registered patches, see perl -V for more detail) Copyright 1987-2006, Larry Wall Binary build 820 [274739] provided by ActiveState http://www.ActiveSta +te.com Built Jan 23 2007 15:57:46 Perl may be copied only under the terms of either the Artistic License + or the GNU General Public License, which may be found in the Perl 5 source ki +t. Complete documentation for Perl, including FAQ lists, should be found +on this system using "man perl" or "perldoc perl". If you have access to + the Internet, point your browser at http://www.perl.org/, the Perl Home Pa +ge. C:\>perl -MEvent -e"print qq($Event::VERSION\n)" 1.08 C:\>perl -Mthreads -e"print qq($threads::VERSION\n)" 1.58
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re^5: Event module and threads/fork segfault on Win32
by BrowserUk (Patriarch) on Jun 05, 2007 at 16:04 UTC | |
To resolve this you're probably going to have to track down which version of what caused things to break and then raise a specific bug report against the specific component. And that will likely be a PITA, as there are so many versions and combinations of versions to test. For example; threads appears to have gone through around 20+ version between where you are and I am. A few things that might help: HTH some. Good luck. Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
| [reply] [d/l] |
|
Re^5: Event module and threads/fork segfault on Win32
by BrowserUk (Patriarch) on Jun 06, 2007 at 03:12 UTC | |
It would appear to be 5.8.8 that is the deciding factor as to whether it segfaults or not. Having installed the latest versions threads:v1.62 and Event:v1.09; I get no trap from your code under 5.8.6(AS811), but I do under 5.8.8(AS817). However, if I do not nest the threads stuff inside the Event callback, no trap occurs either. HTH. Update: I finally got the segfault to occur under the auspices of a debugger. The trap is occurring in ev.c:187, when the if statement attempts to access WvACTIVE(wa). That doesn't explain why it happens, but it might give somebody a starting point.
And a stack trace:
I'm intrigued by what you are trying to achieve by mixing these two anyway? Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
| [reply] [d/l] [select] |