[Webkit-unassigned] [Bug 46695] [Qt] Invalid pointer access & incomplete memcmp in setUpIterator

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=46695





--- Comment #10 from chris reiss <christopher.reiss at nokia.com>  2011-01-31 14:04:10 PST ---
> This is not sufficient. 'string' can be == 'iterator.string' for different strings in the case where the allocator re-uses the same address in a subsequent allocation.

I see - in the case that 'string' has been freed, reallocated and overwritten by 'iterator.string'.  In which  case there is no first string anymore :)

Is this a problem, so long as the first thing we do to the TextBreakIterator is call toStart() ?   It doesn't seem to me that TextBreakIterator maintains any sort of state which clings to the string once its been rewound.  (its parent, QTextBoundaryFinder, doesn't do a copy either - or we cd compare against *that*)

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.