Subject: Re: /etc/login.conf required to exist after user(8) changes
To: Peter Seebach <>
From: Martin Husemann <>
List: current-users
Date: 07/31/2005 12:17:51
On Sun, Jul 31, 2005 at 05:08:40AM -0500, Peter Seebach wrote:
> It's not the NULL part that's at issue; it's that some processors trap if you
> load an invalid address into an address register, and invalidate the addresses
> of freed memory.  So it generates a processor trap, and the question of what
> would happen if you got to the compare instruction is rendered irrelevant.

I'm not arguing the processor trap part, but I don't believe any 
implementation would be allowed to risk such a user visible trap on the
comparison of a pointer against NULL.

Is there any concrete implementation that you think about?