httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject DO NOT REPLY [Bug 48030] Segmentation Fault
Date Fri, 23 Oct 2009 21:40:21 GMT

--- Comment #14 from Jeff Trawick <> 2009-10-23 14:40:19 UTC ---
This is one of the more craptastic things I've seen in a while :(

S10 U5, Sun Studio 12, x86 (running in VMWare Fusion, though I doubt that has
anything to do with it)

port_getn() returns -18857291
(so says fprintf; if I dbx it or truss it then port_getn() returns normal

APR 1.3.8 and previous: 

They checked for rc == -1 to catch errors.  Unless you ran it under truss or
dbx, that logic didn't run.  (I wondered why there was the special case "else
if (nget == 0) { rv = APR_TIMEUP; }").

APR 1.3.9:

This checks for rc < 0 to catch errors.  Apparently that logic catches things
that aren't errors, and unless errno happens to be one of a couple of magic
values real events won't be seen, and then the proper event won't ever be
associated again.


I wonder if I could have a compiler bug that somehow is worked around when
running under dbx or truss?  dbx I could believe, but I don't know about truss.
 I need to play outside of APR, and also try other service levels of S10.

Configure bugmail:
------- You are receiving this mail because: -------
You are the assignee for the bug.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message