Re: [wdiff-bugs] redirecting wdiff output inside a script

[Martin von Gagern]

Hello Steffan,

I fail to reproduce your problem. I don't have a FreeBSD at my disposal,
but perhaps you can help me locate this bug. As I am pretty mystified by
the bug you describe, I'll have to consider unlikely causes, as I can
think of no likely ones.

Can you give me details about what /bin/sh is, i.e. what version of what
shell implementation you're using? Can you try other shells, e.g. bash
or the shell you use for your command line?

Can you please try dropping all paths from the script, like this:

#!/bin/sh
wdiff file1 file2 > scriptout

Executed in the directory where the command line version works, this
should work just as well.

Can you please try without redirecting the output? And also try
redirecting the output not within the script but when calling the script?

Try to have a look at the output in "hexdump -C" or something similar.
Perhaps wdiff decided (for some reason I'd have to discover) to e.g. end
deleted lines with carriage return, so that they would be overwritten by
simple cat output.

Perhaps you could also run the script through strace. Try somthing like
this:

# strace -s 1024 -f -o script.strace /bin/sh scriptfile.sh

The generated file script.strace might provide useful information about
the interaction between wdiff and the other components of your system,
like files, shell, diff, and so on. If you could send me the file, I'd
have a look.

Greetings,
 Martin von Gagern

signature.asc
Description: OpenPGP digital signature