[aplusdev] Re: Source code change to src/a/u.c to report DOS text APL script corruption

[John.Mizel at morganstanley.com]

I just use plain and simple gdb from either an xterm or xemacs.  I've also
used valgrind to track down memory issues.

Thanks,
John

On Fri, 28 Mar 2003, Art wrote:

>
> --- John.Mizel at morganstanley.com wrote:
> > Hi Art,
> >
> > Thanks for the change, I'll add it to our code base.  I also have
> > some
> > changes and new features pending.
> >
> > I'm suprized 2.96 caused you problems.  Our next build will use some
> > release of 3.2, though we no longer have the hardware or resources to
> > create all the binaries we currently have available for 4.18-8.
> Hi, John,
>
> I build under Windows Cygwin:
>  CYGWIN_98-4.10 1.3.13(0.62/3/2) 2002-10-13 23:15 i686
>  gcc version 2.95.3-5 (cygwin special)
> with no problem - just slow.
>
> Under Linux, I must've corrupted the gcc-c++ installation.
> I used RPM's to install gcc-2.96, libstdc++-2.96, the cpp
> and a few others, but in the end with 3.2-1, I noticed that
> forcing an install with no dependency checking did not
> update the cpp, so I uninstalled the old cpp and installed
> the one compatible with gcc-3.2-1 and also had to do a
> "make clean" which I had not been disciplined about doing
> consistently with my other trials, so I'm almost certain
> I had inconsistent objects in my build space which interfered
> with the APlus build.
>
> I also did a grep for "include.*new.h" and a few others to
> identify and replace the deprecated names with the new names.
> I didn't do this with strstream.h -> sstream.h because this
> caused more problems than I was willing to fix.
>
> I wanted to use DDD to debug, but found myself too clumsy to
> use it effectively, so I just did a few "printf" debugs.
> (Crude, but effective :-)
>
> What debugger do you use? Or recommend?
>
> Best Regards,
>
> Art
>
> __________________________________________________
> Do you Yahoo!?
> Yahoo! Platinum - Watch CBS' NCAA March Madness, live on your desktop!
> http://platinum.yahoo.com
>

This communication is intended for the addressee(s) and may contain
confidential and legally privileged information.  We do not waive
confidentiality or privilege by mistransmission.  If you have received
this communication in error, any use, dissemination, printing or
copying is strictly prohibited; please destroy all electronic and
paper copies and notify the sender immediately.