From: Eli Zaretskii <eliz@gnu.org>
To: Jean Louis <bugs@gnu.support>
Cc: 27816@debbugs.gnu.org
Subject: bug#27816: 26.0.50; X protocol error: BadPixmap (invalid Pixmap parameter) on protocol request 55
Date: Thu, 27 Jul 2017 20:18:00 +0300 [thread overview]
Message-ID: <83vamd4x4n.fsf@gnu.org> (raw)
In-Reply-To: <20170727073827.GA17695@protected.rcdrun.com> (message from Jean Louis on Thu, 27 Jul 2017 10:38:27 +0300)
> Date: Thu, 27 Jul 2017 10:38:27 +0300
> From: Jean Louis <bugs@gnu.support>
> Cc: 27816@debbugs.gnu.org
>
> I am starting Emacs through screen, without X windows. So I started as:
>
> gdb screen
>
> then I do:
>
> breakpoint x_error_quitter
>
> It asks me for future loaded libraries, I said y.
>
> Then I "run" and get screen and bash.
>
> Then I start emacs as
>
> emacs --user admin --chdir /home/data1/protected (that is my home dir)
No, I think this is a mistake. You should first start screen, then
start GDB from that like this:
gdb emacs
Then when GDB shows its prompt, type
(gdb) break x_error_quitter
(gdb) run --user admin --chdir /home/data1/protected
(The "(gdb)" part is the GDB prompt, you don't need to type it.)
And then continue as you usually would:
> And then I connect to emacs as emacsclient
>
> and evaluate (x-synchronize t)
>
> and then if I connect each 4th or 5th time, not clearly known why,
> then I get that bug, and X frame of new emacsclient is not appearing.
>
> But back in debugger I do not see much, emacs as server is still
> running.
If you start Emacs as above, you should see GDB take control when the
problem happens. Then type
(gdb) thread apply all bt
and post here everything it displays.
next prev parent reply other threads:[~2017-07-27 17:18 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-25 6:20 bug#27816: 26.0.50; X protocol error: BadPixmap (invalid Pixmap parameter) on protocol request 55 Jean Louis
2017-07-25 14:31 ` Eli Zaretskii
2017-07-25 17:48 ` Jean Louis
2017-07-25 18:33 ` Eli Zaretskii
2017-07-26 5:25 ` Jean Louis
2017-07-26 14:46 ` Eli Zaretskii
2017-07-27 7:09 ` Jean Louis
2017-07-27 7:38 ` Jean Louis
2017-07-27 17:18 ` Eli Zaretskii [this message]
2017-07-27 19:25 ` Jean Louis
2017-07-27 19:31 ` Eli Zaretskii
2017-07-27 20:31 ` Jean Louis
2017-07-27 19:30 ` Jean Louis
2017-07-28 7:09 ` Eli Zaretskii
2017-07-28 8:28 ` Jean Louis
2017-07-28 8:42 ` Eli Zaretskii
2017-07-28 8:47 ` Eli Zaretskii
2017-07-28 21:23 ` Jean Louis
2017-07-28 23:17 ` Jean Louis
2017-07-28 23:31 ` Jean Louis
2017-07-29 6:29 ` Eli Zaretskii
2017-07-29 7:31 ` Jean Louis
2017-07-29 7:41 ` Jean Louis
2017-07-29 7:46 ` Jean Louis
2017-08-02 16:12 ` Jean Louis
2017-08-02 18:51 ` Eli Zaretskii
2017-08-02 19:31 ` Jean Louis
2017-08-03 3:25 ` Eli Zaretskii
2017-08-03 4:59 ` Jean Louis
2017-08-03 16:09 ` Eli Zaretskii
2017-08-03 9:04 ` martin rudalics
2017-08-03 16:25 ` Eli Zaretskii
2017-08-03 16:44 ` Glenn Morris
2017-08-03 17:56 ` martin rudalics
2017-08-03 18:35 ` Eli Zaretskii
2017-08-04 8:54 ` martin rudalics
2017-08-04 9:51 ` Eli Zaretskii
2017-08-04 8:54 ` martin rudalics
2017-08-04 9:50 ` Eli Zaretskii
2017-08-05 12:46 ` martin rudalics
2017-08-05 12:56 ` Eli Zaretskii
2017-08-06 9:13 ` martin rudalics
2017-08-05 17:56 ` Jean Louis
2017-08-05 18:43 ` npostavs
2017-08-05 20:12 ` npostavs
2017-08-06 9:13 ` martin rudalics
2017-08-06 9:34 ` martin rudalics
2017-08-06 16:51 ` Eli Zaretskii
2017-09-01 22:34 ` Jean Louis
2017-09-02 6:30 ` martin rudalics
2017-09-02 7:06 ` Jean Louis
2017-09-03 10:13 ` martin rudalics
2018-07-16 22:22 ` Noam Postavsky
2017-09-03 10:14 ` martin rudalics
2017-08-06 13:33 ` npostavs
2017-08-06 9:12 ` martin rudalics
2017-08-30 8:31 ` martin rudalics
2017-08-30 10:52 ` npostavs
2017-09-03 10:14 ` martin rudalics
2017-09-03 15:47 ` Noam Postavsky
2017-09-03 17:30 ` martin rudalics
2017-08-06 9:12 ` martin rudalics
2017-08-02 22:04 ` Jean Louis
2017-08-02 22:47 ` Jean Louis
2017-08-02 23:33 ` Jean Louis
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=83vamd4x4n.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=27816@debbugs.gnu.org \
--cc=bugs@gnu.support \
/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).