openSUSE 12.3 or 13.1 MilestoneをGNOME環境で使われている方に質問があります。 gnome-shellが時々coreを吐きませんか?
Windows 7 64 bitマシンにVirtualBox 4.2.14 r86644を入れ、 その上にopenSUSE 12.3 と 13.1 Milestone 2 x64を入れています。
知らない内にcore fileが生成されています。 特に使い勝手が悪くなることは無いのですが、 SEGVですし、気持ちが悪いです。
Bugzillaに報告しようかと思うのですが、 皆さんの環境で、このような現象は起きていないでしょうか?
GNU gdb (GDB) SUSE (7.5.1-2.1.1) Copyright (C) 2012 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-suse-linux". For bug reporting instructions, please see: http://www.gnu.org/software/gdb/bugs/... Reading symbols from /usr/bin/gnome-shell...Reading symbols from /usr/lib/debug/usr/bin/gnome-shell.debug...done. done. [New LWP 2804] [New LWP 2842] [New LWP 2840] [New LWP 2820] [New LWP 2823] [New LWP 2816] [New LWP 2817] [New LWP 2824] [New LWP 2811] [New LWP 2822] [New LWP 2818] [New LWP 2815] [New LWP 2821] [New LWP 2819] [New LWP 2814] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". Core was generated by `gnome-shell --mode=gdm'. Program terminated with signal 11, Segmentation fault. #0 0x00007f890524db20 in tbl_B15 () from /usr/lib64/dri/swrast_dri.so (gdb) bt full #0 0x00007f890524db20 in tbl_B15 () from /usr/lib64/dri/swrast_dri.so No symbol table info available. #1 <signal handler called> No locals. #2 0x00007f8916a3687d in poll () at ../sysdeps/unix/syscall-template.S:81 No locals. #3 0x00007f8916f6aaa4 in g_main_context_poll (n_fds=11, fds=0x354c5a0, timeout=54, context=0x23a4d50, priority=<optimized out>) at gmain.c:3584 poll_func = 0x7f8916f78b50 <g_poll> #4 g_main_context_iterate (context=0x23a4d50, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3285 max_priority = 2147483647 timeout = 54 some_ready = <optimized out> nfds = 11 allocated_nfds = <optimized out> fds = 0x354c5a0 #5 0x00007f8916f6af02 in g_main_loop_run (loop=0x23aa3e0) at gmain.c:3484 __PRETTY_FUNCTION__ = "g_main_loop_run" #6 0x00007f8918ad3167 in meta_run () at core/main.c:545 log_domains = {0x0, 0x7f8918b19657 "mutter", 0x7f8918b189e2 "Gtk", 0x7f8918b189e6 "Gdk", 0x7f8918b189ea "GLib", 0x7f8918b189ef "Pango", 0x7f8918b189f5 "GLib-GObject", 0x7f8918b18a02 "GThread"} i = <optimized out> #7 0x0000000000401c3c in main (argc=1, argv=0x7fffc0afe6a8) at main.c:416 ctx = <optimized out> error = 0x0 ecode = <optimized out> sender = 0x27ad920 [TpDebugSender] (gdb) bt full #0 0x00007f890524db20 in tbl_B15 () from /usr/lib64/dri/swrast_dri.so No symbol table info available. #1 <signal handler called> No locals. #2 0x00007f8916a3687d in poll () at ../sysdeps/unix/syscall-template.S:81 No locals. #3 0x00007f8916f6aaa4 in g_main_context_poll (n_fds=11, fds=0x354c5a0, timeout=54, context=0x23a4d50, priority=<optimized out>) at gmain.c:3584 poll_func = 0x7f8916f78b50 <g_poll> #4 g_main_context_iterate (context=0x23a4d50, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3285 max_priority = 2147483647 timeout = 54 some_ready = <optimized out> nfds = 11 allocated_nfds = <optimized out> fds = 0x354c5a0 #5 0x00007f8916f6af02 in g_main_loop_run (loop=0x23aa3e0) at gmain.c:3484 __PRETTY_FUNCTION__ = "g_main_loop_run" #6 0x00007f8918ad3167 in meta_run () at core/main.c:545 log_domains = {0x0, 0x7f8918b19657 "mutter", 0x7f8918b189e2 "Gtk", 0x7f8918b189e6 "Gdk", 0x7f8918b189ea "GLib", 0x7f8918b189ef "Pango", 0x7f8918b189f5 "GLib-GObject", 0x7f8918b18a02 "GThread"} i = <optimized out> #7 0x0000000000401c3c in main (argc=1, argv=0x7fffc0afe6a8) at main.c:416 ctx = <optimized out> error = 0x0 ecode = <optimized out> sender = 0x27ad920 [TpDebugSender] (gdb) bt full #0 0x00007f890524db20 in tbl_B15 () from /usr/lib64/dri/swrast_dri.so No symbol table info available. #1 <signal handler called> No locals. #2 0x00007f8916a3687d in poll () at ../sysdeps/unix/syscall-template.S:81 No locals. #3 0x00007f8916f6aaa4 in g_main_context_poll (n_fds=11, fds=0x354c5a0, timeout=54, context=0x23a4d50, priority=<optimized out>) at gmain.c:3584 poll_func = 0x7f8916f78b50 <g_poll> #4 g_main_context_iterate (context=0x23a4d50, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3285 max_priority = 2147483647 timeout = 54 some_ready = <optimized out> nfds = 11 allocated_nfds = <optimized out> fds = 0x354c5a0 #5 0x00007f8916f6af02 in g_main_loop_run (loop=0x23aa3e0) at gmain.c:3484 __PRETTY_FUNCTION__ = "g_main_loop_run" #6 0x00007f8918ad3167 in meta_run () at core/main.c:545 log_domains = {0x0, 0x7f8918b19657 "mutter", 0x7f8918b189e2 "Gtk", 0x7f8918b189e6 "Gdk", 0x7f8918b189ea "GLib", 0x7f8918b189ef "Pango", 0x7f8918b189f5 "GLib-GObject", 0x7f8918b18a02 "GThread"} i = <optimized out> #7 0x0000000000401c3c in main (argc=1, argv=0x7fffc0afe6a8) at main.c:416 ctx = <optimized out> error = 0x0 ecode = <optimized out> sender = 0x27ad920 [TpDebugSender] (gdb)
ls -lt /var/crash total 1420960 -rw------- 1 gdm gdm 223875072 Jun 29 16:52 core.gnome-shell.489.1372492328 -rw------- 1 gdm gdm 242270208 Jun 27 17:50 core.gnome-shell.489.1372323033 -rw------- 1 gdm gdm 220360704 Jun 15 23:03 core.gnome-shell.489.1371304985 -rw------- 1 gdm gdm 226242560 Jun 15 22:40 core.gnome-shell.489.1371303625 -rw------- 1 gdm gdm 226353152 Jun 15 22:39 core.gnome-shell.489.1371303586 -rw------- 1 gdm gdm 234512384 Jun 15 22:14 core.gnome-shell.489.1371302052 -rw------- 1 mitsutoshi users 30289920 Jun 5 21:37 core.nm-applet.1000.1370435876 -rw------- 1 gdm gdm 241950720 Jun 2 11:33 core.gnome-shell.489.1370140394 -rw------- 1 gdm gdm 223588352 Jun 2 00:02 core.gnome-shell.489.1370098969 -rw------- 1 mitsutoshi users 393510912 May 16 20:53 core.gdbus.1000.1368705191 -rw------- 1 mitsutoshi users 27455488 May 15 16:41 core.eekboard.1000.1368603683 -rw------- 1 mitsutoshi users 287191040 May 15 16:31 core.gnome-shell.1000.1368603100 -rw------- 1 mitsutoshi users 22900736 May 15 16:20 core.eekboard.1000.1368602439 -rw------- 1 mitsutoshi users 22548480 May 14 21:03 core.eekboard.1000.1368533011 -rw------- 1 mitsutoshi users 27627520 May 7 21:36 core.eekboard.1000.1367930185 -rw------- 1 mitsutoshi users 33288192 May 7 21:22 core.eekboard-server.1000.1367929366 -rw------- 1 mitsutoshi users 30064640 May 7 20:34 core.eekboard.1000.1367926457 -rw------- 1 gdm gdm 225914880 Apr 26 23:25 core.gnome-shell.489.1366986331 -rw------- 1 mitsutoshi users 11059200 Apr 26 23:22 core.xfce4-power-man.1000.1366986176 -rw------- 1 mitsutoshi users 21909504 Apr 6 17:45 core.eekboard.1000.1365237913 -rw------- 1 mitsutoshi users 34140160 Apr 1 19:31 core.nm-applet.1000.1364812312 -rw------- 1 gdm gdm 158547968 Mar 22 13:52 core.gnome-shell.489.1363927934 -rw------- 1 gdm gdm 175452160 Mar 22 13:31 core.gnome-shell.489.1363926685 -rw------- 1 gdm gdm 153104384 Mar 21 20:21 core.gnome-shell.489.1363864911
-- 1xx ItSANgo@gmail.com https://twitter.com/ItSANgo http://d.hatena.ne.jp/Itisango/
2013/6/30 1xx itsango@gmail.com:
GNU gdb (GDB) SUSE (7.5.1-2.1.1)
コピーペーストをミスって間違ったbacktraceを送信しておりました。
正しくはこちらです。 https://bugzilla.novell.com/show_bug.cgi?id=827522#c1
というわけでBugzillaに報告しておきました。
-- 1xx ItSANgo@gmail.com https://twitter.com/ItSANgo http://d.hatena.ne.jp/Itisango/
2013/6/30 1xx itsango@gmail.com:
openSUSE 12.3 or 13.1 MilestoneをGNOME環境で使われている方に質問があります。 gnome-shellが時々coreを吐きませんか?
gdmからloginするときに必ずSEGVを起こすことに気付きました。 Bugzillaに報告しておきます。
皆さんの環境で、このような現象は起きていないでしょうか?
-- 1xx ItSANgo@gmail.com https://twitter.com/ItSANgo http://d.hatena.ne.jp/Itisango/