Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 47071 - monodevelop crashes, problem fixed after upgrading to ~x86
Summary: monodevelop crashes, problem fixed after upgrading to ~x86
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: All Linux
: High critical (vote)
Assignee: dotnet project
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-04-07 04:59 UTC by Martin Probst
Modified: 2004-06-02 13:33 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Probst 2004-04-07 04:59:34 UTC
Monodevelop used to crash on my system after typing a few letters with this message:
(MonoDevelop:29817): Gtk-WARNING **: Invalid text buffer iterator:
either the iterator is uninitialized, or the characters/pixbufs/widgets
in the buffer have been modified since the iterator was created.
You must use marks, character numbers, or line numbers to preserve a
position across buffer modifications.
You can apply tags and insert marks without invalidating your iterators,
but any mutation that affects 'indexable' buffer contents (contents that
can be referred to by character offset)
will invalidate all outstanding iterators
/usr/bin/monodevelop: line 40: 29817 Speicherzugriffsfehler  mono
--debug ./MonoDevelop.exe $@

I didn't file a bug report because I installed some things from CVS and thought it was a problem with my installation in here.
Now yesterday I upgraded my gnome desktop to ~x86 2.6 version which includes GTK+ 2.4 and now monodevelop works like a charm.

It's only a guess, but could it be that monodevelop depends on GTK+ 2.4?

Reproducible: Didn't try
Steps to Reproduce:




Portage 2.0.50-r3 (default-x86-1.4, gcc-3.3.3, glibc-2.3.
3_pre20040207-r0, 2.6.4-gentoo-r1)
=================================================================
System uname: 2.6.4-gentoo-r1 i686 Intel(R) Pentium(R) 4 CPU 2.60GHz
Gentoo Base System version 1.4.3.13p1
distcc 2.12.1 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) 
[disabled]
Autoconf: sys-devel/autoconf-2.59-r3
Automake: sys-devel/automake-1.8.3
ACCEPT_KEYWORDS="x86 ~x86"
AUTOCLEAN="yes"
CFLAGS="-march=pentium4 -O3 -funroll-loops -fomit-frame-pointer -pipe"
CHOST="i686-pc-linux-gnu"
COMPILER="gcc3"
CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config 
/usr/kde/3.1/share/config /usr/kde/3.2/share/config 
/usr/kde/3/share/config /usr/lib/mozilla/defaults/pref 
/usr/share/config /usr/share/texmf/dvipdfm/config/ 
/usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ 
/usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ 
/var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-O2 -mcpu=i686 -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs ccache sandbox"
GENTOO_MIRRORS="ftp://ftp.tu-clausthal.de/pub/linux/gentoo/ ftp:
//sunsite.informatik.rwth-aachen.de/pub/Linux/gentoo http://linux.rz.
ruhr-uni-bochum.de/download/gentoo-mirror/ ftp://linux.rz.
ruhr-uni-bochum.de/gentoo-mirror/ http://mirrors.sec.informatik.
tu-darmstadt.de/gentoo http://ftp.uni-erlangen.de/pub/mirrors/gentoo 
ftp://ftp.uni-erlangen.de/pub/mirrors/gentoo"
MAKEOPTS="-j3"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage"
SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage"
USE="X acpi alsa apache2 apm arts avi berkdb cdr crypt cups doc dvd 
encode esd foomaticdb gdbm gif gnome gpm gtk gtk2 gtkhtml guile imlib 
java jpeg libg++ libwww mad mikmod mmx motif mozilla mozilla-firebird 
mpeg ncurses nls nptl oggvorbis opengl oss pam pdf pdflib perl php png 
python qt quicktime readline samba sdl slang spell ssl svga tcltk tcpd 
tetex tiff truetype vim vim-with-x x86 xml2 xmms xv zlib"
Comment 1 Peter Johanson (RETIRED) gentoo-dev 2004-06-02 09:34:04 UTC
This should be fine for gtk+-2.2... MD doesn't really bind anything particular to gtk+-2.2. Is this bug still valid with the new Beta2 mono stuff just added to portage?
Comment 2 Martin Probst 2004-06-02 13:33:32 UTC
Sorry I didn't keep this bugreport up to date. It seems to have been a bug in monodevelop not related to GTK+ - at least Todd Bermann says so.

With the latest MonoDevelop everything works fine.