At the top of dmalloc.h, there's a test that determines the return type
of all the wrapped functions. It ends up setting DMALLOC_PNT to void*
in the C++ case. The strdup function is supposed to always return a
char*, though. Because C++ is very picky about pointer conversion,
this can cause compiler errors because strdup is not returning a char* .
Does the following patch make sense?

--
Dan Nelson
dnelson@...

--- dmalloc.h.3~ Tue Jun 10 14:55:53 2003
+++ dmalloc.h.3 Wed Jun 18 16:40:38 2003
@@ -240,7 +240,7 @@
* of memory.
*/
extern
-DMALLOC_PNT dmalloc_strdup(const char *file, const int line,
+char * dmalloc_strdup(const char *file, const int line,
const char *string, const int xalloc_b);

/*

--- malloc.c.orig Tue Jun 10 14:55:53 2003
+++ malloc.c Wed Jun 18 16:45:34 2003
@@ -937,18 +937,18 @@
* xalloc_b -> If set to 1 then print an error and exit if we run out
* of memory.
*/
-DMALLOC_PNT dmalloc_strdup(const char *file, const int line,
+char * dmalloc_strdup(const char *file, const int line,
const char *string, const int xalloc_b)
{
DMALLOC_SIZE len;
- DMALLOC_PNT *new_string;
+ char *new_string;

len = strlen(string) + 1;

new_string = dmalloc_malloc(file, line, len, DMALLOC_FUNC_STRDUP,
0 /* no alignment */, xalloc_b);
if (new_string != NULL) {
- strncpy((char *)new_string, string, len - 1);
+ strncpy(new_string, string, len - 1);
new_string[len - 1] = '\0';
}