To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=61109
User hr changed the following:
What |Old value |New value
================================================================================
Assigned to|hr |cd
--------------------------------------------------------------------------------
------- Additional comments from [EMAIL PROTECTED] Thu Jan 26 08:32:48 -0800
2006 -------
@mmeeks: we need a bit more information. This is not the STLport, right? GCC
STL? framework::LayoutManager::UIElement has a compiler generated assignment
operator so I'm inclined to see either GCC or more probably the GCC STL as
guilty here. Is this optimized code? If yes, does this valgrind diagnostic also
happen without optimization? I've seen a few valgrind false positives in
optimized code.
memcpy(0xA08F00C, 0xA08F00C, 19)
Anyway, copying a memory area to the exactly same place looks wasteful to me,
but not exactly a bug. On the other hand the standard strictly forbids
overlapping copies for memcpy(). The STlport seems to use memmove() in such
cases.
---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
