home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.os.os2.programmer:7127 comp.os.os2.apps:9488 comp.os.os2.misc:39883
- Newsgroups: comp.os.os2.programmer,comp.os.os2.apps,comp.os.os2.misc
- Path: sparky!uunet!cs.utexas.edu!zaphod.mps.ohio-state.edu!malgudi.oar.net!news.ans.net!cmcl2!panix!os2man
- From: os2man@panix.com (Larry Salomon Jr.)
- Subject: Re: DLL question
- Message-ID: <1992Dec18.140136.1455@panix.com>
- Date: Fri, 18 Dec 1992 14:01:36 GMT
- References: <lj1ktuINNftf@exodus.Eng.Sun.COM>
- Organization: PANIX Public Access Unix, NYC
- Keywords: DLL library
- Lines: 34
-
- In <lj1ktuINNftf@exodus.Eng.Sun.COM> deepakd@ural.Eng.Sun.COM (Deepak Dhamdhere) writes:
-
- >I am posting this question for a friend, hope that the DLL experts can
- >help him out.
-
- >Deepak Dhamdhere
-
- >************
- >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.
-
- >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.
-
- >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.
-
- >Your immediate help will be appreciated very much.
- >************
-
- This really belongs in comp.os.os2.programmer, but...
-
- Insure that he is building the DLLs by linking with LLIBCDLL and that the
- functions he is calling are defined as EXPENTRY.
-
- Lar
- --
- "If you choose not to decide, you | "My other body is in the shop" - seen
- still have made a choice" - Rush | on a T-shirt
- ------------------------------------------------------------------------
-