On Thu, 22 Feb 2001, mouss wrote:
> At 18:37 22/02/01 +0200, diman wrote:
>
> >Open AF_UNIX socket to syslogd and then use err_set_file()
> >to redirect all err/warn messages to syslogd instead of
> >stdin/stdout. That should help you debug daemons.
>
> I agree, but one of the nice things abou
In message <[EMAIL PROTECTED]>, mouss writes:
>Now having free() write to stdout/stderr isn't necessarily a good thing
>for daemons. If the message goes through a socket, it'll be hard to
>debug, which was the original intent.
>
>I suggest having some way so that when a program becomes a daemon,
>
At 18:37 22/02/01 +0200, diman wrote:
>Open AF_UNIX socket to syslogd and then use err_set_file()
>to redirect all err/warn messages to syslogd instead of
>stdin/stdout. That should help you debug daemons.
I agree, but one of the nice things about syslog interface is that it hides
all the socket
On Thu, 22 Feb 2001, mouss wrote:
> Now having free() write to stdout/stderr isn't necessarily a good thing
> for daemons. If the message goes through a socket, it'll be hard to
> debug, which was the original intent.
>
> I suggest having some way so that when a program becomes a daemon,
> it
Now having free() write to stdout/stderr isn't necessarily a good thing
for daemons. If the message goes through a socket, it'll be hard to
debug, which was the original intent.
I suggest having some way so that when a program becomes a daemon,
it can set some "silent-libc" or "libc messages go t
Also, if you do something like:
void *ptr = malloc(size);
...
ptr++;
free() will complain about it.
Make sure you are not modifying ptr after it has been malloc()ed.
On 22-Feb-01 Alfred Perlstein wrote:
> * Madhavi Suram <[EMAIL PROTECTED]> [010222 05:09] wrote:
>>
>
In message <[EMAIL PROTECTED]>, Madhavi S
uram writes:
>
>Hi
>
>I am running a C program in user space on FreeBSD 3.3 release. I got a
>warning like this:
>
> testing in free(): warning: modified (chunk-) pointer.
>
>testing is the name of the executable I am running.
>
>Could anyone tell me
* Madhavi Suram <[EMAIL PROTECTED]> [010222 05:09] wrote:
>
> Hi
>
> I am running a C program in user space on FreeBSD 3.3 release. I got a
> warning like this:
>
> testing in free(): warning: modified (chunk-) pointer.
>
> testing is the name of the executable I am running.
>
> Could a
Hi
I am running a C program in user space on FreeBSD 3.3 release. I got a
warning like this:
testing in free(): warning: modified (chunk-) pointer.
testing is the name of the executable I am running.
Could anyone tell me what this warning means? What may be the effect of
this code wh
9 matches
Mail list logo
