From: Thierry Volpiatto <thierry.volpiatto@gmail.com>
To: Dmitry Antipov <dmantipov@yandex.ru>
Cc: 16058@debbugs.gnu.org
Subject: bug#16058: 24.3.50; X protocol error: BadAlloc...
Date: Thu, 05 Dec 2013 08:10:05 +0100 [thread overview]
Message-ID: <87y53zu62a.fsf@gmail.com> (raw)
In-Reply-To: <52A02273.2030003@yandex.ru> (Dmitry Antipov's message of "Thu, 05 Dec 2013 10:51:31 +0400")
Dmitry Antipov <dmantipov@yandex.ru> writes:
> On 12/05/2013 09:51 AM, Thierry Volpiatto wrote:
>
>> Start emacs -Q
>>
>> M-x icomplete-mode
>>
>> C-x C-f <backspace> <backspace> <backspace> <right>
>>
>> --8<---------------cut here---------------start------------->8---
>> X protocol error: BadAlloc (insufficient resources for operation) on protocol request 53
>> [Thread 0x7fffefbbd980 (LWP 9875) exited]
>> [Inferior 1 (process 9875) exited with code 0106]
>> --8<---------------cut here---------------end--------------->8---
>
> Reproduced. Could you please obtain the backtrace? Currently I'm seeing:
How did you get the backtrace ?
bt return "No stack"
>> Configured using:
>> `configure --with-x-toolkit=lucid --without-toolkit-scroll-bars
>> --without-gconf --without-gsettings'
>
> Note that I can't reproduce this with a minimal Lucid build, i.e. 'configure --with-x-toolkit=lucid
> --without-all'. We can have a nasty clash with some external library; it would be nice if you can
> shrink your configuration from `--without-gconf --without-gsettings' to `--without-all', library
> by library, and find a minimal configuration where the problem still exists.
So you mean try to reproduce the bug with emacs compiled with:
./configure --with-x-toolkit=lucid --without-toolkit-scroll-bars
then with:
./configure --with-x-toolkit=lucid --without-toolkit-scroll-bars --without-gconf
then with:
./configure --with-x-toolkit=lucid --without-toolkit-scroll-bars --without-gconf --without-gsettings
then with:
./configure --with-x-toolkit=lucid --without-toolkit-scroll-bars --without-all
--
Thierry
Get my Gnupg key:
gpg --keyserver pgp.mit.edu --recv-keys 59F29997
next prev parent reply other threads:[~2013-12-05 7:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-05 5:51 bug#16058: 24.3.50; X protocol error: BadAlloc Thierry Volpiatto
2013-12-05 6:51 ` Dmitry Antipov
2013-12-05 7:10 ` Thierry Volpiatto [this message]
2013-12-05 8:46 ` Dmitry Antipov
2013-12-05 17:44 ` Eli Zaretskii
2013-12-05 19:52 ` Jan Djärv
2013-12-06 6:26 ` Dmitry Antipov
2013-12-06 8:39 ` Thierry Volpiatto
2013-12-09 8:36 ` Dmitry Antipov
2013-12-09 16:43 ` Eli Zaretskii
2013-12-09 17:11 ` Dmitry Antipov
2013-12-09 18:15 ` Eli Zaretskii
2013-12-10 13:26 ` Dmitry Antipov
2013-12-14 8:13 ` Thierry Volpiatto
2013-12-14 8:56 ` Eli Zaretskii
2013-12-14 10:10 ` Thierry Volpiatto
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y53zu62a.fsf@gmail.com \
--to=thierry.volpiatto@gmail.com \
--cc=16058@debbugs.gnu.org \
--cc=dmantipov@yandex.ru \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).