Marco van de Voort schreef:
In our previous episode, Vincent Snijders said:
Vincent Snijders schreef:
While running valgrind on fpcdoc, I got a warning in
Maybe you are interested in the valgind output. See attachment.
Another problem, that was also in the valgrind output (reading uninitialized
memory):
EAccessViolation : Access violation
$08099882 TNODEPOOL__DESTROY, line 3304 of src/dom.pp
$080BFF73 THTMLWRITER__WRITEDOC, line 3341 of dw_html.pp
$08049809 CREATEDOCUMENTATION, line 267 of fpdoc.pp
$08049A00 main, line 290 of fpdoc.pp
Nodepool and friends use objects on non-allocated memory. It might be that
valgrind doesn't understand that. I think DOM should have a define to turn
that off, for debugging purposes.
Well, this AV is from a build with gt, which seems to suggest that the nodepool is
reading from uninitialized memory. I doubt that the valgrind warning is false.
I admit these are mere hints at a possible bug, but if I were maintainer of that
code, I would take another look at it.
Vincent
_______________________________________________
fpc-devel maillist - [email protected]
http://lists.freepascal.org/mailman/listinfo/fpc-devel
