<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><font face="Calibri,sans-serif">I have two installations of Shibboleth SP v2.5.2 in two different Solaris 10 servers; they both exhibit the following behavior: When I load the mod_shib module in Apache and bounce Apache, a </font><span style="background-color: rgb(255, 255, 255); "><font face="Calibri,sans-serif"><span style="white-space: pre-wrap;">"Segmentation Fault - core dumped" message is displayed in the console and a core file is created; however, Apache does start and so far I haven't experience any other issues: I can access my applications, Shibboleth behaves as expected, etc. In other words, other than the Segmentation fault, nothing else seems wrong!!</span></font></span></div><div><span style="background-color: rgb(255, 255, 255); "><font face="Calibri,sans-serif"><span style="white-space: pre-wrap;"><br></span></font></span></div><div><font face="Calibri,sans-serif"><span style="white-space: pre-wrap;">I</span></font><font face="Calibri,sans-serif"><span style="background-color: rgb(255, 254, 254); "><span style="white-space: pre-wrap;"> use the dbx tool to look inside the core file and here is the output:</span></span></font></div><div><font face="Calibri,sans-serif"><span style="background-color: rgb(255, 254, 254); "><span style="white-space: pre-wrap;"><br></span></span></font></div><div><div><div>-bash-3.00# dbx - /usr/local/apache2.2.17_test/bin/core</div><div>Corefile specified executable: "/usr/local/apache2.2.17_test/bin/httpd"</div><div>For information about new features see `help changes'</div><div>To remove this message, put `dbxenv suppress_startup_message 7.7' in your .dbxrc</div><div>Reading httpd</div><div>core file header read successfully</div><div>Reading ld.so.1</div><div>Reading libz.so.1</div><div>Reading libssl.so.1.0.0</div><div>Reading libcrypto.so.1.0.0</div><div>Reading libdl.so.1</div><div>Reading libm.so.2</div><div>Reading libaprutil-1.so.0.3.10</div><div>Reading libexpat.so.0.5.0</div><div>Reading libapr-1.so.0.4.2</div><div>Reading libuuid.so.1</div><div>Reading libsendfile.so.1</div><div>Reading librt.so.1</div><div>Reading libsocket.so.1</div><div>Reading libnsl.so.1</div><div>Reading libpthread.so.1</div><div>Reading libc.so.1</div><div>Reading libaio.so.1</div><div>Reading libmd.so.1</div><div>Reading libc_psr.so.1</div><div>Reading libscf.so.1</div><div>Reading libdoor.so.1</div><div>Reading libuutil.so.1</div><div>Reading libgen.so.1</div><div>Reading libmd_psr.so.1</div><div>Reading libmp.so.2</div><div>Reading mod_shib_22.so</div><div>Reading libshibsp-lite.so.6.0.2</div><div>Reading libxmltooling-lite.so.6.0.3</div><div>Reading libxerces-c-3.1.so</div><div>Reading libicuuc.so.3</div><div>Reading libicudata.so.3</div><div>Reading liblog4shib.so.1.0.8</div><div>Reading libstlport.so.1</div><div>Reading libCrun.so.1</div><div>t@1 (l@1) program terminated by signal SEGV (no mapping at the fault address)</div><div>0xfe69020c: ~locale+0x0008: ld [%o3 + 16], %o2</div><div>Current function is destroy_and_exit_process</div><div> 272 exit(process_exit_value);</div><div>(dbx) where</div><div>current thread: t@1</div><div> [1] std::locale::~locale(0xfe003c58, 0x2b4, 0xfdfff374, 0x0, 0xfeff2a00, 0x1c00), at 0xfe69020c</div><div> [2] _exithandle(0xfedb7500, 0xfedb5900, 0x1c00, 0x0, 0xffbffb50, 0x0), at 0xfecc27d8</div><div> [3] exit(0x0, 0x2710, 0x756c00, 0x756c0048, 0x80808080, 0x1010101), at 0xfecb07d0</div><div>=>[4] destroy_and_exit_process(process = 0x12b888, process_exit_value = 0), line 272 in "main.c"</div><div> [5] main(argc = 3, argv = 0xffbffcdc), line 662 in "main.c"</div></div></div><div><br></div><div>From the above, looks like an issue in Apache when destroying child process; but again, only happens when mod_shib is loaded. Apache has been compiled with the same version of <span style="background-color: rgb(255, 255, 255); white-space: pre-wrap; ">C in sunstudio12.3</span> as Shibboleth.</div><div><br></div><div>My questions are:</div><ul><li>Have anyone else experienced this problem? (I've seen other "Segmentation fault" issues in the mailing list, but none seems to describe this "fails, but works anyway" scenario)</li><li>Are there any suggestions I should try? (other than moving away from Solaris – this will happen eventually)</li></ul><div>Thanks,</div><div><br></div><div>David.</div></body></html>