Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!news.cs.indiana.edu!maytag!watstat.waterloo.edu!dmurdoch
From: dmurdoch@watstat.waterloo.edu (Duncan Murdoch)
Newsgroups: comp.os.msdos.programmer
Subject: TD 2.01 bug
Message-ID: <1990Dec12.213319.20466@maytag.waterloo.edu>
Date: 12 Dec 90 21:33:19 GMT
Sender: daemon@maytag.waterloo.edu (Admin)
Organization: University of Waterloo
Lines: 25

Here's a bug in the new version of Borland's debugger that may have you
scratching your head for a while.

If you set a conditional breakpoint, TD will pop up a window telling you
when the condition has been met.  Nice and friendly.

However, if your condition has too many characters in it (mine was
  scWorld.right - scWorld.left > 100*scXAxisTicSize )
then the window may try to create itself wider than your screen.  (Mine's
80 characters wide, which is probably the only width that TD supports.)

If it's just a little bit too wide, it'll wrap around and you'll see the
left part on the right side of your screen.  But if it's a lot too wide,
as the expression above is, then your machine will crash before the
window pops up.  You won't know that the condition has been met, or why
your machine is in outer space.

If you want to try it yourself, you can just add embedded blanks to any
old condition, and eventually trigger the bug.

I've reported it to Borland.  If I hear of a patch from them, I'll 
pass it on.

Duncan Murdoch
dmurdoch@watstat.waterloo.edu