🚀 go-pugleaf

In article <lj1ktuINNftf@exodus.Eng.Sun.COM> deepakd@ural.Eng.Sun.COM (Deepak Dhamdhere) writes:
>I have an application that calls functions from ABC.DLL,
>those functions call routines from XYZ.DLL and those, in turn,
>call routines from the C library. This application starts a child process
>using DosExecPgm, which in turn, does the same thing. I have used 
>llibcdll.lib to link all these programs and libraries. 

Are you also using the compiler switches to ensure that DS!=SS and
that DS is always loaded on process entry.  I think these are in the
keyword EXPENTRY.  I believe that any functions you export to a DLL
must be declared with this.

>Very frequently, it generates a segementation violation. When I checked
>with Codeview, I found that the malloc() call fails because it tries to
>load a non-existent segment into DS.

It sounds like the DLL is (correctly) assuming that DS!=SS, and is
loading it, but the calling program isn't providing the segment.  Be
sure that the code and headers are using the EXPENTRY keyword for all
exported functions.

>Any clues to why is this happening ? I would like to know the correct
>way of compiling and linking ABC.DLL, XYZ.DLL and the applications.

In general, I don't like to call C run-time functions from DLL's, but
that's a different story.  Some compilers (like EMX/GCC) have the C
library functions in a DLL, so there's little linkage problems, but
you can't do that with MS-C.



-- 
  |)  David Charlap          | .signature confiscated by FBI due to
 /|_  dic5340@hertz.njit.edu | an ongoing investigation into the
((|,)                        | source of these .signature virusses
 ~|~