Pipe/Fork in C (win32)

Question

0.00/5 (No votes)

See more:

Hello Friends

I have to Different C Programs and i want to implement InterProcess Communication in between both of them. I have read some documentation on InterProcess Communication and I found that "Pipe" is best solution for me.

Than i started implementing this Program in 'C' because my both programs are in 'C language'. As i read from documents i had to #include <unistd.h> for pipe() and fork() functions. But when i compiled it; Compiler show me an Error that "Unable to open Include file 'unistd.h'." This was in Turbo c++ compiler.

After this i moved on to 'Dev-C++' there i met a new error "[Linker error] undefined reference to `pipe'."

Than i tried the same program in VC++; here i got same error as in Turbo-C++.

Actually I have windows XP installed on my system and now i found that pipe() and fork() functions are basically from POSIX Library that is designed for UNIX, LINUX, MAC OS (Not for WINDOWS)

So Plz suggest me what i have to do to run the same Program with same Functions
OR
I have to use other libraries/Functions/Header Files???????

Thanks a lot in Advance
Naveen Kumar Dushila

Posted 22-Jul-11 19:45pm

nk.dushila

Updated 22-Jul-11 19:46pm

v2

Add a Solution

Comments

Philippe Mori 23-Jul-11 9:27am

Do you want your program to be portable or you want to do Windows only development and you were using POSIX mainly because you know it (or have found sample code that use it)?

2 solutions

Solution 3

You might also consider Boost. I never tried anythink related to threading with boost as all multithreaded program I wrote was for Windows...

boost C++ Librairies[^]

Chapter 20, Threads[^]

You could also look at the result of a search for posix on windows[^]

Here is a section on Wikepedia page on POSIX: POSIX for Windows[^]

Posted 23-Jul-11 3:23am

Philippe Mori

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Sergey Alexandrovich Kryukov · Accepted Answer · 2011-07-22T20:15:00

Solution 1

Pipes for IPC? Use Named Pipes: http://msdn.microsoft.com/en-us/library/aa365590%28v=vs.85%29.aspx[^].

[EDIT]
Find some Named Pipe samples here: http://msdn.microsoft.com/en-us/library/aa365799%28v=vs.85%29.aspx[^].
[END EDIT]

For threading, use Thread functions, see http://msdn.microsoft.com/en-us/library/ms684847%28v=vs.85%29.aspx[^]. You also should learn using thread pools, see http://msdn.microsoft.com/en-us/library/ms686760%28v=VS.85%29.aspx[^].

With C++, better use _beginthread, _beginthreadex: http://msdn.microsoft.com/en-us/library/aa246693%28v=vs.60%29.aspx[^]. See also this discussion: http://social.msdn.microsoft.com/forums/en-US/vclanguage/thread/c727ae29-5a7a-42b6-ad0b-f6b21c1180b2[^].

You actually need to learn a lot more about thread synchronization primitives: events, critical sections, mutexes, semaphores and more. One often overlooked IPC approach is provided by sockets which were originally were designed for IPC, not networking. Please search MSDN for these topics.

This is a short CodeProject tutorial on threading in Windows: Multithreading Tutorial[^].

Another useful short tutorial: http://www.relisoft.com/win32/active.html[^].

—SA

Posted 22-Jul-11 20:15pm

Sergey Alexandrovich Kryukov

Updated 25-Jul-11 13:38pm

v4

Comments

nk.dushila 23-Jul-11 2:28am

@SA

ohhhh

It means in Windows we called it "Threads"

Thanks a Lot

Sergey Alexandrovich Kryukov 24-Jul-11 0:40am

You are welcome.
What do you mean? Threads are called threads in all systems I know, including POSIX-based. When I started to work with Linux, there were only processes; and threads were introduced later. Old processed could be understood like newer single-thread-only process. The units of execution are always threads; processes just host one ore more thread and provide complete data isolation; this is a reason why IPC is needed; threads of the same process can freely share data; that's why thread synchronization primitives are needed.

If you think it makes sense for you, please formally accept the answer (green button).
If not yet, your follow-up questions are welcome.
--SA

Albert Holguin 23-Jul-11 13:39pm

excellent answer and suggestions... i almost always prefer to use sockets over pipes...

Sergey Alexandrovich Kryukov 24-Jul-11 0:34am

Thank you, Albert.
As to sockets, I can understand you, they provide more flexibility. Few months ago I faced with one limitation: with a blocking pipe function, a variant of the method with timeout is not provided. I suited our needs but I was surprised a bit.
--SA

nk.dushila 25-Jul-11 0:31am

@SAKryukov

Thank you again.
That really helps me a lot.
Now i know that i am on right way.
:)

nk.dushila 25-Jul-11 0:33am

Now i am working on it and i can see the improvement.
;-)

Sergey Alexandrovich Kryukov 25-Jul-11 0:39am

You're very welcome.
Good luck, call again.
--SA

nk.dushila 25-Jul-11 8:44am

@SA

Hello again.
Actually i am little confused.

I am using pipes between two different programs.
These both are just for testing(first program for sending text and second is for receiving)

I have written some code in c in first program.
That successfully send data and receive it.

But when i'm using second program to receive data than it's not working.

now my question is
Have i to create pipe, file again in second program??
May be it needs CreateFile() or CreatePipe() again in second program(The Receiving End)

Sergey Alexandrovich Kryukov 25-Jul-11 19:40pm

Why do you think pipes are named? To identify the same pipe from the other process. Yes, you open the same pipe if two or more processes, say, one in server, one or more in clients. The pipe is identified by some name. This is pretty much like with files.
I added a link to some Microsoft samples, under [EDIT]
--SA

nk.dushila 26-Jul-11 7:43am

Okay DONE!
But there is an another Error now.
[ERROR_PIPE_BUSY 231 (0xE7) ]
[All pipe instances are busy ]

When i Google for its solution; there were showing me solutions like "Its an error b'coz of my Hardware; Nothing Else."

It is true???

Ohhh!!
By the way Thanks for those new Links.
:)

nk.dushila 26-Jul-11 8:53am

@ SA

but i don't think that i need Threads
Bcoz
i have two programs both are sending and receiving data(not simultaneously).
I just want to the basic that i got from those Links(MSDN etc. etc.)
Now i'm implementing those functions in two C Programs.

One is for sending text and second for receiving.
Here i really want to explain you that what i did in both programs:

* Sending Program--> lets say server.c
i created pipe with CreateNamedPipe();
than create a file with CreateFile();
than write data with WriteFile();

** Receiving Program: Client.c
Create a file with CreateFile(); //Error :- 231 ERROR_PIPE_BUSY
[ When i used WaitNamedPipe(), than it start waiting infinitely ]
Reading data with ReadFile();
[in this program i didn't use CreateNamePipe(), is this the Problem?? ]
Can i have to define CreateNamedPipe() again in Client.c???
Or Something else is generating error??????????????????????

Thank you In Advance.

Sergey Alexandrovich Kryukov 26-Jul-11 10:42am

Don't even play with the idea of ***not*** using threads. UI thread is not good for any sequential tasks, any time-consuming or blocking call, etc. It really should be: handle event -- quick response, nothing else. Everything else should be in threads. Threads, nothing else.

With "busy" -- this is normal situation, just check up life cycle and sequence of operations in two processes. I would advice you make the MSDN sample work as is first and later change things.

--SA

nk.dushila 28-Jul-11 1:45am

@SAKryukov

Hi

That sample programs really helped me a lot.
i used and edited
> Named pipe server using completion routines
> Named pipe client

i got that How's Client is working but Server side code is very complicated but i successfully edited that code and now it's working much better than my programs. ;-)

Now i have to prepare it for Transferring Binary data.
:)

Thanks a Lot.

nk.dushila 4-Aug-11 7:15am

Hello SA

i have one more question!!

can we use Pipes in Windows Device Driver Kit's program???

i tried but that was generating errors while building :(

I searched over MSDN about this but didn't found anything helpful..

nk.dushila 29-Jul-11 4:19am

@SAKryukov

Finally i am with Full, Working, ErrorFree Program. ;-)
And this is all because of you SAKryukov.

Thanks a lot and a lot and a lot to You.

Sergey Alexandrovich Kryukov 17-Aug-11 9:43am

Even though it's hard to believe you have something error-free as it seemingly contradicts to the First Principles :-), this is my great pleasure to hear about it.
You're most welcome.
Good luck, call again.
--SA