I've got an up-to-date gentoo linux with KEYWORDS="x86". If I try (as a normal user) to run abiword-2.0, I see the window opening, then instantaneously I get this message on the console and the process is killed: $ abiword-2.0 The program 'AbiWord' received an X Window System error. This probably reflects a bug in the program. The error was 'BadAlloc (insufficient resources for operation)'. (Details: serial 2133 error_code 11 request_code 53 minor_code 0) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) The program 'AbiWord' received an X Window System error. This probably reflects a bug in the program. The error was 'RenderBadPicture (invalid Picture parameter)'. (Details: serial 2233 error_code 184 request_code 157 minor_code 6) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) While if I run it as root it works well.
Hello. I can't reproduce this crash. Could you please paste the output from running "emerge info" on your system? Thanks.
Portage 2.0.49-r3 (default-x86-1.4, gcc-3.2.3, glibc-2.3.2-r1, 2.4.22) ================================================================= System uname: 2.4.22 i686 AMD Athlon(TM) XP 2000+ ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-O3 -pipe -march=athlon-xp -fforce-addr -fomit-frame-pointer -falign-fun ctions=4 -mfpmath=sse" CHOST="i686-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /var/qmail/control /usr/kde/2/share/config /usr/kde/3/share /config /usr/X11R6/lib/X11/xkb /usr/kde/3.1/share/config /usr/share/texmf/tex/ge neric/config/ /usr/share/texmf/tex/platex/config/ /usr/share/config" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" CXXFLAGS="-O3 -pipe -march=athlon-xp -fforce-addr -fomit-frame-pointer -falign-f unctions=4 -mfpmath=sse" DISTDIR="/usr/portage/distfiles" FEATURES="sandbox ccache autoaddcvs" GENTOO_MIRRORS="http://gentoo.oregonstate.edu http://distro.ibiblio.org/pub/Linu x/distributions/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage" USE="x86 oss apm avi crypt encode foomaticdb jpeg libg++ mad mikmod mpeg ncurses nls pdflib png quicktime spell truetype xmms xv zlib gdbm berkdb slang readline arts tetex bonobo svga java X sdl gpm tcpd pam libwww ssl perl python esd imlib oggvorbis gnome gtk qt kde motif opengl gphoto2 3dnow aalib apache2 cdr cscope cups curl directfb dga doc dvb faad fbcon flash gd ggi gif gtk2 guile jikes kerb eros imap lcms ldap mcal memlimit mmx mozaccess mozcalendar mozilla mozp3p mozsv g mozxmlterm mpi mysql offensive parse-clocks ppds samba scanner skey slp sse tc ltk tiff v4l vim-with-x wmf wxwindows X509 xchattext xml xml2 xvid"
tune down on optimizations first, build with debugging support and get us a backtrace. What xfree are you running ?
I'm using xfree-4.3.0-r2. Sorry but I don't know how to make a backtrace. I've done "CFLAGS="-g" emerge abiword", now what?
run it in gdb : 'gdb abiword-2.0' .. then when it crashes do 'bt' and paste the output here..
(gdb) set args --sync (gdb) run Starting program: /usr/bin/abiword-2.0 --sync (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...[New Thread 16384 (LWP 4194)] (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... The program 'AbiWord' received an X Window System error. This probably reflects a bug in the program. The error was 'BadAlloc (insufficient resources for operation)'. (Details: serial 7321 error_code 11 request_code 53 minor_code 0) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) (no debugging symbols found)...(no debugging symbols found)... Program exited with code 01. (gdb) bt No stack. (gdb) Quit (gdb) As I said, I've compiled it using 'CFLAGS="-g" emerge abiword'. I've also checked out the gcc commands and they were ok (-g, no optimizations).
Thank you for your help on this bug. However, the backtrace you provided don't have useful information, due to the stripping of symbols when installing the package. Please, try emerging abiword again via FEATURES="nostrip keeptemp" USE="debug" emerge abiword and try generating a backtrace again. If the same problem keeps coming up (no debugging symbols found), try running the abiword binary from the /var/tmp/portage/abiword-2.0.0 directory. I know this is getting very bothersome, but your bug seems to be difficult to reproduce... So we're going to have to rely on the information you can give us in order to take an action on this bugreport. Thanks
belay that, there is no stack anyway. The error indicates an X problem, you should try to rebuild your xfree with conservative CFLAGS.
re-merged with this command: #FEATURES="nostrip keeptemp" CFLAGS="-g" USE="debug" emerge abiword Then I run it with gdb: $ gdb abiword-2.0 GNU gdb 5.3 This GDB was configured as "i686-pc-linux-gnu"... (gdb) set args="--sync" (gdb) run Starting program: /usr/bin/abiword-2.0 ="--sync" [New Thread 16384 (LWP 12945)] The program 'AbiWord' received an X Window System error. This probably reflects a bug in the program. The error was 'BadAlloc (insufficient resources for operation)'. (Details: serial 2122 error_code 11 request_code 53 minor_code 0) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) Program exited with code 01. (gdb) bt No stack. (gdb) What do you mean, "rebuild your xfree with conservative CFLAGS"? P.S. I've updated xfree and gnome to the latest "x86" version.
that you don't use stuff like '-fthis -mthat' , just compile it with a basic '-march=i686 -O2 -pipe' or something. Extensive use of optimizing CFLAGS can result in a bad behaving system.
A relatively common bug that happens much less frequently with 2.0, but we don't know any one cause (within our codebase). Problems have been traced to memory, to xfree, to wm, etc. Actually, I'm don't think I've seen the RenderBadPicture before. The BadAlloc is common (and may be causing the following). BTW, with a debug xfree syncing under a mem tracer (such as the subfncs of valgrind) you could trace the allocation to the exact operation in charge, but I don't know what you could do about it. You do have sufficient ram and all that, right? Oh, and another thing: CXXFLAGS="-O3 -pipe -march=athlon-xp -fforce-addr -fomit-frame-pointer -falign-f unctions=4 -mfpmath=sse" has to go. That is trashing your build, assuming you are using gcc3 on an athlon xp. Notice the cxxflags: abiword is a c++ program. ditch the force-addr and forced sse. omitted frame pointers are fine as long as you arent debugging (afaik), and I doubt align-functions is any problem. The easiest way to start debugging for flags though would be: CXXFLAGS="-O2 -pipe" If that works, from there, you can start adding back individual flags to isolate, but it won't get you any significant perf gain AFAIK (talking about this program specifically).
Fixed in 2.0.1. I'd suggest masking 2.0.0.
*nod*
2.0.1 has other problems... i can make it crash switching document langauge. Only can't get a bt because of nptl/gdb/kernel i think (havent really looked into that). Is this fixed in 2.0.1 because you lowered CFLAGS or because of bugfixes in it ?
I didn't touch my CFLAGS (-march=athlon-xp -fomit-frame-pointer -O3 -fforce-addr). I can change language without any problem. Is there a specific sequence to take?