abrt version: 1.1.14
Attached file: backtrace
cmdline: bluefish /home/davor/Web/Papak/galerija.html /home/davor/Web/Papak/galerija2.html /home/davor/Web/Papak/galerija3.html /home/davor/Web/Papak/index.html /home/davor/Web/Papak/kontakt.html /home/davor/Web/Papak/lm.js /home/davor/Web/Papak/omeni.html /home/davor/Web/Papak/pp.js /home/davor/Web/Papak/predlozak.html /home/davor/Web/Papak/slika.html /home/davor/Web/Papak/style.css
comment: I have no problem. Replacement was finished well. But Bugzilla wish to report this.
reason: Process /usr/bin/bluefish was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
How to reproduce
1.replace string in multiple files
Created attachment 468606 [details]
Created attachment 468758 [details]
Fixed upstream SVN revision 6201. Fix will be part of the 2.0.3 release. Patch to fix the Fedora package is attached.
bluefish-2.0.2-5.fc13 has been submitted as an update for Fedora 13.
bluefish-2.0.2-5.fc14 has been submitted as an update for Fedora 14.
bluefish-2.0.2-5.fc13 has been pushed to the Fedora 13 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
su -c 'yum --enablerepo=updates-testing update bluefish'. You can provide feedback for this update here: https://admin.fedoraproject.org/updates/bluefish-2.0.2-5.fc13
Created attachment 469521 [details]
Revised patch to fix another potential issue that was discovered.
Whilst testing this update, I came across an unrelated, repeatable segfault.
1. Open a large XML file, such as the uncompressed version of http://download.fedora.redhat.com/pub/epel/beta/6/x86_64/repodata/51d199dde1508f8d58483c613d551c93f245ac13402cab26ad754700c09f9d9b-primary.xml.gz
2. Whilst the scanning runs are still in progress, click the "Save As..." button and save the file with a different name. The segfault happens very quickly afterwards.
I cannot reproduce the segfault with current SVN. This may have been fixed already. A document save bug was fixed in SVN after the release of 2.0.2. I'll have to test with 2.0.2.
The scanning engine goes into a continuous loop and highlighting never completes. This is an unreported bug.
I can confirm that the segfault is fixed in current svn; is there any forecast for when 2.0.3 will be released? If it's likely to be in the next few weeks then it's probably not worth issuing another update for 2.0.2 with the latest patch.
bluefish-2.0.2-5.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.
bluefish-2.0.2-5.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.
(In reply to comment #9)
> I can confirm that the segfault is fixed in current svn; is there any forecast
> for when 2.0.3 will be released?
I expect a 2.0.3-rc1 to be released any day now.