Search Results

You cannot debug kernel code from gdb. You have to use a kernel debugger.

I would suggest that you are probably corrupting the kernel with repeated segfaults.

You probably are not aware, but...

There are many reasons it could be returning NULL, for instance, if it was never set in the first place, or used before the main thread managed to set it (race condition), or the main thread had a...

The only possibility I see for a problem on that line is:
the pthread_mutex_t *mutex pointer variable is probably NULL or has been subject to arithmetic change (++ or --), which usually called an...

I have no experience with busybox (that I'm aware of) and haven't used linux very much during the past few years. That said, I think you may be overestimating the memory impact of running sleep.
...

As an alternate to sleep, have you considered using ping? Read the man page appropriate to your OS and define it to ping the local host twice. This usually takes one second, but do check it. ...

You could do even better. When you start the process with /var/bin/pooya_start.sh start &, you could save the pid of the process:

echo $! > /tmp/pooya.pidAt the next iteration, you could simply...

OK,
change:

pgrep pooya > /dev/nullto

ps -ef | grep '[p]ooya' > /dev/null

I don't know what's Sh4, but if:

pgrep pooyaor

pgrep -f pooyareturn the correct pid, you could try something like this:

while sleep 10; do
pgrep pooya > /dev/null || {
echo `date` R...

Which OS and shell are you using?