[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Search]
Re: dectalk giving invalid command parameter
- To: covici@xxxxxxxxxxx
- Subject: Re: dectalk giving invalid command parameter
- From: "James R. Van Zandt" <jrv@xxxxxxxxxxx>
- Date: Thu, 28 Nov 2002 11:04:28 -0500 (EST)
- CC: emacspeak@xxxxxxxxxxx
- In-reply-to: <m3vg2ovsmj.fsf@xxxxxxxxxxx> (message from John Covici on Sat,23 Nov 2002 17:16:52 -0500)
- Resent-Date: Thu, 28 Nov 2002 14:19:27 -0500 (EST)
- Resent-From: emacspeak@xxxxxxxxxxx
- Resent-Message-ID: <"K9Dq7C.A.QuB.Osm59"@hub>
- Resent-Sender: emacspeak-request@xxxxxxxxxxx
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
-----------------------------------------------------------------------------
To unsubscribe from the emacspeak list or change your address on the
emacspeak list send mail to "emacspeak-request@xxxxxxxxxxx" with a
subject of "unsubscribe" or "help"