01-02-2007, 06:55 AM
Debugging 101!
Well you know it's connected sooo... we'll just jump to the server side at start at the beginning.. ish!
Server: modServerTCP->Sub IncomingData()
Cause a break somewhere after it gets the data!
![[Image: debug101kk9.jpg]](http://img456.imageshack.us/img456/918/debug101kk9.jpg)
Just click where that red dot is on any line past 'frmServer.Socket(Index).GetData ~'
that'll cause a break in your server, pausing it on that line right before it is executed.
Put your mouse over Buffer (anywhere) and make sure it's sendign the right packet.
Try the same thing with handledata(), senddatato(), then go to the client and retry until you figure out where it is 'freezing'.
Sure, there are faster ways, but thats the funnest
You can queue up multiple breaks throughout your source. Just hit F5 or Continue to continue your server as per normal (until/unless it hits another break or soemthing).
Be reminded though, causing breaks can lead to 'timeouts' on either client or server side.
Even if you already knew this, I'm sure someone else didn't so idc.
Well you know it's connected sooo... we'll just jump to the server side at start at the beginning.. ish!
Server: modServerTCP->Sub IncomingData()
Cause a break somewhere after it gets the data!
Just click where that red dot is on any line past 'frmServer.Socket(Index).GetData ~'
that'll cause a break in your server, pausing it on that line right before it is executed.
Put your mouse over Buffer (anywhere) and make sure it's sendign the right packet.
Try the same thing with handledata(), senddatato(), then go to the client and retry until you figure out where it is 'freezing'.
Sure, there are faster ways, but thats the funnest
You can queue up multiple breaks throughout your source. Just hit F5 or Continue to continue your server as per normal (until/unless it hits another break or soemthing).
Be reminded though, causing breaks can lead to 'timeouts' on either client or server side.
Even if you already knew this, I'm sure someone else didn't so idc.