Bug#397412: wmaker: Wmaker crash on creating desktop
On Tue, 05 Dec 2006, jamhed wrote: Well, it worked for me, and seemingly for most other people. I'm not sure what makes your configuration special, though :-) I was suspecting my 'special config', because of upgrade, so I've installed fresh etch on another clean machine, it crashed there too. That makes me think there is something wrong. It was netinst from this mirror: http://ftp.kulnet.kuleuven.ac.be/debian I could reproduce the bug. It's locale-dependent. Using ru_RU.KOI8-R or ru_RU.UTF-8 allowed me to reproduce the bug. How to reproduce: - dpkg-reconfigure locales and activate ru_RU.KOI8-R - if you never used windowmaker start it in your current locale and create a second desktop (I don't understand russian) this is done with right click on the desktop and then follow the menu Workspace/Workspaces/New - kill wmaker and restart it with: $ export LC_ALL=ru_RU.KOI8-R $ wmaker (I also unset the various other LANG* env variables just for safety) Valgrind didn't give any useful information because /usr/bin/wmaker is just a shell script. Running it on WindowMaker gives something more interesting: $ LC_ALL=ru_RU.KOI8-R valgrind WindowMaker ==21367== Memcheck, a memory error detector. ==21367== Copyright (C) 2002-2006, and GNU GPL'd, by Julian Seward et al. ==21367== Using LibVEX rev 1658, a library for dynamic binary translation. ==21367== Copyright (C) 2004-2006, and GNU GPL'd, by OpenWorks LLP. ==21367== Using valgrind-3.2.1-Debian, a dynamic binary instrumentation framework. ==21367== Copyright (C) 2000-2006, and GNU GPL'd, by Julian Seward et al. ==21367== For more details, rerun with: -v ==21367== ==21367== Invalid read of size 4 ==21367==at 0x4010E00: (within /lib/ld-2.3.6.so) ==21367==by 0x4004B78: (within /lib/ld-2.3.6.so) ==21367==by 0x4006792: (within /lib/ld-2.3.6.so) ==21367==by 0x428A2AF: (within /lib/tls/i686/cmov/libc-2.3.6.so) ==21367==by 0x400B44E: (within /lib/ld-2.3.6.so) ==21367==by 0x4289D1E: _dl_open (in /lib/tls/i686/cmov/libc-2.3.6.so) ==21367==by 0x4186D8D: (within /lib/tls/i686/cmov/libdl-2.3.6.so) ==21367==by 0x400B44E: (within /lib/ld-2.3.6.so) ==21367==by 0x418742C: (within /lib/tls/i686/cmov/libdl-2.3.6.so) ==21367==by 0x4186D20: dlopen (in /lib/tls/i686/cmov/libdl-2.3.6.so) ==21367==by 0x40B3448: (within /usr/lib/libX11.so.6.2.0) ==21367==by 0x40B3756: _XNoticeCreateBitmap (in /usr/lib/libX11.so.6.2.0) ==21367== Address 0x44D8780 is 24 bytes inside a block of size 25 alloc'd ==21367==at 0x401D38B: malloc (vg_replace_malloc.c:149) ==21367==by 0x4006B83: (within /lib/ld-2.3.6.so) ==21367==by 0x428A2AF: (within /lib/tls/i686/cmov/libc-2.3.6.so) ==21367==by 0x400B44E: (within /lib/ld-2.3.6.so) ==21367==by 0x4289D1E: _dl_open (in /lib/tls/i686/cmov/libc-2.3.6.so) ==21367==by 0x4186D8D: (within /lib/tls/i686/cmov/libdl-2.3.6.so) ==21367==by 0x400B44E: (within /lib/ld-2.3.6.so) ==21367==by 0x418742C: (within /lib/tls/i686/cmov/libdl-2.3.6.so) ==21367==by 0x4186D20: dlopen (in /lib/tls/i686/cmov/libdl-2.3.6.so) ==21367==by 0x40B3448: (within /usr/lib/libX11.so.6.2.0) ==21367==by 0x40B3756: _XNoticeCreateBitmap (in /usr/lib/libX11.so.6.2.0) ==21367==by 0x40B3B3C: XCreatePixmap (in /usr/lib/libX11.so.6.2.0) ==21367== ==21367== Conditional jump or move depends on uninitialised value(s) ==21367==at 0x4008ED5: (within /lib/ld-2.3.6.so) ==21367==by 0x428A704: (within /lib/tls/i686/cmov/libc-2.3.6.so) ==21367==by 0x400B44E: (within /lib/ld-2.3.6.so) ==21367==by 0x4289D1E: _dl_open (in /lib/tls/i686/cmov/libc-2.3.6.so) ==21367==by 0x4186D8D: (within /lib/tls/i686/cmov/libdl-2.3.6.so) ==21367==by 0x400B44E: (within /lib/ld-2.3.6.so) ==21367==by 0x418742C: (within /lib/tls/i686/cmov/libdl-2.3.6.so) ==21367==by 0x4186D20: dlopen (in /lib/tls/i686/cmov/libdl-2.3.6.so) ==21367==by 0x40B3448: (within /usr/lib/libX11.so.6.2.0) ==21367==by 0x40B3756: _XNoticeCreateBitmap (in /usr/lib/libX11.so.6.2.0) ==21367==by 0x40B3B3C: XCreatePixmap (in /usr/lib/libX11.so.6.2.0) ==21367==by 0x40B29BF: XCreateBitmapFromData (in /usr/lib/libX11.so.6.2.0) ==21367== ==21367== Conditional jump or move depends on uninitialised value(s) ==21367==at 0x4008B2E: (within /lib/ld-2.3.6.so) ==21367==by 0x428A704: (within /lib/tls/i686/cmov/libc-2.3.6.so) ==21367==by 0x400B44E: (within /lib/ld-2.3.6.so) ==21367==by 0x4289D1E: _dl_open (in /lib/tls/i686/cmov/libc-2.3.6.so) ==21367==by 0x4186D8D: (within /lib/tls/i686/cmov/libdl-2.3.6.so) ==21367==by 0x400B44E: (within /lib/ld-2.3.6.so) ==21367==by 0x418742C: (within /lib/tls/i686/cmov/libdl-2.3.6.so) ==21367==by 0x4186D20: dlopen (in /lib/tls/i686/cmov/libdl-2.3.6.so) ==21367==by 0x40B3448: (within /usr/lib/libX11.so.6.2.0) ==21367==by 0x40B3756: _XNoticeCreateBitmap (in /usr/lib/libX11.so.6.2.0) ==21367==by 0x40B3B3C: XCreatePixmap (in /usr/lib/libX11.so.6.2.0)
Bug#397412: wmaker: Wmaker crash on creating desktop
On Fri, 17 Nov 2006, Steinar H. Gunderson wrote:
Well, it's a step, at least, but it doesn't really help all that much. Lines
123 and 124 are
123 wWorkspaceMenuUpdate(scr, scr-workspace_menu);
124 wWorkspaceMenuUpdate(scr, scr-clip_ws_menu);
I've put a breakpoint on line 122 and checked the evolution of the various
variables here:
Breakpoint 1, wWorkspaceNew (scr=0x80f0530)
at
/home/rhertzog-deb/partages/debian/paquets/NMU/wmaker-0.92.0/src/workspace.c:123
123 wWorkspaceMenuUpdate(scr, scr-workspace_menu);
(gdb) print scr
$1 = (WScreen *) 0x80f0530
(gdb) print scr-clip_ws_menu
$2 = (struct WMenu *) 0x0
(gdb) print scr-workspace_menu
$3 = (struct WMenu *) 0x817da38
(gdb) n
121 scr-workspaces = list;
(gdb) n
123 wWorkspaceMenuUpdate(scr, scr-workspace_menu);
(gdb) print scr
$4 = (WScreen *) 0x80f0530
(gdb) print scr-clip_ws_menu
$5 = (struct WMenu *) 0x0
(gdb) print scr-workspace_menu
$6 = (struct WMenu *) 0x817da38
(gdb) n
124 wWorkspaceMenuUpdate(scr, scr-clip_ws_menu);
(gdb) print scr-clip_ws_menu
Cannot access memory at address 0x3220c0a0
(gdb) print scr
$7 = (WScreen *) 0x3220bed0
I tried to look in the code how scr could be modified but I didn't find
anything self-evident. :-/
And the only way it could SIGSEGV in line 124, was if scr (that is, the
pointer) was somehow invalid -- but if line 123 was run first (which I'd
assume, even with -O2), scr would have to be valid (unless, of course,
wWorkspaceMenuUpdate was inlined, but it's big and -O2 doesn't normally
inline functions like that).
Stepping inside the function line 123 gives this:
Breakpoint 1, wWorkspaceNew (scr=0x80f0530)
at
/home/rhertzog-deb/partages/debian/paquets/NMU/wmaker-0.92.0/src/workspace.c:123
123 wWorkspaceMenuUpdate(scr, scr-workspace_menu);
(gdb) print scr
$1 = (WScreen *) 0x80f0530
(gdb) step
121 scr-workspaces = list;
(gdb) step
123 wWorkspaceMenuUpdate(scr, scr-workspace_menu);
(gdb) step
wWorkspaceMenuUpdate (scr=0x80f0530, menu=0x817da38)
at
/home/rhertzog-deb/partages/debian/paquets/NMU/wmaker-0.92.0/src/workspace.c:1410
1410if (!menu)
(gdb) step
1403{
(gdb) step
1410if (!menu)
(gdb) step
1413if (menu-entry_no scr-workspace_count+2) {
(gdb) n
1415i = scr-workspace_count-(menu-entry_no-2);
(gdb) s
1417while (i0) {
(gdb) s
1418strcpy(title, scr-workspaces[ws]-name);
(gdb) print title
$2 = \000\002\000\000\000ô_Þ·ÀtÞ·\030%\026\bhsÚ¿ÂåÑ·ÀtÞ·\030%\026\b
(gdb) n
1422entry-flags.editable = 1;
(gdb) print title
$3 = \000\002\000\000\000ô_Þ·ÀtÞ·\030%\026\bhsÚ¿ÂåÑ·ÀtÞ·\030%\026\b
(gdb) n
1418strcpy(title, scr-workspaces[ws]-name);
(gdb) n
1422entry-flags.editable = 1;
(gdb) n
1420entry = wMenuAddCallback(menu, title, switchWSCommand,
(void*)ws);
(gdb) n
1422entry-flags.editable = 1;
(gdb) n
1417while (i0) {
(gdb) n
1433wMenuRealize(menu);
(gdb) n
1435for (i=0; iscr-workspace_count; i++) {
(gdb) n
1436menu-entries[i+2]-flags.indicator_on = 0;
(gdb) n
1435for (i=0; iscr-workspace_count; i++) {
(gdb) n
1436menu-entries[i+2]-flags.indicator_on = 0;
(gdb) n
1435for (i=0; iscr-workspace_count; i++) {
(gdb) n
1436menu-entries[i+2]-flags.indicator_on = 0;
(gdb) n
1435for (i=0; iscr-workspace_count; i++) {
(gdb) n
1436menu-entries[i+2]-flags.indicator_on = 0;
(gdb) n
1435for (i=0; iscr-workspace_count; i++) {
(gdb) n
1438menu-entries[scr-current_workspace+2]-flags.indicator_on = 1;
(gdb) n
1441if (scr-current_workspace == scr-workspace_count-1) {
(gdb) n
1444wMenuSetEnabled(menu, 1, True);
(gdb) print menu
$5 = (WMenu *) 0x817da38
(gdb) n
1447tmp = menu-frame-top_width + 5;
(gdb) n
1449if (menu-frame_x tmp - (int)menu-frame-core-width)
(gdb) n
1447tmp = menu-frame-top_width + 5;
(gdb) n
1449if (menu-frame_x tmp - (int)menu-frame-core-width)
(gdb) n
1452wMenuPaint(menu);
(gdb) n
1453}
(gdb) n
wWorkspaceNew (scr=0x3220bed0)
at
/home/rhertzog-deb/partages/debian/paquets/NMU/wmaker-0.92.0/src/workspace.c:124
124 wWorkspaceMenuUpdate(scr, scr-clip_ws_menu);
So the only solution is that something is overwriting the part of the
memory which contains the pointer scr. But I don't know how to find out
what is responsible of that.
Cheers,
--
Raphaël Hertzog
Premier livre français sur Debian GNU/Linux :
http://www.ouaza.com/livre/admin-debian/
Bug#397412: wmaker: Wmaker crash on creating desktop
On Fri, Dec 15, 2006 at 12:14:02PM +0100, Raphael Hertzog wrote: I could reproduce the bug. It's locale-dependent. Using ru_RU.KOI8-R or ru_RU.UTF-8 allowed me to reproduce the bug. Oh, but that makes it rather obvious. Line 1418, src/workspace.c: strcpy(title, scr-workspaces[ws]-name); title is defined as char title[MAX_WORKSPACENAME_WIDTH+1]; with (wmaker/src/wconfig.h) #define MAX_WORKSPACENAME_WIDTH 32 The ru_RU string for a new workspace is 'Рабочее пространство 1', which is 41 bytes long in UTF-8. Classic stack smash. Just increase MAX_WORKSPACENAME_WIDTH, or stop using strcpy; both should fix the problem. /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#397412: wmaker: Wmaker crash on creating desktop
On Fri, 17 Nov 2006 16:55:58 +0100 Steinar H. Gunderson [EMAIL PROTECTED] wrote: Which GCC version did you used ? I've downloaded a source etch package, and compiled it with GCC-3.4 (it doesnt compile with gcc-4.1), doing export CC=gcc-3.4 ; dpkg-buildpackage, and everything works just fine after that. Yet using etch package and these you've sent to me it crashes predictably. -- С Уважением, Роман Галеев, Уралтелебест - Уфа, 7 3472 512-503
Bug#397412: wmaker: Wmaker crash on creating desktop
On Tue, Dec 05, 2006 at 12:47:50AM +0500, jamhed wrote: when wmaker source package is compiled with default gcc (gcc version 4.1.2 20061028 (prerelease) (Debian 4.1.1-19)), it crashes. when it compiled with gcc-3.4 (gcc version 3.4.6 (Debian 3.4.6-4)), with export CC=gcc-3.4 before making package, it works just fine. This is most likely by accident -- as we saw, building it without optimization does the same thing. wmaker compiled with gcc-4.1 just is not usable. Well, it worked for me, and seemingly for most other people. I'm not sure what makes your configuration special, though :-) /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#397412: wmaker: Wmaker crash on creating desktop
On Mon, Dec 04, 2006 at 11:48:31PM +0500, jamhed wrote: Which GCC version did you used ? 4.1.2, AFAICS. /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#397412: wmaker: Wmaker crash on creating desktop
On Mon, 4 Dec 2006 19:52:11 +0100 Steinar H. Gunderson [EMAIL PROTECTED] wrote: On Mon, Dec 04, 2006 at 11:48:31PM +0500, jamhed wrote: Which GCC version did you used ? Here is what I've got: when wmaker source package is compiled with default gcc (gcc version 4.1.2 20061028 (prerelease) (Debian 4.1.1-19)), it crashes. when it compiled with gcc-3.4 (gcc version 3.4.6 (Debian 3.4.6-4)), with export CC=gcc-3.4 before making package, it works just fine. I've just compiled two versions, and got this stable behaviour. So I suggest to build wmaker with GCC-3.4 only (until anybody'll figure out what happend inside gcc-4.1), and I'd like to see wmaker compiled with gcc-3.4 in etch repository. wmaker compiled with gcc-4.1 just is not usable. -- С Уважением, Роман Галеев, Уралтелебест - Уфа, 7 3472 512-503
Bug#397412: wmaker: Wmaker crash on creating desktop
On Mon, 4 Dec 2006 21:00:07 +0100 Steinar H. Gunderson [EMAIL PROTECTED] wrote: Well, it worked for me, and seemingly for most other people. I'm not sure what makes your configuration special, though :-) I was suspecting my 'special config', because of upgrade, so I've installed fresh etch on another clean machine, it crashed there too. That makes me think there is something wrong. It was netinst from this mirror: http://ftp.kulnet.kuleuven.ac.be/debian Should I try another ? -- С Уважением, Роман Галеев, Уралтелебест - Уфа, 7 3472 512-503
Bug#397412: wmaker: Wmaker crash on creating desktop
On Thu, 16 Nov 2006 17:33:31 +0100 Steinar H. Gunderson [EMAIL PROTECTED] wrote: OK, here's a version of wmaker built with -g -O2 (the other one was built with -g -O0 -DDEBUG). Is it capable of giving a proper backtrace? http://people.debian.org/~sesse/wmaker_0.92.0-6.1~debug2_i386.deb We got it. Finally :) Program received signal SIGSEGV, Segmentation fault. wWorkspaceNew (scr=0x3220bed0) at /home/sesse/nmu/wmaker-0.92.0/src/workspace.c:124 124 /home/sesse/nmu/wmaker-0.92.0/src/workspace.c: No such file or directory. in /home/sesse/nmu/wmaker-0.92.0/src/workspace.c (gdb) bt #0 wWorkspaceNew (scr=0x3220bed0) at /home/sesse/nmu/wmaker-0.92.0/src/workspace.c:124 #1 0x080a6137 in newWSCommand (menu=0x81939d0, foo=0x8194080) at /home/sesse/nmu/wmaker-0.92.0/src/workspace.c:1284 #2 0x08078dba in menuMouseDown (desc=0x8193c08, event=0xafab68b4) at /home/sesse/nmu/wmaker-0.92.0/src/menu.c:2232 #3 0x0806b630 in handleButtonPress (event=0xafab68b4) at /home/sesse/nmu/wmaker-0.92.0/src/event.c:758 #4 0x0806c4fc in DispatchEvent (event=0xafab68b4) at /home/sesse/nmu/wmaker-0.92.0/src/event.c:259 #5 0x080b4183 in WMHandleEvent (event=0xafab68b4) at /home/sesse/nmu/wmaker-0.92.0/WINGs/wevent.c:235 #6 0x0806b079 in EventLoop () at /home/sesse/nmu/wmaker-0.92.0/src/event.c:325 #7 0x08073573 in main (argc=0, argv=0xafab6a04) at /home/sesse/nmu/wmaker-0.92.0/src/main.c:867 May be it will help ;) -- С Уважением, Роман Галеев, Уралтелебест - Уфа, 7 3472 512-503
Bug#397412: wmaker: Wmaker crash on creating desktop
On Fri, Nov 17, 2006 at 01:55:17PM +0500, jamhed wrote: We got it. Finally :) Well, it's a step, at least, but it doesn't really help all that much. Lines 123 and 124 are 123 wWorkspaceMenuUpdate(scr, scr-workspace_menu); 124 wWorkspaceMenuUpdate(scr, scr-clip_ws_menu); And the only way it could SIGSEGV in line 124, was if scr (that is, the pointer) was somehow invalid -- but if line 123 was run first (which I'd assume, even with -O2), scr would have to be valid (unless, of course, wWorkspaceMenuUpdate was inlined, but it's big and -O2 doesn't normally inline functions like that). Did you try running it in valgrind? It might shed some light on what's happening here. /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#397412: wmaker: Wmaker crash on creating desktop
On Fri, 17 Nov 2006 12:41:00 +0100 Steinar H. Gunderson [EMAIL PROTECTED] wrote: What is strange to me that different compiler optimization produces such a devastating difference. Could it be a compiler bug also ? I will try to run it with valgrind, but I've not got much experience with it. At least, yet :) -- С Уважением, Роман Галеев, Уралтелебест - Уфа, 7 3472 512-503
Bug#397412: wmaker: Wmaker crash on creating desktop
On Fri, 17 Nov 2006 12:41:00 +0100 Steinar H. Gunderson [EMAIL PROTECTED] wrote: Here is what I got with Valgrind: ==6506== Memcheck, a memory error detector. ==6506== Copyright (C) 2002-2006, and GNU GPL'd, by Julian Seward et al. ==6506== Using LibVEX rev 1658, a library for dynamic binary translation. ==6506== Copyright (C) 2004-2006, and GNU GPL'd, by OpenWorks LLP. ==6506== Using valgrind-3.2.1-Debian, a dynamic binary instrumentation framework. ==6506== Copyright (C) 2000-2006, and GNU GPL'd, by Julian Seward et al. ==6506== For more details, rerun with: -v ==6506== ==6506== My PID = 6506, parent PID = 6505. Prog and args are: ==6506==wmaker ==6506== ==6506== Conditional jump or move depends on uninitialised value(s) ==6506==at 0x4008ED5: (within /lib/ld-2.3.6.so) ==6506==by 0x4179704: (within /lib/tls/i686/cmov/libc-2.3.6.so) ==6506==by 0x400B44E: (within /lib/ld-2.3.6.so) ==6506==by 0x4178D1E: _dl_open (in /lib/tls/i686/cmov/libc-2.3.6.so) ==6506==by 0x417B53C: (within /lib/tls/i686/cmov/libc-2.3.6.so) ==6506==by 0x400B44E: (within /lib/ld-2.3.6.so) ==6506==by 0x417B59D: __libc_dlopen_mode (in /lib/tls/i686/cmov/libc-2.3.6.so) ==6506==by 0x4097BFA: (within /lib/tls/i686/cmov/libc-2.3.6.so) ==6506==by 0x4097148: (within /lib/tls/i686/cmov/libc-2.3.6.so) ==6506==by 0x409781A: (within /lib/tls/i686/cmov/libc-2.3.6.so) ==6506==by 0x4090480: (within /lib/tls/i686/cmov/libc-2.3.6.so) ==6506==by 0x40F602C: (within /lib/tls/i686/cmov/libc-2.3.6.so) ==6506== ==6506== Conditional jump or move depends on uninitialised value(s) ==6506==at 0x4008B2E: (within /lib/ld-2.3.6.so) ==6506==by 0x4179704: (within /lib/tls/i686/cmov/libc-2.3.6.so) ==6506==by 0x400B44E: (within /lib/ld-2.3.6.so) ==6506==by 0x4178D1E: _dl_open (in /lib/tls/i686/cmov/libc-2.3.6.so) ==6506==by 0x417B53C: (within /lib/tls/i686/cmov/libc-2.3.6.so) ==6506==by 0x400B44E: (within /lib/ld-2.3.6.so) ==6506==by 0x417B59D: __libc_dlopen_mode (in /lib/tls/i686/cmov/libc-2.3.6.so) ==6506==by 0x4097BFA: (within /lib/tls/i686/cmov/libc-2.3.6.so) ==6506==by 0x4097148: (within /lib/tls/i686/cmov/libc-2.3.6.so) ==6506==by 0x409781A: (within /lib/tls/i686/cmov/libc-2.3.6.so) ==6506==by 0x4090480: (within /lib/tls/i686/cmov/libc-2.3.6.so) ==6506==by 0x40F602C: (within /lib/tls/i686/cmov/libc-2.3.6.so) And here is how I run it: .xinitrc: valgrind --tool=memcheck --leak-check=full --log-file=/tmp/wmaker.grind wmaker It seems to me the log above has no use to that particular problem. -- С Уважением, Роман Галеев, Уралтелебест - Уфа, 7 3472 512-503
Bug#397412: wmaker: Wmaker crash on creating desktop
On Fri, Nov 17, 2006 at 04:59:28PM +0500, jamhed wrote: What is strange to me that different compiler optimization produces such a devastating difference. Not really; if it's doing undefined stuff (like writing outside structs), it's just what you would expect happening: Crashes that vary at random with seemingly non-related changes (often with optimization). Could it be a compiler bug also ? Yes, but it's rather unlikely. /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#397412: wmaker: Wmaker crash on creating desktop
On Fri, 17 Nov 2006 12:41:00 +0100 Steinar H. Gunderson [EMAIL PROTECTED] wrote: By the way, I've checked wmaker on additional machine, where I installed fresh etch, It crashes there too. Both are Intel Pentiums, one Mobile, another Celeron. I guess it will crash on every other ? -- С Уважением, Роман Галеев, Уралтелебест - Уфа, 7 3472 512-503
Bug#397412: wmaker: Wmaker crash on creating desktop
On Fri, Nov 17, 2006 at 05:13:17PM +0500, jamhed wrote: .xinitrc: valgrind --tool=memcheck --leak-check=full --log-file=/tmp/wmaker.grind wmaker Well, could you please try the debug2 version too? It looks like this was the debug1 version -- or doesn't it crash in valgrind? /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#397412: wmaker: Wmaker crash on creating desktop
On Fri, 17 Nov 2006 16:55:58 +0100 Steinar H. Gunderson [EMAIL PROTECTED] wrote: On Fri, Nov 17, 2006 at 05:13:17PM +0500, jamhed wrote: .xinitrc: valgrind --tool=memcheck --leak-check=full --log-file=/tmp/wmaker.grind wmaker Well, could you please try the debug2 version too? It looks like this was the debug1 version -- or doesn't it crash in valgrind? What is debug2 ? I didnt figured it from man. -- С Уважением, Роман Галеев, Уралтелебест - Уфа, 7 3472 512-503
Bug#397412: wmaker: Wmaker crash on creating desktop
On Fri, Nov 17, 2006 at 11:59:27PM +0500, jamhed wrote: Well, could you please try the debug2 version too? It looks like this was the debug1 version -- or doesn't it crash in valgrind? What is debug2 ? I didnt figured it from man. The last Debian package I sent you. /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#397412: wmaker: Wmaker crash on creating desktop
On Fri, 17 Nov 2006 20:13:17 +0100 Steinar H. Gunderson [EMAIL PROTECTED] wrote: On Fri, Nov 17, 2006 at 11:59:27PM +0500, jamhed wrote: Well, could you please try the debug2 version too? It looks like this was the debug1 version -- or doesn't it crash in valgrind? What is debug2 ? I didnt figured it from man. The last Debian package I sent you. It was debug2. I've run it with valgrind and crash it. -- С Уважением, Роман Галеев, Уралтелебест - Уфа, 7 3472 512-503
Bug#397412: wmaker: Wmaker crash on creating desktop
On Sat, Nov 18, 2006 at 12:21:57AM +0500, jamhed wrote: The last Debian package I sent you. It was debug2. I've run it with valgrind and crash it. That's odd; the valgrind log you sent didn't contain anything about a crash. Actually, when I look at it, it looks incomplete; it's supposed to print out more stuff when it ends... /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#397412: wmaker: Wmaker crash on creating desktop
On Thu, Nov 16, 2006 at 10:35:02AM +0500, jamhed wrote: It doesnt crash :) Aieee :-) OK, here's a version of wmaker built with -g -O2 (the other one was built with -g -O0 -DDEBUG). Is it capable of giving a proper backtrace? http://people.debian.org/~sesse/wmaker_0.92.0-6.1~debug2_i386.deb You may also want to try all three versions in valgrind; it sometimes gives better backtraces, and it might be able to find the errors even though it doesn't crash. /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#397412: wmaker: Wmaker crash on creating desktop
On Tue, 14 Nov 2006 23:54:56 +0100 Steinar H. Gunderson [EMAIL PROTECTED] wrote: I'm unable to reproduce this. Could you please provide a backtrace? (Start wmaker, attach to it using gdb -p $( pidof WindowMaker ), provoke the crash, do a bt and output the results.) #0 0x080a4ffc in ?? () #1 0x080ef6d8 in ?? () #2 0x0814ebe0 in ?? () #3 0x0002 in ?? () #4 0x0814ebe0 in ?? () #5 0x0814ebe0 in ?? () #6 0x0814f2c0 in ?? () #7 0xafe36908 in ?? () #8 0x080a6137 in ?? () #9 0x080ef6d8 in ?? () #10 0x0814ebe0 in ?? () #11 0xafe36a58 in ?? () #12 0x08078dba in ?? () #13 0x0814ebe0 in ?? () #14 0x0814f2c0 in ?? () #15 0xafe369c8 in ?? () #16 0xa7ea5b24 in ?? () from /usr/lib/libX11.so.6 #17 0x080e2108 in ?? () #18 0x080ef6d8 in ?? () #19 0xafe36968 in ?? () #20 0x013f in ?? () #21 0x in ?? () Here you are, please. -- С Уважением, Роман Галеев, Уралтелебест - Уфа, 7 3472 512-503
Bug#397412: wmaker: Wmaker crash on creating desktop
On Wed, Nov 15, 2006 at 03:37:50PM +0500, jamhed wrote: #16 0xa7ea5b24 in ?? () from /usr/lib/libX11.so.6 #17 0x080e2108 in ?? () #18 0x080ef6d8 in ?? () #19 0xafe36968 in ?? () #20 0x013f in ?? () #21 0x in ?? () Here you are, please. Ugh, bad luck. :-) I've prepared a version with debugging symbols; please install the packages from http://people.debian.org/~sesse/wmaker_0.92.0-6.1~debug_i386.deb http://people.debian.org/~sesse/libwraster3_0.92.0-6.1~debug_i386.deb and fetch a new backtrace. /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#397412: wmaker: Wmaker crash on creating desktop
severity 397412 grave tags 397412 moreinfo unreproducible thanks On Tue, Nov 07, 2006 at 01:48:50PM +0500, Roman Galeyev wrote: It works only with one desktop, called 'Main'. The bug is systematic, it crashes all times I am trying to spawn a desktop. I'm unable to reproduce this. Could you please provide a backtrace? (Start wmaker, attach to it using gdb -p $( pidof WindowMaker ), provoke the crash, do a bt and output the results.) /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#397412: wmaker: Wmaker crash on creating desktop
Package: wmaker Version: 0.92.0-6 Severity: critical Justification: breaks unrelated software I've just upgraded from sarge to etch (testing), was unable to run Wmaker with my old Config. Further investigation shows that Wmaker starts with default config (e.g. from brand new user), but crashes in attempt to spawn one more desktop. It works only with one desktop, called 'Main'. The bug is systematic, it crashes all times I am trying to spawn a desktop. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (990, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-2-686 Locale: LANG=ru_RU.KOI8-R, LC_CTYPE=ru_RU.KOI8-R (charmap=KOI8-R) Versions of packages wmaker depends on: ii cpp 4:4.1.1-13 The GNU C preprocessor (cpp) ii libc62.3.6.ds1-7 GNU C Library: Shared libraries ii libfontconfig1 2.4.1-2 generic font configuration library ii libwraster3 0.92.0-6Shared libraries of Window Maker r ii libx11-6 2:1.0.3-2 X11 client-side library ii libxext6 1:1.0.1-2 X11 miscellaneous extension librar ii libxft2 2.1.8.2-8 FreeType-based font drawing librar ii libxinerama1 1:1.0.1-4.1 X11 Xinerama extension library wmaker recommends no packages. -- no debconf information !DSPAM:455048a2207451223150608! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
