Mail Archives: djgpp/1995/04/12/00:13:58
> This is a very strange thing I've noticed, and I'm pretty sure it's not
> intentional. If you do a command like:
>
> symify -o test flibble
>
> Then the screen is dumped into the file called test. (Of course, I'm assuming
> that flibble doesn't exist).
>
> Why?
symify normally reads the screen, looking for a stack trace, and fills
in the extra information. If you specify an output file, the screen
is read and the stack trace is dumped to the file. If there is no
stack trace, it just reads the screen and dumps it to a file. Neat,
huh?
Note that symify has an option for an *input* file as well, from which
it looks for stack traces. No, it doesn't write it to the screen - it
prints it on stdout, if anything.
- Raw text -