Path: utzoo!mnetor!uunet!husc6!mit-eddie!ll-xn!ames!ucsd!sdcsvax!ucsdhub!hp-sdd!hplabs!hpcea!hpfcdc!hpldola!patch
From: patch@hpldola.HP.COM (Pat Chkoreff)
Newsgroups: comp.lang.c++
Subject: Re: C++ debugging?
Message-ID: <11430006@hpldola.HP.COM>
Date: 16 Feb 88 02:03:22 GMT
References: <41938@ti-csl.CSNET>
Organization: HP Elec. Design Div. -ColoSpgs
Lines: 14

> .../ hpldola:comp.lang.c++ / jss@hector.UUCP (Jerry Schwarz)
> Second, ksh is important because if provides a history mechanism and
> inline editing.  I have a ksh script that sits as a filter in front
> of dbx, and allows me to use these ksh features while interacting
> with dbx.  The history is preserved across invocations of dbx.  Once
> I have used a name in debugging I can usually get it back quickly by
> doing a search in the history.

Easy for you to say!  I want to be able to do this for an arbitrary
interactive program.  I tried some filters using 'set -o vi', '|&', and
read/print with the '-p' option.  I failed.  Would you tell me how you
did it for `dbx'?

P.S.  Do you handle signals correctly?  (Does _anyone_?)