rxi / log.c Goto Github PK

You can't use an internal locking-unlocking system, because you should disable interruptions during lock or unlock execution (it's not possible with CPU in user-mode). So you can include pthread and use a mutex. Let me know for a pull-request.

log_trace("%s", NULL);
output is (null) but according to standard C library usage states NULL argument behaivour is undefined. So passing NULL to functions like printf() could produce Segmentation Fault.
It would be nice to be able to log NULLs without worries.

Should the lock be locked before changing level, for the case where the log level is configurable during runtime?

I'm trying to implement it to my project but I'm facing difficulties due to the improper documentation and the functions that are not explained in it.

Is thread safe ?
can it use in multi threads ?

How to use this function in a new c program.

Is there any way to send the longs through syslog for background services?

Is this library multithreaded safe?

I want to open a single file, for example xxxx.txt, to record all the logs including all levels generated from different modules or C files.

Hello,
I wanted to ask what happens when log file reaches maximum size of fatfs (2^32 - 1).
FatFS just stops writing into file and in the library I cannot find if it's possible to set maximum size of the log file, reaching which it would start overwriting from the begging of the file
or this functionality is not foreseen or needs yet to be implemented?
thank you

rn i have

log_add_callback((void*)log_callback, (void *)0, LOG_ERROR);

but wtf do i put in place of the udata and log level?

I want to write logging messages to a text file, here is what i have done.

  FILE *fp_test = fopen("logging.txt","w");
  log_add_fp(fp_test,"INFO");
  log_info("%s is good man","rxi");
  fclose(fp_test);

But i got an empty file logging.txt.
How to achieve this?

Apparently you changed the copyright year from 2017 to 2020 but the year of first publication should be set out. It is a common misconception that the current year should always be given.

The general rule is that the year to include in a copyright notice is the year of first publication of the work. First publication is when the work is made available to the public without restriction. This includes selling a book or leaving free copies of it in a public place or posting content on your blog. Publication does not include, for example, circulating copies internally to co-workers or sending copies of a book to a publisher.

For compilations or derivative works which incorporate previously published content, the year of first publication of the compilation or derivative work is sufficient.

Source: Which Year Should You Use in Your Copyright Notice?

Best regards, Michael

Hi,

Maybe you consider changing log level names inside enum in log.h (LOG_INFO, LOG_ERROR etc.). Some of the decleration also used in linux syslog utility and that leads confisuon. For example, LOG_INFO also defined in syslog and has value 6 despite your utility's LOG_INFO has number 2.

Best regards,
Said.