By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
446,193 Members | 843 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 446,193 IT Pros & Developers. It's quick & easy.

Purify reports UMR in wrong location

P: n/a
I am sending a structure over a socket, and so the structure is copied
into a message buffer first. The structure has some spare fields in
order to align the fields properly. Since those spare fields are
never set, I expect Purify to report an Uninitialized Memory Read when
the structure is copied into the message buffer, but Purify actually
waits until the message buffer is read before reporting the error. So
Purify doesn't report an error when the actual uninitialized byte is
read, it reports an error when a memcpy of the uninitialized byte is
read. Anyone else ever see this?

Thanks,
Eric Simon
Jul 22 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a

"Eric" <pu*****@hotmail.com> wrote in message news:dd**************************@posting.google.c om...
I am sending a structure over a socket, and so the structure is copied
into a message buffer first. The structure has some spare fields in
order to align the fields properly.


This is way off topic, but I think you'll find that Purify has some special
suppressions in effect for struct copies. Call Pure Software, Rational, IBM
or whoever now owns the product.

Jul 22 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.