Description of problem:
Since Fedora 14 calling memcpy() with overlapping source and destination ranges may produce incorrect results (which complies to the specification of memcpy).
I wrote a simple wrapper for memcpy to detect such cases and when starting ddd (which actually uses lesstif) it reports an unsafe memcpy call. Checking with valgrind (which detects such unsafe calls as well) verifies the problem.
The unsafe memcpy() call is in lib/Xm-2.1/Manager.c line 2014. It should be changed to memmove().
I'm not sure if there are more such calls hidden in the code...
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. valgrind ddd
Besides other strange stuff (probably also some false positives) it reports:
"Source and destination overlap in memcpy"
No "Source and destination overlap in memcpy" message.
Fedora 14 is End-of-Life, please reopen against a current release if this bug is still occurring. Thank you!