Mail Archives: djgpp/1994/11/01/02:06:41
> I agree that a stack trace does tell you exactly where it broke, but if the
> trace were accompanied by a message "NULL pointer passed to xxxxxx", you
> would know the cause a little quicker. Whether this small advantage is worth
> the trouble of creating and maintaining a debugging library is questionable.
It does. The stack trace lists strcat as the failing function, and
the register dump says that the offending memory address (cr2) is
0x00000000. It's not spelled out in plain English, but it's there.
- Raw text -