Re: [LTP] More informative error messages from SAFE_*?

[<ch...@su...>]

Hi!
> I ran into problems when using SAFE_OPEN, it complained about a
> non-existing path. It didn't tell me what path it tried, which made
> debugging more difficult than necessary.
> 
> I'm prepared to change the error messages in safe_macros.c to have a
> syntax similar to what I plan for safe_open():
> 
> 		tst_brkm(TBROK | TERRNO, cleanup_fn,
> 			"%s:%d: open(%s,%d) failed",
> 			file, lineno, pathname, oflags);
> 
> 
> I skipped the creation mode parameter since it was too much work
> handling an optional parameter...
> 
> Would anyone see a point in having all functions using a similar error
> syntax?

Sounds good to me.

-- 
Cyril Hrubis
ch...@su...