Bug #110019 for EV: Segfault when preloading under mod_perl

Hi! Please send your bug report to the official contact/author address for the module in question (or send it to rt.cpan.org@schmorp.de, that's fine as well). What follows is the rationale for this request, you don't have to read it if you don't care. Why is this necessary? rt.cpan.org has many deficiencies which makes it tedious and hard to use, increasing the workload on the people who provide all the perl modules you probably appreciate (and that is really to be avoided - module authors should be able to invest all their time into improving their modules and not fighting with rt.cpan.org's bugs). Still, for some people, rt.cpan.org is useful to have, and some people even like it and really want to use it. That is fine, too. Unfortunately, the designers of rt.cpan.org didn't make their "service" optional - you can neither opt-in nor opt-out of rt.cpan.org as a module author. Just like a spammer, rt.cpan.org forces its "service" (whether wanted or unwanted) on everybody. Just like a spammer, they don't care for the people they actively hurt. Just like a spammer, they don't don't care to fix these issues and make their "service" ethically acceptable. You cannot even configure it to redirect tickets to somewhere else. Unfortunately, ignoring rt.cpan.org is not an option either: for people reporting possible bugs there is no indication that their report will be ignored, and for module authors it means they miss potentially vital bug reports such as yours (and of course it's a great impression if rt.cpan.org has lots of bug reports that are unanswered, making a module look unmaintained when in fact the opposite might be true). I am sorry that this wasted a bit of your time, but please understand that I am just as much a victim as you are - the problem is the unethical stance of the rt.cpan.org providers who force their "service" on everybody. Please redirect your bug report as stated in the beginning of this mail, and please consider petitioning the rt.cpan.org providers to stop their unethical behaviour and allow opt-in, opt-out, or some redirect option. One last issue: many people mail me that this can be "fixed" by including the bugtracker element in my module meta file. This is not true: 1. This field only affects search.cpan.org and maybe similar services. (Many people confuse rt.cpan.org with search.cpan.org for some reason). 2. It doesn't even work (there are still links to rt.cpan.org displayed). 3. Even if search.cpan.org does no longer display the link, it doesn't actually affect rt.cpan.org (and tests have shown that people go to rt.cpan.org regardless) Even *iff* rt.cpan.org would start listening on the bugtracker field, however, it's still wrong. I have a lot of modules, and each time a service like rt.cpan.org comes out, I would have to make dummy releases for all my modules. This not only creates a lot of extra work for me (I take releases very seriously) but also users, who would wonder why there is a new release. Thanks a lot, Marc Lehmann <rt.cpan.org@schmorp.de> Last updated: 2012-04-22

Thank you for abusing rt.cpan.org by ignoring my express wish, ignoring my reasonable reply, spreading bullshit propaganda, wasting my time and being a fucking troll in general. If that's your idea of getting support, I wish you a short life top spare me and others more of your presence,

MLEHMANN replies: Show quoted text
[...] Show quoted text

(Not engaging in the author's flames and limiting my reply to the technical issue at hand, for the audience of other folks having this problem who might have possible solutions.) On Sat Dec 05 10:36:16 2015, IVAN wrote: Show quoted text
If you preload EV in a mod_perl environment, it crashes the web server. Every other Perl module among the other hundreds used does not. There is a simple test case in the link. There is a problem with EV in this environment, not mod_perl. Show quoted text
Ideally, fix the bug in EV which causes Apache/mod_perl to crash when this module is preloaded. Since that seems somewhat unlikely to happen, we could consider workarounds and actions such as trying to limit what depends on the module and thus can trigger the problem.

Courtesy of Niko Tyni (thanks!): Apache dies with SIGSEGV, backtrace below. It goes away if libev-perl is built with EV_NO_ATFORK defined, so it's the __register_atfork() call in EV.xs:541 or so that causes it somehow. Presumably the event loop hooking into fork() breaks when it's mod_perl2 doing the forking. Core was generated by `apache2'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x00007f76efa2ef80 in ?? () (gdb) bt full #0 0x00007f76efa2ef80 in ?? () No symbol table info available. #1 0x00007f76f433f90f in __libc_fork () at ../nptl/sysdeps/unix/sysv/linux/x86_64/../fork.c:188 self = <optimized out> now = <optimized out> pid = 0 allp = 0x7ffcdb0b7bd0 runp = <optimized out> ppid = <optimized out> parentpid = <optimized out> __PRETTY_FUNCTION__ = "__libc_fork" #2 0x00007f76f4875585 in apr_proc_detach () from /usr/lib/x86_64-linux-gnu/libapr-1.so.0 No symbol table info available. #3 0x00007f76f15b0c1b in prefork_pre_config (p=0x7f76f512f028, plog=<optimized out>, ptemp=<optimized out>) at prefork.c:1376 no_detach = 0 debug = <optimized out> foreground = <optimized out> rv = <optimized out> userdata_key = 0x7f76f15b21fc "mpm_prefork_module" #4 0x0000560f94b449be in ap_run_pre_config (pconf=0x7f76f512f028, plog=0x7f76f50fd028, ptemp=0x7f76f50ff028) at config.c:89 pHook = <optimized out> n = 3 rv = 0 #5 0x0000560f94b22f4b in main (argc=1, argv=0x7ffcdb0b7e28) at main.c:733 c = 0 '\000' showcompile = 0 showdirectives = 0 confname = 0x560f94b66cc2 "apache2.conf" def_server_root = 0x560f94b66cb5 "/etc/apache2" temp_error_log = 0x0 error = <optimized out> process = 0x7f76f5131118 pconf = 0x7f76f512f028 plog = 0x7f76f50fd028 ptemp = 0x7f76f50ff028 pcommands = 0x7f76f510d028 opt = 0x7f76f510d118 rv = <optimized out> mod = 0x560f94d89160 <ap_prelinked_modules+64> opt_arg = 0x7f76f5131028 "(P\023\365v\177" signal_server = <optimized out>