I put in a fix a while back and its in valgrind's court to explain why it
doesn't work
'flags' usage looks like this:
unsigned int flags;
/* error checking, assignments, no goto's ... */
if (vex)
{
vex->noexec = -1;
vex->pgrp = -1;
flags = vex->flags;
...
}
else
{
flags = 0;
...
}
/* valgrind complains about 'flags' usage somewhere after here ... */
why does valgrind think 'flags' is not defined?
it must believe vex->flags is ok otherwise it would have complained earlier
On Mon, 6 May 2013 14:24:51 +0200 Roland Mainz wrote:
> Here is the _workaround_ I'm using for ast-ksh.2013-05-03 ... I don't
> know whether this is the _correct_ fix or not:
> -- snip --
> --- ./src/lib/libast/misc/spawnvex.c 2013-05-06 14:16:35.057550745 +0200
> +++ ./src/lib/libast/misc/spawnvex.c 2013-05-06 14:17:25.400515058 +0200
> @@ -793,7 +793,7 @@
> {
> int i;
> int op;
> - unsigned int flags;
> + unsigned int flags = 0U;
> pid_t pid;
> #if _lib_posix_spawn
> int arg;
> -- snip --
> Glenn... can you please *VERIFY* whether this is the right fix (or not) ?
_______________________________________________
ast-developers mailing list
[email protected]
http://lists.research.att.com/mailman/listinfo/ast-developers
