[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: dectalk giving invalid command parameter



Thanks, I was thinking of doing something like that as the only way
to get what was actually sent. I'll try this and let everyone know
what happened.

on Thursday 11/28/2002 James R. Van Zandt(jrv@vanzandt.mv.com) wrote
 > 
 > John -
 > 
 > I think you should try strace, which will run a program and generate a
 > trace of every system call.  It's a very powerful debugging tool.
 > 
 > I suggest you run emacspeak under strace, to get a record of exactly
 > what gets written to the device.  Something like this:
 > 
 >   strace -o log -ff -F -s 120 emacspeak  
 > 
 > Run it just long enough to generate the error message.  You'll get
 > several files (some pretty large) named log.XXX where XXX is a process
 > number.  One of them will be for tcl, which reads from emacs and
 > writes to the DECtalk.  Grep for the error message with something like
 > this:
 > 
 >        grep -n invalid log.*
 > 
 > Then visit that file, and look at the preceding few lines to find what
 > was written to the device.
 > 
 > 	    - Jim Van Zandt

-- 
         John Covici
         covici@ccs.covici.com

-----------------------------------------------------------------------------
To unsubscribe from the emacspeak list or change your address on the
emacspeak list send mail to "emacspeak-request@cs.vassar.edu" with a
subject of "unsubscribe" or "help"