Hi,
The patch I sent is not actually applicable to this issue.
This issue was fixed in revision 3169, and was released in 1.1.
You report that you are using 1.1, so I'm not sure how you hit this bug.
Is it possible that you are reporting the version of an executable that is different from the one that you are running for the command?
Thanks,
James
Hi,
The patch I sent is not actually applicable to this issue.
This issue was fixed in revision 3169, and was released
in 1.1.
You report that you are using 1.1, so I'm not sure how you
hit this bug.
Is it possible that you are reporting the version of an
executable that is different from the one that you are
running for the command?
Thanks,
James