Login | Register   
LinkedIn
Google+
Twitter
RSS Feed
Download our iPhone app
TODAY'S HEADLINES  |   ARTICLE ARCHIVE  |   FORUMS  |   TIP BANK
Browse DevX
Sign up for e-mail newsletters from DevX


Tip of the Day
Language: Visual Basic
Expertise: Beginner
Aug 7, 1997

Use Code Profiler for Debugging

Sometimes a runtime error only manifests itself after an EXE is made and not in debug mode. This can be hard to track down, even with message-box statements. Use the code profiler add-in to find the offending line of code. Following these steps should lead to your error:

  1. First back up your code.
  2. Select the code profiler add-in.
  3. Select the source code file (or all source code files).
  4. Select the Line Hit Count option.
  5. Select the Add Profiler Code button.
  6. Compile the code into an EXE.
  7. Run the code to the error.
  8. Go back to the code profiler and select View Results from the File menu.

Look for the last line that was executed in the offending module. You may have to trace through your code in debug mode at the same time that you look for the last line executed in the profiler.

Rich Spencer
 
Comment and Contribute

 

 

 

 

 


(Maximum characters: 1200). You have 1200 characters left.

 

 

Sitemap
Thanks for your registration, follow us on our social networks to keep up-to-date