DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=27751>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=27751

Segmentation Fault in shmcb_cyclic_cton_memcpy





------- Additional Comments From [EMAIL PROTECTED]  2004-03-23 17:27 -------
Ouch, ok - I have this gloomy sense that I'm about to dive back into apache 
code ... 
 
I notice you're on apache 2.0.48 ... I could try to help track the problem in 
that version 
and worry about migrating it (if applicable) to cvs after, but to avoid the 
potential for 
logjams with other issues already fixed, are you able to move to 2.0.49, or 
better still, 
CVS (head or 2.0.**-stable)? At the least, have you diffed the ssl module 
source 
against later releases or CVS to check if any fixes have already been made that 
might 
cover this? 
 
Whatever you do w.r.t. apache versions - please email me a copy of the first 
few 
pages of a *trace* log during startup (this should give me all the shmcb 
geometry 
settings), and then the last few pages leading up to your first crash. I 
noticed from the 
info you've already provided that you are caching sessions around ~10Kb, which 
would indicate that you're using client-authentication and probably with some 
biggish 
certs (or longish cert-chains). My hunch is that this is triggering some 
wrap-around 
issue, either in the cyclic logic itself or in the use of variables of 
insufficient size. 
 
Please mail me the details privately, no point drowning the bugzilla database. 
As/when 
I have potential suggestions/fixes, how should we handle that? Can I send you 
diffs to 
try? Can I shell to a box where this can be reproduced? Thanks again for the 
detailed 
report.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to