Hide Forgot
abrt version: 1.1.14 architecture: x86_64 Attached file: backtrace cmdline: anjuta component: anjuta crash_function: __libc_message executable: /usr/bin/anjuta kernel: 2.6.33.8-149.local.fc13.x86_64 package: anjuta-1:2.30.2.1-1.fc13 rating: 4 reason: Process /usr/bin/anjuta was killed by signal 6 (SIGABRT) release: Fedora release 13 (Goddard) time: 1297970231 uid: 500 How to reproduce ----- 1. Left Anjuta open 2. Crashed when other windows were active 3.
Created attachment 479399 [details] File: backtrace
Thanks for your report, pasting the interesting backtrace snippet here: #3 0x0000003fe74751e6 in malloc_printerr (action=3, str= 0x3fe75430d8 "double free or corruption (out)", ptr=<value optimized out>) at malloc.c:6283 buf = "000000000275c290" cp = <value optimized out> #4 0x00007ff4978f7cc5 in on_save_finished (file=0x7ff47804b660 [GLocalFile], result=0x40e1920, data=<value optimized out>) at sourceview-io.c:249 sio = 0x2f9e090 [SourceviewIO] shell = 0x275f0a0 err = 0x413c770 etag = 0x275c290 "\001" I assume you have autosave enabled if this happend in the background.
Not sure why the etag could have been invalid but as we don't need it we just don't query it anymore: http://git.gnome.org/browse/anjuta/commit/?id=98231f60fadf859ff5ea7b1d08cebb78b52fc54f