unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Mauro Aranda <maurooaranda@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 53778@debbugs.gnu.org
Subject: bug#53778: 29.0.50; Can't start Emacs because of RenderBadPicture X protocol error
Date: Fri, 4 Feb 2022 12:45:26 -0300	[thread overview]
Message-ID: <CABczVwc=aVWyTQoRdxMFo7SU9nc=b-rA6dUgz6fai5q5jDMEqA@mail.gmail.com> (raw)
In-Reply-To: <83czk23bmn.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 928 bytes --]

On Fri, Feb 4, 2022, 12:16 Eli Zaretskii <eliz@gnu.org> wrote:

>> From: Mauro Aranda <maurooaranda@gmail.com>
>> Date: Fri, 4 Feb 2022 12:14:54 -0300
>> Cc: 53778@debbugs.gnu.org
>>
>> With GDB 10.1, I get:
>>
>> ../../gdb/utils.c:671: internal-error: virtual memory exhausted: can't
allocate 4064 bytes.
>> A problem internal to GDB has been detected,
>> further debugging may prove unreliable.

> How much memory and how much swap do you have on that system?  Can you
> enlarge the virtual memory available to applications (e.g., by
> enlarging the amount of swap)?

bash-5.1$ free -m
               total        used        free      shared  buff/cache
available
Mem:            1883         554         523          34         806
 1083
Swap:           4095           0        4095

> Or maybe try a different version of GDB, either newer (GDB 11 was
> released some time ago) or older.

I'll see what I can do, thank you.

[-- Attachment #2: Type: text/html, Size: 1305 bytes --]

  reply	other threads:[~2022-02-04 15:45 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-04 14:07 bug#53778: 29.0.50; Can't start Emacs because of RenderBadPicture X protocol error Mauro Aranda
2022-02-04 14:38 ` Mauro Aranda
2022-02-04 14:52   ` Eli Zaretskii
2022-02-04 15:14     ` Mauro Aranda
2022-02-04 15:16       ` Eli Zaretskii
2022-02-04 15:45         ` Mauro Aranda [this message]
2022-02-04 16:42           ` Eli Zaretskii
2022-02-04 15:34   ` Stephen Berman
2022-02-04 15:49     ` Mauro Aranda
2022-02-04 15:49       ` Stephen Berman
2022-02-05  1:13     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-05  1:11   ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-05  1:14     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-05 15:33       ` Mauro Aranda
2022-02-05 15:38     ` Mauro Aranda
2022-02-05 12:56       ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-10 13:45         ` Mauro Aranda
2022-02-11  1:07           ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors

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='CABczVwc=aVWyTQoRdxMFo7SU9nc=b-rA6dUgz6fai5q5jDMEqA@mail.gmail.com' \
    --to=maurooaranda@gmail.com \
    --cc=53778@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    /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).