www.delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1995/04/12/00:13:58

Date: Tue, 11 Apr 1995 22:43:07 -0400
From: dj (DJ Delorie)
To: A DOT D DOT Brown AT bradford DOT ac DOT uk
Cc: djgpp AT sun DOT soe DOT clarkson DOT edu
Subject: Re: symify does a screen grab???

> 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 -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019