I have written a c program that forks and execv's another
C++ program.  The reason for this is because Oracle external
stored procedure functionality does not support C++ shared
object files.  Here is my dilemma: when I create the
executable and run the a.out the program forks, and executes
the C++ program just fine.  However, when I compile the
program and use the .o file to create a .so file and then
trigger the program by executing the stored procedure from
Oracle... the .so file runs well and produces output, but
the program appears to skip over the execv function (as the
C++ program never does get executed).  Why is this so!?  Any
help would be greatly appreciated; I've been working on this
for weeks.

Thank you.

* Sent from AltaVista http://www.*-*-*.com/ Where you can also find related Web Pages, Images, Audios, Videos, News, and Shopping.  Smart is Beautiful

| I have written a c program that forks and execv's another
| C++ program.  The reason for this is because Oracle external
| stored procedure functionality does not support C++ shared
| object files.  Here is my dilemma: when I create the
| executable and run the a.out the program forks, and executes
| the C++ program just fine.  However, when I compile the
| program and use the .o file to create a .so file and then
| trigger the program by executing the stored procedure from
| Oracle... the .so file runs well and produces output, but
| the program appears to skip over the execv function (as the
| C++ program never does get executed).  Why is this so!?  Any
| help would be greatly appreciated; I've been working on this
| for weeks.

The issue causing your problem is something in either the operating system,
or the associated libraries.  You probably should proceed by posing the
problem on comp.unix.programmer, and include more detail such as the OS
you are using.  It may be the case that due to threads being present from
the Oracle execution environment, that execv is suppressed (it would be a
disaster to run execv with threads).  Likely the proper steps would be to
make the code disable all threading before or after the fork, or us the
threading functions to manage this.

I don't know enough about either Oracle or threads to give any detail to
the advice, and it wouldn't be appropriate on comp.lang.c anyway, since
this newsgroup is specifically for issues of the standard C language.
Try comp.unix.programmer, but be prepared to move on from there in the
event it really is an Oracle or threading issue (though they may be able
to help some with threads).

BTW, I'm assuming Unix based on your reference to execv.  If this is not
the case, follow to the programming group for your environment.

--
| Phil Howard - KA9WGN | for headlines that | Just say no to absurd patents |

| Dallas - Texas - USA | linuxhomepage.com  | Shop http://bn.com/ instead   |