Uhm sorry if I missed something here.. are you doing something like
allocating memory in cygwin that is freed on visual, or the other way
around..
I don't think that is a good idea.. At least not when you are using
Visual and Borland, so I guess the same problem might happen with
Visual and cygwin.
/Andy
/ Troy Noble <[EMAIL PROTECTED]> wrote:
| Personally, I'd instead write it as follows:
|
| char*
| mallocAndStrCpy (const char* srcStr) {
| if (srcStr == NULL)
| return NULL;
| return strdup(srcStr);
| }
|
| The caller can use free() on the pointer you return, since the
| DLL runs inside the same process on Win32 and thus shares the
| same global heap for malloc operations. Note that you won't be able
| to modify the "original" pointer passed to you by the caller, so
| the caller will need to make sure they also free(srcStr) at
| some point as well or you'll have a memory leak.
|
[...]
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
