Re: [dev] valgrind work

2006-08-29 Thread Caolan McNamara 
On Thu, 2006-08-24 at 11:42 +0100, Caolan McNamara wrote:
> I see that there appears to be some valgrind work underway, at least in
> reporting valgrind warnings. 

Sort of relevant to this, glib has it's own memory allocating trickery
just OOo does, and export G_SLICE=always-malloc apparently turns it off
so 

G_SLICE=always-malloc valgrind ... 

might be a more suitable way to call valgrind to also pick up on
problems with glib allocated objects used by OOo.

C.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [dev] valgrind work

2006-08-24 Thread Oliver Braun 

Caolan McNamara wrote:

I see that there appears to be some valgrind work underway, at least in
reporting valgrind warnings. Can I suggest that accessibility be enabled
for these valgrind tests. I highly suspect there are a gadzillion
valgrind-findable bugs exposed with enabling a11y :-(


+1

Oliver

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[dev] valgrind work

2006-08-24 Thread Caolan McNamara 
I see that there appears to be some valgrind work underway, at least in
reporting valgrind warnings. Can I suggest that accessibility be enabled
for these valgrind tests. I highly suspect there are a gadzillion
valgrind-findable bugs exposed with enabling a11y :-(

C.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]