valgrind [Re: [Dillo-dev] dillo-2.2-rc1]

[Jeremy Henty]

On Wed, Feb 03, 2010 at 08:07:13AM +0000, corvid wrote:
> Jeremy wrote:
> > 
> > Thanks.  Everyone is welcome to suggest improvements.
> 
> I've been  wondering whether  it is possible  to check dpid  and the
> dpis as well. Apparently  there's a --trace-children=yes option, but
> it's probably not that simple :)

I'll look into  it.  It may not be so complicated  - valgrind logs the
PID so  it should be  easy to group  the log entries by  process.  The
tricky thing is  identifying the process - currently  I just slurp the
whole output before  doing anything, by which time  the dpi might have
died.  It  might be better to  process it line-by-line so  I can check
the   process  table   right   away.   That   would   need  a   little
re-engineering.  Or maybe it would  be better to replace the dpis with
wrappers that run valgrind?

Hmm,  dillo is somewhat  unusual in  that it  forks children  that are
intended to keep running after  the parent dies.  I don't know whether
valgrind will handle that usefully.  This needs some research.

Meanwhile,  you've  got  to  love  this extract  from  "man  valgrind"
regarding the "--child-silent-after-fork" option:

    This can make the output less confusing (although more misleading)

Meaningful and correct: pick one! :-)

Regards,

Jeremy Henty