Welcome, Guest. Please login or register.

Author Topic: Help debugging VBCC output...  (Read 2837 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline Karlos

  • Sockologist
  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Nov 2002
  • Posts: 16879
  • Country: gb
  • Thanked: 5 times
    • Show all replies
Re: Help debugging VBCC output...
« on: June 02, 2005, 02:29:50 PM »
Sorry, I tend to go for serial line level debugging at a source level rather than using debugging software (other than mungwall and enforcer).
int p; // A
 

Offline Karlos

  • Sockologist
  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Nov 2002
  • Posts: 16879
  • Country: gb
  • Thanked: 5 times
    • Show all replies
Re: Help debugging VBCC output...
« Reply #1 on: June 02, 2005, 03:01:44 PM »
The first thing I do is to go through my code very closely and with a lot of coffee. I find this eliminates 95% of problems.

Serial line debugging is just using functions like debuglib/KPrintF() (sends data to the serial port, which can be intercepted with tools like sushi or a terminal on a null modem link since it is not always possible to use printf() or fprintf() functions.

Stuff like enforcer and mungwall just let you spot illegal memory accesses which in my experience are almost always down to oversights with pointers.
int p; // A