Received: (qmail 85635 invoked by uid 65534); 7 Jan 2000 17:34:34 -0000 Message-Id: <20000107173434.85634.qmail@locus.apache.org> Date: 7 Jan 2000 17:34:34 -0000 From: Alexander Prohorenko Reply-To: white@la.com To: submit@bugz.apache.org Subject: getting signal 11 working with shared module X-Send-Pr-Version: 3.110 >Number: 5559 >Category: mod_so >Synopsis: getting signal 11 working with shared module >Confidential: no >Severity: critical >Priority: medium >Responsible: apache >State: open >Class: sw-bug >Submitter-Id: apache >Arrival-Date: Fri Jan 07 09:40:00 PST 2000 >Closed-Date: >Last-Modified: >Originator: white@la.com >Release: 1.3.9 >Organization: apache >Environment: FreeBSD nwlynx.silver-lynx.com 3.4-STABLE FreeBSD 3.4-STABLE #7: Fri Dec 31 10:5 8:48 MST 1999 din@nwlynx.silver-lynx.com:/usr/src/sys/compile/NWLYNX i386 gcc version 2.7.2.3 MySQL version 3.22.27 >Description: Jan 7 10:26:56 nwlynx /kernel: pid 95389 (httpd), uid 70: exited on signal 11 When we're trying to access some (.so) modules we're getting such segfault. Anything was okay on FreeBSD-2.2-STABLE with the same modules. However, some modules return segfault and some do not. I suppose this to be problem of Apache working with ELF binaries. >How-To-Repeat: http://www.silver-lynx.com/gtl/list - module will generate segfault. I can provide sources and makefiles for modules in a personal touch. Free for contacts on this topic. >Fix: No ideas. My 'list' module wouldn't return segfault if there will be no functions inside; segfault beeing generated even when on try to run simple function (like, void zzz(void) { return; }) >Release-Note: >Audit-Trail: >Unformatted: [In order for any reply to be added to the PR database, you need] [to include in the Cc line and make sure the] [subject line starts with the report component and number, with ] [or without any 'Re:' prefixes (such as "general/1098:" or ] ["Re: general/1098:"). If the subject doesn't match this ] [pattern, your message will be misfiled and ignored. The ] ["apbugs" address is not added to the Cc line of messages from ] [the database automatically because of the potential for mail ] [loops. If you do not include this Cc, your reply may be ig- ] [nored unless you are responding to an explicit request from a ] [developer. Reply only with text; DO NOT SEND ATTACHMENTS! ]