深度终端崩溃了,我也崩溃了
Tofloor
poster avatar
ryanorz
deepin
2017-05-23 00:38
Author
OS: Deepin 15.04
深度终端使用过程中崩溃了,之前也有发生过,只不过频率很低,但今天正远程更新其他系统呢,然后瞬间有种哔了狗的赶脚。。。。以前也用深度自带的软件反馈过一些问题,但是从没发现给我回过邮件,不知道我发的反馈有没有人处理。发现论坛上处理问题速度快,就把问题也在论坛上发下。deepin-feedback-cli-Deepin-15.4-all-20170522-162720.tar.gz


Reply Favorite View the author
All Replies
1 / 3
To page
avatar
wangyong
deepin
2017-05-23 04:25
#1
用别的终端启动深度终端,步骤如下:
1、gdb deepin-terminal
2、深度终端失败以后,在gdb里面键入 bt 然后回车
3、把崩溃的堆栈粘贴到论坛

我一看堆栈我就知道怎么处理了

最近没改代码啊,为啥两个人都报崩溃的问题?(我天天也在用)
Reply View the author
avatar
153******66
deepin
2017-05-24 01:55
#2
https://bbs.deepin.org/post/139837
用别的终端启动深度终端,步骤如下:
1、gdb deepin-terminal
2、深度终端失败以后,在gdb里面键入 bt 然后 ...

我今天也崩溃了3次. 每次都是我在编译东西的时候. 疯了.  我没有其他终端.  (摊手
Reply View the author
avatar
wangyong
deepin
2017-05-24 02:29
#3
eleveni386 发表于 2017-5-23 17:55
我今天也崩溃了3次. 每次都是我在编译东西的时候. 疯了.  我没有其他终端.  (摊手 ...

按照我上面的方式,深度终端套深度终端,里面的深度终端挂了,粘贴一下错误堆栈
Reply View the author
avatar
153******66
deepin
2017-05-24 02:34
#4
https://bbs.deepin.org/post/139837
按照我上面的方式,深度终端套深度终端,里面的深度终端挂了,粘贴一下错误堆栈 ...

偶然现象, 比如我现在又编译了50多分钟... 却在没有崩溃.. 我感觉我需要一直开着gdb来跑. 一直等到崩溃出来的那一刻. 明天从早开到晚 gdb.  今天没时间了. 下班
Reply View the author
avatar
ryanorz
deepin
2017-05-24 02:54
#5
https://bbs.deepin.org/post/139837
我今天也崩溃了3次. 每次都是我在编译东西的时候. 疯了.  我没有其他终端.  (摊手 ...

我安装了个konsole,在gdb挂着呢,一天了都没崩溃
Reply View the author
avatar
snyh1010
deepin
2017-05-24 04:35
#6
..... 安装下sudo apt-get install  systemd-coredump

然后如果出现崩溃的现象后, 直接 ``` coredumpctl gdb deepin-terminal```  然后bt 输出stack就行了.
Reply View the author
avatar
153******66
deepin
2017-06-01 22:23
#7
https://bbs.deepin.org/post/139837
按照我上面的方式,深度终端套深度终端,里面的深度终端挂了,粘贴一下错误堆栈 ...

➜  ~ coredumpctl gdb deepin-terminal
           PID: 19088 (deepin-terminal)
           UID: 1000 (eleven220)
           GID: 1000 (eleven220)
        Signal: 11 (SEGV)
     Timestamp: Thu 2017-06-01 14:21:46 CST (1min 11s ago)
  Command Line: deepin-terminal
    Executable: /usr/bin/deepin-terminal
Control Group: /user.slice/user-1000.slice/session-2.scope
          Unit: session-2.scope
         Slice: user-1000.slice
       Session: 2
     Owner UID: 1000 (eleven220)
       Boot ID: 1bb142deb7a147f081f2d0902db6fcf6
    Machine ID: 7c1ef2230f334fbf85d1fb1dc74cecf4
      Hostname: eleven220-pc
      Coredump: /var/lib/systemd/coredump/core.deepin-terminal.1000.1bb142deb7a147f081f2d0902db6fcf6.19088.1496298106000000000000.xz
       Message: Process 19088 (deepin-terminal) of user 1000 dumped core.
               
                Stack trace of thread 19088:
                #0  0x00007efd9d456446 gtk_widget_get_mapped (libgtk-3.so.0)
                #1  0x00007efd9d38df99 n/a (libgtk-3.so.0)
                #2  0x00007efd9d38e0b0 n/a (libgtk-3.so.0)
                #3  0x00007efd9d38e194 n/a (libgtk-3.so.0)
                #4  0x00007efd9b17fd33 n/a (libglib-2.0.so.0)
                #5  0x00007efd9b17f2fa g_main_context_dispatch (libglib-2.0.so.0)
                #6  0x00007efd9b17f678 n/a (libglib-2.0.so.0)
                #7  0x00007efd9b17f992 g_main_loop_run (libglib-2.0.so.0)
                #8  0x00007efd9d304805 gtk_main (libgtk-3.so.0)
                #9  0x00005614c344b736 application_main (deepin-terminal)
                #10 0x00005614c33ec0d0 main (deepin-terminal)
                #11 0x00007efd996d02b1 __libc_start_main (libc.so.6)
                #12 0x00005614c33ec10a _start (deepin-terminal)
               
                Stack trace of thread 19091:
                #0  0x00007efd9978f56d __poll (libc.so.6)
                #1  0x00007efd9b17f616 n/a (libglib-2.0.so.0)
                #2  0x00007efd9b17f992 g_main_loop_run (libglib-2.0.so.0)
                #3  0x00007efd9dcff236 n/a (libgio-2.0.so.0)
                #4  0x00007efd9b1a6095 n/a (libglib-2.0.so.0)
                #5  0x00007efd96fab464 start_thread (libpthread.so.0)
                #6  0x00007efd997989df __clone (libc.so.6)
               
                Stack trace of thread 19089:
                #0  0x00007efd9978f56d __poll (libc.so.6)
                #1  0x00007efd9b17f616 n/a (libglib-2.0.so.0)
                #2  0x00007efd9b17f71c g_main_context_iteration (libglib-2.0.so.0)
                #3  0x00007efd9b17f761 n/a (libglib-2.0.so.0)
                #4  0x00007efd9b1a6095 n/a (libglib-2.0.so.0)
                #5  0x00007efd96fab464 start_thread (libpthread.so.0)
                #6  0x00007efd997989df __clone (libc.so.6)
               
                Stack trace of thread 20563:
                #0  0x00007efd99794119 syscall (libc.so.6)
                #1  0x00007efd9b1c35c4 g_cond_wait_until (libglib-2.0.so.0)
                #2  0x00007efd9b154b29 n/a (libglib-2.0.so.0)
                #3  0x00007efd9b15511c g_async_queue_timeout_pop (libglib-2.0.so.0)
                #4  0x00007efd9b1a6b3d n/a (libglib-2.0.so.0)
                #5  0x00007efd9b1a6095 n/a (libglib-2.0.so.0)
                #6  0x00007efd96fab464 start_thread (libpthread.so.0)
                #7  0x00007efd997989df __clone (libc.so.6)

  GNU gdb (Debian 7.11.1-2) 7.11.1
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/bin/deepin-terminal...(no debugging symbols found)...done.
[New LWP 19088]
[New LWP 19091]
[New LWP 19089]
[New LWP 20563]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `deepin-terminal'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x00007efd9d456446 in gtk_widget_get_mapped () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
[Current thread is 1 (Thread 0x7efd9e114a80 (LWP 19088))]
Reply View the author
avatar
153******66
deepin
2017-06-01 22:24
#8
https://bbs.deepin.org/post/139837
按照我上面的方式,深度终端套深度终端,里面的深度终端挂了,粘贴一下错误堆栈 ...

刚才漏掉了 堆栈信息

#0  0x00007efd9d456446 in gtk_widget_get_mapped () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#1  0x00007efd9d38df99 in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#2  0x00007efd9d38e0b0 in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#3  0x00007efd9d38e194 in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#4  0x00007efd9b17fd33 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007efd9b17f2fa in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x00007efd9b17f678 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#7  0x00007efd9b17f992 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#8  0x00007efd9d304805 in gtk_main () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#9  0x00005614c344b736 in application_main ()
#10 0x00005614c33ec0d0 in main ()
Reply View the author
Comments
snyh1010
2017-06-02 03:49
libgtk-3-0-dbg libglib2.0-0-dbg 这两个包装上  在用gdb看会多一些信息的.
avatar
wangyong
deepin
2017-06-01 23:19
#9
你的段错误到gtk的库里面去了,你最近折腾过系统的gtk+版本吗?
Reply View the author
avatar
nicot
deepin
2017-06-02 00:28
#10
我也崩溃过两次,有一次是在交叉编译内核的时候,编了一半,直接闪退了
Reply View the author
avatar
153******66
deepin
2017-06-02 03:01
#11
https://bbs.deepin.org/post/139837
你的段错误到gtk的库里面去了,你最近折腾过系统的gtk+版本吗?

显然没有, 选择使用Deepin 就是不再想去折腾这些东西了. 选择Deepin, 远离折腾,
Reply View the author
avatar
153******66
deepin
2017-06-02 03:02
#12
https://bbs.deepin.org/post/139837
我也崩溃过两次,有一次是在交叉编译内核的时候,编了一半,直接闪退了

我也好几次在交叉编译 崩溃.
Reply View the author
avatar
wangyong
deepin
2017-06-02 03:10
#13
eleveni386 发表于 2017-6-1 19:02
我也好几次在交叉编译 崩溃.

你们编译的环境写个重现步骤行吗?我自己实验一下
Reply View the author
avatar
leixiaozeng
deepin
2017-06-02 03:44
#14
好可怜
Reply View the author
avatar
153******66
deepin
2017-06-02 05:23
#15
https://bbs.deepin.org/post/139837
你们编译的环境写个重现步骤行吗?我自己实验一下

好几次交叉编译崩溃, 还有几次是打开remote manager panel 选择主机崩溃, 还有就是已经在远程主机上作业 突然崩溃, vim写代码, 写着写着 崩溃. 前提都是我开了好几个tab, 单tab还没遇到过崩溃情况(不过单tab也用的少),
我的编译openwrt的步骤如下链接
https://github.com/liudf0716/apf ... AF%91Apfree_wifidog
Reply View the author
avatar
153******66
deepin
2017-06-02 05:26
#16
https://bbs.deepin.org/user/33235 另外 我给你看看我gtk版本.
Reply View the author
avatar
wangyong
deepin
2017-06-02 05:50
#17
https://bbs.deepin.org/post/139837
好几次交叉编译崩溃, 还有几次是打开remote manager panel 选择主机崩溃, 还有就是已经在远程主机上作业  ...

编译这个必挂?
Reply View the author
avatar
153******66
deepin
2017-06-02 07:28
#18

这个要看脸!! 脸白 就没事. 不然我怎么编译好的... 脸黑 就接连挂掉.
Reply View the author
avatar
wangyong
deepin
2017-06-02 07:48
#19
https://bbs.deepin.org/post/139837
这个要看脸!! 脸白 就没事. 不然我怎么编译好的... 脸黑 就接连挂掉.

哎呀,说的我好尴尬啊。
Reply View the author
avatar
xh97
deepin
2017-06-02 07:49
#20
https://bbs.deepin.org/post/139837
用别的终端启动深度终端,步骤如下:
1、gdb deepin-terminal
2、深度终端失败以后,在gdb里面键入 bt 然后 ...

我也报一个。在学Linux命令,这昨天开始偶尔输入命令后终端没反应,只能关掉重开
Reply View the author
1 / 3
To page