This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
Re: AW: DLL function with string result?
- To: "Larry Hall (RFK Partners, Inc)" <lhall at rfk dot com>
- Subject: Re: AW: DLL function with string result?
- From: Christian Lescher <christian at lescher dot de>
- Date: Fri, 20 Apr 2001 18:00:00 +0200
- CC: Lescher Christian <christian dot lescher at icn dot siemens dot de>, 'Andrew Markebo' <flognat at flognat dot myip dot org>, Troy Noble <troy dot noble at channelpoint dot com>, cygwin at cygwin dot com
- References: <4.3.1.2.20010420103953.022a2700@pop.ma.ultranet.com>
> Yes, there is a general problem when you want to allocate in one DLL made
> by one compiler and de-allocate in another built be another compiler. In
> this case, the heaps are different. This is not a Cygwin-specific issue.
I see. Would it be possible then to define a second function within the DLL, let's say freeStr(const char* resStr) which releases the memory
again?
And should Troy Noble's code then work for strings > 64 KB, too? (Currently, I get an access violation, even when not freeing the allocated
memory outside the DLL.)
char*
mallocAndStrCpy (const char* srcStr) {
if (srcStr == NULL)
return NULL;
return strdup(srcStr);
}
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple