Thread: Endless loop without program freeze

Hello,

Inside my program i have an endless loop. When the loop starts the program freeze. Is there any way for the endless loop to run without the program freeze?

The endless loop is not causing the program to freeze. Something inside of it is causing it to freeze, independent of the fact that it is an endless loop.

fgets will wait for input. Make sure the input is properly (un)buffered, and make sure that the input does happen (i.e., if the application is only putting something out there every thirty seconds, then fgets will wait for that thirty seconds until more input arrives).

hm.. wait i use this

fp2 = popen("application ", "r");
setvbuf ( fp2, NULL, _IOLBF, 2048);

the fp2 is an endless stream, how can i fgets it line-line without my program freeze? :/

I'm writing this from memory because I'm at work and I did the test this morning at home, but try something like this:

Code:

/* helper.c -- the application that provides the data */
#include <stdio.h>
#include <unistd.h>

int main(void) {
    printf("Very first output!\n");
    while(1) {
        sleep(10);
        printf("More output.\n");
    }
    return 0;  /*won't happen but whatever*/
}

Code:

/* pt.c -- reads the other application */
#define _XOPEN_SOURCE
#include <stdio.h>

int main(void) {
    FILE *hey;
    int i = 0, j = 0;
    char data[80];
    hey = popen("./helper", "r");
    setvbuf(hey, 0, _IONBF, 0);
    while (1) {
        fgets(data, 80, hey);
        if (strcmp(data, "Very first output!\n") == 0) {
            printf("Received first output %d\n", ++i);
        } else if (strcmp(data, "More output.\n") == 0) {
            printf("Received data %d\n", ++j);
        } else {
            printf("Received unexpected data %s\n", data);
        }
    }
    return 0; /* won't happen but whatever */
}

You should see regular status updates.

grrrr....well i made this

Code:

#include <stdio.h>
#include <unistd.h>


FILE		*fp2;
char 		path[300];




int main(void) {




fp2 = popen("/bin/bash -c 'airodump-ng mon0 2>&1' ", "r"); 

while (1){

	
sleep(10);
printf("test \n");



}
return 0;

and i name it helper.c

and this

Code:

test5 = fopen("test5.txt", "w");
	
	fp2 = popen("/bin/bash -c ./helper ", "r"); 

	
	setvbuf ( fp2, NULL, _IOLBF,  1024);

	while (1){

	fgets(path, PATH_MAX, fp2);

	fprintf(test5 , path);

	}

but the program freeze AGAIN wtf? :/

How can you tell that it's frozen? You are never ever ever printing anything to the screen. And printing to a file is block-buffered, so you won't see anything in your file for a long time.

I have a gui. I run the second code when a button clicked and the gui frozen :/ maybe i'm too idiot pff :/

And now that I'm testing again: it's also important how the helper application's buffers are set -- if they're set to default (block buffers), then it doesn't matter what your application does, it won't get the data until the helper has filled up a block.

Originally Posted by TuXaKoS

I have a gui. I run the second code when a button clicked and the gui frozen :/ maybe i'm too idiot pff :/

Right, but the second code doesn't print anything to the screen (and the application being popen'ed can't print anything to the screen, since all that output is going to your driver application), so not seeing anything is Exactly What You Should Expect.

could you give me an example? maybe using the code i paste it above or something like that? :/

Originally Posted by tabstop

Right, but the second code doesn't print anything to the screen (and the application being popen'ed can't print anything to the screen, since all that output is going to your driver application), so not seeing anything is Exactly What You Should Expect.

Yes , but the gui becomes gray and i cant clicked anything. It freeze.

Originally Posted by TuXaKoS

Yes , but the gui becomes gray and i cant clicked anything. It freeze.

If everything was working perfectly, that's what you would see. You have an infinite loop that is writing to the file. You will see nothing on the screen, and the GUI won't continue (because your function will never return). That is what you have written, so you can't go complaining when that's what happens. (You may have other reasons for complaining, but this is not one of them.)