all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Andres MM <carlos.mariscal.melgar@gmail.com>
Cc: 31249@debbugs.gnu.org
Subject: bug#31249: 27.0.50; Emacs crash, running in Ubuntu:xenial docker with x11 forwarding to windows
Date: Tue, 24 Apr 2018 20:03:02 +0300	[thread overview]
Message-ID: <834lk0wn95.fsf@gnu.org> (raw)
In-Reply-To: <CAB-zfNR8fFG+Hkijkbvyb36pAmaLXKQqQ2djiE394OFRrtiQ5g@mail.gmail.com> (message from Andres MM on Tue, 24 Apr 2018 11:31:54 +0300)

> From: Andres MM <carlos.mariscal.melgar@gmail.com>
> Date: Tue, 24 Apr 2018 11:31:54 +0300
> 
> Backtrace:
> emacs[0x50f469]
> emacs[0x4f5877]
> emacs[0x50de1e]
> emacs[0x50e123]
> emacs[0x50e160]
> /lib/x86_64-linux-gnu/libpthread.so.0(+0x11390)[0x7fe1481e8390]
> emacs[0x58e595]
> emacs[0x58e90f]
> emacs[0x56c4f6]
> emacs[0x5a8418]
> emacs[0x56c453]
> emacs[0x5a8418]
> emacs[0x56c053]
> emacs[0x56c453]
> emacs[0x5a8418]
> emacs[0x56c053]
> emacs[0x56c453]
> emacs[0x5a8418]
> emacs[0x56c053]
> emacs[0x56c453]
> emacs[0x5a8418]
> emacs[0x56c053]
> emacs[0x56c453]
> emacs[0x5a8418]
> emacs[0x56c053]
> emacs[0x56c453]
> emacs[0x56e1d3]
> emacs[0x56c4f6]
> emacs[0x5a8418]
> emacs[0x56c453]
> emacs[0x5a8418]
> emacs[0x56c053]
> emacs[0x56c453]
> emacs[0x56e0ac]
> emacs[0x56c4f6]
> emacs[0x5a8418]
> emacs[0x56c453]
> emacs[0x5a8418]
> emacs[0x56c053]
> emacs[0x56c453]
> emacs[0x56e1d3]
> ...
> 
> #----Additional Information ----#
> 
> https://github.com/SerialDev/tiqsi-emacs
> 
> Generate the docker file using the UI by providing your IP for Display
> env export.
> Remove Pragmata pro from dockerfile since it is not in the repo
> (personal use font)
> 
> With this image it should be able to replicate without failure on this
> commit:
> 882d7ee34f193ee0581429f0a1ea71f93fe097c0

Thanks, but please try producing a human-readable backtrace from the
crash using the technique described in the node "Crashing" of the
Emacs user manual.

Alternatively, if there's a core file left by the crash, you could run
GDB on the core file and produce a backtrace from there.





      reply	other threads:[~2018-04-24 17:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-24  8:31 bug#31249: 27.0.50; Emacs crash, running in Ubuntu:xenial docker with x11 forwarding to windows Andres MM
2018-04-24 17:03 ` Eli Zaretskii [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=834lk0wn95.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=31249@debbugs.gnu.org \
    --cc=carlos.mariscal.melgar@gmail.com \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.