GNOME Bugzilla – Bug 679402
segfault in bftextview2_run_scanner
Last modified: 2012-08-24 12:25:00 UTC
Created attachment 218019 [details] Source code for file where crash happened This report originated as Fedora Bug #824464 (https://bugzilla.redhat.com/show_bug.cgi?id=824464). The Fedora 16 package of bluefish 2.0.3 has quite a few patches as a result of previous fixes, so I'll attach the bftextview2_scanner.c code included in the build. No word from the original reporter as to whether the crash is repeatable - they just said "bluefish has crashed after I tried to open an html file".
Created attachment 218020 [details] Backtrace from Fedora bug 824464
This is likely fixed in the 2.2 series. However, because we changed the scanning engine to do incremental scanning, there is no backport possible. Is this an issue for Fedora?
(In reply to comment #2) > This is likely fixed in the 2.2 series. However, because we changed the > scanning engine to do incremental scanning, there is no backport possible. Is > this an issue for Fedora? Not a biggie. I'm not seeing many duplicates of this and Fedora 16 will be end of life in five months or so (Fedora 17 has 2.2). I'm reluctant to update 2.0->2.2 because of the (albeit slight) UI changes, which are factors to consider when updating according to Fedora's updates policy, though I may end up having to do so for EPEL-6, which still has 2.0.3 and a long life ahead of it.
what is the release policy for EPEL regarding feature changes? 2.0.3 is relatively stable, and from 2.0.3 to 2.2.3 there have been lots of changes.
EPEL is actually stricter than Fedora in this respect: http://fedoraproject.org/wiki/Updates_Policy#Stable_Releases http://fedoraproject.org/wiki/EPEL/GuidelinesAndPolicies#Policy However, Fedora releases reach end of life much more quickly than EPEL releases, which makes it easier to ignore bugs in old versions and just suggest to people that they update to the latest release. If there was a serious issue with 2.0.x in EPEL I'd have to consider updating to 2.2.x as otherwise it would be unsupportable.