Either my gcc is making fun of me, or... it finally happened, happened, I'm slightly maaaaaaad. What is going on? I thought I did not drink any of his special tea... his specialty... Why is a raven like a writing desk?

***

Sorry about the Carroll-esque tone, I could not help it — maybe I am indeed slightly mad. If you know why syslog(3) fixes the bug, or if you have any insight about what is happening here, I will be happy to hear from you.

Cheers guys.

Nicolas Canceill

[1] http://www.zsh.org/mla/users/2014/threads.html#0061
[2] http://www.zsh.org/mla/workers/2014/threads.html#00534



Le 8 juin 2014 à 17:47, Jun T. <takimoto-j@kba.biglobe.ne.jp> a écrit :

> 2014/06/08 19:25, nicolas.canceill <nicolas.canceill@laposte.net> wrote:
>> 
>>  ... so I prefer to log a bunch of stuff from within the C functions.
> 
> How about writing to the tty of another window?
> 
> Open a terminal window, and use the 'tty' command to show the device name
> of the tty of this window:
> 
> $ tty
> /dev/ttys002
> 
> Then open another terminal window, edit the source code to add lines like
> 
>    FILE *mylog = fopen("/dev/ttys002", "w");
>    ...
>    fprintf(mylog, "log/debug info....\n");
> 
> and build/run the program.