uaesupp.c
- removed my implementation of my_strdup(); it improved the malloc() debugging in so far that I could
see the strings were allocated by use of my_strdup(), but not where in the code, since it always
showed me the line in my_strdup() that contained the malloc() call, which wasn't helpful
uae2fell.h
- this macro does the trick: #define my_strdup(a) strcpy(malloc(strlen(a)+1), a)
since it can be used inline the debugger now shows the exact line where those strings were allocated,
not the best coding style, which is why I online use it when _FELLOW_DEBUG_CRT_MALLOC is set,
otherwise the standard CRT strdup is used
