Hello,
First of all, thanks for all who've worked on valgrind, it's a very useful
tool!
I frequently get an error message that I don't understand:
==28571== Thread 2:
==28571== Syscall param msgsnd(msgp->mtext) points to uninitialised byte(s)
==28571== at 0x437F66F: msgsnd (msgsnd.c:43)
==28571== by 0x804D166: send_final_message (processor.c:5043)
My message structure is something like this:
typedef _f_msg {
long mtype;
unsigned int quit_type;
char *quit_msg;
int prolong;
unsigned long prolong_count;
unsigned short prolong_type;
} f_msg;
In my function, I definitely initialize every value in the structure (both
by clearing with memset and also individually), but I still get this
message. Is it because I'm using individual types instead of a mtext
structure or array? Sorry if this is a newbie question.
Thanks for reading.
SS
------------------------------------------------------------------------------
Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
Finally, a world-class log management solution at an even better price-free!
Download using promo code Free_Logger_4_Dev2Dev. Offer expires
February 28th, so secure your free ArcSight Logger TODAY!
http://p.sf.net/sfu/arcsight-sfd2d
_______________________________________________
Valgrind-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/valgrind-users
