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 689210 - SIGSEGV while editing a file
SIGSEGV while editing a file
Status: RESOLVED OBSOLETE
Product: bluefish
Classification: Other
Component: application
development (SVN TRUNK)
Other Linux
: Normal normal
: 2.2.4
Assigned To: Bluefish Maintainer(s)
Bluefish Maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2012-11-28 10:47 UTC by Jean-Luc Coulon
Modified: 2020-04-24 15:16 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Bluefish sigsegv gdb backtrace (4.15 KB, text/plain)
2012-11-28 10:47 UTC, Jean-Luc Coulon
Details
gdb backtrace with symbols (4.39 KB, text/plain)
2012-11-30 09:48 UTC, Jean-Luc Coulon
Details
gdb bt svn 7742 (4.59 KB, text/plain)
2012-12-03 14:33 UTC, Jean-Luc Coulon
Details

Description Jean-Luc Coulon 2012-11-28 10:47:58 UTC
Created attachment 230073 [details]
Bluefish sigsegv gdb backtrace

Hi,

I got a segfault while editing a file.
I was simply entering a paragraph of text.
This occurs randomly but quite often.

Attached the gdb backtrace.

Regards

Jean-Luc
Comment 1 Olivier Sessink 2012-11-28 14:10:26 UTC
Thanks for reporting

Are there more details for the bugreport? Which gtk version and bluefish svn revision (see the about menu - buildinfo), which linux distribution, does this happen with any language or just one specific language (html? C?, javascript?).
Comment 2 Olivier Sessink 2012-11-28 15:11:43 UTC
can you see if you can create a backtrace with debugging symbols, such as described here:
http://bfwiki.tellefsen.net/index.php/Debugging_Bluefish

after looking at the source code I don't understand where this segfault is happening.
Comment 3 Jean-Luc Coulon 2012-11-30 09:48:47 UTC
Created attachment 230264 [details]
gdb backtrace with symbols

backtrace with symbols as requested

J-L
Comment 4 Olivier Sessink 2012-11-30 11:09:06 UTC
can you add the extra information to the bugreport:

which gtk and bluefish version

which linux distribution and version

was there a specific language syntax (C? html? etc.) active when you got the segfault (how can it be reproduced?)

I added a few checks to the latest svn (revision 7742), can you see if that gives any useful output?
Comment 5 Jean-Luc Coulon 2012-11-30 15:33:21 UTC
gtk version: 2.24.13

bluefish version: svn revision 7737

Distribution: debian sid (some parts from experimental), x86_64 (amd64) architecture

linux: 3.6.8, x86_64

syntax: html, crash occured while entering plain text between <p> </p> tags.


I've updated to svn revision 7742 and rebuilt bluefish. I will try to reproduce the crash.

Regards

J-L
Comment 6 Jean-Luc Coulon 2012-12-03 14:15:22 UTC
I've done more editing.

I never got a crash with 7742 so I reinstalled 7737 et got quickly several crashes...

J-L
Comment 7 Jean-Luc Coulon 2012-12-03 14:31:59 UTC
I was too quick... got the crash.
Attached the bt (no other messages???).

I remarked I built it with gtk3.

version of libgtk3 is 3.6.1
Comment 8 Jean-Luc Coulon 2012-12-03 14:33:12 UTC
Created attachment 230527 [details]
gdb bt svn 7742
Comment 9 Olivier Sessink 2012-12-03 20:01:24 UTC
I've added some extra debug info in revision 7748. 

Can you, furthermore instal debugsymbols, on Debian these are available in libgtk-3-0-dbg, libglib2.0-0-dbg and libxml2-dbg? That will give more info on the possibility that this bug is in gtk or glib and not in bluefish.

Can you run it again in the debugger and post the output?

Thank you very much.
Comment 10 Fabio Durán Verdugo 2013-04-07 00:47:57 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!
Comment 11 Olivier Sessink 2014-04-03 18:01:25 UTC
reopened, more users can reproduce this, see https://bugs.launchpad.net/ubuntu/+source/bluefish/+bug/1161314

we still need a very extensive backtrace to fix this, or a valgrind log.
Comment 12 André Klapper 2020-04-24 15:16:31 UTC
Hi, if this ticket is still valid in a recent version of Bluefish, then please report this under https://sourceforge.net/p/bluefish/tickets/ as GNOME Bugzilla is not used anymore by the Bluefish developers - thanks a lot!