[ale] OpenBSD, FreeBSD

[Dan Newcombe]

Slight diff...a GPF is usually a programmer not coding for something
(trying to write to a null pointer) and the OS then terminates the
program...very similar to a core dump for a segmentation fault.  Just with
the huge windows API, there are tons of things to forget to do, set,
check.

The BSOD is caused by the kernel barfing, or something in the kernel area
like a driver barfing.  While the kernel can halt an app pretty decently
when it misbehaves, it can't do so for itself.  The BSOD usually has
enough info on it to figure out what driver caused the barf...not why, but
its a start.

Don't know about the serial port thing though - glad my NT install is
stable.

On Wed, 15 Dec 1999, Chris Fowler wrote:
> I believe that if you run debug on a serial port attach a terminal to it and
> then get BSOD you should be able to debug the problem.  I could be wrong but
> I do think that is how it works.
> 
> -----Original Message-----
> From: Dan Newcombe [mailto:Newcombe at mordor.clayton.edu]
> Sent: Wednesday, December 15, 1999 1:02 PM
> To: ALE
> Subject: Re: [ale] OpenBSD, FreeBSD
> 
> 
> > My issue is performance and security, I don't care much about flexibility
> > anymore. I like linux because it is alot more friendlier then MS, at least
> > with linux you can tell if something failed, in MS you get a GPS. But the
> > company I work for has *outgrowed* linux, we have more attacks and
> different
> > stuff.
> 
> Cool...next time my MS app dies, I'll get a free Global Positioning
> Satellite!!!   ;)    GPF I believe  you mean.  However, I don't see what
> you mean by "you can tell if something failed".  I think the GPF is a
> pretty good indication something failed.  
> 
> --
> To unsubscribe: mail majordomo at ale.org with "unsubscribe ale" in message
> body.
> --
> To unsubscribe: mail majordomo at ale.org with "unsubscribe ale" in message body.
> 

--
To unsubscribe: mail majordomo at ale.org with "unsubscribe ale" in message body.