search

sebastiencs / company-box

A company front-end with icons
563 stars 64 forks source link

Company Box crashes EMACS on first display #191

Closed anoduck closed 1 year ago

anoduck commented 1 year ago

It has taken me two weeks to figure out what has been happening to my EMACS installation. This package is so cool, I didn't even want to consider it as a culprit. Unfortunately, once disabled, I realized my life was over as I knew it... :( The love was lost...

The problem has been very little output to inform what has been happening, this was what I received when I ran emacs-gtk3 from the terminal:

Backtrace:
0x8b1c7d0ebd7 <XSetWMNormalHints+0x30397> at emacs
0x8b1c7cf0058 <XSetWMNormalHints+0x11818> at emacs
0x8b1c7d103fe <XSetWMNormalHints+0x31bbe> at emacs
0x8b1c7d10482 <XSetWMNormalHints+0x31c42> at emacs
0x8b1c7d0e8b9 <XSetWMNormalHints+0x30079> at emacs
[1]    25779 segmentation fault (core dumped)  emacs

The XSetWMNormalHints was the big tip off that something funky was going with rendering. When I opened gdb to attempt to further gather information, EMACS crashed on this frame:

0xdc1d452f3a <thrkill+10>               jb     0xdc1d452f3d <thrkill+13>

Retrieving info from the frame, landed me with this.

Stack level 0, frame at 0xd9a79d5ab0:
 rip = 0xdc1d452f3a in thrkill (/tmp/-:3); saved rip = 0xd9a74d6085
 called by frame at 0xd9a79d5ae0
 source language asm.
 Arglist at 0xd9a79d5aa0, args:
 Locals at 0xd9a79d5aa0, Previous frame's sp is 0xd9a79d5ab0
 Saved registers:
  rip at 0xd9a79d5aa8

I am completely out of my comfort zone working with gdb, since I have little to no experience with C++, but am learning what I can. RS does provide a nice manual for it.

anoduck commented 1 year ago

Nope, it is not company box... must be something else.