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
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
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);
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
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
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]
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)
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
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
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
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
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
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
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 ?
--
ะก
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 */
--
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
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 */
--
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
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
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
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
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
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
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
24 matches
Mail list logo
