On 08/31/2012 12:01 AM, Jiri Svoboda wrote: > Jakub wrote: >> Not >> sure if log_msg() is suitable for logging from the async framework. >> Perhaps klog_printf() could do.
> Several points here: - in case of libraries errors should be > propagated to the caller, not logged out of band and out of control > of the caller In this case, there is no caller to return to as the failure happens in a manager fibril. I think we already use klog_printf() to report malloc assertions in order to avoid deadlock with the malloc locks, so this would not be the first libc user of it. I think losing a notification is a problem serious enough which warrants logging of a message. Jakub _______________________________________________ HelenOS-devel mailing list [email protected] http://lists.modry.cz/cgi-bin/listinfo/helenos-devel
