Date: Mon, 3 Aug 2020 21:47:51 -0700 From: Kevin Oberman <rkoberman@gmail.com> To: Ashish SHUKLA <ashish@freebsd.org> Cc: Niclas Zeising <zeising+freebsd@daemonic.se>, "freebsd-x11@freebsd.org" <x11@freebsd.org>, emacs@freebsd.org Subject: Re: Recent libX11 update broke emacs Message-ID: <CAN6yY1tSjZT4vnuiU46ijCXHSk15ikMOUiAHaY2UbcWagP7sXw@mail.gmail.com> In-Reply-To: <808fd843-cf7d-f427-f2c5-bf75765b03ae@FreeBSD.org> References: <CAN6yY1sOsGd5YdjAMdO01opmDvV8LRcqPQUg3gze5yu0XOKShQ@mail.gmail.com> <3fd8de9f-5746-1216-6047-af576d851b1a@daemonic.se> <CAN6yY1sUeG-aCwq4yfwhXzf=aSq5hrOCXW_WhN8dYKFZ1=hA_Q@mail.gmail.com> <808fd843-cf7d-f427-f2c5-bf75765b03ae@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Aug 3, 2020 at 9:37 PM Ashish SHUKLA <ashish@freebsd.org> wrote: > On 8/4/20 9:56 AM, Kevin Oberman wrote: > > On Mon, Aug 3, 2020 at 3:09 PM Niclas Zeising > > <zeising+freebsd@daemonic.se <mailto:zeising%2Bfreebsd@daemonic.se>> > wrote: > > > > On 2020-08-03 19:07, Kevin Oberman wrote: > > > This is a weird problem and I'm uncertain if it is in libW11, > > x11-server, > > > or emacs. As a result, I'm crossposting to both lists. > > > > > > Yesterday, after upgrading libX11 and x11-server, I could no > > longer run > > > Emacs to an X display. It crashed quickly with a segmentation > > error in the > > > pthread library. Oddly, I could run it to my local xserver from a > > remote > > > system. > > > > Where does the segfault occur before entering pthreads? > > > > Here is a backtrace with symbols: > > * thread #1, name = 'emacs-28.0.50', stop reason = signal SIGSEGV > > * frame #0: 0x000000002dc8584a > > frame #1: 0x000000002dc83ca4 > > frame #2: 0x0000000000374fc0 > > emacs`detect_coding_utf_16(coding=0x00000000f2ee705a, > > detect_info=0x0000000009d690dc) at coding.c:0:4 > > frame #3: 0x000000000039584e > > emacs`encode_invocation_designation(charset=0x000000000039584e, > > coding=0x000000000083da20, dst="", p_nchars=0x000000000000000b) at > > coding.c:4273:15 > > frame #4: 0x00000000003958c3 > > emacs`encode_invocation_designation(charset=0x000000000083e230, > > coding=0x0000000000000000, dst="", p_nchars=0x000000000083da40) at > > coding.c:4280:4 > > frame #5: 0x0000000000393df9 > > emacs`coding_alloc_by_realloc(coding=0x0000000000393df9, bytes=8641104) > > at coding.c:1012:7 > > frame #6: 0x0000000000395906 > > emacs`encode_invocation_designation(charset=0x000000000083dec0, > > coding=0x000000000083de40, dst="", p_nchars=0x000000000083da70) at > > coding.c:4285:6 > > thread #2, name = 'emacs-28.0.50', stop reason = signal SIGSEGV > > frame #0: 0x000000002dc2beda > > frame #1: 0x000000002c929a26 > > thread #3, name = 'emacs-28.0.50', stop reason = signal SIGSEGV > > frame #0: 0x000000002dc2beda > > frame #1: 0x000000002c929a26 > > thread #4, name = 'emacs-28.0.50', stop reason = signal SIGSEGV > > frame #0: 0x000000002dc2beda > > frame #1: 0x000000002c929a26 > > Thanks for the providing the information. > > Is the above backtrace with `emacs', or `emacs -Q' ? If former, then > could you see if latter segfaults as well ? > Thanks! > -- > Ashish SHUKLA | GPG: F682CDCC39DC0FEAE11620B6C746CFA9E74FA4B0 > emacs-Q? Emacs with qt? It's stock emacs.Default build options. I've tried both emacs and emacs-devel and seen no difference. > -- > Kevin Oberman, Part time kid herder and retired Network Engineer > E-mail: rkoberman@gmail.com > PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 > > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAN6yY1tSjZT4vnuiU46ijCXHSk15ikMOUiAHaY2UbcWagP7sXw>