Using the VCL source to track down bugs

My very first article that I had published in a programming Journal happened in the May 2000 issue of C++Builder Developer's Journal. The one and a half page article discussed an issue I had with the behaviour of the VCL and the steps I took to diagnose and fix the problem.

You have probably encountered debugging situations where you lost all hope of ever finding the source of an error. When nothing appears to be wrong with your code, you may have to consider the VCL as a possible source of the problem.

A HTML version of this article is available here

Publication: C++ Builder Developer's Journal
Issue: Volume 4, Number 5, May 2000

Comments

Add new comment

Plain text

  • No HTML tags allowed.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Lines and paragraphs break automatically.
By submitting this form, you accept the Mollom privacy policy.