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 120118 - crash: enable line numbers, then disabling them causes crash
crash: enable line numbers, then disabling them causes crash
Status: RESOLVED NOTABUG
Product: gtksourceview
Classification: Platform
Component: General
unspecified
Other Linux
: High major
: ---
Assigned To: GTK Sourceview maintainers
GTK Sourceview maintainers
: 124880 127845 127900 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2003-08-18 06:19 UTC by Ken Deeter (Kentarou Shinohara)
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.3/2.4

Attachments
gtksourceview-0.6.0-border_fix.patch (479 bytes, patch)
2003-10-02 00:27 UTC, Leonardo Boshell 		none Details | Review

Description Ken Deeter (Kentarou Shinohara) 2003-08-18 06:19:16 UTC 
Using 2.4 beta1 ebuilds from breakmygentoo.net

Steps to reproduce:

1 launch gedit
2 go to prefs
3 enable line numbers
4 don't close prefs window and disable line numbers --> crash
Comment 1 Paolo Maggi 2003-08-23 14:37:12 UTC 
I cannot reproduce this bug.
Could you please attach more info. A backtrace would help a lot.
See http://bugzilla.gnome.org/getting-traces.cgi for more info on how
to get a stack trace.
Comment 2 yoplait 2003-09-29 18:15:26 UTC 



+
Trace
    40524






    

  • 
#0
gdk_window_get_toplevel

    
                from
                /usr/lib/libgdk-x11-2.0.so.0

    

    • 













Comment 3


yoplait





          2003-09-29 18:16:09 UTC
        



Aucun processus de ce type = processus not found






Comment 4


Marinus Schraal





          2003-09-29 21:58:59 UTC
        






+
Trace
    40532






    

  • 
#0
gdk_window_get_toplevel

    
                from
                /usr/lib/libgdk-x11-2.0.so.0

    

    • 

  • 
#1
gdk_window_process_updates_internal

    
                from
                /usr/lib/libgdk-x11-2.0.so.0

    

    • 

  • 
#2
gdk_window_process_all_updates

    
                from
                /usr/lib/libgdk-x11-2.0.so.0

    

    • 

  • 
#3
gdk_window_update_idle

    
                from
                /usr/lib/libgdk-x11-2.0.so.0

    

    • 

  • 
#4
g_idle_dispatch

    
                from
                /usr/lib/libglib-2.0.so.0

    

    • 

  • 
#5
g_main_dispatch

    
                from
                /usr/lib/libglib-2.0.so.0

    

    • 

  • 
#6
g_main_context_dispatch

    
                from
                /usr/lib/libglib-2.0.so.0

    

    • 

  • 
#7
g_main_context_iterate

    
                from
                /usr/lib/libglib-2.0.so.0

    

    • 

  • 
#8
g_main_loop_run

    
                from
                /usr/lib/libglib-2.0.so.0

    

    • 

  • 
#9
gtk_main

    
                from
                /usr/lib/libgtk-x11-2.0.so.0

    

    • 

  • 
#10
main

    • 

  • 
#11
__libc_start_main

    
                from
                /lib/libc.so.6

    

    • 








backtrace from gedit crash

it only seems to happen when turning line numbers off. The gconf
setting gets propagated before the crash, on next startup the
linenumbers will be off.






Comment 5


Paolo Maggi





          2003-09-30 15:35:36 UTC
        



According to Obz and foser in #gentoo this bug can be reproduced using
test-widget in gtksourceview/tests disabling both markers and line
numbers.

I cannot reproduc it on my machine (gtk+ from CVS on RH Linux 8)







Comment 6


Gustavo Giráldez





          2003-09-30 17:14:27 UTC
        



I can't reproduce either (RH9 + very recent CVS Gnome 2.4).  Which
version of Gtk+ and GtkSourceView are you using?






Comment 7


Vincent Untz





          2003-09-30 21:29:00 UTC
        



I'm using Garnome (the version for GNOME RC1, IIRC) on Debian. I can't
reproduce. I don't think there are Debian packages for 2.4 yet, so I
can't test native packages.

It may be a problem with programs compiled with -O5 and more (like
many bugs reported by gentoo users). Can you rebuild things without
optimizations ?






Comment 8


Leonardo Boshell





          2003-10-02 00:27:59 UTC
        



Created attachment 20422 [details] [review]
gtksourceview-0.6.0-border_fix.patch






Comment 9


Leonardo Boshell





          2003-10-02 00:34:49 UTC
        



Hello.

I can reproduce the behavior reported, as well as the backtrace
attached by foser.

Having a look at the problem, I found a possible workaround. The crash
seems to go away when gtksourceview (v0.6.0) is compiled with the
above patch. As foser told me:

"..although i think your patch is a workaround for the real problem, i
think it indicates where we need to look.. could you contact paolo or
add it to the gnome bugreport later on so we can work from there ?"

Thanks.






Comment 10


Paolo Maggi





          2003-10-02 16:38:56 UTC
        



This patch looks a workaround to me and so I don't think it should be
included in gtksourceview.
BTW, it shows as that the problem is the disappearing of the "left
window" (I was already suspecting it).

Are you sure your gtk+ patches are not the cause of the problem?
Have you tried to reproduce it on a non-over-optimized glib/pango/gtk+
stack?






Comment 11


Paolo Maggi





          2003-10-18 14:57:38 UTC
        



*** Bug 124880 has been marked as a duplicate of this bug. ***






Comment 12


Ken Deeter (Kentarou Shinohara)





          2003-10-21 22:21:08 UTC
        



Just to comment, I'm using "-march=pentium3 -O3 -pipe -fPIC" on my 
gentoo. Last time I checked, thats still pretty conservative. 






Comment 13


Elijah Newren





          2003-12-10 05:07:52 UTC
        



Ken: We mark all bugs compiled with -O3 or higher as NOTABUG since
that level of optimization is known to break some things.  Can you
recompile with -O2 and see if the crash still occurs?






Comment 14


Ken Deeter (Kentarou Shinohara)





          2003-12-10 05:29:02 UTC
        



I tried with -O2 with 2.4.0, problem still exists. I get the same
stacktrace as foser above.






Comment 15


Paolo Maggi





          2003-12-10 13:38:25 UTC
        



This seems to be a gentoo specific bug. Nobody using other dists is 
able to reproduce it.
I'm going to re-close it as NOTABUG. 
Please, repost this bug to gentoo guys if you want to see it fixed.






Comment 16


Paolo Maggi





          2003-12-11 14:47:56 UTC
        



*** Bug 127845 has been marked as a duplicate of this bug. ***






Comment 17


Paolo Maggi





          2003-12-11 15:20:44 UTC
        



*** Bug 127900 has been marked as a duplicate of this bug. ***