On Mon, 19 Jul 2004, Robert Marshall wrote:

> On Fri, 16 Jul 2004, Bradley T. Hughes wrote:
> 
>> I've been trying to clean this up some.  Attached is a patch that I've 
>> been working on the past week.  I have been running it for a few days 
>> now, and it seems ok, but there might be some kinks to iron out.  Give 
>> it a shot, if you dare :)
>> 
> 
> I thought at first it was a fix but I've just had another crash in
> Toolbar::redrawWindowLabel so maybe the patch has just made it harder to
> replicate ;-)
> 

With the new build (i.e. that patch) I'm also seeing some windows refusing
to focus 

> Now that I'm back from a weekend away I'll look into my menu problem with
> valgrind in the next 24 hours...
> 

I'm trying this but am getting

valgrind bin/blackbox-cvs  -display :1 
==15189== Memcheck, a.k.a. Valgrind, a memory error detector for x86-linux.
==15189== Copyright (C) 2002, and GNU GPL'd, by Julian Seward.
==15189== Using valgrind-1.9.6, a program instrumentation system for x86-linux.
==15189== Copyright (C) 2000-2002, and GNU GPL'd, by Julian Seward.
==15189== Estimated CPU clock rate is 969 MHz
==15189== For more details, rerun with: -v
==15189== ....
...
--15189-- FATAL: unhandled syscall: 7
--15189-- Do not panic.  You may be able to fix this easily.

That's waitpid are there going to be lots of things for which I have to
provide wrappers or is my valgrind installation missing something?

Is anyone running multiple versions of cvs bb? do I just need to have
blackbox and libbt.a somewhere that ld.so.conf knows about?

Too many questions..!

Robert

-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
List archives:  http://asgardsrealm.net/lurker/splash/index.html
Trouble? Contact [EMAIL PROTECTED]

Reply via email to