Summary: | Selection crash | ||
---|---|---|---|
Product: | poppler | Reporter: | Johan Dahlin <johan> |
Component: | general | Assignee: | Kristian Høgsberg <krh> |
Status: | RESOLVED FIXED | QA Contact: | |
Severity: | critical | ||
Priority: | high | CC: | bugs-fd, burner, chpe, freedesktop.domain.sjmorgan, ghepeu, nshmyrev |
Version: | unspecified | ||
Hardware: | x86 (IA32) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: |
proposed fix
Proposed patch Updated patch |
Description
Johan Dahlin
2005-09-08 19:16:19 UTC
Created attachment 3205 [details] [review] proposed fix For a stack trace, see: http://bugzilla.gnome.org/show_bug.cgi?id=315552 krh, this bug has more than ten dups in evince bugzilla. Any chance to see patch applied? I've discussed that bug with krh on irc and he was disappointed that p == NULL appears in the list. It should _not_ be so. Really, why it doesn't happens on splash and only on cairo backend? So this patch doesn't solve the reason of trouble. I think we should found why NULL is appeared on the list. Created attachment 3819 [details] [review] Proposed patch This patch should fix the problem, the real reason was that begin >= end invariant was not holded. Created attachment 3830 [details] [review] Updated patch The previous patch doesn't solve all cases in selection crashes. The updated patch is intended to do that. Besides it fixes build of current CVS with cairo and several splash color problems. *** Bug 4386 has been marked as a duplicate of this bug. *** Would you like testing on this? I'm one of the people that reported this bug against Evince. If there are particular things to try that should exercise this, I'm willing to give them a shot. P.M. Of course testing is needed krh: ping, evince bug already has more than 20 dups *** Bug 4929 has been marked as a duplicate of this bug. *** *** Bug 4326 has been marked as a duplicate of this bug. *** Nickolay, thanks, I've committed you patch to CVS HEAD. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.