Yet another EOF issue

Hello,

I tried the following code to experiment with EOF:

Code:

---

    int c;
   
    while(1)
    {
        printf("<GET>");
        c = getchar();
        if (c == EOF) {
            printf("<EOF>");
        }
        printf("<PUT>");
        putchar(c);
    }

---

When I ran the program and typed asd and pressed CTRL+D (EOF), I got the following output:

<GET>asd<PUT>a<GET><PUT>s<GET><PUT>d<GET>

No EOF value was passed to the program. So far so good, I understand. When I pressed CTRL+D (EOF) again with no text entered, I expected EOF to be passed to the program which happened but the <EOF> text wasn't printed - I tried setting a breakpoint on the printf line and it did trigger yet nothing was printed. Why?

When I add the break command after the call to printf, the <EOF> text gets printed when I repeat the above procedure (run, type asd, press CTRL+D twice).

I'm totally confused...

EDIT: I'm using a *nix system, not Windows.

Y'know what... you need to try that on a different system/computer ... it is possible you've found a bug in your linux shell.

Are you running this directly from a console, or within some IDE?

Code:

---

$ ./a.out
<GET>hello
<PUT>h<GET><PUT>e<GET><PUT>l<GET><PUT>l<GET><PUT>o<GET><PUT>
<GET><EOF>$
$
$ ./a.out
<GET>hello
<PUT>h<GET><PUT>e<GET><PUT>l<GET><PUT>l<GET><PUT>o<GET><PUT>
<GET>world<PUT>w<GET><PUT>o<GET><PUT>r<GET><PUT>l<GET><PUT>d<GET><EOF>$

---

The first test, I pressed ctrl-d once, at the start of an input line.
The second test I pressed ctrl-d after the 'd' of world, which caused the output of 'world'.
A second ctrl-d then caused normal EOF to be detected.

Is this other reply relevant?

Quote:

---

Originally Posted by CommonTater

Y'know what... you need to try that on a different system/computer ... it is possible you've found a bug in your linux shell.

---

I tried running the code outside my IDE and it worked. So the problem is in the IDE!

Quote:

---

Originally Posted by CommonTater

Y'know what... you need to try that on a different system/computer ... it is possible you've found a bug in your linux shell.

---

Possible, yes, but highly, highly, highly unlikely. This is not some crazy program that tests the limits of the Linux terminal and shell, it likely revolves around kkk's misunderstanding of how the terminal and program handle the keyboard signals.

@kkk: How do you know the program got an EOF if nothing was printed? I'd like to see a cut-and-paste of you running the program, from start to finish, not a paraphrase of what happened.

EDIT: Nevermind, I see it was the IDE!