Giters

martanne / dvtm

dvtm brings the concept of tiling window management, popularized by X11-window managers like dwm to the console. As a console window manager it tries to make it easy to work with multiple console based programs.

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Crash in put_wc

MarSoft opened this issue · comments

commented

Another sporadic crash. Last time it happened when I ran git diff in one of the active windows, but I don't know what could cause that.

Core dump info:

           PID: 2177 (dvtm)
           UID: 1000 (mars)
           GID: 1000 (mars)
        Signal: 11 (SEGV)
     Timestamp: Tue 2017-11-14 17:24:04 MSK (6min ago)
  Command Line: dvtm -d 10 -h 5000 -c /run/user/1000/dvtm-session-cmd-2168.fifo -s /run/user/1000/dvtm-session-status-2168.fifo
    Executable: /usr/bin/dvtm
 Control Group: /user.slice/user-1000.slice/session-c2.scope
          Unit: session-c2.scope
         Slice: user-1000.slice
       Session: c2
     Owner UID: 1000 (mars)
       Boot ID: 4c2eea29941a40f7b7deba554b1a2fd3
    Machine ID: e05da9ccd03d465a8b5ecee7a9103251
      Hostname: hpook
       Storage: /var/lib/systemd/coredump/core.dvtm.1000.4c2eea29941a40f7b7deba554b1a2fd3.2177.1510669444000000.lz4
       Message: Process 2177 (dvtm) of user 1000 dumped core.
                
                Stack trace of thread 2177:
                #0  0x000056181865e7bb put_wc (dvtm)
                #1  0x0000561818658a85 main (dvtm)
                #2  0x00007ffa6163ff6a __libc_start_main (libc.so.6)
                #3  0x00005618186592fa _start (dvtm)

Tried to debug it with gdb and found that the problem happened in dvtm/vt.c line 1393, and that b->curs_row->cells was 0x2000000000 which is obviously not the correct memory address.

$ dvtm -v
dvtm-v0.15-37-gb45828d-dirty © 2007-2016 Marc André Tanner
commented

Core dump info:

How did you get the core dump info?