At 1244816834 time_t, Uli Schlachter wrote:
So this must be in some C function from awesome. Sadly they are all marked
static and thus don't emit any symbol, anyone got an idea how we could further
narrow this down?
Recompile with -O0 -fno-inline might help.
--
Julien Danjou
// ᐰ
Success.
It seems the problem is related to Gimp. I had it often running next to Eclipse,
but since the crashes happened when doing something in Eclipse, I suspected the
latter.
I cannot tell any exact way to reproduce the crash. I simply opened a 640x480
greyscale image, drew something in
Hello everybody,
I'll skip all the thank yous and congratulations for this great piece of
software which was the end to my search for the perfect window manager.
Since a few days (since 3.3, I believe), I've had a number of segfault crashes.
Most, if not all of them, happened while using
Andrei Thorp wrote:
awesome[6139]: segfault at 5723000 ip 7f2aa2d7c714 sp 7fffaef40b48
error
4 in libc-2.10.1.so[7f2aa2cff000+14b000]
Good start -- does awesome's std output have anything interesting by the way?
(tell me if you don't quite know what I'm on about)
As I let gdm
Julien Danjou wrote:
At 1244379479 time_t, ElkMonster wrote:
If there's something I can do to find out more, please give some advice. I'm not
very experienced with manual program tracing, gdb, etc.
Try that:
http://awesome.naquadah.org/wiki/Debugging
Oh, I could've found that myself.
