FROM : Michael Heins
DATE : Sat Oct 30 18:14:33 2004
On Oct 30, 2004, at 9:21 AM, Wade Tregaskis wrote:
> For a definitive test of your theory, check the contents of the
> registers at some stage before the data is actually sent down the
> wire, and compare it to what you receive... if your theory is correct
> (and you check the register contents close enough to where the data is
> actually sent) you should see some clear correlation.
Wade - Thanks for your help. I did verify with a little
structure-passing C program that the compiler passes the first 32 bytes
of the structure in 8 registers R3 through R10. In my passed
structure, the first 7 registers worth of data are correct, so that's
close but not an exact match to my theory.
As far as catching a look at the data just before it goes over the
wire, I don't know exactly how to do that, but if I set up an
authenticationDataForComponents: method in the sender and break in
there, I can see the encoded data structure just before it is sent, and
by that time, it is very clear that only the first part of the encoded
structure data actually contains valid contents, with the string cut
off with garbage at the same place it is in the received copy.
Michael Heins AA7XY
DATE : Sat Oct 30 18:14:33 2004
On Oct 30, 2004, at 9:21 AM, Wade Tregaskis wrote:
> For a definitive test of your theory, check the contents of the
> registers at some stage before the data is actually sent down the
> wire, and compare it to what you receive... if your theory is correct
> (and you check the register contents close enough to where the data is
> actually sent) you should see some clear correlation.
Wade - Thanks for your help. I did verify with a little
structure-passing C program that the compiler passes the first 32 bytes
of the structure in 8 registers R3 through R10. In my passed
structure, the first 7 registers worth of data are correct, so that's
close but not an exact match to my theory.
As far as catching a look at the data just before it goes over the
wire, I don't know exactly how to do that, but if I set up an
authenticationDataForComponents: method in the sender and break in
there, I can see the encoded data structure just before it is sent, and
by that time, it is very clear that only the first part of the encoded
structure data actually contains valid contents, with the string cut
off with garbage at the same place it is in the received copy.
Michael Heins AA7XY
| Related mails | Author | Date |
|---|---|---|
| Michael Heins | Oct 30, 10:16 | |
| Wade Tregaskis | Oct 30, 11:25 | |
| Michael Heins | Oct 30, 16:28 | |
| Wade Tregaskis | Oct 30, 17:21 | |
| Michael Heins | Oct 30, 18:14 | |
| Jim Correia | Oct 30, 19:46 | |
| Michael Heins | Oct 30, 19:59 | |
| Michael Heins | Oct 31, 17:53 |






Cocoa mail archive

