Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#4270 - scite segfaults randomly

Attached to Project: Arch Linux
Opened by Leonard Ritter (paniq) - Saturday, 25 March 2006, 01:20 GMT
Last edited by Dale Blount (dale) - Saturday, 25 March 2006, 02:33 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To dorphell (dorphell)
Architecture not specified
Severity Low
Priority Normal
Reported Version 0.7.1 Noodle
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

after a short period of time, even after seconds, scite segfaults, preferrably during disk access. this problem persisted in the last 2 releases.
This task depends upon

Closed by  Roman Kyrylych (Romashka)
Saturday, 07 April 2007, 17:01 GMT
Reason for closing:  Fixed
Additional comments about closing:  current version is 0.73 and in repo there is 0.72, assuming fixed
Comment by Jan de Groot (JGC) - Saturday, 25 March 2006, 11:06 GMT
Hmm, I can't reproduce it here. Does it give output to your terminal?
Comment by Leonard Ritter (paniq) - Saturday, 25 March 2006, 11:30 GMT
no, it just says segmentation fault.

its also quite hard to say when it happens. sometimes it works for 5 minutes, and then again it crashes after 15 seconds.
Comment by Jan de Groot (JGC) - Saturday, 25 March 2006, 12:50 GMT
Could you rebuild the package from ABS with these settings:

- add -g to the CFLAGS and CXXFLAGS in /etc/makepkg.conf
- build the package with "makepkg -n"

Install the package, run it with gdb `which scite`, type "run" in the program and use it for a while, wait until it crashes and type "bt" in the gdb commandline terminal. Attach the backtrace you get in a textfile here so we can find out what is going on with your scite.
Comment by Leonard Ritter (paniq) - Saturday, 25 March 2006, 22:43 GMT
will do that. so far i can definitely say that the error is gone when i pick a non-x-font, to render the font with freetype2.
Comment by Hidden (robbel) - Tuesday, 27 June 2006, 08:36 GMT
I have the same problem. Goes away when I built the latest version (1.70) from source.

Loading...