[krbdev.mit.edu #5562] config file parsing error messages

[Ken Raeburn via RT]

On May 21, 2007, at 11:28, Ken Raeburn via RT wrote:
> Many of the specific parse error types already have distinct error
> codes, but os_init_paths maps several of them onto
> KRB5_CONFIG_BADFORMAT.

And, of course, if os_init_paths fails, we won't have a context in  
which to store the detailed error info.  *sigh*

Perhaps we should pass back the profile-library error codes instead  
of mapping them to KRB5_CONFIG_BADFORMAT?