🚀 go-pugleaf

In article <1990Dec12.213319.20466@maytag.waterloo.edu> dmurdoch@watstat.waterloo.edu (Duncan Murdoch) writes:
>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 ...

I tried to set a conditional breakpoint with a long expression and, nearly
as I could figure, the expression was being evaluated incorrectly (triggering
the breakpoint when it shouldn't).  Sounds to me like a buffer overflow that
can manifest itself in more than one way.

Incidently, I recently ran into a floating point divide by zero bug which
would appear only when output was being redirected to a file.  Later, it
crashed the debugger (error window popped up, but further keyboard input
was ignored), forcing a power down reset.  Is Borland's handling of
'87 exceptions up to spec?

                           - Jim Van Zandt