|
From: | thebohemian at gmx dot net |
Subject: | [Bug swing/26918] GapContent - assertion triggered |
Date: | 31 Mar 2006 21:04:58 -0000 |
------- Comment #3 from thebohemian at gmx dot net 2006-03-31 21:04 ------- I suspect a threading issue here: if thread A modifies the document (and therefore the GapContent) another thread may be reading the offset values of the GapContent.GapContentPosition instances. due to the value of GapContentPosition.mark not being properly exposed to all threads the assertion in GapContentPosition.getOffset is triggered. -- thebohemian at gmx dot net changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |ASSIGNED Ever Confirmed|0 |1 Last reconfirmed|0000-00-00 00:00:00 |2006-03-31 21:04:57 date| | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26918
[Prev in Thread] | Current Thread | [Next in Thread] |