El vie, 4 feb 2022 a las 11:52, Eli Zaretskii (<eliz@gnu.org>) escribió:
>> From: Mauro Aranda <maurooaranda@gmail.com>
>> Date: Fri, 4 Feb 2022 11:38:46 -0300
>>
>> After commit b944841173... I can't start GUI Emacs.
>>
>> I did:
>> ./configure && make
>>
>> And when I start Emacs with "emacs -Q" I get:
>> X protocol error: RenderBadPicture (invalid Picture parameter) on
protocol request 138
>> When compiled with GTK, Emacs cannot recover from X disconnects.
>> This is a GTK bug: https://gitlab.gnome.org/GNOME/gtk/issues/221
>> For details, see etc/PROBLEMS.
>> Backtrace:
>> ./src/emacs(emacs_backtrace+0x41)[0x81bc731]
>> ./src/emacs(terminate_due_to_signal+0x7f)[0x809958c]
>> ./src/emacs[0x8099abd]
>> ./src/emacs[0x8098b20]

> We need you to start Emacs under GDB, passing Emacs the command-line
> option '-xrm "emacs.synchronous: true"', and then show the backtrace
> inside GDB.  That should produce a much more useful backtrace than the
> one you posted.

I know, but...

> Why are you unable to run GDB?

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.

I have never run into this problem before.