After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 679203 - программа падает при редактировании открытого файла сторонней программой
программа падает при редактировании открытого файла сторонней программой
Status: RESOLVED FIXED
Product: bluefish
Classification: Other
Component: application
2.2.3
Other Linux
: High critical
: 2.2.4
Assigned To: Bluefish Maintainer(s)
Bluefish Maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2012-06-30 19:21 UTC by alex1442
Modified: 2012-07-03 20:29 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
gdb output for /usr/local/bin/bluefish (1.13 KB, text/plain)
2012-07-01 06:25 UTC, alex1442
Details
compile result with debug flags on error (11.35 KB, text/x-log)
2012-07-02 07:18 UTC, alex1442
Details
I also put a "full bt" gdb.txt for /src/bluefish (3.46 KB, text/plain)
2012-07-02 07:19 UTC, alex1442
Details

Description alex1442 2012-06-30 19:21:24 UTC
program crashes when editing a file, open a third-party software

программа падает при редактировании открытого файла другой программой 

system: linux mint 12 32-bit
Comment 1 André Klapper 2012-06-30 20:21:28 UTC
Thanks for taking the time to report this bug.
Without a stack trace from the crash it's very hard to determine what caused it.
Can you get us a stack trace? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Comment 2 Olivier Sessink 2012-06-30 20:29:53 UTC
Bluefish specific information how to provide more information can be found here:
http://bfwiki.tellefsen.net/index.php/Debugging_Bluefish#Run_Bluefish_in_the_debugger
Comment 3 alex1442 2012-07-01 06:25:30 UTC
Created attachment 217756 [details]
gdb output for /usr/local/bin/bluefish
Comment 4 alex1442 2012-07-01 06:31:53 UTC
падает через несколько секунд после редактирования открытого файла в другой программе

crashes after a few seconds after editing the file open in another program
Comment 5 Daniel Leidert 2012-07-01 13:32:34 UTC
This has also/already been reported by an Ubuntu user (including a backtrace).
Comment 6 Olivier Sessink 2012-07-01 22:02:39 UTC
can you re-create that gdb.log including the backtrace?

you forgot to type 'bt' after the crash.

did you install the debug symbols?
Comment 7 alex1442 2012-07-02 07:18:35 UTC
Created attachment 217806 [details]
compile result with debug flags on error

when kompiling with debug flags(CFLAGS="-g3 -O0 -fno-inline -fno-omit-stack-pointer) results in an error:

./configure CFLAGS="-g3 -O0 -fno-inline -fno-omit-stack-pointer"

checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking whether to enable maintainer-specific portions of Makefiles... no
checking for style of include used by make... GNU
checking for gcc... gcc
checking whether the C compiler works... no
configure: error: in `/home/alex1442/source/bluefish-2.2.3':
configure: error: C compiler cannot create executables
See `config.log' for more details.
Comment 8 alex1442 2012-07-02 07:19:51 UTC
Created attachment 217807 [details]
I also put a "full bt" gdb.txt for /src/bluefish
Comment 9 alex1442 2012-07-02 07:21:31 UTC
кстати с версией 2.0.3 в репозиториях такая же проблема

the way to version 2.0.3 in the repositories have the same problem
Comment 10 Daniel Leidert 2012-07-02 09:24:10 UTC
The configuration with the flags you want to use fails with:
cc1: error: unrecognized command line option '-fno-omit-stack-pointer'

It is probably '-fno-omit-frame-pointer' instead. 

About the backtrace you attached: Better use "bt full" to see the full backtrace. And please do an `export LANG=C` before in the terminal so we don't have russian(?) output in the backtrace.

@Olivier: The ubuntu bug report I linked contains a full backtrace.
Comment 11 alex1442 2012-07-02 10:23:55 UTC
yes i'm from russian

"Olivier: The ubuntu bug report I linked contains a full backtrace."

If you take the full trace
I was glad to help you, good luck in developing your project
___________
with respect Alksandr
Comment 12 Olivier Sessink 2012-07-02 11:02:21 UTC
@Daniel: the ubuntu bugreport doesnt have debug symbols, so I cannot see where g_strup_printf is called from.
Comment 13 Olivier Sessink 2012-07-02 14:13:41 UTC
@Alksandr: thank you for all your help, but you forgot again to type "bt" in gdb after the crash. Please see the example at http://bfwiki.tellefsen.net/index.php/Backtrace_Should_Look_Like

many thanks again for your help
Comment 14 Daniel Leidert 2012-07-02 15:15:29 UTC
Hi Olivier. There is a ull backtrace including the bluefish symbols:
https://launchpadlibrarian.net/96749942/Stacktrace.txt

The call is from modified_on_disk_warning_string() at file_dialogs.c:1402
from release 2.2.1.
Comment 15 Olivier Sessink 2012-07-02 20:48:52 UTC
I hope/think this is fixed in revision 7557 in subversion. Can anyone test this and confirm this?
Comment 16 alex1442 2012-07-03 16:27:07 UTC
hi
I tested the new version(7558), everything works,
  dialog box on the reopen the file works gut
Comment 17 Olivier Sessink 2012-07-03 20:29:53 UTC
thanks for testing, closing the bugreport