<div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> I haven't done tracing in mod_nss for a very long time but it did work early in the development of the module. I'm a little confused what you mean about Apache "debug" versus "normal" mode. Are you referring to the -X flag? I use that frequently myself. What problem are you trying to solve? I believe the error -8174 is a bad database error. This shouldn't cause a segfault. Are you seeing this when not doing debugging? Is it dropping a core file? thanks rob</blockquote><div> Rob, Yes, by the debug mode and normal mode I mean using -X as opposed to not using it. Yes, I see the -8174 error w/ or w/o debugging, but Apache with mod_nss was working ok in normal mode (w/o -X) despite of the -8174 error, so I guess I just ignored it. I'll rebuild my database I guess. I don't find any core files in the 'bin' directory, where I run 'httpd -X -k start -DSSL'. Should I be looking for them elsewhere? What I am doing in essence is that I am extending the TLS/SSL3 implementation in the NSS package to incorporate an extension (as defined in RFC3546). Then, I use this modified NSS in Firefox 1.5 and Apache 2.0.54 w/ mod_nss to test my modifications to the TLS handshake. Inside NSS, I am using the SSL_TRC macros for debugging. It works fine with Firefox, but I needed Apache to stay attached to the shell, so I can see the SSL_TRC output. Alternatively, I am trying to get NSS to ouput the debugging information to the Apache log files, but this might be more of a hack than the right way to do it. Do you have any alternative suggestions here? So, just to confirm, you are using Apache 2 with mod_nss and the -X flag and it works OK, right? Thanks, Peter </div></div>