#4 Flagging some inconsistences
Dear Hayati Aygün,
I am flagging some minor issues. May be they are
related to my lack of understaning of DUMA internals.
I am using Windows XP SP2 and a MinGW + Msys
environment (Gcc 3.4.5).
I left any configuration macro as found in the source
code (latest 2.47.27 from sourceforge).
Ok. I typed make and I found the following issues
1) In the file createconf.c line 287 you are using
a printf. You shuold use fprintf (I guess).
Ok I modified the line 287 of createconf.c to use a
fprintf.
I typed
make clean
make
Everything seems OK. All the test passed. But using
DUMA in some simple examples I observed
1) The variable DUMA_PROTECT_FREE is declared as
global (extern int) in the documentation but
static long in duma.c. So the variable is not global
and I cannot follow the documentation suggetsions
(set the variable in the debugger)
In duma.h the variable is not present in the global
variable blocks (lines from 65 to 69 of duma.h)
2) The same issue is present for the variable
DUMA_ALLOW_MALLOC_0. Declared extern int in the doc
but defined static int in duma.c. It is not present
in duma.h global declaration (lines form 65 to 69 of
duma.h)
Are there any reasons to make those variables static?
At least the documentation is no longer consistent.
I changed the two variable definitions as global int
in duma.c and duma.h.
Doing a
make clean
make
everything went well.
I am starting to use DUMA is some projects...
Regards
Massimo
P.S
Thanks for DUMA. It seems a good tool.
Logged In: YES
user_id=1354765
Originator: NO
You're right. i changed the global variables to static structure elements or thread local structure elements. The man page is really outdated. But I updated the README.
Is there need to change these settings (DUMA_PROTECT_FREE, DUMA_ALLOW_MALLOC_0, ..) from gdb debugger?
I have provided new macro functions (for some few settings) you may call from your code - but not from within gdb.
Some variables are now thread local .. that is why they can't be global any more. The macro functions are to allow compilation of the same source code defining empty macros even without DUMA.
For now i don't see the application, where you need to change the settings via global variables from within gdb. Maybe i'm wrong. I'll overthink if you have good reasons.
regards
Hayati Ayguen