httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ryan Bloom <>
Subject Re: newbie thread/process model question in hybrid server
Date Sat, 10 Jul 1999 17:26:06 GMT

I have spoken to MANY people about this in the last few days.  There are
now two platforms I know of which can handle a seg fault within a thread.
They are MVS and AS/400.  It is possible for OS/2 to catch a sigsegv, it
is also possible for UNIX to do this.  I have spoken to two different OS/2
programmers, who agree that catching a sigsegv and treating it as if it
never happened is not a good idea.  There is no garauntee that the thread
that caused the sigsegv will be the one to get the signal.  IMHO, this is
a bad idea, and it should be re-considered.


On Sat, 10 Jul 1999, Khimenko Victor wrote:

> 10-Jul-99 14:39 you wrote:
> BH> On Fri, 09 Jul 1999 14:07:40 -0400, Rodent of Unusual Size wrote:
> >>Brian Havard wrote:
> >>>
> >>> Why is hybrid more scalable than purely threaded (with proper kernel
> >>> threads)? What advantage is there in dividing the threads between multiple
> >>> processes?
> >>
> >>A segfault won't take out 100% of your server's capacity,
> >>for one thing.
> BH> Yeah, fair point but this isn't a problem on OS/2 where I can trap segfaults
> BH> (and other fatal errors like div 0) and just kill the offending thread.
> Not when this "offending thread" already destroyed important structures :-))
> Common address space is common address space...

Ryan Bloom
4205 S Miami Blvd	
RTP, NC 27709		It's a beautiful sight to see good dancers 
			doing simple steps.  It's a painful sight to
			see beginners doing complicated patterns.	

View raw message